PROBLEM
When using SVG to GCODE the generated GCODE assumes that ending on the exact position as the cut started on will finish the cut perfectly.
However, when using this to drive less accurate lasers or blades, the cut will not finish - rather, a tiny piece of material is left uncut.
Example
Cutting a box generates (pseudocode)
MOVE 0,0
START CUT
MOVE 0,1
MOVE 1,1
MOVE 1,0
MOVE 0,0
SOLUTION
Add a tiny (configurable?) overshoot at the end - similar to starting a second pass, but only for a tiny cut (approx. 1mm or even less).
I had a look at the code briefly and it may belong to append_curves in compiler?
Fixed example
Cutting a box should generate (pseudocode)
MOVE 0.0, 0.0
START CUT
MOVE 0.0, 1.0
MOVE 1.0, 1.0
MOVE 1.0, 0.0
MOVE 0.0, 0.0
MOVE 0.0, 0.1 # Overshoot cut
PROBLEM
When using SVG to GCODE the generated GCODE assumes that ending on the exact position as the cut started on will finish the cut perfectly.
However, when using this to drive less accurate lasers or blades, the cut will not finish - rather, a tiny piece of material is left uncut.
Example
Cutting a box generates (pseudocode)
SOLUTION
Add a tiny (configurable?) overshoot at the end - similar to starting a second pass, but only for a tiny cut (approx. 1mm or even less).
I had a look at the code briefly and it may belong to
append_curvesincompiler?Fixed example
Cutting a box should generate (pseudocode)