Mail Archives: geda-user/2014/06/02/02:17:44
Dear John,
Thanks, this is exactly what I need !
I strongly suggest that your improvements became an integral part of the "regular" gnetlist !
Regards,
Renaud
----- Mail original -----
De: "John Doty" <jpd AT noqsi DOT com>
À: geda-user AT delorie DOT com
Envoyé: Vendredi 30 Mai 2014 22:55:40
Objet: Re: [geda-user] gnetlist question/wish
On May 28, 2014, at 12:42 AM, renaud DOT gaglione AT free DOT fr wrote:
> Dear all,
>
> In order to pruduce netlist usable with ngspice, I use gnetlist with "-g spice-sdb" option.
> But sometimes, I want some device to be present and connected in the schematic (testpoint, connector), but omited by the netlister in case of simulation netlist (but not in case of e.g. PCB manufacturing).
>
> Is there any attribute, in gschem, which would inform the netlister to not include itself in the netlist ?
>
> The reason is that I like have the same schematic for simulation and for manufacturing, and the software I use at work allow this behavior.
My netlist back end at https://github.com/noqsi/gnet-spice-noqsi can do this. It uses a spice-prototype attribute to control SPICE netlisting. An attribute like:
spice-prototype=* ? omitted for simulation
will emit a SPICE comment in place of the component “card”.
It can do a variety of things to make manufacturing schematics usable in SPICE. You can make explicit connections by pinnumber rather than in pinseq order. You can turn hierarchical subcircuits drawn for manufacturing into SPICE subcircuits, and bind pins by pinlabel. It can control prefixing, so you may, for example, use a refdes “L1” for an inductor modeled by a subcircuit, and have “XL1” as its designation for SPICE.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -