"stop button" behaviour on our different software are not consistent and not well documented

[mbonani]

Followig a email interaction

we’ll have to look into

• what kind of messages the stop buttons from the different interfaces send,
• and how the robot and simulated robot react to those messages.

Ideally, it makes sense to

• stop the execution
• stop the motors for the reasons Moti mentioned
• keep the rest of the internal state as is

as for the correct/ defined state when you start the execution, it should happen when “load execute” is clicked, not when stop or pause or restart or step is clicked.