Saving And Collecting Debug Logs - Canon imageRUNNER ADVANCE 715iF III 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 machine 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 to use a USB device with 1 GB
or more of free 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 272
restart.
3. Save and collect reports by referring to
Files" on page
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 272
4. Save and collect reports by referring to
Files" 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
Files" 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.
267
Procedure for Obtaining Logs
"Preparation" on page 269
274.
"Preparation" on page 269
274.
"Preparation" on page 269
274.
272.
"Saving of Manual Logs, Network Packet
"Saving of Manual Logs, Network Packet
6. Troubleshooting
and make the preparations such
"Saving of Manual Logs, Network
immediately after
"Saving and Collecting Report
"Collection of Log" on page 275.
and make the preparations such
"Saving of Manual Logs, Network
after startup.
"Saving and Collecting Report
"Collection of Log" on page 275.
and make the preparations such
"Saving of Manual Logs, Network
272.
"Saving and Collecting Report
"Collection of Log" on page 275.
"Saving of Manual Logs, Network
272.
"Collection of Log" on page 275.
272.
272.
"Sav-