CAN-FD - Extended Data Fields - Vehicle Networks

CAN-FD Frame Differences from CAN 2.0

CAN-FD Frame New Bits (after RTR/SRR in arbitration)

  CAN 2.0:  ... RTR IDE r0 DLC[3:0] DATA[0-64bits] CRC[15] ...
  CAN-FD:   ... RRS IDE FDF res BRS ESI DLC[3:0] DATA[0-512bits] CRC[17or21] ...

  New bits:
    FDF (FD Frame)  = 1 → this is a CAN-FD frame (was reserved r1 in 2.0)
    BRS (Bit Rate Switch) = 1 → data phase at higher rate; 0 = same rate as arbitration
    ESI (Error State Indicator) = 0 if transmitter Error Active; 1 if Error Passive

  DLC encoding extended:
    DLC 9  → 12 bytes    DLC 12 → 32 bytes
    DLC 10 → 16 bytes    DLC 13 → 48 bytes
    DLC 11 → 20 bytes    DLC 14 → 64 bytes
    DLC 15 → 64 bytes    (DLC 0-8 = same as CAN 2.0)

DLC Value	CAN 2.0 Bytes	CAN-FD Bytes
0–8	0–8	0–8 (same)
9	N/A (invalid in 2.0)	12
10	N/A	16
11	N/A	20
12	N/A	24
13	N/A	32
14	N/A	48
15	N/A	64

CRC Enhancement in CAN-FD

Frame Size	CRC Length	Polynomial	Coverage
DLC 0–10 (≤16 bytes)	17-bit CRC	0x3685B	Stronger than CAN 2.0 15-bit for FD frame lengths
DLC 11–15 (20–64 bytes)	21-bit CRC	0x302899	Required for longer payloads at higher data rates
CAN 2.0 frames	15-bit CRC	0x4599	HD distance 6 for up to 64 bits of data

💡 Stuffed Bit Count in CRC Seed

CAN-FD embeds the count of stuff bits inserted during the frame directly into the CRC seed calculation. This means the receiver can verify not just the data but also that the correct number of stuff bits were processed — an additional protection against burst errors that corrupt stuff bits at higher data rates. This field (4 bits + even parity) is included in the CRC region of the frame.

Backward Compatibility Constraints

⚠️ CAN 2.0B Nodes Generate Error Frames on FD Traffic

A CAN 2.0B (non-FD) node on the same bus sees the FDF bit as a protocol violation and immediately transmits an Active Error Flag. This destroys the FD frame. There is no workaround — CAN 2.0B and CAN-FD nodes cannot coexist on the same bus segment unless the 2.0B nodes are upgraded to FD-tolerant 2.0B mode (which ignores FD frames but does not transmit error flags). Migration strategy: upgrade all nodes in a bus segment before enabling FD traffic, or isolate FD traffic on a new segment.

Node Type	Receives FD Frame	Transmits Error Flag?
CAN-FD node	Decodes correctly	No
CAN 2.0B (FD-intolerant)	Detects protocol violation at FDF bit	Yes — destroys the FD frame
CAN 2.0B (FD-tolerant mode)	Ignores frame after FDF bit	No — silent discard

AUTOSAR Configuration for CAN-FD

XMLCanIf_FD_Config.arxml



  CanController_0_FD
  
    
      
      500
      
      
        2000
        7
        4
        2
        2

Summary

CAN-FD extends payload to 64 bytes and adds BRS for dual-rate operation, ESI for error state transparency, and strengthened 17/21-bit CRC. The critical migration constraint is backward incompatibility with CAN 2.0B — all nodes on a segment must be FD-capable before FD frames are transmitted. AUTOSAR BSW configuration requires CanIfCtrlDrvCfg FD mode and separate data-phase timing registers in CanControllerBaudrateConfig.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.