VX150 TO VX2 TROUBLESHOOTING MANUAL RESPONDING TO ALARMS
VERSION 2.0 2023-04-20 PAGE 3.1.21
Host Network Down The Host is not detecting the presence of valid
Ethernet connection to the transmitter.
The Host has detected the presence of valid
Ethernet connection to the transmitter.
The most likely cause of this alarm is a
disconnected or damaged Ethernet cable.
Check that the Ethernet cable is securely
connected to the transmitter.
Host Not Booted The DSP has yet to receive any communication
from the Host.
This alarm is normal for approximately one to
five minutes while the host is booting,
immediately after AC power has been applied/
restored or after a software upgrade.
The remote AUI will not yet be available while
this alarm is present.
This alarm clears immediately once the DSP
has received at least one successful
communication packet from the Host.
If this alarm continues to occur for more
than 30 minutes after AC power has been
applied to the transmitter, cycle (turn off,
then on) the AC power. If the alarm
continues to persist after an additional
30 minutes, it is likely the SD card is
corrupted. Replace the SD card with a
backup SD card or perform a software
update to restore the SD card to a
functional state.
Host Not Responding The DSP has not had any communication from
the Host for greater than 60 seconds.
The remote AUI may not be available while
this alarm is present.
This alarm clears immediately once the DSP
has received a successful communication
packet from the Host.
This alarm is most likely caused by an
issue with the Host either becoming
excessively busy or crashing.
Reboot the transmitter or cycle the AC
power to force the Host to reboot
Invalid Date & Time After AC power has been applied/restored or
after a software upgrade, the Real-Time Clock
reported that an invalid date and time was
retrieved and the system has not had valid
date and time set.
A valid date and/or time has set via any of the
following methods:
Set in the FPUI
Set in the AUI
Via NTP when it is enabled
Received over RDS when enabled
The most likely cause is that the
transmitter has been left unpowered for
an extended period of time and the Real-
Time Clock lost power. Set the time and/
or date via one of the methods listed.
If this does not resolve the alarm, it could
be caused by a component failure on the
Exciter PWB. Consider replacement of the
Exciter PWB. See
Exciter PWB
Replacement on page 3.1.37.
Invalid FPGA Image Signature not available at time of release
Alarm Name Trigger Conditions Clear Conditions Troubleshooting
To Next Page
Loading...
