ANISOTROPIC MAGNETO-RESISTIVE SENSOR FLAP MEASURING ON GIMBALLED HUB

TECHNICAL FIELD

The present disclosure relates generally to systems and methods for measuring rotor-hub flapping in vertical takeoff and landing(“VTOL”) rotary aircraft and more particularly, but not by way of limitation, to systems and methods employing anisotropic magneto-resistive (“AMR”) sensors.

BACKGROUND

This section provides background information to facilitate a better understanding of the various aspects of the disclosure. It should be understood that the statements in this section of this document are to be read in this light, and not as admissions of prior art.

Rotor-hub flapping-measurement systems have used rotary-variable-differential transducer (“RVDT”) sensors. However, such systems have a number of drawbacks, including size, weight, cost, complexity of electronics, and sensitivity to temperature and mechanical vibration.

SUMMARY

This summary is provided to introduce a selection of concepts that are further described below in the detailed description. This summary is not necessarily intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of claimed subject matter.

A rotor-hub flap-measurement system includes a rotor hub operable to flap relative to a rotational axis of a rotor mast. The rotor hub includes a fork driver fixedly coupled to the rotor mast and operable to rotate about the rotational axis, a drive plate operable to rotate about the rotational axis and to rotate out of a plane perpendicular to the rotational axis, out-of-plane rotation indicating flapping of the rotor hub, and a universal joint coupled to the drive plate and comprising a cross, the cross comprising four trunnions equally spaced azimuthally about the rotational axis. The rotor-hub flap-measurement system also includes a magneto-resistive sensor system coupled to the cross and operable to detect rotation of a first trunnion of the four trunnions.

A rotor-hub flap-measurement system includes a rotor hub operable to flap relative to a rotor-mast rotational axis and includes a universal joint that includes a cross. The cross includes four trunnions equally spaced azimuthally about the rotor-mast rotational axis. The rotor-hub flap-measurement also includes a magneto-resistive sensor system coupled to the cross and operable to detect rotation of a first trunnion of the four trunnions. The magneto-resistive sensor system includes a magnet connected to the cross a magneto-resistive sensor positioned relative to the magnet and operable to detect rotation of the magnet connected to a rotational axis of the cross.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

FIG. 1 is an illustrative vertical takeoff and landing(“VTOL”) rotary aircraft;

FIG. 2 shows the rotor system of FIG. 1 in more detail according to one illustrative embodiment;

FIG. 3 illustrates an AMR sensor system in detail;

FIGS. 4A-C show sensor arrangements that employ the AMR sensor;

FIG. 5 illustrates a sensor system that utilizes multiple sensor arrangements;

FIG. 6 illustrates a sensor system that utilizes multiple sensor arrangements;

FIG. 7 illustrates a sensor system that utilizes multiple sensor arrangements;

FIG. 8 illustrates a sensor system that utilizes multiple sensor arrangements;

FIG. 9 illustrates a rotor hub according to an illustrative embodiment;

FIG. 10 illustrates in more detail aspects of the rotor hub of FIG. 9;

FIG. 11 illustrates the rotor hub of FIG. 9 in a different flapping position;

FIG. 12 is a cross-sectional side view of a drive plate, a cap, an AMR sensor assembly , and associated components of the rotor hub of FIG. 9;

FIG. 13 is a cross-sectional plan view of the rotor hub of FIG. 9;

FIG. 14 is a top perspective view of a rotor hub according to an illustrative embodiment;

FIG. 15 is a top perspective view of a fork driver and associated components;

FIG. 16 is a bottom perspective view of a drive plate and associated components of the rotor hub of FIG. 14; and

FIG. 17 is a cross-sectional plan view of the rotor hub of FIG. 14.

DETAILED DESCRIPTION

Various embodiments will now be described more fully with reference to the accompanying drawings. The disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.

FIG. 1 is an illustrative vertical takeoff and landing(“VTOL”) rotary aircraft 100. The rotary aircraft 100 includes a rotor system 102, a fuselage 104, and a tail boom 106. The tail boom 106 carries an anti-torque system 108. The rotor system 102 includes a teetering rotor hub and a main rotor 110 that includes a plurality of rotor blades for creating flight, a rotor blade 111(1) and a rotor blade 111(2) being shown in FIG. 1, although a different number of rotor blades could be used other than two as illustrated. The rotor system 102 may include a control system for selectively controlling pitch of each of the plurality of rotor blades 111(1) and 111(2) of the main rotor 110 to control direction, thrust, and lift of the rotary aircraft 100. The anti-torque system 108 includes a tail rotor 112. The tail rotor 112 provides thrust to counter torque due to rotation of the main rotor 110 about a main-rotor axis 114. The teetering rotor hub has a discrete hinge in line with the main-rotor axis 114. The teetering rotor hub and the rotor blades 111(1) and 111(2) are shown as perpendicular to the main-rotor axis 114, at which orientation relative to the main rotor 110 a rotor-hub-flapping angle α = 0°.

FIG. 2 shows a rotor system 201 of FIG. 1 in detail according to one illustrative embodiment. In the example of FIG. 2, the rotor system 201 includes a rotor mast 200 and a rotor hub 202. In contrast to the teetering rotor hub of FIG. 1, the rotor hub 202 is a gimballed rotor hub. The rotor hub 202 couples the rotor blades 111(1) and 111(2) of the main rotor 110 to the rotor mast 200, the rotor blades 111(1) and 111(2) being shown only in part. In some examples, the rotor system 201 may include more or fewer components, not all of which are necessarily shown or are shown but not labeled with a reference numeral in FIG. 2 for purposes of clarity.

The rotor mast 200 and the rotor hub 202 are examples of mechanical components that generate and transmit torque and rotation. A power train of which the rotor mast 200 and the rotor hub 202 are a part may include a variety of components, such as, for example, an engine, a transmission, and differentials. The rotor blades 111(1) and 111(2) are coupled to the rotor hub 202 such that rotation of the rotor hub 202 causes the rotor blades 111(1) and 111(2) to rotate about the rotor mast 200.

The rotor blades 111(1) and 111(2) may be subject to a variety of different forces. For example, rotation of the rotor blades 111(1) and 111(2) may result in a centrifugal(“CF”) force against the rotor blades 111(1) and 111(2) in a direction away from the rotor mast 200. In addition, weight of the rotor blades 111(1) and 111(2) may result in a transverse force being applied against the rotor hub 202. These and other forces may cause the rotor blades 111(1) and 111(2) to feather, drag(i.e., lead/lag), and flap during flight of the rotary aircraft 100.

The term rotor-hub flapping generally refers to motion of a rotor hub that has a discrete hinge in line with a rotor-mast axis(e.g., main-rotor axis 114) during operation such that α ≠ 0°. Such rotor hub designs are commonly used in gimballed rotor hubs and teetering rotor hubs. In the example of FIG. 2, the rotor hub 202 is shown at a substantially zero-degree rotor-hub flapping angle in which α is slightly offset from zero, zero degrees being 90° from the main-rotor axis 114. When rotor-hub flapping occurs, the rotor blades 111(1) and 111(2) deviate upward or downward.

The rotor system 201 includes a hub-flap measurement system 208. The hub-flap measurement system 208 measures flapping of the rotor hub 202 such that the rotor hub 202 is not perpendicular to the main-rotor axis 114. It will be appreciated that when the rotor hub 202 is not perpendicular to the main-rotor axis 114, an amount of hub flap will be different at different azimuthal positions of the rotor hub 202. The hub-flap measurement system 208 may be used to estimate flapping of the rotor blade 111(2) at a given azimuthal position by measuring flapping of the rotor hub 202, since the majority of rotor-blade flapping typically is the result of rotor-hub flapping. Although the hub-flap measurement system 208 is illustrated as aligned azimuthally with the blade 111(2), this need not necessarily be the case, since any suitable number of hub-flap measurement systems 208 may be arranged around a circumference of the rotor hub 202 as desired in a given implementation. The hub-flap measurement system 208 includes a flap-linkage arm 204, an anisotropic magneto-resistive(“AMR”) sensor system 210, and a platform 212. The flap linkage couples the rotor hub 202 to the AMR sensor system 210, as described in more detail below.

The AMR sensor system 210 utilizes an AMR sensor. An AMR sensor has a function where resistance decreases when a magnetic field is applied and in which the function is dependent on a direction of magnetic force lines applied to the sensor. AMR sensors measure flux angle and not magnitude and can operate in a saturated condition, such that they are less susceptible to external influences and have increased sensitivity with decreased variation in measurement in comparison to rotary-variable differential-transformer(“RVDT”) based systems. Many AMR sensors are programmable, which facilitates their use in a wide variety of applications. For purposes of this application, the term angle sensors includes both AMR sensors and giant magneto-resistive(“GMR”) sensors, either of which may be used in systems and methods discussed herein. Outputs of many angle sensors may be analog or digital.

The platform 212, shown for example integrated into spinner-spoke mounts, supports the AMR sensor system 210 and couples the AMR sensor system 210 to the rotor mast 200. In the example of FIG. 2, the flap-linkage arm 204 is coupled to the AMR sensor system 210 and to the rotor hub 202, respectively, via a spherical bearing 216 and a spherical bearing 218. During operation, in an illustrative embodiment, flapping of the rotor hub 202 causes the flap-linkage arm 204 to move, which movement is translated to the AMR sensor system 210 via the spherical bearing 218 so the AMR sensor system 210 may use an AMR sensor, discussed in more detail below, contained therein to measure an amount of flapping of the rotor hub 202. The AMR sensor system 210 is configured, in a typical embodiment, to rotate with the rotor mast 200 during operation. The hub-flap measurement system 208 does not directly measure flapping of the rotor blade 111(1); rather, the hub-flap measurement system 208 measures movement of the rotor hub 202 at the spherical bearing 216 and, based thereon, estimates flapping of the rotor blade 111(1) based on movement of the rotor hub 202 at the spherical bearing 216. A second hub-flap measurement system(unnumbered) is shown in FIG. 2. It will be appreciated that the second hub-flap measurement system is analogous to the hub-flap measurement system 208 and that, in a typical embodiment, a hub-flap measurement system is associated with each rotor blade 111(1)-111(n) of a given VTOL rotary aircraft.

Measurements provided by the hub-flap measurement system 208 alone may be of limited value. For example, the hub-flap measurement system 208 does not itself include mechanisms for correlating measurements with rotor-blade azimuthal rotational positions. Therefore, even if the hub-flap measurement system 208 accurately measures rotor-hub flapping angles, for example, the hub-flap measurement system 208 alone is not able to calculate at which points of a 360° rotational azimuth of the main rotor 110 given measurements occur.

FIG. 3 illustrates the AMR sensor system 210 in more detail. As shown in FIG. 3, the AMR sensor system 210 includes an AMR sensor 300, a magnet 302, a mounting bracket 304(shown as an L bracket), a bearing housing 306, a bearing 308 housed by the bearing housing 306, and a sensor arm 310. The magnet 302 may be, for example, a Neodymium magnet or a Cobalt magnet. In a typical embodiment, the magnet 302 is diametrically magnetized. In the embodiment shown, the AMR sensor 300 is mounted to the mounting bracket 304 and the magnet 302 is mounted to the sensor arm 310; however, the AMR sensor 300 could be mounted to the sensor arm 310 and the magnet 302 mounted to the mounting bracket 304 without departing from principles disclosed herein. The bearing 308, which is mounted within the bearing housing 306, is typically a ball bearing, although other suitable types of bearings such as a needle-roller bearing or a TEFLON bearing may be used.

The magnet 302 and the AMR sensor 300 are positioned so as to be near one another in order that the AMR sensor 300 can detect relative rotation between the AMR sensor and the magnet 302. The sensor arm 310 includes a spherical-bearing mounting section 312, to which the flap-linkage arm 204 is connected via the spherical bearing 218. Flapping of the rotor hub 202 causes the flap-linkage arm 204 to move up or down in response thereto. As the flap-linkage arm 204 moves, the spherical-bearing mounting section 312 and the magnet 302 are caused to rotate about a rotational axis 314 of the bearing 308. The AMR sensor 300 mounted adjacent to the magnet 302 is able to measure an amount of the rotation of the magnet 302 about the rotational axis 314.

Even though AMR sensors have a number of advantages relative to RVDT sensors, many AMR sensors do not have the robust in-line monitoring capabilities of RVDT sensors; therefore, several AMR-sensor-based architectures are outlined below that can be utilized to identify erroneous AMR sensing. In typical embodiments, full-channel independence of both power and signal are implemented and concepts can be applied to federated or distributed architectures.

FIGS. 4A-4C illustrate different configurations in which multiple AMR sensors and magnets are utilized in order to identify erroneous AMR sensing. Any of the configurations can be employed in embodiments of an AMR sensor system similar to the AMR sensor system 210.

FIG. 4A shows a sensor arrangement 400 that includes an AMR sensor 402(1) and an AMR sensor 402(2) on either side of a magnet 404(1). As noted above, either the magnet 404(1) or the AMR sensors 402(1) and 402(2) could rotate with the other being held stationary. It will be appreciated that, in the sensor arrangement 400, each of the AMR sensors 402(1) and 402(2) senses relative rotation with respect to the magnet 404(1) and, in the event of a failure of one of the AMR sensors 402(1) or 402(2), sensing of relative rotation could still be accomplished.

FIG. 4B shows a sensor arrangement 406 that includes the AMR sensors 402(1) and 402(2) as well as the magnet 404(1) and a magnet 404(2). The magnets 404(1) and 404(2) are each paired with a respective one of the AMR sensors 402(1) and 402(2), such that two independent magnet-AMR-sensor pairs that are sufficiently magnetically distant from one another are utilized to reduce the chance of a common mode failure, especially in situations in which a common mode could validate a measurement in a given architecture.

FIG. 4C shows a sensor arrangement 410 that includes the AMR sensors 402(1) and 402(2) as well as the magnet 404(1) and an intermediate circuit board 408, on either side of which are mounted the AMR sensors 402(1) and 402(2). In the sensor arrangement 410, each of the AMR sensors 402(1) and 402(2) is able to sense relative rotation of the magnet 404(1).

FIG. 5 illustrates a sensor system that utilizes multiple sensor arrangements 400. A sensor system 500 includes a hub 502 and a rotor blade 504, a rotor blade 506, and a rotor blade 508 extending from the hub 502. The hub 502 has three sensor arrangements 400(1), 400(2), and 400(3) associated therewith, each of which is aligned azimuthally with one of the rotor blades 504, 506, and 508, respectively. The sensor system 500 may be referred to as a dual triplex architecture. As noted above, the sensor arrangements 400(1)-(3) need not necessarily be so aligned.

Each of the sensor arrangements 400(1), 400(2), and 400(3) includes a pair of AMR sensors and a magnet. Each of the AMR sensors is inter-operably coupled to a respective channel of a flight control computer(“FCC”), FCC 510, FCC 512, and FCC 514 being associated with sensor arrangements 400(1), 400(2), and 400(3), respectively. Each of the FCC 510, 512, and 514 has a channel A and a channel B inter-operably coupled to a given AMR sensor, each of which channels is output to respective data buses 516, 518, and 520. Data buses 516, 518, and 520 are each inter-operably coupled to a cross channel datalink(“CCDL”) 522.

Each of the FCC 510, FCC 512, and FCC 514 can identify erroneous sensing by its associated sensor arrangement 400(1), 400(2), and 400(3) by comparing measurement across channels A and B or comparing flapping solutions across channels. In a typical embodiment, a mis-compare by one of the FCC 510, FCC 512, and FCC 514 between channels A and B identifies a solution as invalid. In some embodiments, even if a mis-compare occurs, the sensor system 500 can continue to operate in spite of the mis-compare based on valid measurements of one or more of the remaining FCCs.

FIG. 6 illustrates a sensor system that utilizes multiple sensor arrangements 400. A sensor system 600 includes the hub 502 the rotor blade 504, the rotor blade 506, and the rotor blade 508 extending from the hub 502. The hub 502 has two sensor arrangements 400(1) and 400(2) associated therewith, each of which is aligned azimuthally with one of the rotor blades 504 and 506, respectively. The sensor system 600 may be referred to as a dual duplex architecture. As noted above, the sensor arrangements 400(1)-(2) need not necessarily be so aligned.

Each of the sensor arrangements 400(1) and 400(2) includes a pair of AMR sensors and a magnet. Each of the AMR sensors is inter-operably coupled to a respective channel of a flight control computer(“FCC”), FCC 510 and FCC 512 being associated with the sensor arrangements 400(1) and 400(2), respectively. Each of the FCC 510 and 512 has a channel A and a channel B inter-operably coupled to a given AMR sensor, each of which channels is output to respective data buses 516 and 518. Data buses 516 and 518 are each inter-operably coupled to the cross channel datalink(“CCDL”) 522.

Each of the FCC 510 and the FCC 512 can identify erroneous sensing by its associated sensor arrangement 400(1) and 400(3) by comparing measurement across channels A and B or comparing flapping solutions across channels. In a typical embodiment, In a typical embodiment, a mis-compare by one of the FCC 510 and FCC 512 between channels A and B identifies a solution as invalid. In some embodiments, even if a mis-compare occurs, the sensor system 600 can continue to operate in spite of the mis-compare based on valid measurements of one or more of the remaining FCCs.

FIG. 7 illustrates a sensor system that utilizes multiple sensor arrangements 702. A sensor system 700 includes the hub 502, the rotor blade 504, the rotor blade 506, and the rotor blade 508 extending from the hub 502. The hub 502 has four sensor arrangements 702(1), 702(2), 702(3), and 702(4) associated therewith, the sensor arrangement 702(1) and the sensor arrangement 702(3) being aligned azimuthally with the rotor blades 504 and 506, respectively, the sensor arrangement 702(2) and the sensor arrangement 702(4) being offset azimuthally from any of the rotor blades 504, 506, and 508. Each of the sensor arrangements 702(1)-(3) includes only a single magnet and a single AMR sensor. The sensor system 700 may be referred to as a dual duplex architecture.

Each of the AMR sensors is inter-operably coupled to a respective channel of a flight control computer(“FCC”), FCC 510 and FCC 512 being associated with the sensor arrangements 702(1), 702(2), 702(3), and 702(4), respectively, as indicated in FIG. 7. In other words, sensor arrangements 702(1), 702(2), 702(3), and 702(4) are associated with channel A of the FCC 510, channel B of the FCC 512, channel A of the FCC 512, and channel B of the FCC 512. Data buses 516 and 518 are each inter-operably coupled to a cross channel datalink(“CCDL”) 522.

Each of the FCC 510 and 512 can identify erroneous sensing by one of its associated sensor arrangements 702(1)-(4) by comparing flapping solutions across channels. In a typical embodiment, a mis-compare by one of the FCC 510 and the FCC 512 identifies a solution as invalid. In some embodiments, even if a mis-compare occurs, the sensor system 700 can continue to operate in spite of the mis-compare based on valid measurements of the remaining FCC.

FIG. 8 illustrates a sensor system that utilizes multiple sensor arrangements 702. A sensor system 800 includes the hub 502, the rotor blade 504, the rotor blade 506, and the rotor blade 508 extending from the hub 502. The hub 502 has three sensor arrangements 702(1), 702(2), and 702(4) associated therewith, each of which is aligned azimuthally with one of the rotor blades 504, 506, and 508, respectively. The sensor system 800 may be referred to as a single triplex architecture. As noted above, the sensor arrangements 702(1), 702(2), and 702(4) need not necessarily be so aligned.

Each of the sensor arrangements 702(1), 702(2), and 70243) includes an AMR sensor and a magnet. Each of the AMR sensors is inter-operably coupled to a flight control computer(“FCC”), FCC 810, FCC 812, and FCC 814 being associated with sensor arrangements 702(1), 702(2), and 702(4), respectively. Each of the FCC 810, 812, and 814 is a single-channel FCC that is inter-operably coupled to a given AMR sensor and outputs a signal to respective data buses 802, 804, and 806. Data buses 802, 804, and 806 are each inter-operably coupled to cross channel datalink(“CCDL”) 522. In a typical embodiment, the sensor system 800 can identify erroneous sensing by a process of comparing outputs of the sensor arrangements 702(1), 702(2), and 702(4) and applying a voting algorithm of flapping solutions among the FCC 810, FCC 812, and FCC 814. In another embodiment, the sensor arrangement 702(4) and the FCC 814 may be eliminated such that erroneous flapping is detected by comparing solutions between the FCC 810 and the FCC 812.

In addition to the capabilities of the architectures described relative to FIGS. 5-8, an additional layer of failure robustness can be achieved in the case all system FCCs have invalid measurements. For example, in the dual duplex embodiment of FIG. 5, if two channels of a given FCC have different sensor outputs, but the sensor system as a whole can determine that two sensors, each on a different FCC, yield an overall flapping solution that is in agreement, the agreed-upon flapping solution can be selected and utilized.

FIG. 9 illustrates a gimballed rotor hub 900 that utilizes a plurality of AMR sensors and that eliminates a need for various components described above as included within the hub-flap measurement system 208. The rotor hub 900 includes a fork driver 902 fixedly couplable, for example, to the rotor mast 200 and that rotates with a rotor mast such as the rotor mast 200 about a main-rotor axis such as the main-rotor axis 114.

The rotor hub 900 also includes a drive plate 904 that also rotates about the main-rotor axis 114.The rotor hub 900 may rotate out of a plane perpendicular to the main-rotor axis 114, such rotation being indicative of flapping. A top surface 922 of the drive plate 904 is also illustrated. In a typical embodiment, the top surface 922 includes a planar surface that is perpendicular to the main-rotor axis 114 when no flapping is occurring. The drive plate 904 is shown bolted to a yoke 916, only a portion of which is shown. The yoke 916 is coupled to a plurality of rotor blades (not shown).

The fork driver 902 has a cap 906 fixedly attached to an external surface thereof, while the drive plate 904 has a cap 908 fixedly attached to an external surface thereof. An AMR sensor assembly 910 is carried by a bracket attached to an external surface of the cap 906. In similar fashion, an AMR sensor assembly 912 is carried by a bracket attached to an external surface of the cap 908. AMR sensor assemblies corresponding to the AMR sensor assemblies 910 and 912 may be included on opposite sides of the rotor hub 900, such that identical AMR sensor assemblies are on opposite sides thereof from one another in a mirrored configuration. Each of the AMR sensor assembly 910 and the AMR sensor assembly 912 is illustrated as translucent in order to better demonstrate various aspects of the rotor hub 900 and includes an AMR sensor that can detect rotational movement of a magnet in proximity to the AMR sensor. Also shown is a portion of a cross 914 of a universal joint of the rotor hub 900, which universal joint permits the rotor hub 900 to flap. In operation, AMR sensors of the AMR sensor assemblies 910 and 912 measure rotation of a corresponding magnet in proximity thereto.

In FIG. 9, a magnet 918 is shown on the cap 906. The magnet 918 has shown thereon a line 920. The line 920 is illustrated as substantially parallel to an amount of rotation of the magnet 918 about an axis perpendicular to a face plane 924 of the cap 906 and the bracket of the AMR sensor assembly 910, the axis corresponding to a rotational axis of a trunnion of the cross 914. In other words, as the magnet 918, which is positioned in proximity to an AMR sensor of the AMR sensor assembly 910 and is fixedly coupled to the cross 914, rotates about the axis perpendicular to the face plane 924, the AMR sensor of the AMR sensor assembly 910 detects relative rotational movement between the AMR sensor and the magnet 918, such relative movement being indicative of flapping about the rotational axis of the trunnion of the cross 914. It will be understood that the line 920 is shown for illustrative purposes only. FIG. 10 illustrates a portion of the cap 906, the AMR sensor assembly 910, the magnet 918, the line 920, and the face plane 924 in greater detail.

In similar fashion, a magnet 926 is shown on the cap 908. The magnet 926 has shown thereon a line 928. The line 928 is illustrated as substantially parallel to an amount of rotation of the magnet 926 about an axis perpendicular to a face plane 930 of the cap 908 and the bracket of the AMR sensor assembly 912, the axis corresponding to a rotational axis of a trunnion of the cross 914. In other words, as the magnet 926, which is positioned in proximity to an AMR sensor of the AMR sensor assembly 912 and is fixedly coupled to the cross 914, rotates about the axis perpendicular to the face plane 930, the AMR sensor of the AMR sensor assembly 912 detects relative rotational movement between the AMR sensor and the magnet 926, such relative rotational movement being indicative of flapping about the rotational axis of the trunnion of the cross 914. It will be understood that the line 928 is shown for illustrative purposes only and need not be included for the rotor hub 900 to operate properly. FIG. 11 illustrates the rotor hub 900 in a different flapping position from that shown in FIG. 9 as indicated by the lines 920 and 928.

FIG. 12 is a cross-sectional side view of the drive plate 904, the cap 908, the AMR sensor assembly 912, and associated components. As illustrated in FIG. 12, the drive plate 904 is shown such that the top surface 922 of the drive plate 904 is parallel to the y axis, which axis is perpendicular to the face plane 924. In similar fashion, the x axis is parallel to the main-rotor axis 114. Rotation of the drive plate 904 about a rotational axis A, which axis is parallel to the y axis is detected by relative rotation of the magnet 926 and an AMR sensor 1208.

The AMR sensor 1208 is part of the AMR sensor assembly 912 and is mounted to a bracket as shown. The magnet 926 is mounted to a spacer 1204. The spacer 1204 is fixedly connected to a trunnion 1212. In some embodiments, no spacer is used and the magnet 926 is mounted directly to the trunnion 1212. A bearing assembly 1202, which may include, for example, needle bearings and bearing races, permits the drive plate 904 to rotate about the axis A relative to the trunnion 1212, which rotation causes the AMR sensor 1208 to rotate about the same axis, thereby resulting in relative rotational movement of the AMR sensor 1208 and the magnet 926. Those having skill in the art will appreciate that operation of the AMR sensor assembly 910 relative to a respective trunnion of the cross 914 is analogous to that described herein relative to FIG. 12 in that relative AMR-sensor-magnet rotation occurs.

In some embodiments of the rotor hub 900, only a single AMR sensor and magnet are utilized. In such cases, so long as measurements can be correlated to an azimuthal position of rotation of the rotor hub 900 about the main-rotor axis 114, amplitude and direction of flapping can be determined. However, if two or more pairs of AMR sensors and magnets are utilized, more instantaneous measurements of flapping can be made.

FIG. 13 is a cross-sectional plan view of the rotor hub 900. The cross-section passes through the rotational axes of the four trunnions of the cross 914, respective trunnions 1212(1)-(4) being shown arranged in 90° azimuthal increments in a plane perpendicular to the main-rotor axis 114 such that no flapping out of the plane is occurring. A rotational axis A and a rotational axis B are shown perpendicular to one another. Bearing assemblies 1202(1)-(4) are illustrated associated with respective ones of the trunnions 1212(1)-(4).

The fork driver 902 has coupled thereto on opposite sides thereof a cap 906(1) and a cap 906(2), a magnet 918(1) and a magnet 918(2), and an AMR sensor assembly 910(1) and an AMR sensor assembly 910(2), respective opposing components being associated with one of the trunnions 1212(3) or 1212(4). Thus, rotation of the trunnions 1212(3) and 1212(4) about the axis B may be detected.

In similar fashion, the drive plate 904 has coupled thereto on opposite sides thereof a cap 908(1) and a cap 908(2), a magnet 926(1) and a magnet 926(2), and an AMR sensor assembly 912(1) and an AMR sensor assembly 912(2), respective opposing components being associated with one of trunnions 1212(1) or 1212(2). Thus rotation of the trunnions 1212(1) and 1212(2) about the axis A may be detected.

FIG. 14 illustrates a gimballed rotor hub 1400 that utilizes a plurality of AMR sensors and that eliminates a need for various components described above as included within the hub-flap measurement system 208. The rotor hub 1400 includes a fork driver 1402 fixedly couplable, for example, to the rotor mast 200 and that rotates with a rotor mast such as the rotor mast 200 about a main-rotor axis such as the main-rotor axis 114.

The rotor hub 1400 also includes a drive plate 1404 that also rotates about the main-rotor axis 114; however, in contrast to the fork driver 1402, the drive plate 1404 may also rotate out of a plane perpendicular to the main-rotor axis 114, such rotation being indicative of flapping of the rotor hub 1400. A top surface 1422 of the drive plate 1404 is also illustrated. In a typical embodiment, the top surface 1422 includes a planar surface that is perpendicular to the main-rotor axis 114 when no flapping is occurring. The drive plate 1404 is typically bolted to a yoke coupled to a plurality of rotor blades (not shown).

The fork driver 1402 has AMR sensor assemblies 1410(1) and 1410(2) carried by respective brackets attached to an internal surface of the fork driver 1402 and thereby rigidly coupled to the rotor mast 200. In similar fashion, AMR sensor assemblies 1412(1) and 1412(2) are carried by respective brackets attached to an internal surface of the drive plate 1404. As illustrated in FIG. 14, the AMR sensor assemblies 1410(1) and 1410(2) and 1412(1) and 1412(2) are positioned on opposite sides of the rotor hub 1400, such that identical AMR sensor assemblies are on opposite sides thereof from one another in a mirrored configuration. Each of the AMR sensor assemblies 1410(1) and 1410(2) and the AMR sensor assemblies 1412(1) and 1412(2) includes an AMR sensor that can detect rotational movement of a magnet in proximity to the respective AMR sensor. Also shown is a portion of a cross 1414 of a universal joint of the rotor hub 1400, which universal joint permits the rotor hub 1400 to flap. In operation, AMR sensors of the AMR sensor assemblies 1410(1) and 1410(2) and 1412(1) and 1412(2) measure rotation of a corresponding magnet in proximity thereto.

In FIG. 14, a magnet 1418 is shown on an internal surface of the fork driver 1402. Rotation of the magnet 1418 about an axis formed by the AMR sensor of the AMR sensor assembly 1410(1) and the magnet 1418 corresponds to a rotational axis of a trunnion of the cross 1414. In other words, as the magnet 1418, which is positioned in proximity to an AMR sensor of the AMR sensor assembly 1410(1) and is fixedly coupled to the cross 1414, rotates about the rotational axis of the trunnion of the cross 1414, the AMR sensor of the AMR sensor assembly 1410(1) detects relative rotational movement between the AMR sensor and the magnet 1418, such relative movement being indicative of flapping about the rotational axis of the trunnion of the cross 1414. The AMR sensor assembly 1410(2) and a corresponding magnet (not shown) operate in similar fashion.

In similar fashion, a magnet 1426 is shown on an internal surface of the drive plate 1404. Rotation of the magnet 1426 about an axis formed by the AMR sensor of the AMR sensor assembly 1412(1) and the magnet 1426 corresponds to a rotational axis of a trunnion of the cross 1414. In other words, as the magnet 1426, which is positioned in proximity to an AMR sensor of the AMR sensor assembly 1412(2) and is fixedly coupled to the cross 1414, rotates about the rotational axis of the trunnion of the cross 1414, the AMR sensor of the AMR sensor assembly 1412(2) detects relative rotational movement between the AMR sensor and the magnet 1426, such relative rotational movement being indicative of flapping about the rotational axis of the trunnion of the cross 1414. The AMR sensor assembly 1412(1) and a corresponding magnet (not shown) operate in similar fashion.

FIG. 15 is a perspective view of a fork driver and associated components. In FIG. 15, a perspective view of the fork driver 1402 is shown. The AMR sensor assemblies 1410(1) and 1410(2) are also shown. As described above, the AMR sensor assemblies 1410(1) and 1410(2) are positioned so as to detect rotational movement of corresponding trunnions, for example, of the cross 1414 (not shown). The brackets illustrated in FIG. 15 that support the AMR sensor assemblies 1410(1) and 1410(2) are shown as supported by a ring assembly 1500 that is fixedly coupled to the rotor mast 200 and includes a ring 1501 and arms 1502(1) and 1502(2) extending therefrom on opposite sides of the rotor mast 200. Thus, the fork driver 1402 and the AMR sensor assemblies 1410(1) and 1410(2) rotate about the rotor mast 200 in unison.

FIG. 16 is a bottom perspective view of the drive plate 1404 and associated components of the rotor hub 1400. A bracket holding the AMR sensor assembly 1412(2) is shown. The cross 1414 is not shown for purposes of clarity. FIG. 17 is a cross-sectional plan view of the rotor hub 1400. The cross-section passes through the rotational axes of four trunnions of the cross 1414, respective trunnions 1415(1)-(4) being shown arranged in 90° azimuthal increments in a plane perpendicular to the main-rotor axis 114 such that no flapping out of the plane is occurring. A rotational axis A and a rotational axis B are shown perpendicular to one another.

The drive plate 1404 has coupled thereto on opposite sides thereof a magnet 1418(1) and a magnet 1418(2) and an AMR sensor assembly 1410(1) and an AMR sensor assembly 1410(2), respective opposing components being associated with one of the trunnions 1415(1) or 1415(3). Thus, rotation of the trunnions 1415(1) and 1415(3) about the axis A may be detected.

In similar fashion, the fork driver 1402 has coupled thereto on opposite sides thereof a magnet 1426(1) and a magnet 1426(2) and an AMR sensor assembly 1412(1) and an AMR sensor assembly 1412(2), respective opposing components being associated with one of the trunnions 1415(2) or 1415(4). Thus rotation of the trunnions 1415(2) and 1415(4) about the axis B may be detected.

Those having skill in the art will recognize that as few as one AMR sensor assembly and magnet may be utilized and that four or more AMR sensor assemblies and magnets may be utilized depending upon design objectives.

Those having skill in the art will appreciate that principles set forth herein can be applied to either teetering rotor hubs or gimballed rotor hubs. The term “substantially” is defined as largely but not necessarily wholly what is specified(and includes what is specified; e.g., substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by a person of ordinary skill in the art. In any disclosed embodiment, the terms “substantially,” “approximately,” “generally,” and “about” may be substituted with “within 10% of” what is specified.

For purposes of this patent application, the term computer-readable storage medium encompasses one or more tangible computer-readable storage media possessing structures. As an example and not by way of limitation, a computer-readable storage medium may include a semiconductor-based or other integrated circuit(IC)(such as, for example, a field-programmable gate array(FPGA) or an application-specific IC(ASIC)), a hard disk, an HDD, a hybrid hard drive(HHD), an optical disc, an optical disc drive(ODD), a magneto-optical disc, a magneto-optical drive, a floppy disk, a floppy disk drive(FDD), magnetic tape, a holographic storage medium, a solid-state drive(SSD), a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, a flash memory card, a flash memory drive, or any other suitable tangible computer-readable storage medium or a combination of two or more of these, where appropriate.

Particular embodiments may include one or more computer-readable storage media implementing any suitable storage. In particular embodiments, a computer-readable storage medium implements one or more portions of a controller as appropriate. In particular embodiments, a computer-readable storage medium implements RAM or ROM. In particular embodiments, a computer-readable storage medium implements volatile or persistent memory. In particular embodiments, one or more computer-readable storage media embody encoded software.

In this patent application, reference to encoded software may encompass one or more applications, bytecode, one or more computer programs, one or more executables, one or more instructions, logic, machine code, one or more scripts, or source code, and vice versa, where appropriate, that have been stored or encoded in a computer-readable storage medium. In particular embodiments, encoded software includes one or more application programming interfaces(APIs) stored or encoded in a computer-readable storage medium. Particular embodiments may use any suitable encoded software written or otherwise expressed in any suitable programming language or combination of programming languages stored or encoded in any suitable type or number of computer-readable storage media. In particular embodiments, encoded software may be expressed as source code or object code. In particular embodiments, encoded software is expressed in a higher-level programming language, such as, for example, C, Python, Java, or a suitable extension thereof. In particular embodiments, encoded software is expressed in a lower-level programming language, such as assembly language(or machine code). In particular embodiments, encoded software is expressed in JAVA. In particular embodiments, encoded software is expressed in Hyper Text Markup Language(HTML), Extensible Markup Language(XML), or other suitable markup language.

Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether(e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. Although certain computer-implemented tasks are described as being performed by a particular entity, other embodiments are possible in which these tasks are performed by a different entity.

Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, the processes described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of protection is defined by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

	Number	Date	Country
Parent	17555024	Dec 2021	US
Child	18115213		US
Parent	17555104	Dec 2021	US
Child	18115213		US

ANISOTROPIC MAGNETO-RESISTIVE SENSOR FLAP MEASURING ON GIMBALLED HUB

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Continuation in Parts (2)