X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=M1GUdfaQ49IhWZU6SPbo4UV5ku//UcT+Xw28JCVpilw=;
        b=mqC3elnjXB1gbbefMpMEXQK0G3OPpvaoTptgJXk5BvvI8rJK/+Uz7sLHHKd+Gc/9n8
         blcDX9S9AvSgByyztXzjjwZCbzX5jz8295V2v0MfJAZeMDyO2DEhA/EzVUpgi1CSmOhq
         f0NO/F47Yod2/+HEEIDIg2LiUpRurDjRVQOLR6SICyrCQvaScJiesWjOMjn2yTFuGgS9
         khjpGNH1nZE+eN0Gsm7vNpVE7nzRsGnicmshjiRSh4INg27WLEjCNxYI7vMebyzdLjJe
         tTY68F4OeOU6KcbVBzQpLG3EERpreVaElOPv/fxIVXjWWVBCxo9k2qsKbUFSxV0RXdfZ
         Xd0Q==
MIME-Version: 1.0
X-Received: by 10.194.80.137 with SMTP id r9mr8363049wjx.88.1374868861015;
 Fri, 26 Jul 2013 13:01:01 -0700 (PDT)
In-Reply-To: <CAJEG_NfPFgP8qmXtW4u8U6CfotxHGN14QXfUS+-zd4Qy-0e0sg@mail.gmail.com>
References: <CAJEG_Nez8wpC+_sC-MefTvDqvLTJT9TPKwzO5j3fsgiZ9_XR=Q AT mail DOT gmail DOT com>
	<CAJEG_NfPFgP8qmXtW4u8U6CfotxHGN14QXfUS+-zd4Qy-0e0sg AT mail DOT gmail DOT com>
Date: Fri, 26 Jul 2013 16:01:00 -0400
Message-ID: <CA+qhd=9dW=PHHvMFWnrPAHXt0btY31N_6s_JaUQuvyMrdi=YuA@mail.gmail.com>
Subject: Re: [geda-user] Fwd: How do I represent VSS in the schema ?
From: John Luciani <jluciani AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=047d7bdc8e8612de6904e26f9ab9
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

--047d7bdc8e8612de6904e26f9ab9
Content-Type: text/plain; charset=ISO-8859-1

I would make the copper area pin 33.

(* jcl *)


On Fri, Jul 26, 2013 at 3:53 PM, Jorge Ventura <
jorge DOT araujo DOT ventura AT gmail DOT com> wrote:

>
> I am using one component that VSS (gnd) is in the copper area at bottom of
> 32-QFN package and it has no pin number.
>
> How do I handle that to be consistent with PCB ?
>
>


-- 
http://www.wiblocks.com

--047d7bdc8e8612de6904e26f9ab9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I would make the copper area pin 33.<br><br></div>(* =
jcl *)<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">On Fri, Jul 26, 2013 at 3:53 PM, Jorge Ventura <span dir=3D"ltr">&lt;<a =
href=3D"mailto:jorge DOT araujo DOT ventura AT gmail DOT com" target=3D"_blank">jorge.arau=
jo DOT ventura AT gmail DOT com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr">I am using one component that VSS (gnd) is in the copp=
er area at bottom=20
of 32-QFN package and it has no pin number. <br><br>How do I handle=20
that to be consistent with PCB ?</div>
</div><br></div>
</blockquote></div><br><br clear=3D"all"><br>-- <br><a href=3D"http://www.w=
iblocks.com" target=3D"_blank">http://www.wiblocks.com</a> =A0
</div>

--047d7bdc8e8612de6904e26f9ab9--