Since the update to the current version my laser control command setting to Inline not set in gcode and replaced by M106/ M107 commands but Inline is set!
Then I am forced to go to the settings and set to M106 or M03 and back to Inline to get the S Values in the G moves again in the exported code.
Even after an update from 1.0.04 to 1.0.06 the same issue exists.
This is a bug and not a feature 
Hello, I have the same problem, is there a solution?
Unbelievable, no support or reply for a payed software!
I didn’t understand this post but assume it’s related to Marlin. Is the generated g-code the same whether or not inline has been selected? Can you pinpoint the specific version when things changed?
Don’t know if the change was deliberate but perhaps downgrade to an older working version until the problem is resolved.
Hello, thank’s for the reply.
This issue appears after the update from LB 0.9.24 to 1.0.0.04, and yes I use Marlin style GCode creation.
The issue are that even if in LB the Inline laser control is set after a restart of LB the GCode is Created with M106 / M107.
When I then go into the LB Settings and select M106 or M03 and then Inline again the LB GCode is created as selected.
There is a bug → LB do not read the user made settings on startup and uses not selected default values.
Hopefully this is just the laser control settings but I assume it is more than that.
So essentially you’re saying the issue is that the setting to use inline for Marlin devices is not respected after a restart of the application starting from v1.0.04? But that inline continues to show selected.
Can you confirm that going back to 0.9.24 eliminates this problem?
Not sure if it’s related but I noticed a different problem where display text size changes did not survive an application restart. This has been recognized as a bug.
Yes, with the old Version 0.9.24 this issue do not exist, I do not have any other version between the 09.24 and 1.0.04 to test on which version exactly this issue appears.
You can get access to all LightBurn releases here:
Releases · LightBurnSoftware/deployment · GitHub
If you can identify the version where behavior changes it would help the bug report.
Tagging @LightBurn here for visibility after the holiday.
You are posting on a community forum, and we unfortunately can’t read every message here (though we do try). If there is something that you feel requires a response, it is best to email support@lightburnsoftware.com
I will have a look and see if I can reproduce this.
Are you actually connected to a laser, or no? (As in, do you have a COM port chosen and are actively connected to a device?)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.