Make sure you set the s-max value at 255 in Lightburn and adjust your laser power in the cut setup appropriately.
This looks correct, so you should be good here.
Nice use of macros to move the focus length, I use the gcode header function so I don’t forget and automate everything I can. 
Although, I thought the 10W laser had a fixed focus of 30mm. Try using Z30 for your focal length, maybe the weakness issue is you’re just out of focus.
These shouldn’t be needed, as the snapmaker will not change intensity until it receives another S# value, I assume this option is for lasers that turn the laser off on lines without S. There’s also no need for the G0 for overscan moves, as the snapmaker makes no real difference between G1 cut moves, and G0 fast travel moves. Feel free to experiment with these options, however!
EDIT: Oh! Also since you did that roundabout with the firmware, I would also suggest going through the 10W laser calibration again, just incase.
Ahhhh, you won’t believe what the mistake was! The door was open and the door monitoring was enabled again after the update. I always use the glasses during settings and experiments to see exactly what the laser is doing. Then, when everything is working, I close the case.
OK… now it seems to run
Many greetings and thanks!
Unfortunately I can’t upload the update tool here, because it is over 30MB big :-(. But if someone needs it, I can send it to him by e-mail.
VG Rötty
You can always upload it to something like zippyshare.com and PM the link.
Maybe zip the file and upload it here?
@Skreelink first of all thank you for this guide and the firmware.
I’ve followed the guides all the way but I’m stuck on one major problem - Lightburn is sending all of the x and y movements twice to my A350. Z movements are fine. This happens if I’m using the movement buttons, running a boundary or running a burn.
I thought I may have done something wrong in the gcode section of the device settings so I removed the lines, but it still sends x and y twice.
The only thing I can think of is some mismatch between my lightburn settings and the custom firmware.
Here’s an example from the LB console after clicking the move X+ button one time (1mm):
Starting stream
G21 G54
G91
G1 X1 Y0 F5000 S0
G90
M2
echo:Unknown command: “M2”
Stream completed in 0:00
G21 G54
G91
G1 X1 Y0 F5000 S0
G90
M2
ok
ok
ok
ok
echo:Unknown command: “M2”
ok
Same result for Y movements.
Snapmaker A350
10W laser
FW: Snapmaker_V4.4.19_20220919
Lightburn is setup with the GRBL-M3 machine according to the guide
If you have any ideas I’d appreciate the assist! Thanks.
I never use the buttons so I’ve never noticed. However, a quick test does the same on my machine. I assume it’s part of the fact Lightburn is expecting GRBL, but we’re using a Marlin machine. So some of the various checks are semi-broken. Such as the M2 it tries to send at the end. This is normally a “program end” command that shuts off coolant, turns off spindle, resets workspace, etc. I wonder since it’s not getting a proper ok response fast enough (since the snapmaker doesn’t understand it), it sends it again.
It could also be how GRBL and Marlin send ok messages. If I recall correctly (it’s been awhile) GRBL actually sends an ok response after every line is executed (which is why using buffered mode is faster, as Lightburn is just filling the buffer and not waiting on an ok), whereas Marlin responds after the command queue is clear (notice the flood of ok) So it seems Lightburn is trying again until it gets the ok that the command was received, which happens to be after a resend. Fun fact; this isn’t just the movement buttons. If you hand-type a command in the console it doubles it as well. However! Macro buttons, do not double. I don’t remember it doing this on previous versions of Lightburn, though. On my GRBL machine it’s fine, and setting the machine type to Snapmaker it acts as normal as well.
This is all speculation, but I’m sure the main issue is the fact that Lightburn expects GRBL, and Snapmaker is running Marlin. While the core gcode works, there’s a few nuances that are different.
Edit: due to your question making me investigate, I found an option to make my projects easier, and detailed it in my full rotary control guide. Thanks
First Off, thank you for all you have done and information you have provided in this thread. I am having a similar issue to the one you were troubleshooting with Savak. When I first run the job, it works fine. I am getting used to the 10W so I have stopped the job midway and that’s where my problem seems to start.
Once I stop a job, the next time I try to run, the toolhead goes all the way to the top of the Z axis and stays up there and will try to engrave as if that is the new Z Height, even know my G Code specifies my Z as 27. Here is the beginning of my G Code. I have ensured that I am using absolute coordinates. Closing Light Burn and restarting seems to help but then usually the next time around the same issue occurs. When I click “stop” in light burn I do get an error saying the echo:Unknown command: “M5”, so maybe that gums everything up until it’s restarted.
; LightBurn 1.3.01
; GRBL-M3 (1.1e or earlier) device profile, absolute coords
; Bounds: X16.78 Y22.4 to X49.12 Y43.3
;USER START SCRIPT
M106 P0 S255
G28
G53
G0 Z27.2 F6000
G54
G92 Z0
G0 Z300
G53
G0 X7.1 Y0 F6000
G54
G92 X0 Y0
M3 S0
;USER START SCRIPT
G00 G17 G40 G21 G54
G90
; Image @ 1000 mm/min, 15% power
M8
M5
G0 X32.683Y22.399
G0 Z2.6
; Layer C00
G91
M3
G1 X0.417F1000S0
G1 X0.4S38.3
G1 X0.416S0
G1 X0.1Y0.1S0
G1 X-0.416S0
Here is the log when I have to stop the job. It seems Light Burn might be inserting some unknown character into the M5 command but even manually typing it in the command line does not work.
Starting stream
echo:Unknown command: "M2"
Stream completed in 0:00
door opened!
cannot pause in current status: 1
door closed!
Starting stream
leveling OFF
X:-19.00 Y:347.00 Z:334.00 E:0.00 Count X:0 Y:57120 Z:133600 B:0
Select workspace 0
X:-7.10 Y:0.00 Z:-306.80 E:0.00 Count X:0 Y:57120 Z:10880 B:0
echo:Settings Stored (1077 bytes; crc 13294)
X:-7.10 Y:0.00 Z:-0.00 E:0.00 Count X:0 Y:57120 Z:10880 B:0
Select workspace 0
X:19.00 Y:-347.00 Z:300.00 E:0.00 Count X:4176 Y:1600 Z:130880 B:0
echo:Settings Stored (1077 bytes; crc 38605)
X:0.00 Y:0.00 Z:300.00 E:0.00 Count X:4176 Y:1600 Z:130880 B:0
echo:Unknown command: "M9"
Stream completed in 0:42
ok
echo:Unknown command: "M5"
ok
door opened!
cannot pause in current status: 1
door closed!
I think the main problem is the way Lightburn works. For all main moves in the program, it uses relative motion. It only uses absolute at the start, and swaps back at the end. However, if you stop the program in the middle. The machine is still in relative mode. So even if you start over, it’s not until the first G90 that it swaps back into absolute. I guess a remedy would be to add another safety line in the header. Place a G90 after the G28. Thus after it homes, it immediately swaps back to absolute movements.
I just switched over to the 10W after the Christmas rush and set up with the new firmware and GRBL-M3 machine settings.
I noticed that when framing it performs the task twice. Sometimes after completing a burn the laser and bed return to the coordinates set in the Gcode (see below) but the laser flashes a few times on completion at the top of the Z axis.
Also,“Get Position” causes an endless stream of "echo:Unknown command: “?” in the consoles display until “Set Origin” is selected.
It’s not really a big deal, just thought I would mention it.
Any control button seems to run twice. Be it framing, jog, etc. Even if you hand-type a command in the console it runs it twice. Why? I don’t know. I speculated a few posts back it’s because Lightburn is expecting GRBL, but the snapmaker runs Marlin. So likely it’s some kind of buffer or waiting for specific machine response so it repeats the command. I’m not sure.
2 Likes
Hallo und guten Abend. Ich bin neu hier, bin Besitzer eines Snapmaker A350 und habe mir die Software lightburn schon gekauft.
Einige Fragen müsste ich vorher für mich noch beantwortet haben, bevor ich mit Lightburn ans Werk gehe und mich versuche. 
Die wichtigste Frage die ich hier erst einmal für heute stellen möchte ist folgende: ich habe gelesen, dass man, nachdem man alle Updates herunter gelanden und (von Snapmaker) installiert hat, eine neue Firmware auf den Snapmaker installieren muss um Lightburn zu benutzen.
Wenn ich jetzt wieder einmal drucken oder fräsen möchte muss ich wieder die Original Firmware von Snapmaker installieren.
Bedeutet das dass ich immer hin und her switchen muss für unterschiedliche Arbeiten und noch wichtiger, ist das überhaupt möglich.
Wenn die Frage geklärt ist, ist für mich schon vieles geschafft.
Ich bedanke mich schon Mal im Vorwege für etwaige Antworten.
Euch noch einen schönen Tag.
Tut mir leid, wenn das schlecht klingt, ich benutze einen Übersetzer.
Nein, Sie müssen die Firmware nicht hin und her tauschen. Es funktioniert gut für alle drei Modi. Aktualisieren Sie einfach zuerst auf die neueste offizielle Version und verwenden Sie dann die benutzerdefinierte Version.
Sie müssen auch nicht die Firmware für Lightburn verwenden, es ist nur die benutzerdefinierte Firmware und diese Anleitung sorgt für schnellere und bessere Ergebnisse.
English for others;
No, you do not have to swap the firmware back and forth. It works fine for all three modes. Just update to the latest official first, then use the custom one.
You don’t have to use the firmware for Lightburn either, it’s just the custom firm ware and this guide makes for faster and better results.
Not sure if this question has been asked but herre we go.
I’ve upgraded to the 10 watt laser and calibrated it, but in the touch screen there is no height shown on the touch screen like there was for the 1.6 watt.
How do I set this for Lightburn in the Gcode line G54 Zxx.x F6000?
I would like to have two machines set up in lLightburn for each of the lasers so that I don’t have to set the height each time.
Regards
Graeme
Looks like there is a new firmware to battle with…
Still no Inline Power included.
I’m beginning to think that they’re lying about adding it…
Snapmaker 2.0 Firmware Updates and Downloads - Snapmaker 2.0 - Snapmaker: where creation happens
Hi MaxMuell,
die angepasste Firmware brauchst Du übrigens nur, wenn Du den A350 direkt aus Lightburn heraus ansteuern möchtest. Wenn Du die Firmware nicht antasten möchtest, kannst Du mit LightBurn GCode erzeugen, den Du dann per USB-Stick oder Luban auf den Drucker bringst.
@Savak
There should be a laser height on the touchscreen. My 10W shows 30mm, which I think should be the same and fixed focus for all since it no longer does the line calibration like the 1.6W. All it does is the thickness calibration.
Also @VaporPhoxxe they haven’t pushed any commits to their public github either. Last merged commit was October 10, 2022. So my firmware is still the latest with inline if you tested the official. I have not yet.
Danke für den Hinweise!
Bist du dir sicher? Der gcode hat dann immer noch Inline Power Kommandos, und die versteht der Controller ohne angepasste Firmware nicht.