Case where Axis.is_moving=False even if Axis.state=Moving
I had this situation where I started a move, bliss crashed (kinda, probably my fault, but still) while the motor was still moving. I restarted the session right away, saw that the axis state was sill MOVING (as expected), but I couldn't do a stop since Axis.is_moving returned False.
Is this wanted behaviour? Thanks!