ASAM OSI for Closed-Loop System Tests of Assisted and Automated Driving
While most control functions can be interfaced on a signal-based approach, ADAS/AD functions typically require input from environment sensors – often in form of object lists. Although their content is widely comparable across different implementations, the structure of the complex data and the interpretation details differ significantly.
The ASAM definition of the Open Simulation Interface (OSI) allows for standardized, more reliable and re-usable interfacing between different tools and with the system under test. For this reason, ASAM OSI features have been integrated into CANoe and DYNA4. CANoe 15 contains the sample configuration "ADAS System Configuration (DYNA4)" to demonstrate the new features.
CANoe configuration with integrated DYNA4 models using the ASAM OSI object representation
Benefits of using OSI with CANoe and DYNA4
Increased test efficiency through a standardized object model Re-use tests from MIL over SIL to HIL by filling object lists independent of their source based on the OSI object model
Closed-Loop system tests of ADAS/AD functions with reliable interfaces Provide simulated sensor data from DYNA4 easily to CANoe and the system under test through the standardized OSI interface. Feed back actuations to the DYNA4 vehicle model to perform closed-loop system tests.
Flexible use of sensor models Use DYNA4‘s integrated sensor models or exchange them easily with other OSI-compliant sensor models.
MIL, SIL, HIL Seamless integration of your function in CANoe as Simulink model or FMU, C-Code, virtual ECU or real ECU hardware
Automated testing Thousands of virtual test drives triggered by automated test scripts in CANoe