X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Ironport-SBRS: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2E8AgAzSShW/52AA4BdgzaBQ4JcuzgBDYFZhh0CgT84FAEBAQEBAQEDgQeELwEBBDoxHgsYCRMSDwUNPBOIGwMSBb8vDYRnAQEIAiGGd4R+glCCRIMagRQFh0eGQTuHZIspgW2UXYdNHwEBQoIRHYF1HjSGQwEBAQ X-IronPort-AV: E=Sophos;i="5.20,180,1444719600"; d="scan'208";a="2925535" Date: Wed, 21 Oct 2015 19:30:02 -0700 From: Larry Doolittle To: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] A lesson from gnet-makefile Message-ID: <20151022023002.GA25952@recycle.lbl.gov> References: <73ED29DA-968B-4675-9B00-125E03683C9B AT noqsi DOT com> <201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com> <201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com> <201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Guys -0 On Thu, Oct 22, 2015 at 02:03:43AM +0000, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > On Thu, Oct 22, 2015 at 1:49 AM, DJ Delorie wrote: > > It would be great if you could just connect two > > nets like that and have the system remember the topology long enough > > to DTRT in layout. But in gEDA, this type of connection only results > > in an error. > > Well I was approaching that with the stuff I was talking about in the > other thread but I realized there were fundamental issues with it. > This is kind of why I was thinking about star grounds. Really this is > a type of star topology. I don't think this failing is unique to gEDA. I just had a board laid out in PADS (schematic in gschem), and some analog stuff had to be left hand-wired, non-design-rule-checked, because of this exact issue. Just like in PCB, there seemed to be no way to communicate to the layout tool that two nets are supposed to touch in a defined spot, but be independent. I think it's easy enough to create a "star" component in gschem; getting a layout tool to deal with it seems harder. I've heard of hacks involving extra layers to make it happen in PCB. The team of PADS experts (not sure if a smiley face belongs there or not) couldn't even imagine a way to make it happen for that tool. Other than adding a bunch of zero Ohm resistors, which I rejected. - Larry