• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. Library uprev Best Practices

Stats

  • State Not Answered
  • Replies 1
  • Subscribers 166
  • Views 655
  • Members are here 0
More Content

Library uprev Best Practices

melview1
melview1 2 months ago

HI~

While running layout v24.1, I ran into the issue that it could no longer open my footprints as they were in an older version and needed updating.  I just completed uprev'ing all my footprints (.dra and .psm).  I did it incrementally by running once with the v17.4 dbdoctor and then running again with the v24.1 dbdoctor (some of them were failing if trying to just run v24.1 dbdoctor right away).  Now I can open my footprints in v24.1.  The part that I have a question about is how to handle the psm files?  AI has suggested several options and I wanted to reach out to see if anyone had any advice as to what the appropriate next step should be.

1. Use the psm files as-is after uprev'ing them.  Nothing else needed.

2. Delete all psm and let OrCAD recreate the psm on-demand the next time each footprint is loaded (does it actually work this way?)

3. Delete all psm files, then open/regenerate psm/save each and every footprint.  This isn't really feasible to do manually for a whole library of hundreds, if not thousands, of parts.

4. Delete all psm files, then use a batch file (that I don't have) to open/regenerate psm/save each footprint.  Still a lot of parts that would take awhile, but the batch file would make it pretty automatic.

Thanks!

-melview1

  • Cancel
  • Sign in to reply
Parents
  • Ulf K
    0 Ulf K 2 months ago

    I had the same problem some years ago and if I remember correctly, it was possible to use wildcards for the dBdoctor (the separate version avilable in the \tools section, or if it was in the \bin.

    I first copied the directory to another folder, just in case I had to use them with an old version, then invoked dBdoctor, defining using wild cards.

    Let it loose and went for a mug of coffee...

    When I came back, all symbols, .dra as well as .psm had been updated.

    If you decide to try the above: Always make backups!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Ulf K
    0 Ulf K 2 months ago

    I had the same problem some years ago and if I remember correctly, it was possible to use wildcards for the dBdoctor (the separate version avilable in the \tools section, or if it was in the \bin.

    I first copied the directory to another folder, just in case I had to use them with an old version, then invoked dBdoctor, defining using wild cards.

    Let it loose and went for a mug of coffee...

    When I came back, all symbols, .dra as well as .psm had been updated.

    If you decide to try the above: Always make backups!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information