• 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. Keep part of the $LOCATION the same in attribute

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 164
  • Views 11025
  • 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

Keep part of the $LOCATION the same in attribute

BaoNguyen1
BaoNguyen1 over 4 years ago

Hi,

We are moving from OrCAD to Design Entry HDL and have a question. 

We have four pages that are designed for 4 similar sites on the physical layout. Since they are the same, we just add a suffix to each signal name for each page. Example for PG signal, page1: PG_1, page2: PG_2 ... We would like to be able to do the same thing for other component like IC, cap, resistor ... Best if we can some what automate the process so we can just do one sheet and modify for the other 3 sheets.

I found in attribute the $LOCATION, and change the value to C?_1, and C?_2 with hope that the system will just fill in the ? and keep everything else intact but it didn't work. The Packager just replace it with normal increment number.

Thank you

Note: We found away to do the signal name, but not yet reference designator.

  • Cancel
  • BaoNguyen1
    BaoNguyen1 over 4 years ago

    Found a solution in Packager advanced option

    File -> Export Physical -> Select Preserve / Repackage -> Advanced -> Layout

    Paste in: ($PHYS_DES_PREFIX)[0-9](00)_($PAGE)

    • ($PHYS_DES_PREFIX) keep the C, L, R in front of component
    • [0-9] specify the range the number the increment can use. Should not change
    • (00) start of the counter
    • _($PAGE) create underscore page number
    • Cancel
    • Vote Up 0 Vote Down
    • 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