element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Testpoints for ICT testers
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 26 replies
  • Subscribers 173 subscribers
  • Views 3415 views
  • Users 0 members are here
Related

Testpoints for ICT testers

Former Member
Former Member over 14 years ago

Is there a way to systematically insert ICT testpoints onto a PCB layout

without putting a testpoint component on each net on my schematic?

Ideally I'd like to know the percent of nets covered by testpoints and

have someway to highlight or locate nets without a testpoint so I can

either add one or can decide that the particular net isn't worth the

trouble to test.

 

-Michael

 

 

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    Former Member over 14 years ago

     

    "Michael Sansom"  wrote .

    Is there a way to systematically insert ICT testpoints onto a PCB layout

    without putting a testpoint component on each net on my schematic?

     

    ......Ideally I'd like to know the percent of nets covered by testpoints

    and

    have someway to highlight or locate nets without a testpoint so I can

    either add one or can decide that the particular net isn't worth the

    trouble to test.

     

    There have been a lot of discussion on  the placement of pads and the

    validity of testing regimes but very little on the second part of the

    question.

     

    As I understand it, most of the points contacted during testing are regular

    pads. Eagle does not have a way of flagging these pads with a test point

    attribute. Hopefully this will arrive when 'pad stacks' are implemented.

     

    So, how do you analyse the layout to determine if nets have  test points or

    pads acting as testpoints or nothing suitable?

    It maybe reasonable to give a library part an 'ICT-testpoint' attribute.

    This would imply that any time it is used all its pins were useful for

    machine probing. The format of the text value within  the attribute could

    even exclude or include particular pins. Only this would not be acceptable

    for parts under heatsinks, for example. To counter this an attribute applied

    to the part on the board of  'Don't probe' could be used. Now a ULP could

    provide a listing of nets to points, close to what you were asking.

     

    I imagine something could be done with another ULP that copies these points

    designated as testpoints, and that includes vias, to a user defined layer or

    the tTest and bTest layers. A bright colour here may assist in confirming

    testpoint locations before generating a file for the fixture maker.

     

    Just some thoughts

    Warren

     

     

     

     

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Warren Brayshaw schrieb:

     

    There have been a lot of discussion on  the placement of pads and the

    validity of testing regimes but very little on the second part of the

    question.

     

    As I understand it, most of the points contacted during testing are regular

    pads.

     

    To my knowledge, this is not true. Especially in high volume ICT,

    testpoints always are separate SMD pads. This makes sure that these

    areas are always free for the test needles and have a clean, smooth

    surface. When using pads as test points, it is very difficult to get

    reproducible contact - and the needles wear out much faster due to

    horizontal forces.

     

    So, how do you analyse the layout to determine if nets have  test points or

    pads acting as testpoints or nothing suitable?

     

    If there were special ICTP objects (as suggested), it would be no

    problem to generate a list of covered and uncovered signals, including

    statistics, with a small ULP.

     

    Tilmann

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    Warren Brayshaw schrieb:

     

    There have been a lot of discussion on  the placement of pads and the

    validity of testing regimes but very little on the second part of the

    question.

     

    As I understand it, most of the points contacted during testing are regular

    pads.

     

    To my knowledge, this is not true. Especially in high volume ICT,

    testpoints always are separate SMD pads. This makes sure that these

    areas are always free for the test needles and have a clean, smooth

    surface. When using pads as test points, it is very difficult to get

    reproducible contact - and the needles wear out much faster due to

    horizontal forces.

     

    So, how do you analyse the layout to determine if nets have  test points or

    pads acting as testpoints or nothing suitable?

     

    If there were special ICTP objects (as suggested), it would be no

    problem to generate a list of covered and uncovered signals, including

    statistics, with a small ULP.

     

    Tilmann

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Former Member
    Former Member over 14 years ago in reply to Former Member

    On 12/31/2010 2:01 AM, Tilmann Reh wrote:

    Warren Brayshaw schrieb:

     

    >> There have been a lot of discussion on  the placement of pads and the

    >> validity of testing regimes but very little on the second part of the

    >> question.

    >>

    >> As I understand it, most of the points contacted during testing are regular

    >> pads.

     

    To my knowledge, this is not true. Especially in high volume ICT,

    testpoints always are separate SMD pads. This makes sure that these

    areas are always free for the test needles and have a clean, smooth

    surface. When using pads as test points, it is very difficult to get

    reproducible contact - and the needles wear out much faster due to

    horizontal forces.

     

    >> So, how do you analyse the layout to determine if nets have  test points or

    >> pads acting as testpoints or nothing suitable?

     

    If there were special ICTP objects (as suggested), it would be no

    problem to generate a list of covered and uncovered signals, including

    statistics, with a small ULP.

     

    Tilmann

     

    You can use regular SMT pads, but in general you shouldn't use vias (or

    at least the contract manufactures I use will not use them).

     

    Tilmann is right, in general you want to use a dedicated test pad that

    is separate from both your vias and your SMT pads.  The reasons are as

    follows:

     

    1.) CMs have problems with the ICT test probes sticking in the holes of

    vias.  In some cases this will result in the board getting hung up on

    the ICT test fixture when the fixture tries to open.  In my experience

    very few CMs will want to try this for this reason.

     

    2.) Some CMs will let you use SMT pads but they don't like it since they

    don't know the height of the solder "bump" precisely so they have some

    issues setting the ICT pin height.  They really don't like building a

    fixture that has a mix of dedicated ICT pads (which are unsoldered) and

    SMT pads with solder (or at least in my experience).  However, if your

    board is such that you can get good coverage from just the SMT pads this

    is an option.

     

    3.) Complicating point 2 is the fact that in general you want your ICT

    fixture probes to only interface with one side of the board (this is a

    cost and complexity issue, you can test on both sides if you're

    motivated).  If you've got a board with components on one side only,

    generally you're going to find that you want the ICT test points on the

    side opposite the components.  This also tends to take testing against

    your topside SMT pads off the table.  For a design with components on

    the top side only, you'll tend to be driven to putting all your ICT pads

    on the bottom side.

     

    -Michael

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube