appliedengdesign / gcode-reference Goto Github PK

Add per code markdown generation and all codes generated to markdown from JSON

Hi, I'm adding the Snapmaker 2.0 A350 and started with the additional Mcodes it supports for Milling + Lasering.
I started with the milling file and made a variant like the Mazak example, but I want to turn off the support for some (or all except 05 in this specific case) of the Mcodes that are not supported (m03-5 and M1010-11 are only ones supported). This isn't a problem for laser as currently there aren't the same default predefined Mcodes.
Running the npm run getCodes mill:mcode:snpmaker on my branch gets all the default defined Mcodes and then merges my changes on top (makes sense), but I can't see how to turn off the other Mcodes.
Also on a tangent, but related, could be nice to show the next depth in output

My variant looks like this currently

Would it be valuable to have variants defined for Marlin based 3d printers?

I'd quite like to use the gcode-sytax plugin for VSCode to edit gcode files for my 3d printer but the Marlin variant isn't included. Adding the variant files here looks to be the first step to getting that feature in the plugin.

Marlin documentation is here: https://marlinfw.org/docs/gcode/G000-G001.html

I've made a start here: https://github.com/JoeSimmonds/gcode-reference/tree/marlin and I think the rest is essentially just transcription from the documentation, but I didn't want to carry on unless you'd be interested in a PR for this.

Would like to see support added for Fanuc i-Series controls for lathe.

Dependabot settings need to be updated to create PR's for package.json and not just package-lock.json

Thanks @mikecentola for the remove section and latest release.
I've just pushed changes (then tested and fixed and retested 👍 )

Adding a pull request, but issue must be created first, so here it is!

I think this is a very interesting project and I'd like to be able to contribute to it. However, all gcode is not made alike. I own a Brother and a Mazak machining center, and there are numerous MTB-specific G- and M- codes that I'd love to be able to contribute here, but it appears at the moment that the schema does not support "variants" of gcode.

As a quick, concrete example, M10 and M11 are currently defined as brake enable/release. In Mazak EIA, M11 is going to unclamp the tool in your spindle 😅. Instead, you'd need to use M46 (unclamp 4th) and M47 (clamp 4th).

All the best,
Zach

Similar to the Markdown one I just finished. Create functions to get individual codes or all codes formatted in HTML.