Ways in
Live on the robot
Watch a running robot and stay silent until something changes.
Start trialone watch in the robot's ROS 2 environment. It discovers readable topics, listens to numeric data and reports supported changes during the session. Missing message types and unreadable topics are named at startup. Check that it can see your graph before leaving it running.
Use the same ROS domain and source your ROS installation and workspace as you would for the robot's own nodes. With a model configured, an investigation can read live graph, log, parameter and process evidence. When signed in, the watcher also posts findings and checks in with your workspace.
$ trialone watch$ trialone watch --topics /joint_states,/odom
Other sources
| Source | Flag |
|---|---|
A file that is still growing: a CSV with a header row, or lines of key=value | --follow <file> |
| An existing recording, played as if it were live | --replay <recording> |
| A microcontroller on a serial port: Arduino Serial Plotter lines, ESP32 crash reports | --serial <port>, with --baud |
| Several devices of one machine on one clock: CAN, host board, ROS graph | --robot <robot.yaml> |
The serial port needs the extra: pip install "trialone[serial]".
As a service
$ trialone install-service$ trialone install-service --install
On Linux with systemd, the first command prints the user service. The second installs it, starts it and checks its status. It uses the saved login and model settings, the ROS distribution and domain selected during installation. The installer reports if permission is needed to keep it running after logout. If your robot needs a custom workspace or environment, review the generated service before relying on it.
A connected watcher posts findings, checks in every minute and receives workspace jobs such as building a reference or checking a repair. Configure its recordings folder under Settings, Robots for those recording jobs.
Silence and incidents
When a watcher stops checking in, the website marks the machine as silent and alerts you. A watcher stopped by hand says so first, so a planned stop is not an alarm.
When you observe a problem, mark it with a short description. The active watcher uses the recent evidence around that moment to investigate what happened:
$ trialone mark "The robot stopped beside the loading station"Camera context
The current pilot watcher can keep a small recent buffer from supported ROS camera topics and send selected frames to the configured model during an investigation. This is visual context, not a continuous video upload or an image fault detector. Turn it off for a machine under Settings, Robots, or start with --no-camera. See Data and model processing.
Limits
- The numerical value-change trigger can miss an isolated change on one channel. This is separate from missing-data, timing and protocol checks.
- Explanations on the live path are leads. Verify them on a recording.
Something missing or wrong here? Tell us.