Xerox Phaser 8860, Руководство по обслуживанию

Страница: 255 / 316

09/2007
6-35 Phaser 8860/8860MFP Service Manual
General Troubleshooting
Diagnostics Initial Issue
When executed from the Print Engine Function menu, the Diagnostic Fault History displays on
the Control Panel and updates as each error event is detected. Fault History events are
recorded only when no pre-existing errors are present. The second and subsequent occur-
rences of the same event are not recorded. The maximum number of events recorded is 25.
Once the list is full, additional new events are lost until the log is cleared by either a system
reboot or by selecting Fault History Master Clear from the Fault History menu. New events
occurring after the list is cleared are recorded.
For display, the list combines a line number, a code, and potentially a test precondition indi-
cated by the letter P (for events requiring a power cycle), a U for unknown event sequence, an
M for more entries, or a string of asterisks ***** to indicate the last error recorded.
As an example:
Fault History Display
1 [150]
2 [42]P
3 [198]P
4 [T2]M
Press CANCEL to exit
The example shows a single screen displaying four events. Lines 2 and 3 include the precondi-
tion indicator
P directing a reboot before component testing continues. Line 4 includes an
abbreviated Misfeed at Tray 2 code, and the continuation notation M indicating more events
appear on subsequent pages. Pressing OK calls up the next page. Pressing Cancel exits the
utility and displays the Fault History menu.
Events typically appear in the order detected. However, occasionally the event’s sequence is
indeterminate. As is the case with simultaneous events. In these cases, a U is appended to the
event to indicate an unknown sequence. While event sequence can be important in determin-
ing cause, the event itself provides a starting point for investigation.
For those events listed with a P , testing of a specific component may not require the indicated
power cycle. For example, if the log lists a motor failure, it’s reasonable to go directly to the
appropriate motor test to confirm the failure without first power cycling the system. For events
involving components, such as the Drum, Transfix Roller, or Ink Sticks, power cycling is recom-
mended before additional testing is performed.
Using Diagnostic Fault History
The general approach to using the Diagnostic Fault History utility is as follows:
1. Determine the diagnostic test necessary to reproduce a suspected transient event.
2. Determine if the current logged events are important to understanding the problem. If so,
examine or record the events currently in the log, perform whatever analysis is appropri-
ate, and then clear the log.
3. Perform the selected test.
4. Re-examine the event list.
5. Identify an abnormal or suspicious event based on the test performed. For example, a
door open event while printing a test print when the door remained closed.
As an example, assume the Interlock Switch is suspect. The process to gain access to the
switch will produce a number of events unrelated to switch function.
Therefore, you would:
1. Override the interlock function to provide power.
2. Access the Interlock Switch actuator
3. Clear the list with Clear Fault History.
4. Display Fault History and manipulate the component or connecting wires as required to
reveal the switch’s condition