The way I read his post, he says jogging is OK. TO me, his post reads as if it is movement under G00 or G01 that does not appear to be correct. It is worth checking though to see how the jog speed relates to the rapid speed (maybe it is set to 400%, which would confuse the diagnosis).

—

It is not to clear what the OP means by 'get the correct steps per distance'. Does this mean 'calculate the steps per distance' or 'verify the steps per distance with a tape measure' (even if it is moving slowly during the test move)?

So, first, make sure when you command it to move 100mm, it does move that distance. Then set it to move some distance at a known feed rate. Use your watch and see what the actual feed rate is. Do a rapid move some distance and a 'feed rate move' back to the starting point. Is thate any difference in speed?

This might be a complete red herring but have a look in the motor/driver documentation to see if it has any kind of internal electronic gear ratio that needs setting. My only relevant experience is with a Mitubishi servo motor – at 1:1 electronic ratio, it needed a gazillion pulses per revolution. Mach could not output the pulse train fast enough to drive it at the speed needed, so I had to set the ratio in the servo driver itself to make it work.

What is the displayed feedrate on the MACH main screen while the axis is under feed ( not rapid.)?

F100 would not reset the feed rate, but set it to 100 units/min.

If your axis calibration routine has not set a feed rate it would default to either that as last set, or MACH's default – not sure what that is – it is slow and might be John's 6mm/min..

Use midi to set a feed rate that you want – use John's F100 to try – and try the cal routine again?

Joe

I had the problem as described. I tried all sorts of things to fix it and changing the jog percentage fixed it. I know it does not sound logical but it fixed the issue for me.

Martin C