Bug in Galil Found While Jogging with Keyboard Arrow Keys

[HighOctane]

When I jog the machine using the arrow keys on the keyboard, I get a runaway condition quite often. It will start jogging, and then just go crazy, zipping along down the table at breakneck speeds. I just looked at the code in the GalilDebug.txt file. I noticed that many of the commands don't have a comma between the value for the Z axis and that for the A axis. I think this is causing my problem. An excerpt from my GalilDebug.txt is attached.

My config is as follows:
4 axes: X,Y,Z,A - all servo reverse
X and A are slaved together (X is the master)

Has anyone else ever experienced this? Please advise.

[HighOctane]

Also, I saw this in the debug file

State.nAixs = 4

Shouldn't that read State.nAxis = 4 ?

[smurph]

You have your axis mapping messed up.

This is from your GalilDebug.txt file:
ST ABCA
MO ABCA

Notice and there are two A axes in the command.  This means that you have the Mach A axis mapped to the Galil A(X) axis when it need to be mapped to you Galil D axis.  That will fix you up.

Steve