User Manual

Table Of Contents
Alarms and Error Messages RF-Orchestra!™ Transmitter Installation and Operation
F-30 6880493G02-C July 2000
RF-O! Alarms
Reading the Alarm Logs on the RF-O! (RFO FIPS: a 99)
The Alarm Log is used to hold error/alarm conditions that are relayed to the RF-B! transmitter
controller using the Maintenance Path. All Alarm Log entries have a corresponding Error Log
entry, but not all Error Log Entries appear in the Alarm Log. Alarm Logs are primarily
reserved for RF-O! transmitter conditions that warrant immediate attention, signalling a
module failure, or some other interruption of messaging traffic.
Alarm Logs can be read on the RF-O! transmitter using the RFO FIPS: a99command. Entering
RFO FIPS: a 99 causes all currently logged alarms to be displayed.
When the RFO FIPS: a 99 command is issued, all currently logged alarms are returned to the
terminal. The example below shows a typical alarm log on the RF-O! transmitter.
Figure F-2: Typical RF-O! Transmitter Alarm Log
Each log entry line contains the following information:
XXYYY - <Description>
XX - (Alarm Status). Either AL or OK. AL indicates that the alarm is still active. OK indicates
that the alarm occurred, but is now cleared.
YYY - (Alarm Count). If XX is AL, these three digits will indicate the number of occurrences of
this alarm since the alarm log was last cleared. The alarm count goes to a maximum of 999,
then stops counting. The count is set to 000 whenever the cause of the Alarm is no longer
present, and the Alarm Status changes from AL to OK.
<Description> - A brief textual explanation of the alarm.
RFO FIPS: a 99
RFO FIPS: RA 99
Reported Alarms
---------------
AL001 - Alarm Occurred Due to OCM Reset.
OK000 - Transmitter Disabled Due To High OCM Ambient Temperature.
OK000 - Transmitter Disabled - (Check Disabled Status via FIPS: A 83).