Table of Contents
Advertisement
Page 136 of 220 Maintenance
Event/Alarm log
553-3601-200 Standard 7.00 November 1998
Status (alarm and event) messages appear on the display and are stored in the
Event/Alarm log.
Alarms indicate important and sometimes abnormal system conditions. The
details of every alarm, including date and time, should be noted as soon as
possible, and the alarm cleared. Alarms may require some action to clear.
With the Event/Alarm log, you can
•
check alarms and events that have occurred
•
check when alarms and events occurred
•
check a current alarm
•
check the number of consecutive occurrences of an event or an alarm
•
erase the log
Because the Event/Alarm log holds a maximum of 50
events, you should check and record these alarms and
events periodically. Erase the log after dealing with the
alarms and events. If your system is also equipped with
Companion Manager, these logs can be printed as a
report.
When the log is full, alarms are replaced with new alarms of
higher priority.
Each event is assigned a severity number. An
S4
example,
) may appear in the event message.
the log is full, new event messages with a higher severity number replace
existing event messages of a lower severity. For this reason, check event
messages at regular intervals and deal with all messages.
If an event or alarm occurs while you are using the Administration Terminal
for programming, your session will not be disrupted. Instead, the alarm
message and beep will occur after the programming session ends.
ATTENTION!
S
preceding this number (for
S1
has the lowest priority. If
Advertisement
Table of Contents
Troubleshooting
