Hello everyone, is n4148 not part of the standard Kicad library? I have used the generic diode part for my schematic. And now I am assigning foot prints for my parts. I just can’t find n4148. I’d assume it would be in the standard library. Perhaps it’s not as popular as I thought.
Thanks for response. I am looking for the footprint of 1N4148. I used the no-name generic diode for my schematic.
My question really was is 1N4148 included in the footprint library? I wasn’t able to find it. Thank you!
Yep, I get that. But what kind of part is it? Through hole? Surface mount? There is no such thing as “a footprint for 1N4148” because like in that link I showed, there are tons of types of footprints for parts named 1N4148. These are generic footprints names that apply to a lot of components. If you’re coming from the EAGLE world, this point can be a little confusing because everything is tied together (1N4148 would be a combined footprint/symbol).
Do you have a picture of the 1N4148 you’re trying to use? Or a project you’re using as a reference point for your project? Or maybe even the application this 1N4148 will go into? (i.e. a diode bridge for power rectification)
So what you need to find for the part you’re using is the package you’re using, then that package in KiCad is what you use. It’s unlikely you’ll have a footprint that’s exactly called 1N4148 The value of that part can then be changed on the board to reflect 1N4148,
I have used Eagle here and there just to check the schematics. So I am not a power user at all. That said, I don’t think I have to pick the footprint for my parts in Eagle. I pick whatever the library I use, and I stick with that library from schematics to PCB design. In other words, I pick the part (which I think have the footprint already associated with it) when I work on the schematic. In Kicad, how it is done is I pick the part and later choose the correct footprint.
It all makes sense now. And I was quite literally playing with Kicad between my meals. Hence the self-inflicted confusion.
Why coupling is a bad idea. In the coupled library way, you have to use the full part number, maybe including some text description, as the same part number from TI and NXP may be a completely different package.
This is where you might want a private to the project library, with one project using DO-35 and another SC-70
One manufacturer calls a part xyz and the other does chose the very same name… KiCAD will get confused and always give you the part in the library that is listed first in the kicad.pro file.
As long as you’re aware of that, cool.
@davidsrsb: @Andy_P is referring to ‘internal house part numbers’ as ‘fully qualified part numbers’… he’s not using manufacturer part numbers to identify parts in the libraries.
I do the same.
The difference between me and Andy is that he doesn’t carry the manufacturer number in an extra field in KiCAD, but instead runs external scripts with lists that create him a BOM (they have the link between internal part number and manufacturer part number), where as I use @devbisme’s KiCost, so I got a ‘manf’ and ‘manf#’ field in KiCAD.
Andy’s solution is more flexible (for groups), where as mine is good enough for a 1-man show