I'm trying to run a simulation on the LM158 dual OpAmp component. The component is available on Ultra Librarian from DigiKey. When loading in the component, I'm given the option of adding the Spice model (.MDL) file. When I select this option, I change the spice type to X: Subcircuit, and press Map. At this point, I can select Load Model, and am able to bring in the Model from Ultra Librarian. When I press "OK", however, I receive an error "Part E1 cannot be simulated, check value and connections!
As far as I know, I have not done anything to run a simulation yet; only load in the model.
As an alternative, the LM358 is available from the list of parts included in Eagle. It does, however, separate into two Op Amps and two pins for a power supply, and the model for the 358 is the same as the 158.
Is there a better way to go about this? Is there an error in my procedure for loading up the model? Should I go into the model file and troubleshoot it for an error that I can fix?
All help and advice is appreciated.
Solved! Go to Solution.
Solved by jorge_garcia. Go to Solution.
Hi @Anonymous ,
I hope you're doing well. I would say to grab the LM358 for now, currently NGSPICE requires a vanilla SPICE model. Most of the models online are PSPICE or some other proprietary version of SPICE with some mods. We hope to shortly update our NGSPICE version so that this will no longer be an issue.
Let me know if there's anything else I can do for you.
Best Regards,
Thanks for the quick response Jorge. For the LM358 though, I still need to Map a Model, right? How do I do this for the LM358 model that's already available.
Thanks for your help.
Currently, I can access an Opamp model from the EAGLE 9.6.2\examples\spice\examples folder. Is this what you mean by "vanilla spice model"? Would this mean that there is no way import the specific characteristics of components for ngspice as of right now?
Thanks,
Mathieu Gaydos
Hi @Anonymous ,
I hope you're doing well. That's not what I mean by "vanilla spice model", what I mean by that phrase is that the model file you download should only contain standard SPICE syntax, it can't have any of the proprietary additions that PSPICE, TINA, and others have added to the default SPICE language. This will become less of an issue soon but it's a problem now.
Can't find what you're looking for? Ask the community or share your knowledge.