EEVblog Electronics Community Forum
Electronics => PCB/EDA/CAD => KiCad => Topic started by: Greg J on August 14, 2022, 10:02:23 pm
-
I'm new to KiCAD, but trying to find LTC3113 and RT6154(A/B) . I searched the internet, can't find either.
For a moment snapEDA seemed like it will have the right files, but after downloading them - it's clear it doesn't. Whatever files I can download under these chips from SnapEDA - are not the right items in library.
Maybe I should try using something else than KiCAD, library issues seem a massive slowdown for me atm.
-
I'm new to KiCAD, but trying to find LTC3113 and RT6154(A/B) . I searched the internet, can't find either.
For a moment snapEDA seemed like it will have the right files, but after downloading them - it's clear it doesn't. Whatever files I can download under these chips from SnapEDA - are not the right items in library.
Maybe I should try using something else than KiCAD, library issues seem a massive slowdown for me atm.
Surely you can spend a few minutes and make the symbols you need? It's really not very hard at all.
I didn't look to see what footprints those parts use, but it's likely they're already in the KiCad library.
-
I find parts on digikey that link to either SnapEDA or UltraLibrarian and add them to my own library. I've long since deleted the default libraries.
-
I have looked in the app itself, and I tried SnapEDA. This isn't my first rodeo.
When I found SnapEDA part - https://www.snapeda.com/parts/RT6154AGQW/Richtek+USA+Inc./view-part/ (https://www.snapeda.com/parts/RT6154AGQW/Richtek+USA+Inc./view-part/) - and add it to KiCAD - it does not appear to contain that part. The files you download from that site don't even contain the RT6154 part number.
Dear @Bassman59, I don't know what your experience is - but yes, I've spent some time looking at things - hence why I'm asking here, because it didn't work. I'd appreciate you didn't make terrible assumptions about people. Thanks.
-
The KiCAD libraries are a sad story, No one cares about them, no one moderates them and there's no responsible editor-in-chief. It's just a big tub on GitHub/GitLab or wherever, where manufacturers and others can pour in their symbols and they will then be distributed with the next KiCAD update.
If you want to work with KiCAD, it's essential that you build your own libraries. Also for posterity. Who knows what the next update will bring?
To the immediate issue: it seems that LT has teamed up with Ultra Librarian:
https://www.analog.com/en/design-center/packaging-quality-symbols-footprints/symbols-and-footprints/LTC3113.html (https://www.analog.com/en/design-center/packaging-quality-symbols-footprints/symbols-and-footprints/LTC3113.html)
You'll need to download the Reader, which will then allow you to unpack the symbol to KiCAD format.
-
I have looked in the app itself, and I tried SnapEDA. This isn't my first rodeo.
When I found SnapEDA part - https://www.snapeda.com/parts/RT6154AGQW/Richtek+USA+Inc./view-part/ (https://www.snapeda.com/parts/RT6154AGQW/Richtek+USA+Inc./view-part/) - and add it to KiCAD - it does not appear to contain that part. The files you download from that site don't even contain the RT6154 part number.
Dear @Bassman59, I don't know what your experience is - but yes, I've spent some time looking at things - hence why I'm asking here, because it didn't work. I'd appreciate you didn't make terrible assumptions about people. Thanks.
I didn't make any assumptions about you. I just said that you should create the library parts yourself. You need to know how to do that with every PCB design tool you care to use.
Making symbols in KiCad is very easy. It should take you maybe five minutes.
I checked: In the KiCad footprint library Package_DFN_QFN, we find DFN-16-1EP_4x5mm_P0.5mm_EP2.44x4.34mm.kicad_mod, which is used by the LTC3113EDHD part.
My experience?
SnapEDA is crap. That's part of my experience.
Other than that, long-time KiCad user, since before they started giving KiCad proper major version numbers. Also, long-time Altium user (it's what we have at the day job).
-
Dear @Bassman59, I don't know what your experience is - but yes, I've spent some time looking at things - hence why I'm asking here, because it didn't work. I'd appreciate you didn't make terrible assumptions about people. Thanks.
All he's saying is that it's easy and a necessary skill to be able to draw your own symbols. I don't know how much time you spent looking online for those parts, but I'll bet lunch money for a week that you could have drawn them yourself in less than half the time..
-
I have reached out to people of SnapEDA and they added it to their library: https://www.snapeda.com/parts/RT6154AGQW/Richtek%20USA%20Inc./view-part/ (https://www.snapeda.com/parts/RT6154AGQW/Richtek%20USA%20Inc./view-part/)
Whilst I understand that it's easy to add symbols etc, it feels like duplicating a lot of effort. Maybe KiCAD should have a colab feature that would allow people to contribute these footprints/etc to some common center repo. And no, I already have enough projects ongoing. Most people want to use tools, and not have to fiddle with things themselves. That's just the way things are in the world. ¯\_(ツ)_/¯
-
Whilst I understand that it's easy to add symbols etc, it feels like duplicating a lot of effort. Maybe KiCAD should have a colab feature that would allow people to contribute these footprints/etc to some common center repo. And no, I already have enough projects ongoing. Most people want to use tools, and not have to fiddle with things themselves. That's just the way things are in the world. ¯\_(ツ)_/¯
KiCAD has a series of libraries and if you create a symbol meeting the submission guidelines you can submit it for inclusion. But yes, that means using the tool to create a symbol. That's just the way things are in the world..
No EDA in the world has a symbol for every component either supplied or available elsewhere. No EDA in the world has a footprint meeting your assembly requirements for every package variant of every component. Creating these is a normal part of using such software.
-
KiCad's libraries are already huge but not perfect and they can't contain just every component existing on the planet. No other EDA does that anyway.
If you use git repos for the libraries, you'll see they get updated on a very regular basis.
And yes, you should learn how to create new parts, as this is pretty straightforward and I've never seen any professional using even very expensive EDA software, who never needed to occasionally create a new part anyway.
Digikey also maintains a library of parts for KiCad, you may have a look at that and maybe you"ll find what you need: https://github.com/Digi-Key/digikey-kicad-library
-
KiCad's libraries are already huge but not perfect and they can't contain just every component existing on the planet. No other EDA does that anyway.
If you use git repos for the libraries, you'll see they get updated on a very regular basis.
And yes, you should learn how to create new parts, as this is pretty straightforward and I've never seen any professional using even very expensive EDA software, who never needed to occasionally create a new part anyway.
Digikey also maintains a library of parts for KiCad, you may have a look at that and maybe you"ll find what you need: https://github.com/Digi-Key/digikey-kicad-library
Was maintaining:
This library should be considered unmaintained, but will remain here with and advisory to watch look at the current Issues. The the individuals that were party to creation of this library are currently unable to maintain this. If there are interested in helping update these libraries to 6.0 and continued maintinence through small amounts of contract work please contact me for a chat.
Last commit 2 years ago.
-
KiCad's libraries are already huge but not perfect and they can't contain just every component existing on the planet. No other EDA does that anyway.
If you use git repos for the libraries, you'll see they get updated on a very regular basis.
And yes, you should learn how to create new parts, as this is pretty straightforward and I've never seen any professional using even very expensive EDA software, who never needed to occasionally create a new part anyway.
Digikey also maintains a library of parts for KiCad, you may have a look at that and maybe you"ll find what you need: https://github.com/Digi-Key/digikey-kicad-library
Was maintaining:
This library should be considered unmaintained, but will remain here with and advisory to watch look at the current Issues. The the individuals that were party to creation of this library are currently unable to maintain this. If there are interested in helping update these libraries to 6.0 and continued maintinence through small amounts of contract work please contact me for a chat.
Last commit 2 years ago.
"Digikey aren't paying us to do it any more because they hired some new 20 year olds to break the website every other week"
-
KiCad's libraries are already huge but not perfect and they can't contain just every component existing on the planet. No other EDA does that anyway.
If you use git repos for the libraries, you'll see they get updated on a very regular basis.
And yes, you should learn how to create new parts, as this is pretty straightforward and I've never seen any professional using even very expensive EDA software, who never needed to occasionally create a new part anyway.
Digikey also maintains a library of parts for KiCad, you may have a look at that and maybe you"ll find what you need: https://github.com/Digi-Key/digikey-kicad-library
Was maintaining:
This library should be considered unmaintained, but will remain here with and advisory to watch look at the current Issues. The the individuals that were party to creation of this library are currently unable to maintain this. If there are interested in helping update these libraries to 6.0 and continued maintinence through small amounts of contract work please contact me for a chat.
Last commit 2 years ago.
"Digikey aren't paying us to do it any more because they hired some new 20 year olds to break the website every other week"
DigiKey or whomever they hired to create their library came to the same conclusion as everyone else who maintains libraries: it's really difficult. It's even more difficult when you are dealing with passive devices like simple resistors. How does their library manage them? One symbol per manufacturer part number? That means a giant library.
There are several solutions to the problem, and every user will have a different opinion and a different set of requirements.
And of course a DigiKey library doesn't help when you need a part that DigiKey doesn't carry.
-
This library should be considered unmaintained, but will remain here with and advisory to watch look at the current Issues. The the individuals that were party to creation of this library are currently unable to maintain this. If there are interested in helping update these libraries to 6.0 and continued maintinence through small amounts of contract work please contact me for a chat.
If that is an exact quote, then I sincerely hope that whoever wrote that mess of a paragraph has never been, and never will be, in charge of maintaining the library. ;)
-
This library should be considered unmaintained, but will remain here with and advisory to watch look at the current Issues. The the individuals that were party to creation of this library are currently unable to maintain this. If there are interested in helping update these libraries to 6.0 and continued maintinence through small amounts of contract work please contact me for a chat.
If that is an exact quote, then I sincerely hope that whoever wrote that mess of a paragraph has never been, and never will be, in charge of maintaining the library. ;)
First paragraph of README.md :palm:
-
Ah yeah. That sucks. :-DD
And yes, maintaining such huge libraries is a gigantic endeavour.
Anyway, creating your own parts is easy and during the time wasted for looking up existing parts online, you probably would have been able to create at least a dozen parts or more. ::)
In particular if the footprint already exists and all you need is to create a symbol. That's a very simple job. Footprints (especially if they are a bit exotic) require a bit more care and attention.
-
Folks have already said most of what I want to say, but I'll chip in anyway.
Through out my years in this game, I must have wasted thousands of pounds on PCB re-spins caused by library components that are wrong. From incorrect connections (like a base/collector swap on a transistor footprint) to pad/paste/resist clearances on IC's that prevent paste release or correct soldering in production. It really seems that the libraries are an inconvenience given to interns.
I do use simple components, resistors capacitors and the like, but almost all significant parts are created by myself.
As others have said, regardless of the CAD package used if you are going to design PCB's learning to create your own symbols and footprints is a must.
-
Folks have already said most of what I want to say, but I'll chip in anyway.
Through out my years in this game, I must have wasted thousands of pounds on PCB re-spins caused by library components that are wrong. From incorrect connections (like a base/collector swap on a transistor footprint) to pad/paste/resist clearances on IC's that prevent paste release or correct soldering in production.
This is why - on the flip side - I'm worried that I will cock this up and end up with something I created myself that is just wrong. Unlike software and 3D printing - it's not easy to spin a board with a tiny pitch. I'm trying to create a board with a booster converter and some other components that only come in tiny pitch - for whatever reason. So hand soldering is almost out of the question :)
Thanks!
Now I need to find some good tutorials on how to create these library components myself.
-
This is why - on the flip side - I'm worried that I will cock this up and end up with something I created myself that is just wrong.
Which is exactly why you should not be trusting library components from a public repository..
If you're using PCB footprints from the KiCad libraries, then you only need to draw a schematic symbol with the right pin assignments. That's not too hard. Double check after you're done. Maybe have someone else double check it for you; it will only take a few minutes for them to make sure the pin numbers are correct.
Then, in the schematic, assign the right footprint. Care is required here as there are often a number of footprints that are similar, so you need to make sure to pick the right one by comparing the package drawing in the IC datasheet with the actual dimensions of the footprint in the footprint editor. Again, it's OK to have a second set of eyes verify your choices if you're worried.