Various vehicles are equipped with reverse brake assist systems used to help prevent a driver from backing into an object in the rearward drive path. Such systems sense the presence of an object in the rearward path of the vehicle and take an action in response to such detection. For example, it is known to activate a sensory alarm (e.g., audible or visual) to alert the driver of the presence of an object in the rearward drive path. It is also known for the vehicle to automatically apply the vehicle brake system when an object is sensed in the rearward drive path. Such systems that automatically apply the brake system do so for a particular pre-determined amount of time after detection of the object, which may normally be sufficient to stop the vehicle before coming in contact with the object. However, the inventors have recognized that such automatic breaking systems are not as effective on low friction surfaces (e.g., ice, snow or rain) or on downward inclines as they are on normal high friction road surfaces. It is desirable to have an improved reverse brake assist system that is more effective on low friction and downward inclined surfaces.
A method of deactivating a vehicle's reverse brake assist system that had been automatically activated in response to detection of an object in a rearward path of the vehicle is disclosed. The method comprises detecting when the rearward motion of the vehicle has stopped and deactivating the vehicle brakes a pre-determined period of time after the rearward motion of the vehicle has stopped.
A method of controlling the deactivation of a vehicle brake system is disclosed. The vehicle is configured to detect an object in the drive path (rearward or forward) of a moving vehicle, and, in response to such detection, automatically activate the vehicle brake system. Application of the brake system is deactivated when (i) the system detects that the vehicle has actually stopped, and (ii) a predetermined amount of time thereafter has elapsed. A human-perceptible alert is generated when application of the automatic brake system is deactivated.
The method to deactivate the brake assist system starts at step 200 in
If the driver has not canceled application of the vehicle's reverse brake assist system, then the ECU 100 determines (step 250) the speed of the vehicle. At step 260, the ECU 100 determines if the vehicle has stopped (i.e., vehicle speed is zero). If not, then the algorithm loops back to step 240 to determine if the driver has canceled application of the brake system. If the vehicle has stopped, then the ECU 100 starts the automatic brake deactivation process at steps 270 through 310. Specifically, at step 280, the ECU 100 determines if it is time to display an HMI message indicating that the vehicle brakes are going to be released. If not, then the algorithm loops back to step 280. If so, then, the ECU 100 causes (step 290) an HMI message to be activated alerting the driver of the imminent release of the vehicle brakes. Then, the ECU determines (step 300) if it is time to deactivate the brake application. If not, then the algorithm loops back to step 300. If so, then the ECU 100 causes (step 310) deactivation of the vehicle brakes and the HMI alert message is canceled. At this point, the vehicle brake system has been deactivated. Accordingly, the algorithm loops back to step 210 to determine the vehicle state. The looping at steps 280 and 300 causes the deactivation of the vehicle brakes a pre-determined time period after it is determined that the vehicle has stopped.
As can be seen, the above-described system and method causes deactivation of the vehicle automatic brake system a pre-determined time after detection of the vehicle being stopped. As compared to systems wherein the vehicle brake system is deactivated a pre-determined period of time after its activation due to detection of the object in the rearward vehicle path, the system and method described above will ensure that the vehicle comes to a stop under any driving conditions before the brake system is deactivated.
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. For example, the above-described system and method could be used for forward motion (in addition to or instead of rearward motion).
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.
Number | Name | Date | Kind |
---|---|---|---|
4893691 | Park | Jan 1990 | A |
6129025 | Minakami et al. | Oct 2000 | A |
6604592 | Pietsch et al. | Aug 2003 | B2 |
7857339 | Paulson | Dec 2010 | B2 |
8332097 | Chiba et al. | Dec 2012 | B2 |
8386114 | Higgins-Luthman | Feb 2013 | B2 |
8421865 | Euler et al. | Apr 2013 | B2 |
8502860 | Demirdjian | Aug 2013 | B2 |
20050040939 | Jobes et al. | Feb 2005 | A1 |
20050209762 | Lu et al. | Sep 2005 | A1 |
20050246081 | Bonnet et al. | Nov 2005 | A1 |
20070061487 | Moore et al. | Mar 2007 | A1 |
20080154464 | Sasajima et al. | Jun 2008 | A1 |
20100114445 | Groult | May 2010 | A1 |
20100318256 | Breuer et al. | Dec 2010 | A1 |
20110054756 | Hecker et al. | Mar 2011 | A1 |
20120002052 | Muramatsu et al. | Jan 2012 | A1 |
20120300072 | Kim | Nov 2012 | A1 |
Number | Date | Country |
---|---|---|
2010163058 | Jul 2010 | JP |
Entry |
---|
Automatic Reverse Braking System, <http://www.projecttopics.info/Mechanical/Automatic—Reverse—Braking—System.php>. |
Intelligent Reverse Braking System, Abhishek Mishra and Anil KR. Upadhyay, <http://www.scribd.com/doc/94646980/Intelligent-Reverse-Braking-System>. |
English Translation of JP 2010163058. |