Limit Testing
11-7
Pass condition
For this discussion, assume that all grading mode limit tests pass. After the three limit tests
pass, the
“
PASS
”
message is displayed, and operation drops down to the Binning Control deci-
sion block. (Note that the pass condition can also be determined with the
:CALC2:LIM<n>FAIL? query via remote.)
Immediate binning
—
For immediate binning, the testing process stops. The SourceMeter
outputs the pass pattern to the component handler to perform the binning operation.
End binning
—
For end binning, operation drops down to the Another Test Cycle? decision
block. If programmed to perform additional tests (i.e., sweep) on the DUT package, operation
loops back up to perform the next source-measure action. After all programmed test cycles are
successfully completed, the SourceMeter outputs the pass pattern to the component handler to
perform the binning operation.
If con
fi
gured to test another DUT package, operation loops back to the top of the
fl
owchart
and waits for the SOT (start of test) pulse from the component handler.
Fail condition
When a failure occurs, the FAIL message is displayed (and also can be read via remote with
:CALC2:LIM<n>FAIL?), and operation proceeds to the Binning Control decision block.
Immediate binning
—
For immediate binning, the testing process is terminated and the fail
pattern for that particular failure is sent to the component handler to perform the binning
operation.
End binning
—
For end binning, the fail pattern for the
fi
rst failure is stored in memory and
operation proceeds to the Another Test Cycle? decision block. If programmed to perform addi-
tional tests (i.e., sweep) on the DUT package, operation loops back up to perform the next
source-measure action. Note that when a failure occurs, subsequent tests in the test cycle are
not performed.
After all programmed test cycles are completed, the SourceMeter outputs the fail pattern
stored in memory. This re
fl
ects the
fi
rst failure that occurred in the testing process for the
device package. The component handler places the DUT in the appropriate bin.
If con
fi
gured to test another DUT package, operation loops back to the top of the
fl
owchart
and waits for the SOT (start-of-test) pulse from the component handler.
Summary of Contents for 6430
Page 26: ......
Page 32: ......
Page 78: ...2 14 Connections ...
Page 98: ...3 20 Basic Source Measure Operation ...
Page 138: ...5 30 Source Measure Concepts ...
Page 156: ...6 18 Range Digits Speed and Filters ...
Page 168: ...7 12 Relative and Math ...
Page 176: ...8 8 Data Store ...
Page 202: ...9 26 Sweep Operation ...
Page 248: ...11 22 Limit Testing ...
Page 310: ...16 6 SCPI Signal Oriented Measurement Commands ...
Page 418: ...17 108 SCPI Command Reference ...
Page 450: ...18 32 Performance Verification ...
Page 477: ...A Specifications ...
Page 489: ...B StatusandErrorMessages ...
Page 498: ...B 10 Status and Error Messages ...
Page 499: ...C DataFlow ...
Page 503: ...D IEEE 488BusOverview ...
Page 518: ...D 16 IEEE 488 Bus Overview ...
Page 519: ...E IEEE 488andSCPI ConformanceInformation ...
Page 523: ...F MeasurementConsiderations ...
Page 539: ...G GPIB488 1Protocol ...
Page 557: ......