Uploaded May 2026 | Updated November 2026, 2 hours ago
In this video, we demonstrate an end-to-end approach to testing an automotive ECU using RestBus simulation in a Hardware-in-the-Loop (HIL) environment.
You’ll see how NI VeriStand and the Vehicle Communication Toolkit (VCOM) work together to simulate realistic vehicle networks and enable communication with a physical ECU using an AUTOSAR database.
Unlike basic CAN simulation, this setup maps network signals directly into real-time vehicle dynamics models, allowing you to test not just signal exchange, but full system behavior under realistic conditions.
The demo focuses on a cruise control ECU, highlighting key challenges in embedded software validation:
* Verifying real-time performance and timing behavior
* Evaluating the impact of network latency and I/O delays
* Testing under realistic vehicle and environmental conditions
* Ensuring safe system behavior in edge cases
You’ll also see how engineers can:
* Simulate driver inputs, road conditions, and vehicle dynamics
* Perform RestBus simulation for missing network nodes
* Interface directly with the device under test (DUT)
* Validate AUTOSAR-based communication in a closed-loop system
This workflow is especially relevant for engineers working on:
- ADAS, electrification, software-defined vehicles, and AUTOSAR-based ECU development
Learn more at bit.ly/4urgC5X and bit.ly/49hWISf
In this video, we demonstrate an end-to-end approach to testing an automotive ECU using RestBus simulation in a Hardware-in-the-Loop (HIL) environment.
You’ll see how NI VeriStand and the Vehicle Communication Toolkit (VCOM) work together to simulate realistic vehicle networks and enable communication with a physical ECU using an AUTOSAR database.
Unlike basic CAN simulation, this setup maps network signals directly into real-time vehicle dynamics models, allowing you to test not just signal exchange, but full system behavior under realistic conditions.
The demo focuses on a cruise control ECU, highlighting key challenges in embedded software validation:
* Verifying real-time performance and timing behavior
* Evaluating the impact of network latency and I/O delays
* Testing under realistic vehicle and environmental conditions
* Ensuring safe system behavior in edge cases
You’ll also see how engineers can:
* Simulate driver inputs, road conditions, and vehicle dynamics
* Perform RestBus simulation for missing network nodes
* Interface directly with the device under test (DUT)
* Validate AUTOSAR-based communication in a closed-loop system
This workflow is especially relevant for engineers working on:
- ADAS, electrification, software-defined vehicles, and AUTOSAR-based ECU development
Learn more at bit.ly/4urgC5X and bit.ly/49hWISf










