There are quite a few commands that are not responded to when LightBurn is talking to the controller by watching the debug log and the console. I am a CNC novice to be sure but GCode for a laser seems pretty straightforward to me anyway so long as the controller supports the commands in a way that is understood. With the safety glasses on or by watching through the lens or the LEDs on top you can tell when the laser is trying to cut and when it not. Other times it would start the burn, finish only the first letter, the capital “I” in the word Interval and then stop engaging the laser for the rest of the layout even though it would go through the motions. Sometimes the laser would stay on during the traversal moves for example. They would move the laser around for the most part, but did not seem to control the laser correctly. Not really, but I have tried Marlin and all three GRBL profiles. LaserGRBL works a bit better as far as printing, but the generated GCODE syntax for burning is quite a bit different.įor example, it seems the laser enable/disable is not explicit enough and the Sxxx laser power on the G1 commands is missing on nearly all of the text for the LaserTools->Material-Test for example. I tried upgrading to LightBurn v1.2.04 with the same results. I am running v2.0.8.24F4 on the controllers and screen version 1.0.2. Primarily the laser power and on/off function does not correspond to standard GRBL behavior.
The laser module firmware in the Creality Ender 3 S1 Pro does not seem to support the commands required for LightBurn to successfully engrave and cut.
0 kommentar(er)
