GCode Generation is only making files of 191 bytes

[thiggins (Tom)]

I fired up Lightburn today and all the gcode files I’m generating are all the same size of 191 bytes and only contain the following code:
; LightBurn 1.0.04
; GRBL-M3 (1.1e or earlier) device profile, absolute coords
; Bounds: X0 Y0 to X0 Y0
G00 G17 G40 G21 G54
G90
M5
M9
G1S0
G90
; return to user-defined finish pos
G0 X0 Y0
M2

I don’t recall changing any settings that could cause this output to be modified, so I loaded previous working files and tried saving their gcode again only to generate the same 191 byte files. Can someone assist?

[parsec (FerAS)]

Post one project .lbrn2 file where this happens and the GCode for us to check.

[thiggins (Tom)]

5 o’clock1 Barrel Stave.lbrn2 (17.1 KB)
5 o’clock1 Barrel Stave.gc (191 Bytes)

[parsec (FerAS)]

If you do a preview before saving the GCode what shows up in your preview window?

Enable ´Out of Bounds´ warning as a preventive measure if your OF has a 815 x 1222 mm and your shape as a width of 819.392 it wont be sent to the laser/GCode.
Report back with the dimensions please.

[thiggins (Tom)]

Nothing but a red crosshair shows up in the preview window:

My onefinity Jtech setup is 819x819 mm.

Here are working files from the other day:
Drink Local Horizontal Barrel Stave.lbrn2 (16.5 KB)
Drink Local Horizontal Barrel Stave.gc (199.4 KB)

As I stated initially, when I try opening and saving the gcode on these files today, the same 191 bytes files are created.

[thiggins (Tom)]

I think I figured it out. For some reason, the start from position was changed to Absolute instead of User Origin. I switched it back to User Origin and now I can see it on the preview and the Gcode file is more than 191 bytes.

[parsec (FerAS)]

The new file with a smaller shape was set to User Origin

and the first one is in Absoluite Coordinates.

[thiggins (Tom)]

Thanks. I appreciate it.

[parsec (FerAS)]

Check whether is best to use User Origin or Current Position.