Mail Archives: geda-user/2015/10/18/19:44:17
--Apple-Mail=_0DA31B3B-2C1D-459A-B2F6-D6BE6246191D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On Oct 18, 2015, at 5:24 PM, Nicklas Karlsson =
(nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] =
<geda-user AT delorie DOT com> wrote:
>> On Oct 18, 2015, at 4:38 PM, Nicklas Karlsson =
(nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] =
<geda-user AT delorie DOT com> wrote:
>>=20
>>>>> In my opinion, geda-gaf must remain neutral with respect to the
>>>>> specifics of the downstream flow.
>>>>=20
>>>> If we added a tool that sat between gschem and <downstream> that
>>>> "heavified" symbols, would that tool be part of geda-gaf and thus =
have
>>>> to be neutral about <downstream>, or would that tool not be, and =
thus
>>>> something geda-gaf would have to be neutral about?
>>>=20
>>> It depends on if there need to be feedback. I guess manufacturer =
part number do not need feed back. Revision number from for example =
subversion or other would however be useful. Pin numbers?
>>>=20
>>=20
>> Feedback is perfectly reasonable if done in a tool-neutral way. For =
manual topology feedback from Osmond PCB, I have a script that compares =
the gnetlist output with the Osmond as-built netlist. If we defined a =
format for importing this data into geda-gaf, each downstream flow could =
provide such a script.
>>=20
>> One geda-gaf issue is that the fundamental pin ID is =
refdes/pinnumber, confused a bit by slotting. That would be very hard to =
change, but I think mapping (original refdes)/(original pinnumber) to =
(as-built refdes)/(as-built pinnumber) is possible.
>>=20
>> John Doty Noqsi Aerospace, Ltd.
>> http://www.noqsi.com/
>> jpd AT noqsi DOT com
>=20
> Gnetlist can generate a netlist from a *.sch file. A tool running the =
other direction from netlist to gschem should also be posibble, this =
tool can also do the pin mapping if this is a suitable method to solve =
the problem. If there are no synchronization problem to update the *.sch =
file while it is open in gschem this could be a suitable method.
If you want to work backward. But for me, it makes more sense to work =
forward: (ideal schematic)->(layout)->(as-built schematic).
>=20
> Nicklas Karlsson
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_0DA31B3B-2C1D-459A-B2F6-D6BE6246191D
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
iQIcBAEBCgAGBQJWJC64AAoJEF1Aj/0UKykRUbwP/1q/50w28Yp/YW8aZz2xaGb8
Vzwp9j76dKBPPKIOMjqAKLGj4FjFwERscAljqGKbfW8G6sdKKs0tacocAUh6Vo5/
Vu7WTsKykbhxU7Bg+fJ5kF0oEzaNqJaJywa1uwl1VMfQ48lZfT9gRxEMv+j1Cdx4
rOadxwrcx3L3oRtVcZ4//5Oh0DSJDH03K07rTg0aiyyvAznLiMU9b8yKkAoV3pj/
XZuSQJpnpPcp3klPDiT+7rfWp3TIhYoujZWqZU4kf7TiFTiFS44OwPrsN7v/OZU1
Ho0sZN/fAi4e43ACFOp6CK9PY6cJjRx2HPX+wV1ygyxUTyGYYPMJfuv2yE5ATxIJ
GX41Rf+Es4dK5NWKW88SwasdkKrSGRi78V2MoCTxITYLSLDWyCslXy4jm7SpixXh
L3EQdccRhaPrVcQxFzp20NjGitLVD8X14VqWW4q61fnOnKM0KHpwOF9vh4RnnaCI
rbh9/0ifvENK6pdXI/3FZn1YP85el5Doi1fyeLQkfh7eA8tRyHrXFVofzuYA3p6Z
Bouo+qXcNsHCEW9vRrni2IUjswo0avxFZrqNB2oeILUjvCKUztbZL7nY74qDIX65
y/VI7QwcXZcc6XvakUKw6otI0vh+74kwYUjrAGaeJn9yXEuLRnzLtPnA6Kxgvl0M
IPMTpGKykunZvcBSpQLf
=7y1+
-----END PGP SIGNATURE-----
--Apple-Mail=_0DA31B3B-2C1D-459A-B2F6-D6BE6246191D--
- Raw text -