This disclosure relates generally to control systems for electro-mechanical transmissions.
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 for decreasing the size of a space from within which a two-dimensional search engine selects points defined by numerical pairs for evaluation, the space including at least one two-dimensional first region, the first region having minimum and maximum abscissa and ordinate values associated with it, includes generating a plurality of contour plots, the contour plots having abscissa and ordinate axes, and including contours which are representative of a property associated with points within the first region bounded by the abscissa and ordinate axes, selecting a second region from each of the contour plots, the second regions each comprising minimum and maximum abscissa values and minimum and maximum ordinate values, providing four tables of data, the data in each table of the four tables including one of four variables selected from the group consisting of: the minimum abscissa value, the maximum abscissa value, the minimum ordinate value, and the maximum ordinate value, providing a two-dimensional input request, extracting a value for each of the minimum abscissa value, the maximum abscissa value, the minimum ordinate value, and the maximum ordinate value from the tables, to provide extracted values based upon the input request, and defining a search space based on the extracted values.
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,
In one embodiment, the exemplary engine 14 comprises a multi-cylinder internal combustion engine which is selectively operative in several states to transmit 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 is preferably present to monitor rotational speed of the input shaft 12. Power output from the engine 14, comprising rotational speed and output torque, can differ from the input speed, NI, and the input torque, TI, to the transmission 10 due to torque-consuming components being present on or in operative mechanical contact with 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).
In one embodiment the exemplary transmission 10 comprises three planetary-gear sets 24, 26 and 28, and four selectively-engageable torque-transmitting devices, i.e., clutches C1 70, C2 62, C3 73, and C4 75. 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. In one embodiment, clutches C2 62 and C4 75 preferably comprise hydraulically-applied rotating friction clutches. In one embodiment, clutches C1 70 and C3 73 preferably comprise hydraulically-controlled stationary devices that can be selectively grounded to a transmission case 68. In a preferred embodiment, each of the clutches C1 70, C2 62, C3 73, and C4 75 is preferably hydraulically applied, selectively receiving pressurized hydraulic fluid via the hydraulic control circuit 42.
In one embodiment, 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 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, e.g., to vehicle wheels 93, one of which is shown in
The input torques from the engine 14 and 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. 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, in response to torque commands for the first and second electric machines 56 and 72 to achieve the input torques TA and TB. Electrical current is transmitted to and from the ESD 74 in accordance with commands provided to the TPIM which derive from such factors as including operator torque requests, current operating conditions and states, and such commands determine whether the ESD 74 is being charged, discharged or is in stasis at any given instant.
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 achieve the input 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, depending on commands received which are typically based on factors which include current operating state and operator torque demand.
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 such as 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 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 powertrain, including the ESD 74, the HCP 5 generates various commands, including: the operator torque request (‘TO
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 which may include without limitation: a manifold pressure, engine coolant temperature, throttle position, 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, which may include without limitation actuators such as: 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., C1 70, C2 62, C3 73, and C4 75, 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 C1 70, C2 62, C3 73, and C4 75 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
Each of the control modules ECM 23, TCM 17, TPIM 19 and BPCM 21 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 preferably executed at regular intervals, for example at each 3.125, 6.25, 12.5, 25 and 100 milliseconds during ongoing operation of the powertrain. However, any interval between about 2 milliseconds and about 300 milliseconds may be selected. Alternatively, algorithms may be executed in response to the occurrence of any selected event.
The exemplary powertrain shown in reference to
Each of the transmission operating range states is described in the table and indicates which of the specific clutches C1 70, C2 62, C3 73, and C4 75 are applied for each of the operating range states. As an example, a first continuously variable mode, i.e., EVT Mode 1, or M1, is selected by applying clutch C1 70 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 C2 62 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, is achieved. For example, a first fixed gear operation (‘G1’) is selected by applying clutches C1 70 and C4 75. A second fixed gear operation (‘G2’) is selected by applying clutches C1 70 and C2 62. A third fixed gear operation (‘G3’) is selected by applying clutches C2 62 and C4 75. A fourth fixed gear operation (‘G4’) is selected by applying clutches C2 62 and C3 73. 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 the 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, the input torque from the engine 14, clutch torques for the torque-transfer clutches C1 70, C2 62, C3 73, C4 75 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 engine state and the transmission operating range state are determined based upon 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 transmission operating range state and the engine 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 transmission operating range state and the engine 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 at output member 64 that is required to meet the operator torque request while meeting other powertrain operating demands, e.g., charging the ESD 74. 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.
In operation, the operator inputs to the accelerator pedal 113 and the brake pedal 112 are monitored to determine the operator torque request. The operator inputs to the accelerator pedal 113 and the brake pedal 112 comprise individually determinable operator torque request inputs including an immediate accelerator output torque request (‘Output Torque Request Accel Immed’), a predicted accelerator output torque request (‘Output Torque Request Accel Prdtd’), an immediate brake output torque request (‘Output Torque Request Brake Immed’), a predicted brake output torque request (‘Output Torque Request Brake Prdtd’) and an axle torque response type (‘Axle Torque Response Type’). As used herein, the term ‘accelerator’ refers to an operator request for forward propulsion preferably resulting in increasing vehicle speed over the present vehicle speed, when the operator selected position of the transmission gear selector 114 commands operation of the vehicle in the forward direction. The terms ‘deceleration’ and ‘brake’ refer to an operator request preferably resulting in decreasing vehicle speed from the present vehicle speed. The immediate accelerator output torque request, the predicted accelerator output torque request, the immediate brake output torque request, the predicted brake output torque request, and the axle torque response type are individual inputs to the control system. Additionally, operation of the engine 14 and the transmission 10 are monitored to determine the input speed (‘Ni’) and the output speed (‘No’). The immediate accelerator output torque request is determined based upon a presently occurring operator input to the accelerator pedal 113, and comprises a request to generate an immediate output torque at the output member 64 preferably to accelerate the vehicle. The predicted accelerator output torque request is determined based upon the operator input to the accelerator pedal 113 and comprises an optimum or preferred output torque at the output member 64. The predicted accelerator output torque request is preferably equal to the immediate accelerator output torque request during normal operating conditions, e.g., when any one of antilock braking, traction control, or vehicle stability is not being commanded. When any one of antilock braking, traction control or vehicle stability is being commanded the predicted accelerator output torque request remains the preferred output torque with the immediate accelerator output torque request being decreased in response to output torque commands related to the antilock braking, traction control, or vehicle stability control.
The immediate brake output torque request is determined based upon a presently occurring operator input to the brake pedal 112, and comprises a request to generate an immediate output torque at the output member 64 to effect a reactive torque with the driveline 90 which preferably decelerates the vehicle. The predicted brake output torque request comprises an optimum or preferred brake output torque at the output member 64 in response to an operator input to the brake pedal 112 subject to a maximum brake output torque generated at the output member 64 allowable regardless of the operator input to the brake pedal 112. In one embodiment the maximum brake output torque generated at the output member 64 is limited to −0.2 g. The predicted brake output torque request can be phased out to zero when vehicle speed approaches zero regardless of the operator input to the brake pedal 112. When commanded by the operator, there can be operating conditions under which the predicted brake output torque request is set to zero, e.g., when the operator setting to the transmission gear selector 114 is set to a reverse gear, and when a transfer case (not shown) is set to a four-wheel drive low range.
A strategic control scheme (‘Strategic Control’) 310 determines a preferred input speed (‘Ni_Des’) and a preferred engine state and transmission operating range state (‘Hybrid Range State Des’) based upon the output speed and the operator torque request and based upon other operating parameters of the hybrid powertrain, including battery power limits and response limits of the engine 14, the transmission 10, and the first and second electric machines 56 and 72. The predicted accelerator output torque request and the predicted brake output torque request are input to the strategic control scheme 310. The strategic control scheme 310 is preferably executed by the HCP 5 during each 100 ms loop cycle and each 25 ms loop cycle. The desired operating range state for the transmission 10 and the desired input speed from the engine 14 to the transmission 10 are inputs to the shift execution and engine start/stop control scheme 320.
The shift execution and engine start/stop control scheme 320 commands changes in the transmission operation (‘Transmission Commands’) including changing the operating range state based upon the inputs and operation of the powertrain system. This includes commanding execution of a change in the transmission operating range state if the preferred operating range state is different from the present operating range state by commanding changes in application of one or more of the clutches C1 70, C2 62, C3 73, and C4 75 and other transmission commands. The present operating range state (‘Hybrid Range State Actual’) and an input speed profile (‘Ni_Prof’) can be determined. The input speed profile is an estimate of an upcoming input speed and preferably comprises a scalar parametric value that is a targeted input speed for the forthcoming loop cycle. The engine operating commands and the operator torque request are based upon the input speed profile during a transition in the operating range state of the transmission.
A tactical control scheme (‘Tactical Control and Operation’) 330 is executed during one of the control loop cycles to determine engine commands (‘Engine Commands’) for operating the engine 14, including a preferred input torque from the engine 14 to the transmission 10 based upon the output speed, the input speed, and the operator torque request comprising the immediate accelerator output torque request, the predicted accelerator output torque request, the immediate brake output torque request, the predicted brake output torque request, the axle torque response type, and the present operating range state for the transmission. The engine commands also include engine states including one of an all-cylinder operating state and a cylinder deactivation operating state wherein a portion of the engine cylinders are deactivated and unfueled, and engine states including one of a fueled state and a fuel cutoff state. An engine command comprising the preferred input torque of the engine 14 and the present input torque (‘Ti’) reacting between the engine 14 and the input member 12 are preferably determined in the ECM 23. Clutch torques (‘Tcl’) for each of the clutches C1 70, C2 62, C3 73, and C4 75, including the presently applied clutches and the non-applied clutches are estimated, preferably in the TCM 17.
An output and motor torque determination scheme (‘Output and Motor Torque Determination’) 340 is executed to determine the preferred output torque from the powertrain (‘To_cmd’). This includes determining motor torque commands (‘TA’, ‘TB’) to transfer a net commanded output torque to the output member 64 of the transmission 10 that meets the operator torque request, by controlling the first and second electric machines 56 and 72 in this embodiment. The immediate accelerator output torque request, the immediate brake output torque request, the present input torque from the engine 14 and the estimated applied clutch torque(s), the present operating range state of the transmission 10, the input speed, the input speed profile, and the axle torque response type are inputs. The output and motor torque determination scheme 340 executes to determine the motor torque commands during each iteration of one of the loop cycles. The output and motor torque determination scheme 340 includes algorithmic code which is regularly executed during the 6.25 ms and 12.5 ms loop cycles to determine the preferred motor torque commands.
The hybrid powertrain is controlled to transfer the output torque to the output member 64 to react with the driveline 90 to generate tractive torque at wheel(s) 93 to forwardly propel the vehicle in response to the operator input to the accelerator pedal 113 when the operator selected position of the transmission gear selector 114 commands operation of the vehicle in the forward direction. Similarly, the hybrid powertrain is controlled to transfer the output torque to the output member 64 to react with the driveline 90 to generate tractive torque at wheel(s) 93 to propel the vehicle in a reverse direction in response to the operator input to the accelerator pedal 113 when the operator selected position of the transmission gear selector 114 commands operation of the vehicle in the reverse direction. Preferably, propelling the vehicle results in vehicle acceleration so long as the output torque is sufficient to overcome external loads on the vehicle, e.g., due to road grade, aerodynamic loads, and other loads.
The preferred operation in each of M1 and M2 can be determined by executing a 2-dimensional search scheme 620, shown with reference to
The power cost inputs to the cost function 450 are determined based upon factors related to vehicle driveability, fuel economy, emissions, and battery usage. Power costs are assigned and associated with fuel and electrical power consumption and are associated with a specific operating points of the hybrid powertrain. Lower operating costs can be associated with lower fuel consumption at high conversion efficiencies, lower battery power usage, and lower emissions for each engine speed/load operating point, and take into account the candidate operating state of the engine 14. As described hereinabove, the power costs may include the engine power losses (‘PLOSS ENG’), electric motor power losses (‘PLOSS MOTOR’), battery power losses (‘PLOSS BATT’), brake power losses (‘PLOSS BRAKE’), and mechanical power losses (‘PLOSS MECH’) associated with operating the hybrid powertrain at a specific operating point which includes input speed, motor speeds, input torque, motor torques, a transmission operating range state and an engine state.
The mechanical power loss in the transmission 10 includes power losses due to rotational spinning, torque transfer, and friction, and operation of parasitic loads, e.g., a hydraulic pump (not shown) for the transmission 10. The mechanical power loss can be determined for each operating range state for the transmission 14 and input speed. Mechanical power loss related to the input speed (‘Ni’) and the output speed (‘No’) can be represented by Eq. 1:
PMECH LOSS=aNi+bNi2+cNiNo+dNo2 [1]
wherein a, b, c, and d comprise calibrated scalar values determined for the specific powertrain system and each specific transmission operating range state.
Thus, in fixed gear operation, i.e., in one of the fixed gear operating ranges states of G1, G2, G3 and G4 for the embodiment described herein, the power cost input comprising the mechanical power loss to the cost function 450 can be predetermined outside of the 1-dimension search scheme 610. In mode operation, i.e., in one of the mode operating ranges states of M1 and M2 for the embodiment described herein, the power cost input comprising the mechanical power loss to the cost function 450 can be determined during each iteration of the search scheme 620.
The state stabilization and arbitration block 280 selects a preferred transmission operating range state (‘Hybrid Range State Des’) which preferably is the transmission operating range state associated with the minimum preferred cost for the allowed operating range states output from the operating range state analyzer 260, taking into account factors related to arbitrating effects of changing the operating range state on the operation of the transmission to effect stable powertrain operation. The preferred input speed (‘Ni_Des’) is the engine input speed associated with the preferred engine input comprising the preferred engine input speed (‘Ni*’), the preferred engine input power (‘Pi*’), and the preferred engine input torque (‘Ti*’) that is responsive to and preferably meets the operator torque request for the selected preferred transmission operating range state. Due to subjective constraints imposed on a system such as that herein described, the transmission operating range state selected may not in all cases be that which is truly optimal from the standpoint of energy usage and power losses.
In one embodiment, such a system may provide a search method for determining a desirable input speed for a transmission in a combination that comprises at least one torque actuator mechanically coupled to the transmission, the torque actuator contributing to the input speed of said transmission. One search method includes first selecting a potential operating point for the at least one torque actuator from a search range, in which the potential operating point has associated with it a transmission input speed value and a transmission input power value. For purposes of the disclosure, the term ‘candidate’ can be used interchangeably with the term ‘potential’ in describing operating points and transmission operating range states. A plurality of power losses associated with operation of the combination at the potential operating point is determined, each which is combined to provide a total power loss for that point. The selection of a potential operating point, determination of power losses and their combination is repeated to provide a plurality of potential operating points, each of which have a total power loss associated with them. The potential operating points are evaluated for desirability, based on at least one criteria selected from the group consisting of: objective operating criteria and subjective operating criteria, and one operating point is selected from the plurality of potential operating points. Conducting such a search method under the constraint that the output power of said transmission is kept substantially-constant provides that the contours of the power losses (costs) are more prone to be linear when defined in an NI, PI plane, thus providing advantageous rapidity for a search engine that incorporates such methodology to convergence on an operating point of interest.
A search engine such as 410 can be conceived of as operating on a defined two-dimensional space that contains points corresponding to candidate NI and PI values for each potential transmission operating range state, such as space S as shown in
In one embodiment a search engine such as search engine 410 selects, either randomly or according to any desired algorithm, an NI and PI pair present in the space S, and a maximum transmission output torque (TO Max) and a minimum transmission output torque (TO Min) associated with the NI and PI pair chosen is calculated based on system constraints. Repetition of this method for a large number of different potential NI and PI pairs provides a plurality of different TO Min and TO Max values for each potential transmission operating range state. The method is repeated for each potential transmission operating range state and a plurality of TO Min and TO Max pairs are generated for the space S of and for each potential transmission operating range state and NI and PI pairs provided.
From such plurality of different TO Min and TO Max values so generated by a search engine for a given potential transmission operating range state, the NI and PI pair having the highest TO Max value associated with each potential transmission operating range state is generally selected as the preferred NI and PI pair when an operator torque request is greater than TO Max. In some embodiments for cases in which an operator torque request is less than TO Min, the potential NI and PI pair associated with the lowest TO Min value is generally selected as the preferred NI and PI for the particular potential transmission operating range state under consideration. In any event, it is in generally desirable to be able to quickly locate, within a space S for each potential transmission operating range state, that NI and PI pair that has the least power losses associated with it. The effectiveness of such a task is inhibited by the fact that the location of the space S is moving essentially constantly, which over time makes the effective size of the search range of the space S very large.
Towards reduction of the effective size of the space S, pre-calculations are undertaken in a computer simulation which in one embodiment is not operatively connected to a drivetrain as described herein. Such pre-calculations, or off-line simulations, are carried out using values for engine coolant temperature, engine torque curves, battery power limits, electric machine speed limits, electric machine torque limits, transmission oil temperature, and battery state-of-charge which are frequently encountered by a motorized vehicle during its operation, to determine maximum and minimum values for NI and PI which can be used to define a space S that is smaller in range than the space S that is encountered during use of a search engine and system useful therewith as herein described. Without use of a method as described herein, the search range embraced by the space S was based on NI min and NI max values that were based on speed-based system constraints and PI min and PI max values that were based on TI min and TI max values provided by the ECM 23; however a method as provided herein narrows down the search range embraced by the space S, based on off-line simulation results.
In one embodiment of the disclosure the NI, PI plane representing search range embraced by the space S is determined by first choosing one point in that plane and evaluating it for power losses. Other points are chosen, either arbitrarily or according to any desire algorithm and similarly evaluated for power loss if the system were operating at those points. By evaluating, via an off-line computer simulation, a large number of points (which may be on the order of 100,000 points), a contour plot such as that shown in
Thus, according to the foregoing, the search range was determined by an off-line simulation that evaluates each point in the Ni, Pi plane within the “large” search range space S set by system constraints.
From
in which a, b, c, and d are cost criteria that can reduce the search range to exclude operating points that reside outside of the system constraints. Setting these values to 0 will exclude all points not within the constraints. Setting the values to a small, non-zero positive value has the effect of providing a margin around each of the system constraints to minimize the effect of simulation errors that could otherwise erroneously exclude points that are within the constraints. The Ta/Tb/Ti/PBatt penalty costs refer to the costs that are imposed to the NI, PI pair that is associated with Ta, Tb, Ti, PBatt points that are not within their achievable limits. In general, these penalty costs are provided to increase proportionally with the amount of how much each point exceeds each achievable limit. The cost criteria “e” can further reduce the search range to exclude points that are within the system constraints but have high objective power loss costs subjectively determined as being non-optimal. In the first If step, a ToMax(ToMin) is calculated for each Ni, Pi point that is evaluated by including the Output Torque limiting inside the search loop. ToMaxMax (ToMinMin) is the maximum(minimum) of all ToMax(ToMin), which represents the maximum(minimum) output torque that can be produced within the evaluated Ni, Pi range. In the Else step, the Objective Power Loss cost is the sum of battery power loss, machine power loss, engine power loss, and transmission power loss.
A process as set forth above with respect to determining the area B on
An alternate representation of the four points for each of the 2500 plots so generated per the foregoing, is to provide four tables of data, each of which four tables of data comprise 2500 entries, and each of which four tables contain values of NI min, NI max, PI min, and PI max, as shown in
Thus, a method for determining a set of values for NI min, NI max, PI min, and PI max for input to a 2-D search engine such as 410 has been provided, and these values of NI min, NI max, PI min, and PI max are sufficient to define search range space S having a substantially smaller size than what is otherwise provided by a system as described herein. This decreased size of the space S provided by a method according to this disclosure translates to decreased demand on computer resources and accordingly results in more efficient searching and faster pinpointing of exact operating points for potential transmission operating modes.
It is understood that modifications are allowable within the scope of the disclosure. The disclosure has been described with specific reference to the preferred embodiments and modifications thereto. Further modifications and alterations may occur to others upon reading and understanding the specification. It is intended to include all such modifications and alterations insofar as they come within the scope of the disclosure.
This application claims the benefit of U.S. Provisional Application No. 60/985,227 filed on Nov. 3, 2007, which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5274559 | Takahashi et al. | Dec 1993 | A |
6110066 | Nedungadi et al. | Aug 2000 | A |
6832148 | Bennett | Dec 2004 | B1 |
6868318 | Cawthorne | Mar 2005 | B1 |
6957137 | Hubbard et al. | Oct 2005 | B2 |
7024299 | Hubbard et al. | Apr 2006 | B2 |
7154236 | Heap | Dec 2006 | B1 |
20030217876 | Severinsky et al. | Nov 2003 | A1 |
20040148096 | Katou | Jul 2004 | A1 |
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 |
20060213704 | Mack | Sep 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 | 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 | 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 et al. | May 2009 | A1 |
20090118921 | Heap | May 2009 | A1 |
20090118922 | Heap et al. | 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 | 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 |
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 |
20100295810 | Nagata et al. | Nov 2010 | A1 |
Number | Date | Country | |
---|---|---|---|
20090118952 A1 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60985227 | Nov 2007 | US |