Table 105 defines the namespace metadata for this specification. The Objects are 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 105 – NamespaceMetadata Object for this Document
|
Attribute |
Value |
||
|
BrowseName |
|||
|
Property |
DataType |
Value |
|
|
NamespaceUri |
String |
||
|
NamespaceVersion |
String |
1.0.1 |
|
|
NamespacePublicationDate |
DateTime |
2021-04-13 |
|
|
IsNamespaceSubset |
Boolean |
False |
|
|
StaticNodeIdTypes |
IdType [] |
0 |
|
|
StaticNumericNodeIdRange |
NumericRange [] |
|
|
|
StaticStringNodeIdPattern |
String |
|
|
This chapter defines the corresponding Profiles and Conformance Units for the OPC UA Information Model for PROFINET. 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 PROFINET Information Model companion specification.
Table 106 defines a facet for implementation of the OPC UA Server providing the information model in a PROFINET device.
Table 106 – PROFINET Device Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Device View from Device |
Supports the objects and variables defined in the device view illustrated in chapter 6.3.1. The information model is created with the PROFINET device aspect of the data. |
M |
|
Controller View from Device |
Supports the objects and variables defined in the controller / application view illustrated in chapter 6.3.1. The information model is created with the PROFINET device aspect of the data. |
M |
|
Profile |
||
|
Nano Embedded Device Server Profile (defined in [OPC 10000-7]) |
M |
|
|
ComplexType Server Facet (defined in [OPC 10000-7]) |
M |
|
Table 107 defines a facet for implementation of the OPC UA Server providing the information model in a PROFINET Controller.
Table 107 – PROFINET Controller Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Device View from Controller |
Supports the objects and variables defined in the device view illustrated in chapter 6.3.1. The information model is created with the PROFINET controller aspect of the data. |
M |
|
Controller View from Controller |
Supports the objects and variables defined in the controller / application view illustrated in chapter 6.3.1. The information model is created with the PROFINET controller aspect of the data. |
M |
|
Network Topology from Controller |
Supports the objects and variables defined in the chapter 6.3.1.7 for representing the physical network topology. The information model is created with the PROFINET controller aspect of the data. |
O |
|
Events |
Supports the event notification of changes in the assets and the topology if topology objects are supported. |
M |
|
Conditions |
Supports diagnosis conditions for the notification of new device diagnosis events. |
O |
|
Profile |
||
|
Micro Embedded Device Server Profile (defined in [OPC 10000-7]) |
M |
|
|
ComplexType Server Facet (defined in [OPC 10000-7]) |
M |
|
|
A & C Base Condition Server Facet (defined in [OPC 10000-7]) |
O |
|
|
Standard Event Subscription Server Facet (defined in [OPC 10000-7]) |
M |
|
Table 108 defines a facet for implementation of the OPC UA Server providing the information model in a PROFINET Gateway.
Table 108 – PROFINET Gateway Server Facet Definition
|
Conformance Unit |
Description |
Optional/ Mandatory |
|
Device View from Gateway |
Supports the objects and variables defined in the device view illustrated in chapter 6.3.1. The information model is created with the PROFINET gateway aspect of the data. |
M |
|
Controller View from Gateway |
Supports the objects and variables defined in the controller / application view illustrated in chapter 6.3.1. The information model is created with the PROFINET gateway aspect of the data. |
M |
|
Network Topology from Gateway |
Supports the objects and variables defined in the chapter 6.3.1.7 for representing the physical network topology. The information model is created with the PROFINET gateway aspect of the data. |
O |
|
Events |
Supports the event notification of changes in the assets and the topology if topology objects are supported.
|
M |
|
Conditions |
Supports diagnosis conditions for the notification of new device diagnosis events. |
O |
|
Profile |
||
|
Micro Embedded Device Server Profile (defined in [OPC 10000-7]) |
M |
|
|
ComplexType Server Facet (defined in [OPC 10000-7]) |
M |
|
|
A & C Base Condition Server Facet (defined in [OPC 10000-7]) |
O |
|
|
Standard Event Subscription Server Facet (defined in [OPC 10000-7]) |
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 UA 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 109 provides a list of mandatory and optional namespaces used in a PROFINET OPC UA Server.
Table 109 – Namespaces used in a PROFINET OPC UA 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 PROFINET Device represented by the Server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames of the base information model defined in this specification. The namespace index is Server specific. |
Mandatory |
|
|
Vendor specific types |
A Server may provide vendor-specific types like types derived from ObjectTypes defined in this specification in a vendor-specific namespace. |
Optional |
|
Vendor specific instances |
A Server provides vendor-specific instances of the standard types or vendor-specific instances of vendor-specific types in a vendor-specific namespace. It is recommended to separate vendor specific types and vendor specific instances into two or more namespaces. |
Mandatory |
Table 110 – Namespaces used in this specification 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 110 – Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |