Gday Mark
got some sense out of the program now with your help file
I really should update it some day, but the app was designed as an ultra low level test app
that would be used "dynamically" by people who have a fair bit of experience.
The other inbuilt scripts are just for general testing of capabilities, not so much low level diagnostics.
I have proved the encoders work on the DEC and RA so thats a good start.
How did you do that ????
The mount returns its master "position" data via the :j commands
and these update if a microstep "request" is sent, ( not if it is processed )
The encoder is a very coarse unit ( one quadrature tick is 1450 microsteps )
and returns data via the 
commands
When ON, if the axes moves too far, the system resets the :j data to suit.
Soooo, if you have encoders ON and manually declutch and slew, and the data changes
( as well as the :j data ) then the encoders are working.
If you note the reported :j data, then lock the clutch and slew using the slew controls,
even if the mount doesnt move, if the :j data changes, then the CPU is "requesting" the move
and the problem is in the motor driver or the motor.
Another way to test visually is go to the "Move" tab
At the top, check the "Plot" "Az" and "Alt" boxes
Under Slew Mode, Uncheck the "Hi Speed" box and set the ":I" to say 152992
( It should show a rate of about 1x sidereal )
Select the "Plots" tab on the right
Now hit the "Az +ve" button, wait say 5 secs and hit the "Az Stop"
Now hit the "Alt +ve" button, wait say 5 secs and hit the "Alt Stop"
This will start both axes tracking at the given rates and plot the :j position data
and you should get a plot like attached
If you did get a slope to each trace, it means the CPU "thinks" it is sending
microsteps to the motors
Andrew Johansen Melbourne Australia
PS, at any time you can use the "Convert Log"
This will turn the log into a human readbale form in a floating dialog
so you can look at it whilst other stuff is still going on.
