RS485 wiring for Modbus: a complete installer guide (2026)

RS485 wiring is the physical layer Modbus RTU runs on, and in the field it's where most "Modbus isn't working" tickets come from. Wrong cable, missing termination, A and B swapped, shield grounded at both ends, or 230 V running parallel to the signal pair: each of those mistakes takes minutes to make and hours to track down.

This guide consolidates the spec, the choices, and the installer field traps. Written for people pulling cable and tightening terminals, not for protocol designers. By the end you'll know which cable to grab in which enclosure, where the 120 Ω termination resistors belong, how to untangle the A/B polarity confusion, and when a Modbus gateway gets you further than another stretch of copper.

Key takeaways

• RS485 needs a twisted-pair cable with 120 Ω characteristic impedance and a shield; plain Cat6 (100 Ω) works at short range but is not a spec choice.
• Maximum bus length is roughly 1200 m at 19,200 baud (the Modbus RTU default) and drops sharply above 100 kbps; at 1 Mbps you're down to about 120 m.
• Place 120 Ω termination resistors at both physical ends of the bus, never in an intermediate device, and bond the shield to earth at one end only.

What RS485 is and why Modbus uses it

RS485 is a differential transmission layer, standardized as TIA/EIA-485-A in 1983 and revised in 2003. Instead of one wire against ground (RS232), RS485 uses two wires carrying mirror images of each other. A receiver reads the difference between A and B, so common-mode noise averages out. That's why RS485 runs over 1200 m in EMI-noisy environments where RS232 fails inside 10 m.

Modbus RTU has run over RS485 since 1979 because the combination meets three things installers care about: long distance, multidrop bus for 32+ devices, and ordinary terminal-block wiring. The Modbus over Serial Line Specification V1.02 from the Modbus Organization (December 2006) describes this layer for Modbus and remains the reference vendors point to. For the Modbus RTU layer above the wiring, see our Modbus RTU explained guide.

Choosing the right RS485 cable

A spec RS485 cable meets three conditions: twisted pair, 120 Ω characteristic impedance, and a shield against capacitive coupling. Three families dominate the global installer toolkit.

Belden 9841 (one pair) and 9842 (two pair) are the international reference. AWG 24 conductors, foil plus braid shield, 120 Ω impedance. Belden 3105A is a Modbus-specific variant with AWG 22 conductors for slightly better noise margin on long runs. Lapp UNITRONIC BUS LD is the European equivalent. Alpha Wire 6020C and L-com / Pro Power cover the same spec niche.

Can Cat5e or Cat6 work? At short range inside a single enclosure, often yes; the pair is twisted and FTP variants have a shield. But the impedance is 100 Ω, not 120 Ω, so reflections grow as you push the baud rate or the run length. At 9600 baud over 50 m Cat6 will run cleanly; at 19,200 baud over 800 m you'll see CRC errors creep in.

Maximum cable length vs. data rate

The RS485 length rule of thumb comes from TIA-485-A and is summarized in the TI RS-485 Design Guide SLLA272. Up to about 100 kbps, length stays flat at 1200 m. Above 100 kbps the allowed length scales inversely with the data rate, because signal rise times shorten and stub reflections fall closer together in time.

For Modbus RTU this is good news. The common rates of 9600, 19,200, and 38,400 baud all sit far below the 100 kbps corner, so you always work on the flat 1200 m plateau. A typical installation with an Eastron SDM630 at 9600 baud daisy-chains 800 m of twisted pair without issue. Only at 115 kbps and above (rare in HVAC) does the data rate start to constrain topology.

A and B, D+ and D-: untangling polarity

Swapping A and B is the most reported terminal-block mistake on installer forums. It isn't carelessness; it's a real conflict between specs. Since 2003, TIA/EIA-485-A defines "A" as the negative wire in the marking state and "B" as the positive. The Modbus 2002 spec and many vendor datasheets use the opposite convention; some vendors sidestep the issue with D+ and D- or D0 and D1 labels.

A (D-)

signal, non-inverting

B (D+)

signal, inverting

GND

signal common reference

In practice: try both orderings when first commissioning a bus. The CRC error window won't tell you which way is right, and no device burns out from swapped polarity. The table below maps how vendors installers see globally label their terminals:

Termination: 120 Ω at each end

Place a 120 Ω terminator at each physical end of the bus segment, never in between. That's the entire rule from the Modbus over Serial Line Specification, section 2.4. Forget one and reflections distort the signal, triggering intermittent CRC errors. Add three and the parallel resistance pulls so low that the driver can't reach valid logic levels and the bus dies.

Many modern devices include an internal 120 Ω switchable via DIP switch or jumper. Always verify only the two end devices have it enabled and turn it off on every device in the middle. A bias resistor (typically 680 Ω pull-up on A, pull-down on B) belongs at one point on the bus, usually the master or gateway, to guarantee a defined idle level. Many ModbusCloud Gateway variants ship with this failsafe bias built in.

Topology: daisy chain, not branches

RS485 is specified as a linear bus, also called a daisy chain. Each device gets two pairs of terminals: one for the incoming line, one for the outgoing line. Star topologies and T-junctions break the spec and create reflections.

A stub must be shorter than roughly one-tenth of the signal rise time. At 19,200 baud the rise time is about 26 µs, so a stub of a few meters is tolerable; at 1 Mbps it drops to 30 cm. That's why most vendors don't support branches even though they look practical inside an enclosure.

If you genuinely need a star topology (for example, a central gateway feeding multiple risers in a building), put an active repeater between each branch. Each branch then becomes its own linear bus.

Shielding, grounding, and the signal common

Bond the cable shield to earth at one end only. Earthing both ends creates a ground loop, into which mains frequency (50 Hz EU, 60 Hz US) couples as common-mode noise. The Schneider Electric FAQ FA221785 puts it bluntly: "the shield should be earthed at one end only".

For the signal common (GND wire), the TIA-485-A rule is clear: as soon as devices are powered from different potential references, the common-mode voltage drifts outside the allowed -7 V to +12 V range. Then a third wire as signal common is mandatory. On a single panel sharing one PE bar you can sometimes skip it, but the spec choice is always three conductors.

Field mistakes that break a Modbus bus

Three installer mistakes show up in nearly every support ticket. First: 230 V or 120 V power cables running parallel to the RS485 pair in the same trunking, with no metal divider. EN 50174-2 and IEC 60364-5-52 require at least 200 mm separation between ELV signal cables and LV power circuits, or a metallic barrier. Over 50 m of parallel run in one tray you'll start seeing CRC errors on a 9600 baud bus.

Second: a termination resistor left active in a middle device. The previous installer left the DIP switch on, the next device too, and the third again. The result is a parallel resistance of 40 Ω, which the driver can't drive. Test every new bus by measuring the idle voltage between A and B: about 200 mV is healthy; 5 mV means too many terminators are in circuit.

Third: reusing whatever cable already sits in the building. Cat6 is acceptable as a stopgap, telephone cable J-Y(St)Y can pass in older installations, but unknown control cable without a twisted pair spec must stay out. A 4-conductor untwisted control cable in a tray full of 230 V will produce unreadable frames within 30 m.

Testing and troubleshooting RS485

Three tools belong in the bag of any installer wiring Modbus RTU. A multimeter for the first sanity check: between A and B in idle expect about 200 mV from the bias resistors. Below 50 mV: bias missing or too many terminators. Above 800 mV: a terminator is missing at one end.

A USB-to-RS485 adapter (FTDI based, around USD 30 from L-com or AutomationDirect) plus a laptop running modpoll or QModMaster lets you read any register from any point on the bus. Move the adapter along the chain to pinpoint which segment is failing. A Modbus gateway with a built-in diagnostic mode, such as the ModbusCloud Gateway, shows you remotely which slaves answer and which time out, without having to be on site.

When a Modbus gateway beats stretching RS485 further

RS485 is excellent at one site, and only at one site. If you need to link a rooftop solar array on building A to a dashboard in building B, or aggregate 50 distributed sites into one platform, more copper won't help. That's where a Modbus gateway earns its keep: it speaks RS485 locally to the slaves and forwards the data over IP as Modbus TCP, MQTT, or a vendor cloud protocol.

The ModbusCloud Gateway is built for this. It acts as the RS485 master with built-in failsafe bias, runs the polling cycle to the slaves, and ships the data to the cloud over an encrypted link without needing a VPN or a separate router. For a comparison with other gateway options see the Modbus gateway buyer guide for installers.

Frequently asked questions

Conclusion

RS485 wiring isn't rocket science, but the details matter. Reach for a specified twisted-pair cable with 120 Ω impedance, daisy-chain every device on one linear bus, place 120 Ω terminators at both ends, ground the shield at one end only, and keep clear of 230 V trunking per IEC 60364-5-52. Keep failsafe bias on one gateway, and run a third wire as signal common whenever devices are fed from different potential references.

If you need to reach beyond one site or aggregate alarms and logs across many installations, a Modbus gateway is the next step. It takes the RS485 layer off your hands and pushes the data over IP without another foot of copper.