Mail Archives: geda-user/2013/12/29/16:37:21
--e89a8f50347c4624ee04eeb320d1
Content-Type: text/plain; charset=ISO-8859-1
You can do what you want by simply drawing a short net out from the pins
you want to connect. Be sure to edit the attribute of the net,
specifically put in a meaningful netname. Do the same for wherever you want
to connect it to. As long as the netnames match, they will be treated as
the same net. Make the attribute visible for it to show up visibly and in
printouts etc.
Personally, I find this tends to make pretty but fundamentally unreadable
schematics. I would suggest you look at the symbols in the Input/Output
section of the standard library for what to do when you need to connect
across sheets. This does, of course, work within a sheet as well but
overuse can lead to unreadable schematics. It's basically slightly prettier
way to do what renaming the net does.
If all your source and destination pins are grouped, such as in a parallel
bus or any other meaningful grouping of signals, I would encourage you to
explore using buses instead of nets.
Regards
Shashank
On 30-Dec-2013 2:59 AM, "Jan Kasprzak" <kas AT fi DOT muni DOT cz> wrote:
> Stuart Brorson wrote:
> : I believe you can attach a net= attribute to your symbol. Here's some
> : documentation about it:
> :
> : http://wiki.geda-project.org/geda:master_attributes_list#net
> : http://wiki.geda-project.org/geda:na_howto
>
> Thanks. I have read the above documents, and it looks like the
> way I am supposed to do is to add the attribute
>
> net=netname1:pinnumber1,netname2:pinnumber2,...
>
> to the component (e.g. the MCU) itself. This would not result in readable
> schematics, though. The Arduino schematics below has the net name assigned
> and visible near each pin of the connector and MCU.
>
> Or am I misinterpreting the above documents?
>
> Thanks,
>
> -Yenya
>
> --
> | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net -
> private}> |
> | New GPG 4096R/A45477D5 - see http://www.fi.muni.cz/~kas/pgp-rollover.txt|
> | http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/|
> Please don't top post and in particular don't attach entire digests to your
> mail or we'll all soon be using bittorrent to read the list. --Alan Cox
>
--e89a8f50347c4624ee04eeb320d1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">You can do what you want by simply drawing a short net out f=
rom the pins you want to connect.=A0 Be sure to edit the attribute of the n=
et, specifically put in a meaningful netname. Do the same for wherever you =
want to connect it to. As long as the netnames match, they will be treated =
as the same net. Make the attribute visible for it to show up visibly and i=
n printouts etc. </p>
<p dir=3D"ltr">Personally, I find this tends to make pretty but fundamental=
ly unreadable schematics. I would suggest you look at the symbols in the In=
put/Output section of the standard library for what to do when you need to =
connect across sheets. This does, of course, work within a sheet as well bu=
t overuse can lead to unreadable schematics. It's basically slightly pr=
ettier way to do what renaming the net does. </p>
<p dir=3D"ltr">If all your source and destination pins are grouped, such as=
in a parallel bus or any other meaningful grouping of signals, I would enc=
ourage you to explore using buses instead of nets. </p>
<p dir=3D"ltr">Regards <br>
Shashank </p>
<div class=3D"gmail_quote">On 30-Dec-2013 2:59 AM, "Jan Kasprzak"=
<<a href=3D"mailto:kas AT fi DOT muni DOT cz">kas AT fi DOT muni DOT cz</a>> wrote:<br typ=
e=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
Stuart Brorson wrote:<br>
: I believe you can attach a net=3D attribute to your symbol. =A0Here's=
some<br>
: documentation about it:<br>
:<br>
: <a href=3D"http://wiki.geda-project.org/geda:master_attributes_list#net" =
target=3D"_blank">http://wiki.geda-project.org/geda:master_attributes_list#=
net</a><br>
: <a href=3D"http://wiki.geda-project.org/geda:na_howto" target=3D"_blank">=
http://wiki.geda-project.org/geda:na_howto</a><br>
<br>
=A0 =A0 =A0 =A0 Thanks. I have read the above documents, and it looks like =
the<br>
way I am supposed to do is to add the attribute<br>
<br>
=A0 =A0 =A0 =A0 net=3Dnetname1:pinnumber1,netname2:pinnumber2,...<br>
<br>
to the component (e.g. the MCU) itself. This would not result in readable<b=
r>
schematics, though. The Arduino schematics below has the net name assigned<=
br>
and visible near each pin of the connector and MCU.<br>
<br>
=A0 =A0 =A0 =A0 Or am I misinterpreting the above documents?<br>
<br>
Thanks,<br>
<br>
-Yenya<br>
<br>
--<br>
| Jan "Yenya" Kasprzak =A0<kas at {<a href=3D"http://fi.muni.c=
z" target=3D"_blank">fi.muni.cz</a> - work | <a href=3D"http://yenya.net" t=
arget=3D"_blank">yenya.net</a> - private}> |<br>
| New GPG 4096R/A45477D5 - see <a href=3D"http://www.fi.muni.cz/~kas/pgp-ro=
llover.txt" target=3D"_blank">http://www.fi.muni.cz/~kas/pgp-rollover.txt</=
a> |<br>
| <a href=3D"http://www.fi.muni.cz/~kas/" target=3D"_blank">http://www.fi.m=
uni.cz/~kas/</a> =A0 =A0Journal: <a href=3D"http://www.fi.muni.cz/~kas/blog=
/" target=3D"_blank">http://www.fi.muni.cz/~kas/blog/</a> |<br>
Please don't top post and in particular don't attach entire digests=
to your<br>
mail or we'll all soon be using bittorrent to read the list. =A0 =A0 --=
Alan Cox<br>
</blockquote></div>
--e89a8f50347c4624ee04eeb320d1--
- Raw text -