Actions
Forum Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 177 subscribers
  • Views 1653 views
  • Users 0 members are here
Related

Eagle library export issue

earckens

When a library is extracted from a .brd file with the file/run ulp/exp-lbrs.ulp command then all separate parts are stored in individual little libraries in the projects folder where also the .sch and .brd files are.

 

When in the libraries folder a new library is created for that project and all individual little libraries are copied into this single new library then there still is no live link with the .brd and .sch file. Example: if I change a component in this new single library (for example the pad size from long to round) and activate the "update" button on the library menu, nothing changes in the open .brd file.

If however I make the change in the little individual library and press "update" there, then the component changes in the .brd open file.

 

How can I change this so that the new library is connected "live" to the corresponding .brd file?

Parents
  • 0

    The update in the library editor only updates the other portions of the

    library that may be affected by your library change. Like modifying a

    symbol used by many devices. Libraries don't know which boards use their

    parts. Schematic and boards only retain the library name and part name,

    not where the library lives

    That's also a potential problem and propagation of chaos...you end up

    wondering why your boards arrive with oblong pads or some other unexpected

    result. Eagle should make it absolutely impossible to have more than one

    device, symbol or package with a duplicated name anywhere in the library

    system.  Doing otherwise invites chaos.  If you want a slightly different

    version of a 2N3904, it must be enforced to have a different library

    storage name (2N3904_style2, 2N3904#ver2, etc).  

     

    Fifty devices each called exactly "2N3904" floating around in different &

    unknown locations, having exactly the same or POSSIBLY substantially

    different parameters than its cousins is a recipe for madness.  Apparently

    there is not even a way to compare and find out what those 50 potential

    differences are.

    --

    http://www.eaglecentral.ca :: The original and best browser access to CadSoft EAGLE support forums.  Supported by EAGLE licenses purchased through us :: http://www.eaglelicenses.com

     

Reply
  • 0

    The update in the library editor only updates the other portions of the

    library that may be affected by your library change. Like modifying a

    symbol used by many devices. Libraries don't know which boards use their

    parts. Schematic and boards only retain the library name and part name,

    not where the library lives

    That's also a potential problem and propagation of chaos...you end up

    wondering why your boards arrive with oblong pads or some other unexpected

    result. Eagle should make it absolutely impossible to have more than one

    device, symbol or package with a duplicated name anywhere in the library

    system.  Doing otherwise invites chaos.  If you want a slightly different

    version of a 2N3904, it must be enforced to have a different library

    storage name (2N3904_style2, 2N3904#ver2, etc).  

     

    Fifty devices each called exactly "2N3904" floating around in different &

    unknown locations, having exactly the same or POSSIBLY substantially

    different parameters than its cousins is a recipe for madness.  Apparently

    there is not even a way to compare and find out what those 50 potential

    differences are.

    --

    http://www.eaglecentral.ca :: The original and best browser access to CadSoft EAGLE support forums.  Supported by EAGLE licenses purchased through us :: http://www.eaglelicenses.com

     

Children
  • 0 in reply to e14candies

    Interesting note!

     

    Would it be best then to keep a library per project and export to a new library in a new project whatever is necessary? And maybe also keep a general "overall" library where all updated devices are being kept, so that it can be used as a "personal master library"?

     

    Erik

  • 0 in reply to earckens

    On 19/11/16 04:33, Erik Arckens wrote:

    Interesting note!

     

    Would it be best then to keep a library per project and export to a new library in a new project whatever is necessary? And maybe also keep a general "overall" library where all updated devices are being kept, so that it can be used as a "personal master library"?

     

    I suppose you could...

     

    Or you could always keep all of your libraries in one place, only use

    the ones you've created (or, at minimum, thoroughly reviewed and edited

    as needed), and be disciplined about it. These libraries would then

    always adhere to your "house style".

     

    You may need more than one set of libraries if you do work for several

    customers with different house styles, of course. And if you frequently

    do a single project for a customer, that will largely boil down to what

    you suggest.

     

     

  • 0 in reply to autodeskguest

    Hi I have experienced the same problem where the newly created library is not linked to the sch/brd files. A couple years ago I found a way to re-assign the existing library name  of each part to the newly created combined library. Unfortunately old age has caught up to me and I can't remember the command that did this. Can someone tell us how we can do this. All I remember is I typed in the command and then I clicked each component on the schematic and then the associated library became the newly created library. Thanks