US20200332737A1 - Low speed pre-ignition knock detection, mitigation, and driver notification - Google Patents
Low speed pre-ignition knock detection, mitigation, and driver notification Download PDFInfo
- Publication number
- US20200332737A1 US20200332737A1 US16/387,677 US201916387677A US2020332737A1 US 20200332737 A1 US20200332737 A1 US 20200332737A1 US 201916387677 A US201916387677 A US 201916387677A US 2020332737 A1 US2020332737 A1 US 2020332737A1
- Authority
- US
- United States
- Prior art keywords
- engine
- knock
- vehicle
- lspi
- fuel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 13
- 230000000116 mitigating effect Effects 0.000 title claims abstract description 12
- 239000000446 fuel Substances 0.000 claims abstract description 65
- 238000000034 method Methods 0.000 claims abstract description 47
- 230000004044 response Effects 0.000 claims abstract description 8
- 230000000246 remedial effect Effects 0.000 claims abstract description 5
- 238000002485 combustion reaction Methods 0.000 claims description 16
- 230000002159 abnormal effect Effects 0.000 claims description 9
- 238000002347 injection Methods 0.000 claims description 5
- 239000007924 injection Substances 0.000 claims description 5
- 230000006835 compression Effects 0.000 description 8
- 238000007906 compression Methods 0.000 description 8
- 238000012544 monitoring process Methods 0.000 description 6
- 239000000203 mixture Substances 0.000 description 5
- 230000009467 reduction Effects 0.000 description 5
- 230000001276 controlling effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 239000002828 fuel tank Substances 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000011217 control strategy Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 239000003502 gasoline Substances 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000003321 amplification Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003638 chemical reducing agent Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000001627 detrimental effect Effects 0.000 description 1
- 238000006073 displacement reaction Methods 0.000 description 1
- 230000037406 food intake Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000006698 induction Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- TVMXDCGIABBOFY-UHFFFAOYSA-N octane Chemical compound CCCCCCCC TVMXDCGIABBOFY-UHFFFAOYSA-N 0.000 description 1
- 230000010355 oscillation Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/22—Safety or indicating devices for abnormal conditions
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D35/00—Controlling engines, dependent on conditions exterior or interior to engines, not otherwise provided for
- F02D35/02—Controlling engines, dependent on conditions exterior or interior to engines, not otherwise provided for on interior conditions
- F02D35/027—Controlling engines, dependent on conditions exterior or interior to engines, not otherwise provided for on interior conditions using knock sensors
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/0002—Controlling intake air
- F02D41/0007—Controlling intake air for control of turbo-charged or super-charged engines
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/02—Circuit arrangements for generating control signals
- F02D41/14—Introducing closed-loop corrections
- F02D41/1497—With detection of the mechanical response of the engine
- F02D41/1498—With detection of the mechanical response of the engine measuring engine roughness
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/22—Safety or indicating devices for abnormal conditions
- F02D2041/228—Warning displays
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D2200/00—Input parameters for engine control
- F02D2200/02—Input parameters for engine control the parameters being related to the engine
- F02D2200/025—Engine noise, e.g. determined by using an acoustic sensor
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D2200/00—Input parameters for engine control
- F02D2200/02—Input parameters for engine control the parameters being related to the engine
- F02D2200/06—Fuel or fuel supply system parameters
- F02D2200/0625—Fuel consumption, e.g. measured in fuel liters per 100 kms or miles per gallon
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D2250/00—Engine control related to specific problems or objectives
- F02D2250/18—Control of the engine output torque
- F02D2250/26—Control of the engine output torque by applying a torque limit
Definitions
- the present application generally relates to engine knock detection and, more particularly, to techniques for low speed pre-ignition (LSPI) knock detection, mitigation, and driver notification.
- LSPI low speed pre-ignition
- LSPI knock is a stochastic, abnormal start of combustion prior to spark discharge. Possible causes of LSPI knock include cylinder hot spots or oil ingestion, or chemical pre-reactions, each creating pressure waves that collide causing the LSPI knock.
- LSPI knock is often one or more orders of magnitude greater in intensity than spark knock.
- a typical knock control strategy is spark retardation. This control strategy, however, is not effective against LSPI knock and is actually detrimental in mitigating LSPI knock. This is because during LSPI knock, combustion has already been initiated prior to the spark discharge, and thus retardation of the spark timing provides the cylinder charge even more time for auto-ignition to occur. Accordingly, while such knock detection and control systems work for their intended purpose, there remains a need for improvement in the relevant art.
- a control system for an engine of a vehicle comprises: a knock sensor configured to generate a knock signal indicative of a vibration of the engine caused by abnormal combustion and a controller configured to: receive the knock signal, analyze the knock signal to detect low speed pre-ignition (LSPI) knock of the engine, in response to detecting the LSPI knock, enrich a fuel/air ratio of the engine and limit a torque output of the engine to a level that is less than a maximum torque output of the engine, and when enriching the fuel/air ratio of the engine and limiting the torque output of the engine does not mitigate the LSPI knock, output at least one message for a driver of the vehicle instructing the driver to take remedial action to mitigate the LSPI knock.
- LSPI low speed pre-ignition
- the message (i) instructs the driver of the vehicle to supply at least one of a specific quality of oil and a specific quality of fuel to the vehicle or (ii) instructs the driver of the vehicle to take the vehicle to a service center for service.
- the controller in response to detecting the LSPI knock, is configured to enrich the fuel/air ratio of the engine and limit the torque output of the engine to a first torque limit for a calibratable number of engine power pulse (EPP) events. In some implementations, when enriching the fuel/air ratio of the engine and limiting the torque output of the engine to the first torque limit for the first period does not mitigate the LSPI knock, the controller is configured to limit the torque output of the engine to a second torque limit for a remainder of a key cycle of the engine.
- EPP engine power pulse
- the controller when limiting the torque output of the engine to the second torque limit for the second period does not mitigate the LSPI knock, the controller is configured to limit the torque output of the engine to a third torque limit until a calibratable amount of fuel has been used by the engine.
- the controller is configured to output a first message while limiting the torque output of the engine to the third torque limit until the calibratable amount of fuel has been used by the engine, wherein the first message instructs the driver of the vehicle to provide at least one of a specific quality of oil and a specific quality of fuel to the vehicle.
- the controller is configured to output a second message instructing the driver of the vehicle take the vehicle to a service center for service.
- the controller is configured to output the at least one message to a display of the vehicle for display to the driver of the vehicle.
- the engine is a turbocharged, direct injection (DI) engine.
- an LSPI knock detection, mitigation, and driver notification method for a vehicle comprises: receiving, by a controller of the vehicle from a knock sensor of the vehicle, a knock signal indicative of a vibration of an engine of the vehicle caused by abnormal combustion, analyzing, by the controller, the knock signal to detect LSPI knock of the engine, in response to detecting the LSPI knock, enriching, by the controller, a fuel/air ratio of the engine and limiting, by the controller, a torque output of the engine to a level that is less than a maximum torque output of the engine, and when enriching the fuel/air ratio of the engine and limiting the torque output of the engine does not mitigate the LSPI knock, outputting, by the controller, at least one message for a driver of the vehicle instructing the driver to take remedial action to mitigate the LSPI knock.
- the message (i) instructs the driver of the vehicle to supply at least one of a specific quality of oil and a specific quality of fuel to the vehicle or (ii) instructs the driver of the vehicle to take the vehicle to a service center for service.
- the controller in response to detecting the LSPI knock, enriches the fuel/air ratio of the engine and limits the torque output of the engine to a first torque limit for a calibratable number of EPP events. In some implementations, when enriching the fuel/air ratio of the engine and limiting the torque output of the engine to the first torque limit for the first period does not mitigate the LSPI knock, the controller limits the torque output of the engine to a second torque limit for a remainder of a key cycle of the engine. In some implementations, when limiting the torque output of the engine to the second torque limit for the second period does not mitigate the LSPI knock, the controller limits the torque output of the engine to a third torque limit until a calibratable amount of fuel has been used by the engine.
- the controller outputs a first message while limiting the torque output of the engine to the third torque limit until the calibratable amount of fuel has been used by the engine, wherein the first message instructs the driver of the vehicle to provide at least one of a specific quality of oil and a specific quality of fuel to the vehicle.
- the controller when the torque output of the engine is limited to the third torque limit until the calibratable amount of fuel has been used by the engine occurs a calibratable number of times, the controller outputs a second message instructing the driver of the vehicle take the vehicle to a service center for service.
- the controller outputs the at least one message to a display of the vehicle for display to the driver of the vehicle.
- the engine is a turbocharged DI engine.
- FIG. 1 is a diagram of an example engine according to the principles of the present disclosure
- FIG. 2 is a plot of an example low speed pre-ignition (LSPI) knock detection and mitigation process according to the principles of the present disclosure.
- LSPI low speed pre-ignition
- FIGS. 3A-3B are flow diagrams of an example LSPI knock detection, mitigation, and driver notification method according to the principles of the present disclosure.
- low speed pre-ignition (LSPI) knock cannot be mitigated via conventional spark retardation. Because its intensity is orders of magnitude higher than end-gas spark knock, LSPI knock could potentially damage the engine, thereby increasing vehicle warranty costs. In particular, LSPI knock often occurs in smaller displacement engines having high compression ratios, such as a turbocharged four-cylinder engine, particularly during high load operation. In addition, if the incorrect oil and/or fuel is provided to the engine, the probability of LSPI knock increases. Oil grade, for example, may vary from region to region.
- the engine 104 is configured to combust a fuel/air mixture to generate drive torque.
- the engine 104 include a spark ignition direct injection (SIDI) engine, but it will be appreciated that the techniques of the present disclosure could be applicable to any suitable engine comprising a knock sensor, such as a port fuel injection (PH) engine.
- the engine 104 could be a gasoline compression ignition engine (homogeneous charge compression ignition (HCCI), partially pre-mixed charge compression ignition (PPCI), pre-mixed charge compression ignition, etc.).
- HCCI homogeneous charge compression ignition
- PPCI partially pre-mixed charge compression ignition
- pre-mixed charge compression ignition etc.
- the engine 104 draws air into an intake manifold 108 through an induction system 112 that is regulated by a throttle valve 116 .
- the air in the intake manifold 108 is distributed to a plurality of cylinders 120 and therein combined with fuel injected by respective DI fuel injectors 124 . While four cylinders are shown, it will be appreciated that the engine 100 could have any suitable number of cylinders.
- the engine 104 includes a boost system 122 (a turbocharger, a supercharger, etc.) having an associated wastegate or surge valve 126 for regulating boost pressure.
- the fuel/air mixture in the cylinders 120 is compressed by pistons (not shown) and combusted by spark generated by respective spark plugs 128 .
- a compression ratio of the cylinders 120 may be relatively high.
- the combustion of the fuel/air mixture within the cylinders 120 drives the pistons (not shown), which rotatably turn a crankshaft 132 to generate drive torque.
- the drive torque is then transferred, e.g., via a transmission (not shown), to a driveline 136 .
- a knock sensor 140 is configured to generate a knock signal indicative of vibration of the engine 104 caused by abnormal combustion.
- the knock sensor 140 is an accelerometer-based sensor that is mounted to a block of the engine 104 .
- the abnormal combustion if unaccounted for, causes noticeable vibrations (noise, vibration, and/or harshness, or NVH) and/or could potentially damage the engine 104 .
- NVH noise, vibration, and/or harshness, or NVH
- the engine 104 could include a plurality of distinct knock sensors (one knock sensor per cylinder bank or group of cylinders, one knock sensor per cylinder, etc.).
- Exhaust gas resulting from combustion is expelled from the cylinders 120 into an exhaust system 144 configured to treat the exhaust gas before releasing it into the atmosphere.
- a controller 148 controls operation of the engine system 100 , such as controlling the throttle valve 116 (airflow), the DI fuel injectors 124 (fuel), and the spark plugs 128 (spark) and communicates with a display 152 (e.g., a driver interface).
- the controller 148 also receives the knock signal from the knock sensor 140 .
- the controller 148 is configured to detect knock of the engine 104 by analyzing the knock signal.
- the controller 148 is configured to detect both (i) LSPI knock and (ii) spark knock using the knock signal, which will be described in greater detail below. While not shown, it will be appreciated that the controller 148 is configured to receive other inputs, such as a crank angle measurement (e.g., in crank angle degrees, or CAD) from a crankshaft position sensor (not shown).
- a crank angle measurement e.g., in crank angle degrees, or CAD
- LSPI knock events are numerous. Extended and reoccurring LSPI can lead to thermal runways and surface (cylinder wall) ignition. Possible causes of LSPI events include: (1) hot combustion chamber deposits that flake off and ignite the cylinder charge because the flaking deposit is exposed to long resonance times and elevated pressure, which causes it to ignite, (2) oil droplets from the piston crevice enter into the combustion chamber of the cylinder 120 and act as a localized octane reducer causing auto-ignition prior to the spark discharge, and (3) auto-ignition prior to the spark discharge due to the boundary conditions, such as in gasoline compression ignition engines. Some engines overcome these surface ignition problems with improved hardware, engine design, and calibration. LSPI events, however, are still problematic in boosted engines with very retarded combustion phasing and high compression ratios (long resonance times at elevated pressure), particularly when operating at low speed and high load.
- the analyzing or processing of the knock signal is as follows. For a particular monitoring window, the knock signal is processed according to associated parameters (signal amplifications, detection thresholds, etc.). In one exemplary implementation, the knock signal is filtered, rectified, and its energy is integrated across the monitoring window to obtain a single value. The window could be calibrated throughout the engine speed range. Based on a fast Fourier transform (FFT), the “knocking frequency” is isolated, which allows monitoring of first and second order pressure oscillations occurring in a particular frequency range (e.g., 5-10 kilohertz (kHz)). As previously discussed herein, only one monitoring window is typically active at a time.
- FFT fast Fourier transform
- a single controller 148 is capable of detecting both LSPI knock and spark knock using a single knock sensor 140 .
- FIG. 2 a plot of an example LSPI knock detection and mitigation process is illustrated.
- the engine 104 is not limited below its maximum output torque and is generating a nominal torque T N .
- an LSPI knock event is detected. This represents the start of a first phase (Phase 1).
- the term “LSPI knock event” could comprise a plurality of detected occurrences of LSPI knock (e.g., a series of consecutive LSPI knocks).
- the controller 148 limits the torque output of the engine 104 to a first torque limit T 1 that is less than the nominal torque T N .
- This reduction in torque output of the engine 104 could be achieved, for example, by controlling the throttle valve 116 and/or by controlling the wastegate or surge valve 126 associated with the boost system 122 .
- This torque reduction is also referred to herein as a “torque derate.”
- the controller 148 also enriches the fuel/air ratio of the engine 104 (e.g., increases the amount of fuel injected by the DI fuel injectors 128 ). As shown, this torque drop to the first torque limit T 1 occurs very fast as the process is attempting to quickly mitigate the LSPI knock.
- the torque output of the engine 104 is held at the first torque limit for a calibratable period, such as a calibratable number of engine power pulse (EPP) events (e.g., 30 EPP events).
- EPP engine power pulse
- the controller 148 removes the limiting and increases engine torque output back to the nominal torque T N . This represents the end of Phase 1. As shown, however, another LSPI knock event is subsequently detected at time t 2 . Thus, the fuel enrichment and temporary torque limiting did not mitigate (or fully mitigate) the LSPI knock. This represents the start of a second phase (Phase 2).
- the controller 148 again limits the torque output of the engine 104 for the calibratable period (e.g., repeat a portion of Phase 1). After this calibratable period, however, the controller 148 limits the torque output of the engine to a second torque limit T 2 . As shown, this second torque limit T 2 is greater than the first torque limit T 1 but still less than the nominal torque T N .
- the second torque limit T 2 could be the same as the first torque limit T 1 .
- This second torque limit T 2 is maintained by the controller 148 for the remainder of a current key cycle of the engine 104 (e.g., until the engine is turned off), after which Phase 2 ends.
- a first message could be output for the driver.
- Various exit conditions also exist to effectively reset this Phase 2 counter. These are discussed in greater detail below with reference to FIGS. 3A-3B .
- Phase 3 yet another LSPI knock event is detected at time t 3 before the end of the current key cycle of the engine 104 .
- the controller 148 limits the torque output of the engine 104 to a third torque limit T 3 until a calibratable amount of fuel has been consumed by the engine 104 .
- This calibratable amount of fuel could be one entire fuel tank of the vehicle 100 , but it will be appreciated that other suitable amounts could be used. It will also be appreciated that fuel consumption monitoring could continue across one or more partial fuel refill events (e.g., Phase 3 would not end upon any single fuel refill event).
- phase 3 ends.
- a second message could be output to the driver.
- exit conditions also exist to effectively reset this Phase 3 counter.
- FIGS. 3A-3B flow diagrams of example LSPI knock detection, mitigation, and driver notification methods 300 , 380 are illustrated.
- an example method 300 of knock detection, mitigation, and driver notification is illustrated.
- the controller 148 detects whether an LSPI event has occurred. When true, the method 300 proceeds to 304 . Otherwise, the method 300 ends or returns to 304 .
- the controller 148 increments an LSPI event counter.
- the controller 148 determines whether the LSPI event detected at 304 is the first LSPI event of a potential chain of events (e.g., whether the LSPI event counter is equal to one).
- the method 300 proceeds to 316 where fuel enrichment (enrichment of the FA ratio of the engine 104 ) is performed by the controller 148 . Otherwise, the method 300 proceeds directly to 320 .
- the controller 148 determines whether there are enough LSPI events to form a chain (e.g., whether the LSPI event counter exceeds a calibratable event threshold).
- the controller 148 increments an LSPI chain counter.
- the controller 148 performs short-term torque reduction. This could include, for example, limiting torque to the first torque limit T 1 for a calibratable number of EPP events (see FIG. 2 ).
- the controller 148 determines whether there are enough chains to derate torque for the remainder of the current trip or key-cycle (e.g., whether the LSPI chain counter exceeds a calibratable chain threshold). When true, the method 300 proceeds to 336 . Otherwise, the method 300 ends or returns to 304 . At 336 , the controller 148 increments a trip derate counter.
- the controller 148 performs key cycle torque reduction. This could include, for example, limiting torque to the second torque limit T 2 for the remainder of the current key-cycle (see FIG. 2 ).
- the controller 148 determines whether there are enough chains or derated trips to derate torque for the remainder of the fuel tank or some other calibratable amount of fuel (e.g., whether the respective counters exceed respective calibratable tank thresholds). When true, the method 300 proceeds to 348 . Otherwise, the method 300 ends or returns to 304 .
- the controller 148 increments a tank fail counter.
- the controller 148 performs tank torque reduction. This could include, for example, limiting torque to the third torque limit T 3 until the calibratable amount of fuel has been consumed by the engine 104 (see FIG. 2 ).
- the controller 148 determines whether there are enough derated tanks or trip events to output the second message instructing the driver to take the vehicle to a service station for service (e.g., whether the respective counters exceed calibratable service thresholds). When true, the method 300 proceeds to 360 where the controller 148 outputs the second message (e.g., to display 152 ) and the method 300 then ends or returns to 304 . Otherwise, the method 300 proceeds to 364 where the controller outputs the first message (e.g., to display 152 ) instructing the driver to provide a specific type or quality of oil and or fuel to the vehicle 100 and the method 300 then ends or returns to 304 .
- the controller 148 determines whether a refuel event has occurred. This could be determined, for example, using a fuel level sensor in a fuel tank of the vehicle 100 . When true, the method 380 proceeds to 384 . Otherwise, the method 380 ends or returns to 382 . At 384 , the controller 148 determines whether a tank derate is currently active. When true, the method 380 proceeds to 386 where the controller 148 clears or discontinues the tank derate and the method 380 then ends or returns to 382 . Otherwise, the method 380 proceeds to 388 .
- the controller 148 determines whether the tank fail counter is greater than zero. When true, the method 380 proceeds to 390 . Otherwise, the method 380 ends or returns to 382 . At 390 , the controller 148 increments a clear tank counter. At 392 , the controller 148 determines whether enough clear tanks (tank refill events) have occurred to decrement the tank fail counter (e.g., whether the number of clear tanks exceeds a calibratable threshold). When true, the method 380 proceeds to 394 . Otherwise, the method 380 ends or returns to 382 . At 394 , the controller 148 decrements the tank fail counter. At 396 , the controller 148 sets the clear tank counter to zero and the method 380 then ends or returns to 382 . In other words, a certain number of clear tanks (fuel refill events) without entering the tank derate can result in the tank fail counter being decremented.
- controller refers to any suitable control device or set of multiple control devices that is/are configured to perform at least a portion of the techniques of the present disclosure.
- Non-limiting examples include an application-specific integrated circuit (ASIC), one or more processors and a non-transitory memory having instructions stored thereon that, when executed by the one or more processors, cause the controller to perform a set of operations corresponding to at least a portion of the techniques of the present disclosure.
- ASIC application-specific integrated circuit
- the one or more processors could be either a single processor or two or more processors operating in a parallel or distributed architecture.
Landscapes
- Engineering & Computer Science (AREA)
- Chemical & Material Sciences (AREA)
- Combustion & Propulsion (AREA)
- Mechanical Engineering (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Combined Controls Of Internal Combustion Engines (AREA)
Abstract
Description
- The present application generally relates to engine knock detection and, more particularly, to techniques for low speed pre-ignition (LSPI) knock detection, mitigation, and driver notification.
- Internal combustion engines combust a fuel/air mixture within cylinders to drive pistons that rotatably turn a crankshaft to generate drive torque. Abnormal combustion of the fuel/air mixture can cause vibration of the engine (e.g., seismic waves through the engine structure), which is also known as “knock.” There are two primary types of engine knock: (1) end-gas auto-ignition (also known as “spark knock”) and (2) low speed pre-ignition (LSPI) knock (also known as “mega knock”). LSPI knock is a stochastic, abnormal start of combustion prior to spark discharge. Possible causes of LSPI knock include cylinder hot spots or oil ingestion, or chemical pre-reactions, each creating pressure waves that collide causing the LSPI knock.
- LSPI knock is often one or more orders of magnitude greater in intensity than spark knock. A typical knock control strategy is spark retardation. This control strategy, however, is not effective against LSPI knock and is actually detrimental in mitigating LSPI knock. This is because during LSPI knock, combustion has already been initiated prior to the spark discharge, and thus retardation of the spark timing provides the cylinder charge even more time for auto-ignition to occur. Accordingly, while such knock detection and control systems work for their intended purpose, there remains a need for improvement in the relevant art.
- According to one example aspect of the invention, a control system for an engine of a vehicle is presented. In one exemplary implementation, the control system comprises: a knock sensor configured to generate a knock signal indicative of a vibration of the engine caused by abnormal combustion and a controller configured to: receive the knock signal, analyze the knock signal to detect low speed pre-ignition (LSPI) knock of the engine, in response to detecting the LSPI knock, enrich a fuel/air ratio of the engine and limit a torque output of the engine to a level that is less than a maximum torque output of the engine, and when enriching the fuel/air ratio of the engine and limiting the torque output of the engine does not mitigate the LSPI knock, output at least one message for a driver of the vehicle instructing the driver to take remedial action to mitigate the LSPI knock.
- In some implementations, the message (i) instructs the driver of the vehicle to supply at least one of a specific quality of oil and a specific quality of fuel to the vehicle or (ii) instructs the driver of the vehicle to take the vehicle to a service center for service.
- In some implementations, in response to detecting the LSPI knock, the controller is configured to enrich the fuel/air ratio of the engine and limit the torque output of the engine to a first torque limit for a calibratable number of engine power pulse (EPP) events. In some implementations, when enriching the fuel/air ratio of the engine and limiting the torque output of the engine to the first torque limit for the first period does not mitigate the LSPI knock, the controller is configured to limit the torque output of the engine to a second torque limit for a remainder of a key cycle of the engine. In some implementations, when limiting the torque output of the engine to the second torque limit for the second period does not mitigate the LSPI knock, the controller is configured to limit the torque output of the engine to a third torque limit until a calibratable amount of fuel has been used by the engine.
- In some implementations, the controller is configured to output a first message while limiting the torque output of the engine to the third torque limit until the calibratable amount of fuel has been used by the engine, wherein the first message instructs the driver of the vehicle to provide at least one of a specific quality of oil and a specific quality of fuel to the vehicle. In some implementations, when the torque output of the engine is limited to the third torque limit until the calibratable amount of fuel has been used by the engine occurs a calibratable number of times, the controller is configured to output a second message instructing the driver of the vehicle take the vehicle to a service center for service.
- In some implementations, the controller is configured to output the at least one message to a display of the vehicle for display to the driver of the vehicle. In some implementations, the engine is a turbocharged, direct injection (DI) engine.
- According to another example aspect of the invention, an LSPI knock detection, mitigation, and driver notification method for a vehicle is presented. In one exemplary implementation, the method comprises: receiving, by a controller of the vehicle from a knock sensor of the vehicle, a knock signal indicative of a vibration of an engine of the vehicle caused by abnormal combustion, analyzing, by the controller, the knock signal to detect LSPI knock of the engine, in response to detecting the LSPI knock, enriching, by the controller, a fuel/air ratio of the engine and limiting, by the controller, a torque output of the engine to a level that is less than a maximum torque output of the engine, and when enriching the fuel/air ratio of the engine and limiting the torque output of the engine does not mitigate the LSPI knock, outputting, by the controller, at least one message for a driver of the vehicle instructing the driver to take remedial action to mitigate the LSPI knock.
- In some implementations, the message (i) instructs the driver of the vehicle to supply at least one of a specific quality of oil and a specific quality of fuel to the vehicle or (ii) instructs the driver of the vehicle to take the vehicle to a service center for service.
- In some implementations, in response to detecting the LSPI knock, the controller enriches the fuel/air ratio of the engine and limits the torque output of the engine to a first torque limit for a calibratable number of EPP events. In some implementations, when enriching the fuel/air ratio of the engine and limiting the torque output of the engine to the first torque limit for the first period does not mitigate the LSPI knock, the controller limits the torque output of the engine to a second torque limit for a remainder of a key cycle of the engine. In some implementations, when limiting the torque output of the engine to the second torque limit for the second period does not mitigate the LSPI knock, the controller limits the torque output of the engine to a third torque limit until a calibratable amount of fuel has been used by the engine.
- In some implementations, the controller outputs a first message while limiting the torque output of the engine to the third torque limit until the calibratable amount of fuel has been used by the engine, wherein the first message instructs the driver of the vehicle to provide at least one of a specific quality of oil and a specific quality of fuel to the vehicle. In some implementations, when the torque output of the engine is limited to the third torque limit until the calibratable amount of fuel has been used by the engine occurs a calibratable number of times, the controller outputs a second message instructing the driver of the vehicle take the vehicle to a service center for service.
- In some implementations, the controller outputs the at least one message to a display of the vehicle for display to the driver of the vehicle. In some implementations, the engine is a turbocharged DI engine.
- Further areas of applicability of the teachings of the present disclosure will become apparent from the detailed description, claims and the drawings provided hereinafter, wherein like reference numerals refer to like features throughout the several views of the drawings. It should be understood that the detailed description, including disclosed embodiments and drawings referenced therein, are merely exemplary in nature intended for purposes of illustration only and are not intended to limit the scope of the present disclosure, its application or uses. Thus, variations that do not depart from the gist of the present disclosure are intended to be within the scope of the present disclosure.
-
FIG. 1 is a diagram of an example engine according to the principles of the present disclosure; -
FIG. 2 is a plot of an example low speed pre-ignition (LSPI) knock detection and mitigation process according to the principles of the present disclosure; and -
FIGS. 3A-3B are flow diagrams of an example LSPI knock detection, mitigation, and driver notification method according to the principles of the present disclosure. - As mentioned above, low speed pre-ignition (LSPI) knock cannot be mitigated via conventional spark retardation. Because its intensity is orders of magnitude higher than end-gas spark knock, LSPI knock could potentially damage the engine, thereby increasing vehicle warranty costs. In particular, LSPI knock often occurs in smaller displacement engines having high compression ratios, such as a turbocharged four-cylinder engine, particularly during high load operation. In addition, if the incorrect oil and/or fuel is provided to the engine, the probability of LSPI knock increases. Oil grade, for example, may vary from region to region. Thus, there remains a need for improved techniques for detecting and mitigating LSPI knock and, in the event that the vehicle cannot mitigate the LSPI knock, instructing the driver of the vehicle to provide the proper oil and/or fuel to the engine and, if all of the above fails to mitigate the LSPI knock, instructing the driver of the vehicle to take the vehicle to a service center for service.
- Referring now to
FIG. 1 , a diagram of avehicle 100 having anengine 104 is illustrated. Theengine 104 is configured to combust a fuel/air mixture to generate drive torque. Non-limiting examples of theengine 104 include a spark ignition direct injection (SIDI) engine, but it will be appreciated that the techniques of the present disclosure could be applicable to any suitable engine comprising a knock sensor, such as a port fuel injection (PH) engine. In some implementations, theengine 104 could be a gasoline compression ignition engine (homogeneous charge compression ignition (HCCI), partially pre-mixed charge compression ignition (PPCI), pre-mixed charge compression ignition, etc.). Theengine 104 draws air into anintake manifold 108 through aninduction system 112 that is regulated by athrottle valve 116. The air in theintake manifold 108 is distributed to a plurality ofcylinders 120 and therein combined with fuel injected by respectiveDI fuel injectors 124. While four cylinders are shown, it will be appreciated that theengine 100 could have any suitable number of cylinders. In some implementations, theengine 104 includes a boost system 122 (a turbocharger, a supercharger, etc.) having an associated wastegate orsurge valve 126 for regulating boost pressure. - The fuel/air mixture in the
cylinders 120 is compressed by pistons (not shown) and combusted by spark generated byrespective spark plugs 128. For a smaller (e.g., 4 cylinder) configuration of theengine 104 with theboost system 122, a compression ratio of thecylinders 120 may be relatively high. The combustion of the fuel/air mixture within thecylinders 120 drives the pistons (not shown), which rotatably turn acrankshaft 132 to generate drive torque. The drive torque is then transferred, e.g., via a transmission (not shown), to adriveline 136. Aknock sensor 140 is configured to generate a knock signal indicative of vibration of theengine 104 caused by abnormal combustion. In one exemplary implementation, theknock sensor 140 is an accelerometer-based sensor that is mounted to a block of theengine 104. The abnormal combustion, if unaccounted for, causes noticeable vibrations (noise, vibration, and/or harshness, or NVH) and/or could potentially damage theengine 104. While oneknock sensor 140 is illustrated and discussed herein, it will be appreciated that theengine 104 could include a plurality of distinct knock sensors (one knock sensor per cylinder bank or group of cylinders, one knock sensor per cylinder, etc.). - Exhaust gas resulting from combustion is expelled from the
cylinders 120 into an exhaust system 144 configured to treat the exhaust gas before releasing it into the atmosphere. For example, unburnt fuel from the abnormal combustion could cause increase emissions that must then be handled by the exhaust system 144, which could increase the cost or complexity of the exhaust system 144. Acontroller 148 controls operation of theengine system 100, such as controlling the throttle valve 116 (airflow), the DI fuel injectors 124 (fuel), and the spark plugs 128 (spark) and communicates with a display 152 (e.g., a driver interface). Thecontroller 148 also receives the knock signal from theknock sensor 140. Thecontroller 148 is configured to detect knock of theengine 104 by analyzing the knock signal. In one exemplary implementation, thecontroller 148 is configured to detect both (i) LSPI knock and (ii) spark knock using the knock signal, which will be described in greater detail below. While not shown, it will be appreciated that thecontroller 148 is configured to receive other inputs, such as a crank angle measurement (e.g., in crank angle degrees, or CAD) from a crankshaft position sensor (not shown). - Causes of LSPI knock events are numerous. Extended and reoccurring LSPI can lead to thermal runways and surface (cylinder wall) ignition. Possible causes of LSPI events include: (1) hot combustion chamber deposits that flake off and ignite the cylinder charge because the flaking deposit is exposed to long resonance times and elevated pressure, which causes it to ignite, (2) oil droplets from the piston crevice enter into the combustion chamber of the
cylinder 120 and act as a localized octane reducer causing auto-ignition prior to the spark discharge, and (3) auto-ignition prior to the spark discharge due to the boundary conditions, such as in gasoline compression ignition engines. Some engines overcome these surface ignition problems with improved hardware, engine design, and calibration. LSPI events, however, are still problematic in boosted engines with very retarded combustion phasing and high compression ratios (long resonance times at elevated pressure), particularly when operating at low speed and high load. - In one exemplary implementation, the analyzing or processing of the knock signal is as follows. For a particular monitoring window, the knock signal is processed according to associated parameters (signal amplifications, detection thresholds, etc.). In one exemplary implementation, the knock signal is filtered, rectified, and its energy is integrated across the monitoring window to obtain a single value. The window could be calibrated throughout the engine speed range. Based on a fast Fourier transform (FFT), the “knocking frequency” is isolated, which allows monitoring of first and second order pressure oscillations occurring in a particular frequency range (e.g., 5-10 kilohertz (kHz)). As previously discussed herein, only one monitoring window is typically active at a time. Before a new window is active, there may be a reset period for the
controller 148. Thus, by implementing two distinct monitoring windows separated by a controller reset window, asingle controller 148 is capable of detecting both LSPI knock and spark knock using asingle knock sensor 140. - Referring now to
FIG. 2 , a plot of an example LSPI knock detection and mitigation process is illustrated. During normal engine operation prior to time t1, theengine 104 is not limited below its maximum output torque and is generating a nominal torque TN. At time t1, an LSPI knock event is detected. This represents the start of a first phase (Phase 1). It will be appreciated that the term “LSPI knock event” could comprise a plurality of detected occurrences of LSPI knock (e.g., a series of consecutive LSPI knocks). In response to detecting the LSPI knock event, thecontroller 148 limits the torque output of theengine 104 to a first torque limit T1 that is less than the nominal torque TN. This reduction in torque output of theengine 104 could be achieved, for example, by controlling thethrottle valve 116 and/or by controlling the wastegate orsurge valve 126 associated with theboost system 122. This torque reduction is also referred to herein as a “torque derate.” For the initial detected LSPI knock event, thecontroller 148 also enriches the fuel/air ratio of the engine 104 (e.g., increases the amount of fuel injected by the DI fuel injectors 128). As shown, this torque drop to the first torque limit T1 occurs very fast as the process is attempting to quickly mitigate the LSPI knock. The torque output of theengine 104 is held at the first torque limit for a calibratable period, such as a calibratable number of engine power pulse (EPP) events (e.g., 30 EPP events). - After this calibratable period, the
controller 148 removes the limiting and increases engine torque output back to the nominal torque TN. This represents the end ofPhase 1. As shown, however, another LSPI knock event is subsequently detected at time t2. Thus, the fuel enrichment and temporary torque limiting did not mitigate (or fully mitigate) the LSPI knock. This represents the start of a second phase (Phase 2). Thecontroller 148 again limits the torque output of theengine 104 for the calibratable period (e.g., repeat a portion of Phase 1). After this calibratable period, however, thecontroller 148 limits the torque output of the engine to a second torque limit T2. As shown, this second torque limit T2 is greater than the first torque limit T1 but still less than the nominal torque TN. It will be appreciated, however, that the second torque limit T2 could be the same as the first torque limit T1. This second torque limit T2 is maintained by thecontroller 148 for the remainder of a current key cycle of the engine 104 (e.g., until the engine is turned off), after whichPhase 2 ends. When a calibratable number of entries intoPhase 2 have occurred, a first message could be output for the driver. Various exit conditions also exist to effectively reset thisPhase 2 counter. These are discussed in greater detail below with reference toFIGS. 3A-3B . - As shown, before
Phase 2 ends, yet another LSPI knock event is detected at time t3 before the end of the current key cycle of theengine 104. This represents the start of a third phase (Phase 3). Thecontroller 148 limits the torque output of theengine 104 to a third torque limit T3 until a calibratable amount of fuel has been consumed by theengine 104. This calibratable amount of fuel could be one entire fuel tank of thevehicle 100, but it will be appreciated that other suitable amounts could be used. It will also be appreciated that fuel consumption monitoring could continue across one or more partial fuel refill events (e.g., Phase 3 would not end upon any single fuel refill event). While the third torque limit T3 is shown as being less than the first and second torque limits T1 and T2, it will be appreciated that two or all of these torque limits T1, T2, and T3 could have the same magnitudes. After the calibratable amount of fuel has been consumed by theengine 104, Phase 3 ends. When a calibratable number of entries into Phase 3 have occurred, a second message could be output to the driver. Various exit conditions also exist to effectively reset this Phase 3 counter. These are discussed in greater now with reference toFIGS. 3A-3B . - Referring now to
FIGS. 3A-3B , flow diagrams of example LSPI knock detection, mitigation, anddriver notification methods FIG. 3A , anexample method 300 of knock detection, mitigation, and driver notification is illustrated. At 304, thecontroller 148 detects whether an LSPI event has occurred. When true, themethod 300 proceeds to 304. Otherwise, themethod 300 ends or returns to 304. At 308, thecontroller 148 increments an LSPI event counter. At 312, thecontroller 148 determines whether the LSPI event detected at 304 is the first LSPI event of a potential chain of events (e.g., whether the LSPI event counter is equal to one). When true, themethod 300 proceeds to 316 where fuel enrichment (enrichment of the FA ratio of the engine 104) is performed by thecontroller 148. Otherwise, themethod 300 proceeds directly to 320. At 320, thecontroller 148 determines whether there are enough LSPI events to form a chain (e.g., whether the LSPI event counter exceeds a calibratable event threshold). - When true, the
method 300 proceeds to 324. Otherwise, themethod 300 ends or returns to 304. At 324, thecontroller 148 increments an LSPI chain counter. At 328, thecontroller 148 performs short-term torque reduction. This could include, for example, limiting torque to the first torque limit T1 for a calibratable number of EPP events (seeFIG. 2 ). At 332, thecontroller 148 determines whether there are enough chains to derate torque for the remainder of the current trip or key-cycle (e.g., whether the LSPI chain counter exceeds a calibratable chain threshold). When true, themethod 300 proceeds to 336. Otherwise, themethod 300 ends or returns to 304. At 336, thecontroller 148 increments a trip derate counter. At 340, thecontroller 148 performs key cycle torque reduction. This could include, for example, limiting torque to the second torque limit T2 for the remainder of the current key-cycle (seeFIG. 2 ). At 344, thecontroller 148 determines whether there are enough chains or derated trips to derate torque for the remainder of the fuel tank or some other calibratable amount of fuel (e.g., whether the respective counters exceed respective calibratable tank thresholds). When true, themethod 300 proceeds to 348. Otherwise, themethod 300 ends or returns to 304. - At 348, the
controller 148 increments a tank fail counter. At 352, thecontroller 148 performs tank torque reduction. This could include, for example, limiting torque to the third torque limit T3 until the calibratable amount of fuel has been consumed by the engine 104 (seeFIG. 2 ). At 356, thecontroller 148 determines whether there are enough derated tanks or trip events to output the second message instructing the driver to take the vehicle to a service station for service (e.g., whether the respective counters exceed calibratable service thresholds). When true, themethod 300 proceeds to 360 where thecontroller 148 outputs the second message (e.g., to display 152) and themethod 300 then ends or returns to 304. Otherwise, themethod 300 proceeds to 364 where the controller outputs the first message (e.g., to display 152) instructing the driver to provide a specific type or quality of oil and or fuel to thevehicle 100 and themethod 300 then ends or returns to 304. - Referring now to
FIG. 3B , anexample method 380 of controlling the various counters described above is illustrated. At 382, thecontroller 148 determines whether a refuel event has occurred. This could be determined, for example, using a fuel level sensor in a fuel tank of thevehicle 100. When true, themethod 380 proceeds to 384. Otherwise, themethod 380 ends or returns to 382. At 384, thecontroller 148 determines whether a tank derate is currently active. When true, themethod 380 proceeds to 386 where thecontroller 148 clears or discontinues the tank derate and themethod 380 then ends or returns to 382. Otherwise, themethod 380 proceeds to 388. At 388, thecontroller 148 determines whether the tank fail counter is greater than zero. When true, themethod 380 proceeds to 390. Otherwise, themethod 380 ends or returns to 382. At 390, thecontroller 148 increments a clear tank counter. At 392, thecontroller 148 determines whether enough clear tanks (tank refill events) have occurred to decrement the tank fail counter (e.g., whether the number of clear tanks exceeds a calibratable threshold). When true, themethod 380 proceeds to 394. Otherwise, themethod 380 ends or returns to 382. At 394, thecontroller 148 decrements the tank fail counter. At 396, thecontroller 148 sets the clear tank counter to zero and themethod 380 then ends or returns to 382. In other words, a certain number of clear tanks (fuel refill events) without entering the tank derate can result in the tank fail counter being decremented. - It will be appreciated that the term “controller” as used herein refers to any suitable control device or set of multiple control devices that is/are configured to perform at least a portion of the techniques of the present disclosure. Non-limiting examples include an application-specific integrated circuit (ASIC), one or more processors and a non-transitory memory having instructions stored thereon that, when executed by the one or more processors, cause the controller to perform a set of operations corresponding to at least a portion of the techniques of the present disclosure. The one or more processors could be either a single processor or two or more processors operating in a parallel or distributed architecture.
- It should be understood that the mixing and matching of features, elements, methodologies and/or functions between various examples may be expressly contemplated herein so that one skilled in the art would appreciate from the present teachings that features, elements and/or functions of one example may be incorporated into another example as appropriate, unless described otherwise above.
Claims (14)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/387,677 US10823098B1 (en) | 2019-04-18 | 2019-04-18 | Low speed pre-ignition knock detection, mitigation, and driver notification |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/387,677 US10823098B1 (en) | 2019-04-18 | 2019-04-18 | Low speed pre-ignition knock detection, mitigation, and driver notification |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200332737A1 true US20200332737A1 (en) | 2020-10-22 |
US10823098B1 US10823098B1 (en) | 2020-11-03 |
Family
ID=72833201
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/387,677 Active US10823098B1 (en) | 2019-04-18 | 2019-04-18 | Low speed pre-ignition knock detection, mitigation, and driver notification |
Country Status (1)
Country | Link |
---|---|
US (1) | US10823098B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210215116A1 (en) * | 2016-08-31 | 2021-07-15 | Ai Alpine Us Bidco Inc | System and method for determining the timing of an engine event |
WO2022178374A1 (en) * | 2021-02-22 | 2022-08-25 | Caterpillar Inc. | Derating operating strategy and gaseous fuel engine control system |
CN115523034A (en) * | 2022-09-13 | 2022-12-27 | 长城汽车股份有限公司 | Protection method of exhaust pollution conversion device and related equipment |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP7183915B2 (en) * | 2019-03-29 | 2022-12-06 | トヨタ自動車株式会社 | Hybrid vehicle and its control method |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5594649A (en) | 1994-12-19 | 1997-01-14 | Delco Electronics Corporation | Digitally reconfigurable engine knock detecting system |
JP3116826B2 (en) | 1996-07-15 | 2000-12-11 | トヨタ自動車株式会社 | Preignition detection device |
JP3129403B2 (en) | 1997-05-15 | 2001-01-29 | トヨタ自動車株式会社 | Ion current detector |
US6615811B1 (en) | 2002-03-04 | 2003-09-09 | Delphi Technologies, Inc. | Ignition coil integrated ion sense with combustion and knock outputs |
US6883497B2 (en) | 2003-09-17 | 2005-04-26 | General Motors Corporation | Method of preventing preignition for an internal combustion engine |
US7533651B2 (en) | 2006-03-17 | 2009-05-19 | Ford Global Technologies, Llc | System and method for reducing knock and preignition in an internal combustion engine |
DE102008013199A1 (en) | 2008-03-07 | 2009-09-17 | Beru Ag | Apparatus and method for detecting malfunctions in combustion anomalies |
US9080521B2 (en) | 2010-03-01 | 2015-07-14 | Southwest Research Institute | Method and related system of using crankcase pressure to to detect pre-ignition in spark ignition engine |
JP5020367B2 (en) | 2010-10-08 | 2012-09-05 | 三菱電機株式会社 | Preignition estimation control device for internal combustion engine |
US8245692B2 (en) | 2010-12-03 | 2012-08-21 | Ford Global Technologies, Llc | Method and system for pre-ignition control |
US8720416B2 (en) | 2011-01-25 | 2014-05-13 | Southwest Research Institute | Methods and apparatus to detect and inhibit low-speed pre-ignition in an engine |
US9038596B2 (en) * | 2011-12-02 | 2015-05-26 | Ford Global Technologies, Llc | Method and system for pre-ignition control |
DE102012219353B3 (en) | 2012-10-23 | 2014-02-13 | Advanced Combustion Gesellschaft zur Vergabe von Aufträgen zur Berechnung technischer Verbrennungsprozesse mbH | Calculation and forecasting method of knocking and super-knocking processes and control device for the control of combustion processes in internal combustion engines, in particular in gasoline engines |
US8973429B2 (en) | 2013-02-25 | 2015-03-10 | GM Global Technology Operations LLC | System and method for detecting stochastic pre-ignition |
US20150322369A1 (en) | 2014-05-09 | 2015-11-12 | Exxonmobil Research And Engineering Company | Method for preventing or reducing low speed pre-ignition |
US9869262B2 (en) | 2015-01-19 | 2018-01-16 | Fev North America, Inc. | System and process for predicting and preventing pre-ignition |
US9759145B2 (en) | 2015-08-21 | 2017-09-12 | Ford Global Technologies, Llc | Method and system for pre-ignition control |
US9903334B2 (en) | 2016-05-10 | 2018-02-27 | Fca Us Llc | Low speed pre-ignition knock detection |
JP6381726B1 (en) | 2017-04-14 | 2018-08-29 | 三菱電機株式会社 | Abnormal combustion detection device for internal combustion engine |
-
2019
- 2019-04-18 US US16/387,677 patent/US10823098B1/en active Active
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210215116A1 (en) * | 2016-08-31 | 2021-07-15 | Ai Alpine Us Bidco Inc | System and method for determining the timing of an engine event |
US11761398B2 (en) * | 2016-08-31 | 2023-09-19 | Ai Alpine Us Bidco Inc. | System and method for determining the timing of an engine event |
WO2022178374A1 (en) * | 2021-02-22 | 2022-08-25 | Caterpillar Inc. | Derating operating strategy and gaseous fuel engine control system |
CN115523034A (en) * | 2022-09-13 | 2022-12-27 | 长城汽车股份有限公司 | Protection method of exhaust pollution conversion device and related equipment |
Also Published As
Publication number | Publication date |
---|---|
US10823098B1 (en) | 2020-11-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10823098B1 (en) | Low speed pre-ignition knock detection, mitigation, and driver notification | |
US9903334B2 (en) | Low speed pre-ignition knock detection | |
US20150034047A1 (en) | Control device for internal combustion engine | |
US9482202B2 (en) | Torque compensation for detonation | |
US9127604B2 (en) | Control system and method for preventing stochastic pre-ignition in an engine | |
JP2006329158A (en) | Controller for spark ignition type cylinder injection type internal combustion engine | |
US8924134B2 (en) | Knock control device of internal combustion engine | |
JP4784467B2 (en) | Premixed compression ignition internal combustion engine | |
US10208691B2 (en) | System and process for predicting and preventing pre-ignition | |
US20170009728A1 (en) | Method of engine control for eliminating knocking combustion due to a misfire for spark-ignited engines equipped with external exhaust gas recirculation | |
US11187201B1 (en) | Ion current sensing for estimation of combustion phasing in an internal combustion engine | |
US9803570B2 (en) | System and method for controlling engine air flow | |
JP2015014229A (en) | Abnormal combustion avoidance device for internal combustion engine | |
US9835127B2 (en) | Internal combustion engine ignition device and ignition method | |
US10995690B2 (en) | Control device of internal combustion engine | |
US11365712B2 (en) | Control system for a dedicated exhaust gas recirculation engine | |
EP2918821A1 (en) | Engine control system | |
US10570874B2 (en) | Method for operating an internal combustion engine | |
JP6607138B2 (en) | Exhaust gas recirculation control device for internal combustion engine | |
JP2016156295A (en) | Fuel injection control device and fuel injection control method of internal combustion engine | |
GB2604617A (en) | Control method and apparatus for an internal combustion engine | |
KR20190073175A (en) | Noise reduction system of engine | |
JP2013104323A (en) | Device for controlling internal combustion engine | |
JP2014105662A (en) | Engine control device | |
JP2014109196A (en) | Control device for internal combustion engine |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FCA US LLC, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAYER, ETHAN E;STOFFER, JONATHAN D;LAWRENCE, DAVID A;AND OTHERS;SIGNING DATES FROM 20190307 TO 20190412;REEL/FRAME:048926/0895 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |