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

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 tric= k
and bluntly keeps flagging this construct as a short, for reasons
unknown.

Was the net on the schematic page or inside the symbol? (I do= n'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.... dr= c 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 coppe= r
traces (e.g. inductors or heating areas). Still it would be nice if the
functionality for this could be implemented some day.

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.

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).

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.

Peter

--001a1137d9ecfd7b3a05472d052e--