I was testing my laser on some anodized aluminum to see how that would work out and I got some strange artifacts, I’m not sure if it’s software, hardware or something else, but figured I should get some opinions from more experienced folks.
In the engraving there are areas where the laser appears to have not turned off and instead continued burning until it reached the end of the overscan area around the image (one example is highlighted above in yellow), it does seem to have turned off consistently at the end of the overscan though.
The burn was done by sending directly from Lightburn to the laser via the USB-Serial link.
I’m not sure if this is just a missed command in the command stream, a problem with the Gcode itself or the laser controller not turning off for some reason, though I doubt that last one because of how consistent it seems to be.
I haven’t tried exporting the Gcode and running it directly on the printer, I ran out of time for today, but I’m thinking of giving that a shot to see if it’s something getting lost in the command stream. Is there a way to pull a complete gcode log from Lightburn? I’d like to see if there are any missing acks in the stream that would indicate something was not received properly.
My machine is an i3 clone 3D printer running Marlin 1.1.9 with Lightburn running on Linux Mint 19.