Guiding failed after meridian flip

Sequence Generator
1

Hello,
as I was running a session yesterday evening, it ended up failing in the middle of the night with a meridian flip .
After meridan flip, phd2 (v2.6.5) don’t start to guide:

[05/20/18 02:32:37.437][DEBUG] [Telescope Thread] Scope solve complete…
[05/20/18 02:32:37.437][DEBUG] [Telescope Thread] SGM_TELESCOPE_SOLVE message complete…
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Meridian flip: Scope solve complete…
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Meridian Flip: Solve was Successful
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Meridian Flip: Stopping the Auto Guider
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Attempting to stop PHD2 guiding…
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Checking PHD2 state…
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[05/20/18 02:32:37.447][DEBUG] [Pier Flip Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}

[05/20/18 02:32:37.547][DEBUG] [Pier Flip Thread] PHD2 GetPhdStatus - Post-Wait: Guiding
[05/20/18 02:32:37.547][DEBUG] [Pier Flip Thread] Sending to PHD2:
{“method”: “stop_capture”, “id”: 1004}

[05/20/18 02:32:37.547][DEBUG] [Pier Flip Thread] Checking PHD2 state…
[05/20/18 02:32:37.547][DEBUG] [Pier Flip Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[05/20/18 02:32:37.547][DEBUG] [Pier Flip Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}

[05/20/18 02:32:37.647][DEBUG] [Pier Flip Thread] PHD2 GetPhdStatus - Post-Wait: Guiding
[05/20/18 02:32:38.647][DEBUG] [Pier Flip Thread] Checking PHD2 state…
[05/20/18 02:32:38.647][DEBUG] [Pier Flip Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[05/20/18 02:32:38.647][DEBUG] [Pier Flip Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}

I have put the SGP log and the two PHD2 logs into a drop box:
https://www.dropbox.com/s/6sy507efj8m1dbf/sg_logfile_20180519204945.txt?dl=0

2

Could you share the link to the PHD2 log files? The link goes to the SGP log.

3

Hello Andy,
There are the links to PHD2 log files : https://www.dropbox.com/s/a54duu4hd4kku2g/PHD2_DebugLog_2018-05-19_205251.txt?dl=0

https://www.dropbox.com/s/fun46njw232lg8c/PHD2_GuideLog_2018-05-19_205251.txt?dl=0

Thanks

4

It seems that the problem is probably caused by an incorrect reporting of the side of pier by the ASCOM driver(s). I see from the debug log that you are using EQASCOM indirectly through the POTH ASCOM hub driver.

Is there some reason that you need to go through POTH rather then connecting to EQASCOM directly?

In the EQASCOM driver setup do you have the SideOfPier setting set to “Pointing (ASCOM)”? EQASCOM Settings · OpenPHDGuiding/phd2 Wiki · GitHub

Andy

5

Is there some reason that you need to go through POTH rather then connecting to EQASCOM directly?_
Yes because sgepro is also connected on eqmod and i think it’snt possible tout connect sgepro and phd2 directly to eqascom (But can be am I in the error)

In the EQASCOM driver setup do you have the SideOfPier setting set to “Pointing (ASCOM)”?
Yes

Thanks

6

Most ASCOM telescope drivers allow multiple simultaneous connections. I would ditch POTH and try that.

Thanks,
Jared

7

Thanks Jared,
Next time, i will try to connect directly.