CAN FD protocol supports more than 8 bytes of data transfer within vehicle ECU network. Leverage our ready-to-deploy CAN FD stack & bootloader to migrate from CAN to CAN FD protocol

1. Embitel Technologies International presence:
CAN FD Stack Integration Services

2. Embitel Technologies International presence:
The modern vehicle manufacturers stipulate transmission of larger amounts of data at optimum rates across the vehicle
network. And The Classical CAN BUS protocol supports the transfer of only up to 8 bytes of data.
Hence, there was a need for next generation CAN protocol. CAN FD (CAN with flexible data rate) vehicle network protocol
has been designed to support up to 64 bytes of data transfer.
CAN FD stack Integration, Configuration, and Testing services:
The CAN FD drivers or firmware, an interface layer and a network management layer have been designed, developed and
tested according to ISO 11898 standard.
• End-user Application Analysis:
Detailed analysis of the user application/vehicle application layer to understand the extent of customizations needed for the
CAN Network layer
• CAN FD Stack Integration Services:
Integration and configuration of the CAN software stack with three software layer services. The software stack solution
comprises of CAN FD drivers, Interface layer, and Network Management layer.
Need for CAN FD – a next generation vehicle network protocol

3. Embitel Technologies International presence:
• CAN FD Bootloader Services:
The CAN FD Bootloader development to support re-programming of the automotive ECU.Testing services for the CAN FD
Bootloader as per the ISO standards.
• Conformance Testing Services:
Testing and validation of the pre-defined test cases as per the ISO 16845 standards. Integration testing of the end-user
application.
The software layers of the CAN FD stack support following functionalities:
• CAN FD Driver: This layer is created to enable the physical layer interaction with the higher layers of the stack. It helps
in the abstraction of the transmitting and receiving of data from the ECU hardware
• CAN FD Interface Layer: This layer helps in the routing of the Bus channel regardless of its location. CAN FD Interface
help in the abstraction of the driver from the higher layers because the higher application layers only interact with the
channels and not the ECUs. CAN FD interface layer also ensure hardware independence thus ensuring reusability of this
stack across platforms

4. Embitel Technologies International presence:
.
• CAN FD Network Layer: The network BUS transitions between various modes of operation cycles namely bus-off or
sleep mode, active and inactive mode.Network management layer sends a notification to the application layer about
the status of the CAN BUS to the vehicle application layer.
The Tx and Rx messages between the NM layer and the user application are configured to achieve the same.
The architecture of CAN FD software stack
We have designed and developed a CAN FD software stack which is
similar to CAN bus. The CAN FD stack can be integrated with your
applications to help reduce time-to-market for the product
development.
Our pre-packaged and off the shelf stack is effective in saving the
development time and helps the OEMs to focus on product
development.

5. Embitel Technologies International presence:
Following diagram is the graphical comparison between the frame architecture of Classical CAN and CAN FD protocol
Classical CAN v/s CAN FD frame architecture

6. Embitel Technologies International presence:
CAN FD protocol supports increased bandwidth for data communication across the automotive ECUs within a vehicle
network. The following are some of the benefits of using CAN FD protocol over the legacy CAN-BUS protocol.
• Improved Data Rate: The Classical CAN protocol allows the bandwidth of 1 Mbit/s whereas CAN FD protocol supports
bandwidth more than 8 Mbit/s.
• Support for larger payloads ( data):
• CAN FD supports up to 64 bytes of data field as compared to Classical CAN that supports up to 8 bytes of data
• Due to high bandwidth capacity and larger payload (data field), CAN FD stack doesn’t require transport layer
protocol for enabling the in-vehicle network communication among ECUs
• During ECU re-programming, the speed of data transmission (data of sizes larger than 8 bytes) is significantly
higher in a CAN FD network as compared to classical CAN.
• Thus the end-of-line software upgrade can be done more efficiently, that translates into time and cost savings
What are the advantages of CAN FD over CAN?

7. Embitel Technologies International presence:
• Improve Real-time data transfer: During in-vehicle ECU communications, a single message (or data signal) is transferred
as multiple independent packets. Since CAN FD supports 8 times more data volume than Classical CAN, the transfer
rates are faster and signal fidelity is better due to simpler packet management All these factors play a significant role
while developing real-time data transfer applications
• Data security: The data security parameter in CAN FD remains the same as that of the classical CAN despite the
increased data packet size.This is achieved by using longer CRC check keys with adapted algorithms.
• Backward compatibility: The CAN FD controllers can be used as classical CAN nodes as well. Hence the legacy network
nodes can be gradually replaced with CAN FD-capable devices. When the entire network becomes CAN FD complaint,
then the advantages of this next generation CAN are realized to the fullest extent.
Contact us today for CAN FD Software ! Mail us at sales@embitel.com