• 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. Work on the Components' property

Stats

  • Replies 5
  • Subscribers 158
  • Views 7304
  • Members are here 0
More Content

Work on the Components' property

archive
archive over 19 years ago

what difference with the properties, which attached to component instance and component definition?
The property of component instance is general property, which can edit by "poterty edit", like as "Fixed".
But the property of component definition is read only, like as "part_number", "alt_symbols".

For these properties, how about the command "axlSelectByProperty" and "axlSelectByProperty" work?


Originally posted in cdnusers.org by leonlee
  • Sign in to reply
  • Cancel
  • archive
    archive over 19 years ago

    Component definition properties are defined in the components device file and passed to the board through a netlist import. Each instance of any particular component/device has all of the common component definition properties of that particular component/device.
    Component definition properties cannot be modifieed through the Allegro property edit command.

    Component instance properties may also be passed forward from the netlist and may be defined in Allegro using property edit.

    The Skill function axlSelectByProperty can be used to select either component definition or component instance properties.

    For example I have a very simple database with exactly two unique component definitions. Each of these definitions has PART_NUMBER property. I have defined a property "SPECIAL" on one of the schematic instances and packaged this "SPECIAL" property forward to Allegro. I have defined a property "COMMENT" on one of the placed component instances in Allegro.

    axlSelectByProperty("compdef" "PART_NUMBER") returns the two compdef dbids.

    axlSelectByProperty("component" "SPECIAL") returns the one component dbid.

    axlSelectByProperty("component" "COMMENT") returns the other component dbid.


    Originally posted in cdnusers.org by AshCan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 19 years ago

    Ok, it's clear for the two kinds properties.
    In my last post, there is a little mistake. my means another property command is "axlDBGetProperties".

    I can get the compdef or compent by both two kinds proterty("axlSelectByProperty").
    But I can't get the component definition proterty by "axlDBGetProperties".
    Do you have this issue?


    Originally posted in cdnusers.org by leonlee
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 19 years ago

    axlDBGetProperties(sym ->component ->compdef)


    Originally posted in cdnusers.org by Dave Elder
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 19 years ago

    haha, I have tried to get prpoerty for Symbol and Component by axlDBGetProperties, but ignored compdef.
    Ok, thank AshCan and Dave.


    Originally posted in cdnusers.org by leonlee
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 19 years ago

    This is exactly what you should expect. axlDBGetProperties has the limitations you observe. See the HTML at $CDSROOT\doc\algroskill for the whole story.


    Originally posted in cdnusers.org by AshCan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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