Debug Log; Scope Of Application; Overview - Canon imageRUNNER ADVANCE C5255 Series Service Manual

Debug log

Scope of Application

■ Purpose
When the Canon quality-appointed staff determines the need for an analysis of debug log
by the R&D department, we ask the field to collect log for an investigation to determine the
cause.

Overview

■ Function Overview
Debug log is an integrated log for failure analysis that gathers logs prepared by the software
modules in the device for debug purpose.
In the case of a field failure that is hard to be reproduced, this measure is intended to improve
efficiency in failure analysis and reduce the time for failure support by collecting debug log at
the user site (which was created immediately after the failure) and sending it to the R&D.
When the Canon quality-appointed staff determines the need for an analysis of firmware
debug log by the R&D department, we ask the field to collect log for an investigation to
determine the cause.
● Effective Instances of Collecting Debug Log
• The error occurs only at the customer site and cannot be reproduced by the sales company
or the Canon staff who is in charge of quality follow-up.
• When the error frequency is low.
• When the error is suspected of links with firmware rather than a mechanical/electrical
failure.
* Collection of Sublog is not necessary when the reproduction procedure is identified and
the error can be reproduced by the sales company HQ or the Canon staff who is in charge
of quality follow-up.
6
Troubleshooting > Debug log > Overview > Function Overview
6 Troubleshooting > Debug log > Overview > Function Overview
● Types of Logs
There are continuous logs, event logs, and manual logs.
Type Collecting method
Event log Automatically recorded in accordance
with the conditions specified in
DEBUG-1.
Manual log Perform the following procedure.
1. Hold down the [Counter] button (10
seconds or longer).
2. Press 1 on the numeric keypad.
3. Press 2 on the numeric keypad.
4. Press 3 on the numeric keypad.
While logs are being obtained, the
screen is locked. It takes approx. 3
minutes before obtaining the logs is
completed and the user can work on
the screen.
● Conditions of Log Collection
• Logs can be collected on a PCB-by-PCB basis. (SUBLOG, SUBLOG_RCON, SUBLOG_
DCON)
Location File name Automatic collection
Logs generated
while the host
machine is
being operated.
Main Controller SUBLOG Yes
Reader Controller SUBLOG_RCON No
DC Controller SUBLOG_DCON No
● Collection of Logs
Connect SST or a USB memory device,
and select COPIER > FUNCTION > SYSTEM > DOWNLOAD > OK to collect logs.
6-135
Size of logs Setting
Less than 500MB Service mode Lev2: COPIER
> FUNCTION > SYSTEM >
DEBUG-1 > 3 (default)
3: Exception + E code + Reboot
Make movement same as 3
even if you change setting of it.
n/a
Manual collection
Event log Manual log
When an event has
occurred
Yes Yes
Yes Yes
Yes Yes
6-135
T-6-33
T-6-34