Re: gEDA-dev: Pinning down libgeda

[al davis <ad136-at-NOSPAMfreeelectron_dot_net>]

On Thursday 22 February 2007 22:57, Dan McMahill wrote:
> Something left off of this list which I think is important is
> that in the current system, nets don't have names in gschem
> unless you name them explicitly.  The unnamed nets get
> assigned names at netlist time by gnetlist.  This makes it a
> bit of a pain I think to then use the schematic to drive a
> waveform viewer.  In other words, how can I click on a net
> and press "plot it" if the schematic tool doesn't know what
> that net is called in the netlist (and hence in the simulator
> output).

The same way the netlister makes all connections.

You put a probe on your schematic, with connections.  The 
netlister converts it to an appropriate circuit element, with 
the syntax the simulator understands.

You just made me think of something for gnucap ...  with the 
conversion to Verilog format (with VHDL not far behind), no 
longer stuck with the Spice legacy of the dot print and dot 
plot ...  There is a new way ..  A probe is a circuit element, 
with connections and attributes.  Either Verilog or VHDL syntax 
supports it perfectly.

resistor #(10k) r1 (in, out);
capacitor #(10n) c1 (out, gnd);
generator g1 (in, gnd);
tranprobe  tp1 (out, gnd);
tranprobe  tp2 (in, gnd); 

...
etc.

tranprobe is just an element.
In this case, you have 2 probes: tp1 and tp2.  That is what you 
will see on the gwave menu.

tranprobe is a plugin.  The code for it can be written in 
verilog, VHDL, C++, Spice, C, Fortran, ....

You solved a problem for me by asking the right question at the 
right time.

Before, I was thinking it needs a plot COMMAND.  NO!!  It needs 
a plot ELEMENT.  Maybe I can call it "oscilloscope".




_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev