Consistent usage of simulations: from the function design for ADAS/AD up to the real control unit hardware
The approach for testing an ADAS/AD function is equivalent to the one taken for other control functions. In either case, the “system under test“ needs to be separated and embedded in a plausible simulation of the remaining system. At first, the function can be developed and tested independent of the target hardware. Depending on the state of development we speak of:
- Model-in-the-Loop (MiL) for function design,
- Software-in-the-Loop (SiL) for testing of electronic control unit (ECU) software without real hardware or
- Hardware-in-the-Loop (HiL), for executing the function as embedded software on an ECU.
Even before testing the function, simulation supports during system design and specification and also in failure mode and effects analyses (FMEA). The simulation tools CANoe and DYNA4 by Vector ensure a consistent deployment of simulation throughout the entire development process. This also holds true for the continuous testing during the implementation phase. Figure 1 illustrates this by means of the V-model.
