It is assumed that basic concepts of OPC UA information modelling and OPC for Machinery are understood in this specification. This specification will use these concepts to describe the powertrain information model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7, OPC 10000-100, OPC 40001-1, OPC 10000-81 as well as the following apply.
Note that OPC UA terms and terms defined in this specification are italicized in the specification.
Table 1 – OPC UA for Powertrain Terms
Name [en] |
Definition [en] |
Source |
AC/AC converter |
Electric energy converter that changes single-phase or polyphase alternating electric currents to single-phase or polyphase alternating current. |
|
Analog output |
Terminal to which generates an analog voltage signal (e. g. -10 V ...+10 V) or current signal (e. g. 0 ... 20 mA). |
|
Analog input |
Terminal which samples an analog voltage signal (e. g. -10 V ...+10 V) or current signal (e. g. 0 ... 20 mA). |
|
Auxiliary power supply module |
Separately orderable hardware for power supply (e.g., 24V DC) for the electronics of the components of a power drive system (PDS). |
Naming according to IEC 61800-2 |
Axis |
Logical element inside an automation system (e.g., a motion control system) that represents some form of movement. |
DIN EN 61800-7-1:2016-11 |
Basic drive module (BDM) |
Electronic power converter and related control, connected between an electric supply and a motor. |
IEC 61800-2:2015 [3.4];DIN EN 61800-2 (VDE 0160-102):2016-08 |
Braking resistor |
Ohmic resistor that is connected with a brake chopper to the DC link. |
|
Communication interface |
Interface to provide communication capabilities (e.g. RS-485, also known as TIA-485(-A) or EIA-485 and/or Ethernet with related support of communication protocols like e.g. CAN, PROFIBUS, PROFINET, vendor specific communication bus) of a device. The communication interface may be an integrated part of a device (e.g. control module, output converter, ...) or part of an additional extension board/module. |
|
Communication module |
Separately orderable hardware that contains at least one communication interface. |
|
Complete drive module (CDM) |
Drive module consisting of, but not limited to, the BDM and extensions such as protection devices, transformers and auxiliaries, but excluding the motor and the sensors which are mechanically coupled to the motor and/or to the load side of a powertrain. |
IEC 61800-2:2015 [3.8] DIN EN 61800-2 (VDE 0160-102):2016-08 |
Component |
Constituent part of a device which cannot be physically divided into smaller parts without losing its particular function. |
IEC 60050-151 [151-11-21] |
Contactor |
Element intended to carry electric current. |
195-01-07 MOD, see IEC 60050-121, 151-15-56. |
Control module |
Physical unit that contains – in a module/subassembly or device – an application program to control the BDM. |
IEC 61800-7-1 3.2.7 for "control device" |
DC bus |
DC bus is a type of circuit that serves as a common pathway shared by several components, and which uses a direct current voltage level as a reference. |
|
DC bus module |
Separately orderable component and serves as an interface between rectifier and DC/AC converter in electric drives. |
|
DC/DC converter |
Electric energy converter that changes direct electric current to direct electric current of another voltage. |
|
DC link |
Power DC circuit linking the input converter and the output converter of an indirect converter, consisting of capacitors and/or reactors to reduce DC voltage ripple or DC current ripple. |
IEC 61800-2:2015 [3.11] |
Device |
Material element or assembly of such elements intended to perform a required function. NOTE – A device may form part of a larger device. |
IEC 60050-151 [151-11-20] |
Digital output |
Terminal which samples a binary signal (characterized by the states "high" and "low"), with active signal (e.g., 24 V DC) or passive signal (e.g., via optocoupler) and if necessary configurable as switching, pulse, or frequency output. |
|
Digital input |
Terminal which receives a binary signal (characterized by the states "high" and "low"), with active signal (e.g., 24 V DC) or passive signal (e.g., via optocoupler) and if necessary configurable as switching, pulse, or frequency input. |
|
Electric motor |
Electric machine intended to transform electric energy into mechanical energy. Note to entry: For the purposes of this OPC UA Companion Specification, the motor includes all sensors which are mounted on it and which are relevant for supporting the operating mode and interacting with a CDM. |
IEC 61800-2 [3.50] |
Encoder interface |
Interface for any velocity/position sensor input + optionally sensor emulation for output.
The encoder interface may be an integrated part of a device (e.g. control module, output converter, ...) or part of an additional extension module. The encoder interface can also include an interface for additional sensor data (internal or external and a motor type plate). |
|
Encoder interface module |
Separately orderable hardware that contains at least one encoder interface. |
|
Frequency converter |
A device with open loop or/and closed loop control functions for changing the frequency and amplitude of an AC input voltage to control the torque/speed of at least one connected motor. Frequency converters are mainly used in applications with no/slow setpoint changes at their working point like in pumps, fans or conveyor belts. |
|
Gear |
Part of machine to transfer and transform (transmission ratio) movements, energy and torques or forces. |
|
Input converter interface |
Electric energy converter that changes single-phase or polyphase alternating electric currents to unidirectional direct electric current (non-regenerative) and optionally also direct electric current to single-phase or polyphase alternating electric currents (regenerative). |
Based on "rectifier" acc. to IEC 60050-151-2001 [151.13.45] and active input converter acc. to IEC 61800-2 |
Input converter |
Separately orderable hardware that contains at least one input converter interface. |
|
Input filter |
Input filters are filters in the CDM input which are designed to protect the supply network from harmonic loads and/or interference voltages created in the converter. Input filters can be passive or active filters for low-frequency harmonics. Input filters combined with an input reactor are designed to limit the cable-born electromagnetic interference caused by power units according to the specifications of the EMC regulations. Alternative name: Line filter |
|
Input reactor |
Reactor between mains and input converter. Input reactors limit low-frequency network effects to permissible values. Alternative name: line reactor, input choke. |
|
Inverter/Drive |
Electric energy converter that changes direct electric current to single-phase or polyphase alternating current |
IEC 61800-2:2015 |
Motor contactor |
Switching device that is suitable for switching motors on and off. |
|
Motor starter |
The combination of all the devices required to start and stop a motor in combination with suitable overload protection. |
IEC 60947-4-1 |
Operation |
Combination of activities necessary to permit an installation to function. NOTE – Operation includes matters as switching, controlling, monitoring and maintenance as well as any work activities. |
IEC 60050-151 [151-11-28] |
Output converter |
Separately orderable hardware that contains at least an output converter module interface. |
|
Output converter module interface |
Electric energy converter that changes direct electric current to single-phase or polyphase alternating current. |
Based on “output converter module interface” acc. to IEC 60050-151:2001 [151.13.46] for "inverter" |
Output filter |
Du/dt filter or sinus filter to limit high charging/discharging currents and overvoltage (du/dt) on the motor cable (cable between output converter and motor). Alternative name: Motor filter. |
|
Output reactor |
Reactor (inductivity) in the converter or inverter output for reducing the capacitive charge/discharge currents of long motor cables. Alternative name: Motor reactor, choke. |
|
Powertrain |
All asset components related to one or multiple motor(s)/axis system(s) including the drive equipment. |
|
Power drive system(PDS) |
System consisting of one or more complete drive module(s) (CDM) and a motor or motors; any sensors which are mechanically coupled to the motor shaft are also part of the PDS, however the driven equipment is not included. |
IEC 61800-2:2015 [3.79] DIN EN 61800-2 (VDE 0160-102):2016-08 |
Rated value |
Quantity value assigned, generally by a manufacturer, for a specified operating condition of a machine.
Note 1 to entry: The rated voltage or voltage range is the rated voltage or voltage range between lines at the terminals. |
IEC 60050-411:1996, 411-51-23 (also used in IEC 60034-1:2017) |
Rated voltage range |
Voltage range as declared by the manufacturer expressed by its lower and upper rated voltages. |
IEC 60050-151: Amd 2 [151-16-49] |
Resolver |
Electromagnetic motor feedback device with one sine and cosine signal, respectively, are induced in two coils displaced by 90°. |
|
Safe torque off (STO) |
Function to stop a PDS safely by preventing force-producing power from being provided to the motor and by preventing an unwanted restart of the motor (acc. to stop category 0 in EN 60204-1). |
|
Safety interface |
Interface to provide (additional) functional safety capabilities (e.g. STO, SS1, SS2) of a CDM / motor starter. The safety interface may be an integrated part of a device (e.g. control module, output converter, ...) or of an additional extension board/module.
The following standards deal with functional safety: IEC 62061, 61800-5-2, 61800-5-3, ISO 13849-2 |
|
Safety module |
Separately orderable hardware that contains at least a safety interface. |
|
Servo drive |
A device with at least open loop/closed loop control functions for changing the frequency and amplitude of an DC or AC input voltage to control the torque/speed of at least one connected motor.
Servo drives are mainly used in applications in which it is required to follow a setpoint with a high dynamic, respectively where disturbances must be compensated dynamically.
Servo drives usually control servo motors.
The connected motor is not included in this definition of servo drive. |
|
Softstarter |
A motor starter that offers a stepless, smooth starting with a limited starting torque and starting current. |
|
Transformer |
Transformers are used to transform AC voltages and to separate two different voltage potentials. They consist of two coils (primary coil and secondary coil) that are coupled via a magnetic field. |
|
Variable speed drive |
A device that converts the incoming electrical supply of fixed frequency and voltage into a variable frequency and variable voltage output to the motor with the purpose of corresponding the motor speed and torque. |
|
AC Alternating Current
BDM Basic Drive Module
BiSS BiSS Association e.V.
CAN Controller Area Network
CCC China Compulsory Certificate
CC-LinkControl & Communication Link
CDM Complete Drive Module
CE Conformité Européenne
CEL China Energy Label
CiA CAN in Automation
CIP Common Industrial Protocol
CNC Computerized Numerical Control
CoE CAN application Protocol over EtherCAT
DC Direct Current
DIN DIN e.V. (Deutsches Institut für Normung e.V.)
DoE Department of Energy
DT Delta Time
DV Delta Voltage
EMC Electromagnetic Compatibility
EIA-xxx Electronic Industries Alliance
FF-SIS Fieldbus Foundation Safety Instrumented Systems
FSoE Fail Safe over EtherCAT
HTL High-Threshold-Logic
I/O Input/Output
IE International Efficiency
IEC International Electrotechnical Commission
IoT Internet of Things
ISO International Organization for Standardization
MES Manufacturing Execution System
NPN Negative, Positive, Negative
OPC UA FXOPC UA Field eXchange
PDS Power Drive System
PLC Programmable Logic Controller
PNP Positive, Negative, Positive
ProfibusProcess Field Bus
Profinet Process Field Network
RAPIEnetReal-time Automation Protocols for Industrial Ethernet
RS-xxx Recommended Standard
Sercos Serial Realtime Communication System
SLS Safely Limited Speed
SoE Servodrive-Profile over EtherCAT
SSI Synchronous Serial Interface
STO Safe Torque Off
TSN Time-Sensitive Networking
TIA-xxx Telecommunications Industry Association
UKCA UK Conformity Assessment
UL Underwriters Laboratories
VDE Verband der Elektrotechnik Elektronik Informationstechnik e.V.
VDMA Machinery and Equipment Manufacturers Association
Node definitions are specified using tables (see Table 3).
Attributes are defined by providing the Attribute name and a value, or a description of the value.
References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.
- If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.
- The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value (see OPC 10000-3). In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value (see OPC 10000-3) and the ArrayDimensions is set to null or is omitted. Examples are given in Table 2.
Table 2 – Examples of DataTypes
Notation |
DataType |
ValueRank |
ArrayDimensions |
Description |
0:Int32 |
0:Int32 |
-1 |
omitted or null |
A scalar Int32. |
0:Int32[] |
0:Int32 |
1 |
omitted or {0} |
Single-dimensional array of Int32 with an unknown size. |
0:Int32[][] |
0:Int32 |
2 |
omitted or {0,0} |
Two-dimensional array of Int32 with unknown sizes for both dimensions. |
0:Int32[3][] |
0:Int32 |
2 |
{3,0} |
Two-dimensional array of Int32 with a size of 3 for the first dimension and an unknown size for the second dimension. |
0:Int32[5][3] |
0:Int32 |
2 |
{5,3} |
Two-dimensional array of Int32 with a size of 5 for the first dimension and a size of 3 for the second dimension. |
0:Int32{Any} |
0:Int32 |
-2 |
omitted or null |
An Int32 where it is unknown if it is scalar or array with any number of dimensions. |
0:Int32{ScalarOrOneDimension} |
0:Int32 |
-3 |
omitted or null |
An Int32 where it is either a single-dimensional array or a scalar. |
- The TypeDefinition is specified for Objects and Variables.
- The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.
- The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object.
If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.
Note that if a symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2).
Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition.
Table 3 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point to the Node definition.
Table 3 – Type Definition Table
Attribute |
Value |
||||
Attribute name |
Attribute value. If it is an optional Attribute that is not set “--“ will be used. |
||||
|
|
||||
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Other |
ReferenceType name |
BrowseName of the target Node. |
DataType of the referenced Node, only applicable for Variables. |
TypeDefinition of the referenced Node, only applicable for Variables and Objects. |
Additional characteristics of the TargetNode such as the ModellingRule or AccessLevel. |
|
NOTE Notes referencing footnotes of the table content. |
Components of Nodes can be complex that is containing components by themselves. The TypeDefinition, NodeClass and DataType can be derived from the type definitions, and the symbolic name can be created as defined in 3.4.3.1. Therefore, those containing components are not explicitly specified; they are implicitly specified by the type definitions.
The Other column defines additional characteristics of the Node. Examples of characteristics that can appear in this column are show in Table 4.
Table 4 – Examples of Other Characteristics
Name |
Short Name |
Description |
0:Mandatory |
M |
The Node has the Mandatory ModellingRule. |
0:Optional |
O |
The Node has the Optional ModellingRule. |
0:MandatoryPlaceholder |
MP |
The Node has the MandatoryPlaceholder ModellingRule. |
0:OptionalPlaceholder |
OP |
The Node has the OptionalPlaceholder ModellingRule. |
ReadOnly |
RO |
The Node AccessLevel has the CurrentRead bit set but not the CurrentWrite bit. |
ReadWrite |
RW |
The Node AccessLevel has the CurrentRead and CurrentWrite bits set. |
WriteOnly |
WO |
The Node AccessLevel has the CurrentWrite bit set but not the CurrentRead bit. |
If multiple characteristics are defined they are separated by commas. The name or the short name may be used.
To provide information about additional References, the format as shown in Table 5 is used.
The components of the ObjectType have additional references which are defined in Table 5.
Table 5 – <some> Additional References
SourceBrowsePath |
Reference Type |
Is Forward |
TargetBrowsePath |
SourceBrowsePath is always relative to the TypeDefinition. Multiple elements are defined as separate rows of a nested table. |
ReferenceType name |
True = forward Reference |
TargetBrowsePath points to another Node, which can be a well-known instance or a TypeDefinition. You can use BrowsePaths here as well, which is either relative to the TypeDefinition or absolute. If absolute, the first entry needs to refer to a type or well-known instance, uniquely identified within a namespace by the BrowseName. |
References can be to any other Node.
To provide information about sub-components, the format as shown in Table 6 is used.
Table 6 – <some>Type Additional Subcomponents
BrowsePath |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
BrowsePath is always relative to the TypeDefinition. Multiple elements are defined as separate rows of a nested table |
NOTE Same as for Table 3 |
The type definition table provides columns to specify the Attribute values for child Nodesrequired Node Attributes for InstanceDeclarations. To provide information about additional Attributes, the format as shown in Table 7 is used.
Table 7 – <some>Type Attribute values for child Nodes
BrowsePath |
<Attribute name> Attribute |
BrowsePath is always relative to the TypeDefinition. Multiple elements are defined as separate rows of a nested table |
The values of attributes are converted to text by adapting the reversible JSON encoding rules defined in OPC 10000-6. If the JSON encoding of a value is a JSON string or a JSON number then that value is entered in the value field. Double quotes are not included. If the DataType includes a NamespaceIndex (QualifiedNames, NodeIds or ExpandedNodeIds) then the notation used for BrowseNames is used. If the value is an Enumeration the name of the enumeration value is entered. If the value is a Structure then a sequence of name and value pairs is entered. Each pair is followed by a newline. The name is followed by a colon. The names are the names of the fields in the DataTypeDefinition. If the value is an array of non-structures then a sequence of values is entered where each value is followed by a newline. If the value is an array of Structures or a Structure with fields that are arrays or with nested Structures then the complete JSON array or JSON object is entered. Double quotes are not included. |
There can be multiple columns to define more than one Attribute.
The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.
The symbolic name of each Node defined in this document is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, a “.”, and the BrowseName of itself. In this case “part of” means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this document, the symbolic name is unique.
The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri is vendor-specific and depends on the position of the NamespaceUri in the server namespace table.
Note that this document not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this document, because they are not defined by this document but generated by the Server.
The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this document is defined in Table 164.
For InstanceDeclarations of NodeClass Object and Variable that are placeholders (OptionalPlaceholder and MandatoryPlaceholder ModellingRule), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended in OPC 10000-3. If the BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to ‘0:EngineeringUnits’ or prefix '2' leading to ‘2:DeviceRevision’). This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this document. Table 166 provides a list of namespaces and their indexes as used in this document.
The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this specification or if it is server-specific.
For all Nodes specified in this specification, the Attributes named in Table 8 shall be set as specified in the table.
Table 8 – Common Node Attributes
Attribute |
Value |
DisplayName |
The DisplayName is a LocalizedText. Each server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId “en”. Whether the server provides translated names for other LocaleIds is server-specific. |
Description |
Optionally a server-specific description is provided. |
NodeClass |
|
NodeId |
The NodeId is described by BrowseNames as defined in 3.4.2.1. |
WriteMask |
Optionally the WriteMask Attribute can be provided. If the WriteMask Attribute is provided, it shall set all non-server-specific Attributes to not writable. For example, the Description Attribute may be set to writable since a Server may provide a server-specific description for the Node. The NodeId shall not be writable, because it is defined for each Node in this specification. |
UserWriteMask |
Optionally the UserWriteMask Attribute can be provided. The same rules as for the WriteMask Attribute apply. |
RolePermissions |
Optionally server-specific role permissions can be provided. |
UserRolePermissions |
Optionally the role permissions of the current Session can be provided. The value is server-specifc and depend on the RolePermissions Attribute (if provided) and the current Session. |
AccessRestrictions |
Optionally server-specific access restrictions can be provided. |
For all Objects specified in this specification, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.
Table 9 – Common Object Attributes
Attribute |
Value |
EventNotifier |
Whether the Node can be used to subscribe to Events or not is server-specific. |
For all Variables specified in this specification, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.
Table 10 – Common Variable Attributes
Attribute |
Value |
MinimumSamplingInterval |
Optionally, a server-specific minimum sampling interval is provided. |
AccessLevel |
The access level for Variables used for type definitions is server-specific, for all other Variables defined in this specification, the access level shall allow reading; other settings are server-specific. |
UserAccessLevel |
The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least one user. |
Value |
For Variables used as InstanceDeclarations, the value is server-specific; otherwise it shall represent the value described in the text. |
ArrayDimensions |
If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the Variable. |
Historizing |
The value for the Historizing Attribute is server-specific. |
AccessLevelEx |
If the AccessLevelEx Attribute is provided, it shall have the bits 8, 9, and 10 set to 0, meaning that read and write operations on an individual Variable are atomic, and arrays can be partly written. |
For all VariableTypes specified in this specification, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.
Table 11 – Common VariableType Attributes
Attributes |
Value |
Value |
Optionally a server-specific default value can be provided. |
ArrayDimensions |
If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType. |
For all Methods specified in this specification, the Attributes named in Table 12 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.
Table 12 – Common Method Attributes
Attributes |
Value |
Executable |
All Methods defined in this specification shall be executable (Executable Attribute set to “True”), unless it is defined differently in the Method definition. |
UserExecutable |
The value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user. |