Broadband haptic system

Abstract

A broadband haptic system for a controller of a controller system to provide enhanced haptic functionality is described herein. A control, such as a touchpad, of the controller may include a cover, a circuit board disposed behind and coupled to the cover, a haptic actuator mounted to the circuit board, and a spring disposed behind the cover, the spring coupled to the cover, and mounted to a housing of the controller. The haptic actuator is configured to vibrate, and the spring is configured to bidirectionally deflect in response to the vibration of the haptic actuator. Further, the haptic actuator has a first resonant frequency, and the control has a second resonant frequency different from the first resonant frequency to provide a broadband haptic system for the controller.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Patent Application Serial No. 18 / 450,262, filed August 15, 2023, which is incorporated herein by reference in its entirety. Background Technology

[0002] Handheld controllers are used in arrays of architectures that provide input to, for example, local or remote computing devices. For instance, handheld controllers are used in the gaming industry to allow players to interact with gaming applications running on computing devices such as game consoles, game servers, and the handheld controller itself. Furthermore, to simulate the sensation of touch and motion, some handheld controllers are configured to provide haptic feedback to the user. Many haptic systems utilize single-resonant haptic actuators, such as linear resonant actuators (LRAs) with a single resonant frequency. These haptic systems are only capable of providing a limited range of haptic feedback.

[0003] The content disclosed in this article is presented in relation to these and other considerations. Attached Figure Description

[0004] Specific embodiments are described with reference to the accompanying drawings. In the drawings, the leftmost numeral of the reference numeral indicates the drawing in which the reference numeral first appears. Identical or similar reference numerals in different drawings indicate similar or identical items.

[0005] Figure 1A This example shows a perspective view of a touchpad-style control, which is in... Figure 1A It is shown in an upright orientation.

[0006] Figure 1B Examples Figure 1A The perspective of the example control, which is in... Figure 1B The orientation is shown in reverse.

[0007] Figure 1C Examples Figure 1A Another perspective of the example control, which is in Figure 1C The orientation is shown in reverse.

[0008] Figure 1D Examples Figure 1C A perspective breakdown of the example control.

[0009] Figure 1E Examples Figure 1A The front view of the example control.

[0010] Figure 1F Examples Figure 1A The back view of the example control.

[0011] Figure 1G Examples Figure 1A The side view of the example control.

[0012] Figure 1H Examples Figure 1A The other side view of the example control.

[0013] Figure 2 Examples Figure 1A The example control is shown as a Bode plot of its impedance magnitude, which is a proxy for the vibrational acceleration of the control during actuation of the control's haptic actuator.

[0014] Figure 3 Examples Figure 1A The example control's offset is a Bode plot, which is another alternative indicator of the control's vibrational acceleration during the actuation of the control's haptic actuator.

[0015] Figure 4A Examples Figure 1A The example control is the back view of a spring.

[0016] Figure 4B Examples Figure 4A Example front view of a spring.

[0017] Figure 4C Examples Figure 4A A side view of an example spring.

[0018] Figure 5A The example controller is shown in the rear view, where the rear panel of the controller housing has been removed to show the example control mounted to the housing.

[0019] Figure 5B Examples Figure 5A A magnified view of one of the controls shown.

[0020] Figure 6 The example view shows a sample controller with sample controls for user finger operation.

[0021] Figure 7 Example functional components of the example controller system are illustrated. Detailed Implementation

[0022] As mentioned above, handheld controllers are used in a range of environments and include a range of functionalities, with some controllers including haptic feedback functionality. However, traditional handheld controllers offer only a limited range of haptic feedback, which can be partly attributed to the relatively narrow operating frequency band of the haptic systems implemented in those controllers.

[0023] This document specifically describes a broadband haptic system for a controller system to provide enhanced haptic functionality. The controller has various controls, at least one of which includes a haptic actuator for providing haptic feedback to a user of the controller. The control with the haptic actuator may further include a spring mounted to the housing of the controller, the spring being configured to deflect bidirectionally in response to vibrations of the haptic actuator. As described in more detail below, this spring-mounted control has a resonant frequency different from the resonant frequency of the haptic actuator itself. By separating the aforementioned resonant frequencies, the operating bandwidth of the haptic system is widened (or broadened), thereby creating a broadband haptic system with improved performance compared to conventional narrowband haptic systems. For example, a controller system having the broadband haptic system disclosed herein can deliver richer haptic signals to a user of the controller. For example, the disclosed broadband haptic system can provide a variety of high-fidelity waveforms to a user of the controller, thereby improving the user experience. Therefore, the broadband haptic system described herein can allow for the provision of a wider range of haptic feedback than its narrowband counterpart. In some instances, the range of tactile feedback types that can be provided by the disclosed broadband tactile system ranges from sharp “ticks” to long rumbles and intermediate types of tactile responses in between.

[0024] In some instances, the controls of the controller disclosed herein can be operated by one or more fingers to participate in a video game via a running video game application, and / or control other types of applications and / or programs. In some cases, the handheld controller may include controls for controlling a game or application running on the handheld controller itself (e.g., a handheld gaming system largely independent of the controller). In some cases, the handheld controller may include controls for controlling remote devices (e.g., televisions, audio systems, personal computing devices, game consoles, vehicles, etc.).

[0025] In some instances, the spring-mounted controls of the controller may be touchpads, or may include touchpads. In some instances, the touchpad is disposed on the front surface of the controller's housing and configured to be operated by the user's thumb when the user (e.g., with both hands) holds the controller. In some instances, the controller includes multiple spring-mounted controls (e.g., multiple spring-mounted touchpads) disposed on the front surface of the housing, each control being operable by the user's thumb and configured to provide haptic feedback to the user holding the controller.

[0026] In some instances, the haptic actuators of the disclosed spring-mounted controls can provide haptic feedback in response to the fulfillment of one or more criteria and / or in response to the occurrence of one or more events. For example, during gameplay of a video game, haptic feedback can be provided via the haptic actuators of the disclosed spring-mounted controls when the player-controlled character is shot by a non-playable character (NPC) in the video game. As another example, the spring-mounted controllers disclosed herein may include various sensors, such as touch sensors, pressure sensors, etc. In these instances, the processor of the controller system can be configured to detect when a force applied to the control meets a threshold and can provide haptic feedback in response to a pressure applied to the control meeting the threshold. These are merely examples of when haptic feedback can be provided to the user as a haptic stimulus (e.g., during gameplay), and depending on the implementation, other criteria may be utilized to provide haptic feedback.

[0027] The disclosed broadband haptic system outperforms conventional narrowband haptic systems because it is configured to deliver richer haptic signals to the user of the controller. In other words, the disclosed broadband haptic system has a wider (or more extensive) operating bandwidth than its narrowband counterpart, thus providing haptic engineers with greater creative freedom and flexibility to program the disclosed controller system to utilize a wider range of haptic feedback responses.

[0028] The disclosed broadband haptic system also offers cost savings for manufacturers of controls and / or controllers that incorporate broadband haptic systems. This is because the haptic actuators utilized in the disclosed spring-mounted controls can be implemented as single-resonant haptic actuators, such as LRAs with a single resonant frequency, which are significantly cheaper than dual-resonant haptic actuators (e.g., LRAs with multiple different resonant frequencies). However, the disclosed broadband haptic system can be utilized in conjunction with such dual-resonant haptic actuators if desired. Therefore, the disclosed broadband haptic system can be implemented with a wider range of haptic actuators, providing controller manufacturers with greater flexibility in designing their haptic systems.

[0029] This disclosure provides a general understanding of the principles of the structure, function, manufacture, and use of the systems and methods disclosed herein. One or more examples of this disclosure are illustrated in the accompanying drawings. Those skilled in the art will understand that the systems and methods specifically described herein and illustrated in the accompanying drawings are non-limiting embodiments. Features illustrated or described in connection with one embodiment may be combined with features of other embodiments, including, as in systems and methods. These modifications and variations are intended to be included within the scope of the appended claims.

[0030] Figures 1A to 1HVarious views of a sample control 100 in the form of a touchpad are illustrated. Control 100 can be implemented in a controller. Instances of controller 600 are shown in... Figure 6 As shown in the figure. If the controller 600 is operated by one or more of the user's hands, the controller 600 can be considered "handheld", regardless of whether the entire controller 600 is supported by the user's hand or held in the user's hand.

[0031] Control 100 is configured to be operated by a finger, such as the finger of a user of controller 600. In this sense, control 100 is configured to receive input from the user of controller 600. Figures 1A to 1H The example control 100 depicted herein takes the form of a touchpad and is configured to at least sense the touch of a finger (e.g., thumb) on the control 100 and / or the proximity of a finger to the control, as well as the movement of a finger across the control 100 when the finger is touching and / or approaching the control 100 (e.g., hovering over the control). However, it should be understood that the control 100 disclosed herein may be implemented as other types of controls besides a touchpad, such as a D-pad, button, trackball, joystick, trigger button, shoulder button, knob, scroll wheel, toggle switch, panel, wingplate, or any other suitable type of control configured to be operated by a finger.

[0032] Figure 1A An illustration shows a perspective view of a control 100 in an upright orientation. The control 100 includes a cover 102. The cover 102, as its name suggests, covers components of the control 100 disposed behind it. Therefore, since the cover 102 is the outward-facing component of the control 100, at least when the control 100 is in an upright orientation, such as... Figure 6 When implemented in the controller 600, the remaining components of the control 100 can be concealed by the cover 102. In some instances, the control 100 and therefore the cover 102 may be configured to be positioned within an opening defined in the housing of the controller, such as the controller 600. An example of the housing 500 of the controller 600 is... Figure 5A and Figure 5B As shown in the diagram. This housing 500 can accommodate the internal components of the controller 600. For example, cover 102 may represent... Figure 6 The visible portions of controls 100(1) and 100(2) (e.g., touchpad) depicted in the image, while the internal components within the housing 500 are... Figure 6The control 100 is not visible in the foreground. Typically, the cover 102 is configured to interact with the control 100 (e.g., hovering over the control, touching the control, pressing the control, etc.) to manipulate the control. For example, a user may touch the cover 102 with a finger (e.g., thumb) and / or drag the finger across the cover 102 to move the cursor on the display 610 of the controller 600, or to control other aspects of an application being executed (e.g., controlling the movement of a player-controlled character and / or aiming a weapon in an ongoing video game). In some instances, the user may manipulate the control 100 by pressing the cover 102 (e.g., applying force to the cover 102 in the negative Z direction). Because the examples herein envision the control 100 being implemented on the front surface 602 of the controller 600, the Z direction shown in the figures is intended to represent a forward (positive Z direction) and a backward (negative Z direction) reference frame. In this sense, components positioned relative to cover 102 in the negative Z direction are referred to as being "behind" cover 102, but it should be understood that in other orientations, these components may be referred to as being "below" cover 102, or even "in front" cover 102, for example, if control 100 is positioned on the rear surface of controller 600.

[0033] Control 100 may further include circuit board 104 (sometimes referred to herein as a “control board” or “touchpad”), which in Figure 1D The control 100 is shown in an exploded perspective view. A circuit board 104 may be disposed behind a cover 102. Typically, the control 100 may comprise a stack or layer of components stacked in a stacking direction (e.g., the Z-direction). It should be understood that... Figures 1B to 1D The stacking direction of the controls 100 shown is reversed. This is why the positive Z direction is... Figures 1B to 1D The middle finger points downwards. Therefore, the cover 102 can be positioned in front of the circuit board 104, regardless of... Figures 1A to 1H The different orientations of the control 100 depicted in the image.

[0034] Circuit board 104 may be coupled to cover 102, for example, by adhesive, by fasteners, or a combination thereof. As used herein, the term “coupled” may refer to indirect or direct coupling between components. As used herein, the term “coupled” may also refer to removable or permanent coupling between components. A component is removably coupled if a user or another entity can decouple it. A component is permanently coupled if a user or another entity cannot decouple it without damaging or significantly harming it, or if it cannot be decoupled in an excessively strenuous manner without the use of tools or mechanical means. As used herein, the term “coupled” may be interpreted as connection, attachment, affixation, combination, engagement, interface, link, fastening, or binding. Unless otherwise stated herein, the term “coupled” will be interpreted as a coupling element in, for example, a mechanical sense, rather than an electrical sense. However, it should be understood that mechanical coupling of components can achieve electrical coupling between multiple components of a system.

[0035] Various components (e.g., electronic components) can be mounted to circuit board 104. At least one of the components mounted to circuit board 104 is a haptic actuator 106. Therefore, haptic actuator 106 can be disposed behind cover 102. In other words, cover 102 can be disposed in front of circuit board 104, and also in front of haptic actuator 106. Although haptic actuator 106 can be mounted on either side of circuit board 104, Figure 1D The illustrated embodiment depicts a haptic actuator 106 mounted on the back of a circuit board 104. The haptic actuator 106 is configured to provide haptic feedback (e.g., through vibration, pulses, etc.). In some instances, the haptic actuator 106 is configured to vibrate in response to a control signal received from a processor of a controller system, as described below. Figure 7 A more detailed description follows. In some instances, control signals for driving the haptic actuator 106 are provided by a processor in response to the satisfaction of one or more criteria and / or the occurrence of one or more events. For example, the processor may be configured to process data (e.g., game state data, user input data, etc.) to determine whether one or more criteria are met, and if so, send control signals to the haptic actuator 106 to drive it to provide haptic feedback. The control signals may specify the gain and / or frequency driving the haptic actuator 106, and the haptic actuator 106 may be configured to vibrate in response to the control signals from the processor, allowing the user to feel haptic vibrations of the cover 102. The haptic actuator 106 may be any suitable type of haptic actuator, including but not limited to LRAs, eccentric rotating mass ERMs, etc. The haptic actuator 106 may be controlled to vibrate or resonate in any suitable direction. Figure 1DIn this example, the vibration direction is shown as the X direction. For instance, when control 100 is implemented on the front surface 602 of controller 600, as... Figure 6 As shown, the haptic actuator 106 can vibrate bidirectionally in the X direction (e.g., from the perspective of the user holding the controller 600, vibrating left and right). In some instances, the haptic actuator 106 is configured to vibrate in multiple different directions, such as in the X, Y, and / or Z directions, as depicted in the figures.

[0036] Control 100 may further include a spring 108 (sometimes referred to herein as a “biasing member” or “suspension mechanism”). The spring 108 is disposed behind the cover 102 and coupled to the cover 102. Reference Figures 4A to 4C Let's discuss the details of the example spring 108 shown in the attached diagram. Figure 4A and Figure 4B As depicted, the spring 108 may include one or more (e.g., a pair) side flanges 400, such as a first side flange 400(1) and a second side flange 400(2), which are used to couple the spring 108 to the cover 102. For example, the first side flange 400(1) may include one or more (e.g., three) holes 402, and the second side flange 400(2) may include one or more (e.g., three) holes 402. These holes 402 may be configured to receive one or more corresponding protrusions 110 extending from the back surface of the cover 102 (see [link to relevant documentation]). Figure 1D ).exist Figures 1A to 1H In some examples, these protrusions 110 extend from the back of the cover 102 at opposite sides 112 of the cover 102. For example, Figures 1B to 1D , Figure 1F ,and Figure 1G Three protrusions 110 are depicted on one side 112(1) of the cover 102, and three other protrusions 110 are depicted on the opposite side 112(2) of the cover 102. Thus, a first side flange 400(1) of the spring 108 can be coupled to the back surface of the cover 102 at the first side 112(1), and a second side flange 400(2) of the spring 108 can be coupled to the back surface of the cover 102 at the second side 112(2) opposite to the first side 112(1). In some instances, an adhesive is used to permanently couple the spring 108 to the cover 102, and / or to ensure that the spring 108 does not accidentally detach from the cover 102 during use of the controller 600 in which the control 100 is located.

[0037] Spring 108 is also mounted to housing 500 of controller 600 (sometimes referred to herein as “frame” or “controller body”), such as Figure 5A and 5BAs illustrated. In some instances, the spring 108 is mounted to the housing 500 via one or more (e.g., multiple) flanges 404. Figures 4A to 4C The example spring 108 depicted includes four flanges 404(1), 404(2), 404(3), and 404(4) at the corners of the spring 108, which are depicted as having a generally rectangular shape. Therefore, these flanges 404 are sometimes referred to herein as “corner flanges.” Figure 4A and Figure 4B As shown, each of the corner flanges 404 may include a hole 406 configured to receive a corresponding protrusion extending from the inner surface of the housing 500. In some instances, an adhesive is used to permanently mount the spring 108 to the housing 500 of the controller 600, and / or to ensure that the spring 108 does not accidentally detach from the housing 500 during use of the controller 600, in which the controls 100 are located.

[0038] Spring 108 is made of a compliant material such as metal (e.g., spring steel). In some instances, spring 108 is manufactured from a single piece of material (e.g., a single piece of spring steel), which can be cut (e.g., machined) and shaped as depicted in the figures. In other words, spring 108 can be implemented as a monolithic spring made of metal (e.g., spring steel).

[0039] Spring 108 further includes one or more (e.g., a pair) elongated spring arms 408 (sometimes referred to herein as “spring bars” or “spring blades”), such as a first elongated spring arm 408(1) and a second elongated spring arm 408(2). Spring 108 may further include a body 410, which may have various features (e.g., openings, holes, fins, protrusions, etc.). In some instances, features of the body 410 of spring 108 allow airflow through the space between spring 108 and circuit board 104, which can help cool electronic components mounted to circuit board 104 by convection. In some instances, the body 410 of spring 108 is rectangular in shape, but other shapes of the body 410 are also possible, and the shape of the body 410 may depend on the type of control 100 in which spring 108 is implemented. For example, if spring 108 is included in a D-pad, the body 410 of spring 108 may have a cross shape, similar to the cross shape of a four-way D-pad.

[0040] like Figures 4A to 4C As shown, a first elongated spring arm 408(1) abuts the body 410 of the spring 108 at a first neck region 412(1). Similarly, a second elongated spring arm 408(2) abuts the body 410 of the spring 108 at a second neck region 412(2), as... Figure 4A and Figure 4B As shown. In some instances, such as Figure 4C As shown, an elongated spring arm 408 protrudes downward (e.g., in the negative Z direction) from the body 410 of the spring 108. In some instances, the side flange 400 extends along opposite sides of the body 410, while the elongated spring arm 408 extends along other opposite sides of the body 410. Thus, when the spring 108 is coupled to the cover 102, the elongated spring arm 408 is adjacent to (and in some cases parallel to) opposite sides 112 of the cover 102. For example, when the spring 108 is coupled to the cover 102, a second elongated spring arm 408(2) may be adjacent to (and parallel to) a third side 112(3) of the cover 102, and a first elongated spring arm 408(1) may be adjacent to (and parallel to) a fourth side 112(4) of the cover 102. As used in this context, "adjacent" can mean "closer to". Therefore, when the spring 108 is coupled to the cover 102, the second elongated spring arm 408(2) is closer to the third side 112(3) of the cover 102 than the fourth side 112(4) of the cover 102 opposite to the third side 112(3), and the first elongated spring arm 408(1) is closer to the fourth side 112(4) of the cover 102 than the third side 112(3) of the cover 102 opposite to the fourth side 112(4).

[0041] like Figure 4CAs illustrated, the elongated spring arm 408 is longer than the length of the neck region 412 (e.g., in the Y direction). In some instances, the lengths of the first neck region 412(1) and the second neck region 412(2) are substantially equal, ranging from about 5 mm to 20 mm. Because the elongated spring arm 408 is longer than the neck region 412, each elongated spring arm 408 includes a pair of cantilevers 414. Each cantilever 414 is fixed at one end to the body 410 at the neck region 412, and extends from the neck region 412. The pair of cantilevers 414 of a given elongated spring arm 408 extend in opposite directions. For example, the first elongated spring arm 408(1) may include a first cantilever 414(1) extending from the first neck region 412(1) in a first direction (e.g., the positive Y direction) and a second cantilever 414(2) extending from the first neck region 412(1) in a second direction opposite to the first direction (e.g., the negative Y direction). Similarly, the second elongated spring arm 408(2) may include a third cantilever 414(3) extending from the second neck region 412(2) in a first direction (e.g., the positive Y direction) and a fourth cantilever 414(4) extending from the second neck region 412(2) in a second direction (e.g., the negative Y direction). These cantilevers 414 are configured to flex or bend at least bidirectionally and move relative to the body 410 of the spring 108. This ability of the cantilevers 414 to flex or bend when the spring 108 is mounted to the housing 500 of the controller 600 allows the spring 108 to deflect at least bidirectionally in response to vibrations of the haptic actuator 106. In some instances, because spring 108 is coupled to cover 102, when haptic actuator 106 vibrates, the vibration is transmitted to circuit board 104 on which haptic actuator 106 is mounted. This causes cover 102 to vibrate (because circuit board 104 is coupled to cover 102), and this vibration of cover 102 causes spring 108 to deflect back and forth (e.g., in the X direction, as...). Figures 1A to 1C (As depicted). This deflection of spring 108 is allowed by the flexing of the cantilever 414 of the elongated spring arm 408. In some instances, the length of the neck region 412 and / or the length of the cantilever 414 (e.g., in the Y direction) partially defines the spring constant K of spring 108. For example, the longer the neck region 412 and / or the shorter the cantilever 414 (e.g., in the Y direction), the stiffer spring 108, and the shorter the neck region 412 and / or the longer the cantilever 414, the more flexible the spring 108. The material of spring 108 and at least the thickness of cantilever 414 also play a role in the spring constant K of spring 108. In any case, the spring constant K, together with the mass of the entire control 100 (e.g., the mass of cover 102, the mass of circuit board 104, and the mass of one or more components mounted to circuit board 104, including haptic actuator 106), defines the resonant frequency of control 100.

[0042] The haptic actuator 106 itself may have a first resonant frequency (also known as the "natural resonant frequency"). For example, if the haptic actuator 106 is implemented as a single resonant LRA comprising a magnet attached to a spring, the resonant frequency of the LRA is defined by the spring constant K (or stiffness) of the spring inside the LRA and the mass of the magnet inside the LRA. Typical resonant frequencies of a single resonant LRA are in the range of approximately 175 Hz to 235 Hz. The resonant frequency of the haptic actuator 106 is the frequency at which the haptic actuator 106 is most efficient in its operation, meaning that for a given amount of input energy, the acceleration output is maximized to drive the haptic actuator 106.

[0043] When the control 100 is mounted to the housing 500 of the controller 600 via the spring 108, as Figure 5A and Figure 5B As depicted, control 100 is suspended within housing 500 by spring 108, and because spring 108 is configured to deflect bidirectionally in response to vibrations of haptic actuator 106, control 100 has its own resonant frequency (second resonant frequency). Specifically, example control 100 has a second resonant frequency different from the first resonant frequency of haptic actuator 106. This second resonant frequency of control 100 can be tuned by manufacturing components of control 100 with a specific mass, and / or by manufacturing spring 108 with a specific spring constant K (or stiffness). In other words, the second resonant frequency of control 100 is defined by the spring constant K (or stiffness) of spring 108, the mass of cover 102, the mass of circuit board 104, and the mass of one or more components, including haptic actuator 106, mounted to circuit board 104. If other components, such as sensors (e.g., touch sensor layers, such as capacitive touch sensing layers), are included in control 100, the mass of those components also affects the second resonant frequency of control 100. For example, a touch sensor layer (e.g., a capacitive sensor array) may be disposed between cover 102 and circuit board 104, the touch sensor having its own mass that influences the second resonant frequency of control 100. Similarly, if a pressure sensor is included in control 100, the mass of the pressure sensor is taken into account in the second resonant frequency. Thus, the mass of any of these components, and / or the spring constant K of spring 108, can be tuned to achieve a desired second resonant frequency of control 100 that differs from the first resonant frequency of the haptic actuator 106 itself. By tuning these resonant frequencies differently, a broadband haptic system is created that combines the single resonance of a potentially inexpensive single-resonant haptic actuator 106 (e.g., an LRA with a single resonant frequency) with the different resonances (e.g., self-resonance) of a spring-mounted control 100 (e.g., a touchpad) to widen the operating bandwidth of the haptic system.

[0044] In some instances, the difference between the first resonant frequency of the haptic actuator 106 and the second resonant frequency of the spring-mounted control 100 is in the range of approximately 70 Hz to 160 Hz. This difference between the first and second resonant frequencies allows the second resonant frequency of the control 100 to be coupled and combined with the first resonant frequency of the haptic actuator 106, and causes the spacing between these resonant frequencies to widen the overall spectrum (or operating bandwidth) of the haptic system. In contrast, if these resonant frequencies were tuned to the same resonant frequency, the operating bandwidth of the haptic system would not be widened (i.e., the operating bandwidth would be narrower than it is achievable), and equivalent resonant frequencies could reinforce each other, causing an unwanted "clicking" sound from the control 100 within the housing 500 whenever the haptic actuator 106 is actuated. To eliminate this unwanted clicking sound, the second resonant frequency of the control 100 can be detuned relative to the first resonant frequency of the haptic actuator 106. Furthermore, by tuning the spring constant K of spring 108, and / or by tuning the mass of components of control 100 (e.g., the mass of cover 102, the mass of circuit board 104, the mass of haptic actuator 106, and / or the mass of one or more other components of control 100, etc.), these resonant frequencies can differ to some extent from each other, widening the operating bandwidth of the haptic system and creating a broadband haptic system capable of providing a wider range of haptic feedback. In some instances, the second resonant frequency of control 100 is “sufficiently different” from the first resonant frequency of haptic actuator 106 if the first and second frequencies differ by at least about 70 Hz. Therefore, the overall resonance of the haptic system disclosed herein has a significantly wider bandwidth compared to the bandwidth created at the same resonant frequency.

[0045] Figure 2 Examples Figure 1A A Bode plot 200 of the impedance amplitude of the example control 100 is provided. Impedance amplitude is a suitable proxy for the vibrational acceleration (haptic response) of the control 100 during actuation of the haptic actuator 106 of the control 100. As shown in Bode plot 200, a first peak 202 in the impedance amplitude occurs at a first frequency of approximately 180 Hz, and a second peak 204 in the impedance amplitude occurs at a second frequency of approximately 300 Hz. In the example Bode plot 200, the second peak 204 is reduced by approximately 9% relative to the first peak 202, which is considered a non-significant reduction in impedance amplitude. These peaks 202 and 204 indicate different resonant frequencies of the broadband haptic system disclosed herein. That is, the first peak 202 may indicate a first resonant frequency of the haptic actuator 106, and the second peak 204 may indicate a second resonant frequency of the control 100. The combination of the two different resonant frequencies gives the entire haptic system a wider bandwidth 206 than its narrowband counterpart.

[0046] Figure 3 A similar broadband effect of the disclosed tactile system is illustrated. Figure 3 Examples Figure 1A The Bode plot of the offset of the example control 100 is 300. Figure 3 The “offset” plotted herein represents the measured displacement (e.g., in the X direction) of control 100 during actuation of the haptic actuator 106 of control 100. Offset is another suitable alternative indicator of the vibrational acceleration (haptic response) of control 100 during actuation of the haptic actuator 106 of control 100. As shown in Bode plot 300, a first peak 302 in the offset occurs at a first frequency of approximately 160 Hz, and a second peak 304 in the offset occurs at a second frequency of approximately 230 Hz. These peaks 302 and 304 indicate different resonant frequencies of the broadband haptic system disclosed herein. That is, the first peak 302 may indicate a first resonant frequency of the haptic actuator 106, and the second peak 304 may indicate a second resonant frequency of control 100. In Bode plot 300, the second peak 304 is larger than... Figure 2 The second peak 204 in Bode plot 200 is more pronounced, and the midpoint offset between peaks 302 and 304 in Bode plot 300 is more pronounced compared to the midpoint impedance magnitude between peaks 202 and 204 in Bode plot 200. In any case, both Bode plots 200 and 300 illustrate a broadband response created using the disclosed haptic system, although the effect may be more pronounced in Bode plot 300. Figure 3 In this system, the combination of two different resonant frequencies gives the entire tactile system a wider bandwidth 306 than its narrowband counterpart.

[0047] Figure 5A An example controller is shown (e.g., Figure 6 The rear view of the controller 600 shown is shown, in which the rear panel of the controller housing 500 is removed to show example controls 100(1) and 100(2) mounted to the housing 500. Figure 5B Examples Figure 5A An enlarged view of control 100(1) is shown. Each of controls 100(1) and 100(2) can represent Figures 1A to 1H The 100 control introduced in [the context]. For example... Figure 5A and Figure 5BAs shown, the spring 108 of each control 100(1), 100(2) is mounted to the housing 500 in a corresponding position (e.g., on the opposite side of the centrally located display 610 of the controller 600). As discussed above, the spring 108 of each control 100(1), 100(2) is coupled to the cover 102 of each control 100(1), 100(2). Thus, these controls 100(1), 100(2) are spring-mounted and are suspended within the housing 500 by their respective springs 108. The spring 108 of each control 100(1), 100(2) is mounted to the housing 500 via corner flanges 404 of the spring 108, which are positioned at the distal ends of elongated spring arms 408. That is, as Figure 4A and Figure 4B As shown, the first elongated spring arm 408(1) may include a first corner flange 404(1) at a first end of the first elongated spring arm 408(1) and a second corner flange 404(3) at a second end of the first elongated spring arm 408(1), and the second elongated spring arm 408(2) may include a third corner flange 404(2) at a first end of the second elongated spring arm 408(2) and a fourth corner flange 404(4) at a second end of the second elongated spring arm 408(2). In some instances, the corner flange 404 may be mounted to a protrusion extending from the inner surface of the housing 500. In this way, the spring 108 is anchored to the housing 500, and when the user properly holds the controller 600, the spring 108 biases the cover 102 (and therefore the control 100) toward the user in a forward direction (e.g., the positive Z direction). In some instances, a portion of the cover 102 (e.g., a lip surrounding the periphery of the cover 102) may be abutted against the inner surface of the housing 500 by a spring 108 and biased within an opening in the housing 500, allowing a user to access (e.g., touch, press, etc.) the control 100 from the outside without “pushing” the control 100 out of the housing 500. In other words, because the corresponding opening in the housing 500 is slightly smaller than the area of ​​the cover 102 including the peripheral lip of the cover 102, the peripheral lip surrounding the cover 102 can hold the control 100 within the housing 500.

[0048] Spring 108 may be configured to deflect and / or deform in response to an object (e.g., a finger) pressing on cover 102, and return to its original form and / or position when pressure on cover 102 ceases (e.g., when the finger is removed from cover 102, or pressure is no longer applied to the cover). In other words, spring 108 may be configured to apply a biasing force on cover 102 in the direction opposite to the direction of the force applied by the user of control 100 and / or controller 600 to cover 102. In some instances, spring 108 applies a forward biasing force (e.g., a biasing force in the positive Z direction) on cover 102 from opposite sides 112(1), 112(2) to provide a balanced forward biasing force on cover 102 (and therefore control 100). In some instances, spring 108 may have anisotropic characteristics that optimize the force of spring 108 on cover 102 in orthogonal directions. For example, the bias force in the positive Z direction can be optimized for pressing on the cover 102, and the bias force in the X direction (and / or Y direction) can be optimized for vibration of the haptic actuator 106. Again, the vibration of the haptic actuator 106 causes the circuit board 104 to vibrate, which in turn causes the cover 102 to vibrate, which in turn causes the spring 108 to deflect bidirectionally to provide haptic feedback. Thus, the cover 102 is biased against the inner surface of the housing 500 in the forward (e.g., positive Z) direction so that the user can press the control 100 (e.g., touchpad), and the spring 108 will allow a certain amount of deflection in the rearward (e.g., negative Z) direction, while the spring 108 (and in particular the spring arm 408) further allows the control 100 to vibrate laterally, or in a plane with respect to the surface of the controller housing 500 (e.g., front surface 602) (e.g., in the X direction).

[0049] In the example described herein, the haptic actuator 106 is configured to vibrate laterally (e.g., in the X direction). When the spring 108 of each control 100 is mounted to the housing 500, the elongated spring arm 408, and in particular its cantilever 414, allows the spring 108 to deflect bidirectionally as the suspended control 100 moves back and forth laterally (e.g., in the X direction) along the same vibration axis of the haptic actuator 106 (see [link to documentation]). Figure 1D As noted above, the mass of cover 102, the mass of circuit board 104, and the mass of components mounted to circuit board 104 (e.g., the mass of haptic actuator 106) constitute the total mass of control 100. This total mass, combined with the compliance (or stiffness) of spring 108 (e.g., the combined compliance of elongated spring arm 408), forms a resonant system, referred herein to as the resonant frequency of control 100. By tuning the compliance of spring 108 and the total mass of the components of control 100, the resonant frequency of control 100 can be tuned to a different frequency than the resonant frequency of haptic actuator 106 itself, as shown below. Figure 2 and Figure 3As indicated by Bode plots 200 and 300. This creates a broadband haptic system (sometimes referred to in this paper as a "broadband coupled resonant system").

[0050] The disclosed broadband haptic system outperforms its narrowband counterpart and offers broadband haptic response at a fraction of the cost of other systems—which, while promising similar versatility in haptic response, employ more complex and expensive haptic actuators. The broadband haptic response of the disclosed haptic system is achieved by widening the operating bandwidth of the haptic system (e.g., in...). Figure 2 and Figure 3 The bandwidths 206 and 306 shown are implemented. In other words, the haptic actuator 106 (with its own resonant frequency) is coupled and combined with the suspended control 100 (with its own but different resonant frequency). In some instances, this relatively wide bandwidth can allow for the generation of more complex haptic signals (e.g., square waves) in the haptic response. Thus, haptic feedback can be provided as a very tight “tick” rather than being limited to one type of haptic response (e.g., a longer rumbling vibration). Therefore, the disclosed broadband haptic system can provide haptic engineers with more creative freedom to create a wide range of haptic feedback responses.

[0051] Figure 6 A front view of an example controller 600 is shown, illustrating example controls 100(1) and 100(2) for operation by a user's finger. (See above regarding...) Figure 5A and Figure 5B Each of the controls 100(1) and 100(2) mentioned above can represent Figures 1A to 1H The control 100 introduced herein. According to the various embodiments described herein, the terms "device", "handheld device", "handheld gaming device", "handheld console", "handheld gaming console", "controller", and "handheld controller" are used interchangeably herein to describe any device in which the control 100 may be implemented, such as controller 600.

[0052] The housing 500 of the controller 600 can have various surfaces, including a front surface 602 (or front side), a rear surface (or back side), a top surface (or top edge, or top), a bottom surface (or bottom edge, or bottom), a left surface (or left edge, or left side), and a right surface (or right edge, or right side). Therefore, the housing 500 can be a cuboid. Compared to the top, bottom, left, and right surfaces of the housing 500, the front surface 602 and the rear surface (… Figure 6 (Not shown in the image) can be a relatively large surface.

[0053] like Figure 6As illustrated, the front surface 602 of the housing 500 may include a plurality of controls configured to receive user input. Touch data generated by the controls can be used to detect the presence, position, and / or gesture of a user's fingers operating the controller 600. In some cases, the front surface 602 of the housing 500 may include one or more front surface controls that can be controlled by one or more thumbs of a user operating the controller 600. The handheld controller 600 may further include one or more top surface controls residing on the top surface (or top edge) of the housing 500. Additionally or alternatively, the handheld controller 600 may include one or more rear surface controls residing on the rear surface of the housing 500 and operable by the fingers of a user's left and / or right hand. Additionally or alternatively, the handheld controller 600 may include one or more left surface controls and / or right surface controls residing on respective left and right surfaces of the housing 500.

[0054] Controls 100(1) and 100(2) are shown as exemplary front surface controls in the form of touchpads. The front surface controls may further include one or more trackballs, joysticks, buttons, D-pads, etc. For example, in addition to the left control 100(1) (e.g., the left touchpad), the front surface 602 may include a left joystick 604(1) and / or a left D-pad 606 controllable by a user's left thumb. In some embodiments, the front surface 602 may include an additional left button controllable by the left thumb. In addition to the right control 100(2) (e.g., the right touchpad), the front surface 602 may also include a right joystick 604(1) and / or one or more right buttons 608 (e.g., X, Y, A, and B buttons) controllable by a user's right thumb. In some embodiments, the front surface 602 may include an additional right button controllable by the right thumb. In some instances, the front surface 602 may include other controls such as tilt buttons, trigger buttons, knobs, scroll wheels, levers, panels, and / or wingplates, and multiple controls may be configured to receive input from any combination of the user's thumb and / or fingers.

[0055] In some embodiments, controls 100(1) and 100(2) are each implemented as a quadrilateral-shaped touchpad. For example, controls 100(1) and 100(2) may be implemented as a generally square-shaped touchpad. Furthermore, the quadrilateral-shaped controls 100(1) and 100(2) may have rounded corners. Additionally, as Figure 6As shown, the straight side edges of each control 100(1), 100(2) are aligned (e.g., parallel) with the side (e.g., left and right) edges of the display 610 at the center of the housing 500 on the front surface 602 of the housing 500. Compared to a circular touchpad, the quadrilateral-shaped controls 100(1), 100(2) (e.g., touchpads) provide additional space at the corners that can be reached by the user's fingers (e.g., thumbs). Therefore, the quadrilateral-shaped controls 100(1), 100(2) (e.g., touchpads) are more ergonomic than circular touchpads due to the additional area provided by the controls 100(1), 100(2) (e.g., touchpads). For example, the quadrilateral shape of the controls 100(1), 100(2) (e.g., touchpads) allows the user to reorient their hand on the controller 600 and still reach the controls 100(1), 100(2) (e.g., touchpads) with their thumb. Additionally or alternatively, the user may choose to grip the controller 600 in a slightly different manner, such that the corners of the control 100 (e.g., a touchpad) are used like the north, south, east, and west portions of the touchpad (e.g., like a diamond-shaped touchpad).

[0056] The housing 500 may further include a left handle 612(1) and a right handle 612(2), through which a user can hold the controller 600 via the user's right and left hands, respectively. Holding the left handle 612(1) in the left hand provides access to the left control (e.g., left control 100(1)), and holding the right handle 612(2) in the right hand provides access to the right control (e.g., right control 100(2)).

[0057] The top of the housing 500 may include one or more controls, such as a left trigger button, shoulder button, or button, and / or a right trigger button, shoulder button, or button. These top surface controls can be controlled by the user's index finger during normal operation while the controller 600 is held by the user. In some instances, the top of the housing 500 may include a wired communication interface (e.g., port, plug, jack, etc.) and / or a power port for coupling the controller 600 to an external device (e.g., charger, game console, monitor, computing device, etc.). The back of the housing 500 may include controls that can be easily manipulated by the user's index or middle finger. In some cases, the back of the housing 500 may include a portion that can be pressed to control one or more lower buttons within the controller 600.

[0058] The handheld controller 600 allows for different arrangements or functionalities to modify its configuration to meet the needs of various applications (e.g., game titles), users, etc. For example, a user can select which controls to use based on the currently running game application. Therefore, the user can configure the handheld controller 600 to operate with certain controls based on certain needs and / or preferences. In some cases, the handheld controller 600 can be dynamically configured based on which user is currently operating it. Furthermore, in some cases, the handheld controller 600 or a remote system can determine its configuration and which controls are currently being operated or are capable of being operated. This information can be provided to the system executing the current application, which can then modify it based on the handheld controller's configuration.

[0059] Figure 7 Example functional components of the example controller system 700 are illustrated. For example... Figure 7 As shown, the controller system 700 may include communication ground coupling to Figure 6 One or more remote systems and / or devices 701 of a handheld controller 600, the handheld controller 600 itself including one or more controls 100, as described in detail above. Figure 7 As illustrated, controller 600 includes one or more input / output (I / O) devices 702, such as controls 100, 604, 606, and 608 described above, and potentially any other type of input or output device. For example, I / O device 702 may include one or more microphones to receive audio input, such as user voice input. In some implementations, one or more cameras or other types of sensors (e.g., inertial measurement units, IMUs) may be used as input devices to receive gesture input, such as movement of the handheld controller 600. In some embodiments, additional input devices may be provided in the form of a keyboard, keypad, mouse, touchscreen, joystick, control buttons, etc. Input devices may further include control mechanisms, such as basic volume control buttons for increasing / decreasing volume, and power and reset buttons.

[0060] Simultaneously, the output devices may include a display 610, an optical element (e.g., an LED), a vibrator for creating tactile sensations (e.g., a tactile actuator 106 included in control 100), speakers 614(1), 614(2), headphones, etc. Simple optical elements (e.g., LEDs) may also be present to indicate states, such as, for example, a power-on state and / or a functional (e.g., mode) state of the controller. While several examples have been provided, controller 600 may additionally or alternatively include any other type of output device.

[0061] In some cases, the output of one or more output devices may be based on input received by one or more input devices. For example, selection of control 100 may result in a haptic response being output by a vibrator of control 100 (e.g., haptic actuator 106), or at any other location within the housing 500 of controller 600. In some cases, the output may be at least partially based on the characteristics of touch input on a touch sensor, such as a touch sensor associated with a control. For example, touch input at a first location on the touch sensor may result in a first haptic output, while touch input at a second location on the touch sensor may result in a second haptic output. Furthermore, a specific gesture on the touch sensor may result in a specific haptic output (or other types of output). For example, a swipe gesture on the control may result in a first type of haptic output, while a tap on the control (detected by the touch sensor) may result in a second type of haptic output, and a hard press on the control may result in a third type of haptic output. Additionally, certain controls or portions of controls may be illuminated based on received input.

[0062] Furthermore, the handheld controller 600 may include one or more communication interfaces 704 to facilitate wireless connectivity to a network and / or to one or more remote systems and / or devices 701 (e.g., host computing devices executing applications, game consoles, etc.). The communication interface 704 may implement one or more of various wireless technologies, such as Wi-Fi, Bluetooth, radio frequency (RF), etc. It should be understood that the handheld controller 600 may further include physical ports to facilitate wired connections to a network, connected peripheral devices, or plug-in network devices communicating with other wireless networks.

[0063] In the illustrated embodiments, the handheld controller 600 further includes one or more processors 706 and a computer-readable medium 708. In some embodiments, the processor 706 may include a central processing unit (CPU), a graphics processing unit (GPU), both a CPU and a GPU, a microprocessor, a digital signal processor, or other processing units or components known in the art. Alternatively or additionally, the contents functionally described herein may be performed at least in part by one or more hardware logic components. Examples, but not limited to, exemplary types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), etc. Additionally, each processor in the processor 706 may have its own local memory, which may also store program modules, program data, and / or one or more operating systems.

[0064] Computer-readable medium 708 may include volatile and non-volatile memory, removable and non-removable media implemented by any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Such memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory or other memory technologies, compact disk ROM (CD-ROM), digital versatile disks (DVD) or other optical storage devices, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, redundant array of independent disks (RAID) storage systems, or any other medium that can be used to store desired information and is accessible by a computing device. Computer-readable medium 708 may be implemented as a computer-readable storage media (CRSM), which may be any available physical medium accessible by processor 706 to execute instructions stored on computer-readable medium 708. In one basic implementation, CRSM may include RAM and flash memory. In other implementations, the CRSM may include, but is not limited to, ROM, EEPROM, or any other tangible medium that can be used to store desired information and can be accessed by the processor 706.

[0065] Several modules, such as instructions and data repositories, may be stored in computer-readable medium 708 and configured to execute on processor 706. Several example functional modules are shown stored in computer-readable medium 708 and executed on processor 706, although the same functionality may alternatively be implemented in hardware, firmware, or as a system on a chip (SOC).

[0066] For the benefit of other modules, the operating system module 710 may be configured to manage hardware located within and coupled to the handheld controller 600. Furthermore, the computer-readable medium 708 may store a network communication module 712 that enables the handheld controller 600 to communicate with one or more other devices 701 via a communication interface 704, such as personal computing devices running applications (e.g., game applications), game consoles, remote servers, etc. The computer-readable medium 708 may further include a game session database 714 to store data associated with games (or other applications) running on or on computing devices coupled to the controller 600. The computer-readable medium 708 may also include a device record database 716 that stores data associated with devices coupled to the controller 600, such as personal computing devices, game consoles, remote servers, etc. The computer-readable medium 708 may further store game control instructions 718 configuring the controller 600 as a game controller and general control instructions 720 configuring the handheld controller 600 as a controller for other non-game devices.

[0067] In some cases, Figure 7 Some or all of the components (software) shown may be implemented on another computing device 701 as part of a controller system 700 including controller 600. In such cases, the processes and / or functions described herein may be implemented by another computing device 7001 and / or controller 600. For example, controller 600 may be coupled to a host PC or console, computing device / server in the same environment and provide device 701 with data indicating presses, selections, etc., received at controller 600. For instance, controller 600 may transmit data indicating touch input received at control 100 (e.g., touchpad) of controller 600 to computing device 701, and computing device 701 may determine the characteristics of the data and / or the location where the touch input is received on controller 600 (or the control of controller 600). Computing device 701 may then cause associated actions within a game or application to be performed, and / or computing device 701 may cause associated outputs to be provided via an output device, such as the haptic actuator 106 of control 100 described in detail above. However, although some scenarios are described, the controller 600 and the computing device 701 can be communicatively coupled to each other for transmitting and receiving data, enabling the controller 600, the computing device 701 and / or other devices of the controller system 700 to perform the operations and processes described herein.

[0068] Unless otherwise stated, all figures expressing quantities, properties, conditions, etc., used in the specification and claims should be understood to be modified by the term "about" in all cases. Therefore, unless indicated to the contrary, the numerical parameters set forth in the specification and appended claims are approximate values ​​that may be varied according to the desired properties sought to be obtained in this disclosure. At least and without attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should be interpreted based on the number of significant figures reported and by applying ordinary rounding techniques. When further clarification is required, the term “about” has the meaning reasonably assigned by a person skilled in the art when used in conjunction with a specified value or range, meaning slightly greater than or slightly less than the specified value or range, within ±20% of the specified value; ±19% of the specified value; ±18% of the specified value; ±17% of the specified value; ±16% of the specified value; ±15% of the specified value; ±14% of the specified value; ±13% of the specified value; ±12% of the specified value; ±11% of the specified value; ±10% of the specified value; ±9% of the specified value; ±8% of the specified value; ±7% of the specified value; ±6% of the specified value; ±5% of the specified value; ±4% of the specified value; ±3% of the specified value; ±2% of the specified value; or ±1% of the specified value.

[0069] While various examples and embodiments have been described individually herein, they can be combined, rearranged, and modified to achieve other variations within the scope of this disclosure. Furthermore, although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described.

Claims

1. A controller system, the controller system comprising: a processor; and a controller, the controller comprising: a housing; and a touchpad configured to be operated by a finger of a user of the controller, the touchpad comprising: a cover; a circuit board disposed behind the cover and coupled to the cover; a haptic actuator mounted to the circuit board and configured to vibrate in response to a control signal from the processor, wherein the haptic actuator has a first resonant frequency; and a spring disposed behind the cover, coupled to the cover, and mounted to the housing, wherein the spring is configured to deflect bi-directionally in response to the vibration of the haptic actuator, wherein the touchpad has a second resonant frequency that is different from the first resonant frequency.

2. The controller system of claim 1, wherein the second resonant frequency is defined by a spring constant of the spring, a mass of the cover, a mass of the circuit board, and a mass of one or more components including the haptic actuator mounted to the circuit board.

3. The controller system of claim 1, wherein a difference between the first resonant frequency and the second resonant frequency is in a range of about 70 hertz (Hz) to 160 Hz.

4. The controller system of claim 1, wherein the spring comprises: a first elongated spring arm parallel to and adjacent to a first side of the cover; and a second elongated spring arm parallel to and adjacent to a second side of the cover opposite the first side of the cover.

5. The controller system of claim 4, wherein: the first elongated spring arm abuts a body of the spring at a first neck region; the second elongated spring arm abuts the body of the spring at a second neck region; the first neck region and the second neck region are substantially equal in length; and the length is in a range of about 5 millimeters (mm) to 20 mm.

6. A touchpad of a controller, the touchpad comprising: a cover; a circuit board disposed behind the cover and coupled to the cover; a haptic actuator mounted to the circuit board and configured to vibrate, wherein the haptic actuator has a first resonant frequency; and a spring disposed behind the cover, coupled to the cover, and mounted to a housing of the controller, wherein the spring is configured to deflect bi-directionally in response to the vibration of the haptic actuator, wherein the touchpad has a second resonant frequency that is different from the first resonant frequency.

7. The touchpad of claim 6, wherein the second resonant frequency is defined by a spring constant of the spring, a mass of the cover, a mass of the circuit board, and a mass of one or more components including the haptic actuator mounted to the circuit board.

8. The touchpad of claim 6, wherein a difference between the first resonant frequency and the second resonant frequency is in a range of about 70 hertz (Hz) to 160 Hz. ​ ​ 9. The touchpad of claim 6, wherein the spring comprises: a first elongated spring arm adjacent to a first side of the cover; and a second elongated spring arm adjacent to a second side of the cover opposite the first side of the cover.

10. The touchpad of claim 9, wherein: the first elongated spring arm comprises: a first corner flange at a first end of the first elongated spring arm; and a second corner flange at a second end of the first elongated spring arm; and the second elongated spring arm comprises: a third corner flange at a first end of the second elongated spring arm; and a fourth corner flange at a second end of the second elongated spring arm, wherein the spring is mounted to the housing via the first corner flange, the second corner flange, the third corner flange, and the fourth corner flange.

11. The touchpad of claim 9, wherein: the first elongated spring arm abuts a body of the spring at a first neck region; and the second elongated spring arm abuts the body of the spring at a second neck region.

12. The touchpad of claim 11, wherein: the first neck region and the second neck region are substantially equal in length; and the length is in a range of about 5 millimeters (mm) to 20 mm.

13. The touchpad of claim 11, wherein: the first elongated spring arm comprises: a first cantilever arm extending from the first neck region in a first direction; and a second cantilever arm extending from the first neck region in a second direction opposite the first direction; and the second elongated spring arm comprises: a third cantilever arm extending from the second neck region in the first direction; and a fourth cantilever arm extending from the second neck region in the second direction.

14. The touchpad of claim 6, wherein the spring is configured to exert a biasing force on the cover in a direction opposite a direction of a force exerted on the cover by a user of the touchpad.

15. The touchpad of claim 6, wherein the spring is manufactured from a single piece of material.

16. The touchpad of claim 6, wherein the spring is coupled to the cover via: a first side flange of the spring coupled to a back of the cover at a first side of the cover; and a second side flange of the spring coupled to the back of the cover at a second side of the cover opposite the first side of the cover.

17. A controller system, the controller system comprising: a processor; and a controller comprising: a housing; and a control configured to be operated by a finger, the control comprising: a cover; a circuit board disposed behind the cover and coupled to the cover; a haptic actuator mounted to the circuit board and configured to vibrate in response to a control signal from the processor, wherein the haptic actuator has a first resonant frequency; and a spring disposed behind the cover, coupled to the cover, and mounted to the housing, wherein the spring is configured to deflect bi-directionally in response to the vibration of the haptic actuator, wherein the control has a second resonant frequency that is different from the first resonant frequency.

18. The controller system of claim 17, wherein a difference between the first resonant frequency and the second resonant frequency is in a range of about 70 hertz (Hz) to 160 Hz.

19. The controller system of claim 17, wherein the spring comprises: a first elongated spring arm adjacent to a first side of the cover; and a second elongated spring arm adjacent to a second side of the cover opposite the first side of the cover.

20. The controller system of claim 17, wherein the control comprises a trackpad. ​

Images