Modbus Gateway Replies but the Device Does Not? Check Unit Identifier
- PLC Play Ground
- 0
- Posted on
Reaching a Modbus TCP gateway is not the same as selecting the correct device behind it. Check the Unit Identifier and gateway route when the TCP session works but one downstream instrument remains unavailable.
Routing behavior depends on the gateway and direct-device implementation.
What is happening?
The Unit Identifier can participate in routing through gateways to other Modbus devices. Direct TCP products may interpret it differently. The gateway and downstream device documentation define the accepted mapping.
Check these five things
-
Record gateway address, port, and requested Unit Identifier.
-
Compare the gateway routing configuration with the serial device address.
-
Check downstream communication diagnostics.
-
Test a documented read from the intended device.
-
Keep route and register map together in the interface record.
Worked example
A teaching gateway serves serial nodes 3 and 7. The client reaches the gateway but sends the identifier intended for node 3 while expecting data from node 7. A healthy TCP connection cannot correct that application routing mismatch.
Quick diagnostic reference
| Layer | Identity |
|---|---|
| TCP endpoint | Gateway |
| Unit Identifier | Downstream route as configured |
| Register request | Object within device |
The mistake to avoid
Trying arbitrary identifiers on production equipment can address another real device. Use the documented route rather than guessing until a reply appears.
How to verify the fix
Verify the returned identity or known read-only value against the intended instrument. Confirm errors distinguish gateway reachability from downstream failure.
Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.
Technical reference
Modbus Organization: TCP messaging and Unit Identifier. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.
