Application Defined Namespaces
The application defined namespaces contain the information model designed for the specific application. The namespaces can be device specific or be defined by Companion specifications, organizations and vendors.
Namespace Index | Namespace |
|---|---|
0 | OPC Foundation namespace |
1 | Local server namespace |
2–N | Application defined namespaces |
M (M ⊂ 2-N) | Parameters namespace, see Parameters Namespace. If mapping an OPC UA variable to an ADI, this namespace must be included in the information model. The namespace URI of this namespace shall be set to urn:compactcom40:parameters. |
NodeClasses
The NodeClasses table describes the supported node classes and any limitations when using them in an application defined information model namespace. No multilingual support (except variable nodes mapped to ADIs) is available.
NodeClass | Considerations |
|---|---|
OBJECT | The EventNotifier attribute must be set to 0 (no event support) |
VARIABLE | Variables tied to ADIs must be modeled in the Parameters namespace, see Parameters Namespace. Other variables can be modeled in any namespace. Variables tied to ADIs can only use data types (no structured data types) from the OPC Foundation namespace (namespace 0). |
METHOD | Method calls will be forwarded to the host application, see Command Details: Method_Call. |
OBJECT_TYPE | |
VARIABLE_TYPE | The value attribute of this node class defines the default value of any variable node of this type. The host application must be aware of this default value and use it for any ADI that maps to a variable node of this type. |
REFERENCE_TYPE | |
DATA_TYPE | The following data types are not supported:
|
VIEW | The EventNotifier attribute must be set to 0 (no event support). Use of view nodes in the Browse service of the view service set is not supported. |