ICT / FCT Test System (with programming)

Selection criteria

Bed-of-nails fixture design, test coverage, programming interface, cycle time, data logging and traceability.

Supply chain

Shenzhen has a dense cluster of ICT/FCT and fixture makers that build a custom fixture for each board. Ask for a test-coverage report and make sure every result is logged against the board serial number.

Buyer FAQ

What test coverage should I expect from ICT?

Aim for test access on over 90 % of nets, which requires test pads designed into the board, typically at least about 0.8–1 mm diameter at a pitch of 1.27–2.54 mm. Ask for a coverage report listing untested components and nets. For prototypes and low volumes, a flying-probe tester avoids the cost and lead time of a bed-of-nails fixture.

How should firmware programming be handled in test?

Program through SWD, JTAG or UART pins reached by spring probes, ideally several boards in parallel to keep cycle time down. The station should verify the checksum after programming and log the firmware version against each board serial number. Lock the firmware file under change control so a station cannot load the wrong version.

What should FCT check on a motor-driver board?

Typical checks are power-up current, supply rails, Hall or encoder inputs, PWM gate outputs into a real or dummy motor load, over-current and other protection trips, and communication interfaces. Run a known-good and a known-bad board at each shift start to prove the fixture. Track probe cycles and replace spring probes before contact wear causes false failures.

Where it is used