@Captn91 As an addition to my latest reply, I downloaded Luban 4.0.1 once again. And something did actual happen when I turned the power under the “Laser Panel” to 100%! I have now made some tests with two simple squares side by side. The power is set to 100% in the toolpath for the first square and 50% in the toolpath for the second square. (The new in this is, that in all the other g-codes I have made and run in Luban, the Laser has been set to 100% for all objects in the toolpath).
If I set the Laser to 100% under the panel in workspace and then press play, the laser cut the first square at 100% and then the second square at 50%. It even change the % in the panel in Luban. This is what is wanted.
If I set the Laser to 20% under the panel in workspace and then press play the laser cut the first square at 20% and then the second square at 50%.
Also it “leave” the laser power % at the last used value (in the example with the two squares it would stay at 50% after the job is done). Now what I think happens is, that my snapmaker “forget” to “look” what the power-settings is for the first object in the g-code it is working on, BUT “looks” what the power settings is for the next objects in the g-code. It therefor just use the value it is on (which for me was close to 0%). This explain why the g-code made in Luban 4.0.1 is working in older versions. The g-code is fine but somewhere between Luban 4 and Snapmaker 2.0 the power settings for the first object is lost in the translation.
As long as you remember to adjust the power to the value for your first cut or engraving you should be fine, but it would be nice if the Snapmaker would actual run the g-code as it is supposed to, regardless of some settings in the workspace, that has not been touched.
Kind regards Jonas