Bug: Luban 4.0.3 ignores change of laser power

Snapmaker Luban
1

I’ve set up a job in Luban, consisting of two SVG imports. The first is an image I etch into wood at 20% laser power. The second is the outline to cut through the wood in 2 passes at 100% laser power. Here’s screenshots:

grafik
grafik769×705 64.6 KB

grafik
grafik738×731 70.6 KB

The resulting GCode misses the switch to 100% laser power, the whole thing is done at 20%. Just inserted a
M3 P100 S255
at the regarding position, now it’s fine.

2

OK, things getting weird: Now cloned the snowflake two times and created the tool pathes. Result:

  • GCode for first cut misses laser set to 100%
  • GCode for second burn misses laser set to 20%
  • rest of the GCode is correct!

So I went to the options of the first cut, typed in 100% laser power again. New GCode is rendered. Exported. Result:

  • GCode for first cut OK!
  • GCode for second burn misses laser set to 20%
  • Rest of GCode OK

Now in the editor set the value for the 2nd burn to 20% again. Result: GCode OK.

That’s crap! I don’t want to inspect the GCode every time for such errors…

3

It’s not a good answer, but I just use 3.14. (I don’t have rotary module)
I don’t like the new interface and the changes they’ve made.
I wish they’d improve Luban instead of just randomly changing it.

-S