The difference between results for the two pointing positions is explained by the geometry of the sky – a given angular error in RA translates into a measured error on the sensor according to 1/cos(Dec). So if we take the 1.05 arc-sec error you got at Dec=-13 and forecast how that translates into error at Dec=53, we get 1.6 arc-sec which is pretty close. This has nothing to do with guiding, it’s just a reflection of RA tracking errors in your mount. Before guiding, what PHD2 sees is this:
So this is roughly a 30 arc-sec peak-peak error that PHD2 is trying to guide out with a frequency signature that looks like this:
The longer-period errors could probably be reduced by getting a high-quality periodic error curve programmed into the mount. The higher frequency components like the 13-sec error are caused by common problems with the EQ spur gears. If you look on this forum and others, you will find explanations of how people have improved on these by fiddling around with the meshing of those gears.
Hope this helps,
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/711f1665-ebdc-4544-a169-5fef12e8f60dn%40googlegroups.com.
Sorry, Yang, I typed the first part of my answer incorrectly. I should have said the 1.05 a-s error you got at Dec=53 corresponds to an expected tracking error of 1.6 arc-sec at Dec=-13. I said it backwards…
Bruce