TM 11-7025-221-20
2-9. TD-1337(V)/G Troubleshooting.
Use the procedures in this paragraph to start troubleshooting a TD-1337(V)/G. The troubleshooting procedures
are In the form of an easy to follow flowchart. The flowchart is arranged so that you will identify and
replace the faulty assembly or be directed to another paragraph to continue troubleshooting.
a. Description of Troublshooting Flowchart. The left-hand side of each flowchart page contains a
series of decision blocks with each block describing a particular fault condition. Adjacent to each block
Is the action to be taken for that fault condition. Following are descriptions of these fault conditions.
(1) POWER AC or DC Indicators Off. Either or both of these indicators being off indicates a power
problem.
(2) ALARMS hdicator(s) Lit. There is a block for each ALARMS indicator. One or more of these
Indicators will light when the TD-1337(V)/G detects a fault. if more than one indicator is lit, perform the
action with the first lit indicator appearing In the flowchart.
(3) Display/Keyboard Problem. Use this block to start troubleshooting when entries made on keyboard
are not displayed correctly (or missing) on display.
(4) Dedicated User Problem. There would be no ALARMS indicator lit. Use this block to start trouble-
shooting when a problem is reported by the dedicated user.
(5) Download To Standby Problem. There would be no ALARMS indicator lit, Use this block to
start troubleshooting when it is determined that a download standby routine cannot be performed properly
with a standby TD-1337(V)/G.
(6) Orderwire Problem. There would be no ALARMS indicator lit. Use this block to start trouble-
shooting when you have an orderwire probliem.
(7) Group Problem. There would be no ALARMS indicator lit. Use this block to start troubleshooting
when a problem is reported by a earth-side user connected to one of your input/output ports.
(8) Control Te/emetry Problem. There would be no ALARMS indicator lit. Use this block to start
troubleshooting when you cannot perform a transmit download routine or receive control telemetry routine
Property.
(9) CNCE Reports Loss of CESE. There would be no ALARMS indicator lit. Use this block to start
troubleshooting when the CNCE reports a loss of CESE data.
b. Use of Troubleshooting Flowchart. Go to the START entry in the flowchart. Proceed through the
blocks until your fault condition is described. if you have more than one fault condition, perform the trouble-
shooting actions for the first faulot condition appearing in the flowchart. Then, proceed to any remaining
fault conditions. Troubleshooting is completed when no fault conditions exist. Some troubleshooting actions
direct you to replace more than one assembly. in these cases, replace them one at a time, in the order
hated, until fault no longer exists. At the conclusion of troubleshooting, replace any substituted assemblies
with the original assemblies (except for faulty ones). Use appropriate replacement procedures as directed
in c below.
2.12
