Topics / Communication Protocols / Q23
What is the difference between CAN and CAN FD?
Short answer: CAN FD (Flexible Data-rate) keeps classic CAN's arbitration (at the nominal bit rate, so priorities and robustness stay the same) but allows up to 64 data bytes per frame instead of 8, switches to a faster bit rate for the data phase (commonly 2–5 Mbps, versus ≤ 1 Mbps for arbitration), uses stronger CRCs (17 or 21 bits plus a stuff-bit counter), and drops remote frames.
| Classic CAN | CAN FD | CAN XL | |
|---|---|---|---|
| Max payload | 8 bytes | 64 bytes | 2048 bytes |
| Data-phase bit rate | ≤ 1 Mbps | typically 2–5 Mbps (up to 8) | up to ~20 Mbps |
| CRC | 15-bit | 17-bit (≤ 16 bytes) / 21-bit | 13-bit header CRC + 32-bit frame CRC |
| DLC | 0–8 | 0–8, 12, 16, 20, 24, 32, 48, 64 | 1–2048 |
| Remote frames | yes | no | no |
New control bits: FDF (marks an FD frame), BRS (bit-rate switch on/off), ESI (error state indicator of the transmitter).
Practical points
- A classic CAN controller that sees an FD frame flags errors, so mixed networks need FD-tolerant controllers or gateways ("partial networking" transceivers can ignore FD traffic).
- Data-phase timing is more demanding: transceiver delay compensation (TDC) and accurate sample points are needed at higher rates.
- Linux SocketCAN supports FD (
struct canfd_frame,ip link set can0 type can bitrate 500000 dbitrate 2000000 fd on). - Larger payloads mean fewer frames for the same data: essential for security (room for MACs, AUTOSAR SecOC) and for flashing ECUs faster.