I slaved A to X and X runs faster than A. They are both calibrated the same. Both run the same using MDI without slaving. Both motors identical as are drivers. I swapped the connections coming from the BOB which swapped the problem to the other side. I am at a loss as to the problem.

Running Mach3 Version R3.043.066 thru ethernet smooth stepper, C32 BOB.

Bob
Sanddollarwoodworks.com

"I swapped the connections coming from the BOB which swapped the problem to the other side."

The first to recheck is the Motor Tuning page.  Be sure everything is the same for X and A axis.
If you ever plan on adding a 4th axis I would suggest you do not use the A axis for slaving as Mach will only do 4th axis Radius Correct on the A axis.

Ray

Thanks for reminding me of the obvious Ray.  Sometimes it is the obvious that is overlooked, however, I have the motors tuned exactly the same.  I tried slaving the B axis with the same result. 

There HAS to be something stupid that I am overlooking.

Bob

Maybe the X axis is "Scaled" on the mach screen.

By switching the X and slave axis at the BOB you proved that Mach was sending out different pulses to the motors.  This eliminates all the hardware and electronics you are using.   It has to be something coming from Mach.

Ray

Which screen would that be, Ray?

The Program Run screen.

There is no scaling set.

Scott N. from mach support found the problem.  ESS frequencies not configured the same.  Moving now together except when homing.  Slave axis does not move with X when homing.