error during motor move does not raise exception
I observed today a strange behavior with a move command to an icepap axis.
If during the movement the controller switch to an "OFF" state (due for example to a closed loop error) there is no error message, and bliss continue the execution of a function (if the move command is part of, like the exemple here below).
def toto():
mvr(vo5,10)
print('next')
mvr(bet,-1)
This can lead to wrong measurements or even worst collisions.
Can you have a look on it? Do we miss some configuration for avoiding this behavior?