TROUBLESHOOTING
4-4
Document No.: COM-00-05-16 June 2006, Revised June 2014
Version: C.1
To isolate the problem, power off the WAG or the ATCS device on the LAN. On the computer,
open a DOS window and ping the IP addresses for both devices. If a ping response is received,
another device shares an IP address the user wants to use. To solve the problem, ping the next
sequential IP address until the user finds an IP address that is not being used. Assign it to the
ATCS device or the WAG.
Be careful to avoid assigning an IP address that is already assigned elsewhere on a device that
is currently powered down. When that device is powered up in the future the user will see this
problem again.
4.4
WAG LIGHTS ARE OFF
Typical reasons for the POWER OK LED to be off include:
•
The B/N battery leads on the J4 connector do not have power applied
•
The polarity on the B/N battery leads is reversed
•
The voltage is out of specification
To diagnose the above problems, use a voltmeter to verify that the power supply is within voltage
specification and that the polarity is correct.
•
The power connector can be faulty, either a broken connector or the wires to the connector
are broken or shorted. Use a voltmeter at the B/N pins to verify that the power is getting to
the pins.
It is possible that the hardware is damaged such that the DC to DC converter inside is not
working. Because the LED is hard-wired to be ON when power is applied, if power is good at the
B/N pins at the battery connector, the DC/DC converter may be damaged. Verify the voltage at
the B/N pins are within specification and the correct polarity.
If power is correct, send the WAG in for repair.
4.5
WAG WILL NOT COMPLETE THE BOOT PROCESS
The user might see the boot menu appear over and over again on a terminal emulator. Typically
this failure shows the menu, pauses for 5 seconds, and then shows the menu again.
If this occurs, the Executive software stored in the WAG FLASH ROM is corrupted. The user must
download a new Executive to the WAG using the boot menu option. For more information about
this procedure, see Section 5.
Another way the user can see this failure is when the boot menu appears on the terminal
emulator screen, the Executive boots successfully, but the Executive code either does not appear
to run or it runs for a short period of time.