Hello I ran the wobble_01.lbrn2 under lightburn 1.7.04 and here is what I got with my 40w xtool s1 -
Are we all running the same firmware?
Could you post yours please?
Not sure if you already did but for the sake of continuity?
I also have my units set to mm/min I thought somewhere someone said if you had it set for mm/sec it would cause issues.
It used to be mm/min and mm/inch would cause issues, I believe this is patched.
ok, I will have to test when I get a chance, and see if there is a difference. Thank you, Brian
I tested, and it works with mm/sec and mm/min no issues. I did notice one thing. If I startup the laser first and then load lightburn, the laser connects, homes, and then I focus, but then if I goto run a job it will not work. SO, I load lightburn first, then turn on the laser and all is good. Just noting this, as I never had this issue before.
1 Like
Sometimes, I experience similar behavior with my S1, which is on 24/7 and connected via USB. Occasionally, the LB connects but doesn’t home. When I command a frame, the process never ends on the software side — the progress bar keeps running, and the timer continues counting, even though the frame finishes as expected on the laser. When I start a job in this state, it burns one line and then stops.
I’ve learned that when I see the progress bar running for no apparent reason, I need to switch the laser off and on. This action resolves the issue every time.
Exactly. This is why I’m fiinding, to load lightburn first, then turn on the laser. I’m also finding, If I create a test image, with 6 or more layers, that I created using the trace function, Lightburn will crash.
I just saw that RC4 dropped. I compared GCode output from RC2, and they were the same outside of the version number incrementing. Do the developers have any info on adding the X/Y moves to reduce the wobble?
Hello Raine,
This is still being worked on, I should have a possible update this week.
Or possibly @adammhaile will have!
Not forgotten though!
5 Likes
@raine @pmbrothny @lastingimage
Could you guys give RC5 a try:
The RC that Gil linked above includes code that always outputs X & Y GCode when generating cutting moves.
If I save to a gcode file will it also write both X/Y? As I’m not seeing that happen.
That is a great question - that is @LightBurn question.
1 Like
There is no difference between running a job and saving the GCode - the way the GCode is generated is identical.
X & Y coordinates are only forced to output if you’re running a Line or Offset Fill layer (not Fill or Image), and only if you are using the XTool specific device, not GRBL or generic gcode.
1 Like
Understood. Thanks!
1 Like
Thank you Oz!
