Mithat Konar (the wiki)

User Tools

Site Tools

You are here: Mithat Konar (the wiki) » KiCad notes » Quick Guide to Using KiCad for SPICE Simulation
kicad:kicad_spice_quick_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
kicad:kicad_spice_quick_guide [2014/06/01 21:52] – mithatkicad:kicad_spice_quick_guide [2014/06/01 21:58] – mithat
Line 12: Line 12:
     * [[https://www.gnu.org/software/gnucap/|gnucap]]: Not actually SPICE but tries to be syntax-compatible.     * [[https://www.gnu.org/software/gnucap/|gnucap]]: Not actually SPICE but tries to be syntax-compatible.
     * [[http://www.spiceopus.si/|SpiceOpus]]: Proprietary but nice, especially the output plotting.     * [[http://www.spiceopus.si/|SpiceOpus]]: Proprietary but nice, especially the output plotting.
-    * [[http://www.linear.com/designtools/software/|LTSpice]]: Linear Technology's popular, proprietary Windows solution. Works in [[http://www.winehq.org/|Wine]]. Need to verify if it is scriptable. Has a GUI anyway, so ... +    * [[http://www.linear.com/designtools/software/|LTSpice]]: Linear Technology's popular, proprietary Windows solution. Works in [[http://www.winehq.org/|Wine]]. Has a GUI anyway, so ... ? Whether it's scritable needs to be verified. 
-    * [[http://www.cadence.com/products/orcad/pspice_simulation/Pages/default.aspx|PSpice]]: Windows-only, expensive, defacto standard professional solution in the USA. They also have a tradition of making available a //gratis// crippleware student version. Also has a a GUI, so ...  +    * [[http://www.cadence.com/products/orcad/pspice_simulation/Pages/default.aspx|PSpice]]: Windows-only, expensive, defacto standard professional solution in the USA. They also have a tradition of making available a //gratis// crippleware student version. Also has a a GUI, so ... ? 
-    * (Your favorite goes here.)+    * Any others?
   * Component libraries with SPICE symbols   * Component libraries with SPICE symbols
     * There is a library of basic SPICE components that ships with KiCad. It's good enough for initial experimentation.     * There is a library of basic SPICE components that ships with KiCad. It's good enough for initial experimentation.
-      * The library isn't included in Eeschema projects by default. You'll have to add it manually if you want to use it. +      * The library isn't included in Eeschema projects by default. You'll have to add it manually if you want to use it. In Debian-based Linux, it's at ''/usr/share/kicad/library/pspice.lib''. (PSpice is a popular proprietary version of SPICE.)
-      * In Debian-based Linux, it's at ''/usr/share/kicad/library/pspice.lib''. (PSpice is a popular proprietary version of SPICE.)+
     * I am developing (very slowly) [[https://bitbucket.org/mithat/kicad-spice-library|my own library]] of components based on the above with some changes and additions.     * I am developing (very slowly) [[https://bitbucket.org/mithat/kicad-spice-library|my own library]] of components based on the above with some changes and additions.
  
Line 26: Line 25:
   - Open Eeschema and remove all the library references included by default.   - Open Eeschema and remove all the library references included by default.
   - Manually add one or more libraries with SPICE components to the project.   - Manually add one or more libraries with SPICE components to the project.
-    * The SPICE library that comes packaged with KiCad is //not// included by default in new KiCad projects. +    * Note that the SPICE library that comes packaged with KiCad is //not// included by default in new KiCad projects. 
-  - Specify the SPICE engine you want to use.+  - Specify the SPICE engine you want to use:
     * Click the "Generate netlist" button (or the equivalent menu item).     * Click the "Generate netlist" button (or the equivalent menu item).
     * Select the "Spice" tab     * Select the "Spice" tab
Line 35: Line 34:
   - Do your schematic capture, subject to a couple best practices:   - Do your schematic capture, subject to a couple best practices:
     * For named nets, use global labels instead of local labels.     * For named nets, use global labels instead of local labels.
-      * In the netlists, global identifiers will be used as-is. However, local labels will get text prepended to the name, and this will make it hard for you to remember/guess what the full identifier is.+      * The reason for this is that in the netlists, global identifiers will be used as-is but local labels get text prepended to the name---which makes it hard for you to remember/guess what the full identifier is.
     * Use the "''0''" component from a SPICE component library rather than the ''GND'' symbol.     * Use the "''0''" component from a SPICE component library rather than the ''GND'' symbol.
-      * "''0''" is the official name of ground node in SPICE. Some engines may translate ''GND'' into ''0'', some are not.+      * "''0''" is the official name of ground node in SPICE. Some engines may translate ''GND'' into ''0'', some may not.
   - Specify the simulations you want to run and the output you want to display by adding a text block (i.e., "comment") with the needed SPICE and Nutmeg syntax plus a little added mojo. To do an AC analysis and plot the response at node ''vout'', you would add the following block:<code>   - Specify the simulations you want to run and the output you want to display by adding a text block (i.e., "comment") with the needed SPICE and Nutmeg syntax plus a little added mojo. To do an AC analysis and plot the response at node ''vout'', you would add the following block:<code>
 +PSPICE  +PSPICE 
kicad/kicad_spice_quick_guide.txt · Last modified: 2018/10/17 14:56 by mithat
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki