Sorry, I should have mentioned that it’s the focus I’m trying to get right. I’ve already set the material height manually having turned off Relative Z axis. In a recent Snapmaker Artisan Q&A, they shared this information showing the focus as 10mm.
Here’s my cuts/layers tab. Have I just been a complete idiot and not noticed that I need to set the focus height to 0.0mm?
Focus height on the cuts tab should be set to 0. We’re setting the focal height via the header (and thus making it Z0 so it moves to the proper material height set in Material.
I hadn’t even noticed the focus height was an option here. Changed it first thing this morning and of course, it worked. It had been a long day! Thanks for your help. Running tests now. Sorry for wasting your time! 
Never a waste if at the end it works.
G’day… Bit of work for you:
Snapmaker2_V1.15.26 is out 
Could you patch it please?
Thanks
From what I can see from the code, this is for engraving using bottom left as the origin starting from Absolute Coords.
If I wanted to engrave from the centre of my material, do I only need to change the header code coords of X and Y? Or do I need to switch to User Origin?
Yes, following the guide as a whole sets up your origin as lower left. If you want to use elsewhere, remove the last three lines from your header, user origin, and set appropriately where you want it to start.
However, I’ve not tested this, as I always use absolute positioning for accuracy. I’ll try to remember to test and have a better answer this evening after work.
My last release on March 19th is still the latest. Snapmaker has not updated their github since March 17th. They’re getting lax again on updating the public repo and depending solely on their private one.
What is the recommended Snapmaker firmware release for use with your March 19th release?
1.15.21 was the base it was built on. However, I would assume being a minor upgrade, it could be flashed ontop of 1.15.26 if it included any updates for the modules/touchscreen since mine is just the controller. Naturally do at your own risk, ensure you know how to recover/downgrade.
Thank you, sorry about that question. It was right there in front of me, plain as day.
Please update the top post to remove commends from start/end gcode, thanks @Skreelink. Also should I still be using grbl preset instead of snapmaker these days? And lastly do I need the option “emit S value for every G1 command” enabled (if I’m on official firmware, or if I’m on yours [i’m not yet])?
Sadly, given the age of the original post, I cannot edit it. I really wish I could so I could edit in updates and changes I’ve made. They need to be cleaned up badly.
Also, if you’re on official firmware, use Snapmaker in devices, if you’re using mine, use GRBL-M3. For the last bit, no, you do not need that option. Make sure to leave it off.
Observation:
Firmware: Official Snapmaker 1.15.21 with Snapmaker_V4.5.34-SKREE_20230319.bin_20230319.bin
Machine Configuration: GRBL-M3 (1.1e or earlier)
Laser: 1.6W and 10W
In the Move Tab in Lightburn set laser power to 0.50% then fire, laser fires at specified power.
Change laser power to 1.0% and then fire, laser fires at previous setting (0.5%) until fire is toggled off then on again, then fires at new (1.0%) setting.
Change laser power to 0.5% and then fire, laser fires at previous setting (1.0%) until fire is toggled off then on again, then fires at new (0.5%) setting.
This behavior does not occur with machine configured with Lightburn Marlin device.
Would this be considered “normal” behavior given the configuration and settings?
Would this behavior impact the normal operation of the laser when in use?
Likely, given the machine is actually Marlin, so there’s a specific difference in the actual commands being sent. I don’t have a way to cable up to check, but could you tick the show all option in the command window, then toggle the laser via the fire button again, and paste back the differences? (do it once in grbl, and once in marlin). I suspect there’s an M3/5 on the Marlin command.
Not in the slightest.
As requested:
GRBL:
Waiting for connection…
ok
echo:Unknown command: “$I” (Select device GRBL)
ok
ok
ok
echo:Unknown command: “S0” (Fire 1.0%)
ok
ok
ok
ok
ok
echo:Unknown command: “S0” (Fire 0.5%)
ok
ok
ok
MARLIN:
Waiting for connection…
ok (Select device MARLIN)
ok
ok
ok
ok
M03 S2.5 (Fire 1.0%)
ok
M05
ok
M03 S1.3 (Fire 0.5%)
ok
M05
ok
Yeah, as suspected, Marlin is using M03 and M05 to control the laser, basically on and off commands with each. While grbl is only adjusting power via S# giving the assumption that M3 isn’t required. (in GRBL the laser is ‘always on’ so it just needs S values to change the intensity, 0 being off) Is a bit odd that the S# values in GRBL are 0, they should match the ones in Marlin. Verify in your device settings that your S value is 255 under GRBL.
Could always make a macro instead of the fire button to turn on the laser before framing. On the console tab, right click on of the macro buttons, name it, and put in M3 S2.5 and another with M5.
Thank you for your good work, I have the following problem with the positioning with the camera, the higher I go with the laser the less accurate the position of the laser.
Does anyone have an idea what this could be?
