X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 21 Oct 2012 22:23:59 +0200
From:	Jan Kasprzak <kas AT fi DOT muni DOT cz>
To:	geda-user AT delorie DOT com
Subject:	[geda-user] Pin labeling: best practices?
Message-ID:	<20121021202359.GA24620@fi.muni.cz>
MIME-Version:	1.0
User-Agent:	Mutt/1.5.20 (2009-12-10)
X-Muni-Spam-TestIP:	147.251.48.3
X-Muni-Envelope-From:	kas AT fi DOT muni DOT cz
X-Muni-Virus-Test:	Clean
X-Greylist:	Sender IP whitelisted, not delayed by milter-greylist-3.0 (tirith.ics.muni.cz [147.251.4.35]); Sun, 21 Oct 2012 22:24:01 +0200 (CEST)
Reply-To:	geda-user AT delorie DOT com

	Hello again,

what are the best practices with respect to pin labeling? For example,
I have a 10-pin connector (CONNECTOR_10) which will be used as Atmel AVR
programming connector for USBASP programmer. I want to be able to label
which pin is GND, which pin is clock, which is +5V, etc in my schematics,
and preferably in my PCB as well. In a similar way, I want to be able
to label pins of ATTiny MCU not by their official labels (such as PA1 or ADC3),
but by their actual usage in my board ("current feedback 3", "switch 2",
"PWM output for module 1", "status LED 1", "error LED 2", etc.).

	What is the recommended way to do it? Should I copy the *.sym files
for connectors or the ATTiny MCU to my own project directory, and then
relabel the pins?

	Thanks,

-Yenya

-- 
| Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| 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

- Raw text -