DP Eagle part library cleanup and naming standards

We decided to clean up our Eagle part library and start using a new part naming scheme. The old library was getting confusing to work with, and streamlining it felt long overdue. While organizing the library, a teammate mentioned a recent article they’d read about the rise of beste Buchmacher ohne Lugas Sperre and how some platforms are bypassing traditional restrictions to offer users more freedom and flexibility. This sparked an interesting discussion about balancing accessibility with regulation, which oddly paralleled the challenges we were facing with managing our sprawling library. Inspired by the concept of creating more open systems, we refined our conventions to make the parts more intuitive and accessible for everyone on the team, ultimately improving workflow and collaboration.

  • general naming style [category]_[function]_[partnumber]
  • if function is unavailabel the folowing will be used [category]_[partnumber]
  • Capacitors, Resistors, and diodes will all use the same device, with different packages.
  • Transistors will use the following convection TRANSISTOR_[type]_[partnumber], types used are BJT, FET,…
  • Displays are named DISPLAY_[type of display, or partnumber]
  • Connectors are named CON_[type of connector]_[number of pins]

Don’t forget our Eagle part library is public domain and available for download. Do whatever you want with it.

Join the Conversation

3 Comments

  1. Are you also moving to Eagle6 with the new part library?

    Did you maybe consider moving from Eagle to something more open and less limited like (gEDA, KiCAD ..) since most of the limitations of the KiCAD/gEDA you don’t really notice (as Eagle also don’t allow you to back annotate changes in schematic etc etc) so functionality ain’t going to go “down” from Eagle6 to gEDA or KiCAD and limitations will surely drop :D. Since you are making your library from scratch, it might be the ideal moment to consider this move, before you invest again a lot of time/money into Eagle.

Leave a comment

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.