CAN vs LIN vs FlexRay vs Ethernet
Choosing the Right Protocol
A vehicle architect does not choose one protocol for the entire car. Each protocol occupies a specific niche defined by bandwidth needs, latency requirements, cost per node, and wiring constraints. Understanding where each protocol fits is essential for system design.
| Protocol | Max Speed | Wires | Max Nodes | Cost/Node | Primary Use Case |
|---|---|---|---|---|---|
| CAN 2.0B | 1 Mbit/s | 2 (differential pair) | ~32 electrical, 2048 logical | Medium ($2–5) | Powertrain, chassis, body control |
| CAN FD | 8 Mbit/s (data phase) | 2 (same as CAN) | Same as CAN | Medium ($3–7) | High-bandwidth CAN replacement |
| LIN | 20 kbit/s | 1 (single wire + GND) | 1 master + 15 slaves | Very low ($0.5–1) | Mirrors, seats, rain sensors, HVAC flaps |
| FlexRay | 10 Mbit/s | 2 or 4 (dual channel) | ~64 | High ($10–20) | X-by-wire (steer, brake), advanced chassis |
| 100BASE-T1 | 100 Mbit/s | 1 pair (unshielded) | Point-to-point via switch | Medium-High ($5–10) | ADAS cameras, surround view, gateway links |
| 1000BASE-T1 | 1 Gbit/s | 1 pair (shielded) | Point-to-point via switch | High ($15–30) | Autonomous driving compute, radar data |
When to Use CAN
CAN is the right choice when:
- You need real-time control data at moderate bandwidth (signals updating every 10–100 ms)
- Multiple ECUs need to share the same bus (broadcast model)
- Fault tolerance matters — CAN's error detection and fault confinement are exceptionally robust
- Cost must be balanced against performance (CAN is cheaper per node than FlexRay or Ethernet)
- The data payload fits in 8 bytes (CAN 2.0B) or 64 bytes (CAN FD)
When NOT to Use CAN
- Large data transfers (firmware update over CAN takes 10+ minutes via ISO-TP; Ethernet does it in seconds)
- Video or point-cloud data (cameras and lidars produce megabytes per second — Ethernet only)
- Extremely low-cost nodes that only need occasional commands (LIN is cheaper)
- Safety-critical by-wire systems requiring redundant communication channels (FlexRay or Ethernet with TSN)
LIN: CAN's Budget Companion
LIN (Local Interconnect Network) was designed specifically for cost-sensitive nodes where CAN is overkill. A rain sensor, a seat position motor, or an interior light does not need 500 kbit/s and hardware arbitration. LIN provides 20 kbit/s on a single wire with a software-based master-slave architecture.
The typical pattern is: a body control module (BCM) sits on the CAN bus and also acts as the LIN master for 5–15 LIN slave nodes. The BCM bridges between CAN and LIN, forwarding relevant signals in both directions.
Key Concept: A common interview question: "Why not just use CAN everywhere?" The answer is economics. A CAN transceiver costs $2–5; a LIN transceiver costs $0.30–0.50. Multiply by 30 low-bandwidth nodes per vehicle, and LIN saves $50–130 per car. At 500,000 cars/year, that's $25–65 million in savings.
FlexRay: The High-Reliability Option
FlexRay was developed by a consortium of BMW, DaimlerChrysler, Motorola, and Philips for safety-critical, high-bandwidth applications. It offers 10 Mbit/s with deterministic time-triggered scheduling and optional dual-channel redundancy.
In practice, FlexRay saw limited adoption. BMW used it extensively in the X5 (E70) and 7 Series (F01) for active suspension and steering systems. However, its complexity and cost led most OEMs to skip FlexRay and wait for Automotive Ethernet, which offers higher bandwidth at comparable cost.
Automotive Ethernet: The Future Backbone
100BASE-T1 (BroadR-Reach) and 1000BASE-T1 bring IT-world Ethernet into vehicles with a crucial adaptation: single unshielded twisted pair instead of the 4-pair cables used in offices. This reduces weight and cost while delivering 100 Mbit/s or 1 Gbit/s bandwidth.
Ethernet does not replace CAN — it complements it. The emerging architecture is: Ethernet backbone connecting domain controllers and high-bandwidth sensors, with CAN remaining as sub-bus for the hundreds of low-bandwidth control nodes that don't need Ethernet's throughput.
Exercise: Look up the communication architecture diagram for any recent vehicle platform (VW MEB, Hyundai E-GMP, BMW CLAR). Identify which functions use CAN, which use LIN, and which use Ethernet. Notice how CAN persists even in the most modern architectures.
Assessment
Q1: A rain sensor that needs to send a simple on/off signal every 500 ms would be best served by:- A) CAN FD at 8 Mbit/s
- B) LIN at 20 kbit/s
- C) 100BASE-T1 Automotive Ethernet
- D) FlexRay with dual-channel redundancy
- A) FlexRay is slower than CAN
- B) Its complexity and cost led OEMs to wait for Automotive Ethernet instead
- C) FlexRay was never standardized
- D) FlexRay cannot support safety-critical applications