Robot telemetry
Robot telemetry platform
Track robot telemetry as it returns through the Robot Agent and site gateway, including freshness, battery, faults, and execution state.
What a robot telemetry platform records
Robot telemetry is the state the robot reports: battery, faults, operating mode, connectivity, and the execution context around the active command. Dagmont Command stores those snapshots as they return from the robot through the Robot Agent and the Site Gateway.
Telemetry monitoring is part of physical robot supervision. It tells operators whether the picture on screen is current. It is not a substitute for the safety system that must act without waiting for a cloud round trip.
The return path
Commands travel from Command to the Site Gateway, then to the Robot Agent or adapter, then to the robot controller. Telemetry travels back: robot, Robot Agent, Site Gateway, Dagmont Command. Robot telemetry monitoring only means something if that return path is visible separately from the command path.
A gateway can acknowledge a command and still fail to deliver a fresh snapshot. Command records that gap instead of copying the last snapshot forward as if the robot had reported again. The operations platform treats the snapshot time as part of the record.
Freshness, battery, and faults
Heartbeat and telemetry freshness are independent. If the robot heartbeat is current but no telemetry snapshot has arrived within five minutes, Command opens a stale-telemetry issue. Battery and fault fields from an older snapshot stay historical. They are not described as live.
Fault text and fault codes in the latest snapshot become operational issues, including serial or controller disconnects when the robot reports them. Physical robot monitoring shows how those issues sit next to gateway and agent health.
Telemetry and command results
Execution state in telemetry supports the command lifecycle. A command completes when the robot reports completion and the execution evidence agrees. Telemetry that shows no movement after a move was commanded is evidence of failure, not a successful dispatch.
That evidence is what operators review in the command center and what Command can attach when a failure escalates into Deployment Intelligence. The telemetry platform is the return half of the audit trail.