• 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. Import Design: Reference Designators

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 166
  • Views 13922
  • 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

Import Design: Reference Designators

dsone1
dsone1 over 10 years ago

Hi,

       I have an existing Allegro HDL schematic design (Project A) and PCB (.brd). I'm not starting a new design (Project B). The starting point for Project B is an internal project template (blank). As Project B will be heavily based on Project A I wish to start off importing this design into Project B. Project A is complex Hierarchical design, once I copy the top level sheet into Project B I lose the original reference designators.

1. Am I correct in thinking that there is now way to avoid this happening using a complex hierarchical design?  

2.  If it is unavoidable to loose the designators on import, should I be able to copy over the .brd file from Project A and back annotate the Reference Designators from the Project A .brd into the Project B schematic?

I cannot seem to find a way to make this work, we will encounter this scenario regularly within our organization, where an existing pcb is reused with some modification. It seems if the Reference Designators in the schematic are lost, then when I repackage then the Project A .brd file is not much use to Project B and the layout would have to be restarted.

 

  • Cancel
Parents
  • redwire
    redwire over 10 years ago

    This should work.  What happens however is that with the complex hierarchy designs you need to push the physical reference designators back into the logical design..  This is not well documented.

    Assume "A" schematic is sync'd with "A" layout. If not be sure to backannotate "A" layout into "A" schematic first.

    Once that is done then each schematic symbol will have two reference designators.  You now need to go to the menu and select "Accessories->Transfer Occ. Prop to Instance->Push Occ Prop into Instance.

    Follow the prompts and choose the first option and checkbox.

    Now you should have a "physical" schematic of the board that can be copied and will not lose the reference designators.  Make sure you have your option set under Preferences->Miscellaneous to "Preserve reference on copy"

    Now you can copy all or part of "A" into "B" and also copy all or part of "A" layout into "B" layout.

    See if this procedure clears up the issue.  Otherwise post back up.  Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • redwire
    redwire over 10 years ago

    This should work.  What happens however is that with the complex hierarchy designs you need to push the physical reference designators back into the logical design..  This is not well documented.

    Assume "A" schematic is sync'd with "A" layout. If not be sure to backannotate "A" layout into "A" schematic first.

    Once that is done then each schematic symbol will have two reference designators.  You now need to go to the menu and select "Accessories->Transfer Occ. Prop to Instance->Push Occ Prop into Instance.

    Follow the prompts and choose the first option and checkbox.

    Now you should have a "physical" schematic of the board that can be copied and will not lose the reference designators.  Make sure you have your option set under Preferences->Miscellaneous to "Preserve reference on copy"

    Now you can copy all or part of "A" into "B" and also copy all or part of "A" layout into "B" layout.

    See if this procedure clears up the issue.  Otherwise post back up.  Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • 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