Package variant error when copying to new schematic

Package variant error when copying to new schematic

Anonymous
Not applicable
2,446 Views
5 Replies
Message 1 of 6

Package variant error when copying to new schematic

Anonymous
Not applicable

I am trying to copy a portion of a schematic to a new schematic and I am getting an error:

"Package variant C1206 in the old version of this device set CAP is not present in the new version of this device set. A library update for the old device may be required first"

 

I'm not using any 1206 parts, so I have no idea what is tripping it up. I tried copying portions of the schematic and as long as I don't include any caps it will work. I'll probably just temporarily delete the caps from the source schematic and add them back in later as a work around.

 

I'd like to understand what is going on and how to fix or prevent this issue going forward. I'm using Eagle 9.2.2. I am not using managed libraries. 

Reply
Reply
0 Likes
Accepted solutions (1)
2,447 Views
5 Replies
Replies (5)
Message 2 of 6

Anonymous
Not applicable

No answers? I hope I don't see this issue again. I fixed by removing parts and re-adding them manually.

Reply
Reply
0 Likes
Message 3 of 6

one-of-the-robs
Advisor
Advisor

It's pretty hard to be certain when there's so little actual information available but my guess would be...

When you created the original schematic, you used a capacitor from a library where C1206 was a valid option for the package of that device. You have since edited the library (or changed your paths to pick up a different library of the same name) such that the device no longer has a C1206 option. The new schematic uses this newer library. When you try to copy the part, Eagle checks that it can map the old part completely, even if you're not using all the possible options.

I don't know whether this behaviour is intentional or required, nor whether it's the same with Design Blocks. You could try making a copy of the old design first, running a full library update, then copying the bit you need from that version.

Reply
Reply
Message 4 of 6

rachaelATWH4
Mentor
Mentor

I'm pretty sure @one-of-the-robs is thinking along the right lines here. Basically, when you include a particular device in a design, ALL the various package options are then present in the design. So, if you have a capacitor device which has multiple package options and you are only using 0603 caps in your design, the 1206 package which is also associated with it is also present in the design. So, if there have been changes in the versions stored between the first design and the second, then it will conflict in this way as the two wont match. The best thing would have been to update the parts on the source design (because probably the footprint was updated because it wasn't quite right anyway) and then it would have imported without having to delete and re-add all your capacitors.

 

Best Regards,

 

Rachael

Reply
Reply
0 Likes
Message 5 of 6

Anonymous
Not applicable

I think I understand, but it's pretty confusing. I am learning as I go, however I find training materials to be rather lacking. I'm not sure how to avoid issues like that in the future.

Reply
Reply
0 Likes
Message 6 of 6

rachaelATWH4
Mentor
Mentor
Accepted solution

@Anonymous wrote:

I think I understand, but it's pretty confusing. I am learning as I go, however I find training materials to be rather lacking. I'm not sure how to avoid issues like that in the future.


 

Part of it comes down to library management and this is an issue no matter what ECAD tools you are using, not just EAGLE. If you make sure your libraries are well developed and you design / check them to a standard there is less chance you'll be modifying them down the line when they've already been used.

 

The next thing is, if you want to reuse part of an existing design in a new design, first you need to make sure that existing design is clean and up to date. Take a backup of your existing design for safety, then do a library update on it to ensure that there are no library changes which would affect any of it's components which are not yet implemented. Check the design to make sure it's all good and the update hasn't caused any issues. Now, go to your new design. Make sure that's also up to date (it's more likely to be) and now you can copy the sections of your old design into your new design without fear of conflict between current and out of date libraries.

 

Essentially, make sure everything is up to date before trying to reuse design sections.

 

Best Regards,

 

Rachael

Reply
Reply
0 Likes