PSA For Lightburn Users

Recently put my 10W back on and had to dial it in with the new square I use for repeatable origins. Accidentally ran a fill instead of just a score and… huh, the edges were massively blurry kinda like my offsets were absolutely horrible. Some more testing and I figured out, the laser isn’t actually turning off during the overscan sections! Something in the background changed on the firmware. If you’ve been dealing with fuzzy/blurry edges, this might be your fix as well.

Here’s an image from testing (one square goes in the opposite direction because I rotated the stock).

Notice on the red dot one, all the lines go outside the box, no matter the offset, they look fairly even too! So I made a massive offset and changed the setting “Use G0 moves for overscan” as seen below. I also added the below code to the start gcode box.

image

G0 S0
G1 S0

Since Marlin saves the power for G0 and G1 separately, if there’s a different value it can just run as well, as Lightburn expects any G0 line to be off (like every other laser does). Those two lines ensure they’re set to 0 power.

This gave me green dot square, success! So I put my offset back to where it was, obtained blue dot square. Perfection.

So yeah, TL;DR, enable Use G0 moves for overscan and put the two lines above in your start, and end gcode (just for safety on the end).

2 Likes

So if you hadn’t run the test with fill, it would not have been apparent that they changed something in the code processing?
More customization. Please advise SM 2.0 Firmware version that produced this behavior.

My machine is on the latest as of writing, 1.20.3