Health and Status
Report faults, messages, 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 operator-facing messages. The agent forwards these to the cloud.
Message types
| Type | Purpose |
|---|---|
| Fault | A fault/error condition on the robot. |
| Message | A human-readable note for the operator UI (info / warn / error). |
| System health | Host CPU/mem/disk/temperature/signal. |
| 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.
Robot messages and system health
- Messages: free-text, leveled notes for the operator UI. A message can
optionally require operator confirmation; the reply arrives back at the robot
as a
messageConfirmationcommand. 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/health). See Uplink Messages → Publishing and Custom Integrations. - ROS 2: map your diagnostic topics through the bridge. See Telemetry Mappings.
Tip. Use faults for conditions that require attention or block operation, and messages for informational notes to the operator. Keep messages concise and human-readable.