LTspice Library API - Revision history

Lewispaul: Added a link to previous versions.

2011-09-21T01:03:55Z

Added a link to previous versions.

Lewispaul: Add DISQUS for comments

2011-09-21T00:55:58Z

Add DISQUS for comments

Analogspiceman: moved LTSPICE Library API to LTspice Library API

2011-05-31T07:15:10Z

moved LTSPICE Library API to LTspice Library API

Analogspiceman at 07:09, 31 May 2011

2011-05-31T07:09:40Z

Cmcdowell at 20:39, 9 April 2011

2011-04-09T20:39:19Z

Cmcdowell at 10:52, 31 March 2011

2011-03-31T10:52:52Z

Cmcdowell at 10:51, 31 March 2011

2011-03-31T10:51:50Z

Cmcdowell at 10:50, 31 March 2011

2011-03-31T10:50:31Z

Cmcdowell: Motiviation for summary of LTspice library

2011-03-31T10:47:40Z

Motiviation for summary of LTspice library

Cmcdowell: Blanked the page

2011-03-30T07:21:57Z

Blanked the page

@@ Line 13: / Line 13: @@
 The link below gives you a quick summary of the LTspice installation and the library parts.  You can use this to help satisfy the above requirements.
-[http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf LTspice Part Summary]
+Current Version: [http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf LTspice Part Summary]<br>All Versions: [[File:LTSpicePartListAPI.pdf]]
 {{#widget:DISQUS

@@ Line 13: / Line 13: @@
 The link below gives you a quick summary of the LTspice installation and the library parts.  You can use this to help satisfy the above requirements.
-[[LTspice Part Summary]]:
+[http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf LTspice Part Summary]
 http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf

@@ Line 1: / Line 1: @@
 You can use an external schematic editor to generate your LTspice netlist.  LTspice can read the netlist and do your simulation.  This saves you time drawing the schematic in both applications.
-To be compatible with most SPICE libraries, you must satisfy the following requirements:
+To be compatible with most SPICE libraries, your SPICE syntax must satisfy the following requirements:
-.) Your part name must be one of the part names in the library.
+# Your part name must be one of the part names in the library.
-.) "IC" typically map to a sub-circuit.  Therefore, you must use the standard PSPICE "X" prefix for your reference designators.
+# An "IC" typically maps to a sub-circuit.  Therefore, you must use the standard SPICE "X" prefix for your reference designators.
-.) You need to have your SPICE netlister export the correct number of nodes that the corresponding libraries sub-circuit expects.
+# You need to have your SPICE netlister export the correct number of nodes that the corresponding libraries sub-circuit expects.
-.) Your node parameters must be in the correct calling sequence.  Node names do not have to be the same.
+# Your node parameters must be in the correct calling sequence.  Node names do not have to be the same.
-.) Typically you must include the corresponding library in your netlist.
+# Typically you must include the corresponding library in your netlist.
 Sub-circuit example:
-----
+ XU1  0 /My/V5in /Vc LT1086-5 ; Node Sequence Specification <GND,VO,VI>
 The link below gives you a quick summary of the LTspice installation and the library parts.  You can use this to help satisfy the above requirements.
-[[LTSPICE Part Summary]]
+[[LTspice Part Summary]]:
 http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf

← Older revision		Revision as of 20:39, 9 April 2011
Line 16:		Line 16:

	[[LTSPICE Part Summary]]		[[LTSPICE Part Summary]]
−	http://ltwiki.org/~~files~~/LTSpicePartListAPI.~~html~~	+	http://ltwiki.org/images/4/4e/LTSpicePartListAPI.pdf

@@ Line 1: / Line 1: @@
 You can use an external schematic editor to generate your LTspice netlist.  LTspice can read the netlist and do your simulation.  This saves you time drawing the schematic in both applications.
-To be compatible with most SPICE libraries, you must satisfy the following requirements:</br>
+To be compatible with most SPICE libraries, you must satisfy the following requirements:
 .) Your part name must be one of the part names in the library.
 .) "IC" typically map to a sub-circuit.  Therefore, you must use the standard PSPICE "X" prefix for your reference designators.

← Older revision	Revision as of 07:15, 31 May 2011
(No difference)

← Older revision	Revision as of 10:47, 31 March 2011
Line 1:	Line 1:

	+	You can use an external schematic editor to generate your LTspice netlist. LTspice can read the netlist and do your simulation. This saves you time drawing the schematic in both applications.
	+
	+	To be compatible with most SPICE libraries, you must satisfy the following requirements:
	+	1.) Your part name must be one of the part names in the library.
	+	2.) "IC" typically map to a sub-circuit. Therefore, you must use the standard PSPICE "X" prefix for your reference designators.
	+	3.) You need to have your SPICE netlister export the correct number of nodes that the corresponding libraries sub-circuit expects.
	+	4.) Your node parameters must be in the correct calling sequence. Node names do not have to be the same.
	+	5.) Typically you must include the corresponding library in your netlist.
	+
	+	Sub-circuit example:
	+	----
	+	XU1 0 /My/V5in /Vc LT1086-5 ;Node Sequence Spec.<GND,VO,VI>
	+	----
	+
	+	The link below gives you a quick summary of the LTspice installation and the library parts. You can use this to help satisfy the above requirements.
	+
	+	[[LTSPICE Part Summary]]
	+	http://ltwiki.org/files/LTSpicePartListAPI.html

← Older revision		Revision as of 07:21, 30 March 2011
Line 1:		Line 1:
−	~~[[Media:file:///C:/MyPythonScripts/LTSpicePartListAPI.html]]~~	+