Testing and Experimenting with V-ECUs

The Advantages

• Support of relevant automotive standards, such as XCP and ASAM XIL-API and usable as an additional platform, connectable by its IP address
• Access V-ECUs that run in VEOS using XCP over Ethernet based on A2L variable descriptions
• Use the same tooling for experiments and tests that you use for Hardware-in-the-Loop (HIL) systems
• Make use of scenario-based testing in your VEOS test setups

Preparing Hardware-in-the-Loop (HIL) Tests

The PC-based simulation platform VEOS has the same standard interfaces as a HIL simulator, so you can design and validate test scenarios and layouts for the HIL simulation in advance. In addition, you can develop, parameterize, and test plant models without using a HIL system.

Layouts that were previously developed for the HIL system can be reused and adapted to new requirements. Failures of the actual HIL tests due to faulty test sequences can be avoided. Layouts and tests are created once and can be reused across the different development stages to save both time and effort.

Frontloading HIL Tests

With the PC-based simulation platform VEOS, a V-ECU can be tested comprehensively on a PC in real HIL test scenarios, including automated test sequences. If necessary, two or more virtual ECUs can be combined with environment models to perform system integration tests. VEOS can simulate automated ECU test sequences on a PC that can be reused with a HIL system. Since you do not need additional hardware, you can easily distribute virtual ECUs. Frontloading tests this way lets you improve the quality of the ECU software even before starting any of the subsequent HIL tests.

Cluster Simulation

Using a PC-based simulation platform does not only offer the option to run test scenarios on a single PC, but on multiple execution modes simultaneously. This way, you can easily scale a test execution to your needs, and perform the huge amount of test runs needed, e.g., for autonomous driving.