| www.delorie.com/archives/browse.cgi | search |
| 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=googlemail.com; s=20161025; | |
| h=mime-version:in-reply-to:references:from:date:message-id:subject:to; | |
| bh=i8VbXdWZjTBTyJLAplc1vj0MiuijbZOmfqaI7u+n4wU=; | |
| b=PQcYAMjmTvgiB9CtjsKefEMghCfmiWZBbMuQr2E3TZ+dTj39GIGNtIuIezzF+XDQD9 | |
| vq8ronjTSBmjtHB6/sHIS4ViTuO0qICBqNzMqjb0iZneJn4+HRMt3Vf6jpCare+814Yn | |
| V+PO5UD1Du4fjFkaj3lhvHQo9YtGQczhXMcTU2mu1/nWkKQHF8EKFZnM1+4OxNI5H36W | |
| zAc1DM0Z0i3ull0+aFRMdxHW9nj6JBI/rn7YCP03mpiEbcwUHhyMfKlr7sSXCIOiB1Jm | |
| kf8AVgzZ+q4sVzChewtWaaUDMiImvhJWs7A0iTCo3Eoq8WYwBU15SLtb5f8182pyMniN | |
| lZ+A== | |
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
| d=1e100.net; s=20161025; | |
| h=x-gm-message-state:mime-version:in-reply-to:references:from:date | |
| :message-id:subject:to; | |
| bh=i8VbXdWZjTBTyJLAplc1vj0MiuijbZOmfqaI7u+n4wU=; | |
| b=G8ME9Uo0VkIaofRA8KF6CnNpzyurBbeKZ7j6aigGK5JWtNylJvp6Og3Q/Doq1HmBE9 | |
| bdgPD85iJLzzgY1aROIyKeSWWKzufqUVv6Y0mxTcb9TsAxaQIEFCzyRfOzRkYw2K+4LY | |
| Vd8JbbvauDvSNnuEwCPyHOIjddVX2R8RTOmKUwJ5LtHVmlzoZygn58Xcx4sry0T1997O | |
| 5KBHVYIB1FKMyXjbjNjiOLuyLpTdfJ32XqJBnVmOylVm42rVVcC6sJEYpTgmY3lxNles | |
| 9a3vMd7uQVNdo2hVFDObP75OyadJ6MTr2++IHQOzRiblTlJqjoYNgD0Kxe4pfGN3J9J1 | |
| tBvw== | |
| X-Gm-Message-State: | AIkVDXKRsvB4KswR5zx8adD2nXzKcMRc/R5yt7IPb9hZUfxCN7/IYSntUmHaR5Wjm6Lvh6SLDr9i/Aa701Nk7A== |
| X-Received: | by 10.200.56.76 with SMTP id r12mr13659383qtb.2.1485633583150; |
| Sat, 28 Jan 2017 11:59:43 -0800 (PST) | |
| MIME-Version: | 1.0 |
| In-Reply-To: | <1485629830.3072.163.camel@linetec> |
| References: | <1485607260 DOT 3072 DOT 77 DOT camel AT linetec> <CAJXU7q8k4synABy2rOSbjmcarmZ_TONwKxG7ED9f4mP6jAiwJw AT mail DOT gmail DOT com> |
| <1485629830 DOT 3072 DOT 163 DOT camel AT linetec> | |
| From: | "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
| Date: | Sat, 28 Jan 2017 19:59:42 +0000 |
| Message-ID: | <CAJXU7q9GkEOuzakRg3=hU3QVmC_gc=mnsarnUoJfKH3DNwjOcg@mail.gmail.com> |
| Subject: | Re: [geda-user] PCB antenna question |
| To: | gEDA User Mailing List <geda-user AT delorie DOT com> |
| 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 |
--001a1137d9ecfd7b3a05472d052e Content-Type: text/plain; charset=UTF-8 On 28 Jan 2017 19:00, "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote: I also tried approaching the issue from the other side, defining a loop antenna symbol in gschem with pins 1 and 2 already connected through a net (pre-shorted, so to speak). However, PCB doesn't fall for this trick and bluntly keeps flagging this construct as a short, for reasons unknown. Was the net on the schematic page or inside the symbol? (I don't recall whether the netlist would spot the later). If you short the schematic, you might as well make both connection points on the antenna "1" though.... drc won't help you in either case. Anyway, as said it's not a big deal, mostly because designs usually don't have lots of antennas or other special elements made out of copper traces (e.g. inductors or heating areas). Still it would be nice if the functionality for this could be implemented some day. The other classic use (although slightly different) is implementing different net names for signals connecting a star ground. In this case, it isn't some rf or resistive component you instantiate, but a node point. In the antenna case, what you possibly want is copper shape definitions that are explicitly not followed for checking connectivity. (Might need to implement a keep away rule to avoid accidental shorts that could then go undetected). For the pcb resistor / inductors, I guess similar could work - although it is probably desirable to implement within some kind of "footprint" like construct in order to get the end connection points tested as a part of the netlist. Peter --001a1137d9ecfd7b3a05472d052e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma= il_quote">On 28 Jan 2017 19:00, "Richard Rasker (<a href=3D"mailto:ras= ker AT linetec DOT nl">rasker AT linetec DOT nl</a>) [via <a href=3D"mailto:geda-user AT del= orie.com">geda-user AT delorie DOT com</a>]" <<a href=3D"mailto:geda-user@= delorie.com">geda-user AT delorie DOT com</a>> wrote:<blockquote class=3D"quote= " style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I also tried approaching the issue from the other side, defining a loop<br> antenna symbol in gschem with pins 1 and 2 already connected through a<br> net (pre-shorted, so to speak). However, PCB doesn't fall for this tric= k<br> and bluntly keeps flagging this construct as a short, for reasons<br> unknown.<br></blockquote></div></div></div><div dir=3D"auto"><br></div><div= dir=3D"auto">Was the net on the schematic page or inside the symbol? (I do= n't recall whether the netlist would spot the later).</div><div dir=3D"= auto"><br></div><div dir=3D"auto">If you short the schematic, you might as = well make both connection points on the antenna "1" though.... dr= c won't help you in either case.</div><div dir=3D"auto"><br></div><div = dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockqu= ote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p= adding-left:1ex"> Anyway, as said it's not a big deal, mostly because designs usually<br> don't have lots of antennas or other special elements made out of coppe= r<br> traces (e.g. inductors or heating areas). Still it would be nice if the<br> functionality for this could be implemented some day.<br></blockquote></div= ></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">The other classi= c use (although slightly different) is implementing different net names for= signals connecting a star ground. In this case, it isn't some rf or re= sistive component you instantiate, but a node point.</div><div dir=3D"auto"= ><br></div><div dir=3D"auto">In the antenna case, what you possibly want is= copper shape definitions that are explicitly not followed for checking con= nectivity. (Might need to implement a keep away rule to avoid accidental sh= orts that could then go undetected).</div><div dir=3D"auto"><br></div><div = dir=3D"auto">For the pcb resistor / inductors, I guess similar could work -= although it is probably desirable to implement within some kind of "f= ootprint" like construct in order to get the end connection points tes= ted as a part of the netlist.</div><div dir=3D"auto"><br></div><div dir=3D"= auto"><br></div><div dir=3D"auto">Peter</div></div> --001a1137d9ecfd7b3a05472d052e--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |