Health and Status
Report faults, events, and overall robot health to the cloud.
- Direction: Uplink (robot → cloud)
- Topic:
uplink/robot/{robot_id}/{message_type} - 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.
Detailed message schemas (fields, types, and units) are coming soon.
Event
An event carries an event type, a human-readable message, and the time it occurred.
Detailed message schemas (fields, types, and units) are coming soon.
Publishing
- Native: publish to
uplink/robot/{robot_id}/{message_type}. See 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.