the issue is that my laser makes all “G01” movements a “Flame on” Movement. Travel moves need to be a “G00” Command. so as it is right now, all travel movements are etched, not just the actual etch lines.
LightBurn posts the correct movement commands when i use “cut to debug”, but then i have to manually change the code to use the E9 cut condition, and i lose the “scanning” feature for the etching.
To be clear, you mean the Y moves like this one should be G00?
E9
M103
G01 Y0.003
M104
if that is a rapid travel movement from one etch line to another, then yes.
E9; Cut condition to tell laser to etch
M103; Head down, Shutter open
G01 X1; laser etches from current X position to X1
M104; Head up, Shutter Closed
G00 X2; Rapid travel movement to position X2
E9
M103
G01 X3; Laser etches from position x2, to x3
M104
Ok, I found it and it’ll be fixed in LB 2.0 - turns out it’s a bug with Custom GCode and LinuxCNC specifically.
You can’t do this now because you won’t get the UI but once you have 2.0 (more on that in a second):
Set Fast Whitespace Scan and then set the value below it to 0.0
That will enable raster moves to be G0 instead of G1 with zero power.
This will be in either the next release candidate (possibly tomorrow or the next day) or the full release (within 2 weeks).
sounds great! thank you very much i’ll test that asap when it’s released.
1 Like