User Manual
Table Of Contents
- Foreword
- PSG Limited Equipment Warranty for U.S. And Canadian Markets
- PSG Limited Equipment Warranty for NonU.S. and Non-Canadian Markets
- Introduction 1
- System Description 2
- The Wireless Messaging System Overview
- FLEX, ReFLEX and InFLEXion Messaging Protocol Overview
- RF-B! Transmitter Controller Functional Description
- RF-Baton! Transmitter Controller Specifications
- Preinstallation 3
- Installation 4
- Operation 5
- Maintenance 6
- Troubleshooting
- Data Path Diagnostics
- GPS Diagnostics
- Removal and Installation
- Assigning an RF-B! Transmitter Controller to a Multicast Group
- Remote Software Download from Choreographer! Network Manager
- Local Software Download Using the Front Panel
- Parameter Database Updating
- Abbreviations and Acronyms A
- Connector Pinouts B
- FIPS Action Commands and Parameter IDs C
- Alarms and Error Messages D
- Traces E
Operation RF-Baton! Transmitter Controller Installation and Operation
5-28 6880497G01-B June 1999
Station Error Log
The station error log contains the station operational errors logged during operation. This log
can be used to determine an operational history of the RF-B! transmitter controller. To read the
station error log, perform the following steps:
1. Establish a FIPS session (see paragraph, "Service Terminal").
2. Read the station error log.
At the prompt, type:
a 104 <Enter>
The service terminal lists the recorded station errors.
Each log entry line contains the following information:
<Type><Action><Error Code><Caller><Line Num><Timestamp><Occurrences>
Table 5-12 describes the log entries.
Table 5-12: Station Error Log Entries
Entry Description
Type Helps to 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, and so forth.
Action Tells what action the error logging mechanism took when the error occurred. The action can be
either RESET_STATION or LOG_ERROR (nonfatal, error was logged, but station was not reset.)
Error Code Identifies individual errors. The tables in this Appendix D contain descriptions of each of the
possible error codes.
Caller Identifies the software source code module that logged the error. Used for software debugging.
Line Num Identifies the physical line number of the calling software source code module from where the
error was logged. Used for software debugging.
Timestamp Marks the GPS time when the latest occurrence of the error was logged. If GPS time is not
known at the time the error is logged, the Timestamp contains the current value of the onboard
clock, which starts timing from 1996/04/02.12:00:00 upon reset.
Occurrences Gives 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 are made.