Problème Update Library on MacOS X still exist....(Eagle 9.1.2)

[RitchieFromParis]

Hi all and sorry if this question was be posted many time, but I don't find the reply.

I regulary change the mane of the Device or Package library part during a Engineering conception, and each time I have this familiar message :

Following devicesets are used in schematic but have not been found in the corresponding update library:
xxxxxxxx.
If this is not intended, adjust the library paths or library deviceset names and update again.

My directory is ok :

/Users/ritchiembp/Documents/EAGLE/libraries/

It's not really grave but tiresome !! I spent many time to understand the problem.

For solve the problem I have to delete the component and re-add on the schematics.

It's not really convenient.

When I try to open the device in my schematics I have this error message:

Package variant 'XX' of deviceset xxxxx does not exist in current library /Users/ritchiembp/Documents/EAGLE/libraries/con-3m-skt-header.lbr.

Please adjust the library paths or export the drawing libraries first!

I am sure there is a solution, I'm sure I have to do something wrong , but please confirm me.

Thanks all for your help and happy holidays.

Best 

Ritchie

[rachaelATWH4 · Accepted solution]

Hi Ritchie,

When you rename a device in the library, the schematic editor has no way to know the new name. When you try and perform an operation on such a device in the schematic (or board) all it will know about is the old name which no longer exists which is why you get the message you are seeing.

Rather than deleting the part and adding it again, if you right click on it and choose the replace option you should be able to navigate to your new version of the part and select that. This will then replace the existing part with the new part for that instance in the schematic. You'll have to repeat this for every copy of that part in your design though as it won't do them all automatically. You could probably write some ULP to find all instances of <OldPartName> and replace them with <NewPartName> which might speed things up if you do this a lot.

Maybe you can solve the problem another way by amending your design flow a little though. Why do you find you are changing the names of parts so often? This is something that is quite a rare occurrence for me so I hadn't seen this as an issue. I tend to have pretty defined naming conventions for parts so once created they don't need to change. 

Best Regards,

Rachael

[RitchieFromParis]

Hi my friend and thanks again for your precious help.

Ok I see the problem, I have to change the name or something else when a customer want a different name, but this is the problem of me and my customer 🙂

I tried to "REPLACE" but not work.

I have to change my engineering process in the futur, but if the "REPLACE" must to works, I can confirm you it's not work.

Thanks again Rachael and happy holidays to you.

Ritchie

[rachaelATWH4]

Hi Ritchie,

What error message are you getting with the replace command? Have you changed anything more about the part than just the name? Can you give an example of an old and new part which don't allow replace?

Best Regards,

Rachael

[RitchieFromParis · Accepted solution]

Hi Rachael

I've just test with one component and IT'S WORK !! INCREDIBLE.

I let you know when I meet the problem in my project.

Thanks to you and sorry for the trouble.

Cheer

[rachaelATWH4 · Accepted solution]

You're welcome Ritchie, it's no trouble I'm always happy to help 

Best Regards,

Rachael

[RitchieFromParis]

All is you honor...

Best

Ritchie

[RitchieFromParis]

Hi Rachael, 

Just for infos, I tested with the "REPLACE" mode and work !! !I don't understand what was  wrong....

Thanks again to you.

Cheer

Ritchie