Hi Rick, I will contribute an honest two cents worth.
I think you understand your problem very well. The simple solution is to arrange for your CAD software to output appropriately formatted files. Since you have no control over that then you have no choice but to use a text editor to format them yourself. If you are a programmer you could write a conversion program, of course. The way the industry copes with this stuff is... to use a text editor. It is a bit fiddly and has the potential for making errors but it is very easy. There are many Excellon commands but only very few of them are needed. If you have any questions I can answer all but the most tediously arcane. What do you want to do with the rout file? It will most likely be useless to the manufacturer. If there is any information in it that they need they will probably put your job on hold while you supply the information in their preferred way. Steve. On 03/03/2012, at 7:22 AM, rickman wrote: > Hi Julian, > > Thanks for the help. I am attaching the drill file here. The issue seems to > be that in spite of the fact that there are Execellon commands to specify the > drill sizes some software puts them in comments in a header or I've even seen > web pages saying the tool descriptions should be in a separate file! So I > expect the problem really is the source software that created this file which > I have no control over. I was thinking that whatever the fix is, I would > need to do the same with the software I use, FreePCB. But FreePCB adds the > appropriate commands... mostly. FreePCB adds a decimal spec to the INCH > command that throws an error message, but seems to work anyway. Attached is > the drill file that started this thread. > > On a similar note when I dug for specs on routing files I came up empty > handed. It seems they are much less standardized although Excellon covers > that in the drill codes if you stick with that. The routing file that came > with the board info doesn't import well either. Just for grins I'm attaching > that as well. At least it is short. How does the industry ever cope with > this stuff? > > Regards, > > Rick > > > > On 3/2/2012 3:08 PM, Julian Lamb wrote: >> Hi Rick, >> I can try to help you out. I don't see the problem file anywhere in this >> reply chain...can you send me your question and attach the problem file? >> >> Cheers-- >> Julian >> >> On 03/02/2012 01:50 PM, rickman wrote: >>> I've tried to subscribe to the gerb-devel list but it seems to be >>> waiting for moderator approval. We'll see if this message makes it to >>> the lists. >>> >>> Rick >>> >>> >>> On 3/2/2012 11:54 AM, Stuart Brorson wrote: >>>> I am forwarding this e-mail to the gerbv-devel list, which is the best >>>> place to find the gerbv developers. >>>> >>>> Alternately, if you get no traction from the gerbv-devel list, you can >>>> file a bug report at the sourceforge site: >>>> >>>> http://sourceforge.net/tracker/?group_id=33921&atid=409538 >>>> >>>> Stuart >>>> >>>> >>>> ---------- Forwarded message ---------- >>>> Date: Fri, 2 Mar 2012 07:45:27 -0500 >>>> From: Matthew Sager<matthewsa...@gmail.com> >>>> Reply-To: geda-h...@delorie.com >>>> To: geda-h...@delorie.com >>>> Subject: Re: [geda-help] GerbV Support >>>> >>>>> So is there any chance of getting some feedback on my issue with the tool? >>>>> Is this the right place to ask? I used to post on geda-user but that >>>>> list >>>>> seems to have been deprecated in favor of this one for support and the >>>>> developers have their own list now. >>>>> >>>>> Rick >>>>> >>>> Hello Rick, >>>> >>>> It looks like the Gerbv does not understand the tool definitions at the top >>>> of your file. >>>> >>>> Here is an example of how the tool definitions usually look. >>>> >>>> M48 >>>> INCH >>>> T29C0.040 #this is for a 40 MIL hole >>>> T28C0.035 #this is for a 35 MIL hole >>>> % >>>> T28 >>>> X012900Y009100 >>>> X010700Y010000 >>>> X010700Y011000 >>>> X020500Y009500 >>>> X020500Y010900 >>>> X012900Y014100 >>>> T29 >>>> X008196Y009433 >>>> X007196Y008933 >>>> X008196Y005033 >>>> M30 >>>> >>>> If you manually edit the header of the file to something like this it will >>>> probably work. I do not remember right now what G90 is for. Also, You >>>> might want to split the non-plated holes to another file. >>>> >>>> M48 >>>> INCH >>>> T01C0.008 >>>> T02C0.012 >>>> T03C0.038 >>>> etc.... >>>> % >>>> G90 >>>> T01 >>>> X00291000Y00105000 >>>> X00282000Y00097000 >>>> ... >>>> >>>> Matthew >>>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Virtualization& Cloud Management Using Capacity Planning >>> Cloud computing makes use of virtualization - but cloud computing >>> also focuses on allowing computing to be delivered as a service. >>> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >>> _______________________________________________ >>> Gerbv-devel mailing list >>> Gerbv-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/gerbv-devel >> > > <beaglebone_revC1_NCDRILL.drl><beaglebone_revC1_NCROUTE.rou>------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________ > Gerbv-devel mailing list > Gerbv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gerbv-devel ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Gerbv-devel mailing list Gerbv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gerbv-devel
