I’ve had a problem randomly start happening.
I’ll setup my drawing just like I normally have, as well as set my zero…but when I start my program the g code will call for -0.125, but ground control will only show me -0.0.
I’ve verified that my g code is calling for G20 in the beginning. I’ve also reset ground control, rebooted my Arduino, verified my z axis connections, and confirmed that I can command the z axis below 0 manually. Also I’ve verified that I don’t have the steps set extremely low, and even tried making a full depth cut in the g code.
I’m currently making a cut with my zero set at -0.125 just so that I can get it done.
This is with the metal maslow kit, and with a setup that I have cut with before already and had zero issues.
I’ve got the roughing file running and haven’t seen the issue crop up. Is there a particular spot in the file where it most often occurs? When this happens, does GC pause waiting for the bit to reach -0.125?
Are we talking about the line of gcode being executed
So I finished a cut that I started last night. I had reset everything, verified my connections once again, and then verified them again lol. I ran into the same issue where I had to set my zero to -0.125 to make a cut.
I’ll keep playing later, currently I’ve got a newborn that needs some attention though!
Thanks for including the video. On my rig, I get that sound when the firmware is using a very low feed rate. Often that’s because I’ve just started GC and the first file I run is one where I’ve forgotten to put a feed rate in my gcode file.
Here’s a copy of my gcode from above, with a feed rate ‘F40’ set:
Load that in GC, quit then start again and see if it runs correctly. Then repeat with the old copy without the feed rate to see if that fails when GC first starts.
The z-axis control sets its own feed rate, and when you ran a different file that included a feed rate, so the problem “disappeared”.
Edit – I’m not certain about the above, I started in to see if I could write a ‘fix’ for it and the steps I listed didn’t make the issue happen. Which versions of firmware and GC are you using? I’d sure like to find a way to reliably cause the issue to occur here…