Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Presented by
AUFFRET Hervé
Indication / Warning / Maintenance System
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 2
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 3
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
MAINTENANCE LEVELS
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 4
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
MAINTENANCE LEVELS
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 5
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 6
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
TSM TSM
EFIS, LOCAL or OBSV Index ECAM or CMS Index
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 7
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 8
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AIRCRAFT SYSTEMS
Operational failure messages Maintenance failure messages
(function lost) : (LRU lost) :
"Warnings/Malfunctions" "CMS Fault Messages"
FWCs CMC
LOG BOOK
POST FLIGHT
Warnings/Malfunctions REPORT
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
ECAM or TSM
EFIS Warnings/ CMS
Malfunctions Fault
indications HYDB RSVR LO PRESS
-BLUE ELEC PUMP....OFF
or
TEST>
LOCAL FAULT
indications Fault Isolation Procedures
associated to Warnings/Malfunctions MCDU
and CMS Fault Messages
FAULTY LRU
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 9
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 10
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
MESSAGE CLASSIFICATION
MESSAGE CLASS 1 2 3
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 11
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. Message Classification
5. TSM Use
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 12
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
TSM USE
TSM LEVEL ATA CHAPTER LEVEL ATA SECTION LEVEL
Fault
I-ECAM Symptoms PB 201
XX-ECAM
I-EFIS
FAULT
XX-EFIS ISOLATION
I-LOCAL
XX-LOCAL
PB 301
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
I-OBSV
XX-OBSV BLOCK
I-CFDS
DIAGRAM
XX-CFDS
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 13
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
I-LOCAL
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 14
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
A320
TROUBLE SHOOTING MANUAL
AUTO FLIGHT FAULT SYMPTOMS A320
CFDS FAULT MESSAGES FAULT UBLE SHOOTING MANUAL
WARNINGS/MALFUNCTIONS ISOLATION O FLIGHT FAULT SYMPTOMS
SOURCE MESSAGE ATA C PROCEDURE CFDS FAULT MESSAGES FAULT
ISOLATION
EWD WARNING(S) SOURCE MESSAGE ATA C PROCEDURE
CFDS MESSAGES
22-ECAM
EFF : ALL Page 101
22-CFDS
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Jan 01/94
Page 101
XXX
Jan 01/94
34-EFIS
EFF : ALL Page 101
Jan 01/94
XXX 22-OBSV
22-LOCAL Page 101
Jan 01/94
EFF : ALL Page 101
Jan 01/94
XXX
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 15
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
A320
TROUBLE SHOOTING MANUAL
TASK 21-26-00-810-808
Monitoring Discrete Output to Extract Fan
1. Possible Causes
- FAN EXTRACT, AVCNS VENT (7HQ)
TASK 21-26-00-810-805 - Wiring between the pin C of the extract fan and the AEVC (2HQ)
REFERENCE DESIGNATION
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
FAULT CONFIRMATION
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
5. Close-up
Close Access
FAULT ISOLATION 21-26-00
EFF : ALL Page 213
Jan 01/94
XXX
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 16
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
A320
TROUBLE SHOOTING MANUAL
EXT A320
TROUBLE SHOOTING MANUAL
FLAPS TASK SUPPORTING DATA
RET
functions
SHOOTING DATA
Cs have TROUBLE SHOOTING DATA for a given fault which shows :
FLIGHT WARNING FLIGHT WARNING antennae messages
COMPUTER 1 COMPUTER 2 mplementary information, if applicable; The complementary information is
(REF 3-53-00) (REF 3-53-00)
26VAC 26VAC
SYSTEM 2 SYSTEM 2
X INPUTS.
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 17
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
AGENDA
1. Maintenance Levels
4. TSM Use
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 18
TROUBLE SHOOTING PHILOSOPHY WITH A320 CFDS/A340 CMS
• Purpose:
• Reduce number of items in the PFR
• Improve PFR pertinance
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 19
© AIRBUS S.A.S. All rights reserved. Confidential and
proprietary 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.
© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.
Troubleshooting with A320 CFDS / A340 CMS - REFERENCE 952.1003/05 May 2005 Page 20
A340-500/600
TECHNICAL TRAINING MANUAL
ONBOARD MAINTENANCE SYSTEMS
A340-500/600 T2 MAINTENANCE COURSE (ELECTRICS/
AVIONICS)
This Page Intentionnaly Left Blank
This document must be used for training purposes only
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).
CMS data can also be loaded into the CMCs through the MDDU.
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.
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.
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.
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.
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.
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.
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.
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.
TR 1 MENU
If the reset is not successful, the fault message shown on the figure is
displayed.
COMPLETE FORMAT
In this case the report is composed of all servicing and summary items
presented on two pages.
The report shown in the next figure is presented as an example.
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
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.
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.
DC 1+ DC 2 MAINTENANCE PHASE
When a type 3 system unit fails, the system status is sent to the CMC.
The CMC processes the class 1 fault message and stores it in its
CURRENT FLIGHT memory zone. At the same time, if there is a
warning message, it is also memorized.
The AVIONICS STATUS zone memorizes the name of the system as
long as the fault is present.
The CMC consolidates the fault status at DC1/NULL transition to
process the POST FLIGHT REPORT.
In normal operation, the main clock provides date and time data to the ECAM
and the Aircraft System computers through Central Maintenance Computer
(CMC) 1 or CMC 2. The latter cyclically check and validate the time and the
date from the clock every second.
ABNORMAL OPERATION
In case of main clock failure, the active CMC internal clock takes over.
The CMC internal clock supplies time and date to the ECAM and the Aircraft
System computers.
In addition, if a long power interrupt affects both CMCs, for more than 5
seconds, the Universal Time Coordinate (UTC)-DATE INIT item is added in
the Central Maintenance System menu. In this case time and date are no longer
provided to the ECAM and Aircraft System computers.
These functions enable the crew to initialize the time and date.
In this menu, UTC and date can be initialized by entering data in the
scratchpad and by pressing the corresponding INIT key.
Supposing that you have already initialized the date and entered the UTC in the
scratchpad, you have to validate it by pressing the correct key.
The printer is used for printing Central Maintenance System reports and other
system reports.
It is loaded with a 8.5 inch (216 mm) wide paper roll.
CONTROLS
The printer face features two pushbutton switches and two annunciator
pushbutton switches.
The TEST switch is used to perform a functional test of the printer.
The SLEW switch is used to feed the paper out.
The PAPER ALARM switch includes an amber caution light which illuminates
if a new paper roll is required.
The OFF switch is used to switch the printer ON or OFF. It includes a status
indicator light which illuminates if the printer is set OFF.
Several systems can be connected to the printer, which uses a multiplexed The CMS is connected to the printer in order to print fault reports for
input receiver, so that the printer is in communication with only one of the maintenance in flight or on ground.
possible source systems at a time. When the last engine is shut down, a Post Flight Report may be automatically
The input data is transmitted on ARINC 429 buses and is ready to be printed. printed.
The output data is transmitted on a single low speed ARINC 429 bus to It is possible to print data displayed on the MCDU by pressing the Print line
indicate the printer status (Ready, Busy, etc...). select key.
The printer is usually connected to the following systems:
- the Flight Management Guidance and Envelope Computers (FMGECs). ENGINE INTERFACE VIBRATION MONITORING UNIT
- the Central Maintenance System (CMS).
Each EIVMU automatically constitutes a report in case of an excessive
- the Engine Interface and Vibration Monitoring Units (EIVMU).
vibration level or upon a manual request, before the flight, via the CMS in
- the Air Traffic Service Unit (ATSU). interactive mode.
- the Aircraft Condition Monitoring System (ACMS). The report is stored in the EIVMU in a volatile memory. Therefore it may be
Some examples of prints are given hereafter. lost before printing in case of a power supply interruption.
The report is printed on ground as soon as the engine shuts down.
FLIGHT MANAGEMENT GUIDANCE AND ENVELOPE The MCDU page is accessed from the MCDU EIVMU main menu page and
COMPUTERS allows frequency analysis acquisition requests. When all the values are
correctly entered the request is validated by pressing on the RETURN key.
The FMGECs are connected to the printer so the following types of report can
be printed:
AIR TRAFFIC SERVICE UNIT
- Flight plans,
- take-off data, The ATSU is connected to the printer in order to print:
- wind data - The data elaborated by itself received from the ground and from peripheral
- and flight reports. computers and the data entered by the MCDUs.
The print function allows various Flight Management (FM) reports to be
printed, either automatically or manually. AIRCRAFT CONDITION MONITORING SYSTEM
The FM pre-flight report becomes available when the current flight phase is
The ACMS collects data from aircraft systems and formats it to suit various
PREFLIGHT, whether or not any data has actually been entered.
standard reports, which can be printed.
The ACMS report prints can be done manually via the MCDU or
automatically.
Depending on programming, some reports can be triggered and then printed by
the remote ACMS print push button.
The up and down data loading system is defined as an interface between the
onboard computers and the ground-based data processing stations (PCs).
The system has two functions, a main uploading function and a downloading
function.
From a data processing media (3.5 inch disk), the onboard computers use the
uploading function to update their databases or to modify part of their
operational software (no OBRM on the front face of the computers).
The downloading function is used to transfer to a 3.5 inch disk the data
recorded by certain computers during aircraft operation. This disk-stored data
can be directly analyzed on ground by the airlines.
Note that all the computers involved by the system use the uploading function.
Only a limited number also use the downloading function.
Interconnection between the onboard data loader, called Multipurpose Disk
Drive Unit (MDDU), and the onboard computers using the system, called
target computers, is mainly ensured by input and output ARINC 429 buses.
Loading operation is basically controlled by the Data Loading Routing Box
(DLRB) by means of the Data Loading Selector (DLS).
ON BOARD MAINTENANCE SYSTEM TEST / REPORT PRINTING SYSTEM MCDU MENU CAPABILITY
ON BOARD MAINTENANCE SYSTEM TEST / UP/DOWN DATA LOADING SYSTEM MCDU MENU CAPABILITY
(DLS/DLRB)
The Central Maintenance Computer (CMC) data base is made up of a CMC
filter database, a servicing report database and a diskette configuration
database. Each database must be individually prepared prior to the loading of
the entire CMC database, by using the appropriate MAINTENANCE TOOL.
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
Note: The three first digits refer to the CMC filter Data Base
Number (DB/N), the three following ones refer to the servicing
report data base and the three last digits to the diskette
configuration data base.
Return to the SYSTEM REPORT/TEST page. Perform the same
check for opposite CMC.
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO LOAD THE DATA BASE OF THE CMC (DLS/DLRB) (CONTINUED)
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / ENABLE/DISABLE OF THE FLIGHT REPORT FILTER
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / ENABLE/DISABLE OF THE SERVICING REPORT (COUPON OR COMPLETE MODE)
NOTE:
If there is still paper on the spool:
- cut the paper,
- Slew the engaged paper until it is fully out.
ON BOARD MAINTENANCE SYSTEM LINE MAINTENANCE / PROCEDURE TO INSTALL PAPER IN THE PRINTER
Menu
The Onboard Maintenance System (OMS), beside its basic functions, provides
the maintenance operator with a compilation of LRU P/N, data base numbers
and, software references installed on the aircraft, called AVIONICS
CONFIGURATION DATABASE.
On the A/C, when one of these LRU, software or database is changed or
updated, the CMS detects this new configuration, thanks to the AVIONICS
CONFIGURATION DATABASE. It displays it through an onboard printed
coupon. Then the AVIONICS CONFIGURATION DATABASE may be
updated and validated through the following task.
NOTE: Make sure that all systems are powered and not in interactive
mode, to allow the active CMC to check the actual avionics configuration.
Pushing the START key launches the CMC avionics configuration reports
construction.
Push the CONFIGURATION CHANGE key to access to the corresponding
page.
NOTE: This line is displayed only if the active CMC has detected a
configuration change.
The CONFIGURATION CHANGE page(s) shows all changes detected by the
active CMC, one change per page. The VALIDATE key will validate the LRU
change displayed on the page. This key is protected by a passcode.
Switch off the two other MCDUs and enter the access code "XXX" on the
scratchpad to be able to validate the change.
Push the VALIDATE key to access the CONFIGURATION VALIDATION
page.
Push the VALIDATE CHANGE key and check for confirmation.
You can now transmit to the slave CMC, the active CMC as memorized the
AVIONICS CONFIGURATION DATABASE. This allows you to use the slave
CMC in case of active CMC failure.
Put the aircraft back into its initial configuration.
AIRBUS S.A.S.
31707 BLAGNAC CEDEX, FRANCE
AI/STDC
REFERENCE FWU04451
JANUARY 2005
PRINTED IN FRANCE
AIRBUS S.A.S. 2002
ALL RIGHTS RESERVED