Skip header
 

Overview

Important

  • This function is not available on machines without a hard disk.

With this feature, you can save debug logs that are stored in the machine (HDD) on an SD card. It allows the Customer Engineer to save and retrieve error information for analysis.

The Capturing Log feature saves debug logs for the following two.

Important

  • In older models, a technician enabled the logging tool after a problem occurred. After that, when the problem had been reproduced, the technician was able to retrieve the debug log.

  • However, this 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.

Types of debug logs that can be saved

Type

Storage Timing

Destination (maximum storage capacity)

Controller debug log (GW debug log)

  • Saved at all times

HDD (4 GB)

Compressed when written to an SD card from the HDD (from 4 GB to about 300 MB)

Engine debug log

  • When an engine SC occurs

  • When paper feeding/output stop by jams

  • When the machine doors are opened during normal operation

HDD (Up to 300 times)

Note

  • Debug logs are not saved in the following conditions:
    When there is no optional 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)