X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 18 Feb 2015 10:31:32 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] Star connection points in PCB? (intconn) In-Reply-To: Message-ID: References: <1502170242 DOT AA18887 AT ivan DOT Harhan DOT ORG> <54E354D4 DOT 3040509 AT ecosensory DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 >>> Add a component flag in pcb that tells "there is no short between >>> the pads of this component, even if they overlap!", then draw the >>> actual star out of pads. > > >> I like this because the netlist generated is sane. One sees the >> converging of power nets at a symbol, and that >> symbol can relate to a physical location. > > I like this approach, too. It also kind of resolves the case where a > actual component connects some of its pins internally. This is quite > common with switches and other mechanical components like shielding. I think it does not solve that problem: you'd need the two internally connected pin of the switch to be drawn as overlapping pads so you wouldn't be able to pass a trace on that layer between the pads. What solves it is the opposite: a way to explain pcb that two pads are connected even if they do not seem to be so, PCB-copper-wise. I have such a patch in my fork: http://repo.hu/projects/pcb-rnd/intconn.html you can have multiple groups of internal connections and find.c considers them as real connections. Regards, Igor2