Sat, 25 Mar 2017 14:16:37 GMT
I forked flatcam because I wanted to implement the customisation of gcode output that has been talked about in other discussions. I've implemented a post system, where we use a post file including what text to use for generating a G00, a G01, the coordinate format, what G-code to use for setting the spindle speed, what gcode to use for lifting the bit out of the material, etc etc. It's a system completely similar to what other CAM programs use (Each particuler machine has its postprocessor file with the special code that this particular machine needs).
I feel it's now "releaseable", if you want to check it out it's at https://bitbucket.org/matthieu_berthome/flatcam/branch/new-camlib
It's completely backward compatible, I've added unit tests to ensure that the default postprocessor generates exactly the same g-code as the previous system. It's a major rewrite of a part of the app so I hope jpcaram loves it ^^
With this system, everyone can customize the gcode generation to their particular machine (for me, the G00 and G01 instead of G0 and G1 was annoying, f or others it could be implementing multi pass drilling. It's very powerful IMO, and would free flatcam from taking care of too much of the specifics of the machining
Tue, 28 Mar 2017 14:30:23 GMT
Can you start submitting your changes in small chunks at a time?
Sat, 08 Apr 2017 12:25:40 GMT
I'll try to chunk my changes and send some palatable stuff :-)
Sun, 01 Oct 2017 17:15:33 GMT
This is very interesting idea and will end the search and replace in gcode for many of us. Has it been merged in the master yet?