No, I took it from the "power" category and modified to permit changing the net name. Here's an embedded example from my schematic:
C 21000 17300 1 0 0 EMBEDDEDFrameGnd.sym
[
P 21200 17400 21200 17500 1 0 1
{
T 21258 17461 5 4 0 1 0 0 1
pinnumber=1
T 21258 17461 5 4 0 0 0 0 1
pinseq=1
}
L 21100 17400 21300 17400 3 0 0 0 -1 -1
L 21300 17400 21245 17350 3 0 0 0 -1 -1
L 21200 17400 21145 17350 3 0 0 0 -1 -1
L 21100 17400 21045 17350 3 0 0 0 -1 -1
T 21000 17200 5 8 1 1 0 0 1
net=RFGND:1
]
I guess what annoys me is that gnetlist is trying to tell me something by listing a part as "U?", but it doesn't tell me what's causing that anomaly. Typically, the geda tools will emit something usable in response to bad input data, but not this time, I guess. I'd be happy with a line number of the source file.
Marshall
-----Original Message-----
From: owner-geda-user@xxxxxxxx on behalf of John Doty
Sent: Sat 1/7/2006 1:53 PM
To: geda-user@xxxxxxxx
Subject: Re: gEDA-user: gnetlist finding "U?"
Which symbol are you using for ground? DO NOT use ground.sym from the
IEC417 library: it doesn't have proper attributes.
In fact, *never* use anything from the IEC417 library in a circuit.
It's only good for abridged diagrams in documents. The "pins"
generally represent ports, not node connections. Dangerous to newbies
to have it in the standard distribution...
<<winmail.dat>>