For a better experience on, enable JavaScript in your browser. Thank you!

Model-in-the-Loop Simulation and Virtual Validation

As OEMs face the need to reduce the time to market for new developments, they strive to make their development and testing more efficient. One way to do this is to perform verification and validation tasks earlier in the development process. The concept of virtual validation gives them the tools to do just that.

Virtual validation is based on using virtual ECUs (V-ECUs) without real hardware prototypes on the PC-based simulation platform VEOS. This platform enables function and integration tests on the developer's PC to find and correct errors early in the process, thus saving time and iterations.

Generating Virtual ECUs

You can use two methods to create a V-ECU, depending on the starting point and project needs.

  • Function and software developers who work only with single components can create a suitable model with Simulink® or a V-ECU directly from TargetLink. The result is a basic V-ECU that contains only a specific part of the application layer of the ECU software. This basic V-ECU enables basic functional tests.
  • Software integrators who want to test a more complex network of functions can combine software components, functions, or non-AUTOSAR code from different sources in SystemDesk to create the V-ECU.

Integrating VEOS in Your Tool Chain

VEOS provides various interfaces that you can integrate into an existing tool chain. You can connect the software with any tool that supports the standard interfaces provided, such as XCP or XIL API. For measuring, stimulating, and calibrating, VEOS supports description files that are commonly used in the automotive industry:

  • To access plant models, VEOS uses the same TRC files that are also used for HIL simulation
  • To access V-ECUs, VEOS uses A2L files, which is the same format used for real ECUs

Additionally, VEOS can be automated, which means it is ideally suited for a continuous integration tool chain. Using VEOS as part of your tool chain lets you use the same configurations and layouts for your calibration and automation software for virtual validation as for your hardware-in-the-loop projects.

Real-Time-Independent Simulation

During the simulation run, VEOS ensures a deterministic simulation with a defined processing sequence. Simulation models can also be executed faster than real-time, provided the simulation models allow for such fast execution times, thus increasing the test throughput.

Even simulation models that are not real-time capable can be executed with VEOS. Models provided as Functional Mock-up Units (FMUs) can be used directly with other models.

Use Cases