Stats

  • Locked Locked
  • Replies 4
  • Subscribers 166
  • Views 16325
  • 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

backannotation

rainbowtrout

i am using allegro pcb and capture. my question is what files are need to backanno to capture, and how to generate. The bd was renaned with no errors.  i was using Orcad before and there was a swap file that was used, is there still a swap file for allegro?

Parents
  • Cadpro2K
    If the only change done on the board is a re sequencing of reference designators
    then there is an alternative to the third party back annotation.

    After re-annotation the board is completed, Allegro creates a file called rename.log or
    reftext.log. This file can easily be turned into a swap file which can be applied to Capture

    The format of a Capture swap file is

    CHANGEREF H1  H1
    CHANGEREF R5082   R1
    CHANGEREF R5084   R2


    For example the rename.log file lists

    Processing TOP of board, R5471 has AUTO_RENAME property but is on BOTTOM, component ignored.
    Processing TOP of board, R5470 has AUTO_RENAME property but is on BOTTOM, component ignored.
    OLD H1    NEW H1
    OLD R5082    NEW R1
    OLD R5084    NEW R2

    For example the reftext.log file lists

    *NOTE: Refdes C281 changed to C33
    *NOTE: Refdes U12 changed to U44
    *NOTE: Refdes C44 changed to C15

    Either of these files can easily be converted to the Capture swap file format using find
    and replace in a text editor .

    Some suggestions

    Lines can be commented out the  by adding a *
    For example find and replace "Processing" with "*Processing"
    Then changing the word OLD to the command CHANGREF
    Then replacing the word NEW with a space
     
    The result will be
     
    * Processing TOP of board, R5471 has AUTO_RENAME property but is on BOTTOM, component ignored.
    * Processing TOP of board, R5470 has AUTO_RENAME property but is on BOTTOM, component ignored.
    CHANGEREF H1  H1
    CHANGEREF R5082   R1
    CHANGEREF R5084   R2
     
    Then this SWAP file can be applied by going to tools back annotate, select the layout tab
    and point to the .SWP file you just created.
Reply
  • Cadpro2K
    If the only change done on the board is a re sequencing of reference designators
    then there is an alternative to the third party back annotation.

    After re-annotation the board is completed, Allegro creates a file called rename.log or
    reftext.log. This file can easily be turned into a swap file which can be applied to Capture

    The format of a Capture swap file is

    CHANGEREF H1  H1
    CHANGEREF R5082   R1
    CHANGEREF R5084   R2


    For example the rename.log file lists

    Processing TOP of board, R5471 has AUTO_RENAME property but is on BOTTOM, component ignored.
    Processing TOP of board, R5470 has AUTO_RENAME property but is on BOTTOM, component ignored.
    OLD H1    NEW H1
    OLD R5082    NEW R1
    OLD R5084    NEW R2

    For example the reftext.log file lists

    *NOTE: Refdes C281 changed to C33
    *NOTE: Refdes U12 changed to U44
    *NOTE: Refdes C44 changed to C15

    Either of these files can easily be converted to the Capture swap file format using find
    and replace in a text editor .

    Some suggestions

    Lines can be commented out the  by adding a *
    For example find and replace "Processing" with "*Processing"
    Then changing the word OLD to the command CHANGREF
    Then replacing the word NEW with a space
     
    The result will be
     
    * Processing TOP of board, R5471 has AUTO_RENAME property but is on BOTTOM, component ignored.
    * Processing TOP of board, R5470 has AUTO_RENAME property but is on BOTTOM, component ignored.
    CHANGEREF H1  H1
    CHANGEREF R5082   R1
    CHANGEREF R5084   R2
     
    Then this SWAP file can be applied by going to tools back annotate, select the layout tab
    and point to the .SWP file you just created.
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.