The present invention relates to systems for mitigating trailer sway. More specifically, embodiments of the invention relate to stabilizing trailer oscillation or sway in a vehicle towing system by using torque vectoring device without braking or slowing down the vehicle.
A trailer being towed by a tow vehicle can oscillate or sway back and forth for many different reasons and this sway can create vehicle stability problems. Some of the reasons that cause trailer sway include road conditions, traffic, weather conditions, load position, load quantity, and vehicle speed. Significant trailer sway can lift the rear end of a vehicle and push the vehicle to the side, significantly increasing the risk of loosing control of the vehicle and a rollover accident.
While there are existing systems for controlling and mitigating trailer sway, they do not, in general, include systems that mitigate the trailer sway without braking or slowing down the vehicle.
Existing systems that detect and control trailer sway in vehicles generally control the brake system of the vehicle in order to brake the wheels of the trailer or the vehicle and to control the trailer sway. In this situation, the vehicle eventually slows down or stops. Trailer sway mitigation systems that rely on braking are sometimes abrupt in their level of driver intervention. Thus, drivers often find such systems disturbing or unsettling. In addition, some conventional vehicle systems transfer drive torque between the left and the right vehicle wheels when the vehicle is turning (e.g., when the vehicle is proceeding around a corner). However, trailer sway occurs not only during turning situations, but also when a vehicle is driving in a straight line (forward or backward). Accordingly, there is a need for an improved system and method for stabilizing trailer sway that transfers drive torque between the rear wheels using a torque vectoring device without slowing down or braking the vehicle.
The invention provides a system for stabilizing a sway of a trailer attached to a vehicle. The system includes a controller, a plurality of sensors in electronic communication with the controller and transmitting sensor data to the controller. A torque vectoring device is in electronic communication with the controller, and a computer readable memory stores instructions executed by the controller. The instructions cause the controller to evaluate the sensor data received from the sensors to determine a current vehicle yaw rate, a target vehicle yaw rate, and a yaw rate error of the vehicle. The instructions further cause the controller to determine if the vehicle is traveling in a straight line, to determine a torque distribution signal, and to transmit this signal to the torque vectoring device to stabilize the sway of the trailer without braking the vehicle.
The invention also provides a method for stabilizing a sway of a trailer attached to a vehicle. The method includes receiving sensor data from a plurality of sensors at a controller, evaluating the sensor data received from the sensors, determining a current vehicle yaw rate, a target vehicle yaw rate, and a yaw rate error of the vehicle. The method further includes determining if the vehicle is traveling in a straight line, determining a torque distribution signal, and transmitting the torque distribution signal to a torque vectoring device to stabilize the sway of the trailer without braking the vehicle.
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.
As best illustrated in
The sensors 40 are used to sense current operating conditions of the vehicle 15 and provide information representative of the same to the controller 32. The sensors 40 transmit sensor measurement data in a defined data structure that can include analog data or digital data. These sensors 40 include one or more wheel speed sensors, yaw rate sensors, lateral acceleration sensors, steering angle sensors, and brake pressure sensors. In other embodiments, the vehicle 15 could include more or less sensors. In embodiments utilizing the ESP system, the sensors 40 are the sensors incorporated in that system. If the sensors are equipped with calibration circuitry or a processor, the sensors can internally convert the sensed conditions to a calibrated form. Otherwise, the sensed conditions can be converted into calibrated signals by other external processes, e.g., the ECU 32). The sensors 40 can be connected directly to the ECU 32 or connected to a network, such as a controller area network (CAN) bus 70, which is connected to the controller 32. The CAN bus 70 is connected to other vehicle systems.
As best shown in
As noted, trailer oscillation can occur not only during turning situations but also when the vehicle 15 is driving in a straight line (forward or backward). Some of the reasons for this type of trailer sway include road conditions (e.g. driving over potholes, road bumps, or other objects on the road), traffic (e.g., sudden braking due to traffic congestion or accident), position and quantity of the load of the trailer 20, and the speed of the vehicle 15. As explained below, the system 30 is configured to regulate the trailer sway created while driving in a straight line or cornering without braking or slowing down the vehicle 15. The system 30 distributes torque between the back wheels 65C and 65D with the torque vectoring device 60.
In the embodiment illustrated in
The RAM 130 and the ROM 135 can be internal to the processor 120, external to the processor 120, or a combination thereof. The EPU 120 sends information (e.g., information received from the bus 70 or information generated by the modules executed by the EPU 120) to the RAM 130. Further, the RAM 130 can receive and store data from other components of the system 30. While RAM 130 is used in the embodiment shown in
The controller 32 also includes a variety of systems (e.g., in the form of hardware) and modules that are stored as instructions in a memory (e.g., RAM 130 or ROM 135) and are executed by the EPU 120. In one particular configuration, the controller 32 comprises an application or software module 140, a band-pass filter 145, a plurality of summing nodes circuits 150, and a proportional integral derivative (“PID”) controller 155. In one embodiment, the software module 140 is the Software module of the ESP controller in Robert Bosch's ESP system.
As described in greater detail below, the software module 140 is a software program executed by the EPU 120 and is architected to evaluate the sensor data received from the sensors 40 to determine a current vehicle yaw rate, a target vehicle yaw rate, and a yaw rate error of the vehicle 15. Further, the software module 140 is architected to communicate with the other elements of the controller 32 (e.g., the band-pass filter 145 and the PID controller) to determine a trailer yaw rate and a torque distribution signal, and to transmit this torque distribution signal to the torque vectoring device 60. The torque vectoring device 60 is operable to distribute a compensatory wheel torque to the wheels 65 based on the torque distribution signal in order to stabilize the sway of the trailer.
The operation of the system 30 is illustrated in
The software module 140 receives the sensor readings from the sensors 40 and is configured to process the received readings. As mentioned above, one of the inputs to the module 140 is the vehicle yaw rate 183 of the vehicle 15. Based on the sensor data, the software module 140 calculates the speed of the vehicle 15. Further, the software module 140 analyzes the information about the steering wheel angle received from the steering angle sensor 175. The module 140 determines whether the driver is actually steering the vehicle intentionally or the oscillation of the vehicle is based on the trailer sway. The module 140 further determines if the vehicle 15 is traveling in a straight line or is cornering. By using the determined vehicle speed, the vehicle yaw rate 183, and by evaluating the data from the sensors 40, the software module determines a target vehicle yaw rate 185. The target yaw rate 185 represents the driver-intended yaw rate of the vehicle 15 based on the analyzed characteristics.
Next, the controller 32 provides the target vehicle yaw rate 185 determined by the software module 140 to a first summing node circuit 150. The other input to the first summing node circuit 150 is the current vehicle yaw rate 183 filtered by the software module 140. The output from the first summing node circuit 150 is a yaw rate error signal E1 that shows the difference between the target vehicle yaw rate 185 intended by the driver and the current vehicle yaw rate 183 measured by the system 30. The yaw rate error signal E1 represents the level of input of the trailer sway to the vehicle yaw rate.
The determined yaw rate error signal E1 is inputted into the band-pass filter 145. The band-pass filter 145 filters the yaw rate error signal E1 and passes signals of specific frequency that are indicative of the trailer sway. This helps to distinguish between the actual trailer sway and driver assisted sway where the vehicle oscillates due to the fact that the driver intentionally cause the vehicle to turn by moving the steering wheel. For example, the band-pass filter 145 can be configured to filter the received signal and to pass signals that have frequencies between 0.5 Hz and 1.5 Hz. When the yaw rate error signal has very low or very high frequency, the system determines that this is not caused by the trailer sway. Such low or high frequencies of the yaw rate error signal can be created by driving fast or steering the vehicle by the driver.
The band-pass filter 145 outputs a signal 187 that represents the actual yaw rate of the trailer 20. That signal is inputted into a second summing node circuit 150. The second input to the second summing mode circuit 150 is a trailer target yaw rate 189. The value of the trailer target yaw rate 189 depends on the moving direction of the vehicle and the trailer. For example, when the vehicle and the trailer move in a straight direction, the trailer target yaw rate 189 is always a constant zero because the driver wants to move straight. Having the trailer target yaw rate 189 at a constant zero and summing it with the actual trailer yaw rate 187, allows the system 30 to control the actual trailer yaw rate 187, and consequently the trailer sway, based on the determined characteristics of the vehicle and the trailer. Further, when the vehicle and the trailer are cornering, the trailer yaw rate 187 is a specific value associated with the radius of cornering. The output of the second summing mode circuit 150 is an asymmetric controller signal E2 that will bring the vehicle and the trailer to a steady state (e.g., driver intended state).
The outputted asymmetric controller signal E2 can be different depending on the current traveling situation of the vehicle 15 and the trailer 20. For example, during cornering of the vehicle 15 the trailer 20 must sustain a certain yaw rate in order to make the corner along with the vehicle. In that case, the trailer target yaw rate 189 is greater than zero. The controller 32 evaluates the speed and the position of the vehicle 15 and the trailer 20, and determines the trailer target yaw rate needed for the trailer to make that corner. Based on that determination, the controller 32 outputs the appropriate asymmetric controller signal E2 (a signal that is greater than zero). In another example, the controller 32 determines that the trailer must travel with no yaw rate at all (e.g., when the vehicle is driving straight) and it should not be oscillating at all. In that situation, trailer target yaw rate 189 is zero and the outputted asymmetric controller signal E2 would require the system 30 to produce the appropriate amount of torque that would stabilize the trailer 20 completely.
The asymmetric controller signal E2 output from the second summing node circuit 150 is input into the PID controller 155. The role of the PID controller is to amplify the asymmetric controller signal E2 by converting it to a voltage signal. The PID controller 155 outputs a continuous asymmetric torque distribution signal 190 that is transmitted to the torque vectoring device 60. The continuous asymmetric torque distribution signal 190 includes information about the compensatory wheel torque that the torque vectoring device 60 needs to distribute to the back wheels of the vehicle 15 to stabilize the sway of the trailer. The torque transferred between the wheels of the vehicle 15 counters the trailer sway and stabilizes the trailer 20 without braking or slowing down the vehicle.
In some configurations, the torque vectoring device 60 includes a controller that executes software stored on a memory (elements not shown). The torque vectoring device 60 receives the continuous asymmetric torque distribution signal 190 and distributes compensatory wheel torque either to the left back wheel, the right back wheel, or both back wheels as directed by the signal 190 in order to stabilize the trailer sway. For example, the torque vectoring device 60 transfers torque from the right back wheel to the left back wheel (e.g., when the trailer sways to the left,
In an embodiment, the torque vectoring device 60 needs additional compensatory wheel torque in order to control the trailer sway. The torque vectoring device 60 does not produce any torque on its own but only distributes torque based on the asymmetric torque distribution signal 190. The additional torque is generally produced or generated by the engine 50. The torque vectoring device 60 sends a compensatory wheel torque request to the four-wheel drive coupling device 45 based on the torque distribution signal 190. The four-wheel drive coupling device 45 includes a controller that executes software stored on a memory and determines how much torque is currently transferred from the engine 50 to the torque vectoring device 60. Based on that determination and the request from the torque vectoring device 60, the four-wheel drive coupling device 45 transfers the necessary torque from the engine 50 to the torque vectoring device 60.
The transfer and control of torque from the torque vectoring device 60 to the back wheels 65B is completed, in one configuration, by using a clutch plate (not shown). The amount of torque transmitted to the clutch plate from the engine 50 is regulated by the torque vectoring device 60 and the clutch plate distributes the torque to an input shaft that drives an output shaft, which distributes the torque to the wheels 65B. In another embodiment, the transfer and control of torque is completed by using a motor (not shown) that connects the torque vectoring device 60 and the back wheels 65B.
Next, the system 30 determines the actual trailer yaw rate 187 of the trailer 20 by passing the yaw rate error signal E1 through the band-pass filter 145 (step 225). Then, the system 30 determines the asymmetric controller signal E2 by using the second summing node circuit 150 that inputs the actual trailer yaw rate 187 and the trailer target yaw rate 189 that is equal to zero (when driving straight) or is greater than zero (when cornering) (step 230). Using the PID controller 155, the system transforms the asymmetric controller signal E2 and produces the continuous asymmetric torque distribution signal 190 that is provided to the torque vectoring device 60 in order to stabilize the oscillation of the trailer without braking the vehicle (step 235).
The torque vectoring device 60 analyzes the torque distribution signal 190 and determines the amount of torque that needs to be transferred to the back wheels (step 240). If the torque vectoring device 60 determines that the amount of torque that is currently available in the back wheels is sufficient to stabilize the trailer sway (step 245), the torque vectoring device 60 transfers the torque between the wheels as directed by the torque distribution signal 190 (step 250). The transferred torque counters the trailer sway and stabilizes the trailer 20. If the torque vectoring device 60 determines that the amount of torque that is currently available in the back wheels is insufficient to stabilize the trailer sway (step 245), the torque vectoring device 60 requests additional torque from the controllable four-wheel drive coupling device 45 (step 255). When torque vectoring device 60 receives the necessary torque from the engine 50 via the four-wheel drive coupling device 45, the torque vectoring device 60 transfers the torque to the wheels and stabilizes the sway of the trailer (step 250).
Various features and advantages of the invention are set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4023863 | Sisson et al. | May 1977 | A |
4034822 | Stedman | Jul 1977 | A |
RE30550 | Reise | Mar 1981 | E |
4254998 | Marshall et al. | Mar 1981 | A |
4275898 | Llambrich | Jun 1981 | A |
5011170 | Forbes et al. | Apr 1991 | A |
5671982 | Wanke | Sep 1997 | A |
5707071 | Prestidge et al. | Jan 1998 | A |
5747683 | Gerum et al. | May 1998 | A |
5799745 | Fukatani | Sep 1998 | A |
5986544 | Kaisers et al. | Nov 1999 | A |
6012780 | Duvernay | Jan 2000 | A |
6042196 | Nakamura et al. | Mar 2000 | A |
6074020 | Takahashi et al. | Jun 2000 | A |
6446998 | Koenig et al. | Sep 2002 | B1 |
6450019 | Wetzel et al. | Sep 2002 | B1 |
6498977 | Wetzel et al. | Dec 2002 | B2 |
6516260 | Wetzel et al. | Feb 2003 | B2 |
6522956 | Hecker et al. | Feb 2003 | B2 |
6523911 | Rupp et al. | Feb 2003 | B1 |
6550810 | Bauer et al. | Apr 2003 | B1 |
6600974 | Trechtler | Jul 2003 | B1 |
6655710 | Lindell et al. | Dec 2003 | B2 |
6668225 | Oh et al. | Dec 2003 | B2 |
6748307 | Sala et al. | Jun 2004 | B1 |
6940026 | Rundell et al. | Sep 2005 | B2 |
6959970 | Tseng | Nov 2005 | B2 |
7226134 | Horn et al. | Jun 2007 | B2 |
7272481 | Einig et al. | Sep 2007 | B2 |
7302332 | Nenninger | Nov 2007 | B2 |
7561953 | Yu | Jul 2009 | B2 |
7917274 | Hackney et al. | Mar 2011 | B2 |
8060288 | Choby | Nov 2011 | B2 |
20040249547 | Nenninger | Dec 2004 | A1 |
20060033308 | Waldbauer et al. | Feb 2006 | A1 |
20060108781 | Giordano | May 2006 | A1 |
20060125313 | Gunne et al. | Jun 2006 | A1 |
20060155457 | Waldbauer et al. | Jul 2006 | A1 |
20060204347 | Waldbauer et al. | Sep 2006 | A1 |
20060229782 | Deng et al. | Oct 2006 | A1 |
20070260385 | Tandy, Jr. et al. | Nov 2007 | A1 |
20080036296 | Wu et al. | Feb 2008 | A1 |
20080172163 | Englert et al. | Jul 2008 | A1 |
20090005931 | Komatsu | Jan 2009 | A1 |
20090005946 | Futamura et al. | Jan 2009 | A1 |
20090093928 | Getman et al. | Apr 2009 | A1 |
20090105906 | Hackney et al. | Apr 2009 | A1 |
20090198425 | Englert | Aug 2009 | A1 |
20090210112 | Waldbauer et al. | Aug 2009 | A1 |
20090228182 | Waldbauer et al. | Sep 2009 | A1 |
20090242289 | Murty | Oct 2009 | A1 |
20090306861 | Schumann et al. | Dec 2009 | A1 |
20100203999 | Yokoo et al. | Aug 2010 | A1 |
20100211277 | Craig et al. | Aug 2010 | A1 |
20120053806 | Tronnberg et al. | Mar 2012 | A1 |
Number | Date | Country |
---|---|---|
102005028787 | May 2006 | DE |
1516792 | Mar 2005 | EP |
2856362 | Dec 2004 | FR |
2402453 | Dec 2004 | GB |
07164924 | Jun 1995 | JP |
2005132360 | May 2005 | JP |
Entry |
---|
PCT/US2011/057799 International Search Report and Written Opinion dated May 4, 2012 (11 pages). |
Office Action from the Japanese Patent Office for Application No. 2009-524739 dated Jul. 13, 2012 (Translation only, 2 pages). |
Number | Date | Country | |
---|---|---|---|
20120109471 A1 | May 2012 | US |