Searching \ for '[ee] First stab at an Eagle library' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/pcbs.htm?key=eagle
Search entire site for: 'First stab at an Eagle library'.

Exact match. Not showing close matches.
PICList Thread
'[ee] First stab at an Eagle library'
2005\11\11@044725 by M Graff

flavicon
face
part 0 44 bytes
his is a multi-part message in MIME format.
part 1 1064 bytes content-type:text/plain; charset=ISO-8859-1; format=flowed (decoded 7bit)

I'm starting to do what most other CAD (at least Eagle) users do --
building a library.  In this case, I'm starting with things that are
missing but I have on hand and intend to use on an upcoming project.

Since I'm new to this level of layout (I usually write software :) I'd
appreciate feedback on this first part.  It's for Tamura transformers
with a single primary and dual secondaries, models 3FS-3XX.  The ones I
use are 3FS-312, which has two 12 VAC secondaries when the primary is
driven by 120 VAC.

In particular, please give feedback on the pad sizes vs. holes, and so
on.  I _think_ this looks sane (and if so, I will happily add the
3FS-1XX, -2XX, and -5XX varities, which have different pin spacing),
then move on to other components.

Things I've done:

       Put the transformer symbols on the tDocu layer, for high-detail
documentation.

       Put only a box outline on the tPlace layer, since that is all that is
needed for placement.

       Put a box on the tKeepout layer, since this is a large box.

--Michael


part 2 3708 bytes content-type:application/octet-stream; (decode)

part 3 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

2005\11\11@105420 by olin piclist

face picon face
part 1 2776 bytes content-type:text/plain; (decoded 7bit)

M Graff wrote:
> I'm starting to do what most other CAD (at least Eagle) users do --
> building a library.  In this case, I'm starting with things that are
> missing but I have on hand and intend to use on an upcoming project.

I make some of my Eagle stuff available at
http://www.embedinc.com/pic/dload.htm.  Install the Eagle tools release and
you'll get a few libraries, scripts, some cool (well I think so) ULPs, and a
few associated programs.  I've also attached my transformer library which is
not included in the Eagle tools release.  It includes one Tamura
transformer.

> In particular, please give feedback on the pad sizes vs. holes, and so
> on.

There are too many rules to list here in the available time.  A good writeup
on designing Eagle parts would take quite a few pages.

Here is a short answer to your direct question.  The hole size should be
just big enough to guarantee it will exceed the maximum diameter of the pin.
Assume the board house will make the hole +-4mil from your specification.
Look in the data sheet for the part and find the maximum pin diameter, then
add 4mil, then find the smallest standard hole size that meets or exceeds
that.  Use one of the hole sizes in the holes.txt file in the Eagle
directory after installing my Eagle tools.  For small holes where tight
spacing might matter, make the pad diameter 16mil larger than the hole
diameter.  For medium size holes use 20 mil.  For big fat mounting holes add
25mil to the max diameter of the screw head or whatever.

> Put the transformer symbols on the tDocu layer, for high-detail
> documentation.

I like to put as nice a picture as possible on the tplace layer.  You can
especially see this for the Tamura transformer in the attached library.  For
a large part like that, you can add lots of niceties like that.  The extra
paint is free to you.  Make parts with >NAME in the tnames layer.  Make sure
the resulting line width is at least 8mil.  For small parts use SIZE .05 and
RAT 16.

Some parts are so small or packed so densly that I use the tdocu layer to
write >NAME much smaller.  This will not go on the silkscreen, but will show
up in the drawing later when using GRID_BRD.ULP.  Every one of my parts has
>NAME in the tdocu layer somewhere near the middle.  See my examples for
SIZE and RAT.

> Put only a box outline on the tPlace layer, since that is all that is
> needed for placement.

That may be all that is needed (don't forget orientation), but a good visual
indication of what goes where is a very good idea.  People make mistakes,
and the easier you make it on them, the less they'll make.  Remember, unlike
in too many schools, neatness and clarity count for a lot in the real world.


part 2 3648 bytes content-type:application/x-zip-compressed; (decode)

part 3 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...