We have early view of LightBurn 1.7.00, specifically for xTool S1 and BSL Galvo lasers! This adds support for BSL Devices, as well as the xTool S1 improbements.
Hi Colin,
Thanks very to you and all the team who are working on this, its very much appreciated. I wiil test and give you feedback in due course.
Cheers, Steve Jones.
@JoeSpanier will have more context than I here - but yes, the diagonal lines, general communication issues, air assist, and I believe rotary is also working in this release for the S1.
BSL lasers are also supported with this release, you’ll need to import the config into LightBurn.
i have an Atomstack M4 laser, which is supposed to work with SeaCAD. I can’t get it to work with the Lightburn 1.7.00 BETA version. Here’s what I’ve done so far:
Installed Lightburn version 1.7.00.
Connected the laser with USB, found it, and loaded the “BslCAD.cfg” file that has settings from SeaCAD. (With versions before 1.7.00, the laser isn’t even detected)
Checked the settings as best as I could and compared them with the settings in SeaCAD.
However, I’m still facing some odd behavior:
As soon as I start Lightburn and turn on the laser, it wants to start lasering right away.
Lightburn keeps flashing the message “Start Marking triggered, but no layers set to output” continuously.
Also, if I draw anything on the workspace, it immediately tries to start lasering.
I can’t stop the process; the STOP button in Lightburn doesn’t work anymore.
The only thing that stops it is turning off the power. It doesn’t laser what it’s supposed to, but instead keeps lasering a small triangle at what seems to be full power.
The console on the right side in Lightburn, which usually shows information when I’m working with my GCODE laser, is just empty.
I know this is a BETA, but maybe this information can help the developers, or perhaps someone else has an idea?
The console will never show anything, because there’s no human readable communication between this machine and LightBurn, and it doesn’t accept GCode commands, so that’s expected.
The ‘Start Marking’ behavior sounds like you have an IO pin set to trigger marking, and it’s on. Go to Edit > Device Settings (or press F3) and look at the Ports page for the Start Marking setting. If it’s not set to “None” change it to that. I just got an AtomStack M4 here, so I can see if it works here.
Doesn’t work with bsl cards like dbk21b. In Mac os is not connected, in windows its connected but(framing), galvos dont move. Maybe work with small cards.
Does the guide lines really need to default to 20 meters ? or is this a case of an extra zero slipping in ? Cant say that I have have heard of anyone making a Laser 20m in X or Y.
Try to keep questions there so they are easier to track. Let me know if there’s anything odd. I put a lot of testing in but I’m sure I didn’t get everything.
No, no problem just curious about size, initially it seemed overkill to me even if you were using Print and Cut. It turned out person I was assisting had Selected everything (including Toolpath) and moved to a single layer, and couldn’t work out why the job was going out of bounds when trying to frame. the job was roughly 6" square in middle of work bed, They kept insisting that it was only a reasonably simple vector and nothing else…until I connected remotely and could see what they had done.
Thank you!!! I have been waiting for months for this! I downloaded 1.7 and upgraded my license… it is working perfectly with my Mr Carve S4 Galvo laser with a BSL card. No more BSLAppsimple! So much better. Doing a happy dance. I have tested with the materials card in LB and with some slate coasters… works perfectly so far!