RPC call to Thorlabs driver will return before the commanded action is complete about artiq HOT 3 CLOSED

All those are now blocking since 4d077f5
The only motor-moving and non-blocking call is move_velocity() which just moves the motor in one direction until you call move_stop().

I let this issue open until you test it and ack it works as expected.

from artiq.

Blocking as default is good.

As a note for the future, I can imagine a few situations where you want to start a move to a certain point and then abort or override it with a different target. With fire-and-forget I suspect you can not abort a blocking move. If those situations come up, I would propose adding either a state to the driver that determines blocking behavior or add the async keyword argument back back in.

from artiq.

Tested working.

from artiq.