Luban G Code.nc (1.8 MB)
Lightburn G Code.nc (762.7 KB)
Sure thing - here is the code for both Luban and Lightburn.
Cheers!
Everything looks fine in the gcode. Try toggling emit S value with every G1.
Device settings for GRBL-M3
Try Marlin (not Snapmaker Marlin) with inline. Or Snapmaker Marlin to test.
The Emit S value seems to have made the cutting better but it still doesn’t cut through all the way. I can see the lines of the cuts on the back of the board now but still not enough to cut all the way through.
For the device setting itself, I tried both of those setting previously and they do not control the A350 in any way as far as I can tell. Using the GRBL setting I can instantly move the laser around. Nothing happens on the other 2 settings.
Make sure to clean the lens of the laser, also keep in mind variation in materials can affect how well it cuts through. The gcode is sending max power lines to the machine, so there should be no difference between them.
Using the same file, same machine, same basswood from the same package I get 2 very different results when using Luban and Lightburn.
If the files are the same how are they producing such different results given every other variable is the same?
For the rotary encoder I use Snapmaker Marlin. The other don’t have B axis.
For the other things: (The 40W is only for the 40W specific G-code)
For inline:
You didn’t specify which image was which. From looks alone, it looks like one ran slower, causing scorching, or the plywood was warped, causing the beam to be out of focus and scorching. You also didn’t provide the updated gcode files, unless you went back to use the ones you uploaded.
By the ones you uploaded, power and speed are both being set the same;
Lightburn;
G1 X-0.01Y0.08S255F180 G1 power is set to S255, which is 100% power, and F180 is the cut speed.
Luban;
G1 F180
G0 X-12.54 Y-17.10
G1 X-12.54 Y-17.09 S255
Sets the speed first on its own line, but still F180 and power at the end S255.
By ‘weight’ the Lightburn code is a lot leaner 762KB vs 1.83MB, part of it is the thumbnail, but most of it is Luban generated almost double the amount of code. Lightburn is only producing just under 60k lines of code, where Luban is ballooning it up to almost double at over 110k lines.
Lightburn;
Luban;
More lines slows down the program as the machine has to send each line to the controller, it does a move, and sends an ok response, and it waits for that response before sending another one. So the heavier the code, the longer it takes between each line, slows it down. Especially in areas of higher detail, such as the web and grass.
By this assumption alone, I would say the bottom, more burned image would be from Luban, however, I could be wrong.
1 Like
@Skreelink The images above have their names on if you hover over the image. The one at the top is from Luban, the bottom (more scorched) is from Lightburn.
These are the Gcode files for each -
cobweb Luban Gcode.nc (1.6 MB)
cobweb Lightburn Gcode.nc (93.8 KB)
@buckfast_beekeeper I set my Lightburn up exactly as your images showed. I got the error below
However, when I swapped back to the GRBL-M3 device it connected and worked immediately.
Baudrate 115200 correct?
Wich firmware do you use on the SM?
That explains it, in your lightburn file, if you’re using the touchscreen or auto method of focusing, you’re defocusing the laser.
; Cut @ 180 mm/min, 100% power
M8
M5
G0 X15.704Y4.152
G0 Z3
; Layer C16
You input 3mm into the material thickness, the G0 Z3 line is moving the laser 3mm up above your focus height, causing it to not be focused properly. If you’re not using my full repeatable origin, do NOT input a material height. So it’s similar to warping wood, etc. Remove the material height, or disable Z movement and try again. 
This is caused by the thumbnail string being too long to send over buffered connection via USB. Either send the file to the touchscreen, via luban, USB drive, or change your connection method from buffered to synchronous.
Do you mean 115,200 or 115200? Not sure if the , matters but want to be sure. Mine is 115,200.
The firmware version of the A350 is V1.20.3_20240716
The version of Lightburn is 1.7.01
ok I want to just clarify some stuff before I proceed.
I should definitely be using the Marlin Device setup detailed above, and overcome the warning error by changing from buffered to Async. Correct?
Once I have done that I should be able to control the SM through the move panel?
115,200 is the american way to work with numbers. Then the . is the decimal point. In Europe it is the opposite. Example US 123,456.78 is in Europe 123.456,78 or 123 456,78.
Wrong baudrate gives error too.
ok I think we cracked it. The 3mm offset is what I think was causing the problem. Setting the laser height using the Auto height setting in Snapmaker and then setting the material to zero gave a clean cut and can be controlled directly from Lightburn.
I couldn’t find any way to control the system with anything but the GRBL device setup, but that combined with the removal of the 3mm material thickness now seems to work fine.
thanks everyone for your help it is much appreciated!
Cheers
Paul
Glad to hear it.
One question to lightburn and my sm a350 with 40W.
Is it possible to use the “run boundary” on touchscreen? This is not working properly on my environment. I defined origin to “bottom left” on lightburn machine settings and if I start my job with origin set bottom left on touchscreen, all will be as expected. But when I run “boundary” it will mark an area which is not where it will laser. It is always first moving to the center and marks the boundary around the center point as I suspect.
Hopefully my question is understandable.
Hello everyone, the forum is impressively documented. I’ve had my SM 2.0 for a while but I had only used 3D printing. I wanted to venture out and bought the 40W head. different problems that I have solved with the help of many people. But now there is one that I don’t know what to do anymore.
Using LB 1.7.01 it starts to burn and after a couple of seconds the laser turns off but the head continues as if everything is normal. Any ideas?
I have read the forum a lot but I have not read anything related
thanks a lot
Make sure you are running the latest firmware, there was a correction made to the flame sensor sensitivity that might correct this issue.
When I installed the head and cabinet, I think it made 2 improvements. From the screen it tells me that there are no new updates. Firmware version Snapmaker2_V1.20.3_20240716.
In the LB console I received an error due to the flame sensor, but I managed to avoid generating that error anymore, but the result is exactly the same.