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: multipart/signed; boundary="Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Pin mapping (separate symbols from mappings) X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: Date: Fri, 23 Oct 2015 08:42:34 -0600 Message-Id: References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com> <36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com> <201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com> <20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com> <201510190242 DOT t9J2gl7w009345 AT envy DOT delorie DOT com> <20151019092555 DOT 46eed4540c2d2044bbeab878 AT gmail DOT com> <1A419AED-FCCA-4B1F-8589-912435534E2E AT noqsi DOT com> <201510191647 DOT t9JGlu4j024585 AT envy DOT delorie DOT com> <041FF42A-691F-4E6B-9DEB-8C6B3C2F3E53 AT noqsi DOT com> <201510191850 DOT t9JIop8Y029095 AT envy DOT delorie DOT com> <201510192055 DOT t9JKt2o6005861 AT envy DOT delorie DOT com> <1E816300-E31E-4B85-B51D-7EAEC5A466BF AT noqsi DOT com> <201510192110 DOT t9JLAFKG007281 AT envy DOT delorie DOT com> <201510192340 DOT t9JNeo6n020302 AT envy DOT delorie DOT com>

<1EBD978A-B82E-4DB0-B420-20D3A63D3324 AT noqsi DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3 Content-Type: multipart/alternative; boundary="Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6" --Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Oct 23, 2015, at 2:29 AM, Carlos Nieves (cnieves DOT mail AT gmail DOT com) [via = geda-user AT delorie DOT com] wrote: >=20 > I=92m thinking about a bottom-up approach to detecting missing slot = assignments and missing parts of split symbols. The standard gEDA = footprint names are pretty good for this purpose, as they encode the pin = count in a regular way. Some of the symbols in the gEDA library also = have pins=3D attributes. Since I export to Allegro, and it expects the = netlister to tell it how many pins the footprint is expected to have, I = have to deal with this anyway. So, count pins and verify that the right = number are present. >=20 > The main problem with that is that it's only valid for PCB workflow, = and depends on the footprint names... ;) It doesn=92t depend on footprint names: the approach I=92m using for = Allegro looks for a pins=3D attribute, and only tries to deduce pin = count from the footprint if that=92s absent. Of course, a DRC version = might want to check that the footprint matches, if present. A peripheral, optional tool like a specialized DRC script doesn=92t have = to cover every possibility. It need only be applicable to the flows for = which it makes sense. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

On Oct 23, 2015, at 2:29 AM, Carlos = Nieves (cnieves DOT mail AT gmail DOT com) [via = geda-user AT delorie DOT com] = <geda-user AT delorie DOT com>= wrote:

I=92m thinking = about a bottom-up approach to detecting missing slot assignments and = missing parts of split symbols. The standard gEDA footprint names are = pretty good for this purpose, as they encode the pin count in a regular = way. Some of the symbols in the gEDA library also have pins=3D = attributes. Since I export to Allegro, and it expects the netlister to = tell it how many pins the footprint is expected to have, I have to deal = with this anyway. So, count pins and verify that the right number are = present.

The = main problem with that is that it's only valid for PCB workflow, and = depends on the footprint names... = ;)

It doesn=92t depend on footprint = names: the approach I=92m using for Allegro looks for a pins=3D = attribute, and only tries to deduce pin count from the footprint if = that=92s absent. Of course, a DRC version might want to check that the = footprint matches, if present.

A peripheral, = optional tool like a specialized DRC script doesn=92t have to cover = every possibility. It need only be applicable to the flows for which it = makes sense.

John Doty Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6-- --Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWKkdbAAoJEF1Aj/0UKykRrL0P/jMEHElFBnGEgj432jOrG72O X945m2Y0oKdGnjs1SUwcSQHr7slqDdlNjMUcPhj5S85CTHKbqI4GhxfDBTnDlLs7 vwup+AT5OyyL9mVYv/j+jAj/wJOhtIpRX7l21/QnCfYHt+WUBccI1T9G2RjH7eLP k2vFRYpgyg6qWSqEHyR2q6RZSBZp/xKfRHKHsO35ybUP+8fdfQMnhB3LRY5uuYiR cRSOxNrDjyT1Z/Qu9ppnLNJBfSSSMfS6kU4NJhGey2ILD+KG35SMXXaKksoMmZWa +qXIL0S/rmhlNgWOsgxAT9lyPg3suW1guL0f+AWeBso1+P1qaEvoDwoJ9PQeZeev UJieFZ79nfJbBL8xZ47b2u7DyB/wOo59RKo+rQ4EtMf6mG4GetWSXjouICUSSPh4 ZXQXoAV8dpVM3OR3fNTtRghtyUh/p49S6KYySsMKQUpDfUsTJHgAb2jeBhNUQO+s uHPxudn22kewCbwbJObQzc1PUpaI9RRDkJ3eHBtU3d46SIEfoXGMINzjrY1M7sPI qN7nZaWKBXDEX0KJlOJ5YmNinC+bY0vcCIHzXF/8J2ct6hCVRQkG6aYtKQQ+mBk5 y7Ys8UiE90TOEJBgB2Jv6wRTXTzdk04PNYiLG72x9Zeoc0JTo5+iIRXQhqUv8ifg CxCvc1HNP+X0o77YqEd9 =e5wK -----END PGP SIGNATURE----- --Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3--