[PCB_FORUM] Re: Passing physical and spacing constraints from Orcad to Allegro

Flow still works the same.  when upreving from 15.x to 16.x be sure to:

1)      Uprev in Allegro

2)      Back annotate to OrCAD


Do not forward annotate an existing design with net and spacing properties.
You'll unwind for hours. J

 

Other than that. use the NET_PHYS/SPACING like normal.  No need to map it to
PhysicalCSET/SpacingCSET.

 

From: icu-pcb-forum-bounce@xxxxxxxxxxxxx
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Christopher Nunn
Sent: Wednesday, March 11, 2009 11:46 AM
To: icu-pcb-forum@xxxxxxxxxxxxx
Subject: [PCB_FORUM] Passing physical and spacing constraints from Orcad to
Allegro

 

Hi,

 

We have just gotten our engineers trained to add NET_PHYSICAL_TYPE and
NET_SPACING_TYPE properties (as well as prop dly, rel prop dly, etc.) to
their Orcad schematics.  It has been very helpful in implementing Part 68
rules in our designs, among other things.

 

Now that we are moving to allegro version 16.x, we are wondering if
NET_PHYSICAL_TYPE and NET_SPACING_TYPE properties will continue to be
supported.  It does appear that an existing design has mapped properly to
the new Constraint manager physical and spacing heirarchies.

 

Orcad has the option of adding an ECSET at the schematic level, but not a
PhysicalCSET or SpacingCSET.

 

I would like to know if other users who have physical and spacing
constraints coming from their Orcad schematics are doing anything different
in light of the new Constraint Manager System in version 16.x

 

Thanks,

Chris

Other related posts: