On Sat, Mar 29, 2025 at 05:58 PM, John Dias wrote:
Thanks Doug, to be clear the mount was NOT parked as the software/driver lost communication.
John, it sounds like Gemini was in a bad state if everything was initialized properly, but then it lost communications with the PC and continued to track past the safety limit.
?
A few things to check, before trying to figure out what may have caused this:
?
1. Did you start in CWD position with a cold start during that session? Gemini has to know the physical position of the mount relative to the safety limits when you start it, otherwise there's no guarantee that it'll stop at the right position.
2. Check and possibly replace the 3v battery in Gemini, reset Gemini to HGM Defaults and set all the settings again
3. If this happens again and you're using ASCOM, try going to the ASCOM driver and run Setup->Troubleshooting Report... It'll collect all the recent logs, connect to Gemini and retrieve settings, etc., and will create a single Zip file that you can upload here to Files section. Possibly there'll be something in the logs to indicate what happened.
?
Regards,
?
? ?-Paul
?
Paul Kanevsky