X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fYO4RVREvSrL20AOgoQL9HhozkgULiXY0WyMQQIYgnw=; b=OO7zZfWj6QxgAZXOqqzmGGNAsgJSbxMFcvdy+pzs2VuwDAx81MXrgiHkGV/6CG/um3 YbxvLNMLGSNhJCA1jc5+ISklcdpK536kbklrt+4veAi0RE8SJ10X4ITyeIlGw/dzJ2L7 +nJmSKhRDCWYIO4FO1TaB/WcSXfXq2NxrZmIIIblJfxnRhZ9kxJ4WHfNc9RqZ8ocBwvc KgP77zrtS9shYNPnoDyVWCgYdmfBEEvKQHzkS24bCL5HG92wjHMy1wHMR5QjNEV/Ik8s UrIrWyYlBpKwkF1WKGgreIxlW4RSsriaaNeRT+F5bJ+8ZjtUuAqoxpuOXw2VNyvXUVYl FXsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fYO4RVREvSrL20AOgoQL9HhozkgULiXY0WyMQQIYgnw=; b=MffPQ1dyjw/TVyifH16WonP+Rlxo/aNYkNJsXN/GuUJkvBpyxzQ2GNjQP0AKCKFjQ6 goFb+EmLAzU4JKflkVXut9JqLZR6dBCubJaojY1fCnyxVjwI4ywdlBiQmT/bX/E2Ju19 oXeqrnvzCCeemnT2CE0c6ojaM76guhuikcnk6jed9BBMZwB7FQ1dDfRR2YWqwRJcX3lP 6pOJJMKdhlRr2Ws7CgwhbW0Bq5G83J1Puvibv36zzmaCy1TDfoQHjY0Fmvewf97iLCBw zaiLkV7BgxB6tG3uDyX+spWyKIDNTNd+dsRWsCqfjeHnh45y+3dF+LFe0YGgJVZI/tg8 zl2A== X-Gm-Message-State: APt69E2TsCujGLzwBKt2T5KL42NzbuF97CA1yAy6nP0UmvAg0odoVV+I clf4dusn8J3ppnQFhcWbcxPpdIa3nSFrvszhGNg= X-Google-Smtp-Source: AAOMgpdLgKgMj9xcKm7GsKvPPZMtevtNgaAJeGJ7deyJ39Zrev3UvNS6qdmCN73RuHW9/xc+LzMJqqspdAqavPI+oaU= X-Received: by 2002:a62:a018:: with SMTP id r24-v6mr27269406pfe.144.1531256050918; Tue, 10 Jul 2018 13:54:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <04df2ed2-45a1-dff5-6f6c-d9b9d5fcca0f AT neurotica DOT com> From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Tue, 10 Jul 2018 16:54:10 -0400 Message-ID: Subject: Re: [geda-user] shorted pads and the netlist in PCB To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary="000000000000f9a8fc0570ab5426" 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 --000000000000f9a8fc0570ab5426 Content-Type: text/plain; charset="UTF-8" The only way that pcb can know your intent for that pin is for you to tell it, in one way or another. So, if you're not going to use a symbol in gschem that has that pin, then you're going to have to explicitly tell pcb what you want, somehow. One way to do this is to edit the netlist and manually to add the pin in question. If there's another ground pin on the package, I believe you can assign the same pin number to both footprint pads, and then the existing netlist doesn't have to be altered. This method does require you to edit the footprint. You can also manually draw the ground net yourself by selecting the "rat lines" layer and using the line tool to connect the extra pin to something with the desired net. The netlist is saved in the pcb file, however, it is not saved to the external netlist file generated from the schematic. So, if you choose this method, and you have to later make schematic changes that require you to reload the netlist, the change will not persist. Do any of these options solve your problem? Thanks, --Chad On Tue, Jul 10, 2018 at 4:00 PM, Marvin Dickens (mpdickens AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > Well, I am not a unicorn... > > This bug has been around for over a *decade* and has been one of the deal > breakers for us. > A solid net list is required when bringing up non-trivial boards for the > first time and later during DUT > after engineering changes / repair. > > Unless you are a one man shop, a defective net list that has to be > massaged in order to be > reliable will always suspect. > > > Regards > > Marvin > --000000000000f9a8fc0570ab5426 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The only way that pcb can know your intent for that p= in is for you to tell it, in one way or another. So, if you're not goin= g to use a symbol in gschem that has that pin, then you're going to hav= e to explicitly tell pcb what you want, somehow.

O= ne way to do this is to edit the netlist and manually to add the pin in que= stion.

If there's another ground pin on th= e package, I believe you can assign the same pin number to both footprint p= ads, and then the existing netlist doesn't have to be altered. This met= hod does require you to edit the footprint.

Yo= u can also manually draw the ground net yourself by selecting the "rat= lines" layer and using the line tool to connect the extra pin to some= thing with the desired net. The netlist is saved in the pcb file, however, = it is not saved to the external netlist file generated from the schematic. = So, if you choose this method, and you have to later make schematic changes= that require you to reload the netlist, the change will not persist.

Do any of these options solve your problem?

Thanks,
--Chad


On Tue, Jul 10,= 2018 at 4:00 PM, Marvin Dickens (mp= dickens AT gmail DOT com) [via geda-u= ser AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Well, I am not a unicor= n...

This bug has been around for over a *decade* and h= as been one of the deal breakers for us.
A solid net list is requir= ed when bringing up non-trivial boards for the first time and later during = DUT
after engineering changes / repair.=C2=A0

Unless you are a one man shop, a defective net list that has to be ma= ssaged in order to be=C2=A0
reliable will always suspect.


Regards

Marvin

--000000000000f9a8fc0570ab5426--