Remote monitoring
Remote robot monitoring is not the motion control loop
By NOVEMIQ · Engineering explainer
Monitoring collects state and events for diagnosis. Motion control acts on a time-dependent reference. Keeping those responsibilities distinct helps define what the robot must do when connectivity changes.
- 01Robot state
- 02Telemetry boundary
- 03Remote dashboard
- 04Human investigation
Understand the boundary
An illustrative monitoring architecture sends operating state, faults, and selected measurements to a remote view. It should make stale information visible and preserve enough context to investigate an event.
What to review
Specify timestamps, units, sampling policy, and retention before building charts. A green status indicator without a freshness signal can hide a disconnected robot. Identify which information is operationally necessary and which is merely interesting.
Put it into practice
Monitoring does not by itself provide safe remote operation. Any command path needs its own authorization, acknowledgement, and failure behavior. Keep local control and protective functions within the system’s assessed architecture.
Technical reference
ROS 2 quality of service. Consult documentation for your selected software version before implementation.
Continue reading
- A simulation test matrix for robot software changes
- Joint names, units, and frames: small contracts with large consequences
Bring your integration challenge
NOVEMIQ supports motion planning and control, robot integration, simulation and remote monitoring. Start with your hardware, application and constraints.
Discuss robotics software →