Why CAN FD Matters: A Leap Beyond Classical CAN
Why CAN FD Matters: A Leap Beyond Classical CAN
Classical CAN needs to evolve
In 1986, Bosch officially presented the CAN protocol at the Society of Automotive Engineers (SAE). In 1994, the CAN2.0 Specification was published. Since then, Classical CAN has become the de facto standard for in-vehicle communication networks. However, the emergence of electric vehicles—demanding increasingly complex, high-performance, and intelligent ECUs—has created the need for a more efficient and higher-bandwidth communication protocol within the automotive industry.
CAN FD Introduced
Bosch officially introduced CAN FD (Flexible Data-Rate), an enhanced version of the CAN protocol, in 2012. It was subsequently standardized by ISO in 2015 and is now in ISO 118981:2015.
Note: The original Bosch CAN FD (non-ISO) is incompatible with ISO CAN FD.
CAN FD Features
- Maximum data rate increased from 1 Mbps to 8 Mbps.
- Data payload increased from 8 bytes to 64 bytes.
- Backward compatibility with CAN 2.0.
-
Adds BRS (Bit-Rate Switch) bit for balancing reliability and speed:
Using low bitrate for safe arbitration and high bitrate for efficient data transfer. -
Adds ESI (Error State Indicator) bit:
Allows a CAN FD node to signal its error state directly in the data frame, improving network robustness and safety.
Why CAN FD?
- Higher data throughput
- Support for complex ECUs
- Improved Error Handling
- Backward Compatibility
- Lower protocol overhead per byte
CAN FD is designed to meet the bandwidth, reliability, and scalability demands of next-generation automotive and industrial systems, while remaining compatible with existing CAN infrastructure.
Applications
Electric Vehicles
Due to the growing number and complexity of ECUs in next-generation electric and hybrid vehicles, there is a critical need for faster, more efficient, secure, and highly reliable in-vehicle communication networks. Only systems equipped with CAN FD support are capable of fulfilling these requirements.
ECU Flashing
Vehicle software is becoming increasingly complex. Higher data rates are essential for efficient ECU flashing and parameter tuning operations.
What is ECU Flashing?
Watch here
Robotics
In industrial control and automation, systems depend on time-synchronized operations, e.g., multi-axis robotic arms. These systems often use CANopen and need several Process Data Objects (PDOs) from each controller to be transmitted in a tightly synchronized manner. By adopting CANopen FD, all necessary data can be packed into a single frame, improving transmission efficiency and timing precision.
ADAS and Safe Driving
As more passenger vehicles integrate ADAS features, the data traffic has grown substantially, creating a serious load on Classical CAN.
Heavy Vehicle / Commercial Vehicle
Currently, all heavy-duty and commercial vehicles are required to comply with the J1939 communication protocol, including buses, trucks, and large construction machinery. J1939 is a higher-layer protocol built on CAN, and most implementations only support the 250K and 500K bitrates defined in CAN 2.0. As vehicle systems become more complex, heavy-duty vehicles will migrate to CAN FD. The upcoming J1939 FD standard is expected to significantly enhance performance, especially for applications such as ADAS and electric buses.
Secure CAN - CAN FD authentication via SecOC
What is SecOC?
SecOC stands for Secure Onboard Communication, a key concept defined in the AUTOSAR standard.
SecOC is a security module designed to protect the authenticity and integrity of messages exchanged between Electronic Control Units (ECUs) within a vehicle. It helps:
- Prevent message tampering within the in-vehicle network (e.g., CAN, CAN FD, Ethernet)
- Detect unauthorized modifications
- Ensure that the data originates from a trusted ECU
Why CAN FD Matters: A Leap Beyond Classical CAN
Why CAN FD Matters: A Leap Beyond Classical CAN
Classical CAN needs to evolve
In 1986, Bosch officially presented the CAN protocol at the Society of Automotive Engineers (SAE). In 1994, the CAN2.0 Specification was published. Since then, Classical CAN has become the de facto standard for in-vehicle communication networks. However, the emergence of electric vehicles—demanding increasingly complex, high-performance, and intelligent ECUs—has created the need for a more efficient and higher-bandwidth communication protocol within the automotive industry.
CAN FD Introduced
Bosch officially introduced CAN FD (Flexible Data-Rate), an enhanced version of the CAN protocol, in 2012. It was subsequently standardized by ISO in 2015 and is now in ISO 118981:2015.
Note: The original Bosch CAN FD (non-ISO) is incompatible with ISO CAN FD.
CAN FD Features
- Maximum data rate increased from 1 Mbps to 8 Mbps.
- Data payload increased from 8 bytes to 64 bytes.
- Backward compatibility with CAN 2.0.
-
Adds BRS (Bit-Rate Switch) bit for balancing reliability and speed:
Using low bitrate for safe arbitration and high bitrate for efficient data transfer. -
Adds ESI (Error State Indicator) bit:
Allows a CAN FD node to signal its error state directly in the data frame, improving network robustness and safety.
Why CAN FD?
- Higher data throughput
- Support for complex ECUs
- Improved Error Handling
- Backward Compatibility
- Lower protocol overhead per byte
CAN FD is designed to meet the bandwidth, reliability, and scalability demands of next-generation automotive and industrial systems, while remaining compatible with existing CAN infrastructure.
Applications
Electric Vehicles
Due to the growing number and complexity of ECUs in next-generation electric and hybrid vehicles, there is a critical need for faster, more efficient, secure, and highly reliable in-vehicle communication networks. Only systems equipped with CAN FD support are capable of fulfilling these requirements.
ECU Flashing
Vehicle software is becoming increasingly complex. Higher data rates are essential for efficient ECU flashing and parameter tuning operations.
What is ECU Flashing?
Watch here
Robotics
In industrial control and automation, systems depend on time-synchronized operations, e.g., multi-axis robotic arms. These systems often use CANopen and need several Process Data Objects (PDOs) from each controller to be transmitted in a tightly synchronized manner. By adopting CANopen FD, all necessary data can be packed into a single frame, improving transmission efficiency and timing precision.
ADAS and Safe Driving
As more passenger vehicles integrate ADAS features, the data traffic has grown substantially, creating a serious load on Classical CAN.
Heavy Vehicle / Commercial Vehicle
Currently, all heavy-duty and commercial vehicles are required to comply with the J1939 communication protocol, including buses, trucks, and large construction machinery. J1939 is a higher-layer protocol built on CAN, and most implementations only support the 250K and 500K bitrates defined in CAN 2.0. As vehicle systems become more complex, heavy-duty vehicles will migrate to CAN FD. The upcoming J1939 FD standard is expected to significantly enhance performance, especially for applications such as ADAS and electric buses.
Secure CAN - CAN FD authentication via SecOC
What is SecOC?
SecOC stands for Secure Onboard Communication, a key concept defined in the AUTOSAR standard.
SecOC is a security module designed to protect the authenticity and integrity of messages exchanged between Electronic Control Units (ECUs) within a vehicle. It helps:
- Prevent message tampering within the in-vehicle network (e.g., CAN, CAN FD, Ethernet)
- Detect unauthorized modifications
- Ensure that the data originates from a trusted ECU
Why CAN FD Matters: A Leap Beyond Classical CAN
Why CAN FD Matters: A Leap Beyond Classical CAN
Classical CAN needs to evolve
In 1986, Bosch officially presented the CAN protocol at the Society of Automotive Engineers (SAE). In 1994, the CAN2.0 Specification was published. Since then, Classical CAN has become the de facto standard for in-vehicle communication networks. However, the emergence of electric vehicles—demanding increasingly complex, high-performance, and intelligent ECUs—has created the need for a more efficient and higher-bandwidth communication protocol within the automotive industry.
CAN FD Introduced
Bosch officially introduced CAN FD (Flexible Data-Rate), an enhanced version of the CAN protocol, in 2012. It was subsequently standardized by ISO in 2015 and is now in ISO 118981:2015.
Note: The original Bosch CAN FD (non-ISO) is incompatible with ISO CAN FD.
CAN FD Features
- Maximum data rate increased from 1 Mbps to 8 Mbps.
- Data payload increased from 8 bytes to 64 bytes.
- Backward compatibility with CAN 2.0.
-
Adds BRS (Bit-Rate Switch) bit for balancing reliability and speed:
Using low bitrate for safe arbitration and high bitrate for efficient data transfer. -
Adds ESI (Error State Indicator) bit:
Allows a CAN FD node to signal its error state directly in the data frame, improving network robustness and safety.
Why CAN FD?
- Higher data throughput
- Support for complex ECUs
- Improved Error Handling
- Backward Compatibility
- Lower protocol overhead per byte
CAN FD is designed to meet the bandwidth, reliability, and scalability demands of next-generation automotive and industrial systems, while remaining compatible with existing CAN infrastructure.
Applications
Electric Vehicles
Due to the growing number and complexity of ECUs in next-generation electric and hybrid vehicles, there is a critical need for faster, more efficient, secure, and highly reliable in-vehicle communication networks. Only systems equipped with CAN FD support are capable of fulfilling these requirements.
ECU Flashing
Vehicle software is becoming increasingly complex. Higher data rates are essential for efficient ECU flashing and parameter tuning operations.
What is ECU Flashing?
Watch here
Robotics
In industrial control and automation, systems depend on time-synchronized operations, e.g., multi-axis robotic arms. These systems often use CANopen and need several Process Data Objects (PDOs) from each controller to be transmitted in a tightly synchronized manner. By adopting CANopen FD, all necessary data can be packed into a single frame, improving transmission efficiency and timing precision.
ADAS and Safe Driving
As more passenger vehicles integrate ADAS features, the data traffic has grown substantially, creating a serious load on Classical CAN.
Heavy Vehicle / Commercial Vehicle
Currently, all heavy-duty and commercial vehicles are required to comply with the J1939 communication protocol, including buses, trucks, and large construction machinery. J1939 is a higher-layer protocol built on CAN, and most implementations only support the 250K and 500K bitrates defined in CAN 2.0. As vehicle systems become more complex, heavy-duty vehicles will migrate to CAN FD. The upcoming J1939 FD standard is expected to significantly enhance performance, especially for applications such as ADAS and electric buses.
Secure CAN - CAN FD authentication via SecOC
What is SecOC?
SecOC stands for Secure Onboard Communication, a key concept defined in the AUTOSAR standard.
SecOC is a security module designed to protect the authenticity and integrity of messages exchanged between Electronic Control Units (ECUs) within a vehicle. It helps:
- Prevent message tampering within the in-vehicle network (e.g., CAN, CAN FD, Ethernet)
- Detect unauthorized modifications
- Ensure that the data originates from a trusted ECU
Why CAN FD Matters: A Leap Beyond Classical CAN
Why CAN FD Matters: A Leap Beyond Classical CAN
Classical CAN needs to evolve
In 1986, Bosch officially presented the CAN protocol at the Society of Automotive Engineers (SAE). In 1994, the CAN2.0 Specification was published. Since then, Classical CAN has become the de facto standard for in-vehicle communication networks. However, the emergence of electric vehicles—demanding increasingly complex, high-performance, and intelligent ECUs—has created the need for a more efficient and higher-bandwidth communication protocol within the automotive industry.
CAN FD Introduced
Bosch officially introduced CAN FD (Flexible Data-Rate), an enhanced version of the CAN protocol, in 2012. It was subsequently standardized by ISO in 2015 and is now in ISO 118981:2015.
Note: The original Bosch CAN FD (non-ISO) is incompatible with ISO CAN FD.
CAN FD Features
- Maximum data rate increased from 1 Mbps to 8 Mbps.
- Data payload increased from 8 bytes to 64 bytes.
- Backward compatibility with CAN 2.0.
-
Adds BRS (Bit-Rate Switch) bit for balancing reliability and speed:
Using low bitrate for safe arbitration and high bitrate for efficient data transfer. -
Adds ESI (Error State Indicator) bit:
Allows a CAN FD node to signal its error state directly in the data frame, improving network robustness and safety.
Why CAN FD?
- Higher data throughput
- Support for complex ECUs
- Improved Error Handling
- Backward Compatibility
- Lower protocol overhead per byte
CAN FD is designed to meet the bandwidth, reliability, and scalability demands of next-generation automotive and industrial systems, while remaining compatible with existing CAN infrastructure.
Applications
Electric Vehicles
Due to the growing number and complexity of ECUs in next-generation electric and hybrid vehicles, there is a critical need for faster, more efficient, secure, and highly reliable in-vehicle communication networks. Only systems equipped with CAN FD support are capable of fulfilling these requirements.
ECU Flashing
Vehicle software is becoming increasingly complex. Higher data rates are essential for efficient ECU flashing and parameter tuning operations.
What is ECU Flashing?
Watch here
Robotics
In industrial control and automation, systems depend on time-synchronized operations, e.g., multi-axis robotic arms. These systems often use CANopen and need several Process Data Objects (PDOs) from each controller to be transmitted in a tightly synchronized manner. By adopting CANopen FD, all necessary data can be packed into a single frame, improving transmission efficiency and timing precision.
ADAS and Safe Driving
As more passenger vehicles integrate ADAS features, the data traffic has grown substantially, creating a serious load on Classical CAN.
Heavy Vehicle / Commercial Vehicle
Currently, all heavy-duty and commercial vehicles are required to comply with the J1939 communication protocol, including buses, trucks, and large construction machinery. J1939 is a higher-layer protocol built on CAN, and most implementations only support the 250K and 500K bitrates defined in CAN 2.0. As vehicle systems become more complex, heavy-duty vehicles will migrate to CAN FD. The upcoming J1939 FD standard is expected to significantly enhance performance, especially for applications such as ADAS and electric buses.
Secure CAN - CAN FD authentication via SecOC
What is SecOC?
SecOC stands for Secure Onboard Communication, a key concept defined in the AUTOSAR standard.
SecOC is a security module designed to protect the authenticity and integrity of messages exchanged between Electronic Control Units (ECUs) within a vehicle. It helps:
- Prevent message tampering within the in-vehicle network (e.g., CAN, CAN FD, Ethernet)
- Detect unauthorized modifications
- Ensure that the data originates from a trusted ECU
