Hardware in loop testing

Hardware in loop testing services

Hardware-in-the-loop (HIL) testing validates vehicle software by running it on the final target hardware while a simulated environment represents the rest of the vehicle. Because HIL testing uses real components and real power, it requires specialised hardware.

HIL testing catches a few classes of bugs that MIL or SIL testing cannot:

• defects in the hardware.
• bugs in the toolchain or compiler, such as incorrect optimisations.
• runtime exceptions, such as stack overflows.
• performance issues, such as cascade failure from excessive CAN bus load.

HIL testing can be expensive, sometimes even more expensive than building a vehicle prototype. Much of its value comes from validating the underlying hardware, but many teams using model-based design already work with pre-validated hardware. For that reason, teams should carefully assess whether HIL testing is the right fit for their project.

If you intend to enter high-volume production, HIL testing is almost certainly required.

We help teams who are:

• designing HIL test benches using COTS options such as Vector, Speedgoat, or dSPACE.
• adding semi-automated testing using CCP/XCP live calibration.
• automating validation, verification, calibration, and change-management tests.
• integrating HIL rigs with other systems, such as continuous integration.

Small or resource-constrained teams should consider Software-in-the-loop (SIL) testing as a first step because, unlike HIL testing, it does not require specialised hardware. Many SIL tests can also be converted into HIL tests later.