Table 50 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 50 – NamespaceMetadata Object for this specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.0.0 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2017-10-10 , 13:00 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
False |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
{Numeric} |
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
Null |
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
Null |
|
This chapter defines the corresponding profiles and conformance units for the OPC UA Information Model for POWERLINK 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 POWERLINK Information Model companion standard, and for Clients that are communicating with such Servers.
Table 51 defines a server facet for direct access to the POWERLINK Objects through a structured NodeId that may be generated by user entry or by tools.
Table 51 – POWERLINK Direct Access Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
POWERLINK BinaryAddress |
Supports generic access to POWERLINK Objects using opaque NodeIds |
M |
|
POWERLINK StringAddress |
Supports generic access to POWERLINK Objects using string NodeIds |
M |
|
Profiles |
||
|
M |
||
|
O |
||
Table 52 defines a client facet for direct access to the POWERLINK Objects through a structured NodeId that may be generated by user entry or by tools.
Table 52 – POWERLINK Direct Access Client Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
POWERLINK DirectAccessClient |
Use services like Attribute Read or Attribute Write to access POWERLINK Objects through constant NodeIds |
M |
|
Profiles |
||
|
M |
||
|
M |
||
|
O |
||
|
O |
||
Table 53 defines a server facet for access to POWERLINK Objects of the communication profiles EPSG DS 301 and EPSG DS302 through the OPC UA Information Model.
Table 53 – POWERLINK Communication Profile Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
POWERLINK CommunicationProfileServer |
Supports the Information Model for the communication profile EPSG DS 301 and EPSG DS 302 |
M |
|
Profiles |
||
|
M |
||
|
M |
||
|
BaseDevice_Server_Facet (defined in OPC 10000-100) |
M |
|
|
DeviceIdentification_Server_Facet (defined in OPC 10000-100) |
M |
|
|
DeviceCommunication_Server_Facet (defined in OPC 10000-100) |
M |
|
Table 54 defines a client facet for access to POWERLINK Objects of the communication profiles EPSG DS 301 and EPSG DS302 through the OPC UA Information Model.
Table 54 – POWERLINK Communication Profile Client Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
POWERLINK CommunicationProfileClient |
Use OPC UA services like the View Service Set and the Attribute Service Set to browse and access POWERLINK Objects available in the OPC UA Information Model. |
M |
|
Profiles |
||
|
M |
||
|
M |
||
|
M |
||
|
BaseDevice_Client_Facet (defined in OPC 10000-100) |
M |
|
|
DeviceIdentification_Client_Facet (defined in OPC 10000-100) |
M |
|
|
DeviceCommunication_Client_Facet (defined in OPC 10000-100) |
M |
|
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 UA Address Space 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 55 provides a list of mandatory and optional namespaces used in a POWERLINK OPC UA Server.
Table 55 – Namespaces used in a POWERLINK OPC UA Server
|
Namespace |
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 a device represented by the server. This namespace shall have namespace index 1 in the server. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in OPC 10000-100. The namespace index is server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is server specific. |
Mandatory |
|
|
Namespace for NodeId scheme defined in paragraph 8. The namespace index is server specific. |
Optional |
|
|
Vendor specific types and instances |
A server may provide vendor specific types like types derived from PowerlinkDeviceType or PowerlinkCnConnectionPointType, or vendor specific instances of devices in a vendor specific namespace. |
Optional |
Table 56 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 56 – Namespaces used in this specification
|
Namespace |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
1 |
1:SerialNumber |