Table of Contents
Advertisement
5-4
Using BBTALK to Test the ADFM
BBTALK allows you to send direct commands to the ADFM. You may use
the following commands to further test the system.
5-4.1
Diagnostic Tests
The diagnostic test checks the major ADFM modules and signal paths. We
recommend you run this test before a deployment. If any test fails, call
MGD for further troubleshooting information.
a. Start BBTALK. Press the
b. Type
c. Type
>pc
Transducer Communications:
Recorder BIT (RT ):
Modem (MO ):
System Voltages (PT2):
CPU RAM (PI ):
Timing Card RAM (PI ):
Demodulator RAM (PI ):
Checksum Code/Tables (PT8):
Receive Test (PT3):
Transmit Test (PT4):
Electronics Wrap Test (PT5):
LPF Bandwidth Test (PT6):
Clock Interrupt (PI ):
Error Log:
Power Loss
Auto Restart Occurred
Transducer Communications Error
Self Tests Complete
Many users tell us their ADFM reports a FAIL condition during the self-
tests that check the ADFM's "electronics wrap test." In most cases, the
cause of the failure is external interference. A "noisy" environment, such as
in a lab usually causes this external interference. You can take a few simple
steps to find out if the FAIL condition is being caused by external interfer-
ence or by a problem with the ADFM.
The following procedure explains how to conduct the PC test to reduce the
likelihood of a false failure.
a. Turn off any nearby equipment (monitors, radios, etc.) that is not
needed to conduct the test.
b. The electronic housing case should be closed to help shield the circuit
boards from external electronic "noise."
c. The ADFM transducer head must be immersed in water. Ensure there
are no air bubbles on the transducer faces.
ADFM Technical Manual (January 2000)
End
CP
to clear the fault log.
PC
. A message similar to the following should appear.
ADFM Test Procedures
key to wake the ADFM.
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
PASS
page 5-3
Advertisement
Table of Contents
