In trying to import the model for the LT1028 op-amp, I get this error:
Fatal error: Unknown device type:a
There is no item A in the Device Reference of the current QSPICE Documentation.
Is it correct to understand that it is currently under development and is in a pending state?
A-devices are Linear Technology Corporation’s proprietary special function/mixed mode circuit simulation elements. Not sure if Qspice can support that, let see Mike’s response.
LTspice has the A-device as an OTA building block for Op-Amps. It’s dated and unique to LTspice, so I didn’t implement it for QSPICE.
The next generation, in QSPICE, is the à device. It solves the hardest part of Op-Amp modeling, a transconductance that draws power from the appropriate rail. It also supports an extension that is a compete Rail-To-Rail Op-Amp as a native circuit element. I’m generating a notes on how to use it and illustrate its value.
As far as the LT1028, that is a device I’ve used extensively for signal conditioning down hole in oil exploration.
The trick to modeling it is that it has about 30pF capacitance between the inputs which makes stability challenging. The datasheet isn’t lying when it talks about just a few pF input capacitance. That’s on the non-inverting input while in voltage-follower configuration. You don’t see the 30pF because it’s bootstrapped due to the voltage follower configuration.
If you can find a PSpice LT1028 model, use that. If it’s missing the input to input capacitance add it.
Thank you very much for your clear explanation.
I understand that you have incorporated a new device to replace the A device.
So I researched and found one in the PSpice library for the old LT1028.
@ rmruthyun proposed an idea to convert LTspice A-device to Qspice Ã-device or ¥-device. It is a tedious process and requires a lot of knowledge and between these device model.
Here is a conversion results for LT1028.lib
As Qspice and LTspice are different (or my knowledge limitation), I cannot model all instance parameters and have to give up some of them during conversion, which included incm, incmk, en with equation and ilimit in diode model. But simulation result by compare to LT1082 demo circuit in LTspice is still identical. Up to now, I can successfully convert 3 subckt which include logic or OTA A-device, and with identical or very close simulation results.
@piero.giubilato Thanks for the like. For your reference, I have been working on converting more complicated LTspice A-devices to Qspice native devices over the past two months. However, I am still assessing how universal my method currently is. If you have a subcircuit with an A-device that needs conversion but you do not have a solution, feel free to post it in the forum. Here are some of the recent tasks I have shared.
Using different values of the DC and AC resistor.
I suggest using such a resistor instead of an inductor. Moreover, by default, the inductance is shunted by a parallel resistor.
I am trying to use the LTSpice LT1028 model for noise analysis, and made some advancements thanks to your suggested conversion. However, I still did not mage to have it working properly, as QSpice signals few warnings after updating the model:
Warning: Ignoring unknown instance parameter “VV2P” of device Ã1.
Warning: Ignoring unknown instance parameter “V2P” of device Ã1.
Warning: Unexpected number, “0”, in device Ã1•X4.
Warning: Unexpected number, “2”, in device Ã1•X4.
I am sure I am missing something relatively obvious, but my experience in models building is quite limited. Below the reworked model generating the errors (the original one is from the latest LTSpice library).
Oh, unfortunately, noise analysis is not something that I believe can have an equivalent using the A-device OTA in Qspice Ã-device. I am also not an expert in noise analysis, which is why I lack the experience to verify things in this area. Sorry to disappoint you.
@piero.giubilato Let me explain a bit more about what is happening with the equivalent model of the A-device for noise analysis.
When comparing the A-device OTA and the Qspice Ã-device OTA, the noise parameters en, enk, in, and ink have identical definitions between them. However, the A-device OTA has incm and incmk, while the Ã-device OTA has inf, and I have no idea how to deal with this discrepancy.
In addition, the A-device may have EN=…freq…, which is not accepted in Qspice. It appears that noise analysis in LTspice considers the simulation frequency for its EN value. This is why I don’t think an equivalent model for noise analysis can currently be created.
But for .ac or .tran, I currently can achieve quite a good match.