This function is not available on models without a hard disk.
Log related to FAX like FCU debug log is stored only when a machine has FAX.
With this feature, you can save debug logs that are stored in the machine (HDD or operation panel) on an SD card. It allows the service representative to save and retrieve error information for analysis.
The Capturing Log feature saves debug logs for the following three.
Controller debug log
Engine debug log
FCU debug log (MP 501/601 only)
Operation panel log
Communication log (network packet)
Configuration page
Printer setting list
Font list
Error log
Fax information (MP 501/601 only)
SMC
In older models, a service representative enabled the logging tool after a problem occurred. After that, when the problem had been reproduced, the service representative was able to retrieve the debug log.
However, this new feature saves the debug logs at the time that problems occur. Then you can copy the logs to an SD card.
You can retrieve the debug logs using an SD card without a network.
Analysis of the debug log is effective for problems caused by the software. Analysis of the debug log is not valid for the selection of defective parts or problems caused by hardware.
Type |
Storage Timing |
Destination (maximum storage capacity) |
|---|---|---|
Controller debug log (GW debug log) |
|
HDD (4 GB) Compressed when written to an SD card from the HDD (from 4 GB to about 300 MB) |
Engine debug log |
|
HDD (Up to 300 times) |
Operation panel debug log |
|
Operation panel (400 MB /Up to 30 times) When updating the firmware for the operation panel, the debug logs are erased. |
Debug logs are not saved in the following conditions.
When there is no HDD.
While erasing all memory
While data encryption equipment is installed
While changing the firmware configuration
Forced power OFF (accidentally disconnecting the outlet)
Engine debug log in shutdown
When the power supply to the HDD is off because of energy saving (engine OFF mode /STR mode)
