I'm not having much luck with guiding recovery - yet another failure last night due to a brief loss of a guide star in the early hours.
The conditions that I'm hoping to get resumption working with are temporary loss of guide star due to stray clouds OR a remote facility temporary roof closure due to either wind gusts or short term high humidity (their rulez). In the latter case the roof may reopen 15+ minutes later (no earlier).
I don't seem to be able get the two software components to work together well. Going on last nights logs the guide star was lost for 40 - 50 seconds (4 cycles of 10 sec guide exposures). During this period it seems from the PHD2 logs that it was commanded (by SGPro?) to stop guiding. Meanwhile in SGPro's logs it spent the next 4 hours at 1 minute intervals asking for the PHD2 status and getting back "stopped" - it was at some sort of impasse regarding who makes the first recovery move. I suspect I have something miss set.
I think I need a fresh slate - and start over again with all the recovery settings - so if anyone can share what PHD2 and SGPro settings that they know works - that would be great. TIA.
As a foot note - very occasionally my Lodedstar X2 guide camera errors via its ASCOM link - a manual disconnect/reconnect of just the camera in PHD2 resolves this and guiding can be restarted. Can this solution be automated in PHD2? I.e. is there a recovery-on-camera-error feature hidden away somewhere?
Edited by Tonk, 14 October 2019 - 08:31 AM.