X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <1485622036.3072.141.camel@linetec> Subject: Re: [geda-user] PCB antenna question From: "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Date: Sat, 28 Jan 2017 17:47:16 +0100 In-Reply-To: <20170128150609.8ac62105042db89007e46335@gmail.com> References: <1485607260 DOT 3072 DOT 77 DOT camel AT linetec> <20170128150609 DOT 8ac62105042db89007e46335 AT gmail DOT com> Organization: Linetec Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] schreef op za 28-01-2017 om 15:06 [+0100]: Hello Nicklas, > On Sat, 28 Jan 2017 13:41:00 +0100 > "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" wrote: > > > Lately, I started on projects involving Bluetooth and UHF RF, and for > > simplicity and cost, I'd like to use PCB antennas. [snip] > This is what I found about the footprint format > http://www.ssalewski.de/PcbFootprintRef.txt and there is limitations. Yes, I already found this definition, and from what I see, a PCB footprint element can only contain pins and simple(*) pads as copper items. Lines and arcs are strictly silk screen items. *: rectangular or rounded lines, no polygons etc. [snip] > The source is out there and I guess this would rather simple to check > a flag if object should be not be considered as conductive if we could > just agree about a suitable flag or attribute? Indeed, a sort of "no-net" flag could provide a solution; this flag would signal that the copper item should not be treated as a connection in the netlist. In addition, it would be desirable to include lines, arcs and polygons as copper items within an element. But as it is, PCB doesn't have this functionality. I was hoping there was a work-around for this, but I guess I'll simply leave any PCB antenna connections until last, to avoid getting error messages all the time. And it's not that big a deal -- usually a design contains only one antenna. > > *: A related question: when defining connector footprints, I usually > > define all mechanical metal parts as pin/pad 0. > > What do you mean by mechanical part? I mean any metal parts that aren't functional electrical connections, such as pins and/or fasteners (e.g. screw holes) for mechanically mounting a connector to the PCB. Often, it is desirable or even required to connect these metal parts to a ground plane, which means they must have a netlist entry and thus a defined pin number to avoid error messages. So I usually give these pins/pads the number 0. But come to think about it, this is not a case where the aforementioned "no-net" flag would apply -- because often, several metal mounting pins are interconnected in the connector itself. This means that the actual connection must be recognized as such, contrary to PCB antennas and the likes. So this is a different thing. Best regards, Richard Rasker Linetec -- Linetec Translation and Technology Services Vleerkottelanden 14 7542 MJ Enschede The Netherlands +31-53-4350834 http://www.linetec.nl/ e-mail: rasker AT linetec DOT nl