• 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. Different Force and Sense Line Widths using Pin Pair Physical...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 168
  • Views 18332
  • 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

Different Force and Sense Line Widths using Pin Pair Physical Constraints

jackg23
jackg23 over 14 years ago
Hi all,

I have been trying to find a method to specify different line widths for the same net. Specifically, I need a force line and sense line to be routed separately to single DuT pin. These lines should be different line widths since the force line carries high current and the sense line doesn't. I also need these different line widths to flag errors when the DRC is run if not met.

I have been doing a bit of research on this topic and have figured out how to accomplish a couple of these requirements. I found a link to an app note about using the NET_SHORT symbol to, from what I gather, merge nets at a physical padstack where all nets become electrically connected then finally connect to the DuT pin. This method is undesirable since it requires placing another component which takes room on a very dense board.

I am currently using the SYNONYM part to connect the nets together in the schematic. This unforunately merges the nets in the Physical section of the Constraint Manager and forces one line width setting for the whole net. I tried to deal with this by using Pin Pairs in the net. I was able to separate the force line width from the sense line width. When I use the autorouter, it routes the lines correctly with the different line widths.

This is great and almost what I need but it lacks any checks from the DRC if the line widths were to be changed or if it was routed by hand (my company routes most PCBs by hand due to the numerous critical traces).

In the end, I am asking: how do I force the DRC to check minimum line width against the pin pair specs and not the net specs, if pin pairs exist?

Thanks, Jack
design pics.zip
  • Cancel
Parents
  • Khurana
    Khurana over 14 years ago

    >>When routing traces (manually) between two pins of a pin pair, the line width always defaults to the NET line width, not the Pin Pair line width defined in the CS

    Thereis was a bug - ensure that you've got the latest hotfix installed.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Khurana
    Khurana over 14 years ago

    >>When routing traces (manually) between two pins of a pin pair, the line width always defaults to the NET line width, not the Pin Pair line width defined in the CS

    Thereis was a bug - ensure that you've got the latest hotfix installed.

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