SmartCycle Troubleshooting1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

CUST-T-027-1

Smartcycle/Trendcheck Altair Avionics


Fault Lamp Troubleshooting

Smartcycle/Trendcheck Fault Lamp


Troubleshooting
Fault Lamp Isolation for the Smartcycle or
Trendcheck
NOTE: This Troubleshooting Flow is a job aid. This document does not replace the
Instruction For Continued Airworthiness (ICA) nor the Flight Manual Supplement
(FMS). Please reference the ICA or FMS for all troubleshooting requirements.

NOTE: Find your fault indication on the left column and then accomplish the
response to the right. If the response solves the problem, exit this checklist. If the
response has been previously accomplished/verified and the problem continues OR
not applicable, move to the next response.

NOTE: The following Lamp Status are defined in the Instruction for Continued
Airworthiness within Section 2.1.1.

CAUTION: Pressing the Fault Lamp, Resetting the Log, or entering Engine Run
Mode extinguishes the fault lamp but the fault may still be active. The fault is still
active if the fault lamp re-illuminates when the processor is placed in run mode with
the engine not running.

13 JUNE 2001
Change 1 – 4 August 2001
Page 1 of 4
CUST-T-027-1
Smartcycle/Trendcheck
Fault Lamp Troubleshooting
1. Determine the proper lamp indications to determine the sensors that are faulting.

LAMP INDICATIONS RESPONSES


LAMP FLASHING Accomplish Retrieve Log Data Checklist

Look for the following WARNINGS within the Log


File, if applicable.

a. Events Detected

b. Factory Reset

c. Low Log Warning

Go to Step 2.

LAMP SOLID Accomplish Retrieve Log Data Checklist

Look for the following faults within the Log File, if


applicable.

a. System FATAL Error

b. System ASSERT Error

c. Sensor Failures

d. Memory Full

e. Time Slice Overflow

Go to Step 2.

13 JUNE 2001
Change 1 – 4 August 2001
Page 2 of 4
CUST-T-027-1
Smartcycle/Trendcheck
Fault Lamp Troubleshooting

2. Determine the Type of Fault(s) for the applicable sensor(s).

INDICATIONS RESPONSES
Log Data displays all 9s for a sensor value Check Log Data for other failures and accomplish
this checklist for those failures.

NOTE: BIT Failures and Sensor Values of all 9s


shall always be accompanied by other faults.

System Error Go to Step 3.

Lamp Failure Accomplish the Cockpit Fault Lamp Display Test


in the System Troubleshooting Guide within the
Instructions for Continued Airworthiness.

Go to Step 3.

Unexpected Event Detected If the event actually occurred, accomplish


appropriate actions or directives, as required.

TIPS AND TRICKS: DO NOT assume that the If an event did not occur or is suspected of not
processor failed. An event was recorded occurring, verify the settings within the
because an actual event occurred OR the Configuration File.
event parameters are incorrect within the
configuration file. a. If the settings are not correct,

• Edit the Configuration File

• Accomplish the Download Configuration


File Checklist.

• Accomplish the Load Configuration File


into Processor Checklist.

• Accomplish the Calibration Checklist, if


required.

b. If the settings are correct, go to step 3.

13 JUNE 2001
Change 1 – 4 August 2001
Page 3 of 4
CUST-T-027-1
Smartcycle/Trendcheck
Fault Lamp Troubleshooting

INDICATIONS RESPONSE
Sensor Failure If the sensor had worked previously, start here

Range Failure Accomplish the System Troubleshooting Guide for


the applicable sensor in the Instructions for
Continued Airworthiness.

If the applicable sensor is not listed within the


System Troubleshooting Guide, go to “Fault Flow
Not In System Troubleshooting Guide” fault flow.

Go to Step 3.

If the sensor had not worked previously, start here

Verify that the sensor is properly installed. If the


sensor is not properly installed, exit this checklist
and properly install the sensor.

If the sensor is properly installed, Go to Step 3.

3. Contact Customer Support and have the following information available:

a. Processor Type

b. Processor Serial Number

c. Airframe and Engine Type

d. All indications and problem history

LESSONS LEARNED: It is VERY IMPORTANT to explain what was happening


and who was doing what when the indications were received.

e. Computer with the MLP program and associated MLP .hst files

f. Processor Log Files, if available

g. Live Data Files, if available

13 JUNE 2001
Change 1 – 4 August 2001
Page 4 of 4

You might also like