326 Chapter6
General Troubleshooting
System Analyzer Programming Errors (100 to 150)
713 RAM U301 Checksum error of system RAM A2U301.
714 RAM U300 Checksum error of system RAM A2U300.
715 RAM U305 Checksum error of system RAM A2U305.
716 RAM U304 Checksum error of system RAM A2U304.
Microprocessor Error (717)
717 BAD uP Microprocessor not fully operational. Refer to Chapter
9, "Controller Section."
Battery Problem (718)
If STATE or TRACE data is found to be corrupt, the
processor tests the display RAMs and the program
RAMs containing the STATE information. If the RAMs
are working properly, this error message is generated.
To check the BT1 battery and the battery backup
circuitry, refer to "STATE and TRACE Storage
Problems" in Chapter 9.
718 BATTERY? Nonvolatile RAM not working; check battery BT1.
This error can also be generated if the battery has been
disconnected then reconnected. If this is the cause,
cycling power clears the error.
Model Number Error (719)
If this error occurs, return the instrument to a service
center for repair.
719 MODEL #? Could not read ID string from EEROM A2U501.
System Errors (750 to 759)
These errors often require troubleshooting the A2
controller and A3 interface assemblies.
750 SYSTEM Hardware/firmware interaction, zero divide. Check for
other errors.
751 SYSTEM Hardware/firmware interaction, floating point overflow.
Check for other errors.
752 SYSTEM Hardware/firmware interaction, floating point
underflow. Check for other errors.
753 SYSTEM Hardware/firmware interaction, log error. Check for
other errors.
754 SYSTEM Hardware/firmware interaction, integer overflow.
Check for other errors.
To Next Page
Loading...
Need help?
General
