jog when large files are loaded

When running a 84000+line file Axis did not update smoothly, this was expected.
What I didn't anticipate was simply loading that file made keyboard jogging very unpredictable.
What part of best practice was I ignoring ?

Keyboard jogging is not under realtime control so will be unpredictable while AXIS is busy.
Using a MPG would be much better. or don't jog while loading a program.

Chris M

The program was loaded, or at least the progress bar gave that indication.
Good thing this machine doesn't have enough power to hurt itself as jog pushed it right past the soft limits.
An mpg would be nice but hardware limit switches are looking like a must-have.
From now I'll do touch-offs before calling a file.

had you homed it? it shouldn't move past soft limits - something seems wrong there.

Chris M

From now I'll do touch-offs before calling a file.

That is probably a better practice and avoids Axis having to update after the touch off.

Rick G

cmorley wrote:

had you homed it? it shouldn't move past soft limits

You're right, it wasn't re-homed after I shut down in panic/confusion. Confirmed by recreating the situation. The gcode ran perfectly so all ended well.