The present disclosure is related to internal combustion engines and more particularly to stochastic pre-ignition (SPI) in internal combustion engines.
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.
Engine control systems monitor a position of a crankshaft of an engine. Rotational speed of the crankshaft (engine speed) and crankshaft acceleration can be determined based on the crankshaft position. For example only, fueling, ignition timing, throttle opening, and/or other engine parameters may be controlled based on the crankshaft position, the engine speed, and/or the acceleration.
A crankshaft position monitoring system typically includes a control module (e.g., an engine control module), a crankshaft position sensor, and a toothed wheel that rotates with the crankshaft. The toothed wheel may have N number of teeth, and the crankshaft position sensor may monitor passing of the teeth. The crankshaft position sensor generates pulses in a crankshaft position signal as the teeth of the toothed wheel pass the crankshaft sensor.
The control module determines the crankshaft position based on the pulses in the crankshaft position signal. The control module may determine the crankshaft position at various crankshaft rotation intervals. As an example, the control module may determine the crankshaft position at intervals of greater than or equal to 90° of crankshaft rotation. The resolution of the crankshaft position signal (e.g., number of samples per crankshaft revolution) may increase as the intervals decrease.
A system for a vehicle includes a time stamping module, a period determination module, a stochastic pre-ignition (SPI) indication module, and an SPI remediation module. The time stamping module generates first and second timestamps when a crankshaft of an engine is in first and second crankshaft positions during an engine cycle, respectively. The period determination module determines a period between the first and second timestamps. The SPI indication module selectively indicates that an SPI event occurred within a cylinder of the engine based on the period. The SPI remediation module selectively adjusts at least one engine operating parameter in response to the SPI indication module indicating that the SPI event occurred within the cylinder.
A method for a vehicle includes: generating first and second timestamps when a crankshaft of an engine is in first and second crankshaft positions during an engine cycle, respectively; determining a period between the first and second timestamps; selectively indicating that a stochastic pre-ignition (SPI) event occurred within a cylinder of the engine based on the period; and selectively adjusting at least one engine operating parameter in response to the indication that the SPI event occurred within the cylinder.
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:
The following description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. 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 steps within a method may be executed in different order 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 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 or a group of execution engines. For example, multiple cores and/or multiple threads of a processor may be considered to be execution engines. In various implementations, execution engines may be grouped across a processor, across multiple processors, and across processors in multiple locations, such as multiple servers in a parallel processing arrangement. 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.
A crankshaft position sensor generates pulses in a crankshaft position signal as teeth of an N-toothed wheel pass the crankshaft position sensor. The N-toothed wheel rotates with a crankshaft of an engine. The N-toothed wheel may have space for, for example, 60 equally spaced teeth (i.e., N=60). The N-toothed wheel may include 58 teeth that are approximately equally spaced and a gap where 2 approximately equally spaced teeth are missing. Accordingly, a given point (e.g., an edge) of each of the teeth (including the missing teeth) may be separated by a rotational distance of approximately 6° (360°/60=6°).
A control module, such as an engine control module (ECM), determines various parameters based on the crankshaft position signal. For example only, the ECM may determine the crankshaft position based on the number of pulses detected in the crankshaft position signal. The ECM may also determine a period between two pulses (corresponding to two teeth) and determine a rotational speed of the crankshaft based on the period between the two pulses and the rotational distance between the two teeth. The ECM may also determine an acceleration and one or more other parameters based on the crankshaft position.
Under some circumstances, a stochastic pre-ignition (SPI) event may occur within a cylinder of the engine. For example only, SPI may occur when the engine speed is less than a predetermined speed (e.g., approximately 3000 revolutions per minute) and an engine load is greater than a predetermined load.
The ECM of the present disclosure generates timestamps when pulses are detected in the crankshaft position signal. The ECM determines periods between consecutive timestamps and determines delta periods (change in period) between consecutive periods. The ECM selectively indicates whether an SPI event occurred within a cylinder of the engine based on the delta periods. More specifically, the ECM selectively indicates whether an SPI event occurred within a cylinder based on a delta period difference caused by a sudden one event change in cylinder pressure at a given piston position.
Referring now to
A cylinder 114 includes a piston (not shown) that is coupled to a crankshaft 118. Although the engine 102 is depicted as including only the cylinder 114, the engine 102 may include more than one cylinder. One combustion cycle of the cylinder 114 may include four strokes: an intake stroke, a compression stroke, an expansion stroke, and an exhaust stroke. One engine cycle includes each of the cylinders undergoing one combustion cycle.
During the intake stroke, the piston approaches a bottom most position, and the air and fuel may be provided to the cylinder 114. The bottom most position may be referred to as a bottom dead center (BDC) position. During the compression stroke, the crankshaft 118 drives the piston toward a top most position and compresses the air/fuel mixture within the cylinder 114. The top most position may be referred to as a top dead center (TDC) position. A spark plug 120 may ignite the air/fuel mixture in various types of engines. A spark actuator module 122 controls the spark plug 120.
Combustion of the air/fuel mixture drives the piston away from the TDC position during the expansion stroke and rotatably drives the crankshaft 118. The rotational force (i.e., torque) may be a source of compressive force for a compression stroke of a combustion cycle of one or more cylinders that follow the cylinder in a predetermined firing order. Exhaust gas resulting from the combustion of the air/fuel mixture is expelled from the cylinder 114 during the exhaust stroke.
A camshaft phaser 124 may control opening of the intake and/or exhaust valve(s) of the cylinder 114. More specifically, the camshaft phaser 124 controls rotation of a camshaft (not shown) to control opening of the intake and/or exhaust valve(s). A phaser actuator module 126 controls the camshaft phaser 124.
One or more boost devices, such as boost device 127, may be implemented in various implementations. The boost device(s) are omitted in naturally aspirated engine systems. The boost device 127 may include, for example, a turbocharger or a supercharger. The boost device 127 may increase pressure within the intake manifold 104. A boost actuator module 128 controls the boost device 127. Boost may be described as an amount that the pressure within the intake manifold 104 is greater than ambient pressure.
A crankshaft position sensor 130 monitors an N-toothed wheel 132 and generates a crankshaft position signal 134 based on rotation of the N-toothed wheel 132. For example only, the crankshaft position sensor 130 may include a variable reluctance (VR) sensor, a hall-effect, or another suitable type of crankshaft position sensor. The N-toothed wheel 132 rotates with the crankshaft 118. The N-toothed wheel 132 includes space for N equally spaced teeth.
The crankshaft position sensor 130 generates a pulse in the crankshaft position signal 134 each time that a tooth of the N-toothed wheel 132 (e.g., rising or falling edge of the tooth) passes the crankshaft position sensor 130. Accordingly, each pulse in the crankshaft position signal 134 may correspond to an angular rotation of the crankshaft 118 by an amount equal to 360° divided by N.
For example only, the N-toothed wheel 132 may include space for 60 equally spaced teeth (i.e., N=60), and each pulse in the crankshaft position signal 134 may therefore correspond to approximately 6° of crankshaft rotation (360°/60=6°/tooth). In various implementations, one or more of the N teeth may be omitted. For example only, two of the N teeth may be omitted in various implementations. The one or more missing teeth may be used to indicate the completion of a revolution of the crankshaft 118.
The engine 102 outputs torque to a transmission 140. The transmission 140 may include a manual type transmission, an automatic type transmission, an auto-manual type transmission, or another suitable type of transmission. The transmission 140 may output torque to one or more wheels (not shown) via a transmission output shaft 142 and a driveline (not shown).
While the rotational distance between consecutive teeth of the N-toothed wheel 132 should be equal (e.g., 6° in the above example), the rotational distances between consecutive teeth may vary. The variation may be due to, for example, manufacturing tolerances, part-to-part variation, wear, sensor variation, and/or one or more other sources.
An engine control module (ECM) 160 may selectively learn the distance between each pair of consecutive teeth of the N-toothed wheel 132. The ECM 160 determines a position of the crankshaft 118 based on the crankshaft position signal and the distances between the teeth. The ECM 160 monitors the period between consecutive teeth and generates an engine speed based on the period between consecutive teeth and the distance between the teeth. The engine speed at a given crankshaft position corresponds to an instantaneous engine speed (rotational speed of the crankshaft 118) at the crankshaft position. The ECM 160 also monitors the change between consecutive periods (delta period) and may generate an acceleration based on the change in the period.
The ECM 160 stores the delta periods for the cylinder 114 when the crankshaft 118 within a predetermined position range for the cylinder 114. The ECM 160 may store the delta periods for the cylinder 114 for each engine cycle. When the delta periods for the cylinder 114 have been stored for a predetermined number of engine cycles, the ECM 160 may determine whether a stochastic pre-ignition (SPI) event occurred within the cylinder 114 based on a change in the delta period at a given position relative to the delta period at the given position from previous and subsequent firing events of the cylinder 114. The ECM 160 may also determine a level of the SPI event based on a change in the crankshaft position where a peak value of the delta period occurs. SPI events may cause engine damage if not detected and/or not remediated. SPI is different than misfire and knock.
Referring now to
A pulse detection module 210 receives the crankshaft position signal 134 generated using the crankshaft position sensor 130. The pulse detection module 210 may generate an indicator 214 when a pulse is detected in the crankshaft position signal 134. The pulse detection module 210 may generate an indicator each time that a pulse is detected in the crankshaft position signal 134. The pulse detection module 210 may also indicate whether a pulse indicates that the tooth passed in a forward direction or a reverse direction.
A position determination module 218 may determine a crankshaft position 222 based on the number of pulses detected in the crankshaft position signal 134. The position determination module 218 may determine the crankshaft position 222 further based on whether the teeth pass in the forward direction or the reverse direction. The position determination module 218 may generate the crankshaft position 222 using, for example, a Kalman filter, a Chebyshev filter, a Butterworth type II filter, or another suitable type of filter. The crankshaft position 222 may correspond to an angular position of the crankshaft 118 at a given time.
A time stamping module 226 generates a time stamp 230 when a pulse is detected in the crankshaft position signal 134. The time stamping module 226 generates a time stamp each time that a pulse is detected in the crankshaft position signal 134. The time stamping module 226 may index the timestamps by the crankshaft positions 222 corresponding to the timestamps, respectively, in a time stamp storage module 234. The time stamping module 226 may index the timestamps in the time stamp storage module 234 by engine cycle. An example table that is illustrative of the data stored in the time stamp storage module 234 is presented below.
CP1 is a first value of the crankshaft position 222 corresponding to a first pulse in the crankshaft position signal 134, CP2 is a second value of the crankshaft position 222 corresponding to a second pulse in the crankshaft position signal 134, CP3 is a third value of the crankshaft position 222 corresponding to a third pulse in the crankshaft position signal 134, and CPM is an M-th value of the crankshaft position 222 corresponding to an M-th pulse in the crankshaft position signal 134. M is an integer greater than one. T1 is a first time stamp corresponding to the first pulse in the crankshaft position signal 134 (and the first crankshaft position), and T2 is a second time stamp corresponding to the second pulse in the crankshaft position signal 134 (and the second crankshaft position). T3 is a third time stamp corresponding to the third pulse in the crankshaft position signal 134 (and the third crankshaft position), and TM is an M-th time stamp corresponding to the M-th pulse in the crankshaft position signal 134 (and the M-th crankshaft position).
A period determination module 238 determine a period 242 for the crankshaft position 222 based on the timestamp 230 for the crankshaft position 222 and a timestamp for a last crankshaft position. For example only, the period determination module 238 may set the period 242 equal to the period between the timestamp 230 for the crankshaft position 222 and the timestamp for the last crankshaft position. An example table that is illustrative of the value of the period 242 at various crankshaft positions is presented below.
P1 is the period 242 corresponding to the first crankshaft position (CP1), P2 is the period 242 corresponding to the second crankshaft position (CP2), P3 is the period 242 corresponding to the third crankshaft position (CP3), and PM is the period 242 corresponding to the M-th crankshaft position (CPM). The period 242 for a given crankshaft position 222 may be used to generate an instantaneous engine speed at the given crankshaft position 222 as discussed further below.
A delta period determination module 246 determines a delta period 250 for the crankshaft position 222 based on the period 242 for the crankshaft position 222 and a period for a last crankshaft position. For example only, the delta period determination module 246 may set the delta period 250 based on a difference between the period 242 for the crankshaft position 222 and the period for the last crankshaft position. An example table that is illustrative of the value of the delta period 250 for various crankshaft positions is presented below.
DP1 is the delta period 250 corresponding to the first crankshaft position (CP1), DP2 is the delta period 250 corresponding to the second crankshaft position (CP2), DP3 is the delta period 250 corresponding to the third crankshaft position (CP3), and DPM is the delta period 250 corresponding to the M-th crankshaft position (CPM). The delta period 250 for a given crankshaft position 222 may be used to generate an instantaneous (crankshaft) acceleration at the given crankshaft position 222.
A storage control module 254 selectively stores the delta period 250 with the corresponding crankshaft position 222 within a delta period storage module 258. The storage control module 254 associates the delta period 250 with the cylinder 114 within the delta period storage module 258. The storage control module 254 also associates the delta period 250 with an engine cycle during which the crankshaft position 222 occurred. In this manner, the delta period storage module 258 includes cylinder and engine cycle specific delta periods.
The storage control module 254 may determine whether to store the delta period 250 within the delta period storage module 258 for the cylinder 114 and the present engine cycle based on the corresponding crankshaft position 222 and a predetermined crankshaft position range for the cylinder 114. The storage control module 254 may store the delta period 250 in the delta period storage module 258 when the crankshaft position 222 is within the predetermined crankshaft position range for the cylinder 114. For example only, the predetermined crankshaft position range may be between approximately 20 degrees (°) before the piston reaches the TDC position (BTDC) within the cylinder 114 and approximately 40° after the piston reaches the TDC position (ATDC). An example table illustrating the data stored in the delta period storage module 258 is provided below.
An SPI indication module 262 selectively generates an SPI indicator 266 based on the delta periods for the last three engine cycles (n, n−1, and n−2). The SPI indicator 266 indicates whether an SPI event occurred within the cylinder 114 during the n−1 engine cycle.
The SPI indication module 262 may determine average delta periods for the crankshaft positions within the predetermined range, respectively. The SPI indication module 262 may determine the average delta periods for the crankshaft positions based on the delta periods for the crankshaft positions, respectively, of the n and n−2 engine cycles. For example only, for a given crankshaft position 316, the SPI indication module 262 may determine the average delta period for the crankshaft position 316 based on the average of the delta period for the n engine cycle 320 and the delta period for the n−2 engine cycle 324. The SPI indication module 262 may determine the average delta period for each of the other crankshaft positions similarly. An example table of average delta periods is presented below.
ADP1 is the average delta period for the first crankshaft position 222, ADP2 is the average delta period for the second crankshaft position 222, ADP3 is the average delta period for the third crankshaft position 222, and ADPM is the average delta period for the M-th crankshaft position 222. DP1(n−2) is the delta period 250 for the first crankshaft position of the n−2 engine cycle, DP1(n) is the delta period 250 for the first crankshaft position of the n engine cycle, DP2(n−2) is the delta period 250 for the second crankshaft position of the n−2 engine cycle, and DP2(n) is the delta period 250 for the second crankshaft position of the n engine cycle. DP3(n−2) is the delta period 250 for the third crankshaft position of the n−2 engine cycle, DP3(n) is the delta period 250 for the third crankshaft position of the n engine cycle, DPM(n−2) is the delta period 250 for the M-th crankshaft position of the n−2 engine cycle, and DPM(n) is the delta period 250 for the M-th crankshaft position of the n engine cycle.
The SPI indication module 262 may determine delta period differences for the crankshaft positions within the predetermined range, respectively. The SPI indication module 262 may determine the delta period differences for the crankshaft positions based on the delta periods and the average delta periods for the crankshaft positions, respectively. For example only, for a given crankshaft position, the SPI indication module 262 may determine the delta period difference based on the difference between the average delta period for the crankshaft position and the delta period 250 for the crankshaft position of the n−1 engine cycle. The SPI indication module 262 may determine the delta period difference for each other crankshaft position similarly. An example table of delta period differences is presented below.
DPD1 is the delta period difference for the first crankshaft position, DPD2 is the delta period difference for the second crankshaft position, DPD3 is the delta period difference for the third crankshaft position, and DPDM is the delta period difference for the M-th crankshaft position. DP1 is the delta period for the first crankshaft position of the n−1 engine cycle, DP2 is the delta period for the second crankshaft position of the n−1 engine cycle, DP3 is the delta period for the third crankshaft position of the n−1 engine cycle, and DPM is the delta period for the M-th crankshaft position of the n−1 engine cycle.
The SPI indication module 262 may determine whether an SPI event occurred within the cylinder 114 during the n−1 engine cycle based on one or more of the delta period differences. For example only, the SPI indication module 262 may determine that an SPI event occurred within the cylinder 114 during the n−1 engine cycle when one or more of the delta period differences is greater than a predetermined value. Written conversely, the SPI indication module 262 may determine that an SPI event did not occur within the cylinder 114 during the n−1 engine cycle when the delta period differences are all less than the predetermined value. The predetermined value may be calibratable and may be set, for example, to correspond to a change in pressure within the cylinder 114 of approximately 3.0 megapascal (MPa) or another suitable value. The SPI indication module 262 may set the SPI indicator 266 to an active state when an SPI event occurred. The SPI indication module 262 may set the SPI indicator 266 to an inactive state when an SPI event did not occur.
When an SPI event occurred, the SPI indication module 262 may also determine and indicate a level for the SPI event. The SPI indication module 262 may determine a peak pressure for the n−1 engine cycle. The peak pressure may correspond to the delta period 250 for the n−1 engine cycle where a greatest pressure occurred within the cylinder 114. The SPI indication module 262 may determine the level of the SPI event based on the crankshaft position 222 corresponding to the delta period 250 with the largest magnitude.
Referring now to
Example trace 428 tracks the cylinder pressure 404 as a function of the crankshaft position 408 during an engine cycle during which an SPI event occurred and knock did not occur. Example trace 432 tracks the cylinder pressure 404 as a function of the crankshaft position 408 during an engine cycle during which an SPI event occurred and knock occurred. As illustrated in
Referring again to
A braking mean effective pressure (BMEP) may be used as the engine load parameter in various implementations. Other suitable engine load parameters may be used in other implementations. A BMEP determination module 274 determines a BMEP 276 based on the engine speed 272. For example only, an indicated work for a combustion cycle of the cylinder 114 may be generated based on squares of two or more engine speeds at predetermined crankshaft positions of the combustion cycle, respectively. An indicated mean effective pressure (IMEP) of the combustion cycle of the cylinder 114 may be generated based on the indicated work and the displacement volume of the engine 102. A BMEP can be determined based on the IMEP.
An enabling module 280 selectively enables and disables the SPI indication module 262 based on the engine speed 272 and the BMEP 276 over the n−2, n−1, and n engine cycles. For example only, the enabling module 280 may disable the SPI indication module 262 when the engine speed 272 is greater than the predetermined speed at least once during the n−2, n−1, and n engine cycles and/or the BMEP 276 is less than the predetermined load value at least once during the n−2, n−1, and n engine cycles. In this manner, the enabling module 280 prevents the SPI indication module 262 from indicating that an SPI event occurred when the engine speed 272 was greater than the predetermined speed and/or the BMEP 276 was greater than the predetermined load value.
Conversely, the enabling module 280 may enable the SPI indication module 262 when the engine speed 272 remains less than the predetermined speed during the n−2, n−1, and n engine cycles and the BMEP 276 remains greater than the predetermined load value during the n−2, n−1, and n engine cycles. For example only, the predetermined speed may be approximately 3000 revolutions per minute (rpm) or another suitable speed, and the predetermined load value may be approximately 13 bar BMEP or another suitable value.
An SPI remediation module 284 selectively adjusts at least one engine operating parameter in response to the SPI indication module 262 indicating that an SPI event occurred. For example only, when an SPI event has occurred, the SPI remediation module 284 may command the fuel control module 202 to increase the amount of fuel provided to provide a richer air/fuel mixture. The SPI remediation module 284 may command the fuel control module 202 to increase the amount of fuel provided to the cylinder 114. Additionally or alternatively, the SPI remediation module 284 may command the boost control module 206 to reduce the amount of boost provided by the boost device 127. Additionally or alternatively, the SPI remediation module 284 may command the spark control module 204 to disable knock control and to set the spark timings using a predetermined set of optimal spark timings. The SPI remediation module 284 may additionally or alternatively take one or more other suitable remedial actions.
Referring now to
Control determines whether the n engine cycle is complete at 508. If so, control proceeds with 512. If false returns to 504. At 512, control determines whether the engine speed 272 was greater than the predetermined speed and/or the BMEP 276 was less than the predetermined load value at least once during the n, n−1, or n−2 engine cycles. If true, control may disable SPI event detection and indication at 516, and control may end. If false, control may continue with 520.
Control determines the average delta periods at 520. Control determines the average delta period for a crankshaft position based on the average of the delta period for the crankshaft position of the n engine cycle and the delta period for the crankshaft position of the n−2 engine cycle. Control determines the delta period differences at 524. Control determines the delta period difference for a crankshaft position based on a difference between the average delta period for the crankshaft position and the delta period for the crankshaft position of the n−1 engine cycle.
Control determines whether one or more of the delta period differences are greater than the predetermined value at 528. If false, control may indicate that an SPI event did not occur during the n−1 engine cycle at 532, and control may end. If true, control may continue with 536. The predetermined value may be calibratable and may be set, for example, to correspond to a change in pressure within the cylinder 114 of approximately 3.0 megapascal (MPa) or another suitable value.
At 536, control may indicate that an SPI event occurred during the n−1 engine cycle and take remedial action. Remedial actions may include, for example, providing a fuel-rich air/fuel mixture to the cylinder 114, decreasing boost, commanding use of the predetermined set of optimum spark timings, and/or one or more other suitable remedial actions.
At 540, control may determine the crankshaft position where the peak pressure occurred during the n, n−1, and n−2 engine cycles. Control may determine a level of the SPI event based on the crankshaft position where the peak pressure occurred during the n−1 engine cycle at 544. Control may determine the level of the SPI event further based on one or more other crankshaft positions where peak pressures occurred or should occur. Control may then end. While control is shown as ending,
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 to the skilled practitioner upon a study of the drawings, the specification, and the following claims.
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 |
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 |
---|
U.S. Appl. No. 13/775,628, filed Feb. 25, 2013, Gwidt et al. |
U.S. Appl. No. 12/478,159, filed Jun. 4, 2009, Verdejo et al. |
U.S. Appl. No. 12/762,516, filed Apr. 19, 2010, Kaiser et al. |
U.S. Appl. No. 13/590,351, filed Aug. 21, 2012, Betz. |
U.S. Appl. No. 13/590,369, filed Aug. 21, 2012, Betz. |
Chinese Search Report dated Sep. 27, 2012 for Chinese Application No. CN201110097845.3, (2 pages). |
U.S. Appl. No. 12/357,776, filed Jan. 22, 2009, J. Verdejo et al. |
U.S. Appl. No. 12/762,523, filed Apr. 19, 2010, D. Mathews et al. |
U.S. Appl. No. 12/984,818, filed Jan. 5, 2011, J. Verdejo et al. |
U.S. Appl. No. 13/024,726, filed Feb. 10, 2011, J. Verdejo et al. |
U.S. Appl. No. 13/118,985, filed May 31, 2011, J. Morgan et al. |
O'Reilly Auto Parts; Possible Cause of Engine Misfire: http://oreillyauto.com/site/app/newsfeed/detail?article=800649141; Nov. 23, 2011. |
Number | Date | Country | |
---|---|---|---|
20130054109 A1 | Feb 2013 | US |