I am using Nvidia Isaac control with the latest code: GitHub - nvidia-isaac/isaac_mission_dispatch: VDA5050-compatible cloud service for fleet mission dispatch deployed using docker compose. I have my master controller connected to a test robot and the robot connects successfully and is assigned its mission:
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] Created robot
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] Received a new mission [gain_control1]
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Mission state: PENDING -> RUNNING
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] Robot state: RobotStateV1.IDLE -> RobotStateV1.ON_TASK
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Mission started at 2025-03-13 19:25:48.487322
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Sending mission action node node1
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Node node1: PENDING -> RUNNING
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] Robot Online
However, the mission fails in Isaac:
mission-dispatch-1 | [Isaac Mission Dispatch] | WARNING: [A33-001124030] Fatal Errors present, failing mission
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Node node1: RUNNING -> FAILED
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Mission state: RUNNING -> FAILED
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Mission failed at 2025-03-13 19:25:50.409561
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Failure reason: None
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] [Mission ID - gain_control1] Mission duration: 0:00:01.922239
mission-dispatch-1 | [Isaac Mission Dispatch] | INFO: [A33-001124030] Robot state: RobotStateV1.ON_TASK -> RobotStateV1.IDLE
and no information is given as to why the mission is failing. On the robot itself the action associated with this mission completes with no problems according to the ROS logs. For reference I am using the VDA5050 connector: GitHub - inorbit-ai/ros_amr_interop on my robot.
The API Mission GET response doesn’t tell me much either:
{
"name": "gain_control1",
"status": {
"state": "FAILED",
"current_node": 0,
"node_status": {
"root": {
"state": "FAILED",
"error_msg": null
},
"node1": {
"state": "FAILED",
"error_msg": null
}
},
"start_timestamp": "2025-03-13T19:25:48.487322",
"end_timestamp": "2025-03-13T19:25:50.409561",
"failure_reason": null,
"failure_category": null
},
"lifecycle": "ALIVE",
"robot": "A33-001124030",
"mission_tree": [
{
"name": "node1",
"parent": "root",
"route": null,
"move": null,
"action": {
"action_type": "requestControl",
"action_parameters": {}
},
"notify": null,
"selector": null,
"sequence": null,
"constant": null
}
],
"timeout": 90,
"deadline": null,
"needs_canceled": false,
"update_nodes": null
},
This appears to be an error reporting bug in Nvidia Isaac