CalcMotor state MOVING while underlying physical motors are READY
After a Ctl+C, the Calc Motor wbdmz
remains MOVING
while the move is actually finished.
EH1_OPTICS [3]: umvr(wbdmz,0.1)
!!! === RuntimeError: axis wbdmz state is 'MOVING (Axis is MOVING)' === !!! ( for more details type cmd 'last_error(1)' )
Underlying motors wbdmzd
and wbdmzu
(Bliss and IcepapCMS) reports READY
.
sync_hard()
on HW motors did not solve the issue. sunc_hard
on the calc is not possible (since it thinks it's moving)
Restarting the session did not solve the issue.
Calling wbdmz.stop()
freeze the session -that needs to be killed.
cc: @cammarat
Edited by Samuel Debionne