X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: [geda-user] Parts with internally connected pins
From: Donald Tillman <don AT till DOT com>
In-Reply-To: <CA+uY=MTbF9im-DxJq2n+C3zE=p5FyLohUZ6bmtuCSm85BQi10w@mail.gmail.com>
Date: Fri, 12 Jun 2015 10:14:57 -0700
Message-Id: <EC42E8F3-1598-4FC6-B71A-E50833CF949E@till.com>
References: <B79C9937-FF0D-4301-9569-66E5EA167B03 AT till DOT com> <CA+uY=MTbF9im-DxJq2n+C3zE=p5FyLohUZ6bmtuCSm85BQi10w AT mail DOT gmail DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.2098)
X-Sonic-CAuth: UmFuZG9tSVYf2TPI1DV5WA3eUQuKGRmgFsb6mxVTvuwGpi+yhaK2K0KS4LadXJOM9ybzmWfeEnMHearZEL53R71PDMU8oRZR
X-Sonic-ID: C;vhvVjCYR5RGrAPjYVPtzAg== M;KDgNjSYR5RGrAPjYVPtzAg==
X-Spam-Flag: No
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5CHF4nI025678
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> On Jun 12, 2015, at 8:36 AM, Russell Nelson (russnelson AT gmail DOT com) <geda-user AT delorie DOT com> wrote:
> 
> The problem there is that you could have an "any pin" relationship (as in your example), or an "all pins" relationship as in this example: the 75441 quad H-bridge has four ground pins which are also heat sinks, and which all should be connected to a nice fat ground plane.

Indeed.  And the standard approach in that case is to include all the pin numbers and be explicit in the schematic, "Yea verily, connect each and every one of these pins to ground."

(And that also works for the case of using internally connected pins as a jumper.  'Not recommending that, just pointing out the flexibility.)

But in my case I have the two shield pins on the pot.

One approach would be to include the two shield pins, 4 and 5, in the schematic symbol, and then I could back-annotate which pin that I actually connected.   But man, that seems excessive.  And confusing.

My current approach, giving the shield pins the same pin number in the footprint, isn't bad, the rats nest just complains about missing connections.  And I can add the connections, it's not holding me up.  But I'm wondering if there's an approach that's more preferable, that's more in line with the internals.

  -- Don

--
Don Tillman
Palo Alto, California
don AT till DOT com
http://www.till.com