• 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 are you creating your testpoints?

Stats

  • Replies 3
  • Subscribers 167
  • Views 456
  • Members are here 0
More Content

How are you creating your testpoints?

John T
John T 1 month ago

In theory we should have a testpoint for every net. How are you achieving this or coming close? There are multiple different testpoint approaches.

Let us know if you are designing by any of the following:

  1. Testpoints created in the schematic; become single pin surface components on the PCB.
  2. Assigning testpoints manually to specific component pins.
  3. Vias as testpoints with open soldermask.
  4. Other…?

Let us know if you have any problems or advice about how to approach this important part of design using the Allegro/OrCad PCB Editors. We can help the community with any questions on this.

  • Cancel
  • Sign in to reply
Parents
  • JCTEYSSIER0
    JCTEYSSIER0 30 days ago

    It depend on testpoint usage destination.Of course, all are free of soldermask Slight smile

    Testpoint for debug/measurement:

    - Added in schematic as components so it will have a refdes and appear on assembly drawing and silkscreen if available

    - Will be either a smd pad or thru pad. Were thru pad in old time; now pretty all are smd pad

    - Placed on the accessible layer. Generaly TOP

    Testpoint for bend of nails or flying probe:

    - Not in schematic

    - will use either thru pin, thru via or undrilled via. Testpoints placed on schematic for debugging purpose may aslo be used 

    - Ideally only on one face; can be both side on some case

    - big enougth for nails

    - distance between nails controled

    - distance to components body controled

    - 

    - One by net by default

    - Unconnected/unused pind have also testpoint by default

    - May have several one on some case (verry smal component value, small tolerance value, higth current, ...)

    - Personnaly i add these tespoint while routing, not at the end. May lead to heavy rework/modifications and/or impossiblity at the end of project. May have to revalidate routing on some case if added after routing completion. Testability IS a part of routing.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • JCTEYSSIER0
    JCTEYSSIER0 30 days ago

    It depend on testpoint usage destination.Of course, all are free of soldermask Slight smile

    Testpoint for debug/measurement:

    - Added in schematic as components so it will have a refdes and appear on assembly drawing and silkscreen if available

    - Will be either a smd pad or thru pad. Were thru pad in old time; now pretty all are smd pad

    - Placed on the accessible layer. Generaly TOP

    Testpoint for bend of nails or flying probe:

    - Not in schematic

    - will use either thru pin, thru via or undrilled via. Testpoints placed on schematic for debugging purpose may aslo be used 

    - Ideally only on one face; can be both side on some case

    - big enougth for nails

    - distance between nails controled

    - distance to components body controled

    - 

    - One by net by default

    - Unconnected/unused pind have also testpoint by default

    - May have several one on some case (verry smal component value, small tolerance value, higth current, ...)

    - Personnaly i add these tespoint while routing, not at the end. May lead to heavy rework/modifications and/or impossiblity at the end of project. May have to revalidate routing on some case if added after routing completion. Testability IS a part of routing.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • 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.

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

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