X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sun, 23 Dec 2012 18:43:07 +0100 From: Leonardo Guardati To: geda-user AT delorie DOT com Subject: Re: [geda-user] PCB: gcode export: missing drill file Message-ID: <20121223174307.GD2518@guardati.it> References: <20121223154752 DOT GC2518 AT guardati DOT it> <50D72EAE DOT 6010307 AT estechnical DOT co DOT uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50D72EAE.6010307@estechnical.co.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, Dec 23, 2012 at 04:17:50PM +0000, Ed Simmons wrote: > On 23/12/12 15:47, Leonardo Guardati wrote: > >Hi to all, > > > > I've got a problem exporting gcode drill file from PCB. > > > >Here the situation. > > > >I'm new to gEDA, but I managed to capture a schematic using > >gschem, then passing it to PCB for layout. > >I exported the gcode of the board and used it with EMC2 to > >mill the actual board. > > > >Now I need to drill the holes for through-hole elements. > > > >I'm using PCB 20110918. > > > >When I export gcode, PCB generate 4 files: > > name.gcode.group1.cnc (and .png) > > name.gcode.top.cnc (and .png) > > > >The *.gcode.top.cnc file has got the tracks. > >The *.gcode.group1.cnc has got the pins. > > > >Reading PCB Manual for 20110918 ( section 3.9.2 about gcode > >export) it says: > >"A drill file is also generated, and it contains all drills > > regardless of the hole size; the drilling sequence is > > optimized in order to require the least amount of movement." > > > >[I've checked the previous and the next manual versions, and > >they don't have this section.] > > > >I suppose the *.gcode.group1.cnc file is the drill file. > > > >_Here is the problem_. > > > >There is no drill info, just the drawing of the pins on the > >board surface. > > > >I would expect to see on emc2 a path going 2mm (for example) > >below the plane containing the other tracks. > > > >Am I missing something? Is this a missing compile-time option? > > > > > >Leonardo. > > Hi Leonardo, > > Have you opened the generated drill file in a text editor? > > It ought to have a drill depth variable in there for you to adjust > in the header. Also, I found recently that if you don't have > something drawn (eg a trace or rectangle of copper) on both top and > bottom layers, sometimes no drill file is output. That was the problem! :D I drawn a little rectangle on the bottom layer and now 2 additional file (.cnc) are generated: somename.gcode.bottom.cnc (and .png) somename.gcode.drill.cnc I saw the parameter about the depth; is named #101 (drill depth) I've checked the drill file on emc2 and it looked like I expected. > > The .cnc files are not the drill files, IIRC the drill file is > called somename.drill.gcode. > Here with PCB 20110918 the name is: somename.gcode.drill.cnc > I hope that helps - I'm glad to see someone's getting on with > something productive despite the festive season ;) > Yes you saved me a lot of time! Thank you. I think a little note could be added to the manual page to help others understand why the drill file is not created. http://pcb.geda-project.org/pcb-20110918/pcb.html#gcode *** pcb.html 2012-12-23 18:34:41.121253206 +0100 --- pcb-mod.html 2012-12-23 18:38:05.997691892 +0100 *************** *** 2045,2054 **** --- 2045,2056 ----

A drill file is also generated, and it contains all drills regardless of the hole size; the drilling sequence is optimized in order to require the least amount of movement. +

Note: The drill file is generated only if the bottom layer is not empty. +

The export function generates an intermediate raster image before extracting the contour of copper elements, and this image is saved as well (in .png format) for inspection.

When the spacing between two elements is less than the tool diameter they will merge and no isolation will be cut between them; the control image should be checked for I don't know if this apply to newer versions too. > Best, > Ed > Thank you. Leonardo.