Actions
Forum Thread Details
  • Replies 5 replies
  • Subscribers 189 subscribers
  • Views 513 views
  • Users 0 members are here
Related

Easy way to create a new package?

e14 Contributor

I don't actually want to create a new package all I want to do is create

a new device which uses an existing package. An SOIC8 to be precise. Now

I have to look up the pad layout for this package and workout the

footprint to be added to a library even though the package is probably in

the current Eagle libs once or twice. I've tried various methods to do

this but the paste buffer is always empty when I try and paste a SO8 into

my library.

 

Parents

  • John schrieb:

     

    I don't actually want to create a new package all I want to do is create

    a new device which uses an existing package. An SOIC8 to be precise. Now

    I have to look up the pad layout for this package and workout the

    footprint to be added to a library even though the package is probably in

    the current Eagle libs once or twice. I've tried various methods to do

    this but the paste buffer is always empty when I try and paste a SO8 into

    my library.

     

    CUT and PASTE work fine - but since they don't use the buffer of the OS,

    only within one instance of EAGLE. Maybe you tried it with two

    instances. Or you didn't click the reference position after CUT.

     

    However, there are other methods to copy packages, too. I prefer the

    command line (within the library editor, type "copy package@library" and

    there it is (including the description)). You might also use the control

    panel: when a library editor window is open, expand the library tree in

    the CP to the particular (source) package and right-click on it, then

    choose "copy to library".

     

    Tilmann

     

  • in reply to e14 Contributor

    Thanks for all the info. I used the copy to library option. That gave me

    the package I needed but now I've got a device in my lib that I can't

    seem to remove at all. image

     

     

     

  • in reply to e14 Contributor

    John schrieb:

     

    Thanks for all the info. I used the copy to library option. That gave me

    the package I needed but now I've got a device in my lib that I can't

    seem to remove at all. image

     

    You can remove devices with the REMOVE command - funny, isn't it? image

     

    BTW, did you copy the complete device? It's also possible to copy just

    the package alone.

     

    Tilmann

     

  • in reply to e14 Contributor

    Tilmann Reh wrote:

     

    John schrieb:

     

    >> Thanks for all the info. I used the copy to library option. That

    gave me

    >> the package I needed but now I've got a device in my lib that I

    can't

    >> seem to remove at all. image

     

    You can remove devices with the REMOVE command - funny, isn't it? image

     

    BTW, did you copy the complete device? It's also possible to copy

    just

    the package alone.

     

    Tilmann

     

    Up the top in the Library menu. Thanks found it. Yeah can't argue with

    the naming convention used. Thanks a million

     

Reply
  • in reply to e14 Contributor

    Tilmann Reh wrote:

     

    John schrieb:

     

    >> Thanks for all the info. I used the copy to library option. That

    gave me

    >> the package I needed but now I've got a device in my lib that I

    can't

    >> seem to remove at all. image

     

    You can remove devices with the REMOVE command - funny, isn't it? image

     

    BTW, did you copy the complete device? It's also possible to copy

    just

    the package alone.

     

    Tilmann

     

    Up the top in the Library menu. Thanks found it. Yeah can't argue with

    the naming convention used. Thanks a million

     

Children
No Data