A320 Family Maintenance concept - Diagnosis

Reference: 31.32.00071 Issue date: 23-JUL-2021 Last check date: 23-JUL-2021 Status: Closed
A/C type/serie: A318, A319, A320, A321 ATA: 31-32
Engine manufacturer: Supplier: THALES AVS FRANCE SAS
Purpose / Reason for revision: Update Interfaces chapter
Engineering Support Status: Closed

A320 Family Maintenance concept – Diagnosis

RECORD OF REVISIONS

Date Effect on Effect on paragraph Reasons for revision

page

15/05/2019 All All ISI creation

01/04/2019 - §Generalities The following chapters were

§Equipment description added to the ISI :
§Interfaces - §Generalities
§Correlation - §Equipment description
§Details on customization - §Interfaces
- §Correlation
- §Details on customization

23/11/2020 - §Notions and Philosophy Introduce ISI 45.00.00045

§Reports
§Tools
22/06/2021 - §General Parameters Introduce new information
about flight phase parameter
 §Time management Introduce ISI 31.32.00006
23/07/2021 - §BITE Standards and Types Introduce ISI 45.00.00046
TABLE OF CONTENTS

1. GLOSSARY 4

2. OVERVIEW 6

2.1 GENERALITIES 6

3. ARCHITECTURE 8

3.1 EQUIPMENT DESCRIPTION 8

3.2 INTERFACES 8

3.2.1 General parameters 9

3.2.2 MCDUs 10

3.2.3 Printer 10

3.2.4 ACARS-MU / ATSU (Datalink) 11

3.2.5 Dataloader (MDDU) or Portable Data Loader Connector (CDLC) 11

3.2.6 FWC 11

3.2.7 Type 1 and Type 2 systems 12

3.2.7.1 From CFDS to BITE Type 1 12
3.2.7.2 From BITE Type 1 and Type 2 systems to CFDS 12
3.2.7.3 Maintenance data 12
3.2.7.4 LRU identification data 13

3.3 FLS MANAGEMENT 13

4. NOTIONS AND PHILOSOPHY 13

4.1 BITE STANDARDS AND TYPES 13

4.2 BITE MODES AND MAINTENANCE PHASES 14

4.3 FAULT CLASSIFICATION 15

4.4 EFFECT TYPES 15

4.5 DISPATCH / TROUBLESHOOTING WORKFLOW 15

4.6 PROACTIVE MAINTENANCE 15

4.7 PREVENTIVE MAINTENANCE 15

4.8 CORRELATION 16

4.9 TIME MANAGEMENT 22

5. FUNCTIONALITIES 22

5.1 REPORTS 22

5.2 TOOLS 22

5.3 FILTERING 23

5.4 DATALINK CAPABILITY 23

5.5 DETAILS ON CUSTOMIZATION 24

5.6 PRINTING 31

6. CONFIGURATION MANAGEMENT 31

7. KNOWN ISSUES 32

8. TOOLS 32

8.1 GROUND TOOLS 33

8.2 TSD 33

1. GLOSSARY

ACARS Aircraft Communication Addressing and Reporting

System
ACARS- ACARS Management Unit
MU

ARINC Aeronautical Radio INCorporated

ATSU Air Traffic Service Unit

BITE Built In Test Equipment

CDLC Centralized Data Loading Connector

CFDIU Centralized Fault Display Interface Unit

CFDS Centralized Fault Display System

CMC Centralized Maintenance Computer (equivalent to

CFDIU)

CMS Centralized Maintenance System (equivalent to

CFDS)

DB DataBase

DMC Display Management Computer

DMU Data Management Unit

ECAM Electronic Centralized Aircraft Monitoring

ESLD ECAM System Logic Data

FAC Flight Augmentation Computer

FAQ Frequently Asked Questions

FDIU Flight Data Interface Unit

FLS Field Loadable Software

FWC Flight Warning Computer

LRU Line Replaceable Unit

MCDU Multipurpose Control & Display Unit

MDDU Multipurpose Disk Drive Unit

MSG MeSsaGe

PFR Post Flight Report

TSD Trouble Shooting Data

UMS User Modifiable Software

2. OVERVIEW

GENERALITIES

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 Centralized Fault Display Interface Unit (CFDIU) which interfaces with Built-In Test Equipment (BITE) of each
connected Line Replaceable Unit (LRU).
The CFDIU is located in the avionics bay. The following table provides identification references for CFDIU.

Functional CFDIU
designation :

FIN : 1TW

ATA : 31-32-34

Panel : 87VU

Zone : 127
The CFDIU is identified by a PNR that defines the hardware with its OBRM.
The following figure provides location of the CFDIU on the aircraft.
3. ARCHITECTURE

EQUIPMENT DESCRIPTION

The CFDS is made up of the following components:

- The systems’ BITE: The BITE is an electronic device (hard + soft) located inside each electrical or electronic system of the aircraft. The main functions of the
BITE are to detect, locate and store the faults of the system.
- The CFDIU: This computer is connected to the BITE of the electronic systems of the aircraft and receives the fault data from these systems. Moreover, the Flight
Warning Computer 1 or 2 (FWC), the Flight Augmentation Computer 1 (FAC1), the Clock, the Flight Data Interface Unit (FDIU) and the Display Management
Computer 1 (DMC) are used in the basic definition to deliver general parameters.
The CFDIU is connected to most of the electronic systems (BITE) of the aircraft.
It receives:
- and centralizes the fault data from the BITEs of the systems ;
- additional data from the FWC, the FAC, the clock, the FDIU and DMC to compute and broadcast the general parameters.
CFDIU has different user interfaces:
- 2 MCDUs, which are located in the cockpit and consists in :
o a screen used for the display of data ;
o an alphanumerical keyboard ;
o line selectable keys (LSK) for sending commands to the systems that are connected to it.
- the Printer, located in the cockpit on right section of the center pedestal. e.g. for maintenance reports.
- the ACARS (optional, ACARS-MU or ATSU), located in the avionics compartment. It manages the datalink transmissions of maintenance data from the aircraft
to the ground.
- the Data Loader, which could be either on-board (MDDU, located in the cockpit, on the left section of the center pedestal (117VU)) or portable (PDL).

INTERFACES

CFDIU receives fault information from approximately 130 aircraft basic and optional systems. Those systems could be either directly
connected to the CFDIU or indirectly connected to the CFDIU through another system.
Please refer to AMM 31-32-00-00 paragraph 5. Interfaces to get the complete list of systems, as well as their BITE type, and if they are
connected directly or indirectly to the CFDIU.
The CFDIU inputs (for maintenance) consist of:
- ARINC 429 buses from type 1 and 2 systems,
- Discretes from type 3 systems,
- Hardware Pin Programming and Flight/Ground condition.
The CFDIU outputs consist of:
- ARINC 429 buses to type 1 systems,
- Discretes to type 2 and 3 systems.
The following figure provides an overview of the CFDS with its main peripherals.
 For additional information on Type 1, Type 2 and Type 3 system, refer to section BITE STANDARD.

General parameters

CFDIU transmits general parameters to Type 1 systems which use them to generate and memorize fault reports. CFDIU also uses these
general parameters to generate fault reports that are stored in CFDIU memory.
These general parameters are received by the CFDIU from the following systems:

- Clock: provides the GMT/Date. CFDIU also comprises an internal clock that it will use when the GMT from the Cockpit CLOCK is not available anymore
(confirmed for 1 minute). In that case CFDIU internal clock will be initiated with the last valid GMT acquired (incremented by 1 minute). If no valid GMT was
acquired since CFDIU power up then CFDIU will use the GMT 79:99 and 1 JAN 00 for the date.

- FWC: provides the flight phase.

The Flight Phase parameter, which may vary from 01 to 10, is acquired each second from the FWC1 or 2 on label 126. It is processed in a nominal or a degraded
way as described hereafter:
- Nominal case: the FWC1 label 126 is valid. The CFDIU sets its Flight Phase value to the acquired Flight Phase value.
- Degraded cases : the Flight Phase is not correctly acquired from FWC1 and the CFDIU switched to FWC2 :
o If the Flight Phase parameter is acquired correctly from FWC2, the functioning is the same as in Nominal case ;
o If the Flight Phase parameter is not acquired correctly from FWC2, the CFDIU sets its Flight Phase value to :
o The last Flight Phase acquired correctly, if there is a value in CFDIU NVM (the last value correctly acquired);
 o A Flight Phase of “01”, which is the default value, if there is no value in CFDIU NVM.

Note: Once the switching to FWC2 is done, the CFDIU stays on this input to get FWC information until the CFDIU is restarted.

- FDIU and DMU: provides the A/C identification. CFDIU processes warnings data coming from the FDIU and DMU (on their label 350), and transmits these data
to FWC (on label 270) to permit to display the maintenance status messages on the ECAM.

- FAC1: provides the flight number as well as the City pair (departure and arrival airports). For additional information on CFDIU acquisition of City pair information,
please refer to: ISI 31.32.00033 Centralized Fault Display Interface(CFDIU)-Acquisition of City pair information by the CFDIU

- DMC1: provides the engine serial number

MCDUs

MCDUs allow to dialog between the CFDIU and the BITEs of the various systems connected to the CFDIU, depending on the flight/ground
conditions.
The CFDIU is able to transmit to the MCDU through ARINC 739-1:
- its own pages,
- the pages sent by the type 1 and type 2 systems in Interactive Mode,
- the pages generated from “raw data” received from the type 2 systems.

Printer

The Printer is located in the cockpit, on the right section of the center pedestal. It is connected to the CFDIU and serves to print reports using
ARINC 740 protocol. Printing can be requested manually by an operator or programmed in the reports to print some reports automatically.
ACARS-MU / ATSU (Datalink)

ACARS-MU / ATSU is connected to the CFDIU through ARINC 724-Band enables transmission of reports to the ground station.
On A/C, either ACARS MU or ATSU is installed and only one LRU (ACARS-MU or ATSU) is installed.
CFDIU STD 8 only knows the ACARS-MU as data link system (no ATSU) whereas subsequent standards (post STD 8) are capable of managing BITE information
received either from an ACARS-MU LRU or from an ATSU LRU.
To ensure the CFDS computes the right configuration and displays correct maintenance message in case of ACARS-MU or ATSU failure, the hard-wired pin-prog
are used.
Dual ACARS / ATSU pin programming (MOD 31397) allows then two way interchangeability condition (ICY 200) in case operator needs to replace a faulty CFDIU
(STD >8) with a CFDIU STD 8 or pre-STD 8 as a spare.

Dataloader (MDDU) or Portable Data Loader Connector (CDLC)

The data loader (MDDU), or Portable Data Loader Connector (CDLC) is located in the cockpit on the left section of the center pedestal
(117VU) or in the overhead panel (52VU, CDLC only). It is connected to the CFDIU and enables to upload the filter data base. The
maintenance filter (or PFR filter) database is the only software (UMS) that can be uploaded into the CFDIU through ARINC 615-3 “low speed”
dataloading.
For trouble shooting guidance whenever CFDIU PFR filter data loading is not working, please refer to: ISI 31.32.00048 Centralized Fault
Display Interface-CFDIU PFR data loading not working

FWC

In addition to the flight phase provided in general parameters, CFDIU also acquires ECAM Warnings from FWC on label 357 in DC1
maintenance phase only.
ECAM warnings are sent by FWC only once, except if the CFDIU is not ready to acquire them (Maintenance phase = NUL or DC2). An alert
detected in Maintenance phase NUL or DC2 will be sent again to CFDIU at the transition DC2/DC1 if this alert is still present.
CFDIU is able to treat only one FWC input source at a time. CFDIU will firstly acquire the ECAM warnings on label 357 from the FWC1. If
FWC1 is considered INOP by the CFDIU then CFDIU will start acquiring those messages from FWC2, and will stay in this configuration until
CFDIU is power cycled (even in case FWC2 becomes INOP and/or FWC1 is available again).
Type 1 and Type 2 systems

From CFDS to BITE Type 1

As explained in General parameters section, CFDS transmits general parameters to the BITE Type 1 systems which use them to generate and
memorize fault reports.
In Interactive mode, operator can activate tests or access reports from a specific system using the CFDS. CFDS sends then BITE commands to
the BITE of the System.

From BITE Type 1 and Type 2 systems to CFDS

BITE Type 1 and Type 2 send maintenance data through label 356 and LRU identification data through label 354 to the CFDS.

Maintenance data

In normal mode, systems send their fault messages on label 356 directly to the CFDIU, or indirectly through another system.
For additional information on the sending of fault messages from the BITE of the systems to the CFDIU, please refer to: ISI 45.00.00045 All
A/C families Diagnosis – Maintenance Phases and BITE modes.
For each new fault message received, CFDIU extracts:
- the ATA 6 digits from the failure message,
- the origin (External or Internal),
- the source for the failure message.
CFDIU performs then a coherency check on the fault message and enriches the fault message with the GMT/Date and the flight phase.

In Interactive mode, systems communicate with CFDIU through label 356 to send their display and screen encoding.

In flight, each failure message is sent to CFDIU continuously by Systems Type 1 and 2 as long as it is consolidated (not intermittent).
 LRU identification data

All Type 1 and Type 2 systems have to transmit their own identification and the identification of their sub-systems to the CFDIU in normal
mode through label 354, including:
- the name of the LRU
- the P/N’s of the LRU (Hardware and Software / database)
- the S/N of the LRU’s hardware.

FLS MANAGEMENT

For additional information on CFDIU Maintenance filter data loading not working, please refer to: ISI 31.32.00048 Centralized Fault Display
Interface-CFDIU PFR data loading not working

4. NOTIONS AND PHILOSOPHY

BITE STANDARDS AND TYPES

All systems including a BITE function are connected to a Diagnosis System by means of system bus or discrete signals.
When a fault is detected by the BITE function of an A/C system, the corresponding system sends a failure message to the Diagnosis System.
BITE standards define the overall communications means of the Diagnosis System (including the method of communication between the
aircraft systems and the Diagnosis System) and the reporting capacities.
Two different standards of BITE have been developed and are used in the Airbus family :
- Standard A is the classic standard basically developed for A320, A330 and A340 aircrafts families and still used on A380 and A350 family.
- Standard B developed for A380 and then used for A350.

According to the complexity of the systems monitored by the different BITEs, Airbus has defined several requirements concerning the capacities of maintenance data
transmission and memorization.
Depending on the system complexity, the BITE capacities are more or less advanced.
For this reason, the standard A or B systems are categorized in different types (type 1, 2, 3).

For additional information on BITE standards and types, please refer to ISI 45.00.00046 All A/C families – BITE Standards and Types.

- What is the meaning of fault messages CLASS S : 31.32.00015

- BITE standard A type 1, 2 and 3 memory management : 45.11.00013

BITE MODES AND MAINTENANCE PHASES

 There are two modes of communication between the diagnosis system and the BITE of the systems:
- Normal mode: one way reporting transmission from systems BITE to CFDIU
- Interactive mode or Menu mode: duplex communication between BITE and CFDIU for testing and specific BITE data access
Activation and capabilities of Normal mode and Interactive Mode depend of the Maintenance Phase computed by the CFDIU.
For additional information on Normal/Interactive modes, failures acquisition, maintenance phase computation, please refer to ISI 45.00.00045 All
A/C families Diagnosis – Maintenance Phases and BITE modes.
 FAULT CLASSIFICATION

- Signification of Spurious : 31.00.00015

- Onboard maintenance systems-What is the difference between SOURCE and IDENTIFIER shown on the PFR : 31.32.00017

- Class failure definition on A320 : 31.32.00028

- CFDIU - Relationship between the PFR and the three fault classifications : 31.32.00044

EFFECT TYPES

- CFDIU - ECAM warnings ending with XX on ACARS PFR : 31.32.00036

- Centralized fault display interface(CFDIU)-MAINTENANCE STATUS processing : 31.32.00016

- Centralized fault display interface(CFDIU)-MAINT STS IN PFR ENDING WITH XX : 31.32.00019

DISPATCH / TROUBLESHOOTING WORKFLOW

- CFDIU - Relationship between the PFR and the three fault classifications: 31.32.00044

- A320 Centralised Fault Display System - Troubleshooting guidelines: 31.32.00069

- How to handle different class fault messages: 45.00.00028

- Central Maintenance System(CMS)-Handling of Class 1 Fault MSG without associated cockpit effect: 45.13.00012

PROACTIVE MAINTENANCE

- CFDIU - Relationship between the PFR and the three fault classifications: 31.32.00044

PREVENTIVE MAINTENANCE

- CFDIU - Relationship between the PFR and the three fault classifications: 31.32.00044

CORRELATION
 From the CFDIU standard 10A (PNR C12860AA03), a function of correlation between effect (warning or maintenance status) and fault
message is implemented in the CFDIU. The aim of this function is to determine whether warning or maintenance status acquired during a
flight could be correlated with a fault message acquired during the same flight. Each warning/maintenance status can be correlated to one
fault message at most. Each fault message can be correlated to one warning/maintenance status at most.

CORRELATION ACCESS
The correlation results are only available on MCDU through the CFDS main page, from the LAST LEG REPORT or LAST LEG ECAM REPORT and
could not be printed or sent to the ground station. They are not either memorized. On MCDU, if a correlation between warning/ or
maintenance status and fault message has been established, a prompt (“>”) on the right of corresponding fault message or
warning/maintenance status enables to display the associated warning/maintenance status or fault message on the MCDU.

The following figure illustrates access to the correlation results from the CFDS main page.

- From CFDS main page, if the 1L MCDU line key is pressed, the LAST LEG REPORT page is displayed. If an effect is correlated to a fault message, a prompt (“>”)
is added on the right of the corresponding fault message. Then, if the MCDU line key corresponding to one of the prompts is pressed, the correlated effect is
displayed. The level of detail of the correlated effect is the same as those of the LLER (hour, flight phase, ATA and effect message), but only the correlated effect is
shown.

- From CFDS main page, if the 2L MCDU line key is pressed, the LAST LEG ECAM REPORT page is displayed. If a fault message is correlated to an effect, a prompt
(“>”) is added on the right of the corresponding effect. Then, if the MCDU line key corresponding to one of the prompts is pressed, the correlated fault message is
displayed. The level of detail of the correlated fault message is the same as those of the LLR subpage, i.e. once the operator has selected a fault message in the
LLR to get more details about a fault message (hour, flight phase, ATA, fault message, source and identifiers).
CORRELATION PRINCIPLE
The correlation consists in building fault cases by pairing effects (warning or maintenance status) with fault messages based on their
occurrence time and their ATA number (those of messages or Source or Identifier(s) if any). For that, two kinds of correlation are performed:
- fault/fault correlation,
- effect/fault correlation.

FAULT/FAULT CORRELATION
 To apply the effect/fault correlation, the CFDIU carries out before a fault/fault correlation in order to display in the Post Flight Report (PFR)
only one fault message for a given "aircraft failure", sufficient to launch the troubleshooting of the failure. The general principle of this
correlation is to group all fault messages linked to the same aircraft failure and to keep the most significant ones with the name of the
component or system that has triggered it (system "source"), together with the name of the other components (“identifiers”) that have
triggered a fault message for this failure.

The “correlation criteria” is based on the ATA of the fault message : two faults which have the same three first ATA digits are correlated
together, excepted for two particular cases called “simple particular cases” and “double particular cases” where a fault needs to have its four
first ATA digits equal to one of a specific list to be correlated only with another fault with the same ATA (see AMM for ATA list of simple and
double particular cases).

The CFDIU correlates faults messages of the same ATA family acquired in a limited timeframe called "correlation window". The starting point
of fault correlation is an aircraft failure. A “correlation window” lasts:
- at least one minute and two scanning laps from the time of opening of the window if opened under DC1,
- or at least one minute and two scanning laps from the time of DC2/DC1 maintenance phase transition if opened under the Maintenance Phase DC2.

At the end of the correlation timeframe, the CFDIU will have generated as many correlated fault messages as there are fault origins ; in other
words as many group of fault messages as there are different failures. In a correlated fault case, the primary fault is recorded as the “source”
and the others are recorded as “identifiers”.
In the PFR, the “source” is the system (for system BITE) or the computer which generated the fault message retained by the CFDIU for this
failure and recorded in the PFR. The identifier(s) is(are) the computer(s) which has(have) also reacted in relation to the failure by generating
fault messages accusing the same LRU. The number of identifiers is limited to 6. If more than 6 are correlated, the CFDIU keeps only the first
six systems received. The remaining are ignored.

Example of fault/fault correlation :

In this example, during the flight, three fault messages have been received by CFDIU.

- An internal fault message “FAULT MSG A ACCUSING ATC1” on ATC1 input bus :
GMT PH ATA SOURCE
1646 06 32-31-71 FAULT MSG A “ATC1” ATC 1

- Two external fault messages:

o “FAULT MSG B ACCUSING ATC1 OR INTERFACE BETWEEN ATC1 AND RA2” on RA2 input bus
1646 06 32-31-71 FAULT MSG B “ATC1” RA 2
OR INTERFACE ATC1/RA2

o “FAULT MSG C ACCUSING ATC1 OR INTERFACE BETWEEN ATC1 AND AMU” on AMU input bus
1646 06 32-31-71 FAULT MSG C “ATC1” AMU
OR INTERFACE ATC1/AMU

The three fault messages have been received in the same minute (16h46) and have the same ATA. The three fault messages are correlated in
the PFR.
GMT PH ATA SOURCE IDENT.
1646 06 32-31-71 FAULT MSG A “ATC1” ATC 1 RA 2
AMU

EFFECT/FAULT CORRELATION
The aim of this effect/fault correlation is to determine whether effects acquired during a flight could be correlated with fault messages
acquired during the same flight. The Effect/Fault correlation associates an effect (warning/maintenance status) to one fault message. Once
one effect has been correlated to one fault message, both fault message and effect could not be used for any other effect/fault correlation.

The CFDIU correlates fault messages of the same ATA family (“correlation criteria”) acquired in a limited timeframe ("correlation window").

For the Effect/Fault correlation, the CFDIU tries to apply:

- first, a 4 digit correlation rule: each effect could be associated to a fault, if the GMT of the fault is within GMT effect +/- 2 minutes and if one of these conditions
is true :
o the first 4 ATA digits of the fault message or of the fault source or of one of the fault identifiers are equal to the first 4 ATA digits of the effect ;
o the first 4 ATA digits of the fault message or of the fault source or of one of the fault identifiers and the first 4 ATA digits of the effect are in the same
pre-defined group (see AMM for more details concerning pre-defined group).
- and then for the remaining effects which have not been correlated with the 4 digit correlation rule, a second rule applies to try to correlate them to faults: the 2
digit correlation rule. For each of the remaining effects, a fault could be associated if the GMT of the fault is within GMT effect +/-2 minutes and if one of these
conditions is true (except for some ATA number of fault message or effect message or source or identifier identified in the AMM) :
o the first 2 ATA digits of the fault message or of fault source or of fault identifiers are equal to the first 2 ATA digits of the effect.

The effect/fault correlation is performed:

- at the DC1/NULL maintenance phase transition,
- at the end of a filter data loading, if this data loading is successful and if the filter functionality is active,
- if the filter programming is modified from inactive to active.
- after the healthy discrete computation, if the memorized maintenance phase is equal to NULL.

This function is stopped:

- when all the effects have been processed,
- if the effect/fault correlation is in progress for more than 2 minutes,
- at NULL/DC2 transition.

ILLUSTRATION OF CORRELATION

>> 1 to be correlated with a (thanks to same 4 ATA digits between fault message and warning)
>> 2 to be correlated with b (thanks to same 2 ATA digits between fault message and warning)
>> 3 to be correlated with d (thanks to same 2 ATA digits between fault message and warning)
>> 4 to be correlated with d (thanks to same 2 ATA digits between fault identifier and maint. status)
 >> 5 to be correlated with e (thanks to same 2 ATA digits between fault message and warning)
>> c is orphan (in this case, the effect is not reported to CFDS. It could be a local effect like a loss of TCAS data display on PFD or ND)

TIME MANAGEMENT

The aircraft time base, in normal operation, is the electrical CLOCK located on the main instrument panel.
The CFDIU permanently acquires the UTC and Date from the CLOCK and synchronizes its internal clock with it.
Moreover the CFDIU retransmits these data to some systems on its output buses.
To get additional explanations regarding time management by the CFDIU, failure declaration in case of CLOCK issue and procedure to
restore the CFDIU clock, please refer to 31.32.00006 A320 Diagnosis – Time management.

5. FUNCTIONALITIES

REPORTS

To get the list of reports available in flight and on ground, please refer to ISI 45.00.00045 All A/C families Diagnosis – Maintenance Phases and
BITE modes.

- CFDIU - Avionics Data line function in CFDS Reports Programming page 31.32.00032

- Central Fault Display System (CFDS) - CFDS REPORT layout and SYSTEM BITE REPORT layout : 31.32.00056

- CFDS REPORT ACARS FORMAT : 31.32.00066

- FADEC - SMR management : 73.22.00002

- Maximum number of warning and failure messages in the PFR : 31.32.00007

- Rejected PFR in AIRMAN-web : 31.32.00008

- Onboard maintenance systems-What is the difference between SOURCE and IDENTIFIER shown on the PFR : 31.32.00017

- Centralized fault display interface(CFDIU)-Meaning of the three letters -DB-N- in the PFR header : 31.32.00020

- CFDIU - Relationship between the PFR and the three fault classifications : 31.32.00044

- Centralized fault display interface unit(CFDIU)-When is the PFR automatic printed : 31.32.00046

TOOLS
To get the list of tools available in flight and on ground, please refer to ISI 45.00.00045 All A/C families Diagnosis – Maintenance Phases and BITE
modes.

- Central Fault Display System (CFDS) - CFDS REPORT layout and SYSTEM BITE REPORT layout : 31.32.00056

- Line Replaceable Unit (LRU) - Interpretation of Troubleshooting Data (TSD) for all avionics boxes : 31.32.00026

FILTERING

- PFR - Spurious GROUND CFDS message : 31.00.00003

- Central fault display system(CFDS)-CFDS computation of Ground - Flight or Flight - Ground transition : 31.32.00018

- Centralized fault display interface(CFDIU)-Meaning of the three letters -DB-N- in the PFR header : 31.32.00020

- Centralized Fault Display Unit (CFDIU) Creation of an empty PFR filter : 31.32.00023

- Centralized Fault Display Interface-CFDIU PFR data loading not working : 31.32.00048

- MFT Maintenance Filter Tool v3.2 for CMC and CFDS filter file production : 31.32.00062

- A320 family CFDS filter – FAQ : 31.32.00064

- Authorized SOURCE NAME for CFDIU PFR FILTER DATABASE : 31.32.00068

- SA Centralized Fault Display System (CFDS) Filter Envelope content : 45.00.00039

- How to filter AIR PACK 1+2 FAULT with CFDS filter : 45.13.00024

DATALINK CAPABILITY

- PFR RTF RTW ACTIVATION : 31.00.00001

- CFDIU - RTW transmission mechanism : 31.32.00004

- Loss of PFR in AIRMAN : 31.32.00011

- How to activate ATSU configuration on CFDS : 31.32.00021

- CFDIU - Automatic transmission of PFR : 31.32.00024

- CFDIU - Avionics Data line function in CFDS Reports Programming page : 31.32.00032

- CFDIU - How to disable Manual Sending of AVIONICS DATA (BITE Reports) : 31.32.00034

- CFDS REPORT ACARS FORMAT : 31.32.00066

- Centralized Fault Display Interface Unit (CFDIU) - Capability of handling uplink request received from ATSU : 31.32.00042

DETAILS ON CUSTOMIZATION

The CFDIU is capable of transmitting and/or printing automatically some reports if automatic transmission and/or print is configured.
The values of customization related to automatic transmission (SEND) / print (PRINT) of those reports are displayed in the REPORTS
PROGRAMMING page of the CFDS main menu.
Note: Before CFDIU standard 8 (included), this page dedicated to the reports programming was named ACARS/PRINT PROGRAM.
But in this chapter, the REPORTS PROGRAMMING naming is used to present the CFDS programming possibilities.
What can be programmed to be automatically transmitted/printed?
Until CFDIU standard 10, the REPORTS PROGRAMMING page of the CFDS main menu displays the following reports:
- POST FLT REP
- REAL TIME FAIL
- REAL TIME WARN
- AVIONICS DATA

Note that each function associated to an asterisk in the REPORTS PROGRAMMING page of CFDS could be directly modifiable by the MCDU.
When there is a “YES” or “NO” in green it means that it cannot be modified, whereas “YES” or “NO” in blue means that the corresponding setting
can be modified.
From CFDIU standard 10, two additional reports are available in this page:
- AVIONICS CONF REP
- NON CORRELATED PFR
 The above reports are associated to both SEND and PRINT columns:

- "SEND": displays the programming status (YES or NO) for the automatic ACARS transmission of the report.
The following table summarize the programming possibilities for the SEND function.
For AVIONICS DATA (BITE menu), AVIONICS CONF REP and NON CORRELATED PFR, there is no automatic DOWNLINK capability. The transmission can only
be performed manually thanks to PRINT ALSO SEND function of the dedicated pages.
 SEND programming from REPORTS
Reports Consequence
PROGRAMMING page of CFDS
This status “YES” or “NO” is “YES” indicates that this report will be transmitted
POST FLT REP
received from the ATSU. The programming is automatically at the end of the flight
displayed in green and is not modifiable in this “YES” indicates that this report will be transmitted
page. The status “YES” or “NO” can be automatically each time a new maintenance
REAL TIME FAIL changed only by reprogramming the Airline message is processed by the CFDIU during the
Operational Control (AOC) database (which PFR recording period.
requires the GSE tool of the vendor) or from
MCDU “programming” page of AOC.

(see below explanations in order to configure “YES” indicates that this report will be transmitted
REAL TIME those settings) automatically each time an ECAM
WARN alert/maintenance status is processed by the
Note: if the CFDIU has not received any CFDIU during the PFR recording period.
programming from the ATSU, it is displayed
blank.
This programming activates the PRINT ALSO SEND
function for the AVIONICS DATA

“YES” or “NO” can be changed through MCDU “YES” indicates that this report will be transmitted (and
AVIONICS DATA
scratch pad printed) automatically each time a manual
printout of an interactive mode is commanded.
“NO” indicates that this report will not be
transmitted (and will be only printed).
“YES” or “NO” can be changed through MCDU On CFDIU standard 10 to 13, this programming
scratch pad. activates the PRINT ALSO SEND function for the
AVIONICS CONF REP.
AVIONICS CONF But it is recommended to set it to “NO” because
REP sending of Avionics Configuration Report is “YES” indicates that this report will be transmitted (and
affected by a limitation on CFDIU standard printed) each time a manual printout of the report
lower than standard 14 and issues can be is commanded. “NO” indicates that this report will
encountered during transmission. not be transmitted (and will be only printed).
This programming activates the PRINT ALSO SEND
“YES” or “NO” can be changed through MCDU
function for the NON CORRELATED PFR.
scratch pad.
NON
“YES” indicates that this report will be transmitted (and
CORRELATED But it is recommended to set it to “NO” because
printed) each time a manual printout of the report
PFR this kind of report is not recognized by the
is commanded. “NO” indicates that this report will
Health Monitoring ground tool (like AIRMAN-
not be transmitted (and will be only printed).
web) if transmitted.
The procedure to activate/deactivate PRINT ALSO SEND function of AVIONICS DATA is described in the AMM 31-32-00-610-802-A Activation/Deactivation of the
Avionic Data Printout also Send Function.
No AMM is proposed for activation/deactivation of PRINT ALSO SEND function of AVIONICS CONF REP and NON CORRELATED PFR as it is not recommended
to activate it and it is by default deactivated.
 To summarize, “SEND” can be programmed through REPORTS PROGRAMMING page of CFDS only for AVIONICS DATA (and also for AVIONICS CONF REP
and NON CORRELATED PFR but it is not recommended) whereas for other reports programming status (i.e. PFR, RTF and RTW) can be only read from this page
(and are programmed by another mean - see explanations in part “How to program automatic transmission of PFR, RTF and RTW”).

- “PRINT”: programs the automatic printing of the report.

The following table summarize the programming possibilities for the PRINT function.
For AVIONICS DATA (BITE menu), AVIONICS CONF REP and NON CORRELATED PFR, there is no automatic PRINT capability. The print can only be performed
manually from the PRINT key of the dedicated pages.

PRINT programming from

Reports REPORTS PROGRAMMING Consequence
page of CFDS
POST FLT “YES” indicates that this report will be printed automatically at the end
REP of the flight.
“YES” indicates that this report will be printed automatically each time a
REAL TIME “YES” or “NO” can be
new maintenance message is processed by the CFDIU during the PFR
FAIL changed through MCDU
recording period.
scratch pad for each reports
“YES” indicates that this report will be printed automatically each time
REAL TIME
an ECAM alert/maintenance status is processed by the CFDIU during
WARN
the PFR recording period.
AVIONICS Set to “YES” by default and “YES” indicates that this report will be printed each time a manual
DATA cannot be modified. printout of an interactive mode is commanded.
AVIONICS The PRINT function is basic “YES” indicates that this report will be printed each time a manual
CONF REP for this report, always printout of an interactive mode is commanded.
available and controlled
NON manually by the operator. This “YES” indicates that this report will be printed each time a manual
CORRELATED is why the print control cannot printout of this report is commanded.
PFR be programmed. Nevertheless, the print of this report is restricted by a specific procedure.

The procedures to activate/deactivate the AUTO PRINT function of the reports are described in the following AMMs :
o AMM 31-32-00-610-002-A Activation/Deactivation of the Automatic Post Flight Report (PFR) Printout
o AMM 31-32-00-610-804-A Activation/Deactivation of the Real Time Failure Printout
o AMM 31-32-00-610-803-A Activation/Deactivation of the Automatic Real Time Warning Printout

To summarize, “PRINT” can be programmed through REPORTS PROGRAMMING page only for PFR, RTF and RTW reports. For the other reports, the print is by
default activated for their print on request.

How to program automatic transmission of PFR, RTF and RTW:

The programming of the automatic ACARS transmission of PFR, RTF and RTW is managed by the AOC function hosted in the ATSU.
There are two possibilities to activate/deactivate their transmissions.

- Permanent transmission :
PFR, RTF, RTW transmissions can be activated by loading to the ATSU a customized AOC (Airline Operational Control) database.
The customization of the AOC database can be done either by the AOC provider or, by the Airlines (if they have the AOC ground programming tool).
As it is dependent to the AOC provider for both cases, there is no Airbus AMM reference to describe the customization actions.
 Nevertheless, the following bits shall be set to 1 (or 0) on label 270 to activate (or deactivate) the data transmission:
 RTW transmission: BIT 27 = 1,
 RTF transmission: BIT 28 = 1,
 PFR transmission: BIT 29 = 1.
When the customized AOC database is loaded to the ATSU, the transmission settings are permanently activated on board.
They are kept even after aircraft/ATSU power off.

- Temporary transmission :
PFR, RTF, RTW transmissions can be also activated on board through MCDU, but its programming will be temporary (i.e. until next ATSU power-up).
After aircraft/ATSU power off, the programming modification via MCDU will get back automatically to the default ATSU Airline Operational Control (AOC) database
value.

The “programming” page of the AOC enables to modify the CFDIU programming bit settings (see details in the below table).
The modified settings will override the default AOC database settings until next ATSU power-up.
This “programming” page is accessible on MCDU from ATSU menu then AOC menu. The name of the page will depend on the AOC supplier and P/N installed. It is
sometimes named “CFDIU PROGRAMMING” or “AOC CFDIU PROG”.
This temporary programming is described in the AMM 46-23-00-00 CONF 01 - ATIMS - AIRLINE INFORMATION SERVICES - DESCRIPTION AND OPERATION
(see 4. Operation – A. (9) (i) CFDIU PROG page).

Reports Consequence
To set or clear the bit 29 in the output ATSU status label 270.
POST FLIGHT
1 is for activation of automatic PFR report transmission / 0 is
REPORT
for deactivation
To set or clear the bit 28 in the output ATSU status label 270.
FAILURE REPORT 1 is for activation of automatic RTF report transmission / 0 is
for deactivation
To set or clear the bit 27 in the output ATSU status label 270.
ECAM WARNING
1 is for activation of automatic RTW report transmission / 0 is
REPORT
for deactivation

The settings applied through the customized AOC database or through the “programming” page of AOC MENU are duplicated in the
REPORTS PROGRAMMING page of CDFS described in the previous part.
In the REPORT PROGRAMMING page of CFDS, the “SEND” activation state are only displayed but cannot be modified for PFR, RTF and RTW.
They are displayed in green and are not modifiable.
The displayed content of the "SEND" column is managed by the CFDIU referring to the label 270 coming from the ATSU (or ACARS MU) for
the Post Flight Report, the Real Time Failures and the Real Time Warnings.
On-board, those settings are only modifiable through the “programming” page of the AOC menu managed by the ATSU.

When is the SEND/PRINT programming possible:

The availability of SEND/PRINT programming in the REPORTS PROGRAMMING page of CFDS is dependent on the ACARS/ATSU Pin Programming.
Depending on the Pin Prog, when pushing the MCDU key to access to the REPORTS PROGRAMMING page of CFDS:

ACARS Pin Prog ATSU Pin Prog SEND/PRINT availability

0
0 “ACARS NOT INSTALLED”
is displayed
1
0
0
1
Access to the page is possible
1
1

The REPORTS PROGRAMMING settings are not memorized when changing the ACARS pin prog.
The settings are set to default values when going from a configuration without ACARS to a configuration with ACARS.
By default the configuration is the following:

Reports Default value for SEND Default value for PRINT

POST FLT REP - YES *
REAL TIME FAIL - NO *
REAL TIME WARN - NO *
AVIONICS DATA NO * YES
AVIONICS CONF YES
NO *
REP
NON CORRELATED YES
NO *
PFR

Fields with a ‘*’ can be modified from “NO” to “YES” or from “YES” to “NO”.

And the programming is lost when going to a configuration without ACARS.

Note: When going from a configuration with ACARS to a configuration without ACARS, the menu REPORTS PROGRAMMING is available from
CFDIU restart until the A/C configuration is recalculated by the CFDIU.
On A/C on which ACARS pin prog is not activated, it is therefore not possible to inhibit the automatic PFR print at the end of the flight.
 Is it possible to protect the SEND/PRINT programming:
The access to the REPORTS PROGRAMMING page can be restricted thanks to the password function.
This function is only available on CFDIU STD 9B (P/N C12960AA01) and subsequent standards.
For more details concerning password function, refer to §Tools.

PRINTING

- Centralized fault display system(CFDS)-Logic behind PRINT"star" and PRINT"prompt" in the various CFDS page: 31.32.00014

6. CONFIGURATION MANAGEMENT
- CFDIU PNR C12860AA04 (STD 11A) - SB RELEASE : 31.32.00010

- Indicating Recording System-Central Fault Display Interface--CFDIU STD 8 - STD 9B INTERCHANGEABILITY : 31.32.00035

- CFDIU Standard 12 (P/N: C12860AA06) – Information : 31.32.00070

7. KNOWN ISSUES
- A320 Centralized Fault Display System (CFDS) anomalies : 00.00.00228

- CFDS missing prompt on MCDU MAIN MENU page : 31.00.00006

- No access to Last - Previous Leg Report : 31.00.00007

- CFDIU STD 9B LIMITATIONS WITH NEW ATA 21/26/31/38 SYSTEMS : 31.32.00002

- Access to Toilet BITE : 31.32.00005

- Loss of time indication on Lower ECAM : 31.32.00006

- Loss of PFR in AIRMAN : 31.32.00011

- Central fault display interface(CFDIU) - MCDU ILS item missing and substituted by MMR : 31.32.00013

- Centralized fault display interface(CFDIU)-MAINT STS IN PFR ENDING WITH XX : 31.32.00019

- CFDIU - ECAM warnings ending with XX on ACARS PFR : 31.32.00036

- Data loading equipment - MDDU NOT LOADED message : 45.23.00001

- FADEC - SMR management : 73.22.00002

8. TOOLS
- Rejected PFR in AIRMAN-web : 31.32.00008

- Authorized SOURCE NAME for CFDIU PFR FILTER DATABASE : 31.32.00068

- How to filter AIR PACK 1+2 FAULT with CFDS filter : 45.13.00024

GROUND TOOLS

- Centralized Fault Display Unit (CFDIU) Creation of an empty PFR filter : 31.32.00023

- MFT Maintenance Filter Tool v3.2 for CMC and CFDS filter file production : 31.32.00062

TSD

- Line Replaceable Unit (LRU) - Interpretation of Troubleshooting Data (TSD) for all avionics boxes : 31.32.00026

- TSD MEMORY LOCATION : 31.32.00041

Survey for the Engineering Support section

 Annex

General Information
Potential impact:
Key information:
Solution benefit:
First issue date: 31-MAY-2019 Issue date: 23-JUL-2021 Last check date: 23-JUL-2021

Technical parameters
ATA: 31-32
A/C type/serie: A318, A319, A320, A321
Engine:
Engine manufacturer:
Fault code/ECAM
warning:
FIN: 1TW
Part Number:
Supplier: THALES AVS FRANCE SAS

Attachments
General:
- ISI_31.32.00071_Summary.docx

Links
N/A
© Airbus SAS, 2021. All rights reserved. Confidential and proprietary document.The technical information provided in this article is for convenience and information purposes only. It
shall in no case replace the official Airbus technical or Flight Operations data which shall remain the sole basis for aircraft maintenance and operation. These recommendations and
information do not constitute a contractual commitment, warranty or guarantee whatsoever. They shall not supersede the Airbus technical nor operational documentation; should
any deviation appear between this article and the Airbus or airline's official manuals, the operator must ensure to cover it with the appropriate document such as TA, FCD, RDAS.
Access to WISE is supplied by Airbus under the express condition that Airbus hereby disclaims any and all liability for the use made by the user of the information contained in
WISE. It shall be used for the user's own purposes only and shall not be reproduced or disclosed to any third party without the prior consent of Airbus.