-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Node-opcua inherits variables from objectType with same name as variable browseName. #1326
Comments
Might actually be related to #1320. |
Just to clarify this only goes wrong when doing dynamic object instantiation, i.e. |
Problem is probably caused by this line of code:
The while loop keeps iterating until it reaches |
…ed object type to a node with the same browseName.
…ed object type to a node with the same browseName.
…ed object type to a node with the same browseName.
…type to a node with the same browseName.
fixed in node-opcua@2.121.0 |
Current behavior / Describe the bug
When a variable's BrowseName on one objectType matches the name of another objectType that inherits from BaseObjectType then it will take over the reference from that objectType when instantiating.
See the configuration in the Siemens modelling editor:
See how the instantiated node looks like:
Step by step instruction to reproduce
Steps to reproduce the behavior:
Opc.Ua.NodeSet2.xml
into the folder as wellnpm install
node server.js
Expected behavior
In the example scenario in the image I would expect only the Name variable to be there.
Gist
gist: https://gist.github.com/tetanw/248223774efafe9a5593dbd55f063145
Context
( ) my request is related to node-opcua acting as an OPCUA CLIENT
(x) my request is related to node-opcua acting as an OPCUA SERVER
( ) I have installed node-opcua from source ( using git clone)
(x) I have installed node-opcua as a package ( using npm install )
( ) I am using an application that uses node-opcua
Device: Lenovo Thinkstation P700
OS version:
Description of the other OPCUA system I am trying to connect to: NA
node-opcua version: 2.118.0
Node: v18.16.0
The text was updated successfully, but these errors were encountered: