Symptom: Cal data seems to be overwritten with "old" data.
Root Cause: Cal Data was saved when the system clock was set to a future date. The system loads the Cal data with the latest creation date which is actually in the future or "after" expected cal data, even if Cal data that was more recently created is available. Avoid this in the future by setting Network Time Protocol (NTP) settings, confirming local date/time is set correctly, and verify that the BIOS battery is charged.
Confirm the latest DIB Cal data is being loaded by following the steps to "To Confirm Latest Dut Interface Cal data is being Loaded", then if it is not as expected, follow the steps to "Obsolete Specific Dut Interface Cal Data".
To Confirm Latest Dut Interface Cal data is being Loaded:
- Open the configuration window by choosing System > Tester.
- Choosing Tester > Create Config Log from the tester's configuration window to save a text file with the systems current configuration named "<Tester SN> Description.txt"
- Change directory to D:\Shared and choose OK to save the file.
- Open the file by navigating to the D:\Shared\ folder using the Files icon along the toolbar and select the newly saved file it to open in a Text Editor window.
- Identify the "Dut Interface" instrument and note the value of the "cal date".
- From the configuration window, select the Dut Interface instrument choose Calibration > Restore, choose Yes to confirm.
- Identify the last date at the bottom of the list and choose Cancel to abort.
- If the cal date identified in step 5 matches the last date at the bottom of the list, then the latest Cal data is being loaded.
If not, then document the "cal date" in the file and use it follow the steps to Obsolete Specific Dut Interface Cal Data below.
Obsolete Specific Dut Interface Cal Data:
- Only proceed if the latest DIB Cal data is not being loaded and a specific Dut Interface Cal Data has been identified.
- Identify the cal date of the data that is being loaded by choosing Tester > Create Config Log from the tester's configuration window (System > Tester), change directory to D:\Shared and choose OK to save the file.
- Open the file by navigating to the D:\Shared\ folder and selecting it to open in a Text Editor window.
- Identify the "Dut Interface" instruments in the list and note the value of the "cal date". It will be a string representing the date and time the Cal data was saved.
- Launch Guru Explorer from the Apps menu, change Key 1 to ri.sys.ObjClass to RiDibCal from the pull down menu.
- Scroll and select the entry matching the cal date identified in step 3 and confirm the ri.sys.Title matches the DIB.
- Choose Obsolete Object(s) from the right mouse button menu to remove this entry from Guru.
(Note: It can be restored later, see "Restore Obsolete Objects" section of How to Obsolete (permanently remove/delete) objects in Guru https://roos.com/docs/RBEH-9L25CC)
- Now remove the Dut Interface instrument from the Configuration window by first left clicking on the name to select the instrument and then choosing Remove from the right mouse button menu.
- Choose System > Check to add the Dut Interface instrument back into the configuration.
- Confirm the Cal data is valid by repeating steps 1 and 2 and confirming the latest date is being loaded.
Timezone and Clock Synchronization (NTP) on eComStation
Replace CMOS Battery in EPC