Adaptive cruise control systems (“ACC”) for automotive vehicles, which control gap distances between a vehicle and another vehicle ahead of it, are known. These ACC systems typically use a forward-looking radar device, installed behind the grill of the vehicle, to detect the speed and distance of the vehicle ahead of it. Based on these measurements, the ACC systems can automatically adjust the speed of the vehicle to maintain a predetermined distance from the lead vehicle. As one example, if the lead vehicle slows down, or if another object is detected in the vehicle path, the ACC system may send a signal to the engine or braking system to decelerate the vehicle. Then, when the path is clear, the system may accelerate the vehicle back to the set speed and set gap distance.
Further, a typical ACC system may include control switches mounted to a steering wheel to permit a driver to manually adjust the gap distance setting. In this respect, a driver can in real-time manually adjust the settings to provide various gap distances or following distances along the traveled route, such that the entire drive is within the comfort level of the driver. For example, a driver may commute to work along a portion of an interstate freeway having light, high speed traffic and adjust the setting of the ACC system to provide a gap distance of approximately 65 meters based on a speed of 100 kilometers per hour (KPH). In slower, more congested sections of the freeway where, for example, multiple freeways merge together, the driver may readjust the ACC system to provide a gap distance of 30 meters. Accordingly, the driver can manually select multiple predetermined gap distances for respective portions of a route.
A driver performance mapping system for a vehicle system is disclosed. On embodiment of the driver performance mapping system may include a GPS receiver generating GPS data indicative of a current location of the vehicle. In addition, the system may also have a radar device generating current gap data indicative of a current gap distance between the vehicle and a lead vehicle. Further, the system may include an electronic controller configured to generate learned gap data based on the current gap data and stored gap data, and then assign the learned gap data with the GPS data.
A method of learning and modifying a driver performance set point for a vehicle system is disclosed. One embodiment of the method can include the step of receiving GPS data from a GPS satellite indicative of a current location of a vehicle. The method may also include receiving current gap data from a radar device indicative of a current gap distance from the vehicle to a lead vehicle. In addition, the method may also include generating learned gap data based on the current gap data and stored gap data and then assign the learned gap data with the GPS data.
One embodiment of a system and method for modifying and assigning learned gap data and learned speed data to vehicle locations along a currently traveled route is disclosed. The system, in one form, may build and utilize a localized and adaptive map of the route. In particular, the system may be located on the automotive vehicle itself, periodically receive location data for the vehicle from GPS satellites, and selectively store some of the location data based upon certain criteria. The system may store the learned gap data and learned speed data of the vehicle as it travels along the route. In this way, map data and vehicle performance data associated with a particular route traveled by the vehicle can be stored locally with a relatively small amount of electronic storage space. The locally stored map and performance data may be specific to the vehicle that records the data or may be specific to selected drivers who drive the vehicle. The locally-stored map data may be used on subsequent trips by the same vehicle to preview the intended travel path of the vehicle. The locally-stored performance data may be used on subsequent trips in conjunction with an ACC system to adjust the performance of the vehicle as a function of the historical driving habits associated with the vehicle at associated locations along the route. The disclosed method may not be dependent upon pre-defined maps and does not require a communication link to data outside of the vehicle (though it does not exclude the possible use or interaction with such pre-defined maps and/or communication links). Instead, the disclosed system may acquire location data and vehicle performance data specific to the actual drive paths of the vehicle and use such customized data on subsequent trips on the same drive path.
Location node 310a represents the first sampled location data of the vehicle on a new route. Accordingly, the system may store the location data associated with location node 310 as the “head” or starting point of the route. The system may then periodically acquire or sample longitude and latitude data associated with the then-location of the vehicle received from GPS satellites by GPS receiver 130. The system may make a determination to store the currently-sampled location data as a location node (e.g., location nodes 310b-310e) when the sampled location data falls outside of an “envelope” defined by the combination of a parallel threshold and a perpendicular threshold.
The parallel threshold 330 can be a distance between two imaginary parallel lines on opposite sides of the vehicle and between which the vehicle is centered. The direction of the parallel lines at any given moment may be defined by the heading of the vehicle at that moment. For example, the parallel threshold 330 shown in
The method described above in connection with
The two-dimensional map of routes traveled by the vehicle described in connection with
The map generated by the method in
At step 610, a vehicle location matching envelope may be determined, which, in this case, includes a latitude threshold and a longitude threshold, which may be pre-defined or variable. The dimensions of the location matching envelope can be independent of the dimensions of the earlier-described location envelope used for learning a route (described in connection with
At step 640, the system 10 can store the vehicle location as a new location node. The system may also store a new gap set point and a new speed set point associated with the new node. However, the system may instead utilize set points for speed and gap distance associated with the immediately preceding node.
At step 650, the system 10 may update gap data associated with the nodes along the previously-traveled route. In particular, this step may be initiated by determining that a predetermined threshold has been satisfied. For example, the controller may receive GPS data from the GPS receiver, indicative that the vehicle is substantially close to a node, such as being located less than 1% of the distance from node 310a to node 310b. The controller 100 may then further receive current gap data from the radar device and stored gap data from the storage device. The controller 100 may calculate the learned gap data, based on the current gap data and stored gap data so as to provide the updated gap set point. The controller may then assign the learned gap data to the corresponding GPS data. As one example, the controller 100 may calculate the learned gap data is the sum of 10% of a current gap distance of 70 meters and 90% of the stored or previously-learned gap distance of 50 meters at node 310a, so as to provide an updated gap set point of 52 meters at node 310a. The learned gap data may be stored on the storage device and utilized in conjunction with the ACC system as described below for steps 670 and thereafter, in the next trip along this route.
At step 660, the controller 100 may update speed data associated with the nodes along the previously-traveled route. In particular, the controller may receive the current speed data from the wheel speed sensor and the stored speed data from the storage device. The controller may then calculate the learned speed data, based on the current speed and the stored speed so as to provide the learned speed data. The controller may then assign the learned speed data to the corresponding GPS data. For example, the controller 100 may calculate the learned speed data as the sum of 10% of the current speed of 95 KPH and 90% of the stored or previously-learned speed of 110 KPH at the node 310a, so as to provide an updated speed set point of 108.5 KPH at node 310a. The learned speed data may be stored on the storage device and utilized in conjunction with the ACC system as described below for steps 670 and thereafter, in the next trip along this route.
At step 670, the controller 100 may in real-time interpolate the speed set point between consecutive nodes along the historical driving route. In particular, the controller may calculate the speed set point based on the previously-learned speeds at the nodes 310a, 310b, and further based on the distance of the vehicle with respect to those nodes. Continuing the previous example, the vehicle may be located less than 1% of the distance from node 310a to node 310b. The previously-learned speeds at nodes 310a, 310b may be 110 KPH and 80 KPH, respectively. Accordingly, the controller may calculate the speed set point as the sum of 1% of 110 KPH and 99% of 80 KPH, so as to provide an interpolated speed set point of 109.7 KPH.
Similarly, at step 680, the controller 100 may interpolate the gap set point between consecutive nodes along the historical driving route. To continue the example above, the vehicle may be located less than 1% of the distance from node 310a to node 310b. The previously-learned gaps at nodes 310a, 310b may be 50 meters and 70 meters, respectively. Accordingly, the controller may interpolate the current gap set point by adding 99% of 50 meters to 1% of 70 meters, such that the current gap set point for the ACC system may be 50.2 meters. This interpolation may permit the ACC system to gradually operate the vehicle without sudden acceleration or braking.
At step 690, the controller 100 may determine whether the ACC system 10 has been actuated by the driver to provide automated speed and gap control. If not, the method returns to step 620. If so, however, the method continues to step 700.
At step 700, the controller 100 may determine whether the ACC system has been disposed in a standby mode. If not, the method immediately continues to step 720. If, however, the ACC system is in the standby mode, the method proceeds to step 710.
At step 710, the controller 100 may determine whether an auto resume function of the ACC system has been activated. If not, the method may return to step 620. However, if the auto resume mode function has been activated, the method may continue to step 720.
At step 720, the controller 100 may provide the current set points for vehicle speed and gap distance to the ACC system, so as to permit the ACC system to control vehicle devices, such as a throttle body and/or braking mechanism. To continue the example above, the ACC system may use the current gap set point of 50.2 meters in the next trip along the same route. However, if the controller 100 determines that the vehicle is traveling into a new location envelope and therefore along a route not previously traveled by the vehicle, the controller may assign the previously-learned gap set point to the new node. Similarly, if the controller 100 determines that the vehicle is traveling into a new location envelope, the controller may assign the previously-learned speed set point to the new node.
With regard to the processes, systems, methods, heuristics, etc. described herein, it should be understood that, although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating certain embodiments, and should in no way be construed so as to limit the claimed invention.
Accordingly, it is to be understood that the above description is intended to be illustrative and not restrictive. Many embodiments and applications other than the examples provided would be apparent upon reading the above description. The scope of the invention should be determined, not with reference to the above description, but should instead be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. It is anticipated and intended that future developments will occur in the technologies discussed herein, and that the disclosed systems and methods will be incorporated into such future embodiments. In sum, it should be understood that the invention is capable of modification and variation.
All terms used in the claims are intended to be given their broadest reasonable constructions and their ordinary meanings as understood by those knowledgeable in the technologies described herein unless an explicit indication to the contrary in made herein. In particular, use of the singular articles such as “a,” “the,” “said,” etc. should be read to recite one or more of the indicated elements unless a claim recites an explicit limitation to the contrary.
This application is a Continuation-in-Part of U.S. Ser. No. 13/846,969, with a filing date of Mar. 19, 2013, which application is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5956250 | Gudat et al. | Sep 1999 | A |
6012002 | Tapping et al. | Jan 2000 | A |
6198996 | Berstis | Mar 2001 | B1 |
6944533 | Kozak et al. | Sep 2005 | B2 |
7991549 | Kimita et al. | Aug 2011 | B2 |
8612107 | Malikopoulos | Dec 2013 | B2 |
8626568 | Warkentin et al. | Jan 2014 | B2 |
8676466 | Mudalige | Mar 2014 | B2 |
20020091473 | Gardner et al. | Jul 2002 | A1 |
20050102098 | Montealegre et al. | May 2005 | A1 |
20060271246 | Bell et al. | Nov 2006 | A1 |
20100100310 | Eich et al. | Apr 2010 | A1 |
20100256835 | Mudalige | Oct 2010 | A1 |
20100256836 | Mudalige | Oct 2010 | A1 |
20100256852 | Mudalige | Oct 2010 | A1 |
20110166731 | Kristinsson et al. | Jul 2011 | A1 |
20110184588 | Brusilovsky et al. | Jul 2011 | A1 |
20120083960 | Zhu et al. | Apr 2012 | A1 |
20120253605 | Denaro | Oct 2012 | A1 |
20120265433 | Viola et al. | Oct 2012 | A1 |
20120271544 | Hein et al. | Oct 2012 | A1 |
20130231824 | Wilson et al. | Sep 2013 | A1 |
Number | Date | Country |
---|---|---|
1111336 | Jun 2001 | EP |
1529695 | May 2005 | EP |
Number | Date | Country | |
---|---|---|---|
20140288799 A1 | Sep 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13846969 | Mar 2013 | US |
Child | 13903117 | US |