This disclosure is related to controlling an engine within a hybrid vehicle.
The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.
Known powertrain architectures include torque-generative devices, including internal combustion engines and electric machines, which transmit torque through a transmission device to an output member. One exemplary powertrain includes a two-mode, compound-split, electromechanical transmission which utilizes an input member for receiving motive torque from a prime mover power source, preferably an internal combustion engine, and an output member. The output member can be operatively connected to a driveline for a motor vehicle for transmitting tractive torque thereto. Electric machines, operative as motors or generators, generate a torque input to the transmission, independently of a torque input from the internal combustion engine. The electric machines may transform vehicle kinetic energy, transmitted through the vehicle driveline, to electrical energy that is storable in an electrical energy storage device. A control system monitors various inputs from the vehicle and the operator and provides operational control of the powertrain, including controlling transmission operating state and gear shifting, controlling the torque-generative devices, and regulating the electrical power interchange among the electrical energy storage device and the electric machines to manage outputs of the transmission, including torque and rotational speed.
An internal combustion engine is mechanically coupled to an electro-mechanical transmission to transmit power to a driveline in response to an operator torque request. A method for operating the engine includes defining a two-dimensional search region based upon an input power transmittable between the internal combustion engine and the electromechanical transmission. The method further includes iteratively dividing the two-dimensional search region into a plurality of subregions based upon one of the input power and the input speed, iteratively determining an engine operating point within each of the subregions, iteratively calculating an operating cost to operate the internal combustion engine and the electromechanical transmission to meet the operator torque request for each engine operating point within each of the subregions, and iteratively identifying the subregion having a minimum operating cost to meet the operator torque request. A preferred engine operating point is determined based upon the engine operating point within the identified subregion having the minimum operating cost to meet the operator torque request.
One or more embodiments will now be described, by way of example, with reference to the accompanying drawings, in which:
Referring now to the drawings, wherein the showings are for the purpose of illustrating certain exemplary embodiments only and not for the purpose of limiting the same,
The exemplary engine 14 comprises a multi-cylinder internal combustion engine selectively operative in several states to transfer torque to the transmission 10 via an input shaft 12, and can be either a spark-ignition or a compression-ignition engine. The engine 14 includes a crankshaft (not shown) operatively coupled to the input shaft 12 of the transmission 10. A rotational speed sensor 11 monitors rotational speed of the input shaft 12. Power output from the engine 14, comprising rotational speed and engine torque, can differ from the input speed N, and the input torque TI to the transmission 10 due to placement of torque-consuming components on the input shaft 12 between the engine 14 and the transmission 10, e.g., a hydraulic pump (not shown) and/or a torque management device (not shown).
The exemplary transmission 10 comprises three planetary-gear sets 24, 26 and 28, and four selectively engageable torque-transferring devices, i.e., clutches C170, C262, C373, and C475. As used herein, clutches refer to any type of friction torque transfer device including single or compound plate clutches or packs, band clutches, and brakes, for example. A hydraulic control circuit 42, preferably controlled by a transmission control module (hereafter ‘TCM’) 17, is operative to control clutch states. Clutches C262 and C475 preferably comprise hydraulically-applied rotating friction clutches. Clutches C170 and C373 preferably comprise hydraulically-controlled stationary devices that can be selectively grounded to a transmission case 68. Each of the clutches C170, C262, C373, and C475 is preferably hydraulically applied, selectively receiving pressurized hydraulic fluid via the hydraulic control circuit 42.
The first and second electric machines 56 and 72 preferably comprise three-phase AC machines, each including a stator (not shown) and a rotor (not shown), and respective resolvers 80 and 82. The motor stator for each machine is grounded to an outer portion of the transmission case 68, and includes a stator core with coiled electrical windings extending therefrom. The rotor for the first electric machine 56 is supported on a hub plate gear that is operatively attached to shaft 60 via the second planetary gear set 26. The rotor for the second electric machine 72 is fixedly attached to a sleeve shaft hub 66.
Each of the resolvers 80 and 82 preferably comprises a variable reluctance device including a resolver stator (not shown) and a resolver rotor (not shown). The resolvers 80 and 82 are appropriately positioned and assembled on respective ones of the first and second electric machines 56 and 72. Stators of respective ones of the resolvers 80 and 82 are operatively connected to one of the stators for the first and second electric machines 56 and 72. The resolver rotors are operatively connected to the rotor for the corresponding first and second electric machines 56 and 72. Each of the resolvers 80 and 82 is signally and operatively connected to a transmission power inverter control module (hereafter ‘TPIM’) 19, and each senses and monitors rotational position of the resolver rotor relative to the resolver stator, thus monitoring rotational position of respective ones of first and second electric machines 56 and 72. Additionally, the signals output from the resolvers 80 and 82 are interpreted to provide the rotational speeds for first and second electric machines 56 and 72, i.e., NA and NB, respectively.
The transmission 10 includes an output member 64, e.g. a shaft, which is operably connected to a driveline 90 for a vehicle (not shown), to provide output power to the driveline 90 that is transferred to vehicle wheels 93, one of which is shown in
The input torque from the engine 14 and the motor torques from the first and second electric machines 56 and 72 (TI, TA, and TB respectively) are generated as a result of energy conversion from fuel or electrical potential stored in an electrical energy storage device (hereafter ‘ESD’) 74. The ESD 74 is high voltage DC-coupled to the TPIM 19 via DC transfer conductors 27. The transfer conductors 27 include a contactor switch 38. When the contactor switch 38 is closed, under normal operation, electric current can flow between the ESD 74 and the TPIM 19. When the contactor switch 38 is opened electric current flow between the ESD 74 and the TPIM 19 is interrupted. The TPIM 19 transmits electrical power to and from the first electric machine 56 by transfer conductors 29, and the TPIM 19 similarly transmits electrical power to and from the second electric machine 72 by transfer conductors 31 to meet the torque commands for the first and second electric machines 56 and 72 in response to the motor torques TA and TB. Electrical current is transmitted to and from the ESD 74 in accordance with whether the ESD 74 is being charged or discharged.
The TPIM 19 includes the pair of power inverters (not shown) and respective motor control modules (not shown) configured to receive the torque commands and control inverter states therefrom for providing motor drive or regeneration functionality to meet the commanded motor torques TA and TB. The power inverters comprise known complementary three-phase power electronics devices, and each includes a plurality of insulated gate bipolar transistors (not shown) for converting DC power from the ESD 74 to AC power for powering respective ones of the first and second electric machines 56 and 72, by switching at high frequencies. The insulated gate bipolar transistors form a switch mode power supply configured to receive control commands. There is typically one pair of insulated gate bipolar transistors for each phase of each of the three-phase electric machines. States of the insulated gate bipolar transistors are controlled to provide motor drive mechanical power generation or electric power regeneration functionality. The three-phase inverters receive or supply DC electric power via DC transfer conductors 27 and transform it to or from three-phase AC power, which is conducted to or from the first and second electric machines 56 and 72 for operation as motors or generators via transfer conductors 29 and 31 respectively.
The aforementioned control modules communicate with other control modules, sensors, and actuators via a local area network (hereafter ‘LAN’) bus 6. The LAN bus 6 allows for structured communication of states of operating parameters and actuator command signals between the various control modules. The specific communication protocol utilized is application-specific. The LAN bus 6 and appropriate protocols provide for robust messaging and multi-control module interfacing between the aforementioned control modules, and other control modules providing functionality including e.g., antilock braking, traction control, and vehicle stability. Multiple communications buses may be used to improve communications speed and provide some level of signal redundancy and integrity. Communication between individual control modules can also be effected using a direct link, e.g., a serial peripheral interface (‘SPI’) bus (not shown).
The HCP 5 provides supervisory control of the hybrid powertrain, serving to coordinate operation of the ECM 23, TCM 17, TPIM 19, and BPCM 21. Based upon various input signals from the user interface 13 and the hybrid powertrain, including the ESD 74, the HCP 5 determines an operator torque request, an output torque command, an engine input torque command, clutch torque(s) for the applied torque-transfer clutches C170, C262, C373, C475 of the transmission 10, and the motor torques TA and TB for the first and second electric machines 56 and 72. The TCM 17 is operatively connected to the hydraulic control circuit 42 and provides various functions including monitoring various pressure sensing devices (not shown) and generating and communicating control signals to various solenoids (not shown) thereby controlling pressure switches and control valves contained within the hydraulic control circuit 42.
The ECM 23 is operatively connected to the engine 14, and functions to acquire data from sensors and control actuators of the engine 14 over a plurality of discrete lines, shown for simplicity as an aggregate bi-directional interface cable 35. The ECM 23 receives the engine input torque command from the HCP 5. The ECM 23 determines the actual engine input torque, TI, provided to the transmission 10 at that point in time based upon monitored engine speed and load, which is communicated to the HCP 5. The ECM 23 monitors input from the rotational speed sensor 11 to determine the engine input speed to the input shaft 12, which translates to the transmission input speed, NI. The ECM 23 monitors inputs from sensors (not shown) to determine states of other engine operating parameters including, e.g., a manifold pressure, engine coolant temperature, ambient air temperature, and ambient pressure. The engine load can be determined, for example, from the manifold pressure, or alternatively, from monitoring operator input to the accelerator pedal 113. The ECM 23 generates and communicates command signals to control engine actuators, including, e.g., fuel injectors, ignition modules, and throttle control modules, none of which are shown.
The TCM 17 is operatively connected to the transmission 10 and monitors inputs from sensors (not shown) to determine states of transmission operating parameters. The TCM 17 generates and communicates command signals to control the transmission 10, including controlling the hydraulic circuit 42. Inputs from the TCM 17 to the HCP 5 include estimated clutch torques for each of the clutches, i.e., C170, C262, C373, and C475, and rotational output speed, No, of the output member 64. Other actuators and sensors may be used to provide additional information from the TCM 17 to the HCP 5 for control purposes. The TCM 17 monitors inputs from pressure switches (not shown) and selectively actuates pressure control solenoids (not shown) and shift solenoids (not shown) of the hydraulic circuit 42 to selectively actuate the various clutches C170, C262, C373, and C475 to achieve various transmission operating range states, as described hereinbelow.
The BPCM 21 is signally connected to sensors (not shown) to monitor the ESD 74, including states of electrical current and voltage parameters, to provide information indicative of parametric states of the batteries of the ESD 74 to the HCP 5. The parametric states of the batteries preferably include battery state-of-charge, battery voltage, battery temperature, and available battery power, referred to as a range PBAT
A brake control module (hereafter ‘BrCM’) 22 is operatively connected to friction brakes (not shown) on each of the vehicle wheels 93. The BrCM 22 monitors the operator input to the brake pedal 112 and generates control signals to control the friction brakes and sends a control signal to the HCP 5 to operate the first and second electric machines 56 and 72 based thereon.
Each of the control modules ECM 23, TCM 17, TPIM 19, BPCM 21, and BrCM 22 is preferably a general-purpose digital computer comprising a microprocessor or central processing unit, storage mediums comprising read only memory (‘ROM’), random access memory (‘RAM’), electrically programmable read only memory (‘EPROM’), a high speed clock, analog to digital (‘A/D’) and digital to analog (‘D/A’) circuitry, and input/output circuitry and devices (‘I/O’) and appropriate signal conditioning and buffer circuitry. Each of the control modules has a set of control algorithms, comprising resident program instructions and calibrations stored in one of the storage mediums and executed to provide the respective functions of each computer. Information transfer between the control modules is preferably accomplished using the LAN bus 6 and serial peripheral interface buses. The control algorithms are executed during preset loop cycles such that each algorithm is executed at least once each loop cycle. Algorithms stored in the non-volatile memory devices are executed by one of the central processing units to monitor inputs from the sensing devices and execute control and diagnostic routines to control operation of the actuators, using preset calibrations. Loop cycles are executed at regular intervals, for example each 3.125, 6.25, 12.5, 25 and 100 milliseconds during ongoing operation of the hybrid powertrain. Alternatively, algorithms may be executed in response to the occurrence of an event.
The exemplary hybrid powertrain selectively operates in one of several operating range states that can be described in terms of an engine state comprising one of an engine-on state (‘ON’) and an engine-off state (‘OFF’), and a transmission state comprising a plurality of fixed gears and continuously variable operating modes, described with reference to Table 1, below.
Each of the transmission operating range states is described in the table and indicates which of the specific clutches C170, C262, C373, and C475 are applied for each of the operating range states. A first continuously variable mode, i.e., EVT Mode 1, or M1, is selected by applying clutch C170 only in order to “ground” the outer gear member of the third planetary gear set 28. The engine state can be one of ON (‘M1_Eng_On’) or OFF (‘M1_Eng_Off’). A second continuously variable mode, i.e., EVT Mode 2, or M2, is selected by applying clutch C262 only to connect the shaft 60 to the carrier of the third planetary gear set 28. The engine state can be one of ON (‘M2_Eng_On’) or OFF (‘M2_Eng_Off’). For purposes of this description, when the engine state is OFF, the engine input speed is equal to zero revolutions per minute (‘RPM’), i.e., the engine crankshaft is not rotating. A fixed gear operation provides a fixed ratio operation of input-to-output speed of the transmission 10, i.e., NI/NO. A first fixed gear operation (‘G1’) is selected by applying clutches C170 and C475. A second fixed gear operation (‘G2’) is selected by applying clutches C170 and C262. A third fixed gear operation (‘G3’) is selected by applying clutches C262 and C475. A fourth fixed gear operation (‘G4’) is selected by applying clutches C262 and C373. The fixed ratio operation of input-to-output speed increases with increased fixed gear operation due to decreased gear ratios in the planetary gears 24, 26, and 28. The rotational speeds of the first and second electric machines 56 and 72, NA and NB respectively, are dependent on internal rotation of the mechanism as defined by the clutching and are proportional to the input speed measured at the input shaft 12.
In response to operator input via the accelerator pedal 113 and brake pedal 112 as captured by the user interface 13, the HCP 5 and one or more of the other control modules determine torque commands to control the torque generative devices comprising the engine 14 and first and second electric machines 56 and 72 to meet the operator torque request at the output member 64 and transferred to the driveline 90. Based upon input signals from the user interface 13 and the hybrid powertrain including the ESD 74, the HCP 5 determines the operator torque request, a commanded output torque from the transmission 10 to the driveline 90, an input torque from the engine 14, clutch torques for the torque-transfer clutches C170, C262, C373, C475 of the transmission 10; and the motor torques for the first and second electric machines 56 and 72, respectively, as is described hereinbelow.
Final vehicle acceleration can be affected by other factors including, e.g., road load, road grade, and vehicle mass. The operating range state is determined for the transmission 10 based upon a variety of operating characteristics of the hybrid powertrain. This includes the operator torque request communicated through the accelerator pedal 113 and brake pedal 112 to the user interface 13 as previously described. The operating range state may be predicated on a hybrid powertrain torque demand caused by a command to operate the first and second electric machines 56 and 72 in an electrical energy generating mode or in a torque generating mode. The operating range state can be determined by an optimization algorithm or routine which determines optimum system efficiency based upon operator demand for power, battery state of charge, and energy efficiencies of the engine 14 and the first and second electric machines 56 and 72. The control system manages torque inputs from the engine 14 and the first and second electric machines 56 and 72 based upon an outcome of the executed optimization routine, and system efficiencies are optimized thereby, to manage fuel economy and battery charging. Furthermore, operation can be determined based upon a fault in a component or system. The HCP 5 monitors the torque-generative devices, and determines the power output from the transmission 10 required in response to the desired output torque at output member 64 to meet the operator torque request. As should be apparent from the description above, the ESD 74 and the first and second electric machines 56 and 72 are electrically-operatively coupled for power flow therebetween. Furthermore, the engine 14, the first and second electric machines 56 and 72, and the electromechanical transmission 10 are mechanically-operatively coupled to transfer power therebetween to generate a power flow to the output member 64.
Boundary conditions of the engine operating points are defined (248). In one embodiment, the boundary conditions define a two-dimensional search area 303 from which a plurality of engine operating points 302 can be provided within the two-dimensional search area 303. The two-dimensional search area 303 is determined based upon the input power PENG
The range of permissible input power values associated with engine input power include input power values [‘Y’] from a minimum permissible input power [‘YMIN’] to a maximum permissible input power [‘YMAX’]. The range of permissible input speed values from the engine 14 include input speed values [‘X’] from a minimum permissible input speed [‘XMIN’] to a maximum permissible input speed [‘XMAX’]. The HCP 5 utilizes the output speed NO of the transmission 10 and the operator torque request TO
The maximum permissible input power YMAX and the minimum permissible input power YMIN are normalized such that the maximum permissible input power YMAX corresponds to a normalized maximum input power [‘yMAX’], which has a value of one, and the minimum permissible input power YMIN corresponds to a normalized minimum permissible input power [‘yMIN’], which has a value of zero. The maximum permissible input speed XMAX and the minimum permissible input speed XMIN are normalized such that the maximum permissible input speed XMAX corresponds to a normalized maximum permissible input speed [‘xMAX’], which has a value of one, and the minimum permissible input speed XMIN corresponds to a normalized minimum permissible input speed [‘xMIN’], which has a value of zero.
In one embodiment each of the engine operating points 302 is a predetermined engine operating point associated with a predetermined coordinate (that is, a predetermined normalized input speed value x and a predetermined normalized input power value y) of the two-dimensional search area 303. The engine operating points 302 are stored in one of the memory devices accessible by the HCP 5. In one embodiment, a distance between each of the engine operating points 302 is spaced at equal increments of normalized input speed x and normalized input power y throughout the two-dimensional search area 303.
The HCP 5 defines search regions within the two-dimensional search area 303. In one embodiment, a single search region comprises the entire area of the two-dimensional search area 303. In one embodiment, more search regions are provided by dividing the two-dimensional search area 303 at normalized input speed values x, at normalized input power values y, or at both normalized input speed values x and normalized input power values y. In one embodiment, the HCP 5 defines search regions by segmenting the two-dimensional search area 303 into three search regions by providing lines at two normalized input speed values. In one embodiment, the HCP 5 defines the search regions by providing a plurality of search regions such that each search region is a rectangle. In one embodiment, the HCP 5 defines search regions such that each search region has an equal area.
The HCP 5 defines the search regions by segmenting the two-dimensional search area 303 into a plurality of search regions comprising search regions 310, 312, 314, 316, 318, 320, 322, 324, and 326.
The HCP 5 determines an engine operating point within each search region 310, 312, 314, 316, 318, 320, 322, 324, and 326. In one embodiment, the HCP 5 determines an engine operating point located at a center of each search region 310, 312, 314, 316, 318, 320, 322, 324, and 326. Each search region includes one of a corresponding first plurality of engine operating point 350, 352, 354, 356, 358, 360 and 362. In one embodiment, each engine operating point is precalibrated and is preassociated with one of the search regions in the memory device. The search region 310 includes the engine operating point 350, the search region 312 includes the engine operating point 352, the search region 314 includes the engine operating point 354, a search region 316 includes the engine operating point 356, a search region 318 includes the engine operating point 358, a search region 320 includes the engine operating point 360, a search region 322 includes the engine operating point 362, a search region 324 includes an engine operating point 364, and a search region 326 includes the engine operating point 366.
The HCP 5 calculates an operating cost PCOST to operate the engine 14 associated with each engine operating point 350, 352, 354, 356, 358, 360, 362, 364, 366 and associated with the operator torque request TO
wherein, NO is the output speed, NA is the operating speed for the first electric machine 56, NB is the operating speed for the second electric machine 72, and b11, b12, b21, b22, are known scalar values determined for the specific application in the specific operating range state. Therefore, the determined scalar values for b11, b12, b21, b22 are specific to each of EVT Mode 1 and EVT Mode 2. In this application, when the transmission output speed, NO is known, there is one degree of freedom in input speed NI, by which NA and NB can be determined.
The HCP 5 determines the torque the relationship as shown in Eq. 2, below:
wherein the TO is the transmission output torque at which is set to the operator torque request TO REQ, TA and TB are the operating torques for MG-A 56 and MG-B 72, {dot over (N)}I and {dot over (N)}O represent time-rate changes in input speed from the engine 14 and output speed of the transmission 10, and d11, d12, d13, d14, d21, d22, d23, d24 are known scalar values determined for each operating range state, i.e., either one of EVT Mode 1 and EVT Mode 2, of the application. In this application, when the transmission output torque TO is known, there is one degree of torque freedom for input torque TI, by which TA and TB can be determined.
The HCP 5 denormalizes each engine operating point of the first plurality of engine operating points to their corresponding input speed and input power values (X,Y) using scaling based on normalization. The HCP 5 inputs the operator torque request TO
The HCP 5 calculates a cost PCOST352, a cost PCOST354, a cost PCOST356, a cost PCOST358, a cost PCOST360, a cost PCOST362, a cost PCOST364, and a cost PCOST366 for the corresponding engine operating points 352, 354, 356, 358, 360, 362, 364, respectively. The HCP 5 performs a base point determination by determining which of the cost PCOST352, the cost PCOST354, the cost PCOST356, or the cost PCOST358, the cost PCOST360, the cost PCOST362, the cost PCOST364, and the cost PCOST366 has the lowest value, and determines the engine operating point associated with the lowest value as a base point of the first plurality of engine operating points.
The HCP 5 segments the search region 310 into a first plurality of subregions utilizing the search engine 250 based on normalized input speeds x. In one embodiment, the HCP 5 divides the search region 310, into a first plurality of subregions comprising a subregion 328, a subregion 330, and a subregion 332. The HCP 5 determines an engine operating point within each of the subregions of the first plurality of subregions. In one embodiment, the HCP 5 determines an engine operating point located at a geometric center of each of the subregions. In one embodiment, each of the subregions of the first plurality of subregions includes one of a second plurality of engine operating points comprising engine operating points 350, 368, and 370. In one embodiment, the subregion 328, the subregion 330 and the subregion 332 have a rectangular shape. In one embodiment, the subregion 328 includes the engine operating point 368, the subregion 330 includes the engine operating point 350, and the subregion 332 includes the engine operating point 370.
The HCP 5 executes the cost function 252 to calculate a cost PCOST associated with each engine operating point of the second plurality of engine operating points. The HCP 5 calculates a third plurality of cost values comprising a cost PCOST368 and a cost PCOST370 for the engine operating point 368, and the engine operating point 370, respectively. The HCP 5 performs the base point determination by determining which of the cost PCOST368, the cost PCOST370, or the cost PCOST350 has the lowest value, and determines the engine operating point associated with the lowest value as the base point of the second plurality of engine operating points.
The HCP 5 segments the subregion 330 into a second plurality of subregions based on the normalized input power y. In one embodiment, the HCP 5 divides the subregion 330 into subregions 334, 336, and 338. In one embodiment, subregions 334, 336 and 338 have a rectangular shape. In one embodiment, the subregions 334, 336, and 338 are orthogonal to the first plurality of subregions. In one embodiment, the subregion 334 includes the engine operating point 372, the subregion 336 includes the engine operating point 350, and the subregion 338 includes the engine operating point 374. A third plurality of engine operating points includes engine operating points 350, 372, and 374.
The HCP 5 executes the cost function 252 to calculate a cost PCOST associated with each engine operating point of the third plurality of engine operating points. The HCP 5 calculates a cost PCOST372 and a cost PCOST374 for the engine operating point 372, and the engine operating point 374, respectively. The HCP 5 performs the base point determination by determining which of the cost PCOST372, the cost PCOST350, or the cost PCOST374 has the lowest value, and determines the engine operating point associated with the lowest value as the base point of the third plurality of engine operating points.
The HCP 5 determines a third plurality of subregions comprising subregions 340, 342, and 344 based on the engine operating point 350. The HCP 5 determines a cost PCOST376 for an engine operating point 376 in subregion 340, a cost PCOST378 for an engine operating point 378 for engine operating point 378 in subregion 344. The HCP 5 performs the base point determination by determining which of the cost PCOST372, the cost PCOST374, or the cost PCOST378 has the lowest value, and determines the engine operating point associated with the lowest value as the base point for the fourth plurality of engine operating points.
The HCP 5 determines a fourth plurality of subregions comprising a subregion 346, a subregion 348, and a subregion 349 based on the engine operating point 376. The HCP 5 determines a cost PCOST380 for an engine operating point 380 in subregion 346, and a cost PCOST382 for an engine operating point 382 in subregion 340. The HCP 5 performs the base point determination by determining which of the cost PCOST380, the cost PCOST376, or the cost PCOST382 has the lowest value, and determines the engine operating point associated with the lowest value as the base point for the fifth plurality of engine operating points.
The HCP 5 continues to utilize the search engine 250 and the cost function 252 until a selected number of costs are calculated, or a predetermined number of iterations are executed. Although, the predetermined number iterations can be determined based on a desired search resolution or a desired search speed, in one embodiment, ten iterations are performed. In one embodiment, eleven iterations are performed. In one embodiment, the HCP 5 calculates 100 cost values. In one embodiment, the HCP 5 calculates 30 cost values. The HCP 5 determines a preferred engine operating point within the iteratively identified subregion (that is, the subregion identified as having a engine operating point with a lowest cost PCOST after a predetermined number iterations) having the minimum operating cost to meet the operator torque request. The preferred engine operating points associated with an optimal speed value XOPT and an optimal input power value YOPT.
The HCP 5 utilizing the method 200 to calculate cost values PCOST rapidly due to the separation of the search engine 250 and the cost function 252. In particular, the search engine 250 determines pluralities of engine operating points and provides each plurality of engine operating points to the cost function 252 such that the cost function 252 of cost only has to solve for one unknown variable per engine operating point. The HCP 5 utilizing the method 200 to calculate twenty-eight cost values in less than twenty-five milliseconds.
In alternative embodiments, the HCP 5 performs other amounts of cost calculations. Further, in other alternative embodiments, the HCP 5 performs cost calculations until a selected amount of time elapses or until a selected search tolerance level is reached.
The powertrain is controlled based on the optimal engine operating point as determined by the search engine 250 and the cost function 252. The values for XOPT, YOPT are translated to an optimal input speed NI
As mentioned above, the HCP 5 utilizes the method 200 to control the transmission 10 in the first or second continuously variable modes. The HCP 5 controls the input speed and input torque of the engine utilizing Eqs. 1 and 2 as described wherein the input speed NI is set to the optimal input speed NI
The disclosure has described certain preferred embodiments and modifications thereto. Further modifications and alterations may occur to others upon reading and understanding the specification. Therefore, it is intended that the disclosure not be limited to the particular embodiment(s) disclosed as the best mode contemplated for carrying out this disclosure, but that the disclosure will include all embodiments falling within the scope of the appended claims.
This application claims the benefit of U.S. Provisional Application No. 60/985,257 filed on Nov. 4, 2007 which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
6832148 | Bennett | Dec 2004 | B1 |
6868318 | Cawthorne | Mar 2005 | B1 |
7154236 | Heap | Dec 2006 | B1 |
20050076958 | Foster | Apr 2005 | A1 |
20050077867 | Cawthorne | Apr 2005 | A1 |
20050077877 | Cawthorne | Apr 2005 | A1 |
20050080523 | Bennett | Apr 2005 | A1 |
20050080527 | Tao | Apr 2005 | A1 |
20050080535 | Steinmetz | Apr 2005 | A1 |
20050080537 | Cawthorne | Apr 2005 | A1 |
20050080538 | Hubbard | Apr 2005 | A1 |
20050080539 | Hubbard | Apr 2005 | A1 |
20050080540 | Steinmetz | Apr 2005 | A1 |
20050080541 | Sah | Apr 2005 | A1 |
20050182526 | Hubbard | Aug 2005 | A1 |
20050182543 | Sah | Aug 2005 | A1 |
20050182546 | Hsieh | Aug 2005 | A1 |
20050182547 | Sah | Aug 2005 | A1 |
20050189918 | Weisgerber | Sep 2005 | A1 |
20050252283 | Heap | Nov 2005 | A1 |
20050252305 | Hubbard | Nov 2005 | A1 |
20050252474 | Sah | Nov 2005 | A1 |
20050255963 | Hsieh | Nov 2005 | A1 |
20050255964 | Heap | Nov 2005 | A1 |
20050255965 | Tao | Nov 2005 | A1 |
20050255966 | Tao | Nov 2005 | A1 |
20050255967 | Foster | Nov 2005 | A1 |
20050255968 | Sah | Nov 2005 | A1 |
20050256617 | Cawthorne | Nov 2005 | A1 |
20050256618 | Hsieh | Nov 2005 | A1 |
20050256623 | Hubbard | Nov 2005 | A1 |
20050256625 | Sah | Nov 2005 | A1 |
20050256626 | Hsieh | Nov 2005 | A1 |
20050256627 | Sah | Nov 2005 | A1 |
20050256629 | Tao | Nov 2005 | A1 |
20050256631 | Cawthorne | Nov 2005 | A1 |
20050256633 | Heap | Nov 2005 | A1 |
20050256919 | Cawthorne | Nov 2005 | A1 |
20060194670 | Heap | Aug 2006 | A1 |
20070078580 | Cawthorne | Apr 2007 | A1 |
20070093953 | Heap | Apr 2007 | A1 |
20070149348 | Holmes | Jun 2007 | A1 |
20070191181 | Burns | Aug 2007 | A1 |
20070225886 | Morris | Sep 2007 | A1 |
20070225887 | Morris | Sep 2007 | A1 |
20070225888 | Morris | Sep 2007 | A1 |
20070225889 | Morris | Sep 2007 | A1 |
20070260381 | Sah | Nov 2007 | A1 |
20070276569 | Sah | Nov 2007 | A1 |
20070284162 | Zettel | Dec 2007 | A1 |
20070284163 | Heap | Dec 2007 | A1 |
20070284176 | Sah | Dec 2007 | A1 |
20070285059 | Zettel | Dec 2007 | A1 |
20070285060 | Zettel | Dec 2007 | A1 |
20070285061 | Zettel | Dec 2007 | A1 |
20070285063 | Zettel | Dec 2007 | A1 |
20070285097 | Zettel | Dec 2007 | A1 |
20080004779 | Sah | Jan 2008 | A1 |
20080028879 | Robinette | Feb 2008 | A1 |
20080032855 | Sah | Feb 2008 | A1 |
20080064559 | Cawthorne | Mar 2008 | A1 |
20080064562 | Aettel | Mar 2008 | A1 |
20080103003 | Sah | May 2008 | A1 |
20080119320 | Wu | May 2008 | A1 |
20080119321 | Heap | May 2008 | A1 |
20080120000 | Heap | May 2008 | A1 |
20080120001 | Heap | May 2008 | A1 |
20080120002 | Heap | May 2008 | A1 |
20080176706 | Wu | Jul 2008 | A1 |
20080176709 | Wu | Jul 2008 | A1 |
20080181280 | Wang | Jul 2008 | A1 |
20080182696 | Sah | Jul 2008 | A1 |
20080183372 | Snyder | Jul 2008 | A1 |
20080234097 | Sah | Sep 2008 | A1 |
20080236921 | Huseman | Oct 2008 | A1 |
20080243346 | Huseman | Oct 2008 | A1 |
20080249745 | Heap | Oct 2008 | A1 |
20080262694 | Heap | Oct 2008 | A1 |
20080262698 | Lahti | Oct 2008 | A1 |
20080272717 | Gleason | Nov 2008 | A1 |
20080275611 | Snyder | Nov 2008 | A1 |
20080275624 | Snyder | Nov 2008 | A1 |
20080275625 | Snyder | Nov 2008 | A1 |
20080287255 | Snyder | Nov 2008 | A1 |
20090069148 | Heap | Mar 2009 | A1 |
20090069989 | Heap | Mar 2009 | A1 |
20090070019 | Heap | Mar 2009 | A1 |
20090082170 | Heap | Mar 2009 | A1 |
20090088294 | West | Apr 2009 | A1 |
20090105039 | Sah | Apr 2009 | A1 |
20090105896 | Tamai | Apr 2009 | A1 |
20090105898 | Wu | Apr 2009 | A1 |
20090105914 | Buur | Apr 2009 | A1 |
20090107745 | Buur | Apr 2009 | A1 |
20090107755 | Kothari | Apr 2009 | A1 |
20090108673 | Wang | Apr 2009 | A1 |
20090111637 | Day | Apr 2009 | A1 |
20090111640 | Buur | Apr 2009 | A1 |
20090111642 | Sah | Apr 2009 | A1 |
20090111643 | Sah | Apr 2009 | A1 |
20090111644 | Kaminsky | Apr 2009 | A1 |
20090111645 | Heap | Apr 2009 | A1 |
20090112385 | Heap | Apr 2009 | A1 |
20090112392 | Buur | Apr 2009 | A1 |
20090112399 | Buur | Apr 2009 | A1 |
20090112412 | Cawthorne | Apr 2009 | A1 |
20090112416 | Heap | Apr 2009 | A1 |
20090112417 | Kaminsky | Apr 2009 | A1 |
20090112418 | Buur | Apr 2009 | A1 |
20090112419 | Heap | Apr 2009 | A1 |
20090112420 | Buur | Apr 2009 | A1 |
20090112421 | Sah | Apr 2009 | A1 |
20090112422 | Sah | Apr 2009 | A1 |
20090112423 | Foster | Apr 2009 | A1 |
20090112427 | Heap | Apr 2009 | A1 |
20090112428 | Sah | Apr 2009 | A1 |
20090112429 | Sah | Apr 2009 | A1 |
20090112495 | Center | Apr 2009 | A1 |
20090115349 | Heap | May 2009 | A1 |
20090115350 | Heap | May 2009 | A1 |
20090115351 | Heap | May 2009 | A1 |
20090115352 | Heap | May 2009 | A1 |
20090115353 | Heap | May 2009 | A1 |
20090115354 | Heap | May 2009 | A1 |
20090115365 | Heap | May 2009 | A1 |
20090115373 | Kokotovich | May 2009 | A1 |
20090115377 | Schwenke | May 2009 | A1 |
20090115408 | West | May 2009 | A1 |
20090115491 | Anwar | May 2009 | A1 |
20090118074 | Zettel | May 2009 | A1 |
20090118075 | Heap | May 2009 | A1 |
20090118076 | Heap et al. | May 2009 | A1 |
20090118077 | Hsieh | May 2009 | A1 |
20090118078 | Wilmanowicz | May 2009 | A1 |
20090118079 | Heap | May 2009 | A1 |
20090118080 | Heap | May 2009 | A1 |
20090118081 | Heap | May 2009 | A1 |
20090118082 | Heap | May 2009 | A1 |
20090118083 | Kaminsky | May 2009 | A1 |
20090118084 | Heap | May 2009 | A1 |
20090118085 | Heap | May 2009 | A1 |
20090118086 | Heap | May 2009 | A1 |
20090118087 | Hsieh | May 2009 | A1 |
20090118089 | Heap | May 2009 | A1 |
20090118090 | Heap | May 2009 | A1 |
20090118091 | Lahti | May 2009 | A1 |
20090118093 | Heap | May 2009 | A1 |
20090118094 | Hsieh | May 2009 | A1 |
20090118877 | Center | May 2009 | A1 |
20090118879 | Heap | May 2009 | A1 |
20090118880 | Heap | May 2009 | A1 |
20090118882 | Heap | May 2009 | A1 |
20090118883 | Heap | May 2009 | A1 |
20090118884 | Heap | May 2009 | A1 |
20090118885 | Heap | May 2009 | A1 |
20090118886 | Tamai | May 2009 | A1 |
20090118887 | Minarcin | May 2009 | A1 |
20090118888 | Minarcin | May 2009 | A1 |
20090118901 | Cawthorne | May 2009 | A1 |
20090118914 | Schwenke | May 2009 | A1 |
20090118915 | Heap | May 2009 | A1 |
20090118916 | Kothari | May 2009 | A1 |
20090118917 | Sah | May 2009 | A1 |
20090118918 | Heap | May 2009 | A1 |
20090118919 | Heap | May 2009 | A1 |
20090118920 | Heap | May 2009 | A1 |
20090118921 | Heap | May 2009 | A1 |
20090118922 | Heap | May 2009 | A1 |
20090118923 | Heap | May 2009 | A1 |
20090118924 | Heap | May 2009 | A1 |
20090118925 | Hsieh | May 2009 | A1 |
20090118926 | Heap | May 2009 | A1 |
20090118927 | Heap | May 2009 | A1 |
20090118928 | Heap | May 2009 | A1 |
20090118929 | Heap | May 2009 | A1 |
20090118930 | Heap | May 2009 | A1 |
20090118931 | Kaminsky | May 2009 | A1 |
20090118932 | Heap | May 2009 | A1 |
20090118933 | Heap | May 2009 | A1 |
20090118934 | Heap | May 2009 | A1 |
20090118935 | Heap | May 2009 | A1 |
20090118936 | Heap | May 2009 | A1 |
20090118937 | Heap | May 2009 | A1 |
20090118938 | Heap | May 2009 | A1 |
20090118939 | Heap | May 2009 | A1 |
20090118940 | Heap | May 2009 | A1 |
20090118941 | Heap | May 2009 | A1 |
20090118942 | Hsieh | May 2009 | A1 |
20090118943 | Heap | May 2009 | A1 |
20090118944 | Heap | May 2009 | A1 |
20090118945 | Heap | May 2009 | A1 |
20090118946 | Heap | May 2009 | A1 |
20090118947 | Heap | May 2009 | A1 |
20090118948 | Heap | May 2009 | A1 |
20090118949 | Heap | May 2009 | A1 |
20090118950 | Heap | May 2009 | A1 |
20090118951 | Heap | May 2009 | A1 |
20090118952 | Heap | May 2009 | A1 |
20090118954 | Wu | May 2009 | A1 |
20090118957 | Heap | May 2009 | A1 |
20090118962 | Heap | May 2009 | A1 |
20090118963 | Heap | May 2009 | A1 |
20090118964 | Snyder | May 2009 | A1 |
20090118969 | Heap | May 2009 | A1 |
20090118971 | Heap | May 2009 | A1 |
20090144002 | Zettel | Jun 2009 | A1 |
Number | Date | Country | |
---|---|---|---|
20090118999 A1 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60985257 | Nov 2007 | US |