[sdiy] Eagle footprints
rsdio at audiobanshee.com
rsdio at audiobanshee.com
Sun Nov 22 00:55:44 CET 2015
That's a great suggestion, John. I use revision control for my Eagle library, and make comments about each checking, but it's difficult to look at a part and know it's history. Also, some of my custom parts have not been used yet, so presence in my private library is no guarantee that it's been vetted.
With status in the description, it's possible to note which projects have used a part. I just needed to change to larger SMD pads for a diode, and couldn't remember where it had been used.
Of course, there's no way I'll have time to list every project that a given part has been used, but at least the first success can be noted as a reference.
Fortunately, Eagle will not change the footprint in an existing layout if you change it in the library. The update only occurs when you specifically ask for it. Unfortunately, if you put all parts in the same library, then updating one will update them all. Tools like Cadence Allegro allow the update on a part-by-part basis, but the rest of their system is not as easy to use as Eagle.
On Nov 21, 2015, at 1:12 PM, john slee <indigoid at oldcorollas.org> wrote:
> Why not note the validation status in the Eagle part itself, whether in the description, attributes, or whatever. This would be particularly appropriate if you keep all your libraries etc in some sort of revision control system a la git[hub]
> On 21 November 2015 at 11:04, Tim Ressel <timr at circuitabbey.com> wrote:
>> Yeah, same here. I also do things like widen the SMT pads on some parts to make it easier to hand solder.
>> I like the bit about having a spreadsheet of known good library parts. I believe Sparkfun does this.
>> On 11/20/2015 3:12 PM, Richie Burnett wrote:
>>> Thanks everyone for the suggestions. I've kind of ended up building my own libraries on a per project basis now anyway, so I'll just mod the footprints to put a silkscreen dot nearby to mark pin one of the SOIC devices.
>>> As Neil and Brian have said, if your previous board comes back perfect from fab/assembly, then all of those footprints are then "approved". I like that way of working, even though I still check all my artworks in obsessive detail first using GC-prevue, and laser-print life-size paper boards!
>>> -----Original Message----- From: Neil Johnson
>>> Hi Richie,
>>> This is one of the reasons why I never use the libraries provided with CAD tools. The quality is just so varied, rarely consistent, and full of unknown bugs. At least if I fab a board with a mistake in a component I have created I have only myself to blame! And quite honestly by the time I've thoroughly checked a vendor library for correctness I might as well have made it myself.
>>> I separately maintain a catalogue of custom part numbers in a spreadsheet (one sheet for each component type), and when I have fabbed a board with a new footprint and tested it I then mark that entry in bold so I know it works.
More information about the Synth-diy