SC-F2000 Revision C
TROUBLE SHOOTING Overview 31
Confidential
2.1.2 Troubleshooting Procedure
Refer to the following items according to the observed symptom, carry out the
corresponding troubleshooting following the procedures described in the next sections.
1. Trouble with a Maintenance Request or Service Call Error. (See P.32, page
33)
2. Trouble on print quality (See P.45)
3. Other troubles (See P.48)
4. Trouble on Service Program (See P.50)
5. Trouble on NVRAM Viewer (See P.51)
2.1.3 Procedure after troubleshooting
2.1.3.1 If the trouble has been successfully solved
Check if the movement of the covers is normal (without any damage, noises).
If any abnormality is found, lubricate or replace the faulty parts.
Carry out the cleaning after repair.
Prepare a report on the repair. (follow your company/local office's policy.)
2.1.3.2 If necessary to escalate the trouble case
Make a report with the following data.
Backed-up NVRAM data
Firmware version
Service program version
For bad print quality: a print sample with the marked symptom and a printed
test pattern.
For faulty parts: the faulty parts themselves and a photos of the troubling
section.
Information on the user/the repair listed below
This is a format of the escalation report. At least check out the items on the
list and register the case in the escalation system.
• Model name
• Serial number
• With or without options
• Content of the claim from the user
• Date of occurrence
• Trouble occurrence conditions/recurrence method
• What the service person actually observed
(Check items before check, the content of troubleshooting and repair.)
• Date of escalation
• Purpose of escalation
(Measures what the user/service person want done)
• Degree of urgency (S/A/B/C)
S: High (those which may cause a death, ignition, etc.)
A: Problems, bugs
B: Strong request
C: Inquiry
• Deadline for the response
• Repair history
• Part-replacement history
To Next Page
Loading...
Need help?
General