Sudden loss of guidance ... incomprehensible

374 views
Skip to first unread message

Dominique DANIEL

unread,
Apr 4, 2021, 6:22:55 PM4/4/21
to Open PHD Guiding
Hello
after more than an hour of very good guidance, and recovery after the meridian flip. The guidance remains good 10 or 20 minutes more, then  PHD2 was no longer able to follow the star. External conditions have not changed. At the start of the evening, I did a PEC training with CPWI, then I used the guidance assistant. Guidance remained good for an hour and then suddenly deteriorated. I stopped PHD2 and restarted it. Guidance resumed normally, and well, then again lost the star (although very present).
What is going on ? what to do?
I am using a CGX. Of course, the "inversion of Dec" option was activated.
Here is the log file.

Thanks for your help!
Best, Dominique

Bruce Waddington

unread,
Apr 6, 2021, 11:47:02 AM4/6/21
to open-phd...@googlegroups.com

Something external to PHD2 caused the mount/scope to suddenly lurch by a huge amount to the south:

 

 

A common reason for this is a cable that hasn’t been routed correctly and starts to pull or drag at various pointing positions.  At the point of the red arrow above, the Dec motor on the mount wasn’t running at all, which is the normal case during basic sidereal tracking.  But anything that touches the scope or interferes with the tracking by even a tiny amount can cause these large excursions.  Guiding is a very precise business – on your setup, a measured movement of 10 arc-sec corresponds to 20 microns of movement at the guide camera sensor, less than ½ the thickness of a human hair.

 

You will probably need to start using the LogViewer tool to sort through basic problems like this:

 

https://openphdguiding.org/phd2-log-viewer/

 

https://openphdguiding.org/tutorial-analyzing-phd2-guiding-results/

 

Imaging and guiding is a difficult undertaking and most people go through a lot of trouble-shooting to get things working correctly.

 

Good luck,

Bruce

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/787825f1-8fb9-4cfa-a054-03d459820461n%40googlegroups.com.

image001.png

Dominique DANIEL

unread,
Apr 6, 2021, 5:04:55 PM4/6/21
to open-phd...@googlegroups.com
Thanks Bruce,
Before that, considering your last advises,  I have reorganised all the cabling system. I also replaced my laptop pc ( connected with  powered USB Hub to 5 meters - 2 USB 3 for cameras and one USB 2 for the mount) with a small one attached to the pier with 2 meters cables. I pay a particular attention at the free movements of the mount. I always stay very closed to the mount, looking at all components during meridian flip.I spend a lot of time and efforts on that. The problem happens only after a meridian flip, never before (I've experienced several hours of guiding). And if I recalibrate PHD guiding (after the flip), the problem disappears. So I think it comes from PHD2, not from the setup (a CGX on a fixed pier!). 
I have also used NINA supervising the setup (included guiding with PHD2). Informations given about the telescope are exact (good side of the pier), and NINA manage correctly the meridian flip... Even in this case, the problem occurs after some minuts. The error message is something like "PHD2 is not able to correct enought ..." 
Before the derivative, polar alignment precision was 17'', and RMS 1.5''...
I use this mount from september 2020, of course on two sides! The problem has appeared some weeks ago, when I wanted to image exoplanet transit, with a flip (manual the first times, the objective is to automatise with NINA). The other software used are SharpCap (or NINA) for imaging, and CPWI for mount managment.
Where is the devil is hiding?
Best, Dominique

You received this message because you are subscribed to a topic in the Google Groups "Open PHD Guiding" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-phd-guiding/nxxppKhHifQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/000f01d72afc%241476bc90%243d6435b0%24%40earthlink.net.

Bruce Waddington

unread,
Apr 6, 2021, 11:42:06 PM4/6/21
to open-phd...@googlegroups.com

I think you’re in denial about the problem and aren’t remembering/characterizing your experience accurately.  I have no doubt you made a good attempt at cable management and you’re convinced it’s exactly right.  That’s a very common beginner mistake because it’s hard to get this right.  What often happens is that people use a lot of cable ties, get a nice cable loom that’s fastened on the mount somewhere and it’s very tidy, looks very professional.  And it works fine 95% of the time.  But if one of the cables in the bundle is slightly shorter, the scope can move into a position where it pulls because it can’t move enough to create slack.  That’s just one of dozens of possibilities – maybe there’s a projection or a knob on the mount that the cable is looped around.  The fact that your problems emerge after a meridian flip is a strong clue.  You probably need to invest at least a full night’s work on this – forget imaging, forget using NINA, forget anything but eliminating this problem.  You have to do a whole sequence of manual meridian flips working through a full range of pointing positions.  In your case, you can start at a known problem point – a meridian flip at Dec = 21 degrees, then let the mount track for about 5 minutes.  You can’t do this during the daytime and only guiding will show the problem – as I said, you aren’t going to see movements of 20 microns.  Of course, you won’t want to do any of this until you get past the notion that it’s a PHD2 problem – IT ISN’T.

 

Now I will walk you through the exact sequence of things that happened in the log you sent for April 4:

 

1.        You did a calibration at 23:04 that looked ok.  THIS WAS THE LAST CALIBRATION OF THE SESSION.

2.        At 23:05, you started a 15 minute Guiding Assistant session at a pointing position of RA = 10.33 hr, Dec = 21.8 deg, side-of-pier = west. 

3.       You stayed in that location for another 15 minutes letting the system guide, and the guiding was fine.

4.       At 23:47, you did a meridian flip and started another guiding session in the same pointing position but with the side-of-pier now east.  PHD2 adjusted the calibration data correctly and things went fine for about 5 minutes.  Then something caused the guiding assembly to make an abrupt move to the south.  That is what I explained in the previous message.  Did you look at the arrow?  There were no guide commands issued when this occurred and the Dec motor wasn’t running.  This move was not caused by PHD2.

5.       Staying in the same pointing position, you then attempted four short guiding sessions in which the guide star continued to make huge excursions to the south.  There were zero south guiding commands issued during this time – these moves were simply a continuation of your original mechanical problem in step 4.

6.       At 00:01, you started another guiding session and the guiding went fine for about 3 minutes.  During this 3-minute period, some south guide commands were issued and the mount responded correctly.  YOU DID NOT RECALIBRATE.  THE PRIOR CALIBRATION WAS APPARENTLY FINE AND ADJUSTMENT FOR THE MERIDIAN FLIP WAS FINE.

7.       After about 3 minutes, the guiding assembly made another huge excursion in Dec, but this time to the north.  Again, the guide star was never restored to its lock position. 

 

I don’t see how I can help you any further.  I’m not there to see what you’ve done with your setup or why it’s misbehaving.   I think you need to roll up your sleeves and do the hard and annoying work to determine the cause.  If you have any doubt about the correct setting of ‘reverse-dec-after-meridian-flip’, you should re-run the ‘Calibrate meridian flip’ wizard, being extremely careful to do exactly what is says.

image001.png

Dominique DANIEL

unread,
Apr 7, 2021, 4:10:26 AM4/7/21
to open-phd...@googlegroups.com
Hello Bruce
thank you again for all the attention and advice you give me. It is very very precious. In particular the analysis on the behavior of PHD2. I sent you the log of only one evening, but the observations made relate to several evenings (in particular for the recalibrations). After the overhaul of the wiring, I focused on the setting of PHD2. You have ruled out that it could be the cause of the failure. I will focus on the wiring again. I understood that the cause may seem ridiculous. A question remains: why does the failure occur after a few minutes and not immediately after the turnaround? Maybe there is a link with the elasticity of a cable? However if I recalibrate PHD2 the guidance becomes normal again.
It's a shame that the weather is ticking..I'm hurried to carry out these new tests .. I'll keep you informed if I find it ..
It is very precious to have you in support in this way. Thanks again.
Dominique

Bruce Waddington

unread,
Apr 7, 2021, 1:25:03 PM4/7/21
to open-phd...@googlegroups.com

The delay can be random depending on the scope’s pointing position.  Elasticity in the cable loom is definitely a possibility but it could also happen if the loom is getting blocked by some mechanical projection on the mount like a knob or some other fixture.  If you still think that the problem is always resolved by re-calibrating – I haven’t seen any data to support that – you should by all means re-run the ‘Calibrate Meridian Flip’ wizard doing exactly as it says.  Meridian flip adjustments in PHD2 have been around for as long as PHD2 has, it’s used by thousands of people every month so it works.

 

Hope you can track it down,

image001.png

Dominique DANIEL

unread,
Apr 15, 2021, 9:41:52 AM4/15/21
to Open PHD Guiding
Hello Bruce, here I am again. The good weather returned and I resumed my tests and still have not solved the problem.
I may have an idea where the problem comes from: during the calibration of the inversion, the calibration model is very bad: orthogonality error of 74 °!
Here are all the operations carried out, after installing 2.6.9dev4
- near 40 "polar alignment with SharpCap
- calibration of the PHD guidance (very good orthogonality)
- guidance test for a few minutes: excellent
- assistant guiding tool confirm (187 sec later) RMS erroe 0.57 arcsec polar error 1.8 arcmin.
- manual meridian flip (via CPWI)
- unable to resume guidance (PHD2 does not know how to correct telescope movements)
- reloading of the pointing model
- normal calibration
- calibration of the meridian flip (orthogonality error of 74 °). and the message "attention, calibration completed but few guidance steps were used. check DEC output option etc ..". I never had this message when "normal" calibrations
- meridian flip execution (manual)
- unable to resume guidance (PHD2 does not know how to correct telescope movements)
- new calibration on the same side of the pier (very good orthogonality)
- guidance during one hour of shooting: very good
I really do not believe that there is an obstacle to the mobility of the telescope. All calibrations were made at a position close to the equator. The option "invert the DEC output after reversal" is activated.
I join a printscreen of orthogonality error.

10 days ago, I image a 4 hours exoplanet transit (without meridian flip): guidage was excellent (and every thing)


does this give you more ideas?

Bests, Dominique
14avr PHD erreur orthogonalité en calib retournement.png

Bruce Waddington

unread,
Apr 16, 2021, 11:20:00 PM4/16/21
to open-phd...@googlegroups.com

Have you run the Meridian flip calibration wizard or are you just guessing at the setting?   It looks like the CPWI software has lots of settings dealing with meridian flips so I suggest you take this up with one of the Celestron forums.  There are 100’s of users who use CPWI and don’t have this problem with PHD2, so I think you’ll get better help elsewhere.  Sorry, I don’t have anything else to suggest.

Dominique DANIEL

unread,
Apr 17, 2021, 2:25:16 AM4/17/21
to open-phd...@googlegroups.com
OK Bruce I will do that.
But I think they will say that CPWI has nothing to see with PHD2 bad meridian flip calibration (74° orthogonal error) when normal calibration is good.
Dominique 

Dominique DANIEL

unread,
Apr 17, 2021, 5:54:13 PM4/17/21
to Open PHD Guiding
Hi Bruce I realize that I haven't answer to your question: yes I run the meridian calibration wizard from A to Z, successfully, but with the comment (that I translate in english): "Attention, calibration completed but few guidance steps were used. Check if the option "invert DEC output" in the advanced dialog box is false, and check if there is a problem with the mount "
Dominique
PS: I also post the issue on Cloudy Nights (celestron discussion) and teamcelestron.com forum.

Dominique DANIEL

unread,
Apr 19, 2021, 7:49:55 AM4/19/21
to Open PHD Guiding
Hello Bruce,

here Inspector Dominique who is leading the investigation! Big news: I am not alone in this case: I found 3 other astrams on Webastro (follow the attached link - in French but Google Translate does the job well!). They are with EQ6 and EQ8 (and GSS) that they have exactly the same problem. It seems to me that this seriously brings suspicion on PHD2 !! Hmm hmm ... So they deactivate the DEC inversion on reversal. We all use NINA (the problem also happens without NINA) and want to completely automate a session.
 I use a CGX thru CPWI. They use EQ6 or 8 thru GSS. On my opinion that brings the problem out of CPWI and GSS.. and the mounts.
 A workaround would be to re-calibrate PHD2 after flipping. But I'm afraid NINA will just restart guidance, which shouldn't cause a new calibration. How to do?
My analyse is that the "meridian flip calibration" wizard does'nt do the job.
And for the moment, I have no response from Celestron (celestronteam.com and CloudyNights).
Best, Dominique

https://www.webastro.net/forums/topic/179360-alternative-%C3%A0-eqmod-gs-server/page/2/?tab=comments#comment-2879273

Dominique DANIEL

unread,
Apr 19, 2021, 5:40:24 PM4/19/21
to Open PHD Guiding
Last news after tonight test: it works!! the solution: 
1. desactivate "inverse DEC at meridian flip"
2. no "meridian flip calibration"
I suppose there is a conflict between actionable parameters and automatic ones...
The other change was that I disconnect Stellarium from CPWI. I suppose that there is no effect.. but it's the observation.
I suggest to improve documentation and comments about the good usage of "inverse dec .." and about the calibration at meridian flip tool.
I will do others tests to confirm this experience.

Dominique

Reply all
Reply to author
Forward
0 new messages