Service Diagnostics Utilities; Status; Test Prints; Diagnostic Fault History - Xerox Phaser 6360 Service Manual

Service Diagnostics Utilities

Status

Test Prints

Diagnostic Fault History

Phaser 6300/6350/6360 Service Manual
Three Service Diagnostics utilities are especially useful for troubleshooting:
■ Status
■
Test Prints
■
Diagnostic Fault History
What follows is an overview that describes the function and proper application
of each utility.
Located in the General Status menu, Status reports on the condition of the
printer. Status reports either No Status to Report, or sequentially lists error
conditions occurring since power-up. Conditions that prevent printing are
listed before warnings. Status listings are not stored. If the printer reaches
Ready, the list is cleared. Some applications of status are:
■
Provides an initial condition from boot to begin troubleshooting.
■
Captures static or dynamic events.
■
Confirms diagnostic test results and subsequent repairs.
Test Prints can isolate printing problems to the Engine Control or Image
Processor Board by eliminating image data transfer between the two. Test
Prints does not exercise any Image Processor Board circuitry. Test Prints gets
its image data from ROM. This allows the examination of Engine Control
Board function in isolation.
Test Prints is also useful for stimulating asynchronous (dynamic) events
related to the print process, or as a test for paper path and media related
problems. Some other key features of Test Prints:
■
Is the only diagnostic utility to exercise the entire print cycle.
■
Isolated from the operating system (PostScript). Runs from firmware.
■ Isolates the Image Processor Board from Engine Control Board.
■
Captures static or dynamic events.
■
Helps to isolate events that cause print artifacts or prevents printing.
The Diagnostic Fault History utility records a list of engine-generated error
events that occur during diagnostic testing. Use this utility to record error
events that occur while executing tests in Diagnostic Mode. The Diagnostic
Fault History utility captures asynchronous (transient) events only. For static
(continuous), or pre-existing events, rely on the Status utility.
General Troubleshooting
4-9