• 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. How exactly does this physical constraint "Allow" function...

Stats

  • State Verified Answer
  • Replies 6
  • Answers 1
  • Subscribers 161
  • Views 3840
  • Members are here 0
More Content

How exactly does this physical constraint "Allow" function work?

Ram1234
Ram1234 over 2 years ago

Hi Team,

Good Day!...,

I couldn't figure out "how this Allow works in physical constraint" because there are multiple drop-down menus, each with a different function.

what is mean by Ts and it stands for ?

To better understand the concept, kindly explain in depth with a few examples.

Thanks in advance.....

.

  • Sign in to reply
  • Cancel
Parents
  • aniju
    +1 aniju over 2 years ago

    its a Pad-to-Pad overlap checks, please see below Pad-Pad conditions. 

    PAD-PAD:

    Constriant Set to 'Not-Allowed', if any via are overlaping with pins, it will flag the DRC.

    Constriant Set to 'VIAS_PINS_ONLY', it means pins and vias are accepatble and won't flag the DRC.

    Constriant Set to 'VIAS_VIAS_ONLY', It means Via-Via overlap is only acceptable, if via overlaps with pads will flag the DRC, similarly for microvias and pins.

    TS: Ts is a T junctions on subclass of cline segments, here are conditions.

    Set Ts as Not_Allowed. it means T- junctions are not allowed anywhere in the net but T-junction is present here and flagging the DRC.

    Set Ts as 'PINS_VIAS_ONLY'. it means T-junctions are accepted at Pins or vias. here is the DRC which is outside of PINS and VIAS.

    Set Ts as 'NOT_ALLOWED' and created the T junction at pins and flagging the DRC.

    Set Ts as 'PINS ONLY' and created T joint at via and flaging the DRC.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
  • Ram1234
    0 Ram1234 over 2 years ago in reply to aniju

    Hi aniju

    Good day!...

    Thanks for your response,

    Can you please explan in detail for the below one 

    "MICROVIAS_MICROVIAS_ONLY
    MICROVIAS_MICROVIAS_COINCIDENT_ONLY "

    Thanks .

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • aniju
    0 aniju over 2 years ago in reply to Ram1234

    Here are the details.

    MICROVIAS_MICROVIAS_ONLY - its only accepts microvia-microvia direct connections can be formed.

    MICROVIAS_MICROVIAS_COINCIDENT_ONLY - Specifies that microvia-microvia direct connections can be formed, only if the microvias are co-incident

    Constriant set to 'NOT_ALLOWED' overlapping uvia's [micro via defined for 1 to 2 layers] (MICROVIAS_MICROVIAS ONLY) and flagging the drc.

    Constraint set to 'MICROVIAS_MICROVIAS_ONLY',uvia-uvia overlap is not flagging the drc.

    Constriant set to 'MICROVIAS_MICROVIAS_COINCIDENT_ONLY', In this condition, uvias/uvias overlap each other will accepts and it won't flag the DRC.

    here is the image, uVIA overlap is not flaging the drc and other condition flagging the drc because both uvias are not coincidents.

    Please let us know if you have further queries.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Ram1234
    0 Ram1234 over 2 years ago in reply to aniju

    Hi aniju

    Thanks, great work. I received a clear answer to the questions.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Ram1234
    0 Ram1234 over 2 years ago in reply to aniju

    Hi aniju

    Thanks, great work. I received a clear answer to the questions.

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

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

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