Systems and methods for implementing dynamic operating modes and control strategies for hybrid vehicles
Through the control strategy of the dual-motor-dual-clutch power system, dynamically switching the working mode of the hybrid vehicle is solved, and the fuel efficiency and battery life problems in the existing technology are achieved, and efficient fuel use and battery management are achieved.
Patent Information
- Application Number
- CN202110539715.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2013-02-08
- Filing Date
- 2014-02-07
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2034-02-07
AI Technical Summary
Existing hybrid vehicles are difficult to achieve dynamic switching of multiple control strategies and working modes under different driving conditions and strategies, resulting in poor fuel efficiency and battery life.
采用双电机-双离合动力系统,通过控制器根据车辆的速度、电池充电状态和其他信号动态切换全电动模式、原动机模式和混合动力模式,优化电能使用和发动机的工作曲线。
It achieves efficient fuel use and extended battery life under different driving conditions, and improves the fuel economy and electric mileage of the vehicle.
Smart Images

Figure CN113370963B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with the application date of February 7, 2014, the national application number of 201810142940.2, and the invention name of "System and method for implementing dynamic working mode and control strategy for hybrid vehicles". And the invention patent application with the application date of February 7, 2014, the application number of 201810142940.2, and the invention name of "System and method for implementing dynamic working mode and control strategy for hybrid vehicles" is a divisional application of the invention patent application with the national application number of 201410044794.1 and the invention name of "System and method for implementing dynamic working mode and control strategy for hybrid vehicles". Technical Field
[0002] The present application relates to hybrid vehicles, and more particularly to systems and methods for implementing dynamic operating modes and control strategies used in hybrid vehicles. Background Art
[0003] In the field of electric vehicles (EV), hybrid electric vehicles (HEV) and plug-in hybrid electric vehicles (PHEV), there are many feasible powertrain (or powertrain) structures that can achieve multiple operating modes. For example, in the field of HEV alone, the HEV powertrain can be configured to achieve series, parallel, series-parallel and all-electric operating modes. In addition, some of these modes can be configured to operate according to different strategies such as power conservation, power consumption, etc.
[0004] These different modes and strategies provide advantages such as range extension, fuel efficiency, operation of the internal combustion engine (ICE) on its ideal operating line (IOL), and all-electric operation. It is desirable to have a single powertrain system that can implement the above-mentioned multiple control strategies and operating modes, for example, during different possible driving conditions and under different strategies that may be adopted, depending on the desired driving characteristics such as fuel efficiency, range extension, maximum range of electric energy, efficient battery usage, etc. Summary of the invention
[0005] A brief summary of the invention is given below for the purpose of providing a basic understanding of some of the applications described herein. This summary is not an exhaustive review of the claimed subject matter. This summary is neither intended to identify the key or decisive elements of the claimed subject matter nor to limit the scope of protection of the subject invention. The sole purpose of this summary is to present some of the concepts in the claimed subject matter in a simplified form as a preface to the more detailed description that will be given later.
[0006] Systems and / or methods for controlling a dual motor-dual clutch powertrain for HEVs and PHEVs are disclosed. In one embodiment, a method is disclosed, comprising: determining a state of charge (SOC) of the battery; determining a speed of a vehicle; if the SOC is greater than a specified first threshold, selecting a charge depleting operating mode of the vehicle; and during operation of the vehicle, if the SOC is less than a specified second threshold, selecting a charge preserving operating mode of the vehicle. In another embodiment, a system is disclosed, the system having a controller that operates the powertrain according to various embodiments.
[0007] Other features and applications of the present system presented in the following detailed description may be understood in conjunction with the drawings provided in this application. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Exemplary embodiments are shown with reference to the accompanying drawings. It should be understood that the embodiments and drawings disclosed herein are to be regarded as illustrative rather than restrictive.
[0009] Figure 1 A possible embodiment of a hybrid vehicle or a plug-in hybrid vehicle implemented according to the principle of the present application is shown.
[0010] Figure 2 One possible embodiment of a powertrain architecture in a HEV or PHEV vehicle implemented according to the principles of the present application is shown.
[0011] Figures 3A to 3C Shown by Figure 2 The powertrain architecture in Figure 1 implements the outline flow of different operating modes.
[0012] Figure 4A Shown as Figure 2 A possible set of operating envelopes and efficiency islands for motor-generators in a powertrain of the illustrated architecture.
[0013] Figure 4B Shows the use of Figure 4A One possible embodiment of a control flow diagram of the information shown.
[0014] Figure 5A and 5B It is shown that, for example, Figure 2 Two possible embodiments of mode control and / or operation for HEV and / or PHEV vehicles of the illustrated architecture.
[0015] Figure 6 For example, Figure 2 One possible embodiment of a control flow diagram for a HEV and / or PHEV vehicle of the illustrated architecture.
[0016] Figure 7 and Figure 8 Dynamic operation diagrams for switching between various modes are shown for a HEV and / or PHEV vehicle implemented according to the principles of the present application.
[0017] Fig. 9 is a possible embodiment of a state diagram for a mode transition flow chart.
[0018] Figures 10 to 12 Various embodiments of advanced control operations designed to improve battery performance and life are shown. DETAILED DESCRIPTION
[0019] As used herein, the terms "component", "system", "interface", etc. are intended to refer to computer-related entities such as hardware, (e.g., running) software, and / or firmware. For example, a component can be a process running on a processor, a processor, an object, an executable program, and / or a computer. For example, an application running on a server and the server can both be components. One or more components can reside within a process and a component can be centralized on one computer and / or distributed between two or more computers.
[0020] The claimed subject matter is described with reference to the accompanying drawings, wherein like reference numerals are used throughout to denote like elements. In the following description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the subject invention. However, it should be apparent that the claimed subject matter can be implemented without these specific details. In other cases, well-known structures and devices are shown in block diagram form for ease of description of the subject invention.
[0021] Preface
[0022] In one embodiment, control algorithms are provided for managing dynamic operating modes and / or control strategies used by hybrid electric vehicles (HEVs), which can be applied to both plug-in HEVs and non-plug-in HEVs. In addition, these control algorithms can allow for efficient, cost-effective and responsive operation of batteries and motors. In other embodiments, the prime mover (PM) can also be minimized to achieve a high degree of power mixing. Suitable PMs can include: ICE, fuel cell or any other combustion, chemical and / or fuel-based (e.g., known liquid or gaseous fuel) prime movers.
[0023] By "high degree of hybrid power" is meant that the vehicle (e.g., HEV, PHEV, etc.) and / or the powertrain can be designed to use as much of the electrical energy stored in the battery as possible during the driving cycle to provide motive power for the vehicle. The electrical energy stored in the battery can be obtained from a variety of sources: regenerative braking, charging operation of the PM, or from a wall socket or other external charging. In other embodiments, electrical power (e.g., from on-board and off-board sources and obtained through one or more motors and / or batteries) can be managed by multiple controllers connected together in various ways so that proper management of the battery can be provided to improve driving range, life, and performance.
[0024] It is known that in many cases the battery life in an electric or hybrid vehicle may be less than 1 / 4 of its expected life. In some embodiments, a hybrid vehicle (HEV, PHEV, etc.) manages how the vehicle is used and / or driven to obtain a desired driving range and life with a specific set of batteries. Therefore, in some embodiments, it is desirable to use a software controller to coordinate the control of the engine, transmission, and battery pack to achieve the desired fuel economy or fuel consumption and possibly also achieve the desired electric driving range and battery life.
[0025] It should be appreciated that the control software used by the vehicle may run on one controller (and that controller send signals to the various components of the powertrain), or alternatively the control software may be distributed among multiple controllers in any known manner, wherein a subset of the multiple controllers may communicate with a subset of the multiple controllers. Thus, any reference to the term "controller" may also encompass embodiments including multiple controllers and distributed control software.
[0026] One embodiment of a vehicle / power system
[0027] Figure 1 It is one vehicle and / or power system feasible platform (100) among various vehicle and / or power system feasible embodiments in which the technology of the present invention can be applied.
[0028] Vehicle 100 (eg Figure 1 1) includes a dual clutch-dual motor HEV / PHEV powertrain that can dynamically operate as a full electric vehicle, a hybrid vehicle, or a plug-in hybrid vehicle at different times during a driving cycle through control operations. The engine (or any suitable PM) 102 is arranged on a common drive shaft 112 equipped with two motors 106 and 110. The clutch 104 is located between the engine 102 and the motor 106 and the clutch 108 is located between the motor 106 and the motor 110. As will be described in further detail below, the clutches 104 and 108 can be actuated to achieve different operating modes of the vehicle 100.
[0029] The battery 114 uses the charge to power the motors 106 and 110. The battery 114 may draw power through onboard charging (e.g., using the engine 102 and the motor 106), regenerative braking (e.g., using the motor 110 alone or in combination with the motor 106), or through an optional wall charger 116. The wall charger 116 may draw power from a wall outlet and the charger 116 may be designed according to local standards for grid power distribution.
[0030] The drive shaft 112 delivers mechanical power to and from the final drive 120, which then delivers the power to wheels 122A and 122B, which are rear wheels in this embodiment. The final drive 120 may include a differential that may be optionally combined with an additional transmission device such as a manual transmission, an automatic transmission, a mechanical or electronic continuously variable transmission (CVT), or a power distribution device (PSD) such as used in a Toyota Prius. In addition, it should be appreciated that front-wheel drive or all-wheel drive embodiments are also feasible embodiments and are also within the scope of protection of the present application. Other feasible embodiments may include: (1) a front-engine / dual-motor front-wheel drive structure; (2) a front-engine / single-motor or dual-motor / variable transmission (e.g., CVT, automatic transmission, manual transmission, electronic transmission, planetary gear transmission, etc.) structure; and (3) a front-engine / single-motor transmission and a rear-motor transmission structure. Several such embodiments are disclosed in commonly owned patent application Ser. No. 13 / 762,860, entitled “POWERTRAIN CONFIGURATIONS FOR TWO-MOTOR, TWO-CLUTCH HYBRID ELECTRIC VEHICLES,” filed on the same date as the present application (and incorporated herein by reference).
[0031] In one embodiment, motor 110 may have a higher torque and / or power rating than motor 106. The power ratings of both motors may be adjusted for the vehicle application; however, in one embodiment, motor 106 may be 1 / 2 the power and torque of motor 110 and PM may be approximately the power of motor 106. In another embodiment, where all-electric mode may have higher performance than ICE operation, the ICE and motor 106 may be much smaller than motor 110. Such a vehicle may be used in certain situations where limited charging infrastructure is required to provide electrical energy for all-electric operation and other possible situations.
[0032] In another embodiment, both motors 106 and 110 may be reduced in size for cost / weight reduction. In such an embodiment, it may be necessary to operate both motors 106 and 110 by closing clutch 108 more frequently so that sufficient torque is available and / or at a desired level (e.g., a 30% level) when the vehicle is launched. Such motor sizes may be specifically designed based on the size, weight, and / or intended function of the intended vehicle (e.g., passenger vehicle, light truck, freight vehicle, etc.). In some embodiments, motor 110 comprises a high torque motor and motor 106 comprises a low torque motor.
[0033] Figure 2 Shown according to Figure 1 An embodiment of a possible control system 200 for a vehicle and / or powertrain system based on the principles and / or designs of the present invention. The controller 202 may include a suitable combination of hardware, firmware and / or software for inputting various system signals and outputting various control signals to achieve the desired operation of the vehicle 100. Signals may be input into the controller 202 from sensors and / or actuators via a CAN bus architecture known in the art. Possible signal inputs to the controller 202 may include: vehicle speed, drive shaft speed, crankshaft speed, battery state of charge (SOC), driver demands through actuation of the accelerator pedal and the brake pedal, clutch slip, and other possible signals related to vehicle operation in a variety of different possible situations.
[0034] Other signals for the controller 202 may also include the following:
[0035] (1) External charger information, i.e., Level 1, Level 2, and other characteristics such as charging time, grid-to-vehicle, vehicle-to-grid, charging history, etc.
[0036] (2) Battery management system information, such as state of charge (SOC), temperature of battery pack and individual cells, state of health (SOH), SOC and temperature history, instantaneous power capacity, fault codes, contactor status, battery voltage and current, etc.
[0037] (3) Engine controller data, such as SOH, fuel usage, speed, throttle, temperature, torque, etc.
[0038] (4) Clutch 1 data, such as on / off, clutch position, engine start / series operation, temperature, etc.
[0039] (5) Data of the motor 1 (M1), such as motoring or generating, on / off, speed, torque, temperature, voltage, current, etc.
[0040] (6) Clutch 2 data, such as on / off, position, pressure, M1+M2 electric, engine+M1+M2 parallel, engine+M1 and M2 series operation, temperature, etc.
[0041] (7) Driven by M2 motor, including data such as on / off, speed, torque, temperature, voltage, current, single motor drive, dual motor drive, series operation, parallel operation temperature, etc.
[0042] Other system signals and / or control signals may be coupled to the controller 202 via various interfaces and / or subsystem controllers such as the engine controller 102a, the clutch actuators 104a and 108a, the motor controllers 106a and 110a, and the battery management system 114a. It should be appreciated that the controller 202 may receive other signals and send control signals from other sensors and / or actuators.
[0043] Working Mode Example
[0044] For similar Figure 1 and Figure 2 The vehicle / powertrain design has multiple possible operating modes for HEV and PHEV vehicles, including:
[0045] (1) All-Electric Mode (AEM): In this mode, energy can be provided by the battery without concern for where the energy comes from (e.g., on-board or off-board). This mode can implement a "charge-depleting" strategy, whereby it may be desirable to provide as much "all-electric" range as possible before starting PM (e.g., based on some suitable metric or state). AEM can be implemented by operating one or two motors (e.g., using energy from the battery pack).
[0046] (2) Prime Mover Mode 1 (PMM1): In this mode, the vehicle can be powered primarily by the PM and the battery power can be used to improve performance. This mode can implement a "charge retention" strategy, whereby power can then be returned to the battery via the PM to provide a solid foundation for the battery's SOC. This mode can also be used to achieve a temporary maximum speed, where the PM power is added to the motor. Sustained maximum speed can be achieved using only the PM.
[0047] (3) Prime Mover Mode 2 (PMM2): In this mode, the motor 110 provides substantially all of the motive power and the motor 106 provides electrical energy to drive the vehicle through the motor 110 and maintain the battery within the desired SOC range. This mode can also implement a “charge retention” strategy.
[0048] Although there are a number of possible intermediate modes that can be implemented on the vehicle 100, FIG. 3A to FIG. 3COnly the three modes enumerated above are shown. Figure 3A The AEM mode is shown. In this mode, electrical energy can be delivered from the battery 114 to one or all of the motors 110 and / or 106 under the control signal sent by the controller 202. The clutch 108 can be opened or closed as needed. The dashed line 302 shows the drive to the wheels by the motor 110 (or in some cases by the motor 110 and the motor 106, where the clutch 108 is engaged as needed) and possible regenerative braking. In the AEM mode, the clutch 104 can be disengaged, so the engine 102 can remain in the deactivated (OFF) state. Depending on the desired state (such as the driver's power and / or torque demand), the motor 106 can be in an enabled (ON) or disabled (OFF) state, where the clutch 108 is appropriately engaged or disengaged (as shown by the dashed line 303).
[0049] Figure 3B PMM1 mode is shown. In this mode, clutches 104 and 108 are both engaged and engine 102 can be placed in an enabled (ON) state and provide drive power to the wheels. Motor 106 and / or motor 110 can be in an enabled (ON) or disabled (OFF) state depending on the power and / or torque required by the driver, the SOC of the battery, or any other desired state monitored and / or controlled by controller 202.
[0050] Figure 3C PMM2 mode is shown. In this mode, clutch 104 can be engaged and clutch 108 can be disengaged. When clutch 104 is engaged, engine 102 can be in an enabled state and drive motor 106 as a generator to provide power to the battery (as shown by dashed line 310). In addition, motor 110 can be in an enabled state and provide drive power to the wheels according to the desired state generated by the controller.
[0051] In another embodiment, motor 106 may be driven by engine 102 and provide electrical energy directly to motor 110 when clutch 108 is open (as shown by dashed line 313). This may be desirable when it is not possible or necessary to convert electrical energy from motor 106 to chemical energy within a battery.
[0052] During PMM2, the engine torque and speed can be designed to operate on the ideal operating curve (IOL) or not at all during operation. The controller 202 (or any other suitable controller) can determine which mode to operate in and when to switch to another mode based on a set of desired conditions. In one embodiment, the PMM2 mode can operate at any vehicle speed from zero to the maximum AEM speed. The AEM mode can be used in a range from zero speed to a minimum threshold according to the desired control rules. The maximum speed in AEM may not be as high as PMM1. In one embodiment, PMM1 can operate above a certain threshold speed and is used for highway driving and obtaining optimal fuel efficiency.
[0053] The accelerator pedal (gas pedal) for HEV or PHEV needs to control the torque or power of the vehicle according to the vehicle speed and the motor characteristics. The driver's desired torque (T) and / or desired power (P) can be determined by the characteristics of the motor and the PM. Specifically, the angular speed (corner speed) at which the constant torque characteristic curve intersects the constant power characteristic curve is the curve that defines the motor and can be added to the torque-speed characteristic curve of the PM.
[0054] Examples of AEM patterns
[0055] As described above, the AEM mode is intended for low speed, zero emission operation, where substantially all of the drive power is derived from electrical power. For PHEV embodiments, this electrical power may be obtained from outside the vehicle (e.g., from a public or private power grid) or from an onboard generator, such as one that derives power from a liquid fuel. It may be desirable to use off-board electrical power because it may be more efficient and provide electrical power with zero vehicle emissions. The AEM mode may be used in Figure 1 This is achieved in the configuration by using only motor 110 or by closing clutch 108 and using motors 106 and 110 with clutch 104 in an open state. When only motor 110 is used, clutch 108 can be open or closed because motor 106 can be controlled to provide zero torque or zero power at any speed.
[0056] In AEM mode, in embodiments where the final drive 120 includes a differential (but not necessarily another variable ratio transmission, such as an automatic transmission, CVT, etc.), both motors 106 and 110 may be used for operation. At certain points in a given driving cycle, only motor 110 may provide drive power to the vehicle 100, particularly at low speeds, and up to the specified efficiency of motor 110. However, if the driver requires more power and / or torque, or if driving conditions so require, then motor 106 may provide drive power simultaneously with motor 110. In this case, it may be desirable for controller 202 to operate motor 106 and motor 110 to work together with better efficiency than using either motor alone.
[0057] In one embodiment, it may be desirable to have one or both motors running substantially on their respective IOLs while the vehicle is in motion. In the absence of a variable ratio gearbox, then a single motor may be used to control the vehicle in torque mode. If there are two motors in parallel, then an embodiment may prefer that a particular torque request be made to the motor that has the best efficiency at that moment in time. Since the two motors are on the same or parallel shafts, this switching can be performed substantially immediately or with a slight delay by electronic control.
[0058] In the case of starting from zero speed, the vehicle 100 can be started in AEM mode, or if the engine 102 is running, the controller 202 can increase the torque of the engine by slipping the clutch while controlling the engine speed. The controller 202 can select the initial acceleration torque according to the driver's request through the accelerator pedal. For a low accelerator pedal starting point, the motor 106 can be used, especially if the motor 106 is designed to have a lower torque and / or power specification than the motor 110. In this case, the clutch 108 should be closed. Thus, the vehicle can be started by the motor 106 or the motor 110 or the motor 106 plus the motor 110 (for example, in a high torque / high traction electric mode). Such a high torque / high traction electric mode can also be used when the vehicle is at a certain non-zero speed and the driver issues a command requiring additional power and / or torque as needed.
[0059] Figure 4A One possible mapping 400 of torque-speed characteristics for a small electric machine (shown as dashed line 406) and a large electric machine (shown as solid line 408) is shown. Additionally, their corresponding envelope curves for an exemplary vehicle are shown as envelope curves 404 and 402, respectively.
[0060] Using this mapping, the relative efficiency of the vehicle can be determined by the instantaneous power required and the instantaneous power provided by motor 1 (106) and motor 2 (110). Figure 4A In the example above, if the torque or power requirement is as indicated by point 410, then using motor 1 or 2 can achieve substantially the same efficiency. Therefore, either motor can be used at this point. However, if the operating point 410 at that time indicates that the torque and / or power is higher, then motor 2 (110) should be used preferentially. If the torque at point 410 is lower, then motor 1 (106) should be used preferentially. The difference can become more significant as the power or torque required becomes lower.
[0061] This can also be seen in Figure 4A As further shown in . Assuming point A is the desired operating point requested by the accelerator pedal, if the accelerator pedal is further depressed to request torque and power at point B, then motor 1 can be used because motor 1 performs more efficiently at this point. If the accelerator pedal is further depressed to power point C, then motor 2 can be used, at which time motor 1 is set to zero torque because this configuration performs more efficiently at this point. It should be appreciated that at certain operating points, for better efficiency, it may be more efficient to use a combination of drive power from motor 1 (M1) and motor 2 (M2), such as (a*M1)+(b*M2), where a and b are determined by the corresponding efficiencies of M1 and M2. Finally, if the accelerator pedal is retracted to the power represented by point D on the motor diagram, then only motor M1 is used because it performs more efficiently.
[0062] Should be aware of Figure 4A The motor efficiency information shown can be determined through motor specifications, testing, etc. This information can be provided to the controller in various forms - such as into a lookup table (LUT) or can be determined through modeling and calculation. In any embodiment, the motor efficiency data can be provided to the controller to make such switching decisions based on any performance metric required.
[0063] In embodiments where the final drive comprises a variable ratio transmission (e.g., a mechanical CVT, an electronic CVT, an automatic transmission, a manual transmission, a planetary gear set, etc.), the motor 110 can be controlled by the controller 202 (or any other suitable controller within the system) to operate on its IOL at substantially all points in its operation. In such a vehicle having a variable ratio transmission, the vehicle can be controlled as described in U.S. Patents (1) 5,842,534, (2) 6,054,844, (3) 6,116,363, (4) 6,809,429, (5) 6,847,189, (6) 6,931,850, (7) 7,217,205, (8) 7,261,672, (9) 7,713,166, all of which are hereby incorporated by reference in their entirety.
[0064] Figure 4B Given the operation for example Figure 2 A possible embodiment of the control algorithm / flow chart of a dual-motor drive vehicle is shown. It should be appreciated that this control algorithm can be applied to pure electric vehicles equipped with at least two motors, that is, without an ICE / gas engine.
[0065] The control algorithm 450 may begin at 452 by determining the maximum torque limits of M1 and M2 and possibly the performance envelope and efficiency island. This information may be Figure 4A The encoding mapped in and stored in a directory that can be set, for example Figure 2 As previously mentioned, each of these controllers has accessible electronic memory and this information can be stored in a variety of formats, including look-up tables (LUTs) or by modeling and calculating the encoding of the motor performance envelope curve and / or efficiency island.
[0066] The control algorithm can also adjust this information based on inputs from various sensors such as current motor speed, temperature readings at different locations (such as ambient air temperature, operating temperature of M1, M2, engine, battery or other locations related to motor / vehicle efficiency), voltage, current, etc.
[0067] At 454, the control algorithm may receive a torque request from the driver from any source such as an accelerator pedal, brake pedal, other torque requests from electronic sources, etc. These torque request signals are input into the processing module 454 and the module may determine the space of allowable torque combinations / configurations of M1 and M2 that can satisfy the given torque request.
[0068] Module 456 can then find the best torque combination of M1 and M2 that has the highest efficiency (or satisfies some other desired metric for vehicle operation). This can be done by traversing the space of allowable combinations and performing some minimum / maximum calculation, such as traversing Figure 4A Once the best combination of M1 and M2 to meet the torque requirements is determined, the torque demand signals for M1 and M2 can be sent to the relevant controllers to achieve these corresponding torque requirements.
[0069] PMM parallel mode implementation
[0070] In PMM parallel operation (such as Figure 3BAs shown), clutch 104 and clutch 108 are all closed, and the engine and two motors can all be directly connected to the final reducer and wheels. In one embodiment, the engine 102 can be controlled on its IOL by the controller 202, just as described above in the PMM series mode.
[0071] To maintain the battery, the motor / generator 106 can be used to add the required incremental power in the next time increment, such as 60 seconds, to maintain the SOC of the battery, while the motor 110 can be used to supplement the power of the engine 102 to provide acceleration and power. In one embodiment, since the engine 102 can be directly connected to the final reducer gear set that drives the wheels, it may not be desirable to implement the PMM parallel mode before reaching a minimum threshold speed. Such a threshold speed can be set as a compromise after considering fuel economy and performance and drive system smoothness. In one embodiment, depending on the vehicle and its specifications, the threshold speed for this mode can be set at approximately 30 kilometers per hour.
[0072] In many parts of the driving cycle, since the engine 102 is directly driving the wheels, this mode can be more mechanically efficient than the PMM series mode. However, in embodiments where there is no gearbox between the engine and the final reducer, it may be necessary to adjust the speed of the engine 102 to maintain the desired drive torque or power, so that more fuel can be used to generate the required power to drive the vehicle and maintain the battery. In such a case, there may be a difference in fuel efficiency between the PMM series mode and the PMM parallel mode. The controller 202 can determine this difference by continuously monitoring the two modes. It may also be more efficient to slightly adjust the speed of the engine 102 than to send energy into the battery and then retrieve the energy.
[0073] In one embodiment, it may be desirable to set a strategy for switching from series mode to parallel mode or vice versa based on the most efficient operating state over a period of time (e.g., the first 60 seconds). If the controller 202 determines that less fuel can be used in the first 60 seconds by operating in another mode, the controller 202 may switch modes in the next 60 seconds. To avoid switching between modes too frequently, an optional delay may be added.
[0074] PMM tandem mode implementation
[0075] In PMM series operation (such as Figure 3C As shown), the clutch 108 is in the open state, and the motor 106 can be used as a generator to generate electricity for the motor and maintain the battery within the desired range. Therefore, the clutch 108 can be used less frequently in the open state. This strategy can allow for less use of the clutch release bearing. In addition, this can tend to extend the life as needed to meet the durability requirements of the vehicle.
[0076] This condition may occur if the battery has been depleted to its minimum SOC by driving the vehicle and the vehicle is at a low speed (e.g., below 50 km / h). In this case, the clutch 108 can be opened and the vehicle can be placed in a series operating mode or PMM2 mode, where power from the PM and generator M1 can be used to charge the battery and drive the vehicle. The division of power can depend on the torque and charging strategy required by the PM. Additional power may also be required for accessory loads, etc. The PM can operate on its IOL to generate the total power required at that time. The recharging strategy can depend on the control strategy for recharging set into the program of the controller 202. Generally, a feasible strategy may be to recharge to the upper limit of the SOC, possibly at the slowest speed, as required by the driving mode. In PMM2 or series mode, the vehicle speed can be from zero to a maximum value maintained by the motor 110. In one embodiment, the motor 110 can be controlled substantially as in the AEM mode. The PM (e.g., the engine 102) can be as Figure 3C It is shown along its IOL and operates under the command of the controller to provide the power requested by the driver (eg, by closing clutch 104) as well as providing a power source to maintain the battery.
[0077] In another embodiment, the controller may control the engine 102 and the electric machine 106 to charge the battery with appropriate power to maintain the desired SOC in the battery during the current drive cycle. Thus, for example, the power requested by the driver / vehicle at a particular instant in time may be 50 kW, then the IC engine and generator may be set to generate 50 kW plus an additional power increment required to maintain the battery for a predetermined period of time based on a priori known drive cycle measurements.
[0078] Continuing with this example, the time period may be determined to be, for example, a minimum of 10 kW to charge the battery to a high SOC within 60 seconds. Accordingly, the engine 102 and the motor / generator 106 may be set at 60 kW until the battery reaches a predetermined high SOC. However, if the threshold is not reached within the desired time period, the incremental power required to maintain the SOC within the next 60 seconds may be increased by an expected (e.g., proportional) amount based on the deviation value. In this way, the SOC is automatically maintained regardless of how the driver behaves and what the terrain or driving cycle requires.
[0079] In another embodiment, if the driver's request is determined to be unreasonable by the controller 202 (for example, as can be detected by the controller from the pedal detection sensor, if the driver steps hard on the accelerator pedal and steps hard on the brake pedal and may have a high cycle frequency), then an indication signal can be issued to the driver to inform that more fuel than reasonable expectations have been consumed. The indication signal can be in the form of a bar graph or other proportional visual indication signals, indicating that the driver has not foreseen traffic conditions and is wasting energy. In another embodiment, the controller 202 can dynamically change the setting of the accelerator pedal to limit the acceleration rate and power required at the moment. This can be used as an economic mode used by the vehicle, and this economic mode can be selected by the driver to help save fuel. The difference in fuel consumption per kilometer can also be displayed so that the driver can see the difference in fuel consumption in real time through such selection.
[0080] Additional dynamic operating mode selection / control
[0081] As mentioned above, AEM is a type of electric vehicle that is used in pure electric vehicles or vehicles equipped with two or more motor drives, such as Figure 1 and Figure 2 Possible operating modes for a plug-in hybrid electric vehicle (PHEV) are shown. For a PHEV, the number of possible operating modes should increase due to the opportunity to use a gas engine or other ICE to provide drive power. Figure 5A and Figure 5B are two examples of allowable operating mode spaces for various vehicles as described herein. Figure 5A The operating mode space is shown on a state of charge (SOC) versus vehicle speed grid 500. As can be seen, if the SOC is high enough, the vehicle tends to use more of the electrical energy stored in the battery (rather than other motive forces, gas engine, etc.).
[0082] This can be illustrated by the exemplary bar graph on the left side of the coordinate grid 500. As can be seen, if the system indicates that the SOC is high (i.e., greater than or equal to the "SOC_high" threshold), then the system may tend to operate in a "charge depleting" mode. In this mode, the system may preferentially operate in AEM 502 (but may operate in series, parallel, or some other operating mode for different situations described herein). Alternatively, if the system indicates that the SOC is low (i.e., less than the "SOC_high" threshold), then the system may tend to operate in a "charge sustaining" mode. In this mode, the system may preferentially operate in parallel hybrid mode 504, series hybrid mode 506, or some combination thereof (but may operate in AEM for limited periods of time for different situations).
[0083] It should be appreciated that for vehicles that preferentially operate in a power-depleting operating mode, the SOC is substantially greater than or equal to the SOC_high threshold as the first threshold. Additionally, for vehicles that preferentially operate in a power-sustaining operating mode, the SOC may be less than or equal to the SOC_high threshold as the second threshold. The first threshold and the second threshold may be substantially the same threshold (i.e., SOC_high). However, in other embodiments, the first threshold and the second threshold may be different SOC values. This may be desirable from the perspective of reducing switching between operating modes used by the vehicle. In other embodiments, the first threshold and the second threshold may be functionally related to vehicle speed or other vehicle states (e.g., battery health, driver requirements, etc.) and the battery's SOC.
[0084] Additionally, it can be seen that at some point where the SOC is sufficiently low, the system can switch between AEM 502 and parallel hybrid mode 504. At even lower SOC points, the system can dynamically switch between series hybrid mode 506 and parallel hybrid mode 504. Figure 5A As shown, the switching can be performed based on the vehicle speed and also based on the SOC. Other switching conditions are also feasible. For example, the switching mode can also depend on the driver's torque requirement, traffic mode, battery health status, drive shaft speed, etc.
[0085] Figure 5B is another example of an operational mode availability space (550) available for a suitable vehicle. As can be seen, space 550 can operate in a combination of AEM and series mode 552 at low speeds / sufficiently high SOC. At higher speeds, the system can switch to a combination of series and parallel modes 554. At sufficiently high speeds, the system can preferentially operate in parallel mode 556.
[0086] As can also be seen, there can be an envelope curve 560 that defines a "minimum SOC" region 558, below which the system can operate in a mode where the engine is enabled and the system attempts to add energy back into the battery. This can limit the amount of switching between modes performed by the system controller. Above the minimum SOC line, there can be another envelope curve 562 that distinguishes between a "charge-maintaining" region and a "charge-depleting" mode. In the charge-maintaining region, the system can tend to select modes that increase and / or conserve energy within the battery. In the charge-depleting mode, the system can tend to select modes that prioritize using energy within the battery over onboard liquid fuel.
[0087] It can also be seen that the system can optionally increase the envelope curve upward as speed increases. Therefore, at higher speeds, the system can dynamically adjust the envelope curve to favor mode switching at higher SOC levels. This can be used to compensate for the faster rate of energy use at higher vehicle speeds.
[0088] One embodiment
[0089] Figure 6 is a feasible flow chart embodiment for realizing dynamic switching between the disclosed working modes. It should be appreciated that there are other feasible Figure 5A and 5B control algorithm implementation schemes, and this application covers all such applicable control algorithms.
[0090] At 602, the system and / or controller may read all system inputs including SOC, SOH, vehicle speed, engine temperature from sensors, etc. as described above. At 604, the controller may make a determination as to whether the SOC is at a sufficiently high level (e.g., SOC>SOC_high). If the answer is yes, the system / controller may select AEM 614 (or high traction electric mode if desired). If the answer is no, a determination may be made at 606 as to whether the engine has a sufficiently high temperature. If the answer is yes, the system / controller may select series hybrid mode 616. If the answer is no, a determination may be made as to whether the SOC is above a minimum SOC (SOC>SOC_low), and the vehicle may also be temporarily operated in PMM2 or series mode to warm up the engine to its operating range. If the answer is yes, a determination may be made at 612 as to whether the vehicle speed is above a certain threshold. If the answer is yes, the system / controller may select AEM at 618. If the answer is no, the system / controller may select parallel hybrid mode 620.
[0091] If the determination at 608 indicates that the SOC is not greater than or equal to the threshold level, then another determination may be made at 610 to determine if the vehicle speed is above a certain threshold. If the answer is yes, then the system / controller may select parallel hybrid mode 622. If the answer is no, then the system / controller may select series hybrid mode 624.
[0092] It will be appreciated that the thresholds for the various conditions (eg, SOC, vehicle speed) may themselves change as the state of the vehicle changes.
[0093] Dynamic operation / mode switching
[0094] Figure 7 and Figure 8 Two examples of dynamic operation in the control algorithm as described herein are shown. Figure 7 Two figures are used to illustrate an exemplary driving cycle. The upper figure shows the speed of motor 1, motor 2 and the engine in a time segment. The lower figure shows the vehicle speed (related to the RPM of the drive shaft) in the same time segment. The upper figure shows how a control algorithm embodiment can match and switch the vehicle's operating mode according to the driving cycle.
[0095] At 702, during the time segment from zero to about 440 seconds, it can be seen that the controller has selected parallel mode for the vehicle. During this time, the speeds of motor 1, motor 2, and the engine are matched because they are all running on the same drive shaft and both clutches are closed. At point 704, the system / controller detects that the user has commanded the vehicle to stop. However, considering the SOC or other appropriate conditions, it may be necessary for the system / controller to switch to series mode between 440 seconds and 480 seconds.
[0096] At this point, the engine and motor 1 can be decoupled from motor 2. Therefore, the engine and motor 1 can continue to operate along curve 708 to generate electrical energy to be sent back to the battery. At the same time, motor 2 can continue to operate along curve 706 to stop the vehicle or coast. At about 470 seconds, it can be seen that the user commands the vehicle to accelerate, and motor 2 responds to increase the speed of the vehicle. PM (e.g., engine 102) and motor 1 can operate along their IOLs to power motor 2 and provide additional power to maintain the battery.
[0097] At point 710, it can be seen that it is necessary to have the system / controller switch to parallel mode at around 480 seconds. In this case, clutch 108 needs to be engaged to allow the engine and motor 1 to engage with the rest of the drive shaft to provide power directly to the wheels. At this time, it is necessary to have the speed of the drive shaft disengage from motor 1 substantially match the start speed of the drive shaft at motor 2. Therefore, for example, in order to smooth the transition, the speed of the engine and motor 1 are slowed to a substantially matching level and clutch 108 is closed. For Figure 7 In the rest of the diagram, it can be seen that the system / controller operates and switches the vehicle's operating modes in a similar manner.
[0098] Figure 8 is similar to Figure 7 An exemplary driving cycle diagram of Figure 8, the system / controller switches primarily between AEM (EV) mode and parallel mode. As can be seen at 802, the vehicle is operating in parallel mode and the speeds of motor 1, motor 2, and the engine are matched because they are all engaged on the main drive shaft. At point 804, the system / controller switches from parallel mode to AEM mode at approximately 1277 seconds. As can be seen, clutch 108 opens and the engine and motor 1 go to zero speed (i.e., shut down). During this process, motor 1 can be actively torque or speed controlled to reduce engine shutdown vibrations.
[0099] The vehicle can be driven by motor 2, and at approximately 1290 to 1296 seconds, the system / controller detects conditions (e.g., torque requested by the user) to ensure that the switch to parallel mode is made. At point 808, the engine can be seen to be started by motor 1, at which time clutch 104 is closed and clutch 108 is open. At this point, the speed of the engine and motor 1 can be controlled to match the speed of motor 2 (or drive shaft) (since motor 1 has been disengaged from the drive shaft). At speed synchronization, clutch 108 is closed and the engine is available to provide torque to the drive shaft, with substantially no or little torque disturbance to the drive shaft.
[0100] Another embodiment
[0101] In order to control Figure 7 and Figure 8 For mode transitions shown, the controller may have an algorithm for determining mode actions and transitions. Fig. 9 In one embodiment shown, the controller may have a state machine that defines hybrid powertrain "permanent states (or modes)" such as all-electric mode 904, series hybrid mode 906, parallel hybrid mode 908, and fault mode 910. The powertrain system generally operates in one of these permanent modes until a mode transition trigger condition is detected and / or satisfied. The transition trigger condition from the source mode to the target mode may be based on, for example, Figure 5A ,5B or Figure 6 Before achieving the target permanent mode, the powertrain system enters a transition mode such as AEM-PMM2 transition mode 912, PMM1-PMM2 transition mode 914, and AEM-PMM1 transition mode 916. A transition mode is a temporary mode in which the powertrain system can be controlled or configured to support operation in a transition to the target mode. The transition is allowed only after the fault and diagnostic based verification is completed and the new powertrain mode request is satisfied. For example, Figure 7 Points 704 and 710 in correspond to the parallel-to-series (PMM1 -PMM2) transition mode 1014. Figure 8 Points 804 and 808 in correspond to Fig. 9 All-electric-parallel (AEM-PMM1) transition mode 916.
[0102] Fault Tolerance Strategy
[0103] A fault algorithm may be implemented in each powertrain mode, and is implemented to detect whether a fault has occurred while the vehicle is operating in that mode. Fig. 9 is an embodiment of a control algorithm / state diagram for implementing fault tolerance. When a system fault is detected, the power system switches to fault mode 910 to continue operating the vehicle in a safe manner. The fault mode can force the power system to operate at a reduced level, such as reducing the motor torque. In some cases, if the fault severity is high and the vehicle is not allowed to travel, the fault mode can force the power system to stop operating completely. After the fault state is removed, the power system can be allowed to switch back to the appropriate permanent mode (904, 906 and 908). A feasible fault-tolerant design is that if the system is operating in a transition mode (912, 914 or 916) and the transition time before entering the target mode exceeds a predetermined threshold due to component aging, the system state is transferred to fault mode 910. The system can remain in the fault mode or switch back to the source mode depending on the severity of the fault.
[0104] It should be appreciated that there may be other situations that may cause the system to be processed in failure mode. The following are some other examples of such situations / failures:
[0105] Fault Example 1: If the motor temperature sensor feedback is not normal (e.g., out of range fault), the system can enter fault mode operation 910. In this mode, the motor torque can be significantly reduced and an alarm can be issued to the driver.
[0106] Fault Example 2: In series mode (PMM2) 906, if the system detects that motor 1 is not generating electricity (e.g., due to motor 1 failure or engine failure), then the series mode can be terminated and the fault mode can be entered. The fault mode can shut down the engine and operate the vehicle only electrically driven by motor 2. If the fault condition is resolved, the system can be allowed to resume full electric mode 904 for normal operation.
[0107] Fault Example 3: If the clutch position cannot be confirmed from the sensor (eg due to a sensor failure), the system may enter Fault Mode 910. In Fault Mode only the motor 2 may be used to drive the vehicle. No clutch actuation is permitted.
[0108] Advanced Battery Management Examples
[0109] In another application of the present application, it may be necessary to add appropriate battery management to improve the life and performance of the battery. Although most batteries provided by battery manufacturers typically include a battery management system (BMS) 119A, these BMSs are not able to fully and / or optimally manage vehicle batteries for HEV / PHEV. Therefore, a typical BMS can provide information to a higher-level controller (such as controller 202) and rely on the controller to further control secondary factors such as efficient use of electrical energy and maintenance of correct battery use. Such an additional control system-battery monitoring and maintenance system (BMMS) can be provided by Figure 1 The controller 202 is shown implemented.
[0110] In a BMMS embodiment implemented according to the principles of the present application, when the battery pack is discharged to generate the power required by the vehicle and the driver, in order to promote the healthy use of the battery to extend the battery life, it may be desirable to provide power when the vehicle is driven in AEM or PMM (e.g., PMM1 and / or PMM2) mode to maximize the use of electrical energy. If the battery system has limitations on the available power and / or current (as can be determined by the BMMS considering the battery SOC), the temperature and temperature distribution, battery age and other parameters can be considered by the BMMS (and / or controller 202). The BMMS and / or controller 202 can limit the power and / or current performance to protect the battery from sudden adverse impacts. Such adverse impacts can occur, for example, when the vehicle is started. In this case, the controller 202 can actively control the current output of the battery and thereby control the motor output. In this embodiment, it is possible to achieve a reduced performance compared to the performance achieved if such restrictions are not imposed. However, this performance limitation can be converted into a longer battery life and a larger power range in a vehicle driven in AEM or PMM mode.
[0111] It is known that all batteries have internal resistance, and the internal resistance loss in the battery pack will cause the battery pack to heat up. However, this loss is proportional to I 2 ×R, where I is the battery current and R is the instantaneous internal resistance of the battery. This battery internal resistance tends to vary depending on battery type, SOC, temperature, age, etc. Therefore, in one embodiment, the BMMS can regulate the discharge of the battery pack based on the battery's state of health (SOH), state of charge (SOC), temperature, and other factors, as may be necessary to affect the life of the battery pack.
[0112] In addition, when the vehicle's kinetic energy is used to recharge the battery in the vehicle through the vehicle's main PM (e.g., engine 102, fuel cell) or other power generation equipment or during regenerative braking, the BMMS and / or controller 202 can determine the maximum current required to meet the power required to maintain the power demand of the transmission system and charge the battery pack with a minimum current sufficient to replenish the power consumed by the specified driving event. Such a driving event can occur within a specified time period, such as within the past "X" seconds, where X can be a function of the driving event, such as driving on a congested urban road or mountain road. This recharging current limit can also be determined by the driver's driving characteristics and the vehicle's environmental conditions, such as traffic conditions, ambient temperature, etc.
[0113] In one embodiment, the control program may be integrated into the BMMS controller. Fig.10 It is an embodiment of an advanced battery management control strategy. Fig.10 A grid of SOC versus vehicle speed is shown and an exemplary drive cycle resulting in a momentary discharge and speed curve 1006 is shown therein. An average discharge and speed curve 1008 is derived from curve 1006 and plotted alongside it.
[0114] The driving cycle is managed and / or controlled between two SOC values, namely, a maximum SOC cutoff envelope 1002 and a minimum SOC cutoff envelope 1004. For illustration purposes only, curves 1002 and 1004 are illustrated as straight lines, but it should be understood that other envelopes are possible. Fig.10 It is shown that the average vehicle speed is lower when discharging the battery (that is, when turning from the upper charge limit state to the lower charge limit state line) and the vehicle speed is higher when charging the battery. This is not always the case, but it can be used to distinguish between taking energy from the battery and charging energy back into the battery. These states can be about the same speed, for example. The division of speed is to clarify the concept. The trajectory lines show the changes as the battery is charged and discharged and the vehicle speed. The green line is the average trajectory of discharge or charge. It should be noted that the discharge trajectory can be shorter in time than the charge because it may be necessary to charge as slowly as possible to significantly improve charging efficiency as well as reduce battery heating and enhance battery health. Charging time can be maximized by BMMS. Fig.10 It is further shown that the threshold value may be a function of vehicle speed, since the energy required to drive the vehicle is a function of vehicle speed.
[0115] The upper SOC threshold 1002 and the lower SOC threshold 1004 can be straight lines or curves, which can be functions of vehicle speed and other parameters. Currently, hybrid vehicles tend to maintain high SOC and low SOC of the battery independently of speed. In one embodiment, the BMMS implements curves or other dependencies between these thresholds. In another embodiment, the BMMS can implement curves or other dependencies between different relationships between (1) high SOC threshold and vehicle speed and (2) low SOC threshold and vehicle speed. These relationships can be determined by the needs of the vehicle and the battery pack. The curves can be different for the combination of vehicle range and battery specifications and can also depend on the application and possible driver instructions.
[0116] Driver-characteristics-based implementation
[0117] Driver demand can be gauged by the driver's action on the accelerator and brake pedals. It is desirable to collect this information for feedback into the BMMS. In one embodiment, this can be accomplished by measuring average accelerator and brake pedal action and the secondary torque of these pedal positions to determine the offset and frequency of the action. This data can be used to determine the aggressiveness of the driver. Since the energy required to drive a particular vehicle speed profile tends to be proportional to the driver's action, this statistical information can be used to determine the energy consumption per specified vehicle distance traveled or the energy efficiency of the vehicle.
[0118] This information can be compared to a "standard" or controlled test condition, and in one embodiment the indications can be displayed to the driver with a time history to provide driver feedback on a more appropriate driving style. Possible improvement indications can be provided to the driver to encourage him to minimize acceleration and brake pedal changes, thereby reducing power consumption and improving electric range and vehicle efficiency.
[0119] In addition, this information can be used to set the range of variation and the average state of charge (SOC) of the battery pack. In one embodiment, the more vigorously and frequently the accelerator and brake pedals are used, the higher the minimum SOC threshold can be set, in order to avoid the battery SOC from becoming too low during driving. This is done because it is necessary to meet the requirements of the road or other overload conditions to allow the battery SOC to be temporarily reduced to beyond the lower limit boundary. In one such example, if the accelerator pedal is pressed to the limit for more than a first time period (e.g., 5 seconds, etc.), for example, meaning that the driver continues to require high power during this time period and therefore may need to operate seriously to require the full power of the vehicle, then the lower limit boundary can be allowed to be crossed. Beyond this first time period, the power can be reduced through a degradation strategy that does not endanger safety but protects the battery, as will be described in reference to the present document. Fig.11 As discussed.
[0120] In another embodiment, the BMMS can also be used to notify the system when changing from AEM mode (e.g., charge depletion) to series or parallel PMM (e.g., charge preservation) or vice versa. Since average vehicle speed can be a determining factor in the energy used over time, this information combined with the accelerator pedal demand can determine the power used. In one embodiment, speed and accelerator and brake pedal demands can be used as inputs, which can be used to determine the power required and the energy required over a specific time period, assuming that future maneuvers have the same statistical characteristics in terms of road load and driver behavior.
[0121] With this information, it is possible to predict or estimate what the conditions may be for a future time period (e.g., the next ten (10) seconds, etc.). One strategy may be to use the same maximum power and energy as the previous ten (10) seconds, or any suitable time period. It will be appreciated that other strategies may be used. For example, the prediction time and the data collection time do not need to be the same. Once the predicted value of the charging current is determined, the power level of the engine and generator can then be determined. If this current level is too high for the current state of the battery (determined by the battery's temperature, state of charge, state of health, etc.), then the vehicle's performance can be limited by the vehicle controller. In the case of a pure EV, all vehicles driven solely by the battery pack may have limited performance in certain circumstances. The BMMS can limit performance in advance to protect the battery and provide the longest expected range for battery alone.
[0122] One embodiment
[0123] Fig.11 An embodiment of a dynamic BMMS control strategy obtained according to the principles of the present application is shown.
[0124] Fig.11 is a mapping of vehicle speed and SOC. As can be seen, the BMMS module can dynamically select among several curves for high SOC or low SOC thresholds. In one embodiment, the BMMS can set such charge and discharge limits based on battery demand rather than vehicle speed demand. The driver may not be able to distinguish the difference, but the battery can be better protected.
[0125] exist Fig.11At the bottom of this graph there may be an optional appropriately adequate minimum allowed SOC below which the BMMS will not allow the battery to be depleted. If this value is included within the BMMS, it may be determined by a variety of factors such as battery specifications, warranty considerations, etc. Other curves that may be implemented include: a high SOC threshold for charge retention (1108), a low SOC for large variations in acceleration and / or braking action (1106), a low SOC for average acceleration and / or braking action (1104), and a low SOC for small variations in acceleration and / or braking action (1102). As described above, these curves may be selected based on the driver's acceleration and / or braking action and any identifiable relevant statistical information (e.g., 1110).
[0126] The BMMS can determine that low-speed travel in AEM mode can consume the battery to the minimum SOC boundary, and then the powertrain system should switch to PMM or series or parallel mode. In order to determine the appropriate SOC for a specified vehicle speed and driver action, the average and standard distribution of speeds can be measured and / or calculated. In one embodiment, the low SOC can be set as small as possible based on these data. For example, if the average vehicle speed is below a certain speed (e.g., 30 kilometers per hour) and the speed change is also small, the SOC can be set to the minimum value allowed by battery durability and planned vehicle instantaneous power and energy considerations. However, if the speed changes too quickly, indicating an emergency stop and start of traffic, the low SOC boundary should be set to a higher value to allow the use of higher power over a longer period of time. This situation may occur, for example, when driving on a road with heavy traffic.
[0127] When the vehicle is in a PMM state in charge retention or series or parallel mode, the charging rate can be set to a minimum value determined by the above-mentioned vehicle state and battery characteristics. As described above, the charging rate can depend on vehicle action and driver action. Statistical information can be used to determine the charging rate for the battery pack as well as the average SOC and ΔSOC. It may be necessary to set the maximum SOC line and the minimum SOC line and the rated SOC or intermediate SOC according to the vehicle speed. Then, based on the driving statistical information, the high SOC line and the low SOC line can be modified to be narrower through the statistical information. This narrowing can lead to better maintenance of the battery and stimulating the battery in a shorter trip to thereby extend the life.
[0128] An example
[0129] Fig.12 An exemplary drive cycle and battery SOC control as a function of vehicle speed and time is shown. Fig.12 It is helpful to introduce BMMS control and mode switching. The vehicle mode shown here is AEM (or charge depletion), where the battery can be regenerated by braking the vehicle. Fig.12 Also shown is the PMM charge-sustaining mode for series or parallel connections.
[0130] As can be seen, the BMMS may optionally set a minimum SOC floor (1202) that is shown to avoid battery damage or protect warranty obligations.
[0131] Fig.12 A graph of battery state of charge SOC, vehicle speed, and time is shown. Curve 1208 shows this exemplary driving cycle. Curve 1208 starts from a stop point (vehicle speed = 0) and at a high SOC. Since the vehicle is traveling in AEM mode, the battery is shown as being consumed. The vehicle travels along the black line in AEM mode until the battery SOC reaches the high SOC plane (1206) at point A. At this point, the vehicle can remain in AEM mode or change to PMM mode, but the battery can continue to be consumed to the low SOC plane (1204) at point B.
[0132] At point B, the vehicle can switch to PMM and the battery can be charged until the SOC reaches the high SOC plane again at point C. The battery can be consumed again while driving in PMM mode or AEM mode. In the case of a vehicle on a mountain road or in a continuous high load state (such as pulling a trailer), the SOC may drop below the low SOC plane. This may be required to maintain performance or for safety reasons. However, for such high performance requirements, the battery can continue to discharge until the minimum SOC plane (1202) is reached, and the battery is not allowed to drop below this plane.
[0133] In one embodiment, the vehicle controller may then warn the driver that he can no longer continue driving at this performance level and begin limiting performance to protect the battery. The vehicle may slow down as power may be reduced to protect the battery. The reduction in power may begin before the SOC floor is reached to warn the driver that the floor is approaching by gradually reducing the available power by a certain amount, such as about 5% every 10 seconds.
[0134] Fig.12 It is also helpful to show the relationship between the three planes of high SOC, low SOC and floor. In one application, the BMMS strategy can be used to achieve minimum fuel consumption, and in one embodiment, the engine can be reduced to a minimum size to maintain a constant speed on a flat road. The battery can not take into account small changes in the road or road load until the floor is reached, and the output power of the vehicle and the dynamic performance of the vehicle can be reduced. If there is a gearbox, the torque performance of the vehicle can be maintained by switching the gearbox to a higher reduction gear or a lower gear.
[0135] In another embodiment, the "degree of hybridization" or relative size of the engine and motor / battery pack can determine the potential minimum SOC and ΔSOC. For example, if the engine is minimized and the average power demand of the vehicle is high and varies widely, the minimum SOC should be set higher because the battery and motor may need to frequently supplement the power from the engine. If the engine or prime mover is larger, the SOC can be set lower for longer all-electric range (AER), but the highway fuel economy of the vehicle in charge preservation mode may become lower due to the larger engine and therefore the engine is running less efficiently.
[0136] In one embodiment, the vehicle can be designed so that when the engine is running, the engine should be large enough to drive the set full load on a flat or nearly flat road. When there is a possibility of continuous high load, such as driving on a mountain road or driving a trailer, the average SOC and ΔSOC should also be relatively large or dynamically increased. The prime mover power must be large enough to meet the load at the required speed and the specific load and slope conditions for long-term or steady-state operation. The engine can be further reduced, but accordingly it may not be able to maintain speed for a long time for a specific load. Therefore, a compromise must be made between hybrid power and the ability to maintain speed on a flat road or a road with minimal slope.
[0137] For example, the top speed of the vehicle can be determined by the sum of the prime mover and motor power and the battery power. But how long this speed can be maintained is determined by the specifications of the battery pack. After the battery pack is depleted to a minimum SOC determined by the battery program of the vehicle controller, the speed is gradually reduced to a speed that can be maintained by the engine alone. Therefore, the hybrid power is limited by the vehicle speed maintained.
[0138] Hybrid power may also be used to determine battery specifications and motor size. However, minimum cost may be determined by the minimum battery size and power. The optimal battery capacity (kWh) and power (kW) may be determined to meet performance requirements and cost targets. An optimization algorithm as a function of driving expectations, fuel economy expectations, and acceleration performance specifications may be determined to minimize vehicle cost and petroleum energy consumption. A tax rebate for saving 40% fuel on a standard vehicle regardless of hybrid power may be a general rule that can determine the required engine size.
[0139] The above-described vehicle control strategy may be implemented to maximize the vehicle's hybrid degree DOH, but also to protect the battery from entering an area where its life and performance may be affected and fall short of the battery manufacturer's expectations.
[0140] In general, PHEVs can be used to replace fossil fuels and to enable the use of renewable energy. It may also be necessary to use larger battery packs that can have longer AEM ranges in the future. Therefore, the use of renewable energy from local sun and wind can be integrated into high DOH vehicles.
[0141] This concept can allow a high DOH vehicle to replace a large portion of fossil fuels while still maintaining performance through the battery pack. The performance may not be maintained for too long, but the duration should still be long enough to meet the user's driving needs for more than 90%. The few cases where performance drops below the low SOC plane and reaches the bottom where performance may be reduced should be kept to a minimum based on the vehicle specifications. If the frequency of reaching the bottom is frequent and drivers and owners need more performance, the PHEV can be equipped with a larger engine for this purpose. It is possible for PHEV manufacturers to offer multiple vehicle variants, such as with 3 or more engine sizes. It may also be necessary to offer 3 or more DOH configurations for the same vehicle. It should be noted that battery management can consider DOH together with the architecture because they can both affect the robustness of the BMMS.
[0142] The above description includes multiple examples of the subject invention. It is certainly impossible to introduce every possible combination of components or methods for the purpose of introducing the claimed subject matter, but those skilled in the art will recognize that many further permutations and combinations are possible in the subject invention. Therefore, it should be determined that the claimed subject matter includes all such alternatives, modifications and variations that fall within the spirit and scope of the appended claims.
[0143] Specifically and with respect to the various functions implemented by the above-mentioned components, devices, circuits, systems, etc., unless otherwise specified, the terms used to introduce these components (including references to "means") should be understood to correspond to any component that performs the specific functions of the components (e.g., functional equivalence), even if the structure is not identical to the disclosed structure, as long as the functions of the exemplary application of the claimed subject matter are performed as shown herein. In this regard, it should also be recognized that the present invention includes a system and a computer-readable medium having computer-executable instructions for performing the actions and / or events of the various methods in the claimed subject matter.
[0144] In addition, although a particular feature of the subject invention may have been disclosed with reference to only one of several embodiments, such feature may also be combined with one or more other features in other embodiments as desired and advantageous for any given or particular application. Moreover, to the extent the terms "comprises" and "comprising" and variations thereof are used in the detailed description or claims, these terms should be understood to be inclusive in a manner similar to the term "comprising".
Claims
1. A method for controlling operation of a powertrain of a hybrid electric vehicle (HEV), the HEV vehicle comprising a prime mover; a first motor-generator; a battery, the battery being electrically connected to the first motor-generator, the battery being configured to provide electrical energy to the first motor-generator; and a controller configured to receive signals from one or more sensors and to provide control signals to the prime mover and the first motor-generator; The method comprises: determining a driver's energy usage pattern over time, the energy usage pattern comprising: the driver's actions on an accelerator pedal and actions on a brake pedal; selecting a first state of charge (SOC) threshold curve from a set of SOC threshold curves, the first SOC threshold curve being dependent on the energy usage pattern of the driver; selecting an operating mode of the HEV vehicle according to SOC and vehicle speed based on the first SOC threshold curve; selecting a second SOC threshold curve that is higher than the first SOC threshold curve if the driver's energy usage pattern over time exhibits a first change in at least one of accelerator pedal actuation and brake pedal actuation over time; selecting a second SOC threshold curve that is lower than the first SOC threshold curve if the driver's energy usage pattern over time exhibits a second change in at least one of accelerator pedal actuation and brake pedal actuation over time that is less than the first change; and selecting an operating mode of the HEV vehicle according to the SOC and the vehicle speed based on the second SOC threshold curve; Wherein selecting the operating mode of the HEV vehicle according to the SOC and the vehicle speed based on the first SOC threshold curve or the second SOC threshold curve includes: determining the SOC of the battery and the speed of the vehicle; determining a corresponding SOC threshold for the vehicle speed on the first SOC threshold curve or the second SOC threshold curve; If the SOC of the battery is greater than the corresponding SOC threshold, selecting a power-depleting operating mode of the HEV vehicle; and If the SOC of the battery is less than the corresponding SOC threshold, a charge-sustaining operating mode of the HEV vehicle is selected.
2. The method of claim 1, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
3. The method of claim 2, further comprising: Driver demand information is displayed to give suggestions to the driver to improve energy efficiency.
4. The method of claim 2, further comprising: The driver's future energy demand is predicted, and an SOC threshold curve is selected based on the prediction.
5. The method of claim 1, wherein the prime mover comprises a fuel cell.
6. The method of claim 5, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
7. The method of claim 1, wherein the powertrain for the HEV vehicle comprises: a first clutch, the first motor-generator being mechanically connected to the prime mover via the first clutch; a second motor-generator and a second clutch, the second motor-generator being mechanically connected to the first motor-generator via the second clutch; the battery being electrically connected to the second motor-generator, the battery being configured to provide electrical energy to the second motor-generator; And the controller is configured to provide control signals to the first clutch, the second clutch, and the second motor-generator.
8. The method of claim 7, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
9. A system for controlling operation of a powertrain of a hybrid electric vehicle (HEV), the HEV vehicle comprising a prime mover; a first motor-generator; a battery, the battery being electrically connected to the first motor-generator, the battery being configured to provide electrical energy to the first motor-generator; and a controller configured to receive signals from one or more sensors and to provide control signals to the prime mover and the first motor-generator; The controller executes the following computer-implemented instructions, including: determining a driver's energy usage pattern over time, the energy usage pattern comprising: the driver's actions on an accelerator pedal and actions on a brake pedal; selecting a first state of charge (SOC) threshold curve from a set of SOC threshold curves, the first SOC threshold curve being dependent on the energy usage pattern of the driver; selecting an operating mode of the HEV vehicle according to SOC and vehicle speed based on the first SOC threshold curve; selecting a second SOC threshold curve that is higher than the first SOC threshold curve if the driver's energy usage pattern over time exhibits a first change in at least one of accelerator pedal actuation and brake pedal actuation over time; and selecting a second SOC threshold curve that is lower than the first SOC threshold curve if the driver's energy usage pattern over time exhibits a second change in at least one of accelerator pedal actuation and brake pedal actuation over time that is less than the first change; and selecting an operating mode of the HEV vehicle according to the SOC and the vehicle speed based on the second SOC threshold curve; Wherein selecting the operating mode of the HEV vehicle according to the SOC and the vehicle speed based on the first SOC threshold curve or the second SOC threshold curve includes: determining the SOC of the battery and the speed of the vehicle; determining a corresponding SOC threshold for the vehicle speed on the first SOC threshold curve or the second SOC threshold curve; If the SOC of the battery is greater than the corresponding SOC threshold, selecting a power-depleting operating mode of the HEV vehicle; and If the SOC of the battery is less than the corresponding SOC threshold, a charge-sustaining operating mode of the HEV vehicle is selected.
10. The system of claim 9, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
11. The system of claim 10, further comprising: Driver demand information is displayed to give suggestions to the driver to improve energy efficiency.
12. The system of claim 10, further comprising: The driver's future energy demand is predicted, and an SOC threshold curve is selected based on the prediction.
13. The system of claim 9, wherein the prime mover comprises a fuel cell.
14. The system of claim 13, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
15. The system of claim 9, wherein the powertrain for the HEV vehicle comprises: a first clutch, the first motor-generator being mechanically connected to the prime mover via the first clutch; a second motor-generator and a second clutch, the second motor-generator being mechanically connected to the first motor-generator via the second clutch; the battery being electrically connected to the second motor-generator, the battery being configured to provide electrical energy to the second motor-generator; And the controller is configured to provide control signals to the first clutch, the second clutch, and the second motor-generator.
16. The system of claim 15, wherein determining the driver's energy usage pattern over time further comprises: Measuring average accelerator pedal movement and average brake pedal movement; And measuring the second torque of the accelerator pedal action and the brake pedal action.
