On the bench, both ends of an RS485 link share one power supply and one ground. On site they do not. A controller in a panel and a sensor or meter next to a pump can sit at ground potentials several volts apart, and the difference moves when a motor starts or a welder runs nearby.
A standard RS485 transceiver only tolerates a limited common-mode range, typically from about −7 V to +12 V relative to its own ground. Push past that and you get corrupted frames at best. At worst the transceiver is slowly damaged by repeated transients. We have seen links that pass every bench test, run for a week or two on site, then stop answering, and the transceiver turns out to be dead.
What we check on the schematic
Isolation. If the two ends can be at different grounds, the transceiver should be isolated: an isolated RS485 part, or a standard transceiver behind a digital isolator, powered through an isolated DC-DC converter. This removes the common-mode problem instead of hoping it stays small.
A reference conductor. RS485 is often described as “two wires”. In practice the link needs a third, a signal reference between the nodes, run through a resistor or on the isolated side. Without it the common-mode voltage is whatever the site decides.
Surge protection. TVS diodes on A and B, rated for the line, and a sensible place for the surge current to go. Long cable runs outdoors or near motors pick up a lot.
Termination and bias. 120 Ω at the two physical ends of the bus, not on every node. Bias resistors so the line sits in a known state when nobody is talking; without them, noise on an idle line can look like a start bit.
Cable and routing. Twisted pair, kept away from mains and motor cables. A shield, if used, grounded at one point.
What isolation does not fix
Isolation will not save a bus with three terminators, a star topology, or nodes with duplicate addresses. It also does not help if the firmware has no timeout and waits forever for a reply that never comes. On the firmware side we want a response timeout, a retry count and a log entry for every failed poll, so a field problem shows up as a pattern before it becomes an outage.
A quick test before you deploy
Power the two ends from separate supplies, then shift one ground by a few volts with a bench supply and watch the error count. If it climbs, the site will find the problem for you.
If an RS485 or Modbus link in your product keeps dropping out, book a discovery call and tell us about the installation.
