Automotive CAN IVN stack
CAN protocol is the backbone of the In Vehicle Network (IVN) Communications and the messages flowing around the vehicle are typically represented using Vector DBC file format in form of messages and signals. It is important for each transmitting ECU in the system to stick to the predefined format and receiver able to decode it at high speeds.
With rich experience in working on the same for both industrial and automotive applications, Embien offers ISO11898 compatible implementation of automotive CAN IVN stack. Designed for performance, the stack can handle even the high loads with ease. Embien also offers its Flint CAN IVN Configurator tool to import DBC files and generate configuration files that can be quickly integrated to our stack and signals received without any effort.
How our stack handles In-Vehicle Network data easily?
Modular
Scalable designs allows adding necessary features only
Portable
Small footprint design customized for all major MCU families
High Throughput
Minimal software handling to offer low latency
Optimal Filtering
Use of hardware filtering and intelligent software algorithms
Why RAPIDSEA Automotive CAN IVN Stack ?
Our RAPIDSEA automotive CAN IVN stack leverages the hardware filtering mechanisms available in the underlying MCU/SoC and supports both 11-bit and 29-bit identifier format. It can be configured for any baud rate and capable of handling CAN bus errors. The stack is proven across multiple devices such as
- Renesas RL78
- Renesas RH850
- NXP S32K
- Infineon Traveo S6J3360
- NXP iMxRT devices
Speak to our technical team to understand how it can be made available in your customer platform.In addition to the In-Vehicle Network stack, RAPIDSEA also has the following automotive protocol support that can be used on top of this one
- ISO15765 DoCAN/CAN-TP stack
- ISO14229 UDS Stack
One-step DBC file format to Data acquisition
Flint CAN IVN Configurator offers no-code approach for generating configuration files for the CAN Stack. The user can simply import the DBC file and select the signals to be extracted along with optional Timeout information. Once done, the C files generated can be built with our automotive CAN IVN stack and callbacks are invoked on reception of the signals or timeouts. Other customization like filters, mailboxes etc are also available.
Our automotive CAN stack and configurator is compatible with dbc file format output generated from standard tools such as Elektrobit Tresos, Davinci Autosar, Simulink Autosar and validated with Vector CAN analyzers and Peak PCAN USB adapters.