Hi,

I don't remember things turning that bad for me. I bet your scope was tracking when that happened? If so, it may be a consecquence of communication failure between the mount and the driver. Tracking means the driver periodically reprogrammes the mount to slew at a specific speed at each axes. Having some of this command getting a communication error, the mount may have programmed to slew at a crazy speed. The same communication failure may prevent the driver from instructing the mount to stop... I know, not a really reliable system desing...

After having to turn off the mount, it seems to be a good idea to have a clean start. Maybe you don't need to turn off the RPI, but definitelly disconnect the driver, restart the inidserver, and start from park position, to have a clean sync state.

Read More...