Simple G-Code Generator

Hello everybody,

based on the python scripts in the wiki (wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple...NC_G-Code_Generators) I wrote a framework for small python g-code generators (for milling):
Download and screen-shots here

Currently (v3.3.0) it supports the following generators for milling:

• Outlining: Rectangle, Circle, Arc, Ellipse, Polygon
• Pocketing: Rectangle, Circle, Arc, Slot
• Drill: Matrix, Grill
• Engraving: Bezel, Text (all qcad fonts are now usable)

Other features:

• Save, load and insert projects.
• Edit values and order of generated objects (see above).
• Remote control of AXIS to load the generated g-code.
• Easy to add other generators or modify existing ones (at least this was the goal).

It is meant for hobbyist use only, so please do not expect the perfect path generation.
So this is my small contribution.....if anyone is interested to optimise, debug, add generator features, please let me know and I will write a short how-to. Any feedback is very appreciated!

Best regards
Erik

Thanks for your feedback!
I was able to reproduce it: It is an issue with the encoding (end of line). Running dos2unix solved it. Still do not know how this happened. The configuration of the editor that I use seems fine.
Update on the way...
Erik

Updated version 3.3.1 is available.

I think I fixed the segmentation fault issue. There were mandatory parameter checks (avoid endless loops) missing in three classes.

Version 3.3.2. is now available.

I am not sure if I understood your suggestion. Default units and plane for each object, or overall? For overall I got the preamble (custom code). I guess the metric default values are an issue, right? They can be edited in the code in the file <nclasses> class <Basedata>.

Found another issue on my LinuxCNC controller. I do not get axis-remote working from within the script when started stand-alone (the button <Save & LCNC Load> should be activated if LCNC is running.

Erik

I assume setting the units is only needed once. At the moment there are two ways possible:
1. edit the default preamble in the code <sgg.py> or...
2. put a g-code file named <preamble.ngc> into the directory of the script. This will be loaded as the default. Same works for the postamble.

Setting the plane makes sense for each object. Unfortunately the object classes are not written with this in mind. I will have a look on that...

Erik