Comments on: Hierarchies in Orcad schematics: Please, don’t

By: Nicolas PERRIN

Nicolas PERRIN — Wed, 26 Oct 2022 09:47:35 +0000

Orcad way of naming net is pretty straightforward in herarchical designs.
Net name can come from upper level.
If there is a conflict, net is renamed NAME_INSTANCENAME

You can find PCB nets in schematics by searching by flat nets.

Sometimes in my schematics, the same page is used 16 times. In this case having a hierarchical schematic is a must.
It helps also to have consistency accros schematics and it facilitate schematic page reuse.
I would not live without hierarchical design :)

By: David Clarke

David Clarke — Wed, 30 Oct 2019 16:45:15 +0000

Mmm, we are going the other way.
Dx to Orcad, which does not look good to me.

The only way to create hierarchy is top-down. If you have the right tools, they will add hierarchy ports with the correct name as you add the connections. Push down and the job’s a good’un.

Good point about navigating PDFs. I hate them.
It would help a lot if the PDF printer added the page number to each hierarchy block, but then that would be far too hard to automate, eh?

By: Dave Anderson

Dave Anderson — Thu, 24 Aug 2017 01:04:26 +0000

So true! And if you think it’s bad in Orcad, pray you never get forced to use (x)DxDesigner!