Canon imageRUNNER ADVANCE C5500 Series, Service Manual, Page: 473 / 1331

Debug Log
Overview
■ Function Overview
The debug log is a log that analyzes the program behavior of the machine to enable developers to identify problems.
This machine is embedded with this function to collect the history for the behavior of each software module in the debug log and
output it as an integrated log for analyzing problems.
Since the frequency of outputting the debug log and the content of the log can be changed, the settings need to be changed
according to the trouble that occurs and the situation.
However, the on-site service technician does not need to make such decisions because instructions are sent from the Support
Dept. of your sales company.
■ Conditions for Obtaining Logs
● Cases where Logs Cannot Be Obtained
In the following cases, the procedure for obtaining logs is not required because logs cannot be obtained.
• When the background of the Control Panel is solid black and an error code is displayed in text
• When the device is frozen on the startup screen
• When the device repeats the startup process and does not become available
● Prerequisites for Obtaining Logs
• If a problem has occurred, suspend operations where possible. If operations are continued or jobs are executed even after
a problem has occurred, the log of the problem may not be able to be obtained because it is overwritten.
• While the problem is occurring or quickly after the problem occurs, save the debug log to a backup area before turning OFF
and then ON the power (refer to Saving to a USB Device with Counter Key + Numeric Key ).
• Ask the user to make a note of the date and time when the problem occurred and the procedure.
• If the user notifies the log has been saved, collect the log.
• The DEBUG PCB ASS'Y Board may need to be installed to obtain the log, depending on the problem (refer to
“Flow of
Determining the Procedure for Obtaining Logs ” on page 460 ).
NOTE:
The DEBUG SRAM PCB ASS'Y Board is required when the following problems occur.
• Problems relating to restart
• Problems that cause the Control Panel to become inoperable
• Problems relating to recovery from deep sleep
• When an unexpected error, E code error, or problem relating to restart occurs, the log can be automatically saved to the hard
disk. To automatically save the log to the hard disk, confirm that the following service mode is set to "101".
• (Level2) COPIER > Function > CBG-LOG > LOG-TRIG
● Type of log
Type of log Description
Sublogs Manual logs Up to 1 log (MCON/RCON/DCON) at the time of log collection is created.
Automatic logs When an event (exceptional behavior, error code or reboot) occurs, up to 10 logs (MCON/RCON/
DCON) stored in the machine are created.
Continuous logs During startup of the machine, up to 100 logs (MCON) continuously stored are created.
Key operation logs History of key operations
Network packet logs Logs of network packet data sent from or received by the host machine
● Collecting Logs Saved to the Hard Disk
If more than the above number of logs is generated, the oldest archive log is deleted.
When logs are retrieved from the machine, the saved log files are erased.
When a problem occurs, it is necessary to collect the log for the problem before it is overwritten.
6. Troubleshooting
459