eclipse-aaspe / package-explorer

AASX Package Explorer
Other
57 stars 20 forks source link

interconnected for REST data exchange with OperationalData/Plotting of Properties #92

Open mhlee0328 opened 2 years ago

mhlee0328 commented 2 years ago

Hello team,

Describe the bug We saw an impressive example from Festo_Demo_Box and the 210201_Sample_Repo_AASX.mp4 video doing nice sync to plotting! We download Sample_Repo_AASX_publish and a bunch of aasxs. The option stay connected was enabled. We tried to monitor the sensor data value in aasx-package-explorer sync to the REST API. But OperationalData value only updates when we double click reload ​download the aasx files via HTTP from AASX Server.

To Reproduce

  1. AAS/Demo_box_123456/Submodel/OperationalData/Cylinder_1_Counter value via AASX Server REST API put method in the postman, we have succeeded in changing the value from '300' to '1234'.
  2. We could see that the Blazor web interface port: 5010 retrieves new value without clicking the refresh button in chrome.

Expected behavior However, the value of an element changed over OPC UA and the same element is observed via the REST interface, the value change is not recognized by the REST API. The PlottingViewControl value is not interconnected for OPCUA or REST data exchange.

Screenshots

The code Plugins\PlottingViewControl.xaml and the code behind PlottingViewControl.xaml.cs. The following property values bind and sync well when VS2019 c# debug mode by manually changing the particular Cylinder_1_Counter {AasxPluginPlotting.PlottingViewControl.PlotItem}/SME/value. The plotting DataGridPlotItems value change as I want.

Desktop (please complete the following information):

thanks

mhlee0328 commented 2 years ago

Hello, teams

I made the MQTT client subscribe OperationalData payload dynamic binding to AasxPluginPlotting display value. It is not in an elegant way but works so far. As I mention the same property value that exists on the aasx server still needs to be set manually either the OPC UA or REST, otherwise they do not synchronize with the aasx-package-explorer. Also, the aasx server REST put method causes property valueType missing from double to empty. This causes stop to update values.

2021-12-09_100238

2021-12-07_200002

2021-12-07_195938

2021-12-09_103101

juileetikekar commented 6 months ago

Hi @mhlee0328,

Does the issue still exist? If possible, could you please try the latest version of the AASX Package Explorer?