On Wed, 03 Feb 2010 06:47:19 -0500
Ethan Swint <[email protected]> wrote:

> On 02/03/2010 03:33 AM, timecop wrote:
> >> At the very least, it seems that there should be a way to specify that
> >> "any" pin with the same number satisfies the connection. 
> > fairly ridiculous assumption especially with ICs, many of which
> > specifically say something like "all GND/VCC pads must be connected".
> >    
> In which case, the pins have unique numbers, if not names.

I ran into the same thing four times within the last week, just tinkering with 
some old projects:

* A common four-pin SPST momentary button with two pairs of electrically 
connected pins,
* A DB25 connector had its metal metal shield/shell connected to the two 
primary mounting holes,
* A four-pin fuse holder had two pairs of electrically connected pins with the 
fuse between the pairs,
* A DIN connector had its two primary mounting holes electrically connected 
through the shield.

Routing signals through those internal connections would have been no issue at 
all, though I wouldn't have thought to actually do so in the projects in 
question (and adding the extra copper to satisfy the netlist was no big deal).

To that end, if I had to make a suggestion, it would be if the component can't 
handle the possibility of signals flowing through its internal connections 
(unsafe, won't work, etc.), then the footprint should get unique pin numbers 
and the existing policy should apply.

Otherwise, give each of the pins in an electrically-connected set the same 
number, and PCB should simply assume they're electrically equivalent.  PCB 
should also further assume that connecting two such pins together with a copper 
trace does not violate the netlist.

Seems pretty straightforward to me.

("Yeah, that's fine Vanessa, but who's going to write all the code to implement 
it?" :-) )

-- 
"There are some things in life worth obsessing over.  Most
things aren't, and when you learn that, life improves."
http://starbase.globalpc.net/~ezekowitz
Vanessa Ezekowitz <[email protected]>


_______________________________________________
geda-user mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user

Reply via email to