X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [geda-user] Declare a pin as GND in symbol From: John Doty In-Reply-To: <53206871.10800@buffalo.edu> Date: Wed, 12 Mar 2014 10:48:19 -0600 Message-Id: <2BA3CA5A-FEAB-4A2D-9F17-54DE20693A50@noqsi.com> References: <5320667A DOT 6050402 AT buffalo DOT edu> <53206871 DOT 10800 AT buffalo DOT edu> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1085) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s2CLs74E001914 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 On Mar 12, 2014, at 8:00 AM, Stephen R. Besch wrote: > OOPS!! I forgot to mention that there cannot be a pin defined in the symbol file which has the same number at that used in the net=GND:x attribute. I'm not sure what will happen if there is, but I am sure that it is probably undefined. Actually, it's well defined as long as the net connected to the pin has no name. An unnamed net attached to the pin will connect to GND. That's how the "Power Rail" symbols work. However, gnetlist's behavior in case of a short circuit is not well defined, so conflicts between net= and netname= are are problem in general, not just in this case. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com