SPICE Netlists #

Everything on the breadboard is a SPICE netlist — Breadpad generates it from your placed parts, and you can always drop down to the text.

The SPICE Shell #

Open SPICE Shell from the oscilloscope menu to see the current breadboard’s full netlist in a syntax-aware editor. Node names follow the board: GND, VCC1, VCC2 for the rails, and column-based names for the signal strips.

• Run executes the netlist and opens the results charts.
• Export saves the text as a standalone .spice file.
• Edits here are a scratchpad for experiments — they don’t modify the breadboard.

.spice documents #

New Netlist on the launch screen creates a standalone SPICE document — no breadboard, just text plus Run. Dozens of bundled netlist examples (filters, oscillators, an entire AM radio) open the same way. .spice files made elsewhere open directly.

Plot commands drive the charts #

If a netlist contains plot, .plot, or .print commands, Breadpad reads them to pre-select which vectors the results chart shows:

.tran 10u 5m
plot v(in) v(out)

opens the chart with v(in) and v(out) already selected; every other vector remains available to toggle on.

Notes on Breadpad’s ngspice #

• Analyses run in batch mode. Use standard dot-cards (.tran, .ac, .dc, .op) or a .control block; inside .control, use run to execute the deck’s analysis cards.
• All eight XSPICE code-model families are loaded, so digital primitives (d_nand, …), analog behavioral models, and table models all work.
• The full syntax accepted is documented in the SPICE Reference.