CENTRALIZED FAULT DISPLAY INTERFACE UNIT (CFDIU) - DESCRIPTION AND OPERATION

** ON A/C NOT FOR ALL

1. General

A. Purpose of the Maintenance
The purpose of the onboard maintenance is to provide maintenance personnel with an aid to fault diagnosis further to a complaint of the crew.
To accomplish this goal:

(1) Each system includes a Built-In-Test Equipment (BITE) used for detection and isolation of faulty equipment.
Furthermore the system is able to initiate tests for the purpose of confirming a fault condition or checking that proper system operation is restored after corrective action.
Remark:
To simplify the task of maintenance personnel:

the faces of the computers and the maintenance test functions have been standardized
the maintenance messages are displayed in clear English language and always concern the faulty component or, in some cases, the faulty system.

(2) A Centralized Fault Display Interface Unit (CFDIU) acquires and processes (completes, correlates, memorizes and presents) the data transmitted by the BITEs and the warnings which have originated the crew complaint.

(3) The result of fault diagnosis is displayed to the maintenance operator through the Multipurpose Control and Display Units (MCDU) and the Printer which constitute the user interface.

CFDS - Component Location ** ON A/C NOT FOR ALL

B. Levels of Maintenance
The failure information delivered by the Centralized Fault Display System (CFDS) corresponds to several levels of maintenance.

(1) Line maintenance
This maintenance is characterized by rapid intervention of maintenance personnel in a short time period; it is limited to the isolation and replacement of a faulty equipment.
This action consists of the identification and/or confirmation of fault condition(s), the isolation of the fault and the replacement of the faulty unit (i.e the Line Replaceable Unit (LRU)).
A test is carried out before and after the removal/installation procedure to check the correct operation of the system.

(2) Hangar or main base maintenance
This maintenance is characterized by intervention of maintenance personnel in a longer time period and generally concerns actions that cannot be performed at line maintenance level, either because the procedures are too lengthy or because more skilled personnel are required.

(3) Workshop maintenance
These maintenance actions are performed at regular intervals (as defined by the Operator Maintenance Program (OMP)).
Intervention of maintenance personnel is then scheduled according to aircraft utilization and concerns the items of equipment for which some mechanical parts are not monitored and/or tested. These failures are called hidden failures.

** ON A/C NOT FOR ALL

2. Component Location

CFDS - CFDIU Location ** ON A/C NOT FOR ALL

FIN	FUNCTIONAL DESIGNATION	PANEL	ZONE	ACCESS DOOR	ATA REF
** ON A/C ALL
1TW	CFDIU	87VU	127		31-32-34

** ON A/C NOT FOR ALL

3. System Description

A. System Architecture

CFDS - Block Diagram ** ON A/C NOT FOR ALL

The CFDS is made up of the following components :

(1) The BITEs of the systems :
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.

(2) 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.

(3) The MCDUs :

CFDS - Multipurpose Control and Display Unit (MCDU)

The MCDU consists of a screen used for the display of data, an alphanumerical keyboard and lines keys for sending commands to the systems that are connected to it:

FMGC (Flight Management function)
DATA LINK (ACARS) (optional)
CFDS (Centralized Fault and Display System)
AIDS (optional)
SAT (SATCOM) (optional)
ATSU (optional).

CFDS - Interconnection with the MCDUs ** ON A/C NOT FOR ALL

The MCDUs enable the dialog with these connected systems for the display of their data or for transmitting commands to them.

Several keys are reserved for using the FMGS which is the system with priority, these keys are described in 22-82-00.

The MCDU MENU key allows the operator to select one of the systems with which he wants to dialog.

The next page key allows the display of a new page when the lenght of the text imposes the use of another page.

The alphanumerical keys allow the operator to enter data for a particular system.

The line keys allow the operator to send commands to a particular system.

As far the CFDS is concerned, it has been seen that the MCDUs allow a dialog with the CFDIU or with the BITEs of the various systems connected to the CFDIU, depending on the flight/ground conditions.

If MCDU 3 is installed (option), only MCDU 2(3) can be used for maintenance.

(4) The printer :
It is located in the cockpit, on the right section of the center pedestal.
The printer is connected to the CFDIU and serves to print reports.

(5) The ACARS (with ATSU installed):

It is an electronic system located in the avionics compartment.
Morever, the ACARS uses VHF3.
This system is connected to the CFDIU and serves to send reports to the ground.

(6) The DATA LOADER panel
The DATA LOADER panel (117VU) is located in the cockpit on the left section of the center pedestal. It is connected to the CFDIU and enables connection of a portable data loader for Maintenance filter data base uploading. Also a MDDU can be installed as an alternative to the connector for filter data base uploading.

(7) The Centralized Data Loading Connector (CDLC)
The CDLC (2TD) is located in panel 52VU in the cockpit on the overhead panel. It is connected to the CFDIU and enables connection of a Portable Data Loader (PDL) for Maintenance filter data base uploading.

(8) The Centralized Data Loading Connector (CDLC)
The CDLC (2147VC) is installed on panel 117VU in the cockpit on the center pedestal. It is connected to the CFDIU and lets you to connect a Portable Data Loader (PDL) for maintenance filter data-base-uploading.

B. System BITE Functions

(1) General

Each electrical or electronic system of the aircraft includes a fault detection, isolating and storing device called a BITE
A system consists of a set of removable components called LRUs that are specific to the system and that are said to be internal to the system.
In many cases, a system uses data from other systems that can be considered as "sensors" and that are said to be LRUs external to the system.
Example : In an autopilot, the control unit, the computers which determine the laws and the power systems are internal LRUs.
The air data and inertial reference units, the radio altimeter, ... are external LRUs.
The BITE system reacts to any fault affecting operation, whether INTERNAL or EXTERNAL to the system.
Each LRU is a component internal to a given system and no other.
Example : A pressure sensor used for several systems is taken into account as an internal component by one of these systems only.
All systems including a BITE system are connected to the CFDIU.
The systems are connected to the CFDIU by means of the system bus.
Exceptions : the FMGS via the FAC 1 and the EFCS via the FCDC use specific b uses.
The responsibility for fault detection and isolation lies with the system. The CFDS does not perform any processing and it does not modify the diagnosis made by the system.
For complex systems, one of the computers plays the role of system BITE, in other words :
it collects the maintenance data from the peripheral computers and it ensures the interface between the computers and the CFDS.

NOTE: A system BITE is supposed to analyze the data received with a view to establishing a consolidated diagnosis.

(2) BITE operating principles

The BITE is capable of memorizing, while making the distinction between internal and external faults, over a period of one or several flights (depending on the system).
The fault data memorized during the flight(s) are not affected by the various ground maintenance operations.
The BITE enables the memorization of faults in flight and on the ground, by means of different memory zones.
All LRU input buses (ARINC 429) are monitored according to the configuration of each system.
The faults are memorized following confirmation over several cycles (intermittent faults).
Faulty LRUs are identified by their ATA 100 reference and sometimes by their Functional Item Number (FIN).
The BITE permanently transmits maintenance messages in real time (in flight).
These maintenance messages cover internal and external faults of the current flight or of the last flight.

System BITEs operate in 2 modes : NORMAL MODE and MENU MODE.

(3) The various fault classes detected by the system BITEs.
The faults detected by the system BITEs are classified in 3 categories with respect to their consequences on aircraft safety and availability.

(a) Class 1 faults
These are faults detected by the systems, which may have an operational consequence (safety aspect) on the current flight.
These faults are indicated to the crew in flight:

by the ECAM system (upper and/or lower display unit)
by local warning in the cockpit.

NOTE: The FWC receives the class 1 faults from the aircraft systems which are connected to it.

(b) Class 2 faults
These are faults detected by the systems and which do not have any operational consequences (safety aspects) on the current flight or on the following flight(s) but which may have consequences if a second fault occurs.
These faults are indicated to the cockpit crew on ground by a Maintenance STATUS on the ECAM STATUS page after the engines shut down.

NOTE: The warning messages (class 1 and 2) presented to the crew are transmitted in real time by the FWC to CFDIU which memorizes them and constitutes the ECAM REPORT (only messages corresponding to primary and independent faults are transmitted).

(c) Class 3 faults
These are faults detected by the systems which have no consequences on aircraft safety or availability.
The operator may have these faults corrected at his convenience.
These faults are not indicated to the crew.

(4) Various types of systems and BITE connected to the CFDS

CFDIU - Connection With Different System Types

(a) Type 1 systems

Systems connected to CFDS with an ARINC 429 input and output bus, the input being specific to the CFDS.

These constitute the majority of aircraft systems.

Type 1 systems are capable of memorizing data concerning faults detected on a maximum of 64 flights.

Schematically, a Type 1 system BITE consists of 5 zones of non-volatile memory:

1 Zone 1

This zone is used for storing the identity of the LRU declared faulty during the current or the last flight. It is also used for storing the identity of LRUs declared faulty during the last 63 flights (background over 64 flights). The capacity is approximately 30 failures.

2 Zone 2

This zone is used for storing complementary data (e.g. : aircraft configuration, ...) concerning faults occurred during the last 64 flights. The capacity is approximately 30 failures.

3 Zone 3

This zone is used to store the identity of faulty LRUs and the complementary data concerning these fault, for faults that occurred on the ground during the last line stops. The capacity is approximately 3 failures.

Zone 3 access:

a On the center pedestal, on the MCDU, get access to the MCDU page.

b On the MCDU MENU page, push the line key adjacent to the SYSTEM REPORT/TEST indication.

c On the SYSTEM REPORT/TEST page, push the line key adjacent to the related system.

d On the SYSTEM REPORT/TEST page of the system that you have selected, push the line key adjacent to the related computer indication.

e Push the line key adjacent to the trouble shooting function indication (if the computer has this function).

4 Zone 4

This zone is used for storing more detailed data concerning the faults (parts of the LRU). This zone is only accessible in the workshop (test bench).

5 Zone 5

This zone is used for storing the identity of the LRUs affected by a class 3 fault. The capacity is approximately 400 flight hours.

Memorization of failures in these memories and transmission of these data to the CFDIU is carried out according to 2 operating modes, Normal Mode and Menu Mode.

Ref. Table below :

BITE memory structure/type 1 system

-------------------------------------------------------------------------------

! ZONE 4 ! SHOP USE ONLY ! !

!-------------------------------------------------------------! !

! ! TROUBLE ! CODED ! SNAPSHOT OF FAULTS IN ! !

! !SHOOTING ! INFOR- ! LAST 64 FLIGHTS ! !

! ZONE 2 ! DATA ! MATION ! ! INFORMATION !

! ! ! ! ! TRANSMITTED !

!--------!-----------! !-------------------------------! ON THE GROUND !

! ! ! ! SNAPSHOT OF FAULTS DETECTED ! ON REQUEST !

! ! ! ! ON THE GROUND (IF FUNCTION ! !

! ! GROUND ! ! ACTIVATED BY MENU MODE) ! !

! ! TROUBLE ! ! ! !

! ZONE 3 ! SHOOTING !--------!-------------------------------! !

! ! ! CLEAR ! FAULTS DETECTED ON THE ! !

! ! ! LAN- ! GROUND (IF FUNCTION ACTIVATED ! !

! ! ! GUAGE ! BY MENU MODE) ! !

!--------!-----------! !-------------------------------! !

! ZONE 5 ! BACK- ! ! CLASS 3 FAULTS ! !

!--------! GROUND OF ! !-------------------------------! !

! ! FAILED ! ! FAULTS IN LAST 63 FLIGHTS ! !

! ! EQUIPMENT ! !-------------------------------!---------------!

! ZONE 1 ! ! ! FAULTS IN LAST FLIGHT (OR ! INFORMATION !

! ! ! ! PRESENT FLIGHT) ! TRANSMITTED !

! ! ! ! ! PERMANENTLY !

! ! ! ! ! ON THE SYSTEM !

! ! ! ! ! BUS (GROUND !

! ! ! ! ! OR FLIGHT) !

(b) Type 2 systems

CFDIU - Connection With Different System Types

Systems interfaced to CFDS with an ARINC 429 output and a discrete input.
Type 2 systems are not capable of memorizing data concerning faults that they detect beyond the last flight.
Schematically, a Type 2 system BITE consists of 4 zones of non-volatile memory (EEPROM):

Zone 1 : This zone is used for storing the identity of the LRU declared faulty during the current or the last flight.
Zone 2 : This zone is used for storing complementary data concerning faults occurred during the current or the last flight. This zone is only accessible in the workshop.
Zone 3 : This zone is used to store the identity of faulty LRUs, for faults that occurred on the ground during the last line stop.
Zone 4 : This zone is used for storing more detailed data concerning the faults (parts of the LRU). This zone is only accessible in the workshop.

Memorization of faults in these memories and transmission of these data to the CFDIU is carried out according to a single operating mode, Normal Mode.
The input discrete is used to initialize a ground test.

Ref. Table below :

BITE memory structure/type 2 system

------------------------------------------- --- --- ---

! ! C ! ! ! ! !

! ! L ! FAULTS DETECTED ! ! IN ! O !

! ZONE 1 ! E ! DURING LAST FLIGHT ! ! ! N !

! ! A ! (OR PRESENT FLIGHT) ! ! FLIGHT ! !

! ! R ! ! ! ! ! INFORMATION

!---------! !-----------------------! --- ! G ! TRANSMITTED

! ! L ! ! ! R ! PERMANENTLY

! ! A ! ! ! O ! ON THE

! ! N ! FAULTS DETECTED ON ! ! U ! SYSTEM BUS

! ZONE 3 ! G ! THE GROUND (FUNCTION ! ! N !

! ! U ! ALWAYS ACTIVATED) ! ! D !

! ! A ! ! ! !

! ! G ! ! ! !

! ! E ! ! ! !

!-----------------!-----------------------! --- ---

! ! C ! TROUBLE SHOOTING !

! ! O ! DATA (FACULTATIVE) !

! ZONE 2 ! D ! !

! ! E ! SHOP USE ONLY !

! ! D ! !

!---------! !-----------------------!

! ! I ! !

! ! N ! !

! ! F ! !

! ! O ! !

! ! R ! !

! ZONE 4 ! M ! SHOP USE ONLY !

! ! A ! !

! ! T ! !

! ! I ! !

! ! O ! !

! ! N ! !

CFDIU - Connection With Different System Types

Systems interfaced to CFDS with discrete inputs and outputs only.
Type 3 systems are not capable of memorizing beyond the current flight.
Type 3 system BITEs do not have a memory.
Fault detection and transmission to the CFDIU is carried out by means of a single operating mode.
The input discrete is used for initializing a Ground test or Reset.

C. The Interface Unit : the CFDIU

(1) General
The CFDIU is a computer that is used as the interface between the system BITEs and the MCDUs.

(2) CFDIU operating principles
The CFDIU permanently generates maintenance phases NULL/DC2/DC1 from external data.
The CFDIU permanently memorizes in real time (to within a few seconds) the maintenance messages from the system BITEs.
The maintenance messages memorized by the CFDIU concern the internal faults detected during the current or last flight.
The CFDIU monitors all its inputs from BITEs (monitoring of the non-refreshment of buses and the state of the discretes) and memorizes a fault message in the event of non-validity of an input.
The CFDIU permanently memorizes in real time the ECAM warnings presented to the crew during the current or the last flight.
The CFDIU associates the occurrence flight phase and the occurence time (hours and minutes) with each fault memorized.
The CFDIU associates the occurrence time (hours and minutes) and the flight phase with each warning message memorized.
The CFDIU correlates each internal fault memorized with all external faults which may be a consequence of the internal fault.
The CFDIU permanently monitors and memorizes the status of the systems, in other words correct or faulty operation (using fault data transmitted by the systems or the non-refreshment of inputs).
The CFDIU establishes a fault history of the last 64 flights giving the flight counter number and the date for each flight.
The CFDIU operates in 2 modes, Normal Mode and Menu Mode.

D. The Complete System : CFDS
Operating principles
The CFDS (BITE + CFDIU) is characterized by two operating modes :
Normal Mode and Menu Mode.

E. The Complete System : CFDS - Normal Mode
Normal Mode characterizes the permanent and systematic operation in flight and on the ground of all the systems and of the CFDIU.
This mode is based on the permanent memorization in real time of fault data. This memorization takes place at 2 levels : system and CFDIU.
The characteristics of Normal Mode are the following :

Memorization at aircraft systems level :
All the systems connected to the CFDIU (types 1 and 2) memorize fault data concerning the system in the system BITE non-volatile memories.
The nature of these data depends on the flight phases and on the systems; it is described below.
These maintenance data are transmitted by the system to the CFDIU.
The nature of these data concerns the last flight and depends on the system; it is described below.
Memorization at the CFDIU level :
The CFDIU memorizes the maintenance data concerning all the aircraft systems in non-volatile memories.
The nature of the data memorized by the CFDIU concerns internal or external faults of systems.

This mode involves :

For the systems (BITE) :
. Permanent monitoring, detection and isolation of faults
. the storage in memory of maintenance data
. the permanent transmission to the CFDIU of the last flight fault messages.
For the CFDIU :
. Reading by scanning of all the buses coming from the systems
. selection and memorization of corresponding messages.

(1) Operation of Type 1 systems

CFDIU - Fault Storage "at the latest" in System BITE and Transmission to the CFDIU : Normal Mode/Type 1 Systems ** ON A/C NOT FOR ALL

CFDIU - Fault Storage "at the latest" in System BITE and Transmission to the CFDIU: Normal Mode/Type 1 Systems ** ON A/C NOT FOR ALL

CFDIU - Fault Storage "at the soonest" in System BITE and Transmission to the CFDIU : Normal Mode/Type 1 Systems ** ON A/C NOT FOR ALL

CFDIU - Fault Storage "at the soonest" in System BITE and transmission to the CFDIU: Normal Mode/Type 1 Systems ** ON A/C NOT FOR ALL

(a) Detection/memorization of faults in BITEs:
Transition to flight is defined "at the soonest" or "at the latest" depending on whether the flight number is entered by the crew before takeoff or not.

1 In flight : (maintenance phases corresponding to DC2 or DC1)

Phases corresponding to DC2:
(memorized phase = NULL confirmed over 120 s) and (engine running = running confirmed over 180 s) and ((flight phase more than or equal to 4 and less than 9) or (flight number SSM at NO and acquired flight number different from memorized flight number)).
The system BITE ensures detection and permanent memorization of its class 1 and 2 internal faults in the "flight memory" (zones 1 and 2 of the BITE) and class 3 in zone 5 of the BITE.
Phases corresponding to DC1:
(memorized phase = DC2 confirmed over 30 s).
The system BITE ensures detection and permanent memorization of its class 1 and 2 internal and external faults in the "flight memory" (zones 1 and 2) and class 3 in zone 5.

2 On the ground : (maintenance phases corresponding to NULL)
(memorized phase = DC1 or DC2) and ((flight phase more than or equal to 9b and less than 4) or (engine running = shutdown confirmed over 4 s)).
The system BITE ensures detection and permanent memorization of its class 1 and 2 internal faults in the "ground memory" (zone 3) and class 3 in zone 5.
These flight and ground faults concern the last 64 flights (or 400 flight hours for class 3).
Furthermore, the system BITE ensures permanent memorization of more detailed data concerning the faults (data at LRU parts level) in zone 4. These data are only accessible in the workshop (test bench).

(b) Transmission of these data to the CFDIU

1 In flight and on the ground:
The system BITE ensures the permanent transmission on its output bus of the part of the flight memory concerning the identity of the LRUs declared faulty (internal or external, class 1 or 2) during the current or last flight (part of zone 1).
This transmission is made on label 356 at a fixed rate of between 50 ms and 250 ms depending on the system.
The flight and ground memories are never erased on the aircraft. The part of the flight memory transmitted to the CFDIU is erased at each ground to flight transition (but it remains stored in the other parts of the memory).

(2) Operation of Type 2 systems

CFDIU - Fault Storage in System BITE and Transmission to the CFDIU : Normal Mode/Type 2 Systems ** ON A/C NOT FOR ALL

CFDIU - Fault Storage in System BITE and Transmission to the CFDIU: Normal Mode/Type 2 Systems ** ON A/C NOT FOR ALL

(a) Detection/memorization of faults in BITEs :

1 In flight :
The system BITE ensures detection and permanent memorization of its class 1, 2, and 3 internal and external faults in the flight memory (zone 1).

2 On the ground :
The system BITE ensures detection and permanent memorization of its class 1, 2 and 3 internal faults in the ground memory (zone 3).
These flight and ground faults concern the current and the last flight.
Furthermore, the system BITE ensures memorization of complementary or more detailed data of these failures in zones 2 and 4. These data are only accessible in the workshop (test bench).

(b) Transmission of these data to the CFDIU :

1 In flight and on the ground :
The system BITE ensures the permanent transmission on its output bus of the flight and ground memories contents (zones 1 and 3).
This transmission is made on label 356 at a fixed rate of between 50 ms and 250 ms depending on the system.
The flight and ground memories are erased at each ground to flight transition.

(3) Operation of Type 3 systems

(a) Detection of faults in BITE in flight and on the ground.
The system BITE ensures permanent detection of its class 1, 2 and 3 internal and external faults (no memorization).

(b) Transmission of these data to the CFDIU in flight and on the ground.
The system BITE ensures permanent transmission on its output discrete of correct or faulty operation information.

(4) CFDIU operation

CFDIU - Faults Storage "at the soonest" in CFDIU : Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU : Normal Mode ** ON A/C NOT FOR ALL

The CFDIU carries out a permanent scan of inputs from each system connected (Type 1, 2 or 3), in flight and on the ground.
However, CFDIU processing is not the same depending on whether it is performed on the ground or in flight.

(a) In flight : (maintenance phases corresponding to DC2 or DC1)

"at the soonest" for Type 1 and 3 systems - phases 2 b thru 9 a.
"at the latest" for Type 1 and 3 systems - phases 4 thru 9 a

For Type 2 systems - phases 5 a thru 7a.

1 The CFDIU establishes the CURRENT/LAST LEG REPORT.
At each scrutinization of a system input (bus or discrete), the CFDIU:

Monitors refreshment of information transmitted on the buses on each of the ARINC 429 input ports (except those which are excluded by pin programming). Non-refreshment detection is carried out by monitoring label 356 which is permanently transmitted by the subscriber systems. Non-refreshment is confirmed in 4 seconds.
Each time a non-refreshment is detected, the CFDIU associates the ATA reference and the system identity and memorizes the following internal fault message:

XX - XX - XX NO XX...X DATA

system ATA System identity coded

REFERENCE on 9 characters max.

Assignment is carried out with respect to the input port.
Furthermore the CFDIU carries out correlation of this fault (see Correlation Function below).
It detects intermittent operation of the system and adds (INTM) to the message so as to indicate that the system operates intermittently.
Example of message:

NO XXXX...X DATA (INTM)

9 char. max.

NOTE: The CFDIU does not monitor the non-refreshment of the ECB bus when it is not supplied in flight.

Acquires the fault messages and memorizes them:
* Type 1 or 2 systems
It checks the validity of the received frames (messages) prior to their memorization.
The following checks are performed:
. Delta Block Word Count of first Start of Text (STX) more than 0.
It checks that the number of words received between the first STX and the End of Transmission (EOT) is equal to the Block Word Count of the first STX.
It checks that the Block Word Count associated with the STX(s) (except the first one in the frame) is at zero.
It checks that this intermediary STX is preceded by an End of Text word (ETX).
It checks that an End of Text (ETX) is always followed by an STX.
In these conditions the message(s) corresponding to the Block Word count increase is(are) acquired and memorized.
Increase of the Block Word Count indicates that a first or a new fault has been detected by the system. The most recent fault message (the one that caused the modification of the Block Word Count) is the first message transmitted.
. Delta Block Word Count of first STX less than or equal to 0.
In this case the frame is immediately rejected and the following system is selected (polling).
. Character check
It checks that the characters composing the messages belong to the ASCII table of the MCDU characters.
It detects the nature of the fault (internal or external to the system), the class of the fault (1 & 2 or 3) and checks if it is a "FAULT DATA".
It memorizes the new class 1 or 2 internal fault message and it also memorizes the identity of the systems that reacted to the internal fault by transmitting an external fault within the minute that preceded or followed (see Correlation Function below).
* Type 3 systems
On each input discrete which is associated with the identification of a system fault, it scrutinizes discrete state so as to detect the state indicating the fault.
It associates and memorizes a text enabling identification of the anomaly at each change in discrete state.
Example : 308100 ICE DETECTOR 1
CFDIU - Example of CFDIU Operation - Type 3 System ** ON A/C NOT FOR ALL
Let us suppose that an angle of attack sensor fault has been detected and that systems A, B, C and D are affected by this fault. Systems A, B, C and D transmit EXTERNAL fault information on their bus.
The air data system transmits the INTERNAL fault information; this is the message memorized by the CFDIU.
The CFDIU also memorizes the identity of systems A, B, C and D which reacted to the air data system fault by transmitting an external fault message (correlation).
Assigns the time to each event:
For each new or the first fault occurrence memorized by the CFDIU, the latter associates the GMT (hour and minute) at which it occurred with it.
GMT is memorized with the fault identity.
Example:
GMT : 0920
315000 FWC1
In the event of several non-refreshments being detected in a given flight, only the GMT associated with the first occurrence is memorized (capacity : 40 lines of 24 characters).

2 The CFDIU establishes the CURRENT/LAST LEG ECAM REPORT.
The FWCs transmit the following information in real time on their output bus and on label 357:

The characters making up the title of the fault message displayed on the display units (lower and upper).
Example : ENG LOOP A FAULT

ATA reference (4 digits) of the system affected by the fault (the first 5 characters of the warning message are always the ATA reference).

Example : 2 6 - 1 0

! ! ! ! !

1st------- ! ! ! ---------5th

2nd------------ ! --------------4th

3rd

The informations above are sent only once, at the moment of the FWC Warning computation (wathever the flight phase display inhibition is). The warning message is limited to 24 characters.
Example of message sent by the FWC:
26-10 ENG LOOP A FAULT.

The CFDIU ensures the following functions so as to establish the ECAM REPORT:

Selection of the valid FWC bus.
Reading filtering and memorization of label 357.
Association of GMT and of the flight phase with each ECAM warning message memorized.

3 The CFDIU establishes the AVIONICS STATUS.
At each sequential scrutinization of all buses of Type 1 and 2 systems and of discretes of Type 3 systems, the CFDIU:

Monitors the non-refreshment of label 356.
After confirmation over 4 seconds, the CFDIU associates a NO X DATA message with this event, X being the identify of the system.
If the system resumes normal transmission, the message is deleted.
So the CFDIU operates in real time, to the nearest system scrutinization period.
Monitors systems status:
* Type 1 and 2 systems
The CFDIU monitors the status of bits 20 and 21 of the initial STX word of label 356 on the systems input buses.
If bit 21 is set to 1, this means that the system is currently affected by at least class 1 or 2 failure.
If bit 20 is set to 1, this means that the system is currently affected by at least class 1 or 2 failure.
The CFDIU associates the identity of the system, with respect to its input port, with bit 21 and the indication CLASS 3 with bit 20.
Example : ILS1.
If bit 21 returns to 0, the CFDIU deletes the system identity display.
* Type 3 systems
The status of Type 3 systems is given by the status of the discrete connected to the CFDIU.
The discretes are monitored regularly and the system status can be managed in real time.
The CFDIU associates system identity with each incorrect status detection (Capacity: 40 lines of 24 characters).

4 The CFDIU carries out FAULT/FAULT CORRELATION

Principle of the fault correlation function.
The purpose of the fault correlation function is to memorize in the CFDIU only one fault message for a given "aircraft fault event".
The general principle of this function is therefore to group round a single message all messages which may occur further to a given aircraft event. This single message is as near as possible to the primary fault which generated this aircraft event.

Criteria of fault correlation and application "window".
. Criterion of correlation
The criterion of correlation of the fault messages (association or exclusion) is defined by means of the ATA reference of the LRU incriminated by the message.
This reference is given by the first 2 labels 356 which follow the STX of the fault message.
As a general rule the messages are associated if their ATA reference is nearly the same, i.e.:
* in most cases, if the first 3 digits of the ATA reference are identical
* in some particular cases, if the first 4 digits of the ATA reference are identical (simple case) or if they belong to the same group of several digits (double case).

22-81
22-82
22-83
22-8N N different from 1, 2 or 3
23-11
23-12
23-13
23-1N N different from 1, 2 or 3
26-10
26-12
26-13
26-1N N different from 0, 2 or 3
27-92
27-93
27-94
27-95
27-9N N different from 2, 3, 4 or 5
31-32
31-33
31-36
31-3N N different from 2, 3 or 6
32-41
32-49
32-4N N different from 1 or 9
34-35
34-36
34-37
34-3N N different from 5, 6 or 7
34-41
34-42
34-48
34-4N N different from 1, 2 or 8
34-51
34-52
34-53
34-55
34-5N N different from 1, 2, 3 or 5
73-25
73-2N N different from 5
XX-XX + 23-13
XX-XX + 22-83
letters

. Application window
the application window of this criterion is:
* Under DC1
If a correlation window has been opened under DC1:
that window must be kept open for a minimum time of 1 minute and for a minimum of 2 scanning laps from the time of opening of the window.
when both conditions are met, then the correlation window is closed.
* Under DC2
If a correlation window has been opened under DC2:
that window must be kept open for a minimum time of 1 minute and for a minimum of 2 scanning laps from the time of DC2/DC1 maintenance phase transition.
when both conditions are met, then the correlation window is closed.

General rules of correlation processing
The starting point of fault correlation is an aircraft event.
Depending on fault confirmation time of each system and according to scanning principle of the CFDIU this aircraft event is detected in the CFDIU through reception of internal fault(s) or external fault(s), although it is not possible to know whether the internal failure will precede or follow the external fault.
* Rule No. 1 :
Any fault (internal or external and with any ATA reference) which occurs outside the duration of the correlation processing of a previous fault (internal or external and with any ATA reference) is considered as a new fault and initiates a new correlation processing.
* Rule No.2 :
Any fault (internal or external) which occurs during the correlation processing of one or several previous faults (internal or external) is considered differently, depending on its ATA reference:
. First case : the ATA reference of the fault is nearly the same that of one or several faults under processing :the fault is not considered as a new fault and is correlated with these faults under processing.
. Second case : the ATA reference of the fault is different from that of all faults under processing : the fault is considered as a new fault and initiates a new correlation processing (processing of the other faults is not interrupted).
Description of the fault correlation processing
CFDIU - Description of the Fault Correlation Processing ** ON A/C NOT FOR ALL

NOTE: An internal fault is an internal fault transmitted by a system BITE or a fault internal to the CFDIU BITE (CFDIU/CLOCK/MCDU3) or a non-refreshment of label 356 detected by the CFDIU. An external fault is an external fault transmitted by a system BITE. For faults internal to the CFDIU BITE the source/identifier of the fault is CFDS.

NOTE: A given system can be source/identifier only once. Particularly, if several external faults are transmitted by a given system during a correlation processing, this system is mentioned as identifier only once.

NOTE: - For a given fault, the number of identifiers is limited to 6 (1 page).
- For the totality of faults occurred in flight the number of identifiers is limited to 200.

NOTE: The number of simultaneous correlation processings is limited to 8. If a 9th fault occurs, the processing of the first fault is arbitrarily stopped.

Transmission to the ACARS (if installed)
The identifiers are sent to the ACARS together with the fault message, in real time. They are also transmitted on transmission of the complete POST FLIGHT REPORT.

5 The CFDIU establishes the PREVIOUS LEGS REPORT.

Memorization of maintenance information.
The CFDIU transfers and stores the complete LAST LEG REPORT in the PREVIOUS LEGS REPORT at DC1/NULL transition.
The CFDIU can memorize up to 200 fault data over 64 flights.
The faults prior to the last 64 flights are deleted. Only flights with at least one fault appear in the PREVIOUS LEGS REPORT.
Flight leg identification.
The CFDIU associates the data below with the maintenance information so that maintenance personnel can clearly identify the flight concerned:
. The flight count (generated by the CFDIU). LEG -00 coresponds to the last flight. It is identical to the LAST LEG REPORT.
Example : LEG -13
. The flight date (emitted by the CLOCK or generated by the CFDIU, using label 260).
. Aircraft identification (emitted by the FDIU using labels 301, 302, 303 and 304).

The CITY PAIR (FROM TO) (emitted by the FMS using labels 040, 041 and 042 transmitted by the FAC) used by the printer only.

(b) On the ground
At each scrutinization of a system input, the CFDIU monitors refreshment of the fault information transmitted on the bus (see description in flight) ; it does not memorize a fault message.
This monitoring is only used for determining the status of aircraft systems at any moment and for establishing the AVIONICS STATUS.

(5) CFDIU operation

CFDIU - Faults Storage "at the soonest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

The CFDIU carries out a permanent scan of inputs from each system connected (Type 1, 2 or 3), in flight and on the ground.

However, CFDIU processing is not the same depending on whether it is performed on the ground or in flight.

(a) In flight : (maintenance phases corresponding to DC2 or DC1)

"at the soonest" for Type 1 and 3 systems - phases 2 b thru 9 a.
"at the latest" for Type 1 and 3 systems - phases 4 thru 9 a

For Type 2 systems - phases 5 a thru 7a.

1 The CFDIU establishes the CURRENT/LAST LEG REPORT.

At each scrutinization of a system input (bus or discrete), the CFDIU:

Monitors refreshment of information transmitted on the buses on each of the ARINC 429 input ports (except those which are excluded by pin programming). Non-refreshment detection is carried out by monitoring label 356 which is permanently transmitted by the subscriber systems. Non-refreshment is confirmed in 4 seconds.

Each time a non-refreshment is detected, the CFDIU associates the ATA reference and the system identity and memorizes the following internal fault message:

XX - XX - XX NO XX...X DATA

system ATA System identity coded

REFERENCE on 9 characters max.

Assignment is carried out with respect to the input port.

Furthermore the CFDIU carries out correlation of this fault (see Correlation Function below).

It detects intermittent operation of the system and adds (INTM) to the message so as to indicate that the system operates intermittently.

Example of message:

NO XXXX...X DATA (INTM)

9 char. max.

NOTE: The CFDIU does not monitor the non-refreshment of the ECB bus when it is not supplied in flight.

Acquires the fault messages and memorizes them:

* Type 1 or 2 systems
It checks the validity of the received frames (messages) prior to their memorization.
The following checks are performed:
. Delta Block Word Count of first Start of Text (STX) more than 0.
It checks that the number of words received between the first STX and the End of Transmission (EOT) is equal to the Block Word Count of the first STX.
It checks that the Block Word Count associated with the STX(s) (except the first one in the frame) is at zero.
It checks that this intermediary STX is preceded by an End of Text word (ETX).
It checks that an End of Text (ETX) is always followed by an STX.
In these conditions the message(s) corresponding to the Block Word count increase is(are) acquired and memorized.
Increase of the Block Word Count indicates that a first or a new fault has been detected by the system. The most recent fault message (the one that caused the modification of the Block Word Count) is the first message transmitted.
. Delta Block Word Count of first STX less than or equal to 0.
In this case the frame is immediately rejected and the following system is selected (polling).
. Character check
It checks that the characters composing the messages belong to the ASCII table of the MCDU characters.
It detects the nature of the fault (internal or external to the system), the class of the fault (1 & 2 or 3) and checks if it is a "FAULT DATA".
It memorizes the new class 1 or 2 internal fault message and it also memorizes the identity of the systems that reacted to the internal fault by transmitting an external fault within the minute that preceded or followed (see Correlation Function below).
* Type 3 systems
On each input discrete which is associated with the identification of a system fault, it scrutinizes discrete state so as to detect the state indicating the fault.
It associates and memorizes a text enabling identification of the anomaly at each change in discrete state.
Example : 308100 ICE DETECTOR 1
CFDIU - Example of CFDIU Operation - Type 3 System ** ON A/C NOT FOR ALL
Let us suppose that an angle of attack sensor fault has been detected and that systems A, B, C and D are affected by this fault. Systems A, B, C and D transmit EXTERNAL fault information on their bus.
The air data system transmits the INTERNAL fault information; this is the message memorized by the CFDIU.
The CFDIU also memorizes the identity of systems A, B, C and D which reacted to the air data system fault by transmitting an external fault message (correlation).
Assigns the time to each event:
For each new or the first fault occurrence memorized by the CFDIU, the latter associates the GMT (hour and minute) at which it occurred with it.
GMT is memorized with the fault identity.
Example:
GMT : 0920
315000 FWC1
In the event of several non-refreshments being detected in a given flight, only the GMT associated with the first occurrence is memorized (capacity : 40 lines of 24 characters).

2 The CFDIU establishes the CURRENT/LAST LEG ECAM REPORT.
The FWCs transmit the following information in real time on their output bus and on label 357:

The characters making up the title of the fault message displayed on the display units (lower and upper).
Example : ENG LOOP A FAULT

ATA reference (4 digits) of the system affected by the fault (the first 5 characters of the warning message are always the ATA reference).

Example : 2 6 - 1 0

! ! ! ! !

1st------- ! ! ! ---------5th

2nd------------ ! --------------4th

3rd

The CFDIU ensures the following functions so as to establish the ECAM REPORT:

Selection of the valid FWC bus.
Reading filtering and memorization of label 357.
Association of GMT and of the flight phase with each ECAM warning message memorized.

3 The CFDIU establishes the AVIONICS STATUS.
At each sequential scrutinization of all buses of Type 1 and 2 systems and of discretes of Type 3 systems, the CFDIU:

Monitors the non-refreshment of label 356.
After confirmation over 4 seconds, the CFDIU associates a NO X DATA message with this event, X being the identify of the system.
If the system resumes normal transmission, the message is deleted.
So the CFDIU operates in real time, to the nearest system scrutinization period.
Monitors systems status:
* Type 1 and 2 systems
The CFDIU monitors the status of bits 20 and 21 of the initial STX word of label 356 on the systems input buses.
If bit 21 is set to 1, this means that the system is currently affected by at least a class 1 or 2 failure.
If bit 20 is set to 1, this means that the system is currently affected by a class 3 fault.
The CFDIU associates the identity of the system, with respect to its input port, with bit 21 and the indication CLASS 3 with bit 20.
Example : ILS1.
If bit 21 returns to 0, the CFDIU deletes the system identity display.
* Type 3 systems
The status of Type 3 systems is given by the status of the discrete connected to the CFDIU.
The discretes are monitored regularly and the system status can be managed in real time.
The CFDIU associates system identity with each incorrect status detection (Capacity: 40 lines of 24 characters).

4 The CFDIU carries out FAULT/FAULT CORRELATION

Principle of the fault correlation function.
The purpose of the fault correlation function is to memorize in the CFDIU only one fault message for a given "aircraft fault event".
The general principle of this function is therefore to group round a single message all messages which may occur further to a given aircraft event. This single message is as near as possible to the primary fault which generated this aircraft event.

22-81
22-82
22-83
22-8N N different from 1, 2 or 3
23-11
23-12
23-13
23-1N N different from 1, 2 or 3
26-10
26-12
26-13
26-1N N different from 0, 2 or 3
27-92
27-93
27-94
27-95
27-9N N different from 2, 3, 4 or 5
31-32
31-33
31-36
31-3N N different from 2, 3 or 6
32-41
32-49
32-4N N different from 1 or 9
34-35
34-36
34-37
34-3N N different from 5, 6 or 7
34-41
34-42
34-48
34-4N N different from 1, 2 or 8
34-51
34-52
34-53
34-55
34-5N N different from 1, 2, 3 or 5
73-25
73-2N N different from 5
XX-XX + 23-13
XX-XX + 22-83
23-2X-XX + 46-2X-XX
letters

General rules of correlation processing
The starting point of fault correlation is an aircraft event.
Depending on fault confirmation time of each system and according to scanning principle of the CFDIU this aircraft event is detected in the CFDIU through reception of internal fault(s) or external fault(s), although it is not possible to know whether the internal failure will precede or follow the external fault.
* Rule No. 1 :
Any fault (internal or external and with any ATA reference) which occurs outside the duration of the correlation processing of a previous fault (internal or external and with any ATA reference) is considered as a new fault and initiates a new correlation processing.
* Rule No.2 :
Any fault (internal or external) which occurs during the correlation processing of one or several previous faults (internal or external) is considered differently, depending on its ATA reference:
. First case : the ATA reference of the fault is nearly the same that of one or several faults under processing :the fault is not considered as a new fault and is correlated with these faults under processing.
. Second case : the ATA reference of the fault is different from that of all faults under processing : the fault is considered as a new fault and initiates a new correlation processing (processing of the other faults is not interrupted).
Description of the fault correlation processing
CFDIU - Description of the Fault Correlation Processing ** ON A/C NOT FOR ALL

NOTE: - For a given fault, the number of identifiers is limited to 6 (1 page).
- For the totality of faults occurred in flight the number of identifiers is limited to 200.

NOTE: The number of simultaneous correlation processings is limited to 8. If a 9th fault occurs, the processing of the first fault is arbitrarily stopped.

Transmission to the ACARS (if installed)
The identifiers are sent to the ACARS together with the fault message, in real time. They are also transmitted on transmission of the complete POST FLIGHT REPORT.

5 The CFDIU establishes the PREVIOUS LEGS REPORT.

Memorization of maintenance information.
The CFDIU transfers and stores the complete LAST LEG REPORT in the PREVIOUS LEGS REPORT at DC1/NULL transition.
The CFDIU can memorize up to 200 fault data over 64 flights.
The faults prior to the last 64 flights are deleted. Only flights with at least one fault appear in the PREVIOUS LEGS REPORT.
Flight leg identification.
The CFDIU associates the data below with the maintenance information so that maintenance personnel can clearly identify the flight concerned:
. The flight count (generated by the CFDIU). LEG -00 coresponds to the last flight. It is identical to the LAST LEG REPORT.
Example : LEG -13
. The flight date (emitted by the CLOCK or generated by the CFDIU, using label 260).
. Aircraft identification (emitted by the FDIU using labels 301, 302, 303 and 304).

The CITY PAIR (FROM TO) (emitted by the FMS using labels 040, 041 and 042 transmitted by the FAC) used by the printer only.

(6) CFDIU operation

CFDIU - Faults Storage "at the soonest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

The CFDIU carries out a permanent scan of inputs from each system connected (Type 1, 2 or 3) in flight and on the ground.

However, CFDIU processing is not the same depending on whether it is performed in flight or on the ground.

(a) In flight (maintenance phases corresponding to DC2 or DC1)

For Type 1 and 3 systems:

Phases 2 b through 9 a - "at the soonest"
Phases 4 through 9 a - "at the latest".

For Type 2 systems - phases 5 a through 7 a.

1 The CFDIU establishes the CURRENT/LAST LEG REPORT.

At each scrutinization of a system input (bus or discrete), the CFDIU:

Monitors refreshment of information transmitted to the buses on each of the ARINC 429 input ports (except those which are excluded by pin programming). Non-refreshment detection is carried out by monitoring label 356 which is permanently transmitted by the subscriber systems. Non-refreshment is confirmed in 4 seconds.

Each time a non-refreshment is detected, the CFDIU associates the ATA reference and the system identity and memorizes the internal fault message.
Example:

XX - XX - XX NO XX...X DATA

System ATA System identity coded

REFERENCE on 9 characters max.

Assignment is carried out with respect to the input port.

Furthermore the CFDIU carries out correlation of this fault (see Correlation Function below).

It detects intermittent operation of the system and adds (INTM) to the message so as to indicate that the system operates intermittently.
Example of message:

NO XXXX...X DATA (INTM)

9 char. max.

NOTE: The CFDIU does not monitor the non-refreshment of the ECB bus when it is not supplied in flight.

Acquires the fault messages and memorizes them.

* Type 1 or 2 systems
It checks the validity of the received frames (messages) prior to their memorization.

The following checks are performed:
. Delta Block Word Count of first Start of Text (STX) more than 0.
It checks that the number of words received between the first STX and the End of Transmission (EOT) is equal to the Block Word Count of the first STX.
It checks that the Block Word Count associated with the STX(s) (except the first one in the frame) is at 0.
It checks that this intermediary STX is preceded by an End of Text (ETX) word.
It checks that an ETX is always followed by an STX.
In these conditions, the message(s) corresponding to the Block Word count increase is(are) acquired and memorized.
Increase of the Block Word Count indicates that a first or a new fault has been detected by the system. The most recent fault message (the one that caused the modification of the Block Word Count) is the first message transmitted.
. Delta Block Word Count of first STX less than or equal to 0.
In this case the frame is immediately rejected and the following system is selected (polling).
. Character check
It checks that the characters composing the messages belong to the ASCII table of the MCDU characters.
It detects the nature of the fault (internal or external to the system), the class of the fault (1 & 2 or 3) and checks if it is a "FAULT DATA".
It memorizes the new class 1 or 2 internal fault message and also the identity of the systems that reacted to the internal fault, by transmitting an external fault within the minute that preceded or followed (see Correlation Function below).

* Type 3 systems
On each input discrete which is associated with the identification of a system fault, it scrutinizes discrete state so as to detect the state indicating the fault.
It associates and memorizes a text enabling identification of the anomaly at each change in discrete state.
Example : 308100 ICE DETECTOR 1
CFDIU - Example of CFDIU Operation - Type 3 System ** ON A/C NOT FOR ALL
Let us suppose that an angle of attack sensor fault has been detected and that systems A, B, C and D are affected by this fault. Systems A, B, C and D transmit EXTERNAL fault information to their bus.
The air data system transmits the INTERNAL fault information. This is the message memorized by the CFDIU.
The CFDIU also memorizes the identity of systems A, B, C and D which reacted to the air data system fault by transmitting an external fault message (correlation).
Assigns the time to each event.

For each new or the first fault occurrence memorized by the CFDIU, the CFDIU associates the GMT (hour and minute) at which the fault occurred with it.
GMT is memorized with the fault identity.
Example:
GMT : 0920
315000 FWC1
In the event of several non-refreshments being detected in a given flight, only the GMT associated with the first occurrence is memorized (capacity : 40 lines of 24 characters).

2 The CFDIU establishes the CURRENT/LAST LEG ECAM REPORT.

The FWCs transmit the following information in real time to their output bus and to label 357:

ATA reference (4 digits) of the system affected by the fault (the first 5 characters of the warning message are always the ATA reference).

Example : 2 6 - 1 0

! ! ! ! !

1st------- ! ! ! ---------5th

2nd------------ ! --------------4th

3rd

The characters making up the title of the fault message displayed on the display units (lower and upper).
Example : ENG LOOP A FAULT

The information above are sent only once, at the moment of the FWC Warning computation (irrespective of the flight phase display inhibition). The warning message is limited to 24 characters.
Example of a message sent by the FWC:
26-10 ENG LOOP A FAULT.

The CFDIU ensures the following functions so as to establish the ECAM REPORT:

Selection of the valid FWC bus.
Reading, filtering and memorization of label 357.
Association of GMT and of the flight phase with each ECAM warning message memorized.

3 The CFDIU establishes the AVIONICS STATUS.

At each sequential scrutinization of all buses of Type 1 and 2 systems and of discretes of Type 3 systems, the CFDIU:

Monitors the non-refreshment of label 356.
After confirmation over 4 seconds, the CFDIU associates a NO X DATA message with this event, X being the identity of the system.
If the system resumes normal transmission, the message is deleted.
So the CFDIU operates in real time, to the nearest system scrutinization period.
Monitors system status.
* Type 1 and 2 systems
The CFDIU monitors the status of bits 20 and 21 of the initial STX word of label 356 on the systems input buses.
If bit 21 is set to 1, this means that the system is currently affected by at least a class 1 or 2 failure.
If bit 20 is set to 1, this means that the system is currently affected by a class 3 fault.
The CFDIU associates the identity of the system, with respect to its input port, with bit 21 and the indication CLASS 3 with bit 20.
Example : ILS1.
If bit 21 returns to 0, the CFDIU deletes the system identity display.

* Type 3 systems
The status of Type 3 systems is given by the status of the discrete connected to the CFDIU.
The discretes are monitored regularly and the system status can be managed in real time.
The CFDIU associates system identity with each incorrect status detection (Capacity: 40 lines of 24 characters).

4 The CFDIU carries out FAULT/FAULT CORRELATION.

Principle of the fault correlation function.
The purpose of the fault correlation function in the CFDIU is to memorize only one fault message for a given "aircraft fault event".
The general principle of this function is to group all the messages around a single message which may occur further to a given aircraft event. This single message is as near as possible to the primary fault which generated this aircraft event.

Criteria of the fault correlation and the application "window".

The criteria of the fault correlation (association or exclusion) is defined by means of the ATA reference of the LRU incriminated by the message.
This reference is given by the first 2 labels 356 which follow the STX of the fault message.
As a general rule, the messages are associated if their ATA reference is nearly the same.
For Example:
* In most cases, if the first 3 digits of the ATA reference are identical.
* In some particular cases, if the first 4 digits of the ATA reference are identical (simple case) or if they belong to the same group of several digits (double case).

22-81
22-82
22-83
22-8N N different from 1, 2 or 3
23-11
23-12
23-13
23-1N N different from 1, 2 or 3
26-10
26-12
26-13
26-1N N different from 0, 2 or 3
27-92
27-93
27-94
27-95
27-9N N different from 2, 3, 4 or 5
31-32
31-33
31-36
31-3N N different from 2, 3 or 6
32-41
32-49
32-4N N different from 1 or 9
34-35
34-36
34-37
34-3N N different from 5, 6 or 7
34-41
34-42
34-48
34-4N N different from 1, 2 or 8
34-51
34-52
34-53
34-55
34-5N N different from 1, 2, 3 or 5
73-25
73-2N N different from 5
XX-XX + 23-13
XX-XX + 22-83
23-2X-XX + 46-2X-XX
letters

The criteria of the application "window" is:
* If a correlation window has been opened under DC1.
That window must be kept open for a minimum of 1 minute and 2 scanning laps from the time of opening of the window.
When both the conditions are met, then the correlation window is closed.

* If a correlation window has been opened under DC2.
That window must be kept open for a minimum of 1 minute and 2 scanning laps from the time of DC2/DC1 maintenance phase transition.
When both the conditions are met, then the correlation window is closed.

General rules of correlation processing
The starting point of the fault correlation is an aircraft event.
Depending on the fault confirmation time of each system and according to the scanning principle of the CFDIU, this aircraft event is detected in the CFDIU through reception of internal fault(s) or external fault(s), although it is not possible to know whether the internal failure will precede or follow the external fault.
* Rule No. 1:
Any fault (internal or external and with any ATA reference) which occurs outside the duration of the correlation processing of a previous fault (internal or external and with any ATA reference) is considered as a new fault and initiates a new correlation processing.
* Rule No.2:
Any fault (internal or external) which occurs during the correlation processing of one or several previous faults (internal or external), is considered differently depending on its ATA reference.
When the ATA reference of the fault is nearly the same as that of one or several faults under processing, then the fault is not considered as a new fault and is correlated with these faults under processing.
When the ATA reference of the fault is different from that of all the faults under processing, then the fault is considered as a new fault and initiates a new correlation processing (processing of the other faults is not interrupted).
Description of the fault correlation processing
CFDIU - Description of the Fault Correlation Processing ** ON A/C NOT FOR ALL

NOTE: An internal fault is a fault transmitted by a system BITE or a fault internal to the CFDIU BITE (CFDIU/CLOCK/MCDU3) or a non-refreshment of label 356 detected by the CFDIU. An external fault is a fault transmitted by a system BITE. For faults internal to the CFDIU BITE or external faults (non-refreshment of label 356), the source/identifier of the fault is CFDS.

NOTE: For a given fault, the number of identifiers is limited to 6 (1 page). For the totality of faults occurred in flight, the number of identifiers is limited to 200.

NOTE: The number of simultaneous correlation processing is limited to 8. If a 9th fault occurs, the processing of the first fault is arbitrarily stopped.

Transmission to the ACARS (if installed)
The identifiers are sent to the ACARS together with the fault message, in real time. They are also transmitted to the transmission of the complete POST FLIGHT REPORT.

5 The CFDIU carries out a Warning/Failure correlation.

Principle of the Warning/Failure correlation function
The aim of this function is to determine whether warnings acquired during a flight could be correlated with failures acquired during the same flight. This function takes into account Last Leg Report (LLR) failures (enriched and correlated) and Last Leg ECAM Report (LLER).
If the GMT is acquired with a SSM different from NO, failures and warnings are enriched with a GMT equal to 7999. Those failures and warnings are not taken into account for the warning/failure correlation.
Each warning can be correlated to one failure at the most.
Each failure can be correlated to one warning at the most.
The warning/failure 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 warnings have been processed.
* After 2 minutes of CFDIU processing this function.
* At NULL/DC2 transition.
Rules of the Warning/Failure correlation function
For each warning, a failure could be associated to it if the GMT failure is within GMT warning +/- 2 minutes and if one of these conditions is true:
* The first four ATA digits of the failure message are equal to the first four ATA digits of the warning or are in the following list
* The first four ATA digits of the failure source are equal to the first four ATA digits of the warning or are in the following list
* The first four ATA digits of one of the failure identifiers are equal to the first four ATA digits of the warning or are in the following list.

-----------------------------

! WARNING ATA ! FAILURE ATA !

!-------------!-------------!

! 23-73 ! 26-17 !

!-------------!-------------!

! 23-73 ! 38-31 !

!-------------!-------------!

! 23-24 ! 46-21 !

!-------------!-------------!

! 26-10 ! 26-12 !

!-------------!-------------!

! 32-41 ! 32-49 !

For the remaining warnings, a second rule applies to correlate them to failures. For each of them, a failure could be associated if the GMT failure is within GMT warning +/- 2 minutes and if one of these conditions is true:
* The first two ATA digits of the failure message are equal to the first two ATA digits of the warning.
* The first two ATA digits of the failure source are equal to the first two ATA digits of the warning.
* The first two ATA digits of one of the failure identifiers are equal to the first two ATA digits of the warning.
* Except if the ATA numbers (failure message or warning message or source or identifier) are in the following list.

---------------------------------------------------

! WARNING OR FAILURE ATA !

---------------------------------------------------

! 22-81 ! 22-82 ! 22-83 ! 23-11 ! 23-12 !

---------------------------------------------------

! 23-13 ! 26-13 ! 27-92 ! 27-93 ! 27-94 !

---------------------------------------------------

! 27-95 ! 31-32 ! 31-33 ! 31-36 ! 34-35 !

---------------------------------------------------

! 34-36 ! 34-37 ! 34-41 ! 34-42 ! 34-48 !

---------------------------------------------------

! 34-51 ! 34-52 ! 34-53 ! 34-55 ! 73-25 !

Result presentation of Warning/Failure correlation

Warning/Fault Correlation Results ** ON A/C NOT FOR ALL

Warning/Fault correlation results are available on the CFDS main page, through the Last Leg Report (LLR) or the Last Leg ECAM Report (LLER) menus.

* Last Leg Report (LLR)
On the CFDS main menu, when the Line Select Key (LSK) adjacent to the LAST LEG REPORT is pressed, the CFDIU displays the content of the LLR. If a warning is correlated to a fault, a prompt (">") is shown on the right side of the corresponding fault.
Then, if the MCDU LSK corresponding to one of the prompts is pressed, the CFDIU displays the correlated warning.
If the MCDU LSK 1R is pressed, the CFDIU will display the correlated warning associated to the 1st fault.
If the MCDU LSK 2R is pressed, the CFDIU will display the correlated warning associated to the 2nd fault.
The level of detail of the correlated warning is the same as those of the LLER (hour, flight phase, ATA and warning message), but only the correlated warning is shown.
If the operator selects '<RETURN', the CFDIU displays the LLR page.

* Last Leg ECAM Report (LLER)
On the CFDS main menu, when the LSK adjacent to the LAST LEG ECAM REPORT is pressed, the CFDIU displays the content of the LLER. If a fault is correlated to a wiring, a prompt (">") is shown on the right side of the corresponding warning.
Then, if the MCDU LSK corresponding to one of the prompts is pressed, the CFDIU displays the correlated fault.
If the MCDU LSK 1R is pressed, the CFDIU will display the correlated fault associated to the 1st warning.
If the MCDU LSK 2R is pressed, the CFDIU will display the correlated fault associated to the 2nd warning.
The level of detail of the correlated fault is the same as that of the LLR sub page (hour, flight phase, ATA, fault message, source and identifiers).
If the operator selects '<RETURN', the CFDIU displays the LLER page.
Display and transmission means of Warning/Failure correlation
Warning/Failure correlation results are only available on the MCDU and cannot be printed or sent to the ground station. Also, they are not memorized.

6 The CFDIU establishes the PREVIOUS LEGS REPORT.

Memorization of the maintenance information.
The CFDIU transfers and stores the complete LAST LEG REPORT in the PREVIOUS LEGS REPORT at DC1/NULL transition.
The CFDIU can memorize up to 200 fault data over 64 flights.
The faults prior to the last 64 flights are deleted. Only flights with at least one fault appear in the PREVIOUS LEGS REPORT.
Flight leg identification.
The CFDIU associates the data below with the maintenance information so that the maintenance personnel can clearly identify the concerned flight:
. The flight count (generated by the CFDIU) corresponds to the last flight. It is identical to the LAST LEG REPORT.
Example : LEG -13
. The flight date (emitted by the CLOCK or generated by the CFDIU, using label 260).
. Aircraft identification (emitted by the FDIU using labels 301, 302, 303 and 304).
. The CITY PAIR (FROM TO) (emitted by the FMS using labels 040, 041 and 042 transmitted by the FAC) used by the printer only.

(b) On the ground

At each scrutinization of a system input, the CFDIU monitors refreshment of the fault information transmitted to the bus (see description in flight). It does not memorize a fault message.
This monitoring is only used for determining the status of aircraft systems at any moment and for establishing the AVIONICS STATUS.

(7) CFDIU operation

CFDIU - Faults Storage "at the soonest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

The CFDIU does a permanent scan of the inputs from each connected system (Type 1, 2 or 3) in flight and on the ground.

But the CFDIU processing is not the same on the ground and in flight.

(a) In flight (maintenance phases related to DC2 or DC1)

"At the soonest" for the Type-1 and Type-3 systems - Phases 2b thru 9a
"At the latest" for the Type-1 and Type-3 systems - Phases 4 thru 9a.

For the Type-2 systems - Phases 5a thru 7a.

1 The CFDIU gives the CURRENT/LAST LEG REPORT.

Each time there is a scan of a system input (bus or discrete):

"The CFDIU monitors the update of the information transmitted on the buses on each ARINC 429 input port that is included by pin-programming.
Monitoring label 356 finds if the transmitted information is not updated and shows it in four seconds. The subscriber systems permanently transmit monitoring label 356.

Each time monitoring label 356 finds that the transmitted information is not updated, the CFDIU:
Gives the ATA reference and the system name

Keeps this internal fault message in memory:

XX - XX - XX NO XX...X DATA

system ATA System identity coded

REFERENCE on 9 characters max.

The message is given in relation to the input port.

The CFDIU also gives the correlation of this fault (refer to the Correlation Function that follows).

The CFDIU finds each intermittent operation of the system. The CFDIU adds (INTM) to the message to show that the system operates intermittently.

Example of this message:

NO XXXX...X DATA (INTM)

9 characters maximum

NOTE: The CFDIU does not monitor the ECB bus to make sure that there is an update of the transmitted information when it is not supplied in flight.

The CFDIU gets the fault messages and keeps them in memory:

* Type-1 or Type-2 system:
The CFDIU makes sure that the received frames (messages) are correct before it keeps them in memory.
The CFDIU does the checks that follow:
. The Delta Block Word Count of the first Start of Text (STX) that is more than 0:
The CFDIU makes sure that the number of words received between the first STX and the End of Transmission (EOT) is equal to the Block Word Count of the first STX.
The CFDIU ignores the first Block Word Count in the frame. The CFDIU makes sure that the next Block Word Count related to the STX(s) is set to zero.
The CFDIU makes sure that an End of Text (ETX) word is shown before this first STX.
It makes sure that an STX always follows an ETX.
In these conditions, the CFDIU gets and keeps in memory the message(s) related to the Block Word Count that increases.
When the Block Word Count increases, this shows that the system found a first or a new fault. The last fault message that is received (the one that caused the change of the Block Word Count) is the first message transmitted.
. The Delta Block Word Count of the first STX less than or equal to zero:
In this condition, the frame is immediately rejected and the next system is selected (polling).
. The character check:
The CFDIU makes sure that the characters in the messages are included in the American Standard Code for Information Interchange (ASCII) table of the Multipurpose Control & Display Unit (MCDU) characters.
The CFDIU finds the type of the fault (internal or external to the system) and the class of the fault (1 and 2 or 3). It also examines if it is a "FAULT DATA".
The CFDIU keeps in memory the new class-1 or class-2 internal fault message. The CFDIU also keeps in memory the name of the systems that transmit an external fault in relation to this internal fault. The transmission of the external fault occurs in the minute before or after the internal fault is found (refer to the Correlation Function that follows).
* Type-3 systems:
On each discrete input related to the identification of a system fault, the CFDIU does a scan of the discrete state. The CFDIU gives and keeps in memory a message that causes the identification of the fault at each change that occurs in a discrete state.
Example: 308100 ICE DETECTOR 1
CFDIU - Example of CFDIU Operation - Type 3 System ** ON A/C NOT FOR ALL
This message is shown if an Angle Of Attack (AOA) sensor fault is found and has an effect on systems A, B, C and D. Systems A, B, C and D transmit the EXTERNAL fault information on their bus.
The Air Data System (ADS) transmits the INTERNAL fault information. This information is the message that the CFDIU keeps in memory.
The CFDIU also keeps in memory the name of the systems (A, B, C and D) that transmit an external fault message in relation to the fault of the air data system (correlation).
The CFDIU gives the time for each message:
Each time a new fault is found or a first fault is kept in memory, the CFDIU gives the related Greenwich Mean Time (GMT) (hours and minutes).
The GMT is kept in memory with the fault name.
Example:
GMT : 0920
315000 FWC1
If the CFDIU finds that there is no update in some messages in a given flight, only the GMT related to the first message is kept in memory (capacity: 40 lines of 24 characters).

2 The CFDIU gives the CURRENT/LAST LEG ECAM REPORT.
The Flight Warning Computers (FWC) transmit this information in real time on their output bus and on label 357:

The characters that make the title of the fault message shown on the display units (lower and top)
Example: ENG LOOP A FAULT

The ATA reference (4 digits) of the system related to the fault (the first five characters of the warning message are always the ATA reference).

Example: 2 6 - 1 0

! ! ! ! !

1st------- ! ! ! ---------5th

2nd------------ ! --------------4th

3rd

This information is sent only one time, when the FWC warning is computed (the flight phase display-inhibition has no effect on this transmission). The warning message has a maximum of 24 characters.
Example of a message from the FWC:
26-10 ENG LOOP A FAULT.

The CFDIU operates these functions to give the ECAM REPORT:

The selection of the correct FWC bus
The reading filter and memory of label 357
The relation between the GMT and the flight phase for each ECAM warning message kept in memory.

3 The CFDIU gives the AVIONICS STATUS.
Each time there is a sequential scan of:

All the buses of the Type-1 and Type-2 systems, and
All the discretes of the Type-3 systems:

a The CFDIU monitors label 356 to make sure that its updates are correct.
After four seconds, the CFDIU makes the relation between a NO X DATA message and this condition (where X is the name of the system).
If the system is back to a normal transmission, the message is erased.
The CFDIU operates in real time, in the shortest time after the system scan period.

b Monitors the status of the systems:
* Type-1 and Type-2 systems
The CFDIU monitors the status of bits 20 and 21 of the initial STX word of label 356 on the system input buses.
If bit 21 is set to 1, this shows that, to the minimum, a class-1 or class-2 fault has an effect on the system.
If bit 20 is set to 1, this shows that a class-3 fault has an effect on the system.
The CFDIU makes the relation between:

The name of the system, in relation to its input port, and bit 21
Indication CLASS 3 and bit 20.
Example: ILS1.
If bit 21 is back to 0, the CFDIU erases the system name display.
* Type-3 systems:
The status of the discrete connected to the CFDIU gives the status of the Type-3 systems.
The discretes are monitored regularly and it is possible to manage the system status in real time.
The CFDIU makes a relation between the system name and each status that is found incorrect (capacity: 40 lines of 24 characters).

4 The CFDIU operates the FAULT/FAULT CORRELATION:

Fault correlation function:
With the fault correlation function, only one fault message for a given "aircraft fault event" is kept in memory in the CFDIU.
Thus, the general principle of this function is to collect, for one message, all the messages that can occur after a given aircraft event. This message is as near as possible to the primary fault that caused this aircraft event.

Fault correlation criteria and application "window":
. Criterion of correlation:
The criterion of correlation of the fault messages (relation or exclusion) is given by the ATA reference of the Line Replaceable Unit (LRU) related to the message.
This reference is given by the first two labels 356 that follow the STX of the fault message.
The messages are usually related if their ATA references are almost the same:
* Usually, if the first three digits of the ATA references are the same
* In special conditions, if the first four digits of the ATA references are the same (simple condition) or if they are from the same group of digits (double condition).

22-81
22-82
22-8N N different from 1, 2 or 3
23-11
23-12
23-13
23-1N N different from 1, 2 or 3
23-51 Only if RAIMS is "installed"
23-52 Only if RAIMS is "installed"
23-5N N different from 1, 2 only if RAIMS is "installed"
26-12 + 26-10
26-13
26-1N N different from 0, 2 or 3 (only if the aircraft configuration
includes CIDS configuration 1 or 2)
26-1N N different from 0, 2 or 3 and 2373 (only if the aircraft
configuration includes CIDS configuration 3)
27-92
27-93
27-94
27-95
27-9N N different from 2, 3, 4 or 5
31-32
31-33
31-36
31-3N N different from 2, 3 or 6
32-41
32-49
32-4N N different from 1 or 9
34-35
34-36
34-37
34-3N N different from 5, 6 or 7
34-41
34-42
34-48
34-4N N different from 1, 2 or 8
34-51
34-52
34-53
34-55
34-5N N different from 1, 2, 3 or 5
73-25
73-2N N different from 5
23-2X-XX + 46-2X-XX
XXXX + 23-13
23-73 + 38-31 (only if a new CIDS is installed)
letters

. Application window
The application window of this criterion is:
* With DC1
If you open a correlation window with DC1, you must keep this window open for a minimum of:

One minute
Two scanning cycles from the time you opened the window.

When these conditions are satisfactory, then the correlation window closes.
* With DC2
If you open a correlation window with DC2, you must keep this window open for a minimum of:

One minute
Two scanning cycles from the time of the DC2/DC1 maintenance-phase transition.

When these conditions are satisfactory, then the correlation window closes.

General rules for the correlation processing:
The start of a fault correlation is an aircraft event.
The CFDIU finds this aircraft event when it receives internal fault(s) or external fault(s). This (these) fault(s) is (are) found in relation to:
The fault confirmation time of each system
The scan function of the CFDIU.

It is not possible to know if the internal failure will come before or after the external fault.
* Rule No. 1:
One fault (internal or external and with one ATA reference) that occurs out of the correlation processing time of a fault (internal or external and with one ATA reference) that occurred before it is a new fault. It starts a new correlation processing.
* Rule No. 2:
One fault (internal or external) that occurs during the correlation processing of fault(s) (internal or external) that occurred before it is managed in relation to its ATA reference:
. First condition:
The ATA reference of the fault is almost the same as that of the faults that are processed. The fault is not a new fault and it is related to the faults that are processed.
. Second condition:
The ATA reference of the fault is different from that of all the faults that are processed. The fault is a new fault and it starts a new correlation processing. The processing of the other faults is not stopped.

Description of the fault correlation processing:
CFDIU - Description of the Fault Correlation Processing ** ON A/C NOT FOR ALL

NOTE: An internal fault is of the types that follow:
. A system Built-In Test Equipment (BITE) or a fault internal to the CFDIU BITE (CFDIU/CLOCK/MCDU3)
. The CFDIU that finds that the update of label 356 did not occur. An external fault is a fault that the system BITE transmits.
For faults internal to the CFDIU BITE or external faults (label 356 that has no update), the source/identifier of the fault is the Centralized Fault Display System (CFDS).

NOTE: A given system can be the source/identifier only one time. If a given system transmits external faults during correlation processing, this system is given as the identifier only one time.

NOTE: - For a given fault, there is a maximum number of 6 identifiers (1 page).
- For the total of faults that can occur in flight, there is a maximum number of 200 identifiers.

NOTE: A maximum number of 16 correlation windows can come into view at the same time. If you get the maximum number of open correlation windows (16), and if the CFDIU receives a new failure message that cannot be related to one open correlation window, the CFDIU must:

Close the correlation window that it opened first
Open a new correlation window
Make a relation between the new failure message and this new correlation window.

Transmission to the Aircraft Communication Addressing and Reporting System (ACARS) (if it is installed):
The identifiers and the fault message are sent to the ACARS in real time. They are also sent with the transmission of the full POST FLIGHT REPORT.

5 The CFDIU does a Warning/Failure correlation.

Principle of the Warning/Failure correlation function
This function determines if it is possible to correlate the warnings acquired during a flight with the failures acquired during the same flight. This function takes into account the Last Leg Report (LLR) failures (enriched and correlated) and the Last Leg ECAM Report (LLER).
If the GMT is acquired with an SSM different from NO, failures and warnings are enriched with a GMT equal to 7999. Those failures and warnings are not taken into account for the warning/failure correlation.
Each warning can be correlated to a maximum of one failure.
Each failure can be correlated to a maximum of one warning.
The warning/failure correlation occurs:
* At the DC1/NULL maintenance-phase transition
* At the end of a filter data loading, if this data loading is satisfactory and if the filter function is active
* If the filter programming changes from inactive to active
* After the healthy discrete computation, if the memorized maintenance phase is equal to NULL.

This function is stopped:
* After the processing of all the warnings
* After two minutes of CFDIU processing this function
* At NULL/DC2 transition.
Rules of the Warning/Failure correlation function
A failure can be related to each warning if the GMT failure is in the GMT warning +/- two minutes limit and if one of these conditions is true:
* The first four ATA digits of the failure message are equal to the first four ATA digits of the warning or are in the list that follows
* The first four ATA digits of the failure source are equal to the first four ATA digits of the warning or are in the list that follows
* The first four ATA digits of one of the failure identifiers are equal to the first four ATA digits of the warning or are in the list that follows:

-----------------------------

! WARNING ATA ! FAILURE ATA !

!-------------!-------------!

! 23-73 ! 26-17 !

!-------------!-------------!

! 23-73 ! 38-31 !

!-------------!-------------!

! 23-24 ! 46-21 !

!-------------!-------------!

! 26-10 ! 26-12 !

!-------------!-------------!

! 32-41 ! 32-49 !

For the remaining warnings, a second rule applies to correlate them to failures. A failure can be related to each remaining warning if the GMT failure is in the GMT warning +/- two minutes limit and if one of these conditions is true:
* The first two ATA digits of the failure message are equal to the first two ATA digits of the warning.
* The first two ATA digits of the failure source are equal to the first two ATA digits of the warning.
* The first two ATA digits of one of the failure identifiers are equal to the first two ATA digits of the warning.
* This is not applicable if the ATA numbers (failure message or warning message or source or identifier) are in the list that follows:

---------------------------------------------------

! WARNING OR FAILURE ATA !

---------------------------------------------------

! 22-81 ! 22-82 ! 22-83 ! 23-11 ! 23-12 !

---------------------------------------------------

! 23-13 ! 26-13 ! 27-92 ! 27-93 ! 27-94 !

---------------------------------------------------

! 27-95 ! 31-32 ! 31-33 ! 31-36 ! 34-35 !

---------------------------------------------------

! 34-36 ! 34-37 ! 34-41 ! 34-42 ! 34-48 !

---------------------------------------------------

! 34-51 ! 34-52 ! 34-53 ! 34-55 ! 73-25 !

Results of the Warning/Failure correlation

Warning/Fault Correlation Results ** ON A/C NOT FOR ALL

The Warning/Failure correlation results are available on the CFDS main page, through the Last Leg Report (LLR) or the Last Leg ECAM Report (LLER) menus.

* Last Leg Report (LLR)
On the CFDS main menu, when you push the Line Select Key (LSK) adjacent to the LAST LEG REPORT, the CFDIU shows the content of the LLR. If a warning is correlated to a fault, a prompt (">") is shown on the right side of the related fault.
Then, if you push the MCDU LSK related to one of the prompts, the CFDIU shows the correlated warning.
If you push MCDU LSK 1R, the CFDIU shows the correlated warning related to the first fault.
If you push MCDU LSK 2R, the CFDIU shows the correlated warning related to the second fault.
The level of detail of the correlated warning is the same as that of the Last Leg ECAM Report (LLER) (hour, flight phase, ATA and warning message), but only the correlated warning is shown.
If the operator selects '<RETURN', the CFDIU shows the LLR page.

* LLER
On the CFDS main menu, when you push the LSK adjacent to the LAST LEG ECAM REPORT, the CFDIU shows the content of the LLER. If a fault is correlated to a wiring, a prompt (">") is shown on the right side of the related warning.
Then, if you push the MCDU LSK related to one of the prompts, the CFDIU shows the correlated fault.
If you push MCDU LSK 1R, the CFDIU shows the correlated fault related to the first warning.
If you push MCDU LSK 2R, the CFDIU shows the correlated fault related to the second warning.
The level of detail of the correlated fault is the same as that of the LLR sub-page (hour, flight phase, ATA, fault message, source and identifiers).
If the operator selects '<RETURN', the CFDIU shows the LLER page.
Display and transmission means of Warning/Failure correlation
The Warning/Failure correlation results are only available on the MCDU. You cannot print them or send them to the ground station and they are not memorized.

6 The CFDIU gives the PREVIOUS LEGS REPORT.

Memory of maintenance information:
The CFDIU moves the full LAST LEG REPORT to the PREVIOUS LEGS REPORT at the DC1/NULL transition and keeps it in memory.
The CFDIU can keep a maximum of 200 fault data in 64 flights.
The faults that occur before the last 64 flights are erased. Only the flights with a minimum of one fault are shown in the PREVIOUS LEGS REPORT.
Flight leg identification:
The CFDIU makes a relation between the data that follow and the maintenance information to make sure that the maintenance personnel can clearly identify the related flight:
. The flight count from the CFDIU. LEG -00 is related to the last flight. It is the same as the LAST LEG REPORT.
Example: LEG -13
. The flight date (that comes from the CLOCK or from the CFDIU, with label 260)
. The aircraft identification (from the FDIU with labels 301, 302, 303 and 304).

The CITY PAIR (FROM TO) from the Flight Management System (FMS) with labels 040, 041 and 042 transmitted by the Flight Augmentation Computer (FAC). Only the printer uses the CITY PAIR (FROM TO).

(b) On the ground:
Each time there is a scan of a system input:
. The CFDIU monitors the update of the fault information transmitted on the bus (refer to the "In flight" description).
. The CFDIU does not keep a fault message in memory.
This check occurs to:
. Find the status of the aircraft system at all times
. Give the AVIONICS STATUS.

(8) CFDIU operation

CFDIU - Faults Storage "at the soonest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

The CFDIU does a permanent scan of the inputs from each connected system (Type 1, 2 or 3) in flight and on the ground.

The CFDIU processing is not the same on the ground and in flight.

(a) In flight (maintenance phases related to DC 2 or DC 1)

"At the soonest" for the Type-1 and Type-3 systems - Phases 2b thru 9a
"At the latest" for the Type-1 and Type-3 systems - Phases 4 thru 9a.

For the Type-2 systems - Phases 5a thru 7a:

1 The CFDIU gives the CURRENT/LAST LEG REPORT.

Each time there is a scan of a system input (bus or discrete):

The CFDIU monitors the update of the information transmitted on the buses on each ARINC 429 input port that is included by pin-programming.
Monitoring label 356 finds the transmitted information that is not updated and shows it in four seconds. The subscriber systems permanently transmit monitoring label 356.

Each time monitoring label 356 finds that the transmitted information is not updated, the CFDIU:
Gives the ATA reference and the system name

Keeps this internal fault message in memory:

XX - XX - XX NO XX...X DATA

system ATA System identity coded

REFERENCE on 9 characters max.

NO XXXX...X DATA (INTM)

9 characters maximum

NOTE: The CFDIU does not monitor the ECB bus to make sure that there is an update of the transmitted information when it is not supplied in flight.

The CFDIU gets the fault messages and keeps them in memory:

* Type-1 or Type-2 systems:
The CFDIU makes sure that the received frames (messages) are correct before it keeps them in memory.
The CFDIU does the checks that follow:
. The Delta Block Word Count of the first Start of Text (STX) that is more than 0:
The CFDIU makes sure that the number of words received between the first STX and the End of Transmission (EOT) is equal to the Block Word Count of the first STX.
The CFDIU ignores the first Block Word Count in the frame.
The CFDIU makes sure that the next Block Word Count related to the STX(s) is set to zero.
The CFDIU makes sure that an End of Text (ETX) word is shown before this first STX.
It makes sure that an STX always follows an ETX.
In these conditions, the CFDIU gets and keeps in memory the message(s) related to the Block Word Count that increases.
When the Block Word Count increases, this shows that the system found a first or a new fault. The last fault message that is received (the one that caused the change of the Block Word Count) is the first message transmitted.
. The Delta Block Word Count of the first STX is less than or equal to zero.
In this condition, the frame is immediately rejected and the next system is selected (polling).
. The character check:
The CFDIU makes sure that the characters in the messages are included in the American Standard Code for Information Interchange (ASCII) table of the Multipurpose Control & Display Unit (MCDU) characters.
The CFDIU finds the type of the fault (internal or external to the system) and the class of the fault (1 or 2 or 3). It also examines if it is a "FAULT DATA".
The CFDIU keeps in memory the new class-1 or class-2 internal fault-message. The CFDIU also keeps in memory the names of the systems that transmit an external fault in relation to this internal fault. The transmission of the external fault occurs in the minute before or after the internal fault is found (refer to the Correlation Function).
* Type-3 systems:
On each discrete input related to the identification of a system fault, the CFDIU does a scan of the discrete state. The CFDIU gives and keeps in memory a message that causes the identification of the fault at each change that occurs in a discrete state.
Example: 308100 ICE DETECTOR 1
CFDIU - Example of CFDIU Operation - Type 3 System ** ON A/C NOT FOR ALL
This message is shown if an Angle Of Attack (AOA) sensor fault is found and has an effect on systems A, B, C and D. Systems A, B, C and D transmit the EXTERNAL fault information on their buses.
The Air Data System (ADS) transmits the INTERNAL fault information. This information is the message that the CFDIU keeps in memory.
The CFDIU also keeps in memory the names of the systems (A, B, C and D) that transmit an external fault message in relation to the fault of the ADS (correlation).
The CFDIU gives the time for each message:
Each time a new fault is found or a first fault is kept in memory, the CFDIU gives the related Greenwich Mean Time (GMT) (hours and minutes).
The GMT is kept in memory with the fault identification.
Example:
GMT : 0920
315000 FWC1
If the CFDIU finds that there is no update in some messages in a given flight, only the GMT related to the first message is kept in memory (capacity: 40 lines of 24 characters).

2 The CFDIU gives the CURRENT/LAST LEG ECAM REPORT.
The Flight Warning Computers (FWC) transmit the information that follows immediately on their output buses and on label 357:

The characters that make the identification of the fault message shown on the display units (lower and top)
Example: ENG LOOP A FAULT

The ATA chapter reference (4 digits) of the system related to the fault (the first five characters of the warning message are always the ATA reference).

Example: 2 6 - 1 0

! ! ! ! !

1st------- ! ! ! ---------5th

2nd------------ ! --------------4th

3rd

The CFDIU operates the functions that follow to give the ECAM REPORT:

The selection of the correct FWC bus
The reading filter and memory of label 357
The information about the relation between the GMT and the flight phase for each ECAM warning message kept in memory.

3 The CFDIU gives the AVIONICS STATUS.
Each time there is a sequential scan of:

All the buses of the Type-1 and Type-2 systems, and
All the discretes of the Type-3 systems:

The name of the system, in relation to its input port, and bit 21
Indication CLASS 3 and bit 20.
Example: ILS1.
If bit 21 is back to 0, the CFDIU erases the system name display.
* Type-3 systems:
The status of the discrete connected to the CFDIU gives the status of the Type-3 systems.
The discretes are monitored regularly and it is possible to manage the system status in real time.
The CFDIU makes a relation between the system name and each incorrect status (capacity: 40 lines of 24 characters).

4 The CFDIU operates the FAULT/FAULT CORRELATION:

Fault correlation function:
With the fault correlation function, only one fault message for a given "aircraft fault event" is kept in memory in the CFDIU.
Thus, the general principle of this function is to collect, for one message, all the messages that can occur after a given aircraft event. This message is as near as possible to the primary fault that caused this aircraft event.

Fault correlation criteria and the application "window":
. Criterion of correlation:
The criterion of correlation of the fault messages (relation or exclusion) is given by the ATA reference of the Line Replaceable Unit (LRU) related to the message.
This reference is given by the first two labels 356 that follow the STX of the fault message.
The messages are usually related if their ATA references are almost the same:
* Usually, if the first three digits of the ATA references are the same
* In special conditions, if the first four digits of the ATA references are the same (simple condition) or if they are from the same group of digits (double condition).

22-81
22-82
22-8N N different from 1, 2 or 3
23-11
23-12
23-13
23-1N N different from 1, 2 or 3
23-51 Only if RAIMS is "installed"
23-52 Only if RAIMS is "installed"
23-5N N different from 1, 2 only if RAIMS is "installed"
26-12 + 26-10
26-13
26-1N N different from 0, 2 or 3 (only if the aircraft configuration
includes CIDS configuration 1 or 2)
26-1N N different from 0, 2 or 3 and 2373 (only if the aircraft
configuration includes CIDS configuration 3)
27-92
27-93
27-94
27-95
27-9N N different from 2, 3, 4 or 5
31-32
31-33
31-36
31-39
31-3N N different from 2, 3, 6 or 9
32-41
32-49
32-4N N different from 1 or 9
32-55
32-5N N different from 5
34-35
34-36
34-37
34-3N N different from 5, 6 or 7
34-41
34-42
34-48
34-4N N different from 1, 2 or 8
34-51
34-52
34-53
34-55
34-5N N different from 1, 2, 3 or 5
46-26
73-25
73-2N N different from 5
23-2X + [46-2N with N different from 6 (FOMAX)]
XXXX + 23-13
23-73 + 38-31 (only if a new CIDS is installed)
letters

.Application window
The application window of this criterion is:
* With DC 1
If you open a correlation window with DC 1, you must keep this window open for a minimum of:

One minute
Two scanning cycles from the time you opened the window.

When these conditions are satisfactory, then the correlation window closes.
* With DC 2
If you open a correlation window with DC 2, you must keep this window open for a minimum of:

One minute
Two scanning cycles from the time of the DC 2/DC 1 maintenance-phase transition.

When these conditions are satisfactory, then the correlation window closes.

General rules for the correlation processing:
The start of a fault correlation is an aircraft event.
The CFDIU finds this aircraft event when it receives internal fault(s) or external fault(s). This (these) fault(s) is (are) found in relation to:
The fault confirmation time of each system
The scan function of the CFDIU.

Description of the fault correlation processing
CFDIU - Description of the Fault Correlation Processing ** ON A/C NOT FOR ALL

An internal fault has the two types that follow:

A system Built-In Test Equipment (BITE) or a fault internal to the CFDIU BITE (CFDIU/CLOCK)
The CFDIU that finds that the update of label 356 did not occur. An external fault is a fault that the system BITE transmits.

For faults internal to the CFDIU BITE or external faults (label 356 that has no update), the source/identifier of the fault is the Centralized Fault Display System (CFDS).
A given system can be the source/identifier only one time. If a given system transmits external faults during correlation processing, this system is given as the identifier only one time.
- For a given fault, there is a maximum number of 6 identifiers (1 page).
- For the total of faults that can occur in flight, there is a maximum number of 200 identifiers.
A maximum number of 16 correlation windows can come into view at the same time. If you get the maximum number of open correlation windows (16), and if the CFDIU receives a new failure message that cannot be related to one of the open correlation windows, the CFDIU must:

Close the correlation window that it opened first
Open a new correlation window
Make a relation between the new failure message and this new correlation window.

Transmission to the Aircraft Communication Addressing and Reporting System (ACARS) (if it is installed):
The identifiers and the fault message are sent to the ACARS in real time. They are also sent with the transmission of the full POST FLIGHT REPORT.

5 The CFDIU does a Warning/Failure correlation.

Principle of the Warning/Failure correlation function
This function determines if it is possible to correlate the warnings acquired during a flight with the failures acquired during the same flight. This function takes into account the Last Leg Report (LLR) failures (enriched and correlated) and the Last Leg ECAM Report (LLER).
If the GMT is acquired with an SSM different from NO, failures and warnings are enriched with a GMT equal to 7999. Those failures and warnings are not taken into account for the warning/failure correlation.
Each warning can be correlated to a maximum of one failure.
Each failure can be correlated to a maximum of one warning.
The warning/failure correlation occurs:
* At the DC1/NULL maintenance-phase transition
* At the end of a filter data loading, if this data loading is satisfactory and if the filter function is active
* If the filter programming changes from inactive to active
* After the healthy discrete computation, if the memorized maintenance phase is equal to NULL.

This function is stopped:
* After the processing of all the warnings
* After two minutes of CFDIU processing this function
* At NULL/DC2 transition.
Rules of the Warning/Failure correlation function
A failure can be related to each warning if the GMT failure is within the GMT warning +/- two minutes and if one of these conditions is true:
* The first four ATA digits of the failure message are equal to the first four ATA digits of the warning or are in the list that follows
* The first four ATA digits of the failure source are equal to the first four ATA digits of the warning or are in the list that follows
* The first four ATA digits of one of the failure identifiers are equal to the first four ATA digits of the warning or are in the list that follows:

-----------------------------

! WARNING ATA ! FAILURE ATA !

!-------------!-------------!

! 23-73 ! 26-17 !

!-------------!-------------!

! 23-73 ! 38-31 !

!-------------!-------------!

! 23-24 ! 46-21 !

!-------------!-------------!

! 26-10 ! 26-12 !

!-------------!-------------!

! 32-41 ! 32-49 !

For the remaining warnings, a second rule applies to correlate them to failures. A failure can be related to each remaining warning if the GMT failure is the GMT warning +/- two minutes limit and if one of these conditions is true:
* The first two ATA digits of the failure message are equal to the first two ATA digits of the warning.
* The first two ATA digits of the failure source are equal to the first two ATA digits of the warning.
* The first two ATA digits of one of the failure identifiers are equal to the first two ATA digits of the warning.
* This is not applicable if the ATA numbers (failure message or warning message or source or identifier) are in the list that follows:

---------------------------------------------------

! WARNING OR FAILURE ATA !

---------------------------------------------------

! 22-81 ! 22-82 ! 22-83 ! 23-11 ! 23-12 !

---------------------------------------------------

! 23-13 ! 26-13 ! 27-92 ! 27-93 ! 27-94 !

---------------------------------------------------

! 27-95 ! 31-32 ! 31-33 ! 31-36 ! 34-35 !

---------------------------------------------------

! 34-36 ! 34-37 ! 34-41 ! 34-42 ! 34-48 !

---------------------------------------------------

! 34-51 ! 34-52 ! 34-53 ! 34-55 ! 73-25 !

Results of the Warning/Failure correlation

Warning/Fault Correlation Results ** ON A/C NOT FOR ALL

The Warning/Failure correlation results are available on the CFDS main page, through the Last Leg Report (LLR) or the Last Leg ECAM Report (LLER) menus.

* Last Leg Report (LLR)
On the CFDS main menu, when you push the Line Select Key (LSK) adjacent to the LAST LEG REPORT, the CFDIU shows the content of the LLR. If a warning is correlated to a fault, a prompt (">") is shown on the right side of the related fault.
Then, if you push the MCDU LSK related to one of the prompts, the CFDIU shows the correlated warning.
If you push MCDU LSK 1R, the CFDIU shows the correlated warning related to the first fault.
If you push MCDU LSK 2R, the CFDIU shows the correlated warning related to the second fault.
The level of detail of the correlated warning is the same as that of the Last Leg ECAM Report (LLER) (hour, flight phase, ATA and warning message), but only the correlated warning is shown.
If the operator selects '<RETURN', the CFDIU shows the LLR page.

* LLER
On the CFDS main menu, when you push the LSK adjacent to the LAST LEG ECAM REPORT, the CFDIU shows the content of the LLER. If a fault is correlated to a wiring, a prompt (">") is shown on the right side of the related warning.
Then, if you push the MCDU LSK related to one of the prompts, the CFDIU shows the correlated fault.
If you push MCDU LSK 1R, the CFDIU shows the correlated fault related to the first warning.
If you push MCDU LSK 2R, the CFDIU shows the correlated fault related to the second warning.
The level of detail of the correlated fault is the same as that of the LLR sub-page (hour, flight phase, ATA, fault message, source and identifiers).
If the operator selects '<RETURN', the CFDIU shows the LLER page.
Display and transmission means of Warning/Failure correlation
The Warning/Failure correlation results are only available on the MCDU. You cannot print them or send them to the ground station and they are not memorized.

6 The CFDIU gives the PREVIOUS LEGS REPORT.

Memory of maintenance information:
The CFDIU moves the full LAST LEG REPORT to the PREVIOUS LEGS REPORT at the DC1/NULL transition and keeps it in memory.
The CFDIU can keep a maximum of 200 fault data in 64 flights.
The faults that occur before the last 64 flights are erased. Only the flights with a minimum of one fault are shown in the PREVIOUS LEGS REPORT.
Flight leg identification:
The CFDIU makes a relation between the data that follow and the maintenance information to make sure that the maintenance personnel can clearly identify the related flight:
. The flight count from the CFDIU. LEG -00 is related to the last flight. It is the same as the LAST LEG REPORT.
Example: LEG -13
. The flight date (that comes from the CLOCK or from the CFDIU, with label 260)
. The aircraft identification (from the FDIU with labels 301, 302, 303 and 304).

The CITY PAIR (FROM TO) from the Flight Management System (FMS) with labels 040, 041 and 042 is transmitted by the Flight Augmentation Computer 1 (FAC 1). Only the printer uses the CITY PAIR (FROM TO).

F. The Complete System : CFDS - Menu Mode
Menu Mode (Type 1 systems) and pseudo menu mode (Type 2 and 3 systems)
The menu mode concerns a specific operation that is only possible on the ground for Type 1 systems (ARINC input and output).
This mode is based on an interactive dialog between an aircraft system (Type 1) and the MCDU, the operator being guided by the information provided by the system itself.
Menu mode can only be connected to one system and one MCDU at a time.
The characteristics of menu mode are a selective transmission of data (depending on the operators selection) on the bus between the MCDU and the system, the CFDIU serving as interface. This transmission is described below.
This mode involves:

For the system (BITE):
* Interruption of normal mode, i.e. detection, memorization and transmission of faults.
* Display of its menu and execution of the menu functions, when ordered from the MCDU (via the CFDIU).
For the CFDIU:
* Interruption of normal mode, i.e. input scanning and fault memorization.
* Permanent connection to the system selected and establishing a dialog between the MCDU and the system.

For Type 2 and 3 systems there is a pseudo menu mode, which can be used on the ground only. This mode does not consist of a CFDIU - system dialog, as the operator is guided by the information provided by the CFDIU (and not by the system).
The characteristics of this pseudo menu mode are:

Permanent transmission of maintenance information by the system on the system bus to the CFDIU, except for the Test item, where transmission is only temporary. This transmission is described below.
Reading by the CFDIU of data corresponding to the menu item selected by the operator. This processing is described below.

This mode involves:

For the system (BITE):
No interruption of normal mode, except in some cases for the Test item of the menu triggered by the discrete.
For the CFDIU:
* interruption of normal mode,
* permanent connection to the system selected,
* presentation by the CFDIU of the system menu,
* reading by the CFDIU of the information transmitted by the systems that correspond to the menu item selected by the operator.

Menu Mode (Type 1 systems) and pseudo menu mode (Type 2 and 3 systems)
The menu mode concerns a specific operation that is only possible on the ground for Type 1 systems (ARINC input and output).
This mode is based on an interactive dialog between an aircraft system (Type 1) and the MCDU, the operator being guided by the information provided by the system itself.
Menu mode can only be connected to one system and one MCDU at a time.
The characteristics of menu mode are a selective transmission of data (depending on the operators selection) on the bus between the MCDU and the system, the CFDIU serving as interface. This transmission is described below.
This mode involves:

For the system (BITE):
* Interruption of normal mode, i.e. detection, memorization and transmission of faults.
* Display of its menu and execution of the menu functions, when ordered from the MCDU (via the CFDIU).
For the CFDIU:
* Interruption of normal mode, i.e. input scanning and fault memorization.
* Permanent connection to the system selected and establishing a dialog between the MCDU and the system.

Permanent transmission of maintenance information by the system on the system bus to the CFDIU, except for the Test item, where transmission is only temporary. This transmission is described below.
Reading by the CFDIU of data corresponding to the menu item selected by the operator. This processing is described below.

This mode involves:

For the system (BITE):
No interruption of normal mode, except in some cases for the Test item of the menu triggered by the discrete.
For the CFDIU:
* interruption of normal mode,
* permanent connection to the system selected,
* presentation by the CFDIU of the system menu,
* reading by the CFDIU of the information transmitted by the systems that correspond to the menu item selected by the operator.

(1) Operation of Type 1 systems and the CFDIU
When the operator selects the required system (on the MCDU):

The CFDIU transmits the identification code of the system selected to its output buses, using label 227 at a rate of 120 ms.
The system BITE transmits the menu contents to the CFDIU once on its output bus. This transmission is made on label 356 at a variable rate depending on the system. However, these data are transmitted in less than 3 s.
The CFDIU displays these data on the MCDU i.e. it reads the messages contained in labels 356 and adapts these messages to the MCDU.

When the operator selects one of the menu items (except the TEST item):

The CFDIU transmits the code of the line key corresponding to the item selected by the operator to the system; this transmission is made on label 227 at a rate of 120 ms.
The system BITE transmits the maintenance data stored in the different memory zones and corresponding to the selected item (except TEST item) to the CFDIU once on its output bus.
This transmission is made on label 356 at a variable rate depending on the system. However, these data are transmitted in less than 3 s.
Example:
The contents of zone 1, covering the last 63 flights is transmitted by the BITE when PREVIOUS LEGS REPORT is activated by the operator.
The CFDIU displays these data on the MCDU.

When the TEST item is selected in the menu:

The CFDIU transmits the code of the line key corresponding to this item (label 227) to the system.
The system BITE executes its test and may transmit a standby message to the CFDIU (label 356).
At the end of the test, the BITE transmits the test results (label 356) to the CFDIU once.
These data are not stored in the BITE.
The CFDIU displays these data on the MCDU.

(2) Operation of Type 2 systems and the CFDIU
When the operator selects the required system:
The CFDIU displays the system menu on the MCDU.
When one of the menu items is selected (except TEST item):

The CFDIU reads, on the system output bus, the maintenance data permanently transmitted by the BITE, which correspond to the item selected.
This transmission is made on label 356 in normal mode, i.e. at a rate set between 50 ms and 250 ms.
The CFDIU displays these data on the MCDU.

When the TEST item is selected in the menu:

The CFDIU connects the CFDIU-to-the-system discrete to ground for 500 ms.
The system BITE executes its test and may transmit a standby message to the CFDIU (label 356) when the test lasts a long time.
At the end of the test, the system BITE transmits the test results on its output bus (label 356) three times consecutively and then restarts transmission of faults in Normal Mode. These data are not stored in the BITE.
The CFDIU reads, on the system output bus, the test results (having previously read the standby messages that may have been sent by the system).
The CFDIU displays these data on the MCDU. In the event of non-reception, (after 3 seconds) the CFDIU displays the following message:
NO RESPONSE.

(3) Operation of Type 3 systems and the CFDIU
The only functions possible are Test (GCU emergency) or Reset (TR1, 2 and 3) depending on the systems
When these items are selected:

The CFDIU connects the CFDIU-to-the-system discrete to ground.
The system BITE executes its Test or Reset.
At the end of the Test or the Reset, the system BITE transmits, on its output discrete, the test result (correct or faulty operation depending on discrete status) or the Reset result (Reset performed or not, depending on discrete status).
The CFDIU decodes the result (reads discrete status).
The CFDIU displays this result on the MCDU by creating a correct or faulty operation text.

NOTE: - For the TEST function, the command (ground connection) lasts 500 ms ; for the RESET it lasts 60 ms.
- GCU emergency:
discrete open = fault.
discrete connected to ground = correct operation.
not monitored by the CFDIU in flight and on ground.
only test function available.
- TR1, 2 and 3:
discrete open = correct operation.
discrete connected to ground = fault.

(4) Operation of the Type-1 systems and the Centralized Fault Display Interface Unit (CFDIU)
When the operator selects the applicable system (on the Multipurpose Control & Display Unit (MCDU)):

The CFDIU transmits the identification code and the SDI of the selected system to its output buses, with label 227 at a rate of 120 ms.
The system BITE transmits the menu contents to the CFDIU one time on its output bus. This transmission occurs on label 356 at a rate that changes in relation to the system. But these data are transmitted in less than 3 s.
The CFDIU shows these data on the MCDU. The CFDIU reads the messages contained in label 356 and adapts these messages to the MCDU.

When the operator selects one of the menu items (the TEST item is not included in the menu items that the operator can select):

The CFDIU transmits to the system the code of the line key related to the item that the operator selected. This transmission occurs on label 227 at a rate of 120 ms.
The system BITE transmits the maintenance data kept in the different memory zones and related to the selected item (the TEST item is not included) to the CFDIU one time on its output bus.
This transmission is made on label 356 at a rate that changes in relation to the system. But, these data are transmitted in less than 3 s.
Example:
The BITE transmits the contents of zone 1 that include the last 63 flights when the operator starts the PREVIOUS LEGS REPORT.
The CFDIU shows these data on the MCDU.

When the TEST item is selected on the menu:

The CFDIU transmits the code of the line key related to this item (label 227) to the system.
The system BITE does its test and can transmit a standby message to the CFDIU (label 356).
At the end of the test, the BITE transmits the test results (label 356) to the CFDIU one time.
These data are not kept in the BITE.
The CFDIU shows these data on the MCDU.

(5) Operation of the Type-2 systems and the CFDIU
When the operator selects the applicable system:
The CFDIU shows the system menu on the MCDU.
When one of the menu items is selected (the TEST item is not included):

On the system output bus, the CFDIU reads the maintenance data that the BITE permanently transmits. These data are related to the selected item.
This transmission is made on label 356 in the normal mode, at a rate set between 50 ms and 250 ms.
The CFDIU shows these data on the MCDU.

When the TEST item is selected on the menu:

The CFDIU connects the CFDIU-to-the-system discrete to the ground for 500 ms. Then, the CFDIU puts the system discrete to the ground for a minimum of 3 seconds for the AFMS.
The system BITE does its test and can transmit a standby message to the CFDIU (label 356) when the test continues for a long time.
At the end of the test, the system BITE transmits the test results to its output bus (label 356) three times one after the other. Then the transmission of the faults starts again in the Normal Mode. These data are not kept in the BITE.
On the system output bus, the CFDIU reads the test results (after it read the standby messages that the system possibly sent).
The CFDIU shows these data on the MCDU. If no data is received, (after 3 seconds) the CFDIU shows the message that follows:
NO RESPONSE.

(6) Operation of the Type-3 systems and the CFDIU
The only functions that are possible are Test (GCU emergency and ICE DETECTOR 1 and 2) or Reset (TR1, 2 and 3) in relation to the systems.
When these items are selected:

The CFDIU connects the CFDIU-to-the-system discrete to the ground.
The system BITE does its Test or Reset.
At the end of the Test or the Reset, the system BITE transmits, on its output discrete, the test result (correct or faulty operation in relation to the discrete status) or the Reset result (Reset operated or not operated, in relation to the discrete status).
The CFDIU decodes the result (it reads the discrete status).
The CFDIU shows this result on the MCDU and gives a correct or faulty operation text.

NOTE: - For the TEST function, the command (ground connection) has a duration of 500 ms. For the RESET function, it has a duration of 500 ms.
- GCU emergency and ICE DETECTOR 1 and 2:
discrete open = fault.
discrete connected to the ground = correct operation.
not monitored by the CFDIU in flight and on the ground.
only test function available.
- TR1, 2 and 3:
discrete open = correct operation.
discrete connected to the ground = fault.
- DLRB/DLS:
discrete connected to the ground = correct operation.
discrete open = fault.

G. Flight/Ground Conditions of Systems and the CFDIU

Depending on the ground or flight conditions, the systems use different memorization and transmission modes and the CFDIU uses different modes for processing this information.

So the systems and the CFDIU require a flight/ground indication; this indication depends on the type of system.

(1) Type 1 systems

CFDIU - Maintenance Phase Logic (Nominal Case) ** ON A/C NOT FOR ALL

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

CFDIU - CFDIU Transmission to BITE - Normal Mode (Label 227) ** ON A/C NOT FOR ALL

The flight/ground condition is sent to the system by the CFDIU on the CFDIU to the system buses. This condition is coded on label 227, it is generated by the CFDIU.

The flight condition is coded DC2 and DC1 and corresponds:

for DC2:

. memorized phase : NULL (confirmed over 120s) and

. Engine running (CONF 180s) : running and

. (flight phase more than or equal to 4 and less than 9b) or ((SSM of acquired flight number at NO) and (acquired flight number different from memorized flight number)).
for DC1:

. memorized phase : DC2 (confirmed over 30s)
for NULL:

. memorized phase : DC1 or DC2 and

. (flight phase more than or equal to 9b and less than 4) or (engine running: shutdown (CONF 4s))

A flight change is given by a NULL/DC2 transition.

If the CFDIU is not available (input bus coming from the CFDIU declared invalid by the system because of the SSM, or refreshment, ...) the systems use a second condition sent directly as a result of aircraft configuration information (landing gear, engines, ...).

Furthermore, given their functionalities, certain systems (e.g. brakes which in theory only operate on the ground) cannot use these transition signals and generate their flight/ground logic using aircraft configuration information.

NOTE: In order to satisfy safety requirements the majority of Type 1 systems use a combination of 2 means for confirming their flight/ground condition and for inhibiting access to the menu mode and in particular to the test function, in flight.

(2) Type 2 or 3 systems

CFDIU - Fault Storage in System BITE and Transmission to the CFDIU : Normal Mode/Type 2 Systems ** ON A/C NOT FOR ALL

CFDIU - Maintenance Phase Logic (Nominal Case) ** ON A/C NOT FOR ALL

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

The flight/ground condition is sent directly to the system by means of one or several pieces of aircraft configuration information (e.g. discrete from the landing gear and/or engines) which correspond to flight phases 5, 6 and 7 for the flight condition.

(3) CFDIU

CFDIU - Faults Storage "at the soonest" in CFDIU : Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU : Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Maintenance Phase Logic (Nominal Case) ** ON A/C NOT FOR ALL

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

The CFDIU generates its flight/ground condition using some parameters transmitted by the FWC, the FAC, the memorized maintenance phases and a discrete from the LGCIU1 (nose landing gear shock absorber compressed).
For memorization of message in flight, the flight/ground condition is given by the flight phases from the FWC and depends on the type of system which is connected to it.

For type 1 and 3 systems:
Flight condition "at the latest" (flight number not acquired) corresponds to flight phases 4, 5, 6, 7, 8 and 9a.
Flight condition "at the soonest" (flight number acquired prior to engine start up) corresponds to flight phases 2b, 3, 4, 5, 6, 7, 8 and 9a.
Ground condition "at the latest" corresponds to flight phases 1, 2, 3, 9b and 10.
Ground condition "at the soonest" corresponds to flight phases 1, 2a, 9b and 10.
For Type 2 systems:
The flight condition corresponds to flight phases 5b, 6 and 7.
The ground condition corresponds to phases 1, 2, 3, 4, 8, 9 and 10.
A flight change is given by NULL/DC2 transition:
* For in flight inhibition of the functions which are forbidden in flight, i.e presentation of the CFDS main menu and availability of some specific functions (e.g : system menu mode/test) the flight/ground condition is given by an "OR" between the flight phases from the FWC and the discrete from the LGCIU1.
* For activation or non-activation of complete CFDIU power-up test (long or short test) in the event of CFDIU long power cutoff, the flight/ground condition is given by the discrete from the LGCIU1.

(4) Type 1 systems

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

Maintenance Phases - Logic Diagram (transition to flight "at the soonest". FLT N°. parameter entered prior to engine) ** ON A/C NOT FOR ALL

Maintenance Phases - Logic Diagram (transition to flight "at the latest". FLT N° . parameter not entered) ** ON A/C NOT FOR ALL

CFDIU - CFDIU Transmission to BITE - Normal Mode (Label 227) ** ON A/C NOT FOR ALL

for DC2:

. memorized phase : NULL (confirmed over 120s) and

. Engine running (CONF 180s) : running and

. (flight phase more than or equal to 4 and less than 9b) or ((SSM of acquired flight number at NO) and (acquired flight number different from memorized flight number)).
for DC1:

. memorized phase : DC2 (confirmed over 30s)
for NULL:

. memorized phase : DC1 or DC2 and

. (flight phase more than or equal to 9b and less than 4) or (engine running: shutdown (CONF 4s))

A flight change is given by a NULL/DC2 transition.

If the CFDIU is not available (input bus coming from the CFDIU declared invalid by the system because of the SSM, or refreshment, ...) the systems use a second condition sent directly as a result of aircraft configuration information (landing gear, engines, ...).

Furthermore, given their functionalities, certain systems (e.g. brakes which in theory only operate on the ground) cannot use these transition signals and generate their flight/ground logic using aircraft configuration information.

(5) Type 2 or 3 systems

CFDIU - Fault Storage in System BITE and Transmission to the CFDIU: Normal Mode/Type 2 Systems ** ON A/C NOT FOR ALL

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

(6) CFDIU

CFDIU - Faults Storage "at the soonest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Faults Storage "at the latest" in CFDIU: Normal Mode ** ON A/C NOT FOR ALL

CFDIU - Computation of Maintenance Phases (Downgraded Case - Loss of Both FWCs) ** ON A/C NOT FOR ALL

Maintenance Phases - Logic Diagram (transition to flight "at the soonest". FLT N°. parameter entered prior to engine) ** ON A/C NOT FOR ALL

Maintenance Phases - Logic Diagram (transition to flight "at the latest". FLT N° . parameter not entered) ** ON A/C NOT FOR ALL

For type 1 and 3 systems:
Flight condition "at the latest" (flight number not acquired) corresponds to flight phases 4, 5, 6, 7, 8 and 9a.
Flight condition "at the soonest" (flight number acquired prior to engine start up) corresponds to flight phases 2b, 3, 4, 5, 6, 7, 8 and 9a.
Ground condition "at the latest" corresponds to flight phases 1, 2, 3, 9b and 10.
Ground condition "at the soonest" corresponds to flight phases 1, 2a, 9b and 10.
For Type 2 systems:
The flight condition corresponds to flight phases 5b, 6 and 7.
The ground condition corresponds to phases 1, 2, 3, 4, 8, 9 and 10.
A flight change is given by NULL/DC2 transition:
* For in flight inhibition of the functions which are forbidden in flight, i.e presentation of the CFDS main menu and availability of some specific functions (e.g : system menu mode/test) the flight/ground condition is given by an "OR" between the flight phases from the FWC and the discrete from the LGCIU1.
* For activation or non-activation of complete CFDIU power-up test (long or short test) in the event of CFDIU long power cutoff, the flight/ground condition is given by the discrete from the LGCIU1.

H. Standby Clock Function

(1) Principle
The aircraft time base in normal operation is the clock located on the main instrument panel, it provides:

GMT/Date
Elapsed time
Chronometer.

It has been shown that the CFDIU permanently acquires GMT and the date and retransmits these data to the systems on its output buses.
In the event of clock fault, the CFDIU takes over and transmits GMT and date on its output buses.

(2) Operation
In normal operation, the CFDIU receives the time from the clock and synchronizes its internal clock with it.
In the event of fault of the main clock detected by the CFDIU (using the scrutinization of the status matrices and/or refreshment rate), the CFDIU calculates and transmits the time and the date using its internal clock. This transition does not require any reinitialization.
Reinitialization of the time and the date is only necessary after a long power cutoff (> 200 ms) and it must be carried out by the crew on the MCDU through the GMT/DATE INIT function displayed by the CFDIU on the MCDU, one minute after CFDIU power-up.

I. Pin Programming Function
The CFDIU generates and transmits on its output bus 2 aircraft configuration labels which contain pin programming of the electronic items of equipment which are optional on the aircraft. These configuration labels (155 and 156) are used by all BITEs to know the printer status (installed or not installed) and by some systems (e.g: RMP) to know the status of some optional items of equipment (e.g: VHF3, HF2...).

The CFDIU generates and transmits on its output bus 4 aircraft configuration labels which contain pin programming of the electronic items of equipment which are optional on the aircraft. These configuration labels (155, 156, 157 and 162 ) are used by all BITEs to know the printer status (installed or not installed) and by some systems (e.g: RMP) to know the status of some optional items of equipment (e.g: VHF3, HF2...).

The CFDIU generates and transmits, on its output bus, five aircraft configuration labels. These labels contain the pin programming of the electronic items of equipment which are optional on the aircraft. All the BITE(s) use configuration labels (155, 156, 157, 162 and 163) to know the printer status (installed or not installed). Some systems (for example the RMP) also use configuration labels to know the status of some optional items of equipment (for example VHF 3, HF 2, etc.).

(1) Description and generation of aircraft configuration labels
The aircraft configuration labels 155 and 156 are generated either from pin programming directly wired to the CFDIU or from data transmitted by the bus of other computers connected to the CFDIU.

(2) Acquisition of labels making up the aircraft configuration labels.
The configuration is memorized by the CFDIU 45 seconds after power-up tests and on maintenance phase NULL/DC2 transition.
In the event of incorrect data at CFDIU input (labels not refreshed or SSM invalid), the CFDIU remains in the previous configuration.
If the CFDIU detects a memory fault, it assigns the "present" default code to all systems on labels 155 and 156.

(3) Description and generation of aircraft configuration labels

The aircraft configuration labels 155, 156, 157 and 162 are generated either from pin programming directly wired to the CFDIU or from data transmitted by the bus of other computers connected to the CFDIU.

(4) Acquisition of labels making up the aircraft configuration labels.

The configuration is memorized by the CFDIU 45 seconds after power-up tests and on maintenance phase NULL/DC2 transition.

In the event of incorrect data at CFDIU input (labels not refreshed or SSM invalid), the CFDIU remains in the previous configuration.

If the CFDIU detects a memory fault, it assigns the "present" default code to all systems on labels 155, 156, 157 and 162.

(5) Description and generation of aircraft configuration labels

The aircraft configuration labels 155, 156, 157, 162 and 163 are generated from:

Pin programming directly connected to the CFDIU, or
Data from the buses of other computers connected to the CFDIU.

(6) Acquisition of labels that make up the aircraft configuration labels.

The CFDIU stores the configuration in memory 45 seconds after the power-up tests and at the time of the maintenance-phase NULL/DC2 transition.

When the data at the CFDIU input is incorrect (labels not refreshed or SSM invalid), the CFDIU stays in the last configuration.

If the CFDIU detects a memory fault, it gives the "present" default code to all the systems on labels 155, 156, 157, 162 and 163.

J. Warning/Fault Messages Filtering Function

(1) Principle

The purpose of this function is to improve the operational use of the POST FLIGHT REPORT, LAST LEG ECAM REPORT and LAST LEG REPORT printed at the end of the flight as well as the real-time fault and warning information transmitted by the ACARS, by filtering all the spurious or unjustified faults/warnings.

(2) Operation

The filtering function can be activated or de-activated from the MCDU.
The filter criteria can be uploaded by means of the portable data loader or the MDDU (option).
When PFR function is activated, FILTER does apply to the LAST LEG REPORT, CURRENT LEG REPORT, LAST LEG ECAM REPORT, CURRENT LEG ECAM REPORT, POST FLIGHT REPORT, CURRENT FLIGHT REPORT, REAL TIME FAILURE, REAL TIME WARNING whatever the output mode could be (ACARS, PRINTER, MCDU).
When PFR FILTER is not activated, none of the above mentioned reports are filtered.

** ON A/C NOT FOR ALL

4. Power Supply

CFDIU - Power Supply

A. Power Supply and Consumption
The CFDIU is supplied with 28VDC.
Power consumption is less than 28W.

B. Circuit Breakers
The following table defines the circuit breakers used by the system :

-------------------------------------------------------------------------------

FIN ! FUNCTIONAL DESIGNATION ! PANEL!ZONE!ACCESS ! ATA

! ! ! ! DOOR ! REF.

-------------------------------------------------------------------------------

2TW CFDS/CFDIU/SPLY 121VU 210

8TW CFDS/CFDIU/BACK/UP 121VU 210

** ON A/C NOT FOR ALL

5. Interfaces

A. CFDIU Inputs/Outputs
The list of all the systems connected to the CFDIU and the characteristics of these connections are given in the table below.

CFDIU - Inputs/Outputs Architecture ** ON A/C NOT FOR ALL

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ATA : 21 ! ! ! ! ! ! ! !

! CAB PRESS ! 1 ! 3 ! X ! ! ! X ! X !

! CONT 1 ! ! ! ! ! ! ! !

! CAB PRESS ! 1 ! 4 ! X ! ! ! ! !

! CONT 2 ! ! ! ! ! ! ! !

!ZONE CONT/ACSC2! 1 ! 4 ! X ! ! ! ! X !

! AEVC ! 2 ! ! X ! X ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA : 21 ! ! ! ! ! ! !

! CAB PRESS ! 1 ! 3 ! X ! ! ! X !

! CONT 1 ! ! ! ! ! ! !

! CAB PRESS ! 1 ! 4 ! X ! ! ! !

! CONT 2 ! ! ! ! ! ! !

!ZONE CONT/ACSC2! 1 ! 4 ! X ! ! ! X !

! AEVC ! 2 ! ! X ! X ! ! !

! HEAT CONT-AFT ! 2 ! X ! ! ! X ! !

!CARGO COMPT ! ! ! ! ! ! !

!HEAT CONT-FWD ! 1 ! 1 ! x ! ! ! !

!CARGO COMPT ! 1 ! X ! 3 ! ! ! !

!CSAS/FTIS ! 1 ! 3 ! x ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! HEAT CONT-AFT ! 1 ! 1 ! X ! ! ! ! !

! CARGO COMPT ! ! ! ! ! ! ! !

! HEAT CONT-FWD ! 1 ! 3 ! X ! ! ! ! !

! CARGO COMPT ! ! ! ! ! ! ! !

! CSAS/FTIS ! 1 ! 3 ! X ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! HEAT CONT-AFT ! 1 ! 1 ! X ! ! ! !

! CARGO COMPT ! ! ! ! ! ! !

! HEAT CONT-FWD ! 1 ! 3 ! X ! ! ! !

! CARGO COMPT ! ! ! ! ! ! !

! CSAS/FTIS ! 1 ! 3 ! X ! ! ! !

------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! HEAT CONT-FWD ! 1 ! 3 ! X ! ! ! !

! CARGO COMPT ! ! ! ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ! ! ! ! ! ! ! !

! ATA : 22 ! ! ! ! ! ! ! !

! FAC 1 ! 1 ! 3 ! FIDS BUS! ! ! X ! X !

! ! ! ! ! ! ! ! !

! ATA : 23 ! ! ! ! ! ! ! !

! CIDS 1 ! 1 ! 3 ! X ! ! ! ! !

! CIDS 2 ! 1 ! 4 ! X ! ! ! ! !

! AMU ! 1 ! 4 ! X ! ! ! ! !

! RMP 1 ! 1 ! 1 ! FREQ.BUS! ! ! ! !

! VHF 1 ! 1 ! 1 ! X ! ! ! ! !

! VHF 2 ! 1 ! 2 ! X ! ! ! ! !

------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 22 ! ! ! ! ! ! !

! FAC 1 ! 1 ! 3 ! FIDS BUS! ! ! X !

! ! ! ! ! ! ! !

! ATA : 23 ! ! ! ! ! ! !

! CIDS 1 ! 1 ! 3 ! X ! ! ! !

! CIDS 2 ! 1 ! 4 ! X ! ! ! !

! AMU ! 1 ! 4 ! X ! ! ! !

! RMP 1 ! 1 ! 1 ! FREQ.BUS! ! ! !

! VHF 1 ! 1 ! 1 ! X ! ! ! !

! VHF 2 ! 1 ! 2 ! X ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! HF 1 ! 1 ! 1 ! X ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! HF 1 ! 1 ! 1 ! X ! ! ! !

! HF 2 ! 1 ! 2 ! X ! ! ! !

------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! HF 2 ! 1 ! 2 ! X ! ! ! !

! ACARS MU ! 1 ! 4 ! X ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! VHF 3 ! 1 ! 4 ! X ! ! ! ! !

------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! VHF 3 ! 1 ! 4 ! X ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! VHF4 ! ! ! ! ! ! ! !

! (Provision) ! ! ! ! ! ! ! !

! ACARS MU2 ! ! ! ! ! ! ! !

! (Provision) ! ! ! ! ! ! ! !

! SATCOM ! ! ! ! ! ! ! !

! (Provision) ! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! SATCOM ! 1 ! 3 ! X ! ! ! !

! ACARS MU ! 1 ! 4 ! X ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! CVR* ! 1 ! 3 ! X ! ! ! !

NOTE: * If installed.

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ! ! ! ! ! ! ! !

! ATA : 24 ! ! ! ! ! ! ! !

! CSM/G CONTROL ! 3 ! ! ! X ! X ! ! !

! UNIT ! ! ! ! ! ! ! !

! GPCU ! 2 ! ! X ! X ! ! X ! X !

! GPCU STEP 2 ! ! ! ! ! ! ! !

! (Provision) ! ! ! ! ! ! ! !

! BCL 1 ! 2 ! ! 3 ! X ! ! ! !

! BCL 2 ! 2 ! ! 3 ! X ! ! ! !

! TR 1 ! 3 ! ! ! X ! X ! ! !

! TR 2 ! 3 ! ! ! X ! X ! ! !

! TR 3 ! 3 ! ! !NOT !NOT ! ! !

! ! ! ! !ACTIVATED !ACTIVATED! ! !

! ! ! ! ! ! ! ! !

! ATA : 26 ! ! ! ! ! ! ! !

! FDU 1 ! 2 ! ! X ! X ! ! ! !

! FDU 2 ! 2 ! ! X ! X ! ! ! !

! APU FDU ! 2 ! ! X ! X ! ! ! !

! SDCU/CIDS-SDF ! 1 ! 3 ! X ! ! ! ! !

! ! ! ! ! ! ! ! !

! ATA : 27 ! ! ! ! ! ! ! !

! FCDC 1 ! 1 ! 3 ! 1 ! ! ! X ! X !

! FCDC 2 ! 1 ! 4 ! 1 ! ! ! X ! X !

! SFCC 1 ! 1 ! 3 ! 1 ! ! ! X ! X !

! SFCC 2 ! 1 ! 4 ! 1 ! ! ! X ! X !

! ! ! ! ! ! ! ! !

! ATA : 28 ! ! ! ! ! ! ! !

! FQI ! 1 ! 3 ! 2 ! ! ! ! X !

! ! ! ! ! ! ! ! !

! ATA : 30 ! ! ! ! ! ! ! !

! WHC 1 ! 2 ! ! X ! X ! ! ! !

! WHC 2 ! 2 ! ! X ! X ! ! ! !

! PHC 1 ! 2 ! ! X ! X ! ! ! !

! PHC 2 ! 2 ! ! X ! X ! ! ! !

! PHC 3 ! 2 ! ! X ! X ! ! ! !

! ICE DET 1 ! 3 ! ! ! X ! X ! ! !

! ICE DET 2 ! 3 ! ! ! X ! X ! ! !

! ! ! ! ! ! ! ! !

! ATA : 31 ! ! ! ! ! ! ! !

! FWC 1 ! 1 ! 1 ! 3 ! ! ! X ! X !

! FWC 2 ! 1 ! 2 ! 3 ! ! ! X ! X !

! DMC 1 ! 1 ! 1 ! 1 ! ! ! X ! X !

! DMC 2 ! 1 ! 2 ! 1 ! ! ! X ! X !

! DMC 3 ! 1 ! 4 ! 1 ! ! ! ! X !

! FDIU/FDIU ! 1 ! ! X ! ! ! X ! X !

! Channel ! ! ! ! ! ! ! !

! FDIU ! 3 ! ! ! X ! X ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 24 ! ! ! ! ! ! !

! CSM/G CONTROL ! 3 ! ! ! X ! X ! !

! UNIT ! ! ! ! ! ! !

! GPCU ! 2 ! ! X ! X ! ! X !

! BCL 1 ! 2 ! ! 3 ! X ! ! !

! BCL 2 ! 2 ! ! 3 ! X ! ! !

! TR 1 ! 3 ! ! ! X ! X ! !

! TR 2 ! 3 ! ! ! X ! X ! !

! TR 3 ! 3 ! ! !NOT !NOT ! !

! ! ! ! !ACTIVATED !ACTIVATED! !

! GAPCU ! 1 ! 4 ! X ! ! ! !

! ! ! ! ! ! ! !

! ATA : 26 ! ! ! ! ! ! !

! FDU 1 ! 2 ! ! X ! X ! ! !

! FDU 2 ! 2 ! ! X ! X ! ! !

! APU FDU ! 2 ! ! X ! X ! ! !

! SDCU/CIDS-SDF ! 1 ! 3 ! X ! ! ! !

! ! ! ! ! ! ! !

! ATA : 27 ! ! ! ! ! ! !

! FCDC 1 ! 1 ! 3 ! 1 ! ! ! X !

! FCDC 2 ! 1 ! 4 ! 1 ! ! ! X !

! SFCC 1 ! 1 ! 3 ! 1 ! ! ! X !

! SFCC 2 ! 1 ! 4 ! 1 ! ! ! X !

! ! ! ! ! ! ! !

! ATA : 28 ! ! ! ! ! ! !

! FQI ! 1 ! 3 ! 2 ! ! ! !

! ! ! ! ! ! ! !

! ATA : 30 ! ! ! ! ! ! !

! WHC 1 ! 2 ! ! X ! X ! ! !

! WHC 2 ! 2 ! ! X ! X ! ! !

! PHC 1 ! 2 ! ! X ! X ! ! !

! PHC 2 ! 2 ! ! X ! X ! ! !

! PHC 3 ! 2 ! ! X ! X ! ! !

! ICE DET 1 ! 3 ! ! ! X ! X ! !

! ICE DET 2 ! 3 ! ! ! X ! X ! !

! ! ! ! ! ! ! !

! ATA : 31 ! ! ! ! ! ! !

! FWC 1 ! 1 ! 1 ! 3 ! ! ! X !

! FWC 2 ! 1 ! 2 ! 3 ! ! ! X !

! DMC 1 ! 1 ! 1 ! 1 ! ! ! X !

! DMC 2 ! 1 ! 2 ! 1 ! ! ! X !

! DMC 3 ! 1 ! 4 ! 1 ! ! ! !

! FDIU/FDIU ! 1 ! ! X ! ! ! X !

! Channel ! ! ! ! ! ! !

! DLRB/DLS ! 3 ! ! ! X ! X ! !

------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM TEST !

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 24 ! ! ! ! ! ! !

! CSM/G CONTROL ! 3 ! ! ! X ! X ! !

! UNIT ! ! ! ! ! ! !

! GPCU ! 2 ! ! X ! X ! ! X !

! BCL 1 ! 2 ! ! 3 ! X ! ! !

! BCL 2 ! 2 ! ! 3 ! X ! ! !

! TR 1 ! 3 ! ! ! X ! X ! !

! TR 2 ! 3 ! ! ! X ! X ! !

! TR 3 ! 3 ! ! !not !not ! !

! ! ! ! !started !started ! !

! ! ! ! ! ! ! !

! ATA : 26 ! ! ! ! ! ! !

! FDU 1 ! 2 ! ! X ! X ! ! !

! FDU 2 ! 2 ! ! X ! X ! ! !

! APU FDU ! 2 ! ! X ! X ! ! !

! SDCU/CIDS-SDF ! 1 ! 3 ! X ! ! ! !

! ! ! ! ! ! ! !

! ATA : 27 ! ! ! ! ! ! !

! FCDC 1 ! 1 ! 3 ! 1 ! ! ! X !

! FCDC 2 ! 1 ! 4 ! 1 ! ! ! X !

! SFCC 1 ! 1 ! 3 ! 1 ! ! ! X !

! SFCC 2 ! 1 ! 4 ! 1 ! ! ! X !

! ! ! ! ! ! ! !

! ATA : 28 ! ! ! ! ! ! !

! FQI ! 1 ! 3 ! 2 ! ! ! X !

! AFMS ! 2 ! ! X ! X ! ! !

! ! ! ! ! ! ! !

! ATA : 30 ! ! ! ! ! ! !

! WHC 1 ! 2 ! ! X ! X ! ! !

! WHC 2 ! 2 ! ! X ! X ! ! !

! PHC 1 ! 2 ! ! X ! X ! ! !

! PHC 2 ! 2 ! ! X ! X ! ! !

! PHC 3 ! 2 ! ! X ! X ! ! !

! ICE DET 1 ! 3 ! ! ! X ! X ! !

! ICE DET 2 ! 3 ! ! ! X ! X ! !

! ! ! ! ! ! ! !

! ATA : 31 ! ! ! ! ! ! !

! FWC 1 ! 1 ! 1 ! 3 ! ! ! X !

! FWC 2 ! 1 ! 2 ! 3 ! ! ! X !

! DMC 1 ! 1 ! 1 ! 1 ! ! ! X !

! DMC 2 ! 1 ! 2 ! 1 ! ! ! X !

! DMC 3 ! 1 ! 4 ! 1 ! ! ! X !

! FDIU/FDIU ! 1 ! 4 ! X ! ! ! X !

! Channel ! ! ! ! ! ! !

! DLRB/DLS ! 3 ! ! ! X ! X ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! DMU/DMU ! 1 ! 1 ! 1 ! ! ! ! !

! Channel (AIDS)! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! DMU/DMU ! 1 ! 1 ! 1 ! ! ! !

! Channel (AIDS)! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! DLRB / DLS 3 ! ! ! X ! X ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! MDDU ! 2 ! 4 ! X ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! PRINTER ! 1 ! 1 ! X ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! PRINTER ! 1 ! 1 ! X ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! PRINTER ! 1 ! 1 ! X ! ! ! !

! CVDR 1/RIU* ! 1 ! 3 ! X ! ! ! !

! ! ! !(no inter! ! ! !

! ! ! ! active ! ! ! !

! ! ! ! mode) ! ! ! !

! CVDR 2* ! 1 ! 1 ! X ! ! ! !

! ! ! !(no inter! ! ! !

! ! ! ! active ! ! ! !

! ! ! ! mode) ! ! ! !

NOTE: * If installed.

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ! ! ! ! ! ! ! !

! ATA : 32 ! ! ! ! ! ! ! !

! LGCIU 1 ! 1 ! 3 ! 3 ! ! ! X ! X !

! LGCIU 2 ! 1 ! 4 ! 3 ! ! ! ! X !

! BSCU 1 ! 1 ! 3 ! 2 ! ! ! X ! X !

! BSCU 2 ! 1 ! 4 ! 4 ! ! ! ! X !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 32 ! ! ! ! ! ! !

! LGCIU 1 ! 1 ! 3 ! 3 ! ! ! X !

! LGCIU 2 ! 1 ! 4 ! 3 ! ! ! X !

! BSCU 1 ! 1 ! 3 ! 2 ! ! ! X !

! BSCU 2 ! 1 ! 4 ! 4 ! ! ! X !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA: 32 ! ! ! ! ! ! !

! LGCIU 1 ! 1 ! 3 ! 3 ! ! ! X !

! LGCIU 2 ! 1 ! 4 ! 3 ! ! ! X !

! BSCU 1 ! 1 ! 3 ! 2 ! ! ! X !

! BSCU 2 ! 1 ! 4 ! 4 ! ! ! X !

! TPIS ! 1 ! 3 ! X ! ! ! X !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ! ! ! ! ! ! ! !

! ATA : 34 ! ! ! ! ! ! ! !

! ADIRU1 IRS 1 ! 1 ! 1 ! 3 ! ! ! X ! X !

! ADC 1 ! 1 ! 1 ! 4 ! ! ! X ! X !

! ADIRU2 IRS 2 ! 1 ! 2 ! 3 ! ! ! X ! X !

! ADC 2 ! 1 ! 2 ! 4 ! ! ! X ! X !

! ADIRU3 IRS 3 ! 1 ! 3 ! 3 ! ! ! ! X !

! IADC 3 ! 1 ! 3 ! 4 ! ! ! ! X !

! ILS 1 or MMR 1! 1 ! 1 ! 2 ! ! ! ! X !

! ILS 2 or MMR 2! 1 ! 2 ! 2 ! ! ! ! X !

! VOR 1 ! 1 ! 1 ! 2 ! ! ! ! !

! VOR 2 ! 1 ! 2 ! 2 ! ! ! ! !

! DME 1 ! 1 ! 1 ! 2 ! ! ! ! !

! DME 2 ! 1 ! 2 ! 2 ! ! ! ! !

! ATC 1 ! 1 ! 1 ! CFDS BUS! ! ! ! !

! ATC 2 ! 1 ! 2 ! CFDS BUS! ! ! ! !

! RA 1 ! 1 ! 1 ! 2 ! ! ! ! X !

! RA 2 ! 1 ! 2 ! 2 ! ! ! ! X !

! RADAR 1 ! 1 ! 1 ! X ! ! ! ! !

! ADF 1 ! 1 ! 1 ! 2 ! ! ! ! !

! ADF 2 * ! 1 ! 2 ! 2 ! ! ! ! !

! HUDC * ! 2 ! ! X ! ! ! ! !

! HUDC 1 * ! 2 ! 1(**)! X ! ! ! ! !

! HUDC 2 * ! 2 ! 2(**)! X ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 34 ! ! ! ! ! ! !

! ADIRU1 IRS 1 ! 1 ! 1 ! 3 ! ! ! X !

! ADC 1 ! 1 ! 1 ! 4 ! ! ! X !

! ADIRU2 IRS 2 ! 1 ! 2 ! 3 ! ! ! X !

! ADC 2 ! 1 ! 2 ! 4 ! ! ! X !

! ADIRU3 IRS 3 ! 1 ! 3 ! 3 ! ! ! X !

! IADC 3 ! 1 ! 3 ! 4 ! ! ! X !

! ILS 1 or MMR 1! 1 ! 1 ! 2 ! ! ! X !

! ILS 2 or MMR 2! 1 ! 2 ! 2 ! ! ! X !

! VOR 1 ! 1 ! 1 ! 2 ! ! ! !

! VOR 2 ! 1 ! 2 ! 2 ! ! ! !

! DME 1 ! 1 ! 1 ! 2 ! ! ! !

! DME 2 ! 1 ! 2 ! 2 ! ! ! !

! ATC 1 ! 1 ! 1 ! CFDS BUS! ! ! !

! ATC 2 ! 1 ! 2 ! CFDS BUS! ! ! !

! RA 1 ! 1 ! 1 ! 2 ! ! ! X !

! RA 2 ! 1 ! 2 ! 2 ! ! ! X !

! RADAR 1 ! 1 ! 1 ! X ! ! ! !

! ADF 1 ! 1 ! 1 ! 2 ! ! ! !

! ADF 2 * ! 1 ! 2 ! 2 ! ! ! !

! HUDC * ! 2 ! ! X ! ! ! !

! HUDC 1 * ! 2 ! 1(**)! X ! ! ! !

! HUDC 2 * ! 2 ! 2(**)! X ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 34 ! ! ! ! ! ! !

! ADIRU1 IRS 1 ! 1 ! 1 ! 3 ! ! ! X !

! ADC 1 ! 1 ! 1 ! 4 ! ! ! X !

! ADIRU2 IRS 2 ! 1 ! 2 ! 3 ! ! ! X !

! ADC 2 ! 1 ! 2 ! 4 ! ! ! X !

! ADIRU3 IRS 3 ! 1 ! 3 ! 3 ! ! ! X !

! IADC 3 ! 1 ! 3 ! 4 ! ! ! X !

! ILS 1 or MMR 1! 1 ! 1 ! 2 ! ! ! X !

! ILS 2 or MMR 2! 1 ! 2 ! 2 ! ! ! X !

! VOR 1 ! 1 ! 1 ! 2 ! ! ! !

! VOR 2 ! 1 ! 2 ! 2 ! ! ! !

! DME 1 ! 1 ! 1 ! 2 ! ! ! !

! DME 2 ! 1 ! 2 ! 2 ! ! ! !

! ATC 1 ! 1 ! 1 ! CFDS BUS! ! ! !

! ATC 2 or ! ! ! ! ! ! !

! T3CAS-ATC2 ! 1 ! 2 ! CFDS BUS! ! ! !

! RA 1 ! 1 ! 1 ! 2 ! ! ! X !

! RA 2 ! 1 ! 2 ! 2 ! ! ! X !

! RADAR 1 ! 1 ! 1 ! X ! ! ! !

! ADF 1 ! 1 ! 1 ! 2 ! ! ! !

! ADF 2 * ! 1 ! 2 ! 2 ! ! ! !

! HUDC * ! 2 ! ! X ! ! ! !

! HUDC 1 * ! 2 ! 1(**)! X ! ! ! !

! HUDC 2 * ! 2 ! 2(**)! X ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ADF 2 ! 1 ! 2 ! 2 ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! GPWC/T2CAS- ! 1 ! 4 ! X ! ! ! ! !

! TAWS * ! ! ! ! ! ! ! !

! GPS 1 * ! 1 ! 1 ! X ! ! ! ! !

! GPS 2 * ! 1 ! 2 ! X ! ! ! ! !

! GPSSU 1 * ! 1 ! 1 ! X ! ! ! ! !

! GPSSU 2 * ! 1 ! 2 ! X ! ! ! ! !

! TCAS/T2CAS- ! 1 ! 4 ! X ! ! ! ! !

! TCAS * ! ! ! ! ! ! ! !

! ISIS ! 2 ! ! X ! X ! ! ! !

! OANS * ! 2 ! ! ! X ! ! ! !

NOTE: * if installed.
** not used for bite protocol.

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! GPWC/T2CAS- ! 1 ! 4 ! X ! ! ! !

! TAWS * ! ! ! ! ! ! !

! GPS 1 * ! 1 ! 1 ! X ! ! ! !

! GPS 2 * ! 1 ! 2 ! X ! ! ! !

! GPSSU 1 * ! 1 ! 1 ! X ! ! ! !

! GPSSU 2 * ! 1 ! 2 ! X ! ! ! !

! TCAS/T2CAS- ! 1 ! 4 ! X ! ! ! !

! TCAS * ! ! ! ! ! ! !

! ISIS ! 2 ! ! X ! X ! ! !

! OANS * ! 2 ! ! ! X ! ! !

NOTE: * if installed.
** not used for bite protocol.

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! GPWC or T2CAS-! 1 ! 4 ! X ! ! ! !

! TAWS* or ! ! ! ! ! ! !

! T3CAS-TAWS* ! ! ! ! ! ! !

! GPS 1 * ! 1 ! 1 ! X ! ! ! !

! GPS 2 * ! 1 ! 2 ! X ! ! ! !

! GPSSU 1 * ! 1 ! 1 ! X ! ! ! !

! GPSSU 2 * ! 1 ! 2 ! X ! ! ! !

! TCAS/T2CAS- ! 1 ! 4 ! X ! ! ! !

! TCAS or ! ! ! ! ! ! !

! T3CAS-TCAS ! ! ! ! ! ! !

! ISIS ! 2 ! ! X ! X ! ! !

! OANS * ! 2 ! ! ! X ! ! !

NOTE: * if installed.
** not used for bite protocol.

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ! ! ! ! ! ! ! !

! ATA : 36 ! ! ! ! ! ! ! !

! BMC 1 ! 1 ! 3 ! X ! ! ! ! X !

! BMC 2 ! 1 ! 4 ! X ! ! ! ! X !

! ! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ! ! ! ! ! ! !

! ATA : 36 ! ! ! ! ! ! !

! BMC 1 ! 1 ! 3 ! X ! ! ! X !

! BMC 2 ! 1 ! 4 ! X ! ! ! X !

! ! ! ! ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ATA : 38 ! ! ! ! ! ! ! !

! TOILET SYS. ! 1 ! 2 ! X ! ! ! ! !

! (VSC or CIDS ! ! ! ! ! ! ! !

! TOILET SYS) ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA : 38 ! ! ! ! ! ! !

! TOILET SYS. ! 1 ! 2 ! X ! ! ! !

! (VSC or CIDS ! ! ! ! ! ! !

! TOILET SYS) ! ! ! ! ! ! !

! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA : 46 ! ! ! ! ! ! !

! ATSU ! 1 ! 4 ! X ! ! ! !

! SIU ! 1 ! 4 ! X ! ! ! !

! ! ! ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA: 46 ! ! ! ! ! ! !

! ATSU ! 1 ! 4 ! X ! ! ! !

! FOMAX ! 1 ! 4 ! X ! ! ! !

! ! ! ! ! ! ! !

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ATA : 49 ! ! ! ! ! ! ! !

! ECB ! 1 ! 3 ! X ! ! ! ! X !

! ! ! ! ! ! ! ! !

! ATA : 70/80 ! ! ! ! ! ! ! !

! EIU 1 ! 1 ! 3 ! B ! ! ! X ! X !

! EIU 2 ! 1 ! 4 ! B ! ! ! X ! X !

! EVMU ! 1 ! 3 ! X ! ! ! ! X !

!_______________!________!_________!_________!__________!_________!_____!_____!

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED DIREC- ! SYSTEM !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! TLY TO THE ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! CFDIU (FOR ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA : 49 ! ! ! ! ! ! !

! ECB ! 1 ! 3 ! X ! ! ! X !

! ! ! ! ! ! ! !

! ATA : 70/80 ! ! ! ! ! ! !

! EIU 1 ! 1 ! 3 ! B ! ! ! X !

! EIU 2 ! 1 ! 4 ! B ! ! ! X !

! EVMU ! 1 ! 3 ! X ! ! ! X !

!_______________!________!_________!_________!__________!_________!_____!

------------------------------------------------------------------------------

! SYSTEM CONNECTED ! ! !BACK-UP ! TEST !

! TO THE CFDIU ! ! !CONNEC- ! PLUG !

! THROUGH ANOTHER ! THROUGH ! NOTES ! TION ! CONNEC-!

! SYSTEM (FOR FAULTS ! ! ! ! TION !

! DATA) ! ! ! ! !

!----------------------------------------------------------------------------!

! ATA : 21 ! ! ! ! !

! FLOW AMPLIFIER !_ ! ACSC2 or Zone CTL ! ! !

! PACK CONT 1 ! ! ZONE ! Title : TEMP CTL ! ! !

! PACK CONT 2 !_! CONT ! ! ! !

! ! ! ! ! !

! ATA : 22 ! ! ! ! !

! FAC 2 _ !_ !_ ! X_ ! X_ !

! FMGC 1 ! ! ! ! ! ! X ! ! X ! !

! ! FMC 1 ! ! ! ! ! X_! ! X_! !

! _! FGC 1 ! ! FAC 1 ! ! Title : AFS ! X ! ! X ! !

! FMGC 2 ! FMC 2 ! ! ! ! ! X_! ! X_! !

! _! FGC 2 ! ! ! ! ! X ! !

! FCU !_! ! ! ! ! !

! MCDU 1 ! ! FMGC 1 ! ! ! ! !

! MCDU 2 ! ! and !_! ! ! !

! !_! FMGC 2 ! ! ! !

! ! ! ! ! !

! ATA : 23 !_ ! ! ! !

! RMP 2 ! ! RMP 1 ! ! ! !

! RMP 3 (IF INSTALLED)!_! ! ! ! !

! ACP 1 ! ! ! ! ! !

! ACP 2 ! ! AMU ! ! ! !

! ACP 3 ! ! ! ! ! !

! ACP 4 !_! ! ! ! !

! Tape Reproducer ! ! ! ! ! !

! (Prerecorded ! ! ! ! ! !

! announcement) ! ! ! ! ! !

! Tape Reproducer ! ! ! ! ! !

! (Passenger Enter- ! ! ! ! ! !

! tainment system PES)! ! ! ! ! !

! Amplifier PES ! ! ! ! ! !

! Amplifier Video ! ! CIDS ! ! ! !

! Video Reader ! ! ! ! ! !

! FWD Attendant Panel ! ! ! ! ! !

! (FAP) (IF INSTALLED)! ! ! ! ! !

! Programming and Test! ! ! ! ! !

! Panel (PTP) ! ! ! ! ! !

! (IF INSTALLED) ! ! ! ! ! !

! Attendant Indication! ! ! ! ! !

! Panel (AIP) !_! ! ! ! !

! ! ! ! ! !

! ATA : 24 !_ ! ! ! !

! GCU 1 ! ! ! ! ! !

! GCU 2 ! ! ! ! ! !

! GCU APU ! ! GPCU ! Title : AC GEN ! ! !

! EGIU 1 ! ! ! ! ! !

! EGIU 2 !_! ! ! ! !

! ! ! ! ! !

! ATA : 27 ! ! ! ! !

! SEC 1 !_ ! ! ! !

! SEC 2 ! ! FCDC 1 ! Title : EFCS = X ! ! !

! SEC 3 ! ! and ! (X = 1 or 2) ! ! !

! ELAC 1 ! ! FCDC 2 ! ! ! !

! ELAC 2 !_! ! ! ! !

! ! ! ! ! !

! ATA : 28 !_ ! ! ! !

! FLSCU 1 ! ! FQI ! Title : FUEL ! ! !

! FLSCU 2 !_! ! ! ! !

! ! ! ! ! !

! ATA : 30 ! ! ! ! !

! Wing Anti Ice ! ZONE CONT ! Title : TEMP CTL ! ! !

! ! or ACSC2 ! ! ! !

! ! ! ! ! !

! ATA : 31 !_ ! ! ! !

! CAPT PFD ! ! ! ! ! !

! F/O PFD ! ! ! ! ! !

! CAPT ND ! ! ! ! ! !

! F/O ND ! ! DMC 1 ! Title : EIS X ! ! !

! ECAM Engine/Warning ! ! 2 and 3 ! (X = 1, 2 or 3)! ! !

! Display ! ! ! ! ! !

! ECAM System/Status ! ! ! ! ! !

! Display !_! ! ! ! !

! SDAC 1 ! ! FWC 1 ! Title : ECAM X ! X ! X !

! SDAC 2 ! ! and ! (X = 1 or 2) ! X ! X !

! ECAM CTL PNL

! QAR (IF INSTALLED) ! ! ! ! ! !

! DFDR !_! FDIU ! ! ! !

! DAR (IF INSTALLED) ! DMU ! ! ! !

! ! (AIDS) ! ! ! !

! ! ! ! ! !

! ATA : 34 ! ! ! ! !

! OHU (IF INSTALLED) ! HUD ! ! ! !

! ! ! ! ! !

! ATA : 47 ! ! ! ! !

! IGGS/FTIS ! CSAS/FTIS ! ! ! !

! IGGS/FTIS ! ! FUEL INERTING ! ! !

! (IF INSTALLED) ! ! ! ! !

! ! ! ! ! !

! ATA : 70/80 !_ ! ! ! !

! FADEC 1 CHA ! ! EIU 1 ! Title : FADEC 1A, 1B, ! X ! X !

! CHB !_! ! 2A, 2B ! X ! !

! FADEC 2 CHA ! ! EIU 2 ! (EIU transparent for ! X ! X !

! CHB !_! ! FADEC) ! X ! !

!_____________________!___________!________________________!________!________!

---------------------------------------------------------------------

! SYSTEM CONNECTED ! ! ! TEST !

! TO THE CFDIU ! ! ! PLUG !

! THROUGH ANOTHER ! THROUGH ! NOTES ! CONNEC-!

! SYSTEM (FOR FAULTS ! ! ! TION !

! DATA) ! ! ! !

!-------------------------------------------------------------------!

! ATA : 21 ! ! ! !

! FLOW AMPLIFIER !_ ! ACSC2 or Zone CTL ! !

! PACK CONT 1 ! ! ZONE ! Title : TEMP CTL ! !

! PACK CONT 2 !_! CONT ! ! !

! ! ! ! !

! ATA : 22 ! ! ! !

! FAC 2 _ !_ !_ ! X_ !

! FMGC 1 ! ! ! ! ! ! X ! !

! ! FMC 1 ! ! ! ! ! X_! !

! _! FGC 1 ! ! FAC 1 ! ! Title : AFS ! X ! !

! FMGC 2 ! FMC 2 ! ! ! ! ! X_! !

! _! FGC 2 ! ! ! ! ! X !

! FCU !_! ! ! ! !

! MCDU 1 ! ! FMGC 1 ! ! ! !

! MCDU 2 ! ! and !_! ! !

! !_! FMGC 2 ! ! !

! ! ! ! !

! ATA : 23 !_ ! ! !

! RMP 2 ! ! RMP 1 ! ! !

! ! ! or ! ! !

! ! ! RAIMS ! ! !

! RMP 3 (IF INSTALLED)!_! ! ! !

! ACP 1 ! ! ! ! !

! ACP 2 ! ! AMU ! ! !

! ! ! or ! ! !

! ! ! RAIMS ! ! !

! ACP 3 ! ! ! ! !

! ACP 4 !_! ! ! !

! Tape Reproducer ! ! ! ! !

! (Prerecorded ! ! ! ! !

! announcement) ! ! ! ! !

! Tape Reproducer ! ! ! ! !

! (Passenger Enter- ! ! ! ! !

! tainment system PES)! ! ! ! !

! Amplifier PES ! ! ! ! !

! Amplifier Video ! ! CIDS ! ! !

! Video Reader ! ! ! ! !

! FWD Attendant Panel ! ! ! ! !

! (FAP) (IF INSTALLED)! ! ! ! !

! Programming and Test! ! ! ! !

! Panel (PTP) ! ! ! ! !

! (IF INSTALLED) ! ! ! ! !

! Attendant Indication! ! ! ! !

! Panel (AIP) !_! ! ! !

! ! ! ! !

! ATA : 24 !_ ! ! !

! GCU 1 ! ! ! ! !

! GCU 2 ! ! ! ! !

! GCU APU ! ! GPCU/ ! Title : AC GEN ! !

! EGIU 1 ! ! GAPCU ! ! !

! EGIU 2 !_! ! ! !

! ! ! ! !

! ATA : 27 ! ! ! !

! SEC 1 !_ ! ! !

! SEC 2 ! ! FCDC 1 ! Title : EFCS = X ! !

! SEC 3 ! ! and ! (X = 1 or 2) ! !

! ELAC 1 ! ! FCDC 2 ! ! !

! ELAC 2 !_! ! ! !

! ! ! ! !

! ATA : 28 !_ ! ! !

! FLSCU 1 ! ! FQI ! Title : FUEL ! !

! FLSCU 2 !_! ! ! !

! ! ! ! !

! ATA : 30 ! ! ! !

! Wing Anti Ice ! ZONE CONT ! Title : TEMP CTL ! !

! ! or ACSC2 ! ! !

! ! ! ! !

! ATA : 31 !_ ! ! !

! CAPT PFD ! ! ! ! !

! F/O PFD ! ! ! ! !

! CAPT ND ! ! ! ! !

! F/O ND ! ! DMC 1 ! Title : EIS X ! !

! ECAM Engine/Warning ! ! 2 and 3 ! (X = 1, 2 or 3)! !

! Display ! ! ! ! !

! ECAM System/Status ! ! ! ! !

! Display !_! ! ! !

! SDAC 1 ! ! FWC 1 ! Title : ECAM X ! X !

! SDAC 2 ! ! and ! (X = 1 or 2) ! X !

! ECAM CTL PNL ! ! ! ! !

! QAR (IF INSTALLED) ! ! ! ! !

! DFDR !_! FDIU ! ! !

! DAR (IF INSTALLED) ! DMU ! ! !

! ! (AIDS) ! ! !

! ! ! ! !

! ATA : 34 ! ! ! !

! OHU (IF INSTALLED) ! HUD ! ! !

! VOR1 ! MMR1 ! Only in MMR ! !

! ! ! configuration 4 with ! !

! ! ! VOR included ! !

! VOR2 ! MMR2 ! Only in MMR ! !

! ! ! configuration 4 with ! !

! ! ! VOR included ! !

! ATA : 47 ! ! ! !

! IGGS/FTIS ! CSAS/FTIS ! ! !

! IGGS/FTIS ! ! FUEL INERTING ! !

! (IF INSTALLED) ! ! ! !

! ! ! ! !

! ATA : 70/80 !_ ! ! !

! FADEC 1 CHA ! ! EIU 1 ! Title : FADEC 1A, 1B, ! X !

! CHB !_! ! 2A, 2B ! !

! FADEC 2 CHA ! ! EIU 2 ! (EIU transparent for ! X !

! CHB !_! ! FADEC) ! !

!_____________________!___________!________________________!________!

-------------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! BACK! TEST!

! NECTED TO THE ! !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! -UP ! PLUG!

! CFDIU (FOR ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-! CON-!

! OTHER THAN ! ! ! ! ! ! NEC-! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION! TION!

!---------------!--------!---------!---------!----------!---------!-----!-----!

! ATA : 22 ! ! ! ! ! ! ! !

! MCDU 1 ! 1 ! 1 ! 1 ! ! ! X ! !

! MCDU 2 ! 1 ! 2 ! 1 ! ! ! ! !

! ! ! ! ! ! ! ! !

! ATA : 31 ! ! ! ! ! ! ! !

! CLOCK ! - ! ! X ! ! ! ! !

-------------------------------------------------------------------------

! SYSTEMS CON- ! ! CFDIU ! SYSTEM ! CFDIU ! SYSTEM ! TEST!

! NECTED TO THE ! !TO SYSTEM!TO CFDIU !TO SYSTEM !TO CFDIU ! PLUG!

! CFDIU (FOR ! TYPE ! BUS No. ! BUS No. ! DISCRETE ! DISCRETE! CON-!

! OTHER THAN ! ! ! ! ! ! NEC-!

! FAULTS DATA) ! ! ! ! ! ! TION!

!---------------!--------!---------!---------!----------!---------!-----!

! ATA : 22 ! ! ! ! ! ! !

! MCDU 1 ! 1 ! 1 ! 1 ! ! ! !

! MCDU 2 ! 1 ! 2 ! 1 ! ! ! !

! ! ! ! ! ! ! !

! ATA : 31 ! ! ! ! ! ! !

! CLOCK ! - ! ! X ! ! ! !

-------------------------------------------------------------------------------

! BUS 1 ! BUS 2 ! BUS 3 ! BUS 4 !

!------------------!------------------!-------------------!-------------------!

! SYSTEM ! SYSTEM ! SYSTEM ! SYSTEM !

!------------------!------------------!-------------------!-------------------!

! ADR 1 ! ADR 2 ! BMC 1 ! BMC 2 !

! ILS 1 or *MMR 1! ILS 2 or *MMR 2! EIU 1 ! EIU 2 !

! VOR 1 ! VOR 2 ! FAC 1 ! CIDS 2 !

! DME 1 ! DME 2 ! CIDS 1 ! SFCC 2 !

! ATC 1 ! ATC 2 ! SFCC 1 ! CAB PRESS !

! ! ! CAB PRESS ! CONT 2 !

! RA 1 ! RA 2 ! CONT 1 ! !

! RADAR 1 ! * RADAR 2 ! ! LGCIU 2 !

! ADF 1 ! * ADF 2 ! LGCIU 1 ! * ACARS MU !

! FWC 1 ! FWC 2 ! FQI ! BSCU 2 !

! DMC 1 ! DMC 2 ! BSCU 1 ! AMU !

! VHF 1 ! VHF 2 ! ECB ! FCDC 2 !

! * DMU (AIDS) ! IR 2 ! FCDC 1 ! * VHF 3 !

! IR 1 ! MCDU 2 ! ! !

! MCDU 1 ! * HF 2 ! EVMU ! ZONE CONT/ACSC2 !

! * AFT CARGO HEAT ! VACUUM SYS ! * FWD CARGO ! DMC 3 !

! CONT ! CONT ! HEAT CONT ! FDIU !

! * HF 1 ! * GPSSU 2 ! * SDCU/CIDS-SDF1 ! * GPWC/T2CAS-TAWS !

! RMP 1 ! CNSU ! ADR 3 ! * TCAS/T2CAS-TCAS !

! PRINTER ! IFE CENTER ! IR 3 ! * MDDU !

! * GPSSU 1 ! * ISIS ! * TPIS ! * GAPCU !

! ! * HUDC2 ! AGS/OBCE ! SIU !

! ! ! ! CSAS/FTIS !

!__________________!__________________!___________________!___________________!

* : options

The table below lists the output discretes.

------------------------------------------

! TYPE 2 ! TYPE 3 !

!--------------------!-------------------!

! AEVC ! GCU Emergency !

! GPCU ! TR 1, 2, 3 !

! BCL 1, 2 ! ICE DET 1 + 2 !

! FDU 1, 2, APU ! !

! WHC 1, 2 ! !

! PHC 1, 2, 3 ! !

! ISIS ! !

! HUDC 1, 2 ! !

! * OANS ! !

!____________________!___________________!

* : options

The table below gives the distribution of type 1 systems on the output buses.

-------------------------------------------------------------------------------

! BUS 1 ! BUS 2 ! BUS 3 ! BUS 4 !

!------------------!------------------!-------------------!-------------------!

! SYSTEM ! SYSTEM ! SYSTEM ! SYSTEM !

!------------------!------------------!-------------------!-------------------!

! ADR 1 ! ADR 2 ! BMC 1 ! BMC 2 !

! ILS 1 or *MMR 1! ILS 2 or *MMR 2! EIU 1 ! EIU 2 !

! VOR 1 ! VOR 2 ! FAC 1 ! CIDS 2 !

! DME 1 ! DME 2 ! CIDS 1 ! SFCC 2 !

! ATC 1 ! ATC 2 ! SFCC 1 ! CAB PRESS !

! ! ! CAB PRESS ! CONT 2 !

! RA 1 ! RA 2 ! CONT 1 ! !

! RADAR 1 ! * RADAR 2 ! ! LGCIU 2 !

! ADF 1 ! * ADF 2 ! LGCIU 1 ! * ACARS MU !

! FWC 1 ! FWC 2 ! FQI ! BSCU 2 !

! DMC 1 ! DMC 2 ! BSCU 1 ! AMU !

! VHF 1 ! VHF 2 ! ECB ! FCDC 2 !

! * DMU (AIDS) ! IR 2 ! FCDC 1 ! * VHF 3 !

! IR 1 ! MCDU 2 ! ! !

! MCDU 1 ! * HF 2 ! EVMU ! ZONE CONT/ACSC2 !

! * AFT CARGO HEAT ! VACUUM SYS ! * FWD CARGO ! DMC 3 !

! CONT ! CONT ! HEAT CONT ! FDIU !

! * HF 1 ! * GPSSU 2 ! * SDCU/CIDS-SDF1 ! * GPWC/T2CAS-TAWS !

! RMP 1 ! CNSU ! ADR 3 ! * TCAS/T2CAS-TCAS !

! PRINTER ! IFE CENTER ! IR 3 ! * MDDU !

! * GPSSU 1 ! * ISIS ! * TPIS ! * GAPCU !

! ! * HUDC2 ! AGS/OBCE ! SIU !

! ! ! ! CSAS/FTIS !

!__________________!__________________!___________________!___________________!

* : options

The table below lists the output discretes.

------------------------------------------

! TYPE 2 ! TYPE 3 !

!--------------------!-------------------!

! AEVC ! GCU Emergency !

! GPCU ! TR 1, 2, 3 !

! BCL 1, 2 ! ICE DET 1 + 2 !

! FDU 1, 2, APU ! * DLRB/DLS !

! WHC 1, 2 ! !

! PHC 1, 2, 3 ! !

! ISIS ! !

! HUDC 1, 2 ! !

! * OANS ! !

!____________________!___________________!

* : option(s)

The table below gives the distribution of the Type-1 systems on the output buses.

-------------------------------------------------------------------------------

! BUS 1 ! BUS 2 ! BUS 3 ! BUS 4 !

!------------------!------------------!-------------------!-------------------!

! SYSTEM ! SYSTEM ! SYSTEM ! SYSTEM !

!------------------!------------------!-------------------!-------------------!

! ADR 1 ! ADR 2 ! BMC 1 ! BMC 2 !

! ILS 1 or *MMR 1! ILS 2 or *MMR 2! EIU 1 ! EIU 2 !

! VOR 1 ! VOR 2 ! FAC 1 ! CIDS 2 !

! DME 1 ! DME 2 ! CIDS 1 ! SFCC 2 !

! ATC 1 ! ATC 2 ! SFCC 1 ! CAB PRESS !

! ! ! CAB PRESS ! CONT 2 !

! RA 1 ! RA 2 ! CONT 1 ! !

! RADAR 1 ! * RADAR 2 ! ! LGCIU 2 !

! ADF 1 ! * ADF 2 ! LGCIU 1 ! * ACARS MU !

! FWC 1 ! FWC 2 ! FQI ! BSCU 2 !

! DMC 1 ! DMC 2 ! BSCU 1 ! AMU !

! VHF 1 ! VHF 2 ! ECB ! FCDC 2 !

! * DMU (AIDS) ! IR 2 ! FCDC 1 ! * VHF 3 !

! IR 1 ! MCDU 2 ! ! !

! MCDU 1 ! * HF 2 ! EVMU ! ZONE CONT/ACSC2 !

! * AFT CARGO HEAT ! VACUUM SYS ! * FWD CARGO ! DMC 3 !

! CONT ! CONT ! HEAT CONT ! FDIU !

! * HF 1 ! * GPSSU 2 ! * SDCU/CIDS-SDF1 ! * GPWC/T2CAS-TAWS !

! RMP 1 ! CNSU ! ADR 3 ! * TCAS/T2CAS-TCAS !

! PRINTER ! IFE CENTER ! IR 3 ! * MDDU !

! * GPSSU 1 ! * ISIS ! * TPIS ! * GAPCU !

! * HUDC1 ! * HUDC2 ! AGS/OBCE ! SIU !

! ! ! ! CSAS/FTIS !

! ! ! ! !

! ! ! CVR ! !

!__________________!__________________!___________________!___________________!

* : options

The table below gives the output discretes.

------------------------------------------

! TYPE 2 ! TYPE 3 !

!--------------------!-------------------!

! AEVC ! GCU Emergency !

! GPCU ! TR 1, 2, 3 !

! BCL 1, 2 ! ICE DET 1 + 2 !

! FDU 1, 2, APU ! * DLRB/DLS !

! WHC 1, 2 ! !

! PHC 1, 2, 3 ! !

! ISIS ! !

! HUDC 1, 2 ! !

! * OANS ! !

! * AFMS ! !

!____________________!___________________!

* : option(s)

The table that follows gives the distribution of the Type-1 systems on the output buses:

---------------------------------------------------------------------------------

! BUS 1 ! BUS 2 ! BUS 3 ! BUS 4 !

!------------------ !------------------ !-------------------!-------------------!

! SYSTEM ! SYSTEM ! SYSTEM ! SYSTEM !

!------------------ !------------------ !-------------------!-------------------!

! ADR 1 (RS) ! ADR 2 (RS) ! BMC 1 ! BMC 2 !

! ILS 1 or * MMR 1! ILS 2 or * MMR 2! EIU 1 ! EIU 2 !

! VOR 1 ! VOR 2 ! FAC 1 ! CIDS 2 !

! DME 1 ! DME 2 ! CIDS 1 ! SFCC 2 !

! ATC 1 ! ATC 2/T3CAS-ATC2! SFCC 1 ! CAB PRESS !

! ! ! CAB PRESS ! CONT 2 !

! RA 1 ! RA 2 ! CONT 1 ! !

! RADAR 1 ! * RADAR 2 ! ! LGCIU 2 !

! ADF 1 ! * ADF 2 ! LGCIU 1 ! * ACARS MU/ATSU !

! FWC 1 ! FWC 2 ! FQI ! BSCU 2 !

! DMC 1 ! DMC 2 ! BSCU 1 ! AMU !

! VHF 1 ! VHF 2 ! ECB ! FCDC 2 !

! * DMU (AIDS) ! IR 2 ! FCDC 1 ! * VHF 3 !

! IR 1 ! MCDU 2 ! ! !

! MCDU 1 ! * HF 2 ! EVMU ! ZONE CONT/ACSC2 !

! * AFT CARGO HEAT ! VACUUM SYS ! * FWD CARGO ! DMC 3 !

! CONT ! CONT ! HEAT CONT ! FDIU !

! * HF 1 ! * GPSSU 2 ! * SDCU/CIDS-SDF1 ! * GPWC/T2CAS-TAWS !

! RMP 1 ! CNSU ! ADR 3 (RS) ! * TCAS/T2CAS-TCAS !

! PRINTER ! IFE CENTER 1 ! IR 3 ! !

! * GPSSU 1 ! ! * TPIS ! * GAPCU !

! * HUDC 1 ! * HUDC 2 ! ! FOMAX !

! * CVDR 2 ! Test plug (198Vc) ! * MDDU ! CSAS !

! ! ! SDU SATCOM ! !

! ! ! * CVR/* CVDR 1/ ! !

! ! ! * RIU ! !

!___________________!___________________!___________________!___________________!

* Options
RS: Reserved Spare

The table that follows gives the output discretes:

------------------------------------------

! TYPE 2 ! TYPE 3 !

!--------------------!-------------------!

! AEVC ! GCU Emergency !

! GPCU ! TR 1, 2, 3 !

! BCL 1, 2 ! ICE DET 1 + 2 !

! FDU 1, 2, APU ! * DLRB/DLS !

! WHC 1, 2 ! !

! PHC 1, 2, 3 ! !

! ISIS ! !

! HUDC 1, 2 ! !

! * OANS ! !

! * AFMS ! !

!____________________!___________________!

* Options

The list of input/output labels is given in the figure below.

CFDIU - Input/Output Labels List ** ON A/C NOT FOR ALL

(1) Inputs
The CFDIU receives fault information from approx. 130 aircraft systems (basic + optional), directly (Type 1, 2 or 3 systems) or indirectly (System BITEs).
The CFDIU inputs (for maintenance) consist of :

ARINC 429 buses from Type 1, 2 systems, SYSTEM BITEs and peripherals
discretes from Type 3 systems, pin programming and flight/ground condition.

NOTE: These inputs receive fault messages except: CLOCK and MCDUs.
The PRINTER input also receive the data constituting the protocol with the CFDIU.

(2) Outputs
At output, the CFDIU has:

ARINC 429 buses to Type 1 systems and systems BITEs
discretes to type 2 and 3 systems.

(3) Inputs
The CFDIU receives fault information from approx. 130 aircraft systems (basic + optional), directly (Type 1, 2 or 3 systems) or indirectly (System BITEs).
The CFDIU inputs (for maintenance) consist of :

ARINC 429 buses from Type 1, 2 systems, SYSTEM BITEs and peripherals
discretes from Type 3 systems, pin programming and flight/ground condition.

NOTE: These inputs receive fault messages except: CLOCK and MCDUs.
The DMU input receives fault messages and it also receives other data.
The MCDUs and PRINTER inputs also receive the data constituting the protocol with the CFDIU.

(4) Outputs
At output, the CFDIU has:

ARINC 429 buses to Type 1 systems and systems BITEs
discretes to type 2 and 3 systems.

(5) Discrete input/output characteristics
The CFDIU has the capacity for 24 discrete inputs and 24 discrete outputs, of the GROUND/OPEN CIRCUIT type.
When open, each input/output has a maximum leakage current of 10 micro.A.

(a) Ground/open circuit type input

Low-pass filter with 1.6 ms time constant.
For a ground signal at input, the typical current is approximately 0.5 mA.

(b) Ground/open circuit type output

Leakage current in open state : less than 10 micro.A up to 150 degrees.
In closed state (= ground), the current capacity is between 6 and 30 mA.

These discretes are closed (connected to ground) at each TEST (or RESET) request for the corresponding Type 2 or 3 systems, when the request is made from the MCDU.

B. Interface with the MCDUs
The MCDUs allow a dialog with the CFDIU or with the BITEs of the various systems connected to the CFDIU, depending on the flight/ground conditions.

C. Interface with the Systems which Provide General Parameters
(clock, FWC, FDIU and DMU and FAC1).
Dating and Fault Identification.
The CFDIU is connected to several aircraft systems which provide general parameters enabling identification of faults.
These general parameters are retransmitted by the CFDIU to the various Type 1 systems which are connected to it, via its output buses. They are memorized by the system BITEs for the establishment of fault reports that are memorized in the systems.
These parameters are also used and memorized by the CFDIU itself, for establishing fault reports that are memorized in the CFDIU.
The transmission of these parameters by the CFDIU is synchronous. It implies permanent scrutinization of the FWC (1 or 2) and CLOCK input buses, and sequential scrutinization of the FAC1, DMC1 and FDIU buses.
(clock, FWC, FDIU and DMU and FAC1).
Dating and Fault Identification.
The CFDIU is connected to several aircraft systems which provide general parameters enabling identification of faults.
These general parameters are retransmitted by the CFDIU to the various Type 1 systems which are connected to it, via its output buses. They are memorized by the system BITEs for the establishment of fault reports that are memorized in the systems.
These parameters are also used and memorized by the CFDIU itself, for establishing fault reports that are memorized in the CFDIU.
The transmission of these parameters by the CFDIU is synchronous. It implies permanent scrutinization of the FWC (1 or 2) and CLOCK input buses, and sequential scrutinization of the FAC1, DMC1 and FDIU buses.

(1) Interface with the clock
The CFDIU is connected to the clock, located on the center instrument panel, which provides:

GMT/Date
elapsed time
chronometer.

The CFDIU permanently acquires GMT and the date and transmits these data on its output buses.
The clock provides the date and the time at which faults occur.
The time associated with the fault messages and the ECAM warnings enables the correlation between the ECAM warnings and the fault messages memorized by the CFDIU.
In the event of loss of clock operation or incorrect operation detected by the CFDIU, the CFDIU takes over and calculates the time and the date using its internal clock.
This transition does not require reinitialization if there is not a long power cutoff (> 200 ms). If there is a long power cutoff, the crew performs reinitialization using the MCDU.
The CLOCK is declared failed or invalid (= incorrect operation) by the CFDIU when one of the labels of the GMT and DATE parameters is not refreshed or transmitted with incorrect parity or with SSM at NCD or FT confirmed over 1 minute.

(2) Interface with the FWC
In normal configuration (no fault) the CFDIU permanently reads the FWC1 bus and reads the FWC2 bus cyclicly for the reception of fault messages (label 356).
When FWC1 incorrect operation is detected by the CFDIU, only FWC2 bus is read.
The CFDIU returns to FWC1 bus after a long or a very long CFDIU power cutoff.
The FWC provides the flight phases associated with ECAM warnings and used to generate the flight/ground conditions of the CFDIU and of type 1 systems.

NOTE: In addition to this parameter, it has been seen that the FWC provides:

the fault messages presented to the ECAM with label 357, using the same transmission protocol and the same transmission frequency as label 356 in Normal Mode. This label is permanently read by the CFDIU, message transmission is asynchronous and it is only emitted once for each warning
the fault messages generated by the BITE function which are transmitted by the FWC with label 356 using established protocol.

The FWC1 is declared failed by the CFDIU when "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at FW = 0, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU reads the FWC2 bus and uses this bus to retransmit the flight phases transmitted by the FWC2.
The FWC1 is declared invalid (but not failed) by the CFDIU when "flight phase" label is transmitted with SSM at NCD = 01 or FT = 10, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC1, i.e. received with SSM at NO = 11 and flight phase comprised between 1 and 10. If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation time on the FWC1, the CFDIU uses and retransmits phase 1 at NCD = 01 by default.
During the confirmation time the CFDIU retransmits the last correct value.
the FWC2 is declared out of order or invalid, if after FWC2 switching: FWC2 "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at NCD = 01, FW = 00 or FT = 10, or with flight phase smaller than 1 or greater than 10.
In this case, after the confirmation times on the FWC2, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC2 i.e. received with SSM at NO = 11 and phase comprised between 1 and 10.
If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation times on FWC2, the CFDIU uses and retransmits phase 1 at NCD = 01 by default. During the confirmation times, the CFDIU retransmits the last correct value.

NOTE: - During the confirmation times related to the invalid or failed state, except in the case of CFDIU power cutoff, the CFDIU uses and retransmits at NO = 11 the last correct flight phase received.
- When the invalid or failed state disappears, the CFDIU resumes use and normal transmission of flight phases.
- The command label 227 (NULL/DC2/DC1) directly follows the value of the flight phase transmitted by the CFDIU, whether this phase is transmitted at NO or at NCD.
- After a power-up test of the CFDIU without FWCs, the CFDIU presents the Flight menu or the Ground menu depending on the status of the Flight/Ground discrete; however, it considers itself on the ground (phase 1) as far as its operation is concerned.

(3) Interface with the FDIU and the DMU
The FDIU provides aircraft identification.
This parameter is acquired at CFDIU power on, 45 seconds after CFDIU power on and at the NULL/DC2 maintenance phase transition.
The FDIU and the DMU provide warning information (label 350) to the CFDIU (label 270), which in turn transmits it to the ECAM system. These items of information are permanently acquired by the CFDIU.
The FDIU is declared failed or invalid (= incorrect operation) by the CFDIU when at least one of the labels of the "aircraft identification" parameter is not refreshed or transmitted with incorrect parity, confirmed over 4 seconds (no SSM).
In this case, the CFDIU uses and retransmits in lieu of the incorrect label(s), the last label(s) acquired correctly.
This (these) used and retransmitted label(s) is (are) frozen, as long as it (they) remains (remain) incorrect.
In this case, if a NULL/DC2 occured, the CFDIU acquires the A/C Ident at each flight phase transition.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes characters for its own reports (e.g. printouts) and retransmits 0s by default, for the incorrect label(s) before cutoff.

NOTE: - During the confirmation time related to the incorrect operation, the CFDIU uses and retransmits the last correct labels acquired.
- When the incorrect operation disappears, the CFDIU resumes use and normal transmission of the parameter at the following acquisition (phase transition).

The FDIU or the DMU is declared invalid (but not failed) by the CFDIU when their fault information (label 350) is transmitted at NCD = 01 or FW = 11 or FT = 10, or with a bad parity or is not refresh over 4 seconds.
In this case, after the confirmation time, the CFDIU retransmits at NO = 00 the label 270 with the last correct value acquired on the failed label 350. The label 270 bits corresponding to the failed label 350 are frozen as long as the label is failed. If moreover a CFDIU power cutoff occurs, the CFDIU retransmits 0s by default at NO = 00 for the values corresponding to failed label 350.

(4) Interface with the FAC1
The FAC1 provides the flight number and the departure and arrival airports.
The CFDIU acquires the flight number: after CFDIU power on; 45 seconds after CFDIU power on; at the NULL/DC2 maintenance phase transition, and at each flight phase transitions in flight.
The CFDIU acquires the departure and arrival airports: after CFDIU power on; 45 seconds after CFDIU power on; at each scrutiny cycle on ground; at the NULL/DC2 maintenance phase transition, and at each flight phase transitions in flight.
The FAC1 is declared failed by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is not refreshed or transmitted with incorrect parity, or with a SSM FW (=00) confirmed over 4 seconds.
In this case, after a flight phase transition (+ confirmation), the CFDIU uses and retransmits at NCD = 01, in lieu of the failed label(s), the last label(s) acquired correctly, i.e. received with the correct state during a flight phase transition.
This (these) used label(s) which is (are) retransmitted at NCD = 01, is (are) frozen, even after other flight phase transitions, as long as it (they) remains (remain) incorrect.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes for its own reports (e.g. printout) and retransmits 0s by default at NCD = 01, for the incorrect label(s) before cutoff.
The FAC1 is declared invalid (but not failed) by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is transmitted with an SSM NCD (=01) or FT (=10) confirmed for 4 seconds.
In this case, the CFDIU performs a processing which is identical to that of the previous case.

NOTE: - During the confirmation times related to the invalid or failed state, the CFDIU uses and retransmits at NO = 11 the last correct labels acquired.
- when the invalid or failed state disappears, the CFDIU resumes use and normal transmission of the parameters at the following acquisition.

(5) Interface with the clock
The CFDIU is connected to the clock, located on the center instrument panel, which provides:

GMT/Date
elapsed time
chronometer.

(6) Interface with the FWC
In normal configuration (no fault) the CFDIU permanently reads the FWC1 bus and reads the FWC2 bus cyclicly for the reception of fault messages (label 356).
When FWC1 incorrect operation is detected by the CFDIU, only FWC2 bus is read.
The CFDIU returns to FWC1 bus after a long or a very long CFDIU power cutoff.
The FWC provides the flight phases associated with ECAM warnings and used to generate the flight/ground conditions of the CFDIU and of type 1 systems.

NOTE: In addition to this parameter, it has been seen that the FWC provides:

the fault messages presented to the ECAM with label 357, using the same transmission protocol and the same transmission frequency as label 356 in Normal Mode. This label is permanently read by the CFDIU, message transmission is asynchronous and it is only emitted once for each warning
the fault messages generated by the BITE function which are transmitted by the FWC with label 356 using established protocol.

The FWC1 is declared failed by the CFDIU when "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at FW = 0, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU reads the FWC2 bus and uses this bus to retransmit the flight phases transmitted by the FWC2.
The FWC1 is declared invalid (but not failed) by the CFDIU when "flight phase" label is transmitted with SSM at NCD = 01 or FT = 10, or with flight phase smaller than 1 or greater than 10, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC1, i.e. received with SSM at NO = 11 and flight phase comprised between 1 and 10. If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation time on the FWC1, the CFDIU uses and retransmits phase 1 at NCD = 01 by default.
During the confirmation time the CFDIU retransmits the last correct value.
the FWC2 is declared out of order or invalid, if after FWC2 switching: FWC2 "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at NCD = 01, FW = 00 or FT = 10, or with flight phase smaller than 1 or greater than 10.
In this case, after the confirmation times on the FWC2, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC2 i.e. received with SSM at NO = 11 and phase comprised between 1 and 10.
If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation times on the FWC1 and on the FWC2, the CFDIU uses and retransmits phase 1 at NCD = 01 by default. During the confirmation times, the CFDIU retransmits the last correct value.

(7) Interface with the FDIU and the DMU
The FDIU provides aircraft identification.
This parameter is acquired at CFDIU power on, 45 seconds after CFDIU power on and at the NULL/DC2 maintenance phase transition.
The FDIU and the DMU provide warning information (label 350) to the CFDIU (label 270), which in turn transmits it to the ECAM system. These items of information are permanently acquired by the CFDIU.
The FDIU is declared failed or invalid (= incorrect operation) by the CFDIU when at least one of the labels of the "aircraft identification" parameter is not refreshed or transmitted with incorrect parity, confirmed over 4 seconds (no SSM).
In this case, the CFDIU uses and retransmits in lieu of the incorrect label(s), the last label(s) acquired correctly.
This (these) used and retransmitted label(s) is (are) frozen, as long as it (they) remains (remain) incorrect.
In this case, if a NULL/DC2 occured, the CFDIU acquires the A/C Ident at each flight phase transition.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes characters for its own reports (e.g. printouts) and retransmits 0s by default, for the incorrect label(s) before cutoff.

(8) Interface with the FAC1
The FAC1 provides the flight number and the departure and arrival airports.
The CFDIU acquires the flight number: after CFDIU power on; 45 seconds after CFDIU power on; at the NULL/DC2 maintenance phase transition, and at each flight phase transitions in flight.
The CFDIU acquires the departure and arrival airports: after CFDIU power on; 45 seconds after CFDIU power on; at each scrutiny cycle on ground; at the NULL/DC2 maintenance phase transition, and at each flight phase transitions in flight.
The FAC1 is declared failed by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is not refreshed or transmitted with incorrect parity, or with a SSM FW (=00) confirmed over 4 seconds.
In this case, after a flight phase transition (+ confirmation), the CFDIU uses and retransmits at NCD = 01, in lieu of the failed label(s), the last label(s) acquired correctly, i.e. received with the correct state during a flight phase transition.
This (these) used label(s) which is (are) retransmitted at NCD = 01, is (are) frozen, even after other flight phase transitions, as long as it (they) remains (remain) incorrect.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes for its own reports (e.g. printout) and retransmits 0s by default at NCD = 01, for the incorrect label(s) before cutoff.
The FAC1 is declared invalid (but not failed) by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is transmitted with an SSM NCD (=01) or FT (=10) confirmed for 4 seconds.
In this case, the CFDIU performs a processing which is identical to that of the previous case.

(9) Interface with the clock
The CFDIU is connected to the clock, located on the center instrument panel, which provides:

GMT/Date
elapsed time
chronometer.

(10) Interface with the FWC
In normal configuration (no fault) the CFDIU permanently reads the FWC1 bus and reads the FWC2 bus cyclicly for the reception of fault messages (label 356).
When FWC1 incorrect operation is detected by the CFDIU, only FWC2 bus is read.
The CFDIU returns to FWC1 bus after a long or a very long CFDIU power cutoff.
The FWC provides the flight phases associated with ECAM warnings and used to generate the flight/ground conditions of the CFDIU and of type 1 systems.

NOTE: In addition to this parameter, it has been seen that the FWC provides:

the fault messages presented to the ECAM with label 357, using the same transmission protocol and the same transmission frequency as label 356 in Normal Mode. This label is permanently read by the CFDIU, message transmission is asynchronous and it is only emitted once for each warning
the fault messages generated by the BITE function which are transmitted by the FWC with label 356 using established protocol.

The FWC1 is declared failed by the CFDIU when "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at FW = 0, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU reads the FWC2 bus and uses this bus to retransmit the flight phases transmitted by the FWC2.
The FWC1 is declared invalid (but not failed) by the CFDIU when "flight phase" label is transmitted with SSM at NCD = 01 or FT = 10, or with flight phase smaller than 1 or greater than 10, confirmed over 4 seconds.
In this case, after the confirmation time on the FWC1, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC1, i.e. received with SSM at NO = 11 and flight phase comprised between 1 and 10. If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation time on the FWC1, the CFDIU uses and retransmits phase 1 at NCD = 01 by default.
During the confirmation time the CFDIU retransmits the last correct value.
the FWC2 is declared out of order or invalid, if after FWC2 switching: FWC2 "flight phase" label is not refreshed or transmitted with incorrect parity or with SSM at NCD = 01, FW = 00 or FT = 10, or with flight phase smaller than 1 or greater than 10.
In this case, after the confirmation times on the FWC2, the CFDIU uses and retransmits at NCD = 01 the last correct flight phase received from the FWC2 i.e. received with SSM at NO = 11 and phase comprised between 1 and 10.
If this last correct phase is no longer memorized, i.e. if moreover a CFDIU power cutoff occurs, after the confirmation times on the FWC1 and on the FWC2, the CFDIU uses and retransmits phase 1 at NCD = 01 by default. During the confirmation times, the CFDIU retransmits the last correct value.

(11) Interface with the FDIU and the DMU
The FDIU provides aircraft identification.
This parameter is acquired at CFDIU power on, 45 seconds after CFDIU power on and at the NULL/DC2 maintenance phase transition.
The FDIU and the DMU provide warning information (label 350) to the CFDIU (label 270), which in turn transmits it to the ECAM system. These items of information are permanently acquired by the CFDIU.
The FDIU is declared failed or invalid (= incorrect operation) by the CFDIU when at least one of the labels of the "aircraft identification" parameter is not refreshed or transmitted with incorrect parity, confirmed over 4 seconds (no SSM).
In this case, the CFDIU uses and retransmits in lieu of the incorrect label(s), the last label(s) acquired correctly.
This (these) used and retransmitted label(s) is (are) frozen, as long as it (they) remains (remain) incorrect.
In this case, if a NULL/DC2 occured, the CFDIU acquires the A/C Ident at each flight phase transition.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes characters for its own reports (e.g. printouts) and retransmits 0s by default, for the incorrect label(s) before cutoff.

(12) Interface with the FAC1
The FAC1 provides the flight number and the departure and arrival airports.
The CFDIU acquires the flight number: after CFDIU power on; 45 seconds after CFDIU power on; at the NULL/DC2 maintenance phase transition, and every minute in flight.
The CFDIU acquires the departure and arrival airports: after CFDIU power on; 45 seconds after CFDIU power on; at each scrutiny cycle on ground; at the NULL/DC2 maintenance phase transition, and every minute in flight.
The FAC1 is declared failed by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is not refreshed or transmitted with incorrect parity, or with a SSM FW (=00) confirmed over 4 seconds.
In this case, after a flight phase transition (+ confirmation), the CFDIU uses and retransmits at NCD = 01, in lieu of the failed label(s), the last label(s) acquired correctly, i.e. received with the correct state during a flight phase transition.
This (these) used label(s) which is (are) retransmitted at NCD = 01, is (are) frozen, even after other flight phase transitions, as long as it (they) remains (remain) incorrect.
If moreover a CFDIU power cutoff occurs, the CFDIU uses dashes for its own reports (e.g. printout) and retransmits 0s by default at NCD = 01, for the incorrect label(s) before cutoff.
The FAC1 is declared invalid (but not failed) by the CFDIU when at least one of the labels of the "flight number" or "city pair" parameters is transmitted with an SSM NCD (=01) or FT (=10) confirmed for 4 seconds.
In this case, the CFDIU performs a processing which is identical to that of the previous case.

(13) Interface with the DMC1
The DMC1 provides the engine serial number. This parameter is acquired on CFDIU power-up, 45 s after CFDIU power-up and at NULL/DC2 transition.
The DMC1 is declared failed by the CFDIU when at least one of the labels of the "engine serial number" parameter is not refreshed or transmitted with incorrect parity, or with SSM FW confirmed for 18 seconds.
In this case :

If a good acquisition has already been done, then the CFDIU retransmits at NCD the last labels acquired correctly.
Else if no labels have been acquired before (EEPROM clear), the CFDIU retransmits at NCD the labels with the engine serial number value "0".
This (these) label(s) transmitted at NCD = 01 is (are) frozen, even after other NULL/DC2 transitions, as long as it (they) remains (remain) incorrect.

If moreover a CFDIU power cutoff occurs, the CFDIU retransmits at NCD = 01 the last labels acquired correctly (as this value is memorized in EEPROM). Else if no labels have been acquired before, the CFDIU retransmits at NCD the labels with "0".
The DMC1 is declared invalid (but not failed) by the CFDIU when at least one of the labels of the "engine serial number" parameter is transmitted at with SSM NCD = 01 or FT = 10, confirmed for 4 seconds.
In this case, the CFDIU performs a processing which is identical to that of the previous case.

NOTE: - During the confirmation times related to the invalid or failed state, the CFDIU retransmits at NCD the last correct labels acquired.
- When the invalid or failed state disappears, the CFDIU resumes parameter normal transmission at the following acquisition.

(14) General information

NOTE: The labels used for transmitting these parameters and the transmission rates are indicated in the associated table.

CFDIU - Input/Output Labels List ** ON A/C NOT FOR ALL

D. Interface with the On-Board Printer

(1) Architecture

The on-board printer is located in the cockpit, on the rear right section of the center pedestal.
The printer enables the data, sent by the various systems connected to it, to be printed (multi-input printer).
As the CFDS is itself connected to other aircraft systems, the printer enables the data stored in the CFDIU or in the systems connected to it to be printed.

(2) General rules for printing CFDIU data

The CFDIU has a buffer memory with a capacity equal to one MCDU screen page in which it memorizes the CFDIU page.
The CFDIU controls transmission of the contents of the page displayed.

(3) General rules for printing data from systems connected to the CFDIU

Each system connected to the CFDS supervises printing of the data pages:

The CFDIU memorizes the page displayed and sent by the system.
The CFDIU controls transmission of the contents of the page displayed.

If the quantity of data to be sent to the printer is greater than the capacity of one page, printing is carried out page after page.

The CURRENT LEG REPORT and CURRENT LEG ECAM REPORT information can be printed in flight.

CFDIU - Printer Interface Architecture

CFDIU - Process for Printing a Page

E. Interface with ACARS

(1) Structure of the files transmitted to ACARS

(a) Message structure

1 Imbedded Message Identifier (IMI)
Placed at the beginning of the text to identify its contents.
Only one IMI is necessary for each report to be transmitted.

List of IMIs:

DBN = IMI of DATA BASE NUMBER used for filtering function
FLR = IMI of REAL TIME FAILURE
MPF = IMI of POST FLIGHT REPORT
SMD = IMI of BITE transmission
WRN = IMI of REAL TIME WARNING

2 Imbedded Element Identifier (IEI)
Used to identify and define one or several elements in an IMI.
The two IMI letters are preceded by the delimiter "solidus" (/).

List of IEIs:

AN = IEI of A/C IDENT
DA = IEI of CITY PAIR FROM
DM = IEI of the date and time of file generation
DS = IEI of CITY PAIR TO
FI = IEI of FLIGHT NUMBER
FR = IEI of recorded fault messages
WN = IEI of recorded warning messages

(b) Structure of the POST FLIGHT REPORT

------------------------------------------------------------------

! Character ! Content !

------------------------------------------------------------------

! 1 to 5 ! control/accountability header !

! 6 ! C !

! 7 to 9 ! downlink message sequence code !

! 10 to 12 ! MPF !

! 13 ! / !

! 14 to 16 ! DBN (optional: entered if FILTER MODE) !

! 17 to 31 ! DATA BASE NUMBER (variable)

! 18 ! / !

! 19 , 20 ! AN !

! 21 to 27 ! A/C IDENT !

! 28 ! / !

! 29 , 30 ! FI !

! 31 to 40 ! FLIGHT NUMBER !

! 41 ! / !

! 42 , 43 ! DM !

! 44 ! years (tens) !

! 45 ! years (units) !

! 46 ! months (tens) !

! 47 ! months (units) !

! 48 ! days (tens) !

! 49 ! days (units) !

! 50 ! hours (tens) !

! 51 ! hours (units) !

! 52 ! minutes (tens) !

! 53 ! minutes (units) !

! 54 ! seconds (tens) !

! 55 ! seconds (units) !

! 56 ! / !

! 57 , 58 ! DA !

! 59 to 62 ! DEPARTURE AIRPORT !

! 63 ! / !

! 64 , 65 ! DS !

! 66 to 69 ! DESTINATION AIRPORT !

! 70 ! / !

! 71 , 72 ! WN !

! 73 to 78 ! date of warning occurrence ! !

! 79 to 84 ! time of warning occurrence ! first !

! 85 to 90 ! ATA chapter concerned ! warning !

! 91 , 92 ! flight phase of warning occurrence ! message !

! 93 to x-2 ! text of warning message ! !

! x-1 ! CR ! !

! x ! , !

! x+1 to x+6 ! date of warning occurrence ! second !

! x+7 to x+12 ! time .... ! warning !

! .... ! .... ! message !

! ! , !

! .... ! .... ! last !

! .... ! .... ! warning !

! y-1 ! CR ! message !

! y ! / !

! y+1 to y+2 ! FR !

! y+3 to y+8 ! date of fault occurrence ! !

! .... ! time of fault occurrence ! !

! .... ! ATA chapter concerned ! first !

! .... ! flight phase ! fault !

! .... ! text of fault messages ! message !

! .... ! CR ! !

! .... ! /id source CR, ident CR,..., ident! !

! z-1 ! CR ! !

! z ! / !

! z+1 to z+2 ! FR !

! z+3 to z+8 ! date of fault occurrence ! !

! .... ! .... ! second !

! .... ! .... ! fault !

! .... ! .... ! message !

! . ! CR ! !

! .... ! / !

! .... ! FR !

! .... ! .... ! last !

! .... ! .... ! fault !

! n-1 ! CR ! message !

! n ! ETX !

! (n = 186 max. for a block) !

!______________!_________________________________________________!

------------------------------------------------------------------

! Character ! Content !

------------------------------------------------------------------

! 1 to 5 ! control/accountability header !

! 6 ! C !

! 7 to 9 ! downlink message sequence code !

! 10 to 12 ! FLR !

! 13 ! / !

! 14 , 15 ! FR !

! 16 ! years (tens) ! !

! 17 ! years (units) ! date of failure !

! 18 ! months (tens) ! occurrence !

! 19 ! months (units) ! !

! 20 ! days (tens) ! !

! 21 ! days (units) ! !

! 22 ! hours (tens) ! !

! 23 ! hours (units) ! time of failure !

! 24 ! minutes (tens) ! occurrence !

! 25 ! minutes (units) ! !

! 26 ! seconds (tens) ! !

! 27 ! seconds (units) ! !

! 28 ! ATA chapter (tens) ! !

! 29 ! ATA chapter (units) ! ATA chapter !

! 30 ! ATA section (tens) ! concerned !

! 31 ! ATA section (units) ! !

! 32 ! ATA LRU IDENT (tens) ! !

! 33 ! ATA LRU IDENT (units) ! !

! 34 ! flight phase (tens) ! flight phase of !

! 35 ! flight phase (units) ! failure occurence !

! 36 to n-2 ! text of fault message !

! .... ! /ID source CR, identifier CR, ..., identifier !

! n-1 ! CR !

! n ! ETX !

! (n = 186 max. for a block) !

(d) Structure of the REAL TIME WARNING

------------------------------------------------------------------

! Character ! Content !

------------------------------------------------------------------

! 1 to 5 ! control/accountability header !

! 6 ! C !

! 7 to 9 ! downlink message sequence code !

! 10 to 12 ! WRN !

! 13 ! / !

! 14 , 15 ! WN !

! 16 ! years (tens) ! !

! 17 ! years (units) ! date of warning !

! 18 ! months (tens) ! occurrence !

! 19 ! months (units) ! !

! 20 ! days (tens) ! !

! 21 ! days (units) ! !

! 22 ! hours (tens) ! !

! 23 ! hours (units) ! time of warning !

! 24 ! minutes (tens) ! occurrence !

! 25 ! minutes (units) ! !

! 26 ! seconds (tens) ! !

! 27 ! seconds (units) ! !

! 28 ! ATA chapter (tens) ! !

! 29 ! ATA chapter (units) ! ATA chapter !

! 30 ! ATA subchapter (tens) ! concerned !

! 31 ! ATA subchapter (units) ! !

! 32 ! ATA LRU IDENT (tens) ! !

! 33 ! ATA LRU IDENT (units) ! !

! 34 ! flight phase (tens) ! flight phase of !

! 35 ! flight phase (units) ! warning occurrence !

! 36 to n-2 ! text of warning !

! n-1 ! CR !

! n ! ETX !

! (n = 186 max. for a block) !

(e) Structure of the BITE system pages
(example with TROUBLE SHOOTING DATA of SDAC 1)

------------------------------------------------------------------

! Character ! Content !

------------------------------------------------------------------

! 1 to 5 ! control/accountability header !

! 6 ! C !

! 7 to 9 ! downlink message sequence code !

! 10 to 12 ! SMD !

! 13 ! CR !

! 14 ! LF !

! 15 to 23 ! spaces !

! 24 ! S !

! 25 ! D !

! 26 ! A !

! 27 ! C !

! 28 ! space !

! 29 ! 1 !

! 30 ! CR !

! 31 ! LF !

! 32 ! space !

! 33 ! T !

! 34 ! R !

! 35 ! O !

! 36 ! U !

! 37 ! B !

! 38 ! L !

! 39 ! E !

! 40 ! space !

! 41 ! S !

! 42 ! H !

! 43 ! O !

! 44 ! O !

! 45 ! T !

! 46 ! I !

! 47 ! N !

! 48 ! G !

! 49 ! space !

! 50 ! D !

! 51 ! A !

! 52 ! T !

! 53 ! A !

! 54 ! CR !

! 55 ! LF !

! 56 ! CR !

! 57 ! LF !

! 58 ! space !

! 59 to n-1 ! page content !

! n ! ETX !

! (n = 186 max. for a block) !

(2) Structure of the files transmitted to the ACARS

(a) Message structure

1 Imbedded Message Identifier (IMI)
You can find the IMI at the start of the text to identify its contents.
Only one IMI is necessary for each report that is transmitted.

List of IMIs:

DBN = IMI of DATA BASE NUMBER used for filtering function
FLR = IMI of REAL TIME FAILURE
MPF = IMI of POST FLIGHT REPORT
SMD = IMI of BITE transmission
WRN = IMI of REAL TIME WARNING
PNR = IMI of the CFDIU PART NUMBER
NCP = IMI of the ”NOT COMPLETE” shown at the end of the Post Flight Report (PFR) if the failure memory capacity and/or warning memory capacity is overloaded.

2 Imbedded Element Identifier (IEI)
The IEI is used to identify and specify one or more elements in an IMI.
The delimiter "solidus" (/) comes before the two IMI letters.

List of IEIs:

AN = IEI of A/C IDENT
DA = IEI of CITY PAIR FROM
DM = IEI of the date and time of file generation
DS = IEI of CITY PAIR TO
FI = IEI of FLIGHT NUMBER
FR = IEI of recorded fault messages
WN = IEI of recorded warning messages.

(b) Structure of the POST FLIGHT REPORT

-------------------------------------------------------------------------------

! Character ! Content !Identifier !

-------------------------------------------------------------------------------

! 1 to 5 ! control/accountability header ! !

! 6 ! C ! !

! 7 to 9 ! downlink message sequence code ! !

! 10 to 12 ! MPF ! IMI !

! 13 ! / ! !

! 14 to 16 ! PNR ! IMI !

! 17 to 31 ! CFDIU Part Number ! !

! 32 ! / ! !

! 33 to 35 ! DBN (optional: entered if FILTER MODE) ! IEI !

! 36 to 50 ! DATA BASE NUMBER (always 15 characters) ! !

! 32 or 51 ! / ! !

! 33,34 or 52,53 ! AN ! IEI !

! 35,41 or 54,60 ! A/C IDENT (7 characters) ! !

! 42 or 61 ! / ! !

! 43,44 or 62,63 ! FI ! IEI !

! 45,54 or 64,73 ! FLIGHT NUMBER 10 characters ! !

! 55 or 74 ! / ! !

! 56,57 or 75,76 ! DM ! IEI !

! 58 or 77 ! years (tens) ! !

! 59 or 78 ! years (units) ! Beginning of the leg ! !

! 60 or 79 ! months (tens) ! information (NULL/DC2) ! !

! 61 or 80 ! months (units) ! Maintenance phase transition! !

! 62 or 81 ! days (tens) ! !

! 63 or 82 ! days (units) ! !

! 64 or 83 ! hours (tens) ! !

! 65 or 84 ! hours (units) ! !

! 66 or 85 ! minutes (tens) ! !

! 67 or 86 ! minutes (units) ! !

! 68 or 87 ! seconds (tens) ! !

! 69 or 88 ! seconds (units) ! !

! 70 or 89 ! / ! !

! 71,72 or 90,91 ! DA ! IEI !

! 73,76 or 92,95 ! DEPARTURE AIRPORT ! (4 characters) ! !

! 77 or 96 ! / ! !

! 78,79 or 97,98 ! DS ! IEI !

! 79,82 or 98,101 ! DESTINATION AIRPORT ! (4 characters) ! !

! 83 or 102 ! / ! !

! 84,85 or 103,104! WN ! IEI !

! 86,91 or 105,110! date of warning occurrence ! ! !

! 92,97 or 111,116! time of warning occurrence ! first ! !

! 98,103 or 117,122! ATA chapter concerned ! warning ! !

!104,105 or 123,124! flight phase of warning occurrence! message ! !

!106 or 125 to x-2 ! text of warning message ! ! !

! x-1 ! CR ! ! !

! x ! , (comma) ! !

! x+1 to x+6 ! date of warning occurrence ! second ! !

! x+7 to x+12 ! time .... ! warning ! !

! .... ! .... ! message ! !

! ! CR ! ! !

! ! , (comma) ! ! !

! .... ! .... ! last ! !

! .... ! .... ! warning ! !

! y-1 ! CR ! message ! !

! y ! / ! !

! y+1 to y+2 ! FR ! IEI !

! y+3 to y+8 ! date of fault occurrence ! ! !

! .... ! time of fault occurrence ! ! !

! .... ! ATA chapter concerned ! first ! !

! .... ! flight phase ! fault ! !

! .... ! text of fault messages ! message ! !

! .... ! CR ! ! !

! .... ! /id source CR, ident CR,..., ident! ! !

! z-1 ! CR ! ! !

! z ! / ! !

! z+1 to z+2 ! FR ! IEI !

! z+3 to z+8 ! date of fault occurrence ! ! !

! .... ! .... ! second ! !

! .... ! .... ! fault ! !

! .... ! .... ! message ! !

! . ! CR ! ! !

! .... ! / ! !

! .... ! FR ! IEI !

! .... ! .... ! last ! !

! .... ! .... ! fault ! !

! n ! CR ! message ! !

! ! / ! !

! ! NCP ! IMI !

! ! NOT COMPLETE !Optional text field ! ! !

! ! CR ! End of Report ! ! !

!__________________!______________________________________________!___________!

-------------------------------------------------------------------------------

! Character ! Content !Identifier !

-------------------------------------------------------------------------------

! 1 to 5 ! control/accountability header ! !

! 6 ! C ! !

! 7 to 9 ! downlink message sequence code ! !

! 10 to 12 ! FLR ! IMI !

! 13 ! / ! !

! 14 to 16 ! PNR ! IMI !

! 17 to 31 ! CFDIU.Part.Number ! !

! 32 ! / ! !

! 33, 34 ! FR ! IEI !

! 35 ! years (tens) ! ! !

! 36 ! years (units) ! date of fault ! !

! 37 ! months (tens) ! occurrence ! !

! 38 ! months (units) ! ! !

! 39 ! days (tens) ! ! !

! 40 ! days (units) ! ! !

! 41 ! hours (tens) ! ! !

! 42 ! hours (units) ! time of fault ! !

! 43 ! minutes (tens) ! occurrence ! !

! 44 ! minutes (units) ! ! !

! 45 ! seconds (tens) ! ! !

! 46 ! seconds (units) ! ! !

! 47 ! ATA chapter (tens) ! ! !

! 48 ! ATA chapter (units) ! ATA chapter ! !

! 49 ! ATA section (tens) ! concerned ! !

! 50 ! ATA section (units) ! ! !

! 51 ! ATA LRU IDENT (tens) ! ! !

! 52 ! ATA LRU IDENT (units) ! ! !

! 53 ! flight phase (tens) ! flight phase of ! !

! 54 ! flight phase (units) ! fault occurrence ! !

! 55 to ... ! text of fault message (48 characters max) ! !

! ... ! / ! !

! ... ! ID ! !

! ... ! Source (14 characters max) ! !

! ... ! CR ! !

! ... ! , (comma) ! !

! ... ! First identifier (14 characters max) ! !

! ... ! CR ! !

! ... ! , (comma) ! !

! ... ! Second identifier (14 characters max) ! !

! ... ! CR ! !

! ... ! , (comma) ! !

! ... ! ... ! !

! ... ! Sixth identifier (last one, 14 characters max) ! !

! n ! CR ! !

!_______________!_________________________________________________!___________!

(d) Structure of the REAL TIME WARNING

-------------------------------------------------------------------------------

! Character ! Content !Identifier !

-------------------------------------------------------------------------------

! 1 to 5 ! control/accountability header ! !

! 6 ! C ! !

! 7 to 9 ! downlink message sequence code ! !

! 10 to 12 ! WRN ! IMI !

! 13 ! / ! !

! 14 to 16 ! PNR ! IMI !

! 17 to 31 ! CFDIU.Part.Number ! !

! 32 ! / ! !

! 33, 34 ! WN ! IEI !

! 35 ! years (tens) ! ! !

! 36 ! years (units) ! date of warning ! !

! 37 ! months (tens) ! occurrence ! !

! 38 ! months (units) ! ! !

! 39 ! days (tens) ! ! !

! 40 ! days (units) ! ! !

! 41 ! hours (tens) ! ! !

! 42 ! hours (units) ! time of warning ! !

! 43 ! minutes (tens) ! occurrence ! !

! 44 ! minutes (units) ! ! !

! 45 ! seconds (tens) ! ! !

! 46 ! seconds (units) ! ! !

! 47 ! ATA chapter (tens) ! ! !

! 48 ! ATA chapter (units) ! ATA chapter ! !

! 49 ! ATA subchapter (tens) ! concerned ! !

! 50 ! ATA subchapter (units) ! ! !

! 51 ! ATA LRU IDENT (tens) ! ! !

! 52 ! ATA LRU IDENT (units) ! ! !

! 53 ! flight phase (tens) ! flight phase of ! !

! 54 ! flight phase (units) ! warning occurrence ! !

! 55 to n-2 ! text of warning (24 characters max) ! !

! n ! CR ! !

!_______________!_________________________________________________!___________!

(e) Structure of the BITE system pages
(example with TROUBLE SHOOTING DATA of SDAC 1)

------------------------------------------------------------------

! Character ! Content !

------------------------------------------------------------------

! 1 to 5 ! control/accountability header !

! 6 ! C !

! 7 to 9 ! downlink message sequence code !

!10 to 12 ! SMD !

! 13 ! CR !

! 14 ! LF !

!15 to 23 ! spaces !

! 24 ! S !

! 25 ! D !

! 26 ! A !

! 27 ! C !

! 28 ! space !

! 29 ! 1 !

! 30 ! CR !

! 31 ! LF !

! 32 ! space !

! 33 ! T !

! 34 ! R !

! 35 ! O !

! 36 ! U !

! 37 ! B !

! 38 ! L !

! 39 ! E !

! 40 ! space !

! 41 ! S !

! 42 ! H !

! 43 ! O !

! 44 ! O !

! 45 ! T !

! 46 ! I !

! 47 ! N !

! 48 ! G !

! 49 ! space !

! 50 ! D !

! 51 ! A !

! 52 ! T !

! 53 ! A !

! 54 ! CR !

! 55 ! LF !

! 56 ! CR !

! 57 ! LF !

! 58 ! space !

! 59 to n-1 ! page content !

! n ! ETX !

!(n = 186 max. ! !

!for a block) ! !

F. Interface with the Systems which Provide Aircraft Configuration
(AMU, CIDS1, FWC1 and DMC1)
The AMU, CIDS1, FWC1 and DMC1 provide aircraft configuration information. These parameters are acquired 45 s after CFDIU power-up, and on flight phase 1/2 transition.
(AMU, CIDS1, FWC1, DMC1, SDCU/CIDS 1&2, DMU/FDIMU, ZONE CTL/ASCS2, ILS/MMR and GPWC/T2CAS-TAWS)
The AMU, CIDS1, FWC1 and DMC1 provide aircraft configuration information. These parameters are acquired 45 s after CFDIU power-up, at the NULL/DC2 maintenance phase transition.

G. Interface with the Multi Mode Receiver (MMR)

The MMR is installed on the aircraft in place of the ILS. To be in MMR configuration, the CFDIU only needs one of the two labels 271 MMR1 and MMR2.

NOTE: When the MCDU MENU page comes into view, you must wait between 30s and a maximum of one minute before you can push the line key adjacent to the CFDS indication to get access to the MMR BITE through the SYSTEM REPORT/TEST/NAV menu pages. In this way, these pages will show the actual aircraft configuration. The MMR item is valid when the MMR is powered up at the same time as the CFDIU or within 15s after CFDIU powerup. After 15s, the CFDIU must be reset.

There is no modification in the failure correlation processing. Access to the GPSSU BITE through the SYSTEM REPORT/TEST/NAV item is active depending on the state of the GPSSU1(2) installation pin programming (M/11A - T/11K).

H. Interface with the Air Traffic Service Unit (ATSU)

When the ATSU is connected, it fulfills all the functions provided by the ACARS MU.

Particulars:

The ATSU is connected to the ACARS MU input.

The ATSU must be pin-programmed.

System specificity:

In this case, the CFDIU specifies, on the aircraft configuration labels, ATSU aircraft installation and ACARS MU aircraft installation.

** ON A/C NOT FOR ALL

6. Component Description

A. Architecture FIN: 1-TW

CFDIU - Internal Architecture ** ON A/C NOT FOR ALL

CFDIU - Exploded View ** ON A/C NOT FOR ALL

The CFDIU consists of two distinct channels:

a normal channel which ensures operation in normal conditions (no fault)
a back-up channel which ensures restricted operation when the normal channel is faulty.

These two channels are located in a 4MCU housing and they are physically segregated within the housing

B. Architecture FIN: 1-TW

The CFDIU consists of one channel which ensures operation in normal conditions.

C. Characteristics of the Normal Channel FIN: 1-TW
The normal channel consists of:

A power supply unit: -15V, +15V, +5V.
2 input/output boards
A logic/monitoring and interface board essentially consisting of a normal/back-up channel selection device
A CPU1 board

The normal channel interfaces all the aircraft systems connected to the CFDS.
These systems are linked directly or via a computer, which acts as a concentrator, to the CFDS.
The normal channel ensures all maintenance functions for all aircraft systems connected, as long as this channel is not declared faulty.

D. Characteristics of the Back-up Channel FIN: 1-TW
The back-up channel consists of:

A power supply unit: -15V, +15V, +5V.
1 input/output board consisting of two segregated channels
A CPU2 board

The back-up channel constitutes partial normal channel redundancy. It only interfaces a limited number of systems among the main aircraft systems from an operational point of view and it only ensures the SYSTEM REPORT TEST function (and all the system functions accessible from this function).
The side 1 systems are connected to channel 1 of the input/output board and side 2 systems are connected to channel 2, thus ensuring system segregation.

E. Switching Logic FIN: 1-TW
In normal operation only the normal channel is energized. In the event of fault in this channel, switching to the back-up channel is immediately and automatically performed.
In the event of minor fault (input/output boards), automatic switching is not performed; it is only carried out manually on the ground using the MCDU so as not to lose the functions of the main CFDS menu for systems connected to valid input/output boards.

Indications:
A normal channel fault is indicated by means of a discrete output with the following characteristics:
Ground/Open circuit
Ground = normal channel operative
Control:
Switching to the back-up channel is ensured by means of an input discrete with the following characteristics:
Ground/Open circuit
Ground = switching to back-up channel.

** ON A/C NOT FOR ALL

7. Operation
The maintenance system operates using the Menus presented on the MCDU. The operator selects the relevant functions or reports in these Menus.
There are two types of maintenance report:

reports proper to the CFDIU
reports proper to the system BITEs.

Furthermore, these reports can be printed, or transmitted to ground.
The maintenance system operates using the Menus presented on the MCDU. The operator selects the relevant functions or reports in these Menus.

There are two types of maintenance report:

reports proper to the CFDIU
reports proper to the system BITEs.

Furthermore, these reports can be printed, or transmitted to ground.

A. Reports Proper to the CFDIU
The reports proper to the CFDIU form the main CFDS menu.
On the ground the menu is:

CFDIU - CFDS Menu on Ground ** ON A/C NOT FOR ALL

LAST LEG REPORT !

LAST LEG ECAM REPORT !

PREVIOUS LEGS REPORT ! In normal operation

AVIONICS STATUS !

SYSTEM REPORT/TEST !

POST FLIGHT REPORT !

! Item added in the event of clock

GMT/DATE INIT ! fault plus a long power cutoff

! (> 200 ms)

! Item added in the event of CFDIU

BACKUP MODE ! normal channel fault

PFR FILTER PROGRAM ! Filter activation

! Filter printing

The reports proper to the CFDIU form the main CFDS menu.

On the ground the menu is:

CFDIU - CFDS Menu on Ground ** ON A/C NOT FOR ALL

LAST LEG REPORT !

LAST LEG ECAM REPORT !

PREVIOUS LEGS REPORT ! In normal operation

AVIONICS STATUS !

SYSTEM REPORT/TEST !

POST FLIGHT REPORT !

! Item added in the event of clock

GMT/DATE INIT ! fault plus a long power cutoff

! (> 200 ms)

PFR FILTER PROGRAM ! Filter activation

! Filter printing

PASSWORD CHANGE ! Password modification

The reports proper to the CFDIU form the main CFDS menu.

On the ground, the menu is:

CFDIU - CFDS Menu on Ground ** ON A/C NOT FOR ALL

LAST LEG REPORT !

LAST LEG ECAM REPORT !

PREVIOUS LEGS REPORT ! In normal operation

AVIONICS STATUS !

SYSTEM REPORT/TEST !

POST FLIGHT REPORT !

! Item only displayed in case of clock

GMT/DATE INIT ! fault

AVIONICS CONFIG REPORT !

REPORTS PROGRAMMING ! ACARS MU (or ATSU) programming

(IF ACARS MU OR ATSU ! and printing functions programming

INSTALLED) !

PFR FILTER PROGRAM ! Filter activation

! Filter printing

PASSWORD CHANGE ! Password modification

In flight the menu is:

CURRENT LEG REPORT ! In normal operation

CURRENT LEG ECAM REPORT !

GMT/DATE INIT ! Item added in the event of clock

! failure, plus long power cutoff.

PFR FILTER PROGRAM ! Filter printing

CFDIU - CFDS Menu in Flight ** ON A/C NOT FOR ALL

These different maintenance reports are transmitted by the CFDIU to the MCDU and they are principally intended for line maintenance.
In flight the menu is:

CURRENT LEG REPORT !

CURRENT LEG ECAM REPORT ! In normal operation

CURRENT FLIGHT REPORT !

GMT/DATE INIT ! Item added in the event of clock

! failure, plus long power cutoff.

REPORTS PROGRAMMING ! ACARS MU (or ATSU) programming

(IF ACARS MU or ATSU ! and printing functions programming

INSTALLED) !

PFR FILTER PROGRAM ! Filter printing

PASSWORD CHANGE ! Password modification

CFDIU - CFDS Menu in Flight ** ON A/C NOT FOR ALL

These different maintenance reports are transmitted by the CFDIU to the MCDU and they are principally intended for line maintenance.

B. Reports Proper to the CFDIU - Description

(1) LAST/CURRENT LEG REPORT

CFDIU - LAST (or CURRENT) LEG REPORT

The purpose of this item, which is part of the main maintenance menu, is to present, in flight or on the ground, the internal fault messages (class 1 and 2), concerning all systems, occured during the last or the current flight, and the list of systems affected by this fault that are called identifiers.
Capacity : 40 failures.
These messages contain the text of the internal fault i.e. the faulty LRU and its ATA reference, associated with the time at which the fault occurred and the flight phase during which it occurred.
The date is entered in the header.
Access to the identifiers can be gained by pressing the line key adjacent to the fault, so as to help identification of the fault.
This information is displayed on the MCDU in clear when this function is activated by the operator.
On the ground, the item is presented under the title LAST LEG REPORT, in flight it is presented under the title CURRENT LEG REPORT.

(2) LAST/CURRENT LEG ECAM REPORT

CFDIU - LAST (or CURRENT) LEG ECAM REPORT

The purpose of this item, which is part of the main maintenance menu, is to present, in flight or on the ground, the warning messages (class 1 and 2 faults) displayed on the upper ECAM display unit during the last or the current flight. These are the primary or independent warnings.
When several identical and consecutive warnings are transmitted, the CFDIU memorizes the first occurence only and carries out counting with a maximum of 8.
Capacity: 40 warnings.
These messages contain the ECAM warning associated with its ATA reference, the time and the flight phase at which the fault occurred. The date is entered in the header.
This information is displayed on the MCDU in clear when this function is activated by the operator.
On the ground, the item is presented under the title LAST LEG ECAM REPORT, in flight it is presented under the title CURRENT LEG ECAM REPORT.

(3) PREVIOUS LEGS REPORT

CFDIU - PREVIOUS LEGS REPORT

The purpose of this item, which is part of the main maintenance menu, is to present, on the ground only, the internal fault messages (class 1 and 2) concerning all systems, appeared during the previous 64 flights (fault history). This item is the "sum" of LAST LEG REPORT items over several flights.
These fault messages contain the names of the LRUs affected by a fault associated with the time and date at which the fault occurred, the flight phase during which it occurred, the flight number (0 to 63) and the ATA references of the faulty systems.
Aircraft identification is entered in the header.
This information is displayed on the MCDU in clear when this function is activated by the operator.

(4) AVIONICS STATUS

CFDIU - AVIONICS STATUS

The purpose of this item, which is part of the main maintenance menu, is to present, on the ground and in real time, the identity of systems that are affected by an internal or external fault (class 1, 2 or 3).
(CLASS 3) is displayed next to the name of a system that is affected by at least one class 3 fault.
These messages contain the names of systems affected by a fault when this function is executed, or a NO X DATA message when the system X bus is no longer valid.
This information is displayed on the MCDU in clear when this function is activated by the operator.

(5) POST FLIGHT REPORT

CFDIU - POST FLIGHT REPORT ** ON A/C NOT FOR ALL

The purpose of this item, which is part of the main maintenance menu, is to present, in a single report after the flight, the ECAM warnings (primary and independent) and the fault messages (class 1 and 2) of the last flight (so as to permit correlation). This item is the "sum" of LAST LEG REPORT and LAST LEG ECAM REPORT items.
So these messages are separated into two parts; the first part contains the ECAM warnings associated with the time, the flight phase and the ATA reference, the second contains the failed LRUs associated with the time, the ATA reference and the identifiers.
Aircraft identification, the date, the flight time, the flight number (airline) and the departure and arrival airports are included in the header.
This information is printed out directly by the printer in clear (not displayed on the MCDUs), when this function is activated by the operator or automatically at DC1/NULL or DC2/NULL transition (refer to figures of AMM 31-32-00, System Description, para. The Complete System : CFDS, Normal Mode, Operation of Type 1 systems).

(6) CURRENT FLIGHT REPORT

CFDIU - Current Flight Report ** ON A/C NOT FOR ALL

The purpose of this item is to enable manual printing or transmission through ACARS MU or ATSU of all current faults and warnings which occured since the beginning of the flight and up to printing and/or transmission request.

(7) GMT/DATE INIT

CFDIU - GMT/DATE INITIALIZATION

In the event of clock fault, a flag comes into view on the main clock.
The CFDIU displays the time on the ECAM display unit.
If, in addition, there is a long power cutoff (> 200 ms), the CFDS adds the GMT/DATE INIT item in its menu, enabling the crew to reinitialize the time and date on the MCDU.
When the main clock is failed, and there is a long power interrupt (> 200ms), the CFDIU sends as GMT 79:99 (displayed on the ECAM display unit, and recorded by each system).

(8) PFR/FILTER PROGRAM

PFR/FILTER PROGRAM - Sheet 1/4 ** ON A/C NOT FOR ALL

lav0 ** ON A/C NOT FOR ALL

CFDIU - POST FLIGHT REPORT (Not Filtered) - Sheet 2/4 ** ON A/C NOT FOR ALL

CFDIU - Printing of Memorized Filter - Sheet 3/4 ** ON A/C NOT FOR ALL

CFDIU - Pinting of Memorized Filter - Sheet 3/4 ** ON A/C NOT FOR ALL

CFDIU - POST FLIGHT REPORT (Filtered) - Sheet 4/4 ** ON A/C NOT FOR ALL

The purpose of this function, which is part of main maintenance menu, is to improve the operational use of the POST FLIGHT REPORT, CURRENT/LAST LEG ECAM REPORT and LAST LEG REPORT printed at the end of the flight as well as the real-time fault and warning information transmitted by the ACARS, by filtering all the spurious or unjustified faults/warnings.
The filter data base is activated after correct uploading. It can be de-activated then activated again through the second page of the main maintenance menu by pushing line key 4L then 2L.
Action on line key 3R, when the PFR/FILTER PROGRAM page is shown, enables printing of the memorized data base.

(9) PASSWORD CHANGE

CFDIU - PASSWORD CHANGE ** ON A/C NOT FOR ALL

The purpose of this function is to enable customized access to REPORTS PROGRAMMING and PFR FILTER PROGRAM pages through a password.

Two modes can be used:

Transparent mode: free access
Password mode: access through a password.

The operator can exit the transparent mode to use the password mode and vice versa.
The transparent mode is active at component delivery.
If there is no password, the operator must make a new password.
First, the operator must enter eight #X# symbols (XXXXXXXX) in the field LAST PASSWORD.
Then it is possible to enter a new password in the fields NEW PASSWORD and CONFIRM PASSWORD.
The password must have eight symbols maximum.
If the password contains more than eight symbols the system uses only the first seven symbols and the last one.
To give the password or to get access to the protected menu, operator must push the MCDU key.
Each time when the operator pushes the MCDU key, symbol #+# comes into view on the scratchpad.
When changing the password:

. OK means "password corrected and accepted"

. ERROR means "not OK"
The three fields LAST PASSWORD, NEW PASSWORD and CONFIRM PASSWORD must be correctly filled in (i.e. three OK indications) to validate the new password.

When the password entered cannot be validated, the ERROR message is displayed in the scratchpad.

(10) SYSTEM REPORT/TEST

CFDIU - SYSTEM REPORT/TEST ** ON A/C NOT FOR ALL

The purpose of this function, which is part of the main maintenance menu, is to ensure, on the ground only, a dialog between the MCDUs and each of the systems connected to the CFDS.
The text presented by the CFDIU is a list of all the systems connected to the CFDS, in ATA chapter order.
Pressing the line key adjacent to a system indication enables access to the menu specific to the system. These system menus constitute the second category of functions which are the functions proper to the system BITEs.

(11) Avionics Configuration Report

Avionics Configuration Report ** ON A/C NOT FOR ALL

The purpose of this item, which is part of the main maintenance menu, is to present into a single report, all the LRU identification information sent by some type 1 & 2 BITE. It also contains the information sent by the clock and MCDU.

For each equipment related to the ACR, the data that follow are given:

The ATA (6 digits),
The equipment name,
The P/N, S/N, DB/N1 and DB/N2 if available.

It is possible to establish this report for a given ATA by entering the first two digits on the scratchpad before starting the function.

This function is available on ground only and can only be triggered manually. (No automatic updating)

NOTE: The ACR is not memorized in NVM.

C. Reports Proper to the CFDIU - Establishment
These various reports are established by the CFDIU:
These various reports are established by the CFDIU:

(1) LAST/CURRENT LEG REPORT
This report is established using systems Normal Mode and CFDIU in flight configurations, i.e. using the permanent memorization in the CFDIU of faults transmitted by the systems during the last or current flight.

(2) LAST/CURRENT LEG ECAM REPORT
This report is established by the memorization in the CFDIU of the warnings transmitted permanently by the FWC in flight.

(3) PREVIOUS LEGS REPORT
This report is established by the memorization in the CFDIU of the LAST LEG REPORT of several flights (64).

(4) POST FLIGHT REPORT
This report is established by the transmission of the LAST LEG and LAST LEG ECAM REPORTS to the printer by the CFDIU.

(5) LAST/CURRENT LEG REPORT

This report is established using systems Normal Mode and CFDIU in flight configurations, i.e. using the permanent memorization in the CFDIU of faults transmitted by the systems during the last or current flight.

(6) LAST/CURRENT LEG ECAM REPORT

This report is established by the memorization in the CFDIU of the warnings transmitted permanently by the FWC in flight.

(7) PREVIOUS LEGS REPORT

This report is established by the memorization in the CFDIU of the LAST LEG REPORT of several flights (64).

(8) POST FLIGHT REPORT/CURRENT FLIGHT REPORT

This report is established by the transmission of the LAST/CURRENT LEG and LAST/CURRENT LEG ECAM REPORTS to the printer by the CFDIU.

(9) AVIONICS STATUS
This report is established by means of the permanent reading of systems status by the CFDIU, by monitoring refreshment of input buses, or by reading these buses and fault message detection, in Normal Mode.
Whenever report bus scanning is made by the CFDIU, the table giving the systems status is updated.
When one of these functions is selected by the operator, these data are transmitted once by the CFDIU to the MCDU (or the printer for the POST FLIGHT REPORT).

(10) SYSTEM REPORT/TEST
The system Report/Test function is established using data that are stored once and for all in the CFDIU (list of systems) and data that are stored once and for all in the system BITE (Type 1 system menu), or that are stored once and for all in the CFDIU (Type 2 and 3 system pseudo menus).
When the operator selects this function, the CFDIU transmits the list of systems to the MCDU once, and then when a system is selected:

the system transmits its menu once on its output bus to the MCDU via the CFDIU (for a Type 1 system).
or, the CFDIU itself, transmits the selected system menu once to the MCDU (for a Type 2 or 3 system).

Among the functions proper to the CFDIU, only the SYSTEM REPORT TEST function (access to a system menu) for a Type 1 system implies an action on the system (request for transmission of data).

D. Reports Proper to the CFDIU - Periods for Establishment
Periods for the establishment of these reports and availability on the MCDU

CFDIU - Establishment and Availability of the Reports Listed in the CFDS menu by the MCDU - Sheet 1/2 ** ON A/C NOT FOR ALL

CFDIU - Establishment and Availability of the Reports Listed in the CFDS menu by the MCDU - Sheet 2/2 ** ON A/C NOT FOR ALL

The figures referenced above detail the periods when these reports are memorized by the CFDIU, and when they are available on the MCDU.
It should be noted that only the LAST LEG REPORT and LAST LEG ECAM REPORT functions are accessible in flight. The other CFDS functions are only available on the ground.
Periods for the establishment of these reports and availability on the MCDU

CFDIU - Establishment and Availability of the Reports Listed in the CFDS menu by the MCDU - Sheet 1/2 ** ON A/C NOT FOR ALL

CFDIU - Establishment and Availability of the Reports Listed in the CFDS menu by the MCDU - Sheet 2/2 ** ON A/C NOT FOR ALL

The figures referenced above detail the periods when these reports are memorized by the CFDIU, and when they are available on the MCDU.

It should be noted that only the CURRENT LEG REPORT, CURRENT LEG ECAM REPORT and CURRENT FLIGHT REPORT functions are accessible in flight.

The other CFDS functions are only available on the ground.

E. Reports Proper to System BITEs Available on the MCDU
Access to these reports is only possible on the ground.
The reports proper to the BITE constitute the SYSTEM MENU.
These different maintenance reports are mainly intended for maintenance at the main base.
They depend on the type of system (1, 2, or 3) and the requirements of each system.

(1) Type 1 systems
For these systems, the basic functions are:

LAST LEG REPORT
PREVIOUS LEGS REPORT
LRU IDENTIFICATION

Among the optional functions, there are:

GROUND SCANNING
TROUBLE SHOOTING DATA
CLASS 3 FAULTS
TEST.

CFDIU - Type 1 System Report ** ON A/C NOT FOR ALL

These functions constitute the system MENU MODE and they are displayed on the MCDU by the system itself.

(a) Description of reports

CFDIU - Type 1 System Report - Description

1 LAST LEG REPORT

CFDIU - Type 1 System Report - Description

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground only, the internal and external fault messages concerning this system, appeared during the last flight (similar to the CFDIU function with the same name).
Maximum capacity: 30 faults.
These fault messages contain the name of the faulty LRU associated with the time at which the fault occurred and the ATA reference.
The date is indicated in the header.
This information is presented on the MCDU in clear, when this function is activated by the operator.

2 PREVIOUS LEGS REPORT

CFDIU - Type 1 System Report - Description

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground only, the internal and external fault messages concerning this system, appeared during the previous 64 flights (similar to the CFDIU function with the same name). This function gives the "sum" of the LAST LEG REPORT items over several flights.
These fault messages contain the name of the faulty LRU associated with the time and date at which the fault occurred, the flight number (1 to 64) and the ATA reference.
Aircraft identification is included in the header.
This information is presented on the MCDU in clear when this function is activated by the operator.

3 LRU IDENTIFICATION

CFDIU - Type 1 System Report - Description

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground only, the PART NUMBER of the LRUs.

4 GROUND SCANNING

CFDIU - Type 1 System Report - Description

CFDIU - LRU IDENTIFICATION

CFDIU - LRU IDENTIFICATION ** ON A/C NOT FOR ALL

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground only, the internal and external faults concerning this system, present when the request is made.

NOTE: The ground Scanning function can be used as an additional mean to track intermittent faults and to confirm faults on ground.

5 TROUBLE SHOOTING DATA

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground only, complementary information concerning the faults.
These messages contain the data constituting a snapshot of the system environment when the fault occurs or contain parameters internal to the computer (example: aircraft configuration, valve positions, ...).
This information is presented on the MCDU in coded language when this function is activated by the operator.

6 CLASS 3 FAULTS

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION

The purpose of this function, which is part of the Type 1 system menus, is to present, on the ground, CLASS 3 FAULTS messages concerning this system, appeared during previous flights.
These fault messages contain the name of the equipment affected by a CLASS 3 FAULTS associated with the time, the date, the flight number and the ATA reference.
This function is similar to the PREVIOUS LEGS REPORT but only covers CLASS 3 FAULTS.
This information is presented on the MCDU in clear when this function is activated by the operator.

7 TEST

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION

The purpose of this function, which is part of the Type 1 system menus, is double:

Initiation of a system test (there may be several) on the MCDU.
Display on the MCDU of the test results, i.e.: the fault message corresponding to the equipment found faulty by the test or, the message indicating correct operation of the system.

(b) Report establishment mode
These different reports are established by the systems:

LAST LEG REPORT
TROUBLE SHOOTING DATA
CLASS 3 FAULTS

These reports are established using Normal Mode operation of the system in flight, i.e. using the permanent memorization in the system of faults detected during the last 64 flights.
The first of these reports concerns zone 1 of the BITE; the second concerns zone 2 and the third concerns zone 5.

1 PREVIOUS LEGS REPORT
This report is constituted by the memorization in the system of the LAST LEG REPORT of several flights (64). This report concerns zone 1 of the BITE.

2 GROUND SCANNING
This report is established by forcing operation in system Normal Mode, when on the ground (simulation of a flight command (DC1), when on the ground, transmitted on label 227 by the CFDIU).
This report concerns zone 3 of the BITE.

3 LRU IDENTIFICATION
This report is established using data memorized once and for all in the system BITE.
When one of these functions is selected by the operator, the corresponding data are transmitted once by the system to the MCDU (via the CFDIU).

4 TEST
This report is established using data only available after execution of the test activated by the operator and transmitted once by the system to the MCDU (via the CFDIU) (data not memorized by the BITE).
For all these functions the CFDIU is only used as an interface between the system and the MCDU. It displays the data transmitted by the system and corresponding to the function selected on the MCDU.
All these functions, proper to a Type 1 system BITE, involve an action on the system ( request for transmission of data).

CFDIU - Establishment and Availability of the Reports - Type 1 and 2 Systems ** ON A/C NOT FOR ALL

CFDIU - Establishment and Availability of the Reports - Type 1 and 2 systems ** ON A/C NOT FOR ALL

The figures referenced above detail the periods when these reports are memorized by the system and when they are available on the MCDU.
It should be noted that the BITE functions are only available on the ground.

(2) Type 2 systems
For these systems, the basic functions is the LAST LEG REPORT.
Among the optional functions, there are:

CLASS 3 FAULTS
TEST

CFDIU - Type 2 System Report ** ON A/C NOT FOR ALL

Unlike Type 1 systems, Type 2 systems do not have a Menu Mode: these functions are presented on the MCDU by the CFDIU (pseudo Menu Mode).

(a) Description of reports
The contents of these functions is the same as for Type 1 systems but their presentation is slightly different:

1 LAST LEG REPORT

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

The fault messages contain the name of the faulty LRU associated with the ATA reference (the time at which the failure occurred is not displayed).

2 CLASS 3 FAULTS

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

The fault messages contain the name of the faulty equipment associated with the ATA reference.

3 TEST

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

Identical to Type 1 system.

(b) Report establishment mode
These different reports are established by the systems.
The LAST LEG REPORT and the CLASS 3 FAULTS are established using Normal Mode operation of the system in flight and on the groundi.e. using the permanent memorization in the system of faults detected during the last flight.
These reports concern zones 1 and 3 of the BITE.
When one of these functions is selected by the operator, the corresponding data are read by the CFDIU and displayed by the latter on the MCDUs (pseudo Menu Mode).
The test function is established using data only available after execution of the test activated by the operator via the MCDU and the CFDIU and transmitted three times by the system to the CFDIU (data not memorized by the BITE and transmitted in addition to the previous fault data).
For all these functions, the CFDIU is no longer only used as an interface between the system and the MCDU: it reads, on the system-to-the-CFDIU bus, the data transmitted by the system and corresponding to the function selected, it then displays them on the MCDU.
Among the functions proper to the BITE of a Type 2 system, only the TEST function implies an action on the system (request for transmission of data).

CFDIU - Establishment and Availability of the Reports - Type 1 and 2 Systems ** ON A/C NOT FOR ALL

CFDIU - Establishment and Availability of the Reports - Type 1 and 2 systems ** ON A/C NOT FOR ALL

The figures referenced above detail the periods when these reports are memorized by the system and when these reports are available on the MCDU.
It should be noted that these BITE functions are only available on the ground.

(3) Type 2 systems
For these systems, the basic functions is the LAST LEG REPORT.
Among the optional functions, there are:

CLASS 3 FAULTS
TEST
LRU IDENTIFICATION

CFDIU - Type 2 System Report ** ON A/C NOT FOR ALL

Unlike Type 1 systems, Type 2 systems do not have a Menu Mode: these functions are presented on the MCDU by the CFDIU (pseudo Menu Mode).

(a) Description of reports
The contents of these functions is the same as for Type 1 systems but their presentation is slightly different:

1 LAST LEG REPORT

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

The fault messages contain the name of the faulty LRU associated with the ATA reference (the time at which the failure occurred is not displayed).

2 CLASS 3 FAULTS

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

The fault messages contain the name of the faulty equipment associated with the ATA reference.

3 TEST

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

Identical to Type 1 system.

(b) Report establishment mode
These different reports are established by the systems.
The LAST LEG REPORT and the CLASS 3 FAULTS are established using Normal Mode operation of the system in flight and on the groundi.e. using the permanent memorization in the system of faults detected during the last flight.
These reports concern zones 1 and 3 of the BITE.
The LRU IDENTIFICATION is established using the LRU IDENTIFICATION frame sent continuously through label 354 by the systems. As this label is not mandatory, it could happen that there is no data to be displayed. In this case, the CFDIU displays a default MCDU page containing the message 'DATA NOT AVAILABLE'.
When one of these functions is selected by the operator, the corresponding data are read by the CFDIU and displayed by the latter on the MCDUs (pseudo Menu Mode).
The test function is established using data only available after execution of the test activated by the operator via the MCDU and the CFDIU and transmitted three times by the system to the CFDIU (data not memorized by the BITE and transmitted in addition to the previous fault data).
For all these functions, the CFDIU is no longer only used as an interface between the system and the MCDU: it reads, on the system-to-the-CFDIU bus, the data transmitted by the system and corresponding to the function selected, it then displays them on the MCDU.
Among the functions proper to the BITE of a Type 2 system, only the TEST function implies an action on the system (request for transmission of data).

CFDIU - Establishment and Availability of the Reports - Type 1 and 2 systems ** ON A/C NOT FOR ALL

(4) Type 3 systems

CFDIU - Type 3 System Report ** ON A/C NOT FOR ALL

For these systems, the only possible function is the TEST function (for the GCU EMER AND ICE DETECTOR 1 AND 2) or RESET (for the 3 TRs).
The Type 3 systems do not have a Menu Mode: these functions are presented on the MCDU by the CFDIU.
Their establishment mode is different from that of Type 1 and 2 systems.
The Test or Reset function is established using data only available after execution of the Test or the Reset (not memorized by the BITE) that are transmitted by the system to the CFDIU during a certain time (a few hundred ms) on its output discrete.
When these functions are selected by the operator, the CFDIU initiates the Test or the Reset via the CFDIU-to-the system discrete and then reads the result on the system-to-the CFDIU discrete (= discrete status) and creates a message (correct operation or fault) on the MCDU.
These functions imply an action on the system.

(5) Type 3 systems

CFDIU - Type 3 System Report ** ON A/C NOT FOR ALL

For these systems, the only possible function is the TEST function (for the GCU emergency and DLRB/DLS) or RESET (for the 3 TRs).

The Type 3 systems do not have a Menu Mode: these functions are presented on the MCDU by the CFDIU.

Their establishment mode is different from that of Type 1 and 2 systems.

The Test or Reset function is established using data only available after execution of the Test or the Reset (not memorized by the BITE) that are transmitted by the system to the CFDIU during a certain time (a few hundred ms) on its output discrete.

When these functions are selected by the operator, the CFDIU initiates the Test or the Reset via the CFDIU-to-the system discrete and then reads the result on the system-to-the CFDIU discrete (= discrete status) and creates a message (correct operation or fault) on the MCDU.

These functions imply an action on the system.

NOTE: Regarding DLRB/DLS, if the DLS display does not show the STANDBY indication, the NO RESPONSE message is displayed in the scratchpad and the test cannot be executed.

F. Printing of CFDIU and System Reports

(1) Control of transmission of the contents of the page displayed by the CFDIU
The CFDIU assigns the 6R line key PRINT * to the command and ensures transmission of data towards the printer.

CFDIU - LAST (or CURRENT) LEG REPORT ** ON A/C NOT FOR ALL

CFDIU - PREVIOUS LEGS REPORT ** ON A/C NOT FOR ALL

(2) Control of transmission of the contents of the page displayed by a system

(a) Type 1 systems
The system assigns the 6R line key PRINT > to the command and the CFDIU transmits the page memorized to the printer:

if it receives the code of the 6R key (PRINT key on the MCDU),
and if coding of bits 23 and 24 of the initial STX word of the page is other than 23 at 0 and 24 at 1.

CFDIU - Type 1 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION ** ON A/C NOT FOR ALL

(b) Type 2 and 3 systems
The CFDIU assigns the 6R line key to the command and ensures transmission of data to the printer for these systems.

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 3 System Report ** ON A/C NOT FOR ALL

During printing the ">" or "*" sign is cleared by the CFDIU and replaced by "*" at the end of printing.

(3) POST FLIGHT REPORT function

(a) Purpose
The CFDIU generates a POST FLIGHT REPORT, grouping together the ECAM messages and the fault data of the last flight in order to facilitate maintenance data transmission between the crew and ground maintenance personnel.

(b) Principle
The CFDIU memorizes:

the ECAM messages
the fault messages in real time.

It establishes the report header, which includes:

aircraft identification
DATE/GMT of the flight
the flight number
identification of the departure and arrival airports.

When controlled from the MCDU (POST FLIGHT PRINT key) it sends the report established according to the example given in the figure referenced below.

CFDIU - POST FLIGHT REPORT ** ON A/C NOT FOR ALL

(c) POST FLIGHT REPORT control
This report is only available on the ground.
It is controlled by a line key from the main menu or automatically at transition below 80 kts + 30 s (transition DC1/NULL).

(4) Standard header
Each maintenance report sent to the printer begins with a standard header that includes:

- aircraft identification

- date ! read when

- GMT ! the report is

- the flight number ! printed

- identification of the departure !

and arrival airports. !

If the print control concerns a quantity of data greater than the MCDU display capacity, the report is established as follows:

STANDARD HEADER

DATA 1 or several MCDU pages.

The functions entering into this category are:

LAST LEG REPORT
LAST LEG ECAM REPORT

AVIONICS STATUS.

The remaining functions:

PREVIOUS LEGS REPORT
SYSTEM REPORT/TEST

can only be printed page by page (see example).
If the operator controls printing of several pages while remaining in the same function, the CFDIU only sends the header at the first print request.

(5) Control of transmission of the contents of the page displayed by the CFDIU

The CFDIU assigns the 6R line key PRINT * to the command and ensures transmission of data towards the printer.

CFDIU - LAST (or CURRENT) LEG REPORT ** ON A/C NOT FOR ALL

CFDIU - PREVIOUS LEGS REPORT ** ON A/C NOT FOR ALL

(6) Control of transmission of the contents of the page displayed by a system

(a) Type 1 systems

The system assigns the 6R line key PRINT > to the command and the CFDIU transmits the page memorized to the printer:

if it receives the code of the 6R key (PRINT key on the MCDU),
and if coding of bits 23 and 24 of the initial STX word of the page is other than 23 at 0 and 24 at 1.

CFDIU - Type 1 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION ** ON A/C NOT FOR ALL

(b) Type 2 and 3 systems

The CFDIU assigns the 6R line key to the command and ensures transmission of data to the printer for these systems.

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 3 System Report ** ON A/C NOT FOR ALL

During printing the ">" or "*" sign is cleared by the CFDIU and replaced by "*" at the end of printing.

(7) POST FLIGHT REPORT function

(a) Purpose

The CFDIU generates a POST FLIGHT REPORT, grouping together the ECAM messages and the fault data of the last flight in order to facilitate maintenance data transmission between the crew and ground maintenance personnel.

(b) Principle

The CFDIU memorizes:

the ECAM messages
the fault messages in real time.

It establishes the report header, which includes:

aircraft identification
DATE/GMT of the flight
the flight number
identification of the departure and arrival airports.

When controlled from the MCDU (POST FLIGHT PRINT key) it sends the report established according to the example given in the figure referenced below.

CFDIU - POST FLIGHT REPORT ** ON A/C NOT FOR ALL

(c) POST FLIGHT REPORT control

This report is only available on the ground.

It is controlled by a line key from the main menu or automatically at transition below 80 kts + 2 mn 30 s (transition DC1/NULL).

(8) Standard header

Each maintenance report sent to the printer begins with a standard header that includes:

- aircraft identification

- date ! read when

- GMT ! the report is

- the flight number ! printed

- identification of the departure !

and arrival airports. !

If the print control concerns a quantity of data greater than the MCDU display capacity, the report is established as follows:

STANDARD HEADER

DATA 1 or several MCDU pages.

The functions entering into this category are:

LAST LEG REPORT
LAST LEG ECAM REPORT

AVIONICS STATUS.

The remaining functions:

PREVIOUS LEGS REPORT
SYSTEM REPORT/TEST

can only be printed page by page (see example).
If the operator controls printing of several pages while remaining in the same function, the CFDIU only sends the header at the first print request.

(9) Control of transmission of the contents of the page displayed by the CFDIU

The CFDIU assigns the 6R line key PRINT * to the command and ensures transmission of data towards the printer.

CFDIU - LAST (or CURRENT) LEG REPORT ** ON A/C NOT FOR ALL

CFDIU - PREVIOUS LEGS REPORT ** ON A/C NOT FOR ALL

(10) Control of transmission of the contents of the page displayed by a system

(a) Type 1 systems

The system assigns the 6R line key PRINT > to the command and the CFDIU transmits the page memorized to the printer:

if it receives the code of the 6R key (PRINT key on the MCDU),
and if coding of bits 23 and 24 of the initial STX word of the page is other than 23 at 0 and 24 at 1.

CFDIU - Type 1 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 1 System Report - TROUBLE SHOOTING DATA DESCRIPTION ** ON A/C NOT FOR ALL

(b) Type 2 and 3 systems

The CFDIU assigns the 6R line key to the command and ensures transmission of data to the printer for these systems.

CFDIU - Type 2 System Report - Description ** ON A/C NOT FOR ALL

CFDIU - Type 3 System Report ** ON A/C NOT FOR ALL

During printing the ">" or "*" sign is cleared by the CFDIU and replaced by "*" at the end of printing.

(11) POST FLIGHT REPORT function

(a) Purpose

The CFDIU generates a POST FLIGHT REPORT, grouping together the ECAM messages and the fault data of the last flight in order to facilitate maintenance data transmission between the crew and ground maintenance personnel.

(b) Principle

The CFDIU memorizes:

the ECAM messages
the fault messages in real time.

It establishes the report header, which includes:

aircraft identification
DATE/GMT of the flight
the flight number
identification of the departure and arrival airports.

When controlled from the MCDU (POST FLIGHT PRINT key) it sends the report established according to the example given in the figure referenced below.

CFDIU - POST FLIGHT REPORT ** ON A/C NOT FOR ALL

(12) Standard header

Each maintenance report sent to the printer begins with a standard header that includes:

- aircraft identification

- date ! read when

- GMT ! the report is

- the flight number ! printed

- identification of the departure !

and arrival airports. !

If the print control concerns a quantity of data greater than the MCDU display capacity, the report is established as follows:

STANDARD HEADER

DATA 1 or several MCDU pages.

The functions entering into this category are:

LAST LEG REPORT
LAST LEG ECAM REPORT

AVIONICS STATUS.
AVIONICS CONFIGURATION REPORT

The remaining functions:

PREVIOUS LEGS REPORT
SYSTEM REPORT/TEST

can only be printed page by page (see example).
If the operator controls printing of several pages while remaining in the same function, the CFDIU only sends the header at the first print request.

G. Transmission to Ground of CFDIU and System Reports

(1) Modification of the CFDIU main menu

(a) The POST FLIGHT REP PRINT item is replaced by:

POST

* SEND FLT REP PRINT *

This function is available when the ATSU option is installed on the aircraft: it cannot be reprogrammed.

It enables:

printing of the POST FLIGHT REPORT, filtered or not filtered, if the line key adjacent to PRINT* is activated
or, sending of the POST FLIGHT REPORT, filtered or not filtered, to the ATSU if the line key adjacent to *SEND is activated.

Colors:

The *SEND and PRINT* controls are blue.

POST FLIGHT REPORT printing corresponds to the basic definition of the CFDIU.

(b) Addition of the ATSU/PRINT PROGRAM item in the CFDIU main menu

This function gives access to the reprogramming page.

(2) Programming principle

Programming of the various functions is carried out manually or is delivered by the ATSU.

The programming provided by the ATSU only concerns the SEND column of the following functions:

POST FLIGHT REPORT
REAL TIME FAILURES
REAL TIME WARNINGS.

The ATSU codes this programming on label 270 bit 29 (POST FLIGHT REPORT), bit 28 (REAL TIME FAILURES) and bit 27 (REAL TIME WARNING) at a rate of 1 second.
These bits are set to 1 when the function is active.
The remaining functions are only manually programmable.

POST FLIGHT REPORT
The SEND column enables display of the programming received from the ATSU.
YES indicates that this report will be transmitted automatically at the end of the flight.
The end of flight condition is determined by the transition to flight phase 10.
The PRINT column allows the operator to program whether this report is to be automatically printed when it is transmitted to the ATSU.
REAL TIME FAILURE messages
The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the internal failure messages provided by the systems or created by the CFDIU.
The PRINT column allows the operator to program whether the failure message is to be automatically printed when it is transmitted to the ATSU.
REAL TIME WARNING messages
The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the warning messages provided by the FWC.
The PRINT column allows the operator to program whether the warning message is to be automatically printed when it is transmitted to the ATSU.
AVIONICS DATA
This function enables transmission to the ground of system pages displayed on the MCDU to be programmed (only when requested manually), to which access has been gained by the SYSTEM REPORT/TEST item.
Principle:
The 6R line key allocated to PRINT by the system, controls printing of the page and its transmission to the ATSU.
The SEND column enables the operator to program this transmission and indicates to the CFDIU that it must add the PRINT ALSO SEND message (amber) in the scratchpad line of all the system pages.

NOTE: In this specific case, the print control cannot be programmed as the PRINT message is written by the system and consequently, it cannot be modified by the CFDIU. Therefore, the PRINT column contains a YES and cannot be modified.

(3) Operational aspects
The programming sent by the ATSU (YES or NO messages in the SEND column of the first three functions) and the YES in the PRINT column of the AVIONICS DATA function, are displayed in green (not modifiable by the Captain).
The other YES* or NO* messages are displayed in blue.
The title, the column names and the name of the different items are displayed in white.
Each action on the line keys used for manual programming (4L, 1R, 2R, 3R) switches the YES message to NO and vice versa.
If the CFDIU has not received any programming from the ATSU, it displays blanks.
All manual programming is memorized by the CFDIU so that at initialization it can present the last configuration in vigor.
All manual programming can be modified on the ground and in flight.

(a) Manual message transmission
When the operator requests manual transmission (action on the line key adjacent to SEND* for example), the CFDIU deletes the asterisk.
If manual transmission cannot be performed (ATSU BUSY, NOT READY or NOT AVAILABLE) the CFDIU displays the NOT XMITTED TO ATSU message in the scratchpad and displays the asterisk again.

NOTE: In both cases, transmission is not attempted again, except if the operator presses the line key again after the CFDIU has displayed the asterisk again.

When transmission has been performed correctly, the CFDIU displays the XMITTED TO ATSU message in the scratchpad and displays the asterisk again.
These two messages are amber.
The operator cannot change page as long as the CFDIU has not displayed one of the above messages and displayed the asterisk again.
The CFDIU may abandon all its current functions in order to satisfy a manual transmission request.

(b) Automatic message transmission
When the CFDIU carries out an automatic transmission, it does not display a message in the scratchpad.

(4) Modification of the CFDIU main menu

(a) The POST FLIGHT REP PRINT item is replaced by:

POST

* SEND FLT REP PRINT *

This function is available when the ATSU option is installed on the aircraft: it cannot be reprogrammed.

It enables:

Printing of the POST FLIGHT REPORT, filtered or not filtered, if the line key adjacent to PRINT* is activated
Or, sending of the POST FLIGHT REPORT, filtered or not filtered, to the ATSU if the line key adjacent to *SEND is activated.

Colors:

The *SEND and PRINT* controls are blue.

POST FLIGHT REPORT printing corresponds to the basic definition of the CFDIU.

(b) Addition of the REPORTS PROGRAMMING item in the CFDIU main menu.

This function gives access to the reprogramming page.

(5) Programming principle

Programming of the various functions is carried out manually or is delivered by the ACARS MU or ATSU equipment.

The programming provided by the ATSU system only concerns the SEND column of the following functions:

POST FLIGHT REPORT
REAL TIME FAILURES
REAL TIME WARNINGS.

The ACARS MU and ATSU code this programming on label 270 bit 29 (POST FLIGHT REPORT), bit 28 (REAL TIME FAILURES) and bit 27 (REAL TIME WARNING) at a rate of 1 second.
These bits are set to 1 when the function is active.
The remaining functions are only manually programmable.

POST FLIGHT REPORT

The SEND column enables display of the programming received from the ATSU.
YES indicates that this report will be transmitted automatically at the end of the flight.
The end of flight condition is determined by the transition to DC1/NULL.
The PRINT column allows the operator to program whether this report is to be automatically printed when it is transmitted to the ATSU.
REAL TIME FAILURE messages

This report is transmitted by the CFDIU to the ground station through the DATA LINK (if the SEND is programmed to YES) and/or to the printer (if the PRINT is programmed to YES) each time a new maintenance message is processed by the CFDIU.

The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the internal failure messages provided by the systems or created by the CFDIU during the flight.
The PRINT column allows the operator to program whether the failure message is to be automatically printed when it is transmitted to the ATSU.
REAL TIME WARNING messages

This report is transmitted by the CFDIU to the ground station through the DATA LINK (if the SEND is programmed to YES) and/or to the printer (if the PRINT is programmed to YES) each time an ECAM alert/maintenance status is processed by the CFDIU.

The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the warning messages provided by the FWC during the flight.
The PRINT column allows the operator to program whether the warning message is to be automatically printed when it is transmitted to the ATSU.
AVIONICS DATA

This report is transmitted to the printer and to the ground station through the DATA LINK (if the SEND is programmed to YES) each time a printout of an interactive mode page is commanded. If the SEND is programmed to NO, the report is only printed.

This function enables transmission to the ground of system pages displayed on the MCDU to be programmed (only when requested manually), to which access has been gained by the SYSTEM REPORT/TEST item.
Principle:
The 6R line key allocated to PRINT by the system, controls printing of the page and its transmission to the ATSU.
The SEND column enables the operator to program this transmission and indicates to the CFDIU that it must add the PRINT ALSO SEND message (amber) in the scratchpad line of all the system pages.

NOTE: For the "AVIONICS DATA", "AVIONICS CONF REPORT" and "NON CORRELATED PFR", the PRINT control cannot be programmed consequently, it cannot be modified by the CFDIU. Therefore, the PRINT column contains a YES and cannot be modified.

The programming of the SEND for the REAL TIME FAILURE and the REAL TIME WARNING is similar to the one for the SEND of the PFR report. It is done on the AOC pages of the ATIMS MCDU menu (ATA 46) and is duplicated on the CFDS REPORT PROGRAMMING page.
The programming of the PRINT for the REAL TIME FAILURE and the REAL TIME WARNING is similar to the one for the PRINT of the PFR report. It is done on the CFDS REPORT PROGRAMMING page.
The programming of the SEND for the AVIONICS DATA is similar to the one for the print of the PFR report. It is done on the CFDS REPORT PROGRAMMING page. This programming activates the PRINT ALSO SEND function for the AVIONICS DATA.

(6) Operational aspects

The programming sent by the ATSU (YES or NO messages in the SEND column of the first three functions) and the YES in the PRINT column of the other functions, are displayed in green (not modifiable by the Captain).

The other YES* or NO* messages are displayed in blue.

The title, the column names and the name of the different items are displayed in white.

Each action on the line keys used for manual programming (4L, 5L, 1R, 2R, 3R for the first page, 1L for the second page) switches the YES message to NO and vice versa.
If the CFDIU has not received any programming from the ATSU, it displays blanks.

All manual programming is memorized by the CFDIU so that at initialization it can present the last configuration in vigor.

All manual programming can be modified on the ground and in flight.

(a) Manual message transmission

When the operator requests manual transmission (action on the line key adjacent to SEND* for example), the CFDIU deletes the asterisk.
If manual transmission cannot be performed (ATSU BUSY or ACARS MU BUSY, NOT READY or NOT AVAILABLE) the CFDIU displays the NOT XMITTED TO ACARS (or NOT XMITTED to ATSU) message in the scratchpad and displays the asterisk again.

NOTE: In both cases, transmission is not attempted again, except if the operator presses the line key again after the CFDIU has displayed the asterisk again.

(b) Automatic message transmission
When the CFDIU carries out an automatic transmission, it does not display a message in the scratchpad.

(7) Modification of the CFDIU main menu

(a) The POST FLIGHT REP PRINT item is replaced by:

POST

* SEND FLT REP PRINT *

This function is available when the ACARS option is installed on the aircraft: it cannot be reprogrammed.

It enables:

printing of the POST FLIGHT REPORT, filtered or not filtered, if the line key adjacent to PRINT* is activated
or, sending of the POST FLIGHT REPORT, filtered or not filtered, to the ACARS if the line key adjacent to *SEND is activated.

Colors:

The *SEND and PRINT* controls are blue.

POST FLIGHT REPORT printing corresponds to the basic definition of the CFDIU.

(b) Addition of the REPORTS PROGRAMMING item in the CFDIU main menu

This function gives access to the reprogramming page.

(8) Programming principle

Programming of the various functions is carried out manually or is delivered by the ACARS MU or ATSU equipment.

The programming provided by the ACARS system only concerns the SEND column of the following functions:

POST FLIGHT REPORT
REAL TIME FAILURES
REAL TIME WARNINGS.

POST FLIGHT REPORT

The SEND column enables display of the programming received from the ATSU.
YES indicates that this report will be transmitted automatically at the end of the flight.
The end of flight condition is determined by the transition to DC1/NULL.
The PRINT column allows the operator to program whether this report is to be automatically printed when it is transmitted to the ACARS.
REAL TIME FAILURE messages

The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the internal failure messages provided by the systems or created by the CFDIU during the flight.
The PRINT column allows the operator to program whether the failure message is to be automatically printed when it is transmitted to the ATSU.
REAL TIME WARNING messages

The SEND column enables display of the programming received from the ATSU.
YES indicates that the CFDIU must automatically transmit, in real time, all the warning messages provided by the FWC during the flight.
The PRINT column allows the operator to program whether the warning message is to be automatically printed when it is transmitted to the ACARS.
AVIONICS DATA

This function enables transmission to the ground of system pages displayed on the MCDU to be programmed (only when requested manually), to which access has been gained by the SYSTEM REPORT/TEST item.
Principle:
The 6R line key allocated to PRINT by the system, controls printing of the page and its transmission to the ACARS.
The SEND column enables the operator to program this transmission and indicates to the CFDIU that it must add the PRINT ALSO SEND message (amber) in the scratchpad line of all the system pages.

(9) Operational aspects

The programming sent by the ACARS (YES or NO messages in the SEND column of the first three functions) and the YES in the PRINT column of the AVIONICS DATA function, are displayed in green (not modifiable by the Captain).

The other YES* or NO* messages are displayed in blue.

The title, the column names and the name of the different items are displayed in white.

Each action on the line keys used for manual programming (4L, 1R, 2R, 3R) switches the YES message to NO and vice versa.
If the CFDIU has not received any programming from the ATSU, it displays blanks.

All manual programming is memorized by the CFDIU so that at initialization it can present the last configuration in vigor.

All manual programming can be modified on the ground and in flight.

(a) Manual message transmission

When the operator requests manual transmission (action on the line key adjacent to SEND* for example), the CFDIU deletes the asterisk.
If manual transmission cannot be performed (ATSU BUSY or ACARS MU BUSY, NOT READY or NOT AVAILABLE) the CFDIU displays the NOT XMITTED TO ACARS (or NOT XMITTED to ATSU) message in the scratchpad and displays the asterisk again.

NOTE: In both cases, transmission is not attempted again, except if the operator presses the line key again after the CFDIU has displayed the asterisk again.

When transmission has been performed correctly, the CFDIU displays the XMITTED TO ACARS message in the scratchpad and displays the asterisk again.
These two messages are amber.
The operator cannot change page as long as the CFDIU has not displayed one of the above messages and displayed the asterisk again.
The CFDIU may abandon all its current functions in order to satisfy a manual transmission request.

(b) Automatic message transmission
When the CFDIU carries out an automatic transmission, it does not display a message in the scratchpad.

H. Use of the CFDS by the Maintenance Operator
It has been seen that the MCDU enables dialog with the CFDIU, or with the systems connected to the CFDIU.

NOTE: After a power-up of the CFDS:

The CFDS prompt is shown in the MCDU MENU page after approximately 60 seconds.
The full CFDS functionality is available after approximately 3 minutes, to make computation of the A/C configuration possible.

(1) Use of the CFDS at line stops
It has been seen that the purpose of line maintenance is to repair the aircraft in 15 to 20 minutes, in other words to find the faulty LRU and replace it.
In order to do this the line mechanic mainly uses the dialog with the CFDIU, i.e. the functions proper to the CFDIU.
Access to these functions is gained by performing two consecutive actions:

press the MCDU MENU mode key on keyboard
press the CFDS line key.

This can be done on any MCDU, but only on one at a time.
The operator then obtains the CFDS main menu functions on the MCDU.
With this menu displayed, the mechanic shall select the following items:

(a) LAST LEG REPORT or POST FLIGHT REPORT
These reports inform him of all aircraft system faults.
In theory the LAST LEG REPORT enables the mechanic to find the LRU to be replaced. The POST FLIGHT REPORT associates all the ECAM warnings and gives further information concerning the failed LRU if the faulty message is not sufficiently precise (the correlation between the fault messages and the ECAM warnings is carried out by means of GMT).

(b) AVIONICS STATUS
When the faulty LRU has been replaced, the mechanic executes this function, which gives the status of aircraft systems (correct or faulty operation) and enables him to check that the repair is effective.

NOTE: When the replaced equipment is energized, the power-up tests enable the system to declare its status (correct or faulty). Furthermore, the CFDIU monitors refreshment of the output bus.

NOTE: Certain systems have a TEST function in their menu; access to this function is gained by means of the SYSTEM REPORT/TEST function. In most cases this test, activated from the menu, is the same as the power-up test, consequently it does not have to be activated. However, for certain systems, this test is more complete than the power-up test. For these systems, the procedure may ask the operator to activate this test before executing the AVIONICS STATUS.

REMARK:
As the LAST LEG REPORT and the LAST LEG ECAM REPORT functions are accessible in flight, it is possible to send these two reports to the ground by means of the ACARS so as to allow the mechanic to prepare the necessary spare parts.

(2) Use of the CFDS in the hangar (main base)
It has been seen that the purpose of main base maintenance is to repair faults that it has not been possible to repair at line stops (too long or insufficiently qualified personnel or difficult fault) and class 3 faults.
For these repairs the mechanic mainly uses the dialog with the systems, i.e. the functions proper to the systems.
Access to these functions is gained by performing 4 consecutive actions on the MCDU:

press the MCDU MENU menu key on the keyboard
press the CFDS line key
press the SYSTEM REPORT/TEST line key
press the key corresponding to the system to be selected.

This can be done on any MCDU, but only on one at a time. The operator then obtains the system menu functions on the MCDU.
The system selected shall be the system corresponding to the unrepaired fault.
With this menu displayed, the mechanic shall select the following items:

(a) LAST LEG REPORT or TROUBLE SHOOTING DATA
The LAST LEG REPORT informs the mechanic of the faults in this system during the last flight. In theory this report enables the mechanic to find the LRU to be replaced.
In the case of a fault that is difficult to detect, the TROUBLE SHOOTING DATA report gives him further indications concerning the fault.

(b) TEST
When the fault has been repaired, the mechanic executes this function which gives the status of the system (correct or faulty operation) and enables him to check that the repair is effective.

(c) CLASS 3 FAULTS
The reading of these faults is on regular basis, within a maximum time frame specified by the MPD.
The operator may have these faults corrected at his convenience.
However, if the mechanic has the time, he can carry out this repair earlier. In order to do this, he must first of all select the AVIONICS STATUS function on the CFDS main menu.
This function informs him of the aircraft systems that are affected at that moment by at least one class 3 fault.
The mechanic then selects the CLASS 3 FAULTS function of these systems, he obtains the class 3 faults of the selected system which he can then repair.
When the fault has been repaired, the mechanic executes the AVIONICS STATUS function again to check that the repair is effective.

(3) General rules for the use of the CFDS

(a) comment messages
When in the SYSTEM REPORT/TEST function, after each action on a line key or function key, the CFDIU displays the message WAIT FOR SYSTEM RESPONSE on the MCDU scratchpad line (last line), this informs the operator that his request has been taken into account.
As a general rule, if the CFDIU has not detected the response from the system interrogated within 3 seconds, it replaces this message by the NO RESPONSE PRESS RETURN message.
In both cases, the CFDIU adds these comments on the scratchpad line without deleting the page displayed on the MCDU.

(b) CFDIU time out
In the SYSTEM REPORT/TEST function, the CFDIU time out is 15 minutes when there is no action from the operator on the MCDU.

(c) RETURN rules
The return in the menu hierarchy is performed, in all cases, using the 6L RETURN line key.
Each sub-system connected to the CFDIU and to the MCDUs in Menu Mode manages the return in the hierarchy by means of the RETURN control. The CFDIU must also assign the 6L line key to the RETURN control each time it is necessary.
The transition from the main menu of a sub-system to the last CFDIU menu is ensured by the CFDIU which displays its last menu if:

the sub-system displays its main menu
the 6L line key is pressed.

When the CFDIU displays its menu, it sends a LOG OFF to the sub-system which returns to its Normal Mode.
The transition is transparent for the operator.

I. CFDS Backup Modes

(1) First back-up mode
The CFDIU consists of two distinct channels: normal channel and back-up channel.
In normal operation, the normal channel of the CFDIU ensures all maintenance functions and the back-up channel is not energized.
In the event of a CFDIU normal channel fault:

If this fault is serious (power supply board or micro):
it is automatically and immediately switched to the CFDIU back-up channel. In addition, the back-up channel is power supplied on the ground only (ground/flight discrete). When the CFDS item is selected in the MCDU MENU, the CFDS BACKUP MODE page is directly displayed on the MCDU.
In flight: No functions are possible (not supplied).
On the ground: The only function possible is the SYSTEM REPORT/TEST function, for the aircraft main systems only.
CFDIU - BACKUP MODE Through MCDU - On Ground ** ON A/C NOT FOR ALL
If the fault in the CFDIU normal channel is not serious (interface board), automatic switching is not performed, so as not to lose the other CFDS functions for the systems not affected by the fault.
However, the CFDS adds a BACKUP MODE item in its menu, on the ground only, enabling manual switching to the back-up channel on the MCDU.
This switching gives the operator access to the systems affected by the fault in the normal channel. When the switching has been performed by the operator, the CFDIU is placed in the previous configuration (automatic switching).

NOTE: Only the MCDU1 or 3 is connected to the CFDIU back-up channel and can alone be used in BACKUP MODE.

After switching to the back-up channel (automatic or manual), return to the normal channel is not possible using the MCDU. The return can only be performed after a CFDIU power cutoff longer than 1 second.
A CFDIU fault is indicated by a class 2 warning to the ECAM.

(2) Second CFDS back-up mode: the test plugs
In the event of total CFDIU failure (normal and back-up channels), it is still possible to read the maintenance information sent by certain systems by means of two test plugs located in the avionics compartment, on either side of rack 80VU.

(a) Characteristics of the test plugs

Round plugs
Connected to a limited number of systems among the main aircraft systems (located essentially in racks 80VU and 90VU)
46 buses are connected (certain systems have two buses connected)
The side 1 and 3 systems are connected to plug 1 and side 2 systems are connected to plug 2, which ensures system segregation
Directly shunted on the system output buses, without passing through the CFDIU
28VDC power supply: Plug 1 on sub-busbar 103PP (C/B 9TW) and plug 2 on sub-busbar 204PP (C/B 10TW).

CFDIU - Test Plug Power Supply ** ON A/C NOT FOR ALL

(b) Operational use of the test plugs

On the ground only.
The buses are read by means of an ARINC 429 bus reader.
The only maintenance data that can be read on these buses are the data permanently transmitted by the systems, i.e. the data transmitted in Normal Mode, i.e. internal and external faults that occurred during the last flight.

None of the maintenance data normally accessible via the Menu Mode can be read.

(3) Test plugs

In the event of total CFDIU failure, it is still possible to read the maintenance information sent by certain systems by means of two test plugs located in the avionics compartment, on either side of rack 80VU.

(a) Characteristics of the test plugs

Round plugs
Connected to a limited number of systems among the main aircraft systems (located essentially in racks 80VU and 90VU)
46 buses are connected (certain systems have two buses connected)
The side 1 and 3 systems are connected to plug 1 and side 2 systems are connected to plug 2, which ensures system segregation
Directly shunted on the system output buses, without passing through the CFDIU
28VDC power supply: Plug 1 on sub-busbar 103PP (C/B 9TW) and plug 2 on sub-busbar 204PP (C/B 10TW).

CFDIU - Test Plug Power Supply ** ON A/C NOT FOR ALL

(b) Operational use of the test plugs

On the ground only.
The buses are read by means of an ARINC 429 bus reader.
The only maintenance data that can be read on these buses are the data permanently transmitted by the systems, i.e. the data transmitted in Normal Mode, i.e. internal and external faults that occurred during the last flight.

None of the maintenance data normally accessible via the Menu Mode can be read.

** ON A/C NOT FOR ALL

8. CFDS BITE

A. Constitution of the CFDS - General
The CFDS as a whole is made up of the following components:

---------------------------------------------------------------------------

! Components internal to the CFDS ! Components external to the CFDS !

!-------------------------------------------------------------------------!

! - CFDIU (Normal and standby) ! - MCDU1 !

! ! - MCDU2 !

! - CLOCK ! - PRINTER !

! ! -- !

! - MCDU3 (if installed) ! - FAC1 ! !

! ! - FDIU ! !

! ! - FWC1 ! label encoding the general !

! ! - FWC2 ! parameters used by the !

! ! - DMC1 ! CFDIU !

! ! - CIDS1 ! !

! ! - AMU ! !

! ! -- !

NOTE: Monitoring of system BITEs (labels 356) constitutes an operational function of the CFDS which is not covered by the CFDIU BITE.

The CFDIU must therefore monitor the internal and external components described above.

The CFDS as a whole is made up of the following components:

---------------------------------------------------------------------------

! Components internal to the CFDS ! Components external to the CFDS !

!-------------------------------------------------------------------------!

! - CFDIU ! - MCDU1 !

! ! - MCDU2 !

! - CLOCK ! - PRINTER !

! ! -- !

! - MCDU3 (if installed) ! - FAC1 ! !

! ! - FDIU ! !

! ! - FWC1 ! label encoding the general !

! ! - FWC2 ! parameters used by the !

! ! - DMC1 ! CFDIU !

! ! - CIDS1 ! !

! ! - AMU ! !

! ! __! !

!_________________________________!_______________________________________!

NOTE: Monitoring of system BITEs (labels 356) constitutes an operational function of the CFDS which is not covered by the CFDIU BITE.

The CFDIU must therefore monitor the internal and external components described above.

The CFDS as a whole is made up of the following components:

---------------------------------------------------------------------------

! Components internal to the CFDS ! Components external to the CFDS !

!-------------------------------------------------------------------------!

! - CFDIU ! - MCDU1 !

! ! - MCDU2 !

! - CLOCK ! - PRINTER !

! ! -- !

! - MCDU3 (if installed) ! - FAC1 ! !

! ! - FDIU ! !

! ! - FWC1 ! label encoding the general !

! ! - FWC2 ! parameters used by the !

! ! - DMC1 ! CFDIU !

! ! - CIDS1 ! !

! ! - AMU ! !

! ! - DMU ! !

! ! __! !

!_________________________________!_______________________________________!

NOTE: Monitoring of system BITEs (labels 356) constitutes an operational function of the CFDS which is not covered by the CFDIU BITE.

The CFDIU must therefore monitor the internal and external components described above.
The faults of the internal components are memorized in the general LAST LEG REPORT of the CFDS and indicated in the AVIONICS STATUS.
The faults of the internal and external components are memorized in the LAST LEG REPORT or presented in the specific GROUND SCANNING of the CFDIU.

B. Power-Up Tests of the CFDIU
The back-up channel of the CFDIU is tested at each power-up, like the normal channel. Whether there is a fault or not (primary or secondary) in the normal channel, the back-up channel is activated to enable progress of these tests.

(1) Fault of the back-up channel
In the event of an internal fault in the back-up channel, the CFDIU immediately presents the CFDS message in the AVIONICS STATUS of the CFDS
Moreover, on NULL/DC2 transition, the CFDIU memorizes the CFDIU BACKUP message in the LAST LEG REPORT function of the CFDIU menu (accessible at the end of the flight only) and in the general LAST LEG REPORT of the CFDS.
In this case, the time assigned to the fault is the time at which the NULL/DC2 transition occurs.

(2) Fault of the normal channel
In the event of an internal fault in the normal channel, the CFDIU immediately presents the CFDS message in the AVIONICS STATUS of the CFDS
Moreover, on NULL/DC2 transition, the CFDIU memorizes the CFDIU message in the LAST LEG REPORT function of the CFDIU menu (accessible at the end of the flight only) and in the general LAST LEG REPORT of the CFDS.
In this case, the time assigned to the fault is the time at which the NULL/DC2 transition occurs.

(3) Fault of the channel
In the event of an internal fault in the channel, the CFDIU immediately presents the CFDS message in the AVIONICS STATUS of the CFDS
Moreover, on NULL/DC2 transition, the CFDIU memorizes the CFDIU message in the LAST LEG REPORT function of the CFDIU menu (accessible at the end of the flight only) and in the general LAST LEG REPORT of the CFDS.
In this case, the time assigned to the fault is the time at which the NULL/DC2 transition occurs.

C. Processing of the General Functions of the CFDS
This processing consists in adapting the normal mode of the BITEs. The CFDIU monitors the internal and external fault to:

memorize the CFDS BITE internal faults in the LAST LEG REPORT of the CFDS during the flight phases corresponding to DC2 and DC1

indicate the presence of the CFDS BITE internal faults in the AVIONICS STATUS function of the CFDS during the phases corresponding to NULL.

(1) LAST LEG REPORT function of the CFDS
The CFDIU uses this function to memorize the CFDS BITE internal faults during the flight phases corresponding to DC2 and DC1.
Processing of these faults is identical to that of the other faults (correlation with CFDS = source or identifier, transfer in the PREVIOUS LEGS REPORT, etc).
In the general case, these faults are detected through permanent monitoring and in some cases, through the power-up test.

(a) Monitoring of the MCDU3 (if installed)
The CFDIU memorizes "MCDU3" when it detects label 270 with bit 29 set to 1 (bit status). The CFDIU memorizes "NO MCDU3 DATA" in the event of incorrect reception of this label (label absent or SSM at FW = 11, confirmation over 4 seconds).
Rate of label 270: 1 s.

NOTE: The MCDU3 is not monitored under DC1 as it is not power supplied.

(b) Monitoring of the CFDIU

through permanent monitoring:
The CFDIU memorizes "CFDS" when it detects an internal fault in the channel.
through power-up tests

(c) Monitoring of the CLOCK
The CFDIU memorizes "CLOCK" when it detects incorrect transmission of label 125 (GMT) or of label 260 (DATE) (label absent or with a bad parity or with a SSM <> NO, confirmation over 4 seconds).

(2) LAST LEG REPORT function of the CFDS
The CFDIU uses this function to store in memory the CFDS BITE internal faults during the flight phases related to DC 2 and DC 1.
These faults are processed as the other faults (correlation with CFDS = source or identifier, transfer in the PREVIOUS LEGS REPORT, etc.).
In the general condition, these faults are detected through permanent monitoring and in some conditions, through the power-up test.

(a) Monitoring of the CFDIU

Through permanent monitoring:
The CFDIU stores "CFDS" in memory when it detects an internal fault in the channel.
Through power-up tests.

(b) Monitoring of the CLOCK
The CFDIU stores "CLOCK" in memory when it detects an incorrect transmission of label 125 (GMT) or of label 260 (DATE) (label absent or with a bad parity or with a SSM <> NO, confirmation in one minute).

(3) AVIONICS STATUS function of the CFDS
The CFDIU uses this function to indicate in real time the presence (or the absence) of at least one CFDS BITE internal fault.
i.e.:
The CFDIU presents "CFDS" when the normal or back-up channel of the CFDIU is affected by at least one CFDS BITE internal fault detected through the permanent monitoring or the power-up test.
For faults detected through the permanent monitoring, the "CFDS" message disappears if all faults disappear (in real time).
For faults detected through the power-up test, the "CFDS" message disappears if all faults have disappeared when the next power-up occurs.

D. Menu Mode of the CFDIU
The menu mode of the CFDIU comprises the following four functions:

LAST LEG REPORT
LRU IDENTIFICATION
POWER UP TEST RESULT
GROUND SCANNING.

The menu mode is possible with the channel of the CFDIU only.
The menu mode is possible only during the flight phases corresponding to NULL.

The menu mode of the CFDIU comprises the following four functions:

LAST LEG REPORT
LRU IDENTIFICATION
POWER UP TEST RESULT
GROUND SCANNING.

The menu mode is possible only during the flight phases corresponding to NULL.

(1) LAST LEG REPORT function
The purpose of this function is to memorize the internal or external faults in flight, whether these faults are already present on the ground or not.
In the general case, these faults are detected through permanent monitoring and in some cases, through the power-up test.

(a) Handling of faults

1 Memorization

During the flight phases corresponding to DC1, the CFDIU memorizes the internal and external fault except the MCDU 3 fault (which is not monitored under DC2).
During the flight phases corresponding to DC2, the CFDIU memorizes the internal faults only.
The ATA reference, the time at which the failure occurred and the flight phase during which it occurred are associated with each fault message.
If an external/internal fault was present on DC2/DC1 transition and is still present, the time associated with this fault is the time of the DC2/DC1 transition.
The same applies to the internal faults on NULL/DC2 transition.
Processing of faults detected during the power-up tests is described in the paragraphs above.

2 Memorization capacity
Memorization capacity is 5 faults, while new faults delete the oldest ones.

3 Criteria of monitoring

Reminder of acquisition of the components which are internal or external to the CFDS:
* Aircraft configuration parameters :
. FWC 1/2 (label 013)
. DMC 1 (label 305)
. AMU (label 350)
. CIDS (label 146)
and engine serial number parameter : DMC 1 (label 46,47):
These labels are acquired on the ground 45 s after power-up (i.e. further to long power cutoff) and on flight phase 1/2 transition.
* Parameters from :
. FAC 1 (labels 233 ---> 236, 040 --->042)
. FDIU (labels 301 ---> 304):
These labels are acquired at each flight phase transition and at power-up.
* Parameters from :
. FWC 1/2 (label 126)
. PRINTER (labels 303, 350) (IF INSTALLED)
. MCDU 1/2 (labels 303, 270)
. CLOCK (labels 125, 260):
These labels are acquired permanently.
* Parameters from MCDU 3 (labels 303, 270)(If installed):
As the MCDU 3 is supplied on the ground only, these parameters are permanently acquired on the ground (under NULL or DC2).
Criteria of monitoring
* For the FAC 1, FDIU, DMC 1, AMU, CIDS 1, monitoring consists in checking labels only when they are used.
* For the MCDU PRINTER, CLOCK and CFDIU, monitoring is of the permanent type.
* For the FWCs, monitoring is described below.

(b) Description of faults

Monitoring of the FAC 1 (external fault)
The FAC 1 provides the following parameters:
Flight Number : labels 233, 234, 235, 236
City Pair : labels 040, 041, 042.

In the event of incorrect reception of at least one of these labels (No refresh or transmission with bad parity or with SSM=FW confirmed for 4 seconds), the CFDIU memorizes:
"NO FAC 1 DATA"
Monitoring of the FDIU (external fault)
The FDIU provides the following parameter:
A/C Identification : labels 301, 302, 303, 304.

In the event of incorrect reception of at least one of these labels (No refresh or transmission with bad parity or with SSM=FW confirmed for 4 seconds), the CFDIU memorizes:
"NO FDIU DATA"
Monitoring of the FWC 1 and 2 (external faults)
Monitoring described below.
Monitoring of the DMC 1 (external fault)
The DMC 1 provides the following parameters:
Engine serial number : labels 46, 47
A/C configuration : label 305.

In the event of incorrect reception of label 305, (no refresh or transmission with bad parity or with SSM FW=11, confirmed for 12 seconds), the CFDIU memorizes:
"NO DMC 1 DATA"
Monitoring of the AMU (external fault)
The AMU provides the following parameter:
A/C configuration : label 350.

In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11, confirmed for 4 seconds) of this label, the CFDIU memorizes:
"NO AMU DATA"
Monitoring of the CIDS 1 (external fault)
The CIDS 1 provides the following parameter:
A/C configuration : label 146.

In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11, confirmed for 4 seconds) of this label, the CFDIU memorizes:
"NO CIDS 1 DATA"
Monitoring of the MCDU 1 and 2 (external faults)
In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of label 270, the CFDIU memorizes:
"NO MCDU (1 or 2) DATA"
Monitoring of the PRINTER (if installed) (external fault)
In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of label 350, the CFDIU memorizes:
"NO PRINTER DATA"

(details of label 350 are given in the ARINC 740 specification)
Monitoring of CFDIU, MCDU 3 (if installed) and clock (internal faults)
Monitoring and associated message are identical to the case of the Normal Mode described above.

(2) LAST LEG REPORT function

The purpose of this function is to memorize the internal or external faults in flight, whether these faults are already present on the ground or not.
In the general case, these faults are detected through permanent monitoring and in some cases, through the power-up test.

(a) Handling of faults

1 Memorization

During the flight phases corresponding to DC1, the CFDIU memorizes the internal and external fault except the MCDU 3 fault (which is not monitored under DC2).
During the flight phases corresponding to DC2, the CFDIU memorizes the internal faults only.
The ATA reference, the time at which the failure occurred and the flight phase during which it occurred are associated with each fault message.
If an external/internal fault was present on DC2/DC1 transition and is still present, the time associated with this fault is the time of the DC2/DC1 transition.
The same applies to the internal faults on NULL/DC2 transition.
Processing of faults detected during the power-up tests is described in the paragraphs above.

2 Memorization capacity
Memorization capacity is 5 faults, while new faults delete the oldest ones.

3 Criteria of monitoring

Reminder of acquisition of the components which are internal or external to the CFDS:
* Aircraft configuration parameters :
. FWC 1/2 (label 013)
. DMC 1 (label 305)
. AMU (label 350)
. CIDS (label 146)
and engine serial number parameter : DMC 1 (label 46,47):
These labels are acquired on the ground 45 s after power-up (i.e. further to long power cutoff) and on flight phase 1/2 transition.
* Parameters from :
. FAC 1 (labels 233 ---> 236, 040 --->042)
. FDIU (labels 301 ---> 304):
These labels are acquired at each flight phase transition and at power-up.
* Parameters from :
. FWC 1/2 (label 126)
. PRINTER (labels 303, 350) (IF INSTALLED)
. MCDU 1/2 (labels 303, 270)
. CLOCK (labels 125, 260):
These labels are acquired permanently.
* Parameters from MCDU 3 (labels 303, 270)(If installed):
As the MCDU 3 is supplied on the ground only, these parameters are permanently acquired on the ground (under NULL or DC2).
Criteria of monitoring
* For the FAC 1, FDIU, DMC 1, AMU, CIDS 1, monitoring consists in checking labels only when they are used.
* For the MCDU PRINTER, CLOCK and CFDIU, monitoring is of the permanent type.
* For the FWCs, monitoring is described below.

(b) Description of faults

Monitoring of the FAC 1 (external fault)
The FAC 1 provides the following parameters:
Flight Number : labels 233, 234, 235, 236
City Pair : labels 040, 041, 042.

In the event of incorrect reception of at least one of these labels (no refresh or transmission with bad parity or with SSM=FW confirmed for 4 seconds), the CFDIU memorizes:
"NO FAC 1 DATA"
Monitoring of the FDIU (external fault)
The FDIU provides the following parameter:
A/C Identification : labels 301, 302, 303, 304.

In the event of incorrect reception of at least one of these labels (no refresh or transmission with bad parity or with SSM=FW confirmed for 4 seconds), the CFDIU memorizes:
"NO FDIU DATA"
Monitoring of the FWC 1 and 2 (external faults)
Monitoring described below.
Monitoring of the DMC 1 (external fault)
The DMC 1 provides the following parameters:
Engine serial number : labels 46, 47
A/C configuration : label 305.

In the event of incorrect reception of label 305, (no refresh or transmission with bad parity or with SSM FW=11, confirmed for 12 seconds), the CFDIU memorizes:
"NO DMC 1 DATA"
Monitoring of the AMU (external fault)
The AMU provides the following parameter:
A/C configuration : label 350.

In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of this label, the CFDIU memorizes:
"NO AMU DATA"
Monitoring of the CIDS 1 (external fault)
The CIDS 1 provides the following parameter:
A/C confirmation : label 146.

In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of this label, the CFDIU memorizes:
"NO CIDS 1 DATA"
Monitoring of the MCDU 1 and 2 (external faults)
In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of label 270, the CFDIU memorizes:
"NO MCDU (1 or 2) DATA"
Monitoring of the PRINTER (if installed) (external fault)
In the event of incorrect reception (no refresh or transmission with bad parity or with SSM FW=11 confirmed for 4 seconds) of label 350, the CFDIU memorizes:
"NO PRINTER DATA"

(details of label 350 are given in the ARINC 740 specification)
Monitoring of CFDIU, MCDU 3 (if installed) and clock (internal faults)
Monitoring and associated message are identical to the case of the Normal Mode described above.

(3) LRU identification function
The purpose of this function is to display the computer part number.

(4) GROUND SCANNING function
The purpose of this function is to present the internal or external faults on the ground, whether these faults are already present in flight or not.
These faults are detected through monitoring activated on manual selection of the function.

(a) Handling of faults

1 Activation

After manual selection of the function, the CFDIU monitors the internal and external faults.
The ATA reference and the time at which the fault is detected are associated with each fault message.

2 Presentation capacity
Presentation capacity is 5 failures while new faults delete the oldest ones.

3 The presentation of this function is identical to that of the LAST LEG REPORT.

4 During function progress the CFDIU presents the message: IN PROGRESS (50 SEC) and a RETURN/STOP key is presented to enable function interruption and return to CFDIU BITE menu.

5 Criteria of monitoring

Monitoring is activated on function selection for the following systems:
FAC 1, FDIU, DMC 1, AMU, CIDS 1, MCDU, PRINTER, CLOCK, CFDIU
For the FWCs, monitoring is described below.

(b) Description of faults
Monitoring and associated message are identical to the case of the LAST LEG REPORT.

NOTE: This manually activated monitoring does not entail acquisition of monitored parameters by the CFDIU.

(5) POWER-UP TEST RESULT function
The purpose of this function is to present the CFDIU internal components detected faulty during the last Power-Up Test.
The ATA reference 31-32-34 is associated with each fault message.

(a) In the event of fault, the following messages are displayed:

CFDIU I/0 ARINC 1 (or 2 or 3) for fault of multiplexor 1, 2 or 3
CFDIU I/0 DISCRETE 1 (or 2) for fault of discrete inputs/outputs 1 or 2
CFDIU BITE MEMORY for fault in NVM
CFDIU for any other fault of the normal channel
CFDIU BACK UP for any fault of the back-up channel.

(6) LRU identification function
The purpose of this function is to display the computer part number.

(7) GROUND SCANNING function
The purpose of this function is to present the internal or external faults on the ground, whether these faults are already present in flight or not.
These faults are detected through monitoring activated on manual selection of the function.

(a) Handling of faults

1 Activation

After manual selection of the function, the CFDIU monitors the internal and external faults.
The ATA reference and the time at which the fault is detected are associated with each fault message.

2 Presentation capacity
Presentation capacity is 5 failures while new faults delete the oldest ones.

3 The presentation of this function is identical to that of the LAST LEG REPORT.

4 During function progress the CFDIU presents the message: IN PROGRESS (50 SEC) and a RETURN/STOP key is presented to enable function interruption and return to CFDIU BITE menu.

5 Criteria of monitoring

Monitoring is activated on function selection for the following systems:
FAC 1, FDIU, DMC 1, AMU, CIDS 1, MCDU, PRINTER, CLOCK, CFDIU
For the FWCs, monitoring is described below.

(b) Description of faults
Monitoring and associated message are identical to the case of the LAST LEG REPORT.

NOTE: This manually activated monitoring does not entail acquisition of monitored parameters by the CFDIU.

(8) POWER-UP TEST RESULT function
The purpose of this function is to present the CFDIU internal components detected faulty during the last Power-Up Test.
The ATA reference 31-32-34 is associated with each fault message.

(a) In the event of fault, the following messages are displayed:

CFDIU I/0 ARINC 1 (or 2 or 3) for fault of multiplexor 1, 2 or 3
CFDIU I/0 DISCRETE 1 (or 2) for fault of discrete inputs/outputs 1 or 2
CFDIU BITE MEMORY for fault in NVM
CFDIU for any other fault of the channel

(9) LRU identification function
The purpose of this function is to display the computer part number.

(10) GROUND SCANNING function
The purpose of this function is to present the internal or external faults on the ground, whether these faults are already present in flight or not.
These faults are detected through monitoring activated on manual selection of the function.

(a) Handling of faults

1 Activation

After manual selection of the function, the CFDIU monitors the internal and external faults.
The ATA reference and the time at which the fault is detected are associated with each fault message.

2 Presentation capacity
Presentation capacity is 5 failures while new faults delete the oldest ones.

3 The presentation of this function is identical to that of the LAST LEG REPORT.

4 During function progress the CFDIU presents the message: IN PROGRESS (50 SEC) and a RETURN/STOP key is presented to enable function interruption and return to CFDIU BITE menu.

5 Criteria of monitoring

Monitoring is activated on function selection for the following systems:
FAC 1, FDIU, DMC 1, AMU, CIDS 1, MCDU, PRINTER, CLOCK, CFDIU
For the FWCs, monitoring is described below.

(b) Description of faults
Monitoring and associated message are identical to the case of the LAST LEG REPORT.

NOTE: This manually activated monitoring does not entail acquisition of monitored parameters by the CFDIU.

(11) POWER-UP TEST RESULT function
The purpose of this function is to present the CFDIU internal components detected faulty during the last Power-Up Test.
The ATA reference 31-32-34 is associated with each fault message.

(a) In the event of fault, the following messages are displayed:

CFDIU MUX1 (or 2 or 3) for fault of multiplexor 1, 2 or 3
CFDIU I/0 DISCRETE 1 (or 2) for fault of discrete inputs/outputs 1 or 2
CFDIU BITE MEMORY for fault in NVM
CFDIU WATCHDOG for watchdog failure
CFDIU ALIMENTATION for power supply failure.

E. Monitoring of the FWC 1 and 2
The FWC 1 is connected to the "switch" only (FWC 1 to FWC 2) while the FWC 2 is connected to the switch and to the multiplexor 2.

(1) Monitoring of the FWC 1

(a) Processing of label 356
In the event of incorrect reception of label 356 (not refreshed, confirmed for 4 seconds), the CFDIU carries out the following processing :

No switching to the FWC 2
real-time display and as long as fault is present, of the NO FWC 1 DATA message in the AVIONICS STATUS of the CFDS (function accessible under NULL).
Real-time memorization of the NO FWC 1 DATA message in the LAST LEG REPORT of the CFDS, if the fault is present in flight (DC2 or DC1).

(b) Processing of label 126
In the event of incorrect reception of label 126 (no refresh or bad parity or SSM at FW, confirmation over 4s), the CFDIU carries out the following processing :

Switching to the FWC 2 (consequently, the FWC 1 is no longer monitored).
Memorization of the NO FWC 1 DATA message in the LAST LEG REPORT of the CFDIU:
* in real-time (with the occurrence time of the fault) if the fault occurs during DC1
* with the DC2/DC1 transition time, if the failure occurs under NULL or DC2 (switching to FWC 2).
Presentation of the NO FWC 1 DATA message in the GROUND SCANNING of the CFDIU if the fault is present on activation of this function (switching to FWC 2).

NOTE: There is no message (NO FWC 1 DATA or CFDS) in the AVIONICS STATUS or in the LAST LEG REPORT of the CFDS.

REMARK : In the event of switching to the FWC 2 (in this case,

the FWC 1 and therefore labels 356 and 013 are no longer

monitored), the CFDIU performs by default processing

corresponding to label 126 processing and does not display

the messages corresponding to processing of labels 356 and

013.

(c) Processing of label 013
In the event of incorrect reception of label 013 (label absent or SSM at FW, confirmed for 4 seconds), the CFDIU carries out the following processing:

no switching to the FWC 2
presentation of the NO FWC 1 DATA message in the GROUND SCANNING of the CFDIU if the fault is present on activation of this function.

NOTE: There is no message (NO FWC 1 DATA or CFDS) in the LAST LEG REPORT or in the AVIONICS STATUS of the CFDS or in the LAST LEG REPORT of the CFDIU.

(2) Monitoring of the FWC 2

(a) Processing of label 356
Identical to processing of FWC 1.

(b) Processing of label 126
1st case :
The CFDIU works with the FWC 1 : label 126 of the FWC 2 is not monitored.
2nd case :
The CFDIU switched to the FWC 2 :
In the event of incorrect reception of label 126 :

the CFDIU memorizes in real time the NO FWC 2 DATA message in the LAST LEG REPORT of the CFDIU if the fault occurs during DC1
the CFDIU presents the NO FWC 2 DATA message in the GROUND SCANNING of the CFDIU if the fault is present on activation of this function.

NOTE: There is no message (NO FWC 2 DATA or CFDS) in the AVIONICS STATUS or in the LAST LEG REPORT of the CFDS.

(c) Processing of label 013
1st case :
The CFDIU works with the FWC 1 : label 013 of the FWC 2 is not monitored.
2nd case :
The CFDIU switched to the FWC 2 :
In the event of incorrect reception of label 013, the CFDIU presents the NO FWC 2 DATA message in the GROUND SCANNING of the CFDIU if the fault is present on activation of this function.

NOTE: There is no message (NO FWC 2 DATA or CFDS) in the AVIONICS STATUS or in the LAST LEG REPORT of the CFDS or in the LAST LEG REPORT of the CFDIU.

F. SYSTEM REPORT TEST - Indicating/Recording Systems - CFDIU

Indicating/Recording Systems - SYSTEM REPORT/TEST ** ON A/C NOT FOR ALL

(1) Power-up test

Integrity test of the CFDIU.

(2) Tested LRUs and related messages during CFDIU test

CFDIU - SYSTEM REPORT/TEST

Integrity test of the CFDIU.

(3) Ground scanning of the CFDIU

CFDIU - GROUND SCANNING

[Rev.10 from 2021] 2026.04.01 05:00:10 UTC