From: Patrick B. <pbi...@us...> - 2011-11-20 16:54:26
|
On Wed, 16 Nov 2011 21:56:40 +0100 Filip Dominec <fil...@gm...> wrote: Hi Filip, good to hear it works for you. My machine has play-free guides and actuators, so repeatability is not an issue for me (even with 0.5mm pitch TQFP ICs). I've been thinking about the optimisation you propose, but I don't see any work on it from my side happen anytime soon (not this year), I'd rather improve --extra-passes. Internally, pcb2gcode represents toolpaths as huge lists of coordinates (icoords; coordinate list using inches), and for each layer a list of toolpaths is created. That list is passed down from the "Surface" class that does the image processing to "Layer", "Board" and then an "Exporter". I think Layer::get_toolpaths() could be a good starting point here. Might even be not that much effort. If you get something to work, I'm always happy to accept patches ;-) -- Patrick > Hi, I have succesfully tested pcb2gcode on my home-build PCB milling > robot and it works great, except for one issue. I use the Voronoi > feature and I need that no path is milled twice. > > Not only the double-pass of almost all traces doubles the manufacture > time, but also the second pass sometimes wipes off the subtle > connections for SOIC circuits due to little imprecision of my machine. > > What should I do to help fix this? Is some work underway or should I > download the sources and begin experimenting with the code? > Filip Dominec > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Pcb2gcode-devel mailing list > Pcb...@li... > https://lists.sourceforge.net/lists/listinfo/pcb2gcode-devel |