• 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. PCB Design
  3. Issue with 3D ( IDF(EMN,EMP)

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 168
  • Views 8404
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issue with 3D ( IDF(EMN,EMP)

Raam
Raam over 14 years ago

I am having some issue with IDF file and details given bellow.

In Footprint at placebound property i am assigning maximum height of the component and also the placebound area i am creating larger size than the actual body size, because this shows the package to package separation error, so in the IDF file obviously component will have approximate (larger) size with correct height which i given and this makes problem in CAD like showing the component hitting with encloser

My requirements:.

Any one of the actual body shape should have the property of max-height, which is going to support IDF file.

Other one of the shape should have the property of package clearance, which supports to show the package to package error.

Please any body give me remedy,

 

  • Cancel
  • djhutchi
    djhutchi over 14 years ago

    Raam,

    Here is my suggestion, based upon what we have discovered using 16.3:

                   Make your place_bound_top shape match the actual package body outline

                   Make a dfa_bound_top shape that includes the place_bound_top and pin extents

                   Create dfa spacing table to specify the package clearances between different package types

    By default the IDF output uses the DFA_BOUND outlines, not the PLACE_BOUND, you can change that with the following Allegro variables:

                   set idf_place_bounds_bottom = PLACE_BOUND_BOTTOM

    set idf_place_bounds_top = PLACE_BOUND_TOP

    Also, by default the IDF output uses the HEIGHT property attached to the component definition, not the height attached to the place_bound shapes, to disable that set the following Allegro variable:

    set idf_ignore_comp_height

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oscar migs
    oscar migs over 14 years ago

    Raam,

     

    Have you defined the minimum height for PACKAGE KEEPOUT/TOP shape?

    The maximum height defined by IDF is really the minimum height.

     

    Best,

    -oscar

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oscar migs
    oscar migs over 14 years ago

    Hi Raja,

     IDF has a limitation of defining only the maximum height for all objects.

     Turn on the Package Keepout Top or Bottom layer and assign a minimum height property, which is the maximum height..

     Best of luck,

    -oscar

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • steve
    steve over 14 years ago

    In PCB Editor you can have multiple place_bound_top shapes and you can use package_height_min and max to control the overlaps so you could specify the actual component body and the max height but use a different shape with a max height of zero for the PCB keepout area. The alternative would be to keep the place bound as is and when the IDF file is imported into the 3D Mechanical Tool (Pro-E or Inventor etc) then have an actual model created (in a MCAD library) that is used instead of the standard 3D block created by the IDF. I think all you need to do is have a 3D model called the same as the footprint name (i.e. SOIC20 for both PCB and MCAD).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Raam
    Raam over 14 years ago
    Can u please guide me, how to set the variables for the following?

    set idf_place_bounds_bottom = PLACE_BOUND_BOTTOM

    set idf_place_bounds_top = PLACE_BOUND_TOP

    set idf_ignore_comp_height
    • Cancel
    • Vote Up 0 Vote Down
    • 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