Omisión de la Procuraduría para la Defensa de los Derechos Humanos de

This chapter explains the procedures for solving troubles occurring in the equipment.

When a trouble occurs, check if an error code is displayed on the LCD screen of the control panel first. If displayed, refer to“ P. 5-4 “5.2 Error Code List”” to figure out the classification and contents of the error, and then refer to “ P. 5-27 “5.3 Diagnosis and Prescription for Each Error Code”” to remove its cause.

If not displayed and the equipment does not operate properly or images are not printed properly, refer to “ P. 5-103 “5.4 Other errors”” to remove its cause.

Note:

If unusual odor is detected or if smoke or fire comes out of the equipment, immediately turn the power OFF.

Even in the cases other than the above, fully observe safety precautions.

If any PC board or HDD shall be replaced, refer to“6.3 Precautions for Installation of GP-1070 and Disposal of HDD/Board”.

5.1.1 If a problem continues even after performing all troubleshooting.

If a problem continues even after performing all troubleshooting and technical tips, report the problem to the appropriate service center along with the following information. This information will help the service center understand your problem and take quick action to find the solution.

1. Serial Number 2. List Print

Refer to the appropriate Service Manual / Service Handbook for the detailed procedure to obtain a List Print.

A. Enter the value given below to obtain a List Print by CSV file.

9S-300: All CSV files

B. Enter the value given below to obtain a List Print by printing it out.

9S-101: 05 code 9S-102: 08 code

9S-106: Error history (1000 cases max) 9S-108: Firmware update log (200 cases max)

9S-110: Power on/off log (100 cases max)

3. For image-related problems, collect image samples with the problem areas and the feeding direction marked first. Then provide information about the media type and weight, and the print data / spool files for duplicating the problem.

4. For abnormal acoustic noise, describe the situation in as much detail as possible.

5. For hardware-related problems, provide photos of any broken parts, paper jams, etc.

In case of paper jams, include the type of paper and its manufacturer.

6. For software-related problems, provide list prints, Web Page Logs and the detailed procedure needed to duplicate the problem.

* This is the minimum information required to report a complaint. It would be appreciated if you could obtain additional information.

* Follow the directions of the service center if they request additional information as each issue is unique to some degree.

5.1.2 Collection of debug logs with a USB device [1] General description

The purpose of collecting the debug logs is to acquire the information for analyzing problems which occurred during the MFP’s operation. In such a case, you can collect the debug logs by inserting a USB device into the MFP. Even if the power has to be turned OFF with the main power switch after a problem occurs, the debug logs will be saved in the MFP (up to 3 logs). If the debug logs have already been saved in the MFP, they also can be collected.

The following information is included in the USB debug logs.

Internal operation, Job history, HDD/memory usage status, etc. (Personal/Corporate information (address book) not included)

When the debug logs are collected, also do so for the following information. since it may be difficult to investigate only using the debug log.

• List print mode ([9] + [START]) [300: All CSV files]

• Job logs below in Web Page -> [Logs] -> [Export Logs]

- Print Job Log Export

- Fax Transmission Journal Export - Fax Reception Journal Export - Scan Log Export

- Messages Log Export

• Problem occurrence time

Or the time when the customer called if it is difficult to work out when it occurred.

• Status of when you collected the debug log

As in the example below, check the status to know if the problem occurred at the debug log collection or how the customer recovered it.

• E.g.

- You checked the problem and connected a USB device to the equipment.

- No problem occurred when an attempt to collect the debug log was made; however the customer did turn the main power switch OFF when the problem occurred, so the log can be collected.

[2] Collection procedure 1. Note

When collecting a log, be sure to obtain consent from the user in advance and get the dedicated script file from the service center.

2. About USB devices

Be sure to format the USB device with FAT16/32 beforehand. (Recommend size: 2GB or more)

3. Advance preparation of collection

Store the dedicated script file to the root directory of the USB device.

4. Procedure for collecting debug logs

1. Insert USB device, in which the dedicated script file is stored, into the MFP while the power is ON.

2. The LED in the MFP starts blinking after the USB device has been inserted.

3. When the collection of the debug logs is finished, beeping is heard.

4. After the beeping has stopped, remove the USB device.

Notes:

• Do not remove the USB device while the LED in the MFP is blinking.

• If the LED does not start blinking after the USB device is inserted and a few minutes have passed, try the procedure from step 1 again.

• If there is no beeping after the LED starts blinking (about 20 minutes), try procedure from step 1 again.

• If the USB device is inserted when the MFP is not ready, the debug logs cannot be collected.

5. Collected debug logs

- When the collection of the debug logs is completed, the compressed file of the collected logs is stored in the root directory of the USB device.

File name: XXXX.YYYYMMDDHHmmSS

(XXXX= Serial number of the equipment, YYYY= year, MM= month, DD= day, HH= hour, mm= minute, SS= second)

- After the debug logs have been collected, be sure to send them to the service center together with a report.