• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. Update Package_Height_Max from Orcad Capture

Stats

  • State Suggested Answer
  • Replies 12
  • Answers 2
  • Subscribers 162
  • Views 4632
  • Members are here 0
More Content

Update Package_Height_Max from Orcad Capture

EA20241106783
EA20241106783 9 months ago

I am using OrCAD PCB Designer Standard version 17.4-2019. I want to force update the Package_Height_Max property on the place bound top shape. The footprint library that we've created has that property set in the dra file, but I'd like to override that from capture so I can be certain that the height is correct.

This is coming from a place where we have created a very large footprint library over that past ++ years. Everyone who creates a new footprint is supposed to make sure that we add Package_Height_Max to the footprint, but of course footprints get reused for various parts, not all of which will have the same package height. What I want to do is export a list of package heights from our part database and then import the package heights into Capture and override the package height in the footprint.

I have found a post here  Using Height Property from Orcad Capture which says its not possible, but it also says its from 15 years ago, so maybe things have changed?

  • Sign in to reply
  • Cancel
Parents
  • SL202501027531
    0 SL202501027531 8 months ago

    Hello, have you found a solution for this question?

    I used PADS before and it can assign different height for different part with the same PCB footprint. But in Allegro I can only change the package height in every single footprint. This is very troublesome when building PCB library because different manufacturer have different height even they use same footprint. It will save much time if I can update height in Orcad Capture.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • EA20241106783
    0 EA20241106783 8 months ago in reply to SL202501027531

    No - I have not found a work around for this. The only way I know is to do it manually by either modifying the dra/footprint and refreshing it in the design or, in the design, select then right click on the place bound shape and modifying the package_height_max. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • EA20241106783
    0 EA20241106783 8 months ago in reply to SL202501027531

    No - I have not found a work around for this. The only way I know is to do it manually by either modifying the dra/footprint and refreshing it in the design or, in the design, select then right click on the place bound shape and modifying the package_height_max. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • SL202501027531
    0 SL202501027531 8 months ago in reply to EA20241106783

    Hi EA, I read the post you attached 15 years ago and found a solution:

    1. assign "height" property in part in Orcad

    2. change the netlist configuration file which is in C:\Cadence\SPB_23.1\tools\capture\allegro.cfg

    add "HEIGHT=YES" in [ComponentDefinitionProps]

    This makes the netlist include "height" property

    After Allegro Netin, you can find "height" when show symbol element.

    3. Keep  the place bound shape of .dra do not have package_height_max defination, or it will cover the height you assign in Orcad.

    Then in Allegro's 3D viewer I can see the component height change to the height I assign.

    In Orcad, you should only add a property line when building part library. I think it's easy compared to modifying the dra/footprint for any single height.

    Hope to help you

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information