AI agent for research and development engineers
Hardware-in-the-Loop Test Run Agent
Run the full rig suite unattended and classify each failure with evidence
What it does
Running scenarios on a rig by hand is slow, and when something fails people argue about whether the rig or the code is at fault. This agent flashes the build to the device, runs the scripted scenarios in order, and records signals such as voltages, bus traffic and timing. When a test fails it reruns it, then checks the rig state: supply voltage, cable connections, temperature, the last calibration. It classifies each failure as rig, code or timing, with the evidence. It repeats the failing scenario after a rig reset to confirm. The engineer approves the summary before it goes to the team. Edge case: a test only fails right after a power cycle, so the agent notes the pattern as a timing issue.
How it works
Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.
Read the steps as a list
- New build or nightly schedule
- Check rig health and flash the build
- Run the scripted scenarios and record signals
- Compare results with expected values
- Did every scenario pass?If not: rerun each failed scenario twice and record the signals again. Back to step 3.
- Read rig state: supply, cables, temperature, calibration age
- Classify each failure as rig, code or timing
- Does the failure repeat after a rig reset?If not: mark it as a rig fault and ask for maintenance. Back to step 3.
- Engineer approves the summaryThe agent waits here for your OK.
- Test report with failure classes and signals
How it decides
It labels a failure as rig when the rig health check fails or a reset fixes it, as code when it repeats on a healthy rig, and as timing when it passes or fails depending on sequence.
- Rerun a failed scenario twice before classifying
- Label rig fault when supply varies more than 3% or a cable test fails
- Label code fault when it fails the same way on three reruns with a healthy rig
- Label timing when results change with start delay or order
Make it yours
Every agent is a starting point. You choose these settings for your own situation.
- Scenario list and order
- Rig health limits
- Rerun count (default 2)
- Schedule (default nightly)
- Signals to record for each scenario
What keeps you in control
It always asks you first
- Engineer approves the summary before it is shared
- Engineer approves any scenario script change
Hard limits
- Never run scenarios when rig health is out of limits
- Never change a pass criterion in order to pass
It stops when
- Done: all scenarios pass or failures are classified and approved
- Stop: the rig health check fails and testing cannot continue
Set it up
We guide you through the set-up, step by step
Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.
- One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
- The agent then walks you through connecting your own data, one source at a time
- A downloadable copy with the flow chart, the rules and the full guide