I’m afraid there is no easy answer here, but if it’s never happened before is there anything at all in your rig / system that has changed recently?
- Anything different with your PHD2 profile?
- ASCOM platform upgrade?
- Drivers?
- etc
Is the issue repeatable in different areas of the sky?
From the logs, I can see that PHD2 is successfully restarts and then, as you say, immediately loses the star. Have you been able to observe this in the PHD2 app itself? It may offer clues.
In terms of possible SGPro bugs:
- I notice that you are not using dither or settling. This is totally fine, but atypical. It has me wondering if the absence of those options introduces some kind of timing issue, but, for an issue like this I would expect to see SGPro fail and all I see is an error directly from PHD2. In any case, you might see if you observe different results when you enable settling (don’t worry about enabling dither). I am not implying that, if this works, that it’s the solution… we’re just gathering evidence at the moment. Has it been on in the past?
In general, and I don’t know if any of this applies to you:
- Does PHD2 connect to an ASCOM driver for its mount connection? There are non-ASCOM connections available, but ASCOM is, by far, the most reliable and resilient connection type.
- When PHD2 is asked to auto select a star does it lock on to a real star?
- Have you made sure that the PHD2 exposure length is sufficient and that the local stretch function produces clean data?
- How are you calibrating? If re-using an existing calibration, maybe delete it and re-calibrate from scratch.
- Anything that may be preventing PHD2 from pulse guiding.