Sielux SL2 10W Diode Galvo Laser (GRBL/GCODE) compatibility with Lightburn V2+

LightBurn Hardware Compatibility
, ,
1

HI,

I got a Sielux SL2 Galvo Laser, which is based on GRBL controller.

Sielux claims that it works with Lightburn. I tried for weeks to make it work with my Lightburn setup (currently at at V2.1.04, but I tried for several weeks on V2+, without success. It finally worked, when I used v1.7.00-RC-2-6e0d954.

Did something change to V2 on the way GRBL data is sent?

Would it be possible to make the Sielux SL2 laser work with V2+?

Thanks,

Marco.

2

The advertisement on an Amazon site says.

run production on PC/Lightburn

So I’d assume so.

:grinning_cat:

3

I meant to ask, to Lightburn Support, if V2.xx.xx can run the device (Sielux SL2), It runs with V 1.7.xx, but I have not been able to make it run with V2.xx.xx. And if there is anything I would need to change in the setup for that to happen.

Thanks,

Marco.

4

I’m not a Lightburn employee, but I have their stuff since before 1.0. Everything they do in a newer version is supported on the new version. If anything, it’s more likely that 2.0 and above will operate more machines.

I’m afraid I can’t be more exact. Lightburn pro is for a normal galvo, these are not gcode machine and their isn’t really a way for Lightburn to know what kind of controller it is. It’s unlikely, as far as I know, that it can even determine if it is a galvo.

There is no standard gcode for many of the standard galvo operations. If this happens, then it will think it’s just a standard gantry machine. In other words you won’t get some of the galvo parts you might want.

Hang in there
 Maybe @Aaron.F can help?

:grinning_cat:

5

Jack,

Thanks for your reply.

Yes, I would think v2+ would be compatible with 1.7x and below, with more functionality, but the fact is that v1.7.08 and below works ok with this galvo GRBL based laser. And v2+ does not.

I have several licenses of Lightburn, all PRO. And I use them with grbl, jzc and bsl controllers. Have not had issues keeping up to date on all my machines, until this one.

Hopefully someone from Lightburn support can help.

Thanks again.

6

Hello Marco,

Yes. Some “GRBL-Based” devices aren’t following the GRBL specs and we were missing OK responses from some devices.

In version 2.0, we rely more strictly on the appropriate feedback from the firmware, which has led to a situation with some devices where the lack of feedback causes LightBurn to think the machine is still busy processing.

Plus, some proprietary firmware implementations wrongly process all commands as “immediate” commands, unless we also sent a /n newline character.

Don’t worry, if that doesn’t make much sense to you, and I might be misremembering the exact details, but that’s certainly where we should start looking.

7

@malvarez Did Sielux send you a LightBurn Device Profile with the machine?
If so, please upload it here.

If you’ve manually set up the device in LightBurn, please export it to a .LBZIP from the Devices menu and upload it here.

My guess is that they are using the GRBL device type. We can then change this to our “Custom GCode” device type, giving more control over the codes we send.

8

I found the .LBDEV settings file on their manual page

I’ve converted it to use our Custom GCode device type:

Sielux_SL2_Custom_GCode_Aa_25-08-2026.lbzip (37.2 KB)
Download this file and drag it into LightBurn to add it.

The latest version 2.1.04 should be used.

If something doesn’t work, please try to explain it in as much detail as possible.
If you see any error messages in the Console Window, please enable “Show All”, do the same thing that led to the error and send us a screenshot of the entire LightBurn window, including the console output.
That would help us investigate what else could be needed.

I’m eager to hear how it goes!

10

Aaron,

Thanks for your help. I will download it and will try it today. Will let you know what I find.

Marco.

11

Aaron,

I installed the custom Gcode device. I did not get errors, but when framing, it only does it once and the framing does not correspond to what is on the screen. It completes the stream in 0:00

Also, when I hit start, it does the same one time framing, and the Start window does not come up. Nothing gets engraved. The streaming is also 0:00.

How can I send you a couple quick videos? They are 5MB each.

Thanks again for your help.

Marco.

AaronSieluxAfterFrame2026-08-26 064518
AaronSieluxAfterFrame2026-08-26 064518218×197 2.84 KB

12

That’s progress.

Yes. “Frame Continuously” is currently not available when using Custom GCode. We have an internal task to add this.

The speed of the framing is taken from the “Speed” inpout in the Move panel here:
Slowing it down should make it easier to see the trace, but you’ll need to press Frame again if you missed it.

image
image1151×630 32.3 KB

Hopefully, the videos you mentioned will explain this part.

You can upload videos to YouTube, or WeTransfer and paste a link here.

13

Additionally, I’d like to see the GRBL parameters of the firmware:

Please open the Console window (Top menu bar > ‘Window’ > ‘Console’), then Right-click this field and select “Clear Console”

Once cleared, please enter these commands, one line at a time, and press “enter” after each:

$i
$$
$#
?

Once completed, right-click the field again and choose “Select All”

Finally, copy and paste the results in a reply here.

15
Here is the console info dump. Not much to see...

ok

ok

[1.0.0(20240616)]

[VER:1.1f.20240427:]

[OPT:VNZHSL,2000,500000,3,0]

Target buffer size found

[BOARD:HY-Laser]

[AUX IO:1,0,0,0]

?

ok

?

$i

ok

?

$$

ok

?

$#

ok

?

?

?

The videos are at:

I changed the framing speed on the MOVE window, but there were no changes on the actual framing.

Thanks,

Marco.

16

Aaron,

I made another video with 1.7.00RC2 and 2.1.04CustomGcode. Here is the link. Thanks.

17

In the videos, the Start From option was set to “Current Position”:

image
image295×236 16.8 KB

This won’t work on a GRBL based galvo. Always use “Absolute Coords” here.

We have plans to create a dedicated device type for GRBL based galvos like yours to accomodate this and have it set to always use absolute.

The “Framing” window showed up in the 1.7.00 RC-2, because you were using the “GRBL” device type with “Continous Framing” enabled. That’s the the option that’s currently missing from the other Custom GCode Device profile. (We have a task to add this).

image
image1022×507 58.9 KB

18

That’s unfortunate.
We don’t know much about Sielux’s proprietary implementation of the firmware.

The command $$ is supposed to tell us important GRBL parameters like the S-Value, maximum speed and dimensions.

19

Thanks for jumping in
 Don’t know much about the gcode galvo machines.

Thanks for the information.

:grinning_cat:

20

Aaron,

Ok. I understand.

I changed to Absolute coordinates.

I tried it again, and I get the same results.

Thanks for working in the GRBL Galvo Device definition. In the meantime, is there anything else I can try?

Thanks,

Marco.

21

Can you record another screencap using the latest version 2.1.04?

Also:

22

Aaron, I apologize, I am out of town and should be back on Saturday. I will provide the information as I get back. Thank you very much for your help.