The importance of test points
Hardware bring-up, firmware development and production quality control can all be aided using test points. They can make the product development process easier and helps with programming, test, calibration, and setup when the printed circuit board (PCB) gets to volume production.
What is a test point?
A test point is a small area of exposed copper you can connect a probe to – either an oscilloscope probe for development or contact pin in production, these are usually on the bottom of the printed circuit board. More complex or dense boards may have test points on both sides of the board.
Should I label test points?
Most PCBs need to go through some element of engineering test and validation. If you have the room to label these meaningfully it makes life easier and therefore make testing quicker for the engineering team during initial bring-up and debug. If there is minimal room then identifying them by a simple numerical reference is also useful.
Which signals should have test points?
Power supply rails, ground, programming connections, JTAG ports, serial communications busses, reset lines, UARTs, programmable references, interrupt lines, and other signals that could be of use to the development and production teams. It is especially important where a key signal is routed between BGA, QFN or LGA devices as without planning there would be no access to the signal.
What is the optimum number of test points?
You need just enough test points for the expected needs. The gold standard is to have a hardware bring up plan and a production test plan and ensure each necessary signal has a test point.
Test point hazards to watch out for
- Test points are an exposed copper area that could accidentally short to another test point and cause damage. Testing on the bench should ensure that the workspace is clean and has no stray wires, component leads or other boards. Conductive enclosures and heatsinks need clearance from the test points to avoid issues.
- Too many test points – A scattergun approach to test points complicates boards, perforates power and ground planes and brings little additional benefit.
- Creates stubs on high speed or controlled impedance nets. Where test points are needed they should be routed to minimise additional track stubs to prevent signal reflections degrading signal integrity and to avoid contributing to Electromagnetic Compatibility (EMC) issues.
How have test points have historically been used?
The older school of thought.
In the past test points, or test lands, were usually put on each signal junction between every component. This included a big bed of nails tester to check value and positioning of each signal component on a pcb.
This often leads to the pcb design being bigger or having a higher layer count than needed which is more expensive on material costs. Additionally, extra time ends up being spent on pcb layout and routing than is needed.
Why should I consider using test points?
Of course, some businesses use no test points. This could be because the boards are so compact that there is no room and that alternate test strategies like boundary scan are more appropriate. Sometimes test points have never been added to electronics in the product portfolio because of the products simplicity or because the expected sales volumes are very low.
The benefits of adding test points during the initial design process
Adding appropriate test points during initial design opens up the possibilities of automating test where volumes increase, where quality problems are identified or to make bring up a little easier.
Where there are no test points it’s possible to probe onto solder joints or onto larger component connections, but this can be less reliable and limits the test coverage.
How can they be used for product development purposes?
Test points are useful for development, bring-up and test. They are useful for hardware and software teams as you can solder a wire onto the test point to make monitoring easy during bring-up. The same points can also be useful later to diagnose issues found during environmental testing.
Are test points useful for quality control?
Quality control gold for the production line
The real value comes in the production environment where you can use test points for quality control or for programming, setup, or calibration. Repeatable automation of these tasks can speed up the process, reduce costs and de-skill engineering led tasks to allow non-technical staff to reliably use.
Do they speed things up?
For the record…
Having test points can speed up development and more importantly provide you with quality control reassurance. It also gives you the ability to automate set up test calibration. Vitally it is also traceable.
Can test points be used for traceability?
Using traceability to check a fault’s origin using historic data
Test results can be linked to individual boards and products using bar codes and label printers. Each board can be scanned to access its test record. Testing with historic evidence is very useful if problems emerge later if the right measurements have been recorded. You can look at test result trends to better understand if an issue is batch related, supply chain related or has other causes such as a bill of materials change or firmware update.
Why an instant fail is a good thing!
Sometimes knowing something is going to fail now is far better than getting an instant pass, why? Because of the time and money it saves.
During our careers as engineering in product development we have sadly often spoken with product owners who have no sub-assembly testing in place. This means that the full product needs to be assembled before any faults can be observed. This leads to costly and time-consuming reworks.
Using test points to find hidden problems
Worse still are subtle problems that affect the products long term performance. Sensor accuracy and power consumption are two issues that could be caught at the populated PCB stage but which may find their way into a customers hands untested. Getting right to the end and having to go back is not ideal to say the least!
Finding faults early using test points makes it cheaper and saves on cost and quality issues. It also gives you something you can’t measure. Peace of mind.
Often at the production stage it can be tempting to assume that testing processes are robust but using a test fixture takes this to the next level of certainty.
Using test fixtures to test at the manufacturing stage.
Your own little advocate
If you outsource manufacturing to third party you can think of your production test fixture as part of your quality control team, almost like an employee, on your side sat on someone else’s production line, right before you pay for it.
If the product has been manufactured correctly then the unit passes the test and you have confidence, and proof, that all is well. If the product doesn’t pass the tests then there is an early warning that there is something wrong. This could be a manufacturing issue or a design issue. Either way having the knowledge of an issue enables corrective action to be put in place and prevents poor quality product reaching your customers and potentially damaging your reputation.
Blog authorship: This blog was created with the knowledge of Richard Fletcher Ignys MD who has over 20 years’ experience in the electronics industry.
Introducing RapiJig – The Ignys Test Fixtures Solution
We have created RapiJig test fixtures solution to provide rapid deployment options with shorter lead times. This solution provides speedy test times for low volume manufacture. Test your PCBs.