Health and Status
Report faults, events, and overall robot health to the cloud.
- Direction: Uplink (robot → cloud)
- Topic: a sub-key of
robot/**on the local Zenoh session (e.g.robot/fault) - Encoding: Cap'n Proto over Zenoh
High-level operational status travels with status telemetry. Use the message types below for discrete faults and events. The agent forwards these to the cloud.
Message types
| Type | Purpose |
|---|---|
| Fault | A fault/error condition on the robot. |
| Event | A notable operational event (state change, milestone, warning). |
| Status telemetry | Continuous high-level health/mode (see Telemetry). |
Fault
A fault carries a fault code, a severity level, a human-readable message, the time it occurred, and whether it is currently active or has cleared.
Clear your faults. Robot software must re-send the fault with
active = falsewhen the condition clears, otherwise it persists on Rover Nexus.
See Uplink Messages → fault for the full schema,
including the FaultSeverity levels.
Event
An event carries a discrete state transition (e-stop engaged/released, mode changed, mission started/completed, fault raised/cleared) and the time it occurred.
See Uplink Messages → eventTelemetry for the
full EventKind union.
Robot messages and system health
- Messages — free-text, leveled notes for the operator UI: see Uplink Messages → message.
- System health — host CPU/mem/disk/temperature/signal, filled by the agent by default: see Uplink Messages → systemHealth.
Publishing
- Native: publish to the
robot/**key space (e.g.robot/fault,robot/event). See Uplink Messages → Publishing and Custom Integrations. - ROS 2: map your diagnostic/event topics through the bridge. See Telemetry Mappings.
!!! tip Use faults for conditions that require attention or block operation, and events for informational state changes. Keep messages concise and human-readable.