Re: gEDA: gaf - Spice question

["Bas Gieltjes" <S_dot_Gieltjes-at-NOSPAMITS_dot_TUDelft_dot_nl>]

On Tue, 19 Mar 2002, Ales Hvezda wrote:

Hi Chris,

> >I am trying to use the gnetlist -g spice for the first time.
> >
> >I have a schematics with a LM324 and a couple of resistors. When I do 
> >gnetlist -g spice test.sch
> >I get
> >Invalid wanted-pins passed to get-nets [unknown]
> >
> >Anyboy knows what I'm dong wrong ?
> 
> 
> 	I don't think the LM324 is a spice aware symbol.  Basically
> gnetlist is complaining about that.  Or rather the spice backend doesn't
> know what to do with the LM324.  

If the spice backend finds no specific spice component it outputs the
uref, pins and value of a component. The backend determines the amount of
pins (here 5 for the LM324) and then outputs the connected net to each pin. 

The order in which the nets, connected to the pins, get written is pin1,
pin2, pin3, pin4, pin5 (in function spice:write-net-name-of-component).
The strings pin1, pin2, etc. are generated in the backend and are used to
request the net connected to a pin. The spice backend expects that the
order in which the pins are written is hardcoded in the symbol.

The invalid wanted-pin(s) is pin5. In the LM324.sym the fifth pin is
pin11, which is not found. Changing the attribute pin11=11 to pin5=11 is a
solution, the spice backend ignores the <value> which is given to
pin#=<value>. (Please check that pin11 is really the fifth pin that should
be written to the netlist, I have no lm324 spice model to check that)

I am unaware about other netlist backends and there use of pin#=<value>.


 Bas
--