06/19/2020
Hello everyone,
I am implementing the specification and have a couple unresolved questions related to the differences between static and dynamic nodes.
The specification in its part 5 says that "Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. For TypeDefinitionNodes, also the InstanceDeclarations shall be identical". It's also true that we could add a reference to an instance node (for example a property) that is not defined in the corresponding type definition. But nothing has been said about references.
My questions:
From an aggregating server point of view
1. Is it true that two instance nodes with identical attributes but different (sets of refferences) on two different server could be considered static?
2. Am I right that for an static TypeDefinitionNode both the attribute set and the references set should be identical? Should a server forbid writes to the value attribute of an Instance declaration that is incorporated into TypeDefinitionNode?
3. Having the OPC foundation namespace as an example, which nodes (types or instances) are static? Where I can find that info?
Thank you.
05/30/2017
1) InstanceDeclarations are Instance nodes. These Nodes are almost always static. Instance Nodes that are not also InstanceDeclarations are rarely static since it would not serve any purpose.
2) The Value of a InstanceDeclaration is the default value and should be fixed by the organization that defined the type.
3) See https://reference.opcfoundatio.....adataType/ StaticNumericNodeIdRange
Search for NodeId="i=15963" in https://files.opcfoundation.or.....deSet2.xml
1 Guest(s)