Virtual ECUs Without AUTOSAR

Test software components early on your PC

The advantages: Virtual ECU tests with VEOS

• Integration tests on the developer's PC
• Use of established tools for debugging, code coverage, and parameter analysis
• Early integration tests without a hardware prototype
• Virtual ECU tests even without AUTOSAR

The challenge: Integration tests during the development process

The necessity for integrating new functions and validating their interaction with environment models at an early development stage is growing every day. The C code modules of functions that were developed in the C language had to be tested either individually or at a relatively late stage, when they were integrated on real ECU (electronic control unit) prototypes and tested with a HIL simulator. Potential errors were difficult to detect and correct. Until now.

The idea: Virtual ECUs

A more practical way of testing the interaction of the various functions as early as possible is using virtual ECUs for validation on a PC. Function developers can use dSPACE's PC-based simulation platform, VEOS, to test the interaction of their new functions on their PC. In addition, developers can use established methods such as debugging or code coverage to analyze errors and implement the required changes even during the development phase.

One example: Integration tests of TargetLink modules

dSPACE's production code generator, TargetLink, generates C code modules for a variety of functions. These modules can now be used in SystemDesk for the automated generation of virtual ECUs, including the appropriate task scheduling. In VEOS, developers can connect the virtual ECUs to a plant model to perform the first function tests on the PC.