Stats

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

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

 

 

 

 

 

Parents
  • EngineerPerson

    WARNING!  If you netlist a complex hierarchical schematic and layout a PCB, you will be unable to make changes to the schematic after the fact.  From what I can tell, any time you cut and paste a hierarchical block (to move within a schematic page or move to another page, for example), the OCCURRENCE properties (your actual reference designators used during layout) are DELETED and overwritten by a random new reference designator or question mark (depends on the annotation checkbox), and all parts in the hierarchical block are assigned new ID values.  This deletes any correlation to the physical circuit that you have already laid out on the board.  For this reason, and as of 4/8/2016, I do not think that the Cadence software actually supports maintainable and robust complex hierarchical circuit board design.

    Please somebody prove me wrong here, as I'm in the process of undoing 2 months of work on an incredibly complex hierarchical design, to flatten the design, BEFORE we can even start working the layout...  This is a severe disappointment, and has set our project back by months.  I would have preferred it if Cadence just admitted that hierarchical designs are not supported, so that I would not have gone down the path of a complex hierarchical design...

Reply
  • EngineerPerson

    WARNING!  If you netlist a complex hierarchical schematic and layout a PCB, you will be unable to make changes to the schematic after the fact.  From what I can tell, any time you cut and paste a hierarchical block (to move within a schematic page or move to another page, for example), the OCCURRENCE properties (your actual reference designators used during layout) are DELETED and overwritten by a random new reference designator or question mark (depends on the annotation checkbox), and all parts in the hierarchical block are assigned new ID values.  This deletes any correlation to the physical circuit that you have already laid out on the board.  For this reason, and as of 4/8/2016, I do not think that the Cadence software actually supports maintainable and robust complex hierarchical circuit board design.

    Please somebody prove me wrong here, as I'm in the process of undoing 2 months of work on an incredibly complex hierarchical design, to flatten the design, BEFORE we can even start working the layout...  This is a severe disappointment, and has set our project back by months.  I would have preferred it if Cadence just admitted that hierarchical designs are not supported, so that I would not have gone down the path of a complex hierarchical design...

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.