• 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. saving in a previous version

Stats

  • State Suggested Answer
  • Replies 3
  • Answers 1
  • Subscribers 161
  • Views 9587
  • Members are here 0
More Content

saving in a previous version

carl carley
carl carley over 2 years ago

we are running version v17.2 and have modified a customers design which was in v16.6. as 17.2 is not backward compatible is it straight forward to export a placement & routing file from the 17.2 pcb to be imported into the 16.6 version?

Delete all the routing etc and use the 2 files and regenerate the pcb data in the 16.6 version

i know exactly how to do this in other pcb tools but i'm new to allegro!

regards

carl

  • Sign in to reply
  • Cancel
  • JuanCR
    0 JuanCR over 2 years ago

    Files such as .brd, .mcm, .sip, .dra, and .pad, which are saved in version 17.2, cannot be opened or downrev’d to 16.x. The recommended practice is to maintain both 16.6 and 17.2 databases/libraries.

    If you try to downrev any of the above files from version 17.2 using File — Export — Downrev design, the tool will display the following message:

    Padstacks (.pad) and symbols (.psm, .bsm, .fsm, .ssm) created in 16.x will load into 17.2 databases.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • tennywhy
    0 tennywhy over 1 year ago

    now you can search x_downrev17.il ,and load it as loadi("x_downrev17.il" "deargds") ,then execute downrev17, the skill will ouput all need file to a directory

    then, you can load the skill in 16.6 software,  and excute it, it will create a same file in 16.6 version.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • jc teyssier
    0 jc teyssier over 1 year ago in reply to tennywhy

    Be aware that some behavior change between 16.x and 17.x (example: dynamic shape: different result)

    And some notion exist in 17.x and NOT in 16.x (example: in 17.2 you can change shape connections to pins per layers; not in 16.6).

    Same for stackup, constraint manager, ...

    I doubt you can get exactly the same thing in 16.x from 17.x. Except for very simple board with no new 17.x feature used and transfers with clipdrawings.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • 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