The Vector CANbedded environment consists of a number of adaptive source code components that cover the basic communication requirements in automotive applications.
Reusable Software
Distributed applications in automotive networks require the same protocol stack in all control units involved. This protocol stack is provided by the CANbedded software components and is integrated into various applications. This results in:
- Guaranteed CAN bus compatibility
- Reduced development costs for implementation and testing
- Usability of low-cost hardware based on highly optimized software algorithms
- Reliable software based on wide usage in various control units.
International Standards and Software Architecture
Most functional requirements are based on international standards. Vector makes CANbedded available for a wide range of tasks, based on the following specifications:
- ISO: International Organisation for Standardization
- OSEK: Open Systems and their interfaces for Automotive Electronics
- ASAM: Work Group for Standardization of Application Systems
- AUTOSAR: Automotive Open System Architecture
Conformance with the standards has been verified in many projects with international automobile manufacturers.
Features and Advantages:
The Vector embedded software components provide a wide range of features that are indispensable for control units in automotive applications and which integrate Vector's experience in the areas of embedded software and CAN communication:
- Standard components that are based on generic code and are 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. This results in standardized CANbedded software components that are independent of the functionality of the target node.
Functions
The basic concept behind Vector's implementation is to provide an interface that is simple to use and is well adapted to all applications. The standardized interface includes:
- Basic initialization of hardware/software
- Cyclical call of the corresponding state machine (if timing aspects are necessary)
- Functions needed to change the internal state of the CANbedded software components.
Asynchronous events resulting from CAN bus activities such as receiving messages, wake-up functions or different error states are forwarded to the application via callback functions.
Some applications must run multiple CAN buses. For such applications, the CAN Driver, and usually the higher CANbedded software components, must provide a multi-channel interface. Therefore, all Vector software components are available in a multi-channel version.
During the integration of CANbedded software components, internal errors and unexpected states result in application notification via appropriate user error functions.
Using existing run time and memory resources economically results in inexpensive controllers. Due to the high number of pieces, this is one of the basic requirements for control units in the automotive industry.
The illustration below shows the software structure of a typical automotive control unit with the application section, the run time environment, for example an OSEK/VDX operating system (osCAN) and the CANbedded environment, i.e. the software components together with the generating tool, based on the CAN controller hardware. Beside of this standardized feature set, Vector provides customer-specific solutions.
Please click on one of the boxes to get further information: 