Why RS-485 Is Not Just UART Over a Longer Cable

5 minute

Why RS-485 Is Not Just UART Over a Longer Cable

RS-485 is often discussed together with UART and Modbus. Manuals say “RS-485 serial port”, and many tools treat it like a longer serial port.

That is convenient, but it creates bad debugging habits. UART defines asynchronous byte framing. Modbus RTU defines master requests to slave registers. RS-485 defines an electrical layer for differential signaling, multi-drop buses, longer distance, and noisy environments.

UART

11 minute

UART

Devices do not always need a shared bus, and they do not always need complex arbitration. Debug ports, module links, and data exchange between an MCU and a host often have a simpler requirement: each side gets a transmit line and a receive line, no extra clock, no chip select, and no address broadcast, as long as bytes can be delivered reliably to the other side.

UART solves exactly that kind of point-to-point serial communication. It optimizes first for low implementation cost, direct wiring, and a low barrier for both hardware and software rather than for bus expansion or high throughput. That is why it has stayed in engineering use for decades: often what you need is not a more complex link, but a channel that works as long as both sides agree on the parameters.