User Documentation
Table Of Contents
- Table of contents
- 1 Introduction
- 2 Safety instructions
- 3 System overview
- 4 Operating behavior
- 5 Software installation
- 6 Configuration
- 7 Program development
- 8 Licensing
- 9 Device Administration (DevAdmin)
- 10 Software units
- 11 OPC UA Server
- 12 Node-RED
- 13 LongtermDiagnosticMonitor
- 14 Data recorder
- 15 Diagnostics
- 16 Maintenance
- 17 Technical data
- 18 Directives and standards
- 19 Appendix: Tutorial - creating an IEC project
- 20 Appendix: Addressing in the Ethernet (basics)
- 21 Appendix: Tutorial FoE
- 22 Appendix: Tutorial - call C function from IEC
- Index

OPC UA Server
System manual
2696790000/02/04.2020
64
Information
Currently not all data types defined in the OPC UA standard are supported.
The following table describes the supported OPC UA data types with the
corresponding IEC data types. The unique node address that must be used
when creating in the XML file is specified for each data type. The node ad-
dress consists of multiple so-called "BrowseNames". BrowseName is an
OPC UA concept that can be used to specify node addresses. A Browse-
Name consists of a namespace index and a name. In the XML definition,
these are separated by a colon. The BrowseNames are compiled into a
node address in XML separated by a period. The node addresses for the
standard data types are specified by the OPC UA standard and can be read
out from the address space using a client.
The node address for a Boolean variable is defined as follows, for example:
0:Types.0:DataTypes.0:BaseDataType.0:Boolean. In the table below,
the node addresses are displayed in abbreviated form. However, for each
node address, in the XML file the following character string must be ap-
pended at the front: 0:Types.0:DataTypes.0:BaseDataType.
OPC UA
data type
IEC data type Node address
Boolean BOOL
0:Boolean
SByte SINT
0:Number.0:Integer.0: SByte
Byte BYTE, USINT
0:Number.0:UInteger.0:Byte
Int16 INT
0:Number.0:Integer.0:Int16
UInt16 WORD, UINT
0:Number.0:UInteger.0:UInt16
Int32 DINT
0:Number.0:Integer.0:Int32
UInt32 DWORD, UDINT
0:Number.0:UInteger.0:UInt32
Int64 LINT
0:Number.0:Integer.0:Int64
UInt64 LWORD, ULINT
0:Number.0:UInteger.0:UInt64
Float REAL
0:Number.0:Float
Double LREAL
0:Number.0: Double
String STRING, WSTRING
0:String
DateTime
DATE_AND_TIME,
DATE,
TIME_OF_DAY
0:DateTime
Information
The mapped data types between OPC UA and IEC must match, otherwise
a node is not generated.