The following table lists the execution data properties you can access from this step.
NameTypeDescriptionAccess Restrictions
BinTypeNumber or NI_SemiconductorModule_BinTypeType of the bin assigned to the part tested on the current site. (0=Pass, 1=Fail, 2=Other)Test Socket Threads Only

Valid in PostUUT

BinTypesArray of numbers or array of NI_SemiconductorModule_BinTypeThe types of the bins assigned to each part on each site. (0=Pass, 1=Fail, 2=Other)Valid in PostBatch
CSVTestResultsLogFilePathStringReturns the absolute file path of the last CSV Test Results Log generated for the current lot.Valid in MainSequence
CSVTestResultsLogFilePathsArray of stringsReturns the absolute file paths of all CSV Test Results Logs generated for the current lot. If the Generate One File per Wafer option is enabled, one path is returned for each wafer processed in the lot so far. Otherwise, the length of the array is 1.Valid in MainSequence
DebugTestResultsLogFilePathStringReturns the absolute file path of the Debug Test Results Log generated for the current site.Valid in MainSequence
DebugTestResultsLogFilePathsArray of stringsReturns the absolute file paths of the Debug Test Results Logs generated for all sites in the current lot.Controller Thread Only
DidInlineQABlockExecuteBooleanReturns true if an InlineQA step executed its block of steps for this site.Test Socket Threads Only

Valid in MainSequence

DieCoordinateXNumberReturns the X wafer coordinate of the current die being tested on this site. The handler/prober driver sets this property value by setting values in the WaferRuntimeData.SiteDieCoordinates parameter in the StartOfTest handler driver entry point sequence. This property corresponds to the X_COORD field in the Part Results Record (PRR) in the STDF log file.Test Socket Threads Only

Valid in MainSequence

DieCoordinateYNumberReturns the Y wafer coordinate of the current die being tested on this site. The handler/prober driver sets this property value by setting values in the WaferRuntimeData.SiteDieCoordinates parameter in the StartOfTest handler driver entry point sequence. This property corresponds to the Y_COORD field in the Part Results Record (PRR) in the STDF log file.Test Socket Threads Only

Valid in MainSequence

HardwareBinNameStringReturns the name of the hardware bin that the tester assigned to the last part that was tested on this site.Test Socket Threads Only

Valid in PostUUT

HardwareBinNamesArray of stringsThe names of the hardware bins that the tester assigned to the parts in the current batch.Valid in PostBatch
HardwareBinNumberNumberThe number of the hardware bin that the tester assigned to the last part that was tested on this site. Returns -1 if the tester has not yet assigned a bin to the part or a value between 0 and 65535 if the bin was assigned.Test Socket Threads Only

Valid in PostUUT

HardwareBinNumbersArray of numbersThe numbers of the hardware bins that the tester assigned to the parts in the current batch.Valid in PostBatch
IsDuplicateDieCoordinatesBooleanReturns true if a part with the same die coordinates as the current part was tested previously in the current wafer.Test Socket Threads Only

Valid in MainSequence

IsDuplicatePartIdBooleanReturns true if a part with the same part ID as the current part was tested previously in the current lot.Test Socket Threads Only

Valid in MainSequence

IsRetestingBooleanReturns true if the tester is currently retesting the same parts from the previous batch because the operator requested a retest.Valid in PreBatch
IsStartOfWaferBooleanReturns true if the current batch is the first batch of parts of a new wafer. This property remains true if the first batch of parts are retested.Valid in PreBatch
LotSummaryReportFilePathStringReturns the absolute file path of the last Lot Summary Report generated for the current lot.Valid in MainSequence
LotSummaryReportFilePathsArray of stringsReturns the absolute file paths of all Lot Summary Reports generated for the current lot. If the Generate One File per Wafer option is enabled, one path is returned for each wafer processed in the lot so far. Otherwise, the length of the array is one.Valid in MainSequence
NumberOfSitesNumberThe number of sites that are testing the current lot.
PartIdStringReturns the part identifier for the current part being tested on this site. The handler/prober driver sets this property value by setting values in the SitePartIds parameter in the StartOfTest handler driver entry point sequence. If the handler/prober driver does not set this property, the tester sets the value to a unique value if the GenerateUniquePartIds station settings is set to true. This property corresponds to the PART_ID field in the Part Results Record (PRR) in the STDF log file.

When the GenerateUniquePartIds property is True, TSM reassigns the same unique Part ID to the part when it is retested. Customize the behavior of GenerateUniquePartIds to assign a new unique Part ID to a part when it is retested .

Test Socket Threads Only

Valid in MainSequence

PartTextStringReturns the part description text for the current part being tested on this site. The handler/prober driver sets this property value by setting values in the SitePartTexts parameter in the StartOfTest handler driver entry point sequence. This property corresponds to the PART_TXT field in the Part Results Record (PRR) in the STDF log file.Test Socket Threads Only

Valid in MainSequence

SiteNumberNumberSite number of the current site.Test Socket Threads Only
SiteNumbersArray of numbersThe site numbers that are testing the current lot.
SiteTestTimeInSecondsNumberReturns the time to execute the MainSequence sequence for the last part that was tested on this site.Test Socket Threads Only

Valid in PostUUT

SoftwareBinNameStringThe name of the software bin that the tester assigned to the last part that was tested on this site.Test Socket Threads Only

Valid in PostUUT

SoftwareBinNamesArray of stringsThe names of the software bins that the tester assigned to the parts in the current batch.Valid in PostBatch
SoftwareBinNumberNumberThe number of the software bin that the tester assigned to the last part that was tested on this site. Returns -1 if the tester has not yet assigned a bin to the part or a value between 0 and 65535 if the bin was assigned.Test Socket Threads Only

Valid in PostUUT

SoftwareBinNumbersArray of numbersThe numbers of the software bins that the tester assigned to the parts in the current batch.Valid in PostBatch
StdfLogFilePathStringReturns the absolute file path of the last STDF log file generated for the current lot.Valid in MainSequence
StdfLogFilePathsArray of stringsReturns the absolute file paths of all STDF log files generated for the current lot. If the Generate One File per Wafer option is enabled, one path is returned for each wafer processed in the lot so far. Otherwise, the length of the array is one.Valid in MainSequence
WaferRuntimeData.ExecDescriptionStringReturns the wafer description supplied by exec. This property corresponds to the EXC_DESC field in the Wafer Results Record (WRR) in the STDF log file.Valid in PreBatch
WaferRuntimeData.FabWaferIdStringReturns the fab wafer ID. This property corresponds to the FABWF_ID field in the Wafer Results Record (WRR) in the STDF log file.Valid in PreBatch
WaferRuntimeData.FrameIdStringReturns the wafer frame ID. This property corresponds to the FRAME_ID field in the Wafer Results Record (WRR) in the STDF log file.Valid in PreBatch
WaferRuntimeData.MaskIdStringReturns the wafer mask ID. This property corresponds to the MASK_ID field in the Wafer Results Record (WRR) in the STDF log file.Valid in PreBatch
WaferRuntimeData.UserDescriptionStringReturns the wafer description supplied by user. This property corresponds to the USR_DESC field in the Wafer Results Record (WRR) in the STDF log file.Valid in PreBatch
WaferRuntimeData.WaferIdStringValid in PreBatch

Access Restrictions

  • Some properties are valid only when accessed from certain process model threads. If you access these properties from an unsupported model thread, the step reports a run-time error.

    Some properties are valid only at certain times during execution. If you access these properties before they are valid, the step either returns default values or reports a run-time error as described below.

    • Test Socket Threads Only—You must access these site-specific properties from a test socket thread. The step reports a run-time error if you access the property in a sequence that executes in a controller thread, such as ProcessSetup when executing the Batch process model. You can access these properties from any sequence when using the Sequential process model.
    • Controller Thread Only—You must access these properties from a process model callback sequence that executes in a controller thread, such as ProcessCleanup. The step reports a run-time error if you access the property in a sequence that executes in a test socket thread, such as MainSequence or PreUUT.
    • Valid in PreBatch—TSM assigns values to these properties before testing starts for the current batch. These properties have meaningful values only in the following locations. The step returns default values if you access the property from other locations. The step returns default values if you access the property from other locations.
      • In the Model Plugin – Pre Batch entry point and beyond in model plug-ins when using the Batch process model.
      • In the Model Plugin – Pre UUT entry point and beyond in model plug-ins when using the Sequential process model.
      • In the PreUUT Model callback and beyond in test programs.
    • Valid in MainSequence—TSM assigns values to these site-specific properties before testing starts for the current part. These properties have meaningful values only in the following locations. The step returns default values if you access the property from other locations.
      • In the Model Plugin – Pre UUT entry point and beyond in model plug-ins.
      • In the MainSequence sequence and beyond in test programs.
    • Valid in Post UUT—TSM assigns values to site-specific properties after testing completes for the current part. These properties have meaningful values only in the following locations. The step reports a run-time error if you access these properties from other locations.
      • In the Model Plugin – UUT Done entry point and beyond in model plug-ins.
      • In the PostUUT Model callback and beyond in test programs.
    • Valid in Post Batch—TSM assigns values to these properties after testing completes for all sites. These properties have meaningful values only in the following locations. The step reports a run-time error if you access these properties from other locations.
      • In the Model Plugin – Batch Done entry point and beyond in model plug-ins when using the Batch process model.
      • In the Model Plugin – UUT Done entry point and beyond in model plug-ins when using the Sequential process model.
      • In the PostBatch callback and beyond in test programs when using the Batch process model.
      • In the PostUUT callback and beyond in test programs when using the Sequential process model.