You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I add an additional variable to my instance object using. It does not get picked up by the gateway and not pass in the json. I have found this issue in two specific cases:
If I have an object instance that implements a interface that has additional optional components like ICable in the image bellow.
In this case the gateway is able to monitor the maintenance variables from the base type IVisionInfoType but not the ones added in the subtype ICableType. When the information is transmitted the Diameter, Length, Shielding and Connectors properties are missing from the json.
If I instantiate additional variables inside a folder or below an object. The new variables are instantiated as component in the
folder or as addIn.
(Note: Please ignore that the screen shot is not Machinery ResultManagment it is just to illustrate)
Consider the use case for Machinery ResultManagement where the result variables are contained inside a folder. If I instance a single variable inside the folder for umati to monitor ( i will be updating the variable with the latest result) the gateway does not add it to the json, independent on the type of the variable that I use (Int32, string or a structure). This same problem persist if I for example try to add a variable instance to my object instance. If I add any variable to my object that is not on the type it does not pick it up. I had to create a subtype of my ObjectType that includes the variable as a mandatory component to get the gateway to transmit the information. However, this seems to break the umati app in other ways (see : https://github.com/umati/Dashboard/issues/1107)
The text was updated successfully, but these errors were encountered:
@izonfreak
Could you please give us more information: Environment:
OS: [e.g. Windows Version xx, Linux, Container]
OPC UA Dashboard Client Version [branch, version]
Used Enviroment [umati.app, staging.umati.app, dev.umati.app]
OPC UA SDK of server [e.g. open62541]
Log
Upload log file or relevant error logs.
@xenonforlife: Are these variables used in the Dashboard at the automatica fair? @mdornaus: Could you please have a look at the for the fair relevant variables?
For the variables in a folder I suppose that the gateway indeed finds the variables otherwise #497 will not happen, but it seems that it just ignore them.
Your questions: Are these variables used in the Dashboard at the automatica fair?
Other than the results in the result folder, the additional variables in the components are not really relevant for the automatica fair as far as I understood. However, I find this issue relevant for future demos that might want to add additional components only to the instances of their objects.
When I add an additional variable to my instance object using. It does not get picked up by the gateway and not pass in the json. I have found this issue in two specific cases:
In this case the gateway is able to monitor the maintenance variables from the base type IVisionInfoType but not the ones added in the subtype ICableType. When the information is transmitted the Diameter, Length, Shielding and Connectors properties are missing from the json.
folder or as addIn.
(Note: Please ignore that the screen shot is not Machinery ResultManagment it is just to illustrate)
Consider the use case for Machinery ResultManagement where the result variables are contained inside a folder. If I instance a single variable inside the folder for umati to monitor ( i will be updating the variable with the latest result) the gateway does not add it to the json, independent on the type of the variable that I use (Int32, string or a structure). This same problem persist if I for example try to add a variable instance to my object instance. If I add any variable to my object that is not on the type it does not pick it up. I had to create a subtype of my ObjectType that includes the variable as a mandatory component to get the gateway to transmit the information. However, this seems to break the umati app in other ways (see : https://github.com/umati/Dashboard/issues/1107)
The text was updated successfully, but these errors were encountered: