Common problems with Modbus RTU and how to solve them
Modbus RTU is simple, but small mistakes can stop it from working. Most problems fall into a few common groups.
1. No response from the device
What it looks like:
The master sends requests, but nothing comes back.
Common causes:
- wrong slave ID
- wrong baud rate, parity, or stop bits
- A and B swapped
- device not powered
- wrong port
- broken wiring
How to fix it:
Check power first. Then check wiring. Then verify all serial settings on both sides. Finally, confirm the slave ID.
2. Exception response from the device
What it looks like:
The device replies, but with an error.
Common causes:
- wrong register address
- wrong function code
- trying to write to a read-only register
- unsupported register count
How to fix it:
Read the manual carefully. Make sure the register exists and that the device supports the request you are sending.
3. Values look wrong
What it looks like:
Communication works, but the values are too high, too low, negative, or otherwise impossible.
Common causes:
- wrong scaling
- signed or unsigned confusion
- wrong byte order
- wrong word order
- wrong register address
How to fix it:
Check how the value is stored. See whether it is a 16-bit integer, 32-bit integer, or float. Then check scaling and value format.
4. Works in one tool but not another
What it looks like:
A Modbus test tool works, but the PLC, BMS, or SCADA system does not.
Common causes:
- address offset confusion
- different input style in the client tool
- different byte order settings
- different timeout settings
How to fix it:
Compare the exact request sent by both tools. Many times the difference is not the device, but how the client software handles addressing or data format.
5. Works sometimes, fails sometimes
What it looks like:
Communication is unstable.
Common causes:
- noise on the RS-485 line
- poor grounding
- missing termination
- long stub lines
- duplicate slave IDs
- weak cable connections
How to fix it:
Check the wiring and bus layout. Make sure the line is wired as a bus, not a star. Check termination only where needed. Check cable quality and grounding.
6. Wrong register type
What it looks like:
The value does not read correctly, or the device returns an error.
Common causes:
- trying to read holding registers when the value is in input registers
- trying to write to a read-only area
How to fix it:
Make sure the correct register type is used. The device manual should clearly state this.
Final note
Modbus RTU problems are usually not mysterious. Start with wiring and settings. Then check the exact request. Then check how the data is interpreted. That order solves most issues quickly.
Consulting
Manufacturers can hire me for help with Modbus device documentation, testing, and troubleshooting.