5
Trouble Shooting > Debug log > How the log is written
Debug log
Sublog
■ Function Overview
Sublog is the record of behavior inside the Main Controller PCB.
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 staff who is in charge of quality follow-up 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.
● Sublog
It is available only when the Sublog Board is installed on the Main Controller PCB.
When the Sublog Board is not installed, log is not saved anywhere.
It is stored in the Sublog Board and its content is stored even when the power is turned OFF
to be displayable when the power is turned ON again.
The Sublog Board has a limited capacity and when the log exceeding this storage number is
attempted to be stored, the log is deleted in the order of length of time stored.
● 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.
5
Trouble Shooting > Debug log > How the log is written
How the log is written
Main Controller Board
• In case of using the Sublog Board:
• Write the log directly to RAM on the Sublog Board.
• The on-board battery prevents data from being erased when the power is turned OFF.
5-48
F-5-50
5-48