15 Profiles and Namespaces

15.1 Namespace Metadata

15.1.1 Namespace http://opcfoundation.org/UA/IOLink/

Table 71 defines the namespace metadata for this specification. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.

The information is provided as Object of type NamespaceMetadataType. This Object is a component of the Namespaces Object that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in OPC 10000-5.

The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.

15.1.2 Namespace http://opcfoundation.org/UA/IOLink/IODD/

Table 72 defines the namespace metadata for the namespace http://opcfoundation.org/UA/IOLink/IODD/. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.

The information is provided as Object of type NamespaceMetadataType. This Object is a component of the Namespaces Object that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in OPC 10000-5.

The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.

15.2 Conformance Units and Profiles

This chapter defines the corresponding Profiles and Conformance Units for the OPC UA for IO Link Information Model. Profiles are named groupings of Conformance Units. Facets are Profiles that will be combined with other Profiles to define the complete functionality of an OPC UA Server or Client.

15.3 Server Facets

The following tables specify the Facets available for Servers that implement the OPC UA for IO-Link Information Model companion specification.

15.3.1 IO-Link Event Facet

The “IO-Link Event Facet” defines a Facet for the functionality necessary for IO-Link Events derived from Type IOLinkEventType (see 9.2).

The content of the Profile if defined in Table 73.

In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 74.

15.3.2 IO-Link Base Condition Facet

The “IO-Link Base Condition Facet” defines a Facet for the functionality necessary for IO-Link Conditions derived from Type IOLinkAlarmType (see 9.7).

The content of the Facet if defined in Table 75.

In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 76.

15.3.3 IO-Link Alarm Facet

The “IO-Link Alarm Facet” defines a Facet for the functionality necessary for IO-Link Alarms derived from Type IOLinkAlarmType (see 9.7).

The content of the Facet if defined in Table 77.

In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 78.

15.4 Server Profiles

The following tables specify the Profiles available for IO-Link Devices and Masters that implement the OPC UA for IO-Link Information Model companion specification.

15.4.1 IO-Link Base Profile

This Profile supports the information for IO-Link Masters and IO-Link Devices. It does not include support for IO-Link Device Description file handling.

This Profile is intended to be used of OPC UA servers with limited resources. It is built upon the “Micro Embedded Device 2017 Server Profile” Profile, which supports subscriptions and at least two sessions.

The content of the Profile if defined in Table 79.

In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 80.

15.4.2 IO-Link Advanced Profile

This Profile supports the communication with IO-Link Masters and IO-Link Devices via OPC UA. It includes support for IO-Link Device Description file handling and includes all features of the "IO-Link Base Profile".

This Profile builds upon the “Embedded 2017 UA Server Profile”. In comparison to the "Micro Embedded Device 2017 Server Profile" it adds for example support for Security Policies and the "Standard DataChange Subscription Server Facet".

The content of the Profile if defined in Table 81.

15.5 Client Facets

This specification does not define any Client Facets.

15.6 Handling of OPC UA namespaces

Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.

Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property. All NodeIds of Nodes not defined in this specification shall not use the standard namespaces.

Table 82 provides a list of mandatory and optional namespaces used in an OPC UA for IO-Link Server.

Table 83 provides a list of namespaces and their index used for BrowseNames in this specification. The default namespace of this specification is not listed since all BrowseNames without prefix use this default namespace.