Icemaker: Why use LTSpice to SVG?

For a modest sized schematic, a nicely hand drawn schematic takes about 1 min to create. Unfortunately, using a general purpose drawing program to create the same schematic takes from 10 to 15 minutes even if a library of symbols are made in advance.

However, a good schematic editing tool can create a schematic in about 2 minutes. Unfortunately, schmematic editors are well known to create schematics that are not suitable for publications in research papers or educational material.

The purpose of Icemaker LTSpice to SVG is to let the user create an LTspice schematic and then use Icemaker to "beautify" the schematic so that the resulting output can be used in publications. If needed, the svg file can be further edited (or tweaked) using Inkscape.

Icemaker: LTSpice to SVG Examples

Example asc file: example.asc

Example svg file: example.svg

Example asc file: example2.asc

Example svg file: example2.svg

The above examples requires the custom "svg" library to be installed for LTSpice (see Installation)

The svg file can be imported into Inkscape (Inkscape.org) and, if needed, easily modified
(things should remain on grid)

You can also create your own LTSpice symbols but they should be placed in the svg directory below where -symPath points to. No new symbol names should be the same as existing LTSpice symbols.

You can also create your own svg symbols to go with your new LTSpice symbols (if you don't like the automatically generated svg symbols). Place any new svg symbol inside the symDefn.svg file within the svg directory (see existing examples)


For the above example (in the command line) run ...
% icemaker -export=example.svg -text=subscript example.asc


A one figure example can be found within the zip file: FigureAsc.zip
- The pdf for this basic example is here: figureAsc.pdf

A presentation example (using the Latex Beamer class) and making use of LTSpice figures can be found within the zip file: TalkAsc.zip
- The pdf for this presentation example is here: talkAsc.pdf

More Information

For more info, see Documentation