8
© 2013-2017 TOSHIBA TEC CORPORATION All rights reserved
e-STUDIO2006/2306/2506/2007/2307/2507/2303A/2303AM/2803AM/2309A/2809A
ERROR CODE AND TROUBLESHOOTING
8 - 3
8.1.2
Collection of debug logs with a USB device
[ 1 ] General description
The purpose of collecting debug log data is to acquire the information needed for analyzing problems
by following the procedure below only when a phenomenon requiring an investigation has occurred
during the MFP's operation. If such a phenomenon occurs, you can collect debug log data into a USB
device by inserting it into the MFP and operating the buttons on the control panel.
Notes: Precautions for collecting debug log data with a USB device
• Be sure to obtain the customer’s agreement before you collect the setting information of the
MFP into a USB device.
• Debug log data to be collected include the internal behavior of the MFP, job histories, memory
usage information, etc. in binary data.
• Since the collected setting information of the MFP is output in a CSV format, handle and
manage it with care.
• Manage the collected setting information of the MFP properly to avoid loss or its leaking.
• Do not use the collected setting information of the MFP for purposes other than the
enhancement of maintenance, product quality or services.
• If the customer requests the presentation of the data, do so promptly.
• Do not remove the USB device while data are being stored.
When the debug logs are collected, do so also for the information from 1 to 4 below since investigation
may be difficult using only the debug logs.
1. List print mode ([9]+[START]) [300: All CSV files]
2. When printing data, acquire information below.
- 9S-101: Adjustment mode (05) (Example: [101]->[START]->[0]->[START]->[9999]->[START])
- 9S-102: Setting mode (08) (Example: [102]->[START]->[0]->[START]->[9999]->[START])
- 9S-103: PM support mode
- 9S-106: Error history (maximum 30 events)
- 9S-108: Firmware update log (maximum 5 events)
- 9S-111: Version list
- 9S-403: 13 code list (when the FAX unit is installed)
3. Problem occurrence time
Or the time when the customer called if it is difficult to work out when it occurred.
4. Status of when you collected the debug logs
As in the example below, check the status to know if the problem occurred at the debug log
collection or how the customer recovered it.
E.g.:
- You checked the problem and connected a USB device to the equipment.
- No problem occurred when an attempt to collect the debug logs was made; however, the
customer did turn the main power switch OFF when the problem occurred, so the logs can be
collected.
Содержание E-STUDIO2006
Страница 14: ......
Страница 729: ......
Страница 730: ...1 11 1 OSAKI SHINAGAWA KU TOKYO 141 8562 JAPAN ...