Re: OT: Eagle feathers, part 1 of N

On Dec 16, 1:05 am, Robert Baer <robertb...@xxxxxxxxxxxx> wrote:
Joerg wrote:
Robert Baer wrote:
  I tried to add a part to the California Micro Devices library and
found it impossible to add a SMD part (or any part other than an
18-pin dip).
  Now the system thinks there is this extra 18-pin dip "part" and i
cannot get rid of it.
  There are parts i would like to add but can find no way to do so.
?help?

You need to read the handbook, Eagle isn't as intuitive as OrCad or
others but it can be tamed. You need to create the footprint separately,
has nothing to do with your part or even the symbol. You can also find
the desired footprint in another library and grab it via "cut", then
open your target library, create a new footprint with same name,
"paste", save library, then add that footprint to your device and
connect all pins.

Why cut & paste and not copy & paste, beats me. Maybe because the
initial GUI for Eagle may have been Bavarian ... ahm, German.

   Handbook? What handbook?
   Hell, i got lost trying to follow instructions from some site found
by the drooling baby gull (goo...).
   Wound up with more un-erasable trash.
**
   Wonderful..
1) "Group" does nothing.
2) For libraries, the "use" makes zero difference - hell i cannot even
use ref_packages and smd_ipc libraries which came with Eagle; "outside"
libraries are slightly worse.
3) If i go into the control panel and select libraries, i definitely can
see all of the libraries (that are on the hard drive in the \eagle\lib
folder).
   All of the libraries have a green dot, except for the recently added
"outside" libraries. I can click on the grey dot and make it green
(right click shows no check by "use" before, and a check after).
   But that makes ZERO difference in that one cannot use any of the
"outside"
libraries or even the two mentioned libs.

   Selecting my on-going schematic, selecting Library and Use etc makes ZERO
difference; nothing helps.
**
   (NOT) Attached is my latest: mcu.sch, err.gif (showing errors that
cannot be fixed) and a wild stab at making a board from the mess.
   Hand translated err.gif: Net GND overlaps pin (not true; checked VERY
carefully), Net N$# overlaps pin (ditto), Net N$4 overlaps pin (ditto),
Only one pin on net N$3 (wire clearly goes from MCU pin to connector
pin), Only one pin on net N$4 (wire clearly goes from MCU pin to
connector pin), POWER pin IC1 VDD connected to +5, POWER pin IC1 VDD
connected to +5, POWER pin IC1 VSS connected to GND, POWER pin IC1 VSS
connected to GND, Unconnected pin X1-16 KL (this is true and acceptable).
   Note that the errors about N$# and N$4 are about pins 39 and 40...and
that no wires resulted on the (messy) board.
   Adding a connector (green dot) made zero difference.
**
   And, naturally, i cannot get rid of that spurious "part" DIP18 (i
think) in the California Micro Devices lib.
   There are a number of parts i would like to make but if i goof there
is no way to delete..then that option is gone.
   If magically there was a lib that had what i wanted, there would be
no way to use it..- Hide quoted text -

- Show quoted text -


Eagle birthing pains! I feel your pain. Fortunately when I was
learning Eagle I had a co-worker working with it at the same time...
We could each discover how to do something and share.

From the control panel you can pull down 'options' select
'Directories' and then add more library directories. The green dot
means that that library is 'active'. You can add parts from it to your
schematic.

Making new parts in a library is a bit of a pain to learn. There are
three separate steps you need to do.
1.) make a schematic part (symbol)
2.)make the pcb foot print (package)
3.) link these two together (device)

You can 'group' 'cut' and then 'paste' from and existing part. The
group and cut are a bit strange... cutting doesn't make the part go
away, but really copies it.... strange syntax, but as Joerg said
perhaps it's a German thing.

You really do need the manual. At one time I think you could down
load it from their website... not sure if that's still true.

Ohh I'm also using version 4.15

George H.

.

Relevant Pages

  • Re: OT: Eagle feathers, part 1 of N
    ...   There are parts i would like to add but can find no way to do so.. ... For libraries, the "use" makes zero difference - hell i cannot even ... carefully), Net N$# overlaps pin, Net N$4 overlaps pin, ... Only one pin on net N$3 (wire clearly goes from MCU pin to connector ...
    (sci.electronics.design)
  • Re: OT: Eagle feathers, part 1 of N
    ... You need to read the handbook, Eagle isn't as intuitive as OrCad or others but it can be tamed. ... even use ref_packages and smd_ipc libraries which came with Eagle; ... Net GND overlaps pin, Net N$# overlaps pin, Net N$4 overlaps pin, Only one pin on net N$3 (wire clearly goes from MCU pin to connector pin), Only one pin on net N$4, POWER pin IC1 VDD connected to +5, POWER pin IC1 VDD connected to +5, POWER pin IC1 VSS connected to GND, POWER pin IC1 VSS connected to GND, Unconnected pin X1-16 KL. ...
    (sci.electronics.design)
  • Re: OT: Eagle feathers, part 1 of N
    ... For libraries, the "use" makes zero difference - hell i cannot even ... Net GND overlaps pin (not true; ... Only one pin on net N$3 (wire clearly goes from MCU pin to connector ... connector pin), POWER pin IC1 VDD connected to +5, POWER pin IC1 VDD ...
    (sci.electronics.design)
  • Re: OT: Eagle feathers, part 1 of N
    ... You need to read the handbook, Eagle isn't as intuitive as OrCad or others but it can be tamed. ... use ref_packages and smd_ipc libraries which came with Eagle; ...
    (sci.electronics.design)
  • Re: OT: Eagle feathers, part 1 of N
    ... For libraries, the "use" makes zero difference - hell i cannot even use ref_packages and smd_ipc libraries which came with Eagle; ...
    (sci.electronics.design)