G54 frustration, and file extensions

[Mike_B (Mike Bogart)]

Wondering if there is a way to turn off the output of G54 to gcode? I’m using a CNC with a laser attachment and have programmed offsets for some of the common projects I make. With the output of G54 I’ve been screwed a couple of times now. My CNC automatically changes the offset from the laser to traditional CNC via tool offset. So if I’d like to use a fixture that is programmed to let’s say G56 and then switch to laser on that offset currently I have to remember to go back to G54 and set zero. It’s something I’m likely to forget more than once. I don’t see a postprocessor per se in the Lightburn directory, I’m happy to change this myself if someone can point me in the right direction.

Also, is there a way to set a default file extension of gcode that is output? My machine will only accept .NC and again I find myself forgetting to type in the .NC and end up with a .GC file that my controller won’t load.

I feel like these would be fairly simple feature additions to a future version if there isn’t a way to accomplish these items already?

TIA

[berainlb (PY)]

@Mike_B

I don’t see a postprocessor per se in the Lightburn directory, I’m happy to change this myself if someone can point me in the right direction.

You can set Pre and Post g-code commands in the G-code tab of Edit->Device Settings. Or else setup a Macro in Console to do this before running.

@Mike_B

Also, is there a way to set a default file extension of gcode that is output?

Manually enter .nc the first time you save gcode… after that, it should use .nc by default for subsequent files even without explicitly entering the extension.

[Mike_B (Mike Bogart)]

@berainlb

You can set Pre and Post g-code commands in the G-code tab of Edit->Device Settings. Or else setup a Macro in Console to do this before running.

This route isn’t really how I’d like to go. This still means having to enter separate offset commands for different locations in the macro or pre-command in the settings. It would be much better for me if the G54 could just be removed from the header of the gcode (without having to manually edit the code) so that whatever WCS I’m in will be applied when I run the file. A macro won’t work either way my machine isn’t connected via USB I’m saving the files to run them from my controller. My controller can’t be connected via USB to Lightburn.

@berainlb

Manually enter .nc the first time you save gcode… after that, it should use .nc by default for subsequent files even without explicitly entering the extension.

As for the file extension, I previously was using .GC on my old machine. So do I have to uninstall and reinstall Lightburn to get it to save .NC automatically?

[berainlb (PY)]

@Mike_B

It would be much better for me if the G54 could just be removed from the header of the gcode

I’m not aware of any way to do this. LightBurn always works from the same work offset for consistency from what I’ve seen.

@Mike_B

So do I have to uninstall and reinstall Lightburn to get it to save .NC automatically?

Save the file with an explicit .nc extension. Subsequent saves should retain the .nc on its own.