Why does my Z raise up and over travel and stutter/skip every time I start gcode program. After I zero Z, I jog up a little to remove my paper I used for zeroing and than press “start” and Z raises and over travels and I lose my zero. When I initialize/home machine it works as it should. I have doubled and tripled checked everything on Z and can’t find anything lose. I was 3 hours into program, when I got Grbl socket error, cutter not found, and couldn’t recover so I had to shut everything down and attempt to restart from beginning. XY axis kept zero but Z I can’t get to stay zero and start without over traveling up.
Any ideas, I’m running out of time on this project.
This is usually cased by setting safety/retract height to a dimension greater than there is to travel from where you have Z zero set relative to the stock.
If you continue to have this difficulty, please post:
.c2d source file
generated G-Code
step-by-step notes on how you are securing your stock and setting Z relative to it
Let us know what you find out and we’ll do our best to work through this with you.
Program started fine with no issues until I got the Grbl error 3 hours into program. nothing program wise had changed. All I did after recovering from error was re-load same gcode. Re-zero z only. I started off with 1.5” piece of pvc board 14.375”T x 22”W x 1.5” thick. It had cut up to .5-.6” before the disconnect error. I’m using blue tape and CA glue. I was on a 3D roughing pass, using aspire and carbide motion.
For the Grbl error, was it software or an EMI disconnect? Check to see if it was the former by running the file in check mode (send $C, then send the file — it will process but the machine won’t move), then send $C again to get out of check mode).
The error is most likely EMI.
Unable to connect can probably be solved by closing CM, unplugging USB, then reconnecting.
The Z crash is probably because you’re retracing 0.8in and don’t have that much room?
It’s just a text file.
Be cautious “resuming” from a line unless you know a bit about what’s going on in the gcode. I usually go to a retract move prior to the point I want to resume, and be sure to include any header info.
Not sure what garbage your referring to, lol. I know I was on line 7751 because I took picture of it, and I caught it with in a minute so was going to back to whatever safe zone would be prior to that. I guess at this point I’m just going to start it over from beginning and let it cut air for 3-3.5 hours, I’m sure my z isn’t going to be where it was the 1st three hours, good news is it’s on a 3D roughing pass so hopefully the finish pass clears up any issues in the redoing of the Z on the rough pass
