Here's a photo showing what I mean: (The correct path is overlaid in yellow, and I've pointed out the problems in orange.)
I'm using GRBL 0.8c on an Azteeg G1 controller board. Anyone know what causes this to happen?
(P.S. As you can see, I also had some issues with heat as well as depth inconsistency; I'm guessing these are related to feed rate and the quality of my clamping.)
I've gotten all of my issues in this thread figured out. After posting on the GRBL issue tracker for assistance, I was told that the problem was because GRBL 0.8c only accepts lines of Gcode up to 50 characters, truncating any excess characters. Inkscape's Gcodetools extension outputs all of its coordinates with 6 digits after the decimal point, so its output lines are almost always teasing this limit (and, with arcs, the codes are so long that this is pretty much a guaranteed issue). By rounding all of the numbers in my Gcode down to 2 or 3 decimal places, I was able to make perfect cuts free of deviations.
Also, in response to this, the GRBL devs released a new v0.8c build with the following changes:
- The line limit was bumped from 50 to 70, making it generally safe to use the Gcodetools output without rounding
- GRBL will now treat lines that exceed the limit as an error case, returning an error message instead of continuing to cut using truncated codes