The present invention relates to user interface systems and, more particularly, to a passive haptic feedback system for a user interface, such as a pilot controlled side stick.
Aircraft typically include a plurality of flight control surfaces that, when controllably positioned, guide the movement of the aircraft from one destination to another. The number and type of flight control surfaces included in an aircraft may vary, but typically include both primary flight control surfaces and secondary flight control surfaces. The primary flight control surfaces are those that are used to control aircraft movement in the pitch, yaw, and roll axes, and the secondary flight control surfaces are those that are used to influence the lift or drag (or both) of the aircraft. Although some aircraft may include additional control surfaces, the primary flight control surfaces typically include a pair of elevators, a rudder, and a pair of ailerons, and the secondary flight control surfaces typically include a plurality of flaps, slats, and spoilers.
The positions of the aircraft flight control surfaces are typically controlled using a flight control surface actuation system. The flight control surface actuation system, in response to position commands that originate from either the flight crew or an aircraft autopilot, moves the aircraft flight control surfaces to the commanded positions. In most instances, this movement is effected via actuators that are coupled to the flight control surfaces.
Typically, the position commands that originate from the flight crew are supplied via some type of input control mechanism. For example, many aircraft include two yoke and wheel type of mechanisms, one for the pilot and one for the co-pilot. Either mechanism can be used to generate desired flight control surface position commands. More recently, however, aircraft are being implemented with side stick type mechanisms. Most notably in aircraft that employ a fly-by-wire system. Similar to the traditional yoke and wheel mechanisms, it is common to include multiple side sticks in the cockpit, one for the pilot and one for the co-pilot.
Most side sticks are implemented with some type of feedback mechanism for providing force feedback (or “haptic feedback”) to the user, be it the pilot or the co-pilot. In some implementations, the haptic feedback mechanism is an active mechanism that includes one or more electrically controlled motors to supply force feedback to the side stick(s), and in other implementations the haptic feedback mechanism is a passive mechanism that includes one or more springs to supply force feedback to the side stick(s), in still other implementations the haptic feedback mechanism includes both active and passive mechanisms. In the latter implementations the active mechanism is a primary mechanism and includes one or more electrically controlled motors to supply the force feedback, while the passive mechanism is a backup mechanism and includes one or more tension springs.
Presently known passive feedback mechanisms, whether used as primary or backup feedback mechanisms, while useful, can present certain drawbacks. In particular, presently used passive feedback mechanisms may be overly large to meet desired performance characteristics. For example, in many implementations it is desirable that the passive mechanisms provide different force gradients for different side stick movement directions. Moreover, the passive mechanisms may need to supply a particular preload or breakout force from the side stick null position, an increasing linear force between the null and maximum position, and no reduction in the established breakout force as the side stick passes through the null position.
Hence, there is a need for a passive haptic feedback mechanism for a user interface such as, for example, an active pilot control stick, that can provide different force gradients for different user interface movement directions, and/or can supply a particular preload or breakout force from a null position, and/or an increasing linear force between the null and maximum position, and/or no reduction in the established breakout force as the user interface passes through the null position. The present invention addresses one or more of these needs.
In one embodiment, and by way of example only, a user interface system includes a user interface and a plurality of torsion bars. The user interface is configured to rotate, from a null position, about two perpendicular rotational axes. The user interface is adapted to receive an input force and, in response to the input force, to rotate, from the null position to a control position, about one or both of the rotational axes in a rotational direction. The plurality of torsion bars are coupled to the user interface and include two or more torsion bars disposed along a first one of the rotational axes and two or more torsion bars disposed along a second one of the rotational axes. Each torsion bar is configured to selectively supply a feedback force to the user interface that opposes the rotational direction and that varies as a function of the control position and the rotational direction.
In yet another exemplary embodiment, a user interface system includes a user interface, a torsion bar, and a preload force adjustment mechanism. The user interface is configured to rotate, from a null position, about a rotational axis. The user interface is adapted to receive an input force and, in response to the input force, to rotate, from the null position to a control position, about the rotational axis. The torsion bar is coupled to, and is configured to supply a preload force to, the user interface when the user interface is in the null position. The preload force adjustment mechanism is disposed adjacent to, and is configured to adjust the preload force of, the torsion bar.
In still another exemplary embodiment, an aircraft flight control surface actuation haptic feedback system includes a flight control stick, a motor control unit, a plurality of motors, and a plurality of torsion bars. The flight control stick is configured to rotate, from a null position, about two perpendicular rotational axes. The flight control stick is adapted to receive an input force supplied by a pilot and is configured, in response to the input force, to rotate, from the null position to a control position, about one or both of the rotational axes in a rotational direction. The motor control unit is operable to selectively supply motor feedback signals. The plurality of motors are coupled to the flight control stick. Each motor is further coupled to receive the selectively supplied motor feedback signals and is operable, upon receipt thereof, to supply a variable feedback force to the flight control stick that opposes the rotational direction. The plurality of torsion bars are coupled to the user interface, and include two or more torsion bars disposed along a first one of the rotational axes and two or more torsion bars disposed along a second one of the rotational axes. Each torsion bar is configured to selectively supply a feedback force to the user interface that opposes the rotational direction and that varies as a function of the control position and the rotational direction.
Other independent features and advantages of the preferred user interface system will become apparent from the following detailed description, taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
The present invention will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and
The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. Furthermore, there is no intention to be bound by any theory presented in the preceding background or the following detailed description. In this regard, although the user interface is depicted and described herein as being implemented in an aircraft, and more specifically in an aircraft flight control surface actuation system, the user interface could also be implemented in numerous other environments and systems.
Turning first to
The primary flight control surfaces 102-106 control aircraft movements about the aircraft pitch, yaw, and roll axes. Specifically, the elevators 102 are used to control aircraft movement about the pitch axis, the rudder 104 is used to control aircraft movement about the yaw axis, and the ailerons 106 control aircraft movement about the roll axis. It is noted, however, that aircraft movement about the yaw axis can also be achieved by varying the thrust levels from the engines on opposing sides of the aircraft 100. It will additionally be appreciated that the aircraft 100 could include horizontal stabilizers (not shown).
The secondary control surfaces 108-114 influence the lift and drag of the aircraft 100. For example, during aircraft take-off and landing operations, when increased lift is desirable, the flaps 108 and slats 112 may be moved from retracted positions to extended positions. In the extended position, the flaps 108 increase both lift and drag, and enable the aircraft 100 to descend more steeply for a given airspeed, and also enable the aircraft 100 get airborne over a shorter distance. The slats 112, in the extended position, increase lift, and are typically used in conjunction with the flaps 108. The spoilers 114, on the other hand, reduce lift and when moved from retracted positions to extended positions, which is typically done during aircraft landing operations, may be used as air brakes to assist in slowing the aircraft 100.
The flight control surfaces 102-114 are moved to commanded positions via a flight control surface actuation system 200, an exemplary embodiment of which is shown in
Before proceeding further, it is noted that the flight control surface actuation system 200 additionally includes a plurality of secondary control surface actuators, such as flap actuators, slat actuators, and spoiler actuators. However, the operation of the secondary flight control surfaces 108-114 and the associated actuators is not needed to fully describe and enable the present invention. Thus, for added clarity, ease of description, and ease of illustration, the secondary flight control surfaces and actuators are not depicted in
Returning now to the description, the flight control surface actuation system 200 may additionally be implemented using various numbers and types of primary flight control surface actuators 204-208. In addition, the number and type of primary flight control surface actuators 204-208 per primary flight control surface 102-106 may be varied. In the depicted embodiment, however, the system 200 is implemented such that two primary flight control surface actuators 204-208 are coupled to each primary flight control surface 102-106. Moreover, each of the primary flight control surface actuators 204-208 are preferably a linear-type actuator, such as, for example, a ballscrew actuator. It will be appreciated that this number and type of primary flight control surface actuators 204-208 are merely exemplary of a particular embodiment, and that other numbers and types of actuators 204-208 could also be used.
No matter the specific number, configuration, and implementation of the control units 202 and the primary flight control surface actuators 204-208, the control unit 202 is configured to receive aircraft flight control surface position commands from one or more input control mechanisms. In the depicted embodiment, the system 200 includes two user interfaces, a pilot user interface 210-1 and a co-pilot user interface 210-2, and one or more motor control units 212. As will be described in more detail below, the pilot 210-1 and co-pilot 210-2 user interfaces are both implemented as flight control sticks. It will be appreciated that in some embodiments, the system 200 could be implemented with more or less than this number of flight control sticks 210. It will additionally be appreciated that the system could be implemented with more than one motor control unit 212, and that each flight control unit 202 and each motor control unit 212 could be integrated into a single device. Nonetheless, the motor control unit 212, in response to position signals supplied from one or both flight control sticks 210, supplies flight control surface position signals to the flight control unit 202. The flight control unit 202, in response to the flight control surface position signals, supplies power to the appropriate primary flight control surface actuators 204-208, to move the appropriate primary flight control surfaces 102-106 to positions that will cause the aircraft 100 to implement the commanded maneuver. As depicted in phantom in
Turning now to
Returning once again to
As
The system 200, in addition to using the motors 318 to supply active haptic feedback to the pilot and/or co-pilot, includes a plurality of passive feedback mechanisms associated with each control stick 210. In the depicted embodiment the passive feedback mechanisms are each configured to passively supply haptic feedback to the flight control sticks 210 in the unlikely event the associated motors 318, the motor control unit 212, or various other electrical components become inoperable and prevent, or at least inhibit, active feedback. It will be appreciated, however, that in alternative embodiments, the system 200 may be configured without the motors 318, and include only the passive feedback mechanisms to supply haptic feedback. In either instantiation, the passive feedback mechanisms are implemented using a plurality of torsion bars 326. Each torsion bar 326 is coupled to its associated user interface 210, with two or more torsion bars 326 disposed along the pitch axis 222 and two or more torsion bars 326 disposed along the roll axis 224. As was just eluded to, each torsion bar 326 is configured to selectively supply a feedback force to its associated flight control stick 210 that opposes the rotational movement direction of the associated flight control stick 210 and that varies as a function of the control position and the rotational direction. To more fully explain how the torsion bars 326 are configured to provide this functionality, a more detailed description of at least a portion of the gimbal assemblies 302 will now be provided.
Referring now to
Before proceeding further it is noted that, for clarity and ease of depiction, the active feedback motors 318, gear sets 322, and position sensors 308 are not depicted in
Returning once again to the description, and with continued reference to
Referring now to
As shown in
The torsion bar retainer mechanism 706, which may also be implemented using any one of numerous suitable devices, such as a threaded screw-type device, retains the preload force supplied by the torsion bar 326 to the user interface 210 when the torsion bar 326 is in its null position. Although this may be accomplished using any one of numerous suitable configurations, in the depicted embodiment it is seen that the torsion bar 326 further includes a retainer tang 614, which extends through a groove 712 formed in the torsion bar drive housing 601. The torsion bar retainer mechanism 706 engages the torsion bar retainer tang 614 when the torsion bar 326 is in its null position, thereby retaining the preload force supplied by the torsion bar 326.
Turning now to
The passive centering and haptic feedback system described herein for use in conjunction with a user interface independently provides rotational resistance in a plurality of rotational directions. The system provides for the setting and adjustment of a preload force to the user interface, for retaining the set preload force, for passively returning the user interface to its null position, and for preventing each passive mechanism from introducing additional force into adjacent vectors. The system additionally enables the spring gradients in one or both rotational directions about one or both perpendicular axes to be different, and for the preload forces to be set in dependence upon the direction the user interface is moved relative to both axes.
While at least one exemplary embodiment has been presented in the foregoing detailed description of the invention, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an exemplary embodiment of the invention. It being understood that various changes may be made in the function and arrangement of elements described in an exemplary embodiment without departing from the scope of the invention as set forth in the appended claims.