Get started
TrialONE documentation
Find out what went wrong on a robot from a recording of it running, and prove that the repair held.
TrialONE reads what a robot recorded (a ROS 2 bag, an MCAP file, a CSV or HDF5 export, a PX4 or ArduPilot log, a firmware crash report) and answers four questions: what happened, why, what to change, and how to check that the change worked. Every answer becomes an issue on your account, with the numbers it rests on.
In short
Request access, install the command line tool on the robot or a laptop, sign in once with trialone login, and run trialone diagnose on a recording. The Quickstart takes you from there to your first issue.
The mental model
Five terms carry the whole product.
| 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 of one recording, or one session of the live watcher. It keeps the state of the machine at the time: the commit, the parameter files, the devices. |
| Finding | One thing that left its normal range, with the second it happened, the channels involved and the measured numbers. |
| Issue | The same finding across every run it appeared in. 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?
QuickstartFrom an approved account to your first issue.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.