



I know that is a painful thing to do, but it is the correct way to go.Since you already have Marlin 2.0.9 I would strongly advise you to not use this feature, disable it and instead turn on LASER_FEATURE in the configuration and re-flash the controller. I thought it would be nice if there were a list of specific g and m code definitions that Lightburn creates. I tried to do some research, but laser_power_inline appears to be pretty much undocumented, the only matches I get are to the Marlin M3 page, which says ‘dont use with laser_power_inline’, and this bug, which doesn’t look promising.Īnd, I can confirm that LaserWeb does not produce code with the necessary G1 Xxxx Yyyy I Sxxx power setting lines used by laser_power_inline, and is unlikely to do so just to support this feature. I was confusing laser_power_inline with the real Laser feature of marlin 2.0.9, as documented here and enabled by setting LASER_FEATURE in the Marlin configuration.
