Stats

  • Locked Locked
  • Replies 4
  • Subscribers 165
  • Views 14768
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Converting projects between old and new library

EvanShultz

Hi all,

Due to some infrastructure changes, we have the opportunity to change our library. During the years since we first switched to Cadence we've found that our library could be improved in a number of ways. The library is all set up and being exported, but we will need to convert our projects (both completed and in-progress) from the old to the new library. This can be done in Part Manager, part-by-part, but there must be a better way.

The library changes mostly fall into a few different categories:

  • Libraries names have been changed (cells have only been moved around)
  • Attributes have been added and changed
  • Key properties have been reduced (moved the injected)

 Note that both libraries are held at different network locations to make them site-accessible.

I have to believe that other companies have also done a library migration. Has anyone done that before? Do you know of any tools or services (I expect paid) that can help?

  • RandyBye

    We went thru a similar effort a couple years ago.   We determined that the best way to do it was convert to ADW/EDM as it far superior for managing the library.   The new EDM library was built from existing footprints & schematic symbols, but totally new part attributes that were developed in and imported from a spreadsheet.   The spreadsheet also defined the part/schematic classification and part Lifecycles.   The only thing that was always consistent between the new EDM library and existing library was the part number.   The schematic symbol name was usually the same, but not always.   Once you have the EDM based library the process is to "migrate' the designs to EDM.  During that process the EDM Library Revision Manager tool is able to compare the parts from the old library to the new EDM library and automate the part and/or symbol replacements on the schematic.   We had a lot of help from the Cadence team creating the process and some custom utilities were required to automate some cleanup tasks, but overall the project was successful.  Because the same footprints were used in the old and new library, there were no PCB changes as a result of moving to EDM and new library.  To date we have migrated over 300 projects from the old non-EDM library to the new EDM library.  Mind you it's not easy, but if you spend the time up front and planning and testing, it can be a huge improvement.

    Regards,

    Randy

  • EvanShultz
    Thanks Randy!

    We also will be keeping part number as the one piece of info to use as the key between old and new libraries. In addition, our footprints will also stay the same.

    Is there anything special about EDM-based libraries? Does it change the library, or only help to manage the library? In other words, does adding EDM make some breaking change to the library? The new library is being generated directly from our PLM system, and I'd like to continue managing part data there.

    It sounds like we have a similar situation, albeit I haven't looked at EDM before. I appreciate hearing your story, especially since it appears so relevant. Thanks again!
  • eDave

    I agree with Randy. Using ADW/EDM will offer you big advantages for library management. Albeit that it comes with an administration overhead.

    We migrated a few years ago and have never looked back.

    There are some tricks for doing the part migration. In DE HDL there is a batch utility to globally change parts. _GlobalModify rings a bell. Cadence should be able to support you with using this.

    Allegro won't be a problem if you can get the part tables correct.

  • RandyBye

    Every item in the EDM library is under revision control, that is probably the biggest difference.   Interaction/searching, etc.. with component browser is much faster too because it connects to a database instead of a bunch of files.   Because parts are under rev control, the LRM (Library Revision Manager) tool will automatically report when the symbols/parts on your schematic do not match the revision of parts/symbols in the library.   This is made possible by a local cache of the parts/symbols used on your project.  Additionally, when a brd is opened via EDM Flow Manager, the footprint symbol revisions on the board are immediately compared to the footprint symbol revisions in the library.   Any differences are reported.  You can chose to accept the updated version of the symbols/parts/footprints, or keep what you have on your design.   The ability to assign a Part Lifecycle is also very useful.   If for example you assign a part lifecycle of EOL, if you desire you can prevent engineering from adding that part to a new schematic.   You can still see the part in the library, but it cannot be placed on the schematic.

    The library is still composed of all the items it had before, symbols, footprints, padstacks, etc..., it is just arranged differently with the part number being the highest level.  Schematic symbols and footprints are assigned to a part number.

    Hope this helps.

    Randy

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.