CAN FD
CAN FD (Controller Area Network Flexible Data-Rate) is a data-communication protocol used for broadcasting sensor data and control information on 2 wire interconnections between different parts of electronic instrumentation and control system. This protocol is used in modern high performance vehicles.
CAN FD is an extension to the original CAN bus protocol that was specified in ISO 11898-1. CAN FD is the second generation of CAN protocol developed by Bosch.[1] The basic idea to overclock part of the frame and to oversize the payload dates back to 1999.[2] Developed in 2011 and released in 2012 by Bosch, CAN FD[3] was developed to meet the need to increase the data transfer rate up to 5 times faster and with larger frame/message sizes for use in modern automotive Electronic Control Units.
As in the classical CAN, CAN FD protocol is designed to reliably transmit and receive sensor data, control commands and to detect data errors between electronic sensor devices, controllers and microcontrollers. Although CAN FD was primarily designed for use in high performance vehicle ECUs, the pervasiveness of classical CAN in the different industries will[citation needed] lead into inclusion of this improved data-communication protocol in a variety of other applications as well, such as in electronic systems used in robotics, defense, industrial automation, underwater vehicles, medical equipment, avionics, down-hole drilling sensors, etc.
CAN FD versus classical CAN
[edit]The primary difference between the classical CAN (Controller Area Network) and CAN FD is the Flexible Data (FD). Using CAN FD, Electronic Control Units (ECUs) are enabled to dynamically switch between different data rates and longer or shorter messages. Faster data speed and more data capacity enhancements results in several system operational advantages compared to classical CAN. Commands issued by the executing ECU software reach the output controller much faster. CAN FD is typically used in high performance ECUs of modern vehicles. A modern vehicle can have more than 70 ECUs that use CAN FD to exchange information over the CAN bus when the engine is running or when the vehicle is moving.
On a CAN bus, a frame is the basic unit of messaging. For a classic CAN bus, a frame consists of an 11-bit identifier along with an 8-byte message payload. For CAN FD, a frame is labeled with a 29-bit identifier and carries a 64-byte message payload. Frames with 11-bit identifiers are said to be in FD Base Frame Format (FDBF) and frames with 29-bit identifiers are referred to as FD Extended Frame Format (FEFF). While payload data rates of 5-8 Mbit/s are possible in CAN FD, overall data transfer rates depend on the total length of the bus network and the transceivers used to generate and detect bus signals. Additionally, arbitration data rates are limited to 1 Mbit/s to maintain compatibility with classical CAN devices. The CAN FD protocol specification provides improved error detection[4] in received CAN messages and enhanced flexibility of data transfer speeds to account for differences in sensor polling rates. The CAN bus consists of a shared pair of wires onto which electronic sensors, controller units, and ECUs are connected and is used to exchange information between units operating periodically or on demand. The total number of units connected, the length of the CAN bus wires, and additional electromagnetic factors determine the fastest data transfer rate possible for a given CAN bus. All versions of the CAN protocol are designed with robust collision resolution that depends on signal propagation time, network topology, and the number of units on the bus. To minimize message collision and reduce costly error correction, many CAN bus configurations may limit their data transfer rate well below the bus's theoretical maximum speed.
CAN-FD bus load that was developed by "De Andrade's" equation based on Tindel's equation.[1][5][6]
β = τ/ω (1) (β = Busload), (τ = time of slow bits plus faster bits), ω (time in seconds of measurement). τ = Ts + Tf (2)
CAN-FD protocol defines five different error detection mechanisms: Two of them work at the bit level, and the other three at the message level. They are:
- (1) Bit Monitoring, - (2) Bit Stuffing, - (3) Frame Check, - (4) Acknowledgement Check and - (5) Cyclic Redundancy Check. There are two options of CRC which should be denoted as for CRC length of 17 (Data Length 0-16 bytes) or CRC length of 21 bits (Data Length 17–64) bytes.
Ts = ([(SOF+ID+r1+IDE+EDL+r0+BRS/2+CRCdel/2)* 1,2]+ACK+DEL+EOF+IFS)/t_x (3)
Tf = ([(D〗_f+BRS/2+ESI+DLC+CRCdel/2)*1,2]+〖CRC〗_17+5)/t_y (4)
where SOF (Start of Frame) + ID (Identifier) + r1 (reserved bit 1) + IDE + EDL(Extended Data Length) + r0(reserved bit 0) + BRS/2 (Bit Rate Switch) + CRCdel/2 (CRC delimiter)= 17 bits; 1.25 is the factor of the worst case bit stuffing,[7] which means the computation shall be increased by 25%. It is considered BRS and CRCdel divided by 2, because they are exactly in the shift of bit rate transition. The ACK (Acknowledge) + DEL (Delimiter) + EOF (End-of-Frame) + IFS (Interframe Spacing) = 12 bits without bit stuffing. The CAN-FD payload size may be 0 to 8, 12, 16, 20, 24, 32, 48, 64 Bytes. t_X is the transmission bandwidth for the message header (up to 1 Mbit/s).
- For data < 16 Bytes
β = ( (SOF+ID+r1+IDE+EDL+r0+BRS/2+CRCdel/2 * 1,25)+ACK+DEL+EOF+IFS)/t_x + (〖[(D〗_f+BRS/2+ESI+DLC+CRCdel/2)*1,25]+〖CRC〗_17+5)/t_y)/ω (5)
- For data >= 16 Bytes
β = ( (SOF+ID+r1+IDE+EDL+r0+BRS/2+CRCdel/2 * 1,25)+ACK+DEL+EOF+IFS)/t_x + (〖[(D〗_f+BRS/2+ESI+DLC+CRCdel/2 )*1,25]+〖CRC〗_21+6)/t_y )/ω (6)
CAN FD also has decreased the number of undetected errors through increases in the performance of the CRC-algorithm.[8] In addition, CAN FD is compatible with existing CAN 2.0 networks, allowing the new protocol to function on the same network as classical CAN.[9] CAN FD bit rate can be up to 8 Mbit/s with the right CAN SIC (Signal Improvement Capability) Transceiver and so up to 8 times faster than classical CAN with 1 Mbit/s data phase.
Due to higher communication speed, CAN FD constraints are tougher in terms of line parasitic capacitance. Therefore, all components on the line have seen their "capacitance" budget reduced compared to regular CAN bus. That is the reason why semiconductor suppliers have released new components approved by car makers. This approval reflects the need for interoperability between all CAN FD systems. Indeed, selected ESD protection components are compatible with all transceivers (CAN or CAN FD) and withstand ISO7637-3.[10]
Despite a higher stand-off voltage (37 V), devices for truck applications must also comply with the low capacitance requirement (3.5 pF).[11]
Data frame
[edit]The data frame used for actual data transmission have two message formats:
- Base frame format: with 11 identifier bits
- Extended frame format: with 29 identifier bits
The frame format is as follows: The bit values are described for CAN-LO signal.
| Field name | Length (bits) | Purpose |
|---|---|---|
| Start-of-frame | 1 | Denotes the start of frame transmission |
| Identifier | 11 | A (unique) identifier which also represents the message priority |
| Stuff bit | 1 | A bit of the opposite polarity to maintain synchronisation; see CAN Bus#Bit stuffing |
| Remote Request Substitution (RRS) | 1 | |
| Identifier extension bit (IDE) | 1 | |
| FD Format Indicator (FDF) | 1 | Must be recessive(1) for CAN FD frames and dominant (0) for classic CAN. |
| Reserved bit in FD frames (res) | 1 | |
| Bit Rate Switch (BRS) | 1 | |
| Error State Indicator (ESI) | 1 | |
| Data length code (DLC) | 4 | Number of bytes of data (0–64 bytes)[a] |
| Data field | 0–512 (0-64 bytes) | Data to be transmitted (length in bytes dictated by DLC field) |
| CRC | 15 | Cyclic redundancy check |
| CRC delimiter | 1 | Must be recessive (1) |
| ACK slot | 1 | Transmitter sends recessive (1) and any receiver can assert a dominant (0) |
| ACK delimiter | 1 | Must be recessive (1) |
| End-of-frame (EOF) | 7 | Must be recessive (1) |
| Inter-frame spacing (IFS) | 3 | Must be recessive (1) |
- ^ The values 0-8 indicate 0-8 bytes like classic CAN. The values 9-15 are translated to a value between 12-64 which is the actual length of the data field: 9→12 10→16 11→20 12→24 13→32 14→48 15→64
CAN & CAN FD TP Headers
[edit]| 7 .. 4 (byte 0) | 3 .. 0 (byte 0) | 15 .. 8 (byte 1) | 23..16 (byte 2) | (byte 3) | (byte 4) | (byte 5) | (byte 6) | .... | ||
|---|---|---|---|---|---|---|---|---|---|---|
| Single Frame (SF) | according to CAN | 0 | size (1..7) | Data | ||||||
| CAN-FD specific | 0 | size (0..62) | Data | |||||||
| First Frame (FF) | according to CAN | 1 | size (8..4095) | Data | ||||||
| CAN-FD specific | 0 | 0 | size (4bytes ~4 GB) | Data | ||||||
| Consecutive Frame (CF) | according to CAN | 2 | index (0..15) | Data | ||||||
| Flow Control Frame (FC) | according to CAN | 3 | FC flag (0,1,2) | Block size | ST | Unused | ||||
The above table explains the transfer protocol defined for CAN + CANFD, based on ISO 15765-2 (ISO-TP), used for sending packets of data longer than what fits in a CAN frame.
- if the first byte is 0x00, then it's a CAN-FD SF, and the second byte specifies the size of the data.
- if the first byte is 0x01-0x07, then it's a normal CAN SF with this byte indicating the size of 1-7 bytes data.
- if the first 2 bytes are 0x1000, then it's a CAN-FD FF, and the following 4 bytes specifies the size of data in high byte first order. This virtually enables to send ~4 GB (approx.) data in CAN FD.
- if the first 2 bytes are 0x1008-0x1FFF, then it's a normal CAN FF with a size of 0x008-0xFFF.
CAN Transceiver
[edit]CAN FD can use Transceiver for classical CAN and CAN FD. Additionally there are new CAN SiC (Signal improvement Capability) Transceiver with 5 to 8 Mbit/s data rate.[12]
CAN FD in action
[edit]In 2017, CAN FD was predicted to be used in most vehicles by 2019–2020.[13]
CAN FD supporters
[edit]Some of the companies behind the new standard include STMicroelectronics, Infineon,[14] NXP, Texas Instruments, Kvaser, Daimler and GM.
CAN FD forms a basic data link layer in some higher Layer protocols like CANopen as CANopen FD and J1939 and supported by different companies with protocol stacks.
CAN XL
[edit]CAN XL is the 3rd version of the CAN data link layer after classical CAN and CAN FD. CAN FD is compatible to CAN XL.
References
[edit]- ^ a b "CAN in Automation (CiA): CAN FD - The basic idea". www.can-cia.org. Archived from the original on 2017-02-02. Retrieved 2017-01-25.
- ^ Cena, G.; Valenzano, A. (1999). "Overclocking of controller area networks". Electronics Letters. 35 (22): 1923. Bibcode:1999ElL....35.1923C. doi:10.1049/el:19991289.
- ^ "Bosch CAN FD Specification Version 1.0 (released April 17th, 2012)" (PDF). Archived from the original (PDF) on 2015-12-11. Retrieved 2019-01-02.
- ^ "CAN FD and the CRC issue" (PDF).
- ^ de Andrade, R.; Hodel, K. N.; Justo, J. F.; Laganá, A. M.; Santos, M. M.; Gu, Z. (2018). "Analytical and Experimental Performance Evaluations of CAN-FD Bus". IEEE Access. 6: 21287–21295. Bibcode:2018IEEEA...621287D. doi:10.1109/ACCESS.2018.2826522..
- ^ De Andrade, Ricardo (2014). Sistemas de comunicação CAN FD: modelamento por software e análise temporal (PDF) (Master's thesis). Universidade de São Paulo.
- ^ "can: length: add definitions for frame lengths in bits".
- ^ "Archived copy" (PDF). Archived from the original (PDF) on 2019-04-16. Retrieved 2017-01-25.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ "High speed CAN FD bus is coming to cars, says Microchip". Electronics Weekly. 2015-10-26. Retrieved 2017-01-26.
- ^ "CAN bus ESD protection for 12V systems". STMicroelectronics-ESDCAN03-2BWY.
- ^ "CAN bus ESD protection for 24V systems". STMicroelectronics-ESDCAN05-2BWY.
- ^ "CAN Signal Improvement". www.nxp.xom. Archived from the original on 2020-08-04. Retrieved February 2, 2022.
- ^ "CAN 2020: The future of CAN technology". www.can-cia.org. Retrieved 2017-01-26.
- ^ Kelling, Ursula (April 2014). "Infineon Microcontrollers" (PDF). CAN Newsletter Online. Retrieved June 2, 2019.
External links
[edit]- Comparing CAN FD with Classical CAN
- CAN FD: From Theory to Practice
- CAN Bus Protection : Protect What Protects You
- Linux and ISO 15765-2 with CAN FD - Details of how (payload) data length differs between CAN and CANFD
- Linux and ISO 15765-2 with CAN FD 15th international CAN Conference 2015
- CAN FD Explained