M’ARMS / EC 225 - EC725
Page
1 / 262
SUMMARY
Introduction
p3
- p4
Presentation
p5
- p10
Acronyms
p11
1. Equipment and Description
p13
- p55
2. Communication
p56
- p66
3. Operating with the system
p67
- p86
4. Usage Analysis
p87
- p104
5. System Analysis
p105 - p109
6. Health Domain
p110 - p118
7. Health Monitoring
p119 - p133
8. Ground-Station Computer
p134 - p173
9. Ground Tools
p174 - p220
10. Quick Health
p221 - p230
11. Multibase Principle
p231 - p232
12. Health Indicators
p233 - p257
Appendix
p258 - p262
Page
2 / 262
Introduction
M’ARMS : Modular Aircraft Recording Monitoring System
HUMS system on EC 225 has been built for the following purpose:
- Satisfy to JAR OPS3’s compliances relative to flight data parameters
- Automation of flights and their analysis
- Provide a maintenance report and optimise help for maintenance
- Deliver a diagnostic for the main mechanical “critical parts”.
Airborne architecture has been developed on EC155 experience.
In the same way M ’Arms architecture on EC 225 is built following 3 concepts:
CVFDR
for the flight data recording parameters (crash recorder)
UMS
HUMS
defining the ARMS system
M’ARMS installed on EC225 is a full M’ARMS configuration. It will integrate the Ums
function and HUMS function. It has been developed using Euroarms MKII
experience and EC 155 architecture (M ’Arms).
Page
3 / 262
Introduction
1. CVFDR : Combined Voice and Flight Data recorder
The first purpose of this recorder is to save any time the last historical data : mandatory parameters and recommended
will be used for expertise in case of crash or investigation.
CVFDR will be downloaded by maintenance team for data validation and for investigation on overshooting.
2. UMS: Usage monitoring
Way of aircraft utilisation in flight. Monitoring flight data condition on every flight.
UMS function will integrate the historic of counting hours for maintenance job: mechanical main parts following.
The customer will have to provide data to keep his data base updated by downloading flight data daily.
3. HUMS : Health monitoring
Indicators qualified as “Health indicators” extraction from vibration spectrum will allow the identification of any degradation
of performance
This function will provide an important help for following mechanic trends
The M’ARMS system has been defined in 3 parts :
- An airborne segment to collect flight data acquisitions on board.
- A ground Segment will assist the treatment, the analysis, the historic management and data coming from UMS and HUMS
This is called GSC or Ground station
- A PCMCIA card will collect all data under a file name. These files will be called under the word of “sessions”.
At the end of each session, after the last engine shut down, Arms data will be transfer automatically o
PCMCIA card . This card will be downloaded daily on GSC
Page
4 / 262
Presentation
1. CVFDR
Purpose : Crash recorder storing in memory FDR data and audio signals for CVR function.
Compliance with CAA authorities.
FDRS= CVR+FDR
FDR : Data collected on helicopter. These data coming from the frame, engines, navigation, systems installed.
At power on, ”mandatory ” and recommended will be recorded under frame and subframe
CVR : 3 “audio“ signals insure the CVR function:
“Pilot“ et “copilot” audio signals collected on audio and mike issued from P and CP jacks
An ambiance mike will care about audio recorded in cabin.
Recording parameters will start at battery switched on. Supplied on battery (essential network).
CVFDR Objectives
Main goal on data recording is:
a) To confirm overshooting parameters exceeded during the flight detected by the Arms le system ARMS :
Overtorque, NR and Engines
b) to deliver a real diagnostic : after downloading data in case of accident
Nota: SSCVFDR will not deliver any message after flight in case of exceedance.
Download operation will be realized by an operator to check and confirm data stored inside the equipment.
For this purpose a computer Kontron called AHMU will be used for investigation.
Page
5 / 262
Presentation
2. Function UMS or Usage
Monitoring Counters associated to component to inform maintenance about time reached and alarms displayed
in flight:
- Time in operation
- Flying time
- Landings
- NR cycles
- Engines cycles N1(NG) et N2 (NF).
Exceedances monitoring on usage threshold in order to generate overshooting message in
of overshooting with flight manual:
case
- TQ1+TQ2 for Overtorque detection (damaging on MGB),
- Engines exceedances (limitation on these 3 modes T4, NG, NF )
- NR exceedance NR max (MRP damaging)
- Engine Power check basic function on EC 225 will be done from VMS. M’ARMS system will record data
for trend following.
All these functions will be automatically linked with operator after downloading data in he flight report
They will be saved inside GSC
UMS Objectives
Deliver useful parameters to maintenance in order to mention all exceedance about overshoot about engines
and frame.
Provide information about the flight helpful for maintenance purpose
Page
6 / 262
Presentation
3. HUMS Function or Health
Provide vibration data on main mechanical parts.
Generate maintenance message when threshold will be overshooted.
Analyse monitoring will be displayed on the following components:
- MGB: input shafts 23000, left & right ancillary gearbox, ….
- TDS : shafts and bearings on tail transmission
- IGB : Shafts and pinions
- TGB: input shaft and pinions
- ROTORS : vibration level in n
All the acquisitions are realised on these components in a predefined order automatically on board.
This function will be automatic and doesn’t need any pilot action. (less of load for operator)
HUMS function will realise also the « Rotor Tuning » function.
These specific acquisitions will be launch manually by the crew and will request a specific flight
configuration in accordance with flight manual.
HUMS Objectives:
Safety
Improve safety on board by detection abnormal vibration level
Anticipate detection on cracks, misalignment , unbalance, corrosion.
In-condition benefits
Improve comfort on board
Help and anticipate maintenance workload
Maintenance benefits
Adjust rotors : doesn’t request a specific technical flight
Help monitoring : daily spectrum on all mechanical components
Page
7 / 262
Presentation
MFDAU
F
D
R
S
Aircraft
Sensors
SSCVFDR
+
+
P
ACMS FDR
C
CVFDR
= CVFDR function
M
C
MFDAU
DTU
I.H.M
I
U
+
+
M
AIRBORNE
SGEMENT
ACMS HUMS
U
A
GROUND
SEGMENT
S
H
GSC
USAGE
Sensors
= UMS function
VPU
Magnetic Top
+
+
M
S
HEALTH
= HUMS function
AHMU
Page
8 / 262
Presentation
Airborne Segment is composed of:
For CVFDR function
- A recorder (voice and parameters)
- A module MFDAU (Miscellaneous Flight Data Acquisition Unit) used to concentrate data to the flight recorder.
it will be called MFDAU_ FDRS.
For ACMS function (Arms)
- A second module MFDAU ; heart of HUMS system will be called MFDAU_ ACMS.
Both MFDAU are identical (same P/N). They will be loaded with the same software but with different configuration tables
(ICT and DFS) introduced by Eurocopter.
These module are not interchangeable.
Each MFDAU will receive a different pin code (recognised at installation).
A single control unit including CVFDR et ACMS functions called IHM will insure
- failure monitoring
- Access to ARMS menu displayed on the screen pad
Flight Data : Acknowledgement about flight data
Data Transfer: Data Transfer at engine shut down
Rotor Tuning : acquisitions requested on rotors
A DTU called also MDR (Data transfer Unit) will receive flight data on PCMCIA card (link RS 422)
A VPU (Vibration Processing unit) will acquire HUMS the vibration data base on specific accelerometers.
These accelerometers are mandatory to collect vibration monitoring on aircraft.
Two magnetic pick-up used to deliver rotor speed and phase balancing
A set of magnetic electric plugs will monitor for the ACMS any alarm coming from gearboxes on A/C.
Page
9 / 262
Presentation
EC 155, EC 135, AS 365 N3, EC145,EC225
M’ARMS
AS 365 N3
EC 145
EC 225
EC 155
EC 135
Page
10 / 262
Acronyms
ADC
Air Data Computer
CVR
Cockpit Voice Recorder
AFCS
Automatic Flight Control System
ULB
Underwater Locator Beacon
APM
Auto Pilot Module
PCMCIA
VMS
Vehicle Monitoring system
Personal Computer Memory Card
International Association
EID
Electronic Instrument Display
IHM
Interface Helicopter Monitoring
AMC
Acquisition memory computer
CDU
Control Display Unit
MFD
Multifunction Flight Display
DTU
Data Transfer Unit
KDU
Key Display
MFDAU
Miscellaneous Flight Data Acquisition Unit
PU
Primary Unit
NF
Engine free turbine speed (N2)
NG
Gas generator speed (N1)
APIRS
FCDS
Flight Control Display System
NR
Rotor speed
ICP
Instrument Control Panel
EPAC
Engine Power Assurance Check
RCU
Reconfiguration Control Unit
VPU
Vibration Processing Unit
FADEC
Full Authority Digital Engine Control
GSC
Ground Station Computer
UMS
Usage monitoring system
EMU
Eurocopter Maintenance Unit
HUMS
Health and Usage Monitoring System
PGS
Software Professional Ground Station for CVFDR
CVFDR
Combined Voice and Flight Data Recorder
SOTAR
Software Spy Arinc Line 429
FDR
Flight Data Recorder
VIBRATO
Software for accelerometers check
ICT
Input Configuration Table
PMT
Portable Maintenance Terminal
CMT
Configuration Maintenance tool
Page
11 / 262
NOTES
Page
12 / 262
1. Equipment & Description
CVFDR
CVFDR ARCHITECTURE
SUMMING AMPLIFIER
AMBIANCE MIKE
IMMERSION UNIT
INERTIA CONTACT
CVR FUNCTION
CVR LISTENING
CVFDR INTERFACE WITH AHMU
IHM CONTROL UNIT
DTU CONTROL UNIT
DTU CONNECTION
PCMCIA CARD
HEALTH ARCHITECTURE
VPU
MAGNETIC PICKUP ON MRH & TRH
ACCELEROMETERS
MGB SINGLE AXIS ACCELEROMETERS
TGB SINGLE AXIS ACCELEROMETERS
TDS SINGLE AXIS ACCELEROMETERS
ENGINES ACCELEROMETERS
Page
13 / 262
CVFDR
1. Equipment & Description
1
2
4
A
3
3
A
BITE
5
Page
14 / 262
CVFDR
1. Equipment & Description
Definition
Recorder Unit Solid State technology
HONEYWELL (ALLIED Signals) called Black Box
Localisation
Inside tail boom to minimize damaging in case of crash.
Function
Recording data parameters mandatory representative of the
flight (engine configuration, altitude, airspeed) and audio signal
pilot, copilot and cabin.
Passive system which doesn’t modify aircraft input parameters.
Characteristics
Choc Résistance : 15 g
Resistance temperature: 1100°C/ 1 hour
Immersion : 1 month /20 000 ft.
No fan installed
24 hours recording data (FDR function)
2 hours recording for CVR each mike
Description
- An orange unit including the static memory (1)
- A logic circuit including power supply and control commands
(2).
- An acoustic beacon ULB (4) supplied by an internal battery is
fitted in its front face: low frequency transmission to localize the
unit.
Front face a connector to download data for laboratory
operation (3).
Maintenance
Before flight: manual Test on IHM (check list)
Periodicity : Battery on ULB. (SLL 6ans)
Data Downloading every 18 months.
Synoptique de la fonction
CVR/FDR
An amber light (5) “BIT” on unit will display an internal failure .
This light is associated to FDR light on IHM control unit
Power supply:
+28v essential (pin 55 )
Supplied through inertia contact and logic immersion unit.
FDR
IHM/ CDU
Page
15 / 262
CVFDR
Start Recording
SSCVFDR is recording as soon as power on.
Mandatory for >2730 kg.
Operative after BIT done (few ms after initialization test)
CVR et FDR flashing on IHM at power on
List of parameters mandatory and recommended coming from
MFDAU_FDRS are captured under Arinc 573 format.
Parameters are recorded under frames and subframes
transmitted under 12 bits at speed of 128 word/s.
One frame is fitted with four subframes. Each subframe will be
sampled every 4 seconds.
Stop of record:
- At battery switched off or In Case of crash or immersion:
- an inertia switch
- a logic unit associated with an immersion probe
1. Equipment & Description
IHM Functions dedicated to CVFDR
TEST Manuel:
During test no light will come on
Only an audio signal : “800 Hz” is generated through CVFDR
headset.
ERASE:
2 Pushbuttons should be set to initialise Erase function Audio
signal is cancelled from recording data.
(private flight)
Helicopter on ground with rotor brake applied and action on:
1. Erase on IHM
2. Erase on switch Erase in luggage compartment.
(2 operators required)
3. EVENT :
On of these condition will cut SSCVFDR line.
At this level; data cannot be overwritten. CVR light is coming on Provide a mark on the CVFDR graph to investigate after an
abnormal configuration
IHM control unit.
Analyse cannot be done alone and request a download operation
on CVFDR
Input
FDR Data : transit par MFDAU-FDR
CVR Data : signaux audio pilot , co-pilot, ambiance mike.
Page
16 / 262
CVFDR
ARCHITECTURE
Inertia Contact
1. Equipment & Description
Summing Amplifier
ambiance Mike
Immersion Logic Unit
I.H.M
CVFDR
VMS
AHRS
Airborne Segment
Immersion Probe
MFDAU/ FDRS
Ground Segment
A.H.M.U
(PGS: Software used to download CVFDR data and analyse in real time )
Page
17 / 262
SUMMING
AMPLIFIER
1. Equipment & Description
Page
18 / 262
1. Equipment & Description
SUMMING
AMPLIFIER
J1
SSCVFDR
GND
46
GROUND
Ambiance mike
Rouge
Mike signal
+ Mike signal Area Micro signal -
38
39
39
38
5 VDC
37
Return 5 V
Ground
45
31
-12 dB
- 6 dB
49
48
Commun Attenuation
Noir
Blanc
Vert
55
Return 28 VDC
53
Pilot audio IN +
Pilote Audio In +
+Pilot audio IN Pilote Audio In -
+ 5 VDC
PWR -
Return 5 VDC
Attenuation ambiance mike
A
audio
Copilot
IN In
- Copilote
Audio
PWR +
54
+ 28VDC
audio Copilot IN +
S10 -
Mike Out +
Micro Out +
Mike Out Micro Out -
S10 +
16
15
24
9
8
27
Summing Amplifier
Channel B Audio Copilote
1
4
Channel A Audio Pilote
9
38
33
17
11
21
46
+ 28 V dc
47
Ground
45
0 Vdc
CoPilot Mike
Audio CoPilot +
Audio Co-Pilot Pilot Mike +
Audio Pilot +
Audio Pilot -
Page
19 / 262
SUMMING
AMPLIFIER
1. Equipment & Description
Definition
Channels summing amplifier
Function
Dedicated Equipment dedicated for CVR function : amplifier
Audio signals+ Mike are directly linked from from jacks P and CP
Description
Mixing Amplifier for the signals Mike and audio coming from channels pilot et copilot.
Location
Inside Cargo
Characteristics
Weight : 500 g
Operation
Test equipment CVR will be realized through a special headset impedance 600 ohms.
Connexion
input = Audio Pilot et Copilot
output = to flight recorder unit
Power supply
Double supply with a +28 V Battery / protection par breaker 3 A
Page
20 / 262
SUMMING
AMPLIFIER
1. Equipment & Description
Page
21 / 262
AMBIANCE
MIKE
1. Equipment & Description
Definition
Ambiance Mike
Function
Monitoring noises and frequencies coming from cabin to identify rotor regime for adding information for analyze purpose.
Location
On the overhead panel between pilot et copilot seats.
Characteristics
Frequency band:150 -6000 Hz.
Operation
Audio issued from ambiance mike can be checked :
1. in real time (PGS software) To test ambiance mike will be tested through a specific headset (real time audio check)
2. after downloading CVR function (PGS software) through AHMU
Connection
INPUT = signals audio and micro
OUTPUT = CVR recording
Power supply
Ambiance mike receives a 5volts input to supply its internal amplifier provided by CVFDR unit
Page
22 / 262
IMMERSION
UNIT
1. Equipment & Description
Immersion Probe
Logic Immersion Unit
Page
23 / 262
IMMERSION
UNIT
1. Equipment & Description
Definition
Electronic Immersion logic
Function
Detection following a major incident (A/C ditched).
Logic unit is linked with an external probe
Cut the main power supply of the CVFDR unit keeping in memory the last hours recorded on board.
Description
An immersion probe fitted with two resistors, one hot and one cold.
When immerged probe resistors become equal unbalancing logic unit input : “CVR” light is coming on IHM control unit.
Location
Immersion probe is fitted inside right side.
immersion logic unit fitted rear cargo side (close to BTP)
Characteristics
Weight : 80 g.
Periodic check : Maintenance every 18 months.
Power Supply
+28 V / 3 A
Page
24 / 262
1. Equipment & Description
INERTIA
CONTACT
Inertia contact
+ 28 V Battery
Logic unit Immersion
A
A
B
C
C
Input 28v control
F
Output 28v to SSCVFDR
Immersion probe
Thermo probe 1
Thermo probe 2
A
D
B
C
J
M
V
K
L
A
B
Hot Probe
Ground
Cold probe
+ 28 V dc power supply
0 Vdc
Page
25 / 262
INERTIA
CONTACT
1. Equipment & Description
Definition
Ball contact compressed through a spring.
Function
Stop recording CVR and FDR following a hard landing
Cut the line over an acceleration of 6,5g.
This detection (open contact) will cut the CVFDR power supply. CVR light will come on on IHM.
Description
Electrical Contact.
This equipment will be replaced after release.
When it is new, it is delivered with a cutter pin to avoid any activation.
Localisation
Back MGB on top.
Characteristics
Weight :105 g
Operation
Contact is closed between pin B and C
Page
26 / 262
CVR
FUNCTION
Erase : to cancel audio data
« Erase » Operation : “400 Hz” Tone is generated in
CVFDR headset (transmission signal 3s, blanc 1s)
SSCVFDR
summing Ampli
1. Equipment & Description
Ambiance mike
“Erase”
switch 2
Hydraulic switch on rotor brake
“Erase”
switch 1
IHM
Page
27 / 262
CVR
LISTENING
1. Equipment & Description
CVR in real time
Luggage Compartment
Inside tail boom
Page
28 / 262
CVFDR INTERFACE
WITH AHMU
1. Equipment & Description
Download processing and real time analysis
552VC
SSCVFDR ALLIED
TEST
552
VCet
déchargeme
nt CV/FDR.
Test Plug
maintenance
552Vc
Download is possible from plug 552Vc
Lignes
Arinc 573
B
A
N
11
22
33
D
C
66
77
F
E
H
1313
1414
2121
RTS RTS +
G
K
J
2222
3333
4141
CTS +
FDR Data - IN
FDR Data + IN
M
L
3434
4242
FDR Data - OUT
TX TX +
ATE Présent
RX RX +
CTS -
FDR Data+ OUT
Page
29 / 262
CVFDR INTERFACE
WITH AHMU
1. Equipment & Description
Page
30 / 262
IHM CONTROL
UNIT
Definition
I.H.M : Interface Helicopter Monitoring
Description
Control unit fitted with :
- A screen pad displaying :
- HUMS menu (function used by crew)
- status PCMCIA card (ARMS+ CVFDR)
- An alarm system status indicating:
- alarms on CVR, FDR and HUMS
Function
Permanent Check on : CVFDR, MFDAU and ACMS
CVFDR : CVR, FDR
ACMS : HUMS light to detect
- inconsistency between software MFDAU/ACMS
(configuration files ) and pin code
- Missing signals NR, NG or NF or not updated over
than 10‘’
- dialogue loss between equipments
Location
On pedestal control unit
1. Equipment & Description
Characteristics
Weight: 600g
Consumption = 30 w
CVFDR Functions
– Test
– Event
– Erase
HUMS Functions
- Rotor Tuning
- Flight Data
- Data transfer
Operation
Following initialization sequence (few seconds after power
on) main menu will take place
Connexion
input : MFDAU ACMS / MFDAU FDR
output : CVFDR and HUMS purpose
Alimentation
+28v Essential network / 3 A
Page
31 / 262
DTU CONTROL
UNIT
1. Equipment & Description
Magnetic Detector
TARGA
Page
32 / 262
DTU CONTROL
UNIT
1. Equipment & Description
Definition
Data transfer unit.
Allow to read files fitted on PCMCIA card.
Function
PCMCIA should have to be inserted inside DTU before flight
Interface between MFDAU and PCMCIA card. Flight data issue from MFDAU are transferred under RS 422 format.
Block of raw data 4Kb capacity will be transferred every 4 seconds.
File .225 (ACMS) file will be transferred at the end of flight
At the end of transfer a message ” transfer Done” will be displayed. Card can be removed
Description
2 types of DTU
- One on the GSC which request an external power supply 15v
- One on aircraft 28v fitted with a cover
Opening front cover on airborne DTU will affect the message “No card” on IHM.
Location
Rear side of Cargo bay
Characteristics
Weight : 750g
Power supply
+28 V / 3 A
Page
33 / 262
DTU
CONNECTION
1. Equipment & Description
MFDAU HUMS
DTU
C2
A
DTU IN +
27
10
DTU/MFDAU +
DTU IN -
28
9
DTU/MFDAU -
7
GND
29
8
MFDAU/DTU +
30
18
MFDAU/DTU -
RS 422
DTU OUT +
DTU OUT -
6
DTU présent
ACTIVATION ACMS
GND
11
RTS + (RS 422)
C1
14
CTS + (RS 422)
26
20
RTS - (RS 422)
21
CTS - (RS 422)
22
RTS (RS 232)
17
CTS (RS 232)
12
+ 28 V
13
+ 28 V
19
1
Ground
5
Page
34 / 262
PCMCIA CARD
1. Equipment & Description
File format:
The card will contain files created on board. Each session will get 2 files:
- One file with extension “.225” where HUMS data will be
recorded (Usage and Health data).
- The other one with extension “.raw” which contains the
defined list of FDR data used for FDM.
PCMCIA card is not affected to a special aircraft. It can be installed on any
helicopter fitted with M’ARMS system
Possibility to record files coming from different helicopter
2 types of Messages relative to card status:
”No Card ” : missing card
“Full Card” : memory available < 8Mb
Session
PCMCIA description:
High capacity : 256 MB solid state (non volatile memory)
FDM data
HUMS data
« .raw » file
« .225 » file
PCMCIA characteristics:
MTBF> 1000 000 Hours / Temp -40 à +85° C
Page
35 / 262
PCMCIA CARD
1. Equipment & Description
File Format:
Each file will be identified as below:
- software version helicopter
FDM
1FF41
02d
raw
HUMS
1FF41
02d
225
- pin program (family, S/N)
- session number
File format and session number will be displayed in
hexadecimal.
At session starting MFDAU /ACMS memorise time and date
of the session.
Pin code in Hexadecimal
(Decimal = 130881)
Session number
in Hexadecimal
Extension file
(Decimal = 45)
Every start, airborne segment will generate a new session.
This session will be recorded and displayed in GSC
computer.
ACMS data coming from different cards and helicopters will
be recorded inside GSC.
File List displayed under Windows Explorer
Page
36 / 262
PCMCIA CARD
1. Equipment & Description
« .RAW » File Definition:
Such file is the result of 128 parameters recorded on configurable input defined on MFDAU DFS table. This file
created at each starting will generate raw data for a maintenance help.
This is to provide « replay » of the flight and analyse the exceedance limitation.
A « .raw » file will integrate pin helicopter code and session number. It will be displayed on GSC through PGS
software.
Input data are read by blocks of data and recorded on DTU every 4 seconds without coding under format A429.
Frequency of each data identified is 2 Hz.
MFDAU time will be a parameter user can select on parameters list
SSQAR function « downloading in continuous flight data » is a part of module MFDAU/ ACMS and will
be closed correctly if a «watchdog is deactivating the system.
If during continuous data recording DTU front cover is opened or card removed, data will be lost temporally .
Page
37 / 262
PCMCIA CARD
1. Equipment & Description
Parameters list fitted in. Raw files
Provided by VMS
Date
Time
Nr
P0
OAT
Airspeed (IAS)
Trq 1
Trq 2
Dng 1
Dng 2
N11
N12
N21
N22
TOT 1 (Eng 1 temperature)
TOT 2 (Eng 2 temperature)
Engine configuration (Training,OEI ou AEO)
Flight/ground Logic
Altitude ZB
MGB Oil Pressure
MGB Oil Temperature
Weight
FLI 1 (first limitation)
FLI 2
Provided by FDRS
Vertical Acceleration (Gama Z)
TR Position
Collective pitch
Altitude Radio altitude
Pitch Position
Roll Position
Heading
Pitch Attitude
Roll Attitude
Pitch rate
Roll rate
Yaw rate
GAM Z
TR_Pos
ZRS
Pitch
Roll
Hdg
Pitch attitude
Roll attitude
Pitch rate
Roll rate
Yaw rate
Page
38 / 262
HEALTH
ARCHITECTURE
TGB
(1)
IGB
(1)
1. Equipment & Description
+
TDS
(5)
Fan
(1)
MGB
(8)
Engines
(2)
Load
Amplifiers
I.H.M
(4)
Pickup TR
2 M.F.D.A.U++
TR
MR2
D.T.U
MR3
VPU
Airborne SEGMENT
MR1
Ground
SEGMENT
AHMU
PCMCIA
GSC M ’ARMS
Page
39 / 262
VPU
Vibration Processing Unit
1. Equipment & Description
During the session VPU is used for the following check :
-rotors monitoring
Health interface for the HUMS function.
-gears on MGB, IGB,TGB
- Realize Health monitoring for all the components
monitored
-TDS monitoring shafts and bearings
- Compute the results for rotors adjustment
- Bearings monitoring on MGB, IGB and TGB
- Engines vibration monitoring in stabilized mode and at starting
- Rotors adjustment MR and TR
VPU is a generic equipment loaded with a software to be
installed on a EC 225. It can be installed on any ECF family
Software downloading will be done before installation.
Acquisitions are executed following a predefined cycle
This determine VPU cycle from beginning to end of session
Some acquisitions called priority can be requested any time
interrupting the normal cycle, time to realize the acquisition.
MFDAU_ACMS will pilot VPU for acquisitions processing.
For each demand requested by VPU, VPU sends back a
message “correct acquisition” or “incorrect acquisition”.
On ground
priority 2: rotor monitoring
priority 2:eng vib stabilized
Acquisitions correct: MFDAU_ACMS asks VPU to send back
its results before to pass to next acquisition.
priority 1: engine start monitoring
priority 1: rotor monitoring
priority 0: Rotors adjustment
priority 0: rotor adjustment
In flight
Page
40 / 262
VPU
VPU Characteristics
Integration of a new software on VPU could be done with
AHMU using CMT software ( uploading process)
MFDAU_ACMS and VPU will be linked through an RS
422 line.
VPU defect
At power on
VPU generates its “BIT” and elaborates its status.
ACMS (MFDAU) sends a status command “status” and
receive in return VPU status “Go” or “No Go”
If VPU doesn’t answer or sending a bad result (No Go)
(checksum error ) in Status mode a VPU failure will be
recorded. This code (result of Status) coded under 8 bits.
If pin code is not recognized health acquisitions will be
inhibited
1. Equipment & Description
If the status is “Go” then the MFDAU reads the ACMS version
addressed to VPU and the one waited by the S/W downloaded
onto the VPU. If it is not compliant, “ACMS/VPU
inconsistency” is recorded.
Defects on VPU:
In normal operation
For each acquisition , VPU sends back a message to MFDAU
about the result acquisition.
If OK: Result is sent to MFDAU/ACMS
If no OK:
1/ No response from VPU or response unclear: major failure
recorded on VPU, interruption of acquisition cycle (major
defect)
2/ acquisition not acquired :out of range: minor failure
Page
41 / 262
VPU
1. Equipment & Description
“Discrete Input”
Capacity:12 discrete input
8 discrete available to identify aircraft pin coding
4 discrete available for maintenance (VPU reconfiguration) (Reset,
Reprog, flight/ground position, presence computer RS232)
Tachometers:
Capacity: 8 channels available
4 used for phonic wheel as N11,N12, N21,N22.
2 used for magnetic pick up MR and TR.
2 not used
Accelerometers
Capacity: 36 input axis
Page
42 / 262
MAGNETIC PICKUP
ON MRH & TRH
1. Equipment & Description
MRH
TRH
Interruptor on MGB
+
target
Page
43 / 262
MAGNETIC PICKUP
ON MRH & TRH
1. Equipment & Description
Function
Determine airspeed and phase rotor position.
Mandatory to validate acquisition RTB on VPU
Description
Magnetic pick up is fitted in face of a target in order to generate the speed signal.
Process
Used to tune rotor AR (software Steady Control Rotor) to define track and balance and determine unbalance
phase position.
This information is required to optimize level of vibration on aircraft.
Characteristics
Distance between sensor and target: 1.25 mm -/+0.25.
Page
44 / 262
ACCELEROMETERS
Function
Provide vibration data on VPU for health acquisitions
Description
3 type accelerometers (Mono-axis, Bi-axis, Tri-axis)
Fitted at different places they are monitoring:
- Bi-axis is monitoring Health on MR an TR
(automatic acquisitions ground and flight )
- Rotor tuning (specific function for rotors) MR and TR
1. Equipment & Description
Rotor Tuning
Bi-axis : Measures vertical acceleration (interchangeable
between main and tail rotor)
Y
TR
Z
Characteristics
Health monitoring on components
Pinions/Shafts/Bearings
Type: Single with internal amplifier
Rotor Tuning
3 Accelerometers with amplifier integrated
Y
Y
Z
Z
single Vertical
MR
Bi-axis
Vertical /Lateral
+
Y
X
Z
Engines
Specific single axis on engine resisting to high temperature. Two
amplifiers by engine associated to 2 accelerometers.
Tri-axis
Vertical/ Lateral /Longitudinal
Page
45 / 262
ACCELEROMETERS
1. Equipment & Description
Main Rotor and Tail Rotor
4 accelerometers dedicated on adjustment : 3 MR;1TR
Tail Rotor
Bi-axis on tail
Main rotor
Accelerometer
Single axis under
pilot seat
Main rotor
Tri-axis under cabin floor
Main rotor
Accelerometer Bi-axis under
copilot seat
Vibrations acquisitions are necessary for the following configurations (FPOG, Hover, Cruise 100 knts, MCP)
to obtain the correct adjustment will be requested by a crew member
Result on balancing will be displayed on IHM control unit
Page
46 / 262
ACCELEROMETERS
MGB
1. Equipment & Description
Health monitoring
Page
47 / 262
ACCELEROMETERS
TDS
1. Equipment & Description
Health monitoring
Page
48 / 262
MGB SINGLES AXIS
ACCELEROMETERS
1. Equipment & Description
Page
49 / 262
MGB SINGLES AXIS
ACCELEROMETERS
1. Equipment & Description
Interchangeable Single axis on MGB monitoring components on MGB :
Input Monitoring 23 000 rpm
Epicyclic module monitoring
Page
50 / 262
MGB SINGLES AXIS
ACCELEROMETERS
1. Equipment & Description
MGB
Left Ancillary Box
Page
51 / 262
TGB SINGLES AXIS
ACCELEROMETERS
1. Equipment & Description
Monitoring
Input TGB
Page
52 / 262
TDS SINGLES AXIS
ACCELEROMETERS
1. Equipment & Description
A single axis fitted on transmission for shaft and engine monitoring
Page
53 / 262
ENGINES
ACCELEROMETERS
1. Equipment & Description
Engine accelerometer ( 2 per engine interchangeable)
Accelerometer linked with load amplifier
4
Amplifiers in cabin
Page
54 / 262
NOTES
Page
55 / 262
2. Communication
ARCHITECTURE FDRS/HUMS
INTERCONNECTION
SYSTEM
MFDAU MODULE
Page
56 / 262
2. Communication
ARCHITECTURE
FDRS/HUMS
There are 2 MFDAU modules fitted on the aircraft and powered up by direct battery:
- One for CVFDR data
- The other for HUMS & FDM data
DTU
MFDAU CVFDR
CVFDR
HUMS & FDM
MFDAU HUMS & FDM
MFDAU modules powered up by direct
battery
Page
57 / 262
2. Communication
INTERCONNECTION
Vibration sensors
VMS - MFD- FADEC- APM
VPU
NR,N1, N2
RS422
ARINC 429
ARINC 573
in
out
MFDAU
FDRS
RS 485
MFDAU
ACMS
HMI - CP
CVFDR
RS 422
DTU
Flight segment
Ground segment
M’ARMS GSC
Page
58 / 262
SYSTEM
2. Communication
The system stores in memory all data recorded as soon as
one engine start .
During download the system transfers automatically the file
225.
The session will be linked to one helicopter only and
identified as Helicopter Type _ serial number_ session
number
« .raw »: Continuous download: 1,8MB/hour
A session = A flight or a ground run
« .225 »: Around 300 Kb per flight
A/C S/N and A/C type are identified through a pin code. This
pin code is made by straps rear side on MFDAU
Health acquisition are automatic, following a cycle defined
inside the VPU and don’ t require any pilot action.
Each file will be identified on the airborne segment and a
packed session will be generated if the last flight was
not transferred correctly.
Only rotors adjustment request manual acquisition
How to define a session?
 First engine start
 Start engine 1: N11>5% or N12> 5 %
 Last engine Stop : N11<5% and N12<5 % with NR< 85trs
 ACMS data will be transferred end of flight PCMCIA card.
 “Usage” data will be displayed on IHM control unit
Page
59 / 262
SYSTEM
2. Communication
The number of session is automatically increased after each use and re-initialise after each MFDAU replacement or
download of a new ACMS S/W version onto MFDAU.
This number is recorded at file transfer on PCMCIA and compared with the last MARMS number session recorded onto
GSC for the associated aircraft. This makes the operator aware about any missing or non downloaded sessions.
In case of, the user is able to create missing flight on GSC and so update the usage cycles counters.
Regarding the on-board, before engine start, it is necessary to check the system status.
If the last flight has been correctly downloaded, it will be deleted from the memory of the MFDAU.
On contrary, if the session has not been correctly downloaded, the message « transfer » will be displayed on IHM
requiring a manual download through the command « Data Transfer ». At this step, if the transfer is not done, an
abbreviated session will be generated and saved on MFDAU memory. Such session contains only usage information. A
maximum of last 20 files could be saved like this.
Page
60 / 262
2. Communication
MFDAU MODULE
PACKAGING EQUIPMENT LINE CONCEPT « AVIONIQUE NOUVELLE »
PELICAN Rack
MFDAU-FDRS
A
MFDAU-ACMS
2
Miscellaneous Flight Data Acquisition unit
Module fitted with a lock handle
Page
61 / 262
MFDAU MODULE
Definition
FDR et ACMS
Function
MFDAU is an acquisition unit which convert flight
parameters format under different format.
Flight data are coming from different sensors with
different input data entrée
- analog
(NR,NG,NF)
- digital
(APM, VEMD, FCDM, FADEC)
- discrete
(Alternat Radio, logic input)
Process is to record flight data in order to compute
ACMS function on board. This will insure HUMS function
through VPU to provide health purpose.
Dialog with different interface working with VPU,IHM,
CVFDR.
A link between MFDAU Arinc 429 checks the
consistency between acquired signals
Description
MFDAU++ ACMS is fitted with a lithium battery to maintain
date and time on board generating starting session time
(OTL : 5ans)
2. Communication
 Fitted with internal memory (RAM) in order to save ACMS data
on the last flight. Keep on memory for 5O hours through
capacitor. If the flight has been downloaded correctly data on RAM
will be erased.
To operate MFDAU_ACMS and FDRS will receive a software.
One version only will be provided on both MFDAU++ fitted on EC
225.
On MFDAU FDRS the software will be grounded (software
inhibited)
2 tables ICT and DFS will be loaded on equipment : un code
707A…..will be set.
These tables will be different according to the module function
FDRS or ACMS : two pin program different.
Pin code linked with (helicopter family, configuration system, DTU
presence...). Their position on the rack are essential.
They are not interchangeable.
Pin code is defined by jumpers rear side of the connectors.
18 bits recognising :
Position: discrete
Type : coding on 5 bits : EC 225 (family)
Configuration :coding on 7 bits (engines, Fadec)
Serial Number :coding on 6 bits
 System configuration is identified at power on through the
configuration file but also through pin code which is different on
each helicopter.
Page
62 / 262
MFDAU MODULE
2. Communication
MFDAU_ACMS & MFDAU_FDRS realize a status process and auto validate the processing.
Memory inside MFDAU_ACMS will not be saved over 50 h.
Difference between MFDAU modules
Pin code type + configuration defined on EC225
APIRS will be used to provide accelerations under three axis . No adding accelerometers will be fitted for this
function
Page
63 / 262
MFDAU MODULE
code Pin
2. Communication
module MFDAU power supply
Page
64 / 262
MFDAU MODULE
Operation
ICT /DFS tables are loaded inside MFDAU EEPROM.
(Electrical Erasable Programmable Read only Memory)
At power on: each MFDAU is sending a “BIT” (Built in test)
and elaborate a status validity following its function and its
position.
MFDAU -FDRS can generate two status failure introducing
FDR alarm :
-failure type “incompatibility” between helicopter type
(pin code) and version table configuration.
- Failure type “logic” internal to MFDAU module or CVFDR.
Nota: A MFDAU module failure will not interrupt the ACMS
software
MFDAU -ACMS can generate HUMS alarm on IHM :
lost of validity or invalidity NR, NG1 or NG2 mandatory to
define data status of the system
On ground : no starting session
During flight : <10s minor failure code PACM recorded
>10s disconnection of ACMS (watchdog)
2. Communication
Power Supply
Double power supply 28 v (pin 34 and 35 connector C)
Essential Network and direct battery
Consumption : 25 w each
Input
 VMS: data coming from vehicle and engines (alarms and flight
parameters.).
 APM modules
 PU: EID/MFD navigation parameters navigation control
 RCU: Reconfiguration system unit
 FADEC 1 and 2: digital computers managing both engines
block of data coming from analog sensors (NR), (NF), PA settings,
discrete).
Output
.
Interfaces aux formats:
 A 573 for SSCVFDR treatment of parameters
(Solid State Cockpit Voice and Flight Data Recorder)
 RS 422 data link DTU and VPU
 RS 485 interface with IHM control unit
A429 to dialog between modules
Page
65 / 262
NOTES
Page
66 / 262
3. Operating With The System
PROCESS
IHM CONTROL UNIT
IHM MENU
FLIGHT DATA ACCESS
FLIGHT DATA ACKNOWLEDGEMENT
ROTOR TUNING
DATA TRANSFER
MARMS GSC
MARMS GSC DOWNLOADING
FLIGHT REPORT
MAINTENANCE REPORT
DISCREPANCY REPORT
DIAGNOSTIC REPORT
Page
67 / 262
PROCESS
3. Operating With The System
OPERATOR
PROCESS
STEP1: PRE-FLIGHT
PILOT/ENGINEER
STEP2: IN FLIGHT
STEP3: POST FLIGHT
SESSION
« .raw » file
« .225 » file
PILOT/ENGINEER
STEP4: TRANSFER to GSC
FDM data
File stored on GSC Hard Disk to be used later on…
HUMS data
MAINT
REPORT
---------------------
STEP5: ANALYSIS AND
DIAGNOSTIC
GSC M’ARMS
DATABASE
ENGINEER /
HUMS EXPERT
AMM
… PGS s/w
or other.
PRINTER
STEP6: MAINTENANCE
ACTION
EC SUPPORT
MAINTENANCE
EXPERT
Page 68 / 262
IHM CONTROL 3. Operating With The System
UNIT
1
2
3
6
4
No.
1
DESCRIPTION
SCREEN
EVENT
CVR
2
MENU zone
Selection of Menu options:
 Flight data / Data Transfer / Engine check/ Rotor Tuning
 View status and results of acquisition (Run,Done,Fail…)
3
EVENT Marker
Create a marker on CVFDR to take note of flight data
parameters in event of an unusual incident encountered by
the pilot/ crew during flight.
4
ERASE button
To erase audio tracks recorded in CVFDR on ground only.
Activation of this erase button is associated with erase
switch located in the luggage compartment. (2 persons)
5
6
TEST pushbutton
CVR indicator light
7
FDR indicator light
8
HUMS warning light
9
ENTER key
ERASE
FDR
BACK
ENTER
TEST
HUMS
7
13
12
11
10
9
5
8
FUNCTION
3 rows of information (19 alphanumeric characters
maximum)displayed :
 Menu selection and scratchpad zone
 Page Number displayed on right hand bottom area.
10 SCRATCH PAD zone
11
UP arrow key
DOWN arrow key
Initialize the CVFDR built-in test.
Indicates an audio recording fault.
Indicates a flight data recording failure or a MFDAU module
failure.
Indicates a major failure of the ACMS.C.
It is used:
 To activate a selected command
 To reach a sub-menu .
 To manage the option type field in flight data menu (Y/N)
Displays on ground only with engines and rotor stopped.
“Full Card” or “No Card” message : PCMCIA status
“Transfer “ message in case of last flight not downloaded
 Provide Initialisation of IHM self-test procedure by
simultaneously pressing both arrow keys for more than
5 seconds
 Scrolling through the menu.
12 Dashed line
Permanently displayed on the screen.
13 BACK key
Return to previous selection of menu option.
Page
69 / 262
IHM MENU
3. Operating With The System
A. At power on (engines stopped)
B. Rotor running
Flight Data
Flight Data
Data Transfer
Data Transfer
Not enough Memory
PCMCIA not installed
No Card
Rotor Tuning
1/2
Full Card
1/2
2/2
. “HUMS” Alarm
Software Pb MFDAU/ACMS or helicopter pin code not recognised (No Data from Hums)
Inconsistency between MFDAU/ACMS and tables configuration
NR ,NG or NF parameters invalid
•
Alarm “FDR”
FDR alarm or module MFDAU failure or FDR function not operating
•
Alarm “CVR”
CVR function not operative or power supply missing on SSCVFDR unit.
Page
70 / 262
FLIGHT DATA 3. Operating With The System
ACCESS
After flight: Possibility to display the last flight data
Once automatic data transfer has been realised, crew member can get access to “ Usage” data contained on last session.
(engines shut down , main battery on)
1. Get access to ”Flight Data” menu then Press “Enter “
2. Use index “Down “or “Up” to access to the different pages
In case of exceedance it will be shown : the type; max value reached ;duration ; and date of it.
Cycles NG / mot 1
Cycles NF/ mot 1
Airborne
Oat at take off
1 H 43
N11 Cycle
1.20
N12 CYCLE
1.20
OAT
+18.0 C
2
N21 Cycle
1.0
N22 CYCLE
0.9
Wow
9500Kg
Landing
NR exceedance
NR
Cycles NG/mot 2
Cycles NF/mot 2
None
Torque exceedance
TORQUE
None
Eng 1 exceedance
ENG 1
None
Eng 2 Exceedance
ENG 2
None
Page
71 / 262
FLIGHT DATA 3. Operating With The System
ACKNOWLEDGEMENT
“Acknowledge” (last page of the menu FLIGHT DATA)
Objective: check & acknowledge flight data
Crew member can provide data validation about each parameter mentioned of the flight (command Y/N ) then confirm by
pressing « Enter » inside the “Acknowledge” menu. Acknowledgement flag is then sent to the file already transferred in
PCMCIA.
It’s the way on board to process the “Lock” of the file. Then file locked cannot be modified any more
Eurocopter advise to do it on board after every session.
If the process is not done on board it should be done by the maintenance operator in front of the GSC during flight
downloading.
data Validation under processing
Acknowledge
Run
Validation done
Acknowledge
Validation fail
Done
Acknowledge
Fail
Page
72 / 262
ROTOR TUNING
3. Operating With The System
• Rotor Tuning on MR
Determine main rotor adjustment to optimise vibration level in 1, 2 , 5  for processing adjustment on weight,
pitch rods, tabs angles
• Flight Configurations in MR tuning
FPOG:
HOVER ground effect:
CRUISE 100kts:
CRUISE PMC:
low pitch with NR>245 rpm and Delta NR< 5rpm
Flight logic - ZRS < 50 ft - IAS hover < 50 kts
90 kts < IAS < 110 kts
IAS>130 kts
Minimum on rotor acquisition: One engine running
ROTOR TUNING
1.
Highlight « ROTOR Tuning » . Select Main Rotor then
Enter.
2.
Select configuration FPOG, then valid by pressing
« Enter », acquisition will be displayed few seconds later
Main Rotor
Tail Rotor
Main R-FPOG
RUN MAIN.R-100KT
Main R-FPOG
DONE
FAIL
MAIN.R-HOVER
MAIN.R-MCP
Acquisition in process
Result Acquisition
Page
73 / 262
ROTOR TUNING
3. Operating With The System
• Rotor Tuning on TR
Determine tail rotor adjustment to optimise vibration level in 1  and realise the weight adjustment for each blade on TR
One configuration possible : on ground
Regime : FPOG flat pitch on ground with NR > 245 rpm and Delta NR< 5rpm + Top validity presence
Minimum on acquisition: One engine running
ROTOR TUNING
1. Highlight menu « ROTOR Tuning » press « Tail Rotor »
then press « Enter ».
2. Select FPOG, then valid by pressing « Enter », Done
will appear few seconds later
Main Rotor
Tail Rotor
Tail rotor
TAIL.R
FPOG
Tail.R-FPOG
RUN
Tail.R- FPOG
DONE
FAIL
Selection
Acquisition in process
Result on acquisition
Page
74 / 262
ROTOR TUNING
3. Operating With The System
File transfer on
floppy
Value on acquisition
No threshold
: use AHMU for adjustment process
Page
75 / 262
ROTOR TUNING
Inside VPU
Function
Optimise rotor adjustment to obtain comfort on board without
any additional installation (maintenance job)
Washers added on tail rotor
Input Parameters
1 accelerometer bi-axis
Ground/Flight Logic
NR
Top RA
3. Operating With The System
41RK2
sol
245trs
Acquisition realised on accelerometers 41Rk2 synchronised on
TR pick up
If instability during acquisition: a message will be sent and
acquisition aborted
« acquisition impossible » or « fail »
If acquisition OK: VPU will compute amplitudes and phases
issued from signals accelerometer, a flag validity on phonic
wheel and MR magnetic pick up
Inside ACMS
Configuration :
1 acquisition recognised under IHM control menu : FPOG
Inside ACMS:
Identification
NR and ground configuration valid
Number of revolution to take to catch one acquisition on MR:
24 rpm
Acquisition will be done 5 times in a row before to provide the
result. Priority on VPU cycle
One acquisition stored only : the last one
On ground
Results will be identified after a manual transfer without shutting
down the engines.
For any correction to be applied use Steady Control Rotor
application
Rotor tuning /Main Rotor
On IHM, a message “Run “then ”Done” or “Fail” will follow
acquisition result
Ground Station
Rotor Tuning/ Main rotor.
Y and Z amplitude levels monitored.
Amplitude in “ips”
No threshold , no adjustment proposal under GSC application
Possibility to transfer rotor data afterwards on floppy disk
Page
76 / 262
ROTOR TUNING
3. Operating With The System
acquisition Value
No threshold
: use AHMU for rotor adjustment
Page
77 / 262
DATA TRANSFER
3. Operating With The System
Data transfer monitoring
Transferring data remains an automatic operation. A« manual transfer » can be done by the operator through IHM control unit.
In automatic : when Ng and NR parameters pass under the defined threshold. All data are transferred to PCMCIA card
During transfer phase « Data Transfer » will be displayed to the crew until done is done.
Following messages can be displayed on IHM
Transfer activated
Transfer
Transfer realised
Run
Transfer
Failure during transfert
Done
Or
Transfer
Fail
For any reason a session not downloaded automatically can be done manually
If this operation is not done, a packed flight will be recorded on board at next start
If fail message appear after transfer operation:
Get in menu « Data Transfer” and activate « ENTER »
Page
78 / 262
MARMS GSC
3. Operating With The System
M‘ARMS Ground Station Computer : GSC
GSC software is working under Windows Server 2003 associated to SQL server 2000 software
PCMCIA unit to download data
DAT driver to make back-up and restore database
GSC purpose is to collect data from flight to save them on mirroring drive
Software GSC version V 5.1 called “Groundstation” has been defined by ECF . Its purpose is
- to give access to different groups of work (crew, maintenance, expert, administrator)
- Store data coming from one aircraft or fleet of aircrafts
- Display flight report (where all usage data will be displayed: alarms, exceedance in flight domain)
- Inform operator on health acquisitions overshooted on main mechanical components
- Print and keep history flight report and maintenance message
- Provide rights to administrator to modify settings inside GSC (threshold modification, new users, new
groups creation )
Page
79 / 262
MARMS GSC
3. Operating With The System
M‘ARMS Menu
Page
80 / 262
MARMS GSC 3. Operating With The System
DOWNLOADING
At downloading .225 and raw present on PCMCIA card a consistency : A/C identification, compliance session date & GSC date,
PIN code identification.
• Files not acknowledged on board will be locked on GSC
• A flight report will be delivered.
Flying time, operating time and landings, engines cycles, exceedances, alarms detected during flight and engines power
check .
Any exceedance detected by ARMS will be compared to raw file
To update usage and health counters on the different parts monitored it’s necessary to pass by flight analysis .
After analysis operator will be driven by maintenance message:
Apply work cards MMA chap.45
Confirm overshoot by using raw file
Use communication form with ECF technical support
Page
81 / 262
FLIGHT REPORT
A/C Family
3. Operating With The System
A/C Reference
Engines
Date and starting session
Airframe
Page
82 / 262
MAINTENANCE 3. Operating With The System
REPORT
MAINTENANCE ACTION
Maintenance report will be the result of the flight analysis.
Each message monitored will be linked with a work card associated.
Each message identified by session date are classified in 3 categories: usage, system and health
Purpose: Produce to maintenance operator the work card reference
Messages can be acknowledged after checking
maintenance Messages
Maintenance
Report
Page
83 / 262
DISCREPANCY 3. Operating With The System
REPORT
System : MARMS
 Fault report-DR
Customer :
Customer ref.:
Page : 1 / 1
Modification request
Report / Request :
Official Link: DR
EC ref.:
Test site :
A/C tail number :
Concerning a problem: airborne or
ACMS-C S/N & S/W version :
GSC S/N & S/W version :
software, equipment module as
EMU S/N S/W version :
DSP S/N & S/W version :
MFDAU, VPU, EMU, GSC ...
FDAU S/N & S/W version :
Date & Flight report # :
Problem description :
Writer :
Approved by :
Visa :
Visa :
Transmitted to EC the :

EC answer :
Units involved :
Evolution decided?
By FAX :
Yes
No
Evolution description :
S/W evolution :
Availability :
Writer :
Approved by :
Visa :
Visa :
Transmitted to Customer the :

By FAX :
Page
84 / 262
DIAGNOSTIC 3. Operating With The System
REPORT
Official Health form: EDR
Usage or Health overshooting on a red or
amber threshold, abnormal Trend
detected on a component
Brice.fernando@eurocopter.com
Alexandre.diaz@eurocopter.com
Jean-sebastien.menaspa@eurocopter.com
Tel : 04.42.85.99.25
Tel : 04.42.85.17.04
Page
85 / 262
NOTES
Page
86 / 262
4. Usage Analysis
OPERATING TIME
FLYING TIME
FLYING TIME & LANDINGS
NR CYCLES
TORQUE CYCLES
ENGINE EXCEEDANCE
NR EXCEEDANCE
TORQUE LIMIT MONITORING
ENGINE POWER ASSURANCE CHECK
Page
87 / 262
4. Usage Analysis
OPERATING TIME
Function
Pilot Confirmation
yes
- accurate time for maintenance calculation
- Consistency check with flying time computation
- Provide low temperature flag information for special flight
conditions
Flight Report
Duration in operating Time
OAT at take off ( ***** ex: PF or after crank or engine washing)
Input Parameters
OAT
N11 et N12
NR
Signal source
A429 APM
Arinc Fadec
Phonic wheel
Maintenance Message
In case of pilot disagreement > 3° “System message”
Ground Station
Operation
Take in account time at first engine starting :Tf0
Take in account temperature at take off: OAT
Take in account time at last engine shut down: Tff
Affect operating time counters to parts.
Cumulated operating time since beginning.
Time in operation = Tff_- Tf0
Invalidity on OAT if flight condition not activated (ground run).
Message « invalidity » on this parameter will be recorded on this
session
Page
88 / 262
4. Usage Analysis
OPERATING TIME
End of Session
Start of Session

 N11 or N12 > 5%
N11 and N12 < 5%
N1_1
N1_2
NR
 with NR < 85 rpm
T running = Tf end - Tf init
Session will start: at first engine starting (NG < 5%) and close at last engine shut down (NG < 5% et NR <85 rpm)
Page
89 / 262
4. Usage Analysis
FLYING TIME
Function
Flight Report
Duration
Landing Number
Helpful for TBO and SLL
Accurate time computation
Record the number of landings
Input Parameters
Flight/ground Logic
Weight
Signal source
Discrete train
A 429
Operation
Computation flying time by storing starting flying time and
end flying time :
Flying Time =  (Tf take off – Tf landing)
On each take off it will be stored max weight to estimate
time in overload
Implement landing counters after each landing
Pilot Confirmation : yes
Maintenance Report
In case of pilot disagreement “System message “
”Airborne time has been declared faulty” if t >5mn.
“Landing count has been declared faulty” if =+/-1
«Flight in overweight: duration xxx »
Ground Station
Displayed time and landings
Under « Usage »/ Airframe/Time : Counters Access to total
« Flying time » and « Landings » monitored.
Flying time cumulated or by session
Landing numbers cumulated or per session
Page
90 / 262
4. Usage Analysis
FLYING TIME &
LANDINGS
Time spent in flight
By session
Counter cumulated
Landings session
and cumulated
Page
91 / 262
NR CYCLES
4. Usage Analysis
Function
Recording NR cycles to determine spectrum domain.
Can be used for manufacturer for mechanical parts
expertise
Input Parameters
Phonic wheel
Signal Source
NR
Operation
Detect NR regime to compute NR cycles
NR cycle=1 when NR pass over a threshold max and
pass lower a threshold min
Compute and store session cycles
Flight Report : none
Maintenance Report
“Reasonableness check failure, NR cycle <= 0 has been
detected”.
Ground station
Tab « USAGE »/ Airframe / NR cycles
Historic Check on NR cycle (session and cumulated)
Page
92 / 262
RPM
NR CYCLES
4. Usage Analysis
400
350
300
NR_cycle_max = 245 rpm
250
200
NR_cycle_min = 220 rpm
150
100
50
NR cycle = 1
0
Time
Page
93 / 262
TORQUE CYCLES
4. Usage Analysis
Function
Recording TQ cycles to determine spectrum domain.
Can be used for manufacturer for mechanical parts expertise
Input Parameters
TQ1, TQ2: Engine Torque
Signal Source
A429 VMS
Operation
Detect TQ regime to compute TQ cycles
Cumulated Cylces
One torque cycle is defined when pass over a threshold max
and pass lower a threshold min
Compute and store session cycles
Torque Cycle For The Session
Flight Report : none
Maintenance Report :
“Reasonableness check failure, NR cycle <= 0 has been
detected”.
Ground station
Tab « USAGE »/ Airframe / TQ data
Historic Check on TQ cycle (session and cumulated)
Page
94 / 262
Engine Torque (%)
TORQUE CYCLES
120
4. Usage Analysis
Torque
HOVER
100
CRUISE
80
TQ_cycle_max = 70 %
60
40
TQ_cycle_min = 30 %
20
FPOG
Torque cycle = 1
0
Time
Page
95 / 262
4. Usage Analysis
ENGINE
EXCEEDANCE
Function
Maintenance Report
Maintenance Message if pilot disagreement
“Eng N° xx N1cycle count has been declared faulty” or
“Eng N° xx N2cycle count has been declared faulty”
Automate cycle counting on NG and NF cycle:
getting accurate counting
evaluate next inspection on
Input Parameters
N11/N12 (NG) cycle
N21/N22 (NF) cycle
Signal Source
A429 Fadec
A429 Fadec
Ground Station
USAGE/ Engine1or 2 /Engine damage
cycles counters N1 and N2 displayed session/cumulated
Operation
N1 and N2 cycles taken from Fadec computers:
4 counters per engine
N1 cycle session = N1 cycle end - N1 cycle end
N2 cycle session = N2 cycle end - N2 cycle start
Flight Report
N1/ session
N2/ session
By session
Cumulated
Page
96 / 262
ENGINE
EXCEEDANCE
4. Usage Analysis
Page
97 / 262
NR EXCEEDANCE
Function
Detect and measure NR exceedance to determine
maintenance operation.
This value can be acknowledged by the crew
Input Parameters
NR
Signal Source
NR phonic wheel
System in operation
Each NR exceedance duration will be identified and stored
following NR max conditions
- NR max value for NR>310 rpm
- NR min value for NR<290 rpm
4. Usage Analysis
Maintenance Report
“Main Rotor Overspeed has been detected » with NR max
displayed.
Message classified in Usage in case of pilot disagreement
‘’NR max value has been declared faulty”
Ground Station
Tab Usage/ Airframe/NR exceedance
Session and cumulated.
Flight Report : yes
-time
-duration
-max value
Pilot: on Max value
Page
98 / 262
NR (rpm)
NR EXCEEDANCE
4. Usage Analysis
400
NR high = 310 rpm
310
290
NR low = 290 rpm
200
NR exceedance duration
0
Time
Page
99 / 262
TORQUE LIMIT
MONITORING
Function
Detect and measure TQ exceedance to introduce maintenance
actions following flight configuration and power transmitted on the
mechanic (MRP et TR)
Input Parameters (Arinc line VMS)
Torque threshold in OEI
Torque threshold in MTP
Torque threshold in climb 1
Torque threshold in climb 2
Torque threshold in Cruise
IAS Threshold in MTP
IAS Threshold in climb 1
IAS Threshold in climb 2
TR position for torque limitation
Value
95 %
104,6 %
103,6 %
102,7 %
100,5 %
45 knts
57 knts
70 knts
80 %
Operation
Store exceedance under 4 ranges in OEI and 11 in AEO and
for each exceedance (OEI, MTP, Spot Turn, CLIMB, CRUISE)
IAS , TR position, TRQ max value and duration
4. Usage Analysis
Flight Report : yes
Time, configuration Type, Max Value reached/duration
Maintenance Report :
Case of exceedance: « Overtorque has been detected”
In case of pilot disagreement on TQ value:
” TQ exceedance max value has been declared faulty ”
“TQ exceedance duration has been declared faulty ”
Ground station: «Usage/airframe/ TQ exc
Page
100 / 262
4. Usage Analysis
TORQUE (%)
TORQUE LIMIT
MONITORING
110
Torque limit in AEO
MTP
105
CLIMB 1
SPOTTURN
CLIMB 2
CRUISE
(Tr Position)
100
95
90
IAS (kts)
85
0
20
40
60
80
100
REGIME DEFINITION
MTP
SPOT TURN
CLIMB 1
CLIMB 2
CRUISE
Tq > 104,6 % IAS < 45 kts
Tq > 104,6 %
TR position < 80 %
IAS < 45 kts TR position > 80 % (action on yaw pedals )
Tq > 103,6 % 45 knts <IAS < 57 kts
Tq > 102,7 % 57knts <IAS < 70 kts
Tq > 100,5 %
(Climb MTP)
(Transitory flight)
(Transitory flight)
IAS > 70 kts
Page
101 / 262
4. Usage Analysis
ENGINE POWER
ASSURANCE CHECK
EPC Function (engine power check)
Provided by VMS.
ACMS module collect results and output parameters from
VMS and Fadec
Acquisition Parameters
N1
N2
TRQ 1+TRQ2
OAT
Marg TOT 1/2 Fadec
Marg TRQ 1/2 Fadec
TOT 1 + TOT 2
IAS
ZB
Source
Fadec
Parameters provided by VMS
Marg TOT1
corrected T4 margin1
Marg _TRQ1
corrected TQ margin 1APM
EPC1_STAT
status EPC eng1
EPC2_STAT
status EPC eng2
Marg TOT2
corrected T4 margin 2
Marg _TRQ2
corrected TQ margin 2
Aircraft Configuration
Air intake closed
VMS is checking that EPC conditions are required before to send
the command to Fadec to compute engine margins
Once the computation is done each Fadec sends back a
transmission status message 5 times in a row
- If one engine doesn’t mix VMS conditions a message « EPC
invalid » will be displayed .
- If one parameter is not valid a message « EPC not available »
will be displayed.
- If a EPC is requested with Air intake opened; a message bleed
valve opened will be displayed
During acquisition phase MFDAU/ACMS is monitoring the status
messages « EPC STAT_VMS » and « EPC Trans FADEC» .
Both engines are monitored independently
20 EPC (2 X10) per session max
CSM request
Demande
CSM
VMS
0
Status VMS
Status VMS
(EPC_TRANS) (EPC_Stat_VMS
VMS/ Fadec
60
80
Stab Phase VMS
90
S
Margin computation
by Fadec
paramètres calcul + marges
Computation Margin
Fadec 5X
by VMS
Margins computation VMS
5X
Page
102 / 262
4. Usage Analysis
ENGINE POWER
ASSURANCE CHECK
Display in flight report
Trend in TOT and TRQ
TQ Margins
2
EPC Eng 1 under Health
TOT Margins
1
Page
103 / 262
NOTES
Page
104 / 262
5. System Analysis
ALARMS
SYSTEM STATUS
Page
105 / 262
ALARMS
Maintenance Report
Yes if chip detection on MGB /TGB /IGB / Engines
Message : «Oil debris has been detected on P/N ..S/N… »
Function
Stores and displays alarms displayed in flight to:
- Identify failures to analyse discrepancies
- Help for maintenance
- Confirm Pb appear during the flight
Input Parameters
Chip detection
Red Alarms
Logic ground /flight
5. System Analysis
Source
discrete
MFDAU
discrete
Ground Station
Aircraft Status (Warning /failure) for alarms appeared during
flight.
- Duration
- Occurrence
System Status ( minor/major defects) for any equipment failure
Activation Condition
Starting Activation start /end session for chip detection for a
discret status >5s (logic Flight/ground not taken into account)
Activation for all the others failures only in flight configuration
Each failure can be record no more than 3 times.
Each one will be identified (date start , date end)
Flight Report : yes
Number of alarms and occurrences appeared in flight
Page
106 / 262
ALARMS
5. System Analysis
Click« Aircraft status » alarms displayed
« Failures » and « Warnings »
FAILURES
Maintenance report
(ex: chip detection)
WARNINGS
Page
107 / 262
SYSTEM STATUS
5. System Analysis
Displayed major and minor defects appeared in flight
Major defects
Minor defects will be stored over 30’ flight
Minor defects
Page
108 / 262
NOTES
Page
109 / 262
6. Health Domain
HEALTH GENERALITY
SIGNAL TREATMENT
Page
110 / 262
6. Health Domain
HEALTH GENERALITY
VIBRATION
MONITORING
ENGINES
LEFT
Engine Power up
Engine Stabilized
MGB
RIGHT
Engine Power Up
Engine Stabilized
TGB
GEARS / BEARINGS / SHAFTS
TDS
ROTORS
MAIN
- Balance
- Tuning
TAIL
- Balance
- Tuning
Page
111 / 262
HEALTH GENERALITY
6. Health Domain
An accelerometer delivers a signal representative of all vibrations registered in the vicinity of its attachment. This signal contains
information from gears, shafts and bearings in close proximity: this will define the ACCELEROMETER RAW vibration signal.
To identify the vibration signal of each element, a signal from phonic wheels (toothed wheel associated with a sensor delivering a
pulse with each passage of tooth) is used to obtain its own rotation speed. With this information, the vibration signal of each
element could be extracted from the raw signal and will elaborate the vibratory SIGNATURE.
Page
112 / 262
SIGNAL TREATMENT
6. Health Domain
Signal Treatment
The Signal issued from the accelerometer will be sampled to obtain a number of points constant per shaft revolution and this
whatever the variation speed : This is called synchronous sampling average
NF phonic wheel (1or 2) will be the reference for the synchronous sampling: For each Rpm we will take a number constant of
points.
This reference should be in phase with the different reduction rate of the train drive shaft.
The synchronous average
Synchronous average is composed of: signature of the shaft monitored + signals issued from the other shafts around
Sampling will be done following a number of revolution known by the system. Noise will be erased from the shaft signatures
Mesh frequency is not a perfect multiplier of the shaft period.
Conclusion: Synchronous average will allow to filter the signal in order to obtain a revolution of a shaft removed from its noise
around
Page
113 / 262
6. Health Domain
SIGNAL TREATMENT
Signal Interpolation
Signal of the phonic wheel
5
Phonic wheel NF
4
3
2
1
Multiplier
0
0
5
100
200
300
400
500
600
700
800
100
200
300
400
500
600
700
800
100
200
300
400
500
4
The signal is multiplied to obtain a number of tops equal to
numbers of points requested
3
2
1
0
10
0.5
Superimpose to the accelerometer signal to the multiplier
of tops.
0
0
-0.5
This is called signal interpolation
600
700
800
sampling
points
-1
Accelerometer signal
Page
114 / 262
SIGNAL TREATMENT
6. Health Domain
Synchronous average
N signaux/ N
Page
115 / 262
SIGNAL TREATMENT
6. Health Domain
Fast Fourier Transform
Fast Fourier Transform FFT is a treatment of the signal : Breakdown of the signal in sinusoids amplitude and frequencies different
in order to identify the frequencies of a part monitored
It’s the graphic representation in harmonics in the frequencial domain.
One revolution
of the part monitored
FFT Spectrum
Fundamental (Harmonic 1)
Harmonic 2
Harmonic 3
Page
116 / 262
6. Health Domain
HEALTH GENERALITY
1.5
1
1
0.5
0.8
0
0.6
OM-1
OM-5
-0.5
0.4
-1
0.2
-1.5
0
10
20
30
40
50
60
70
80
90
0
100
0
5
10
15
Temporal Signal
20
25
30
35
40
45
50
FFT Spectrum
1
0.8
0.6
0.4
0.2
0
-0.2
-0.4
-0.6
-0.8
-1
0
10
20
30
40
50
60
70
80
90
100
Page
117 / 262
NOTES
Page
118 / 262
7. Health Monitoring
MAIN ROTOR
TAIL ROTOR
GEARS
SHAFTS & TRANSMISSIONS
BEARINGS
ENGINES
Page
119 / 262
MAIN ROTOR
Function
Detect and anticipate defects on MR by monitoring indicators
to check daily health on rotor and its harmonics.
Input Parameters
Magnetic pickup
NR rotor threshold
IAS cruise threshold
ZB altitude
Ground /flight
accelerometer bi-axis
Source
1 top per rev MR
>245 rpm
>125 knts
 ZB<50ft
Discrete
41K1valid (y and z)
Configuration
2 configuration identified :FPOG and Cruise
FPOG : NR>245 rpm with NR< 5trs
CRUISE: stabilized with IAS 125knts and IAS<25knts with
NR>245, NR< 5trs and ZB<50ft.
- Accelerometer will be synchronised on MRP magnetic
pickup.
Number of rpm on rotor to acquire acquisition RP:24rpm
Acquisition magnetic pickup will provide rotor frequency (time
computed ) to define rotor speed
92% <Time computed <103 % (100%=365rpm)
Harmonics: 1 , 2 , 5 ,10 .
Priority on this acquisition: interruption of VPU cycle
7. Health Monitoring
Inside ACMS
- Check during acquisition signal stability for more than 5 ’’
FPOG: flight/ground = ground and NR>245rpm+/- 5rpm
Cruise: Zb stabilised ( Zb) <50ft and IAS stabilised > 125knts
Then the command is sent to VPU
Inside VPU
Acquisitions done for 24 rpm rotor with magnetic pick-up
5 acquisitions max per session per configuration
Inside MFDAU-ACMS
- Compute NR average and stability during acquisition
If data are instable during acquisition, this one will be
interrupted.
ACMS receive a validity from the VPU :store on acquisition can
be performed and result including time and NR average
Maintenance Message
Exceedance on Health Indicators:
“indicator OM1 has exceed its amber threshold on MR”
No data monitoring over 5 hours
-“MR is not monitored for > 5hours “
- if no acquisition on MR with a flying time > 30mn
“Check accelerometer MR04/MR05 and Main Rotor Top” in
minor defect
Page
120 / 262
MAIN ROTOR
7. Health Monitoring
Start acquisition NR average
flight configuration
Numbers of acquisitions par session: 5 max
Health /MR/ Balance Monitoring in ground and flight configuration
Health Graphic extraction
(ips en Y et Z harmonics in OM1,OM2,OM5,OM10)
Fixed threshold on indicators OM1(red and amber) and OM2
(amber)
Ground configuration
Page
121 / 262
TAIL ROTOR
Function
Detect and anticipate defects on TR by monitoring indicators
to check daily health on TR and its harmonics
Input Parameters
Magnetic pickup
NR rotor Threshold
IAS cruise
ZB altitude
Flight /Ground
Accelerometer
1 top per rev TR
>245 rpm
>125 knts
 ZB<50ft
Discrete
bi-axis 41K2 valid
axis y et z
Configuration :
2 configurations :FPOG and Cruise
FPOG : NR > 245 rpm with NR< 5trs
CRUISE: stabilized at IAS 125knts and IAS<25knts with
NR>245 and NR< 5trs ( ZB<50ft)
-Accelerometer signal will be synchronised on TR magnetic
pickup
Number of rpm on rotor to acquire acquisition RP:24rpm
To validate acquisition magnetic pickup will provide tail rotor
frequency to compute rotorspeed
92% <Time computed<103 % (100%=365rpm)
Harmonics: 1 ,2 ,4
7. Health Monitoring
Inside VPU
Acquisition done for 24 rpm on TR
No more than 5 acquisitions per session
Inside ACMS
-Compute NR average and stability during acquisition
If data instable acquisition will be interrupted
ACMS receive a validity from VPU and store results as time
and NR average
Maintenance Message
Health overshooting detected:
“ indicator OM1 has exceed its amber threshold on TR”
No vibration monitoring on TR over 5 H
“TR is not monitored for > 5hours “
-if no acquisition on MR with a flying time >30mn
« Check accelerometer TR and tail rotor top » in minor
defect
Inside ACMS
- Check during acquisition signal stability for more than 5’’
FPOG: flight/ground = ground and NR>245trs +/- 5trs
Cruise: Zb stabilized (Zb) <50ft and IAS > 125knts
Then order is sent to VPU
Page
122 / 262
TAIL ROTOR
7. Health Monitoring
TR monitoring in flight
GSC:
Health /MR/ Balance Monitoring in ground and flight
configuration
Health graphic extraction des signaux MR en indicateurs santé
(ips in Y and Z in harmonics 1, 2,4)
-Threshold monitoring in learning period
Numbers, start time and NR average on acquisition
TR monitoring on ground
Page
123 / 262
GEARS
7. Health Monitoring
Function
Anticipate on gears deteriorations MGB,IGB,TGB
No acquisition on ground
Parameters
For VPU
identify sensor validity for acquisition
Phonic wheel NF1or 2
Ratio between phonic wheel and gear monitored
10 accelerometers valid (8 on BTP, 1 on BTI, 1 on BTA)
For ACMS:
TR position
TRQ1+TRQ2
flight/ground logic
Operation
Included in VPU cycle
2 conditions requested
For IGB and TGB gears: flight and TR position> 70%
For MGB gear: flight and TRQ1+TRQ2> 45%
-Acquisitions are realised based on 10 accelerometers tours
Following gears number of rpm could be different
(48rpm, 100rpm or 200 rpm )
If acquisition rejected: VPU follows up next one
-5 acquisitions max stored in MFDAU.
(Acquisition recorded with 30 mn interval)
If flight logic is lost interruption on acquisition.
Maintenance Report
Exceedance on a health indicator for a gear monitored.
“ indicator “XX” has exceed its amber threshold on LH
first reduction pinion”
No data over 5 hours
“LH double pinion is not monitored for > 5hours“
“Check accelerometer xx and the corresponding VPU treatment”
GSC
date
Time for each acquisition
signal accelerometer for the gear monitored
Average (TRQ1+2) or Tr position displayed
Indicators affected:
OM1, OM2,nOM, MOD,RMS,RMSR, Km, Kr, Kg
.
Page
124 / 262
GEARS
7. Health Monitoring
Signal issued from computation
Convertion in FFT
(harmonics)
Page
125 / 262
SHAFTS &
TRANSMISSIONS
7. Health Monitoring
Function
Anticipate on gears deteriorations shafts and bearings on TDS
No acquisition on ground
If acquisition rejected, VPU follows up next one
-5 acquisitions max stored inside MFDAU.
(Acquisition recorded every 30 mn interval )
If flight logic is lost interruption on acquisition
Parameters
For VPU
Identify validity of the sensor requested to acquire acquisition
Phonic wheel
Numbers of revolution
Ratio between phonic wheel and shaft monitored
6 accelerometers valid (1 per shaft)
For ACMS:
TR position
Flight /ground logic
NF1 or 2
200trs
Maintenance Report
“ indicator “XX” has exceed its amber threshold on
TRD forward shaft element”
If no data from more than 5 hours, following message sent :
“TRD center shaft 3 is not monitored for >5hours “
“Check accelerometer xx ”
Ground Station
-harmonic monitoring in OM1 and OM2
Time on Acquisition
Accelerometer signal on 200 rpm
TR position during acquisition
Operation
Including in VPU cycle
Condition: flight/ground = flight and TR pos >70%
Acquisition on 200 rpm on the shaft monitored.
Page
126 / 262
SHAFTS &
TRANSMISSIONS
7. Health Monitoring
Health SPECTRUM
OM1 monitoring
Shaft n°3 health monitoring
Page
127 / 262
7. Health Monitoring
BEARINGS
Function
Inside VPU
Control and Anticipate on bearings problems to avoid bigger
damage on the mechanic around
Synchronous sampling on 4 or 8 rpm.
Parameters
For VPU
identify validity of the sensor requested to acquire acquisition
Phonic wheel
NF1 or 2
Numbers of revolution
200trs
Ratio between phonic wheel and shaft monitored 128/256pts rpm
17
accelerometers
For MFDAU/ACMS:
TRQ1+TRQ2
TR position
Flight/ground logic
Maintenance report
No message because no threshold on bearings
If no data for more than 5 hours :
“TRD Bearing 4 is not monitored for >5hours
if no data on a bearing with flight time >30mn
“Check accelerometer xx »
Ground Station:
Associated indicators : FI, FE, M6, RMS, H2FE.
Operation
Belong to VPU cycle
Recognising configuration:
For IGB and TGB bearings: flight and Tr pos> 70%
For MGB: Flight and TQ1+TQ2> 45%
For MRH bearings : Flight and IAS> 125 knts
Inside ACMS
Acquisition identification to be done according VPU cycle. If
TRQ1+TRQ2 or RA pos or Vi above limit, acquisition will be
expected
Page
128 / 262
BEARINGS
7. Health Monitoring
Page
129 / 262
BEARINGS
7. Health Monitoring
Function
Optimise rotor adjustment to obtain comfort on board without
Any adding maintenance job
-Weight on sleeves
- Pitch rods adjustment (yellow fixed)
-Tabs angle on blades (2 only ajustables)T8 and T9
Input Parameters
Magnetic Pickup
NR rotor
IAS cruise threshold
ZB altitude
Flight/ground position
6 axis required
1 per rev
>245 rpm
>125 knts
ZB<50ft
Discrete
(40Rk,41Rk,42Rk)
Configuration :
4 configuration recognised by ACMS on pilot action
FPOG
Hover
100knts
MCP
Inside ACMS:
Identify configuration
Numbers of rpm to catch acquisition:24 rpm
Acquisition will be done 5 times in a row.
Priority on VPU cycle
Inside VPU
Acquisition realised on the 6 axis monitored (3 Acc)
synchronised on MGB magnetic pick-up
If configuration instable: a message is sent to IHM
« acquisition impossible » or « fail »
If acquisition correct : VPU will address results: amplitudes and
phases , a flag validity
Inside ACMS
One acquisition only will be preserved: the last one
On ground
Results will be analysed after a manual transfer through
Steady Control Rotor software located on AHMU
Ground Station
Rotor tuning /Main Rotor
Message “Run “then ”Done” or “Fail”
Monitoring on the 6 axis in ips
No threshold : no adjustment proposal
Transfer possibility through floppy disk
Page
130 / 262
7. Health Monitoring
ENGINES
Function
1. Per engine vibration level in NG and Nf at starting and
regime stabilized
Gas generator and free wheel unbalance
(Blades compressor damaging)
2. Recording parameters as EOT and TOT at starting
Vibrations N1 and N2 under 8 harmonics
Input Parameters
2 accelerometers per engine
N11,N12,N21,N22
flight/ground
EOT 1/2
TOT1et TOT2
valid
phonic wheel
discrete
Operation
Automatic Acquisitions following 2 phases:
1. Starting phase : condition N1> 20% (stop at 95 %N2)
VPU will be activated and acquisition gets the priority on the
cycle
2. In regime stabilize: Flight condition N1> 84 %.
4 acquisitions max stored
Output
Flight report : No
Pilot Confirmation : No
Maintenance Report :
Alert message
Ground Station
Graphics in mm/s on engine in N1 and N2 in each
phase considered
At interval following VPU cycle .
Acquisition collected under 2048 points
Page
131 / 262
ENGINES
7. Health Monitoring
Engine spectrum at Power up
In Stabilized
mode
Page
132 / 262
NOTES
Page
133 / 262
8. Ground-Station Computer
DESCRIPTION
SOFTWARE INSTALLATION
SOFTWARE ARCHITECTURE
USER GROUPS MANAGEMENT
ACCESS
AIRCRAFT TEMPLATE
AIRCRAFT CONSTRUCTION
COMPONENT MANAGEMENT
DOWNLOAD CARD
FLIGHT REPORT
MISSING FLIGHT
FLIGHT ANALYSIS
UTILITIES
AIRCRAFT STATUS
SYSTEM STATUS
SOFTWARE CONFIGURATION
USAGE FUNCTION
HEALTH FUNCTION
EXPORT AIRCRFAT
IMPORT AIRCRAFT
BACKUP / RESTORE
DATA TRANSFER
DATA CLEANER
Page
134 / 262
DESCRIPTION
8. Ground-Station Computer
Main GSC is fitted with various hard disks + mirroring disks (RAID Partition) and can manage a fleet of helicopters
containing 3 partitions
C:/ integrates OS Windows Server 2003 and Grounstation V5 application
D:/ integrates SQL server
E:/ integrates MARMS data & database
Grounstation version V5.1 will operate under SQL Server 2000 software
Components :
Driver PCMCIA, DVD rom , Floppy disk GSC acquires and processes data recorded by the MARMS computer in
flight.
Description
Act as administrator tool (manage rights, back-up/restore, missing flight can be generated)
Provide after each flight a flight report and store these data
Automate data back up periodically (once a week or daily on hard disk)
Possibility to download on a same GSC flights coming from different helicopters family
Update counters and health affecting them to the components monitored
Alert operator after a usage or health threshold overshooted by providing the work card associated
Page
135 / 262
DESCRIPTION
HARDWARE
• HP ML350 Proliant Server XEON G5
• Ecran 17’’
• RAM memory 1Go
8. Ground-Station Computer
SOFTWARE
- Windows Server 2003 US
Improve network capability: use
with VPN or remote access.
• 9 HD
• USB PCMCIA Reader
•DVD Burner Double Layer
• Hardware Key protection (Dongle)
• UPS power supply
• HP Printer LaserJet
• Modem (56 kbps)
- Microsoft SQL Server 2000
 Optimization for SQL query
execution.
 Automatic sizing of the
database.
Page
136 / 262
SOFTWARE
INSTALLATION
8. Ground-Station Computer
Installation Type
CD Rom is provided to customer.
Place CD and Autorun will be launched automatically to
install GSC application
Full Installation GSC + Database.
Ex: First installation
Update a new version or reinstall a new GSC
software.
Reinstall a new database
Page
137 / 262
SOFTWARE
ARCHITECTURE
8. Ground-Station Computer
 Architecture
Data Initialisation
Flight Data
Flight Session
Flying hours, landings,Cycles,
exceedances, Alarms,
Vibrations
Data from crew
Aircraft template for database
Usage data
Configuration Data
P/N
Flight Report
Aircraft
DataBase
GSC
S/ N
Counters (SLL; TBO,…)
Health indicators
Usage Data
Usage
Data
MMA
Maintenance
tasks
Page
138 / 262
USER GROUPS
MANAGEMENT
8. Ground-Station Computer
EQUIPAGE
Proposal List of groups
MAINTENANCE
EXPERT en ANALYSES
ADMINISTRATION
Page
139 / 262
USER GROUPS
MANAGEMENT
C
r
e
w
M
a
i
n
t
e
n
a
n
c
e
Download card
Flight report
E
x
p
e
r
t
+
Manually flight
(missing flight)
Flight analysis
Maintenance report
PCMCIA utilities
Operation
M
a
i
n
t
e
n
a
n
c
e
8. Ground-Station Computer
Aircraft Template
Aircraft status
Health
System Status
Usage
Rotor Tuning
Component Management
Import
A
d
m
i
n
i
s
t
r
a
t
o
r
Aircraft Construction
Access Control Management
Software Configuration
Data Cleaner
Backup / Restore
Data Transfer
Export
Log Book
Maintenance
Administration
Page
140 / 262
ACCESS
8. Ground-Station Computer
Connect GSC.
User : administrator with Password: groundstation
Open GSC by shortcut GSC V5 or by main menu Start /Groundstation.
Enter GSC User: “F0210” and password “000000”
Never remove F0210 from database; it’s an administrator user (ECF Ref)
Each user will enter its own password to get in the GSC
Page
141 / 262
ACCESS
8. Ground-Station Computer
5 groups defined by ECF as “User groups” by default.
Possibility to customize the Access control management to set all customers users (delete, create
groups and users)
A user created should belong to one of the group already created
Rights can be modified any time and updated
Administrator will get the rights to modify these following settings
Page
142 / 262
ACCESS
8. Ground-Station Computer
« User » creation
Generate a new user
Ex:“11” to “Line” group
Page
143 / 262
8. Ground-Station Computer
AIRCRAFT TEMPLATE
Hierarchic list containing all the Part numbers
This list has been defined by ECF (integrated inside GSC database)
ECF aircraft template cannot be modified. It should be duplicated before first aircraft creation
Ex: EC225/RESCO
List of Nodes and P/N

Page
144 / 262
AIRCRAFT TEMPLATE
8. Ground-Station Computer
For each P/N defined a list of counters are associated
- General information for the part monitored ( flying hours, cycles….)
Counters in Cumulative , SS counters (per session), and Health with indicators
monitored
These counters will introduce the maintenance messages associated
Counter Tab
Usage Tab
Health Tab
Page
145 / 262
AIRCRAFT TEMPLATE
Each component is monitored from counters defined
under its own aircraft template
So each P/N will be monitored differently in order to generate
the right maintenance messages
8. Ground-Station Computer

3 Counters type :cumulative, per session
- Cumulative Counters
- S&S Counters
- Health
Ex: Engine
counter list available
Assigned counters
Counters are covered by the aircraft template and only
an administrator can modify them
They will generate the maintenance messages inside the
maintenance report “usage system” or “health incident”
Page
146 / 262
AIRCRAFT TEMPLATE
Counters properties
8. Ground-Station Computer
Page
147 / 262
AIRCRAFT
CONSTRUCTION
8. Ground-Station Computer
File- New
You must set
His ID
His serial number
His pin code
His aircraft template reference EC225
Define its own counters
Screen divided in two parts
“Contents” Zone: contains P/N and aircraft template EC225
Message
will indicate a part missing. Any download will at
this level is not possible.
“Stock” Zone: parts available ready to be installed on aircraft
Page
148 / 262
AIRCRAFT
CONSTRUCTION
8. Ground-Station Computer
Page
149 / 262
COMPONENT
MANAGEMENT
8. Ground-Station Computer
S/N creation (component) following a P/N Possibility to
know stock (parts available, lend or in overhaul….)
A
B
A/ General : serial Number
B/ Counters initialized : to initialize
Page
150 / 262
COMPONENT
MANAGEMENT
8. Ground-Station Computer
After validation, a new serial number is created on the stock.
All component displayed on the stock represent all the part
available and ready to install on A/C.
Next processing :
Go to “Aircraft construction” in order to install all serial numbers
previously created.
Page
151 / 262
COMPONENT
MANAGEMENT
8. Ground-Station Computer
Removal operation
Install missing part
Page
152 / 262
DOWNLOAD CARD
8. Ground-Station Computer
Page
153 / 262
DOWNLOAD CARD
8. Ground-Station Computer
GSC realizing:
- Recognising aircraft pin code
- Detect automatically files “already downloaded“ and “unknown” files
- Configuration between airborne software version and GSC version
- Aircraft fitted with major components (in term of mechanical parts mandatory for flight)
- path to open files on PCMCIA card
- Consistency time check between : airborne time ACMS / GSC
Insert card PCMCIA inside DTU on GSC
Invalid Sessions
Already downloaded
Valid Sessions to be downloaded
Click “Download Card ”
List of sessions fitted on PCMCIA
All of them can be downloaded
Indication concerning: aircraft, type, session time
Only sessions
can be downloaded
Session Types possible :
Complete Session
Abbreviated Session
Page
154 / 262
DOWNLOAD CARD
8. Ground-Station Computer
Data to be checked
First flight coming:
Possible to introduce few data concerning the flight:
pilot, copilot, base names , flight number delivered
Data no confirmed on board
Data already confirmed on board
Example here: Flight not confimed on board
- At this level data can still be modified before to be locked
Locking data by action
File - Lock
Page
155 / 262
FLIGHT REPORT
8. Ground-Station Computer
“Flight Report”.
Access to flight reports recorded
Possibility : using File - Print command
Page
156 / 262
MISSING FLIGHT
8. Ground-Station Computer
Purpose: Update usage data inside database following missing flights
Consistency between aircraft counters and manuals data
Click on “Manually Entered Flights”
Introduce a session starting time
Mention values inside Crew columns
At beginning general indicator is marked by a red cross
Once values defined it will become green
Possibility to generate also a usage incident as NR, TQ or
Engine
“ File - Lock” to save missing flight created
Page
157 / 262
FLIGHT ANALYSIS
8. Ground-Station Computer
Maintenance message will be created following the flight analysis. Quite long when database is managing a lot of data
Analysis is mandatory to set all counters and update the database
Sessions already analysed or to be analysed
: Already Analyzed session
At the end of the analysis acquisitions levels will be compared
to threshold defined inside GSC (consigne EC725)
Two acquisitions exceeded on a window of five acquisition is
generating a maintenance message.
: Validated not analyzed.
Session/StartAnalyses.
-Analysis of a flight cannot be done is the flight report has
not been locked.
-GSC is checking if there is not discontinuity between last
flight analysis and the last one (if not a message will appear)
Possibility to acknowledge messages generated by applying command
« File-Acknowledge » in the main menu
Page
158 / 262
UTILITIES
8. Ground-Station Computer
Function: Delete files on PCMCIA card
Card inserted, use utilities command
Select files to delete
Then click on Delete button
Possibility to format a new card
Page
159 / 262
AIRCRAFT STATUS
8. Ground-Station Computer
Classified in 2 types
Failures appeared in flight
Warnings appeared in flight
Page
160 / 262
SYSTEM STATUS
Minor defects
8. Ground-Station Computer
HUMS System failures
Major defects
Page
161 / 262
SOFTWARE
CONFIGURATION
(1) : Specify the directory path of the drive for archiving the session(s) before download.
(2) : Lock flight data : locks the flight data after deleting card.
Stop : stops the downloading process (prohibits any report printing).
(3) : Print flight report : prints the flight report after data locking.
(4) : starts analysis of the flight data after printing of the flight report.
Stop : prohibits printing of the maintenance report.
(5) : Print maintenance report : prints the maintenance report after analysis of the flight data.
(6) : Discontinous session : ignore the discontinous session.
(7) : Continue : continue with flight data analysis for subsequent download of the next flight even
if those maintenance messages complied from the previous downloading has not been
acknowledged.
8. Ground-Station Computer
(1) : Data Cleaner function : used to modify the number of sessions to be kept in
memory.
(2) : BackUp-Restore-Data Transfer : used to modify the data transfer speed.
(3) : Edit and print gross weight(s) : used to specify the unit value for the weight (Kg or Lb).
(4) : Equipment failures analysis : used to modify the minimum flying time to take into
account the failures for equipment analysis and used to modify the minimum fliyng time to
generate amaintenance message.
Page
162 / 262
SOFTWARE
CONFIGURATION
8. Ground-Station Computer
Path to select PCMCIA card
Downloading procedure
Page
163 / 262
USAGE FUNCTION
8. Ground-Station Computer
Airframe
Landings
Flying Time
NR exceedance
Page
164 / 262
USAGE FUNCTION
8. Ground-Station Computer
ENGINE
N1 exceedance
TOT exceedance
N2 exceedance
Page
165 / 262
HEALTH FUNCTION
8. Ground-Station Computer
Reference in flying hours for the acquisitions monitored
Components in the list
Possible from maintenance message to activate the curve
Page
166 / 262
EXPORT AIRCRAFT
Access to « Export » menu
Select the aircraft
8. Ground-Station Computer
Select components to be exported
Transfer them in tempory zone
Export aircraft
Aircraft in tempory zone
Page
167 / 262
EXPORT AIRCRAFT
Select DAT
Clean tempory zone
8. Ground-Station Computer
Back up proceeded
Aircraft removed
from list
Page
168 / 262
IMPORT AIRCRAFT
8. Ground-Station Computer
Select “IE GS Euroarms”
Restore Result
then Restore
Import and select DAT
Page
169 / 262
BACKUP / RESTORE
8. Ground-Station Computer
Backup
Save data + database
Done automatically by SQL server (scheduled tasks)
weekly on Sunday 18h00 or manual through
application)
To realize before any modification to avoid any error
Restore : to update data or install a new database on
hard disk fitted on DAT band
Page
170 / 262
DATA TRANSFER
Insert DAT for backup data and database.
8. Ground-Station Computer
1
Select “Overwrite” or “don’t Overwrite”
Activate “Transfer”
Backup Function
Specificity: Possibility not overwrite last
database
2
3
Page
171 / 262
DATA CLEANER
8. Ground-Station Computer
1
This function will be used to cancel data in order to
get more speed on GSC
Sessions Number to clean in database
Valid with Clean
2
Only flights selected will be cancelled
3
Page
172 / 262
NOTES
Page
173 / 262
9. Ground Tools
AHMU
CVFDR KIT
CVFDR WIRING DRAWING
CVFDR DOWNLOAD & ANALYSIS
« .RAW » FILE
PMT SOFTWARE
VIBRATO SOFTWARE
ACCELEROMETER TEST
ACQUISITION COMMAND
ACCELEROMETER CALIBRATION
CMT SOFTWARE
STEADY CONTROL ROTOR SOFTWARE
Page
174 / 262
9. Ground Tools
AHMU
*
*
USB
COM1
*
703-AKCVFDR.00
CVFDR
552 VC
552 VC
PMT (s/w number: L03497-01-05)
Vibrato V3.1
PGS V3.5
NOT USED
ANYMORE
WITH USB
CVFDR KIT
*
*
*
MFDAU
FDR
MFDAU
HUMS
*
*
*
VPU
552 VC
CMT V006
Steady Control Rotor© V5.1
703-AKMFDAU.00
Page
175 / 262
9. Ground Tools
CVFDR KIT
On ground
Laptop
Laptop with PGS
Vision
On Board
FDRS
MFDAU
Aircraft
Sensors
+
SSCVFDR
+
Acquisition
unit
IHM
+
Crash
Recorder
Plug
+
+
Control panel
On board
connexion
Kit
CVFDR Function
USB kit
Downloading
19/06/2012
Page
176 / 262
CVFDR KIT
•
•
9. Ground Tools
Definition
Kit used to download and to display the
CVFDR data
Description
In the kit you must have:
– CTS USB MDU379 box (P/N 300-020000)
– Aircraft cable (P/N 703-A97-6832.00)
– USB cable for MDU379
– PGS Vision CD-ROM (V3.6 minimum)
– Driver CD-ROM for MDU379 box
– Database file
•
This Kit can be used with any laptop with windows XP or Windows Server 2003
Page
177 / 262
CVFDR WIRING
DRAWING
19/06/2012
9. Ground Tools
Page
178 / 262
CVFDR WIRING
DRAWING
19/06/2012
9. Ground Tools
Page
179 / 262
CVFDR DOWNLOAD &
ANALYSIS
Step1:
(Fig. 1)
9. Ground Tools
To perform a download of the
SSCVFDR, you need, first of all and
by order, to:
(1)
(2)
- Switch on the laptop,
- Plug the dedicated wiring on the
helicopter (1) and after on CTS box
(2).
- Switch on the helicopter,
(3)
- Connect the CTS kit (3) on the
laptop (4).
(4)
Then, after go to “Step2”.
- Fig. 1 -
Page
180 / 262
CVFDR DOWNLOAD &
ANALYSIS
Step2:
(Fig. 2)
9. Ground Tools
Once you are logged on, double Click
on PGS Vision icon to open PGS
software.
Then, after go to “Step3”.
- Fig. 2 -
Step3:
(Fig. 3)
Go to menu “Databases” (1) and
select “Database Manager” (2).
(1)
(2)
Then, after go to “Step4”.
- Fig. 3 -
Page
181 / 262
9. Ground Tools
CVFDR DOWNLOAD &
ANALYSIS
Step4:
(Fig. 4)
Directly click on “Load” (1).
Then, after go to “Step5”.
(1)
- Fig. 4 -
Step5:
(Fig. 5)
To download SSCVFDR, the
database to be used must be the
one named “EC225_01_a.arb”* (1)
which contains all parameters.
Select it, make sure that it is active
on file name (2), and open it (3).
Then, after go to “Step6”.
* PGS databases are located on C:\Program Files\PGS\Database
(1)
(2)
(3)
- Fig. 5 -
Page
182 / 262
CVFDR DOWNLOAD &
ANALYSIS
9. Ground Tools
(1)
Step6:
(Fig. 6)
The name of the database you have
selected is displayed on the window
topic (1).
Then, after go to “Step7”.
- Fig. 6 -
(1)
(2)
Step7:
(Fig. 7)
Go after to menu “ReadOut” (1) and
select “Crash Recorders” (2).
Then, after go to “Step8”.
- Fig. 7 -
Page
183 / 262
CVFDR DOWNLOAD &
ANALYSIS
9. Ground Tools
(1)
Step8:
(Fig. 8a)
Before downloading the SSCVFDR,
make sure that the CVFDR type is
correct. To do so, click on “Select
FDR” (1) and…
- Fig. 8a -
(1)
(Fig. 8b)
…choose the type “980-6021-066”
(1) and validate by “OK” (2).
(2)
Then, after go to “Step9”.
- Fig. 8b Page
184 / 262
CVFDR DOWNLOAD &
ANALYSIS
Step9:
(Fig. 9a)
9. Ground Tools
You can now start the downloading
process; to do so, click on
“Download” (1) and wait until the
process has been fully completed.
(1)
- Fig. 9a -
(Fig. 9b)
- Finally, you will have a message
telling you if the download has been
correctly done or not. After to
analyse the flight, you just need to
go to menu “Flight” and choose
“Open Flight”.
- Fig. 9b Page
185 / 262
9. Ground Tools
CVFDR DOWNLOAD &
ANALYSIS
(1)
(2)
(3)
(4)
“Open Flight” (1) , select the file (2)
and click on “Open” (3) .To select
additional parameters, click on the
associated icon
and choose the
parameters you want to display (4) .
Page
186 / 262
9. Ground Tools
CVFDR DOWNLOAD &
ANALYSIS
(1)
(2)
(3)
(4)
Page
187 / 262
« .RAW » FILE
Step1:
(Fig. 1)
9. Ground Tools
Double Click on PGS Vision icon to
open PGS software.
Then, after go to “Step2”.
- Fig. 1 -
(1)
Step2:
(Fig. 2)
Go to menu “Databases” (1) and
select “Database Manager” (2).
(2)
Then, after go to “Step3”.
- Fig. 2 -
Page
188 / 262
« .RAW » FILE
Step3:
At this level, you have 2 possibilities:
(Fig. 3a)
- Either the correct database has
already been imported (1), then you
can directly go to “Step5”.
9. Ground Tools
(1)
- Fig. 3a -
(Fig. 3b)
- Either the database has not been
imported, then you have to do it. As
a result, click on “New” (1), and
select “Import” (2) in order to choose
the correct database. Then, after go
to “Step4”.
(1)
(2)
- Fig. 3b -
Page
189 / 262
9. Ground Tools
« .RAW » FILE
Step4:
(Fig. 4)
For “.raw” file, the database to be
used must be the one named
“EC225_PGSV3_128_02.arb”* (1)
which contains 128 parameters.
Select it, make sure that it is active
on file name (2), and open it (3).
(1)
(2)
(3)
Then, after go to “Step5”.
- Fig. 4 -
* PGS databases are located on C:\Program Files\PGS\Database
Step5:
(Fig. 5)
To definitely load the database,
highlight it by directly clicking on the
associated line (1) and after click on
“Select” (2).
(1)
Then, after go to “Step6”.
(2)
- Fig. 5 -
Page
190 / 262
9. Ground Tools
« .RAW » FILE
(1)
Step6:
(Fig. 6)
The name of the database you have
selected is displayed on the window
topic (1). Now to go to the menu
“Aircraft” (2) & select “Fleet” (3).
(2)
(3)
Then, after go to “Step7”.
Step7:
At this level, you have 2 possibilities:
(Fig. 7a)
- Either you aircraft is already
created, then select it (1) and after
go directly to “Step8”.
(Fig. 7b)
- Fig. 6 -
(1)
- Fig. 7a -
-Either aircraft is not created, then
you have to do it. As a result, fulfil
manually the needed fields such as:
 Airline
(1)
 A/C Type
(2)
 A/C Tail
(3)
 A/C S/N
(4)
…Then, after go to “Step8”.
(1)
(2)
(3)
(4)
- Fig. 7b -
Page
191 / 262
9. Ground Tools
« .RAW » FILE
(1)
Step8:
(Fig. 8)
(2)
Once the aircraft has been chosen,
click on “Edit” (1), then select
“Details” (2).
Then, after go to “Step9”.
- Fig. 8 -
(1)
Step9:
(Fig. 9)
At this step, it needs to fulfil various
information. The 1st one is the
database name. To do so, click on
the associated icon (1).
Then, after go to “Step10”.
- Fig. 9 Page
192 / 262
« .RAW » FILE
9. Ground Tools
(2)
(1)
Step10: The database previously imported
(Fig. 10)
appears now (1). Choose it, then
click on “Select” (2).
Then, after go to “Step11”.
- Fig. 10 -
(1)
Step11: The database name path is now
(Fig. 11)
correctly displayed (1). The following
operation consists in selecting the
correct maintenance recorder; to do
so click on the associated “Select”
button (2).
(2)
Then, after go to “Step12”.
- Fig. 11 Page
193 / 262
« .RAW » FILE
9. Ground Tools
(2)
Step12: The type of maintenance recorder
(Fig. 12)
used here is “SSQAR with P/N
HUMS from Eurocopter”. Then
highlight it (1), and validate this
choice by clicking on the “Select”
button (2).
(1)
Then, after go to “Step13”.
- Fig. 12 -
Step13: The maintenance recorder type is
(Fig. 13)
now correctly displayed (1). Then it
needs to identify where the “.raw”
files will be taken from for analysis.
So, click on the associated icon (2).
Then, after go to “Step14”.
(1)
(2)
- Fig. 13 Page
194 / 262
9. Ground Tools
« .RAW » FILE
Step14: The correct path must be:
(Fig. 14)
E:\Mssql\Backup\BackupRawFiles
(1). After, validate by clicking on the
“OK” button (2).
(1)
Then, after go to “Step15”.
(2)
- Fig. 14 -
Step15: The directory where the “.raw” files
(Fig. 15)
will be now taken from for analysis is
correctly displayed (1). In order to
validate all these settings, click now
on “OK” (2).
Then, after go to “Step16”.
(1)
(2)
- Fig. 15 Page
195 / 262
« .RAW » FILE
9. Ground Tools
(1)
Step16: Now click on “Download” (1) and
(Fig. 16)
(2)
select “Maintenance Recorder” (2).
Then, after go to “Step17”.
- Fig. 16 -
Step17: The window here displays now all
(Fig. 17)
the flights contained on the directory
selected on “Step14”. Select one
particular file (1) and click on
“Record” (2): this will automatically
generates a file with the extension
“.xff”.
(1)
(2)
Then, after go to “Step18”.
- Fig. 17 Page
196 / 262
« .RAW » FILE
9. Ground Tools
(2)
Step18: The “.xff” file previously converted is
(Fig. 18a)
(1)
now displayed. To get the graph,
highlight it (1), then after click on
”Select” (2).
- Fig. 18a -
(Fig. 18b)
… and after you just need to choose
the parameters you want to display.
- Fig. 18b Page
197 / 262
9. Ground Tools
PMT SOFTWARE
MFDAU FDR
MFDAU HUMS
552 VC
703-AKMFDAU.00
Page
198 / 262
PMT SOFTWARE
9. Ground Tools
MFDAU HUMS
MFDAU FDR
703-AKMFDAU.00
Page
199 / 262
PMT SOFTWARE
9. Ground Tools
Page
200 / 262
PMT SOFTWARE
9. Ground Tools
MFDAU software and Checksum
reading
Time setting
Page
201 / 262
9. Ground Tools
VIBRATO SOFTWARE
VPU
552 VC
703-AKMFDAU.00
Page
202 / 262
VIBRATO SOFTWARE
9. Ground Tools
VPU
703-AKMFDAU.00
Page
203 / 262
VIBRATO SOFTWARE
9. Ground Tools
Load first configuration file for EC225
Select the right VPU configuration file
Page
204 / 262
ACCELEROMETER
TEST
9. Ground Tools
EMU cable Vibrato connected on port RS232 port Com 1
Global « Sensors Test »
Start Sequency
Individual test
Page
205 / 262
ACQUISITION
COMMAND
9. Ground Tools
Launch a specific command during Ground run for a special acquisition
Page
206 / 262
ACCELEROMETER
CALIBRATION
•
9. Ground Tools
What is it?
- A new test to control the whole acquisition chain (Accelerometers + wiring + VPU)
•
Why this new test?
- To check the calibration of the accelerometer sensors
- Today “functional test” enables to check only the electrical continuity and not calibration
•
When to perform it?
- Every 3000 FH / 2 Years for transmission accelerometers
- Every 1 Year for engine accelerometers
•
What are the requirements to perform it?
- Calibrated Handled Shaker delivering 1g peak or rms at 159 Hz for up to 250 grams
(eg: PCB 699A02 Model)
- Wax (to install the accelerometer on the shaker)
- Vibrato SW V3.1 (With the new “Raw Data” function) + VPU wiring
Page
207 / 262
ACCELEROMETER
CALIBRATION
9. Ground Tools
- Remove the accelerometer (without removing the electrical connection)
- Mount the accelerometer on the shaker with wax
Step 1
Step 4
Step 2
Step 3
Step 5
Step 6
Page
208 / 262
ACCELEROMETER
CALIBRATION
9. Ground Tools
Testing accelerometer on aircraft:
Check higher switch is
on “RMS” position
Rotor tuning accelerometer
Maintain the shaker without moving during the whole acquisition duration (1 or 2 seconds)
Page
209 / 262
ACCELEROMETER
CALIBRATION
9. Ground Tools
Testing accelerometer on aircraft:
Transmission accelerometer
Engine accelerometer
Maintain the shaker without moving during the whole acquisition duration (1 or 2 seconds)
Page
210 / 262
ACCELEROMETER
CALIBRATION
9. Ground Tools
- Use VIBRATO “Raw Data” function to launch the acquisitions and edit the results
Exit
Wait for validity
If the Validity delivers the
icon,
Close Vibrato SW, check wirings,
press on reset button and wait for 50
seconds before restarting Vibrato SW.
Click on “Raw Data” button
Select an accelerometer to test
Click on “Start Acquisition” button
Check “Execution Report Validity” and
click on the graph for reading a value
of FFT in g (at 159 Hz if the shaker is
used). Use the zoom function to have
a better precision.
Page
211 / 262
9. Ground Tools
CMT SOFTWARE
VPU
552 VC
703-AKMFDAU.00
Page
212 / 262
CMT SOFTWARE
9. Ground Tools
(1)
(2)
Username: EC
Password: lowtide1
Page
213 / 262
CMT SOFTWARE
9. Ground Tools
CONFIGURATION FILE
STORED IN AHMU
VPU FILE
Page
214 / 262
CMT SOFTWARE
9. Ground Tools
SOFTWARE
DOWNLOAD TO VPU
Page
215 / 262
CMT SOFTWARE
9. Ground Tools
CONFIGURATION FILE
DOWNLOAD TO VPU
Page
216 / 262
STEADY CONTROL
ROTOR SOFTWARE
9. Ground Tools
Setting for a new aircraft under
To create a new aircraft you must set it first
under « Expert » mode
Password : expert
Page
217 / 262
STEADY CONTROL
ROTOR SOFTWARE
9. Ground Tools
Mode Expert
Modification of the
previous setting
Adjustment proposal on MR in weight, pitch rods and tabs
Ask a tune from another PCMCIA file
Overlimit on MR will be displayed in red
Page
218 / 262
STEADY CONTROL
ROTOR SOFTWARE
9. Ground Tools
User Mode
Sessions recognized by Steady control
getting rotor tuning data
Tuning realised already
Files already used to adjust rotor
Possibility to set rotor following parameters
Page
219 / 262
NOTES
Page
220 / 262
10. Quick Health
ASSUMPTION
SOFTWARE ARCHITECTURE
DOWNLOAD FILES
WARNINGS
OVERSHOOTS ACKNOWLEDGEMENT
HEALTH WARNINGS ACKNOWLEDGEMENT
SETTINGS & PURGE
REFRESH DATA
Page
221 / 262
ASSUMPTION
10. Quick Health
Requirements:
•
Product developped for EC 225/725
•
Data transfer on PCMCIA card with rotor turning
•
Quick download & analysis of session:
 1 minute maximum for 1 session
•
« Go - No Go » philosophy
Page
222 / 262
10. Quick Health
FUNCTIONS
SOFTWARE
ARCHITECTURE
SQL (Engine Database)
GS Database
Health
Usage
Maintenance Report
Flight Report
Considered as…
THE REFERENCE
Threshold Management
GS Software
V5.1
Component Management
Thresholds

Flight
Files
No link between the applications
Health
Maintenance Report:
FUNCTIONS
QH Database
Quick Health
Software
- Overshoot
- Failure (chip)
Considered as…
A VIEWER
- Health exceedance
Page
223 / 262
DOWNLOAD FILES
10. Quick Health
Page
224 / 262
WARNINGS
10. Quick Health
OVERSHOOT
FAILURE
HEALTH
Page
225 / 262
OVERSHOOTS
ACKNOWLEDGEMENT
10. Quick Health
Page
226 / 262
HEALTH WARNINGS
ACKNOWLEDGEMENT
10. Quick Health
Page
227 / 262
SETTINGS & PURGE
10. Quick Health
Page
228 / 262
REFRESH DATA
10. Quick Health
Page
229 / 262
NOTES
Page
230 / 262
11. Multibase Principle
Page
231 / 262
11. Multibase Principle
GSC V5.1
SQL (Engine Database)
GS Databases
AIRCRAFT S/N 1
A/C 1
A/C 2
AIRCRAFT S/N 2
A/C 3
A/C 4
AIRCRAFT S/N 3
AIRCRAFT S/N 4
QH V1.1
QH Database
! DOWNLOAD TO BE PERFORMED ON EACH ASSOCIATED GSC DATABASE !
Page
232 / 262
12. Health Indicators
GENERALITIES
SHAFT MONITORING
GEAR MONITORING
BEARING MONITORING
THRESHOLD POLICY
THRESHOLD METHODOLOGY
THRESHOLD MANAGEMENT
MAINTENANCE ACTIONS
Page
233 / 262
GENERALITIES
12. Health Indicators
 Shafts, gears and bearings vibration signatures by the HUMS system
are generally too complex for visual monitoring.
 The purpose of the HUMS data analysis process is to reduce
complicated signatures to a set of indicators.
 There are two main categories of indicators:
- Energy Indicators: measure absolute or relative energy levels :
- Pattern Indicators: search for pattern in the vibration signature that can be
associated with defects
 Vibration energy measurements will provide useful information on the
fault severity.
 Pattern indicators can be effective detectors on fault condition.
Page
234 / 262
12. Health Indicators
GENERALITIES
List of MARMS indicators
Gears
Shafts
RMS : Root mean square
RMS-R : Root mean square of residual Signal
OM1 : 1st harmonic
OM2 : 2nd harmonic
OMx : Mesh frequency (x = teeth number)
OM2x : 2nd harmonic of mesh frequency (=H2FE)
MODx : Average of mesh frequency side bands
Kg
: RMS-r/RMS
Km
: Kurtosis of signal
Kr
: Kurtosis of residual signal
OM1
OM2
: 1st harmonic (unbalance)
: 2nd harmonic (misalignment)
Bearings
Fi
Fe
RMS
M6
: Internal race frequency
: External race frequency
: Root mean square
: Statistical moment (order 6)
Rotors
OM1 => Unbalance / Damper wear
OM2 => Unbalance
OMb => MGB suspension bars or flexible mounting plate
(b is the number of blades)
OM2b: Harmonics of rotors
Page
235 / 262
SHAFT MONITORING
12. Health Indicators
RMS
Root Mean Square
- Total energy of the average signal
Theory:
• Standard deviation of the signal average.
• Most faults involving damage will increase the energy of the vibration signal.
• This indicator used in conjunction with other indicators enables detection of
defects on a component, although at a fairly late stage of damage component.
Fault types:
• General.
Page
236 / 262
SHAFT MONITORING
12. Health Indicators
RMS-r
Residual Root Mean Square
- Energy of the average signal without meshing tones
Theory:
• This indicator provides information of the signal residual energy once the
“strong tones” (mesh frequency) have been removed.
• Some defects, especially those involving wear, do not affect strong tones in
spectra created by shaft rotation or gear mesh.
• The ability to measure the background noise of a spectrum, away from
generally strong tones, is therefore a good powerful detection technique.
• WHT is short for “white” as this amounts in the white part of the spectrum.
• WHT = RMS minus MFL1
Fault types:
• Distributed gear tooth damage / wear.
• Gear tooth bending.
Page
237 / 262
SHAFT MONITORING
12. Health Indicators
OM1
Shaft Order 1
- Energy of the signal average at once per revolution
Theory:
• This indicator provides information on the unbalance of the shaft monitored.
This unbalance is the result of an offset between the center of gravity “G” and
its own rotation center “C”.
• This unbalance is generated by a centrifugal force created by this phenomena.
• Important indicator for high speed shaft.
Fault types:
• Unbalance shaft.
• Loss of gear support, gear web/shaft crack.
SECTION AA
A
G
C
A
M : shaft weight
r : distance C to G
Force = mr2
Page
238 / 262
SHAFT MONITORING
12. Health Indicators
OM2
Shaft Order 2
- Energy of the signal average at twice per revolution
Theory:
• This indicator provides information on the misalignment of the shaft monitored.
• This misalignment is the result of bending reaction generated by load applied
on the contact surface bearing linked to the shaft.
• This indicator is related with OM1 for analysis.
Fault types:
• Misalignment shaft / bad coupling.
• Shaft crack / local shaft inertia / stiffness / bending.
or
Page
239 / 262
GEAR MONITORING
12. Health Indicators
OMx
Mesh Frequency
- Energy of the signal average at meshing frequency
Theory:
• X is the number of teeth of the pinion/wheel.
• This indicator is representative of the load applied on a gear.
• The variation of this indicator underlines the evolution in the gear teeth profile
(wear of teeth).
• It may be not useful when a gear does not produce a clear meshing frequency
in the signal average.
Fault types:
• Distributed gear tooth damage.
• Wear on gear teeth.
Page
240 / 262
GEAR MONITORING
12. Health Indicators
OM2x or H2FE
2nd Harmonic of the Mesh Frequency
- Energy of the tone at 2x
Theory:
• X is the number of teeth of the pinion/wheel.
• This indicator is also representative of the load applied on a gear.
• The variation of this indicator underlines the evolution in the gear teeth profile
(wear of teeth).
• It may be not useful when a gear does not produce a clear meshing frequency
in the signal average.
Fault types:
• Distributed gear tooth damage.
• Wear on gear teeth.
Page
241 / 262
GEAR MONITORING
12. Health Indicators
MODx
Modulation of Meshing frequency
- Energy of the 1st side bands of the gear
meshing tone.
MODx = ((OMx-1) +
(OMx+1))/2
Theory:
• This indicator gives the energy located around the gear mesh tone by
analyzing the signal on its nearest side-band.
• Damage affecting the gear as a whole (as compared to localised damage)
produces low modulation of the gear meshing frequency.
• This indicator is specially suitable for signature when the mesh tone are not
well identified or when the mesh frequency is not produced clearly.
Fault types:
• Gear web or hub cracks.
• Shaft or coupling damage.
• Misalignment.
Page
242 / 262
GEAR MONITORING
12. Health Indicators
Kg
- Kg = RMS-r divided by RMS
Theory:
• This indicator provides information of small shocks
when a defect is generalized on a gear.
• Kg is the ratio of the energy of residual signal (RMS-r) to the total energy of the
signal average (RMS).
• Kg does not depend any more of the energy levels but clarifies clearly shocks
damage such as spalling or pitting.
• This indicator detects distributed damage and the severity of fatigue cracks.
Fault types:
• General teeth damage on gear / wear.
Page
243 / 262
GEAR MONITORING
12. Health Indicators
Km
- Kurtosis of average signal
Theory:
• This indicator provides a statistical measure of any
impulsive events in the signal average.
• When a crack appears on a gear tooth, the tooth stiffness reduces with
increasing bending forces.Consequently, the next tooth could interfere and
generate an impulse signal.
• This indicator will be highly sensitive and increases quickly at early stage of
fault development. It can fall back as the damage becomes extensive.
Fault types:
• Localised gear tooth spalling, chipped or loss.
• Tooth root bending.
Page
244 / 262
GEAR MONITORING
12. Health Indicators
Kr
- Kurtosis of residual signal
Theory:
• This indicator provides a statistical measure of
any impulsive events in the residual signal average.
• This indicator is related with OM1 for analysis.
Fault types:
• Localised gear tooth spalling, chipped or loss.
• Tooth root bending.
Page
245 / 262
BEARING
MONITORING
RMS
12. Health Indicators
Fi - Fe
Root Mean Square
Evaluation of total energy of the signal
Internal /External frequency bearing face
monitoring
Theory
RMS indicator is an evaluation of the total energy of the signal.
When a damage occurred, the total amplitude of the signal
increases.
Theory
These indicators allow to detect a local defect on a rolling
component by analyzing the balls in the frequency domain on
the external and internal face of a bearing:
Value issued from bearing frequency is taken around +/-10%
of the balls frequency.
Fault types:
General
Fault types
Fi: Local damage on internal race.
Fe: Local damage on external race.
M6
Page
246 / 262
THRESHOLD POLICY
12. Health Indicators
FUNCTION
Learning thresholds
Threshold is a critical value which is set to alert the user
when data change significantly.
Threshold value = m + N@
Some components will have threshold , others as bearings
don’t have.
m=average computed on acquisitions obtained on 25 flying
hours
N=number defined by Eurocopter
@=standard deviation on the X last flight hours
NATURE OF THRESHOLD
Two nature of threshold:
Amber: amber alerts should give advance warning in the
vibration signature.
Further an amber alert, trend monitoring on the alert indicator
is required.
Specific visual or sensitive inspection may be required to help
localise the defect.
Red: red alerts indicate that the aircraft integrity has to be
restored in priority before next flight.
- During the learning period :(from 0 to 25 hours flight)
• If a max value exists on the component,a maintenance
message will be delivered during the learning period .
• If the max value doesn’t exist, no threshold.
- After the computation period:
• If the max value exists and the learning threshold > max
value, the threshold will have the max value.
• If the min and max value doesn’t exist, the
calculated threshold will be saved
TYPE OF THRESHOLD
-Fixed threshold :Threshold value is defined by Eurocopter
design Office (mechanical department) but can be modified
on GSC by administrator ( SB is mandatory)
bendix shaft, rotors, fan shaft output
- Learning threshold : Threshold value is automatically
computed on the last X flight hours (X=25 by default).
Page
247 / 262
THRESHOLD POLICY
12. Health Indicators
Indicator
Red threshold
Stop flights
Amber threshold
Alert
Time
Trend graph can be displayed for each indicator each component monitored to know :
• Acquisitions results comparing to Red and Amber threshold.
• Evolution follow-up flight after flight on a component .
•Trend to suspect a defect and anticipate on an alarm validity.
Page
248 / 262
THRESHOLD
METHODOLOGY
•
12. Health Indicators
Step 0 :
- Amber thresholds on Main and Tail Rotor indicators
- Amber thresholds on Primary indicators
•
Step 1 : (more than 1000 samples required)
- Amber & Red thresholds on Main and Tail Rotor indicators
- Amber & Red thresholds on Primary indicators
- Amber thresholds on Secondary indicators
•
PRIMARY
THRESHOLDS
SECONDARY
THRESHOLDS
EuroHUMS
EuroARMS
M’ARMS
EuroHUMS
EuroARMS
M’ARMS
SO1
OM1
FM4A
Kr
Step 2 : (more than 2000 samples required)
SO2
OM2
FM4B
Kg
Partial redefinition of some thresholds if necessary
MFL1
OMZ
WHT
RMSr
SDB1
MODZ
IEI
Fi
RMS
RMS
OEI
Fe
---
H2FE
---
M6
Page
249 / 262
12. Health Indicators
THRESHOLD
METHODOLOGY
• Phase 1 : Data gathering and global overview of all Indicators
• Phase 2 : Study of Distributions and classification of these distributions
Criteria:
F: statistical Fisher-value of the Variance (ANOVA)
W: statistical Fisher-value of the Levene Test
Data set homogeneity
Homogenous
Analyst decides
Not homogenous
F/W
F
F/W < 4
and
F < 500
4 < F/W < 6
or
500 < F < 1.000
F/W > 6
and
F > 1.000
Page
250 / 262
12. Health Indicators
THRESHOLD
METHODOLOGY
• Phase 3: Choice of Threshold type for each indicator
Distribution type
Indicator
Primary
Secondary
Homogenous
Fixed Amber & Red
Fixed Amber
Homogenous spiky
Fixed Amber
No threshold
Not Homogenous
Learning Amber
No threshold
• Phase 4: Definition of Thresholds value and test on distribution
Warning simulation
using 2/5 filter
Amber threshold
Page
251 / 262
THRESHOLD
MANAGEMENT
12. Health Indicators
Example
Fixed RED
Fixed AMBER
Page
252 / 262
12. Health Indicators
THRESHOLD
MANAGEMENT
Example
25 H
mean
@
Learning Threshold
Page
253 / 262
THRESHOLD
MANAGEMENT
12. Health Indicators
Trend damaging :
Apply Work card following AMM chap 45.
Change level :
Pb following a maintenance action or a sudden mechanical
failure (rupture)
See MMA chap 45
Spikes: erratic acquisitions
Do not take in account
Possibility to select more acquisition ex: “500” in Health
« Tools options » to identify the trend
Page
254 / 262
MAINTENANCE
ACTIONS
12. Health Indicators
MMA Chapter 45
Page
255 / 262
MAINTENANCE
ACTIONS
12. Health Indicators
Maintenance Action Performed
Page
256 / 262
NOTES
Page
257 / 262
APPENDIX
Page
258 / 262
CVFDR PARAMETERS (1)
f
Wd
1
2
3
4
5
6
7
8
9
10
11
12
Parameter
/
SYNCHRO
WORD
/
TIME ( SEC / MIN )
Drift Angle
MFD 1
FRAME COUNTER
Drift Angle
MFD 4
TIME ( HOUR / YEAR )
DME frequency 1 MFD1
DME frequency 2 MFD1
DME frequency 3 MFD1
TIME ( MONTH / DAY)
DME distance 1
MFD1
DME distance 2
MFD1
DME distance 3
MFD1
/
Collective stick position
(Pilot input)
APM 1
/
Collective control output
APM 1
/
/
Longitudinal stick position
(Pilot input)
APM 1
/
Longitudinal control output
APM 1
/
/
Lateral stick position
(Pilot input)
APM 1
/
Lateral control output
APM 1
/
/
Tail rotor pedal position
(Pilot input)
APM 1
/
Tail rotor control output
APM 1
/
13
14
15
16
/
Lateral Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
17
18
19
20
21
22
23
24
25
26
27
Parameter
/
INDICATED AIRSPEED
MFD 1
/
/
HEADING
MFD 1
/
/
RADIO ALTITUDE (LSP)
MFD 1
/
/
RADIO ALTITUDE (MSP)
MFD 1
/
/
Free Turbine speed
NF1
/
/
Ng Engine 1
AMC 1
/
/
Engine 1 torque
AMC 1
/
/
YAW RATE
APM 1
/
/
Discrete word #6
(serial)
/
/
Discrete word #7
(latched)
/
Selected VS APM 1
Selected VS APM 2
Selected VS APM 1
Selected VS APM 2
Wd
33
34
35
36
37
38
39
40
41
42
43
28
44
29
45
30
31
32
/
Longitudinal Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
46
47
48
Parameter
/
PITCH ATTITUDE
MFD 1
/
/
ROLL ATTITUDE
MFD 1
/
/
Marker beacon passage
SDI 01
MFD 1
/
Marker beacon passage
SDI 10
MFD 1
/
SLING LOAD FORCE
AMC 1
/
/
Ng Engine 2
AMC 1
/
/
Engine 2 torque
AMC 1
/
/
Engine 1 Commands
AMC 1
/
/
Engine 2 Commands
AMC 1
/
/
T4 Engine 1
AMC 1
/
/
T4 Engine 2
AMC 1
/
/
AMC discrete word #1
AMC 1
/
/
Lateral Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
49
50
51
52
53
54
55
56
57
58
Parameter
/
Main Rotor Speed
NR
/
/
ILS Glideslope deviation
SDI 01
MFD 1
/
ILS Glideslope deviation
SDI 10
MFD 1
/
MLS Glideslope deviation
MFD 1
/
/
ILS Localizer deviation
SDI 01
MFD 1
/
ILS Localizer deviation
SDI 10
MFD 1
/
MLS Localizer deviation
MFD 1
/
/
YAW RATE
APM 2
/
/
MFDs ON / OFF / severe failure
MFD 1
/
/
MFDs discrepancies
MFD 1
/
Wd
65
66
67
68
69
70
71
72
73
74
59
75
60
76
61
77
62
63
64
/
Longitudinal Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
78
79
80
Parameter
/
AP PITCH MODE
APM 1
/
/
AP COLLECTIVE MODE
APM 1
/
/
AP ROLL/YAW MODE
APM 1
/
/
AP ARMED MODE
APM 1
/
/
Collective stick position
(Pilot input)
APM 2
/
Collective control output
APM 2
/
/
Longitudinal stick position
(Pilot input)
APM 2
/
Longitudinal control output
APM 2
/
/
Lateral stick position
(Pilot input)
APM 2
/
Lateral control output
APM 2
/
/
Tail rotor pedal position
(Pilot input)
APM 2
/
Tail rotor control output position
APM 2
/
/
Lateral Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
81
82
83
84
85
86
87
88
89
90
91
Parameter
/
MGB Oil Pressure
AMC 1
/
Pilot selected course
MFD 1
Pilot selected course
MFD 4
Pilot selected course
MFD 1
Pilot selected course
MFD 4
/
Altitude rate (LSP)
APM 1
/
/
Altitude rate (MSP)
APM 1
/
Outside Air Temperature AMC 1
MGB Oil Temperature
AMC 1
Outside Air Temperature AMC 1
MGB Oil Temperature
AMC 1
IGB Oil Temp. Caution
AMC 1
TGB Oil Temp. Caution AMC 1
IGB Oil Temp. Caution AMC 1
TGB Oil Temp. Caution AMC 1
AP Failures
MFD 1
AMC discrete word #2 AMC 1
AP Failures
MFD 4
AMC discrete word #2 AMC 2
/
YAW RATE
APM 1
/
MFD 1 pages
MFD 1
MFD 2 pages
MFD 1
MFD 3 pages
MFD 1
MFD 4 pages
MFD 1
T1 Engine 1
AMC 1
T1 Engine 2
AMC 1
T1 Engine 1
AMC 2
T1 Engine 2
AMC 2
Copilot selected course
MFD 1
Copilot selected course MFD 4
Copilot selected course
MFD 1
Copilot selected course MFD 4
Wd
97
98
99
100
101
102
103
104
105
106
107
92
108
93
109
94
95
96
/
Longitudinal Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
110
111
112
Parameter
/
PITCH ATTITUDE
MFD 4
/
/
ROLL ATTITUDE
MFD 4
/
VOR/ILS Freq. SDI 01(LSP) MFD1
VOR/ILS Freq. SDI 10(LSP) MFD1
VOR/ILS Freq. SDI 01(LSP) MFD4
VOR/ILS Freq. SDI 10(LSP) MFD4
VOR/ILS Freq. SDI 01(MSP) MFD1
VOR/ILS Freq. SDI 10(MSP) MFD1
VOR/ILS Freq. SDI 01(MSP) MFD4
VOR/ILS Freq. SDI 10(MSP) MFD4
/
SLING LOAD FORCE
AMC 2
/
Selected Heading
APM 1
Selected Heading
APM 2
Selected Heading
APM 1
Selected Heading
APM 2
Pilot Baro.Correct. (LSP)
MFD 1
Copilot Baro.Correct. (LSP) MFD 1
Pilot Baro.Correct. (LSP)
MFD 4
Copilot Baro.Correct. (LSP) MFD 4
Pilot Baro.Correct. (MSP) MFD 1
Copilot Baro.Correct. (MSP) MFD 1
Pilot Baro.Correct. (MSP) MFD 4
Copilot Baro.Correct. (MSP) MFD 4
/
LATITUDE (LSP)
MFD 1
/
/
LATITUDE (MSP)
MFD 1
/
/
LONGITUDE (LSP)
MFD 1
/
/
LONGITUDE (MSP)
MFD 1
/
Wd
113
114
115
116
117
118
119
120
121
122
Parameter
/
AMC discrete word #3
AMC 1
/
/
PRESSURE ALTITUDE
LSP
MFD 1
PRESSURE ALTITUDE
MSP
MFD 1
/
Fuel Flow Engine 1
AMC 1
/
/
Fuel Flow Engine 2
AMC 1
/
MFD 1 Config. (LSP) MFD 1
MFD 2 Config. (LSP) MFD 1
MFD 3 Config. (LSP) MFD 1
MFD 4 Config. (LSP) MFD 1
MFD 1 Config. (MSP) MFD 1
MFD 2 Config. (MSP) MFD 1
MFD 3 Config. (MSP) MFD 1
MFD 4 Config. (MSP) MFD 1
/
YAW RATE
APM 2
/
/
AMC discrete word #4
AMC 1
/
/
MFDs status
MFD 1
/
123
124
125
/
Lateral Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
126
127
128
/
Longitudinal Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
Page
259 / 262
CVFDR PARAMETERS (2)
Wd
129
130
131
132
133
134
135
136
137
138
139
140
Parameter
Fuel Quantity 1
AMC 1
Fuel Quantity 2
AMC 1
Fuel Quantity 1
AMC 2
Fuel Quantity 2
AMC 2
Selected manual ALT APM 1
Selected manual ALT APM 2
Selected manual ALT APM 1
Selected manual ALT APM 2
Ice detection
DMU 1
DME frequency 1 MFD4
DME frequency 2 MFD4
DME frequency 3 MFD4
DME distance 1
MFD4
DME distance 2
MFD4
DME distance 3
MFD4
/
Collective stick position
(Pilot input)
APM 1
/
Collective control output
APM 1
/
/
Longitudinal stick position
(Pilot input)
APM 1
/
Longitudinal control output
APM 1
/
/
Lateral stick position
(Pilot input)
APM 1
/
Lateral control output
APM 1
/
/
Tail rotor pedal position
(Pilot input)
APM 1
/
Tail rotor control output
APM 1
/
141
142
143
144
/
Lateral Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
145
146
147
148
149
150
151
152
153
154
155
Parameter
/
INDICATED AIRSPEED
MFD 4
/
/
HEADING
MFD 4
/
/
RADIO ALTITUDE (LSP)
MFD 4
/
/
RADIO ALTITUDE (MSP)
MFD 4
/
/
Free Turbine speed
NF2
/
/
Ng Engine 1
AMC 2
/
/
Engine 1 torque
AMC2
/
/
YAW RATE
APM 1
/
/
Discrete word #4
(shunt)
/
/
Discrete word #5
(serial)
/
Selected auto ALTA APM 1
Selected auto ALTA APM 2
Selected auto ALTA APM 1
Selected auto ALTA APM 2
Wd
161
162
163
164
165
166
167
168
169
170
171
156
172
157
173
158
159
160
/
Longitudinal Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
174
175
176
Parameter
/
PITCH ATTITUDE
MFD 1
/
/
ROLL ATTITUDE
MFD 1
/
/
Marker beacon passage
SDI 01
MFD 4
/
Marker beacon passage
SDI 10
MFD 4
/
SLING LOAD FORCE
AMC 1
/
/
Ng Engine 2
AMC 2
/
/
Engine 2 torque
AMC2
/
/
Engine 1 Commands
AMC 2
/
/
Engine 2 Commands
AMC 2
/
/
T4 Engine 1
AMC 2
/
/
T4 Engine 2
AMC 2
/
/
AMC discrete word #1
AMC 2
/
/
Lateral Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
177
178
179
180
181
182
183
184
185
186
Parameter
/
Main Rotor Speed
NR
/
/
ILS Glideslope deviation
SDI 01
MFD 4
/
ILS Glideslope deviation
SDI 10
MFD 4
/
MLS Glideslope deviation
MFD 4
/
/
ILS Localizer deviation
SDI 01
MFD 4
/
ILS Localizer deviation
SDI 10
MFD 4
/
MLS Localizer deviation
MFD 4
/
/
YAW RATE
APM 2
/
/
MFDs ON / OFF / severe failure
MFD 4
/
/
MFDs discrepancies
MFD 4
/
Wd
193
194
195
196
197
198
199
200
201
202
187
203
188
204
189
205
190
191
192
/
Longitudinal Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
206
207
208
Parameter
/
AP PITCH MODE
APM 2
/
/
AP COLLECTIVE MODE
APM 2
/
/
APROLL/YAW MODE
APM 2
/
/
AP ARMED MODE
APM 2
/
/
Collective stick position
(Pilot input)
APM 2
/
Collective control output
APM 2
/
/
Longitudinal stick position
(Pilot input)
APM 2
/
Longitudinal control output
APM 2
/
/
Lateral stick position
(Pilot input)
APM 2
/
Lateral control output
APM 2
/
/
Tail rotor pedal position
(Pilot input)
APM 2
/
Tail rotor control output position
APM 2
/
/
Lateral Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
Wd
209
210
211
212
213
214
215
216
217
218
Parameter
/
MGB Oil Pressure
AMC 2
/
Pilot selected DH
MFD 1
Copilot selected DH
MFD 1
Pilot selected DH
MFD 4
Copilot selected DH
MFD 4
/
Altitude rate (LSP)
APM 2
/
/
Altitude rate (MSP)
APM 2
/
Outside Air Temperature AMC 2
MGB Oil Temperature
AMC 2
Outside Air Temperature AMC 2
MGB Oil Temperature
AMC 2
IGB Oil Temp. Caution
AMC 2
TGB Oil Temp. Caution AMC 2
IGB Oil Temp. Caution
AMC 2
TGB Oil Temp. Caution AMC 2
APM discrepancies
MFD 1
EID 2 pages
AMC 1
APM discrepancies
MFD 4
EID 2 pages
AMC 2
/
YAW RATE
APM 1
/
MFD 1 pages
MFD 4
MFD 2 pages
MFD 4
MFD 3 pages
MFD 4
MFD 4 pages
MFD 4
AMC 1 failure
AMC 1
EID 1 pages
AMC 1
AMC 2 failure
AMC 2
EID 1 pages
AMC 2
Wd
225
226
227
228
229
230
231
232
233
234
219
235
220
236
221
237
222
223
224
/
Longitudinal Acceleration
MFD 1
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
238
239
240
Parameter
/
PITCH ATTITUDE
MFD 4
/
/
ROLL ATTITUDE
MFD 4
/
Selected IAS
APM 1
Selected IAS
APM 2
Selected IAS
APM 1
Selected IAS
APM 2
Wind Speed
MFD 1
Wind Direction MFD 1
Wind Speed
MFD 4
Wind Direction MFD 4
/
SLING LOAD FORCE
AMC 2
/
/
Discrete word #1
(shunt)
/
/
Discrete word #2
(shunt)
/
/
Discrete word #3
(shunt)
/
/
LATITUDE (LSP)
MFD 4
/
/
LATITUDE (MSP)
MFD 4
/
/
LONGITUDE (LSP)
MFD 4
/
/
LONGITUDE (MSP)
MFD 4
/
Wd
241
242
243
244
245
246
247
248
249
250
Parameter
/
AMC discrete word #3
AMC 2
/
/
PRESSURE ALTITUDE
LSP
MFD 4
/
PRESSURE ALTITUDE
MSP
MFD 4
/
Fuel Flow Engine 1
AMC 2
/
/
Fuel Flow Engine 2
AMC 2
/
MFD 1 Config. (LSP) MFD 4
MFD 2 Config. (LSP) MFD 4
MFD 3 Config. (LSP) MFD 4
MFD 4 Config. (LSP) MFD 4
MFD 1 Config. (MSP) MFD 4
MFD 2 Config. (MSP) MFD 4
MFD 3 Config. (MSP) MFD 4
MFD 4 Config. (MSP) MFD 4
/
YAW RATE
APM 2
/
/
AMC discrete word #4
AMC 2
/
/
MFDs status
MFD 4
/
251
252
253
/
Lateral Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 4
/
Normal Acceleration
MSP
MFD 4
254
255
256
/
Longitudinal Acceleration
MFD 4
/
/
Normal Acceleration
LSP
MFD 1
/
Normal Acceleration
MSP
MFD 1
Page
260 / 262
GSC MESSAGES
Fonction
CSM
Message activating
TRQ or TOT VEMD margin <0
N°
Message
136 Engine check has shown negative margin on engine #%NumeroMot%, %DescPN%(%PN%/%SN%).
UCTF
OAT < -30°C
USLN
NR exceedance
USLC
Torque exceedance
120 Overtorque has been detected,%DepTQ%.
CEPA
Chip alarm (MGB, TGB)
88
CEPA
Chip alarm (engine)
89
USLM
Engine exceedance
124 Engine %NumeroMot%/%DatesDep%/%DureeDep%/%ValMax% exceedance has been detected.
UCTV
Pilot disagreement on flight duration
1
UCTF
Pilot disagreement on session beginning date
2
UCTF
Pilot disagreement on OAT
UCTV
Task
Flight manual
Type
Health Incident
4
For helicopter operating under severe climatic conditions, special maintenance procedures and time
calculation apply.
MSR
Usage Incident
8
Main Rotor Overspeed has been detected. %DepNRMini%.
MMA
Usage Incident
MMA
Usage Incident
Oil debris has been detected in %DescPN%(%PN%/%SN%).
MMA
Usage Incident
Oil debris has been detected in Engine #%NumeroMot%, %DescPN%(%PN%/%SN%).
MMA
Usage Incident
MMA
Usage Incident
Airborne time has been declared faulty.
MMA
System Maintenance
Session date has been declared faulty.
MMA
System Maintenance
3
T/O OAT has been declared faulty.
MMA
System Maintenance
Pilot disagreement on number of landings
5
Landing Count has been detected faulty.
MMA
System Maintenance
USLN
Pilot disagreement on NR max value
25
NR Exceedance max value has been declared faulty.
MMA
System Maintenance
USLC
Pilot disagreement on TRQ exceedance type
29
TQ Exceedance type has been declared faulty.
MMA
System Maintenance
USLC
Pilot disagreemment on TRQ exceedance max value
30
TQ Exceedance max value has been declared faulty.
MMA
System Maintenance
USLC
Pilot disagreement on TRQ exceedance duration
31
TQ Exceedance duration has been declared faulty.
MMA
System Maintenance
UECM
Pilot disagreement on N1 cycles count
113 Engine #%NumeroMot%, %DescPN%(%PN%/%SN%) N1 cycle count has been declared faulty.
MMA
System Maintenance
UECM
Pilot disagreement on N2 cycles count
114 Engine #%NumeroMot%, %DescPN%(%PN%/%SN%) N2 cycle count has been declared faulty.
MMA
System Maintenance
USLM
Pilot disagreement on engine exceedance type
121 Engine %NumeroMot%, %DatesDep% exceedance type has been declared faulty.
MMA
System Maintenance
USLM
Pilot disagreement on engine exceedance max value
122 Engine %NumeroMot%, %DatesDep% exceedance max value has been declared faulty.
MMA
System Maintenance
USLM
Pilot disagreement on engine exceedance duration
123 Engine %NumeroMot%, %DatesDep% exceedance duration has been declared faulty.
MMA
System Maintenance
PACM
DTU failure
133* DTU failure has been detected.
MMA
System Maintenance
PACM
PCV failure
134* PCV failure has been detected.
MMA
System Maintenance
PACM
VPU failure
141* VPU failure has been detected
MMA
System Maintenance
PACM
HUMS failure
107* Failure %PACM%%Date PACM%.
MMA
System Maintenance
CEPA
Alarm (except chips)
108* Alarm %CEPA%%Dates CEPA%.
MMA
System Maintenance
USLM
OEI_HI or OEI_LO counters for the flight (end-beg) >0
135* Engine %NumeroMot%/%DatesDep%/%DureeDep%/%ValMax% regime has been used.
MMA
Usage Incident
UECN
NR cycles number <0
24*
MMA
System Maintenance
CEPA
System failure
**
129* Suspected fault on %CEPA%, occurrences %DatesCEPA%.
109 %DescPN%, %PN%/%SN% needs an overhaul.
MMA
MSR
System Maintenance
Scheduled Maintenance
**
110 %DescPN%, %PN%/%SN% reached its life limit.
MSR
Scheduled Maintenance
**
111 %DescPN%, %PN%/%SN% reached its operating time limit.
MSR
Scheduled Maintenance
**
112 %DescPN%, %PN%/%SN% needs a check. %SeuilCptr%
MSR
Scheduled Maintenance
Reasonableness check failed, NR cycle <= 0 has been detected.
* Messages defined but not affected to counters (no message in Maintenance Report)
** Messages 109 to 112: programmed maintenance (see common part specification [1])
Page
261 / 262
NOTES
Page
262 / 262