Jim, I don't my customer does, the purpose of the property is to eliminate the need for different pcb symbols when the only difference is the height. For part symbols without varying heights it does not make sense. Gerry Meier, Sr. PCB Designer Freedom CAD Services. Inc Voice: (256) 776-7470 or (603) 864-1350 Email:gerry.meier@xxxxxxxxxxxxxx Skype: rgmeier3 visit us at http://www.freedomcad.com From: icu-pcb-forum-bounce@xxxxxxxxxxxxx [mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Wages Sent: Tuesday, April 20, 2010 5:36 PM To: icu-pcb-forum@xxxxxxxxxxxxx Subject: [PCB_FORUM] Re: Orcad to Allegro Height property Gerry, I'm sorry I can't help you with this, but I must admit I am curious as to why you would want to assign a height property in the schematic. Just curious. Best of luck on your search Jim From: icu-pcb-forum-bounce@xxxxxxxxxxxxx [mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Gerry Meier Sent: Tuesday, April 20, 2010 5:29 PM To: icu-pcb-forum@xxxxxxxxxxxxx Subject: [PCB_FORUM] Orcad to Allegro Height property All, 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 component property. But I have not been able to get it to replace the Package_height_max property for DRC checking. If anyone has this working please let me know the steps required. Thanks, Gerry Below is an excerpt from the props ref document. I know it is written for Concept but this should work for Orcad too. HEIGHT 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 precedence. ■ 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. Gerry Meier, Sr. PCB Designer Freedom CAD Services. Inc Voice: (256) 776-7470 or (603) 864-1350 Email:gerry.meier@xxxxxxxxxxxxxx Skype: rgmeier3 visit us at http://www.freedomcad.com From: icu-pcb-forum-bounce@xxxxxxxxxxxxx [mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Dave Seymour Sent: Friday, April 09, 2010 12:31 PM To: icu-pcb-forum@xxxxxxxxxxxxx Subject: [PCB_FORUM] Re: Constraints From Orcad => Allegro Orcad has no "concept" of an XNET. This is a pain. We ended up only being able to put properties on the input or the output of a series resistor or cap. There is a good little paper available on this problem. http://www.alspcb.com/pdfs/OrCAD_xNets.pdf and the problems of maintaining and linking netlists. Hope this helps. Dave Seymour Ixia 919.267.4840 ________________________________ From: icu-pcb-forum-bounce@xxxxxxxxxxxxx [mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of ameehan@xxxxxxxxxxxxxx Sent: Friday, April 09, 2010 1:11 PM To: icu-pcb-forum@xxxxxxxxxxxxx Subject: [PCB_FORUM] Constraints From Orcad => Allegro I'm still looking for differences between ConceptHDL and Orcad, but I'm rewording my question to simplify the request. Which constraints can NOT be passed from Orcad to Allegro that ConceptHDL easily passes? Thanks for any info - we're trying to decide whether or not to switch from Orcad to Concept, and I'm not finding many advantages to the switch so far. Thanks. Alexis Meehan, Opnext Inc. ----------------------------------------------------------- To subscribe/unsubscribe: Send a message to icu-pcb-forum-request@xxxxxxxxxxxxx with a subject of subscribe or unsubscribe To view the archives of this list go to //www.freelists.org/archives/icu-pcb-forum/ Problems or Questions: Send an email to icu-pcb-forum-admins@xxxxxxxxxxxxx ----------------------------------------------------------- This correspondence and any attachments are considered confidential. If you are not the intended recipient, please notify Freedom CAD Services, Inc. immediately by either replying to this message or by sending an email to operations@xxxxxxxxxxxxxx; please destroy all copies of this message and any attachments. Thank you.