Robot command software

People searching for software to control multiple robots usually need a supervisory command layer, not a replacement motor controller. Dagmont Command issues high-level commands: pause, resume, cancel, controlled stop, return to charge or base, mode changes, and mission dispatch when the integration supports them.

The robot controller still runs real-time motion. Collision avoidance, braking, and physical emergency stop stay on the robot and the site safety system. A Command stop is a supervisory command. It is not a safety-rated e-stop.

Operator intent becomes a command with an explicit lifecycle. The states operators follow are requested, queued, dispatched, gateway acknowledged, robot acknowledged, executing, completed, or failed. A command can also be rejected, cancelled, expired, or left dispatch uncertain when the outcome cannot be confirmed.

Gateway acknowledged means the Site Gateway accepted the message. Robot acknowledged means the Robot Agent or controller accepted it. Neither state is physical completion. Executing means the robot reports that it is carrying the command out. Execution monitoring stays on that reported state.

• Requested — an authorized operator submits the command
• Queued — the command is waiting to be sent
• Dispatched — Command has sent it toward the site
• Gateway acknowledged — the Site Gateway accepted it
• Robot acknowledged — the robot side accepted it
• Executing — the robot reports the command in progress
• Completed or failed — decided from robot-reported state and physical evidence

Dagmont does not treat a network acknowledgement as physical completion. The result follows robot-reported state and execution evidence. If motors were commanded and encoders or other evidence do not show movement, the command fails rather than completing on a transport response.

Vendor HTTP and Python integrations use the same rule. The gateway can receive HTTP success and the vendor can accept the call, and the command still waits for an explicit completion report. Failures stay on the command record with a reason.

Viewers can watch the fleet and the command history. They cannot send commands. Operators send permitted commands when the organization has command execution enabled. Admins enroll gateways, robots, and adapters and decide who may command.

The audit trail answers who issued the command, when it was acknowledged, whether the robot executed it, and how it ended. That record is the robot operations audit trail. It is also the context Command attaches when a failure escalates into Deployment Intelligence.

• Dagmont Command
• Robot fleet management
• Robot operations platform
• Physical robot monitoring
• AMR fleet management
• AGV fleet management