Getting To Grips With A320 &

Recording Systems - Getting to grips with A320 &
A330-A340 ACMS, FDRS & CVRS
ATA: 23-71 FIN: Ref: 31.33.00010

31-33
31-36
31-37
A/C Type: A318 A/C Serie: Topic: First Issue 21-OCT-2013
A319 Date:
A320
A321
A330
A340
Part Number: Last Publication 19-JUL-2017
Date:
Supplier:
Linked Linked
Articles: Documentation:
Old Wise Ref:

EngOps-16274
Old ISI Ref:

31.33.00003
Engineering Support
First Issue Date: 21-OCT-2013
Model: Last Publication Date: 19-JUL-2017
Manufacturer:
SUBJECT: GETTING TO GRIPS WITH A320 & A330/A340 ACMS / FDRS /

CVRS RECORDING SYSTEMS & USER
RECOMMENDATIONS
ATA CHAPTER: 31-33-00, 31-36-00, 31-37-00, 23-71-00

AIRCRAFT TYPE: A320, A330/A340 Family
APPLICABILITY: All A320, A330/A340
REFERENCES: AMM chapter 31-33-00, 31-36-00, 31-37-00, 23-71-00

1. PURPOSE
The purpose of this article is to provide customers with some basic information and
user recommendations on A320, A330/A340 Family ACMS / FDRS / CVRS
recording systems.
This article aims at helping customers to better understand the system architectures
and to use the various recording functions in the most efficient way as possible within
the scope of their daily operations.
TABLE OF CONTENTS
1. PURPOSE..............................................................................................................................2
2. SCOPE OF THE DOCUMENT...............................................................................................5
3. DESCRIPTION: .....................................................................................................................5
3.1. ACMS / FDRS / CVRS - RECORDING SYSTEMS OBJECTIVES .............................................5
3.1.1. Flight data recording (FDRS) objective ............................................................................6
3.1.2. Cockpit voice & datalink recording (CVRS) objective ...................................................8
3.1.3. A/C condition & monitoring (ACMS) objective................................................................9
3.2. ACMS / FDRS / CVRS - SYSTEM ARCHITECTURE PRINCIPLES ........................................10
3.2.1. CVRS architecture overview ...........................................................................................10
3.2.1.1. Audio recording ..............................................................................................11
3.2.1.2. Data-link recording .........................................................................................11
3.2.2. FDRS and ACMS architecture overview .......................................................................11
3.2.2.1. FDIU / DMU / FDIMU Configurations .............................................................14
3.2.2.2. FDIMU/DMU data acquisition .........................................................................16
3.2.2.3. ACMS cockpit interface ..................................................................................18
3.2.2.4. ACMS/FDRS data output ...............................................................................18
3.2.3. QAR versus DAR data recording....................................................................................19
3.2.3.1. External QAR 3TU vs QAR 2TV LRU.............................................................20
3.2.3.2. Wireless Ground Link (WGL) QAR units: .......................................................21
3.2.3.3. QAR / DAR LRU removal ...............................................................................23
3.2.3.4. QAR and DAR data recording onto FDIMU / DMU PCMCIA card..................24
3.2.4. FDIMU / DMU PCMCIA interface ...................................................................................24
3.2.4.1. PCMCIA card Configuration ...........................................................................25
3.2.4.2. PCMCIA recording file structure .....................................................................28
3.2.4.3. Formatting guidelines .....................................................................................29
3.2.4.4. PCMCIA Card capacities................................................................................29
3.2.4.5. PCMCIA data dump........................................................................................30
3.2.5. Recording autonomy and speed considerations..........................................................30
3.2.6. Start/stop recording logic considerations ......................................................................31
3.2.7. FDIU / DMU / FDIMU Software loading considerations..............................................34
3.3. ACMS MAIN FUNCTIONS ................................................................................................35
3.3.1. Generality ...........................................................................................................................35
3.3.2. ACMS Reports...................................................................................................................36
3.3.2.1. Report characteristics.....................................................................................37
3.3.2.2. Generic recommendations .............................................................................39
3.3.3. ACMS Real Time monitoring...........................................................................................42
3.3.3.1. Parameter Call-up Functions..........................................................................42
3.3.3.2. Other MCDU functions ...................................................................................44
3.3.4. ACMS SAR / DAR and QAR Data Recording ..............................................................45
3.3.4.1. SAR recording function...................................................................................45
3.3.4.2. DAR recording function ..................................................................................45
3.3.4.3. QAR recording function ..................................................................................47
3.4. ACMS – PROGRAMMING CAPABILITIES ...........................................................................47
3.4.1. FDIMU/DMU Ground Programming tool (GSE) ...........................................................47
3.4.2. Programmable functions: .................................................................................................48
3.4.3. Programming interfaces ...................................................................................................49
3.4.3.1. On-board MCDU programming ......................................................................50
3.4.3.2. ACARS uplink programming...........................................................................50
3.4.3.3. On-ground GSE programming........................................................................50
3.5. ACMS / FDRS / CVRS – DATA DOWNLOADING AND READOUT ........................................51
3.5.1. FDRS (FDR / QAR data) downloading and readout....................................................53
3.5.1.1. FDR/QAR data downloading: .........................................................................53
3.5.1.2. FDR/QAR data readout: .................................................................................55
3.5.2. ACMS (DMU report / DAR / SAR data) download and readout ................................57
3.5.2.1. FDIMU / DMU PCMCIA data dump ................................................................58
3.5.2.2. MDDU data dump...........................................................................................58
3.5.2.3. Remote Print Button .......................................................................................61
3.5.2.4. ACARS output ................................................................................................62
3.5.2.5. MCDU interface ..............................................................................................63
3.5.2.6. ACMS data readout: .......................................................................................64
3.5.3. CVRS (audio & datalink data) downloading and readout ...........................................66
3.5.3.1. Concerning CVRS data downloading: ............................................................67
3.5.3.2. Concerning CVRS data readout: ....................................................................67
3.6. ACMS / FDRS / CVRS – RETROFIT CONSIDERATIONS ....................................................67
4. REFERENCES.....................................................................................................................69
4.1. AMM REFERENCES ........................................................................................................69
4.2. IPC REFERENCES ...........................................................................................................69
4.3. TSM REFERENCES .........................................................................................................69
4.4. ASM REFERENCES .........................................................................................................69
4.5. AWM REFERENCES ........................................................................................................69
4.6. AIRBUS SIL REFERENCES .............................................................................................69
4.7. AIRBUS BOOKLET REFERENCES....................................................................................70
4.8. FIN REFERENCES ...........................................................................................................70
ANNEX 1 – ONBOARD DATA RECORDING AND MAINTENANCE CONCEPT .....................71
ANNEX 2 – FDRPL APPLICATION ...........................................................................................72
ANNEX 4 – SAGEM FDIMU PCMCIA RECORDING FORMAT AND FILE STRUCTURE........74
ANNEX 5 – TELEDYNE FDIMU PCMCIA RECORDING FORMAT AND FILE STRUCTURE..76
ANNEX 6 – TELEDYNE WGL-QAR PCMCIA STORAGE RECORDING FORMAT..................78
ANNEX 7 – GSE VENDOR (FDIMU/DMU GROUND PROGRAMMING TOOLS) .....................79
ANNEX 8 – LIST OF STANDARD ACMS REPORTS................................................................80
ANNEX 9 – READOUT AND ANALYSIS TOOLS......................................................................82
ANNEX 10 – MAILING/CONTACT INFORMATION...................................................................83
ANNEX 11 – VENDOR SIL’S .....................................................................................................84
GLOSSARY ................................................................................................................................85
1. SCOPE OF THE DOCUMENT
The purpose of this article is to provide customers with some basic information and
some guidelines on the A320, A330/A340 Family ACMS / FDRS / CVRS recording
systems:
- Aircraft Condition Monitoring System (ACMS 1)
- Flight Data Recording System (FDRS)
- Cockpit Voice Recorder System (CVRS)
This article aims at helping customers to better understand the system architectures,
its operation and specificities, and to use the various recording functions in the most
efficient way as possible in order to support and enhance their daily operations.
The ACMS / FDRS / CVRS recording systems provide various users (investigation
authorities, operators, aircraft and systems/engine manufacturers, flight safety offices
and other data consumers) with numerous standard capabilities and several options
to collect and to monitor flight data on a regular or occasional basis for multiple
purposes.
Please note that the SIL contains generic information applicable to a wide range of
possible aircraft but does not intend to be exhaustive, and may vary according to
each aircraft configuration.
AMM or other maintenance technical documents remain the reference.
(1) ACMS is also called Aircraft Integrated Data System (AIDS) on A320 Family aircraft.
The “ACMS” wording will only be used along the SIL for sake of simplicity.
2. DESCRIPTION:
2.1. ACMS / FDRS / CVRS - Recording systems objectives
The development and installation of the ACMS and FDR & CVR systems are
primordial as it plays a major role in aircraft accident and incident investigation
(contributing to operational efficiency and promoting aviation safety) and in the today
economic context & highly competitive market to meet airline operational needs:
- to quickly, efficiently, accurately determine the cause of an accident/incident

and prevent future occurrences (FDRS & CVRS),
- to optimise day-to-day operations and streamline the maintenance actions
in a preventive and proactive way (ACMS),
• by identifying arising faults within Engines and A/C systems in advance
before they occur (detection and notification of exceedances / anomalies
of A/C systems deviating from normal behavior,),
• by supporting specific trouble-shooting actions (complex T/S or in-depth
investigation when persistent issues are experienced, to confirm or
invalidate a suspicion),
• by collecting data for various purposes (meet specific flight data
monitoring requirements or needs: FDM, FOQA programs),
• to reduce repair time and maintenance costs in the most effective and
economic way.
- to increase profitability.
[see ANNEX1 for brief overview on Onboard Data Recording and Maintenance
concept]
ACMS and FDRS data recording concept and main applications
2.1.1. Flight data recording (FDRS) objective
The purpose of the FDRS is to record a set of relevant flight parameters required to
accurately determine the aeroplane flight path, speed, attitude, engine power,
configuration and operation in order to support the accident/incident inquiries. The
FDRS is designed in compliance with the mandatory recording requirements from
Authorities (civil aviation’ regulatory agencies) to enable operators to fulfil their
operational Regulations (e.g. EU-OPS (JAR-OPS), FAR121.344, and other national
regulations).
The recording is performed by means of specific avionics hardware and software

equipment (FDRS equipment, source systems equipment), and wiring installation (with
suitable source connections and pin programming activations).
The scope of FDRS has been extended throughout the years, as a secondary
objective, to support and optimize flight operations, by facilitating access to the FDR
data and by increasing storage capacities by the use of additional recording means
and devices (e.g. QAR data recording).
The FDRS is mainly controlled by the FDIU equipment, or FDIU part of the FDIMU
equipment in charge of the flight data acquisitions, together with the use of other
ancillary recording equipment (FDR, 3-axis Linear Accelerometer, optional QAR LRU,
cockpit devices).
Flight data recording (FDRS)

2.1.2. Cockpit voice & datalink recording (CVRS)
objective
The CVRS is designed to record audio data (cockpit crew voice communications,
audio signals, ambient noises), as well as, for the newly proposed architectures,
datalink communications (Air-to-Ground , Air-to-Air CNS/ATM digital
communications and crew actions) in order to meet the applicable mandatory
recording requirements.
The audio and datalink recording is also performed by means of specific avionics
hardware and software equipment (CVR equipment, cockpit instruments, and relevant
source systems equipment), and wiring installation (with suitable source connections
and pin programming activations).
The datalink recording has been recently introduced on AIRBUS fleet and concerns
some specific aircraft only, equipped with Datalink systems, and has been defined in
compliance with the applicable regulation.
Cockpit voice recording (CVRS)

- audio data –
Cockpit voice recording (CVRS)

- datalink communications -
2.1.3. A/C condition & monitoring (ACMS) objective
The objective of the ACMS is to monitor and to report engine & aircraft system
parameters in order to support aircraft maintenance, to perform trend and
exceedance monitoring, to support flight operations, for FOQA/FDM monitoring or for
in-depth T/S analysis, among other applications.
The ACMS is mainly controlled by the DMU equipment, or DMU part of the FDIMU
equipment, together with the use of other ancillary recording equipment (optional
QAR LRU used in DAR function) and other aircraft system interfaces (MCDU, MDDU,
ACARS MU/ATSU,..).
For this purpose, the ACMS acquires characteristic system data and provides the
operators with performance and trend information as well as indications of incipient
deviations of any system conditions from normal:
- Predictive monitoring to identify anomalies before real failure occurrence

and anticipate maintenance actions aiming at preventing and minimizing
incident/accident occurrences.
- Condition-based monitoring to provide performance and trend information

(Engine Condition monitoring, APU health monitoring, A/C systems and
Structure monitoring).
A/C Condition Monitoring System (ACMS)

The ACMS data recording means are also available for extensive trouble-shooting
campaigns, if complex in-service problems need to be solved.
Besides the above considerations, the ACMS is usually associated with various
Ground Support Equipment (GSE) tools used to further process the acquired ACMS
data (AIRMAN, AirFASE, APM or other data exploitation tools,..) or to support the
ACMS programming operations (FDIMU/DMU vendor GSEs).
A dedicated ACMS ground tool (FDIMU/DMU vendor GSE) enables airlines to

configure some user-programmable ACMS functions and program their own
monitoring functions according to their needs (ACMS database customization).
2.2. ACMS / FDRS / CVRS - System architecture principles
Though having their own specificities, the A320 Family and A330/A340 Family mostly
present the same Recording systems architecture in principle, briefly depicted in the
below chapter.
2.2.1. CVRS architecture overview
The CVR System for the A320 Family aircraft is composed of:
• one Cockpit Voice Recorder (CVR *)
• one Cockpit Area Microphone (CAM)
• one Preamplifier module
• one TEST push-button, one ERASE push-button
• one headset plug
• one recording relay logic to manage recording phases according to the
A/C configuration.
The CVR System for the A330/A340 Family aircraft is composed of:
• one Cockpit Voice Recorder (CVR *)
• one Cockpit Area Microphone (CAM)
• one Cockpit Voice Recorder Control Unit (CVR CU) which integrates
preamplifier, TEST and ERASE functions, one bargraph indicator one
headset and one boomset plug
• one recording relay logic to manage recording phases according to the
A/C configuration.
The various equipments are designed in accordance with the standards of ARINC
757 characteristics to ensure compatibility with existing systems/equipment and allow
flexible installation.
The CVR system is associated with a Ground Support Equipment (CVR GSE) for
data download and readout operations (audio data and, when applicable, datalink
messages).
(*) Solid State CVR (SSCVR) or Magnetic Tape CVR as regards older equipment.
Note: Several CVR equipments are certified by Airbus, ranging from oldest to
newest CVR units using different technology for data recording (magnetic
tape, solid state memory). The newest CVR models are solid state recorders
(SSCVR) while former models use magnetic tape technology. Metal foil for the
very first generation recorders is no longer used.
The “CVR” wording will be used along the SIL for sake of simplicity.
2.2.1.1. Audio recording
The CVR System is designed to record the following information coming from the
Audio Management Unit (AMU) and its remote microphone (CAM) source:
 voice communications transmitted from or received on the flight deck by radio,

 the aural environment of the flight deck including the audio signals received from
each boomset and mask microphone in use,
 voice communications of flight crew members on the flight deck using the aircraft
interphone system,
 voice or audio signals identifying navigation or approach aids introduced into a
headset or loudspeaker,
 voice communications of flight crew members on the flight deck using the public
address system.
2.2.1.2. Data-link recording
The CVR System has recently evolved to record the required data-link
communications messages from Datalink systems as required by the new regulation
(mostly ATC related messages) in addition to the traditional audio data recording
function.
(new regulation requirements: FAR Amendments 25-124 and 121-338 - Revisions to
Cockpit Voice Recorder and Flight Data Recorder regulations -, and other regulation
requirements EASA EU-OPS/ICAO/others)
The recording of datalink communications is therefore not implemented on all

AIRBUS A/C (not standard), but depends on the A/C configuration in accordance with
the applicable regulatory requirements or operators’ option.
2.2.2. FDRS and ACMS architecture overview
The ACMS and FDRS functions are supported by various equipment and components.
- ACMS and FDRS related equipment (FDIU, DMU, FDIMU, FDR, 3-axis Linear
Accelerometer,..),
- A/C source systems equipment (other avionics computers with appropriate bus
connections),
- A/C Interfaces to several peripheral devices (MCDU, MDDU, Printer, ACARS

MU/ATSU, cockpit instruments),
- use of ancillary or optional recording equipment/devices (PCMCIA card

interface, external QAR LRU used in DAR or QAR function).
Note: Several FDR equipment are certified by Airbus, ranging from oldest to newest
FDR units using different technology for data recording (magnetic tape, solid
state memory).
The newest FDR models are solid state recorders (SSFDR) while former
models use magnetic tape technology (e.g. FDR).
Metal foil for the very first generation recorders is no longer used.
The “FDR” wording will be used along the SIL for sake of simplicity.
The aircraft (system and engine) data can be collected by means of the FDRS or
ACMS systems through various recording means and in different formats (FDR data
= QAR data, ACMS reports, DAR data, or SAR data).
The data collection and output means mostly depend on the aircraft configuration,
varying from one installation to another (if the aircraft is equipped with a DMU / FDIU
or FDIMU computer, if providing some alternate recording means like integrated
PCMCIA media capability, if dataloader MDDU/DLRB devices and/or if any external
QAR recorder is installed), among other criteria to be considered (type of software
version loaded, bus connections,..).
The functions are inherent to each equipment, manufactured by different vendors

(TELEDYNE, SAGEM, HONEYWELL certified products) and having consequently their
own design specificities/capabilities.
From a data acquisition standpoint, several configurations are today certified by

AIRBUS and deployed in-service.
Depending on the aircraft configuration, the following configurations can be found:
1) FDIU + DMU configuration
2) FDIMU configuration
3) FDIU + FDIMU configuration (FDIMU working as a DMU function only)
which can therefore provide different functionalities and output means, and be
expanded through the use of external and optional QAR LRU equipment (used in
QAR FIN 3TU function or used in DAR FIN 2TV function).
Typical FDIU + DMU configuration
Typical Full FDIMU configuration

2.2.2.1. FDIU / DMU / FDIMU Configurations
 FDIU + DMU configuration
This configuration corresponds to the oldest A320 & A330/A340 configurations but still
in use on many AIRBUS aircraft.
The FDIU (FIN 2TU) is designed to perform the FDRS functions.
The DMU (FIN 1TV) is designed to perform the ACMS functions.
FDIU + DMU configuration
 Full FDIMU configuration
This configuration corresponds to the newest A320 & A330/A340 configurations

based on FDIMU TELEDYNE or SAGEM LRU equipment.
This configuration relies on the FDIMU which combines both FDIU and DMU
functions into a single unit, allowing operators to benefit from various improvements
(gain in weight, extended recording functions, reliability, less power consumption,
enhanced GSE and MCDU programming capabilities, etc.).
Note: The FDIMU software is made up of two parts, the FDIU software and the DMU
software partition.
These two parts execute out of two distinct processors, each implemented as
a separate single board computer.
The FDIMU (FIN 10TV) is designed to achieve its FDIU (FDRS) and is DMU (ACMS)
assigned functions, and has been built accordingly with the necessary processor
boards and input/output (I/O) interface.
The FDIMU is interfaced with many A/C systems/equipment for data acquisition, and
for data output to peripheral devices (ACARS/ATSU, cockpit Printer, MDDU, QAR
equipment/DAR equipment if installed...).
Full FDIMU configuration
 FDIU + FDIMU (working as a DMU) configuration
This alternate configuration corresponds to the latest certified alternative, allowing

some customers to use the FDIMU as a DMU only to replace their former DMU’s
without replacing their original FDIUs (in case of obsolescence concern for instance
or for other reasons).
The FDIMU (DMU only) capabilities are limited compared to Full FDIMU usage due
to limited wiring connections and other specificities, but allows to get same
functionalities as previous FDIU + DMU configuration.
FDIU + FDIMU (working as a DMU) configuration
Note: This configuration is presently applicable to A320 family only (not certified on
A330/A340 aircraft yet).
2.2.2.2. FDIMU/DMU data acquisition
By design, the DMU’s or FDIMU’s are devoted to collect some aircraft parameters
and, for this purpose, connected to a wide range of A/C source systems so as to
access to the largest amount of aircraft data as possible (among the pool of existing
aircraft parameters) for flexible and efficient monitoring:
 data acquired from various A/C connected source systems (Engines, Fuel, Air
Data systems,...)
 mostly based on ARINC429 DITS data busses connections and some dedicated
discrete inputs
FDIMU/DMU data acquisition interfaces

 FDRS acquisition and recording
The parameters, that are acquired and subsequently recorded in the FDR, depend
on which operational regulation the A/C has to comply with and its date of
manufacturing (date of first issuance of individual certificate of airworthiness). The
A/C has been equipped accordingly by AIRBUS with compliant software, hardware
equipment and wiring modifications for recording.
A set of essential parameters as specified by the authorities (mandatory parameters)
and AIRBUS is basically acquired and recorded, along with some other relevant A/C
parameters (documentary parameters) to support the inquiries.
The recording configuration and precise list of recorded parameters depend on

several elements, among which:
- the aircraft model,
- the recording equipment installed (FDI[M]U H/W and S/W components, FDR H/W),
- the source systems interfaces with the precise A/C wiring configuration,
- the pin-programming selected on A/C (64, 128, 256, 1024 words-per-second).
On A320 and A330/A340 Family in particular, the following recording configurations

are possible:
- 64 wps (words per second) configuration
- 128 wps configuration
- 256 wps configuration
- 1024 wps configuration (*)
(*) according to new regulation requirements: FAR Amendments 25-124 and 121-
338 - Revisions to Cockpit Voice Recorder and Flight Data Recorder regulations
Any change in recording speed configuration for the FDRS must be performed by the
application of a certified modification (no user programmable).
The installation of new A/C systems or functions on A/C (new standard of equipment,
new H/W or S/W novelties) may moreover require the need for recording additional
parameters and the evolution of the recording configuration.
 ACMS acquisition and recording
The parameters are acquired from various A/C source systems connected to the DMU
or FDIMU (Engines, Fuel, Air Data systems,...).
The acquisition differs from the FDRS part, with higher number of sources connected
and multiple recording options (ACMS user programmable functions).
Depending on the type of data considered (e.g. DAR, SAR) and monitoring needs, the
acquisition rates and recording speeds may differ and be reprogrammed by user (via
GSE).
2.2.2.3. ACMS cockpit interface
Cockpit interface overview with main communication devices
2.2.2.4. ACMS/FDRS data output
FDIMU (ACMS/FDRS) Data output overview

2.2.3. QAR versus DAR data recording
The purpose of this paragraph is to provide an overview and basic information on the
QAR & DAR recording means and their capabilities.
It is all the more important than “QAR data” can have very different meaning. These
means will operate differently function of the precise aircraft configuration at stake
(any external QAR LRU installed and its location, any FDIMU/DMU integrated
PCMCIA card available and its configuration…).
QAR data can be recorded:
- on an external QAR 3TU equipment (optional QAR LRU, if installed in FIN
3TU position , i.e. used in QAR function)
- on the integrated FDIMU PCMCIA card (if properly configured for it and for full
FDIMU configurations only)
The QAR data is a copy of the FDR data frame, coming from the FDIU equipment (or
FDIU part of FDIMU).
DAR data can be recorded:

- on an external QAR 2TV equipment (optional QAR LRU, if installed in FIN 2TV
position, i.e. used in DAR function)
- on the integrated FDIMU PCMCIA card or DMU PCMCIA card (when
available) (if properly configured for it)
The DAR data (programmable DAR data frame) is coming from the DMU equipment (or
DMU part of FDIMU).
QAR data vs DAR data recording
Note1: when an external “QAR equipment” LRU is therefore installed:

- in FIN 3TU position:
the data is supplied by the FDIU equipment (or FDIU part of FDIMU) and
the QAR LRU will record QAR data (= copy of the FDR data)
- in FIN 2TV position:
the data is supplied by the DMU equipment (or DMU part of FDIMU) and
the QAR LRU will record DAR data
Note2: A QAR equipment in 2TV position (= DAR) can be used to record

ACMS reports in addition to the DAR data frame. However, such a report
recording option requires installation of specific RS422 link between the DMU
and QAR 2TV equipment, as well as compatible QAR and FDIMU equipment
(FDIMU TELEDYNE only).
Note3: The certified FDIMU’s provide an integrated PCMCIA card slot, which
can be used for data recording and for software loading.
The PCMCIA card of the FDIMU can particularly be configured to record QAR
data (= copy of the FDR data), or DAR data, or both in parallel. The DAR data
(resp. QAR data) recorded into the FDIMU PCMCIA card will be the same
data as if recorded into an external QAR LRU used in DAR 2TV function (resp.
used in QAR 3T function).
Nevertheless, the PCMCIA recording functions are GSE programmable
(memory space allocation, start/stop logic [Flight phase dependent], data
wrapping options, etc....), which can lead to different recording periods. The
recordings will therefore not necessarily start/stop at the same time, upon the
same conditions, depending on the programmed PCMCIA trigger and selected
options.
2.2.3.1. External QAR 3TU vs QAR 2TV LRU
The QAR LRU equipment in FIN 3TU or 2TV position provides the following main
recording characteristics and capabilities:
External QAR 3TU (= QAR data) installation

 QAR data recording (only)
 fixed data frame (= copy of FDR data)
 easy access to data and download (function of the chosen media type: Tape / Optical
disk / PCMCIA card)
 wireless transmission capability possible if proper QAR model and wiring installed
(WGL-QAR LRU)
External QAR 2TV (= DAR data) installation :

 DAR data recording
 programmable DAR data frame
 easy access to data and download (function of the media type: Tape / Optical
disk / PCMCIA card)
 wireless transmission capability possible if proper QAR model and wiring installed
(WGL-QAR LRU)
 capability to record AIDS reports (provided RS422 link is available and
depending on QAR & FDIMU equipment - as per a.m. §3.2.3 Note2 -)
Several external QAR models are certified on A320 and A330/A340 Family and
can be installed in replacement to existing QAR LRUs (any old tape model for
instance) or as a new equipment when needed:
- ARINC404 or ARINC600 compliant models,
- from various vendors (THALES, TELEDYNE,...),
- with Tape, Optical Disk, or newer PCMCIA storage media card or wireless
data transmission capability,
- to be installed either in FIN 3TU (QAR data) or FIN 2TV (DAR data) position,
at operator’s convenience.
2.2.3.2. Wireless Ground Link (WGL) QAR units:
Several WGL QAR equipment (ARINC 600, equipped with GSM/GPRS radio
modules, using standard PCMCIA media card) are certified and available for
installation.
These WGL-QAR provides PCMCIA recording function and automated wireless
transfer of the recorded data when the aircraft is on the ground, shortly after
landing. Recorded data is transmitted via cellular/PCS phone communication
means and via internet network up to the Ground base station computer for data
processing.
Compared to standard QAR units or FDIMU/DMU integrated PCMCIA means, it is
then no longer necessary to remove the data manually from the A/C.
Wireless QAR equipment (e.g. TELEDYNE)
WGL-QAR main features:

• Data recorded into PCMCIA media and automatically transmitted at the
Gate using mobile telephone network and Internet services, up to end-
users
• No need for accessing the A/C, fully automated system
• Quick availability of the data, within minutes after A/C landing, compared
to manual downloading operations
• Alphanumeric display and keypad (located on QAR front face panel)

• Several models already certified (e.g. 4, 8 GSM radios) from TELEDYNE
supplier, to be used either in QAR or DAR position
This WGL-QAR function has proved to be of great interest to several operators to

fulfil their data monitoring operations. However, please be informed that such WGL-
QAR requires additional wiring modifications on A/C in addition to the installation of
the WGL-QAR equipment itself (ARINC600 WGL-QAR provisions).
Operators can contact their dedicated AIRBUS Fulfill Customer Order (FCO)
manager or QAR vendors for further information on these available products and
capabilities, when necessary.
Note1: The decision to install an external QAR LRU equipment on an A/C

actually depends on the operator’s scope of use of the ACMS and intended
operations, among other criteria to be considered like:
 the need for recording either DAR data or QAR data, or both simultaneously,
 the current A/C configuration (if the A/C is equipped with a FDIMU/DMU and providing
some alternate recording means or not - like PCMCIA capability -, and/or if the A/C is
already provisioned or not with ARINC404/ARINC600 wiring...),
 the external QAR equipment recording characteristics and desired technology (QAR
Tape, or Optical, or PCMCIA media or even wireless QAR models, to be challenged
against existing FDIMU/DMU PCMCIA means),
 any vendor preferences,
 cost considerations,
 other justifications at operator’s discretion.
Note2: Enclosed herewith some existing AIRBUS possibilities (non exhaustive list of
certified equipment) for QAR installation:
External QAR 3TU (= QAR data):
P/N ARINC Media Vendor

PC6033-3-56 A404 Tape SCHLUMBERGER
D50761-1-01 A404 Tape PENNY & GILES
D51438-1 A404 Tape PENNY & GILES
D52000-42200 A404 Optical PENNY & GILES
D52000-64000 A600 PCMCIA PENNY & GILES
1374-100-000 A404 Optical THALES
2248000-41 A404 Optical TELEDYNE
2243800-73 A600 WGL / PCMCIA TELEDYNE
External QAR 2TV (= DAR data):
P/N ARINC Media Vendor

D50761-1-01 A404 Tape PENNY & GILES
No miniQAR (also known as microQAR) are certified by AIRBUS today.

In case any operator wishes to install a miniQAR equipment on their aircraft, it is then
recommended to contact the dedicated FCO manager through usual RFC/RMO
process.
The use of QAR equipment and media type for data storage is very dependent on the
operator's monitoring needs and shall be adapted to the end-users.
There could be indeed a need to perform some downloads at specific time intervals,
on a regular or occasional basis. The type of QAR media used (size of optical disk,
PCMCIA card..) must therefore also be considered as it will influence the download
frequency (the higher capacity is used, the better, allowing higher data storage
durations and therefore reducing the need for accessing frequently to the aircraft),
unless the wireless option is preferred.
2.2.3.3. QAR / DAR LRU removal
In case external QAR equipment are no longer needed on A/C and it is decided to
rely on FDIMU QAR/DAR recording functions through PCMCIA interface instead,
operators have the possibility to definitely remove their QAR equipment along with its
associated disk from the A/C.
Such a removal is available through the embodiment of specific AIRBUS
modifications that will particularly adapt the ventilation plate, install safety clips on
relevant circuit breakers, among other necessary works.
There is no other alternate way nor approved procedure to deactivate QAR
equipment.
QAR removal will moreover provide a certain gain in weight.
Should any operator concur in removing its QAR, we would then recommend
contacting our FCO Manager through standard RFC/RMO procedure for appropriate
modification/SB embodiment.
2.2.3.4. QAR and DAR data recording onto FDIMU / DMU PCMCIA card
The PCMCIA card of the FDIMU (resp. DMU) can particularly be used to record QAR
data or DAR data or both (resp. DAR data).
The recording is however not systematic and depends on the programmed database
(GSE user-programmable functionality).
[see below chapter 3.2.4 for further detail in this regard]
2.2.4. FDIMU / DMU PCMCIA interface
The FDIMU’s and some DMU’s provide PCMCIA interface capability (integrated
PCMCIA card slot) which can be used:
- for the uploading of the S/W applications (for ACMS software only),
- and also for data recording.
The FDIU’s (FIN 2TU) do not provide PCMCIA interface.
Integrated
H/W part number DMU FDIMU A/C Type
PCMCIA card
P/N ED45A100  No A320 Family
P/N ED45A200  No A320 Family
P/N ED45A300  Yes A320 Family
P/N 795020-12-xxx  No A320 Family
P/N 795030-10-001  No A320 Family
P/N 795040-3x-00x  No A320 Family
P/N 2234320-01-01  Yes A320 Family
P/N 2234340-01-01  Yes A330/A340 Family
P/N 2234340-02-02  Yes A330/A340 Family
P/N 967-51x-00x  No A330/A340 Family
Note1: HAMILTON DMU’s P/N 795020-12-xxx models are equivalent to NORD

MICRO
903116243Bxxxxx models. These former NORD MICRO and HAMILTON
equipment are now managed by TELEDYNE vendor.
Note2: The FDIMU/DMU PCMCIA card can be used for ACMS S/W loading
only (not FDIU S/W loading). The FDIU S/W is loadable via PDL or MDDU
interface.
The PCMCIA functions (type of data to record, memory space allocation, and
other options,..) are freely programmable by user through the FDIMU/DMU
GSE.
The PCMCIA card of the FDIMU can be used to record several data (ACMS and
FDRS data), provided it is adequately configured for it (GSE programmable).
PCMCIA card can be configured to record:
- ACMS reports
- and/or DAR data
- and/or SAR data
- and/or QAR data (= copy of the FDR data for FDIMU equipment only, in full FDIMU
configuration)
In a similar way to the recording on the PCMCIA media of an external QAR LRU
equipment, we would like to highlight that it is also important to use an integrated
FDIMU/DMU PCMCIA card with adequate capacity in order to have efficient
recording (the higher size is used, the better). The capacity must be chosen in
accordance with the selected data recording speed to allow longer recording
autonomy and avoid the need for frequent download.
2.2.4.1. PCMCIA card Configuration
PCMCIA card can be used (programmed) for recording ACMS data (Reports, SAR
data, DAR data) or FDR data (QAR data). Such a PCMCIA recording option has
proved to be suitable to a large number of operators for flight data recording,
particularly sparing the need for using an external QAR 3TU or 2TV LRU equipment
or both.
The PCMCIA card of the DMU’s allows to record:

- Reports
- and/or DAR data
- and/or SAR data
The PCMCIA card of the FDIMU’s allows to record:

- Reports
- and/or DAR data
- and/or SAR data
- and/or QAR data (= copy of the FDR data)
Note that the PCMCIA recording functionality depends on the loaded ACMS S/W
database and is programmable by GSE (with a standard AIRBUS programming
provided by default at delivery function of the standard AIRBUS ACMS S/W version
installed).
The recording of the data may therefore not be activated or sufficient PCMCIA
memory space may not be allocated for storage of a specific type of data. Other
PCMCIA functions are moreover reprogrammable at Operator’s convenience (wrap
enable option, etc.)
It is therefore strongly recommended, in addition to the card size selection for a

suitable recording autonomy, to ensure that the card has been properly configured
to record its desired set of data and with proper memory space allocated on the
card.
 Example for SAGEM FDIMU’s:
The below information is an example of the default configuration applicable for an

A319 A/C equipped with SAGEM FDIMU P/N ED48A100, loaded with ACMS
standard 360-04020-020 & 360-04023-020 S/W version (AI05/V3406):
By default,
- only DAR data is recorded (neither the Reports, nor the SAR data, nor the
QAR data are recorded)
- a specific memory space allocation in percentage has also been assigned by

default (set to 20% for QAR and 80% for DAR allocation)
PCMCIA Memory Allocation example (SAGEM)
Note applicable for DMU software PN prior IAE software -050 and CFM software
-045:
Despite above default 20% memory allocation for QAR data, the QAR recording onto
PCMCIA card is not activated and therefore no QAR data is stored by default (only
DAR data will be recorded).
- if the standard database is loaded, only DAR data will be recorded on

PCMCIA card,
- in order to have Report data (or QAR or SAR) additionally recorded onto the
PCMCIA, the recording must be activated and the PCMCIA memory allocation
for these files must be configured (through SAGEM GSE tool).
This implies customization of the FDIMU database. The associated
folders and data will then appear on the card accordingly.
For further information on this part and GSE customization aspects, SAGEM vendor can
be contacted.
Note applicable from DMU software PNs IAE software -050 and CFM software -
045:
The QAR recording onto PCMCIA card is activated by default as per below default
PCMCIA Memory allocation:
- QAR data recording: 49%
- DAR data recording: 49%
- SAR data recording: 1%
- Reports recording: 1%
Above default PCMCIA Memory allocation can be customized through FDIMU

database programming
 Example for TELEDYNE FDIMU’s:
The below information is another example of the default configuration applicable for
A319 A/C equipped with TELEDYNE FDIMU P/N 2234320-01-01, loaded with ACMS
standard D04SAIA03C00000 S/W version:
By default,
- DAR and QAR data is recorded on PCMCIA
- a specific memory space allocation in percentage has also been assigned by

default, set to:
 49% for QAR

 49% for DAR
 1% for SAR
 1% for Reports
PCMCIA Memory Allocation example (TELEDYNE)
2.2.4.2. PCMCIA recording file structure
The FDIMU/DMU stored data (ACMS reports, QAR / DAR / SAR raw data files) will
be recorded onto the PCMCIA card in different format and according to specific disk
structure, as described below, depending on the involved equipment:
 For SAGEM FDIMU:
- DAR data will be recorded as RECxxxxx.dat located under "A/C TAIL.REC"

directory
- QAR data will be recorded as RECxxxxx.dat located under "A/C TAIL.QAR"
directory
- Reports data will be recorded as Ryyxxxxx.txt, located under "A/C TAIL.REP > Report
yy" directory
- SAR data will be recorded as SAxxxxxxx.datlocated under "A/C TAIL.SAR > SAR_x"
directory
Note: Digits xxxxx will identify each file individually (file numbering increment), while
digits yy will correspond to the Report number.
[see ANNEX4 for detailed PCMCIA Data Recording format and file structure for
SAGEM FDIMU/DMU’s]
Note that QAR stored data files are using the same format as DAR data files,
whereas the directory name is different. It is therefore recommended to pay attention
to it when transferring the data to AIRBUS or to other QAR or DAR data requester for
quick analysis.
The ACMS reports will therefore directly be stored in .txt readable format, which can
be sent and read by the engine manufacturer or other data users without further
processing.
The other ACMS data (SAR/DAR/QAR) will be recorded in .dat format. These .dat
files cannot be converted in a .txt format for readout. To decode these files, it is
necessary to reprocess them by using adequate GSEs, and to use the associated
input specifications for readout (DAR/QAR data frame specifications or SAR
programmed definitions showing detailed frame mapping and bit encoding
definitions).
 For TELEDYNE FDIMU:
The PCMCIA card will contain a set of files written by the FDIMU used for ACMS
reports / QAR / DAR / SAR data recording and may also include other files for other
purposes (e.g. upload files and mapping files).
Concerning data recording, the PCMCIA will always contain the same data files:
- DAR data will be recorded as dar.dat

- QAR data will be recorded as qar.dat
- Reports data will be recorded as msg.dat
- SAR data will be recorded as sarx.dat (Each SAR file correspond to a SAR
channel)
[see ANNEX5 for detailed PCMCIA Data Recording format and file structure for
TELEDYNE FDIMU’s]
2.2.4.3. Formatting guidelines
We would like to highlight that PCMCIA card must be properly configured

(prepared/formatted) before it is inserted to the FDIMU or DMU and used for ACMS
data recording.
It is moreover recommended to re-format the cards at regular intervals.
SAGEM/TELEDYNE Vendors can be contacted directly for further advices on

recommended cards and characteristics, or tools, compatible with the DMU or
FDIMU equipment when necessary.
SAGEM DMU P/N ED45A300 or FDIMU P/N ED48A100/ED48A200:

[see ANNEX11]
TELEDYNE FDIMU P/N 2234320-01-01 or 2234340-01-01 or 2234340-02-02:
[see ANNEX11]
2.2.4.4. PCMCIA Card capacities
We would like to highlight that it is important to use PCMCIA card with adequate
capacity in order to have efficient recording. The capacity must be chosen in
accordance with the selected recording speed to allow longer recording autonomy
and avoid the need for frequent download.
As an example, given a 44% memory allocated for DAR part, and a recording speed
of 256 wps.
- a 512 MB PCMCIA card could allow to get around 120 Hrs of DAR data recording.
- a 1024 MB PCMCIA card could allow to get around 240 Hrs of DAR data recording.
This number of flight covered will however depend on the programmed trigger
conditions and the way the aircraft is operated.
A speed programming of 128 wps will multiple the above autonomy by a factor 2 and
so forth.
2.2.4.5. PCMCIA data dump
Please refer to paragraph 3.5.2.2.
2.2.5. Recording autonomy and speed considerations
The recording duration depends on several factors such as the selected recording
speed/rates, the media type and the capacity used, the start/stop recording trigger
definitions or other programming selections, as well as on the A/C operations (power
up/off cycles).
CVR and FDR records are managed in a FIFO manner (once full recording autonomy
is reached, oldest data is overwritten).
Note: Operators are hereby advised to quickly proceed to the download of the CVR
& FDR data after any incident/accident event requiring data analysis,
otherwise data may be lost by overwriting.
The activation of GND CTL push-button on ground or a simulated flight within
the scope of some maintenance actions may particularly force FDR & CVR
recording operation and ultimately consume memory capacity until overwriting.
This also applies to other data records (DAR, QAR records).
For CVRS:
The SSCVR has a 2-hour recording duration (formerly 30 minutes) for audio
data and provides at least 2 hour of data link messages as specified by the
applicable regulation.
Note that the datalink recording functionality does not consume as much as
CVR memory space than audio (in practice datalink recording allows to cover
a very large number of flights).
For FDRS:
• FDR 1TU
FDR/SSFDR’s are designed to record the last 25 hours of flight data (as
required by regulation).
• External QAR 3TU

Variable. Function of media type and size used and recording speed
selection.
QAR is used to record QAR data (= FDR data) for longer durations than a
FDR equipment.
• Integrated FDIMU PCMCIA card (= QAR data recording)

Variable. Function of media size used, memory allocation and trigger
definition (GSE programmable), and recording speed selection.
Note: These QAR data can be recorded onto the FDIMU PCMCIA card
alone or in addition to the other possible PCMCIA recorded data
(ACMS SAR/DAR/Reports).
For ACMS:
• Reports and SAR storage on FDIMU/DMU internal memory

Variable. Reports (Snapshot or pre/post data event recording) and/or SAR
(continuous captures) will be recorded in internal non volatile storage
memory of the FDIMU/DMU.
The FDIMU/DMU allows keeping a large but limited amount of reports

stored in memory / managed per individual report and GSE programmable.
 Report storage in FDIMU/DMU memory is typically managed in a FIFO

manner per report type. New generations replace the oldest stored
reports in memory (a limited number of stored reports is defined). This
is also configurable by user (GSE), function of the DMU equipment.
• Reports and SAR data storage on MDDU floppy

Variable. 1.44MB max in capacity.
Reports (Snapshot or pre/post data event recording) and/or SAR
(continuous captures) will be recorded.
• External QAR 2TV (= DAR data recording and others)

Variable. Function of media type and size used, trigger definition (GSE
programmable), and recording speed selection.
 QAR 2TV is mostly used to record DAR data for long durations,
allowing to cover a large number of flights.
Some QAR 2TV can additionally be used to record ACMS Reports (for
some FDIMU’s and DAR’s only fitted with RS422 link) (Variable.
Function of media size used and programming).
• Integrated FDIMU PCMCIA card (= DAR / SAR data recording, Reports)

Variable. Function of media size used, type of recorded data, memory
allocation and trigger definitions (GSE programmable), as well as recording
speed selections.
Note: These Reports, DAR and SAR data can be recorded onto the
FDIMU PCMCIA card individually or all together, or in addition to
the QAR data.
2.2.6. Start/stop recording logic considerations
The FDR, CVR, DMU and QAR equipment rely on different trigger logics for
recording, controlled by different parameters, and operation supplied by different
power-supply sources, which can lead to different recording behaviors (recording
periods and durations) depending on the event occurrence and A/C operation (power
up/off cycles).
The recordings will therefore not necessarily start/stop at the same time and upon the
same conditions upon normal/abnormal event, depending on the type of event
occurrence experienced.
Start/stop logic for the FDR (1TU):

The FDR recording is controlled by the start & stop power-supply relay logic based
on several inputs including direct engine control and Flight/Ground information
(power-supply interlock logic).
The start & stop recording logic of the FDR, under normal operating conditions,
can be briefly summarized as follows:
The FDR is automatically recording (provided it is supplied with electrical power

115VAC on its busbar), when the aircraft is in one of the configurations given
below:
- In flight with engines running or stopped,
- On the ground with at least one engine running,
- On the ground during the first five minutes following power-up of the aircraft
electrical network,
- On the ground up to five minutes after last engine shutdown.
A means is also provided to the crew (RCDR/GND CTL switch), allowing to

activate the recording on command by supplying the FDR recorder with power at
any time while the aircraft is on the ground, all engines stopped (provided A/C is
powered by APU or external power).
On A320 Family aircraft, the engine control signal used for the start/stop logic is
available through relays 12KS1 & 12KS2 which are commanded by EIU1 and
EIU2 (respectively OIL LOW PRESS & GND Eng 1 and OIL LOW PRESS & GND
Eng 2). A ground signal is transmitted to Relay 12TU and 10RK via 12KS2 and
12KS1(in serial) when both engines are off.
Note that the FDR/QAR automatic start/stop recording logic is based on OIL LOW
PRESS & GND signal received from EIUs (e.g. 60 PSI on A320 family with IAE
engines; 13 PSI on A320 family with CFM engines) and the recording will
therefore in effect only start after a % threshold of N1 & N2 (~15 % of N1, ~40% of
N2) is reached at first engine start.
If the GND CTL is normally switched ON (per normal pre-flight procedure and kept
ON until engine start), the complete engine 1 & 2 start sequence will be recorded.
On A330/A340 Family aircraft, same logic principal is used. Nevertheless, the

engine control signal used for the start/stop logic is available through Engine
Master lever signals (e.g. Eng Master1 2KC1, Eng Master2 2KC2,.. through
aircraft Master Switch relays 3QG1, 3QG2..).
The FDR will record for five minutes after last engine shutdown provided it is
supplied with electrical power 115VAC on its busbar (i.e. A/C typically powered by
APU or external power).
The AMM, ASM and AWM Technical documentations can be referred for
architecture descriptions.
Start/stop logic for the CVR (1RK or 2RK):
Same as FDR with some slight deviations.

The CVR recording is controlled by the same start & stop power-supply relay logic
based on several inputs as the FDR logic (CVR and FDR sharing similar relay
logic circuitry).
However it is to be noted that:
o Power sources are different (different busbars involved)
o New regulation (*) introduced several changes in CVR start/stop logic
design, including 28 VDC as new permanent power supply for CVR
system operation (instead of 115 VAC) and increased segregation
requirements on some newly delivered aircraft.
(*) FAR Amendments 25-124 and 121-338 – Revisions to Cockpit Voice Recorder
and Flight Data Recorder regulations.
The following picture gives an overview of the CVR & FDR recording logics
(recording phases) in use on today A320 & A330 /A340 Family aircraft:
CVR & DFDR Recording phases
Start/stop logic for the external QAR in 3TU (QAR data):
Same as FDR logic. The external QAR will start and stop to record at same time
interval than FDR equipment (relying on same power supply relay logic circuitry).
Start/stop logic for the external DAR in 2TV (DAR data):
The start/stop recording is programmable. A standard trigger is available in the

basic configuration, controlled by the FDIMU/DMU equipment.
The QAR is typically set to record by default from flight phase PH1.1 (= ACMS*
PH1.1 i.e. ENGINE STARTS) and to stop at the end of PH 10 (ENGINE
SHUTDOWN) when the DMU sees PH 1. It is entirely controlled by the
FDIMU/DMU (pre-programmed trigger). The trigger can moreover be customized
(via the GSE or manually controlled).
(*) ACMS flight phase computed by the FDIMU/DMU (based on FWC flight phase).
Start/stop logic for the PCMCIA QAR data (FDIMU PCMCIA card):
The start/stop recording is programmable. Note that QAR data recording on

FDIMU PCMCIA card is not systematic (normally deactivated by default). This
however depends on the P/N of FDIMU and software loaded (ACMS setup
database).
Start/stop logic for the PCMCIA DAR data (DMU or FDIMU PCMCIA card):
Same as external QAR 2TV equipment. The start/stop recording is programmable

and controlled by the FDIMU/DMU equipment. It is to be noted that DAR data
recording on FDIMU PCMCIA card is also not systematic (normally activated by
default). This however depends on the P/N of FDIMU/DMU and software loaded
(ACMS setup database).
2.2.7. FDIU / DMU / FDIMU Software loading
considerations
Several alternatives can be chosen for the loading of the FDIU and DMU software
components (FDIU system software, ACMS system software & setup database)
depending on the A/C configuration and the P/N of equipment at stake:
- Software loading via data loader PDL/MDDU cockpit interface (floppy disk)
- Software loading via FDIMU/DMU PCMCIA card interface
Note that some FDIU’s are loadable through Portable Data loader (PDL) only, or
some A/C may not be equipped with the necessary MDDU connections & suitable
DLRB database for FDIU software loading (MDDU – FDIMU[FDIU] link).
The PCMCIA card of the FDIMU’s and DMU’s can be used for the uploading of the
ACMS S/W applications only.
The following maintenance procedures apply and can be further referred for any software
loading purpose:
A320 family:
AMM TASK 31-36-00-710-004 – AIDS S/W load procedure (SAGEM DMU).
AMM TASK 31-36-00-710-008 – AIDS Software Load Procedure through the
PCMCIA-Card.
AMM TASK 31-36-00-710-013 – FDIMU (10TV) AIDS Software Load Procedure.
AMM TASK 31-33-00-710-013 – FDIMU (10TV) DFDRS Software Load
Procedure.
A330/A340 family:
AMM TASK 31-36-00-710-805 – DMU (1TV) ACMS Software Load Procedure.
AMM TASK 31-36-00-710-814 – DMU Software Load Procedure via PCMCIA-
Card.
AMM TASK 31-33-00-710-811-A – FDIU Software Load Procedure.
AMM TASK 31-36-00-710-809 – FDIMU (10TV) Software Load Procedure.
AMM TASK 31-33-00-710-809-A – FDIMU DFDRS Software Load Procedure.
AMM TASK 31-33-00-710-809-A-01 – FDIMU DFDRS Software Load Procedure
with PDL.
For further information on compatible PDL’s and approved adapter cables when needed, SIL
45-004 (Portable Data Loader selection) can be consulted or Equipment vendors should be
contacted otherwise.
AIRBUS Technical Documentation & GSE/Tools offices or Customer Services Engineering
office also remain at operator’s disposal for any assistance in this regard.
2.3. ACMS Main functions
2.3.1. Generality
The FDIMU or DMU equipment with its software components provide users with
several recording capabilities and means for efficient condition & performance
monitoring of the aircraft systems.
The ACMS provides the following main generic functions:
 ACMS reports processing

– Concise set of parameters collected and recorded according to specific
trigger conditions
– Synthetic format adapted to cockpit Printer, dump and downlink devices
– Two report types : AIRBUS Standard Reports / Airline Programmable
Reports
 Purpose : to provide operators with relevant data in convenient form

to support Condition & Performance system analysis
 Real-time data monitoring

– Real-time display of aircraft parameters in the cockpit
– Easy access to aircraft data, complementary to maintenance
 Purpose: to access to aircraft data for quick Maintenance support

actions & T/S investigations
 Raw data recording (SAR, DAR)

– Continuous or event controlled recording of incoming A/C parameters in
different format
– Airline customizable (SAR channels / DAR frame / recording rates / trigger
logics / other options..)
 Purpose: to support in-depth problem analysis, FOQA program

development,
 Parameter broadcast
– Broadcast of avionics parameter (ARINC 429 labels sent to
ACARS/ATSU for onboard or on ground usage)
The ACMS data is made available in various formats to meet various purposes,
depending on the aircraft configuration. The typical formats per data type are:
• Report layout
- Paper form (Printout)
- Electronic exportable format (MDDU and PCMCIA files, ACARS ASCII
format)
• Raw data format

- SAR file
- DAR file
- QAR file
• Parameters
- MCDU display
- Paper form (Printed via MCDU)
2.3.2. ACMS Reports
The ACMS provides a set of predefined standard reports, specified by AIRBUS (as
part of the standard ACMS software installation), as well as the capability to create
some new reports (User programmable reports) according to operator’s needs and
preferences:
 AIRBUS Standard Reports

- Report content (collected parameters), layout and trigger logics defined
by AIRBUS
- Triggering according to pre-defined automatic trigger conditions or
manual operations
- Provide basic Engine, APU, Structure and Aircraft Systems monitoring.
- Limited customization capability (e.g. limit values modification, inhibition
and output rules settings), via MCDU or via GSE (ACMS Ground
Programming Tool)
- Mostly same reports for all A320 Family / A340-A330 Family operators
but adapted to A/C models & engine types.
 User Programmable Reports

- Report content, layout, output rules and triggering logics programmable
by user
- Programming through the dedicated ACMS GSE tool
2.3.2.1. Report characteristics
The main Report characteristics are:
• Report content
- Set of snapshot or averaged parameters allowing to assess Engine /
APU / Structure / Aircraft Systems condition in a simple and efficient
way (based on ACU mnemonics)
- AIRBUS Standard reports vs User programmable reports
- Report description available in AMM chapter 31-37
- For each DMU/FDIMU aircraft configuration, exhaustive list of reports is
available in AMM chapter 31-37
• Routine vs On-event reports

- Periodical routine reports (generated upon typical normal conditions)
- On-event reports (generated upon abnormal conditions/exceedance
monitoring)
• Automatic vs Manual report generation

- Automatic generation: according to pre-defined logics
- Manual generation: Remote Print Button (RPB) / MCDU request for
report generation / ACARS uplink request for Report generation
- A/L programmable trigger logics (code 3xxx)
• Output rules
- Immediate / End-of-Flight (EOF) output
- Storage only / Printer output / MDDU floppy disk output / ACARS
output / PCMCIA card storage or even external DAR if RS422 with
some conditions
- A/L programmable
• Inhibition rules
- Enable / Disable report generations (general or individual inhibitions)
- Inhibit output for Printing / ACARS routing (general or individual
inhibitions)
Complete Report descriptions (all individual standard ACMS reports provided

by AIRBUS at delivery as part of the standard ACMS configuration) are
accessible from AMM chapter 31-37:
- detailed report layout with associated parameter definitions (ACU, display
format, units..)
- detailed trigger conditions (trigger logic codes, with user programmable
limits/constants,..)
Note that the given report definitions depend on the actual aircraft
configuration, aligned on IPC data.
ACMS Report description example as per AMM chapter 31-37
Once generated, the reports are stored in the FDIMU/DMU unit for distribution to one
or several peripheral devices.
Possible Outputs:
- ACARS downlink
- cockpit printer
- integrated FDIMU/DMU PCMCIA card (if available and properly configured)
- MDDU floppy disk (if installed)
- an external optional DAR 2TV media (if RS422 link with capable FDIMU and
DAR)
The table in ANNEX8 is a brief overview of the provided AIRBUS standard reports
per aircraft program & engine type:
(routine and Exceedance/on-event reports used for A/C performance monitoring,
Engine Trend monitoring, Airframe structure monitoring, Environmental Control
System / Doors / APU monitoring, other T/S and monitoring purposes).
[see ANNEX8 for the list of reports available for A320/A340/A330 FDIMU/DMU’s]
2.3.2.2. Generic recommendations
Operators may sometimes notice that some standard ACMS reports are not always
available (not generated, or not transmitted to a particular output device) for some
unobvious reasons.
The objective of this following chapter is to provide brief recommendations on how to

possibly explain this unavailability and to return to a normal situation if necessary:
General information:
Several factors could actually explain the unavailability of a report or a set of reports
during a particular flight:
 The report triggering conditions may not be fully met during the corresponding flights,
 Some particular FDIMU/DMU settings (report inhibition settings, report constant/limit

values, report output rules) may be used resulting in the report not being available or
not frequently available (i.e. not generated or not output to the desired peripheral
device [ACARS, PRINTER], or some constant/limit values or inhibit/output rules may
have been temporarily changed)
 The report may not be available due to a ground network congestion, an ACARS
system failure or an issue linked to the ground readout tools (outdated version,
misconfiguring).
Note that all the ACMS reports are not necessarily generated and transmitted during
a normal flight.
Indeed, some reports are routine reports (e.g. Report <01>, R<02>, R<04>,.. ) and
will be generated upon normal conditions at quite regular predefined intervals,
whereas some other reports (e.g. R<06>,R<07>,R<14>,...) are on-event reports,
triggered upon some limit exceedances or when other abnormal conditions are
detected.
Some particular reports may also combine routine or on-event trigger logics
depending on the considered trigger code.
Provided the predefined trigger conditions are fully met and during a certain
monitoring period (i.e. after a flight or some flights are performed), some ACMS
reports will therefore be automatically generated, stored into the FDIMU/DMU and
transmitted to the expected devices (according to the selected output rules when
appropriate).
It is to be noted that, under normal operation:
- The reports must generate as expected, according to their defined trigger conditions
and settings used (default setting, or any programmed settings).
- All reports, once generated, will be automatically stored in FDIMU/DMU internal

memory (according to the report storage configuration)
It is reminded that the ACMS report generation highly depends on the setting used
(programmable reports limits, inhibition rules, output rules) for each individual report
and trigger code, which is moreover customizable by the user (through ground GSE
tool or directly, but to a lesser extent, onboard the A/C via the dedicated MCDU
ACMS programming menu).
Troubleshooting guidelines:
In the event of a suspected anomaly where reports would be missing and before
contacting AIRBUS to better isolate the source of the matter, it is therefore
recommended to perform in a first step the following standard verifications:
 to check/confirm if the Reports have been well generated or not for the
concerned flights (i.e. stored in the FDIMU/DMU memory) or just not output to
the selected device (ACARS, Printer):
 for this purpose, it is advised to look at the ACMS STORED REPORT menu from
MCDU ACMS main menu and check for generated reports. The generated report
should appear in the list of stored reports together with a status on its output (printed,
transmitted to ACARS or in progress).
 to check inhibition settings & output rules, or the constant/limit values used
controlling Report generation and reconfigure it when necessary:
 the output rules and inhibition settings used (report output rules not selected for
ACARS transmission / printing, or report inhibited for generation/ACARS
downlink/printing…)
 the report limits/constants used controlling the report generation (which may be set
in a way that reports are not generated/stored at all, or not frequently enough, and
consequently not transmitted to the selected output device),
Note: For instance, the Engine Take-Off Report <04> is generated every
“F04” Take-Off where F04 is a programmable parameter. By default,
this parameter can be set at a particular value (e.g. F04=5), meaning
that the Take-Off Report <04> is set to generate every 5 flights only and
will be stored in memory accordingly.
This also applies for other reports, particularly Cruise and Performance
reports whose trigger generation logic is based on ‘flight legs’ (Y01.1,
Y02.1 programmable constants) or flight hours.
Therefore, the limit/constant values might be set in a way that the
reports are not generated and stored frequently in the FDIMU/DMU
memory.
 the triggering conditions were not met preventing the report from generating (e.g.
due to a conditional limit setting used or possible source failure), and consequently
not transmitted by ACARS or printed,
Note: For instance, in the event of no limit exceedance detected for report
<06> or <07>, or the appropriate stability criterion was not met to
enable generation of a stable cruise report <01>.
 some limit values, or inhibit rules, or output rules may have been temporarily
modified through MCDU (manual change) or GSE (new database), and therefore
alter report generation or transmission to ACARS or printing for a while.
Note: Reconfiguration can be done manually through the MCDU ACMS menu
or from GSE database programming.
The reconfiguration capabilities from MCDU depend on the type of
FDIMU/DMU equipment and software part number used.
Some latest ACMS software versions provide capability to modify
inhibition and output rules manually from MCDU for each report and
trigger code individually (e.g. ACMS AIRLINE FUNCTION menu for
TELEDYNE FDIMU’s).
 Last but not least, in case the reports are found stored in FDIMU/DMU memory but not
transmitted by ACARS despite proper configuring, the issue could be related to:
- an ATSU/ACARS system failure or occupancy matter

(possibly congested and not able to transmit the received data),
or
- a ground network failure, congestion of the network or any routing issue along the
communication line
(FDIMU/DMU  ATSU/ACARS  Ground segment / ARINC / SITA network Operator
facility).
or
- the configuration or version of the readout tool used for report acquisition and
display
(e.g. AIRMAN or other tools/applications).
In such a case, it is usually recommended:
 to check Post Flight Report (PFR) for any reported ATSU/ACARS MU failure,
 to check the ACARS raw data flow & ground traces (if reports are properly routed
on the ground, before being received and further computed by ground readout tool),
 to check Ground Readout tools if properly configured or up-to-date to receive

and display the incoming ACMS report(s).
Note: Note that a quick comparison between the ACARS report received in
raw data format and the report displayed by the Ground Readout tool is
sometimes enough to identify an anomaly and to better isolate the
origin of the issue.
2.3.3. ACMS Real Time monitoring

2.3.3.1. Parameter Call-up Functions
Alpha Call-up
- Parameter value is displayed in engineering unit (Deg, Ft, Kt, Lbs, etc.)
- Sets of alpha call ups can be stored for later recall or sent in real time to
the printer
- Ability to display in real time via the MCDU, any digital data on the
aircraft that is available to the FDIMU/DMU.
(All ARINC 429 parameters from computers connected to ACMS can be
read)
- Outputs: MCDU display, printer
Label Call-up
- Parameter value is displayed in binary form  ACMS = ARINC429
reader
- Sets of label call ups can be stored for later recall or to be sent in real
time to the printer
- EQ.SYS.LAB.SDI data entry concept
- SSM readout
- Outputs: MCDU display, printer
MCDU menu examples for Parameter
callup
(e.g. A330/A340 Teledyne FDIMU)
Alpha Call-up list and EQ codes:
- The Alpha Call-up list is accessible under AMM 31-36 or 31-37

- The EQ codes list is accessible under AMM 31-36 or 31-37
(A/C Input Parameter lists [AIPL] – ref. Paragraph 3.5.2.6 – can also be used
conjointly to help readout)
It is recommended to use the ACMS parameter callup functions intensively as being an

efficient means for system T/S. The following AMM tasks can be consulted for this
purpose:
A320 family:
AMM TASK 31-36-00-740-008 – Access to the Parameter Call-Up menus.
A330/A340 family:
AMM TASK 31-36-00-740-805 – Access to the Parameter call-up menus.
2.3.3.2. Other MCDU functions
Function of the FDIMU or DMU hardware and software, the user can access to some
DMU generic functions for consultation or action from cockpit Multipurpose Control
Display Unit (MCDU), such as for instance:
• Reprogramming of some ACMS functions

- Report Inhibit / Reset / Limits or Constants modification
- Report output rules modification (to printer, to ACARS, ...)
- Statistic counters modification
• Status of various reports and recordings

- Stored reports consultation and output (to printer / ACARS / PCMCIA /
...)
- Stored SAR data consultation
- DAR data frame monitoring
• Manual triggering of reports and recordings

- Manual request for Report generation
- Manual request for SAR recording
- Manual request for DAR recording
• ACMS P/N consultation
• Control of the DAR/SAR recordings
• PCMCIA control functions (disk content status)

2.3.4. ACMS SAR / DAR and QAR Data Recording
2.3.4.1. SAR recording function
• Continuous recording of incoming A/C raw data between a programmable

start/stop event
• High capacity storage.
• A/L Programmable.
• Recorded onto the internal FDIMU/DMU memory.
Possible Outputs:
- integrated FDIMU/DMU PCMCIA card (if properly configured)
- MDDU floppy disk
 Suitable for specific event recording well localized in time, parts of

the flight
Once generated, SAR files are stored in FDIMU/DMU unit for further distribution to
either a data loader device (MDDU/PDL) or integrated PCMCIA disk
SAR main features:
2.3.4.2. DAR recording function
• Continuous recording of incoming A/C raw data.

• A/L Programmable
• Customizable data frame (GSE programmable)
Possible Outputs:
- an external optional QAR 2TV media
- integrated FDIMU/DMU PCMCIA card (if properly configured)
 Suitable for long lasting recording in order to capture complete /

several flights
DAR main features:
• DAR default recording typically set from PH1.1 [engine start] until end of PH10
[engine off + 5 minutes] (GSE reprogrammable).
• Data frame definition can be exported from FDIMU/DMU GSE (e.g. AGSIV,
ADRT tools,..) or obtained from AIRBUS when needed.
2.3.4.3. QAR recording function
• Continuous recording of A/C raw data.

• Fixed data frame = copy of FDR data frame
Possible Outputs:
- an external optional QAR 3TU media
- integrated FDIMU PCMCIA card (if properly configured) [for full FDIMU
configurations only]
 Suitable for quick and easy FDR data retrieval
2.4. ACMS – Programming capabilities
2.4.1. FDIMU/DMU Ground Programming tool (GSE)
The FDIMU or DMU Ground Support Equipment (GSE) allows reprogramming of the
ACMS functions.
GSE TELEDYNE: AGS IV (Application Generation Station)

GSE SAGEM: SAGEM GSE
GSE HONEYWELL:ADRT (ACMS DMU Reconfiguration Tool)
The above 3 ground-based GSE’s provide the user (ACMS application developers)
with various functionalities and user-friendly interface to customize the ACMS
databases to support the various recording & monitoring needs (enhanced data
programming for Maintenance/Engineering/Flight operations purposes: e.g. FOQA
programs accomplishment, Flight Safety purposes...).
GSE tools are PC-based application, which can be installed on standard PC

computers (Windows running, with minimum requirements). The capabilities vary
from one GSE vendor to another.
[see ANNEX7 for vendor GSE examples]
The GSE particularly allows programming various functions such as:
 ACMS report functions

(e.g. content, trigger conditions, report layout, limits and outputs rules..),
 SAR recording functions

(SAR channel definitions, start/stop logics),
 DAR recording functions
(data frame and sub-frame definitions, and mapping, start/stop logics),
 QAR recording function

(PCMCIA trigger,...) (FDIMU only),
 PCMCIA recording functions,
 Alpha Call-Up definitions,
among other possibilities (creation of MCDU screens, etc.)
Once the programming is done, a newly customized database is generated and a

new set of upload files are created by the tool, to be then uploaded onboard the A/C
into the FDIMU or DMU unit (upload Floppy or PCMCIA files containing database
configuration data).
The GSE tools extend the programming capabilities of the FDIMU’s or DMU’s already
available at MCDU level (MCDU programming possibilities are very limited, - MCDU
“DMU PROGRAMING” menu – allowing to reprogram manually a few DMU functions
from cockpit, mainly to change report limits/ report counters/statistics
counters/inhibition settings among other possibilities depending on the H/W and S/W
used).
Note that the oldest DMU’s (HAMILTON/TELEDYNE DMU’s P/N 7950x0-xx-xxx

models / Nord Micro 903116243Bxxxxx models) are almost exclusively
programmable from MDCU menu. Some specific DMU’s (DMU’s using 2 CPU’s only)
can be GSE programmable (CPU2 part only). For any further information on the GSE
CPU2 programming capabilities, TELEDYNE can be contacted.
2.4.2. Programmable functions:
 ACMS Report programming:
 inhibition of the reports
 output rule destinations
 modifications of the limits or constants
 create a free programmable report
 define customized logics for the triggering of the report
 SAR / DAR / QAR Recording programming:
 Data frame creation
 Start/stop logics
 Pre-event time recording

 Other options
 Parameter programming:
 create new parameters
 create new Alpha call-ups
2.4.3. Programming interfaces
ACMS functions can be programmed throughout three main interfaces:
• Onboard MCDU
• ACARS uplink
• On ground GSE
Note: Oldest DMU’s (HAMILTON/TELEDYNE DMU’s P/N 7950x0-xx-xxx model /

Nord Micro 903116243Bxxxxx models) are mostly programmable from MCDU
menu (no GSE, nor by ACARS). [refer to paragraph 3.4.1].
ACMS MCDU/ACARS/GSE programming capabilities

2.4.3.1. On-board MCDU programming
- limited capabilities (mainly report limits & report counters, statistic

counters, inhibition rules,) and limited in time (temporary change)
- newly added Airline functions (depending on S/W versions- TELEDYNE
FDIMU’s only)
The following AMM tasks can be referred to get access to the FDIMU/DMU
programming menus :
A320 family:
AMM TASK 31-36-00-740-009 – DMU Programming Procedures (DMU SAGEM).
AMM TASK 31-36-00-740-016 – FDIMU Programming Procedures.
A330/A340 family:
AMM TASK 31-36-00-740-815 – ACMS Special Function/Reprogramming
Procedures.
2.4.3.2. ACARS uplink programming

- limited capabilities (e.g. Temporary change of limits/constants, Change
of APU / Engine Hours and cycles)
2.4.3.3. On-ground GSE programming

- in-depth programming of DMU functions
- flexible/user-friendly tool allowing to configure standard DMU functions +
user-programmable capabilities for enhanced monitoring according to
user requirements
- a new ACMS database and upload files are created (to be uploaded into
the FDIMU/DMU)
Main GSE programming features:
2.5. ACMS / FDRS / CVRS – Data downloading and readout
Downloading and readout of the recorded aircraft flight data is required on a quite
regular basis or occasionally, as part of a particular scheduled or non-schedule
maintenance action, or for other analysis purposes.
• To meet specific regulation requirements
• To support investigations
• To meet specific flight data monitoring requirements (e.g. FDM/FOM, FOQA,
T/S campaign)
• Others
ACMS and FDRS raw data readout process overview
Main inputs for readout & support analysis:

- Recorded data (Reports / SAR data / DAR data / QAR/FDR data extracted
from the A/C)
- ACMS Input parameter lists (for detailed description of A/C parameter
definitions)
- FDRPL export / Technical Notes (= FDR data frame specifications)
- Other documents (DAR frame specification, A/C systems I/O definitions)
Several equipment/tools exist on the market which can be used for downloading and
readout of the FDR or QAR, CVR or ACMS data (Reports / SAR / DAR data).
Prior to any decoding activities, raw data must be retrieved from the aircraft (Refer to
SIL 00-086). The retrieved data is then processed thanks to specific Ground
tools/Working stations.
• FDIMU/DMU/FDR vendor tools:

(e.g. TELEDYNE AGSIV/TDRS, HONEYWELL ADRT/READOUT/ADRAS,
SAGEM GSE/AGS, L-3 COMMUNICATIONS ROSE/ROC)
• Engine report & data exploitation tools from Engine Manufacturers /

AIRBUS:
(e.g. SAGE, ADEPT, EHM from Engine Manufacturers, APM from AIRBUS
allowing to monitor engine performances over the time and detect abnormal
variations or degradation)
• others (AIRMAN, AirFASE, FLIDRAS, INSIGHT analysis,…)

 allows the operator to view the reports, SAR, DAR or QAR/FDR data
recordings in tabular or graphical format, translate the collected data
into meaningful information or export it for use in other ground based
tools
ACMS and FDRS data retrieval means and ground processing
2.5.1. FDRS (FDR / QAR data) downloading and readout
2.5.1.1. FDR/QAR data downloading:
FDR data can be retrieved either:
1) from the FDR recorder (FIN 1TU located in the tail of the A/C),
2) or from the external QAR LRU recorder (if this latter is installed on A/C in FIN 3TU
position)
3) or also from FDIMU PCMCIA card (if the aircraft is equipped with a FDIMU/PCMCIA
card interface used and configured for QAR data recording)
Note: The options 2) and 3) correspond to the downloading of QAR data = copy of
the FDR data.
It is however to be noted that, in case of option 3) with QAR PCMCIA
recording, the QAR trigger can be customized and recording timings and
durations may therefore differ from FDR ones.
Option 2) allows easing access to the FDR data (directly from the avionics
bays) with typically higher recording autonomy than FDR equipment, function
of QAR model and media used).
 To download FDR raw data from FDR 1TU:

Operators can refer to:
A320 family:
AMM TASK 31-33-00-710-009 – Readout Procedure of the Digital Flight Data
Recorder.
A330/A340 family:
AMM TASK 31-33-00-710-807-A – Readout Procedure of the Digital Flight
Data Recorder.
A portable interface (PDL= Portable Data Loader *) shall be connected to the

FDR (front face connector while the recorder is still installed on the A/C) in
order to download the FDR raw data. These PDLs are dependent on the P/N
of FDR installed, provided by FDR manufacturers.
(*) also called HHDLU (Hand Held Download Unit) for HONEYWELL FDR
equipment or PI (Portable interface) for L-3 COMMUNICATIONS FDR
equipment. Other PDLs from other vendors can likely be used.
Nevertheless, we would recommend to use PDL approved by vendors to
ensure full compatibility and avoid any unexpected issue.
Another alternative consists in removing FDR from the A/C and sent it to an
authorized Maintenance/Repair/Readout station, equipped with proper
equipment/stations for data downloading and subsequent readout if
necessary.
For further information on compatible PDL’s and approved adapter cables

when needed, SIL 45-004 (Portable Data Loader selection) can be consulted
or Equipment vendors should be contacted otherwise.
AIRBUS Technical Documentation & GSE/Tools offices or Customer Services

Engineering office also remain at operator’s disposal for any assistance in this
regard.
 To download QAR raw data (= FDR data):
The QAR 3TU storage media or integrated FDIMU PCMCIA card media shall
simply be removed from the unit (from QAR LRU or FDIMU LRU).
2.5.1.2. FDR/QAR data readout:
Once downloaded from the A/C, the FDR data (or QAR data) must be then
processed through specific ground readout tools, which must be set according to the
FDR data frame (FDRPL specification).
 FDR data frame specification (FDRPL):
[see ANNEX2 for brief FDRPL description]
The FDRPL is an AIRBUS application. The FDRPL specification must be used as

an input to the ground readout tools used for decoding, which will allow the user
to convert the raw data back into the original engineering values.
The FDRPL is the main application allowing to access to the FDR data frame
definition corresponding to the precise A/C recording configuration.
FDRPL contains a detailed description of the FDR recorded parameters

(including which source equipment is used for recording, with primary and
backup sources, input label definitions for each individual recorded parameters)
and the data frame mapping information required for readout (FDR words
assignments).
Flight Data Recorder Parameter Library (FDRPL) features

Note1: QAR data being the exact copy of FDR data, the FDRPL can therefore
also be used for QAR data decoding.
To access to the applicable FDR/QAR data frame information through FDRPL,
some entries are required (the user shall in particular select Aircraft model,
Engine type, LRU information – i.e. FDIU S/W and H/W part numbers -, and
recording speed information – i.e. 64 / 128 / 256 / 1024 wps – matching the
aircraft configuration). The data can also be exported in Excel format. Refer to
AIRBUS FDRPL user guide.
Note2: For your information, FDRPL is not available onto AIRBUS World
portal, the FDRPL is a CD Rom which is given to the customer at Aircraft
delivery, along with other A/C Technical documentation. In case any copy is
necessary, AIRBUS Tech pub Office can be contacted.
In case of any issues to retrieve a particular data frame, AIRBUS Customer
Services Engineering Office can still be contacted.
Note3: The FDR/DAR/QAR raw data, once downloaded, is normally readable

by standard flight data ground readout tools, without any reprocessing (as
originally based on ARINC standards and recorded in binary format).
Some specific files may however not be directly readable and need
reprocessing of the recorded data before readout for some equipment
(decompression or small conversion of the data) (e.g. file .fld extension). The
conversion tools are normally supplied by FDR/QAR/DAR vendors or directly
supported by the ground readout tools.
Tape cartridge media (file retrieved from Magnetic tape recorders) may
moreover require deeper processing or the use of specific tools for decoding.
 In case of any Flight data decoding and analysis required to be

performed by AIRBUS within the scope of an accident/incident or
for Trouble-shooting purposes, please refer to ISI 31.30.00002.
(ISI 31.30.00002 reminds the required raw data format compatible
with AIRBUS tools for readout and the procedure to follow for the
transfer of the data to AIRBUS facilities)
 FDR/QAR readout tools:
Several ground readout tools exist on the market for FDR/QAR raw data
decoding but, like PDLs, not managed by AIRBUS (at the discretion of
operators).
These ground readout tools are more or less sophisticated, depending on the
vendor, according to the intended needs and targeted users (for accident/incident
investigations or Flight Safety purposes, Maintenance/engineering/flight data &
operations monitoring purposes: e.g. FOM, FDM, FOQA programs…).
Among the possible tools (hardware and software applications) marketed by

various vendors are (non-exhaustive list):
- ADRAS (HONEYWELL)
- ROSE (Read Out Support Equipment) / ROC computer stations from L-3
COMMUNICATIONS vendor,
- AGS (Analysis Ground Station) from SAGEM vendor,
- AirFASE (AIRBUS & TELEDYNE controls joint product),
- INSIGHT analysis.
- others
We would then recommend operators to refer to the respective vendors and/or

commercial Handbooks for further information on these various products.
The tools will have then to take into account FDRPL inputs as an entry and the
capability to process FDR raw data files as well as QAR data files.
Operators can also choose to rely/outsource their FDR decoding & analysis to
specific companies/vendors (e.g. HONEYWELL, L-3 COMMUNICATIONS),
specialized and experienced in this domain, or purchase the tools/applications if
preferred.
Note: For further information on AirFASE product and scope of use, AIRBUS
AirFASE team can be contacted.
2.5.2. ACMS (DMU report / DAR / SAR data) download

and readout
The ACMS data can typically be accessed & retrieved through one (or several) of the
following peripheral devices at operator’s convenience:
 MCDU device
(Alpha call up / Label call up consultation, other Report/DAR/SAR functions
monitoring)
 Cockpit Printer
(reports printout, MCDU pages printout)
 ACARS
(reports downlink)
 MDDU Data loader /Floppy disk when installed

(Reports, SAR data dump)
 FDIMU PCMCIA card

(reports, SAR, DAR, QAR data downloading)
 External recorders (DAR 2TV) when installed

(DAR data downloading,..)
 CMC or CFDIU Maintenance Computers

(LRU identification/System configuration data, BITE test & status reports)
The available outputs are function of the A/C configuration, the FDIMU or DMU
hardware installed and loaded software version.
These communication means for data consultation and transmission are moreover
programmable (though MCDU or GSE).
2.5.2.1. FDIMU / DMU PCMCIA data dump
The PCMCIA card must simply be removed from its DMU or FDIMU slot, as per
below maintenance procedures:
A320 family:
AMM TASK 31-36-00-710-016 – Downloading Procedure of FDIMU/DMU Data on a
PCMCIA Card.
AMM TASK 31-36-00-000-001 – Removal of the Personal Computer Memory Card
(PCMCIA).
A330/A340 family:
AMM TASK 31-36-00-000-802 – Removal of the Personal Computer Memory Card
(PCMCIA) of the FDIMU.
2.5.2.2. MDDU data dump
The ACMS provides the capability to download the following ACMS data from
Multipurpose Disk Drive Unit (MDDU) device (A/C equipped with a MDDU device
connected to the FDIMU / DMU):
- ACMS reports
- SAR data
• Reports and SAR data are recorded on the internal non volatile storage
memory (SSMM) of the FDIMU/DMU
• The data can be retrieved through floppy disks inserted on the MDDU
• The data can be either downloaded manually or automatically:
 Through a manual dump
 Through an automatic dump

The following pictures briefly describe the relevant procedure for manual / automatic
MDDU data dump:
The below AMM tasks can also be consulted for this purpose:
A320 family:
AMM TASK 31-36-00-710-010 – Dump Procedure to Download DMU Data (SAGEM
DMU).
AMM TASK 31-36-00-710-014 – Dump Procedure to Download FDIMU Data.
A330/A340 family:
AMM TASK 31-36-00-710-806 – Automatic/Manual Dump Procedure to download ACMS Data
from the DMU (1TV).
AMM TASK 31-36-00-710-811 – Automatic/Manual Dump Procedure to download ACMS Data
from the FDIMU (10TV)
Automatic data dump:
(DLS or Rotary Switch*)
(*) A/C equipped with Data Loading Selector (DLS) or with Rotary Switch otherwise.
Manual data dump:
(DLS or Rotary Switch*)
(*) A/C equipped with Data Loading Selector (DLS) or with Rotary Switch otherwise.
2.5.2.3. Remote Print Button
The remote print button (RPB) activation, located on the cockpit pedestal, is used to
trigger the generation and printing of a set of standard ACMS reports (flight phase
dependent).
The type of report that will print depends on which flight phase the aircraft is located
when RPB is activated.
The RPB report assignment depends on the FDIMU/DMU (H/W & S/W) equipment
installed, set according to the programmed database. It can therefore vary from one
aircraft to another.
A specific assignment is predefined by default (typically linked by default to some
standard reports such as R<05>, R<10>, R<11> or R<14>…) but can be
reprogrammed by user if needed (via GSE tool, or via MCDU for some
FDIMU/DMU’s).
As an example on some A320 Family aircraft, RPB generation is enabled by default

for :
- Report <05>, that will trigger and print while in phase 4, 5, 5.1, 6, 7.1, 7, 8,
9, and 10,
- Report <10>, that will trigger and print while in phase 1.1,
- Report <11>, that will trigger and print while in phase 2 and 3,
The information about which report is generated upon manual trigger by the RPB, in
which Flight phase, is actually defined in the report logic description part of each
individual report.
(see AMM 31-37-xx Trigger logic part – code 2000).
 Trigger code 2000 corresponds to a manual report generation where the report is triggered by
means of the RPB
 The column “Std value” is used to indicate the triggering Flight Phase, otherwise “not” or
“n.pro.”
(not programmed) is indicated.
As an example, for Report <11>, the following Flight phases 2 & 3 have been
assigned by default:
2.5.2.4. ACARS output
The ACMS System, through the FDIMU/DMU and its loaded ACMS software
(standard or customized version) provides a set of messages (DMU reports and other
data), which can be sent or received by the ARINC Communications Addressing &
Reporting System (ACARS) via the ACARS-MU/ATSU equipment.
Among the main messages sent/received by the FDIMU/DMU via ACARS/ATSU can
be:
ACARS Downlink/Uplink messages routing
Downlink messages:
• ACMS reports (upon manual or automatic trigger, or upon uplink request from
the ground)
• broadcast of avionics parameters
Uplink messages:
• request for downlink of FDIMU/DMU data such as ACMS reports
• reprogramming of the DMU functions (e.g. modification of report limits,…)
Note: In addition to the above standard features, some other ACARS DMU functions
are available and programmable using the GSE.
The ACMS standard reports are typically defined for ACARS transmission (controlled
by the FDIMU or DMU) and can be transmitted if properly configured for ACARS
downlink.
ACARS ACMS report transmission example
2.5.2.5. MCDU interface
The Multi-Purpose Control and Display Unit (MCDU) is used to display, print ACMS
data and reconfigure some functions (providing status on several generic ACMS
functions, various reports and recordings, access to parameter call ups, and
reprogramming options).
The MCDU ACMS pages typically provide access to the following functions, when
appropriate:
• access to parameter callup functions (for Alpha callup and Label callup actions),
• access to ACMS stored report menu (for generated report consultation and view their
output status),
• access to aircraft documentary data (e.g. ACMS part numbers, A/C type, ..)
• manual triggering of reports (manual request for report generation),
• distribution of reports to output devices,
• management of the report inhibitions,
• temporary reprogramming of some FDIMU/DMU functions (limits, engine & APU hours
and cycles,..)
• control of the DAR/SAR functions or data consultation (e.g. DAR monitoring),
• PCMCIA card status (recorded file size and directories)
The capabilities are function of the aircraft configuration (type of DMU or

FDIMU and the loaded database software).
 For a brief description of the various MCDU ACMS menus available for a
particular DMU or FDIMU per vendor and A/C program, please refer to ISI article
31.36.00119 - ACMS MCDU Menu description - A320-A330-A340-A350 Family.
2.5.2.6. ACMS data readout:
Once downloaded or transmitted from the A/C, the ACMS data must be then
processed though specific ground readout tools (e.g. SAR, DAR data requiring
specific GSE processing). ACMS reports are typically readable in text format but may
also be processed by readout tools (e.g. ACARS report layout), when not otherwise
directly available in print format.
 DAR data frame specification and readout:
In a similar way to FDR data and FDRPL usage, DAR data frame specifications
are required for DAR data readout.
The DAR readout tools are usually the same as FDR/QAR GSE tools, given that
similar ARINC recording format is used. The GSE tools must be configured
according to the DAR data frame input specification for decoding (including
mapping and recorded parameter definitions) to come back to original
engineering values.
It is reminded that DAR frames are customizable (user reprogrammable), unlike

FDR frames (frozen).
Operator can freely program the DAR logic and parameters to be recorded at
convenience through the Ground programming tool (FDIMU/DMU GSE). AIRBUS
only provides by default, as part of the standard ACMS software installation, a
basic DAR default data frame.
In case the DAR frame has been customized, AIRBUS cannot therefore help
further to identify clearly the recorded DAR parameters and detailed mapping in
the frame (customized DAR frame definition is not known to AIRBUS). The
relevant office who performed the DAR programming (e.g.
SAGEM/TELEDYNE/HONEYWELL vendor or other approved office) will have to
be then contacted.
Note: There is so far no such application available as FDRPL for DAR default
data frame consultation. Either AIRBUS or the relevant office from
Operator’s facility or FDIMU/DMU vendors, who performed DAR
programming, must be then contacted.
DAR default frames, sorted per program, per equipment hardware &
software, are however available on AIRBUS WORLD portal in ISI article
31.36.00002 - Aircraft Condition Monitoring System (ACMS) - Standard
DAR dataframe definitions.
 In case of any Flight data decoding and analysis required to be

performed by AIRBUS within the scope of an accident/incident or
for Trouble-shooting purposes based on DAR raw data, please
also refer to ISI 31.30.00002.
- Compatible raw data format have to be provided to AIRBUS, along with

other relevant information (MSN, A/C configuration,..)
- a DAR data decoding by AIRBUS requires the provision by operators, in

addition to the raw data, of the associated customized DAR data frame
description (unless the DAR default data frame is used), or preferably
the ACMS database source files.
 ACMS database source files vs Upload files:
ACMS database source files (database itself) should not be mixed with the
upload files (upload floppy or PCMCIA files used for ACMS S/W loading)
• The ACMS database source file is a specific file (specific extension) or set of
files used by the GSE and characterizing the entire ACMS programmed database
of a given aircraft (AIRBUS standard database or a customized database).
Such source file(s) is(are) typically required for the reprogramming of the ACMS
or to visualize the content of a particular programming.
The source file(s) can be exported from the FDIMU or DMU GSE’s (ADRT tool,
AGSIV tool, SAGEM GSE tool), or obtained from the relevant office who
performed the ACMS customization (Operator’s office in charge of the ACMS
programming operations or from the FDIMU/DMU vendor directly if this latter
handled the programming).
• The upload files are different files (configuration files) generated by the GSE
created upon the selected ACMS database and used for software loading
purposes only.
Such upload files can for instance not be used to obtain DAR data frame
specification and should consequently not be sent to AIRBUS in the event of a
DAR data readout analysis.
Such files are also useless in the event of a database reprogramming to be
performed by AIRBUS for T/S purposes when needed (source files of the
customized database must be sent instead).
For HONEYWELL DMU:
o ACMS database source file is identified as an archive.
(containing several relevant files: INSTALL.dat, among other required files)
o exportable from ADRT tool.
For TELEDYNE FDIMU:

o ACMS database source file is identified as a .mdb file extension (e.g.
D0646RR05CAIB01.mdb)
o exportable from AGSIV tool.
For SAGEM FDIMU:

o ACMS database source file is identified as a .vec file extension (e.g.
v3403.vec)
o exportable from SAGEM GSE tool.
 A/C Input Parameter lists (AIPL):
The AIPL provide the (non exhaustive) list of parameters accessible to the DMU
or FDIMU equipment (ACMS part) for various purposes, like:
- for a parameter call up consultation (parameter definition for a MCDU label
call up readout)
- for any assistance in ACMS programming operations (database programming)
It provides detailed information on each acquired parameter (ARINC label

identification, Source system and complete label definition including LSB,
resolution and other relevant parameter information), already in use by the
FDIMU/DMU within the scope of a particular ACMS function or for a potential
programming or T/S purposes.
 AIPLs are available for consultation in ISI article 31.36.00102 – “ACMS-AIDS

Input Parameter List (AIPL)”,
2.5.3. CVRS (audio & datalink data) downloading and

readout
Several tools exist on the market which can be used for CVR data readout and
analysis.
This is however very dependent on the P/N of CVR installed on the aircraft (each
CVR manufacturer having developed its own GSE tools).
CVR readouts must be authorized by relevant airline/crew office (for privacy

considerations). AIRBUS performs CVR readout for its own purposes or on an
exceptional basis within the scope of a specific event investigation. Otherwise,
AIRBUS proposes a CVR audio data inspection service for regular inspections as per
CAT.GEN.MPA.195(b). Further information is available in Airbus e-catalogue.
Refer to ISI 23.71.00009 for further information on CVR download and readout.
For CVR equipment removal, Operators can refer to:
A320 family:
AMM TASK 23-71-35-000-001 – Removal of the Cockpit Voice Recorder (CVR).
A330/A340 family:
AMM TASK 23-71-35-000-801 – Removal of the Cockpit Voice Recorder (CVR).
2.6. ACMS / FDRS / CVRS – Retrofit considerations
The FDRS and ACMS systems provide the user with various recording means
(FDR/QAR data recording, Reports/SAR/DAR data recording) and storage
capabilities onto different peripherals/media (external QAR/DAR Optical disk /
PCMCIA card or FDIMU internal PCMCIA media card when available).
These various recording and storage means prove to be very helpful to operators
according to their needs.
It is also to be noted that latest software releases include various modifications

(minor/major improvements or corrections as a result of past experiences and for
continuous improvement).
It is therefore strongly recommended to apply the latest improvements and

recommendations from AIRBUS and Suppliers so as to ensure most optimized use of
the various equipment and ensure highest reliability (such as PCMCIA media
formatting procedures for instance, or latest ACMS software versions even when not
duly required).
Besides, due to the high degree of evolution of the recording systems and monitoring
needs, some operators may also need to upgrade their configuration with new
functions and/or new equipment, or remove some others:
- Change of the FDRS recording configuration (e.g. replacement of an existing

FDR model or Accelerometer model, installation of a new QAR 3TU
equipment or its definitive removal, upgrade of FDIU software or a modification
of the speed configuration due to a regulation evolution or for other specific
purposes,…),
- Change of the CVRS recording configuration (e.g. replacement of an existing

CVR model, datalink recording activation, 28VDC / RIPS power-supply
implementation due to a regulation evolution or for other specific purposes,...),
- Change of the ACMS recording configuration (e.g. installation of a new ACMS

software version, installation of new QAR 2TV model or its definitive removal
for a specific purpose,…),
- Or a combination of some of the above changes (e.g. move towards a full

FDIMU configuration, replace an existing DMU by a FDIMU working as a DMU
only for a specific reason,…),
It is recommend then to contact AIRBUS CUSTOMER SERVICES ENGINEERING

office or the dedicated AIRBUS Fulfill Customer Order (FCO) Manager through usual
RFC/RMO process for technical analysis and configuration upgrade proposal. The
request for change will be analyzed and answered accordingly.
3. REFERENCES
3.1. AMM references

FDRS AMM 31-33
ACMS AMM 31-36, 31-37
CVRS AMM 23-71
3.2. IPC references

FDRS IPC 31-33
ACMS IPC 31-36
CVRS IPC 23-71
3.3. TSM references

FDRS TSM 31-33
ACMS TSM 31-36
CVRS TSM 23-71
3.4. ASM references

FDRS ASM 31-33
ACMS ASM 31-36, 31-37
CVRS ASM 23-71
3.5. AWM references

FDRS AWM 31-33
ACMS AWM 31-36, 31-37
CVRS AWM 23-71
3.6. AIRBUS SIL references
SIL 00-086 Flight Data Analysis – Data Format and Supply

SIL 00-084 Aircraft Registration Change
SIL 31-023 Teledyne DMU: Status of Certified Standards
SIL 31-036 ATA 31 – Aircraft Condition Monitoring System (ACMS) Load Report
<15>
SIL 31-037 FDIMU replacing obsolete Teledyne DMU – Functional Constraints
SIL 45-004 Portable Data Loader Selection
3.7. AIRBUS Booklet references
- Booklet Ref. SEEA/952.0023/08 – June 08 (update of ST33004 – June 89)

“A320 Family AIDS – Troubleshooting Guidelines” valid for oldest DMU’s
(HAMILTON/TELEDYNE DMU’s P/N 7950x0-xx-xxx model / Nord Micro 903116243Bxxxxx
models)
3.8. FIN references
ATA A320 A330/A330

DMU 31-36 / 31-37 1TV 1TV
FDIU 31-33 2TU 2TU
FDIMU 31-36 / 31-37 10TV 10TV
LA 31-33 6TU 6TU
FDR 31-33 1TU 1TU
CVR 23-71 1RK 2RK
CVR CU 23-71 N/A 1RK (*)
CVR microphone 23-71 16RK 14RK
CVR preamplifier 23-71 18RK N/A
QAR (QAR position) 31-33 3TU 3TU
QAR (DAR position) 31-36 2TV 2TV
(*) CVR CU fitted with integrated preamplifier

ANNEX 1 – Onboard Data Recording and Maintenance concept
ACMS / FDRS
ANNEX 2 – FDRPL application
FDRPL tool and FDRPL user guide can be referred for any further information.
ANNEX 4 – SAGEM FDIMU PCMCIA Recording format and file
structure
(Applicable for SAGEM FDIMU/DMU’s only)
For DAR data:
DAR files are stored in a specific file format: RECxxxxx.dat

All DAR files are located in a specific directory with the A/C TAIL of the aircraft as
name with the extension “.REC”.
Disk architecture will be the following:
<< ROOT>> \ <<A/C TAIL.REC>> \ REC00000.DAT

\ REC00001.DAT
\ …..
For QAR data:
QAR Files are recorded under the same format as DAR: RECxxxxx.dat
All QAR Files are located in a specific directory with the A/C TAIL of the aircraft as
name with the extension “.QAR”.
Note that QAR stored data files are using the same format as DAR data files,
whereas the directory name is different.
<<ROOT>> \ <<A/C TAIL.QAR>> \ REC00000.DAT

\ REC00001.DAT
\ …..
For ACMS reports:
Each individual report are recorded as Rxxxxxxx.TXT

All SAR Files are located in a specific directory with the A/C TAIL of the aircraft as
name with the extension “.REP” (in a dedicated REPORT number folder).
<<ROOT>> \ <A/C TAIL>.REP \ REPORT01 \R0100000.TXT

\R0100001.TXT
\ ….
\REPORT02 \R0200000.TXT
\ ….
For SAR data:
SAR files are stored in a specific file format: Saxxxxxx.dat

All SAR Files are located in a specific directory with the A/C TAIL of the aircraft as
name with the extension “.SAR” (in a dedicated SAR channel folder).
<<ROOT>> \ <A/C TAIL>.SAR \SAR_1 \SA100000.DAT

\SA100001.DAT
\....
\SAR_2 \SA200000.DAT
\SAR_3 \SA300000.DAT
\….
\SAR_4 \ SA400000.DAT
ANNEX 5 – TELEDYNE FDIMU PCMCIA Recording format
and file structure
(Applicable for TELEDYNE FDIMU’s only)
The FDIMU PCMCIA card will contain the following files:
eoflocat.qar
eoflocat.qa2
qar.dat
dar.dat
msg.dat
sar1.dat
sar2.dat
sar3.dat
sar4.dat
sar5.dat
sar6.dat
sar7.dat
sar8.dat
For DAR data:
The DAR data will be recorded as dar.dat
For QAR data:
The QAR data (copy of the DFDR data) will be recorded as qar.dat
For ACMS reports:
The Reports will be recorded in a single file under msg.dat
For SAR data:
The SAR data will be recorded as sarx.dat (Each SAR file correspond to a SAR
channel)
Note1: x = 1 to 8 corresponding respectively to the eight SAR channels

available for recording, numbered from 1 to 8 (sar1.dat to sar8.dat) of the
TELEDYNE FDIMU’s.
Note2: As soon as the PCMCIA disk is inserted and before any recording of
data, the FDIMU will directly prepare the entire disk structure by writing all the
data files in it, and filling it up to the full card size.
The FDIMU will actually look at the available free space on the disk and then
write all the files on it according to the programmed partition (PCMCIA
memory allocation defined in percentage) and to the given PCMCIA card size.
The card will therefore be already filled at max size shortly after insertion (filled
with “empty” data”). Then, the data will be subsequently recorded in each
dedicated partition according to the programmed trigger once all the conditions
for recording are met.
(as an example, the sar1.dat file will always be present on the card and will
always show the same max file size whatever data has been recorded in it or
not).
Note that the file eoflocat files are locator files used for defining the beginning and
end of the data for each file. It is recommended to pay attention to it when
transferring the data to AIRBUS or other data requester in order to support decoding
operations.
PCMCI
A card
FDIMU PCMCIA card – Recorded files

ANNEX 6 – TELEDYNE WGL-QAR PCMCIA Storage
recording format
(Applicable for TELEDYNE WGL-QAR’s only)
The PCMCIA card (Recording media - Right slot) of the TELEDYNE WGL-QAR
equipment will contain the following files:
Message.dat
Eoflocat.qar
Eoflocat.qa2
Newdisk.dat
Raw.tag
Raw.dat
Wqar.log
The Raw.dat file will correspond to the actual recorded flight data: either the DAR
data (if QAR equipment is installed in FIN 2TV position) or the QAR data (if QAR
equipment is installed in FIN 3TU position).
The Message.dat file corresponds to the ACMS reports data (provided the reports
are transmitted through RS422 link to the WGL-QAR equipment) and other types of
message data.
Other files (Raw.tag, Eoflocat.qar, Eoflocat.qa2..) are used to ease data and event
identification or for trouble-shooting purposes (e.g. wqar.log for the logging of
significant events posted by the WQAR software).
Teledyne WQAR user guide can be referred for further information.

ANNEX 7 – GSE Vendor (FDIMU/DMU ground programming
tools)
ANNEX 8 – List of standard ACMS reports
A320 & A330/A340 AIRBUS standard ACMS reports

Note that some ACMS reports are not available for all equipment configurations, but
for some DMU’s or FDIMU’s only:
- FDIMU configurations only (highlighted in red color)
- DMU SAGEM and FDIMU configurations only (highlighted in blue color)
Besides, some reports are not available for all FDIMU software versions, but
depends on the P/N of software loaded into the FDIMU (e.g. new reports <16>, <34>
to <39>).
These AIRBUS standard ACMS reports are pre-programmed reports, which have
been defined and validated by AIRBUS.
This table is given for information only. It is recommended to refer to the AMM
(chapter 31-37) corresponding to the precise A/C (MSN) configuration.
ANNEX 9 – Readout and analysis tools
For further information on these tools, please contact AIRBUS.

ANNEX 10 – Mailing/Contact information
Please refer to your standard Supplier Customer Services & Technical Support focal
point. Otherwise (Contact in 2011):
 For HONEYWELL products when necessary:
HONEYWELL’s Technical Operations Center (TOC)
24-7 support contact:
Technical Support Engineer
U.S./Canada 800-601-3099
Europe 00800-601-30999
All Others 01-602-365-3099
21111 N. 19th Ave.
Phoenix, Arizona 85027
Email: aerotechsupport@HONEYWELL.com
Web Site: http://www51.honeywell.com/honeywell/
 For L-3 COMMUNICATIONS products when necessary:

L-3 COMMUNICATIONS, Aviation Recorders
Product Support
P/O Box 3041
Sarasota, FL. 34230-3041 USA
Phone: 941-371-0811
Fax: 941-377-5591
Web Site: http://www.l-3ar.com/
 For SAGEM products when necessary:

SAFRAN Sagem
Customer Technical Support
178 rue de Paris
91344 Massy Cedex
FRANCE
Web Site: https://www.sagem-avionics-support.com/
 For TELEDYNE products when necessary:

TELEDYNE-CONTROLS
REGIONAL AOG HOTLINE: +44-(0)-7699-391535
Head office:
501 Continental Boulevard
El Segundo, CA 90245, USA
Tel: +1-310-765-3600
Fax: +1-310-765-3604/3605
Web Site: http://www.teledyne-controls.com/
ANNEX 11 – Vendor SIL’s
This part is not exhaustive. Only main and most useful Vendor SIL’s are referred.
Latest revisions must be considered.
SAGEM DMU P/N ED45A300 and FDIMU P/N ED48A100/ED48A200:

- SIL 360-31-1040 for SAGEM FDIMU ED48A100, ED48A200 and DMU ED45A300 units.
Personal Computer Memory Card International Association (PCMCIA) Flash card
- SIL 360-31-1028 for SAGEM DMU ED45A300 units.
Maintenance Procedure for ground stations ED45/ED47
TELEDYNE FDIMU P/N 2234320-01-01 or 2234340-01-01 or 2234340-02-02:

- SIL 795020 No. 1 for DMU 795020-12-xxx units.
DMU Parts Obsolescence
- SIL 2234340 No. 1 for FDIMU 2234340-01-01 or 2234340-02-02 units.
Use of Microsoft Windows XP for formatting PCMCIA media
- SIL 2234340 No. 2 for FDIMU 2234340-01-01 or 2234340-02-02 units.
Recommendation for PCMCIA card vendor / type
- SIL 2234320 No. 3 for FDIMU 2234320-01-01 units.
Discovered error in Flight Data Interface (FDIU) software
Recommendation for PCMCIA card vendor / type
Use of Microsoft Windows XP for formatting PCMCIA media
FDIMU PCMCIA Media Insertion Guidelines
FDIMU Mandatory Software Upgrade
THALES QAR P/N 1374-100-00x or P/N 1374-200-00x:

- SIL THAV/SIL-1092 for QAR 1374-100-00x or P/N 1374-200-00x units.
Extended-storage Quick Access Recorder PNR 1374-XXX-YYY – Magneto
optical disk formatting procedure
GLOSSARY
A/C Aircraft
A/L Airline
ACARS Aircraft Communication Addressing & Reporting System
ACMS Aircraft Condition Monitoring System
ACU Alpha Call-Up
ADIRS Air Data Inertial Reference System
ADRT ACMS DMU Reconfiguration Tool
AIDS Aircraft Integrated Data System
AIPL Aircraft Input Parameter List
AIRFASE Aircraft Flight Safety and Analysis Explorer
AIRMAN Aircraft Maintenance Analysis
AMM Aircraft Maintenance Manual
AMU Audio Management Unit
APM Aircraft Performance Monitoring Program
APU Auxiliary Power Unit
ATM Air Traffic Management
ASM Aircraft Schematic Manual
AWM Aircraft Wiring Manual
CAM Cockpit Area Microphone
CMS Centralized Maintenance System
CNS Communication Navigation Surveillance
CPU Central Processing Unit
CRS Content Repository Server
CVR Cockpit Voice Recording
CVR CU CVR Control Unit
CVRS Cockpit Voice Recorder System
DAR Digital AIDS Recorder
DITS Digital Information Transfer System
DFDR Digital Flight Data Recorder
DLS Data Loading Selector
DMU Data Management Unit
ECAM Electronic Centralized Aircraft Monitoring
EEC Electronic Engine Controller
EOF End Of Flight
FADEC Full Authority Digital Engine Control
FCO Fulfill Customer Order
FDIU Flight Data Interface Unit
FDIMU Flight data Interface & Management Unit
FDM Flight Data Monitoring
FDR Flight Data Recorder
FDRPL Flight Data Recorder Parameter Library
FDRS Flight Data Recording System
FIFO First In First Out
FIN Functional Item Number
FOQA Flight Operations Quality Assurance
FWS Flight Warning System
GSE Ground Support Equipment
H/W Hardware
HMI Human-Machine Interface
I/O Input / Output
IAE International Aero Engines
ICAO International Civil Aviation Organization
IPC Illustrated Parts Catalogue
LRU Line Replaceable Unit
LSB Least Significant Bit
MCDU Multi-Purpose Control and Display Unit
MDDU Multipurpose Disk Drive Unit
MSB Most Significant Bit
OMS Onboard Maintenance System
P/N Part Number
PATS Playback and Test Station
PCMCIA Personal Computer Memory Card International Association
PDL Portable Data Loader
PFR Post Flight Report
PI Portable Interface
PNR Part Number
PW Pratt & Whitney
QAR Quick Access Recorder
RAU ROSE Analysis Unit
RFC Request for Change
RMO Retrofit Modification Order
ROC Read Out Computer
RPGSE Recorders Portable Ground Support Equipment
RPB Remote Print Button
RR Rolls-Royce
RTM Real-Time Monitoring
T/S Trouble shooting
S/W Software
SAR Smart Access Recorder
SIL Service Information Letter
TSM Trouble-Shooting Manual
VSB Vendor Service Bulletin
WQAR Wireless QAR
WPS Words Per Second
Survey for the Engineering Support section
© Airbus SAS, 2018. All rights reserved. Confidential and proprietary document.The technical information
provided in this article is for convenience and information purposes only. It shall in no case replace the
official Airbus technical or Flight Operations data which shall remain the sole basis for aircraft
maintenance and operation. These recommendations and information do not constitute a contractual
commitment, warranty or guarantee whatsoever. They shall not supersede the Airbus technical nor
operational documentation; should any deviation appear between this article and the Airbus or airline's
official manuals, the operator must ensure to cover it with the appropriate document such as TA, FCD,
RDAS. Access to WISE is supplied by Airbus under the express condition that Airbus hereby disclaims any
and all liability for the use made by the user of the information contained in WISE. It shall be used for
the user's own purposes only and shall not be reproduced or disclosed to any third party without the
prior consent of Airbus.

Getting To Grips With A320 &

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Getting To Grips With A320 &

Caricato da

Copyright:

Formati disponibili

Recording Systems - Getting to grips with A320 &

A330-A340 ACMS, FDRS & CVRS

ATA: 23-71 FIN: Ref: 31.33.00010

Old Wise Ref:

Old ISI Ref:

SUBJECT: GETTING TO GRIPS WITH A320 & A330/A340 ACMS / FDRS /

ATA CHAPTER: 31-33-00, 31-36-00, 31-37-00, 23-71-00

APPLICABILITY: All A320, A330/A340

REFERENCES: AMM chapter 31-33-00, 31-36-00, 31-37-00, 23-71-00

- to quickly, efficiently, accurately determine the cause of an accident/incident

ACMS and FDRS data recording concept and main applications

2.1.1. Flight data recording (FDRS) objective

The recording is performed by means of specific avionics hardware and software

Flight data recording (FDRS)

Cockpit voice recording (CVRS)

Cockpit voice recording (CVRS)

- Predictive monitoring to identify anomalies before real failure occurrence

- Condition-based monitoring to provide performance and trend information

A/C Condition Monitoring System (ACMS)

A dedicated ACMS ground tool (FDIMU/DMU vendor GSE) enables airlines to

2.2. ACMS / FDRS / CVRS - System architecture principles

2.2.1. CVRS architecture overview

2.2.1.1. Audio recording

 voice communications transmitted from or received on the flight deck by radio,

2.2.1.2. Data-link recording

The recording of datalink communications is therefore not implemented on all

2.2.2. FDRS and ACMS architecture overview

- A/C Interfaces to several peripheral devices (MCDU, MDDU, Printer, ACARS

- use of ancillary or optional recording equipment/devices (PCMCIA card

The functions are inherent to each equipment, manufactured by different vendors

From a data acquisition standpoint, several configurations are today certified by

Depending on the aircraft configuration, the following configurations can be found:

1) FDIU + DMU configuration

3) FDIU + FDIMU configuration (FDIMU working as a DMU function only)

Typical Full FDIMU configuration

 FDIU + DMU configuration

FDIU + DMU configuration

 Full FDIMU configuration

This configuration corresponds to the newest A320 & A330/A340 configurations

 FDIU + FDIMU (working as a DMU) configuration

This alternate configuration corresponds to the latest certified alternative, allowing

FDIU + FDIMU (working as a DMU) configuration

FDIMU/DMU data acquisition interfaces

The recording configuration and precise list of recorded parameters depend on

On A320 and A330/A340 Family in particular, the following recording configurations

 ACMS acquisition and recording

Cockpit interface overview with main communication devices

2.2.2.4. ACMS/FDRS data output

FDIMU (ACMS/FDRS) Data output overview

DAR data can be recorded:

QAR data vs DAR data recording

Note1: when an external “QAR equipment” LRU is therefore installed:

Note2: A QAR equipment in 2TV position (= DAR) can be used to record

2.2.3.1. External QAR 3TU vs QAR 2TV LRU

External QAR 3TU (= QAR data) installation

External QAR 2TV (= DAR data) installation :

2.2.3.2. Wireless Ground Link (WGL) QAR units:

Wireless QAR equipment (e.g. TELEDYNE)

WGL-QAR main features:

• No need for accessing the A/C, fully automated system

• Alphanumeric display and keypad (located on QAR front face panel)

This WGL-QAR function has proved to be of great interest to several operators to

Note1: The decision to install an external QAR LRU equipment on an A/C