Filter
Top Products
Troubleshooting 51
EEPROM Troubleshooting and Initialization
Troubleshooting
The power module can detect an EEPROM checksum error. This error is not identified by number, but causes the following
symptoms:
þ The power module starts up with both the VOLTS and AMPS full-scale programming and metering ranges accepting
values up to 1000.
þ Selftest error code 330 is stored in the SCPI error queue where it can be read by the controller (see Chapter 5 in the
Power Module Programming Guide).
þ The *IDN? query returns 0A in the model field.
þ The calibration password is set to 0.
An EEPROM checksum error can occur if there has been an excessive number of write cycles to an EEPROM. This
condition is not recoverable and requires a new EEPROM.
An EEPROM checksum error can also occur due to loss of ac power during a checksum calculation. This condition is very
unlikely, but may be recoverable by performing the following steps from the controller:
þ Enable calibration mode (CAL:STAT ON,0)
þ Save an operating state to EEPROM. (for example, *SAV 2)
Initialization
EEPROM U22 on the power board stores the module’s GPIB address, model number, and other operating and calibration
constants. The EEPROM was initialized with the proper constants at the factory. If you need to re-initialize the module with
the proper operating constants, run the following program.
After you have initialized the module by running the initialization program, you must calibrate the module as described in
Appendix A of the Power Module User’s Guide.