Hello,

I have found a problem with my setup, when driving a HEQ5 mount with the indi eqmod driver.
It is totally repeatable and It will lead to a physical crash when operated on remote !

* connected the eqmod driver
* activate the tracking (sideral rate)
* Within the motion control section, ask for a motion (to north)
The mount starts moving as expected
* Ask the driver to stop the motion
The stop does not occur. At that point, driver logs show read timeouts.
The eqmod driver won't disconnect (timeout error disconnecting)!. If the driver (process) is killed/restarted it can't establish connection (handshake fails).

The mount will continue to move at the specified rate until powered off !

Logs of the driver are attached.
I use a recent GIT snapshot of the driver, with direct connection to the mount.

Ludovic

The way the HEQ5 mounts work, it will continue to move until told to stop, or make a pule movement for a shot time. If the connection is interrupted it will continue to move because it can not receive the stop command.
A few things to check:
Check the cable. If it is loose it may disconnect when shifting from a slew. Wiggle it and observe what happens.You may have to pinch the USB end.
Check the power. If the power is not stable due to voltage drop it might interrupt the connection.
Try different cables or upgrade to bluetooth.

Thank you for your advises: I unplugged/plugged everything and the problem did not reappear until now ! You're probably right

I wonder if it would be hard to include a stop request in the handshake ? (so that the situation can be recovered without power-cycling the mount ...)