阅读说明：本技术 用于移动设备实现的旋翼跟踪和平衡的系统和方法 (System and method for mobile device implemented rotor tracking and balancing ) 是由 保罗·迈克尔·邓宁 史蒂文·博尼特 尼古拉斯·科宁利 史蒂芬·P·杰克逊 安德鲁·约翰·詹姆 于 2021-06-22 设计创作，主要内容包括：一种可以被配置为在飞行器的驾驶舱或机舱内使用的手持移动设备。手持移动设备可以包括显示器和存储器,该存储器包括被配置为利用显示器的应用。手持移动设备还可以包括联接到存储器的处理器。经由处理器应用可以被配置为接收特定于飞行器的配置数据。应用还可从跟踪器模块接收对应于叶片高度和位置的输入数据。应用还可以从加速度计模块接收机身振动数据。应用可以进一步计算关于跟踪和平衡的建议。应用还可以进一步经由显示器输出跟踪和平衡建议。(A handheld mobile device that may be configured for use within a cockpit or cabin of an aircraft. A handheld mobile device may include a display and a memory including an application configured to utilize the display. The handheld mobile device may also include a processor coupled to the memory. The application may be configured via the processor to receive aircraft-specific configuration data. The application may also receive input data from the tracker module corresponding to blade height and position. The application may also receive body vibration data from the accelerometer module. The application may further calculate recommendations for tracking and balancing. The application may further output tracking and balancing recommendations via a display.)

1. A handheld mobile device configured for use within a cockpit or cabin of an aircraft, comprising:

a display;

a memory comprising an application configured to utilize the display;

a processor coupled to the memory, wherein the application is configured to, via the processor:

receiving aircraft-specific configuration data;

receiving input data corresponding to blade height and position from a tracker module;

receiving fuselage vibration data from an accelerometer module;

computing recommendations regarding tracking and balancing; and is

Outputting the tracking and balancing recommendation via the display.

2. An aircraft, characterized in that it comprises:

a cockpit, a cabin, or both; and

the handheld mobile device of claim 1, wherein the handheld mobile device is secured to the cockpit or a portion of the nacelle.

3. The aircraft of claim 2, wherein the handheld mobile device is secured to the cockpit or a transparent exterior portion of the cabin.

4. The handheld mobile device of claim 1, wherein:

the input data is configured to be wirelessly received from the tracker module; and is

The tracker module is a physical device that is fixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device.

5. The handheld mobile device of claim 1, wherein:

the body vibration data is configured to be wirelessly received from the accelerometer module; and is

The accelerometer module is a physical device affixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device.

6. The handheld mobile device of claim 1, wherein:

the input data is configured to be wirelessly received from the tracker module;

the tracker module is a physical device affixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device;

the body vibration data is configured to be wirelessly received from the accelerometer module;

the accelerometer module is a physical device affixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device; and is

The tracker module is physically separate from the accelerometer module.

7. The handheld mobile device of claim 1, wherein the application further comprises a blade identification component configured to process blade tracking data using image recognition and output the result to an RTB (rotor tracking and balance) solver.

8. The handheld mobile device of claim 7, wherein the RTB solver is configured to:

analyzing the processed blade tracking data;

comparing the processed blade tracking data to the configuration data; and is

A tracking and balancing recommendation is calculated based on the comparison.

9. A system configured for use within a cockpit or cabin of an aircraft, the system comprising:

a handheld mobile device, the handheld mobile device comprising:

a display;

a memory, the memory including an application; and

a processor coupled to the memory, wherein the processor is configured to execute the application to:

receiving aircraft-specific configuration data;

receiving input data corresponding to blade height and position from a tracker module;

receiving fuselage vibration data from an accelerometer module;

computing recommendations regarding tracking and balancing; and is

Outputting the tracking and balancing suggestions via the display;

a tracker module comprising a camera, the tracker module configured to:

generating input data corresponding to blade height and position with the camera; and is

Outputting the input data to the handheld mobile device;

the accelerometer module comprising an accelerometer and configured to:

generating body vibration data with the accelerometer; and is

Outputting the body vibration data to the handheld mobile device; and

a configuration service configured to output the aircraft-specific configuration data to the handheld mobile device.

10. The system of claim 9, wherein the handheld mobile device is secured to the cockpit or a portion of the nacelle.

Technical Field

The present application relates generally to aircraft maintenance and, more particularly, to calibrating rotor tracking and balancing.

Background

Helicopter rotor blades travel around the hub and can change their pitch angle to affect the helicopter's flight direction, speed, and lift. Under ideal conditions, when identical blades are installed to specification and based on a centralized set/configuration, the rotor blade tips all "track" through exactly the same spatial point around the hub at a given point in rotation. Unbalanced blades can transmit vibrations to the rotor head, transmission, fuselage and other helicopter components. Excessive vibration can lead to excessive wear and failure of components, resulting in increased maintenance costs and increased helicopter downtime. Therefore, regular maintenance is required to check and correct rotor tracking and balancing.

Disclosure of Invention

A handheld mobile device configured for use within a cockpit or cabin of an aircraft and comprising: a display; a memory comprising an application configured to utilize a display; and a processor coupled to the memory. The processor is configured to execute an application to receive aircraft-specific configuration data. The application also receives input data from the tracker module corresponding to the blade height and position. The application further receives body vibration data from the accelerometer module. The application calculates recommendations on tracking and balancing. The application outputs tracking and balancing recommendations via the display.

In another embodiment, a system configured for use within a cockpit or cabin of an aircraft, the system comprising: a handheld mobile device; a tracker module comprising a camera; an accelerometer module comprising an accelerometer; and configuring the service. The handheld mobile device includes: a display; a memory comprising an application; and a processor coupled to the memory. The processor is configured to execute an application to: receiving aircraft-specific configuration data; receiving input data corresponding to blade height and position from a tracker module; receiving fuselage vibration data from an accelerometer module; computing recommendations regarding tracking and balancing; and outputting the tracking and balancing recommendation via the display. The tracker module is configured to generate input data corresponding to blade height and position with the camera and output blade tracking data to the handheld mobile device. The accelerometer module is configured to generate body vibration data with the accelerometer and output the body vibration data to the handheld mobile device. The configuration service is configured to output aircraft-specific configuration data to the handheld mobile device.

In yet another embodiment, a method of using a handheld mobile device in an aircraft cockpit or cabin, the method comprising: accessing an application on a handheld mobile device; downloading, with the application, aircraft-specific configuration data; starting data acquisition of a state; synchronously vibrating and collecting blades; acquiring blade and vibration data; storing the state vibration and blade data; calculating and storing the vibration result of the state; calculating tracking and balancing recommendations; and displaying the vibration results, tracking recommendations, and balancing recommendations on the handheld mobile device.

These and additional features provided by the embodiments described herein will be more fully understood in view of the following detailed description in conjunction with the accompanying drawings.

Drawings

The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the subject matter defined by the claims. The following detailed description of exemplary embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals, and in which:

fig. 1 is a side view of a helicopter featuring a handheld mobile device, tracker module, and accelerometer module for implementing various systems and processes in accordance with one or more embodiments shown and described herein;

FIG. 2 is a diagram schematically illustrating an exemplary system for implementing various systems and processes utilizing a handheld mobile device, a tracker module, and an accelerometer module, in accordance with one or more embodiments shown and described herein;

FIG. 3 is a side view of a helicopter featuring a handheld mobile device and tracker module for implementing various systems and processes in accordance with one or more embodiments shown and described herein;

FIG. 4 is a diagram schematically illustrating an exemplary system for implementing various systems and processes utilizing a handheld mobile device and a tracker module, in accordance with one or more embodiments shown and described herein;

FIG. 5 is a side view of a helicopter featuring a handheld mobile device and an accelerometer module for implementing various systems and processes in accordance with one or more embodiments shown and described herein;

FIG. 6 is a diagram schematically illustrating an exemplary system for implementing various systems and processes utilizing a handheld mobile device and an accelerometer module, in accordance with one or more embodiments shown and described herein;

FIG. 7 is a side view of a helicopter featuring a handheld mobile device for implementing various systems and processes in accordance with one or more embodiments shown and described herein;

FIG. 8 is a diagram schematically illustrating an exemplary system for implementing various systems and processes with a handheld mobile device in accordance with one or more embodiments shown and described herein;

FIG. 9 shows a flow diagram for determining tracking and balancing recommendations on a handheld mobile device in accordance with one or more embodiments described and illustrated herein; and

fig. 10 is a block diagram illustrating computing hardware used in one or more devices for implementing various systems and processes in accordance with one or more embodiments shown and described herein.

Detailed Description

Embodiments of the present disclosure relate to rotor tracking and balancing implemented by mobile devices in an aircraft (also interchangeably referred to herein as a rotorcraft) that utilizes one or more rotors. More specifically, the aircraft-specific configuration data may be compared to other data obtained by observing the operation of the aircraft. This may include, for example, fuselage vibration data and/or input data corresponding to blade height and position. This comparison may then be used to calculate and provide rotor tracking and balancing recommendations, which may result in reduced rotor induced vibrations. Embodiments employing tracker modules and accelerometer modules that are physically separate from and in wireless communication with a mobile device may provide significant reduction in installation time and improved user operation compared to systems in which the tracker modules and accelerometer modules are hardwired. Various embodiments of mobile device implemented rotor tracking and balancing are described in detail below.

Turning to fig. 1, an aircraft 100 is depicted with occupants 102 present in the cockpit and/or cabin. In this embodiment, aircraft 100 is a helicopter, but any type of aircraft that uses rotors and/or rotating blades for maneuverability may be utilized. In this embodiment, the occupant 102 may be a pilot, co-pilot, or any other person capable of flying the aircraft 100. In other embodiments, the occupant 102 may be a passenger, a flight crew member, a technician, or any other person capable of using the handheld mobile device 104 as described herein. The handheld mobile device 104 may be any suitable type of portable electronic device that processes or stores data and that is capable of being used while worn or held in one or both hands of an operator. In some embodiments, handheld mobile device 104 may refer to the type of device rather than actually being handheld by a user, so it need not be held by a user but may be mounted or otherwise affixed/attached to any suitable portion of an aircraft. Non-limiting examples of handheld mobile devices 104 may include laptops, tablets, smart phones, servers, client devices, wearable devices, and the like. As described below, handheld mobile device 104 includes a display on which rotor trajectory and balance recommendations may be displayed. The aircraft 100 may also have one or more rotors 107 that rotate one or more blades 106 to lift the aircraft 100. This ensures that the aircraft 100 can be lifted off, while also generating sufficient thrust to overcome the aerodynamic drag encountered in forward flight.

A portion of a maintenance procedure for an aircraft utilizing rotors 107 and blades 106 may include Rotor Tracking and Balancing (RTB). Rotor tracking may involve adjustment of the blade tip paths so that they rotate in the same plane of rotation. Rotor tracking may be implemented by any suitable device capable of tracking rotor blades 106. In this embodiment, one or more tracker modules 108 may be used to capture one or more tracked views 110 of the blade 106. The tracker module 108 may be a dedicated hardware device utilizing wireless and/or wired connections. For example, the input data may be configured to be wirelessly received from one or more cameras of the tracker module 108, where the tracker module 108 is a physical device fixed to a location within the cockpit that is physically separate from the handheld mobile device.

The tracker module 108 may be attached to or adjacent to any transparent surface of the cockpit (e.g., the windshield) for clear unobstructed viewing of the blades 106. In some embodiments, the tracker may be mounted (temporarily or permanently) with the blade view so that the tracker mount may be mounted on the aircraft exterior and the tracker may be secured (via bolts or by any other suitable fastener type) when performing RTB. The tracker module 108 may track blade height and position with a camera. The blade "pulse" can be used to track individual blades, where one blade can be identified as a reference blade by identifying differences in blade pulses. The reference blade pulses may also be used to determine the rotational speed. In some embodiments, tracker module 108 may be secured to any suitable surface of aircraft 100 by any suitable means (e.g., using mounting devices, via bolts or other fasteners, adhesives, etc.). In some embodiments, tracker module 108 may be fixed or otherwise reside on any suitable surface inside or outside of the aircraft. Any suitable positioning, perspective, and/or perspective for tracking the view 110 may be utilized. The tracker module 108 may include or otherwise utilize one or more cameras and/or other devices capable of tracking the blade 106. In other embodiments, at least a portion of tracker module 108 may include software or other components within another device. The tracker module 108 may include a communication device to communicate blade tracking data (wireless or wired) to the portable device using any suitable communication mechanism discussed herein. Rotor balancing may involve the rotational frequency of rotor 107. Rotor-induced vibrations may be measured for rotor balancing by one or more accelerometer modules 112 using wireless and/or wired connections. The accelerometer module 112 may include or otherwise utilize one or more accelerometers and/or other devices capable of tracking movements/vibrations of the fuselage of the aircraft 100. Accelerometer module 112 (which may also be referred to as a device accelerometer in some embodiments) may be an accelerator device secured to a portion of the fuselage to detect the frequency and/or intensity of vibrations of the fuselage. Accelerometer module 112 may be secured to any suitable surface of aircraft 100 in any suitable manner (e.g., via mounting devices, by bolts and/or other fasteners, adhesives, etc.). For example, the body vibration data may be wirelessly received from the accelerometer module 112, where the accelerometer module 112 is a physical device affixed to a location within the cockpit that is physically separate from the handheld mobile device 104. In this embodiment, the tracker module 108 may be physically separate from the accelerometer module 112. In other embodiments, at least a portion of the accelerometer module 112 may comprise software or a component within another device.

Turning to fig. 2, a schematic diagram of a system utilizing a handheld mobile device, a tracker module, and an accelerometer module that may be used in the system of fig. 1 is depicted. The occupant 102 may utilize the handheld mobile device 104 to request RTB data relating to the occupant 102 and the aircraft 100 in which the handheld mobile device 104 is located. As described above, the tracker module 108 may be secured to the cockpit windshield and utilize a camera to track blade height and position. In some embodiments, the input data may include camera data/images. The blade "pulse" may be used to track an individual blade, where one blade may be designated as a reference blade. The blade pulses may also be used to determine the rotational speed. Tracker module 108 can wirelessly transmit tracking blade height and position data to RTB solver 122 within RTB application 114 resident on handheld mobile device 104. In some embodiments, one or more tachometer modules may be used to track the blades, instead of tracking module 108 or in combination with tracking module 108. The tachometer module may be located on the aircraft or at any suitable location within the aircraft (e.g., on the rotor mast) to directly measure rotational speed. The tachometer module may be a wireless module or a wired connection to a digital bus (for example).

The accelerometer module 112 may wirelessly transmit the body vibration data to the RTB application 114 resident on the handheld mobile device 104. Additionally, the aircraft-specific configuration 118 may be provided by the configuration service 116. The configuration service 116 may utilize any remote type of data service (e.g., cloud-based, web-based, FTP, etc.) and/or local data (e.g., local hard drive, optical media, thumb drive, etc.). The aircraft-specific configuration 118 may include data regarding blade size, blade height, rotor balance, aircraft type, aircraft model, aircraft weight, and the like. The aircraft-specific configuration 118 data may be requested by the occupant 102 using the RTB application 114 on the handheld mobile device 104 and/or retrieved by the RTB application 114 from the configuration service 116 (e.g., continuously, periodically, according to user-defined parameters, in response to receiving the same request, etc.). In some embodiments, the RTB application 114 retrieves from the configuration service 116 one or more parameters that may be configured by the occupant 102 and/or another user (e.g., a remote administrator). In other embodiments, the aircraft-specific configuration 118 data may be automatically sent or pushed to the RTB application 114.

RTB solver 122 can utilize the output received from tracker module 108, accelerometer module 112, and/or configuration service 116 to calculate RTB results and/or recommendations. RTB solver 122 may analyze the processed blade tracking data (which may include blade images in some embodiments) as discussed in more detail below, compare the processed blade tracking data to configuration data, vibration data received from the accelerometer module, and/or calculate tracking and balancing recommendations based on the comparison. Based on the results provided by the RTB solver 122, the RTB application 114 resident on the handheld mobile device 104 can display the RTB results and/or send the RTB results and/or suggestions to the occupant 102, other users, and/or other remote and/or local devices.

Turning to fig. 3, another embodiment depicts a side view of a helicopter featuring a handheld mobile device and a tracker module. Here, the occupant 102 operates the aircraft 100 and does not hold the handheld mobile device 104. Alternatively, the handheld mobile device mount 105 is used to secure the handheld mobile device 104 to the fuselage of the aircraft 100. In this embodiment, the handheld mobile device 104 may have one or more accelerometers for measuring rotor-induced vibrations by measuring vibration frequency and/or intensity, instead of a separate accelerometer module. Further, one or more tracker modules 108 may be used to capture a tracking view 110 of the blade 106.

Turning to FIG. 4, a schematic diagram of a system utilizing a handheld mobile device and a tracker module that may be used with the embodiment shown in FIG. 3 is depicted. The occupant 102 may utilize the handheld mobile device 104 to request RTB data regarding the aircraft 100. Tracker module 108 can wirelessly transmit the tracked blade height and position data to RTB solver 122. Handheld mobile device 104 may utilize its own accelerometer module 112 to detect the body vibration frequency and/or intensity. The accelerometer module 112 may provide vibration data to the RTB application 114 within the handheld mobile device 104. Configuration service 116 may provide aircraft-specific configuration 118 to handheld mobile device 104, RTB application 114, and/or RTB solver 122. RTB solver 122 can utilize the output received from tracker module 108, accelerometer module 112, and/or configuration service 116 to calculate RTB results and/or determine RTB recommendations. Based on the results provided by the RTB solver 122, the RTB application 114 resident on the handheld mobile device 104 can send RTB results and/or suggestions to the occupant 102, such as by displaying such suggestions on a display of the handheld mobile device 104.

Turning to fig. 5, a further embodiment depicts a side view of a helicopter featuring a handheld mobile device and an accelerometer module. Here, the occupant 102 operates the aircraft 100 and does not hold the handheld mobile device 104. Alternatively, the handheld mobile device 104 is secured to the cockpit windshield to obtain a tracked view 110 of the tracked blade height and position. In this embodiment, the handheld mobile device 104 may have one or more device cameras 109 (see fig. 6) in place of the tracker module. Furthermore, one or more accelerometer modules 112 may be secured to any suitable surface of aircraft 100 in any suitable manner to measure rotor-induced vibrations.

Turning to FIG. 6, a schematic diagram of a system utilizing a handheld mobile device and an accelerometer module that may be employed by the embodiment of FIG. 5 is depicted. The occupant 102 may utilize the handheld mobile device 104 to request RTB data regarding the aircraft. The accelerometer module 112 may wirelessly transmit the body vibration data to the RTB application 114 resident on the handheld mobile device 104. The handheld mobile device 104 may track raw blade height and position data with its own device camera 109. The device camera 109 may provide raw blade height and position data to the blade image recognition program 120 within the RTB application 114. The blade image recognition program 120 may track one or more blades using any suitable image processing/recognition technique. The blade image recognition program 120 may then output/transmit the blade pulses and reference blade data to the RTB solver within the RTB application 114. Configuration service 116 may provide aircraft-specific configuration 118 to handheld mobile device 104, RTB application 114, and/or the RTB solver. RTB solver 122 can utilize the output received from tracker module 108, accelerometer module 112, and/or configuration service 116 to calculate RTB results and/or provide RTB recommendations. Based on the results provided by the RTB solver 122, the RTB application 114 can send and/or display RTB results and/or RTB suggestions to the occupant 102.

Turning to fig. 7, various embodiments depict a side view of a helicopter featuring a handheld mobile device. The occupant 102 operates the aircraft 100 without holding the handheld mobile device 104. Alternatively, the handheld mobile device mount 105 secures the handheld mobile device 104 to the fuselage of the aircraft 100. In this embodiment, the handheld mobile device 104 may have one or more accelerometers for monitoring rotor-induced vibrations by measuring vibration frequency and/or intensity, instead of an accelerometer module. The handheld mobile device 104 may also have one or more device cameras 109 in place of the tracker module.

Turning to fig. 8, a schematic diagram of a system utilizing a handheld mobile device that may be employed by the embodiment of fig. 7 is depicted. The occupant 102 may utilize the handheld mobile device 104 to request RTB data regarding the aircraft. Handheld mobile device 104 may utilize its own accelerometer module 112 to detect the body vibration frequency and/or intensity. The accelerometer module 112 may provide vibration data to the RTB application 114 within the handheld mobile device 104.

The handheld mobile device 104 may also track raw blade height and position data with its own device camera 109. The device camera 109 may provide raw blade height and position data to the blade image recognition program 120 within the RTB application 114. The blade image recognition program 120 may track one or more blades using any suitable image processing/recognition technique. The blade image recognition program 120 may then transmit the blade pulses and reference blade data to the RTB solver within the RTB application 114. Configuration service 116 may also provide aircraft-specific configuration 118 to handheld mobile device 104, RTB application 114, and/or RTB solver 122. RTB solver 122 can utilize the output received from tracker module 108, accelerometer module 112, and/or configuration service 116 to calculate RTB results and/or recommendations. Based on the results provided by the RTB solver 122, the RTB application 114 can send the RTB results and/or RTB recommendations to the occupant 102.

Turning to fig. 9, a flow diagram for determining tracking and balancing recommendations on a handheld mobile device is presented. The first operation in the RTB process of step 900 may be to ensure that the application is properly configured with an aircraft-specific configuration that defines the aircraft variable parameters used in the RTB calculation. This may be accomplished, for example, by downloading the aircraft configuration from the cloud-based distribution service (e.g., by transmitting the aircraft-specific configuration 118 from the configuration service 116 to the handheld mobile device 104, as described above with respect to fig. 2, 4, 6, and 8). Once the RTB application is ready, the aircraft can fly with the system installed.

At step 902, a state (region) acquisition may be initiated such that RTB data may be collected at a plurality of flight states, wherein the collection is initiated by an operator once the operator confirms that the aircraft is operating at a specified flight state. At step 904, the vibration and blade acquisition may be synchronized. For example, when initiating acquisition, the system ensures that the various components are synchronized. Once synchronization is confirmed, the RTB application may simultaneously acquire blade position and vibration data at steps 906 and 908, respectively. Such synchronization may be accomplished over a wireless link, for example, where the accelerometer module 112 and/or tracker module 108 are remote from the handheld mobile device 104. In the case of using sensors (accelerometer module 112 and/or tracker module 108) internal to handheld mobile device 104, the mechanisms provided by the computing platform of the handheld mobile device are used. At step 906, blade data may be acquired. At step 908, the acquisition of vibration data may include detection of the relative position of the leading and trailing edges of each blade to determine blade tracking height and lead/lag, and/or identification of reference blades, which may be used to identify the remaining blades. In the case of using a device camera (e.g., in the embodiments shown in fig. 5-8), image recognition software may be used to detect unique features of the image associated with the reference blade. In the case where a remote blade camera (such as tracker module 108 shown and described in fig. 1-4) is used, the blade camera generates a unique signal for the reference blade that results from the detection of a unique feature of that blade. By automatically identifying the reference blade in the manner described herein, a separate tachometer may not be required to effectuate reference blade identification in some embodiments. In other embodiments, a tachometer module (e.g., an optical tachometer), which may be wireless or wired, may be affixed to the aircraft for blade tracking.

At step 910, raw vibration data acquired via the device accelerometer or accelerometer module may be stored on the mobile device along with the blade data. Once the blade pass frequency is determined from the reference blade number (digital), signal processing may be employed to determine the level of rotor-induced vibrations at one or more harmonics of the blade frequency in the current flight condition, and it may be determined whether more conditions are required, step 912. At step 914, if more data from further flight states is needed (yes at step 914), the flowchart may return to step 902 until the aircraft has flown all of the needed states and data is collected in each state. Otherwise, if data for all required states has been collected (NO of step 914), the system may proceed to step 916 to calculate balance recommendations and make relevant predictions regarding reduced vibration levels. The proposed modifications may include, for example, placing weight at a specific location on the rotor hub and/or sweeping the rotor blades (i.e., moving the blades forward or backward in their angular position), adjusting the rotor Pitch Change Link (PCL) that controls the angle of each rotor blade individually. Continuing with this non-limiting example, the PCL of a particular leaflet may be lengthened or shortened to move the leaflet up or down. Another adjustment may be a tab of the rotor. To fly the blade higher or lower, it may be advisable to raise or lower the tab.

At step 918, upon request (e.g., from an occupant), RTB vibration measurements and balancing recommendations may be displayed to, for example, the occupant. In some embodiments, the vibration measurement and balance recommendations are displayed on a display of the handheld mobile device 104. For example, lateral vibration measurements obtained while hovering and suggestions to sweep the blade backward or forward may be displayed in conjunction with vertical vibration measurements also obtained while hovering, with suggestions to lengthen or shorten the PCL to correspondingly modify the blade angle. In other embodiments, RTB vibration measurements and balance recommendations may be automatically displayed.

Turning to fig. 10, a block diagram illustrates an exemplary computing device 1000 by which the computing device 1000 may implement embodiments of the present disclosure, for example, in each of the tracker module 108, the accelerometer module 112, and the handheld mobile device 104. The computing device 1000 described herein is but one example of a suitable computing device and does not imply any limitation as to the scope of any embodiments presented. Nothing shown or described with respect to computing device 1000 should be construed as required or to create any type of dependency on any element or elements. In various embodiments, computing device 1000 may include, but is not limited to, a laptop, a server, a client, a tablet, a smartphone, or any other type of device that may utilize data. Computing device 1000 may correspond to a handheld mobile device as described herein. In an embodiment, computing device 1000 includes at least one processor 1002 and memory (non-volatile memory 1008 and/or volatile memory 1010). Computing device 1000 may include non-volatile memory 1008(ROM, flash memory, etc.), volatile memory 1010(RAM, etc.), or a combination thereof. In some embodiments, at least one processor 1002 is coupled to non-volatile memory 1008 and/or volatile memory 1010. By way of non-limiting example, computing device 1000 may utilize RAM, ROM, cache, optical fiber, EPROM/flash memory, CD/DVD/BD-ROM, hard drives, solid state memory devices, optical or magnetic storage devices, diskettes, electrical connections having wires, any system or device of magnetic, optical, semiconductor, or electronic type, or any combination thereof.

For example, computing device 1000 may include one or more displays and/or output devices 1004 such as a monitor, speaker, headset, projector, wearable display, holographic display, and/or printer. This may be used, for example, as part of the handheld mobile device 104 with respect to fig. 1 to display the RTB application 114. Computing device 1000 may also include one or more input devices 1006, which input devices 1006 may include, by way of example, any type of mouse, keyboard, disk/media drive, memory stick/thumb drive, memory card, pen, touch input device, biometric scanner, sensor, accelerometer, voice/auditory input device, motion detector, camera, ruler, and the like. As shown in fig. 8, the handheld mobile device 104 may include a device camera 109 and/or an accelerometer module 112.

The network interface/communication module 1012 may facilitate communication over the network 1014 via wire, via a wide area network, via a local area network, via a personal area network, via a cellular network, via a satellite network, and so forth. Suitable local area networks may include wired ethernet and/or wireless technologies, such as wireless fidelity (Wi-Fi). Suitable personal area networks may include wireless technologies such as IrDA, Bluetooth, wireless USB, Z-Wave, ZigBee, and/or other near field communication protocols. Suitable personal area networks may similarly include wired computer buses such as USB and FireWire. Suitable cellular networks include, but are not limited to, technologies such as LTE, WiMAX, UMTS, CDMA, and GSM. Computing device 1000 may include one or more communication devices 1008 to facilitate communications with one or more remote devices, which may include, for example, client and/or server devices. The network interface/communication module 1012 may be communicatively coupled to any device capable of transmitting and/or receiving data via the network 1014. Thus, the network interface/communication module 1012 may include a communication transceiver for sending and/or receiving any wired or wireless communications. For example, the network interface/communication module 1012 may include an antenna, a modem, a LAN port, a Wi-Fi card, a WiMax card, mobile communication hardware, near field communication hardware, satellite communication hardware, and/or any wired or wireless hardware for communicating with other networks and/or devices.

The computer-readable medium 1016 may include a plurality of computer-readable media, each of which may be a computer-readable storage medium or a computer-readable signal medium. The computer-readable medium 1016 may reside, for example, within the input device 1006, the non-volatile memory 1008, the volatile memory 1010, or any combination thereof. Computer readable storage media may include tangible media capable of storing instructions associated with or used by a device or system. By way of non-limiting example, a computer-readable storage medium comprises: RAM, ROM, cache, fiber optics, EPROM/flash memory, CD/DVD/BD-ROM, a hard disk drive, a solid state memory device, an optical or magnetic storage apparatus, a magnetic disk, an electrical connection having wires, or any combination thereof. The computer readable storage medium may also include systems or devices of a magnetic, optical, semiconductor, or electronic type, for example. The computer-readable storage medium is non-transitory and excludes propagated signals and carrier waves.

It should be noted that recitations of a component of the present disclosure being "configured" or "programmed" in a particular manner to embody a particular property or function in a particular manner herein are structural recitations as opposed to recitations of intended use. More specifically, references herein to the manner in which a component is "configured" or "programmed" denotes an existing physical condition of the component and, as such, is to be taken as a definite recitation of the structural characteristics of the component.

The order of execution or performance of the operations in the examples of the disclosure illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and examples of the disclosure may include more or less operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the disclosure.

It should be noted that the terms "substantially" and "approximately" may be utilized herein to represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. These terms are also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue.

Although specific embodiments have been illustrated and described herein, it should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, these aspects need not be used in combination. It is therefore intended to cover in the appended claims all such changes and modifications that are within the scope of the claimed subject matter.

Further aspects of the invention are provided by the subject matter of the following clauses:

a handheld mobile device configured for use within a cockpit of an aircraft, comprising: a display; a memory comprising an application configured to utilize the display; a processor coupled to the memory, wherein the application is configured via the processor to: receiving aircraft-specific configuration data; receiving input data corresponding to blade height and position from a tracker module; receiving fuselage vibration data from an accelerometer module; computing recommendations regarding tracking and balancing; and outputting the tracking and balancing recommendation via the display.

The handheld mobile device of any preceding item, wherein: the input data is configured to be wirelessly received from the tracker module; and the tracker module is a physical device affixed to a location within the cockpit that is physically separate from the handheld mobile device.

The handheld mobile device of any preceding item, wherein: the body vibration data is configured to be wirelessly received from the accelerometer module; and the accelerometer module is a physical device secured to a location within the cockpit that is physically separate from the handheld mobile device.

The handheld mobile device of any preceding item, wherein: the input data is configured to be wirelessly received from the tracker module; the tracker module is a physical device affixed to a location within the cockpit that is physically separate from the handheld mobile device; the body vibration data is configured to be wirelessly received from the accelerometer module; the accelerometer module is a physical device secured to a location within the cockpit that is physically separate from the handheld mobile device; and the tracker module is physically separated from the accelerometer module.

The handheld mobile device of any preceding claim, wherein the application further comprises a blade recognition component configured to process blade tracking data with image recognition and output the result to an RTB (rotor tracking and balance) solver.

The handheld mobile device of any preceding item, wherein the RTB solver is configured to: analyzing the processed blade tracking data; comparing the processed blade tracking data to the configuration data; and calculating a tracking and balancing recommendation based on the comparison.

An aircraft, comprising: a cockpit or cabin; and a handheld mobile device according to any preceding item, wherein the handheld mobile device is fixed to the cockpit or a portion of the nacelle.

The aircraft of any preceding item, wherein the handheld mobile device is secured to the cockpit or a transparent exterior portion of the cabin.

A system configured for use within a cockpit or cabin of an aircraft, the system comprising: a handheld mobile device, the handheld mobile device comprising: a display; a memory, the memory including an application; and a processor coupled to the memory, wherein the processor is configured to execute the application to: receiving aircraft-specific configuration data; receiving input data corresponding to blade height and position from a tracker module; receiving fuselage vibration data from an accelerometer module; computing recommendations regarding tracking and balancing; and outputting the tracking and balancing suggestions via the display; a tracker module comprising a camera, the tracker module configured to: generating input data corresponding to blade height and position with the camera; and outputting the input data to the handheld mobile device; the accelerometer module comprising an accelerometer and configured to: generating body vibration data with the accelerometer; and outputting the body vibration data to the handheld mobile device; and a configuration service configured to output the aircraft-specific configuration data to the handheld mobile device.

The system of any preceding item, wherein the handheld mobile device is secured to the cockpit or a portion of the nacelle.

The system of any preceding item, wherein the handheld mobile device is secured to the cockpit or a transparent exterior portion of the nacelle.

The system of any preceding clause, wherein: the input data is configured to be wirelessly received from the tracker module; and the tracker module is a physical device affixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device.

The system of any preceding clause, wherein: the body vibration data is configured to be wirelessly received from the accelerometer module; and the accelerometer module is a physical device affixed to the cockpit or a location within the nacelle that is physically separate from the handheld mobile device.

The system of any preceding clause, wherein: the tracker module is a physical device affixed to a transparent exterior surface of the flight deck or the cabin at a location within the aircraft flight deck or cabin that is physically separate from the handheld mobile device; the accelerometer module is a physical device affixed to a location within the cockpit or nacelle that is physically separate from the handheld mobile device; and the tracker module is physically separated from the accelerometer module.

The system of any preceding item, wherein the application further comprises a blade identification component configured to process blade tracking data using image recognition and output the result to an RTB (rotor tracking and balancing) solver.

The system of any preceding item, wherein the RTB solver is configured to: analyzing the processed blade tracking data; comparing the processed blade tracking data to the configuration data; and calculating a tracking and balancing recommendation based on the comparison.

A method of utilizing a handheld mobile device in an aircraft cockpit or cabin comprising: accessing an application on the handheld mobile device; downloading aircraft-specific configuration data using the application; starting data acquisition of a state; synchronously vibrating and collecting blades; acquiring blade and vibration data; storing the vibration and blade data for the state; calculating and storing a vibration result of the state; calculating tracking and balancing recommendations; and displaying the vibration results, tracking recommendations, and balancing recommendations on the handheld mobile device.

The method of any preceding item, wherein calculating the tracking and balancing recommendation is based on more states that are not required.

The method of any preceding item, wherein acquiring blade and vibration data further comprises: analyzing the processed blade tracking data; comparing the analyzed blade tracking data with the configuration data and the acquired vibration data; and calculating a tracking and balancing recommendation based on the comparison.

The method of any preceding item, further comprising securing the handheld mobile device to a transparent exterior portion of the aircraft cockpit or cabin.