Engine Diagnostic System Fuel Injection Anomaly Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional engine diagnostic systems face challenges in accurately detecting hardware anomalies, often resulting in false outputs and uncertainty about the failing component when engine knock or misfire occurs, which can affect engine performance and drivability.

Innovation Solution

A method and system that control a fuel injector to inject different quantities of fuel into engine cylinders, detect corresponding parameter values, and compare them to identify hardware anomalies, using a controller and sensor network to differentiate between normal and abnormal conditions, including faulty sensors and injectors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional knock detection systems are used to detect engine knock, then engine knock can be detected, but false outputs are generated and uncertainty exists about the failing component

Engineering Contradiction:
Improvedetection accuracyVSAvoidcomponent identification uncertainty
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The diagnostic process is segmented into multiple distinct phases: baseline parameter collection with normal fuel injection, anomaly detection phase with reduced fuel injection, and comparison analysis. This segmentation allows the system to isolate and identify specific component failures (knock sensor, fuel injector, or true knock condition) by observing parameter changes across phases, thereby resolving the uncertainty about which component has failed.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If fuel injection quantity is varied to detect hardware anomalies, then precise anomaly detection is achieved, but additional control operations and time are required

Engineering Contradiction:
Improveanomaly detection precisionVSAvoiddiagnostic time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system employs periodic action by implementing a baseline collection phase followed by a diagnostic phase with reduced fuel injection, then comparing results. This periodic structure allows precise anomaly detection through controlled parameter variation while managing diagnostic time by using predetermined threshold comparisons rather than continuous monitoring.

Inventive Principle:
Principle #19Periodic action

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

This approach enables precise detection of hardware anomalies, distinguishing between true and false knock or misfire, allowing for targeted repairs and maintaining engine operability by identifying the root cause of issues.

Implementation Method 1

controlling a fuel injector to inject a first quantity of a fuel into a cylinder from a plurality of cylinders, of an engine

Methodology Applied
Scientific EffectFuel injection: Injector

Implementation Method 2

The air-and-fuel mixture is combusted within a plurality of cylinders to drive pistons which rotatably turn a crankshaft to produce drive torque

Methodology Applied
Scientific EffectCombustion: Combustion

Data Source

PatentUS9617940B2Engine diagnostic system and an associated method thereof
Publication Date: 2017.04.11 TRANSPORTATION IP HOLDINGS LLC
  • US9617940B2 patent drawing
  • US9617940B2 patent drawing
  • US9617940B2 patent drawing

AI summary

A method involves controlling a fuel injector to inject a first quantity of a fuel into a cylinder from a plurality of cylinders, of an engine and detecting a first value of a parameter associated with the engine. The method further involves controlling the fuel injector to inject a second quantity of the fuel different from the first quantity of the fuel, into the cylinder of the engine and detecting a second value of the parameter associated with the engine. The method also involves comparing the first value with the second value and detecting a hardware anomaly associated with the engine based on the comparison of the first value with the second value.