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.

Sign up for GitHub

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

Jump to bottom

MachineryBuildingBlocks not in Machinery but LADSNodeSet wants to use via BrowseName #4

Open

AlbrechtLiebscher opened this issue Nov 15, 2024 · 1 comment

Collaborator

AlbrechtLiebscher commented Nov 15, 2024 •

edited

Loading

And is defindes twice with different IDs

<UAObject NodeId="ns=4;i=5063" BrowseName="3:MachineryBuildingBlocks" ParentNodeId="ns=4;i=1002">
-----parent---><UAObjectType NodeId="ns=4;i=1002" BrowseName="4:LADSDeviceType">
second one:
<UAObject NodeId="ns=4;i=5088" BrowseName="3:MachineryBuildingBlocks" ParentNodeId="ns=4;i=1024">
-----parent---><UAObjectType NodeId="ns=4;i=1024" BrowseName="4:LADSComponentType">

Modelcompiler is strongly nameoriented and struggles after usage

The text was updated successfully, but these errors were encountered:

Collaborator Author

AlbrechtLiebscher commented Nov 22, 2024

Create new Names in other Namespace from LADS Nodeset. This could not be handled by modelcompiler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment