OPA1662 SPICE Model by Texas (Problem)

OPA1662 SPICE Model by Texas (Problem)

Anonymous
Not applicable
2,292 Views
8 Replies
Message 1 of 9

OPA1662 SPICE Model by Texas (Problem)

Anonymous
Not applicable

Hello everyone!

 

I would like to simulate the OPA1662 amplifier. I found the Spice model, but it's in the format used by Texas Instruments. This format is not 100% compatible with Nnspice used by Eagle. Is it possible to translate this model to one compatible with Eagle? (Spice model is attached.)

 

Regards,

Jose de Franca

Reply
Reply
0 Likes
2,293 Views
8 Replies
Replies (8)
Message 2 of 9

jorge_garcia
Autodesk
Autodesk
Hi @Anonymous,

I hope you're doing well. Thanks for including the model file. I'll take to our developers to see if there's anything that can be done to translate the file.

Let me know if there's anything else I can do for you.

Best Regards,


Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
Reply
Reply
0 Likes
Message 3 of 9

john.barnett
Participant
Participant

The model file that you have in your post is in the proper SPICE format and can be used as a subcircuit in ngspice.  Since the OPA1662 is a dual op amp,  it will be necessary to properly mapped the pins for the part when the model parameters are added to eagle part file.  There is a eagle youtube video that show how to map spice model parameters to eagle parts. 

Reply
Reply
0 Likes
Message 4 of 9

Anonymous
Not applicable

Thank you very much for your help! 🙂

 

I've read a lot about how to associate the spice model with a new component. Maybe I did something wrong. Now that I know the model is compatible with Spice, I will try to find what I did wrong. I'll let you know if it works.

 

Thanks!

Reply
Reply
0 Likes
Message 5 of 9

john.barnett
Participant
Participant

Jorge,.  

 

You don't have to translate the file.  It is in the spice format.  It just need to be mapped in the eagle OPA1662AIDR file.  I just created the OPA1662AIDR eagle file and placed it into my Texas Instruments_By_element14_Batch_1.lbr library.  Keep in mind that the OPA1662AIDR is a dual op amp so the same model file will have to be mapped to both the op amps in the same package.  Once I looked at the data sheet and seen the device parameters I thought this device might be a great replacement for SN5534 which has been the main device because of its low noise characteristics for the input to high end audio boards for decades.

 

John

Reply
Reply
0 Likes
Message 6 of 9

Anonymous
Not applicable

Hello!

 

Thank you again! Well ... No, I can't associate the MDL file with the new component. I imported the symbol from the TL082 device (it is also a dual op-amp). Next, I try to import the model. But I get an error message right away. 😞 Please see the attached printscreen. Do you have any idea what I'm doing wrong?

Reply
Reply
0 Likes
Message 7 of 9

Anonymous
Not applicable

I tried a different solution. I created a new schematic. Then I inserted a new device, Opamp from the "ngspice-simulation" library. Lastly, I tried to assign the OPA1662 model to Opamp (as a subckt). I got the same error message: "Part E1 cannot be simulated". 😞

Reply
Reply
0 Likes
Message 8 of 9

jorge_garcia
Autodesk
Autodesk

Hi @Anonymous  @john.barnett 

 

  I looked at the model more carefully and because it is a Pspice file it's close but not what Ngspice needs. The issue is with E1 and G1 components. These are voltage controlled sources however in the PSpice file they are used as independent sources and it appears Pspice is OK with that. Ngspice is not, I was able to get the model processed by changing E to V and G to I. See attached model, just unzip it.

 

It can be mapped but I can't vouch for it's accuracy, you'll have to try it out.

 

Let me know if there's anything else I can do for you.

 

Best Regards,



Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
Reply
Reply
0 Likes
Message 9 of 9

Anonymous
Not applicable

Hello!

 

Thank you very much for your help!

 

Now I was able to assign the model and map the model pins to the device pins. Unfortunately, however, the simulation returns a multitude of errors. I attached a TXT file with the error messages. Something is wrong.

Reply
Reply
0 Likes