A318/A319/A320/A321 Airbus: Indicating/Recording Systems 31
A318/A319/A320/A321 Airbus: Indicating/Recording Systems 31
A318/A319/A320/A321 _(non-enhanced-technology)
Differences to non-enhanced-technology Revision: 1JAN2010
ATA 31
Author: PoL
For Training Purposes Only
E LTT 2007
Indicating/Recording Systems
A318-21E_31B_L3/D-NEN
Training Manual
www.Lufthansa-Technical-Training.com
Revision Identification:
S The date given in the column ”Revision” on the face of S Dates and author’s ID, which may be given at the base S The LTT production process ensures that the Training
this cover is binding for the complete Training Manual. of the individual pages, are for information about the Manual contains a complete set of all necessary pages
latest revision of that page(s) only. in the latest finalized revision.
Lufthansa Technical Training
INDICATING/RECORDING SYSTEMS A318/A319/A320/A321
GENERAL
31−00
BITE
The BITE (Built In Test Equipment) is a function incorporated in the computers
which detects, localizes and memorizes failures.
All systems including a BITE are connected to the CFDIU.
ECAM
The ECAM monitors the aircraft systems. The warning information is delivered
to the Centralized Fault Display System.
FWC (Flight Warning Computer).
Only the primary and the independent failure information is sent to the CFDS.
MCDU
The MCDU (Multipurpose Control and Display Unit) is a display unit and a
keyboard used by the CFDS to display and interrogate BITE‘s and to initiate
FOR TRAINING PURPOSES ONLY!
system tests.
The 2nd MCDU is also connected to the CFDS.
You can only use the CFDS on one MCDU at a time.
PRINTER
The PRINTER is used for printing information automatically or on request.
CENTRALIZED FAULT
DISPLAY INTERFACE
UNIT (CFDIU)
FLIGHT
WARNING
COMPUTER
(FWC 1 & 2)
AIR TRAFFIC
FOR TRAINING PURPOSES ONLY!
SERVICE UNIT
(ATSU)
MEMORIZATION
Memorization of failures is different when the aircraft is on ground or in flight.
The full BITE functions and memorization operate in flight.
On ground, the memorization is done only in the BITEs. The BITEs are
provided with flight and ground memory zones.
CFDIU
The CFDIU centralizes all information concerning aircraft system failures.
Reading or printing of all the failure information is done in the cockpit.
The CFDS (Centralized Fault Display System = CFDIU + BITEs) functions are
accessed through the MCDUs.
CFDS MODES
Two CFDS modes are available: NORMAL and MENU modes. The MENU
MODE is available only on ground.
NORMAL MODE
In this mode, the CFDIU scans all the connected system outputs and
FOR TRAINING PURPOSES ONLY!
MENU MODE
In this mode, the CFDIU dialogues with one computer at a time in order to read
the contents of its BITE memory and to initiate various tests. This mode can
only be selected on ground and interrupts the normal mode of operation.
0832/1001
Type 2 Systems
Type 2 Systems memorize only failures from the last flight leg.
The discrete signal is provided to initiate the test of the system.
Example: AEVC (Avionics Equipment Ventilation Computer)
MCDU IN FLIGHT
FOR TRAINING PURPOSES ONLY!
MCDU IN FLIGHT
FOR TRAINING PURPOSES ONLY!
MAINTENANCE
CIDS 1
Indication after
Engine Shut down
MCDU ON GROUND
FOR TRAINING PURPOSES ONLY!
Twelve line select keys, six on the left and six on the right, give access
to a page or a function.
The line select keys permit access to a page or a function when these
symbols appear (>, <, *).
They are identified as 1L to 6L on the left, and 1R to 6R on the right.
->
< LAST LEG REPORT
CFDS ->
< CURRENT LEG REPORT
< CURRENT LEG ECAM REPORT
FOR TRAINING PURPOSES ONLY!
S TEST
S GROUND SCANNING and many more.
CLASS 3 faults
This item presents class 3 failure messages concerning this system that
appeared during previous flights. These failure messages contain the name of
the equipment affected by a class 3 fault associated with the time, the date, the
flight number and the ATA reference.
TEST
This item initiates system tests and shows the test results on the MCDU. The
CFDIU transmits the code of the line key (TEST) to the system. The system
BITE executes its test and may display a wait message to the CFDIU when the
test lasts for a long time. At the end of the test, the BITE transmits the test
results to the CFDIU for display.
GROUND SCANNING
This item presents the internal and external failures concerning this system and
which are present when the request is made (on ground only). This report is
FOR TRAINING PURPOSES ONLY!
established by forcing the operation of the BITE in system normal mode (same
BITE operation as in flight).
A/C ID DATE GMT FLTN CITY PAIR A/C ID DATE GMT FLTN CITY PAIR
D-AIRB 28MAY 18:00 LH021 EDDH EDDF D-AIRB 28MAY 18:00 LH021 EDDH EDDF
+−−−−−−−−−−−−−−−−−−−−+ +−−−−−−−−−−−−−−−−−−−−+
! MAINTENANCE ! DB/N ! MAINTENANCE !
! POST FLIGHT REPORT ! A320FAM03 ! POST FLIGHT REPORT !
+−−−−−−−−−−−−−−−−−−−−+ +−−−−−−−−−−−−−−−−−−−−+
A/C ID DATE GMT FLTN CITY PAIR A/C ID DATE GMT FLTN CITY PAIR
D-AIRB 28MAY 16:20 LH021 EDDH EDDF D-AIRB 28MAY 16:20 LH021 EDDH EDDF
1649 06 34−41−11 WXR ANTENNA (11SQ) RADAR 1 1649 06 34−41−11 WXR ANTENNA (11SQ) RADAR 1
1702 06 36−11−34 BMC 1 BMC 1 1702 06 36−11−34 BMC 1 BMC 1
1713 06 22−83−34 AFS:FMGC1 AFS 1713 06 22−83−34 AFS:FMGC1 AFS
Version 1 Version 2
12 34
FOR TRAINING PURPOSES ONLY!
Figure 23 PFR Filter Program − Filter Activated & Print Filter Content
FRA US/T-5 PoL Mar 8, 2010 19|PFR Filter|L3 Page 47
Lufthansa Technical Training
INDICATING/RECORDING SYSTEMS A318/A319/A320/A321
CENTRALIZED FAULT DISPLAY
INTERFACE (CFDIU) 31−32
DB/N
A320FAM03
FOR TRAINING PURPOSES ONLY!
Figure 26 Examples
FRA US/T-5 PoL Mar 8, 2010 22|Filter Example|L3 Page 53
Lufthansa Technical Training
INDICATING/RECORDING SYSTEMS A318/A319/A320/A321
CENTRALIZED FAULT DISPLAY
INTERFACE (CFDIU) 31−32
STEP 1 STEP 2
STEP 3 STEP 4
SYSTEM REPORT SYSTEM REPORT
TEST TEST
< ADR 1 IR 1 > < FADEC 1B
FOR TRAINING PURPOSES ONLY!
CFDS CFDS
ENTER >
< RETURN < RETURN
FLIGHT/GROUND TRANSITION
Transition to ground occurs when, after touch down, the aircraft speed has
been below 80 knots for 30 seconds. At this time, the CURRENT LEG
REPORT is renamed under the title LAST LEG REPORT and is stored in the
PREVIOUS LEGS REPORT.
NOTE: As the leg has not changed, the content of the LAST LEG
REPORT is identified in the PREVIOUS LEGS REPORT under
the LEG −00.
TYPE 2 SYSTEMS
FOR TRAINING PURPOSES ONLY!
TYPE 1 SYSTEMS
CFDIU FUNCTIONS
MAIN FUNCTIONS INTERFACES
Memory Clock
The CFDIU stores the failure messages and the ECAM warning messages in a The CFDIU permanently receives the GMT (UTC) and the date from the
non volatile memory. aircraft clock and then sends these two parameters to all type 1 systems.
The GMT and date are used by the system BITE’s as well as the CFDIU for
Management
the various maintenance reports.
The CFDIU manages failure information and adds data such as GMT, DATE,
LEG, FLIGHT PHASE to elaborate reports. FAC (Flight Augmentation Computer)
The CFDIU receives the flight number and city pair from the FAC.
Correlation
The city pair (FROM/TO airports) is sent to the MU (Management Unit) of the
If a computer internal failure is detected, the CFDIU achieves a correlation
ACARS (Aircraft Communication Addressing and Reporting System) and to the
function that means it isolates or ignores the malfunctions of systems relating
DMU (Data Management Unit) of the AIDS (Aircraft Integrated Data System).
to this failure.
Example: ”ADC FAILURE” causes ”NO DATA FROM ADC” in other FDIU (Flight Data Interface Unit, part of Flight Recorder System)
computers. The CFDIU receives the aircraft identification from the Flight Data Interface
The CFDS will present only the initial failure in the last leg report. Unit and sends this parameter to all type 1 systems.
The function ”IDENT” will then present the systems affected by this failure. The CFDIU is used as an interface between the FDIU and the FWC (Flight
Warning Computer) to send some FDIU class 2 failures to the FWC in order to
Monitoring constitute the maintenance status.
The CFDIU scans permanently all input buses in order to detect a transmitted
failure message. FWC (Flight Warning Computer, part of ECAM)
The CFDIU detects intermittent operation of the systems and adds (INTM) to The CFDIU receives the flight phases and ECAM warnings from the FWC.
the failure message. The ECAM warnings are used by the CFDIU to generate the LAST or
CURRENT LEG ECAM REPORT.
Detection
Only PRIMARY failures, INDEPENDENT failures and CLASS 2 failure
FOR TRAINING PURPOSES ONLY!
The CFDIU can detect the nature of the failure by reading the ARINC words. messages (Maintenance status) are received.
Nature of failures:
DMU (Data Management Unit, part of AIDS)
S Internal Example: ”SDAC FAULT”
The CFDIU is used as an interface between the DMU and the FWC to send
S External Example: ”FWC1: NO DATA FROM ADIRU1”
some DMU class 2 failures.
S Intermittent (INTM) added
DMU class 2 failures are used for the maintenance status on the ECAM.
S Class 3 ( CLASS 3) added
S Messages requiring more investigation with the help of the trouble−shooting
manual Example: ”CHECK EIU 1”
CLASS 2 FLIGHT
FAILURES PHASES
ECAM
WARNINGS
FOR TRAINING PURPOSES ONLY!
ABNORMAL OPERATION
Clock Back Up
If the aircraft clock fails, the CFDIU takes over and its internal clock sends
GMT (UTC) and DATE on the output bus to all type 1 systems.
Upon power−on after A/C clock failure, the item ”GMT/DATE INIT” is added to
the CFDS Menu.
This option enables GMT and date initialization.
FOR TRAINING PURPOSES ONLY!
CLASS 2 FLIGHT
FAILURES PHASES
ECAM
WARNINGS
FOR TRAINING PURPOSES ONLY!
Monitoring and associated message are identical to the case of the LAST LEG
S CFDIU I/0 ARINC 1 (or 2 or 3) for fault of multiplexor 1, 2 or 3 REPORT.
S CFDIU I/0 DISCRETE 1 (or 2) for fault of discrete inputs/outputs 1 or 2 NOTE: This manually activated monitoring does not entail acquisition of
S CFDIU BITE MEMORY for fault in NVM monitored parameters by the CFDIU.
S CFDIU for any other fault of the channel
< RETURN
CFDS
LRU IDENTIFICATION
FOR TRAINING PURPOSES ONLY!
P/N: B401ACM507
If there is no filter,
DB/N: A320FAM03 „A320FAM03“ is replaced by „SPACE“
MCDU 1 3CA 1
MCDU 2 3CA 2
PRINTER
FOR TRAINING PURPOSES ONLY!
STA977/FR24A
STA808/FR20
PFR
For the class 1 and 2 failures of CFDS monitored systems, the PFR (Post
Flight Report) permits an access to the concerned list of faults in Airn@v. For
this purpose, it gives the following information: ECAM (Electronic Centralized
Aircraft Monitoring) WARNING message (if it exists), FAULT message with its
SOURCE, ATA reference and IDENTIFIERS list.
When the PFR print is not available, this information can be retrieved through
the MCDU (in Normal mode or Menu mode). SIL (Service Information Letter)
00−028, made of ”spurious maintenance messages”, and the maintenance
knowledge let the airlines create a specific data base to filter the messages to
be displayed on the PFR.
Once loaded into the CFDIU (Centralized Fault Display Interface Unit), this
maintenance filter data base can be activated through the MCDU.
FOR TRAINING PURPOSES ONLY!
1440/16
34
FOR TRAINING PURPOSES ONLY!
101 TD
POWR SPLY
FROM DLRB
103PP
103XP-B 28VDC
115 VAC BUS1
BUS1
FOR TRAINING PURPOSES ONLY!
102 TD
1 TD
DMC: DISPLAY MANAGEMENT COMPUTER FMGC: FLIGHT MANAGEMENT & GUIDANCE COMPUTER
FDIMU: FLIGHT DATA INTERFACE MANAGEMENT UNIT (DMU + FDIU) TCAS: TRAFFIC ALERT AND COLLISION AVOIDANCE SYSTEM
DMU: DATA MANAGEMENT UNIT ATSU: AIR TRAFFIC SERVICE UNIT
FDIU: FLIGHT DATA INTERFACE UNIT CFDIU: CENTRALIZED FAULT DISPLAY INTERFACE UNIT
data loader, the TRANSFer IN PROGress message is displayed and the data
Other messages shown on the MDDU window tell the operator of the transfer
is transferred to the computer.
status:
NOTE: The disk should not be extracted while TRANSF IN PROG message is
S TRANSFER FAILURE: If the MDDU has to stop data transfer (up or down
shown as damage to the disk could result.
loading) for any reason, this message is shown.
When the data transfer is terminated and no anomalies are detected, the
S UNIT FAIL: The MDDU shows this message if a hardware (H/W) failure is
TRANSF COMPLETE message is shown to inform the operator that the
detected during the self−test. In this case, the MDDU stops all operations.
transfer is successfully completed.
S DISK ERROR: If the MDDU cannot read or write data on the disk (incorrect
If more than one disk for the up loading is necessary , the EJECT DISK and
formatting, write−protected, disk damaged, etc), it will interrupt the
INSERT NEXT DISK message are displayed one after the other on the MDDU
operations and send this message.
when the next disk needs to be inserted. This disk must contain a configuration
E-LOGBOOK (OPTION)
GENERAL
The eLogbook is the main communication means for aircraft operational staff. It
enables the flight crew and the technical staff to be aware of the aircraft status,
to enter aircraft defect and to report maintenance and servicing actions.
The eLogbook lets the flight crew:
S consult the Logbook status,
S accept / create a new flight,
S report aircraft defects,
S hand over to maintenance.
The maintenance staff uses the eLogbook to:
S consult the aircraft status,
S report aircraft defects,
S report corrective or scheduled maintenance actions,
S report servicing actions,
S build the Certificate of Release into Service (CRS) of the aircraft.
Finally the cabin crew can also use the eLogbook to:
S consult the aircraft status,
S inform the flight crew about regulatory cabin defects,
S report none regulatory cabin defects.
The eLogbook runs on a fully stand−alone laptop and is not connected to the
aircraft. The eLogbook is stowed in the cockpit by the flight crew.
FOR TRAINING PURPOSES ONLY!
TABLE OF CONTENTS
ATA 31 INDICATING/RECORDING SYSTEMS 1 TROUBLE SHOOTING PROCEDURE WITH CFDS . . . 68
TROUBLE SHOOTING PROCESS . . . . . . . . . . . . . . . . . . 70
31−32 CENTRALIZED FAULT DISPLAY INTERFACE (CFDIU) 2 31−38 UP AND DOWN DATA LOADING SYSTEM . . . . . . . . . . 78
CFDS PRESENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . 78
SYSTEM BITE PHILOSOPHY . . . . . . . . . . . . . . . . . . . . . . 4 UP & DOWN DATA LOADING SYSTEM INTERFACES 80
SYSTEM BITE PHILOSOPHY CONTINUED . . . . . . . . . 6 UP & DOWN DATA LOADING SYSTEM UTILIZATION 82
SYSTEM BITE PHILOSOPHY . . . . . . . . . . . . . . . . . . . . . . 8
31−00 INDICATING/RECORDING SYSTEMS - GENERAL . . . 84
CFDS MODES PRESENTATION . . . . . . . . . . . . . . . . . . . . 8
AIRMAN (OPTIONAL) PRESENTATION . . . . . . . . . . . . . 84
SYSTEM BITE TYPES INTERFACE . . . . . . . . . . . . . . . . . 10
E-LOGBOOK (OPTION) . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
CLASS 1 FAILURE PRESENTATION . . . . . . . . . . . . . . . . 12
CLASS 2 FAILURE PRESENTATION . . . . . . . . . . . . . . . . 14
CLASS 3 FAILURE PRESENTATION . . . . . . . . . . . . . . . . 16
SYNTHESIS SYSTEM DESCRIPTION AND FAILURE
CLASSES OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MULTIPURPOSE CONTROL AND DISPLAY
UNIT DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CFDS REPORTS TROUBLESHOOTING . . . . . . . . . . . . 22
CFDS REPORTS (AV STS) TROUBLESHOOTING . . . . 30
CFDS REPORTS (SYS REP/TEST) PRESENTATION . 32
CFDS REPORTS (MENU TYPES) PRESENTATION . . 34
CFDS REPORTS (PFR) INTRODUCTION . . . . . . . . . . . 40
GMT/DATE INITIALIZATION OPERATION . . . . . . . . . . . 42
ACARS/ PRINT PROGRAM OPERATION . . . . . . . . . . . . 44
CFDS PFR FILTER PROGRAM-MAINTENANCE
PRACTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
PFR FILTERING FUNCTION MAINTENANCE
PRACTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
PFR FUNCTION (INDICATION) OPERATION . . . . . . . . 50
POST FLIGHT REPORT FILTERING FUNCTION
(EXAMPLE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
BACKUP MODE (OPTION) OPERATION . . . . . . . . . . . . 54
PASSWORD CHANGE (OPTION) OPERATION . . . . . . 56
CFDS PHASES FUNCTIONAL OPERATION . . . . . . . . . 58
CFDIU FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CFDIU TEST MENU PRESENTATION . . . . . . . . . . . . . . 64
CFDS COMPONENT LOCATION . . . . . . . . . . . . . . . . . . . 66
Page i
A318-21_31-32_L3
TABLE OF CONTENTS
Page ii
A318-21_31-32_L3
TABLE OF FIGURES
Figure 1 CFDS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Figure 36 Trouble Shooting Process − AIRN@V Entry . . . . . . . . . . . . . . 71
Figure 2 BITE Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 37 Trouble Shooting Process − ECAM Warning Selection . . . . . 73
Figure 3 Reports Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 38 Trouble Shooting Process − Correlation . . . . . . . . . . . . . . . . . . 75
Figure 4 Internal/External Failures & Failure Gravity . . . . . . . . . . . . . . . . 9 Figure 39 Fault Isolation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 5 System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 40 Data Loading Component Location . . . . . . . . . . . . . . . . . . . . . . 79
Figure 6 Class 1 Failure Indication and Annunciation . . . . . . . . . . . . . . . 13 Figure 41 Up Loading & Down Loading Interfaces . . . . . . . . . . . . . . . . . . 81
Figure 7 Class 2 Failure Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Figure 42 Data Loading System Operation . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 8 Class 3 Failure Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Figure 43 Airman Overview (Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 9 Failure Classification Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Figure 44 e-Logbook (OPTION) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 10 MCDU LCD & CRT Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 11 CFDS Menus on Ground and in Flight . . . . . . . . . . . . . . . . . . . 23
Figure 12 Last Leg Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 13 Last Leg ECAM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 14 Previous Legs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 15 Avionics Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 16 System Report/Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 17 System Report/Test - BSCU SYS1 (Type 1 System) . . . . . . . 35
Figure 18 System Report/Test−AEVC (Type 2 System) . . . . . . . . . . . . . 37
Figure 19 System Report/Test−GCU EMER (Type 3 System) . . . . . . . . 39
Figure 20 Post Flight Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 21 GMT/Date Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 22 ACARS/Print Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 23 PFR Filter Program − Filter Activated & Print Filter Content 47
Figure 24 Purpose & Filter Data Base Customization and Loading . . . 49
Figure 25 Filter Data Base Identification . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 26 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 27 Backup Mode (OPTION) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 28 PASSWORD SETTINGS (OPTION) . . . . . . . . . . . . . . . . . . . . 57
Figure 29 Ground/Flight Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 30 CFDIU Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 31 CFDIU Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 32 CFDS System Report/Test Menu . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 33 Components Location (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 34 Components Location (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 35 Cockpit Effect & PFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Page i
A318-21_31-32_L3
TABLE OF FIGURES
Page ii
A318-21_31-32_L3
TABLE OF FIGURES
Page iii
A318-21_31-32_L3
TABLE OF FIGURES
Page iv