Patent Grant
9534547
The present disclosure relates to internal combustion engines and more particularly to engine control systems and methods for vehicles.
The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
Internal combustion engines combust an air and fuel mixture within cylinders to drive pistons, which produces drive torque. Air flow into the engine is regulated via a throttle. More specifically, the throttle adjusts throttle area, which increases or decreases air flow into the engine. As the throttle area increases, the air flow into the engine increases. A fuel control system adjusts the rate that fuel is injected to provide a desired air/fuel mixture to the cylinders and/or to achieve a desired torque output. Increasing the amount of air and fuel provided to the cylinders increases the torque output of the engine.
In spark-ignition engines, spark initiates combustion of an air/fuel mixture provided to the cylinders. In compression-ignition engines, compression in the cylinders combusts the air/fuel mixture provided to the cylinders. Spark timing and air flow may be the primary mechanisms for adjusting the torque output of spark-ignition engines, while fuel flow may be the primary mechanism for adjusting the torque output of compression-ignition engines.
Engine control systems have been developed to control engine output torque to achieve a desired torque. Traditional engine control systems, however, do not control the engine output torque as accurately as desired. Further, traditional engine control systems do not provide a rapid response to control signals or coordinate engine torque control among various devices that affect the engine output torque.
An engine control system for a vehicle, includes a delay and rate limit module, a throttle control module, a phaser control module, and an exhaust gas recirculation (EGR) control module. The delay and rate limit module applies a delay and a rate limit to a first torque request to produce a second torque request. The throttle control module determines a target throttle opening based on the second torque request and selectively adjusts a throttle valve based on the target throttle opening. The phaser control module determines target intake and exhaust phasing values based on the second torque request and selectively adjusts intake and exhaust valve phasers based on the target intake and exhaust phasing values, respectively. The EGR control module determines a target EGR opening based on the first torque request and selectively adjusts an EGR valve based on the target EGR opening.
An engine control method for a vehicle, includes: applying a delay and a rate limit to a first torque request to produce a second torque request; determining a target throttle opening based on the second torque request; and selectively adjusting a throttle valve based on the target throttle opening. The engine control method further includes: determining target intake and exhaust phasing values based on the second torque request; selectively adjusting intake and exhaust valve phasers based on the target intake and exhaust phasing values, respectively; determining a target exhaust gas recirculation (EGR) opening based on the first torque request; and selectively adjusting an EGR valve based on the target EGR opening.
Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.
The present disclosure will become more fully understood from the detailed description and the accompanying drawings, wherein:
An engine control module (ECM) controls torque output of an engine. More specifically, the ECM controls actuators of the engine based on target values, respectively, to produce a requested amount of torque. For example, the ECM controls intake and exhaust valve phasing based on target intake and exhaust phasing angles, a throttle valve based on a target throttle opening, an exhaust gas recirculation (EGR) valve based on a target EGR opening, and a wastegate of a turbocharger based on a target wastegate duty cycle.
The ECM determines a torque request for controlling intake and exhaust cam phasing, the throttle valve, the EGR valve, and the wastegate. The ECM shapes the torque request into a shaped torque request. The ECM determines a first target torque based on the shaped torque request and a first torque adjustment and determines the target throttle opening and the target wastegate duty cycle based on the first target torque. The ECM also determines a second target torque based on the shaped torque request and a second torque adjustment and determines the target intake and exhaust phasing angles based on the second target torque. The ECM determines a third target torque based on the (non-shaped) torque request and a third torque adjustment and determines the target EGR opening based on the third target torque. In this manner, setting of the first target torque, the second target torque, and the third target torque is coordinated with the response characteristics of the throttle valve 112 and the turbocharger, the intake and exhaust cam phasers 148 and 150, and the EGR valve 170, respectively. The coordination of the target torques with the respective response characteristics may increase engine performance and response.
Referring now to
Air from the intake manifold 110 is drawn into cylinders of the engine 102. While the engine 102 may include multiple cylinders, for illustration purposes a single representative cylinder 118 is shown. For example only, the engine 102 may include 2, 3, 4, 5, 6, 8, 10, and/or 12 cylinders. The ECM 114 may instruct a cylinder actuator module 120 to selectively deactivate some of the cylinders, which may improve fuel economy under certain engine operating conditions.
The engine 102 may operate using a four-stroke cycle. The four strokes, described below, may be referred to as the intake stroke, the compression stroke, the combustion stroke, and the exhaust stroke. During each revolution of a crankshaft (not shown), two of the four strokes occur within the cylinder 118. Therefore, two crankshaft revolutions are necessary for the cylinder 118 to experience all four of the strokes.
During the intake stroke, air from the intake manifold 110 is drawn into the cylinder 118 through an intake valve 122. The ECM 114 controls a fuel actuator module 124, which regulates fuel injection to achieve a target air/fuel ratio. Fuel may be injected into the intake manifold 110 at a central location or at multiple locations, such as near the intake valve 122 of each of the cylinders. In various implementations (not shown), fuel may be injected directly into the cylinders or into mixing chambers associated with the cylinders. The fuel actuator module 124 may halt injection of fuel to cylinders that are deactivated.
The injected fuel mixes with air and creates an air/fuel mixture in the cylinder 118. During the compression stroke, a piston (not shown) within the cylinder 118 compresses the air/fuel mixture. While not shown, the engine 102 may be a compression-ignition engine, in which case compression within the cylinder 118 ignites the air/fuel mixture. Alternatively, as shown, the engine 102 may be a spark-ignition engine, in which case a spark actuator module 126 energizes a spark plug 128 in the cylinder 118 based on a signal from the ECM 114, which ignites the air/fuel mixture. The timing of the spark may be specified relative to the time when the piston is at its topmost position, referred to as top dead center (TDC).
The spark actuator module 126 may be controlled by a timing signal specifying how far before or after TDC to generate the spark. Because piston position is directly related to crankshaft rotation, operation of the spark actuator module 126 may be synchronized with crankshaft angle. The spark actuator module 126 may halt provision of spark to deactivated cylinders. Generating spark may be referred to as a firing event. The spark actuator module 126 may have the ability to vary the timing of the spark for each firing event. The spark actuator module 126 may vary the spark timing for a next firing event when the spark timing is changed between a last firing event and the next firing event.
During the combustion stroke, the combustion of the air/fuel mixture drives the piston away from TDC, thereby driving the crankshaft. The combustion stroke may be defined as the time between the piston reaching TDC and the time at which the piston reaches bottom dead center (BDC). During the exhaust stroke, the piston begins moving away from BDC and expels the byproducts of combustion through an exhaust valve 130. The byproducts of combustion are exhausted from the vehicle via an exhaust system 134.
The intake valve 122 may be controlled by an intake camshaft 140, while the exhaust valve 130 may be controlled by an exhaust camshaft 142. In various implementations, multiple intake camshafts (including the intake camshaft 140) may control multiple intake valves (including the intake valve 122) for the cylinder 118 and/or may control the intake valves (including the intake valve 122) of multiple banks of cylinders (including the cylinder 118). Similarly, multiple exhaust camshafts (including the exhaust camshaft 142) may control multiple exhaust valves for the cylinder 118 and/or may control exhaust valves (including the exhaust valve 130) for multiple banks of cylinders (including the cylinder 118). The cylinder actuator module 120 may deactivate the cylinder 118 by disabling opening of the intake valve 122 and/or the exhaust valve 130. In various other implementations, the intake valve 122 and/or the exhaust valve 130 may be controlled by devices other than camshafts, such as camless valve actuators.
The time when the intake valve 122 is opened may be varied with respect to piston TDC by an intake cam phaser 148. The time when the exhaust valve 130 is opened may be varied with respect to piston TDC by an exhaust cam phaser 150. A phaser actuator module 158 may control the intake cam phaser 148 and the exhaust cam phaser 150 based on signals from the ECM 114. When implemented, variable valve lift (not shown) may also be controlled by the phaser actuator module 158.
The engine system 100 may include a boost device that provides pressurized air to the intake manifold 110. For example,
A wastegate 162 may allow exhaust to bypass the turbine 160-1, thereby reducing the boost (the amount of intake air compression) provided by the turbocharger. The ECM 114 may control the turbocharger via a boost actuator module 164. The boost actuator module 164 may modulate the boost of the turbocharger by controlling opening of the wastegate 162. In various implementations, multiple turbochargers may be controlled by the boost actuator module 164. The turbocharger may have variable geometry, which may be controlled by the boost actuator module 164.
An intercooler (not shown) may dissipate some of the heat contained in the compressed air charge, which is generated as the air is compressed. The compressed air charge may also have absorbed heat from components of the exhaust system 134. Although shown separated for purposes of illustration, the turbine 160-1 and the compressor 160-2 may be attached to each other, placing intake air in close proximity to hot exhaust.
The engine system 100 may include an exhaust gas recirculation (EGR) valve 170, which selectively redirects exhaust gas back to the intake manifold 110. The EGR valve 170 may be located upstream of the turbocharger's turbine 160-1. The EGR valve 170 may be controlled by an EGR actuator module 172.
The engine system 100 may measure the speed of the crankshaft in revolutions per minute (RPM) using an RPM sensor 180. The temperature of the engine coolant may be measured using an engine coolant temperature (ECT) sensor 182. The ECT sensor 182 may be located within the engine 102 or at other locations where the coolant is circulated, such as a radiator (not shown).
The pressure within the intake manifold 110 may be measured using a manifold absolute pressure (MAP) sensor 184. In various implementations, engine vacuum, which is the difference between ambient air pressure and the pressure within the intake manifold 110, may be measured. The mass flow rate of air flowing into the intake manifold 110 may be measured using a mass air flow (MAF) sensor 186. In various implementations, the MAF sensor 186 may be located in a housing that also includes the throttle valve 112.
The throttle actuator module 116 may monitor the position of the throttle valve 112 using one or more throttle position sensors (TPS) 190. The ambient temperature of air being drawn into the engine 102 may be measured using an intake air temperature (IAT) sensor 192. The engine system 100 may also include one or more other sensors. The ECM 114 may use signals from the sensors to make control decisions for the engine system 100.
The ECM 114 may communicate with a transmission control module 194 to coordinate shifting gears in a transmission (not shown). For example, the ECM 114 may reduce engine torque during a gear shift. The ECM 114 may communicate with a hybrid control module 196 to coordinate operation of the engine 102 and an electric motor 198.
The electric motor 198 may also function as a generator, and may be used to produce electrical energy for use by vehicle electrical systems and/or for storage in a battery. In various implementations, various functions of the ECM 114, the transmission control module 194, and the hybrid control module 196 may be integrated into one or more modules.
Each system that varies an engine parameter may be referred to as an actuator. Each system receives a target actuator value. For example, the throttle actuator module 116 may be referred to as an actuator, and a target throttle opening (e.g., area) may be referred to as the target actuator value. In the example of
Similarly, the spark actuator module 126 may be referred to as an actuator, while the corresponding target actuator value may be a target spark timing relative to piston TDC. Other actuators may include the cylinder actuator module 120, the fuel actuator module 124, the phaser actuator module 158, the boost actuator module 164, and the EGR actuator module 172. For these actuators, the target actuator values may include target number of activated cylinders, target fueling parameters, target intake and exhaust cam phaser angles, target wastegate duty cycle, and target EGR valve opening area, respectively. The ECM 114 may generate the target actuator values to cause the engine 102 to generate a target engine output torque.
Referring now to
The driver torque module 202 may determine a driver torque request 254 based on a driver input 255 from the driver input module 104. The driver input 255 may be based on, for example, a position of an accelerator pedal and a position of a brake pedal. The driver input 255 may also be based on cruise control, which may be an adaptive cruise control system that varies vehicle speed to maintain a predetermined following distance. The driver torque module 202 may store one or more mappings of accelerator pedal position to target torque and may determine the driver torque request 254 based on a selected one of the mappings.
An axle torque arbitration module 204 arbitrates between the driver torque request 254 and other axle torque requests 256. Axle torque (torque at the wheels) may be produced by various sources including an engine and/or an electric motor. For example, the axle torque requests 256 may include a torque reduction requested by a traction control system when positive wheel slip is detected. Positive wheel slip occurs when axle torque overcomes friction between the wheels and the road surface, and the wheels begin to slip against the road surface. The axle torque requests 256 may also include a torque increase request to counteract negative wheel slip, where a tire of the vehicle slips in the other direction with respect to the road surface because the axle torque is negative.
The axle torque requests 256 may also include brake management requests and vehicle over-speed torque requests. Brake management requests may reduce axle torque to ensure that the axle torque does not exceed the ability of the brakes to hold the vehicle when the vehicle is stopped. Vehicle over-speed torque requests may reduce the axle torque to prevent the vehicle from exceeding a predetermined speed. The axle torque requests 256 may also be generated by vehicle stability control systems.
The axle torque arbitration module 204 outputs a predicted torque request 257 and an immediate torque request 258 based on the results of arbitrating between the received torque requests 254 and 256. As described below, the predicted and immediate torque requests 257 and 258 from the axle torque arbitration module 204 may selectively be adjusted by other modules of the ECM 114 before being used to control the actuators of the engine system 100.
In general terms, the immediate torque request 258 is the amount of currently target axle torque, while the predicted torque request 257 is the amount of axle torque that may be needed on short notice. The ECM 114 controls the engine system 100 to produce an axle torque equal to the immediate torque request 258. However, different combinations of actuator values may result in the same axle torque. The ECM 114 may therefore adjust the target actuator values to enable a faster transition to the predicted torque request 257, while still maintaining the axle torque at the immediate torque request 258.
In various implementations, the predicted torque request 257 may be set based on the driver torque request 254. The immediate torque request 258 may be set to less than the predicted torque request 257 under some circumstances, such as when the driver torque request 254 is causing wheel slip on an icy surface. In such a case, a traction control system (not shown) may request a reduction via the immediate torque request 258, and the ECM 114 reduces the engine torque output to the immediate torque request 258. However, the ECM 114 performs the reduction so the engine system 100 can quickly resume producing the predicted torque request 257 once the wheel slip stops.
In general terms, the difference between the immediate torque request 258 and the (generally higher) predicted torque request 257 can be referred to as a torque reserve. The torque reserve may represent the amount of additional torque (above the immediate torque request 258) that the engine system 100 can begin to produce with minimal delay. Fast engine actuators are used to increase or decrease current axle torque with minimal delay. As described in more detail below, fast engine actuators are defined in contrast with slow engine actuators.
In various implementations, fast engine actuators are capable of varying axle torque within a range, where the range is established by the slow engine actuators. The upper limit of the range is the predicted torque request 257, while the lower limit of the range is limited by the torque (varying) capacity of the fast actuators. For example only, fast actuators may only be able to reduce axle torque by a first amount, where the first amount is a measure of the torque capacity of the fast actuators. The first amount may vary based on engine operating conditions set by the slow engine actuators.
When the immediate torque request 258 is within the range, fast engine actuators can be controlled to cause the axle torque to be equal to the immediate torque request 258. When the ECM 114 requests the predicted torque request 257 to be output, the fast engine actuators can be controlled to vary the axle torque to the top of the range, which is the predicted torque request 257.
In general terms, fast engine actuators can change the axle torque more quickly than slow engine actuators. Slow actuators may respond more slowly to changes in their respective actuator values than fast actuators do. For example, a slow actuator may include mechanical components that require time to move from one position to another in response to a change in actuator value. A slow actuator may also be characterized by the amount of time it takes for the axle torque to begin to change once the slow actuator begins to implement the changed actuator value. Generally, this amount of time will be longer for slow actuators than for fast actuators. In addition, even after beginning to change, the axle torque may take longer to fully respond to a change in a slow actuator.
For example only, the ECM 114 may set actuator values for slow actuators to values that would enable the engine system 100 to produce the predicted torque request 257 if the fast actuators were set to appropriate values. Meanwhile, the ECM 114 may set target actuator values for fast actuators to values that, given the slow actuator values, cause the engine system 100 to produce the immediate torque request 258 instead of the predicted torque request 257.
The fast actuators therefore cause the engine system 100 to produce the immediate torque request 258. When the ECM 114 decides to transition the axle torque from the immediate torque request 258 to the predicted torque request 257, the ECM 114 changes the target actuator values for one or more fast actuators to values that correspond to the predicted torque request 257. Because the target actuator values for the slow actuators have already been set based on the predicted torque request 257, the engine system 100 is able to produce the predicted torque request 257 after only the (minimal) delay imposed by the fast actuators. In other words, the longer delay that would otherwise result from changing axle torque using slow actuators is avoided.
For example only, in a spark-ignition engine, spark timing may be a fast actuator value, while throttle opening may be a slow actuator value. Spark-ignition engines may combust fuels including, for example, gasoline and ethanol, by applying a spark. By contrast, in a compression-ignition engine, fuel flow may be a fast actuator value, while throttle opening may be used as an actuator value for engine characteristics other than torque. Compression-ignition engines may combust fuels including, for example, diesel fuel, via compression.
When the engine 102 is a spark-ignition engine, the spark actuator module 126 may be a fast actuator and the throttle actuator module 116 may be a slow actuator. After receiving a new target actuator value, the spark actuator module 126 may be able to change spark timing for the following firing event. When the spark timing (also called spark advance) for a firing event is set to an optimum value, a maximum amount of torque may be produced in the combustion stroke immediately following the firing event. However, a spark timing deviating from the optimum value may reduce the amount of torque produced in the combustion stroke. Therefore, the spark actuator module 126 may be able to vary engine output torque as soon as the next firing event occurs by varying spark timing. For example only, a table of optimum spark timings corresponding to different engine operating conditions may be determined during a calibration phase of vehicle design, and the optimum value is selected from the table based on current engine operating conditions.
By contrast, changes in throttle opening take longer to affect engine output torque. The throttle actuator module 116 changes the throttle opening by adjusting the angle of the blade of the throttle valve 112. Therefore, once a new actuator value is received, there is a mechanical delay as the throttle valve 112 moves from its previous position to a new position based on the new target actuator value. In addition, air flow changes based on the throttle opening are subject to air transport delays in the intake manifold 110. Further, increased air flow in the intake manifold 110 is not realized as an increase in engine output torque until the cylinder 118 receives additional air in the next intake stroke, compresses the additional air, and commences the combustion stroke.
Using these actuators as an example, a torque reserve can be created by setting the throttle opening to a value that would allow the engine 102 to produce the predicted torque request 257. Meanwhile, the spark timing can be set based on the immediate torque request 258, which is less than the predicted torque request 257. Although the throttle opening generates enough air flow for the engine 102 to produce the predicted torque request 257, the spark timing is retarded (which reduces torque) based on the immediate torque request 258. The engine output torque will therefore be equal to the immediate torque request 258.
When additional torque is needed, the spark timing can be set based on the predicted torque request 257 or a torque between the predicted and immediate torque requests 257 and 258. By the following firing event, the spark actuator module 126 may return the spark timing to an optimum value, which allows the engine 102 to produce the full engine output torque achievable with the air flow already present. The engine output torque may therefore be quickly increased to the predicted torque request 257 without experiencing delays from changing the throttle opening.
The axle torque arbitration module 204 may output the predicted torque request 257 and the immediate torque request 258 to a propulsion torque arbitration module 206. In various implementations, the axle torque arbitration module 204 may output the predicted and immediate torque requests 257 and 258 to the hybrid optimization module 208.
The hybrid optimization module 208 may determine how much torque should be produced by the engine 102 and how much torque should be produced by the electric motor 198. The hybrid optimization module 208 then outputs modified predicted and immediate torque requests 259 and 260, respectively, to the propulsion torque arbitration module 206. In various implementations, the hybrid optimization module 208 may be implemented in the hybrid control module 196.
The predicted and immediate torque requests received by the propulsion torque arbitration module 206 are converted from an axle torque domain (torque at the wheels) into a propulsion torque domain (torque at the crankshaft). This conversion may occur before, after, as part of, or in place of the hybrid optimization module 208.
The propulsion torque arbitration module 206 arbitrates between propulsion torque requests 290, including the converted predicted and immediate torque requests. The propulsion torque arbitration module 206 generates an arbitrated predicted torque request 261 and an arbitrated immediate torque request 262. The arbitrated torque requests 261 and 262 may be generated by selecting a winning request from among received torque requests. Alternatively or additionally, the arbitrated torque requests may be generated by modifying one of the received requests based on another one or more of the received torque requests.
For example, the propulsion torque requests 290 may include torque reductions for engine over-speed protection, torque increases for stall prevention, and torque reductions requested by the transmission control module 194 to accommodate gear shifts. The propulsion torque requests 290 may also result from clutch fuel cutoff, which reduces the engine output torque when the driver depresses the clutch pedal in a manual transmission vehicle to prevent a flare (rapid rise) in engine speed.
The propulsion torque requests 290 may also include an engine shutoff request, which may be initiated when a critical fault is detected. For example only, critical faults may include detection of vehicle theft, a stuck starter motor, electronic throttle control problems, and unexpected torque increases. In various implementations, when an engine shutoff request is present, arbitration selects the engine shutoff request as the winning request. When the engine shutoff request is present, the propulsion torque arbitration module 206 may output zero as the arbitrated predicted and immediate torque requests 261 and 262.
In various implementations, an engine shutoff request may simply shut down the engine 102 separately from the arbitration process. The propulsion torque arbitration module 206 may still receive the engine shutoff request so that, for example, appropriate data can be fed back to other torque requestors. For example, all other torque requestors may be informed that they have lost arbitration.
The reserves/loads module 220 receives the arbitrated predicted and immediate torque requests 261 and 262. The reserves/loads module 220 may adjust the arbitrated predicted and immediate torque requests 261 and 262 to create a torque reserve and/or to compensate for one or more loads. The reserves/loads module 220 then outputs adjusted predicted and immediate torque requests 263 and 264 to the torque requesting module 224.
For example only, a catalyst light-off process or a cold start emissions reduction process may require retarded spark timing. The reserves/loads module 220 may therefore increase the adjusted predicted torque request 263 above the adjusted immediate torque request 264 to create retarded spark for the cold start emissions reduction process. In another example, the air/fuel ratio of the engine and/or the mass air flow may be directly varied, such as by diagnostic intrusive equivalence ratio testing and/or new engine purging. Before beginning these processes, a torque reserve may be created or increased to quickly offset decreases in engine output torque that result from leaning the air/fuel mixture during these processes.
The reserves/loads module 220 may also create or increase a torque reserve in anticipation of a future load, such as power steering pump operation or engagement of an air conditioning (NC) compressor clutch. The reserve for engagement of the NC compressor clutch may be created when the driver first requests air conditioning. The reserves/loads module 220 may increase the adjusted predicted torque request 263 while leaving the adjusted immediate torque request 264 unchanged to produce the torque reserve. Then, when the NC compressor clutch engages, the reserves/loads module 220 may increase the adjusted immediate torque request 264 by the estimated load of the A/C compressor clutch.
The torque requesting module 224 receives the adjusted predicted and immediate torque requests 263 and 264. The torque requesting module 224 determines how the adjusted predicted and immediate torque requests 263 and 264 will be achieved. The torque requesting module 224 may be engine type specific. For example, the torque requesting module 224 may be implemented differently or use different control schemes for spark-ignition engines versus compression-ignition engines.
In various implementations, the torque requesting module 224 may define a boundary between modules that are common across all engine types and modules that are engine type specific. For example, engine types may include spark-ignition and compression-ignition. Modules prior to the torque requesting module 224, such as the propulsion torque arbitration module 206, may be common across engine types, while the torque requesting module 224 and subsequent modules may be engine type specific.
For example, in a spark-ignition engine, the torque requesting module 224 may vary the opening of the throttle valve 112 as a slow actuator that allows for a wide range of torque control. The torque requesting module 224 may disable cylinders using the cylinder actuator module 120, which also provides for a wide range of torque control, but may also be slow and may involve drivability and emissions concerns. The torque requesting module 224 may use spark timing as a fast actuator. However, spark timing may not provide as much range of torque control. In addition, the amount of torque control possible with changes in spark timing (referred to as spark reserve capacity) may vary as air flow changes.
In various implementations, the torque requesting module 224 may generate an air torque request 265 based on the adjusted predicted torque request 263. The air torque request 265 may be equal to the adjusted predicted torque request 263, setting air flow so that the adjusted predicted torque request 263 can be achieved by changes to other (e.g., fast) actuators.
Target actuator values for airflow controlling actuators may be determined based on the air torque request 265. For example only, the air control module 228 (see also
The boost control module 248 may determine a target duty cycle 269 for the wastegate 162 based on the target MAP 266. While the target duty cycle 269 will be discussed, the boost control module 248 may determine another suitable value for controlling the wastegate 162. The phaser control module 252 may determine target intake and exhaust cam phaser angles 270 and 271 based on the second target APC 268. The EGR control module 253 determines a target EGR opening 292 based on the third target APC 291.
The torque requesting module 224 may also generate a spark torque request 272, a cylinder shut-off torque request 273, and a fuel torque request 274. The spark control module 232 may determine how much to retard the spark timing (which reduces engine output torque) from an optimum spark timing based on the spark torque request 272. For example only, a torque relationship may be inverted to solve for a desired spark timing 299. For a given torque request (Tdes), the desired spark timing (Sdes) 299 may be determined based on:
Sdes=f−1(Tdes,APC,I,E,AF,OT,#). (0)
This relationship may be embodied as an equation and/or as a lookup table. The air/fuel ratio (AF) may be the actual air/fuel ratio, as reported by the fuel control module 240. The spark control module 232 may also generate a target spark timing 275, as discussed further below in conjunction with
When the spark timing is set to the optimum spark timing, the resulting torque may be as close to a maximum best torque (MBT) as possible. MBT refers to the maximum engine output torque that is generated for a given air flow as spark timing is advanced, while using fuel having an octane rating greater than a predetermined octane rating and using stoichiometric fueling. The spark timing at which this maximum torque occurs is referred to as an MBT spark timing. The optimum spark timing may differ slightly from MBT spark timing because of, for example, fuel quality (such as when lower octane fuel is used) and environmental factors. The engine output torque at the optimum spark timing may therefore be less than MBT.
The cylinder shut-off torque request 273 may be used by the cylinder control module 236 to determine a target number of cylinders to deactivate 276. The cylinder control module 236 may also instruct the fuel control module 240 to stop providing fuel for deactivated cylinders and may instruct the spark control module 232 to stop providing spark for deactivated cylinders. The spark control module 232 may stop providing spark to a cylinder once an fuel/air mixture that is already present in the cylinder has been combusted.
The fuel control module 240 may vary the amount of fuel provided to each cylinder based on the fuel torque request 274. More specifically, the fuel control module 240 may generate target fueling parameters 277 based on the fuel torque request 274. The target fueling parameters 277 may include, for example, target mass of fuel, target injection starting timing, and target number of fuel injections.
During normal operation of a spark-ignition engine, the fuel control module 240 may operate in an air lead mode in which the fuel control module 240 attempts to maintain a stoichiometric air/fuel ratio by controlling fueling based on air flow. The fuel control module 240 may determine a target fuel mass that will yield stoichiometric combustion when combined with a present mass of air per cylinder (APC).
In compression-ignition systems, the fuel control module 240 may operate in a fuel lead mode in which the fuel control module 240 determines a target fuel mass for each cylinder that satisfies the fuel torque request 274 while minimizing emissions, noise, and fuel consumption. In the fuel lead mode, air flow is controlled based on fuel flow and may be controlled to yield a lean air/fuel ratio. In addition, the air/fuel ratio may be maintained above a predetermined level, which may prevent black smoke production in dynamic engine operating conditions.
The air control module 228 generates the target MAP 266 further based on a MAP estimated torque 278. The MAP estimated torque 278 corresponds to an estimated value of the present engine torque output determined based on a MAP 279 measured using the MAP sensor 184. The MAP torque estimation module 246 generates the MAP estimated torque 278 based on the MAP 279 and other measured engine operating parameters. For example, the MAP torque estimation module 246 generates the MAP estimated torque 278 using the relationship:
TMAP=f(MAP,RPM,SM,IM,EM,AF,OT,#), (1)
where TMAP is the MAP estimated torque 278, MAP is the MAP 279, RPM is engine speed (rotational speed of the crankshaft), SM is present spark timing 280 being used by the spark actuator module 126, IM is a measured intake cam phaser angle 281, EM is a measured exhaust cam phaser angle 282, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is oil temperature, and # is the present number of cylinders that are activated. The relationship may be embodied as an equation or as a look-up table.
The phaser control module 252 may provide the measured intake and exhaust cam phaser angles 281 and 282. The phaser control module 252 may generate the measured intake and exhaust cam phaser angles 281 and 282 based on previous values of the measured intake and exhaust cam phaser angles 281 and 282 and the target intake and exhaust cam phaser angles 270 and 271. For example, the phaser control module 252 may generate the measured intake and exhaust cam phaser angles 281 and 282 using the relationships:
IM=f(IT)+k*(IT−IM_PREV), and (2)
EM=f(ET)+k*(ET−EM_PREV), (3)
where IM is the measured intake cam phaser angle 281, IT is the target intake cam phaser angle 270, k is a predetermined scalar/gain value, IM_PREV is a previous value of the measured intake cam phaser angle 281, EN, is the measured exhaust cam phaser angle 282, ET is the target exhaust cam phaser angle 271, k is a predetermined scalar/gain value, and EM_PREV is a previous value of the measured exhaust cam phaser angle 282.
The air control module 228 generates various target values further based on a first APC estimated torque 283. The first APC estimated torque 283 corresponds to an estimated value of the present engine torque output determined based on a present APC 284. The present APC 284 is determined based on one or more measured parameters, such as the MAF, the MAP, and/or the IAT. The APC torque estimation module 244 generates the first APC estimated torque 283 based on the present APC 284 and other measured engine operating parameters. The APC torque estimation module 244 generates the first APC estimated torque 283 using the relationship:
TAPC1=f(APCM,RPM,SM,IM,EM,AF,OT,#) (4)
where TAPC1 is the first APC estimated torque 283, APCM is the present APC 284, RPM is the engine speed, SM is the present spark timing 280 being used by the spark actuator module 126, IM is the measured intake cam phaser angle 281, EM is the measured exhaust cam phaser angle 282, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, and # is the present number of cylinders that are activated. The relationship may be embodied as an equation or as a look-up table.
The APC torque estimation module 244 also generates a second APC estimated torque 298 based on the present APC 284 and the target intake and exhaust cam phaser angles 270 and 271. The APC torque estimation module 244 generates the second APC estimated torque 298 using the relationship:
TAPC2=f(APCM,RPM,SM,IT,ET,AF,OT,#), (5)
where TAPC2 is the second APC estimated torque 298, APCM is the present APC 284, RPM is the engine speed, SM is the present spark timing 280 being used by the spark actuator module 126, IT is the target intake cam phaser angle 270, ET is the target exhaust cam phaser angle 271, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, and # is the present number of cylinders that are activated. The relationship may be embodied as an equation or as a look-up table.
The air control module 228 may output the target throttle opening 267 to the throttle actuator module 116. The throttle actuator module 116 regulates the throttle valve 112 to produce the target throttle opening 267. The air control module 228 outputs the target MAP 266 to the boost control module 248. The boost control module 248 controls the wastegate 162 based on the target MAP 266. The air control module 228 outputs the second target APC 268 to the phaser control module 252. Based on the second target APC 268 and the engine speed (and/or crankshaft position), the phaser control module 252 may control positions of the intake and/or exhaust cam phasers 148 and 150.
Referring now to
A torque error module 304 determines a torque error 308 based on a difference between the shaped air torque request 303 and the first APC estimated torque 283. For example, the torque error module 304 may set the torque error 308 equal to the air torque request 265 minus the first APC estimated torque 283.
An adjustment module 312 generates a torque adjustment 316 based on the torque error 308. The adjustment module 312 may generate the torque adjustment 316, for example, using the relationship:
TADJ=KP*(TERROR)+KI*∫TERROR∂t, (6)
where TADJ is the torque adjustment 316, KP is a proportional gain, TERROR is the torque error 308, and KI is an integral gain. KP*(TTERROR) will be referred to as a proportional (P) torque adjustment, and KI*∫TERROR∂t at is referred to as an integral (I) torque adjustment 318. The torque adjustment 316 is equal to the sum of the P torque adjustment and the I torque adjustment 318. In various implementations, another suitable type of closed-loop controller may be used to generate the torque adjustment 316 based on the torque error 308.
A target determination module 320 determines a target torque 324 based on the shaped air torque request 303 and the torque adjustment 316. For example, the target determination module 320 may set the target torque 324 equal to the shaped air torque request 303 plus the torque adjustment 316.
A target APC module 328 generates a first target APC (APC1) 329.
APCT_1=T−1(TT,RPM,ST,ISEL,ESEL,AF,OT,#), (7)
where APCT_1 is the first target APC 329, TT is the target torque 324, RPM is engine speed, ST is the target spark timing 275, ISEL is the selected intake cam phaser angle 330, ESEL is the selected exhaust cam phaser angle 331, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, # is the present number of cylinders that are activated, and T−1 denotes inversion of relationship (4) above used to relate the present APC 284 to the first APC estimated torque 283. In various implementations, the target intake and exhaust cam phaser angles 270 and 271 may be used in place of the selected intake and exhaust cam phaser angles 330 and 331. This relationship may be embodied as an equation or as a look-up table. Generation of the selected intake and exhaust cam phaser angles 330 and 331 is discussed further below.
The target APC module 328 also generates the second and third target APCs 268 and 291. A second APC determination module 408 determines the second target APC 268 based on a phaser target torque 412, the target spark timing 275, and selected intake and exhaust cam phaser angles 330 and 331. The second APC determination module 408 determines the second target APC 268 further based on the engine speed, the present air/fuel ratio, the oil temperature, and the present number of active cylinders. Relationship (4) provided above may be inverted and solved to determine the second target APC 268. For example, the second APC determination module 408 may generate the second target APC 268 using the relationship:
APCT_2=T−1(TPTT,RPM,ST,ISEL,ESEL,AF,OT,#), (8)
where APCT_2 is the second target APC 268, TPTT is the phaser target torque 412, RPM is engine speed, ST is the target spark timing 275, ISEL is the selected intake cam phaser angle 330, ESEL is the selected exhaust cam phaser angle 331, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, # is the present number of cylinders that are activated, and T−1 denotes inversion of relationship (4) above used to relate the present APC 284 to the first APC estimated torque 283. In various implementations, the target intake and exhaust cam phaser angles 270 and 271 may be used in place of the selected intake and exhaust cam phaser angles 330 and 331. This relationship may be embodied as an equation or as a look-up table.
A target phaser torque module 416 determines the phaser target torque 412 based on the shaped air torque request 303 and a phaser torque adjustment 420. For example, the target phaser torque module 416 may set the phaser target torque 412 equal to the phaser torque adjustment 420 plus the shaped air torque request 303.
A first selection module 424 sets the phaser torque adjustment 420 to one of zero and the I torque adjustment 318 based on a first selection signal 428. For example, the first selection module 424 may set the phaser torque adjustment 420 to zero when the first selection signal 428 is in a first state and set the phaser torque adjustment 420 to the I torque adjustment 318 when the first selection signal 428 is in a second state. The state of the first selection signal 428 may be set, for example, during the calibration stage of vehicle design. For example, the first selection signal 428 may be set to the first state when the phaser control module 252 can change the target intake and/or exhaust phaser angles 270 and 271 at greater than a predetermined rate. The first selection signal 428 may be set to the second state when the phaser control module 252 is limited to changing the target intake and/or exhaust phaser angles 270 and 271 at less than the predetermined rate.
As stated above, the phaser control module 252 (
IT=f(RPM,APCT_2); and (9)
ET=f(RPM,APCT_2), (10)
where IT is the target intake cam phaser angle 270, RPM is the engine speed, APCT_2 is the second target APC 268, and ET is the target exhaust cam phaser angle 271. These relationships may be embodied as equations or as look-up tables. The phaser actuator module 158 controls the intake and exhaust cam phasers 148 and 150 based on the target intake and exhaust cam phaser angles 270 and 271, respectively.
A third APC determination module 432 determines the third target APC 291 based on an EGR target torque 436, the target spark timing 275, and selected intake and exhaust cam phaser angles 330 and 331. The third APC determination module 432 determines the third target APC 291 further based on the engine speed, the present air/fuel ratio, the oil temperature, and the present number of active cylinders. Relationship (4) provided above may be inverted and solved to determine the third target APC 291. For example, the third APC determination module 432 may generate the third target APC 291 using the relationship:
APCT_3=T−1(TEGRT,RPM,ST,ISEL,ESEL,AF,OT,#) (11)
where APCT_3 is the third target APC 291, TEGRT is the EGR target torque 436, RPM is engine speed, ST is the target spark timing 275, ISEL is the selected intake cam phaser angle 330, ESEL is the selected exhaust cam phaser angle 331, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, # is the present number of cylinders that are activated, and T−1 denotes inversion of relationship (4) above used to relate the present APC 284 to the first APC estimated torque 283. In various implementations, the target intake and exhaust cam phaser angles 270 and 271 may be used in place of the selected intake and exhaust cam phaser angles 330 and 331. This relationship may be embodied as an equation or as a look-up table.
A target EGR torque module 440 determines the EGR target torque 436 based on the air torque request 265 and an EGR torque adjustment 444. For example, the target EGR torque module 440 may set the EGR target torque 436 equal to the EGR torque adjustment 444 plus the air torque request 265.
A second selection module 448 sets the EGR torque adjustment 444 to one of zero and the I torque adjustment 318 based on a second selection signal 452. For example, the second selection module 448 may set the EGR torque adjustment 444 to zero when the second selection signal 452 is in a first state and set the EGR torque adjustment 444 to the I torque adjustment 318 when the second selection signal 452 is in a second state. The state of the second selection signal 452 may be set, for example, during the calibration stage of vehicle design. For example, the second selection signal 452 may be set to the first state when the EGR control module 253 can change the target EGR opening 292 at greater than a predetermined rate. The second selection signal 452 may be set to the second state when the EGR control module 253 is limited to changing the target EGR opening 292 at less than the predetermined rate.
As stated above, the EGR control module 253 (
MEGRT=f(RPM,APCT_3) (12)
where MEGRT is the mass EGR flow rate, RPM is the engine speed, and APCT_3 is the third target APC 291. This relationship may be embodied as an equation or as a look-up table.
The EGR control module 253 may determine the target EGR opening 292 based on the target EGR mass flow rate. The EGR control module 253 determines the target EGR opening 292 further based on the target MAP 266, an exhaust temperature, and an exhaust pressure. For example, the EGR control module 253 may determine the target EGR opening 292 using the relationship:
where AREAEGRT is the target EGR opening 292, MEGRT is the target EGR mass flow rate, MAPT is the target MAP 266, RGAS is the ideal gas constant, Texh is an exhaust temperature, Pexh is an exhaust pressure, and φ represents an air density function. As stated above, the EGR actuator module 172 controls the EGR valve 170 based on the target EGR opening 292.
Referring back to
MAPT=T−1((TT+f(TEST_DIFF)),RPM,ST,ISEL,ESEL,AF,OT,#) (14)
where MAPT is the target MAP266, TT is the target torque 324, TEST_DIFF is the estimated torque difference 336, RPM is the engine speed, ST is the target spark timing 275, ISEL is the selected intake cam phaser angle 330, ESEL is the selected exhaust cam phaser angle 331, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, # is the present number of cylinders that are activated, and T−1 denotes inversion of relationship (1) above used to relate the MAP 279 to the MAP estimated torque 278. In various implementations, the target intake and exhaust cam phaser angles 270 and 271 may be used in place of the selected intake and exhaust cam phaser angles 330 and 331. This relationship may be embodied as an equation or as a look-up table. As noted above, generation of the selected intake and exhaust cam phaser angles 330 and 331 is discussed further below.
A difference module 340 determines the estimated torque difference 336. The difference module 340 determines the estimated torque difference 336 based on a difference between the MAP estimated torque 278 and the first APC estimated torque 283. The difference module 340 may also apply a filter to the difference between the MAP estimated torque 278 and the first APC estimated torque 283, such as a low pass filter, and output the filtered difference as the estimated torque difference 336.
As stated above, the boost control module 248 may generate the target duty cycle 269 based on the target MAP 266. The boost actuator module 164 controls the wastegate 162 (and therefore the turbocharger) based on the target duty cycle 269.
A target MAF module 344 generates a target MAF 348 into the engine 102 based on the first target APC 329. The target MAF module 344 generates the target MAF 348 further based on the engine speed and the total number of cylinders of the engine 102. For example, the target MAF module 344 may generate the target MAF 348 using the relationship:
where MAFT is the target MAF 348, APCT_1 is the first target APC 329, RPM is the engine speed, and kCYL is a predetermined value set based on the total number of cylinders of the engine 102. For example only, kCYL may be approximately 15 for an 8-cylinder engine and approximately 30 for a 4-cylinder engine.
A throttle control module 352 determines the target throttle opening 267 for the throttle valve 112 based on the target MAF 348. The throttle control module 352 determines the target throttle opening 267 further based on the target MAP 266, an air temperature, and a barometric pressure. For example, the throttle control module 352 may determine the target throttle opening 267 using the relationship:
where AREAT is the target throttle opening 267, MAFT is the target MAF 348, MAPT is the target MAP 266, RGAS is the ideal gas constant, T is the air temperature (e.g., ambient or intake), B is the barometric pressure, and φ represents an air density function. As stated above, the throttle actuator module 116 controls the throttle valve 112 based on the target throttle opening 267.
In sum, the throttle valve 112 and the turbocharger (if present) are controlled based on the target torque 324, which is generated based on the shaped air torque request 303 and the torque adjustment 316. The intake and exhaust cam phasers 148 and 150, however, are controlled based on the phaser target torque 412, which is generated based on the shaped air torque request 303 and the phaser target torque 412. Additionally, the EGR valve 170 will be controlled based on the air torque request 265 and the EGR target torque 436. This ensures that generation of the target torque 324, the phaser target torque 412, and the EGR target torque 436 is coordinated with the response characteristics of the throttle valve 112 and the turbocharger, the intake and exhaust cam phasers 148 and 150, and the EGR valve 170, respectively. This coordination may provide a steady-state and transient performance improvement.
Referring back to the target spark timing 275, the torque relationship (4) provided above may be inverted to solve for a spark APC (not shown). For example, the spark control module 232 may determine the spark APC using the relationship:
APCSPARK=T−1(TSPARK,RPM,SM,IT,ET,AF,OT,#) (17)
where APCSPARK is the spark APC, TSPARK is the spark torque request 272, RPM is the engine speed, SM is the present spark timing 280 being used by the spark actuator module 126, IT is the target intake cam phaser angle 270, ET is the target exhaust cam phaser angle 271, AF is the present air/fuel ratio being used by the fuel actuator module 124, OT is the oil temperature, # is the present number of cylinders that are activated, and T−1 denotes inversion of relationship (4) above used to relate the present APC 284 to the first APC estimated torque 283. This relationship may be embodied as an equation or as a look-up table.
The spark control module 232 determines the target spark timing 275 based on the spark APC and the engine speed. For example, the spark control module 232 may determine the target spark timing 275 using the relationship:
ST=f(APCSPARK,RPM), (18)
where ST is the target spark timing 275, APCSPARK is the spark APC, and RPM is the engine speed.
A selecting module 356 sets the selected intake and exhaust cam phaser angles 330 and 331 based on either the measured intake and exhaust cam phaser angles 281 and 282 or the target intake and exhaust cam phaser angles 270 and 271, respectively. More specifically, the selecting module 356 sets the selected intake cam phaser angle 330 based on either the measured intake cam phaser angle 281 or the target intake cam phaser angle 270 and sets the selected exhaust cam phaser angle 331 based on either the measured exhaust cam phaser angle 282 or the target exhaust cam phaser angle 271.
A selection signal 360 controls whether the selecting module 356 sets the selected intake and exhaust cam phaser angles 330 and 331 based on the measured intake and exhaust cam phaser angles 281 and 282 or based on the target intake and exhaust cam phaser angles 270 and 271. For example, the selecting module 356 may set the selected intake and exhaust cam phaser angles 330 and 331 based on the target intake and exhaust cam phaser angles 270 and 271 when the selection signal 360 is in a first state. When the selection signal 360 is in a second state, the selecting module 356 may set the selected intake and exhaust cam phaser angles 330 and 331 based on the measured intake and exhaust cam phaser angles 281 and 282.
When the selection signal 360 transitions from the first state to the second state or vice versa, the selecting module 356 may rate limit changes in the selected intake and exhaust cam phaser angles 330 and 331. For example, when the selection signal 360 transitions from the first state to the second state, the selecting module 356 may adjust the selected intake and exhaust cam phaser angles 330 and 331 toward the measured intake and exhaust cam phaser angles 281 and 282 by up to a first predetermined amount every predetermined period. When the selection signal 360 transitions from the second state to the first state, the selecting module 356 may adjust the selected intake and exhaust cam phaser angles 330 and 331 toward the target intake and exhaust cam phaser angles 270 and 271 by up to a second predetermined amount every predetermined period. The first and second predetermined amounts may be the same or different.
A selection generation module 364 generates the selection signal 360. The selection generation module 364 sums an APC torque difference 365 over a predetermined period (or a predetermined number of samples) to determine a cumulative difference. A second difference module 366 determines the APC torque difference 365. The second difference module 366 determines the APC torque difference 365 based on a difference between the first APC estimated torque 283 and the second APC estimated torque 298. The second difference module 366 may also apply a filter to the difference between the first APC estimated torque 283 and the second APC estimated torque 298, such as a low pass filter, and output the filtered difference as the APC torque difference 365.
The selection generation module 364 generates the selection signal 360 based on the cumulative difference. More specifically, the selection generation module 364 sets the selection signal 360 to the first state when the cumulative difference is less than a predetermined value. When the cumulative difference is greater than the predetermined value, the selection generation module 364 may set the selection signal 360 to the second state. In this manner the selecting module 356 sets the selected intake and exhaust cam phaser angles 330 and 331 based on the target intake and exhaust cam phaser angles 270 and 271 when the cumulative difference is less than the predetermined value. When the cumulative difference is greater than the predetermined value, the selecting module 356 may set the selected intake and exhaust cam phaser angles 330 and 331 based on the measured intake and exhaust cam phaser angles 281 and 282. This may ensure that use of the target intake and exhaust cam phaser angles 270 and 271 is limited to times when the target intake and exhaust cam phaser angles 270 and 271 are accurate, as indicated by the cumulative difference being less than the predetermined value.
Referring now to
The torque error module 304 generates the torque error 308 at 512. The torque error module 304 determines the torque error 308 based on a difference between the shaped air torque request 303 and the first APC estimated torque 283. The adjustment module 312 determines the P torque adjustment, the I torque adjustment 318, and the torque adjustment 316 at 516 based on the torque error 308. As discussed above in conjunction with (6), the adjustment module 312 may determine the P torque adjustment based on a product of the proportional gain (KP) and the torque error 308 and determine the I torque adjustment 318 based on a product of the torque error 308 and an integral gain (KI). The adjustment module 312 may set the torque adjustment 316 equal to the I torque adjustment 318 plus the P torque adjustment.
At 520, the target determination module 320 generates the target torque 324, the target phaser torque module 416 generates the phaser target torque 412, and the target EGR torque module 440 generates the EGR target torque 436. The target determination module 320 determines the target torque 324 based on the torque adjustment 316 and the shaped air torque request 303, as discussed above. The target phaser torque module 416 determines the phaser target torque 412 based on the shaped air torque request 303 and the phaser torque adjustment 420, as discussed above. The target EGR torque module 440 determines the EGR torque target 436 based on the air torque request 265 and the EGR torque adjustment 444, as described above.
At 528, the first APC determination module 404 determines the first target APC 329, the second APC determination module 408 determines the second target APC 268, and the third APC determination module 432 determines the third target APC 291. The first APC determination module 404 determines the first target APC 329 based on the target torque 324, as discussed above. The second APC determination module 408 determines the second target APC 268 based on the phaser target torque 412, as discussed above. The third APC determination module 432 determines the third target APC 291 based on the EGR target torque 436, as described above.
At 532, the target MAF module 344 generates the target MAF 348, the throttle control module 352 generates the target throttle opening 267, and the target MAP module 332 generates the target MAP 266. The target MAF module 344 determines the target MAF 348 based on the first target APC 329, as discussed above. The throttle control module 352 determines the target throttle opening 267 based on the target MAF 348, as discussed above. The target MAP module 332 determines the target MAP 266 based on the target torque 324, as discussed above.
Also at 532, the boost control module 248 generates the target duty cycle 269, the phaser control module 252 generates the target intake and exhaust cam phaser angles 270 and 271, and the EGR control module 253 generates the target EGR opening 292. The boost control module 248 determines the target duty cycle 269 based on the target MAP 266, as discussed above. The phaser control module 252 determines the target intake and exhaust cam phaser angles 270 and 271 based on the second target APC 268, as discussed above. The EGR control module 253 determines the target EGR opening 292 based on the third target APC 291, as discussed above.
At 536, the throttle actuator module 116 selectively adjusts the throttle valve 112 based on the target throttle opening 267, and the boost actuator module 164 selectively adjusts the duty cycle applied to the wastegate 162 based on the target duty cycle 269. Also at 536, the phaser actuator module 158 selectively adjusts the intake and exhaust cam phasers 148 and 150 based on the target intake and exhaust cam phaser angles 270 and 271, and the EGR actuator module 172 selectively adjusts the EGR valve 170 based on the target EGR opening 292. Control may then end. While control is shown and discussed as ending,
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical OR. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure.
As used herein, the term module may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC); a discrete circuit; an integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip. The term module may include memory (shared, dedicated, or group) that stores code executed by the processor.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, and/or objects. The term shared, as used above, means that some or all code from multiple modules may be executed using a single (shared) processor. In addition, some or all code from multiple modules may be stored by a single (shared) memory. The term group, as used above, means that some or all code from a single module may be executed using a group of processors. In addition, some or all code from a single module may be stored using a group of memories.
The apparatuses and methods described herein may be partially or fully implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on at least one non-transitory tangible computer readable medium. The computer programs may also include and/or rely on stored data. Non-limiting examples of the non-transitory tangible computer readable medium include nonvolatile memory, volatile memory, magnetic storage, and optical storage.
This application claims the benefit of U.S. Provisional Application No. 61/702,430, filed on Sep. 18, 2012. The disclosure of the above application is incorporated herein by reference in its entirety. This application is related to U.S. patent application Ser. No. 13/613,588, filed on Sep. 13, 2012, and U.S. patent application Ser. No. 13/613,683, filed on Sep. 13, 2012. The entire disclosures of the above applications are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4161929 | Nohira et al. | Jul 1979 | A |
| 5070846 | Dudek et al. | Dec 1991 | A |
| 5101786 | Kamio | Apr 1992 | A |
| 5293553 | Dudek et al. | Mar 1994 | A |
| 5706780 | Shirakawa | Jan 1998 | A |
| 5727528 | Hori | Mar 1998 | A |
| 5775293 | Kresse | Jul 1998 | A |
| 5921219 | Frohlich et al. | Jul 1999 | A |
| 6014955 | Hosotani | Jan 2000 | A |
| 6155230 | Iwano | Dec 2000 | A |
| 6532935 | Ganser | Mar 2003 | B2 |
| 6606981 | Itoyama | Aug 2003 | B2 |
| 6704638 | Livshiz et al. | Mar 2004 | B2 |
| 6714852 | Lorenz et al. | Mar 2004 | B1 |
| 6826904 | Miura | Dec 2004 | B2 |
| 6840215 | Livshiz et al. | Jan 2005 | B1 |
| 6985809 | Yasui | Jan 2006 | B2 |
| 7016779 | Bowyer | Mar 2006 | B2 |
| 7021282 | Livshiz et al. | Apr 2006 | B1 |
| 7051058 | Wagner | May 2006 | B2 |
| 7076953 | Kreso | Jul 2006 | B2 |
| 7274986 | Petridis et al. | Sep 2007 | B1 |
| 7275374 | Stewart et al. | Oct 2007 | B2 |
| 7328577 | Stewart et al. | Feb 2008 | B2 |
| 7395147 | Livshiz et al. | Jul 2008 | B2 |
| 7400967 | Ueno et al. | Jul 2008 | B2 |
| 7433775 | Livshiz et al. | Oct 2008 | B2 |
| 7441544 | Hagari | Oct 2008 | B2 |
| 7472692 | Nakagawa et al. | Jan 2009 | B2 |
| 7614384 | Livshiz et al. | Nov 2009 | B2 |
| 7650225 | Nakagawa et al. | Jan 2010 | B2 |
| 7703439 | Russell | Apr 2010 | B2 |
| 7715975 | Yamaoka et al. | May 2010 | B2 |
| 7775195 | Schondorf et al. | Aug 2010 | B2 |
| 7783409 | Kang et al. | Aug 2010 | B2 |
| 7813869 | Grichnik et al. | Oct 2010 | B2 |
| 7885756 | Livshiz et al. | Feb 2011 | B2 |
| 7941260 | Lee et al. | May 2011 | B2 |
| 7967720 | Martin et al. | Jun 2011 | B2 |
| 8041487 | Worthing et al. | Oct 2011 | B2 |
| 8050841 | Costin et al. | Nov 2011 | B2 |
| 8073610 | Heap et al. | Dec 2011 | B2 |
| 8103425 | Choi et al. | Jan 2012 | B2 |
| 8103428 | Russ et al. | Jan 2012 | B2 |
| 8116954 | Livshiz et al. | Feb 2012 | B2 |
| 8176735 | Komatsu | May 2012 | B2 |
| 8255139 | Whitney et al. | Aug 2012 | B2 |
| 8307814 | Leroy et al. | Nov 2012 | B2 |
| 8447492 | Watanabe et al. | May 2013 | B2 |
| 8468821 | Liu et al. | Jun 2013 | B2 |
| 8483935 | Whitney et al. | Jul 2013 | B2 |
| 8560204 | Simon, Jr. et al. | Oct 2013 | B2 |
| 8739766 | Jentz et al. | Jun 2014 | B2 |
| 8862248 | Yasui | Oct 2014 | B2 |
| 8954257 | Livshiz et al. | Feb 2015 | B2 |
| 9052997 | Ono | Jun 2015 | B2 |
| 9062631 | Kinugawa et al. | Jun 2015 | B2 |
| 9075406 | Nakada | Jul 2015 | B2 |
| 9127614 | Ueno et al. | Sep 2015 | B2 |
| 9145841 | Miyazaki et al. | Sep 2015 | B2 |
| 9175628 | Livshiz et al. | Nov 2015 | B2 |
| 9243524 | Whitney et al. | Jan 2016 | B2 |
| 20020038647 | Tashiro | Apr 2002 | A1 |
| 20020078924 | Yagi | Jun 2002 | A1 |
| 20020128116 | Idogawa | Sep 2002 | A1 |
| 20020179050 | Soliman et al. | Dec 2002 | A1 |
| 20030074892 | Miura | Apr 2003 | A1 |
| 20030110760 | Shirakawa | Jun 2003 | A1 |
| 20030145836 | Linna et al. | Aug 2003 | A1 |
| 20040116220 | Yamamoto | Jun 2004 | A1 |
| 20050065691 | Cho | Mar 2005 | A1 |
| 20050131620 | Bowyer | Jun 2005 | A1 |
| 20050166900 | Song et al. | Aug 2005 | A1 |
| 20050171670 | Yoshioka | Aug 2005 | A1 |
| 20050193739 | Brunell et al. | Sep 2005 | A1 |
| 20050267608 | Nishira et al. | Dec 2005 | A1 |
| 20060137335 | Stewart et al. | Jun 2006 | A1 |
| 20060199699 | Berglund et al. | Sep 2006 | A1 |
| 20070068159 | Ueno et al. | Mar 2007 | A1 |
| 20070174003 | Ueno et al. | Jul 2007 | A1 |
| 20080127938 | Hagari | Jun 2008 | A1 |
| 20080271718 | Schondorf et al. | Nov 2008 | A1 |
| 20080308066 | Martin et al. | Dec 2008 | A1 |
| 20090018733 | Livshiz et al. | Jan 2009 | A1 |
| 20090033264 | Falkenstein | Feb 2009 | A1 |
| 20090037066 | Kuwahara | Feb 2009 | A1 |
| 20090037073 | Jung | Feb 2009 | A1 |
| 20090118968 | Livshiz | May 2009 | A1 |
| 20090118969 | Heap et al. | May 2009 | A1 |
| 20090118972 | Baur | May 2009 | A1 |
| 20090143959 | Yamaoka et al. | Jun 2009 | A1 |
| 20090229562 | Ramappan et al. | Sep 2009 | A1 |
| 20090292435 | Costin et al. | Nov 2009 | A1 |
| 20100049419 | Yoshikawa | Feb 2010 | A1 |
| 20100057283 | Worthing et al. | Mar 2010 | A1 |
| 20100057329 | Livshiz et al. | Mar 2010 | A1 |
| 20100075803 | Sharples | Mar 2010 | A1 |
| 20100116249 | Guerrassi et al. | May 2010 | A1 |
| 20100116250 | Simon, Jr. | May 2010 | A1 |
| 20100180876 | Leroy et al. | Jul 2010 | A1 |
| 20100211294 | Soejima | Aug 2010 | A1 |
| 20100241335 | Aso | Sep 2010 | A1 |
| 20100263627 | Whitney | Oct 2010 | A1 |
| 20100268436 | Soejima et al. | Oct 2010 | A1 |
| 20100280738 | Whitney | Nov 2010 | A1 |
| 20110034298 | Doering | Feb 2011 | A1 |
| 20110045948 | Doering et al. | Feb 2011 | A1 |
| 20110066308 | Yang et al. | Mar 2011 | A1 |
| 20110082629 | Soejima | Apr 2011 | A1 |
| 20110087421 | Soejima | Apr 2011 | A1 |
| 20110100013 | Whitney et al. | May 2011 | A1 |
| 20110113773 | Liu et al. | May 2011 | A1 |
| 20110125390 | Bellinger | May 2011 | A1 |
| 20110144838 | Matthews et al. | Jun 2011 | A1 |
| 20110264353 | Atkinson et al. | Oct 2011 | A1 |
| 20120065864 | Whitney et al. | Mar 2012 | A1 |
| 20120150399 | Kar | Jun 2012 | A1 |
| 20120203434 | Sujan et al. | Aug 2012 | A1 |
| 20130032123 | Kinugawa et al. | Feb 2013 | A1 |
| 20130032127 | Jentz et al. | Feb 2013 | A1 |
| 20130060448 | Nakada | Mar 2013 | A1 |
| 20130080023 | Livshiz | Mar 2013 | A1 |
| 20130104859 | Miyazaki et al. | May 2013 | A1 |
| 20130151124 | Seiberlich et al. | Jun 2013 | A1 |
| 20130184961 | Kumar et al. | Jul 2013 | A1 |
| 20130213353 | Rollinger et al. | Aug 2013 | A1 |
| 20130255625 | Kar | Oct 2013 | A1 |
| 20140076279 | Livshiz et al. | Mar 2014 | A1 |
| 20140123938 | Whitney | May 2014 | A1 |
| 20140174413 | Huang et al. | Jun 2014 | A1 |
| 20140174414 | Huang et al. | Jun 2014 | A1 |
| 20140311446 | Whitney | Oct 2014 | A1 |
| 20140316681 | Whitney | Oct 2014 | A1 |
| 20140316682 | Whitney | Oct 2014 | A1 |
| 20140316683 | Whitney | Oct 2014 | A1 |
| 20150039206 | Storch et al. | Feb 2015 | A1 |
| 20150275569 | LeBlanc | Oct 2015 | A1 |
| 20150275711 | Whitney et al. | Oct 2015 | A1 |
| 20150275771 | Pochner et al. | Oct 2015 | A1 |
| 20150275772 | Long et al. | Oct 2015 | A1 |
| 20150275783 | Wong et al. | Oct 2015 | A1 |
| 20150275784 | Whitney et al. | Oct 2015 | A1 |
| 20150275785 | Cygan, Jr. et al. | Oct 2015 | A1 |
| 20150275786 | Jin et al. | Oct 2015 | A1 |
| 20150275789 | Cygan, Jr. et al. | Oct 2015 | A1 |
| 20150275792 | Genslak et al. | Oct 2015 | A1 |
| 20150275794 | Verdejo et al. | Oct 2015 | A1 |
| 20150275795 | Cygan, Jr. et al. | Oct 2015 | A1 |
| 20150275796 | Pochner et al. | Oct 2015 | A1 |
| 20150275806 | Genslak et al. | Oct 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 1594846 | Mar 2005 | CN |
| WO-03-065135 | Aug 2003 | WO |
| Entry |
|---|
| U.S. Appl. No. 14/225,492, filed Mar. 26, 2014, Wong et al. |
| U.S. Appl. No. 14/225,496, filed Mar. 26, 2014, Pochner et al. |
| U.S. Appl. No. 14/225,502, filed Mar. 26, 2014, Long et al. |
| U.S. Appl. No. 14/225,507, filed Mar. 26, 2014, Jin et al. |
| U.S. Appl. No. 14/225,516, filed Mar. 26, 2014, Whitney et al. |
| U.S. Appl. No. 14/225,531, filed Mar. 26, 2014, Genslak et al. |
| U.S. Appl. No. 14/225,569, filed Mar. 26, 2014, Long et al. |
| U.S. Appl. No. 14/225,587, filed Mar. 26, 2014, Cygan Jr. et al. |
| U.S. Appl. No. 14/225,626, filed Mar. 26, 2014, Verdejo et al. |
| U.S. Appl. No. 14/225,808, filed Mar. 26, 2014, Whitney et al. |
| U.S. Appl. No. 14/225,817, filed Mar. 26, 2014, Cygan Jr. et al. |
| U.S. Appl. No. 14/225,891, filed Mar. 26, 2014, Genslak et al. |
| U.S. Appl. No. 14/225,896, filed Mar. 26, 2014, Cygan Jr. et al. |
| U.S. Appl. No. 14/226,006, filed Mar. 26, 2014, Pochner et al. |
| U.S. Appl. No. 14/226,121, filed Mar. 26, 2014, Wong et al. |
| U.S. Appl. No. 13/613,588, Livshiz et al. |
| U.S. Appl. No. 13/613,683, Livshiz et al. |
| U.S. Appl. No. 14/675,828, filed Apr. 1, 2015, Long et al. |
| U.S. Appl. No. 14/675,860, filed Apr. 2001, Long et al. |
| John C. G. Boot; “Quadratic Programming: Algorithms, Anomalies, Applications vol. 2 of Studies in mathematical and managerial economics”; North-Holland Publ.Comp., 1964; 213 pages. |
| N. Lawrence Ricker; “Use of quadratic programming for constrained internal model control”; Ind. Eng. Chem. Process Des. Dev., 1985, pp. 925-936. |
| C. E. Lemke; “A Method of Solution for Quadratic Programs”; Rensselaer Polytechnic Institute, Troy, New York, Published Online: Jul. 1, 1962, pp. 442-453. |
| U.S. Appl. No. 14/309,047, filed Jun. 19, 2014, Jose C. Zavala Jurado et al. |
| U.S. Appl. No. 14/617,068, filed Feb. 9, 2015, Whitney et al. |
| U.S. Appl. No. 13/911,121, Whitney et al. |
| U.S. Appl. No. 13/911,132, Whitney et al. |
| U.S. Appl. No. 13/911,148, Whitney et al. |
| U.S. Appl. No. 13/911,156, Whitney et al. |
| U.S. Appl. No. 14/032,508, Storch et al. |
| Kolmanovsky, I., “Towards Engine and Powertrain Control Based on Model Predictive Control,” (Sep. 28, 2012), Powerpoint Presentation, 47 slides. |
| U.S. Appl. No. 14/931,134, filed Nov. 3, 2015, Wong et al. |
| Number | Date | Country | |
|---|---|---|---|
| 20140076279 A1 | Mar 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61702430 | Sep 2012 | US |
