I’ve been saying this for a while. The question is what specifically triggers the bug on the S1.
It seems xTool is giving users the runaround and not even accepting it as an issue.
honestly seems like a little parser bug on S1 only firmware
but xtool priority might not be to fix it at the moment
might need a bit of patience and or push.
1 Like
Bet you too if you remove the end script commands
(which i am unsure what they do)
but very probably the laser will run across and stay ON
my suspecious is the xtool gcode interpreter is trimming a bit of the bottom of Gcode
Not this time. All I got was a big advertisement.
Take the file and add .TXT to the end of it. You can then paste in in the reply box.
I’m seeing the same problem w/ my S1. I had been using the same file w/ a D1 pro before w/ no issues. Traingles in my file and even on a light burn “material test” run. Watching this thread for updates. I’ll file a ticket as well.
the file is 12 mb
even when I copy paste it into a new file and save as txt.
can’t upload it into this forum. to big it says. that’s why I tried wetranfer.
uploaded it to drive, now.
I am having the same problem just running the test wizard on my xtool S1 with 40w laser. v40.32.007.2025.01
1 Like
when reimporting the gcode to lightburn or lasergrbl it seems perfectly correct and valid
I am still convinced this is a issue on the xtool S1 firmware interpreter layer.
Only Xtool or Lightburn deep dive might figure it out
Did you have a chance to test that g-code to see if it would recreate the issue?
yeah using the Gcode cuts the triangle.
I also think it’s firmware related.
assuming zero word from Xtool so far?
correct that is
Can you try these additional variants. These all have simplified scenarios in different ways. Trying to narrow down to the simplest case.
S1_triangle_bug_M4.gc.txt (556 Bytes)
S1_triangle_bug_no_image.gc.txt (431 Bytes)
S1_triangle_bug_no_image_M4.gc.txt (431 Bytes)
S1_triangle_bug_no_image_no_M.gc.txt (427 Bytes)
What are the results for each file?
I also see when sending a ticket its not being registered in there system. that’s why it may take so long. I just retried sending it.
Is this helpful at all? Output Looks Wrong - LightBurn Software Documentation
this situation really seems to be a Xtool S1 firmware issue on the Gcode decoder/Planner/translator thingy
1 Like
Just to add I’m getting this too so will keep an eye on this thread. I’ve also logged a ticket with Xtool.
2 Likes
We’re aware of this issue and have logged the issue into our internal system.
We’re making progress on opening up a more constructive dialogue with xTool - thanks for your patience everyone.
1 Like
Hi, I don’t know if this will help at all but I’ve been experimenting with this problem.
I have created my own test cut. All layer modes are Line. Layer 00 is an engrave layer containing text. Layer 20 is the final perimeter cut. All other layers are the squares for the test.
Here’s the interesting thing: Wherever you position layer 00 (the text engrave), the triangle error ONLY occurs after it.
In the image attached, top left cut is without layer 00 output.
Top right cut is with layer 00 positioned after layer 15
Bottom left cut is with layer 00 positioned after layer 14
So it seems something within layer 00 triggers this error.
I hope this may be of use to you!
Attached image and gcode.
LB Test Cut.gcode (56.4 KB)