Table of Contents
Advertisement
TROUBLESHOOTING
_________________________________________________________________________________________________________
PROBLEM
BS Detected & No
Connection
Low Throughput
Console Messages are
Slow or Garbled
COM-00-21-03
Version No.: A
TROUBLESHOOTING PROCEDURE
If the BS signal is detected (DL ACQUIRED) but a connection is not
established, then the following needs to be determined:
An RF scan using Apollo should be performed to verify that there
is no interference in the channel. This needs to be performed at
both the RS site and the BS site. Note that often the BS site is
installed on a high tower and as such, the antenna is more
susceptible to interference which could obscure the reception of
the signal from the RS. Omnidirectional antennas will tend to
experience greater interference than sectorized or directional
(Yagi) antennas.
Verify the orientation (both horizontal and vertical) of the antennas.
Check the TX power of each unit. If both units are transmitting at
maximum power, then there is most likely an issue with the RF
path. Note that the BS actively controls the TX power of the RS, so
if the RS is transmitting at maximum power, it is an indication that
the signal level is too low at the BS. In this case, interference may
be obscuring the signal, the antennas are misaligned (which
reduces the signal level), the RF cabling or lightning protector is
damaged, or water has entered the connectors or cables.
The throughput is dynamically determined based on the RF
environment and the default configuration for this is shown in the
following table:
To increase throughput, the CINR needs to increase to support the
higher modulation techniques as shown.
* 64 QAM 1/2 is not implemented as it provides the same performance as 16 QAM
13/4
** Note that FEC 7 (64 QAM 5/6) is only implemented in Uplink by Mercury
Verify correct interface settings for console
5-2
OCTOBER 2021
Advertisement
Table of Contents
