Hi there,
I am running the latest edge branch and have been testing out a new CNC build recently and have run into this problem several times. I have SOFT_LIMITS true in the machine config, I home the machine, zero it and then run a job. It is pretty tight on the z-axis and several times i have not changed my clearance height to be low enough and it outputs a move that would raise the z -axis above the limit. However rather than the job stopping in an alarm state as i would have expected g2core simply ignores the G0 Zx move and carries on. This obviously results in the bit ploughing into the workpiece. For now i will disable SOFT_LIMITS, better to run the machine into the endstop than run it into the workpiece. Does anybody know if this is expected behaviour or if there is a setting that alters this behaviour? Does this happen to anybody else?
thanks,
Will
Update: This is running on Universal GCODE Sender Platform by the way, so it may be a problem with the interface between UGS and G2Core.
Hi there,
I am running the latest edge branch and have been testing out a new CNC build recently and have run into this problem several times. I have
SOFT_LIMITS truein the machine config, I home the machine, zero it and then run a job. It is pretty tight on the z-axis and several times i have not changed my clearance height to be low enough and it outputs a move that would raise the z -axis above the limit. However rather than the job stopping in an alarm state as i would have expected g2core simply ignores the G0 Zx move and carries on. This obviously results in the bit ploughing into the workpiece. For now i will disable SOFT_LIMITS, better to run the machine into the endstop than run it into the workpiece. Does anybody know if this is expected behaviour or if there is a setting that alters this behaviour? Does this happen to anybody else?thanks,
Will
Update: This is running on Universal GCODE Sender Platform by the way, so it may be a problem with the interface between UGS and G2Core.