Mail Archives: geda-user/2016/01/19/11:20:24
--Apple-Mail=_8E56BE8D-CA49-4336-BAC1-E16D0F45DBED
Content-Type: multipart/alternative;
boundary="Apple-Mail=_E0308476-0CE9-48C0-BEAE-47A0BEABB6DA"
--Apple-Mail=_E0308476-0CE9-48C0-BEAE-47A0BEABB6DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Jan 19, 2016, at 8:53 AM, Peter Clifton =
(petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] =
<geda-user AT delorie DOT com> wrote:
> Really you need to have a reuse at the schematic level before you can =
expect any intelligent behaviour in the pcb tool.
>=20
> I've done multi channel designs with hierarchical schematics before... =
The rename just becomes X1/R1 -> X2/R1 etc...
>=20
> My rename plugin might still be floating about somewhere =
"sedrename"... Now we've got more plugins committed with the main =
repository, it might be fun to dig that one out and include it too... =
Was very handy when your transformation between channels can be =
expressed as a regex.
>=20
> The main downside with heirarchical refdes is the silkscreen and board =
fab house. They HATED IT. Couldn't cope with the long heirarchical =
refdes, didn't WANT to cope with the patch I applied to just put the =
last heirarchical part on the silk by each part, but then drew boxes =
manually with module designations.
>=20
>=20
The printed circuit culture is a little behind the times. With some =
gnetlistrc/Makefile work, you can make hierachical netlists from gschem =
schematics. They=92re useful if you=92re doing ASIC design, but you get =
various downstream issues if you want printed circuits.
> In the end, I used pcb's renumber feature to assign completely new =
refdes on the board, but instead of back annotating (impossible as we =
stand, with heirarchical schematics),I added a quick kludgy patch to =
read back in the rename file, so pcb could map between the gnetlist =
produced heirarchical netlist, and the flat refdes on the board.
>=20
> Made debugging extra fun, having to manually indirect from =
heirarchical schematic refdes to on board refdes, but at least it didn't =
upset the board assembly fab!
>=20
> I suppose I could also have post proceed out a flattened set of =
schematics with the renamed refdes if that became useful.
>=20
>=20
Existing capability. You can flatten schematics with =
https://github.com/xcthulhu/lambda-geda, and then edit the refdeses with =
textutils. Or you can use one of the refdes renumberers kicking around =
after flatten.
> Peter
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_E0308476-0CE9-48C0-BEAE-47A0BEABB6DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Jan 19, 2016, at 8:53 AM, Peter =
Clifton (<a =
href=3D"mailto:petercjclifton AT googlemail DOT com">petercjclifton AT googlemail DOT co=
m</a>) [via <a =
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <<a =
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><p dir=3D"ltr">Really you need to have a reuse at the =
schematic level before you can expect any intelligent behaviour in the =
pcb tool. </p><p dir=3D"ltr">I've done multi channel designs with =
hierarchical schematics before... The rename just becomes X1/R1 -> =
X2/R1 etc...</p><p dir=3D"ltr">My rename plugin might still be floating =
about somewhere "sedrename"... Now we've got more plugins committed with =
the main repository, it might be fun to dig that one out and include it =
too... Was very handy when your transformation between channels can be =
expressed as a regex.</p><p dir=3D"ltr">The main downside with =
heirarchical refdes is the silkscreen and board fab house. They HATED =
IT. Couldn't cope with the long heirarchical refdes, didn't WANT to cope =
with the patch I applied to just put the last heirarchical part on the =
silk by each part, but then drew boxes manually with module =
designations.</p><div><br></div></blockquote><div><br></div>The printed =
circuit culture is a little behind the times. With some =
gnetlistrc/Makefile work, you can make hierachical netlists from gschem =
schematics. They=92re useful if you=92re doing ASIC design, but you get =
various downstream issues if you want printed circuits.<br><blockquote =
type=3D"cite"><p dir=3D"ltr">In the end, I used pcb's renumber feature =
to assign completely new refdes on the board, but instead of back =
annotating (impossible as we stand, with heirarchical schematics),I =
added a quick kludgy patch to read back in the rename file, so pcb could =
map between the gnetlist produced heirarchical netlist, and the flat =
refdes on the board.</p></blockquote><blockquote type=3D"cite"><p =
dir=3D"ltr">Made debugging extra fun, having to manually indirect from =
heirarchical schematic refdes to on board refdes, but at least it didn't =
upset the board assembly fab!</p><p dir=3D"ltr">I suppose I could also =
have post proceed out a flattened set of schematics with the renamed =
refdes if that became =
useful.</p><div><br></div></blockquote><div><br></div><div>Existing =
capability. You can flatten schematics with <a =
href=3D"https://github.com/xcthulhu/lambda-geda">https://github.com/xcthul=
hu/lambda-geda</a>, and then edit the refdeses with textutils. Or you =
can use one of the refdes renumberers kicking around after =
flatten.</div><blockquote type=3D"cite"></blockquote><blockquote =
type=3D"cite"><p dir=3D"ltr">Peter</p>
</blockquote></div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><p style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">John =
Doty<span class=3D"Apple-converted-space"> =
<span class=3D"Apple-converted-space"> </span><span =
class=3D"Apple-converted-tab"> <span =
class=3D"Apple-converted-space"> </span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><a href=3D"http://www.noqsi.com/">http://www.noqsi.com/</a></p><p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"mailto:jpd AT noqsi DOT com">jpd AT noqsi DOT com</a></font></p><br =
class=3D"Apple-interchange-newline"></span>
</div>
<br></body></html>=
--Apple-Mail=_E0308476-0CE9-48C0-BEAE-47A0BEABB6DA--
--Apple-Mail=_8E56BE8D-CA49-4336-BAC1-E16D0F45DBED
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
iQIcBAEBCgAGBQJWnmH3AAoJEF1Aj/0UKykRJRUP/iNpwp82IaTecNCxJKg5sK2U
a2i6c0BqUP+IEIxLSoXxqLH4n2POeEfOi/40Ouz/lHVlQ0O573n/CaCtaIIg2yLG
RLF804ePqtFYmx53XlXs6s72uR5LwGiAXAvEPVrGP1FUaUe4o3v7tDaxM2Q+bhCb
siMnTRYPemkCiy265jkslxse7OAA4d7R2QEqGmen+wUhEaSfDbiMgH2Xy64i9hIH
ZxKIXKBvUfC9M2r0sYTY/gJgQSnnsyqeJwwcA57KDn6dScCHcgvRWrzlK3PiTHCA
ttQcpBZNKEPWvZ3bA36rjt7cbvxeGtBNV3JNL0Uy+0kVf0tsqjf/aX5Pe0CJ+oUQ
Xq5XDK0PyUHA1Dkrn/wquHO2U7Hs8JD9T0HMJVrfOs+mBaZPrA243/TTmQELSM8w
yxmQ/yf8uWa5ekhRHFBj55ID/e0BD17IIbSqr8KdbUizILnaf4Sr7Plx8P+XEEVQ
lN0UA/GVF2BGXesEjaWNxT2NpyQKESlgqHpMO7qnZRhu3UqHgHzoTrGHVXJ6UosF
+0trQTem1Qh5ZaTyVUxs3OTkSxq3dXuHd0Rhzl71FQ7N2jGpWYyfgwYCxsreRKnr
QSCPYpTk/PEZuzm6agaVW0XBJfP450TO7ATkAH6qtvi/iROogOHXT8SMFZmmB//e
UtZ+bknUMbdEvNlAETso
=DkMF
-----END PGP SIGNATURE-----
--Apple-Mail=_8E56BE8D-CA49-4336-BAC1-E16D0F45DBED--
- Raw text -