Over the last few years, there are instances when SGP and PHD2 get out of sync. At all times, if I start a sequence via SGP and allow it to boot up PHD2, connect, calibrate and guide, all goes well. The niggles occur when you pause or abort and try and restart. Sometimes PHD2 does not start guiding, or the opposite, it may be guiding, yet SGP sits and waits for the guider to start up or settle - clearly it is out of sync somehow.
It is also sometimes the case that at the start of a new sequence, even before the first exposure is made, it is necessary to abort, make some changes to the control panel etc and restart. In these cases, not only does the abort move the sequence to resume status, when you hit resume, the missing elements of the sequence start up are skipped over and it is necessary to do a full abort, sequence reset and start over.
These general observations highlight some practical suggestions:
1 Can SGP and PHD2 communicate in such a way with regard to status, so that SGP does not have to assume a status, which, if it has been interrupted, could be out of date?
2 Can an abort, made before the first exposure completion, reset the clock so to speak, so the the sequence action button returns to ‘run sequence’ rather than ‘resume sequence’