Patent Application
20050076161
A portion of the disclosure of this patent document contains material which is subject to copyright or mask work protection. The copyright or mask work owner has no objection to the facsimile reproduction by any one of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright or mask work rights whatsoever.
1. Field of the Invention
The present invention relates generally to a video game input system, and, more particularly, to a system and method for converting movement of a moving object into input device data, such as mouse controller input data, to a video game or computer application.
2. Description of Related Art
Video games are a popular form of entertainment. Video games often use input devices, such as a mouse, joystick, keyboard, or other game controller, to receive the input data from the user that is necessary to control the game characters and features of the game. When playing a sports video game, it is desirable to the user to feel like they are actually playing the sport that is the subject of the video game. The aforementioned input devices are generic to all types of video games and do not give the user such a realistic feeling of playing a sport. Accordingly, a need exists for a method and system that better captures the realistic feeling of actually playing the sport that is the subject of a video game when the user is providing input to control the game characters and features of the video game.
3. Summary of the Invention
The foregoing as well as other, needs are satisfied by the present invention. According to certain embodiments, systems and methods for converting movement of a moving object into input device data are disclosed.
One embodiment of the invention is directed to a system for use with a computer application configured to respond to first input device data from a first input device, the first input device having a first format. This embodiment of the present invention includes: a second input device, different than the first input device, the second input device including one or more sensors configured to measure movement of an object and creating second input device data representative of the movement of the object, the second input device data having a second format different than the first format; and a processor configured to convert the second input device data into simulated first input device data, the simulated first input device data having the first format, the processor further configured to provide the simulated first input device data to the computer application, thereby simulating the first input device with the second input device.
Another embodiment of the invention is directed to a system for converting movement of an object from a first format into input device data of a second format that a computer application is configured to receive. This embodiment of the present invention includes a sensor unit including: one or more sensors configured to measure movement of the object in one or more directions and create a signal representative of the movement of the object in a first format; a transmitter configured to communicate the signal; and a user station having driver software configured to receive the signal, convert the signal into simulated input device data having the second format, and provide the simulated input device data to the computer application.
Yet another embodiment of the invention is directed to a method of providing input to a computer application configured to receive first input device data having a first format. This embodiment of the present invention includes: measuring movement of an object in one or more directions; creating second input device data representative of the movement of the object, the second input device data having a second format different than the first format; converting the second input device data into simulated first input device data, the simulated first input device data having the first format; and providing the simulated first input device data to the computer application, thereby simulating the first input device with the second input device.
Yet another embodiment of the invention is directed to a system of providing input to a computer application configured to receive first input device data having a first format. This embodiment of the present invention includes: means for measuring movement of an object in one or more directions; means for creating second input device data representative of the movement of the object, the second input device data having a second format different than the first format; means for converting the second input device data into simulated first input device data, the simulated first input device data having the first format; and means for providing the simulated first input device data to the computer application, thereby simulating the first input device with the second input device.
Yet another embodiment of the invention is directed to a method for replicating first input device data of a first input device, the first input device data having a first format, to a computer application, to control movement of a graphical representation of an object. This embodiment of the present invention includes: measuring movement of the object with a second input device; creating an electronic signal representative of the movement of the object, the electronic signal having a second format different from the first format; translating the electronic signal into replicated first input device data having the first format; and making the replicated first input device data available to the computer application, thereby replicating first input device data from the first input device with replicated first input device data for the second input device.
Yet another embodiment of the invention is directed to a computer readable medium comprising code for configuring a processor. This embodiment of the present invention includes: providing simulated input device data to a computer application, the computer application configured to control a graphical representation of an object in response to input device data; and translating a signal into the simulated input device data, the signal representing physical movement of the object, the signal having a signal format incompatible with the computer application and the simulated input device data compatible with the computer application, thereby simulating the input device data.
The invention will next be described in connection with certain exemplary embodiments; however, it should be clear to those skilled in the art that various modifications, additions, and subtractions can be made without departing from the spirit or scope of the claims.
The following drawing figures, which are included herewith and form a part of this application, are intended to be illustrative examples and not limiting of the scope of the present invention.
FIGS. 6(a)-6(d) are graphs illustrating the mapping of the angle data to the correct quadrants according to one embodiment of the present invention.
FIGS. 7(a)-7(c) are flowcharts illustrating the process for transformation of the unfiltered angle data to filtered angle data according to one embodiment of the present invention.
Certain embodiments of the present invention will now be described in greater detail with reference to the aforementioned figures.
In the present embodiment, as shown in
In alternate embodiments, the sensor unit 10 and a dongle unit, each house a wireless transceiver 60. The dongle unit may plug into the USB or serial port of the user station 90 to allow wireless two-way communication of data between the sensor unit 10 and the user station 90. Additionally, the sensor unit 10 may house a transmitter 60 and the dongle unit may house a receiver to allow wireless one-way communication of data from the sensor unit 10 to the user station 90.
The user station 90 is a computing device—a personal computer (PC) having a mouse in the present embodiment, although in alternate embodiments other processors may be used, such as a personal digital assistant (PDA), hand-held game device, web-enabled cellular telephone, laptop computer, home entertainment system (such as those offered by Nintendo of America Inc. and Sega Corporation) and the like, having the ability to accept input data from a mouse controller and having the ability to run a video game or computer application, such as a training simulation, requiring mouse controller input data. Additionally, in alternate embodiments, the user station 90 may have associated therewith any other type of input device, such as a joystick, paddle, keyboard, or any other type of game controller input and the like, and may have the ability to run a video game or computer application requiring input device data from any of the aforementioned input devices and the like.
The driver software 80 running on the user station 90 is configured to process the digital signal representative of the movement of a moving object received from the sensor unit 10 and convert the digital signal into input device data that can be used to control the movement of game character in the video game or computer application running on the user station 90. In alternate embodiments, the computer application may reside on a machine other than the user station and be accessible to the user of the system via a network, such as the Internet, local area network, cable television, satellite television, and the like.
In the present embodiment, the moving object is a golf club 70 and the digital signal received by the driver software 80 from the sensor unit 10 is a digital signal representative of the acceleration and angle of a swinging club 70. In the present embodiment, the digital signal received from the sensor unit 10 is converted into mouse controller input data. However, in alternate embodiments, the digital signal received from the sensor unit 10 may be converted into other types of input device data, such as joystick, paddle, keyboard, or any other type of game controller input data, and the like, that may be used to control the movement of game character in the video game or computer application running on the user station 90. In the present embodiment, the driver software 80 has a user interface associated therewith for communicating visually and/or audibly with the user, including, but not limited to, receiving user inputs, configuring parameters, logging data, displaying captured data, selecting a port from which to read data, and setting a mode for a left-handed or right-handed golfer.
The system of the present embodiment is used to provide input to any commercial off-the-shelf computer or other video game or computer application capable of using data from an input device, including those simulating the sport of golf, such as that offered by Microsoft Corporation under the trademark LINKS2003, by Electronic Arts Inc. under the trademark TIGER WOODS PGA TOUR 2003, as well as those simulating other sports and scenarios, such as baseball, tennis, soccer, volleyball and hockey. In the present embodiment the sensor unit 10 is attached to a golf club 70. However, in alternate embodiments, the sensor unit 10 may be attached to any other type of moveable object including, a piece of sporting equipment (such as a baseball bat, tennis racket, hockey stick) or may be attached to the user themselves (such as the user's arm or leg, via an arm or leg band having a material, such as velcro) to measure data to convert to mouse controller movement to play a video game or computer application, such as a training simulation.
More specifically, in the present embodiment, the system is designed to allow a user to capture a more realistic feeling of playing golf with the LINKS2003 golf game, by choosing to use a golf club 70 as the input device to a golf video game, instead of the mouse controller, to control the movement of the game characters of the video game, such as the swing of the golf club 70 and, consequently, the movement of the golf ball (path, direction, speed, etc.). The sensor unit 10 attached to the golf club 70 measures the acceleration and angle of the user's swing and produces mouse controller input data representative of the user's swing to be utilized by the video game to control the aforementioned game characters. Thus, the sensor unit 10 is an input device that is separate and distinct from the input device—the mouse—that the video game is designed to respond to. By translating or converting the sensor output signal into the format of the mouse controller, the system replicates or simulates the mouse controller data. Notably, when the format of the translated sensor signal is described to be the same as that of the controller input data, such as mouse controller data, it is to be understood that exact identity of format need not be accomplished, as the description is meant to encompass identity only to the degree required for the user station (and any necessary software) to use the translated sensor signal. Because the system functions independently of the video game and the conversion to mouse controller input data occurs prior to the input of swing data to the video game, the video game receives the mouse controller input data unaware of use of the golf club 70, sensor unit 10, or any prior conversion of data. In this manner, the system of the present embodiment may be utilized for any golf video game that is designed to use mouse controller input data, without the necessity of any additional coding to the video game. In alternate embodiments, however, the translation of movement data into mouse, or other controller, input data may be incorporated into the applicable video game or other computer application.
Having generally described the components of the present embodiment, each component will now be described in greater detail.
As illustrated, the sensor unit 10 houses the first and second accelerometers 20, the analog-to-digital converter 40, the sensor processor 50, and the transceiver 60. The sensor unit 10 is attachable to the shaft of any conventional golf club 70 by any known or developed means, including those permanently and temporarily attached. In the present embodiment, a Velcro hook on the curved bottom of the sensor unit 10 is wrapped in a Velcro loop on the shaft of the club 70 to attach the sensor unit 10 to the club 70. Another velcro hook/loop combination is used to further secure the sensor unit 10 onto the shaft of the club 70. In alternate embodiments, the sensor unit 10 is molded plastic having deformable clips molded therein for receiving the golf club 70. In further alternate embodiments, the means for attaching the sensor unit 10 to the golf club 70 may be clasps, straps, loops, rings, fasteners, velcro, and the like. Preferably, the sensor unit 10 is attached near the bottom third of the club 70 to be close to head of the club 70, which is the point at which the most accurate acceleration and angle of the user's swing can be measured. However, in alternate embodiments, the sensor unit 10 is housed directly within the moveable equipment, such as within a golf club 70, hockey stick, or tennis racket.
As shown in
The analog-to-digital converter 40 is communicatively coupled to the accelerometers 20 and converts the analog signal representative of the acceleration and angle of the swing produced by the accelerometers 20 to a digital signal representative of the acceleration and angle of the swing.
The sensor processor 50 is communicatively coupled to the analog-to-digital converter 40 to receive the digitized acceleration and angle data. This sensor processor receives the data, assembles it into data frames and communicates it to the transceiver 60. Each data frame contains measurements of acceleration data and angle data at a specific point in time during a swing.
The transceiver 60 is communicatively coupled to the sensor processor 50 and the sensor firmware 65 communicates the digital signal representative of the acceleration and angle of the swinging club 70 to the user station 90. The transceiver 60 may also receive command data from the user station 90.
The sensor firmware 65 is communicatively coupled to the transceiver 60 and sensor processor 50 and continuously listens for command data sent from the user station 90 to the sensor unit 10 (when turned on), which requests the sensor unit 10 to send data to the user station 90, such as a request for calibration data (described later in the application). When the sensor firmware 65 recognizes that command data is being received by the sensor unit 10, via the transceiver 60, the assembly and transmission of data frames by the sensor processor 50 to the sensor unit 10 is temporarily halted, to allow the requested information to be sent to the user station 90.
In the present embodiment, the sensor unit 10 (when turned on) continuously communicates the acceleration data and angle data in the form of data frames to the data buffer of the serial port located in the operating system on the user station 10. The data frames are communicated to the data buffer at a rate of 100 data frames per second, although in alternate embodiments that rate may be higher or lower. The driver software 80 retrieves the data frames stored in the data buffer in the form of data blocks. Each data block includes one or more data frames. The number of data frames in each data block depends on the driver software 80, operating system, and the user station 90. Each data frame consists of an array of data containing the following values:
In each data frame, the term “acc” represents acceleration, the term “ang” represents angle, the numbers 1 and 2 represent the corresponding accelerometer 20, and the letters x and y represent the corresponding axis of measurement (for example, variable acc_x1 represents the acceleration data in the x axis for the first accelerometer 20.)
In each data frame, the acceleration data for acc_x1, acc_y1, acc_x2, and acc_y2 is measured directly from the corresponding accelerometers 20. Each accelerometer 20 may also be used as a dual axis tilt sensor to measure angle data. In each data frame, the angle data for ang_x1, ang_y1, ang_x2, and ang_y2 is computed by the sensor firmware 65 residing on the sensor unit 10 using data received from the corresponding accelerometer 20. In the present embodiment, the angle data is output by the accelerometer 20 encoded as Pulse Width Modulation (“PWM”) data, although different accelerometers may output the data differently.
The accelerometers 20 use the force of gravity as an input vector to determine orientation of an object in space. An accelerometer is most sensitive to tilt when its sensitive axis is perpendicular to the force of gravity (parallel to the Earth's surface). At this orientation, sensitivity to changes in tilt is highest. The reference point for the angle of the club 70 is calibrated at the factory, preferably to be 1 g where g represents a unit of gravity (−1 g when parallel to the Earth's surface in an opposite orientation).
In general, when each accelerometer 20 is oriented on an axis parallel to the force of gravity, near its 1 g or −1 g reading, the change in calculated angle per degree of tilt is negligible. As each accelerometer's 20 orientation approaches an axis perpendicular to the force gravity, the relative sensitivity of the calculated angle per degree of tilt becomes greater. By utilizing the change in output acceleration for x and y axes of each accelerometer 20, it is possible to calculate the angle data for x and y axes of each accelerometer 20 and the degree of orientation of the golf club 70 with respect to the Earth's surface. The relationship between the output acceleration and the degree of orientation for accelerometers 20 are typically known, and, if not, can be determined by routine testing. It has been found that in the present embodiment, generally, the angle data is useful only when the sensor unit 10 is in static status, because when the sensor unit 10 is in motion, the angle data is inaccurate because the movement is based on a combination of gravity and the user-induced motion. Accordingly, the present invention utilizes angle data primarily when the club 70 is in a static or slow moving state.
In the present embodiment, the driver software 80 receives the calibration data from the particular sensor unit 10 being used with the system in order to more accurately convert the acceleration and angle data received from the sensor unit 10 into mouse controller movement data. The driver software 80 running on user station 90 sends a request for the retrieval of calibration data to the sensor unit 10 (at any time when the sensor unit is turned on). The sensor firmware 65, listening for command data, recognizes the request for the retrieval of calibration data from the user station 90. The sensor firmware 65 instructs the sensor processor 50 to temporarily halt the assembly and continuous transmission of data frames to the user station 90 and retrieves the calibration data for each sensor 20 requested by the driver software 80. The calibration data for each sensor 20 is sent, via the transceiver 60, to the driver software 80 and used by the driver software 80 to determine the proper mouse controller movement data. Without the proper calibration data for each sensor 20, the driver software 80 would not have a proper reference point at which to correctly interpret the acceleration and angle data from the sensors and would result in simulating mouse movement that is not properly representative of the user's swing.
Additionally, in alternate embodiments, a data frame may be organized in a variety of manners having one or more of the aforementioned variables or additional variables to allow for the storage of angle and/or acceleration data and/or additional measurement data that may be calculated by other types of sensors, such as turn rate and direction, as calculated by a rate gyro.
Persons of skill in the art will recognize that, although the above-referenced system components are discussed and shown as being housed in a singular sensor unit 10, as a matter of design choice, any number of system components may be housed in separate units or combined into one or more system components or units to be utilized within the scope of the present invention. In alternate embodiments, multiple sensors or sensor units may be spaced at different points along the moveable object to better measure the position of the moveable object. Also, in alternate embodiments, the accelerometers 20 are configured to directly output a digital signal, obviating the need for an analog-to-digital converter 40. Additionally, although in the present embodiment the sensor unit 10 attaches to a golf club 70, in alternate embodiments, the sensor unit 10 may attach to any other type of moveable equipment that could be used as an input device for a user station, including, but not limited to, a baseball bat, a hockey stick, tennis racket, and the like. Further, although in the present embodiment the data received from the sensor unit 10 is converted to mouse controller input data, it should be understood that the data received from the sensor unit 10 may be converted into any type of input device data that is utilized by a video game or simulation on a user station 90.
Having described the components of the present embodiment, the operation thereof will now be described in greater detail. The process for using a device and software to play a golf video game according to one embodiment of the present invention will now be described with reference to
In step 300, the user loads or runs a golf video game, such as those identified above, and the driver software 80 on a user station 90. In step 310, the user sets up the video game according to the game's instructions, such as configuring the game to play in real-time swing mode in LINKS2003. In step 320, the user starts the video game, preparing the game to accept input data to control the movement of the video game characters.
In step 330, driver software recognizes the type of swing mode that has been selected by the user on the video game, for example (1) full swing, (2) chipping, or (3) putting, to configure the proper conversion of acceleration and angle data into mouse controller input data for the swing. In many golf video games, the amount of mouse controller movement necessary to hit the golf ball a certain distance will vary based upon the type of swing mode. For example, a long putt may require a relatively large amount of mouse controller movement similar to a long drive on a video game; whereas a long putt may require only slight club movement as compared to a drive using a golf club 70. Therefore, in certain embodiments, the driver software 80 accounts for this change by being aware of the proper conversion rate of the acceleration and angle data of the user's swing into mouse controller input data to be used by the particular video game. In step 340, the user swings the golf club 70, having the attached sensor unit 10 of the present embodiment. In step 350, the driver software 80 recognizes that the golf club 70 is being swung by the user, via the process described in greater detail herein in
As noted above, the driver software 80 converts the accelerometer data into mouse controller input data for simulating a user's movement of the mouse. The process for simulating mouse controller movement according to one embodiment of the present invention will now be described in greater detail with reference to
In step 400, the driver software 80 reads a data block having one or more data frames from the data buffer to determine whether the sensor unit 10 is in static status. In step 410, the driver software 80 determines whether the sensor unit 10 is in static status. To determine whether the sensor unit 10 is in a static state, namely, when the user holds the golf club 70 relatively still prior to beginning to swing, the driver software 80 reads the acceleration and angle data from sensor unit 10 in the data buffer 10 to determine if the acceleration and angle data indicate movement below a certain threshold. This determination is described in greater detail below with reference to
If it is determined that the sensor unit 10 is in static status, the driver software 80 reads the data block, in step 420, to determine the acceleration data and angle data representative of the user's swing. In step 430, the driver software 80 uses window filtering to smooth the current data frame in the data block to filter out the noise resulting from unintentional movement of the golf club 70. In step 440, the driver software 80 converts the filtered acceleration data and angle data to mouse controller input data by computing the incremental mouse controller movement distance between the current data frame in the data block and the prior data frame in the data block. As described in greater detail below with reference to
In step 450, the mouse controller input data that is representative of the user's swing is received, as if directly from the mouse controller, by the video game software running on the user station 90 to control the movement of a game character in the video game running. In step 460, the driver software 80 determines whether point of impact has been reached. The driver software 80 determines whether the point of impact has been reached by utilizing delayed processing. Following the determination that the sensor unit 10 is in static status, the driver software 80 processes data frames in real-time or substantially real-time until the software driver 80 detects a reading of valid angle data following the acceleration due to the backswing of the club 70 by the user (This generally occurs as the user pauses at the top of his backswing prior to his downswing). Following recognition of valid angle data, as described herein, the driver software 80 continues to process the data frame, but in a delayed format, so that the driver software 80 can determine whether the highest acceleration for the swing has been reached, signaling the point of impact. The delay in processing should be as long as necessary to ensure that the highest acceleration had been reached and the acceleration is now decreasing due to the follow through of the golf swing. If driver software 80 determines that point of impact has been reached, in step 460, then driver software 80 continues to read data frames until angle data shows for the golf club 70 is equal to 20 degrees past the angle data at the point of impact in step 470, and then there is no additional processing of data for current swing and the subprocess ends in step 480. The driver software 80 may be configured to continue reading data frames until the angle data for the golf club 70 is greater than or less than 20 degrees. If driver software 80 determines that point of impact has not been reached, in step 460, then the driver software 80 determines whether the current data block includes another data frame that has not been processed for the user's swing, in step 490. If it is determined that all data frames have not been processed for the current data block in step 490, then driver software 80 reads the next data frame and return to step 430. If it is determined that all data frames have been processed for the current data block in step 490, then process returns to step 420 and driver software 80 reads the next data block.
Having generally described the process of converting swing data to mouse data in the present embodiment, each step in the process will now be described in greater detail.
The process for reading a data block from the sensor unit 10 according to one embodiment of the present invention will now be described. The driver software 80 reads a data block having one or more data frames from the sensor unit 10 to determine whether the sensor unit 10 is in static status. A timer of the driver software 80 is set to allow the driver software 80 to read a data block from the data buffer of the serial port of the user station 90. The timer's interval is preferably set at 200 ms. The data buffer of the driver software 80 for the serial port communication is preferably large enough for 100 data frames to be read by the driver software 80. In alternate embodiments, the timer's interval may be greater or less than 200 ms, and the data buffer may allow for greater or less than 100 data frames to be read by the driver software 80 at one time, as appropriate for the particular application.
The process for determining whether the sensor unit 10 is in static status according to one embodiment of the present invention will now be described in greater detail. The driver software 80 determines whether the sensor unit 10 is in static status. The sensor unit 10 is considered to be in static status when the golf club 70 is being held at a relatively steady position, in the present golf embodiment, at the bottom (prior to swing) or top (pause following backswing) of the user's swing. If the driver software 80 determines that the sensor unit 10 is in static status, the sensor unit 10 is prepared to measure the acceleration data and angle data of the user's next swing. The driver software 80 embodies appropriate algorithms to be used to convert the acceleration and angle data to mouse controller input data, as described herein and one or more audible or other perceptible signals, such as beeps, lights, or voice commands, will occur to alert the user that he or she may now swing the golf club 70.
The number of audible signals depends on the type of swing mode that has been set by the user prior to his or her swing. There are three swing modes that may be selected by the user: (1) full swing; (2) chipping; and (3) putting. The number of audible signals for each type of swing mode are one, two, and three, respectively. In alternate embodiments, other manners of alerting the user as to the status or mode of the golf swing may be utilized, such as a voice command or visual signal (e.g. a group of one, two and three flashes repeated) displayed on the user station 90. The driver software 80 is configured to process the acceleration data and angle data received from the sensor unit 10 using a different method depending upon the type of swing mode that has been set by the user prior to his or her swing. A detailed explanation of the methods employed to process the acceleration data and angle data received from the sensor unit 10 and are described herein.
If the driver software 80 determines that the sensor unit 10 is not in static status from the current data block, the driver software 80 will read the next data block, continuously repeating the process until the driver software 80 determines the sensor unit 10 to be in static status. During this determination of whether the driver software 80 is in static status, no acceleration data, nor angle data received from the sensor unit 10 is converted into mouse controller input data by the driver software 80.
An exemplary process for determining whether the sensor unit 10 is in static status is shown in
When the driver software 80 determines that the sensor unit 10 is in static status, the sensor unit 10 is prepared to measure the acceleration data and angle data of the user's swing and an audible signal (based on the type of swing mode) will alert the user that he or she may now swing the golf club 70. As the user swings the golf club 70, a data block having one or more data frames of acceleration data and angle data is measured by the sensor unit 10 and processed by the driver software 80 to convert the acceleration data and angle data representative of the user's swing into mouse controller input data via the following processes in the present embodiment.
The process for smoothing the current data frame using window filtering will now be described in greater detail according to one embodiment of the present invention. The acceleration data and angle data read by the driver software 80 from the sensor unit 10 often has noise (jitter) associated therewith that is the result of unintentional movement of the golf club 70. The reasons for such noise may include the shaking of a person's hands, the sensitivity of the accelerometers 20 in the sensor unit 10, and the like. It is desirable to filter out this unintentional noise in order to obtain a more accurate representation of the acceleration and angle data to be processed by the driver software 80.
In the present embodiment, the driver software 80 applies a non-linear technique is applied to filter out noise and smooth the acceleration and angle data in the data frame using a sliding window to a data sequence, such as the exemplary process shown below. In the following example, t is the current time; f(i) is acceleration and/or angle data at time (i) (where i=1,2,3, . . . t); n is the filter size; p and y are temporary storage variables; f(t−n to t) represents raw angle or acceleration data; and f(t)=transformed angle or acceleration data. At each time, t, the data is processed as follows:
It is to be understood that the filtering is optional and that other filtering techniques may be used.
The process for transformation of the unfiltered angle data into filtered angle data according to one embodiment of the present invention will now be described. The particular accelerometers 20 used in the present embodiment measure the angle position in a range of 0 to +/−90 degrees with respect to the vertical direction. Therefore, certain readings may be in one of two quadrants, as illustrated in
As described herein, the acceleration data of the golf club swing is measured directly by the accelerometers 20. The first four values in each data frame constitute the acceleration of the golf club swing in the x and y axes of the first accelerometer 20 and the x and y axes of the second accelerometer 30 (acc_x1, acc_y1, acc_x2, acc_y2). The angle data in each data frame is computed by the sensor firmware 65 using PWM data. The last four values in each data frame constitute the angle of the golf club swing in the x and y axes of the first accelerometer 20 and the x and y axes of the second accelerometer 30 (ang_x1, ang_y1, ang_x2, ang_y2).
In the present embodiment, the golf club 70 may be positioned in one of four quadrants (90° to 0°, 0° to −90°, −90° to −180°, or −180° to −270°, as pictured in
It has been determined that, in the present embodiment, the angle data is more reliable when the sensor unit 10 is in static status, as opposed to when the sensor unit 10 is in motion, where the angle data is inaccurate. Therefore, the conversion from the golf club swing data (acceleration and angle data) to mouse controller input data will be delayed. In order to improve this conversion rate to substantially real-time, the exemplary process, shown in FIGS. 7(a)-7(c), is used to transform the unfiltered angle data into filtered angle data. In this example, t is the current time; ang_y1(i) represents the angle data in the y axis of the first accelerometer 20 (i=1,2,3, . . . t); acc_y1(i) represents the acceleration data in the y axis of the first accelerometer 20 (i=1,2,3, . . . t); n is the filter size; Tss is the threshold for STD filtering; Stack is a data structure for temporarily storing angle data during the transformation process; and STD( ) is a function of standard deviation.
In step 700, the driver software 80 reads the current data frame and obtains the angle data in the y axis at time j, ang_y1(j), where j=t−n+1, . . . , t. In step 705, the software 80 calculates the standard deviation over the filter time period, Stdy1=STD(ang_y1(j)). Having determined the standard deviation, in step 710, the software 80 determines whether the standard deviation is greater than the threshold value (i.e., whether Stdy1>Tss). If the standard deviation is greater than the threshold, then the sensor unit 10 is deemed to be in motion and the process continues with step 740.
If the standard deviation is equal to or less than the threshold, then the sensor unit 10 is deemed to be in static status and the process continues with the software 80 transforming the angle data, ang_y1(t), into transformed angle data, ang_y1(t), to reflect the correct quadrant of the club 70 in step 715. Because the particular accelerometers 20 measure the angle position in a range of 0 to +/−90 degrees, certain readings may be in one of two quadrants, as illustrated in
In step 720, the software 80 determines whether Stack B is null, or empty. If stack B is not null, then, in step 725 the driver software 80 artificially generates angle information according to Stack B and the transformed angle, ang_y1′(t), takes them as new data frames and insert them into Stack C; Stack B remains null. If Stack B is null, then the driver software 80 determines whether Stack A is null, in step 730.
If Stack A is not null, then, in step 730, then the driver software 80 artificially generates angle information according to Stack A and the transformed angle, ang_y1′(t), takes them as new data frames and insert them into stack C; Stack A remains null. If Stack A is null, then the process returns to step 700 to read a new data frame.
Continuing with step 740, the driver software 80 determines whether the current acceleration in the y axis is less than the acceleration at the beginning of the time period, as stored by the driver software 80 (i.e., acc_y1<acc_y1_starting). If the current acceleration is less than the starting acceleration, then, in step 745, the software 80 inserts the current data frame and transformed angle data, ang_y1′(t), into Stack B, and the process returns to step 700 to read new data frame.
If the current acceleration data is not less than the starting data, then the driver software 80 determines whether Stack B is null in step 750. If Stack B is not null in step 750, then, in step 755, the driver software 80 artificially generates angle information according to Stack B and the transformed angle, ang_y1′(t), takes them as new data frame, inserts them into Stack C, and lets Stack B be null. The process then returns to step 700 to read new data frame. If Stack B is null in step 750, then the driver software 80 inserts current frame data and transformed angle data, ang_y1′(t), into Stack A in step 760, and then the process returns to step 700 to read new data frame.
The process for transforming the value of raw angle data into correct quadrant angle data according to one embodiment of the present invention will now be described with reference to the exemplary pseudocode shown in
An example of raw angle data, transformed angle data, and raw acceleration data for a three-quarter swing according to one embodiment of the present invention will now be described with reference to the illustrative graph in
As seen in
The process for transforming the angle change of a golf club swing into mouse controller movement distance according to one embodiment of the present invention will now be described.
Once raw angle, ang_y1(t), is transformed into correct quadrant angle, ang_y1′(t), the mouse controller movement distance can be computed. The following exemplary processes for transforming (a) full swing; (b) chipping; and (c) putting into mouse controller movement distance are described respectively with reference to the pseudocode in FIGS. 10(a)-10(c).
In these examples, t is current time; and ang_y1′(t) is angle data in the current data frame of the y axis of the first accelerometer 20; ang_y1′(t−1) is angle data in the prior data frame of the y axis of the first accelerometer 20. The mouse controller movement distance between ang_y1 ′(t) and ang_y1′(t−1) may be mapped based on the swing mode and the position of the golf club 70.
An additional process for transforming the angle change of a golf club putt into mouse controller movement distance according to one embodiment of the present invention will now be described.
A user has to move the mouse a relatively long distance to drive in putting mode for certain video games. However, a user usually moves the club 70 in a short distance for putting. In order to let the user feel more real, in putting mode, it is necessary to move a long distance for a small angle change. The angle changes can be mapped to mouse movement distance directly, as for full swing mode and chipping mode. However, because of the noise in raw angle data, when the player holds the club 70 in static position, there is no guarantee that the angle data has not changed after the window filtering technique, as described earlier, is applied. The following pseudocode represents one possible way to overcome this problem, in which the distance of club movement is equal to the angle change of the club 70 multiplied by a conversion variable, R, which is based on the difference between the current angle and starting angle. In the following pseudocode, the variable, distance, represents mouse movement distance, and the unit of measurement of distance is pixels. The code also determines whether to ignore nominal movements (lines 2-5) so as not to inadvertently hit the ball. Furthermore, if the club 70 passes the starting position, the code assumes the user intended to hit the ball (in line 7) and ensure a minimum distance, for example, five pixels.
Input: angle_change and current_angle; Output: distance
It is to be understood that modifications may be made to the code. For example, the values of R are merely exemplary, as are the ranges of angle data corresponding to such values.
Where the user station 90 is a PC operating Windows based operating system, a Windows API “sendInput” is used to move mouse automatically. The declaration is: Declare Function SendInput Lib “user32.dll” (ByVal nInputs as Long, pInputs As INPUT_TYPE, ByVal cbSize as Long) As Long. The detailed explanation of this API could be found in Microsoft's SDK document, which can be found at http://www.partware.com/ebooks/API/ref/s/sendinput.html.
The mouse controller movement distance computed by the driver software 80 may need to be implemented in multiple incremental movements instead of a single large mouse controller movement to ensure proper simulation of the user's swing. For example, where the acceleration data and angle data representative of the user's swing is converted into a mouse controller movement distance of more than 50 pixels, such a large mouse controller movement distance would not be accurately understood by a video game, such as LINKS2003. Where the mouse controller movement distance computed by the driver software 80 would be too large to be accurately understood by the video game, the mouse controller movement distance is represented by several mouse movement steps. For each different swing mode, the length of the mouse movement step is different. Between every two simulated mouse controller movement s, the driver software 80 should wait some time to allow the operating system of the user station 90 to respond to the last mouse controller movement command. Otherwise, a new SendInput will be triggered and it will stop last mouse controller movement, which let the club 70 in LINKS 2003 not correspond to the real swing. Also, if a long wait-time is used, the swing in LINKS 2003 will be delayed. In our tests, we use 10 milliseconds for wait-time in our software for both backswing and downswing.
An exemplary process for converting exceptionally large swing data into mouse controller movement data that can be understood by a video game according to one embodiment of the present invention will now be described below with reference to the pseudocode
Input: distance; Output: distance_loop( ) and distance_number
In further embodiments, the software driver 80 further accounts for club face position, namely open, closed, or square, to determine the angle or direction at which the golf ball would travel following the point of impact. In certain embodiments, each club face position is assigned a particular range of swing speed. When a user swings the club 70, a club face position for the swing is determined based upon the range that encompasses the user's swing speed. In alternate embodiments, the club face direction is determined by an examination of the acceleration components transverse to the direction of motion of the club.
More specifically, in one embodiment, the determination as to the position of the club face is based on the speed of the user's swing at the point of impact: an average speed swing results in a square club face position; a slower than normal swing results in a closed club face; and a faster than normal swing results in an open club face. To determine what is normal for any given golfer/user, the software 80 is trained by the user taking several practice swings. The range of speeds for these practice swings are noted in memory and divided into three ranges, one for each of the three club face positions. In certain embodiments, once the user's swing has been calibrated, the speed of the actual swing is determined as the average of the speed at the point of impact and during two frames immediately following impact, although the value may be taken at fewer or more points in the swing (i.e., frames). For example, using the Analog Devices Inc. ADXL202 dual axis accelerometer, certain golfers would have the following ranges and club face positions for a full swing: if ang_y1 is in the high range of 148-180 mg the club head is in open club face position, if ang_y1 is the middle range of 143-147 mg the club head is in square club face position, and if ang_y1 is in the low range of 120-142 mg the club head is in the closed club face position (mg=one thousandth of the gravitational constant, g). For a chip or putt, if ang_y1 is in the high range of 131-165 mg the club head is in open club face position, if ang_y1 is the middle range of 126-130 mg the club head is in square club face position, and if ang_y1 is in the low range of 90-125 mg the club head is in the closed club face position. It should be understood that any number of positions may be deemed relevant, including fewer than three or more than three (e.g., different degrees of open or closed position) and the range of speeds can be correspondingly divided into fewer or more subranges. Furthermore, the subranges associated with the positions can be, but need not be, uniform in size.
In alternate embodiments of the present invention, rate gyros may be used as additional sensors 20 to extract rotational motion, in addition to translational motion, to allow for six degrees of freedom.
Those skilled in the art will recognize that the method and system of the present invention has many applications, may be implemented in many manners and, as such, is not to be limited by the foregoing exemplary embodiments and examples. Additionally, the functionality of the components of the foregoing embodiments may be implemented in different manners. Further, it is to be understood that the steps in the foregoing embodiments may be performed in any suitable order, combined into fewer steps or divided into more steps. Thus, the scope of the present invention covers conventionally known and future developed variations and modifications to the system components described herein, as would be understood by those skilled in the art.
This Application claims the benefit of U.S. Provisional Application Ser. No. 60/508,466, filed on Oct. 3, 2003, entitled VIDEO GAME INPUT SYSTEM AND METHOD OF PROVIDING SAME, hereby incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60508466 | Oct 2003 | US |
