delorie.com/archives/browse.cgi   search  
Mail Archives: geda-help/2016/01/15/22:32:58

X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Date: Sat, 16 Jan 2016 04:36:31 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: "Gene Heskett (gheskett AT shentel DOT net) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
X-Debug: to=geda-help AT delorie DOT com from="gedah AT igor2 DOT repo DOT hu"
From: gedah AT igor2 DOT repo DOT hu
Subject: Re: [geda-help] adding missing footprints
In-Reply-To: <201601151906.12486.gheskett@shentel.net>
Message-ID: <alpine.DEB.2.00.1601160426360.9035@igor2priv>
References: <201601151906 DOT 12486 DOT gheskett AT shentel DOT net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com


On Fri, 15 Jan 2016, Gene Heskett (gheskett AT shentel DOT net) [via geda-help AT delorie DOT com] wrote:

> On Friday 15 January 2016 07:58:57 gedah AT igor2 DOT repo DOT hu wrote:
>
>> On Fri, 15 Jan 2016, Gene Heskett (gheskett AT shentel DOT net) [via
> geda-help AT delorie DOT com] wrote:
>>> Greetings, new subscriber;
>>>
>>> Using gEDA as in the debian wheezy repo's, although I was able to
>>> get a newer pcb to build, so it is 1.99z.
>>>
>>> I have composed a little 6 part schematic in gschem, but when I do
>>> the translation gsch2pcb step, 4 of the 6 parts I chose schematic
>>> symbols for, have no "footprint" and are omitted from the pcb.
>>> Loaded into pcb, it obviously makes no sense to this beginner.
>>>
>>> Can this data be added to the library part description?
>>>
>>> If so how?  And if I do it, how can I submit back to gEDA?
>>
>> For the PCB workflow, you need to specify the "footprint" attribute in
>> gschem. It is not possible to ship a generic purpose lib with
>> footprints already set because most devices are available in different
>> footprints (e.g. lm358 in SO8 or DIP8, 2n3904 in to92 or sot23 or even
>> dual NPN in sot23 with 6 pins).
>>
>> HTH,
>>
>> Igor2
>
> Can this be done with a text editor, or must it refer to a known pattern
> from a library entry somehow?

The normal PCB workflow is that you edit the schematics (the sch file) and 
then use gsch2pcb (or PCB's builtin "import schematics" feature).

The most common way to edit the schematics is using gschem. However, the 
file format is plain text so it is posible to edit it with a text editor 
or using a script.

The text editor way is rather painful as the format is not too friendly: 
you need to find your element (searching for the refdes, probably), then 
add two new lines in the right "attribute list" of it.

I recommend using gschem first, and go with text editing only when you are 
already experienced with the workflow.

>
> IOW, where does this "footprint" data come from?

The info what footprint you want comes the datasheet of the component and 
your wise choice between the options. The pcb-name of the footprint (the 
string you need to use) comes from checking what pcb or gedasymbols.org or 
other footprint collections have.

> As a for instance the transistor is a 2SK3264 mosfet.

> The diodes are 1N5822's, and because they are bulky bodied, will likely
> be mounted standing up, and that may still require pads on >100 mill
> centers.  That same pattern will serve for mounting everything but the
> transistor, which of course has 3 legs.

Datasheet says to220; the stadard pcb footpritn lib has multiple to200 
variants, if you need standing try TO220 or TO220W.

Tip: run pcb and press i, then type to220.

> FWIW, I drew up a perfectly servicable pcb pattern in pcb 2 days back,
> but when I exported it as gcode, what should have been about 100k of
> gcode, was 1500 bytes and didn't backplot anything but a small blob, so
> obviously it ignored what I drew and placed on the bottom of the pcb.

Could you attach the pcb file?

Regards,

Igor2

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019