-
Invalid Calibration Data
AN ALTERNATIVE TO CALIBRATION 4.5.
You do not have to calibrate the system at every power-up. A
more convenient procedure is to restore calibration data from the
user disk after the self-tests have been performed and the system
configured. If you do not calibrate the system at power-up, you
should at least restore saved calibration data.
Each calibration generates data, which can be saved on the user
disk using the SETUP MENU key. Once the system is
calibrated for a given pod, probe, clock module, and I/O
module, the data is good until one or more of those devices is
changed.
If you test or troubleshoot one type of UUT and then change to
another, the calibration data stored on user disk for the new
UUT will be invalid if a new pod is connected. In this case, the
system should be recalibrated, after which the new data can be
stored on the user disk.
4.5.1.
The calibration data you restore from user disk may be invalid if:
l
After the data was saved, your system’s pod, probe, I/O
modules, or clock module was changed. This includes
swapping I/O modules: for example, removing an I/O
module from connector 1 and attaching it to connector 2.
0
Your system has never been calibrated.
l
Your system was last calibrated more than one month ago.
0
When testing or troubleshooting, you changed pods or I/O
modules when changing from one type of UUT to another.
4-9
To Next Page
Loading...
