- Edited
Hello,
I know there are numerous threads on this forum including ones where several users confirmed that short guide exposures with short guide pulses and low aggression settings in ASIAir or PHD2 seem to drastically improve the guiding capabilities of the AM5. Yesterday I had the chance to take my AM5 for the second time to try some of these suggestions since my first attempt was very disappointing. Before getting into the details, please note that my main mount is an ioptron CEM70 with a Evoguide 50 guide scope and an ASI178mm camera. I consistently get sub .4 arcsec rms total error consistently under the seeing conditions in my area.
With this second attempt, I decided to eliminate as many variables as possible so I used the same guide scope on the AM5 setup which is also carrying an Askar 80PHQ with a PO Ares-c camera...total weight about 6 KG. The setup including the guide scope was bench balanced, marked, and mounted on the AM5 so that the COM is approximately aligned with the centre of the dovetail plate of the mount.
As you'll see in the attached log, I tried an imaging sessions with very fast guide exposures and lower than default guide pulse aggression settings and was getting the same results as I was on the first night, around .9 arcsec rms total error. I then decided to perform shorter guide runs starting with default settings and changing one parameter at a time to see how the mount is behaving. Each 10 minute run started in the same Alt/Az point very near the zenith to minimize atmospheric effects.
My conclusion from what I saw is while the AM5 benefits greatly from short guide exposures, lowering the aggression settings definitely lowers the mounts ability to respond to errors. Lowering the guide pulse durations doesn't seem to have as much of an impact as others reported. Also switching from hysteresis to predictive PEC seems to have the biggest positive impact on the RA RMS error. This seems to contradict the information I found on this forum around improving the AM5 guiding results (referring to this thread among others https://bbs.zwoastro.com/d/15711-very-large-backlash-in-new-am5/13).
Please note that when I did imaging runs with some of the settings(the guide runs in the log that have dithers are all also imaging runs), the results where acceptable given the image scale of the main imaging scope, but certainly no where near as sharp/consistent as my CEM70 (running the same guiding scope and a faster imaging scope but a similar image scale). I'm not obsessing about sub pixel or sub arcsec rms errors, I'm just trying to understand why my mount behaves very differently from others. Also since I just received the mount, I'm still in the 30 day return period in case the results indicate there's something actually wrong with the mount.
For your reference, I'm on the latest driver and firmware for the AM5 and using the latest ASCOM platform and PHD2 as well. Calibration was performed at the beginning of the session with good results (shown in the log) and the guide scope is very securely attached to the setup.