On nearly every job,

CAD & CAM Tool Chain ChiliPeppr
1

On nearly every job, I see errors returned from the Inventables gShield running GRBL 0.9. Error codes 25 and 33 seem to be the common ones. Often clicking up-pause in Chillipepper is required to get the job to continue. Today the XCarve cutter gouged my part badly after one of these errors. So I guess I need to get to the bottom of it. I use MeshCAM to generate the GCode. My files are typically 3-10k lines. And I am running SPJS 1.86 with Chillipepper.

Another clue - when I send the nc file with GRBL in $C (code check) mode, it seems to parse the file without error.

Is anyone else seeing this? Any solutions out there?

1b30b45ed98b934eb63377cebd7c61c9.jpeg
1b30b45ed98b934eb63377cebd7c61c9.jpeg1705×1385 473 KB

2

Please check this link: https://github.com/grbl/grbl/wiki/Interfacing-with-Grbl 25 A G-code word was repeated in the block.

3

I don’t believe its a problem with the GCode. The file runs fine in $C mode and in several simulators. I’m thinking its a comm error, either a buffering issue or electrical noise.

4

What if you step through your gcode file line by line? The buttons next to play/pause/stop allow for that and you could possibly debug better. However, what line is it erroring out on? You should be able to see that in the Gcode widget as it puts checkmarks in there when completed.

5

Is there a way to log errors in $C mode with CP? In $C mode, will the player pause on an error like it does in live cutting mode?

6

You’d have to talk to @Jarret_Luft as he created the Grbl workspace. I would also guess you could try.

7

This issue seems better since I stopped monitoring the host laptop with a remote desktop program.