X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 1 Aug 2016 18:45:34 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: "michalwd1979 (michalwd1979 AT o2 DOT pl) [via 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] Wilkinson splitter - how to implement and use? In-Reply-To: Message-ID: References: <23abdc31 DOT 72365e7a DOT 572529a9 DOT 212e2 AT o2 DOT pl> 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 On Mon, 1 Aug 2016, michalwd1979 (michalwd1979 AT o2 DOT pl) [via geda-user AT delorie DOT com] wrote: >Dear Members, > >I need to design a RF board with some Wilkinson splitters on it. While the >symbol of splitter is ready (rf/splitter-1.sym) and for pcb we have even a >java generator >(https://github.com/erichVK5/WilkinsonPowerDividerFootprintGenerator), I'm >not sure how to use it. The splitter is just a few fancy tracks on pcb (plus >a resistor) that in fact are all connected. In schematics however this is an >element with 3 pins. In pcb I can not name the splitter pins "1", "2", "3", >because this will give warnings about shorted nets. If I change schematics >symbol (short its pins) there will be no warnings but all RF nets are >reduced to one - that is not the case (all splitter input/output connections >are lost). > >Is there a better/preferred way to deal with such RF components in gEDA? >Thanks in advance, >Michael Widlok > In pcb-rnd I see an ugly workaround for this: two footprints. One normal footprint with 3 separate terminals, so the netlist can ensure you connect the right things to the right places. Another footprint with a "track drawn of pads" (hack), marked as "nonetlist", placed on top of the first footprint. This would physically connect the three terminals, on copper, but because of the nonetlist flag pcb-rnd would still think there's no connection (DRC-wise). Regards, Igor2