top of page

What is CAN FD? A Detailed Guide to CAN FD (Flexible Data-Rate) for Modern Automotive and Industrial Systems

Updated: Apr 7

As modern vehicles and industrial automation systems become increasingly software-driven, the amount of data exchanged between electronic control units (ECUs) continues to grow rapidly. Features such as Advanced Driver Assistance Systems (ADAS), electric powertrains, battery management systems, central gateways, over-the-air (OTA) firmware updates, and high-speed diagnostics require significantly higher bandwidth than traditional in-vehicle networks were originally designed to handle.

To address these growing demands, CAN FD (Controller Area Network Flexible Data-Rate) was introduced as an enhanced version of Classical CAN. Developed by Robert Bosch GmbH, CAN FD extends the capabilities of the traditional CAN protocol while preserving its robustness and reliability.

This article provides a detailed technical overview of CAN FD, explains why it was introduced, and outlines how it improves modern embedded communication systems.


Understanding the Limitations of Classical CAN


Classical CAN has been the backbone of automotive communication for decades. It is widely respected for its noise immunity, deterministic arbitration mechanism, and cost-effective implementation. However, as system complexity increased, two fundamental limitations became increasingly restrictive.

The first limitation is data rate. Classical CAN supports a maximum bit rate of 1 Mbps. While this is sufficient for transmitting control signals and small sensor data, it becomes a bottleneck when transferring large data blocks such as calibration data, firmware images, or high-resolution diagnostic information.

The second limitation is payload size. Classical CAN restricts each data frame to a maximum of 8 bytes. When applications require transferring 32, 48, or 64 bytes of data, multiple frames must be transmitted sequentially. This increases arbitration overhead, consumes more bus bandwidth, and introduces higher latency.

In modern domain-based or zonal vehicle architectures, where centralized ECUs manage multiple subsystems, these inefficiencies significantly impact overall network performance.


What is CAN FD?



CAN FD, standardized in ISO 11898-1:2015, is an extension of Classical CAN that enhances both data rate and payload capacity. Importantly, it retains the same arbitration mechanism used in Classical CAN, ensuring backward compatibility during network migration.

The key innovation in CAN FD is its ability to operate at two different bit rates within a single frame. During the arbitration phase, communication occurs at the nominal bit rate (typically up to 1 Mbps), maintaining compatibility and signal integrity across the network. Once arbitration is complete, the protocol can switch to a higher data bit rate—up to 8 Mbps—for transmitting the actual payload.

This feature is known as Bit Rate Switching (BRS) and is one of the most significant architectural improvements in CAN FD.


Increased Payload Capacity: From 8 Bytes to 64 Bytes


Perhaps the most impactful enhancement in CAN FD is the expansion of the data field from 8 bytes to 64 bytes per frame.

This change dramatically improves bus efficiency. For example, transmitting 64 bytes of data in Classical CAN requires eight separate frames, each undergoing arbitration. In CAN FD, the same 64 bytes can be transmitted in a single frame, reducing arbitration overhead and minimizing latency.

Larger payload capacity leads to:

  • Reduced bus load

  • Fewer frame transmissions

  • Lower network congestion

  • Improved real-time performance

  • Faster firmware flashing

This is especially beneficial in systems performing diagnostics, software updates, or high-speed logging.


Improved Error Detection and Reliability


While increasing speed and payload, CAN FD also enhances error detection mechanisms. Classical CAN uses a 15-bit CRC (Cyclic Redundancy Check). CAN FD extends this to:

  • 17-bit CRC for payloads up to 16 bytes

  • 21-bit CRC for payloads greater than 16 bytes

The longer CRC improves error detection capability, which is critical in safety-relevant automotive systems.

Additionally, CAN FD introduces the Error State Indicator (ESI) bit, allowing nodes to indicate whether they are in an error-active or error-passive state. This improves system diagnostics and fault management.

Despite the higher data rates, CAN FD maintains the strong electromagnetic robustness that made Classical CAN reliable in harsh automotive environments.


Efficiency and Performance Improvements


The combination of higher data rates and larger payloads significantly increases effective throughput. Even though a CAN FD frame may contain more bits due to longer CRC and additional control bits, the overall time required to transfer large data blocks is much lower compared to Classical CAN.

In practical terms, CAN FD offers:

  • Higher bandwidth utilization

  • Reduced latency for large data transfers

  • Improved scalability for software-defined vehicles

  • Better support for high-data applications

This makes CAN FD ideal for modern automotive systems that must handle increasing amounts of sensor and software data.


Typical Applications of CAN FD



CAN FD is now widely adopted in advanced automotive and industrial applications, including:

  • Advanced Driver Assistance Systems (ADAS)

  • Powertrain and electric vehicle control units

  • Battery management systems (BMS)

  • Central automotive gateways

  • High-speed diagnostics and calibration

  • Firmware flashing and OTA updates

  • Industrial automation and robotics

In many new vehicle platforms, CAN FD serves as a bridge between traditional CAN networks and higher-speed automotive Ethernet systems.


Hardware and Migration Considerations


Although CAN FD maintains compatibility at the arbitration level, full CAN FD functionality requires:

  • CAN FD-capable controllers

  • CAN FD-compatible transceivers

Existing Classical CAN nodes can coexist on the same network, but they will ignore CAN FD frames unless specifically configured.

For system designers, migration typically involves upgrading microcontrollers and transceivers while preserving much of the existing physical network infrastructure.


CAN FD vs Automotive Ethernet


While automotive Ethernet provides even higher bandwidth, it introduces additional complexity, cost, and architectural considerations. CAN FD offers a balanced middle ground by significantly increasing CAN performance without requiring a complete network redesign.

For many automotive subsystems, CAN FD delivers sufficient bandwidth while retaining the simplicity and determinism of CAN arbitration.


The Future of CAN FD


As vehicles become increasingly software-centric and connected, communication bandwidth requirements will continue to grow. CAN FD represents a strategic evolution of the CAN protocol, ensuring it remains relevant in next-generation vehicle architectures.

Rather than replacing Classical CAN immediately, CAN FD extends its life by adapting it to modern performance demands.


Conclusion


CAN FD (Flexible Data-Rate) is a powerful enhancement of the Classical CAN protocol that addresses its two major limitations: restricted data rate and limited payload size. By enabling up to 8 Mbps data transmission and supporting payloads up to 64 bytes, CAN FD significantly improves network efficiency, reduces latency, and enhances overall system performance.

For engineers designing modern automotive or industrial embedded systems, CAN FD provides a scalable, reliable, and cost-effective solution that bridges traditional CAN networks and high-speed communication requirements.

Comments

bottom of page