Property filled when Elipse E3 connects to an OPC UA Server, which indicates the data type on an OPC UA Server. This property is initially filled in the browsing process, if performed, and at each communication or connection with an OPC UA Server. Values below 1,000 are scalars and values above 1,000 are arrays. This is a read-only property. Possible values for this property are described on the next table.
Possible values for the DataType property
Value |
Description |
|---|---|
-1 |
udtUnknown (Unknown value, disconnected item, or data type unsupported by Elipse E3) |
0 |
udtNull |
1 |
udtBoolean |
2 |
udtSByte |
3 |
udtByte |
4 |
udtInt16 |
5 |
udtUInt16 |
6 |
udtInt32 |
7 |
udtUInt32 |
8 |
udtInt64 (please check the next note) |
9 |
udtUInt64 (please check the next note) |
10 |
udtFloat |
11 |
udtDouble |
12 |
udtString |
13 |
udtDateTime |
14 |
udtGuid (Unique global identifier with 128 bits, formatted as text in Elipse E3) |
15 |
udtByteString (Array of bytes or a binary String) |
16 |
udtXmlElement (XML element, formatted as text in Elipse E3) |
17 |
udtNodeId (OPC UA Node Identifier, formatted as a three-element array in Elipse E3) |
18 |
udtExpandedNodeId (Expanded OPC UA Node Identifier, formatted as a three-element array in Elipse E3) |
19 |
udtStatusCode (Equivalent to quality, indicates errors) |
20 |
udtQualifiedName (Text with the Namespace, which in Elipse E3 is discarded) |
21 |
udtLocalizedText (Text with the locale, which in Elipse E3 is discarded) |
22 |
udtStructure (Indicates this is an OPC UA complex data type, but not specific, formatted as an array where each element is a member of the structure) |
23 |
udtDataValue (Value with quality and timestamp, which in Elipse E3 are discarded) |
24 |
udtVariant (Value with a variable or undefined data type) |
25 |
udtDiagnosticInfo |
1000 |
udtArrayUnknown (Generic array, with unknown data types) |
1001 |
udtArrayBoolean |
1002 |
udtArraySByte |
1003 |
udtArrayByte |
1004 |
udtArrayInt16 |
1005 |
udtArrayUInt16 |
1006 |
udtArrayInt32 |
1007 |
udtArrayUInt32 |
1008 |
udtArrayInt64 |
1009 |
udtArrayUInt64 |
1010 |
udtArrayFloat |
1011 |
udtArrayDouble |
1012 |
udtArrayString |
1013 |
udtArrayDateTime |
1014 |
udtArrayGuid |
1015 |
udtArrayByteString |
1016 |
udtArrayXmlElement |
1017 |
udtArrayNodeId |
1018 |
udtArrayExpandedNodeId |
1019 |
udtArrayStatusCode |
1020 |
udtArrayQualifiedName |
1021 |
udtArrayLocalizedText |
1022 |
udtArrayStructure |
1023 |
udtArrayDataValue |
1024 |
udtArrayVariant |
•Although the OPC UA standard allows 64-bit values, currently in Elipse E3 the Bit00 to Bit31 properties only allow controlling the first 32 least significant bits. •Structures defined by specific OPC UA Servers, not compatible with the OPC UA standard, are not read by Elipse E3. •Complex data types with values below 1,000 must be used in OPC UA Block Tags. •Data types udtQualifiedName, udtArrayQualifiedName, udtLocalizedText, udtArrayLocalizedText, udtStructure, udtArrayStructure, udtDataValue, udtArrayDataValue, udtUnknown, and udtArrayUnknown do not allow writings in the current version of Elipse E3, because Elipse E3 uses a simplified formatting of these data types. •Data types ServiceCounterDataType (array with two positions), BuildIndfo (array with six positions), Argument (array with six positions), ApplicationDescription (array with eight positions), SessionDiagnosticsDataType (array with 44 positions), SessionSecurityDiagnosticsDataType (array with 10 positions), SubscriptionsDiagnosticsDataType (array with 31 positions), ServerDiagnosticsSummaryDataType (array with 12 positions), ServerStatusDataType (array with six positions), EuInformation (array with four positions), Range (array with two positions), TimeZoneDataType (array with two positions), DiagnosticInfo (array with seven positions), StatusResult (array with two positions), ComplexNumberType (array with two positions), DoubleComplexNumberType (array with two positions), XVType (array with two positions), RedundanteServerSataType (array with three positions), SamplingIntervalDiagnosticsDataType (array with four positions), EnumValueType (array with three positions), EndpointUrlListDataType (array with two positions), and NetworkGroupDataType (array with three positions) are displayed as udtStructure, but Elipse E3 handles the specific data type. •In the current version, Elipse E3 only allows single-dimension arrays, that is, it does not allow matrices as data types. |