I would like to use the Height property in Orcad Capture and transfer it to Allegro PCB Editor. I am able to get the height property exported from Orcad and attached as a property in Allegro as a componemt property.But I have not been able to get it to replae the Package_height_max property for DRC checking. If anyone has this working please let me know the steps required.
Below is an excerpt fro mthe props ref document. I know it is written for Concept but thisshould work for Orcad too.
The HEIGHT property, attached to component definitions in a schematic system and a value
maintained in user units in the database, controls package height and can be sourced from
the Allegro Design Entry HDL Part Table File (PTF). For discrete parts, whose physical
footprints are identical except for height variations due to multiple manufacturers, use the PTF
package height model, which minimizes design disruption as front-end librarians may already
be using this property for IDF support.
When creating the physical footprint, ensure that no PACKAGE_HEIGHT_MAX property is
assigned to place-bound shapes. Only those symbols whose height is driven from the
schematic require this change. (Any existing HEIGHT properties assigned to package
symbols take precedence.)
To allow the DRC system to use the component-definition HEIGHT property driven from the
PTF, choose File – Import– Logic (netin command) to map the component-definition
HEIGHT property currently used by the IDF interface to the PACKAGE_HEIGHT_MAX
property on the component definition.
Because the HEIGHT property is defined as a component property in Allegro, it may be
passed forward to Allegro from an Allegro Design Entry HDL netlist. Its value cannot be
changed in the Allegro database as it is device and netlist driven.
Define the HEIGHT property in one or more of the following locations. When the design is
packaged, Packager XL applies the first HEIGHT value found in the following order of
■ as a body property in the symbol definition
■ in the part table as either a key or injected property
■ the chips.prt file as a body property
However, the component may have only one HEIGHT property value. If the component’s
actual height is irregular, the varying heights of its profile cannot be described using a
HEIGHT property, and component-to-component or component-to-package-keepout DRC
audits ignore the HEIGHT property’s value.