Stats

More Content

How to change the DFA_DEV_CLASS for individual symbol that shared same COMPONENT TYPE

ENEGUE

Hello Everyone,

Scenario, i got two 0402 component sharing same symbol with two different supplier, one of them with higher package/footprint tolerance. Theoretically, designer is advice to space out the component with Hi-Tolerance.

Hence i try to cater this by using skill to change the symbol definition properties DFA_DEV_CLASS then use DFA table to catch the DRC whenever designer place the Hi-Tolerance part too close with one another.

I managed to change the DFA_DEV_CLASS using the axlDBAddProp->  axlDBAddProp(same_sym_pn->symbol->definition '("DFA_DEV_CLASS" "CHIP_0402_HTOL")), but this method will apply to all the same symbol name.

Is there a way only change individual symbol DFA_DEV_CLASS properties? 

Any other suggestion is welcome too.=)

Thanks,

Eugene

  • digital1
    0

    if you use ipc names for your footprint then you wouldnt have this problem ipc names are resc0402_height for resistors or capc0402_height for capacitors where height is the height of the component 

    chip_0402 is not a recognised name and will cause problems for you in the future as is what is happening now

  • ENEGUE
    0 in reply to digital1

    Hello, 

    Thanks for your input, possible to elaborate more? current plan is to use DFA to catch the distance between H-Tolerance component with others. As much as i know DFA table is refer to component DFA_DEV_CLASS, may i know how does IPC name able to help in this case?

    Eugene 

  • K3PO
    0 in reply to digital1

    Some organizations have their own naming scheme so using IPC guidelines isn't always possible. I have essentially the same question, how to modify/change the DFA class for a symbol in a design (or create a local symbol and modify that)?

  • K3PO
    0

    It doesn't appear that you can overload the symbol property from a design.brd as it is applied at the symbol level.

    One workaround to this might be to make a local library and create a <symbol_name>_DFA_DEV_CLASS symbol and use it as an alternate.

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.