Author Topic: Good Componet Library Practices  (Read 1507 times)

0 Members and 1 Guest are viewing this topic.

Offline VK3DRB

  • Super Contributor
  • ***
  • Posts: 1606
  • Country: au
Good Componet Library Practices
« on: March 24, 2014, 11:28:25 am »
One of the big problems some companies have is  :bullshit: component libraries. That is, they are not maintained properly, have bugs, and they end up not being trusted. One company I worked for had several libraries by different teams because there was no trust and little cooperation between the teams... a BIG waste of money and time.

Here are some ideas that seem to work:

First of all, have PCB Design Standards for Guidelines within your company that everyone can work within.

A really good idea is to have TWO sets of libraries. As an example, the libraries would be named:

(1) Component Libraries - these are libraries of parts, also containing component footprints.
(2) Verified Component Libraries - this are libraries of verified correct parts, also containing footprints WHICH HAVE BEEN VERIFIED to be correct as evident on new boards. These verified parts are moved from Component Libraries into the Verified Component Libraries when a new board arrives.

Then you can use footprints from (2) with complete confidence - not double checking needed. Those new components in (1) might need to be double checked with their datasheet before being used.

I am interested to know other ideas people have in maintaining libraries. What standards do you use in maintaining libraries? Do you think a strict standards operating component libraries is a good or bad idea? Any war stories?

Offline peter.mitchell

  • Super Contributor
  • ***
  • Posts: 1568
  • Country: au
Re: Good Componet Library Practices
« Reply #1 on: March 24, 2014, 04:28:08 pm »
One thing i found very useful is keep the footprint name short and simple, but add as much as you can to the description text.
That way it all stays neat but you can identify what packages work with what footprints still.

Another thing, different manufacturers have different names for the same footprints, and there are footprints that can be used between a lot of different packages (eg, a universal power so-8 footprint that can do LFPAK,PG-TDSON-8,PowerFLAT,8-HVSON), using custom footprints that allow compatibility between multiple packages can help with design changes, part compatibility and minimize confusion.


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo