CUST-T-028-1

ADAS Troubleshooting Altair Avionics

ADAS Troubleshooting
Fault Isolation for the ADAS
NOTE: This Troubleshooting Flow only applies to the ADAS. This
Troubleshooting Flow does not apply to the ADAS+.

1. Accomplish the appropriate Troubleshooting Flow.

2. If the Troubleshooting Flow fixes the problem, exit this checklist.

3. If the Troubleshooting Flow does not fix the problem OR if the problem is
not addressed by the Troubleshooting Flow, contact the appropriate Help
Desk and have the following information readily available:

a. Customer Contact Information (Customer Name, Point of Contact,

Telephone Number, and Email Address)

b. Monitor Type (in this case, ADAS)

c. Monitor Serial Number

d. Airframe and Engine Type

e. Mode of Monitor (Normal, Warning, or Failure)

NOTE: The mode of the monitor can be determined by the Fault Lamp.
If the Fault Lamp is not present, the mode of the monitor can be
determined by accomplishing a MLU Status Command and noting the
System Error Condition listed.

f. All Indications and Problem History

18 JULY 2001
Change 4 – 19 November 2002
Page 1 of 7
CUST-T-028-1
ADAS Troubleshooting

g. Monitor Log (.log) Files, if available. Log Files contain the ADAS
data. They are found in c:\mlp\log directory unless the user saved
them in another location.

h. Monitor Live Data (.tab) Files, if available. Live Data files are
generated when View Live Data is accomplished. They are found in
c:\mlp\log\livedata unless the user saved them in another location.

i. Monitor Link Program (MLP) History (.hst) Files, if available. MLP

activity is recorded in the History Files. They are found in c:\mlp.

18 JULY 2001
Change 4 – 19 November 2002
Page 2 of 7
CUST-T-028-1
ADAS Troubleshooting
UNEXPECTED EVENT OR
EXPECTED EVENT Unexpected Event
or Non Event PURPOSE: To troubleshoot an event that was
recorded but not expected OR an event that was
expected but not recorded

Verify Applicable
Sensor Readings

Manual Trend
Calibration
(Accurate only if
Equipment (Most View Live Data
A the Aircraft is
Accurate (Accurate)
steady during
Verification)
Trend)

Event Occurred or Did

Readings OK? Yes Not Occur, as
applicable

NOTE: Sensor Calibrations apply to Analog Sensors

No
Only. Speed Sensors and Digital Discretes are not
calibrated

Analog Recalibrate
Yes
Sensor? Sensor

No

Verify Sensor Reading in

accordance with ADAS ICA 3.4.10
and 3.4.11, as applicable

18 JULY 2001
Change 4 – 19 November 2002
Page 3 of 7
CUST-T-028-1
ADAS Troubleshooting

SYSTEM BOOTUP
Apply Power to the
VERIFICATION ADAS

Lamp Should
Illuminate Solid for
3 to 5 seconds

Lamp should
System Bootup Process
extinguish

Lamp should Stay

Cycle Power to Extinguished,
ADAS Flash, or
Illuminate Solid

System Bootup
Yes Processor OK
Process Occur?

No

Fault Lamp
Change Bulb No
Bulb OK?

Yes

Contact Help Desk for

Return Material Authorization
(RMA) Number to return
Monitor

18 JULY 2001
Change 4 – 19 November 2002
Page 4 of 7
CUST-T-028-1
ADAS Troubleshooting

WARNING MODE
"Flashing Lamp"
Warning Mode
"Flashing Lamp"

NOTE: If you accomplish an Auto Detect and

a Trendcheck is detected, contact the Help
Desk for a Return Material Authorization
(RMA) Number to return Monitor

Retrieve Log Data

from Monitor

NOTE: If you are unable to

communicate with Monitor,
accomplish System Bootup
Troubleshooting

Analyze Log File

Event Detected Low Log Warning

(Memory is 85%
Full)

Problem Fixed by
Retrieving Data

18 JULY 2001
Change 4 – 19 November 2002
Page 5 of 7
CUST-T-028-1
ADAS Troubleshooting

FAILURE MODE
"Solid Lamp"
Failure Mode
"Solid Lamp"

NOTE: If you are unable to

communicate with Monitor,
accomplish System Bootup
Troubleshooting

Retrieve Log Data

from Monitor

Analyze Log File

System FATAL Error Memory Full

Sensor Failure
System ASSERT Error (Memory is 100%
"9999.9999"
Time Slice Overflow Error Full)

Problem Fixed by
Contact Help Desk Accomplish Sections 3.4.4
Retrieving Data
through 3.4.11, as appropriate,
in the ADAS ICA

18 JULY 2001
Change 4 – 19 November 2002
Page 6 of 7
 CUST-T-028-1
ADAS Troubleshooting

Lessons Learned
Where Problems Exist
! Monitor Itself ! Download Cable
" Failed System Bootup " Good Loopback Test
! Wiring from Monitor to Sensor " Unable to communicate with
" Bad sensor reading Monitor
" Bad resistance or voltage " Good resistance or voltage
measurements on wires measurements on Cockpit
Download Port wires
! Sensor itself " Different download cable works
" Bad sensor reading
! Laptop
" Good Resistance and Voltage
measurements on wires " Laptop Comm Port not
configured
! Cockpit Download Port " Software Program using Comm
" Bad Loopback Test Ports
" Unable to Communicate with ! Monitor Link Program (MLP)
Monitor
" Laptop Comm Port configured
" Bad resistance or voltage
measurements on Cockpit " No software programs using
Download Port Wires Comm Ports
" Different download cable doesn’t
work

18 JULY 2001
Change 4 – 19 November 2002
Page 7 of 7