The mapping of IEC 61131-3 generic data types to OPC UA data types is formally defined in Table 28. Since the generic data type should not be used in user-declared Ctrl Program Organization Units, this mapping definition is defined for completeness but is normally not used in an OPC UA AddressSpace.
Table 28 – Mapping IEC 61131-3 generic data types to OPC UA data types
|
IEC 61131-3 generic data types |
OPC UA data types |
Description |
|
ANY |
BaseDataType |
This abstract OPC UA DataType defines a value that can have any valid OPC UA DataType. |
|
ANY_DERIVED |
BaseDataType |
|
|
ANY_ELEMENTARY |
BaseDataType |
|
|
ANY_MAGNITUDE |
BaseDataType |
|
|
ANY_NUM |
Number |
This abstract OPC UA DataType defines a number value that can have any of the OPC UA Number subtypes. |
|
ANY_REAL |
Number |
|
|
ANY_INT |
Number |
|
|
ANY_BIT |
Number |
|
|
ANY_STRING |
String |
This OPC UA Built-in DataType defines a Unicode character string that should exclude control characters that are not whitespaces (0x00 - 0x08, 0x0E-0x1F or 0x7F). |
|
ANY_DATE |
DateTime |
This OPC UA Built-in DataType defines a Gregorian calendar date. It is a 64-bit signed integer which represents the number of 100 nanosecond intervals since January 1, 1601. |