Technical data

Module 11

Advanced Definitions and Operations

11-17

Subsite_xxxx.exe

Start

End

Chuck down

Moves to the next subsite

Chuck up

Returns response

Yes

Prober error?

Yes

Prober error?

Gets X-Y coordinate

• Arguments: -a GPIB_address

-l log_file_name

Example:

–a GPIB0::5::INSTR –l C:\temp\prb.log

• Response: XML format data

status: True (error) or False

device_id: prefix:coordinate

Example:

<Break>status</Break>

<Target>device_id</Target>

</Response>

<Break>False</Break>

</Response>

To realize sub die move operation, you need to define Subsite_xxxx.exe in your test definition and

create your application test setup. However, you do not need to take care of this procedure by using

the Subsite move test setup included in the application library. The Subsite move setup moves wafer

chuck to the next subsite, reads device ID from the prober, and sets it to the Device ID of the test

result record.

Open the Subsite move test setup and save it as a setup in your preset group (My Favorite Setup).

Then you can use the setup for your quick test.

Note: To use the Subsite move setup, set the GPIB address and log file name in the prober_info.ini.

And ignore the Arguments for Subsite_xxxx.exe.

Note: If you use a Suss prober, the number of Subsite move setups used in your quick test (die test)

is important. It must be N-1; N is the number of subsites defined in the prober.

The status is True or False. It is used for the EasyEXPERT repeat measurement stop function. When

the Procedure return condition box is checked in the Repeat Measurement Setup dialog box, the

repeat measurement will be stopped if status = True.

The device_id is a string for the Device ID of the test result record.