It's equivalent to .CIR or .NET.
..SPI is usually from Silvaco SmartSpice.
Curly bracket stuff will need to be changed, {...} -> '...' and there are differences where subcircuit parameters are used.
...Jim Thompson
It's equivalent to .CIR or .NET.
..SPI is usually from Silvaco SmartSpice.
Curly bracket stuff will need to be changed, {...} -> '...' and there are differences where subcircuit parameters are used.
...Jim Thompson
I have a customer that wants my PSPICE design files but they must be in "*.spi" files only and only primitives from SPICE library (resistors,inductors, diodes.....) can be used. I work in Micro-Cap 7 and can export PSPICE files but what are they talking about? How do I meet this requirement?
TIA Harry
"Harry Dellamano" schrieb im Newsbeitrag news:CvxHe.10167$DJ5.5708@trnddc07...
Hello Harry,
they just want the SPICE netlist with no MC7 specific control statements. You should give it the extension ".spi" instead of ".cir" or whatever you get from MC7.
Some component vendors also name their model files containing the ".model .." and ".subckt ..." with the extension ".spi" .
This means that they don't like any behavioral sources in your netlist because the syntax can be very different among the different SPICE programs. The SPICE elements E, F, G and H are also standard in every SPICE program. You can take a look to PSPCREF.PDF what syntax PSPICE accepts.
Best regards, Helmut
Thanks Helmut and Jim, that is exactly what I needed. I will have your favorite beverages ASAP! Cheers, Harry
Have something to add? Share your thoughts — no account required.
Ask the community — no account required