I’m still having problems with my XTool S1. I’m connected using the new XTool protocol but still my files keep stalling mid cut or mid engrave. I tried a Macbook and a Windows 11 laptop. No error codes thrown just stops and says it’s finished. On the macbook the laser kept firing when it stalled but on Windows the laser stopped. I’ve tried different baud rates on the com port but nothing works for me. It’s been a constant problem since I got the machine. It’s the same if I used the Xtool set up file. I was hoping the new Lightburn protocol would fix this but it’s still the same. Not sure what to do or if there is anything I can do. Thanks for any help.
Everything you describe appears to be a hardware problem. Try running a test using maybe 25% laser power and see if it completes.
I run Xtool S1 with Lightburn 1.7x and 2.0x and both work without issues. Yes with 2.0, there are still some bugs, but nothing specific with Xtool S1 thus far with 2.0 rc6.
Brian
1 Like
I’m using 1.7x but I’ve had problems always. Are you running from Windows? What is the baud rate of your com port in Device Manager? I wish I could figure out what’s not working!
I’ve run marking at 25 and 30% and cuts at 85-100% and it’s always the same. Adn when marking I find that in some spots it will accelerate rapidly and then slow down again for no reason I can fathom. I don’t have constant power enabled but when it speeds up the line is fainter so the power is not changing with the acceleration.
That is Fast Whitespace Scan in the Device Settings window. It speeds up in the non-burn (white space) areas of a scan to help lower the burn time. You can turn it off if you want.
Can you provide a clear image showing this? There should be no marking in the whitespaces.
It’s not in white spaces. It’s along the cut or burn lines. It just speeds up sometimes.
If this is true, it is not Lightburn doing it. Although it will be a difficult search because there are many lines of code, but it can be verified be examining the GCode generated by lightburn.
If you wish to test my claim:
- Run a program that fails (speed up thingie).
- Generate (save) the GCode from the program that failed.
- Make a copy and add .txt to the end of the filename.
- Attach the copy to a Reply. We will examine it.
- In Lightburn, use the Run GCode button and select your original GCode file.
- See if the GCode file also shows that speed-up characteristic.
- Report the results of your test with the GCode file.
Good luck!
I decided to reset the connection with my computer in Creative Space so I set up the S1 as a new device with a usb connection and ran a file with multiple layers successfully. Then I shut down creative space and connected with lightburn on the same com connection. And I ran multiple different files with lots of layers in each and they all ran successfully. I still feel like some of the curves are burning at different speeds but it could be an optical illusion since some of the curves are smaller and tighter radii and some are much bigger and longer. Maybe I’m seeing acceleration differences? Not sure. But the good thing is that multiple files ran to their ends without stalling. I’ll try again another time. Thanks for the help.
1 Like
I have been using Lightburn 1.78 and 2.0 latest release candidate with my Xtool S1,and I have had no issues with windows 11
Make sure you have the latest firmware for your laser.
Brian
1 Like
Thanks. I reset my connections with the S1 completely. I reset it in Creative Space first and then in Lightburn setting it up as a new machine and deleting the old connections. Thankfully, I have not had any issues since with stalling.
1 Like
I was having the exact problem this past week. I’d been using LB with my S1 with no problems for months, but then it started freezing just as @vlnmkr described. I’m using 2.0 RC6 and latest S1 firmware. I did the same thing you did by using XCS to reset the connection and LB is doing much better. I’m still seeing weird control characters in the console though, which concerns me, but at least it doesn’t hang. The time estimates to complete the job go into negative territory every time however.