Get started
TrialONE documentation
Investigate robot failures from live data, recordings and source code. Check the repair on a new run.
TrialONE helps robotics engineers investigate failures across software and hardware. It connects measurements and logs with the source and configuration available to it, then produces a finding with evidence, a proposed change or a next measurement. You can investigate a running ROS 2 robot or analyse recordings on a laptop.
Start with one real incident
Request Pilot Access, install the CLI and sign in with trialone login. Bring one failing recording, the symptom you observed and, if available, a healthy recording and the relevant source tree. Follow the Quickstart, then the Pilot guide.
The workflow
- Connect the live robot or provide a recording. Name the robot so its runs stay together.
- Review the evidence, proposed cause and remaining uncertainty in the report.
- Apply the change yourself, or give the issue to your coding agent. Physical work needs a person at the robot.
- Repeat the triggering scenario and compare a fresh recording with the original finding.
Terms you will see
| Term | What it is |
|---|---|
| Machine | One robot. Its runs are filed under its name: --machine, the variable TRIALONE_MACHINE, or the computer's hostname. |
| Run | One diagnosis or live watcher session, with the measurements and available code, configuration and device metadata. |
| Finding | One thing that left its normal range, with the second it happened, the channels involved and the measured numbers. |
| Issue | Related findings grouped across runs. It is open, in repair, resolved or ignored. |
| Recipe | What a fix needs, in nine fixed fields, from the symptom to an acceptance criterion that a partial fix fails. |
What do you want to do?
QuickstartInstall, sign in and analyse your first recording.Pilot guideChoose an incident and agree what a useful result looks like.How it worksWhat is measured, what is explained, and where the limits are.Watch a robot liveAttach to the running ROS 2 graph and stay silent until something changes.Hand a fault to a coding agentClaude Code, Codex or Cursor reads the issue and reports the repair back.
Something missing or wrong here? Tell us.