I have a more clear definition of this issue, I hope.
Running Windows 10 Pro Anniversary
SGP 2.5.2.5
PHD 2.6.2
Camera is STT-8300 using SGP API to run autoguider
Problem is that with settling timer un-ticked and 0 typed in the box, nothing happens when the settling distance reaches and crosses the distance threshold.
I am attaching logs which have only one attempt to run a sequence as I described above. I am also including the matching PHD logs, although my lay-person guess is that PHD is doing what it is asked to do.
SGP Log:
https://www.dropbox.com/s/6b8wxyb5c53wx93/sg_logfile_20161025213156.txt?dl=0
PHD logs
https://www.dropbox.com/s/7ulhyg1wqki3n5d/PHD2_GuideLog_2016-10-25_213414.txt?dl=0
https://www.dropbox.com/s/n2p98bsswkrpx7y/PHD2_DebugLog_2016-10-25_213414.txt?dl=0
I'm not sure if it is helpful, but I'd like to draw your attention to this section of the log:
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Guiding
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] {"method": "guide", "params": [{"pixels": 0.5, "time": 0, "timeout": 300}, false ], "id": 1003}
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] Sending to PHD2:
{"method": "guide", "params": [{"pixels": 0.5, "time": 0, "timeout": 300}, false ], "id": 1003}
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] Checking PHD2 state...
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] Sending to PHD2:
{"method": "get_app_state", "id": 1001}
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Guiding
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] User has elected to skip guider settling over time...
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] Waiting for Auto Guider distance to fall below 0.1
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] PHD2 distance request...
[10/25/2016 9:39:51 PM] [DEBUG] [Sequence Thread] PHD2 distance request returned 0.2...
It says "Waiting for the Autoguider Distance to fall below 0.1" but my setting is 0.5 for this sequence. Maybe you are doing this for another reason, though, because next, a capture occurs and the distance increases. Then the distances come back down. Lower and lower distances are reported, eventually they are lower than the threshold, but nothing ever happens, and I eventually abort the sequence. This excerpt is from the entire log in the link above.
If there is reason to think there is something peculiar about my setup, I am happy to try any suggestions. As I mentioned in my OP, I tried running a couple Beta versions of SGP, but they all exhibited this problem. I have not yet rolled all the way back to the release version, 2.5.1.17.
If you provide any suggestions, I would sure appreciate it!
Thanks,
Craig