• 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)
Security of the Operation Log
The following operation logs related to security are not saved.
• User ID
• Password
• IP address
• Telephone number
• Encryption key
• Transition to SP mode
Also, the following operation logs are not saved.
• Soft keyboard on the touch panel display
• External keyboard
Retrieving the Debug Logs
• Retrieve the debug logs to identify the time and date of the problem occurred and to learn the
details of the issues; e.g. at 8:00am on March 10, an engine stall occurred. The operation
panel is not responding. Turn the main power OFF/ON.
• You need to retrieve the debug logs dating back three days from the date of the problem,
because the software development department needs the logs from three days ago to
determine what lead up to the problem.
• 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.
To Next Page
Loading...
