What can I do to troubleshoot Modbus communication failure?
What can I do to troubleshoot Modbus communication failure?
Modbus communication failure impacts PLC and SCADA networks. Physical layer up. Then change the software. Then change the network reliability overall.
1. Check wiring and power
Make that the slave is powered, port enabled, and connectors are snug. Terminal labels may vary. Check A and B polarity for Modbus RTU over RS485 in the device handbook. Use shielded twisted pair, not star wiring, inspect for cable damage, moisture and loose terminals. Do not run communications cables with variable frequency drive output cables.
2. Verify settings
The master and slave must have the same baud rate, parity, data bits and stop bits. Verify the slave address is valid. Make sure the addresses are unique. For Modbus TCP check IP address, subnet, TCP port and network path.
3. Inspect the bus
Check termination at the two physical ends of the RS485 trunk, usually 120 ohms if required for the cable. Check biasing and reference grounding.Remove excess terminators Check the timeout, response latency and polling periods.
4. Match symptoms to causes
- No response: check power, address, polarity, settings and network path.
- CRC errors: Check noise, grounding, cable quality and termination.
- Incorrect values: check register address, function code, data type, word order and scaling.
- Intermittent drops: Test devices one at a time and check traffic with a Modbus tester or serial analyzer.
Field tip
If failure began after adding an instrument, disconnect that node and test the remaining network. Change one variable at a time, then document settings and test every device under normal plant conditions.