US 8,103,472 B2Grant
Method and apparatus for compensating for position slip in interface devices
Issue Date:2012-01-24
•17 Claims
•7 Drawing Sheets
Abstract
Method and apparatus for compensating for position slip in interface devices that may occur between a manipulandum and a sensor of the device due to a mechanical transmission. A device position delta is determined from a sensed position of a manipulandum of an interface device. It is determined if position slip has occurred caused by a change in position of the manipulandum that was not sensed by a sensor of the interface device, typically caused by a mechanical transmission between sensor and manipulandum. If position slip has occurred, an error in the sensed position caused by the position slip is corrected by adjusting the sensed position to take into account the position slip. The adjusted position delta is used as the position of the manipulandum and the display of objects controlled by the interface device are accordingly compensated.
Metadata
Assignee
- Immersion Corporation
Inventors
- Adam C Braun
- Kollin M Tierling
- Kenneth M Martin
- Bruce M Schena
Application Information
Application Number:US 12/191,983
Filing Date:2008-08-14
Priority Date:1999-05-11
Art Unit:2857
Classifications
IPC:
G06F19/00
Patent Drawings (7 sheets)
Description
CROSS-REFERENCES TO RELATED APPLICATION
[0001] This application is a continuation of U.S. patent application Ser. No. 10/995,586, now U.S. Pat. No. 7,447,604 filed Nov. 23, 2004, entitled “Method and Apparatus for Compensating for Position Slip in Interface Devices,” which is a continuation of Ser. No. 09/570,157, now U.S. Pat. No. 6,903,721, filed May 11, 2000, entitled “Method and Apparatus for Compensating for Position Slip in Interface Devices,” which claims priority to U.S. Provisional patent application No. 60/133,586, filed May 11, 1999, all of which are incorporated herein by reference in their entirety.
BACKGROUND
[0002] The present invention relates generally to sensing techniques for human-computer interface devices.
[0003] Using an interface device, a user can interact with an environment displayed by a computer system to perform functions and tasks on the computer, such as playing a game, experiencing a simulation or virtual reality environment, using a computer aided design system, operating a graphical user interface (GUI), or otherwise influencing events or images depicted on the screen. Common human-computer interface devices used for such interaction include a joystick, mouse, trackball, steering wheel, stylus, tablet, pressure-sensitive ball, or the like, that is connected to the computer system controlling the displayed environment.
[0004] In some interface devices, haptic feedback is also provided to the user, also known as “force feedback.” These types of interface devices can provide physical sensations which are felt by the user manipulating the physical object of the interface device. For example, the Force-FX joystick controller from CH Products, Inc. or the Wingman Force joystick from Logitech may be connected to a computer and provides forces to a user of the controller. Other systems might use a force feedback mouse controller. One or more motors or other actuators are used in the device and are connected to the controlling computer system. The computer system controls forces on the force feedback device in conjunction and coordinated with displayed events and interactions on the host by sending control signals or commands to the force, feedback device and the actuators.
[0005] In both force feedback devices and non-force feedback devices, it is important to accurately sense the position of the manipulandum moved by the user so that interactions displayed on the screen are accurately portrayed. Furthermore, the determination of forces in force feedback devices often depends on the position of the manipulandum so that accurate sensed position is critical for realistic force feedback.
[0006] Thus, all interface devices require some sort of position sensor (or sensors) in order to read the input position of the manipulandum (“end effector”). Sometimes the position sensors are connected directly to the end effector itself. However, in other cases the sensor is actually connected through a mechanical transmission to the end effector. For example, a gear transmission, capstan drive (cable) transmission, or belt drive transmission can be used. The purpose of the transmission, as far as the position sensor is concerned, is to amplify the range of motion that the sensor can detect and allow the use of lower resolution sensors, which are typically less expensive. A mechanical transmission may also be used to amplify forces output by the actuators of the force feedback device. The transmission for a sensor can be the same transmission as an actuator uses; several different joystick devices use this method, such as the device described in copending patent application Ser. No. 09/138,304, which provides a, sensor connected to an, actuator shaft. In other devices, an independent mechanical transmission dedicated to the sensor can be used.
[0007] In either of these cases, there is the possibility of position slip occurring in the transmission, where the end effector moves some distance without the sensor detecting that movement or inaccurately detecting that movement; e.g., a gear skips teeth, a belt or cable slips on a pulley, etc. When a relative position sensor is used in the device, such as a quadrature encoder, this position slip should be detected or the device will be unable to determine an accurate position for the end effector when slip occurs. The problem is amplified for force feedback devices because they often operate in a limited workspace and depend on the ability to determine the absolute device position in the limited workspace. Furthermore, some forces output by the device are based on an accurate position of the manipulandum, so that the forces can become discontinuous or distorted if position slip occurs.
SUMMARY
[0008] The present invention provides a method and apparatus for compensating for position slip in interface devices that may occur between a manipulandum and a sensor of the device due to a mechanical transmission. More accurate sensing of manipulandum position and smooth display of controlled objects based on manipulandum position are achieved.
[0009] More specifically, a method for correcting for slippage in a position sensing system of an interface device coupled to a host computer includes determining a device position delta from a sensed position of a manipulandum of the interface device in a degree of freedom. The position delta indicates a change in position of the manipulandum. It is determined if position slip has occurred in the position sensing system, where the position slip is caused by a change in position of the manipulandum that was not sensed by a sensor of the interface device. The position slip is typically caused by a mechanical transmission provided between the sensor and manipulandum, such as a gear drive, a belt drive, and a capstan drive. If position slip has occurred, an error in the sensed position caused by the position slip is corrected by adjusting the sensed position to take into account the position slip. The adjusted position delta is used as the position of the manipulandum.
[0010] Preferably, the determining if the slip has occurred includes checking a reference signal from a reference sensor included on the interface device, the reference sensor detecting a position of a reference location coupled to the manipulandum. A computation value is preferably determined from the device position delta, where a display of the host computer is updated based on the computation value. In one method, the computation value is not adjusted with the device position delta when the position slip is detected, allowing smoother display of graphical objects. In some embodiments, a force having a magnitude and direction is determined at least partially based on the computation value, and where the force is output by an actuator included in the interface device. Preferably, the computation value is modified to compensate for an offset between device position and screen position that may occur due to the position slip and the adjustment of computation value. For example, a user-controlled object displayed by the host computer can be allowed to continue to be moved after the manipulandum has reached a limit to a workspace of the manipulandum, where the user-controlled object continues to be moved in a direction corresponding to a direction of the manipulandum into the limit.
[0011] In another method, the determining of a device position, determining if a position slip has occurred, and correcting an error are performed over several iterations, and the sensed position is adjusted or corrected by an amount which gradually reduces the error in the sensed position over those iterations. The adjusting of the sensed position in this fashion is preferably not performed if the manipulandum is not moving in the degree of freedom.
[0012] In another aspect of the present invention, an interface device provides input to a host computer based on manipulations of a user. The interface device includes a manipulandum physically contacted by the user and movable in at least one degree of freedom. A position sensor detects a position of the manipulandum in the degree of freedom. A mechanical transmission is coupled between the manipulandum and the position sensor, and a reference sensor detects the motion of at least one reference location coupled to the manipulandum, the reference sensor providing a reference signal used to determine if position slip has occurred between the manipulandum and position sensor. One or more actuators can be provided to output forces for force feedback devices. A local microprocessor can receive the reference signal and adjust the detected position of the manipulandum to compensate for the position slip. The local microprocessor can also determines a computation value from a position delta, where the computation value is adjusted if the position slip has occurred. The computation value provided to the host computer to update a display of the host computer and can be used to update output forces and other values.
[0013] The present invention advantageously provides a sensing system that takes advantage of the increased sensing resolution offered by the use of mechanical transmissions such as gear drives and belt drives, and yet accurately compensates for the inaccurate sensing that may occur when using such transmissions due to position slip.
[0014] These and other advantages of the present invention will become apparent to those skilled in the art upon a reading of the following specification of the invention and a study of the several figures of the drawing.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] FIG. 1 is a block diagram of system including an interface device and host computer for use with the present invention;
[0016] FIG. 2 is a top plan view of an example of a force feedback interface device suitable for use with the present invention;
[0017] FIG. 3 is a perspective view of a reference sensor of the present invention for detecting position slip;
[0018] FIG. 4 is a flow diagram illustrating a first method of the present invention for compensating for position slip in interface devices;
[0019] FIG. 5 is a flow diagram illustrating a method for detecting position slip and the amount of slip; and
[0020] FIG. 6 is a flow diagram illustrating a second method of the present invention for compensating for position slip in interface devices.
DETAILED DESCRIPTION
[0021] FIG. 1 is a block diagram illustrating a force feedback interface system 10 suitable for use with the present invention controlled by a host computer system. Interface system 10 includes a host computer system 12 and an interface device 14.
[0022] Host computer system 12 can be a personal computer, such as an IBM-compatible or Macintosh personal computer, or a workstation, such as a SUN or Silicon Graphics workstation. Alternatively, host computer system 12 can be one of a variety of home video game systems, such as systems available from Nintendo, Sega, or Sony, a television “set top box” or a “network computer”, etc. Host computer system 12 preferably implements a host application program with which a user 22 is interacting via peripherals and interface device 14. For example, the host application program can be a video or computer game, medical simulation, scientific analysis program, operating system, graphical user interface, or other application program that utilizes force feedback. Typically, the host application provides images to be displayed on a display output device, as described below, and/or other feedback, such as auditory signals.
[0023] Host computer system 12 preferably includes a host microprocessor 16, a clock 18, a display screen 20, and an audio output device 21. Microprocessor 16 can be one or more of any of well-known microprocessors. Random access memory (RAM), read-only memory (ROM), and input/output (I/O) electronics are preferably also included in the host computer. Display screen 20 can be used to display images generated by host computer system 12 or other computer systems, and can be a standard display screen, CRT, flat-panel display, 3-D goggles, or any other visual interface. Audio output device 21, such as speakers, is preferably coupled to host microprocessor 16 via amplifiers, filters, and other circuitry well known to those skilled in the art (e.g. in a sound card) and provides sound output to user 22 from the host computer 12. Other types of peripherals can also be coupled to host processor 16, such as storage devices (hard disk drive, CD ROM/DVD-ROM drive, floppy disk drive, etc.), printers, and other input and output devices. Data for implementing the interfaces of the present invention can be stored on computer readable media such as memory (RAM or ROM), a hard disk, a CD-ROM or DVD-ROM, etc.
[0024] An interface device 14 is coupled, to host computer system 12 by a bidirectional bus 24. The bidirectional bus sends signals in either direction between host computer system 12 and the interface device. An interface port of host computer system 12, such as an RS232 or Universal Serial Bus (USB) serial interface port, parallel port, game port, etc., connects bus 24 to host computer system 12. Alternatively, a wireless communication link can be used.
[0025] Interface device 14 can include a local microprocessor 26, sensors 28, actuators 30, a user object 34, optional sensor interface 36, an optional actuator interface 38, and other optional input devices 39. Local microprocessor 26 is coupled to bus 24 and is considered local to interface device 14 and is dedicated to sensor I/O and force feedback (if provided) of interface device 14. Microprocessor 26 can be provided with software instructions to wait for commands or requests from computer host 12, decode the command or request, and handle/control input and output signals according to the command or request. In addition, processor 26 preferably operates independently of host computer 12 by reading sensor signals and, if appropriate, calculating appropriate forces in accordance with a host command. Suitable microprocessors for use as local microprocessor 26 include the MC68HC711E9 by Motorola, the PIC16C74 by Microchip, and the 82930AX by Intel Corp., for example. Microprocessor 26 can include one microprocessor chip, or multiple processors and/or co-processor chips, and/or digital signal processor (DSP) capability.
[0026] Microprocessor 26 can receive signals from sensors 28 and provide signals to actuators 15′ 30 of the interface device 14 in accordance with instructions provided by host computer 12 over bus 24. For example, in a preferred local control embodiment, host computer 12 provides high level supervisory commands to microprocessor 26 over bus 24, and microprocessor 26 manages low level force control loops to sensors and actuators in accordance with the high level commands and independently of the host computer 12. The force feedback system thus provides a host control loop of information and a local control loop of information in a distributed control system. This operation is described in greater detail in U.S. Pat. No. 5,734,373, incorporated herein by reference. Microprocessor 26 can also receive commands from any other input devices 39 included on interface apparatus 14, such as buttons, and provides appropriate signals to host computer 12 to indicate that the input information has been received and any information included in the input information. Local memory 27, such as RAM and/or ROM, is preferably coupled to microprocessor 26 in interface device 14 to store instructions for microprocessor 26 and store temporary and other data. In addition, a local clock 29 can be coupled to the microprocessor 26 to provide timing data.
[0027] Sensors 28 sense the position, motion, and/or other characteristics of a user object 34 of the interface device 14 along one or more degrees of freedom and provide signals to microprocessor 26 including information representative of those characteristics. Rotary or linear optical encoders, analog potentiometers, photodiode or photoresistor sensors, velocity sensors, acceleration sensors, strain gauge, or other types of sensors can be used. Sensors 28 provide an electrical signal to an optional sensor interface 36, which can be used to convert sensor signals to signals that can be interpreted by the microprocessor 26 and/or host computer system 12.
[0028] Actuators 30 can be included in some interface devices to transmit forces to manipulandum 34 or housing of the interface device 14 in one or more directions along one or more degrees of freedom in response to signals received from microprocessor 26. Actuators 30 can include two types: active actuators and passive actuators. Active actuators include linear current control motors, stepper motors, pneumatic/hydraulic active actuators, a torquer (motor with limited angular range), voice coil actuators, and other types of actuators that transmit a force to move an object. Passive actuators can also be used for actuators 30, such as magnetic particle brakes, friction brakes, or pneumatic/hydraulic passive actuators. Actuator interface 38 can be optionally connected between actuators 30 and microprocessor 26 to convert signals from microprocessor 26 into signals appropriate to drive actuators 30.
[0029] Other input devices 39 can optionally be included in interface device 14 and send input signals to microprocessor 26 or to host processor 16. Such input devices can include buttons, dials, switches, levers, or other mechanisms. For example, in embodiments where user object 34 is a joystick, other input devices can include one or more buttons provided, for example, on the joystick handle or base. Power supply 40 can optionally be coupled to actuator interface 38 and/or actuators 30 to provide electrical power. A safety switch 41 is optionally included in interface device 14 to provide a mechanism to deactivate actuators 30 for safety reasons.
[0030] Manipulandum (“end effector” or “user object”) 34 is a physical object, device or article that may be grasped or otherwise contacted or controlled by a user and which is coupled to interface device 14. By “grasp”, it is meant that users may releasably engage, contact, or grip a portion of the manipulandum in some fashion, such as by hand, with their fingertips, or even orally in the case of handicapped persons. The user 22 can manipulate and move the object along provided degrees of freedom to interface with the host application program the user is viewing on display screen 20. Manipulandum 34 can be a joystick, mouse, trackball, stylus (e.g. at the end of a linkage), steering wheel, sphere, medical instrument (laparoscope, catheter, etc.), pool cue (e.g. moving the cue through actuated rollers), hand grip, knob, button, or other object. Mechanisms which may be used to provide the degrees of freedom to the user object include gimbal mechanisms, slotted yoke mechanisms, flexure mechanisms, etc. Various embodiments of suitable mechanisms are described in U.S. Pat. Nos. 5,767,839, 5,721,566, 5,623,582, 5,805,140, 5,825,308, and patent application Ser. Nos. 08/965,720, 09/058,259, and 09/138,304, all incorporated herein by reference.
[0031] A mechanical transmission can be connected between the actuator and the manipulandum and/or between the sensor and the manipulandum. The invention described herein is most suitable for devices including a transmission between the sensor and the manipulandum, since the transmission typically causes the most position slip in the device. Mechanical transmissions can include belt drive transmissions, capstan (cable) drive transmissions, and gear transmissions, many of which are described in greater detail in the patents and patent applications incorporated above. Furthermore, other compliance issues that may occur are described in copending patent application Ser. No. 09/138,309, incorporated herein by reference.
[0032] FIG. 2 is a top plan view of one example of a interior portion 50 of a force feedback mouse interface device 14 that can make use of the present invention. Mouse 54 (shown in dashed lines) is the manipulandum 34 which the user grasps and moves in planar degrees of freedom, similar to a traditional mouse. A mouse device similar to mouse device 50 is described in copending application Ser. Nos. 08/881,691 and 08/965,720, both incorporated herein by reference. Unlike a traditional mouse, mouse 54 has hard limits to its motion in its planar workspace due to it being attached to the mechanical linkage, described below.
[0033] Mechanical linkage 52 provides support for a mouse 54 and couples the mouse to a grounded surface 56, such as a tabletop or other support. Linkage 60 is, in the described embodiment, a 5-member (or “5-bar”) linkage including a ground member 62 (the base), a first base member 64 coupled to ground member 62, a second base member 68 coupled to ground member 62, a first link member 66 coupled to base member 64, and a second link member 70 coupled to link member 66 and base member 68. Mouse 54 is coupled to the linkage at the coupling between link members 66 and 70. Ground member 62 of the linkage 60 is a base for the support of the linkage and is coupled to or resting on ground surface 56. Fewer or greater numbers of members in the linkage can be provided in alternate embodiments.
[0034] The members of linkage 60 are rotatably coupled to one another through the use of rotatable pivots or bearing assemblies having one or more bearings, all referred to as “bearings” herein. Base member 64 is rotatably coupled to ground member 62 by a grounded bearing 72 and can rotate about an axis A. Link member 66 is rotatably coupled to base member 64 by bearing 74 and can rotate about a floating axis B, and base member 68 is rotatably coupled to ground member 62 by bearing 72 and can rotate about axis A. Link member 70 is rotatably coupled to base member 68 by bearing 76 and can rotate about floating axis C, and link member 70 is also rotatably coupled to link member 66 by bearing 78 such that link member 70 and link member 66 may rotate relative to each other about floating axis D. In an alternate embodiment, link member 66 can be coupled at its end to a mid-portion of link member 70 and mouse 54 can be coupled to the end of link member 70. Mouse 54 in the preferred embodiment is coupled to link members 66 and 70 by rotary bearing 78.
[0035] Linkage 60 is formed as a five-member closed-loop chain. Each member in the chain is rotatably coupled to two other members of the chain. The five-member linkage is a planar linkage that is arranged such that the members can rotate about their respective axes to provide mouse 54 with two degrees of freedom, i.e., mouse 54 can be moved within a planar workspace defined by the x-y plane, which is defined by the x- and y-axes.
[0036] Sensors 82a and 82b collectively sense the movement of the mouse 54 in the provided degrees of freedom and send appropriate signals to the electronic portion of interface device 14. Sensor 82a senses movement of link member 68 about axis A, and sensor 82b senses movement of base member 64 about axis A. These sensed positions about axis A allow the determination of the position of mouse 54 using known constants such as the lengths of the members of linkage 60 and using well-known coordinate transformations. Sensors 82, as described, use gear transmissions and thus can be subject to slip with respect to the manipulandum. The sensors are described in greater detail below with respect to FIG. 3 .
[0037] Actuators 84a and 84b to transmit forces to mouse 54 in space, i.e., in two (or more) degrees of freedom of the user object. In the preferred embodiment, actuators 84a and 84b are electromagnetic voice coil actuators which provide force through the interaction of a current in a magnetic field. These types of actuators are described in detail in patent application Ser. Nos. 08/560,091, 08/881,691, and 08/965,720, all incorporated by reference herein. In other embodiments, other types of actuators can be used, both active and passive, such as DC motors, pneumatic motors, passive friction brakes, passive fluid-controlled brakes, etc.
[0038] The housing plate of a grounded portion of actuator 84a is rigidly coupled to ground member 62 (or grounded surface 56) and a moving portion of actuator 84a (preferably a coil) is integrated into the base member 64. The actuator 84a transmits rotational forces to base member 64 about axis A. The housing plate of the grounded portion of actuator 84b is rigidly coupled to ground member 62 or ground surface 56 through the grounded housing of actuator 84b, and a moving portion (preferably a coil) of actuator 84b is integrated into base member 68. Actuator 84b transmits rotational forces to link member 68 about axis A. The combination of these rotational forces about axis A allows forces to be transmitted to mouse 54 in all directions in the planar workspace provided by linkage 60 through the rotational interaction of the members of linkage 60.
[0039] Base member 64 includes an integrated coil portion 90a on which a wire coil 92a is provided; Wire coil 92a includes at least two loops of wire wound on a portion 90a, e.g. 222 loops, in the described embodiment, are wound like a spool about a center portion of portion 90a. Terminals (not shown) from wire coil 82a to the electronic portion of the interface device are provided so that host computer. 18 or local microprocessor 26 can control the direction and/or magnitude of the current in wire coil.
[0040] Voice coil actuator 84a also includes a magnet assembly 98a, which is grounded and preferably includes four magnets 100a and a flux plate 102a Opposite polarities of magnets 100 face each other, such that coil 92a is positioned between opposing polarities on either side of the coil. The magnetic flux guide surrounding the magnets is provided as, in the described embodiment, metal plate 102a provided on the top side of the magnets 100a and metal base plate 85 provided on the bottom side of the actuator 84a. Plates 102a and 85 house actuator 84a to allow magnetic flux from magnets 100a to travel from one end of the magnets 100a to the other end.
[0041] The magnetic fields from magnets 90a interact with a magnetic field produced from wire coil 82a when current is flowed in coil 82a, thereby producing forces on member 64. The magnitude or strength of the force is dependent on the magnitude of the current that is applied to the coil, the number of loops in the coil, and the magnetic field strength of the magnets. The direction of the force depends on the direction of the current in the coil; the force can be applied in either direction about axis A. Force can thus be applied to member 64 and through member 66, thereby applying force to mouse 54 in the x-y plane workspace of the mouse. Stop supports 91 can be provided at each end of the range of motion of the member 64 about axis A to provide a limited angular range.
[0042] Voice coil actuator 64b operates similarly to actuator 64a. A current is flowed through coil 82b to cause interaction with a magnetic field from magnets 100b of magnet assembly 98b which is similar to the magnet assembly 98a described above, and inducing magnetic forces that rotate portion 90b of base member 68 about axis A. This causes forces to be applied to mouse 54 in the x-y workspace of the mouse through the member 68 and member 70.
[0043] In alternate embodiments, the mechanical linkage 60 can be replaced by other mechanical linkages or structures which can provide desired degrees of freedom. For example, linear motion can be provided. In other embodiments, other types of actuators may be used in place of or in addition to actuators 84 of the interface device. For example, the linkage can be driven by a direct drive DC motor or a geared/belt DC motor to provide mechanical advantage.
Sensing Position Slip in Interface Devices
[0044] In some interface devices, slip may occur between the sensor and the manipulandum, where the manipulandum is moved and the sensor does not detect or detects inaccurately the movement of the manipulandum in one or more degrees of freedom of the manipulandum. Slip is often a greater problem when a mechanical transmission is provided between the sensor and the manipulandum. Mechanical transmissions are typically provided in such a configuration to amplify the motion of a moving sensor member (such as an encoder wheel) for a given amount of motion of the manipulandum, thereby increasing the sensing resolution of the sensor. Examples of such mechanical transmissions include gear drives, belt drives, and capstan drives.
[0045] Slip can cause problems in the display of graphical objects or interactions on a display screen of computer device, since the host computer controlling the display assumes the manipulandum is in a particular position when it may actually be in a different position; the difference is due to the slip. Furthermore, with respect to force feedback interface devices, many types of force sensations output by the device, such as spring forces, damping forces, attractive forces, texture forces, periodic forces activated based on position, etc., depend at least in part on the position of the manipulandum and can be distorted to varying degrees if slip occurs.
[0046] The present invention detects slip so as to reduce or eliminate these undesired effects. One aspect of the present invention for detecting the slip in a device uses a reference sensor (or “index sensor”) that is connected directly to the manipulandum. In a simple case, this sensor can provide a digital flag signal that changes state when the, manipulandum travels past a predetermined location (or one of several different locations) in its range of travel or workspace. The important aspect of the reference sensor is that it is connected to the manipulandum “before” any mechanical transmission, i.e. there is no transmission mechanism between the reference sensor and the manipulandum. It is therefore not possible to generate transmission-induced slippage between the manipulandum and the reference sensor. In general, there is preferably one reference sensor for each degree of freedom of the manipulandum that is sensed on the device.
[0047] One example of a reference sensor is an emitter/detector pair similar to those used in standard optical encoders. This sensor can be used, for example, to detect the edges of a “flag,” e.g., a reference location such as a mark, edge, or other distinguishing feature, as it moves past the sensor position. Multiple flags can be used to generate several possible different index locations that are sensed during the motion of the manipulandum.
[0048] FIG. 3 is a perspective view illustrating one embodiment of the reference sensor of the present invention in use with the force feedback mouse embodiment shown in FIG. 2 . A mechanical member 101 is directly connected to the manipulandum with no mechanical transmission positioned therebetween. Member 101, for example, is shown as the end of a mechanical member 64 or 68 of the force feedback mouse device shown in FIG. 2 , in which a wire coil is coupled to the member to pass through a magnetic field and generate a force on the manipulandum. Member 101 rotates about an axis A as shown by arrows 107.
[0049] At one end of member 101 is sensor 62a or 62b as shown in FIG. 2 , which includes a gear transmission mechanism 103. Mechanism 103 includes teeth 104 coupled to the member 101 and a gear 106 which—includes gear teeth about—its circumferential surface that interlock with the teeth 104. When member 101 moves, gear 106 thus rotates about axis E. Gear 106 is rigidly coupled to an encoder disk 108 by a shaft 110, where the encoder disk includes a number of marks or slots 112 that rotate through one or more emitter-detectors 114. The emitter-detectors 114 sense the motion of member 101 by detecting the passage of the marks or slots (“counts”), as is well known to those skilled in the art. Gear 106 can be biased to engage the teeth 104 by a pivotable spring-loaded member 116 which presses the gear 106 to engage the teeth 104 and pivots about a grounded coupling 105.
[0050] A reference sensor of the present invention can take many forms. One embodiment provides a grounded emitter 120 and a grounded detector 122 positioned on opposite sides of the member 101 somewhere in the range of motion of the member, such as approximately in the center of the range of motion. The emitter 120 emits a beam 124 that is blocked by the member 101 from reaching the detector 122. An aperture 126 is placed in the member 101, the aperture extending the entire thickness t of the member and allowing the beam 124 to reach the detector 122 when the member 101 is in a position placing the aperture 126 directly in the path of the beam 124. Thus, the detector will detect a change in state (producing a signal edge) three times during a motion in a single direction, assuming the member 101 starts in a position completely outside the beam: when one (or either) outside edge or side 127 of the member 101 moves to block the beam, when a first-encountered physical edge of the aperture 126 allows the beam to be transmitted, and when the second-encountered physical edge of the aperture 126 again blocks the beam in other embodiments, a different number of changes in state can be detected; for example, only the side of the member 101 need be detected.
[0051] Alternatively, other reference sensors can be used. For example, one or more members can be placed extending out from the member 101, where the extending members successively moves through an emitted horizontally-aligned beam of an optical sensor as the member 101 moves. Other types of optical sensors, such as phototransistor, photodiode, and photoresistor sensors, can be used. Magnetic sensors can also be used in some embodiments.
[0052] It should be noted that, in other embodiments, other types of interface devices can be used with the reference sensor of the present invention. For example, interface devices such as a joystick, trackball, rotatable cylinder, steering wheel, gamepad, or other types of mice can be used. For example, a joystick handle can include a member extending from its lower section which crosses a beam of an emitter-detector. The closer the sensor is positioned to the actual manipulandum, the more accurate is the reference position sensed as an indication of actual manipulandum position.
[0053] FIG. 4 is a flow diagram illustrating a first method 200 of the present invention of sensing motion of a manipulandum of an interface device while compensating for slippage between sensor and manipulandum. This method can be performed by program code running on the local microprocessor, host computer, or other controlling device.
[0054] The process begins at step 202. In a step 204, a device position delta (change from the last position) is determined from the position sensor. This is obtained by reading a current device position and finding the difference between the current position and the last sensed device position. In step 206, the process checks whether a slip in position has been detected by using the reference sensor(s) described above. The details of determining if a slip has occurred are detailed below with respect to FIG. 5 . This step also preferably provides the amount of slip that has occurred. If slip has not been detected, then in step 208 a computation value is determined using the position delta determined in step 204. The “computation value” is the position value that is used for displaying and computation purposes, e.g. by the host computer, as opposed to the device position value which is the position of the manipulandum in its workspace. For example, a computation value can be determined in one embodiment by simply adding the sensed position delta to the previously-used computation value to achieve the current computation value. Alternatively, the position delta can be factored into a more complicated computation value that depends also on other factors. For example, a ballistics algorithm can be used which determines a computation value based on factors such as the manipulandum velocity and the location of the manipulandum within its workspace. Some ballistics methods are described in greater detail in copending patent application Ser. No. 08/924,462, incorporated herein by reference. Once the computation value is determined, the process continues to step 214 where the host computer's display is updated based on the computation value, and other processes using the computation value can be performed (force computation, etc.). For example, if the computation value is determined by a device processor, the computation value can be sent to the host computer as a cursor location which updates the display of a cursor on the screen. Or, the motion of a displayed user-controlled entity or viewpoint in a game or simulation can be updated. The process then returns to step 204.
[0055] If slip has been detected in step 206, then in step 209 the device updates the device position value using the amount of slip detected in step 206, and uses this as the current device position. This corrected device position allows the device to accurately determine when, for example, the manipulandum hits a limit to its workspace. In step 210, the process determines the computation value without the use of the position delta resulting from the slip updating in step 209. The slipped position delta from step 209 has been corrected and may include a large jump in position, and it is not desired to update the display screen in accordance with this jump since such a jump can be disconcerting to the user. For example, in systems where the absolute position of the device is being used to position an object in a graphical environment having the same proportional dimensions, this discontinuity can be disconcerting for the user. If the manipulandum position is displayed graphically as a graphical object on the display screen, then a sudden jump in the displayed location of the graphical object will occur if the slippage is included in the computation value. Furthermore, if the manipulandum position is being used in force feedback embodiments for force computations, then a sudden, unexpected force change may occur that is noticeable to the user. Thus, the computation value in step 208 is determined without using the slippage position delta determined in step 209 to prevent any significant discontinuities from occurring in computation value and in the display. In a simple case, this means that the last-computed computation value is simply used again as the current computation value, i.e. the display does not change. The current device position is still saved to be used as the “last” device position in the next iteration so that the next determined position delta is determined correctly.
[0056] In next step 212, if the current position of the manipulandum indicates that the manipulandum is at a limit to its workspace, then the computation value should be compensated for this event. This compensation allows recovery of the situation in which the device position is at one of its limits and the computation position has not reached a limit value (such as the edge of the screen). In such a case, without compensation, the user would try to continue to move the cursor (or other object) towards the edge of the screen, but could not since the manipulandum has encountered a hard limit to its motion. This situation can happen more frequently if the slip described herein is present in the device, since the slip increases any offset between device position in its workspace and screen cursor position on the display screen. Furthermore, the display from the computation value used in step 210 may cause a greater offset. To mitigate this situation, the computation value can be modified to allow the user to continue to move the cursor when the manipulandum has reached a physical limit. For example, in one embodiment, rate control limits are provided, in which the user can move the mouse into a border region of its workspace; the amount of distance moved into the border region controls the rate of speed of motion of the cursor in a corresponding direction. In a different embodiment, once the device reaches a predetermined distance to a limit, the remaining distance the cursor must travel to reach a screen limit is determined and an appropriate scaling factor is applied to the motion of the cursor to allow it to reach the screen limit when the device limit is reached. These and other methods are described in greater detail in copending application Ser. No. 08/924,462, incorporated herein by reference.
[0057] In next step 214, the computation value is used to update the display of the host computer and update other processes (force computation, etc.). The process then returns to step 204.
[0058] FIG. 5 is a flow diagram 230 illustrating the step 206 of FIG. 4 in which position slip is detected. The process begins at 232, and in step 234, the process checks whether a signal edge is detected in the output of the reference sensor. The signal edge indicates that the sensing of a flag or reference location has occurred. If no signal edge is sensed, then no reference location has been sensed, and the process is complete at 236. If a signal edge has been detected, then in step 238 the process immediately reads a position value that corresponds with the signal edge from the position sensor and stores this position value (or the device position read in step 204 of FIG. 4 can be used as the corresponding device position if it was read sufficiently close in time to the signal edge).
[0059] In step 240, the process determines which reference location in the range of motion of the member 101 is being sensed. For example, three different reference locations are sensed in the embodiment of FIG. 3 , including one side of the member 101 and the two sides of the aperture 126. Each reference location is associated with a stored reference position value. To determine which of these reference locations was sensed, different methods can be used. In one method, the reference sensor can detect 2 different types of signal edges (rising or, falling edge), and the process can use the information of which type of edge was detected to determine which reference location is being sensed. Thus, the first encountered reference location may produce a rising edge, the second location may produce a falling edge, and the third encountered location may produce a rising edge. The process can further examine the current direction of member 101 to help determine which reference location was sensed, e.g. the reference locations are encountered in a particular order depending on the direction of travel of the member 101.
[0060] In next step 242, the process checks if it is the first time that a reference location has been sensed. If it is the first time, then the position value read at step 238 is stored at step 244 to correspond to the identified reference location and the process is complete at 236. In addition, a determination of no slippage is assumed at this stage and returned to the main process of FIG. 4 . Since there is only one position value known to, correspond with the reference location, no comparison with previous positions at that location can be made, so that no slippage can be determined. In one preferred embodiment, a number of position values are stored for the first few times that signal edges are first detected before slippage is computed so that a stable, accurate reference location position is obtained. For example, the first position value that does not significantly deviate after five consecutive sensings is established as the position value for that reference location, and only after that position is established does the process check for slippage starting at step 246.
[0061] If it is not the first time that the reference location has been sensed (or the position value for that reference location is otherwise established), then in step 246 the process compares the current position value to the most recent, previously stored position value for this reference location. In step 248, the slip amount is determined as the difference between these position values. If the slip value is zero, then it indicates that no slippage has occurred. If the slip value is a nonzero value, then some slippage has occurred, since a single reference location has been sensed at a different position of member 101. In step 250, the process checks if the slip amount is greater than a predetermined threshold; this threshold should at least be larger than the possible variation in the reference sensor position produced by the sensor device being used. If the slip 10 amount is less than the threshold, the slip amount is too low to be worth compensating, and no slip is considered to be detected at step 252. The process is then complete at 256. If the slip amount is greater than the threshold in step 250, then in step 254 then slip is considered to have been detected, and all stored reference position values are updated with the slip amount. Since slip has occurred and the reference locations are now being detected at a new position, the stored reference positions for those locations must be updated so that any additional slip can be detected if it occurs. For example, the position values corresponding to all three reference locations in the embodiment of FIG. 3 are all updated by adding the slip amount to each position value; this prevents the same slip from being detected again when the next reference position on member 101 is detected. The process is then complete at 256.
[0062] A special case exists when the mechanical transmission that is used in the device skips only in discrete units. An example of this case is a gear drive transmission, such as shown in FIG. 3 . When a transmission such as this is employed, it is known that any slippage that occurs in the system will be equivalent to a change of one discrete unit of the transmission. In a geared system, this means that any observed slips will always be a certain number of gear teeth that have been jumped over. Since the number of position sensor counts that occur for each gear position is fixed (call this value N), all actual slip in the system will be in multiples of the value N. Since N is typically several sensor counts (when using a digital encoder sensor), this allows the detection of slip to be easier and the updating of reference position values to be more accurate.
[0063] FIG. 6 is a flow diagram illustrating a second method 280 of the present invention of sensing motion of a manipulandum of an interface device while compensating for slippage between sensor and manipulandum. In this method, slippage is not ignored for computation value purposes, so that the screen display is correlated with slipped device position smoothly and the offset between device position and screen display is corrected over time. Basically, small “corrections” are applied to the device position delta values in order to reduce slippage error. These corrections are then also subtracted out of the error value. This process is continued until the error values are reduced to zero and the actual manipulandum position matches the sensed manipulandum position. The result is that the computation value slowly approaches the correct value as the error values are reduced. This allows this second method to be used in embodiments that are not using rate control borders, scaling, or other methods that allow a user to continue to control a cursor after a device limit has been reached. This method can be more suitable for devices providing absolute position mapping with no great changes to computation position, such as in most joystick embodiments.
[0064] The process begins at 282, and in step 284, the process determines the device position delta, similar to step 204 of FIG. 4 . In step 286, the process determines if slip has occurred, similar to step 206 of FIG. 4 . If slip has occurred, then in step 288 an error value is set equal to the previous error value plus the current slip amount found in step 286 (the error value is initially set to zero upon device start-up). The error value is thus a total indication of slip that has occurred during device operation, including slip amounts from previous slippage occurrences and adjustments from manipulandum movement (described below). After step 288, or if no slip has been detected in step 286, then step 290 is performed, in which the process checks whether the error value is currently is nonzero. If not, i.e. if the error value is zero, then no slippage needs to be compensated for and in step 298 the position delta from step 284 is used to determine the computation value without correction. The computation value can then be used for display purposes, force computation purposes, etc. The process then returns to step 284.
[0065] If the error value is nonzero in step 290, then in step 292 the process checks whether the manipulandum or member 101) is moving. This check is performed so that computation value corrections do not cause disconcerting effects to the user that may occur if the manipulandum is not moving, e.g. the mouse may be stationary yet the cursor may be moving to correct for slippage. To avoid this, computation value corrections are preferably made only when the manipulandum is moving. Thus, if the manipulandum is moving in step 292, the process continues to step 298 to determine a computation value normally. If the manipulandum is moving, the process continues to step 294 to adjust the position delta (described below). In some embodiments, to allow computation value corrections when a device limit has been reached (and the manipulandum is stationary), a check can be made for the amount of time that the manipulandum has been stationary. For example, if the manipulandum is stationary for a predetermined number of iterations, then the manipulandum can be considered moving. A check can also be made whether the manipulandum is positioned at a device limit.
[0066] In step 294, the position delta determined in step 284 is adjusted based on the error value. This can be implemented in many ways. For example, in one embodiment, the position delta can be adjusted by adding or subtracting a predetermined number of counts (or other sensor measurement units) to the current device position, thereby changing the position delta, to compensate for the slippage. The number of counts is preferably small enough so that the adjustment is not easily noticed by the user. This may cause the slippage error to be fully corrected only after multiple iterations of the process 280, since the error value could be much larger than the adjustment made. However, such slow correction is desired to prevent the user from noticing the correction process.
[0067] Alternatively, the adjustment can be proportional to the size of the current error value, where larger error values cause larger adjustments (with a maximum limit to the size of the adjustment so that the user will not easily notice the adjustments). In some embodiments, each adjustment or correction in the loop, of method 280 can depend on the current manipulandum position in its workspace. For example, if the manipulandum is moved by the user to an actual position that would increase the slippage amount (if the incorrect sensed position were held stationary), then a greater adjustment can be applied. If, however, the manipulandum is moved by the user to an actual position that would decrease the slippage amount (if the incorrect sensed position were held stationary), then a smaller correction can be applied, since the manipulandum motion is already helping to decrease the slippage error by being in the direction of decreasing the slippage delta.
[0068] After step 294, the process adjusts the error value by the amount of the adjustment made in step 294. Thus, if 10 counts were added to the position delta in step 294, the error value can be reduced by 10 counts. The process then continues to step 298 to determined a computation value that is based on the adjusted position delta. This allows the graphical display (and other computations based on device position) to be correlated with a device position that is slowly being corrected to remove slippage error. At some iteration, the error value has been reduced in size sufficiently so that the last adjustment at step 296 causes the error value to be zero, and slippage error has been eliminated from the system.
[0069] While this invention has been described in terms of several preferred embodiments, it is contemplated that alterations, permutations and equivalents thereof will become apparent to those skilled in the art upon a reading of the specification and study of the drawings. For example, many different types of interface devices, both force feedback and non-force feedback, may be used with the position sensing techniques described herein. Furthermore, certain terminology has been used for the purposes of descriptive clarity, and not to limit the present invention. It is therefore intended that the following appended claims include alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.
Claims
That which is claimed is:
1. A method comprising:
determining a device position delta from a sensed position of a manipulandum of an interface device in a degree of freedom, the position delta indicating a change in an actual position of the manipulandum;
determining if a position slip has occurred in a position sensing system, the position slip caused by a change in position of the manipulandum not sensed by a sensor of the interface device;
correcting an error in the sensed position caused by the position slip by adjusting the sensed position to take into account the position slip, and using the adjusted position as the actual position of the manipulandum; and
using the sensed position of the manipulandum as the actual position of the manipulandum if the manipulandum is not moving in the degree of freedom.
2. A method as recited in claim 1 wherein the determining if the position slip has occurred comprises checking a reference signal from a reference sensor coupled to the interface device, the reference sensor detecting a position of a reference location of the manipulandum.
3. A method as recited in claim 1 further comprising determining a computation value from the device position delta, and outputting the computation value.
4. A method as recited in claim 3 further comprising disregarding the position slip when determining the computation value.
5. A method as recited in claim 1 wherein the position slip comprises slip caused by a mechanical transmission coupled between the sensor and the manipulandum.
6. A method as recited in claim 5 wherein the mechanical transmission comprises a drive selected from the group consisting of a gear drive, a belt drive, and a capstan drive.
7. A device comprising:
a manipulandum movable in at least one degree of freedom;
a position sensor operative to detect a position of the manipulandum in the at least one degree of freedom;
a mechanical transmission coupled between the manipulandum and the position sensor;
a reference sensor operative to detect a motion of at least one reference location of the manipulandum; and
a local microprocessor operable to receive the reference signal and operable to adjust the detected position of the manipulandum if position slip has occurred and to use the detected position of the manipulandum as the actual position of the manipulandum if the manipulandum is not moving in the degree of freedom.
8. A device as recited in claim 7 wherein the mechanical transmission comprises a gear drive.
9. A device as recited in claim 7 wherein the mechanical transmission comprises a belt drive.
10. A device as recited in claim 7 wherein the position sensor comprises a relative digital encoder.
11. A device as recited in claim 7 wherein the local microprocessor is operable to determine a computation value from a position delta determined from the position, and to adjust the computation value if the position slip has occurred.
12. A non-transitory computer-readable medium on which is encoded program code to cause a processor to execute a method, comprising:
determining a device position delta from a sensed position of a manipulandum of an interface device in a degree of freedom, the position delta indicating a change in an actual position of the manipulandum;
determining if a position slip has occurred in a position sensing system, the position slip caused by a change in position of the manipulandum not sensed by a sensor of the interface device;
correcting an error in the sensed position caused by the position slip by adjusting the sensed position to take into account the position slip, and using the adjusted position as the actual position of the manipulandum;
using the sensed position of the manipulandum as the actual position of the manipulandum if the manipulandum is not moving in the degree of freedom.
13. The non-transitory computer-readable medium as recited in claim 12 wherein the determining if the position slip has occurred comprises checking a reference signal from a reference sensor coupled to the interface device, the reference sensor detecting a position of a reference location of the manipulandum.
14. The non-transitory computer-readable medium as recited in claim 12 further comprising determining a computation value from the device position delta, and outputting the computation value.
15. The non-transitory computer-readable medium as recited in claim 14 further comprising determining a force having a magnitude and a direction at least partially based on the computation value, and outputting the force with an actuator disposed within the interface device.
16. The non-transitory computer-readable medium as recited in claim 12 further comprising performing the determining a device position, the determining if a position slip has occurred, and the correcting an error over a plurality of iterations, and adjusting the sensed position by an amount which gradually reduces the error in the sensed position over the plurality of iterations.
17. The non-transitory computer-readable medium as recited in claim 12 further comprising using the sensed position of the manipulandum as the actual position of the manipulandum if the manipulandum is not moving in the degree of freedom.
Patent Citations (104)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3832895(A) | 1974-09-01 | Strandh | Applicant |
| US3919691(A) | 1975-11-01 | Noll | Applicant |
| US4103155(A) | 1978-07-01 | Clark | Applicant |
| US4148014(A) | 1979-04-01 | Burson | Applicant |
| US4398889(A) | 1983-08-01 | Lam et al. | Applicant |
| US4477043(A) | 1984-10-01 | Repperger | Applicant |
| US4560983(A) | 1985-12-01 | Williams | Applicant |
| US4637264(A) | 1987-01-01 | Takahashi et al. | Applicant |
| US4678908(A) | 1987-07-01 | LaPlante | Applicant |
| US4689449(A) | 1987-08-01 | Rosen | Applicant |
| US4692756(A) | 1987-09-01 | Clark | Applicant |
| US4696445(A) | 1987-09-01 | Wright et al. | Applicant |
| US4706294(A) | 1987-11-01 | Ouchida | Applicant |
| US4712101(A) | 1987-12-01 | Culver | Applicant |
| US4712971(A) | 1987-12-01 | Fyler | Applicant |
| US4767923(A) | 1988-08-01 | Yuasa | Applicant |
| US4794384(A) | 1988-12-01 | Jackson | Applicant |
| US4800721(A) | 1989-01-01 | Cemenska et al. | Applicant |
| US4823634(A) | 1989-04-01 | Culver | Applicant |
| US4825157(A) | 1989-04-01 | Mikan | Applicant |
| US4861269(A) | 1989-08-01 | Meenen, Jr. | Applicant |
| US4868549(A) | 1989-09-01 | Affinito et al. | Applicant |
| US4906843(A) | 1990-03-01 | Jones et al. | Applicant |
| US4949119(A) | 1990-08-01 | Moncrief et al. | Applicant |
| US5006703(A) | 1991-04-01 | Shikunami et al. | Applicant |
| US5044956(A) | 1991-09-01 | Behensky et al. | Applicant |
| US5065145(A) | 1991-11-01 | Purcell | Applicant |
| US5086401(A) | 1992-02-01 | Glassman et al. | Applicant |
| US5103404(A) | 1992-04-01 | McIntosh | Applicant |
| US5138154(A) | 1992-08-01 | Hotelling | Applicant |
| US5146566(A) | 1992-09-01 | Hollis, Jr. | Applicant |
| US5159990(A) | 1992-11-01 | Abe et al. | Examiner |
| US5184319(A) | 1993-02-01 | Kramer | Applicant |
| US5193963(A) | 1993-03-01 | McAffee et al. | Applicant |
| US5197003(A) | 1993-03-01 | Moncrief et al. | Applicant |
| US5204600(A) | 1993-04-01 | Kahkoska | Applicant |
| US5209131(A) | 1993-05-01 | Baxter | Applicant |
| US5209661(A) | 1993-05-01 | Hildreth et al. | Applicant |
| US5228356(A) | 1993-07-01 | Chuang | Applicant |
| US5254919(A) | 1993-10-01 | Bridges et al. | Applicant |
| US5264768(A) | 1993-11-01 | Gregory et al. | Applicant |
| US5327790(A) | 1994-07-01 | Levin et al. | Applicant |
| US5402680(A) | 1995-04-01 | Korenaga | Applicant |
| US5436638(A) | 1995-07-01 | Bolas et al. | Applicant |
| US5473344(A) | 1995-12-01 | Bacon et al. | Applicant |
| US5477237(A) | 1995-12-01 | Parks | Applicant |
| US5491477(A) | 1996-02-01 | Clark et al. | Applicant |
| US5532585(A) | 1996-07-01 | Oudet et al. | Applicant |
| US5576704(A) | 1996-11-01 | Baker et al. | Applicant |
| US5583407(A) | 1996-12-01 | Yamaguchi | Applicant |
| US5587937(A) | 1996-12-01 | Massie et al. | Applicant |
| US5589828(A) | 1996-12-01 | Armstrong | Applicant |
| US5591924(A) | 1997-01-01 | Hilton | Applicant |
| US5592401(A) | 1997-01-01 | Kramer | Applicant |
| US5611731(A) | 1997-03-01 | Bouton et al. | Applicant |
| US5629594(A) | 1997-05-01 | Jacobus et al. | Applicant |
| US5642469(A) | 1997-06-01 | Hannaford et al. | Applicant |
| US5643087(A) | 1997-07-01 | Marcus et al. | Applicant |
| US5687080(A) | 1997-11-01 | Hoyt et al. | Applicant |
| US5694153(A) | 1997-12-01 | Aoyagi et al. | Applicant |
| US5701140(A) | 1997-12-01 | Rosenberg et al. | Applicant |
| US5712725(A) | 1998-01-01 | Faltermeier et al. | Applicant |
| US5724068(A) | 1998-03-01 | Sanchez et al. | Applicant |
| US5724264(A) | 1998-03-01 | Rosenberg et al. | Applicant |
| US5734373(A) | 1998-03-01 | Rosenberg et al. | Applicant |
| US5742278(A) | 1998-04-01 | Chen | Applicant |
| US5749577(A) | 1998-05-01 | Couch et al. | Applicant |
| US5755577(A) | 1998-05-01 | Gillio | Applicant |
| US5760764(A) | 1998-06-01 | Martinelli | Applicant |
| US5763874(A) | 1998-06-01 | Luciano et al. | Applicant |
| US5767839(A) | 1998-06-01 | Rosenberg | Applicant |
| US5790108(A) | 1998-08-01 | Salcudean et al. | Applicant |
| US5805140(A) | 1998-09-01 | Rosenberg et al. | Applicant |
| US5821920(A) | 1998-10-01 | Rosenberg et al. | Applicant |
| US5825308(A) | 1998-10-01 | Rosenberg | Applicant |
| US5841428(A) | 1998-11-01 | Jaeger et al. | Applicant |
| US5844673(A) | 1998-12-01 | Ivers | Applicant |
| US5889670(A) | 1999-03-01 | Schuler et al. | Applicant |
| US5907487(A) | 1999-05-01 | Rosenberg et al. | Applicant |
| US5912661(A) | 1999-06-01 | Siddiqui | Applicant |
| US5944151(A) | 1999-08-01 | Jakobs et al. | Applicant |
| US5984785(A) | 1999-11-01 | Takeda et al. | Applicant |
| US5990869(A) | 1999-11-01 | Kubica et al. | Applicant |
| US6001014(A) | 1999-12-01 | Ogata et al. | Applicant |
| US6004134(A) | 1999-12-01 | Marcus et al. | Applicant |
| US6020876(A) | 2000-02-01 | Rosenberg et al. | Applicant |
| US6031222(A) | 2000-02-01 | Carapelli | Applicant |
| US6067077(A) | 2000-05-01 | Martin et al. | Applicant |
| US6100874(A) | 2000-08-01 | Schena et al. | Applicant |
| US6104379(A) | 2000-08-01 | Petrich et al. | Applicant |
| US6104382(A) | 2000-08-01 | Martin et al. | Applicant |
| US6166723(A) | 2000-12-01 | Schena et al. | Applicant |
| US6219034(B1) | 2001-04-01 | Elbing et al. | Applicant |
| US6252579(B1) | 2001-06-01 | Rosenberg et al. | Applicant |
| US6259433(B1) | 2001-07-01 | Meyers | Applicant |
| US6275213(B1) | 2001-08-01 | Tremblay et al. | Applicant |
| EP85518(A1) | 1983-08-01 | Applicant | |
| EP626634 | 1994-11-01 | Applicant | |
| EP640902(A2) | 1995-03-01 | Applicant | |
| JP1-003664 | 1990-07-01 | Applicant | |
| JP2-109714 | 1992-01-01 | Applicant | |
| JP4-007371 | 1993-08-01 | Applicant | |
| JP5-193862 | 1995-01-01 | Applicant | |
| WO9520788 | 1995-08-01 | Applicant |
Non-Patent Literature (20)
- Helmers, C., In the Beginning, Robotics Age magazine, Hayden Book Co., 1983, pp. 12-19.Applicant
- Hirota, Koichi et al., “Development of Surface Display,” IEEE 0-7803-1363-1, 1993, pp. 256-262.Applicant
- Russo, “The Design and Implementation of a Three Degree-of-Frredom Force Output Joystick”, Submitted to the Department of Mechanical Engineering on May 11, 1990.Applicant
- Ellis, R.E. et al., “Design and Evaluation of a High-Performance Prototype Planar Haptic Interface,” ASME Dec. 3, 1993, DSC-vol. 49, pp. 55-64.Applicant
- Jacobsen, S.C. et al., “High Performance, High Dexterity, Force Reflective Teleoperator II,” ANS Topical on Robotics and Remote Systems, Feb. 24-27, 1991, pp. 1-10 and pp. 1-5 apndx.Applicant
- Adelstein, B. et al., “Design and Implementation of a Force Reflecting Manipulandum for Manual Control Research,” Dept. of Mech. Engineering, MIT, 1992, pp. 1-24.Applicant
- Hasser, C., “Tactile Feedback for a Force-Reflecting Haptic Display”, Univ. of Dayton, Dayton OH, 1995, pp. 1-96.Applicant
- Rosenberg et al., “Commercially Viable Force Feedback Controller for Individuals with Neuromotor Disabilities,” USAF Armstrong Lab. AL/CF-TR-1997-0016,1996, pp. 1-33.Applicant
- Akamatsu, M., et al., “Multimodal Mouse: A Mouse-Type Device with Tactile and Force Display”, Presence, vol. 3, No. 1, Winter 1994, pp. 73-80.Applicant
- Ramstein, C., “Combining Haptic and Braille Technologies: Design Issues and Pilot Study,” ASSETS '96, 2nd Annual ACM Conf. on Assistive Technologies, 1996, pp. 37-44.Applicant
- Kelley, A.J. et al., “MagicMouse: Tactile and Kinesthetic Feedback in the Human-Computer Interface using an Electromagnetically Actuated Input/Output Device,” Dept. of Elec. Engineering, Univ. of British Columbia, 1993, pp. 1-27.Applicant
- Schmult, Brian et al., “Application Areas for a Force-Feedback Joystick,” ASME 1993, DSC-vol. 49, pp. 47-54.Applicant
- Colgate, J. et al., “Implementation of Stiff Virtual Walls in Force-Reflecting Interfaces,” Sep. 22, 1993.Applicant
- Rutherford, M. “Third Generation Digital Flight Controls,” CAE Electronics, Ltd., The Royal Aeronautical Society, 1984 Spring Convention Future Applications and Prospects for Flight Simulation, May 9-10, 1984, paper No. 15.Applicant
- Iwata, H., “Artificial Reality with Force-feedback: Development of Desktop Virtual Space with Compact Master Manipulator,” Computer Graphics, vol. 24, No. 4, 1990, pp. 165-170.Applicant
- Corrao, Joseph M., “Control Loading,” American Institute of Aeronautics and Astronautic's Flight Simulation Update 1987, Jan. 12-16, 1987.Applicant
- Kaczmarek et al., “Tactile Displays,” Virtual Environment Technologies, May 1995.Applicant
- Ouhyoung et al., “The Development of a Low-Cost Force Feedback Joystick and Its Use in the Virtual Reality Environment,” Proceedings of the Third Pacific Conference on Computer Graphics and Applications, Pacific Graphics '95, Seoul, Korea, Aug. 21-24, 1995.Applicant
- Scannell, “Taking a Joystick Ride,” Computer Currents, Boston Edition, vol. 9, No. 11, Nov. 1994.Applicant
- United States Patent and Trademark Office, Office Action, U.S. Appl. No. 10/995,586, mailed Dec. 13, 2007.Applicant