• 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. Regarding Reference Designator / reuse / renumber /...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 163
  • Views 20599
  • 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

Regarding Reference Designator / reuse / renumber /...

archive
archive over 17 years ago

My quesiton is the following, and is looking for any comments and experience.

I am converting from Orcad( Design Entry CIS) to Concept( Design Entry HDL) for schematics entry. From Orcad, I am able to renumber the whole schematic, or set all reference designator to ?, so that I can update the entir design.

Now, in DE HDL, I see that reference designator started to be ?, and after I "export physical", I can then see the updated refdes like R1, R2..etc.

How do I setup so that I can see all the reference designator converted to ? such as R?, U?, D?..etc.

Also, I am looking for refdes reuse setup. For example, I have deleted R5 and R7, how to I make the later added refdes does not use R5 and R7, but continue from the largest value. Or, vise versa.

Any ideas?
Your helps are much appreciated.


Originally posted in cdnusers.org by jasonhuang@mic.com.tw
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Hi Jason

    There's 2 levels of property in DEHDL - soft and hard. Soft properties are typically system assigned (like by the packager when Export Physical is run), and these soft properties do not need to be set (can have a value of ?). Hard properties are set by the user and need to have a value (other than ?) otherwise an error is generated on Save in DEHDL.

    The LOCATION property is a hard property, the equivalent soft property is $LOCATION - so in the sch everything that has a LOCATION property needs to have a value set to save without an error.

    It sounds like your schematic used hard LOCATIONS - which leaves you with 2 options:-

    1. Manually set all the LOCATION properties
    2. Change the LOCATION property to $LOCATION (using Global Update)

    The second is the easiest - once this is done the sch should save and export physical OK (as long as there are no other errors), and the $LOCATION property will be populated by backannotation.

    Cheers
    Andy


    Originally posted in cdnusers.org by andrewjw
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    Hi Jason

    There's 2 levels of property in DEHDL - soft and hard. Soft properties are typically system assigned (like by the packager when Export Physical is run), and these soft properties do not need to be set (can have a value of ?). Hard properties are set by the user and need to have a value (other than ?) otherwise an error is generated on Save in DEHDL.

    The LOCATION property is a hard property, the equivalent soft property is $LOCATION - so in the sch everything that has a LOCATION property needs to have a value set to save without an error.

    It sounds like your schematic used hard LOCATIONS - which leaves you with 2 options:-

    1. Manually set all the LOCATION properties
    2. Change the LOCATION property to $LOCATION (using Global Update)

    The second is the easiest - once this is done the sch should save and export physical OK (as long as there are no other errors), and the $LOCATION property will be populated by backannotation.

    Cheers
    Andy


    Originally posted in cdnusers.org by andrewjw
    • 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