Hi,
whats happening is that jog moves are being stacked up in the buffer before execution. In essence you are providing
more moves than the machine can keep up with. It is not a fault.
A couple of things you can do are:
1) increase the jog speed by tuning your motors with as high acceleration and velocity as possible.
2) reduce the step size.
I have this problem also if I use a jog increment of 1mm per mpg step. I can spin the MPG fast enough that the machine
lags behind and even when I stop spinning the MPG it will carry on moving until all those moves have been executed,
very un-nerving. I find however if I reduce the maximum step size to 0.5mm per MPG click the problem is vastly reduced.
When jogging in this fashion I'm often trying to find an edge or similar so I want the jog velocity to be low. When jogging at
maximum step size you often want to traverse at speed. It is possible to write some Lua code that will jog fast at max step
size, thereby reducing the over-run, and slow when at less than maximum step size for edge finding etc.
Craig