"Waiting for guider to report it is done settling" problem with sg_2_4_3_18

After upgrading SGP from sg_2_4_3_16 to sg_2_4_3_18 I set a sequence running, only to get the following message at the bottom of the window:

“Waiting for guider to report it is done settling”

This message did not go away and after several minutes so I aborted it.

I think the issue here is that the guider PHD2 (phd2-2.5.0dev7) was already running and guiding before I started the sequence. Perhaps PHD2 does not send the done settling signal if SGP did not initiate the guiding?

The log file for this session is here:
http://www.mikeoates.org/tmp/sg_logfile_20151122170951.txt

As a side note, as I really did not have time to experiment, I installed the previous version sg_2_4_3_17 (which I had skipped passed anyway) But that install did not actually install SGP, the exe was no where to be found and no icon was available on the start menu. (using Windows 10 64bit)

So I installed sg_2_4_3_16 and I was back to a working session. Not tried sg_2_4_3_19 yet as the weather is bad.

Mike

Thx for the report. The PHD logs would likely be helpful for troubleshooting this one.

Ken,

Ok, I am work now so will post the PHD2 log later, in about 8 hrs.

Mike

I had the same issue the other day. I too had PHD2 (phd2-2.5/0dev7) already running and guiding when I started the sequence. I used the “Center Here” from my previous nights image so I had the mount pointed at my target, everything in focus and guiding before I started my sequence. After a couple of minutes of the “Waiting for guider to report it is done settling”, I manually stopped then restarted PHD2 guiding after which the message went away. Once I restarted guiding it took about 20 seconds for the message to go away and for imaging to begin. I had no other issues the remainder of the night, This was also with sg-2.4.3.18.

Mark

Ken,

Both logs are now here:
SGP:
http://www.mikeoates.org/tmp/sg_logfile_20151122170951.txt
PHD2:
http://www.mikeoates.org/tmp/phd2_guidelog_2015-11-22_170929.txt

Thanks,

Mike

Mike,

Could you upload the PHD2 Debug Log too?

Thanks,
Andy

Andy,

The debug log is here, I have compressed it as it was over 50Mb.
http://www.mikeoates.org/tmp/phd2_debuglog_2015-11-22_170929.zip

Mike

Thanks. 

This should be resolved in the 2.4.3.20 beta.

This just happened to me tonight and last night. I was able to resolve by stopping & starting PHD2 guiding. I’m running 2.4.3.21