HELP!!! Terrified by not getting PHD2 to track!

[uhb1966]

Guys and girls, I desperately need your help!

Last night I spent hours trying to get PhD2 to track. I must admit that I not know what to do.

The problem: the guiding cam's picture continuously moves to the south, fast (about 5 microns evry 3-5 seconds) - i suspect a PA eror - BUT astrotortilla claims that my pa error is only 8 minutes- according to a pa error calculation site, this is insane- maybe astrotortilla is computing the pa error incorrectly?

Which errors did i check?

• I do know that PhD two is connected correctly to the mount.
• I can hear the motors running when i manually correct the position.
• According to Astrotortilla, my PA error is approx. 8 minutes.
• The mount is connected via ASCOM drivers.
• The guiding rate was too low at first (0.1x the sidereal rate; corrected that to 0.9x the sidereal rate)
• The focal length of the guide scope is correctly set up (162 mm)
• PHD2 is set up to immediately correct.
• Target was NGC 6992 yesterday night at around 0130CEST.
• When the problem was most critical, 6992 was at max. 72 deg altitude.

===> From my limited knowledge, it looks like the PA is so far off that PHD2 cant correct it... but with 8 min PA error???

I am pasting my settings:

Plus two iterations of my log?!

 

01:28:10.645 00.000 3856 Worker thread wakes up
01:28:10.645 00.000 3856 worker thread servicing REQUEST_EXPOSE 1500
01:28:10.645 00.000 3856 Handling exposure in thread
01:28:10.661 00.016 4044 IsSlewing returns 0
01:28:10.661 00.000 4044 IsGuiding returns 0
01:28:10.661 00.000 4044 Movement stopped - continuing
01:28:10.692 00.031 4044 PulseGuide returned control before completion, sleep 483
01:28:11.177 00.485 4044 IsGuiding returns 1
01:28:11.177 00.000 4044 scope still moving after pulse duration time elapsed
01:28:11.192 00.015 4044 IsSlewing returns 0
01:28:11.192 00.000 4044 IsGuiding returns 1
01:28:11.208 00.016 4044 IsSlewing returns 0
01:28:11.208 00.000 4044 IsGuiding returns 1
01:28:11.239 00.031 4044 IsSlewing returns 0
01:28:11.239 00.000 4044 IsGuiding returns 1
01:28:11.255 00.016 4044 IsSlewing returns 0
01:28:11.255 00.000 4044 IsGuiding returns 1
01:28:11.270 00.015 4044 IsSlewing returns 0
01:28:11.270 00.000 4044 IsGuiding returns 1
01:28:11.302 00.032 4044 IsSlewing returns 0
01:28:11.364 00.062 4044 IsGuiding returns 1
01:28:11.380 00.016 4044 IsSlewing returns 0
01:28:11.380 00.000 4044 IsGuiding returns 1
01:28:11.395 00.015 4044 IsSlewing returns 0
01:28:11.395 00.000 4044 IsGuiding returns 1
01:28:11.427 00.032 4044 IsSlewing returns 0
01:28:11.427 00.000 4044 IsGuiding returns 1
01:28:11.442 00.015 4044 IsSlewing returns 0
01:28:11.442 00.000 4044 IsGuiding returns 1
01:28:11.458 00.016 4044 IsSlewing returns 0
01:28:11.458 00.000 4044 IsGuiding returns 1
01:28:11.489 00.031 4044 IsSlewing returns 0
01:28:11.489 00.000 4044 IsGuiding returns 1
01:28:11.505 00.016 4044 IsSlewing returns 0
01:28:11.505 00.000 4044 IsGuiding returns 1
01:28:11.520 00.015 4044 IsSlewing returns 0
01:28:11.520 00.000 4044 IsGuiding returns 1
01:28:11.552 00.032 4044 IsSlewing returns 0
01:28:11.552 00.000 4044 IsGuiding returns 1
01:28:11.614 00.062 4044 IsSlewing returns 0
01:28:11.645 00.031 4044 IsGuiding returns 0
01:28:11.645 00.000 4044 scope move finished after 500 + 486 ms
01:28:11.645 00.000 4044 Move returns status 0, amount 500
01:28:11.645 00.000 4044 scope calibration move dir= 2 dur= 500
01:28:11.645 00.000 4044 Move(2, 500, 0)
01:28:11.645 00.000 4044 Guiding  Dir = 2, Dur = 500
01:28:11.645 00.000 4044 IsSlewing returns 0
01:28:11.645 00.000 4044 IsGuiding returns 0
01:28:11.677 00.032 4044 PulseGuide returned control before completion, sleep 480
01:28:12.161 00.484 4044 IsGuiding returns 1
01:28:12.161 00.000 4044 scope still moving after pulse duration time elapsed
01:28:12.177 00.016 4044 IsSlewing returns 0
01:28:12.177 00.000 4044 IsGuiding returns 1
01:28:12.208 00.031 4044 IsSlewing returns 0
01:28:12.208 00.000 4044 IsGuiding returns 1
01:28:12.223 00.015 4044 IsSlewing returns 0
01:28:12.223 00.000 4044 IsGuiding returns 1
01:28:12.239 00.016 4044 IsSlewing returns 0
01:28:12.239 00.000 4044 IsGuiding returns 1
01:28:12.270 00.031 4044 IsSlewing returns 0
01:28:12.270 00.000 4044 IsGuiding returns 1
01:28:12.286 00.016 4044 IsSlewing returns 0
01:28:12.286 00.000 4044 IsGuiding returns 1
01:28:12.317 00.031 4044 IsSlewing returns 0
01:28:12.317 00.000 4044 IsGuiding returns 1
01:28:12.395 00.078 4044 IsSlewing returns 0
01:28:12.395 00.000 4044 IsGuiding returns 1
01:28:12.427 00.032 4044 IsSlewing returns 0
01:28:12.427 00.000 4044 IsGuiding returns 1
01:28:12.442 00.015 4044 IsSlewing returns 0
01:28:12.442 00.000 4044 IsGuiding returns 1
01:28:12.458 00.016 4044 IsSlewing returns 0
01:28:12.473 00.015 4044 IsGuiding returns 1
01:28:12.489 00.016 4044 IsSlewing returns 0
01:28:12.489 00.000 4044 IsGuiding returns 1
01:28:12.505 00.016 4044 IsSlewing returns 0
01:28:12.505 00.000 4044 IsGuiding returns 1
01:28:12.536 00.031 4044 IsSlewing returns 0
01:28:12.536 00.000 4044 IsGuiding returns 1
01:28:12.552 00.016 4044 IsSlewing returns 0
01:28:12.552 00.000 4044 IsGuiding returns 1
01:28:12.567 00.015 4044 IsSlewing returns 0
01:28:12.567 00.000 4044 IsGuiding returns 1
01:28:12.598 00.031 3856 Exposure complete
01:28:12.598 00.000 4044 IsSlewing returns 0
01:28:12.630 00.032 3856 worker thread done servicing request
01:28:12.677 00.047 4044 IsGuiding returns 0
01:28:12.677 00.000 4044 scope move finished after 500 + 522 ms
01:28:12.677 00.000 4044 Move returns status 0, amount 500
01:28:12.677 00.000 4044 Processing an image
01:28:12.677 00.000 4044 UpdateGuideState(): m_state=6
01:28:12.677 00.000 4044 Star::Find(0x017E0E08, 50, 940, 495)
01:28:12.677 00.000 4044 Star::Find returns 1, X=940.39, Y=496.62
01:28:12.677 00.000 4044 SchedulePrimaryMove(001E2608, x=-2.97, y=7.30, normal=1)
01:28:12.677 00.000 4044 Enqueuing Move request for scope (-2.97, 7.30)
01:28:12.677 00.000 4044 Status Line 0: m=260605 SNR=56.4
01:28:12.677 00.000 3856 Worker thread wakes up

 

 

01:28:12.677 00.000 3856 worker thread servicing REQUEST_MOVE scope dir 0 (-2.97, 7.30)
01:28:12.677 00.000 3856 Handling move in thread for scope dir=0
01:28:12.677 00.000 4044 UpdateImageDisplay: Size=(1280,1024) min=0, max=63744, FiltMin=640, FiltMax=31232
01:28:12.677 00.000 3856 endpoint = (-2.97, 7.30)
01:28:12.677 00.000 3856 CameraToMount -- cameraTheta (1.96) - m_xAngle (-0.52) = xAngle (2.48 = 2.48)
01:28:12.677 00.000 3856 CameraToMount -- cameraTheta (1.96) - (m_xAngle (-0.52) + m_yAngleError (-1.06)) = yAngle (3.54 = -2.74)
01:28:12.677 00.000 3856 CameraToMount -- cameraX=-2.97 cameraY=7.30 hyp=7.88 cameraTheta=1.96 mountX=-6.22 mountY=-3.05, mountTheta=-2.69
01:28:12.677 00.000 3856 Moving (-2.97, 7.30) raw xDistance=-6.22 yDistance=-3.05
01:28:12.677 00.000 3856 GuideAlgorithmHysteresis::Result() returns -6.22 from input -6.22
01:28:12.677 00.000 3856 GuideAlgorithmResistSwitch::Result() returns -3.05 from input -3.05
01:28:12.677 00.000 3856 Move(2, 279, 1)
01:28:12.677 00.000 3856 Guiding  Dir = 2, Dur = 279
01:28:12.677 00.000 3856 IsSlewing returns 0
01:28:12.677 00.000 3856 IsGuiding returns 0
01:28:12.708 00.031 3856 PulseGuide returned control before completion, sleep 262
01:28:12.723 00.015 4044 Resizing image to 506,405
01:28:12.739 00.016 4044 UpdateGuideState exits:m=260605 SNR=56.4
01:28:12.739 00.000 4044 OnExposeCompete: CaptureActive=1 m_continueCapturing=1
01:28:12.739 00.000 4044 ScheduleExposure(1500)
01:28:12.739 00.000 4044 Enqueuing Expose request
01:28:12.739 00.000 4044 scope calibration move dir= 2 dur= 500
01:28:12.739 00.000 4044 Move(2, 500, 0)
01:28:12.739 00.000 4044 Guiding  Dir = 2, Dur = 500
01:28:12.739 00.000 4044 IsSlewing returns 0
01:28:12.739 00.000 4044 IsGuiding returns 1
01:28:12.739 00.000 4044 Entered PulseGuideScope while moving
01:28:12.786 00.047 4044 IsSlewing returns 0
01:28:12.786 00.000 4044 IsGuiding returns 1
01:28:12.786 00.000 4044 Still moving
01:28:12.848 00.062 4044 IsSlewing returns 0
01:28:12.848 00.000 4044 IsGuiding returns 1
01:28:12.848 00.000 4044 Still moving
01:28:12.927 00.079 4044 IsSlewing returns 0
01:28:12.927 00.000 4044 IsGuiding returns 1
01:28:12.927 00.000 4044 Still moving
01:28:12.958 00.031 3856 IsGuiding returns 1
01:28:12.958 00.000 3856 scope still moving after pulse duration time elapsed
01:28:12.973 00.015 4044 IsSlewing returns 0
01:28:12.973 00.000 4044 IsGuiding returns 1
01:28:12.973 00.000 4044 Still moving
01:28:12.989 00.016 3856 IsSlewing returns 0
01:28:12.989 00.000 3856 IsGuiding returns 1
01:28:13.005 00.016 3856 IsSlewing returns 0
01:28:13.005 00.000 3856 IsGuiding returns 1
01:28:13.036 00.031 3856 IsSlewing returns 0
01:28:13.036 00.000 4044 IsSlewing returns 0
01:28:13.036 00.000 3856 IsGuiding returns 1
01:28:13.036 00.000 4044 IsGuiding returns 1
01:28:13.036 00.000 4044 Still moving
01:28:13.052 00.016 3856 IsSlewing returns 0
01:28:13.052 00.000 3856 IsGuiding returns 1
01:28:13.067 00.015 3856 IsSlewing returns 0
01:28:13.067 00.000 3856 IsGuiding returns 1
01:28:13.083 00.016 4044 IsSlewing returns 0
01:28:13.083 00.000 4044 IsGuiding returns 1
01:28:13.083 00.000 4044 Still moving
01:28:13.098 00.015 3856 IsSlewing returns 0
01:28:13.098 00.000 3856 IsGuiding returns 1
01:28:13.114 00.016 3856 IsSlewing returns 0
01:28:13.114 00.000 3856 IsGuiding returns 1
01:28:13.177 00.063 4044 IsSlewing returns 0
01:28:13.177 00.000 4044 IsGuiding returns 1
01:28:13.177 00.000 4044 Still moving
01:28:13.177 00.000 3856 IsSlewing returns 0
01:28:13.177 00.000 3856 IsGuiding returns 1
01:28:13.223 00.046 3856 IsSlewing returns 0
01:28:13.223 00.000 3856 IsGuiding returns 0
01:28:13.223 00.000 3856 scope move finished after 279 + 277 ms
01:28:13.223 00.000 3856 Move returns status 0, amount 279
01:28:13.223 00.000 3856 Move(0, 500, 1)
01:28:13.223 00.000 3856 Guiding  Dir = 0, Dur = 500
01:28:13.223 00.000 3856 IsSlewing returns 0
01:28:13.239 00.016 3856 IsGuiding returns 0
01:28:13.302 00.063 4044 IsSlewing returns 0
01:28:13.302 00.000 3856 PulseGuide returned control before completion, sleep 434
01:28:13.302 00.000 4044 IsGuiding returns 1
01:28:13.317 00.015 4044 Still moving
01:28:13.364 00.047 4044 IsSlewing returns 0
01:28:13.364 00.000 4044 IsGuiding returns 1
01:28:13.364 00.000 4044 Still moving
01:28:13.442 00.078 4044 IsSlewing returns 0
01:28:13.442 00.000 4044 IsGuiding returns 1
01:28:13.442 00.000 4044 Still moving
01:28:13.489 00.047 4044 IsSlewing returns 0
01:28:13.489 00.000 4044 IsGuiding returns 1
01:28:13.489 00.000 4044 Still moving
01:28:13.536 00.047 4044 IsSlewing returns 0
01:28:13.536 00.000 4044 IsGuiding returns 1
01:28:13.536 00.000 4044 Still moving
01:28:13.598 00.062 4044 IsSlewing returns 0
01:28:13.598 00.000 4044 IsGuiding returns 1
01:28:13.598 00.000 4044 Still moving
01:28:13.708 00.110 4044 IsSlewing returns 0
01:28:13.708 00.000 4044 IsGuiding returns 1
01:28:13.708 00.000 4044 Still moving
01:28:13.739 00.031 3856 IsGuiding returns 1
01:28:13.739 00.000 3856 scope still moving after pulse duration time elapsed
01:28:13.755 00.016 4044 IsSlewing returns 0
01:28:13.755 00.000 4044 IsGuiding returns 1
01:28:13.755 00.000 4044 Still moving
01:28:13.770 00.015 3856 IsSlewing returns 0
01:28:13.770 00.000 3856 IsGuiding returns 1
01:28:13.786 00.016 3856 IsSlewing returns 0
01:28:13.786 00.000 3856 IsGuiding returns 1
01:28:13.801 00.015 3856 IsSlewing returns 0
01:28:13.801 00.000 3856 IsGuiding returns 1
01:28:13.817 00.016 4044 IsSlewing returns 0
01:28:13.817 00.000 4044 IsGuiding returns 1
01:28:13.817 00.000 4044 Still moving
01:28:13.833 00.016 3856 IsSlewing returns 0
01:28:13.833 00.000 3856 IsGuiding returns 1
01:28:13.848 00.015 3856 IsSlewing returns 0
01:28:13.848 00.000 3856 IsGuiding returns 1
01:28:13.864 00.016 4044 IsSlewing returns 0
01:28:13.864 00.000 4044 IsGuiding returns 1
01:28:13.864 00.000 4044 Still moving
01:28:13.864 00.000 3856 IsSlewing returns 0
01:28:13.880 00.016 3856 IsGuiding returns 1
01:28:13.895 00.015 3856 IsSlewing returns 0
01:28:13.895 00.000 3856 IsGuiding returns 1
01:28:13.958 00.063 4044 IsSlewing returns 0
01:28:13.958 00.000 3856 IsSlewing returns 0
01:28:13.958 00.000 4044 IsGuiding returns 1
01:28:13.958 00.000 4044 Still moving
01:28:13.958 00.000 3856 IsGuiding returns 1
01:28:13.989 00.031 3856 IsSlewing returns 0
01:28:13.989 00.000 3856 IsGuiding returns 1
01:28:14.005 00.016 3856 IsSlewing returns 0
01:28:14.005 00.000 3856 IsGuiding returns 1
01:28:14.020 00.015 4044 IsSlewing returns 0
01:28:14.020 00.000 4044 IsGuiding returns 1
01:28:14.020 00.000 4044 Still moving
01:28:14.036 00.016 3856 IsSlewing returns 0
01:28:14.036 00.000 3856 IsGuiding returns 1
01:28:14.051 00.015 3856 IsSlewing returns 0
01:28:14.051 00.000 3856 IsGuiding returns 1
01:28:14.067 00.016 4044 IsSlewing returns 0
01:28:14.067 00.000 4044 IsGuiding returns 1
01:28:14.067 00.000 4044 Still moving
01:28:14.067 00.000 4044 Still moving after 1s - aborting
01:28:14.067 00.000 4044 Error thrown from scope_ascom.cpp:568->ASCOM Scope: scope is still moving after 1 second
01:28:14.067 00.000 4044 Error thrown from scope.cpp:544->guide failed
01:28:14.067 00.000 4044 Move returns status 1, amount 0
01:28:14.067 00.000 4044 Throw from scope.cpp:464->Move failed
01:28:14.067 00.000 3856 IsSlewing returns 0
01:28:14.067 00.000 3856 IsGuiding returns 1
01:28:14.098 00.031 3856 IsSlewing returns 0
01:28:14.098 00.000 3856 IsGuiding returns 1
01:28:14.114 00.016 3856 IsSlewing returns 0
01:28:14.114 00.000 3856 IsGuiding returns 1
01:28:14.130 00.016 3856 IsSlewing returns 0
01:28:14.130 00.000 3856 IsGuiding returns 1
01:28:14.145 00.015 4044 Resizing image to 506,405
01:28:14.208 00.063 3856 IsSlewing returns 0
01:28:14.208 00.000 3856 IsGuiding returns 1
01:28:14.223 00.015 3856 IsSlewing returns 0
01:28:14.223 00.000 3856 IsGuiding returns 1
01:28:14.255 00.032 3856 IsSlewing returns 0
01:28:14.255 00.000 3856 IsGuiding returns 0
01:28:14.255 00.000 3856 scope move finished after 500 + 520 ms
01:28:14.255 00.000 3856 Move returns status 0, amount 500
01:28:14.255 00.000 3856 Status Line 1: Ost  6.22 px 279 ms           Norden 3.05 px 500 ms
01:28:14.255 00.000 3856 Ost  6.22 px 279 ms           Norden 3.05 px 500 ms
01:28:14.255 00.000 3856 move complete, result=0
01:28:14.255 00.000 3856 worker thread done servicing request
01:28:14.255 00.000 3856 Worker thread wakes up

 

 

 

 

 

 

 

[D4N]

I'm not used to pulse guiding so it looks different to mine but I'm pretty sure hysteresis shouldn't be zero so try increasing that.

 

Did it calibrate ok?  PHD2 should be able to tell you how good the calibration was.

[uhb1966]

Thank you D4N - No, i believe phd2 didnt even calibrate successfully - You are using the ST4 port? I could use the ST4 as well...

[D4N]

Yeh my mount doesn't seem to like pulse guiding so I always use the ST4 port.

Have a go with ST4, this will at least eliminate any ascom / eqmod issues.

[uhb1966]

Thanks D4N! I also realised my phd2 version was a bit old, and upgraded to the newest version. It also looks like calibration should always be done between +30 and -30 degree... will retry tonight.

[Rush]

Hi,

Hyst,Minimum mo, Not Ok.

Do plug in ST4 and correct the parameters as shown in the picture.

if everything goes well ,you will get a similar graph.

Good luck

CS

Rush

[alacant]

Hi. I think that with anything PHD, you need to start from zero. Use only EQMOD and PHD2. Take everything else out of the equation. Make a new profile and take all default settings. Change nothing. Use drift align to get spot on the pole. Calibrate -somewhere in the top half of Ophiuchus is good ATM- then guide in the same place you calibrated for at least 20 minutes. If it still drifts maybe post a link to the guide log. HTH

[ollypenrice]

I'm another one for ST4 which takes as much extraneous software as possible out of the equation. I'd try to introduce EQMod later, personally.

Connect the camera and choose 'On Camera' for the mount.

8 minutes out on PA seems a lot to me but would it account for the problem? I'd be surprised.

Autoguiders can be incredibly cable-sensitive so I would try replacing all cables.

Olly

[tomato]

I connect via the mount comms to use the drift alignment tool in PHD2 but revert back to the ST-4 port for guiding. It means two lots of calibration but I always seem to achieve more reliable guiding via the ST-4 connection.

Hope you get it sorted.

[Thalestris24]

Hi

If PHD2 doesn't calibrate you need to sort out what the problem is. You can't expect guiding to work properly without a successful calibration. Do run the guiding assistant tool - it will give you hints regarding any systemic problems. Astrotortilla is not very good for polar alignment...

Good luck

Louise

[ollypenrice]

Yes, the guiding assistant is very effective. A long run of a few minutes for it to do its thing has worked superbly for me.

Olly

[uhb1966]

First, a big thanks to everybody!

To be honest, I believe you are right - Astrotortilla's PA seems to get a bit touchy below 30 arcminutes. So i think i'll just use it for getting my error below 1 degree (i dont have a visual on the north star), and then try the PHD2 drift alignment from there next night.

Thanks again!!!

[ollypenrice]

I do this for pleasure and for a living. What is the least reliable part of my technological life? Software. In second place? Software. In the next ten places? Yes, I don't want to become even more boring than usual so I leave you to guess.

To dift align to a very high degree of precision for AP you need a mount, a lens, a camera and a sky. You do NOT need.... etc etc etc.

Olly

[uhb1966]

Olly, youre probably right

 

[ollypenrice]

19 minutes ago, uhb1966 said:

Olly, youre probably right

 

We had a rare trailing problem recently which I put down to a shift in PA caused by a human bump or something like that. Or maybe a heave in the underlying ground beneath the base. Tom and I ran a classical drift test and after ten minutes got bored waiting for the star to drift by a visible fraction of a pixel. That was in the south. East was the same. We tried a 30 min test sub. Perfect. Whatever had affected our long subs previously had gone away. That's AP for you...

Olly

[Thalestris24]

1 hour ago, ollypenrice said:

I do this for pleasure and for a living. What is the least reliable part of my technological life? Software. In second place? Software. In the next ten places? Yes, I don't want to become even more boring than usual so I leave you to guess.

To dift align to a very high degree of precision for AP you need a mount, a lens, a camera and a sky. You do NOT need.... etc etc etc.

Olly

I think the phd2 drift align tool is actually very good and easy to use, Olly!

Louise

[ollypenrice]

1 minute ago, Thalestris24 said:

I think the phd2 drift align tool is actually very good and easy to use, Olly!

Louise

Yes, I tried it and it was fine. However, I have about twice the resolution in my imaging camera. The real question is - if it isn't fine why is it not fine? - and at this point being 'software minimalist' is an advantage. Well, for me at least, but I'm stone age.

Olly

[Thalestris24]

4 minutes ago, ollypenrice said:

Yes, I tried it and it was fine. However, I have about twice the resolution in my imaging camera. The real question is - if it isn't fine why is it not fine? - and at this point being 'software minimalist' is an advantage. Well, for me at least, but I'm stone age.

Olly

Me, I'm all for tools that make life easier! Of course, Hubble managed to do an awful lot with glass photo plates... 

[uhb1966]

Oh my, the REAL Hubble!

 

[uhb1966]

Dear all,

thanks a lot for your suggestions!!! PHD2 drift align did the trick!

However, for phd2 to calibrate effectively, you need to calibrate on star close to the celestial equator first. I use +3 degree now.

It really looks like AT's alignment procedure does not always give reproducible results- it is sometimes measuring the very same position up to 10 arcminutes different.

With PHD2, i got below 1 arcsec on the second try:

 

[Tiny Small]

On ‎09‎/‎08‎/‎2016 at 21:35, Thalestris24 said:

I think the phd2 drift align tool is actually very good and easy to use, Olly!

Louise

I tried using this last night (couldn't finish due to cloud). My impression is that it is extremely accurate but my word, it's a slow process. I'm very tempted to put my slr on the scope and do it the traditional way. Much quicker, though probably not as accurate.

[tomato]

Like most things it gets easier with practice. If you are using PHD through the mount  comms you get the magenta circles to tell you roughly how far to adjust the mount. In my experience these aren't terribly accurate, but you soon home in on how much to turn the adjusters on your respective mount to correct the error. I generally find it a bit quicker than the classic ' watch the star move off the reticle crosshairs' approach.

[uhb1966]

20 minutes ago, tomato said:

Like most things it gets easier with practice. If you are using PHD through the mount  comms you get the magenta circles to tell you roughly how far to adjust the mount. In my experience these aren't terribly accurate, but you soon home in on how much to turn the adjusters on your respective mount to correct the error. I generally find it a bit quicker than the classic ' watch the star move off the reticle crosshairs' approach.

In my (second) try, i was faster on 1arsec with phd2 then on 20 arcmin with AT... it took my maybe 20 minutes. Could have been faster if i had known from the start which direction to turn

[Thalestris24]

3 hours ago, Tiny Small said:

I tried using this last night (couldn't finish due to cloud). My impression is that it is extremely accurate but my word, it's a slow process. I'm very tempted to put my slr on the scope and do it the traditional way. Much quicker, though probably not as accurate.

Hi

It should only take about 5-8 mins or so on each axis to get it good enough for guided imaging. You only need to do 1 sec exposures in order to get a quick response. Don't waste time and effort trying to be 100% accurate. A slight drift is not necessarily a bad thing 

Louise