Gday Mel
Thks for the reply.
I figured it was going to hurt ( trying to save the data ) but, as i already have PICs i had to try.

"the BIG question is what value will it be to you? All you'll see is your motors start, speed up, slow down and stop. No big deal,

I'd luv to see that.

"you can see that happen already by watching the telescope move."

The problem cannot be visualised by watching the telescope move
as it is moving at siderial speed when the problem occurs ( Ie slower than drying paint )
The problem is based on Nth vs Sth hemispheres rotating the wrong way, and all sorts of esoteric corrections being made to take up mechanical slop, whenever the scope changes direction, or receives a "move" request.
The PIC that drives the motors controls direction ( hemisphere specific ) and also has "backlash" compensation as well as "training compensation". These all have to be applied in the correct order/sign for it to work.
I have put a std CRO on the motors, but it all happens too quick to see.
As such i need the traces so i can study the "relative" speed and direction changes. From this i can tell if they are applying the relevant changes using the correct directions and signs.

"(I suppose it's the mech-techie version of watching paint dry)"
A truly noble pasttime, especially with a beer in hand.

Andrew

Off to look for a dedicated datalogger