In my (partial :) defense, I have been using 0.20 MinMove on DEC literally for years while imaging on the West side of the mount, and I had never seen this oscillation pattern and my images were just

Good to hear. Throughout this, it sounded like you were equating low MinMo values to better images. Not sure if you were actually intending to do that, but its most certainly not the case. Getting

An update from last night's imaging run - and it's good news :) I gathered some more data on NGC7000, including doing an automated meridian flip using SGP. The guide settings matched a lot of what

If this group was easier to use, easier to read, didn't repeat everything over and over and over and over... included attachments. People wouldn't need places like cloudynights. Forums are VERY EASY

I installed a Rayox saddle on my mount and yes, it works beautifully and I find it a huge improvement in confidently mounting my C-11 Edge. Previously, especially in the dark, I was always concerned

Thanks Ray - really looking forward to your interpretation of the logs. Let me know if you need any additional data - I still have the ascom logs from my previous nights testing / older PHD2 logs.

Hello, I ran APPM for the first time. Over all there were 47 points and all were plate solved just fine. The differences between assumed RA,DEC and what plate solving showed were in [-15,15] arc-min

That peak error may be +- error or Peak to Peak. If that's the case, divide it by 2 to get the peak error. Then multiply it by 0.6 to get 1.1 arc sec or 0.37 pixels (or multiply by 0.8 to get 0.5

>That is why I recommend using a short unguided Dec graph to determine the actual atmospheric motion peak value. Yep. And that is exactly what PHD2 Guiding Assistant is doing (measuring seeing with

That is why I recommend using a short unguided Dec graph to determine the actual atmospheric motion peak value. Then set the MinMove to between 60 and 80% of that value. If the star motion is +-2 arc

I've not gotten that deep into it. I'm still trying to work out kinks. The manual (being a translation from French is less than detailed). But the program keeps forcing me to come back and work with

>You say that you have seen peak Dec errors of 3.71 arc seconds. Well the fact is that this error happened in the past and the next measurement may show a different position of the star, Again, to

Again, you turn off Dec guiding and just look at the Dec axis peak motions of the star. You eliminate any guider commands and all motor and axis motions. You have only the pure atmospheric movements,

The whole point of using Dec with guiding turned off is that it doesn't produce any guiding spikes because the axis is not moving and there is no guiding happening. All you see then is pure

Hi Wade, >Let the mount run unguided for a few minutes while watching the graph. Throw out any really big outlier values and take the peak from what is left. This, ideally, is exactly what PHD2 GA

Hi Roland, I just responded to Bill on this before seeing your post. RMS is a measure of error from the predicted data, which in this case is the error with respect to straight line tracking, I would

One thing I would like to see is to do rapid corrections after a dither so that the star is brought back to zero quickly, after which the rate of corrections can be slowed down. The way things work

Let the mount run unguided for a few minutes while watching the graph. Throw out any really big outlier values and take the peak from what is left. Taking the RMS seems like it would guarantee that

You may have a different mechanical load on the mount axis on one side versus the other. If on one side the cabling impedes movement of the axis but on the other side it does not, then you may get

Hi Bill, I wanted to come back to the "right" way to use GA to determine the MinMo values, as I agree it is critical that these be set correctly. Specifically for setting DEC MinMo you wrote: >Look at