139 Hums

TDM 2128
AGUSTA
AB-139 HELICOPTER
HEALTH AND USAGE MONITORING SYSTEM (HUMS)

OPERATION AND MAINTENANCE
SOURCE DATA
© 2006 Smiths Aerospace LLC, Electronic Systems – Grand Rapids All Rights Reserved
DESTINATION CONTROL NOTICE

THESE COMMODITIES, TECHNOLOGY, OR SOFTWARE ARE EXPORTED FROM THE UNITED STATES IN ACCORDANCE WITH
THE EXPORT ADMINISTRATION REGULATIONS. DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED.
PROPRIETARY DATA – IN CONFIDENCE

THE INFORMATION CONTAINED HEREIN IS PROPRIETARY TO SMITHS AEROSPACE, INC., ELECTRONIC SYSTEMS – GRAND
RAPIDS AND SHALL NOT BE REPRODUCED OR DISCLOSED IN WHOLE OR IN PART OR USED FOR ANY DESIGN OR
MANUFACTURE EXCEPT WHEN SUCH USER POSSESSES DIRECT WRITTEN AUTHORIZATION FROM SMITHS AEROSPACE,
INC., ELECTRONIC SYSTEMS – GRAND RAPIDS.
Agusta 2ND EDITION 2005-1-28

Change 1 2006-2-24
SMITHS AEROSPACE LLC,

ELECTRONIC SYSTEMS - GRAND RAPIDS
TDM 2128
UNCLASSIFIED
INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.

LIST OF EFFECTIVE PAGES
Dates of issue for original and changed pages are:
Original .... 0 ....28 January 2005

Change .... 1 ....24 February 2006
TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 116 CONSISTING OF THE FOLLOWING:
Document Page Change Document Page Change

Identifier No. No. Identifier No. No.
Title page 1 1 Chapter 1.13 1 thru 3 0

List of effective pages 1 1 4 and 5 1
Table of contents 1 and 2 0 6 0
Introduction 1 and 2 0 Chapter 1.14 1 thru 8 0
Chapter 1 1 1 Chapter 1.15 1 thru 4 0
2 0 Chapter 1.16 1 and 2 0
3 1 Chapter 1.17 1 thru 4 0
4 0 Chapter 1.18 1 and 2 0
Chapter 1.1 1 1
2 thru 4 0 Chapter 2 1 thru 3 1
Chapter 1.2 1 and 2 0 4 0
Chapter 1.3 1 thru 4 0
Chapter 1.4 1 1 Chapter 3 1 thru 4 0
2 0
3 and 4 1
5 1
6 thru 8 0
9 and 10 1
11 thru 13 0
14 and 15 1
16 0
17 1
18 0
Chapter 1.6 1 0
2 1
3 and 4 0
Chapter 1.8 1 1
2 thru 4 0
5 1
6 1
Chapter 1.9 1 and 2 0
Chapter 1.10 1 0
2 1
Chapter 1.11 1 0
2 1
Chapter 1.12 1 and 2 0
Effectivity: All 39-A-31-30-00-LOAP-001A-A

Change 1 2006-2-24 Page 1 of 1
TDM 2128
UNCLASSIFIED
Table of contents Chapter
INTRODUCTION .......... ...................................... ..............................................................................................1

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
Blade Tracking Tape Installation ...........................................................................................................1.18
AIRCREW FLIGHT INFORMATION.................... …. .........................................................................................2
ILLUSTRATED PARTS CATALOGUE................ …. .........................................................................................3
Effectivity: All 39-A-31-30-00-00A-001A-A

2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED
This page intentionally left blank.

2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
INTRODUCTION
1 PURPOSE
The purpose of this manual is to provide aircraft-level source data on the Health and Usage
Monitoring System (HUMS) 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.
2 SCOPE
This manual covers the on-board components of the HUMS, specifically the components
supplied by Smiths Aerospace LLC, Electronic Systems-Grand Rapids. Coverage of other
HUMS components and related equipment is limited to general information only. HUMS
installation-related information is not included.
3 ARRANGEMENT
This manual is divided into the following three chapters:
3.1 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.

2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED

2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
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 .........................................................................................................................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 accelerometer....................................................................2
2.2 Rotor track and balance accelerometer ...................................................................................2
2.3 Load factor accelerometer........................................................................................................2
3 Tachometers ....................................................................................................................................3
3.1 Main rotor tachometer ..............................................................................................................3
3.2 Tail rotor tachometer ................................................................................................................3
3.3 Drivetrain tachometer ...............................................................................................................3
4 Sensor reference designator cross reference listing ........................................................................3
1.5 HUMS OPERATION..................................... ..............................................................................................1
1 Introduction.......................................................................................................................................2
2 Equipment Interface .........................................................................................................................2
3 HUMS Initialization and Startup .......................................................................................................5
3.1 Initialization...............................................................................................................................5
3.2 Startup ......................................................................................................................................5
3.3 DTD operations ........................................................................................................................5
4 HUMS operations and ground/flight regimes ...................................................................................6
5 Data acquisition and processing ......................................................................................................6
6 Transmission vibration monitoring ...................................................................................................8
7 Rotor track and balance operations .................................................................................................9
7.1 Rotor health monitoring ............................................................................................................9
7.2 Rotor tuning ............................................................................................................................10
8 Usage monitoring ...........................................................................................................................10
8.1 Logbook functions ..................................................................................................................10
8.2 Structural usage monitoring (SUM) ........................................................................................11
8.3 Transmission usage monitoring (TUM) ..................................................................................12

TDM 2128
UNCLASSIFIED
9 Engine power assurance (EPA) .....................................................................................................13

10System built in test .........................................................................................................................13
10.1 Start-up BIT ............................................................................................................................13
10.2 Periodic BIT ............................................................................................................................14
10.3 Initiated BIT ............................................................................................................................14
10.4 Status and BIT log displays ....................................................................................................14
1.6 ADVISORY MESSAGES.............................. ..............................................................................................1
1 Advisory messages ..........................................................................................................................1
1.7 DISPLAY PAGES .. ...................................... ..............................................................................................1
1Menu tree .........................................................................................................................................2
2Detailed displays ..............................................................................................................................2
3Startup ..............................................................................................................................................4
4Top-level menu.................................................................................................................................5
5A/C maintenance menu....................................................................................................................5
5.1 RT&B ........................................................................................................................................5
5.2 EPA...........................................................................................................................................7
5.3 DPD ..........................................................................................................................................8
6 Configure RBT................................................................................................................................11
6.1 Modification of RBT status......................................................................................................11
7 DTD status......................................................................................................................................12
8 View logbook ..................................................................................................................................13
8.1 Last operation.........................................................................................................................13
8.2 Cumulative totals ....................................................................................................................14
9 BIT ..................................................................................................................................................14
9.1 Initiate IBIT..............................................................................................................................14
9.2 Viewing BIT results.................................................................................................................15
9.3 Clearing BIT results ................................................................................................................16
10 Setup ..............................................................................................................................................16
10.1 Upload ....................................................................................................................................16
10.2 Date/Time ...............................................................................................................................17
10.3 Configuration P/N ...................................................................................................................18
11 Event mark .....................................................................................................................................18
12 Pop up displays ..............................................................................................................................19
12.1 CDU/DAU communication failure ...........................................................................................20
12.2 File 80% full indication............................................................................................................20
12.3 File 100% full indication..........................................................................................................20
12.4 File Overwrite Indication .........................................................................................................20
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............................................................................................................................4
2.10 DTD removal ............................................................................................................................5
2.11 Log book data viewing..............................................................................................................5

2006-2-24 Page 2 of 4
TDM 2128
UNCLASSIFIED
2.12 Configuring rotor blade tracker.................................................................................................5

2.13 Performing a manual acquisition (Event mark) ........................................................................5
1.9 OPERATIONAL CHECKOUT PRELIMINARY SET UP ..............................................................................1
1Operational 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
1.18 BLADE TRACKING TAPE INSTALLATION ..............................................................................................1
1 Blade Tape Installation .....................................................................................................................2

TDM 2128
UNCLASSIFIED

2006-2-24 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.1
HUMS introduction
Table of contents Page

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
List of figures Page

1 HUMS LRUs 3
1 System description
The Health and Usage Monitoring System (HUMS) is an integrated recording and monitoring
system. The HUMS provides the AB-139 helicopter with structural and transmission usage
monitoring (TUM), transmission vibration monitoring (TVM), rotor track and balance (RTB), and
engine power assurance (EPA) 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 built-in test (BIT) of the system and interfacing sensors, and
performing RTB and EPA checks. In addition, when a universal tracking device (UTD) referred
to as a rotor blade tracker (RBT) 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 is 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 Number Used Part Number

Data Acquisition Unit 1 176990-03-01
consisting of the following:
Auxiliary Acquisition and Tracker Power 1 175394-01-01 or
Supply CCA 177169-01-01
Vibration Acquisition Unit CCA 1 174357-03 or 56000001
or 56000005
Enhanced Digital Processing Unit CCA 1 176993-01-01
System Power Supply 1 175434-01-02
Battery 1 3B1065-XB
Cockpit Display Unit/Data Transfer Unit 1 180305-001

Chapter 1.1
TDM 2128
UNCLASSIFIED
1.3 List of dedicated sensors

The following is a list of HUMS dedicated sensors:
Sensor Number Used Part Number or Type

Designation
Main Rotor Tachometer 1 Electro Corp. P/N 3030AN
Drivetrain Tachometer 1 Agusta P/N EA6300V083-001
Tail Rotor Tachometer 1 Electro Corp. P/N 3025
Rotor Track and Balance Accelerometers 4 Dytran Instruments P/N 3062A1
Transmission Vibration Accelerometers 11 Agusta P/N 3G6340V00151
Load Factor Sensor 1 Magnatek P/N 3001-01-100-4
1.4 Associated equipment

The following is a list of associated equipment used with HUMS:
Item Number Used Part Number

Data Transfer Device 1 SDP3BI-384-101
Rotor Blade Tracker 1 29750000

Chapter 1.1
2006-2-24 Page 2 of 4
TDM 2128
UNCLASSIFIED
Figure 1. HUMS LRUs

Chapter 1.1
2006-2-24 Page 3 of 4
TDM 2128
UNCLASSIFIED

Chapter 1.1
2006-2-24 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.2
Data acquisition unit function

1 Data acquisition unit 1

1 Data Acquisition Unit identification view 2
1 Data acquisition unit

The Data Acquisition Unit (DAU) (figure 1) is the system’s interface with the Health and Usage
Monitoring System (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 its 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/Data Transfer Unit (CDU/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 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 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.

Chapter 1.2
2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED
Figure 1. Data acquisition unit identification view

Chapter 1.2
2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
Chapter 1.3
Cockpit display unit/data transfer unit function

1 Cockpit display unit/data transfer unit 1
2 Controls and displays 1

1 Cockpit display unit/data transfer unit identification view 3
2 Cockpit display unit/data transfer unit front panel view 4
List of tables Page

1 CDU/DTU controls and displays 2
1 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 Health and Usage Monitoring System
(HUMS) 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, Night Vision Imaging
System (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
with the Data Acquisition Unit (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, configuration parameters and for recording 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 pushbutton lighting.
2 Controls and displays

For a description of the controls and displays refer to table 1 and figure 2.

Chapter 1.3
2005-1-28 Page 1 of 4
TDM 2128
UNCLASSIFIED
Table 1. CDU/DTU controls and displays

Control/Display 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
ENT
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 page when the È (down arrow) is displayed on the menu. Continuing to
press the PAGE key will cycle through all available pages and then returns
to the first page.
The CLR (clear) key is used to perform three functions:
(1) Used to clear informational messages.
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 EPA measurement.
If the HUMS configuration parameters have been set up to allow manual

EVNT acquisitions then 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 the 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
> or < cursor is 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
Ejector button
DTD compartment when the DTD access door is open.

Chapter 1.3
2005-1-28 Page 2 of 4
TDM 2128
UNCLASSIFIED
Access Door Allows DTD access door to flip open to gain access to DTD.
Release
The power light emitting diode (LED) indicator is in view in the DTD
Power indicator
compartment when the DTD access door is open. The indictor comes on
(red)
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 identification view

Chapter 1.3
2005-1-28 Page 3 of 4
TDM 2128
UNCLASSIFIED
> MAINT DTD STS EVNT PAGE
RBT SYS VAL ENT CLR
Access Door DTD Access Door

Release
CDU/DTU with Door Closed
> MAINT DTD STS EVNT PAGE
RBT SYS VAL ENT CLR
Ejector Button Power Indicator

Write Cycle Indicator
CDU/DTU with Door Open
Figure 2. Cockpit display unit/data transfer unit front panel view

Chapter 1.3
2005-1-28 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.4
HUMS dedicated sensors function

1 General 1
2 Accelerometers 1
2.1 Transmission vibration monitoring accelerometer 2
2.2 Rotor track and balance accelerometer 2
2.3 Load factor accelerometer 2
3 Tachometers 3
3.1 Main rotor tachometer 3
3.2 Tail rotor tachometer 3
3.3 Drivetrain tachometer 3
4 Sensor reference designator cross reference listing 3
List of tables Page
1 Accelerometer details 2
2 Tachometer details 3
3 Sensor reference designator cross reference list 3
1 General
The Health and Usage Monitoring System (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.
2 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 Data Acquisition Unit (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.
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.

Chapter 1.4
TDM 2128
UNCLASSIFIED
2.1 Transmission vibration monitoring accelerometer

The 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 accelerometer
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 accelerometer
The load factor accelerometer is designed to sense aircraft vertical acceleration, which enables
the DAU 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 main cabin floor.
Table 1. Accelerometer details

Accelerometer Location Accelerometer Function
A1 Engine #1 Transmission Vibration Monitoring
A2 Engine #2 Transmission Vibration Monitoring
A3 Annulus Gear (Forward) Transmission Vibration Monitoring
A4 Annulus Gear (Right) Transmission Vibration Monitoring
A5 Annulus Gear (Aft) Transmission Vibration Monitoring
A6 Tail Drive Shaft Take Off Transmission Vibration Monitoring
A7 Tail Drive Shaft Hangar Bearing Transmission Vibration Monitoring
A8 Intermediate Gear Box (IGB) Transmission Vibration Monitoring
A9 Tail Gear Box Transmission Vibration Monitoring
A10 Engine #1 (2nd Stage) Transmission Vibration Monitoring
A11 Engine #2 (2nd Stage) Transmission Vibration Monitoring
A20 Main Rotor (Lateral) Rotor Track and Balance
A21 Main Rotor (Vertical) Rotor Track and Balance
A22 Tail Rotor (Lateral) Rotor Track and Balance
A23 Tail Rotor (Vertical) Rotor Track and Balance
- Main Cabin Floor Load factor sensing

Chapter 1.4
2006-2-24 Page 2 of 4
TDM 2128
UNCLASSIFIED
3 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 (TVM) measurements. Refer to Table 2 for
tachometer details.
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 in 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 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 Location Tachometer Function
AZ1 Main Rotor Variable Reluctance Speed Sensor (1 pulse/rev)
AZ2 Tail Rotor Variable Reluctance Speed Sensor (1 pulse/rev)
AZ3 Drivetrain (Transmission) Multi-pulse (29 pulses/rev)
4 Sensor reference designator cross reference listing

Refer to Table 3 for a cross reference listing of HUMS sensor reference designators to the
reference designators used on Agusta engineering drawings.
Table 3. Sensor reference designator cross reference list

HUMS Reference Agusta Reference
Sensor
Designator Designator
Engine #1 Accelerometer A1 MT23
Engine #2 Accelerometer A2 MT24
Annulus Gear (Forward) Accelerometer A3 MT25
Annulus Gear (Right) Accelerometer A4 MT26
Annulus Gear (Aft) Accelerometer A5 MT27
Tail Drive Shaft Take Off Accelerometer A6 MT30
Tail Drive Shaft Hangar Bearing Accelerometer A7 MT38
Intermediate Gear Box (IGB) Accelerometer A8 MT39

Chapter 1.4
TDM 2128
UNCLASSIFIED
HUMS Reference Agusta Reference

Sensor
Designator Designator
Tail Gear Box Accelerometer A9 MT31
Engine #1 (2nd Stage) Accelerometer A10 MT29
Engine #2 (2nd Stage) Accelerometer A11 MT28
Main Rotor (Lateral) Accelerometer A20 MT40
Main Rotor (Vertical) Accelerometer A21 MT36
Tail Rotor (Lateral) Accelerometer A22 MT35
Tail Rotor (Vertical) Accelerometer A23 MT37
Main Cabin Floor Accelerometer LFS MT41
Main Rotor Tachometer AZ1 MT32
Tail Rotor Tachometer AZ2 MT33
Drivetrain (Transmission) Tachometer AZ3 MT34

Chapter 1.4
TDM 2128
UNCLASSIFIED
Chapter 1.5
HUMS operation

1 Introduction 2
2 Equipment interface 2
3 HUMS initialization and startup 5
3.1 Initialization 5
3.2 Startup 5
3.3 DTD operations 5
4 HUMS operations and ground/flight regimes 6
5 Data acquisition and processing 6
6 Transmission vibration monitoring 8
7 Rotor track and balance operations 9
7.1 Rotor health monitoring 9
7.2 Rotor tuning 10
8 Usage monitoring 10
8.1 Logbook functions 10
8.1.1 Operation time 10
8.1.2 Flight time 10
8.1.3 Flight time fail time 11
8.1.4 Landing count 11
8.1.5 Rotor starts 11
8.1.6 Rotor turning time 11
8.1.7 Rotor speed fail time 11
8.1.8 One engine inoperative (OEI) time 11
8.2 Structural usage monitoring (SUM) 11
8.3 Transmission usage monitoring (TUM) 12
8.3.1 TUM time history log 12
8.3.2 TUM event log 12
9 Engine power assurance (EPA) 13
10 System built in test 13
10.1 Start-up BIT 13
10.2 Periodic BIT 14
10.3 Initiated BIT 14
10.4 Status and BIT log displays 14

1 HUMS block diagram 4
List of tables Page

1 HUMS operation start/stop criteria 6
2 Aircraft input parameters 7
3 Direct parameter display list 8
4 Transmission monitoring components 9
5 RTB monitoring components 9
6 HUMS status and BIT log displays 15

Chapter 1.5
2006-2-24 Page 1 of 18
TDM 2128
UNCLASSIFIED
1 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 On-
Board System (OBS). The DTD is also used as the means to upload new configuration data to
the OBS.
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 (TVM)
• Usage Monitoring
• Rotor Track and Balance (RTB) Operation
• Engine Power Assurance (EPA)
• Built In Test (BIT)
2 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 called a vertical load sensing accelerometer is
used to detect vibration levels in the vertical direction. Power is supplied separately to this

Chapter 1.5
2006-2-24 Page 2 of 18
TDM 2128
UNCLASSIFIED
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 (RBT). 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). The +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.

Chapter 1.5
2006-2-24 Page 3 of 18
TDM 2128
UNCLASSIFIED
+5VDC
+28VDC (Panel Lighting)
Data Acquisition Unit
5A
(DAU)
+28VDC
1.5A
CDU/DTU
ARINC 429
RS-422 Cockpit Display Unit
(CDU)
Modular Avionic Unit Enhanced Data
(MAU) Processing Unit
(EDPU)
ARINC 429 RS-422 Data Transfer Unit
(DTU)
Data
Transfer
RTB Accelerometers 4
Device
(4) (DTD)
(PCMCIA CARD)
TVM Accelerometers 11
(11)
Vibration Acquistion Unit

(VAU)
Main Rotor Tachometer
Tail Rotor Tachometer

Rotor Data
DrivetrainTachometer
Universal
Tracking
+24 VDC Device
(UTD)*
+28VDC +12 VDC
1A
Auxilary Acquistion and (Lamp Power)
Load Acelerometer Tracker Power Supply
(AATPS)
+5VDC
(Panel Lighting)
* When Installed
Figure 1. HUMS block diagram

Chapter 1.5
2006-2-24 Page 4 of 18
TDM 2128
UNCLASSIFIED
3 HUMS Initialization and Startup

3.1 Initialization
The 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
Enhanced Digital Processing Unit (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. The
values entered are only used by HUMS and don't 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 (NVM) to ensure both agree. If the aircraft ID checks
good, HUMS system processing will begin.
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 (EPA) data files on the DTD
become full, recording is stopped or the data is overwritten on a first in first out basis. To stop
recording or to overwrite the data is configurable on a file-by-file basis. The same DTD can be
used interchangeably on any HUMS-equipped aircraft so long as there is 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.

Chapter 1.5
Change 1 2006-2-24 Page 5 of 18
TDM 2128
UNCLASSIFIED
4 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.
Table 1. HUMS operation start/stop criteria

Operation Criteria
Start A "HUMS Operation" starts when at least one engine gas generator speed
(NG) is greater than 50%.
Stop Both NG below 10% and the aircraft is in GROUND MODE.
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:
• Vibration Acquisition Unit (VAU) (TVM and rotor health monitoring)
• Usage (Structural Usage Monitoring (SUM)

The 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 (SUM) type regimes.
HUMS VAU and Usage regimes are configurable and can be uploaded to the aircraft system
using a configuration DTD.
All usage 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.
5 Data acquisition and processing

The HUMS acquires and processes aircraft data from the 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.

Chapter 1.5
2006-2-24 Page 6 of 18
TDM 2128
UNCLASSIFIED
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

Chapter 1.5
2006-2-24 Page 7 of 18
TDM 2128
UNCLASSIFIED
Table 3. Direct parameter display list

Type Name
Aircraft Aircraft ID
Parameters 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
6 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 (TVM) occurs automatically based on certain configured flight regimes.
TVM consists of a suite of diagnostic techniques comprised of shaft, gear and bearing vibration
analysis. If the HUMS configuration parameters have been set up to allow manual vibration
acquisition an acquisition can 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
VAU. The HUMS utilizes 11 TVM accelerometers to sense transmission and drivetrain
vibrations. In addition, the VAU receives component speed information from 3 aircraft mounted

Chapter 1.5
2006-2-24 Page 8 of 18
TDM 2128
UNCLASSIFIED
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
data 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 table 4 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

A1-A6, A10, A11 AZ3 Gear, shaft, and bearing faults.
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 Rotor track and balance operations

7.1 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, The accelerometers 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.
Table 5. RTB monitoring components
Components Monitored Accelerometers Used Tachometer Purpose
Main rotor lateral/vertical A20, A21 AZ1 Rotor unbalance and faults
Tail rotor lateral/vertical A22, A23 AZ2 Rotor unbalance and faults.

Chapter 1.5
Change 1 2006-2-24 Page 9 of 18
TDM 2128
UNCLASSIFIED
7.2 Rotor tuning
When an RBT 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 is 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. If an RBT is not installed, HUMS can
still perform rotor tuning balance operations as described above. However, it just will not be
able to collect rotor track data.
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.
8 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 non-volatile memory (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 system is configured.
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.

Chapter 1.5
Change 1 2006-2-24 Page 10 of 18
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
One engine inoperative (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 a moving
average value of the following parameters over the duration of each regime:
• Roll angle
• Pitch angle
• True airspeed
• Longitudinal acceleration
• Ratioed airspeed
• Load factor
• Engine 1 torque
• Engine 2 torque
• Density altitude
• Radio altitude
As part of the Structural Usage Monitoring (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 includes 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.

Chapter 1.5
2006-2-24 Page 11 of 18
TDM 2128
UNCLASSIFIED
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 Transmission Usage Monitoring (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.
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

Chapter 1.5
2006-2-24 Page 12 of 18
TDM 2128
UNCLASSIFIED
9 Engine power assurance (EPA)

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 Engine Air Particle
Separator (EAPS), heater, and anti-ice systems are off. HUMS will also 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 is not met, HUMS will terminate the
acquisition and inform the operator via a CDU display. Once initiated, EPA checks require
approximately 30 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 NVM 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 related 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 types 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.
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

Chapter 1.5
2006-2-24 Page 13 of 18
TDM 2128
UNCLASSIFIED
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, if the HUMS configuration parameters have
been set up to allow manual vibration acquisitions, the tachometers can be checked when a
manual vibration acquisition is commanded by the operator once the engines are running. If
the HUMS configuration parameters have not been set up to allow manual acquisitions, then
the tachometers are only checked during flight when the system performs automatic vibration
acquisitions. SBIT requires no operator action to initiate and is automatically scheduled during
the system power-up 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.
If an RBT is fitted to the aircraft, PBIT will also perform tests on the unit to verify its operation.
The RBT must be powered up in order for PBIT to be performed. This is accomplished by
enabling the RBT for DAY or NIGHT operation. If using HUMS top-level software P/N 553477-
01-01, and the RBT is enabled before the engines are started, PBIT may cause AATPS 12V
ON, AATPS 24V ON, and AATPS LAMP SW BIT errors to be detected and displayed upon
engine start. This is due to a power drop on the unit during the engine start. No actual damage
or harm to the system or RBT occurs when this happens. If these faults are detected due to
enabling of the tracker before engines are started, the fault should be cleared after the mission
has been accomplished and the engines have been shut down, with no further maintenance
action required. (Note: To determine which top-level software P/N is being used, inspect the
label on the front of the DAU).
Also included 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.

Chapter 1.5
Change 1 2006-2-24 Page 14 of 18
TDM 2128
UNCLASSIFIED
Table 6. HUMS status and BIT log displays

HUMS BIT LOG ENTRY FAILURE CONDITION SYSTEM EFFECT
STATUS
MESSAGE
ID FAIL None Aircraft ID number stored in Cumulative logbook values
DAU is corrupted or aircraft are invalidated and no data
ID received from MAU is downloaded to ground
invalid or no aircraft ID station.
received from MAU.
OP# FAIL None Operation number set No data downloaded to
invalid due to failure or ground station.
mismatch of aircraft ID.
DAU FAIL DAU FAIL Internal DAU hardware Partial or complete loss of
EDPU OFP CHKSUM failure HUMS functions depending
DAU FAIL upon type of failure.
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
EDPU CFG CONFIG FAIL EDPU configuration Loss of all HUMS functions
EDPU parameters corrupted or not
loaded.

Chapter 1.5
Change 1 2006-2-24 Page 15 of 18
TDM 2128
UNCLASSIFIED

STATUS
MESSAGE
VAU CFG CONFIG FAIL VAU configuration Loss of all vibration-related
VAU parameters corrupted or not processing. Usage
loaded. monitoring still available.
DTU FAIL CDU/DTU FAIL DTU not responding to Inability to record any data
DTU RESPONSE commands from DAU. to DTD or upload data from
DTD FAIL DTD FAIL DTD cannot be read from or the DTD. All other
WRAP written to. functions still available.
DTD FMT DTD FAIL DTD format incorrect. Inability to record any data
FORMAT Missing or damaged files on to DTD. All other functions
DTD. still available.
NO DTD DTD NOT None Inability to record any data
PRESENT to DTD or upload data from
the DTD. All other
functions still available.
VAU FAIL DAU FAIL VAU circuit card assembly Vibration monitoring and
VAU FAILED hardware failure RTB cannot be performed.
DAU FAIL Usage monitoring still
VAU RESPONSE available.
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
VAU DEGR DAU FAIL VAU circuit card analog Partial loss of vibration data
VAU ADC 0 input circuitry failure acquisition depending upon
DAU FAIL failure.
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

Chapter 1.5
2006-2-24 Page 16 of 18
TDM 2128
UNCLASSIFIED

STATUS
MESSAGE
VAU DEGR DAU FAIL
(Cont) VAU CH 2 GAIN
DAU FAIL VAU circuit card analog Partial loss of vibration data
VAU CH 3 GAIN input circuitry failure acquisition depending upon
DAU FAIL failure.
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
TVM DEGR TACH AZ3 FAIL Transmission tachometer Degraded transmission
failure vibration monitoring.
ACCEL Axx FAIL Accelerometer output Degraded transmission
BIAS amplifier failure. vibration monitoring. Loss
(xx = Accel No. 1 - 11) of ability to record some
ACCEL Axx FAIL Signal received from vibration data, depending
SATURATION (xx = accelerometer is not within upon which accelerometer
Accel No. 1 - 11) expected signal range. has failed.
RTB DEGR TACH AZ1 FAIL Tail Rotor Tachometer Degraded rotor vibration
failure. monitoring and rotor tuning.
TACH AZ2 FAIL Main Rotor Tachometer
failure.
TRACKER FAIL Rotor Blade Tracker failure Rotor tuning cannot be
performed using RBT.
DAU FAIL AATPS RBT lamp switch
AATPS LAMP SW failure.
DAU FAIL AATPS RBT power supply
AATPS 24V ON control failure.
DAU FAIL
AATPS 24V OFF
DAU FAIL AATPS RBT lamp power
AATPS 12V ON failure.
DAU FAIL
AATPS 12V OFF
ACCEL Axx FAIL Accelerometer output Degraded RTB vibration
BIAS amplifier failure. monitoring. Loss of ability
(accel no. 20 - 23) to record some vibration
ACCEL Axx FAIL Signal received from data, depending upon
SATURATION accelerometer is not within which accelerometer has
(accel no. 20 - 23) expected signal range. failed. Loss of ability to
perform RTB.

Chapter 1.5
Change 1 2006-2-24 Page 17 of 18
TDM 2128
UNCLASSIFIED

STATUS
MESSAGE
CDU FAIL CDU/DTU FAIL CDU not responding to DAU Loss of CDU/DTU control
CDU RESPONSE commands and display functions. No
CDU/DTU FAIL Internal CDU failure control over HUMS
CDU BIT functions.
LFS FAIL LOAD FACTOR Load factor sensor output Structural usage monitoring
SENSOR FAIL invalid. will be degraded.
DAU BATT RTC BATTERY DAU battery voltage low. Possible loss of HUMS
VOLTAGE LOW time and date if battery
goes completely dead.
INIT SYS None At least one cumulative Cumulative logbook values
logbook entry invalid. invalidated.

Chapter 1.5
2006-2-24 Page 18 of 18
TDM 2128
UNCLASSIFIED
Chapter 1.6
Advisory messages

1 Advisory messages 1
List of tables Page

1 Advisory messages 1
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

Message Description
A/C ID MISMATCH 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.
A/C ID UNAVAILABLE 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.
ACQUISITION COMPLETE This message is displayed if a data acquisition completes

without any errors.
ACQUISITION IN Indicates that a manually commanded vibration/RTB data

PROGRESS acquisition is in progress or an Engine Power Assurance test
is in progress.
ACQUISITION TIMEOUT This message is displayed if a data acquisition fails to return

any status.
BIT LOG CLEARED Displayed after operator-initiated clear BIT log action to
indicate that BIT log has been cleared.
COMM FAIL Indicates that the CDU/DTU has lost communication with the
DAU for over one minute. Keys are locked until
communication is restored.

Chapter 1.6
2006-2-24 Page 1 of 4
TDM 2128
UNCLASSIFIED
Message Description
CONFIG DTD Indicates a configuration DTD has been installed when trying
to do an initialization upload.
CONFIGURATION DTD Displayed after SBIT is complete if a configuration DTD is
INSTALLED installed in CDU/DTU.
DATA UNSTABLE Displayed upon completion of engine power assurance test if

stability test of calculated engine margins fails.
DTD NOT INSTALLED Displayed after SBIT is complete if a DTD is not installed in
CDU/DTU.
“FILE ID" FILE XXX% FULL This is an indication to the operator that the data file on the
DTD with the name "FILE ID" is more than 80% full or 100%
full and not configured to wrap. XXX is the actual percentage
full.
“FILE ID" FILE OVERWRITE This is an indication to the operator that the data file on the
DTD with the name "FILE ID" has reached 100% of its
allocated capacity and is configured to wrap.
IBIT IN PROGRESS Displayed when the operator initiates IBIT. Remains

displayed for approximately 20-30 seconds.
INVALID DTD INSTALLED Displayed after SBIT is complete if an invalid (not correctly
formatted) DTD is installed in CDU/DTU.
INVALID INIT FILE Displayed during an initialization upload if the DTD contains an
invalid initialization file.
INVALID REGIME This message is displayed if the aircraft is not in a proper

regime for collecting engine EPA data.
INVALID SETUP Displayed if the aircraft is in a valid regime and the selected
engine is not properly configured for an EPA test for the
current regime.
NO CONFIG FILE Displayed when a configuration upload is attempted and DTD

does not contain a valid configuration file.
NO DTD This message is displayed when the operator attempts either

an initialization or a configuration upload, with no DTD
installed.
NO INIT FILE Displayed when an initialization upload is attempted and DTD

does not contain a valid initialization file.
OLD INIT FILE Displayed during an initialization upload if the DTD contains an
old initialization file.

Chapter 1.6
TDM 2128
UNCLASSIFIED
Message Description
SBIT IN PROGRESS Displayed initially upon power application to HUMS to indicate
that startup BIT is being performed.
UPLOAD COMPLETE Displayed upon completion of a successful initialization or

configuration data upload.
UPLOAD FAIL Displayed if the initialization file or configuration file was not
successfully uploaded from the DTD to the DAU.
UPLOAD IN PROGRESS Displayed when a valid initialization or configuration file is

being uploaded from the DTD.

Chapter 1.6
2006-2-24 Page 3 of 4
TDM 2128
UNCLASSIFIED

Chapter 1.6
2006-2-24 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.7
Display pages

1 Menu tree 2
2 Detailed displays 2
3 Startup 4
4 Top-level menu 5
5 A/C maintenance menu 5
5.1 RT&B 5
5.1.1 Running an acquisition 6
5.1.2 Viewing data 7
5.2 EPA 7
5.2.1 Running an acquisition 7
5.3 DPD 8
5.3.1 Aircraft parameters 9
5.3.2 Engine parameters 10
5.3.3 Drive system parameters 10
6 Configure RBT 11
6.1 Modification of RBT status 11
7 DTD Status 12
8 View logbook 13
8.1 Last operation 13
8.2 Cumulative totals 14
9 BIT 14
9.1 Initiate IBIT 14
9.2 Viewing BIT results 15
9.3 Clearing BIT results 16
10 Setup 16
10.1 Upload 16
10.1.1 Initialization upload 16
10.1.2 Configuration upload 17
10.2 Date/Time 17
10.2.1 Modification of date setting 18
10.2.2 Modification of time setting 18
10.3 Configuration P/N 18
11 Event Mark 18
12 Pop up display 19
12.1 CDU/DAU communication failure 20
12.2 File 80% full indication 20
12.3 File 100% full indication 20
12.4 File Overwrite 20

1 Display tree 3
List of tables Page

1 FileID definition 12

Chapter 1.7
2005-1-28 Page 1 of 22
TDM 2128
UNCLASSIFIED
1 Menu tree
Figure 1 shows the menu structure in a tree format.
2 Detailed displays
The detailed displays are organized by function as follows:
• Startup
• Top-Level Menu
• A/C Maintenance
• Configure RBT
• DTD Status
• View Logbook
• BIT
• Setup
• Event Mark
• Pop-Up Displays
Flashing is indicated by an underlined position in the display pages that follow.

Chapter 1.7
2005-1-28 Page 2 of 22
TDM 2128
UNCLASSIFIED
Startup
Process
View
A/C Config BIT Setup
Logbook
Maintenance RBT (Note 1) (Note 1)
(Note 1)
Last Op Run IBIT Upload

DTD
RT&B
Status
Summary Clear Log Initialization
Idle
View Log Config

FPOG
Hover Clock
Cruise
Config P/N
VNE
EPA
Engine 1
Engine 2
DPD
Aircraft
Engine
Note 1: This menu is not available in an operation.

Drive
System
Figure 1. Display tree

Chapter 1.7
2005-1-28 Page 3 of 22
TDM 2128
UNCLASSIFIED
3 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 Data Acquisition Unit (DAU) and the
Data Transfer Unit (DTU), a check is done of the DTD. This check can result in one of the
following displays:
D T D N O T
I N S T A L L E D
Or
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
Or
I N V A L I D D T D
I N S T A L L E D
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. If a file
reached 80% of its allocated capacity, the CDU will display:
f i l e i d
F I L E X X X % F U L L ↓
where “fileid” is the name of the file exceeding the limit and XXX is the actual percentage of the
allocated capacity used. The user can view all files more than 80% full by depressing the
“PAGE” key. The full list of “fileid”s is the same as in the DTD status menu. If a file reaches
100% of its allocated capacity and is not configured to wrap when full, the CDU displays the
same message where “fileid” is the name of the file exceeding the limit and XXX is the actual
percentage of the allocated capacity used. This list is cleared by pressing the “CLR” key or
starting an operation.
If a valid aircraft (A/C) identification (ID) is not available from the ARINC 429 bus, the system
will then display:
A / C I D
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 nonvolatile
memory (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

Chapter 1.7
2005-1-28 Page 4 of 22
TDM 2128
UNCLASSIFIED
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 Vibration Acquisition Unit (VAU) has not
completed its CSBIT, the initial screen will be displayed until the VAU CSBIT is complete or times out.
4 Top-level menu
The Top-Level menu contains two pages as shown below:
> M A I N T D T D S T S
T R K R ↓ X X M S G X X X
> L O G B K S E T U P
B I T ↓ 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
Enhanced Digital Processing Unit (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 D T D S T S
T R K R X X M S G X X X
5 A/C maintenance menu

Selecting “MAINT” from the Top-Level menu will display the A/C Maintenance menu as shown
below:
> R T & B D P D
E P A
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 ↓

Chapter 1.7
2005-1-28 Page 5 of 22
TDM 2128
UNCLASSIFIED
> 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 R O T O R
T A C H 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 R O T O R
T A C H F A I L ↓
T A I L R O T O R
T A I L R O T O R
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:
C O M P L E T E
An initiated RT&B acquisition can also fail to return any status, which will result in the following
CDU display:
T I M E O U T

Chapter 1.7
2005-1-28 Page 6 of 22
TDM 2128
UNCLASSIFIED
Pressing the “CLR” key will return to the RT&B menu with the cursor on the failed acquisition.
In this case, there will be no “DATA” indication to the right of the acquisition.
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 “FPOG” acquisition is run successfully,
the return display will look like:
I D L E
> F P O G ↓ D A T A
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
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 ↓
M R V E R T 1 R
1 2 . 3 4 I P S ↓
T R L A T 1 T
1 2 . 3 4 I P S ↓
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
Selecting “EPA” from the A/C Maintenance menu will display the EPA menu below:
> E N G 1
E N G 2
5.2.1 Running an Acquisition

Acquisitions are run by selecting the desired engine from the EPA menu. When an acquistion
is run, the system will first verify that all inputs required to calculate EPA are valid. If any EPA
input parameter is invalid, the CDU will display:
I N V A L I D
I N P U T

Chapter 1.7
2005-1-28 Page 7 of 22
TDM 2128
UNCLASSIFIED
“EPA" menu with the cursor on the last attempted acquisition.
If all EPA inputs are valid, the system will then verify that the aircraft is in a proper regime for
collecting EPA data. If the aircraft is not in a valid regime, the CDU will display:
I N V A L I D
R E G I M E
“EPA” menu with the cursor on the last attempted acquisition.
If the aircraft is in a valid regime, the system will then verify that the engine is properly
configured for EPA for the regime. If the configuration is not valid, the CDU will display:
I N V A L I D
S E T U P
The above three tests are running continuously throughout the acquisition. For example, if all
required parameters are valid at the outset of an acquisition, but halfway through the acquisition
a required parameter goes invalid, the acquisition will abort and the “INVALID DATA” message
will be displayed.
If all required parameters, and the regime and configuration are valid, the CDU will display:
I N P R O G R E S S
Upon completion of the acquisition, the system performs a stability check of the calculated
margins. If the stability check fails, the CDU will display:
D A T A
U N S T A B L E
If the stability test passes, the CDU will display the calculated Ng and ITT margins as shown:
N G M A R G I N
1 2 . 3 % ↓
I T T M A R G I N
1 2 . 3 D E G C ↓
Pressing the “CLR” key while either display is present will return to the “EPA” menu with the
cursor on the completed acquisition.
5.3 DPD
Direct Parameter Display (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 D R V S Y S
E N G I N E

Chapter 1.7
2005-1-28 Page 8 of 22
TDM 2128
UNCLASSIFIED
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 ↓
B A R O A L T
- 9 0 0 F T ↓
D A T E ( D D / M M / Y Y )
3 1 / 1 2 / 9 9 ↓
D E N S I T Y A L T
- 9 0 0 F T ↓
F L T / G N D S T A T U S
F L T ↓
T I M E ( H H : M M : S S )
2 3 : 5 9 : 5 9 ↓
H E A D I N G
- 1 7 9 D E G ↓
T A S
1 2 0 K T S ↓
L O A D F A C T O R
- 1 2 . 3 G ↓
O A T
- 5 5 D E G C ↓
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 ↓
R A D A L T
4 9 9 9 F T ↓
R O L L A N G L E
- 1 7 9 D E G ↓
R O L L R A T E
- 1 7 D E G / S ↓
V E R T S P D
- 1 9 9 F P M ↓

Chapter 1.7
2005-1-28 Page 9 of 22
TDM 2128
UNCLASSIFIED
V N E
1 2 0 K T S ↓
Y A W R A T E
- 1 7 D E G / S ↓
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 I T T
- 6 9 D E G C ↓
E N G 1 N F
1 4 7 % ↓
E N G 1 N G
1 1 2 % ↓
E N G 1 T Q
1 6 6 % ↓
E N G 2 I T T
- 6 9 D E G C ↓
E N G 2 N F
1 4 7 % ↓
E N G 2 N G
1 1 2 % ↓
E N G 2 T Q
1 6 6 % ↓
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:
I G B O I L T E M P
1 4 9 D E G C ↓
M G B O I L P R E S S
1 1 B A R S ↓
M G B O I L T E M P
1 4 9 D E G C ↓

Chapter 1.7
2005-1-28 Page 10 of 22
TDM 2128
UNCLASSIFIED
M A I N R T R T Q
9 6 2 2 8 N m ↓
R O T O R S P E E D
1 4 0 % ↓
T G B O I L T E M P
1 4 9 D E G C ↓
T R P D L P O S
8 5 D E G ↓
T A I L R T R T Q
3 7 2 0 N m ↓
Y A W A C T 1 P O S
- 8 . 4 m m ↓
Y A W A C T 2 P O S
- 8 . 4 m m ↓
key while displaying any parameter will return to the DPD menu with the cursor on “DRV SYS”.
6 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
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.

Chapter 1.7
2005-1-28 Page 11 of 22
TDM 2128
UNCLASSIFIED
7 DTD status
Selecting “DTD STS” from the Top-Level menu will display the current status of the Data
Transfer Device (DTD).
If a properly formatted DTD is installed, this option will display the space available on the DTD
for each file as shown below:
f i l e i d
F I L E X X X % F U L L ↓
E N D 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
VIB LOG viblog.hsd
If there is no DTD installed, the display will appear as:
D T D N O T
I N S T A L L E D
If a DTD is installed and contains a “config.hsd” file, the CDU will display:

Chapter 1.7
2005-1-28 Page 12 of 22
TDM 2128
UNCLASSIFIED
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:
I N V A L I D D T 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.
8 View logbook
Selecting “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 ↓
O P T I M E
1 . 2 H R S ↓
R O T O R S T A R T S
1 2 ↓
R O T O R T U R N T I M E
1 . 2 H R S ↓
N R F A I L T I M E
1 . 2 H R S ↓
F L I G H T T I M E
1 . 2 H R S ↓
F L T F A I L T I M E
1 . 2 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 ↓

Chapter 1.7
2005-1-28 Page 13 of 22
TDM 2128
UNCLASSIFIED
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 T I M E
1 2 3 4 5 . 6 H R S ↓
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 H R S ↓
key will return to the View Logbook menu with the cursor on “TOTAL”.
9 BIT
Selecting “BIT” from the Top-Level Menu will display the following BIT menu:
> I B I T C L R L O G
V W 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 power-
up plus some additional interactive CDU tests. The CDU will display the following for
approximately 20 - 30 seconds:
I B I T
I N P R O G R E S S

Chapter 1.7
2005-1-28 Page 14 of 22
TDM 2128
UNCLASSIFIED
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 S W I T C H
C L R E N D S 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
P A G E
E N T E R
R I G H T
D O W N
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. Below is an example of a
possible filtered BIT status display.
D A U F A I L
E D P U O F P C H K S U M ↓
A C C E L A 1 5 F A I L
B I A S ↓
E N D O F 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.

Chapter 1.7
2005-1-28 Page 15 of 22
TDM 2128
UNCLASSIFIED
9.3 Clearing BIT results

Selecting “CLR LOG” will clear the current BIT log and display the following on the CDU:
B I T L O G
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 L O C K
C O N F P N
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
I N P R O G R E S S
It should be noted that if the DTD containing the initialization file (init.hsd) isn’t formatted
correctly an “Invalid DTD Installed” message will appear, but the system will still allow the
initialization file to be uploaded. 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
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

Chapter 1.7
2005-1-28 Page 16 of 22
TDM 2128
UNCLASSIFIED
N O
I N I T F I L E
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 a
configuration file from the DTD. If a valid configuration file is present, the CDU will display:
U P L O A D
I N P R O G R E S S
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
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 3 0 / 1 2 / 0 2
T I M E 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 3 0 / 1 2 / 0 2
T I M E 1 6 : 4 5 : 5 1

Chapter 1.7
2005-1-28 Page 17 of 22
TDM 2128
UNCLASSIFIED
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 3 0 / 1 2 / 0 2
T I M E 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 3 0 / 1 2 / 0 2
> T I M E 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
5 5 3 4 7 6 0 1 0 1
Pressing the “CLR” key will return to the Setup menu with the cursor on “CONF PN”.
11 Event mark
If the HUMS configuration parameters have been set up to allow manual vibration acquisitions,
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:
I N P R O G R E S S
first page of the Top-Level menu with the cursor on “MAINT”.

Chapter 1.7
2005-1-28 Page 18 of 22
TDM 2128
UNCLASSIFIED
An event mark acquisition can result in display of a list of one or more of the following error
messages:
M A I N R O T O R
T A C H F A I L ↓
M A I N R O T O R
M A I N R O T O R
T A I L R O T O R
T A C H F A I L ↓
T A I L R O T O R
T A I L R O T O R
X M S N
T A C H F A I L ↓
X M S N
X M S N
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 Top-
Level menu with the cursor on “MAINT”.
If the acquisition completes without any tachometer failures, the CDU will display:
C O M P L E T E
Pressing the “CLR” key will return to the Top-Level menu with the cursor on “MAINT.
If the acquisition fails to return any status, the following will be displayed on the CDU:
T I M E O U T
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.

Chapter 1.7
2005-1-28 Page 19 of 22
TDM 2128
UNCLASSIFIED
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 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.
12.2 File 80% full indication
If a file reaches 80% of its allocated capacity, the CDU will display:
f i l e i d
F I L E X X X % F U L L
allocated capacity used. The full list of “fileid”s 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 manually-commanded 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.
12.3 File 100% full indication
If a file reaches 100% of its allocated capacity and is not configured to wrap when full, the CDU
will display:
f i l e i d
F I L E X X X % F U L L
allocated capacity used. The full list of “fileid”s 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 manually-commanded acquisition
was running at the time that a file reached 100% full, the display of the 100% full indication will
be delayed until all displays associated with the manual acquisition are complete.
12.4 File Overwrite Indication
If a file reaches 100% of its allocated capacity and is configured to wrap when full, the CDU will
display:
f i l e i d
F I L E O V E R W R I T E
where “fileid” is the name of the file exceeding the limit. The full list of “fileid”s 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,

Chapter 1.7
2005-1-28 Page 20 of 22
TDM 2128
UNCLASSIFIED
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 manually-
commanded acquisition was running at the time that a file reached 100% full, the display of the
overwrite indication will be delayed until all displays associated with the manual acquisition are
complete.

Chapter 1.7
2005-1-28 Page 21 of 22
TDM 2128
UNCLASSIFIED

Chapter 1.7
2005-1-28 Page 22 of 22
TDM 2128
UNCLASSIFIED
Chapter 1.8
Operating procedures

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 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 4
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 (Event mark) 5
1 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 Using the two arrow keys (DOWN, RIGHT), the cursor (> or <) is moved adjacent to the
desired field for data entry.
2 Pressing the ENT key causes the first character of the field to begin flashing.
3 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.
4 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.
5 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 Using the two arrow keys (DOWN, RIGHT), the cursor (> or <) is moved adjacent to the
desired field for data entry.
2 Pressing the ENT key causes the entire field to begin flashing.
3 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.).
4 After the desired selection has been made, pressing the ENT key causes the system to
accept the value.

Chapter 1.8
TDM 2128
UNCLASSIFIED
2 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
On-Board System (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 Ensure operational DTD is in the CDU/DTU.

2 On the CDU/DTU, access the Top Level Menu.
3 Press the PAGE key. Main menu page 2 is displayed.
4 Using the arrow keys, place the cursor next to SETUP and press the ENT key. Setup
menu page is displayed.
5 Using the arrow keys, place the cursor next to UPLOAD and press the ENT key. Upload
6 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.
7 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 Ensure configuration DTD is in the CDU/DTU.

5 Using the arrow keys, place the cursor next to UPLOAD and press the ENT key. Upload
6 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.
7 Press CLR key to return to UPLOAD menu page.
8 Remove configuration DTD from CDU/DTU.
2.3 Setting system date/time

The following instructions allow the operator to view and change system date and system time.

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.

Chapter 1.8
2006-2-24 Page 2 of 6
TDM 2128
UNCLASSIFIED
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.

4 Using the arrow keys, place the cursor next to CONF PN to and press the ENT key.
Configuration page is displayed with current value.
5 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.

3 Press the down arrow key to place the cursor next to BIT and press the ENT key. BIT menu
is displayed.
4 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.
5 Press each key on CDU/DTU keyboard except CLR key. Name of key pressed is displayed
on top line of CDU display.
6 Press the CLR key. HUMS top level menu is displayed and SYS VAL is displayed on
bottom right side of CDU/DTU display.
is displayed.
9 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.
10 Press PAGE key to cycle through messages or press CLR key to return to BIT menu page.

Chapter 1.8
2006-2-24 Page 3 of 6
TDM 2128
UNCLASSIFIED
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.

is displayed.
4 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.
5 To ensure the BIT log is cleared, perform IBIT in accordance with paragraph 2.5.
6 Press the CLR key to return to BIT menu.
2.7 Direct parameter display viewing

Direct Parameter Display (DPD) viewing instructions allow the operator to view parameters
associated with the aircraft, engine, and drive train system.

2 Using the arrow keys, place the cursor next to MAINT and press the ENT key. Aircraft
maintenance menu is displayed.
3 Using the arrow keys, place the cursor next to DPD and press the ENT key. DPD menu
page is displayed.
4 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.
5 Press the PAGE key to view the next page. Next parameter page is displayed.
6 Repeatedly press the PAGE key to continue viewing additional parameters.
7 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.

2 Using the arrow keys, place the cursor next to DTD STS and press the ENT key. First DTD
file status page is displayed.
3 Press the PAGE key to view the next page. Next DTD file status page is displayed.
4 Repeatedly press the PAGE key to continue viewing status of remaining DTD files.
5 Press the CLR key to return to HUMS top level menu page.
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 Slide door latch to the left. Door springs open.

2 With label side facing up, insert the memory card into the slot.
3 Seat memory card by pushing it towards the rear of the case until all motion stops. Ejector
button is in the extended position.
4 Close door until it latches.

Chapter 1.8
2006-2-24 Page 4 of 6
TDM 2128
UNCLASSIFIED
2.10 DTD removal

Note
Removal of an operational DTD during a HUMS operation may result in the loss of HUMS data.
1 Slide door latch to the left. Door springs open.

2 Press ejector button. Card ejects.
3 Remove card.
4 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.

3 Using the arrow keys, select LOGBK and press the ENT key. Logbook menu is displayed.
4 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 Press the PAGE key to view the next page. Next log book page is displayed.
6 Repeatedly press the PAGE key to continue viewing additional log book values.
7 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:
Note
If using HUMS top-level software P/N 553477-01-01, do not enable the tracker to DAY or
NIGHT mode until both engines have been started. Enabling the tracker prior to engine start
may cause RBT BIT errors to be displayed upon engine start. See paragraph 10.2 of Chapter
1.5 for additional information.

2 Using the down arrow key select TRKR and press the ENT key. Tracker current status is displayed.
3 To change tracker status, press ENT key. Current status will begin flashing.
4 Repeatedly press down arrow key to cycle through available values.
5 Press ENT key to accept value selected.
6 Press CLR key to return to HUMS top level menu page.
2.13 Performing a manual acquisition (Event mark)

If the HUMS configuration parameters have been set up to allow manual vibration acquisition
an acquisition can be initiated manually by pressing the EVNT key on the CDU/DTU.
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:

Chapter 1.8
TDM 2128
UNCLASSIFIED
Note
HUMS must be in a normal operation to perform the following procedure.
1 Press CDU/DTU EVNT key. ACQUISITION IN PROGRESS will be displayed until all data
has been collected.
2 Once ACQUISITION COMPLETE is displayed, press CLR key to return to top level menu.

Chapter 1.8
TDM 2128
UNCLASSIFIED
Chapter 1.9
Operational checkout preliminary set up

References 1
Preliminary requirements 1
Procedure 2
1 Operational checkout preliminary procedures 2
1.1 General 2
1.2 Preliminary setup 2
Requirements after job completion 2
List of tables Page

1 References 1
2 Required persons 1
3 Support equipment 1
4 Required actions 2
References
Table 1. References
Chapter Title
1.10 HUMS system checkout
1.11 HUMS sensor checkout
1.12 HUMS troubleshooting introduction
1.13 HUMS symptom index
Preliminary requirements
Required Conditions: None
Required Persons
Table 2. Required persons

Person Function
1 Perform preliminary set up
Support Equipment
Table 3. Support equipment

Nomenclature Identification no. Qty
Data Transfer Device SDP3BI-384-101 1
Supplies: None
Safety Conditions: Observe all aircraft ground safety procedures. Refer to aircraft maintenance
publications.

Chapter 1.9
2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED
Procedure
1 Operational checkout preliminary procedures

1.1 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
dependent upon the MAU. Ensure the MAU is in proper working order before performing the
HUMS operational checkout.
1.2 Preliminary setup

1 Connect external power to the aircraft in accordance with applicable aircraft maintenance
publication procedure.
2 Close all required circuit breakers on the applicable Power Distribution Panel(s) if not
already closed.
3 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 Insert initialized DTD into CDU/DTU.

5 Apply power to the aircraft.
6 Adjust display intensity for normal viewing.
Requirements after job completion
Required actions
Table 4. Required actions

Title Chapter
HUMS system checkout 1.10
HUMS sensor checkout 1.11

Chapter 1.9
2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
Chapter 1.10
HUMS system checkout

References 1
Procedure 2
List of tables Page

1 References 1
2 Required conditions 1
References
Table 1. References
Chapter Title
1.9 Operational checkout preliminary set up
Required Conditions
Table 2. Required conditions

Title Chapter
Operational Checkout Preliminary Set Up 1.9
Required Persons

Person Function
1 Perform HUMS checkout procedure
Support Equipment: None
Supplies: None
Safety conditions
Observe all ground safety procedures when performing test.

Chapter 1.10
2006-2-24 Page 1 of 2
TDM 2128
UNCLASSIFIED
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.
1A. Wait up to 4 minutes before continuing.
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. If SYS VAL is not displayed, note the BIT failure message and refer to the
HUMS symptom index, Chap 1.13 for troubleshooting.
Required actions
1. If sensors are to be checked, perform procedures of Chapter 1.11.

2. If checkout is complete remove power from MAU, HUMS, and aircraft in accordance with
maintenance publication procedures.

Chapter 1.10
TDM 2128
UNCLASSIFIED
Chapter 1.11
HUMS Sensor checkout

References 1
Procedure 2
List of tables Page

1 References 1
2 Required conditions 1
References
Table 1. References
Chapter Title
1.10 HUMS System Checkout
Required Conditions
Table 2. Required conditions

Title Chapter
Operational Checkout Preliminary Set Up 1.9
HUMS System Checkout 1.10
Required Persons

Person Function
2 Perform HUMS sensor checkout
procedure
Supplies: None
Safety conditions
Observe all aircraft ground safety procedures when performing test.

Chapter 1.11
2006-2-24 Page 1 of 2
TDM 2128
UNCLASSIFIED
Procedure
Note
This procedure verifies operation of the Main Rotor tachometer

(AZ1 and Tail Rotor tachometer (AZ2).
1 Start engines and bring to FPOG condition.

2 On the CDU/DTU. Access the Top Level Menu if not already displayed.
3 Using the arrow keys, select MAINT and press the ENT key. Maintenance menu will be displayed.
4 With cursor next to RT&B press ENT key. RTB acquisition type menu will be displayed.
5 Using the down arrow key, select FPOG then press ENT key.
RESULT: ACQUISITION IN PROGRESS is displayed for up to three minutes then ACQUISITION
COMPLETE is displayed.
6 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.
Required actions
1 Shutdown engines and remove power from MAU, HUMS, and aircraft in accordance with aircraft
maintenance procedures.

Chapter 1.11
TDM 2128
UNCLASSIFIED
Chapter 1.12
HUMS troubleshooting introduction

References 1
1 Troubleshooting introduction 1
List of tables Page

1 References 1
References
Table 1. References
Chapter Title
1.10 HUMS system checkout
1.13 HUMS symptom index
1.14 HUMS fault isolation procedures
1 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.

Chapter 1.12
2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED

Chapter 1.12
2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
Chapter 1.13
HUMS fault symptom index

References 1
1 HUMS fault symptom index 1
List of tables Page

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

SYMPTOM REMEDY OR ISOLATION PROCEDURE
HUMS SYSTEM CHECKOUT SYMPTOMS:
SBIT IN PROGRESS message not displayed Refer to Chapter 1.14, item 1.
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 Refer to Chapter 1.14, item 3.
HUMS SBIT complete.
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. Refer to Chapter 1.14, item 5.
Main menu page 2 not displayed when PAGE Replace CDU/DTU.

key pressed.
BIT menu not displayed when down arrow key

pressed.
IBIT IN PROGRESS not displayed when IBIT

initiated.

Chapter 1.13
2006-2-24 Page 1 of 6
TDM 2128
UNCLASSIFIED

One or more characters fail display Replace CDU/DTU.
checkerboard pattern test.
One or more keys fail key press test.
Top menu not displayed after pressing CLR

key.
SYS VAL not displayed after completion of View BIT LOG and refer to BIT failure message symptoms
IBIT. for failure message displayed.
HUMS SENSOR CHECKOUT SYMPTOMS:

ACQUISITION COMPLETE not displayed after Press CLR key twice to return to HUMS top level menu.
initiating RTB acquisition. View BIT LOG and refer to BIT failure message symptoms
for failure message displayed.
SYS VAL not displayed after completion of View BIT LOG and refer to BIT failure message symptoms
RTB acquisition. for failure message displayed.
BIT FAILURE MESSAGE SYMPTOMS:

DAU FAIL Replace DAU.
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

Chapter 1.13
2006-2-24 Page 2 of 6
TDM 2128
UNCLASSIFIED

DAU FAIL Replace DAU battery. If failure still exists replace DAU.
RTC RAM CHKSUM
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 Reload configuration data. If failure continues replace
EDPU DAU.
CONFIG FAIL
VAU
CDU/DTU FAIL Refer to Chapter 1.14, item 6.
DTU RESPONSE
DTD FAIL Replace DTD. If failure continues replace CDU/DTU.
WRAP
DTD FAIL Missing or damaged files on DTD. Replace DTD with
FORMAT properly initialized DTD.
DTD NOT Normal indication when DTD not installed. If message
PRESENT occurs when DTD is installed replace CDU/DTU.
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

Chapter 1.13
2006-2-24 Page 3 of 6
TDM 2128
UNCLASSIFIED

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
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 Refer to Chapter 1.14, item 7.
ACCEL Axx FAIL Refer to Chapter 1.14, item 8.

BIAS (see note a)
ACCEL Axx FAIL Check accelerometer mounting and tighten as necessary.
SATURATION (see note a) If failure still exists, replace accelerometer then check
wiring.

Chapter 1.13
TDM 2128
UNCLASSIFIED

TRACKER FAIL Refer to Chapter 1.14, item 11.
DAU FAIL Replace DAU. Note: If using HUMS top-level software

AATPS LAMP SW P/N 553477-01-01, and the RBT is enabled before the
DAU FAIL engines are started, PBIT may cause AATPS 12V ON,
AATPS 24V ON, and AATPS LAMP SW BIT errors to be
AATPS 24V ON
displayed upon engine start. If these faults are detected
DAU FAIL due to enabling of the tracker before engines are started,
AATPS 24V OFF the fault should be cleared after mission has been
DAU FAIL accomplished and engines have been shut down, with no
AATPS 12V ON further maintenance action required. To determine which
top-level software P/N is being used, inspect the label on
DAU FAIL
the front of the DAU.
AATPS 12V OFF
CDU/DTU FAIL Refer to Chapter 1.14, item 6.
CDU RESPONSE
CDU/DTU FAIL Replace CDU/DTU
CDU BIT
LOAD FACTOR SENSOR FAIL Refer to Chapter 1.14, item 12.
RTC BATTERY Replace DAU battery.
VOLTAGE LOW
Note a.
XX corresponds to accelerometer number that has failed.

Chapter 1.13
TDM 2128
UNCLASSIFIED

Chapter 1.13
2006-2-24 Page 6 of 6
TDM 2128
UNCLASSIFIED
Chapter 1.14
HUMS fault isolation procedures

References 1
Procedure 2
1 Troubleshooting Procedures 2
List of tables Page

1 References 1
3 Support equipment 1
References
Table 1. References
Chapter Title
1.8 Operating procedures
1.13 Symptom index
1.15 Removal and installation procedures
Required Persons

Person Function
1 Perform troubleshooting procedure
Support Equipment
Table 3. Support equipment
Multimeter - 1
Safety conditions
Observe all standard safety procedures when troubleshooting.

Chapter 1.14
2005-1-28 Page 1 of 8
TDM 2128
UNCLASSIFIED
Procedure
1 Troubleshooting procedures
ISOLATION PROCEDURE REMEDY

Item 1. SBIT IN PROGRESS not displayed at HUMS power up
Step 1. Wait one minute. Is COMM FAIL message YES Replace DAU then proceed to step 2.
displayed?
NO Proceed to step 3.
Step 2. Does problem still exist? YES Troubleshoot aircraft +28 Vdc power
wiring to DAU and RS-422 wiring
between DAU and CDU/DTU.
NO End of test.
Step 3. Is display completely blank? YES Proceed to step 4.
Step 4. Look closely at display. In bright light, display YES Proceed to step 5.
may only appear to be blank if lighting is set to NVIS
level. Is display actually blank? NO End of test.
Step 5. Check HUMS circuit breaker(s). Are HUMS YES Replace CDU/DTU then proceed to
circuit breaker(s) closed? step 6.
NO Close HUMS circuit breaker(s) then

proceed to step 6.
Step 6. Does problem still exist? YES Troubleshoot aircraft +28 Vdc power
wiring to CDU/DTU.
NO End of test.
Step 7. Is display garbled? YES Replace CDU/DTU. If problem still
exists, replace DAU.
NO Replace DAU.
End of test

Item 2. Display intensity incorrect or display corrupted or garbled
Step 1. Is display intensity correct? YES Proceed to step 2.
Step 2. Is HUMS top level menu page displayed but YES Replace CDU/DTU.
corrupted or garbled?
NO Replace DAU. If problem still exists
replace CDU/DTU.

Chapter 1.14
2005-1-28 Page 2 of 8
TDM 2128
UNCLASSIFIED
Step 3. Adjust pedestal lighting power. Did display YES Adjust pedestal lighting to desired level.
intensity change? End of test.
Step 4. Adjust pedestal lighting power while observing YES Replace DAU then proceed to step 5.
CDU/DTU pushbutton switches. Did pushbutton
nomenclatures vary in brightness? NO Troubleshoot pedestal lighting power
system.
Step 5. Does problem still exist? YES Troubleshoot aircraft +5 Vdc pedestal
lighting power wiring to DAU.
NO End of test.
End of test

Item 3. Top level menu not displayed after HUMS SBIT complete.
Step 1. Is DTD NOT INSTALLED message YES Proceed to step 2.
displayed?
Step 2. Remove and reinsert DTD. Did message YES Proceed to step 3.
clear?
NO Replace CDU/DTU.
Step 3. Is HUMS top level menu now displayed? YES End of test.
Step 4. Is CONFIGURATION DTD INSTALLED YES Replace DTD with properly initialized
message or INVALID DTD INSTALLED message DTD.
displayed?
Step 5. Is there a fileid FILE XXX% FULL message YES Press CLR key for each fileid message
displayed? displayed then continue with checkout
procedure.
Step 6. Is A/C ID UNAVAILABLE message YES Proceed to step 7.
displayed?
Step 7. Check MAU system and verify MAU is YES Replace DAU then proceed to step 8.
working properly. Is MAU working properly?
NO Troubleshoot MAU.
Step 8. Does problem still exist? YES Troubleshoot aircraft wiring from MAU
to DAU.
NO End of test.

Chapter 1.14
2005-1-28 Page 3 of 8
TDM 2128
UNCLASSIFIED
Step 9. Is A/C ID MISMATCH message displayed? YES Proceed to step 10.
NO Replace DAU.
Step 10. Check MAU system and verify correct YES Proceed to step 11.
aircraft ID has been entered or is displayed. Is aircraft
ID correct? NO Enter correct aircraft information into
MAU system.
Step 11. Is HUMS operational checkout procedure YES Note
being performed to confirm that a previous failure has
been remedied by replacement of DAU? 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.
This is normal for a new DAU being
installed.
2. Perform initialization upload into

new DAU.
NO Replace DAU then proceed to step 12.

Step 12. Does problem still exist? YES Check aircraft wiring from MAU to DAU.
NO End of test.
End of test

Item 4. SYS VAL not displayed after SBIT.
Step 1. Has a HUMS LRU/LRI been previously YES Proceed to step 2.
replaced?
Step 2. Was the BIT LOG cleared after replacement? YES Proceed to step 3.
NO Clear HUMS BIT LOG then repeat

checkout procedure.
Step 3. Has HUMS been reinitialized? YES Proceed to step 4.
NO Perform initialization upload procedure

then repeat checkout procedure.

Chapter 1.14
2005-1-28 Page 4 of 8
TDM 2128
UNCLASSIFIED
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

Item 5. Some or all pushbutton nomenclatures not lit.
Step 1. Are any pushbuttons lit? YES Replace CDU/DTU.
Step 2. Check pedestal lighting power input to YES Replace CDU/DTU.
CDU/DTU. Is voltage present?
NO Troubleshoot aircraft +5 Vdc pedestal
lighting power wiring to CDU/DTU.
End of test

Item 6. CDU/DTU FAIL DTU RESPONSE message
Step 1. Replace CDU/DTU. Does problem still exist? YES Replace DAU then proceed to step 2.
NO End of test.
Step 2. Does problem still exist. YES Troubleshoot aircraft wiring between
DAU and CDU/DTU.
NO End of test.
End of test

Item 7. TACH AZ3 FAIL
Step 1. Replace transmission tachometer AZ3. Does YES Check wiring between tachometer AZ3
problem still exist? and DAU then proceed to step 2.
Step 2. Does problem still exist? YES Replace DAU.
NO End of test.
End of test

Chapter 1.14
2005-1-28 Page 5 of 8
TDM 2128
UNCLASSIFIED

Item 8. ACCEL Axx FAIL BIAS
Step 1. Replace associated accelerometer. Does YES Check wiring between failing
problem still exist? accelerometer and DAU then proceed
to step 2.
NO End of test.
End of test

Step 1. Replace main rotor tachometer AZ1. Does YES Check wiring between tachometer AZ1
NO End of test.
End of test

Step 1. Replace tail rotor tachometer AZ2. Does YES Check wiring between tachometer AZ2
NO End of test.
End of test

Item 11. TRACKER FAIL
Step 1. Was Rotor Blade Tracker installed when YES Replace RBT then proceed to step 3.
failure occurred?
Step 2. Go to HUMS top level menu screen then YES Check wiring between Rotor Blade
press down arrow key to select TRKR. Press ENTER Tracker and DAU then proceed to step
key. Is TRACKER OFF displayed? 4.
NO Press ENTER key. Press down arrow

key until OFF is selected then press
ENTER key. Clear BIT LOG then repeat
sensor checkout procedure.

Chapter 1.14
2005-1-28 Page 6 of 8
TDM 2128
UNCLASSIFIED
Step 3. Does problem still exist? YES Check wiring between Rotor Blade
Tracker and DAU then proceed to step
4.
NO End of test.
NO End of test.
End of test

Item 12. LOAD FACTOR SENSOR FAIL
Step 1. Check power to load factor sensor. Is power YES Proceed to step 2.
present?
NO Troubleshoot power source to load
factor sensor.
Step 2. Replace load factor sensor. Does problem YES Check wiring between load factor
still exist? sensor and DAU then proceed to step 3.
NO End of test.
NO End of test.
End of test
Required actions

Title Chapter
Removal and installation procedures 1.15

Chapter 1.14
2005-1-28 Page 7 of 8
TDM 2128
UNCLASSIFIED

Chapter 1.14
2005-1-28 Page 8 of 8
TDM 2128
UNCLASSIFIED
Chapter 1.15
Removal and installation

References 1
Procedure 2
1 Removal and Installation 2
1.1 Data acquisition unit 2
1.1.1 Removal 2
1.1.2 Installation 2
1.2 DAU battery 2
1.2.1 Removal 2
1.3 Cockpit display unit/data transfer unit 3
1.3.1 Removal 3
List of tables Page

1 References 1
3 Spares 2
References
Table 1. References
Chapter Title
1.8 Operating Procedures
Required Persons

Person Function
1 Perform removal/installation procedure
Supplies: None

Chapter 1.15
2005-1-28 Page 1 of 4
TDM 2128
UNCLASSIFIED
Spares
Table 3. Spares
Data Acquisition Unit 176990-01-01 1
Lithium Battery 3B1065-XB 1
Cockpit Display Unit/Data Transfer Unit 180305-001 1
Safety Conditions: None
Procedure
1 Removal and installation

1.1 Data acquisition unit
1.1.1 Removal
1 Ensure all electrical power is off.
2 Gain access to Data Acquisition Unit.
3 Disconnect aircraft electrical connectors from DAU connectors J1, J2, and J3.
4 Loosen two thumb nuts and remove two hold-down collars positioned over two hold-
down hooks on front of the unit.
5 Grasp handle and pull the DAU forward to clear wedges at rear of mounting base.
6 Support the DAU and lift out of mounting base.
1.1.2 Installation
1 Place the DAU on mounting base and slide back to align wedges on mounting base
with wedges on rear of the DAU.
2 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.
3 Connect aircraft electrical connectors to DAU connectors J1, J2, and J3.
4 Close/reinstall all access panels/equipment removed or opened.
5 Initialize DAU in accordance with Chap 1.8.
6 Clear BIT log in accordance with Chap 1.8.
7 Enter date and time in accordance with Chap 1.8.
1.2 DAU battery

1.2.1 Removal
1 Gain access to DAU.
2 Locate the battery receptacle on the rear panel of the DAU.
3 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.
4 Using a slotted screwdriver, rotate the battery holder cover 90 degrees counter-
clockwise to release the cover.

Chapter 1.15
2005-1-28 Page 2 of 4
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 Insert a new lithium battery into the battery holder with the (-) end entering first.
2 Place the metal face of the battery holder cover against the (+) end of the lithium
battery.
3 Align the tabs on the battery holder cover with the slots in the battery holder.
4 Push the cover/battery into the holder and rotate the battery holder cover clockwise to
the end of rotation.
5 Place the Battery Access Cover over the battery holder.
6 Engage the two mounting screws for the Battery Access Cover using a Phillips
screwdriver.
7 Re-fit any equipment or panels previously removed.
8 Enter date and time as described in Chap 1.8.
1.3 Cockpit display Unit/Data transfer unit

1.3.1 Removal
1 Ensure all electrical power is off.
2 Loosen the four fasteners on the face of the CDU/DTU.
3 Pull the CDU/DTU out from mounting location sufficient to access electrical connector
and disconnect.
4 Remove the CDU/DTU.
1.3.2 Installation
1 Position the CDU/DTU in front of mounting location and connect electrical connector.
2 Install the CDU/DTU into its mounting location and secure the four fasteners.
Required actions

Title Chapter
Operating Procedures 1.8
HUMS System Checkout 1.10

Chapter 1.15
2005-1-28 Page 3 of 4
TDM 2128
UNCLASSIFIED

Chapter 1.15
2005-1-28 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.16
Servicing

References 1
1 Servicing 1
1.1 Cleaning 1
1.2 Inspection 1
1.3 Scheduled maintenance 1
List of tables Page

1 References 1
References
Table 1. References
Chapter Title
1.17 Cleaning
1 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 Inspection
There are no inspection requirements for the HUMS on-board system LRUs.
1.3 Scheduled maintenance
There are no scheduled maintenance requirements for the HUMS on-board system LRUs.

Chapter 1.16
2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED

Chapter 1.16
2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
Chapter 1.17
Cleaning

References 1
Procedure 2
1 Cleaning 2
List of tables Page

1 References 1
3 Supplies 1
References
Table 1. References
Chapter Title
Required Persons

Person Function
1 Perform cleaning procedure
Supplies
Table 3. Supplies
Detergent, GP Liquid MIL-D-16791 As required
Cloth, Lint-free - As needed
Alcohol, Isopropyl TT-I-735 As required
Glass cleaner MS-260 (FSC 18598) As required

Chapter 1.17
2005-1-28 Page 1 of 4
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
1 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.
4. 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.

Chapter 1.17
2005-1-28 Page 2 of 4
TDM 2128
UNCLASSIFIED
Required actions

Title Chapter
HUMS Operational Checkout 1.10

Chapter 1.17
2005-1-28 Page 3 of 4
TDM 2128
UNCLASSIFIED

Chapter 1.17
2005-1-28 Page 4 of 4
TDM 2128
UNCLASSIFIED
Chapter 1.18
Blade Tracking Tape Installation

Procedure 2
1 Blade Tracking Tape Installation 2
List of tables Page

2 Supplies 1
Required Persons

Person Function
1 Install tape
Supplies
Table 2. Supplies
Blade Tape 10605000 As required
Cleaning Supplies To be supplied by Agusta As required
Safety Conditions: To be supplied by Agusta.

Chapter 1.18
2005-1-28 Page 1 of 2
TDM 2128
UNCLASSIFIED
Procedure
1 Blade Tape Installation
1 For Night Tracking the tracker uses an integral light to illuminate retro-reflective tape targets on the
underside of the rotor.
2. Before night tracking it is necessary to prepare the blades by applying a single strip of reflective
tape to the trailing edge of each blade in the span section scanned by the tracker.
3. The scanned span section is identified as having the lower blade black paint finish that runs from
leading edge to trailing edge. This can be found just adjacent to the outer tabs.
4. Blade surface should be clean and free from grease to allow the tape to adhere properly. The
tape should be applied carefully to ensure that it abuts accurately along the trailing edge of the
blade. If the tape is not properly aligned, lead and lag offsets will be introduced into the
measurement.
5. The tape should be smoothed down to expel air bubbles with a clean grease free cloth. Grease
deposits should be removed from the tape as they impair the tape’s reflective qualities.
6. The presence of the tape does not interfere with the tracker operation in day mode.
Required actions: None

Chapter 1.18
2005-1-28 Page 2 of 2
TDM 2128
UNCLASSIFIED
CHAPTER 2
AIRCREW FLIGHT INFORMATION

1 General 1
2 Checklist information 1
2.1 Preflight procedures 1
2.1.1 With power Off 1
2.1.2 Before Rotors Turning 1
2.2 Inflight procedures 2
2.3 Postflight procedures 2
3 Operating procedures 2
3.1 Data entry methods and guidelines 2
3.2 Procedures 2
3.2.1 Configuring rotor blade tracker 2
3.2.2 Setting system date/time 2
3.2.3 DTD insertion 2
3.2.4 DTD removal 2
3.2.5 Direct parameter display viewing 2
3.2.6 Checking DTD status 3
3.2.7 Performing rotor track and balance acquisition 3
3.2.8 Performing engine power assurance 3
1 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 Checklist information
2.1 Preflight procedures
2.1.1 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 on the ground station for the particular HUMS
operation to be performed.
If the HUMS operation will be a rotor tuning flight, and track and balance data is to be acquired,
then the aircrew should ensure that a rotor blade tracker has been fitted to the aircraft. Note:
Rotor balance tuning can be performed without a rotor blade tracker fitted.
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.

Chapter 2
TDM 2128
UNCLASSIFIED
If the correct time and date have not been received from the MAU, the aircrew should enter a
time and date into HUMS.
Note
If using HUMS top-level software P/N 553477-01-01, do not enable the tracker to DAY or
NIGHT mode until both engines have been started. Enabling the tracker prior to engine start
may cause RBT BIT errors to be detected upon engine start. See paragraph 10.2 of Chapter
1.5 for additional information.
If the HUMS operation will be a rotor tuning flight (track and balance) then the Rotor Blade
Tracker should be configured for either day or night operation as applicable. If a 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 Operating procedures
3.1 Data entry methods and guidelines
Refer to Chapter 1.8 for data entry methods and guidelines.
3.2 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.

Chapter 2
TDM 2128
UNCLASSIFIED
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, but rotor blade track data will not be acquired.
1A. Ensure aircraft is in desired condition to perform acquisition.

1 On the CDU/DTU, access the Top Level Menu
2 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
1A. Ensure aircraft is in proper configuration for EPA acquisition.

2 Using the arrow keys, select MAINT and press the ENT key. Maintenance menu is
displayed.
3 With cursor next to EPA press ENT key. EPA menu will be displayed.
4 Using the arrow keys, select the desired engine.
5 Once cursor is next to desired engine, press ENT key to initiate the acquisition.
ACQUISITION IN PROGRESS will be displayed until all data has been collected.
6 Once the calculated NG or ITT margins are displayed, press CLR key to return to EPA
menu.

Chapter 2
TDM 2128
UNCLASSIFIED

Chapter 2
2006-2-24 Page 4 of 4
TDM 2128
UNCLASSIFIED
CHAPTER 3
ILLUSTRATED PARTS CATALOGUE

1 Introduction 1
1.1 Identification 1
1.2 Parts which are listed 1
2 Maintenance parts list 1
2.1 Figure and index no. column 1
2.2 Part number column 2
2.3 Smiths part numbers 2
2.4 Vendor part numbers 2
2.5 Similar assemblies 2
2.6 Nomenclature column 2
2.6.1 Indentation 2
2.6.2 SCD notation 2
2.7 Usage code column 2
2.8 Units per assembly column 2
3 Maintenance parts list 3

1 Health and usage monitoring system 3
1 Introduction
1.1 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.
2 Maintenance parts list

2.1 Figure and index no. column
Each part is index–numbered 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.

Chapter 3
2005-1-28 Page 1 of 4
TDM 2128
UNCLASSIFIED
2.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.
2.3 Smiths part numbers
The Smiths Aerospace part number assigned to a part is the drawing number of that part with a
suffixed dash number beginning with "01". A repairable assembly may have a "double dash"
part number consisting of the drawing number and two suffixed dash numbers. Repairable
assemblies having the same basic (drawing) number and first suffixed number are
interchangeable. A difference in the second suffixed number denotes noninterchangeable
internal part differences within the assembly.
2.4 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.
2.5 Similar assemblies
When similar assemblies exist that contain many identical parts, the assemblies are combined.
2.6 Nomenclature column
The drawing title is listed in this column along with parenthetical notations which give additional
information required to identify the part.
2.6.1 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
...Sub–subassemblies
...Attaching parts for detail parts of the subassemblies and the sub–subassemblies
2.6.2 SCD notation

When a Smiths Aerospace part number has been assigned to a vendor's part number, the
parenthetical notation "(SCD…..)" follows the description.
2.7 Usage code column
This column contains a code to indicate the applicability to aircraft type.
2.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.

Chapter 3
2005-1-28 Page 2 of 4
TDM 2128
UNCLASSIFIED
3 Maintenance parts list
J1
J2
3
EVNT
PA
GE
ENT
CLR
Figure 1. Health and usage monitoring system

Chapter 3
2005-1-28 Page 3 of 4
TDM 2128
UNCLASSIFIED
NOMENCLATURE UNITS
FIG AND USAGE
PART NUMBER PER
INDEX CODE
1234567 ASSY
01
-000 200111-01-01 HEALTH AND USAGE MONITORING REF
SYSTEM
-001 176990-03-01 . **ESD** DATA ACQUISITION UNIT 1
-002 3B1065-XB ..Battery, Lithium, AA (62713) 1
(SCD 174356-07)
-003 177035-01 .MOUNTING TRAY, ELECTRICAL 1
EQUIPMENT
-004 180305-001 . **ESD** COCKPIT DISPLAY 1
UNIT/DATA TRANSFER UNIT

Chapter 3
2005-1-28 Page 4 of 4

139 Hums

Uploaded by

Copyright:

Available Formats

139 Hums

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

139 Hums

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What components make up the Health and Usage Monitoring System (HUMS)?

What components make up the Health and Usage Monitoring System (HUMS)?

TDM 2128

HEALTH AND USAGE MONITORING SYSTEM (HUMS)

DESTINATION CONTROL NOTICE

PROPRIETARY DATA – IN CONFIDENCE

Agusta 2ND EDITION 2005-1-28

SMITHS AEROSPACE LLC,

INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.

Dates of issue for original and changed pages are:

Original .... 0 ....28 January 2005

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 116 CONSISTING OF THE FOLLOWING:

Document Page Change Document Page Change

Title page 1 1 Chapter 1.13 1 thru 3 0

Effectivity: All 39-A-31-30-00-LOAP-001A-A

Table of contents Chapter

INTRODUCTION .......... ...................................... ..............................................................................................1

Effectivity: All 39-A-31-30-00-00A-001A-A

This page intentionally left blank.

Effectivity: All 39-A-31-30-00-00A-001A-A

Effectivity: All 39-A-31-30-01-00A-001A-A

This page intentionally left blank.

Effectivity: All 39-A-31-30-01-00A-001A-A

1.1 HUMS INTRODUCTION .............................. ..............................................................................................1

Effectivity: All 39-A-31-30-02-00A-001A-A

9 Engine power assurance (EPA) .....................................................................................................13

Effectivity: All 39-A-31-30-02-00A-001A-A

2.12 Configuring rotor blade tracker.................................................................................................5

Effectivity: All 39-A-31-30-02-00A-001A-A

This page intentionally left blank.

Effectivity: All 39-A-31-30-02-00A-001A-A

Table of contents Page

List of figures Page

HUMS Components Number Used Part Number

Cockpit Display Unit/Data Transfer Unit 1 180305-001

Effectivity: All 39-A-31-30-00-00A-011A-A

1.3 List of dedicated sensors

Sensor Number Used Part Number or Type

1.4 Associated equipment

Item Number Used Part Number

Effectivity: All 39-A-31-30-00-00A-011A-A

Figure 1. HUMS LRUs

Effectivity: All 39-A-31-30-00-00A-011A-A

This page intentionally left blank.

Effectivity: All 39-A-31-30-00-00A-011A-A

Table of contents Page

List of figures Page

1 Data acquisition unit

The DAU is comprised of three main functional sub-assemblies:

Effectivity: All 39-A-31-30-00-00A-042A-A

Figure 1. Data acquisition unit identification view

Effectivity: All 39-A-31-30-00-00A-042A-A

Table of contents Page

List of figures Page

List of tables Page

1 Cockpit display unit/data transfer unit

2 Controls and displays