Last night I was hoping for some trouble free autoguiding as I thought I had my problems ironed out...but no!
I was running PHD2, EQMOD and SharpCap Pro on my Windows 10 laptop. A Lynx Astro FTDI EQDIR USB Adapter for Sky-Watcher Mounts connected my laptop to the mount.
In my previous session I had discovered that setting the Total Steps to 5184000 and the Worm Steps to 38400 and the communications baud rate to 115200bps on the EQASCOM setup screen gave me good autoguiding. The baud rate change was particularly important as before that PHD2 couldn't even send manual guiding pulses to the mount successfully. With these settings I managed to get sub 1 arcsecond guiding for several minutes before I had to pack things away.
But last night I couldn't connect to my mount at all. Neither EQMOD or PHD2 could connect. I checked the cables and the COM port but all looked OK. In the end I changed the EQASCOM baud rate back to the default 9600 and now I could connect again!
Unfortunately my autoguiding run showed 4.63 arcseconds and the graph showed that the guiding pulses were not sufficient to correct for my mount's periodic error. I have attached the PHD2 log file if anyone is interested in taking a look.
I will take a look at PHD2 PEC training soon but first I was wondering if anyone knows which baud rate I should be using with my set-up. Why does the suggested rate (http://eq-mod.sourceforge.net/prerequisites.html) only sometimes work?
Thanks, Jim
PHD2_GuideLog_2022-07-03_235800.txt
I was running PHD2, EQMOD and SharpCap Pro on my Windows 10 laptop. A Lynx Astro FTDI EQDIR USB Adapter for Sky-Watcher Mounts connected my laptop to the mount.
In my previous session I had discovered that setting the Total Steps to 5184000 and the Worm Steps to 38400 and the communications baud rate to 115200bps on the EQASCOM setup screen gave me good autoguiding. The baud rate change was particularly important as before that PHD2 couldn't even send manual guiding pulses to the mount successfully. With these settings I managed to get sub 1 arcsecond guiding for several minutes before I had to pack things away.
But last night I couldn't connect to my mount at all. Neither EQMOD or PHD2 could connect. I checked the cables and the COM port but all looked OK. In the end I changed the EQASCOM baud rate back to the default 9600 and now I could connect again!
Unfortunately my autoguiding run showed 4.63 arcseconds and the graph showed that the guiding pulses were not sufficient to correct for my mount's periodic error. I have attached the PHD2 log file if anyone is interested in taking a look.
I will take a look at PHD2 PEC training soon but first I was wondering if anyone knows which baud rate I should be using with my set-up. Why does the suggested rate (http://eq-mod.sourceforge.net/prerequisites.html) only sometimes work?
Thanks, Jim
PHD2_GuideLog_2022-07-03_235800.txt