User Manual

Maintenance RF-Orchestra!™ Transmitter Installation and Operation
6-12 6880493G02-C July 2000
These errors may be caused by incorrect network link delay or incorrect router committed
information rate (CIR). If the RF-C! controller is not locked to the GPS receiver, the RF-C!
controller will either send packets too late to be launched or too early and overrun the RF-B!
transmitter controller buffer space. The inconsistent data may cause the RF-B! transmitter
controller to illogically couple packets.
To check for plug-and-play errors, complete the following steps:
1. Verify that the following parameters are correct for the RF-O! transmitter:
2. Check to ensure the plug-and-play data cable is properly connected to J4 on both the
RF-O! transmitter and RF-B! transmitter controller backplanes.
Check Control Data Received by the RF-O! Transmitter
To determine whether the RF-O! transmitter is receiving control data from the transmitter
controller, complete the following steps
1. Verify the RF-O! transmitter is receiving control commands from the RF-B! transmitter
controller with a Plug-and-Play Control Data trace (the trace does not show messaging
data).
– Typical Sync and SCI Pattern (FM only Data):
– Typical Voice Page Pattern (FM and AM Data):
E_INVALID_NEXT_MODULATION_TYPE,
E_INVALID_NUMBER_OF_SUBCHANNELS,
E_MOD1_INPUT_OVERFLOW_ERROR,
E_MOD2_INPUT_OVERFLOW_ERROR,
E_MODULATION_TYPE_ERROR,
E_START_TIME_ERROR,
E_SYMBOL_DATA_COMMAND_FORMAT_ERROR,
E_UNEXPECTED_SYMBOL_COMMAND_ERROR,
E_WORK_AHEAD_WINDOW_ERROR
RFO FIPS: r 2058
RFO FIPS: RR 2058 50000 (default min work ahead time is 50000 us)
RFO FIPS: r 2059
RFO FIPS: RR 2059 50000 (default work ahead width is 50000 us)