B2 - M13.10 - 2012.07.11 Ata45
B2 - M13.10 - 2012.07.11 Ata45
B2 - M13.10 - 2012.07.11 Ata45
eJAMF
Revision: 1JUN2012
11.07.2012
Module 13.10
Author: SaR
For Training Purposes Only
E LTT 2007
On Board Maintenance Systems
EASA Part-66
B2
EJ_M13.10_B2_E
Training Manual
www.Lufthansa-Technical-Training.com
Revision Identification:
S The date given in the column ”Revision” on the face of S Dates and author’s ID, which may be given at the base S The LTT production process ensures that the Training
this cover is binding for the complete Training Manual. of the individual pages, are for information about the Manual contains a complete set of all necessary pages
latest revision of that page(s) only. in the latest finalized revision.
Lufthansa Technical Training
ONBOARD MAINTENANCE SYSTEM FUNDAMENTALS
ATA 45
CMCS FUNCTIONS
The CMCS has 2 modes of operation. The modes are called:
S reporting mode
S and interactive mode.
In the reporting mode, the CMC scans all of the aircraft systems that are
connected to it. As it does this, the CMC memorizes the transmitted fault
information.
This memorized fault information can be read at anytime by use of the MCDU
or a printout from the printer. It can also be sent to the home base via the
datalink system.
FOR TRAINING PURPOSES ONLY!
1. Function
2. Function
FOR TRAINING PURPOSES ONLY!
Figure 6 BITE
HAM US/F-4 SaR 01.10.2007 02|Functions Page 13
Lufthansa Technical Training
ON BOARD MAINTENANCE SYSTEMS FUNDAMENTALS
CMC SYSTEM ARCHITECTURE
ATA 45
CMCS REDUNDANCY
As you will remember, in the reporting mode, information from the various
BITEs is stored in the memory of the CMC.
To be able to read this information after the flight the CMC must be operational.
However, if the CMC fails during flight, this would have a major influence on the
maintenance activities.
It would not be possible to read data or perform tests from the MCDU.
Therefore the CMCS must have a redundancy.
This is completely fulfilled with a second standby CMC.
This identical CMC receives the same input data and the output becomes
active automatically when the normal CMC fails.
On some aircraft, the standby CMC can be activated by pressing a control
pushbutton even if the normal CMC is working.
FOR TRAINING PURPOSES ONLY!
MCDU BASICS
We saw that the MCDU is the main interface to the CMCS.
Now lets discuss some basic information about the MCDU. We will use an
A340 MCDU as an example.
The MCDU consist of:
S a control area with many push buttons and 1 control knob,
S a display area which uses either a color or monochrome CRT or TFT
display
S and several annunciator lights to provide information to the operator.
FOR TRAINING PURPOSES ONLY!
Brightness
Control
Knob
FOR TRAINING PURPOSES ONLY!
Display
Figure 10 MCDU II
HAM US/F-4 SaR 01.10.2007 04|Basics Page 21
Lufthansa Technical Training
ON BOARD MAINTENANCE SYSTEMS FUNDAMENTALS
CMC SYSTEM ARCHITECTURE
ATA 45
MCDU basics cont.
The only annunciator that is important for CMC use is the FAIL annunciator.
It shows you that this MCDU is defective and that you must use another one.
The MCDU MENU annunciator is also not used for CMC operation and its
function will therefore not be discussed here.
FOR TRAINING PURPOSES ONLY!
Scratchpad
FOR TRAINING PURPOSES ONLY!
MCDU PAGES
Another piece of information that you must be able to recognize on the MCDU
is the page number on the title line.
This page number is always shown if the information for the selected title does
not fit onto 1 display screen.
In this case the information is divided into several screens, called pages.
The first digit is the number of the displayed page and the second digit shows
the total number of pages which belong to the same title.
Two page control keys are used to switch from page to page.
One is the ”next page key” shown by a down arrow and the other the ”previous
page key” shown by an up arrow.
FOR TRAINING PURPOSES ONLY!
Figure 24 No Response
HAM US/F-4 SaR 01.10.2007 08|Functions1 Page 49
Lufthansa Technical Training
ON BOARD MAINTENANCE SYSTEMS FUNDAMENTALS
CMC SYSTEM ARCHITECTURE
ATA 45
CMCS report functions 1 cont.
The same procedures are used when a report is sent by ACARS to the home
base.
On the graphic you can now see how an ACARS data link is shown on the
747-400 MCDU.
FOR TRAINING PURPOSES ONLY!
Figure 33 Correlation
HAM US/F-4 SaR 01.10.2007 01|ReportfromlastFlight|B12 Page 67
Lufthansa Technical Training
ON BOARD MAINTENANCE SYSTEMS FUNDAMENTALS
CMC SYSTEM OPERATION
ATA 45
ADDITIONAL INFORMATION
We will have a look at an example of an automatic correlation on the printout of
the post flight report from the A340.
Here you can make a comparison of the content of the display image with the
printout.
The content of the cockpit effect on the left part of the printout is identical to the
upper display image and the fault message on the right part of the printout
corresponds to the lower display.
The time and flight phase is presented in the middle because it is identical for
both sets of information.
The printout is the best entry tool for trouble shooting because of this optimal
arrangement of information.
An additional advantage is that the printout is automatically available at the end
of the flight at engine shutdown.
It often happens that fault messages are reported which have no corresponding
cockpit effect. In our example this results in the left part of the printout being
blank.
FOR TRAINING PURPOSES ONLY!
Figure 34 Printout
HAM US/F-4 SaR 01.10.2007 02|AddInfo|B12 Page 69
Lufthansa Technical Training
ON BOARD MAINTENANCE SYSTEMS FUNDAMENTALS
CMC SYSTEM OPERATION
ATA 45
additional information cont.
The memorization of faults starts at the beginning of the flight, which is defined
as 3 minutes after engine start.
The fault memorization stops when the flight is terminated during the taxiing.
This means that when the aircraft is on the ground, no faults are memorized in
the post flight report.
Flight phase information shows when the failure occurred, in this example flight
phase 6 which is the cruise.
FOR TRAINING PURPOSES ONLY!
HISTORY REPORT
You can see this information from the history in the previous leg reports.
In the previous leg report you get a list of all flights with reported faults, in this
case on 4 different pages.
The presentation of the previous leg report has the same layout as the post
flight report.
This means that no fault history data is lost for up to a maximum of 63 previous
flights.
FOR TRAINING PURPOSES ONLY!
GROUND REPORT
For CMC operation on the ground, the reporting mode is continued as long as
the interactive mode is not selected.
But instead of memorizing the faults they are listed on the MCDU or on the
printout in the ground report, which is called ”Avionics Status” in our Airbus
example.
All systems that are affected by a failure are listed by using the name of the
central computer.
In our example, you can see that the system from the last flight still has a
failure because the SFCC is presented .
When the line select key adjacent to the system computer is pressed, the CMC
is switched into the interactive mode.
FOR TRAINING PURPOSES ONLY!
SYSTEM TEST
There are 2 main purposes for the different test functions on a CMC.
S The first purpose is to confirm that the LRU suspected as the most probable
cause of failure in the last leg report is in fact really faulty
S and secondly to make sure that a repair or component removal solved the
problem.
Up to 3 different tests are available:
S The system test, which is available in all systems,
S the complementary test,
S and the output test.
The complementary test and the output test are only available in certain
systems.
FOR TRAINING PURPOSES ONLY!
FAIL
OK
FOR TRAINING PURPOSES ONLY!
COMPLERMENTARY TEST
You perform a complementary test when a component is not tested during the
system test, for example the moving parts of the Airbus system.
Here you can see that 4 different complementary tests are available for the flap
system.
Before you can start a complementary test, you always get a caution message
that there are moving parts during the test.
This caution advises you that there are risks of personal injury and of possible
damage to the aircraft.
In addition you have to fulfil initial conditions to allow the test to run. For the
flap system for instance, the hydraulic system must be pressurized. Then you
are ready to start the test by pressing the corresponding line select key.
Before the test really starts you get the caution message again to remind you
of the dangers of this test.
Then you have to confirm the start of the test by pressing a different line select
key to the 1 on the previous page.
This is to make sure that the operator is 100% aware of what is going to
happen.
When the test is running the BITE generates inputs to actuators and valves to
start operation and checks the result by reading the feedback signals.
At the end of the test the result is presented in the same way as you saw in the
system test.
To finish, a test close up is necessary to bring the aircraft back to the status it
was in before you started the test.
FOR TRAINING PURPOSES ONLY!
OUTPUT TEST
The third test option on the Airbus CMC is the output test.
Please continue by selecting the air data reference number 1 as the central
computer of the system.
The ADR menu provides the same choices as the flap system menu, but in
addition, an output test item is available.
2 different slew tests are available here.
FOR TRAINING PURPOSES ONLY!
TABLE OF CONTENTS
M13.10 ON BOARD MAINTENANCE SYSTEMS 1
CMC SYSTEM ARCHITECTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
INTRODUCTION TO CMCS . . . . . . . . . . . . . . . . . . . . . . . . 2
CMCS FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CMCS REDUNDANCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
MCDU BASICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MCDU CMCS DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
MCDU DISPLAY AND DATA ENTRY . . . . . . . . . . . . . . . . 30
MCDU PAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CMCS REPORT FUNCTIONS 1 . . . . . . . . . . . . . . . . . . . . 44
CMCS REPORT FUNCTIONS 2 . . . . . . . . . . . . . . . . . . . . 52
CMC SYSTEM OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
REPORT FROM LAST FLIGHT . . . . . . . . . . . . . . . . . . . . . 58
ADDITIONAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . 68
HISTORY REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
GROUND REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
CMC INTERACTIVE MODES INTRODUCTION . . . . . . . 80
SYSTEM TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
COMPLERMENTARY TEST . . . . . . . . . . . . . . . . . . . . . . . . 94
OUTPUT TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
DATA LOADING SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DATA LOADING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Page i
EJ M13.10 B2 E
TABLE OF CONTENTS
Page ii
EJ M13.10 B2 E
TABLE OF FIGURES
Figure 1 Location of the System Test Switches . . . . . . . . . . . . . . . . . . . . 3 Figure 36 Type of Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 2 Components of a CMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 37 Report Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 3 CMC Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 38 Previous Leg Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 4 Reporting Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Figure 39 Ground Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 5 Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 40 CMC INTERACTIVE MODES . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 6 BITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Figure 41 Additional Trouble Shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 7 CMCS Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Figure 42 Test Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 8 CMC Backup Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Figure 43 Test Sequence I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 9 Components of a MCDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Figure 44 Test Sequence II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 10 MCDU II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Figure 45 System Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 11 MCDU III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 46 Clear Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 12 Brightness Control Knob . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Figure 47 Complementary Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 13 MCDU MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 48 Output Test Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 14 MCDU MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 49 Slewing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 15 MCDU Display I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Figure 50 Slewing Process II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 16 MCDU Display II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 51 End of Slewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 17 MCDU Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Figure 52 Data Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 18 Page Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 53 Data Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 19 747 MCDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 20 A 320 MCDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 21 RETURN Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 22 CMC Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 23 747 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 24 No Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 25 ACARS Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 26 Printout Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 27 Page Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 28 SEND Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 29 Report from last Flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 30 Report from last Flight II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 31 Fault Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 32 Fault Message Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 33 Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 34 Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 35 Flight Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Page i
EJ M13.10 B2 E
TABLE OF FIGURES
Page ii
EJ M13.10 B2 E
TABLE OF FIGURES
Page iii
EJ M13.10 B2 E
TABLE OF FIGURES
Page iv