PRELIMINARY
Customer Support (202) 333-7031
5-1
These troubleshooting tips are intended to help the user fix any problems that may cause an alarm alert.
When a certain alarm condition exists, read through all the troubleshooting steps to make sure you
understand all of the possible causes of the alarm conditions.
The steps provided do not necessarily need to be performed in the order they are given, rather they
should be performed in order of convenience. For example, if the first step is to check the far end Modem
unit and the second step is to check the antenna alignment but it is much easier to check the antenna first,
then you should do that before going to the far end of the link. When prompted to run any tests, make
sure to use a good input data stream. Using a BERT to generate the data can do this. The BERT will
then read and compare the output to the original input. If the alarm continues after going through the
troubleshooting steps, please contact
ioWave
Technical Support.
Singular Alarm Conditions
5.1 Transmit LOS
No data into DSX or G.703
1. Check connection to CPE.
a. Verify that the CPE is connected to either the DSX or G.703 interface.
b. If connecting to the G.703 interface, make sure that TX on the Modem unit is connected to
RX on the CPE and that RX on the Modem unit is connected to TX on the CPE.
c. Check the cable for continuity or visible damage.
2. Check that CPE is configured correctly and working properly. Consult the documentation for the
CPE for this.
5.2 LIU Not Responding
Error in the communication between the control processor and the LIU chip
This is usually a fatal alarm condition that indicates a problem the user cannot fix. Call
ioWave
Technical Support.
5.3 Firmware Not Responding
Error in the communication between the control processor and the
firmware controlling the FEC and spreading chip
This is usually a fatal alarm condition that indicates a problem the user cannot fix. Call
ioWave
Technical Support.
SECTION 5 TROUBLESHOOTING ALARM CONDITIONS FOR ioLink 4
