Telemetry
Telemetry reports the robot's live state to the cloud.
- Direction: Uplink (robot → cloud)
- Topic:
uplink/robot/{robot_id}/{message_type} - Encoding: Cap'n Proto over Zenoh
The agent consumes motion/status/extras to maintain live robot state and relays them to the cloud (rate-limited per message type). Detected objects are forwarded as well.
Message types
| Type | Purpose |
|---|---|
| Motion telemetry | Pose, velocity, and motion state. |
| Status telemetry | Mode, operational status, and high-level health. |
| Telemetry extras | Vendor-specific or supplementary fields. |
| Object | Detected objects in the environment. |
Motion telemetry
Carries the robot's pose (position and orientation) and velocity.
Detailed message schemas (fields, types, and units) are coming soon.
Status telemetry
Carries the robot's mode and operational status.
Detailed message schemas (fields, types, and units) are coming soon.
Telemetry extras
A place for fields not covered by the standard motion/status messages.
Detailed message schemas are coming soon.
Object
Reports a detected object. Objects are persisted by the agent.
| Field | Notes |
|---|---|
id |
Object identifier. |
name |
Display name. |
object_type |
Object classification. |
location |
Object location. |
trajectory |
Optional motion of the object. |
radius_m |
Object radius in meters. |
scope |
Object scope. |
| timing | Creation / expiry timestamps (epoch ms). |
Detailed field schemas (enumerations, geometry, and units) are coming soon.
Publishing
- Native: publish each type to
uplink/robot/{robot_id}/{message_type}. See Custom Integrations. - ROS 2: the bridge maps your ROS 2 topics to these messages. See Telemetry Mappings.