ModbusTCP - Modbus Transaction Identifier

Modbus Transaction Identifier

When sending a Modbus TCP frame, the frame is split into 6 different sections:

1)      Transaction Identifier ( 2 bytes )

2)      Protocol Identifier (2 bytes)

3)      Length Field (2 bytes)

4)      Unit Identifier (1 byte)

5)      Function Code (1 byte)

6)      Data bytes (n bytes)

The very important bytes for this frame are the Unit Identifier, Function Code and Data bytes and some scanners will only use these bytes when polling for and displaying information via a Modbus TCP protocol.

However other scanners will use the transaction identifier as a means of validating response messages.

The actual use for the transaction identifier is for synchronization between messages of server and client.  So if a scanner checks the transaction identifier from the query it sent against the transaction identifier from the response it receives and the values do not match, it identifies the response message as an invalid Modbus message and will timeout.

Contact Us

Contact us via phone (+1 866-383-1657) or leave a detailed message below for sales, support, or any other needs

*Required Field
*Required Field
I'd like to receive the newsletter. *Check email for confirmation.
*Required Field
8:00am - 12:00pm 12:00pm - 5:00pm