Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
PSPICE a simulation tool for electronic circuits released by Berkeley university...
SPICE is an acronym for "Simulation Program with Integrated Circuit Emphasis."
PSPICE a simulation tool for electronic circuits released by Berkeley university...
SPICE is an acronym for "Simulation Program with Integrated Circuit Emphasis."
PSPICE came from MicroSim (around 1985). It was a very nice DOS-based version of Berkeley SPICE (around 1975). PSPICE later moved to OrCAD and then to Cadence, and became a Windows app.
There is also TSpice from Tanner.
I wonder why there is no IEEE SPICE standard like there is for VHDL for example. PSpice, HSPICE, and Berkeley SPICE are all a little different.
There is no hope for a netlist standard for spice because each vendor add there own features to follow the user requirements. Examples are: parametric subcircuits, namespace conventions, simulation options, result storage options and uncounted model flavors.
There is an actual requirement for a standard which is driven by automatic characterisation and exploration tools. In this usage spice is only used as an engine driven by a higher layer design enviroment. This enviroment could run for example 2 HSIM for functional, 8 Spectre for DC, 6 ADS for HB and 46 Spice3F4 on a cluster system for a complex mixed signal circuit verfication. The interface is then a specific ripper for the commercial engine. It drives the netlist, commands and collects the results.
The next level of interface bypass the spice netlist and command reader and use a memory API to drive direct the matrix engine. I expect that this come only with a single vendor because there is a dramatic drop of understanding of the advantages of this approach in the design community. Furtheron the single big company trend defocus interop standards.
I have heard that there is a TCL-Spice, so a spice driven by a TCL-Script interpreter. But I think it is more focused on automation features.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
