Wednesday, June 20, 2018

Creating a New Device in an Eagle Library--9mm Pot

(Advanced warning: If you don't use Eagle CAD for schematic capture/PCB/gerber creation, this post will mean zilch....You have been warned....)

 I bought some dual concentric pots from Small Bear and needed it in the PCB for a few projects.  I couldn't believe I couldn't find an existing Eagle library (Alps?  Bourns? Adafruit?  Anyone?) that already had this part--this is super simple, just an array of 100 mil traces with proper spacing and some kind of tName silkscreening that works….but I couldn't.

Time to roll my own....

To summarize the very basics: Eagle libraries provide us with "devices": electronic components represented in software we can use in our designs.

Right out of the box, Eagle CAD provides tons of devices: common passive components, resistors, caps, diodes, SMD parts, and so on.

But sometimes what you need for a design doesn't exist in any library you can find. So the purpose of this post is to help you (well, me, really) remember how to create these custom parts.

First some Eagle terms--they could have called all of these things anything, but this is what they chose to call them:
  • Library: a set of devices.  In Eagle on Windows they are .lbr files.
  • Device: the entire component--the IC, header, switch, whatever; a joining of a Footprint aka Package and Symbol 
  • Package: the representation of the component that goes on your PCB. Pads/drills etc. must be right or your part won't lay onto the PCB correctly after you fab. Just to make this confusing, I have also frequently seen this called a "footprint".
  • Symbol: the representation of the component as it will be shown on your schematic.
  • 3D package: 3D graphics that represent your device So you can make sure your part fit in your stompbox or whatever.  I am not going to talk about 3D packages at all here.
There are already many web resources about creating and editing Eagle libraries and devices; I won't go into it all of it here. Here is a good webpage link; here is a good vid.  Another good blog entry (although based on older versions of Eagle is here. If you need to create or edit devices, start there.

But I figure it might be worthwhile to mention what to me is unclear, and what I got stuck on; the things I seemed to be able to do (and not); maybe it will help you, or maybe it will help me in 4 months when I forget all of this.

OK let's start with the basics: editing any damn thing at all.....

Why can't I edit a @$%^ library?  And I do mean @$%(#@$

The libraries that come with Eagle are "read only". You knew that right? (I didn't).  It's in the docs right?  Kinda, but not right off the top.  Okay....

Assuming you're modifying the library content that came with Eagle--it's often easier to modify something vs. starting from scratch--you have to make a copy of the source .lbr file or the device you want to modify and copy it somewhere else first.  Only then can you edit the library or new device.

It's described here and here--yes, you have to do all this. 

Note: I got somewhat confused when I read that you "import" Eagle libraries--OK, but how?  Where is the import button?  There isn't one. What web tutorials really mean is just copy the damn library somewhere else--then you can edit it.

OK fine, but, Where are the %#@&$^ libraries that come with Eagle?

For windows 10 they are here:

C:\Users\[username]\AppData\Roaming\Eagle\lbr. You may have to enable hidden files and folders in Windows to see this at all. Search for the library you want in there and create the copy somewhere else. Now you can edit the latter.

You knew that right?

For other OS's?  No idea. I am pretty good with Linux and Mac but have never gotten round to using Eagle in either. I assume they are in /users somewhere. Beyond that? Sorry.

OK that's copying the entire library to somewhere then editing it.

There are lots of things you can do surrounding libraries:

  • You can duplicate an existing device, symbol, or package, then edit it to change it.
  • You can create alternate packages for a single device (so you can, for instance, choose between a SMD version of an IC or a DIP version)
  • You can add new devices to an existing library.
  • You can copy a device from an existing library to a new one you create.
  • You can create managed libraries that allow other users to edit whatever devices you are using.
  • Lots more things....
The most common thing I find myself doing is to edit an existing library to change a device, footprint, and/or symbol. That's what I will cover here.

OK, first, you open libraries in Eagle same as you'd open anything else--from the "Eagle Control panel"--the small window you see when you first open the program--File > open > Library

Choose the Library you want to edit. Can't edit?  See above--you can't edit the default Eagle libraries that live in their default locations, so copy the library or device somewhere else, but by now you already know that.

For v. 9.5.1 and earlier (hopefully later as well, but Eagle has been known to move around the furniture a lot) you see a screen with 4 sections: Device, footprint, 3D package, and symbol:

First thing I always do is duplicate whatever I want to work on.

So right click on the device and left click on "Duplicate". Call the new device something unique, say


You can duplicate a symbol (using the add symbol icon from the left column or the command below), in the same manner, same thing with a footprint: Right click > Duplicate.

Then right click on the new item and left click on EDIT.

Good news: editing footprints and symbols is the same as editing schematics and boards--it's almost all the same tools. So if you know how to edit those, you are a long way to creating custom parts already.

And--of course--make sure to always save your work after editing.  A library is saved the same as any other object in Eagle. If you forget to save, well, you might feel stupid.

DEVICE MANIA: Devices editing--again that's where you join a package and symbol and how everything connects--is done using a UI you've not seen elsewhere in Eagle; it's its own strange thing.

The FOOTPRINT or PACKAGE is in the top left, it's this thingy:

 The SYMBOL is to the right of it that, looks like this:

The device edit UI is a bit painful, but i always get stuck on the same thing: I have edited a devices and a footprint, and then connected things up with the CONNECT button, but once it's time to use it, the new device doesn't recognize a given new footprint.

When I go to test out the new device, my new footprint doesn't show up, it's only the original one.

How do I make the device recognize the new footprint?

here's how:

  • Click on group, left click and lasso the FOOTPRINT you want to get rid of, click on DELETE (garbage can icon) then delete the group.  Poof!  The old footprint is gone!
  • Now go to Edit > add and  Add the new footprint  When you edit > add in this context the UI shows you any footprints you have for the device including new/duplicated ones. You knew that too, right?
  • Another way to do the same thing: in the new device, click on the "NEW" pull down in the lower right.  Select "ADD LOCAL PACKAGE" from the drop down and create a new "package variant" for your new footprint.   

ANOTHER GOTCHA: Where is "ground zero" for your symbol or footprint? If you look at the editor for these, on the blank canvas, you will find a plus sign.  Move your creation so it's close by the + symbol.  That's where you grab your part to move it around. Took me a bit to figure that one out!

OK once all of that is sorted, you need to make sure things are CONNECTED correctly.  Click the CONNECT button in the device UI:

The process of connecting symbols to footprints is pretty straightforward although obviously you can make mistakes. So always test your component before using it in production--for instance, for a resistor array create a new Schem and board, wire it up, and see if it makes sense.


When editing a device, you can also use command line commands for this:

Create your new device and then issue this command:

ADD [packagename] and the package pops into the device, ready to connect.


ADD [symbolname]

CONNECT and then make sure you connections look OK.

After having used Eagle for a few years I have learned the hard way: NEVER TRUST A NEW DEVICE. Or maybe even an old one. Especially ones you download from some unknown source.

Update: to remind myself of this, I just got a PCB back with a  stock 74HC595 from the Eagle 74xx library. Shift register--really common CMOS part right? Sorry the device for the 74HC595 was butt--pins labeled wrong. Kiss that PCB goodbye.

I have seen devices and LBRs I have downloaded that have all sorts of stupid mistakes: unwired pins, footprints that don't match the part at all, footprints that don't have enough pins, symbols that are upside down, etc.

I usually print out the PCB 1:1 before sending off to fab and make sure any new device looks reasonable, the drills are big enough, the name is showing correctly, and so on.

One more trick: to use a new library, you can click on Library > use but it won't stick. You have to close and reopen Eagle sometimes to see your new parts.


….with all of the blah blah ginger blah blah in hand it's time to do a Proof of concept board.

Again I am created a new device for a dual 9mm concentric pot. I followed all the instructions above,
I did a quick layout for 3 concentric pots spaced 850 mils apart. I watched the vids I mentioned, reread my own notes, and poof--new device.

You can find the files for this  PCB on my website. I've now used this pot on a few PCBs, the result--yep it worked.

Now what?

You can get the clone pot library from my GITHUB page.  As always if you find mistakes, have problems, etc. please let me know and I'll fix it.

OK that's it for today. Comment below if you need an Eagle device I use in a design but you can't find, I should be able to help you out.  Maybe you have some cool ones or a nice LBR file you want to share.

And (literally) above all: if an Eagle flies over, don't look up, because them turds are big ones.

Have fun!

No comments:

Post a Comment

Minimalist Atmel 328 Development Board--How to Build One

Hello again:  if you've been following the last few posts you see that I am trying to use Arduino's IDE a lot less, and learning to ...