Nick,
I looked at your log file. Several things jump out at me.
1. I noticed you have backlash compensation turned off.? Have you run the Guiding Assistant to determine your Dec backlash. I notice there are times when it takes quite a few pulses to make the correct and the pulse width is small at 20ms.?
2, Your pixel scale is 6.45 "/px. By comparison mine is 1.24 "/px.? At this low resolution I'm not sure one can put too much into the guiding numbers, your numbers will look super good as you can not really detect true movement.? But others here are way more experienced on this front and I'm sure I'll get shot down for saying this.. Personally, I think the guide resolution ideally ought to be under 2x the imaging resolution.?
3. Your 240s error is at 4" to 4.5" peak-to-peak give or take. But that is with running the Predictive PEC algorithm. You might what to do a run using say the Hysteresis algorithm with Mount PEC off to get a baseline value. I reduced my native error down to just under 3 arc-sec peak-to-peak by installing a rigid coupler in the Ra. This way the motor shaft and worm are better aligned.? But your number is already low and it guides out really well to around 0.15", so is under control.
4. You have a very large low frequency component at 1100s or so. Not sure what might be causing this?
5. Those spikes are the biggest issue for me, and the elephant in the room is the 76s error, which is surely giving rise to those large transient moves in Ra. PHD2 is only able to reduce it by 2/3rds. There is a lot out there on this problem. With the OPW I do not see this error but I have an equally large one at 80s. Fortunately, I think I can build a PEC curve using PEMPRo to eliminate it. At least that's what I hope.
Overall, this are pretty good results with the caveat that things might look different at a higher guiding pixel scale. Time to take some pictures!
Peter
