I saw something similar @Griff. The carve finished and I didn’t notice until it was almost done.
Just did a test (not on a real carve and not when it was “frozen”)…
Clicked View --> Reload
CNCjs looked like it was disconnected, but serial communication was still going.
Opened connection again, and it was still going, running the whole time in the background.
Looks like the same as this?
UGH
Griff
(Well crap, my hypometric precursor device is blown…)
82
I’ll do some digging tomorrow.
Another glitch to note, I paused the cut successfully but was not able to restart.
I’ve never experienced these sorts of problems before, is it possible the file size has anything to do with it?
Griff
(Well crap, my hypometric precursor device is blown…)
83
No luck with this file in CNCjs.
Installed UGS, dusted off non-existent skills, watched Mr. Beavers probe video, back in business. I think.
File is cutting, complete override controls plus pause/resume.
This is without ‘apply tool length offset’ selected
feeder> G91
ok
feeder> G38.2 Z-50 F75
error:33 (Invalid gcode ID:33)
feeder> G90
ok
feeder> G10 L20 P1 Z10
ok
feeder> G91
ok
feeder> G0 Z4
ok
feeder> G90
ok
and with it selected
feeder> G49
ok
feeder> G91
ok
feeder> G38.2 Z-50 F75
error:33 (Invalid gcode ID:33)
feeder> G90
ok
feeder> G4 P1
ok
feeder> G43.1 Z4
ok
feeder> G91
ok
feeder> G0 Z4
ok
feeder> G90
ok
@stutaylo This is really weird. I think you’d see that error on s probe only if you’re making the probe move TO your current location. The G91 sets incremental mode with means all motion moves are FROM your location. So, to me, it seems it’d be impossible to get that error.
Did you compile your version of grbl? If not, where’d you get it?
How’d you flash Grbl?
@neilferreri Yeah to the best of my understanding, error 33 occurs either when calling for an upsupported arc move or during G38. 2, if you’re calling the machine to move to its current position.
I updated using the grbl updater from the carbide 3D website.