Bit of a strange one last night, generally I have no problems with a meridian flip and everything goes as planned and imaging restarts after the flip with no problems, BUT! last night(early this morning) SGP shut down after a failed flip which is not surprising because I started imaging after my target had crossed the meridian! VDB9 crossed the meridian at 22:16 hrs, SGP decided at 04:20 hrs that it needed to flip! and shortly after shut down…
[29/11/2016 04:20:47] [DEBUG] [Telescope Thread] ASCOM Telescope: Failed to flip because starting pier side and ending pier side are the same!
[29/11/2016 04:20:48] [DEBUG] [Pier Flip Thread] Meridian Flip: Telescope command to meridian flip has completed
[29/11/2016 04:20:48] [DEBUG] [Pier Flip Thread] Meridian Flip: Telescope failed to perform meridian flip
[29/11/2016 04:20:52] [DEBUG] [Pier Flip Thread] Meridian Flip: Procedure complete
[29/11/2016 04:21:31] [DEBUG] [Main Thread] PopulateDataModel: Transferring view to the data model…
[29/11/2016 04:21:31] [DEBUG] [MF Update Thread] Performing serialize…
[29/11/2016 04:21:38] [DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute, checking socket with status…
[29/11/2016 04:21:38] [DEBUG] [PHD2 Listener Thread] Checking PHD2 state…
[29/11/2016 04:21:38] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[29/11/2016 04:21:38] [DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[29/11/2016 04:21:38] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[29/11/2016 04:21:54] [DEBUG] [Sequence Thread] Blocking Pier Flip: Failed to meridian flip, aborting sequence (True)
[29/11/2016 04:21:54] [DEBUG] [Sequence Thread] Adding sequence level notification: Failed to meridian flip, aborting sequence.
Any ideas anyone?