Parking assistants are often included as standard equipment in modern cars − convenient, smart, and seemingly flawless. But what happens when the technology fails? A scratch on the paintwork is harmless, but an incorrectly calculated angle can quickly lead to expensive damage or even pose a danger to pedestrians. The truth is: convenience alone is not enough. These systems must perform reliably under all conditions. That is where the real challenge emerges: How do you test a function that must account for countless variables in the complexity of the real world? Traditional methods are reaching their limits. One answer is vehicle-in-the-loop (VIL) testing − a validation method that combines reality and simulation, setting new standards. UN Regulations such as UN ECE R171 (“DCAS”) even propose using simulation for virtual homologation. Time to take a closer look.

Things to Consider

Validating automated and autonomous parking systems requires some critical aspects to be addressed. From safety mechanisms to user experience, the following aspects need to be kept in mind:

  1. Fail-safe strategies: The vehicle must immediately switch to a safe state in the event of errors (e.g., emergency braking). 
  2. Testing in complex scenarios, such as tight parking spaces, moving obstacles, poor visibility conditions, and different road markings. 
  3. Adaptive algorithms: AI-supported systems that learn from environmental conditions and can predict movements of other vehicles. 
  4. Cybersecurity & safety: protection against manipulation and compliance with standards, such as ISO 26262 and UNECE WP.29. 
  5. User-friendliness: intuitive activation, clear feedback signals, and easy cancellation options.

Ready to Bring Automated Parking Testing to the Next Level?

End-to-End Validation Across All Test Levels: SIL, HIL, and VIL

Best practice is a combination of simulation methods such as SIL & HIL testing with real-world testing. Introducing the vehicle-in-the-loop (VIL) testing method enables road testing to be accelerated by reusing tools from SIL and HIL simulations on the actual vehicle.

To validate automated parking assist (APA), ultrasonic sensors are stimulated on a real vehicle in dynamic driving mode. During slow driving, e.g., during parking maneuvers, objects are defined in any virtual scenario, and object distances are calculated at run time in the simulation environment. These distances are the target values for the ultrasonic stimulators of the ultrasonic sensors installed on the vehicle. To validate the parking system's performance, the echo signal can be generated in real time. In addition to the time of flight, parameters such as amplitude, frequency, and number of signal oscillations can be adjusted. 

Consequently, simulated environmental data can be varied as desired and validated on the actual vehicle. Critical environments, such as parking garages with tight parking spaces, poles, and other types of barriers, can be simulated again and again. Variations in surfaces reflectivity can also be included in the tests. 

Finally, feedback to the vehicle’s real human-machine interface (HMI) can also be validated based on the simulated environment.
 

How Your Validation Task Benefits from VIL Testing

Vehicle-in-the-loop (VIL) testing can significantly improve your validation task for an automated parking assistant. Here are the key benefits and considerations.

Realistic tests without complete vehicle integration

VIL combines real vehicle hardware (e.g., control units, sensors) with a virtual environment. This allows you to test the behavior of the parking assistant under realistic conditions without having to recreate every scenario on a test track.

High flexibility for scenarios

You can simulate complex parking environments (e.g., narrow parking spaces, obstacles, different floor coverings) that are difficult to reproduce. Variations such as different vehicle types, weather conditions, or sensor errors can easily be adjusted.

Cost and time savings

VIL testing makes it possible to reduce the time spent on real-world test drives. Consequently, software updates can be validated much faster. 

Integration of safety and edge case tests

Critical scenarios (e.g., pedestrians or vehicles that appear suddenly) can be safely simulated, reducing possible risks that might occur during real-world tests.
 

Comparing Real-World Testing vs. VIL

Criterion Real-World Testing Vehicle-in-the-Loop (VIL)
Degree of Realism Very high (real environment) High (real hardware + virtual environment)
Scenario Flexibility Low (complex setup required) High (complex virtual scenarios possible)
Cost Very high (test vehicles, tracks) Low to medium (simulation + vehicle)
Time Effort High (planning, execution) Low (quick scenario changes)
Safety Risk High (critical scenarios in real world) Very low (critical scenarios virtual)
Sensor Realism Perfect (real sensors) High (real sensors on vehicle)
Edge Case Testing Hard to realize Excellent
Software Update Testing Slow (vehicle required) Fast

 

Vehicle-in-the-Loop Requirements and Setup

The most important requirements for the validation of parking assistants in a VIL test system
  • Physically correct models of the vehicles, sensors, and environment.
  • Simulation of typical parking scenarios like narrow gaps, curbs, and critical scenarios like highly reflective surfaces or unusual obstacles.
  • Minimal latency between virtual environment and hardware.
  • Precise synchronization between vehicle inertial measurement unit (IMU) and simulation.
  • Closed-loop operation for dynamic scenarios.
  • Error injection (e.g., noise, occluded objects) for robustness testing.
  • Real-time analysis of fusion results.
  • Easy parameter variation to generate a big variety of test cases.
  • Logging and replay function for error analysis.
     

VIL Setup and Components

Device under test (DUT)

The DUT is the automatic parking assistance system installed on a real vehicle – a vehicle prepared for over-the-air-testing. 

Over-the-Air Sensor Stimulation

Over-the-Air Sensor Stimulation

For VIL testing, only non-invasive test methods are considered, meaning there is no need to tap into the communication line between the real sensor and the ECU. Among others, manipulation of time of flight, frequency, amplitude, and pulse count is required. To achieve this, special adapters comprising ultrasound transducers, housing, and special insulation to cancel environmental disturbances must be attached to the real vehicle. 

Vehicle positioning and motion sensors (GNSS & IMU)

In this setup, the device under test (DUT)—in this case, the automatic parking assistance system—makes decisions on steering, braking, or throttle commands based on its perception of the environment. The key is to measure vehicle position, orientation, and motion accurately in real time. Without accurate real-time localization, the simulated environment can fall out of sync with the actual vehicle, resulting in incorrect stimuli being sent to the DUT.

Simulation platform

Simulation platform

This is a real-time system that generates a virtual environment and provides set values for sensor stimulation. It also comprises high-speed Ethernet for transmitting vehicle states and receiving simulation updates, as well as data logging units to capture sensor readings, actuator signals, and vehicle response for validation.

Physics-based simulation for ultrasonic sensors

The ASM environment and ASM traffic models are calculated on a real-time PC with access to the automotive bus. Standards such as ASAM OpenDRIVE® can be used to convert a real network into a format that can be used by the simulation system. The physics-based sensor simulation AURELION creates a 3D representation of the ego-vehicle, its environment, and surrounding traffic participants. While AURELION can generate raw data for all environment sensor types, its capabilities also extend to the generation of raw ultrasonic sensor data. For ultrasonic simulation, AURELION models wave propagation, reflection, and absorption based on material properties and environmental conditions. This enables the reproduction of realistic sensor behavior in scenarios such as parking maneuvers, obstacle detection, or close-range navigation. By incorporating accurate intrinsic and extrinsic parameters, the simulation can replicate manufacturer-specific sensor characteristics, ensuring that virtual signals closely match those of real hardware.

Over-the-air sensor stimulation can be seen as the interface between the simulation and real sensors that are mounted on the vehicle. It automatically analyzes the ultrasound signal generated by the vehicle's internal ultrasonic sensor, including ultrasonic frequency and signal amplitude. Based on the simulated environment, the response is calculated in AURELION and precisely reproduced and injected as a delayed echo signal to stimulate the sensor installed on the vehicle. By doing so, the over-the-air sensor stimulation delivers the appropriate feedback signal back to the real sensor, ensuring that the sensor perceives the simulated environment as if it were happening in the real world.
This closed-loop setup enables deterministic testing of ultrasonic sensors under a wide variety of conditions. It allows engineers to validate sensor behavior in complex scenarios, such as parking maneuvers, obstacle detection, or close-range navigation, while maintaining full reproducibility and scalability.
 

User Interface

Business Value: Efficiency and Compliance

Business Value: Efficiency and Compliance

Once the vehicle-in-the-loop setup is established for testing and development, this approach can be extended towards virtual homologation. The UN ECE R171 (“DCAS”) regulation explicitly encourages simulation-based validation, opening new doors for cost-efficient virtual homologation. In practice, this not only accelerates development cycles and reduces costs by minimizing test drives, but also delivers reproducible results. 

This regulation requires a credibility assessment to ensure that simulation sufficiently reflects real-world behavior. To achieve this, it is necessary to compare real sensor data with simulated data for specific operational design domains (ODD) and document it in a simulation handbook. 

By adopting vehicle-in-the-loop testing early in development, you can pave the way towards a changing world with new requirements and even support deterministic tests for changing software within the context of the software-defined vehicle (SDV). 

Summary

Vehicle-in-the-loop (VIL) testing enhances the validation of automated parking assistant systems by combining real vehicle hardware with a simulated environment. Using AURELION and ASM models, realistic ultrasonic responses are calculated and transmitted via over-the-air (OTA) stimulation back to real sensors, enabling closed-loop testing. 

VIL testing is key for validating automated parking assistants because it combines real vehicle hardware with a virtual environment. This enables realistic testing under controlled conditions without the high costs and risks of physical road tests. VIL offers high flexibility for complex scenarios, supports edge case and safety evaluations, and accelerates software update cycles. In the context of future virtual homologation, VIL is particularly relevant as it provides reproducible evidence of safety and functional compliance, paving the way for digital type approval processes.

흥미로운 이야기입니다. 연락:

About the Author

Caius Seiger

Caius Seiger

Product Manager Sensor Simulation, dSPACE

Thomas Michalsky

Thomas Michalsky

Senior Manager Application Engineering, dSPACE

dSPACE direct 뉴스레터 서비스를 통해 최신 소식을 받아보세요.

dSPACE 뉴스레터 서비스를 통해 최신 use case 와 신규 솔루션 및 제품, 교육 및 이벤트에 대한 정보를 지속적으로 확인하세요. 여기에서 무료 로구독을 신청하세요.

Enable form call

At this point, an input form from Click Dimensions is integrated. This enables us to process your newsletter subscription. The form is currently hidden due to your privacy settings for our website.

External input form

By activating the input form, you consent to personal data being transmitted to Click Dimensions within the EU, in the USA, Canada or Australia. More on this in our privacy policy.