- 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 four.
- Controller debug log
- Engine debug log
- FCU debug log (IM 550F/600F/600SRF only)
- Operation panel debug log
- On older models, logging tool enabled by a service representative when a problem occurred. Once the problem reoccurred, the service representative was able to retrieve the debug log.
- With this new feature, debug logs are saved at the moment any problem occurs and then can be copied to an SD card.
- SD card is an option to retrieve the debug logs when there is no network.
- Analyzing the debug log is a good way to figure out software issues, but it is not an effective way to find defective parts, if there are any, or detect problems caused by hardware.
Types of debug logs that can be saved
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 |
| The 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)