VEHICLE INTERFACE TO COMMUNICATE A SAFETY ALERT MODE COMMAND

Abstract
One of the embodiments of the invention includes an interface for communicating a vehicle command from a user to a vehicle. The interface preferably includes an engagement system to engage the torso and an appendage of a user, a sensor system to sense forces imparted by the user, a processor to interpret the vehicle “safety alert mode” command based on a forceful shift of the user, to confirm that the user wishes to invoke the vehicle “safety alert mode” command, and to communicate the vehicle “safety alert mode” command to the vehicle. The vehicle, armed with this vehicle “safety alert mode” command, may initiate a defensive action, such as tightening the suspension.
Description
BRIEF DESCRIPTION OF THE FIGURES


FIGS. 1-3 include side and front views of the first preferred embodiment.



FIGS. 4-6 include side and front views of the second preferred embodiment.



FIGS. 7-9 include side and front views of the third preferred embodiment.



FIG. 10 includes side views of the fourth preferred embodiment.



FIG. 11 includes isometric views of the second variation of the engagement system, showing the seat bolsters in an “engaged” mode and a “relaxed” mode.



FIG. 12 includes a side view of the fourth preferred embodiment.







DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of five preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.


1. The Interface

As shown in the FIGS. 1-12, the interface 100 of the preferred embodiments includes an engagement system 110, a sensor system coupled to the engagement system 110, and a processor adapted to interpret a vehicle command based on an output from the sensor system and to communicate the vehicle command to a vehicle. While some of the vehicle commands are known in the art, the invention teaches a more intuitive interface to sense and interpret these commands. The invention, therefore, provides an interface 100 that senses and interprets new commands (such as a vehicle roll or pitch command in an automobile) that the user would not have been able to quickly activate with conventional interfaces, or more commands (such as a vehicle configuration command in an aircraft) that the user would not have been able to easily navigate with conventional interfaces. With this interface 100, the vehicle may be able to react better or faster to upcoming situations (such as a bump, a turn, or a climb), since the user may be able to communicate better or faster information to the vehicle. With this interface 100, the vehicle may also be able to perform better and/or the user may be able to perform with less mental or physical strain. The vehicle, it is hoped, will become a more natural (or intuitive) extension of the user with the incorporation of this invention.


The interface 100 of the preferred embodiments is preferably integrated into a vehicle. The vehicle is preferably a wheeled vehicle (such a two-wheeled bicycle or motorcycle, a three-wheeled cycle, a four-wheeled automobile, truck, or all-terrain vehicle, or a multi-wheeled tractor), a watercraft (such as a jet ski, a motorboat, or a submarine), an aircraft (such as a small plane, a helicopter, or a hovercraft), a tracked vehicle (such as a snowmobile or a tank), or a railed vehicle (such as a train). The vehicle may, however, be any suitable vehicle that transports people or cargo with either human power, fuel power, or any other suitable power source. Although the interface 100 is preferably integrated into a vehicle, the interface 100 may alternatively be remotely coupled to a vehicle or may alternatively be integrated into a virtual vehicle environment. Alternatively, the interface 100 may be integrated into any suitable environment.


The command communicated by the interface 100 of the preferred embodiment is preferably a vehicle command. The vehicle command is preferably an attitude command (such as a vehicle pitch or a vehicle roll), a handling command (such as a suspension command or a height command), a configuration command (such as a track command, a wheelbase command, a hull shape command, or a wing shape command), a mode command (such as a “safety alert mode” command), or a combination command (such as a “bunny hop” command). The command communicated by the interface 100 may, however, be any suitable command. Although the command is preferably communicated to a vehicle, the command may be communicated to any suitable device or system.


The engagement system 110 of the preferred embodiments functions to engage or support the user in the vehicle. In a first variation, as shown in FIGS. 1-3, the engagement system 110 supports at least a portion of the weight of the user, engages at least two appendages of the user, and includes: at least two of the following: a handbase 120, a footbase 130, and a seat 140. As best shown in FIG. 2A, the handbase 120 preferably includes a handlebar 122 with a left handgrip 124 engageable by the left hand of the user and a right handgrip 126 engageable by the right hand of the user. The footbase 130 preferably includes a left footrest 132 engageable by the left foot of the user and a right footrest 134 engageable by the right foot of the user. The handbase 120 and footbase 130 may alternatively include any suitable device or system to engage the hands and feet of the user. As best shown in FIG. 1A, the seat 140 preferably includes a straddle-type seat 140 (most commonly found on cycles and all-terrain vehicles) engageable by the lower torso of the user, but may alternatively include any suitable device to engage the lower torso of the user.


In a second variation, as shown in FIGS. 4-6 and 11, the engagement system 110 engages the torso of the user and includes at least two of the following: a seat back 142, a seat bottom 144, and side bolsters 146 and 148. The seat back 142 and the seat bottom 144 are preferably conventional seating elements, but may alternatively be any suitable system that engages the torso of the user, including a platform that supports the user in a prone position. The side bolsters 146 and 148 preferably include a left side bolster 146 engageable with the left side of the torso of the user and a right side bolster 148 engageable with a right side of the torso of the user. Preferably, the side bolsters 146 and 148 have an “engaged” position (FIG. 11A) in which they engage the torso of the user and a “relaxed” mode (FIG. 11B) in which they do not engage the torso user. The “engaged” and “relaxed” modes of the side bolsters 146 and 148 may be selected by the user by any suitable method (such as a finger-activated switch mounted on an instrument panel or a steering wheel, or a voice-activated switch), or may be selected by the vehicle upon the achievement of particular conditions.


In a third variation, as shown in FIGS. 7-9, the engagement system 110 is very similar to the engagement system 110 of the first variation except that at least a portion of engagement system 110 is movable from a first position to a second position. The movable portion of the engagement system 110 preferably includes two portions that are movable in opposite directions (either linearly or rotationally) from a “near position” to a “far position”, such as the handbase 120 and the footbase 130 that move in linearly opposite directions (FIG. 7) or rotationally opposite directions (FIG. 8), or the left handgrip 124 and the right handgrip 126 of the handbase 120 and/or the left footrest 132 and the right footrest 134 of the footbase 130 (FIG. 9). The movable portions of the engagement system 110 may be moved by the user, or may be moved by an actuator or any other suitable device.


In a fourth variation, as shown in FIG. 10, the engagement system 110 is very similar to the engagement system 110 of the second embodiment except that the engagement system 110 also includes a handbase 120, such as a steering wheel.


As shown in FIG. 12, the interface of the preferred embodiments may also include a second engagement system 110′. The second engagement system 110′ functions to engage or support a passenger in the vehicle. The second engagement system 110′ is preferably similar to the engagement system 110, but may alternatively be any suitable engagement system to support the passenger in the vehicle.


The sensor system of the preferred embodiments functions to sense an intuitive input from the user and to send a sensor output to the processor. In a first variation, as shown in FIGS. 1-3, the sensor system senses the weight distribution of the user. More particularly, the sensor system senses a shift in the weight distribution of the user. The sensor system of this variation may sense a shift in the weight distribution of the user at the handbase 120 and the footbase 130, at the seat 140 and the footbase 130, at the left handgrip 124 and the right handgrip 126, at the left footrest 132 and the right footrest 134, or at any other suitable combination within the engagement system 110. Preferably, the sensor system includes an upper load cell integrated into the handbase 120, a lower load cell integrated into the footbase 130, and a middle load cell integrated into the seat 140. Alternatively, the sensor system may include any other suitable device to sense the weight distribution of the user.


In a second variation, as shown in FIGS. 4-6, the sensor system senses forces imparted by the torso of the user. More particularly, the sensor system senses a shift (either in force or in movement) of the torso of the user. The sensor system of this variation may sense a shift of the torso of the user at the left side bolster 146, at the right side bolster 148, at the seat back 142, at the seat bottom 144. Preferably, the sensor system includes force transducers integrated into the left side bolster 146, into the right side bolster 148, into the seat back 142, and into the seat bottom 144. Alternatively, the sensor system may include any other suitable device to sense a shift (either in force or in movement) of the torso of the user.


In a third variation, as shown in FIGS. 7-9, the sensor system senses forces imparted by the appendages of the user. More particularly, the sensor system senses a shift (either in force or in movement) of the appendages of the user. The sensor system of this variation may sense a shift of the appendages of the user at the left handgrip 124 and the right handgrip 126 of the handbase 120, at the left footrest 132 and the right footrest 134 of the footbase 130, or at the handbase 120 and the footbase 130. Preferably, the sensor system includes load cells or force transducers, but may alternatively include any suitable device to sense a shift (either in force or in movement) of the appendages of the user. If the engagement system 110 includes an actuator, the actuator is preferably connected to the sensor system and arranged to move at least a portion of the engagement system 110 from a first position to a second position based on the forces sensed by the sensor system. Thus, the sensor system of this variation may be based on a shift of the forces (and may subsequently command the actuator to move at least a portion of the engagement system 110 between the first position to the second position), or the sensor system may be based on a shift of the position of the engagement system 110 by the user between the first position to the second position.


In a fourth variation, as shown in FIG. 10, the sensor system senses forces imparted by the appendages or the torso of the user. More particularly, the sensor system senses a shift (either in force or in movement) of the appendages or the torso of the user. The sensor system of this variation preferably senses a shift of the appendages (at the handbase, armrests, handles of the vehicle, dashboard, headrest, footrest of the vehicle, or floorboards of the vehicle) or senses a shift of the torso (at the side bolsters, seat back 142 or seat bottom 144). Preferably, the sensor system includes load cells or force transducers, but may alternatively include any suitable device to sense a shift (either in force or in movement) of the appendages or the torso of the user.


The interface of the preferred embodiment may also include a second sensor system. The second sensor system functions to sense an intuitive input from a passenger and to send a sensor output to the processor. The second sensor system is preferably similar to the sensor system of the preferred embodiments, but may alternatively be any suitable sensor system to sense an intuitive input from the passenger and to send a sensor output to the processor.


In a first variation, the second sensor system senses forces imparted by the torso of the passenger. More particularly, the sensor system senses a shift (either in force or in movement) of the torso of the passenger. The sensor system of this variation may sense a shift of the torso of the passenger at the left side bolster 146′, at the right side bolster 148′, at the seat back 142′, at the seat bottom 144′. Preferably, the sensor system includes force transducers integrated into the left side bolster 146′, into the right side bolster 148′, into the seat back 142′, into the seat bottom 144′, or into any combination thereof. Alternatively, the sensor system may include any other suitable device to sense a shift (either in force or in movement) of the torso of the passenger.


In a second variation, the second sensor system senses forces imparted by the appendages of the passenger. More particularly, the sensor system senses a shift (either in force or in movement) of the appendages of the passenger. The sensor system of this variation may sense a shift of the appendages of the passenger at the dashboard 152′, at the handles of the vehicle, at the armrests 150′, at the headrest 154′, at the footbase 130′ or floorboards of the vehicle, or any combination thereof. Preferably, the second sensor system includes load cells or force transducers, but may alternatively include any suitable device to sense a shift (either in force or in movement) of the appendages of the passenger.


The processor of the preferred embodiments functions to receive the sensor output from the sensor system, interpret a vehicle command based on the sensor output, and communicate a vehicle command to the vehicle. The processor preferably receives the sensor output via an electrical bus integrated within the vehicle, but may alternatively receive the sensor output via any suitable device or method, such as Bluetooth RF technology. The processor may interpret the vehicle command only when there is significant information to confirm that the user indeed wishes to invoke a particular vehicle command. As an example, the processor may only invoke a vehicle roll command when the user shifts their weight distribution at both the handbase 120 and the footbase 130, and may ignore sensor output when the user only shifts their weight at only one of the handbase 120 and footbase 130. The processor preferably interprets the vehicle command based on the sensor output and other factors, such as vehicle speed, vehicle yaw rate, or any other suitable vehicle parameter. The processor may also interpret the vehicle command based on user preference, whether inputted and stored on a memory device or derived from past experiences. The processor may include a connection to a computer or a network to download new software or to upload user preferences. The processor preferably includes a conventional processor, but may alternatively include any suitable device or method to interpret a vehicle command based on the sensor output.


2. The First Preferred Embodiment

In a first preferred embodiment of the invention, as shown in FIGS. 1-3, the interface 100 includes an engagement system 110 of the first variation, a sensor system of the first variation, and a processor that interprets a vehicle command based on the weight distribution of the user. The vehicle is preferably a “ride on” vehicle, such as a two-wheeled bicycle or motorcycle, a four-wheeled all-terrain vehicle (“ATV”), a jet ski, or a snowmobile. The vehicle command is preferably an attitude command (such as a vehicle pitch or a vehicle roll) or a handling command (such as a suspension command or a height command).


The processor may be arranged to interpret a vehicle pitch command based on a shift of the weight distribution of the user at the handbase 120, at the footbase 130, and at the seat 140. As an example, if the user shifts their weight distribution from the seat 140 or footbase 130 (FIG. 1A) to the handbase 120 (FIG. 1B), the processor may interpret the user command as a “pitch forward” command. Similarly, if the user shifts their weight distribution from the handbase 120 (FIG. 1A) to the footbase 130 and/or seat 140 (FIG. 1C), the processor may interpret the user command as a “pitch rearward” command. These commands are fairly intuitive for the user since the user will want to dive down upon the approach of a downward slope, and pull up upon the approach of an upward slope of the terrain.


The processor may be arranged to interpret a vehicle roll command based on a shift of the weight distribution of the user at the right handgrip 126 and the left handgrip 124 of the handbase 120, or at the left footrest 132 and the right footrest 134 of the footbase 130. As an example, if the user shifts their weight distribution from a center position (FIG. 2A) to the right side of the handbase 120 and/or the footbase 130 (FIG. 2B), the processor may interpret the user command as a “roll right” command. Similarly, if the user shifts their weight distribution from a center position (FIG. 2A) to the left side of the handbase 120 and/or the footbase 130 (as shown in FIG. 2C), the processor may interpret the user command as a “roll left” command. Like riding a bicycle or a motorcycle, these commands are fairly intuitive for the user since the user will want to lean into a right turn, and lean into a left turn. This interface 100 allows the user to disconnect the roll command from the steering command, and to invoke a roll command either separate from, or significantly before, a steering command.


The processor may be arranged to interpret a vehicle height command based on a shift of the weight distribution of the user at the handbase 120, at the footbase 130, and at the seat 140. As an example, if the user shifts their weight distribution from the seat 140 (FIG. 3A) to the handbase 120 and/or footbase 130 (FIG. 3B), the processor may interpret the user command as a “height upward” command and/or a “suspension softer” command. Similarly, if the user shifts their weight distribution from the handbase 120 and/or footbase 130 (FIG. 3B) to the seat 140 (FIG. 3A), the processor may interpret the user command as a “height downward” command and/or a “suspension tighter” command. Like riding a bicycle or a motorcycle, these commands are fairly intuitive for the user since the user will want to stand up and protect their spine during rough terrain (where it is beneficial to ride at a higher height and with a softer suspension), and will want to sit back and secure their grip of the controls during high speeds (where it is beneficial to ride at a lower height and with a tighter suspension).


The processor may, of course, be arranged to interpret any particular combination or permutation of the above vehicle commands.


3. The Second Preferred Embodiment

In a second preferred embodiment of the invention, as shown in FIGS. 4-6, the interface 100 includes an engagement system 110 of the second variation, a sensor system of the second variation, and a processor that interprets a vehicle command based on a shift of the torso of the user. The vehicle is preferably a “seated” vehicle, such as a three-wheeled cycle, a four-wheeled automobile or truck, a motorboat, or a small plane or helicopter. The vehicle command is preferably an attitude command (such as a vehicle pitch or a vehicle roll) or a handling command (such as a suspension command or a height command).


The processor may be arranged to interpret a vehicle pitch command based on a shift of the torso of the user at the seat back 142 or at the seat bottom 144. As an example, if the user shifts their torso from a normal position (FIG. 4A) to a forward position (FIG. 4B), the processor may interpret the user command as a “pitch forward” command. Similarly, if the user shifts their torso rearward, the processor may interpret the user command as a “pitch rearward” command. These commands are fairly intuitive for the user since the user will want to dive down upon the approach of a downward slope, and pull up upon the approach of an upward slope of the terrain.


The processor may be arranged to interpret a vehicle roll command based on a shift of the torso of the user at the seat bottom 144 or at the side bolsters 146 and 148. As an example, if the user shifts their torso from a center position (FIG. 5A) to a leaning left position (FIG. 5B), the processor may interpret the user command as a “roll left” command. Similarly, if the user shifts their weight distribution from a center position (FIG. 5A) to a leaning right position (FIG. 5C), the processor may interpret the user command as a “roll right” command. Like taking a hard turn in an automobile, these commands are fairly intuitive for the user since the user will want to lean into a right turn, and lean into a left turn. This interface 100 allows the user to disconnect the roll command from the steering command, and to invoke a roll command either separate from, or significantly before, a steering command.


The processor may be arranged to interpret a vehicle height command based on a shift of the torso of the user at the seat back 142 or at the seat bottom 144. As an example, if the user shifts their torso from a normal position (FIG. 4A) to a forward position (FIG. 4B), the processor may interpret the user command as a “height upward” command. Similarly, if the user shifts their torso rearward, the processor may interpret the user command as a “height downward” command. Like riding in an automobile with a high or tall belt line, these commands are fairly intuitive for the user since the user will want to lean forward and increase their view of the surroundings during rough terrain (where it is beneficial to ride at a higher height), and will want to sit back and secure their grip of the controls during high speeds (where it is beneficial to ride at a lower height).


The processor may be arranged to interpret a vehicle suspension command based on a shift of the torso of the user at the seat back 142 or at the seat bottom 144. As an example, if the user shifts their torso from a normal position (FIG. 6A) to a taut position with more weight and force on the thighs and upper back of the user (FIG. 6B), the processor may interpret the user command as a “suspension softer” command. Like riding in an automobile with stiff (or no) shock absorbers, this command is fairly intuitive for the user since the user will want to lift up and protect their spine during rough terrain (where it is beneficial to ride with a softer suspension).


The processor may, of course, be arranged to interpret any particular combination or permutation of the above vehicle commands.


4. The Third Preferred Embodiment

In a third preferred embodiment of the invention, as shown in FIGS. 7-9, the interface 100 includes an engagement system 110 of the third variation, a sensor system of the third variation, and a processor that interprets a vehicle command based on a shift of the appendages of the user. The vehicle is preferably a “ride on” vehicle, such as a two-wheeled bicycle or motorcycle, a four-wheeled all-terrain vehicle (“ATV”), a jet ski, or a snowmobile. The vehicle command is preferably a configuration command (such as a wheelbase command, a track command, a hull shape command, or a wing shape command).


The processor may be arranged to interpret a vehicle pitch command based on a shift in opposite directions of the appendages of the user at the handbase 120 and/or at the footbase 130. As an example, if the appendages of the user impart a force that tends to bias the handbase 120 and the footbase 130 in linearly opposite directions (FIG. 7) or rotationally opposite directions (FIG. 8), or that tends to bias the left handgrip 124 and the right handgrip 126 toward each other and/or the left footrest 132 and the right footrest 134 toward each other (FIG. 9), then the processor may interpret the user command as a vehicle “speed mode” command. Similarly, if the appendages of the user impart a force that tends to bias the handbase 120 and the footbase 130 toward each other, tends to bias the left handgrip 124 and the right handgrip 126 in opposition directions, or tends to bias the left footrest 132 and the right footrest 134 in opposition directions, then the processor may interpret the user command as a vehicle “maneuverability mode” command. Like riding a bicycle or a motorcycle, these vehicle commands are fairly intuitive for the user since the user will want to minimize their aerodynamic drag during high speed, and will want to maximize their stability during high maneuverability.


The vehicle, notified with this vehicle configuration command, may take appropriate actions, such as changing the wheelbase (the distance between the front wheels and the rear wheels) or the track (the distance between the left wheels and the right wheels) of a four wheeled automobile, changing the shape of the hull of a motorboat or the wing shape of an aircraft, or deploying stabilizer surfaces or fins on a land vehicle, a watercraft, or an aircraft.


The processor may, of course, be arranged to interpret any particular combination or permutation of the above vehicle commands.


5. The Fourth Preferred Embodiment

In a fourth preferred embodiment of the invention, as shown in FIGS. 10A, 10B, and 10C, the interface 100 includes an engagement system 110 of the fourth variation, a first sensor system of the fourth variation, a second sensor system of the first and second variations or any combination thereof, and a processor that interprets a vehicle command based on a shift of the appendages and/or the torso of the user. The processor in this embodiment is further adapted to receive the sensor output from the second sensor system, interpret a vehicle command based on the sensor output and to communicate the vehicle command to a vehicle. Additionally in the fourth preferred embodiment, the interface 100 may further include a second engagement system 110′ (FIG. 12) and the second sensor system may be coupled to the second engagement system 110′. While there is preferably a single processor in the interface 100, there may alternatively be any suitable number of processors (i.e. one per engagement system) to receive the sensor output from the corresponding sensor system, interpret a vehicle command based on the sensor output, and communicate a vehicle command to the vehicle. The vehicle is preferably a “seated” vehicle with room for a passenger, such as a three-wheeled cycle, or a four-wheeled automobile or truck. The vehicle command is preferably a “safety alert mode” command, which is generated by the intuitive and/or instinctive reactions of the user and/or passenger to a perceived impending sudden deceleration (such as a collision of the vehicle with another vehicle or a stationary object). Since an observant user or passenger may be able to perceive an impending sudden deceleration better and/or sooner than an autonomous avoidance system of the vehicle, the vehicle “safety alert mode” command may be able to improve overall safety of a vehicle equipped with the invention.


The processor of the fourth preferred embodiment may be arranged to interpret a vehicle “safety alert mode” command based on a shift of the user's appendages at the steering wheel, dashboard, headrest, footrests of the vehicle, and/or floorboards of the vehicle or a shift of the torso of the user at the left side bolster, right side bolster, seat back 142 or seat bottom 144. As an example, if the user forcefully shifts their appendages forward into the steering wheel and/or dashboard, shifts their torso rearward into the seat back 142 (FIG. 10B), shifts their head forcefully rearward into the headrest, shifts their torso upward and out from the seat bottom 144 (FIG. 10C), shifts their appendages forcefully downward into the footrest or floorboards of the vehicle, or any combination thereof, the processor may interpret the user command as a vehicle “safety alert mode” command. This command is fairly intuitive for the user since the user will want to brace themselves in the event of a perceived potential collision of their vehicle. The processor may interpret the user command as a vehicle “safety alert mode” command based on the relative change in output of two or more sensors; for example, a decrease in force applied to the seat bottom sensed simultaneously with an increase in force applied rearwards into the seat back and an increase in force applied downwards into the floorboard of the vehicle. The processor may interpret the user command as a vehicle “safety alert mode” command based on the relative change in output of any suitable combination of sensors.


In the fourth preferred embodiment, the processor further functions to interpret a vehicle “safety alert mode” command based on a shift of the passenger's appendages at the dashboard 152′, handles of the vehicle, headrest 154′, footbase 130′ (FIG. 12), or floorboards of the vehicle, and/or a shift of the passenger's torso at the left side bolster 146′, the right side bolster 148′, the seat back 142′ or the seat bottom 144′. As an example, if the passenger forcefully shifts their appendages forward into the dashboard 152′, quickly grabs or pulls on the handles of the vehicle, shifts their torso rearward into the seat back 142′, shifts their head forcefully rearward into the headrest 154′, shifts their torso upward and out from the seat bottom 144′, and/or slams their foot into the footbase 130′ or floorboards of the vehicle, or any combination thereof, the processor may interpret the passenger command as a vehicle “safety alert mode” command. This command is fairly intuitive for the passenger since the passenger will want to brace themselves in the event of a perceived potential collision of the vehicle. The processor may interpret the passenger command as a vehicle “safety alert mode” command based on the relative change in output of two or more sensors; for example, a decrease in force applied to the seat bottom sensed simultaneously with an increase in force applied to the seat back and the floorboard of the vehicle. The processor may interpret the passenger command as a vehicle “safety alert mode” command based on the relative change in output of any suitable combination of sensors.


The vehicle, when armed with this vehicle “safety alert mode” command, may take one or more of the following defensive actions: tightening the suspension, lowering the vehicle, shutting off the engine, placing the transmission in neutral gear, tightening seatbelts, inflating or preparing for a quicker inflation of an external and/or internal airbag, preparing for a quicker braking response to a brake pedal push, amplifying power steering assistance, or any other suitable action. The vehicle command may be communicated to the vehicle of the user, or may be broadcasted to multiple vehicles. Since the user and passenger may be able to sense a potential collision better and/or sooner than an avoidance system of the vehicle, the vehicle “safety alert mode” command may be able to save lives.


The processor may, of course, be arranged to interpret any particular combination or permutation of the above vehicle commands. The processor may further consider vehicle information such as vehicle yaw rate or roll rate when interpreting a user command; for example, the processor may not interpret the user command as a vehicle “safety alert mode” command if it determines the vehicle yaw rate is too high for the vehicle to safely perform one or more of the above vehicle commands.


6. The Fifth Preferred Embodiment

In a fifth preferred embodiment of the invention, as shown in FIG. 12, the interface 100 includes an engagement system 110 of the fourth variation, a first sensor system of the fourth variation, a second sensor system of the first and second variations or any combination thereof, and a processor that interprets a vehicle command based on a shift of the appendages and/or the torso of the user. The processor in this embodiment is further adapted to receive the sensor output from the second sensor system, interpret a vehicle command based on the sensor output and to communicate the vehicle command to a vehicle. Additionally in the fifth preferred embodiment, the interface 100 may further include a second engagement system 110′ (FIG. 12) and the second sensor system may be coupled to the second engagement system 110′. While there is preferably a single processor in the interface 100, there may alternatively be any suitable number of processors (i.e. one per engagement system) to receive the sensor output from the corresponding sensor system, interpret a vehicle command based on the sensor output, and communicate a vehicle command to the vehicle. The vehicle is preferably a “seated” vehicle with room for a passenger, such as a three-wheeled cycle, or a four-wheeled automobile or truck. The vehicle command is preferably a “safety alert mode” command, which is generated by the intuitive and/or instinctive reactions of the user and/or passenger to a perceived impending sudden movement of the vehicle in the vertical direction (such as a pothole or object in the path of the vehicle). Since an observant user or passenger may be able to perceive an impending obstacle in the path of the vehicle better and/or sooner than an autonomous avoidance system of the vehicle, the vehicle “safety alert mode” command may be able to improve overall safety of a vehicle equipped with the invention.


The processor in the fifth preferred embodiment may be arranged to interpret a vehicle “safety alert mode” command based on a shift of the user's appendages at the steering wheel, armrests, handles of the vehicle, headrest, footrest of the vehicle, and/or floorboards of the vehicle, or a shift of the torso of the user at the left side bolster, right side bolster, seat back 142 or seat bottom 144. As an example, if the user shifts their appendages forcefully downwards on the steering wheel, armrests, or footrest of the vehicle, shifts their torso upwards from the seat bottom or any combination thereof in an effort to raise their body, the processor may interpret the user command as a vehicle “safety alert mode” command. This command is fairly intuitive for the user since the user will want to raise their body off the seat bottom in the event of the vehicle approaching a pothole, speed bump, or other obstacle in the path of the vehicle, in order to reduce the jarring force transferred through the seat bottom to their body as the vehicle encounters the obstacle. The processor may interpret the user command as a vehicle “safety alert mode” command based on the relative change in output of two or more sensors; for example, a decrease in force applied downwards into the seat bottom sensed simultaneously with an increase in force applied downwards to the armrests. The processor may interpret the user command as a vehicle “safety alert mode” command based on the relative change in output of any suitable combination of sensors.


The processor further functions to interpret a vehicle “safety alert mode” command based on a shift of the passenger's appendages at the dashboard 152′, armrests 150′, handles of the vehicle, headrest 154′, footbase 130′ or floorboards of the vehicle and/or a shift of the passenger's torso at the left side bolster 146′, the right side bolster 148′, the seat back 142′ or the seat bottom 144′ (FIG. 12). As an example, if the passenger shifts their appendages forcefully downwards on the armrests 150′ or footbase 130′ of the vehicle, shifts their torso upwards from the seat bottom 144′ or any combination thereof in an effort to raise their body, the processor may interpret the passenger command as a vehicle “safety alert mode” command. This command is fairly intuitive for the passenger since the passenger will want to raise their body off the seat bottom in the event of the vehicle approaching a pothole, speed bump, or other obstacle in the path of the vehicle, in order to reduce the jarring force transferred through the seat bottom to their bottom as the vehicle encounters the obstacle. The processor may interpret the passenger command as a vehicle “safety alert mode” command based on the relative change in output of two or more sensors; for example, a decrease in force applied downwards into the seat bottom sensed simultaneously with an increase in force applied downwards to the armrests. The processor may interpret the passenger command as a vehicle “safety alert mode” command based on the relative change in output of any suitable combination of sensors.


The vehicle, when armed with this vehicle “safety alert mode” command, may take one or more of the following defensive actions: softening the suspension (attainable with a suspension system such as that taught by Coombs et al., U.S. Pat. No. 6,811,167, which is incorporated in its entirety by this reference) or gently applying brakes to decelerate the vehicle as the vehicle approaches the obstacle in its path. The vehicle command may be communicated to the vehicle of the user, or may be broadcasted to multiple vehicles. Since the user and passenger may be able to sense an impending sudden movement of the vehicle in the vertical direction better than an avoidance system of the vehicle, the vehicle “safety alert mode” command may be able to save lives.


The processor may, of course, be arranged to interpret any particular combination or permutation of the above vehicle commands. The processor may further consider vehicle information such as vehicle yaw rate or roll rate when interpreting a user command; for example, the processor may not interpret the user command as a vehicle “safety alert mode” command if it determines the vehicle yaw rate is too high for the vehicle to safely perform one of the above vehicle commands.


Although omitted for conciseness, the preferred embodiments include every combination and permutation of the various engagement systems, the sensor systems, the processors, the vehicles, and the vehicle commands. The preferred embodiments also include every combination of multiple engagement systems, the sensor systems, the processors, the vehicles, and the vehicle commands. As an example, the processor may be arranged to interpret a “bunny hop” command, which may be a combination of a vehicle “pitch forward” command, a vehicle “pitch rearward” command, and a vehicle “height upward” command.


As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.

Claims
  • 1. An interface for communicating a vehicle “safety alert mode” command from a user to a vehicle that is adapted to initiate a defensive action of one or more of the following when armed with the vehicle “safety alert mode” command: tightening the suspension, loosening the suspension, lowering the vehicle, shutting off the engine, placing the transmission in neutral gear, tightening seatbelts, preparing for inflation of an airbag, preparing for a quick braking response to a brake pedal push, gently applying brakes to decelerate the vehicle, and amplifying power steering; comprising: an engagement system adapted to engage the torso and an appendage of a user;a sensor system coupled to the engagement system and adapted to sense forces imparted by the user; anda processor coupled to the sensor system and adapted to interpret the vehicle “safety alert mode” command based on a forceful shift of the user, to confirm that the user wishes to invoke the vehicle “safety alert mode” command, and to communicate the vehicle “safety alert mode” command to the vehicle.
  • 2. The interface of claim 1, wherein the engagement system includes a handbase, and wherein the sensor system is adapted to sense forces imparted by the appendage of the user on the handbase.
  • 3. The interface of claim 1, wherein the engagement system includes a headrest, and wherein the sensor system is adapted to sense forces imparted by the appendage of the user on the headrest.
  • 4. The interface of claim 1, wherein the engagement system includes an armrest, and wherein the sensor system is adapted to sense forces imparted by the appendage of the user on the armrest.
  • 5. The interface of claim 1, wherein the engagement system includes a footrest, and wherein the sensor system is adapted to sense forces imparted by the appendage of the user on the footrest.
  • 6. The interface of claim 1, wherein the engagement system includes a seat back, and wherein the sensor system is adapted to sense forces imparted by the torso of the user on the seat back.
  • 7. The interface of claim 6, wherein the engagement system includes a side bolster, and wherein the sensor system is adapted to sense forces imparted by the torso of the user on the side bolster.
  • 8. The interface of claim 1, wherein the engagement system includes a seat bottom, and wherein the sensor system is adapted to sense forces imparted by the torso of the user on the seat bottom.
  • 9. The interface of claim 1, wherein the interface further comprises: a second engagement system adapted to engage the torso and an appendage of a passenger;a second sensor system coupled to the second engagement system and adapted to sense forces imparted by the passenger; anda second processor coupled to the second sensor system and adapted to interpret the vehicle “safety alert mode” command based on a forceful shift of the passenger, to confirm that the passenger wishes to invoke the vehicle “safety alert mode” command, and to communicate the vehicle “safety alert mode” command to the vehicle.
  • 10. The interface of claim 9, wherein the second engagement system includes a dashboard of the vehicle, and wherein the second sensor system is adapted to sense forces imparted by the appendage of the user on the dashboard.
  • 11. The interface of claim 9, wherein the second engagement system includes a handle of the vehicle, and wherein the second sensor system is adapted to sense forces imparted by the appendage of the user on the handle of the vehicle.
  • 12. The interface of claim 9, wherein the second engagement system includes an armrest, and wherein the second sensor system is adapted to sense forces imparted by the appendage of the user on the armrest.
  • 13. The interface of claim 9, wherein the second engagement system includes a seat back, and wherein the second sensor system is adapted to sense forces imparted by the torso of the user on the seat back.
  • 14. The interface of claim 13, wherein the second engagement system includes a side bolster, and wherein the second sensor system is adapted to sense forces imparted by the torso of the user on the side bolster.
  • 15. The interface of claim 9, wherein the second engagement system includes a seat bottom, and wherein the second sensor system is adapted to sense forces imparted by the torso of the user on the seat bottom.
  • 16. The interface of claim 9, wherein the second engagement system includes a footbase, and wherein the second sensor system is adapted to sense forces imparted by the appendage of the user on the footbase.
  • 17. The interface of claim 1, wherein the processor is adapted to communicate the vehicle “safety alert mode” command to more than one vehicle.
  • 18. The interface of claim 9, wherein the first processor and the second processor are the same processor.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of prior application Ser. No. 11/239,963 entitled “Vehicle Interface to Communicate a Safety Alert Mode Command”, which was filed on 30 Sep. 2005. This application also claims the benefit of U.S. Provisional Application No. 60/971,744 entitled “Vehicle Interface to Communicate a Safety Alert Mode Command”, which was filed on 12 Sep. 2007. Both of these applications are incorporated in their entirety by this reference. This application is related to application Ser. No. 11/239,805 entitled “Vehicle Interface Based On The Weight Distribution Of A User” (docketed JOSH-Po1 and related to the description of the first preferred embodiment), application Ser. No. 11/239,804 entitled “Vehicle Interface Based On A Shift Of The Torso Of A User” (docketed JOSH-Po2 and related to the description of the second preferred embodiment), application Ser. No. 11/239,803 entitled “Vehicle Interface Based On A Shift Of The Appendages Of A User” (docketed JOSH-Po3 and related to the description of the third preferred embodiment), which were all filed on 30 Sep. 2005 and are incorporated in their entirety by this reference.

Provisional Applications (1)
Number Date Country
60971744 Sep 2007 US
Continuation in Parts (1)
Number Date Country
Parent 11239963 Sep 2005 US
Child 12209303 US