Pspice To Ltspice Converter Weight
In airborne applications, the size and weight of equipment are critical. Tailed cycle-by-cycle transient simulations on PSPICE are used to study the converters'. I am interested in looking at signal and power intergrities. The only models that I have are the pspice and the TINA models. Does TINA work.? Is there anyway I can convert my spice model to a file type supported by pspice? OnSemi provides a few spice models for this part and I am getting stuck converting the Pspice file so that it is usable in LTspice. The netlist into Hello All, Is it possible to convert the pspice. 1.5A Monolithic Buck-Boost DC/DC Converter with LTspice.
I am designing a buck-boost regulator for a course at school and I would like to use the OnSemi ntk3139p PMOS transistor. OnSemi provides a few spice models for this part and I am getting stuck converting the Pspice file so that it is usable in LTspice. I realize I could pick something else, but I wanted to take this opportunity to dive into some of the nitty gritty in spice.
Some of the references I have been following for spice are:
- There are more but I don't have 10 reputation points yet to post them
The Pspice file in question is listed bellow:
My crack at converting it is:
I have rearranged some of the lines so that they resemble some of the other subcircuit LTspice files that I have been looking at with the netlist first and the model definitions second and I have added the parenthesis to the parameters of the model directives. Most of the subcircuit file makes sense to me but a few of the devices I am not sure about such as FI2. I think this is a current dependent current source but it may not be used properly here. I am not sure where I am going wrong here as the error I am getting in LTspice is
The way I implement my NTK3139P.sub is:
- I save the NTK3139P.sub file in
C:Program Files (x86)LTCLTCspiceIVlibsub - Open LTspice
- Create New symbol
- Pin numbers coorelate with subcircuit definitions
- In attributes: Prefix = X, Value = ntk3139p
- Saved where it can be seen by LTSpice
- Restart LTspice
- Create super simple schematic to test it with the FET, a resistor, a voltage source, and ground
- Run a
.tran 1simulation - The aforementioned error occurs
Any help debugging this and/or explanations of where I went wrong or a friendly point to some more general spice literature would be appreciated!
$endgroup$1 Answer
$begingroup$Ltspice Transistor Models
If I simply save that PSpice file to a ntk3139p.lib file and import it in LTspice, it all works fine:
The Rds(on) looks in line with the datasheet for that part.
What you need to keep in mind is to change the PMOS statement line to X (because it's a subcircuit) and match the name to the subckt name declared in that lib. Ctrl-click to access the advanced properties page for the FET:
This is actually explained in detail at http://www.linear.com/solutions/1083
And if you actually want to import that model into LTspice so that you don't have to use an .include statement, what you need to do is
- Copy the aforementioned
ntk3139p.libintoLTspiceIVlibsub; this directory can [and does] contain both.liband.subfiles. - Create a
ntk3139p.asyinLTspiceIVlibsym(or in one of its subfolders, in which case the component will show up in the corresponing category in theF2select component dialog). This.asyfile is initially a copy ofpmos.asythat comes with LTspice in this case. Now you need to edit thisntk3139p.asyfile either in a text editor or using LTspice itself (viaEdit->AttributesorCtrl+A) so that it reads:
Now you can add the new component, but since we're using X as type it automatically get labelled as an IC (U) rather than MOSFET as before. But we don't need an .inc line anymore for the simulation to work:
Pspice Model In Ltspice
Honestly this procedure is usually not worth the hassle for me... and if you reinstall LTspice or load your schematic on a different machine, you have to do it all over again, never mind that it becomes less clear in the schematic what components you need[ed] extra libraries for. Furthermore, you can no longer change the MOSFET by right-clicking on it an picking a new model. If you try that with your custom asy file, you get:
Which for me is the most annoying part. So I don't recommend doing this import procedure for MOSFETS; I think it's only worth the hassle for ICs.
I honestly don't know exactly what the .sub files are restricted to contain in LTspice, but the ones that come with the program are all binary files containing LT's proprietary models, some of which also make use of LT's extensions like steady and so forth. I don't think the .sub binary format that LTspice uses is publicly documented anywhere.
Add Spice Model To Ltspice
$endgroup$