top of page

Modbus TCP Connects but No Meter Replies? Verify Unit ID Routing

4 days ago
4 min read

A monitoring client opens a TCP connection to a gateway, yet the intended meter stays silent or the returned values belong to another device. Reaching the IP address proves only part of the path. Before increasing timeouts, establish how the request identifies the instrument behind that address.


For a Modbus TCP-to-serial bridge, verify the Unit Identifier together with the gateway’s routing configuration and downstream device address. For a gateway that collects measurements and exposes its own register map, follow that upstream map instead. These architectures need different commissioning records.


Separate the network endpoint from the instrument


The Modbus Organisation’s TCP/IP Implementation Guide describes the Unit Identifier as a routing field. Where a gateway serves a serial sub-network, the destination IP identifies the gateway and the Unit Identifier identifies the remote device. A direct TCP server is a different case; its IP identifies the server itself.


The guide recommends the non-significant value 0xFF for a direct TCP server. That recommendation should not be copied blindly into a project that now reaches serial instruments through a bridge. Confirm the actual product’s documented implementation and gateway mode before changing a working driver.



Confirm which gateway architecture you have


Draw the path from client to measurement: client connection, gateway interface, selected serial channel and physical instrument. Ask whether requests are routed to field devices, or whether the gateway independently collects data into an upstream point map. Record any address translation. Ethernet and RS485 connectors alone do not answer those questions.


The ProSense catalogue’s ACREL 2 Ethernet 4 or 8 RS485 Communication Gateway is an example of equipment used between field instruments and a monitoring system. Its listing describes protocol conversion, forwarding and configurable channels. Select the exact variant and obtain its applicable configuration documentation; do not infer the selected operating mode from a photograph or family name.


ACREL communication gateway product photograph showing its metal enclosure and communication connectors
ACREL Ethernet/RS485 communication gateway - ProSense Instruments catalogue product photograph, not a commissioned installation.


Acrel’s ANet family documentation includes configurable data collection and forwarding functions. The linked manufacturer overview discusses ANet-1E2S1; it is family context, not a substitute for the pictured product’s exact model manual or evidence that all ANet variants share routing settings.



Build a route record before testing


For each intended measurement, write down the asset label, exact model, firmware revision, gateway IP and port, client Unit ID, downstream serial channel and device address, then the function and register range. Keep register location separate from device destination. A column labelled only Address is too ambiguous for a handover.


Add the gateway mode, any translation table and the source of each setting. For a collector, include the upstream point-map revision and how that point is linked to its field device. Retain an export or screenshot of the original configuration before proposing changes.


Use one documented, read-only measurement during an authorised test window. Capture the request and response, including Unit ID, and compare the result with an independent observation of the intended asset. A plausible number is weaker evidence than a reading positively associated with the correct meter.


Hypothetical example: one IP, two instruments


Assume a simple bridge is documented to route Unit IDs directly to serial addresses. Two identical meters use addresses 7 and 8 on the same channel. A copied client connection uses the correct gateway IP but retains a Unit ID intended for the previous installation. This is a hypothetical diagnostic example, not an Acrel default configuration.


Prepare separate approved read tests for the documented destinations. Keep the function, register and scaling unchanged while checking the route. Record which instrument supplies each result. If the project instead uses a collector’s consolidated register map, abandon the direct-address assumption and reconcile its point mapping before proceeding.


Do not identify a device by deliberately changing a live process or issuing writes to unknown destinations. Where a safe identifying value is unavailable, agree another verification method with the responsible engineer. Leave an uncertain route unaccepted.


Common mistakes and practical acceptance


Avoid treating a successful connection as proof of a complete field transaction, assigning every point the same default Unit ID, or changing register offsets to disguise a destination problem. Do not perform an unrestricted device scan on an operating system. A timeout should be recorded as an observation while its cause remains under investigation.


Acceptance should show the intended asset, verified route, fresh reading and expected behaviour for an unavailable device. Retain the configuration revision and test evidence so a future gateway replacement does not silently change where requests go.


For assistance, provide the topology, gateway mode, exact models, point map and a concise read-only transaction record. Keep credentials and unrelated site traffic out of enquiry attachments. Electrical installation and application-specific validation belong with competent people; this monitoring procedure does not establish a certified safety function.


Need help with your application?


ProSense Instruments - discuss instruments and communications hardware: sales@prosenseinstruments.com.au or 1800 560 854.


ProSense Solutions - discuss system integration: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.


Comments


bottom of page