[sdiy] Eagle footprints

charlie wallace charlie at finitemonkeys.com
Mon Nov 23 03:04:13 CET 2015

i do a similar thing, i added a digikey/mouser/oem part number
attribute and then i use the bom-ex.ulp to manage them all.


there are couple of versions knocking about.

someone mentioned ultra librarian as well, there is a free version
that also exports scripts for eagle (And others) for specific oems.

eagle also has a bsdl ulp that can make parts.

On Sun, Nov 22, 2015 at 5:12 PM, Sarah Thompson <plodger at gmail.com> wrote:
> One thing I have recently started to do in EAGLE is to religiously add attributes to every library object that specify Digikey/Mouser/manufacturer part numbers. This makes it really easy to generate an accurate BOM directly from Eagle, the import it directly to the Digikey web site to create a kit for a prototype build. This means that BOMs update with design changes, and you can create derivative designs by cutting and pasting schematics between projects and still create a kittable BOM just as quickly. It takes more time to set up first time around, but saves a ton of time over multiple spins whilst also reducing mistakes.
> A second huge timesaver is the Octopart Excel add-in, which lets you create a BOM spreadsheet that can automatically check stock, availability and pricing. If you have to deal with a stupid procurement process that takes forever between approval and ordering, this can be a lifesaver by making it possible to check for out of stock situations really quickly across multiple suppliers just by reopening the spreadsheet.
> Sarah
>> On Nov 22, 2015, at 3:50 PM, rsdio at audiobanshee.com wrote:
>>> On Nov 21, 2015, at 11:14 PM, john slee <indigoid at oldcorollas.org> wrote:
>>>> On 22 November 2015 at 10:55, Brian Willoughby <brianw at audiobanshee.com> wrote:
>>>> I imagine that your command-line tool will useful as well for managing and coordinating many projects.
>>> I hope so. It's already helping me with a few things. Feedback/constructive abuse/etc welcome :-)
>> Unfortunately - at least in terms of interoperability - I'm still working with Eagle 5.11.0, and I'm a little reluctant to install the Ruby development environment even if I upgrade to Eagle 6.
>> Meanwhile, all of this talk has me wondering whether an Eagle ULP would be able to accomplish the same things you're doing without depending upon Ruby or the XML versions of Eagle.
>> I may just have to learn Eagle User Language Programming and see how far I can get with the ideas you've implemented in Ruby/XML. I hate to suggest that you switch languages after you've gotten a good start, but it might serve more Eagle users if you were to develop in their internal language (assuming it's capable).
>> Brian
>> _______________________________________________
>> Synth-diy mailing list
>> Synth-diy at synth-diy.org
>> http://synth-diy.org/mailman/listinfo/synth-diy
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy

More information about the Synth-diy mailing list