|
The next table lists Driver's native data types, which can be defined when configuring I/O Tags.
As explained on topics String Configuration and Operations Tab, the Modbus protocol itself only supports Bit and Word data types (16 bits) for the most commonly used functions implemented by this Driver (the only exception is currently function 7). All other Driver's data types are converted to Word at protocol's level, for reading from or writing to a device or slave device.
Also notice that this Driver supports User-Defined Data Types, defined as structures with elements composed by the native data types listed on the next table.
On the next table, data types use the same denominations of mnemonics for the data type field, when Tags are configured by Strings. For the old numerical configuration, the same denominations are also used on Data column of Driver's configuration window (on Operations Tab). In some cases, frequent alternative denominations are displayed between parentheses.
Available options for data types
Type
|
Range
|
Description
|
Char
|
-128 to 127
|
Eight-bit word, character. Writing must always occur in blocks with even size (Words)
|
Byte
|
0 to 255
|
Unsigned eight-bit word. Writing must always occur in blocks with even size (Words)
|
Int8
|
-128 to 127
|
Signed eight-bit word. Writing must always occur in blocks with even size (Words)
|
Int16
|
-32768 to 32767
|
Signed 16-bit integer
|
Int32
|
-2147483648 to 2147483647
|
Signed 32-bit integer
|
Word (or UInt)
|
0 to 65535
|
Unsigned 16-bit integer
|
DWord (or ULong)
|
0 to 4294967295
|
Unsigned 32-bit integer (Double Word)
|
Float
|
-3.4E38 to 3.4E38
|
32-bit floating point (IEEE 754) (four bytes: EXP F2 F1 0)
|
Float_GE
|
-1.427E+45 to 1.427E+45
|
32-bit floating point used by GE, not compatible with IEEE 754. It is used in GE GEDE UPS devices, with an eight-bit exponent 2[-128 ... +127] and 24-bit mantissa [-223 ...+(223-1)]. (four bytes: EXP F2 F1 F0). For more information, please check device's documentation
|
Double (or Real)
|
-1.7E308 to 1.7E308
|
64-bit floating point (IEEE 754)
|
String
|
Does not apply
|
Text in ANSI format, with a determined number of eight bit ASCII characters (Chars)
|
BCD
|
Check description
|
BCD (Binary-Coded Decimal) numerical value. When using this data type, an application must provide a positive and integer decimal value, sent in BCD format, respecting the specified size. The Size field, for BCD types, refers to the number of bytes sent to represent a value. As in BCD encoding each figure is converted to a nibble, then the allowed values must have a maximum number of figures equal to double the size of the value specified in the Size field, that is, if a value of two is selected for the Size field, the maximum value that can be sent is 9999. Likewise, if Size is equal to four, the maximum value is then 99999999. Allowed values for the Size field for BCD types are two (Word) and four (Double Word). For more information about the BCD encoding, please check topic BCD Encoding
|
GE_events
|
Check description
|
Data type used when reading an event buffer (SOE) from a GE PAC RX7 PLC. Its definition is only allowed for operations that use the special reading function GE SOE. These events are returned as blocks with two Elements, with timestamps defined by the controller. For more information, please check topic Reading an Event Buffer in GE PAC RX7 Controllers
|
Bit
|
0 (zero) or 1 (one)
|
This data type is automatically selected when a bit-access function is selected. Bit-access functions are 01, 02, 05, and 15. The Size field is not used for Bit types. When using this data type, each Tag or Block Tag Element represents a bit
|
SP_events
|
Check description
|
Data type used when reading events (SOE) in Schneider Electric relays from SEPAM 20, 40, and 80 series. Its definition is only allowed for operations that use the special reading function SP SOE. These events are returned as a three-Element Block, with a device-provided timestamp. For more information, please check topic Reading Events in Schneider Electric Relays from SEPAM 20, 40, and 80 Series
|
GenTime
|
1/1/1970 00:00 to 31/12/2035 23:59:59.999 (please check the next note)
|
Date and time type composed by an eight-bit structure, originally created for use when reading events using generic SOE algorithm (GenSOE). This data type can be used with other Modbus protocol functions, in addition to GenSOE. This format is read internally as a structure of Words, and the only valid swap function for this type is Swap Bytes. Representation of this type in PLC memory is described on topic GenTime Data Type. For more information about this type, please check topic Elipse Software's Generic SOE Reading Algorithm
|
Sp_time
|
1/1/1970 00:00 to 31/12/2035 23:59:59.999 (please check the next note)
|
Date and time data type composed by an eight-byte structure, used by Schneider Electric relays from SEPAM 20, 40, and 80 series, usually to represent a timestamp. For more information, please check device's documentation
|
UTC64d
|
1/1/1970 00:00 to 31/12/2035 23:59:59.999 (please check the next note)
|
Date and time data type represented in Double format (64-bit IEEE 754), with seconds since 1/1/1970 00:00
|
UTC32
|
1/1/1970 00:00 to 31/12/2035 23:59:59.999 (please check the next note)
|
Date and time data type represented as an unsigned 32-bit integer (DWord or UInt), with seconds since 1/1/1970 00:00. This format does not represent milliseconds, which are always considered as 0 (zero)
|
Int16_sm
|
-32767 to 32767
|
Signed 16-bit integer (magnitude signal)
|
Int32_sm
|
-2147483647 to 2147483647
|
Signed 32-bit integer (magnitude signal)
|
NOTE
|
Although the representation of date and time data types on the previous table can represent dates greater than 12/31/2035, this limit is displayed on the table because Elipse Software applications do not currently support ranges of values that exceed this limit for timestamps.
|
|