If you are an electrical engineer, these parameters are more or less like loop gain of a feedback system.
There are just two other parameters that ASIAIR allows you to change, and that is the RA and DEC aggressiveness. Just tune the values so that ASIAIR can keep up with periodic error of your particular mount. On the other hand, you don't want the max step to be too large in case some noise occurs that causes ASIAIR to overcorrect like crazy. You don't want a max step to be too small since you may not be able to keep up with correcting the PE. (Not just the model, but the mount itself, how badly unbalanced, insufficient torque,etc). The Max DEC and RA steps depends on your particular mount. Cone error of the guide scope can produce non orthogonality too, so keep that in mind. The same is true if the Info panel in the Autoguide window shows red and blue lines that are radically non-orthogonal. If the North-South and East-West have radically different number of steps, you need to check your mount for problems. Rinse and repeat until the number of steps in North-South and East-West each has between 12 and 25 steps or so. If you find that it finishes with fewer than 12 steps, go and reduce the Calibration step parameter and do another calibration. I believe PHD2 recommends at least 12 steps. Notice how many steps it takes to finish the North-South and East-West calibrations (it tries to move 25 pixels total in each direction before reversing). Stay some 30 degrees away from pole and 60 degrees from the horizon, and you are probably fine. Do not use a star too close to the poles, or too close to the horizon. This parameter will depend on the focal length of your guide scope and the pixel size of the guide camera, so you need to redo when you change either of them.įirst, pick the guiderate that you want and do a calibration pass. If the Calibration steps are too fine, you would have to wait a long time to calibrate each time, but there is really not too much harm there than wasting time. If the calibration steps are too coarse, you will end up with imprecise calibration and get "jumpy" guide graphs. It determines the stepping size PHD2 uses when it is executing the calibration process. Next is the easiest one, but you need to spend a few minutes to tune it one time. For high end mounts with small PE and PE slope, you can probably back the guide rate down to 0.25x and still guide successfully. This parameter is in your Telescope Setup window (in the case of my mount, the parameter is not sticky, and I need to change it every time I boot up ASIAIR). For other mounts, just stick with the default 0.5x rate.
These mounts also require very short guide updates (short guide exposure times). For mounts that have large slope for the periodic error (PE), like the Avalon M-zero and RainbowAstro mounts, you would want to choose the 0.9x rate so that you have enough speed to "chase down" the error.
The following might get you by until (if?) there is a guide assistant in ASIAIR.įirst is the guide rate. PHD2.5 good for Orion StarShoot Autoguiderįor the detail of the bug, it can be found here PHD2.Given the limited flexibility of the ASIAIR autoguiding, it is not that difficult to manually come up with a decent guiding parameter set that matches your own situation. Here’s a link to a previous version that I’m not sure where to find it and that’s the reason I’m sharing it here. There’s a problem with Orion StarShoot Autoguider as I have already reported that it wasn’t able to find the camera and fails to continue and hung up. I have managed to compile it and it’s available for download.
#ASTROGUIDER VS PHD2 MAC OSX#
The new version of PHD 2.5 that you can download on the main site (at the time of this blog) gives some problem to users using Mac OSX version 10.11 (El Capitan) because the available downloadable package was compiled with lower version of OSX.
#ASTROGUIDER VS PHD2 MAC OS X#
If you are getting this error “PHD2 instance 1 is already running” on a Mac OS X El Capitan, you need a version of PHD2.5 that is compiled with the latest OS Version.
0 kommentar(er)
