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)
Thank you! Much appreciated! And thanks for your entire library, very nice of you to share.
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?
Ratsnest: Nothing to do!
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.
I double checked. Unfortunately there is no better way. The part I’m using is already done the ‘optimal’ way for an Eagle part. I think everybody else is already using the above pictured part or a similar one.
As we can see above, the GND “pin” on the schematic connects to both GND2 and GND3 “pads” on the footprint. This is the intended, ‘correct’ part construction you’ll find if you Google around. It does generate an airwire between the two pads on your Board view. This may be ignored, dismissed, approved, or whatever.
‘My way’ is official way. I don’t know what makes you think that you’ll never need to use Pin2, but that way of thinking does limit your layout options when a trace gets routed under the 7135. Clearly the footprint I pictured above allows GND to come in from either side of the 7135. When you remove the “connection” to Pin2 you limit yourself to bringing in GND from only one side! This applies whether you do it manually with a trace or attempt to connect it with a pour.
I think you’ve got blinders on as far as my drivers. 
Only one of my drivers needs specific 7135’s populated: A22-7135. That is certainly not what I’m encouraging you to do. It was a hack in order to get the features I wanted into the space allotted - the hack works well (why wouldn’t it?) but it has little to do with my recommendation for you to stick with the correct connections w/in your Eagle part.
I’d recommend you just ignore the airwires.
I hear you but I cant, too OCD…
Lol
Then it just comes down to “whatever works”. I’ve violated design rules, pushed minimum spacing, clearances, modified parts to cram a design onto boards that are too small. Not good to let it become a habit but its just personal boards. We not even suppose to route traces under 7135s.
Uh oh, better watch out, I said that same exact thing once and got schooled up and down!
Though if you get boards from cheap chinese fabs I would inspect the soldermask on traces that run under 7135s or other exposed pads. Oshpark spoils us.
Comes from the different mindset of doing production boards. Violate design rules there and it can really cost you.
Hmm. Let’s try not to get too sanctimonious here.
“Can” is the operative word in Halo…’s statement. Engineering hacks are sprinkled through consumer goods as necessary. High powered flashlights certainly require more of that sort of thing than most.
The design requirements for the Nanjg-105c, for example, force the use of traces under that GND tab.
Could you edit the part and give it and additional pin? Make it a four pin component, having the middle leg as the fourth pin? Then just avoid connect it to anything in the schematics and it should be ok. It could make your schematic look a little ugly with an additional unused pin on the 7135s but it should work.
Note that I haven’t tried this… just brainstorming.
That would definitely work, (as Alex and Halo have pointed out it still wouldnt be technically correct) but make both a TAB and a GND on the symbol, then you could GND them both in the .sch when you initially lay it out and once the board’s finished if you find those remaining air wires you could go back and remove the needed GND from whichever of the 2 pins was giving you that issue from the .sch.
Anybody have an Omten 1217 library to share with me?
It’s not by any means official but I’m trying to figure out how to up load it. I’m digitally challenged so the obvious isn’t. In the end it might take you less time to make your own but his evening is dedicated to omten.
I didn’t totally understand the tutorial on creating my own, and I couldn’t find a data sheet for the 1217.
You can also just take measurements of a switch. Mtn lists the body as 12.40mm x 16.80mm and I believe the tabs are 5mm wide.
Thanks, that’s helpful. I’m still waiting for fasttech to deliver mine or else I’d measure myself.
I just wish I could install Eagle at work so i could do this when I’m bored…. 
Anyone have a library part for the mmu size 13A and the LFPAK 33?