Hybrid vehicles typically have a combustion engine and an eMachine which can act as both an electric motor and a generator. During braking, such vehicles are capable of capturing and storing the braking energy in a battery for later use in propelling the vehicle. This process is commonly referred to as regenerative braking. Some hybrid vehicles are configured to use the energy stored in the battery to boost propulsion performance beyond the capabilities of the engine acting alone. However, it is generally preferred to instead operate the vehicle in a manner which simulates the propulsion response of the engine only. This assures the operator will experience a response which is consistent with non-hybrid vehicles.
In order to achieve this engine-only simulated response when using both the electric motor and engine to propel the vehicle, many hybrid vehicles reduce the output of the engine by that of the hybrid motor to match the equivalent engine-only output. This method is typically satisfactory for normally aspirated engines, since the torque produced by the engine at a given rotational engine speed (rpm) is relatively constant over time.
In turbocharged engines, however, the power generated by the engine may change with time due to the effect of the turbocharger. A turbocharger uses engine exhaust gases to drive a turbine wheel. A shaft connects the turbine wheel to a compressor wheel in the air intake path of the engine. Therefore, as the turbine wheel is driven by the flow of exhaust gas, the compressor wheel also spins and compresses the air to the intake of the engine. As the intake air is compressed over time (and increasing amounts of fuel are added), the power generated by the engine also increases. As the engine output increases and more exhaust gases are generated, the turbine and compressor wheels spin faster, thereby increasing the power generated by the engine still further. However, because the turbocharger requires time to overcome the inertia of the compressor wheel and begin to spin, there is a delay in the delivered power response. This effect is commonly referred to as turbo lag and gives the operator a feeling of gradual building of engine power.
The turbocharger effect prevents the simple substitution of electrical power for engine power in a hybrid vehicle where an engine-only equivalent response is desired. This is because as electrical power from the motor replaces engine power, the engine power generation capacity is diminished even further due to the loss of the turbo effect. In other words, if a portion of the engine power is substituted by power generated by the electric motor, the resulting combination output will not match that of the equivalent output if the engine had been acting alone.
Thus, there is a need for improvement in this field.
The system and method described herein addresses the issues mentioned above. In a general sense, the disclosed system monitors the engine output over time to determine a dynamic model of the turbocharger effect. The system then applies the model to determine a propulsion power limit for the combined output of the engine and electric motor which will simulate the response of the engine acting alone.
According to one aspect of the disclosure, a method of operating a hybrid vehicle is disclosed, comprising using a vehicle controller, determining a zero boost power limit of an engine of the hybrid vehicle, said engine including a turbocharger, determining a torque curve power limit of the engine, the torque curve power limit based upon the maximum available power when the turbocharger is operating at a predetermined level, monitoring a current power of the engine and a maximum available power of the engine when the maximum available power is between the zero boost power limit and the torque curve power limit, determining a dynamic response model of the engine based on said monitoring, the model providing an estimation of the engine output power over time as the turbocharger increases in speed, receiving a driver output torque request, and operating the hybrid vehicle such that the collective output power of the engine and an eMachine of the hybrid vehicle is automatically limited to a turbo-equivalent power limit based on said model, said-turbo equivalent power limit representing the power limit of the engine acting alone.
According to another aspect, a hybrid system is disclosed, comprising an engine having a turbocharger, an engine controller operatively coupled to the engine, an eMachine, a hybrid controller operatively coupled to the eMachine and in communication with the engine controller. The hybrid controller is configured to determine a zero boost power limit of the engine, receive torque curve information from the engine controller, determine a torque curve power limit of the engine from the torque curve information, monitor a current power of the engine and a maximum available power of the engine when the maximum available power is between the zero boost power limit and the torque curve power limit, determine a dynamic response model of the engine based on the monitoring, the model providing an estimation of the engine output power over time as the turbocharger increases in speed, receive a driver output torque request from the engine controller, and operate the hybrid vehicle such that the collective output power of the engine and an eMachine of the hybrid vehicle is automatically limited to a turbo-equivalent power limit based on the model, the turbo-equivalent power limit representing the power limit of the engine acting alone.
Further forms, objects, features, aspects, benefits, advantages, and embodiments of the present invention will become apparent from a detailed description and drawings provided herewith.
For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Any alterations and further modifications in the described embodiments and any further applications of the principles of the invention as described herein are contemplated as would normally occur to one skilled in the art to which the invention relates. One embodiment of the invention is shown in great detail, although it will be apparent to those skilled in the relevant art that some features not relevant to the present invention may not be shown for the sake of clarity.
The reference numerals in the following description have been organized to aid the reader in quickly identifying the drawings where various components are first shown. In particular, the drawing in which an element first appears is typically indicated by the left-most digit(s) in the corresponding reference number. For example, an element identified by a “100” series reference numeral will first appear in
The hybrid module 104 is designed to operate as a self-sufficient unit, that is, it is generally able to operate independently of the engine 102 and transmission 106. In particular, its hydraulics, cooling and lubrication do not directly rely upon the engine 102 and the transmission 106. The hybrid module 104 includes a sump 116 that stores and supplies fluids, such as oil, lubricants, or other fluids. To circulate the fluid, the hybrid module 104 includes a mechanical pump 118 and an electrical (or electric) pump 120. With this combination of both the mechanical pump 118 and electrical pump 120, the overall size and, moreover, the overall expense for the pumps is reduced.
The hybrid system 100 further includes a cooling system 122 that is used to cool the fluid supplied to the hybrid module 104 as well as the water-ethylene-glycol (WEG) to various other components of the hybrid system 100 which will be described later in further detail. Looking at
The eMachine 112 in the hybrid module 104, depending on the operational mode, at times acts as a generator and at other times as a motor. When acting as a motor, the eMachine 112 draws alternating current (AC). When acting as a generator, the eMachine 112 creates AC. An inverter 132 converts the AC from the eMachine 112 and supplies it to an energy storage system 134. The eMachine 112 in one example is an HVH410 series electric motor manufactured by Remy International, Inc. of Pendleton, Ind., but it is envisioned that other types of eMachines can be used. In the illustrated example, the energy storage system 134 stores the energy and resupplies it as direct current (DC). When the eMachine 112 in the hybrid module 104 acts as a motor, the inverter 132 converts the DC power to AC, which in turn is supplied to the eMachine 112. The energy storage system 134 in the illustrated example includes three energy storage modules 136 that are connected together, preferably in parallel, to supply high voltage power to the inverter 132. The energy storage modules 136 are, in essence, electrochemical batteries for storing the energy generated by the eMachine 112 and rapidly supplying the energy back to the eMachine 112. The energy storage modules 136, the inverter 132, and the eMachine 112 are operatively coupled together through high voltage wiring as is depicted by the line illustrated in
High voltage wiring connects the energy storage system 134 to a high voltage tap 138. The high voltage tap 138 supplies high voltage to various components attached to the vehicle. A DC-DC converter system 140, which includes one or more DC-DC converter modules 142, converts the high voltage power supplied by the energy storage system 134 to a lower voltage, which in turn is supplied to various systems and accessories 144 that require lower voltages. As illustrated in
The hybrid system 100 incorporates a number of control systems for controlling the operations of the various components. For example, the engine 102 has an engine control module 146 that controls various operational characteristics of the engine 102 such as fuel injection and the like. A transmission/hybrid control module (TCM/HCM) 148 substitutes for a traditional transmission control module and is designed to control both the operation of the transmission 106 as well as the hybrid module 104. The transmission/hybrid control module 148 and the engine control module 146 along with the inverter 132, energy storage system 134, and DC-DC converter system 140 communicate along a communication link as is depicted in
To control and monitor the operation of the hybrid system 100, the hybrid system 100 includes an interface 150. The interface 150 includes a shift selector 152 for selecting whether the vehicle is in drive, neutral, reverse, etc., and an instrument panel 154 that includes various indicators 156 of the operational status of the hybrid system 100, such as check transmission, brake pressure, and air pressure indicators, to name just a few.
In terms of general functionality, the transmission/hybrid control module 148 receives power limits, capacity, available current, voltage, temperature, state of charge, status, and fan speed information from the energy storage system 134 and the various energy storage modules 136 within. The transmission/hybrid control module 148 in turn sends commands for connecting the various energy storage modules 136 so as to supply voltage to and from the inverter 132. The transmission/hybrid control module 148 also receives information about the operation of the electrical pump 120 as well as issues commands to the electrical pump 120. From the inverter 132, the transmission/hybrid control module 148 receives a number of inputs such as the motor/generator torque that is available, the torque limits, the inverter's voltage, current and actual torque speed. Based on that information, the transmission/hybrid control module 148 controls the torque speed and the pump 130 of the cooling system. From the inverter 132, the transmission/hybrid control module 148 also receives a high voltage bus power and consumption information. The transmission/hybrid control module 148 also monitors the input voltage and current as well as the output voltage and current along with the operating status of the individual DC-DC converter modules 142 of the DC-DC converter system 140. The transmission/hybrid control module 148 also communicates with and receives information regarding engine speed, engine torque, engine power, engine power limit, torque curve information, and driver requested output torque, to name a few, from the engine control module 146 and in response controls the torque and speed of the engine 102 via the engine control module 146.
As discussed above, it may be advantageous to simulate an engine-only response during operation, even when operating the vehicle with the assistance of the eMachine 112. In order to better represent such a response, a method for compensating for the turbo-lag effect (e.g., when engine 102 is implemented as a turbocharged engine) will now be discussed.
The response of a turbocharged engine may be modeled as a first order linear system described by the differential equation (1) below:
where u(t) is the input engine power, y(t) is the resulting output power due to the turbocharger, T is a time constant, and k is a gain constant. It shall be understood that equation (1) represents only one possible turbo response model and that any model of turbocharger dynamics known in the art may be used in block 304. Furthermore, the first order linear system of equation (1) can be expressed in discrete time as equation (2) below:
y([n+1]Ts)=αy(n Ts)+k(1−a)u(nTs) (2)
where
and Ts is the discrete sample time, and n is the current iteration. Therefore, y([n+1]Ts) is the output value of the n+1 iteration, y(nTs) is the output value of the n iteration, and u(nTs) is the input value of the n iteration.
The engine control module 146 is continuously broadcasting the current power, power limit, torque curve, and the driver requested output torque to the transmission/hybrid control module 148. The engine control module 146 determines these values based on data received from various sensors within the system 100 and other stored data. For example, the current engine power may be determined by the actual engine torque (based on known fueling rate to torque relationships for the engine) multiplied by the current engine shaft speed received from a speed sensor on the engine output shaft. The engine power limit is the current power that the engine could supply if requested. The torque curve is a data table which equates various engine speeds to the amount of torque that could be supplied by the engine at those speeds if the turbo was already spun up to a given speed. The driver requested output torque is determined by the engine control module 146 based on the position of an accelerator pedal or other driver input device. It shall be understood that the values being received and calculated by the engine control module 146 may also be received and calculated directly by the transmission/hybrid control module 148. The engine control module 146 and the transmission/hybrid control module 148 may be implemented as separate units or integrated into a single controller or housing.
If the input u(nTs) of equation (1) is taken to be the current engine power and the output y(nTs) is taken to be the engine power limit, then as long as the engine is operating between an identified zero boost power limit and the torque curve limit, the constants k and a can be identified. In other words, since the input and output of the equation (1) are being broadcast by the engine and are therefore known, the remaining unknown k and a constants can be determined. The process for determining the k and a constants based on the known input and output may be implemented using adaptive infinite impulse response (IIR) filtering, such as the Steiglitz-McBride algorithm, although other methods known in the art may also be used. The determination of the constants k and a may be run continuously in order to constantly improve the accuracy of the turbo response model over time. To determine the zero boost power limit, the power limit broadcast by the engine control module 146 may be monitored while the engine is operating at low power, such as during an idle condition.
The identified constants k and a can be used to determine an overall turbo-equivalent power limit. The turbo-equivalent power limit is the limit that will be imposed on the combined output power of the engine 102 and eMachine 112 when both the engine 102 and eMachine 112 are contributing to the power being fed to the transmission 106. In this way, response of the vehicle perceived by the vehicle will simulate that of the turbocharged engine acting alone.
At stage 306, the transmission/hybrid control module 148 determines the torque curve power limit. As discussed above, the transmission/hybrid control module 148 receives the torque curve data (available torques at various speeds) from the engine control module 146. Alternatively, the torque curve data may be stored in memory of the transmission/hybrid control module 148. To determine the torque curve power limit, the transmission/hybrid control module 148 retrieves the maximum torque available at the current engine speed from the torque curve data, and multiplies the result by the current engine speed.
Continuing to stage, 308, the transmission/hybrid control module 148 monitors the values for current engine power, and current maximum available engine power being broadcast by the engine control module 146. As discussed above, at times when the current maximum available engine power is between the zero boost power limit (from stage 304) and the torque curve power limit (from stage 306), the observed data is used to determine the constants k and a of the turbocharger response equation (2). The stages 304, 306, and 308 above may be run continuously and independent of the remaining stages to adaptively identify and update the values being determined.
At stage 310, the transmission/hybrid control module 148 determines the current engine power being output by the engine 102. The transmission/hybrid control module 148 receives the actual engine torque and the current engine speed from the engine control module 146, and multiplies these values to determine the current engine power.
At stage 312, the transmission/hybrid control module 148 determines the current eMachine 112 output power being delivered to the transmission 106. To determine this, the transmission/hybrid control module 148 multiplies the eMachine 112 motor torque (which is known by the transmission/hybrid control module 148) by the eMachine 112 speed (received from a speed sensor on a shaft of the eMachine 112).
At stage 314, the transmission/hybrid control module 148 determines a total propulsion power being delivered to the transmission 106 by adding the current engine power from stage 310 to the current eMachine 112 power from stage 312.
At stage 316, along with the known constants k and a, the total propulsion power is applied as input u(nTs) to equation (2). This gives the resulting turbo equivalent power limit, y([n+1]Ts), for the propulsion power of the combination of engine 102 and eMachine 112.
At stage 318, the transmission/hybrid control module 148 compares the turbo-equivalent power limit from stage 314 to the zero boost power limit from stage 304. If the turbo-equivalent power limit is less than the zero boost power limit, then the turbo-equivalent power limit is set to the zero boost power limit. If not, the turbo-equivalent power limit remains unchanged.
At stage 320, the transmission/hybrid control module 148 compares the turbo-equivalent power limit from stage 318 to the torque curve power limit from stage 306. If the torque curve power limit is less than the turbo-equivalent power limit, then the turbo-equivalent power limit is set to the torque curve power limit. If not, the turbo-equivalent power limit remains unchanged. At this point, the turbo-equivalent power limit is characterized as a total propulsion power limit. The stages 310-320 above may also be run continuously and independent of the other stages to adaptively identify and update the values being determined, including total propulsion power limit.
At stage 322, the transmission/hybrid control module 148 determines the driver requested output power. In one embodiment, the transmission/hybrid control module 148 receives the driver requested torque (based on acceleration pedal displacement) and current engine speed from the engine control module 146, and multiplies the values to determine the driver requested output power.
At stage 324, the transmission/hybrid control module 148 compares the driver requested power to the total propulsion power limit from stage 320 and determines a transmission input power request value. If the driver requested output power is less than the total propulsion power limit, then the input power request value will be set to a value equal to the driver requested power. However, if the driver request power is more than the total propulsion power limit, then the transmission input power request will be set to a value equal to the total propulsion power limit.
At stage 326, the transmission/hybrid control module 148 determines the amount of power to be supplied by each of the engine 102 and the eMachine 112 in order to collectively provide a total amount of input power to the transmission which is equal to the transmission input power request value from stage 324. Any combination of power levels of the engine 102 and eMachine 112 may be used as long as the total combined power is equal to the transmission input power request. This ensures that the response felt by the driver is limited to that of the turbocharged engine acting alone
It shall be understood that the process of the
While the invention has been illustrated and described in detail in the drawings and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only the preferred embodiment has been shown and described and that all changes, equivalents, and modifications that come within the spirit of the inventions defined by following claims are desired to be protected. All publications, patents, and patent applications cited in this specification are herein incorporated by reference as if each individual publication, patent, or patent application were specifically and individually indicated to be incorporated by reference and set forth in its entirety herein.
This application is a continuation of U.S. Pat. No. 15,657,875 filed Jul. 24, 2017, which is a continuation of U.S. application Ser. No. 14/838,403 filed Aug. 28, 2015, which is a continuation of International Application No. PCT/US2014/020417 filed Mar. 4, 2014, which claims the benefit of U.S. Provisional Application No. 61/782,962 filed Mar. 14, 2013, which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4901530 | Kawamura | Feb 1990 | A |
5881559 | Kawamura | Mar 1999 | A |
6441588 | Yagi et al. | Aug 2002 | B1 |
6469403 | Omata et al. | Oct 2002 | B2 |
6518732 | Palanisamy | Feb 2003 | B2 |
6686724 | Coates et al. | Feb 2004 | B2 |
6727676 | Ochiai | Apr 2004 | B2 |
6904342 | Hanada et al. | Jun 2005 | B2 |
7009401 | Kinoshita et al. | Mar 2006 | B2 |
7015676 | Kohama et al. | Mar 2006 | B2 |
7017348 | Tajima et al. | Mar 2006 | B2 |
7021409 | Tamor | Apr 2006 | B2 |
7078877 | Salasoo et al. | Jul 2006 | B2 |
7131708 | Tao et al. | Nov 2006 | B2 |
7295902 | Chen et al. | Nov 2007 | B2 |
7305873 | Hubbard et al. | Dec 2007 | B2 |
7314043 | Berger et al. | Jan 2008 | B1 |
7407026 | Tamor | Aug 2008 | B2 |
7449891 | Cawthorne | Nov 2008 | B2 |
7479761 | Okumura | Jan 2009 | B2 |
7482767 | Tether | Jan 2009 | B2 |
7486036 | Oyobe et al. | Feb 2009 | B2 |
7521935 | Uchida | Apr 2009 | B2 |
7538520 | Zettel et al. | May 2009 | B2 |
7550946 | Zettel et al. | Jun 2009 | B2 |
7639018 | Zettel et al. | Dec 2009 | B2 |
7640744 | Rollinger et al. | Jan 2010 | B2 |
7645209 | Dreibholz et al. | Jan 2010 | B2 |
7657350 | Moran | Feb 2010 | B2 |
7661370 | Pike et al. | Feb 2010 | B2 |
7677341 | Tomo | Mar 2010 | B2 |
7719238 | Iida et al. | May 2010 | B2 |
7730984 | Heap et al. | Jun 2010 | B2 |
7768235 | Tae et al. | Aug 2010 | B2 |
7770676 | Tenbrock et al. | Aug 2010 | B2 |
7770678 | Nozaki et al. | Aug 2010 | B2 |
7784575 | Yamanaka et al. | Aug 2010 | B2 |
7795844 | Ichikawa et al. | Sep 2010 | B2 |
7800345 | Yun et al. | Sep 2010 | B2 |
7828693 | Soliman et al. | Nov 2010 | B2 |
7836985 | Itoh | Nov 2010 | B2 |
7863789 | Zepp et al. | Jan 2011 | B2 |
7865287 | Huseman | Jan 2011 | B2 |
7877996 | Berger et al. | Feb 2011 | B2 |
7878282 | Kumazaki et al. | Feb 2011 | B2 |
7893637 | Suhama et al. | Feb 2011 | B2 |
7908064 | Cawthorne et al. | Mar 2011 | B2 |
7923950 | Takahashi | Apr 2011 | B2 |
7928699 | Kohn | Apr 2011 | B2 |
7935015 | Tabata et al. | May 2011 | B2 |
7967091 | Yamazaki et al. | Jun 2011 | B2 |
7977896 | Heap et al. | Jul 2011 | B2 |
7987934 | Huseman | Aug 2011 | B2 |
7998023 | Holmes et al. | Aug 2011 | B2 |
8000866 | Heap et al. | Aug 2011 | B2 |
8002667 | Hsieh et al. | Aug 2011 | B2 |
8010247 | Heap et al. | Aug 2011 | B2 |
8020652 | Bryan et al. | Sep 2011 | B2 |
8022674 | Miura | Sep 2011 | B2 |
8029408 | Seel | Oct 2011 | B2 |
8030883 | Katayama | Oct 2011 | B2 |
8035324 | Heap | Oct 2011 | B2 |
8035349 | Lubawy | Oct 2011 | B2 |
8047959 | Fuechtner et al. | Nov 2011 | B2 |
8053921 | Ichikawa | Nov 2011 | B2 |
8063609 | Salasoo et al. | Nov 2011 | B2 |
8078417 | Ishishita | Dec 2011 | B2 |
8082743 | Hermann et al. | Dec 2011 | B2 |
8091667 | Zettel et al. | Jan 2012 | B2 |
8098050 | Takahashi | Jan 2012 | B2 |
8136615 | Pels et al. | Mar 2012 | B2 |
8250864 | Pott et al. | Aug 2012 | B2 |
20030160455 | Hu | Aug 2003 | A1 |
20040168840 | Kuang et al. | Sep 2004 | A1 |
20040235614 | Tajima et al. | Nov 2004 | A1 |
20070090803 | Yun et al. | Apr 2007 | A1 |
20070125083 | Rollinger et al. | Jun 2007 | A1 |
20080087482 | Ledger et al. | Apr 2008 | A1 |
20080224478 | Tamor | Sep 2008 | A1 |
20090037060 | Carlhammar et al. | Feb 2009 | A1 |
20090118929 | Heap et al. | May 2009 | A1 |
20090118941 | Heap | May 2009 | A1 |
20090118964 | Snyder et al. | May 2009 | A1 |
20090118971 | Heap et al. | May 2009 | A1 |
20090204280 | Simon, Jr. et al. | Aug 2009 | A1 |
20090308674 | Bhattarai et al. | Dec 2009 | A1 |
20100116235 | Imamura et al. | May 2010 | A1 |
20100125019 | Tabata et al. | May 2010 | A1 |
20100250037 | Yoshida et al. | Sep 2010 | A1 |
20100262308 | Anderson et al. | Oct 2010 | A1 |
20100263952 | Richter et al. | Oct 2010 | A1 |
20100299036 | Vespasien | Nov 2010 | A1 |
20100312422 | Imaseki | Dec 2010 | A1 |
20110040433 | Steuernagel | Feb 2011 | A1 |
20110048823 | Connolly et al. | Mar 2011 | A1 |
20110130904 | McGrogan et al. | Jun 2011 | A1 |
20110301791 | Swales et al. | Dec 2011 | A1 |
20110320075 | Kim et al. | Dec 2011 | A1 |
20120119509 | West | May 2012 | A1 |
20120179317 | Kuberczyk | Jul 2012 | A1 |
20120208672 | Sujan et al. | Aug 2012 | A1 |
20120329603 | Yamazaki et al. | Dec 2012 | A1 |
Number | Date | Country |
---|---|---|
102257296 | Nov 2011 | CN |
102869905 | Jan 2013 | CN |
10 2008 001128 | Oct 2009 | DE |
10 2008 054802 | Jun 2010 | DE |
2000-175305 | Jun 2000 | JP |
WO 2008034661 | Mar 2008 | WO |
WO 2010079275 | Jul 2010 | WO |
WO 2011134704 | Nov 2011 | WO |
Entry |
---|
International Search Report and Written Opinion issued in PCT/US2014/020417, dated Jun. 19, 2014, 15 pgs. |
Number | Date | Country | |
---|---|---|---|
20200114899 A1 | Apr 2020 | US |
Number | Date | Country | |
---|---|---|---|
61782962 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15657875 | Jul 2017 | US |
Child | 16708564 | US | |
Parent | 14838403 | Aug 2015 | US |
Child | 15657875 | US | |
Parent | PCT/US2014/020417 | Mar 2014 | US |
Child | 14838403 | US |