13.3 Configuring an alarm log
Default
Per default, the alarm log contains all alarms and messages - with their incoming and outgoing
time stamps - in chronological order since the last boot. The exceptions are messages from
the NC part program (msg command).
Contrary to the "Alarm List" or "Messages" window, all of the alarms or messages that are no
longer active when the log is displayed are also displayed (historical alarm events).
Specify the number of results
The alarm log is organized as a ring buffer: When the maximum size is exceeded, the oldest
entries are overwritten by the new alarm events. Each incoming or outgoing time stamp
represents a separate event.
Persistent storage (permanent storage)
If required, the alarm log can be set up as a persistent log that also contains alarm events from
before the last time it was switched on. This means that the log is then either time controlled
or for each alarm event, is backed-up in an internal binary format in the file system.
Depending on the hardware being used, for the NCU, the alarm log is saved on the
CompactFlash card or for the PC/PCU, on the hard disk.
NOTICE
Shorter CF card service life
If the alarm log is a continuously written to the CompactFlash card, then only a limited number
of write cycles is possible. Therefore, ensure that the storage is only performed when there
is a justifiable need! Undo the setting "at every event" if you no longer require that the alarm
log is saved.
The CompactFlash card has a service life of over 10 years for an average written data volume
of approx. 60 MB/day.
The alarm log is not saved in the default configuration.
Configuring an alarm log
● Via the operator software in the "Diagnostics" operating area
● Via the "slaesvcconf.xml" configuration file
Configuring alarms
13.3 Configuring an alarm log
SINUMERIK Operate (IM9)
Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1 277
To Next Page
Loading...
Need help?
General
