This application is related to U.S. patent application Ser. No. 13/590,351 filed on Aug. 21, 2012. The disclosure of the above related application is incorporated herein by reference in its entirety.
The present disclosure relates to internal combustion engines and more particularly to systems and methods for identifying faults in a valvetrain.
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.
Vehicles include an internal combustion engine that generates drive torque. An intake valve is selectively opened to draw air into a cylinder of the engine. The air mixes with fuel to form an air/fuel mixture. The air/fuel mixture is combusted within the cylinder. An exhaust valve is selectively opened to allow the exhaust gas resulting from combustion to exit the cylinder.
One or more rotating camshafts regulate the opening and closing of the intake and/or exhaust valves. The camshafts include cam lobes that are fixed to and rotate with the camshafts. The geometric profile of a cam lobe determines a valve opening schedule. More specifically, the geometric profile of a cam lobe generally controls the period that the valve is open (duration) and the amount or distance (lift) that the valve opens.
Variable valve actuation (WA) and variable valve lift (VVL) improve fuel economy, engine efficiency, and/or performance by modifying valve duration and lift, respectively, as a function of engine operating conditions. Two-step VVL systems include VVL mechanisms, such as hydraulically-controlled, switchable roller finger followers (SRFFs). A SRFF associated with a valve (e.g., the intake or exhaust valves) allows the valve to be lifted in two discrete states: a low lift state and a high lift state. The valve lift associated with the high lift state is greater than the valve lift associated with the low lift state.
A system for a vehicle includes a misfire indication module, a valve control module, and a fault indication module. The misfire indication module selectively indicates that misfire occurred within a cylinder of an engine. The valve control module controls lifting of a valve of a cylinder of the engine and, in response to the misfire indication module indicating that misfire occurred within the cylinder, transitions lifting of the valve from one of a low lift state and a high lift state to the other one of the low lift state and the high lift state. The fault indication module selectively indicates that a fault is present in a variable valve lift (VVL) mechanism of the cylinder based on whether the misfire indication module indicates that misfire occurred within the cylinder after the transition to the other one of the low lift state and the high lift state.
A method for a vehicle includes: selectively indicating that misfire occurred within a cylinder of an engine; and controlling lifting of a valve of a cylinder of the engine. The method further includes: in response to an indication that misfire occurred within the cylinder, transitioning lifting of the valve from one of a low lift state and a high lift state to the other one of the low lift state and the high lift state. The method further includes: selectively indicating that a fault is present in a variable valve lift (VVL) mechanism of the cylinder based on whether occurrence of misfire within the cylinder is indicated after the transition to the other one of the low lift state and the high lift state.
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 combusts an air/fuel mixture within cylinders to generate drive torque. Air flows into a cylinder through an intake valve. Exhaust flows out of a cylinder through an exhaust valve. Each cylinder may include one or more intake valves and one or more exhaust valves.
A variable valve lift (VVL) mechanism enables operation of an associated valve (e.g., an intake valve or an exhaust valve) in two discrete lift states: a high lift state and a low lift state. During operation in the low lift state, the VVL mechanism opens the valve a first distance. The VVL mechanism opens the valve a second distance during operation in the high lift state, and the second distance is greater than the first distance.
A cylinder with a faulty VVL mechanism will have different combustion characteristics (e.g., burn rate) than other cylinders. For example, a cylinder with a faulty VVL mechanism may exhibit a greater level of misfire than one or more other cylinders. The present disclosure describes systems and methods for detecting and indicating whether a fault is present in a VVL mechanism of a cylinder based on engine misfire.
Referring now to
A cylinder 114 includes a piston (not shown) that is coupled to a crankshaft 116. Although the engine 102 is depicted as including only the cylinder 114, the engine 102 may include more than one cylinder. The fuel injectors may inject fuel directly into the cylinders or at another suitable location. One combustion cycle of the cylinder 114 may include four strokes: an intake stroke, a compression stroke, an expansion stroke, and an exhaust stroke. During one revolution of the crankshaft 116 (i.e., 360 degrees of crankshaft rotation), two of the four strokes can occur. One engine cycle includes each of the cylinders undergoing one combustion cycle and occurs over two revolutions of the crankshaft 116 (i.e., 720 degrees of crankshaft rotation).
Referring also to
During the compression stroke, the crankshaft 116 drives the piston toward a top most position. The top most position may be referred to as a top dead center (TDC) position. The intake valve 118 and the exhaust valve 120 are both closed during the compression stroke, and the piston compresses the contents of the cylinder 114. A spark plug 122 may ignite the air/fuel mixture. A spark actuator module 124 controls the spark plugs of the engine 102. The spark plugs may be omitted in various types of engines.
Combustion of the air/fuel mixture drives the piston back toward the BDC position during the expansion stroke. The piston drives the crankshaft 116. The rotational force (i.e., torque) on the crankshaft 116 from combustion of the air/fuel mixture may be a source of compressive force for a compression stroke of a combustion cycle of a next cylinder in a predetermined firing order of the cylinders.
Exhaust resulting from the combustion of the air/fuel mixture is expelled from the cylinder 114 during the exhaust stroke. The exhaust is expelled from the cylinder 114 via the exhaust valve 120. While the engine 102 is described as a four-stroke, spark ignition engine, the engine 102 may be another suitable type of engine. One or more electric motors may be provided with the engine 102.
The timing of opening and closing of the intake valve 118 is regulated by an intake camshaft 126. An intake camshaft, such as the intake camshaft 126, may be provided for each bank of cylinders of the engine 102. The timing of opening and closing of the exhaust valve 120 is regulated by an exhaust camshaft 127. An exhaust camshaft (not shown) may be provided for each bank of cylinders of the engine 102. Rotation of the intake camshaft(s) and the exhaust camshaft(s) is generally driven by rotation of the crankshaft 116, such as by a belt or a chain.
A cam phaser regulates rotation of an associated camshaft. For example only, intake cam phaser 128 regulates rotation of the intake camshaft 126. The intake cam phaser 128 may adjust the rotation of the intake camshaft 126, for example, with respect to rotation of the crankshaft 116, with respect to a position of the piston, with respect to another camshaft, etc. For example only, the intake cam phaser 128 may retard or advance rotation of the intake camshaft 126, thereby changing the opening and closing timing of the intake valve 118. An exhaust cam phaser 129 regulates rotation of the exhaust camshaft 127. Adjusting rotation of a camshaft with respect to rotation of the crankshaft 116 may be referred to as camshaft phasing.
A valve actuator module 130 controls the intake cam phaser 128. The valve actuator module 130 or another actuator module may control operation of the exhaust cam phaser 129. A cam phaser may be electrically or hydraulically actuated. Hydraulically actuated cam phasers operate based on pressure of a hydraulic fluid (e.g., oil) supplied to the cam phaser. Electrically actuated cam phasers operate using electrical power.
A variable valve lift (VVL) mechanism 136 (
The VVL mechanism 136 includes a lift adjuster 138 and a cam follower 140. The cam follower 140 is in mechanical contact with a valve stem 142 of the intake valve 118. A biasing device 143 biases the valve stem 142 into contact with the cam follower 140. The cam follower 140 is also in mechanical contact with the intake camshaft 126 and the lift adjuster 138.
The intake camshaft 126 rotates about a camshaft axis 144. The intake camshaft 126 includes a plurality of cam lobes including low lift cam lobes and high lift cam lobes, such as low lift cam lobe 146 and high lift cam lobe 148. For example only, the intake camshaft 126 may include one low lift cam lobe and one high lift cam lobe for each intake valve of each cylinder. The exhaust camshaft 127 may include one low lift cam lobe and one high lift cam lobe for each exhaust valve of each cylinder. While only lifting of the intake valve 118 will be discussed, the present application is also applicable to exhaust valves and other intake valves.
The low and high lift cam lobes 146 and 148 rotate with the intake camshaft 126. Air may flow into the cylinder 114 through an inlet passage 150 when the intake valve 118 is open. Airflow into the cylinder 114 through the inlet passage 150 is blocked when the intake valve 118 is closed. The intake valve 118 is selectively opened and closed via the intake camshaft 126. More specifically, one of the low lift cam lobe 146 and the high lift cam lobe 148 opens and closes the intake valve 118 during a given combustion cycle.
A cam lobe contacting the cam follower 140 applies a force to the cam follower 140 in the direction of the valve stem 142 and the lift adjuster 138. The cam follower 140 may also be referred to as a rocker arm. The lift adjuster 138 is collapsible to allow the intake valve 118 to be opened to two discrete positions, a low lift position and high lift position. Pressure of a hydraulic fluid 152 may be controlled to control which one of the low lift cam lobe 146 and the high lift cam lobe 148 opens the intake valve 118 during a given combustion cycle.
During operation of the intake valve 118 in the low lift state, the low lift cam lobe 146 causes the VVL mechanism 136 to pivot in accordance with the geometry of the low lift cam lobe 146. The pivoting of the VVL mechanism 136 caused by the low lift cam lobe 146 opens the intake valve 118 a first predetermined amount or distance. During operation in the high lift state, the high lift cam lobe 148 causes the VVL mechanism 136 to pivot in accordance with the geometry of the high lift cam lobe 148. The pivoting of the VVL mechanism 136 caused by the high lift cam lobe 148 opens the intake valve 118 a second predetermined amount or distance. The second predetermined amount or distance is greater than the first predetermined amount or distance.
A fluid control valve 154 regulates the pressure of the hydraulic fluid 152. The valve actuator module 130 or another actuator module controls the fluid control valve 154 to control the pressure of the hydraulic fluid 152. The fluid control valve 154 may also be referred to as an oil control valve (OCV).
A crankshaft position sensor 160 (
A manifold absolute pressure (MAP) sensor 164 monitors pressure within the intake manifold 104 and generates a MAP signal based on the pressure. In various implementations, vacuum within the intake manifold 104 may be measured, where the vacuum is measured relative to ambient pressure. A mass air flowrate (MAF) sensor 166 monitors mass flowrate of air flowing through the throttle valve 106 and generates a MAF signal based on the mass flowrate.
A cylinder pressure sensor 168 measures pressure within the cylinder 114 and generates a cylinder pressure signal based on the pressure within the cylinder 114. A cylinder pressure sensor may be provided for each cylinder of the engine 102. In various implementations, cylinder pressure sensors may be omitted. One or more other sensors may also be implemented.
The engine 102 transfers torque to a transmission 170. The transmission 170 may include a manual type transmission, an automatic type transmission, an auto-manual type transmission, or another suitable type of transmission. The transmission 170 may transfer torque to one or more wheels (not shown) via a transmission output shaft 172 and a driveline (not shown).
An engine control module (ECM) 180 controls operation of the engine 102. More specifically, the ECM 180 controls the throttle valve 106 via the throttle actuator module 108 and controls the fuel injectors via the fuel actuator module 112. The ECM 180 controls the spark plugs via the spark actuator module 124. The ECM 180 controls phasing of the intake and exhaust valves via the valve actuator module 130. The ECM 180 may also control lifting of the intake and exhaust valve via the valve actuator module 130.
The ECM 180 selectively learns the distance between each pair of consecutive teeth of the N-toothed wheel 162. Based on the learned distances and the crankshaft position signal, the ECM 180 generates a second crankshaft position signal. The ECM 180 generates an engine speed signal based on the second crankshaft position signal. The engine speed signal at a given crankshaft position indicates instantaneous engine speed at the crankshaft position.
The ECM 180 may determine an indicated work of a combustion cycle of the cylinder 114 based on squares of two or more instantaneous engine speeds at predetermined crankshaft positions of the combustion cycle, respectively. The ECM 180 may determine an indicated mean effective pressure (IMEP) for the combustion cycle of the cylinder 114 based on the indicated work and a displacement volume of the engine 102. The ECM 180 determines an IMEP for each combustion cycle of each cylinder of the engine 102. In various implementations, the ECM 180 may determine the IMEPs based on cylinder pressures measured by cylinder pressure sensors.
Based on the IMEPs, the ECM 180 may determine whether engine misfire occurred during the combustion cycle and perform one or more other actions, such as adjusting one or more engine operating parameters. For example only, engine operating parameters may include camshaft phasing based on a crankshaft angle at which 50% of the fuel will be burnt (CA50) within the cylinder 114, intake and/or exhaust valve lift state, ignition timing, and/or one or more other suitable engine operating parameters.
The ECM 180 may determine a coefficient of variation (COV) for the cylinder 114 using the IMEP and a predetermined number of previous IMEPs determined for previous combustion cycles of the cylinder 114, respectively. The ECM 180 may determine a COV for each cylinder. The ECM 180 determines and indicates whether misfire occurred within a cylinder based on the cylinder's COV.
Referring now to
For example, a throttle control module 212 may determine a desired throttle opening 216 based on the driver torque request 208. The throttle actuator module 108 may adjust opening of the throttle valve 106 based on the desired throttle opening 216. A spark control module 220 may determine a desired spark timing 224 based on the driver torque request 208. The spark actuator module 124 may generate spark based on the desired spark timing 224.
A fuel control module 228 may determine one or more desired fueling parameters 232 based on the driver torque request 208. For example, the desired fueling parameters 232 may include fuel injection timing and amount. The fuel actuator module 112 may actuate the fuel injectors to inject fuel based on the desired fueling parameters 232.
A valve control module 236 may determine a desired lift state 240, a desired intake phase angle 244, and a desired exhaust phase angle 248 based on the driver torque request 208. The desired lift state 240 may be one of the high lift state and the low lift state. The valve actuator module 130 controls operation of the valves in the high lift state or the low lift state at a given time based on the desired lift state 240. The valve actuator module 130 may control intake and exhaust camshaft phasing based on the desired intake and exhaust phase angles 244 and 248, respectively.
A filter module 252 generates estimates of the (instantaneous) crankshaft position, the (instantaneous) engine speed, and the crankshaft acceleration based on a crankshaft position 256 generated using the crankshaft position sensor 160. The filter module 252 generates a crankshaft position (not specifically shown), an engine speed 260, and an acceleration (not specifically shown) to indicate the estimates, respectively. The filter module 252 may generate the estimates using, for example, a Kalman based filter, a Chebyshev based filter, a Butterworth type II based filter, or another suitable type of filter.
An IMEP module 264 determines an IMEP 268 for the combustion cycle of the cylinder 114. The IMEP module 264 may determine the IMEP 268 for a combustion cycle based on an indicated work for the combustion cycle. The IMEP module 264 determines the IMEP 268 for the combustion cycle further based on a displacement volume of the engine 102. The IMEP module 264 may determine the indicated work for the combustion cycle of the cylinder 114 based on squares of two or more of values of the engine speed 260 at predetermined crankshaft positions of the combustion cycle, respectively. The IMEP module 264 determines the indicated work and the IMEP 268 for each combustion cycle of each of cylinder of the engine 102. In various implementations, the IMEP module 264 may determine the indicated work and/or the IMEP 268 based on cylinder pressures measured using cylinder pressure sensors.
A coefficient of variation (COV) module 272 determines a COV 276 for the cylinder 114 based on a predetermined number of values of the IMEP 268 determined for a predetermined number of previous (e.g., most recent) combustion cycles of the cylinder 114, respectively. The COV module 272 may, for example, set the COV 276 equal to a standard deviation of the predetermined number of values of the IMEP 268 divided by an average of the values of the IMEP 268. The COV module 272 determines a COV for each cylinder based on the cylinders' IMEP values, respectively.
A misfire indication module 280 indicates whether misfire occurred within the cylinder 114 based on the COV 276 of the cylinder 114. The misfire indication module 280 generates misfire data 284 indicating whether misfire occurred within the cylinder 114. The misfire indication module 280 also determines whether misfire occurred in each other cylinder based on each cylinder's respective COV and generates the misfire data 284 accordingly. For example, the misfire indication module 280 may determine and indicate that misfire occurred within a cylinder when the cylinder's COV is greater than a predetermined value. For example only, the misfire indication module 280 may indicate that misfire occurred within a cylinder when the cylinder's COV is 18 percent (%) or more.
A cylinder with a faulty VVL mechanism will have different combustion characteristics (e.g., burn rate) than other cylinders. For example, a cylinder with a faulty VVL mechanism may exhibit a greater level of misfire than one or more other cylinders. A cylinder with a faulty VVL mechanism may, for example, exhibit misfire more frequently than cylinders with reliable VVL mechanisms, a cylinder with a faulty VVL mechanism may exhibit more observable misfire (e.g., a greater COV) than cylinders with reliable VVL mechanisms.
When a VVL mechanism is faulty, the associated valve will be stuck in operation in one of the high lift state and the low lift state, regardless of whether the desired lift state 240 is the high lift state or the low lift state. For example, when the VVL mechanism is faulty, the associated valve may be stuck operating in the high lift state both when the desired lift state 240 is the high lift state and when the desired lift state 240 is the low lift state.
A storage module 288 stores the misfire data 284 for the cylinders. For example, the storage module 288 may track a number of times that the misfire indication module 280 indicated that misfire occurred for each cylinder over a predetermined period or a predetermined number of engine cycles. The storage module 288 may also store the value of the COV 276 for each cylinder.
A fault detection module 290 may include a transition command module 292 and a fault indication module 294. When one or more enabling conditions are satisfied, the transition command module 292 commands the valve control module 236 to transition the desired lift state 240 to the other one of the lift states. For example only, the transition command module 292 may command the valve control module 236 to perform the transition when the COV of a cylinder is greater than the predetermined value, the COV of a cylinder is greater than the COF of one or more other cylinders by at least a predetermined amount, and/or when one or more misfires are detected by the misfire indication module 280.
When the desired lift state 240 is set to the high lift state, the valve control module 236 transitions the desired lift state 240 to the low lift state in response to the command. When the desired lift state 240 is set to the low lift state, the valve control module 236 transitions the desired lift state to the high lift state in response to the command.
When the desired lift state 240 is set to the low lift state and the valve control module 236 transitions the desired lift state 240 to the high lift state in response to the command, the transition command module 292 may also command the spark control module 220 to adjust spark timing and command the valve control module 236 to adjust intake and/or exhaust cam phasing. The transition command module 292 may, for example, command the spark control module 220 to adjust the spark timing to a predetermined timing by adjusting the desired spark timing 224 by a predetermined amount each combustion cycle. When the desired lift state 240 is set to the low lift state initially, the transition command module 292 may also command the valve control module 236 to adjust intake and/or exhaust cam phasing to achieve predetermined phase angles by adjusting the desired intake and exhaust phase angles 244 and 248, respectively, by a predetermined amount each combustion cycle. The predetermined timing for the spark timing and the predetermined phase angles for intake and/or exhaust cam phasing may be predetermined, calibrated values that make misfire more observable during operation in the high lift state.
When the desired lift state 240 is set to the high lift state when the command is received, adjustments to the spark timing and/or the intake and exhaust phase angles may not be performed. Misfire may be readily observable during operation in the low lift state (that is, after a transition from the high lift state to the low lift state) without adjustments to spark timing and/or intake and/or exhaust cam phasing.
In response to the transition to the other one of the lift states, the fault indication module 294 monitors whether misfire occurs in one or more cylinders. The fault indication module 294 may wait a predetermined period or a predetermined number of engine cycles after the transition to the other one of the lift states before performing the monitoring.
The fault indication module 294 indicates whether a fault is present in a VVL mechanism of the cylinder based on whether a cylinder that experienced misfire before the transition to the other one of the lift states continues to experience misfire after the transition. For example, the fault indication module 294 may indicate that a fault is present in a VVL mechanism when a cylinder that experienced misfire before the transition does not experience misfire after the transition. When the cylinder continues to experience misfire after the transition, the fault indication module 294 may indicate that no fault is present in a VVL mechanism.
In various implementations, a second transition in the desired lift state 240 may be performed when the cylinder does not exhibit misfire after the transition to the other one of the lift states. In other words, the desired lift state 240 may be transitioned back to the initial one of the lift states. The second transition may be performed, for example, to verify the presence of a fault in the VVL mechanism by verifying that the cylinder experiences misfire during operation one of the lift states and does not experience misfire during operation in the other one of the lift states.
The fault indication module 294 may indicate whether a fault is present in a VVL mechanism of the cylinder based on whether the cylinder experiences misfire after the second transition. For example, the fault indication module 294 may indicate that a fault is present in a VVL mechanism of the cylinder when the cylinder experiences misfire after the second transition. When the cylinder does not experience misfire after the second transition, the fault indication module 294 may indicate that no fault is present in a VVL mechanism. The fault indication module 294 may again wait a predetermined period or a predetermined number of engine cycles after the second transition to the other one of the lift states before performing the monitoring.
The fault indication module 294 indicates whether a fault is present in a VVL mechanism of the cylinder via a VVL mechanism fault indicator 295. For example, the fault indication module 294 may set the VVL mechanism fault indicator 295 to an active state in memory 296 when a fault is present in a VVL mechanism of the cylinder. The fault indication module 294 may set the VVL mechanism fault indicator 295 to an inactive state when a fault is not present in a VVL mechanism. For example, the VVL mechanism fault indicator 295 may be a predetermined diagnostic trouble code (DTC) associated with a fault in a VVL mechanism of the cylinder. The fault in the VVL mechanism may be, for example, a broken rocker arm.
The fault indication module 294 may also generate the VVL mechanism fault indicator 295 that indicates whether the faulty VVL mechanism is stuck in operation in the high lift state or the low lift state. When the cylinder stops experiencing misfire after the transition and/or experiences misfire after the second transition, the fault indication module 294 may indicate that the VVL mechanism is stuck operating the associated valve in the initial lift state. For example, when the desired lift state 240 was first transitioned from the low lift state to the high lift state and second transitioned from the high lift state to the low lift state, the fault indication module 294 may indicate that the VVL mechanism is stuck in the low lift state when the cylinder stops experiencing misfire after the first transition to the high lift state and/or the cylinder experiencing misfire after the second transition to the low lift state.
A monitoring module 297 may monitor generation of the VVL mechanism fault indicator 295 and/or one or more other fault indicators. In response to generation of the VVL mechanism fault indicator 295, the monitoring module 297 may, for example, illuminate a malfunction indicator lamp (MIL) 298. Based on the VVL mechanism fault indicator 295, a vehicle servicer can identify and replace the VVL mechanism that includes the fault and that caused the misfire.
One or more other remedial actions may be taken in response to generation of the VVL mechanism fault indicator 295. For example only, the valve control module 236 may limit setting of the desired lift state 240 to the one of the lift states that the VVL mechanism is stuck. For example, when the fault indication module 294 indicates that the VVL mechanism is stuck in the low lift state, the valve control module 236 may set the desired lift state 240 only to the low lift state and refrain from setting the desired lift state 240 to the high lift state.
Referring now to
At 306, control may determine whether the lift state is currently the low lift state. If false, control may selectively adjust the spark timing, the intake cam phase angle, and/or the exhaust phase cam angle at 308 and proceed with 312. If true, control may transfer to 312.
At 312, control transitions the desired lift state 240 to the other one of the lift states. For example, if the desired lift state 240 is in the low lift state, control transitions the desired lift state 240 to the high lift state, and vice versa. At 316, control may determine whether the cylinder (that experienced misfire before the transition) is still experiencing misfire. If false, control may indicate that a fault is present in a VVL mechanism of the cylinder at 320, and control may end. Control may also indicate that the VVL mechanism is stuck in operation in the one of lift states from before the transition at 320. For example, if the desired lift state 240 was in the low lift state before the transition, control may indicate that the VVL mechanism is stuck in operation in the low lift state at 320. If true at 316, control may indicate that no fault is present in the VVL mechanisms of the engine 102 at 324, and control may end.
One or more remedial actions may be taken when a fault is present in a VVL mechanism of the cylinder. For example, control may limit the desired lift state 240 to the one of the lift states in which the VVL mechanism is stuck and prevent the desired lift state 240 from being transitioned to the other one of the lift states. Additionally or alternatively, control may illuminate the MIL 298.
Referring now to
At 406, control may determine whether the lift state is currently the low lift state. If false, control may selectively adjust the spark timing, the intake cam phase angle, and/or the exhaust phase cam angle at 408, and control may proceed with 412. If true, control may transfer to 412.
Control may determine whether one or more cylinders have experienced a greater level of misfire than one or more other cylinders at 412. For example, control may determine whether a number of misfires that have occurred within a cylinder during a predetermined period or a predetermined number of engine cycles is greater than a number of misfires that have occurred within one or more other cylinders during the period or number of engine cycles at 412. Control may require the number of misfires to be greater than the number of misfires in the one or more other cylinders by at least a predetermined amount. If true, control may continue with 416-428. If false, control may continue with 432-444, which are discussed further below.
Control transitions the desired lift state 240 to the other one of the lift states at 416. For example, if the desired lift state 240 is in the low lift state, control transitions the desired lift state 240 to the high lift state, and vice versa. At 420, control may determine whether the one or more cylinders (that experienced a greater level of misfire than one or more other cylinders before the transition) is/are still experiencing a greater level of misfire than one or more other cylinders. If false, control may indicate that a fault is present in a VVL mechanism of the cylinder at 428, and control may end. Control may also indicate that the VVL mechanism is stuck in operation in the one of lift states from before the transition at 428. For example, if the desired lift state 240 was in the low lift state before the transition, control may indicate that the VVL mechanism is stuck in operation in the low lift state at 428. If true at 420, control may indicate that no fault is present in the VVL mechanisms of the cylinder at 424, and control may end.
As stated above, when 412 is false, control may continue with 432-444. At 432, control transitions the desired lift state 240 to the other one of the lift states. For example, if the desired lift state 240 is in the low lift state, control transitions the desired lift state 240 to the high lift state, and vice versa.
At 436, control may determine whether one or more cylinders have, after the transition, experienced a greater level of misfire than one or more other cylinders while not experiencing a greater level of misfire before the transition. For example, control may determine whether a number of misfires that have occurred within a cylinder during a predetermined period or a predetermined number of engine cycles is greater than a number of misfires that have occurred within one or more other cylinders during the period or number of engine cycles at 412. Control may require the number of misfires to be greater than the number of misfires in the one or more other cylinders by at least a predetermined amount. If true, control may indicate that a fault is present in a VVL mechanism of the cylinder at 440, and control may end. Control may also indicate that the VVL mechanism is stuck in operation in the one of lift states from before the transition at 440. For example, if the desired lift state 240 was in the low lift state before the transition, control may indicate that the VVL mechanism is stuck in operation in the low lift state at 440. If true at 436, control may indicate that no fault is present in the VVL mechanisms of the engine 102 at 444, and control may end.
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); an electronic 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 implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on a non-transitory tangible computer readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage.
Number | Name | Date | Kind |
---|---|---|---|
3923021 | Stark | Dec 1975 | A |
4233943 | Rogora et al. | Nov 1980 | A |
4525781 | Konomi et al. | Jun 1985 | A |
4587938 | Kobayashi et al. | May 1986 | A |
4658787 | Takizawa | Apr 1987 | A |
4691677 | Hotate et al. | Sep 1987 | A |
4716873 | Takaba et al. | Jan 1988 | A |
4730587 | Norota et al. | Mar 1988 | A |
4760825 | Morita | Aug 1988 | A |
4763264 | Okuno et al. | Aug 1988 | A |
4788942 | Pouring et al. | Dec 1988 | A |
4915076 | Takizawa | Apr 1990 | A |
4919096 | Manaka et al. | Apr 1990 | A |
5005547 | Suga et al. | Apr 1991 | A |
5046468 | Erhard | Sep 1991 | A |
5074810 | Hobbs et al. | Dec 1991 | A |
5107813 | Inoue et al. | Apr 1992 | A |
5110310 | Hobbs | May 1992 | A |
5229945 | Demizu et al. | Jul 1993 | A |
5408863 | Sawyers et al. | Apr 1995 | A |
5477826 | Hara et al. | Dec 1995 | A |
5632247 | Hashizume et al. | May 1997 | A |
5699253 | Puskorius et al. | Dec 1997 | A |
5700171 | Horton | Dec 1997 | A |
5715794 | Nakamura et al. | Feb 1998 | A |
5732382 | Puskorius et al. | Mar 1998 | A |
5751147 | Nakata et al. | May 1998 | A |
5765528 | Kamimaru | Jun 1998 | A |
5771482 | Rizzoni | Jun 1998 | A |
5905193 | Hashizume et al. | May 1999 | A |
6023651 | Nakayama et al. | Feb 2000 | A |
6085143 | Przymusinski et al. | Jul 2000 | A |
6109986 | Gaynor et al. | Aug 2000 | A |
6415656 | Bidner et al. | Jul 2002 | B1 |
6485341 | Lanyi et al. | Nov 2002 | B1 |
6668812 | Javaherian | Dec 2003 | B2 |
6672282 | Harrison et al. | Jan 2004 | B2 |
6691653 | Denz | Feb 2004 | B2 |
6752009 | Minich et al. | Jun 2004 | B2 |
6757606 | Gonring | Jun 2004 | B1 |
6758179 | McKay et al. | Jul 2004 | B1 |
6866024 | Rizzoni et al. | Mar 2005 | B2 |
6999868 | Funke et al. | Feb 2006 | B2 |
7024304 | Fukasawa et al. | Apr 2006 | B2 |
7047125 | He et al. | May 2006 | B1 |
7047924 | Waters et al. | May 2006 | B1 |
7063057 | Waters et al. | Jun 2006 | B1 |
7117080 | Sobel | Oct 2006 | B2 |
7133766 | Kokubo | Nov 2006 | B2 |
7146851 | Wakahara et al. | Dec 2006 | B2 |
7167789 | Froloff et al. | Jan 2007 | B1 |
7178503 | Brehob | Feb 2007 | B1 |
7197916 | Matsumoto et al. | Apr 2007 | B2 |
7214110 | Ehlers et al. | May 2007 | B1 |
7243532 | Tsujimura et al. | Jul 2007 | B2 |
7246583 | Cinpinski et al. | Jul 2007 | B2 |
7251557 | Strom et al. | Jul 2007 | B2 |
7325446 | Assaf et al. | Feb 2008 | B1 |
7353803 | Mathews et al. | Apr 2008 | B2 |
7361067 | Smedema | Apr 2008 | B1 |
7437233 | Yasui et al. | Oct 2008 | B2 |
7444236 | Wiles | Oct 2008 | B2 |
7451739 | Yasui et al. | Nov 2008 | B2 |
7469678 | Ruiz | Dec 2008 | B2 |
7500470 | Buslepp et al. | Mar 2009 | B2 |
7526943 | Cubr et al. | May 2009 | B2 |
7530261 | Walters | May 2009 | B2 |
7607415 | Mathews et al. | Oct 2009 | B2 |
7623955 | Rackmil et al. | Nov 2009 | B1 |
7654248 | Buslepp et al. | Feb 2010 | B2 |
7665558 | Akimoto et al. | Feb 2010 | B2 |
7685996 | Brehob | Mar 2010 | B2 |
7698935 | Dibble et al. | Apr 2010 | B2 |
7784443 | Hitomi et al. | Aug 2010 | B2 |
7861689 | Haug et al. | Jan 2011 | B2 |
7877174 | Walser et al. | Jan 2011 | B2 |
7918212 | Verdejo et al. | Apr 2011 | B2 |
8027782 | Assaf et al. | Sep 2011 | B2 |
8176896 | Verdejo et al. | May 2012 | B2 |
8245692 | Glugla et al. | Aug 2012 | B2 |
8251043 | Smith | Aug 2012 | B2 |
8261603 | Kondo et al. | Sep 2012 | B2 |
8307808 | Kaiser et al. | Nov 2012 | B2 |
8387384 | Quigley et al. | Mar 2013 | B2 |
8392096 | Mathews et al. | Mar 2013 | B2 |
8478511 | Hamama et al. | Jul 2013 | B2 |
8532908 | Morgan et al. | Sep 2013 | B2 |
8612124 | Verdejo et al. | Dec 2013 | B2 |
20020157639 | Kidokoro et al. | Oct 2002 | A1 |
20040153286 | Yamada | Aug 2004 | A1 |
20040236496 | Sobel | Nov 2004 | A1 |
20050039721 | Truscott et al. | Feb 2005 | A1 |
20050056240 | Sugiyama et al. | Mar 2005 | A1 |
20050121005 | Edwards | Jun 2005 | A1 |
20050204805 | Wakahara et al. | Sep 2005 | A1 |
20060112933 | Yasui et al. | Jun 2006 | A1 |
20060124107 | Sauler et al. | Jun 2006 | A1 |
20060241848 | Strom et al. | Oct 2006 | A1 |
20060254560 | Mann et al. | Nov 2006 | A1 |
20060293827 | Frauenkron et al. | Dec 2006 | A1 |
20070068474 | Cinpinski et al. | Mar 2007 | A1 |
20070119391 | Fried et al. | May 2007 | A1 |
20070233430 | Singh | Oct 2007 | A1 |
20070239343 | Okubo et al. | Oct 2007 | A1 |
20070295290 | Cao | Dec 2007 | A1 |
20080006244 | Asano et al. | Jan 2008 | A1 |
20080028387 | Nakagawa et al. | Jan 2008 | A1 |
20080077307 | Wiles | Mar 2008 | A1 |
20080178844 | Naegele et al. | Jul 2008 | A1 |
20080183367 | Kapus et al. | Jul 2008 | A1 |
20080283025 | Sato | Nov 2008 | A1 |
20080312810 | Nonoyama | Dec 2008 | A1 |
20090048729 | Waters et al. | Feb 2009 | A1 |
20090090106 | Muller | Apr 2009 | A1 |
20090192693 | Bottcher et al. | Jul 2009 | A1 |
20090215331 | Suzuki et al. | Aug 2009 | A1 |
20090223495 | Ohata et al. | Sep 2009 | A1 |
20090229568 | Nakagawa | Sep 2009 | A1 |
20090276142 | Leone et al. | Nov 2009 | A1 |
20090276143 | Rackmil et al. | Nov 2009 | A1 |
20090276147 | Hamama et al. | Nov 2009 | A1 |
20100012079 | Nakazono et al. | Jan 2010 | A1 |
20100037859 | Mashiki | Feb 2010 | A1 |
20100063712 | Bromberg et al. | Mar 2010 | A1 |
20100083936 | Verdejo et al. | Apr 2010 | A1 |
20100088010 | Verdejo et al. | Apr 2010 | A1 |
20100089361 | Inada et al. | Apr 2010 | A1 |
20100094528 | Auclair et al. | Apr 2010 | A1 |
20100152990 | Bjernetun et al. | Jun 2010 | A1 |
20100152991 | Suzuki | Jun 2010 | A1 |
20100192905 | Lewis et al. | Aug 2010 | A1 |
20100294027 | Kondo et al. | Nov 2010 | A1 |
20110067396 | Quigley et al. | Mar 2011 | A1 |
20110088468 | Mayhew | Apr 2011 | A1 |
20110139120 | Rollinger et al. | Jun 2011 | A1 |
20110224882 | Makino et al. | Sep 2011 | A1 |
20110246049 | Matsuo et al. | Oct 2011 | A1 |
20110253100 | Kaiser et al. | Oct 2011 | A1 |
20110265761 | Amann et al. | Nov 2011 | A1 |
20110283972 | Wermuth et al. | Nov 2011 | A1 |
20120048234 | Hamama et al. | Mar 2012 | A1 |
20120078485 | Verdejo et al. | Mar 2012 | A1 |
20120191275 | Clever et al. | Jul 2012 | A1 |
20120191276 | Clever et al. | Jul 2012 | A1 |
20120191277 | Clever et al. | Jul 2012 | A1 |
20120209494 | Verdejo et al. | Aug 2012 | A1 |
20130047956 | Davis | Feb 2013 | A1 |
20130054109 | Buslepp et al. | Feb 2013 | A1 |
Number | Date | Country |
---|---|---|
1204003 | Jan 1999 | CN |
101074634 | Nov 2007 | CN |
101331305 | Dec 2008 | CN |
102007024415 | Jan 2009 | DE |
102009008247 | Aug 2010 | DE |
2009174397 | Aug 2009 | JP |
2009275663 | Nov 2009 | JP |
2011012607 | Jan 2011 | JP |
Entry |
---|
Tim Gilles; Automotive Service: Inspection, Maintenance, and Repair; Jun. 12, 2003; Delmar Learning; Second Edition; p. 560. |
O'Reilly Auto Parts; Possible Causes of Engine Misfire; http://www.oreillyauto.com/site/app/newsfeed/detail?article=800649141; Nov. 23, 2011. |
U.S. Appl. No. 13/024,726, Julian R. Verdejo et al., filed Feb. 10, 2011. |
U.S. Appl. No. 13/590,351, Brian E. Betz et al., filed Aug. 21, 2012. |
U.S. Appl. No. 13/775,628, filed Feb. 25, 2013, Gwidt et al. |
U.S. Appl. No. 12/357,776, Verdejo et al. |
U.S. Appl. No. 12/478,159, Verdejo et al. |
U.S. Appl. No. 12/762,516, Kaiser et al. |
U.S. Appl. No. 12/762,523, Mathews et al. |
U.S. Appl. No. 12/984,818, Verdejo et al. |
U.S. Appl. No. 13/118,985, Morgan et al. |
Number | Date | Country | |
---|---|---|---|
20140053809 A1 | Feb 2014 | US |