The present invention relates to determining the direction of travel or movement of a vehicle. More particularly, embodiments of the invention relate to determining vehicle direction in low-speed situations.
Increasingly sophisticated features are being proposed for modern vehicles, such as automatic parallel parking, and forward/backward emergency braking. In automatic parallel parking systems, forward/backward emergency braking systems, and other vehicle systems, there is a need to know the direction in which a vehicle is traveling. Although vehicle direction can be determined in a number of ways, it is possible to determine the direction of a vehicle using information output by wheel speed sensors. Some intelligent wheel spend sensors must operate for a certain amount of time before there is sufficient data to calculate the direction of movement. During this minimum time, the vehicle must move in a single direction. If the vehicle moves less than is required to obtain needed data, the wheel speed sensor is not able to determine the direction of vehicle movement. If the vehicle repeatedly moves less the required distance (such as might occur during close-quarter maneuvering when the vehicle moves forward and then backward to execute a tight turn), the accumulated distance traveled by the vehicle can reach a significant level, yet because each distinct movement was relatively short, none of the movement was sufficient to allow the direction of movement to be determined. As a consequence, an accumulated error occurs and vehicle systems relying on information from the sensors to determine vehicle direction operate improperly (because they are receiving inaccurate information). These errors can cause improper movement of the vehicle, such as during automatic parallel parking or forward/backward emergency braking maneuvers, which can cause a vehicle to collide with other vehicles or obstacles.
In one embodiment, the invention provides method of determining a driving direction of a vehicle traveling at a low speed. The method includes determining whether the vehicle is in one of three states: (1) an uphill state in which the vehicle is located on an upward sloping surface, (2) a downhill state in which the vehicle is located on a downward sloping surface, and (3) a flat surface state in which the vehicle is located on a flat surface. The method further includes obtaining information from a plurality of vehicle sensors and determining a direction of movement of the vehicle based upon the determined state of the vehicle and information from the plurality of vehicle sensors.
Another embodiment of the invention provides a system for determining a driving direction of a vehicle traveling at a low speed. The system includes a controller, and a plurality of sensors connected to the controller. Each of the sensors configured to transmit information to the controller. A network connects the sensors to the controller. The controller is programmed to determine whether the vehicle is in one of three states: (1) an uphill state in which the vehicle is located on an upward sloping surface, (2) a downhill state in which the vehicle is located on a downward sloping surface, and (3) a flat surface state in which the vehicle is located on a flat surface, and determine a direction of movement of the vehicle based upon the determined state of the vehicle and information from the plurality of sensors.
Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.
Before any embodiments of the invention are explained in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The invention is capable of other embodiments and of being practiced or of being carried out in various ways.
It should also be noted that a plurality of hardware and software based devices, as well as a plurality of different structural components, may be utilized to implement the invention. As described in subsequent paragraphs, the specific configurations illustrated in the drawings are intended to exemplify embodiments of the invention and other alternative configurations are possible.
As shown in
The EPU 42 receives the information from the input/output interface 40 and processes the information by executing one or more applications or modules. The applications or modules are stored in memory, such as ROM 45. The EPU 42 stores information (e.g., information received from the bus 22 or information generated by applications or modules executed by the EPU 42) to the RAM 44.
In the example shown in
The operations of LSDDD module 50 may be modeled with or represented by an if-then statement. The method of
Breaking down the method of
Step (3a) includes determining whether the reading or output from the longitudinal acceleration sensor 26 when the vehicle 10 first starts to move (axlnvRadln) minus the reading from the longitudinal acceleration sensor 26 when the vehicle 10 is substantially stationary is greater than zero.
Evaluating whether the vehicle is moving may be accomplished by analyzing readings from the wheel speed sensors 24 over a period of cycles or polls. For example, if three successive readings indicate that the wheel speed is increasing then it can be assumed that the vehicle is moving. Step (3a) determines whether the vehicle's drive force (or its longitudinal acceleration once the vehicle starts to move) is great enough to overcome the weight or force of gravity pulling the vehicle down the upward sloping surface. In
Finally, in step (4a) the output from the gear shift sensor 36 (PRNDL) is evaluated. It is assumed that when the vehicle's transmission is in “drive” or “D,” the vehicle is moving forward or at least the intended movement is forward. Thus, “PRNDL=D” is yet another factor indicating that forward movement is occurring. If the LSDDD module 50 determines that all of the steps (1a) through (4a) are satisfied, the LSDDD module 50 outputs a direction indicator indicating that the vehicle 10 is moving in a forward direction.
As shown in
Breaking down the logic of
As shown in
Breaking down the method of
Step (4a) includes determining whether the vehicle's longitudinal acceleration at or after the vehicle's zero-crossing point (axln(dvRadln/dt>=0)) minus the vehicle's longitudinal acceleration sensor 26 when the vehicle 10 is substantially stationary (axlnBls) is greater than zero. As shown in
Steps (5a) and (6a) evaluate the vehicle's brake light switch 34 and the vehicle's gear shift sensor 36. It is assumed that when the operator's foot is off the brake and the vehicle's transmission is in “drive,” the vehicle is moving forward or at least the intended movement is forward. Thus, “!BLS” and “PRNDL=D” are two additional factors indicating that forward movement is occurring. If the LSDDD module 50 determines that all of the steps (1a) through (6a) are satisfied, the LSDDD module 50 outputs a direction indicator (e.g., to the automatic parallel parking control module 52) indicating that the vehicle 10 is moving in a forward direction.
As shown in
The operations of LSDDD module 50 in this situation may be modeled with or represented by an if-then statement. The method of
Breaking down the method of
As shown in
Depending on the decline of the downward sloping surface, the vehicle 10 may initially free-roll forward when the vehicle is placed in “reverse” before it moves backward as a result of the driver pressing the accelerator pedal. As described below in more detail, by monitoring (1) the difference of the sensor readings of the longitudinal acceleration sensor between the time the vehicle is at a standstill and the time the vehicle is free-rolling forward, (2) the value of the sensor readings from the wheel speed sensors, (3) the zero-crossing point of sensor readings from the wheel speeds, (4) the sensor readings from the steering angle sensor, (5) the sensor readings from the lateral acceleration sensor, and (6) the sensor readings form the yaw rate sensor, the LSDDD module 50 determines the direction of vehicle movement.
In the flat surface case, the vehicle initially free-rolls forward when the vehicle's transmission is shifted from “drive” to “reverse” due to the vehicle's forward inertia. Similarly, the vehicle initially free-rolls backward when the vehicle's transmission is shifted from “reverse” to “drive” due to the vehicle's backward inertia. As described below in more detail, by monitoring (1) the difference of the sensor readings of the longitudinal acceleration sensor between the time the vehicle is at a standstill and the time the vehicle is free-rolling forward or backward, (2) the value of the sensor readings from the wheel speed sensors, (3) the zero-crossing point of sensor readings from the wheel speeds, (4) the sensor readings from the steering angle sensor, (5) the sensor readings from the lateral acceleration sensor, and (6) the sensor readings form the yaw rate sensor, the LSDDD module 50 determines the direction the vehicle is moving on the generally flat surface.
Step (1a) includes determining whether a sensor reading from the vehicle's longitudinal acceleration when substantially stationary is between the predetermined downhill threshold and the predetermined uphill threshold. If so, the flat surface case is assumed. Step (2a) includes determining whether the derivative of current sensor readings from the vehicle's wheel speed sensor(s) 24 is greater than zero. Step (3a) includes determining whether the vehicle's longitudinal acceleration when it first starts to move minus the vehicle's longitudinal acceleration when it is substantially stationary is greater than zero. Step (4a) determines whether the gear shift sensor 36 indicates that the vehicle's transmission is in “drive.” If the LSDDD module 50 determines that all of the steps (1a) through (4a) are satisfied, the LSDDD module 50 outputs a direction indicator (e.g., to the automatic parallel parking control module 52) indicating that the vehicle 10 is moving in a forward direction.
As with other cases, the logic can alternatively use sensor readings from the vehicle's steering angle sensor 28, yaw rate sensor 32, and lateral acceleration sensor 30 to determine whether the vehicle 10 is moving in a forward direction (see steps (1b) and (2b) above). If the LSDDD module 50 determines that both steps (1b) and (2b) are satisfied, the LSDDD module 50 outputs a direction indicator indicating that the vehicle 10 is moving in a forward direction.
Step (1a) includes determining whether the vehicle's longitudinal acceleration when it is substantially stationary is between the predetermined uphill threshold and the predetermined downhill threshold. Step (2a) includes determining whether the derivative the output from the wheel speed sensors 24 during a previous time period is less than zero. Thus, step (2a) determines whether the vehicle was decelerating during a previous time period. If so, this would indicate that the vehicle was previously decelerating while it was free-rolling forward before the vehicle stopped and started moving backward. Step (3a) determines whether the derivative of current readings from the vehicle's wheel speed sensors 24 is greater than or equal to zero. Step (4a) includes determining whether the vehicle's longitudinal acceleration at or after a zero-crossing point minus the vehicle's longitudinal acceleration when it is substantially stationary is less than zero. As described above, the vehicle's zero-crossing point occurs when the vehicle stops after free-rolling forward and before moving backward. Therefore, the zero-crossing point occurs when the derivative of readings from the vehicle's wheel speed sensors 24 is zero, indicating that the vehicle 10 is stationary. After the zero-crossing point, the vehicle starts moving backward. Therefore, its longitudinal acceleration should be negative at this point.
Finally, steps (5a) and (6a) evaluate the brake light switch sensor 34 and the gear shift sensor 36. If the operator is not pressing the brake pedal and the vehicle's transmission is in “reverse,” it is assumed that the vehicle is moving backward. Thus, “!BLS” and “PRNDL=R” are two other factors indicating that backward movement is occurring. If the LSDDD module 50 determines that all of the steps (1a) through (6a) are satisfied, the LSDDD module 50 outputs a direction indicator indicating that the vehicle 10 is moving in a backward direction.
As shown in
In some embodiments, the automatic parallel parking control module 52 is executed by the same controller 14 that executes the LSDDD module 50. In other embodiments, the automatic parallel parking control module 52 is executed by a different controller than the controller 14 executing the LSDDD module 50 and the controller 14 can output the direction indicator generated by the LSDDD module 50 to the controller executing the automatic parallel parking control module 52 (e.g., over the bus 22). Of course, the LSDDD module 50 can be used to determine the direction of vehicle movement in vehicle applications outside automatic parallel parking. For example, others systems or controllers (such as forward/backward emergency braking systems) that need to know the direction of vehicle movement in low speed situations can obtain and use the direction indicator generated by the LSDDD module 50.
Thus, the invention provides, among other things, a controller and methods for determining a direction in which a vehicle is moving when the vehicle is traveling at low speeds.
The present patent application claims priority to U.S. Provisional Application No. 61/187,568, filed on Jun. 16, 2009, the content of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
6141605 | Joyce | Oct 2000 | A |
6272403 | Sugitani et al. | Aug 2001 | B2 |
6428120 | Holl | Aug 2002 | B1 |
6513886 | Weber et al. | Feb 2003 | B1 |
6539298 | Inagaki et al. | Mar 2003 | B2 |
6564140 | Ichikawa et al. | May 2003 | B2 |
6577948 | Skellenger et al. | Jun 2003 | B1 |
6616572 | Suzuki | Sep 2003 | B2 |
6701224 | Klusemann | Mar 2004 | B1 |
6714851 | Hrovat et al. | Mar 2004 | B2 |
7070247 | Offerle | Jul 2006 | B2 |
7096100 | Arata | Aug 2006 | B2 |
7229139 | Lu et al. | Jun 2007 | B2 |
7363116 | Flechtner et al. | Apr 2008 | B2 |
7424357 | Ozaki et al. | Sep 2008 | B2 |
7451029 | McLaren et al. | Nov 2008 | B2 |
7835840 | Chiu et al. | Nov 2010 | B2 |
8065066 | Mori et al. | Nov 2011 | B2 |
20030130778 | Hrovat et al. | Jul 2003 | A1 |
20040024513 | Aizawa et al. | Feb 2004 | A1 |
20040215385 | Aizawa et al. | Oct 2004 | A1 |
20050209763 | Offerle et al. | Sep 2005 | A1 |
20060149451 | Maas | Jul 2006 | A1 |
20070027598 | Mori et al. | Feb 2007 | A1 |
20070131473 | Jonasson et al. | Jun 2007 | A1 |
20070299581 | Torralbo et al. | Dec 2007 | A1 |
20080086269 | Joe et al. | Apr 2008 | A1 |
20090187324 | Lu et al. | Jul 2009 | A1 |
20100036564 | Blaise et al. | Feb 2010 | A1 |
20100318255 | Li et al. | Dec 2010 | A1 |
20110276225 | Nefcy et al. | Nov 2011 | A1 |
Number | Date | Country |
---|---|---|
102006054516 | Jun 2007 | DE |
0849142 | Jun 1998 | EP |
1108605 | Jun 2001 | EP |
1327553 | Jul 2003 | EP |
1764580 | Mar 2007 | EP |
2920732 | Mar 2009 | FR |
63038043 | Feb 1988 | JP |
0769102 | Mar 1995 | JP |
09287962 | Nov 1997 | JP |
2000351362 | Dec 2000 | JP |
2002083914 | Mar 2002 | JP |
2003089350 | Mar 2003 | JP |
2004203061 | Jul 2004 | JP |
2006296135 | Oct 2006 | JP |
2008174102 | Jul 2008 | JP |
2008224352 | Sep 2008 | JP |
2009126307 | Jun 2009 | JP |
2008003530 | Jan 2008 | WO |
2008113533 | Sep 2008 | WO |
Entry |
---|
Pasquier, M.; Quek, C.; Tung, W.L.; Chen, D.; Yep, T.M.; , “Fuzzylot II: a novel soft computing approach to the realisation of autonomous driving manoeuvres for intelligent vehicles,” Control, Automation, Robotics and Vision, 2002. ICARCV 2002. 7th International Conference on , vol. 2, no., pp. 746-751 vol. 2, Dec. 2-5, 2002 doi: 10.1109/ICARCV.2002. |
“Fuzzylot II . . . ” citation above continued: available on IEEE URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1238515&isnumber=27724. |
EP10165970 European Search Report dated Sep. 3, 2010 (2 pages). |
Second Examination Report from the European Patent Office for Application No. 10165970.4 dated Nov. 15, 2011 (4 pages). |
Meister, Tilo, et al., “Enabling Technologies for Lateral Dynamic Assistant Systems”, SAE Technical Paper Series, document No. 2006-1-1172, 2006 SAE World Congress, Detroit, Michigan, Apr. 3-6, 2006. |
Japanese Office Action for Application No. 2010-132849 dated Dec. 17, 2013 (English Translation, 5 pages). |
Number | Date | Country | |
---|---|---|---|
20100318255 A1 | Dec 2010 | US |
Number | Date | Country | |
---|---|---|---|
61187568 | Jun 2009 | US |