Overview
It may be necessary to capture the engine debug log in order to conduct analysis for problems with the machine or peripherals. There are 3 methods for capturing the engine debug log at the machine. Features of each method are described below.
Save Timing |
Maximum Capture Period |
Use |
|---|---|---|
At the timing described above, a log from about 10 previous pages is automatically saved to the HDD. |
HDD (Up to 300 times) |
Capturing an after-the-fact log for SC and jams |
Saving is automatically performed when SC or jams occur. Therefore, no advance preparation is required and an after-the-fact log can be acquired. However, the log does not provide information on errors other than SC and jams, nor does it provide information on SC/jams which occurred more than 10 pages previously. In such cases, it is necessary to acquire a log using the Service Slot Board (Service Option) method.
Save Timing |
Maximum Capture Period |
Use |
|---|---|---|
A log is continuously saved when an SD card is inserted. |
Approx.10 days for an 8GB SD card (assuming about 8 hours of use per day) |
Capturing a log for all errors |
It is necessary to install a Service Slot Board in the machine in advance and to insert an SD card. When a Service Slot Board is installed, the log is continuously acquired for a long capture period. Therefore, the log provides information on errors other than SC and jams, as well as information on SC/jams for a longer time period.
Save Timing |
Maximum Capture Period |
Use |
|---|---|---|
A log is continuously saved when executing log capture at “Teraterm”. |
Depends on HDD space at PC |
Capturing a log when time is needed to obtain the Service Slot Board. Generally, we recommend using the Service Slot Board to capture a log. |
Capturing a log in special cases. Through the Debug Cable only, it is possible to capture special logs (fixing temperature log, etc.) by entering commands.
