I notice that I have some issues when I try to burn multiple paths using the same values, laser fire no problem on the first path but does not fire on the second one ex:
Every time the laser value is updated it will output a new value in the GCode ex G1 Y40 S200 but, if the value remains the same the line won’t be created with the output value G1 Y40 = no laser =
Your code has an issue and I’m not sure why. The interface picture and the comment by Lightburn say 20% power, but S200 == about 80% power. The travel (G0) move with the laser on is also strange. I tried to duplicate your cut using an 80 x 40 rectangle in the lower left corner. My code doesn’t suffer from your problems. I am one version behind at 1.1.01 instead of 1.1.02, and there are likely settings that are different from your Lightburn setup and mine. My code is attached.
Same Issues with 1.1.01 that why I did the update.
In your devise setup witch controler are you usng?
I use GRBL and try Marlin (same result), witch device are you using from the device list?
I’m using Marlin on Lightburn. I run Marlin on my MPCNC. The issues I spotted might just be differences between the GRBL and the Marlin post processors. If you put Lightburn file in a ZIP file and upload to a post, I could try generating g-code with it to see if I have the same problem.
In LightBurn, in the top right corner you see a box with Cuts/Layers in it. You’ll see your one layer is called C00. If you click (or double-click?) on that, it should open a settings window for the actual cut path.
One thing to note is that I get an S51 on the first cutting move after the G0 g-codes. I don’t know enough about the differences in the way g-code is interpreted in GRBL vs. Marlin to understand if the problem is Lightburn or your GRBL setup. GRBL and Lightburn dominate the diode laser market, so I would not think that a problem this serious would last two versions of Lightburn. Here are my settings just in case this is a settings issue:
