- Overview
- 1. Introduction
- 2. CAN Communication
- 3. CAN Framing
- 4. CAN Bus Access
- 5. CAN Data Protection
-
6. CAN FD
- Motivation
- Advantages and Consequences
- Details of a CAN FD Frame
- Distinguishing CAN from CAN FD Frames
- Compatibility of CAN and CAN FD Controllers
- Accelerated Transmission
- Indicating too many Errors
- Length of the Data Field
- More Data with the same Security
- Changed Rules for Bit Stuffing and CRC Calculation
Standard and extended format
Just like traditional CAN also CAN FD knows two types of data frame formats: the standard frame with 11 bit identifier and the extended frame with 29 bit identifier. This guarantees that add-on protocols to CAN, such as CANopen and SAE J1939, can be used with some adaptions as add-ons to CAN FD as well.
No CAN FD remote frame
CAN FD does not define an individual format for Remote Frames. If looked closely this doesn’t mean any limitation. Remote Frames have no data field which renders an increased transmission rate useless. Consequently the CAN FD protocol allows for CAN FD frames to be requested by classical CAN Remote Frames.
Last modified: Wednesday, 11 April 2018, 1:46 PM