Why Serial Buses?
The Wiring Problem
In the 1970s, a typical passenger car had around 50 electrical functions: headlights, wipers, turn signals, ignition, fuel gauge, and a handful of sensors. Each function had its own dedicated wire running from the sensor or actuator to its control switch or dashboard indicator. This was manageable.
By the 1990s, a mid-range car had over 200 electrical functions. By 2020, a modern premium vehicle has over 3,000 signals being exchanged between 70–100 ECUs. If every signal had its own dedicated wire, a modern car would need a wiring harness weighing over 100 kg and containing 4,000+ individual wires. This is physically impossible to route through a vehicle body, prohibitively expensive to manufacture, and a nightmare to diagnose when something fails.
Key Concept: The fundamental reason serial buses exist in vehicles is weight and cost reduction. A single CAN bus wire pair replaces dozens of point-to-point signal wires. This isn't about speed or elegance — it's about making modern vehicles physically buildable.
Parallel vs Serial Communication
In parallel communication, multiple bits are transmitted simultaneously on separate wires. An 8-bit parallel bus sends all 8 bits at once but requires 8 data wires plus ground and control lines. This is fast over short distances (think: PCB traces between a microcontroller and RAM) but terrible for automotive use because each additional wire adds weight, cost, and potential failure points.
Serial communication sends bits one after another on a single wire (or differential pair). It requires far fewer physical connections but needs a higher clock rate to achieve the same throughput. For automotive applications, this trade-off is overwhelmingly favorable: two wires replacing dozens is worth the added protocol complexity.
| Aspect | Parallel | Serial |
|---|---|---|
| Wires for 8-bit data | 8 data + clock + control = 10–12 | 1 or 2 (differential pair) |
| Typical distance | < 0.5 m (PCB-level) | Up to 40 m (CAN bus) |
| Cost per connection | High (many connectors) | Low (single connector) |
| EMC susceptibility | High (parallel wire crosstalk) | Low with differential signaling |
| Automotive use | None (within-chip only) | CAN, LIN, FlexRay, Ethernet |
The Multi-Drop Bus Concept
CAN uses a multi-drop bus topology: a single pair of wires runs through the vehicle, and every ECU connects to this same wire pair. When one ECU transmits, every other ECU on the bus hears the message. Each ECU then decides, based on the message identifier, whether to accept or ignore it.
This is fundamentally different from point-to-point communication (like UART between two chips). In a point-to-point system, there is one sender and one receiver. On a CAN bus, there is one sender and potentially 50+ receivers — but the sender does not need to know who is listening. It broadcasts data, and interested nodes consume it.
Key Concept: CAN is producer-consumer, not client-server. An ECU producing "engine RPM" doesn't send it "to the instrument cluster" — it broadcasts a message containing RPM data, and any node that needs RPM (cluster, transmission ECU, ADAS controller) independently decides to receive it. This decoupling is what makes CAN networks easy to extend.
A Brief History of CAN
CAN (Controller Area Network) was developed by Robert Bosch GmbH starting in 1983. The key milestones:
- 1983: Bosch begins CAN development, led by engineer Uwe Kiencke.
- 1986: CAN protocol officially introduced at the SAE Congress in Detroit.
- 1987: Intel produces the first CAN controller chip (82526). Philips follows with the 82C200.
- 1991: Mercedes-Benz W140 (S-Class) becomes the first production car to use CAN for internal ECU communication.
- 1993: CAN is standardized as ISO 11898 (high-speed CAN, up to 1 Mbit/s).
- 2003: ISO 11898-1:2003 revision solidifies the data link layer specification.
- 2012: Bosch releases CAN FD (Flexible Data-rate) specification, allowing 64-byte payloads and higher bit rates.
- 2015: CAN FD standardized as ISO 11898-1:2015.
Today, CAN remains the most widely deployed automotive network protocol. A modern vehicle typically has 2–5 separate CAN buses serving different domains (powertrain, chassis, body, infotainment, diagnostics).
Exercise: Open the hood of any car made after 2005. Locate the OBD-II diagnostic connector (usually under the dashboard, driver side). Pins 6 and 14 are CAN-High and CAN-Low. This is your first physical encounter with a CAN bus.
Assessment
Q1: What is the primary reason automotive systems adopted serial buses over dedicated wiring?- A) Serial buses are faster than parallel wiring
- B) Weight and cost reduction as electronic functions multiplied
- C) Serial protocols were invented before parallel communication
- D) Government regulations mandated serial communication
- A) It addresses the message specifically to the instrument cluster
- B) Only the nearest ECU on the bus can receive it
- C) Any node on the bus can independently decide to receive or ignore it
- D) The message must be acknowledged by all nodes before transmission completes