Rockwell Automation T80020 Application Note Diagnostic Procedures - Manual (Page 37)

Trusted TM
AN-T80020 Diagnostics Procedure
Issue 12 Feb 11 AN-T80020 37
Processor System Event Logs
If an 8000 series processor shuts down, the reason may be documented in the processor's event log.
The processor keeps two event log files. One is the current log and is written to during operation. On
starting, the processor swaps to the other log file and leaves the original file as a record of the events
before it last shut down. This is the backup log, and it may reveal the reason for a shutdown that
caused the processor to stop completely.
If a processor is started up again more than once, the evidence for the first shutdown is lost because
the processor will have overwritten both log files. The backup log will now only document the last start-
up attempt.
Another log is kept by the operating system kernel. This records the fault found when the processor
firmware was last halted by the kernel. This log is kept in memory even after repeated restarts, but is
lost if the non-volatile RAM is erased. The only kernel fault that is normally expected is 1F5, which is
found in a processor that has shut itself down after handing over to another processor. 1F5 is a
watchdog timeout caused by the firmware deliberately not resetting the watchdog, in order to shut
down the module. Any other kernel fault needs to be captured and reported.
Before restarting the processor, connect a terminal program (Teraterm or Hyperterminal) with a
maintenance cable. Set the keyswitch to ‘Run’ and set the terminal program to collect data to a file.
If you can connect, collect the current and backup logs by typing:
ls b
ls d
ls k
If you have the Analysis Tool, collect the processor data online and save it in a file. This includes the
logs listed above.
If you cannot connect, restart the processor only once, even if the system does not function properly
first time. Collect the logs as above.
After collecting the logs, proceed to establish normal operation, including further restarts if required.
Send the data files to ICS Triplex Technology for investigation. They may request further information,
such as:
Logs from I/O modules
Application and System.INI file
Please do NOT send:
• SOE logs; these are never useful for diagnosis; they are system specific and only document
the state of I/O points, not system health.
• Screenshots of I/O configurations or data values
• Event logs from graphics stations
• Videos of LED states. These create large files which will delay email delivery. Instead, note
the colours/flashing state as requested above.