gEDA-bug: [ geda-Bugs-1529418 ] Odd behavior when shorting nets in a
lower hierarchy sch
SourceForge.net
noreply at sourceforge.net
Wed Jul 26 22:23:26 EDT 2006
Bugs item #1529418, was opened at 2006-07-26 22:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=818426&aid=1529418&group_id=161080
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ales Hvezda (ahvezda)
Assigned to: Nobody/Anonymous (nobody)
Summary: Odd behavior when shorting nets in a lower hierarchy sch
Initial Comment:
If I make a subnet, with a bunch of components in it,
it seems to work alright. However, I also tried to make
a 2-pin subnet containing only a short-circuit. This
connection was completely ignored by gnetlist!!
(originally reported by Arvid Rosén)
Attached are the schematics and symbol.
Here is the output from gnetlist -g geda top.sch
unnamed_net9 : Rload 1, Rtop4 1, Rtop2 2
GND : Rload 2, Vin 2
unnamed_net8 : Rtop3 2, Rtop1 1, Vin 1
unnamed_net4 : Utest/R34 1, Rtop3 1
unnamed_net3 : Utest/R34 2, Rtop4 2
unnamed_net2 : Rtop1 2
unnamed_net1 : Rtop2 1
Ideally the last two nets should be shorted, however
gnetlist is ignoring the net connecting the two in -
out symbols in test.sym.
The workaround is use a zero ohm resistor.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=818426&aid=1529418&group_id=161080
More information about the geda-bug
mailing list