GCode generator for PCBs from KiCAD files
Hi,
.
The project presented this time is purely programming but I hope it fits in this section and maybe someone will find it interesting or useful in the workshop. The aim of the project was to create a convenient-to-use GCode generator for making PCBs on a CNC milling machine. I design my PCBs in KiCAD so I focused on this input format. I've previously used FreeCAD for this purpose, but the conversion time and the number of operations required effectively discouraged me - processing one PCB could take me several hours, most of which was spent waiting for FreeCAD to convert everything.
As with previous projects, I decided to write the application in c# as a Windows Forms application using Visual Studio. The result is an application with which you can have a complete GCode generated in a few minutes.
Functions:
-Generation of code for milling paths including filled zones
-Generation of code for milling the shape of the insert, including any holes
-Code generation for hole drilling
-Possibility to select TOP or BOTTOM layer
-Automatic movement of the insert to 0.0 position
-Save settings
Description of operation :
The generation of the GCode takes place in several stages:
- The first stage takes place when the PCB file is opened. The file is parsed, all relevant elements of the PCB are searched for and saved as polygons consisting of segments and arcs. The filled zones are also converted to polygons. After this stage, the tile looks like this:
.
At the same time, a list of all the holes is displayed in the console window, this is useful to select the correct drill bits. This is the point at which all milling and drilling parameters should be set. If we now leave the default option "ALL" and press "RUN", all the subsequent stages will be executed sequentially and at the end a window will be displayed in which we have to select where the generated code should be saved.
It is also possible to perform these steps one by one.
- The next step is to merge the polygons belonging to the paths. In order to optimise execution time, only segments belonging to the same network are merged. After this step, the board looks as follows:
.
- In the next step, the paths are combined with the completed zones, also within the network:
.
- The final step in preparation for milling is to merge the fragments of the filled zones which are connected by paths:
.
- All polygons are now ready so this stage generates milling paths at the correct distance from the prepared polygons, separately for milling the copper and separately for milling the plate shape.
.
- The next step is to process the holes, matching them to the available drill list, the large holes are allocated for milling.
- The final step is the generation of the GCode from the prepared data.
What is missing:
Currently the milling of unfilled surfaces is not implemented - I did not need this for the time being.
The correctness of the insert is not checked, and the diameter of the cutter must be chosen so that it does not exceed the minimum distance between the paths.
The source code is available on github, feel free to test it and report comments and possible bugs.
https://github.com/r-gal/KiCAD2GCode
.
The project presented this time is purely programming but I hope it fits in this section and maybe someone will find it interesting or useful in the workshop. The aim of the project was to create a convenient-to-use GCode generator for making PCBs on a CNC milling machine. I design my PCBs in KiCAD so I focused on this input format. I've previously used FreeCAD for this purpose, but the conversion time and the number of operations required effectively discouraged me - processing one PCB could take me several hours, most of which was spent waiting for FreeCAD to convert everything.
As with previous projects, I decided to write the application in c# as a Windows Forms application using Visual Studio. The result is an application with which you can have a complete GCode generated in a few minutes.
Functions:
-Generation of code for milling paths including filled zones
-Generation of code for milling the shape of the insert, including any holes
-Code generation for hole drilling
-Possibility to select TOP or BOTTOM layer
-Automatic movement of the insert to 0.0 position
-Save settings
Description of operation :
The generation of the GCode takes place in several stages:
- The first stage takes place when the PCB file is opened. The file is parsed, all relevant elements of the PCB are searched for and saved as polygons consisting of segments and arcs. The filled zones are also converted to polygons. After this stage, the tile looks like this:
.
At the same time, a list of all the holes is displayed in the console window, this is useful to select the correct drill bits. This is the point at which all milling and drilling parameters should be set. If we now leave the default option "ALL" and press "RUN", all the subsequent stages will be executed sequentially and at the end a window will be displayed in which we have to select where the generated code should be saved.
It is also possible to perform these steps one by one.
- The next step is to merge the polygons belonging to the paths. In order to optimise execution time, only segments belonging to the same network are merged. After this step, the board looks as follows:
.
- In the next step, the paths are combined with the completed zones, also within the network:
.
- The final step in preparation for milling is to merge the fragments of the filled zones which are connected by paths:
.
- All polygons are now ready so this stage generates milling paths at the correct distance from the prepared polygons, separately for milling the copper and separately for milling the plate shape.
.
- The next step is to process the holes, matching them to the available drill list, the large holes are allocated for milling.
- The final step is the generation of the GCode from the prepared data.
What is missing:
Currently the milling of unfilled surfaces is not implemented - I did not need this for the time being.
The correctness of the insert is not checked, and the diameter of the cutter must be chosen so that it does not exceed the minimum distance between the paths.
The source code is available on github, feel free to test it and report comments and possible bugs.
https://github.com/r-gal/KiCAD2GCode
Comments
And you haven't used FlatCam? [Read more]
. You probably won't do much milling without sampling the surface with a probe beforehand, or the results will come out so-so. https://www.youtube.com/results?search_query=pcb+map+height+milli... [Read more]
This is taken care of by the CNC software, all you need is a map of the passes and the depth of the [Read more]
There is a plug-in for eagle that generates gcode in seconds on an old notebook with intel atom and 2 Gb ram. [Read more]
. I admit that when I started working on my project I was not familiar with this tool, maybe because I was looking for a converter for KiCAD files and not gerbers. Maybe I would have decided against... [Read more]
KiCAD exports to gerbers as well as the drill map. And FlatCAM I use and it is fast. Work on this because as a cool programmer this feature will come in handy. I will be happy to use [Read more]
I am testing (?) this programme, but every time a window like this appears: https://obrazki.elektroda.pl/7926977300_1757933612_thumb.jpg . Where to look for the error? [Read more]
. Hi, thanks for reporting the problem, it looks like there is a lack of support for some unusual pad shapes, you can see I didn't use such anywhere in my boards and it didn't work out for me. I didn't... [Read more]
And this is where I was surprised by something: In the archive in the "YES" directory there are the original "*.kicad_pcb" files from "http://mynor.org" - and they open correctly (?), while in the "NO"... [Read more]
Thanks for the test files. The problem with loading the files turned out to be quite simple, KiCAD 8.0 uses tabs in its files instead of the previous spaces which causes a network parsing error. I have... [Read more]
nice project [Read more]
I uploaded the new version v1.1 Files are already processing correctly, you can look for further problems and deficiencies ;) [Read more]
. I guess the author forgot about try-catch [Read more]
Hi, I've been away for a while but finally found some time and improved the program, removed some bugs found in the meantime and added milling of unfilled surfaces. Version v1.4 is uploaded on github,... [Read more]