[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-user: pcb:All v. Any pin connectivity
I've just join the list recently and I've also encountered this "problem".
In my view, the current gschem/PCB approach gives all the liberty to the designer although obliges him to take all the decisions. (a bit like spider man, with great power comes great responsibility :-)
I was using IRLD024 for a project, there are actually two pins for the drain, I chose to draw the part in gschem with two available drains and be able to route them on separate nets if needed (could be interesting regarding RFI or even measure if such a small piece of copper/tin could be used).
I you're doing power electronics (or other high speed analog) you'll probably want that power to route any way you like...
JCS
--- On Wed, 3/2/10, geda-user-request@xxxxxxxxxxxxxx <geda-user-request@xxxxxxxxxxxxxx> wrote:
> From: geda-user-request@xxxxxxxxxxxxxx <geda-user-request@xxxxxxxxxxxxxx>
> Subject: geda-user Digest, Vol 45, Issue 8
> To: geda-user@xxxxxxxxxxxxxx
> Date: Wednesday, 3 February, 2010, 18:00
> Send geda-user mailing list
> submissions to
> geda-user@xxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www..seul.org/cgi-bin/mailman/listinfo/geda-user
> or, via email, send a message with subject or body 'help'
> to
> geda-user-request@xxxxxxxxxxxxxx
>
> You can reach the person managing the list at
> geda-user-owner@xxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more
> specific
> than "Re: Contents of geda-user digest..."
>
>
> Today's Topics:
>
> 1. Re: new components (Chris Cole)
> 2. Re: pcb: All v. Any pin connectivity
> (Vanessa Ezekowitz)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 Feb 2010 14:20:13 +0000
> From: Chris Cole <clecol@xxxxxxxxx>
> Subject: Re: gEDA-user: new components
> To: gEDA user mailing list <geda-user@xxxxxxxxxxxxxx>
> Message-ID:
> <5cde7bd51002030620w4117202t89b5d84ea31b7e0@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I must say, I'm extremely impressed by the feedback and
> discussion on this
> mailing list so far; long live FOSS!
> Unfortunately I haven't had a chance to look at all the
> links yet, but
> hopefully I'll be able to work on some stuff tonight. I'm a
> software
> engineer by trade and well versed in Linux development. I
> would be very
> interested in getting involved in gEDA and friends once I
> get more familiar
> with the project. Thanks again for all the help!
>
> Chris
> -------------- next part --------------
> I must say, I'm extremely impressed by
> the feedback and discussion on
> this mailing list so far; long live
> FOSS!
> Unfortunately I haven't had a chance to
> look at all the links yet, but
> hopefully I'll be able to work on some
> stuff tonight. I'm a software
> engineer by trade and well versed in
> Linux development. I would be very
> interested in getting involved in gEDA
> and friends once I get more
> familiar with the project. Thanks again
> for all the help!
> Chris
>
> ------------------------------
>
> Message: 2
> Date: Wed, 3 Feb 2010 09:53:30 -0600
> From: Vanessa Ezekowitz <vanessaezekowitz@xxxxxxxxx>
> Subject: Re: gEDA-user: pcb: All v. Any pin connectivity
> To: geda-user@xxxxxxxxxxxxxx
> Message-ID: <20100203095330.191cb78f@rainbird>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 03 Feb 2010 06:47:19 -0500
> Ethan Swint <eswint..ramu@xxxxxxxxxxx>
> 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 <vanessaezekowitz@xxxxxxxxx>
>
>
> ------------------------------
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
>
> End of geda-user Digest, Vol 45, Issue 8
> ****************************************
>
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user