Contents

CAN FD

CAN with Flexible Data-rate: up to 64-byte payloads and a faster data phase, keeping CAN's arbitration and robustness — today's default for MCU-based ECUs.

Why it exists

By the 2010s, classical CAN was running out of room: more signals, software flashing and security overhead all needed more bytes per frame. Replacing CAN entirely would have been expensive. CAN FD keeps everything engineers liked about CAN and raises the payload and speed.

What it is

  • Same arbitration and error handling as classical CAN.
  • Up to 64 bytes of payload per frame (instead of 8).
  • Two bit rates: arbitration at the normal rate (e.g. 500 kbit/s), then a faster data phase (commonly 2 Mbit/s, up to 5 Mbit/s or more with suitable transceivers).
  • Can coexist on networks with classical CAN nodes only if those nodes tolerate FD frames — in practice networks are migrated as a whole.
CAN FD frame (11-bit identifier)
SOF1 bit
Identifier11 bitsarbitration, as in classical CAN
RRS · IDE · FDF · res4 bitsFDF = this is an FD frame
BRS · ESI2 bitsBRS switches to the fast data rate
DLC4 bits0–8, 12 … 64 bytes
Data0–512up to 64 bytes
Stuff count · CRC4 + 17 / 21back to nominal rate after it
ACK · EOF9 bits

With BRS set, everything from BRS up to the CRC delimiter is sent at the faster data-phase bit rate.

How it is used

Brake, steering, airbag, battery management and inverter ECUs typically communicate over CAN FD with their zone controller or domain controller. Bigger frames allow grouping many signals into one PDU and adding SecOC and E2E data.

Example: a protected 32-byte CAN FD PDU
Application signals22 bytese.g. brake torque request, status0–21
E2E header4 bytescounter + CRC (safety)22–25
Freshness2 bytestruncated freshness value26–27
MAC4 bytestruncated SecOC MAC (security)28–31

Example sizes only. E2E profile, truncated freshness and MAC lengths are configured per PDU.

When to use it

For MCU-based ECUs with control traffic, diagnostics and security needs. For bandwidth beyond a few Mbit/s or IP-based services, use Ethernet; CAN XL bridges the two.

Best practices

  • Choose data-phase rates per network based on topology length and stubs; validate with physical-layer measurements.
  • Use the extra payload for SecOC and E2E rather than squeezing them.
  • Keep a consistent PDU design across platforms to simplify gateways.

Common pitfalls

  • Mixing classical-CAN-only nodes into an FD network.
  • Pushing data-phase speed too high on long, branched topologies, causing ringing and error frames.

What it means for your discipline

  • Networks & communication Core

    Chooses data-phase bit rates, sample points and topology; larger frames change bus-load and latency calculations.

  • Base software Core

    Configures CAN FD controllers, PDU layouts and multiplexing; migrates communication from classical CAN.

  • Cybersecurity Partial

    The 64-byte payload makes SecOC practical: room for a reasonable MAC and freshness value.

  • Hardware & silicon Partial

    Needs CAN FD-capable controllers and transceivers rated for the chosen data rate (e.g. 2–5 Mbit/s, or SIC transceivers for more).

  • Functional safety Partial

    Safety signals with E2E profiles fit comfortably; ringing at high data rates must be controlled to avoid errors.

  • Diagnostics & lifecycle Partial

    Faster flashing and diagnostics thanks to bigger frames and data-phase speed.

  • Software update & OTA Partial

    Accounts for CAN FD payload size, data-phase speed and bus load when configuring diagnostic flashing and estimating installation times.

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)
  • MCAL — The safety island usually owns the HPC's CAN FD controllers and their drivers.
  • Classic RTE & COM — Classic COM and PduR pack and route CAN FD PDUs between the island and the application processor.
MCU-based ECU · AUTOSAR Classic
  • Communication — COM packs signals into PDUs; PduR routes them; SecOC adds the MAC that fits into 64-byte frames.
  • ECU abstraction — CanIf and CanTrcv abstract the controller and transceiver from the rest of the stack.
  • Microcontroller abstraction (MCAL) — The Can driver configures bit timing for the arbitration and data phases.
  • Microcontroller · HSM — Needs a CAN FD-capable controller and a transceiver rated for the data-phase rate.