03/01/2026
OfflineHello OPC UA community!
We are in a discussion with the support of a manufacturer of NC-controllers, providing a integrated OPC UA server, about the namespaces of the BrowseNames of the standard FileType methods Open/Close,...
I am not able to find a clear statement about this in the OPC UA specification, presumable because OPC UA is a quite new topic for me.
The implementation in the OPC UA server defines the BrowseName of the methods in the same namespace as the instance of the file itself. As example:
- NodeId of file: ns=2;s=FileSystem/Part Program/TEST123.MPF
- BrowseName of file: 2:TEST123.MPF
- NodeId of method: ns=2;s=FileSystem/Part Program/TEST123.MPF.Open
- BrowseName of method Open: 2:Open
Should the BrowseName of the method part of namespace 0 because it is inherit from the type definition FileType? Do you can give me a hint to the OPC UA specification, which clearify this?
I would assume, the NodeId and BrowseName of the methods as follows:
- NodeId of method: ns=2;s=FileSystem/Part Program/TEST123.MPF.Open
- BrowseName of method Open: 0:Open
Thank your for your ansers in advance
nico
05/30/2017
OfflineAll ObjectType definitions specify the BrowseNames of their components including the Namespace.
If you create an instance of a FileType then all of the components will use the BrowseName from the FileType.
The NodeId of the component is whatever you want because the Node is owned by you even if the BrowseName comes from the FileTYpe.
This all explained in Part 3:
https://reference.opcfoundatio.....5/docs/6.4
1 Guest(s)


Log In

Usage Policy