• 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
  • RFinley
    RFinley 29 days ago

    Don’t think probing more than 10-20% of nets is cost effective.  Most SMT errors are caught by AOI/xray. 

    We drive probe placement from the schematic to verify we didn’t drop a MOSI signal (again) and it helps us reuse our test investment on future configurations.  Time-to-test will cause conversations you don’t want to have with an annoyed operations/finance team.  Our test fixtures are about $10K each.   It’s an expensive bottleneck to address if you need six of them running in parallel as loading firmware takes forever..

    Things on our checklist:

    Always have extra system ground probes near signal probes.  But, everyone likes fewer probes to get damaged/bent and don't understand grounding.   You can no-load that probe later.   Should you have ESD protection on your test probes?  Keep reading.

    Basics of test:  turn on the DUT.  Verify power rails.  Measure current at the main input.  Make sure probes and fixture can supply enough power to program everything.  Verify power-on-reset/watchdog circuits.  Have hooks to program and communicate everything.  It’s pre-programmed on tape-and-reel before SMT until its no longer available.

    With multiple ARM SOCs on the same board, we discovered why we shouldn’t multiplex the UART lines for test.  The ICs most susceptible to ESD failures is the DPDT switch on the UART lines controlled by the test system.  But, having every debug UART accessible supports remote debugging when things stopped working at an overseas production line. 

    Lastly, ODMs love robust and portable test fixtures that can be moved around the factory floor and still work.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • RFinley
    RFinley 29 days ago

    Don’t think probing more than 10-20% of nets is cost effective.  Most SMT errors are caught by AOI/xray. 

    We drive probe placement from the schematic to verify we didn’t drop a MOSI signal (again) and it helps us reuse our test investment on future configurations.  Time-to-test will cause conversations you don’t want to have with an annoyed operations/finance team.  Our test fixtures are about $10K each.   It’s an expensive bottleneck to address if you need six of them running in parallel as loading firmware takes forever..

    Things on our checklist:

    Always have extra system ground probes near signal probes.  But, everyone likes fewer probes to get damaged/bent and don't understand grounding.   You can no-load that probe later.   Should you have ESD protection on your test probes?  Keep reading.

    Basics of test:  turn on the DUT.  Verify power rails.  Measure current at the main input.  Make sure probes and fixture can supply enough power to program everything.  Verify power-on-reset/watchdog circuits.  Have hooks to program and communicate everything.  It’s pre-programmed on tape-and-reel before SMT until its no longer available.

    With multiple ARM SOCs on the same board, we discovered why we shouldn’t multiplex the UART lines for test.  The ICs most susceptible to ESD failures is the DPDT switch on the UART lines controlled by the test system.  But, having every debug UART accessible supports remote debugging when things stopped working at an overseas production line. 

    Lastly, ODMs love robust and portable test fixtures that can be moved around the factory floor and still work.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Children
  • excellon1
    excellon1 28 days ago in reply to RFinley

    Hi John,

    Typically I go with options 1, 3 & 4

    Option 1 is usually for only a few dedicated test points that it makes sense to have driven by the schematic.
    Option 3, is kind of a norm in that all vias are left open, usually plated with ENIG.
    Option 4, I use alot. For Communications equipment aka RF based that contain mostly mini and large planes I use a simple circle shape drawn in on the solder mask layer. Works well, Fast to do.

    Bed of nails are less common today for ICT due to the cost, but for industrial high reliability boards & customer may what it. They don't care about the cost Slight smile, In that regard the Allegro Route Editor "Specctra" has a highly capable Testpont generation option. Works very well !!

    Best regards.

    • Cancel
    • Vote Up +1 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.

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

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