Canon imageRUNNER ADVANCE C3330 Series, Service Manual

Page: 447 / 1225

Procedure for Collecting Logs
Log Collection Procedure List
Problem
Case
Details of Problem DEBUG SRAM
PCB ASS'Y
Board
Procedure for Obtaining Logs
Case A Problem that repeats re-
start Necessary 1. Refer to “Preparation” on page 437 and make the preparations such
as installing the DEBUG SRAM PCB ASS'Y Board or change the set-
tings.
2. Execute log saving by referring to “Saving of Manual Logs, Network
Packet Logs and Key Operation Logs” on page 440 immediately after
restart.
3. Save and collect reports by referring to “Saving and Collecting Reports”
on page 441
4. Collect debug logs by referring to “Collection of Log” on page 442 .
Case B Problem causing the
Control Panel to be
locked Necessary 1. Refer to “Preparation” on page 437 and make the preparations such
as installing the DEBUG SRAM PCB ASS'Y Board or change the set-
tings.
2. Turn OFF and then ON the power immediately after the Control Panel
is locked.
3. Execute log saving by referring to “Saving of Manual Logs, Network
Packet Logs and Key Operation Logs” on page 440 after startup.
4. Save and collect reports by referring to “Saving and Collecting Reports”
on page 441 .
5. Collect debug logs by referring to “Collection of Log” on page 442 .
Case C Problem related to the
sleep mode Necessary 1. Refer to “Preparation” on page 437 and make the preparations such
as installing the DEBUG SRAM PCB ASS'Y Board or change the set-
tings.
2. After the problem occurs, turn OFF and then ON the power if necessary,
and execute log saving by referring to “Saving of Manual Logs, Network
Packet Logs and Key Operation Logs” on page 440 .
3. Save and collect reports by referring to “Saving and Collecting Reports”
on page 441 .
4. Collect debug logs by referring to “Collection of Log” on page 442 .
Case D Problem when execut-
ing a job (Example:
Printing is not per-
formed, etc.) Not necessary 1. Execute log saving while the problem is occurring by referring to “Sav-
ing of Manual Logs, Network Packet Logs and Key Operation Logs” on
page 440
.
2. Execute log saving by referring to “Saving of Manual Logs, Network
Packet Logs and Key Operation Logs” on page 440 .
3. Collect debug logs by referring to “Collection of Log” on page 442 .
When an E code error
has occurred Not necessary Execute log saving by referring to “Saving of Manual Logs, Network Packet
Logs and Key Operation Logs” on page 440 .
However, if the background of the Control Panel is blank and an error code
is displayed in text, logs cannot be obtained.
Case E Problems other than
above Not necessary Execute log saving by referring to “Saving of Manual Logs, Network Packet
Logs and Key Operation Logs” on page 440 .
Check with the user on the date and time when the problem occurred and
the procedure.
Saving and Collecting Debug Logs
■ Tools Required
The following tools are necessary to save/collect debug logs of the machine.
Exporting to a USB Device
• USB device
When exporting debug logs to a USB device, use a USB device in which the system software for the device is registered
using SST.
Since the size and number of log files to collect varies according to the device status and the logs that have been saved,
the size of the collected files may be several hundred MB. Therefore, it is recommended that you use a USB device with
1 GB or more space.
The USB device must be formatted with the FAT file system.
6. Troubleshooting
435