• 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. Occurrences reference designator assignment in complex hierarchical...

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 168
  • Views 22566
  • 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

Occurrences reference designator assignment in complex hierarchical design

coronas
coronas over 10 years ago

Hi all,

consider this AN

when he says:

"Note: As a part will have more than one occurrence in a complex hierarchical design, it is essential that all these occurrences have a unique reference designator in the design. For this, the yellow columns for the parts must have unique reference designator. Therefore, for a complex hierarchical design, the preferred mode of annotation is Occurrence. This ensures that each occurrence gets a unique reference designator."

what  does it means?
when in occurrence annotation mode,
1)sub-circuit reference designators change automatically at each hierarchical block placement/copy action
2)user have to change sub-circuit reference designators at each hierarchical block placement/copy action

I'm asking this because maybe I misunderstand and / or I forgot to set something
if I copy a hierarchical block, the reference designator does not change automatically, and I want that it does.

I had some problems also manually change the reference designator in sub-circuits by double click text to open the display properties dialog, changes made in one occurrence affects other occurrences and other weird things ...
the only way is to change the reference designator manually in property editor view.

i'm using Orcad Capture 16.6-S032.

Thanks

 

 

 

 

 

  • Cancel
Parents
  • oldmouldy
    oldmouldy over 9 years ago
    If you understand how the software works, you will appreciate that this behaviour is not "a bug". Complex hierarchy, repeated h-blocks, in Capture has one copy of the schematic, in reality this is the "Instances" (original) version, and "n" sets of properties for that schematic, the "Occurrences" properties, one set of properties for each h-block that references the schematic. When the schematic is copied, to paste "somewhere else", the "Instances" version is actually copied, including the original Instances properties, if any - any other implementation of "copy" would involve determining "which" set of Occurrences properties were to be retained, this wouldn't be impossible to implement but tricky to make fool proof. If another h-block that references the schematic is added, another set of properties are added to the "Occurrences" properties, no copy of the underlying schematic is made. Maybe more control of Annotation would be the way to go.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • oldmouldy
    oldmouldy over 9 years ago
    If you understand how the software works, you will appreciate that this behaviour is not "a bug". Complex hierarchy, repeated h-blocks, in Capture has one copy of the schematic, in reality this is the "Instances" (original) version, and "n" sets of properties for that schematic, the "Occurrences" properties, one set of properties for each h-block that references the schematic. When the schematic is copied, to paste "somewhere else", the "Instances" version is actually copied, including the original Instances properties, if any - any other implementation of "copy" would involve determining "which" set of Occurrences properties were to be retained, this wouldn't be impossible to implement but tricky to make fool proof. If another h-block that references the schematic is added, another set of properties are added to the "Occurrences" properties, no copy of the underlying schematic is made. Maybe more control of Annotation would be the way to go.
    • 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