There are DIP ICs in socket 3D models here:
http://smisioto.no-ip.org/elettronica/kicad/kicad-en.htm
Search for “PTH ICs” on the page
The most likely DIP-8 socket that one would expect a newcomer to know.
I actually used Google to translate “package” in several languages. It certainly could be possible that “package” means “housing” in some language, but certainly NOT most of them. I tried French, German, Latin, Chinese, and several others for fun; Google is pretty amazing in being able to “speak” these languages.
So, which country is the term “Housing” used instead of “Package”; now you have me curious.
Yes, but I was under the impression that re-fining the libraries was to be timed to sync with the next version of KiCad. If I was wrong about this, thanks for the clarification.
Your post seems a little combative. I hold no ill will towards anyone regarding this topic. In the past I held a class at a maker space and showed the members an intro demo of KiCad. As with the posters in this thread, the small quirks in the library wording were not intuitive to them; as well as to me. My single point was that small changes could be more intuitive to a larger set of groups of people; nothing more.
I even pointed out that KiCad DID/DOES use the term “package” and choosing to use only ONE would go a long ways to reducing the confusion. I don’t really care which one gets picked, but pick one, and it will likely make it more intuitive for every user.
This is starting to become sorta funny on my end. From my point of view, this is a DISCUSSION forum. A place to discuss topics related to KiCad.
This is at least the second time where I have made comments about my initial ideas on how to make better experience ends up with being told to “Do it yourself”.
It is like as if I went into a steak house and posted a review of my opinion of the experience. The result was then being told by the restaurant to go into the kitchen to cook it myself.
In my opinion KiCad is a fantastic EDA tool. That is why I recommended it to everyone at the Maker Space. That doesn’t mean that it is “intuitive” for most beginners.
I did not have to spend my time to try out “Test Nightlies” that broke my install. I did not have to spend my time to try to help KiCad users by creating a detailed post here on how to successfully create a NPTH. At some point in the future I may have the spare time to “Do it yourself” for some of these things. That time is not now.
It’s more a thing of ‘be the change you want to see (in the world)’.
Most of the people posting and helping here know their way around KiCAD, but are not so deeply involved that they are coding for/on KiCAD due to whatever reasons - alone posting help here is a lot already. So telling ‘them’ what you want or think should be done is rather pointless, as they’re definitely the wrong audience.
If you really want your voice be heard take it up with the developers on the bugtracker, but those dudes 
have even some thicker skin than us and no qualms showing that to anyone proposing something.
The only way to succeed there is either convincing them of your proposal (very faint chance) or doing it yourself, which again, is what we have been telling you all along.
Sorry.
4 Likes
This is another one of those examples where people frame KiCad as a commercial product, when it is not, so that example is invalid in all respects.
I can’t think of an exact analogy. But it is more like going to a charity soup kitchen who give out free soup, and asking them to cook a special soup for you because you don’t like the ones the are giving out.
Or perhaps, there is a volunteer project, where people are building swings for kids. You tell them that you won’t be helping, but they should also build a climbing frame.
Or you hang Christmas decorations outside your house, and your neighbour (who doesn’t bother with any decorations), says “that’s great, can you do that at Easter as well please? I won’t help at all, because I have other things to do”.
The point is, people who create KiCad are volunteers. Their motivations are completely different than to increase “sales”. In particular, when it comes to asking other people to essentially work for you for free, that needs to be approached with care. In the context of an Open Source project, which is essentially a community volunteer project, it is actually not an unreasonable thing to say “if you think that is such a great idea, then do it”.
Commenting on technical aspects is ok to a point, but no one wants to be the guy who always seems to be asking for more free stuff but never contributes to the voluntary effort.
4 Likes
Well the forum is a good place to start a discussion. (Maybe not the place where the developers or library maintainers will “hear” you.)
Of course there are problems in kicad but i don’t think library names are the most pressing issue.
Over the last few month the “kicad library convention” (KLC) got a major overhaul inspired by a topic on this forum requesting a more IPC compatible footprint library. We are currently already thinking about the next version of the KLC.
So if you want to help make the library better:
Have a look at the current KLC and the associated FAQ.
If you understand both of them, chime in to the discussion for KLC 2.1 and make your voice heard. But please keep it civil in there and remember that nothing will change over night.
You might find that a lot of stuff can be done better. But some stuff has a higher priority than other things. (Currently the main priority has been to better describe the KLC to beginners and to get it nearer to being ipc compliant.)
1 Like
Back when PCBs were taped out on lightboxes by chain smoking contractors, I never heard “decal” but did hear the word “transfer”. Decal is an US English term and this language split is part of the problem here
We had this before - in Germany for example the package is called ‘Gehaeuse’ and not ‘Verpackung’.
‘Gehaeuse’ translates loosely to housing, as the term ‘Ge-Haeuse’ contains ‘Haus’ which means house.
‘Verpackung’ usually refers to removable - non essential (protection, marketting, etc.) - parts of a thing when you get it.
‘Gehaeuse’ is part of the thing - so it can be used at all - to keep components together or assembled.
I’m pretty sure it’s similar in French, where the original Author(s) of KiCAD reside(s) afaik.
I think the US would understand it like this:
shell = Gehaeuse
wrapping = Verpackung
1 Like
Anyway, changing the names causes havoc working on old projects. New KiCad users must understand that many people have many months of effort invested in projects using the current naming
I think it could be done with a major kicad release. Especially if the kicad release changes the file types anyway. Which means it could be something we might want to keep in mind for the v6 release.
Another option would be to do the same as we currently do with the THT vs ThroughHole renames. Keep the old repo but declare it legacy.
Which can also trip you if two libraries contain the same name
1 Like
not if the new system (.sweet) is being implemented - then the library ‘name’ becomes part of the symbol/component identification and is not a problem anymore (same way you can have the same named footprints in different footprint directories today and experience no problems).
That really means that there should be some serious thought and debate going into these .sweet naming, in an attempt to get it right first time. Meanwhile the legacy libraries, do as little name changing as possible.
The only ones that deserve a new name are KLC compliant, multi unit alternatives to the 74xx and cmos4000.
Ok, please for a dummy like me, could anybody tell me, what I have to do in the KiCAD - Component - Selection, to get a DIP-socket for the schema? What search-term do I have to enter?
You might have a bit of a misunderstanding here. You ask for a dip socket which is a footprint but you write about component selection which (if you use stable v4.0.x [1]) only allows to add symbols to the schematic.
So normally you add a symbol for your specific IC. Lets say an NE555. Then you assign the correct dip socket to it.
Short version:
a symbol represents the function of your component (your ic)
the footprint represents the landing pattern of the physical devise.
More details in this old post of mine (it is a link so you can read the full post):
[1]
If you use nightly (or if you read this later and use v5) then the component chooser also allows to set the footprint field on addition. There the same rules apply as in cvpcb. The footprints shown are filtered via the symbols footprint filter fields.
1 Like
Ok, thank you for your answer.
What I really want to do, is the following: I want to put a 74AHCT125 DIP-14 into a DIP-16-socket.
So I thought it could be possible, to have a DIP-16-socket in the schema and asign it a dip-16-socket footprint and in the real world I put my dip-14 74AHCT125 into the socket.
Is there a better kicad-way to do this?
I use Version 4.0.7 in ubuntu …
Why would you put a 14 pin part into a 16 pin socket?
If you really think this is a good idea, open the footprint for dip 14 in the footprint editor and add two additional pins (without pad number) on the bottom to it. Save this new footprint to a project specific footprint library and assign it to your symbol.
Do not use the dip 16 footprint because the pin numbers of it will not align with the pin numbers used in the 74ahct125 dip 14!
1 Like
…
??
@Rene_Poschl: Because I already have the parts and do not want to buy new ones.
Thank you for your description, I will try it out