Professional Documents
Culture Documents
A320 Family
Centralised Fault
Display System
Troubleshooting Guidelines
Guidelines for System Troubleshooting
_
A320 Family
GUIDELINES FOR TROUBLESHOOTING USING
CENTRALISED FAULT DISPLAY SYSTEM (CFDS)
Note:
•T
hese instructions do not amend or supersede any information contained in the Aircraft
Maintenance Manual (AMM).
•T
he AMM remains the main reference document.
•F
or additional information refer to: AMM 31-32-00.
Table of content
_
Glossary 005
CAPT Captain
CFDIU Central Fault Display Interface Unit
CFDS Central Fault Display System
COM Communication
CPU Central Processing Unit
Glossary
_
FMGC Flight Management and Guidance Computer
FWC Flight Warning Computer
FWS Flight Warning System
IDENT Identifier
ILS Instrument Landing System
INIT Initialisation
INOP Inoperative
NAV Navigation
REF Reference
SYS System
1. General
_
1.1. CFDS Architecture
The A320 Family maintenance concept is based on the use of the Centralised Fault Display
System (CFDS) and the Troubleshooting Manual (TSM).
The main purpose of the CFDS is to ease aircraft maintenance by compiling failure information
from system BITE (Built-In Test Equipment) and providing system BITE test capability from
the cockpit.
The CFDS is made of the Centralised Fault Display Interface Unit (CFDIU) which interfaces with:
• Built-In Test Equipment (BITE) of each connected Line Replaceable Unit (LRU)
• Multipurpose Control and Display Unit (MCDU)
• Multipurpose Disk Drive Unit (MDDU) or Portable Data Loader (PDL)
• Aircraft Communications Addressing and Reporting System (ACARS)
or Air Traffic Service Unit (ATSU)
• Printer
• Clock
GENERAL PARAMETERS
CFDIU (FWC1 OR FWC2, FAC1,
CLOCK, FDIU, DMC1, etc.)
MCDU 1 MCDU 2
OPTION
1. General
_
1.1. CFDS ARCHITECTURE
1. General
_
1.2. Component Location
The user interface items (MCDU and Printer) are located on the center pedestal in the cockpit.
CFDS filter data base loading is achieved with an MDDU or a PDL connector located on
the pedestal (117 VU Panel) or in overhead panel (52VU).
The CFDIU is located in the avionics bay.
Printer
TO MCDUs
AND PRINTER
A (80VU)
B (CFDIU)
TOUCH DOWN
5MN AFTER
POWER UP
< 80 KTS
LIFT OFF
1 2 3 4 5 6 7 8 9 10
POST FLIGHT
PREFLIGHT
APPROACH
TAKE OFF
TAXI OUT
LANDING
CRUISE
TAXI IN
CLIMB
Note:
•T
he CFDIU generates its flight/ground condition using some parameters transmitted by the
Flight Warning Computer (FWC), the Flight Augmentation Computer (FAC), the memorised
maintenance phases and a discrete signal from the Landing Gear Control and Interface Unit
(LGCIU).
• In normal operation, flight phase information is transmitted by the FWCs to the CFDIU and
when a new flight number is entered the information is given by the FAC.
• In downgraded mode, the discrete signal (nose landing gear shock absorber compressed)
from the LGCIU is used by the CFDIU as backup when the FWCs are inoperative.
2. Failure Classification & Indication
_
2.2. Failure Classification
FAILURE / FAULT
1 2 3
CLASSES
OPERATIONAL
CONSEQUENCES
YES NO NO
ON THE CURRENT
FLIGHT
YES
Automatically Displayed.
YES
INDICATION TO Warning or caution
Available on ECAM
messages on Engine NO
THE FLIGHT CREW status page.
Warning Display, local
Engines not running.
warning
Flag in the Flight Deck.
YES YES
INDICATION TO THE
Automatically printed out at the end of each flight: Available on request thru
MAINTENANCE TEAM Fault message on the CFDS Post Flight Report. System Report/Test.
The Class 1 failures are indicated to the pilots on Primary Flight Display (PFD) and/or
the Engine / Warning Display (E/WD).
LOCAL WARNINGS
LOCAL
indication
Note:
•O
nly the title of the warning or caution is reported in the CFDS “LAST LEG ECAM” report
(here “HYD B RSVR OVHT”).
•T
he ECAM action lines (here “BLUE ELEC PUMP OFF”) are not reported in the PFR.
•T
he aircraft configuration warning (ex: OVER SPEED VFE (VLE), L/G GEAR NOT DOWN,
CONFIG PARK BRK ON, etc.) are usually not reported in the PFR.
2. Failure Classification & Indication
_
2.4. What are the cockpit effects associated
with class 2 failures?
The cockpit effects associated to Class 2 failures are indicated to the cockpit crew on ground
by a maintenance status on the ECAM STATUS page after the engines shut down.
MAINTENANCE STATUS
MESSAGE ON THE “STATUS” PAGE
SYSTEMS IN WHICH
CLASS 2 FAILURES
ARE DETECTED
Note:
•O
nly the name of the affected system is reported in the “LAST LEG ECAM” report
(here “ADR3” and “EIVMU2”).
• “ STS” displayed on the Status Display means there is a Maintenance Status accessible by
pressing the “STS” button to call up the “STATUS” page.
Several types of reports are established by the CFDS in flight or on ground. On ground, all
the reports are available. In flight, only CURRENT LEG ECAM REPORT and CURRENT LEG
REPORT are available.
• LAST (CURRENT) LEG ECAM REPORT:
ECAM Warnings / Caution messages seen by the crew during the last (current) flight leg.
• LAST (CURRENT) LEG REPORT:
Failures recorded during the last flight (current) leg.
• PREVIOUS LEGS REPORT:
Equivalent to LAST LEG REPORT but accessible for the last 64 flights.
• AVIONICS STATUS:
List in real time of the systems affected by at least one internal or external failure
(Class 1,2 or 3).
• POST FLIGHT REPORT:
Sum of the LAST LEG ECAM REPORT and LAST LEG REPORT.
Note:
•A
fter a flight when the aircraft is on ground, the CURRENT LEG (ECAM) REPORT is renamed
LAST LEG REPORT and stored in the PREVIOUS LEGS REPORT by the CFDS.
•C
lass 1 and 2 failures are displayed in the LAST (or CURRENT) LEG REPORT,
LAST (or CURRENT) LEG ECAM REPORT and the POST FLIGHT REPORT.
•A
VIONICS STATUS displays on ground and in real-time the name of the systems affected
by failures of any class.
3. Access to CFDS Reports
_
3.2. How to access the different CFDS reports?
Pressing the “MCDU MENU” key and then selecting CFDS gives access to CFDS menu page
(ground or flight). All CFDS reports are accessible on ground.
MCDU MENU
<FMGC
<ACARS
<AIDS
<CFDS
RETURN>
SELECT DESIRED SYSTEM
CFDS
<LAST LEG REPORT
<LAST LEG ECAM REPORT
<PREVIOUS LEG REPORT
NORMAL OPERATION
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*
NEXT PAGE
CFDS
ITEM ONLY DISPLAYED <GMT/DATE INIT
IN CASE OF CLOCK FAULT
<AVIONICS CONFIGURATION REPORT
<REPORTS PROGRAMMING
<PFR FILTER PROGRAMM
<PASSWORD CHANGE
The SYSTEM REPORT/TEST function is available on the ground only. It enables an interactive
dialogue between the CFDS and one particular system.
Pressing the line key adjacent to a system name enables access to the menu of the system,
generally made up of below items (Systems of Type 1):
• LAST LEG REPORT
• PREVIOUS LEGS REPORT
• LRU IDENTIFICATION
For some systems, the following optional functions may be available:
• TROUBLE SHOOTING DATA (TSD)
• CLASS 3 FAULTS
• TEST
• GROUND SCANNING
MCDU MENU
<FMGC
<ACARS
<AIDS
<CFDS
RETURN>
SELECT DESIRED SYSTEM
CFDS
<LAST LEG REPORT
<LAST LEG ECAM REPORT
<PREVIOUS LEG REPORT
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*
The LAST (OR CURRENT) LEG REPORT displays the failures (Class 1 and 2 only) detected by
the system BITE during the last flight leg. The CFDS can store up to 40 failures over this period.
Pressing the line key adjacent to an item, the SOURCE/IDENTIFIERS page comes in to view.
This page provides for a given failure its “Source” and the “Identifiers”.
CFDS MENU
• Concerns all systems connected to CFDS
TIME AT WHICH THE CFDS
RECEIVES THE FAULT but only for faults recorded from phase 02
to 09 for type 1 and 3 systems and 05 to 07
LAST LEG REPORT FEB 23 for type 2 systems.
Phases ground faults avail “GND scanning”
<GMT1245 PH04 ATA362200 system report.
CHECK R WING LOOP A
<GMT1302 PH06 ATA282100 •D isplays “Class1” and “Class2” failures
FUEL L TK PUMP 1QM
<GMT1315 PH06 ATA220000 received by CDFS during last flight leg.
FMGC 1
<GMT1317 PH06 ATA261200
ENG1 LOOP A FAULT
<GMT1317 PH06 ATA220000
ATS DISCONNECT
<RETURN PRINT*
<RETURN PRINT*
The LAST (OR CURRENT) LEG ECAM REPORT displays the warning messages sent
to the CFDIU by the Flight Warning System (FWS) flight leg. The CFDS can store up
to 40 warnings over the last flight leg.
CFDS MENU
TIME WHEN THE CFDS
RECEIVES THE FAULT
<RETURN PRINT*
<RETURN PRINT*
ONE PRINT ACTION CAUSES PRINTING
OF TOTAL REPORT
3. Access to CFDS Reports
_
3.6. What is the previous legs report?
At each new flight the content of the LAST LEG REPORT is transferred into the PREVIOUS
LEGS REPORT. The CFDS can store up to 200 failures over the last 64 flight legs.
The PREVIOUS LEGS REPORT is displayed only on ground. It displays the failure message
history.
CFDS MENU
AIRCRAFT IDENT
<RETURN PRINT*
The AVIONICS STATUS displays the name of systems currently affected by a failure regardless
of the classification. This function is only available on ground and in real-time. The information
presented is permanently updated but not stored.
CFDS MENU
AVIONICS STATUS
NO GPCU DAIA
ADF1 (CLASS 3)
FMGC
VHF
AIDS
<RETURN PRINT*
<RETURN PRINT*
3. Access to CFDS Reports
_
3.8. What is the post flight report?
The PFR is available on ground to present Warnings/Maintenance status and failure messages
(Class 1 and 2) of the last flight leg. The PFR is only available on the printer after a flight or on
the ground via ACARS by using manual or automatic transmission.
CFDS
MAINTENANCE
POST FLIGHT REPORT DATE AT THE TIME
OF THE FLIGHT
0656: A/C ID DATE GMT FLTN CITY PAIR
1 ENG START + 3MN F-WWJH 01JAN 0656/0700 ITAF9877 LFPG LFMN
OR 80 KTS IF NEW FLIGHT
NUMBER NOT ENTERED
WARNING/MAINT. STATUS MESSAGES
0700: GMT PH ATA FAULT MESSAGE
A/C SPEED < 80 KTS ON TWO LINES MAXI
1353 05 30-31 ANTI ICE F/O TAT
+ 150 SEC(30 SEC
for CFDIU Std 8 or lower)
FAILURE MESSAGES
GMT PH ATA SOURCE IDENT. LIST OF SOURCE AND
IDENTIFIERS (SYSTEM
0657 06 23-24-34 AAA GPSSU 1 SOURCE ON TOP LIST)
0657 06 31-38-22 NO MDDU DATA CFDS
Note:
•T
he PFR displays both LAST LEG ECAM REPORT and LAST LEG REPORT in one single
report.
•T
he logbook is the first entry point for troubleshooting. Associated to the logbook, the PFR
is the means to input the TSM.
The purpose of the correlation is to define the fault symptoms from Logbook entries, and input
the relevant TSM tasks required to isolate and fix the faults reported by the crew.
The fault symptom is the result of a manual warning/failure correlation: it consists in associating
each cockpit effect (logbook entries) to the relevant failure message(s) (PFR or result of
the system BITE test).
CFDS
CORRELATED WARNING
ASSOCIATED TO THE FAULT
“CHECK R WING LOOP A”
<GMT1245 PH04 ATA 362200 > <GMT1245 PH04 ATA 3622 >
CHECK R WING LOOP A BLEED LOOP
Note:
The correlation information is available on the MCDU only, not in the printed PFR.
4. PFR Correlation Principle
_
4.3. How to correlate the different messages
given by the PFR?
| MAINTENANCE | DB/N
| POST FLIGHT REPORT | XXXXXXXXXXXXXXX
GMT PH ATA
1511 04 36-21 AIR ENG1 BLEED FAULT
1527 06 34-00 NAV ADR3 FAULT
1527 06 27-00 F/CTL
1744 06 32-00 WHEEL TYRE LO PR (2)
FAILURE MESSAGES
The first step is to select one Warning / Maintenance Status message as an entry point,
and then to identify the associated failure message(s) or Identifier(s).
The exercise is to repeat until either all Warning / Maintenance Status are correlated
or no correlation is possible.
•C
ase 1: Correlation between Warning / Maintenance Status and failure messages
The selection of items is achieved according to the two following criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first two digits) of messages.
Demonstration: Red, Green and Blue scheme.
•C
ase 2: Correlation between Warning / Maintenance Status and Identifiers
The selection of items is achieved according to the two following criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first two digits) of the Identifier..
Demonstration: Black scheme.
•C
ase 3: No Correlation
For those items (failure or warning) not correlated, they are input individually in the TSM.
5. Utilisation of the PFR
and AirN@v Maintenance
for Troubleshooting
5.1. How to start with Trouble Shooting?
5.2. How to retrieve a TSM Task in AIRN@V from PFR data?
5.3. How to use the TSM for fault confirmation and isolation?
A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 034
After a malfunction, the crew reports the cockpit effect in the Log Book. Once correlated,
the Log book and the PFR provide the fault symptoms relative to the cockpit effect which can
be as follows:
• A cockpit effect (ECAM/Engine/EFIS/Local Warning or Maintenance status
or Crew/Maintenance observation) alone
• A cockpit effect correlated with a failure message
• A failure message alone
POST FLIGHT
LOGBOOK REPORT (PFR)
GMT PH ATA
1411 02 24-00 ELEC BCL 1 FAULT
FAILURE MESSAGES
In order to find the troubleshooting task (fault confirmation and isolation) corresponding to each
fault symptom, AirNav offers a dynamic trouble shooting tool.
The path for it is: “AirNav Maintenance/Home page/Advanced tools/Start troubleshooting”.
5. Utilisation of the PFR and AirN@v
Maintenance for Troubleshooting
_
5.2. How to retrieve a TSM Task in AIRN@V from PFR data?
To find out the reported problem (“ELEC BCL 1 FAULT” in this example), you have to select
“ECAM Warning” (or Maintenance Status for Class 2 failures) and enter the name of the fault
message reported on the logbook.
You can also enter the ATA chapter to have a list of warnings/malfunctions, and then you select
the related fault message.
GMT PH ATA
1411 02 24-00 ELEC BCL 1 FAULT
FAILURE MESSAGES
A cockpit effect correlated with a failure message can lead to several trouble shooting tasks.
Therefore, it is necessary to select the failure message data relevant to the ones given in
the PFR for the same message.
Once the selection of the fault symptom is completed, AirN@v provides access to the relevant
TSM task.
GMT PH ATA
1411 02 24-00 ELEC BCL 1 FAULT
FAILURE MESSAGES
LAST LEG
REPORT
SYSTEM/
REPORT TEST
GROUND
SCANNING
TROUBLE
SHOOTING
DATA
Note:
•S
ome spurious fault messages can affect a PFR.
•S
purious messages can be deleted from the PFR. For that, a customised filter must be
created, uploaded and then activated through the CFDS menu.
6. Additional means to optimise PFR data
_
6.2. Customised Maintenance Filter
ENVELOPE FILTER
FILENVXX.320
MFT
CFDIU
Printer
PDL or
CUSTOMISED MAINTENANCE MDDU
FILTER DATABASE
The customisation of the maintenance filter is achieved from envelop filter delivered
with SIL 00-028 and using Maintenance Filter Tool (MFT) available through SIL 00-088.
The loading of the customised maintenance filter is performed using a PDL or the MDDU.
Note:
•T
he filtering function is effective on the PFR only (no effect on the memorised faults
in the system BITE).
•T
he version of the filter database number loaded into the CFDIU is checked up with
the CFDIU LRU IDENTIFICATION function (Data base number: DB/N) or with an automatic
printing of the Filter content.
The TFU describes in-service issues affecting a system and its maintenance. It is produced
whenever the resolution is ongoing or not. It provides advanced information, until the technical
solution is finalised.
Notes
_
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
Notes
_
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
������������������������������������������������������������������������������������������������������������
AIRBUS S.A.S. 31707 Blagnac Cedex, France
© AIRBUS S.A.S. 2017 - All rights reserved, Airbus, its
logo and the product names are registered trademarks.
Concept design by Airbus Multi Media Support 20172315.
Photos by Airbus: P. Masclet.
Printed in France by Airbus Print Centre.