Testing again last night until clouds shut me down. In PHD I'm really good at tweaking settings but I have no blue in the internal guide module. So - the RA meanders off. (FIRST I'd like it to correct before it gets this far off. - isn't that done with the minimum pulse setting?
Jasem said I should keep it at least at 100. (but my mount wants min move setting in PHD to be really low) If I reduce that from 100 (default) to say 50 will it kick sooner? I'm assuming that's the move... required to get the correction to kick in? (min error to correct?)
I ask because below you can see the RA went off track TO FAR before correction was applied. And then the level of correction was to much and kicked the RA in the opposite direction just as far off! I adjust PHD to kick to the center line. What settings do I use to:
1. minium error for correction to be applied?
2. Agressiveness or (amount of correction kick back to center line-'0'.
Guiding works, but POORLY. I'd like to fine tune this. Also - do you think there is more error/lag in running internal guider on the PI and using VMS or team viewer? That would eliminate the trip to my desktop and the correction then sent back to the PI which might make corrections quicker?
Would guiding be better if I ran Kstars on a linux PC in the dome directly connected to the mount? )team viewer from in the house)?
I guess what I'm asking is - would eliminating the data trip to and from the desktop in the house correct the mount better and quicker? Is the driver on the pi running the guiding module or is Ekos in the house doing the observation and correction?
It shows corrections aren't applied until the error is +/- 2 arc sec! TO MUCH. I want to correct at .5 ac sec error. And increase from there if seeing is causing oscillations. (like I do with PHD).
My DEC was doing the same. That much error makes me feel I should go check my alignment. I may have bumped something swapping from the 6" apo to the RASA install.