Here’s my file, its got lots of wire pad’s / via’s, its got spring pad’s (8mm, 8 but with only 5mm exposed, 5mm). There is another set of battery pad’s, this was when I needed to make a buck driver with one + and one - pad to make a cell connection. My version of 7135, my SOD-323 with slightly oversized (a little extra heigth) pad’s. some PIC parts, the parts needed for BU_CK and RGBW_Clicky and some other crap.
can someone download it and verify it opens for me please.
Other than mine my next most used library is supply.lbr in the E14 download’s, thats where I get my GND symbol and other crap (I use my own batt+ / Vin)
Edit:
Yes got it solved, I’m not sure why my .lbr wasnt visible in windows, I was looking in the exact directory that path told me to but my file was NOT in there, even on a whole hard drive search my file was nowhere to be found. I followed the instructions in that thread to copy and paste to the desktop and was able to get it to show up that way.
I downloaded your LBR file and glanced at it in Wordpad. Looks fine to me.
As to why it’s not showing up, it’s probably an attribute problem - hidden is the common culprit. You may paste this into your “Run” prompt in order to see if the file is listed, use ENTER or SPACE to page through the results:
cmd /K "dir /a C:\EAGLE-7.1.0\lbr\ | more"
or to check the attributes on that particular file, use this:
cmd /K "attrib C:\EAGLE-7.1.0\lbr\dan.lbr"
A normal file will show:
A C:\xxxxxxxxxxxxxxxxxxxxwhateverxxxx
Whereas a file with the hidden and system attributes would show:
I think that the contents of this LBR are based on a combination of things from the regular Eagle distribution and Robert Star’s LBR-EX parts library. robertstarr (Bob Starr) · GitHub
Hey Alex, do you have a preferred library part you use for the LFPAK FET’s? I have a few that are in different stock libraries but there are some differences between them, wondering what one exactly you’re using.
I haven’t actually made a new part yet (yeah, I know) so I’ve been using a stock Eagle part. That part is under:
Transistor Power -> N-MOSFET-SO8S
That’s a correct Power-SO8 footprint. Then I drop a little rectangle of stop on top of it to fix the large exposed pad used on modern 5x6 packages, as well as 3 little rectangles of paste. It should work by itself without those things if someone wanted it to.
Does anyone have an edited 7135 “footprint” for mounting them standing up? I’ve seen somewhere a board design with them standing. I don’t remember who did it. I guess I could make one myself, but would much prefer a tried and tested version.
I have one, only thing is the way I do my library, I do it as a single large library instead of a new .lbr for every part I make. I will break off that one part [threw hole mounted 7135) and post it on my Dropbox today, will post link when I have it up for you…
And in the name of sharing, here’s my entire library, this has all the part’s I’ve made as well as all the parts I often use but didnt make myself (I copy part’s into my library so I only have to look in this one place and so when I’m doing backup’s I only have to backup this one file). If you’ve downloaded my library before I suggest throwing that file away and replacing it with this, I am constantly adding part’s.
I think it would be good info to have in this thread-
How to copy part’s from a .sch or .brd, using 7.2 this is a very simple process no longer requiring a ULP.
Open the file (I always do this from the .sch but it should work from the .brd)
go to the file menu
go to export
the last option is library
Name it what you want, select the 2nd option (for convenience, any will work)
This is a question specifically for other folk’s who use GND plane’s, it has to deal with 7135’s…
Any of you that dont run GND routes, just let a solid GND plane take care of connecting everything, have you considered disconnecting pad 2 of the 7135 from GND? I am considering doing that now, just looking for feedback.
For an example let’s look at this driver, specifically the bottom of it. Notice how there must be a via at pin 2 of each of the bottom 7135’s? That’s because the GND plane is broken where the pin connects EVEN THO it does make connection at the tab. The only real reason those are required is to make the connections in eagle, if those arnt there I’ll get 5 air wire’s remaining during ratsnest (I pay close attention to my net list / ratsnest and make sure I have zero left. I also dont run ANY GND traces at all, I let my main GND poly do it). IRL there is no need to have the pin connected to anything since it is the same as the tab.
In bottom view it’s easy to see, the left most 7135 would be fine without that via, removing the rest would all cause air wire’s from pin2 to GND cause the LED- trace break’s the plane up. Again IRL we know that pin doesnt need to be connected but eagle doesnt.
If I disconnect pin 2 in my library part I would no longer need to have the vias. What do you think, is that ok to do or a bad idea?
Edit: went ahead and did it, now I have no vias and no air wire’s. Does anyone think it’s a bad idea to have the pin disconnected in the .lbr part for any reason?
It’s a bad idea. With the part as you’ve now modified it you are unable to use Pin2 without causing DRC errors. It’s possible to run a wire near (or over top of) Pin2, but of course you are unable to ‘connect’ to it and put it on the same net. So you’ll get overlap errors.
I’m not certain right this moment whether there’s a better way to put the part together so that this may be avoided.
There’s no reason for you not to ignore those airwires.
I understand what you’re saying but the way I work I dont run wires / traces / net’s to pin 2. I dont run ANY ground traces anywhere on my board at all thus I’ll never need to connect to pin2, once I hit f12 (ratsnest) it’s taken care of so I dont have a reason to need to connect anything to any ground pins of any components.
[Now I’m not calling your way wrong. I want to stress that cause we dont always get along but IMO there can be multiple correct way’s to go about it] but you know how on some of your drivers specific component will need to be populated cause ground to another component runs threw it? I never do that, again I dont run a single ground trace on my board because of how I use full GND planes (which is where this “issue” comes about, the 7135 is connected to the plane just fine but having that second pin screws things up and it see’s an open connection where IRL there isn’t.
I’m way to busy this weekend but when I get some free time to google / youtube some boring ass eagle video’s I’ll start looking into other ways to connect multiple pins of a part to the same connection, maybe you’re onto something there.
