Now when I go to the second image, I get 2 minute “resuming the autoguider message” Is there anyway to speed this up? Thanks. Rick
What exactly is happening when it says "resuming the auto guider?"
Here are the pertinent logs.
Parameter name: value
[10/14/2015 12:28:44 AM] [DEBUG] [Sequence Thread] Handling monitoring event (Good Night System, Status).
[10/14/2015 12:28:44 AM] [DEBUG] [Sequence Thread] GNS: Sent status message to GNS ((crescent nebula-1) Attempting to resume the auto guider (post slew / center)…)…
[10/14/2015 12:28:44 AM] [DEBUG] [Sequence Thread] Handling monitoring event (Email 1, Status).
[10/14/2015 12:28:44 AM] [DEBUG] [Sequence Thread] EmailNotification endpoint: Failed sending email! Value cannot be null.
Parameter name: value
[10/14/2015 12:28:44 AM] [DEBUG] [Sequence Thread] DoEventGroupChange: Slewed or Centered, attempting to start guiding.
[10/14/2015 12:28:45 AM] [DEBUG] [Sequence Thread] PHD2: Auto Resume
[10/14/2015 12:28:45 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/14/2015 12:28:45 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/14/2015 12:28:45 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[10/14/2015 12:28:45 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/14/2015 12:28:46 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/14/2015 12:28:46 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/14/2015 12:28:46 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[10/14/2015 12:28:46 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/14/2015 12:28:47 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/14/2015 12:28:47 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/14/2015 12:28:47 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[10/14/2015 12:28:47 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/14/2015 12:28:48 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/14/2015 12:28:48 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/14/2015 12:28:48 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[10/14/2015 12:28:48 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] {“method”: “guide”, “params”: [{“pixels”: 0.5, “time”: 15, “timeout”: 300}, false ], “id”: 1003}
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
{“method”: “guide”, “params”: [{“pixels”: 0.5, “time”: 15, “timeout”: 300}, false ], “id”: 1003}
[10/14/2015 12:28:49 AM] [DEBUG] [Sequence Thread] PHD2: Attempting to start guiding, waiting for PHD2 settle done message…
[10/14/2015 12:29:03 AM] [DEBUG] [Heartbeat Thread] Handling monitoring event (Email 1, Heartbeat).
[10/14/2015 12:29:03 AM] [DEBUG] [Heartbeat Thread] EmailNotification endpoint: Failed sending email! Value cannot be null.
Parameter name: value
We need the entire log file. It looks like it’s taking a long time to finish settling. Do you have any other information? We should be able to figure it out from the log.
Ok, I figured it out, kind of. I had it set to turn off the autoguider after each sequence. So now, instead of 2 minutes to resume, it takes 30 seconds. But I’m not sure why it would take even 30 seconds. Is this normal? Thanks! Rick
Actually, not. It just hung again.
This time it took over 3 minutes to resume.
1 Like
Here are the logs for that 3 minute resume.
I’m at work and can’t see your logs. What is your dither and min motion set to? My guess is you’re doing a high dither along with it being unable to quickly correct back to position.
It’s a High Dither. Min motion is set to .5. However this is before it tries to settle the autoguider. Thanks.
Here is the PHD2 log too.
nope, that link goes to your SG log.
Andy
Oops, sorry.
Hi Rick,
I think the long settling time is simply a matter of the settling tolerance being set too tight. You have it set to settle at less than 0.5 pixels for 15 seconds. These values say not to consider settling complete unless the guide distance stays below 0.5 pixels for at least 15 seconds.
Your PHD2 guide log shows your total RMS error while guiding is about 0.5 pixels so there are frequently small excursions above 0.5 pixels. That’s why it takes many minutes before there is a 15-second interval where it stays below 0.5 pixels.
I think you will have much better results if you increase your settling tolerance to 1.0 pixels (or 0.75 pixels if you want to be really aggressive).
You may find it informative to look at your PHD2 guide log in PHD2 log viewer. That way you can see the actual performance during settling and guiding and make an informed choice about the settling parameters.
Hope that helps,
Andy
Thanks Andy, I’ll give this a shot. However, I’m still curious as to why it takes so long to “Resume the Autoguider” keeping in mind that only after it resumes does it wait to settle the auto guider (where your settings would then take effect). Rick
Rick,
It’s what he just said. You have your tolerance too tight and the constant’over tolerances’ resets the clock.
Chris
So that would mean that it is trying to settle the guider during the Resume the Autoguider sequence. Then after it “resumes” it shows that it is “settling the auto guider” and gives stats as it is doing it. Seems like something is a bit inconsitent there.
So, the initial ‘resume auto guider’ just checks that it can talk to PHD2. The ‘settling’ is where it brings the guide star back into tolerances for guiding.