User Manual

Table Of Contents
D-20 6880493G02-C July 2000
FIPS Action Commands (ver 2.0.0) RF-Orchestra!™ Transmitter Installation and Operation
D-20 6880493G02-C July 2000
Read Error Log
a 104
Returns the Error Log.
Each error is returned in the format:
<Type><Action><Error Code><Caller><Line
Num><Timestamp><Occurrences>
Type - helps determine which subsystem within the
module is responsible for the error condition. The Type
can take on values such as NVM,
DSP,STATION_ERROR,GPS, etc.
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 (non-fatal, error was logged, but station
was not reset.)
Error Code - used to identify individual errors. The
tables in this document contain descriptions of each of
the possible error codes.
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 - The time when the latest occurrence of
the error was logged. During a reset and/or until the
BCM locks GPS, the timestamp will contain the current
value of the onboard clock, which starts timing from
1996/04/02.12:00:00 upon reset. If there is a BCM
present and it locks GPS, the onboard clock will be set
to the GPS Date/Time, which is GMT.
Occurrences - the number of times the current
combination of Type, Action, Error Code, Caller, and
Line Num have occurred since the log was last cleared.
Note that different Callers can log the same Error Code,
in which case separate log entries will be made.
Use RFO FIPS: a 111 to clear this log.
RFO FIPS: a 104
RFO FIPS:
<STATION_ERROR><LOG_ERROR><S_RSR_SOFTWARE_WATCHDOG_RESET> <ROOT>
<653><1996/04/09.12:30:30> <1>
Name and
Command
Description Example