Professional Documents
Culture Documents
04 Health Fonction
04 Health Fonction
T2 Contents
4.1 Generals
4.2 Health Datas Acquisition
4.3 The sensors
4.3.1 ROTORS magnetic TOPS
4.3.2 Chip detectors
4.3.3 Accelerometers
4.3.4 Localisation
4.4 The VPU
4.4.1 Purpose
4.4.2 General operation
4.5 VIBRATO Software
4.5.1 Accelerometers test
4.5.2 Specific acquisition
4.5.3 Acquisition with a vibrating pot
4.6 MMI Man Machine Interface
4.7 Vibrations Acquisitions
4.7.1 Automatic acquisitions in flight
4.7.2 Manual acquisitions in flight
4.7.3 Acquisition on Main Rotor
4.7.4 Acquisition on Tail rotor
4.8 Rotor tuning software on ground station
4.8.1 Main rotor acquisitions display
4.8.2 Tail rotor acquisitions display
4.9 Steady control software on ground station
Sensors
accelerometers
GROUND
SEGMENT
Magnetic pick up VPU
This function ensures the monitoring of rotating mechanics and guarantees their safety.
Accelerometers allow vibrations acquisition requested by the VPU ( Vibration Processing Unit). The VPU is controlled by MFDAU_ACMS.
At the end of the flight, HEALTH data will be added in the « .225 » file.
After downloading on the PCMCIA, this file will be analysed in the ground station.
HEALTH indicators will be extracted from vibrating spectrum of the parts in order a identify a damage.
A flight report will be created. It will contains warnings if a limit has been reached.
A maintenance report will then give maintenance advises for technicians containing recommended tasks.
VIBRATION
MONITORING
• On the MGB, 23000 RPM shafts, accessories drives, epicyclical module, bearings and gears
• On tail drive shaft and bearing ( unbalance and misalignment ).
• On IGB : gears and bearings
• On TGB : inputs shafts, gears and bearings.
• On rotors : unbalance.
• On the engines gas generators wheels.
Recording of this parameters is performed according to a predefined cycle and to flight conditions. Acquisitions are performed automatically without crew intervention.
« Rotor Tuning » only requires crew intervention according to a specific procedure described in the flight manual. The vibrations acquired will be used with the steady control software.
TDS
+ Amplifierss
TGB IGB FAN MGB Engines
(1) (1) (5) (1) (8) (4) (4)
Top TR
MR2
TR
MR3
VPU
MR1
TOP SYNCHRO NR
Sensor
Phonic wheel MR
Target
Function
Detect a metal particle in the MGB ( epicyclical and main modules), IGB and TGB.
General characteristics
Linked to the indicating system ( 16WW ), the provide a ground after detection.
Thanks to these information, the VMS can only display a general »CHIP » message for the whole transmission ). But the MARMS receive an information from each detector, allowing a more
precise diagnosis.
These alarms will be clearly displayed and the maintenance report will provide the crew with maintenance tasks to be performed A maintenance message will also ask for a visual check on all
the magnetic plugs.
CHIP DETECTOR
Description
3 types of accelerometers (Mono axis, Biaxis, Tri axis) Y
TAIL ROTOR
Mounted close to the parts to monitor,
Rotor Tuning
Z
MR : 3 accéléromètres/ 6axes
TR: 1 accéléromètre / 2 axes
Pinions/shafts/bearings
Type: Mono axis, amplifier integrated
Y
Y
Z MAIN Z Engines
Monoaxis Z Vertical ROTOR Specific mono axis installed on the engines (heat resistant)
Biaxis Z Vertical / YLatéral
2 amplifiers associated to 2 accelerometers per engine.
Y
Triaxis
Z Vertical/ Y Latéral / X Longitudinal
X
Z
4.3.4 Localisation
MGB monitoring
11RK1
11RK9 11RK5
accessories drive
épicyclic module
Mono-axis on TGB
TGB
monitoring
Each single shaft and its bearing are monitored by a mono axis.
Acquisitions on engines
4.4.1 Purpose
• Rotors adjustments
Necessary acquisitions are performed cyclically following predefined sequences. It represents the VPU cycle lasting all the session. Link between VPU and MFDAU is RS 422
But some acquisitions may be performed at precise conditions, out of range of the cycle. They are priority acquisitions and they will interrupt the normal VPU cycle.
On ground : In flight :
priority 2: Unbalancing monitoring on Main et Tail Rotor priority 2: Vibration monitoring on engines in stabilized mode
priority 1: Vibration monitoring on engines in stabilized mode priority 1: Unbalancing monitoring on Main et Tail Rotor
priority 0: Vibration Monitoring on Gearbox and Tail drive shaft priority 0 : Vibration Monitoring on Gearbox and Tail drive shaft
At power up :
The VPU initiates a PBIT ( power up built in test ). MFDAU will first request from the VPU a status word ( GO or NO GO).
• A message « no go » will illuminate the « HUMS » light on the MMI ( pin program problem, no answer from VPU, checksum mismatch…. ). No acquisition will be performed then.
• If the message is “Go” The MFDAU will checks its compliance with the VPU software. Software uploading can be performed thanks to CMT.
Software installation in the VPU will allow to verify the acquisitions cycles and to configure the parameters (accelerometers, validity NR, NF…. )
During operation
No answer from VPU or non understandable answer will be considered as a major failure. Cycle will be interrupted and a major failure will be recorded.
AHMU is connected to 552VC ( through VPU connector). This test is just a line continuity test between VPU and the accelerometers ( except for the engines accelerometers where the test will
stop to the amplifiers). Each accelerometer can be tested separately.
« Sensors Test »
Individual Test
It is possible during a ground run to initiate a specific test ( eg engine after engine removal.
1 2 3
EVENT
CVR
ERASE
• Cards problems
- Software MFDAU/ACMS or code pin not recognised (No Data from Hums)
- Incoherence between MFDAU/ACMS and configuration tables
- NR, NG ou NF parameters invalids
EVENT
ERASE
HUMS
Flight data are displayed on the MMI at the end of the flight at the crew request, once engines are stopped and « DATA TRANSFER» achieved.
Data transfer is automatic at the end of the session. . However, in case of problem, the crew can perform a manual transfer.
In case of over limitation detection, the max value and the duration of the over limitation will be displayed.
NR exceeded parameter TQ exceeded parameter eng 1 exceeded parameter eng 2 exceeded parameter
The crew can validate or not usage data (Y/N) at the end of the flight by depressing « ENTER ». Each action on « ENTER will modify the validation message Y or N. Depressing the arrow
down will allow to display the next value. Validation message will be sent to the PCMCIA card Through the MFDAU ACMS with the session file.
Once the data are validated, it will not be possible to modify them after while.
Cruise 14:10:32
Example
TQ Max 95 % 0mn 08
Final validation will be confirmed by depressing acknowledge after the last data display..
It’s a way to lock the session onboard. After then, it will be impossible to modify the data in the flight report.
Automatic acquisitions are requested By the MFDAU ACMS to the VPU. They are performed according to cycles on all the accelerometers and in stabilized flight conditions. Acquisitions will
not be performed in case of instability of the parameter.
Concerns vibrations induced by the rotor only. On request, when the crew feels abnormal vibrations They have to be performed according to a particular procedure and follow a particular
sequence (FPOG, Hover,100 knots ,Cruise, MCP).
On request, MFDAU ACMS verifies the flight parameters concordance with the acquisition before sending the order to the VPU. 24 rotor laps are necessary to validate the acquisition. This
information will come from the magnetic tops. These acquisition have priority on automatic acquisitions.
Acquisitions are performed on 6 signals coming from 3 accelerometers. They are synchronized by the phonic wheel.
If the configuration is unstable, a message « FAIL » will be displayed on the MMI and acquisition will be cancelled.
If acquisition is correct, the VPU will send amplitude and phase signals To MFDAU ACMS.
On the Ground station, using « ROTOR TUNING » software, it will be possible to read the acquisitions signals ( amplitude in « ips » inch per second).
ROTOR TUNING
Acquisition running
acquisition résultat
Acquisition invalid
Configurations :
• FPOG : Full flat pitch with NR>245 trs et Delta NR< 5 trs
• HOVER in ground effect : flight logic - ZRS < 50 ft - IAS hover < 50 knts
• CRUISE 100kts : 90 knts < IAS < 110 knts
• CRUISE PMC : IAS>130 knts
select « ROTOR Tuning ». Select « Main Rotor » depress « Enter ». Select “FPOG”, then validate with « Enter ». Acquisition will be delivered after a few seconds. Vibrations level in “FPOG”
must not exceed a certain value in ips. Otherwise, a first adjustment will be mandatory before performing any other acquisition.
(1)
(3)
(2)
No threshold displayed
Acquisition value
No threshold displayed
Adjustment choice
2 ways to adjust
_ Starting from « 0 » values ( necessary to empty the blades bowls, to adjust pitch rods and tabs to
« 0 ».
_ Starting from previous adjustments memorized in the software.
Adjustment proposal
“EXPERT” mode