![]() I think you need to roll up your sleeves and do the hard and annoying work to determine the cause. I’m not there to see what you’ve done with your setup or why it’s misbehaving. I don’t see how I can help you any further. Again, the guide star was never restored to its lock position. After about 3 minutes, the guiding assembly made another huge excursion in Dec, but this time to the north. THE PRIOR CALIBRATION WAS APPARENTLY FINE AND ADJUSTMENT FOR THE MERIDIAN FLIP WAS FINE.ħ. During this 3-minute period, some south guide commands were issued and the mount responded correctly. ![]() At 00:01, you started another guiding session and the guiding went fine for about 3 minutes. There were zero south guiding commands issued during this time – these moves were simply a continuation of your original mechanical problem in step 4.Ħ. 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. Did you look at the arrow? There were no guide commands issued when this occurred and the Dec motor wasn’t running. That is what I explained in the previous message. Then something caused the guiding assembly to make an abrupt move to the south. PHD2 adjusted the calibration data correctly and things went fine for about 5 minutes. 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. You stayed in that location for another 15 minutes letting the system guide, and the guiding was fine.Ĥ. ![]() 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.ģ. THIS WAS THE LAST CALIBRATION OF THE SESSION.Ģ. You did a calibration at 23:04 that looked ok. Now I will walk you through the exact sequence of things that happened in the log you sent for April 4:ġ. 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. 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. 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. #CANT RUN PHD AND STELLARIUM TELESCOPE CONTROL TIE MANUAL#You have to do a whole sequence of manual meridian flips working through a full range of pointing positions. 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. The fact that your problems emerge after a meridian flip is a strong clue. 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. 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. 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. ![]() That’s a very common beginner mistake because it’s hard to get this right. I have no doubt you made a good attempt at cable management and you’re convinced it’s exactly right. I think you’re in denial about the problem and aren’t remembering/characterizing your experience accurately. Imaging and guiding is a difficult undertaking and most people go through a lot of trouble-shooting to get things working correctly. ![]() You will probably need to start using the LogViewer tool to sort through basic problems like this: 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. But anything that touches the scope or interferes with the tracking by even a tiny amount can cause these large excursions. 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. Something external to PHD2 caused the mount/scope to suddenly lurch by a huge amount to the south:Ī common reason for this is a cable that hasn’t been routed correctly and starts to pull or drag at various pointing positions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |