The present application relates generally to systems and methods for implementing corrections to a reductant delivery system in an exhaust aftertreatment system of an internal combustion engine.
For internal combustion engines, such as diesel engines, nitrogen oxide (NOx) compounds may be emitted in exhaust. It may be desirable to reduce NOx emissions to, for example, comply with environmental regulations. To reduce NOx emissions, a reductant may be dosed into the exhaust by a dosing system. The reductant facilitates conversion of a portion of the exhaust into non-NOx emissions, such as nitrogen (N2), carbon dioxide (CO2), and water (H2O), thereby reducing NOx emissions.
In some situations, reductant may be utilized by a dosing system at a rate that is not optimized for the exhaust or engine. For example, as the dosing system ages, the dosing system may no longer be able to accurately determine characteristics of the exhaust that are used to determine how much reductant is dosed into the exhaust. As a result, the dosing system may dose more or less reductant than is needed. If more reductant is dosed than is needed, the reductant may accumulate within downstream components, such as a catalyst, thereby impacting the performance of these components, potentially causing NOx emissions to exceed desired amounts. If less reductant is dosed than is needed, NOx emissions may exceed desired amounts. When NOx emissions exceed desired amounts, a controller may indicate downstream components, such as a catalyst, as having failed. When such an indication occurs, the downstream components are typically serviced or replaced. However, if the excess of NOx emissions is due to the dosing system, and not a failure of the downstream components themselves, servicing and replacement of the downstream components may not remedy the excess of NOx emissions.
In one embodiment, an exhaust aftertreatment system includes a catalyst, an exhaust conduit system, a first sensor, a second sensor, a reductant pump, a dosing module, and a reductant delivery system controller. The exhaust conduit system is coupled to the catalyst. The first sensor is coupled to the exhaust conduit system upstream of the catalyst and configured to obtain a current first measurement upstream of the catalyst. The second sensor is coupled to the exhaust conduit system downstream of the catalyst and configured to obtain a current second measurement downstream of the catalyst. The reductant pump is configured to draw reductant from a reductant source. The dosing module is fluidly coupled to the reductant pump and configured to selectively provide the reductant from the reductant pump into the exhaust conduit system upstream of the catalyst. The reductant delivery system controller is communicable with the first sensor, the second sensor, the reductant pump, and the dosing module. The reductant delivery system controller is configured to receive and store the current first measurement from the first sensor. The reductant delivery system controller is also configured to receive and store the current second measurement from the second sensor. The reductant delivery system controller is also configured to cause the reductant pump to draw the reductant at a first rate. The reductant delivery system controller is also configured to cause the dosing module to provide a first amount of the reductant. The reductant delivery system controller is also configured to determine a current conversion efficiency based on the current first measurement and the current second measurement. The reductant delivery system controller is also configured to store the current conversion efficiency. The reductant delivery system controller is also configured to determine a current low conversion efficiency time based on the current conversion efficiency. The reductant delivery system controller is also configured to determine a current bias index based on the current low conversion efficiency time. The reductant delivery system controller is also configured to compare the current bias index to a bias index threshold. The reductant delivery system controller is also configured to adjust at least one of the first rate or the first amount when the current bias index is greater than the bias index threshold.
In another embodiment, an exhaust aftertreatment system includes a catalyst, a first sensor, a second sensor, a reductant pump, a dosing module, and a reductant delivery system controller. The first sensor is configured to obtain a current first measurement upstream of the catalyst. The second sensor coupled is configured to obtain a current second measurement downstream of the catalyst. The second sensor is also configured to obtain, prior to obtaining the current second measurement, a previous second measurement downstream of the catalyst. The reductant pump is configured to draw reductant from a reductant source. The dosing module is fluidly coupled to the reductant pump and configured to selectively provide the reductant from the reductant pump upstream of the catalyst. The reductant delivery system controller is communicable with the first sensor, the second sensor, the reductant pump, and the dosing module. The reductant delivery system controller is configured to receive and store the previous second measurement from the second sensor. The reductant delivery system controller is also configured to receive and store the current first measurement from the first sensor. The reductant delivery system controller is also configured to receive and store the current second measurement from the second sensor. The reductant delivery system controller is also configured to cause the reductant pump to draw the reductant at a first rate. The reductant delivery system controller is also configured to cause the dosing module to provide a first amount of the reductant. The reductant delivery system controller is also configured to determine a current conversion efficiency based on the current first measurement and the current second measurement. The reductant delivery system controller is also configured to store the current conversion efficiency. The reductant delivery system controller is also configured to determine a current low conversion efficiency time based on the current conversion efficiency. The reductant delivery system controller is also configured to determine an average second measurement differential based on the current second measurement and the previous second measurement. The reductant delivery system controller is also configured to compare an absolute value of the average second measurement differential to a second measurement spike initial threshold. The reductant delivery system controller is also configured to increase a positive bias counter in response to the absolute value of the average second measurement differential not being greater than the second measurement spike initial threshold. The reductant delivery system controller is also configured to compare the absolute value of the average second measurement differential to a second measurement spike secondary threshold in response to the absolute value of the average second measurement differential not being greater than the second measurement spike initial threshold. The reductant delivery system controller is also configured to increase a negative bias counter in response to the absolute value of the average second measurement differential not being less than the second measurement spike secondary threshold. The reductant delivery system controller is also configured to determine a current bias index based on the negative bias counter and at least one of: the current low conversion efficiency time or the positive bias counter. The reductant delivery system controller is also configured to compare the current bias index to a bias index threshold. The reductant delivery system controller is also configured to adjust at least one of the first rate or the first amount when the current bias index is greater than the bias index threshold.
In yet another embodiment, an exhaust aftertreatment system includes a catalyst, a first sensor, a second sensor, a catalyst temperature sensor, a reductant pump, a dosing module, and a reductant delivery system controller. The first sensor is configured to obtain a current first measurement upstream of the catalyst. The second sensor is configured to obtain a current second measurement downstream of the catalyst. The catalyst temperature sensor is coupled to the catalyst and configured to obtain a temperature of the catalyst. The reductant pump is configured to draw reductant from a reductant source. The dosing module is fluidly coupled to the reductant pump and configured to selectively provide the reductant from the reductant pump upstream of the catalyst. The reductant delivery system controller is communicable with the first sensor, the second sensor, the catalyst temperature sensor, the reductant pump, and the dosing module. The reductant delivery system controller is configured to cause the reductant pump to draw the reductant at a first rate. The reductant delivery system controller is also configured to cause the dosing module to provide a first amount of the reductant. The reductant delivery system controller is also configured to receive and store the current first measurement from the first sensor. The reductant delivery system controller is also configured to receive and store the current second measurement from the second sensor. The reductant delivery system controller is also configured to determine that the first sensor is obtaining the current first measurement. The reductant delivery system controller is also configured to determine that the second sensor is obtaining the current second measurement. The reductant delivery system controller is also configured to compare the catalyst temperature to a target catalyst temperature range. The reductant delivery system controller is also configured to, after determining that (i) the first sensor is obtaining the current first measurement, (ii) the second sensor is obtaining the current second measurement, and (iii) the catalyst temperature is within the target catalyst temperature range, determine a current conversion efficiency based on the current first measurement and the current second measurement. The reductant delivery system controller is also configured to store the current conversion efficiency. The reductant delivery system controller is also configured to adjust at least one of the first rate or the first amount based on the current conversion efficiency.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the disclosure will become apparent from the description, the drawings, and the claims, in which:
It will be recognized that some or all of the figures are schematic representations for purposes of illustration. The figures are provided for the purpose of illustrating one or more implementations with the explicit understanding that they will not be used to limit the scope or the meaning of the claims.
Following below are more detailed descriptions of various concepts related to, and implementations of, methods, apparatuses, and for implementing corrections to a reductant delivery system in an exhaust aftertreatment system of an internal combustion engine. The various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways, as the described concepts are not limited to any particular manner of implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes.
Internal combustion engines (e.g., diesel internal combustion engines, etc.) produce exhaust gases that are often treated by a dosing module within an exhaust aftertreatment system. A dosing module typically treats exhaust gases using a reductant. The reductant is adsorbed by a catalyst. The adsorbed reductant in the catalyst functions to reduce NO in the exhaust gases. Therefore, the amount of reductant that is adsorbed in the catalyst must be maintained at an acceptable level in order for the catalyst to continue to reduce NO in the exhaust gases.
The dosing module typically provides the reductant into the exhaust gases based on a measurement of NO exiting the system (e.g., the NO provided to atmosphere by the system). When this measurement increases, the dosing module increases the amount of reductant provided to the exhaust gases. Conversely, when this measurement decreases, the dosing module decreases the amount of reductant provided to the exhaust gases. In some instances, this measurement can be inaccurate and therefore can cause the dosing module to provide more or less reductant than is needed to reduce NO in the exhaust gases to a desired level.
As a result of providing too much reductant, the catalyst can become saturated and unable to adsorb additional reductant. When the catalyst is saturated, the reductant may slip from the catalyst and be sensed by the sensor as NO in the exhaust gases, thereby distorting the measurement obtained by the sensor. As a result, the dosing module may provide additional reductant to the exhaust gases or may indicate that the catalyst has failed (e.g., is no longer capable of desirably reducing NOR). This may cause premature servicing and/or replacement of the catalyst and represents a substantial cost to an owner and/or warrantor of the exhaust aftertreatment system.
Additionally, the increased consumption of reductant results in inefficiency in the use of the reductant by the exhaust aftertreatment system and causes the exhaust aftertreatment system to initiate more burn-off cycles than otherwise would occur. Burn-off cycles are used by an exhaust aftertreatment system to burn off reductant that is adsorbed in the catalyst by providing hotter exhaust gases to the catalyst. To provide these hotter exhaust gases, the internal combustion engine consumes additional fuel. Therefore, the increased consumption of reductant results in inefficiency in the use of the fuel by the internal combustion engine.
As a result of providing too little reductant, the dosing module may not have adsorbed enough reductant to be capable of desirably reducing NOx in the exhaust gases. In some instances, such as when the amount of NOx being received by the catalyst is low, the measurement read by the sensor may indicate a desirable reduction in NOx when, in fact, the NOx has not been desirably reduced. This may cause the exhaust aftertreatment system to emit more NOx than desired.
Implementations described herein relate to an exhaust aftertreatment system that includes a catalyst, a first sensor configured to obtain a NOx measurement upstream of the catalyst, a second sensor configured to obtain a NOx measurement downstream of the catalyst, a reductant pump, a reductant delivery system, and a reductant delivery system controller. The reductant delivery system controller is capable of receiving, storing, and comparing the NOx measurements from the sensors to determine if the catalyst is saturated (e.g., has adsorbed a maximum amount of reductant), has not adsorbed enough reductant to be able to convert NOx desirably, or if the catalyst is failed. Based on these determinations, the reductant delivery system controller is able to adjust an amount of reductant that is provided in order to substantially prevent saturation of the catalyst while ensuring that the catalyst has adsorbed enough reductant to be able to convert NOx desirably. In this way, the exhaust aftertreatment system is able to minimize the likelihood that a catalyst will be inaccurately indicated as failed, thereby reducing cost to the owner or warrantor, while minimizing reductant and fuel consumption. As a result, the exhaust aftertreatment system described herein is significantly more desirable than other systems which are not able of determining if too much or too little reductant is being provided due to inaccurate NOx measurements.
The DPF 106 is configured to (e.g., structured to, able to, etc.) remove particulate matter, such as soot, from exhaust gas flowing in the exhaust conduit system 104. The DPF 106 includes an inlet, where the exhaust gas is received, and an outlet, where the exhaust gas exits after having particulate matter substantially filtered from the exhaust gas and/or converting the particulate matter into carbon dioxide. In some implementations, the DPF 106 may be omitted.
The decomposition chamber 108 is configured to convert a reductant into ammonia. The reductant may be, for example, urea, diesel exhaust fluid (DEF), Adblue®, a urea water solution (UWS), an aqueous urea solution (e.g., AUS32, etc.), and other similar fluids. The decomposition chamber 108 includes a reductant delivery system 102 having a doser or dosing module 114 configured to dose the reductant into the decomposition chamber 108 (e.g., via an injector). In some implementations, the reductant is injected upstream of the SCR catalyst 110. The reductant droplets then undergo the processes of evaporation, thermolysis, and hydrolysis to form gaseous ammonia within the exhaust conduit system 104. The decomposition chamber 108 includes an inlet in fluid communication with the DPF 106 to receive the exhaust gas containing NOx emissions and an outlet for the exhaust gas, NOx emissions, ammonia, and/or reductant to flow to the SCR catalyst 110.
The decomposition chamber 108 includes the dosing module 114 mounted to the decomposition chamber 108 such that the dosing module 114 may dose the reductant into the exhaust gases flowing in the exhaust conduit system 104. The dosing module 114 may include an insulator 116 interposed between a portion of the dosing module 114 and the portion of the decomposition chamber 108 on which the dosing module 114 is mounted. The dosing module 114 is fluidly coupled to (e.g., fluidly configured to communicate with, etc.) a reductant source 118. The reductant source 118 may include multiple reductant sources 118. The reductant source 118 may be, for example, a diesel exhaust fluid tank containing Adblue®.
A supply unit or reductant pump 120 is used to pressurize the reductant from the reductant source 118 for delivery to the dosing module 114. In some embodiments, the reductant pump 120 is pressure controlled (e.g., controlled to obtain a target pressure, etc.). The reductant pump 120 includes a reductant filter 122. The reductant filter 122 filters (e.g., strains, etc.) the reductant prior to the reductant being provided to internal components (e.g., pistons, vanes, etc.) of the reductant pump 120. For example, the reductant filter 122 may inhibit or prevent the transmission of solids (e.g., solidified reductant, contaminants, etc.) to the internal components of the reductant pump 120. In this way, the reductant filter 122 may facilitate prolonged desirable operation of the reductant pump 120. In some embodiments, the reductant pump 120 is coupled to a chassis of a vehicle associated with the exhaust aftertreatment system 100.
The dosing module 114, the EONOx sensor 111, the SONOx sensor 112, the catalyst temperature sensor 113, and the reductant pump 120 are also electrically or communicatively coupled to a reductant delivery system controller 124. The reductant delivery system controller 124 is configured to control the dosing module 114 to dose the reductant into the decomposition chamber 108. The reductant delivery system controller 124 may also be configured to control the reductant pump 120.
The reductant delivery system controller 124 includes a processing circuit 126. The processing circuit 126 includes a processor 128 and a memory 130. The processor 128 may include a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc., or combinations thereof. The memory 130 may include, but is not limited to, electronic, optical, magnetic, or any other storage or transmission device capable of providing a processor, ASIC, FPGA, etc. with program instructions. This memory 130 may include a memory chip, Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), flash memory, or any other suitable memory from which the reductant delivery system controller 124 can read instructions. The instructions may include code from any suitable programming language. The memory 130 may include various modules that include instructions which are configured to be implemented by the processor 128.
The reductant delivery system controller 124 is configured to communicate with a central controller 132 (e.g., engine control unit (ECU)), engine control module (ECM), etc.) of an internal combustion engine having the exhaust aftertreatment system 100. In some embodiments, the central controller 132 and the reductant delivery system controller 124 are integrated into a single controller.
The central controller 132 is communicable with a display device 134 (e.g., screen, monitor, touch screen, heads up display (HUD), indicator light, etc.). The display device 134 is configured to change state in response to receiving information from the central controller 132. For example, the display device 134 may be configured to change between a static state (e.g., displaying a green light, displaying a “SYSTEM OK” message, etc.) and an alarm state (e.g., displaying a blinking red light, displaying a “SERVICE NEEDED” message, etc.) based on a communication from the central controller 132. By changing state, the display device 134 may provide an indication to a user (e.g., operator, etc.) of a status (e.g., operation, in need of service, etc.) of the reductant delivery system 102.
The SCR catalyst 110 is configured to assist in the reduction of NOx emissions by accelerating a NOx reduction process between the ammonia and the NOx of the exhaust gas into diatomic nitrogen, water, and/or carbon dioxide. The SCR catalyst 110 includes an inlet in fluid communication with the decomposition chamber 108 from which exhaust gas and reductant are received and an outlet in fluid communication with an end of the exhaust conduit system 104.
The exhaust aftertreatment system 100 may further include an oxidation catalyst (e.g., a diesel oxidation catalyst (DOC)) in fluid communication with the exhaust conduit system 104 (e.g., downstream of the SCR catalyst 110 or upstream of the DPF 106) to oxidize hydrocarbons and carbon monoxide in the exhaust gas.
In some implementations, the DPF 106 may be positioned downstream of the decomposition chamber 108. For instance, the DPF 106 and the SCR catalyst 110 may be combined into a single unit. In some implementations, the dosing module 114 may instead be positioned downstream of a turbocharger or upstream of a turbocharger.
The EONOx sensor 111 may be coupled to the exhaust conduit system 104 to detect a condition of the exhaust gas flowing through the exhaust conduit system 104 downstream of the internal combustion engine associated with the exhaust conduit system 104 and upstream of the DPF 106. In some implementations, the EONOx sensor 111 may have a portion disposed within the exhaust conduit system 104; for example, a tip of the EONOx sensor 111 may extend into a portion of the exhaust conduit system 104. In other implementations, the EONOx sensor 111 may receive exhaust gas through another conduit, such as one or more sample pipes extending from the exhaust conduit system 104.
The SONOx sensor 112 may be coupled to the exhaust conduit system 104 to detect a condition of the exhaust gas flowing through the exhaust conduit system 104 downstream of the SCR catalyst 110. In some implementations, the SONOx sensor 112 may have a portion disposed within the exhaust conduit system 104; for example, a tip of the SONOx sensor 112 may extend into a portion of the exhaust conduit system 104. In other implementations, the SONOx sensor 112 may receive exhaust gas through another conduit, such as one or more sample pipes extending from the exhaust conduit system 104.
The EONOx sensor 111 is configured to measure a EONOx measurement for the exhaust aftertreatment system 100 and the SONOx sensor 112 is configured to measure a SONOx measurement for the exhaust aftertreatment system 100. The EONOx measurement for the exhaust aftertreatment system 100 is a measurement of the amount of NOx (e.g., in parts per million, etc.) in the exhaust provided to the exhaust aftertreatment system 100 by the internal combustion engine. The SONOx measurement for the exhaust aftertreatment system 100 is a measurement of the amount of NOx in the exhaust provided by the exhaust aftertreatment system 100 into atmosphere.
The EONOx sensor 111 and the SONOx sensor 112 are each independently operable between an operational state (e.g., valid state, functioning state, etc.) and a non-operational state (e.g., invalid state, malfunctioning state, etc.). When the EONOx sensor 111 and/or the SONOx sensor 112 are in the operational state, NO measurements are obtained in a normal fashion. However, when the EONOx sensor 111 and/or the SONOx sensor 112 is in the non-operational state, NO measurements are not obtained in a normal fashion. When the EONOx sensor 111 and/or the SONOx sensor 112 is in the non-operational state, the reductant delivery system controller 124 is configured to change a state of the display device 134 to instruct an operator to service the EONOx sensor 111 and/or the SONOx sensor 112.
As is explained in more detail below, the reductant delivery system controller 124 is configured to variously interact with the reductant delivery system 102 and the central controller 132 to change a state of the display device 134. For example, where the comparison performed by the reductant delivery system controller 124 indicates that the SONOx measurement exceeds the NO target emission, the central controller 132 may cause the display device 134 to display an alert to a user indicating that service of the reductant delivery system 102 is needed.
The exhaust aftertreatment system 100 may be configured to maintain the SONOx measurement below a target SONOx emission amount. The target SONOx emission amount may be, for example, a maximum NO emission amount permitted under local environmental regulations. The reductant delivery system controller 124 is configured to store the target NOx emission amount and to compare the NO target emission amount to the SONOx measurement. The comparison may be performed by the reductant delivery system controller 124 in a substantially continuous fashion (e.g., every second, etc.) or periodically (e.g., every five seconds, every minute, every five minutes, every ten minutes, every hour, etc.).
While the EONOx sensor 111 is depicted as positioned upstream of the DPF 106, it should be understood that the EONOx sensor 111 may be positioned at any other position of the exhaust conduit system 104, within the DPF 106, between the DPF 106 and the decomposition chamber 108, or within the decomposition chamber 108. In addition, two or more EONOx sensors 111 may be utilized for detecting a condition of the exhaust gas, such as two, three, four, five, or six EONOx sensors 111 with each EONOx sensor 111 located at one of the aforementioned positions of the exhaust conduit system 104.
While the SONOx sensor 112 is depicted as positioned downstream of the SCR catalyst 110, it should be understood that the SONOx sensor 112 may be positioned at any other position of the exhaust conduit system 104, within the decomposition chamber 108, between the decomposition chamber 108 and the SCR catalyst 110, within the SCR catalyst 110, or downstream of the SCR catalyst 110. In addition, two or more SONOx sensors 112 may be utilized for detecting a condition of the exhaust gas, such as two, three, four, five, or six SONOx sensors 112 with each SONOx sensor 112 located at one of the aforementioned positions of the exhaust conduit system 104.
The catalyst temperature sensor 113 is configured to measure a temperature of the SCR catalyst 110. For example, the catalyst temperature sensor 113 may measure a temperature of a catalyst bed of the SCR catalyst 110. The reductant delivery system controller 124 is configured to compare the temperature of the SCR catalyst 110 to a target temperature range of the SCR catalyst 110 to determine (e.g., compute, calculate, etc.) if the SCR catalyst 110 has a temperature that is outside of the target temperature range (e.g., the SCR catalyst 110 has a temperature that exceeds a target maximum temperature for the SCR catalyst 110, the SCR catalyst 110 has a temperature that does not exceed a target minimum temperature for the SCR catalyst 110, etc.). The target temperature range may be associated with temperatures where the SCR catalyst 110 performs optimal NO reduction.
The catalyst temperature sensor 113 is operable between an operational state (e.g., valid state, functioning state, etc.) and a non-operational state (e.g., invalid state, malfunctioning state, etc.). When the catalyst temperature sensor 113 is in the operational state, temperature measurements of the SCR catalyst 110 are obtained in a normal fashion. However, when the catalyst temperature sensor 113 is in the non-operational state, temperature measurements of the SCR catalyst 110 are not obtained in a normal fashion. When the catalyst temperature sensor 113 is in the non-operational state, the reductant delivery system controller 124 is configured to change a state of the display device 134 to instruct an operator to service the catalyst temperature sensor 113.
The dosing module 114 includes a dosing lance assembly 136. The dosing lance assembly 136 includes a delivery conduit (e.g., delivery pipe, delivery hose, etc.). The delivery conduit is fluidly coupled to the reductant pump 120. The dosing lance assembly 136 includes at least one injector 138. The injector 138 is configured to dose the reductant into the exhaust gases (e.g., within the decomposition chamber 108, etc.). While not shown, it is understood that the dosing module 114 may include a plurality of injectors 138.
In some embodiments, the reductant delivery system 102 also includes an air pump 140. In these embodiments, the air pump 140 draws air from an air source 142 (e.g., air intake, etc.). Additionally, the air pump 140 provides the air to the dosing module 114 via a conduit. In these embodiments, the dosing module 114 is configured to mix the air and the reductant into an air-reductant mixture and to provide the air-reductant mixture into the decomposition chamber 108. In other embodiments, the reductant delivery system 102 does not include the air pump 140 or the air source 142. In such embodiments, the dosing module 114 is not configured to mix the reductant with air.
In normal operation of the exhaust aftertreatment system 100, where the reductant delivery system 102 is dosing a correct amount of reductant to the exhaust gases (e.g., as opposed to dosing too much reductant or too little reductant, etc.), a EONOx measurement (MEONOx), obtained from the EONOx sensor 111, and a SONOx measurement (MSONOx), obtained from the SONOx sensor 112, generally change together (e.g., increases in the EONOx measurement (MEONOx) generally correspond to increases in the SONOx measurement (MSONOx), and decreases in the EONOx measurement (MEONOx) generally correspond to decreases in the SONOx measurement (MSONOx)). The reductant delivery system control strategy 200 operates to detect instances where the SONOx measurement (MSONOx) changes more or less than it should in order to determine if the reductant delivery system 102 is dosing too much reductant or too little reductant, and then operates to correct the amount of reductant the reductant delivery system 102 is dosing to prevent any over-dosing or under-dosing.
The SCR catalyst 110 adsorbs the reductant to convert NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O), thereby reducing the SONOx measurement (MSONOx) as opposed to if the SCR catalyst were not included in the exhaust aftertreatment system 100. The SCR catalyst 110 is defined by a storage capacity beyond which the SCR catalyst 110 can no longer substantively adsorb the reductant (e.g., the SCR catalyst 110 can only adsorb so much reductant) and therefore can no longer desirably convert NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O) (e.g., the SCR catalyst 110 can only convert so much NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O)). Furthermore, if a catalyst has not adsorbed enough reductant, the catalyst may not be able to desirably convert NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O). Therefore, it is important to ensure that a catalyst has both adsorbed enough reductant so as to be able to convert NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O) while not adsorbing too much reductant so as to be unable to adsorb additional reductant. The reductant delivery system control strategy 200 operates to prevent under-dosing, so that the SCR catalyst is capable of converting NOx into nitrogen (N2), carbon dioxide (CO2), and water (H2O), and over-dosing, so that the SCR catalyst 110 is capable of adsorbing additional reductant.
During the reductant delivery system control strategy 200, various abort conditions are capable of immediately terminating the reductant delivery system control strategy 200. The abort conditions for the reductant delivery system control strategy 200 may include, for example, detecting, by the reductant delivery system controller 124, a failure of the reductant pump 120, a failure of the reductant filter 122, a failure of the reductant source 118, a failure of the EONOx sensor 111, a failure of the SONOx sensor 112, a lack of reductant in the reductant source 118 (e.g., a reductant tank is empty, etc.), a leak in a conduit, and other similar conditions.
The reductant delivery system control strategy 200 begins in block 202 with setting, by the reductant delivery system controller 124, a global counter (G), a positive bias counter (P), a negative bias counter (N), a catalyst counter (K), a low conversion efficiency level counter (A), a positive incremental counter (a), and a negative incremental counter (β) to zero. Block 202 may be represented by the following equations:
The reductant delivery system control strategy 200 continues in block 203 with setting, by the reductant delivery system controller 124, a universal counter (Ω) to 1. Block 203 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 204 with setting a local counter (c) to zero as shown in the following equation:
The global counter (G), positive bias counter (P), negative bias counter (N), catalyst counter (K), and local counter (c) are utilized by the reductant delivery system controller 124 to catalogue consecutive iterations (e.g., operations, executions, etc.) of the reductant delivery system control strategy 200 such that an instant iteration of the reductant delivery system control strategy 200 can be compared to a previous, or a series of previous, iterations of the reductant delivery system control strategy 200.
The reductant delivery system control strategy 200 continues with a functionality verification test 206. The functionality verification test begins in block 208 with determining, by the reductant delivery system controller 124, if the EONOx sensor 111 is in the functional state. If the EONOx sensor 111 is not in the functional state (e.g., the EONOx sensor 111 is in the non-functional state), the reductant delivery system control strategy 200 continues in block 210 with causing, by the reductant delivery system controller 124, the display device 134 to display an error indicating that service of the EONOx sensor 111 is needed (e.g., a message stating “SERVICE OF ENGINE-OUT NOX SENSOR REQUIRED,” etc.). Thereafter, the reductant delivery system control strategy 200 continues with block 208. This causes the reductant delivery system control strategy 200 to wait until the EONOx sensor 111 has been serviced and is in the functional state before proceeding. However, it is understood that in some embodiments the reductant delivery system control strategy 200 may continue (e.g., after waiting a target amount of time for service to be performed, etc.) despite the EONOX sensor 111 being in the non-functional state.
If the EONOx sensor 111 is in the functional state in block 208, the functionality verification test 206 continues in block 212 with determining, by the reductant delivery system controller 124, if the SONOx sensor 112 is in the functional state. If the SONOx sensor 112 is not in the functional state (e.g., the SONOx sensor 112 is in the non-functional state), the reductant delivery system control strategy 200 continues in block 214 with causing, by the reductant delivery system controller 124, the display device 134 to display an error indicating that service of the SONOx sensor 112 is needed (e.g., a message stating “SERVICE OF SYSTEM-OUT NOx SENSOR REQUIRED,” etc.). Thereafter, the reductant delivery system control strategy 200 continues with block 208. This causes the reductant delivery system control strategy 200 to wait until the SONOx sensor 112 has been serviced and is in the functional state before proceeding. However, it is understood that in some embodiments the reductant delivery system control strategy 200 may continue (e.g., after waiting a target amount of time for service to be performed, etc.) despite the SONOX sensor 112 being in the non-functional state.
If the SONOx sensor 112 is in the functional state in block 212, the functionality verification test 206 continues in block 216 with determining, by the reductant delivery system controller 124, if the catalyst temperature sensor 113 is in the functional state. If the catalyst temperature sensor 113 is not in the functional state (e.g., the catalyst temperature sensor 113 is in the non-functional state), the reductant delivery system control strategy 200 continues in block 218 with causing, by the reductant delivery system controller 124, the display device 134 to display an error indicating that service of the catalyst temperature sensor 113 is needed (e.g., a message stating “SERVICE OF CATALYST TEMPERATURE SENSOR REQUIRED,” etc.). Thereafter, the reductant delivery system control strategy 200 continues with block 208. This causes the reductant delivery system control strategy 200 to wait until the catalyst temperature sensor 113 has been serviced and is in the functional state before proceeding. However, it is understood that in some embodiments the reductant delivery system control strategy 200 may continue (e.g., after waiting a target amount of time for service to be performed, etc.) despite the catalyst temperature sensor 113 being in the non-functional state.
If the catalyst temperature sensor 113 is in the functional state in block 216, the functionality verification test 206 continues in block 220 with determining, by the reductant delivery system controller 124, if the catalyst temperature (Tcatalyst) catalyst temperature sensor 113 is within a target temperature range between a target maximum catalyst temperature (Tmax) and a target minimum catalyst temperature (Tmin). Block 220 may be represented by the following equations, only one of which can be true at any given time:
If the catalyst temperature is not within the target temperature range (e.g., either Equation (11) or (12) is true, etc.), the reductant delivery system control strategy 200 continues in block 222 with causing, by the reductant delivery system controller 124, the display device 134 to display an error indicating that the catalyst temperature is not within the target temperature range (e.g., a message stating “CATALYST TEMPERATURE NOT WITHIN RANGE,” a message stating “CATALYST TEMPERATURE TOO HIGH,” a message stating “CATALYST TEMPERATURE TOO LOW,” etc.). Thereafter, the reductant delivery system control strategy 200 continues with block 208. This causes the reductant delivery system control strategy 200 to wait until the catalyst temperature is within the target temperature range before proceeding. However, it is understood that in some embodiments the reductant delivery system control strategy 200 may continue (e.g., after waiting a target amount of time for the catalyst temperature to be within the target temperature range, etc.) despite the catalyst temperature not being within the target temperature range.
If the catalyst temperature is within the target temperature range in block 220, the functionality verification test 206 continues in block 224 with computing, by the reductant delivery system controller 124, a conversion efficiency (CE) by subtracting the SONOx measurement (MSONOx) from the EONOx measurement (MEONOx), dividing by the EONOx measurement (MEONOx), and multiplying by 100%. Block 224 may be represented by the following equation:
The functionality verification test 206 continues in block 226 with determining, by the reductant delivery system controller 124, if the conversion efficiency (CE) catalyst temperature sensor 113 is within a target conversion efficiency range between a target maximum conversion efficiency (CEmax) and a target minimum conversion efficiency (CEmin). Block 226 may be represented by the following equations, only one of which can be true at any given time:
The target maximum conversion efficiency (CEmax) may be associated with a conversion efficiency (CE) that occurs when the SCR catalyst 110 has no, or almost no, ability to store any additional byproducts of chemical reactions between the reductant and the exhaust gases. This may occur when the SCR catalyst 110 has become saturated and needs to be replaced in order for the exhaust aftertreatment system 100 to continue to operate desirably. The target minimum conversion efficiency (CEmin) may be associated with a conversion efficiency (CE) that occurs when the SCR catalyst 110 has a leak or otherwise lacks the ability to store any substantive amount of the byproducts of chemical reactions between the reductant and the exhaust gases. This may occur when the SCR catalyst 110 fails (e.g., a portion of the SCR catalyst 110 becomes dislodged and creates a pathway through the SCR catalyst 110, etc.) and needs to be replaced in order for the exhaust aftertreatment system 100 to continue to operate desirably.
If the conversion efficiency (CE) is not within the target conversion efficiency (CE) range (e.g., either Equation (15) or (16) is true, etc.), the reductant delivery system control strategy 200 continues in block 228 with causing, by the reductant delivery system controller 124, the display device 134 to display an error indicating that the service of the SCR catalyst 110 is needed (e.g., a message stating “SERVICE CATALYST,” etc.). Thereafter, the reductant delivery system control strategy 200 continues with block 208. This causes the reductant delivery system control strategy 200 to wait until the SCR catalyst 110 has been serviced before proceeding. However, it is understood that in some embodiments the reductant delivery system control strategy 200 may continue (e.g., after waiting a target amount of time for the catalyst to be serviced, etc.) despite the conversion efficiency (CE) not being within the target conversion efficiency (CE) range.
If the conversion efficiency (CE) is not within the target conversion efficiency (CE) range (e.g., Equation (14) is true, etc.), the functionality verification test 206 ends and the reductant delivery system control strategy 200 continues in block 300 with increasing, by the reductant delivery system controller 124, the local counter (c) by one.
The reductant delivery system control strategy 200 continues in block 304 with indexing, by the reductant delivery system controller 124, the EONOx measurement (MEONOx), obtained from the EONOx sensor 111, with the local counter (c). This indexing produces a locally-indexed EONOx measurement (MEONOx, c) having two components: one being the EONOx measurement (MEONOx) and the other being the local counter (c). A listing of a portion of the locally-indexed EONOx measurements (MEONOx, c), according to some embodiments, is shown in Table 1 below.
The reductant delivery system control strategy 200 continues in block 310 with indexing, by the reductant delivery system controller 124, the SONOx measurement (MSONOx), obtained from the SONOx sensor 112, with the local counter (c). This indexing produces a locally-indexed SONOx measurement (MSONOx, c) having two components: one being the SONOx measurement (MSONOx) and the other being the local counter (c). A listing of a portion of the locally-indexed SONOx measurements (MSONOx, c), according to some embodiments, is shown in Table 2 below.
The reductant delivery system control strategy 200 continues in block 312 with computing, by the reductant delivery system controller 124, a SONOx differential (dSONOx) by subtracting a SONOx measurement (MSONOx, c-1) for the previous local counter (e.g., local counter—1) from the SONOx measurement (MSONOx, c) for the local counter. Block 312 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 314 with indexing, by the reductant delivery system controller 124, the SONOx differential (dSONOx) with the local counter (c). This indexing produces a locally-indexed SONOx differential (dSONOx, c) having two components: one being the SONOx differential (dSONOx) and the other being the local counter (c). A listing of a portion of the locally-indexed SONOx differentials (dSONOx, c), according to some embodiments, is shown in Table 3 below.
In some embodiments, the SONOx differential (dSONOx) is determined by subtracting a SONOx measurement (MSONOx) for the local counter of one from the SONOx measurement (MSONOx) for the local counter. In these embodiments, the SONOx differential (dSONOx) is always relative to the first SONOx measurement (MSONOx, 1). It is understood that other similar methodologies for computing the SONOx differential (dSONOx) are also possible (e.g., using averages of the SONOx measurement (MSONOx), etc.).
The reductant delivery system control strategy 200 continues in block 315 with indexing, by the reductant delivery system controller 124, the conversion efficiency (CE) with the local counter (c). This indexing produces a locally-indexed conversion efficiency (CEc) having two components: one being the conversion efficiency (CE) and the other being the local counter (c). A listing of a portion of the locally-indexed conversion efficiencies (CEc), according to some embodiments, is shown in Table 4 below.
The reductant delivery system control strategy 200 continues in block 316 with determining, by the reductant delivery system controller 124, a target local counter (Gtarget). The target local counter (ctarget) is utilized by the reductant delivery system controller 124 to establish an “evaluation window” where a series of EONOx measurements (MEONOx) and SONOx measurements (MSONOx) are determined and indexed. The target local counter (ctarget) is selected so that enough time elapses as to be sufficient to observe spikes (e.g., substantial increases, substantial decreases, etc.) in the SONOx measurement (MSONOx) while mitigating the possibility of “false positives” (e.g., “noise,” etc.) or increases or decreases that are not due to legitimate spikes in the SONOx measurement (MSONOx). As will be explained in more detail herein, these spikes can be helpful in identifying whether the reductant delivery system 102 is dosing too much or too little reductant. In various embodiments, the target local counter (ctarget) is selected to be equal to an amount of time necessary for the reductant delivery system 102 to stabilize (e.g., for the internal combustion engine having the aftertreatment system 100 to reach steady state, etc.). In some embodiments, the target local counter (ctarget) is 10 minutes. In other embodiments, the target local counter (ctarget) is 20 minutes. In other embodiments, the target local counter (ctarget) is between 5 minutes and 10 minutes. The target local counter (ctarget) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the target local counter (ctarget) via machine learning, etc.).
The reductant delivery system control strategy 200 continues in block 317 with determining, by the reductant delivery system controller 124, if the local counter (c) is equal to the target local counter (ctarget). Block 317 may be represented by the following equations, only one of which can be true at any given time:
If in block 317, the local counter (c) is less than the target local counter (ctarget) (e.g., if Equation (18) is true), the reductant delivery system control strategy 200 continues with block 208.
However, if in block 317, the local counter (c) is equal to the target local counter (ctarget) (e.g., if Equation (19) is true), the reductant delivery system control strategy 200 continues in block 318 with increasing, by the reductant delivery system controller 124, the global counter (G) by one. The global counter (G) is different and distinct from the local counter (c) and facilitates indexing separate from the local counter (c).
The reductant delivery system control strategy 200 continues in block 324 with computing, by the reductant delivery system controller 124, a SONOx average differential (ΔSONOx). The SONOx average differential (ΔSONOx) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the SONOx average differential (ΔSONOx) is determined by averaging the SONOx differentials (dSONOx) indexed with local counters of all values (e.g., dSONOx, 1 through dSONOx, ctarget). Block 324 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 326 with indexing, by the reductant delivery system controller 124, the SONOx average differential (ΔSONOx) with the global counter (G). This indexing produces a globally-indexed SONOx average differential (ΔSONOx, G) having two components: one being the SONOx average differential (ΔSONOx) and the other being the global counter (G). As will be explained in more detail herein, the reductant delivery system control strategy 200 can cause additional increases to the global counter (G) and therefore produce additional globally-indexed SONOx average differentials (ΔSONOx, G). A listing of a portion of the globally-indexed SONOx average differentials (ΔSONOx, G), according to some embodiments, is shown in Table 5 below.
The reductant delivery system control strategy 200 continues in block 328 with computing, by the reductant delivery system controller 124, an SONOx average measurement (W). The SONOx average measurement (W) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the SONOx average measurement (W) is determined by averaging the SONOx measurement (MSONOx) indexed with local counters of all values (e.g., MSONOx, 1 through MSONOx, ctarget). Block 328 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 330 with indexing, by the reductant delivery system controller 124, the SONOx average measurement (W) with the global counter (G). This indexing produces a globally-indexed SONOx average measurement (W) having two components: one being the SONOx average measurement (W) and the other being the global counter (G). As will be explained in more detail herein, the reductant delivery system control strategy 200 increases the global counter (G) and therefore produce additional globally-indexed SONOx average measurement (W). A listing of a portion of the globally-indexed SONOx average measurement (W), according to some embodiments, is shown in Table 6 below.
The reductant delivery system control strategy 200 continues in block 332 with computing, by the reductant delivery system controller 124, an average conversion efficiency (ΔCE). The average conversion efficiency (ΔCE) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the average conversion efficiency (ΔCE) is determined by averaging the conversion efficiencies (CE) indexed with local counters of all values (e.g., CE1 through CEctarget). Block 332 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 334 with indexing, by the reductant delivery system controller 124, the average conversion efficiency (ΔCE) with the global counter (G). This indexing produces a globally-indexed average conversion efficiency (ΔCE, G) having two components: one being the average conversion efficiency (ΔCE) and the other being the global counter (G). As will be explained in more detail herein, the reductant delivery system control strategy 200 can cause additional increases to the global counter (G) and therefore produce additional globally-indexed average conversion efficiencies (ΔCE, G). A listing of a portion of the globally-indexed average conversion efficiency (ΔCE, G), according to some embodiments, is shown in Table 7 below.
The reductant delivery system control strategy 200 continues in block 336 with determining, by the reductant delivery system controller 124, a low conversion level efficiency threshold (J). The low conversion efficiency level threshold (J) is utilized by the reductant delivery system controller 124 to determine an amount of time, based on the global counter (G), that the exhaust aftertreatment system 100 is not efficient enough at converting NOx produced by the internal combustion engine associated with the exhaust aftertreatment system 100. The low conversion efficiency level threshold (J) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the low conversion efficiency level threshold (J) via machine learning, etc.). In various embodiments, the low conversion level efficiency threshold (J) (e.g., is not updated by the reductant delivery system control strategy 200, etc.) is static and is determined based on emissions regulation requirements. For example, the low conversion efficiency level threshold (J) may be hard-coded (e.g., written into the program without any variables, etc.). In some embodiments, servicers and/or manufacturers of the reductant delivery system 102 can update the low conversion efficiency level threshold (J) based on changes to emission regulation requirements.
The reductant delivery system control strategy 200 continues in block 338 with determining by the reductant delivery system controller 124, if average conversion efficiency (ΔCE, G) is less than the low conversion efficiency level threshold (J). Block 338 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the average conversion efficiency (ΔCE, G) is not less than the low conversion efficiency level threshold (J) (e.g., if Equation (24) is true), the reductant delivery system control strategy 200 continues in block 340 with increasing, by the reductant delivery system controller 124, the low conversion efficiency level counter (A) by one. However, if the reductant delivery system controller 124 determines that the average conversion efficiency (ΔCE, G) is less than the low conversion efficiency level threshold (J) (e.g., if Equation (23) is true), the reductant delivery system control strategy 200 does not increase the low conversion efficiency level counter (A) by one.
Next, the reductant delivery system control strategy 200 operates to determine if the SONOx average differential (ΔSONOx, G) changed more or less than it should have. To do this, the reductant delivery system control strategy 200 continues in block 402 with determining, by the reductant delivery system controller 124, a SONOx spike initial threshold (SSONOx, initial). The SONOx spike initial threshold (SSONOx, initial) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the SONOx spike initial threshold (SSONOx, initial) via machine learning, etc.). In various embodiments, the SONOx spike initial threshold (SSONOx, initial) is determined by a manufacturer of the reductant delivery system 102. The manufacturer may determine the SONOx spike initial threshold (SSONOx, initial) by testing the reductant delivery system 102 and optimizing the reductant delivery system control strategy 200 so that NOx emissions by the aftertreatment system 100 are maintained at a desirable level and such that usage of the reductant delivery system 102 is maintained at a desirable level. In one such embodiment, the SONOx spike initial threshold (SSONOx, initial) is 20 parts per million (PPM) per second.
The reductant delivery system control strategy 200 then continues in block 404 with determining, by the reductant delivery system controller 124, if the absolute value of the SONOx average differential (ΔSONOx, G) for the current global counter (e.g., as opposed to a previous global counter, etc.) is greater than the SONOx spike initial threshold (SSONOx, initial). Block 404 may be represented by the following equations, only one of which can be true at any given time:
If the absolute value of the SONOx average differential (ΔSONOx, G) is greater than the SONOx spike initial threshold (SSONOx, initial) (e.g., if Equation (25) is true), the absolute value of the SONOx average differential (ΔSONOx, G) did not change less than it should have and the reductant delivery system control strategy 200 operates to determine if the absolute value of the SONOx average differential (ΔSONOx, G) changed more than it should have. To do this, the reductant delivery system control strategy 200 continues in block 406 with determining, by the reductant delivery system controller 124, a SONOx spike secondary threshold (SSONOx, secondary). The SONOx spike secondary threshold (SSONOx, secondary) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the SONOx spike secondary threshold (SSONOx, secondary) via machine learning, etc.). In various embodiments, the SONOx spike second threshold (SSONOx, secondary) is determined by a manufacturer of the reductant delivery system 102. The manufacturer may determine the SONOx spike secondary threshold (SSONOx, secondary) by testing the reductant delivery system 102 and optimizing the reductant delivery system control strategy 200 so that NO emissions by the aftertreatment system 100 are maintained at a desirable level and such that usage of the reductant delivery system 102 is maintained at a desirable level. In one such embodiment, the SONOx spike secondary threshold (SSONOx, secondary) is 50 parts per million (PPM) per second.
The reductant delivery system control strategy 200 then continues in block 408 with determining, by the reductant delivery system controller 124, if the absolute value of the SONOx average differential (ΔSONOx, G) for the current global counter (e.g., as opposed to a previous global counter, etc.) is greater than the SONOx spike secondary threshold (SSONOx, secondary). Block 408 may be represented by the following equations, only one of which can be true at any given time:
If the absolute value of the SONOx average differential (ΔSONOx, G) is less than the SONOx spike initial threshold (SSONOx, initial) (e.g., if Equation (28) is true), the absolute value of the SONOx average differential (ΔSONOx, G) did not change more than it should have and the reductant delivery system control strategy 200 continues in block 512 with determining, by the reductant delivery system controller 124, an initial conversion efficiency level threshold (LCE, initial). The initial conversion efficiency level threshold (LCE, initial) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the initial conversion efficiency level threshold (LCE, initial) via machine learning, etc.). The initial conversion efficiency level threshold (LCE, initial) is a function of the temperature of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.) and a flow rate of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.). In various embodiments, when the temperature of the exhaust gases in the aftertreatment system 100 is 250° C., the initial conversion efficiency level threshold (LCE, initial) is 70% and when the temperature of the exhaust gases in the aftertreatment system 100 is 300° C., the initial conversion efficiency level threshold (LCE, initial) is 90%. In other embodiments, the initial conversion efficiency level threshold (LCE, initial) is a bounded range, rather than a single value.
The reductant delivery system control strategy 200 then continues in block 514 with determining, by the reductant delivery system controller 124, if current average conversion efficiency (ΔCE, G) is less than the initial conversion efficiency level threshold (LCE, initial). Block 514 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is less than the initial conversion efficiency level threshold (LCE, initial) (e.g., if Equation (29) is true), then the reductant delivery system control strategy 200 continues in block 516 with determining, by the reductant delivery system controller 124, a secondary conversion efficiency level threshold (LCE, secondary). The secondary conversion efficiency level threshold (LCE, secondary) is different and distinct from the initial conversion efficiency level threshold (LCE, initial). The secondary conversion efficiency level threshold (LCE, secondary) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the secondary conversion efficiency level threshold (LCE, secondary) via machine learning, etc.). The secondary conversion efficiency level threshold (LCE, secondary) is a function of the temperature of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.) and a flow rate of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.). In various embodiments, when the temperature of the exhaust gases in the aftertreatment system 100 is 250° C., the secondary conversion efficiency level threshold (LCE, secondary) is 10% and when the temperature of the exhaust gases in the aftertreatment system 100 is 300° C., the secondary conversion efficiency level threshold (LCE, secondary) is 20%. In other embodiments, the secondary conversion efficiency level threshold (LCE, secondary) is equal to the product of the initial conversion efficiency level threshold (LCE, initial) and a constant. In such embodiments, the secondary conversion efficiency level threshold (LCE, secondary) is a percentage (e.g., a minimum percentage) of the initial conversion efficiency level threshold (LCE, initial). In other embodiments, the secondary conversion efficiency level threshold (LCE, secondary) is a fixed value that is not a function of the initial conversion efficiency level threshold (LCE, initial). In other embodiments, the secondary conversion efficiency level threshold (LCE, secondary) is a bounded range, rather than a single value.
The reductant delivery system control strategy 200 then continues in block 518 with determining, by the reductant delivery system controller 124, if the current average conversion efficiency (ΔCE, G) is greater than the secondary conversion efficiency level threshold (LCE, secondary). Block 518 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is greater than the secondary conversion efficiency level threshold (LCE) (e.g., if Equation (32) is true), the reductant delivery system control strategy 200 continues with determining if the SCR catalyst 110 is experiencing persistent reductant slip. Persistent reductant slip may occur where the SCR catalyst 110 is saturated and cannot adsorb anymore reductant, thereby causing reductant to slip through the SCR catalyst 110 towards the SONOx sensor 112. This reductant slip may impede accurate measurement of the NOx exiting the SCR catalyst 110.
The reductant delivery system control strategy 200 continues in block 600 with determining, by the reductant delivery system controller 124, a tertiary conversion efficiency level threshold (LCE, tertiary). The tertiary conversion efficiency level threshold ((LCE, tertiary) is different and distinct from the initial conversion efficiency level threshold (LCE, initial), and the secondary conversion efficiency level threshold (LCE, secondary). The tertiary conversion efficiency level threshold (LCE, tertiary) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the tertiary conversion efficiency level threshold ((LCE, tertiary) via machine learning, etc.). The tertiary conversion efficiency level threshold (LCE, tertiary) is a function of the temperature of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.) and a flow rate of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.). In various embodiments, when the temperature of the exhaust gases in the aftertreatment system 100 is 250° C., the tertiary conversion efficiency level threshold (LCE, tertiary) is 40% and when the temperature of the exhaust gases in the aftertreatment system 100 is 300° C., the tertiary conversion efficiency level threshold (LCE, tertiary) is 60%. In other embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is equal to the product of the initial conversion efficiency level threshold (LCE, initial) and a constant. In such embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is a percentage (e.g., a minimum percentage) of the initial conversion efficiency level threshold (LCE, initial). In other embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is equal to the product of the secondary conversion efficiency level threshold (LCE, secondary) and a constant. In such embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is a percentage (e.g., a minimum percentage) of the secondary conversion efficiency level threshold (LCE, secondary). In other embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is a fixed value that is not a function of the initial conversion efficiency level threshold (LCE, initial), or the secondary conversion efficiency level threshold (LCE, secondary). In other embodiments, the tertiary conversion efficiency level threshold (LCE, tertiary) is a bounded range, rather than a single value.
The reductant delivery system control strategy 200 then continues in block 602 with determining, by the reductant delivery system controller 124, if the current average conversion efficiency (ΔCE, G) is less than the tertiary conversion efficiency level threshold (LCE, tertiary). Block 602 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (34) is true), the reductant delivery system control strategy 200 continues in block 604 with determining by the reductant delivery system controller 124, if the previous average conversion efficiency (ΔCE, G-1) is less than the tertiary conversion efficiency level threshold (LCE, tertiary). Block 604 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (36) is true), the reductant delivery system control strategy 200 continues in block 606 with determining by the reductant delivery system controller 124, if the next previous average conversion efficiency (ΔCE, G-2) is less than the tertiary conversion efficiency level threshold (LCE, tertiary). Block 606 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the next previous average conversion efficiency (ΔCE, G-2) is less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (38) is true), the reductant delivery system control strategy 200 continues in block 608 with increasing, by the reductant delivery system controller 124, the positive bias counter (P) by one. The positive bias counter (P) is different and distinct from the local counter (c) and the global counter (G).
If in block 404, the absolute value of the SONOx average differential (ΔSONOx, G) is not greater than the SONOx spike initial threshold (SSONOx, initial) (e.g., if Equation (26) is true), the absolute value of the SONOx average differential (ΔSONOx, G) changed less than it should have and the reductant delivery system control strategy 200 continues to block 608, thereby increasing the positive bias counter (P) by one.
If in block 518, the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is not greater than the secondary conversion efficiency level threshold (LCE) (e.g., if Equation (31) is true), the reductant delivery system control strategy 200 continues to block 608, thereby increasing the positive bias counter (P) by one.
If in block 606, the reductant delivery controller determines that the next previous average conversion efficiency (ΔCE, G-2) is not less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (37) is true), the reductant delivery system controller 124 does not increase the positive bias counter (P) by one. Similarly, if in block 604, the reductant delivery controller determines that the previous average conversion efficiency (ΔCE, G-1) is not less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (35) is true), the reductant delivery system controller 124 does not increase the positive bias counter (P) by one.
It is understood that additional operations, similar to block 606, may be included in the reductant delivery system control strategy 200, such that a target number of previous average conversion efficiencies are compared to the tertiary conversion efficiency level threshold (LCE, tertiary) to determine if the positive bias counter (P) is to be increased by one. Additionally or alternatively, averages or other products, summations, of the average conversion efficiencies may be utilized in block 602, block 604, block 606, and/or in any similar operations.
If in block 602, the reductant delivery controller determines that the current average conversion efficiency (ΔCE, G) is not less than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (33) is true), the reductant delivery system controller 124 does not increase the positive bias counter (P) by one. Instead, the reductant delivery system control strategy 200 continues in block 700 with determining, by the reductant delivery system controller 124, a quaternary conversion efficiency level threshold (LCE, quaternary). The quaternary conversion efficiency level threshold (LCE, quaternary) is different and distinct from the initial conversion efficiency level threshold (LCE, quaternary), the secondary conversion efficiency level threshold (LCE, secondary), and the tertiary conversion efficiency level threshold (LCE, tertiary). The quaternary conversion efficiency level threshold (LCE, quaternary) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the quaternary conversion efficiency level threshold (LCE, quaternary) via machine learning, etc.). The quaternary conversion efficiency level threshold (LCE, quaternary) is a function of the temperature of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.) and a flow rate of the exhaust gases in the aftertreatment system 100 (e.g., as measured by a sensor downstream of the SCR catalyst 110, etc.). In various embodiments, when the temperature of the exhaust gases in the aftertreatment system 100 is 250° C., the quaternary conversion efficiency level threshold (LCE, quaternary) is 60% and when the temperature of the exhaust gases in the aftertreatment system 100 is 300° C., the quaternary conversion efficiency level threshold (LCE, quaternary) is 70%. In other embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is equal to the product of the initial conversion efficiency level threshold (LCE, initial) and a constant. In such embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is a percentage (e.g., a minimum percentage) of the initial conversion efficiency level threshold (LCE, initial). In other embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is equal to the product of the secondary conversion efficiency level threshold (LCE, secondary) and a constant. In such embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is a percentage (e.g., a minimum percentage) of the secondary conversion efficiency level threshold (LCE, secondary). In other embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is equal to the product of the tertiary conversion efficiency level threshold (LCE, tertiary) and a constant. In such embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is a percentage (e.g., a minimum percentage) of the tertiary conversion efficiency level threshold (LCE, tertiary). In other embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is a fixed value that is not a function of the initial conversion efficiency level threshold (LCE, initial), the secondary conversion efficiency level threshold (LCE, secondary), or the tertiary conversion efficiency level threshold (LCE, tertiary). In other embodiments, the quaternary conversion efficiency level threshold (LCE, quaternary) is a bounded range, rather than a single value.
The reductant delivery system control strategy 200 then continues in block 702 with determining, by the reductant delivery system controller 124, if the current average conversion efficiency (ΔCE, G) is greater than the quaternary conversion efficiency level threshold (LCE, quaternary). Block 702 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is greater than the quaternary conversion efficiency level threshold (LCE, quaternary) (e.g., if Equation (39) is true), the reductant delivery system control strategy 200 continues in block 704 with determining by the reductant delivery system controller 124, if the previous average conversion efficiency (ΔCE, G-1) is greater than the quaternary conversion efficiency level threshold (LCE, quaternary). Block 704 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is greater than the tertiary conversion efficiency level threshold (LCE, tertiary) (e.g., if Equation (41) is true), the reductant delivery system control strategy 200 continues in block 706 with increasing, by the reductant delivery system controller 124, the negative bias counter (N) by one. The negative bias counter (N) is different and distinct from the positive bias counter (P), the local counter (c), and the global counter (G).
If in block 408, the absolute value of the SONOx average differential (ΔSONOx, G) is not less than the SONOx spike initial threshold (SSONOx, initial) (e.g., if Equation (27)(28) is true), the absolute value of the SONOx average differential (ΔSONOx, G) changed more than it should have and the reductant delivery system control strategy 200 continues to block 706, thereby increasing the negative bias counter (N) by one.
If in block 514, the reductant delivery system controller 124 determines that the current average conversion efficiency (ΔCE, G) is not less than the initial conversion efficiency level threshold (LCE, initial) (e.g., if Equation (30) is true), the reductant delivery system control strategy 200 continues to block 706, thereby increasing the negative bias counter (N) by one.
If in block 704, the reductant delivery controller determines that the previous average conversion efficiency (ΔCE, G-1) is not greater than the quaternary conversion efficiency level threshold (LCE, quaternary) (e.g., if Equation (42) is true), the reductant delivery system controller 124 does not increase the negative bias counter (N) by one. Similarly, if in block 702, the reductant delivery controller determines that the average conversion efficiency (ΔCE, G) is not greater than the quaternary conversion efficiency level threshold (LCE, quaternary) (e.g., if Equation (40) is true), the reductant delivery system controller 124 does not increase the negative bias counter (N) by one.
It is understood that additional operations, similar to block 704, may be included in the reductant delivery system control strategy 200, such that a target number of previous average conversion efficiencies are compared to the quaternary conversion efficiency level threshold (LCE, quaternary) to determine if the negative bias counter (N) is to be increased by one. Additionally or alternatively, averages or other products, summations, of the average conversion efficiencies may be utilized in block 702, block 704, and/or in any similar operations. However, the number of previous average conversion efficiencies compared to the quaternary conversion efficiency level threshold (LCE, quaternary) does not exceed the number of previous average conversion efficiencies compared to the tertiary conversion efficiency level threshold (LCE, tertiary).
In various embodiments, the initial conversion efficiency level threshold (LCE, initial) is greater than the secondary conversion efficiency level threshold (LCE, secondary), the quaternary conversion efficiency level threshold (LCE, quaternary) is greater than the secondary conversion efficiency level threshold (LCE, secondary) and less than the initial conversion efficiency level threshold (LCE, initial), and the tertiary conversion efficiency level threshold (LCE, tertiary) is less than the initial conversion efficiency level threshold (LCE, initial), less than the quaternary conversion efficiency level threshold (LCE, quaternary), and greater than the secondary conversion efficiency level threshold (LCE, secondary). This relationship is shown in the following equation:
This relationship is also shown in
After the positive bias counter (P) and negative bias counter (N) have been increased, or have had the opportunity to have been increased, the reductant delivery system control strategy 200 continues in block 800 with determining, by the reductant delivery system controller 124, a target global counter (Gtarget). The target global counter (Gtarget) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the target global counter (Gtarget) via machine learning, etc.). The target global counter (Gtarget) may be a function of the current average conversion efficiency (ΔCE, G).
The reductant delivery system control strategy 200 continues in block 802 with determining, by the reductant delivery system controller 124, if the global counter (G) is equal to the target global counter (Gtarget). Block 802 may be represented by the following equations, only one of which can be true at any given time:
If in block 802, the global counter (G) is less than the target global counter (Gtarget) (e.g., if Equation (44) is true), the reductant delivery system control strategy 200 continues with block 204.
However, if in block 802, the global counter (G) is equal to the target global counter (Gtarget) (e.g., if Equation (45) is true), the reductant delivery system control strategy 200 continues in block 804 with determining, by the reductant delivery system controller 124, a global average conversion efficiency (Y). The global average conversion efficiency (Y) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the global average conversion efficiency (Y) is determined by averaging the average conversion efficiencies (ΔCE) indexed with global counters of all values (e.g., CE1 through CEGtarget). Block 804 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 806 with determining, by the reductant delivery system controller 124, a target global average conversion efficiency (U). The target global average conversion efficiency (U) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the target global average conversion efficiency (U) via machine learning, etc.). In various embodiments, the target global average conversion efficiency (U) is greater than 95%.
The reductant delivery system control strategy 200 continues in block 808 with determining, by the reductant delivery system controller 124, if the global average conversion efficiency (Y) is greater than the target global average conversion efficiency (U). Block 808 may be represented by the following equations, only one of which can be true at any given time:
If in block 808, the global average conversion efficiency (Y) is not greater than the target global average conversion efficiency (U) (e.g., if Equation (47) is true), the reductant delivery system control strategy 200 continues with block 204.
If in block 808, the global average conversion efficiency (Y) is greater than the target global average conversion efficiency (U) (e.g., if Equation (48) is true), the reductant delivery system control strategy 200 continues in block 810 with determining, by the reductant delivery system controller 124, a target negative bias counter (Q). The target negative bias counter (Q) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the target negative bias counter (Q) via machine learning, etc.). The target negative bias counter (Q) may be a function of the current average conversion efficiency (ΔCE, G). In various embodiments, the target negative bias counter (Q) is 1.
The reductant delivery system control strategy 200 continues in block 812 with determining, by the reductant delivery system controller 124, if the negative bias counter (N) is less than the target negative bias counter (Q). Block 812 may be represented by the following equations, only one of which can be true at any given time:
If in block 812, the negative bias counter (N) is not less than the target negative bias counter (Q) (e.g., if Equation (50) is true), the reductant delivery system control strategy 200 continues in block 814 with setting, by the reductant delivery system controller 124, a bias constant (ψ) equal to −1. The bias constant (ψ) is used to indicate whether the bias is positive, due to overdosing of the reductant by the reductant delivery system 102, or negative, due to under dosing of the reductant by the reductant delivery system 102.
The reductant delivery system control strategy 200 continues in block 816 with determining, by the reductant delivery system controller 124, a global average SONOx average measurement (Z). The global average SONOx average measurement (Z) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the global average SONOx average measurement (Z) is determined by averaging the SONOx average measurements (W) indexed with global counters of all values (e.g., W1 through WGtarget). Block 816 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 818 with determining, by the reductant delivery system controller 124, a global low conversion efficiency time (X) (e.g., a current low conversion efficiency time). The global low conversion efficiency time (X) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the global low conversion efficiency time (X) is determined by dividing the low conversion efficiency level counter (A) by the target global counter (Gtarget). Block 818 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 820 with determining, by the reductant delivery system controller 124, a bias index (B). The bias index (B) may be determined in a variety of fashions such that the reductant delivery system control strategy 200 is tailored for a target application.
In various embodiments, the bias index (B) is determined by multiplying the bias constant (ψ) by the sum of the global low conversion efficiency time (X) and the global average SONOx average measurement (Z). Block 820 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 822 with indexing, by the reductant delivery system controller 124, the bias index (B) with the universal counter (a). This indexing produces a universally-indexed bias index (BΩ) having two components: one being the bias index (B) and the other being the universal counter (Ω). A listing of a portion of the universally-indexed bias indexes (BΩ), according to some embodiments, is shown in Table 9 below.
If in block 812, the negative bias counter (N) is less than the target negative bias counter (1) (e.g., if Equation (49) is true), the reductant delivery system control strategy 200 continues in block 824 with determining, by the reductant delivery system controller 124, a target positive bias counter (I). The target positive bias counter (I) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the target positive bias counter (I) via machine learning, etc.). The target positive bias counter (I) may be a function of the current average conversion efficiency (ΔCE, G). In various embodiments, the target positive bias counter (I) is 1.
The reductant delivery system control strategy 200 continues in block 826 with determining, by the reductant delivery system controller 124, if the positive bias counter (P) is less than the target positive bias counter (I). Block 826 may be represented by the following equations, only one of which can be true at any given time:
If in block 826, the positive bias counter (P) is not less than the target positive bias counter (I) (e.g., if Equation (54) is true), the reductant delivery system control strategy 200 continues in block 828 with setting, by the reductant delivery system controller 124, the bias constant (ψ) equal to 1. The reductant delivery system control strategy 200 then continues with block 816.
If in block 826, the positive bias counter (P) is less than the target positive bias counter (I) (e.g., if Equation (55) is true), the reductant delivery system control strategy 200 continues in block 830 with setting, by the reductant delivery system controller 124, the bias index (B) equal to 0. The reductant delivery system control strategy 200 then continues with block 822.
The reductant delivery system control strategy 200 then continues in block 832 with determining, by the reductant delivery system controller 124, if the bias index (BΩ) is less than 0 (e.g., a bias index threshold). Block 832 may be represented by the following equations, only one of which can be true at any given time:
If in block 832, the bias index (BΩ) is less than 0 (e.g., if Equation (56) is true), the reductant delivery system control strategy 200 continues in block 834 with determining, if the bias index (BO is greater than the previous bias index (BΩ-1). Block 834 may be represented by the following equations, only one of which can be true at any given time:
If in block 834, the bias index (BΩ) is not greater than the previous bias index (BΩ-1) (e.g., if Equation (59) is true), then the reductant delivery system control strategy 200 continues in block 836 with increasing, by the reductant delivery system controller 124, the negative incremental counter (β) by 1.
The reductant delivery system control strategy 200 in block 900 with determining, by the reductant delivery system controller 124, a negative incremental counter threshold (σ). The negative incremental counter threshold (σ) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the negative incremental counter threshold (σ) via machine learning, etc.). In various embodiments, the negative incremental counter threshold (σ) is 1.
The reductant delivery system control strategy 200 continues in block 902 with determining, by the reductant delivery system controller 124, if the negative incremental counter (β) is less than the negative incremental counter threshold (σ). Block 902 may be represented by the following equations, only one of which can be true at any given time:
If in block 902, the negative incremental counter (β) is not less than negative incremental counter threshold (σ) (e.g., if Equation (61) is true), the reductant delivery system control strategy 200 continues in block 904 with determining, by the reductant delivery system controller 124, a correction using the bias index (BO (e.g., using an inverse of the bias index (BΩ), etc.). The correction may be a change in the voltage and/or frequency of the electricity supplied to the reductant pump 120. The correction may be a change in operating pressure and/or operating speed of the reductant pump 120. The correction may be a change in orifice size of the injector 138 (e.g., where the injector 138 is a variably sized injector, etc.). The reductant delivery system control strategy 200 continues in block 906 with implementing, by the reductant delivery system controller 124, the correction. This implementation may be carried out via a communication from the reductant delivery system controller 124 to, for example, the reductant pump 120.
If in block 834, the bias index (BΩ) is greater than the previous bias index (BΩ-1) (e.g., if Equation (58) is true), then the reductant delivery system control strategy 200 continues with block 900.
If in block 832, the bias index (BΩ) is not less than 0 (e.g., if Equation (57) is true), the reductant delivery system control strategy 200 continues in block 910 with determining, if the bias index (BΩ) is less than the previous bias index (BΩ-1). Block 910 may be represented by the following equations, only one of which can be true at any given time:
If in block 910, the bias index (BΩ) is not less than the previous bias index (BΩ-1) (e.g., if Equation (63) is true), then the reductant delivery system control strategy 200 continues in block 912 with increasing, by the reductant delivery system controller 124, the positive incremental counter (a) by 1.
The reductant delivery system control strategy 200 in block 914 with determining, by the reductant delivery system controller 124, a positive incremental counter threshold (γ). The positive incremental counter threshold (γ) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the positive incremental counter threshold (γ) via machine learning, etc.). In various embodiments, positive incremental counter threshold (γ) is 1.
The reductant delivery system control strategy 200 continues in block 916 with determining, by the reductant delivery system controller 124, if the positive incremental counter (a) is less than the positive incremental counter threshold (γ). Block 916 may be represented by the following equations, only one of which can be true at any given time:
If in block 916, the positive incremental counter (a) is not less than positive incremental counter threshold (γ) (e.g., if Equation (65) is true), the reductant delivery system control strategy 200 continues with block 904.
In combination, blocks 904 and 906 cause the reductant dosed into the exhaust gases to increase when the negative incremental counter (β) is not less than the negative incremental counter threshold (σ), to account for negative dosing bias, and cause the reductant dosed into the exhaust gases to decrease when the positive incremental counter (a) is not less than positive incremental counter threshold (γ), to account for positive dosing bias.
The reductant delivery system control strategy 200 continues in block 1000 with determining, by the reductant delivery system controller 124, an absolute bias index (⊖). The absolute bias index (⊖) is calculated by computing the absolute value of the bias index (BΩ). Block 1000 may be represented by the following equation:
The reductant delivery system control strategy 200 continues in block 1002 with indexing, by the reductant delivery system controller 124, the absolute bias index (⊖) with the universal counter (Ω). This indexing produces a universally-indexed absolute bias index (⊖Ω) having two components: one being the absolute bias index (⊖) and the other being the universal counter (Ω). A listing of a portion of the universally-indexed absolute bias indexes (⊖Ω), according to some embodiments, is shown in Table 10 below.
The reductant delivery system control strategy 200 then continues in block 1004 with determining, by the reductant delivery system controller 124, if the current absolute bias index (⊖Ω) is less than the previous absolute bias index (⊖Ω-1). Block 1004 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current absolute bias index (⊖Ω) is not less than the previous absolute bias index (⊖Ω-1) (e.g., if Equation (68) is true), the reductant delivery system control strategy 200 continues in block 1006 with determining, by the reductant delivery system controller 124, if the current absolute bias index (⊖Ω) is less than the next previous absolute bias index (⊖Ω-2). Block 1006 may be represented by the following equations, only one of which can be true at any given time:
If the reductant delivery system controller 124 determines that the current absolute bias index (⊖Ω) is not less than the previous absolute bias index (⊖Ω-1) (e.g., if Equation (70) is true), the reductant delivery system control strategy 200 continues in block 1008 with increasing, by the reductant delivery system controller 124, the catalyst counter (K) by 1.
The reductant delivery system control strategy 200 in block 1010 with determining, by the reductant delivery system controller 124, a catalyst counter threshold (φ). The catalyst counter threshold (φ) may be stored in the reductant delivery system controller 124 and may be constant or varied over time (e.g., the reductant delivery system controller 124 may determine the catalyst counter threshold (φ) via machine learning, etc.). In various embodiments, the catalyst counter threshold (φ) is greater than 1 and less than or equal to 5. In one embodiments, the catalyst counter threshold (φ) is 3. The manufacturer may determine the catalyst counter threshold (φ) may by testing the reductant delivery system 102 and optimizing the reductant delivery system control strategy 200 so that NOx emissions by the aftertreatment system 100 are maintained at a desirable level and such that usage of the reductant delivery system 102 is maintained at a desirable level.
The reductant delivery system control strategy 200 continues in block 1012 with determining, by the reductant delivery system controller 124, if the catalyst counter (K) is less than the catalyst counter threshold (φ). Block 1012 may be represented by the following equations, only one of which can be true at any given time:
If in block 1012, the catalyst counter (K) is not less than catalyst counter threshold (φ) (e.g., if Equation (72) is true), the reductant delivery system control strategy 200 continues in block 1014 with ceasing, by the reductant delivery system controller 124, any correction that is being implemented by the reductant delivery system controller 124 (e.g., through block 906 in the current universal counter (Ω) or a previous universal counter (Ω). The reductant delivery system control strategy 200 then continues in block 1016 with indicating, by the reductant delivery system controller 124, that the SCR catalyst 112 is failed. In some embodiments, the reductant delivery system controller 124 indicates this failure by causing, by the reductant delivery system controller 124, the display device 134 to display an indication that the SCR catalyst 112 is failed (e.g., a message stating “CATALYST FAILED,” a message stating “SERVICE CATALYST,” etc.). In these embodiments, this indication causes the display device 134 to change from the static state to the alarm state.
The reductant delivery system control strategy 200 continues in block 1018 with setting, by the reductant delivery system controller 124, the global counter (G) to zero. The reductant delivery system control strategy 200 continues in block 1020 with increasing, by the reductant delivery system controller 124, the universal counter (Ω) by 1. The reductant delivery system control strategy 200 then continues in block 204.
It is understood that additional operations, similar to block 1006, may be included in the reductant delivery system control strategy 200, such that a target number of previous absolute bias indexes are compared to the current absolute bias index (⊖Ω) to determine if the catalyst counter (K) is to be increased by one. Additionally or alternatively, averages or other products, summations, of the previous absolute bias indexes may be utilized in block 1004, block 1006, and/or in any similar operations.
If in block 902, the negative incremental counter (β) is less than negative incremental counter threshold (σ) (e.g., if Equation (60) is true), the reductant delivery system control strategy 200 continues with block 1000.
If in block 916, the positive incremental counter (a) is less than positive incremental counter threshold (γ) (e.g., if Equation (64) is true), the reductant delivery system control strategy 200 continues with block 1000.
If in block 1012, the catalyst counter (K) is less than the catalyst counter threshold (φ) (e.g., if Equation (71) is true), then the reductant delivery system control strategy 200 continues with block 1018.
If in block 1006, the absolute bias index (⊖Ω) is less than the next previous absolute bias index (⊖Ω-2) (e.g., if Equation (69) is true), then the reductant delivery system control strategy 200 continues with block 1018.
If in block 1004, the absolute bias index (⊖Ω) is less than the previous absolute bias index (⊖Ω-1) (e.g., if Equation (67) is true), then the reductant delivery system control strategy 200 continues with block 1018.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed but rather as descriptions of features specific to particular implementations. Certain features described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
As utilized herein, the terms “substantially,” generally,” and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the invention as recited in the appended claims.
The terms “coupled” and the like, as used herein, mean the joining of two components directly or indirectly to one another. Such joining may be stationary (e.g., permanent) or moveable (e.g., removable or releasable). Such joining may be achieved with the two components or the two components and any additional intermediate components being integrally formed as a single unitary body with one another, with the two components, or with the two components and any additional intermediate components being attached to one another.
The terms “fluidly coupled to,” “fluidly configured to communicate with,” and the like, as used herein, mean the two components or objects have a pathway formed between the two components or objects in which a fluid, such as air, liquid reductant, gaseous reductant, aqueous reductant, gaseous ammonia, etc., may flow, either with or without intervening components or objects. Examples of fluid couplings or configurations for enabling fluid communication may include piping, channels, or any other suitable components for enabling the flow of a fluid from one component or object to another.
It is important to note that the construction and arrangement of the system shown in the various example implementations is illustrative only and not restrictive in character. All changes and modifications that come within the spirit and/or scope of the described implementations are desired to be protected. It should be understood that some features may not be necessary, and implementations lacking the various features may be contemplated as within the scope of the application, the scope being defined by the claims that follow. When the language “a portion” is used, the item can include a portion and/or the entire item unless specifically stated to the contrary.
This application claims the benefit of U.S. Provisional Patent Application No. 62/795,263, filed Jan. 22, 2019, the entire disclosure of which is incorporated herein by reference.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2020/013033 | 1/10/2020 | WO | 00 |
Number | Date | Country | |
---|---|---|---|
62795263 | Jan 2019 | US |