buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

export to cnc (and other formats) #1033

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
is this basically a gerber format and if so, how does it differ from the 
current gerber export

Original issue reported on code.google.com by irasc...@gmail.com on 31 Mar 2010 at 11:42

GoogleCodeExporter commented 9 years ago
Actually, this means export to gcode.
Brendan discovered pcb2gcode that we might be able to incorporate:

"Including in fritzing would be pretty easy as it's all written in C and 
only depends on libgerbv.  The project is also actively maintained.  It 
appears to be GPL-2 licensed which also works for us but we should sent 
them a mail as I could not find the normal GPL boilerplate in the SVN or 
the source tarball."

http://sourceforge.net/apps/mediawiki/pcb2gcode

Original comment by andre.knoerig@gmail.com on 30 Jun 2010 at 9:45

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 29 Sep 2010 at 6:29

GoogleCodeExporter commented 9 years ago
note this http://wiki.protospace.nl/index.php/Milling_PCB_From_Fritzing from 
forum post http://fritzing.org/forum/thread/49/?page=all#post1484

Original comment by irasc...@gmail.com on 9 Dec 2010 at 11:13

GoogleCodeExporter commented 9 years ago
And an amazingly complete list of scripts and tools from RepRap at 
http://reprap.org/wiki/PCB_Milling

Original comment by andre.knoerig@gmail.com on 14 Jan 2012 at 8:49

GoogleCodeExporter commented 9 years ago
Another alternative could be the FabLab toolchain: http://kokompe.cba.mit.edu/
Seems to be open-source, however its license is limited to non-commercial use.

Original comment by andre.knoerig@gmail.com on 12 Jun 2012 at 1:29

GoogleCodeExporter commented 9 years ago
Issue 1501 has been merged into this issue.

Original comment by irasc...@gmail.com on 5 Sep 2012 at 8:28

GoogleCodeExporter commented 9 years ago
Issue 757 has been merged into this issue.

Original comment by irasc...@gmail.com on 5 Sep 2012 at 8:29

GoogleCodeExporter commented 9 years ago
Issue 1375 has been merged into this issue.

Original comment by irasc...@gmail.com on 5 Sep 2012 at 8:29

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 5 Sep 2012 at 8:30

GoogleCodeExporter commented 9 years ago
Perhaps I should encourage you a bit :-) Export to G-code isn't that difficult. 
gEDA/PCB does it in a couple of simple steps:

- Draw the design to a (memory based) PNG, blown up by half the cutting tool 
diameter. Code from the PNG exporter should do that fine.

- Convert this to a bitmap for potrace (http://potrace.sourceforge.net/). 
Simple pixel copy operation.

- Run potrace over it's bitmap and catch the output. gEDA has tweaked potrace 
for writing G-code text instead of SVG text to do so.

- That's it!

If you look at gEDA/PCB's source code 
(http://git.geda-project.org/pcb/tree/src/hid/gcode/gcode.c), you'll see some 
80% of that code is just about writing file headers and footers, about PNG 
writing, user definable milling depths and other non-essential/easily writeable 
stuff.

Original comment by m...@jump-ing.de on 7 Sep 2012 at 2:04

GoogleCodeExporter commented 9 years ago
Issue has moved to new issue tracker at github. Please continue the discussion 
at https://github.com/fritzing/fritzing-app/issues

Original comment by andre.knoerig@gmail.com on 23 Sep 2014 at 3:37