A successful Ethernet connection confirms only that some network communication is working. It does not prove that the serial slave is wired correctly or responding to Modbus requests.
Use the following troubleshooting sequence:
For the usual Ethernet-master-to-serial-slave arrangement, check that the gateway is in Server mode and that Port1 is configured for the serial device’s protocol.
Confirm that baud rate, data size, parity, and stop bits match the slave.
Verify differential polarity, signal reference, termination where necessary, and correct wiring for the chosen interface.
The request must target the correct serial slave address. Check for duplicate addresses on the bus.
Verify the function code, register address, quantity, and data format against the slave’s documentation.
Where practical, test with one known-good slave and a single known-valid read request before reintroducing other devices.
A slow slave or a timeout that is too short can prevent a response from being received successfully.
Troubleshooting Tip: Use any available serial protocol analyzer or diagnostic tool to establish whether a request reaches the serial bus and whether a response returns. This helps distinguish a network configuration problem from a serial communication problem.