1. Field of the Invention
The invention relates to a centrifugal clutch in an automotive powertrain and a method for controlling clutch engagement.
2. Background Art
In the design of an automated heavy-duty vehicle powertrain system with an internal combustion engine and a multiple-ratio transmission, it is known practice to include a centrifugally operated clutch for coupling the engine to the torque input side of the transmission. The centrifugally operated clutch functions as a master friction clutch that is engageable during vehicle launch. The engagement is a function of throttle position and other system variables, such as engine speed, transmission input shaft speed, transmission output shaft speed, and engine torque. The transmission typically is a multiple-ratio transmission in which ratio changes are controlled using an electronic microprocessor controller. The transmission may be controlled manually, however, by the operator.
The engine may include a controller for regulating fuel supply to the engine based on a closed loop control technique using a microprocessor controller whereby the controller provides a target engine speed and a target engine torque. In the case of a spark ignition engine, spark timing can be used to achieve momentary torque delivery interruption during transmission ratio shifts. In the case of a diesel compression ignition engine, momentary torque interruption can be achieved using engine fueling control during transmission ratio shifts.
Centrifugally operated clutches in powertrains of this type are well known in the prior art. They typically include centrifugally actuated weights that are rotatable with a driving member coupled to the engine. The weights move freely outward under the effect of centrifugal force to cause the driving member to frictionally engage a driven power output member. Examples of a centrifugally operated clutch of this type can be seen by referring to U.S. Pat. Nos. 6,502,476; 5,441,137; 5,730,269; and 4,610,343.
In heavy duty vehicle powertrains, acceptable vehicle launch performance is achieved using closed loop control of engine speed variables. The clutch remains engaged as the controller allows dynamic shifting. The clutch remains engaged at engine speeds greater than the highest expected speed at which downshifts are initiated. It remains engaged also at engine speeds that are greater than the minimum expected engine speed after an upshift. This is accomplished simultaneously with control of engine fueling of the engine during a launch thereby causing the engine speed and torque to equal or not exceed target values. These are determined as a function of sensed input signals, which may be throttle position, engine speed, engine torque, transmission input speed, transmission output speed, transmission ratio, and clutch slip.
Control of the vehicle engine in a heavy duty powertrain of this type is successful if the engine is calibrated to accept engine speed limit requests from the vehicle controller. The control functions discussed in the preceding paragraphs are not compatible with control of a heavy-duty powertrain of known design that does not include an engine calibrated to respond to engine speed requests. Even if the engine is designed to accept engine speed requests, it may not be calibrated for all vehicle applications that might be used with a transmission with a centrifugally actuated clutch. A control response to a speed limit request is needed to achieve a smooth launch. If an engine of this type is used with a transmission with a centrifugally actuated clutch that does not respond to a clutch control strategy using speed limit requests, the clutch will function poorly and a launch will be characterized by undesirable inertia torque disturbances as the friction surfaces of the centrifugal clutch are engaged.
The invention includes a method for controlling a centrifugally actuated master clutch in a heavy duty powertrain that responds to torque requests. All electronically- controlled engines for heavy-duty powertrains that are capable of responding to engine speed requests, as described above, are capable also of responding to torque requests regardless of whether the engine manufacturer has calibrated the engine to correctly respond to speed requests. It is an objective of the invention, therefore, to provide a centrifugal clutch controller that is more universally acceptable for controlling engines in a heavy duty vehicle powertrain. This is accomplished by using the speed output of a known clutch controller and using it as an input to the controller of the present invention to produce a torque request that is distributed to the clutch controller to achieve high quality clutch engagements during launch without the need for a speed limit input. The controller of the invention includes a state filter, which provides a target speed and a target acceleration to effect an acceleration feed- forward value. That value is used, together with an engine inertia calibrated value, to produce an actual feed-forward torque. The inertia feed-forward torque then is combined with a calibrated engine friction feed-forward torque to produce feed-forward torque.
The filter is used also to generate a requested speed and acceleration to effect a smooth and fast acceleration buildup time. An acceleration signal is fed forward as a torque value after it is multiplied by an engine inertia term. This allows the controller to request the extra torque required to accelerate or decelerate the engine during launch.
The controller develops also a computed acceleration, which is multiplied by an estimate of the engine friction torque to produce a friction feed-forward torque. That acceleration term is integrated to produce a target engine speed, which is compared to an actual engine speed. The error in engine speed then is fed to a disturbance rejection system, which produces a feedback torque value. The error also is multiplied by a gain factor that is integrated before it is combined with the feed-forward torques in the computation of a torque request.
a is a generic schematic block diagram of a microprocessor controller that may be used in the control system of
a is a partial schematic view of a centrifugal clutch in which the centrifugally operated elements are in the clutch release position;
b is a partial schematic view of the centrifugal clutch of
a, 5b, and 6 illustrate a centrifugal clutch that functions as a master clutch in a heavy duty powertrain for delivering engine torque from an engine crankshaft to a power input member of a multiple-ratio, heavy-duty transmission. The clutch structure includes a clutch housing at 10 in
Each flyweight 12 carries one or more rollers 20. Each roller is supported for rotation in a recess 22 at the active end of the flyweight. The rollers are journaled about an axis that may intersect the pivot location shown at 14.
When the centrifugal clutch is at rest, the flyweights 12 assume the position shown in
The rollers 20 are situated between reaction plate 34 and clutch plate 36. A ramp surface 46 is formed on the clutch plate 36 whereby the separation of the reaction plate 34 from the clutch plate 36 is variable. The rollers 20, as they are moved in the direction of arrow 48, engage the ramp 46, thereby applying a clutch engaging force on the clutch plate 36 in a lefthand direction. That force is transmitted to the friction disks by a diaphragm plate spring, shown at 50. The spring 50 is preloaded so that the clamping force increases as the rollers 20 move radially outward. The clamping force is capped by a calibrated preload on the spring 50.
The clamping load created by the centrifugal clutch of
Reference may be made to U.S. Pat. No. 5,901,823 for a description of a clutch in which the maximum force applied to the friction elements uses a spring to limit the maximum force.
The plots shown in
The calibrated characteristics shown in
In the system diagram of
The engine includes an engine controller 96, which receives engine commands from the transmission electronic control unit 90 through a signal flow path 98. It also receives engine commands required for proper engine speed from an engine microprocessor unit 100, the latter distributing command signals to the engine controller through a signal flow path 102.
The module 110 includes data, stored in memory, that indicates a relationship between pedal position and engine speed. The pedal position information, transmitted in the form of speed data, as shown at 114, is distributed to module 116, which carries out a calculation to determine the required centrifugal speed for establishing a speed request at data link or signal flow path 118. This will be described with reference to
The engine speed request at 118 is received by control module 120, which establishes a torque request at data link or signal flow path 122. This also will be described with reference to
The torque request at 122 is distributed to the system electronic control unit 92, which carries out several control functions, including the determination of clutch and brake pressures for the transmission. The torque request at 122 is delivered also to engine microprocessor unit 100. The information received by the microprocessor unit 100 develops an engine command that is needed for the proper engine speed, which is distributed, as previously indicated, to the engine controller over a data link or signal flow path 102.
The engine microprocessor unit 100, which is illustrated in a generic, schematic form in
As previously indicated, the engine controller and the engine microprocessor respond to a torque request, rather than an engine speed request. The system shown in
In the system of
a is a generic schematic diagram of a known microprocessor that may be used to establish engine commands for the engine 80. It includes a random access memory 127 (RAM), a read-only memory 130 (ROM) and a central processing unit 132 (CPU). The CPU receives input data, including an engine torque request, and operator ratio and range selections after those input signals are conditioned at 134. The read-only memory 130 contains information of the kind previously described with reference to
The CPU receives the variables in RAM 127 following input signal conditioning and will execute the algorithms stored in read-only memory 130 using the variables in RAM to produce the necessary outputs at the output ports 136.
The required centrifugal speed calculation module 116 in
OUTPUT(K)=LESSER OF [INPUT (K)−OUTPUT (K−1)] AND LIMIT, PLUS OUTPUT (K−1)
where: K=a time sample
The engine speed request at the output side of the module 116 is a time sample of speed in a given control loop of the microprocessor. Its value is equal to the current speed represented by the current time sample constant K less the corresponding time sample for the speed during the previous control loop of the microprocessor. The time sample for the previous or last control sample is expressed by the calibration constant K−1. The difference between the current input speed and the last output speed is compared to a calibration parameter that establishes a limit on the rate of change of the speed signal. The new output speed is equal to the smaller of the limit value and the difference between the input speed during the current control loop and the output speed for the previous or last control loop, plus the output speed for the previous or last control loop. The result is the new output speed for the current time sample. This calculation prevents an undesirable fast change in the engine speed request, and it avoids a harsh clutch engagement, such as an engagement that would be obtained when a clutch is popped.
The engine speed request at 118, developed at 116, is distributed to the control module 120, as previously explained. The control module 120 is shown in diagrammatic form in
The actual engine speed signal at 154 is compared to the target engine speed at comparator 158 to determine an error at 160.
The target engine speed at 152 is fed back along signal flow path 162 and is compared to the desired engine speed at 164. The difference in the speed values at 118 and 162 is multiplied at 138 by the acceleration gain factor 140, which results in an acceleration value that is distributed to the filter module 142.
The target acceleration is a feed-forward term, as shown at 166, which is multiplied by a calibrated engine inertia term 168 to produce an inertia feed-forward torque at 170. The feed forward feature allows the controller time to request the extra engine torque required to accelerate the engine.
The error term at 160 is multiplied by a proportional term 172 to produce a feed forward torque value 174. The error is multiplied also by an integral term 176, and that value is integrated by a discrete sub-module 178 to produce a torque term 180. The torque term at 174 is added to the computed torque term at 180 to produce a feed forward torque at 182.
An engine friction coefficient at 184 is multiplied by the target engine speed at 152 to produce a feed-forward friction torque term at 186. The torque values at 170, 182 and 186 are added to produce an output torque request, as shown at 188. The feed forward value at 186 cancels out the effect of the viscous friction of the engine at the requested speed.
The feedback torque at 182 is that torque that is needed to achieve the proper engine speed component of the engine commands distributed to the controller over data link or signal flow path 102 seen in
Although separate electronic controllers are described, it will be apparent that a single electronic controller or microprocessor unit for the engine, the system and the clutch could be used incorporating the microprocessor unit architecture schematically illustrated in generic form in
Although embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation. It is understood that various changes may be made without departing from the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
3580372 | Schiefer | May 1971 | A |
3696901 | Henry | Oct 1972 | A |
3810533 | Densow | May 1974 | A |
4361060 | Smyth | Nov 1982 | A |
4361065 | Wilcox et al. | Nov 1982 | A |
4493228 | Vukovich et al. | Jan 1985 | A |
4515040 | Takeuchi et al. | May 1985 | A |
4593580 | Schulze | Jun 1986 | A |
4610343 | Hikari | Sep 1986 | A |
4646891 | Braun | Mar 1987 | A |
4648290 | Dunkley et al. | Mar 1987 | A |
4649331 | Jahns | Mar 1987 | A |
4698764 | Inagaki et al. | Oct 1987 | A |
4720793 | Watanabe et al. | Jan 1988 | A |
4754665 | Vandervoort | Jul 1988 | A |
4819779 | Nickel et al. | Apr 1989 | A |
4821590 | Tury et al. | Apr 1989 | A |
4850236 | Braun | Jul 1989 | A |
4899609 | Nagata | Feb 1990 | A |
5281902 | Edelen et al. | Jan 1994 | A |
5335566 | Genise et al. | Aug 1994 | A |
5370013 | Reynolds et al. | Dec 1994 | A |
5409432 | Steeby | Apr 1995 | A |
5437356 | Lohr | Aug 1995 | A |
5441137 | Organek et al. | Aug 1995 | A |
5481170 | Edelen et al. | Jan 1996 | A |
5490063 | Genise | Feb 1996 | A |
5509867 | Genise | Apr 1996 | A |
5582558 | Palmeri et al. | Dec 1996 | A |
5589986 | Shibata | Dec 1996 | A |
5600557 | Ogawa | Feb 1997 | A |
5620392 | Genise | Apr 1997 | A |
5730269 | Hersey | Mar 1998 | A |
5735771 | Genise | Apr 1998 | A |
5775639 | Fage | Jul 1998 | A |
5820104 | Koyano et al. | Oct 1998 | A |
5957001 | Gualtieri et al. | Sep 1999 | A |
5974354 | Janecke et al. | Oct 1999 | A |
5974906 | Stine et al. | Nov 1999 | A |
5980426 | Kamada et al. | Nov 1999 | A |
6015366 | Markyvech et al. | Jan 2000 | A |
6022295 | Liu | Feb 2000 | A |
6126570 | Bohm et al. | Oct 2000 | A |
6149545 | Genise et al. | Nov 2000 | A |
6321150 | Nitta | Nov 2001 | B1 |
6371081 | Hawkins et al. | Apr 2002 | B1 |
6484860 | Bassett | Nov 2002 | B1 |
6502027 | Saotome et al. | Dec 2002 | B2 |
6502476 | Genise | Jan 2003 | B2 |
6539820 | Markyvech | Apr 2003 | B2 |
6561948 | Markyvech et al. | May 2003 | B2 |
6564136 | Asumi et al. | May 2003 | B2 |
6571923 | Kummer | Jun 2003 | B2 |
6574535 | Morris et al. | Jun 2003 | B1 |
6609602 | Gochenour et al. | Aug 2003 | B2 |
6633806 | Gochenour | Oct 2003 | B2 |
6634476 | Inoue et al. | Oct 2003 | B2 |
6641504 | Genise et al. | Nov 2003 | B2 |
7232021 | Abusamra et al. | Jun 2007 | B2 |
7306084 | AbuSamra et al. | Dec 2007 | B2 |
7318513 | AbuSamra et al. | Jan 2008 | B2 |
7338409 | Ronge et al. | Mar 2008 | B2 |
7367440 | AbuSamra et al. | May 2008 | B2 |
20010005805 | Saotome et al. | Jun 2001 | A1 |
20020116111 | Sayman | Aug 2002 | A1 |
20020137595 | Markyvech et al. | Sep 2002 | A1 |
20020137596 | Markyvech | Sep 2002 | A1 |
20030033069 | Bauer et al. | Feb 2003 | A1 |
20030045987 | Gochenour | Mar 2003 | A1 |
20030065432 | Shuman et al. | Apr 2003 | A1 |
20030109358 | Sakamoto et al. | Jun 2003 | A1 |
20030143957 | Lyon | Jul 2003 | A1 |
20030145579 | Surnilla | Aug 2003 | A1 |
20030171867 | Nakamori et al. | Sep 2003 | A1 |
20030186782 | Genise | Oct 2003 | A1 |
20030187566 | Hess et al. | Oct 2003 | A1 |
20030225501 | De La Salle et al. | Dec 2003 | A1 |
20060172849 | Oliver et al. | Aug 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20060135317 A1 | Jun 2006 | US |