• 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. PCB Design
  3. Database comparisons - Version 13 to Version 15

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 164
  • Views 3392
  • 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

Database comparisons - Version 13 to Version 15

archive
archive over 18 years ago

We are in the process of updating numerous Concept-Allegro designs to version 15, from version 13 (and below).  We have it all fairly well figured out, with regards to the migration path.

We are not spinning artwork and cannot easily and automatically verify the conversion by way of comparing Gerbers.  (Issues with differing output formats AND hand manipulation of aperture lists prevent a smooth process.)

Have any of you come across a comparison utility that would allow us to compare the Allegro Design Entry V15 databases to our Concept V13 databases?

There are methods whereby you can extract netlists, and run Unix diff utilities.  This may not work too well due to netname changes across the versions.  I worry there may be too much to filter out.

Help....

Kory Johnson
GE Medical Systems - OEC


Originally posted in cdnusers.org by kory_johnson
  • Cancel
  • archive
    archive over 18 years ago

    Kory,

    There is a design_compare utility bundled in the software. This utility will import two (or more) different XML files and compare the results graphically. Signal names can be different but if the contents are logically equivalent, it resolves them as being the same. It works very well.

    The structure of these xml files is fairly straight forward. There is a nets section and packages. Here's a snippet.



    CRK_SCL_RX_N
    R3.2
    U3.11
    J6.B5

    CRK_SCL_RX_P
    R3.1
    U3.12
    J6.B6

    ...
    RM1005
    RESISTOR_2PIN-/03,200K,1%,0.1W-0.1W,1%,200K
    R17


    RM0502
    RESISTOR_2PIN-/01,7.32K,1%,0.02W-0.02W,1%,7.32K
    R15


    ...


    So the trick here is to convert your 13.x and 15.x pst files to xml. The File->Import Logic in Allegro has an option to Create the PCB XML and launch the design compare utility.

    I haven't tried what I'm about to suggest, but logic suggests it should work.

    1. Open a blank board and import the 13.x pst files, using the generate the XML option.
    2. You should have a file in the board directory called something_sch.xml. Rename it to 13x_sch.xml.
    3. Open a blank board and import the 15.x pst files, using the generate the XML option.
    4. You should have a file in the board directory called something_sch.xml. Rename it to 15x_sch.xml.
    5. Launch the design compare and load the two files.

    I hope this helps.




    Originally posted in cdnusers.org by cdavies
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Kory,

    Sorry, it looks like the XML tags got removed from my last post. If you get the jist of what I'm talking about, you should be able to see an example after you run the import.


    Originally posted in cdnusers.org by cdavies
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Kory,

    Here is another try at the XML sample.  See attached.


    Originally posted in cdnusers.org by cdavies
    • sample_sch.txt
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Try EDACompare from PTC.

    The Cadence compare tool Charlie mentioned only does netlists really.

    EDACompare does parametric comparisions and geometric comparisions (brd to brd, gerber to gerber etc.). It reports Refdes changes netname changes attrinbute changes etc

    Pretty much everyhting InterComm can read, EDACompare can compare it.

    http://www.ptc.com/WCMS/files/25639/en/25639en_file1.pdf

    http://www.ptc.com/appserver/mkt/products/home.jsp?&k=3285

    I hope this helps

    Andy


    Originally posted in cdnusers.org by andyk
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    The design compare inside of Allegro actually works well. We migrated from DxDesigner to ConceptHDL and used the Design Compare in Allegro to verify the schematic logic from both tools. I needed to load the logic from each schematic tool into Allegro to generate the required XML files used by the Design Compare but other than that it did what I needed.

    Every so often I am asked to generate a difference reports between design revisions and the Design Compare in Allegro works flawlessly.

    Good luck,
    Mike Catrambone
    UTStarcom, Inc.


    Originally posted in cdnusers.org by mcatramb91
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
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.

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

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