Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How could we pull the operational amplifier models from OpAmp.lib for other simulators? #501

Closed
1 task done
csrabak opened this issue Jan 25, 2024 · 10 comments · Fixed by #517
Closed
1 task done
Assignees
Labels
Milestone

Comments

@csrabak
Copy link

csrabak commented Jan 25, 2024

OpAmps.lib contains some interesting opamp models which are [still?] not available if Spice class simulator is chosen.

Is it a mean to pull these models, or a pointer to the original source so we could update SpiceOpamp.lib?

TODO

  • Update SpiceOpamp library
@zergud
Copy link
Collaborator

zergud commented Jan 25, 2024

May be we can use discussion for such questions?

@tomhajjar
Copy link

tomhajjar commented Jan 26, 2024

Presently there are 2 OpAmp libraries supplied with Qucs-S.
OpAmps.lib -> Qucs
SpiceOpamp.lib -> Qucs-S

I made a new library called OpAmp.lib that should be released eventually. Here is the last update
OpAmp.lib -> Qucs-S

Back to your question about OpAmps.lib. It was done a very long time ago and optimized to work with Qucs. The devices and models are very old and not used much today. In general it is worthless for ngspice or LTspice. You should search the LTspice forum and ask questions if you want models not included with LTspice.

OpAmp library.zip

@ra3xdh
Copy link
Owner

ra3xdh commented Jan 26, 2024

The current implementation of the OpAmp.lib relies on Qucsator netlist syntax features that cannot be back converted to SPICE. It's need either to extend qucs2spice.cpp or recreate this library. You can recreate the OpAmp.lib library using this manual: https://qucs.sourceforge.net/docs/tutorial/opamp.pdf It explains how the opamp macromodels were done.

@ra3xdh
Copy link
Owner

ra3xdh commented Jan 26, 2024

I made a new library called OpAmp.lib that should be released eventually. Here is the last update

I will add the new models to SpiceOpamp.lib library.

@tomhajjar
Copy link

Vadim

Are you going to replace models in the "new" SpiceOpamp.lib with the versions I did in OpAmp.lib?

Is there a reason for so many versions of "ad822" in the present SpiceOpamp.lib?

2024-01-26_122451

@ra3xdh ra3xdh removed the question label Jan 26, 2024
@ra3xdh ra3xdh self-assigned this Jan 29, 2024
@ra3xdh
Copy link
Owner

ra3xdh commented Jan 31, 2024

I have added OP491 and LF356 models by @tomhajjar to the SpiceOpamp library. The duplicate AD822 models are removed, because all device were sharing one model. Only AD822 remains in the library. See #517

@ra3xdh ra3xdh added this to the 24.1.0 milestone Jan 31, 2024
@ra3xdh ra3xdh linked a pull request Jan 31, 2024 that will close this issue
@ra3xdh
Copy link
Owner

ra3xdh commented Jan 31, 2024

Closing as completed after merged #517

@tomhajjar
Copy link

tomhajjar commented Jan 31, 2024

See below...

@ra3xdh ra3xdh closed this as completed Jan 31, 2024
@ra3xdh
Copy link
Owner

ra3xdh commented Jan 31, 2024

The sent version of the library doesn't contain TLV2371

@tomhajjar
Copy link

tomhajjar commented Jan 31, 2024

Attached is a "replacement" library called SpiceOpamp.lib so the internal labels are the same as your old library. You can splice in any OpAmp from your older version and the internal labels will be the same.

I was having issues creating the library. Qucs wasn't creating the library if I had "Add subcircuit description" checked and didn't add the descriptions and one file was missing it's subcircuit. As I said before any "glitch" and the Create Library program does the wrong thing.

Still have to delete every occurrence of SpiceOpamp.lib...

2024-01-31_110024
SpiceOpamp.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants