How to modify the custom gcode flavor

Hello,

I’m very interested in Millmage. I’m sure I can run it at home, but I’d love to offer it as an option at work as well. The problem is that my controller at work is a Syntec controller and would normally work as just outputting gcode, but the problem is that in Syntec controllers, it uses g70 / g71 for inch / metric and not g20 / g21. I was wondering if there’s a way to modify and load your own post processor / flavor into millmage (yet) or if it’s a future option.

TIA

We actually just released a video about this!

5 Likes

Thanks for the heads-up, Colin! I’ll check out the video to see what’s possible. Just to clarify, does the custom GCode feature support fully replacing commands like G20/G21 with G70/G71 globally, or is it more about adding macros or snippets at specific points? I’m mainly trying to ensure compatibility with a Syntec setup, so a full override would be ideal.

that video has helped with my tool change issue changed M0
to @P tool changes work great now



your guys support is awesome , cant wait for more updates
keep up the awesome work

1 Like

at 3.10m where you type in tool name i dont get that coming up



is my test correct ?

It doesn’t look like G20/G21 can be custom to G70/G71 from this page. I’ve looked at this earlier, but was hoping there was a different way to customize it.

It doesn’t have inch/metric overrides. It looks like I would probably have to post edit the gcode to make it work. This is something that I can do, but probably wouldn’t want to for every file I write. It would be nice in future releases if we were able to create and import our own “Gcode Flavor”. For more advanced users to be able to create it and post it online for others to import. I think most machines use similar gcode, but there are areas that don’t quite overlap (such as the syntec machines).

Sounds like a new feature request to add this to the device settings/custom gcode dialog :slight_smile:

So… Theres more to the flavor than just the output. It also changes how we handle communication in the background for flavors that we do full control over and enables and disables some of our UI tools.

We are already looking at making a more customizable header output, but there is definitely going to be more use cases like this popping up to add more control for flavors we do not control.