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
Some servers may return nodes in the format of ExpandedNodeId when browsing.
When these contain a serverIndex > 0, it points to a remote server that can be discovered using URI information read from a table on the server.
Should the OPC UA support be able to handle such ExpandedNodeIds? If yes, how?
Some servers may return nodes in the format of
ExpandedNodeId
when browsing.When these contain a
serverIndex
> 0, it points to a remote server that can be discovered using URI information read from a table on the server.Should the OPC UA support be able to handle such ExpandedNodeIds? If yes, how?
See also:
https://reference.opcfoundation.org/v104/Core/docs/Part4/7.11/
https://opcfoundation.org/forum/opc-ua-standard/expanded-nodeid-vs-nodeid/
The text was updated successfully, but these errors were encountered: