Free engineering calculators and unit convertersceo@instrumentationblog.in
Troubleshooting Guides · Free Tool

Modbus Communication Fault Finder

Choose the Modbus symptom and get likely causes in settings, RS485 wiring, register mapping and network configuration.

No responseCRC errorsWrong valuesTimeouts
SymptomNo response
Most likely causeAddress, baud or parity mismatch
First checkCompare settings

Causes in order of likelihood

CauseHow to checkFix
Address, baud or parity mismatchCompare settingsMatch settings
A and B wires swappedSwap and retestCorrect polarity
Device not powered or wrong portCheck power and portCorrect
Advertisement

Before You Start

  • Note the exact error: timeout, CRC, exception code.
  • Confirm slave address, baud rate, parity and stop bits on both sides.
  • Test with one device and a laptop master if possible.

Modbus Communication Fault Finder: All Symptoms

No response

Likely causeHow to checkFix
Address, baud or parity mismatchCompare settingsMatch settings
A and B wires swappedSwap and retestCorrect polarity
Device not powered or wrong portCheck power and portCorrect

CRC or framing errors

Likely causeHow to checkFix
Missing or extra terminationCheck 120 Ω at both ends onlyCorrect termination
Star wiring or long stubsCheck topologyDaisy chain
Noise from power cablesCheck routing and shieldSegregate; earth shield at one point

Wrong values

Likely causeHow to checkFix
Register offset of oneTry address −1 or +1Correct the map
Word order of 32 bit valuesSwap registersSet word order
Scaling or data typeCheck device mapApply correct type and scale

Exception code returned

Likely causeHow to checkFix
01 illegal functionCheck supported function codesUse correct code
02 illegal data addressCheck register rangeCorrect address
03 illegal data valueCheck value or quantity limitsCorrect request

Modbus TCP cannot connect

Likely causeHow to checkFix
IP or subnet wrongPing the deviceCorrect IP settings
Port 502 blockedCheck firewallOpen port
Wrong unit ID through gatewayCheck gateway mappingSet unit ID
Key insight: if you get an exception code the wiring works: the problem is the request. If you get nothing, look at settings and wiring.
Advertisement

Frequently Asked Questions

Why is 40001 address 0?

Documentation uses 1 based numbers; the protocol is 0 based.

How do I fix CRC errors?

Check termination, topology, grounding and baud settings.

What does exception 02 mean?

The requested register does not exist in the device.

You May Also Like

Learn more on the blog

Modbus RTU troubleshooting: CRC, no response and fault table

A practical, field focused guide on instrumentationblog.in that explains the theory behind this tool and how engineers apply it on real plants.

Read Full Article

More Troubleshooting Guides

More Instrumentation Tools