RS485 Bus Not Responding: Systematic Diagnosis and Serial Communication Fault Correction

The RS485 bus is robust in theory — differential, noise-tolerant, capable of reaching up to 1.2 km — but in practice, wiring, termination and configuration errors are the most common cause of serial communication failures in the field. This guide covers the four most common problems: how to diagnose them with a basic multimeter and how to resolve them without replacing equipment.

Required tools

• Digital multimeter with DC and AC mode (minimum range 20 V DC)
• Index AMI configuration software or app (to read logs, verify UART parameters and adjust serial communication settings).
• Optional oscilloscope (useful for diagnosing noise in industrial installations)
• 120 Ω resistor (for termination testing)

RS485 concepts you need to understand

RS485 is a differential physical-layer standard: the signal is transmitted as the voltage difference between two lines, A (positive) and B (negative). The receiver interprets:

• V(A) − V(B) > +200 mV → logical bit 1
• V(A) − V(B) < −200 mV → logical bit 0
• |V(A) − V(B)| < 200 mV → undefined state (floating bus)

An idle bus (at rest) should have A around +2.5 V and B around +0.5 V, giving a difference of ~2 V. If you measure values outside this range, there is a wiring, termination or transceiver power issue.

Problem 1 — No response from meter (timeout)

Symptom: the app shows "No response" or the Index AMI log records DLMS timeout after 3 retries.

Diagnosis:

1. Measure with the multimeter between A+ and GND — should be between +2 V and +5 V at rest.
2. Measure between B− and GND — should be between 0 V and +1 V at rest.
3. If both lines read 0 V or the same voltage, the bus is floating: bias (pull-up/pull-down resistors) is missing or there is a cable break.

Solution:

• Verify that the meter has its RS485 port enabled (some meters ship with the port disabled from the factory — consult the ISKRA manual or the utility portal).
• Check cable continuity: measure resistance between the A+ terminal of the meter and the A+ terminal of the Index AMI. Should be <5 Ω for cable up to 100 m.
• If the bus is floating and the wiring is correct, add external bias resistors: 10 kΩ between A+ and +5 V, and 10 kΩ between B− and GND. Some RS485 gateways include internal bias activatable via software; check your device's configuration interface at Settings → RS485 → Bus polarization.

Problem 2 — Inverted polarity

Symptom: the Index AMI receives responses but with framing errors or the log shows framing error on every frame.

Diagnosis:

1. At rest (no active transmission), measure V(A+) − V(B−). If the result is negative (e.g. −2 V), the lines are swapped.
2. Confirm with the meter's terminal diagram: on the ISKRA MT171, D+ is the left pin of the RS485 block when facing the meter from the front.

Solution:

• Physically swap the A+ and B− wires at one end (meter or Index AMI).
• Some RS485 gateways allow inverting polarity via software from their configuration interface: Settings → RS485 → Invert A/B polarity.

Problem 3 — CRC error or corrupted frame

Symptom: the Index AMI receives responses but with frequent CRC mismatch o HDLC frame error (>5% of frames).

Diagnosis:

1. Incorrect baud rate: the meter may have been reprogrammed by the utility. Try 2400, 4800, 9600 and 19200 bps systematically.
2. Electrical noise: if there are variable frequency drives, contactors or high-power lighting near the RS485 cable, noise injects erroneous bits. Measure with the multimeter in AC mode between A+ and GND — more than 200 mVAC indicates significant noise.
3. Floating ground: if the harness GND is not connected or the meter has a different ground reference than the Index AMI, the bus common mode rises and degrades the differential signal.

Solution by cause:

• Incorrect baud rate → use the app's automatic scanner: Tools → Scan RS485 baud rates — tests standard speeds in order and reports the first one that gets a valid response.
• Noise → use shielded cable (STP) for RS485 and connect the shield to ground at one end only (preferably at the Index AMI). The differential pair twist cancels common-mode noise.
• Floating ground → connect the harness GND wire to the meter's ground terminal and verify that the Index AMI is referenced to the same ground as the electrical panel.

Problem 4 — Intermittent timeout on long bus

Symptom: communication works fine in bench tests (short cable) but fails or is unstable with the final installation cable (>50 m).

Diagnosis:

On long cables, the parasitic capacitance of the cable acts as a low-pass filter that rounds signal transitions. Combined with reflections if the bus is not terminated, the receiver sees ambiguous signals on the edges.

Rule of thumb: cables >30 m at 9600 bps require termination. At 19200 bps, the threshold drops to ~15 m.

Solution:

• Connect a 120 Ω resistor between A+ and B− at the farthest end of the bus (usually at the meter). This eliminates reflections by matching the cable impedance (typically 100–120 Ω).
• Do not terminate both ends unless the bus has more than one node between the ends — two 120 Ω terminations in parallel = 60 Ω, which overloads the transceiver.
• Consider reducing the baud rate to 4800 bps in installations with poor-quality cable or lengths exceeding 200 m. The impact on latency is minimal for telemetry with 15-minute intervals.

Quick reference table

Next steps

With stable RS485 communication, the serial bus is ready to transmit data to the management platform. If you need encrypted remote access to the Index AMI for diagnosis or reconfiguration without a site visit, see the guide for WireGuard point-to-point setup to bring up the remote management VPN.