Patent Grant
8398526
1. Field of the Invention
This invention relates generally to a vehicle powertrain having an input clutch. More particularly, the invention pertains to a method for controlling the clutch during a vehicle launch condition.
2. Description of the Prior Art
A vehicle launch is a low-speed drive-away event in which a vehicle with a transmission is accelerated in response to the vehicle operator depressing an accelerator pedal. When the vehicle powertrain is equipped with a conventional automatic transmission, launch behavior is largely regulated by the torque converter, which ultimately sets engine speed and wheel torque as a dynamic function of engine torque. In this conventional powertrain setting, the torque converter characteristics are first engineered to trade off fuel economy and driving performance, then engine pedal maps (the engine control software relationship between accelerator pedal position and engine torque) are tuned to provide the best vehicle feel for the given converter design.
Launch control is used to facilitate vehicle motion from standstill after the driver presses the gas pedal indicating his intention to initiate vehicle motion. In automatic transmissions the launch functionality is provided with a torque converter, which has inherent positive characteristics, such as torque multiplication at low speed ratio, characteristic of launch situations both on level roads and hills. A torque converter also provides hill holding capability. It provides a natural damping or filtering of any possible drivability and NVH-related disturbances that may occur due to jerky gas pedal motion caused by a driver's change-of-mind and similar actions. A torque converter, however, dissipates energy, reducing fuel economy, and imposes a space and weight penalty.
Due to these limitations, an emerging trend in automatic transmission design eliminates the torque converter and replaces it with appropriately controlled friction clutches. One such example is the so-called Powershift (PS) transmission, consisting of only two clutches (one for odd and one for even-numbered gears), synchronizers-like couplers, manual transmission-like gears, sensors and either electrical or electro-hydraulic actuation of the clutches and synchronizers.
Such transmissions offers a number of advantages including low parts count, simplicity, robustness of design, and substantial commonality with manual transmissions, thereby facilitating common production.
The Powershift transmission enables the use of algorithms that can control the clutch in ways more complex than the passive torque converter, eliminating or reducing some of the design tradeoffs inherent in the passive torque converter system. For example, the clutch can be fully opened when the driver presses the brake pedal, eliminating transmission drag on the idling engine, thereby improving fuel economy.
In the automatic clutch setting, the intent of the launch function is to provide a wheel torque that reflects driver demand from the accelerator pedal and provides an engine speed trajectory that meets the competing requirements of providing a “power-on” feel and sound to the driver while limiting clutch component wear associated with slip across the device.
A need exists in the industry for control of the input clutch such that robust, optimized performance is obtained.
A method for controlling a transmission input clutch during a vehicle launch includes determining a desired clutch torque, a desired engine torque, a desired vehicle acceleration and a desired engine speed, determining a change in clutch torque and a change in engine torque with reference to the first and second errors and current operating conditions, applying to the clutch an updated clutch torque capacity whose magnitude is the sum of the desired clutch torque and the change in clutch torque, and producing an updated engine torque whose magnitude is the sum of the desired engine torque and the change in engine torque.
The control produces vehicle behavior that is expected by drivers accustomed to a conventional automatic transmission, and provides a system tuning method similar to that used in a conventional transmission, allowing carryover of former engineering techniques and experience.
The control simplifies the design by eliminating the need for multiple tuned control loops with associated feedback measurement targets and the inherent difficulties of aligning those targets with engine torque.
The control method is insensitive to engine torque hesitation, engine torque errors with respect to driver demand, and clutch torque errors as compared to other control approaches.
The scope of applicability of the preferred embodiment will become apparent from the following detailed description, claims and drawings. It should be understood, that the description and specific examples, although indicating preferred embodiments of the invention, are given by way of illustration only. Various changes and modifications to the described embodiments and examples will become apparent to those skilled in the art.
The invention will be more readily understood by reference to the following description, taken with the accompanying drawings, in which:
Referring now to
To provide a vehicle launch behavior that is consistent with conventional transmissions, the clutch is controlled during the launch event such that it emulates the behavior of a passive transmission input device, such as a torque converter.
The control system of
After the driver depresses the accelerator pedal 11, at 13, engine torque 14 increases with a resulting increase in engine speed 11. As slip 18 across the clutch 10 increases, the torque transmitting capacity of the clutch 10 increases in response, bringing the engine speed 11 into a quasi-equilibrium state and providing propulsion torque to the wheels 6, 7. Ultimately the engine speed 11 converges sufficiently close to the input shaft speed 12 that the launch event is considered complete, and the transmission and clutch controls enter a new state of operation.
Engine speed 11 and transmission input speed 12 are measured and supplied as input to the physical device model 22, which produces a clutch torque command 24. A servo for actuating clutch 10 responds to command 24 by producing the clutch torque capacity corresponding to command 24.
The system operates closed-loop and can be analyzed using conventional closed-loop system design methods. However, the controller 20 in this form is not a tracking controller, i.e., it does not attempt to track a target engine speed or target wheel torque. Instead, wheel torque response and engine speed trajectory during the vehicle launch are tuned by adjusting the characteristics of the model 22 of the passive device and adjusting the software that controls engine torque 14 in response to driver inputs and the vehicle state.
Two possible physical device models 22 are detailed in Equations (1) and (2). Equation (1) models a viscous damper whose desired torque is simply proportional to the slip across clutch 10:
τdesired=k(Neng−Ntrans) (1)
Here, τdesired is the desired clutch torque, Neng is engine speed 11, Ntrans is transmission input shaft speed 12, and k is an adjustable proportionality constant.
Equation (2) models a fluid coupler that behaves like a torque converter operating above its coupling point:
Here, R is the capacity factor, a function of the ratio of engine speed 11 and transmission input shaft speed 12. This function, R the capacity factor, can be determined from a polynomial, a table, or other means indexed by Neng and Ntrans.
Launch performance can be improved in some vehicle systems if different physical device models are chosen according to driver accelerator pedal position. This can be accomplished in the Equation 1 and 2 settings by adjusting proportionality constant k (Equation 1) or capacity factor R (Equation 2) as a function of pedal position.
It is important to note that some physical devices cannot be fully modeled by this method, because a clutch produces the same torque (with opposing direction) on both its input and output shafts, but a device such as a torque converter can provide torque multiplication from its input to its output.
The engine dynamic characteristics and vehicle dynamic characteristics 26, such as mass and inertia, road conditions including road grade and friction, and operating conditions including altitude, determine the engine speed 10 and vehicle acceleration rate 28 during the launch. Model 22 includes checks to ensure that if the depressed position of accelerator pedal 11 is decreasing, the desired clutch torque 16 is not increasing.
A major benefit of this method of clutch control is that clutch torque 16 is responsive to engine speed 11 rather than being responsive to an engine speed error with respect to an engine speed target. This means that clutch 10, like a torque converter or coupler, will not start to produce torque until the engine speed 11 responds to an engine torque increase 14. Therefore, the clutch 10 is not prone to stalling the engine should the engine hesitate during cold operation or when operating on degraded fuel. Similarly, with a properly designed device model 22, clutch torque 16 will find equilibrium with the engine torque 14 regardless of any torque error associated with the engine controls. For instance, engine torque capacity is significantly degraded at high altitude. If the engine controls do not properly account for altitude variation, the clutch torque response and vehicle launch behavior will remain well controlled, because they do not depend on engine torque estimation.
While this method is robust to engine torque errors, clutch torque errors, such as when the clutch system 10 produces the wrong torque as compared to the requested clutch torque, can lead to excessive clutch slip 18. For instance, if clutch 10 produces only one-half of the requested clutch torque 16, the slip 18 across clutch 10 must increase sufficiently to double the clutch torque request so that the actual clutch torque 16 properly balances engine torque 14. This increase in clutch slip 18 can lead to unwanted clutch wear.
To address this concern, a supervisory controller 30 can be constructed as shown in
A typical control law would employ an integral of the error 36, tuned to provide correction of the clutch system torque 16 gently enough to avoid unwanted torque disturbances at the vehicle wheels. Note that the physical device model 22 used in the launch control system 20 is reproduced in the system model inside the supervisory controller 32. Also, using the measured transmission input shaft speed 12 as another input to the supervisory vehicle model 30 insures that the modeled vehicle dynamics are unaffected by changes in road grade or vehicle mass, or a combination of grade and mass.
To provide a vehicle launch behavior that is consistent with conventional transmissions, clutch 10 is controlled during the launch event such that it emulates the behavior of a passive transmission input device, such as a torque converter, viscous coupling, etc.
The controller 52 includes various mathematical models: a clutch torque model 54; engine and accelerator pedal maps 56; a vehicle acceleration model 58, engine speed model 60; a closed loop controller 64, such as a PID controller; and summing junctions 65, 65, 66, 67. The plant 62 is the engine 2 and clutch 10 that are being controlled during the vehicle launch event.
Controller 52 includes three parts: (1) generation of the desired vehicle acceleration 78 and desired engine speed 80 using models 58 and 60, respectively; (2) a closed loop part that operates on (i) the error 74 between the actual engine speed 70 produced by plant 62 and the desired engine speed 80 from model 60, and (ii) the error 76 between the actual vehicle acceleration 72 produced by plant 62 and the desired vehicle acceleration 78 from model 58; and (3) generation of open-loop or feed-forward controls: desired clutch torque 82 and desired engine torque 84.
The open-loop or feed-forward desired clutch torque 82 is determined from a clutch torque model 54, preferably stored electronically in a look-up table, the model being a function of engine speed Ne and the speed of transmission input 8. The open-loop desired engine torque 84 is determined from a engine torque model 56, also stored electronically in a look-up table, the model being a function of engine speed Ne, pedal position 92 and the speed of transmission input 8. The desired vehicle acceleration 78 is determined from the vehicle acceleration model 58, which is a function of engine speed Ne, pedal position 92 and the speed of transmission input 8. The desired engine speed 80 is determined from the engine speed model 60, which is a function of engine speed Ne, pedal position 92 and the speed of transmission input 8.
The nominal model and the open-loop part can contain feedback aspects, e.g., engine mapping torque Te, m scheduling based on engine speed Ne. This type of feedback is called “structural feedback” to distinguish it from the closed-loop control feedback based on an explicit error calculation. In some cases structural feedback may be based on slow or heavily filtered variables, such as vehicle speed VS.
Considerable flexibility is available in choosing the nominal models. One possibility is to use only “open-loop” controls, i.e., models 54, 56, and tailor the engine torque model 56 according to non-electronic throttle control engine “cross-sectional” maps where the accelerator pedal 90 is mechanically, rigidly connected to the engine throttle plate. The clutch torque model 54 produces desired wheel torque as a function of transmission input speed Ni, engine speed Ne and pedal position 92. Since engine mapping is fixed and determined by non-launch conditions, this mapping technique is essentially one degree-of-freedom (DOF), i.e. clutch control-based open-loop, the open-loop part being in the form of a structural feedback.
A one DOF control can be deployed with clutch-control only reinforced with closed-loop controls that ensure repeatability and robustness in view of model and vehicle uncertainties and changes. In this case, clutch torque model 54, vehicle acceleration model 58 and engine speed model 60, on the one hand and models 54 and 58 on the other hand, are synchronized to emulate behavior of different coupling devices 10, such as a linear viscous coupling, fluid coupling or torque converter.
In the case of a vehicle launch control that emulates performance of a viscous coupling, the open-loop portion of the clutch torque model 54 is set forth in the equation
τ=k1(Ne−Ni) (1)
wherein the desired clutch torque T is proportional to the slip across clutch 10, Ne is engine speed and Ni is transmission input speed. This can be further extended to a more general form
τ=k1[Ne−(k2Ni+k3Nidle)] (2)
wherein typically, k3=1. The intent of this expression is to prevent engine loading below the engine idle speed Nidle and to follow the desired vehicle speed, or its equivalent Ni with some desired slope governed by k2.
For the case in which a fluid coupling is emulated, instead of the above linear relations, the quadratic relation among the clutch torque, engine speed and transmission input speed can be imposed.
On a more general level, it is possible to prescribe any desired vehicle acceleration and engine speed behavior in models 58, 60, respectively, as a function of vehicle speed VS or transmission input speed Ni, which is proportional to vehicle speed. In this two DOF approach, both attributes, vehicle acceleration 70 and engine speed Ne, are prescribed within some physical limits.
The two key output components or attributes of the plant 62 that influence the quality of the vehicle launch are the desired or modeled engine speed 80 and desired or modeled vehicle acceleration 78 (or the closely related wheel torque). The vehicle acceleration model 58 produces as output desired vehicle accelerations for a vehicle launch event empirically determined with reference to accelerator pedal position PP 92, engine speed Ne and the speed Ni of transmission input 8. Similarly, the engine and clutch speed model 60 produces as output desired engine speeds for a vehicle launch event determined empirically with reference to accelerator pedal position PP 92, engine speed Ne and the speed Ni of transmission input 8.
In the form of an Input-Output matrix transfer function, the closed loop controller 64 employs both the engine 2 and clutch 10 to control plant 62 output attributes: engine speed Ne 70 and vehicle acceleration 72.
Summing junction 65 produces a vehicle acceleration error (e, acc) 76 representing the difference between the current vehicle acceleration 72 produced by the plant 62 and the desired vehicle acceleration 78 produced as output from vehicle acceleration model 78. Summing junction 66 produces a vehicle speed error (e, Ne) 74 representing the difference between the current vehicle speed 70 produced by the plant 62 and the desired vehicle speed 80 produced as output from vehicle speed model 60.
The closed loop controller 64, preferably a PID controller, is supplied with data 86 representing information, such as ambient temperature, barometric pressure and road grade, required to determine the current engine output torque commanded by the vehicle operator. The closed loop controller 64 uses errors 74 and 76 and data 86 to produce (i) a signal 94 representing a change in commanded clutch torque to be produced by clutch 10, and (ii) a signal 96 representing a change in commanded engine torque to be produced by engine 2.
At summing junction 67, the feed-forward signal 82, representing desired clutch torque, and the feedback signal 94, representing the change in commanded clutch torque, are combined algebraically to produce a signal 98 representing a new or updated commanded clutch torque 52. Preferably signal 98 is converted to a signal that is applied to a solenoid that controls the magnitude of pressure applied to the servos that control the variable magnitude of torque capacity to be transmitted by clutch 10.
Similarly, at summing junction 68, the feed-forward signal 84, representing desired engine torque, and the feedback signal 96, representing the change in commanded clutch torque, are combined algebraically to produce a signal 100 representing a new or updated engine torque to be produced by engine 2.
The open loop, feed-forward desired or modeled clutch torque 82, determined from clutch engine torque map 54 with reference to accelerator pedal position PP 52, engine speed Ne and the speed Ni of transmission input 8, is supplied as input to clutch 10 of the plant 62. At 102, the desired clutch torque 82 or updated clutch torque 98 operates on the vehicle mass Ms to produce the current vehicle acceleration 72 during the vehicle launch event. The current vehicle acceleration is integrated to produce a current vehicle speed 71 during the launch event.
Desired engine torque 84, determined from engine torque map 56 with reference to accelerator pedal position PP 92 and at least one of the speed of engine 2 and the speed of input 8, is supplied as input to summing junction 104.
Similarly, the engine speed model 60 processes current accelerator pedal position PP 92, engine speed Ne and transmission input speed Ni to produce the desired engine speed Ne 80, which is supplied as input to summing junction 66. The engine speed error signal 74 is supplied to closed loop controller 64.
At summing junction 104, the output of summing junction 68, which is the change in engine torque 96, 100, is combined algebraically with desired clutch torque 82 and desired engine torque 84 producing a signal representing the torque 108 used to accelerate rotating components upstream of clutch 10. At 110, torque 108 is applied to the rotational inertial J of the rotating components upstream of clutch 10, principally the mass moment of inertia of engine 2 and driveshaft 3, producing the current engine acceleration, which is integrated to produce the current speed 70 of the engine 2 and driveshaft 3.
Closed-loop implementation requires adequate sensors are available for key measured variables including engine speed. But other relevant variables including wheel torque or vehicle acceleration are not always available and can be estimated based on physical models. Of course, if reliable low-cost wheel torque sensors become available they could be used to further enhance the launch control method.
This application is a continuation-in-part of pending U.S. application Ser. No. 12/015,920, filed Jan. 17, 2008.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4081065 | Smyth et al. | Mar 1978 | A |
| 4091902 | Hamada | May 1978 | A |
| 4576263 | Lane et al. | Mar 1986 | A |
| 4620624 | Mitsui et al. | Nov 1986 | A |
| 4715467 | Sakai | Dec 1987 | A |
| 4723644 | Sakakiyama | Feb 1988 | A |
| 4799160 | Arbeille et al. | Jan 1989 | A |
| 6083139 | Deguchi et al. | Jul 2000 | A |
| 6482123 | Steeby | Nov 2002 | B2 |
| 6676561 | Fritzer et al. | Jan 2004 | B2 |
| 6767311 | Yoshikawa et al. | Jul 2004 | B2 |
| 7037239 | Werner et al. | May 2006 | B2 |
| 7070538 | Babcock | Jul 2006 | B2 |
| 7158873 | Eich et al. | Jan 2007 | B2 |
| 7255663 | Kawamoto et al. | Aug 2007 | B2 |
| 7628728 | Soliman et al. | Dec 2009 | B2 |
| 20050137058 | Fujimoto et al. | Jun 2005 | A1 |
| 20060014608 | Mitchell et al. | Jan 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20100105523 A1 | Apr 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12015920 | Jan 2008 | US |
| Child | 12652865 | US |
