Martin, I appreciate the offer, unfortunately the script cannot solve a key= problem: referencing the BOM lines, back to the assembly drawing/PCB. Sent from my phone On May 7, 2014, at 4:05, Martin K wrote: >=20 > On 5/6/2014 6:00 PM, Vitaliy Maksimov wrote: >> Hi List, >>=20 >> We use an automatic BOM generator (which we put in place, following Olin= 's >> suggestion and relying heavily on his conventions), that pulls the >> names/part numbers out of an EAGLE schematic. >>=20 >> It works great, except when we place modules on a motherboard. We don't >> want the BOM to specify the modules. We want it to specify headers (e.g.= , >> two BOM lines specifying 5x1 headers and referring to CN1 and CN2 on the >> assembly drawing). >>=20 >> So far, the only solution we came up with, is to place a "phantom" >> (pin-less) module that only has the silkscreen, plus the two connectors = on >> either side. Obviously, it is hacky and error-prone. >>=20 >> Vitaliy >=20 > Vitaliy, > In the last year or two I wrote a script that takes the BOM from Olin's=20 > ULP and formats it how I want it and writes to an excel spreadsheet. > I added a couple features for myself, the one I like most is that it=20 > adds part numbers for generic resistors so that I don't have to search=20 > for them when making purchasing BOMs. It would be quite simple to make=20 > it recognize modules as another special class of device that get parsed=20 > differently, assuming all of the information is present in the CSV-BOM. >=20 > The script I wrote is in Perl and it's not intended for public=20 > consumption but I could share it with you. It's not good code but you=20 > get what you pay for. >=20 > - > Martin > --=20 > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .