X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=gxxM3sMyz3t+alB+PSG1jl3Jb5bjLvV3/+mRNAGUSHo=; b=qYE+v1LVZin+CVjGE7RqQ/nicbvGQ+kUpXQnU1Dx43DvY286w50fgiKnf2Mx9vV26d miC6l/+drrKAOo28U20Nck2SgBJTCAI6uZG5JXbbxHEV/5fhzfDE5oDry6NM179bI8Gb gWmnBKluec6xav6jvSqItMgRN3Gv1aMM8WjtLAERCVHt0+I/zSCTho+ZKBqnvGSXkS/y nfTyEQE/wT5d9PvZsr4hl4R80QktfqJe2xswzSV8npavqA8zfxh5xX7LMX6bVWw+Fbty e7KVmTCL0P/U7mOH0adoLJBYfjJSnQ0xGGPkpWKb3sv0pTqrSGiU+vDDbHxpc+kFUA84 0N8Q== MIME-Version: 1.0 X-Received: by 10.49.127.199 with SMTP id ni7mr10662334qeb.17.1360814381708; Wed, 13 Feb 2013 19:59:41 -0800 (PST) In-Reply-To: References:

Date: Wed, 13 Feb 2013 19:59:41 -0800 Message-ID: Subject: Re: [geda-user] gnetlist extractor From: "bsalinux AT gmail DOT com" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7b6dcbd6d3b52304d5a749a6 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --047d7b6dcbd6d3b52304d5a749a6 Content-Type: text/plain; charset=ISO-8859-1 Thanks John, Would that mean I should be using 4 terminal MOSFETS and join the source to substrate? I'll try that with spice-sdb extractor. On GNUCAP list I was suggested to use a plugin for gnucap for gEDA. I just wanted to fixate my workflow so that I know what to do. I'm just getting my feet wet on gnucap and ngspice. Thanks for your suggestions. On Wed, Feb 13, 2013 at 3:39 PM, John Doty wrote: > > On Feb 12, 2013, at 10:31 PM, bsalinux AT gmail DOT com wrote: > > > Hello, > > > > Is gnetlist extractor part of gEDA? > > Yes. There are two gnetlist back ends for SPICE that are part of gEDA: > "spice" and "spice-sdb". There is some pretty good documentation on > spice-sdb at http://www.brorson.com/gEDA/SPICE/intro.html. > > I have an experimental SPICE back end under development at > https://github.com/noqsi/gnet-spice-noqsi. > > > Are there any other extractors available? > > Not that I know of. > > > > > I tried to do a gnucap simulation involving BS170 MOSFET and the > > extractor did not extract / interpret four contacts for the MOSFET as > > expected by GNUCAP. > > > > What was extracted was: > > > > M1 4 1 0 bs170 > > > > instead of (substrate connected to source) > > > > M1 4 1 0 0 bs170 > > The "spice" and "spice-sdb" back ends assume that the SPICE device has the > same number of connections as the symbol, so if you use a three terminal > symbol, you'll get the result you're seeing. One way to get around this is > to have the model-name attribute refer to a three terminal subcircuit in > which the four terminal primitive device is embedded. Be sure to use a > refdes starting with "X" in this case. Or you can use a four terminal > symbol. > > My spice-noqsi back end is more flexible, with a spice-prototype attribute > that you can attach to a symbol to give the netlister more detailed > instructions. For the nmos-3 symbol, you could use use "spice-prototype=M? > #D #G #S #S bs170". > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > > --047d7b6dcbd6d3b52304d5a749a6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Thanks John,

Would that m= ean I should be using 4 terminal MOSFETS and join the source to substrate?<= br>

I'll try that with spice-sdb extractor.

On GNUCAP list I was suggested to use a plugin for gnucap for gEDA.

=

I just wanted to fixate my workflow so that I know what to do. I'= m just getting my feet wet on gnucap and ngspice.

Thanks for y= our suggestions.

On = Wed, Feb 13, 2013 at 3:39 PM, John Doty <jpd AT noqsi DOT com> wrote:

On Feb 12, 2013, at 10:31 PM, bsalinu= x AT gmail DOT com wrote:

> Hello,
>
> Is gnetlist extractor part of gEDA?

Yes. There are two gnetlist back ends for SPICE that are part of gEDA= : "spice" and "spice-sdb". There is some pretty good do= cumentation on spice-sdb at http://www.brorson.com/gEDA/SPICE/intro.html.

I have an experimental SPICE back end under development at https://github.com/= noqsi/gnet-spice-noqsi.

> Are there any other extractors available?

Not that I know of.

>
> I tried to do a gnucap simulation involving BS170 MOSFET and the
> extractor did not extract / interpret four contacts for the MOSFET as<= br> > expected by GNUCAP.
>
> What was extracted was:
>
> M1 =A04 1 0 bs170
>
> instead of (substrate connected to source)
>
> M1 =A04 1 0 0 bs170

The "spice" and "spice-sdb" back ends assume that= the SPICE device has the same number of connections as the symbol, so if y= ou use a three terminal symbol, you'll get the result you're seeing= . One way to get around this is to have the model-name attribute refer to a= three terminal subcircuit in which the four terminal primitive device is e= mbedded. Be sure to use a refdes starting with "X" in this case. = Or you can use a four terminal symbol.

My spice-noqsi back end is more flexible, with a spice-prototype attribute = that you can attach to a symbol to give the netlister more detailed instruc= tions. For the nmos-3 symbol, you could use use "spice-prototype=3DM? = #D #G #S #S bs170".

John Doty =A0 =A0 =A0 =A0 =A0 =A0 =A0Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com

--047d7b6dcbd6d3b52304d5a749a6--