I am running the current version of both SGP and TSX. I am not using PhD for this sequence because it is not needed (Camera lens, dither by mount) so I cannot say if the problem would happen with PhD running as well.
Bottom line is that everything runs fine until I go to disconnect equipment in the AM at which point SGP becomes completely unresponsive and has to be shut down with task manager. Log at link below:
I have experienced the same issue with v3.0.1.0. I walked out to the observatory at 5AM to close the roof. The scope had parked as expected. However, when I sat down in front of the computer, everything was frozen and I simply powered off the PC.
After a reboot, I checked and everything had completed. The last thing that would have been done (I think) was disconnecting all the gear. The next night the same thing happened again.
So for the third night, I disabled the option to disconnect the gear at end of sequence and everything finished up properly.
Unfortunately, I left the dark sky site that morning and forgot to copy the SGP Log. I will run the test again next trip out and get the logs. Often a software freeze-up means the last couple of entries in a log file do not get posted.
[05/18/18 05:51:48.092][DEBUG] [Main Thread] Disconnecting ASCOM Telescope: ASCOM.SoftwareBisque.Telescope (I asked SGP to disconnect the mount - this is where it seemed to lock up)
[05/18/18 05:51:57.389][DEBUG] [Equipment Connectivity Thread] SGPro thinks the telescope is connected, but it’s not, syncing UI… (Hmm, why is it doing this?)
[05/18/18 05:51:57.389][DEBUG] [Equipment Connectivity Thread] Adding sequence level notification: External disconnect of telescope detected… (This is probably where I went into TSX and disconnected the mount - but SGP was still locked up).
At this point I went to Task manager and forced SGP shutdown.
Hi Jared - this version fixes the bug which reverted all the telescope sync methods, both in equipment profiles and sequences, back to ‘sync’ upon intstalling a new version.
Thanks!