Laser staying at low power Snapmaker

The laser on my Snapmaker will come on to frame the project. When I start the engraving job it stays at the low power setting and does not increase to the 70 or 80%. It will run the job correctly just at the framing power setting. I’ve tried a number of things in different posts but have been unable to increase the power.

There is a Snapmaker specific device type. Make sure that’s what you are using. Your profile implies that you’re configured to GRBL.

I’ve tried using the Snapmaker device type and used the find my laser both are doing the same thing.

Can you provide the following:

  1. Screenshot of Edit->Device Settings
  2. Make a simple design, then do File->Save Gcode and save to a file with .txt extension. Then upload file here.

I will when I get home thanks

circle.txt.txt (6.8 KB)

I hope this is correct

From what I can tell the gcode looks okay and I don’t see anything in Device Settings that would prevent this from working.

Has there been anything modified on the Snapmaker or perhaps a configuration that needs to be done to put it into laser mode?

No modifications and if I was to load the same circle in luban it would engrave with no issue. Maybe something needs to be configured special for lightburn but I could not find anything online and I know people are using lightburn. All the updates are done on the machine also software wise

Is Luban able to save gcode? If so, can you make a simple file in Luban with a .txt extension and upload here?

circle2.txt (24.3 KB)

I don’t see a whole lot different actually.

Try a few things:

  1. Can you run the original LB generated file in Luban to see if that behaves differently?
  2. If that doesn’t work, try running these modified versions of the LB gcode.
    2a. the file with m3 appended swaps M03 for M3 as well as M05 for M5.
    2b. the file with header appended adds some additional header information from the other file. Don’t know if this is somehow used in processing.

lbcircle_header.gc.txt (6.9 KB)
lbcircle_m3.gc.txt (6.6 KB)

1 Like

Thank you for your help I figured it out it was the latest update to the firmware. I went back to the previous version and everything works now.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.