OPC UA Object Types
Last updated
Last updated
© Copyright 2024, Cybus GmbH
OPC UA object types define class like structures in OPC UA namespace that can be instantiated and added to the server address space.
For more information on UPC UA Object Types, see the OPC Foundation Reference.
It is possible to create an instance of an object type by using the resource type Cybus::Node::OpcuaObject
Download:
The server provides the structure of the object types and its values as a JSON structure as the example:
_metadata | contains all metadata on a node. The nodeclass corresponds to the node-opcua Nodeclass enum documented here: http://node-opcua.github.io/api_doc/2.0.0/enums/nodeclass.html> On nodes of type “Variable” the dataType entry indicates the OPC UA native data type documented here: http://node-opcua.github.io/api_doc/2.0.0/enums/datatype.html> |
_children | contains child objects in the OPC UA object tree |
_value | contains the plain serialized value as JSON |
Writing updates to the OPC UA object type can be achieved by publishing to the <ObjectNodeName>/write topic. The same JSON structure can be used with updated data in the _value items. For data updates on U/INT64 please review the section on BigInt datatypes in OPC UA Server documentation. It is not necessary to update the complete structure. You can also only write a JSON structure that contains the direct value update. To update all values for the example structure above, only the following structure would be required: