X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=LBAcKyW6h+lYRvkiBbE7mahflc1b8Fg8r8T+nBhunp4=; b=qRGNd6YZBzcPpS8MI/lVpEZjCSqSYevgJocy+c9cElExYclFLnS6+NVJo32BN/wq7g 225GQTg+zVObOe2cDZei3b7d31YcwsNQUWtmQlgwH9MiW8GaH3/rKZ7ONRCgRRub/ER+ CJS/BlMg5TAEL2lDMXVhmW2Byci0Bv4lzbM1e6+x8qY8upcLM/3ePH4zlXMppC/3FpnD hLVJATvbf+bwQ6ZajNuO08zm6Yq9U8m+pBZSFLtb0vRM797nA9RGbR2B2dm89lyYZ1uv PhqcMkkasLlAHYnRElRPugbJolYD5f9Tg2QaM9a6bG8iTdjIboOaC+O4+ild/l9wTc/M bZKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=LBAcKyW6h+lYRvkiBbE7mahflc1b8Fg8r8T+nBhunp4=; b=SdNcP4b5GI0OJDF6+OkA8q7QaZSD3HqRxLAFO23aBGnmJlXskjy3POWmSYYJx2eJKU elpi5orwBJPaGQIcDGuwxZymB18k3dPrZYcp6mVWUXgCAvjR5/sbgVQQ/F+2BDEPJf+6 nERJSsJpvBWv9HqJmg+zdJvH84eKk+BXuVEXFzM4SBtZq0lBdpMca8s2twe1D6l/knLs zF1JE9AnX0r0Gp5vYBFPE7Wqno1c2yusHI7/9Cvc/Yj/Jxu9SKJ4t82kka7a6/H8GHfz +GG8Et+r8vOF77GSSZBBhiOOoQiY3JBg7Q2H2+HEdPAW4UMpcmxd97XXNU8yTeCrjHfe fS/g== X-Gm-Message-State: AEkooutTlWiTgnw1wRS+50SB69UjkHvgK6DJBzQiQ9xBJ20GxqBHvMwK5y3bSNlv8MSkrQ== X-Received: by 10.28.230.205 with SMTP id e74mr59518287wmi.42.1470069937488; Mon, 01 Aug 2016 09:45:37 -0700 (PDT) Date: Mon, 1 Aug 2016 18:45:35 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Wilkinson splitter - how to implement and use? Message-Id: <20160801184535.c7d91c0a53821351e0af0148@gmail.com> In-Reply-To: References: <23abdc31 DOT 72365e7a DOT 572529a9 DOT 212e2 AT o2 DOT pl> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 There is no way to deal with such RF components in gEDA. pcb check for connectivity by checking which drawing primitives on copper layer overlap and there is nothing wrong with this method. With flag to mark the drawing primitives connecting the pins within the radio component this could be solved. I have started to look on clearance values between nets but there have been a long time now because I am busy with other tasks and I will not have time implement it even though I expect to be rather straight forward it there is a possibility to add a flag or other kind of attribute. On Mon, 1 Aug 2016 15:53:23 "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 github.com (https://github.com/erichVK5/W ), 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 > > > > > Dnia 1 maja 2016 00:06 michalwd1979 (michalwd1979 AT o2 DOT pl) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> napisał(a): > > > > > > Hello, Long time ago I remember playing around with a patch that added thermals to SMD pads. There were a few issues with it, however during normal work I figured out that in fact the most usable (maybe not only for me) thermals for pads are "solid" - the same as setting clearance to 0. Problem with just setting clearance to 0 is when You want to change clearance to a part of board (by selecting objects and doing :changeclearsize(selected, xx, mm/mil)) is that this breaks Yours connected pads also. Stripped version for this patch that supports only "solid" thermals for pads is just a few lines of code (just tested it pcb opengl version). My question: Do You think that adding it to mainline might be a good idea? If You want to use it OK, if not it does not breaks anything. Best Regards, Michael Widlok