Semiconductor testers often use handlers and probers to complete the following tasks:

  • Place untested DUTs in test sites
  • (Handlers) Move tested DUTs from test sites to an appropriate hardware bin, depending on the test results
  • Potentially notify the tester to stop the test when no DUTs remain

The tester software must be able to communicate with the handler or prober to execute tests correctly. Handlers and probers use a variety of different communication protocols and command sets. Test program developers might need to ensure that the tester can use different types of handlers or probers.

TSM Implementation

Use the TSM handler/prober driver plug-in architecture to write and enable handler/prober driver sequence files. A handler/prober driver sequence file contains handler/prober driver entry point sequences that TSM calls during execution to accomplish handler-related or prober-related tasks.

Use the NI Built-in Simulated Handler Driver to simulate handler functionality without requiring access to a real handler. To integrate a real handler or prober in the handler/prober driver plug-in architecture, you must create a new handler/prober driver sequence file. TSM uses only one active handler/prober driver sequence file at a time because the lot of DUTs (test lot) can use just one type of handler or prober at a time.