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.
Table 71 – NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.0 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2018-12-01 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
Vendor-specific |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
Null |
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
{0:9999} |
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
Null |
|
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.
Table 72 – NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.0 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2018-12-01 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
Vendor-specific |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
{NUMERIC_0, STRING_1} |
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
Null |
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
Null |
|
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.
The following tables specify the Facets available for Servers that implement the OPC UA for IO-Link Information Model companion specification.
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.
Table 73 – IO-Link Event Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
IO-Link Events |
Supports Events derived from the IOLinkEventType. |
M |
|
Profiles |
||
|
Standard Event Subscription Server Facet http://opcfoundation.org/UA-Profile/Server/StandardEventSubscription |
||
In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 74.
Table 74 – Optional Facets for IO-Link Event Facet
|
Profiles |
|
Address Space Notifier Server Facet http://opcfoundation.org/UA-Profile/Server/AddressSpaceNotifier |
|
Auditing Server 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.
Table 75 – IO-Link Base Condition Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
IO-Link Alarms |
Supports Events and Objects derived from the IOLinkAlarmType. |
M |
|
Profiles |
||
|
A & C Base Condition Server Facet |
||
In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 76.
Table 76 – Optional Facets for IO-Link Base Condition Facet
|
Profiles |
|
A & C Refresh2 Server Facet |
|
A & C Enable Server Facet |
|
A & C Previous Instances Server Facet http://opcfoundation.org/UA-Profile/Server/ACPreviousInstances |
|
A & C Dialog Server Facet |
|
A & C CertificateExpiration Server Facet http://opcfoundation.org/UA-Profile/Server/ACCertificateExpiration |
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.
Table 77 – IO-Link Alarm Facet
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
IO-Link Alarms |
Supports Events and Objects derived from the IOLinkAlarmType. |
M |
|
Profiles |
||
|
A & C Alarm Server Facet |
||
In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 78.
Table 78 – Optional Facets for IO-Link Alarm Facet
|
Profiles |
|
A & C Acknowledgeable Alarm Server Facet |
|
A & C Exclusive Alarming Server Facet http://opcfoundation.org/UA-Profile/Server/ACExclusiveAlarming |
|
A & C Non-Exclusive Alarming Server Facet http://opcfoundation.org/UA-Profile/Server/ACNon-ExclusiveAlarming |
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.
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.
Table 79 – IO-Link Base Profile
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Generic IO-Link Device, IO-Link Master |
Supports all mandatory ObjectTypes that are connected with the ObjectTypes IOLinkDeviceType and IOLinkMasterType (excluding subtypes defined in this specification). |
M |
|
DiagnosticInfos Support |
Supports delivering DiagnosticInfos in the OPC UA response header. This is used to get additional information about the IO-Link errors. |
O |
|
Profiles |
||
|
Micro Embedded Device 2017 Server Profile http://opcfoundation.org/UA-Profile/Server/MicroEmbeddedDevice2017 |
M |
|
|
Method Server Facet |
M |
|
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
In addition, OPC UA Servers supporting this Facet may optionally also support the Facets defined in Table 80.
Table 80 – Optional Facets for IO-Link Base Profile
|
Profiles |
|
IO-Link Event Facet (see 15.3.1) |
|
IO-Link Base Condition Facet (see 15.3.2) |
|
IO-Link Standard Alarm Facet (see 15.3.3) |
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.
Table 81 – IO-Link Advanced Profile
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Handling of IO-Link Device Descriptions |
Supports Handling of IO-Link Device Descriptions - Supports all mandatory ObjectTypes that are connected with the IOLinkIODDDeviceType. |
M |
|
Management of IO-Link Device Descriptions |
Supports standardized management of IODDs via OPC UA - The optional object IODDManagement with its containing objects and methods shall be mandatory. |
O |
|
Profiles |
||
|
Embedded 2017 UA Server Profile |
M |
|
|
M |
||
|
IO-Link Base Profile (see 15.4.1) |
M |
|
This specification does not define any Client Facets.
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 82 – Namespaces used in an OPC UA for IO-Link Server
|
NamespaceURI |
Description |
Use |
|
Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. |
Mandatory |
|
|
Local Server URI |
Namespace for nodes defined in the local server. This may include types and instances used in an AutoID Device represented by the server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is vendor-specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is vendor-specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames for Nodes generated based on IODDs. |
Optional |
|
|
Vendor-specific types and instances |
A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific namespace. |
Optional |
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.
Table 83 – Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:DeviceRevision |