Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MV] Gateway does not detect additional variables #501

Open
Tracked by #537
izonfreak opened this issue Jun 6, 2023 · 3 comments
Open
Tracked by #537

[MV] Gateway does not detect additional variables #501

izonfreak opened this issue Jun 6, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@izonfreak
Copy link

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:

  1. If I have an object instance that implements a interface that has additional optional components like ICable in the image bellow.

image

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.

  1. 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.

image

(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)

@izonfreak izonfreak added the bug Something isn't working label Jun 6, 2023
@izonfreak izonfreak changed the title Gateway do not detect additional variables Gateway does not detect additional variables Jun 6, 2023
@Kantiran91
Copy link
Member

@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?

@Kantiran91 Kantiran91 changed the title Gateway does not detect additional variables [MV] Gateway does not detect additional variables Jun 7, 2023
@izonfreak
Copy link
Author

izonfreak commented Jun 7, 2023

Environment:

OS: Windows 11.
OPC UA Dashboard Client Version: 2.0.0-rc7
Used Enviroment: umati.app
OPC UA SDK of server: C++ Unified Automation Server SD:

Log.
The log message that could be relevant is the ones that say that my components are "empty" for some reason.

DashboardOpcUaClient-20230606.log

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.

@Kantiran91
Copy link
Member

@GoetzGoerisch: Is this issue relvant for our EPIC? The current MV Demo do not show this additional variables.

@Kantiran91 Kantiran91 assigned Kantiran91 and unassigned mdornaus Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants