|
OK, well you originally said the guidescope was an ED80, and Marc then guessed you had a guide scale of 1.8 asp. If the graph is in arc/secs then you certainly dont have a problem, even DEC is only 2 arc secs P/P odd and RA is very good. If its in pixels, then DEC is 3.6 arcsecs P/P, which isnt bad either. The RMS shown Im guessing is RA at 0.21 (and looks like about 1 P/P), which is friggin awesome. I dont know what 0.48 "osc index" means.
Another guess, is the graph is the wrong way round, (RA-DEC are transposed), that would make more sense, the RA as shown is suspiciously low.
The red line looks like the axis is constantly drifting (alignment?) and being periodically corrected with minimum move set to high (not attempting a correction untill its gone too far), and then the correction is too agressive, causeing an overshoot (this could also be backlash).
The "mn mo", which I guess is min move, seems to be a low number, but then I dont know what scale its on. Does "mx dec" mean dec max move?, if so, try lowering that. I cant see a DEC agr setting. Asuming the graph axis are correct, thats a worry, you definitely should be able to set DEC agressivness (or does that come up clicking the RA/DEC button?).
The graph doesnt show what the horizontal timescale is, the oscillation on the 1st graph could even be PE .
All this is based entirely on the graph you have shown (which anyway seems to show no big problem if the scale is as Marc suggested). If you visually get a bad result, then the guide image scale is nothing like 1.8asp.
You can graph whist tracking (I think), just by starting guiding (and the graph) and then pull the guide plug out.
|