100% found this document useful (1 vote)

575 views

MPC Dmu System Requirements

This document provides the functional requirements for the DMU system, which is a component of the MPC P/N ED35E109-01-XX for ATR 42 and ATR 72 aircraft. The DMU system requirements are given for recording and displaying flight data and aircraft parameters. The document describes the interfaces between the DMU and other aircraft systems to acquire data, as well as the data recording, storage, and output functions of the DMU.

Uploaded by

Luis Enrique La Font Franco

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (1 vote)

575 views

MPC Dmu System Requirements

Uploaded by

Luis Enrique La Font Franco

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 220

MPC FOR ATR 42 AND ATR 72

P/N ED35E109-01-XX
DMU SYSTEM REQUIREMENTS DOCUMENT

Document 3300059268 Édition / Issue N° 03 January 7th, 2008

(SK-0000207279)
This document is the property of Sagem DS.
It is strictly forbidden to reproduce or transmit the contents of this
document without the written permission of Sagem DS.

MPC FOR ATR 42 AND ATR 72

P/N ED35E109-01-XX
DMU SYSTEM REQUIREMENTS DOCUMENT

Reference : 3300059268 Édition / Issue N° 03

(SK-0000207279)
Date : January 7th, 2008

KEY WORDS & SUMMARY

MOTS CLES & RESUME
_________________
Mots clés / Key words:
MPC, AFDAMU, DMU, SRD

Résumé / Summary:
The present document gives the functional requirements of the DMU system, component of the MPC
P/N ED35E109-01-XX (XX ≥ 02) for ATR 42 and ATR 72 aircraft

Sagem DS F6151
Unité R & D 23 - Système d'Information Avion
101-10002-851 Ind. I

Établissement de Massy - 178 Rue de Paris - 91344 MASSY CEDEX

3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
RECORD OF REVISIONS
January 7th, 2008

RECORD OF REVISIONS
ETAT DES EVOLUTIONS
_______________

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

ALTEN
01 19/10/2004 All Document creation. (N. DELAPORTE)
P. WIEDERKEHR

02 20/05/2005 All Replace AFDAMU by MPC ALTEN

(N. DELAPORTE)

P. WIEDERKEHR

1 Add SFIM abbreviation

4 Remove BITE/CMC SYSTEM REQUIREMENTS

DOCUMENT

Add two ATR Service Information Letters

Add a SFIM FDAU System requirements

6 MPC will comply with several ATR Flight data

recording systems instead of only ATR 72 ones.

7 Add “ARINC 573 aircraft parameters acquisition”

8 8 discretes inputs instead of 9

11 Add access to analog and discrete parameters through

an internal ARINC 429 bus

14 Interface to MCDU: Add the “Initialize documentary

data” function

15 Add FDAU interface

17 Add access characteristics to ARINC 573 PCM

parameters

Add the access to “Main Gear Squat Switch” and

“All Gear Squat Switch” parameters in the V0
configurations.

18 Delete following sentence: “The EUC rules of PCM

parameters are given in Appendix 6.1.2.”

- II -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
RECORD OF REVISIONS
January 7th, 2008

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

19 Modify NP limit for Engine shut-down detection to

60% instead of 50%

21 Bring minor modifications and clarifications in Figure

5-1 (Logical Flight Modes Detection)

22 Bring minor modifications (part related to computation

of flight modes 9 and 10) and clarifications in Figure
5-2 (Detailed algorithm for Flight Mode determination)

22 Remove Figure 5-3 – Post-Flight Time Management

and integrate it in a simplified form in Figure 5-2 –
detailed algorithm for Flight Mode determination

23 Add definition of A/C type, A/C Number and A/C tail

parameters

30 Modify text in the « Data formatting for Printer »

section

33 G-Meter report: change Air/Ground parameter used

for starting the detection of minimum & maximum
accelerations: “all gear squat switch” discrete instead
of main gear squat switch discrete.

41 G-Meter report: The flight number appearing in the

report will be computed at previous take-off instead of
at report generation

57 Replace a reference to « BITE/CMC SYSTEM

REQUIREMENTS DOCUMENT » by a reference
another section of the document
Add messages files reference

66 Add parameter menu, time & flight setting page, lights

test page

69, 70, 71 Add parameter menu

74 Replace the following alpha call-up:

• AIR by MGEAR
• NH by NHL and NHR
• NP by NPL and NPR
• AIRSP by IAS
• VTG12, VTG34, VTG56, VTG78 by GVER
• LAT12, LAT34 by GLAT
• LON12, LON34 by GLON

83 Add lights test page

- III -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

118 Add time & flight setting

114 Modify text in “ACMS reports” section

140 Replace Aircraft Ident by A/C Number

155 Add the requirements related to the check of A/C

ident

158 to 167 Add the input characteristics of ARINC 573 PCM

parameters

178 Update the alpha call-up default list

187 Add BITE/CMC Excel file description

03 29/06/2005 All New software version as requested by ATR: modify ALTEN

TCAS protocol. (N. DELAPORTE)

7 Add upload of database with aircraft list.

7, 15, 93 Add TCAS as an implemented function.

74 Update predefined call-up lists.

141 Update PCMCIA LED management description.

162 Update DATE parameter.

173, 174, Update maintenance words.

176, 177

178 Update alpha call-up list.

187 Add where to find the Excel files.

01 04/07/2006 All New software version as requested by ATR. ASSYSTEM

(F. DEVOT)
New GITIS reference 3000260589-R10-000 for the ALTEN
document. (N. DELAPORTE)
SII
Revision number reset to 01. (J. THEROND
A. MONCLIN)
LGM
(D.ROBILLARD)

1 §1. Abbreviations added mainly for Ethernet

functionality.

4 §2. List of applicable documents updated

7 §4.1: generalities updated

- IV -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

13 §4.4.8: Standard SAR and Extended SAR added

13 §4.4.9: SAR Event recording added

13 §4.4.10: Interface to ACARS (ARINC 724B) added

16 §4.4.21: Ethernet interface added

17 §5.1: Add A429 speed configuration with discrete

capability

18 §5.2.2: Following parameters added:

• Engine family

• Engine flight hours

• Engine cycle

• Remote print button

• DMU identification

• Database version

• Database revision

23 §5.2.2.6: Modify A/C tail management.

24 §5.2.2.8: Add the engine S/N management.

33 §5.3.2.1: Report <02>: Cruise added

36 §5.3.2.2: Report <03>: Exceedance added

41 §5.3.2.3: Report <15>: G-Meter : Add AIR/GROUND

parameter for V0 configuration.

44 §5.3.2.4: Report <16>: Ident added

47 §5.3.2.5: Report <22>: Flight CMC added

48 §5.3.2.6: Report <23>: GND Test CMC added

49 §5.3.2.7: Report <24>: Instant Flight CMC added

58 §5.9: SAR functionality specified

63 §5.12.2.3: General display rules updated for hardcopy

PCMCIA

66 §5.12.3: MCDU pages tree updated

-V-
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

74 §5.12.3.2.3: Cruise and Exceedance menus added

97 §5.12.3.6: SAR screens added into MCDU DAR/QAR

114 §5.12.3.9.3: Reports <02> and <03> added in manual

report request menu

115 §5.12.3.9.2: Reports <02>, <03>, <22>, <23>, <24>

added in stored reports menu

120 §5.12.3.12.1: Air conditionning discretes and ethernet

configuration management added.

129 §5.13: ACARS functions added

140 §5.14.1: Sending of activity label 0172 added on

MPTR output bus

146 §5.16.5.2: Filtered cruise report storage added

147 §5.16.6: SAR data storage on PCMCIA added

148 §5.16.7: MFC fault words storage on PCMCIA disk

added

149 § 5.16.8: Hardcopy of MCDU screens on PCMCIA

disk added

150 §5.17: Ethernet function added

154 §5.18.1: Ethernet autotest added

158 §6.1.1: table of external ARINC 429 parameters

added

161 §6.1.2.1 and §6.1.2.2: explanations improved.

Correction of error word PCM word computation from
SDI and label

162 §6.1.2.3: list of specific ATR PCM parameters

updated

168 §6.2: limits of reports <02>, <03>, <24> added. G-

Meter limits updated.

172 §6.3: Maintenance words updated for Ethernet

functionality, DMU System software ident error, and
MFC buses internal and external failures

178 §6.4: Alpha Call Up list updated

195 §6.7: ECTM recording format added

- VI -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

02 17/08/2006 All Minor updates. SII

(J. THEROND)

4 §2.2: update MPC SRD and OID document

references.

8 §4.2.3.2: add A429 and discrete interface from MFC.

15 §4.4.20: A/C Tail storage on PCMCIA disk added.

18 §5.2.2 : TRIGGER_DAR and TRIGGER_QAR

parameters description removed from this chapter
(already described in §5.5.5.1 and §5.4.3.1)

25 §5.2.2.16: add BP event management.

28 §5.3.1.1.2: add BP event generation.

33 §5.3.2.1.1: remove BP event generation of reports

<02> and <03>.

34 §5.3.2.1.2: HPL, HPR, ACL, ACR modified in printing

format of report <02>.

36 §5.3.2.1.4: PACK_AIR_L/R description and default

state updated.

36 §5.3.2.2.1: remove BP event generation.

38 §5.3.2.2.2: HPL, HPR, ACL, ACR modified in printing

format of report <03>.

43 §5.3.2.4.1: Update FDAU P/N in report <16>.

75 §5.12.3.2.3: add CMC call-up menu.

112 §5.12.3.8: Update FDAU P/N in identification pages.

121 §5.12.3.12.1.1.1: Air conditioning discrete

configuration screen updated and A/C Tail storage on
PCMCIA disk noticed.

124 §5.12.3.12.2: add Ethernet configuration reset

possibility.

126 §5.12.3.13: add database version display.

135 §5.13.3.1: rectify uplink general format.

140 §5.16: name of files stored on PCMCIA is put in upper

case.

148 §5.16.7: add MFC record format.

- VII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

150 §5.16.10: A/C Tail storage on PCMCIA disk added.

151 §5.17.4: Add GSE Ethernet configuration.

158 §6.1.1: update FDAU_CONF_1 parameter

description.

178 §6.4: Alpha call-up default list updated

03 01/12/2006 All Minor updates. SII

(J. THEROND)

LGM
(D.ROBILLARD)

SII
(A.MONCLIN)

68 §5.12.3.1 Renaming of menu entry "QAR/DAR" in

"QAR/DAR/SAR RECORDING"

61,120, §5.11. Adding of infinite changing of reports limits

125,131,
131,136 5.12.3.12 Modification of MCDU menu due to infinite
change of reports limits

§5.12.3.12.3 New MCDU menu for reports limits

§5.13.2.2.3 Modification due to infinite changing of

reports limits

§5.13.2.2.4 Modification due to infinite changing of

reports limits

§5.13.3.3.4 Modification due to infinite changing of

reports limits

13,58 §4.4.8.1 and §5.9.1.1: Standard SAR PEH length

extended to 10 minutes

01 01/03/2007 All New DMU software version : add PW127M ENGINE SII
CYCLES report and modify CMC report <23>. (J. THEROND)

New document reference 3300059268 / SK-

0000207279

Revision number reset to 01

1 §1. : add LCF, RGB, TM abbreviations

7 §4.1 : PW127M ENGINE CYCLE report added

- VIII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

13, 58 §4.4.8.1 and §5.9.1.1: Standard SAR PEH length

reduced from 10 to 5 minutes

14 §4.4.11: MCDU interface description updated

15 §4.4.16: PEC/EEC interface description updated

16 §4.4.22: Add DTU interface.

26 §5.2.2.17: PW127M ENGINE CYCLE specific

parameters computation added

47 to 50 §5.3.2.5 to §5.3.2.7: precisions added in CMC report

specifications (indicate maximum number of events
and number of faults per report)

50 §5.3.2.8: Report <25>: PW127M Engine Cycles

added

69-126 §5.12.3: Rename ACMS into MPC.

68 §5.12.3.1.2: EEC alerts display mentioned in MPC

main MCDU screen

74 §5.12.3.2.3: Presentation of Alpha Call Up Menus

improved. PW127M ENGINE CYCLE report menus
added.

83 §5.12.3.5: Add DTUE sub-menu. Change some sub-

menu position.

89 §5.12.3.5.4: Add DTUE page description.

89 §5.12.3.5.5: PW127 E and PW127 F engines

renamed in PW127 E/M and PW127 F/M

115 §5.12.3.9.2: Indicate the maximum number of

displayable reports. Add PW127M ENGINE CYCLE
report in stored reports menu.

117 §5.12.3.9.3 Add PW127M ENGINE CYCLES report in

manual report request menu

125 §5.12.3.12.3: Remove reference to a deleted menu.

156 §5.19.2: EEC data invalidity monitoring and LCF

component accumulated cycles monitoring added in
continuous checks

171 §6.2.5: Add PW127M ENGINE CYCLES report limits

178 §6.4: update ALPHA CALL UP default list

- IX -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

02 28/03/2007 Following ATR review (ECM ATR-MPC-261 and Stéphane

MPC-SA-EA-0376): LAROSE

36 §5.3.2.1.4: Replacing “ARPET” by “Web ECTM”.

50 §5.3.2.8.1: Modifying automatic trigger condition.

§6.1.1: Modifying parameters NL_L_V2A and

158
NL_R_V2A.

SII
(J. THEROND)
02_01
26/10/2007 Updates of R03 and R15
(draft)
LGM
(D.ROBILLARD)

§5.3.2.1.2 : add APMWEIGHT_T parameter in

34
CRUISE report format.

§5.3.2.2 : FFT MPC-333: R03: simultaneous

36
Exceedance handling

41 §5.3.2.3.1: FFT MPC-334: R15 untimely generation

avoidance

42 §5.3.2.3.5 : Fix errors in line numbers

§5.3.2.4.1 : Update FDAU P/Ns display in V0

43
configuration

47 §5.3.2.5.2 : add new CMC database L53.

48 §5.3.2.6.1 : add new CMC database L53.

74 §5.12.3.2.3 : Update predefined call-up lists.

158 §6.1.1 : add APMWEIGHT_T, DTUE_FAULTST,

DTUE_TRANSST parameters

168 §6.2 : add " GSE modif. allowed" and "MCDU/ACARS

modif. allowed informations for each limit

169 §6.2.2 : add limits "IAS threshold used for ITT

threshold selection" and " Limit data set number"

178 §6.4 : add report <02> and report <03>

troubleshooting alpha call ups

184 §6.5 : DAR frame updated

-X-
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Édition Date Page(s) Description de l'évolution Auteur

Issue Type of revisions Writer

02_02 SII
Minor updates
(draft) (J. THEROND)

All Standardize memory description

4 §2.3 : Update "Technical Specification for CMC"

document reference

55 §5.5.1 : update DAR frame default programming

description

83 §5.12.3.5 : DTUE screen access protection by a GSE

limit

121 §5.12.3.12.1.1.1 : Add explanations on A/C Tail

modification consequences

171 §6.2.5 : add GSE limit 90 "DTUE MCDU screen

enabled". Protect component life limits against GSE
or MCDU/ACARS modifications.

184 §6.5.1 : Add troubleshooting parameter

R02_ECTIMREF in DAR frame

02_03 SII
02_04 (J. THEROND)
Minor updates during verification process of the
02_05
document
02_06
(drafts)

03 January SII
Official release
7th, 2008 (J. THEROND)

- XI -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

CONTENTS
SOMMAIRE
_______________

Le présent document 3300059268 / (SK-0000207279) comprend :

The present document 3300059268 / (SK-0000207279) comprises :

Page(s)

-1 Couverture.................................................................................................. Non numérotée

-1 Cover........................................................................................................... Not numbered
-1 Page de garde ............................................................................................ Non numérotée
-1 Cover sheet ................................................................................................. Not numbered
-1 Maîtrise du document .............................................................................................I
-1 Document Control...................................................................................................I
-1 État des évolutions..............................................................................................II à XI
-1 Record of revisions .............................................................................................II à XI
-1 Sommaire ............................................................................................................. XII
-1 Contents ............................................................................................................... XII
-1 Table des matières ......................................................................................... XIII à XXII
-1 Table of contents ............................................................................................ XIII to XXII
- 196 Pages numérotées............................................................................................ 1 à 196
- 196 .............................................................................................................. Numbered pages 1 to 196

- XII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

CONTENTS
TABLE DES MATIERES

_______________
Page

1. LIST OF ABBREVIATIONS...................................................................................................................... 1

2. APPLICABLE DOCUMENTS ................................................................................................................... 4

2.1. INDUSTRY .................................................................................................................................... 4

2.2. SAGEM DS ................................................................................................................................... 4

2.3. ATR 4

2.4. OTHER DOCUMENTS .................................................................................................................. 5

3. INTRODUCTION ...................................................................................................................................... 6
3.1. PURPOSE..................................................................................................................................... 6

3.2. DEFINITIONS AND TERMINOLOGY............................................................................................. 6

4. OVERVIEW OF DMU SYSTEM ................................................................................................................ 7

4.1. GENERALITIES............................................................................................................................. 7

4.2. HARDWARE CHARACTERISTICS / ARCHITECTURE AND I/O INTERFACE ............................... 8

4.2.1. Hardware characteristics...................................................................................................... 8

4.2.2. Hardware Architecture ......................................................................................................... 8

4.2.3. I/O interface ......................................................................................................................... 8

4.2.3.1 Acquisition interface............................................................................................................. 8
4.2.3.2 Peripherals interface ............................................................................................................ 8
4.2.3.3 PCMCIA interface ................................................................................................................ 9
4.2.3.4 Discrete output..................................................................................................................... 9
4.2.3.5 Test equipment interface...................................................................................................... 9
4.2.3.6 Ethernet interface................................................................................................................. 9

4.3. SOFTWARE ARCHITECTURE ...................................................................................................... 9

4.3.1. Host Software .................................................................................................................... 10

4.3.2. DMU System Software....................................................................................................... 10

4.3.3. DMU Set-up Database ....................................................................................................... 10

4.4. FUNCTIONS OVERVIEW............................................................................................................ 11

- XIII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

4.4.1. Aircraft parameters acquisition ........................................................................................... 11

4.4.1.1 ARINC 429 parameters...................................................................................................... 11
4.4.1.2 FDAU PCM parameters ..................................................................................................... 11

4.4.2. Standard reports ................................................................................................................ 12

4.4.3. Programmable Reports ...................................................................................................... 12

4.4.4. QAR function ..................................................................................................................... 12

4.4.5. DAR function ..................................................................................................................... 12

4.4.6. BITE/CMC functions .......................................................................................................... 12

4.4.7. Management of APM level output discrete ......................................................................... 13

4.4.8. Standard SAR and Extended SAR recordings .................................................................... 13

4.4.8.1 Standard SAR.................................................................................................................... 13
4.4.8.2 Extended SAR ................................................................................................................... 13

4.4.9. SAR Event recording ......................................................................................................... 13

4.4.10. Interface to ACARS (ARINC 724B) .................................................................................... 13

4.4.11. Interface to MCDU (ARINC 739) ........................................................................................ 14

4.4.12. Interface to MPTR (ARINC 740/744) .................................................................................. 14

4.4.13. Interface to ADL/PDL (ARINC 615) .................................................................................... 14

4.4.14. Interface to PTE (RS232)................................................................................................... 14

4.4.15. Interface to MFC ................................................................................................................ 14

4.4.15.1 RS232 .......................................................................................................................... 14
4.4.15.2 ARINC 429 ................................................................................................................... 15
4.4.15.3 Shunt discrete............................................................................................................... 15

4.4.16. Interface to PEC/EEC (ARINC429) .................................................................................... 15

4.4.17. Interface to TCAS (ARINC 429) ......................................................................................... 15

4.4.18. Interface to FDAU (ARINC 429) ......................................................................................... 15

4.4.19. Temporary changes ........................................................................................................... 15

4.4.20. Interface with PCMCIA card ............................................................................................... 15

4.4.21. Ethernet interface............................................................................................................... 16

4.4.22. Interface to DTUE ............................................................................................................... 16

4.4.22.1 Discrete ........................................................................................................................ 16
4.4.22.2 Ethernet........................................................................................................................ 16

5. FUNCTIONAL REQUIREMENTS ........................................................................................................... 17

5.1. ACQUISITION OF AIRCRAFT PARAMETERS ............................................................................ 17

5.2. HANDLING OF PARAMETERS ................................................................................................... 18

- XIV -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

5.2.1. Standard rules ................................................................................................................... 18

5.2.1.1 Alternate system logic ........................................................................................................ 18
5.2.1.2 Engineering Unit Conversion (EUC) ................................................................................... 18
5.2.1.3 Parameter used for internal processing / data filtering ........................................................ 18

5.2.2. Specific rules ..................................................................................................................... 18

5.2.2.1 Flight Mode........................................................................................................................ 19
5.2.2.2 Flight count ........................................................................................................................ 23
5.2.2.3 A/C Type ........................................................................................................................... 23
5.2.2.4 Engine type........................................................................................................................ 23
5.2.2.5 A/C Number....................................................................................................................... 23
5.2.2.6 A/C Tail.............................................................................................................................. 23
5.2.2.7 Engine family ..................................................................................................................... 24
5.2.2.8 Engine S/N ........................................................................................................................ 24
5.2.2.9 Engine flight hours ............................................................................................................. 24
5.2.2.10 Engine cycle ................................................................................................................. 25
5.2.2.11 Remote print button....................................................................................................... 25
5.2.2.12 DMU database version.................................................................................................. 25
5.2.2.13 DMU database revision ................................................................................................. 25
5.2.2.14 DAR running cause....................................................................................................... 25
5.2.2.15 QAR running cause....................................................................................................... 25
5.2.2.16 Button pushed event ..................................................................................................... 25
5.2.2.17 PW127M Engine Cycles parameters ............................................................................. 26

5.2.3. Parameter display rule ....................................................................................................... 27

5.3. ACMS REPORTS ........................................................................................................................ 27

5.3.1. generality........................................................................................................................... 27
5.3.1.1 Triggering conditions.......................................................................................................... 28
5.3.1.2 Pre-event history................................................................................................................ 29
5.3.1.3 Reports storage ................................................................................................................. 29
5.3.1.4 Report output rules ............................................................................................................ 29
5.3.1.5 Reports data formatting...................................................................................................... 30
5.3.1.6 Report limits....................................................................................................................... 32
5.3.1.7 Specific reports computed parameters ............................................................................... 32

5.3.2. Standard reports definition ................................................................................................. 33

5.3.2.1 Report <02>: Cruise........................................................................................................... 33
5.3.2.2 Report <03>: Exceedance.................................................................................................. 36
5.3.2.3 Report <15>: G-Meter ........................................................................................................ 41
5.3.2.4 Report <16>: Ident ............................................................................................................. 43
5.3.2.5 Report <22>: Flight CMC ................................................................................................... 47
- XV -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

5.3.2.6 Report <23>: GND Test CMC ............................................................................................ 48

5.3.2.7 Report <24>: Instant Flight CMC ........................................................................................ 49
5.3.2.8 Report <25>: PW127M Engine Cycles ............................................................................... 50

5.4. QAR RECORDING ...................................................................................................................... 54

5.4.1. Characteristics ................................................................................................................... 54

5.4.2. Start/stop control................................................................................................................ 54

5.4.3. Specific QAR computed parameters................................................................................... 55

5.4.3.1 TRIGGER_QAR parameter................................................................................................ 55

5.5. DAR RECORDING ...................................................................................................................... 55

5.5.1. Characteristics ................................................................................................................... 55

5.5.2. DAR format general organisation ....................................................................................... 56

5.5.3. DAR data recording rules ................................................................................................... 56

5.5.4. Start/stop control................................................................................................................ 56

5.5.5. Specific DAR computed parameters................................................................................... 57

5.5.5.1 TRIGGER_DAR parameter ................................................................................................ 57
5.5.5.2 DAR frame counter ............................................................................................................ 57

5.6. BITE/CMC FUNCTION ................................................................................................................ 57

5.7. APM LEVEL OUTPUT DISCRETES ............................................................................................ 57

5.8. TRIGGER LOGICS...................................................................................................................... 57

5.9. STANDARD SAR AND EXTENDED SAR FUNCTIONS ............................................................... 58

5.9.1. SAR characteristics............................................................................................................ 58

5.9.1.1 Standard SAR function....................................................................................................... 58
5.9.1.2 Extended SAR function ...................................................................................................... 58

5.9.2. SAR records/memory partition ........................................................................................... 58

5.9.2.1 Standard SAR function....................................................................................................... 58
5.9.2.2 Extended SAR function ...................................................................................................... 59

5.9.3. SAR stored data ................................................................................................................ 59

5.9.3.1 Standard SAR function....................................................................................................... 59
5.9.3.2 Extended SAR function ...................................................................................................... 59

5.9.4. Manual SAR data retrieving ............................................................................................... 59

5.9.4.1 Standard SAR function....................................................................................................... 59
5.9.4.2 Extended SAR function ...................................................................................................... 59

5.9.5. Start/stop control of SAR recording .................................................................................... 59

5.9.5.1 Automatic Start/Stop .......................................................................................................... 59

- XVI -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

5.9.5.2 Manual Start/Stop .............................................................................................................. 60

5.9.5.3 SAR trigger inhibit through ACARS .................................................................................... 60

5.10. SAR EVENT RECORDING.......................................................................................................... 60

5.10.1. Purpose ............................................................................................................................. 60

5.10.2. Trigger Logics.................................................................................................................... 61

5.10.3. Stored Data ....................................................................................................................... 61

5.10.4. Output ............................................................................................................................... 61

5.10.5. Data retrieving ................................................................................................................... 61

5.11. TEMPORARY AND INFINITE CHANGES .................................................................................... 61

5.12. MCDU FUNCTIONS .................................................................................................................... 62

5.12.1. Introduction........................................................................................................................ 62

5.12.2. GENERAL RULES............................................................................................................. 62

5.12.2.1 The screen.................................................................................................................... 62
5.12.2.2 The keyboard................................................................................................................ 63
5.12.2.3 General display rules .................................................................................................... 63

5.12.3. MPC PAGES ..................................................................................................................... 66

5.12.3.1 MPC main menu ........................................................................................................... 68
5.12.3.2 Parameter call up.......................................................................................................... 69
5.12.3.3 Status menu.................................................................................................................. 78
5.12.3.4 Data base loading menu ............................................................................................... 80
5.12.3.5 MAINTENANCE menu .................................................................................................. 83
5.12.3.6 QAR/DAR/SAR menu ................................................................................................... 97
5.12.3.7 PCMCIA menu............................................................................................................ 107
5.12.3.8 Identifications pages ................................................................................................... 112
5.12.3.9 REPORTS menu......................................................................................................... 114
5.12.3.10 Init Time & FLT menu................................................................................................ 118
5.12.3.11 G-meter menu........................................................................................................... 119
5.12.3.12 Init param menu ........................................................................................................ 120
5.12.3.13 CMC menu................................................................................................................ 126

5.13. ACARS FUNCTIONS................................................................................................................. 129

5.13.1. Communication protocol .................................................................................................. 129

5.13.2. Downlink messages ......................................................................................................... 130

5.13.2.1 General messages Format.......................................................................................... 130
5.13.2.2 List of downlink messages........................................................................................... 131

5.13.3. Uplink messages ............................................................................................................. 135

- XVII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

5.13.3.1 General messages Format.......................................................................................... 135

5.13.3.2 Message control: error management ........................................................................... 135
5.13.3.3 List of uplink messages ............................................................................................... 136

5.13.4. Broadcast parameters...................................................................................................... 138

5.13.4.1 Parameters transmitted as received ............................................................................ 138
5.13.4.2 General BCD word...................................................................................................... 138

5.14. PRINTER INTERFACE.............................................................................................................. 140

5.14.1. Dialogue with PRINTER................................................................................................... 140

5.14.2. Printer messages............................................................................................................. 140

5.15. ADL FUNCTIONS...................................................................................................................... 140

5.16. PCMCIA FUNCTIONS ............................................................................................................... 140

5.16.1. Generality ........................................................................................................................ 140

5.16.1.1 PCMCIA interface ....................................................................................................... 140
5.16.1.2 Power cut management .............................................................................................. 141
5.16.1.3 Disk activity indications ............................................................................................... 141
5.16.1.4 PCMCIA error and status reporting.............................................................................. 141
5.16.1.5 PCMCIA disk indications on MCDU............................................................................. 141
5.16.1.6 PCMCIA disk indications on ACARS ........................................................................... 141

5.16.2. QAR recording ................................................................................................................. 142

5.16.2.1 Generality ................................................................................................................... 142
5.16.2.2 QAR files storage on PCMCIA disk ............................................................................. 142

5.16.3. DAR recording ................................................................................................................. 142

5.16.3.1 Generality ................................................................................................................... 142
5.16.3.2 DAR files storage on PCMCIA disk.............................................................................. 143

5.16.4. Data loader emulation ...................................................................................................... 143

5.16.4.1 Uploading functions..................................................................................................... 144
5.16.4.2 Downloading functions ................................................................................................ 145

5.16.5. Report data storage on PCMCIA ...................................................................................... 145

5.16.5.1 Standard storage ........................................................................................................ 145
5.16.5.2 Filtered cruise report storage....................................................................................... 146

5.16.6. SAR data storage on PCMCIA ......................................................................................... 147

5.16.6.1 Generality ................................................................................................................... 147
5.16.6.2 Storage architecture.................................................................................................... 147

5.16.7. MFC fault words storage on PCMCIA disk........................................................................ 148

5.16.8. Hardcopy of MCDU screens on PCMCIA disk .................................................................. 149

5.16.9. Data base version storage ............................................................................................... 150

- XVIII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

5.16.10. A/C Tail storage ............................................................................................................... 150

5.17. ETHERNET FUNCTION ............................................................................................................ 150

5.17.1. Generalities ..................................................................................................................... 150

5.17.2. Implemented network protocols in the DMU ..................................................................... 151

5.17.3. Ethernet start/stop control ................................................................................................ 151

5.17.4. Ethernet configuration ...................................................................................................... 151

5.17.5. Alarms associated to Ethernet function ............................................................................ 152

5.17.5.1 General maintenance word ......................................................................................... 152
5.17.5.2 BITE maintenance word .............................................................................................. 152

5.17.6. FTP Transmission............................................................................................................ 152

5.17.6.1 dirnew command......................................................................................................... 152
5.17.6.2 setdownloaded command ........................................................................................... 153
5.17.6.3 File transfert sequence................................................................................................ 153
5.17.6.4 Error handling ............................................................................................................. 153

5.18. AUTOTEST AND BITE FUNCTION ........................................................................................... 154

5.18.1. List of autotests................................................................................................................ 154

5.18.2. Bite computation and reporting......................................................................................... 155

5.18.3. Alarm storage .................................................................................................................. 155

5.19. CHECKS AND RESET ACTIONS .............................................................................................. 155

5.19.1. Checks at restart.............................................................................................................. 155

5.19.1.1 Check of A/C ident ...................................................................................................... 155

5.19.2. Continuous Checks.......................................................................................................... 156

5.19.3. Reset after loading operation ........................................................................................... 156

5.19.3.1 Reset after system software loading............................................................................ 156
5.19.3.2 Reset after set-up data base loading ........................................................................... 156

5.20. LIGHT TEST.............................................................................................................................. 156

5.21. POWER-DOWN LOGIC/POWER-UP INITIALIZATION .............................................................. 157

5.21.1. Transparency................................................................................................................... 157

5.21.2. LONG cut/COLD start ...................................................................................................... 157

6. APPENDICES ...................................................................................................................................... 158

6.1. DEFINITION OF AIRCRAFT PARAMETERS ............................................................................. 158

6.1.1. External ARINC 429 parameters ...................................................................................... 158

6.1.2. ARINC 573 parameters from FDR dataframes ................................................................. 161

6.1.2.1 Access to any PCM word in the FDR dataframe generated by the FDAU.......................... 161
- XIX -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

6.1.2.2 Access to any PCM word in the FDR dataframe generated by the AFDAU ....................... 162
6.1.2.3 Access to specific ATR PCM parameters in the FDR dataframes generated by the FDAU 162

6.2. LIST OF REPORTS LIMITS PROGRAMMED ON THE GSE...................................................... 168

6.2.1. Cruise report <02> ........................................................................................................... 168

6.2.2. Exceedance report <03>.................................................................................................. 169

6.2.3. G-Meter report <15> ........................................................................................................ 170

6.2.4. Instant Flight CMC report <24> ........................................................................................ 170

6.2.5. PW127M Engine Cycles report <25>................................................................................ 171

6.3. COMPOSITION OF MAINTENANCE WORDS........................................................................... 172

6.3.1. BITE word........................................................................................................................ 172

6.3.2. Maintenance word CPU (MW-CPU) ................................................................................. 173

6.3.3. Maintenance word GENERAL (MW-GEN)........................................................................ 174

6.3.4. Maintenance word PCMCIA (MW-PCMCIA) ..................................................................... 175

6.3.5. Input channel internal failures (STIFDMU)........................................................................ 176

6.3.6. Input channel external failures (STEFDMU)...................................................................... 177

6.4. ALPHA CALL-UP DEFAULT LIST.............................................................................................. 178

6.5. DAR FRAME ............................................................................................................................. 184

6.5.1. Recorded regular parameters........................................................................................... 184

6.5.2. Recorded superframe parameters.................................................................................... 186

6.6. BITE/CMC MESSAGES FILES .................................................................................................. 187

6.6.1. AFCS Excel file................................................................................................................ 187

6.6.1.1 Description table .............................................................................................................. 187
6.6.1.2 Choice table..................................................................................................................... 188
6.6.1.3 FFS table......................................................................................................................... 189
6.6.1.4 Decoding FFS.................................................................................................................. 189

6.6.2. Radio COM/NAV Excel file............................................................................................... 190

6.6.3. PEC/EEC Excel file.......................................................................................................... 191

6.6.3.1 PEC table ........................................................................................................................ 191
6.6.3.2 EEC table ........................................................................................................................ 192

6.6.4. TCAS Excel file................................................................................................................ 193

6.6.5. MFC Excel file.................................................................................................................. 194

6.7. ECTM RECORDING FORMAT .................................................................................................. 195

6.8. ACARS BROADCAST PARAMETERS ...................................................................................... 196

- XX -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

- XXI -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
MPC FOR ATR 42 AND ATR 72
(SK-0000207279)
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
CONTENTS
January 7th, 2008

BLANK PAGE
PAGE BLANCHE

- XXII -
101-10002-851 Ind. I

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
LIST OF ABBREVIATIONS
January 7th, 2008

1. LIST OF ABBREVIATIONS

A/C: Aircraft
ACARS: Aircraft Communications Addressing and Reporting System
ACYC: APU Cycles
ADL: Airborne Data Loader
ADU: Advisory Display Unit
AFCS: Automatic Flight Control System
AFDAMU: Auxiliary Flight Data Acquisition & Management Unit
AFDAU: Auxiliary Flight Data Acquisition Unit
AHRS: APU flight HouRS
AIDS: Aircraft Integrated Data System
APM: Airplane Performance Monitoring
APU: Auxiliary Power Unit
ARINC: Aeronautical Radio, Inc
ARPET: Automated Report Program for Engine Trend
ASCB: Avionics standard communication bus
BPE: Button Pushed Event
BITE: Built-In Test Equipment
Byte: data coded on 8 bits
CMC: Central Maintenance Computer
COM: COMmunication
CSDB: Commercial Standard Digital Bus
DHCP: Dynamic Host Configuration Protocol
DMU: Data Management Unit
DTB: DaTaBase
DTU : Data Transmission Unit with Ethernet
E

DW: (Customer’s abbreviation)

ECTM: Engine Condition Trend Monitoring
ECYC: Engine Cycles
EEC: Electronic Engine Control
EHRS: Engine flight HouRS
EUC: Engineering unit conversion
FDAU: Flight Data Acquisition Unit
FDEP: Flight Data Entry Panel
FFS: Flight Fault Summary
FTP: File Transfer Protocol
GSE: Ground Support equipment
101-10002-851 Ind. I

-1-

Document Sagem DS - Reproduction et divulgation interdites

I/O: Input / Output

IMI: Imbedded Message Identifier
IP: Internet Protocol
LCF: Low Cycle Fatigue
LSB: Less Significant Bit (or Byte)
LSK: Line Selected Key
LRU: Line Replaceable Unit
MAC : Medium Access Control
MCU: Modular Concept Unit
MCDU: Multipurpose Control and Display Unit
MFC: Multi-Function Computer
MPC: Multi-Purpose Computer
MPTR: Multipurpose printer
MSB: Most Significant Bit (or Byte)
MTBF: Mean Time Between Failure
MU: Management Unit
NAV: NAViguation
NVRAM: Non Volatile Random Access Memory
PCMCIA: Personal Computer Memory Card International Association.
PC: Personal Computer
PCM: Pulse Code Modulation
PDL: Portable Data Loader
PEC: Propeller Electronic Control
PEH: Pre-Event History
PLA: Power Level Angle
PROM: Programmable Read Only Memory
PTE: Portable Test Equipment
P/N: Part Number
QAR: Quick Access Recorder
RAD: RADio
RAM: Random Access Memory
RFC: Request For Comment
RGB: Reduction Gear Box
RPB: Remote Print Button
RTCA: Radio Technical Commission for Aeronautics.
SAR: Smart Access Recorder
SFIM: Société de Fabrication d’Instruments de Mesure
SRAM: Static Random Access Memory
SSM: Sign and Status Matrix
101-10002-851 Ind. I

-2-

Document Sagem DS - Reproduction et divulgation interdites

TCAS: Traffic alert Collision and Avoidance System

TCP: Transmission Control Protocol
TFTP: Trivial File Transfer Protocol
TM: Turbo Machine
UDP: User Datagram Protocol
VAC: Voltage alternative current
Word: data coded on 16 bits.
101-10002-851 Ind. I

-3-

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPLICABLE DOCUMENTS
January 7th, 2008

2. APPLICABLE DOCUMENTS

2.1. INDUSTRY
Document designation Reference
[I01] MARK 33, DIGITAL INFORMATION TRANSFER SYSTEM (DITS) ARINC 429-12
[I02] DIGITAL ACMS RECORDER FOR ACMS SYSTEM (DAR) ARINC 591
[I03] AIR TRANSPORT AVIONICS EQUIPMENT INTERFACES ARINC 600-7
[I04] AIRBORNE COMPUTER HIGH SPEED DATA LOADER ARINC 615-1
[I05] AIRCRAFT COMMUNICATIONS ADDRESSING AND ARINC 724B
REPORTING SYSTEM (ACARS)
[I06] MULTI-PURPOSE CONTROL AND DISPLAY UNIT ARINC 739
[I07] Commercial Standard Digital Bus (CSDB) Ed 9 January 14 1998 523-0772774-00911R
[I08] MULTIPLE-INPUT COCKPIT PRINTER ARINC 740
[I09] ENVIRONMENT CONDITIONS & TEST PROCEDURES FOR RTCA DO-160C
AIRBORNE ELECTRONICS/ELECTRICAL EQUIPMENT &
INSTRUMENTS
[I10] SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEM AND RTCA DO-178B Level D
EQUIPMENT CERTIFICATION

2.2. SAGEM DS
Document designation Reference
[S01] MPC OUTLINE AND INTERCONNECT DRAWING 3300058493
[S02] AFDAU SYSTEM REQUIREMENTS DOCUMENT 3000212736
[S03] SYSTEM REQUIREMENTS ACQUISITION AND PROCESSING 4442-C05-ST
SYSTEM FOR EPRS – ATR 42/72 P/N ED34A340
[S04] Ground support equipment user’s manual 3300100356
[S05] MPC FOR ATR 42 AND ATR 72 P/N ED35E109-01-XX DMU 3300021756
OPERATIONAL SOFTWARE CONFIGURATION INDEX DOCUMENT
[S06] Software Development Plan SK-0000200929-01

2.3. ATR
Document designation Reference
[A01] TECHNICAL DOCUMENT MULTI-PURPOSE COMPUTER DO/TA - 4159/03
[A02] DFDR READING SERVICE LETTER for All ATR42-300, ATR42-31-5011 Rev. 2
ATR42-320 aircraft
[A03] DFDR READING SERVICE LETTER for All ATR72 aircraft ATR72-31-6010 Rev. 2
[A04] Technical Specification for CMC DO/TY – 927/06 Issue 2
[A05] PW127M Cycles Report Specification DO/TY – 3116/06 Issue 3
[A06] DFDR READING SERVICE LETTER for All ATR42-400, ATR42-31-5017 Rev 1
ATR42-500 aircraft
101-10002-851 Ind. I

-4-

Document Sagem DS - Reproduction et divulgation interdites

2.4. OTHER DOCUMENTS

Document designation Reference
[O01] IP Protocol IETF RFC 791
[O02] TCP Protocol IETF RFC 793
[O03] UDP Protocol IETF RFC 768
[O04] FTP Protocol IETF RFC 959
101-10002-851 Ind. I

-5-

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
INTRODUCTION
January 7th, 2008

3. INTRODUCTION

3.1. PURPOSE
The purpose of this document is to describe the functional requirements of the DMU system, component of
the MPC P/N ED35E109-01-XX (XX ≥ 02), which will be used as part of the ACMS system in ATR 42 and
ATR 72 airplanes.
The MPC also incorporates the AFDAU system (described in another system requirements document [S02])
that is in charge of managing the crash recorder and also performing the APM function (this function intends
to give indications to the pilot).
The MPC complies with ATR specifications for a Multi-Purpose Computer [A01].
It intends to be compatible with any ATR 42 and ATR 72 flight data recording system using a FDAU
manufactured by SFIM or Sagem DS.
Global MPC hardware specifications have to be found in OID [S01] .

3.2. DEFINITIONS AND TERMINOLOGY

DMU host software: resident software, used to load the system software.
DMU operational software: main software which follows the airworthiness directives and aircraft
manufacturer requirements. This software is loadable and is divided in two parts: a “DMU system software”
and a DMU “set-up data base”.
DMU system software: main part of the operational software, which contains all functions and processing
algorithm to cover aircraft manufacturer requirements. This software is loadable but it can’t be modified by
the customer. It is used to load the set up database software.
DMU set-up database: database software which contains all the configuration data to characterise the
customer application. This software is loadable and can be modified by the customer.
101-10002-851 Ind. I

-6-

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
OVERVIEW OF DMU SYSTEM
January 7th, 2008

4. OVERVIEW OF DMU SYSTEM

4.1. GENERALITIES
The DMU system is dedicated to the aircraft maintenance (including flight data quick access recording
function) and also includes a management function of two APM discretes according to information received
from the AFDAU.
The DMU has been designed to allow the user to customise the system according to his specific
applications, requirements, operating environment and logistics. Programming capabilities are provided, to
allow modification of monitoring functions or implementation of additional monitoring functions.
Most of the functions are configurable or programmable by an "on-ground" equipment called Ground Support
Equipment (GSE), based on a PC. The GSE generates a DMU database, which determines the detailed
functions of the DMU and is supplied to the DMU via a PCMCIA interface.
The customisation that will be performed for ATR will activate the following functions:
− ARINC 429 and ARINC 573 aircraft parameters acquisition,
− System software and set-up database upload from the PCMCIA interface,
− Upload of database with aircraft list,
− Management of two APM discretes,
− Management of trigger logics,
− Management of QAR/DAR recording on a PCMCIA card,
− Management of SAR recording on PCMCIA card,
− Dialogue with a MCDU,
− Dialogue with a Multiprinter,
− Dialogue with an ACARS,
− Management of engine Cruise and Exceedance reports,
− Management of recording of Cruise report in ECTM format,
− Management of a G-Meter report,
− Management of Identification report,
− Management of CMC reports,
− Management of PW127M ENGINE CYCLES report,
− Management of maintenance functions for various aircraft equipment.
− Management of Ethernet link for transmission of PCMCIA files to external equipments via an FTP
server.
Other functions exist but will be either disabled from the GSE database or not used by ATR. However as the
GSE is destined to be usable by the final customer (the airline), some of these functions can be enabled with
the GSE.
These functions include:
− Recording of parameters in NVRAM and PCMCIA disk (SAR functions),
− Management of ACMS reports fully programmed on the GSE.
− Temporary change of DMU configuration (limits, constants) by ACARS uplink requests.
− Moreover, provision has been taken for following function:
− Advisory messages
101-10002-851 Ind. I

-7-

Document Sagem DS - Reproduction et divulgation interdites

4.2. HARDWARE CHARACTERISTICS / ARCHITECTURE AND I/O INTERFACE

4.2.1. Hardware characteristics

For detailed hardware characteristics, refer to "Outline and Interconnect drawing" document [S01].

4.2.2. Hardware Architecture

For detailed hardware architecture refer to "Outline and Interconnect drawing" document [S01]. Hereafter is
given a summary of this architecture.
The DMU consists of:
• one processor board, built around a MOTOROLA MPC860 microprocessor with:
◊ its own local memory:
- RAM working memory: 4 Mbytes.
- NVRAM memory (implemented using battery backed-up SRAM) : 4 Mbytes.
- Flash PROM memory: 12 Mbytes.
◊ Discretes input/output interface
◊ ARINC 429 input/output interface
◊ A PCMCIA interface
◊ Serial Communication Controllers implementing RS232, RS422 and CSDB protocols
◊ An Ethernet interface
• One power supply board common to both DMU and AFDAU part of the unit.

4.2.3. I/O interface

For detailed I/O interface of the DMU part of the MPC unit, refer to "Outline and Interconnect drawing"
document [S01].

4.2.3.1 Acquisition interface

The DMU acquisition interface is made of:
• 8 Discrete inputs,
• 16 Digital ARINC 429 busses (including one from the AFDAU),
• 1 asynchronous HDLC link (from the AFDAU),
• 4 RS422/CSDB busses.

4.2.3.2 Peripherals interface

The DMU can interface with the following onboard equipment:
- MPTR (ARINC 740 or 744)
A bi-directional low speed ARINC 429 link to MPTR
- MCDU (ARINC 739)
A bi-directional low speed ARINC 429 link to a MCDU
- MFC
A bi-directional RS232 link to MFC. This link is shared with PTE. PTE and MFC functions depending of
RS232 link can’t be used at the same time.
4 uni-directional high speed ARINC 429 links from MFC.
101-10002-851 Ind. I

-8-

Document Sagem DS - Reproduction et divulgation interdites

2 discrete from MFC.

- TCAS
A bi-directional low speed ARINC 429 link to a TCAS
- FDAU (for FDEP simulation)
A bi-directional low speed ARINC 429 link that replace the connection between FDEP and FDAU

4.2.3.3 PCMCIA interface

The DMU provides a PCMCIA interface allowing to accept removable type II and III media.

4.2.3.4 Discrete output

The DMU provides the following output discrete:
• DMU Bite Fail
• APM level 1
• APM level 2

4.2.3.5 Test equipment interface

A full duplex asynchronous RS232 link is provided, to connect the DMU to a PTE. This link is shared with
MFC so PTE and MFC functions depending of RS232 link can’t be used at the same time.

4.2.3.6 Ethernet interface

The DMU provides an Ethernet 10/100 Mbits/sec interface allowing transmission of ACMS data (QAR, DAR
and SAR recordings, reports) stored on PCMCIA disk to any external equipment, via an FTP server.

4.3. SOFTWARE ARCHITECTURE

The DMU software is made of three parts:
• one resident software called HOST SOFTWARE,
• one loadable software called DMU SYSTEM SOFTWARE,
• one loadable database called DMU SET-UP DATABASE.
The two loadable software packages have to be loaded into the DMU to achieve the complete functionality of
the DMU.
General software partitioning of the system is as follows:
101-10002-851 Ind. I

-9-

Document Sagem DS - Reproduction et divulgation interdites

HOST N o n lo a d a b le
SO FTW A RE F la s h p ro m

D M U SY STEM L o a d a b le v i a d is c
SO FTW A R E S A G E M c o n tr o ll e d

D M U S E T -U P L o a d a b le v ia d is c
DA TA BA SE C u s to m e r c o n tr o lle d

Figure 4-1 - Software partitioning

4.3.1. Host Software

The resident section called HOST SOFTWARE is under Sagem DS’s control and contains the software
needed to load the DMU system software via the PCMCIA card (see below).
This software load is performed automatically without any MCDU interactions. Dedicated coding of the DMU
software load files indicates the type and version of DMU software and identifies the DMU being addressed
by the software load disk.

4.3.2. DMU System Software

The loadable section called DMU SYSTEM SOFTWARE is under Sagem DS's control and contains the
processing software. This software provides the functionality for the basic system interfaces and the basic
structure of the processing algorithm for the DMU generic functions. It includes all standard DMU functions
being independent from any specific functions programmable by the GSE. This software is loadable via the
PCMCIA card. It is stored in Flash PROM memory and to ensure reliability of the DMU, this flash PROM
memory area is protected against inadvertent data corruption. No functions (except loading and failure
report) will be performed by the DMU if either the system software or the DMU set-up database is
determined to be invalid or not loaded.
Reprogramming of the DMU system software will only be necessary if a new system software version is
required due to recognised software faults or future system modifications. Modification of this software will be
reserved to Sagem DS.

4.3.3. DMU Set-up Database

The loadable section called DMU SET-UP DATABASE contains the configuration data, which characterise
the customer application.
This initial database is controlled by Sagem DS, then the customer can modify it if this database and
associated GSE is provided to him.
The reprogramming of DMU functions by the GSE provides enhanced flexibility and versatility.
The GSE generates a DMU set-up database, which consists mainly of look-up tables and configuration
tables, interpretable by the DMU system software. The database is structured to avoid system hang-up
caused by an erroneous database. This set-up database is loadable via the PCMCIA card. It is stored in
Flash PROM memory and to ensure reliability of the DMU, this flash PROM memory area is protected
against inadvertent data corruption.
The DMU set-up database enables to configure or define:
101-10002-851 Ind. I

- 10 -

Document Sagem DS - Reproduction et divulgation interdites

• constants and limits for standard ACMS reports,

• output rule for reports per trigger code,
• Aircraft and computed parameters definition,
• additional trigger conditions definition,
• QAR/DAR recording map and start/stop conditions,
• SAR recording data sets definition and start stop conditions,
• RPB/BPE programming,
• alpha call-up definition.
The DMU set-up database also contains an export file of the database version. This export file is only stored
in the DMU. It is then possible to retrieve it when downloading data from the DMU and use it as an import file
on a GSE workstation. Loading of this export file is optional and is selectable when the DMU SET UP
DATABASE disk is prepared on the GSE.
Note: due to memory space limitation in the DMU unit, this export file can only be a subset of the database
version.
In addition to above described functions, the database can also contain additional customer software,
providing enhanced programming capabilities to the user. It allows the user to program his own functions,
independent from the DMU basic functions.
The DMU provides mechanisms to run this software and ensure that in any case this software will not disturb
the DMU basic functions.
Sagem DS will provide an initial DMU set-up database containing the aircraft configuration data as described
in section 3.1. A lockout mechanism provided on the GSE will prevent the ATR reserved functions and
constants from being modified by the customer. No additional customer software will be included in this initial
database.

4.4. FUNCTIONS OVERVIEW

4.4.1. Aircraft parameters acquisition

4.4.1.1 ARINC 429 parameters

The DMU performs direct acquisition of ARINC 429 data buses (Up to 16 buses, all high/low speed
programmable), with a checking of message validity before storage (Parity, No data).
Note that analog and discrete parameters that are acquired by the AFDAU are retransmitted by the AFDAU
to the DMU through the internal ARINC 429 bus (named AFDAU in the GSE), so the DMU will accede to
these parameters on this bus.
Each ARINC 429 bus is self-tested by wrap around integrated test routine.
All incoming data may be displayed on the MCDU.

4.4.1.2 FDAU PCM parameters

These parameters are provided to the DMU by the AFDAU in two ways:
− On an asynchronous HDLC line, the AFDAU transmits the FDR frame (which includes all the FDAU
PCM parameters plus new parameters added by AFDAU). Each HDLC frame contains the last
complete FDR sub-frame generated by the AFDAU.
− On the internal ARINC 429 bus (named AFDAU in the GSE), the AFDAU retransmits each PCM word
received from the FDAU.
All incoming data may be displayed on the MCDU.
101-10002-851 Ind. I

- 11 -

Document Sagem DS - Reproduction et divulgation interdites

4.4.2. Standard reports

Standard reports are defined by ATR and consist of fixed data sets collected under pre-defined trigger logics.
The standard reports provided with this DMU version are listed in 5.3.1

The user, via the GSE, can re-program reports limits (specific for each report) and destination (MPTR and/or
ACARS).
In addition to fixed trigger conditions any report can be triggered by:
• programmable trigger conditions,
• manual request on MCDU,
• remote print button (according to GSE programming).

4.4.3. Programmable Reports

In addition to standard reports, up to 69 entirely free programmable reports can be monitored by the DMU.
Those programmable reports are entirely defined by the user via the GSE, i.e.:
• trigger conditions,
• parameters to collect,
• characteristics of collected parameter (collection type and time),
• report format,
• destination.
In addition to programmable trigger conditions, the programmable reports can be triggered by:
• manual request on MCDU,
• remote print button.

4.4.4. QAR function

This function allows recording of the QAR data frame (as received from the AFDAU) on a PCMCIA card.
Recording occurs when a programmable trigger condition is met and runs during a programmable time or
until a stop event are met.
Each trigger condition and each stop condition are defined by a programmable logic tree on the GSE.

4.4.5. DAR function

This function allows recording of a user programmable (on the GSE) DAR data frame on the PCMCIA disk.
The DAR frame can be either a standalone one or with a QAR/FDR basis (received from the AFDAU on the
HDLC line).
The DAR recording rate will be programmable from 64 Words/Sec up to 2048 Words/Sec.
When the DAR uses the QAR basis, the DAR speed can be either the same as QAR one or the QAR speed
multiplied by 2n.
Recording occurs when a programmable trigger condition is met and runs during a programmable time or
until a stop event are met.
Each trigger condition and each stop condition are defined by a programmable logic tree on the GSE.

4.4.6. BITE/CMC functions

These functions allow an operator to perform maintenance operation on various equipment using a MCDU.
101-10002-851 Ind. I

- 12 -

Document Sagem DS - Reproduction et divulgation interdites

4.4.7. Management of APM level output discrete

This function drives the APM level 1 and 2 discrete according to information received from the AFDAU.

4.4.8. Standard SAR and Extended SAR recordings

4.4.8.1 Standard SAR

A SAR integrated in the DMU, with 2 Mbytes NVRAM capacity, allows to store data in a compressed form.
SAR recorder consists of 8 independent recording channels, which are fully programmable by the user. Each
channel has a recording capacity of up to 128 samples per sec. Each channel is recorded according to GSE
programmable start/stop events. Up to 5 minutes of history data can be recorded with each SAR recording
channel. The amount of NVRAM required for the SAR standard function is dependent on the number of
parameters to be recorded, the data compression tolerance limits, the duration of the recording and the
variation of the recorded parameters.
SAR standard is also stored on PCMCIA disk if storage space is reserved for this function on PCMCIA in the
GSE. It can also be downloaded from NVRAM to a special PCMCIA disk prepared with the GSE.

4.4.8.2 Extended SAR

The Extended SAR integrated in the DMU allows to store compressed data exclusively on the PCMCIA disk.
SAR recorder consists of 8 independent recording channels, which are fully programmable by the user. Each
channel has a recording capacity of up to 512 samples per sec. Each channel is recorded according to GSE
programmable start/stop events. Up to 1 minute of history data can be recorded with each SAR recording
channel.
The amount of memory on the PCMCIA disk required for the extended SAR function is dependent on the
number of parameters to be recorded, the data compression tolerance limits, the duration of the recording
and the variation of the recorded parameters.

4.4.9. SAR Event recording

This function allows the storage, when an event is detected, of a user-predefined data set (15 selectable
parameters). A data set contains only one sample of each parameter. An advisory message can also be sent
to the ACARS when an event occurs. Up to 50 different events are monitored, each being defined by a user
programmable logic tree.

4.4.10. Interface to ACARS (ARINC 724B)

This interface provides following functions.
Downlink functions :
• transmit reports either automatically or manually initiated,
• send acknowledgements in response to uplink requests,
• transmit advisory messages when SAR trigger conditions are met, or when SAR data are downloaded on
PCMCIA,
• transmit SAR Event recording statistics upon specific uplink request,
• transmit the unit configuration status upon specific uplink request,
• broadcast programmable parameters to ACARS MU,
• transmit advisory message when PCMCIA disk is removed
Uplink functions :
• trigger reports,
• activate report pre-defined functions,
101-10002-851 Ind. I

- 13 -

Document Sagem DS - Reproduction et divulgation interdites

• modify programming of the DMU (temporary changes),

• enable or disable SAR recordings,
• request SAR event statistics,
• request the unit configuration status,
• modify Engine or APU hours and cycle,

4.4.11. Interface to MCDU (ARINC 739)

This interface allows to:
• display parameters in engineering values,
• display various information about stored reports, QAR/DAR PCM, SAR recording, PCMCIA card,
• trigger reports for test purposes,
• display the contents of the last G-Meter report,
• perform maintenance functions on various equipment.
• Initialise documentary data (Date, Time, Flight Number) for the FDAU.
• Initialise Ethernet configuration for the DMU,
• display alerts of EEC bus invalidity and of engine component life limit exceedance.

4.4.12. Interface to MPTR (ARINC 740/744)

This interface allows to print:
• advisory messages (not provided in this DMU version),
• MCDU displays,
• ACMS reports.

4.4.13. Interface to ADL/PDL (ARINC 615)

Not provided in this DMU version.

4.4.14. Interface to PTE (RS232)

This interface allows to:
• accede to DMU internal memories,
• read and display internal information (ACMS software identifications, DMU BITE),
• read and display data on ARINC 429 buses (acquisition and dialog),
• read and display discrete inputs.

4.4.15. Interface to MFC

4.4.15.1 RS232
This interface allows to:
• accede to MFC version,
• accede to MFC flight fault and basic memories,
• erase MFC memories
101-10002-851 Ind. I

- 14 -

Document Sagem DS - Reproduction et divulgation interdites

4.4.15.2 ARINC 429

This interface allows to accede to MFC alerts using 4 ARINC 429 links high speed (GSE MFC1A, MFC1B,
MFC2A, MFC2B buses).

4.4.15.3 Shunt discrete

When an alert is detected, the MFC activates one of following shunt discrete connected to the DMU :
Master Caution (GSE parameter MC_STATUS)
Master Warning (GSE parameter MW_STATUS)

An additional shunt discrete called TO Config Warning (GSE parameter TCONFIG_WARN), activated by the
MFC , is used to interpret some failures. This discrete is connected to AFDAU and then transmitted to DMU
through the internal ARINC 429 link.

4.4.16. Interface to PEC/EEC (ARINC429)

This interface allows to:
• accede to PEC/EEC maintenance code,
• follow PEC/EEC trim procedure,
• acquire parameters to be displayed on PW127M ENGINE CYCLES report and monitored for MCDU
alerts display.

4.4.17. Interface to TCAS (ARINC 429)

This interface allows to:
• Accede to TCAS maintenance code.

4.4.18. Interface to FDAU (ARINC 429)

This interface allows to:
• Set date and time of FDAU.
• Set flight number.
• Send event flag to FDAU.
• Test the “STATUS SYSTEM” and “STATUS FDAU” lights.

If the FDAU is not available for communication, the interface shall :

• provide an error message to the operator
• disable the previous ability to set parameters of FDAU

4.4.19. Temporary changes

A subset of the reconfiguration data supplied by the DMU set-up database is re-programmable on-board the
aircraft via ACARS.

4.4.20. Interface with PCMCIA card

Interface with the internal PCMCIA card will be used for the following operations:
• Recording of the QAR frame
101-10002-851 Ind. I

- 15 -

Document Sagem DS - Reproduction et divulgation interdites

• Recording of the DAR frame

• Recording of standard SAR, extended SAR, and SAR event.
• Uploading of DMU System software and DMU set-up database into the DMU Flash PROM memory
• Downloading of database export, standard SAR data, SAR Event data, and reports stored in the DMU
memory
• Storage of reports
• Storage of MFC fault data
• Hard copy of MCDU screens
• Storage of A/C Tail
• Management and display of disk contents.

4.4.21. Ethernet interface

Ethernet interface will be used for following operations:
• Transmission of ACMS data (QAR, DAR and SAR recordings, reports) stored on PCMCIA disk to any
external equipment (for instance the DTUE), via an FTP server.

4.4.22. Interface to DTUE

4.4.22.1 Discrete
• This interface allows the transmission of DTUE fault status and DTUE transmission status to the MPC.

4.4.22.2 Ethernet
The Ethernet interface of the MPC (described in §4.4.21) is used to transmit ACMS data to the DTUE.
101-10002-851 Ind. I

- 16 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
FUNCTIONAL REQUIREMENTS
January 7th, 2008

5. FUNCTIONAL REQUIREMENTS

5.1. ACQUISITION OF AIRCRAFT PARAMETERS

All the aircraft parameters acquired by the DMU can come from the following sources:
External ARINC 429 input buses,
Internal ARINC 429 bus from AFDAU,
The FDR frame generated by the AFDAU and received by the DMU in HDLC frames.
The internal ARINC 429 bus from AFDAU to DMU allows the DMU to accede to analog and discrete
parameters as external ARINC 429 parameters.
This internal bus will be used also to transmit the ARINC 573 parameters (FDR frame generated by the
FDAU). The access to these parameters will be facilitated by a pre-acquisition function that will allow on the
GSE:
To address any PCM word and sub-frame(s) with a unique mono-source parameter (including
parameters sampled several times per sub-frame);
To address with a unique mono-source parameter a parameter whose PCM word assignment depends
upon the P/N of the FDAU.
This pre-acquisition function will be applied also to the FDR frame generated by the AFDAU and received in
HDLC frames.
For such parameters the necessary information to accede to them through a GSE parameter is given in
Appendix 6.1.
The unused spare ARINC 429 inputs may be connected on demand to any other aircraft system to enable
special investigations.
The test ARINC 429 inputs can be connected on demand to any DMU ARINC429 output for autotest
purpose.
The characteristics of all buses (including spares) are programmable on the GSE. These characteristics
include transmission speed and port assignment. For each bus, the GSE may indicate a discrete number to
use to determine the speed configuration.
All incoming ARINC 429 labels on each connected bus are acquired by the DMU. If a new label is introduced
on one of the connected input buses or if a new bus providing new parameters is connected to the DMU,
these parameters are accessible for parameter call-up. Once defined on the GSE, they are then usable for
any trigger logics, data recording and ACMS reports.
Parameters being used by the DMU are sampled at programmed sample rates.
The DMU has direct access to the ARINC 429 parameters, which are stored in a memory (RAM protected
during power shut down < 200 ms). Only words with a good parity are stored.
For each acquired parameter, a refresh flag will be set for software processing and failure detection.
Amongst the aircraft parameters that will be used by other functions of the DMU, it must be noted that the
“Main Gear Squat Switch” parameter will have to be retrieved from an AFDAU discrete port for V0
configuration (definition will be found in OID [S01]). For other ATR configurations it will be retrieved from
FDAU FDR dataframe.
Moreover for V0 configuration, the “All Gear Squat Switch” parameter being not available, it’ll be replaced by
the “Main Gear Squat Switch” parameter.
101-10002-851 Ind. I

- 17 -

Document Sagem DS - Reproduction et divulgation interdites

5.2. HANDLING OF PARAMETERS

5.2.1. Standard rules

5.2.1.1 Alternate system logic

Two sources can be programmed on the GSE, for a given parameter.
In that case, following rules are applied for further computations:
• If the first source is valid it is used.
• If the first source is invalid then the second one is taken if it is valid itself.
• If both sources are invalid, then the parameter is declared invalid with the same type of invalidity than
source 1. Invalidity means either parameter not refreshed or parameter with an invalid SSM.
The SSM rule validity is programmable on the GSE for each parameter.

5.2.1.2 Engineering Unit Conversion (EUC)

The DMU provides EUC conversion to convert raw input parameter into the applicable engineering unit. The
GSE allows adding or modifying the conversion constants.

5.2.1.3 Parameter used for internal processing / data filtering

As general rules:
• only valid parameters are used for trigger condition processing.
• all decision parameters are filtered for constants and time.
Two types of parameters can be filtered: aircraft parameters in engineering units, or discrete parameters
(either single discrete or packed status).
For parameters in engineering units, the formula is the following one:
NFV = OFV + α(NRV-OFV)
where:
• NFV = new filtered value
• OFV = old filtered value
• NRV = new raw value
• α is the filter constant and is GSE programmable with 0 < α < 1. Default value for α is 0.33.
For any discrete parameter (general status word or discrete):
The filtered value is updated as soon as 3 consecutive samples are stable, independently for each bit in the
case of a general status word.
As a general rule, when an invalid sample is received, the filtered parameter remains at the same value. The
filtered parameter is declared as invalid after reception of N consecutive invalid raw parameters (invalid =
either not refreshed or invalid SSM).
N is 5 for parameters in engineering units and is 3 for discrete parameters.
When raw parameter becomes valid again, filtered parameter becomes also valid and equal to the raw one.
It is possible to create additional filtered parameters by programming on the GSE

5.2.2. Specific rules

These rules concern specific parameters that will be computed by the DMU.
These parameters will be available on the GSE for user programming purpose.
101-10002-851 Ind. I

- 18 -

Document Sagem DS - Reproduction et divulgation interdites

Parameter definition will include at least:

• input A/C parameters or discrete for computing
• computing algorithm
• computed parameter range
• parameter format and unit
• update rate
• parameter name on the GSE
These parameters are:

5.2.2.1 Flight Mode

The DMU performs flight mode detection every second and the result of this computation is stored in the
FLIMOD parameter, available on the GSE.
This flight mode is especially used for the selection of the reports to be processed but can be used as a
start/stop condition for QAR recording for example.
The flight leg is divided into logical segments or flight modes which are defined below:

1 • Pre-Flight

2 • Taxi-out

3 • Take-off, Roll Initial

4 • Take-off, Roll Final

5 • Initial climb

6 • Flight Phase

7 • Final Approach

8 • Landing roll

9 • Taxi in

10 • Post Flight

The flight phase determination is based on following parameters:

• Main gear squat switch,
• Air Speed,
• Radio Altitude,
• Engine NH,
• Engine NP.

Refer to Figure 5-2 for logical flight mode detection and to Figure 5-3 for detailed flight phase determination
algorithm.
In case of a DMU Power-up, and no flight mode condition encountered, then default flight mode is 1.
If one of the input parameters is not refreshed, the computation of the flight mode will not be updated.
101-10002-851 Ind. I

- 19 -

Document Sagem DS - Reproduction et divulgation interdites

All the flight mode decision parameter limits are programmable by GSE but are protected and only Sagem
DS is able to change them (see their initial value in the following table).

Name of the limit Definition Initial value

C_FM_ALT_C1 Radio altitude limit for Flight Phase detection. 1500 feet
C_FM_ALT_C2 Radio altitude limit for Final Approach detection. 800 feet
C_FM_IAS_C1 Air speed limit for Take off roll final detection. 50 knots
C_FM_NH_C1 NH limit for Take off roll initial detection. 90 %
C_FM_NH_C2 NH limit for Engine start / Taxi out detection. 20 %
C_FM_NP NP limit for Engine shut-down detection. 60 %
C_FM_TO_TIM Post Flight timer duration for Post Flight / Pre Flight detection. 60 sec

Table 5-1 – Definition of the limits used to compute the flight mode
101-10002-851 Ind. I

- 20 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
101-10002-851 Ind. I

January 7th, 2008

Édition/Issue N° 03
(SK-0000207279)
3300059268
1 2 3 4 5 6 7 8 9 10

TAKE OFF TAKE OFF

COMPUTED PRE-FLIGHT TAXI-OUT ROLL ROLL
INITIAL
FLIGHT PHASE
FINAL LANDING
TAXI IN
POST
Document Sagem DS - Reproduction et divulgation interdites
Sagem DS document – May not be reproduced nor disclosed

FLIGHT PHASE INITIAL FINAL

CLIMB APPROACH ROLL FLIGHT
Figure 5-2 - Logical Flight Modes Detection

MAIN GEAR

DMU SYSTEM REQUIREMENTS DOCUMENT

GROUND GROUND GROUND GROUND AIR AIR AIR GROUND GROUND GROUND
SQUAT SWITCH
NP left and

FUNCTIONAL REQUIREMENTS

MPC FOR ATR 42 AND ATR 72

NH left or NH left and NH left or
NP right
ENGINE NH, NP NH right NH right NH right
< 60 % or
> 20 % > 90 % < 90 %
invalid

AIR SPEED AS < 50 Kts AS > 50 Kts AS > 50 Kts AS < 50 Kts
- 21 -

RADIO ALTITUDE ALT<1500 ft ALT > 1500 ft ALT < 800 ft

Notes:
The flight mode detection will be performed only if all parameters are refreshed. If not the flight mode parameter will keep its last computed value.
An empty cell means that the parameter is not used for that condition
All limits needed for the computing are GSE programmable.
Waiting C_FM_TO_TIM after POST FLIGHT phase to turn in PRE FLIGHT
When a NP parameter is invalid, it generates alternatively the minimum and maximum values.
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
FUNCTIONAL REQUIREMENTS
January 7th, 2008

BEGIN

AIRCRAFT YES YES BOTH YES PREVIOUS YES FLIMOD = 3

ON GROUND IAS < C_FM_IAS_C1 NH > C_FM_NH_C1 FLIMOD TAKE OFF
is 1,2,3,9,10 ROLL INITIAL

NO NO NO NO

FLIMOD = 8
LANDING ROLL

PREVIOUS YES EITHER YES

FLIMOD is PREVIOUS YES
NH > C_FM_NH_C2 FLIMOD = 2
is 1,2,3,4,5,6,7 FLIMOD is TAXI OUT
1,2,3,4
NO NO NO
FLIMOD = 1
FLIMOD = 8
PRE-FLIGHT
LANDING ROLL

PREVIOUS YES FLIMOD is 10 for YES

FLIMOD FLIMOD =1
C_FM_TO_TIM sec
is 10 PRE-FLIGHT

NO NO
NO CHANGES

BOTH NP YES FLIMOD = 10

< C_FM_NP POST FLIGHT
or INVALID

NO FLIMOD =9
TAXI IN

PREVIOUS
FLIMOD = 4
FLIMOD TAKE OFF
is 3,4,9 or 10 YES ROLL FINAL

NO
FLIMOD = 8
LANDING ROLL
YES
ALT > C_FM_ALT_C1 FLIMOD = 6
FLIGHT PHASE

YES PREVIOUS YES

ALT < C_FM_ALT_C2 FLIMOD = 7
FLIMOD
FINAL APPROACH
is 6, 7

NO NO

FLIMOD = 5
INITIAL CLIMB

PREVIOUS YES
FLIMOD = 5
FLIMOD
INITIAL CLIMB
is 4,5

FLIMOD = 6
FLIGHT PHASE

Figure 5-3 – Detailed algorithm for Flight Mode determination

101-10002-851 Ind. I

- 22 -

Document Sagem DS - Reproduction et divulgation interdites

5.2.2.2 Flight count

Flight count is an absolute number in the range 0 to 999.
Initial value is 0 when DMU system software is loaded.
It will be memorised at each power-off.
Flight count is incremented by one each time a leg change is detected, until value 999 is reached. Then it is
reset to 0.
Leg change is defined as flight mode transition from "LANDING ROLL” to ”TAXI IN".
Flight count name on GSE: FLCNT.
Format : Integer value on 3 digits. - Unit: none.

5.2.2.3 A/C Type

The A/C type is programmed by an AFDAMU pin programming as shown in Table 5-2.
Name on GSE: ACTYPE.
Format : Integer value on 2 digits. - Unit: none.

5.2.2.4 Engine type

The engine type is programmed by an AFDAMU pin programming as shown in Table 5-2.
The engine type has the same definition than ACTYPE.
Name on GSE: ENGTYPE (decimal display) and SELENGTYPE (binary display)

Discrete port / value ACTYPE

Aircraft type Engine type and
(a logic “1” is a connection to ground,
a logic “0” is open) ENGTYPE
parameter
B27 B26 B25 B24 value
ATR42-300 PW120 0 0 0 0 15
ATR42-320 PW121 1 0 0 0 7
ATR42-400 PW121A 0 1 0 0 11
ATR42-500 PW127E/M 1 1 0 0 3
ATR72-200 PW124 0 0 1 0 13
ATR72-210 PW127 1 0 1 0 5
ATR72-500 PW127F/M 0 1 1 0 9

Table 5-2 – Aircraft/Engine type

5.2.2.5 A/C Number

The A/C number is acquired on the FDAU PCM dataframe (see parameter A/C Ident in section 6.1.2.3).
Name on GSE: ACNUM.
Format : Integer value on 3 digits. - Unit: none.

5.2.2.6 A/C Tail

If the database has not been uploaded with a list of A/C tail and A/C type and A/C number, i.e if the database
is compatible with any aircraft (BYPASS configuration), The A/C tail default value will be the A/C Number
101-10002-851 Ind. I

- 23 -

Document Sagem DS - Reproduction et divulgation interdites

received through the AFDAU if available or to “000000”. The crew can modify the A/C TAIL value using the
"A/C PARAM INIT" MCDU page. (see chapter 5.12.3.12.1)
If the database has been uploaded with a list of A/C tail and A/C type and A/C number (without BYPASS
configuration) the DMU will determine if the A/C type and A/C number parameters received through the
AFDAU matches one item of the list. If yes then the A/C tail parameters will be initialised with the A/C tail
corresponding to this item of the list. (see chapter 0)
Names on GSE: ACTAIL1 (first 4 characters) and ACTAIL2 (last characters).
Format of ACTAIL1 and ACTAIL2 parameters : ASCII value on 4 digits. - Unit: none.

5.2.2.7 Engine family

A parameter is computed by the DMU giving the engine family mounted on aircraft.
Possible parameter values are the following:
ENGFAMILY parameter value Engine family
0 PW

Parameter name on GSE: ENGFAMILY.

Parameter format: integer – 1 digit. - Unit: none.

5.2.2.8 Engine S/N

The engines and APU (if any) S/N can be initialised by operators through the MCDU page “A/C PARAM Init”
(see 5.12.3.12.1). These S/N are made of up to 6 alphanumerical characters.
Names in the GSE:
- ESN_1_1: first 4 characters of engine 1 serial number,
- ESN_1_2: last characters of engine 1 serial number,
- ESN_2_1: first 4 characters of engine 2 serial number,
- ESN_2_2: last characters of engine 2 serial number,
- ESN_3_1: first 4 characters of engine 3 serial number,
- ESN_3_2: last characters of engine 3 serial number,
- ESN_4_1: first 4 characters of engine 4 serial number,
- ESN_4_2: last characters of engine 4 serial number,
- ASN1: first 4 characters of APU serial number,
- ASN2: last characters of APU serial number,
Format : ASCII value on 4 digits. - Unit: none.
Note: On ATR aircraft, only two engines and no APU are available.

5.2.2.9 Engine flight hours

Not provided in this DMU version, the following text is for provision only.
Flight hours are the cumulated time for each engine between main landing gear decompressed and main
landing gear compressed. They are continuously updated during this time. A specific computing is done for
each engine.
EHRS calculation is performed in hours and minutes, but only hours appear in generated reports.
EHRS is set to zero when an engine serial number change is recognised or when it exceeds 99999
101-10002-851 Ind. I

- 24 -

Document Sagem DS - Reproduction et divulgation interdites

EHRS can also be initialised with a special MCDU page “ A/C param init” (see 5.12.3.12.1.2) and by ACARS
uplink request (see 5.13.3.3.9).
The engine flight hours must be updated even if the UTC is not valid (internal software counter).
Parameter name on GSE: EHRS_1 for engine 1 and EHRS_2 for engine 2, EHRS_3 for engine 3 and
EHRS_4 for engine 4.
Parameter format: integer – 5digits.

5.2.2.10 Engine cycle

Not provided in this DMU version, the following text is for provision only.
Engine cycle parameters (ECYC_X, X=1..4) are incremented by one each time a flight phase T/O CLIMB
(PH5) is reached.
ECYC_X is set to zero when an engine serial number change is recognised.
ECYC_X can also be initialised with a special MCDU procedure and by ACARS.
Parameter name on GSE: ECYC_1 for engine 1, ECYC_2 for engine 2, ECYC_3 for engine 3 and ECYC_4
for engine 4.
Parameter format: integer – 5digits.

5.2.2.11 Remote print button

A parameter is computed by the DMU giving the state of the RPB button.
The DMU acquires the RPB discrete at rate of 16 samples per second. If this discrete is set 3 times
consecutive, then the RPB parameter is set to 1. The parameter stays at a 1 state during 1 sec and then
comes back to 0.
Parameter name on the GSE: RPB.

5.2.2.12 DMU database version

A parameter is computed by the DMU giving the DMU database version number.
Parameter name on GSE: DTB_VER.
Parameter format: integer – 8 digits.

5.2.2.13 DMU database revision

A parameter is computed by the DMU giving the DMU database revision number.
Parameter name on GSE: DTB_REV.
Parameter format: integer – 8 digits.

5.2.2.14 DAR running cause

See §5.5.5.1.

5.2.2.15 QAR running cause

See §5.4.3.1.

5.2.2.16 Button pushed event

A parameter is computed by the DMU giving the state of the BPE.
The DMU acquires the BPE discrete at rate of 16 samples per second. If this discrete is set 3 times
consecutive, then the BPE parameter is set to 1. The parameter stays at a 1 state during 1 sec and then
comes back to 0.
101-10002-851 Ind. I

- 25 -

Document Sagem DS - Reproduction et divulgation interdites

The DMU also acquire the BPE on the FDAU dataframe as long as no event was generated by the discrete.
If the BPE is set to 1 in the dataframe, then the BPE parameter is set to 1. The parameter stays at a 1 state
during 1 sec and then comes back to 0.
Parameter name on the GSE: EVENT.

5.2.2.17 PW127M Engine Cycles parameters

Parameters displayed on PW127M ENGINE CYCLES report (see §5.3.2.8) are transmitted to the MPC through
PEC/EEC1 and PEC/EEC2 ARINC429 buses, according to a specific protocol detailed in [A05] document.
All values acquired on PEC/EEC buses are copied into GSE computed parameters.
Specific menus of Alpha Call Up are available for engine cycle parameters display on MCDU (see §5.12.3.2.3)
5.2.2.17.1 Engine identification
Engine identification parameters are transmitted on ARINC label 065. They are copied by the DMU software in
following GSE parameters.
Data GSE parameter
i=1 or 2 (engine number)
k=1 or 2 (parameter splitted in 2 parts)
Engine S/N ENGi_SNk
TM S/N ENGi_TM_SNk
RGB S/N ENGi_RGB_SNk

S/N format is an ASCII characters string AANNNN with A=A..Z and N=0..9
As a GSE computed parameter holds only 4 ASCII characters, two GSE computed parameters are needed to
receive a S/N value. So these parameters are splitted in two parts.
For instance, if engine 1 S/N is 'EB0521', then ENG1_SN1='EB05' and ENG1_SN2='21'

5.2.2.17.2 Engine component identification

P/N and S/N of each LCF component are transmitted on ARINC label 066 (for P/N) and 067 (for S/N). They are
copied by the DMU software in GSE parameters. As for engine identification parameters described in chapter
5.2.2.17.1, two GSE computed parameters are needed to receive a P/N or S/N value.

LCF component GSE parameter

i=1 or 2 (engine number)
k=1 or 2 (parameter splitted in 2 parts)
P/N S/N
LP impeller ENGi_C1_PNk ENGi_C1_SNk
HP impeller ENGi_C2_PNk ENGi_C2_SNk
HP turbine front cover ENGi_C3_PNk ENGi_C3_SNk
HP disk ENGi_C4_PNk ENGi_C4_SNk
HP turbine rear cover ENGi_C5_PNk ENGi_C5_SNk
Interstage air seal ENGi_C6_PNk ENGi_C6_SNk
LP disk ENGi_C7_PNk ENGi_C7_SNk
1st stage PT disk ENGi_C8_PNk ENGi_C8_SNk
2nd stage PT disk ENGi_C9_PNk ENGi_C9_SNk

LCF component P/N format is an ASCII string 3NNNNNN with N=0..9

LCF component S/N format is an ASCII string NNNNNN with N=0..9

5.2.2.17.3 Engine component usage

Accumulated total cycles of each LCF component are transmitted on ARINC label 062. They are copied by the
DMU software in following GSE parameters.
101-10002-851 Ind. I

- 26 -

Document Sagem DS - Reproduction et divulgation interdites

Data GSE parameter

i=1 or 2 (engine number)
LP impeller accumulated total cycles ENGi_C1_TCYC
HP impeller accumulated total cycles ENGi_C2_TCYC
HP turbine front cover accumulated total cycles ENGi_C3_TCYC
HP disk accumulated total cycles ENGi_C4_TCYC
HP turbine rear cover accumulated total cycles ENGi_C5_TCYC
Interstage air seal accumulated total cycles ENGi_C6_TCYC
LP disk accumulated total cycles ENGi_C7_TCYC
1st stage PT disk accumulated total cycles ENGi_C8_TCYC
2nd stage PT disk accumulated total cycles ENGi_C9_TCYC
Total accumulated number of starts ENGi_NSTARTS
Total accumulated number of flights ENGi_NFLIGHT

Accumulated total cycles are monitored for MCDU alert display, as described in §5.12.3.1.2.
5.2.2.17.4 Engine run time and flight time
Engine run time and flight time are transmitted on ARINC label 064. They are copied by the DMU software in
following GSE parameters.
Data GSE parameter
i=1 or 2 (engine number)
Total engine run time all engine models ENGi_TOT_RT
Total flight time all engine models ENGi_TOT_FH
Total engine run time as PW127M ENGi_127M_RT
Total flight time as PW127M ENGi_127M_FH
Total engine run time as PW127F ENGi_127F_RT
Total flight time as PW127F ENGi_127F_FH
Total engine run time as PW127E ENGi_127E_RT
Total flight time as PW127E ENGi_127E_FH
5.2.2.17.5 Engine component remaining life
LCF component remaining life is computed cyclically by the DMU software. It is the difference between the LCF
component life limit (available as GSE limit, see §6.2.5) and the LCF component accumulated total cycles, acquired
on label 062. It is monitored for MCDU alerts display (see §5.12.3.1.2).

Parameter name on GSE: ENGi_Cj_RL with i=1 or 2 (engine number) and j=1..9 (LCF component number).

5.2.3. Parameter display rule

As a general rule for parameter display:
• If a new update of a parameter has not been received since the last sampling, then the parameter is
marked as "Not transmitted" (XXX).
• If a parameter has been received with SSM indicating "Not Normal Operation", then the parameter is
marked with dashes (---).
5.3. ACMS REPORTS

5.3.1. generality
The basic principle is to acquire and store a comprehensive set of data related to a particular advisory/
monitoring event. This set of data is called ACMS reports.
The DMU processes the following reports:
Standard reports:
<02> Cruise
<03> Exceedance
101-10002-851 Ind. I

- 27 -

Document Sagem DS - Reproduction et divulgation interdites

<15> G-Meter
<16> Identification
<22> Flight CMC
<23> Gnd Test CMC
<24> Instant Flight CMC
<25> PW127M Engine Cycles
For standard reports everything is predefined by ATR specification (i.e.: standard header, data
processing, data collection, report format, trigger logics).
The definition of all the ACMS standard reports is given in section 5.3.2. This definition includes:
− trigger conditions and relevant flight mode,
− list of programmable limits and inhibit function,
− output data,
− Report printing format / layout,
− parameters index.
Programmable reports:
69 free programmable reports can be programmed on the GSE.
Those reports are completely free i.e. standard header, data collection, report format, data processing,
trigger logics.

5.3.1.1 Triggering conditions

A report may be triggered:
• as a result of the analysis of predefined conditions on aircraft parameters and DMU computed data,
• manually by the operator via the Remote Print Button (according to GSE programming),
• manually by the operator via MCDU functions,
• through GSE programmable start/stop logics.
The origin of report triggering is stored in the report itself (report code section).

5.3.1.1.1 Predefined conditions

For all standard trigger condition, rules described in section 5.2.1.3 for decision parameters use have to be
applied.
Particular cases where these rules are not to be applied are detailed in individual report definition section.
For details on all predefined conditions, refer to each report description.

5.3.1.1.2 Remote Print Button and Button Pushed Event

A Remote Print button or Button Pushed Event function causes generation of a specified report as a function
of flight phase.
A single report is triggered when the RPB or BPE is depressed. Before a further report can be triggered with
the RPB or BPE, the button must be released for at least 1 second.
The related triggered report and the information about incrementing or not the appropriate report counter are
programmable via GSE.
In this DMU version, only the report <16> in PRE-FLIGHT phase will be triggered from the RPB or BPE.
101-10002-851 Ind. I

- 28 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.1.1.3 MCDU functions

For details, refer to section 5.12.3.9.3.

5.3.1.1.4 ACARS uplink

For details, refer to section 5.13.3.3

5.3.1.1.5 Programmable trigger conditions

Independent from the predefined report trigger logics, GSE programmable trigger logics can be used to
trigger reports (see section 5.8).
At least 100 programmable events can be monitored by the DMU, each event triggering one specific report
(standard or programmable).
In this DMU version, no such additional trigger logic will be programmed on the GSE.

5.3.1.2 Pre-event history

A pre-event recording capability has to be provided by the DMU to cover the history data requirements of all
reports.

5.3.1.3 Reports storage

After generation, reports are stored in the DMU NVRAM (1 Mbyte of NVRAM is reserved for report storage).
The system provides storage capability on a first-in-first-out basis per type of reports. Each report
independently of the trigger condition is stored in the report storage memory. When a specific report area is
full, the oldest report is deleted and the new one takes its place. However, an option reprogrammable by the
GSE allows the automatic printing of this oldest report before its deletion if it hasn't been yet printed.
The number of stored report per report type is programmable on the GSE. A default storage configuration of
at least 10 reports stored per type of reports will be programmed.
Note: Overall storage capacity depends on the size of additional programmed reports. Average standard report
size is about 1 kbyte. Taking this size as a basis leads to an overall capacity of 1000 stored reports.
Independent from this storage in the DMU NVRAM, an option is provided to store all generated reports on
the PCMCIA card. Refer to section 5.16.5 for details on this function.

5.3.1.4 Report output rules

After generation and storage in NVRAM, ACMS reports may be:
• printed on the cockpit printer,
• automatically downloaded on a PCMCIA card, if inserted in the DMU,
• displayed (partially or totally) on a specific MCDU page
The report destination is free programmable by the GSE.
For each ACMS report it is possible to define on the GSE an individual destination for each type of trigger
condition (identified by the report trigger code).
The possible destinations are the following:
• STORAGE only : no automatic output is performed.
• PRINTER immediate : the report is printing as soon as the printer is ready to accept data.
• PRINTER at End of Flight : the report is printed at the End of Flight, i.e. after detection of flight mode 10
(Engine shut-down).
• ACARS Downlink immediate (not provided in this DMU version): As soon as the ACARS MU is ready to
accept data the report is downlinked.
Three possible destination code can be selected for ACARS :
101-10002-851 Ind. I

- 29 -

Document Sagem DS - Reproduction et divulgation interdites

• G "GROUND"
• V "VHF"
• S "SATCOM”
• H ”HF”.
In case of an ACARS destination programmed, if the DMU is not able to downlink a report before the end of
flight, then the report can be redirect to the PRINTER. If the printing attempt is successful, the report is then
deleted from ACARS queue.
This option is programmable by GSE.
The selections of PRINTER output and ACARS output for a given report are independent.
In any case, if a report can't be output to the programmed destination during the current leg, then new
attempts will be performed on the next legs, following the same rules.
When a report has been printed or downlinked via ACARS, a status is then recorded to indicate it. This
status can be displayed on the MCDU, by the function "Display Stored Reports".
This status must contain at least the following information:
• Report PRINTED/NOT PRINTED,
• Report IN ACARS : report downlinked, wait for ground acknowledge,
• Report DOWNLINKED and acknowledged.

5.3.1.5 Reports data formatting

As a general rule for reports, all displayed parameters are unfiltered.
Each non blank line of a report shall be identified by a data category uniquely composed of one letter and
one digit.
The identifier of the first line shall be “A1”.
Within a data category, the identification digit of the first line shall be “1”. The identification digit is
incremented by 1 at each new line. A line following a line identified by “9” shall be identified by “0” with the
same letter. The next line will have a letter incremented by 1, alphabetically speaking. For example if a line is
identified “A9” and the next line belongs to the same data category, this next line shall be identified “A0”, and
if the next belogns also to the same data category, it shall be identified “B1”.
Each data category shall be identified uniquely by one or several letters. The first letter identifying the first
data category shall be “A”. Then, the first letter identifying a category shall be alphabetically just after the last
identification letter of the previous category, e.g. if data category 3 lines are identified by “D1” to “E5”, data
category 4 first line shall be identified by letter “F1”.
If more than 26 letters are required in order to identify each data category of a report, an additional number
shall be used for that particular report (for example "A01"). The same rules as for 1-number identifiers shall
be observed, excepted that the number will go up to 99 before being reset to 00.
Moreover display rule as defined in section 5.2.3 has to be applied.

5.3.1.5.1 Data formatting for Printer

For identification purpose, to each data line a unique 2 digit alphanumeric code named data line identifier
can be assigned. Data line identifiers, if used, are defined individually for each report.

5.3.1.5.2 Data formatting for ACARS transmission

Below is only given the definition of the text message section of the ACARS downlink message. For details
about general ACARS downlink message structure (Control accountability header, Optional ground header
and Text message), refer to section 5.13.2.
101-10002-851 Ind. I

- 30 -

Document Sagem DS - Reproduction et divulgation interdites

Each report when requested to be downlinked via ACARS is formatted as defined afterwards, based on the
printer layout definition and applying the following rules:
• Each report will be associated to a specific IMI.
• Reports are transmitted as a multiblock message.
• Split from one block to another when maximum block size is reached.
• Only lines beginning with line identifiers in the print message are transmitted.
• Line identifiers are transmitted.
• Each data line will end with a "/".
• Every data will be separated by a coma ",".
• Every blank or dots character between data will be rejected.
• All characters except 0..9 or A..Z or "-","/","+" are transmitted as "."
In addition, a specific message structure is provided for the 1st block of a report message allowing to identify
the message content.
First block structure (after the header):

Character Contents Description

IMI
20 "A" Report message ident
21-22 "xx" Report number(01 to 99)
Message descriptor:
23 "/" Solidus
24 "A" Aircraft type
25 "T"
26 "R"
27 "4"
28 "2"
29 "5"
30 "0"
31 "0"

32 "x" Report number(01 to 99)

33 "x"

34 "," Comma
35 "1" Current downlink part
36 "," Comma
37 "1" Number of downlink part

38 "/" Solidus
39..N "dd.." report data

Note: Characters 35 and 37 are frozen to 1. These characters are reserved for future extension.
101-10002-851 Ind. I

- 31 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.1.6 Report limits

All limits used for reports trigger are defined in section 6.2 and are provided by the GSE.
The GSE can provide 24 sets of limits. Each set can be associated to a specific combination of A/C type and
engine type. The DMU must use the appropriate set of limit, according to A/C configuration.
Cross reference between A/C type - engine type and data set number is given by the GSE.
Only one set of limits independent from the A/C configuration will be programmed in the GSE database.
Initial settings of report limits is given in section 6.2.

5.3.1.7 Specific reports computed parameters

5.3.1.7.1 Report count

The DMU computes a counter allowing to identify the sequence of reports.
Parameter name on GSE : RCOUNT
Syntax :
RCOUNT = XXXYY
where
XXX = Report counter, incremented each time any report is generated, except if this generation
results of a MCDU manual request or of a RPB / BPE request.
YY = Number of the previous ACMS report (from 01 to 30)

5.3.1.7.2 Report code

For identification purpose of the condition that has triggered the report, a numeric code is associated to each
generated report. This code will be then displayed on the MCDU pages giving the list of generated reports.
Also this parameter may be stored in the report itself.
Parameter name on GSE: RCODE.

5.3.1.7.3 Trigger logic parameters

For each standard report, whose number is XXX (from 001 to 030), is assigned a specific logic parameter
named _LOGIC_XXX_ giving the state of trigger standard conditions of this report.
The value of _LOGIC_XXX is computed as follows:
- _LOGIC_XXX = 0 as a default.
- _LOGIC_XXX = Report code (1000,2000,4000,etc) as soon as the report is triggered by a standard
trigger condition.
- _LOGIC_XXX comes back to 0 when report generation and storage is finished.
These parameters are computed by the DMU for GSE programming capabilities.
101-10002-851 Ind. I

- 32 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2. Standard reports definition

5.3.2.1 Report <02>: Cruise

5.3.2.1.1 Triggering conditions

The Cruise Report <02> is generated by any one of the following trigger conditions:
1) Automatic generation at end of flight (code 4000)
This report is generated one time per flight during flight phase (6), if a list of parameters verify stability
conditions during 120 seconds. The following tables gives the list of parameters to be monitored, and their
associated stability conditions, which values are modifiable in the GSE (see §6.2.1) :

GENERAL PARAMETERS
Parameter Condition GSE parameter
INDICATED AIRSPEED (IAS) value > 80 Kts AIRSPEED
ALTITUDE (ALT) value > 6000 ft ALTITUDE
ALT variation variation in between -100 ft and +100 ft ALTITUDE
VRTG variation variation in between -0.2 g and 0.2 g GVER
(accélération verticale)
IAS variation variation in between - 5 Kts and + 5 Kts AIRSPEED

ENGINE PARAMETERS (one per engine)

Parameter Condition GSE parameter
NH variation (High Pressure Gaz Variation in between -0.5% and +0.5% NH_L / NH_R
Speed)
Torque variation Variation in between -1% and +1% TORQUE_L / TORQUE_R
NP variation (Propeller speed) Variation in between -0.5% and + 0.5% NP_L / NP_R

2) MCDU manual request (code 1000)

3) ACARS MU immediate request (code 8100)

101-10002-851 Ind. I

- 33 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.1.2 Printing format

111111111122222222233333333334
1234567890123456789012345678901234567890
1 A1 ATRXX PWXXXX REPORT02
2
3
4 B1 RT RC RV MODE AC
5 B2 #ENG SCR A X XXX
6
7 C1 FLT DATE GMT TYP
8 C2 XXXX DDMMYY HHMM XX
9
10 D1 ENGINE S/N
11 D2 ESN1 aaaaaa
12 D3 ESN2 aaaaaa
13
14
15 E1 IAS ALT TAT
16 E2 XXX PXXXXX PXXX
17
18
19 F1 TORQ NP NL
20 F2 XXX.X XXX.X XXX.X
21 F3 XXX.X XXX.X XXX.X
22
23 G1 NH ITT FF IG
24 G2 XXX.X XXXX.X XXX XXX
25 G3 XXX.X XXXX.X XXX XXX
26
27 H1 HPL HPR N/H ACL ACR
28 H2 X X X X X
29
30 I1 WGT
31 I2 XX.XX
32
33
34 *** EOT ***
35
36

List of parameters displayed on the report :

Name on report Comment Range/Unit/Definition GSE parameter

ATRXX Aircraft type XX = 42 or 72 ACNAMEC01_02 à
ACNAMEC07_08(1)
PWXXXX Engine Type XXXX = 120, 121, 121A, 127E, ENGTYPE(2)
124, 127, 127F
RT Report type string "#ENG" N/A
RC 3 characters code for string "SCR" RC_R02
exceedance report
RV Report version string "A" N/A
MODE Flight mode 1 = GROUND, 2 = FLIGHT AIR_GROUND_R
AC Aircraft ident 0 to 255 ACTYPE
101-10002-851 Ind. I

- 34 -

Document Sagem DS - Reproduction et divulgation interdites

Name on report Comment Range/Unit/Definition GSE parameter

FLT Flight number 0 to 9999 FLINUM
DATE date DAY – MONTH – YEAR DAY, MONTH_NUM, YEAR.
GMT GMT (Time) HOURS – MINUTES UTC
TYP Engine type 0 to 15 ENGTYPE
IAS Airspeed 0 to 512 knots AIRSPEED
ALT Altitude - 65536 to 65536 feet ALTITUDE
TAT Total air temperature - 99.15 to 98.85 °C TAT
TORQ Torque (Thrust) left 0 to 204% TORQUE_L
(AVERAGED) Torque (Thrust) right TORQUE_R
NP Propeller speed left 0 to 204% NP_L
(AVERAGED) Propeller speed right NP_R
NL Low pressure gaz speed LH 0 to 110% NL_L
(AVERAGED) Low pressure gaz speed RH 0 to 110% NL_R
NH High pressure gaz speed LH 0 to 110% or NH_L
(AVERAGED) High pressure gaz speed 0 to 256% NH_R
RH
ITT Interturbine temp LH 0 to 1200 °C ITT_L
(AVERAGED) Interturbine temp RH 0 to 1200 °C ITT_R
FF Fuel flow left 0 to 700 kg/h FF_L
(AVERAGED) Fuel flow right 0 to 700 kg/h FF_R
IG Generator current LH 0 to 800 A CD_L
(AVERAGED) Generator current RH 0 to 800 A CD_R
HPL HP Valve left 0 = OPEN, 1 = CLOSED HP_VALVE_L
HPR HP Valve right 0 = OPEN, 1 = CLOSED HP_VALVE_R
N/H Normal/high flow control 0 = HIGH, 1 = NORMAL HIGH_FLOW_CT
ACL Pack air flow left 0 = ON, 1 = OFF PACK_AIR_L
ACR Pack air flow right 0 = ON, 1 = OFF PACK_AIR_R
ESN1 Engine S/N 1 « aaaaaa » with 'a' being an ESN_1_1 (4 char)
alphanumeric symbol ESN_1_2 (2 char MSB)
ESN2 Engine S/N 2 « aaaaaa » with 'a' being an ESN_2_1 (4 char)
alphanumeric symbol ESN_2_2 (2 char MSB)
WGT Instant weight 0 to 32.76 tons APMWEIGHT_T
Character ‘4’ or ‘7’ is always located in ACNAMEC03_04 as the second character of this parameter.
(1)

(2)
ENGTYPE must be converted prior to display following, see §5.2.2.4 for conversion rule.

Note : Parameters marked as "AVERAGED" are averaged for the last 60 seconds, including for manual
requests by MCDU (code 1000), ACARS (8100).
101-10002-851 Ind. I

- 35 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.1.3 Destination peripherals

CRUISE report automatically generated during flight (code 4000) is automatically sent by ACARS.
All CRUISE reports are stored in NVRAM and on PCMCIA disk if it is available.

5.3.2.1.4 ECTM recording

The aim of ECTM recording is to store cruise report data in a format compliant with Web ECTM analysis
software. The MPC stores in ECTM format one report per time interval. A GSE limit given in hours allows to
modify this interval.
When a cruise report code 4000 is generated, it is stored in ECTM format if the following conditions are met :
- no cruise report is stored in ECTM format in the same time interval,
- or if a cruise report is already stored in ECTM format, the quality of the new report is better than the
previous stored report quality.
The quality of report cruise is deducted from the state of that discrete parameters :
Bleed status mask Logical state Default state GSE
0 1 x
HP valve (left and Open Close Don’t Close HP_VALVE_L
right) care HP_VALVE_R
Pack air flow (left On Off Don't On PACK_AIR_L
and right) care PACK_AIR_R
Flow control High Normal Don't Normal HIGH_FLOW_CT
care

"Don't care" means than the discrete state can be ignored.

The quality of a cruise report is the total number of discrete which value is the default state. (0..5)
The default state of each discrete is configurable with the MCDU (see 5.12.3.12.1.1).
A report cruise is decomposed in two ECTM recordings (one per engine).
An ECTM recording is a list of parameters, recorded in one line of text file.
That list is given in APPENDIX 6.7.
ECTM files are stored in PCMCIA disk as explained in chapter 5.16.5.2.

Note : ECTM recording is not made in case of manual request by MCDU (code 1000) or ACARS (code
8100).

5.3.2.2 Report <03>: Exceedance

5.3.2.2.1 Triggering conditions

1) Automatic generation when a parameters is exceeding (code 40XX)

This report is triggered if some engine parameter values exceed predefined thresholds.
For each engine, parameters monitoring starts as soon as the conditions on fuel flow is verified :
Parameter Premonitoring condition Action if condition is TRUE GSE
101-10002-851 Ind. I

- 36 -

Document Sagem DS - Reproduction et divulgation interdites

FUEL FLOW LEFT > 10 Kg/h Monitoring of left engine starts FF_L
FUEL FLOW RIGHT > 10 Kg/h Monitoring of right engine starts FF_R

The table in §6.2.2 gives the list of monitored engine parameters and their associated thresholds (T1, T2,
T3), which depend on motorization. All thresholds are modifiable with the GSE (see §6.2.2).
Thresholds used for ITT exceedance detection are selected according to airspeed value being below or
above 80 Kts (value modifiable with the GSE).

A report generation starts as soon as one parameter exceeds the T1 value during at least 3 seconds (delay
modifiable with GSE). If so, the DMU samples immediately all engine parameters to be displayed on the
report, and monitors the evolution of the parameter in exceedance, so as to compute exceedance
characteristics to be displayed on the report :
- the time t1 of exceedance of T1 threshold
- the time t2 of exceedance of T2 threshold
- the time t3 of exceedance of T3 threshold
- the time t4 representing the interval between the beginning of exceedance and the peak value.
The report is generated when the exceedance is over or when 6 minutes are elapsed since the beginning of
the exceedance (delay modifiable with GSE).

When several parameters are in exceedance at the same time, one report per parameter in exceedance
shall be generated.
The number of exceedance reports is limited to 40 reports per flight and is modifiable with GSE.

The report code depends on the parameter which is exceeding :

Report code EXCEEDANCE PARAMETER
4001 TORQUE LEFT
4002 TORQUE RIGHT
4011 NP LEFT
4012 NP RIGHT
4021 NH LEFT
4022 NH RIGHT
4031 ITT LEFT
4032 ITT RIGHT

2) MCDU manual request (code 1000)

3) ACARS MU immediate request (code 8100)

101-10002-851 Ind. I

- 37 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.2.2 Printing format

111111111122222222233333333334
1234567890123456789012345678901234567890
1 A1 ATRXX PWXXXX REPORT03
2
3
4 B1 RT RC RV MODE AC
5 B2 #EXC BBB A X XXX
6
7 C1 FLT DATE GMT TYP
8 C2 XXXX DDMMYY HHMM XX
9
10 D1 ENGINE S/N
11 D2 ESN1 aaaaaa
12 D3 ESN2 aaaaaa
13
14
15 E1 IAS ALT TAT
16 E2 XXX PXXXXX PXXX
17
18
19 F1 TORQ NP NL
20 F2 XXX.X XXX.X XXX.X
21 F3 XXX.X XXX.X XXX.X
22
23 G1 NH ITT FF IG
24 G2 XXX.X XXXX.X XXX XXX
25 G3 XXX.X XXXX.X XXX XXX
26
27 H1 HPL HPR N/H ACL ACR
28 H2 X X X X X
29
30
31 I1 MAXI: XXXX.X
32 I2 MTOL XXXX
33
34 J1 THRESHOLD TOL
35 J2 1: XXXX.X XXXX
36 J3 2: XXXX.X XXXX
37 J4 3: XXXX.X XXXX
38
39
40 *** EOT ***
41
42

List of parameters displayed on the report :

Name on report Comment Range/Unit/Definition GSE parameter
ATRXX Aircraft type XX = 42 or 72 ACNAMEC01_02 à
ACNAMEC07_08
PWXXXX Engine Type XXXX = 120, 121, 121A, 127E, ENGTYPE
124, 127, 127F
RT Report type string "#EXC" N/A
101-10002-851 Ind. I

- 38 -

Document Sagem DS - Reproduction et divulgation interdites

Name on report Comment Range/Unit/Definition GSE parameter

RC 3 characters string "BBB" See below RC_R03
depending on the parameter
in exceedance
RV Report version string "A" N/A
MODE Flight mode 1 = GROUND, 2 = FLIGHT AIR_GROUND_R
AC Aircraft ident 0 to 255 ACTYPE
FLT Flight number 0 to 9999 FLINUM
DATE date DAY – MONTH – YEAR MONTH, DAY, YEAR.
GMT GMT (Time) HOURS – MINUTES UTC
TYP Engine type 0 to 15 ENGTYPE
IAS Airspeed range 0 to 512 knots AIRSPEED
ALT Altitude range - 65536 to 65536 feet ALTITUDE
TAT Total air temperature - 99.15 to 98.85 °C TAT
ou -50 to 90°C
TORQ Torque (Thrust) left 0 to 204% TORQUE_L
Torque (Thrust) right TORQUE_R
NP Propeller speed left 0 to 204% NP_L
Propeller speed right NP_R
NL Low pressure gaz speed LH 0 to 110% NL_L
Low pressure gaz speed RH 0 to 110% NL_R
NH High pressure gaz speed LH 0 to 110% ou NH_L
High pressure gaz speed 0 to 256% NH_R
RH
ITT Interturbine temp LH 0 to 1200 °C ITT_L
Interturbine temp RH 0 to 1200 °C ITT_R
FF Fuel flow left 0 to 700 kg/h FF_L
Fuel flow right 0 to 700 kg/h FF_R
IG Generator current LH 0 to 800 A CD_L
Generator current RH 0 to 800 A CD_R
HPL HP Valve left 0 = OPEN, 1 = CLOSED HP_VALVE_L
HPR HP Valve right 0 = OPEN, 1 = CLOSED HP_VALVE_R
N/H Normal/high flow control 0 = HIGH, 1 = NORMAL HIGH_FLOW_CT
ACL Pack air flow left 0 = ON, 1 = OFF PACK_AIR_L
ACR Pack air flow right 0 = ON, 1 = OFF PACK_AIR_R
MAXI Maximum reached by the unit depending on the parameter MAXI_R03
parameter that cause the
report
MTOL Time to maximum over limit seconds MTOL_R03
(T4).
101-10002-851 Ind. I

- 39 -

Document Sagem DS - Reproduction et divulgation interdites

Name on report Comment Range/Unit/Definition GSE parameter

THRESHOLD1 Level of the first threshold unit depending on the parameter THRESHO1_R03
(T1)
THRESHOLD2 Level of the second unit depending on the parameter THRESHO2_R03
threshold (T2)
THRESHOLD3 Level of the third threshold unit depending on the parameter THRESHO3_R03
(T3)
TOL1 Time over limit in the first seconds TOL1_R03
threshold (t1)
TOL2 Time over limit in the second seconds TOL2_R03
threshold (t2)
TOL3 Time over limit in the third seconds TOL3_R03
threshold (t3)
ESN1 Engine S/N 1 « aaaaaa » avec a un caractère ESN_1_1 (4 char)
alphanumérique. ESN_1_2 (2 char MSB)
ESN2 Engine S/N 2 « aaaaaa » avec a un caractère ESN_2_1 (4 char)
alphanumérique. ESN_2_2 (2 char MSB)

Note: All values but MAXI, MTOL, TOL1, TOL2, TOL3 are sampled at the beginning of the exceedance, after
the 3 seconds confirmation delay.

Definition of "RC" field depending on exceedance parameter :

Value of string "BBB" Exceedance parameter

1TQ TORQUE LEFT
2TQ TORQUE RIGHT
1NP NP LEFT
2NP NP RIGHT
1NH NH LEFT
2NH NH RIGHT
1TT ITT LEFT
2TT ITT RIGHT

Note: for reports manually generated (codes 1000, 2000, 8100), MAXI, MTOL, THRESHOLD1,
THRESHOLD2, THRESHOLD3, TOL1, TOL2, TOL3, and RC parameters are set to invalid.

5.3.2.2.3 Inhibit function

The report code 4000 is inhibited if the maximum number of reports per flight is set to zero with the GSE.
Other report codes are not inhibited.

5.3.2.2.4 Destination peripherals

Exceedance reports <03> are stored in NVRAM and on PCMCIA disk if it is available and transmitted by
ACARS.
101-10002-851 Ind. I

- 40 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.3 Report <15>: G-Meter

Relevant Flight modes: 4 to 10.

5.3.2.3.1 Computations
1-Maximum vertical accelerations:
The following maximum vertical acceleration values shall be detected and memorised by the DMU during
each flight:
• During the “flight” phase (4 to 7), the maximum and minimum accelerations; during flight phase 4, these
accelerations will be managed only from the moment the “all gear squat switch” discrete is in the air state
(this discrete is supposed to pass from ground to air state earlier than “main gear squat switch” discrete).
• During the “landing” phase (7 to 9), the maximum acceleration.
Also the various GMT values corresponding to maximum/minimum accelerations detection will be
memorized.
The moment to change from flight to ground phase will be 10 seconds prior flight mode changes from 7 to 8.
Once flight mode 8 has been entered:
• if the “main gear squat switch” parameter changes back from “Ground” to “Air” for less than 10 seconds,
even if the flight mode comes back to 5, the maximum acceleration detected during this period shall be
considered as a landing one.
• if the “main gear squat switch” parameter changes back from “Ground” to “Air” for more than 10 seconds,
it shall be considered that the aircraft goes back in flight due to a “Go-Around” and the new maximum
vertical acceleration values up and down (if any) shall be considered as flight ones.
Note: all gear squat switch and main gear squat switch are replaced by AIR/GROUND discrete in V0
configuration. In every cases, a logical one (grounded) means “Ground”, a logical zero (open) means “Air”.
2-Accelerometers validity test:
When the flight phase becomes 10 or 1, the DMU shall check the validity of the accelerometer in the 3 axis.
The average values shall be computed on the 3 acceleration parameters during 2 seconds:
• Vertical acceleration, result valid if value = 1±0.2g
• Lateral acceleration, result valid if value = 0±0.2g
• Longitudinal acceleration, result valid if value = 0±0.2g
If the flight phase has undergone a 4-to-5 transition since the previous report automatic generation, results
shall be presented in the G-Meter report when the flight phase becomes 10 or 1 again..
In case Vertical acceleration is invalid, all previously computed values of this parameter that appear in the
report shall be invalidated.

5.3.2.3.2 Trigger Conditions

The G-Meter Report is generated by any one of the following trigger conditions:
1) When flight phase becomes 10, if a flight phase transition 4-to-5 occurred since the previous
automatic report generation.
OR
When flight phase becomes 01, if a flight phase transitions 4-to-5 and (4 or 3 or 2)-to-1 occurred
since the previous automatic report generation.
101-10002-851 Ind. I

- 41 -

Document Sagem DS - Reproduction et divulgation interdites

If any of these conditions is verified, report is generated as soon as the accelerometers validity test
has been performed.
Code: 4000.
2) MCDU manual request
Code: 1000.
3) ACARS request (code 8100)
In case of MCDU immediate request, all data will be snapshots values at the trigger time.

5.3.2.3.3 Inhibit Function

There is no inhibit function for the G-meter report.
5.3.2.3.4 Destination
- Storage in the NVRAM
- Display with MCDU using:
• The G-Meter Menu (see 5.12.3.11 ) accessible from the ACMS main page. This menu will allow an
operator to accede to the contents of the last generated report.
• The common Stored Reports menu (see 5.12.3.9.2).
- Automatic downlink by ACARS

5.3.2.3.5 Printing format

Printing Format 111111111122222222233333333334

1234567890123456789012345678901234567890
1 A1 G-METER REPORT
2
3 B1 DATE GMT FLT
4 B2 13JUL 1821 0001
5
6 C1 GMT ACC
7 C2 1755 -0.08 FLT
8 C3 1740 +1.52 FLT
9 C4 1807 +1.12 GND
10 D1 VERT ACC : VALID
11 E1 LONG ACC : VALID
12 F1 LAT ACC : INVALID

With:
Line 4: Date, GMT: raw data taken when the report is generated
Flight Number: raw data taken during take-off (when flight mode equals to 4)
Line 7: GMT, Minimum “in flight” vertical acceleration, Flight Mode (FLT): raw parameters computed at the
moment the minimum acceleration is detected. This information will be displayed only if the result of the
validity test performed on the vertical acceleration is valid, otherwise dashes will be displayed.
Line 8: GMT, Maximum “in flight” vertical acceleration, Flight Mode (FLT): raw parameters computed at the
moment the maximum acceleration is detected. This information will be displayed only if the result of the
validity test performed on the vertical acceleration is valid, otherwise dashes will be displayed.
Line 9: GMT, Maximum “landing” vertical acceleration, Flight Mode (GND): raw parameters computed at the
moment the maximum acceleration is detected. This information will be displayed only if the result of the
validity test performed on the vertical acceleration is valid, otherwise dashes will be displayed.
101-10002-851 Ind. I

- 42 -

Document Sagem DS - Reproduction et divulgation interdites

Line 10: Result (VALID or INVALID) of the validity test performed on the vertical acceleration.
Line 11: Result (VALID or INVALID) of the validity test performed on the longitudinal acceleration.
Line 12: Result (VALID or INVALID) of the validity test performed on the lateral acceleration.

5.3.2.4 Report <16>: Ident

This report is used to display the various MPC identifications and to indicate the A/C configuration
recognised by the MPC. It also indicates the current status of each software component of the MPC based
on the maintenance words.

5.3.2.4.1 Report information description

This report stores the following information (the line identifiers on report output is given for each information) :
MPC global status (B1 to C7):
• AFDAMU (MPC) part number.
• AFDAU load S/W part number.
• DMU load S/W part number.
• DMU D/B version number.
• AFDAU STATUS (OK/KO/NO AFDAU).
• DMU STATUS (OK/KO).
• Date of the generation of the report.
General A/C configuration information :
• Configuration of the flight data recording system (some examples listed below) (D2):
ATR V0 : V0 standard dataframe

• Aircraft type (some examples listed below) (D3):

ATR42300 : ATR 42-300 (PW120 engine)
ATR42320 : ATR 42-320 (PW121 engine)
ATR72500 : ATR 72-500 (PW127F engine)
• Additional A/C configuration information that is useful to determine the calibration law of some input
parameters of the MPC (depending on the FDRS configuration) (D4 to D6):
V0 dataframe:
V0-CAA : FDAU P/N 36045171E20 or 36045171E21(blank if other FDAU P/N)
FDAU 36045171E21 : FDAU P/N 36045171E21 (ATR 42 aircrafts)
FDAU 36045171E20 : FDAU P/N 36045171E20 (ATR 42 aircrafts)
FDAU 36045171E01/2A01 : FDAU P/N 36045171E01 or 36045172A01 (ATR 42 aircrafts)
FDAU 36045171E00/2A00 : FDAU P/N 36045171E00 or 36045172A00 (ATR 42 aircrafts)
FDAU 36045182A** : FDAU P/N 36045182Ann, with nn=00,01,12,etc (ATR 72 aircrafts)
V2 dataframe:
ED34A110 : FDAU P/N ED34A110
ED34A3** : FDAU P/N ED34A310 or ED34A320
V2/V2A dataframes:
101-10002-851 Ind. I

- 43 -

Document Sagem DS - Reproduction et divulgation interdites

AFCS dw : AFCS with mod dw

(blank if AFCS without dw)
Detailed operational AFDAU software description :
• The AFDAU operational software low level identifications. As the operational software is made of
different sets of data/software, each of them having its own software identification, the reference of each
of these sets will be displayed. (Maximum 10 sets possible, E1 to F1).
• The AFDAU operational software CRC (G1, G2).
• The AFDAU selected database CRC (H1, H2).
• The AFDAU host software part number (K1, K2).
• The AFDAU host software CRC (L1, L2).
• The AFDAU software bite word part 1. (Used to calculate the AFDAU status) (O1).
• The AFDAU software bite word part 2 (O2).
• The AFDAU software maintenance words (P1 to P0).
Detailed DMU software description :
• The DMU operational software low level identifications (I1, I2).
• The DMU operational software CRC (J1, J2).
• The DMU host software part number (M1, M2).
• The DMU host software CRC (N1, N2).
• The DMU software bite word. (Used to calculate the DMU status). (R1, R2)
• The DMU software maintenance words (S1 to S6).

5.3.2.4.2 Trigger Conditions

The Identification (Ident) report is generated by any one of the following trigger conditions:
1) MCDU manual request (code 1000)

2) ACARS manual request (code 8100).

3) RPB or BPE (code 2000).

This generation upon RPB / BPE can only be activated during pre-flight phase (Phase 1) according to GSE
programmation .
4) DTB (new database) event (code 1001)

5.3.2.4.3 inhibit function

There is no inhibit function for the Identification report.
101-10002-851 Ind. I

- 44 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.4.4 Report output

The destination of the Identification report are the following :
• MCDU Display
• Printer
• ACARS

Printing Format :

111111111122222222233333333334 Comment
1234567890123456789012345678901234567890
1 A1 IDENTIFICATION REPORT
2
3 B1 MPC & A/C IDENT
4 B2 AFDAMU ED35E109-01-03 AFDAMU ED35 version
5 B3 AFDAU S/W L036310102 AFDAU software version
6 B4 DMU S/W L036370110 DMU software version
7 B5 DMU D/B 5112V0096 DMU database version
8
9 B6 AFDAU STATUS OK STATUS OK if AFDAU bite word 1 = 0
10 B7 DMU STATUS KO STATUS OK if DMU bite word = 0
11
12 C1 REPORT INFORMATION
13 C2 DATE GMT FLT
14 C3 13JUL 1821 0001 Date of generation of the report.
15
16 D1 A/C INFORMATION
17
18 D2 V2 AFDAU type of frame used
19 D3 ATR72500 Plane selected
20 D4
21 D5
22 D6
23
24 E1 AFDAU OP S/W DETAIL
25 E2 SOFT L036210500 AFDAU software configuration
26 E3 V2B L036210500 Used for each dataframe
27 E4 V0V1V2 L036210500
28 E5 V3 L036210500
29 E6 V2A L036210500
30 E7
31 E8
32 E9
33 E0
34 F1
35
36 G1 AFDAU OP S/W CRC
37 G2 SOFT 0B4F
38
39 H1 AFDAU SELECTED D/B CRC
40 H2 D/B 0B4F
41
42 I1 DMU OP S/W DETAIL
43 I2 SOFT L036380114
44
101-10002-851 Ind. I

- 45 -

Document Sagem DS - Reproduction et divulgation interdites

111111111122222222233333333334 Comment
1234567890123456789012345678901234567890
45 J1 DMU OP S/W CRC
46 J2 SOFT BB25123F
47
48 K1 AFDAU HOST S/W DETAIL AFDAU host software used
49 K2 SOFT: L012345678
50
51 L1 AFDAU HOST S/W CRC
52 L2 SOFT: 1234ABCD
53
54 M1 DMU HOST S/W DETAIL DMU host software used
55 M2 SOFT: L012345678
56
57 N1 DMU HOST S/W CRC
58 N2 SOFT: 1234BCDE
59
60 O1 AFDAU BITE WORDS Compilation of all AFDAU
61 Maintenance words
62 O2 PART 1: 0012FFBA Used for OK/KO AFDAU status
63 O3 PART 2: 0000001F
64
65 P1 AFDAU MAINT. WORDS AFDAU maintenance word
66
67 P2 MWANAL: 00000000 Analogs input maintenance word
68 P3 MWRCDR: 00000001 Recorder word
69 P4 MWDIS: 00000001 Discrete word
70 P5 MWA429INT: 00012345 ARINC429 input interface
71 P6 MWA429PORT: 0012FFFF ARINC429 input ports
72 P7 MWCSDBASCB: FEDCBA98 ASCB buses
73 P8 MWSERINT: 0012FFCA Serial interface
74 P9 MWLOAD: 00000AAA Loadable memory maintenance word
75 P0 MWMPC: 000ABCDE MPC special functions
76
77 R1 DMU BITE WORD
78
79 R2 BITE: 0001FFFF Used to calculate OK/KO DMU status
80
81 S1 DMU MAINT. WORDS Compilation of all DMU maintenance
82 words
83 S2 MW-CPU: 001234A6 Cpu maintenance word
84 S3 MW-GEN: 0012BCA6 General maintenance word
85 S4 MW-PCMCIA: 00123D56 PCMCIA interface
86 S5 STIFDMU: 00123456 Data input interface
87 S6 STEFDMU: 001234AB Data output interface
88
89
90
101-10002-851 Ind. I

- 46 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.5 Report <22>: Flight CMC

The Flight CMC report is generated at the end of each flight and shows all the fault data detected during the
flight in MFC ARINC429 maintenance words.

5.3.2.5.1 Trigger condition

End of flight (code 4000)

The Flight CMC Report is generated if following conditions are matched :
• flight phase transition from 8 to 9 is detected
• events were detected during flight phases from 3 to 8 (Master Caution or Master Warning discrete were
activated)
Note : The report generation with manual request by MCDU, ACARS or RPB / BPE is not possible.

5.3.2.5.2 Report generation

Once the report triggered, the DMU software :

• Reads all the previously stored fault data coming from MFC ARINC429 maintenance words.
• Associate all event fault codes stored to an explanation sentence, according to the fault code database.
4 databases are possible depending on the type of MFC equipment (Sx, L2x, L5x and L53). The
detection of MFC database is described in the document [A04] §3.3.2.
• Composes the report <22> with all the fault data of all events found in the previous steps.
• Generates the report <22>.
• Erases all the fault data stored to free space for the next flight.

5.3.2.5.3 Report format

Printing Format 111111111122222222233333333334

1234567890123456789012345678901234567890
1 A1 FLIGHT CMC REPORT
2
3 B1 DATE GMT FLT
4 B2 AUG10 1228 0001
5 C1 FLIGHT CMC DATA :
6 C2 10:15:00 MW
7 C3 10:15:00 ELEC SMK
8 C4 ELEC SMK DETECTED
9 C5 CHK 1UA1(2)/PIN AC-
10 C6 06B AND 1WA/PIN A-D
11 C7 CHK WIRE BTW PINS
12 ...

With:
• Line 3 and 4: Date, GMT time and flight number of the generation of the report,
101-10002-851 Ind. I

- 47 -

Document Sagem DS - Reproduction et divulgation interdites

• Line 5: beginning of the flight fault data.

• Line 6: Line to declare the event (master warning or master caution activation).
• Line 7 to 11: Faultsand associated explanation sentences belonging to the event declared in line 6.
Line 6 to 11 are repeated for each event and each fault detected during the flight before the generation of the
report. A maximum of 10 events can be stored in report <22>, each event holding a maximum of 10 faults.

5.3.2.5.4 Report output

Once generated the report is stored in NVRAM and in the PCMCIA card if any.
It can be displayed by two ways :
• the MCDU Stored Reports menu (see 5.12.3.9.2)
• the MCDU CMC -> Last Flight Report menu (see 5.12.3.13.1)

5.3.2.5.5 GSE limits

There is no GSE limit for report <22>.

5.3.2.6 Report <23>: GND Test CMC

The GND Test CMC Report is destined to ground maintenance.

The operator plugs an MFC on the MPC and requests the generation of a report <23> with the MCDU page
CMC -> GND TEST REPORT (see 5.12.3.13.2)
Then the DMU monitors Master Caution and Master Warning discretes to detect an event. When an event is
detected (one of these discrete is activated), associated faults present in MFC maintenance words are
gathered by the DMU and the report is generated.

5.3.2.6.1 Trigger condition

Generation upon operator request on ground (code 4000)

The GND Test CMC Report generation algorithm is the following :
The aircraft is on ground (flight phase 1,2,9 or 10)
The report generation has been requested by an operator with the MCDU CMC -> GND TEST
REPORT menu (see § 5.12.3.13.2).
Once the report generation being requested, the DMU software waits for an event (Master Caution
or Master Warning shunt discrete activation).
While the event is present (i.e. while alarm discrete is activated), the DMU acquires fault data on the
ARINC 429 maintenance words (a maximum of 15 faults are taken into account)
• When the event is over, it associates all fault codes stored to an explanation sentence, according to the
fault code database. (4 databases are possible : Sx, L2x, L5x and L53). Detection of the database is
described in the document [A04] §3.3.2.
• Then it composes the report <23> with all the fault data and text belonging to the event
• The report <23> is then generated with the code 4000 and displayed in the CMC -> GND TEST
REPORT menu (see § 5.12.3.13.2). It can be displayed also by MCDU Stored Reports menu (see
5.12.3.9.2)
• All the fault data stored are erased.
101-10002-851 Ind. I

- 48 -

Document Sagem DS - Reproduction et divulgation interdites

Notes :
- If the operator exits from the CMC -> GND TEST REPORT menu before an alarm is detected, the report
generation is cancelled.
- The report generation with manual request MCDU, ACARS or RPB is not possible.

5.3.2.6.2 Report format

Printing Format 111111111122222222233333333334

1234567890123456789012345678901234567890
1 A1 GND TEST CMC REPORT

2 B1 DATE GMT FLT

3 B2 AUG10 1545 0001
4 C1 GND TEST CMC DATA :
5 C2 10:15:00 MC
6 C3 10:15:00 AIR
7 C4 CAB PRESSURIZATION FLT
8 C5 CHK 1UA1(2)/PIN AC-01F
9 ...

The report <23> format is similar to the report <22> format except :
the text in line 4 being "GND TEST CMD DATA :",
and the lines 5-9 are repeated for each warning detected since the report generation request.

5.3.2.6.3 Report output

Once generated the report is stored in NVRAM and in the PCMCIA card if any.

5.3.2.7 Report <24>: Instant Flight CMC

The instant flight CMC report <24> is downlinked automatically by ACARS during the flight, as soon as an
alarm is detected.

5.3.2.7.1 Trigger conditions :

When an alarm is detected during the flight (code 4000)
The instant flight CMC report <24> is triggered if all the following conditions are matched :
Flight phase is from 3 to 8
An event (Master Caution or a Master Warning activation) is raised and some faults have been
recorded
A recall event was not detected during the two last seconds before the event. Detection of recall
event is described in document [A04] chapter §3.1.4.
Note : The report generation with manual request MCDU, ACARS or RPB is not possible.
101-10002-851 Ind. I

- 49 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.7.2 Report generation

The report is generated when the first of the following events occurs :
- a 5 minutes delay (modifiable with the GSE, see §6.2.4) is elapsed since the end of the event
(deactivation of master alarm) . If a new event appears before the delay is over, all faults belonging to
the new event must be added to the report. Thus, the report <24> holds at maximum 10 events, each
event holding at maximum 10 faults.
- a flight phase transition from 8 to 9 is detected (aircraft is landing).

5.3.2.7.3 Report format

The format is the same than the one of report <22>.

5.3.2.7.4 Report output

The report is stored in NVRAM, in PCMCIA disk (if any) and immediately downlinked by ACARS.

5.3.2.8 Report <25>: PW127M Engine Cycles

The PW127M Engine Cycles report <25> displays life cycles of PW127M engine components.
It is generated either manually by an MCDU request, or automatically in flight phase 2 every 5 flights.

5.3.2.8.1 Trigger conditions :

The PW127M Engine Cycles report is generated by any one of the following trigger conditions:
1) MCDU manual request (code 1000)
2) Automatically every 5 flights in flight phase 2 (code 4000)
The report is triggered automatically every 5 flights (this period is modifiable with the GSE, see §6.2.4),
during flight phase 2, if 3 complete data streams have been received on label 062 and 064, on at least one
EEC bus.

5.3.2.8.2 Report generation

Once the report triggered, the DMU software :
• Composes the report <25> with all engine component life parameters.
• Generates the report <25>.
101-10002-851 Ind. I

- 50 -

Document Sagem DS - Reproduction et divulgation interdites

5.3.2.8.3 Report format

Printing Format 111111111122222222233333333334
1234567890123456789012345678901234567890
1 A1 ATRXX REPORT25
2
3 B1 DATE GMT
4 B2 DDMMYY HHMM
5
6 C1 TOTAL LIFE COUNT
7 C2 ENGINE 1 S/N
8 C3 ESN1 AB1234
9 C4 LP IMPELLER XXXXX
10 C5 HP IMPELLER XXXXX
11 C6 HP FRONT COVER XXXXX
12 C7 HP DISK XXXXX
13 C8 HP REAR COVER XXXXX
14 C9 AIR SEAL XXXXX
15 D0 LP DISK XXXXX
16 D1 1ST PT DISK XXXXX
17 D2 2ND PT DISK XXXXX
18
19 E1 TOTAL LIFE COUNT
20 E2 ENGINE 2 S/N
21 E3 ESN2 AB1234
22 E4 LP IMPELLER XXXXX
23 E5 HP IMPELLER XXXXX
24 E6 HP FRONT COVER XXXXX
25 E7 HP DISK XXXXX
26 E8 HP REAR COVER XXXXX
27 E9 AIR SEAL XXXXX
28 F0 LP DISK XXXXX
29 F1 1ST PT DISK XXXXX
30 F2 2ND PT DISK XXXXX
31
32 H1 REMAINING LIFE
33 H2 ESN1 ESN2
34 H3 AB1234 AB1234
35 H4 XXXXX LP IMP XXXXX
36 H5 XXXXX HP IMP XXXXX
37 H6 XXXXX HP FRONT XXXXX
38 H7 XXXXX HP DISK XXXXX
39 H8 XXXXX HP REAR XXXXX
40 H9 XXXXX AIR SEAL XXXXX
41 I0 XXXXX LP DISK XXXXX
42 I1 XXXXX 1ST PT XXXXX
43 I2 XXXXX 2ND PT XXXXX
44
45 ENGINE 1 ID
46 ENGINE S/N AB1234
47 TM S/N AB1234
48 RGB S/N AB1234
49
50 ENGINE 2 ID
51 ENGINE S/N AB1234
52 TM S/N AB1234
53 RGB S/N AB1234
54
55 ENGINE 1 USAGE
56 STARTS XXXXX
101-10002-851 Ind. I

- 51 -

Document Sagem DS - Reproduction et divulgation interdites

Printing Format 111111111122222222233333333334

1234567890123456789012345678901234567890
57 FLIGHTS XXXXX
58 TOTAL RUN TIME XXXXX
59 TOTAL FH XXXXX
60 127M RUN TIME XXXXX
61 127M FH XXXXX
62 127F RUN TIME XXXXX
63 127F FH XXXXX
64 127E RUN TIME XXXXX
65 127E FH XXXXX
66
67 ENGINE 2 USAGE
68 STARTS XXXXX
69 FLIGHTS XXXXX
70 TOTAL RUN TIME XXXXX
71 TOTAL FH XXXXX
72 127M RUN TIME XXXXX
73 127M FH XXXXX
74 127F RUN TIME XXXXX
75 127F FH XXXXX
76 127E RUN TIME XXXXX
77 127E FH XXXXX
78
79 ENGINE 1 LCF PARTS ID
80 LP IMPELLER S/N XXXXXX P/N XXXXXXX
81 HP IMPELLER S/N XXXXXX P/N XXXXXXX
82 HP FRONT COVER S/N XXXXXX P/N XXXXXXX
83 HP DISK S/N XXXXXX P/N XXXXXXX
84 HP REAR COVER S/N XXXXXX P/N XXXXXXX
85 AIR SEAL S/N XXXXXX P/N XXXXXXX
86 LP DISK S/N XXXXXX P/N XXXXXXX
87 1ST PT DISK S/N XXXXXX P/N XXXXXXX
88 2ND PT DISK S/N XXXXXX P/N XXXXXXX
89
90 ENGINE 2 LCF PARTS ID
91 LP IMPELLER S/N XXXXXX P/N XXXXXXX
92 HP IMPELLER S/N XXXXXX P/N XXXXXXX
93 HP FRONT COVER S/N XXXXXX P/N XXXXXXX
94 HP DISK S/N XXXXXX P/N XXXXXXX
95 HP REAR COVER S/N XXXXXX P/N XXXXXXX
96 AIR SEAL S/N XXXXXX P/N XXXXXXX
97 LP DISK S/N XXXXXX P/N XXXXXXX
98 1ST PT DISK S/N XXXXXX P/N XXXXXXX
99 2ND PT DISK S/N XXXXXX P/N XXXXXXX
100
101 *** EOT ***
102
103

List of parameters displayed on the report :

Report part Name of data Data Signification GSE parameter
on report formatting
ATR XX Aircraft type (XX=42 or 72)
REPORT25 Report name
DATE DDMMYY Date DAY, MONTH, YEAR.
101-10002-851 Ind. I

- 52 -

Document Sagem DS - Reproduction et divulgation interdites

Report part Name of data Data Signification GSE parameter

on report formatting
GMT HHMM GMT (Time) UTC
TOTAL LIFE ESNi AB1234 engine i S/N acquired on ENGi_SNk
COUNT label 065
i=1 or 2 (2 engines)
ENGINE i S/N
k=1 or 2 (parameter
splitted in 2 parts)
LP IMPELLER XXXXX engine i LCF component ENGi_Cj_TCYC
total cycles, acquired on
... i=1 or 2 (2 engines)
label 062
2ND PT DISK j=1..9 (9 LCF
components)
REMAINING ESNi AB1234 engine i S/N acquired on ENGi_SNk
LIFE label 065
i=1 or 2 (2 engines)
k=1 or 2 (parameter
splitted in 2 parts)
LP IMP XXXXX engine i LCF component ENGi_Cj_RL
remaining cycles
.... i=1 or 2 (2 engines)
2ND PT j=1..9 (9 LCF
components)
ENGINE i ID ENGINE S/N AB1234 engine i S/N acquired on ENGi_SNk
label 065
i=1 or 2 (2 engines)
k=1 or 2 (parameter
splitted in 2 parts)
TM S/N AB1234 engine i Turbo Machine ENGi_TM_SNk
S/N moteur i, acquired on
i=1 or 2 (2 engines)
label 065
k=1 or 2 (parameter
splitted in 2 parts)
RGB S/N AB1234 engine i Reduction Gear ENGi_RGB_SNk
Box S/N, acquired on label
i=1 or 2 (2 engines)
065
k=1 or 2 (parameter
splitted in 2 parts)
ENGINE i STARTS XXXXX engine i number of starts, ENGi_NSTARTS
USAGE acquired on label 062
i=1 or 2 (2 engines)
FLIGHTS XXXXX engine i number of flights, ENGi_NFLIGHT
acquired on label 062
i=1 or 2 (2 engines)
TOTAL RUN XXXXX engine i total run time, ENGi_TOT_RT
TIME acquired on label 064
i=1 or 2 (2 engines)
TOTAL FH XXXXX engine i total flight hours, ENGi_TOT_FH
acquired on label 064
i=1 or 2 (2 engines)
127M(F)(E) XXXXX engine i total run time as ENGi_127M(F)(E)_RT
RUN TIME PW127M(F)(E), acquired
i=1 or 2 (2 engines)
on label 064
101-10002-851 Ind. I

- 53 -

Document Sagem DS - Reproduction et divulgation interdites

Report part Name of data Data Signification GSE parameter

on report formatting
127M(F)(E) XXXXX engine i total flight hours as ENGi_127M(F)(E)_FH
FH PW127M(F)(E), acquired
i=1 or 2 (2 engines)
on label 064
ENGINE i LP IMPELLER XXXXXX engine i LCF component ENGi_Cj_SNk
LCF PARTS S/N S/N, acquired on label 067
i=1 or 2 (2 engines)
ID
....
j=1..9 (9 LCF
2ND PT DISK components)
S/N
k=1 or 2 (parameter
splitted in 2 parts)
LP IMPELLER XXXXXXX engine i LCF component ENGi_Cj_PNk
P/N S/N, acquired on label 066
i=1 or 2 (2 engines)
....
j=1..9 (9 LCF
2ND PT DISK components)
P/N
k=1 or 2 (parameter
splitted in 2 parts)

5.3.2.8.4 Report output

The report is stored in NVRAM and in PCMCIA disk (if any).

5.4. QAR RECORDING

5.4.1. Characteristics
The DMU is able to record a QAR data frame on an internal PCMCIA card (Refer to section 5.16.2 for details
on this function).
This data frame that is in fact the FDR one will be provided by the AFDAU through an internal HDLC line
(Refer to the AFDAU SRD [S02] for more information on this HDLC frame).
The QAR frame will be transmitted per sub-frame of either 64 or 128 or 256 or 512 or 1024 words.
The QAR trigger event is fully programmable on the GSE.

5.4.2. Start/stop control

Means are provided to start or stop the recording of the QAR by:
• Automatic trigger conditions programmed on the GSE.
A set of start and stop trigger conditions is programmable on the GSE for the QAR recording.
Up to 20 different trigger events can be monitored by the DMU.
The initial start/stop logic programmed on the GSE will be:
- start if NH Left or NH Right greater than 40 %.
- stop if NH Left and NH Right less than 40 % for 10 minutes.
• Manual request via the MCDU (start/stop function described in section 5.12.3.7.3).
Manual start/stop control of the QAR is independent from the GSE programmed automatic trigger conditions.
It is not possible to start QAR recording manually if automatically triggered recording is active.
A manually initiated recording is only stopped by a manual stop command and an automatically initiated
recording is only stopped by an automatic stop command.
101-10002-851 Ind. I

- 54 -

Document Sagem DS - Reproduction et divulgation interdites

In case of power interrupts longer than 200 msec the recording shall be stopped until reinitiated either
manually or automatically.

5.4.3. Specific QAR computed parameters

Following parameters have to be computed, for documentary purpose.

5.4.3.1 TRIGGER_QAR parameter

A parameter is computed by the DMU giving the status of QAR recording.
This parameter equals:
• 0 when QAR is not running.
• 1001 when QAR is running and was triggered by a manual request from MCDU.
• the logic number that triggered QAR, if QAR is running and was triggered by a programmable logic.
Parameter name on GSE: TRIGGER_QAR.
Parameter format: integer – 4 digits.

5.5. DAR RECORDING

5.5.1. Characteristics
The DMU is able to record a DAR data frame on an internal PCMCIA card (Refer to section 5.16.3 for details
on this function).
The DAR output speed is programmable to 64, 128, 256, 512, 1024 and 2048 words per second.
Data to be recorded, DAR speed and DAR trigger event are fully programmable on the GSE.
The DMU provides pre-event recording capabilities on the DAR; programmable on the GSE by steps of 4
seconds (one main frame). Maximum pre-event duration depends on the DAR speed as described in
following table:
Speed PEH duration
2048 w/s 16 seconds
1024 w/s 32 seconds
512 w/s 60 seconds
256 w/s 120 seconds
128 w/s 240 seconds
64 w/s 480 seconds

Concerning the data to be recorded, it’s possible on the GSE to select one of the two following modes:
♦ DAR standalone: the DAR frame is built only with parameters defined on the GSE.
♦ DAR based on FDR: the DAR frame is built from the FDR frame. It means that from the FDR frame received
by the DMU from the AFDAU, with the GSE it’s possible to add new parameters, to replace any parameter
by new ones directly acquired by the DMU, to add any parameter defined on the GSE.
Moreover, the original FDR number of words per second can be increased from the GSE. In this case the
following rule will be applied to locate the old PCM words (based upon a DAR/FDR rate ratio of 2n):
FDR initial word position w relocated in position (w-1)*2n+1
Example for n=1: FDR new words position: 1,3,5,…
As default programming a DAR frame containing the APM parameters received from the AFDAU, and DMU
function troubleshooting parameters will be programmed. The detailed DAR frame is defined in Appendix
6.5.
101-10002-851 Ind. I

- 55 -

Document Sagem DS - Reproduction et divulgation interdites

5.5.2. DAR format general organisation

DAR data words to be recorded are formatted in 12 bit words.
DAR data are recorded in a cyclic main frame of 4 seconds. This main frame is divided in 4 subframes of 1
second. Number of words inside a subframe depends on the selected speed.
Only complete main frames have to be recorded. That means if a DAR stop condition has been encountered,
recording shall be terminated not before the last main frame has been completely recorded. In addition, in
case of a PEH time programmed, the real stop will only occurs after this time being elapsed.
The parameter word assignment within the DAR frame is fully programmable by GSE. It is possible to create
individual parameter assignment for each of the four subframes of a main frame.
The recording of documentary data can be distributed in form of a superframe. A super frame is recorded
once in the main frame (4sec) and allow the recording of up to 16 different parameters on a cyclic basis.
Super-frame are free programmable by the GSE.
The DAR parameter sample rates inside the frame shall be ¼, ½, 1, 2, 4, 8, 16 and 32 samples per second.
The first word of each subframe shall be reserved for a sync word according to ARINC 717 for the purpose of
bit and word synchronisation on the reading station :
Subframe Synchro
number word
1 0x247
2 0x5B8
3 0xA47
4 0xDB8

5.5.3. DAR data recording rules

All A/C parameters are recorded in a raw format.
All bits from Bit 1 to Bit 32 of ARINC 429 words are accessible for DAR recording.
If more than 12 bits have to be recorded for a single parameter, then several frame locations can be used.
DAR recording is performed according to the SSM status of the parameters to be recorded.
In case of a not-refreshed parameter, or a bad SSM status, then, the last received value of the parameter is
recorded. Default value if parameter has never been acquired by the DMU is 0.

5.5.4. Start/stop control

Means are provided to start or stop the recording of the DAR by:
• Automatic trigger conditions programmed on the GSE.
A set of start and stop trigger conditions is programmable on the GSE for the DAR recording.
Up to 20 different trigger events can be monitored by the DMU.
The initial start/stop logic programmed on the GSE will be the same as for the QAR recording (see
section 5.4.2)
• Manual request via the MCDU (start/stop function described in section 5.12.3.7.3).
Manual start/stop control of the DAR is independent from the GSE programmed automatic trigger conditions.
It is not possible to start DAR recording manually if automatically triggered recording is active.
A manually initiated recording is only stopped by a manual stop command and an automatically initiated
recording is only stopped by an automatic stop command.
In case of power interrupts longer than 200 msec the recording shall be stopped until reinitiated either
manually or automatically.
101-10002-851 Ind. I

- 56 -

Document Sagem DS - Reproduction et divulgation interdites

5.5.5. Specific DAR computed parameters

Following parameters have to be computed, for documentary purpose.

5.5.5.1 TRIGGER_DAR parameter

A parameter is computed by the DMU giving the status of DAR recording.
This parameter equals:
• 0 when DAR is not running.
• 1001 when DAR is running and was triggered by a manual request from MCDU.
• The logic number that triggered DAR, if DAR is running and was triggered by a programmable logic.
Parameter name on GSE: TRIGGER_DAR.
Parameter format: integer – 4 digits.

5.5.5.2 DAR frame counter

The DAR FRAME COUNTER is incremented by 1 at the beginning of each main frame (every 4 sec).
DAR FRAME COUNTER is set to 1 after a DMU power-up.
Parameter name on GSE: DFC.

5.6. BITE/CMC FUNCTION

This function displays maintenance messages and troubleshooting procedure of various external equipment.
The messages and procedures are defined in Excel files (see section 6.6 and CID [S05]), which content is
converted to c file.
This function is managed from MCDU and is described in section 5.12.3.5.

5.7. APM LEVEL OUTPUT DISCRETES

The two APM level output discrete (APM level 1 and APM level 2) must be driven according to their status
received in an ARINC 429 message from the AFDAU (Refer to the AFDAU SRD [S02] for more information
on this message).
If this message is not received as expected for three seconds, then APM level 1 output is inverted and APM
level 2 is set to active state (i.e. grounded).
This mechanism may be overridden by the light test (see section 5.20).

5.8. TRIGGER LOGICS

The DMU shall be able to monitor programmable logics from the GSE. The GSE is in charge of providing
operational code for these logics.
A programmable trigger logic consists of arithmetical and logical combination between parameter values,
memorized variables or numerical constants.
The result of a logic is a numerical expression and can be used as START/STOP function in the DAR, QAR
and SAR recording and report trigger functions.
Logics are programmed in a specific language which provide at least the following capabilities:
− Use of any parameter available (A/C BNR, discrete, status words or internal DMU computed).
− Arithmetical operations on integer or floating point values (+, -, x, /).
− Logical combination (AND/OR/NOT...).
− Use of local variables (allowing history data management).
101-10002-851 Ind. I

- 57 -

Document Sagem DS - Reproduction et divulgation interdites

− Definition of a time delay for any condition: in that case the time delay starts counting as soon as the
condition is TRUE and is reset if the condition becomes FALSE.
− Access to mathematical libraries (Sine cosine etc…)
− Access to enhanced library functions such as:
• Average computing
• Minimum / maximum search
• Time under/over limit search

5.9. STANDARD SAR AND EXTENDED SAR FUNCTIONS

5.9.1. SAR characteristics

5.9.1.1 Standard SAR function

The DMU is able to record ACMS data on a SAR being integrated in the DMU. The storage medium of the
SAR is NVRAM. 2.0 Mbytes are reserved for SAR recording.
Independent from this storage in NVRAM, all generated standard SAR records are stored on the PCMCIA
disk if required conditions are met. Refer to section 5.16.6 for details on this function.
The DMU provides 8 independent recording channels. Each channel has a recording capacity of 128 words
per second.
The DMU provide pre-event recording capabilities on all SAR channels. Up to 5 minutes of history data
programmable in a 1 minute step on the GSE for each channel. By this way, the history of values taken by
parameters before the starting of the recording are available
For retrieving purpose and storage memory partitioning purpose, the 8 Standard SAR channels are split in 2
sets of 4 channels. Those two partitions are identified on the GSE as “SAR Data recording (Data Set 1 to 4)”
and “SAR extended trouble shooting (Data Set 5 to 8)”.
Data to be recorded on SAR channels, history time and SAR trigger events are fully programmable on the
GSE.

5.9.1.2 Extended SAR function

The DMU is able to manage additional SAR channels using the PCMCIA storage medium. Recording of data
is performed exclusively on the PCMCIA media : no storage in NVRAM is provided for this function. This
function will then only be available if a PCMCIA media is inserted in the MPC unit.
The DMU provides 8 independent recording channels. Each channel has a recording capacity of 512 words
per second.
Those 8 channels are identified on the GSE as "Data Recording (Data Set 9 to 16)"
The DMU provide pre-event recording capabilities on all SAR channels. 0 or 1 minutes of history data
programmable on the GSE for each channel.
Data to be recorded on SAR channels, history time and SAR trigger events are fully programmable on the
GSE.

5.9.2. SAR records/memory partition

5.9.2.1 Standard SAR function

As explained in chapter 5.9.1.1, storage memory is split in two partitions “SAR Data recording (Data Set 1 to
4)” and “SAR extended trouble shooting (Data Set 5 to 8)”.
The NVRAM ratio (in %) between those two partitions is programmable on the GSE in the screen
"Programming -> SAR Data recording -> Trigger monitoring -> Setup".
101-10002-851 Ind. I

- 58 -

Document Sagem DS - Reproduction et divulgation interdites

Inside each partition, SAR records are stored in a FIFO mode. When the memory is full, then the oldest
record inside the partition is deleted.
Each SAR channel when triggered is stored in a specific record. A record includes all acquired data from
start event until stop event, plus pre-event history data if programmed. A set of 16 documentary data can
also be recorded once when the recording starts. Documentary data set is programmable on the GSE and is
common for all SAR channels within a partition.
For retrieving purpose, the size of a SAR record is limited to 1 Mbyte.
When a new data base is loaded, the DMU must check the memory partition, and in case that partition has
changed, the whole memory is then reset.

5.9.2.2 Extended SAR function

Not applicable because the SAR extended data recording is stored directly on PCMCIA disk.

5.9.3. SAR stored data

All parameters defined on the GSE are free selectable for storage in a SAR record, including A/C and DMU
computed ones.

5.9.3.1 Standard SAR function

Possible sample rates inside a record are 1, 2, 4, 8, 16 and 32 samples per second.
To reduce the memory requirements of the SAR, SAR data are compressed prior to storage. Selection of the
data compression algorithm and the compression tolerance is programmed on the GSE.

5.9.3.2 Extended SAR function

Possible sample rates inside a record are ¼, ½, 1, 2, 4, 8, 16 and 32 samples per second.
To reduce the memory requirements of the SAR, SAR data are compressed prior to storage. Selection of the
data compression algorithm and the compression tolerance is programmed on the GSE.

5.9.4. Manual SAR data retrieving

5.9.4.1 Standard SAR function

A PCMCIA disk can be used for downloading of standard SAR data stored in DMU NVRAM. Refer to section
5.16.4.2 for details on this function.
For both partitions, whenever data retrieval from the SAR has been requested, the system shall generate an
advisory message and send it to the ACARS MU for downlink purpose (see chapter 5.13.2.2.7). This ACARS
message is optional and can be inhibited by GSE programming. Text of the message is user programmable
through the GSE.

5.9.4.2 Extended SAR function

Not applicable.

5.9.5. Start/stop control of SAR recording

Means are provided to start or stop the recording of the SAR by:
• automatic trigger conditions programmed on the GSE,
• manual request via the MCDU.

5.9.5.1 Automatic Start/Stop

A set of start and stop trigger conditions is programmable on the GSE for both Standard SAR and Extended
SAR recordings.
101-10002-851 Ind. I

- 59 -

Document Sagem DS - Reproduction et divulgation interdites

A total number of 50 events can be monitored by the DMU, each event being able to trigger one or several
SAR channels. Each event is composed of:
• A start condition.
• A stop condition.
• A time-out (optional).
• Trigger limitations (number of triggers per leg).
When a start event occurs, the system first stores pre event data and then starts to collect at and post event
real time data. The post event data time is achieved when the associated stop logic becomes true or when a
programmable time delay (time-out) is reached, whatever comes first.
Only one condition is active at a time per data set, i.e.: if a second start condition occurs when a first one is
already active, on the same data set, this second one is ignored.
An automatically triggered recording is only stopped by:
• the associated stop condition becomes true,
• a programmed time-out is elapsed,
• a DMU power interrupt greater than 200 msec occurs,
• maximum recording size is reached.
The system generates an advisory message and sends it out via ACARS whenever a programmed start
event is met. The text of the advisory message is user programmable via the GSE. This ACARS message is
optional and can be inhibited by GSE programming. Refer to section 5.13.2.2.6 for detailed format of this
message.

5.9.5.2 Manual Start/Stop

A specific MCDU screen is provided to start and stop the recording of SAR channels by manual request
(refer to appendix E). This manual start/stop control of the SAR is independent from the GSE programmed
automatic trigger conditions.
In case of a manual start, no ACARS message is provided.
It is not possible to start SAR recording manually if automatically triggered recording is active. So, if an
automatic trigger becomes true during manually triggered recording, then it is ignored by the DMU.
A manually initiated recording is only stopped when:
• manual stop command is initiated,
• DMU power interrupt greater than 200 msec occurs,
• maximum recording size is reached.
Note: a manual start of a SAR record is identified by logic number 1000.

5.9.5.3 SAR trigger inhibit through ACARS

It is possible to inhibit each trigger event through a specific ACARS message. Refer to section 5.13.3.3.6 for
details on this function.

5.10. SAR EVENT RECORDING

5.10.1. Purpose
The system can store predefined sets of data when corresponding events are met.
101-10002-851 Ind. I

- 60 -

Document Sagem DS - Reproduction et divulgation interdites

5.10.2. Trigger Logics

50 different events are programmable through GSE logics. It is possible to enable/disable individually and
independently each event through GSE or via ACARS uplink (see 5.13.3.3.6).

5.10.3. Stored Data

For each event a specific data set of up to 15 programmable parameters is recorded in the DMU NVRAM.
One sample of each parameter is recorded.
A documentary data set containing up to 8 parameters (like date, time, flight number, etc... ) can also be
recorded. This documentary data set is common for all SAR Event data sets.
All data sets and documentary data are programmable through the GSE.
The system shall memorize the data sets related to the last 60 events.
Independent from this storage in the DMU NVRAM, all generated SAR Event data sets are stored on the
PCMCIA disk if required conditions are met. Refer to section 5.16.6 for details on this function.

5.10.4. Output
The system can downlink an advisory message by ACARS whenever a programmed start event is met (see
chapter 5.13.2.2.6). The text of the advisory message is user programmable via the GSE.
The system shall transmit by ACARS the new stored statistics data on a programmable fixed date of the
month (through the GSE screen Programming -> SAR Event Recording -> Trigger monitoring -> Setup) or if
requested via ACARS uplink (described in chapter 5.13.3.3.7).
That statistic message contains the date and time of last retrieval, the accumulated flight hours and number
of flights, and the status of the logic counter 1 - 50. It is described in chapter 5.13.2.2.8.

5.10.5. Data retrieving

A PCMCIA disk can be used for downloading of data. Refer to section 5.16.4.2 for details on this function.
Whenever data retrieval for event recording data has been requested, the system shall generate an advisory
message and send it to the ACARS MU for downlink purpose. Through the GSE screen Programming ->
SAR Event Recording -> Trigger monitoring -> Setup, the operator can enable or disable this ACARS
message and modify its text.

5.11. TEMPORARY AND INFINITE CHANGES

It is possible to alter the DMU programming entered in the GSE by changing the setting of constants, and
trigger limits for a limited period of time or an infinite time.
The modification shall only be valid during a programmable number of flight legs (1 to 99) ,during a
programmable time period (1 to 99 days) or during an infinite time period or an infinite number of flight legs.
A maximum of 50 limits are modifiable at the same time.
This modification can be done using a specific ACARS uplink message (see section 5.13.3.3.4),
44 characters can be used to indicate information about the reason of the temporary revision. Those
information are sent by ACARS (part of the temporary modification uplink).
The modification shall be erased automatically when the leg, or date limit has been reached and will never
be erased when the infinite limit working is chosen. In this case, the only way to change the limit time
duration is to modify the limit with a new validity. The value valid prior modification shall become valid again.
The modification can also be erased using a specific ACARS uplink message (see section 5.13.3.3.5).
In case of limit modification or erase, a specific message has to be sent to the ACARS, as defined in
sections 5.13.2.2.4 and 5.13.2.2.5.
Detailed list of all limits available for modification is defined in section 6.2.
101-10002-851 Ind. I

- 61 -

Document Sagem DS - Reproduction et divulgation interdites

5.12. MCDU FUNCTIONS

5.12.1. Introduction
The DMU communicates with the MCDU according to ARINC 739 protocol.
In addition to this standard, the following rules have to be applied:
When a 5 seconds delay is elapsed after power-up, the DMU must transmit every second the activity Arinc
word 0x0000437A (label 0172) on MCDU output bus. The 5 seconds delay prevents some MCDU models
from displaying the ACMS page as their first page.
In the aircraft, one MCDU can be connected to the DMU.

┌ ┌
MCDU #1 DATA IN A├
B├ MCDU #1
MCDU DATA OUT A├
B├

Figure 5-4 - Interconnection between the MPC and the MCDU

MENU
1L █ <FMS █ 1R
2L █ <ACARS █ 2R
3L █ <MPC █ 3R
4L █ █ 4R
5L █ █ 5R
6L █ █ 6R

Figure 5-5 - MCDU Main Menu (example)

When a MCDU selects the MPC, then this one transmits its main menu.

5.12.2. GENERAL RULES

5.12.2.1 The screen

The MCDU contains 14 lines, each having 24 characters. The top line is normally used to display the title
and the pages numbering. The bottom line is the scratchpad line and is used by the operator to alter data on
the screen.
The 12 other lines are arranged into 6 pairs (lines 2-3, 4-5, 6-7, 8-9, 10-11, 12-13). Each pair of lines has a
label line (the first one) and a data line. The data lines are adjacent to the line selected key (LSK). The line
pairs are referenced by the select keys. A line pair may be divided into two different parts that are referenced
each by a LSK. The LSK are named xL or xR on the left side or right side (x = 1 to 6).
The line select key is used to alter a data field or to activate a function. If an unaffected key is pressed, the
message "NOT ALLOWED" is displayed in the scratchpad.
101-10002-851 Ind. I

- 62 -

Document Sagem DS - Reproduction et divulgation interdites

The line 6L is always used for RETURN function (return to previous menu) whereas the line 6R is generally
used for printout of the MCDU screen.

┌
LINE FOR TITLE
first half second half
1L █ PAIR 1 PAIR 1 █ 1R
first half second half
2L █ PAIR 2 PAIR 2 █ 2R

3L █ PAIR 3 PAIR 3 █ 3R

4L █ PAIR 4 PAIR 4 █ 4R

5L █ PAIR 5 PAIR 5 █ 5R

6L █ PAIR 6 PAIR 6 █ 6R
scratchpad

Figure 5-6 - MCDU Screen (example)

5.12.2.2 The keyboard

The MPC functions use the following keys:
• Line select keys: 1L,2L,3L,4L,5L,6L,1R,2R,3R,4R,5R,6R.
• Scratchpad keys: Letters A-Z, figures 0-9, / , ., +, - and space.
• Mode key: Pressing the MENU mode key causes the MCDU main menu to be displayed.
• Function keys:
↑ : Display of previous page if it exists.
↓ : Display of next page if it exists.
CLR : Clears the scratchpad or data fields.

5.12.2.3 General display rules

For all display fields, only valid data will be displayed.
• If a data is not refreshed then its field is filled with "XXXXXX".
• If a data is not valid (bad SSM) then its field is filled with "------".
When a new page is accessed or a data is entered, some calculations by the DMU may be required. Then,
the screen is firstly blanked and only the fields that are immediately available are displayed. The other fields
are displayed when data are available.
There are special symbols on MCDU displays that indicate certain functions to the operator. The following
symbols are:
− <,> : This symbol appears in front of a line select key to indicate that this key is available. It is used
for the display of a new page.
− * : This symbol is used to indicate that pressing the corresponding key will activate a function or that the
active situation of the aircraft will be affected.
− [,] : This symbol is used to indicate that a user may enter a value (optional value).
− : The user has to enter data in order for the computer to perform the function.
− ↑ ↓ : Vertical slewing (appears in column 23/24 of scratchpad).
101-10002-851 Ind. I

- 63 -

Document Sagem DS - Reproduction et divulgation interdites

− → ← : Select a data without activating a function.

Certain pages are too long to be displayed on a single page of MCDU. In this case, data are displayed on
different pages. A printout of the screen implies a complete print of all the pages that are in memory.
COLORS
The color of displayed data is in accordance with the following rules:

Data Color

Titles, comments, scratchpad call-up of menus, minor messages symbols of slewing dashes WHITE

Operator modifiable data, brackets selectable data, call-up of function RETURN and PRINT CYAN

Operator non modifiable data active data GREEN

Mandatory data (boxes) mandatory operator action required important messages AMBER

Constraints, max altitude MAGENTA

Temporary situation YELLOW

For MCDU screen descriptions, the colors of characters will be represented by:
− WHITE: W = Large fonts – w = Small fonts.
− CYAN: C = Large fonts – c = Small fonts.
− GREEN: G = Large fonts – g = Small fonts.
− AMBER: A = Large fonts – a = Small fonts.
− MAGENTA: M = Large fonts – m = Small fonts.
− YELLOW: Y = Large fonts – y = Small fonts.
Note: the <,>,←,→,↑,↓, and * have the color of the prompt to which they are associated.

DATA ENTRY
Data are entered on the MCDU through the keyboard. They are displayed in the scratchpad line. Only 22
characters are taken on a line. The 23rd and following characters entered are ignored.
After the data are entered into the scratchpad, they are moved from the scratchpad into the correct data
fields by pressing the adjacent line select key and the scratchpad is blanked. The computer verifies that the
data correspond to the defined fields.
If the data are incorrect, the previous fields are left and an error message is displayed in the scratchpad.
• "INVALID ENTRY":
The format of the data that are expected by the DMU does not correspond to the sent by the MCDU.
For instance, letters instead of figures, octal parameter with a "8" or "9"...
The format of data is right but the values are not correct. For instance, a label greater than 377...
Number of data on the scratchpad does not correspond to the number of fields of the line.
• "NOT ALLOWED":
The LSK or any other key (arrow , MCDU mode key, ..) is not authorized.
Other error messages depends on the displayed menu.
101-10002-851 Ind. I

- 64 -

Document Sagem DS - Reproduction et divulgation interdites

Once an error message has been printed, the following action must be taken:
− Clear the message in the scratchpad by using the CLR key. The incorrect data then appears in the
scratchpad. The operator can either correct them, clear them or press another select key.
− To clear or to correct data, the key CLR is used again. Each single press on the key erases one
character(beginning by the last one). If the CLR key is maintained pressed more than one second then
the whole line is cleared.
− It is also possible to enter a new data: this automatically clears the whole line.
If the scratchpad is empty, the CLR key is used to display "CLR" in the scratchpad. Then, pressing a LSK will
automatically clear the corresponding fields. Another CLR key clears the 'CLR' information in the scratchpad.
The clear of a field allows to recover the default value when it exists.
The entry format of data is described by the number of boxes that are defined on a line. If only one set of
boxes is displayed, just enter a value. This value may have less characters than the number of boxes on the
line: For instance, if the operator must enter a data corresponding to a field with 3 boxes that represents a
decimal number, then 004, or 04 or even 4 are accepted.
If a line contains more than one set of boxes, the values entered in the scratchpad must contain a separator
for the different fields. This separator is the slash (/)5S5
Example:
Enter the port number, Label, SDI on the same line for the Label call-up (port = 1, Label = 322, SDI = 01).
To change all the values, the operator must enter: 1/322/01.
To modify the SDI if the other data do not change, just enter: //10
To modify the label alone, just enter: /222
Some lines which contain multiple fields may be associated to 2 LSK.
It is possible, when the scratchpad is empty, to initialize it with the actual value of the fields. To do that, just
press on the LSK in front of the line. The content of the fields is then transferred into the scratchpad. It is
then possible to modify it as any other scratchpad line.

HARDCOPY: Hard copy function on PRINTER AND/OR storage in a file on PCMCIA disk.
The text "PRINT*" and the possibility to use the hardcopy function depend on PRINTER and on PCMCIA
effective presence :
− If neither PRINTER nor PCMCIA are present and available the message "PRINT*" will be deleted on
MCDU screen. The message “ PRINT&PCMCIA NOT AVAIL” will be displayed in the scratchpad in case
of a HARDCOPY attempt.
− If at least one of the hardcopy peripherals (PCMCIA disk, PRINTER) is present and available, the
message "PRINT*" will be displayed, and the use of hardcopy function will lead to the display of
messages depending on the peripheral(s) which is(are) available :
If only the PCMCIA disk is present and available (PRINTER is not present, or printer is present but
if its status indicates: "out of paper", "printer error" or "inoperative/power off") then the message
"HARDCOPY PCMCIA ONLY" will be displayed in the scratchpad in case of a HARDCOPY
attempt.
If only the PRINTER is present and available (PCMCIA disk not present and not available) then
the message "HARDCOPY PRINTER ONLY" will be displayed in the scratchpad in case of a
HARDCOPY attempt.
101-10002-851 Ind. I

- 65 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3. MPC PAGES

The following schemes summarise the main functions of MCDU application and their hierarchy.
MPC initial menu
├ call up parameters
├ label call-up
├ alpha call-up
├ parameters menus
├ ident
├ flight mode
├ g-meter
├ APM
├ maintenance
├ cruise
├ exceedance
├ CMC
├ eng ident
├ eng stats
├ eng LCF PN
├ eng LCF SN
├ eng LCF CY
7
7
├ status
├ Bite DMU status
├ Load DMU status
7
├ QAR/DAR/SAR
├ QAR PCM
├ DAR PCM
├ SAR SUMMARY
├ SAR RECORDING
├ DATA RECORDING
├ EXTENDED TROUBLESHOOT
├ EVENT RECORDING
├ EXTENDED DATA RECORDING
├ SAR MANUAL REQ.
7
├ MAINTENANCE
├ AFCS
├ general troubleshooting
├ choices

7
├ ADU messages
├ choices

7
├ ground maintenance test
├ choices

7
├ flight fault summary
├ automatic reading
├ choices

7
├ manual reading
├ FFS decoding
├ choices

7
7
7
7
├ version
├ RAD COM/NAV
101-10002-851 Ind. I

- 66 -

Document Sagem DS - Reproduction et divulgation interdites

├ ATC TDR90

├ ATC TDR94D
├ VOR VIR 32
├ DME 42
├ ADF 60
├ VHF 22
7
├ DTUE
├ TCAS
├ PEC/EEC
├ trim EEC
├ code EEC
├ trim PEC
├ code PEC
7
├ MFC
├ basic memory
├ WOW & landing gear
├ flight controls
├ doors
├ miscellaneous 1
├ boots
├ miscellaneous 2
├ navigation
├ miscellaneous 3
├ brake
├ MFC/miscellaneous 4
7
├ flight fault memory
├ WOW & landing gear
├ flight controls
├ doors
├ miscellaneous 1
├ boots
├ miscellaneous 2
├ navigation
├ miscellaneous 3
├ brake
├ MFC/miscellaneous 4
7
├ memory erasing
7
7
├ PCMCIA
├ Disk ident
├ Disk directory
├ Disk dar recording
├ Disk qar recording
7
├ identifications
├ reports
├ list of previous reports
├ stored reports
├ stored report 02
├ stored report 03
├ stored report 15
├ stored report 16
├ stored report 22
├ stored report 23
├ stored report 24
├ stored report 25
7
├ manual report request
7
├ time and flight adjustment
├ g-meter
101-10002-851 Ind. I

- 67 -

Document Sagem DS - Reproduction et divulgation interdites

├ init param

├ A/C param init
├ Ethernet param init
7
├ CMC
├ Last flight report
├ Gnd Test report
7 7

5.12.3.1 MPC main menu

5.12.3.1.1 Screen presentation

After an MPC selection, the MPC following initial menu is displayed.
┌
MPC
Call-up
1L █<PARAM STATUS>█ 1R
QAR/DAR/SAR
2L █<RECORDING MAINTENANCE>█ 2R

3L █<PCMCIA IDENT>█ 3R
init
4L █<REPORTS TIME & FLT>█ 4R
init
5L █<G-METER PARAM>█ 5R

6L █<CMC █ 6R

Figure 5-7 - MPC main menu

In the MPC main menu the following functions can be selected:

• LSK 1L (call-up param): Display menus of ALPHA call-up (programmed by GSE).
• LSK 1R (load status): Displays status .
• LSK 2L (QAR/DAR/SAR): Displays QAR/DAR PCM data. Displays SAR summary. Starts and stops
SAR.
• LSK 2R (Maintenance): Access to external equipment maintenance data.
• LSK 3L (PCMCIA) is used to access to PCMCIA card management functions.
• LSK 3R (ident): Displays MPC & A/C identifications.
• LSK 4L (reports): Displays the list of the last stored reports (reports history), display the list and contents
of all stored reports (stored reports), triggers manually reports.
• LSK 4R (init time & FLT): Enable to initialize time and flight number in the FDAU.
• LSK 5L (g-meter): Displays the contents of the last G-Meter report generated.
• LSK 5R (init param): Display the init param menu giving access to A/C param init and Ethernet param
init pages.
• LSK 6L (CMC) : Display report <22> (flight CMC) and generate report <23> (GND test CMC).

No return is provided. The only way to exit DMU communication is to press the "MCDU" key.
Error messages that can be displayed on that screen are the following ones:
101-10002-851 Ind. I

- 68 -

Document Sagem DS - Reproduction et divulgation interdites

• NOT ALLOWED: undefined LSK or any MCDU key except LSK defined above.

5.12.3.1.2 EEC alerts display

Alerts of invalidity of EEC data and of LCF component life coming close to limit, are displayed in the
scratchpad of MPC main menu. In case of several alerts being present at the same time, only the one with
highest priority (lowest rank) shall be displayed.

Rank Message Color Triggering condition

1 WARNING : ENG 1 LCF Magenta Any of engine 1 LCF total life is above limit (LCF total life limit is
modifiable with the GSE, see §6.2.5)
2 WARNING : ENG 2 LCF Magenta Any of engine 2 LCF total life is above limit (LCF total life limit is
modifiable with the GSE, see §6.2.5)
3 DCU 1 INOPERATIVE Yellow Data received on label 062 of EEC1 bus have an SSM being 00
4 DCU 2 INOPERATIVE Yellow Data received on label 062 of EEC2 bus have an SSM being 00
5 CAUTION : ENG 1 LCF Yellow Any of engine 1 LCF component remaining life is below 1% of limit
(threshold modifiable with the GSE, see §6.2.5)
6 CAUTION : ENG 2 LCF Yellow Any of engine 2 LCF component remaining life is below 1% of limit
(threshold modifiable with the GSE, see §6.2.5)

5.12.3.2 Parameter call up

This menu is used to select which type of parameter call-up is used.
• display parameters in raw values,
• display parameters in engineering values,
• display predefined menus of parameters.
The whole menu is in white except the RETURN and PRINT in cyan characters.
┌
MPC PARAM CALL-UP

1L █<PARAM LABEL CALL-UP █ 1R

2L █<PARAM ALPHA CALL-UP █ 2R

3L █<MENUS █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-8 - MCDU PARAM CALL-UP Menu
The only message associated to that screen is:
• NOT ALLOWED: invalid key (LSK or any other key).
101-10002-851 Ind. I

- 69 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.2.1 Parameter label call up

Every aircraft parameter (ARINC 429 message) available on an acquisition bus is selectable for display on
the MCDU using following information : port, label and SDI.
The raw value of the parameter is displayed in binary and hexadecimal values. The parameter values are
refreshed once per second.
If the parameter hasn't been refreshed on the ARINC 429 bus in the previous 1 (one) second then the
display value fields contains X.
Format of data:
• PORT : ARINC 429 port number (2 characters).
• LAB : Label in octal representation (1 to 3 characters).
• SDI : SDI in binary representation or "XX": bits (10,9).
• HEX/BIN VAL : Binary and Hexadecimal values of the parameter (Bits 31->9).
Port, system, label, SDI are required before data display.
If these fields are not correct, the error messages that appear on the screen are described hereunder with
the different reasons that may occur:
• INVALID ENTRY:
- label is not octal value
- label > 377
- SDI not in binary and not "XX"
- at least a mandatory entry is missing
- invalid delimiter character
- any undefined character

• NOT ALLOWED : invalid key (LSK or any other key)

Format of display:
┌
MPC PAR LAB CALL-UP 1/8
port/lab/sdi
1L █←LL LLL LL █ 1R

2L █ █ 2R

3L █ █ 3R
port/lab/sdi
4L █←LL LLL LL █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
01/344/01 ↑↓

Figure 5-9 - MCDU PARAM LABEL CALL-UP Page (1)
101-10002-851 Ind. I

- 70 -

Document Sagem DS - Reproduction et divulgation interdites

After depressing key 1L:

┌
MPC PAR LAB CALL-UP 1/8
port/lab/sdi
1L █←01 344 01 █ 1R
hex/bin val(bits 31-9)
2L █66C969 █ 2R
11001101100100101101001
3L █ █ 3R
port lab sdi
4L █←LL LLL LL █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
01/344/01 ↑↓

Figure 5-10 - MCDU PARAM LABEL CALL-UP Page (2)

Eight pages are possible for this menu: Up to 16 label call-up.

The selected label call-up are kept in memory when leaving this screen, until next DMU power off.
It is possible to clear individually the display of each label call-up by using the function: "CLEAR" of MCDU
keyboard. For that, after depressing the "CLEAR" key of MCDU the "LSK" key of label call-up to cancel must
be selected.
The function: "PRINT"(LSK 6R) allows to hard copy (on MPTR and/or on PCMCIA disk) the label call-ups
which are selected. Label call-up lines which are not used (no entry) are not hard copied.

5.12.3.2.2 Parameter alpha call up

Every alpha call-up defined in the set-up data base may be selected to visualize one or 2 parameters in
engineering values. The screen gives in addition the origin of the parameter (name of the bus).
Each parameter will be displayed on a line and the value of each displayed parameter should be refreshed at
rate 1Hz.
Up to 1000 alpha call-up may be defined by the GSE, each of them may contain up to 2 parameters.
The list of alpha call-up that are available at delivery is defined in Appendix 6.4.
Up to 20 alpha call-ups can be displayed on this menu (Five pages).The alpha call-ups menu is always
memorized, it is cleared only after OBPM loading.
The function: "CLEAR ALL"(LSK 1R) allows to cancel the display of all alpha call-ups selected for this menu.
Note:
It is possible to clear individually the display of each alpha call-up by using the function: "CLEAR" of MCDU
keyboard. For that, after depressing the "CLEAR" key of MCDU the "LSK" key of alpha call-up to cancel
must be selected.
The function :"PRINT"(LSK 6R) allows to hard copy (on MPTR and/or on PCMCIA) the alpha call-ups
selected. Alpha call-up lines which are not used (no entry) are not hard copied.
Format of data:
• ALPHA : Alpha call-up code (1 to 5 characters).
Alpha is required before data display.
If this field is not correct, the error messages that appear on the screen are described hereunder with the
different reasons that may occur:
• INVALID ENTRY : alpha with more than 5 characters or undefined character in the alpha.
101-10002-851 Ind. I

- 71 -

Document Sagem DS - Reproduction et divulgation interdites

• NOT ALLOWED : invalid key (LSK or any other key).

• UNKNOWN ALPHA CODE : the alpha code does not exist in the data base.
The displayed information is then:
• SOURCE of the parameter (Up to 6 characters): the name of the port from which the parameter
comes.
• POSITION (1 character): position number of the parameter. It may be either 1 (left engine) or 2 (right
engine). If no engine is concerned for this parameter, then a space is displayed.
• VALUE (Up to 8 characters): The parameter value is displayed with the following rules:
if one of the displayed parameters is not refreshed for two seconds then the display value field
contains "XXXXXXXX".
if one of the displayed parameters is not valid (bad SSM) for two seconds then the display value
field contains "--------".
for a numerical parameter, the engineering value is displayed in the GSE format , with signs + and
-.
for a discrete parameter, its signification is displayed (GSE programmation).
set of discretes: in the representation programmed on GSE.
• UNIT of displayed parameter(Up to 5 characters). This information is displayed in the line below the
alpha call-up. If the alpha call-up contains two parameters, only the unit of the first parameter is
displayed.
Format of display:
┌
MPC ALPHA CALL-UP 1/5

1L █*HELP CLEAR ALL *█ 1R
alpha source pos value
2L █←LLLLL █ 2R

3L █←LLLLL █ 3R

4L █←LLLLL █ 4R

5L █←LLLLL █ 5R

6L █<RETURN PRINT*█ 6R
rsp1 ↑↓

Figure 5-11 - MCDU PARAM ALPHA CALL-UP Page (1)

After depressing key 1L:

101-10002-851 Ind. I

- 72 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC ALPHA CALL-UP 1/5

1L █*HELP CLEAR ALL *█ 1R
alpha source pos value
2L █←rsp1 fcdc-1 1:-11.53 █ 2R
deg fcdc-2 2:-11.12
3L █←LLLLL █ 3R

4L █←LLLLL █ 4R

5L █←LLLLL █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-12 - MCDU PARAM ALPHA CALL-UP Page (2)

Colors:
┌
WWWW WWWWW WWWWWWW WWW

1L █CCCCC CCCCC CCC C█ 1R
wwwww wwwwww www wwwww
2L █cccccc gggggg wwgggggggg█ 2R
ggggg gggggg wwgggggggg
3L █aaaaaa █ 3R

4L █aaaaaa █ 4R

5L █aaaaaa █ 5R

6L █CCCCCCC CCCCCC█ 6R
wwww

Figure 5-13 – Colors of MCDU PARAM ALPHA CALL-UP Page

A help is provided on key 1L. When pressing this key, the DMU displays the list of available alpha call-ups.
When 1st accessed, this screen display the list from the 1st alpha call-up in alphabetical order.
The operator can then use the right keys to scroll through this screen one by one UP/DOWN or page per
page (PAGE UP/PAGE DOWN).
The operator can also enter the 1st characters of the alpha name and depress the upper left key to search
for a pattern. The alpha list is then displayed, beginning with the 1st alpha name which matches the selected
pattern.
If the pattern is not found, then the message “INVALID DATA” is displayed in the scratchpad.
Alpha call-up help screen lay-out is the following:
101-10002-851 Ind. I

- 73 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC ALPHA CU LIST xx/nn

1L █←[LLLLL] UP*█ 1R
xxxxx xxxxx xxxxx page
2L █ xxxxx xxxxx xxxxx UP*█ 2R
xxxxx xxxxx xxxxx
3L █ xxxxx xxxxx xxxxx █ 3R
xxxxx xxxxx xxxxx page
4L █ xxxxx xxxxx xxxxx DOWN*█ 4R
xxxxx xxxxx xxxxx
5L █ xxxxx xxxxx xxxxx DOWN*█ 5R
xxxxx xxxxx xxxxx
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-14 – HELP page of MCDU PARAM ALPHA CALL-UP Page

Colors:
┌
WWWW WWWWW WW WWWW WWWWW

1L █CCCCCCCC CCC█ 1R
WWWWW WWWWW WWWWW CCCC
2L █ WWWWW WWWWW WWWWW CCC█ 2R
WWWWW WWWWW WWWWW
3L █ WWWWW WWWWW WWWWW █ 3R
WWWWW WWWWW WWWWW CCCC
4L █ WWWWW WWWWW WWWWW CCCCC█ 4R
WWWWW WWWWW WWWWW
5L █ WWWWW WWWWW WWWWW CCCCC█ 5R
WWWWW WWWWW WWWWW
6L █CCCCCCC CCCCCC█ 6R

Figure 5-15 – Colors of HELP page of MCDU PARAM ALPHA CALL-UP Page

5.12.3.2.3 Parameters menus

When this page is selected, the list of the menus programmed on the GSE and available to the operator is
displayed. Up to 20 menus can be programmed by the GSE.
Each menu contains a programmable title and a list of up to 20 alpha call-ups.
First, when this menu is selected, the titles of all the programmable menus are displayed in front of a LSK.
If more than 5 parameters menus are defined then more than 1 page will be necessary to show the whole
display.
The initial programming will include the following menus:
101-10002-851 Ind. I

- 74 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC PARAMETERS MENU 1/3

1L █<IDENT █ 1R
├
2L █<FLIMOD █ 2R

3L █<G-METER █ 3R

4L █<APM █ 4R

5L █<MAINT. █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC PARAMETERS MENU 2/3

1L █<CRUISE █ 1R
├
2L █<EXCEEDANCE █ 2R

3L █<CMC █ 3R

4L █<ENG IDENT █ 4R

5L █<ENG STATS █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC PARAMETERS MENU 3/3

1L █<ENG LCF PN █ 1R
├
2L █<ENG LCF SN █ 2R

3L █<ENG LCF CY █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-16 - MCDU MPC parameter menu

The whole screen except the title is in cyan characters.

The only message associated to that screen is:
• NOT ALLOWED: invalid key (LSK or any other key).
When one of these menus is selected, the screen programmed on the GSE will appear.
This screen consist of:
• On the first line: "TTTTTTTTTTTTTTTTT" where "TTTTTTTTTTTTTT" is the programmed title of the
menu (16 characters).
101-10002-851 Ind. I

- 75 -

Document Sagem DS - Reproduction et divulgation interdites

• On the following lines, the alpha call-up parameters as programmed on the GSE.
The correspondance between alpha call up and GSE parameters is given in appendix 6.4
Menu name Comment Alpha Call
Up
DATE
GMT
FLT
FLCNT
IDENT Documentary parameters
ACTAI
COEEC
ACTYP
FDRIN
GMT
FM
AIR
NH
FLIMOD Flight Mode computation parameters
NP
IAS
RALTF
FLCNT
GMT
FM
GVER
VTAIR
VTGND
UTAIR
G-METER decision parameters for G-Meter report <15>
UTGND
VRTST
LATST
LONST
GLAT
GLON
APMMW
APMCX
APMCZ
APMLV
APMSP
APMTA
APMW
APM APM menu APMD1
APMD2
APMFG
APMIS
APMJP
APMNP
APMTQ
APMZP
BICOD
Maintenance parameters received from external
MAINT. BISEL
equipment
BITRI
CRUISE decision parameters for Cruise Report <02> GMT
FM
IAS
ALT
101-10002-851 Ind. I

- 76 -

Document Sagem DS - Reproduction et divulgation interdites

Menu name Comment Alpha Call

Up
GVER
NHL
NHR
TORQL
TORQR
NP
R02ST
R02TI
R02EC
R02RQ
R02NT
GMT
FM
R03ST
FFL
FFR
TORQL
decision parameters for Exceedance Report
EXCEEDANCE TORQR
<03>
NP
NHL
NHR
IAS
ITTL
ITTR
GMT
MALAR
MARAW
LIGHT
Decision parameters for CMC Report <22>,
CMC FLPAS
<23> and <24>
APMDI
APMFA
TOCWA
APMTE
Engine identification parameters displayed in EiSN
ENG IDENT report <25> EiTM
i=1 or 2 (engine number) EiRGB
EiNST
Engine usage statistic parameters displayed on
EiNFL
ENG STATS report <25>
i=1 or 2 (engine number) EiTRT
EiM(F)(E)RT
Engine LCF component P/N
ENG LCF PN i=1 or 2 (engine number) CijPN
j = 1..9 (LCF component number)
Engine LCF component S/N
ENG LCF SN i=1 or 2 (engine number) CijSN
j = 1..9 (LCF component number)
Engine LCF component total cycle and
remaining life
ENG LCF CY CijTC
i=1 or 2 (engine number)
j = 1..9 (LCF component number)

The displayed information is then:

101-10002-851 Ind. I

- 77 -

Document Sagem DS - Reproduction et divulgation interdites

• ALPHA (Up to 5 characters): Name of alpha call-up parameter (See section 6.4 to get the complete list of
alpha call-up).
• SOURCE (Up to 6 characters): The name of the equipment/system parameter comes from.
• VALUE (Up to 6 characters): The parameter value is displayed with the following rules:
− for a numerical parameter, the engineering value is displayed in the GSE format, with signs + and - .
− for a discrete parameter, its signification is displayed (GSE programmation).
− if one of the displayed parameters is not refreshed for two seconds then the display value filed
contains "XXXXXX".
− if one of the displayed parameters is not valid (bad SSM) for two seconds then the display value field
contains "------".
− set of discrete : in the representation programmed on GSE.
• UNIT (Up to 4 characters): Units of displayed parameter.

5.12.3.3 Status menu

This menu proposes access to DMU BITE status and to the dataloading status.
┌
STATUS MENU

1L █<BITE DMU █ 1R
├
2L █<LOAD DMU █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-17 – MCDU DMU Status Menu

5.12.3.3.1 BITE DMU status menu

This menu displays the current DMU status.
The status includes all DMU maintenance words as described in appendix 6.2.
For each status word, a help menu gives access to messages corresponding to the failures contained in the
maintenance word.
101-10002-851 Ind. I

- 78 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC DMU BITE

1L █ █ 1R
BITE MW CPU├
2L █<00000000 00001000>█ 2R
MW GEN MW PCMCIA├
3L █<00000010 00110000>█ 3R
STIF STEF├
4L █<00000111 00000110>█ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-18 – MCDU DMU Bite Menu

When on the MPC DMU BITE STATUS menu and selecting the PAGE-DOWN key of the MCDU, the DMU
displays the history of the last 40 failures detected and stored in Flash PROM. At this point only the date,
time and bite are displayed. It is then possible to select one of the storage to have access to the content,
which will be displayed with the same format as the DMU STATUS menu
At this point, the same help menus are available for each status word.
┌
MPC DMU BITE
DATE UTC BITE
1L █<150303 123300 00010000>█ 1R
├
2L █<150303 123300 00010000>█ 2R
├
3L █<150303 123300 00010000>█ 3R
├
4L █<150303 123300 00010000>█ 4R
├
5L █<150303 123300 00010000>█ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-19 – MCDU Bite help Menu
101-10002-851 Ind. I

- 79 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.3.2 Load DMU Status menu

The load/unload menu is used for status of all loading operations.
┌
MPC SOFTWARE LOADING

1L █ █ 1R
├
2L █ █ 2R
xxxxxxxxxxxxxxxxxxxxxxxx├
3L █ █ 3R
yyyyyyyyyyyyyyyy ├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN █ 6R

Figure 5-20 – MCDU MPC Software Loading Menu

The XXXXXXXXXXXXX field indicates if a transfer to the DMU is in progress. The two prompts displayed
according with the transfer status are:
• NO TRANSFER IN PROGRESS.
• TRANSFER IN PROGRESS.
The YYYYYYYYYYYYY field is used to display the error occurred during the last transfer. Only one error
message is displayed.
The error messages can be:
• Bad A/C tail: The A/C identification recognised by the AFDAMU is not among the ones of the
diskette (file ACQUIT.MEM). Check if it is the good diskette.
• Bad S/W num: The software reference number written on the diskette (file ACQUIT.MEM) is not
compatible with the resident software or the loaded software. Check your reference
disk.
• Bad retrieval date: The retrieval date of the diskette (written in file ACQUIT.MEM) has expired. Build a
new disk for data retrieval on GSE.
• Not on ground: This operation is not allowed when aircraft is flying.
• Missing: file name: During the OBPM loading, the software has not found the file name on this diskette.
Check your disk.
• Time out: file name: During the OBPM loading, an error has occurred on processor 2 or 3 when file name
has been opened.
• Disk error: During the transfer, a disk error has occurred. Try again or check your diskette or
check if the wiring is in order.
• Invalid disk config.: the PCMCIA card inserted is not valid for loading process. (system file has not a
valid syntax, subdirectory don’t exist, ACQUIT.MEM file does not exist)

5.12.3.4 Data base loading menu

During the OBPM loading, the system displays automatically the OBPM LOADING menu (if MPC selected).
No return action is possible to see another menu, and the MPC LOG-ON action on MCDU performs also the
display of the menu only.
At the start of loading when the disk is valid (correct disk reference), the display changes and becomes:
101-10002-851 Ind. I

- 80 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC DATABASE LOADING

1L █FILE : █ 1R
├
2L █PERFORMED : 000/NNN █ 2R
wait for loading ├
3L █ █ 3R
├
4L █ █ 4R
return key not valid ├
5L █ during loading █ 5R
├
6L █ █ 6R

Figure 5-21 – MCDU Database Start Loading Menu

This menu informs the operator that the flash memory are being cleared.
When flash memory is cleared, the loading process start, then the display becomes:
┌
MPC DATABASE LOADING

1L █FILE : XXXXXX.XXX █ 1R
├
2L █PERFORMED : YYY/NNN █ 2R
loading in progress ├
3L █ █ 3R
├
4L █ █ 4R
return key not valid ├
5L █ during loading █ 5R
├
6L █ █ 6R

Figure 5-22 – MCDU Database Loading in Progress Menu

With this screen, we can know which file is in loading, and how many files have been performed.
At the end of loading with no error, the display changes and becomes:
101-10002-851 Ind. I

- 81 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC DATABASE LOADING

1L █ █ 1R
├
2L █PERFORMED : YYY/NNN █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
load completed ├
5L █ █ 5R
├
6L █<RETURN █ 6R

Figure 5-23 – MCDU Database Loading Success Menu

And when an error has occurred during loading, the display is:
┌
MPC DATABASE LOADING

1L █FILE : XXXXXX.XXX █ 1R
├
2L █PERFORMED : YYY/NNN █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
load failed ├
5L █ █ 5R
├
6L █<RETURN █ 6R

Figure 5-24 – MCDU Database Loading Error Menu

The LOAD/UNLOAD menu will display which error has occurred.

Note that at the end of loading (successful or not), RETURN action is available.
101-10002-851 Ind. I

- 82 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.5 MAINTENANCE menu

The MAINTENANCE menu allows to accede to the Maintenance functions of external equipment.
┌
MAINTENANCE

1L █<AFCS VERSION>█ 1R
├
2L █<RAD COM/NAV DTUE>█ 2R
├
3L █<TCAS █ 3R
├
4L █<PEC/EEC █ 4R
├
5L █<MFC █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-25 – MCDU maintenance menu
Note 1: MFC and PEC/EEC sub-menus will be hidden and inaccessible if the aircraft type is ATR42-300 or
ATR42-320.
Note 2: DTUE sub-menu will be hidden and inaccessible if Ethernet activation discrete is not grounded or if
GSE limit "DTUE MCDU screen enabled" is set to zero (see §6.2.5).

5.12.3.5.1 AFCS
The AFCS menu provides 4 sub-menus. The aim of the first three sub-menus is to help troubleshooting the
AFCS. They will guide the operator in identifying the reason of a failure. They work the same way and use
the same screens, just the displayed help changes. The last one allows to perform an automatic or manual
decoding of FFS.
┌
AFCS

1L █<GENERAL T/S █ 1R
├
2L █<ADU MESSAGES █ 2R
├
3L █<GND MAINT TEST █ 3R
├
4L █<FLIGHT FAULT SUMMARY █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-26 – MCDU AFCS menu

5.12.3.5.1.1 Troubleshooting help

This function is used by the three first choices.

101-10002-851 Ind. I

- 83 -

Document Sagem DS - Reproduction et divulgation interdites

It consists of the following steps :

1. Displaying the final message or the question (defined in the DESCRIPTION table in the corresponding
Excel file, see section 6.6.1) asked to the operator on the first(s) screen(s) of a page followed by a page
allowing to go to a choices page or to go back to previous question.
┌
GENERAL TROUBLESHOOTI1/2

1L █PWR AFCS & WAIT 3 MIN █ 1R
├
2L █MSG ON MDU ? █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R
↑↓

┌
GENERAL TROUBLESHOOTI2/2

1L █<SEE CHOICES █ 1R
├
2L █ █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-27 – MCDU troubleshooting question pages
2. Displaying the possible answers (choices) defined in the CHOICE table in the corresponding Excel file on
the choices page(s) (see section 6.6.1.2).
┌
GENERAL TROUBLESHOOTI1/1

1L █<ALT SEL ----FT █ 1R
├
2L █<DASHED LINE (------) █ 2R
├
3L █<NOTHING █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-28 – MCDU troubleshooting choices page
3. Waiting until the operator chooses an answer or goes back to the previous page using RETURN (go back to step 1).
4. Go to the next page depending on the chosen answer (link to the next page defined in the CHOICE table)
101-10002-851 Ind. I

- 84 -

Document Sagem DS - Reproduction et divulgation interdites

For ADU messages, one of the choice can lead to a FFS data decoding with a manual input (see next
section).

5.12.3.5.1.2 FFS data decoding

It consists of the following steps:

1. Reading the FFS hexadecimal data on the ASCB bus or asking the operator to type it.
┌
FLIGHT FAULT SUMMARY

1L █<AUTOMATIC READING █ 1R
├
2L █<MANUAL INPUT █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-29 – MCDU FFS automatic/manual menu
┌
FLIGHT FAULT SUMMARY

1L █← 00E0 0104 0000 0000 █ 1R
├
2L █← 0000 0000 000C 0000 █ 2R
├
3L █← 0000 0000 0000 █ 3R
├
4L █← 0000 0700 0000 █ 4R
├
5L █<VALIDATE █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-30 – MCDU FFS manual input
101-10002-851 Ind. I

- 85 -

Document Sagem DS - Reproduction et divulgation interdites

┌
DADC TEST

1L █ENTER DADC BIT DEF. AS █ 1R
DISPLAYED ON ADU ├
2L █ █ 2R
├
3L █← 0000 03D0 █ 3R
├
4L █<VALIDATE █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-31 – MCDU FFS manual input for ADU
2. Decoding FFS to extract the list of choice code to display (see section 6.6.1.4)
3. Displaying an instruction message and proposing to see the choices
┌
FLIGHT FAULT SUMMARY 1/2

1L █CHK ALL FLAGS BEFORE █ 1R
REPLACE / REPAIR ├
2L █ █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

┌
FLIGHT FAULT SUMMARY 2/2

1L █<SEE CHOICES █ 1R
├
2L █ █ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-32 – MCDU FFS instruction pages
4. Display the corresponding choices (found in the FFS table of the AFCS Excel file, see section 6.6.1.3).
101-10002-851 Ind. I

- 86 -

Document Sagem DS - Reproduction et divulgation interdites

┌
FLIGHT FAULT SUMMARY 1/1

1L █<SERIAL I/O FAIL █ 1R
├
2L █<8.33 REALTIME LOOP FAIL█ 2R
├
3L █ █ 3R
├
4L █ █ 4R
├
5L █ █ 5R
├
6L █<RETURN PRINT*█ 6R

Figure 5-33 – MCDU FFS choices page
5. When the operator selects one of these choices, display the corresponding page (link to the next page
defined in the FFS table)
5.12.3.5.2 VERSION
This page presents the table version numbers for each table used in one of the maintenance function.
┌
VERSION AFCS
V 1.0.4
1L █VERSION MFC █ 1R
V 1.0.3
2L █VERSION PECEEC CODE █ 2R
V 1.0.1
3L █VERSION RADIO █ 3R
V 1.0.3
4L █VERSION TCAS █ 4R
V 1.0.2
5L █VERSION TRIM █ 5R
V 1.0.1
6L █<RETURN PRINT*█ 6R

Figure 5-34 – MCDU table version page

5.12.3.5.3 RAD COM/NAV

An extensive self test diagnostic routine can be started from the dedicated control unit of the following
systems:
VHF 22A OR 22C
VOR VIR 32
DME 42
ADF 60
ATC TDR90 OR TDR94D
101-10002-851 Ind. I

- 87 -

Document Sagem DS - Reproduction et divulgation interdites

This function will allow to display on the MCDU the maintenance messages associated to the diagnostic
code displayed on the control unit in self test diagnostic routine.
┌
RAD COMM/NAV

1L █<ATC TDR90 ATC TDR94D>█ 1R

2L █<VOR VIR32 █ 2R

3L █<DME 42 █ 3R

4L █<ADF 60 █ 4R

5L █<VHF 22 █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-35 – MCDU radio com/nav menu
For this, in the « Rad Comm / Nav» menu select the control unit in maintenance and enter through the
keyboard the diagnostic code displayed on the control unit selected.
The program gets the code and finds out the corresponding description and troubleshooting in the radio
COM/NAV Excel file, see section 6.6.2).
┌
RAD COMM/NAV
DIAGNOSTIC CODE:
1L █←02 █ 1R

2L █5V ABOVE LIMIT █ 2R

3L █TROUBLESHOOTING █ 3R
RAI 1RC1/2 XMTR VHF1/2
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-36 – MCDU RAD COM/NAV page
101-10002-851 Ind. I

- 88 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.5.4 DTUE
The DTUE page displays the fail status and transmission status of DTUE.
┌
DTUE

1L █ █ 1R
DTUE STATUS:
2L █NORMAL █ 2R

3L █ █ 3R
RF LAMP STATUS:
4L █ON / ENABLED █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-37 – MCDU DTUE page
The only message associated to this screen is:
• NOT ALLOWED: invalid key (LSK or any other key).
The possible DTUE status are “NORMAL”, “FAULT” and “CAUTION”.
The possible RF lamp status are ‘ON / ENABLED”, “OFF / DISABLED”, “ON / TRANSMISSION”.

5.12.3.5.5 PEC/EEC
The PEC/EEC menu allow to read code and proceed the trim procedure of one of the two PEC or EEC,
depending on which is selected through an external switch.
┌
EEC

1L █<TRIM EEC1 EEC2 TRIM>█ 1R

2L █<CODE EEC1 EEC2 CODE>█ 2R

3L █ PEC █ 3R
NOT SELECTED
4L █ TRIM PEC1 PEC2 TRIM █ 4R

5L █ CODE PEC1 PEC2 CODE █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-38 – MCDU PEC/EEC menu
The only message associated to this screen is:
• NOT ALLOWED: invalid key (LSK or any other key).

5.12.3.5.5.1 TRIM procedure

The aim of this function is to help the operator to process the PEC or EEC trim. The page shows step by
step the TRIM procedure and guide the operator, accordingly to status sent by PEC or EEC. Various
parameter are also displayed.
101-10002-851 Ind. I

- 89 -

Document Sagem DS - Reproduction et divulgation interdites

List of the parameters related to the EEC (Electronic Engine Control) TRIM:
• EEC: Engine type, possible values are:
• STD
• 127
• 127 E/M
• 127 F/M
• BLEED: bleed valve configuration, possible values are:
• OFF
• ON
• HFL: High Flow
• PMGT: Power Management Selector position, possible values are:
• T/O: Take OFF
• MCT: Maximum Continuous
• CLB: Climb
• CRZ: Cruise
• PLA: Power Lever position, possible values are:
• T/O: Take OFF
• OUT
• TRIM SW: TRIM Switch State, possible values are:
• OFF
• ACTIVE
• FDEP: value that contains the coded parameters on 4 digits
• MSG: Message sequence to help the trim procedure. The message changes after operator processing.
The sequence of messages is:
• PMGT IN T/O RANGE
• BLEED OFF
• PLA T/O
• PRESS TRIM SW
• TRIM IN PROGRESS
• TRIM OK this display lasts 5 seconds
• RELEASE TRIM SW
• PLA GI
• TRIM COMPLETED
101-10002-851 Ind. I

- 90 -

Document Sagem DS - Reproduction et divulgation interdites

┌
EEC1 TRIM

1L █EEC :STD BLEED :ON █ 1R

2L █PMGT :CRZ PLA :OUT █ 2R

3L █TRIM SW :OFF █ 3R

4L █MSG :PMGT IN T/O RANGE █ 4R

5L █FDEP CODE : 0014 █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-39 – MCDU EEC TRIM pages
List of the parameters related to the PEC (Propeller Electronic Control ) TRIM:
• PLA: Power Lever position, possible values are:
• T/O: Take OFF
• FI: Flight Idle
• OUT
• PMGT: Power Management Selector position, possible values are:
• T/O: Take OFF
• OUT
• CRZ: Cruise
• TRIM SW: TRIM Switch State, possible values are:
• OFF
• ACTIVE
• FDEP: value that contains the coded parameters on 4 digits
• MSG :Message sequence to help the trim procedure. The message changes after operator processing.
The sequence of messages is:
• PMGT IN CRZ (2)
• PLA T/O
• PRESS TRIM SW
• TRIM IN PROGRESS
• TRIM OK AT T/O this display lasts 5 seconds
• RELEASE TRIM SW
• PLA FI
• PRESS TRIM SW
• TRIM IN PROGRESS
• TRIM OK AT FI this display lasts 5 seconds
• RELEASE TRIM SW
• PLA GI
101-10002-851 Ind. I

- 91 -

Document Sagem DS - Reproduction et divulgation interdites

• PMGT IN T/O
• TRIM COMPLETED
┌
PEC1 TRIM

1L █PMGT :T/O PLA :OUT █ 1R

2L █TRIM SW :OFF █ 2R

3L █MSG :PMGT IN CRZ (2) █ 3R

4L █FDEP CODE : 0014 █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-40 – MCDU PEC TRIM pages

5.12.3.5.5.2 CODE reading

The aim of this function is to display the message matching the error code sent by the EEC (or PEC). This
messages are found in the PEC/EEC Excel file (see section 6.6.3).
List of the parameters related to the EEC (Electronic Engine Control) CODE:
• EEC: Engine type, possible values are:
• 121A (ATR42-400)
• 124B (ATR72-200)
• 127 (ATR72-210)
• 127E/M (ATR42-500)
• 127F/M (ATR72-500)
┌
PEC MAINT CODE

1L █CODE: 01 █ 1R

2L █DESC: █ 2R

3L █MEMORY BEGINNING █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

101-10002-851 Ind. I

- 92 -

Document Sagem DS - Reproduction et divulgation interdites

┌
EEC MAINT CODE

1L █ ENGINE PW127E/M █ 1R

2L █ █ 2R
CODE: 63
3L █ █ 3R
DESC:
4L █ █ 4R
TORQUE SENSOR COIL NO.1
5L █HIGH TORQUE █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-41 – MCDU code reading pages

5.12.3.5.6 TCAS
TCAS function allows the operator to display maintenance data recorded during the flight.
The maintenance data displayed are the alarm message as well as the troubleshooting for each bit activated
in received words from TCAS ; the texts are to be found in the TCAS Excel file (see section 6.6.4).
┌
TCAS

1L █MAINTENANCE MESSAGE █ 1R
BEAM STEERING NETWORK
2L █ █ 2R
TROUBLESHOOTING
3L █RAI 1SG TCAS █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-42 – MCDU TCAS page
The message associated to this screen are:
• NOT ALLOWED: invalid key (LSK or any other key),
• TRANSFERT IN PROGRESS: the TCAS fault words are being downloaded,
• NO FAILURE: the TCAS reports no failure,
• COMMUNICATION ERROR / RESET TCAS POWER SUPPLY / AND TRY AGAIN: the download of
TCAS fault words fails, the TCAS need to be reset and then the operator must exit the TCAS page using
the LSK6 (RETURN) and then enter the page again.

5.12.3.5.7 MFC
Memory selection:
101-10002-851 Ind. I

- 93 -

Document Sagem DS - Reproduction et divulgation interdites

When MFC maintenance software is entered, the operator may select memory to be displayed or memory to
be erased.
┌
MFC MENU

1L █<BASIC MEMORY █ 1R

2L █<FLT FAULT MEMORY █ 2R

3L █<MAINT MEMORY ERASING █ 3R

4L █*COPY TO PCMCIA █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-43 –MCDU MFC main menu
System selection:
After memory selection, the corresponding page appears on MCDU :
┌
BASIC MEMORY

1L █<WOW & LG FLT_CTL>█ 1R

2L █<DOORS MISC1>█ 2R

3L █<BOOTS MISC2>█ 3R

4L █<NAV MISC3>█ 4R

5L █<BRK MFC/MISC4>█ 5R

6L █<RETURN PRINT*█ 6R

┌
FLT FAULT MEMORY

1L █<WOW & LG FLT_CTL>█ 1R

2L █<DOORS MISC1>█ 2R

3L █<BOOTS MISC2>█ 3R

4L █<NAV MISC3>█ 4R

5L █<BRK MFC/MISC4>█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-44 –MCDU MFC system menus

The operator must then select the system prior to check recorded faults (Recorded faults are
displayed on several screens if necessary)
101-10002-851 Ind. I

- 94 -

Document Sagem DS - Reproduction et divulgation interdites

For the flight fault memory part all the faults for the selected system will be displayed from flight 0 to
flight n-8. The text of the fault are listed in the MFC Excel file (see section 6.6.5)
Scrolling through faults and flights can be done by pressing UP and DOWN key.
A print of faults is possible if a printer is connected.
┌
BASIC MEMORY 1/2
WOW & LANDING GEAR
1L █ █ 1R
5-NG SEC DNLK PROX SW
2L █FAIL 32.61 12GB█ 2R

3L █ █ 3R
11-NG WOW 2 PROX SW
4L █FAIL 32.62 52GB█ 4R

5L █ DOWN*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-45 –MCDU MFC fault page
Memory erasing:
Operator can select erasing of basic or flight fault memory.
┌
MAINT MEMORY ERASING

1L █ █ 1R
BASIC MEMORY ERASING
2L █*YES NO*█ 2R

3L █ █ 3R
FLIGHT MEMORY ERASING
4L █*YES NO*█ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-46 – MCDU MFC memory erasing page
The messages associated to this screens are:
• NOT ALLOWED: invalid key (LSK or any other key),
• MFC CONNECTION TIME OUT OR ERROR: communication error with MFC.
101-10002-851 Ind. I

- 95 -

Document Sagem DS - Reproduction et divulgation interdites

Copy to PCMCIA :
The operator can select this capability in order to download all fault data from the MFC and copy these
faults on the PCMCIA disk. MFC fault words storage on PCMCIA disk is detailed in the chapter 5.16.7.
As the procedure may take some minutes, the MCDU screen will change during the download. All
sub-menus will temporarily be inaccessible and the return button will change as ‘Return&abort”, to
allow the operator to return to the previous MCDU screen and stop the download of fault words from
the MFC.
┌
MFC MENU

1L █ BASIC MEMORY █ 1R

2L █ FLT FAULT MEMORY █ 2R

3L █ MAINT MEMORY ERASING █ 3R

4L █*COPY TO PCMCIA █ 4R
READING FLIGHT MEMORY
5L █ █ 5R

6L █<RETURN&ABORT PRINT*█ 6R

Figure 5-47 –MCDU MFC main menu during a copy to PCMCIA
The messages associated to this screens are:
• NOT ALLOWED: invalid key (LSK or any other key),
• CONNECTION INITIATED: beginning of communication with the MFC.
• READING MFC VERSION: reading of the version of the MFC.
• READING BASIC MEMORY: reading of the basic memory of the MFC.
• READING FLIGHT MEMORY: reading of the flight memory of the MFC.
• WRITING IN PROGRESS: writing of MFC fault words to PCMCIA card.
• MFC DATA STORAGE DONE: The storage of fault words to PCMCIA is finish.
• ERROR COMMUNICATION: Error timeout when communication with the MFC.
• ERROR WRITING PCMCIA: Error when writing data on PCMCIA card.
• NO PCMCIA AVAILABLE: There is no PCMCIA disk available. No writing possible.
101-10002-851 Ind. I

- 96 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6 QAR/DAR/SAR menu

When this menu is selected, 5 types of pages are proposed:
DAR PCM
QAR PCM
SAR summary
SAR Recording
SAR manual request

┌
MPC QAR/DAR/SAR

1L █<QAR PCM █ 1R

2L █<DAR PCM █ 2R

3L █<SAR SUMMARY █ 3R

4L █<SAR RECORDING █ 4R

5L █<SAR MANUAL REQ. █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-48 – MCDU PCM QAR/DAR menu

The whole menu is in white characters except the RETURN and PRINT.
The only message associated to this screen is
NOT ALLOWED: invalid key (LSK or any other key).
101-10002-851 Ind. I

- 97 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.1 QAR PCM

This page enables the operator to display the QAR PCM output data by entering the sub-frame/word number
of the desired data.
Three pages (6 words) are possible (values are kept when a new page is selected).
Example of display:
┌
MPC PCM QAR 1/3
sf/word hex dec oct
1L █← 01 0012: 0CB 0203 0313█ 1R
bit 12-1: 000011001011
2L █ █ 2R
sf/word hex dec oct
3L █← LL LLLL █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-49 – MCDU PCM QAR page (example)

The data value is displayed in 4 ways:

• On the first line of display the raw value is in hexa format (3 characters), decimal (4 characters), and octal
(4 characters).
• On the second line of display the raw value is represented in binary format (12 characters).

Range of data:
• SF: 1 to 4
• WORD: 1 to 1024 (Depending upon the size of the QAR frame transmitted by the AFDAU to the DMU)

The messages that are associated to this screen are

• NOT ALLOWED: invalid key (LSK or any other key).
• INVALID ENTRY: data set greater than the maximum of data sets available.
101-10002-851 Ind. I

- 98 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.2 DAR PCM

This page enables the operator to display the DAR PCM output data by entering the subframe/word number
of the desired data.
Three pages (6 words) are possible (values are kept when a new page is selected).
Example of display:
┌
MPC PCM DAR 1/3
sf/word hex dec oct
1L █← 01 0012: 0CB 0203 0313█ 1R
bit 12-1: 000011001011
2L █ █ 2R
sf/word hex dec oct
3L █← LL LLLL █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-50 – MCDU PCM DAR page (example)

The data value is displayed in 4 ways:

• On the first line of display the raw value is in hexa format(3 characters), decimal (4 characters), and octal (4
characters).
• On the second line of display the raw value is represented in binary format (12 characters).

Range of data:
• SF: 1 to 4
• WORD: 1 to 2048 (defined on GSE, see its user’s manual [S04])

The messages that are associated to this screen are:

• NOT ALLOWED: invalid key (LSK or any other key).
• INVALID ENTRY: data set greater than the maximum of data sets available.
101-10002-851 Ind. I

- 99 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.3 SAR summary

This menu is selected when LSK 3L of SAR menu was depressed.
This menu shows a summary of SAR state for the four functions (SAR1 SAR4). It is only a menu of
display.
┌
MPC SAR SUMMARY 1/4

1L █ data recording █ 1R

2L █ █ 2R
generated : 015
3L █ █ 3R
dumped : 007
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC SAR SUMMARY 2/4

1L █extended troubleshooting█ 1R

2L █ █ 2R
generated : 010
3L █ █ 3R
dumped : 000
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC SAR SUMMARY 3/4

1L █ event recording █ 1R

2L █ █ 2R
last retrieval : may24
3L █number of flights: 013 █ 3R
number of events : 014
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

101-10002-851 Ind. I

- 100 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC SAR SUMMARY 4/4

1L █extended data recording █ 1R

2L █ █ 2R

3L █ █ 3R
generated : 010
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-51 – MCDU SAR summary page (example)

For the event recording (page 3/4), the date of last retrieval is used as a reference to display the number of
flights since that moment as well as the number of programmed events that have occurred.
To detail these informations, it is then necessary to get the history of SAR stored records with next screen.
The whole menu is in white characters except the RETURN and PRINT.
If the PCMCIA disk is not inserted the following screen is displayed :
┌
MPC SAR SUMMARY 4/4

1L █extended data recording █ 1R

2L █ █ 2R

3L █ █ 3R
generated : xxx
4L █ █ 4R

5L █ █ 5R
NO MEDIA LOADED
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-52 – MCDU SAR summary page 4
101-10002-851 Ind. I

- 101 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.4 SAR RECORDING

┌
MPC SAR RECORDING

1L █<DATA RECORDING █ 1R

2L █<EXTENDED TROUBLESHOOT █ 2R

3L █<EVENT RECORDING █ 3R

4L █<EXTENDED DATA RECORDING█ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-53 – MCDU SAR recording page

This menu is only a selection menu.

The whole menu is in white characters except the RETURN and PRINT.
The only message associated to this screen is:
• NOT ALLOWED: invalid key (LSK or any other key).

5.12.3.6.4.1 Data recording

When this menu is selected, it is possible to have the history of the last records of data recording function.
This menu is for display only. No action can be initiated from this menu, except print the SAR history.
┌
MPC DATA RECORD 1/4
leg s code date utc
1L █ 0009240 bytes █ 1R
000 1 0200 MAY23 163214
2L █ 0001024 bytes █ 2R
000 2 0125 MAY23 155824
3L █ 0003212 bytes dmp █ 3R
001 1 0101 MAY22 173256
4L █ 0012344 bytes dmp █ 4R
001 3 0101 MAY22 173256
5L █ 0006532 bytes dmp █ 5R
04 2 0200 MAY20 072112
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-54 – MCDU SAR data record page

The whole menu is in white characters except the RETURN and PRINT.
On this menu is displayed:
• the flight leg when the trigger occurred,
• the data set that was recorded,
101-10002-851 Ind. I

- 102 -

Document Sagem DS - Reproduction et divulgation interdites

• the code number of the trigger (given by GSE),

• the date of the trigger,
• the UTC at the beginning of the trigger : Hours/Minutes/Seconds (hhmmss),
• the length of the record in bytes.
• the status of download (see 5.16.4.2): either dmp or nothing,
Only the last 20 records can be displayed (4 successive screens).
The only message associated to this screen is:
• NOT ALLOWED: invalid key (LSK or any other key).

5.12.3.6.4.2 Extended troubleshooting

When this menu is selected, it is possible to have the history of the last records of extended troubleshooting
function. This menu is for display only. No action can be initiated from this menu, except print the SAR
history.
┌
MPC EXT TROUBLE 1/4
leg s code date utc
1L █ 0009240 bytes █ 1R
000 1 0200 MAY23 163214
2L █ 0001024 bytes █ 2R
000 2 0125 MAY23 155824
3L █ 0003212 bytes dmp █ 3R
001 1 0101 MAY22 173256
4L █ 0012344 bytes dmp █ 4R
001 3 0101 MAY22 173256
5L █ 0006532 bytes dmp █ 5R
004 2 0200 MAY20 072112
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-55 – MCDU SAR extended troubleshooting page

The whole menu is in white characters except the RETURN and PRINT.
On this menu is displayed:
• the flight leg when the trigger occurred,
• the data set that was recorded,
• the code number of the trigger (given by GSE),
• the date of the trigger,
• the UTC at the beginning of the trigger : Hours/Minutes/Seconds (hhmmss),
•
• the length of the record in bytes. This is the length of both pre-event record and real time record.
• the status of download (see 5.16.4.2): either dmp or nothing,
101-10002-851 Ind. I

- 103 -

Document Sagem DS - Reproduction et divulgation interdites

Only the last 20 records can be displayed (4 successive screens).

The only message associated to this screen is
• NOT ALLOWED: invalid key (LSK or any other key).

5.12.3.6.4.3 Event recording

When this menu is selected, it is possible to have the history of records of event recording function. This
menu is for display only. No action can be initiated from this menu, except print the SAR history.
┌
MPC EVENT RECORD 1/4
leg event date utc
1L █ █ 1R
000 20 MAY23 163214
2L █ █ 2R
000 12 MAY23 155824
3L █ █ 3R
001 10 MAY22 173256
4L █ █ 4R
003 10 MAY20 173256
5L █ dmp █ 5R
004 02 MAY20 072112
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-56 – MCDU SAR event recording page

The whole menu is in white characters except the RETURN and PRINT.
On this menu is displayed:
• the flight leg when the trigger occurred,
• the event number of the trigger (given by GSE),
• the date of the trigger,
• the UTC of the trigger : Hours/Minutes/Seconds (hhmmss),
• the status of download (see 5.16.4.2): either dmp or nothing.
Only the last 20 event can be displayed (4 successive screens)
The only message associated to this screen is
• NOT ALLOWED: invalid key (LSK or any other key).
101-10002-851 Ind. I

- 104 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.4.4 Extended data recording

When this menu is selected, it is possible to have the history of the last records of extended data recording
function. This menu is for display only. No action can be initiated from this menu, except print the SAR
history.
┌
MPC EXT DATA RECORD 1/4
leg s code date utc
1L █ 0000009240 bytes █ 1R
000 1 0200 MAY23 163214
2L █ 0000001024 bytes █ 2R
000 2 0125 MAY23 155824
3L █ 0000003212 bytes █ 3R
001 1 0101 MAY22 173256
4L █ 0000012344 bytes █ 4R
001 3 0101 MAY22 173256
5L █ 0000006532 bytes █ 5R
004 2 0200 MAY20 072112
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-57 – MCDU SAR extended data recording page
The whole menu is in white characters except the RETURN and PRINT.
On this menu is displayed:
• the flight leg when the trigger occurred,
• the data set that was recorded,
• the code number of the trigger (given by GSE),
• the date of the trigger,
• the UTC at the beginning of the trigger : Hours/Minutes/Seconds (hhmmss),
• the length of the record in bytes. This is the length of both pre-event record and real time record.
Only the last 20 event can be displayed (4 successive screens)
The only message associated to this screen is
• NOT ALLOWED: invalid key (LSK or any other key).
If the PCMCIA disk is not inserted the following screen is displayed :
┌
MPC EXT DATA RECORD 1/1
leg s code date utc
1L █ █ 1R

2L █ █ 2R

3L █ █ 3R

4L █ █ 4R

5L █ █ 5R
NO MEDIA LOADED
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-58 – MCDU SAR extended data recording page
101-10002-851 Ind. I

- 105 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.6.5 SAR manual request

It is possible to record manually any of the data sets of data recording, extended troubleshooting or extended
data recording.
In any case, the recording begins with the MCDU action "START" and ends with MCDU action "STOP".

┌
MPC SAR MANUAL REQ. 1/2

1L █ data recording █ 1R
channel 1
2L █*START STOP █ 2R
channel 2
3L █*START STOP █ 3R
channel 3
4L █*START STOP █ 4R
channel 4
5L █*START STOP █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC SAR MANUAL REQ. 2/2

1L █extended troubleshooting█ 1R
channel 1
2L █*START STOP █ 2R
channel 2
3L █*START STOP █ 3R
channel 3
4L █*START STOP █ 4R
channel 4
5L █*START STOP █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-59 – MCDU SAR manual request page

Only channels which have been programmed on the GSE and which are not automatically running can be
started.
If a channel is not programmed or it has been started automatically, then no “*” is displayed in front of
START and STOP on the screen and both START and STOP words are displayed in green colour.
If a channel is programmed and is not running, then the star is displayed in front of START word. START is
displayed in cyan and STOP in green colour.
Once this channel is manually started, then the “*” is switched in front of the STOP word. START becomes
green and STOP becomes cyan.
Once this channel is manually stopped, then the display switches back to the initial configuration.
The messages that are associated to this screen are:
• NOT ALLOWED: invalid key (LSK or any other key).
101-10002-851 Ind. I

- 106 -

Document Sagem DS - Reproduction et divulgation interdites

5.12.3.7 PCMCIA menu

This menu gives access to pages related to the MPC internal PCMCIA card.
When this menu is selected , four pages are proposed:
• Disk identification and status
• Disk directory and files display
• QAR recording status on PCMCIA
• DAR recording status on PCMCIA
┌
MPC PCMCIA MENU

1L █<DISK IDENT █ 1R

2L █<DISK DIRECTORY █ 2R

3L █<DISK DAR RECORDING █ 3R

4L █<DISK QAR RECORDING █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-60 – MCDU PCMCIA Menu

The whole menu is in white characters except the RETURN and PRINT.
The only message associated to this screen is:
• NOT ALLOWED: invalid key (LSK or any other key).

Note : history of SAR records is displayed in "SAR/DAR/QAR" pages (see chapter 5.12.3.6.4).

5.12.3.7.1 MPC Disk ident

This page displays the PCMCIA ident of the disk including:
• P/N : PCMCIA standard part number. Display format: 2 ASCII lines.
• S/N : disk serial number. Display format: 8 decimal digits.
• Disk status word: internal DMU status word that contains detected failures and status of the disk.
Display format 8 hexa decimal digits.
The key next to the maintenance word gives access to a help screen that displays messages in clear
English according to the content of the status word.
Also, the free/total space on the disk is displayed.
101-10002-851 Ind. I

- 107 -

Document Sagem DS - Reproduction et divulgation interdites

Following is an example of disk ident page:

┌
DISK IDENT

1L █P/N : █ 1R
CALLUNA TECHNOLOGY C
2L █ T80MC █ 2R
S/N :
3L █ 00002750 █ 3R
DISK STATUS WORD
4L █ : 00000000 >█ 4R
FREE/TOTAL SPACE(kbyte)
5L █ : 0082652/0128940 █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-61 – MCDU Disk Ident Menu

In case of no PCMCIA disk inserted in the unit, then all display fields are filled with « --- ».
Definition of the disk status word with associated displayed message is to be found in section 6.3.4.

5.12.3.7.2 MPC disk directory

This page enables the operator to visualise the disk content and go through all directories to list files but also
to display the content of those files.
The first line of the screen contains the actual disk path.
Note that backslash ‘\’ is replaced by a slash ‘/’. In addition all characters which can not be displayed on
MCDU (not ISO 5 characters) are displayed as « ».
Directory offset is the number of directory entries (subdirectories, files) prior to the first one displayed on the
screen. The operator can scroll through the entries by using the UP and DOWN keys or by entering an offset
number.
If an entry is a directory, a ‘<‘ appears on the left side of the screen and depressing this key will change the
path to this new directory. The ‘<..’ corresponds to a return to the previous directory (=DOS command ‘CD..’).
If an entry is a file name, then a ‘>‘ appears on the right side of the screen. The operator depresses this key
to visualise the content of the file.
The file can be scrolled through using UP and DOWN keys but also entering the file offset.
The line above return line is used as a status line. Following messages can be displayed on this line:
• CHANGING DIRECTORY: DMU is executing a directory change request.
• READ DIRECTORY: DMU is scanning directory information.
• OPENING FILE: DMU is opening a specific file.
• FILE OPENED: End of open file action.
• READ IN PROGRESS: DMU is reading file data.
• DATA REFRESHED: Display is refreshed after a requested operation.
• NO MEDIA LOADED: No PCMCIA disk is inserted or disk is removed.
101-10002-851 Ind. I

- 108 -

Document Sagem DS - Reproduction et divulgation interdites

Note: The displayed information is only refreshed when entering the screen, or when requesting a specific
action as changing the display offset or display of a specific file.
Note: For readability purpose, colours of this screen do not follow general display rules defined in chapter
5.12.2.3
Note: It is not possible to clear the offset number by pressing CLR key.
Following is an example of disk directory display page:
┌
PATH: /
DIR OFFSET UP*
1L █*0000 █ 1R

2L █SOFTWARE.cnf 11MAY 1133█ 2R
0000012500 bytes
3L █<D-ABXA.REC 15MAY 2110█ 3R
<DIR>
4L █ <NO MORE FILES> █ 4R

5L █ DOWN*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-62 – MCDU PCMCIA Directory Example
Pressing the 3L LSK will change the displayed path and leads to following screen being displayed:
┌
PATH: /D-ABXA
DIR OFFSET
1L █*0000 UP*█ 1R

2L █REC00000.DAT 16MAY 1215>█ 2R
0000135250 bytes
3L █REC00001.DAT 17MAY 1420>█ 3R
0000140210 bytes
4L █ <NO MORE FILES> █ 4R

5L █ DOWN*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-63 – MCDU Sub-Directory Example
101-10002-851 Ind. I

- 109 -

Document Sagem DS - Reproduction et divulgation interdites

Pressing the 2R LSK will display the associated file and leads to following screen being displayed:
┌
FILE: REC00000.DAT
FILE OFFSET
1L █*00000000 UP*█ 1R
0247 0000 0000 0000 0000
2L █0000 0000 0000 0000 0000█ 2R
0000 0000 0000 0000 0000
3L █0000 0000 0000 0000 0000█ 3R
0000 0000 0000 0000 0000
4L █0000 0000 0000 0000 0000█ 4R
0000 0000 0000 0000 0000
5L █*HEX(ASCII) DOWN*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-64 – MCDU Data in Recorded File Example

Pressing the LSK 5L on this menu, the display mode is changed from hexadecimal to ASCII.
In addition, depressing the key 5L on the disk directory menu gives access to the following disk command
menu: (Remark : This screen access is protected by a password)

┌
MPC DISK COMMANDS
PATH: /DAR
1L █ █ 1R
DIR/FILE NAME
2L █*LLLLLLLLLLLL █ 2R

3L █*DELETE RMDIR*█ 3R

4L █*DISK FORMAT MKDIR*█ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-65 – MCDU Disk Commands Menu

After entering a file name (contained in the current directory) in the scratchpad and depressing the DIR/FILE
NAME key, the operator can delete the specified file from the disk by depressing the DEL key.
To create or remove a directory on the disk, the operator enters the directory name in the scratchpad,
depresses the DIR/FILE NAME key and uses RMDIR or MKDIR key to remove or create the specified
directory.
Depressing the FORMAT key will DOS format the disk.

5.12.3.7.3 MPC Disk DAR recorder

This page displays the status of the MPC disk used as a DAR recorder and also gives the possibility to start
or stop the DAR recording on this disk.
It gives the name of the recording directory, the length of all files recorded in this directory and the size of the
101-10002-851 Ind. I

- 110 -

Document Sagem DS - Reproduction et divulgation interdites

DAR record partition on this disk. The length of the files and the partition size are given in Kbytes.
It displays:
• The status of the recording (STOP, RUN, WAIT, ERROR).
• The name of the file being currently used to record the DAR data along with the size of this file.

┌
MPC DISK DAR RECORDING

1L █DAR RECORD STATUS: RUN █ 1R

2L █DIRECTORY: 000000.REC █ 2R
FILENAME : REC00001.DAT
3L █ █ 3R
LENGTH FILE/DIR/MAX(kb)
4L █0012450/0012450/0250000 █ 4R

5L █ DAR = RUNNING STOP*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-66 – MCDU DAR Recording Menu

Each depression of the key LSK5R shall toggle the running/stopped status of the DAR:

5L █ DAR = STOPPED START*█ 5R

5L █ DAR = RUNNING STOP*█ 5R

The DAR manual stop is possible only if the start was manual.
The DAR manual start is possible only if a PCMCIA card is in the unit.

5.12.3.7.4 MPC Disk QAR recorder

This page displays the status of the MPC disk used as a QAR recorder and also gives the possibility to start
or stop the QAR recording on this disk.
It gives the name of the recording directory, the length of all files recorded in this directory and the size of the
QAR record partition on this disk. The length of the files and the partition size are given in Kbytes.
It displays:
• The status of the recording (STOP, RUN, WAIT, ERROR).
• The name of the file being currently used to record the QAR data along with the size of this file.
101-10002-851 Ind. I

- 111 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC DISK QAR RECORDING

1L █QAR RECORD STATUS: RUN █ 1R

2L █DIRECTORY: ATR002.QAR █ 2R
FILENAME : REC00005.DAT
3L █ █ 3R
LENGTH FILE/DIR/MAX(kb)
4L █0012450/0012450/0250000 █ 4R

5L █ QAR = RUNNING STOP*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-67 – MCDU QAR Recording Menu

Each depression of the key LSK5R shall toggle the running/stopped status of the QAR.
The QAR manual stop is possible only if the start was manual.
The QAR manual start is possible only if a PCMCIA card is in the unit.

5.12.3.8 Identifications pages

These pages enable to display the various MPC identifications and indicate the A/C configuration recognised
by the MPC.
The first page displays:
- On upper part: the P/N of the MPC plus the AFDAU and DMU operational software top level
identifications.
- On lower part: the A/C installation or configuration recognised by the MPC. The following information is
displayed from top to bottom:
The configuration of the Flight Data Recording System:
ATR V0 : V0 standard dataframe
ATR V1 : V1 standard dataframe
ATR V2 : V2 standard dataframe
ATR V2A : V2A standard dataframe
ATR V2B : V2B standard dataframe
ATR V3 : V3 dataframe (V2B dataframe with additional parameters, 256 wps)
The Aircraft Type:
ATR42300 : ATR 42-300 (PW120 engine)
ATR42320 : ATR 42-320 (PW121 engine)
ATR42400 : ATR 42-400 (PW121A engine)
ATR42500 : ATR 42-500 (PW127E/M engine)
ATR72200 : ATR 72-200 (PW124 engine)
ATR72210 : ATR 72-210 (PW127 engine)
ATR72500 : ATR 72-500 (PW127F/M engine)
Additional A/C configuration information that is useful to determine the calibration law of some input
parameters of the MPC (depending on the FDRS configuration):
V0 dataframe:
V0-CAA : FDAU P/N 36045171E20 or 36045171E21
(blank if other FDAU P/N)
FDAU 36045171E21 : FDAU P/N 36045171E21
101-10002-851 Ind. I

- 112 -

Document Sagem DS - Reproduction et divulgation interdites

FDAU 36045171E20 : FDAU P/N 36045171E20

FDAU 36045171E01/2A01 : FDAU P/N 36045171E01 or 36045172A01
FDAU 36045171E00/2A00 : FDAU P/N 36045171E00 or 36045172A00
V2 dataframe:
ED34A110 : FDAU P/N ED34A110
ED34A3** : FDAU P/N ED34A310 or ED34A320
V2/V2A dataframes:
AFCS dw : AFCS with mod dw
(blank if AFCS without dw)

The second page displays:

- The AFDAU operational software low level identifications. As the operational software is made of
different sets of data/software, each of them having its own software identification, the reference of each
of these sets will be displayed.
The third page displays:
- The DMU operational software low level identification.
┌
MPC & A/C IDENT 1/3
MPC
1L █AFDAMUP/N ED35E109-01-02█ 1R
AFDAU S/W L036310102
2L █DMU S/W L036370109 █ 2R
DMU D/B 5112/0003
3L █ A/C █ 3R
STC V2A
4L █ATR72500 █ 4R
No SPTAB
5L █No GPS █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

┌
MPC & A/C IDENT 2/3
AFDAU OPE S/W DETAIL
1L █SOFT L036210500 █ 1R
V0STC L036210500
2L █V0V1STC L036210500 █ 2R
V2STC L036210500
3L █V2ASTC L036210500 █ 3R
V2B L036210500
4L █V0V1V2A L036210500 █ 4R
V3 L036210500
5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

101-10002-851 Ind. I

- 113 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC & A/C IDENT 3/3
DMU OPE S/W DETAIL
1L █S/W L036210500 █ 1R

2L █ █ 2R

3L █ █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-68 – MCDU Identifications pages

5.12.3.9 REPORTS menu

This menu gives access to pages related to the MPC reports (also called ACMS reports).
┌
MPC REPORT MENU
List of
1L █<PREV REP █ 1R
Stored
2L █<REPORTS █ 2R
Man reqst
3L █<REPORTS █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-69 – MCDU Report Menu

When this menu is selected, three pages are proposed:

• List of previous reports
• Stored reports
• Manual report request

5.12.3.9.1 List of previous reports

The last 20 reports can be visualised on this screen, for information only.
Format of display:
101-10002-851 Ind. I

- 114 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC PREVIOUS REPORTS 1/2
no code date utc leg
1L █02 3000 jan23 165200 000█ 1R
07 4500 jan23 164300 000
2L █13 4700 jan23 154300 000█ 2R
04 4004 jan22 204000 001
3L █09 5000 jan21 074200 002█ 3R
19 3000 jan20 155700 003
4L █19 3000 jan20 155200 003█ 4R
07 4400 jan20 152100 003
5L █15 3000 jan20 151400 003█ 5R
02 5000 jan19 113600 004
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-70 – MCDU Previous Reports List Menu

The displayed information is then:

• NO (2 characters) : Report number.
• CODE (4 characters) : Report code.
• DATE (5 characters) : Date of report generation: Month in clear English and day.
• LEG (3 characters) : Flight leg of report.
• UTC (6 characters) : Time of report generation: Hours/Minutes/Seconds (hhmmss).
The only message associated to that screen is:
• NOT ALLOWED : invalid key (LSK or any other key).
Colors:
The whole screen is in white characters (except the RETURN and PRINT*).

5.12.3.9.2 Stored reports

The first menu is used to select the type of report.
The second menu will give the last stored reports for the selected type (up to 16 reports).
The first menu that is used to select report type is the following one:
┌
MPC STORED REPORTS 1/2

1L █< 02: CRUISE █ 1R

2L █< 03: EXCEEDANCE █ 2R

3L █< 16: IDENT █ 3R

4L █< 15: G-METER █ 4R

5L █< 22: FLIGHT CMC █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

101-10002-851 Ind. I

- 115 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC STORED REPORTS 2/2

1L █< 23: GND TEST CMC █ 1R

2L █< 24: INSTANT FLIGHT CMC█ 2R

3L █< 25: PW127M ENGINE CYC █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-71 – MCDU Stored Report Menu

The only message associated to that screen is:

• NOT ALLOWED: invalid key (LSK or any other key).
When a type of report has been selected, the following menu is displayed:
┌
MPC STORED REPRT15 1/2

1L █←print (send) display █ 1R

2L █* ALL █ 2R
prt inacs
3L █* 000 4000 JAN23 172500>█ 3R
prt
4L █* 001 1000 JAN22 153400>█ 4R
dnlnk
5L █* 001 8100 JAN22 081200>█ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-72 – MCDU Stored Report List Menu

For each stored report the following information is displayed:

• LEG (3 characters) : Flight leg of report.
• CODE (4 characters) : Report code.
• DATE (5 characters) : Date of report generation: Month in clear English and day.
• UTC (6 characters) : Time of report generation: Hours/Minutes/Seconds (hhmmss).
In addition, information about destination is given:
• prt : the report has been printed.
• inacs : the report has been transferred to ACARS but no ground acknowledge has been received.
• dnlnk : the report has been transferred to ACARS and ground acknowledge has been received.
It is then possible to print/send each report independently.
It is also possible to:
101-10002-851 Ind. I

- 116 -

Document Sagem DS - Reproduction et divulgation interdites

• print/send all the reports with LSK 2L.

• print/send a report by selecting it with a LSK L key.
• display the contents of a report by selecting it with a LSK R key.
If a report is manually printed or sent to ACARS, the asterisk beside the related line select key shall be
removed during one second to acknowledge the request.
LSK 1L is used to "roll" options print and send. The selected option is the one in the left side. Each time the
key is depressed, the option changes.
• Print option: each generated report will be sent to the PRINTER.
• Send option: each generated report will be sent to the ACARS, with the default destination ACARS
ground.
If a “display” key is activated then the contents of the selected report will be displayed.
The display format will be retrieved from the printing format by:
• Removing the first three lines,
• Discarding all the characters at the end of each line when the number of characters of the line is greater
than the length of a MCDU line.
The messages associated to that screen are:
• NOT ALLOWED: Invalid key (LSK or any other key).
• PRINTER NOT AVAILABLE: Printer is not operative or not installed. The print out is aborted.
• PRINTER BUSY: Printer is busy. The print out is aborted.
• QUEUED TO PRINTER: The report is in the printer queue and is ready to be PRINTED.
• ACARS NOT AVAILABLE: ACARS-MU is not operative or not installed. The downlink is aborted.
• QUEUED TO ACARS: The report is in the ACARS queue and is ready to be downlinked.
When a PRINT or DOWNLINK request has been accepted by the DMU, the associated report is queued to
the requested peripheral and will stay in the queue until the output is performed successfully.

5.12.3.9.3 Manual report request

Each report (except CMC reports 22, 23, and 24) can be individually generated by a MCDU manual request.
The report can then be sent via ACARS, printed or simply stored in NVRAM and on PCMCIA disk (if
available) for further use.
The menu used is the following one:
┌
MPC MAN REQ REPORTS 1/2

1L █←print (send store) █ 1R

2L █* 02:CRUISE █ 2R

3L █* 03:EXCEEDANCE █ 3R

4L █* 15:G-METER █ 4R

5L █* 16:IDENT █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

101-10002-851 Ind. I

- 117 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC MAN REQ REPORTS 2/2

1L █←print (send store) █ 1R

2L █* 25:PW127M ENGINE CYC █ 2R

3L █ █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-73 – MCDU Manual Report Request Menu

LSK 1L is used to "roll" options print, send and store. The selected option is the one in the left side. Each
time the key is depressed, the option changes.
• Print option: each generated report will be stored in NVRAM and sent to the PRINTER.
• Store option: each generated report will be stored in NVRAM. It is then possible either to print or send it
manually or to dump it in a diskette.
• Send option: each generated report will be stored in NVRAM and sent to the ACARS, with the default
destination ACARS ground
The asterisk beside a selected report is removed during report generation.
The different messages that can be displayed on that screen are the following ones:
• NOT ALLOWED: invalid key (LSK or any other key).
• GENERATION IN PROGRESS: This message is displayed after a report selection during generation of
the report.
• REPORT NOT READY: It is not possible to generate the report because an automatic one is in progress.
The manual request is aborted.
• PRINTER NOT AVAILABLE: Printer is not operative or not installed. The print out is aborted.
• PRINTER BUSY: Printer is busy. The print out is aborted.
• QUEUED TO PRINTER: The report is in the printer queue and is ready to be PRINTED.
• ACARS NOT AVAILABLE: ACARS-MU is not operative or not installed. The downlink is aborted.
• QUEUED TO ACARS: The report is in the ACARS queue and is ready to be downlinked.
When a PRINT or DOWNLINK request has been accepted by the DMU, the associated report is queued to
the requested peripheral and will stay in the queue until the output is performed successfully.
The operator can accede to the report output status using the stored report menu.

5.12.3.10 Init Time & FLT menu

This page allows to initialise date, time and flight number in the FDAU through an ARINC 429 interface.
When entering this page, the initial values of date and time are retrieved from the FDAU (if available) and
can be then updated by the user. The value of flight number is kept from previous flight if any, otherwise it is
set to 0000.
101-10002-851 Ind. I

- 118 -

Document Sagem DS - Reproduction et divulgation interdites

┌
TIME & FLIGHT

1L █ █ 1R
HOUR:MINUTE
2L █←11:05 █ 2R
MONTH:DAY
3L █←11:22 █ 3R
YEAR
4L █←2005 █ 4R
FLIGHT NUMBER
5L █←4526 █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-74 – MCDU time and flight page
Range of data:
• HOUR: 0 to 23
• MINUTE: 0 to 59
• MONTH: 1 to 12
• DAY: 1 to 31
• YEAR: 0 to 7999
• FLIGHT NUMBER: 0 to 9999

Note : a “XX” value for a data indicate that the current value is not up to date. A refresh is in progress to acquire
a correct and up to date value to display.
Note : Clearing fields by pressing "CLR" key is not possible in that screen
The messages that are associated to this screen are:
• NOT ALLOWED: invalid key (LSK or any other key).
• INVALID ENTRY: data out of bounds, or mismatching.
• NO FDAU AVAILABLE : impossible to communicate with the FDAU
• UPDATE IN PROGRESS : an update of a data is performed to the FDAU
• COMMUNICATION ERROR : an error occurred during a communication with the FDAU
• LIGHT TEST : a light test is currently being performed by the FDAU upon DMU order
• WAITING: AUTO RETRYING : After an error during a setting protocol, the DMU software retry
automatically the setting.
• UPDATING DATE : the setting of a new date to the FDAU is currently being performed
• REFRESHING DISPLAY : the current date is being read from the FDAU

5.12.3.11 G-meter menu

Display :
101-10002-851 Ind. I

- 119 -

Document Sagem DS - Reproduction et divulgation interdites

┌
G-METER REPORT

1L █ report data █ 1R
report data
2L █ report data █ 2R
report data
3L █ report data █ 3R
report data
4L █ report data █ 4R
report data
5L █ report data █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-75 – MCDU G-Meter report page

This page displays the content of the last generated G-Meter report.

5.12.3.12 Init param menu

Display :
┌
INIT PARAM

1L █<A/C PARAM INIT █ 1R

2L █<ETHERNET PARAM INIT █ 2R

3L █ █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN █ 6R

Figure 5-76 – MCDU init param page

This page allows the access to "A/C Param Init" (LSK 1L), "Ethernet param init" (LSK 2L) and “Reports
limits” pages (LSK_5L).The “Reports limits” menu is hidden
The access to "Ethernet param init" and “Reports limits” pages are password protected: the user must seize
the right password in the scratchpad, then pressing the LSK-2L or 5L key, in order to enter the page.
The password is defined in the GSE in the screen "Programming => MCDU => Function password". In that
screen, the function name associated to the password is "Ethernet Parameters" and “Reports limits”.
Remark : The password defined in the GSE should not be empty.

5.12.3.12.1 A/C Param Init menu

The A/C PARAM init menu is divided in 2 pages:
101-10002-851 Ind. I

- 120 -

Document Sagem DS - Reproduction et divulgation interdites

- the first page manages the A/C TAIL (depending on the database configuration) initialisation and the
configuration of the air conditioning discrete, used for calculation of quality factor of cruise reports for
ECTM generation (see 5.3.2.1.4).
- The second page manages the engine and APU initialisations (depending on the aircraft type).

5.12.3.12.1.1 First page : A/C TAIL init and Air conditioning discrete configuration

5.12.3.12.1.1.1. A/C TAIL init

This page displays the current A/C TAIL and A/C number and allows (under conditions) to initialise A/C TAIL
via the MCDU screen.
Two possible cases:
The loaded database is defined for any aircraft (with BYPASS)
The loaded database has an aircraft list (no BYPASS)

a) DMU loaded with a Database with BYPASS (for any aircraft)

This page allows to initialise A/C TAIL. When entering this page, the initial value of A/C TAIL is displayed
and can be then updated by the user. After power-up, if the A/C tail was never initialised by user and if the
A/C number is known, then this page is the first page displayed upon MCDU log-on.
The A/C TAIL can be initialised at any flight phase.
If the A/C TAIL has never been initialised, the A/C TAIL default value will be the A/C NUMBER value,
If at power up the A/C NUMBER is different from previous one, the A/C TAIL value will be the new A/C
NUMBER value,
The scanned A/C TAIL must be placed in NVRAM so as to be retrieved after a power cut.
This page will be displayed first at first MCDU log on after power up if the A/C TAIL wasn’t set by the user
and if no OBPM loading is in progress.
When A/C TAIL is modified, the following memorised data shall be cleared from NVRAM :
Reports.
SAR (record and statistic).
Temporary change.

Display:

Value of the A/C TAIL and A/C NUMBER parameters

┌
A/C PARAM INIT 1/2
A/C TAIL: A/C NUMBER:
1L █←A72001 00105 █ 1R
├
2L █ █ 2R
HP VALVE 1 HP VALVE 2├
3L █*OPEN CLOSE*█ 3R
PACK FLOW 1 PACK FLOW 2├
4L █*ON OFF*█ 4R
FLOW CONTROL FUEL FLOW├
5L █*NORM kgs/hr*█ 5R
├
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-77 – A/C TAIL INIT page with BYPASS
MCDU screen colour:
- A/C PARAM INIT, A/C TAIL and A/C NUMBER: in white,
101-10002-851 Ind. I

- 121 -

Document Sagem DS - Reproduction et divulgation interdites

- ←A72001 in amber,
- 00105 in green.
- RETURN and PRINT in cyan,

To initialise an A/C TAIL, the operator enters through the keyboard the A/C TAIL number in the scratchpad
and depresses the A72001 key (1L). The new parameter value is displayed in A72001 field.
If these fields are not correct, the error messages that appear on the screen are described hereunder:
• NOT ALLOWED: invalid key (LSK or any other key).
• INVALID ENTRY: data out of bounds, or mismatching.

b) Database without BYPASS (for all aircraft)

The page doesn’t allow to initialise A/C TAIL. When entering this page, the value of A/C TAIL is displayed on
the MCDU screen with a message which informs the operator that the A/C TAIL can only be modified by a
database update.
The A/C TAIL can’t be initialised with this menu and the value belongs to the computed parameter.
┌
A/C PARAM INIT 1/2
A/C TAIL: A/C NUMBER:
1L █ A72001 00105 █ 1R
defined by database ├
2L █ █ 2R
HP VALVE 1 HP VALVE 2├
3L █*OPEN CLOSE*█ 3R
PACK FLOW 1 PACK FLOW 2├
4L █*ON OFF*█ 4R
FLOW CONTROL FUEL FLOW├
5L █*NORM kgs/hr*█ 5R
├
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-78 – A/C TAIL INIT page without BYPASS
MCDU screen colour :

- A/C PARAM INIT, A/C TAIL:, A/C NUMBER:, « defined by database » : in white characters.
- A72001 and 00105 : in green characters.
- RETURN and PRINT in cyan characters.

The associated message to this screen is:

NOT ALLOWED: invalid key (LSK or any other key).

Note: the A/C TAIL is stored in a file on PCMCIA disk as described in §5.16.10.

5.12.3.12.1.1.2. Air conditionning discrete configuration

The air conditioning discrete are used for calculation of quality factor of cruise reports for ECTM generation.
The list of discrete to be configured, and the three possible values for each discrete is given in the chapter
5.3.2.1.4.
Display (common with A/C Tail and A/C number initialisation):
101-10002-851 Ind. I

- 122 -

Document Sagem DS - Reproduction et divulgation interdites

┌
A/C PARAM INIT 1/2
A/C TAIL: A/C NUMBER:
1L █ A72001 00105 █ 1R
defined by database ├
2L █ █ 2R
HP VALVE 1 HP VALVE 2├
3L █*OPEN CLOSE*█ 3R
PACK FLOW 1 PACK FLOW 2├
4L █*ON OFF*█ 4R
FLOW CONTROL FUEL FLOW├
5L █*NORM kgs/hr*█ 5R
├
6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-79 – Air conditioning discrete configuration

Pressing a function key toggles between the different states of each discrete. As explained in chapter
5.3.2.1.4, each discrete can be ignored for computation of quality factor. In that screen, the "ignored" state is
represented by "NA" value.

5.12.3.12.1.2 Second page : Engine parameters init

This page displays the APU and engine S/N, hours and cycles.
There is no APU on some MPC aircraft configurations. In that case, the related lines are hidden.
The engine parameters are initialised depending on the aircraft type. For the MPC, only two engines are
displayed (lines related to engines 3 and 4 are hidden), and only the S/Ns can be initialised (hours and
cycles are hidden).

Display:

ASN: APU Serial Number (6 characters).

AHRS: APU flight hours (5 digits).
ACYC: APU Cycles (5 digits).
ESN1: Engine 1 Serial Number (6 characters).
EHRS1: Engine 1 flight hours (5 digits).
ECYC1: Engine 1 Cycles (5 digits).
ESN2: Engine 2 Serial Number (6 characters).
EHRS2: Engine 2 flight hours (5 digits).
ECYC2: Engine 2 Cycles (5 digits).
ESN3: Engine 3 Serial Number (6 characters).
EHRS3: Engine 3 flight hours (5 digits).
ECYC3: Engine 3 Cycles (5 digits).
ESN4: Engine 4 Serial Number (6 characters).
EHRS4: Engine 4 flight hours (5 digits).
ECYC4 : Engine 4 Cycles (5 digits).
101-10002-851 Ind. I

- 123 -

Document Sagem DS - Reproduction et divulgation interdites

┌
A/C PARAM INIT 2/2
ASN ACYC /AHRS
1L █←aaaaaa bbbbb/ccccc→ █ 1R
ESN1 ECYC1/EHRS1
2L █←aaaaaa bbbbb/ccccc→ █ 2R
ESN2 ECYC2/EHRS2
3L █←aaaaaa bbbbb/ccccc→ █ 3R
ESN3 ECYC3/EHRS3
4L █←aaaaaa bbbbb/ccccc→ █ 4R
ESN4 ECYC4/EHRS4
5L █←aaaaaa bbbbb/ccccc→ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-80 – A/C Param INIT menu – APU and ENGINE management

MCDU screen colour :

- A/C PARAM INIT, ASN, AHRS, ACYC, ESN, ECYC and EHRS in white,
- editable fields (aaaaaa for MPC), RETURN et PRINT in cyan,
- non-editable fields (bbbbb, ccccc for MPC) in green.

5.12.3.12.2 Ethernet param init menu

This page displays the Network configuration of the unit, and allows to change this configuration at any time.
As explained in §5.12.3.12, its access is password protected.

Display :
┌
ETHERNET PARAM INIT
IP adress :
1L █←LLL LLL LLL LLL █ 1R
Subnet mask :
2L █←LLL LLL LLL LLL █ 2R
Gateway adress :
3L █←LLL LLL LLL LLL █ 3R
SN (4 LAST DIGITS):
4L █←LLLL █ 4R

5L █*RESET VALIDATE*█ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-81 – ETHERNET PARAM INIT page

The following data are displayed :

• The IP address of the Ethernet interface of the MPC.
• The Network mask of the Ethernet interface associated with the IP address
• The default gateway for the network
101-10002-851 Ind. I

- 124 -

Document Sagem DS - Reproduction et divulgation interdites

• The 4 last digits of the serial number of the MPC unit which are automatically transformed into a single
MAC (Medium Access Control) address of the interface
Fields will be filled with the previously memorised data.
The VALIDATE (LSK 5R) is activable if all data of Network configuration are defined, and are different from
current network configuration.
Pressing the VALIDATE (LSK 5R) key results in saving of the new Ethernet configuration in NVRAM, so that
it is conserved after a power cut. It also reinitialises the TCP/IP stack with the new configuration. If the user
exits from this screen without pressing the VALIDATE key, any change in the configuration is discarded.
The RESET key (LSK 5L) resets the configuration to the GSE configuration or to the default (see §5.17.4).

5.12.3.12.3 Reports limits menu

This page allows the operator to change some limits that are programmable by the GSE. All the limits that
can be modified have a reference number that is used to access this limit. As explained in §5.12.3.12, its
access is password protected.

┌
MPC REPORTS LIMITS
param nb
1L █←xxxx █ 1R
├
2L █ █ 2R
├
3L █ █ 3R
├
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
0017

Figure 5-82 – MPC REPORTS LIMITS page (initial state)
After depressing LSK1, the system displays beside the number of parameter to modify the present value of
the limit (OLD LIMIT). This value is either a real value or an integer one according to the type of related
parameter.
If the limit is not protected against modification, the operator has then to give:
• The new limit to apply (NEW LIMIT) using LSK2R.
• Its validity duration (VALIDITY) using LSK2L.
• The reason of change if desired (REASON) using LSK3L and LSK4L.
If these fields aren’t displayed, it means that the selected limit is protected against modification.
When all the fields are filled the operator has to press the VALIDATE key to make this modification
operational. At this moment a message is sent to ACARS and to printer to acknowledge the change and a
message is displayed on the MCDU screen: "VALIDATE OK".
101-10002-851 Ind. I

- 125 -

Document Sagem DS - Reproduction et divulgation interdites

┌
MPC REPORTS LIMITS
param nb old limit
1L █←0017 00000000002 █ 1L
validity new limit ├
2L █←xxttt 00000000001→█ 2L
reason ├
3L █←test purpose █ 3L
├
4L █←xxxxxxxxxxxxxxxxxxxxxxx█ 4L
return to
5L █*VALIDATE DEFAULT*█ 5L

6L █<RETURN PRINT*█ 6L

Figure 5-83 – MPC REPORTS LIMITS page (edition state)
Format of display:
• VALIDITY: duration of the temporary change.
− XX: 2 digits from 00 to 99. 00 is a particular value indicating that the change has no time limitation
and must be followed by ‘INF‘ string.
− TTT: day (DAY), flight leg (LEG) or infinite (INF).
• OLD LIMIT: up to 10 digits for integer values or up to 11 digits for real values.
• NEW LIMIT: Same format as the old limit.
• REASON: 2 lines of 23 characters each.
If a parameter has already a temporary change applied, when selecting this parameter for modification, the
present temporary limit, remaining validity time and reason are displayed.
After all the fields are entered, it is necessary to validate the whole menu to really apply the modification.
When the modification is effective the message "VALIDATE OK" is then displayed in the scratchpad.
Note: A message is output on MPTR when a modification request has been validated.
If 50 temporary changes have been made (maximum number of simultaneous changes) then a message is
displayed on the screen: "MODIFICATION TABLE FULL".
The key "RETURN TO DEFAULT" allows the operator to come back to the initial value before the validity is
over.

5.12.3.13 CMC menu

This menu is used to manage fault reports coming from the MFC using 2 ARINC429 links:
• display last stored report <22>. (Flight CMC report),
• generate and display a test report <23>. (GND CMC test report),
• display the CMC database version.

The whole menu is in white except the RETURN and PRINT in cyan characters and version number in green
characters.
101-10002-851 Ind. I

- 126 -

Document Sagem DS - Reproduction et divulgation interdites

┌
CMC REPORT

1L █<LAST FLIGHT REPORT █ 1R

2L █<GND TEST REPORT █ 2R

3L █DB VERSION: V 1.0.1 █ 3R

4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R

Figure 5-84 – MCDU CMC REPORT Menu
The only message associated to that screen is:
• NOT ALLOWED: invalid key (LSK or any other key).

5.12.3.13.1 Last flight report

This MCDU page is used to display the last stored report <22> (flight CMC report).
More information about the data displayed are provided in the report <22> description, chapter 5.3.2.5.
Format of display:
┌
LAST FLIGHT REPORT

1L █ report data █ 1R
report data
2L █ report data █ 2R
report data
3L █ report data █ 3R
report data
4L █ report data █ 4R
report data
5L █ report data █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-85 – MCDU LAST FLIGHT REPORT Page

The function: "PRINT"(LSK 6R) allows to hard copy (on MPTR and/or on PCMCIA disk) the report displayed.
Arrows can be used to navigate though the report in case it take more than one page.

5.12.3.13.2 GND test report

This MCDU page is used to launch a generation, then to display a report <23> (GND TEST CMC report).
More information about the data displayed and generation conditions are provided in the report <23>
description, chapter 5.3.2.6.
101-10002-851 Ind. I

- 127 -

Document Sagem DS - Reproduction et divulgation interdites

First, the DMU software wait for the generation of a new report <23>, and so display a wait message :
┌
GND TEST REPORT

1L █ █ 1R
WAITING
2L █ █ 2R
FOR
3L █ █ 3R
MASTER ALARM
4L █ █ 4R

5L █ █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-86 – MCDU GND TEST report Menu (1)

Then, once the report <23> had been generated, the DMU display it :
┌
GND TEST REPORT

1L █ report data █ 1R
report data
2L █ report data █ 2R
report data
3L █ report data █ 3R
report data
4L █ report data █ 4R
report data
5L █ report data █ 5R

6L █<RETURN PRINT*█ 6R
↑↓

Figure 5-87 – MCDU GND TEST report Menu (2)

The function: "PRINT"(LSK 6R) allows to hard copy (on MPTR and/or on PCMCIA disk) the report displayed.
Arrows can be used to navigate though the report in case it takes more than one page.
101-10002-851 Ind. I

- 128 -

Document Sagem DS - Reproduction et divulgation interdites

5.13. ACARS FUNCTIONS

The DMU is able to manage different functions to:
• send data via ACARS to the ground (downlink),
• receive data via ACARS from the ground (uplink).
In addition to protocol communication, the DMU broadcasts parameters to the ACARS MU.

5.13.1. Communication protocol

The communication with ACARS is achieved using ARINC 724 B protocol.
In addition to this standard, following rules have to be applied:
1) All downlink messages are sent as multi-block messages.
2) The maximum length of a message is limited to 16 blocks.
3) The size of a block is limited to 186 characters (optional ground header not included).
4) The DMU does not insert the optional header in the downlink messages, and have to set bit 17 of the STX
word to 0.
5) In case of no ACARS answer to a DMU dialogue request, the DMU has to wait a 1mn delay before issuing
a new request.
6) After successful transmission of a message to the MU, the DMU waits for a ground acknowledgement
(message with a K in the purpose/nature code), before issuing any new message. If after 10 minutes delay,
no ground acknowledgement is received, then the DMU continue transmission process with a new
message.
7) The DMU must transmit every second the activity Arinc word 0x0000437A (label 0172) on the ACARS
output bus.
Note: Ground acknowledgement delay is programmable on the GSE.
101-10002-851 Ind. I

- 129 -

Document Sagem DS - Reproduction et divulgation interdites

5.13.2. Downlink messages

5.13.2.1 General messages Format

Each block of a message has the same format beginning with a header followed by the message text:

Character Contents Description

Control accountability header:

1 0x1F Unit separator

2 "D" Origin code: DMU

3 "W" Purpose code: downlink

4 "V" Dest. code: VHF

5 X Bloc sequence character

6-9 "D"NNN Message sequence number

Optional ground header :

10-11 "ID" Airline ID

12-15 NNNN Flight number

16 "#"

17-18 "DF" Sublabel:DMU

19 "B" Message type

Text message:

20-22 "XXX" Message IMI

23-N-1 "... User message data

N 0x17/0x03 Value of characters ETB/ETX in

ASCII

5.13.2.1.1 Control accountability header

Characters 1 to 9 are the control accountability header:
• Characters 1 – 2 – 3 are fixed, as described above.
• Character 4 is the destination code. Its default value is V (VHF) for all messages. G(ground), S(SATCOM)
and H(HF) codes can be used for reports downlink.
• Character 5 is the block sequence character. This character is initialised to 40 and is incremented up to 7F
for each block.
• Characters 6 to 9 are the downlink sequence number. Character 6 is fixed to D. Characters 7 to 9 represent
a number from 000 to 999 which is incremented each time a block is transferred.
101-10002-851 Ind. I

- 130 -

Document Sagem DS - Reproduction et divulgation interdites

5.13.2.1.2 Optional ground header

Characters 10 to 19 are the optional ground header. This part of the message is not provided by the DMU.
Length of DMU message blocks is limited to 186 characters, allowing the MU to insert the optional ground
header.

5.13.2.1.3 Text message

Characters 20 and following are the message text and are described below for each particular message. As
a general rule, characters 20 – 22 of the 1 block of a message, are the IMI of the message. They are used
st

to identify the message content.

Each message will be associated to a specific IMI.

5.13.2.2 List of downlink messages

5.13.2.2.1 ACMS reports

ACMS Reports either manual or automatically initiated reports, are transmitted as multiblock messages
according to rules described in chapter 5.3.1.5.2.

5.13.2.2.2 Acknowledgement of pre-defined function activated

The DMU downlinks an acknowledgement message when receiving an uplink request for activation of a
report predefined function.
In this DMU software version, there is no uplink request for activation of a report predefined function, so
there is no acknowledgement message.
•

5.13.2.2.3 List of temporary changes

The DMU downlinks the list of all temporary modifications applied, in answer to specific uplink request
described in chapter 5.13.3.3.3.
• IMI : LTP
• Message : xx,nnnn,vvvvvvvv,f,dd,nnnn,vvvvvvvv,f,dd,...
Message length depends on the total number of temporary changes applied (50 maximum).

xx Number of temporary changes

nnnn Limit number

vvvvvvvv New limit applied

f Duration unit (2= infinite ,1 = day, 0 = leg)

dd Remaining duration of the change (0-99 with zero a specific

value for no-time limit)

5.13.2.2.4 Acknowledgement of limit modification

The DMU downlinks an acknowledgement message after performing a temporary change due to an ACARS
uplink request described in chapter 5.13.3.3.4.
• IMI : TMP
• Message : nnnn,vvvvvvvv,f,dd
101-10002-851 Ind. I

- 131 -

Document Sagem DS - Reproduction et divulgation interdites

nnnn Limit number

vvvvvvvv New limit applied

f Duration unit (2 = infinite ,1 = day , 0 = leg)

dd Duration of the change (0-99 with 0 a specific value for no-

time limit)

5.13.2.2.5 Acknowledgement of limit return to default

The DMU downlinks an acknowledgement message after performing a limit return to default action due to an
ACARS uplink request described in chapter 5.13.3.3.5.
• IMI : TDP
• Message : nnnn,vvvvvvvv

nnnn Limit number

vvvvvvvv Default limit value

5.13.2.2.6 Advisory messages due to SAR recording trigger conditions

As described in chapters 5.9.5.1 and 5.10.4, each time a Standard SAR, an Extended SAR or a SAR Event
recording trigger condition is met, an advisory message can be sent to ACARS (if not inhibited with the
GSE).
• IMI: a specific IMI is defined for each SAR partition:
− SDT: SAR Data recording partition.
− SET: SAR Extended trouble shooting partition.
− SST: SAR Event recording partition.
− SXT: SAR Extended Data recording partition.
• Message: text of 40 characters free programmable on GSE for each individual event.

5.13.2.2.7 Advisory messages due to Standard SAR or SAR Event recordings data dump
Each time an attempt for Standard SAR or SAR Event recording data downloading on PCMCIA is performed
(see chapter 5.16.4.2), an advisory message is sent to ACARS at the end of the downloading procedure.
• IMI: a specific IMI is defined for each SAR partition:
− SDM: SAR Data recording partition.
− SEM: SAR Extended trouble shooting partition.
− SSM: SAR Event recording function.
• Message : 2 different messages are provided. One message is sent if the retrieval procedure is successful
(all the selected data have been downloaded on the disk). The second message is sent if the retrieval
procedure is not successful (any error occurring during file transfer). Both messages are 40 characters free
programmable by GSE using the screens :
− Programming -> SAR Event recording -> Trigger monitoring -> Setup (for SAR Event)
− Programming ->SAR Data recording -> Trigger monitoring -> Setup (for Standard SAR)
101-10002-851 Ind. I

- 132 -

Document Sagem DS - Reproduction et divulgation interdites

5.13.2.2.8 SAR Event recording statistic

The system downlinks a statistic message, for SAR Event recording function as defined in section 5.10.4.
• IMI: SSP.
• Message:
− FROM,DDMMMYY,HHMM,TO,DDMMMYY,HHMM.
− E1,XX,XX,XX,XX,XX,XX,XX,XX,XX,XX.
− E2,XX,XX,XX,XX,XX,XX,XX,XX,XX,XX.
− E3,XX,XX,XX,XX,XX,XX,XX,XX,XX,XX.
− E4,XX,XX,XX,XX,XX,XX,XX,XX,XX,XX.
− E5,XX,XX,XX,XX,XX,XX,XX,XX,XX,XX.

− FROM : Date and time of last retrieval.

− TO : Actual date and time.
− XX : Amount of associated events from 01 to 50.

5.13.2.2.9 Acknowledgement of Enable/Disable SAR recording sequence

The DMU downlinks an acknowledgement message when receiving an uplink request for enable/disable a
Standard SAR, an Extended SAR or a SAR Event trigger logic (this request is described in chapter
5.13.3.3.6).
• IMI: ISP.
• Message: x,n,sss
− x: E = Enabled
D = Disabled
− n: 1 = Data recording partition
2 = Extended trouble shooting partition
3 = Event recording function.
4 = Extended Data recording partition
− sss: Sequence number 001 to 100

5.13.2.2.10 Configuration Load status message

Following an uplink request for configuration load (described in chapter 5.13.3.3.8), the DMU downlinks a
status message to identify the unit configuration: Hardware P/N and reference of loaded software.
• IMI : LCP
• Message : pppppppppppppp,xxxxxxxxxxxxxx,vvvv/llll

pppppppppppppp Hardware Part number = (for example ED35E109-01-02)

xxxxxxxxxxxxxx System Software Disk Part number (for example 252692832-0101)

vvvv/llll Version number / revision level of the customer database

5.13.2.2.11 Acknowledgement of Engine/APU data modification

The DMU downlinks an acknowledgement message when receiving an uplink request for modification of
Engine and APU data (hours and cycle). If no APU is present on the aircraft, the request is ignored and no
acknowledgement is sent. This request is described in chapter 5.13.3.3.9
101-10002-851 Ind. I

- 133 -

Document Sagem DS - Reproduction et divulgation interdites

• IMI : MEP
• Message : tttt,ssssss,hhhhh,ccccc

tttt : Destination (“ENG1”, “ENG2”, “APU “)

ssssss : Serial number

hhhhh : new hours value

ccccc : new cycles value

5.13.2.2.12 Advisory message when PCMCIA disk is removed

The DMU automatically downlink a message to the ground, if T second after detection of a PCMCIA disk
removal (on operational process, or after power up), no disk is inserted in the unit.
The GSE "PCMCIA configuration" page allows to modify the content of the message ,the time delay (T), and
to enable or disable this function.
• IMI : CIA
• Message : text of 40 characters free programmed on the GSE.
101-10002-851 Ind. I

- 134 -

Document Sagem DS - Reproduction et divulgation interdites

5.13.3. Uplink messages

5.13.3.1 General messages Format

Each uplink message will have the following pattern :
Character Contents Description
1 (1/15) Unit separator
2 "V" Origin code : VHF
3 "V" Purpose code : uplink
4 "D" Dest. code : DMU
5 X Bloc sequence character
Optional ground header
6 "."
7-13 AAAAAAA Originator address
14-X ....... Service provider information
Sub-label sequence
X+1 "-"
X+2 "" One space character
X+3 "#"
X+4-X+5 "DF" Sub-label
Optional downlink address header.
X+6 "/"
X+7-Y ....... Optional downlink addresses
Y+1 "."
User text
Y+2-Y+4 "IMI" Message IMI
Y+5 .... N ... User message data
N+1 0x03 Value of character ETX in ASCII
Characters 6 to 14-X and X+6 to Y+1 are optional, and are not treated by the DMU. If one of this character
sequence is missing, the following character sequence start immediately. For example, if characters 6 to 14-
X are missing, then the sub-label sequence start at character 6 (ie X is replaced by 5).
If Optional ground header is missing, then the sub-label sequence may also be missing.
If the uplink message is a ground acknowledgement for the last downlinked message, then the purpose code
will be "K".
Characters Y+2 and following are the message text and are described below for each particular message.
As a general rule, characters Y+2 – Y+4 of the message, are the IMI of the message. They are used to
identify the message content. Each message will be associated to a specific IMI.

5.13.3.2 Message control: error management

After receiving a message with purpose code "D", the DMU check the IMI of the message. All messages
without IMI or with a not defined IMI will be rejected by the DMU (no treatment).
When receiving a message with a correct IMI, then the DMU check the message content (syntax of the
message – and validity of data).
All incorrect messages (i.e.: missing data fields – too many characters – value out of range – invalid report
number – invalid limit number – invalid serial number etc...) will lead to following action:
• Requested treatment not performed.
101-10002-851 Ind. I

- 135 -

Document Sagem DS - Reproduction et divulgation interdites

5.13.3.3 List of uplink messages

5.13.3.3.1 Request for immediate generation of reports

Each report can be triggered immediately by an ACARS uplink request.
• IMI : REQ
• Message : xx
xx: Report number i.e. 01 to 99
The DMU acknowledges reception of the uplink by immediate generation and transmission of the requested
report.

5.13.3.3.2 Activation of pre-defined functions

This uplink requests to the DMU the activation of one of report predefined functions. The goal is to request
special treatments on reports, for example to generate a specific report on the next flight or to reset a report
computing.
The DMU acknowledges reception of the uplink by the transmission of a specific acknowledgement
message.
In this DMU software version, there is no pre-defined function.

5.13.3.3.3 Request for list of temporary changes

This uplink requests to the DMU the immediate downlink of the list of all temporary changes applied.
• IMI : LTR.
• Message : No additional information required.
The DMU acknowledges reception of the uplink by the transmission of the requested list as described in
chapter 5.13.2.2.3.

5.13.3.3.4 Temporary change of limits and constants

This uplink allows modifying, for a temporary time, reports limits and constants.
• IMI : TMR
• Message : nnnn,vvvvvvvv,f,dd,aa...a

nnnn Limit number

vvvvvvvv New limit applied
f Duration unit (2 = infinite,1=day , 0=leg)
dd Duration of the change (0-99 with 0 a specific value for no-time limit)
aa...a Reason for modification – up to 44 characters. Reason text is optional and
can be omitted.

The DMU acknowledges reception of the uplink by the transmission of a specific acknowledgement message
described in chapter 5.13.2.2.4.

5.13.3.3.5 Limit return to default request

This uplink allows resetting a specific limit to its default value.
• IMI : TDR
• Message text : nnnn
nnnn: limit number
101-10002-851 Ind. I

- 136 -

Document Sagem DS - Reproduction et divulgation interdites

The DMU acknowledges reception of the uplink by the transmission of a specific acknowledgement message
described in chapter 5.13.2.2.5.

5.13.3.3.6 Enable/Disable SAR recording sequence

This uplink allows to individually enable or disable each Standard SAR, Extended SAR or SAR Event
recording trigger sequence as described in chapters 5.9.5.3 and 5.10.2.
• IMI : ISR
• Message text : x,n,sss
− x : E = Enable
D = Disable
− n : 1 = Data recording partition
2 = Extended trouble shooting partition
3 = Event recording function
4 = Extended Data recording partition
− sss : Sequence number 001 to 50.
The DMU acknowledges reception of the uplink by the transmission of a specific acknowledgement message
described in chapter 5.13.2.2.9.

5.13.3.3.7 Request for downlink of SAR Event recording statistics

This uplink requests to the DMU the immediate downlink of the SAR Event recording Statistic (see chapter
5.10.4).
• IMI : SSR
• Message : No additional information required
The DMU acknowledges reception of the uplink by the transmission of the requested statistic, as described
in chapter 5.13.2.2.8.

5.13.3.3.8 Configuration Load status request

This uplink requests to the DMU the immediate downlink of the DMU configuration status.
• IMI : LCR
• Message : No additional information required
The DMU acknowledges reception of the uplink by the transmission of the requested status, described in
chapter 5.13.2.2.10.

5.13.3.3.9 Engine/APU data modification

This uplink allows to modify engine hours and cycle, APU offsets for hours and cycle computing.
If there is no APU in the aircraft, related uplink requests will be ignored.
• IMI : MER
• Message : tttt,ssssss,hhhhh,ccccc

tttt Destination ("ENG1", "ENG2", "APU ")

ssssss Serial number
hhhhh hours number
ccccc cycles number
101-10002-851 Ind. I

- 137 -

Document Sagem DS - Reproduction et divulgation interdites

The DMU acknowledges reception of the uplink by the transmission of a specific acknowledgement
message, described in chapter 5.13.2.2.11.
Note: Engine or APU Serial numbers can not be modified, but are transmitted for control only. No modification
will be performed by the DMU if serial number is not correct.

5.13.4. Broadcast parameters

In addition to the reports and the advisory messages the DMU is able to broadcast parameters to the
ACARS MU.
The default list of those broadcast parameters is given in appendix 6.8.
The input data selected, the emission rate, the emission label and SDI are programmable through GSE. The
emission rate can be either 1 sample/sec. or 2 samples/sec. The total amount of parameters to be broadcast
to ACARS should not exceed 64 samples/sec.
The data can be transmitted to ACARS according to the following rules.

5.13.4.1 Parameters transmitted as received

The DMU sends the received ARINC 429 parameters without making any change on the parameters except
the label, and SDI which are changed according to the new label and SDI programmed on the GSE.
When the parameter is not received, the DMU sends the parameter to ACARS with SSM = 01 (no computed
data).
Note: DMU Computed parameters
When DMU computed parameters are broadcast as received to ACARS, the DMU sends the computed
parameters according to BNR 429 SSM rules i.e.:
• SSM = 11 when valid data,
• SSM = 01 when invalid data (computation not possible).
Bit 1 (LSB) of the computed parameter is copied in bit 11 of the ARINC word and so on.
The SDI is XX (don't care).
The label is the one programmed on the GSE.

5.13.4.2 General BCD word

Parameters can be translated in a general BCD format as defined below:

3 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2
1
P SSM 0 BCD (MSB) BCD BCD BCD BCD (LSB) Label
Character # 1 Character # 2 Character # 3 Character # 4 Character # 5

Translation of incoming parameter

Notes:
• SDI is not needed,
• bit 29 is not used (pad 0),
The DMU has to convert the incoming parameter in this general BCD format. The conversion rules are
depending of the incoming parameter type and are described hereafter.
Incoming type = BNR
The BNR parameter (operational data field from bit 28 to XX) is converted in BCD considering that the
operational LSB of the BNR parameter (bit XX) is of weight = 1.
101-10002-851 Ind. I

- 138 -

Document Sagem DS - Reproduction et divulgation interdites

• If BCD result > 99999, SSM = (0.1).

• If BCD result < 99999 this result is sent to ACARS (right justified) with SSM according to bit 29 of BNR
incoming parameter:
• bit 29 = 0 => SSM = positive (0.0),
• bit 29 = 1 => SSM = negative (1.1).

Incoming type = BCD

The incoming parameter is right justified in the output parameter with the same SSM.
Incoming type = discrete
The incoming parameter should have less than 16 operational bits, and then the rule for BNR incoming
parameter has to be followed.
101-10002-851 Ind. I

- 139 -

Document Sagem DS - Reproduction et divulgation interdites

5.14. PRINTER INTERFACE

5.14.1. Dialogue with PRINTER

The DMU dialogues with the PRINTER according to ARINC 740 protocol.
The DMU must transmit every second the activity Arinc word 0x0000437A (label 0172) on the PRINTER
output bus.

5.14.2. Printer messages

The different uses of the multi-printer are the following ones:
• printing of reports,
• hard copy of MCDU screens,
• print of advisory messages (not provided in this DMU version).
Each specific message will be detailed in corresponding function description of this document
As a general rule, all printed messages, except reports, are printed with a standard header, as defined
below:

0000000001111111111222222222233333333334
1234567890123456789012345678901234567890

ATR 42/72 AFDAMU DMU PRINT

A/C DATE UTC FLT
001 08JUL03 123000 5608

Where:
• A/C : A/C Number
• DATE : actual date
• UTC : actual time
• FLT : Actual Flight number

5.15. ADL FUNCTIONS

Not provided in this DMU version.

5.16. PCMCIA FUNCTIONS

5.16.1. Generality

5.16.1.1 PCMCIA interface

The PCMCIA interface is able to accept solid state ATA cards. The logical format is the MS DOS disk format
(DMU software is not able to manage compressed disk). Only cards with 16 bits FAT are managed, cards
with 12 or 32 bits FAT are not supported.
Data are set on the card in INTEL format (LSB byte first, MSB after).
Any media inserted in the unit, which do not comply with these items, will be rejected by the DMU.
101-10002-851 Ind. I

- 140 -

Document Sagem DS - Reproduction et divulgation interdites

5.16.1.2 Power cut management

Power cut shorter than 200ms will be transparent for the DMU, i.e. any access in progress will be performed.
In case of a power cut longer than 200ms occurring while an access is in progress, the last data of the file
can be lost, but in any case the disk is not corrupted.

5.16.1.3 Disk activity indications

Two LEDs are provided on the DMU unit front face (a green led and an amber led).
These 2 LEDs are driven by the system to give some feedback to the operator on PCMCIA disk operation.
Use of the LEDs is according to following logic:
1) No disk inserted: Both LEDs are OFF.
2) A disk has just been inserted in the unit: the green led is blinking during 5sec to acknowledge disk
insertion.
3) A disk is inserted in the unit but no operation is in progress (ex: disk used for QAR recording but recording
is stopped) and no loading or downloading was performed: Both LEDs are OFF
4) A disk is inserted in the unit and a loading or downloading operation is in progress: Green led is blinking -
Amber led is OFF
5) A disk is inserted in the unit, no loading or downloading operation were performed on this disk and a
recording operation is in progress (DAR/QAR/SAR): Green led is blinking - Amber led is OFF
6) End of system software loading operation successful: both LEDs are OFF.
7) End of a downloading or database loading operation successful: Green led is ON - Amber led is off. Green
led will be switched to off when the disk is removed from the unit or on the next power on. It won’t blink in case
of recording operation (DAR/QAR/SAR).
8) End of a loading or downloading operation unsuccessful (i.e. any problem occurring leading to operation
aborted: missing files - wrong disk configuration - any control fails - ...): Green led is OFF - Amber led is ON.
9) Bad disk inserted (any fatal error leading to disk unserviceable): Green led is OFF - Amber led is ON.

5.16.1.4 PCMCIA error and status reporting

For failure detection following status and failures have to be detected:
• Invalid media inserted: the media inserted is not compatible with the standard as defined in previous
section 5.16.1.1.
• Disk format error: the logical format is not compatible with the standard as defined in previous section
5.16.1.1.
• Disk access failure: all DMU application using PCMCIA are aborted due to failures detected when
accessing to the disk.
• No disk inserted: no PCMCIA media is inserted in the unit.
• Disk full: no more space is available on the PCMCIA card.
Note: all above mentioned status belong to the PCMCIA media.
A specific maintenance word is computed by the DMU (see its description in appendix 6.3.4).
Details on error management will be described in a “software requirement specification for DMU”.

5.16.1.5 PCMCIA disk indications on MCDU

Refer to section 5.12.3.7 of this document.

5.16.1.6 PCMCIA disk indications on ACARS

Refer to section 5.13.2.2.12 of this document.
101-10002-851 Ind. I

- 141 -

Document Sagem DS - Reproduction et divulgation interdites

5.16.2. QAR recording

5.16.2.1 Generality
In case of a PCMCIA card installed in the AFDAMU unit, then the standard QAR frame provided by the
AFDAU system through an internal asynchronous HDLC line can be automatically recorded on the card (as
described in section 5.4).
A disk space ratio reserved for QAR frame recording will be programmable by the GSE. This ratio is provided
in case the same PCMCIA media is used to store different kind of data (ex: QAR ,DAR, SAR frames).
This space ratio is calculated using the total PCMCIA media space minus space reserved for special
purpose such as hardcopy and MFC data storage.
A 0 space ratio programmed on the GSE will inhibit the QAR recording function.
As a default, recording of the QAR frame will be enabled with 76% space ratio.
Two modes of recording are provided :
• CONTINUOUS MODE (recommended): Files are continuously recorded on the PCMCIA drive. When the
disk is full (i.e. allocated disk ratio is full), then the oldest recorded file is deleted, allowing the recording
to continue.
• SIMPLE MODE: Files are continuously recorded on the PCMCIA drive. When the disk is full (i.e.
allocated disk ratio is full), then recording stop.
Selection of the recording mode is done by GSE. Default mode is continuous mode.

5.16.2.2 QAR files storage on PCMCIA disk

Each record (defined by a start/stop event ) will be stored in a specific file. Each file will be assigned to a
specific name: RECxxxxx.DAT with xxxxx being a decimal number. 1st record will be REC00001.DAT, 2nd
record REC00002.DAT etc. xxxxx is incremented for each new record. It is only reset when 99999 value is
reached, or a new system software is loaded in the unit. Due to 16 bits FAT format of PCMCIA cards, the
number of QAR files per directory cannot exceed 65500.
All QAR files will be located in a specific directory. Directory name will be made of contents of A/C Tail
parameters with an extension « .QAR ».

Disk architecture will be the following:

« ROOT »\ <A/C TAIL>.QAR\ REC00001.DAT
REC00002.DAT
REC00003.DAT
REC00004.DAT

Inside each record, data are recorded in a binary form. Data are recorded on 16 bits words in Intel format
(LSB 1st). The 4 MSB (not used for QAR recording) are reserved and should be ignored.

5.16.3. DAR recording

5.16.3.1 Generality
In case of a PCMCIA card installed in the AFDAMU unit, then the programmed DAR frame can be
automatically recorded on the card (see section 5.5).
A disk space ratio reserved for DAR frame recording will be programmable by the GSE. This ratio is provided
in case the same PCMCIA media is used to store different kind of data (ex: QAR,DAR and SAR frames).
This space ratio is calculated using the total PCMCIA media space minus space reserved for special
purpose such as hardcopy and MFC data storage.
A 0 space ratio programmed on the GSE will inhibit the DAR recording function.
As a default, recording of the DAR frame will be enabled with 19% space ratio.
Two modes of recording are provided :
101-10002-851 Ind. I

- 142 -

Document Sagem DS - Reproduction et divulgation interdites

• CONTINUOUS MODE (recommended): Files are continuously recorded on the PCMCIA drive. When
the disk is full (i.e. allocated disk ratio is full), then the oldest recorded file is deleted, allowing the
recording to continue.
• SIMPLE MODE: Files are continuously recorded on the PCMCIA drive. When the disk is full (i.e.
allocated disk ratio is full), then recording stop.
Selection of the recording mode is done by GSE. Default mode is continuous mode.

5.16.3.2 DAR files storage on PCMCIA disk

Each record (defined by a start/stop event) will be stored in a specific file. Each file will be assigned to a
specific name: RECxxxxx.DAT. With xxxxx being a decimal number. 1 record will be REC00001.DAT, 2
st nd

record REC00002.DAT etc. xxxxx is incremented for each new record. It is only reset when 99999 value is
reached, or a new system software is loaded in the unit. Due to 16 bits FAT format of PCMCIA cards, the
number of DAR files per directory cannot exceed 65500.
All DAR files will be located in a specific directory. Directory name will be made of contents of A/C Tail
parameters with an extension « .REC ».

Disk architecture will be the following:

« ROOT »\ <A/C TAIL>.REC\ REC00001.DAT
REC00002.DAT
REC00003.DAT
REC00004.DAT

Inside each record, data are recorded in a binary form. Data are recorded on 16 bits words in Intel format
(LSB 1st). The 4 MSB (not used for DAR recording) are reserved and should be ignored. If during recording,
a problem occurs (lost of synchronisation), then the following recorded word will be a synchro word with a
specific value set on the 4 MSB (ex : 8247).
DAR recording files will always begin with the 1 synchro word of a frame.
st

Example:
Begin file
«0247» Synchro word 1
«0354» Data word
«0124»
«0675»
...
«05B8» Synchro word 2
...
... Data words
...
« 8247» Synchro lost – new DAR frame starting
«0354» Data word
«0124»
...
«0A47» Synchro word
...
End of file
Note : see chapter 5.5.2 for details on DAR format organization.

5.16.4. Data loader emulation

The PCMCIA card can be used to emulate data loader functions i.e.
• loading of software and customer data base,
• downloading of data (reports, standard SAR data, database export).
101-10002-851 Ind. I

- 143 -

Document Sagem DS - Reproduction et divulgation interdites

5.16.4.1 Uploading functions

5.16.4.1.1 System software loading

The PCMCIA media can contain files for software loading thus being used as an ADL.
For software loading, a system file (SOFTWARE.CNF) must be present on the root directory of the disk. No
loading operation will be performed if file SOFTWARE.CNF is not present on the disk.
This file contains the name of one or several directories where software files to be loaded can be found.
Each of these directories contains the same files as on the PDL diskette (although file config.ldr is not used).
File format is the following:
Begin file
DIR=<DIRECTORY_NAME1><CR,LF>
DIR=<DIRECTORY_NAME2><CR,LF>
End of file

The software will check each directory in the order described in SOFTWARE.CNF file. The first directory, if
any, that fulfill the loading conditions is used for software loading, otherwise no software loading is done.
Before any loading process starts, a system compatibility control has to be performed:
• It consists in checking that the software disk is dedicated to the DMU sub-system of this unit P/N.
This check is performed using the reference of the “host software”, i.e the reference of the “host software”
of the unit should be in accordance with the reference contained in the identification and control file of the
loading disk.
If the control is completed then the loading process starts.
In case of a unit that is already loaded, a new loading procedure will only be performed if a disk is introduced
in the unit after power-up, i.e. no loading attempt will be performed if, at power-up of the unit, the DMU
detects that the disk is already inserted. If the new loading attempt fails due to above control, then the DMU
continues processing with the actual “system software”.
When one directory has been loaded, then the procedure stops. No attempt to load any further directory will
be performed.
The following additional check is performed once a new system software is loaded :
the DMU system software P/N present in the acquit.mem file is compared with the one present in the DMU
source code. If they are not the same, then the alarm "DMU SYSTEM SOFTWARE IDENT ERROR" is set in
CPU WORD (see §6.3.2) and the alarm “DMU SYSTEM SOFTWARE ERROR” is set in BITE word, so the
DMU fail red light is set in front of the unit (see §5.18.2).

5.16.4.1.2 Customer data base loading

The PCMCIA media can contain files for customer database loading thus being used as an ADL.
For data base loading, a system file (DATABASE.CNF) must be present on the root directory of the disk. No
loading operation will be performed if file DATABASE.CNF is not present on the disk.
This file contains the name of one or several directories where database files to be loaded can be found.
Each of these directories contains the same files as on the ADL diskette (although file config.ldr is not used).
File format is the following:
Begin file
DIR=<DIRECTORY_NAME1><CR,LF>
DIR=<DIRECTORY_NAME2><CR,LF>
End of file

The software will check each directory in the order described in DATABASE.CNF file. The first directory, if
any, that fulfils the loading conditions is used for database loading, otherwise no loading is done.
The following controls are performed by the ″DMU system software″ before any loading process starts:
101-10002-851 Ind. I

- 144 -

Document Sagem DS - Reproduction et divulgation interdites

1) Software configuration: check that the software configuration (reference of the ″system software″ loaded in
the unit) is in accordance with the one contained in the identification and control file of the disk.
2) A/C ident compatibility: A setup database is loadable on different aircraft. The identification and control
file can contain a list of the different aircraft to load. If this list is present, the DMU should control that the
acquired A/C identification belongs to the list.
Note1: control 2 can be by-passed, i.e. a disk can be used for loading whatever is the A/C identification.
Note2: A/C identification control will be by-passed as a default.
If all the controls are completed then the loading process starts.
In case of a unit which is already loaded, a new loading procedure will only be performed if a disk is
introduced in the unit after power-up, i.e. no loading attempt will be performed if, at power-up of the unit, the
DMU detects that the disk is already inserted.
When one directory has been loaded, then the procedure stops. No attempt to load any further directory will
be performed.
Note: it is possible, on a single disk, to have both software and data base files. In that case, both
database.cnf and software.cnf files have to be present in the root directory.

5.16.4.2 Downloading functions

The PCMCIA can be used as an ADL for downloading the reports, the standard SAR recordings, the SAR
Event recordings and the database version export stored in the DMU unit.

Due to the large capacity of the PCMCIA media, a single card can be used for retrieving reports or SAR
recordings from several aircrafts.
For downloading operations, system files must be present on the root directory of the card. No automatic
downloading operation will be performed if they are not present on the card. These files are used to identify
the card as a downloading card and to indicate which kind of data has to be downloaded. They are added on
the card by the GSE, using specific screens dedicated to PCMCIA card preparation for downloading
operation.
The format of these system files is Sagem DS internal.
• For details on PCMCIA media architecture used for reports storage and report files format, refer to
section 5.16.5.1.2.
• For details on PCMCIA media architecture used for data base version export storage, refer to section
5.16.9.
• For details on PCMCIA media architecture used for SAR recordings storage, refer to section 5.16.6.

5.16.5. Report data storage on PCMCIA

5.16.5.1 Standard storage

5.16.5.1.1 Generality
Independent from normal storage in the DMU unit, all reports are automatically stored on the PCMCIA card if
the report disk space ratio (described beneath) is not zero, and if a PCMCIA disk is present.
Storage of reports on the PCMCIA board will be performed in parallel with the normal storage and will not
interfere with the standard management of reports in the unit: no link with MCDU screens ("stored report"
and "report history") and with standard output rules (PRINTER – ACARS).
A card space ratio reserved for report storage will be programmable by the GSE (default value = 5%). This
space ratio is calculated using the total PCMCIA media space minus space reserved for special purpose
101-10002-851 Ind. I

- 145 -

Document Sagem DS - Reproduction et divulgation interdites

such as hardcopy and MFC data storage. A zero value is used to disable the report recording on the
PCMCIA disk.
The DMU software secures the storage of a minimum number of reports for each types.
When the card is full (i.e.: no more space on card or allocated card ratio is full), the deletion of the oldest
recorded file will be done if there is more than C_REP_MIN_NB (GSE constant, default value = 300) number
of reports of the same type already stored. If the allocated card ratio is full and if it is impossible to delete old
records according to the previous rule, the DMU software will use a special reserve on PCMCIA card to store
the new reports. This reserve is calculated to allow the storage of C_REP_MIN_NB reports of each type
(minus the already defined report space ratio on PCMCIA card).
Note :
Even if PCMCIA disk is not present in the MPC unit during the report generation, reports can be downloaded
later from the DMU memory on a PCMCIA disk using the "downloading function", described in chapter
5.16.4.2.

5.16.5.1.2 Storage architecture

All the reports will be located in a specific directory. Directory name will be made of contents of A/C Tail
parameters with an extension « .REP ».

Inside this directory, all reports of the same type (same report number) will be stored in a specific
sub-directory. Name of this sub-directory will be REPORTxx with xx being the report number.
Each report will be stored in a specific file in ASCII format. Additional data will be added at the top of the file
for identification purpose (DATE, UTC...). Detailed format of these additional data is Sagem DS internal.
Name of the files inside the directory will be Rxxyyyyy.TXT with xx being the report number and yyyyy being
a decimal number. yyyyy starts with 0 and is incremented for each new report stored. yyyyy is only reset
when 99999 value is reached, or a new system software is loaded in the unit. Change of the PCMCIA card
will not reset this counter. Due to 16 bits FAT format of PCMCIA cards, the number of report files per
directory cannot exceed 65500.

Following is an example of card architecture for report menu tree:

« ROOT » \<A/C TAIL>.REP \REPORT15 \R1500001.TXT

\R1500002.TXT
\R1500003.TXT
\REPORTxx \...

5.16.5.2 Filtered cruise report storage

For trend monitoring, cruise report are filtered and stored in a specific directory. They are then downloaded
by external equipments. Directory name is made of content of A/C Tail parameters with an extension “.ECT”
Inside this directory, selected cruise reports will be stored in a single file destined to ECTM import named
TRENDYYY.DAT, with YYY being a decimal number. YYY starts with 1 and is incremented for each new file.
YYY is only reset when 999 value is reached, or a new system software is loaded in the unit. Change of the
PCMCIA card will not reset this counter.
The current TRENDYYY.DAT file will be used for filtered report storage as long as it is not downloaded by
the external equipment (see 5.17.6). Once the current TRENDYYY.DAT is downloaded, a new
TRENDYYY.DAT is created.
Following is the card architecture for filtered cruise report storage:

« ROOT » \<A/C TAIL>.ECT \TRENDYYY.DAT

101-10002-851 Ind. I

- 146 -

Document Sagem DS - Reproduction et divulgation interdites

The constant C_PCMCIA_ECT programmable with GSE will define a maximum size in Kbytes for storage of
filtered cruise reports on the PCMCIA disk. When the card is full (i.e. no more space on card or allocated
amount for filtered report is full), then the oldest recorded TRENDYYY.DAT file is deleted, allowing the
storage of new reports. If that constant is set to zero, filtered cruise report storage will be disabled.
If there is no file to delete – only one TRENDYYY.DAT file currently in use, then if this file size reaches the
C_PCMCIA_ECT amount, the recording of new filtered report is stopped. The reserved amount will allow the
recording of at least a thousand filtered report.

5.16.6. SAR data storage on PCMCIA

5.16.6.1 Generality
a) Standard SAR and SAR Event
Independently from normal storage in NVRAM, Standard SAR and SAR Event recordings are automatically
stored on the PCMCIA card if the SAR disk space ratio (described beneath) is not zero, and if a PCMCIA
disk is present.
Storage of SAR data on the PCMCIA board will be performed in parallel with the normal storage and will not
interfere with the standard management of SAR in the unit (no link with MCDU screens).
Note :
Even if the PCMCIA disk is not present in the MPC unit during the SAR recording, Standard SAR and SAR
Event data can be downloaded later from the DMU memory on a special PCMCIA disk, using the
"downloading function" described in 5.16.4.2.
b) Extended SAR
These SAR channels are directly stored on PCMCIA disk card if the SAR disk space ratio (described
beneath) is not zero, and if a PCMCIA disk is present. When the PCMCIA card is not inserted or the SAR
disk space ratio is zero, the extended SAR is disabled as it is not stored in NVRAM.
c) All SAR channels
A disk space ratio reserved for SAR storage on the PCMCIA will be programmable in the GSE. This disk
space ratio is allocated for the whole SAR function (standard SAR, Extended SAR and SAR Event). A zero
value is used to disable the SAR recording on the PCMCIA disk. Default programming will be no SAR
storage on PCMCIA disk.
SAR records are continuously recorded on the PCMCIA drive (when the function is active). When the disk is
full (i.e.: no more space on disk or allocated disk ratio is full), then the oldest recorded file is deleted, allowing
the storage of new SAR records.

5.16.6.2 Storage architecture

All SAR data will be located in a specific directory. Directory name will be the A/C TAIL of the A/C with an
extension ".SAR".
Inside this directory, all SAR records of the same partition will be stored in a specific sub-directory SAR_X
(X=1 to 4) :
SAR Type SAR partition SAR sub-
directory
name
Standard SAR SAR Data recording (Data Set 1 to 4) SAR_1
SAR extended trouble shooting (Data Set 5 to 8) SAR_2
SAR Event Event Recording SAR_3
Extended SAR Data Recording (Data Set 9 to 16) SAR_4

Each SAR record will be stored in a specific file (Sagem DS internal format).
101-10002-851 Ind. I

- 147 -

Document Sagem DS - Reproduction et divulgation interdites

Name of the files inside the directory will be SAxyyyyy.DAT with : x being the SAR function ident and yyyyy
being a decimal number. yyyyy starts with 0 and is incremented for each new record stored. yyyyy is only
reset when 99999 value is reached, or a new system software is loaded in the unit. Change of the PCMCIA
disk will not reset this counter. Due to 16 bits FAT format of PCMCIA cards, the maximum number of
SAxyyyyy.DAT files per directory cannot exceed 65500.
Following is an example of disk architecture for SAR menu tree:

« ROOT » \<A/C TAIL>.SAR \SAR_1 \SA100000.DAT

\SA100001.DAT
\SA100002.DAT
\SAR_2 \SA200000.DAT
\SA200001.DAT
\SAR_3 \SA300000.DAT
\SA300001.DAT
\SAR_4 \SA400000.DAT
\SA400001.DAT

5.16.7. MFC fault words storage on PCMCIA disk

Upon operator order though the MCDU, the DMU software download all MFC faults data and write it on the
PCMCIA disk.
Each storage of MFC data will be stored in a specific file. Each file will be assigned to a specific name:
MFCxxxxx.TXT with xxxxx being a decimal number. 1st record will be MFC00001.TXT, 2nd record
MFC00002.TXT etc. xxxxx is incremented for each new record. It is only reset when 99999 value is reached,
or if the files on the disk are deleted. Due to 16 bits FAT format of PCMCIA cards, the number of
MFCxxxxx.TXT files per directory cannot exceed 65500.
All MFC data files will be located in a specific directory. Directory name will be made of contents of A/C Tail
parameters with an extension « .MFC ».

Disk architecture will be the following:

« ROOT » \<A/C TAIL>.MFC \MFC00001.TXT
\MFC00002.TXT
\MFC00003.TXT

The constant C_PCMCIA_MFC programmable with GSE will define a maximum size in Kbytes of MFC fault
words record on the PCMCIA disk. When this maximum size is reached, the software delete old records in
order to store new ones. If that constant is set to zero, the MFC fault words storage on PCMCIA is disabled.
This size is subtracted to the PCMCIA maximum disk space for calculation of the different disk quotas.

Inside each record, MFC fault words data are recorded in a ASCII text form. The files are readable using a
text editor and each fault stored is described with a few lines of text. A header indicates the date, the MFC
version and the A/C tail. The faults stored in the basic memory are first recorded, and then the fault in the
flight fault memory for each flight from the last to the oldest flight stored. Only system with faults recorded are
recorded.
Example of MFC record:
AUG-10-2005
MFC S4
AIRCRAFT F-WWEY
BASIC MEMORY
************

SYSTEM 2 : DOORS
9: ST3 EMER HATCH PROX SW FAIL - 38WS (52.71)

SYSTEM 5 : BRAKE
101-10002-851 Ind. I

- 148 -

Document Sagem DS - Reproduction et divulgation interdites

6: LH OUTBRD XMTER PWR LOSS/OUT OPEN - 35GG (ATA 32.42)

5: LH INBRD XMTER PWR LOSS/OUT OPEN - 37GG (ATA 32.42)
8: RH OUTBRD XMTER PWR LOSS/OUT OPEN - 34GG (ATA 32.42)
7: RH INBRD XMTER PWR LOSS/OUT OPEN - 36GG (ATA 32.42)

SYSTEM 6 : FLIGHT CONTROL

9: FLAPS POS SW FAIL - 8CV (ATA 27.51)

****************************************

FLIGHT FAULT MEMORY

*******************
FLIGHT 0

SYSTEM 5 : BRAKE
6: LH OUTBRD XMTER PWR LOSS/OUT OPEN - 35GG (ATA 32.42)
5: LH INBRD XMTER PWR LOSS/OUT OPEN - 37GG (ATA 32.42)
8: RH OUTBRD XMTER PWR LOSS/OUT OPEN - 34GG (ATA 32.42)
7: RH INBRD XMTER PWR LOSS/OUT OPEN - 36GG (ATA 32.42)

SYSTEM 6 : FLIGHT CONTROL

9: FLAPS POS SW FAIL - 8CV (ATA 27.51)

****************************************

FLIGHT -1

SYSTEM 2 : DOORS
9: ST3 EMER HATCH PROX SW FAIL - 38WS (52.71)

****************************************

FLIGHT -2

****************************************

FLIGHT –3

****************************************

FLIGHT -4

****************************************

FLIGHT –5

****************************************

FLIGHT –6

****************************************

FLIGHT -7

****************************************

FLIGHT –8

****************************************

END OF TEXT

5.16.8. Hardcopy of MCDU screens on PCMCIA disk

If a PCMCIA is present and available, MCDU screens are stored on PCMCIA disk when the "PRINT" key is
pressed (whatever the state of the PRINTER).
All hardcopy data files will be located in a specific directory. Directory name will be made of contents of A/C
Tail parameters with an extension ".HCP".
101-10002-851 Ind. I

- 149 -

Document Sagem DS - Reproduction et divulgation interdites

Name of the files will be HCPxxxxx.TXT. 1st file will be HCP00001.TXT, 2nd file HCP00002.TXT etc. xxxxx is
incremented for each new record. It is only reset when 99999 value is reached, or a new database is loaded
in the unit. Due to 16 bits FAT format of PCMCIA cards, the number of HCPxxxxx.TXT files per directory
cannot exceed 65500.
Disk architecture will be the following :

« ROOT » \<A/C TAIL>.HCP \HCP00001.TXT

\HCP00002.TXT
\HCP00003.TXT

Each file is recorded in ASCII text form and contains the same data as the one sent to PRINTER.
Hardcopy PCMCIA function is available in the MCDU screens containing a PRINT function (LSK 6R key).

Displayed messages of this capability are listed in chapter 5.12.2.3 .

The constant C_PCMCIA_HCY programmable with GSE will define a maximum size in Kbytes of hardcopy
record on the PCMCIA disk. When this maximum size is reached, the software delete old records in order to
store new ones. If that constant is set to zero, the hard copy PCMCIA function is disabled.
This size is subtracted to the PCMCIA maximum disk space when calculation of the different disk quotas.

5.16.9. Data base version storage

Data base version export when downloaded by the DMU (see 5.16.4.2) is located in a specific directory.
Directory name will be made of contents of A/C Tail parameters with an extension « .DB ».

Inside this directory, a single file can be recorded, i.e. a single data base version can be downloaded and
stored on the card. Any new download will overwrite this file.
Name of the file is GSEDBV.VEC.

5.16.10. A/C Tail storage

The A/C Tail parameter is stored in a file named "ACTAIL.TXT" in the root directory of the PCMCIA disk. This
file is created when the PCMCIA disk is inserted in the unit. It is updated when the operator changes A/C Tail
with MCDU screen "A/C PARAM INIT", described in §5.12.3.12.1.1.1.
It will hold a single line of text, which will be the A/C tail of current aircraft followed by a carriage return + line
feed (0x0D, 0x0A).

5.17. ETHERNET FUNCTION

5.17.1. Generalities

The DMU is able to communicate with external equipment through an Ethernet interface, which is provided
by the Motorola MPC860T. This micro-controller has a Fast Ethernet Controller embedded and gives the
ability to establish a 10/100 Mbits/s link on Area Network.
The Ethernet interface has a full compliance with the IEEE 802.3 standard and supports full-duplex and half-
duplex operations.
101-10002-851 Ind. I

- 150 -

Document Sagem DS - Reproduction et divulgation interdites

5.17.2. Implemented network protocols in the DMU

The DMU has the ability to communicate (reception and emission) across the network with various protocols
due to a TCP/IP stack embedded in the software.
The implemented protocols in the DMU are:
• IP (described in RFC 791) see [O01]
• TCP (described in RFC 793) see [O02]
• UDP (described in RFC 768) see [O03]
• FTP (described in RFC 959) see [O04]

5.17.3. Ethernet start/stop control

The TCP/IP stack is launched if all the following conditions are met:
• The DMU shunt discrete NXG (see [S01]), assigned for enabling the stack, is grounded,
• The flight mode is one of pre-flight(1), taxi-out(2), taxi-in(9), post-flight(10) (see §5.2.2.1),
• The Ethernet wire is plugged.
The TCP/IP stack is stopped if one of the following condition is met:
• The flight mode is not one of pre-flight(1), taxi-out(2), taxi-in(9), post-flight(10) (see §5.2.2.1),
• The Ethernet wire is unplugged.

5.17.4. Ethernet configuration

If an Ethernet configuration has been entered in Ethernet init param screen (see §5.12.3.12.2), then it is
used, else the GSE Ethernet configuration is used if defined, else the default Ethernet configuration is used:
IP address 192.168.1.1
Subnet mask 255.255.255.0
Gateway address 192.168.1.255
MAC address 00.60.4C.2D.30.00

After a new software is loaded or after loss of NVRAM, the GSE Ethernet configuration is used if defined,
else the default is used.
Note: only the parameters of the sheet “IP configuration” of the GSE Ethernet configuration panel are used
by the MPC DMU (local IP address, Subnet mask and Gateway address). All the other parameters of the
panel aren’t used by the DMU and can be set to any value without influence on the DMU. The MAC address
isn’t set by the GSE, in case of GSE configuration defined, it will have the same default value than in above
array until modified through the MCDU page (see §5.12.3.12.2).
101-10002-851 Ind. I

- 151 -

Document Sagem DS - Reproduction et divulgation interdites

5.17.5. Alarms associated to Ethernet function

5.17.5.1 General maintenance word

Following alarms in the general maintenance word (see 6.3.3) are associated to the Ethernet function :
Internal alarms:
• "IP stack init failure": this software alarm is set if an error is detected during the stack initialisation
or if the shunt discrete NXG is not grounded when the DMU is powered on.
• "IP stack failure": this software alarm is set if an error is detected during the stack polling. This error
can be due to the bad state of the DMU shunt discrete NXG or to the flight mode having a value in
the interval [ Take-off Roll Initial (3), Landing roll (8) ] ( see 5.17.3).
• “Ethernet autotest failure”: this hardware alarm is set if the Ethernet autotest (see 5.18.1) has
failed.
External alarm:
• “Ethernet link failure” : this hardware alarm is set if the Ethernet wire is unplugged or if it is not
detected.

5.17.5.2 BITE maintenance word

Following alarm in the BITE maintenance word (see 6.3.1) is associated to the Ethernet function :
• “Ethernet interface failure“ : this alarm is set if the alarm “Ethernet autotest failure” is set in the
general maintenance word.

5.17.6. FTP Transmission

The MPC will allow any external equipment connected by Ethernet to download any of the PCMCIA card
files through an FTP server. So the external equipment will be a FTP client.
Connection to the FTP server of MPC will be possible only if the IP stack is running (see 5.17.3).
The FTP client will use a login and password to connect to the MPC FTP server. These authorised login and
passwords for an FTP connection to the DMU are given in the following table :
Login Password
Pratt Whitney
ATR MPC

To avoid duplicate downloads, the DMU FTP server provide two custom FTP commands allowing to list files
to be downloaded inside one directory (dirnew) and to mark one file as "downloaded" when its download is
over (setdownloaded).
The MPC will reject any writing or deleting operation on PCMCIA card by the external equipment (except the
setdownloaded command which modifies attributes of the file).

5.17.6.1 dirnew command

This command, based on FTP "dir" command, allows the external equipment to list all the files to download
inside the remote current directory, which are the files not marked yet with setdownloaded command.
Syntax : dirnew
Returned message : <filename1>
<filename2>
etc
101-10002-851 Ind. I

- 152 -

Document Sagem DS - Reproduction et divulgation interdites

See §5.17.6.4 for error codes associated to this command.

5.17.6.2 setdownloaded command

This command allows the external equipment to mark one file as downloaded after its download.
Syntax : setdownloaded <filename>
See §5.17.6.4 for error codes associated to this command.

5.17.6.3 File transfert sequence

File transfer operation should be as follow:
1. when the flight phase becomes 1, 2, 9 or 10 (see §5.2.2.1), then the FTP server is activated,
2. an external equipment connects to the MPC as a FTP client using a preconfigured login/password,
3. the external equipment browses through the PCMCIA card directories seeking for files to download with
dirnew command,
4. if such files are found, the external equipment downloads each of them, else it disconnects itself from MPC,
5. for each file to download, if the file transfer is successful, the external equipment mark it as "downloaded"
using setdownloaded command,
6. the external equipment goes back to step 3,
7. if the flight phase changes to another phase than 1, 2, 9 or 10, the MPC shut down the FTP server ; if a file
download operation was in progress, the download is broken ; if a setdownloaded command was in
progress, it is completed.

The MPC will transfer the files as recorded on PCMCIA card.

5.17.6.4 Error handling

List of errors managed by the FTP server:

Command Error case Error message
N.A. login or password not recognised: no operation is "Login or password not
possible. recognised: no operation is
possible"
All No PCMCIA disk inserted in MPC DMU: no “Can not list directory content
operation is possible. of ‘ ’ “
All New PCMCIA disk inserted while connected: the “New PCMCIA disk inserted.
FTP client should disconnect from the MPC and Please quit and login to FTP
then reconnect. server.”
Command Directory does not exist or invalid “Can not change directory to
directory (cd, ls) <directory_name>“
Delete file File does not exist, invalid, or in-writing “Can not delete <file_name> “
(delete)
Delete directory Directory does not exist or invalid “Can not delete
(delete) <directory_name>"
Get file (get) File does not exist or invalid “Can not open <file_name>“
Get directory Directory does not exist or invalid “Can not open
(get) <directory_name>“
setdownloaded - File is currently opened by the MPC DMU "Can not mark
software (may happen if a QAR, DAR <path>\<file_name> as
101-10002-851 Ind. I

- 153 -

Document Sagem DS - Reproduction et divulgation interdites

Command Error case Error message

recording is still running, as these recordings downloaded"
are only stopped one minute after engine
shutdown; this should not happen for report
files). The operation is impossible; to avoid
duplicate download, the FTP client should
discard the downloaded file it just try to mark
on MPC DMU, process the other files and try
again.
- File does not exist
setdownloaded The file is already marked as downloaded "The file <path>\<file_name>
has already been
downloaded"
The command listed above are not the only supported commands. The MPC FTP server support all the
standard FTP commands (see RFC 959).

5.18. AUTOTEST AND BITE FUNCTION

The DMU checks the validity of the system using self-test routines. Several autotests are performed either at
power-up of the unit or continuously during execution of the DMU application.
As a result of power-up or continuous tests, the DMU computes maintenance words as defined in
appendix6.3.

5.18.1. List of autotests

Following autotests have to be provided by the DMU:
• ARINC 429 channels autotest
◊ Test at power-up of input busses,
◊ Test at power-up of peripheral outputs,
◊ Continuous test of acquisition busses for internal/external failure determination.
• Input discrete test at power-up,
• Output discrete test at power-up,
• Power supply autotest: at power-up and in background,
• Watchdog restart detection,
• Test of accumulators at restart,
• Test of memories:
◊ Working RAM memory test at restart
◊ NVRAM memory test at restart
◊ Flash prom memory test when writing data (read back of written data).
• Software integrity test:
◊ Host software checksum calculation at restart,
◊ “DMU system software” checksum calculation at restart,
◊ “DMU system software ident” consistency check at restart,
◊ “DMU set-up data base” checksum calculation at restart
101-10002-851 Ind. I

- 154 -

Document Sagem DS - Reproduction et divulgation interdites

• Software failure detection:

◊ Stack overflow detection
◊ CPU overload detection
◊ GSE logic failure detection
• PCMCIA media test (see section 5.16.1.4).
• Ethernet autotest:
◊ Continuous test of Ethernet working for internal failure detection if the stack is started (see
§5.17.3)
Detailed description of autotests will be found in a software requirements specification for DMU.

5.18.2. Bite computation and reporting

A maintenance word (BITE word) will summarise all the internal autotests performed by the DMU, and give
the “working state” of the unit.
Only DMU internal failures are reported in this BITE word. This BITE word is refreshed at a 1Hz state
according to the last tests performed.
BITE result will also set the DMU fail red light in front of the unit.
Refer to section 6.3.1 for BITE word description.

5.18.3. Alarm storage

The DMU will store all detected alarms in Flash PROM for shop maintenance purpose. At least 40 failures
have to be stored in the unit.
All internal faults (BITE) will be stored.
All software failures and PCMCIA media failures (except no media inserted failure) will be stored.
All ARINC 429 external failures will be stored during "Air" flight mode.
Note: ADL external failures will not be stored. ACARS and Printer failures will not be stored if those systems
are not installed.
A BITE storage will consists of:
• All maintenance words of the system,
• Documentary data such as Date – UTC – flight number – flight mode – A/C tail - …
Note: BITE records are only reset in case a new release of software is loaded and the BITE storage structure
is not compatible.

5.19. CHECKS AND RESET ACTIONS

The DMU checks the validity of the system configuration (pin-programming). This checks are performed
either at restart of the unit or continuously during execution of the DMU application.

5.19.1. Checks at restart

5.19.1.1 Check of A/C ident

This check can be performed only if the database has been uploaded along with a list of A/C Tail defined on
the GSE.
In this case, at each power-up the DMU has to check if the A/C ident (A/C Number + A/C Type) has changed
since the last power-up.
101-10002-851 Ind. I

- 155 -

Document Sagem DS - Reproduction et divulgation interdites

Test of A/C ident is performed when A/C Number and A/C Type have been received from AFDAU.
The test consists in checking if the current A/C Number and A/C Type are the same as the memorised ones.
If a change is detected one of the following two situations may happen:
1) If the A/C tail is part of the list loaded with the set-up database, the set-up database is then compatible with
this new A/C and no loading procedure shall be requested.
The following memorised data shall be cleared from NVRAM:
• Reports.
• SAR (record and statistic).
• Temporary changes.
2) If the A/C tail is not part of the list loaded with the set-up data base, the set-up data base is then not
compatible with this new A/C. In that case, loading of a new data-base is required and the DMU performs
following actions:
• Stop any processing.
• Set DMU Bite signal to fail.

5.19.2. Continuous Checks

Following continuous tests are accomplished by the DMU:

• ARINC429 autotests
• Ethernet autotest if the stack is started (see §5.17.3)
• EEC data invalidity monitoring (see §5.12.3.1.2)
• LCF component accumulated cycles monitoring (see §5.12.3.1.2)

5.19.3. Reset after loading operation

5.19.3.1 Reset after system software loading

The first time a new ″system software″ runs, all memorised data are cleared i.e.:
• Set-up data base area.
• Reports.
• SAR (record memory and statistic memory).
• Temporary changes.

5.19.3.2 Reset after set-up data base loading

After loading of a new "set-up database", the following memorised data are cleared:
• Reports.
• SAR statistic memory (but not the SAR record memory)
• Temporary changes.

5.20. LIGHT TEST

If the light test shunt discrete input (also called APM Enable Test) is active (i.e. grounded), the “SYSTEM
STATUS” and “FDAU STATUS” light are lit and the following sequence is output on APM level output
discrete:
− APM level 1 inactive, APM level 2 active, for one second,
− APM level 1 active, APM level 2 inactive, for one second,
− APM level 1 active, APM level 2 active, as long as the light test discrete input is active.
101-10002-851 Ind. I

- 156 -

Document Sagem DS - Reproduction et divulgation interdites

If the light test discrete input come back to inactive state, the sequence is immediately ended.

5.21. POWER-DOWN LOGIC/POWER-UP INITIALIZATION

5.21.1. Transparency
The AFDAMU unit is transparent to power shut down below 28 V for up to 200ms. No short cut/hot start
mechanism is then required.

5.21.2. LONG cut/COLD start

When power shut down below 28 V for greater than 200 ms, the DMU then stops any processing and will
start in full initialisation on the next power-up.
101-10002-851 Ind. I

- 157 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6. APPENDICES

6.1. DEFINITION OF AIRCRAFT PARAMETERS

6.1.1. External ARINC 429 parameters

The parameters acquired on external ARINC 429 buses are listed in the following table.
Source1 Source2 Sign Data Update
Parameter Name Description Type Name MSB
(Equip/Label/SDI) (Equip/Label/SDI) Bit Bits Rate
ACNAMEC01_02 A/C type name char 1 and 2 CHARACTER AFDAU/124/00 - - 28 16 1
ACNAMEC03_04 A/C type name char 3 and 4 CHARACTER AFDAU/125/00 - - 28 16 1
ACNAMEC05_06 A/C type name char 5 and 6 CHARACTER AFDAU/126/00 - - 28 16 1
ACNAMEC07_08 A/C type name char 7 and 8 CHARACTER AFDAU/127/00 - - 28 16 1
ACTYPE A/C Type PACKED BITS AFDAU/002/01 - - 24 4 1
AIR_GD_V0 Air/Ground for the V0 config DISCRETE AFDAU/002/01 - - 15 1 1
ALT_1 Altitude pressure from ADC-1 (No SSM) BNR LINEAR (A*X) ADC-1/203/ - 29 26 15 1
ALT_1_SSM Altitude pressure SSM from ADC-1 PACKED BITS ADC-1/203/ - - 31 2 1
ALT_2 Altitude pressure from ADC-2 (No SSM) BNR LINEAR (A*X) ADC-2/203/ - 29 26 15 1
ALT_2_SSM Altitude pressure SSM from ADC-2 PACKED BITS ADC-2/203/ - - 31 2 1
APM_APM_ON APM APIU APM ON discrete DISCRETE AFDAU/005/01 - - 22 1 8
APM_DEGRADED APM APIU degraded performance discrete DISCRETE AFDAU/005/01 - - 24 1 8
APM FAULT discrete coming from AFDAU
APM_FAULT DISCRETE AFDAU/004/00 - - 17 1 1
bite
APM_INCREASE APM APIU increase speed discrete DISCRETE AFDAU/005/01 - - 25 1 8
APM_SPEEDLOW APM APIU cruise speed low discrete DISCRETE AFDAU/005/01 - - 23 1 8
APMALTICAPT APM altitude capture mode DISCRETE AFDAU/032/01 - - 23 1 1
APMANTIICING APM anti-icing DISCRETE AFDAU/032/01 - - 25 1 1
APMCXAC60S APM CX aircraft average on 60s coefficient BNR LINEAR (A*X) AFDAU/044/01 - - 28 15 1
APM CX theoretical average on 60s
APMCXTH60S BNR LINEAR (A*X) AFDAU/043/01 - - 28 15 1
coefficient
APMCZ APM CZ coefficient BNR LINEAR (A*X) AFDAU/042/01 - - 28 18 1
APMDEICING APM de-icing (also called icing AOA) DISCRETE AFDAU/032/01 - - 26 1 1
APMFLAPS APM flaps position ou Trailing edge flap BNR LINEAR (A*X) AFDAU/023/01 - 29 28 11 1
APMGAMMA APM gamma coefficient BNR LINEAR (A*X) AFDAU/050/01 - 29 28 14 1
APMGEAR APM selected landing gear position DISCRETE AFDAU/032/01 - - 27 1 1
APMIAS APM selected indicated air speed BNR LINEAR (A*X) AFDAU/021/01 - - 28 12 1
APMIASTH APM theoretical indicated airspeed BNR LINEAR (A*X) AFDAU/045/01 - - 28 8 1
APMICEDETECT APM ice detector DISCRETE AFDAU/032/01 - - 24 1 1
APMJX APM longitudinal acceleration BNR LINEAR (A*X) AFDAU/030/01 - 29 28 11 1
APMLEVEL1 APM level 1 output DISCRETE AFDAU/052/01 - - 12 1 16
APMLEVEL2 APM level 2 output DISCRETE AFDAU/052/01 - - 13 1 16
APMMSIS APM minimum severe icing speed BNR LINEAR (A*X) AFDAU/046/01 - - 28 8 1
APMNP1 APM NP1 (Left prop. rot. speed) BNR LINEAR (A*X) AFDAU/024/01 - - 28 12 1
APMNP2 APM NP2 (Right prop. rot. speed) BNR LINEAR (A*X) AFDAU/025/01 - - 28 12 1
APMPITCH APM pitch position BNR LINEAR (A*X) AFDAU/031/01 - 29 28 11 1
APMROTW APM rotator weight BNR LINEAR (A*X) AFDAU/040/01 - - 28 15 1
APMSAT APM selected static air temperature BNR LINEAR (A*X) AFDAU/022/01 - 29 28 11 1
APMTAS APM true airspeed BNR LINEAR (A*X) AFDAU/047/01 - - 28 9 1
APMTQ1 APM TQ1 (Left Propeller torque) BNR LINEAR (A*X) AFDAU/026/01 - - 28 12 1
APMTQ2 APM TQ2 (Right propeller torque) BNR LINEAR (A*X) AFDAU/027/01 - - 28 12 1
APMTRACTION APM traction BNR LINEAR (A*X) AFDAU/051/01 - 29 28 16 1
APMWEIGHT APM weight (KG) BNR LINEAR (A*X) AFDAU/041/01 - - 28 15 1
APMWEIGHT_T APM weight (TON) for Cruise report display BNR LINEAR (A*X) AFDAU/041/01 - - 28 15 1
APMZP APM selected pressure altitude BNR LINEAR (A*X) AFDAU/020/01 - 29 28 15 1
ATR42OR72 ATR 42 / ATR 72 selection discrete DISCRETE AFDAU/123/00 - - 15 1 1
BITE1_LSB Maintenance word BITE1 LSB PACKED BITS AFDAU/002/00 - - 28 16 2
BITE1_MSB Maintenance word BITE1 MSB PACKED BITS AFDAU/001/00 - - 28 16 2
BITE2_LSB Maintenance word BITE2 LSB PACKED BITS AFDAU/004/00 - - 28 16 2
BITE2_MSB Maintenance word BITE2 MSB PACKED BITS AFDAU/003/00 - - 28 16 2
CAS_1 Computed Air Speed from ADC-1 (No SSM) BNR LINEAR (A*X) ADC-1/206/ - - 28 10 1
CAS_1_SSM Computed Air Speed SSM from ADC-1 PACKED BITS ADC-1/206/ - - 31 2 1
101-10002-851 Ind. I

- 158 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Source1 Source2 Sign Data Update

Parameter Name Description Type Name MSB
(Equip/Label/SDI) (Equip/Label/SDI) Bit Bits Rate
CAS_2 Computed Air Speed from ADC-2 (No SSM) BNR LINEAR (A*X) ADC-2/206/ - - 28 10 1
CAS_2_SSM Computed Air Speed SSM from ADC-2 PACKED BITS ADC-2/206/ - - 31 2 1
CD_L_V2A Current detector left for V2A configuration BNR LINEAR (A*X) ED34-BC/047/00 - - 28 12 1
CD_R_V2A Current detector right for V2A configuration BNR LINEAR (A*X) ED34-BC/050/00 - - 28 12 1
BNR SEGMENTS
CXDRAGINC CXa/c drag increment for APM MFC-1A/001/ - - 28 3 1
(A*X+B)
DI1CNFC01_02 Discret configuration 1 name char 1 and 2 CHARACTER AFDAU/140/00 - - 28 16 1
DI1CNFC03_04 Discret configuration 1 name char 3 and 4 CHARACTER AFDAU/141/00 - - 28 16 1
DI1CNFC05_06 Discret configuration 1 name char 5 and 6 CHARACTER AFDAU/142/00 - - 28 16 1
DI1CNFC07_08 Discret configuration 1 name char 7 and 8 CHARACTER AFDAU/143/00 - - 28 16 1
DI2CNFC01_02 Discret configuration 2 name char 1 and 2 CHARACTER AFDAU/144/00 - - 28 16 1
DI2CNFC03_04 Discret configuration 2 name char 3 and 4 CHARACTER AFDAU/145/00 - - 28 16 1
DI2CNFC05_06 Discret configuration 2 name char 5 and 6 CHARACTER AFDAU/146/00 - - 28 16 1
DI2CNFC07_08 Discret configuration 2 name char 7 and 8 CHARACTER AFDAU/147/00 - - 28 16 1
DI3CNFC01_02 Discret configuration 3 name char 1 and 2 CHARACTER AFDAU/150/00 - - 28 16 1
DI3CNFC03_04 Discret configuration 3 name char 3 and 4 CHARACTER AFDAU/151/00 - - 28 16 1
DI3CNFC05_06 Discret configuration 3 name char 5 and 6 CHARACTER AFDAU/152/00 - - 28 16 1
DI3CNFC07_08 Discret configuration 3 name char 7 and 8 CHARACTER AFDAU/153/00 - - 28 16 1
DI4CNFC01_02 Discret configuration 4 name char 1 and 2 CHARACTER AFDAU/154/00 - - 28 16 1
DI4CNFC03_04 Discret configuration 4 name char 3 and 4 CHARACTER AFDAU/155/00 - - 28 16 1
DI4CNFC05_06 Discret configuration 4 name char 5 and 6 CHARACTER AFDAU/156/00 - - 28 16 1
DI4CNFC07_08 Discret configuration 4 name char 7 and 8 CHARACTER AFDAU/157/00 - - 28 16 1
DI5CNFC01_02 Discret configuration 5 name char 1 and 2 CHARACTER AFDAU/160/00 - - 28 16 1
-DI5CNFC03_04 Discret configuration 5 name char 3 and 4 CHARACTER AFDAU/161/00 - - 28 16 1
DI5CNFC05_06 Discret configuration 5 name char 5 and 6 CHARACTER AFDAU/162/00 - - 28 16 1
DI5CNFC07_08 Discret configuration 5 name char 7 and 8 CHARACTER AFDAU/163/00 - - 28 16 1
DI6CNFC01_02 Discret configuration 6 name char 1 and 2 CHARACTER AFDAU/164/00 - - 28 16 1
DI6CNFC03_04 Discret configuration 6 name char 3 and 4 CHARACTER AFDAU/165/00 - - 28 16 1
DI6CNFC05_06 Discret configuration 6 name char 5 and 6 CHARACTER AFDAU/166/00 - - 28 16 1
DI6CNFC07_08 Discret configuration 6 name char 7 and 8 CHARACTER AFDAU/167/00 - - 28 16 1
DISCGP_0 AFDAU discrete group 0 PACKED BITS AFDAU/001/01 - - 26 16 8
DISCGP_1 AFDAU discrete group 1 PACKED BITS AFDAU/002/01 - - 26 16 8
DISCGP_2 AFDAU discrete group 2 PACKED BITS AFDAU/003/01 - - 26 16 8
DISCGP_3 AFDAU discrete group 3 PACKED BITS AFDAU/004/01 - - 26 16 8
DISCGP_4 AFDAU discrete group 4 PACKED BITS AFDAU/005/01 - - 26 16 8
DISCGP_5 AFDAU discrete group 5 PACKED BITS AFDAU/006/01 - - 26 16 8
Serie discrete B58 of AFDAU : DTUE
DTUE_FAULTST DISCRETE AFDAU/006/01 - - 12 1 8
FAULT STATUS
Serie discrete B59 of AFDAU : DTUE
DTUE_TRANSST DISCRETE AFDAU/006/01 - - 20 1 8
TRANSMISSION STATUS
EEC_SELECTED Failure code on PEC/EEC 1 DISCRETE AFDAU/006/01 - - 11 1 1
ENGINE Engine (conv or EEC) DISCRETE AFDAU/123/00 - - 17 1 1
ENGTYPE Engine type PACKED BITS AFDAU/002/01 - - 24 4 1
Flag set to 1 for FDAU P/N
FDAU_CONF_1 DISCRETE AFDAU/122/00 - - 24 1 1
36045172A01/1E01/1E21
Number of selected input PCM FDR frame
FDR_IN_DTF PACKED BITS AFDAU/115/00 - - 20 4 1
(from FDAU)
FDR_IN_RATE Input PCM FDR rate (from FDAU) PACKED BITS AFDAU/115/00 - - 26 3 1
FDR_OUT_DTF Number of selected output PCM FDR frame PACKED BITS AFDAU/115/00 - - 16 4 1
FDR_OUT_RATE Output PCM FDR rate PACKED BITS AFDAU/115/00 - - 23 3 1
FF_L_V2A Fuel Flow Left for V2A configuration BNR LINEAR (A*X) ED34-BC/013/00 - - 28 10 1
FF_R_V2A Fuel Flow Right for V2A configuration BNR LINEAR (A*X) ED34-BC/014/00 - - 28 10 1
FFSCHAR01_02 FFS char 1 & 2 CHARACTER AFDAU/100/01 - - 28 16 32
FFSCHAR03_04 FFS char 3 & 4 CHARACTER AFDAU/101/01 - - 28 16 32
FFSCHAR05_06 FFS char 5 & 6 CHARACTER AFDAU/102/01 - - 28 16 32
FFSCHAR07_08 FFS char 7 & 8 CHARACTER AFDAU/103/01 - - 28 16 32
FFSCHAR09_10 FFS char 9 & 10 CHARACTER AFDAU/104/01 - - 28 16 32
FFSCHAR11_12 FFS char 11 & 12 CHARACTER AFDAU/105/01 - - 28 16 32
FFSCHAR13_14 FFS char 13 & 14 CHARACTER AFDAU/106/01 - - 28 16 32
FFSCHAR15_16 FFS char 15 & 16 CHARACTER AFDAU/107/01 - - 28 16 32
FFSCHAR17_18 FFS char 17 & 18 CHARACTER AFDAU/110/01 - - 28 16 32
FFSCHAR19_20 FFS char 19 & 20 CHARACTER AFDAU/111/01 - - 28 16 32
FFSCHAR21_22 FFS char 21 & 22 CHARACTER AFDAU/112/01 - - 28 16 32
FFSCHAR23_24 FFS char 23 & 24 CHARACTER AFDAU/113/01 - - 28 16 32
FFSCHAR25_26 FFS char 25 & 26 CHARACTER AFDAU/114/01 - - 28 16 32
FFSCHAR27_28 FFS char 27 & 28 CHARACTER AFDAU/115/01 - - 28 16 32
FFSLIGNE FFS line PACKED BITS AFDAU/116/01 - - 14 2 32
101-10002-851 Ind. I

- 159 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Source1 Source2 Sign Data Update

Parameter Name Description Type Name MSB
(Equip/Label/SDI) (Equip/Label/SDI) Bit Bits Rate
FORCEICEDET Force ice detector for APM DISCRETE MFC-1A/003/ - - 28 1 1
HOSTCRC AFDAU host software CRC PACKED BITS AFDAU/116/00 - - 28 16 1
HOSTPNC01_02 AFDAU host P/N char 1 & 2 CHARACTER AFDAU/40/00 - - 28 16 1
HOSTPNC03_04 AFDAU host P/N char 3 & 4 CHARACTER AFDAU/41/00 - - 28 16 1
HOSTPNC05_06 AFDAU host P/N char 5 & 6 CHARACTER AFDAU/42/00 - - 28 16 1
HOSTPNC07_08 AFDAU host P/N char 7 & 8 CHARACTER AFDAU/43/00 - - 28 16 1
HOSTPNC09_10 AFDAU host P/N char 9 & 10 CHARACTER AFDAU/44/00 - - 28 16 1
HOSTPNC11_12 AFDAU host P/N char 11 & 12 CHARACTER AFDAU/45/00 - - 28 16 1
HOSTPNC13_14 AFDAU host P/N char 13 & 14 CHARACTER AFDAU/46/00 - - 28 16 1
HOSTPNC15_16 AFDAU host P/N char 15 & 16 CHARACTER AFDAU/47/00 - - 28 16 1
IGNFLAPGEAR Ignore flap and gear for APM test DISCRETE MFC-1A/002/ - - 28 1 1
LOADCRC AFDAU loadable code CRC PACKED BITS AFDAU/117/00 - - 28 16 1
LOADPNC01_02 AFDAU load P/N char 1 & 2 CHARACTER AFDAU/060/00 - - 28 16 1
LOADPNC03_04 AFDAU load P/N char 3 & 4 CHARACTER AFDAU/061/00 - - 28 16 1
LOADPNC05_06 AFDAU load P/N char 5 & 6 CHARACTER AFDAU/062/00 - - 28 16 1
LOADPNC07_08 AFDAU load P/N char 7 & 8 CHARACTER AFDAU/063/00 - - 28 16 1
LOADPNC09_10 AFDAU load P/N char 9 & 10 CHARACTER AFDAU/064/00 - - 28 16 1
LOADPNC11_12 AFDAU load P/N char 11 & 12 CHARACTER AFDAU/065/00 - - 28 16 1
LOADPNC13_14 AFDAU load P/N char 13 & 14 CHARACTER AFDAU/066/00 - - 28 16 1
LOADPNC15 AFDAU load P/N char 15 CHARACTER AFDAU/067/00 - - 28 8 1
MWA429EX_LSB Maintenance word MWA429Ext LSB PACKED BITS AFDAU/016/00 - - 28 16 2
MWA429EX_MSB Maintenance word MWA429Ext MSB PACKED BITS AFDAU/015/00 - - 28 16 2
MWA429IN_LSB Maintenance word MWA429Int LSB PACKED BITS AFDAU/014/00 - - 28 16 2
MWA429IN_MSB Maintenance word MWA429Int MSB PACKED BITS AFDAU/013/00 - - 28 16 2
MWANAL_LSB Maintenance word MWANAL LSB PACKED BITS AFDAU/010/00 - - 28 16 2
MWANAL_MSB Maintenance word MWANAL MSB PACKED BITS AFDAU/007/00 - - 28 16 2
MWCSDB_LSB Maintenance word MWCSDB-ASCB LSB PACKED BITS AFDAU/020/00 - - 28 16 2
MWCSDB_MSB Maintenance word MWCSDB-ASCB MSB PACKED BITS AFDAU/017/00 - - 28 16 2
MWDIS_LSB Maintenance word MWDIS LSB PACKED BITS AFDAU/012/00 - - 28 16 2
MWDIS_MSB Maintenance word MWDIS MSB PACKED BITS AFDAU/011/00 - - 28 16 2
MWLOAD_LSB Maintenance word MWLOAD LSB PACKED BITS AFDAU/024/00 - - 28 16 2
MWLOAD_MSB Maintenance word MWLOAD MSB PACKED BITS AFDAU/023/00 - - 28 16 2
MWMPC_LSB Maintenance word MWMPC LSB PACKED BITS AFDAU/026/00 - - 28 16 2
MWMPC_MSB Maintenance word MWMPC MSB PACKED BITS AFDAU/025/00 - - 28 16 2
MWRCDR_LSB Maintenance word MWRCDR LSB PACKED BITS AFDAU/006/00 - - 28 16 2
MWRCDR_MSB Maintenance word MWRCDR MSB PACKED BITS AFDAU/005/00 - - 28 16 2
MWSERINT_LSB Maintenance word MWSERInt LSB PACKED BITS AFDAU/022/00 - - 28 16 2
MWSERINT_MSB Maintenance word MWSERInt MSB PACKED BITS AFDAU/021/00 - - 28 16 2
NL_L_V2A NL Left for the conf V2A BNR LINEAR (A*X) ED34-BC/007/10 - - 22 12 1
NL_R_V2A NL Right for the conf V2A BNR LINEAR (A*X) ED34-BC/010/10 - - 22 12 1
NP_L_1 NP Left from EEC1 BNR LINEAR (A*X) PEC-EEC1/346/00 - - 28 10 1
NP_L_1_SSM NP Left from EEC1 SSM PACKED BITS PEC-EEC1/346/00 - - 31 2 1
NP_R_2 NP Right from EEC2 BNR LINEAR (A*X) PEC-EEC2/346/00 - - 28 10 1
NP_R_2_SSM NP Right from EEC2 SSM PACKED BITS PEC-EEC2/346/00 - - 31 2 1
PECEEC1_CODE Failure code on PEC/EEC 1 BCD PEC-EEC1/240/ - - 29 8 2
PECEEC1_DIG1 Failure code on PEC/EEC 1 digit 1 PACKED BITS PEC-EEC1/240/ - - 29 4 2
PECEEC1_DIG2 Failure code on PEC/EEC 1 digit 2 PACKED BITS PEC-EEC1/240/ - - 25 4 2
PECEEC1_TRIM TRIM parameter on PEC/EEC 1 PACKED BITS PEC-EEC1/270/ - - 29 12 2
PECEEC2_CODE Failure code on PEC/EEC 2 BCD PEC-EEC2/240/ - - 29 8 2
PECEEC2_DIG1 Failure code on PEC/EEC 2 digit 1 PACKED BITS PEC-EEC2/240/ - - 29 4 2
PECEEC2_DIG2 Failure code on PEC/EEC 2 digit 2 PACKED BITS PEC-EEC2/240/ - - 25 4 2
PECEEC2_TRIM TRIM parameter on PEC/EEC 2 PACKED BITS PEC-EEC2/270/ - - 29 12 2
SELACT_1_2 AFDAU selected ac type char 1 & 2 CHARACTER AFDAU/124/00 - - 28 16 1
SELACT_3_4 AFDAU selected ac type char 3 & 4 CHARACTER AFDAU/125/00 - - 28 16 1
SELACT_5_6 AFDAU selected ac type char 5 & 6 CHARACTER AFDAU/126/00 - - 28 16 1
SELACT_7_8 AFDAU selected ac type char 7 & 8 CHARACTER AFDAU/127/00 - - 28 16 1
SELDBC01_02 AFDAU selected database ident char 1 & 2 CHARACTER AFDAU/130/00 - - 28 16 1
SELDBC03_04 AFDAU selected database ident char 3 & 4 CHARACTER AFDAU/131/00 - - 28 16 1
SELDBC05_06 AFDAU selected database ident char 5 & 6 CHARACTER AFDAU/132/00 - - 28 16 1
SELDBC07_08 AFDAU selected database ident char 7 & 8 CHARACTER AFDAU/133/00 - - 28 16 1
SELDBC09_10 AFDAU selected database ident char 9 & 10 CHARACTER AFDAU/134/00 - - 28 16 1
AFDAU selected database ident char 11 &
SELDBC11_12 CHARACTER AFDAU/135/00 - - 28 16 1
12
AFDAU selected database ident char 13 &
SELDBC13_14 CHARACTER AFDAU/136/00 - - 28 16 1
14
AFDAU selected database ident char 15 &
SELDBC15_16 CHARACTER AFDAU/137/00 - - 28 16 1
16
101-10002-851 Ind. I

- 160 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Source1 Source2 Sign Data Update

Parameter Name Description Type Name MSB
(Equip/Label/SDI) (Equip/Label/SDI) Bit Bits Rate
SELDBCRC AFDAU selected database CRC PACKED BITS AFDAU/120/00 - - 28 16 1
SELENGTYPE Selected engine type PACKED BITS AFDAU/002/01 - - 24 4 1
SOFTNAC01_02 AFDAU software name char 1 & 2 CHARACTER AFDAU/100/00 - - 28 16 1
SOFTNAC03_04 AFDAU software name char 3 & 4 CHARACTER AFDAU/101/00 - - 28 16 1
SOFTNAC05_06 AFDAU software name char 5 & 6 CHARACTER AFDAU/102/00 - - 28 16 1
SOFTNAC07_08 AFDAU software name char 7 & 8 CHARACTER AFDAU/103/00 - - 28 16 1
SOFTNAC09_10 AFDAU software name char 9 & 10 CHARACTER AFDAU/104/00 - - 28 16 1
SOFTPNC01_02 AFDAU software P/N char 1 & 2 CHARACTER AFDAU/105/00 - - 28 16 1
SOFTPNC03_04 AFDAU software P/N char 3 & 4 CHARACTER AFDAU/106/00 - - 28 16 1
SOFTPNC05_06 AFDAU software P/N char 5 & 6 CHARACTER AFDAU/107/00 - - 28 16 1
SOFTPNC07_08 AFDAU software P/N char 7 & 8 CHARACTER AFDAU/110/00 - - 28 16 1
SOFTPNC09_10 AFDAU software P/N char 9 & 10 CHARACTER AFDAU/111/00 - - 28 16 1
SOFTPNC11_12 AFDAU software P/N char 11 & 12 CHARACTER AFDAU/112/00 - - 28 16 1
SOFTPNC13_14 AFDAU software P/N char 13 & 14 CHARACTER AFDAU/113/00 - - 28 16 1
SOFTPNC15 AFDAU software P/N char 15 CHARACTER AFDAU/114/00 - - 28 8 1
Total Air Temperature from ADC-1 (No
TAT_1 BNR LINEAR (A*X) ADC-1/211/ - 29 28 11 1
SSM)
TAT_1_SSM Total Air Temperature from ADC-1 SSM PACKED BITS ADC-1/211/ - - 31 2 1
Total Air Temperature from ADC-2 (No
TAT_2 BNR LINEAR (A*X) ADC-2/211/ - 29 28 11 1
SSM)
TAT_2_SSM Total Air Temperature from ADC-2 SSM PACKED BITS ADC-2/211/ - - 31 2 1
TCASCODE TCAS failure code PACKED BITS TCAS/356/ - - 24 16 32
TCASWD TCAS word number PACKED BITS TCAS/356/ - - 28 4 32
Shunt discrete B20 of AFDAU : "TO
TCONFIG_WARN DISCRETE AFDAU/002/01 - - 16 1 1
CONFIG WARNING" (Used for MFC)

6.1.2. ARINC 573 parameters from FDR dataframes

The DMU system software contains a pre-acquisition mechanism that allows access to parameters
contained in FDR dataframes like standard ARINC 429 parameters. A special interface is added in GSE 5.3
to allow an easy PCM parameter declaration. To access it, just select the PCM format in the parameter
definition window.
On previous GSE version, that parameters can be declared in the GSE as standard ARINC 429 parameters
like explained in this chapter.

6.1.2.1 Access to any PCM word in the FDR dataframe generated by the FDAU
These parameters are contained in the FDR dataframe generated by the FDAU. They are transmitted from
the AFDAU to the DMU via the internal ARINC 429 bus (named AFDAU in the GSE) as described in chapter
4.4.1.2.
In order to access to these PCM parameters like standard ARINC 429 parameters, they must be declared in
the GSE with respect ot the following rules (applicable on GSE version 5.1):
Label and SDI of the pseudo ARINC 429 parameter give the PCM word in the FDR dataframe generated by
the FDAU, as follows:
PCM word = SDI + Label + 1
So:
SDI = 00 for PCM words between 1 and 256
SDI = 01 for PCM words between 257 and 512
SDI = 10 for PCM words between 513 and 768
SDI = 11 for PCM words between 769 and 1024

PCM sub-frame is given by the pseudo-bus number as follows:

bus 26 (FDAU1) for sub-frame 1
bus 27 (FDAU2) for sub-frame 2
bus 28 (FDAU3) for sub-frame 3
bus 29 (FDAU4) for sub-frame 4
bus 30 (FDAU1_3) for sub-frames 1&3
101-10002-851 Ind. I

- 161 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

bus 31 (FDAU2_4) for sub-frames 2&4

bus 32 (FDAUALL) for sub-frames 1 to 4

The content of each PCM word is located between bit 12 and bit 1 of the pseudo ARINC 429 message

Notes :
• The rate of the pseudo ARINC 429 parameter programmed in the GSE must be the same than the rate
of the input FDR parameter, excepted for rates less than 1 Hz (1 Hz must be programmed in that case).
• These pseudo ARINC 429 buses are not used in the current version of the DMU software. Most of
parameters are located on specific PCM parameters on bus 40 (FDAU_ATR).

6.1.2.2 Access to any PCM word in the FDR dataframe generated by the AFDAU
These parameters are contained in the FDR dataframe generated by the AFDAU. They are transmitted from
the AFDAU to the DMU via the internal HDLC line as described in chapter 4.4.1.2.
In order to access to these PCM parameters like standard ARINC 429 parameters, they must be declared in
the GSE with respect ot the following rules (applicable on GSE version 5.1) :
Label and SDI of the pseudo ARINC 429 parameter give the PCM word in the FDR dataframe generated by
the AFDAU, as follows:
PCM word = SDI + Label +1

So:
SDI = 00 for PCM words between 1 and 256
SDI = 01 for PCM words between 257 and 512
SDI = 10 for PCM words between 513 and 768
SDI = 11 for PCM words between 769 and 1024

PCM sub-frame is given by the pseudo-bus number as follows:

bus 33 (FDR1) for sub-frame 1
bus 34 (FDR2) for sub-frame 2
bus 35 (FDR3) for sub-frame 3
bus 36 (FDR4) for sub-frame 4
bus 37 (FDR1_3) for sub-frames 1&3
bus 38 (FDR2_4) for sub-frames 2&4
bus 39 (FDRALL) for sub-frames 1 to 4

The content of each PCM word is located between bit 12 and 1 of the pseudo ARINC 429 message

Notes :
• The rate is limited to 1 Hz.
• These buses are not used in the current version of the DMU software. Most of parameters are located
on specific PCM parameters on bus 40 (FDAU_ATR).

6.1.2.3 Access to specific ATR PCM parameters in the FDR dataframes generated
by the FDAU
These parameters represent all the specific ATR FDR parameters generated by the FDAU and transmitted
from the AFDAU to the DMU via the internal ARINC 429 bus (named AFDAU in the GSE) as described in
chapter 4.4.1.2.
In ATR aircrafts, parameters have different characteristics in function of the dataframe configuration
(V0,V1,V2,V2A,V2B). But thanks to specific pre-acquisition tables present in the DMU System software,
most of these parameters can be accessed by declaring in the GSE one single pseudo-arinc 429 parameter,
using the specific pseudo Arinc 429 bus 40 (named FDAU_ATR in the GSE).
These parameters are listed in the following table, the input characteristics in the GSE is given for each of
them.
101-10002-851 Ind. I

- 162 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Note that this list of parameters has been established using:

ATR SIL for ATR42-300 and ATR42-320 [A02], SIL for ATR42-400 and ATR42-500 [A06], and SIL for
ATR72 [A03] for V0, V1, V2 and V2A configurations.
SFIM ED34A340 specification [S03] for V2B configuration.

Notes:
In the “Availability” columns:
X stands for available
ATR42 stands for available only in ATR42 aircraft
ATR72 stands for available only in ATR72 aircraft
SRD stands for available only according to SFIM requirements

In the “Nb Bits” column: the number of bits represents the maximum number of bits available; for some
configurations this number can be less and in this case the LSB bits will be discarded and 0 padded.

Generally, only parameters used in functions of the DMU (ACMS reports, triggering logics, computation of
other parameters, ...) are calibrated. For other parameters, only raw value is available (see the last column
of the table).

Parameter Alpha GSE GSE MSB Nb Availability according to Flight Data Recording Calibrated
call-up Label SDI Bits System (C) or RAW
V0 V1 V2 V2A V2B (R) value
Lateral acceleration GLAT 001 0 28 10 X X X X X C
Longitudinal acceleration GLON 002 0 28 10 X X X X X C
Vertical acceleration GVER 003 0 28 12 X X X X X C
Pitch angle PITCH 004 0 28 12 X X X X X R
Roll attitude ROLL 005 0 28 10 X X X X X R
Roll Surf. pos. LH 1 ROSPL 006 0 28 12 X X X X X R
Roll Surf. pos. RH 1 ROSPR 007 0 28 12 X X R
Pitch Surf. pos. LH1 PISPL 010 0 28 12 X X X X X R
Pitch Surf. pos. RH1 PISPR 011 0 28 12 X R
Pitch Trim position PTRIM 012 0 28 12 X X X X X R
Trailing Edge Flap TRAIL 013 0 28 12 X X X X X R
Yaw Surface position YAWSP 014 0 28 12 X X X X X R
Pitch cont. col pos LH (or left roll trim PCCPL 015 0 28 12 X X X R
position)
Pitch cont. col pos RH (or yaw trim PCCPR 016 0 28 12 X X X R
position)
Longitude (sign+MSD+LSD) LON 017 0 29 21 X X X R
Latitude (sign+MSD+LSD) LAT 020 0 29 21 X X X R
NP Left NPL 021 0 28 12 X X X X X C
NP Right NPR 022 0 28 12 X X X X X C
NH Left NHL 023 0 28 12 X X X X X C
NH Right NHR 024 0 28 12 X X X X X C
FLIGHT number FLT 025 0 28 16 X X X X X C
Date: DATE 026 0 C
DAY (tenth) 22 2 X X X X X
DAY (units) 20 4 X X X X X
MONTH (tenth) 13 1 X X X X X
MONTH (units) 12 4 X X X X X
YEAR (tenth) 8 4 X X X
YEAR (units) 4 4 X X X X X
Altitude ALT 027 0 C
for ATR 42 25 12 ATR42 ATR42 ATR42 ATR42
for ATR 42/72 (coarse+fine) 29 16 ATR72 ATR72 ATR72 ATR72 X
GMT: GMT 030 0 C
Hours (tens) 24 4 X X X X X
Hours (units) 20 4 X X X X X
101-10002-851 Ind. I

- 163 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Parameter Alpha GSE GSE MSB Nb Availability according to Flight Data Recording Calibrated
call-up Label SDI Bits System (C) or RAW
V0 V1 V2 V2A V2B (R) value
Minutes (tens) 16 4 X X X X X
Minutes (units) 12 4 X X X X X
Seconds (tens) 8 4 X X X
Seconds (units) 4 4 X X X
PLA Left PLAL 031 0 28 12 ATR72 ATR72 X X X R
PLA Right PLAR 032 0 28 12 ATR72 ATR72 X X X R
Radio Altitude RALT 033 0 28 12 X X X X X C
Yaw control ped. pos. YAWCP 034 0 28 12 X R
ASCB 7 selected course SELCO 035 0 28 12 X X X R
ASCB 8 selected.v/s SELVS 036 0 28 12 X X X R
ASCB 4 selected IAS SELIA 037 0 28 12 X X X R
ASCB 5 selected ALT SELAL 040 0 28 12 X X X R
ASCB 6 decision.height DECHT 041 0 28 12 X X X R
Airspeed IAS 042 0 28 12 X X X X X C
AIRCRAFT ident ACID 043 0 28 8 X X X X X C
Ground Speed GSPD 044 0 28 10 X X X C
Time in hotel mode (minute) HOTEL 045 0 28 16 X X X X X C
Torque Left TORQL 046 0 28 10 X X X X X C
Torque Right TORQR 047 0 28 10 X X X X X C
Total Air Temperature or TAT 050 0 29 12 X X X X X C
Static Air Temperature or
Outside Air Temperature
Wind Direction WDIR 051 0 28 10 X X R
Select Baro setting SELBA 052 0 29 19 ATR72 ATR72 X R
Selected Heading SELHD 053 0 28 12 X X X R
Desired Track DETRK 054 0 28 12 X X X R
Drift Angle DRIFT 055 0 28 11 X X X R
Resolution Advisory RESAD 056 0 28 12 X X X R
Engine & propeller type PROP 057 0 28 4 X X X R
Roll control wheel pos. ROCWP 060 0 28 12 X R
Aileron tab cde pos. AILTA 061 0 28 10 SRD X R
Localizer dev. Left LOCDL 062 0 28 10 X X X X X R
Localizer dev. Right LOCDR 063 0 28 10 X X X R
ITT Left ITTL 064 0 28 10 X X X X X C
ITT Right ITTR 065 0 28 10 X X X X X C
AOA Left AOAL 066 0 28 10 X X X R
AOA right AOAR 067 0 28 10 X X X R
ASCB 9 EFIS L status STEFL 071 0 16 5 X R
NL Left NLL 072 0 28 12 X X X X C
NL Right NLR 073 0 28 12 X X X X C
HEADing HDG 074 0 28 10 X X X X X R
Glide Slope dev. Left GLSDL 075 0 28 9 X X X X X R
Glide Slope dev. Right GLSDR 076 0 28 8 X X X R
Fuel Flow Left FFL 077 0 28 10 X X X X C
Fuel Flow Right FFR 100 0 28 10 X X X X C
BETASN PEC1 BTPE1 101 0 28 12 X R
BETASN PEC2 BTPE2 102 0 28 12 X R
NAV 1 selected freq.(msd+lsd) NAV1F 103 0 29 19 X R
NAV 2 selected freq. (msd+lsd) NAV2F 104 0 29 19 X R
Objectif TORQUE Left OTQL 105 0 28 10 X X R
Objectif TORQUE Right OTQR 106 0 28 10 X X R
101-10002-851 Ind. I

- 164 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Parameter Alpha GSE GSE MSB Nb Availability according to Flight Data Recording Calibrated
call-up Label SDI Bits System (C) or RAW
V0 V1 V2 V2A V2B (R) value
ASCB 10 EFIS R status RSTAT 107 0 28 7 X R
ASCB 12 EFIS R identifier RIDEN 110 0 28 8 X R
ASCB 13 EFIS L dme dis LDME 111 0 28 16 X R
ASCB 14 EFIS R dme dis RDME 112 0 28 16 X R
ASCB 15 EFIS L terrain LTER 113 0 28 6 X R
ASCB 17 EFIS L WX sel LWX 114 0 28 12 X R
ASCB 18 EFIS R WX sel RWX 115 0 28 12 X R
Current Detector Left IGL 116 0 28 12 X X X X C
Current Detector Right IGR 117 0 28 12 X X X X C
Fuel quantity Left FQTL 120 0 28 12 X X X C
Fuel quantity Right FQTR 121 0 28 12 X X X C
ASCB 1 Auto pilot status APST 122 0 28 2 X X X X X R
ADC selection ADCSE 123 0 28 1 ATR72 ATR72 X X X R
ASCB 1 Abnormal disc. ABDIS 124 0 27 1 X X R
ASCB 3 HDG cap HDCAP 125 0 28 1 X X X X R
Anti ice PROP-1 (LH) AIPLH 126 0 28 1 X X X R
ADC Altitude Warning ALTWN 127 0 28 1 ATR42 ATR42 X R
Nacelle overheat Left NACOL 130 0 28 1 X R
Smoke Aft SMKAF 131 0 28 1 X R
Sensitivity SENSI 132 0 16 3 X X R
FDAU FRAME Counter FCNTR 135 0 28 12 X R
angle of attack AOA 137 0 28 19 X X X X R
ASCB 16 EFIS R terrain RTER 141 0 22 6 X R
HF1 HF 147 0 25 1 X X X X X R
High flow control HFCTL 150 0 24 1 X X X X X R
EVENT selected EVENT 151 0 26 1 X X X X X R
Inner Marker INNMK 152 0 23 1 X X X X X R
Low Pitch LH (Pos/Neg) THRVL 153 0 22 1 X X X X X R
Low Pitch RH (Pos/Neg) THRVR 154 0 21 1 X X X X R
Middle Marker MIDMK 155 0 20 1 X X X X X R
Outer Marker OUTMK 156 0 19 1 X X X X X R
Left Spoiler SPOIL 157 0 18 1 X X X X R
Right Spoiler SPOIR 160 0 17 1 X X X X R
Master Warning MWARN 161 0 14 1 X X X X R
VHF 1 VHF1 162 0 13 1 X X X X X R
VHF 2 VHF2 163 0 12 1 X X X X X R
VHF 31 VHF3 164 0 11 1 X X X X X R
Airframe de icing AFAI 165 0 27 1 X X X X X R
HP Valve left HPVL 166 0 26 1 X X X X X R
HP Valve right HPVR 167 0 25 1 X X X X X R
Left pack air flow PACKL 170 0 24 1 X X X X X R
Right pack air flow PACKR 171 0 23 1 X X X X X R
Propeller Brake control PBCTL 172 0 22 1 X X X X X R
AC 1 electrical bus status AC1BS 173 0 21 1 X X X C
AC 2electrical bus status AC2BS 174 0 20 1 X X X C
DC1 electrical bus status DC1BS 175 0 19 1 X X X R
DC2 electrical bus status DC2BS 176 0 18 1 X X X R

Parameters HF and VHF3 are identical on V0,V1,V2, and V2A configurations

1
101-10002-851 Ind. I

- 165 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Parameter Alpha GSE GSE MSB Nb Availability according to Flight Data Recording Calibrated
call-up Label SDI Bits System (C) or RAW
V0 V1 V2 V2A V2B (R) value
Supercooled Large Droplet ice SLDID 177 0 17 1 X X X X R
detection / Grosse goutte
Hyd Aux low pressure HALP 200 0 16 1 X X X X R
Hyd Blue low pressure HBLP 201 0 15 1 X X X X R
Hyd Green low pressure HGLP 202 0 14 1 X X X X R
Icing AOA IAOA 203 0 13 1 X X X R
PEC-1 status PEC1S 204 0 12 1 X X R
PEC-2 status PEC2S 205 0 11 1 X X R
All Gear Squat Switch AGEAR 206 0 28 1 X X X X C
ASCB 2 Act mode cap/trk CAPTK 207 0 26 1 X X X X R
ASCB 1 ID 800 (ADU caution active) ID800 210 0 25 1 X X X X R
ASCB 1 TCS active TCSAC 211 0 24 1 X X X X R
ASCB 1 Yaw dumper st. YAWDP 212 0 23 2 X X X R
ASCB 2 (V.mode) GS cap GSCAP 213 0 21 1 X X X X R
ASCB 1 HSI sel.status HSISE 214 0 20 2 X X X X R
ASCB 2 ALT ALTST 215 0 18 1 X X X X R
ASCB 2 ALT cap ALTCP 216 0 17 1 X X X X R
ASCB 2 GA cap GACAP 217 0 16 1 X X X X R
ASCB 2 GS arm GSARM 220 0 15 1 X X X X R
ASCB 2 IAS cap IASCP 221 0 14 1 X X X X R
ASCB 2 VS cap VSCP 222 0 13 1 X X X X R
ASCB 3 (L.mode) BC cap BCCP 223 0 12 1 X X X X R
ASCB 3 BC arm BCARM 224 0 11 1 X X X X R
ASCB 3 HHOLD HHOLD 225 0 27 1 X X X X R
ASCB 3 LOC arm LOCAR 226 0 26 1 X X X X R
ASCB 3 LOC cap LOCCP 227 0 25 1 X X X X R
ASCB 3 VOR arm VORAR 230 0 24 1 X X X X R
ASCB 3 VOR cap VORCP 231 0 23 1 X X X X R
Ef on pitch axis (cap n do) CPNDO 232 0 22 1 X X X R
Ef on pitch axis (cap n up) CPNUP 233 0 21 1 X X X R
Ef on pitch axis (f/o n do) FONDO 234 0 20 1 X X X R
Ef on pitch axis (f/o n up) FONUP 235 0 19 1 X X X R
Flap assymetry FLPAS 236 0 18 1 X X X X X R
GPS degrade GPSDE 237 0 17 1 X X R
GPWS status GPWSS 240 0 16 1 X X X R
Main Gear Squat Switch MGEAR 241 0 15 1 X X X X R
Traffic Advisory TRFAD 242 0 13 3 X X R
Anti ice PROP-2 (RH) AIPRH 243 0 27 1 X X X R
Ice detection ICE 244 0 26 1 X X X R
Landing Gear Select pos LGSEL 245 0 25 1 X X X X R
MFC1-A status MFC1A 246 0 24 1 X X X R
MFC1-B status MFC1B 247 0 23 1 X X X R
MFC2-A status MFC1A 250 0 22 1 X X X R
MFC2-B status MFC2B 251 0 21 1 X X X R
Super Frame counter SPFCT 252 0 20 4 X X R
ADC Speed Warning SPDWN 253 0 27 1 ATR42 ATR42 X R
ASCB 1 Bank limit H/L BKLIM 254 0 26 1 SRD SRD X R
ASCB 3 Mode PA L.NAV PANAV 255 0 25 1 SRD X R
Cabin pressure over lim. CABPR 256 0 24 1 X R
CLA 1 Fuel shut off FUEL1 257 0 23 1 X R
101-10002-851 Ind. I

- 166 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Parameter Alpha GSE GSE MSB Nb Availability according to Flight Data Recording Calibrated
call-up Label SDI Bits System (C) or RAW
V0 V1 V2 V2A V2B (R) value
CLA 2 Fuel shut off FUEL2 260 0 22 1 X R
Engine Fire Left FIREL 261 0 21 1 X R
Engine Fire Right FIRER 262 0 20 1 X R
Excessive cabin altitude CBALT 263 0 19 1 X R
Flap unlock FLPUN 264 0 17 1 X R
L/G not down LDGND 265 0 16 1 X R
MLS/ILS 1 selection MLS1S 266 0 15 1 SRD X R
MLS/ILS 2 selection MLS2S 267 0 14 1 SRD X R
PEC 1 Fault PEC1F 270 0 13 1 X R
PEC 2 Fault PEC2F 271 0 12 1 X R
Propeller Brake PRPBK 272 0 11 1 X R
Nacelle overheat Right NACOR 273 0 27 1 X R
Oil low pressure Left OIPLL 274 0 24 1 X R
Oil low pressure Right OIPLR 275 0 22 1 X R
PITCH disconnect or MFC2-B status PIT 276 0 20 1 X R
PITCH disconnect 42 PIT42 277 0 19 1 X R
PITCH disconnect 72 PIT72 300 0 18 1 X R
Propeller Brake lock PBLCK 301 0 17 1 X R
Propeller Brake unlock PBUNL 302 0 16 1 X R
Reserved MFC 22 MFC22 303 0 15 1 X R
Reserved MFC 23 MFC23 304 0 14 1 X R
Reserved MFC 33 MFC33 305 0 13 1 X R
Reserved MFC 34 MFC34 306 0 12 1 X R
Reserved MFC 35 MFC35 307 0 11 1 X R
Smoke Elect. SMKEL 310 0 26 1 X R
Smoke Fwd. SMKFW 311 0 24 1 X R
Stick shaker captain STICP 312 0 22 1 X R
Stick shaker first officer STIFO 313 0 21 1 X R
T/O config. TOCNF 314 0 20 1 X R
Left HP air bleed HPBLL 315 0 28 1 X R
Right HP air bleed HPBLR 316 0 27 1 X R
TAT/SAT TATSL 317 0 26 1 ATR42 ATR42 ATR42 ATR42 X R
FDEP PROG PIN FDEP 356 0 24 1 X X X R
Wind Speed WINSP 357 0 19 8 X X R
ASCB 11 EFIS L identifier LIDEN 360 0 21 8 X R
101-10002-851 Ind. I

- 167 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.2. LIST OF REPORTS LIMITS PROGRAMMED ON THE GSE

6.2.1. Cruise report <02>

ATR42- ATR42- ATR42- ATR42- ATR72 ATR72- ATR72- GSE ACARS
Limit 300 320 400 500 -200 210 500 modif. MCDU
Definition Spare Unit
No. allowed modif
PW120 PW121 PW121A PW127E PW124 PW127 PW127F allowed

1 Indicated AirSpeed maximum 80 80 80 80 80 80 80 kts YES YES

value
2 Indicated Airspeed maximum 5 5 5 5 5 5 5 kts YES YES
variation
3 Altitude maximum value 6000 6000 6000 6000 6000 6000 6000 ft YES YES
4 Altitude maximum variation 100 100 100 100 100 100 100 ft YES YES
5 Vertical acceleration 0.2 0.2 0.2 0.2 0.2 0.2 0.2 g YES YES
maximum variation

6 NH maximum variation 0.5 0.5 0.5 0.5 0.5 0.5 0.5 % YES YES
7 Torque maximum variation 1.0 1.0 1.0 1.0 1.0 1.0 1.0 % YES YES
8 NP maximum variation 0.5 0.5 0.5 0.5 0.5 0.5 0.5 % YES YES
(Propeller speed)

9 Time interval between two 6 6 6 6 6 6 6 hours YES YES

ECTM recordings
10- Reserved - NO NO
20
101-10002-851 Ind. I

- 168 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.2.2. Exceedance report <03>

ATR42- ATR42- ATR42- ATR42- ATR72- ATR72- ATR72- GSE ACARS

Limit 300 320 400 500 200 210 500 modif. MCDU
Definition Spare Unit
No. allowed modif
PW120 PW121 PW121A PW127E PW124 PW127 PW127F allowed

21 Maximum Number of reports 40 40 40 40 40 40 40 - YES YES

code 4000 per flight
22 Minimum exceedance time for 3 3 3 3 3 3 3 sec YES YES
a report generation

23 Maximum exceedance time 6 6 6 6 6 6 6 min YES YES

before report output
24 FF_L premonitoring threshold 10 10 10 10 10 10 10 Kg/h YES YES
25 FF_R premonitoring threshold 10 10 10 10 10 10 10 Kg/h YES YES
26 TORQ T1 100 100 114.2 122 106.3 106.3 106.3 % YES YES
27 TORQ T2 105 107.2 123 130 115 108 108 % YES YES
28 TORQ T3 125 119.7 132.4 137 124.5 109.6 109.6 % YES YES
29 NP T1 101.5 101.5 106 106 101.5 101.5 106 % YES YES
30 NP T2 110 110 115 115 110 106 115 % YES YES
31 NP T3 110 110 120 120 110 120 120 % YES YES
32 NH T1 100 100 103.2 103.2 102.7 103.2 103.2 % YES YES
33 NH T2 102 102 104.1 104.3 103.7 104.3 104.3 % YES YES
34 NH T3 102 102 104.1 104.3 103.7 104.3 104.3 % YES YES
35 IAS threshold used for ITT 80.0 80.0 80.0 80.0 80.0 80.0 80.0 Kts YES YES
threshold selection

36 ITT T1 for 816 816 816 800 800 800 800 deg YES YES
IAS>IAS threshold

37 ITT T2 for 850 850 850 840 840 840 840 deg YES YES
IAS>IAS threshold
38 ITT T3 for 950 950 950 950 95 950 950 deg YES YES
IAS>IAS threshold
39 ITT T1 for 850 850 850 840 840 840 840 deg YES YES
IAS<=IAS threshold

40 ITT T2 for 950 950 950 950 950 950 950 deg YES YES
IAS<=IAS threshold
41 ITT T3 for 950 950 950 950 950 950 950 deg YES YES
IAS<=IAS threshold

42- Reserved - NO NO
49
50 Limit data set number 1 2 3 4 5 6 7 - NO NO

Note : limit 50 "data set number" is not used in report <03>. It has only an informative purpose.
101-10002-851 Ind. I

- 169 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.2.3. G-Meter report <15>

ATR42- ATR42 ATR42- ATR42- ATR72- ATR72- ATR72- GSE ACARS

Limit 300 -320 400 500 200 210 500 modif. MCDU
Definition Spare Unit
No. allowed modif
PW120 PW121 PW121A PW127E PW124 PW127 PW127F allowed

51 Vertical Acceleration -2.5 -2.5 -2.5 -2.5 -2.5 -2.5 -2.5 g NO NO

Minimum

52 Vertical Acceleration +5 + +5 +5 +5 +5 +5 g NO NO
Maximum 5
53 Time to turn in flight after 10 1 10 10 10 10 10 sec NO NO
go-around 0

54 Duration of PEH before 10 1 10 10 10 10 10 sec NO NO

landing 0
55 Duration of Accelerometers 2 2 2 2 2 2 2 sec NO NO
test at end of flight
56 Maximum deviation from 0.2 0. 0.2 0.2 0.2 0.2 0.2 g NO NO
nominal value of 2
accelerometers

57- Reserved - NO NO
60

6.2.4. Instant Flight CMC report <24>

ATR42- ATR42- ATR42- ATR42- ATR72- ATR72- ATR72- GSE ACARS

Limit 300 320 400 500 200 210 500 modif. MCDU
Definition Spare Unit
No. allowed modif
PW120 PW121 PW121A PW127E PW124 PW127 PW127F allowed

61 Delay of generation after 5 5 5 5 5 5 5 min NO NO

desactivation of master
alarm

62- Reserved - NO NO
70
101-10002-851 Ind. I

- 170 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.2.5. PW127M Engine Cycles report <25>

ATR42- ATR42- ATR42- ATR42- ATR72- ATR72- ATR72- GSE ACARS
Limit 300 320 400 500 200 210 500 Spar modif. MCDU
Definition Unit
No. e allowed modif
PW120 PW121 PW121A PW127E PW124 PW127 PW127F allowed

71 Number of flights between two 5 5 5 5 5 5 5 - YES YES

automatic report generations (0
for inhibition)
72 Eng LCF warning threshold (% 1.0 1.0 1.0 1.0 1.0 1.0 1.0 % YES YES
of total life)
73 LP impeller life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
74 HP impeller life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
75 HP turbine front cover life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
76 HP disk life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
77 HP turbine rear cover life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
78 Interstage air seal life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
79 LP disk life limit 15000 15000 15000 15000 15000 15000 15000 - NO NO
80 1 stage PT disk life limit 30000 30000 30000 30000 30000 30000 30000
st
- NO NO
81 2 stage PT disk life limit 30000 30000 30000 30000 30000 30000 30000
nd
- NO NO
82-89 Reserved - NO NO
90 DTUE MCDU screen enabled 0 0 0 0 0 0 0 - NO YES
(0:NO, 1:YES)
101-10002-851 Ind. I

- 171 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3. COMPOSITION OF MAINTENANCE WORDS

6.3.1. BITE word

Bit ALARM
number

0 Power supply Alarm

1 Reserved
2 Host software checksum error
3 DMU System software error
4 DMU set-up data base error
5 Reserved
6 RAM memory Failure
7 SRAM memory failure
8 Flash Prom memory I/O failure
9 Reserved
10 ARINC 429 input internal failure
11 ARINC 429 output internal failure
12 Reserved
13 Discrete input failure
14 Discrete output failure
15 Reserved
16 Battery failure
17 Reserved
18 Ethernet interface failure
19-31 Reserved
101-10002-851 Ind. I

- 172 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3.2. Maintenance word CPU (MW-CPU)

Bit ALARM
number

0 Restart after watchdog

1 Multiple restart after watchdog
2 Host software checksum error
3 DMU System software not loaded
4 DMU System software checksum error
5 DMU System software ident error
6 DMU set-up data base not loaded
7 DMU set-up data base checksum error
8 A/C Tail not compatible with set-up data base
9 Reserved
10 RAM memory Failure
11 SRAM memory failure
12 Flash Prom memory I/O failure – BITE memory
13 Flash Prom memory I/O failure – system software memory
14 Flash Prom memory I/O failure – database memory
15 Reserved
16-23 Reserved
24 User partition failure
25 GSE programmable logics failure
26 Stack overflow
27 CPU overload
28 User partition overload
29 Periodic task of system partition overload
30 System partition overload
31 Reserved
101-10002-851 Ind. I

- 173 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3.3. Maintenance word GENERAL (MW-GEN)

Bit ALARM
number

0 Power supply Alarm

1 Battery failure
2 Reserved
3 ARINC 429 input internal failure
4 ARINC 429 input external failure
5 Reserved
6 ARINC 429 output internal failure on ACARS MU channel
7 ARINC 429 output internal failure on PRINTER channel
8 ARINC 429 output internal failure on MCDU 1 channel
9 Reserved
10 ARINC 429 output internal failure on FDAU
11 ARINC 429 output internal failure on TCAS
12-13 Reserved
14 Discrete input failure
15 Discrete output failure
16 Input QAR PCM absent
17 Reserved
18 FDAU communication error : no FDAU detected
19 IP Stack init failure
20 IP Stack Failure
21 Ethernet link failure
22 Ethernet autotest failure
23-31 Reserved
101-10002-851 Ind. I

- 174 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3.4. Maintenance word PCMCIA (MW-PCMCIA)

Bit ALARM
number

0 No media loaded
1 Invalid PCMCIA media
2 Invalid DOS media
3 Disk access error
4 PCMCIA media full.
5 Disk FIFO access error
6 Too many files opened
7-11 Reserved
12 error open file
13 error write file
14 error read file
15 error close file
16 error directory file
17 error seek file
18 error delete file
19-31 Reserved
Note: One of the bits 12 to 18 is set if the last attempt to perform the associated command is not
successful.
101-10002-851 Ind. I

- 175 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3.5. Input channel internal failures (STIFDMU)

Bit ALARM
number

0 Internal failure on input channel 1 AFDAU

1 Internal failure on input channel 2 MFC-1A
2 Internal failure on input channel 3 MCDU-1
3 Internal failure on input channel 4 FDAU
4 Internal failure on input channel 5 Printer
5 Internal failure on input channel 6 ACARS
6 Internal failure on input channel 7 MFC-1B
7 Internal failure on input channel 8 MFC-2B
8 Internal failure on input channel 9 Port D3
9 Internal failure on input channel 10 Port D4
10 Internal failure on input channel 11 Port D5
11 Internal failure on input channel 12 Port D6
12 Internal failure on input channel 13 Port D7
13 Internal failure on input channel 14 Port D8
14 Internal failure on input channel 15 TCAS
15 Reserved
16 Internal failure on input channel 17 Port D10
17 Internal failure on input channel 18 Port D11
18 Internal failure on input channel 19 MFC-2A
19 Internal failure on input channel 20 Port D13
20 Internal failure on input channel 21 Port D14
21 Internal failure on input channel 22 Port D15
22-31 Reserved
101-10002-851 Ind. I

- 176 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.3.6. Input channel external failures (STEFDMU)

Bit ALARM
number

0 External failure on input channel 1 AFDAU

1 External failure on input channel 2 MFC-1A
2 External failure on input channel 3 MCDU-1
3 External failure on input channel 4 FDAU
4 External failure on input channel 5 Printer
5 External failure on input channel 6 ACARS
6 External failure on input channel 7 MFC-1B
7 External failure on input channel 8 MFC-2B
8 External failure on input channel 9 Port D3
9 External failure on input channel 10 Port D4
10 External failure on input channel 11 Port D5
11 External failure on input channel 12 Port D6
12 External failure on input channel 13 Port D7
13 External failure on input channel 14 Port D8
14 External failure on input channel 15 TCAS
15 Reserved
16 External failure on input channel 17 Port D10
17 External failure on input channel 18 Port D11
18 External failure on input channel 19 MFC-2A
19 External failure on input channel 20 Port D13
20 External failure on input channel 21 Port D14
21 External failure on input channel 22 Port D15
22-31 Reserved
101-10002-851 Ind. I

- 177 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.4. ALPHA CALL-UP DEFAULT LIST

Alpha call
Parameter 1 Parameter 2 Description
up name
42-72 ATR42OR72 ATR 42 / ATR 72 selection discrete
ABDIS AB_DISC Abnormal disc ASCB 1
AC1BS BUS1_26VAC 26VAC BUS 1
AC2BS BUS2_26VAC 26VAC BUS 2
ACID ACNUM A/C Number
ACNUM ACNUM A/C Number
ACTAI ACTAIL1 ACTAIL2 A/C Tail
ACTYP ACTYPE A/C Type
ADCSE ADC_SEL Adc selection
AFAI AIRFRAME Air Frame
AGEAR ALL_GEAR All gear squatt switch
AILTA AIL_TAB_CDE Aileron tab commande position
AIPLH ANTI_ICEPRO1 Anti ice prop 1 LH
AIPRH ANTI_ICEPRO2 Anti ice prop 2 RH
AIR AIR_GROUND Air/Ground switch discrete (Main Landing Gear Squat Switch)
AIRSP AIRSPEED_F Air Speed filtered
ALT ALTITUDE Altitude
ALTCP ALT_CAP ALT CAP ASCB2
ALTST ALT ALT ASCB2
ALTWN ADC_ALT_WAR Adc Altitude warning
AOA ANGLE_ATTACK Angle of attack
AOAL AOA_L AOA left
AOAR AOA_R AOA right
APM CX aircraft average on 60s coefficient and APM theoretical average on
APMCX APMCXAC60S APMCXTH60S 60s coefficient
APMCZ APMCZ APMGAMMA APM CZ coefficient and Gamma
APMD1 APMALTICAPT APMANTIICING APM altitude capture mode and APM anti-icing
APMD2 APMDEICING APMICEDETECT APM de-icing (also called icing AOA) and APM ice detector
APM APIU degraded performance discrete and APM APIU increase speed
APMDI APM_DEGRADED APM_INCREASE discrete
APMFA APM_FAULT APM FAULT discrete coming from AFDAU bite
APM flaps position ou Trailing edge flap and APM selected landing gear
APMFG APMFLAPS APMGEAR position
APMIS APMIAS APMSAT APM selected indicated air speed and APM selected static air temperature
APMJP APMJX APMPITCH APM longitudinal acceleration and APM pitch position
APMLV APMLEVEL1 APMLEVEL2 APM level 1 and level2 output
APMMW MWMPC_MSB MWMPC_LSB Maintenance word MWMPC
APMNP APMNP1 APMNP2 APM NP1 and NP2 (Left and Right prop. rot. speed)
APMSP APMIASTH APMMSIS APM theoretical indicated airspeed and APM minimum severe icing speed
APMTA APMTAS APMTRACTION APM true airspeed and APM traction
APMTE APM_TEST_EN APM test enable discrete
APMTQ APMTQ1 APMTQ2 APM TQ1 (Left Propeller torque) and APM TQ2 (Right propeller torque)
APMW APMROTW APMWEIGHT APM rotator weight and APM weight
APMZP APMZP APM selected pressure altitude
APST AP_STATUS Auto pilote status ASCB 1
ASN ASN1 ASN2 APUserial number ( DMU computed, 4 first characters)
BCARM BC_ARM BC ARM ASCB2
BCCP BC_CAP BC CAP (L.mode) ASCB2
BICOD PECEEC1_CODE PECEEC2_CODE Failure code on PEC/EEC 1 and PEC/EEC 2
BISEL EEC_SELECTED SELENGTYPE Failure code on PEC/EEC 1 and Selected engine type
BITRI PECEEC1_TRIM PECEEC2_TRIM TRIM parameter on PEC/EEC 1 and PEC/EEC 2
BKLIM BANK_LIMIT Bank limit h/L ASCB 1
BTPE1 PEC1 PEC1 BETASN
BTPE2 PEC2 PEC2 BETASN
C11PN ENG1_C1_PN1 ENG1_C1_PN2 EEC Engine left LCF Componant 1 P/N parts 1 & 2
C11SN ENG1_C1_SN1 ENG1_C1_SN2 EEC Engine left LCF Componant 1 S/N parts 1 & 2
C11TC ENG1_C1_TCYC ENG1_C1_RL EEC Engine left LCF Componant 1 Total Cycles & Remaining Life
C12PN ENG1_C2_PN1 ENG1_C2_PN2 EEC Engine left LCF Componant 2 P/N parts 1 & 2
C12SN ENG1_C2_SN1 ENG1_C2_SN2 EEC Engine left LCF Componant 2 S/N parts 1 & 2
C12TC ENG1_C2_TCYC ENG1_C2_RL EEC Engine left LCF Componant 2 Total Cycles & Remaining Life
C13PN ENG1_C3_PN1 ENG1_C3_PN2 EEC Engine left LCF Componant 3 P/N parts 1 & 2
C13SN ENG1_C3_SN1 ENG1_C3_SN2 EEC Engine left LCF Componant 3 S/N parts 1 & 2
C13TC ENG1_C3_TCYC ENG1_C3_RL EEC Engine left LCF Componant 3 Total Cycles & Remaining Life
C14PN ENG1_C4_PN1 ENG1_C4_PN2 EEC Engine left LCF Componant 4 P/N parts 1 & 2
101-10002-851 Ind. I

- 178 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Alpha call
Parameter 1 Parameter 2 Description
up name
C14SN ENG1_C4_SN1 ENG1_C4_SN2 EEC Engine left LCF Componant 4 S/N parts 1 & 2
C14TC ENG1_C4_TCYC ENG1_C4_RL EEC Engine left LCF Componant 4 Total Cycles & Remaining Life
C15PN ENG1_C5_PN1 ENG1_C5_PN2 EEC Engine left LCF Componant 5 P/N parts 1 & 2
C15SN ENG1_C5_SN1 ENG1_C5_SN2 EEC Engine left LCF Componant 5 S/N parts 1 & 2
C15TC ENG1_C5_TCYC ENG1_C5_RL EEC Engine left LCF Componant 5 Total Cycles & Remaining Life
C16PN ENG1_C6_PN1 ENG1_C6_PN2 EEC Engine left LCF Componant 6 P/N parts 1 & 2
C16SN ENG1_C6_SN1 ENG1_C6_SN2 EEC Engine left LCF Componant 6 S/N parts 1 & 2
C16TC ENG1_C6_TCYC ENG1_C6_RL EEC Engine left LCF Componant 6 Total Cycles & Remaining Life
C17PN ENG1_C7_PN1 ENG1_C7_PN2 EEC Engine left LCF Componant 7 P/N parts 1 & 2
C17SN ENG1_C7_SN1 ENG1_C7_SN2 EEC Engine left LCF Componant 7 S/N parts 1 & 2
C17TC ENG1_C7_TCYC ENG1_C7_RL EEC Engine left LCF Componant 7 Total Cycles & Remaining Life
C18PN ENG1_C8_PN1 ENG1_C8_PN2 EEC Engine left LCF Componant 8 P/N parts 1 & 2
C18SN ENG1_C8_SN1 ENG1_C8_SN2 EEC Engine left LCF Componant 8 S/N parts 1 & 2
C18TC ENG1_C8_TCYC ENG1_C8_RL EEC Engine left LCF Componant 8 Total Cycles & Remaining Life
C19PN ENG1_C9_PN1 ENG1_C9_PN2 EEC Engine left LCF Componant 9 P/N parts 1 & 2
C19SN ENG1_C9_SN1 ENG1_C9_SN2 EEC Engine left LCF Componant 9 S/N parts 1 & 2
C19TC ENG1_C9_TCYC ENG1_C9_RL EEC Engine left LCF Componant 9 Total Cycles & Remaining Life
C21PN ENG2_C1_PN1 ENG2_C1_PN2 EEC Engine right LCF Componant 1 P/N parts 1 & 2
C21SN ENG2_C1_SN1 ENG2_C1_SN2 EEC Engine right LCF Componant 1 S/N parts 1 & 2
C21TC ENG2_C1_TCYC ENG2_C1_RL EEC Engine right LCF Componant 1 Total Cycles & Remaining Life
C22PN ENG2_C2_PN1 ENG2_C2_PN2 EEC Engine right LCF Componant 2 P/N parts 1 & 2
C22SN ENG2_C2_SN1 ENG2_C2_SN2 EEC Engine right LCF Componant 2 S/N parts 1 & 2
C22TC ENG2_C2_TCYC ENG2_C2_RL EEC Engine right LCF Componant 2 Total Cycles & Remaining Life
C23PN ENG2_C3_PN1 ENG2_C3_PN2 EEC Engine right LCF Componant 3 P/N parts 1 & 2
C23SN ENG2_C3_SN1 ENG2_C3_SN2 EEC Engine right LCF Componant 3 S/N parts 1 & 2
C23TC ENG2_C3_TCYC ENG2_C3_RL EEC Engine right LCF Componant 3 Total Cycles & Remaining Life
C24PN ENG2_C4_PN1 ENG2_C4_PN2 EEC Engine right LCF Componant 4 P/N parts 1 & 2
C24SN ENG2_C4_SN1 ENG2_C4_SN2 EEC Engine right LCF Componant 4 S/N parts 1 & 2
C24TC ENG2_C4_TCYC ENG2_C4_RL EEC Engine right LCF Componant 4 Total Cycles & Remaining Life
C25PN ENG2_C5_PN1 ENG2_C5_PN2 EEC Engine right LCF Componant 5 P/N parts 1 & 2
C25SN ENG2_C5_SN1 ENG2_C5_SN2 EEC Engine right LCF Componant 5 S/N parts 1 & 2
C25TC ENG2_C5_TCYC ENG2_C5_RL EEC Engine right LCF Componant 5 Total Cycles & Remaining Life
C26PN ENG2_C6_PN1 ENG2_C6_PN2 EEC Engine right LCF Componant 6 P/N parts 1 & 2
C26SN ENG2_C6_SN1 ENG2_C6_SN2 EEC Engine right LCF Componant 6 S/N parts 1 & 2
C26TC ENG2_C6_TCYC ENG2_C6_RL EEC Engine right LCF Componant 6 Total Cycles & Remaining Life
C27PN ENG2_C7_PN1 ENG2_C7_PN2 EEC Engine right LCF Componant 7 P/N parts 1 & 2
C27SN ENG2_C7_SN1 ENG2_C7_SN2 EEC Engine right LCF Componant 7 S/N parts 1 & 2
C27TC ENG2_C7_TCYC ENG2_C7_RL EEC Engine right LCF Componant 7 Total Cycles & Remaining Life
C28PN ENG2_C8_PN1 ENG2_C8_PN2 EEC Engine right LCF Componant 8 P/N parts 1 & 2
C28SN ENG2_C8_SN1 ENG2_C8_SN2 EEC Engine right LCF Componant 8 S/N parts 1 & 2
C28TC ENG2_C8_TCYC ENG2_C8_RL EEC Engine right LCF Componant 8 Total Cycles & Remaining Life
C29PN ENG2_C9_PN1 ENG2_C9_PN2 EEC Engine right LCF Componant 9 P/N parts 1 & 2
C29SN ENG2_C9_SN1 ENG2_C9_SN2 EEC Engine right LCF Componant 9 S/N parts 1 & 2
C29TC ENG2_C9_TCYC ENG2_C9_RL EEC Engine right LCF Componant 9 Total Cycles & Remaining Life
CABPR CAB_PRESSURE Cabin pressure over limit
CAPTK CAP_TRK Act mode cap/trk ASCB2
CBALT CAB_EXCESS_A Cabin excessive altitude
COEEC ENGINE Engine (conv or EEC)
CPNDO EF_CAP_N_DO Effort on pitch axis cap n do
CPNUP EF_CAP_N_UP Effort on pitch axis cap n up
CPU CPU_LOAD CPU_LOAD_MAX CPU load for all partitions
CPUA CPU_LOAD_A CPU_LOADAMAX CPU load for partition A
CPUB CPU_LOAD_B CPU_LOADBMAX CPU load for partition B
CXINC CXDRAGINC CXa/c drag increment for APM
DARFC DFC DAR frame counter (DMU computed)
DATE DATE date DAY MONTH YEAR corrected
DAY DAY GMT Day in BCD corrected
DBREV DTB_REV DMU database revision
DBVER DTB_VER DMU database version
DC1BS DC_BUS1 DC Bus 1
DC2BS DC_BUS2 DC Bus 2
DECHT DEC_HEIGHT Decision height ASCB6
DETRK DES_TRACK Desired track
DRIFT DRIFT_ANGLE Drift angle
E1ERT ENG1_127E_RT ENG1_127E_FH EEC Engine left Run Time and Flight Hours as PW127E
E1FRT ENG1_127F_RT ENG1_127F_FH EEC Engine left Run Time and Flight Hours as PW127F
E1MRT ENG1_127M_RT ENG1_127M_FH EEC Engine left Run Time and Flight Hours as PW127M
E1NFL ENG1_NFLIGHT EEC Engine left number of flights
101-10002-851 Ind. I

- 179 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Alpha call
Parameter 1 Parameter 2 Description
up name
E1NST ENG1_NSTARTS EEC Engine left number of starts
E1RGB ENG1_RGB_SN1 ENG1_RGB_SN2 EEC Engine left Reduction Gear Box S/N parts 1 & 2
E1SN ENG1_SN1 ENG1_SN2 EEC Engine left S/N part 1 & part 2
E1TM ENG1_TM_SN1 ENG1_TM_SN2 EEC Engine left Turbo Machine S/N parts 1 & 2
E1TRT ENG1_TOT_RT ENG1_TOT_FH EEC Engine left Total Run Time all engine models
E2ERT ENG2_127E_RT ENG2_127E_FH EEC Engine right Run Time and Flight Hours as PW127E
E2FRT ENG2_127F_RT ENG2_127F_FH EEC Engine right Run Time and Flight Hours as PW127F
E2MRT ENG2_127M_RT ENG2_127M_FH EEC Engine right Run Time and Flight Hours as PW127M
E2NFL ENG2_NFLIGHT EEC Engine right number of flights
E2NST ENG2_NSTARTS EEC Engine right number of starts
E2RGB ENG2_RGB_SN1 ENG2_RGB_SN2 EEC Engine right Reduction Gear Box S/N parts 1 & 2
E2SN ENG2_SN1 ENG2_SN2 EEC Engine right S/N parts 1 & 2
E2TM ENG2_TM_SN1 ENG2_TM_SN2 EEC Engine right Turbo Machine S/N parts 1 & 2
E2TRT ENG2_TOT_RT ENG2_TOT_FH EEC Engine right Total Run Time and Flight Hours all engine models
ENGFM ENGFAMILY Engine family
ENGTY ENGTYPE Engine type
ESN1 ESN_1_1 ESN_1_2 Engine 1 serial number ( DMU computed)
ESN2 ESN_2_1 ESN_2_2 Engine 2 serial number ( DMU computed)
ESN3 ESN_3_1 ESN_3_2 Engine 3 serial number ( DMU computed)
ESN4 ESN_4_1 ESN_4_2 Engine 4 serial number ( DMU computed)
EVENT EVENT_SEL Event selected
EVT EVENT Event Marker
FCNTR FRAME_COUNT Frame counter
FDEP FDEP_PROGPIN FDEP prog pin
FDRIN FDR_IN_DTF Number of selected input PCM FDR frame (from FDAU)
FFL FF_L Fuel Flow Left
FFR FF_R Fuel Flow Right
FFS03 FFSCHAR03_04 FFSCHAR05_06 FFS char 3 4 5 6
FFS07 FFSCHAR07_08 FFSCHAR09_10 FFS char 7 8 9 10
FFS11 FFSCHAR11_12 FFSCHAR13_14 FFS char 11 12 13 14
FFS15 FFSCHAR15_16 FFSCHAR17_18 FFS char 15 16 17 18
FFS19 FFSCHAR19_20 FFSCHAR21_22 FFS char 19 20 21 22
FFS23 FFSCHAR23_24 FFSCHAR25_26 FFS char 23 24 25 26
FFS27 FFSCHAR27_28 FFS char 27 & 28
FFSLI FFSLIGNE FFS line
FGIGN IGNFLAPGEAR Ignore flap and gear for APM test
FIREL ENG_FIRE_L Engine fire left
FIRER ENG_FIRE_R Engine fire Right
FLCNT FLCNT Flight counter (DMU computed)
FLPAS FLAP_ASSY Flap assymetry (FALSE : FLAP ASSYMETRY DETECTED)
FLPUN FLAP_UNLOCK Flap unlock
FLT FLINUM Flight number
FM FLIMOD Internal flight phase (DMU computed)
FOICE FORCEICEDET Force ice detector for APM
FONDO EF_FO_N_DO Effort on pitch axis f/o n do
FONUP EF_FO_N_UP Effort on pitch axis f/o n up
FQTL FUELQUANT_L Fuel Quantity Indicator Left
FQTR FUELQUANT_R Fuel Quantity Indicator Right
FUEL1 CLA1_FUELOFF CLA1 fuel shut off
FUEL2 CLA2_FUELOFF CLA2 fuel shut off
GACAP GA_CAP GA CAP ASCB2
GLAT GLAT Lateral Acceleration
GLON GLON Longitudal Acceleration
GLSDL GLIDE_L Glide slop dev left
GLSDR GLIDE_R Glide slop dev Right
GMT UTC UTC (format BCD, Hours, Min) corrected.
GPSDE GPS_DEGRADE GPS degrade
GPWSS GPWS_STATUS GPWS status
GSARM GS_ARM GS ARM ASCB2
GSCAP GS_CAP GS CAP (Vmode) ASCB2
GSPD GSPD Ground Speed
GVER GVER Vertical Acceleration
HALP HYD_AUX Hyd aux low pressure
HBLP HYD_BLUE Hyd blue low pressure
HDCAP HDG_CAP HDG Cap ASCB3
HDG HEADING Heading
HF HF HF
HFCTL HIGH_FLOW_CT High flow control
101-10002-851 Ind. I

- 180 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Alpha call
Parameter 1 Parameter 2 Description
up name
HGLP HYD_GREEN Hyd green low pressure
HHOLD HHOLD HHOLD ASCB3
HOTEL HOTEL_TIM_MN Hotel time mn
HPVL HP_VALVE_L HP VAlve left
HPVR HP_VALVE_R HP VAlve Right
HSISE HSI_SEL_ST HSI sel. status ASCB1
IAOA ICING_AOA Icing AOA
IAS AIRSPEED Airspeed
IASCP IAS_CAP IAS CAP ASCB2
ICE ICE_DETECT Ice detection
ID800 ID800 ID800 (ADU caution active) ASCB1
IGL CD_L Current detector left switched parameter
IGR CD_R Current detector right switched parameter
INNMK INNER_MARKER Inner marker
ITTL ITT_L ITT Left
ITTR ITT_R ITT Right
LAT LATITUDE Latitude
LATST LAT_R15_VAL Result of lateral acceleration test at end of flight
LDGND LG_NOT_DOWN L/G not down MFC par
LDME L_DME_DIS EFIS L DME dis ASCB13
LGSEL LANDING_GEAR Landing gear select
LIDEN L_IDENT EFIS L identifier ASCB11
LIGHT LIGHT_TEST Light Test (DMU Computed)
LOCAR LOC_ARM LOC arm ASCB3
LOCCP LOC_CAP LOC capASCB3
LOCDL LOCALIZER_L Localizer dev left
LOCDR LOCALIZER_R Localizer dev right
LON LONGITUDE Longitude
LONST LON_R15_VAL Result of longitudinal acceleration test at end of flight
LSTAT L_STATUS EFIS L status ASCB 9
LTER L_TERRAIN EFIS L terrain ASCB15
LWX L_WX_SEL EFIS L WX sel ASCB17
MALAR MC_STATUS MW_STATUS Master alarms filtered (master caution and master warning)
MARAW MC_STAT_RAW MW_STAT_RAW Master alarms raw (master caution and master warning)
MFC1A MFC1A_STATUS MFCA status
MFC1B MFC1B_STATUS MFC1B status
MFC22 MFC22 Reserved MFC22
MFC23 MFC23 Reserved MFC23
MFC2A MFC2A_STATUS MFC2A status
MFC2B MFC2B_STATUS MFC2B status
MFC33 MFC33 Reserved MFC33
MFC34 MFC34 Reserved MFC34
MFC35 MFC35 Reserved MFC35
MGEAR MAIN_GEAR_SQ Main gear squatt switch
MIDMK MIDDLEMARKER Middlemarker
MLS1S MLS_ILS_SEL1 Mls/Ils selection 1
MLS2S MLS_ILS_SEL2 Mls/Ils selection 2
MONTH MONTH computed month : Textual representation (ex : JAN, FEB, ...)
MWARN MAST_WARNING Master Warning
NACOL NACELLE_L Nacelle overheat left
NACOR NACELLE_R Nacelle overheat right
NAV1F NAV1 NAV 1 selected freq
NAV2F NAV2 NAV 2 selected freq
NH NH_L_F NH_R_F NH Left filtered and NH Right filtered
NHL NH_L NH Left
NHR NH_R NH Right
NLL NL_L NL Left
NLR NL_R NL Right
NP NP_L NP_R NP Left and NP Right
NPL NP_L NP Left
NPR NP_R NP Right
OIPLL OIL_LOW_L Oil low pressure left
OIPLR OIL_LOW_R Oil low pressure right
OTQ OTQ_L OTQ_R Objective Torque Left and Right
OTQC OTQ_LC OTQ_RC Objective Torque Left and Right Calibrated (%)
OTQL OTQ_L Objective Torque Left
OTQR OTQ_R Objective Torque Right
OUTMK OUTER_MARKER outer marker
101-10002-851 Ind. I

- 181 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Alpha call
Parameter 1 Parameter 2 Description
up name
PACKL PACK_AIR_L Pack air flow left
PACKR PACK_AIR_R Pack air flow right
PANAV PA_L_NAV Mode PA L.NAV ASCB3
PBCTL PB_CONTROL Propeller brake control
PBLCK PB_LOCK Propeller brake lock
PBUNL PB_UNLOCK Propeller brake unlock
PCCPL PITCH_CONT_L PITCH control col position LH
PCCPR PITCH_CONT_R PITCH control col position RH
PEC1F PEC1_FAULT PEC1 fault
PEC1S PEC1_STATUS PEC1 status
PEC2F PEC2_FAULT PEC2 fault
PEC2S PEC2_STATUS PEC2 status
PISPL PITCH_SURF_L PITCH surface position LH
PISPR PITCH_SURF_R PITCH surface position RH
PIT PITCH_DISC PITCH disconnect
PIT42 PITCH_DISC42 PITCH disconnect 42
PIT72 PITCH_DISC72 PITCH disconnect 72
PITCH PITCHANGL Pitch Angle
PLAL PLA_L PLA left
PLAR PLA_R PLA right
PROP ENG_TYPE_PIN Engine type prog pin
PRPBK PBMFC Propeller brake MFC
PTRIM PITCH_TRIM_P Pitch trim position
R02EC R02_ECTMSTAT R02 status for ECTM recording (troubleshooting param)
R02 flag TRUE if ECTM time unit is new (troubleshooting param)
R02NT R02_FGNEWTIM R02_ECTIMREF R02 reference time used for ECTM recording (troubleshooring param)
R02RQ R02_REP_QUAL R02 quality of last ECTM recording (troubleshooting param)
R02ST R02_STAB_ST R02 stability status (troubleshooting param)
R02TI R02_MON_TIME R02 stability time in seconds (troubleshooting param)
R03ST EXC_STAT_R03 R03 exceedance status (troubleshooting param)
RALT RALT Radio Altitude
RALTF RALT_F Radio Altitude filtered
RDME R_DME_DIS EFIS R DME dis ASCB14
RESAD RES_ADVISORY Resolution advisory
RIDEN R_IDENT EFIS R identifier ASCB12
ROCWP ROLL_CONT_WH Roll control wheel
ROLL ROLL_ATTITUD Roll attitude
ROSPL ROLL_SURF_LH Roll surface position LH
ROSPR ROLL_SURF_RH Roll surface position RH
RPB RPB Remote Print Button discrete value(DMU computed)
RSTAT R_STATUS EFIS R status ASCB10
RTER R_TERRAIN EFIS R terrain ASCB15
RWX R_WX_SEL EFIS R WX sel ASCB18
SECS SECOND UTC Seconds corrected in BCD.
SELAL ALT_SEL Selected ALT ASCB5
SELBA BAROSETSELEC Selected Baro Setting
SELCO SEL_COURSE Selected Course ASCB7
SELDB SELDBCRC AFDAU selected database CRC
SELHD SEL_HEADING Selected heading
SELIA IAS_SEL Selected IAS ASCB4
SELVS SEL_VS Selected V/S ASCB8
SENSI SENSITIVITY SENSITIVITY
SLDID GROSSEGOUTTE Grosse goutte
SMKAF SMOKE_AFT SMOKE aft
SMKEL SMOKE_ELEC SMOKE elec
SMKFW SMOKE_FWD SMOKE FWD
SPDWN ADC_SPD_WAR Adc Speed warning
SPFCT SPF_COUNTER Superframe counter
SPOIL SPOILER_L Left spoiler
SPOIR SPOILER_R Right spoiler
STICP STICK_CAPT Stick shaker captain
STIFO STICK_OFFI Stick shaker first officer
TAT TAT Calibrated total air temperature according to configuration
TATSL TAT_SAT_SEL TAT SAT selection
TCSAC TCS TCS active ASCB1
TGDAR TRIGGER_DAR Number of DAR trigger(DMU computed)
TGQAR TRIGGER_QAR Number of QAR trigger(DMU computed)
THRVL LOW_PITCH_LH Low pitch LH
101-10002-851 Ind. I

- 182 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

Alpha call
Parameter 1 Parameter 2 Description
up name
THRVR LOW_PITCH_RH Low pitch RH
TOCNF TO_CONFIG t/o config MFC par. (Can be used only on configuration V2B)
TOCWA TCONFIG_WARN Shunt discrete B20 of AFDAU : "TO CONFIG WARNING" (Used for MFC)
TORQL TORQUE_L Torque left calibrated by the DMU software
TORQR TORQUE_R Torque right calibrated by the DMU software
TRAIL TRAILINGEDGE Trailing edge flap
TRFAD TRAFFIC_ADVI Traffic advisory
UTAIR UTC_AIR_MAX UTC_AIR_MIN UTC of max vrtg on air and UTC of min vrtg on air
UTGND UTC_GND_MAX UTC of max vrtg on ground
VELOC VELOCITY Velocity
VHF1 VHF1 VHF1
VHF2 VHF2 VHF2
VHF3 VHF3 VHF3
VORAR VOR_ARM VOR Arm ASCB3
VORCP VOR_CAP VOR cap ASCB3
VRTST VERT_R15_VAL Result of vertical acceleration test at end of flight
VSCP VS_CAP VS CAP ASCB2
VTAIR VRTG_AIR_MAX VRTG_AIR_MIN VRTG max on air and VRTG min on air
VTGND VRTG_GND_MAX VRTG max on ground
WDIR WIND_DIR Wind direction
WINSP WIND_SPEED Wind speed
YAWCP YAW_CTR_PED Yaw control ped position
YAWDP YAW_DUMPER YAW dumper status ASCB1
YAWSP YAW_SURF_POS Yaw surface position
YEAR YEAR GMT year in BCD corrected
101-10002-851 Ind. I

- 183 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.5. DAR FRAME

6.5.1. Recorded regular parameters

Part Input Recording Output

Parameter Name Data Bits Subframes Word
(1,2 or 3) MSB Rate (Hz) MSB

APM_APM_ON 1 22 1 1 1-4 30 11
APM_DEGRADED 1 24 1 1 1-4 29 9
APM_FAULT 1 21 1 1 1-4 27 2
APM_INCREASE 1 25 1 1 1-4 30 12
APM_SPEEDLOW 1 23 1 1 1-4 27 1
APMALTICAPT 1 23 1 1 1-4 2 8
APMANTIICING 1 25 1 1 1-4 2 10
APMCXAC60S 1 28 6 1 1-4 19 6
APMCXAC60S 2 22 9 1 1-4 20 12
APMCXTH60S 1 28 9 1 1-4 18 9
APMCXTH60S 2 19 6 1 1-4 19 12
APMCZ 1 28 8 1 1-4 25 8
APMCZ 2 20 10 1 1-4 26 12
APMDEICING 1 26 1 1 1-4 2 11
APMFLAPS 1 29 12 1 1-4 6 12
APMGAMMA 1 29 3 1 1-4 20 3
APMGAMMA 2 26 12 1 1-4 21 12
APMGEAR 1 27 1 1 1-4 2 12
APMIAS 1 28 12 1 1-4 4 12
APMIASTH 1 28 8 1 1-4 14 8
APMICEDETECT 1 24 1 1 1-4 2 9
APMJX 1 29 12 1 1-4 11 12
APMLEVEL1 1 12 1 1 1-4 2 6
APMLEVEL2 1 13 1 1 1-4 2 7
APMMSIS 1 28 8 1 1-4 22 12
APMNP1 1 28 12 1 1-4 7 12
APMNP2 1 28 12 1 1-4 8 12
APMPITCH 1 29 12 1 1-4 12 12
APMROTW 1 28 12 1 1-4 15 12
APMROTW 2 16 3 1 1-4 29 12
APMSAT 1 29 12 1 1-4 5 12
APMTAS 1 28 9 1 1-4 16 9
APMTQ1 1 28 12 1 1-4 9 12
APMTQ2 1 28 12 1 1-4 10 12
APMTRACTION 1 29 12 1 1-4 3 12
APMTRACTION 2 17 5 1 1-4 2 5
APMWEIGHT 1 28 12 1 1-4 17 12
APMWEIGHT 2 16 3 1 1-4 18 12
APMZP 1 29 12 1 1-4 13 12
APMZP 2 17 4 1 1-4 14 12
BITE1_LSB 1 28 12 1 1-4 58 12
101-10002-851 Ind. I

- 184 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

BITE1_LSB 2 16 4 1 1-4 59 12
BITE1_MSB 1 28 8 1 1-4 59 8
BITE1_MSB 2 20 8 1 1-4 60 12
BITE2_LSB 1 28 4 1 1-4 60 4
BITE2_LSB 2 24 12 1 1-4 61 12
BITE2_MSB 1 28 4 1 1-4 63 4
BITE2_MSB 2 24 12 1 1-4 62 12
CXDRAGINC 1 28 3 1 1-4 27 12
DFC 1 12 12 1/4 2 28 12
EXC_STAT_R03 1 11 11 1 1-4 33 11
FLIMOD 1 4 4 1 1-4 27 9
FORCEICEDET 1 28 1 1 1-4 26 2
IGNFLAPGEAR 1 28 1 1 1-4 26 1
MC_STATUS 1 1 1 4 1-4 16 11
MW_STATUS 1 1 1 4 1-4 16 12
MWA429EX_LSB 1 28 12 1 1-4 38 12
MWA429EX_LSB 2 16 4 1 1-4 39 12
MWA429EX_MSB 1 28 4 1 1-4 36 4
MWA429EX_MSB 2 24 12 1 1-4 37 12
MWA429IN_LSB 1 28 4 1 1-4 40 4
MWA429IN_LSB 2 24 12 1 1-4 41 12
MWA429IN_MSB 1 28 8 1 1-4 39 8
MWA429IN_MSB 2 20 8 1 1-4 40 12
MWANAL_LSB 1 28 8 1 1-4 43 8
MWANAL_LSB 2 20 8 1 1-4 44 12
MWANAL_MSB 1 28 12 1 1-4 42 12
MWANAL_MSB 2 16 4 1 1-4 43 12
MWCSDB_LSB 1 28 8 1 1-4 35 8
MWCSDB_LSB 2 20 8 1 1-4 36 12
MWCSDB_MSB 1 28 12 1 1-4 34 12
MWCSDB_MSB 2 16 4 1 1-4 35 12
MWDIS_LSB 1 28 12 1 1-4 46 12
MWDIS_LSB 2 16 4 1 1-4 47 12
MWDIS_MSB 1 28 4 1 1-4 44 4
MWDIS_MSB 2 24 12 1 1-4 45 12
MWLOAD_LSB 1 28 4 1 1-4 48 4
MWLOAD_LSB 2 24 12 1 1-4 49 12
MWLOAD_MSB 1 28 8 1 1-4 47 8
MWLOAD_MSB 2 20 8 1 1-4 55 8
MWMPC_LSB 1 28 12 1 1-4 24 12
MWMPC_LSB 2 16 4 1 1-4 25 12
MWMPC_MSB 1 28 4 1 1-4 22 4
MWMPC_MSB 2 24 12 1 1-4 23 12
MWRCDR_LSB 1 28 8 1 1-4 51 8
MWRCDR_LSB 2 20 8 1 1-4 52 12
MWRCDR_MSB 1 28 12 1 1-4 50 12
MWRCDR_MSB 2 16 4 1 1-4 51 12
MWSERINT_LSB 1 28 12 1 1-4 54 12
101-10002-851 Ind. I

- 185 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

MWSERINT_LSB 2 16 4 1 1-4 55 12
MWSERINT_MSB 1 28 4 1 1-4 52 4
MWSERINT_MSB 2 24 12 1 1-4 53 12
R02_ECTIMREF 1 32 12 1 1-4 31 12
R02_ECTIMREF 2 20 10 1 1-4 30 10
R02_ECTIMREF 3 10 10 1 1-4 32 10
R02_ECTMSTAT 1 4 4 1 1-4 57 12
R02_FGNEWTIM 1 1 1 1 1-4 56 12
R02_MON_TIME 1 8 8 1 1-4 57 8
R02_REP_QUAL 1 3 3 1 1-4 27 5
R02_STAB_ST 1 11 11 1 1-4 56 11
SECOND 1 8 8 1 1-4 63 12
UTC 1 16 8 1/4 1 29 8
UTC 2 8 8 1/4 2 29 8

6.5.2. Recorded superframe parameters

Superframe Parameter Part Output
Input MSB Data Bits Frame no Subframe Word
Name (1,2 or 3) MSB

DATE 1 24 12 1 1 28 12
DATE 2 12 12 2 1 28 12
FLINUM 1 28 12 3 1 28 12
FLINUM 2 16 4 4 1 28 12
101-10002-851 Ind. I

- 186 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6. BITE/CMC MESSAGES FILES

BITE/CMC function use several Excel files to define the displayed messages, each file containing one or
several tables. See Configuration Index Document [S05] to find these Excel files.

6.6.1. AFCS Excel file

The AFCS function uses three tables, one for the description messages, one for the choices and one for the
FFS faults. There are two versions of each table, one for ATR42-300 aircraft and one version for all other
ATR aircraft, so the file contain six tables.

6.6.1.1 Description table

It contains the steps (instructions/comments) for the operator. The data are hold in three columns, B, E and
H, for up to three pages per text (column B for first page, E, for second if any, H for third if any). The first line
is a column header line, to be ignored. The format of each column is:
− an identification number of text to be displayed (see line 2 and line34 on example below) – this number is the
entry point in the table ; first entry point id. is:
− 101 for general troubleshooting procedure,
− 1 for troubleshooting from ADU messages,
− 50 for use of GMT,
− 202 (for ATR42-300) or 203 (other models) for decoding of FFS,
− the text to be displayed on following lines (up to 14 lines per page),

Figure 6-88 – AFCS description table

101-10002-851 Ind. I

- 187 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.1.2 Choice table

It lists a number of possible answers (choices) to be selected by the operator for the description. ; its format
is:
− column A: an identification number of the calling description (number of the description where the choice
may be selected),
− column B: description of choice – when there are several lines with a same identification number, that means
that all these lines constitutes a package of possible choices for a same description,
− column C: a destination number identifying the description to display upon selection of this choice.

Figure 6-89 – AFCS choice table

101-10002-851 Ind. I

- 188 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.1.3 FFS table

Dedicated to FFS decoding, its format is:
- column A: an aircraft identification number which is:
• 202 for ATR42-300, 203 for other models,
• 205 for ADC bite decoding all models (duplicated in each ffs table),
- column B: description of choice – the choice to display are filtered by data in column D,
- column C: a destination number identifying the description of description table to display upon selection of this
choice,
- column D: bit identification ; this bit id. is extracted via decoding of FFS in ASCB labels or in user inputs. All the
choice whose bit identification is contained in current FFS code should be displayed.

Figure 6-90 – FFS description table

6.6.1.4 Decoding FFS

Excepted for ADC FFS, the FFS is composed of three lines A, B and C, the line C being display on two lines
of the MCDU screen. Line A and B are composed of 4 words (16 bits per word) numbered 1 to 4, and line C
is composed of 6 words numbered 1 to 6. Bits of each word are numbered from 0 to F, 0 being the LSB, F
the MSB. The ADC FFS contain only one line labelled A of two words numbered 1 and 2. A bit of the FFS is
so identified by its line, word number in the line and bit number in the word, forming a three digit code
(examples: A15, B4D, C59), being the choice code.
The choice code are extracted simply by listing the activated bits (bits set to one) of the FFS.
101-10002-851 Ind. I

- 189 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.2. Radio COM/NAV Excel file

The tables of this file list the descriptions and troubleshooting of six radio COM/NAV equipment. Its format is:
− column A: failure code,
− column B: description for the failure code,
− column D (column E for TDR94D equipment): troubleshooting for the failure code.
The 4 first lines are header lines and should be ignored.

Figure 6-91 – Radio COM/NAV table

101-10002-851 Ind. I

- 190 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.3. PEC/EEC Excel file

The PEC table and the EEC table gives the description of maintenance code.

6.6.3.1 PEC table

Its format is:
− column A: fault code,
− column B: name for the fault code.
The first line is a header line and should be ignored.

Figure 6-92 –PEC table

101-10002-851 Ind. I

- 191 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.3.2 EEC table

Its format is:
− column A: engine type for which the following fault code applies,
− column B: fault code,
− column C: name for the fault code Fault name on several lines have to be displayed on the same number of
MCDU lines.
The first line is a header line and should be ignored.

Figure 6-93 –EEC table

101-10002-851 Ind. I

- 192 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.4. TCAS Excel file

This files contains 6 tables, on per maintenance ARINC 429 word the TCAS send to the DMU. Each table
follow the same format:
− column A: bit number of the ARINC 429 word (only bit 9 to 24 are used),
− column B: message associated to the bit,
− column D: troubleshooting associated with the bit.
The first line and following empty lines are header lines and should be ignored.

Figure 6-94 –TCAS table

101-10002-851 Ind. I

- 193 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.6.5. MFC Excel file

This file contains one table defining the fault messages for the 10 systems of each MFC version. Its format
is:
− first line: starting column C and every three columns, the version of MFC applying to the block of three
columns,
− column A from line 3: the system number,
− column B from line 3: the fault code received from MFC for system number of column A,
− following block of three columns, starting column C from line 3 contains:
− first block column: the text describing the fault,
− second and third block column: code to be displayed next to the text.

Figure 6-95 –MFC table

101-10002-851 Ind. I

- 194 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.7. ECTM RECORDING FORMAT

An ECTM recording contains the parameters of one engine, in a line of a text file, as described in the
following table :

Data position Number of Parameter Comment

characters

1 2 IDENTIFIER Constant = « 01 » in ascii

3 6 Engine serial number (alphanumérical defined in “A/C parameters

initialisation” MCDU page of DMU)

9 6 DATE YY/MM/DD (inverted digits from report)

15 5 REFERENCE (GMT) 1 space + report GMT

20 5 CYCLE (AIRCRAFT) 1 space + report FLT rapport

25 5 PRESS ALT report ALT without sign character

30 3 I.O.A.T. Report TAT in Celcius unit

33 3 I.A.S. Report IAS

36 5 TORQUE Report TORQ

41 5 NP /N1 Report NP

46 5 NL Report NL

51 5 NH/NG/N2 Report NH

56 4 ITT Integer part of report ITT

60 4 Fuel Flow (Wf) 1 space + report FF

64 1 Unit of Fuel Flow (Wf) « I » for lbs/hr (pph), « M » for kgs/h

(defined in “A/C parameters initialisation”

MCDU page of DMU)

65 3 Maintenance code Blank if there is not divergence

« MK » if there is divergence

(divergence state depends of Air condition

mask defined in “A/C parameters initialisation”
MCDU page of DMU)

68 2 CRLF CarriageReturn LineFeed (hexa code 0D0A)

Figure 6-96 –ECTM recording format

101-10002-851 Ind. I

- 195 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed
3300059268
(SK-0000207279) MPC FOR ATR 42 AND ATR 72
DMU SYSTEM REQUIREMENTS DOCUMENT
Édition/Issue N° 03
APPENDICES
January 7th, 2008

6.8. ACARS BROADCAST PARAMETERS

No parameter are broadcast in this DMU version.
101-10002-851 Ind. I

- 196 -

Document Sagem DS - Reproduction et divulgation interdites

Sagem DS document – May not be reproduced nor disclosed

A350-1000 Fcom
77% (13)
A350-1000 Fcom
6,404 pages
Airbus A220 Technical Training Manual - General Familiarization Bombardier CSeries CS300
100% (26)
Airbus A220 Technical Training Manual - General Familiarization Bombardier CSeries CS300
956 pages
A320 FCOM - Dec 2021
100% (9)
A320 FCOM - Dec 2021
4,006 pages
Q400 MTM Vol1 Epub
91% (11)
Q400 MTM Vol1 Epub
529 pages
Power Plant PW 1100g
96% (24)
Power Plant PW 1100g
366 pages
A350 System Guide
100% (4)
A350 System Guide
119 pages
Airbus A220 Technical Training Manual - Avionics Bombardier CSeries CS300
100% (15)
Airbus A220 Technical Training Manual - Avionics Bombardier CSeries CS300
798 pages
Leap 1a LM
100% (5)
Leap 1a LM
149 pages
@ ATR 72-600 AMM Including Propellers and Power Plant (P 2623) PDF
100% (16)
@ ATR 72-600 AMM Including Propellers and Power Plant (P 2623) PDF
2,623 pages
Engine Trent XWB Airbus 350 PDF
100% (6)
Engine Trent XWB Airbus 350 PDF
224 pages
Storytelling Special Needs and Disabilities Practical Approaches for Children and Adults 2nd Edition Nicola Grove instant download
100% (2)
Storytelling Special Needs and Disabilities Practical Approaches for Children and Adults 2nd Edition Nicola Grove instant download
64 pages
ATR 72-600 Glass Cockpit
100% (7)
ATR 72-600 Glass Cockpit
198 pages
Airbus A220 Technical Training Manual - Airframe Bombardier CSeries CS300
100% (22)
Airbus A220 Technical Training Manual - Airframe Bombardier CSeries CS300
1,268 pages
A350 900 Flight Deck and Systems Briefing For Pilots 1 PDF
91% (11)
A350 900 Flight Deck and Systems Briefing For Pilots 1 PDF
389 pages
Airbus A330 Panels
75% (4)
Airbus A330 Panels
1 page
Airbus A220 Technical Training Manual - Powerplant Bombardier CSeries CS300
100% (17)
Airbus A220 Technical Training Manual - Powerplant Bombardier CSeries CS300
1,284 pages
A350 Afm
100% (8)
A350 Afm
836 pages
A350 Ata 42
80% (5)
A350 Ata 42
33 pages
Trent XWB Under Cowl Guide
100% (3)
Trent XWB Under Cowl Guide
67 pages
A320 AMM Chapter 21
100% (1)
A320 AMM Chapter 21
1,563 pages
A320 Structure Ata 51-57
100% (4)
A320 Structure Ata 51-57
267 pages
B767 200-300 - Airplane General
100% (20)
B767 200-300 - Airplane General
98 pages
Training A320 Structure
100% (10)
Training A320 Structure
706 pages
ATR 600 Cockpit
100% (5)
ATR 600 Cockpit
48 pages
Philip Erringotn: J. K. Rowling - A Bibliography
No ratings yet
Philip Erringotn: J. K. Rowling - A Bibliography
559 pages
Ethnicity and Family Therapy 3rd Edition PDF
0% (4)
Ethnicity and Family Therapy 3rd Edition PDF
2 pages
ACM Troubleshoot Guide by Honeywell
100% (1)
ACM Troubleshoot Guide by Honeywell
109 pages
Airbus A350
100% (7)
Airbus A350
52 pages
A320 Components Location Manual
100% (2)
A320 Components Location Manual
446 pages
Different by Youngme Moon - Excerpt
17% (6)
Different by Youngme Moon - Excerpt
41 pages
Time Traveling With A Hamster Sneak Peek
0% (1)
Time Traveling With A Hamster Sneak Peek
35 pages
10 1057/9780230308848 PDF
No ratings yet
10 1057/9780230308848 PDF
232 pages
ATR
100% (2)
ATR
20 pages
Skin Heat Exchanger
No ratings yet
Skin Heat Exchanger
1 page
ATA 20 Standard Practices
No ratings yet
ATA 20 Standard Practices
6 pages
ACSS THALES ATR-500-600 Technical Support Comm Kit
67% (6)
ACSS THALES ATR-500-600 Technical Support Comm Kit
52 pages
CLM Atr72 Full-Location PDF
100% (1)
CLM Atr72 Full-Location PDF
447 pages
Acceptance Manual Customer Run Up
100% (1)
Acceptance Manual Customer Run Up
16 pages
Spec MPC Iss2
No ratings yet
Spec MPC Iss2
233 pages
Cfm56 7b Familiarization Print
100% (6)
Cfm56 7b Familiarization Print
86 pages
A350-Avionics PDF
100% (4)
A350-Avionics PDF
207 pages
32 Landing Gear PDF
100% (4)
32 Landing Gear PDF
208 pages
Honeywell Aerospace Yeovil Component Maintenance Manual
No ratings yet
Honeywell Aerospace Yeovil Component Maintenance Manual
41 pages
Inspection After Hard Landing and Exceeding Vle, Vlo: Zoning Data
No ratings yet
Inspection After Hard Landing and Exceeding Vle, Vlo: Zoning Data
18 pages
Acceptance Manual Customer Flight Check
No ratings yet
Acceptance Manual Customer Flight Check
19 pages
7055 Tech Sheet
No ratings yet
7055 Tech Sheet
2 pages
Multi Purpose Computer Presentation
No ratings yet
Multi Purpose Computer Presentation
13 pages
ATR LM Class
100% (1)
ATR LM Class
30 pages
ATR 33 301 Rev02
No ratings yet
ATR 33 301 Rev02
68 pages
Avionics System (AVS) Aboard ATR - 600: ATA104-I General Familiarization Training Course
100% (1)
Avionics System (AVS) Aboard ATR - 600: ATA104-I General Familiarization Training Course
19 pages
568F-1 Prop Sys Aircraft Integration
No ratings yet
568F-1 Prop Sys Aircraft Integration
36 pages
CH-34 (Nav System)
No ratings yet
CH-34 (Nav System)
22 pages
23read 1st MSI 23-52-00 NAS - Issue 01 - Draft - 22-12-2010
No ratings yet
23read 1st MSI 23-52-00 NAS - Issue 01 - Draft - 22-12-2010
49 pages
RTO and BOOST Presentation
100% (1)
RTO and BOOST Presentation
13 pages
Resumen Atr A Color
No ratings yet
Resumen Atr A Color
26 pages
Description/Operation: Acms Report Menu List of Previous Rep Stored Reports Man Reqst Reports
No ratings yet
Description/Operation: Acms Report Menu List of Previous Rep Stored Reports Man Reqst Reports
4 pages
Engine Start Procedure Check List ATR 72-600
No ratings yet
Engine Start Procedure Check List ATR 72-600
2 pages
ATR 42-72 Maintenance Training Record (Rev 0 - Jul 2013)
100% (2)
ATR 42-72 Maintenance Training Record (Rev 0 - Jul 2013)
38 pages
Electropump Removal: Job Card Package Title: IW7 - ATR72 Tail Number - MSN ALL
No ratings yet
Electropump Removal: Job Card Package Title: IW7 - ATR72 Tail Number - MSN ALL
6 pages
A320 A321 P2F Mmel PTC R09 Dec 01 21 PDF
No ratings yet
A320 A321 P2F Mmel PTC R09 Dec 01 21 PDF
170 pages
SB Index 72 APR-2020 PDF
No ratings yet
SB Index 72 APR-2020 PDF
133 pages
A320 - 319 LCL Rev A3
No ratings yet
A320 - 319 LCL Rev A3
21 pages
Atr b1 - b2 - Introduction Module 12-05-2014
No ratings yet
Atr b1 - b2 - Introduction Module 12-05-2014
184 pages
Eec Fault Codes Rev 1
100% (4)
Eec Fault Codes Rev 1
753 pages
Filter Assy - Avionics Ventilation - Removal & Installation
100% (1)
Filter Assy - Avionics Ventilation - Removal & Installation
13 pages
Atr Parts List
No ratings yet
Atr Parts List
23 pages
ATA 20 Standard Practices PDF
100% (1)
ATA 20 Standard Practices PDF
6 pages
Agt Mtm Atr 456 23 Rev 07 Nov 20
No ratings yet
Agt Mtm Atr 456 23 Rev 07 Nov 20
90 pages
Agt-Mtm-456 - Ata 27-500
No ratings yet
Agt-Mtm-456 - Ata 27-500
145 pages
Atr Ata45
100% (1)
Atr Ata45
8 pages
ATR Tool As Jul23
No ratings yet
ATR Tool As Jul23
13 pages
Brake Inspection
No ratings yet
Brake Inspection
5 pages
T2cas Eddit Tool Manual
No ratings yet
T2cas Eddit Tool Manual
56 pages
AGT-MTM-ATR 456-26-REV 07 NOV 20
No ratings yet
AGT-MTM-ATR 456-26-REV 07 NOV 20
77 pages
Mmel Atr
No ratings yet
Mmel Atr
95 pages
Single Aisle Technical Training Manual T1+T2 (CFM 56) (LVL 2&3) Information Systems
No ratings yet
Single Aisle Technical Training Manual T1+T2 (CFM 56) (LVL 2&3) Information Systems
40 pages
Exame de Atr72-212a
No ratings yet
Exame de Atr72-212a
6 pages
Atr Introduction
100% (1)
Atr Introduction
7 pages
Ata 00 General Familiarization
No ratings yet
Ata 00 General Familiarization
25 pages
Atr72-600 Diff b1b2 Iss 1 Rev 0
100% (1)
Atr72-600 Diff b1b2 Iss 1 Rev 0
912 pages
BOOKLET ATR-600 Rev 01-1 (1) (001-025)
No ratings yet
BOOKLET ATR-600 Rev 01-1 (1) (001-025)
25 pages
CTC-232 Fda PDF
No ratings yet
CTC-232 Fda PDF
205 pages
Atr72 Limitation Level 1,2,3
No ratings yet
Atr72 Limitation Level 1,2,3
3 pages
3 ATR - 600 ATA104-I ATA31 Rev-01
No ratings yet
3 ATR - 600 ATA104-I ATA31 Rev-01
44 pages
Atr Pec Trimming Procedure
No ratings yet
Atr Pec Trimming Procedure
5 pages
Reading Principle of PCMCIA Card
No ratings yet
Reading Principle of PCMCIA Card
4 pages
A320 Amm - Ata 74 (Pw11) - Ignition (P 78)
No ratings yet
A320 Amm - Ata 74 (Pw11) - Ignition (P 78)
78 pages
Atr 72
No ratings yet
Atr 72
583 pages
Atr 72
No ratings yet
Atr 72
19 pages
CIDS
No ratings yet
CIDS
2 pages
Agt-Mtm-456 - Ata 22-500 1
No ratings yet
Agt-Mtm-456 - Ata 22-500 1
93 pages
ATR LM7 Radar
100% (2)
ATR LM7 Radar
68 pages
Aircraft - SpecSheetDetails - AT72-1025 - 27jun2021 r1
No ratings yet
Aircraft - SpecSheetDetails - AT72-1025 - 27jun2021 r1
11 pages
ATA 36 B1
No ratings yet
ATA 36 B1
96 pages
Paldo II: Paldo Returns
No ratings yet
Paldo II: Paldo Returns
2 pages
Atr42 - 72 MPC Specs
No ratings yet
Atr42 - 72 MPC Specs
233 pages
A318/A319/A320/A321: Service Bulletin
No ratings yet
A318/A319/A320/A321: Service Bulletin
118 pages
Multipair Ethernet over DMT ver.2: ver, #2
From Everand
Multipair Ethernet over DMT ver.2: ver, #2
Ashlan Chidester
No ratings yet
A320 SRM Oem FM
100% (3)
A320 SRM Oem FM
792 pages
UNITED A319-A320 System and Avionics Supplement S-261
100% (4)
UNITED A319-A320 System and Avionics Supplement S-261
55 pages
Espm 20-52-00
No ratings yet
Espm 20-52-00
27 pages
31-35-12 Rev4
100% (1)
31-35-12 Rev4
420 pages
Advisory Circular: U.S. Department of Transportation
No ratings yet
Advisory Circular: U.S. Department of Transportation
83 pages
Customer: VT Type: ATR72 Rev. Date: April 1, 2008 Manual: AMMDO Selected Effectivity: ALL 31-30-00-019
No ratings yet
Customer: VT Type: ATR72 Rev. Date: April 1, 2008 Manual: AMMDO Selected Effectivity: ALL 31-30-00-019
5 pages
MaintenanceProgusingReliabilityMethods MSG-3 Issue2
0% (1)
MaintenanceProgusingReliabilityMethods MSG-3 Issue2
5 pages
Acceptance Manual Customer Run Up
100% (1)
Acceptance Manual Customer Run Up
17 pages
CUST FLIGHTCHECK 42-500 Is2
No ratings yet
CUST FLIGHTCHECK 42-500 Is2
20 pages
Acceptance Manual Customer Run Up
No ratings yet
Acceptance Manual Customer Run Up
17 pages
Training Manual: EASA Part-66 53 Level 3
No ratings yet
Training Manual: EASA Part-66 53 Level 3
22 pages
Training Manual: EASA Part-66 57 Level 3
No ratings yet
Training Manual: EASA Part-66 57 Level 3
40 pages
Training Manual: EASA Part-66 56 Level 3
No ratings yet
Training Manual: EASA Part-66 56 Level 3
11 pages
Training Manual: EASA Part-66 78 Level 3
No ratings yet
Training Manual: EASA Part-66 78 Level 3
17 pages
Training Manual: EASA Part-66 54 Level 3
No ratings yet
Training Manual: EASA Part-66 54 Level 3
10 pages
Training Manual: EASA Part-66 72 Level 3
100% (2)
Training Manual: EASA Part-66 72 Level 3
16 pages
SL 24 6008 01
No ratings yet
SL 24 6008 01
62 pages
Training Manual: EASA Part-66 75 Level 3
No ratings yet
Training Manual: EASA Part-66 75 Level 3
23 pages
Ata 70 Engine Performance: Training Manual
100% (1)
Ata 70 Engine Performance: Training Manual
14 pages
8 - Banding Tool (Operating Instruction)
No ratings yet
8 - Banding Tool (Operating Instruction)
8 pages
4 - Test Console For Pneulatic De-Icer Bonding
No ratings yet
4 - Test Console For Pneulatic De-Icer Bonding
2 pages
Dictionary of Marketing A. Ivanovic and P.H. Collin
No ratings yet
Dictionary of Marketing A. Ivanovic and P.H. Collin
305 pages
Nature's End
No ratings yet
Nature's End
375 pages
Bruinessen - Kitab Kuning
100% (1)
Bruinessen - Kitab Kuning
45 pages
Laser Fundamentals: Second Edition
No ratings yet
Laser Fundamentals: Second Edition
2 pages
(Palgrave Studies in Nineteenth-Century Writing and Culture) Sara Thornton (Auth.) - Advertising, Subjectivity and The Nineteenth-Century Novel - Dickens, Balzac and The Language of The Walls-Palgrave
No ratings yet
(Palgrave Studies in Nineteenth-Century Writing and Culture) Sara Thornton (Auth.) - Advertising, Subjectivity and The Nineteenth-Century Novel - Dickens, Balzac and The Language of The Walls-Palgrave
225 pages
REVISED DLP September 21-22 E-ACAD
No ratings yet
REVISED DLP September 21-22 E-ACAD
12 pages
Why Is God Laughing? by Deekak Chopra - Excerpt
36% (22)
Why Is God Laughing? by Deekak Chopra - Excerpt
20 pages
Art Books List 1
No ratings yet
Art Books List 1
13 pages
Permissions Request Form: Material To Be Reproduced
No ratings yet
Permissions Request Form: Material To Be Reproduced
2 pages
104564
No ratings yet
104564
59 pages
Identifying First Editions
No ratings yet
Identifying First Editions
6 pages
What Is A Rare Book
No ratings yet
What Is A Rare Book
3 pages
The Perennials Audiobook Supplement SDF
No ratings yet
The Perennials Audiobook Supplement SDF
36 pages
Intermediate 01 (Units 1-3)
No ratings yet
Intermediate 01 (Units 1-3)
26 pages
Web 2.0 For The Novel
100% (1)
Web 2.0 For The Novel
2 pages
The Power of A Half Hour by Tommy Barnett (Sneak Peek)
No ratings yet
The Power of A Half Hour by Tommy Barnett (Sneak Peek)
20 pages
1970.2004 - A.E. Harvey - A Companion To The New Testament (Prefaces) - 9780521788342
No ratings yet
1970.2004 - A.E. Harvey - A Companion To The New Testament (Prefaces) - 9780521788342
9 pages
Prioritizing Academic Programs and Services Reallocating Resources to Achieve Strategic Balance Second Edition Revised and Updated Josse Bass Higher and Adult Education Robert C. Dickeson instant download
100% (1)
Prioritizing Academic Programs and Services Reallocating Resources to Achieve Strategic Balance Second Edition Revised and Updated Josse Bass Higher and Adult Education Robert C. Dickeson instant download
51 pages
Graciela Perez Martinez Biomagnetica
0% (2)
Graciela Perez Martinez Biomagnetica
3 pages
Download Full Religion and American Politics From the Colonial Period to the Present 2nd Edition Mark A. Noll PDF All Chapters
100% (6)
Download Full Religion and American Politics From the Colonial Period to the Present 2nd Edition Mark A. Noll PDF All Chapters
81 pages
International Organization
No ratings yet
International Organization
221 pages
A Guide To Collecting Harry Potter Books
No ratings yet
A Guide To Collecting Harry Potter Books
10 pages
Byron's Poetical Works, Volume 1 by Byron, George Gordon Byron, Baron, 1788-1824
No ratings yet
Byron's Poetical Works, Volume 1 by Byron, George Gordon Byron, Baron, 1788-1824
519 pages
s08 PDF
No ratings yet
s08 PDF
244 pages