Congratulation you just broken a number of license agreements.
Example from the analog devices licence in your repo:
The licensee may not sell, load, rent, lease, or license the macro-models, in whole, in part, or in modified form, to anyone outside the licenseeās company. The licensee may modify these macro-models to suit his specific applications, and the licensee may make copies of this diskette or macromodels for use within his company only.
Man must these be old to still reference diskettes. Leaves me to wonder if any of the models come even close to modeling the behavior of parts produced with modern manufacturing technologies.
You made this even worse by setting the license of the repo as gpl. Just to make it clear: only the copyright owner can change a licence.
*/////////////////////////////////////////////////////////////////////
* Legal Notice: This material is intended for free software support.
* The file may be copied, and distributed; however, reselling the
* material is illegal
I am just beginning with Spice simulation in KiCad and it would be nice to have a bunch of components completely prepared and integrated into KiCad.
A few days ago I did the Sallen_Key demo, and it mostly worked, but I do not have an AD8051. I am also mainly interested in simple and classic parts such as the LM358.
With an LM358 I will also be able to verify phase shifts on my Rigol DS1052, while with the AD8051 (Even if I had it) itās 110MHz bandwith is more of a nuisance than a gain for educational purposes.
So I got a model for the lm358.lib (2.2 KB) from digikey ad it has no licensing info in it whatsoever.
And then of course it did not work. It turned out that all the pins are in the wrong place. At the moment my temprary fix is:
(Note that the feedback is to the non-inverting input now) I know this is redicilous, and probably easy to fix if you know how. Well, I started the NGspice manual, and itās probably in there somewhere on one of those 630 pages, and I will find it (But probably not in that document, it is not written for beginners).
For people beginning with spice experiments in KiCad it would be really nice to have a small library of components that work out of the box. Right now my attention is getting fragmented into such little pieces that itās hard to get anything started with ngSpice in KiCad, and this in turn makes it hard for me to keep motivated.
I do not see why a huge collection of random spice models is usefull. When I start designing some gadget I want to release as an open source gadged (for example an simple electronic load is a popular example) then it would be nice to have accompanying working spice models in it. For more advanced projects I may want low offset opamps or whatever, and selectrion of the opamp I want to use will be partly based on availability of compatible spice models. I may even mail some manufacturers that I wonāt use their opamps in my projects because of incompatible licences. That legal mumbo jumbo is a real nuiscance.
Whatās keeping you from picking this up?
Hand picking a (few) handfulls of spice models and attaching them to KiCad symbols and copying them in a separate lib seems like doable for a single person.
Then anyone can clone your lib from github and add it in KiCad.
Such a collection is more valuable than 10000 random spice libs.
At the moment there are several hundred opamps in the default KiCad libraries. Do any of them contain a spice model? (If so, a simple text file with a list would be nice to have).
I just noticed that the āVSOURCEā voltage source from the Sallen_Key is also nowhere else in KiCadās libs, and quite different from the VSOURCE in the very small āpspiceā lib in Eeschema. Fixing those things should be relatively easy, but to be honest, I have no intention at the moment of involving myself with KiCadās library management.
I have just started working on updating āGetting Started in KiCadā, wich is long overdue and hope to make something decent out of it in a few months time. Itās already stretching it thin for me, because I have to learn the basics of git and asciidoc to be able to work properly with that document.
Everything Spice related is already a sidetrack for me at the moment. I believe that with answering questions here and now working on āGetting Startedā Iām already above average in contributing.