Physical robot monitoring
Physical robot monitoring
Monitor robot, gateway, and Robot Agent status, telemetry freshness, battery, faults, the active command, and stale or failed state.
How to monitor physical robots
Monitoring a physical robot is more than a green icon. Operators need to know whether the robot is online, whether the site gateway is online, whether the Robot Agent is heartbeating, and whether telemetry is current. Dagmont Command keeps those signals separate so a healthy network path is not confused with a healthy robot.
This is robot monitoring software for the supervisory layer. It shows operational state. It does not replace the safety controller that stops a robot in milliseconds.
Online, offline, and agent state
A Site Gateway is online when it is connected and its heartbeat is fresh. A robot can still be offline behind that gateway. If the robot heartbeat stops, Command records the Robot Agent as disconnected. If the heartbeat continues but the robot reports itself offline, Command records the robot as offline.
That split matters during remote robot operations. A technician can see that the site link is up and the agent on the robot computer is not, instead of treating the whole site as down. Fleet management uses the same distinction across many machines.
- Robot online or offline from reported status
- Site Gateway online or offline from heartbeat
- Robot Agent connected or disconnected
- Serial or controller faults reported in telemetry
- Active command and its lifecycle state
Telemetry freshness, battery, and faults
Heartbeat and telemetry are different. A robot can heartbeat while its last telemetry snapshot is old. Command treats telemetry older than five minutes as stale and opens an issue, even when the heartbeat is fresh. Operators should not command from a stale picture of battery, pose, or faults.
Robot telemetry carries battery, fault codes, and execution context back through the Robot Agent. Failure monitoring starts there: a fault in the snapshot becomes an operational issue with the robot, the time, and the reported text.
Active command, stale state, and failure detection
The active command is part of monitoring. Operators should see whether a robot is executing, waiting on an acknowledgement, or already failed. Dispatch uncertain means Command cannot confirm the physical outcome. That is a monitoring result, not a silent success.
When a failure needs root cause, retesting, and acceptance, the operational issue escalates into Deployment Intelligence. Command keeps the monitoring record. Deployment Intelligence keeps the investigation.