Converting File to gcode

I have just had a problem with converting files with layers to gcode to use directly with with laser from a card.

I have a Creality CR Falcon 10 and replaced with Creality Falcon 2 12W. The second machine was included as a device in between using the original Gcode and using the 2nd gcode…

On Monday the gcode came out in the correct layer order but from today they are coming out in the order that the layers were written.

I have 1:changed the colour of the layers and 2: changed the name of the layer to the order required but the Gcode still comes out in the incorrect order.

This is the start of the original version
; LightBurn 1.4.03
; GRBL device profile, absolute coords
; Bounds: X135 Y7.5 to X265 Y407.5
G00 G17 G40 G21 G54
G90
M4
; Cut @ 1000 mm/min, 70% power
M8
G0 X175Y25.5
G0 Z0
; Layer C01
G1 X260S700F1000
G0 X260Y29.5
G1 X175
G0 X175Y33.5
with all layers in order

This is the new gcode starting incorrectly

; LightBurn 1.4.03
; GRBL device profile, absolute coords
; Bounds: X135 Y7.5 to X265 Y407.5
G00 G17 G40 G21 G54
G90
M4
; Cut @ 350 mm/min, 100% power
M8
G0 X265Y407.5
G0 Z0
; Layer C00
G1 Y7.5S1000F350
G1 X135
G1 Y407.5
with the rest in time written as the order

Is this a Lightburn problem or a Creality problem??

LightBurn is exclusively responsible for generating the g-code.

If the generated g-code has a different ordering from one time to another and the design or Cut/Layers have not changed then it’s likely something was changed in “Optimization Settings” in Laser window.

Check the Ordering section there.

Also, make certain that indeed nothing was changed in the ordering of the Cuts/Layers.

Thank you for your prompt reply. That solved the immediate problem, but the question still remains as to why the settings changed. Do they change each time you make an alteration to the Lightburn file?
I allowed that the addition of the new machine would cause the change.

Not arbitrarily. But if a change is made, it will be reflected there.

Note that if you have opened a .lbrn file with different settings that could be a factor in this.

Hasn’t occurred again (thank goodness) must have been a human or maybe a change of machine error.

Thanks for the help.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.