ATA 31-32 Indicating & Recording

Training Manual
A 319/320/321
ATA 31
Indicating/Recording
31-32 Centralized Fault Display System
Line & Base Maintenance
ATA Spec. 104 Level 3
Lufthansa Issue: JAN. 1998

Technical Training GmbH For Training Purposes Only
Book No: All A319/320/321 31-32 LEVEL 3 E Lufthansa Base  Lufthansa 1995
For training purposes and internal use only.
Copyright by Lufthansa Technical Training GmbH.
All rights reserved. No parts of this training
manual may be sold or reproduced in any form
without permission of:
Lufthansa Technical Training GmbH
Lufthansa Base Frankfurt

D-60546 Frankfurt/Main
Tel. +49 69 / 696 41 78
Fax +49 69 / 696 63 84
Lufthansa Base Hamburg

Weg beim Jäger 193
D-22335 Hamburg
Tel. +49 40 / 5070 24 13
Fax +49 40 / 5070 47 46
TABLE OF CONTENTS
ATA 31 INDICATING AND RECORDING . . . . . . . . 1
31-32 CENTRALIZED FAULT DISPLAY SYSTEM (CFDS) . . . . . . 1
CFDS PRESENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
SYSTEM BITE PHILOSOPHY . . . . . . . . . . . . . . . . . . . . . . . 4
CFDS MODES OF OPERATION . . . . . . . . . . . . . . . . . . . . . 10
SYSTEM TYPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FAILURES CLASSIFICATION . . . . . . . . . . . . . . . . . . . . . . . 14
MCDU DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
CFDS REPORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
GMT/DATE INITIALIZATION . . . . . . . . . . . . . . . . . . . . . . . . 38
ACARS/ PRINT PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . 40
BACKUP MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
CFDS FLIGHT PHASES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
CFDIU FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
PFR FILTER PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DATA LOADING SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Page: i
TABLE OF FIGURES
Figure 1 CFDS Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2 System BITE Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3 Post Flight Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 4 Internal/External Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 5 Memorization/Failure Gravity . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 6 System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 7 Class 1 Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 10 Failure Classification Synthesis . . . . . . . . . . . . . . . . . . . . 21
Figure 11 MCDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 12 CFDS Menu on Ground . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 13 Last Leg Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 14 Last Leg ECAM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 15 Previous Legs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 16 Avionics Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 17 System Report/ Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 18 Post Flight Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 19 GMT/ Date Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 20 ACARS/Print Programm . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 21 Backup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 22 Flight Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 23 CFDIU Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 24 CFDIU Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 25 Components Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 26 PFR Filter-Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 27 CFDS Menu (new) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 28 PFR Messages Filter Activation . . . . . . . . . . . . . . . . . . . . 55
Figure 29 Data Base Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 30 Non filtered PFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 31 Print of a Filter Data Base . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 32 Filtered PFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 33 Data Loading System Locations . . . . . . . . . . . . . . . . . . . . 61
Figure 34 Data Loading System Schematic . . . . . . . . . . . . . . . . . . . 62
Page: ii
Lufthansa Technical Training
INDICATING AND RECORDING A319/A320/A321
CENTRALIZED FAULT DISPLAY SYSTEM
31-30
ATA 31 INDICATING AND RECORDING

31-32 CENTRALIZED FAULT DISPLAY
SYSTEM (CFDS)
For Training Purposes Only
FRA US/T WD 03.09.99 Page: 1

31-30
PRINTER
CFDS PRESENTATION The PRINTER is used for printing information automatically or on request.
CFDIU ACARS
The Centralized Fault Display Interface Unit (CFDIU) receives failure mes- The ACARS (Aircraft Communication Addressing and Reporting System) is
sages from the aircraft systems. used to exchange data between the aircraft and a ground station via a radio
It memorizes and manages them. Information is available in various reports. VHF link.
The CFDIU consists of two distinct channels:
S a NORMAL CHANNEL which ensures all the functions.
S a STANDBY CHANNEL (or BACKUP CHANNEL) which permits restricted
operation when the normal channel is faulty.
BITE
The BITE is a function incorporated in the computers which detects, localizes
and memorizes failures.
All systems including a Built in Test Equipment (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 Multipurpose Control and Display Unit (MCDU) is a display unit and a key-
board used by the CFDS to display and interrogate BITE‘s and to initiate sys-
tem tests.
The 2nd MCDU is also connected to the CFDS.

You can only use the CFDS on one MCDU at a time.
FRA TS84, wd 7.12.93 Seite: Page: 2

31-30
AIRCRAFT
ECAM SYSTEM
ACARS COMPUTERS
D.U.
FWC CFDIU
1 2
MCDU MCDU
1 2
PRINTER
Figure 1 CFDS Presentation
31-30
SYSTEM BITE PHILOSOPHY

BITE
Most aircraft systems are equipped with a Built-In Test Equipment (BITE).
The BITE monitors permanently the system operation. It can also store and
transmit the detected failure.
Each system computer includes a BITE circuit which detects failures.
When a failure is detected, it is stored in the BITE memory and is transmitted
to the centralized fault display system.
Memorization of the 64 previous legs report is done by most of the BITE‘s.
CFDS
The Centralized Fault Display System centralizes all information concerning
aircraft system failures.
Reading or printing of all the failure information is done in the cockpit.
The CFDS functions are accessed through the MCDU.

31-30
AIRCRAFT SYSTEM
COMPUTER
ECAM
BITE
memory
BITE ECAM WARNING

INFORMATION MESSAGES
CFDIU
Centralized Fault
Display Interface Unit
MCDU
=- =-
=- CFDS =-
=- =-
=- =-
=- =-
Multipurpose
=-=-=-=-=-
=-=-=-=-=-=-
=-=-
=-=- .....
Control and
.....
.....
.....
.....
Display
.....
Unit PRINTER
Figure 2 System BITE Philosophy
31-30
SYSTEM BITE PHILOSOPHY (CONT.)
LAST LEG REPORT
A CURRENT LEG REPORT is elaborated during the flight.
After the flight, its title becomes LAST LEG REPORT.
All failures are reported in the same form and also indicate ATA reference and
time of failure occurence.
Example of failure message:
GMT ATA
0920 28-21-00 FUEL L TK PUMP 1QM
Time ATA Failure Message FIN (Functional
Reference Item Number)
LAST LEG ECAM REPORT
The primary failure and the independent failure messages are delivered by the
ECAM to the CFDIU.
Warning messages coming from the ECAM are stored in the CURRENT LEG
ECAM REPORT during the flight.
After the flight, the title of this report becomes LAST LEG ECAM REPORT.
Example of warning message:
GMT: 1125 PH: 06 ATA: 3155
HYD BLUE RSVR OVHT
POST FLIGHT REPORT (PFR)

The POST FLIGHT REPORT is the sum of the LAST LEG REPORT and of the
LAST LEG ECAM REPORT.
The POST FLIGHT REPORT can only be printed on ground.
The list of ECAM WARNINGS and FAULT MESSAGES with the associated
time and ATA reference allow the maintenance crew to make a correlation for
easier trouble-shooting.

31-30
LAST LEG REPORT LAST LEG ECAM REPORT
A/C
IDENT DATE GMT FLTN CITY PAIR
F-WWAI FEB23 2350 280 LFBO/LFPO
MAINTENANCE
POST FLIGHT REPORT
ECAM WARNINGS
GMT PH ATA
1125 06 31-55 HYD BLUE RSVR OVHT
1100 06 27-00 SFCC 1 FAULT
0920 05 28-21 FUEL L TK PUMP 1 LO PR
0904 04 36-22 BLEED LOOP
0854 04 22-00 LAND 3 INOP
FAULT MESSAGES
GMT ATA
1125 31-55-00 HYD BLUE TEMP SENSOR
1105 26-17-00 SDCU CHANNEL 1 10WQ
1100 27-00-00 NO SFCC 1 DATA
0920 28-21-00 FUEL L TK PUMP (1QM)
0915 26-12-00 CHECK EIU 1
0904 36-22-00 CHECK R WING LOOP A
0854 22-00-00 FMGC 1
Standard for Example DLH Version
Figure 3 Post Flight Report

31-30
SYSTEM BITE PHILOSOPHY CONT.)
Internal/External Failures
Each Built-In Test Equipment (BITE) can make the difference between an in-
ternal and an external failure.
Let us suppose that an angle of attack sensor failure has been detected and
that systems A, B and C are affected by this failure.
The AIR DATA system will transmit an INTERNAL FAILURE (= SOURCE on
the POST FLIGHT REPORT).
Systems A, B and C will transmit EXTERNAL FAILURE (= IDENTIFIERS on
the POST FLIGHT REPORT).

31-30
AIR DATA SYSTEM
C
ANGLE OF ATTACK
SENSOR
B
AIR DATA
COMPUTER
A
INTERNAL
EXTERNAL FAILURE
FAILURE
CFDIU
Figure 4 Internal/External Failures

31-30
SYSTEM BITE PHILOSOPHY (CONT.) CFDS MODES OF OPERATION
Memorization Two CFDS modes are available. NORMAL MODE is always active except on
Memorization of failures is different when the aircraft is on ground or in flight. ground when MENU MODE is selected.
The full BITE functions and memorization operate in flight. S NORMAL MODE
On ground, the memorization is done only in the BITE‘s. In this mode, the CFDIU scans all the connected system outputs and mem-
The BITE‘s are provided with flight and ground memory zones. orizes the failure messages in order to generate the current (last) leg report
and the current (last) leg ECAM report.
Failure Gravity
In flight the CFDS always operates in normal mode.
The failures are classified according to their importance.
S MENU MODE
Class 1 failures are the most serious ones and require an immediate mainte-
In this mode, the CFDIU dialogues with one computer at a time in order to
nance action subject to the minimum equipment list.
read the contents of its BITE memory and initiate various tests (SYSTEM
Class 2 failures may have consequences if a second failure occurs. REPORT/TEST).
A maintenance action is necessary at the next adequate opportunity. This mode can only be selected on ground and interrupts the normal mode
Class 3 failures can be left uncorrected until the next scheduled maintenance of operation.
check.

31-30
MEMORIZATION FAILURE GRAVITY
CLASS 1
BITE
GROUND FLIGHT
MEMORY MEMORY CLASS 2
OPERATIONAL
CONSEQUENCE
CLASS 3
NO IMMEDIATE
OPERATIONAL
CONSEQUENCE
NO CONSEQUENCE
ON AIRCRAFT SAFETY
Figure 5 Memorization/Failure Gravity

31-30
SYSTEM TYPES Type 3 Systems

Type 3 Systems are simple systems linked to the CFDS by only two discrete
Type 1 Systems signals.
Most Systems are type 1 systems. These systems can memorize failures oc- Type 3 systems cannot memorize failure messages.
cured in the last 64 flight legs. The discrete input permits to initiate the test or reset.
Type 1 systems are connected to the Centralized Fault Display Interface Unit The discrete output indicates if the system is OK or not.
(CFDIU) via an ARINC 429 input bus and an ARINC 429 output bus. Example: Transformer Rectifier Unit (TRU)
S SINGLE COMPUTER
The first configuration in TYPE 1 is a single computer.
Example: VHF 1 Transceiver
S MULTI COMPUTER
The second configuration in TYPE 1 includes several computers in the
same aircraft system.
One computer concentrates the maintenance data of the other computers.
Example: Flight Management and Guidance Computers (FMGC) and Flight
Augmentation Computer (FAC) with
FMGC1 as A
FMGC2 as B
FAC as C
S DUPLICATED SYSTEM
A duplicated system includes two different subsystems in the same com-
puter.
Example: Air Data and Inertial Reference Unit (ADIRU) with
ADR as subsystem 1
IR as subsystem 2
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: Avionic Electronic Ventilation Computer (AEVC)

31-30
TYPE 1 SYSTEMS
B
SINGLE I
COMPUTER T
E
TYPE 2 SYSTEM
B
I
B T
A I
T C E
E S
Y
MULTI C
S
T B
F
COMPUTER E I
SYSTEM M T D
E
B I TYPE 3 SYSTEM
B I
T U
E
B
I
T
E
SUB B
SYSTEM I
T
DUPLICATED 1 E
SYSTEM
SUB B
SYSTEM I
T
2 E
Figure 6 System Types

31-30
FAILURES CLASSIFICATION
Class 1 Failure
Class 1 failures have an operational consequence on the flight.
You can display the class 1 failures on the Multipurpose Control and Display
Unit (MCDU):
S In the LAST (or CURRENT) LEG REPORT
S In the LAST (or CURRENT) LEG ECAM REPORT.
Refer to the Minimum Equipment List (MMEL): ”GO, ”GO IF” or ”NO GO”.

31-30
ELEC PUMP
MASTER FAULT A
U
CAUT T
OFF O
HYD B RSVR OVHT

-BLUE ELEC PUMP..OFF CURRENT LEG REPORT
date:feb 23
STS
GMT:1125 ATA:31-55-00
HYD BLUE TEMP SENSOR
3000 PSI 3000 PSI 3000

< RETURN PRINT *

OVHT
Figure 7 Class 1 Failure

31-30
FAILURES CLASSIFICATION (CONT.)
Class 2 Failure
Class 2 failures have no immediate operational consequence and can be dis-
played on request on the ECAM STATUS page.
You can display the class 2 failures on the Multipurpose Control and Display
Unit (MCDU):
S In the LAST (or CURRENT) LEG REPORT
S In the LAST (or CURRENT) LEG ECAM REPORT.
Refer to the MMEL: ”GO” without condition.
Example: Single smoke detector fault in Smoke Detection Control Unit (SDCU).

31-30
CURRENT LEG REPORT

date:feb 23
GMT:1105 ATA:26-17-00
STATUS SDCU CHANNEL 1(10WQ)
MAINTENANCE
< RETURN PRINT *
SDCU

31-30
Class 3 Failure
Class 3 failures have no operational consequence.
All aircraft systems remain available.
You can display the name of the systems affected by at least a class 3 failure
in the AVIONICS STATUS.
The Class 3 failures can be left uncorrected until the next scheduled mainte-
nance check. (At least before 400 hours or a A check).
Do not refer to the MMEL.

31-30
AVIONICS STATUS
DMC 3 (CLASS 3)
STATUS
NORMAL
< RETURN PRINT *

31-30
Synthesis
NOTE:
AVIONICS STATUS displays on ground the title of the systems currently af-
fected by any failure class.
Class 1 and 2 failures are displayed in the LAST LEG REPORT and in the

31-30
CLASS 1 CLASS 2 CLASS 3

FAILURE FAILURE FAILURE
Operational
consequence on
the current YES NO NO
flight
YES YES
Indicated to Warnings/ flags On the system NO
the pilots System pages Display ”STATUS”
page.
REFER TO MMEL FUNCTIONS LOST

Dispatch may be: INDICATED IN MMEL NO REFERENCE
consequences ”GO” ”GO IF” ”GO” without IN MMEL
”NO GO” condition
Have to be reported by the Available on

request. Can be
pilots in the log book. left uncorrected

Maintenance Are indicated at the end of
information each flight leg. until the next
MMEL entry is required. scheduled main-
tenance check.
Figure 10 Failure Classification Synthesis

31-30
MCDU DESCRIPTION
The brightness knob enables the brightness of the display to be adjusted.
By pressing the MCDU menu key, the MCDU menu page is displayed, and
any one of the systems connected to the MCDU can be selected.
The green colour indicates the system already in dialogue with the MCDU.
The other systems are displayed in white.
A multiple page display is indicated by an arrow in the right upper corner of
the screen. In this case the NEXT PAGE key must be used to give access
to the various pages of the display.
The NEXT PAGE key can be used as long as the arrow is displayed.
Some displays contain too many data for a single page.
In this instances, vertical scroll keys can be used to scroll display, up or
down.
The scroll keys can be used as long as these arrows are displayed.
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.
The MCDU menu annunciator illuminates white when a system connected
to the MCDU request the display.

The CRT contains 14 lines, each having 24 characters.
The top line is used as title line and the bottom one, is the scratchpad.
Two character size can be used, as well as various colours: white, cyan,
green, amber.
Various symbols <, >, *, →, ↑, ↓ can be displayed to indicate special
functions.

31-30
Figure 11 MCDU
31-30
CFDS REPORTS
General
On ground, all the functions are available.
In flight, only CURRENT LEG REPORT and CURRENT LEG ECAM REPORT
are available.
Note that the CFDS menu comprises two pages on ground.

31-30
< PFR FILTER PROGRAM
Figure 12 CFDS Menu on Ground

31-30
CFDS REPORTS (CONT.)
LAST LEG REPORT
The LAST LEG REPORT displays failure information delivered by the BITE‘s of
the aircraft systems.
It can store up to 20 failures occured during the last leg.
Pressing the SFCC channel 1 (4L) line key allows access to the corresponding
IDENTIFIERS page.
The Last Leg Report displays the internal failures (class 1 and 2) only.
On the ground, the title of this item is ”LAST LEG REPORT”. In the flight, it is
”CURRENT LEG REPORT”.
When the report is displayed on several pages, an arrow appears on the top
right-hand corner. The NEXT PAGE key permits to see the following pages.
If you select the NEXT PAGE key on the last page, you come back to the first
page.
When you select the PRINT line key, all the LAST LEG REPORT is printed,
even if it contains several pages.

31-30
Figure 13 Last Leg Report

31-30
LAST LEG ECAM REPORT
The LAST LEG ECAM REPORT displays the list of ECAM warning messages
sent to the CFDIU by the flight warning computers.
It can store up to 20 warnings occured during the last leg.
On ground, the title of this item is ”LAST LEG ECAM REPORT”, in flight it is
”CURRENT LEG ECAM REPORT”.
DOCUMENTARY DATA appears on the print report:
S the A/C identification
S the city pair
S the flight number
S date and GMT (UTC).
All the report is printed.

31-30
Figure 14 Last Leg ECAM Report

31-30
PREVIOUS LEGS REPORT
At each new flight leg, the content of the LAST LEG REPORT is transferred
into the PREVIOUS LEGS REPORT.
This report can store up to 200 failures over the last 63 flight legs.
Each failure message contains the same data as the LAST LEG REPORT:
i.e.: NO FAC 1 DATA
FEB 22 13 12
22-00-00
It also contains a flight leg counter relative to the previous flight.
-XX is the number of flight legs before the last flight leg:
i.e.: -01 (previous leg).
The PREVIOUS LEGS REPORT is displayed only on ground.
(INTM) means that the failure has occurred intermittently.
When you make a print of the PREVIOUS LEGS REPORT, only the displayed
page is printed.

31-30
Figure 15 Previous Legs Report

31-30
AVIONICS STATUS
The AVIONICS STATUS presents the list of systems which are currently af-
fected by a failure.
This function is only available on ground.
The information presented is permanently updated.
The message contains the name of the systems presently affected by a failure,
i.e. VHF 3, or a NO X DATA message when the related system X bus is not
active, i.e. NO ILS 2 DATA.
The AVIONICS STATUS also indicates the class 3 failures.
(Class 3 ) means that the system is affected by at least one class 3 failure.
Note that there could also be class 1 or 2 failures.
When you make a print, all the AVIONICS STATUS report is printed even if it
contains several pages.

31-30
Figure 16 Avionics Status

31-30
CFDS REPORTS (CONT.) AEVC, Avionics Equipment Ventilation Computer (Type 2 system)
Type 2 systems present a menu with one basic function, the LAST LEG RE-
SYSTEM REPORT/TEST
PORT and optional functions depending on the system.
General You are in PSEUDO-MENU mode.
The SYSTEM REPORT/TEST function is available on the ground only. The menu is transmitted by the CFDIU.
It enables a dialogue between the CFDS and one system computer. You don‘t talk directly to the system.
The SYSTEM REPORT/TEST menu presents the list of all the systems con- The system permanently transmits its data on the system bus, and the CFDIU
nected to the Centralized Fault Display Interface Unit, in ATA chapter order. reads them, except for the test.
The menu includes one basic function:
An example for each system type is available:
S the LAST LEG REPORT
S in INST for type 1 systems and optional functions depending on the system, for example here
S in AIR COND for type 2 systems S TEST
S in ELEC for type 3 systems S CLASS 3 FAULTS
ECAM 1 (Type 1 system) GCU EMER, Generator Control Unit Emergency (Type 3 system)
Type 1 systems are the most common systems. Type 3 systems present only one function on their menu.
The menu they present depends on the system itself. Type 3 systems have no MENU mode.
The available functions are displayed by the CFDIU.
Now, you are in MENU mode. The menu is transmitted by the system itself.
You talk directly with the system. The only possible functions are TEST or RESET.
The menu includes three basic functions: When you make a test or a reset, the CFDIU initiates the test or reset, and
reads the result on the CFDIU discrete for MCDU display..
S the LAST LEG REPORT
S the PREVIOUS LEGS REPORT
S the LRU IDENTIFICATION
and optional functions, depending on the system, for example here
S TROUBLE SHOOTING DATA
S CLASS 3 FAULTS
S TEST
S GROUND SCANNING

31-30
SYSTEM REPORT/TEST MENU

Figure 17 System Report/ Test

31-30
POST FLIGHT REPORT (PFR)
The POST FLIGHT REPORT is the sum of the LAST LEG REPORT and of the
It is only available on the printer.
S ECAM WARNINGS (or ECAM WARNING MESSAGES) display the LAST
LEG ECAM REPORT.
S FAULT MESSAGES (or FAILURE MESSAGES) display the LAST LEG RE-
PORT.
You can send this report to the ACARS.

31-30
Standard for Example DLH Version

Figure 18 Post Flight Report
31-30
GMT/DATE INITIALIZATION
The GMT/DATE INITialization function is available only in case of clock failure
plus CFDIU power interrupt.
The Centralized Fault Display System permits to reinitialize the time and the
date on the multipupose control and display unit.
GMT (UTC) and date are entered using the scratchpad.

31-30
TO ALL OTHER
A/C SYSTEMS
Figure 19 GMT/ Date Initialization

31-30
ACARS/ PRINT PROGRAM The AVIONICS DATA function enables to send and/or print system pages
available in the SYSTEM REPORT/TEST item.
An ACARS/PRINT PROGRAM function is available. The printing or/and sending is not automatic; you must select the print line key
It enables programming of the CFDS reports transmission to the ACARS and displayed in the system page.
to the printer NOTE: In the system pages, the PRINT message cannot be modified.
The functions written in green are delivered by the ACARS or the CFDIU. But when you print and send the system pages, the ”PRINT ALSO SEND”
They cannot be modified by the flight crew. message appears in the scratchpad.
The functions written in blue can be changed manually. Functions delivered by the ACARS:
If you select one of these functions, you will switch the YES message to NO When the CFDIU has not received any programming from the ACARS, the
and vice versa. YES or NO message is replaced by a blank.
The REAL TIME FAILURES provide, in real time, all the internal failure mes-
sages delivered by the systems or created by the CFDIU (CURRENT LEG RE-
PORT DATA).
When the associated SEND is on YES, this data is automatically transmitted to
the ACARS, in real time.
The REAL TIME WARNINGS function provides, in real time, warning mes-
sages, sent by the Flight Warning Computers (CURRENT LEG ECAM RE-
PORT DATA).
When the associated SEND is on YES, the report is automatically transmitted
in real time, to the ACARS.
The POST FLIGHT REPORT is the sum of the LAST LEG REPORT and of
the LAST LEG ECAM REPORT.
When the associated SEND is on YES, the POST FLIGHT REPORT will be
automatically transmitted to the ACARS at the end of the flight (transition from
flight phase 9 to 10).
The PRINT function associated to
S the POST FLIGHT REPORT
S the REAL TIME FAILURES
S the REAL TIME WARNINGS

permits an automatic print of the report.
The POST FLIGHT REPORT will be printed automatically at transition from
flight phase 9 to 10 (Second engine shutdown).
Upon power on, the last selected programmed functions are still present.
At the initialization, the manual programming functions present the last configu-
ration in vigor.

31-30
10
Figure 20 ACARS/Print Programm

31-30
BACKUP MODE
The BACKUP MODE function is only displayed in case of CFDIU main channel
failure.
It enables access to the functions of the backup channel.
In flight, no function is available.
On ground, the only function possible is SYSTEM REPORT/ TEST.
This function is available for the main systems only.

31-30
Figure 21 Backup Mode

31-30
CFDS FLIGHT PHASES E- After fist engine start (+ 3 minutes) and before 80 kts
At engine start (after 3 minutes), the contents of the last leg report is stored in
A- In flight and before touchdown the previous legs report. The leg number is then incremented.
In flight, the full BITE functions are operative. S Type 1 systems store internal failures in their flight memory (External fail-
Transmission and storage of internal and external failures for type 1/2/3 sys- ures not stored).
tems in their flight memory. S Type 2 systems store internal failures in their ground memory (still on
B- Between touchdown and 80 kts + 30 seconds ground).
This phase differs from the previous one because type 2 systems are now ”on NOTE: Transfer of the LAST LEG REPORT into the PREVIOUS LEGS RE-
ground” and store only internal failures in their ground memory while type 1 and PORT is done at engine start, both inthe CFDS and in type 1 systems.
3 systems are still considered ”in flight”. F- After 80 kts and before lift-off
C- Between 80 kts + 30 seconds and 5 minutes after engine shutdown After 80 knots, type 1 systems receive a signal from the CFDIU and then store
In this phase, the storage of failures is done in the ground memory for all the all internal and external failures in the flight memory.
systems. S Type 1 systems store internal and external failures in their flight memory.
S Storage of internal failures of all systems in their ground memory. S Type 2 systems store internal failures in their ground memory (still on
S All CFDS functions are available. ground).
D- Between 5 minutes after engine shutdown and first engine start G- After lift-off and in flight
Note that when the aircraft power supply is turned on, the CFDS starts in this The fault memories in type 2 systems are erased at each ground/flight transi-
phase. tion.
Information of the last flight is always there because stored in non-volatile S Transmission and storage for internal and external failure for type 1/2/3 sys-
memory. tems in their flight memory.
S Storage of internal failures of all systems in their ground memory.
S All CFDS functions are available on request.
S Transmission of last flight failures for type 2 systems, even after electrical
power restart.

31-30
CFDS
FLIGHT GROUND FLIGHT
LEG X LEG X+1
5 MIN
FLIGHT AFTER FLIGHT
2 ND 1 ST
TOUCH 80KTS ENG ENG TAKE-
DOWN +30S. SHUTDOWN START 80 KTS OFF
A B C D E F G
FLIGHT MENU GROUND MENU
Figure 22 Flight Phases

31-30
CFDIU FUNCTIONS INTERFACES

Clock
MAIN FUNCTIONS
The CFDIU permanently receives the GMT (UTC) and the date from the air-
Memory craft clock and then sends these two parameters to all type 1 systems.
The CFDIU stores the failure messages and the ECAM warning messages in a The GMT and date are used by the system BITE’s as well as the CFDIU for
non volatile memory. the various maintenance reports.
Management FAC (Flight Augmentation Computer)

The CFDIU manages failure information and adds data such as GMT, DATE, The CFDIU receives the flight number and city pair from the FAC.
LEG, FLIGHT PHASE to elaborate reports. The city pair (FROM/TO airports) is sent to the Management Unit (MU) of the
Aircraft Communication Addressing and Reporting System (ACARS) and to the
Correlation Data Management Unit (DMU) of the AIDS (Aircraft Integrated Data System).
If a computer internal failure is detected, the CFDIU achieves a correlation
function that means it isolates or ignores the malfunctions of systems relating FDIU (Flight Data Interface Unit, part of Flight Recorder System)
to this failure. The CFDIU receives the aircraft identification from the Flight Data Interface
Example: ”ADC FAILURE” causes ”NO DATA FROM ADC” in other computers. Unit and sends this parameter to all type 1 systems.
The CFDIU is used as an interface between the FDIU and the FWC (Flight
The CFDS will present only the initial failure in the last leg report. Warning Computer) to send some FDIU class 2 failures to the FWC in order to
The function ”IDENT” will then present the systems affected by this failure. constitute the maintenance status.
Monitoring FWC (Flight Warning Computer, part of ECAM)
The CFDIU scans permanently all input buses in order to detect a transmitted The CFDIU receives the flight phases and ECAM warnings from the FWC.
failure message. The ECAM warnings are used by the CFDIU to generate the LAST or CUR-
The CFDIU detects intermittent operation of the systems and adds (INTM) to RENT LEG ECAM REPORT.
the failure message. Only PRIMARY failures, INDEPENDENT failures and CLASS 2 failure mes-
sages (Maintenance status) are received.
Detection
The CFDIU can detect the nature of the failure by reading the ARINC words. DMU (Data Management Unit, part of AIDS)
Nature of failures: The CFDIU is used as an interface between the DMU and the FWC to send
S Internal Example: ”SDAC FAULT” some DMU class 2 failures.

S External Example: ”FWC1: NO DATA FROM ADIRU1” DMU class 2 failures are used for the maintenance status on the ECAM.
S Intermittent (INTM) added
S Class 3 (CLASS 3) added
S Messages requiring more investigation with the help of the trouble-shooting
manual Example: ”CHECK EIU 1”

31-30
FWC FAC CLOCK FDIU DMC

FLIGHT
A/C IDENT ENGINE
FLIGHT PHASES NUMBER GMT SERIAL
CLASS 2 CLASS 2 NUMBER
ECAM WARNINGS FAILURES CITY DATE FAILURES
PAIR
MAIN CHANNEL BACKUP CHANNEL

C F D I U
* MEMORY * DETECTION
* MANAGEMENT
INTERNAL * CORRELATION
CLOCK * MONITORING
FLIGHT PHASE GMT A/C IDENT CITY CLASS 2 ENGINE

PAIR CITY FAILURES SERIAL
PAIR
DATE NUMBER
TYPE 1 SYSTEMS MU DMU EVMU
Figure 23 CFDIU Functions

31-30
CFDIU FUNCTIONS (CONT.)
INTERFACES (CONT.)
DMC (Display Management Computer, part of EIS)
The CFDIU receives the Engine Serial Number from the DMC and sends this
parameter to the EVMU (Engine Vibration Monitoring Unit).
MU (Management Unit of ACARS)
The ACARS Management Unit receives the city pair from the FAC through the
CFDIU.
EVMU (Engine Vibration Monitoring Unit)

The EVMU receives the Engine serial number from the DMC through the
CFDIU.
The DMC receives it from the ECU (Engine Control Unit).
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.
BACKUP Mode
In BACKUP Mode, only the main computers are available and only the ”SYS-
TEM REPORT/TEST ” function is available.
In the event of main channel failure:
S If this failure is serious (Power Supply or Microprocessor) the backup chan-
nel takes over.

Only ”BACKUP MODE” is displayed on the CFDS menu.
No function is available in flight.
S If this failure is minor, the item ”BACKUP MODE” is added to the CFDS
menu.
This enables the access to the backup channel.
The main channel remains available.

31-30
FWC FAC CLOCK FDIU DMC

FLIGHT
A/C IDENT ENGINE
FLIGHT PHASES NUMBER GMT SERIAL
CLASS 2 CLASS 2 NUMBER
ECAM WARNINGS FAILURES CITY DATE FAILURES
PAIR
MAIN CHANNEL BACKUP CHANNEL

C F D I U
* MEMORY * DETECTION
* MANAGEMENT
INTERNAL * CORRELATION
CLOCK * MONITORING
FLIGHT PHASE GMT A/C IDENT CITY CLASS 2 ENGINE

PAIR CITY FAILURES SERIAL
PAIR
DATE NUMBER
TYPE 1 SYSTEMS MU DMU EVMU
Figure 24 CFDIU Functions

31-30
COMPONENTS
Student Notes:

31-30
Figure 25 Components Location

Lufthansa Technical Training A321-131
31-30
PFR FILTER PROGRAM

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 52
31-30
Figure 26 PFR Filter-Loading

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 53
31-30
Figure 27 CFDS Menu (new)

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 54
31-30
Figure 28 PFR Messages Filter Activation

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 55
31-30
Figure 29 Data Base Identification

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 56
31-30
Figure 30 Non filtered PFR

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 57
31-30
Figure 31 Print of a Filter Data Base

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 58
31-30
Figure 32 Filtered PFR

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 59
31-30
DATA LOADING SYSTEM

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 60
31-30
Figure 33 Data Loading System Locations

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 61
31-30
Figure 34 Data Loading System Schematic

FRA
FRA US
TS84,
84 wd 7.12.93
01.02.95 Seite: Page: 62

ATA 31-32 Indicating &amp; Recording

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ATA 31-32 Indicating &amp; Recording

Hochgeladen von

Copyright:

Verfügbare Formate

Training Manual

Lufthansa Issue: JAN. 1998

Lufthansa Technical Training GmbH

Lufthansa Base Frankfurt

Lufthansa Base Hamburg

ATA 31 INDICATING AND RECORDING

FRA US/T WD 03.09.99 Page: 1

The 2nd MCDU is also connected to the CFDS.

FRA TS84, wd 7.12.93 Seite: Page: 2

SYSTEM BITE PHILOSOPHY

FRA TS84, wd 7.12.93 Seite: Page: 4

BITE ECAM WARNING

POST FLIGHT REPORT (PFR)

FRA TS84, wd 7.12.93 Seite: Page: 6

LAST LEG REPORT LAST LEG ECAM REPORT

Standard for Example DLH Version

Figure 3 Post Flight Report

FRA TS84, wd 7.12.93 Seite: Page: 8

AIR DATA SYSTEM

Figure 4 Internal/External Failures

FRA TS84, wd 7.12.93 Seite: Page: 10

MEMORIZATION FAILURE GRAVITY

Figure 5 Memorization/Failure Gravity

SYSTEM TYPES Type 3 Systems

FRA TS84, wd 7.12.93 Seite: Page: 12

Figure 6 System Types

FRA TS84, wd 7.12.93 Seite: Page: 14

HYD B RSVR OVHT

3000 PSI 3000 PSI 3000

< RETURN PRINT *

Figure 7 Class 1 Failure

FRA TS84, wd 7.12.93 Seite: Page: 16

CURRENT LEG REPORT

Figure 8 Class 2 Failure

FRA TS84, wd 7.12.93 Seite: Page: 18

< RETURN PRINT *

Figure 9 Class 3 Failure

FRA TS84, wd 7.12.93 Seite: Page: 20

CLASS 1 CLASS 2 CLASS 3

REFER TO MMEL FUNCTIONS LOST

Have to be reported by the Available on

pilots in the log book. left uncorrected

Figure 10 Failure Classification Synthesis

FRA TS84, wd 7.12.93 Seite: Page: 22

FRA TS84, wd 7.12.93 Seite: Page: 24

< PFR FILTER PROGRAM

Figure 12 CFDS Menu on Ground

FRA TS84, wd 7.12.93 Seite: Page: 26

Figure 13 Last Leg Report

FRA TS84, wd 7.12.93 Seite: Page: 28

Figure 14 Last Leg ECAM Report

FRA TS84, wd 7.12.93 Seite: Page: 30

Figure 15 Previous Legs Report

FRA TS84, wd 7.12.93 Seite: Page: 32

Figure 16 Avionics Status

FRA TS84, wd 7.12.93 Seite: Page: 34

SYSTEM REPORT/TEST MENU

Figure 17 System Report/ Test

FRA TS84, wd 7.12.93 Seite: Page: 36

Standard for Example DLH Version

FRA TS84, wd 7.12.93 Seite: Page: 38

Figure 19 GMT/ Date Initialization

S the REAL TIME WARNINGS

FRA TS84, wd 7.12.93 Seite: Page: 40

ATA 31-32 Indicating & Recording

ATA 31-32 Indicating & Recording