Well I don’t know if it is just me or the upgrade or Marlin’s upgrades or the combination but I’ve just had a “looong” running conversation with ChatGPT in regard to an installation using VScode, Marlin CONFIGURATION_H_VERSION 02010205 and LightBurn Core 2.0.04. I had to Manually create a Device based on GRBL-M3 and make several alterations and additions to Marlin to make a dual Y-axis motor, dual Y-axis end-stop custom Openbuild ACRO machine running a typical Arduino Mega w/ Ramps 1.4 combination and get Lightburn to send M3/M5 codes to Pin 6 to fire the Diode Laser I’m using. I finally got it to run and printed an accuracy test pattern. Why doesn’t the Marlin Device in Lightburn have options to control the M3/M5 vs. M106/M107 commands? Why is the custom build option in the devices so limited? And last but least what needs tightening up to improve the symmetry of the X-Y movement?
How about you use the feature built into the forum… to suggest features? It is helpfully named FEATURE SUGGESTIONS…. .. ….
Request submitted.
I also received a response that shows the feature in 1.7.08 version that is not present in 2.0.04 and it does not appear to be addressed in the change log comments I found but I may have missed it as the updated to 2.0 was apparently quite extensive. I’m not clear if it went away, is hidden somewhere or was replaced with some auto-select feature that is defaulting to M106/M107.
I just replied to your email ticket - but you might just want to use Custom GCode Device Settings: Custom GCode - LightBurn Documentation
Thank you. I’ll give that a try this evening.
Reporting back that using the Custom GCode option in the Device Settings opened up the opportunity to change the default Laser On and Laser off to M03 and M05 as desired.
Still working through other options to see if any of them can also enhance the system’s performance. Like changing the Homing code to G28 from $H
Thank you for the recommendation.