Troubleshooting on A320 - A340

(1)

May 2005

Trouble shooting philosophy with

A320 CFDS / A340 CMS

Customer Support Engineering

Presented by

AUFFRET Hervé

(2)

May 2005

Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 Page 2

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(3)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(4)

May 2005

y document.

MAINTENANCE LEVELS

1st Level

2nd Level

No Log-Book complaint

Log-Book complaint (Class 1)

LRU level only

Maintenance status

LRU Level

No Maintenance Action required

PFR + System Report / Test +

Ref to MMEL

PFR (Class 2) +

System Report / Test

LINE MAINTENANCE

(5)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

MAINTENANCE LEVELS

3rd Level

4th Level

Class 3 faults

LRU Level

LRU removal

SRU Level

General Class 3 Report +

System Report / Test

Trouble Shooting Data +

BITE Shop Memory

SCHEDULED CHECKS

(6)

May 2005

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(7)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

LINE MAINTENANCE CONCEPT: Decision Tree applies

AIRBUS

(TSD, ACMS Labels)

LOG BOOK

MEL

NO

GO

Fault

on

PFR

SIL 00-028 / -038/ 041/ -078

•PART A (Fault Msg)

•PART B (Cockpit Effect)

TSM

ECAM or CMS Index

TSM

EFIS, LOCAL or OBSV Index

FOLLOW TSM PROCEDURE

Crew or

Maintenance

Observation

Failure

Isolated

Spare

Available

A/L Engineering

_{(ACMS Labels)}

Maint Action/

LRU Removal

A/C Return to Service

Carried Forward

item

No

Yes

No

Yes

No

Yes

No

Yes

(8)

May 2005

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(9)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

A/C INFORMATION SHARING

ECAM or

EFIS

indications

FAULT

LOCAL

indications

or

FWCs

CMC

Operational failure messages

(function lost) :

Maintenance failure messages

(LRU lost) :

LOG BOOK

AIRCRAFT SYSTEMS

"Warnings/Malfunctions"

"CMS Fault Messages"

OPERATIONAL INFORMATION FOR

FLIGHT CREW : A/C DISPATCH

MAINTENANCE INFORMATION FOR

_{MECHANIC : A/C TROUBLESHOOTING}

HYD B RSVR LO PRESS -BLUE ELEC PUMP....OFF

Warnings/Malfunctions

POST FLIGHT

REPORT

Warnings/ Malfunctions CMS Fault

MCDU

TEST>

TSM

Fault Isolation Procedures

(10)

May 2005

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(11)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

MESSAGE CLASSIFICATION

1

2

3 NOT PRESENTED

PRESENTED

MESSAGE CLASS

INDICATION TO THE

FLIGHT CREW

DISPATCH (MMEL)

CONSEQUENCES

HANDLING

INDICATION TO THE

MAINTENANCE TEAM

Cockpit Effect

Any evidence of fault to the flight

crew: ECAM Warning, Flag on

SD, PFD or ND, Local warnings,

System misbehaviour ...

Maintenance Status

Status light flashing at the end

of the flight; Maintenance

Status messages on SD STS

page, presented only on

ground.

No indication to the flight

crew

POST FLIGHT REPORT

AVIONIC STATUS

MMEL ENTRY

MMEL PREAMBLE

MMEL NOT

APPLICABLE

REF MMEL

600 Hours

UNLIMITED TIME

Can be automatically issued at 80 kts + 180 s

To be manually issued

GO, GO IF or NO GO

GO

for time delay, restrictions etc...

(See also TSM Introduction)

However, correction is

recommended to improve

the dispatch reliability

(12)

May 2005

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. Message Classification

5. TSM Use

(13)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

TSM USE

I-OBSV

I-LOCAL

I-EFIS

I-ECAM

General Indexes

I-CFDS

XX-CFDS

XX-OBSV

XX-LOCAL

XX-EFIS

XX-ECAM

PB 101

Fault

Symptoms

ATA Indexes

(XX= ATA chapter)

TSM LEVEL

ATA CHAPTER LEVEL

BLOCK

DIAGRAM

FAULT

ISOLATION

PB 201

PB 301

ATA SECTION LEVEL

(14)

May 2005

y document.

TSM USE : Indexes

I-CFDS

EFF : ALL Page 1 Jan 01/94 XXX

TROUBLE SHOOTING MANUAL

INDEX OF CFDS FAULT MESSAGES

CFDS MESSAGES ATA SOURCE CLASS CH-PB101 ACARS MU (1RB) 232434 ACARSMU 1 23-ECAM ACCELEROMETER 313316 FDIU 2 31-CFDS

ACCLRM 1 12CE1 279216 EFCS 1 2 27-ECAM ACCLRM 1 12CE1 279216 EFCS 2 2 27-ECAM ACCLRM 2 12CE2 279216 EFCS 1 2 27-ECAM ACCLRM 2 12CE2 279216 EFCS 2 2 27-ECAM ACCLRM 3 12CE3 279216 EFCS 1 2 27-ECAM ACCLRM 3 12CE3 279216 EFCS 2 2 27-ECAM

A320

ADIRU1 341234 ADR 1 1 34-ECAM

ADIRU1 (1FP1)/GPWC (1WZ) 341234 GPWC 1 34-ECAM

ADIRU1 (1FP1)/ OVER TEMP 341234 ADR 1 2 34-CFDS

ADIRU1 OR ADIRS CDU 341234 IR 1 1 34-ECAM

ADIRU1 OR AOA SENSOR 3FP1 341234 ADR 1 1 27-ECAM

I-OBSV

I-LOCAL

I-ECAM

EFF : ALL Page 1 Jan 01/94

XXX

A.ICE L INR WING HI PR 30-00 30-ECAM

AIR ENG 1 BLEED NOT CLOSED 36-00 36-ECAM

AIR ENG 1 HPV NOT OPEN 36-00 36-ECAM

AIR ENG 1 BLEED FAULT 36-00 36-ECAM

AIR ENG 1 BLEED LEAK 36-00 36-ECAM

ENG 2 BLEED NOT CLOSED 36-00 36-ECAM

A320

I-EFIS

INDEX OF WARNING/MALFUNCTIONS

ECAM PFR ATA TSM ATA CH/SE CH-PB101 EWD WARNINGS

A.ICE CAPT AOA HEAT 30-00 30-ECAM

A.ICE CAPT PITOT HEAT 30-00 30-ECAM

A.ICE CAPT TAT HEAT 30-00 30-ECAM

A.ICE F/O AOA HEAT 30-00 30-ECAM

A.ICE F/O PITOT HEAT 30-00 30-ECAM

A.ICE F/O TAT HEAT 30-00 30-ECAM

(15)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

TSM USE : Fault symptoms

22-OBSV

Page 101 Jan 01/94

UBLE SHOOTING MANUAL

O FLIGHT FAULT SYMPTOMS

A320

CFDS FAULT MESSAGES FAULT ISOLATION SOURCE MESSAGE ATA C PROCEDURE CFDS MESSAGES

22-CFDS

Page 101 Jan 01/94

AFS AFS: FAC2/P-B SW 12C 226634 1 226600 P 243 T 810 837

22-LOCAL

34-EFIS

AUTO FLIGHT FAULT SYMPTOMS

A320

CFDS FAULT MESSAGES FAULT WARNINGS/MALFUNCTIONS ISOLATION

SOURCE MESSAGE ATA C PROCEDURE EWD WARNING(S)

22-ECAM

AUTO FLT AP OFF AFS FMGC 1 (1CA1) 228334 1 22100 P205

(16)

May 2005

y document.

TSM USE : Fault isolation

21-26-00

5. Close-up Close Access

A320

TASK 21-26-00-810-808

Monitoring Discrete Output to Extract Fan 1. Possible Causes

- FAN EXTRACT, AVCNS VENT (7HQ)

- Wiring between the pin C of the extract fan and the AEVC (2HQ) 2. Job Set-up Information

A. Referenced Information

REFERENCE DESIGNATION

AMM 21-26-00-710-803 Operational test of the Avionics-Equipment Ventilation System

AMM 21-26-51-000-804 Removal of the Extract Fan (7HQ) AMM 21-26-51-400-804 Installation of the Extract Fan (7HQ) ASM 21-26/01

3. Fault Confirmation A. Job set-up Get access Open access door 810 B. Test

(1) Do the test of the avionics equipment ventilation (Ref. AMM TASK 21-26-00-710-803). 4. Fault Isolation

A. If the test gives the maintenance message EXTRACT FAN (7HQ)/AEVC (2HQ) : (1) Do a check to make sure that there is ground at pin C of the extract fan

TASK 21-26-00-810-805

FAULT CONFIRMATION

(17)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

TSM USE : Task supporting data

TROUBLE SHOOTING MANUAL FLAPS TASK SUPPORTING DATA

A320

functions

SHOOTING DATA

Cs have TROUBLE SHOOTING DATA for a given fault which shows : antennae messages

mplementary information, if applicable; The complementary information is

X INPUTS.

age shows the synchro angles in decimal and hexadecimal values of the LH

27-50-00

LL Page 308 Jan 01/94 XXX

27-50-00

Flap Power Distribution - Block Diagram Figure 306 FLIGHT WARNING COMPUTER 2 (REF 3-53-00) 26VAC SYSTEM 2 FLIGHT WARNING COMPUTER 1 (REF 3-53-00) 26VAC SYSTEM 2

A320

PCU VALVE BLOCK

EXT

(18)

May 2005

y document.

AGENDA

1. Maintenance Levels

2. Line Maintenance Concept

3. A/C Information Sharing

4. TSM Use

(19)

y document.

TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS

SIL 00-028 (A320), 00-038 (A340), 00-041 (A330)

• SILs issued to cover BITE deviations

• PART E covers items (Cockpit Effect and Fault messages) that

AIRBUS recommend to filter from the PFR.

• Purpose:

• Reduce number of items in the PFR

• Improve PFR pertinance

Part A

Part B

Part C

Part D

PFR Failure Messages

PFR Cockpit Effects

Class 3 Fault Messages

CFDS/CMS Anomalies (Interactive Mode)

(20)

May 2005

y document.

This document and all information contained herein is the sole property of AIRBUS S.A.S.. No intellectual property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied. The statements made herein do not constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the supporting grounds for these statements are not shown, AIRBUS S.A.S. will be pleased to explain the basis thereof.

AIRBUS, its logo, A300, A310, A318, A319, A320, A321, A330, A340, A350, A380, A400M are registered trademarks.

(21)

A340-500/600

TECHNICAL TRAINING MANUAL

ONBOARD MAINTENANCE SYSTEMS

A340-500/600 T2 MAINTENANCE COURSE (ELECTRICS/

AVIONICS)

(22)

(23)

This document must be used for training purposes only

Under no circumstances should this document be used as a reference

It will not be updated.

All rights reserved

No part of this manual may be reproduced in any form,

by photostat, microfilm, retrieval system, or any other means,

(24)

(25)

A340-500/600 TECHNICAL TRAINING MANUAL

ONBOARD MAINTENANCE SYSTEMS

CENTRAL MAINTENANCE SYSTEM PRESENTATION . . . 2 CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION . 14 CMS MENUS PRESENTATION . . . 24 MENU NORMAL MODE D/O. . . 36 MENU INTERACTIVE MODE D/O . . . 48 MENU SERVICING D/O . . . 62 MENU AVIONICS CONFIGURATION D/O . . . 74 MESSAGE D/O . . . 86 MESSAGE PROCESSING D/O . . . 96 BACK UP FUNCTIONS D/O . . . 106 PRINTER PRESENTATION . . . 108 PRINTER D/O . . . 110 UP AND DOWN LOADING SYSTEM PRESENTATION. . . 112 UP AND DOWN LOADING SYSTEM D/O . . . 118 ON BOARD MAINTENANCE SYSTEM TEST . . . 126 ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE . . . 134 ON BOARD MAINTENANCE SYSTEMS BASE MAINTENANCE . . . 150

(26)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

January 03/05 Page 2 A340-500/600 T2 MAINTENANCE COURSE (ELECTRICS/AVIONICS)

FM45P3000000001 01 45 - ONBOARD MAINTENANCE SYSTEMS

FWUT200

January 03/05

CENTRAL MAINTENANCE SYSTEM PRESENTATION

CMS PHILOSOPHY

The Central Maintenance System (CMS) includes the Built-In Test Equipment (BITE) of all electronic systems and two fully redundant Central Maintenance Computers (CMCs).

The CMS is used for short term trouble shooting, Line Replaceable Unit (LRU) removal and system failure analysis or test.

The CMCs centralize and memorize warnings generated by the Flight Warning Computers (FWCs) and failure messages produced by the aircraft system BITEs.

The CMS enables maintenance personnel to perform system operational tests, functional checks and read out of BITE memory through the MCDU.

Reports can be printed on-board, saved on a floppy disk via the Multipurpose Disk Drive Unit (MDDU) or transmitted to ground through the Air Traffic Service Unit (ATSU).

(27)

A340-500/600 TECHNICAL TRAINING MANUAL

(28)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

FWUT200

BITE PHILOSOPHY

A system is composed of LRUs which can be: - computers,

- sensors, - actuators, - and probes.

A function of the system computer is to detect and memorize any failure occurring within the systems, it is called the Built-In Test Equipment (BITE). The BITE memory content of each system is sent to the CMCs.

(29)

A340-500/600 TECHNICAL TRAINING MANUAL

(30)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

FWUT200

TESTS

A BITE can perform 4 types of test:

- POWER UP TEST, which are safety tests, they check the system integrity. They are carried out on the ground after a power cut,

- CYCLIC TESTS, which are executed in flight and do not disturb system operation. It is a permanent monitoring of the system,

- SYSTEM TESTS, which enable the maintenance staff to check that the systems are safe for flight and enable trouble shooting. They are carried out on the ground,

- SPECIFIC TESTS, which are available for some systems. They generate stimuli to various command devices such as actuators or valves. As they have major effects on the aircraft, they are only executed on the ground.

(31)

A340-500/600 TECHNICAL TRAINING MANUAL

(32)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

FWUT200

CENTRAL MAINTENANCE COMPUTER

Two CMCs are provided: - number one is active,

- and number two is a hot standby.

A pushbutton is provided for manual transfer from one to the other. The CMCs continuously scan the buses from the aircraft systems.

During flight, if a failure message from a BITE is present on a bus, the CMCs copy and store it.

The CMCs also store warning messages generated by the FWCs during flight operation.

The CMS operator's interface is the MCDU.

(33)

A340-500/600 TECHNICAL TRAINING MANUAL

(34)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

FWUT200

OPERATION MODES

The CMS operates in two modes, a normal mode and an interactive mode. In normal mode, the CMS records fault messages from system BITEs and warnings from the FWCs.

In the interactive mode, which is available on the ground only, the CMS allows the operator to retrieve trouble shooting data and to initiate system tests.

(35)

A340-500/600 TECHNICAL TRAINING MANUAL

(36)

CENTRAL MAINTENANCE SYSTEM PRESENTATION

FWUT200

SYSTEM TYPES

The systems are of three different types depending on their complexity. Most of the systems are type 1 systems.

Type 1 systems can memorize failures that occurred during the last 64 flights. They are connected to both CMCs by an ARINC 429 output bus and to CMC 1 by an ARINC 429 input bus.

This enables on ground trouble shooting and interactive testing of the systems and their components.

The type 2 systems only memorize failures from the last flight. The output connection is an ARINC 429 bus.

A discrete input allows initiation of the system test. The TYPE 3 systems do not generate failure messages. A discrete output indicates the system status.

(37)

A340-500/600 TECHNICAL TRAINING MANUAL

(38)

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FWUT200

January 03/05

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FAILURE CLASSES

Failures are divided into three classes depending on the effect they have on the flight.

CLASS 1 FAILURE

Class 1 failures are the failures which have an operational consequence to the current flight.

Some of them are displayed as a warning in real time on the ECAM and available on the MCDU.

CLASS 2 FAILURE

Class 2 failures are the failures which have no operational consequence on the current flight.

Some affected systems are identified on the ECAM status page. As for class 1 failures, the maintenance team can identify them on the post flight report.

CLASS 3 FAILURES

Class 3 failures have neither operational nor safety consequences on the aircraft. They are not indicated to the flight crew during flight. They are only available on ground through the MCDU class 3 report.

(39)

A340-500/600 TECHNICAL TRAINING MANUAL

(40)

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FWUT200

INTERNAL / EXTERNAL FAILURES

Failure messages transmitted to the CMCs can be internal or external.

INTERNAL FAILURES

If a failure appears within a system, the BITE will send an internal failure message to the CMCs.

EXTERNAL FAILURES

The BITE of each system interfacing with the affected system will send an external failure message to the CMCs.

(41)

A340-500/600 TECHNICAL TRAINING MANUAL

(42)

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FWUT200

FAILURE MESSAGES STRUCTURE

The maintenance messages are all made up of one or several parts. Each part includes the following data :

- the name of the suspected component, - its FIN if it is a LRU,

(43)

A340-500/600 TECHNICAL TRAINING MANUAL

(44)

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FWUT200

TYPES OF MESSAGE

Any part is given in one of these five forms depending on the failure reported: An "LRU (FIN)" message appears when:

- either the computer declares itself suspect,

- or a computer or a system receiving its signals declares the affected computer as suspect.

An "LRU (FIN) COMPLEMENTARY INFO" message appears when the suspected computer is generating several signals. The complementary info helps to identify the suspected signal.

A "WRG : SIGNAL NAME" message appears when a wiring failure is identified, with the name of the transmitted signal.

An "LRU (FIN) SPLY" message appears when an LRU supply loss is identified without ambiguity.

Specific messages are used for some faulty situations that would require a too complex BITE to identify the affected LRU.

In these cases, only the operator can identify the faulty LRU. The procedure required is in the Maintenance Manual.

(45)

A340-500/600 TECHNICAL TRAINING MANUAL

(46)

CENTRAL MAINTENANCE SYSTEM MESSAGES PRESENTATION

FWUT200

AMBIGUOUS / MULTIPLE FAULTS

In the case of ambiguous faults, up to three possible failures may be indicated in the most probable order.

A "/" sign separates the message parts.

In some cases of multiple faults, a BITE may generate a single maintenance message which concerns several defective components.

(47)

A340-500/600 TECHNICAL TRAINING MANUAL

(48)

CMS MENUS PRESENTATION

FWUT200

January 03/05

CMS MENUS PRESENTATION

CMS MCDU MENUS

The functions are displayed on a ground and a flight menu. The flight menu presents only a part of the ground menu.

The CMS menu switches to flight mode, when at least 3 engines are running for 180 seconds with the flight number inserted (or the aircraft speed is above 80 knots). The ground menu comes back during roll-out, when the aircraft speed is below 80 knots for more than 30 seconds.

(49)

A340-500/600 TECHNICAL TRAINING MANUAL

(50)

CMS MENUS PRESENTATION

FWUT200

FLIGHT LEGS

A flight LEG starts at startup of the third engine plus three minutes, if the flight plan is available in the Flight Management System (FMS), or speed higher than 80 knots if the flight plan is not available.

At the beginning of a new LEG, the content of the POST FLIGHT REPORT is transferred to the previous flight report memory.

(51)

A340-500/600 TECHNICAL TRAINING MANUAL

(52)

CMS MENUS PRESENTATION

FWUT200

NORMAL MODE

In normal mode, the CMCs memorize the fault messages from type 1 and type 2 systems and the fault status from type 3 systems.

The three types of system have a different behavior depending on flight phases in the normal mode:

- type 1 systems receive CMC data for flight phase synchronization. They memorize failure messages at the start of each flight LEG until 80 knots +30s after touch down.

- type 2 systems only memorize failure messages when the aircraft is airborne (i.e. as soon as the landing gear is not compressed). - type 3 systems transmit a permanent signal if they are faulty.

In the normal mode, several functions provide aircraft status reports. The CURRENT FLIGHT REPORT function is available on the flight menu. It provides the list of ECAM warnings/cautions and faults related to class 1 and class 2 failures recorded during the current flight.

The POST FLIGHT REPORT function is available on the first page of the ground menu.

It provides the list of ECAM warnings/cautions and faults related to class 1 and class 2 failures recorded during the last flight.

The PREVIOUS FLIGHT REPORT function is available on the first page of the ground menu.

It gives the list of the POST FLIGHT REPORTS over the last 63 previous flights.

(53)

A340-500/600 TECHNICAL TRAINING MANUAL

(54)

FWUT200

(55)

A340-500/600 TECHNICAL TRAINING MANUAL

(56)

CMS MENUS PRESENTATION

FWUT200

INTERACTIVE MODE

The SYSTEM REPORT/TEST function of the ground menu enables access to the interactive mode.

In the interactive mode, which is available on the ground only, the CMS allows the operator to retrieve troubleshooting data and to initiate system tests.

(57)

A340-500/600 TECHNICAL TRAINING MANUAL

(58)

CMS MENUS PRESENTATION

FWUT200

COMPLEMENTARY FUNCTIONS

Several complementary functions are available via the MCDU menus. The AVIONICS STATUS function is accessible on both flight and ground menus.

It provides a real time list of the systems affected by a fault.

The CLASS 3 REPORT function is available on the second page of the ground menu.

It provides the list of class 3 faults.

The REPORTS PROGRAMMING function allows an automatic print or download of the POST FLIGHT REPORT at engine shut down.

The report filter can also be activated from here.

The REPORTS FILTERS function allows spurious messages in the flight reports to be filtered.

This filter can be inserted either manually via the MCDU or by uploading in the CMCs.

The AVIONICS CONFIGURATION REPORTS function manages the inventory of the aircraft computer part numbers and software diskettes. The SERVICING REPORT function provides reports with different parameters which have to be periodically checked and which may induce servicing actions.

The UTC/DATE INIT function is accessible on both flight and ground menus. It appears after a long power interrupt of the CMCs.

(59)

A340-500/600 TECHNICAL TRAINING MANUAL

(60)

MENU NORMAL MODE D/O

FM45D1F45C60301 01 45 - ONBOARD MAINTENANCE SYSTEMS

FWUT200

January 03/05

MENU NORMAL MODE D/O

GENERAL

This is the Multipurpose Control & Display Unit (MCDU) menu page which presents the systems connected to the MCDU.

From the MAINTENANCE MENU displayed on 2 pages, all the Normal Mode Central Maintenance System (CMS) reports can be shown.

These reports will be explained in the following topics, supposing the aircraft on ground and engines shut down.

(61)

A340-500/600 TECHNICAL TRAINING MANUAL

(62)

MENU NORMAL MODE D/O

FWUT200

POST FLIGHT REPORT

The POST FLIGHT REPORT displays the Electronic Centralized Aircraft Monitoring (ECAM) messages such as WARNINGS/CAUTIONS and MAINTENANCE STATUS messages, and also CLASS 1 and 2 FAULT messages which occurred during the last flight and have been memorized in the Central Maintenance Computer (CMC).

It can display a maximum of 64 warnings and 64 faults.

The first item of the POST FLIGHT REPORT, are the ECAM messages. The first page contains only one of these messages.

If there are several messages, they will be displayed 2 at a time only, on the following pages. In this example, there are 2 ECAM message pages. The ECAM messages are displayed in the order of acquisition by the CMC, minute by minute. The last message memorized is displayed first.

If there is no warning, the NO WARNING message will be displayed. From each "warning messages" item page, we can access the first "fault messages" item page by pressing the right arrow key. The first page contains only one message.

If there are several messages, they will be displayed 2 at a time only, on the following pages. In this example there are 2 fault message pages.The number of ECAM message item pages and FAULT message item pages is not necessarily the same.

The fault messages are displayed in the order of acquisition by the CMC, minute by minute. The last message memorized is displayed first. If there are no failures, the NO FAULT message will be displayed. From each fault message item page, it is possible to go back to the first warning message item page by pressing the left arrow key.

In our example, the prompt (<) before the second fault message means that this fault is also detected by other systems as external failures. These systems are called IDENTIFIERS.

The IDENTIFIERS page lists the fault message and the name of the systems, other than the source, which detected the fault. A maximum of 6 systems can be displayed.

This screen shows a summary of the main pages of the MCDU described in the

(63)

A340-500/600 TECHNICAL TRAINING MANUAL

(64)

MENU NORMAL MODE D/O

FWUT200

POST FLIGHT REPORT PRINT

All the information presented on the POST FLIGHT REPORT on different MCDU screens, is printed together on one page.

Extra information is added in this POST FLIGHT REPORT print out. In flight, this report is called the CURRENT FLIGHT REPORT. It can be printed at any time.

The ECAM and FAULT messages concerning the same event and recorded in the same minute are printed side by side.

The header presents general information about the flight and the report print out.

The cockpit effects list presents the ECAM messages.

If a warning is generated during a flight phase inhibit it will not be presented to the crew. On the Post Flight Report Cockpit Effects, the warning will be presented and "NOT DISPLAYED" added to the message.

The time of warning or fault message occurrence and the name of the flight phase are displayed.

The FAULTS list presents intermittent failures and permanent failures called hard failures with their source and their identifiers.

(65)

A340-500/600 TECHNICAL TRAINING MANUAL

(66)

MENU NORMAL MODE D/O

FWUT200

PREVIOUS FLIGHT REPORTS

The PREVIOUS FLIGHT REPORTS item gives access to the previous POST FLIGHT REPORTS affected by failures, with a maximum of 64 previous flights.

It will display a maximum of 252 warning and fault messages.

This report presents the list of the previous flights, 4 per page, and allows access to the corresponding PREVIOUS FLIGHT REPORTS. The flights are presented in reverse order on the MCDU screen.

To study the details of these reports, please refer to the POST FLIGHT REPORT topic.

In case of CMC removal/installation, if the new CMC comes from another aircraft, the previous POST FLIGHT REPORTS concerning this aircraft will not be displayed.

If the new CMC comes from the shop, a pseudo flight (00) is created to indicate the date of the first computer installation on the aircraft.

AVIONICS STATUS

In flight or on ground, the AVIONICS STATUS report displays the identity of systems affected by, at least, one CLASS 1 or 2, internal or external failure at the moment of the request.

The entire report can be printed.

This is the list of systems affected by a failure. If no systems are affected, the NO FAULT message is displayed.

On ground, a prompt (<) indicates that a direct access to interactive mode of the selected system is possible.

If the SYSTEM REPORT/TEST mode is selected on one of the other MCDUs, the "DUAL SYSTEM ACCESS" message is displayed on the scratchpad line. This screen shows a summary of the main pages of the MCDU described in the topic.

(67)

A340-500/600 TECHNICAL TRAINING MANUAL

(68)

MENU NORMAL MODE D/O

FWUT200

CLASS 3 REPORT

This report displays the list of the systems affected by class 3 faults and the failures by system on request. This report is created, on ground only, by the CMC upon selection.

A page tells the operator to check that all systems are in normal configuration and enables the CLASS 3 REPORT to be printed.

The affected systems list is the one shown on the MCDU.

To see the list of the class 3 failures sent to the CMC by a computer, you have to select the corresponding adjacent line key.

If there are no failures, the NO FAULT message will be displayed. In the complete CLASS 3 REPORT print out, class 3 failures and affected systems are printed side by side.

The header presents general information about the aircraft identification and the report print out.

A list presents the systems affected by at least one CLASS 3 fault. A list presents the associated CLASS 3 fault messages.

(69)

A340-500/600 TECHNICAL TRAINING MANUAL

(70)

MENU NORMAL MODE D/O

FWUT200

COMPLEMENTARY FUNCTIONS

Filtering and Report programming functions are available via the second page of the maintenance menu.

The SERVICING REPORT and AVIONICS CONFIGURATION REPORT will be studied in dedicated modules.

REPORTS PROGRAMMING

This function allows automatic printout and transmission via the Air Traffic Service Unit (ATSU), of the POST FLIGHT REPORT at the end of the flight.

It also allows the activation of the report filter.

In the displayed configuration, printout and transmission are automatic, but the filter is not activated.

REPORTS FILTERS

Remember that this function allows spurious messages in the POST FLIGHT REPORT to be filtered.

The purpose of this item is to print the content of the filter database and to transmit the filter database to the opposite CMC. The

programming of the filter can be manually performed via a password at engineering level.

This screen shows a summary of the main pages of the MCDU described in the topic.

(71)

A340-500/600 TECHNICAL TRAINING MANUAL

(72)

MENU INTERACTIVE MODE D/O

FWUT200

January 03/05

MENU INTERACTIVE MODE D/O

GENERAL

This module is developed by supposing that the aircraft is on ground and engines shut down.

From the first page of the MCDU Maintenance Menu, the access to the interactive mode through the System report/Test function is gained. This function ensures the dialog between the MCDUs and each system, type 1, 2, or 3, connected to the Central Maintenance Computers (CMCs), on ground only. The page displayed by the CMC gives the list of all the systems sorted by function in the ATA chapter sequence. This list is displayed on 6 pages, which are shown in the following figures.

Each function allows access to the related computers or units dealing with that function.

(73)

A340-500/600 TECHNICAL TRAINING MANUAL

(74)

MENU INTERACTIVE MODE D/O

FWUT200

TYPE 1 SYSTEM TYPICAL MENU

This is a typical type 1 system menu. However, most of the radio-navigation, navigation and communication systems, which are interchangeable with other aircraft, may have a different menu presentation.

The following items shown in the table are always available.

LAST LEG REPORT

The purpose of this item is to present the internal and external class 1 and 2 fault messages, concerning the system, that appeared during the last flight.

PREVIOUS LEGS REPORT

The purpose of this item is to present the internal and external fault messages, concerning the system that appeared during the previous 64 flights. This item is the sum of the LAST LEG REPORT items over several flights.

LRU IDENT

The purpose of this item is to present the part number of the selected system. The serial number and the data base number can also be indicated for certain systems.

GROUND SCANNING

The purpose of this item is to reconfigure the computer BITE as being in flight.

Fault messages Class 1or 2, internal and external Fault messages, detected by the BITE during the activation of this function, are displayed in real time.

TROUBLE SHOOTING DATA

The purpose of this item is to present internal snapshot data concerning any failure of any class for airline engineering use. In most cases, it is coded data and sometimes can be accessed from other reports as, LAST LEG REPORT, PREVIOUS LEGS REPORT, TEST and GROUND REPORT.

CLASS 3 FAULTS

The purpose of this item is to present the class 3 fault messages, concerning the system, that appeared during the last flight.

TEST

The purpose of this item is to initiate tests from the MCDU and display the test results with their failure class. If the test takes more than 1 second, TEST IN PROGRESS xxS and the maximun waiting time are displayed.

If several types of test exist for a system, they must be displayed in line 2R, 3R, 4R or even on a sub-menu page accessible from line key 6R.

Tests are divided into 3 groups :

- Basic or system tests, which have no effect on the aircraft, are accessibles via key 2R.

- Complementary tests, which affect the A/C and require safety precaution, are accessibles via key 3R.

- Additional tests, which are menu guided tests, are accessibles via key 4R.

GROUND REPORT

The purpose of this item is to present the internal fault messages which appeared since the last flight at the moment of the request.

(75)

A340-500/600 TECHNICAL TRAINING MANUAL

MENU INTERACTIVE MODE D/O / GENERAL

SPECIFIC DATA

The purpose of this item is to display specific information in order to help the trouble shooting.

If only one type of specific data exists in the system, the exact name will be displayed in place of SPECIFIC DATA. If more than 2 types of SPECIFIC DATA exist in a system, they must be displayed on a sub-menu page accessible from line key 6R.

(76)

A340-500/600 T2 MAINTENANCE COURSE (ELECTRICS/AVIONICS)

FWUT200

January 03/05 Page 52

(77)

A340-500/600 TECHNICAL TRAINING MANUAL

(78)

MENU INTERACTIVE MODE D/O

FWUT200

TYPE 1 SYSTEM EXAMPLE MENU

To describe the contents of the different items of a type 1 system, it has been chosen the Electric Power Generation System (EPGS), part of the AC ELECTRICAL GENERATION function.

The Ground and Auxiliary Power Control Unit (GAPCU) is the interface unit between the EPGS and the CMCs, but as the EPGS is controlled by 6 computers (1 GAPCU and 5 GCUs), an intermediate page is added to choose the computer from which we have selected the report.

The EPGS menu, which contains most of the type 1 system items, is shown on the figure and will be explained in the following subtopics.

LAST LEG REPORT

This report presents only 2 messages at a time.

The fault messages are recorded by the system with the Universal Time Coordinated (UTC) at which the fault occurred, the 6 digit ATA reference and the class of the failure.

When no failure has been recorded during the last flight, NO FAULT DETECTED message is displayed on the MCDU.

PREVIOUS LEGS REPORT

As the LAST LEG REPORT, this report presents only two messages at a time.

The fault messages is identical to the LAST LEG REPORT plus the date at which the failure occurred and the leg number.

In addition, the identification of the A/C where the failure occurred is included in the header.

LRU IDENT

This report presents: the name, the part number and, in this example, the serial number of the electronic Line Replaceable Units (LRUs) which are included in the EPGS.

Only 2 are displayed at a time, and in this example, on 3 pages.

TROUBLE SHOOTING DATA

This report presents snapshot coded information.

The information presented is aircraft configuration and system configuration.

If no failure has been recorded by the system, NO FAULT DETECTED message is displayed on the MCDU.

CLASS 3 FAULT

This report presents only 2 messages at a time.

The class 3 faults are recorded during the last flight. Only the time and the ATA reference are presented.

SYSTEM TEST

This item, which is a system test, enables initialization of the power up test, among other things.

All faults detected and presented by the system will be analyzed and reported by this test. If the test is OK, "TEST OK "is displayed on the MCDU.

GROUND REPORT

The characteristics of this report are the same as those of the LAST LEG REPORT but limited to the internal failures of any class. The following screens represent a summary of the main screens shown in this topic.

(79)

A340-500/600 TECHNICAL TRAINING MANUAL

(80)

MENU INTERACTIVE MODE D/O

FWUT200

TYPE 2 SYSTEM TYPICAL MENU

Unlike the Type 1 Systems, there is no Menu Mode for the Type 2 Systems. These functions are presented on the MCDU by the CMC (Pseudo mode Menu).

The following items shown in the table are always available.

LAST LEG/GND REPORT

The purpose of this item is to present the class 1 and 2 fault messages, concerning the system that appeared during the last flight and on ground.

LRU IDENT

The purpose of this item is to present the part number of the selected system.

CLASS 3 FAULTS

The purpose of this item is to present the class 3 fault messages concerning the system during the last flight.

TEST

The purpose of this item is to initiate the system test from the MCDU and to display the test result with its failure class. If the test takes more than 1 second, the CMC displays TEST IN PROGRESS xxS with the maximum waiting time.

(81)

A340-500/600 TECHNICAL TRAINING MANUAL

(82)

MENU INTERACTIVE MODE D/O

FWUT200

TYPE 2 SYSTEM EXAMPLE MENU

To describe the contents of the different items of a type 2 system, we have chosen the Battery Charge Limiter 1(BCL 1) , part of the DC ELECTRICAL GENERATION function.

This is the BCL 1 menu.

LAST LEG/GND REPORT

This report, formatted by the active CMC, presents, only 2 at a time, the fault messages with the 6 digit ATA reference and the class of the failure, which are permanently transmitted by the system.

In case of failure detected on ground, after touch down, the fault message will be preceded by "GND".

LRU IDENT

This report, formatted by the active CMC , presents the part number of the BCL 1.

CLASS 3 FAULTS

This report formatted by the active CMC, presents, only 2 at a time, the class 3 fault messages with the 6 digits, ATA reference, which are permanently transmitted by the system.

TEST

During the progress of the test, some information is provided on the MCDU.

If the test is OK, the CMC displays "TEST OK" on the MCDU screen.

The following screens represent a summary of the main screens shown in the topic.

(83)

A340-500/600 TECHNICAL TRAINING MANUAL

(84)

MENU INTERACTIVE MODE D/O

FWUT200

TYPE 3 SYSTEM TYPICAL MENU

This is a typical type 3 system menu. The menu is fully generated by the active CMC.

TEST AND RESET

The only possible item is TEST function or RESET function. In case of failure, the CMC displays the name of the tested or reset component. If the test or reset is OK the CMC displays "TEST or RESET OK".

TYPE 3 SYSTEM EXAMPLE MENU

To describe the contents of the different items, we have chosen 2 examples: Generator Control Unit (GCU) EMERGENCY and then Transformer Rectifier (TR) 1, in the AC and DC GENERATION function.

GCU EMR MENU

If the test is OK the CMC displays "TEST OK" on the MCDU screen. If the test is not successful the respective messages will appear on the MCDU screen.

TR 1 MENU

If the reset is not successful, the fault message shown on the figure is displayed.

(85)

A340-500/600 TECHNICAL TRAINING MANUAL

(86)

MENU SERVICING D/O

FM45D4F45SA0201 01 45 - ONBOARD MAINTENANCE SYSTEMS

FWUT200

January 03/05

MENU SERVICING D/O

GENERAL

This function provides reports with different parameters, which have to be periodically checked, and which may induce servicing actions. The servicing report is accessible through the MCDU.

It can also be printed, dumped if a data loader is installed, or transmitted to the Air Traffic Service Unit (ATSU) via the Aircraft Communication Addressing and Reported System function (ACARS function).

(87)

A340-500/600 TECHNICAL TRAINING MANUAL

(88)

MENU SERVICING D/O

FWUT200

REPORT

The report is available either in flight or on ground.

The servicing report is composed of the different items listed in the table as: - Engines

- Integrated Drive Generator (IDG) - APU

- Hydraulic - Fuel

- Landing gear - Oxygen

- Door and slide bottles - Water/waste

- Air conditioning

The servicing report can be presented in 3 ways. These are: complete format, coupon mode printout and MCDU presentation that will be shown next.

COMPLETE FORMAT

In this case the report is composed of all servicing and summary items presented on two pages.

(89)

A340-500/600 TECHNICAL TRAINING MANUAL

(90)

MENU SERVICING D/O

FWUT200

REPORT (CONTINUED)

COUPON MODE

The purpose of this is to present to the user only items needing action. First, a SUMMARY COUPON is printed, followed by the items where a parameter is under the minimum or above the maximum value of a threshold.

If a servicing item status is "CHECK" in the summary coupon, the summary coupon will be followed by the servicing item coupon, otherwise the status is OK.

(91)

A340-500/600 TECHNICAL TRAINING MANUAL

(92)

MENU SERVICING D/O

FWUT200

REPORT (CONTINUED)

MCDU PRESENTATION

The servicing report, which is displayed on MCDU is complete and therefore includes all parameters. It consists of 11 MCDU pages. Pressing the up and down arrow keys gives you access to the next (or previous) pages that make up the servicing report.

(93)

A340-500/600 TECHNICAL TRAINING MANUAL

(94)

MENU SERVICING D/O

FWUT200

PROGRAMMING

It is possible to program, through the MCDU, certain functions related to the servicing report. You can program a complete report or a coupon mode report. You can also program the automatic transmission to the printer, the ATSU via the ACARS function, and the Multipurpose Disk Drive Unit. Non programmed printouts, dumps or transmissions to the ground have to be made manually.

(95)

A340-500/600 TECHNICAL TRAINING MANUAL

(96)

MENU SERVICING D/O

FWUT200

THRESHOLD AND TEXT INSERTIONS

The airline engineering first needs to define the various thresholds which will be used for the servicing report. The purpose of these thresholds is to

automatically trigger a coupon if they are exceeded. The airline can also add comments and information texts between the coupons.

Report threshold and text insertions are made on a personal computer using software called a Maintenance Option Tool (MOT). Then, when this programming is made, it is loaded in the Central Maintenance Computers (CMCs) using the data loader, if installed.

The servicing report thresholds and information texts database is printed automatically after uploading.

Manual printing of the servicing report thresholds and information texts data base can be done through an MCDU menu.

(97)

A340-500/600 TECHNICAL TRAINING MANUAL

(98)

MENU AVIONICS CONFIGURATION D/O

FM45D5F45AA0101 01 45 - ONBOARD MAINTENANCE SYSTEMS

FWUT200

January 03/05

MENU AVIONICS CONFIGURATION D/O

GENERAL

This function is used to manage the inventory of the aircraft computer part numbers and software diskettes. It is only available on ground and with the Central Maintenance Computer 1 (CMC1).

From the CMS MCDU MENU, the function AVIONICS CONFIGURATION REPORTS enables access to:

- the EQUIPMENT CONFIGURATION REPORT - DISKETTE CONFIGURATION REPORT, and - CONFIGURATION CHANGE

EQUIPMENT CONFIGURATION REPORT

This item displays the list of computer part numbers and, for some, the serial number and/or the data base number.

The part number and serial number are directly read from the computer memory or On Board Replaceable Modules, thus no updating is necessary.

(99)

A340-500/600 TECHNICAL TRAINING MANUAL

(100)

MENU AVIONICS CONFIGURATION D/O

FWUT200

EQUIPMENT CONFIGURATION REPORT CONT´D

(101)

A340-500/600 TECHNICAL TRAINING MANUAL

(102)

MENU AVIONICS CONFIGURATION D/O

FWUT200

DISKETTE CONFIGURATION REPORT

The purpose of this item is to record and check the version of these floppy disks. On each aircraft, a set of floppy disks is available in the cockpit. They contain databases necessary for the operation of some computers.

The diskette configuration report is first defined by the airline engineering using a Maintenance Option Tool (MOT), then loaded in CMC1.

The CMC will keep this report updated because it can read the data base numbers directly from the computers.

(103)

A340-500/600 TECHNICAL TRAINING MANUAL

(104)

MENU AVIONICS CONFIGURATION D/O

FWUT200

DISKETTE CONFIGURATION REPORT CONT´D

Pushing the line key adjacent to Avionics Configuration Reports gives you access to the different MCDU screens as presented in the following example.

(105)

A340-500/600 TECHNICAL TRAINING MANUAL

(106)

MENU AVIONICS CONFIGURATION D/O

FWUT200

CONFIGURATION CHANGE

This function is designed to validate the part number, data base number and software reference changes through the Central Maintenance System (CMS), and is presented on the MCDU only if new part numbers are detected by the CMS.

The philosophy is that if a person changes a computer part number, creating a new part number then the change is checked and validated on the MCDU by another person called the controller.

The items of equipment that are listed are those for which the change has not yet been validated. A password will be entered to validate the new part number.

After validation, the equipment disappears from the list. It is still available in the Equipment Configuration Report.

The configuration change report can be printed through the MCDU. The screens and reports are presented as an example.

(107)

A340-500/600 TECHNICAL TRAINING MANUAL

(108)

MENU AVIONICS CONFIGURATION D/O

FWUT200

PROGRAMMING

It is possible to program the automatic transmission of the configuration change report, to the printer, the ATSU via the ACARS function, or the data loader.

Non programmed printouts, dumps or transmissions to the ground have to be made manually.

(109)

A340-500/600 TECHNICAL TRAINING MANUAL

(110)

MESSAGE D/O

FM45D6F45F10101 01 45 - ONBOARD MAINTENANCE SYSTEMS

FWUT200

January 03/05

MESSAGE D/O

GENERAL

A maintenance message is generated by the system BITE each time a fault is detected and isolated. This message is memorized in the BITE memory and transmitted to the Central Maintenance Computers (CMCs).

The maintenance message must indicate, as directly as possible, the faulty Line Replaceable Unit (LRU). Each message is limited to a maximum of 48 characters in 2 lines of 24 characters.

It can be composed of one or several parts depending on the number of suspected LRUs.

In addition, the ATA 6-digit reference of the suspected LRU is provided. Even if the message is composed of several suspected LRUs, only one suspected element is faulty.

Each part of the maintenance message is composed in accordance with the syntax presented in the next figure.

(111)

A340-500/600 TECHNICAL TRAINING MANUAL

(112)

MESSAGE D/O

FWUT200

MESSAGE CATEGORIES

Any part of these maintenance messages necessarily belongs to one of the 5 categories presented as follows.

CATEGORY 1

When a computer requires maintenance, this may be detected and declared by the computer itself, or a system using the computer. In this case an LRU(FIN) message appears.

CATEGORY 2

In this category, the primary suspected element is a computer generating several signals. The complementary information makes it possible to identify the suspected signal. This signal may be

controlled on the aircraft.

In this case LRU Functional Item Number (FIN) complementary information messages appear, for example as LRU(FIN) SIGNAL NAME, LRU(FIN) BUS NAME and LRU(FIN) DISCRETE NAME.

(113)

A340-500/600 TECHNICAL TRAINING MANUAL

(114)

MESSAGE D/O

FWUT200

MESSAGE CATEGORIES (CONTINUED)

CATEGORY 3

Wiring is only indicated when the conclusion of the BITE analysis is a wiring fault. The wiring can always be involved even if there is no mention of wiring in the message.

In this case wiring signal name messages appear. Some of these messages are shown on the following figure.

CATEGORY 4

These are cases where precise identification of the faulty LRU would require a too complex BITE.

In this case SPECIFIC messages appear.

In this type, only an analysis of the problem by the technicians makes it possible to identify the component involved.

The procedure to be followed is described in the TROUBLE SHOOTING MANUAL (TSM).

CATEGORY 5

The part of the message belongs to this type when the loss of LRU power supply is unambiguously identified. The LRU power supply must then be precisely checked before LRU replacement.

In this case LRU(FIN)Sply messages appear.

It should be noted that the LRU itself may be one of the causes for this loss of supply.

(115)

A340-500/600 TECHNICAL TRAINING MANUAL

(116)

MESSAGE D/O

FWUT200

MESSAGE CONSTRUCTION

In case of ambiguous faults, up to 3 possible faulty LRUs may be indicated in the most probable order, each possibility being separated by the slash sign ("/ "). Only one component is effectively responsible.

In some cases of multiple faults, it is possible that a BITE generate a single maintenance message, which may concern several defective components. These components are then separated by the plus sign ("+"),

LRU1(FIN)+LRU2(FIN).

The ATA reference next to the message corresponds to the first suspected component.

When the "FIN" part of the message is absent, this means that no LRU is directly involved in this part.

The possible combinations are shown as follows, for example: LRU1(FIN)/LRU2(FIN)

LRU1(FIN) BUS NAME/LRU2(FIN)

Two examples are shown in case of LRU1 (FIN)/WRG type. LRU2 BUS NAME TO LRU1...

And LRU1 (FIN)/SPECIFIC/SPECIFIC. And lastly, SPECIFIC/LRU1 (FIN).

(117)

A340-500/600 TECHNICAL TRAINING MANUAL

(118)

MESSAGE D/O

FWUT200

MESSAGE HANDLING

Each Central Maintenance System message is covered by the TSM and is an entry point to trouble shooting.

(119)