ContactWhat is Communication?
Exchange of information between different ECUs (Electronic Control Units) connected via a certain Bus System (CAN, LIN, FlexRay...).
Where does communication take place?
There are different networks in a modern vehicle. The networks are built-up of ECUs. The border from one network to another is realizes by a so-called Gateway. This is an ECU that speaks the language of both (or more) networks (e.g. CAN and LIN).
How does communication work?
All ECUs use a common data base (DBC, LDF, FIBEX, ...), the communication matrix. This matrix defines the words of the language (messges, signals, ...) and all communication partners (ECUs in the network).
How is a typical ECU built-up
From a very abstract point of view an ECU is built-up of a functional part, the application itself and a part that handles the communication aspects of the ECU.
The functional part realizes the function of the ECU, e.g. being a climate control ECU or a door ECU.
One for all
All ECUs should communicate with each other. All ECUs in a bus system use the same communication matrix. The consequence is that they all use the same software components for the communication, too.
CANbedded - Vector's Standard Components
The Vector embedded software components - CANbedded for short - provide a wide range of features that are indispensable for control units in automotive applications and integrate Vector's experience in the areas of embedded software and CAN communication.
The standard components are based on generic code and scalable for application-specific adaptations.
- Low ROM and RAM resource requirements
- Run time efficient
- Automatic generation of parameter settings and configuration information
- Simple integration into application software
- Compatibility with Vector's analysis, simulation and calibration tools
- Compatibility with the requirements of automobile manufacturers.
The source code is adjusted by parameters and configuration data that are determined offline with a tool, the configuration tool. This results in standardized CANbedded software components that are independent of the functionality of the target node.