Relatively new to the forum and have been learning a lot from reading the various posts. Have not found anything regarding a specific issue in havingso thought I would throw out my first post.
One of my laser units is a multipurpose CNC platform that started out as a CNC router/plotter/drag cutter and has since morphed into a laser platform. Currently using two different blue diode lasers, 1x 10W and 1x 45W depending on the need. Both have PWM power control. I do not try and run them directly from LightBurn but rather just export a gcode file and run it via LinuxCNC on the unit. This has been done happily for quite some time using LaserWeb. Recently acquired LightBurn Pro (LightBurn Pro 2.0.04) to control a Thunder Laser Nova Plus 24, which it does very well by the way. The problem starts when I try and standardize on it and use it to also export gcode to my blue lasers.
Vector cutting and engraving are working fine with some minor tweaks to the custom code to start the laser at low power right away, get rid of S0 commands and have a min power on the laser. I have found that with my hardware set up the diode takes a moment to spool up and with the tweaks vector stuff works fine.
Raster images though are still not optimal. Have got them to work reasonably well by using M67 commands substituting S commands for power in lieu of the Q command. However, unlike the Thunder Laser on Ruida where the laser travels in X at a uniform velocity from side to side firing the laser when necessary - my LinuxCNC treats each on or off of the laser under M67 as a separate move with the X travel constantly starting and stopping. Although it works and looks surprisingly good it is as you can imagine jerky and takes much longer. Does anyone know a trick to get LinuxCNC to behave like the Thunder and sweep continuously? I have been searching documentation for a while and have not found anything yet.
Hope you can just say “well all you need to do is this stupid”.
Regards,
Stephen