Re: shunt trouble

On Sun, 26 Jun 2016 01:11:48 +0000 (UTC)
Sherman <[email protected]> wrote:
> > out2 is not as expected : AND(sel=0, notsel=5) = 5 !

It is correct with the current version.

That original post was 6 years ago.  A lot has changed since then.


> gspiceui, with ngspice, and gnucap or ngspice, and gnucap stand alone. The
> applications have simulation problems where semiconductor devices parameters
> aren't defined properly. I have been successful at simulating devices with
> only capacitors inductors and resistors. I have also not been able to find
> any references of libraries containing semiconductor devices parameters
> useful to bypass the simulation problems. I did find one article and have
> since lost track of it that mentions parameters within the semiconductors'
> netlist must be removed in order to get simulation results. gnucap simply
> displays: #nucap         0.35 and ngspice simply displays messages where it
> asks; "What is this?". These errors occur while using "QUCS". The linux
> application "Electric" is what gave me the proof of problems occurring with
>  gspiceui, with ngspice, and gnucap or ngspice, and gnucap stand alone. I
> simulated a device using only capacitors inductors and resistors, and as I
> placed a single diode within the device, it ceased simulation with the above
> mentioned results.  
> 

The circuit works for me.

al@floyd:/tmp>gnucap -b z
Gnucap : The Gnu Circuit Analysis Package
Never trust any version less than 1.0
Copyright 1982-2013, Albert Davis
Gnucap comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome
to redistribute it under the terms of 
the GNU General Public License, version 3 or later.
See the file "COPYING" for details.
main version: unstable 2016.05.25
core-lib version: unstable 2016.05.25
default plugins: unstable 2016.05.25
GnuCap File : circuit description 
UAND1: can't find subckt: cmosand2, forcing digital
UINV: can't find subckt: cmosinv1, forcing digital
UAND2: can't find subckt: cmosand2, forcing digital
#Time       V(in)      V(out1)    V(sel)     V(notsel)  V(out2)   
 0.         0.         0.         0.         5.         0.        
 1.u        0.         0.         0.         5.         0.        
 2.u        0.         0.         0.         5.         0.        
 3.u        0.         0.         0.         5.         0.        
 4.u        0.         0.         0.         5.         0.        
 5.u        0.         0.         0.         5.         0.        
 100.u      0.         0.         0.         5.         0.        





It is not clear what is the best way to handle unrecognized
parameters.  How it is handled in gnucap depends on the device.