PHD2 won't pause during AF runs


#1

I’ve been advised to try pausing the autoguider during focus runs since I use an OAG and have a standard (ie, mirror-shifting) SCT. So I checked “pause guiding during autofocus,” but PHD2 is still running and issuing move commands, to which the mount seems to be responding. Any idea what I’m doing wrong? SGP 2.4.1.10, PHD2 2.5.0. The SGP log, PHD guide log, and PHD2 debug logs are here:

https://dl.dropboxusercontent.com/u/58468743/sg_logfile_20150611222115.txt
https://dl.dropboxusercontent.com/u/58468743/PHD2_GuideLog_2015-06-11_222459.txt
https://dl.dropboxusercontent.com/u/58468743/PHD2_DebugLog_2015-06-11_222459.txt

Kevin


#2

Hi Kevin,

I see in the SGP log two attempts to pause PHD2, at 10:50PM and 10:56PM.

[6/11/2015 10:50:00 PM] [DEBUG] [Camera Thread] Pause guiding during AF is active, pause command sent, waiting for guider to pause... [6/11/2015 10:50:00 PM] [DEBUG] [Camera Thread] Tried to pause guider for AF, but failed on timeout, continuing AF anyhow...

[6/11/2015 10:56:14 PM] [DEBUG] [Camera Thread] Pause guiding during AF is active, pause command sent, waiting for guider to pause... [6/11/2015 10:56:14 PM] [DEBUG] [Camera Thread] Tried to pause guider for AF, but failed on timeout, continuing AF anyhow...

But in the PHD2 log, the last communication from SGP was at 10:37 PM, and there was no further communication after that until SGP disconnected at 11:04PM.

22:37:38.300 00.001 3080 evsrv: cli 00B96530 response: {"jsonrpc":"2.0","result":"Guiding","id":1001} 23:04:18.376 00.537 3080 evsrv: cli 00B96530 disconnect

In other words, PHD2 did not receive the pause requests from SGP. I think we need Ken or Jared to look into it at this point.

Andy


#3

Hi Kevin,

I have used “pause guiding during autofocus” without issues. My last imaging session was with SGP 2.4.1.7 and one or two revisions before 2.5.0 for PHD2. This was on April 18.

Peter


#4

Thanks for looking at this, Andy. Hopefully Ken and Jared will see an easy fix. Peter, thanks for the input.

Kevin


#5

@astrovienna @Andy The message Andy posted is misleading, but this is not a bug. You aborted your sequence at

[6/11/2015 10:37:42 PM] [DEBUG] [Main Thread] User requested sequence abort...  

It is our policy that SGPro does not talk to the guider unless a sequence is running.


#6

…meaning the message in the SGP log was misleading in this case (and not that my message responding to Kevin was misleading… right?)

Thanks for tracking it down, Ken.

Andy


#7

Thanks Ken. I just checked that out, and it worked fine.


#8

Yes sorry… bad phrasing on my part. I mean the log message is bad and no timeout actually occurred. I have changed it so it is more appropriate.


#9

no problem, thanks.


www.mainsequencesoftware.com