Lightburn 2.0.00 adding move to absolute origin

LightBurn Software Questions
1

I upgraded from 1.7.08 to 2.0.00 and now when I save GCode the generated file contains a move at the end of the file to the absolute origin even when I’m using User origin. For example, comparing the GCode generated from 1.7.08 to 2.0.00, I see the one additional move line:

# diff User\ Origin\ v1.7.08.gc User\ Origin\ v2.0.00.gc
1c1
< ; LightBurn 1.7.08
---
> ; LightBurn Core 2.0.00
426a427
> G1 X-7.2845Y-8.6117S0

Is there a new option in 2.0 that I need to disable? The move to the absolute origin causes my laser to go out of bounds. I can delete the extra G1 line from the generated file and things are good, but I can’t figure out why that line is being generated now. The origin settings look identical between versions.

Thanks,
-mike

User Origin v1.7.08.gc (7.8 KB)
User Origin v2.0.00.gc (7.9 KB)

User Origin 1.7.08
User Origin 1.7.082654×698 102 KB

User Origin 2.0.00
User Origin 2.0.002642×780 285 KB

GCode preview 2.0.00
GCode preview 2.0.00742×358 18.9 KB

3

That is odd - I’m looking into it.
You wouldn’t happen to have a workpiece offset set would you? (if GRBL, you can check the values by sending $# in the console - if any of the values in the square brackets [] aren’t 0 it would help me narrow it down.

4

Do you have a value set / or the toggle enabled for Return to Finish Position in the device settings?

image
image878×607 50 KB

5

Thanks for looking into it. I don’t have Lightburn directly connected to my machine but I simply export the gcode and upload it to the machine manually. So I think that means the offsets don’t apply but maybe I’m misunderstanding your question.

My first thought was the “Return to Finish Position” option but I’m pretty sure I had that enabled in v1.7 without issue. I’ve tried it enabled and disabled in 2.0 but it doesn’t seem to make a difference. It always generates the move to the absolute origin even when using user origin in the exported gcode.

6

Thank you for testing Mike.

Can I ask you to share your configuration bundle (device profile mainly) here? It will help us debug this issue, as we’re already looking at it from other users.

If you can also share the design, that would be appreciated as well (if you prefer not sharing the design in a public forum, please email it to support@lightburnsoftware.com and put a link to this forum thread along with it).

We’re really confused by how all these bugs have cropped up when we’ve been testing things for so long, and not seen them, and doing our best to fix them for everyone ASAP.

7

Here you go.

onefinity_device_export.lbzip (1.6 KB)
Dev Display GPIO v1_5.lbrn2 (8.8 KB)

8

Hello
I have the same problem. I have two devices, a Sculpfun S33 and S9, and the same thing happens with both. It adds travel to the absolute origin, and I haven’t been able to disable it. Could you please help me?

9

Thanks! We found the bug that was at the root of a lot of headaches - we think.

If you can give a try to the 2.0.01 RC we would appreciate it.

Please let us know if this resolves your issue.

10

Great! Thanks. I’m away from my shop for a few days but will check it out on Monday if someone doesn’t get to it first.

1 Like