Paradise Datacom P300 Series Installation & Operating Handbook page 225

Tx Warn: RS Encoder FIFO slip
Tx Warn: Turbo encoder status
Tx Warn: Carrier muted as Ref settles
Tx Warn: BUC Mute as Ref settles <2Min
Tx Warn: BUC Power exceeds P1dB point
Tx Warn: Cannot hold power set at BUC
RX TRAFFIC FAULTS
(Bottom line of disp l
Rx Fault: Demod unlocked at <nn.nnnn>MHz
Rx Fault: FEC sync lost (demod locked)
Rx Fault: De-interleaver sync lost
Rx Fault: Frame sync lost
Rx Fault: TS32 Multiframe sync lost
P300H P300 Series Modem Installation and Operating Handbook
empty). This should never occur in operation (contact factory).
The FIFO, which interfaces the Framer to the Reed-Solomon encoder, has slipped (full or empty).
This should never occur in operation (contact factory).
This is a warning used in the engineering debugging process it should not occur in the field. If it does,
please consult the factory.
This is displayed for 30 seconds from a cold start as the Tx carrier is muted while the frequency
reference temperature stabilises. If a power outage is less than 30 seconds, then the mute is for the
same period as the power outage.
The Modem is configured to operate with a Paradise BUC and to supply a 10MHz reference `up the
coax`. From a cold start the modem will switch of the BUC Tx output for 2 minutes until the internal
reference has settled to avoid bringing up carriers off frequency. After 2 minutes the BUC On/Off
status is returned to it s previous setting. If a power outage is less than 2 minutes, then the mute if for
the same period as the power outage. This is different to the Tx Carrier mute above as it mutes the
BUC itself and will therefor mute any number of carriers transmitted through a single BUC.
The Modem is configured to operate with a Paradise BUC and communicate by FSK. The modem
has read the measured power at the BUC output and it exceeds its P1dB point of this BUC. This
means the BUC is approaching or is into compression, and as such may be degrading the
transmitted spectrum. Either back off the power or monitor the Tx spectrum very carefully.
The Modem is configured to operate with a Paradise BUC, communicate with the BUC by FSK, and
the Modem / BUC are set in `Terminal` mode where the modem maintains the power at the BUC
flange by adjusting both the Tx Carrier Level and where available the BUC attenuator. Currently both
of these adjustments are at an end stop, and the modem cannot adjust the levels any further in order
to try and maintain the set flange power.
Rx Traffic Faults: Rx OK LED Off and Rx Traffic (prompt) relay.
The Demod cannot find a carrier to lock to at the specified frequency. Check the frequency; check
the Data rate and FEC settings (use Info, View Config, Rx). Perhaps check the demod itself by
enabling a IF Loopback (Test, Loopback, IF).
The Demod can lock to the carrier, but the inner FEC decoder (Turbo, Vit or Seq) cannot lock to the
demodulated data. Check you have the correct FEC settings (ie Turbo, Vit or Seq as appropriate,
use Info, View Config, Rx). The most common other cause is Spectrum Inversion; you can check this
by temporarily turning on the Rx Spectrum Inversion (Change, Rx, Demod Spect Inv).
The Demod can lock to the carrier, and the inner FEC decoder to the demodulated data. However
the Reed-Solomon De-interleaver cannot find sync with the decoded data. Check the RS de-
interleaving depth, then the values of `n` and `k`(use Info, View Config, Rx). On Non-Paradise Tx
modems, check the V.35 scrambler is not enabled in addition to the Reed-Solomon scrambler.
The modem cannot find the IBS or IDR frame sync on the receive data. Check the Rx Service
settings (Change, Rx, Service), although as the service type affects the composite data rate over
satellite, it is more likely the demod will fail to lock rather than this message appears if the wrong
service type is selected. On Non-Paradise Tx modems, for IBS, check the V.35 scrambler is not
enabled in addition to the IBS/SMS scrambler.
The modem cannot find the IBS TS32 Multiframe sync on the receive data although it has found
Frame sync (otherwise the message above would display). This is only likely in Custom IBS modes
where the operator has the option of sending a TS32 Multiframe or not. Note that for low data rates
Page 225