User Manual

Table Of Contents
Alarms and Error Messages RF-Orchestra!™ Transmitter Installation and Operation
F-2 6880493G02-C July 2000
RF-O! Transmitter Error Logs
The RF-O! transmitter error log is read through the RF-O! FIPS a 104 command. This
command displays all currently logged errors.
Error Log Description
Each log entry line contains the following information:
<Type><Action><Error Code><Caller><Line Num><Timestamp><Occurrences>
Each item in the entry is defined in Table F-2. The following example shows a typical RF-O!
transmitter error log (See Figure F-1).
Figure F-1: Typical RF-O! Transmitter Error Log
Table F-2: Log Entry Definitions
Information Item Definition
Type
Helps determine which subsystem within the module caused the error condition.
Type value examples: NVM, DSP,STATION_ERROR,GPS.
Action
Tells what action the error logging mechanism took when the error occurred. Action
can be either RESET_STATION (fatal error, station was reset) or LOG_ERROR
(nonfatal error was logged, but station was not reset.
Error Code
Identifies individual errors. The tables in this appendix contain descriptions of each
possible error code.
Caller
Used for software debugging. The caller represents the software source code
module which logged the error.
Line Num
Used for software debugging. The line num is the physical line number of the calling
software source code module from where the error was logged.
Timestamp Not currently supported on the RF-O! transmitter.
Occurrences
Number of times the current combination of Type, Action, Error Code, Caller, and
Line Num have occurred since the log was last cleared. Different Callers can log
the same Error Code, and separate log entries will be made.
RFO FIPS: a 104
<STATION_ERROR><LOG_ERROR><S_STATION_RESET><ROOT><354><1996/04/02.12:00:00><1>