• 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 Capture CIS
  3. OrCAD 17.4 CIS backannotate pin swap

Stats

  • State Not Answered
  • Replies 5
  • Subscribers 45
  • Views 4652
  • Members are here 0
More Content

OrCAD 17.4 CIS backannotate pin swap

MrSpock
MrSpock over 1 year ago

Our design flow updated to OrCAD Capture 17.4 from 17.2.  We use PADS for our PCB layout.  I use a contractor for our digital routing and he has never had a problem doing FPGA pin swapping back to OrCAD.  However in 17.4 he can't find the Backannotate dialog boxes Layout tab.  This is where one used to specify the swap file and the scope of the backannotation.  This dialog box Layout tab is gone in version 17.4.

How does one do a pin swap / netlist backannotation in version 17.4?

Backannotate dialog box in version 17.2

Backannotate dialog box in version 17.4

  • Sign in to reply
  • Cancel
Parents
  • Robert Finley
    0 Robert Finley over 1 year ago

    Ok, I'm not the only PADS sufferer left. 

    You need 17.2 on hand to support backannotation or go to 22.1.  The DSN file format is the same.

    I have been using 16.6 in parallel with 22.1 for the past 8 years because MGC won't update their translator to read Allegro's 17.2 to read current padstack data.  If something breaks, MGC won't talk to me unless I'm running 16.3 on a windows7 machine.

    Facing a long list of stuff PADS can't do, Allegro is my superpower until windows 10 goes EOL and I can't use 16.x anymore.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Robert Finley
    0 Robert Finley over 1 year ago

    Ok, I'm not the only PADS sufferer left. 

    You need 17.2 on hand to support backannotation or go to 22.1.  The DSN file format is the same.

    I have been using 16.6 in parallel with 22.1 for the past 8 years because MGC won't update their translator to read Allegro's 17.2 to read current padstack data.  If something breaks, MGC won't talk to me unless I'm running 16.3 on a windows7 machine.

    Facing a long list of stuff PADS can't do, Allegro is my superpower until windows 10 goes EOL and I can't use 16.x anymore.

    • 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.

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

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