Hardware-in-the-Loop Configuration
Hardware-in-the-Loop configurations (HiL configurations) are a central component of TESTMETRIX®.
In a HiL test environment, the hardware components – such as test devices and the Device under Test (DuT), i.e., the unit under test – are typically stationary.
The software, especially on the DuT, changes with every test run, as new software or firmware versions are continuously tested during development.
A DuT often consists of multiple components (e.g., multiple PCBs).
Depending on the complexity of the test bench, there are thus multiple hardware components, each with their own changing software versions.
Traceability through HiL Configurations
To ensure complete traceability, the HiL configuration captures the software versions used in every test run.
This ensures you always know which software version ran on which component.
Benefit for Root Cause Analysis
Defining a HiL test bench with all its components ensures high reproducibility. This significantly simplifies root cause analysis because:
- Test environments can be reproduced exactly
- Differences between test runs become visible
- Errors can be specifically attributed to certain software versions
Using the HiL Configuration
1. Define the HiL Test Bench
The HiL test bench is defined once in the user interface.
A distinction is made between:
- Device under Test (DuT)
- Test system components (e.g., oscilloscopes, logic analyzers)
Test system components typically have no changing software versions and therefore do not need to be versioned.
DuT components, on the other hand, typically have changing software versions that need to be recorded.
This distinction is important for the later HiL configuration file.
2. Use the HiL Configuration File
After creation, a template for a HiL configuration file is available for download.
This file tells TESTMETRIX® which software versions ran on each DuT component after every test run.
3. Update Software Versions
After each test run, the corresponding fields in the HiL configuration file are automatically filled (e.g., via script) with the actually used software versions.
4. Upload via REST API
Subsequently, the HiL configuration file is uploaded together with the test data via the REST API.
Example: Bluetooth Gateway Test Bench
The following test bench consists of an ESP32 Gateway PCB as the DuT, a BLE Peripheral Simulator, and a TAF system with associated test repository.
After defining this test bench in the user interface, the following template configuration file is available for download:
hil_config:
hil_name: "Bluetooth Gateway HiL Bench"
components:
- name: "ESP32 Gateway PCB"
hw_version: "rev-1.2"
sw_version: ""
- name: "BLE Peripheral Simulator"
hw_version: "rev-2.0"
sw_version: ""
- name: "TAF"
sw_version: ""
- name: "Bluetooth Test Repository"
sw_version: ""
The sw_version fields are intentionally left empty. Before each test run, fill them with the actual software versions used and upload the file along with your test data via the REST API.