System and method for self-adjusting engine performance parameters during fuel quality variation

Abstract

A system and method for self-adjusting engine performance parameters in response to fuel quality variations that includes an exhaust sensor for measuring a level of carbon dioxide present in an exhaust manifold, at least one of a knock sensor and a cylinder pressure transducer for determining a location of peak pressure and a centroid, respectively, a controller in communication with the exhaust sensor and the at least one of the knock sensor and the cylinder pressure transducer, the controller correlating a methane number of the fuel used by the engine to a brake specific carbon dioxide value calculated using the level of carbon dioxide measured by the exhaust sensor and the at least one of the centroid and the location of peak pressure, and an adjusting mechanism, wherein the adjusting mechanism adjusts an engine performance parameter based on the determined methane number.

Claims

1. A controller for self-adjusting engine, performance parameters of an engine in response to fuel quality variations, wherein the controller is configured to: receive data that corresponds to a methane number of fuel used within the engine; determine the methane number based on the data that has been received; and adjust an engine performance parameter based on the methane number, and wherein at least one of: the controller is further configured to determine a brake specific carbon dioxide value from the data, the methane number being determined based on the brake specific carbon dioxide value and the controller is further configured to access correlations of the data to the methane number and to determine, based on the correlations, an optimized air-fuel ratio with which to adjust engine performance parameters.

2. The controller of claim 1, wherein one or more programmable tables containing the correlations are programmed into the controller, and wherein the controller uses the one or more programmable tables to determine the methane number.

3. The controller of claim 1, wherein the controller is further configured to determine an optimized air-fuel ratio based on the methane number.

4. The controller of claim 2, wherein the one or more programmable tables containing the correlations programmed into the controller, the one or more programmable tables further correlating the methane number to the optimized air-fuel ratio, and wherein the controller uses the one or more programmable tables to determine the methane number and the optimized air-fuel ratio.

5. The controller of claim 1 wherein the controller is further configured to monitor the methane number using the controller.

6. The controller of claim 1, wherein the controller is further configured to send a target value for the engine performance parameter to an adjusting mechanism to thereby adjust the engine performance parameter based on the methane number.

7. The controller of claim 6, wherein the engine performance parameter is a fuel quantity provided to a mixer that delivers air and fuel to the engine.

8. The controller of claim 7, wherein the controller is further configured to adjust a fuel control valve that controls an amount of fuel delivered to the mixer.

9. The controller of claim 8, wherein the fuel control valve is adjusted based on an optimized air-fuel ratio determined from the methane number by the controller.

10. The controller of claim 1, wherein the controller is an engine control module.

11. An engine system comprising: an exhaust sensor positioned at a location after cylinders of an engine; a controller in communication with the exhaust sensor and configured to: receive data that corresponds to a methane number of fuel used within the engine; determine the methane number based on the data that has been received; and adjust an engine performance parameter based an the methane number, and wherein at least one of the controller is further configured to determine a brake specific carbon dioxide value from the data, the methane number being determined based on the brake specific carbon dioxide value and the controller is further configured to access correlations of the data to the methane number and to determine, based on the correlations, an optimized air-fuel ratio with which to adjust engine performance parameters.

12. The engine system of claim 11, wherein one or more programmable tables containing the correlations further includes correlations of the methane number to an optimized air-fuel ratio, wherein the controller uses the one or more programmable tables to determine the methane number and the optimized air-fuel ratio.

13. The engine system of claim 12, wherein the controller is further configured to send a target value for the engine performance parameter to an adjusting mechanism to thereby adjust the engine performance parameter based on the methane number.

14. The engine system of claim 11, wherein the engine performance parameter is a fuel quantity provided to a mixer that delivers air and fuel to the engine.

15. The engine system of claim 14, wherein the controller is further configured to adjust a fuel control valve that controls an amount of fuel delivered to the mixer.

16. The controller of claim 15, wherein the fuel control valve is adjusted based on an optimized air-fuel ratio determined from the methane number by the controller.

17. A method for self-adjusting engine performance parameters in response to fuel quality variations, the method comprising: receiving data that corresponds to a methane number of fuel used within an engine; determining ti-re methane number based on the data that has been received; and adjusting an engine performance parameter based on the methane number; and at least one of determining a brake specific carbon dioxide value from the data, the methane number being determined based on the brake specific carbon dioxide value and using one or more correlations of the data to the methane number and determining, based on the correlations, an optimized air-fuel ratio with which to adjust engine performance parameters.

18. The method of claim 17, wherein the data comprises an exhaust carbon dioxide value, and wherein the method further comprises controlling an adjusting mechanism in response to the exhaust carbon dioxide value.

19. The method of claim 17, wherein the data comprises an exhaust carbon dioxide value, and wherein the method further comprises determining a brake specific carbon dioxide value from the exhaust carbon dioxide value, and wherein the methane number is determined based on the brake specific carbon dioxide value.

20. The method of claim 19, further comprising: receiving an inlet carbon dioxide value from an inlet sensor; and adjusting the brake specific carbon dioxide value in response to the inlet carbon dioxide value.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) Advantages and features of the embodiments of this disclosure will become more apparent from the following detailed description of exemplary embodiments when viewed in conjunction with the accompanying drawings, wherein:

(2) FIG. 1 is a schematic view of an engine system of the present disclosure including a mixer, an exhaust manifold, an exhaust sensor, at least one of a knock sensor and a cylinder pressure transducer, a controller and an adjusting mechanism;

(3) FIG. 2 is a schematic view of an engine of the engine system of FIG. 1 with an expanded view showing the placement of the knock sensor and the cylinder pressure transducer on a cylinder head of the engine;

(4) FIG. 3 is a schematic view of an engine system of the present disclosure including a mixer, an exhaust manifold, an exhaust sensor, an inlet sensor, a correcting mechanism, at least one of a knock sensor and a cylinder pressure transducer, a controller and an adjusting mechanism;

(5) FIG. 4 is a plot of the relationship between the determined brake specific carbon dioxide values and centroids and/or locations of peak pressure for determining a methane number;

(6) FIG. 5 is a schematic view of a programmable table of a methane number determiner;

(7) FIG. 6 is a schematic view of a programmable table of an air-fuel ratio determiner of the present disclosure;

(8) FIG. 7 is a schematic view of the controller configurations of the engine system of FIG. 1;

(9) FIG. 8 is a schematic view of the controller configurations of the engine system of FIG. 3;

(10) FIG. 9 is a flow diagram of a method of operating the engine system of FIG. 1; and

(11) FIG. 10 is a flow diagram of a method of operating the engine system of FIG. 3.

(12) Corresponding reference characters indicate corresponding parts throughout the several views. Although the drawings represent embodiments of the present disclosure, the drawings are not necessarily to scale and certain features may be exaggerated in order to better illustrate and explain the present disclosure. The exemplifications set out herein illustrate embodiments of the disclosure, in one form, and such exemplifications are not to be construed as limiting the scope of the disclosure in any manner.

DETAILED DESCRIPTION OF THE DRAWINGS

(13) Referring to FIGS. 1 and 3, an engine system 10 generally includes a mixer 12, an inlet manifold 13, an exhaust manifold 14, an exhaust sensor 16, a knock sensor 18 and/or a cylinder pressure transducer 20, a controller 22, an adjusting mechanism 24 and an engine 32. Generally, engine system 10 further includes a center exhaust manifold positioned between cylinder heads of engine 10 (not shown). In various embodiments, engine system 10 may also include at least one turbocharger, at least one charge air cooler, at least one throttle, a compressor bypass, and/or a compressor bypass valve. Additionally, in various embodiments, intake manifold 13 may extend into the center of the engine between the engine's cylinder heads while exhaust manifold 14 includes portions extending along the sides of the engine or intake manifold 13 may include portions along the sides of the engine while exhaust manifold 14 extends out of the center of the engine between the engine's cylinder heads.

(14) In more detail and still referring to FIGS. 1 and 3, mixer 12 generally includes at least two inlets 26, 28 and at least one outlet 30. Air and fuel may be introduced into mixer 12 through inlets 26, 28, and the mixture of air and fuel may then be released from mixer 12 through outlet 30 to engine 32. In various embodiments, a fuel line 38 is fluidly coupled to inlet 28 such that fuel line 38 provides fuel to mixer 12.

(15) Referring to FIGS. 1-3, exhaust manifold 14 is coupled to engine 32 to route exhaust gases resulting from fuel used in engine 32 away from engine 32. Exhaust sensor 16 is positioned along exhaust manifold 14 such that exhaust sensor 16 may measure a level of carbon dioxide present in the exhaust gases within exhaust manifold 14. In various embodiments, exhaust sensor 16 may be positioned at any location after the cylinder(s) of the engine. For instance, exhaust sensor 16 may be positioned along the exhaust manifold, at a turbo charger inlet, at a turbo charger outlet or at an exhaust stack.

(16) Furthermore, knock sensor 18 and/or cylinder pressure transducer 20 are generally in communication with engine 32. In various embodiments, knock sensor 18 and/or cylinder pressure transducer 20 are coupled to at least one cylinder head(s) 31 of engine 32, as shown in FIG. 2. In various embodiments, knock sensor 18 and/or cylinder pressure transducer 20 may be coupled to each cylinder head 31 of engine 32. Furthermore, in various embodiments, knock sensor 18 may be used to determine a location of peak pressure within engine 32. Generally, knock sensor 18 is a simple accelerometer that measures vibration levels on a cylinder head 31 of each cylinder of engine 32. Knock sensor 18 converts the measured vibration levels into an output voltage. The output voltage from knock sensor 18 is directly proportional to the engine combustion quality. By processing the signal coming from the knock sensor, the location of peak pressure can be determined. Location of peak pressure is the location at which the maximum cylinder pressure occurs for each combustion cycle. Additionally, in various embodiments, cylinder pressure transducer 20 may be used to determine a centroid of engine 32. Cylinder pressure transducer 20 is a pressure measurement device which records cylinder pressure for a cylinder on which it is placed. Once the cylinder pressure is obtained, it can be converted to a heat release rate which shows the quality of combustion. Centroid is the point in the heat release rate where 50% of combustion is complete. The centroid is inversely proportional to engine combustion quality. Thus, if the combustion gets slower, the centroid increases in crank angle degrees.

(17) With reference to FIGS. 1 and 3, adjusting mechanism 24 adjusts an engine performance parameter based on a determined methane number. In general, adjusting mechanism 24 is manipulated by controller 22. In various embodiments, the engine performance parameter may include the quantity of fuel provided. In an exemplary embodiment, adjusting mechanism 24 may be a fuel control valve, wherein the fuel control valve controls the amount fuel delivered to mixer 12 based on an optimized air-fuel ratio determined from the methane number by controller 22.

(18) Controller 22 is generally in communication with exhaust sensor 16, knock sensor 18 and/or cylinder pressure transducer 20 and adjusting mechanism 24. Additionally, controller 22 may include a plurality of programmable tables. In an exemplary embodiment of the present disclosure, controller 22 is an engine control module. In certain embodiments, controller 22 forms a portion of a processing subsystem including one or more computing devices having memory, processing, and communication hardware. The controller 22 may be a single device or a distributed device, and the functions of the controller may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium.

(19) Furthermore, in certain embodiments, the controller 22 includes one or more processors, evaluators, regulators and/or determiners that functionally execute the operations of the controller 22. The description herein including processors, evaluators, regulators and/or determiners emphasizes the structural independence of certain aspects of the controller 22, and illustrates one grouping of operations and responsibilities of the controller. Other groupings that execute similar overall operations are understood within the scope of the present application. Processors, evaluators, regulators and/or determiners may be implemented in hardware and/or as computer instructions on a non-transient computer readable storage medium, and may be distributed across various hardware or computer based components.

(20) Certain operations described herein include operations to interpret and/or to determine one or more parameters or data structures. Interpreting or determining, as utilized herein, includes receiving values by any method known in the art, including at least receiving values from a datalink or network communication, receiving an electronic signal (e.g. a voltage, frequency, current, or PWM signal) indicative of the value, receiving a computer generated parameter indicative of the value, reading the value from a memory location on a non-transient computer readable storage medium, receiving the value as a run-time parameter by any means known in the art, and/or by receiving a value by which the interpreted parameter can be calculated, and/or by referencing a default value that is interpreted to be the parameter value.

(21) Example and non-limiting implementation elements that functionally execute the operations of the controller include sensors providing any value determined herein, sensors providing any value that is a precursor to a value determined herein, datalink and/or network hardware including communication chips, oscillating crystals, communication links, cables, twisted pair wiring, coaxial wiring, shielded wiring, transmitters, receivers, and/or transceivers, logic circuits, hard-wired logic circuits, reconfigurable logic circuits in a particular non-transient state configured according to the module specification, any actuator including at least an electrical, hydraulic, or pneumatic actuator, a solenoid, an op-amp, analog control elements (springs, filters, integrators, adders, dividers, gain elements), and/or digital control elements.

(22) Referring now to FIG. 7, controller 22 generally includes one or more processors, evaluators, regulators and/or determiners, such as a centroid/location of peak pressure processor 13, a brake specific carbon dioxide processor 15, a methane number determiner 17, a methane number evaluator 19, an air-fuel ratio determiner 21, and a fueling regulator 23. Brake specific carbon dioxide processor 15 is generally configured to receive measurements of exhaust carbon dioxide levels from exhaust sensor 16, while centroid/location of peak pressure processor 13 is generally configured to receive signals from knock sensor 18 and/or cylinder pressure transducer 20. Furthermore, centroid/location of peak pressure processor 13 is configured to process the signals from knock sensor 18 and/or cylinder pressure transducer 20 to determine a location of peak pressure from knock sensor 18 and/or a centroid from cylinder pressure transducer 20. Additionally, brake specific carbon dioxide processor 15 is configured to calculate a brake specific carbon dioxide value from the level of exhaust carbon dioxide received. The brake specific carbon dioxide value is calculated using Formula I below, where mf.sub.exh.sub.CO2 is the mass flow of CO.sub.2 in exhaust, Brk_pwr is the brake power of the engine, MW.sub.CO2 is the molecular weight of CO.sub.2, MW.sub.exh is the molecular weight of theoretical exhaust, mf.sub.exh is the mass flow of exhaust, and CO2.sub.ppm is the CO.sub.2 concentration measured by the exhaust carbon dioxide sensor 16.

(23) $\begin{array}{cc}\mathrm{BS}\mathrm{CO}2=\frac{m{f}_{ex{h}_{\mathrm{CO}2}}}{Br{k}_{-}pwr}m{f}_{ex{h}_{\mathrm{CO}2}}=\left(\frac{M{W}_{\mathrm{CO}2}}{M{W}_{exh}}\right)*m{f}_{exh}*{\mathrm{CO}2}_{ppm}& \mathrm{Formula}I\end{array}$

(24) Referring to FIGS. 3-5, methane number determiner 17, within controller 22, may be used to determine a methane number of fuel used within engine 32. The relationship by which the methane number can be determined is shown by plotting the determined brake specific carbon dioxide values against centroids/locations of peak performance, as shown in FIG. 4. Methane determiner 17, includes a programmable table 40, shown in FIG. 5, which is programmed with the relationships shown in FIG. 4 such that table 40 may correlate a determined brake specific carbon dioxide value and the centroid and/or the location of peak pressure with an associated methane number of the fuel.

(25) With further reference to FIGS. 6 and 7, air-fuel ratio determiner 21 within controller 22 may be used to determine an optimized air-fuel ratio. Determiner 21 includes a programmable table 42 that is programmed with the hydrogen/carbon ratios of methane numbers, such that the table 42 correlates the determined methane number with an associated optimized air-fuel ratio. The optimized air-fuel ratio may then be used by fueling regulator 23 of controller 22 to adjust an engine performance parameter. The air-fuel ratio is adjusted by changing the fuel control valve position that controls the amount of fuel that is sent to the engine. Fueling regulator 23 may adjust the engine performance parameter by sending a target value to adjusting mechanism 24. In an exemplary embodiment, the engine performance parameter adjusted is the fuel quantity provided to mixer 12, and adjusting mechanism 24 is a fuel control valve. It should be understood that tables 40, 42, while described as being incorporated into controller 22, may be stored or generated on one or more separate devices that are accessed by controller 22 or distributed among controller 22 and one or more separate devices. Additionally, it should be understood that someone of skill in the art with the benefit of the present disclosure could construct these or other suitable tables.

(26) Referring back to FIG. 3, engine system 10 may further include an inlet sensor 34 and a correcting processor 36. Inlet sensor 34 may be positioned at any location upstream of cylinders of the engine. For instance, inlet sensor 34 may be positioned along fuel line 38 leading to mixer 12, in the charge stream from mixer 12 to engine 32, at a fuel inlet, at an inlet to mixer 12, at an outlet of mixer 12, at a turbocharger(s) inlet, at a turbocharger(s) outlet, at a charger air cooler(s) inlet, at a charger air cooler(s) outlet, or before or after one or more throttles or intake manifolds. Furthermore, inlet sensor 34 may be used to measure the level of intake carbon dioxide present in fuel being provided to engine 32. Additionally, correcting processor 36 may be used to subtract the level of intake carbon dioxide from the level of exhaust carbon dioxide prior to calculating the brake specific carbon dioxide value using brake specific carbon dioxide processor 15 of controller 22. In various embodiments, correcting processor 36 may be part of controller 22. In various embodiments, as seen in FIG. 8, inlet sensor 34 may be configured to transmit the level of inlet carbon dioxide directly to BSCO2 processor 15. Thus, in various embodiments, BSCO2 processor 15 may include correcting processor 36.

(27) Referring now to FIG. 9, a method 100 for self-adjusting engine performance in response to fuel quality variations using engine system 10 of the present disclosure is shown. At step 102 of method 100, a level of exhaust carbon dioxide exiting engine 32 is sensed. At step 104, a centroid and/or location of peak pressure in engine 32 is sensed. At step 106, a brake specific carbon dioxide value is calculated from the level of exhaust carbon dioxide using correlations within controller 22. At step 108, a methane number of fuel used by engine 32 is determined from the determined brake specific carbon dioxide value and the centroid and/or location of peak pressure. At step 110, an optimized air-fuel ratio is determined from the methane number. At step 112, an engine performance parameter is adjusted in response to the optimized air-fuel ratio. In an exemplary embodiment, the engine performance parameter is the quantity of fuel supplied.

(28) Referring to FIG. 10, method 100 may further include the steps 114, 116 and 118. At step 114, the methane number is monitored using methane number evaluator 19 of controller 22. At step 116, a level of inlet carbon dioxide of the fuel entering engine 32 is sensed. At step 118, the determined brake specific carbon dioxide value is adjusted in response to the level of inlet carbon dioxide.

(29) Controller 22 may be used to calculate the brake specific carbon dioxide value from the exhaust carbon dioxide level, determine the methane number of fuel used within the engine from the determined brake specific carbon dioxide value and the centroid or the location of peak pressure, determine the optimized air-fuel ratio from the methane number, and adjust an engine performance parameter based on the optimized air-fuel ratio.

(30) While various embodiments of the disclosure have been shown and described, it is understood that these embodiments are not limited thereto. The embodiments may be changed, modified and further applied by those skilled in the art. Therefore, these embodiments are not limited to the detail shown and described previously, but also include all such changes and modifications.

(31) Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements. The scope is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to “at least one of A, B, or C” is used in the claims, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B or C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

(32) In the detailed description herein, references to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art with the benefit of the present disclosure to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.

(33) Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.