11-APR-06 Rev E OMACS3000
40 of 51
System Screens
Figure 30: Satellite Table Entry Edit Screen
Logs/Alarms
Events and alarms are tabulated in a circular file that contains the time of the event/alarm, the description of
the event/alarm, and any pertinent data. Many of the events are informational and are being logged for
diagnostic purposes. Alarm events are often included twice - once when the alarm condition occurs, and
again when the alarm condition is corrected.
The Logs/Alarms button has six options that are activated by right clicking on the Logs/Alarms button. In
order to select one of the three options, the option must be highlighted and then selected with the mouse and
a left click.
Audible alarms are generated if the Enable Alarms option is set. No audible alarms are generated if the
Disable Alarms option is set but the alarms are still logged. The disable only disables the audible signal, not
the logging of the alarms. (See
Figure 31
.)
The Enable Java Console Output to File option will write all Java console output to a local file. The Disable
Java Console Output to File option will discontinue writing any Java console output to a local file and prevent
any console output being written to a local file.
The Clear Log option clears all alarms and events in the log file. Only events or alarms happening after the
Clear Log option has been selected will be displayed in the log file. For example, persistent alarms such as
direction errors or software limits (if present) will be logged again after the Clear Log is selected.
The Reload Event Log option will write an event log to a local file and will use the time and date as part of
the name of the file to distinguish it from previously written event logs. Note: The event log is also written to
a local file whenever 2000 events have occurred. The ACS3000 event log is a circular log that contains a
maximum of 500 events. However, the Java browser will save up to 2000 events in its memory before
downloading the event log to a local file.