meddev-hardware-in-loop
/meddev-hardware-in-loop
Validate software with real or representative hardware, sensors, actuators, and timing, to uncover integration and safety issues not visible in simulation. Use when working on hardware in loop in medical device software.
- Author
- aminalam ↗
- Repository
- meddev-agent-skills ↗
- Licence
- MIT
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Validate software with real or representative hardware, sensors, actuators, and timing, to uncover integration and safety issues not visible in simulation. Use when working on hardware in loop in medical device software.
Original author description
Validate software with real or representative hardware, sensors, actuators, and timing, to uncover integration and safety issues not visible in simulation. Use when working on hardware in loop in medical device software.
How it works
- Purpose
- When to Apply
- Requirements (testable)
- Recommended Practices
- Patterns
- Anti-Patterns (risks)
- Verification Checklist
- Traceability
- References
- Changelog
SKILL.md preview
---
name: meddev-hardware-in-loop
description: Validate software with real or representative hardware, sensors, actuators, and timing, to uncover integration and safety issues not visible in simulation. Use when working on hardware in loop in medical device software.
license: MIT
metadata:
skill_id: TEST-HIL
version: 1.0.0
last_updated: '2026-01-04'
applies_to: Class A, Class B, Class C
jurisdiction: Global
prerequisites: TEST-INTEGRATION, FW-HAL, ARCH-SAFETY-CLASS
category: testing
---
# Hardware-in-the-Loop (HIL) Testing
## Purpose
Validate software with real or representative hardware, sensors, actuators, and timing, to uncover integration and safety issues not visible in simulation.
## When to Apply
- Before release for safety-relevant features.
- After hardware/driver changes or timing-sensitive refactors.
## Requirements (testable)
1. Fixture Design: Use representative hardware fixtures with controllable stimuli and measurements; include fault injection paths. Rationale: realism and safety coverage.
2. Automation: Automate HIL sequences; script stimuli and assertions; capture logs/measurements. Rationale: repeatability and evidence.
3. Safety Monitoring: Monitor outputs for safety limits; include E-stops; ensure safe state on test failure. Rationale: operator/device safety.
4. Timing: Measure latencies and deadlines under realistic load; verify against requirements. Rationale: timing assurance.
5. Parallelization: Where possible, run tests in parallel fixtures; manage resource contention safely. Rationale: efficiency.
6. Traceability: Link HIL tests to requirements/risks and record configurations (HW rev, firmware rev, calibration). Rationale: reproducibility.
## Recommended Practices
- Use DAQ/logging for analog signals; timestamp with synchronized clocks.
- Combine HIL with fault injection (disconnects, noise, power dips).
- Keep fixtures version-controlled (BOM, wiring, firmware).
- Provide dry-run/simulation mode for CI when hardware not available.
## Patterns
HIL test record (YAML):
```yaml
# REQ-HIL-REC-01
test_id: TEST-HIL-102
reqs: [REQ-62304-102, REQ-FT-WD-01]
hw_rev: "board v2.1"
fw_rev: "1.3.0"
stimuli:
- type: digital
signal: door_open
at_ms: 0
measures:
- signal: motor_pwm
expect: 0 within 50ms
result: pass
```
Fault injection step:
```text
// REQ-HIL-FAULT-02; TEST-HIL-120
At t=500 ms, drop comms line; expect safe state within 200 ms.
```
## Anti-Patterns (risks)
- Ad-hoc manual HIL with no logs -> risk: non-reproducible results.
- No safety limits/E-stop during tests -> risk: injury/device damage.
- Ignoring hardware configuration tracking -> risk: unrepeatable tests.
- Only ideal conditions tested -> risk: missed real-world faults.
## Verification Checklist
- [ ] Fixture representative; stimuli/measurements controlled; fault injection available.
- [ ] Automated scripts/sequences with logged results and timestamps.
- [ ] Safety monitoring and E-stop implemented; safe state on failure.
- [ ] Timing under load measured and within requirements.
- [ ] Parallel execution handled safely; resource conflicts managed.
- [ ] Hardware/firmware/config recorded; tests linked to requirements/risks.
## Traceability
- Map `TEST-HIL-###` to requirements and hazards; store fixture/config data with results.
## References
- IEC 62304 integration/system testing context.
- ISO 14971 risk-based verification.
## Changelog
- 1.0.0 (2026-01-04): Initial HIL testing skill with fixture, automation, and safety/timing focus.
## Audit History
- **2026-01-04**: Audit performed. Verified:
- HIL fixture patterns follow industry best practices
- Safety monitoring and E-stop requirements accurately described
- Fault injection concepts are appropriate for medical device testing
Versions
The database has no other skills named meddev-hardware-in-loop.
Database snapshot: 13.11.2026 · package version 9169d7d14db4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100meddev-integration-testing
Validate interactions between software components and hardware interfaces, ensuring interfaces, protocols, and data flows behave correctly in realistic configurations. Use when working on integration testing in medical device software. - 100meddev-hardware-abstraction
Provide patterns for HAL design that enable testability, portability, and safety: clear interfaces, separation from application logic, and mockability. Use when working on hardware abstraction in medical device software. - 90esp32-hardware-in-loop-fixture-contract
Use when designing, reviewing, debugging or validating hardware in loop fixture contract for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 100repo-b-hardware-first
Enforce hardware-first diagnosis and fixes in <PRIVATE_REPO_B>. Use for runtime probe, telemetry, inference, and integration failures where strict real-hardware behavior, no new stubs, deterministic diagnostics, and no unrequested driver/runtime mutation are required. - 95robotics-testing
Testing strategies, patterns, and tools for robotics software. Use this skill when writing unit tests, integration tests, simulation tests, or hardware-in-the-loop tests for robot systems. Trigger whenever the user mentions testing ROS nodes, pytest with ROS, launch_testing,… - 100hardware-tdd
Use when planning tests for Arduino, ESP32, ESP32-S3, Pico, or Pico W firmware; deciding what can run off-target; using Wokwi or simulation; writing host fakes; or accepting a physical hardware feature without confusing compile proof with system proof.