Contents

Classical CAN (CAN 2.0)

The robust, cheap broadcast bus that still carries most control messages in vehicles: arbitration by message ID, 8-byte payloads, up to 1 Mbit/s.

Why it exists

Before CAN, every connection between ECUs needed its own wires. Bosch introduced CAN in the 1980s as a shared two-wire bus on which all ECUs can talk, with built-in priority and error handling. It is cheap, robust against electrical noise and still the workhorse of vehicle control networks.

What it is

  • A broadcast bus: every message is received by every node; receivers decide what they need.
  • Messages, not addresses: each frame has an identifier (11-bit standard or 29-bit extended) that names its content and sets its priority.
  • Payload: up to 8 bytes per frame.
  • Speed: typically 500 kbit/s in vehicles (up to 1 Mbit/s), limited by bus length and propagation delay.
Classical CAN data frame (11-bit identifier)
SOF1 bitstart
Identifier11 bitsnames the content; lower = higher priority
RTR1 bit
IDE · r02 bits
DLC4 bitsdata length 0–8
Data0–640–8 bytes of signals
CRC15 bits+ delimiter
ACK · EOF9 bitsreceivers confirm; end of frame

Identifier and RTR take part in arbitration. Stuff bits, inserted after five equal bits, are not shown.

Example: what the 8 data bytes carry
Vehicle speed2 bytes16-bit, scaled0–1
Yaw rate2 bytes16-bit, signed2–3
Status flags1 byte8 single-bit signals4
Reserved1 byte5
E2E counter1 byte6
E2E CRC1 byte7

Example layout. The real position, length, scaling and byte order of every signal is defined in the communication matrix (DBC or ARXML).

How it works

  • Arbitration: when two nodes send at once, the frame with the lower ID wins bit by bit without destroying the other frame (non-destructive arbitration). The loser retries.
  • Error handling: CRC, bit monitoring, stuffing and acknowledgement detect errors; a faulty node is automatically isolated by error counters (“error passive”, “bus-off”).
  • Timing: most messages are sent cyclically (e.g. every 10 ms); some are event-driven.

When to use it

Classical CAN fits control signals with small payloads and moderate data rates: body, comfort, legacy powertrain and many truck functions (via J1939). For more payload or security overhead, CAN FD is the better choice.

Best practices

  • Keep bus load below about 50–60 % to leave room for retries and growth.
  • Assign IDs by priority deliberately; document every message in a database (DBC or ARXML).
  • Use gateways to separate external-facing ECUs from control buses.
  • Add E2E protection for safety-relevant signals.

Common pitfalls

  • Assuming CAN is secure because it is “internal” — it is not.
  • 8 bytes leave almost no room for SecOC; consider CAN FD for protected traffic.

What it means for your discipline

  • Networks & communication Core

    Owns message catalogues, IDs and priorities, cycle times, bus load and physical layer design (termination, stub lengths).

  • Base software Core

    Configures the CAN driver, CanIf, COM and timeouts; handles bus-off recovery.

  • Cybersecurity Partial

    CAN has no authentication or encryption: any node can send any ID. Protection comes from segmentation, gateways, SecOC and IDS.

  • Functional safety Partial

    CAN's error handling is strong, but safety messages still need E2E protection against corruption, loss and delay at application level.

  • Hardware & silicon Partial

    Chooses transceivers (e.g. with partial-networking wake-up) and protects against EMC and ground-shift issues.

  • Diagnostics & lifecycle Partial

    UDS over CAN (ISO-TP) is still the most common diagnostic transport in ECUs.

  • Software update & OTA Partial

    Uses ISO-TP over CAN to flash ECUs; accounts for small payloads, arbitration and bus load when setting transfer parameters, timeouts and update duration estimates.

No direct stake: E/E architecture · HPC & application software

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Classic RTE & COM — Packs control signals into CAN PDUs and manages communication through the safety island's Classic stack.
  • MCAL — Drives the safety island's CAN controller, handling frame transmission, reception and controller error states.
MCU-based ECU · AUTOSAR Classic
  • Communication — Packs signals, routes CAN PDUs and supervises message reception timeouts.
  • ECU abstraction — CanIf connects upper communication layers to CAN drivers and coordinates controller modes and bus-off recovery.
  • Microcontroller abstraction (MCAL) — Configures CAN identifiers, hardware filters and bit timing, and transmits and receives frames.