X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eyW3bghvhlwSir9UuZLYOiNyIkinEhAFULnX7TRNywc=; b=BNHg4B1vajJ2gxQO9Gu8jltVkzIAOoUKKK6qMquZBo6ivJlHKrMBcSneGq8xJzwe9o 5vBbHkPviEWy0k6/U/koyXtVNt2xp+29t4UCXtlS8D6B4GFZ3gOtBZk6zciSOHlyC5Pd acN04OSrWmLalr2HkXMW5/gAe+XlRImdNyxmshe7dj0pUG2Xx9eZ3oyF5fxP0BApPSL9 HO4CQSJiY9nHy6QpJ7XnzVrqfxd5B7MUioM54wUqK/Hf0+m3zAgAg8jh9MenLbH2Dcjf aJnPwdyIBU80VGUv/trOTAGDp6IH2fVkuFBvvzl38VVjn1wJQLusyrkEqaycFiJ7og/E L/BA== MIME-Version: 1.0 X-Received: by 10.180.37.112 with SMTP id x16mr42001222wij.48.1388353014865; Sun, 29 Dec 2013 13:36:54 -0800 (PST) In-Reply-To: <20131229212536.GB27189@fi.muni.cz> References: <20131229205407 DOT GA27189 AT fi DOT muni DOT cz> <20131229212536 DOT GB27189 AT fi DOT muni DOT cz> Date: Mon, 30 Dec 2013 03:06:54 +0530 Message-ID: Subject: Re: [geda-user] Gschem nets without explicit connections From: Shashank Chintalagiri To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=e89a8f50347c4624ee04eeb320d1 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 --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" 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 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

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.

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.

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.

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=3D attribute to your symbol. =A0Here's= some
: documentation about it:
:
: http://wiki.geda-project.org/geda:master_attributes_list#= net
: = http://wiki.geda-project.org/geda:na_howto

=A0 =A0 =A0 =A0 Thanks. I have read the above documents, and it looks like = the
way I am supposed to do is to add the attribute

=A0 =A0 =A0 =A0 net=3Dnetname1: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<= br> and visible near each pin of the connector and MCU.

=A0 =A0 =A0 =A0 Or am I misinterpreting the above documents?

Thanks,

-Yenya

--
| Jan "Yenya" Kasprzak =A0<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.m= uni.cz/~kas/ =A0 =A0Journal: 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. =A0 =A0 --= Alan Cox
--e89a8f50347c4624ee04eeb320d1--