
On this page
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.
What RS485 is and why Modbus uses it
RS485 is a differential transmission layer, first published in 1983 and current as ANSI/TIA/EIA-485-A-1998, reaffirmed in 2012. 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.
TIA-485-A specifies only the electrical behaviour of drivers and receivers. The protocol, the connectors and the cable come from Modbus, Profibus or BACnet. The table lists the electrical limits you work against on site.
| Parameter | Value |
|---|---|
| Driver output, loaded | at least 1.5 V differential across 54 Ω |
| Receiver threshold | ±200 mV differential |
| Common-mode range | -7 V to +12 V |
| Devices per segment | 32 unit loads, 256 with 1/8 unit-load transceivers |
Source: ANSI/TIA/EIA-485-A-1998.
Modbus RTU is older than RS485 (1979 against 1983). RS485 became its usual physical layer 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 19200 baud over 800 m you'll see CRC errors creep in. Cable types side by side, with shield construction and the CAT6 question in full, are in RS485 cable selection for Modbus.
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. TIA's application guide TSB-89-A puts the sloped part as a product: baud rate times cable length in metres stays under 10⁸.
For Modbus RTU this is good news. The common rates of 9600, 19200, and 38400 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. 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.
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:
| Brand | Terminal labels | Convention |
|---|---|---|
| Eastron SDM630 | A and B | A = positive (Modbus 2002) |
| Janitza UMG | A and B | B = positive (TIA-485-A) |
| Schneider iEM3000 | A1 and A2 | A1 = positive |
| SMA Sunny Boy | D+ and D- | D+ = non-inverting |
| Daikin Altherma | + and - | + maps to A on Eastron |
A multimeter settles the question before the first frame. With bias on the bus and no device transmitting, the wire with the higher DC voltage is B (D+). If A reads higher than B, the pair is swapped.
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. Two 120 Ω terminators in parallel make 60 Ω, just above the 54 Ω load TIA-485-A specifies the driver for.
The symptom usually tells you which termination fault you are looking at.
| Symptom | Likely cause |
|---|---|
| CRC errors on distant devices, nearby devices fine | Terminator missing |
| Low signal swing on every device | Three or more terminators |
| Random CRC errors at higher baud rates | Terminator on a stub or in the wrong place |
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.
Bias resistors give the bus a defined idle level. With no driver active, the terminators pull the differential voltage to 0 V, and a receiver can read noise as a start bit. A pull-up from B (D+) to the supply and a pull-down from A (D-) to ground, typically 560 Ω or 680 Ω each, hold B above A. Fit them at one point only, usually the master or gateway. Transceivers with true fail-safe inputs, such as the MAX3080 and ISL83082, switch at -50 mV and need no external bias; older devices often do.
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 19200 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". Connect the shield through at every device, so it forms one continuous screen, and earth it once, by convention at the master side.
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. Control Solutions Minnesota names a missing signal common as the most common cause of RS485 failures.
Above 7 V of common-mode difference, for example between buildings or near large motor drives, only a galvanically isolated repeater protects the transceivers. Control Solutions documented a site with 270 V between two earth points, a voltage no non-isolated transceiver survives.
Wiring a Modbus RTU bus step by step
A bus wired in this order shows a fault in the segment you added last, not somewhere in a finished installation.
- 1
Plan the route
Mark every device and draw one line through all of them, with the master or gateway at one end. Cross power cables at right angles only.
- 2
Measure the cable
Add 10 to 15% for routing. Use twisted pair only: untwisted control cable or installation wire rejects no noise.
- 3
Prepare the cable ends
Strip about 50 mm of jacket and 8 mm per conductor, and crimp ferrules on stranded wire. Bare strands work loose and give intermittent contact faults. Keep the pair twisted up to the terminal.
- 4
Connect the master or gateway first
A two-wire port marked D+ and D- takes the pair directly. A gateway with separate transmit and receive terminals needs R+ bridged to D+ and R- to D- for half duplex, which is what Modbus RTU uses. Power it up and check that it boots.
- 5
Loop through to each device
Each device takes the incoming and the outgoing cable on the same terminals, A to A and B to B, with at most two wires per terminal. Give every device a unique address from 1 to 247 and the same baud rate, parity, data bits and stop bits.
- 6
Set the termination
Enable 120 Ω at the first and the last device only. Use the built-in DIP switch or jumper where there is one, otherwise a 120 Ω, 0.25 W resistor between A and B.
- 7
Earth the shield once
Earth the shield at the master side and insulate it at the far end.
- 8
Test each device before adding the next
Read a register from each new device with a USB-RS485 adapter and QModMaster or Modbus Poll before you connect the next one.
Field mistakes that break a Modbus bus
Three installer mistakes show up again and again on service calls. 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.
The same multimeter checks the termination, with the bus powered down, and the potential difference between the GND terminals of two powered devices.
| Measurement | Reading | Meaning |
|---|---|---|
| Resistance A to B, power off | about 60 Ω | Two terminators, correct |
| Resistance A to B, power off | about 120 Ω | One end has no terminator |
| Resistance A to B, power off | open circuit | No termination at all |
| Resistance A to B, power off | under 10 Ω | Short circuit in the cable |
| Voltage GND to GND between two devices | under 1 V | Acceptable |
| Voltage GND to GND between two devices | 1 to 7 V | Marginal |
| Voltage GND to GND between two devices | above 7 V | Isolated repeater needed |
A USB-to-RS485 adapter (FTDI based, around USD 30 from L-com or AutomationDirect) plus a laptop lets you read any register from any point on the bus. modpoll, QModMaster and Modbus Poll all work for this. Adapters with a CH340 chip cause timing and echo problems. Move the adapter along the chain to pinpoint which segment is failing. A Modbus gateway with a built-in diagnostic mode shows you remotely which slaves answer and which time out, without having to be on site.
Standards that apply to an RS485 installation
Next to TIA-485-A, three documents cover an RS485 bus in a building. The Modbus over Serial Line Specification V1.02 sets Modbus RTU on top of the electrical layer: two wires, one master and up to 247 slaves. Its default is 19200 baud with even parity, although 9600 baud 8N1 is more common on site. EN 50174-2 covers separation, earthing and containment for data cabling inside buildings in Europe.
EN 50575 has applied since July 2017 under the EU Construction Products Regulation. Every cable installed permanently in an EU building needs a CE mark and a declaration of performance, and RS485 cables usually fall in reaction-to-fire classes B2ca to Eca.
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 reads your Modbus RTU and TCP devices into a cloud dashboard using ready-made templates. It acts as the RS485 master, 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. Its RS485 port is a single two-wire port marked D+ and D-, so the pair lands directly on it. Register maps for common energy meters and heat pumps are ready to use in the template library. For a comparison with other gateway options see the Modbus gateway buyer guide for installers.
Frequently asked questions
How do you wire an RS485 cable?
Three terminals per device: A (D-, inverting), B (D+, non-inverting), and GND as the signal common. Daisy-chain all devices on one twisted pair plus the common, with a 120 Ω terminator at each physical end of the bus.
Is RS485 2-wire or 4-wire?
Modbus RTU uses RS485 in half-duplex with 2 wires (A and B) plus an optional third wire for the signal common. Full-duplex 4-wire RS485 exists in the spec but isn't used by Modbus.
What happens if you wire RS485 backwards?
The bus won't communicate and you'll see only CRC errors or no responses. No device is damaged by reversed polarity, so swap A and B and try again. This is a frequent issue because vendors label A and B inconsistently across the industry.
Does RS485 need a ground wire?
Per TIA-485-A, yes whenever devices are powered from different potential references. In practice: any time your gateway and slaves sit on different phases or different buildings, run a third wire as signal common. On a single PE bar in one panel you can sometimes skip it, but the spec choice is three conductors.
Can I use Cat6 for RS485?
At short range (under 50 m) and low baud rate (9600 or 19200) Cat6 will run a Modbus RTU bus fine. The impedance is 100 Ω instead of the 120 Ω spec, so reflections are slightly higher. As a design choice, pick a specified RS485 cable; Cat6 is a stopgap.
How long can RS485 cable run be?
About 1200 m at 100 kbps and below. For Modbus RTU at 9600 or 19200 baud the full 1200 m is achievable in low-EMI environments. Above 100 kbps the allowed length drops inversely with the data rate, so at 1 Mbps you're down to about 120 m.
How many devices can I put on one RS485 bus?
Up to 32 standard transceivers per segment, or 256 with 1/8 unit-load drivers. At the Modbus RTU layer you have up to 247 logical slave addresses. Beyond that or over long distances, add an active repeater or a second gateway.
My Modbus RTU bus does not answer. Where do I start?
At the wiring, in this order. Measure the idle voltage: B should sit above A, otherwise swap the pair. Check that every device has the same baud rate, parity and stop bits and its own address. Then check that the GND wire runs through, that 120 Ω sits at both ends, and that the bus has only one master.














