When emergency is pressed and user presses the power on button, after a short while the interface will disconnect.
I think this also impacts other random disconnections, maybe when launching consecutive MDI codes that are longer and prevent some commands to respond, there should be a way to differentiate these cases from a disconnection.
When emergency is pressed and user presses the power on button, after a short while the interface will disconnect.
I think this also impacts other random disconnections, maybe when launching consecutive MDI codes that are longer and prevent some commands to respond, there should be a way to differentiate these cases from a disconnection.
I think there should be something to show that machine is doing something, and so need wait for machine to finish it, and even if user want to send more commands should not loose connection, just wait for machine to finish and have something to show user that it's not finished.
I think there should be something to show that machine is doing something, and so need wait for machine to finish it, and even if user want to send more commands should not loose connection, just wait for machine to finish and have something to show user that it's not finished.
When emergency is pressed and user presses the power on button, after a short while the interface will disconnect.
I think this also impacts other random disconnections, maybe when launching consecutive MDI codes that are longer and prevent some commands to respond, there should be a way to differentiate these cases from a disconnection.
If send MDI to park but machine motion.feed-inhibit is on, if then press some other buttons to move, interface will lose connection
I think there should be something to show that machine is doing something, and so need wait for machine to finish it, and even if user want to send more commands should not loose connection, just wait for machine to finish and have something to show user that it's not finished.