Validating ECU functions in realistic test scenarios during the early stages of development is becoming a more common practice. Simple unit tests do not provide enough coverage anymore, especially for safety-critical driver assistance functions which, by nature, are networked with many other systems. In cases like this, function developers must test the functions' interaction with other control algorithms closed-loop with complex environment models.
The pragmatic approach takes the environment simulation models that already exist for ECU testing and reuses them on the developer PC. dSPACE VEOS is the bridge between these two worlds. It lets function developers perform virtual tests of functions whenever they want to so that they can easily test many different environment scenarios. This holds the number of real test drives at an affordable level. It also makes reproducing virtual test drives much easier, which is useful for checking a corrected function. VEOS also includes established error analysis methods such as debugging and code coverage, which are not possible in real test drives. If function developers do not have access to the environment models, they can use the dSPACE models that cover many ADAS areas.
Performing automated tests of intersection assistance functions on a hardware-in-the-loop simulator involves constructing many test scenarios that describe the exact traffic situations (the course of the road, number of traffic participants, roadside features, etc.) to test all the participating ECUs in detail. With VEOS, function developers can take the relevant function algorithms that were developed in Simulink or AUTOSAR and simulate them in interaction with these environment models. VEOS provides them the same features for visualization, simulation control, and automated tests as a HIL simulator.