Hello, I have spent days trying to get this to work with my Snapmaker 2 A350F with a 10w laser. Best I can do using the GRBL-M3 (1.1eor earlier) is to get it connected once run the test job and it runs, but does not move from the highest Z access. Is the solution to manually move my laser down to my focus height? Every time I come back to it though it won’t connect (even when right clicking on the device button). Any help would be greatly appreciated. Thanks Jeff
Care to upload a gcode file here so I can look over it?
Sure, no problem. Thanks for taking a look. I can connect once and even got it to go down to the bed (by itself) and burn the square, but it only works once until I remove the laser profile and add the same one again.
The gcode looks fine. Using absolute coords, I can see the G92 setting origin after homing, and the G0 Z0 (didn’t set a material height eh?), overall looks fine. Maybe in your movement back up (the end script G0 Z292.5) change it to a slightly lower number so it doesn’t move back up and potentially hit the limit switch. Say Z290.
I assume with the M1010 commands, you have an enclosure. Are you making sure not to open the door until after it finishes it’s final home? Popping the door on the enclosure open before it’s actually finished locks the controller until you close and clear it.
What does the Lightburn console say after running? Also after running, can you type G0 Z100 into the console, and the machine move?
1 Like
Okay I switched it to 290 in both locations. Yes, I have an enclosure and no I would never open the door until the project finished unless for some reason I deactivate it for some far future project where it was necessary, but still wouldn’t open the door until it was finished. Right now it’s hard to find what runs after the job due to not being able to connect again. I’ll remove the profile and re-add it so I can run something and let you know what the results are in lightburn.
Leave it in the start gcode, but reduce it in the end gcode. I’m also wondering if it might be a bad cable.
Hi Skreelink,
Can you specify which version of lightburn and which version of the Snapmaker firmware have been tested with this protocol?
I upgraded from Lightburn 1.6 to 2.0 today… I lost my macros and and config settings and my laser isn’t working like it used to. I think I have to start over.
Thanks
Odd that happened to you. I’m using the latest with zero issues. However, I do not use a USB cable. I use my drag/drop scripts to start projects remotely.
Okay, sorry it took so long, but work, you know.
I removed my profile and added it again. It worked great for a couple times. I ran the 10mm square test, ran it again, then I started a material test and in material test I pressed stop and it looked like the laser froze while it was on and the only way I could get it to stop was with the physical emergency button. Shut down lightburn and restarted the laser removed plugs and put them back in. This is where the problem begins. No matter what I did I could not re-establish connectivity. I took some screen shots through the process to see if it would give you any clues.
After shutting it down I got the top of the image, trying, trying,…. I remove the profile and add it again and it spits out this.
Baud rate should be 115200, that might be your issue. 
That seemed to have done the trick. I just wanted to come back and let you know how much I appreciated you helping me out with that. HUGE! They should get some type of tipping system. I’d send you something if you have a platform. Do you have a community page I could follow. Let me know.
Thanks,
Jeff
I’m glad the fix was a simple one. Baudrate can get overlooked easily and really wreck things. 
I don’t have any community pages to follow (unless you count my rarely used youtube). As far as tips, I don’t think snapmaker has a donation option, though I do have pay apps, but otherwise I’m just here to help. Nobody’s actually offered before.
1 Like
I’s really like to tip you if you could leave your cash app info. 
1 Like
I’ve sent you a message.