I frequently hit issues where halfway through a cut the machine will hit a soft limit (for example a g-code command exceeding a limit by 0.01) which will ruin the workpiece.
Every other CNC I’ve worked on automatically runs a check when you load the file and will flag if the g-code is exceeding the machine limits as soon as you load the file.
As far as I can tell, OneFinity’s advice to avoid this here is to run a “Dry run” before, where the machine runs the whole cut with Z-retracted. This is a comical solution - a say 40min cut will take 40 minutes to run this, when a few trivial lines of software in the controller could check this in a couple milliseconds.
Is this on the radar to be fixed / updated? Seems like a big miss
Which controller are you referring to? BB, Masso, or Redline?
On the BB and Redline They do not allow the program to run and will give you gcode out of bounds errors.
On Masso, it will only do it once it reads the gcode line. Onefinity has no control over the Masso hardware or firmware. You’ll want to reach out directly to Masso and express your desires for it to work like the BB or Redline controller.
Our advice on dry run is to try to get around Massos limitations.
I agree, I wish Masso did a check before beginning.
We dealt a similar issue in a production environment. Not so much overextending the machine boundary, but overextending the stock boundary (running the part where material wasn’t loaded). It became policy to jog the spindle to the 4 corners of a job before starting.
The benefits were two fold. It checked the material was loaded in the correct spot, but also caught a number of completely unrelated problems before starting the program. It was as though the remedial task was enough to clear the operators head a little, and they would remember something else they forgot. It took more time but was an overall net positive as it reduced errors.
Masso makes this easy to do quickly: jog the spindle to the yellow preview extends before pulling the trigger.