Looks like im the first one to add to the hopeful demise of this annoying problem (Freeze at the end of a sequence using 220.127.116.11) but what will be contained in this post is a 2 fold issue if you don’t mind, it will save the confusion of 2 separate threads when they could be related. It’s taken me 2 days of endless trying to get a freeze at the end so I hope all the effort is worth while.
Ran a simple sequence with PHD2 (simulated guiding), slew to object, take some frames with Cam Simulator and my NEQ6-Pro hooked up in the living room - END - As simple as that !
At the end of the sequence the scope parked successfully and SGP completed the sequence as expected with no problems.
Then, I decided to Reset the sequence and run it again (for some strange reason) and 2 things happened on the second run as follows:
I experienced the end of sequence freeze at the end of the second sequence run (primarily relevant to this thread)
The second sequence run did not run and Recovery Mode was fired up which aborted the sequence due to Guiding not being able to resume.
I’ll explain both 1 and 2 together as they are related:
At the end of the first successful sequence run, scope parked and PHD2 guiding was stopped and all PHD2 equipment disconnected as expected as I have checkbox ‘Disconnect equipment on sequence complete’ in the Profile for the PHD2 settings. I then did the ‘Sequence->Reset Sequence Progress’ command and decided to run the same sequence again. Bare in mind at this point, PHD2 is still up & running but all the equipment is disconnected. I hit run sequence, SGP unparked the scope, slewed to the target and put up message that guiding was resuming (forcing re-calibration). This did not work and recovery mode kicked in and went all the way to the end of it’s time without being able to restart guiding (because the equipment is still not connected). Once recovery ended it aborted the sequence as expected, parked the mount and the interface completely froze with ‘Parking Mount’ in the status bar. It required a forced shutdown of SGP.
NOTE: if recovery fires up as a result of the above and you manually connect PHD2’s gear then the next recovery attempt WILL be successful !
Point 1 -
When I reset the sequence and ran it again, why does SGP not check and request equipment connection in PHD2 as all the kit was disconnected at the end of the first run, SGP did not recognise this after the sequence reset. SGP gets PHD2 to connect it’s selected profile equipment on a fresh sequence run, SGP should query the connection status and connect if this should prove False and attempt to re-calibrate or resume guiding from there.
Point 2 - The abort freeze itself
One thing important to know ref the abort freeze is the final line in the log which it froze on which is as follows:
[29/01/2016 16:30:41] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
All entries after this in the log are as a result of a forced ‘Task Manager’ end task where SGP put up a message informing me Kit was still connected, SGP closes normally choosing YES to this info box after informing me that the sequence had changed and do I wish to save. hopefully the following Log will be worth its weight in GOLD.
Here’s the Log File which includes both sequence runs:
sg_logfile_20160129152723.txt (525.6 KB)
Caught exception in CanPierFlipNow : Object reference not set to an instance of an object. at fi.g0()
The above entry looks rather interesting
Probably no use at all but ill add the PHD2 Guiding Log and Debug Log in case it’s helpful:
PHD2_GuideLog_2016-01-29_163003.txt (26.3 KB)
PHD2_DebugLog_2016-01-29_163003.txt (848.3 KB)
Ken, I truly hope this info makes your rather long plane flight shorter and lucrative ! ! !