Canon imageRUNNER ADVANCE C350 series Service Manual page 606

Note:
To remove the USB memory device, exit the service mode screen and perform the
operation for removing memory media on the screen.
Remarks:)
• When there is any debug log file that has been automatically saved in the sublog storage
space, send it to the USB memory device as well.
• Multiple debug logs are archived into one file to be sent into the USB memory device.
• The archived name is automatically given as follows: "date and time", "serial number",
"MN-CONT"
A file name example: 20100425_13-32-ENS00059-V01.44_Debuglog@USB.bin
In the above example, "20100425_13-32" shows the date and time of log collection (the
date and time set in the machine),
"ENS00059" the serial number,
"V01.44" the firmware version of the Main Controller (MNCONT), and
"Debuglog@USB" shows that the log was "collected with "DBG-LOG>LOG2USB".
Note:
The log file is deleted from the machine once it is collected into the USB memory
device.
You can check the description of the logs to be included in .bin file with "LOGLIST.TXT"
that is saved simultaneously with the .bin file into the USB memory device.
LOG2SRVR
When the Canon quality-appointed staff determines that it is necessary to use this function,
the setting file for the FTP server is provided through the sales company HQ.
■ Function
This is a function to transfer debug log to the FTP server.
● Preconditions
Network connection is available from the machine and there is a FTP server with a registered
account (ID/Password) used by the machine.
The address and account of the FTP server used by the machine are specified with the
setting file (to be described later).
6
Troubleshooting > Debug Log > LOG2SRVR > Function
6 Troubleshooting > Debug Log > LOG2SRVR > Function
● Operation Procedure
First, go through the following steps to set the address of the FTP server:
a) Save the log setting file (e.g. "800.conf") provided by the Canon quality-appointed staff into
a USB memory device.
b) Insert the USB memory device to the machine and enter 800 for "LOG-TRIG" to execute
reading.
> The server address described in 800.conf is specified in the transfer destination of
LOG2SRVR.
c) Select "LOG-SRVR" and click "OK" to start a log collection and server transfer processing.
d) An "ACTIVE!" sign blinks during the processing.
Note:
Do not perform the following operations during the processing.
• Turning OFF and then ON the power of the machine.
• Operation on UI.
When the processing results in "NG!" although you tried several times before, check for
the IP address in the loaded setting file again.
Perform an internal ping test from the machine to the specified IP address immediately
after you started the processing; if the result shows OK, start a processing to collect
and transfer the log.
Failure in a ping test can cause "NG!"; in such a case, select "LOG2SRVR" again to try
again.
e) "OK!" is displayed when the processing is successfully completed. "NG!" is displayed when
the processing fails.
When there is any debug log file that has been automatically saved in the sublog storage
space, send it to the server as well.
f) Multiple debug logs are archived into one file to be sent to the server.
The archived name is automatically given as follows: "date and time", "serial number", "MN-
CONT"
A file name example: 20100425_13-26-ENS00059-V01.44_Debuglog@Server.bin
In the above example, "20100425_13-26" shows the date and time of log collection (the
date and time set in the machine),
"ENS00059" the serial number,
"V01.44" the firmware version of the Main Controller (MNCONT), and
"Debuglog@Server" shows that the log was "collected with "DBG-LOG>LOG2SRVR".
Note:
The log file is deleted from the device once it is collected into the server.
6-95
6-95