[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: PCB package creation guidelines
- To: geda-user@xxxxxxxx
- Subject: Re: gEDA-user: PCB package creation guidelines
- From: Dan McMahill <dan@xxxxxxxxxxxx>
- Date: Fri, 4 Feb 2005 18:11:37 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Fri, 04 Feb 2005 18:12:49 -0500
- In-reply-to: <1104358341.27369.10.camel@linux.site>
- References: <20041116171401.GA2734@beton.cybernet.src> <1104358341.27369.10.camel@linux.site>
- Reply-to: geda-user@xxxxxxxx
- Sender: owner-geda-user@xxxxxxxx
- User-agent: Mutt/1.4.2.1i
On Wed, Dec 29, 2004 at 02:12:21PM -0800, Steve Meier wrote:
> In my land patterns I use the center of pad 1 as the centroid. I am
> opposed to putting pad names into land patterns because that would make
> patterns non reusable for different components. Do we really need one
> land pattern for an so14 7400 and a second one for a 7402 and so on and
> on. Now if we could get the pad name inserted into the netlist and then
> inserted into the pcb file... that would be COOL.
>
> Steve Meier
I'd like to come up with a different way for doing forward annotation
from gschem to pcb and perhaps at the same time address the back annotation
problem.
In particular, gsch2pcb right now I think needs to know too much about
pcb, its file formats, library paths, etc. What I'd like is to generate
a file which tells pcb
- instantiate U1 which is a SO8, device type = <some vendor #>, and
here are the pin names to use: 1 -> NC 2-> IN-, 3-> IN+, etc.
Then I want pcb to have to figure the rest out. It seems with some
planning that this intermediate file, similar to the ECO files used
by pads, could have a pretty long life without a need for lots of
incremental changes.
-Dan
--