Guide
What is RS485? Wiring, distance & devices explained
RS485 is the two-wire serial standard behind most industrial field devices — VFDs, energy meters, PLCs, sensors. This guide covers how it works, how to wire it correctly, and how to get its data onto Ethernet, WiFi, or the cloud.
Updated July 2026 · ThingConnect team
What RS485 is
RS485 (also written EIA-485) is an electrical standard for serial communication over a twisted pair of wires, published by the Telecommunications Industry Association. It defines voltage levels and wiring rules only — not a message format. It has become the default physical layer for industrial field devices because it is cheap, tolerant of electrical noise, and can run long distances at moderate speed.
RS485 itself does not define what the bytes mean. A messaging protocol — most commonly Modbus RTU — runs on top of it to give the raw bytes structure: addresses, function codes, data, and error checking.
RS485 vs RS232
RS232 (the classic serial port) and RS485 solve the same basic problem — serial communication — but differ in every practical way that matters on a factory floor:
| RS232 | RS485 | |
|---|---|---|
| Signaling | Single-ended (signal vs ground) | Differential (A minus B) |
| Wiring | Point-to-point, 1 device per port | Multi-drop bus, up to 32+ devices |
| Max distance | ~15 m (50 ft) reliably | Up to 1,200 m at low baud rates |
| Noise immunity | Poor — single-ended signals pick up ground noise | Strong — differential signaling cancels common-mode noise |
| Typical use today | Legacy PC serial ports, short bench links | Field buses: PLCs, VFDs, meters, sensors |
The differential signaling is the key difference: RS485 sends the same signal on two wires, inverted on one, and the receiver reads the difference between them. Electrical noise picked up equally on both wires cancels out — which is why RS485 survives being run next to VFD power cables and motor drives where RS232 would not.
How the differential bus works
An RS485 bus uses two signal wires, usually labeled A (or D-) and B (or D+), plus an optional common/ground wire. Every device on the bus connects to the same A and B lines — it is a shared bus, not point-to-point wiring like RS232 or Ethernet.
Only one device can transmit at a time. In a typical Modbus RTU setup this is managed by a single master (e.g., a PLC or gateway) that polls each slave device by address, one at a time — devices only speak when asked, which avoids collisions on the shared wire.
Wiring rules: termination & biasing
Three rules cause the majority of real-world RS485 problems when skipped:
- Termination.Put a 120-ohm resistor across A and B at each of the two physical ends of the bus — nowhere else. This matches the cable's characteristic impedance and stops signal reflections that corrupt data on longer runs or at higher baud rates.
- Biasing. When the bus is idle (nobody transmitting), the A/B lines can float and pick up noise, which receivers may misread as garbage data. A bias resistor network (pull-up on B, pull-down on A) at one point on the bus holds the idle state in a known logic level.
- Common reference.Run a ground/common wire alongside A and B, especially over longer distances or between devices powered from different supplies, to keep the common-mode voltage within the transceiver's working range.
Use twisted-pair cable, ideally shielded (STP) in electrically noisy plants. Untwisted wire gives up most of RS485's noise rejection advantage.
Distance vs baud rate
RS485's maximum cable length depends directly on baud rate — faster signaling tolerates less cable and reflection before bits become unreadable:
| Baud rate | Typical max distance |
|---|---|
| 9,600 bps | ~1,200 m (4,000 ft) |
| 19,200 bps | ~1,200 m (4,000 ft) |
| 38,400 bps | ~600 m (2,000 ft) |
| 115,200 bps | ~100 m (300 ft) |
| 921,600 bps | ~15 m (50 ft) |
Most industrial Modbus RTU installations run at 9,600–19,200 bps, trading speed for reliability over long cable runs across a plant. Figures are typical guidance, not a hard spec — actual distance depends on cable quality, termination, and the specific transceiver.
Daisy-chain vs star wiring
RS485 is designed for a daisy-chain (linear bus) topology — each device connects to the next, in a line, with termination only at the two ends. Star wiring (a central hub with wires radiating to each device) creates multiple unterminated stub ends and reflection points, and is a common cause of intermittent communication errors that are hard to diagnose.
If a star topology is unavoidable due to existing conduit runs, keep stub lengths as short as possible and consider a repeater or hub designed for RS485 star networks.
Where RS485 shows up on a factory floor
- Energy meters and power analyzers reporting kWh, current, and power factor
- Variable frequency drives (VFDs) exposing speed, load, and fault status
- PLCs and HMIs on a plant-floor field bus
- Environmental sensors — temperature, humidity, pressure transmitters
- Legacy CNC and machine controllers with a serial Modbus interface
Nearly all of these devices speak Modbus RTU on top of RS485 — it is the de facto standard messaging protocol for the bus.
Bridging RS485 to Ethernet, WiFi & the cloud
RS485 devices cannot connect to a network or the internet on their own — they only understand the serial bus. A protocol gateway sits on the RS485 line as a Modbus RTU master, polls each device by address, and re-publishes the same data as Modbus TCP (over Ethernet) or MQTT (over WiFi), so SCADA software, an MES, or a cloud dashboard can read it without any change to the field wiring.
ThingConnect's MDIM-485 RS485-to-Ethernet converter and MDIM-485/WL RS485-to-WiFi converter are both built for exactly this: transparent Modbus RTU ⇄ TCP bridging, rated for unconditioned industrial panels (-40 to 75 °C), with surge and ESD protection on the RS485 line.
Frequently asked questions
What is the maximum distance for RS485?
Up to 1,200 meters (about 4,000 ft) at low baud rates (9600 bps or below) with 24 AWG twisted-pair cable and proper termination. Distance drops as baud rate rises — see the table in this guide.
How many devices can share one RS485 bus?
The standard supports up to 32 unit loads on one bus. Many modern transceivers are "1/4 unit load" or "1/8 unit load" designs, letting 128–256 devices share a single pair — check each device's datasheet for its unit-load rating.
Do I need termination resistors?
Yes, on any run longer than a few meters or at higher baud rates. Put a 120-ohm resistor across A/B at each physical end of the bus (only the two ends, never in the middle) to prevent signal reflections.
Is RS485 the same as Modbus?
No. RS485 is the electrical/physical layer — voltage levels and wiring. Modbus RTU is a messaging protocol that commonly runs on top of RS485. You can run other protocols over RS485 too, and Modbus can also run over Ethernet (as Modbus TCP) instead of RS485 entirely.
Can I connect RS485 devices to Ethernet or WiFi?
Yes — a protocol gateway (RS485-to-Ethernet or RS485-to-WiFi converter) sits on the RS485 bus, polls the connected devices, and re-publishes the data over TCP/IP or WiFi/MQTT, so SCADA, MES, or cloud platforms can read it without rewiring the field devices.
Need to bridge an RS485 bus to Ethernet or WiFi?
MDIM-485 converters are made in India, carry a 2-year warranty, and ship with free technical support.
