In Cutom GCode 740, if Cut through is not selected pause time is added in GCode. If Cut through is selected, Pause is removed from GCode. In neither case is Laser power set. Cut through does not occur. Bug?
In GRBL device, if Cut through is selected, laser is powered, pause occurs. However laser power is then set to zero before continuing. Why? Normally if you have cut through you would want to continue cutting.
Can you explain what this is?
Is your Longer Ray 20w a diode or a CO2 laser?
It’s a Longer Ray 5 20w laser diode. Custom GCode 740 is the new device available in the lastest Lightburn releases. The feature is part of Cut Settings Editor. Standard GRBL device behaves different from Custom GCode device.
Custom GCode means you have to check/adjust all the settings yourself. How does Standard GRBL behave differently?
Custom GCode and GRBL use the same Cut Settings Editor panel. However, each generates a different GCode. The problem is in the code generated when Start Pause time is set and Cut Through is also selected.
It’s been a few years since I similarly wrestled with ‘Start pause time’ and ‘Cut Through’ settings. What I recall is, once you understand the LB behavior that ‘Cut Through’ puts the pause cmd after the laser ON cmd, vs. without ‘Cut Through’ its before the laser ON, then there are [were] variations of gcode depending on use of M3 vs. M4 and, coupled with grbl controller behavior depending on being in laser mode ($32=1) or not.
1 Like
In GRBL device, behavior is supposed to be the way you state. In the Custom device mode, it should be the same. However. if a pause is set, a pause command is inserted into the gcode (G4 Pn). Then if Cut Through is selected, the pause command is completely removed. This is a software bug. This with Lightburn in laser mode.