Saving And Collecting Debug Logs - Canon imageRUNNER ADVANCE C3330 Series Service Manual

Procedure for Collecting Logs
Problem Details of Problem
Case
Case A Problem that repeats re-
start
Case B Problem causing the
Control Panel to be
locked
Case C Problem related to the
sleep mode
Case D Problem when execut-
ing a job (Example:
Printing is not per-
formed, etc.)
When an E code error
has occurred
Case E Problems other than
above

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.
Log Collection Procedure List
DEBUG SRAM
PCB ASS'Y
Board
Necessary 1. Refer to
as installing the DEBUG SRAM PCB ASS'Y Board or change the set-
tings.
2. Execute log saving by referring to
Packet Logs and Key Operation Logs" on page
restart.
3. Save and collect reports by referring to
on page 441
4. Collect debug logs by referring to
Necessary 1. Refer to
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
Packet Logs and Key Operation Logs" on page 440
4. Save and collect reports by referring to
on page
5. Collect debug logs by referring to
Necessary 1. Refer to
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
Packet Logs and Key Operation Logs" on page
3. Save and collect reports by referring to
on page
4. Collect debug logs by referring to
Not necessary 1. Execute log saving while the problem is occurring by referring to
ing of Manual Logs, Network Packet Logs and Key Operation Logs" on
page
2. Execute log saving by referring to
Packet Logs and Key Operation Logs" on page
3. Collect debug logs by referring to
Not necessary Execute log saving by referring to
Logs and Key Operation Logs" on page
However, if the background of the Control Panel is blank and an error code
is displayed in text, logs cannot be obtained.
Not necessary Execute log saving by referring to
Logs and Key Operation Logs" on page
Check with the user on the date and time when the problem occurred and
the procedure.
435
Procedure for Obtaining Logs
"Preparation" on page 437
"Preparation" on page 437
441.
"Preparation" on page 437
441.
440.
"Saving of Manual Logs, Network Packet
"Saving of Manual Logs, Network Packet
6. Troubleshooting
and make the preparations such
"Saving of Manual Logs, Network
440immediately after
"Saving and Collecting Reports"
"Collection of Log" on page 442.
and make the preparations such
"Saving of Manual Logs, Network
after startup.
"Saving and Collecting Reports"
"Collection of Log" on page 442.
and make the preparations such
"Saving of Manual Logs, Network
440.
"Saving and Collecting Reports"
"Collection of Log" on page 442.
"Saving of Manual Logs, Network
440.
"Collection of Log" on page 442
440.
440.
"Sav-
.