Describe the bug
Currently when we schedule a move robot arm mission, the robot becomes busy and then goes back to available. As a consequence the backend will try to schedule a return to home mission because the mission queue is empty. Since the robot current area is null, an error message is sent to the frontend saying "unable to schedule return to home mission".
To Reproduce
Schedule a move arm mission for robot.
Expected behavior
Moving the robot arm should not trigger a return to home mission.
Suggested solution: Create a new mission type: "Move arm". Also relevant for other mission types: "Return home", "Localization".
Describe the bug Currently when we schedule a move robot arm mission, the robot becomes busy and then goes back to available. As a consequence the backend will try to schedule a return to home mission because the mission queue is empty. Since the robot current area is null, an error message is sent to the frontend saying "unable to schedule return to home mission".
To Reproduce Schedule a move arm mission for robot.
Expected behavior Moving the robot arm should not trigger a return to home mission.
Suggested solution: Create a new mission type: "Move arm". Also relevant for other mission types: "Return home", "Localization".
Screenshots