Open okapies opened 1 year ago
according to the opc ua reference: for the requests you need to use the NodeId-Format only!
the ExpandedNodeId-Format is for storing configurations/nodeid's! after client connecting you need to read the namespace array and resolve the nsu (ns-uri) to ns (ns-idx). the reason for that is that the ns index is not an constant and might change over time as models get added or changed... the only constant is the nsu (the actual unique name in the server) to identify the namespace and within the namespace the constant is the identifier (which is unique within the namespace)
Yes, ns-idx is not realiable to access the nodes. Should we support ns-uri in the request like QuickOpc? It seems we need to normalize the given NodeId
before reading/writing a node to the address space:
Otherwise, ExpandedNodeId
should always be rejected as invalid in requests to the Server
to avoid confusion.
Describe the bug
Server
acceptsExpandedNodeId
as a parameter in a request, but it doesn't match with the node added to the server when its nodeid isNodeId
(i.e. registered by using namespace index instead of namespace URI).To Reproduce
Expected behavior
Normalize the received requests by converting
nsu
andsrv
intons
in theServer
's context.Screenshots
n/a
Version