OPC UA namespaces

The GlobalDataSpace namespace

All programs and variables from the IEC 61131 context are displayed in the http://phoenixcontact.com/OpcUA/PLCnext/GlobalDataSpace/ namespace. Via the namespace, the corresponding NamespaceIndex can be determined from the NamespaceArray. The NamespaceIndex is a numeric value for identification of the namespace. It is saved in the NamespaceArray. Via the NamespaceIndex and the NodeIdentifier, a corresponding process variable, structure or function block can be retrieved.

 

The NodeIdentifier is always structured like this: [component name]/[program name].[variable name]

Example: Arp.Plc.Eclr/PG_AllTypes1.DIntVar

 

In the Variable: PC_Worx_Engineer is not defined in the project. it looks like this:

NamespaceGDS.png

 

In the OPC UA client software UaExpert it looks like this:

NamespaceGDS_opc.png

 

The component name for C++ components is defined in the respective C++ project. It therefore differs from the component name from the IEC 61131 context (Arp.Plc.Eclr).

The Device Integration (DI) namespace

In compliance with the OPC UA for Devices OPC UA Companion Specification, the eUA server provides the following nodes:

Node Meaning

DeviceManual

Path or URL to the user manual.
Note: The eUA server does not support this node.
Default value: Empty string

DeviceRevision

General revision status of the device.
Note: The eUA server does not support this node.
Default value: Empty string

HardwareRevision

Hardware revision status, e.g., 02.

Manufacturer

Device manufacturer, e.g., en, Phoenix Contact

Model

Name of the model, e.g., en, AXC F 2152

RevisionCounter

Revision status of the static device data, e.g., 2

SerialNumber

Device serial number, e.g., 13254768

SoftwareRevision

Software version number, e.g., 2019.0 LTS (19.0.0.15906)