Stats

  • Replies 7
  • Subscribers 159
  • Views 4117
  • Members are here 0
More Content

Read drill tolerance and DEFAULT_INTERNAL pad(s) from padstack

stburton

I'm trying to get both the associated hole tolerance from a padstack definition and the defined "DEFAULT INTERNAL" pad(s) using the Allegro SKILL api.

I am able to extract all other portions of the padstack definition except for these two pieces of information. I have tried iterating over the "pads" property of the padstack but the "DEFAULT INTERNAL" pads are mysteriously absent. Similarly, axlDBGetPad is not able to retrieve the pads (as far as I can tell). There are definitely default internal pads defined for the padstacks.

For the drill tolerance I can't seem to find anything about how to retrieve the tolerance values in the documentation. All other drill properties (drillOffset, drillDiameter, etc.) are associated with the padstack definition object and are perfectly readable, but the hole tolerance is mysteriously missing.

I've scoured the Allegro SKILL documentation but can't seem to find any information on these issues. 

Any help or advice would be appreciated. Thank you. 

I'm using Allegro 16.3

Parents

  • Thanks for your reply Dave. 

    Ah, I feared the drill tolerances might not be accessible as simple properties.

    The method you outlined for the default internal pads does not seem to work in my case. Specifically, I'm attempting to read the default internal pads in the context of a package symbol loaded in the symbol editor. When accessing the padstack pads (padstack->pads) through the SKILL console it only retrieves pads for following layers:

     

    • ETCH/TOP
    • ETCH/BOTTOM
    • PIN/SOLDERMASK_TOP
    • PIN/SOLDERMASK_BOTTOM
    • PIN/PASTEMASK_TOP
    • PIN/PASTEMASK_BOTTOM
    • PIN/FILMMASKTOP
    • PIN/FILMMASKBOTTOM

     

     
    However, if I view the padstack in the padstack editor there are DEFAULT INTERNAL pads defined, I just can't seem to get at them from the SKILL API. It does not seem to matter if I'm accessing the padstack definition directly from the design object or from one retrieved by a call to axlLoadPadstack. Again, I'm running in the context of the symbol editor and I don't have any additional internal layers defined. So, in this case there are no actual instances of pads for internal layers but I would still like to be able to determine what the default internal pads are. I'm really hoping I don't have to do something hacky like create an internal garbage layer just to read the data.
     
    Thanks.
     

     

Reply

  • Thanks for your reply Dave. 

    Ah, I feared the drill tolerances might not be accessible as simple properties.

    The method you outlined for the default internal pads does not seem to work in my case. Specifically, I'm attempting to read the default internal pads in the context of a package symbol loaded in the symbol editor. When accessing the padstack pads (padstack->pads) through the SKILL console it only retrieves pads for following layers:

     

    • ETCH/TOP
    • ETCH/BOTTOM
    • PIN/SOLDERMASK_TOP
    • PIN/SOLDERMASK_BOTTOM
    • PIN/PASTEMASK_TOP
    • PIN/PASTEMASK_BOTTOM
    • PIN/FILMMASKTOP
    • PIN/FILMMASKBOTTOM

     

     
    However, if I view the padstack in the padstack editor there are DEFAULT INTERNAL pads defined, I just can't seem to get at them from the SKILL API. It does not seem to matter if I'm accessing the padstack definition directly from the design object or from one retrieved by a call to axlLoadPadstack. Again, I'm running in the context of the symbol editor and I don't have any additional internal layers defined. So, in this case there are no actual instances of pads for internal layers but I would still like to be able to determine what the default internal pads are. I'm really hoping I don't have to do something hacky like create an internal garbage layer just to read the data.
     
    Thanks.
     

     

Children
No Data
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.