Hums PDF

AGUSTA AB-139 HELICOPTER
HEALTH AND USAGE MONITORING SYSTEM (HUMS)
OPERATION AND MAINTENANCE SOURCE DATA
Agusta
1ST EDITION 2002-07-08
SMITHS AEROSPACE, INC., ELECTRONIC SYSTEMS - GRAND RAPIDS
TDM 2128 UNCLASSIFIED
Table of contents
Chapter
INTRODUCTION OPERATION AND MAINTENANCE INFORMATION......................................................................................... 1 HUMS Introduction ................................................................................................................................... 1.1 Data acquisition unit function ................................................................................................................... 1.2 Cockpit display unit/data transfer unit function ........................................................................................ 1.3 HUMS dedicated sensors function........................................................................................................... 1.4 HUMS operation ....................................................................................................................................... 1.5 Advisory Messages .................................................................................................................................. 1.6 Display Pages........................................................................................................................................... 1.7 Operating procedures............................................................................................................................... 1.8 Operational checkout preliminary set up.................................................................................................. 1.9 HUMS system checkout .........................................................................................................................1.10 HUMS Sensor checkout .........................................................................................................................1.11 HUMS troubleshooting introduction .......................................................................................................1.12 HUMS fault symptom index....................................................................................................................1.13 HUMS fault isolation procedures............................................................................................................1.14 Removal and installation ........................................................................................................................1.15 Servicing .................................................................................................................................................1.16 Cleaning..................................................................................................................................................1.17 AIRCREW FLIGHT INFORMATION .................... .............................................................................................. 2 ILLUSTRATED PARTS CATALOGUE ................ .............................................................................................. 3
Effectivity: All
39-A-31-30-00-00A-001A-A 2002-07-08 Page 1 of 2
This page intentionally left blank
Effectivity: All
39-A-31-30-00-00A-001A-A 2002-07-08 Page 2 of 2
INTRODUCTION 1 PURPOSE
The purpose of this manual is to provide aircraft-level source data on the Health and Usage Monitoring System equipment installed on the AB-139 helicopter. It is intended to provide information on the HUMS equipment for use in the development of the formal aircraft maintenance and aircrew publications.
SCOPE
This manual covers the on-board components of the HUMS, specifically the components supplied by Smiths Aerospace Electronic Systems-Grand Rapids. Coverage of other HUMS components and related equipment is limited to general information only. HUMS installationrelated information is not included.
3
3.1
ARRANGEMENT
This manual is divided into the following three chapters:
Chapter 1
Chapter 1 provides operating and maintenance information for the HUMS. It is broken down into sub-chapters by subject and includes general description of the HUMS, theory of operation, operating procedures, testing and troubleshooting, and maintenance.
3.2
Chapter 2
Chapter 2 provides aircrew-related information. Information is divided into aircrew checklist information and operating procedures. Operating procedures common to both the maintainer and the aircrew are referenced to other chapters in the manual rather than repeated in this chapter.
3.3
Chapter 3
Chapter 3 provides an illustration and parts listing for the HUMS on-board equipment.
Effectivity: All
39-A-31-30-01-00A-001A-A 2002-07-08 Page 1 of 2
Effectivity: All
39-A-31-30-01-00A-001A-A 2002-07-08 Page 2 of 2
CHAPTER 1 OPERATION AND MAINTENANCE INFORMATION
Table of contents
CHAPTER/TITLE........... ...................................... ................................................................... CHAPTER PAGE 1.1 HUMS INTRODUCTION ............................... .............................................................................................. 1 1 System description............................................................................................................................ 1 1.1 Component description ............................................................................................................. 1 1.2 List of HUMS major components .............................................................................................. 1 1.3 List of dedicated sensors .......................................................................................................... 2 1.4 Associated equipment............................................................................................................... 2 1.2 DATA ACQUISITION UNIT FUNCTION....... .............................................................................................. 1 1 Data acquisition unit (DAU) .............................................................................................................. 1 1.3 COCKPIT DISPLAY UNIT/DATA TRANSFER UNIT FUNCTION............................................................... 1 1 Cockpit display unit/data transfer unit............................................................................................... 1 2 Controls and displays........................................................................................................................ 1 1.4 HUMS DEDICATED SENSORS FUNCTION .............................................................................................. 1 1 General.............................................................................................................................................. 1 2 Accelerometers ................................................................................................................................. 1 2.1 Transmission vibration monitoring ............................................................................................ 2 2.2 Rotor track and balance............................................................................................................ 2 2.3 Load factor ................................................................................................................................ 2 3 Tachometers ..................................................................................................................................... 3 3.1 Main rotor tachometer............................................................................................................... 3 3.2 Tail rotor tachometer ................................................................................................................. 3 3.3 Drivetrain tachometer................................................................................................................ 3 1.5 HUMS OPERATION...................................... .............................................................................................. 1 1 Introduction ....................................................................................................................................... 1 2 Equipment Interface.......................................................................................................................... 2 3 HUMS Initialization and Startup........................................................................................................ 4 3.1 Initialization................................................................................................................................ 4 3.2 Startup....................................................................................................................................... 4 3.3 DTD operations ......................................................................................................................... 4 4 HUMS operations and ground/flight regimes.................................................................................... 4 5 Data acquisition and processing....................................................................................................... 5 6 Transmission vibration monitoring.................................................................................................... 7 7 Rotor track and balance operations.................................................................................................. 8 7.1 Rotor health monitoring............................................................................................................. 8 7.2 Rotor tuning............................................................................................................................... 9 8 Usage monitoring.............................................................................................................................. 9 8.1 Logbook functions ..................................................................................................................... 9 8.2 Structural usage monitoring (SUM) ........................................................................................10 8.3 Transmission usage monitoring (TUM)...................................................................................11
Effectivity: All
39-A-31-30-02-00A-001A-A 2002-07-08 Page 1 of 4
TDM 2128 UNCLASSIFIED Engine power assurance ................................................................................................................12 System built in test ..........................................................................................................................12 10.1 Start-up BIT .............................................................................................................................13 10.2 Periodic BIT.............................................................................................................................13 10.3 Initiated BIT .............................................................................................................................13 10.4 Status and BIT log displays ....................................................................................................13 1.6 ADVISORY MESSAGES .............................. .............................................................................................. 1 1 Advisory messages ........................................................................................................................... 1 1.7 DISPLAY PAGES... ...................................... .............................................................................................. 1 1 Menu tree .......................................................................................................................................... 1 2 Detailed displays ............................................................................................................................... 1 3 Startup............................................................................................................................................... 1 4 Top-level menu ................................................................................................................................. 3 5 A/C maintenance menu .................................................................................................................... 4 5.1 RT&B......................................................................................................................................... 4 5.2 EPA ........................................................................................................................................... 6 5.3 DPD ........................................................................................................................................... 6 6 Configure RBT .................................................................................................................................. 8 6.1 Modification of RBT status ........................................................................................................ 9 7 DTD status ........................................................................................................................................ 9 8 View logbook...................................................................................................................................10 8.1 Last operation .........................................................................................................................10 8.2 Cumulative totals.....................................................................................................................11 9 BIT...................................................................................................................................................12 9.1 Initiate IBIT ..............................................................................................................................12 9.2 Viewing BIT results .................................................................................................................12 9.3 Clearing BIT results.................................................................................................................13 10 Setup ...............................................................................................................................................13 10.1 Upload .....................................................................................................................................13 10.2 Date/Time................................................................................................................................15 10.3 Configuration P/N....................................................................................................................15 11 Event mark ......................................................................................................................................16 12 Pop up displays...............................................................................................................................17 12.1 CDU/DAU communication failure ...........................................................................................17 12.2 File 80% full indication ............................................................................................................17 1.8 OPERATING PROCEDURES....................... .............................................................................................. 1 1 Data entry methods and guidelines .................................................................................................. 1 1.1 Character data entry. ................................................................................................................ 1 1.2 Field data entry ......................................................................................................................... 1 2 Operating procedures ....................................................................................................................... 2 2.1 OBS initialization ....................................................................................................................... 2 2.2 OBS configuration uploading .................................................................................................... 2 2.3 Setting system date/time........................................................................................................... 2 2.4 Viewing configuration part number ........................................................................................... 3 2.5 BIT initiation and viewing of BIT results.................................................................................... 3 2.6 Clearing BIT log ........................................................................................................................ 4 2.7 Direct parameter display viewing.............................................................................................. 4 2.8 Checking DTD status ................................................................................................................ 4 2.9 DTD insertion ............................................................................................................................ 5 2.10 DTD removal ............................................................................................................................. 5 2.11 Log book data viewing .............................................................................................................. 5 2.12 Configuring rotor blade tracker ................................................................................................. 5 2.13 Performing a manual acquisition .............................................................................................. 6 9 10
Effectivity: All
39-A-31-30-02-00A-001A-A 2002-07-08 Page 2 of 4
TDM 2128 UNCLASSIFIED 1.9 OPERATIONAL CHECKOUT PRELIMINARY SET UP .............................................................................. 1 1 Operational checkout preliminary procedures.................................................................................. 2 1.1 General...................................................................................................................................... 2 1.2 Preliminary setup ...................................................................................................................... 2 1.10 HUMS SYSTEM CHECKOUT .................... .............................................................................................. 1 1.11 HUMS SENSOR CHECKOUT .................... .............................................................................................. 1 1.12 HUMS TROUBLESHOOTING INTRODUCTION ...................................................................................... 1 1 Troubleshooting introduction ............................................................................................................ 1 1.13 HUMS FAULT SYMPTOM INDEX.............. .............................................................................................. 1 1 HUMS fault symptom index .............................................................................................................. 1 1.14 HUMS FAULT ISOLATION PROCEDURES ............................................................................................. 1 1 Troubleshooting procedures ............................................................................................................. 2 1.15 REMOVAL AND INSTALLATION ............... .............................................................................................. 1 1 Removal and installation................................................................................................................... 2 1.1 Data acquisition unit.................................................................................................................. 2 1.2 DAU battery............................................................................................................................... 2 1.3 Cockpit display Unit/Data transfer unit...................................................................................... 3 1.16 SERVICING.......... ...................................... .............................................................................................. 1 1 Servicing............................................................................................................................................ 1 1.1 Cleaning .................................................................................................................................... 1 1.2 Inspection.................................................................................................................................. 1 1.3 Scheduled maintenance ........................................................................................................... 1 1.17 CLEANING ........... ...................................... .............................................................................................. 1 1 Cleaning ............................................................................................................................................ 2
Effectivity: All
39-A-31-30-02-00A-001A-A 2002-07-08 Page 3 of 4
Effectivity: All
39-A-31-30-02-00A-001A-A 2002-07-08 Page 4 of 4
Chapter 1.1 HUMS introduction Table of contents

1 1.1 1.2 1.3 1.4 System description Component description List of HUMS major components List of dedicated sensors Associated equipment Page 1 1 1 2 2 Page HUMS LRUs 3
List of figures
1
System description
The Health and Usage Monitoring System (HUMS) is an integrated recording and monitoring system which provides the AB-139 helicopter with structural and transmission usage monitoring, transmission vibration monitoring, rotor track and balance, and engine power assurance recording. The HUMS is intended to improve airworthiness, improve availability, and reduce the cost of ownership of each aircraft by detecting and diagnosing potential failures, actual failures, monitoring usage, and providing information for potential maintenance action. The HUMS consists of an On-Board System (OBS) for monitoring and recording and a HUMS Ground Station (HGS) for detailed analysis and diagnosis of potential or actual aircraft vibration and usage-related maintenance actions which may be required. Data collected by HUMS sensors is transferred between the OBS and HGS through the use of a Data Transfer Device (DTD). Through the DTD aircraft specific initialization and configuration data can also be uploaded into the HUMS. The HUMS provides an operator display for access to aircraft and usage data as well as initiating builtin test (BIT) of the system and interfacing sensors, and performing engine power assurance checks. In addition, when a universal tracking device referred to as a rotor blade tracker is fitted to the aircraft, HUMS provides the operator the ability to perform a variety of rotor tuning measurements.
1.1
Component description
The HUMS Line Replaceable Units (LRU) are listed in paragraph 1.2 and illustrated in figure 1. The HUMS dedicated sensors which are Line Replaceable Items (LRI) are listed in paragraph 1.3. Equipment associated with HUMS are listed in paragraph 1.4.
1.2
List of HUMS major components

The following list of components covers the HUMS Line Replaceable Units (LRU): HUMS Components Data Acquisition Unit consisting of the following: Auxiliary Acquisition and Tracker Power Supply CCA Vibration Acquisition Unit CCA Enhanced Digital Processing Unit CCA System Power Supply Battery Number Used 1 1 1 1 1 1 Part Number 176990-01-01 175394-01-01 174357-03 176993-01-01 175434-01-02 174356-07
Effectivity: All
39-A-31-30-00-00A-011A-A Chapter 1.1 2002-07-08 Page 1 of 4
Cockpit Display Unit/Data Transfer Unit
180305-001
1.3
List of dedicated sensors

The following is a list of HUMS dedicated sensors: Sensor Main Rotor Tachometer Drivetrain Tachometer Tail Rotor Tachometer Rotor Track and Balance Accelerometers Transmission Vibration Accelerometers Load Factor Sensor Number Used 1 1 1 4 11 1 Part Number or Type Designation Electro Corp. P/N 3030AN Agusta P/N EA6300V083-001 Electro Corp. P/N 3025 Dytran Instruments P/N 3062A1 Agusta P/N 3G6340V00151 Magnatek P/N 3001-01-100-4
1.4
Associated equipment
The following associated equipment is used with HUMS. Item Data Transfer Device Rotor Blade Tracker Number Used 1 1 Part Number SDP3BI-384-101 29750000
Effectivity: All
Figure 1. HUMS LRUs
Effectivity: All
Effectivity: All
Chapter 1.2 Data acquisition unit function
Table of contents
1 Data acquisition unit (DAU)
Page 1 Page
List of figures
1 DAU identification view
Data acquisition unit (DAU)

The DAU (figure 1) is the systems interface with HUMS dedicated sensors as well as other aircraft sensors and interfaces. The DAU performs all of the HUMS on-board monitoring and control functions. The DAU receives it's inputs from the aircraft Modular Avionic Unit (MAU) via an ARINC 429 serial interface and other dedicated aircraft sensors (accelerometers, tachometers, etc.). The DAU processes these inputs and performs required analysis based on program execution and ground station entered configuration data. The DAU provides outputs to the operator via the Cockpit Display Unit(CDU)/Data Transfer Unit (DTU) in the form of visual (CDU) and recorded information on a Data Transfer Device (DTD) installed in the DTU. The DAU electronics are housed within an ARINC 404 form factor, one-half Air Transport Rack (ATR) short chassis. The DAU is comprised of three main functional sub-assemblies: ?? Enhanced Data Processing Unit (EDPU) ?? Vibration Acquisition Unit (VAU) ?? Auxiliary Acquisition and Tracker Power Supply (AATPS) ?? The EDPU assembly transmits and receives data to and from the aircraft Modular Avionic Unit (MAU) via an ARINC 429 serial interface. The EDPU will process, display, and/or store data as directed by its internal software and operator selected configuration. The EDPU also receives operator inputs from and sends display data to the Cockpit Display Unit (CDU). The VAU assembly receives and processes vibration frequency information from transmission and airframe vibration sensors and speed sensors. This information is used in the processing of HUMS health, usage, and maintenance data. If a Rotor Blade Tracker (RBT) is installed, the VAU will also receive this information and process this data for rotor tuning operations. The AATPS assembly processes the data from an aircraft load sensing accelerometer and provides the power for the RBT if one is installed on the aircraft. CDU/DTU display lighting is also controlled through the AATPS assembly.
Effectivity: All
Figure 1. DAU identification view
Effectivity: All
Chapter 1.3 Cockpit display unit/data transfer unit function
Table of contents
1 Cockpit display unit/data transfer unit
Page 1 Page
List of figures
1 2 Cockpit display unit/data transfer unit identification view Cockpit display unit/data transfer unit display
1 3 Page
List of tables
1 CDU/DTU controls and displays
Cockpit display unit/data transfer unit

The Cockpit Display Unit/Data Transfer Unit (CDU/DTU) (figure 1) is a dual function unit in a common housing. The CDU portion provides the HUMS system primary control and display functions while the DTU portion provides the means of transferring data to and from the HUMS to the ground equipment. The CDU/DTU is located in a cockpit console. The CDU function consists of a sixteen character, two-line alphanumeric, NVIS compatible display, a keypad, and signal conversion circuits. The keyboard consists of special function and cursor keys for data entry and display (figure 2), and system control. The CDU keypad provides the means of accessing CDU displays and entering various operation-related data. Table 1 describes the CDU key functions. The CDU communicates to the DAU via a dedicated bi-directional serial RS-422 bus. The DTU portion provides the interface between a Personal Computer Memory Card International Association (PCMCIA) card, also referred to as the Data Transfer Device (DTD), and HUMS via a dedicated bi-directional serial RS-422 bus. The DTU is used for the loading of DAU initialization data and configuration parameters and for downloading of aircraft HUMS data for use by the ground station. The CDU/DTU operates on aircraft supplied 28 VDC. The CDU/DTU also receives aircraft 5 VDC power for panel lighting.
Controls and displays

For a description of the controls and displays refer to table 1 and figure 2.
Effectivity: All
Control/Display
Table 1. CDU/DTU controls and displays Function The?(right arrow) key is used by the operator to move the cursor display to the right or left side of the display. The?(right arrow) key is also used to sequence through alpha or numeric data when in an operator enterable data field. The ?(down arrow) key is used by the operator to move the cursor display up or down on the display. The ?(down arrow) key is also used to sequence through alpha or numeric data when in an operator enterable data field. Pressing the ENT (enter) key selects the menu option at the current cursor position. The ENT key is also used to select operator enterable data fields and is used to cause the DAU to accept operator entered data after data entry is complete. Pressing the PAGE key will cause the display to cycle to the next available page when the ? (down arrow) is displayed on the menu. Continuing to press the PAGE key will cycle through all available pages and then return to the first page. The CLR (clear) key is used to perform three functions: (1) Used to clear informational messages.
ENT
PAGE
CLR
(2) When viewing any menu other than the main menu, the CLR key is used to navigate up the menu structure to access the previous menu level(s). (3) Abort a manually commanded vibration or engine power assurance measurement.
EVNT
The EVNT (event) key is used to manually initiate a general vibration measurement. The "down arrow" display indicates to the operator that additional display pages are available for viewing. The "down arrow" will always be displayed on the bottom line of the display and is used in conjunction with the PAGE key. The "cursor" display indicates the current selectable item on the display. The cursor will always appear in either the leftmost or rightmost position on the line. When on the left of the line, the cursor will appear as > and when on the right of the line, the cursor will appear as <. The cursor is
> or <
moved by using the ?(right arrow) and the ?(down arrow) keys. Pressing the?(right arrow) key will cause the cursor to move from the left to the right or from the right to the left on the display. Pressing the ?(down arrow) key will cause the cursor to move from top to bottom or from bottom to top on the display. When pressed ejects DTD from DTU. The ejector button is in view in the DTD compartment when the DTD access door is open.
Ejector button
Effectivity: All
TDM 2128 UNCLASSIFIED Access Door Release Power indicator (red)
Allows DTD access door to flip open to gain access to DTD. The power light emitting diode (LED) indicator is in view in the DTD compartment when the DTD access door is open. The indictor comes on when power is applied to the DTD.
The write cycle LED indicator is in view in the DTD compartment when the Write cycle DTD access door is open. The indicator comes on when there is no data indicator (green) transfer activity, indicating it is safe to remove a DTD.
Figure 1. Cockpit display unit/data transfer unit (CDU/DTU) identification view
Effectivity: All
> MAINT
RBT
DTD SYS
STS VAL
EVNT
PAGE
ENT
CLR
Access Door Release
DTD Access Door
CDU/DTU with Door Closed
> MAINT
RBT
DTD SYS
STS VAL
EVNT
PAGE
ENT
CLR
Ejector Button
Power Indicator Write Cycle Indicator
CDU/DTU with Door Open
Figure 2. Cockpit display unit/data transfer unit (CDU/DTU) front panel view
Effectivity: All
Chapter 1.4 HUMS dedicated sensors function Table of contents

1 2 2.1 2.2 2.3 3 3.1 3.2 3.3 General Accelerometers Transmission vibration monitoring accelerometer Rotor track and balance accelerometer Load accelerometer Tachometers Main rotor tachometer Tail rotor tachometer Drivetrain tachometer Page 1 1 1 1 2 2 2 2 2 Page Accelerometer details Tachometer details 2 3
List of tables
1 2
General
HUMS employs the use of accelerometers for vibration monitoring and tachometers for speed monitoring. The following paragraphs provide a description of each of these types of sensors.
Accelerometers
For the purpose of vibration and load sense monitoring, the HUMS utilizes three different types of accelerometers: ?? ?? ?? Transmission vibration monitoring (TVM) Rotor track and balance (RTB) Load factor
A total of 15 accelerometers are placed at strategic locations throughout the aircraft to monitor transmission, drive train, and rotor related aircraft vibrations. The accelerometers are used to acquire vibration data which is provided to the DAU Vibration Acquisition Unit (VAU). The raw data acquired from each accelerometer (sine waves in multiple frequency bands) is interpreted, filtered and manipulated by algorithmic software in the DAU. The refined data then provides signature frequencies and normal characteristics for each rotating element (gears, bearing assemblies and shafts) of the aircraft. This signature data is then used to establish the normal vibration characteristics for each rotating element. With this data, the HUMS then establishes acceptable limits and tolerances for each rotating element. Via configurable software, the parameters of acceptable limits and tolerances can be modified to establish when the system should notify the operator or technician that a limit has been exceeded or a potential problem exists. In addition, a separate load factor sensing accelerometer monitors aircraft acceleration in the vertical direction to measure the aircraft load factor.
Effectivity: All
TDM 2128 UNCLASSIFIED The following paragraphs provide a brief description each of the three types of monitoring accelerometers used in the HUMS. Table 1 lists the accelerometer number, general location, and a brief general description.
2.1
Transmission vibration monitoring

HUMS utilizes 11 Transmission Vibration Monitoring (TVM) accelerometers to facilitate transmission and drivetrain vibration monitoring. These accelerometers have a sensitivity of 10mV/G. The TVM accelerometers are hermetically sealed, piezo-electric, annular shear type accelerometers with integral electronics. The accelerometer and electronics have an insulated, double shielded, housing and are electrically isolated from the accelerometer case. The accelerometer case is a through-hole design with a centre bolt. The accelerometers have side mounted electrical connections allowing for the accelerometer to be mounted using a single centre bolt with the cable extended parallel to the mounting surface. Refer to Table 1 for accelerometer numbers, location, and a basic description.
2.2
Rotor track and balance

The Rotor Track and Balance (RTB) accelerometers are used to support rotor track and balance vibration measurements and rotor tuning operations. The HUMS uses 4 RTB Accelerometers which are mounted near the aircraft main and tail rotors to monitor rotor related and asynchronous vibration components. These accelerometers are hermetically sealed, piezo-electric accelerometers with integral electronics and have a sensitivity of 25mV/G. The accelerometer and electronics are electrically isolated from the accelerometer case and are a stud-mounted package with an integral electrical connector. Refer to table 1 for accelerometer number, location, and description.
2.3
Load factor
The load factor accelerometer is designed to sense aircraft vertical acceleration to calculate the aircraft load factor. The accelerometer is a hermetically sealed instrument for simultaneous measurement on one vertical axis. The accelerometer consists of an internal seismic sensor and integral signal conditioning electronics capable of measuring acceleration in the vertical direction between +6g(up) to -3g(down). The load factor accelerometer operates on aircraft 28 VDC and is mounted in the floor area of the main cabin area. Table 1. Accelerometer details Location Accelerometer Type Engine #1 Engine #2 Annulus Gear (Forward) Annulus Gear (Right) Annulus Gear (Aft) Tail Drive Shaft Take Off Tail Drive Shaft Hangar Bearing Intermediate Gear Box (IGB) Tail Gear Box Engine #1 (2nd Stage) Engine #2 (2nd Stage) Main rotor (Lateral) Main rotor (Vertical) Tail rotor (Lateral) Tail Rotor (Vertical) Main Cabin Floor Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Transmission Vibration Monitoring (TVM) Rotor Track and Balance (RTB) Rotor Track and Balance (RTB) Rotor Track and Balance (RTB) Rotor Track and Balance (RTB) Load factor sensing
Accelerometer A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A20 A21 A22 A23 -
Effectivity: All
Tachometers
The HUMS uses speed sensing tachometers to measure rotor and drive train frequencies to perform component usage and health monitoring. The frequency (speed) data provided by the tachometers is used to determine component operating speeds and augment accelerometer data for transmission vibration monitoring measurements.
3.1
Main rotor tachometer

The HUMS main rotor tachometer is a Variable Reluctance Speed Sensor (VRS) that measures main rotor speed and provides this information to the HUMS DAU in the form of an analogue signal. The tachometer is housed an a stainless steel cylinder and attached near the main rotor. The tachometer is fully self-contained and powered. The tachometer has a coil resistance of 910 to 1200 ohms and is capable of providing a minimum output of 190V peak to peak. The main rotor tachometer provides a one pulse per revolution output.
3.2
Tail rotor tachometer

The HUMS tail rotor tachometer is also a Variable Reluctance Speed Sensor (VRS) that is similar in appearance and operation of the main rotor tachometer described in the previous paragraph. The tail rotor tachometer is attached near the tail rotor assembly. The tachometer has a coil resistance of 275 to 330 ohms and is capable of providing a minimum output of 55 V peak to peak. The tail rotor tachometer provides a one pulse per revolution output.
3.3
Drivetrain tachometer
The drivetrain tachometer installed on the main gearbox provides a multi-pulse (29 pulses/rev) output of transmission rotation speed. The output is a high frequency sinusoidal signal input to the DAU. Table 2. Tachometer details Tachometer Type Variable Reluctance Speed Sensor (1 pulse/rev) Variable Reluctance Speed Sensor (1 pulse/rev) multi-pulse (29 pulses/rev)
Tachometer AZ1 AZ2 AZ3
Location Main rotor Tail rotor
Drivetrain (Transmission)
Effectivity: All
Effectivity: All
Chapter 1.5 HUMS operation Table of contents

1 2 3 3.1 3.2 3.3 4 5 6 7 7.1 7.2 8 8.1 8.2 8.3 9 10 10.1 10.2 10.3 10.4 Introduction Equipment interface HUMS initialization and startup Initialization Startup DTD operations HUMS operations and ground/flight regimes Data acquisition and processing Transmission vibration monitoring Rotor track and balance operations Rotor health monitoring Rotor tuning Usage monitoring Logbook functions Structural usage monitoring (SUM) Transmission usage monitoring (TUM) Engine power assurance System built in test Start-up BIT Periodic BIT Initiated BIT Status and BIT log displays Page 1 2 4 4 4 4 4 5 7 8 8 9 9 9 10 11 12 12 13 13 13 13 Page HUMS block diagram 3 Page HUMS operation start/stop criteria Aircraft input parameters Direct parameter display list Transmission monitoring components RTB monitoring components HUMS status and BIT log displays 5 6 7 8 8 14
List of figures
1
List of tables
1 2 3 4 5 6
Introduction
The Health and Usage Monitoring System (HUMS) is an aircraft health and usage monitoring system. The HUMS provides transmission health monitoring, rotor track and balance (RTB), rotor health monitoring, and aircraft and transmission usage monitoring. Aircraft data is acquired from the aircraft Modular Avionics Unit (MAU) and dedicated sensors and processed by the onboard system element of the system to provide health and usage data. This data is stored on a Data Transfer Device (DTD) for subsequent download to the HUMS Ground System (HGS). The HGS provides for additional processing and analysis of the HUMS data. The data acquisition and processing of certain HUMS functions are configurable. The initialization information is loaded onto the DTD via the HGS for subsequent upload into the
Effectivity: All
TDM 2128 UNCLASSIFIED onboard system. The DTD is also used as the means to upload new configuration data to the onboard system. The HUMS theory of operation is divided into the following areas of discussion: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Equipment Interface HUMS initialization and Startup DTD Operations HUMS operations and regimes Data acquisition and processing Transmission vibration Monitoring Usage Monitoring Rotor track and balance operation Engine Power Assurance Built in Test
Equipment Interface
The onboard element of HUMS is comprised of the Data Acquisition Unit (DAU), Cockpit Display Unit/Data Transfer Unit (CDU/DTU), and several accelerometers and tachometers. The functional interconnect of the airborne system components is shown in Figure 1. The HUMS acquires aircraft-related data through an ARINC 429 serial interface with the aircraft Modular Avionics Unit (MAU). Serial data is received from the MAU to HUMS for monitoring, processing, and storage on the DTD and HUMS status information is transmitted back to the MAU. Two RS-422 serial data channels are used to communicate with the HUMS CDU/DTU. One serial channel is used to communicate with the CDU portion to transfer display data to the CDU and receive keypad data back from the CDU. The other serial channel is used to transfer data to and from a DTD installed in the DTU portion of the CDU/DTU. HUMS continuously monitors both the ARINC 429 and RS-422 communication channels to ensure proper communications are maintained. If any channel becomes inoperative the user is notified with an advisory message on the CDU/DTU display. Accelerometers are installed in various locations on the aircraft transmissions to detect the vibrations produced by the various transmission-associated components. Accelerometer outputs are connected directly to the DAU where the analog voltages are converted to digital and processed for use in vibration monitoring, rotor track and balance, and rotor tuning calculations. A special type of accelerometer, is a vertical load sensing accelerometer used to detect vibration levels in the vertical direction. Power is supplied separately to this accelerometer from the aircraft +28 Vdc power source. Remaining analog input signals to HUMS are received by 3 tachometers. The output values from these represent the speed values for the rotating components they are connected to. The DAU interfaces to one additional analog speed input from a temporary fit Universal Blade Tracker referred to as Rotor Blade Tracker. When an RBT is installed, the DAU provides the +24 Vdc power to the RBT as well as the power to the RBT lamp if being used at night. Control of both operating power and lamp power is done through the CDU/DTU via operator selection. The output signal from the RBT is a pulse train and is used in rotor tuning calculations. The HUMS DAU and CDU/DTU receive +28 Vdc power from the aircraft through a dedicated circuit breaker(s). +5 Vdc lighting power from the pedestal lighting supply is also applied to both the DAU and CDU/DTU. The +5 Vdc applied to the CDU/DTU is used to control the brightness level of the pushbutton switches. The +5 Vdc supplied the DAU is used to monitor the voltage level of the lighting. The DAU converts the voltage to a digital value then supplies a digital lighting level code to the CDU/DTU over the RS-422 channel where the code is translated into the correct voltage for the alphanumeric display.
Effectivity: All
+28VDC 5A
Data Acquisition Unit (DAU) 1.5A CDU/DTU ARINC 429 RS-422
+5VDC (Panel Lighting) +28VDC
Modular Avionic Unit (MAU) ARINC 429
Enhanced Data Processing Unit (EDPU) RS-422
Cockpit Display Unit (CDU)
Data Transfer Unit (DTU)
RTB Accelerometers (4) TVM Accelerometers (11)
Data Transfer Device (DTD) (PCMCIA CARD)
11
Vibration Acquistion Unit (VAU) Main Rotor Tachometer
Tail Rotor Tachometer Rotor Data DrivetrainTachometer Universal Tracking Device (UTD)*
+24 VDC +28VDC 1A Load Acelerometer Auxilary Acquistion and Tracker Power Supply (AATPS)
+12 VDC (Lamp Power)
+5VDC (Panel Lighting)
* When Installed
Figure 1. HUMS block diagram
Effectivity: All
3
3.1
HUMS Initialization and Startup

Initialization
HUMS requires several configurable parameters for normal operation. Some of these parameters are preloaded at the factory while others are aircraft specific and must be loaded prior to using HUMS for the first time. Those parameters loaded at the factory are referred to as configuration parameters and typically are not changed unless the operational software within the DAU has been updated by the factory. If configuration parameters do require updating in the field, HUMS provides the capability to upload new configuration data through the use of a special configuration DTD. When a HUMS DAU is first installed into an aircraft certain aircraft specific values must be initialized before an operation can begin. These parameters are referred to as initialization parameters and affect logbook and usage monitoring functions. The initialization values are generated on the ground station and transferred to a DTD as an initialization file. The operator performs an initialization upload to load HUMS DAU non-volatile memory with the aircraft specific data. Once these values are loaded into the DAU for the first time they only need to be updated when the HUMS DAU is replaced or new values from the ground station are desired.
3.2
Startup
Upon power application, HUMS performs a predefined startup sequence controlled by the EDPU control program in the DAU. Immediately at power up, the first task performed is Startup Built-in Test (SBIT). Refer to paragraph 10.1 for a description of SBIT. SBIT checks all internal functions of the DAU, checks the externally connected sensors, and checks the CDU/DTU. Following completion of SBIT, the DAU checks to make sure a correctly configured DTD is installed in the CDU/DTU and the amount of space left in each of the files on the DTD. The DTD must have been previously formatted and initialized on the ground station in order for HUMS to record data to it. After completion of all DTD checks, the DAU checks for communication with the MAU and obtains the aircraft identification number and the time and date to be used by HUMS. If the time or date received from the MAU is not received, the operator can enter new values through the CDU/DTU. Values entered are only used by HUMS and do not affect any other aircraft system values. The aircraft identification number received from the MAU is compared with the identification number stored in HUMS non-volatile memory to ensure both agree. If the aircraft ID checks good then HUMS system processing begins.
3.3
DTD operations
Normal operation of HUMS relies on having a DTD installed upon power application. A DTD must be present in order for HUMS data to be recorded onto the DTD for later analysis on the ground station. The DTD provides sufficient capacity to store data for 25 operating hours. If any of the HUMS vibration data files or engine power assurance data files on the DTD become full the data is overwritten on a first in first out basis. The same DTD can be used interchangeably on any HUMS-equipped aircraft so long as there is still sufficient space left on the DTD for recording. HUMS will operate without a DTD installed; however, no data can be stored for later analysis. HUMS will store current operation usage data within its memory during an operation and if a DTD is subsequently inserted before an operation is completed the data will be written to the DTD without any loss. If a DTD is inserted after the completion of a HUMS operation no data will be written to the DTD.
HUMS operations and ground/flight regimes

All HUMS data collections are based on "HUMS operations". HUMS operation start and stop times are defined by certain aircraft conditions as shown in Table 1.
Effectivity: All
TDM 2128 UNCLASSIFIED Table 1. HUMS operation start/stop criteria Criteria A "HUMS Operation" starts when at least one engine gas generator speed (NG) is greater than 50%. Ground Idle (both engines gas generator speed below 10% and the aircraft is in GROUND MODE).
Operation Start Stop
During each HUMS operation the HUMS analyzes aircraft data received over the ARINC 429 serial interface and from dedicated HUMS sensors. This information is used to calculate the aircraft current ground/flight state and determine the current ground/flight regime used for usage and vibration data collection. Flight regimes are defined as logical combinations of any of the measured flight parameters divided up to uniquely cover the entire flight envelope of the aircraft. At any point in time, the aircraft will normally be in one and only one regime. HUMS flight regime recognition is divided into two separate regime types based on specific HUMS operations. The two types of HUMS regime recognition are: ?? ?? VAU (TVM and rotor health monitoring) Usage (SUM and TUM)
HUMS is capable of recognizing up to 256 different aircraft regimes. Of these, 64 are allocated to VAU (TVM) type regimes and 192 are allocated for usage type regimes. HUMS VAU regimes are configurable and can be uploaded to the aircraft system using a configuration DTD. All regimes detected by HUMS are recorded in a time history log on the DTD. This log contains a regime identifier, the time the regime was detected, and the duration of the regime. HUMS will also monitor and record any detection of any anomalous flight conditions that cause erroneous regime recognition.
Data acquisition and processing

The HUMS acquires and processes aircraft data from the Modular Avionics Unit (MAU) via an ARINC 429 serial interface. Refer to table 2 for a list of aircraft parameters received by HUMS for processing. Aircraft data received is used by the various HUMS functions, detecting when certain events occur, and for calculating various other aircraft parameters such as rotor torque, roll rate, etc. Parameters received from the aircraft as well as calculated parameters are recorded to the DTD continuously during an operation. If an input parameter is determined to be invalid by HUMS it is no longer used by HUMS in any processing or calculations and also recorded as a failure on the DTD. Certain calculated parameters and parameters received from the MAU are available to the operator for display on the CDU. Refer to table 3 for a list of those parameters available for viewing.
Effectivity: All
Table 2. Aircraft input parameters Description Aircraft ID Anti-Ice On Barometric Altitude Date EAPS On EAPS Pressure Status Engine 1 ITT Engine 2 ITT Engine 1 Nf Engine 2 Nf Engine 1 Ng Engine 2 Ng Engine 1 Out Engine 2 Out Engine 1 Torque Engine 2 Torque Greenwich Mean Time Gnd/Flt Status Heater On IGB Oil Temperature Main Rotor Speed MAU 1 Status MAU 2 Status MGB Oil Temperature MGB Oil Pressure Outside Air Temperature Pitch Angle Radio Altitude Roll Angle Tail Rotor Pedal Position TGB Oil Temperature True Airspeed True Heading Vertical Speed Yaw Actuator 1 Position Yaw Actuator 2 Position
Effectivity: All
Table 3. Direct parameter display list Name Aircraft ID Date Greenwich MeanTime Gnd/Flt Status True Airspeed Vne Vertical Speed Barometric Altitude Density Altitude Radio Altitude True Heading Outside Air Temperature Roll Angle Roll Rate Pitch Angle Pitch Rate Yaw Rate Load Factor Engine Engine 1 Ng Parameters Engine 1 Nf Engine 1 ITT Engine 1 Torque Engine 2 Ng Engine 2 Nf Engine 2 ITT Engine 2 Torque Drive System MGB Oil Pressure Parameters MGB Oil Temperature IGB Oil Temperature TGB Oil Temperature Main Rotor Speed Main Rotor Torque Tail Rotor Torque Tail Rotor Pedal Position Yaw Actuator 1 Position Yaw Actuator 2 Position Type Aircraft Parameters
Transmission vibration monitoring

The HUMS performs vibration monitoring of the transmission components listed in Table 4. The HUMS monitors the vibration of these components to verify their overall health. Transmission vibration monitoring occurs automatically based on certain configured flight regimes and consists of a suite of diagnostic techniques comprised of shaft, gear and bearing vibration analysis. Vibration data acquisition can also be initiated manually whenever engines are running by pressing the EVNT key on the CDU/DTU. This function is only used by maintenance personnel for diagnosing possible HUMS malfunctions. The HUMS vibration monitoring acquisition and processing functions are provided by the DAU Vibration Acquisition Unit (VAU). The HUMS utilizes 11 Transmission Vibration Monitoring
Effectivity: All
TDM 2128 UNCLASSIFIED (TVM) accelerometers to sense transmission and drivetrain vibrations. In addition, the VAU receives component speed information from 3 aircraft mounted tachometers. The VAU compares the acquired vibration data against configured internal data parameters and threshold levels. The calculated and raw vibration and speed data are transferred to the DAU Enhanced Data Processing Unit (EDPU) for storage onto the DTD. The is later transferred via the DTD to the HGS for calculation and analysis. Table 4 lists the components monitored by the HUMS during transmission health monitoring and the HUMS sensors involved in these measurements. For information on the location of the dedicated sensors listed in the table below refer to Chapter 1.4. Table 4. Transmission monitoring components Components Monitored Accelerometers Tachometer Purpose Used Engine to main gear box Gear input shaft balance, A1, A2 AZ3 drive shafts alignment, and faults. Main gearbox shaft and Gear, shaft, and bearing faults. A1-A6, A10, A11 AZ3 gears Bearing faults upon the input Main gearbox bearings A1-3,A6 AZ3 and output shafts of the main gear box Accessory gearbox gears, A1, A2, A6 AZ3 Shaft and bearing faults shafts, and bearings Tail rotor drive shaft and A7 AZ3 Shaft and bearing faults hanger bearings Intermediate and tail gearbox gears, shafts, and A8, A9 AZ2 Gear, shaft, and bearing faults bearings Rotational check and shaft Oil cooler fan A6 AZ3 vibration
7
7.1
Rotor track and balance operations

Rotor health monitoring
The HUMS monitors the health of the main and tail rotors through the use of Rotor Track and Balance (RTB) accelerometers and rotor tachometer inputs. To calculate rotor unbalance and other failures, the HUMS uses four RTB accelerometers which are mounted near the main and tail rotors. The accelerometers monitor rotor related and asynchronous vibration components. Rotor health monitoring occurs automatically based on certain configured flight regimes. Table 5 lists the components monitored by the HUMS during rotor health monitoring and the HUMS sensors involved in these measurements. For information on the location of the dedicated sensors listed in the table below refer to Chapter 1.4.
Components Monitored Main rotor lateral/vertical Tail rotor lateral/vertical
Table 5. RTB monitoring components Accelerometers Tachometer Purpose Used A20, A21 AZ1 Rotor unbalance and faults A22,A23 AZ2 Rotor unbalance and faults.
Effectivity: All
7.2
Rotor tuning
When a Rotor Blade Tracking (RBT) device is fitted to the aircraft, the HUMS has the ability to perform rotor track and balance tuning operations to minimise rotor induced vibration levels. Using the components listed in Table 5 and the RBT, the HUMS performs blade tracking lead/lag and balance measurements, when initiated by the operator at the CDU/DTU. Any one of up to eight different types of measurements to perform are selectable by the operator. Upon completion of the acquisition, results are displayed on the CDU/DTU and recorded to the DTD. Values for display and parameters used for rotor tuning are configurable. Note: The RBT is an aircraft temporary fit item and is only used when rotor track and lead/lag measurements and operations are to be performed.
Usage monitoring
HUMS usage monitoring provides the operator with a means of recording aircraft operational (Logbook data), structural, and transmission usage data. Aircraft data is acquired from the MAU ARINC 429 serial interface and a dedicated HUMS load factor sensor. The aircraft data is then processed by the DAU based on a set of configurable software routines and flight regimes. After processing, HUMS usage data is stored in the DAU NVM (Logbook) and on the DTD (Logbook, SUM, and TUM). Usage monitoring begins at the start of an operation. Usage data is recorded to the DTD upon completion of an operation. If any usage file on the DTD becomes 80% full HUMS will alert the user with an advisory message identifying the file. Recording to the DTD will continue until the file is 100% full and then either stop or overwrite earlier data depending upon how the DTD was initialized on the ground station. HUMS usage data is divided into three separate functional areas: ?? ?? ?? Logbook functions Structural usage monitoring (SUM) Transmission usage monitoring (TUM)
8.1
Logbook functions
The logbook functions give the operator the ability to view basic aircraft data that may be recorded in the aircraft logbook. The logbook data is stored in the DAU's NVM and also on the DTD for later viewing on the HGS. Logbook data from the last operation or a summary total of all logbook data can be displayed on the CDU when requested by the operator. Cumulative logbook totals determined to be invalid will remain invalid until new values are uploaded via the DTD. Logbook data is comprised of the following aircraft and HUMS operation data:
8.1.1
Operation time Operation time is the total operating time for the last HUMS operation or the cumulative total operating time for all HUMS operations. The start of an operation begins when one engine enters a ground idle and the end of an operation is when the aircraft is on ground and both engines are shut down. Although only operating time is displayable, the start, stop, operating and total operating time are written to the DTD for review on the HGS.
8.1.2
Flight time Flight time is the total flight time for the last HUMS operation or the cumulative total flight time for all HUMS operations. Flight time begins at takeoff and ends at landing. Although only flight time is displayable, the takeoff time, landing time, flight time and total flight time are written to the DTD for review on the HGS.
Effectivity: All
TDM 2128 UNCLASSIFIED 8.1.3 Flight time fail time Flight time fail time is the total time during the last operation that the ground/flight status was detected as being invalid or the cumulative total flight time fail time for all HUMS operations. 8.1.4 Landing count Landing count is the total number of landings that occurred during the last HUMS operation or the cumulative total landings for all HUMS operations. 8.1.5 Rotor starts Rotor starts is the number of rotor starts during the last HUMS operation or the cumulative total number of rotor starts for all HUMS operations. 8.1.6 Rotor turning time Rotor turning time is the total time the main rotor has been turning during the last HUMS operation or the cumulative total time the rotor has been turning for all HUMS operations. 8.1.7 Rotor speed fail time Rotor speed fail time is the total time during the last operation that the main rotor speed was detected as being invalid or the cumulative total time the rotor speed was invalid for all HUMS operations. 8.1.8 One engine inoperative (OEI) time OEI time is the total time during the last operation that the torque of an engine was below 10% while in a flight mode or the cumulative total time that engine torque was below 10% for all HUMS operations.
8.2
Structural usage monitoring (SUM)

During each HUMS operation the HUMS continuously acquires and calculates aircraft flight data to calculate aircraft structural usage during certain operational time periods (regimes). Based on the current detected aircraft regime, HUMS SUM processing calculates the average value of the following parameters over the duration of each regime: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Roll angle Roll rate Pitch angle Pitch rate Yaw rate True airspeed Longitudinal acceleration Ratioed airspeed Load factor Engine 1 torque Engine 2 torque Density altitude Radio altitude
Effectivity: All
TDM 2128 UNCLASSIFIED As part of the SUM function the HUMS will generate a SUM log for each regime detected during a HUMS operation. The SUM log data is recorded on the DTD at the end of each HUMS operation and will include the averaged values of the parameters mentioned above and the following additional data: ?? ?? ?? ?? Regime identifier Regime Time spent in each regime Number of SUM failures during a operation Aircraft landing counters
The HUMS SUM function also provides two separate counters, a SUM failure time and landing counters, for use in tracking and recording additional SUM data. A SUM failure time counter is used to record the amount of accumulated SUM failure time that has occurred during a HUMS operation. SUM failures occur when there is a failure in aircraft regime detection. Sum failure data will be recorded to the DTD at the end of each HUMS operation. Three separate landing counters are also provided for tracking and recording the total number of aircraft landings for the following three separate landing types: ?? ?? ?? Normal One engine inoperative (OEI) Autorotation
The landing totals for all three types of landings are transferred to the DTD at the end of each HUMS operation.
8.3
Transmission usage monitoring (TUM)

During each HUMS operation the HUMS continuously acquires aircraft engine and rotor data to track the usage of transmission components. During TUM the HUMS maintains the following two internal logs of TUM data: ?? ?? Time history log Event log
8.3.1
TUM time history log The TUM time history log is used to accumulate the amount of time engine and rotor torque and speed values are within certain program defined bands. The following aircraft data is used in the TUM history log: ?? ?? ?? Engine 1 and 2 torque Main and Tail rotor torque Main rotor speed
In addition to the TUM history log, HUMS also maintains a failure time counter to track the amount of time any of the TUM history log values are invalid. At the end of the HUMS operation, the TUM history log and the failure time counter data are transferred to the DTD.
Effectivity: All
TDM 2128 UNCLASSIFIED 8.3.2 TUM event log The HUMS continuously monitors several aircraft parameters to determine if a parameter has exceeded a pre-defined, software configurable limit. If a parameter has exceeded this predefined limit HUMS will record the time the exceedance event occurred, the duration of the event, and the exceeding parameter. This information is recorded on the DTD for later use by the HGS. The following aircraft parameters are monitored by HUMS for exceedances and entry into the TUM event log: ?? ?? ?? ?? Engine 1 and 2 speed Engine 1 and 2 torque Main and Tail rotor torque Main rotor speed
Engine power assurance

The HUMS provides the capability of calculating engine Ng and MGT power assurance margins by initiating an engine power assurance (EPA) check for either engine. The EPA is initiated by the operator via the CDU and can only be performed in an in-flight configuration. Once initiated by the operator, the HUMS will verify that the aircraft EAPS, heater, and anti-ice systems are off and perform a regime stability check to verify the aircraft regimes required for the EPA are stable and within tolerance bands for data acquisition. If either of these conditions are not met the HUMS will terminate the acquisition and inform the operator via a CDU display. Once initiated, EPA checks require about TBD seconds to complete and the results are automatically displayed on the CDU and recorded on the DTD.
10
System built in test

The HUMS provides an extensive set of built in test (BIT) functions to verify that the system is operating correctly. The BIT function provides a means of detecting failures within the HUMS system and interconnecting sensors as well displaying and recording of the BIT results. BIT also detects RBT failures if the RBT is fitted to the aircraft and powered up. The DAU records HUMS BIT results to non-volatile memory in a BIT log and to the DTD. BIT test failures recorded are latched in a BIT status word and will not return to a pass condition even if BIT subsequently passes. BIT test failures can only be returned to the pass condition when the operator clears the BIT log. The only exception to this are those failures relating to the DTD. If a DTD error is detected and the operator takes the appropriate corrective action for the failure, the failure will be cleared automatically by the system without having to clear the BIT log. BIT results are displayed in two different ways on the CDU. Detailed BIT status is available through viewing of the HUMS BIT log and a BIT summary is available for viewing on the CDU top level display in the system status message area. Detailed BIT status is used by maintenance personnel for troubleshooting and isolating HUMS failures. Accessing and clearing of the BIT log is accomplished through menu selection on the CDU. The BIT summary display is primarily intended for the aircrew as an advisory to indicate the status of HUMS and is not generally used by maintenance personnel for troubleshooting purposes. If there are any failures detected by BIT, the top level status display is automatically updated. The highest priority message is always displayed first. Refer to table 6 for a list of HUMS status messages and corresponding BIT Log entries. There are three type of BIT performed on the HUMS. These are Start-up BIT (SBIT), periodic BIT (PBIT), and Initiated BIT (IBIT). The following paragraphs describe the details of the three types of HUMS BIT.
Effectivity: All
10.1
Start-up BIT
Start-up BIT (SBIT) is initiated any time the HUMS begins a power-up sequence or after power interruptions of more than 5 minutes. The HUMS assemblies that perform these tests include the following: ?? DAU Enhance Data Processing Unit (EDPU) Assembly ?? DAU Vibration Acquisition Unit (VAU) Assembly ?? DAU Auxiliary Acquisition and Tracker Power Supply (AATPS) Assembly ?? CDU/DTU Each DAU assembly performs autonomous start-up BIT testing and communicates their respective results to the EDPU assembly, which acts as the central control and processing entity for the HUMS BIT. SBIT tests also include tests of the DTD (if present) and all dedicated sensors as well as a communications check of the serial data channel to the MAU. Because the engines are not running at power up, SBIT cannot completely determine if the tachometers are producing proper output signals. In this case, the tachometers are checked whenever a manual vibration acquisition is commanded by the operator once the engines are running. SBIT requires no operator action to initiate and is automatically scheduled during the system powerup sequence. SBIT tests take approximately 10 seconds to complete. Any abnormal results are automatically displayed on the CDU for operator acknowledgement and also communicated to the MAU over the RS-429 serial bus. Within two minutes of application of power, the HUMS is fully functional, including all vibration acquisition and processing functions.
10.2
Periodic BIT
After completing SBIT, the DAU performs periodic BIT (PBIT) testing at approximately one minute intervals. PBIT is a set of non-intrusive background tests that continually verify the operation and ability of the DAU and its ability to communicate with the CDU/DTU, DTD, sensors, and the MAU. As part of PBIT, reasonableness tests are continuously performed on all data received from the HUMS sensor inputs both during and after an operation, as long as the engines are running. PBIT failures are automatically displayed on the CDU in the status message area of the HUMS top-level menu page.
10.3
Initiated BIT
Initiated BIT (IBIT) is almost identical to SBIT. The difference is in the method of initiation and the performance of some additional tests that are unique to IBIT. In addition to those tests performed during SBIT, IBIT also performs CDU display pixel tests and keypad pushbutton tests. These additional tests require the operator to visually verify the proper operation of the CDU display and manually verify each of the CDU pushbutton keys are operating properly. IBIT is inhibited after the start, and during the duration, of any HUMS operation. IBIT results are stored in the HUMS fault log and available for display by the operator. Fault log data cannot be displayed once a HUMS operation has started.
10.4
Status and BIT log displays

Table 6 lists the HUMS status messages together with the BIT log entries and the affects upon HUMS operation.
Effectivity: All
TDM 2128 UNCLASSIFIED Table 6. HUMS status and BIT log displays BIT LOG ENTRY FAILURE CONDITION
HUMS STATUS MESSAGE ID FAIL
SYSTEM EFFECT
None
OP# FAIL
None
DAU FAIL
EDPU CFG
DAU FAIL EDPU OFP CHKSUM DAU FAIL EDPU FLTNG PT DAU FAIL MAIN W/D TIMER DAU FAIL MAIN TIMER DAU FAIL IOP RESPONSE DAU FAIL IOP W/D TIMER DAU FAIL IOP TIMER DAU FAIL ERM FORMAT DAU FAIL 429 REGISTER DAU FAIL ERM BAD SCTR DAU FAIL 429 CONTROLLER DAU FAIL 429 WRAP DAU FAIL REAL TIME CLK DAU FAIL RTC RAM CHKSUM DAU FAIL ERM PTRN INTEG DAU FAIL RS422 CH 3 DAU FAIL RS422 CH 2 DAU FAIL AATPS RESPONSE DAU FAIL AATPS CAL MUX DAU FAIL AATPS A/D CAL CONFIG FAIL EDPU
Aircraft ID number stored in DAU is corrupted or aircraft ID received from MAU is invalid or no aircraft ID received from MAU. Operation number read from DTD doesn't agree with operation number stored in DAU. Internal DAU hardware failure
Cumulative logbook values are invalidated and no data downloaded to ground station.
No data downloaded to ground station.
Partial or complete loss of HUMS functions depending upon type of failure.
EDPU configuration parameters corrupted or not loaded.
Loss of all HUMS functions
Effectivity: All
TDM 2128 UNCLASSIFIED HUMS STATUS MESSAGE VAU CFG BIT LOG ENTRY FAILURE CONDITION SYSTEM EFFECT
CONFIG FAIL VAU
VAU configuration parameters corrupted or not loaded. DTU not responding to commands from DAU. DTD cannot be read from or written to. DTD format incorrect. None
DTU FAIL DTD FAIL DTD FMT NO DTD VAU FAIL
VAU DEGR
CDU/DTU FAIL DTU RESPONSE DTD FAIL WRAP DTD FAIL FORMAT DTD NOT PRESENT DAU FAIL VAU FAILED DAU FAIL VAU RESPONSE DAU FAIL VAU LP PROC DAU FAIL VAU LP CHKSUM DAU FAIL VAU LP RAM DAU FAIL VAU LP DP RAM DAU FAIL VAU OFP CHKSUM DAU FAIL VAU RAM DAU FAIL VAU PRESENCE DAU FAIL VAU ADC 0 DAU FAIL VAU ADC 1 DAU FAIL VAU ADC 2 DAU FAIL VAU ADC 3 DAU FAIL VAU ADC I/F 0 DAU FAIL VAU ADC I/F 1 DAU FAIL VAU ADC I/F 2 DAU FAIL VAU ADC I/F 3 DAU FAIL VAU CH 0 GAIN DAU FAIL VAU CH 1 GAIN DAU FAIL VAU CH 2 GAIN
Loss of all vibrationrelated processing. Usage monitoring still available. Inability to record any data to DTD or upload data from the DTD. All other functions still available.
VAU circuit card assembly Vibration monitoring and hardware failure RTB cannot be performed. Usage monitoring still available.
VAU circuit card analog input circuitry failure
Partial loss of vibration data acquisition depending upon failure.
VAU DEGR (Cont)
Effectivity: All
TDM 2128 UNCLASSIFIED HUMS STATUS MESSAGE BIT LOG ENTRY FAILURE CONDITION SYSTEM EFFECT
DAU FAIL VAU CH 3 GAIN DAU FAIL VAU TACH 0 DAU FAIL VAU TACH 1 DAU FAIL VAU TACH 2 DAU FAIL VAU TACH 3 DAU FAIL VAU CH 0 FLTR DAU FAIL VAU CH 1 FLTR DAU FAIL VAU CH 2 FLTR DAU FAIL VAU CH 3 FLTR TACH AZ3 FAIL ACCEL Axx FAIL BIAS (xx = Accel No. 1-9, 14, 15) ACCEL Axx FAIL SATURATION (xx = Accel No. 1-9, 14, 15) RTB DEGR TACH AZ1 FAIL TACH AZ2 FAIL TRACKER FAIL DAU FAIL AATPS LAMP SW DAU FAIL AATPS 24V ON DAU FAIL AATPS 24V OFF DAU FAIL AATPS 12V ON DAU FAIL AATPS 12V OFF ACCEL Axx FAIL BIAS (accel no. 10-13, 17, 20) ACCEL Axx FAIL SATURATION (accel no. 10-13, 17, 20)
VAU circuit card analog input circuitry failure
Partial loss of vibration data acquisition depending upon failure.
TVM DEGR
Degraded transmission vibration monitoring. Degraded transmission vibration monitoring. Loss of ability to record some vibration data, Signal received from accelerometer is not within depending upon which accelerometer has expected signal range. failed. Tail Rotor Tachometer Degraded rotor vibration failure. monitoring and rotor tuning. Main Rotor Tachometer failure. Rotor Blade Tracker Rotor tuning cannot be failure performed using RBT. AATPS RBT lamp switch failure. AATPS RBT power supply control failure.
Transmission tachometer failure Accelerometer output amplifier failure.
AATPS RBT lamp power failure.
Accelerometer output amplifier failure.
Degraded RTB vibration monitoring. Loss of ability to record some vibration data, Signal received from accelerometer is not within depending upon which accelerometer has expected signal range. failed. Loss of ability to perform RTB.
Effectivity: All
TDM 2128 UNCLASSIFIED HUMS STATUS MESSAGE CDU FAIL BIT LOG ENTRY FAILURE CONDITION SYSTEM EFFECT
LFS FAIL
CDU/DTU FAIL CDU RESPONSE CDU/DTU FAIL CDU BIT LOAD FACTOR SENSOR FAIL RTC BATTERY VOLTAGE LOW None
CDU not responding to DAU commands Internal CDU failure Load factor sensor output invalid. DAU battery voltage low.
DAU BATT
INIT SYS
At least one cumulative logbook entry invalid.
Loss of CDU/DTU control and display functions. No control over HUMS functions. Structural usage monitoring will be degraded. Possible loss of HUMS time and date if battery goes completely dead. Cumulative logbook values invalidated.
Effectivity: All
Effectivity: All
Chapter 1.6 Advisory messages Table of contents

1 Advisory messages Page 1 Page Advisory messages 1
List of tables
1
Advisory messages
Advisory messages displayed on the CDU/DTU provide the operator with an indication of the following: HUMS acknowledgement of an operator initiated command. Conditions which must be brought to the attention of the operator. Status of commanded operation.
Advisory messages may be removed from the display by pressing the CLR key. Table 1 contains a listing of the HUMS advisory messages along with a brief description of the message. Table 1. Advisory messages Description Displayed after SBIT if the aircraft ID received from the ARINC 429 bus does not match the aircraft ID stored in the DAU. Message will automatically clear if the correct ID is received. Displayed after SBIT is complete if a valid aircraft ID is not available from the ARINC 429 bus. Message will automatically clear if a valid ID is received. This message is displayed if a data acquisition completes without any errors. Indicates that a manually commanded vibration/RTB data acquisition is in progress or an Engine Power Assurance test is in progress. Displayed after operator-initiated clear BIT log action to indicate that BIT log has been cleared. Indicates that the CDU/DTU has lost communication with the DAU for over one minute. Keys are locked until communication is restored. Indicates a configuration DTD has been installed when trying to do an initialization upload.
Message A/C ID MISMATCH
A/C ID UNAVAILABLE
ACQUISITION COMPLETE
ACQUISITION IN PROGRESS
BIT LOG CLEARED
COMM FAIL
CONFIG DTD
Effectivity: All
TDM 2128 UNCLASSIFIED Table 1. Advisory messages Description Displayed after SBIT is complete if a configuration DTD is installed in CDU/DTU. Also displayed anytime a DTD is removed and a configuration DTD installed. Displayed upon completion of engine power assurance test if stability test of calculated engine margins fails. Displayed after SBIT is complete if a DTD is not installed in CDU/DTU. Also displayed anytime a DTD is removed from CDU/DTU. This is an indication to the operator that the data file on the DTD with the name "FILE ID" is more than 80% full. XX is the actual percentage full. Displayed when the operator initiates IBIT. Remains displayed for approximately 20-30 seconds. Displayed after SBIT is complete if an invalid (not correctly formatted) DTD is installed in CDU/DTU. Also displayed anytime a DTD is removed and an invalid (incorrectly formatted) DTD installed. Displayed during an initialization upload if the DTD contains an invalid initialization file. This message is displayed if the aircraft is not in a proper regime for collecting engine power assurance data. Displayed if the aircraft is in a valid regime and the selected engine is not properly configured for an engine power assurance test for the current regime. Displayed when a configuration upload is attempted and DTD does not contain a valid configuration file. This message is displayed when the operator attempts either an initialization or configuration upload with no DTD installed. Displayed when an initialization upload is attempted and DTD does not contain a valid initialization file. Displayed during an initialization upload if the DTD contains an old initialization file. Displayed initially upon power application to HUMS to indicate that startup BIT is being performed.
Message CONFIGURATION DTD INSTALLED
DATA UNSTABLE
DTD NOT INSTALLED
"FILE ID" FILE XX% FULL
IBIT IN PROGRESS
INVALID DTD INSTALLED
INVALID INIT FILE
INVALID REGIME
INVALID SETUP
NO CONFIG FILE
NO DTD
NO INIT FILE
OLD INIT FILE
SBIT IN PROGRESS
Effectivity: All
TDM 2128 UNCLASSIFIED Table 1. Advisory messages Description Displayed upon completion of a successful initialization or configuration data upload. Displayed if the initialization file or configuration file was not successfully uploaded from the DTD to the DAU. Displayed when a valid initialization or configuration file is being uploaded from the DTD.
Message UPLOAD COMPLETE
UPLOAD FAIL
UPLOAD IN PROGRESS
Effectivity: All
Effectivity: All
Chapter 1.7 Display pages Table of contents

1 2 Menu tree Detailed displays Page 1 1 Page Display tree 2 Page FileID definition 2
List of figures
1
List of tables
1
1 2
Menu tree
Figure 1 shows the menu structure in a tree format.
Detailed displays
The detailed displays are organized by function as follows: Flashing is indicated by an underline in the display pages that follow. ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Start-Up Top-Level Menu A/C Maint Config RBT DTD Status View Logbook BIT Setup Event Mark Pop-Up Displays
Startup
The initial screen on power up is: S B I T I N P R O G R E S S Once SBIT has confirmed communication between the DAU and the DTU, a check is done of the DTD. This check can result in one of the following displays: D T D N I N S T A L Or C O N F I G U R D T D I N S T Or I N V A L I D D T D I N S T A L L E D O T L E D A T I O N A L L E D
Effectivity: All
Startup Process
A/C Maintenance
Config RBT
View Logbook (Note 1)
BIT (Note 1)
Setup (Note 1)
RT&B
DTD Status
Last Op
Run IBIT
Upload
Summary Idle
Clear Log
Initialization
View Log FPOG Hover Cruise Config P/N VNE
Config
Clock
EPA
Engine 1 Engine 2
DPD
Aircraft Engine Drive System Note 1: This menu is not available in an operation.
Figure 1. Display tree
Effectivity: All
TDM 2128 UNCLASSIFIED These displays will change to reflect the new status if the DTD is removed and/or installed. These displays can also be cleared by starting an operation or pressing the CLR key. However, the system will not write data to either a configuration DTD or an invalid DTD. If a valid DTD is installed, the system will check the allocated space remaining in each file and display the following message for each file more than 80% full: f i l e i d F I L E X X % F U L L ?
where fileid is the identification of the file. The user can view all files more than 80% full by depressing the PAGE key. The full list of fileids is the same as in the DTD status menu. This list is cleared by pressing the CLR key or starting an operation. If a valid Aircraft ID is not available from the ARINC 429 bus, the system will then display: I D A / C U N A V A I L A B L E While this message is displayed, the system will continue to monitor the ARINC 429 bus for a valid A/C ID. This display will clear automatically if a valid A/C ID is received. It can also be cleared by pressing the CLR key or starting an operation. However, either of these actions will invalidate logbook data. If the A/C ID received over the ARINC 429 bus does not match the A/C ID stored in NVM, the following message will be displayed: A / C I D M I S M A T C H While this message is displayed, the system will continue to monitor the ARINC 429 bus for a new A/C ID. If a new A/C ID is received which matches the A/C ID stored in NVM, this display will clear automatically. It can also be cleared by pressing the CLR key or starting an operation. However, either of these actions will invalidate logbook data. If all the processing defined above has completed but the VAU has not completed its CSBIT, the initial screen will be displayed until the VAU CSBIT is complete or times out.
Top-level menu
The Top-Level menu contains two pages as shown below: > M A I N T T R K R > L O G B K B I T D T D S T S ? ?? X X M S G X X X S E T U P ? ?? X X M S G X X X
The first page of the Top-Level menu is the default display. It is automatically displayed under the following conditions: Completion of SBIT after power-up, Completion of user-commanded IBIT, Start of an operation, End of an operation, and After an Event Mark acquisition. The XXMSGXXX field displays the top-level status of the system based on filtered BIT status, A/C ID validity, operation number validity, cumulative logbook validity, and failure of either the
Effectivity: All
TDM 2128 UNCLASSIFIED EDPU or VAU configurations. This field is not a selectable option (i.e. the cursor cannot be positioned on that field). The highest priority message will be displayed. Refer to Chapter 1.6 for a list of possible messages displayed in this field and the condition that sets each message. The message will be centered in the 8-character field with the extra space to the left of the message for messages with an odd number of characters. The second page of the Top-Level menu is not available during an operation. During an operation, the Top-Level menu will appears as: > M A I N T T R K R D T D S T S ? ? X X M S G X X X
A/C maintenance menu

Selecting MAINT from the Top-Level menu will display the A/C Maintenance menu as shown below: > R T & B E P A D P D ? ?
5.1
RT&B
Selecting RT&B from the A/C Maintenance menu will display the RT&B menu below: > I D L E F P O G > H O V E R S C R Z ?? ?
> C R U I S E ? V N E ?? Note that the number of acquisitions and the displayed name of each acquisition are defined in the EDPU configuration and may differ from what is displayed above. The limitations on the configuration are no more than eight acquisitions and a maximum length of six characters for the name. 5.1.1 Running an acquisition Acquisitions are run by selecting the desired regime from the RT&B menu. When an acquisition is selected, the display will change to: A C Q U I S I T I O N I N P R O G R E S S Pressing the CLR key while this display is present will abort the acquisition and return to the RT&B menu with the cursor on the aborted acquisition. RT&B acquisitions can result in display of a list of one or more of the following error messages: M A I N T A C H R O T O R F A I L ? ?
M A I N R O T O R T A C H U N D E R S P D
Effectivity: All
M A I N R O T O R T A C H O V E R S P D T A I L T A C H R O T O R F A I L
? ? ? ? ?
T A I L R O T O R T A C H U N D E R S P D T A I L R O T O R T A C H O V E R S P D R B T F A I L
These error messages are displayed at the end of the acquisition. Pressing the Down Arrow key will scroll through the list of errors. Pressing the CLR key returns to the RT&B menu with the cursor on the initiated regime. If the acquisition completes without any tachometer or tracker failures, the CDU will display: A C Q U I S I T I O N C O M P L E T E Pressing the CLR key will return to the RT&B menu with the cursor on the initiated regime. The word DATA will be displayed on the right side of the display on the same line as the regime if any data was collected. For example, if an FPG100 acquisition is run successfully, the return display will look like: I D L E > F P O G 5.1.2 Viewing data If an acquisition has been successfully completed, there will be a DATA indication on the right side of the display on the same line as the regime as shown below: I D L E > F P O G ?? ??
D A T A
D A T A
Selecting the DATA indication for a particular regime will display the last 1/Rev values for the RT&B accelerometers configured for that regime as shown below: M R L A T 1 R 1 2 . 3 4 I P S V E R T 1 R 1 2 . 3 4 I P S L A T 1 T 1 2 . 3 4 I P S ?? ?? ??
M R
T R
Effectivity: All
TDM 2128 UNCLASSIFIED T R V E R T 1 T 1 2 . 3 4 I P S
??
Note that the number of CIs and the name for each is defined in the configuration for each acquisition and may be different than shown above. The limitations on the configuration are no more than four CIs per acquisition and a maximum of 16 characters in the name. Missing or invalid data will be indicated by asterisks (*) in the data field. The user must press the CLR key to return to the RT&B menu. The cursor on the return display will be on the regime from which the data was viewed.
5.2
EPA
EPA display pages are not yet defined.
5.3
DPD
DPD allows the user to view the dynamic values of certain acquired and computed parameters. The displayed values are updated at an approximate rate of 1 Hz. Selecting DPD from the A/C Maintenance menu will display the DPD menu shown below: > A / C E N G I N E D R V S Y S
5.3.1
Aircraft parameters Selecting A/C from the DPD menu will display the following: A / C I D 1 2 3 4 5 ?
D A T E ( D D / M M / Y Y ) 3 1 / 1 2 / 9 9 ? T I M E ( H H : M M : S S ) 2 3 : 5 9 : 5 9 ? F L T / G N D S T A T U S F L T T A S 1 2 0 V N E 1 2 0 V E R T S P D - 1 9 9 A L T - 9 0 0 A L T - 9 0 0 K T S ? ? ? ? K T S ? ?
F P M
B A R O
F T
D E N S
F T
Effectivity: All
TDM 2128 UNCLASSIFIED R A D A L T 4 9 9 9
F T
? ? ? ? ? ? ? ?? ? ? ??
H E A D I N G - 1 7 9 O A T - 5 5 R O L L
D E G
D E G
A N G L E - 1 7 9 D E G R A T E - 1 7 D E G / S
R O L L
P I T C H A N G L E - 1 7 9 D E G P I T C H R A T E - 1 7 D E G / S
Y A W
R A T E - 1 7
D E G / S
L O A D F A C T O R - 1 2 . 3 G
Missing or invalid data will be indicated by asterisks (*) in the data field. Pressing the CLR key while displaying any parameter will return to the DPD menu with the cursor on A/C. 5.3.2 Engine parameters Selecting Engine from the DPD menu will display the following: E N G 1 N G 1 1 2 N F 1 4 7 I T T - 6 9 T Q 1 6 6 N G 1 1 2 N F 1 4 7 I T T - 6 9 ? ? ? ? ? ? ?
E N G 1
E N G 1
D E G
E N G 1
E N G 2
E N G 2
E N G 2
D E G
Effectivity: All
E N G 2
T Q 1 6 6
??
Missing or invalid data will be indicated by asterisks (*) in the data field. Pressing the CLR key while displaying any parameter will return to the DPD menu with the cursor on ENGINE. 5.3.3 Drive system parameters Selecting DRV SYS from the DPD menu will display the following: M G B O I L P R E S S 1 1 B A R 2 ? ? ? ? ? ? ? ? ? ??
M G B
O I L T E M P 1 4 9 D E G O I L T E M P 1 4 9 D E G O I L T E M P 1 4 9 D E G S P E E D 1 4 0 % T Q N m T Q N m
I G B
T G B
R O T O R
M A I N R T R 9 6 2 2 8 T A I L R T R 3 7 2 0
T R
P D L
P O S 8 5 D E G P O S m m P O S m m
Y A W
A C T 1 - 8 . 4 A C T 2 - 8 . 4
Y A W
Missing or invalid data will be indicated by asterisks (*) in the data field. Pressing the CLR key while displaying any parameter will return to the DPD menu with the cursor on DRV SYS.
Configure RBT
Selecting TRKR from the Top-Level menu displays the current status of the RBT as shown below: > T R A C K E R ? ? O F F
Effectivity: All
6.1
Modification of RBT status

Selecting TRACKER from the RBT Status display will cause the RBT status to flash as shown: > T R A C K E R ? ? O F F
Pressing the Down Arrow key will cycle through the allowed states of the RBT, i.e. OFF, DAY, and NIGHT. When the desired status is displayed, the ENT key is pressed to accept the change and return to the RBT Status display with the new status shown.
DTD status
Selecting DTD STS from the Top-Level menu displays the current status of the DPD. If a properly formatted DTD is installed, this option will display the space available on the DTD for each file as shown below f F I L E E N D i l e i d X X % F U L L O F L I S T ? ?? ? ? ??
The complete list of fileids displayed is listed in Table 1. Pressing the CLR key will return to the Top-level menu with the cursor on DTD STS. Table 1. FILEID definition File ID File Name SUM DATA sum.hsd TUM DATA tum.hsd EXCEEDANCE exceed.hsd LOGBOOK usage.hsd FLIGHT DATA flight.hsd DISC EVNT discev.hsd EPA DATA engpa.hsd MAINT EVNT mainev.hsd IDENT ident.hsd AUTO ENG CI engaci.hsd AUTO ENG VIB engavib.hsd MAN ENG CI engmci.hsd MAN ENG VIB engmvib.hsd AUTO AIRFRM CI frmaci.hsd AUTO AIRFRM VIB frmavib.hsd MAN AIRFRM CI frmmci.hsd MAN AIRFRM VIB frmmvib.hsd AUTO RTB CI rtbaci.hsd AUTO RTB VIB rtbavib.hsd MAN RTB CI rtbmci.hsd MAN RTB VIB rtbmvib.hsd AUTO XMSN CI trnaci.hsd AUTO XMSN VIB trnavib.hsd MAN XMSN CI trnmci.hsd MAN XMSN VIB trnmvib.hsd VIB ABORT vibabort.hsd
Effectivity: All
TDM 2128 UNCLASSIFIED File ID VIB LOG File Name viblog.hsd
If there is no DTD installed, the display will appear as: N O T D T D I N S T A L L E D If a DTD is installed and contains a config.hsd file, the CDU will display: C O N F I G U R A T I O N D T D I N S T A L L E D A configuration DTD is only used to update the DAU with a new configuration. The DAU will not write to a configuration DTD. If the installed DTD is not correctly formatted, i.e. does not contain the required files, the CDU will display: D T D I N V A L I D I N S T A L L E D On each of these displays, the user must press the CLR key to return to the Top-Level menu.
View logbook
Selecting VIEW LOGBK from the Top-Level menu will display the View Logbook menu as shown below: > L A S T O P T O T A L ?
8.1
Last operation
Selecting LAST OP from the View Logbook menu will display the logbook data from the last completed operation as shown below: O P N U M B E R 1 2 3 4 5 T I M E 1 . 2 ? ? ??
O P
H R S
R O T O R
S T A R T S 1 2
R O T O R 1 N R
T U R N T I M E . 2 H R S ? ? ?
F A I L T I M E 1 . 2 H R S I G H T T I M E 1 . 2 H R S
F L
Effectivity: All
F L T
F A I L 1 . 2
T I M E H R S
? ?? ??
L A N D I N G S 1 2 O E I T I M E 1 . 2
H R S
Missing or invalid data will be indicated by asterisks (*) in the data field. Pressing the CLR key return to the View Logbook menu with the cursor on LAST OP.
8.2
Cumulative totals
Selecting TOTAL from the View Logbook menu will display the cumulative logbook data as shown below: O P N U M B E R 1 2 3 4 5 ?? ?? ??
O P T I M E 1 2 3 4 5 . 6
H R S
R O T O R S T A R T S 1 2 3 4 5
R O T O R T U R N T I M E 1 2 3 4 5 . 6 H R S ?? N R F A I L T I M E 1 2 3 4 5 . 6 H R S F L I G H T T I M E 1 2 3 4 5 . 6 H R S F L T F A I L 1 2 3 4 5 . 6 L A N D I N G S 1 2 3 4 5 O E I T I M E 1 2 3 4 5 . 6 T I M E H R S ?? ?? ?? ?? ??
H R S
Missing or invalid data will be indicated by asterisks (*) in the data field. Pressing the CLR key will return to the View Logbook menu with the cursor on TOTAL.
Effectivity: All
BIT
Selecting BIT from the Top-Level Menu will display the following BIT menu: > I B I T V W L O G C L R ? L O G
Pressing the CLR key will return to the Top-Level menu with the cursor on BIT.
9.1
Initiate IBIT
Selecting IBIT from the BIT menu will initiate IBIT. This test runs the same tests run at powerup plus some additional interactive CDU tests. The CDU will display the following for approximately 20 - 30 seconds: I B I T P R O G R E S S
I N
The CDU will then display a checkerboard pattern in each character of the top row for five seconds followed by the reverse checkerboard pattern in each character for another five seconds. Next, the CDU will display a checkerboard pattern in each character of the bottom row for five seconds followed by the reverse checkerboard pattern in each character for another five seconds. The CDU will then display the following: P U S H A N Y C L R E N D S S W I T C H T E S T
The user can then press keys in any order to verify key operation, except the CLR key. The CDU will display the following, depending on the key pressed. E V E N T K E Y C L R E N D S T E S T P A G E K E Y C L R E N D S
T E S T
E N T E R K E Y C L R E N D S T E S T R I G H T K E Y C L R E N D S T E S T D O W N K E Y C L R E N D S
T E S T
Pressing the CLR key ends the test and the system returns to the Top-Level menu.
9.2
Viewing BIT results

Selecting VW LOG will display the current filtered BIT status. Typical displays are shown below: D A U F A I L E D P U O F P C H K S U M ??
Effectivity: All
A C C E L B I A S E N D O F
A 1 5
F A I L ?? ? ? ??
R E S U L T S
The END OF RESULTS display marks the end of the list. Pressing the PAGE key with END OF RESULTS displayed will cause the first message in the list to be re-displayed. Pressing the CLR key will display the BIT menu with the cursor on VW LOG. For a list of the possible messages displayed in this field and the condition that sets each message refer to Chapter 1.6.
9.3
Clearing BIT results

Selecting CLR LOG will clear the current BIT log and display the following on the CDU: L O G B I T C L E A R E D Pressing the CLR key will return to the BIT menu with the cursor on CLR LOG.
10
Setup
Selecting SETUP from the Top-Level menu will display the Setup menu as shown below:
> U P L O A D C O N F P N?
C L O C K
Pressing the CLR key on the Setup menu will return to the Top-Level menu with the cursor on SETUP.
10.1
Upload
Selecting UPLOAD from the Setup menu will display the Upload menu as shown below: > I N I T C O N F I G ?
Pressing the CLR key will return to the Setup menu with the cursor on UPLOAD 10.1.1 Initialization upload Selecting INIT from the Upload menu will cause the system to attempt to upload an initialization file from the DTD. If a valid initialization file is present, the CDU will display: U P L O A D P R O G R E S S
I N
Pressing the CLR key will abort the upload and return to the Upload menu with the cursor on INIT. Upon completion of the upload, the CDU will display: U P L O A D C O M P L E T E or
Effectivity: All
U P L O A D F A I L depending on whether the upload is successful or not. Pressing the CLR key will return to the Upload menu with the cursor on INIT. The following error displays are possible when INIT is selected from the Upload menu: N O D T D C O N F I G D T D N O F I L E
I N I T
I N V A L I D I N I T F I L E O L D I N I T F I L E Pressing the CLR key will return to the Upload menu with the cursor on INIT. 10.1.2 Configuration upload Selecting CONFIG from the Upload menu will cause the system to attempt to upload an configuration file from the DTD. If a valid configuration file is present, the CDU will display: U P L O A D P R O G R E S S
I N
Pressing the CLR key will abort the upload and return to the Upload menu with the cursor on CONFIG. Upon completion of the upload, the CDU will display: U P L O A D C O M P L E T E or U P L O A D F A I L depending on whether the upload is successful or not. Pressing the CLR key will return to the Upload menu with the cursor on CONFIG. The following error displays are possible when CONFIG is selected from the Upload menu: N O D T D N O C O N F I G F I L E
Effectivity: All
TDM 2128 UNCLASSIFIED Pressing the CLR key will return to the Upload menu with the cursor on CONFIG.
10.2
Date/Time
Selecting CLOCK from the Setup menu will display the current date and time settings as shown: > D A T E T I M E 3 0 / 1 2 / 0 2 1 6 : 4 5 : 5 1
Pressing the CLR key will return to the Setup menu with the cursor on CLOCK. If both time and date are available to the DAU over the ARINC 429 bus, the date and time values cannot be changed by the user. This will be indicated by the lack of a cursor in the first character position on the Date/Time display as shown below: D A T E T I M E 10.2.1 Modification of date setting Selecting DATE from the Date/Time display will cause the tens digit in the day field to flash as shown below: > D A T E T I M E 3 0 / 1 2 / 0 2 1 6 : 4 5 : 5 1 3 0 / 1 2 / 0 2 1 6 : 4 5 : 5 1
Pressing the Down Arrow key will cycle the digit through its allowable values. Depressing the Right Arrow will cause the units digit in the day field to flash. Again, pressing the Down Arrow will cycle the digit through its allowable values. This process is repeated until all required characters have been changed. Pressing the Right Arrow from the units digit in the year field will cause the tens digit of the day field to flash. When the date has been set to the desired value, the ENT key is depressed to accept the changes. This will cause the CDU to return to the Date/Time display with the new value of date displayed and the cursor on DATE. If an invalid date is entered (i.e. 31/11/01), the date displayed will be the closest valid date prior to the entered date. 10.2.2 Modification of time setting Selecting TIME from the Date/Time display will cause the tens digit in the hour field to flash as shown below: D A T E > T I M E 3 0 / 1 2 / 0 2 1 6 : 4 5 : 5 1
Pressing the Down Arrow key will cycle the digit through its allowable values. Depressing the Right Arrow will cause the units digit in the hour field to flash. Again, pressing the Down Arrow will cycle the digit through its allowable values. This process is repeated until all required characters have been changed. The seconds field is not modifiable. Pressing the Right Arrow from the units digit in the minutes field will cause the tens digit of the hour field to flash. When the time has been set to the desired value, the ENT key is depressed to accept the changes. This will cause the CDU to return to the Date/Time display with the new value of time displayed and the cursor on TIME.
10.3
Configuration P/N
Selecting CONF PN from the Setup menu will display the current configuration P/N as shown: C O N F I G P / N X X X X X X X X X X X X X X
Effectivity: All
Pressing the CLR key will return to the Setup menu with the cursor on CONF PN. The actual format of the configuration P/N has not been determined yet.
11
Event mark
Pressing the EVNT key from any display will pre-empt any current manual or automatic acquisition and run a general vibration scan. When the EVNT key is depressed, the CDU will display: A C Q U I S I T I O N I N P R O G R E S S Pressing the CLR key while this display is present will abort the acquisition and return to the first page of the Top-Level menu with the cursor on MAINT. An event mark acquisition can result in display of a list of one or more of the following error messages: M A I N T A C H R O T O R F A I L ? ? ? ? ? ? ? ? ?
M A I N R O T O R T A C H U N D E R S P D M A I N R O T O R T A C H O V E R S P D T A I L T A C H R O T O R F A I L
T A I L R O T O R T A C H U N D E R S P D T A I L R O T O R T A C H O V E R S P D X M S N T A C H F A I L X M S N U N D E R S P D X M S N O V E R S P D
T A C H
T A C H
These error messages are displayed at the end of the acquisition. Pressing the Down Arrow key will scroll through the list of error messages. Pressing the CLR key returns to the TopLevel menu with the cursor on MAINT. If the acquisition completes without any tachometer failures, the CDU will display: A C Q U I S I T I O N C O M P L E T E
Effectivity: All
TDM 2128 UNCLASSIFIED Pressing the CLR key will return to the Top-Level menu with the cursor on MAINT.
12
Pop up displays
These are displays that will pop-up without any action by the user. These messages are typically informational messages to alert the crew of a condition that will require some action to correct.
12.1
CDU/DAU communication failure

If the CDU does not receive a command from the DAU for 1 minute, the CDU will display the following: C O M M F A I L This display can only be cleared by re-establishment of communication between the CDU and the DAU. While COMM FAIL is displayed, all keys are disabled. Upon the re-establishment of communication between the CDU and the DAU, the CDU will display whatever display is required by the current state of the system. This will generally be the display prior to the popup. However, if the system was running a manually-commanded acquisition or an operation was started or stopped while the pop-up was active, the display could be different.
12.2
File 80% full indication

If a file reaches 80% of its allocated capacity, the CDU will display: f F I L E i l e i d X X % F U L L
where fileid is the name of the file exceeding the limit. The full list of fileids is the same as in the DTD Status menu. Pressing the CLR key will return the CDU to the display required by the current state of the system. This will generally be the display prior to the pop-up. However, if the system was running a manually-commanded acquisition or an operation was started or stopped while the pop-up was active, the display could be different. Also, if a manuallycommanded acquisition was running at the time that a file exceeded 80% full, the display of the 80% full indication will be delayed until all displays associated with the manual acquisition are complete.
Effectivity: All
Effectivity: All
Chapter 1.8 Operating procedures Table of contents

1 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 Data entry methods and guidelines Operating procedures OBS initialization OBS configuration uploading Setting system date/time Viewing configuration part number BIT initiation and viewing BIT results Clearing BIT log Direct parameter display viewing Checking DTD status DTD insertion DTD removal Log book data viewing Configuring rotor blade tracker Performing a manual acquisition Page 1 2 2 2 2 3 3 4 4 4 5 5 5 5 6
Data entry methods and guidelines

Data entry is allowed for certain fields on the HUMS display pages. Some data is entered on a character-by-character basis while other types of data are entered by entering a complete field.
1.1
Character data entry.

1 2 3 Using the two arrow keys (DOWN, RIGHT), the cursor (> or <) is moved adjacent to the desired field for data entry. Pressing the ENT key causes the first character of the field to begin flashing. With the character flashing, the DOWN arrow key is now used for data entry and the RIGHT arrow key is used to move right through each enterable character in the data field. The DOWN arrow key is used to cycle forward through each allowable value for the character, starting with the current value. After cycling to the desired value, pressing the RIGHT arrow key causes the character to cease flashing and causes the next character position to begin flashing. Pressing the ENT key after all characters have been set to the desired values causes the system to accept the data values entered. Not all character positions have to be updated during data entry in order for the system to accept the values. If only one character needs to be updated move to that position using the RIGHT arrow key, cycle through the allowable values using the DOWN arrow key and then press the ENT key to complete the entry.
1.2
Field data entry

1 2 3 Using the two arrow keys (DOWN, RIGHT), the cursor (> or <) is moved adjacent to the desired field for data entry. Pressing the ENT key causes the entire field to begin flashing. With the field flashing, the DOWN arrow key is now used for data entry. The RIGHT arrow key has no affect. The DOWN arrow key is used to cycle forward through each allowable value (DAY, NIGHT, OFF, etc.). After the desired selection has been made, pressing the ENT key causes the system to accept the value.
Effectivity: All
Operating procedures
The following HUMS operating procedures are used for normal ground maintenance operations. Refer to data entry methods and guidelines to support these procedures.
2.1
OBS initialization
OBS initialization instructions allow the operator to upload a HUMS initialization file from a DTD. Uploading initialization data to the HUMS should only have to be performed when a DAU has been replaced or if the initialization data set up on the ground station has changed. Initialization requires that a properly initialized DTD prepared on the ground station for that aircraft serial number be inserted into the CDU/DTU at power up. 1 2 3 4 5 6 Ensure operational DTD is in the CDU/DTU. On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Using the arrow keys, place the cursor next to SETUP and press the ENT key. Setup menu page is displayed. Using the arrow keys, place the cursor next to UPLOAD and press the ENT key. Upload menu page is displayed. Using the arrow keys, place the cursor next to INIT and press the ENT key. UPLOAD IN PROGRESS message is displayed while file is being uploaded. When completed, UPLOAD COMPLETE message will be displayed. Press CLR key to return to UPLOAD menu page.
2.2
OBS configuration uploading

Configuration uploading instructions allow the operator to transfer HUMS configuration data from the DTD to the DAU. Uploading configuration data to the HUMS requires that a configuration DTD be inserted into the CDU/DTU at power up. 1 2 3 4 5 6 Ensure configuration DTD is in the CDU/DTU. On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Using the arrow keys, place the cursor next to SETUP and press the ENT key. Setup menu page is displayed. Using the arrow keys, place the cursor next to UPLOAD and press the ENT key. Upload menu page is displayed. Using the arrow keys, place the cursor next to CONFIG and press the ENT key. UPLOAD IN PROGRESS message is displayed while file is being uploaded. When completed, UPLOAD COMPLETE message will be displayed. Press CLR key to return to UPLOAD menu page. Remove configuration DTD from CDU/DTU.
7 8
2.3
Setting system date/time

The following instructions allow the operator to view and change system date and system time. 1 2 3 On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Using the arrow keys, place the cursor next to SETUP and press the ENT key. Setup menu page is displayed.
Effectivity: All
TDM 2128 UNCLASSIFIED 4 Using the arrow keys, place the cursor next to CLOCK to and press the ENT key. Date and Time page is displayed with current values. Note If cursor is not displayed next to DATE, system is receiving valid date and time values from ARINC 429 data bus and values cannot be changed. 5 Using the arrow keys, place the cursor next to desired value to change and press the ENT key. The first digit of the selected field begins flashing. Note When changing system time, the seconds field cannot be changed. 6 With the character flashing, the down arrow key is used to sequentially increment the flashing digit through all allowable values. Continue to press the down arrow key until desired digit is displayed. 7 Press the RIGHT ARROW key. Second digit is flashing. 8 Repeat steps 6 and 7 for remaining digits. Selected data field is as desired. 9 Once the desired data is entered, press the ENT key to make the entry. 10 Press the CLR key to return to the SETUP menu.
2.4
Viewing configuration part number

The following instructions allow the operator to view the current HUMS configuration part number. 1 2 3 4 5 On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Using the arrow keys, place the cursor next to SETUP and press the ENT key. Setup menu page is displayed. Using the arrow keys, place the cursor next to CONF PN to and press the ENT key. Configuration page is displayed with current value. Press the CLR key to return to the SETUP menu.
2.5
BIT initiation and viewing of BIT results

BIT initiation and viewing of BIT results instructions allow the operator to initiate system IBIT and CDU/DTU IBIT and review BIT results. Operator initiated BIT is only available prior to engine start. If engine(s) are started, only viewing of BIT results is allowed. 1 2 3 4 On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Press the down arrow key to place the cursor next to BIT and press the ENT key. BIT menu is displayed. With cursor next to IBIT, press the ENT key. IBIT IN PROGRESS is displayed for approximately 20-30 seconds. Each character position on the top line of the display is displayed as a checkerboard pattern for 5 seconds followed by a reverse checkerboard pattern for 5 seconds. Each character position on the bottom line of the display is displayed as a checkerboard pattern for 5 seconds followed by a reverse checkerboard pattern for 5 seconds. PUSH ANY SWITCH is displayed on top line of CDU. Press each key on CDU/DTU keyboard except CLR key. Name of key pressed is displayed on top line of CDU display. Press the CLR key. HUMS top level menu is displayed and SYS VAL is displayed on bottom right side of CDU/DTU display.
5 6
Effectivity: All
TDM 2128 UNCLASSIFIED 7 8 9 Press the PAGE key. Main menu page 2 is displayed. Press the down arrow key to place the cursor next to VW LOG and press the ENT key. First page of BIT log is displayed. Press PAGE key to cycle through messages or press CLR key to return to BIT menu page.
2.6
Clearing BIT log

The following procedure allows the HUMS BIT log to be cleared. It should be cleared anytime a DAU has been replaced or as directed in HUMS troubleshooting. 1 2 3 4 On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Press the down arrow key to place the cursor next to BIT and press the ENT key. BIT menu is displayed. Using the arrow keys, place the cursor next to CLR LOG and press the ENT key. BIT LOG CLEARED message will be displayed after log file data has been cleared from DAU memory. Press the CLR key to return to BIT menu.
2.7
Direct parameter display viewing

Direct parameter display viewing instructions allow the operator to view parameters associated with the aircraft, engine, and drive train system. 1 2 3 4 5 6 7 On the CDU/DTU, access the Top Level Menu. Using the arrow keys, place the cursor next to MAINT and press the ENT key. Aircraft maintenance menu is displayed. Using the arrow keys, place the cursor next to DPD and press the ENT key. DPD menu page is displayed. Using the arrow keys, place the cursor next to desired category of parameters and press the ENT key. First parameter page of desired category is displayed. Press the PAGE key to view the next page. Next parameter page is displayed. Repeatedly press the PAGE key to continue viewing additional parameters. Press the CLR key to return to DPD menu page for selection of different category of parameters to view.
2.8
Checking DTD status

The DTD status instructions allow the operator to view the available space left for each of the required operational files on the DTD. A properly formatted DTD must be inserted in CDU/DTU. 1 2 3 4 5 On the CDU/DTU, access the Top Level Menu. Using the arrow keys, place the cursor next to DTD STS and press the ENT key. First DTD file status page is displayed. Press the PAGE key to view the next page. Next DTD file status page is displayed. Repeatedly press the PAGE key to continue viewing status of remaining DTD files. Press the CLR key to return to HUMS top level menu page.
Effectivity: All
2.9
DTD insertion
Note An operational DTD must be inserted into the CDU/DTU prior to the start of a HUMS operation to avoid the loss of HUMS data. 1 2 3 4 Slide door latch to the left. Door springs open. With label side facing up, insert the memory card into the slot. Seat memory card by pushing it towards the rear of the case until all motion stops. Ejector button is in the extended position. Close door until it latches.
2.10
DTD removal
Note Removal of an operational DTD during a HUMS operation may result in the loss of HUMS data. 1 2 3 4 Slide door latch to the left. Door springs open. Press ejector button. Card ejects. Remove card. Close door until it latches.
2.11
Log book data viewing

Log book data viewing instructions allow the operator to view either the last operations log book data or the cumulative log book totals for all operations. 1 2 3 4 On the CDU/DTU, access the Top Level Menu. Press the PAGE key. Main menu page 2 is displayed. Using the arrow keys, select VIEW LOGBK and press the ENT key. Log book menu is displayed. Using the down arrow key, select the desired type of log book values to be displayed and press ENT key. First log book value will be displayed.
Note If any of the log book values are missing or invalid, the CDU/DTU will display asterisks (*) in the data field for that value. 5 6 7 Press the PAGE key to view the next page. Next log book page is displayed. Repeatedly press the PAGE key to continue viewing additional log book values. Press the CLR key to return to log book menu page.
2.12
Configuring rotor blade tracker

To set the configuration of the temporary fit rotor blade tracker perform the following: 1 2 3 4 On the CDU/DTU, access the Top Level Menu. Using the down arrow key select TRKR and press the ENT key. Tracker current status is displayed. To change tracker status, press ENT key. Current status will begin flashing. Repeatedly press down arrow key to cycle through available values.
Effectivity: All
TDM 2128 UNCLASSIFIED 5 6 Press ENT key to accept value selected. Press CLR key to return to HUMS top level menu page.
2.13
Performing a manual acquisition

Maintenance personnel can perform a manual data acquisition on the ground as part of maintenance when checking HUMS sensors. To initiate a manual acquisition perform the following: Note HUMS must be in a normal operation to perform the following procedure. 1 2 Press CDU/DTU EVNT key. ACQUISITION IN PROGRESS will be displayed until all data has been collected. Once ACQUISITION COMPLETE is displayed, press CLR key to return to top level menu.
Effectivity: All
Chapter 1.9 Operational checkout preliminary set up
Table of contents
References Preliminary requirements Procedure 1 Operational checkout introduction 1.1 General 1.2 Preliminary set up Requirements after job completion
Page 1 1 1 1 2 2 2 Page
List of tables
1 2 3 4 References Required persons Support equipment Required actions References Table 1. References Title HUMS system checkout HUMS sensor checkout HUMS troubleshooting introduction HUMS symptom index Preliminary requirements Required Conditions: None Required Persons Table 2. Required persons Function Perform preliminary set up
1 1 1 2
Chapter 1.10 1.11 1.12 1.13
Person 1
Support Equipment Table 3. Support equipment Identification no. SDP3BI-384-101
Nomenclature Data Transfer Device
Qty 1
Supplies: None Safety Conditions: Observe all aircraft ground safety procedures. Refer to aircraft maintenance publications.
Effectivity: All
Procedure
1
1.1
Operational checkout preliminary procedures

General
The operational checkout chapters contain procedures used to verify proper operation of the HUMS. Only the procedures contained in Chap 1.10 are required for routine operational checkout. Routine checkout does not require the engines running. If it is suspected that a specific HUMS accelerometer or tachometer has malfunctioned, then the checkout procedures contained in Chapter 1.11 also need to be performed. These checks require the engines to be running. When an indicated result is not obtained, refer to Chap 1.12 and Chap 1.13 HUMS symptom index for the proper troubleshooting procedure. Proper operation of HUMS is dependant upon the MAU. Ensure the MAU is in proper working order before performing the HUMS operational checkout.
1.2
Preliminary setup
1 2 3 Connect external power to the aircraft in accordance with applicable aircraft maintenance publication procedure. Close all required circuit breakers on the applicable Power Distribution Panel(s) if not already closed. Ensure the HUMS circuit breaker(s) are closed. Note Ensure DTD is installed before applying power to HUMS. DTD used in the following step is only for test purposes and does not have to be configured for any specific operation or aircraft. Any DTD will work so long as it is functional, has been properly initialized on the ground station, and is not a configuration DTD. 4 5 6 7 Insert initialized DTD into CDU/DTU. Apply power to the aircraft. Apply power to the MAU. Apply power to HUMS.
Requirements after job completion
Required actions
Title HUMS system checkout HUMS sensor checkout
Table 4. Required actions Chapter 1.10 1.11
Effectivity: All
Chapter 1.10 HUMS system checkout
Table of contents
References Preliminary requirements Procedure Requirements after job completion
Page 1 1 2 2
List of tables
1 2 3 References Required conditions Required persons
Page 1 1 1
References Table 1. References Title Operational checkout preliminary set up HUMS sensor checkout
Chapter 1.9 1.11
Preliminary requirements Required Conditions Table 2. Required conditions Title Chapter Operational Checkout Preliminary Set Up 1.9
Required Persons Table 3. Required persons Function Perform HUMS checkout procedure
Person 1
Support Equipment: None Supplies: None Safety conditions Observe all ground safety procedures when performing test.
Effectivity: All
Procedure 1. Observe CDU/DTU display area. RESULT1: Immediately after power application SBIT IN PROGRESS is displayed for approximately 10 seconds. RESULT2: Display intensity and appearance is normal. RESULT3: HUMS top level menu is displayed. 2. Observe CDU/DTU bottom right message area. RESULT: SYS VAL is displayed. 3. Observe CDU/DTU pushbuttons. RESULT: Pushbutton nomenclatures are lit. 4. Press the PAGE key. RESULT: Main menu page 2 is displayed. 5. Press the down arrow key to place the cursor next to BIT and press the ENT key. RESULT: BIT menu is displayed. 6. With cursor next to IBIT, press the ENT key. RESULT1: IBIT IN PROGRESS is displayed for approximately 20-30 seconds. RESULT2: Each character position on the top line of the display is displayed as a checkerboard pattern for 5 seconds followed by a reverse checkerboard pattern for 5 seconds. RESULT3: Each character position on the bottom line of the display is displayed as a checkerboard pattern for 5 seconds followed by a reverse checkerboard pattern for 5 seconds. RESULT4: PUSH ANY SWITCH is displayed on top line of CDU. 7. Press each key on CDU/DTU keyboard except CLR key. RESULT: Name of key pressed is displayed on top line of CDU display. 8. Press CLR key. RESULT: HUMS top level menu is displayed and SYS VAL is displayed on bottom right side of CDU/DTU display.
Requirements after job completion Required actions 1. 2. If sensors are to be checked, perform procedures of Chapter 1.11. If checkout is complete remove power from MAU, HUMS, and aircraft in accordance with maintenance publication procedures.
Effectivity: All
Chapter 1.11 HUMS Sensor checkout
Table of contents
References Preliminary requirements Procedure Requirements after job completion
Page 1 1 2 2
List of tables
1 2 3 References Required conditions Required persons
Page 1 1 1
References Table 1. References Title HUMS System Checkout
Chapter 1.10
Preliminary requirements Required Conditions Table 2. Required conditions Title Chapter Operational Checkout Preliminary Set Up 1.9 HUMS System Checkout 1.10 Required Persons Table 3. Required persons Function Perform HUMS sensor checkout procedure
Person 2
Support Equipment: None Supplies: None Safety conditions Observe all aircraft ground safety procedures when performing test.
Effectivity: All
Procedure 1 2 3 Start engines and bring to FPOG condition. On the CDU/DTU, access the Top Level Menu if not already displayed. Press the EVNT key. RESULT: ACQUISITION IN PROGRESS is displayed for up to one minute then ACQUISITION COMPLETE is displayed. 4 Press CLR key to return to HUMS top level menu. RESULT: HUMS top level menu is displayed and SYS VAL is displayed on bottom right side of CDU/DTU display. If SYS VAL is not displayed, note the BIT failure message and refer to the HUMS symptom index, Chap 1.13 for troubleshooting. 5 6 7 Using the arrow keys, select MAINT and press the ENT key. Maintenance menu will be displayed. With cursor next to RT&B press ENT key. RTB acquisition type menu will be displayed. Using the down arrow key, select FPOG then press ENTER key. RESULT: ACQUISITION IN PROGRESS is displayed for up to three minutes then ACQUISITION COMPLETE is displayed. 8 Press CLR key twice to return to RTB menu then press CLR key again to return to HUMS top level menu. RESULT: HUMS top level menu is displayed and SYS VAL is displayed on bottom right side of CDU/DTU display. If SYS VAL is not displayed, note the BIT failure message and refer to the HUMS symptom index, Chap 1.13 for troubleshooting.
Requirements after job completion
Required actions 1 Shutdown engines and remove power from MAU, HUMS, and aircraft in accordance with aircraft maintenance procedures.
Effectivity: All
Chapter 1.12 HUMS troubleshooting introduction Table of contents

References 1 Troubleshooting introduction Page 1 1 Page References References Table 1. References Title HUMS system checkout HUMS sensor checkout HUMS symptom index HUMS fault isolation procedures 1
List of tables
1
Chapter 1.10 1.11 1.13 1.14
Troubleshooting introduction
Troubleshooting procedures should be used in conjunction with the operational checkout procedures of Chap 1.10 and Chap 1.11. Symptoms which may occur during operational checkout or during flight are listed in the HUMS fault symptom index, Chap 1.13. For each entry in the symptom index, there is listed either an associated remedy or a reference to an isolation procedure in Chap 1.14. When a malfunction may be caused by either a faulty LRU or faulty aircraft wiring, a multimeter should be used to test and isolate faulty aircraft wiring. Note Do not swap DAUs between aircraft to troubleshoot system failures. Swapping DAUs will require reinitialization of HUMS. The data contained in the DAU memory is platform specific. The recorded data will be different for each platform and could invalidate the data. The highest priority filtered BIT failure message (if any) which occurred during flight is displayed on the CDU/DTU main menu page. BIT results are shown on the BIT LOG page(s) for use by maintenance personnel. This information can be used in troubleshooting symptoms which cannot be recreated during operational checkout. Refer to Chap 1.5 for description of the BIT LOG page(s). Maintenance personnel should review the BIT log information contained on these pages and discuss the symptoms with the flight crew to determine the corrective action to be performed. The HUMS BIT LOG should be cleared after a maintenance corrective action has been accomplished. After clearing BIT LOG entries, HUMS operational checkout procedures should be run again to ensure failures have been corrected. Note BIT results are cleared immediately following a CLEAR BIT LOG command and will not be displayed again until PBIT is performed or until power is cycled (cold power-up) on the system.
Effectivity: All
Effectivity: All
Chapter 1.13 HUMS fault symptom index Table of contents

1 HUMS fault symptom index Page 1 Page References HUMS symptom index References Table 1. References Title Operating procedures HUMS troubleshooting introduction HUMS fault isolation procedures 1 1
List of tables
1 2
Chapter 1.8 1.12 1.13
HUMS fault symptom index

Table 2. HUMS symptom index SYMPTOM REMEDY OR ISOLATION PROCEDURE Refer to Chapter 1.14, item 1.
HUMS SYSTEM CHECKOUT SYMPTOMS: SBIT IN PROGRESS message not displayed when HUMS power applied.
Display intensity too dim or too bright or display Refer to Chapter 1.14, item 2. corrupted (missing pixels) or garbled (wrong characters). HUMS top level menu page not displayed after HUMS SBIT complete. Refer to Chapter 1.14, item 3.
SYS VAL not displayed on top level menu page Refer to Chapter 1.14, item 4. after HUMS SBIT complete. Some or all pushbutton nomenclatures not lit. Main menu page 2 not displayed when PAGE key pressed. BIT menu not displayed when down arrow key pressed. IBIT IN PROGRESS not displayed when IBIT initiated. One or more characters fail display checkerboard pattern test. Refer to Chapter 1.14, item 5. Replace CDU/DTU.
Effectivity: All
SYMPTOM One or more keys fail key press test. Top menu not displayed after pressing CLR key. SYS VAL not displayed after completion of IBIT.
REMEDY OR ISOLATION PROCEDURE Replace CDU/DTU.
View BIT LOG and refer to BIT failure message symptoms for failure message displayed.
HUMS SENSOR CHECKOUT SYMPTOMS: ACQUISITION COMPLETE not displayed after initiating manual or RTB acquisition.
Press CLR key twice to return to HUMS top level menu. View BIT LOG and refer to BIT failure message symptoms for failure message displayed. View BIT LOG and refer to BIT failure message symptoms for failure message displayed.
SYS VAL not displayed after completion of manual or RTB acquisition.
BIT FAILURE MESSAGE SYMPTOMS: DAU FAIL EDPU OFP CHKSUM DAU FAIL EDPU FLTNG PT DAU FAIL MAIN W/D TIMER DAU FAIL MAIN TIMER DAU FAIL IOP RESPONSE DAU FAIL IOP W/D TIMER DAU FAIL IOP TIMER DAU FAIL ERM FORMAT DAU FAIL 429 REGISTER DAU FAIL ERM BAD SCTR DAU FAIL 429 CONTROLLER DAU FAIL 429 WRAP DAU FAIL REAL TIME CLK DAU FAIL RTC RAM CHKSUM DAU FAIL ERM PTRN INTEG DAU FAIL RS422 CH 3 DAU FAIL RS422 CH 2 Replace DAU.
Replace DAU battery. If failure still exists replace DAU. Replace DAU.
Effectivity: All
SYMPTOM DAU FAIL AATPS RESPONSE DAU FAIL AATPS CAL MUX DAU FAIL AATPS A/D CAL CONFIG FAIL EDPU CONFIG FAIL VAU CDU/DTU FAIL DTU RESPONSE DTD FAIL WRAP DTD FAIL FORMAT DTD NOT PRESENT DAU FAIL VAU FAILED DAU FAIL VAU RESPONSE DAU FAIL VAU LP PROC DAU FAIL VAU LP CHKSUM DAU FAIL VAU LP RAM DAU FAIL VAU LP DP RAM DAU FAIL VAU OFP CHKSUM DAU FAIL VAU RAM DAU FAIL VAU PRESENCE DAU FAIL VAU ADC 0 DAU FAIL VAU ADC 1 DAU FAIL VAU ADC 2 DAU FAIL VAU ADC 3 DAU FAIL VAU ADC I/F 0 DAU FAIL VAU ADC I/F 1 DAU FAIL VAU ADC I/F 2 DAU FAIL VAU ADC I/F 3 DAU FAIL VAU CH 0 GAIN
REMEDY OR ISOLATION PROCEDURE Replace DAU.
Reload configuration data. If failure continues replace DAU.
Refer to Chapter 1.14, item 6. Replace DTD. If failure continues replace CDU/DTU. Missing or damaged initialization files on DTD. Replace DTD with properly initialized DTD. Normal indication when DTD not installed. If message occurs when DTD is installed replace CDU/DTU. Replace DAU.
Effectivity: All
SYMPTOM DAU FAIL VAU CH 1 GAIN DAU FAIL VAU CH 2 GAIN DAU FAIL VAU CH 3 GAIN DAU FAIL VAU TACH 0 DAU FAIL VAU TACH 1 DAU FAIL VAU TACH 2 DAU FAIL VAU TACH 3 DAU FAIL VAU CH 0 FLTR DAU FAIL VAU CH 1 FLTR DAU FAIL VAU CH 2 FLTR DAU FAIL VAU CH 3 FLTR TACH AZ3 FAIL ACCEL Axx FAIL BIAS (see note a) ACCEL Axx FAIL SATURATION (see note a) TACH AZ1 FAIL TACH AZ2 FAIL TRACKER FAIL DAU FAIL AATPS LAMP SW DAU FAIL AATPS 24V ON DAU FAIL AATPS 24V OFF DAU FAIL AATPS 12V ON DAU FAIL AATPS 12V OFF CDU/DTU FAIL CDU RESPONSE CDU/DTU FAIL CDU BIT LOAD FACTOR SENSOR FAIL RTC BATTERY VOLTAGE LOW
REMEDY OR ISOLATION PROCEDURE Replace DAU.
Refer to Chapter 1.14, item 7. Refer to Chapter 1.14, item 8. Incorrect accelerometer measurement configuration data. Reload configuration data. Refer to Chapter 1.14, item 9. Refer to Chapter 1.14, item 10. Refer to Chapter 1.14, item 11. Replace DAU.
Refer to Chapter 1.14, item 6. Replace CDU/DTU Refer to Chapter 1.14, item 12. Replace DAU battery.
Note a. XX corresponds to accelerometer number that has failed.
Effectivity: All
Chapter 1.14 HUMS fault isolation procedures Table of contents

References Preliminary requirements Procedure 1 Troubleshooting Procedures Requirements after job completion Page 1 1 1 5
List of tables
1 2 3 4 References Required persons Support equipment Required actions References Table 1. References Title Operating procedures Symptom index Removal and installation procedures
Page 1 1 1 5
Chapter 1.8 1.13 1.15
Preliminary requirements Required Conditions: None Required Persons Table 2. Required persons Function Perform troubleshooting procedure
Person 1
Support Equipment Nomenclature Multimeter Table 3. Support equipment Identification no. Qty 1
Safety conditions Observe all standard safety procedures when troubleshooting.
Effectivity: All
TDM 2128 UNCLASSIFIED Procedure
Troubleshooting procedures
REMEDY Replace DAU then proceed to step 2. Proceed to step 3. Troubleshoot aircraft +28 Vdc power wiring to DAU and RS-422 wiring between DAU and CDU/DTU. End of test. Proceed to step 4. Proceed to step 7. Proceed to step 5. End of test. Replace CDU/DTU then proceed to step 6. Close HUMS circuit breaker(s) then proceed to step 6. Troubleshoot aircraft +28 Vdc power wiring to CDU/DTU. End of test. Replace CDU/DTU. If problem still exists, replace DAU. Replace DAU.
ISOLATION PROCEDURE Item 1. SBIT IN PROGRESS not displayed at HUMS power up Step 1. Wait one minute. Is COMM FAIL message YES displayed? NO Step 2. Does problem still exist? YES
Step 3. Is display completely blank?
NO YES
NO Step 4. Look closely at display. In bright light, display YES may only appear to be blank if lighting is set to NVIS level. Is display actually blank? NO Step 5. Check HUMS circuit breaker(s). Are HUMS YES circuit breaker(s) closed? NO Step 6. Does problem still exist? YES
Step 7. Is display garbled?
NO YES
NO End of test
ISOLATION PROCEDURE REMEDY Item 2. Display intensity incorrect or display corrupted or garbled Proceed to step 2. Step 1. Is display intensity correct? YES NO YES NO Step 3. Adjust pedestal lighting power. Did display intensity change? YES Proceed to step 3. Replace CDU/DTU. Replace DAU. If problem still exists replace CDU/DTU. Adjust pedestal lighting to desired level. End of test. Proceed to step 4. Replace DAU then proceed to step 5. Troubleshoot pedestal lighting power system.
Step 2. Is HUMS top level menu page displayed but corrupted or garbled?
NO Step 4. Adjust pedestal lighting power while observing YES CDU/DTU pushbutton switches. Did pushbutton nomenclatures vary in brightness? NO
Effectivity: All
TDM 2128 UNCLASSIFIED Step 5. Does problem still exist? YES Troubleshoot aircraft +5 Vdc pedestal lighting power wiring to DAU. End of test.
NO End of test ISOLATION PROCEDURE Item 3. Top level menu not displayed after HUMS SBIT complete. Step 1. Is DTD NOT INSTALLED message YES displayed? NO Step 2. Remove and reinsert DTD. Did message YES clear? NO Step 3. Is HUMS top level menu now displayed? YES NO YES
REMEDY Proceed to step 2. Proceed to step 4. Proceed to step 3. Replace CDU/DTU. End of test. Proceed to step 4. Replace DTD with properly initialized DTD. Proceed to step 5. Press CLR key for each fileid message displayed then continue with checkout procedure. Proceed to step 6. Proceed to step 7. Proceed to step 9. Replace DAU then proceed to step 8. Troubleshoot MAU. Troubleshoot aircraft wiring from MAU to DAU. End of test. Proceed to step 10. Replace DAU. Proceed to step 11. Enter correct aircraft information into MAU system. Note If DAU has been swapped from another aircraft instead of supply, accumulated log book data contained in the DAU will be invalidated if operator continues. If continuing, DAU will also be reinitialized. 1. Press CLR key to acknowledge A/C ID MISMATCH message. This will cause the DAU to overwrite the aircraft ID stored in memory with the aircraft ID received from the MAU.
Step 4. Is CONFIGURATION DTD INSTALLED message or INVALID DTD INSTALLED message displayed? Step 5. Is there a fileid FILE xx% FULL message displayed?
NO YES
Step 6. Is A/C ID UNAVAILABLE message displayed? Step 7. Check MAU system and verify MAU is working properly. Is MAU working properly? Step 8. Does problem still exist?
NO YES NO YES NO YES
Step 9. Is A/C ID MISMATCH message displayed?
NO YES
NO YES Step 10. Check MAU system and verify correct aircraft ID has been entered or is displayed. Is aircraft NO ID correct? Step 11. Is HUMS operational checkout procedure YES being performed to confirm that a previous failure has been remedied by replacement of DAU?
Effectivity: All
TDM 2128 UNCLASSIFIED This is normal for a new DAU being installed. 2. Perform initialization upload into new DAU. NO YES NO End of test ISOLATION PROCEDURE Item 4. SYS VAL not displayed after SBIT. Step 1. Has a HUMS LRU/LRI been previously replaced? REMEDY YES Proceed to step 2. Proceed to step 4. Proceed to step 3. Clear HUMS BIT LOG then repeat checkout procedure. Proceed to step 4. Perform initialization upload procedure then repeat checkout procedure. Replace DAU then proceed to step 12. Check aircraft wiring from MAU to DAU. End of test.
Step 12. Does problem still exist?
NO Step 2. Was the BIT LOG cleared after replacement? YES NO Step 3. Has HUMS been reinitialized? YES NO Step 4. View BIT LOG and record all entries. Note any entries associated with HUMS sensors then proceed with step 5. (Once BIT LOG is cleared and IBIT is performed, any sensor related messages will not reappear unless sensor checkout procedure is performed and a sensor fails again.) Step 5. Clear HUMS BIT LOG then continue with checkout procedure. End of test ISOLATION PROCEDURE Item 5. Some or all pushbutton nomenclatures not lit. Step 1. Are any pushbuttons lit? YES NO YES NO End of test ISOLATION PROCEDURE Item 6. CDU/DTU FAIL DTU RESPONSE message Step 1. Replace CDU/DTU. Does problem still exist?
REMEDY Replace CDU/DTU. Proceed to step 2. Replace CDU/DTU. Troubleshoot aircraft +5 Vdc pedestal lighting power wiring to CDU/DTU.
Step 2. Check pedestal lighting power input to CDU/DTU. Is voltage present?
REMEDY YES NO YES Replace DAU then proceed to step 2. End of test. Troubleshoot aircraft wiring between DAU and CDU/DTU. End of test.
Step 2. Does problem still exist.
NO End of test
Effectivity: All
ISOLATION PROCEDURE Item 7. TACH AZ3 FAIL Step 1. Replace transmission tachometer AZ3. Does problem still exist?
REMEDY YES Check wiring between tachometer AZ3 and DAU then proceed to step 2. Proceed to step 2. Replace DAU. End of test.
NO YES NO
End of test ISOLATION PROCEDURE Item 8. ACCEL Axx FAIL BIAS Step 1. Replace associated accelerometer. Does problem still exist? REMEDY YES Check wiring between failing accelerometer and DAU then proceed to step 2. Proceed to step 2. Replace DAU. End of test.
NO YES NO
End of test ISOLATION PROCEDURE Item 9. TACH AZ1 FAIL Step 1. Replace main rotor tachometer AZ1. Does problem still exist? REMEDY YES Check wiring between tachometer AZ1 and DAU then proceed to step 2. Proceed to step 2. Replace DAU. End of test.
NO YES NO
End of test ISOLATION PROCEDURE Item 10. TACH AZ2 FAIL Step 1. Replace tail rotor tachometer AZ2. Does problem still exist? REMEDY YES Check wiring between tachometer AZ2 and DAU then proceed to step 2. Proceed to step 2. Replace DAU. End of test.
NO YES NO
End of test ISOLATION PROCEDURE Item 11. TRACKER FAIL Step 1. Was Rotor Blade Tracker installed when failure occurred? Step 2. Go to HUMS top level menu screen then press down arrow key to select TRKR. Press ENTER key. Is TRACKER OFF displayed? REMEDY YES NO YES Replace RBT then proceed to step 3. Proceed to step 2. Check wiring between Rotor Blade Tracker and DAU then proceed to step 4. Press ENTER key. Press down arrow
NO
Effectivity: All
TDM 2128 UNCLASSIFIED key until OFF is selected then press ENTER key. Clear BIT LOG then repeat sensor checkout procedure. Check wiring between Rotor Blade Tracker and DAU then proceed to step 4. End of test. Replace DAU. End of test.
YES
NO YES NO
End of test
ISOLATION PROCEDURE Item 12. LOAD FACTOR SENSOR FAIL Step 1. Check power to load factor sensor. Is power present?
REMEDY YES NO Proceed to step 2. Troubleshoot power source to load factor sensor. Check wiring between load factor sensor and DAU then proceed to step 3. End of test. Replace DAU. End of test.
Step 2. Replace load factor sensor . Does problem still exist?
YES
NO YES NO
End of test
Requirements after job completion Required actions Table 4. Required actions Chapter 1.15
Title Removal and installation procedures
Effectivity: All
Chapter 1.15 Removal and installation Table of contents

References Preliminary requirements Procedure 1 Removal and Installation 1.1 Data acquisition unit 1.1.1 Removal 1.1.2 Installation 1.2 DAU battery 1.2.1 Removal 1.2.2 Installation 1.3 Cockpit display unit/data transfer unit 1.3.1 Removal 1.3.2 Installation Requirements after job completion Page 1 1 2 2 2 2 2 2 2 3 3 3 3 3 Page References Required persons Spares Required actions References Table 1. References Chapter 1.8 1.10 Title Operating Procedures HUMS System Checkout 1 1 2 3
List of tables
1 2 3 4
Preliminary requirements Required Conditions: None Required Persons Table 2. Required persons Function Perform removal/installation procedure
Person 1
Support Equipment: None Supplies: None
Effectivity: All
TDM 2128 UNCLASSIFIED Spares Table 3. Spares Identification no. 176990-01-01 174356-07 180305-001
Nomenclature Data Acquisition Unit Lithium Battery Cockpit Display Unit/Data Transfer Unit
Qty 1 1 1
Safety Conditions: None
Procedure
1
1.1
1.1.1
Removal and installation

Data acquisition unit
Removal 1 2 3 4 5 6 Ensure all electrical power is off. Gain access to Data Acquisition Unit. Disconnect aircraft electrical connectors from DAU connectors J1, J2, and J3. Loosen two thumb nuts and remove two hold-down collars positioned over two holddown hooks on front of the unit. Grasp handle and pull the DAU forward to clear wedges at rear of mounting base. Support the DAU and lift out of mounting base.
1.1.2
Installation 1 2 3 4 5 6 Place the DAU on mounting base and slide back to align wedges on mounting base with wedges on rear of the DAU. Lift the two hold-down collars on mounting base over the two hold-down hooks on front of the unit and tighten the two thumb nuts. Connect aircraft electrical connectors to DAU connectors J1, J2, and J3. Close/reinstall all access panels/equipment removed or opened. Initialize DAU in accordance with Chap 1.8. Enter date and time in accordance with Chap 1.8.
1.2
1.2.1
DAU battery
Removal 1 2 3 4 Gain access to DAU. Locate the battery receptacle on the rear panel of the DAU. Using a Phillips screwdriver, loosen the two captive screws that attach the Battery Access Cover to the rear of the DAU and remove Battery Access Cover. Using a slotted screwdriver, rotate the battery holder cover 90 degrees counterclockwise to release the cover.
Effectivity: All
TDM 2128 UNCLASSIFIED WARNING DAU battery contains lithium. Explosion and severe burn hazard. Do not recharge, disassemble, heat above 160 f (71 c), incinerate, short circuit, puncture, or expose contents to water. Follow proper safety precautions when handling and dispose of in accordance with proper procedures. 5 Remove battery from battery holder and dispose of the expended battery using proper disposal procedures.
1.2.2
Installation 1 2 3 4 5 6 7 8 Insert a new lithium battery into the battery holder with the (-) end entering first. Place the metal face of the battery holder cover against the (+) end of the lithium battery. Align the tabs on the battery holder cover with the slots in the battery holder. Push the cover/battery into the holder and rotate the battery holder cover clockwise to the end of rotation. Place the Battery Access Cover over the battery holder. Engage the two mounting screws for the Battery Access Cover using a Phillips screwdriver. Re-fit any equipment or panels previously removed. Enter date and time as described in Chap 1.8.
1.3
1.3.1
Cockpit display Unit/Data transfer unit

Removal 1 2 3 4 Ensure all electrical power is off. Loosen the four fasteners on the face of the CDU/DTU. Pull the CDU/DTU out from mounting location sufficient to access electrical connector and disconnect. Remove the CDU/DTU.
1.3.2
Installation 1 2 Position the CDU/DTU in front of mounting location and connect electrical connector. Install the CDU/DTU into its mounting location and secure the four fasteners.
Requirements after job completion Required actions Table 4. Required actions Chapter 1.8 1.10
Title Operating Procedures HUMS System Checkout
Effectivity: All
Effectivity: All
Chapter 1.16 Servicing
Table of contents
1 1.1 1.2 1.3 Servicing Cleaning Inspection Scheduled maintenance
Page 1 1 1 1 Page
List of tables
1 References References Table 1. References Title Cleaning
Chapter 1.17
Servicing
This section lists the procedures and data necessary for servicing of the Health and Usage Monitoring System line replaceable units (LRU).
1.1
Cleaning
The following HUMS equipment have situational cleaning requirements: ?? Cockpit Display Unit/Data Transfer Unit (CDU/DTU) display There are no periodic or scheduled HUMS equipment cleaning requirements. HUMS cleaning procedure should be accomplished as necessary based on situational requirements. Refer to chapter 1.17 for the HUMS CDU/DTU cleaning procedures.
1.2 1.3
Inspection
There are no inspection requirements for the HUMS on-board system LRUs.
Scheduled maintenance
There are no scheduled maintenance requirements for the HUMS on-board system LRUs.
Effectivity: All
Effectivity: All
Chapter 1.17 Cleaning
Table of contents
References Preliminary requirements Procedure 1 Cleaning Requirements after job completion
Page 1 1 1 2 3 Page
List of tables
1 2 3 4 References Required persons Supplies Required actions
1 1 1 3
References Table 1. References Title HUMS System Checkout
Chapter 1.10
Preliminary requirements Required Conditions: None Required Persons Table 2. Required persons Function Perform cleaning procedure
Person 1
Support Equipment: None Supplies Table 3. Supplies Identification no. MIL-D-16791 TT-I-735 MS-260 (FSC 18598)
Nomenclature Detergent, GP Liquid Cloth, Lint-free Alcohol, Isopropyl Glass cleaner
Qty As required As needed As required As required
Effectivity: All
TDM 2128 UNCLASSIFIED Safety Conditions:
WARNING Detergent may be irritating to the skin. Eye and skin contact is hazardous and could result in injury. Use proper eye and skin protection. WARNING Isopropyl alcohol is flammable and toxic. Keep away from heat, sparks, and open flame. Avoid prolonged or repeated breathing of vapor. Use only in a well-ventilated area. WARNING Glass cleaner is flammable and toxic. Keep away from heat, sparks, and open flame. Avoid prolonged or repeated breathing of vapor. Use only in a well-ventilated area. Eye or skin contact is hazardous and could result in injury. Use proper eye and hand protection.
Procedure
Cleaning
CAUTION Display filter is coated with a reflection reducing coating. Use care when cleaning to avoid damage to coating.
1.
Remove dust and loose dirt using a soft, lint-free cloth. CAUTION Display filter is coated with a reflection reducing coating. Take care not to get detergent on filter.
2.
Clean all slightly dirty surfaces using soft lint-free cloth moistened with detergent and water. Remove detergent residue using a soft cloth moistened with clean water. Allow surfaces to air dry. CAUTION Display filter is coated with a reflection reducing coating. Take care not to get alcohol on filter.
3.
Remove stubborn dirt or grease from all surfaces except front panel display filter using a lint-free cloth or soft bristle brush moistened with isopropyl alcohol. Allow surfaces to air dry. Clean front panel display filter using soft lint-free cloth moistened with glass cleaner. Remove excess cleaner using soft lint-free cloth. Allow surface to air dry.
4.
Effectivity: All
Requirements after job completion Required actions
Title HUMS Operational Checkout
Table 4. Required actions Chapter 1.10
Effectivity: All
Effectivity: All
CHAPTER 2 AIRCREW FLIGHT INFORMATION
Table of contents
1 2 2.1 2.2 2.3 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 General Checklist information Preflight procedures Inflight procedures Postflight procedures Operating procedures Data entry methods and guidelines Procedures Configuring rotor blade tracker Setting system date/time DTD insertion DTD removal Direct parameter display viewing Checking DTD status Performing rotor track and balance acquistion Performing engine power assurance
Page 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 3
General
The information contained in this chapter is intended as a guide to the sequence of operating procedures which should be followed by the aircrew when using HUMS. Using HUMS in a manner outside the guidelines below may result in errors or improper operation or invalid data acquisition and recording.
2
2.1
2.1.1
Checklist information
Preflight procedures
With Power Off Before power is applied to HUMS, a DTD should be inserted into the CDU/DTU. The DTD should have already been properly initialized and configured on the ground station for the particular HUMS operation to be performed. If the HUMS operation will be a rotor tuning flight, then the aircrew should ensure that a rotor blade tracker has been fitted to the aircraft.
2.1.2
Before Rotors Turning Once power has been applied to HUMS and the MAU and HUMS has completed power up BIT, the status should be checked on the CDU/DTU. HUMS status should indicate no failure indications and there should be no advisory messages displayed. If the correct time and date have not been received from the MAU, the aircrew should enter a time and date into HUMS.
Effectivity: All
39-A-31-30-01-00A-131A-A Chapter 2 2002-07-08 Page 1 of 4
TDM 2128 UNCLASSIFIED If the HUMS operation will be a rotor tuning flight then the Rotor Blade Tracker should be configured for either day or night operation as applicable. If an FPOG rotor tuning operation is to be performed then follow procedures for performing a rotor track and balance operation.
2.2
Inflight procedures
The following functions are available while in a HUMS operation during flight: ?? ?? ?? ?? Viewing aircraft parameters Checking the status of the DTD Performing a rotor track and balance acquisition Performing an engine power assurance check
2.3
Postflight procedures
After aircraft power has been removed, remove the DTD from the CDU/DTU and return it to the ground station for analysis. Chapter 2.2
3
3.1 3.2
Operating procedures
Data entry methods and guidelines
Refer to Chapter 1.8 for data entry methods and guidelines.
Procedures
The following procedures may be performed by the aircrew. All other HUMS operating procedures are performed by maintenance personnel.
3.2.1
Configuring rotor blade tracker Refer to Chapter 1.8 for the procedure to set the configuration of the temporary fit rotor blade tracker.
3.2.2
Setting system date/time Refer to Chapter 1.8 for the procedure to view and change system date and system time. Note: Once a HUMS operation has started, system date and time cannot be viewed or entered.
3.2.3
DTD insertion Refer to Chapter 1.8 for DTD insertion procedure.
3.2.4
DTD removal Refer to Chapter 1.8 for DTD removal procedure.
3.2.5
Direct parameter display viewing Refer to Chapter 1.8 for procedure to view parameters associated with the aircraft, engine, and drive train system.
3.2.6
Checking DTD status Refer to Chapter 1.8 for procedure to view the available space left for each of the required operational files on the DTD.
3.2.7
Performing rotor track and balance acquisition The HUMS rotor track and balance procedure is used in conjunction with the Rotor Blade Tracker to initiate any one of up to eight different rotor vibration acquisitions and display the results to the operator. Note: If a Rotor Blade Tracker is not installed, a rotor balance acquisition can still be performed.
Effectivity: All
TDM 2128 UNCLASSIFIED 1 2 On the CDU/DTU, access the Top Level Menu. Using the arrow keys, select MAINT and press the ENT key. Maintenance menu is displayed. 3 With cursor next to RT&B press ENT key. RTB acquisition menu will be displayed. 4 Using a combination of the PAGE key and down arrow key, select the acquisition to be performed. Up to eight different acquisitions can be displayed. 5 Once cursor is next to desired selection, press ENT key to initiate the acquisition. ACQUISITION IN PROGRESS will be displayed until all data has been collected. 6 Once ACQUISITION COMPLETE is displayed, press CLR key to return to RTB menu. Cursor will be at the selected acquisition and DATA will be displayed on the right side of the display. 7 Press the right arrow key to select DATA then press ENT key to view the first page of results for the measurement. Up to 4 pages are available for display. Note If any of the values are missing or invalid, the CDU/DTU will display asterisks (*) in the data field for that value. 8 Press the PAGE key to view the next page. Next results page is displayed. 9 Repeatedly press the PAGE key to continue viewing additional RTB results. 10 Press the CLR key to return to RTB menu page.
3.2.8
Performing engine power assurance measurement Engine power assurance function has not been implemented yet.
Effectivity: All
This page intentionally left blank.
Effectivity: All
CHAPTER 3 ILLUSTRATED PARTS CATALOGUE
Table of contents
1 1.1 1.2 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.3.5 1.3.6 1.3.7 1.3.8 2 Introduction Identification Parts which are listed Maintenance parts list Figure and index no. column Part number column Vendor part numbers Similar assemblies Nomenclature column Indentation Usage code column Units per assembly column Maintenance parts list
Page 1 1 1 1 1 2 2 2 2 2 2 2 3 Page
List of figures
1 Health and usage monitoring system
1
1.1
Introduction
Identification
This Illustrated Parts Catalogue lists and illustrates only the assemblies and installation parts of the Health and Usage Monitoring System equipment.
1.2
Parts which are listed

In general, the assemblies and parts installed at the time the end item was manufactured are listed and identified in this manual. When an assembly or part (including vendor items) which is different from the original was installed during the manufacture of later items, series, or blocks, all assemblies and parts are listed (and Usable On coded). However, when the original assembly or part does not have continued application (no spares of the original were procured or such spares are no longer authorized for replacement), only the preferred assembly or part is listed. Also, when an assembly or part was installed during modification, and the original does not have continued application, only the preferred item is listed.
1.3
1.3.1
Maintenance parts list

Figure and index no. column Each part is indexnumbered consecutively in the order of disassembly and corresponding with the index number on the associated figure. Note, However, that attaching parts are listed after the parts they attach. Index numbers are assigned to all parts having maintenance or supply significance.
Effectivity: All
TDM 2128 UNCLASSIFIED 1.3.2 Part number column This column contains the applicable contractor, vendor, and standard (Government, industry, contractor) part numbers for the parts listed. Other items that do not have part numbers are identified in this column by the words NO NUMBER. Items made from raw stock (conduit, wire, tape, etc) or which have lost their identities by being permanently attached to other pieces are not included. 1.3.3 Vendor part numbers Vendor part numbers are the original design activity drawing numbers and are confirmed as such by the presence of a vendor Commercial and Government Entity (CAGE) number. 1.3.4 Similar assemblies When similar assemblies exist that contain many identical parts, the assemblies are combined. 1.3.5 Nomenclature column The drawing title is listed in this column along with parenthetical notations which give additional information required to identify the part. 1.3.6 Indentation To indicate item relationship, the following indention system has been employed in the parts list: 1234567 NOMENCLATURE
End item of each figure .Detail parts of the end item .Attaching parts for detail parts and assemblies of the end item ..Detail parts of the assemblies ..Subassemblies ..Attaching parts for detail parts of the assemblies and the subassemblies ...Detail parts of the subassemblies ...Subsubassemblies ...Attaching parts for detail parts of the subassemblies and the subsubassemblies 1.3.7 Usage code column This column contains a code to indicate the applicability to aircraft type. 1.3.8 Units per assy column This column shows the quantity required for each detail part in an assembly. In the case of assemblies, the quantity shown is the quantity required for one next higher assembly. For attaching parts, the quantity shown is the quantity of each attaching part required to attach one unit or one assembly. When the quantity is indefinite, the abbreviation A/R appears in the column. The abbreviation RF is used to indicate the part is repeated from another location or listed for the purpose of clarity.
Effectivity: All
Maintenance parts list
J1 J2
3
E V N TP A G E E N T C L R
Figure 1. Health and usage monitoring system
Effectivity: All
FIG AND INDEX 01 -000 -001 -002 -003 -004
NOMENCLATURE PART NUMBER 1234567 200111-01-01 176990-01-01 174356-07 177035-01 180305-001 HEALTH AND USAGE MONITORING SYSTEM . **ESD** DATA ACQUISITION UNIT ..battery, lithium .MOUNTING TRAY, ELECTRICAL EQUIPMENT . **ESD** COCKPIT DISPLAY UNIT/DATA TRANSFER UNIT
USAGE CODE
UNITS PER ASSY REF 1 1 1 1
Effectivity: All

Hums PDF

Uploaded by

Copyright:

Available Formats

Hums PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hums PDF

Uploaded by

Copyright:

Available Formats

AGUSTA AB-139 HELICOPTER

HEALTH AND USAGE MONITORING SYSTEM (HUMS)

OPERATION AND MAINTENANCE SOURCE DATA

1ST EDITION 2002-07-08

SMITHS AEROSPACE, INC., ELECTRONIC SYSTEMS - GRAND RAPIDS

TDM 2128 UNCLASSIFIED

39-A-31-30-00-00A-001A-A 2002-07-08 Page 1 of 2

TDM 2128 UNCLASSIFIED

This page intentionally left blank

39-A-31-30-00-00A-001A-A 2002-07-08 Page 2 of 2

TDM 2128 UNCLASSIFIED

39-A-31-30-01-00A-001A-A 2002-07-08 Page 1 of 2

TDM 2128 UNCLASSIFIED

This page intentionally left blank

39-A-31-30-01-00A-001A-A 2002-07-08 Page 2 of 2

TDM 2128 UNCLASSIFIED

CHAPTER 1 OPERATION AND MAINTENANCE INFORMATION

39-A-31-30-02-00A-001A-A 2002-07-08 Page 1 of 4

39-A-31-30-02-00A-001A-A 2002-07-08 Page 2 of 4

39-A-31-30-02-00A-001A-A 2002-07-08 Page 3 of 4

TDM 2128 UNCLASSIFIED

This page intentionally left blank

39-A-31-30-02-00A-001A-A 2002-07-08 Page 4 of 4

TDM 2128 UNCLASSIFIED

Chapter 1.1 HUMS introduction Table of contents

List of HUMS major components

39-A-31-30-00-00A-011A-A Chapter 1.1 2002-07-08 Page 1 of 4

TDM 2128 UNCLASSIFIED

Cockpit Display Unit/Data Transfer Unit

List of dedicated sensors

39-A-31-30-00-00A-011A-A Chapter 1.1 2002-07-08 Page 2 of 4

TDM 2128 UNCLASSIFIED

Figure 1. HUMS LRUs

39-A-31-30-00-00A-011A-A Chapter 1.1 2002-07-08 Page 3 of 4

TDM 2128 UNCLASSIFIED

This page intentionally left blank

39-A-31-30-00-00A-011A-A Chapter 1.1 2002-07-08 Page 4 of 4

TDM 2128 UNCLASSIFIED

Chapter 1.2 Data acquisition unit function

Data acquisition unit (DAU)

39-A-31-30-00-00A-042A-A Chapter 1.2 2002-07-08 Page 1 of 2

TDM 2128 UNCLASSIFIED

Figure 1. DAU identification view

39-A-31-30-00-00A-042A-A Chapter 1.2 2002-07-08 Page 2 of 2

TDM 2128 UNCLASSIFIED

Chapter 1.3 Cockpit display unit/data transfer unit function

Cockpit display unit/data transfer unit

Controls and displays

39-A-31-30-00-00A-043A-A Chapter 1.3 2002-07-08 Page 1 of 4

TDM 2128 UNCLASSIFIED

39-A-31-30-00-00A-043A-A Chapter 1.3 2002-07-08 Page 2 of 4

TDM 2128 UNCLASSIFIED Access Door Release Power indicator (red)

Figure 1. Cockpit display unit/data transfer unit (CDU/DTU) identification view

39-A-31-30-00-00A-043A-A Chapter 1.3 2002-07-08 Page 3 of 4

TDM 2128 UNCLASSIFIED

Access Door Release

DTD Access Door

CDU/DTU with Door Closed

Power Indicator Write Cycle Indicator