Serial communication is a method of sending data one bit at a time, in sequence, over a single communication channel. Instead of pushing multiple bits simultaneously across several wires, serial communication lines them up and transmits them as a stream of digital pulses. It’s the foundation behind USB, the wiring inside your computer’s sensors, and the industrial cables connecting factory equipment over long distances.
How Serial Communication Works
Two devices communicating serially send a series of digital pulses back and forth at a mutually agreed-upon rate. The sender converts data into individual bits and transmits them one after another. The receiver reads the voltage on its wire at precise intervals, interpreting each voltage reading as a new bit. Over time, those individual bits reconstruct a complete message.
Both devices need to agree on a few things before they can talk. First, they need a shared data rate. If two devices agree to communicate at 9,600 bits per second, the receiver checks its wire every 1/9,600th of a second for a new bit. They also need to agree on the order of the bits, typically sending the most significant bit first and the least significant bit last. Without these agreements, the receiver would just see random voltage changes with no way to decode them.
Synchronous vs. Asynchronous Transmission
Serial communication splits into two broad categories based on how the devices stay in sync. In asynchronous serial communication, there’s no shared clock. Each device keeps time independently and relies on the agreed-upon data rate to stay coordinated. This is simpler and cheaper to implement, but both sides have to maintain their timing closely enough that they don’t drift apart during a transmission.
Synchronous serial communication takes a different approach. A controller device sends a clock pulse to one or more peripheral devices, and the devices exchange one bit of data every time the clock signal changes. Because both sides are literally watching the same clock, synchronous communication can run at higher speeds without the timing drift that asynchronous methods risk.
How Data Gets Packaged
In asynchronous serial communication, raw bits aren’t just blasted across the wire. They’re wrapped in a small frame that helps the receiver know where a chunk of data begins and ends. A start bit signals the beginning of a frame, followed by the actual data bits (usually 5 to 8 of them), then an optional parity bit for error detection, and finally a stop bit that signals the end of the frame.
The parity bit is a simple error-checking mechanism. It lets the receiver detect if a bit got flipped during transmission due to electrical noise or interference. It won’t catch every error, and it can’t fix mistakes on its own, but it flags obvious corruption so the system can request a retransmission.
Baud Rate and Bit Rate
You’ll often hear serial communication described in terms of baud rate. Baud rate measures how many signal changes happen per second on the wire. In simple systems where each signal change represents a single bit, baud rate and bit rate are identical. Saying “9,600 baud” means the serial port transmits up to 9,600 bits per second.
In more advanced encoding schemes, a single signal change can carry multiple bits. The relationship is: bit rate equals baud rate multiplied by bits per symbol. A system using 16-QAM encoding, for instance, packs 4 bits into each symbol, so the bit rate is four times the baud rate. Common standard baud rates for basic serial connections include 9,600, 19,200, 38,400, 57,600, and 115,200 bits per second. Higher baud rates require shorter cable lengths to maintain signal quality.
Direction of Data Flow
Serial links operate in one of three modes depending on how data flows between devices:
- Simplex: Data travels in one direction only. A temperature sensor that only sends readings to a display is a simplex connection.
- Half-duplex: Data can travel in both directions, but only one direction at a time. Think of a walkie-talkie, where one person talks while the other listens, then they switch. This conserves bandwidth since only a single channel is needed, but it cuts overall throughput.
- Full-duplex: Data flows in both directions simultaneously. A landline telephone call is full-duplex. Both callers speak and hear at the same time. This typically requires two separate paths, one for each direction.
Why Serial Beat Parallel
Parallel communication sends multiple bits at once across several wires, which sounds faster on paper. But parallel connections create real engineering problems at higher speeds and longer distances. When eight or more signals travel on separate wires, slight differences in wire length cause bits to arrive at slightly different times, a problem called skew. The faster you push data, the worse skew gets.
Serial communication avoids this entirely by using fewer wires. That makes cables cheaper, connectors smaller, and signal integrity easier to maintain over distance. It’s also why virtually every modern high-speed connection, from USB to Ethernet to PCIe inside your computer, is serial despite the seemingly counterintuitive one-bit-at-a-time approach. The engineering wins at high speeds far outweigh the theoretical advantage of sending bits in parallel.
Common Serial Protocols
UART
UART is the simplest and most common asynchronous serial protocol. It uses just two wires: TX (transmit) and RX (receive), enabling full-duplex, point-to-point communication between two devices. There’s no shared clock, so both sides must be configured to the same baud rate, with no more than a 10% mismatch between them. UART is everywhere in embedded systems, from GPS modules to Bluetooth chips to the serial monitor in Arduino projects. Its limitation is that it only connects two devices to each other, making it unsuitable for networks with multiple peripherals.
SPI
SPI is a synchronous protocol that uses four wires: one for the master sending data, one for the slave sending data back, a clock line, and a slave select line. The master generates the clock signal and activates specific peripherals by toggling their select line. Because it uses dedicated wires for each direction, SPI operates in full-duplex mode and reaches higher speeds than UART or I2C. The trade-off is wiring complexity. Each additional peripheral needs its own select line, so connecting many devices gets bulky.
I2C
I2C uses only two wires: a data line and a clock line. It’s a synchronous protocol that supports multiple masters and multiple peripherals on the same two-wire bus, making it ideal for connecting many low-speed sensors or components with minimal wiring. Communication always happens at the initiative of a master device, which addresses specific peripherals on the bus. The downside is that it operates in half-duplex mode, since data and addressing share the same wire, and it’s slower than SPI for high-throughput applications.
Industrial Serial Standards
RS-232 is the classic serial standard that connected computers to modems, printers, and other equipment for decades. It uses single-ended signaling, meaning it measures voltage relative to a common ground. This limits its range to about 50 feet (15 meters) at 19,200 baud. Beyond that, electrical noise overwhelms the signal.
RS-485 was designed for longer distances and noisier environments. It uses differential signaling, comparing voltage between two wires rather than against ground, which makes it far more resistant to interference. RS-485 can reach 4,000 feet (1,200 meters) at 9,600 baud, dropping to about 400 feet (120 meters) at 1 Mbps. Factories, building automation systems, and industrial equipment still rely heavily on RS-485 for exactly this reason.
Serial Communication in Modern Devices
USB is the most visible serial protocol in everyday life, and it has scaled dramatically since its introduction. The latest version, USB4 v2, delivers 80 Gbps of bidirectional data transfer. When configured asymmetrically, it can push up to 120 Gbps in one direction while maintaining 40 Gbps in the other. That’s enough bandwidth for multiple 4K and 6K displays, fast external drives, and heavy multimedia workloads through a single cable. USB4 v2 achieves these speeds using PAM-3 signal encoding over existing USB-C passive cables rated for 40 Gbps, as well as newly defined 80 Gbps active cables.
Ethernet, SATA, PCIe, HDMI, and Thunderbolt are all serial protocols too. The principle is the same as a basic UART link sending 9,600 bits per second: data moves one bit at a time, in sequence, over a channel. The encoding, error correction, and speeds have grown enormously, but the core idea of serial communication remains unchanged.