These shapes were removed from the trace data, rounded off to the nearest available tool diameter and output to a separate file for each tool.

This increases g-code size and the time required to mill the boards due to (de)acceleration required on sharp bends.

Since all bends are 90 degrees the files produced matches the worst-case scenario for this type of work.

A “dumb” machine with no (de)acceleration management will work better than a professional machine in this case, unless the professional machine also has smoothing (there is a G-code for that) but even with smoothing enabled, a properly designed file will still cut faster.

This was what this project intended to address.

Development was stopped, for no reason other than lack of interest. The code was not complex and basically consisted of a pixel tracer, just like pcb2gcode followed by an arc and line detection routine, followed by a routine to calculate the optimum curve/line parameters to match the input data.

According to the sources I find trustworthy, there is no such thing as a 6580.

6581, 6582 and 8580 in chronological order.

Most references to 6580 seem to be in forums and blogs and I can’t find a picture of a chip that reads 6580. Mine are marked 8580.

It seems Heffo is entirely correct, and the wiki article uses the correct part numbers since the page was edited after his/her comment. Blog articles, even the ones that are direct copies from a wiki article, are and will not be corrected.