• 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. How do you back annotate with a .swp file?

Stats

  • State Not Answered
  • Replies 2
  • Subscribers 44
  • Views 8330
  • Members are here 0
More Content

How do you back annotate with a .swp file?

alanbog
alanbog over 2 years ago

I'm trying to use a .swp file to back annotate a schematic in Capture CIS 17.4. If I go to Tools>Back Annotate, there is an option to select a .brd file, but I don't see an option to select a .swp file anywhere. The user guide says that there should be an option to specify the swap file's path and filename here, but I don't see it. What am I missing?

  • Sign in to reply
  • Cancel
Parents
  • avant
    0 avant over 2 years ago

    After re-sequencing is done in Allegro, it produces the report file called “rename.log”. This file is in plain text
    format. We will use this file to produce the was-is file which later we will use it for back annotation in the
    ORCAD schematics. Below is a sample rename.log file for an example.
    (------------------------------------------------------------)
    ( RENAME REFDES )
    ( Drawing : BK-1289200-verB.brd )
    (------------------------------------------------------------)
    Renaming components on BOTH_SIDES on entire BOARD
    Extents: (-19900.0,-19900.0) (26100.0,16100.0)
    Sequencing the Reference Designators SEQUENTIALLY
    Row processing direction : to the RIGHT, from the top down.
    Processing TOP of board, C340 has AUTO_RENAME property but is on BOTTOM, component ignored.
    Processing TOP of board, C155 has AUTO_RENAME property but is on BOTTOM, component ignored.
    OLD C1 NEW C1
    OLD Q1 NEW Q1
    OLD C2 NEW C2
    OLD TP1 NEW TP1
    OLD TP2 NEW TP2
    OLD TP3 NEW TP3
    OLD R1 NEW R1
    OLD L1 NEW L1
    OLD C4 NEW C3
    OLD C5 NEW C4
    OLD C6 NEW C5
    OLD TP8 NEW TP4
    OLD TP4 NEW TP5
    OLD U1 NEW U1
    (Note: Above section is what we need to produce was-is file)
    Processing TOP of board, R172 has AUTO_RENAME property but is on BOTTOM, component ignored.
    HARD_LOCATION property on J1, component ignored.
    Processing TOP of board, RP67 has AUTO_RENAME property but is on BOTTOM, component ignored.
    (Note: Above a HARD_LOCATION message , this prevents from that component to be re-sequenced)
    How do we make a Was-is-file from Allegro re-sequencing file report (rename.log) ?:
    Open “rename.log” file in a Text editor. Copy all the line starting with OLD xx NEW yy. Copy these sections
    into a new text file. Once you go through the report file, and you made sure all lines are copied, (you can also
    cut and paste which would be easier to trace if you missed any lines), save this new file as “was-is-file.txt”.
    Now you have copied all replacement reports from report file to the new was-is file. All you have to do now is
    to search and replace “OLD” with nothing and replace “NEW” with nothing. Basically, erase “OLD” and
    “NEW” prefixes, we do not need them. The file can be any file extension, but essentially it is a text file
    indicating each component reference update in a separate line. Beginning with old component reference
    designator and “SPACE” and the new reference designator.
    Example “was-is-file.txt” file: Explanation:
    Q1 Q1
    C2 C2
    TP1 TP1
    C4 C3
    U3000 U4

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • avant
    0 avant over 2 years ago

    After re-sequencing is done in Allegro, it produces the report file called “rename.log”. This file is in plain text
    format. We will use this file to produce the was-is file which later we will use it for back annotation in the
    ORCAD schematics. Below is a sample rename.log file for an example.
    (------------------------------------------------------------)
    ( RENAME REFDES )
    ( Drawing : BK-1289200-verB.brd )
    (------------------------------------------------------------)
    Renaming components on BOTH_SIDES on entire BOARD
    Extents: (-19900.0,-19900.0) (26100.0,16100.0)
    Sequencing the Reference Designators SEQUENTIALLY
    Row processing direction : to the RIGHT, from the top down.
    Processing TOP of board, C340 has AUTO_RENAME property but is on BOTTOM, component ignored.
    Processing TOP of board, C155 has AUTO_RENAME property but is on BOTTOM, component ignored.
    OLD C1 NEW C1
    OLD Q1 NEW Q1
    OLD C2 NEW C2
    OLD TP1 NEW TP1
    OLD TP2 NEW TP2
    OLD TP3 NEW TP3
    OLD R1 NEW R1
    OLD L1 NEW L1
    OLD C4 NEW C3
    OLD C5 NEW C4
    OLD C6 NEW C5
    OLD TP8 NEW TP4
    OLD TP4 NEW TP5
    OLD U1 NEW U1
    (Note: Above section is what we need to produce was-is file)
    Processing TOP of board, R172 has AUTO_RENAME property but is on BOTTOM, component ignored.
    HARD_LOCATION property on J1, component ignored.
    Processing TOP of board, RP67 has AUTO_RENAME property but is on BOTTOM, component ignored.
    (Note: Above a HARD_LOCATION message , this prevents from that component to be re-sequenced)
    How do we make a Was-is-file from Allegro re-sequencing file report (rename.log) ?:
    Open “rename.log” file in a Text editor. Copy all the line starting with OLD xx NEW yy. Copy these sections
    into a new text file. Once you go through the report file, and you made sure all lines are copied, (you can also
    cut and paste which would be easier to trace if you missed any lines), save this new file as “was-is-file.txt”.
    Now you have copied all replacement reports from report file to the new was-is file. All you have to do now is
    to search and replace “OLD” with nothing and replace “NEW” with nothing. Basically, erase “OLD” and
    “NEW” prefixes, we do not need them. The file can be any file extension, but essentially it is a text file
    indicating each component reference update in a separate line. Beginning with old component reference
    designator and “SPACE” and the new reference designator.
    Example “was-is-file.txt” file: Explanation:
    Q1 Q1
    C2 C2
    TP1 TP1
    C4 C3
    U3000 U4

    • 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