This disclosure is related to powertrain control within hybrid vehicles.
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, electro-mechanical 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.
A method to determine a preferred operating point for an internal combustion engine mechanically coupled to an electro-mechanical transmission to transmit power to a driveline in response to an operator torque request includes determining a current set of candidate operating points for a current search iteration. The method further includes iteratively determining an operating cost for operating the internal combustion engine at each candidate operating point of the current search iteration, iteratively determining a candidate operating point for the current search iteration having a lowest operating cost, iteratively determining a search direction relative to the current set of candidate operating points for the current search iteration based on the candidate operating point of the current search iteration having the lowest operating cost, and iteratively determining a subsequent set of candidate operating points for a subsequent search iteration based upon the search direction. The preferred operating point for operating the internal combustion engine is determined comprising the candidate operating point with the lowest operating cost determined after a predetermined number of search iterations.
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 NI 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 electro-mechanical transmission 10 are mechanically-operatively coupled to transfer power therebetween to generate a power flow to the output member 64.
Boundary conditions comprising a range of permissible input power values associated with the engine operating points are defined (210, 248). The boundary conditions define a two-dimensional search area 303. The two-dimensional search area 303 is determined based upon the input power PI transmitted from the engine 14 to the transmission 10. In an exemplary embodiment, the two-dimensional search area 303 comprises a range of permissible input power values from −1 kW to 40 kW and a range of permissible input speed values from 600 RPM to 2000 RPM. In alternate embodiments, the two-dimensional search area 303 comprises one of a range of permissible input speed values and a range of permissible input torque values and a range of permissible input power values and the range of permissible input torque values.
The range of permissible input power values are 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 12 and the operator torque request TO
The maximum permissible input power YMAX and the minimum permissible input power YMIN are normalized (212) 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 (212) 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.
The HCP 5 iteratively identifies operating points within the search area 303 (214). The operating points include x/y coordinates in which x values correspond to normalized speed values and y values correspond to normalized power values. The HCP 5 identifies a first set of candidate operating points including an operating point 302, an operating point 304, an operating point 306, and an operating point 308.
In one embodiment, the HCP 5 determines the first set of candidate operating points such that the candidate operating points define corners of a rectangle 301, and the rectangle 301 is centered within the search area 303. The rectangle 301 can have a length and width that is off-line optimized based on specific cost functions, allowed maximum iteration number, and desired search accuracy.
The HCP 5 denormalizes each candidate operating point (x,y) of the first set of candidate operating points to their corresponding values (X,Y) using scaling based on normalization (216). The HCP 5 calculates an operating cost PCOST to operate the engine 14 associated with each candidate engine operating point 302, 304, 306, 308 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 using the relationship as shown in Eq. 2, below:
wherein the output torque TO of the transmission 10 is set to the operator torque request TO
The cost function f(X,Y) 252 comprises operating costs which are generally determined based upon factors that include vehicle driveability, fuel economy, emissions, and battery usage. Furthermore, costs are assigned and associated with fuel and electrical power consumption and are further associated with a specific operating points of the powertrain. Lower operating costs are generally associated with lower fuel consumption at high conversion efficiencies, lower battery power usage, and lower emissions for an operating point, and closer proximity to the current operating state of the powertrain system.
The HCP 5 calculates a cost PCOST302, a cost PCOST304, a cost PCOST306, and a cost PCOST308 for the corresponding operating points 302, 304, 306, 308, respectively. The HCP 5 performs a base point determination by determining which of the costs PCOST302, PCOST304, PCOST306, PCOST308 has the lowest value, and determines the point associated with the lowest value as the a base point for the first set of operating points.
The HCP 5 determines a second set of candidate operating points (220) utilizing the search engine 250. In an exemplary embodiment, the search engine 250 selects a search direction relative to the first set of candidate operating points based on the base point by extending the search direction from the base point away from the first set of operating points. The HCP 5 determines the second set of operating points including candidate operating points 310, 312, and 314 along with the candidate operating point 306, which was the base point for the first set of candidate operating points. The second set of candidate operating points defines a rectangle 311 having a common corner at the candidate operating point 306 with the rectangle 301 of the first set of candidate operating points.
In one embodiment, the rectangle 311 is smaller than the rectangle 301 such that search resolution increases between the first set of candidate operating points and the second set of candidate operating points. In one embodiment, each side of the rectangle 311 is a fraction of the length of corresponding side of the rectangle 301.
The HCP 5 denormalizes the operating points (x,y) of the second set of candidate operating points to their corresponding speed and power values (X,Y) 216. The HCP 5 inputs the speed and power values (X,Y) of the second set of operating points into a cost function f(X,Y). The HCP 5 calculates a cost PCOST310, a cost PCOST312, and a cost PCOST314 for operating points 310, 312, 314, respectively. The HCP 5 performs a base point determination by determining which of the costs PCOST310, PCOST312, PCOST314, PCOST306 have the lowest value, and determines the point associated with the lowest value as the a base point for the second set of candidate operating points.
The HCP 5 utilizes the cost function 252 and the search engine 250 to iteratively determine sets of candidate operating points based on the base point of each previously determined set of candidate operating points. The HCP 5 utilizes search engine 250 to identify a third set of candidate operating points comprising operating points 318, 320, 322, along with candidate operating point 310, which is the previously determined base point. The third set of candidate operating points defines corners of a rectangle 321. The search engine 250 identifies a fourth set of candidate operating points comprising candidate operating points 324, 326, 328, along with candidate operating point 310 which is the previously determined base point. The fourth set of candidate operating points defines corners of a rectangle 331. The search engine 250 identifies a fifth set of candidate operating points comprising candidate operating points 330, 332, 334, along with candidate operating point 310, which is the previous determined base point. The fifth set of candidate operating points defines corners of a fifth rectangle 341.
When the HCP 5 evaluates three consecutive sets of candidate operating points, and determines that the base point in each set of candidate operating points is the same, the HCP 5 determines a sixth set of candidate operating points utilizing rectangles having a common side to a previously determined rectangle. In one embodiment, the HCP 5 determines a sixth set of candidate operating points comprising candidate operating point 336 and candidate operating point 338. The candidate operating point 338 defines a corner of a rectangle 343 opposite a corner of the rectangle 343 defined by the candidate operating point 310. The rectangle 343 comprises a rectangle having the same shape and size as the previously determined rectangle 341 and shares a common side and with the rectangle 341 (that is, a side defined by candidate operating point 310 and candidate operating point 332). The candidate operating point 336 defines a corner of a rectangle 345 opposite to a corner of the rectangle 345 defined by the candidate operating point 310. The rectangle 345 comprises a rectangle having the same shape and size as the previously determined rectangle 341 and shares a common side and with the rectangle 341 (that is, a side defined by operating point 310 and candidate operating point 334).
The HCP 5 denormalizes each operating point (x,y) of the sixth set of candidate operating points to their corresponding engine speed and engine power values (X,Y) (216). The HCP 5 inputs the speed and power values (X,Y) of the sixth set of operating points into a cost function f(X,Y) 252 to determine the overall cost PCOST (218).
The HCP 5 calculates a cost PCOST336, and a cost PCOST338 for operating points 336, 338, respectively. The HCP 5 performs a base point determination by determining which of the cost PCOST310, the cost PCOST336, the cost PCOST338, and the cost PCOST310 has the lowest value, and determines the point associated with the lowest value as the a base point for the sixth set of operating points.
The search engine 214 determines a seventh set of candidate operating points comprising candidate operating points 340, 342, 344 along with the candidate operating point 336. The seventh set of candidate operating points define a rectangle 351 extending away from the candidate operating point 310.
The HCP 5 identifies a fourth set of candidate operating points (220) utilizing the search engine 250. The HCP 5 selects a set of candidate operating points for the fourth set of candidate operating points including operating points 320, point 370, 372, 374. However, candidate operating points 372 and candidate operating point 374 have a normalized input speed value x outside the permissible range of normalized speed values 307 (that is a value x that is less than xMIN.) The HCP 5 sets the normalized input speed value x for candidate operating points 372 and 374 to the minimum permissible input speed xMIN, thereby determining new candidate operating points 378 and 380. The HCP 5 identifies a fourth set of candidate operating point including the operating point 320, the operating point 370, the operating point 378, and the operating point 380.
The HCP 5 calculates a cost PCOST370, a cost PCOST378, and a cost PCOST380 for candidate operating points 370, 378380, respectively. The HCP 5 performs a base point determination by determining which of the cost PCOST320, the cost PCOST370, the cost PCOST378, and the cost PCOST380 has the lowest value, and determines the point associated with the lowest value as the a base point for the fourth set of candidate operating points.
When the HCP 5, determines a base point comprising a limit value, that is either minimum permissible input speed xMIN, maximum permissible input speed xMAX, minimum permissible input power yMIN, or maximum permissible input power yMAX, the HCP 5 determines a set of candidate operating points such that the set of candidate operating points rebound away from the search limit. The HCP 5 selects a fifth set of candidate operating points comprising the candidate operating point 378, the candidate operating point 382, the candidate operating point 388, and the candidate operating point 390. The fifth set of candidate operating points defines a rectangle 383. Further, when the base point includes a limit value, the HCP 5 selects candidate operating points to form a rectangle having two sides with an increased length over the length associated with the rectangle of a current set of candidate operating points. For example, the distance between the candidate operating point 378 and the candidate operating point 380, and the distance between the candidate operating point 382 and the candidate operating point 388 are greater than the space normally associated with candidate operating points of a fifth set of candidate operating points in x direction, thereby allowing the search engine 250 to evaluate candidate operating points away from the boundary of the minimum permissible input power xMIN.
The HCP 5 continues to perform steps 216, 218, and 220 until a selected number of iterations are performed (222). In one exemplary embodiment nine iterations are performed.
In one embodiment, the HCP 5 calculates costs until a selected number of costs are calculated. In one embodiment, the HCP 5 calculates costs for twenty-eight candidate operating points. The candidate operating point associated with the lowest cost after the selected number of costs are calculated is an preferred operating point associated with the preferred speed value XOPT and the preferred power value YOPT.
The HCP 5 utilizing the method 200 determines the normalized preferred speed value xOPT and a normalized preferred power value yOPT rapidly due to the separation of the search engine 250 and the cost function 252. In particular, the search engine 250 rapidly determines sets of candidate operating points and provides each set of candidate operating points to the cost function 252 such that the cost function 252 only has to solve for one unknown variable per candidate operating point. The HCP 5 utilizing the method 200 calculates 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.
In alternative exemplary embodiments, the search engine can utilize other types of search functions. In one embodiment, a search engine iteratively generates combinations of inputs over the entire range of permissible input torques TI
In one embodiment, a search engine selects initial values for input torque and input speed that have a golden ratio of relative ranges of a search area, determines costs associated with the initial values input torque and input speeds and exclude certain search area (that is, decreasing the size of the permissible search area) based on the output costs.
In other embodiments, the search engine determines candidate operating points that define corners a geometric shape (such as, for example, a square or a triangle). The search engine evaluates costs based on torque values and speed values associated with each operating point. The search engine then utilizes the operating points to define new corners of a second shape. The second shape differs from the first shape by at least one of size, rotational orientation, location or number of corners, or angles of corners.
The intermediate results (for example various components of the preferred cost) associated with XOPT, YOPT are recorded (224) for implementation by instrumentation and in system diagnostics. In one embodiment, intermediate results associated with XOPT, YOPT are accessed during vehicle diagnostics to determine if the algorithm is selecting preferred engine operating points.
The powertrain is controlled based on the preferred operating point (xOPT, yOPT) (226) as determined by the search engine 250 and the cost function 252. The values for XOPT is correlated with preferred engine 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,984 filed on Nov. 7, 2007 which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
6173574 | Obayashi et al. | Jan 2001 | B1 |
6400993 | Oberg | Jun 2002 | B1 |
6594575 | Pflugl et al. | Jul 2003 | B2 |
6671603 | Cari et al. | Dec 2003 | B2 |
6832148 | Bennett | Dec 2004 | B1 |
6868318 | Cawthorne | Mar 2005 | B1 |
6957137 | Hubbard et al. | Oct 2005 | B2 |
7076356 | Hubbard et al. | Jul 2006 | B2 |
7110871 | Hubbard et al. | Sep 2006 | B2 |
7154236 | Heap | Dec 2006 | B1 |
7398147 | Kozarekar et al. | Jul 2008 | B2 |
7801662 | Kozarekar et al. | Sep 2010 | B2 |
8041495 | Kozarekar et al. | Oct 2011 | B2 |
8079933 | Kaminsky et al. | Dec 2011 | B2 |
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 et al. | 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 |
20070202987 | Kakinami et al. | 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 | Zettel | 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 | 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 et al. | 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 et al. | 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 et al. | 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 |
20090118999 | Heap | May 2009 | A1 |
20090144002 | Zettel | Jun 2009 | A1 |
Number | Date | Country |
---|---|---|
0 365 003 | Apr 1990 | EP |
Entry |
---|
Nocedal et al., Numerical Optimization, 2006, Springer Science+Business Media LLC, 2nd Edition, pp. 1-29, 66-100. |
Number | Date | Country | |
---|---|---|---|
20090118927 A1 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60985984 | Nov 2007 | US |