Initially installed Lightburn, loaded Creality Falcon 2 as device, was working just fine pulling in images. Switched units to inches, then noticed that output gcode was no longer correct. The bounds are correct in the gcode, but after that it is no longer correct. This happened on another PC but once it was reverted to mm it worked as normal no issues. Below is what I am seeing. This is only happening on the IMAGE mode. If I draw something using the software tools, it generates correct gcode.
; LightBurn 1.4.01
; GRBL device profile, absolute coords
; Bounds: X162.95 Y185.15 to X240.25 Y246.25
G00 G17 G40 G21 G54
; Image @ 100 mm/sec, 20% power
; Layer C00
Perhaps the issue you’re referring to is self-evident in the same gcode but it’s not apparent to me what you’re indicating as being a problem.
Can you elaborate and call out specifically what it is that you think is a problem?
In the gcode below, I added a circle with the Lightburn software. As you can see, the final passes of the Image, the gcode is still not within the bounds. Then the code transitions to the circle I drew, and now the gcode is correct and within the bounds of the objects. The incorrect gcode is generating negative numbers…how is that?
; Cut @ 100 mm/sec, 20% power
; Layer C00
Not within the bounds of what?
Are you thinking that negative values are invalid? The G91 at the start of the block indicates relative moves will be used, not absolute coordinates. So all the moves are just relative from current position. Negative values are fine in this case.
In my first post, there are four identical lines as shown below…
Is there an explanation for this?
Impossible to say without understanding the specific context and the details of the gcode generator.
But it’s not invalid in any way.
Let’s approach this differently. Are you experiencing an issue that’s making you question the gcode? May be better to focus on addressing the core issue.
For the record, I’ve never once seen LightBurn create bad gcode for geometry so I tend to think that’s not generally going to be the problem in most scenarios. Not that it’s impossible.
You are correct, gcode is simply being generated using the various settings/configurations. I believe it’s a setting issue that I may have changed not knowing. Again, I load an image file .png or .jpg, the system automatically recognizes it as an image and sets the mode accordingly. When I try to etch the file, it correctly frames the location so I can set the material in the correct position but when I hit start, it simply goes to the start position and just sits there. I’m assuming its going through the gcode with the tiny movements as shown in the code…but it definitely does not etch the image in the location as shown in the software. I uninstalled the software and tried to delete any config files and still having these issues.
Upload the .lbrn file for review.
Because of the
G91 setting relative move mode, those four motions will produce four 0.1 mm moves to the left.
Running the G-Code through a simulator shows they’re part of what looks like a slightly bent straight-ish line. Without knowing more about the original design and how it was created, the backplot seems reasonable.
Are you thinking in inches with the UI set to millimeters?
I don’t see a fundamental problem in the design or in the gcode.
I think it’s more than likely that there’s a problem on the machine side.
Are you saying that you’re able to use another computer to connect to the same laser without issue?