X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 9 Jul 2014 06:39:39 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Silkscreened component values, mailing list, and
 gEDA development
In-Reply-To: <53BCB984.4070701@mcmahill.net>
Message-ID: <alpine.DEB.2.00.1407090619300.3442@igor2priv>
References: <alpine DOT LNX DOT 2 DOT 02 DOT 1406291518550 DOT 30669 AT localhost DOT localdomain> <1404129760 DOT 16971 DOT 8 DOT camel AT pcjc2lap> <53BCB984 DOT 4070701 AT mcmahill DOT net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Tue, 8 Jul 2014, Dan McMahill wrote:

>
> SOT-23's are notorious for this as well.
>
> Others have other approaches but for me having an ascii database that defines 
> the mapping between symbol pins and footprint pins for each complete component 
> has worked reasonably well.

I have a similar setup and it works very well. Mine has two stages:

1. pinmap attribute: name=number pairs, e.g. "pinmap=G=1;S=2;D=3" for a 
mosfet where G, S, and D are pin names on the gschem symbol and 1, 2 and 3 
are pin numbers in pcb

2. a set of small text files named as "device_footprint", e.g. 
"2n7002_sot23" and a "devmap=filename" attribute on the schematics. The 
files contain generic attribute rewrite directives, usually setting up 
pinmap and footprint attributes.

I have a wrapper around gsch2pcb that first executes the devmap attributes 
using a predefined directory as database, then it applies the pinmap 
attributes to renumber pins.

Pros:
  - very easy to maintain the library of mappings - no complicated database 
software, gui, custom version control, but my favorite text editor and my 
favorite VCS
  - easy to follow and manually tweak the process
  - because of the generic attribute rewrite, it can potentially do more 
than just map pinouts
  - very easy and fast to use: instead of footprint, I just assign a devmap 
attribute and I know I won't have to worry about the footprint and pinout
  - can use generic light symbols from any source as long as pins are 
named; can use the same symbol for different models/packages within the 
same schematics

Cons:
  - the major drawback is that the schematics does not show actual pin 
numbers (may be a problem while debugging the circuit)
  - the implementation is hackish: gschlas, a set of scripts
  - I have to remember to use the wrapper version of gsch2pcb


Regards,

Tibor