element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Custom device doesn't update after package editing
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 180 subscribers
  • Views 2626 views
  • Users 0 members are here
  • frontpage
Related

Custom device doesn't update after package editing

Former Member
Former Member over 9 years ago

Hey there,

 

I'm quite new to Eagle, so please don't throw rocks if I'm asking something basic.

I've created a custom device and after turning it into a real PCB I realized I need to modify some pads. I looked up the specific package in my library and performed the necessary changes. The problem is now that I can't get Eagle to allow me to use my updated device.

 

I am attaching a few pics to illustrate the problem:

- SPDT_device_library.png shows the device in my library. I have intentionally edited the pads on the sides to be asymmetrical, so that it would be easy to spot whether the device is updated or not

- Control panel view.png - back to my control panel, when I look inside the library, the old package is being displayed to me

- Using the device.png - not surprisingly, if I use the device in a new project, I get the old package with symmetrical side pads.

 

I can't find an explanation for what is happening here. It looks like there exists no instance of the old package. Yet somehow the device from my library is pooling out from somewhere and using the old package.

 

Your help is greatly appreciated,

Mihaela

Attachments:
image
image
image
  • Sign in to reply
  • Cancel
  • rachaelp
    0 rachaelp over 9 years ago

    Hi,

     

    Just a couple of suggestions to get the really simple possibilities out of the way first before trying to work out what else might be going on:

     

    a) Are you sure you saved the changes in the package editor before using it in the design? Really obvious and probably not the issue but I had to ask!

     

    b) Are you sure you are editing the copy of the library you think you are editing? I had a similar issue a while back and I found that the version of the library I had open in my library editor was in a different folder because I had been in the middle of re-structuring my libraries and my library path in EAGLE was pointing to a different copy! Needless to say I got right back to finishing off my re-structuring so that wouldn't happen again!

     

    Best Regards,

     

    Rachael

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • glennp17321
    0 glennp17321 over 9 years ago

    Try exporting the source (.scr).  Take a look at the source with a simple editor.  Look for the device-in-question's package.  That may give you a hint.

     

    GP

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 9 years ago

    Hi

     

    If you have made the change in the library and saved it.

    Then in the board you performed a library update or update all

    and the problem persists.

    Or if you ADD the part and it is the unmodified one, then I strongly

    suspect the following:

     

    You are accessing a similarly named library in your environment.

    You could confirm another library of the same name exists by searching for

    eeg_parts.lbr

     

    There is a few reason you can target the other file.

    In Control Panel > Options > Directories > Libraries

    if there are multiple paths to library folders, they are checked left to

    right so if you library name is found in another folder, and the device

    name matches, that's the one that gets used.

     

    Another way, if you use projects, comes from your eagle.epf file in the

    project folder. There is one of these files for each project. In it there

    are paths to used library files and hence if a project came from different

    instance of Eagle it could point to the other library location. You can

    un-use all libraries by entering into the command line

    USE -*

    That will un-use all the libraries. Then you should 'use' the ones you want

    again.

     

    HTH

    Warren

     

     

     

     

    --

    Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to rachaelp

    Hi Rachael,

     

    Thank you for pointing out the obvious possible sources. Many times the unexpected behaviour comes from unnoticed small mistakes like the ones you mentioned. I had checked the two options you identified, but I think it's very good practice to start with them.

     

    Best,

    Mihaela

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to glennp17321

    Hi GP,

     

    Your tip led me to exporting the part list (I didn't know where to export the scr from) and noticing a silly mistake I had made. I had changed the library name as the initial one was a bit confusing (in the Control Panel -> I selected the library and hit Rename). And then I changed the package I was interested in.

    In the exported partlist I noticed that the parts that wouldn't update were still considered to belong to a library having the old name. I was assuming that when the library name got changed, the included parts from my project would also update their library source name, but that is not the case. I have now changed the library name back to its original value and the parts from my project updated properly.

     

    Thank you for your patience with noob question,

    Mihaela

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • rachaelp
    0 rachaelp over 9 years ago in reply to Former Member

    Hi Mihaela,

     

    Rather than renaming your library back to allow the update, you could instead have right clicked on the component in question in the schematics and selected 'Replace' from the context menu and then picked the part from your renamed library.

     

    Anyway, I am glad to hear you got to the bottom of your issue and you now have your design updated, I just wanted to let you know of this alternative for the future.

     

    Best Regards,


    Rachael

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube