User Manual
Table Of Contents
- Human Exposure Compliance 1
- Introduction 1
- System Description 2
- Wireless Messaging System Overview
- FLEX, ReFLEX, and InFLEXion Messaging Protocol Overview
- RFO! Transmitter Functional Description
- RFO! Paging Station Options
- Hardware Options
- Software Options
- Network Peripheral Options (Option X267)
- RF-Baton! Transmitter Controller without GPS Receiver (Option X594)
- RFB! Transmitter Controller with GPS Receiver (Option X179)
- Battery Revert (Option X649)
- RFO! Transmitter Peripheral Options (Option X263)
- RFA! Receiver (Option X349, X351, X352, X353)
- RFA! Receiver Peripheral Package (Option X88, X89)
- Equipment Specifications
- Electrical Requirements
- Preinstallation 3
- Installation 4
- Operation 5
- Establishing an RF-O! FIPS Session
- Reset and Initialization
- Operation Modes
- Alarm and Error Logs
- General Operational Setup and First Time Use
- RF-O! Paging Station Parameters
- RF-O! Power Control
- Power Metering
- Wattmeter Calibration
- Amplitude Alignment
- Power Set
- Module Monitoring
- Power Cutback/Shutdown
- Power Leveling
- Alarm Reporting
- Subchannel Configuration Control
- Power Amplifier Configuration Control
- Carrier Feedthrough Nulling
- RF-O! Ambient Temperature Monitoring
- High Ambient Temperature Cutback/Shutdown Operation
- High PA vs. Ambient Temperature Cutback/Shutdown Operation
- Maintenance 6
- Troubleshooting
- Check Front Panel Indications
- Verify Data from the RFB! Transmitter Controller
- RFO! Transmitter Status
- Power Cutback LED is Blinking
- Power Cutback LED is Continuously Illuminated
- Check for Plug-and-Play Errors
- Check Control Data Received by the RFO! Transmitter
- Check RF Power Path
- Check Transmitter Frequency
- Check RF-A! Receiver Functionality
- Pages Not Received
- Voice Quality Diagnostics
- Removal and Replacement
- Cabinet Doors Removal
- Cabinet Doors Replacement
- DC-DC Converter Removal
- DC-DC Converter Installation
- Orchestra Control Board Removal
- Orchestra Control Board Installation
- Exciter Removal
- Exciter Installation
- Power Amplifier Removal
- Power Amplifier Installation
- Power Supply Removal
- Power Supply Installation
- Wattmeter (Power Detector) Removal
- Wattmeter (Power Detector) Installation
- Battery Removal
- Battery Installation
- AC Distribution Panel Removal
- AC Distribution Panel Installation
- RFO! Transmitter Backplane Removal
- RFO! Transmitter Backplane Installation
- RF-A! Receiver Removal and Replacement
- RFB! Transmitter Controller Removal and Replacement
- Resetting the Parameter Database
- Paging Station Alignment
- Temperature Calibration Procedure
- Software Download
- Troubleshooting
- Abbreviations and Acronyms A
- Backplane Connectors B
- Model and Options Charts C
- FIPS Action Commands (ver 2.0.0) D
- FIPS Read/Write Commands (ver.2.0.0) E
- Alarms and Error Messages F
- Transmitter Alignment Checklist G
- Debug Traces H
Operation RF-Orchestra!™ Transmitter Installation and Operation
5-12 6880493G02-C July 2000
Error Log
The error log contains the transmitter operational errors logged during operation, and this log
is not cleared by a reset. Use this log to determine an operational history of the RF-O!
transmitter. To read the transmitter error log, perform the following steps:
1. Establish an RF-O! transmitter FIPS session.
2. Read the transmitter error log. Type this command:
a 104 <Enter>
The service terminal lists the recorded station errors. Table 5-5 describes each error log
entry. Each log entry line contains the following information:
<Type><Action><Error Code><Caller><Line Num><Timestamp><Occurrences>
Table 5-5: 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, and GPS.
Action
Tells what action the error-logging mechanism took when the error occurred. The 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 document 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.