CAN Stack: A Software Solution for In-vehicle Network Communication
Our Business Engagement Model: What are the Value Adds?
Our CAN stack (ISO-11898) is a Ready-to-integrate and Production Grade communication stack. This software solution is ideal for passenger vehicle applications.
We offer this CAN stack under a one-time licensing fee model. This engagement model has proved to be a great value-add for our customers across US, India, China and Europe.
The following are some of the benefits of our One-Time Licensing Fee Model:
- You get access to the source code of the CAN Stack.
- You can become the owner of the IP rights.
- By owning the IP rights, your organization can deploy this CAN stack in multiple production programs.
CAN Stack: Details of the Software Architecture
CAN stack Integration, Configuration and Testing Services
Extensive experience in successful integration and configuration of CAN stack software, by both manual or tool based approach.
We have designed a Proprietary tool for CAN Stack Configuration. This is a PC based tool named as Auto-code Generator Tool. This tool has helped our customers to reduce 3-4 weeks of turn-around time.
Our team has also successfully integrated CAN stack for Automotive Applications such as:
- Seating ECU
- Body Control Module
- Telematics ECU
- Engine Control Unit
Development and Integration of CAN Driver:
Support for all Microcontroller Families (Renesas, TI, Fujitsu etc.)
Supports 29 and 11 bit identifiers
Hardware Filtering (Acceptance Filtering) of messages and signals
Support for standard baud rates of 125kbps, 250 kbps and 500 kbps
Leverage Reusable components of device drivers to reduce time-to-market
Support for driver integration across production programs
CAN Stack Support and Maintenance Services:
Creation of High Level Design documents (HLDD) and Low-Level Documents (LLD)
CAN Conformance Testing of Data Link Layer with Vector tools like CAN Stress
Design of Integration and Functional Test Plans
Support for MISRA compliance report creation
End-to-end Testing Services ( Unit, Integration and Functional Testing)
Design and Development of PC Based Auto Code Generator Tool:
DBC to configuration file generator tool
Auto Generated and MISRA C compliant code
Code generated in fraction of seconds
PC based (Windows) tool
Easy to remove Tx and Rx messages from the CAN Matrix
Development and Configuration of CAN IF Layer:
Ready-to-deploy layer; only configuration is needed
Tx and Rx message configuration from the DBC file (CAN Matrix)
Support for Tool based/ manual configuration of CAN IF layer
Configurable Skeleton code (.C, .F, cgf.c and cgf.h) of CAN IF layer is also available
Low level and high level documents are provided
Support for software level message filtering
Signal and message extraction provided as a default feature
Integration and Configuration of CAN TP and Network Management Layer:
Message and mode monitoring
Checksum strategies to ensure message validation
Integration of UDS stack over CAN TP
Customizations as per your business requirements
Built-in error handling feature of CAN BUS off
Ready-to-deploy CAN TP layer for reduced turnaround time
Meet Our Automotive Leaders
CAN Software Stack Factsheet:
This CAN protocol stack solution factsheet is designed to provide you all the necessary information related to the technical specifications like memory requirement, and integration & support services etc.
Download this CAN protocol stack Factsheet for details about:
- CAN software stack business model
- Advantages of one-time licensing fee engagement model
- CAN stack solution package
- Value-add features of our pre-tested and ready-to-integrate CAN software stack solution
- Use-cases and applications of CAN protocol stack in automotive industry
Please refer to CAN software stack FAQ’s for more details.
FAQs About CAN Stack Solution
Ans. The layered technology architecture of our CAN stack solution is as followed:
- Low-level drivers (CAN, MCU, EEP, Timer)
- CAN Stack (CAN NM and CAN IF)
- ISO TP Layer (ISO15765)
- UDS stack
- Application Layer
Also included are:
- Bootloader Application Layer
- UDS Based Bootloader Software
- CAN Device Drivers support 11&29 bit identifiers
- In-built Interrupt Based data handling
- Data Queuing feature
- APIs for Tx and Rx messages
- CAN Interface Layer w.r.t CAN Matrix
- Supports Signal Extraction
- Supports S/W filtering
- CAN Network Management
- Message and node monitoring
- Sleep/Wake up functionalities
Ans. CAN Stack driver is the only part of the stack that is dependent on the hardware platform. Rest of the software layers, like CAN IF and CAN NM are hardware agnostic.
It implies that the CAN driver will need to be developed based on the microcontroller used in the project.
Our automotive team has expertise of developing device drivers for all major MCU families including Renesas, Fujitsu, TI and others.
Ans. Our experience spans across several automotive ECUs, that have been powered by our CAN stack. A few of the ECUs for which we have successfully deployed CAN stack are
- Seating control ECU,
- Engine Control Unit and
- HVAC systems
Ans. Yes. Our service level agreement for CAN Stack clearly documents the fact that we will provide all the necessary configuration and integration services, along with CAN stack license.
Tool-level integration for low-level drivers as well as application level, will also be a part of our SLA.
Ans. We follow a well-defined test-plan for Our CAN software solution. We use standard tools for the following testing procedures:
- Unit level Testing
- Functional Testing
- Data Link Layer Compliance testing using vector tools
Ans. Depending on the size of the CAN Matrix file, we use manual method or an automation tool for conversion from DBC file to configuration file code.
Our proprietary PC based auto-code generator tool, is capable of generating configuration files instantly as compared to manual method that would take 2-3 weeks.
As a customer, you have the freedom to choose between the manual method and the tool-based method.
Ans. Yes, by the virtue of its design, the CAN stack solution is modular in nature. Our coding guidelines ensure that no global variables are exchanged between different source files.
Each functionality is invoked using an API. The modular nature also makes our stack lightweight in size.