Professional Documents
Culture Documents
TECHNICAL MANUAL
ORGANIZATIONAL
AND
INTERMEDIATE MAINTENANCE
AVIONICS
DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD Contractors only (Administrative or
Operational Use) (1 October 2010). Refer other requests for this document to AFLCMC/WIUBC, Robins AFB, GA 31098.
WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751, et
seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et seq. Violations of these export laws are subject to
severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.
HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the
contents or reconstruction of the document.
A Change X USAF
TO 1H-60(H)G-2-12-3
Change X B
TO 1H-60(H)G-2-12-3
C Change X
TO 1H-60(H)G-2-12-3
7-177 Added . . . . . . . . . . . . . . . X
7-178 Blank Added . . . . . . . . . . X
7-179 Added . . . . . . . . . . . . . . . X
7-180 Blank Added . . . . . . . . . . X
7-181 Added . . . . . . . . . . . . . . . X
7-182 Blank Added . . . . . . . . . . X
7-183 Added . . . . . . . . . . . . . . . X
7-184 Blank Added . . . . . . . . . . X
7-185 Added . . . . . . . . . . . . . . . X
7-186 Blank Added . . . . . . . . . . X
7-187 Added . . . . . . . . . . . . . . . X
7-188 Blank Added . . . . . . . . . . X
7-189 Added . . . . . . . . . . . . . . . X
7-190 Blank Added . . . . . . . . . . X
7-191 Added . . . . . . . . . . . . . . . X
7-192 Added . . . . . . . . . . . . . . . X
TABLE OF CONTENTS
Change 19 i
TO 1H-60(H)G-2-12-3
ii Change 20
TO 1H-60(H)G-2-12-3
LIST OF ILLUSTRATIONS
Change X iii
TO 1H-60(H)G-2-12-3
iv Change X
TO 1H-60(H)G-2-12-3
LIST OF TABLES
If a replacement pin filter adapter is not immediately 12. SCSTC HANDLING AND WARNING
available, annotate the aircraft 781A records with a red PROCEDURES.
diagonal. If an EME modified electrical or electronic
component is replaced by an unmodified component, Any fastener identified as an SCSTC is subject to special
annotate the aircraft 781A records with a red diagonal. handling instructions. No substitutions are allowed with
SCSTC. Only exact replacement parts may be used.
9. KAPTON-INSULATED WIRES. Extreme care should be used to make sure that the correct
component is used in SCSTC applications. Special care
should be taken to ensure that correct torque values are used
NOTE
in SCSTC.
Certain aircraft have wires that are Kapton-in-
sulated. The outer jacket of this type wire is The following warning is used throughout this manual to
dark yellow and provides a surface for wire identify SCSTC procedures:
identification. Under the dark yellow jacket is
the copper-colored, Kapton insulation. Be-
neath the insulation is the silver-coated, elec- WARNING
trical wire. If the outer jacket wears or peels,
the copper-colored insulation may become vis-
ible. Wire repair/replacement is required if the Procedures identified by **SC** are related to
insulation is damaged and/or the electrical Safety Critical Screw Threaded Components.
wire is exposed (TO 1-1A-14). No substitution of parts may be made without
compromising the safety of the aircraft.
10. ELECTROSTATIC DISCHARGE (ESD)
SENSITIVE DEVICES. 13. SCSTC IDENTIFICATION.
This technical order contains maintenance procedures for Most SCSTCs will be painted yellow. Threads will not be
parts and assemblies sensitive to damage by ESD. TO painted. For SCSTC locations which preclude painting,
00-25-234 should be consulted for specific information on most SCSTCs will be stamped with the letter ‘‘C’’ to
how damage can occur to electronic parts, assemblies, and identify the component as a SCSTC. SCSTC maintenance
equipment by ESD and the measures to be taken to protect procedures are identified as follows:
against such damage.
The symbol **SC** placed between paragraph
Paragraphs including specifically identified processes/steps number/letter and title/text identifies the maintenance
that come under the ESD sensitive criteria are marked with procedure affecting SCSTCs.
the symbol **ESD**. The symbol is located between
paragraph number and title or between the specifically Maintenance illustrations will reflect [SC] markings on the
identified process/step number and text. individual items where applicable.
Figures with illustrations including diagrams and schematics 14. ELECTRICAL POWER APPLIED TO
reflecting ESD sensitive items are identified by the AIRCRAFT.
following symbol affixed to the lower right hand corner of
the figure.
vii
TO 1H-60(H)G-2-12-3
viii Change X
TO 1H-60(H)G-2-12-3
7.6 DEGRADED VISUAL ENVIRONMENT (1) Press the Control Head Unit (CHU) power (V*)
SYSTEM (DVES) (AIRCRAFT MODIFIED BY TO button once to start CHU/DVES initialization.
1H-60-1077).
NOTE
Table 7-18. DVES Setup
DVES Setup This takes approx. 2.5 minutes. The CHU will
report status in 20 to 30 seconds.
TOOLS
Ground Support Equipment (2) Wait for the CHU to report OPERATE in the
right pane on the HOME menu page 1 and no
TEST CONDITIONS WCAs reported.
External Electrical Power Connected or APU Operating
NOTE
(TO 1H-60(H)G-2-1)
SPECIAL INSTRUCTIONS WCAs can be viewed on WCA page 1/2 with
fault details on WCA page 2/2.
The DVES operational check is subdivided as follows:
NOTE
7.6.1 Setup.
7.6.2 Normal Operation. During power on, the RSD may be No Go
7.6.3 Shutdown. reporting Removable Memory Cartridge
(RMC) not mounted until 3 to 4 minutes after
7.6.4 DVES Fault Isolation.
CHU/DVES initialization.
c. Enable circuit breaker(s). c. Hold the CHU power (V*) button for 3 seconds
until the Power LED turns from green to orange.
d. Power up DVES as follows:
d. CHU will wait for DVES LRUs to power off and
then will shut itself down.
Change X 7-155
TO 1H-60(H)G-2-12-3
7.6.4 DVES Fault Isolation. The GSE requires a single Acronym Definition
Ethernet connection to the IPU and requires DVES to start in
GCP Guidance Control Program
MAINTENANCE mode. For detailed inspection and
maintenance of specific DVES LRUs see TO 1H-60(H)G-6. GPU Graphics Processing Unit
Fault messages within the DVES can be traced to specific LFP Lidar Frame Program
WCA messages shown in Table 7-19. To isolate system
LIP Lidar Interface Program
faults:
NFP Navigation Filtering Program
NOTE NIP Navigation Interface Program
When Ethernet cable is connected to IPU, DVES NVM Non-volatile Memory
will automatically enter MAINTENANCE mode. OOC Out of Core
a. Attach Ethernet cable to GSE laptop and IPU. PVI Pilot-Vehicle Interface
b. Run Setup (Section 7.6.1) to power on DVES. SBC Single Board Computer
c. Read Fault Messages received from the IPU. SCP System Control Program
SFP Scene Fusion Program
7.6.4.1 DVES Abbreviations and Acronyms. The
following list provides definitions of terms used in the SUP Single Board Computer Utility Program
DVES system. TFTP Trivial File Transfer Protocol
Acronym Definition TOV Time of Validity
AIP Avionics Interface Program FPGA Field Programmable Gate Array
DPP Display Processing Program 7.6.4.2 Warnings, Cautions, and Advisory Messages.
ENAV Electronic Navigation Table 7-19 lists the Warnings, Cautions, and Advisory
FMP File Management Program messages with their definitions that are used by the DVES
7-156 Change X
TO 1H-60(H)G-2-12-3
.
Table 7-19. Warnings, Cautions, and Advisory (WCA) Messages
DVE IPU COMM FAIL The DVE IPU COMM FAIL annunciation indicates a loss of communication
between the IPU and CHU. Loss of communication for this fault is considered to be
when the periodic status message has not been received for at least 30 seconds.
DVE SYS FAIL The DVE SYS FAIL annunciation can occur for the following reasons:
• When the IPU fails to report that it is in the OPERATE state within a period
of 120 seconds after startup.
• When the IPU explicitly reports that it is in the FAULT state.
• When the CHU detects an internal error condition.
This WCA message is displayed on the CHU display only.
DVE DEGRADED The DVE DEGRADED annunciation will occur when one or more LRUs report a
health status that is neither GO or Temperature Warning.
Specific failures are indicated by corresponding fault messages.
DVE HOT The DVE HOT annunciation occurs when an LRU reports a Temperature Warning
health status indicating that the LRU is trending toward an over temperature
condition.
DVE OVERTEMP The DVE OVERTEMP annunciation is triggered when an LRU’s health, as
reported by the IPU, initially indicates a Temperature Warning status and then the
same LRU later transitions to a NO GO status. The overtemp LRU (except for the
CHU, VSE, and AGU) will shut down to self-preserve or the power to that
component will be removed.
DVE CAL MISMATCH A DVE CAL MISMATCH annunciation is triggered when the calibration data
stored in the CHU does not match the reported calibration data sent by the IPU.
DVE SHUTDOWN FAIL The DVE SHUTDOWN FAIL annunciation can happen after a shutdown operation
has been initiated but the CHU detects that communication with the IPU remains
active.
Change X 7-157
TO 1H-60(H)G-2-12-3
7.6.4.3 Fault Messages. Most troubleshooting will be to message.Table 7-21 provides troubleshooting procedures for
confirm system BIT results and check continuity of cabling each of the fault message in the table.
between the IPU and LRUs to which it interfaces.
Suspected faulty LRUs should be removed and forwarded to
Table 7-20 lists the fault messages used within the DVES thigher level maintenance.
system along with an explanation of what triggers the fault
7-158 Change X
TO 1H-60(H)G-2-12-3
Change X 7-159
TO 1H-60(H)G-2-12-3
7-160 Change X
1H-60(H)G-2-12-3
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_CHU_COM_FAULT 1. Perform DVES Reset: DVE_DEGRADED DVE_EGI_COM_FAULT 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) • BIT_NIP_PRIMARY_EGI_TIME a. (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage OUT b. (L4) STATUS Subpage
c. (L2) RESET DVES. • BIT_NIP_SECONDARY_EGI_TI c. (L2) RESET DVES.
2. Problem fixed? - YES, go to step 8 MEOUT 2. Problem fixed (EGI 1 and EGI 2)? – Yes, go to
3. Check for +28 VDC between pins 1 and 3 on the step 9
CHU Power Cable P569. For a BIT_NIP_PRIMARY_EGI_TIMEOUT
4. No +28VDC – Is DVES 5 Amp CB set on Mission 3. Check the DVES NAV/Bezel Data Cable for
Readiness CB Panel? damage and continuity between:
• If CB is set – replace the CHU Power • P583 Pin 4 and P8201 Pin 29
Cable • P583 Pin 5 and P8201 Pin 30
• If CB is not set - set the 5 Amp DVES a. Replace cable if damaged. Go to Step 9
CB. 4. Cable OK? – NO, replace Cable.
5. Problem fixed? – Yes, go to step 8. 5. Troubleshoot aircraft EGI 1 system IAW aircraft
6. Check the IPU Data Cable for damage and maintenance manuals.
continuity between: • If no fault found in EGI 1 system, replace
• P568 Pin 11 and P579 Pin 1 IPU. Go to Step 9.
• P568 Pin 15 and P579 Pin 2 For a BIT_NIP_SECONDARY_EGI_TIMEOUT
• P568 Pin 14 and P579 Pin 3 6. Check the DVES NAV/Bezel Data Cable for
• P568 Pin 18 and P579 Pin 4 damage and continuity between:
a. Replace cable if damaged. Go to Step 8. • P583 Pin 10 and P8225 Pin 29
7. Check for valid signal on P568 pins 11 and 15 and • P583 Pin 17 and P8225 Pin 30
pins 14 and 16. a. Replace cable if damaged. Go to Step 9
• If Signal is good, replace IPU. 7. Cable OK? – NO, replace Cable.
• If Signal is not good, replace CHU. 8. Troubleshoot aircraft EGI 2 system IAW aircraft
8. Turn system on. If no further fault messages maintenance manuals.
appear, the fault has been corrected. • If no fault found in EGI 2 system, replace
IPU. Go to Step 9.
9. Turn system on. If no further fault messages
appear, the fault has been corrected.
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_ENAV_FAULT 1. Perform DVES Reset: DVE_DEGRADED DVE_ENAV_NO_INIT 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) • (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage • (L4) STATUS Subpage
c. (L2) RESET DVES. • (L2) RESET DVES.
2. Problem fixed? – NO 2. Problem fixed? – NO
3. Ensure that none of the following faults are 3. This fault will only occur if one of the following
present. If so, clear any of these faults that exist. faults is also set. Ensure all faults listed below
• DVE CAL DEGRADED have been resolved:
• DVE CAL INVALID • DVE CAL INVALID
• DVE EGI COM FAULT • DVE EGI COM FAULT
• DVE ENAV NO INIT • DVE IMU * (any IMU fault)
• DVE IMU * (any IMU fault) • DVE NAV FAULT
• DVE NAV FAULT • DVE TIMESYNC FAULT
• DVE TIMESYNC FAULT 4. When all faults have been resolved, perform IBIT
4. Verify that both EGIs are in NAV mode. If NO, go to confirm fault does not recur.
to step 6. a. (B5) MAINT Page 1 IBIT
5. Inspect LIDAR and IMU assembly for physical b. (L1) IBIT
damage.
DVE_FLIR_NO_VIDEO 1. Perform DVES Reset:
Note: If the IMU was misaligned to the Lidar, for
example if the chassis was bent, this fault a. (B5) MAINT Page 1 IBIT
may occur. b. (L4) STATUS Subpage
6. Use aircraft/EGI manual to put EGIs in a DVES- c. (L2) RESET DVES.
compatible mode as defined in the DVE NAV 2. Problem fixed? – Yes, go to 5
FAULT Troubleshooting in this table. 3. Check the IPU Video In Cable for damage and
7. Perform DVES Reset: continuity between:
a. (B5) MAINT Page 1 IBIT • P574 Center conductor and P585 Center
b. (L4) STATUS Subpage conductor.
c. (L2) RESET DVES. • P574 Outer conductor and P585 Outer
8. Problem fixed - NO, replace IPU. conductor.
9. Turn system on. If no further fault messages a. Replace cable if damaged. Go to Step 5
appear, the fault has been corrected. 4. Check for valid signal on cable.
• If Signal is good, replace IPU. Go to step
5
• If Signal is not good, troubleshoot FLIR
system IAW aircraft maintenance
manuals.
5. Turn system on. If no further fault messages
appear, the fault has been corrected.
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_FLIR_COM_FAULT 1. Perform DVES Reset: DVE_DEGRADED DVE_IMU_COM_FAULT 1. Perform DVES Reset:
(Cont) • (B5) MAINT Page 1 IBIT (Cont) OR a. (B5) MAINT Page 1 IBIT
• (L4) STATUS Subpage DVE_IMU_TOV_OLD b. (L4) STATUS Subpage
• (L2) RESET DVES. c. (L2) RESET DVES.
2. Problem fixed? – Yes, go to 5 2. Problem fixed? – YES – Go to step 10
3. Check the DVES NAV/Bezel Data Cable for 3. Check +28 VDC power on J71 of the LIDAR/IMU
damage and continuity between: Power Cable:
• P583 Pin 21 and P1073C Pin 1 • Pins 1 and 4 - +28VDC IN
• P583 Pin 22 and P1073C Pin 2 • Pins 2 and 3 – RTN
• P583 Pin 28 and P1073C Pin 3 4. Voltage present? – NO. Go to step 9
• P583 Pin 29 and P1073C Pin 4 For a DVE_IMU_COM_FAULT:
a. Replace cable if damaged. Go to Step 5 5. Check the LIDAR/IMU Data Cable for damage
4. Check for valid signal on cable. and continuity between:
• If Signal is good, replace IPU. Go to step • P571 pin 1 and P572 pin 6
5 • P571 pin 2 and P572 pin 7
• If Signal is not good, troubleshoot FLIR • P571 pin 3 and P572 pin 4
system IAW aircraft maintenance • P571 pin 4 and P572 pin 5
manuals. a. Replace cable if damaged. Go to Step 10
5. Turn system on. If no further fault messages 6. Check for valid RS-422 signals on the pins listed
appear, the fault has been corrected in step 5.
• If Signal is good, replace IPU.
• If Signal is not good, replace lidar
assembly.
• Go to Step 10
For a DVE_IMU_TOV_OLD fault:
7. Check the LIDAR/IMU Data Cable for damage
and continuity between:
• P571 pin 5 and P572 pin 1
• P571 pin 6 and P572 pin 2
8. Check for valid TOV signal on the pins listed in
step 7.
• If Signal is good, replace IPU.
• If Signal is not good, replace lidar
assembly.
9. Check +28 VDC power on J3 of the PDU:
• Pins 1 and 2 - +28VDC IMU
• Pins 3 and 4 – IMU RTN
a. If voltage is present, replace LIDAR/IMU
Power Cable
b. If voltage is not present, replace PDU.
10. Turn system on. If no further fault messages
appear, the fault has been corrected
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_IMU_FAULT 1. Perform DVES Reset: DVE_DEGRADED DVE_LDR_COM_FAULT 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) a. (B5) MAINT Page 1 IBIT
OR
DVE_IMU_MISCONFIGURED b. (L4) STATUS Subpage b. (L4) STATUS Subpage
c. (L2) RESET DVES. c. (L2) RESET DVES.
2. Problem fixed? – NO 2. Problem fixed? – Yes, Go to Step 5
3. Replace lidar assembly 3. Check the LIDAR/IMU Data Cable for damage
4. Turn system on. If no further fault messages and continuity between:
appear, the fault has been corrected • P566 pin 1 and P572 pin 21
DVE_LDR_CMD_MISMATCH • P566 pin 2 and P572 pin 22
1. Perform DVES Reset:
• P566 pin 4 and P572 pin 23
OR a. (B5) MAINT Page 1 IBIT
• P566 pin 5 and P572 pin 24
DVE_LDR_FAULT b. (L4) STATUS Subpage
• P566 pin 15 and P572 pin 26
c. (L2) RESET DVES.
OR • P566 pin 16 and P572 pin 27
2. Problem fixed? – Yes, go to step 6
• P566 pin 18 and P572 pin 28
DVE_LDR_NO_PC_FAULT 3. Check the Lidar/IMU Data Cable for damage and
• P566 pin 19 and P572 pin 29
continuity between:
4. Check for valid signals on cable.
• P566 Pin 7 and P572 Pin 19
• If Signal is good, replace lidar.
• P566 Pin 8 and P572 Pin 20
• If Signal is not good, replace IPU
• P566 Pin 11 and P572 Pin 30
5. Turn system on. If no further fault messages
• P566 Pin 12 and P572 Pin 31
appear, the fault has been corrected
• P566 Pin 13 and P572 Pin 25
a. Replace cable if damaged. Go to Step 7 DVE_LDR_DETECTED_DVE Pilot advisory only.
4. With system powered off, disconnect cable at DVE_LDR_EXCLUDED_LZ_DIST
Lidar connector J1. Then power on system and Pilot advisory only.
check for signal output (a 500 microsecond pulse DVE_LDR_FAULT 1. Perform DVES Reset:
at one second intervals) at:
a. (B5) MAINT Page 1 IBIT
• J1 Pin 11
b. (L4) STATUS Subpage
• J1 Pin 12
c. (L2) RESET DVES.
5. With system powered on and in the OPERATE
state with LIDAR Interlock ON: 2. Problem fixed? – Yes, Go to Step 4
a. Check that voltage on J1 pin 8 is at least 3. Replace lidar.
0.2 volts higher than voltage on J1 pin 7. 4. Turn system on. If no further fault messages
6. Were valid signal/voltages observed in both steps appear, the fault has been corrected
4 and 5?
• If Yes, replace IPU. Go to step 7
• If No, replace lidar. Go to step 7
7. Turn system on. If no further fault messages
appear, the fault has been corrected
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_LDR_RANGE_CAL_FAULT 1. Resolve all other faults first: DVE_DEGRADED DVE_NAV_FAULT 1. Verify EGIs are in NAV Mode.
(Cont) NOTE Range calibration cannot be performed in (Cont) 2. Perform DVES Reset:
the presence of other LiDAR or nav related a. (B5) MAINT Page 1 IBIT
faults. b. (L4) STATUS Subpage
2. The DVE LDR RANGE CAL FAULT is normal c. (L2) RESET DVES.
prior to the system entering OPERATE for the
3. Problem fixed? – Yes. Go to 5
first time after power cycling the LIDAR or IPU.
The fault is indicating that the next transition to 4. Connect bus anaylzer to commanded active EGI.
OPERATE will take longer than usual. After • Verify EGI-OUT-17-******-29 bit 01
transitioning to OPERATE and waiting 60 (standby) is not 1.
seconds the fault will clear. • Verify EGI-OUT-17-******-29 bit 02
3. Perform DVES Reset: (IMA) is not 1.
a. (B5) MAINT Page 1 IBIT • Verify EGI-OUT-17-******-29 bit 03
b. (L4) STATUS Subpage (Stored Heading Align) is not 1.
c. (L2) RESET DVES. • Verify EGI-OUT-17-******-29 bit 04
(GC Align) is not 1.
4. Problem fixed? Yes, go to step 6
• Verify EGI-OUT-17-******-29 bit 09
5. Go to “Troubleshooting DVE LDR FAULT”
(Overfly) is not 1.
6. Turn system on. If no further fault messages
• Verify EGI-OUT-17-******-29 bit 11
appear, the fault has been corrected
(Orient/Boresight) is not 1.
DVE MISSION_DB_DESYNC 1. Perform DVES Reset: • Verify EGI-OUT-17-******-29 bit 12
a. (B5) MAINT Page 1 IBIT (Attitude) is not 1.
b. (L4) STATUS Subpage • Verify EGI-OUT-17-******-29 bit 13
(Test) is not 1.
c. (L2) RESET DVES.
• Verify EGI-OUT-17-******-29 bit 8
2. Problem fixed? – No, Go to 4
(Navigate) is 1 or
3. Perform IBIT to confirm fault does not recur.
• EGI-OUT-17-******-29 bit 15 (NARF)
a. (B5) MAINT Page 1 IBIT is 1.
b. (L1) IBIT • Verify EGI-OUT-17-******-26 bits 4
4. Continue troubleshooting using the through 7 (Blended FOM) are greater
DVE_CHU_COM_FAULT troublshooting than 0 and less than or equal to 8.
procedure. a. All fields set correctly? Yes, Go to
DVE_EGI_COM_FAULT.
b. EGI is not in a compatible mode.
• Use aircraft/EGI TM to put EGI in a
compatible mode.
5. Turn system on. If no further fault messages
appear, the fault has been corrected.
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_PDU_COM_FAULT 1. Perform DVES Reset: DVE_DEGRADED DVE_PDU_POWER_LOSS 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) a. (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage b. (L4) STATUS Subpage
c. (L2) RESET DVES. c. (L2) RESET DVES.
2. Problem fixed? – Yes, Go to 5 2. Problem fixed? – Yes, Go to 7
3. Check the IPU Data Cable for damage and 3. Check the IPU Data Cable for damage and
continuity between: continuity between:
• P568 Pin 1 and P563 Pin 5 • P568 Pin 1 and P563 Pin 5
• P568 Pin 2 and P563 Pin 6 • P568 Pin 2 and P563 Pin 6
• P568 Pin 3 and P563 Pin 7 • P568 Pin 3 and P563 Pin 7
• P568 Pin 5 and P563 Pin 8 • P568 Pin 5 and P563 Pin 8
• P568 Pin 4 and P563 Pin 9 4. Check +28 VDC power on P567 of the IPU Power
d. Replace cable if damaged. Go to Step 5. Cable:
4. Check for valid signals on cable. • Pins A and B - +28VDC IN
• If Signal is good, replace PDU. Go to • Pins C and D - RTN
Step 5 5. If voltage is correct, replace IPU. Go to Step 6
• If Signal is not good, replace IPU. Go to 6. If voltage is not correct, Check +28 VDC power
Step 5 on J1 of the PDU:
5. Turn system on. If no further fault messages • Pins 1 and 2 - +28VDC IN
appear, the fault has been corrected • Pins 3 and 4 –RTN
d. If voltage is present, replace IPU Power
cable. Go to step 7
e. If voltage is not present, check DVES ON/
OFF signal on PDU P563 pin 1.
f. Signal present? Yes, replace the PDU Go to
Step 7
g. Signal not present, check signal on pin 8 of
CHU J1
h. Signal present? Yes, replace IPU Data
Cable. Go to step 7
i. Signal not present, replace CHU.
7. Turn system on. If no further fault messages
appear, the fault has been corrected.
DVE_REC_VID_FAULT 1. Perform DVES Reset:
a. (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage
c. (L2) RESET DVES.
2. Problem fixed? – Yes. Go to 6
3. Resolve any other faults.
4. Problem fixed? – Yes. Go to 6
5. Replace IPU
6. Turn system on. If no further fault messages
appear, the fault has been corrected
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_RMC0_NOT_KEYED 1. Perform DVES Reset: DVE_DEGRADED DVE_RSD_COM_FAULT 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) • BIT_FMP_RSD_LOSS_OF_CO a. (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage MM b. (L4) STATUS Subpage
c. (L2) RESET DVES. • BIT_FMP_TELNET_KEEPALI c. (L2) RESET DVES.
VE_FAIL
2. Problem fixed? – Yes. Go to 7 2. Problem fixed? – Yes, Go to Step 12
3. Perform procedure to load key onto RMC 3. Observe LED indicators on front of RSD. If they
4. Perform DVES Reset: are lit, go to Step 99
a. (B5) MAINT Page 1 IBIT 4. Check +28 VDC power on P560 of the RSD
b. (L4) STATUS Subpage Power Cable:
c. (L2) RESET DVES. • Pins 1 - +28VDC
5. Problem fixed? – Yes. Go to 7 • Pins 2 – RTN
6. Replace RSD/RMC 5. If voltage is correct, procede to step 9.
7. Turn system on. If no further fault messages 6. If voltage is not correct, Check +28 VDC power
appear, the fault has been corrected on PDU J4:
• Pins 1 - +28VDC
DVE_RMC0_UNMOUNTED 1. Remove RMC from RSD • Pins 2 - RTN
2. Reinstall RMC into RSD. 7. If voltage is not correct, replace PDU.
3. Perform IBIT to confirm fault does not recur. 8. If voltage is correct, replace RSD Power cable
a. (B5) MAINT Page 1 IBIT 9. Check the RSD Ethernet Cable for damage and
b. (L1) IBIT continuity between:
• P577 pin 12 and P573 pin 1
• P577 pin 7 and P573 pin 2
• P577 pin 19 and P573 pin 4
• P577 pin 16 and P573 pin 5
• P577 pin 17 and P573 pin 8
• P577 pin 18 and P573 pin 9
• P577 pin 8 and P573 pin 13
• P577 pin 13 and P573 pin 17
10. Check the RSD Ethernet Cable for damage and
continuity between:
• P578 pin 12 and P573 pin 18
• P578 pin 7 and P573 pin 19
• P578 pin 19 and P573 pin 15
• P578 pin 16 and P573 pin 16
• P578 pin 17 and P573 pin 11
• P578 pin 18 and P573 pin 12
• P578 pin 8 and P573 pin 3
• P577 pin 13 and P573 pin 7
11. Check for valid data signal on cable.
• If Signal is good, replace IPU.
• If Signal is not good, replace RSD
12. Turn system on. If no further fault messages
appear, the fault has been corrected
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_DEGRADED DVE_RSD_NO_RW_DRIVES 1. Perform DVES Reset: DVE_DEGRADED DVE_TIMEMARK2_FAULT 1. Perform DVES Reset:
(Cont) a. (B5) MAINT Page 1 IBIT (Cont) a. (B5) MAINT Page 1 IBIT
b. (L4) STATUS Subpage b. (L4) STATUS Subpage
c. (L2) RESET DVES. c. (L2) RESET DVES.
2. Problem fixed? – No, go to Step 4 2. Problem fixed? – Yes, go to step 5
3. Perform IBIT to confirm fault does not recur. 3. Check the DVES NAV/Bezel Data Cable for
a. (B5) MAINT Page 1 IBIT damage and continuity between:
b. (L1) IBIT • P583 pin 10 and P8225 pin 29
4. Continue troubleshooting using the • P583 pin 17 and P8225 pin 30
DVE_RSD_COM_FAULT troublshooting 4. Check for valid signal on P583 of cable.
procedure. • If Signal is good, replace IPU.
DVE_SWTCH_CONF_MODIFIED • If Signal is not good, replace EGI 2
1. Perform DVES Reset:
5. Perform IBIT to confirm fault does not recur.
OR a. (B5) MAINT Page 1 IBIT
a. (B5) MAINT Page 1 IBIT
DVE_SWTCH_CONF_READ_FAIL b. (L4) STATUS Subpage
b. (L1) IBIT
c. (L2) RESET DVES.
OR DVE_TIMESYNC_FAULT
2. Problem fixed? – Yes, go to Step 6 1. Verify both EGIs are in NAV mode. If Yes, go to
DVE_CONFIG_MODIFIED 3. Reload IPU software. step
4. Problem fixed? – Yes, go to Step 6 2. Place EGI in NAV mode IAW aircraft procedures.
5. Replace IPU 3. Perform DVES Reset:
6. Perform IBIT to confirm fault does not recur. a. (B5) MAINT Page 1 IBIT
a. (B5) MAINT Page 1 IBIT b. (L4) STATUS Subpage
b. (L1) IBIT c. (L2) RESET DVES.
DVE_TIMEMARK1_FAULT 4. Problem fixed? – NO
1. Perform DVES Reset:
5. Check the DVES NAV/Bezel Data Cable for
a. (B5) MAINT Page 1 IBIT damage and continuity between:
b. (L4) STATUS Subpage a. EGI 1
c. (L2) RESET DVES. • P583 pin 4 and P8201 pin 29
2. Problem fixed? – NO • P583 pin 5 and P8201 pin 30
3. Check the DVES NAV/Bezel Data Cable for b. EGI 2
damage and continuity between:
• P583 pin 10 and P8225 pin 29
• P583 pin 4 and P8201 pin 29
• P583 pin 17 and P8225 pin 30
• P583 pin 5 and P8201 pin 30
6. Check for valid signal on P583 of cable.
4. Check for valid signal on P583 of cable.
• If Signal is good, replace IPU.
• If Signal is good, replace IPU.
• If Signal is not good, replace EGI 1 or
• If Signal is not good, replace EGI 1 EGI 2 as indicated.
5. Perform IBIT to confirm fault does not recur. 7. Perform IBIT to confirm fault does not recur.
a. (B5) MAINT Page 1 IBIT a. (B5) MAINT Page 1 IBIT
b. (L1) IBIT b. (L1) IBIT
Table 7-21: DVES Troubleshooting Table (Continued) Table 7-21: DVES Troubleshooting Table (Continued)
WCA Message Fault Message Troubleshooting WCA Message Fault Message Troubleshooting
DVE_HOT DVE_IMU_HOT_FAULT 1. Allow IMU to cool. DVE_HOT (Cont) DVE_PDU_HOT_FAULT 1. Is PDU fan running? NO, go to step 7.
2. Perform DVES Reset: 2. Shut Down System. Wait ten minutes to allow the
a. (B5) MAINT Page 1 IBIT PDU to cool.
b. (L4) STATUS Subpage 3. Clean PDU fan.
c. (L2) RESET DVES. 4. Perform DVES Reset:
3. If any IMU faults occur, replace lidar assembly a. (B5) MAINT Page 1 IBIT
4. Turn system on. If no further fault messages b. (L4) STATUS Subpage
appear, the fault has been corrected. c. (L2) RESET DVES.
DVE_IPU_HOT_FAULT 5. If any PDU faults occur, go to Step 7.
1. Is IPU fan running? NO, go to step 8.
6. PDU experienced temporary Hot Fault condition.
2. Shut Down System. Wait ten minutes to allow the
Note: Use system as intended with caution that
IPU to cool.
conditions may exist to cause another hot
3. Clean IPU fan. fault.
4. Perform DVES Reset: 7. Replace PDU.
a. (B5) MAINT Page 1 IBIT 8. Turn system on. If no further fault messages
b. (L4) STATUS Subpage appear, the fault has been corrected
c. (L2) RESET DVES.
DVE_RSD_HOT_FAULT 1. Shut Down System. Wait ten minutes to allow the
5. If any IMU faults occur, go to Step 7
OR component to cool.
6. IPU experienced temporary Hot Fault condition.
2. Perform DVES Reset:
Note: Use system as intended with caution that DVE_VSE_HOT_FAULT
conditions may exist to cause another hot a. (B5) MAINT Page 1 IBIT
fault. b. (L4) STATUS Subpage
7. Replace IPU. c. (L2) RESET DVES.
8. Turn system on. If no further fault messages 3. If any faults occur, replace component.
appear, the fault has been corrected 4. Component experienced temporary Hot Fault
condition.
DVE_LDR_HOT_FAULT 1. Is lidar fan running? NO, go to step 7. Note: Use system as intended with caution that
2. Shut Down System. Wait ten minutes to allow the conditions may exist to cause another hot
lidar to cool. fault.
3. Clean lidar fan. 5. Turn system on. If no further fault messages
4. Perform DVES Reset: appear, the fault has been corrected
a. (B5) MAINT Page 1 IBIT DVE_OVERTEMP DVE_IPU_OVERTEMP_FAULT 1. Shut Down System. Wait ten minutes to allow the
b. (L4) STATUS Subpage
OR component to cool.
c. (L2) RESET DVES.
2. Perform DVES Reset:
5. If any lidar faults occur, replace lidar. DVE_LDR_OVERTEMP_FAULT
a. (B5) MAINT Page 1 IBIT
6. Lidar experienced temporary Overtemperature OR b. (L4) STATUS Subpage
condition.
DVE_PDU_OVERTEMP_FAULT c. (L2) RESET DVES.
Note: Use system as intended with caution that
conditions may exist to cause another over- OR 3. If any faults occur, replace component. Go to Step
temp fault. 5.
DVE_RSD_OVERTEMP_FAULT 4. If no faults, retain component in system.
7. Replace lidar.
8. Turn system on. If no further fault messages 5. Turn system on. If no further fault messages
appear, the fault has been corrected appear, the fault has been corrected
B
A
B C D E
D
V ENT CLR
PWR
→ACKNOW LEDG
E
HOME NAV MODE S CNTL MAINT WCA
E
H G F
AA CONTROL HEAD UNIT POWER DISTRIBUTION UNIT IMAGERY PROCESSING UNIT REMOVABLE STORAGE DEVICE
AAA WITH REMOVABLE MEMORY CARTRIDGE
CC
CCC F G H J
BB
BBB
AAA
J
DD
DDD
EE
EEE
G
G FF
GGGFF F
VIDEO SWITCH ELECTRONICS UNIT ALERT GENERATOR UNIT LIDAR ASSEMBLY INERTIAL MEASUREMENT UNIT
S1000D-649.5
MISSION
MISSION READINESS
READINESS
MISSION
MISSION
MISSION READINESS
READINESS
READINESS
CIRCUIT
CIRCUIT BREAKER
BREAKER PANEL
PANEL (CABIN)
(CABIN)
CIRCUIT
CIRCUIT
CIRCUIT BREAKER
BREAKER
BREAKER PANEL
PANEL
PANEL (CABIN)
(CABIN)
(CABIN)
28 VDC
PILOT
ETHERNET
VIDEO
PILOT
SERVO PILOT
FEEDBACK PILOT FLIR VIDEO DSGU/SGU FLIR
VIDEO
SEU DIGITAL SYMBOLOGY VIDEO VSE ESA
TFU INTERNAL
SYSTEM ELECTRONICS CO-PILOT FLIR VIDEO GENERATOR UNIT / VIDEO SWITCH ETHERNET SWITCH
TURRET/FLIR UNIT VIDEO
UNIT SYMBOLOGY GENERATOR CO-PILOT ELECTRONICS ASSEMBLY
ANALOG UNIT FLIR CO-PILOT
CTRL AIR DATA VIDEO
VIDEO
FORCE- 28VDC
STICK PILOT DVES VIDEO
MFCU DATA FLIR VIDEO CO-PILOT DVES VIDEO VSE CTRL/STAT SMFCD
MULTI-FUNCTION SCU BEZEL DATA
IPU BEZEL DATA
SMART MULTI-FUNCTION
CONTROL UNIT SYSTEM CONTROL UNIT IMAGE PROCESSING UNIT COLOR DISPLAY
IMU STAT/DATA BEZEL DATA
(FORCE-STICK) MODE (CO-PILOT)
CTRLS LDR CTRL/STAT SYS CTRL/STAT
28VDC
28VDC SMFCD SYSTEM
LDR PPS/INTLK PDU RSD CTRL/STAT
AN/AAQ-29A FLIR SYSTEM CTRL/STAT AIRCRAFT POWER
115 VAC
IMU LIDAR PDU 3 PHASE RSD
INERTIAL MEASUREMENT LIGHT DETECTION AND POWER DISTRIBUTION REMOVABLE STORAGE
CHU WoW AJU
CONTROL HEAD UNIT DATA AIRCRAFT JUNCTION UNIT
AIRCRAFT DVES UNIT RANGING UNIT DEVICE
LRU LRU
28VDC 28VDC
ALERT
28VDC PWR CTRL TRIGGER
PWR GOOD
28VDC
(D)ICS
AGU ALERT (DIGITAL)
ALERT GENERATOR UNIT AUDIO INTER-COMMUNICATIONS
SYSTEM
WCA NO . 1
DVE_SYS_FAIL
TROUBLE NO . 1
TROUBLE NO . 4
DVE_AC_MISMATCH _FAULT ARE THE IPU
APPLICATIONS READING DVE_IPU_PBIT _FAULT
CORRECTLY ?
YES NO
TROUBLE NO . 3
PERFORM PBIT
DOES THE IPU PIN IS VIDEO BEING DVE_IPU_FAULT
STRAPPING MATCH AC TYPE ? RENDERED ?
YES NO YES NO DID THE FAULT CLEAR ?
YES NO
PERFORM SYSTEM
RESET
REPLACE IPU TROUBLE NO . 2
CABLING
DVE_VIDEO_FROZEN
PERFORM SYSTEM RESET
DID THE FAULT CLEAR ?
YES NO
REPLACE IPU CABLING
DID THE FAULT CLEAR ?
YES NO
DID THE FAULT CLEAR ? PERFORM SYSTEM
RESET
YES NO
YES NO
REPLACE IPU
WCA NO . 1
DVE _SYS_FAIL
TROUBLE NO . 1
TROUBLE NO . 4
DVE _AC_MISMATCH _FAULT ARE THE IPU
APPLICATIONS READING DVE_IPU_PBIT _FAULT
CORRECTLY ?
YES NO
PERFORM SYSTEM RESET
TROUBLE NO . 3
PERFORM PBIT
DOES THE IPU PIN IS VIDEO BEING DVE _IPU_FAULT
STRAPPING MATCH AC TYPE ? RENDERED ?
YES NO YES NO DID THE FAULT CLEAR ?
YES NO
PERFORM SYSTEM
RESET
REPLACE IPU TROUBLE NO . 2
CABLING
DVE_VIDEO _FROZEN
PERFORM SYSTEM RESET
DID THE FAULT CLEAR ?
YES NO
REPLACE IPU CABLING
DID THE FAULT CLEAR ?
YES NO
DID THE FAULT CLEAR ? PERFORM SYSTEM
RESET
YES NO
YES NO
TO 1H-60(H)G-2-13
REPLACE IPU
WCA NO. 2
DVE_DEGRADED
YES NO
YES NO
YES NO