Log In
03/19/2019
Offline
Hi,
when to use the FileSystem NodeId i=16314 for a FileSystem instance? Is it reserved for FileSystem instances referenced directly under the Objects (i=85) folder?
The spec says, that the BrowseName has to match "<ns>:FileSystem" (not even restricts it to "0:FileSystem") but it does not define the standard NodeId (i=16314):
The Object representing the root of a file directory structure shall have the BrowseName FileSystem. An OPC UA Server may have different FileSystem Objects in the AddressSpace. HasComponent is used to reference a FileSystem from aggregating Objects like the Objects Folder or the Object representing a device.
The Opc.Ua.NodeSet2.xml contains this NodeId, but is not referenced:
<UAObject NodeId="i=16314" BrowseName="FileSystem">
Best regards,
Thomas
05/30/2017
Offline
i=16314 was added to define the BrowseName but it pre-dated IsDesignTool attribute.
Need to add IsDesignTool which will make it clear why it is not referenced.
You should never use i=16314
03/19/2019
Offline
Thank you.
And for the BrowseName under the Objects (i=85) folder: Should we use 0:FileSystem or <instanceNs>:FileSystem (e.g. 5:FileSystem, when 5 is our FileSystem namespace)?
Clients can only detect if a Server supports the File Transfer - File System Spec by browsing the Objects-Folder (i=85) and filtering for *:FileSystem results, right?
1 Guest(s)
Usage Policy