Structure Of The Log File - Siemens SINUMERIK 840D sl Commissioning Manual

Critical alarms
(acknowledgment >= NC reset),
PLC crash signal:
NC channel reset
Tool change
Note
Changes to the override are only logged if the PLC crashes or on a critical alarm with the
IPO trace.
Note
When operating more than one HMI on an NCU (e.g., HMI-Embedded and HMI-Advanced),
the action log must only be activated on one HMI.
8.3.2

Structure of the log file

Overview
When the action log is activated, the following log files are generated:
● Log file "action.com"
● Log file "crash.com"
Both are binary files and are constantly overwritten as ring buffers. When the log files are
displayed, these binary files are converted into readable "action.log" and "crash.log" files.
The entries appear in English and are non-language-specific. The events follow on from
general information, starting with the most recent event.
Log file "crash.com"
The "crash.com" file is empty. Data are written to it after the following events:
● Interface signal DB19.DBX0.6 "Save teleprinter log" changes from 0 to 1.
● The alarm entered in the "Program status on alarm" field is output.
● Even when the action log is deactivated, alarms are still logged in the "alarm.com" log file.
Commissioning HMI-Embedded (IM2)
Commissioning Manual, 01/2008, 6FC5397-8CP10-1BA0
Curr. channel status
Curr. program layer
Curr. actual values of axes
Curr. tool
Curr. G function
Curr. M function
Curr. zero offset
Only subsets of the above events are logged.
Only subsets of the above events are logged.
Diagnostics/Service
8.3 Action log
115