OPC UA Node
OPC UA Node
In OPC UA, information is encapsulated and exchanged using object and variable node structure. In addition, remote procedures can be invoked by using method nodes.
- Object nodes are not holding value information but they can contain other object, variable or method nodes.
- Variable nodes can hold values and they can also contain other variable nodes.
- Method nodes are remote procedures that can be called and they can have input arguments (parameters) and output arguments (return values).
Note: By using CDP Studio OPC UA discovery functionality you can easily find remote server object structure and create OPC-UA-Client configuration and node structures without configuring the nodes manually. See also OPC UA Server Discovery.
All nodes have the following common configuration properties:
| Property | Description |
|---|---|
| IdType<string> | Select one of the following types:
|
| Id<string> | OPC UA node Id. Must be set manually, when non-Automatic IdType is used. Value entered must match chosen IdType. |
| NamespaceIndex<string> | OPC UA namespace index. Must be set manually, when non-Automatic IdType is used. NamespaceIndex 0 is reserved for OPC UA internal use. NamespaceIndex 1 can be safely used for user nodes. |
| DisplayName<string> | Node OPC UA DisplayName (e.g. Name of the Node that should be used to display the name in a user interface) (this property is read only in OPC UA client) |
| AccessLevel<string> | Access level flags for this OPC UA node (this property is read only in OPC UA client). The following OPC UA access flags can be set:
|
In the OPC-UA-Client, node state can be observed at runtime via these read-only properties:
| Property | Description |
|---|---|
| StatusCode<unsigned int> | OPC UA status code of accessing the node |
| StatusString<string> | OPC UA status string of accessing the node |
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.