Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Adapter for Modbus TCP

Register types

  • Last UpdatedAug 27, 2026
  • 3 minute read

The following tables list the DataTypeCodes supported in the adapter.

DataTypeCode 1

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

BoolModbus

Bool

Coil/Discrete

0=Modbus0 / 1=Modbus1

bool

NA

DataTypeCode 10

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Int16

Int16

Any

Read 1 Modbus register1 and interpret as a 16-bit integer. Bytes [BA] read from the PLC are stored as [AB]. 2

Int16

1

DataTypeCode 20

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

UInt16

UInt16

Any

Read 1 Modbus register1 and interpret as an unsigned 16-bit integer. Bytes [BA] read from the PLC are stored as [AB]. 2

Int32

11

DataTypeCode 30

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Int32

Int32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit integer. Bytes [DCBA] read from the PLC are stored as [ABCD]. 2

Int32

7

DataTypeCode 31

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Int32ByteSwap

Int32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit integer. Bytes [BADC] read from the PLC are stored as [ABCD]. 2

Int32

7

DataTypeCode 40

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

UInt32

Int32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit unsigned integer. Bytes [DCBA] read from the PLC are stored as [ABCD]. 2

UInt32

N/A

DataTypeCode 41

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

UInt32ByteSwap

Int32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit unsigned integer. Bytes [BADC] read from the PLC are stored as [ABCD]. 2

UInt32

N/A

DataTypeCode 100

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Float32

Float32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit float. Bytes [DCBA] read from the PLC are stored as [ABCD]. 2

Float32

6

DataTypeCode 101

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Float32ByteSwap

Float32

Holding16/Input16

Read 32-bits from the PLC and interpret as a 32-bit float. Bytes [BADC] read from the PLC are stored as [ABCD]. 2

Float32

6

DataTypeCode 110

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Float64

Float64

Holding16/Input16

Read 64-bits from the PLC and interpret as a 64-bit float. Bytes [HGFEDCBA] read from the device are stored as [ABCDEFGH]. 2

Float64

6

DataTypeCode 111

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

Float64ByteSwap

Float64

Holding16/Input16

Read 64-bits from the PLC and interpret as a 64-bit float. Bytes [BADCFEHG] read from the device are stored as [ABCDEFGH]. 2

Float64

6

DataTypeCode 1001-1250

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

String

String

Holding16/Input16

1001 will a 1-character string, 1002 will read a 2-character string, 1003 will read a 3-character string and so on. Bytes [AB] are interpreted as "AB".

String

101 to 199

DataTypeCode 2001-2250

Name

Value Type

Register Type

Meaning

Output Type

Interface data type code

StringByteSwap

String

Holding16/Input16

2001 will a 1-character string, 2002 will read a 2-character string, 2003 will read a 3-character string and so on. Bytes [BA] are interpreted as "AB".

String

101 to 199

1 For more information about Modbus TCP registers, see How is data stored in Standard Modbus? (https://www.se.com/us/en/faqs/FA168406/)

2 Bytes are read in reverse order.