System and method for virtual reductant mass sensor

The virtual urea quality sensor determines the urea concentration based on the model, which solves the problem of inaccurate measurement of physical sensors under complex conditions, and improves the accuracy of urea concentration measurement and emission reduction effect.

CN118934193APending Publication Date: 2024-11-12CUMMINS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310520170.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-09
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, when measuring the concentration of urea reducing agent, physical urea mass sensors are sensitive to bubbles, resulting in inaccurate measurements during movement or refilling, affecting the effect of reducing NOx emissions.

Method used

A virtual urea mass sensor is used to determine the urea concentration based on the reducing agent characteristics, NOx conversion rate and ammonia amount through the model, reducing dependence on physical sensors and improving measurement accuracy.

Benefits of technology

Improves the accuracy of urea concentration measurement under complex operating conditions, reduces system complexity and potential failures, and enhances the effect of emission reduction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118934193A_ABST
    Figure CN118934193A_ABST
Patent Text Reader

Abstract

The invention relates to a system and method for a virtual reductant mass sensor. Systems and methods for a virtual urea mass sensor (UQS) are provided. A computing system includes at least one processing circuit including one or more memory devices coupled to one or more processors. The at least one processing circuit is configured to: receive an indication of a fluid tank refill event; receiving, after receiving the indication of the fluid tank refill event, an indication of a conversion value of a catalyst of the aftertreatment system; receiving an indication of a reductant characteristic of the reductant; determining an amount of reductant based on the reductant characteristic; receiving a value with respect to the amount of ammonia relative to the NOx value; determining a reductant value based on the conversion value and a value with respect to the amount of ammonia relative to the NOx value; and outputting, for display, an indication of the reductant value.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to reductant diagnostics, such as concentration measurements. More specifically, the present disclosure relates to virtual reductant (eg, urea) quality sensors.

[0002] background

[0003] The exhaust aftertreatment system may include various catalysts (e.g., selective catalytic reduction systems, diesel oxidation catalysts, etc.), reductant dosing systems that introduce reductants (e.g., urea, diesel exhaust fluid (DEF), ammonia solution, etc.) to reduce nitrogen oxide (NOx) emissions from the system, and other components or systems. The reductant dosing system includes a reductant storage device that is configured to store reductants for dosing into the exhaust aftertreatment system. With emission regulations expected to become more stringent in the coming years, it is desirable to mitigate emissions of certain exhaust gas components effectively and over a longer period of time. Therefore, effective reductants are important for reducing undesirable emissions.

[0004] Overview

[0005] One embodiment is directed to a system. The system includes at least one processing circuit, the at least one processing circuit including one or more memory devices coupled to one or more processors, the one or more memory devices configured to store instructions that, when executed by the one or more processors, cause the at least one processing circuit to: receive an indication of a fluid tank refill event; after receiving the indication of the fluid tank refill event, receive an indication of a conversion value of a catalyst of an aftertreatment system; receive an indication of a reductant characteristic of a reductant stored in the fluid tank; determine an amount of ammonia based on the reductant characteristic; receive a value regarding the amount of ammonia relative to a NOx value; determine a reductant value based on the conversion value and the value regarding the amount of ammonia relative to the NOx value; and in response to the determination of the reductant value, output an indication of the reductant value for display.

[0006] Another embodiment relates to a method. The method includes receiving, by a processing circuit including one or more memory devices coupled to one or more processors, an indication of a fluid tank refill event. After receiving the indication of the fluid tank refill event, the method includes receiving, by the processing circuit, an indication of a conversion value of a catalyst of an aftertreatment system. The method includes receiving, by the processing circuit, an indication of a reductant characteristic of a reductant, the reductant being stored in a fluid tank. The method includes determining, by the processing circuit, an amount of ammonia based on the reductant characteristic. The method includes receiving, by the processing circuit, a value regarding an amount of ammonia relative to a NOx value. The method includes determining, by the processing circuit, a reductant value based on the conversion value and the value regarding an amount of ammonia relative to a NOx value. The method includes outputting, by the processing circuit, an indication of the reductant value for display in response to the determination of the reductant value.

[0007] Another embodiment relates to a processing circuit. The processing circuit includes one or more processors; and one or more memory devices coupled to the one or more processors, the one or more memory devices storing instructions, when executed by the one or more processors, the instructions cause the one or more processors to: receive an indication of a fluid tank refill event; after receiving the indication of the fluid tank refill event, receive an indication of a conversion value of a catalyst of an aftertreatment system; receive an indication of a reductant characteristic of a reductant, the reductant stored in the fluid tank; determine an amount of ammonia based on the reductant characteristic; receive a value regarding the amount of ammonia relative to a NOx value; determine a reductant value based on the conversion value and the value regarding the amount of ammonia relative to the NOx value; and in response to the determination of the reductant value, output an indication of the reductant value for display.

[0008] When in conjunction with the accompanying drawings, from the detailed description below, the organization and mode of these and other features and their operation will become apparent. Many specific details are provided to convey a thorough understanding of the embodiments of the disclosed subject matter. In one or more embodiments and / or implementations, the described features of the disclosed subject matter can be combined in any suitable manner. In this regard, one or more features of an aspect of the present invention can be combined with one or more features of different aspects of the present invention. In addition, it can be recognized that additional features that may not be present in all embodiments or implementations can be realized in certain embodiments and / or implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a schematic diagram of an engine-exhaust aftertreatment system coupled to a controller according to an example embodiment.

[0011] Figure 2 is according to an example embodiment and Figure 1 Schematic diagram of the controller used in conjunction with the system.

[0012] Figure 3A-3B According to an example embodiment, Figure 1-Figure 2 A block diagram of the process of implementing a virtual reductant sensor in a controller.

[0013] Figure 4 is a method for using Figure 1-Figure 3B A flow chart of a method for a controller to perform a virtual reductant sensor.

[0014] Figure 5 is a method for using Figure 1-Figure 3B A flow chart of a method for a controller to determine a reductant concentration via a virtual reductant sensor.

[0015] Detailed Description

[0016] What follows is a more detailed description of various concepts and implementations related to methods, devices, and systems for virtual reductant quality sensors. The various concepts introduced above and discussed in more detail below can be implemented in any number of ways, as the concepts described are not limited to any particular implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes.

[0017] Referring generally to the accompanying drawings, various embodiments disclosed herein relate to systems, devices, and methods for determining and / or deploying a virtual reductant sensor that can be used to diagnose the quality of a reductant in a system. As described herein, the system can deploy or execute a virtual reductant sensor to determine (e.g., measure or estimate) the reductant concentration instead of using a physical urea quality sensor (UQS). For example, in some systems, a physical urea quality sensor can be installed in a tank (e.g., a reductant storage device or a fluid tank) that stores the reductant. Certain types of physical UQS installed in these systems can use ultrasonic technology (e.g., an ultrasonic mass piezoelectric sensor) to measure the reductant concentration in the reductant storage device. However, bubbles may form in the reductant storage device under various operating conditions, including when refilling the reductant storage device, during movement (e.g., acceleration or deceleration), and / or during other events involving damage / interference to the reductant storage device. Because the physical UQS may be sensitive to bubbles, the physical UQS may output an inaccurate measurement of the reductant concentration during these operating conditions (e.g., due to changes in the acoustic impedance of the ultrasonic sensor). In such cases, it may be difficult to generate or obtain accurate measurements of reductant concentration during these scenarios. This may result in inaccurate dosing, adversely affecting desired emissions reductions (eg, NOx reductions).

[0018] The systems and methods of the technical solutions described and explained herein provide a virtual reductant sensor configured to determine one or more values ​​of a reductant used in a system, such as a measurement of a reductant concentration. The virtual reductant sensor described herein can replace a physical UQS (e.g., a physical UQS is not installed in the system), thereby reducing the complexity of the system and potentially reducing undesirable failures that may occur based on physical sensor degradation and / or errors.

[0019] A system may include an aftertreatment system coupled to an internal combustion engine. The system may include at least one exhaust gas flow sensor, one or more NOx sensors (e.g., sensors at the inlet and outlet of the aftertreatment system) and at least one reductant doser sensor. The system may be configured to generate, train and execute a model (e.g., a virtual reductant sensor) configured to determine a reductant value (e.g., a reductant concentration value) based at least on reductant characteristics (e.g., reductant dosing characteristics, such as a dosing flow rate or flow rate of the reductant, a temperature of the reductant, a pressure of the reductant at certain locations of the aftertreatment system 22, etc., for determining a value regarding the amount of ammonia relative to a NOx value), a reductant reaction value with NOx (e.g., a NOx conversion rate), an ammonia storage value and / or an ammonia slip value.

[0020] In some implementations, the reductant characteristics may be based on characteristics of the system 10. For example, an increase in the amount of NOx (e.g., the amount of NOx produced by the engine 21), such as measured by the NOx sensor 12 or determined based on operating characteristics of the engine 21 (e.g., engine speed, fuel injection rate, etc.), may result in an increase in the reductant dosing rate (e.g., controlled by the dosing circuit 106). Conversely, a decrease in the amount of NOx may result in a decrease in the reductant dosing rate.

[0021] As discussed herein, the systems and methods described herein enable training and execution of models under or during predetermined conditions to minimize changes in operating conditions. For example, the systems and methods described herein can train or execute models using a moving power window before or after a tank refill event, after a regeneration event, after a calibration is performed on a NOx sensor, etc., thereby improving / increasing the accuracy, consistency, and robustness of the model output (or the output of a virtual reductant sensor). Subsequently and beneficially, the systems and methods described herein can help improve the diagnostic capabilities of the system (e.g., reductant concentration).

[0022] The aftertreatment system can be constructed or configured to reduce byproducts of the exhaust gas (e.g., CO2, NOx, soot, etc.) and include, for example, a selective catalytic reduction (SCR) system that utilizes a two-step process to reduce harmful NOx emissions present in the exhaust gas and an oxidation catalyst that is used to filter or oxidize hydrocarbons, carbon monoxide, or unburned fuel and oil. Referring first to the SCR, a doser injects a reductant into the exhaust gas stream. The reductant can be urea, diesel exhaust fluid (DEF), Urea water solution (UWS), aqueous urea solution (e.g., AUS 32, etc.), or another similar fluid that chemically combines with particles in the exhaust gas. The reductant may decompose into ammonia (NH3) after injection. The mixture then passes through the SCR catalyst, which, when at a certain temperature, causes a reaction in the mixture that converts harmful NOx particles into pure nitrogen and water. In operation, undecomposed reductant and unreacted ammonia may be stored in the catalyst (e.g., SCR catalyst) to chemically react with exhaust products (e.g., NOx particles, etc.). Ammonia that passes through the aftertreatment system and is discharged into the environment is called "ammonia slip."

[0023] More specifically refer to Figure 1 As shown, the system 10 includes an internal combustion engine 21, an exhaust gas aftertreatment system 22 connected to the engine 21 for receiving exhaust gas, and an operator input / output (I / O) device 120 coupled to the controller 100. In the example shown, the system 10 is embodied in a vehicle. The vehicle can be a road or off-road vehicle, including but not limited to a long-distance truck, a mid-range truck (e.g., a pickup truck), a car, a ship, a tank, an airplane, a locomotive, a mining equipment, and any other type of vehicle. The vehicle may include a transmission, a fuel system, one or more additional vehicle subsystems, etc. In this regard, the vehicle may include more, less, and / or different components / systems than shown, so that the principles, methods, systems, devices, processes, etc. of the present disclosure are intended to be applicable to other vehicle configurations. It should also be understood that the principles of the present disclosure should not be interpreted as being limited to vehicles; rather, the present disclosure is also applicable to several fixed equipment such as generators or generator sets. In some embodiments, the vehicle may be another type of vehicle, such as a hybrid vehicle, a fuel cell vehicle, etc., comprising one or more electric motors.

[0024] In this embodiment, the engine is coupled to an exhaust aftertreatment system 22. The exhaust aftertreatment system 22 includes a diesel particulate filter (DPF) 40, a diesel oxidation catalyst (DOC) 30, a selective catalytic reduction (SCR) system 52 having an SCR catalyst 50, and an ammonia oxidation (AMOx) catalyst 60. The SCR system 52 is shown to include a reductant delivery system having a reductant fluid source 54 that supplies reductant to a doser 56 via a reductant line 58.

[0025] In the direction of exhaust flow, as shown by the directional arrow 29, the exhaust gas flows from the engine 21 into the inlet pipe 24 of the exhaust aftertreatment system 22. The exhaust gas flows from the inlet pipe 24 into the oxidation catalyst 30 and leaves the oxidation catalyst into the first section 28A of the exhaust pipe. The exhaust gas flows from the first section 28A of the exhaust pipe into the particulate filter 40 and leaves the particulate filter into the second section 28B of the exhaust pipe. The exhaust gas flows from the second section 28B of the exhaust pipe into the SCR catalyst 50 and leaves the SCR catalyst into the third section 28C of the exhaust pipe. When the exhaust gas flows through the second section 28B of the exhaust pipe, the reducing agent is periodically dosed to it by the reducing agent dosing device 56. Therefore, the second section 28B of the exhaust pipe acts as a decomposition chamber or pipe to promote the decomposition of the reducing agent into ammonia. The exhaust gas flows from the third section 28C of the exhaust pipe into the AMOx catalyst 60 and leaves the AMOx catalyst into the outlet pipe 26 before the exhaust gas is discharged from the system 22. Based on the above, in the illustrated embodiment, the oxidation catalyst 30 is located upstream of the particulate filter 40 and the SCR catalyst 50, and the SCR catalyst 50 is located downstream of the particulate filter 40 and upstream of the AMOx catalyst 60. However, in alternative embodiments, other arrangements of the components of the exhaust aftertreatment system 22 are possible.

[0026] The oxidation catalyst 30 can be configured to have any number of different types of flow-through designs. The oxidation catalyst 30 can be configured to oxidize at least some of the particulate matter in the exhaust (e.g., the soluble organic portion of the soot) and reduce unburned hydrocarbons and CO in the exhaust to compounds that are less harmful to the environment. For example, the oxidation catalyst 30 can be configured to reduce the concentration of hydrocarbons and CO in the exhaust to meet necessary emission standards for those components in the exhaust. An indirect result of the oxidation capacity of the oxidation catalyst 30 is the ability of the oxidation catalyst to oxidize NO to NO2. In this way, the level of NO2 leaving the oxidation catalyst 30 is equal to the NO2 in the exhaust generated by the engine 21, in addition to the NO2 converted from NO by the oxidation catalyst.

[0027] In addition to treating hydrocarbon and CO concentrations in the exhaust gas, the oxidation catalyst 30 can also be used for controlled regeneration of the particulate filter 40, the SCR catalyst 50, and the AMOx catalyst 60. This can be achieved by injecting or dosing unburned HC into the exhaust gas upstream of the oxidation catalyst 30. Upon contact with the oxidation catalyst 30, the unburned HC undergoes an exothermic oxidation reaction that results in an increase in the temperature of the exhaust gas leaving the oxidation catalyst 30 and subsequently entering the particulate filter 40, the SCR catalyst 50, and / or the AMOx catalyst 60. The amount of unburned HC added to the exhaust gas is selected to achieve a desired temperature increase or a target controlled regeneration temperature.

[0028] The particulate filter 40 can be any of a variety of flow-through designs and is configured to reduce the concentration of particulate matter (e.g., soot and ash) in the exhaust gas to meet the necessary emission standards. The particulate filter 40 captures particulate matter and other components and can therefore be periodically regenerated to burn off the captured components. In addition, the particulate filter 40 can be configured to oxidize NO to form NO2 independently of the oxidation catalyst 30.

[0029] As described above, the SCR system 52 includes a reductant delivery system having a reductant (e.g., DEF) source 54, a pump (not shown), and a delivery mechanism or dosing device 56. The reductant source 54 can be a container or tank capable of holding a reductant such as, for example, ammonia (NH3), DEF (e.g., urea), diesel, etc. The reductant source 54 is connected to a pump for reductant supply, and the pump is configured to pump the reductant from the reductant source 54 to the delivery mechanism 56 via a reductant delivery line 58. The delivery mechanism 56 is located upstream of the SCR catalyst 50. The delivery mechanism 56 can be selectively controlled to inject the reductant directly into the exhaust gas flow before the exhaust gas flow enters the SCR catalyst 50. As described herein, the controller 100 is configured to control the timing and amount of the reductant delivered to the exhaust gas. The reductant can decompose to generate ammonia. As briefly described above, ammonia reacts with NOx in the presence of the SCR catalyst 50 to reduce NOx to less harmful emissions, such as N2 and H2O. The NOx in the exhaust gas flow includes NO2 and NO. In the presence of NH3, both NO2 and NO are reduced to N2 and H2O through various chemical reactions driven by the catalytic element of the SCR catalyst.

[0030] The SCR catalyst 50 can be any of a variety of catalysts known in the art. For example, in some implementations, the SCR catalyst 50 is a vanadium-based catalyst, while in other implementations, the SCR catalyst is a zeolite-based catalyst, such as a copper zeolite or an iron zeolite catalyst. In a representative embodiment, the reductant is aqueous urea and the SCR catalyst 50 is a zeolite-based catalyst. In other embodiments, the reductant includes a first reductant and a second reductant, wherein the first reductant is urea and the second reductant is ammonia.

[0031] The AMOx catalyst 60 may be any of a variety of flow-through catalysts configured to react with ammonia to primarily produce nitrogen. As briefly described above, the AMOx catalyst 60 is configured to remove ammonia that has escaped or left the SCR catalyst 50 without reacting with NOx in the exhaust gas. In some cases, the aftertreatment system 22 may be operated with or without the AMOx catalyst. In addition, although the AMOx catalyst 60 is Figure 150 is shown as a separate unit from the SCR system 52, but in some implementations, the AMOx catalyst can be integrated with the SCR catalyst (e.g., the AMOx catalyst and the SCR catalyst can be located in the same housing). In some embodiments, the SCR catalyst and the AMOx catalyst are positioned consecutively, with the SCR catalyst preceding the AMOx catalyst. As described herein, the SCR catalyst 50 and the AMOx catalyst 60 form an SCR and AMOx system. Therefore, the determined health or degradation is related to these catalysts.

[0032] Various sensors, such as temperature sensor 16, NOx sensor 12, and flow sensor 18, can be strategically arranged throughout the exhaust aftertreatment system 22 (or other parts of the system 10), and can communicate with the controller 100 and be configured to monitor the operating conditions of the system 10. In some cases, the flow sensor 18 is located upstream of the engine 21. It should be understood that one or more pressure and various other sensors (oxygen sensors, exhaust gas composition sensors, NH3 sensors, etc.) can also be included in the system and set at various locations. In addition, the precise placement of the sensors is highly configurable, so that the depicted configuration is not meant to be limiting.

[0033] Although the exhaust aftertreatment system 22 shown includes one of the oxidation catalyst 30, the particulate filter 40, the SCR catalyst 50, and the AMOx catalyst 60 positioned at a specific position relative to each other along the exhaust flow path, in other embodiments, the exhaust aftertreatment system may include more than one of any of a variety of catalysts positioned at any position relative to each other along the exhaust flow path. In addition, although the oxidation catalyst 30 and the AMOx catalyst 60 are non-selective catalysts, in some embodiments, the oxidation catalyst and the AMOx catalyst may be selective catalysts.

[0034] The operator I / O device 120 is communicatively coupled to the controller 100 so that information can be exchanged between the controller 100 and the I / O device 120. The information exchanged between the controller 100 and the I / O device 120 may relate to Figure 1 The operator I / O device 120 enables an operator of the vehicle (or an occupant of the vehicle) to communicate with the controller 100 and other components of the vehicle, such as at least Figure 1 For example, the operator input / output device 120 may include an interactive display, a touch screen device, one or more buttons and switches, a voice command receiver, etc. Additional input, output, and / or input / output devices may be included, such as a transmission shifter, an accelerator pedal, a brake pedal, a steering wheel, etc.

[0035] The controller 100 is configured to at least partially control the operation of the system 10 and associated subsystems, such as the internal combustion engine 21, the fuel injectors, and the exhaust aftertreatment system 22 (e.g., the doser 56, etc.). Communication between and among components can be via any number of wired or wireless connections. For example, a wired connection can include a serial cable, a fiber optic cable, a CAT 5 cable, or any other form of wired connection. In contrast, a wireless connection can include the Internet, Wi-Fi, cellular, radio, etc. In one embodiment, a controller area network ("CAN") bus provides for the exchange of signals, information, and / or data. The CAN bus includes any number of wired and wireless connections. Because the controller 100 is communicatively coupled to at least Figure 1 systems and components, so the controller 100 is constructed from at least Figure 1 One or more components shown receive data. For example, the data may include CO data, NOx data, flow data, temperature data, or other data captured by sensors 12, 16, 18, and vehicle operation data (e.g., engine speed, vehicle speed, engine temperature, etc.) received via one or more sensors. As another example, the data may include input from an operator input / output device 120. In addition, the data may include fluid flow data (e.g., rate, amount, temperature, pressure, etc.), which may be measured or determined by an oxygen sensor (not shown) or other gas flow sensor.

[0036] Now refer to Figure 2, depicts an example structure of a controller 100 according to an example embodiment. The controller 100 is shown to include: at least one processing circuit 101, the processing circuit 101 includes at least one processor 102 and at least one memory 103; and various circuits, the circuits include at least an engine circuit 105, a dosing circuit 106, an enabling circuit 107, a stop circuit 108, and a reductant sensor circuit 109. The processor 102 can be implemented as one or more processors, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a group of processing components, or other suitable electronic processing components. At least one memory 103 (e.g., RAM, ROM, flash memory, hard disk storage device, etc.) can store data and / or computer code to facilitate various processes described herein. The memory 103 may be communicatively connected to the processor 102 and one or more circuits (e.g., the engine circuit 105, the dosing circuit 106, the enabling circuit 107, the abort circuit 108, or the reductant sensor circuit 109), and is configured to provide computer code or instructions to the processor 102 for performing certain processes described herein with respect to the controller 100. In addition, the memory 103 may be or include tangible, non-transitory volatile memory or non-volatile memory. Thus, the memory 103 may include a database component, an object code component, a script component, or any other type of information structure for supporting the various activities and information structures described herein.

[0037] The controller 100 is configured to receive input (e.g., signals, information, data, etc.) from the system 10 components / systems and / or operator I / O devices 120. Thus, the controller 100 is configured to at least partially control the components / systems of the system 10 and the associated vehicle. Figure 2 The components may be embodied in a vehicle, and the controller 100 may be constructed as one or more electronic control units (ECUs). The controller 100 may be separated from or included in at least one of a transmission control unit, an exhaust aftertreatment control unit, a powertrain control module, an engine control module, and the like.

[0038] In one configuration, one or more circuits (e.g., engine circuit 105, dosing circuit 106, enabling circuit 107, stop circuit 108, or reductant sensor circuit 109) can be implemented as a machine or computer readable medium that stores instructions that can be executed by a processor (e.g., processor 102) and is stored in a memory device (e.g., memory 103). As described herein and in other uses, machine-readable media helps to perform certain operations to achieve the reception and transmission of data. For example, a machine-readable medium can provide instructions (e.g., commands, etc.) to, for example, obtain data. In this regard, a machine-readable medium can include programmable logic that defines the frequency of data acquisition (or data transmission). A computer-readable medium can include code that can be written in any programming language, including but not limited to Java, etc., and any conventional process programming language, such as "C" programming language or similar programming language. Computer-readable program code can be executed on one processor or multiple remote processors. In the latter case, the remote processors can be interconnected via any type of network (e.g., CAN bus, etc.).

[0039] In another configuration, one or more circuits are implemented as hardware units, such as electronic control units. Therefore, one or more circuits can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-chip (SOC) circuits, microcontrollers, etc.), telecommunications circuits, hybrid circuits, and any other type of "circuit". For example, the circuits described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, etc. One or more circuits may also include programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. One or more circuits may include one or more memory devices for storing instructions that can be executed by processors of various circuits (e.g., engine circuit 105, quantitative distribution circuit 106, enabling circuit 107, stop circuit 108, or reductant sensor circuit 109). One or more memory devices and processors may have the same definitions provided herein with respect to memory 103 and processor 102. In some hardware unit configurations, one or more circuits may be geographically dispersed at various locations in a system (e.g., a vehicle). Alternatively and as shown, one or more circuits may be embodied in or within a single unit / housing, which is shown as controller 100.

[0040] In various arrangements, the controller 100 includes a communication interface 104. The communication interface 104 may include any combination of wired and / or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wired terminals) for data communication with various systems, devices, or networks that are configured to enable communication within the vehicle (e.g., communication between and among components of the vehicle) and in some embodiments, communication outside the vehicle (e.g., direct communication with at least one remote computing system). In this regard, in some embodiments, the communication interface 104 includes a network interface. The network interface is used to establish a connection with other computing devices through a network. The network interface includes program logic that facilitates the controller 100 to connect to the network. The network interface includes any combination of wireless network transceivers (e.g., cellular modems, Bluetooth transceivers, Wi-Fi transceivers) and / or wired network transceivers (e.g., Ethernet transceivers). For example, the communication interface 104 includes a wireless device such as a cellular transceiver and a machine-readable medium such as a cellular driver, and the machine-readable medium is configured to facilitate connection with the network. In some arrangements, the network interface includes hardware and machine-readable media sufficient to support communications on multiple data communication channels. In addition, in some arrangements, the network interface includes a cryptographic function to establish a secure or relatively secure communication session, wherein the data transmitted through the session is encrypted. For example, with respect to communications outside the vehicle / system, the communication interface 104 may include an Ethernet card and port for sending and receiving data via an Ethernet-based communication network, and / or a Wi-Fi transceiver for communicating via a wireless communication network. The communication interface 104 may be configured to communicate via a local area network and / or a wide area network (e.g., the Internet), and various communication protocols (e.g., IP, LON, Bluetooth, ZigBee and radio, cellular, near field communication) may be used. In addition, the communication interface 104 may work together or in series with a telematics unit (if included) to communicate with other vehicles and / or remote computing systems in the queue. In an example embodiment, the communication interface 104 is configured to provide vehicle information (e.g., operating parameters and / or operating data) to a remote computing system, a third-party computing system, and / or other vehicles in the queue. In other embodiments, this network connection / communication aspect may be excluded.

[0041] In the example shown, the controller 100 includes a processing circuit 101, which can be constructed or configured to perform or implement instructions, commands and / or control processes described herein about the engine circuit 105, the quantitative distribution circuit 106, the enabling circuit 107, the suspension circuit 108 and the reductant sensor circuit 109. The depicted configuration represents the engine circuit 105, the quantitative distribution circuit 106, the enabling circuit 107, the suspension circuit 108 and the reductant sensor circuit 109 as instructions in a machine or computer readable medium. In some embodiments, the instructions can be stored by a memory device. However, as described above, the illustration is not meant to be limiting, because the present disclosure contemplates other embodiments, wherein the engine circuit 105, the quantitative distribution circuit 106, the enabling circuit 107, the suspension circuit 108 and the reductant sensor circuit 109 or at least one of these circuits is configured as a hardware unit. All such combinations and variations are intended to fall within the scope of the present disclosure.

[0042] The engine circuit 105 is configured to receive information from a user (e.g., via an operator input / output device 120, an accelerator pedal, etc.) and provide instructions to the engine 21 or otherwise control the engine 21. For example, the engine circuit 105 is configured to control the engine itself and components associated with the engine, including at least an intake valve for controlling the amount of intake air, an exhaust valve for releasing exhaust gas through a conduit (e.g., conduits 24, 28A-C, 26, etc.), or other components of the engine 21. In addition, the engine circuit 105 can control the torque and / or speed from the engine 21. The engine circuit 105 is configured to receive information associated with the engine 21, such as fuel quantity, engine temperature, fuel flow rate (e.g., air-fuel mixture flow rate), etc.

[0043] The dosing circuit 106 is configured to control the doser 56. In this manner, the dosing circuit 106 is configured to provide dosing commands to the doser 56 to control and manage (e.g., adjust) the amount and / or timing of the dosing of the reductant from the doser 56. The dosing circuit 106 may also communicate with one or more other circuits, such as at least one of the enabling circuit 107, the aborting circuit 108, or the reductant sensor circuit 109. For example, the dosing circuit 106 may receive information about the amount of fuel injected into the engine 21 at different times (e.g., during different drive cycle times) from at least one of the processing circuits 101, or receive information about the amount, concentration, or emissions of NOx measured by one or more NOx sensors 12 from one or more sensors (e.g., NOx sensors 12). Based on the information from the one or more circuits or sensors, the dosing circuit 106 may adjust the dosing rate or amount accordingly.

[0044] In some arrangements, the dosing circuit 106 commands the doser 56 to control the dosing of the reductant. The dosing circuit 106 may reduce or increase the dosing of the reductant in proportion to or according to the measurement of the NOx sensor 12 so as to reduce NOx emissions from the system 10. For example, the measurement may come from at least one NOx sensor 12 upstream of the SCR catalyst 50 and / or at least one NOx sensor 12 downstream of the SCR catalyst 50. The dosing circuit 106 may determine to increase the dosing amount based on an increase in NOx upstream of the SCR catalyst 50 or an increase in NOx downstream of the SCR catalyst 50. The dosing circuit 106 may determine to reduce the dosing amount based on a decrease in NOx upstream or downstream of the SCR catalyst 50. For example, the dosing circuit 106 may command the doser 56 to adjust the dosing of the reductant according to the determination.

[0045] In various configurations discussed herein, the controller 100 or one or more components / circuits of the controller 100 (e.g., the enable circuit 107, the disable circuit 108, or the reductant sensor circuit 109) is configured to determine the reductant mass (which may be based on or approximated by the reductant / urea concentration) in the absence of a physical UQS. The term "reductant mass" may correspond to the concentration of the reductant (e.g., the concentration of the reductant stored in a reductant storage device, such as the concentration of the reductant in the reductant tank or the reductant fluid source 54), such as in units of mg / L or parts per million (ppm). As described herein, the concentration of the reductant is determined based on a plurality of parameters (or factors) related to the operation of the system 10 including the aftertreatment system 22, such as parameters related to the dosing of the reductant and how the reductant is used throughout the aftertreatment system 22.

[0046] The dosing flow of the reductant corresponds to the dosing rate of the reductant. The dosing rate of the reductant can be configured and implemented by the dosing circuit 106 via the dosing device. For example, the dosing rate can be based on the NOx measurement performed by the NOx sensor upstream of the SCR catalyst 50 (e.g., at the outlet of the engine 21). For example, the dosing circuit 106 can send a command including the dosing rate of the reductant to control the dosing device 56 to dosing the reductant to the post-treatment system 22 at the dosing rate of the command. As part of determining the reductant mass value (e.g., reductant concentration), the dosing circuit 106 can provide an indication of the dosing rate of the reductant to one or more other circuits (e.g., enabling circuit 107, terminating circuit 108, or reductant sensor circuit 109). In some cases, the system 10 may include a sensor (e.g., a fluid flow rate sensor, such as a flow sensor 18) configured to measure the dosing rate of the reductant in the post-treatment system 22. In this case, the sensor may measure, for example, at least one of the frequency, duration, volume, etc. of the reductant dosed in the aftertreatment system 22. In some implementations, the amount of reductant dosed into the aftertreatment system 22 according to the dosing rate may be determined based in part on the exhaust flow rate measured by the flow sensor 18 at one or more locations within the aftertreatment system 22 (e.g., downstream of the engine 21). In some cases, the controller 100 may determine the exhaust flow rate based on at least one of a pressure difference between two pressure sensors within the aftertreatment system 22, a speed or displacement of the engine 21, etc.

[0047] The reaction of the reductant with NOx may correspond to a conversion value of a catalyst (e.g., SCR catalyst 50) of the aftertreatment system 22. The conversion value may correspond to or be referred to as a conversion efficiency or DeNOx efficiency. The conversion value may be a ratio, a percentage, or other value indicating or relating to the amount of NOx reduction via the catalyst of the aftertreatment system 22. For simplicity and for the purpose of providing examples herein, the conversion value may be a conversion efficiency (e.g., a conversion efficiency value) and the catalyst may be an SCR catalyst 50, although other types of conversion values ​​and catalysts of the aftertreatment system 22 may be additionally or alternatively described herein. In some implementations, the conversion value may be calculated using the following formula: Wherein downstream NOx refers to NOx measured downstream of the catalyst, and upstream NOx refers to NOx exhausted by the engine (e.g., NOx upstream of the catalyst). These NOx values ​​can be measured using the NOx sensor 12 (or virtual NOx sensor). The conversion efficiency can be used to monitor the efficiency of the SCR catalyst 50 in converting NOx into less harmful compounds (e.g., water). Therefore, the higher the conversion value or efficiency, the more effective the catalyst is at conversion.

[0048] One or more components of the controller 100 may determine the conversion efficiency based on NOx measurements, such as NOx measurements upstream and downstream of the SCR catalyst 50 (and / or one or more components or systems, such as upstream and downstream of the entire aftertreatment system 22). As discussed herein, in order to minimize or control the noise associated with the input parameters used to calculate (e.g., determine) the reductant concentration, one or more components of the controller 100 may verify or calibrate one or more NOx sensors 12 used to calculate the conversion efficiency. The determination of the reductant concentration may be affected by noise (e.g., noise factors) of the system 10. Noise includes, but is not limited to, NH3 storage, NH3 slip (e.g., ammonia slip), conversion efficiency, accuracy of one or more sensors (e.g., NOx sensor 12), or other variables that may not be directly determined or that negatively affect the determination of the reductant concentration. NH3 storage refers to the amount of ammonia stored on the catalyst. NH3 slip corresponds to the amount of unreacted ammonia that leaves the system 10, such as caused by an exhaust gas flow rate above an expected threshold, an excess of reductant entering the aftertreatment system 22, the conversion efficiency of the catalyst, etc.

[0049] In some embodiments, the reductant concentration may correspond to a reductant value, wherein the reductant value may be determined based on a conversion value (e.g., conversion efficiency) and a value (e.g., ANR) about the amount of ammonia relative to the NOx value. In various configurations, the amount of reductant quantitatively distributed to the aftertreatment system 22 is associated with the amount of ammonia introduced into the aftertreatment system 22. For example, when a reductant (e.g., urea) reacts with water through a catalyst, a relevant amount of ammonia and carbon dioxide is formed (e.g., produced) according to the conversion efficiency of the catalyst. The ammonia formed may react with NOx to form nitrogen and water vapor to meet emission regulations. Because the accuracy of the determination of the reductant value is based on the amount of NOx and the amount of ammonia, at least one of the conversion efficiency (e.g., affected by catalyst aging and / or high sulfur fuel), NOx sensor accuracy, NH3 storage, etc. is a noise that affects the determination of the reductant value.

[0050] The ammonia storage value refers to the amount of ammonia stored in a component, particularly the amount of ammonia in the SCR catalyst 50. In some cases, the ammonia storage value may not be directly measured. In this case, because some systems cannot directly (or accurately) determine the ammonia storage value, the ammonia storage value may be a factor that interferes with the calculation of the reductant value. One or more components of the controller 100 may perform a reductant concentration calculation and store the result of the reductant concentration calculation under predetermined conditions or standards as described herein, so that the ammonia storage value may not affect the reductant concentration calculation (e.g., minimize or exclude the ammonia storage value from the calculation). In some other cases, the ammonia storage value may be measured using at least one of various techniques, such as using programmed temperature desorption (TPD) to measure the reductant released from the SCR catalyst 50, using infrared (IR) spectroscopy to detect or measure the reductant present in the bed of the SCR catalyst 50, and / or using conductivity measurement to measure the change in conductivity to calculate the ammonia storage level, etc. For simplicity and for the purpose of providing examples herein, the ammonia storage value may not be directly measured, so that the ammonia storage value is considered to be a noise factor to be minimized or excluded under certain operating conditions of the system 10.

[0051] For example, ammonia slip refers to the amount of ammonia released from the aftertreatment system 22 (e.g., SCR catalyst 50) to the outlet line 26 of the system 10. In some cases, a sensor (e.g., an ammonia sensor, an electrochemical sensor, or other type of sensor) located downstream of the component or system, such as a sensor at the outlet of the ambient emissions or at the outlet of the SCR catalyst 50, can be used to measure ammonia slip. The controller 100 receives a measurement result from the sensor, which indicates the concentration or amount of unreacted ammonia that is subsequently discharged into the environment with the exhaust gas. In some other cases, ammonia slip may be a factor that affects the determination of the reductant value, taking into account the noise factors to be minimized. In this case, one or more components of the controller 100 can perform the reductant concentration calculation without using ammonia slip. For simplicity and for the purpose of providing an example (e.g., to minimize variability in the calculation), ammonia slip can be excluded from the reductant concentration calculation discussed herein.

[0052] Based on the above, the reducing agent concentration can be determined using the following equations (1) and (2):

[0053] Reductant concentration × quantitative distribution flow = conversion efficiency × reductant storage × reductant escape (1)

[0055] To calculate the reducing agent concentration, the formula can be modified as follows:

[0056]

[0057] y is a constant or predefined value representing a standard reductant concentration (e.g., 32.5%). n can represent a noise factor, for example, a factor that affects the calculation of the reductant concentration, such as ammonia storage, ammonia slip, or sensor variation (e.g., NOx sensor 12 or flow sensor 18). The dosing flow can be referred to as the reductant flow, which can be part of the reductant characteristics. Based on the dosing flow and the NOx value (e.g., the amount of NOx measured by the NOx sensor 12 upstream of the SCR catalyst 50), the controller 100 can provide a value regarding the amount of ammonia relative to the NOx value (e.g., an ammonia to NOx ratio (ANR)).

[0058] By performing calculations (e.g., determining) or storing calculation results under predetermined operating conditions or circumstances of the system 10, for example, after verifying sensor accuracy, regenerating a catalyst, when the dosing rate is operating as expected, or when the operation of one or more components of the system 10 is operating within predefined maximum / minimum limits / amounts, etc., the controller 100 can minimize or mitigate the impact of noise factors on the calculations. Subsequently, as discussed herein, one or more components of the controller 100 can perform reductant concentration calculations in the absence of noise factors during one or more predetermined operating circumstances of the system 10 as discussed herein. Thus, in the absence of noise factors, one or more components of the controller 100 can calculate the reductant concentration using equation (3):

[0059]

[0060] According to equation (3), to achieve the same conversion efficiency, a relatively high value (e.g., ANR) regarding the amount of ammonia relative to the NOx value can indicate a relatively low reductant concentration. Conversely, to achieve the same conversion efficiency, a relatively low value regarding the amount of ammonia relative to the NOx value can indicate a relatively high reductant concentration, such as the concentration of the reductant stored in the reductant source 54. For simplicity and for the purpose of providing examples herein, the value regarding the amount of ammonia relative to the NOx value can correspond to or be referred to as a ratio between the amount of ammonia (e.g., determined based on reductant characteristics or dosing of the reductant) and the NOx value (e.g., based on NOx measurements upstream of the SCR catalyst 50).

[0061] The enabling circuit 107 is configured to identify enabling conditions. As described herein, the enabling conditions may include an indication of a reductant fluid tank refill event (e.g., a fluid tank refill event). A tank refill event refers to when a tank is refilled, such as by an operator or service personnel of the system 10. The tank may correspond to or include a reductant tank or a reductant source 54 storing a reductant. The enabling circuit 107 is configured to use a tank refill event as an indicator of one or more operations of enabling, activating, or starting the reductant sensor circuit 109. A tank refill event may be determined based on a position sensor (e.g., a Hall effect sensor, etc.) indicating that the fluid in the fluid tank increases by more than a predetermined amount or level. When the sensor is triggered, the enabling circuit 107 may determine that a fluid tank refill event has occurred. In another embodiment, the sensor may be included on the lid of the tank (e.g., a magnetic sensor disposed on the tank and the lid). When the transmission stops, the enabling circuit 107 may determine that the lid is removed. In some cases, removing the lid can be used to help determine whether a refill event has occurred or may occur.

[0062] For example, the enabling circuit 107 is configured to output an enabling state according to whether a tank refill event has occurred or may occur. The enabling circuit 107 provides the enabling state as part of the input to the reductant sensor circuit 109. The enabling state includes an "on" / active state (e.g., outputting "1") or an "off" / inactive state (e.g., outputting "0"). After identifying a tank refill event, the enabling circuit 107 may update or maintain the enabling state as active or on, thereby indicating to the reductant sensor circuit 109 that a tank refill event has occurred.

[0063] As described above, the enabling circuit 107 can be configured to identify or otherwise determine that a tank refill event has occurred or may occur based on a change in the level of the reductant stored in the tank. The amount of reductant or the reductant level can be measured by a sensor (sometimes referred to as a tank sensor) coupled to the tank (e.g., the reductant source 54). The enabling circuit 107 receives a measurement result indicating the reductant level from the tank sensor. The measurement result from the tank sensor can indicate the percentage of the stored reductant relative to the maximum capacity of the tank (e.g., from 0% to 100%) or the volume of the reductant stored in the tank (e.g., from 0 to 20 liters, from 0 to 40 liters, etc.). The enabling circuit 107 is configured to monitor changes in the reductant level to identify a tank refill event. For simplicity, the enabling circuit 107 can receive a percentage representing the amount of reductant stored in the tank.

[0064] For example, the enabling circuit 107 may monitor the reductant level at different time intervals. When the reductant level increases by at least a predetermined threshold, such as 30%, 50%, or 70%, the enabling circuit 107 may identify or determine that a tank refill event has occurred. The predetermined threshold may be configured by the service entity or via a configuration received from the operator I / O device 120.

[0065] In some implementations, the enabling circuit 107 may identify a tank refill event based on a change in the level of the reductant in the tank before and after at least one of an engine idling event, a parking event, or an inactive state of the engine 21. An engine idling event refers to a period of time when the engine 21 is idling. A parking event refers to a period of time when the system 10 is not in motion (e.g., the vehicle is parked). For example, the inactive state of the engine 21 may refer to when the engine 21 is not rotating or after stopping the operation of the engine 21 or shutting down the engine 21. For simplicity and for the purpose of providing an example, an engine idling event may be used herein, although other types of events, such as parking events, inactive states of the engine 21, etc. may be used in addition or alternatively.

[0066] The enabling circuit 107 is configured to determine a first reductant level (e.g., a first amount of reductant) prior to an engine idle event. The enabling circuit 107 is configured to determine a second reductant level (e.g., a second amount of reductant) after an engine idle event (e.g., after the engine 21 is turned on, after stopping engine idling, or when the system 10 is in motion). The enabling circuit 107 may determine a difference between the second reductant level and the first reductant level. If the difference is greater than or equal to a threshold value (e.g., 30%, 50%, or 70%), the enabling circuit 107 may identify that a tank refill event has occurred, such as during an engine idle event. Otherwise, the enabling circuit 107 may not identify the occurrence of a tank refill event.

[0067] In some configurations, the enabling circuit 107 is configured to start the identification or determination of the tank refill event when the reductant level is less than (or equal to) a predefined threshold (e.g., a storage threshold). For example, the storage threshold may be predefined as 30% of the total amount of the reductant storage value. In response to identifying that the reductant level drops to equal to or below the storage threshold, the enabling circuit 107 may initiate the determination or identification of the tank refill event. In other cases, if the reductant level is above the storage threshold, the enabling circuit 107 may not perform the tank refill event identification. In some cases, a second storage threshold may be configured to identify the tank refill event. The second storage threshold indicates the minimum reductant level that will be considered as a tank refill (e.g., 70%, 80%, 90%, etc. of the tank). For example, in this case, after the reductant level drops to or below the first storage threshold, when the reductant level increases to or above the second storage threshold, the enabling circuit 107 determines that the tank has been refilled. In some other cases, for example, the enabling circuit 107 receives a flag or indication from the operator I / O device 120 indicating that the tank refill event has occurred.

[0068] In some implementations, the enabling circuit 107 is configured to output an active state in response to an indication (or flag) of a reductant change event. A reductant change event refers to when a reductant is added, changed, or replaced from a tank. A reductant change event may be associated with a change in conversion efficiency (e.g., DeNOx efficiency) determined or calculated based on NOx measurements from one or more NOx sensors 12 located upstream and downstream of the SCR catalyst 50. In some cases, the enabling circuit 107 (or other circuits of the controller 100) may determine the conversion efficiency after calibrating one or more NOx sensors 12, as discussed herein. In some other cases, the enabling circuit 107 may perform calibration using at least one virtual NOx sensor, as discussed herein. The virtual NOx sensor may estimate or calculate the NOx concentration at various locations within the aftertreatment system 22 (or downstream of the engine 21) based on at least one of the engine speed, fuel injection rate, exhaust gas flow, intake manifold pressure, temperature of the aftertreatment system 22, etc.

[0069] The enabling circuit 107 may determine the conversion efficiency based on a ratio or difference between an upstream NOx measurement and a downstream NOx measurement with respect to the SCR catalyst 50. For example, the following formula (eg, equation (4)) may be used to calculate the conversion efficiency:

[0070]

[0071] Although the above formulas or techniques are provided, the enabling circuit 107 (or other circuits of the controller 100 ) may implement other methods or techniques to determine the conversion efficiency.

[0072] The enabling circuit 107 can monitor changes in conversion efficiency, such as changes before and after an engine idling event. In some cases, the enabling circuit 107 can monitor changes in conversion efficiency outside the engine idling time range. The enabling circuit 107 can identify a reductant change event based on a comparison of the difference between a first conversion efficiency of a first time range (e.g., before an engine idling event) and a second conversion efficiency of a second time range (e.g., after an engine idling event) with a predetermined threshold (e.g., a conversion efficiency threshold). For example, the conversion efficiency threshold can be predefined as 10%, 20%, or 30%. If the difference between the first and second conversion efficiencies is greater than or equal to the threshold, the enabling circuit 107 can determine the occurrence of a reductant change event. In other cases, the enabling circuit 107 determines that the reductant has not been changed.

[0073] In some configurations, the enabling circuit 107 activates the enabling state based on a predefined duration after identifying at least one of a tank refill event or a reductant change event. For example, in response to identifying a tank refill event or a reductant change event, the enabling circuit 107 may start a timer (e.g., a countdown timer) with a predefined duration (e.g., 30 hours or 50 hours). At this stage, the enabling circuit 107 may not activate the enabling state. After the timer expires, the enabling circuit 107 may activate the enabling state, thereby outputting a "1" to the reductant sensor circuit 109, for example. Therefore, the enabling circuit 107 may activate or "turn on" the enabling state based on at least one of the identification of a tank refill event, a reductant change event, or a timer duration.

[0074] In some embodiments, the enabling circuit 107 can be configured to deactivate the enabling state (e.g., output "0") in response to a predefined duration (e.g., expiration of another timer) after activating the enabling state. For example, in response to activating the enabling state (e.g., outputting "1"), the enabling circuit 107 can start a timer, such as a countdown timer. When the timer expires after the predefined duration, the enabling circuit 107 can deactivate the enabling state (e.g., output "0"). The enabling circuit 107 can activate the enabling state in response to at least one of identifying a tank refill event based on a change in level or a change in NOx conversion efficiency (or similarly, DeNOx efficiency) and / or not triggering the enabling state after a predetermined duration (e.g., activating 24 hours, 36 hours, etc. after a tank refill event is not identified). For example, depending on the configuration, the enabling circuit 107 can output "0" when the enabling state is "on" and output "1" when the enabling state is "off". In various configurations, at least Figure 3A (eg, enabling circuit 302 ) describes enabling circuit 107 .

[0075] The abort circuit 108 is configured to reset or abort the operation for calculating the reductant concentration. The abort circuit 108 is configured to output an abort state / condition, including an "on" / active state (e.g., "1" or "0" depending on the configuration) or an "off" / inactive state (e.g., "0" or "1" depending on the configuration). In the following, for example, the abort circuit 108 is configured to transmit a signal "1" indicating an active abort state and a signal "0" indicating an inactive abort state. When the abort state is active or triggered, the abort circuit 108 is configured to send an indication to the reductant sensor circuit 109 to stop calculating the reductant concentration. For example, in response to the system 10 (or the aftertreatment system 22) operating outside of at least one predefined or desired operating condition, the abort circuit 108 can set the abort state to active.

[0076] When the suspend state is inactive or disabled, the suspend circuit 108 is configured to send an indication to the reductant sensor circuit 109 to start or continue calculating the reductant concentration. In response to the system 10 (or the aftertreatment system 22) operating within one or more predefined operating conditions, the suspend circuit 108 can set the suspend state to inactive. The operating conditions may include or at least relate to the temperature of the aftertreatment system 22 (e.g., the bed temperature of the SCR catalyst 50) and the reductant flow (e.g., the dosing rate), as well as other configurable operating conditions.

[0077] The abort circuit 108 may communicate with one or more temperature sensors 16 configured to measure temperatures at various locations within the aftertreatment system 22. For example, the abort circuit 108 may receive temperature measurements from a temperature sensor 16 at an inlet of the SCR catalyst 50. The abort circuit 108 may receive temperature measurements from a temperature sensor 16 at an outlet of the SCR catalyst 50. For example, the abort circuit 108 may determine a temperature (e.g., a bed temperature) of the SCR catalyst 50 based on an average between an inlet temperature and an outlet temperature of the SCR catalyst 50.

[0078] The abort circuit 108 may communicate with one or more flow sensors 18 configured to determine or receive an indication (e.g., measurement) of exhaust gas flow at various locations within the aftertreatment system 22. The exhaust gas flow rate may be used in part with the reductant flow rate (e.g., reductant flow rate) to determine the amount of reductant to be dosed into the aftertreatment system 22 for reacting with NOx. For example, the abort circuit 108 determines the amount of reductant to be dosed based on at least the reductant flow rate and the exhaust gas flow rate (e.g., indicating the rate at which the reductant passes through the aftertreatment system 22 to reach a catalyst such as the SCR catalyst 50). The reductant flow rate may be determined at different locations within the aftertreatment system 22. In some cases, the abort circuit 108 is configured to determine the reductant flow rate around the location of the doser 56 that doses the reductant to the aftertreatment system 22 (e.g., between the DPF 40 and the SCR catalyst 50). In some other cases, the disabling circuit 108 is configured to determine the reductant flow at an outlet of the engine 21 (eg, the inlet pipe 24 ).

[0079] To determine the abort state, for example, the abort circuit 108 may determine whether the temperature of the SCR catalyst 50 (e.g., bed temperature) is within a predetermined temperature range, such as from 300 degrees Celsius to 350 degrees Celsius. If the temperature of the SCR catalyst 50, particularly the bed temperature, is outside the temperature range, such as greater than 350 degrees Celsius or less than 300 degrees Celsius, the abort circuit 108 is configured to activate the abort state (e.g., "on" the abort state). If the temperature of the SCR catalyst 50, particularly the bed temperature, is within the temperature range, the abort circuit 108 may determine to disable the abort state. In other embodiments, other temperatures (e.g., component temperature, DPF temperature, etc.) may be used. In addition, the temperature may be an instantaneous temperature, an average temperature over a predefined operating window (e.g., distance traveled, time, etc.), and a high or low temperature of a predefined operating window, etc.

[0080] The abort circuit 108 may determine whether the reductant flow is within a predetermined flow range, such as 200 to 800 cubic feet per minute (CFM) or 500 to 1500 CFM, or other ranges, based on the configuration (e.g., type, design, size, or power output) of the engine 21. If the reductant flow is outside the flow range, such as greater than an upper limit or less than a lower limit, the abort circuit 108 is configured to activate the abort state. In other cases, if the reductant flow is within the flow range, the abort circuit 108 may determine to disable the abort state.

[0081] In some implementations, the abort circuit 108 may use accumulated data to determine whether the operating condition is met. Accumulated data may refer to the accumulation or aggregation of data (e.g., temperature data or reductant flow data) over a time interval. For example, the abort circuit 108 may accumulate temperature data of the SCR catalyst 50 over a time interval such as 10 seconds, 1 minute, 10 minutes, etc. The abort circuit 108 may determine the accumulated temperature of the SCR catalyst 50 based on the average value, mean, or median of the temperature data accumulated over the time interval. In another example, the abort circuit 108 may accumulate reductant flow data over a time interval (e.g., a similar or different time interval). For example, the abort circuit 108 may determine the accumulated reductant flow based on the average value, mean, or median of the reductant flow data accumulated over the time interval. In this case, the abort circuit 108 is configured to compare the accumulated temperature with a temperature range to determine whether the operating condition is met. The abort circuit 108 is configured to compare the accumulated reductant flow with a flow range to determine whether the operating condition is met.

[0082] In various implementations, the abort circuit 108 may not disable the abort state until multiple operating conditions are met. For example, if at least one of the operating conditions (e.g., temperature or reductant flow) is not met, the abort circuit 108 may activate or maintain the activated state of the abort state. In another example, if both the temperature and reductant flow (or other operating conditions) of the SCR catalyst 50 meet their respective ranges or desired operating conditions, the abort circuit 108 may deactivate or maintain the deactivated state of the abort state. Therefore, based on whether the operating conditions are met, the abort circuit 108 may instruct the reductant sensor circuit 109 to reset or continue the reductant concentration calculation. In various configurations, at least one of the abort circuits 108 may be combined with the abort circuit 108 to reset the reductant concentration calculation. Figure 3A Abort circuits 108 (eg, abort circuits 304 ) are described.

[0083] The reductant sensor circuit 109 is configured to calculate the reductant concentration. The reductant may be, for example, urea. The reductant sensor circuit 109 is configured to perform calculations when the suspend state is "off" or inactive (e.g., receiving a signal "0" from the suspend circuit 108). The reductant sensor circuit 109 is configured to reset or stop performing calculations when the suspend state is "on" or active (e.g., receiving a signal "1" from the suspend circuit 108).

[0084] In some implementations, the reductant sensor circuit 109 is configured to perform a reductant concentration calculation in response to receiving additional reductant flow data and conversion efficiency data. The reductant flow data or conversion efficiency data may be measured or calculated periodically (e.g., every second, every 10 seconds, etc.) or in response to receiving readings from their respective sensors, such as readings from the flow sensor 18 or the NOx sensor 12. In response to receiving the data, the reductant sensor circuit 109 may calculate the reductant concentration based at least on the reductant flow and the conversion efficiency to generate a data point of the reductant concentration. The reductant sensor circuit 109 may store the calculated reductant concentration in the memory 103 of the controller 100. For example, the calculated reductant concentration may be part of a short window performance calculation.

[0085] In various implementations, the reductant sensor circuit 109 is configured to aggregate multiple reductant concentration calculations using a moving time window (sometimes referred to as a moving power window). The moving time window may include a fixed / predefined window size. Each window size includes a set of corresponding reductant concentration calculations. For example, a first group may include first to third reductant concentrations, a second group may include fourth to sixth reductant concentrations, and so on. The moving time window is configured to slide or move over time. Depending on how the moving time window slides, moves, or shifts over time, one or more calculated reductant concentrations may or may not overlap.

[0086] For example, each time window can be sequential or adjacent to each other. In this example, any subsequent time window of the moving time window can be after the current or previous time window without overlapping. For example, if the window size is configured as a first duration (e.g., 100 seconds), the first time window can include a first set of data points associated with the recording time of the first duration (e.g., 0 to 100 seconds), the second time window can include a second set of data points associated with the recording time of the second duration (e.g., 101 to 200 seconds) after the first duration, and so on.

[0087] In another example, the moving time window may slide to the next time window based on a predefined number of data samples or data points (e.g., a predetermined number of calculated reducing agent concentrations). For example, if each time window is associated with 10 data points (e.g., 10 calculated reducing agent concentrations), and the moving time window is configured to slide every 5 data points, then the next time window of the moving time window may include 5 new data points and 5 data points associated with the previous time window.

[0088] The reductant sensor circuit 109 is configured to aggregate the calculated reductant concentrations (e.g., data points) from the moving time windows to produce an aggregated or cumulative reductant concentration. The reductant sensor circuit 109 may aggregate the calculated reductant concentrations based on, for example, an average of the calculated reductant concentrations for the respective time windows. The reductant sensor circuit 109 is configured to store the aggregated reductant concentrations in the memory 103 or a data storage device of the controller 100. The reductant sensor circuit 109 may store a timestamp (or time frame) associated with each aggregated reductant concentration. For example, the aggregated reductant concentration may be part of a long window performance calculation.

[0089] The reductant sensor circuit 109 is configured to determine one or more aggregated reductant concentrations in response to activation of the enable state to be output as a result of the reductant concentration calculation. For example, the reductant sensor circuit 109 can maintain the aggregated concentration in the memory 103. In response to receiving an indication of the "on" enable state, the reductant sensor circuit 109 is configured to identify a set of aggregated reductant concentrations calculated before and after the tank refill event. For example, the reductant sensor circuit 109 is configured to identify a first set of aggregated reductant concentrations (e.g., sometimes referred to as pre-refill reductant concentrations) before the tank refill event. The reductant sensor circuit 109 is configured to identify a second set of aggregated reductant concentrations (e.g., sometimes referred to as post-refill reductant concentrations) after the tank refill event. In various cases, the reductant sensor circuit 109 is configured to perform post-refill actions to minimize or mitigate noise after the tank refill event, as discussed herein.

[0090] In some cases, the reductant sensor circuit 109 determines the average, mean, or median of the reductant concentration before refilling and the reductant concentration after refilling. In this case, the reductant sensor circuit 109 generates a reductant concentration before refilling representing the reductant concentration calculated before the tank refilling event and a reductant concentration after refilling representing the reductant concentration calculated after the tank refilling event. The reductant sensor circuit 109 is configured to compare the reductant concentration before refilling with the reductant concentration after refilling. In some cases, if the difference between the reductant concentration after refilling and the reductant concentration before refilling is within a deviation threshold (e.g., less than 2%, 3%, or 5% deviation), the reductant sensor circuit 109 can output the reductant concentration before refilling as a calculation result (e.g., maintaining the reductant concentration post value).

[0091] In some other cases, if the difference between the reductant concentration after refilling and the reductant concentration before refilling is greater than a predefined deviation threshold, such as a deviation greater than 5% or 10%, the reductant sensor circuit 109 may output the reductant concentration after refilling as a calculation result (e.g., update the reductant concentration after value). The reductant concentration after value may indicate the calculated reductant concentration for display to an operator or service entity, such as via the operator I / O device 120 or a remote computing device (e.g., transmitting the reductant concentration after value over a network). The operation of the reductant sensor circuit 109 may be combined with at least one of the other circuits of the controller 100. Figure 3A-3B to describe.

[0092] refer to Figure 3A-3B , depicting a method for using Figure 1-Figure 2 A block diagram of a process 300 for determining a virtual UQS by a controller. The process 300 may be performed by Figure 1-Figure 2 Components are implemented so that they can be referenced to help explain process 300. As shown in the figure, Figure 3A The process 300 includes an enabling circuit 302, a suspending circuit 304, and a reductant sensor circuit 306. One or more circuits (e.g., the enabling circuit 302, the suspending circuit 304, or the reductant sensor circuit 306) may correspond to one or more components of the controller 100, or be a part of the controller 100. The one or more circuits are configured to perform various operations of the process 300. The one or more circuits may be composed of hardware, software, or a combination of hardware and software components.

[0093] The enabling circuit 302 may include or correspond to the enabling circuit 107 of the controller 100. The enabling circuit 302 may perform the operations of the enabling circuit 107, for example, at least Figure 2 For example, the enabling circuit 302 is configured to output an enabling state indicating whether at least one of the predefined enabling conditions has been met. The enabling conditions may include identification of a reductant change (e.g., a change in reductant) reflected in a change in conversion efficiency (e.g., a conversion value), the occurrence of a (fluid) tank refill event, or whether a duration (e.g., a countdown timer) after identification of a reductant change or tank refill event has been met (e.g., timer expiration).

[0094] For example, if the enabling circuit 302 detects or identifies at least one of a reductant change, a tank refill event, or an expiration of a duration after identifying a reductant change or a tank refill event, the enabling circuit 302 is configured to set or maintain the enabling state to be active or "on". In other cases, if all enabling conditions are not met, the enabling circuit 302 is configured to set or maintain the enabling state to be inactive or "off". The enabling circuit 302 is configured to output the enabling state to at least one of the abort circuit 304 or the reductant sensor circuit 306. The "on" enabling state can trigger the abort circuit 304 to perform its operation. For example, the "on" enabling state can trigger the reductant sensor circuit 306 to output a reductant value (e.g., a calculated reductant concentration).

[0095] The abort circuit 304 may include or correspond to the abort circuit 108 of the controller 100. The abort circuit 304 may perform operations such as combining Figure 2 The operation of the abort circuit 108 is described. For example, the abort circuit 304 is configured to output an abort state of the reductant sensor circuit 306, which indicates whether to start or continue to perform a reductant value (e.g., reductant concentration) calculation. The abort circuit 304 configures the abort state based on at least one of the abort conditions / parameters. The abort condition may be related to the temperature of the aftertreatment system 22 (e.g., the bed temperature of the SCR catalyst 50) or the reductant characteristics, such as the reductant flow value (e.g., the dosing rate of the reductant or the amount of the reductant dosing into the aftertreatment system 22).

[0096] For example, if at least one or both of the temperature or the reductant characteristic of the aftertreatment system 22 satisfies a corresponding predetermined threshold, the abort circuit 304 is configured to deactivate the abort state or configure the abort state to "off". The temperature satisfying the threshold may include the temperature of the SCR catalyst 50 being within a predetermined or desired temperature range of the SCR catalyst 50. In some cases, in order for the reductant characteristic to satisfy the threshold, the abort circuit 304 may determine, for example, that the amount of reductant dosed into the aftertreatment system 22 is above a minimum dosage threshold (e.g., above 2 liters per hour). In some other cases, for example, in order for the reductant characteristic to satisfy the threshold, the abort circuit 304 may determine that the reductant flow rate is within a predetermined flow range. In various configurations, if at least one of the abort conditions / parameters (e.g., temperature and reductant characteristic) is not satisfied, the abort circuit 304 maintains or sets the abort state to "on" or active.

[0097] In some embodiments, the suspend circuit 304 can change or maintain the suspend state based on at least one enabling condition being satisfied, such as after receiving an "on" enable state from the enabling circuit 302. For example, if a tank refill event is identified by the enabling circuit 302, the suspend circuit 304 is configured to receive an "on" enable state from the enabling circuit 302. In response to receiving the "on" enable state, the suspend circuit 304 can maintain or set the suspend state to "on" or active, indicating that the calculation of the reductant concentration will be stopped or reset. In some cases, the enabling circuit 302 can maintain the "on" enable state until a predefined duration (e.g., a countdown timer) after the tank refill event is identified. Therefore, after the timer expires, the suspend circuit 304 can determine whether to maintain the active suspend state or deactivate the suspend state based on the suspend parameters discussed herein.

[0098] The reductant sensor circuit 306 may include or correspond to the reductant sensor circuit 109 of the controller 100. The reductant sensor circuit 306 may perform the features or functions of the reductant sensor circuit 109, such as in combination with Figure 2 The reductant sensor circuit 306 may include a circuit or a subset of various components configured to calculate the reductant concentration and output the calculation result, such as in combination with Figure 3B as described.

[0099] Figure 3B A block diagram of various circuits or components of the reductant sensor circuit 306 is depicted. One or more components of the reductant sensor circuit 306 may be configured to perform the features or operations of the reductant sensor circuit 306 discussed herein. As shown, the reductant sensor circuit 306 includes at least a window-based performance circuit 308, a real-time reductant concentration (e.g., urea concentration (UC)) circuit 310, a pre-refill circuit 312, an action circuit 314, a post-refill circuit 316, and a final UC determination circuit 318. One or more components of the reductant sensor circuit 306 may be composed of hardware, software, or a combination of hardware and software. In some configurations, the window-based performance circuit 308 and the real-time UC circuit 310 may operate or execute based on a suspension state signaled from the suspension circuit 304. In some other configurations, the pre-refill circuit 312, the action circuit 314, the post-refill circuit 316, and the final UC determination circuit 318 may operate or execute based on an enable state signaled from the enable circuit 302.

[0100] When the suspend state is "on", the reductant sensor circuit 306 may suspend or disable the window-based performance circuit 308 and the real-time UC circuit 310. When the suspend state is "on", the reductant sensor circuit 306 may not perform the reductant concentration calculation. In response to the suspend state being "off", the reductant sensor circuit 306 may execute the window-based performance circuit 308 and the real-time UC circuit 310 to perform the calculation.

[0101] The window-based performance circuit 308 is configured to perform a window-based calculation (e.g., a rolling window calculation) on the reductant concentration. The window-based calculation may refer to or correspond to a short-term window calculation. In order to perform the reductant concentration calculation, the window-based performance circuit 308 may receive one or more screen conditions / parameters (or inputs). The screen conditions may include operating conditions of the aftertreatment system 22, such as whether one or more components of the aftertreatment system 22 are operating as expected or within desired operating conditions.

[0102] For example, the screening condition may include an operating condition of at least one of the NOx sensor 12, the doser 56, the flow sensor 18, or other components of the aftertreatment system 22. The window-based performance circuit 308 (or other circuitry of the controller 100) may determine whether the doser 56 is dosing a commanded or expected amount of reductant into the aftertreatment system 22 based on, for example, a reductant sensor configured to measure a dosing rate or amount of reductant at or downstream of the doser 56. In this case, the window-based performance circuit 308 is configured to receive dosing command feedback indicating whether the doser 56 is operating as expected or commanded.

[0103] The window-based performance circuit 308 can determine whether the NOx sensor 12 is operating as expected by comparing the measurement results from the NOx sensor 12 and the output from the virtual NOx sensor. The virtual NOx sensor may correspond to a model that is generated or trained to determine the NOx value (e.g., the amount of NOx) downstream of the engine 21 based on the operating characteristics of the engine 21. For example, the window-based performance circuit 308 can provide the operating characteristics of the engine 21 as input to the model. The operating characteristics may include at least engine speed, temperature, intake manifold pressure, or fuel injection rate, etc. The model receives and processes the input to estimate the NOx value at the outlet of the engine 21. Therefore, the window-based performance circuit 308 can compare the estimated NOx value from the model (e.g., the virtual NOx sensor) with the NOx measurement results from the NOx sensor 12 upstream of the SCR catalyst 50.

[0104] If the NOx measurement is within a predetermined acceptable range from the modeled NOx value (e.g., within a difference of + / - 5%), the window-based performance circuit 308 may use the NOx measurement from the NOx sensor 12 as part of the reductant concentration calculation (e.g., for determining conversion efficiency). In other cases, if the NOx measurement is outside of the predetermined acceptable range of the modeled NOx value, the window-based performance circuit 308 may use the NOx value from the model as part of the reductant concentration calculation. In some cases, the window-based performance circuit 308 determines a ratio between the NOx measurement from the NOx sensor 12 and the NOx value from the model. The ratio may represent a deviation of the NOx measurement from the NOx value, such as In such a case, the window based performance circuit 308 may use the ratio as a correction factor, such as by applying the correction factor to the NOx measurement (eg, calculated, multiplied, or divided based on the ratio), thereby improving the accuracy of the measurement from the NOx sensor 12 .

[0105] Similar to the upstream NOx sensor 12, the window-based performance circuit 308 is configured to determine the operating condition of the NOx sensor 12 downstream of the SCR catalyst 50 (e.g., in part for determining the conversion efficiency). The window-based performance circuit 308 can perform similar processing for determining the operating condition of the upstream NOx sensor 12. For example, the window-based performance circuit 308 can provide the operating characteristics of the engine 21 as an input to the model. In addition, the window-based performance circuit 308 can provide at least an amount of reductant or an indication of the dosing rate as an input to the model, such as the reaction of the reductant with the NOx upstream of the SCR catalyst 50. In some cases, the window-based performance circuit 308 can provide the historical conversion efficiency of the SCR catalyst 50 as an input to the model. Based on the input, the model is configured to estimate the reduction of upstream NOx to determine the residual NOx downstream of the SCR catalyst 50. Therefore, the window-based performance circuit 308 can use the model to determine a NOx value representing the amount of NOx downstream of the SCR catalyst 50. Similar to the upstream NOx sensor 12 , the window based performance circuit 308 is configured to compare the downstream NOx measurement to the downstream NOx value to determine whether to use the measurement from the NOx sensor 12 , the output from the model, or apply a correction (eg, a correction factor) to the NOx measurement.

[0106] The window-based performance circuit 308 can determine the operating condition of the flow sensor 18. Similar to determining the operating condition of the NOx sensor 12, the window-based performance circuit 308 is configured to provide inputs (e.g., engine operating characteristics) to the model to estimate the expected exhaust flow rate (e.g., flow value) from the engine 21, such as based on engine speed, temperature, intake manifold pressure, etc. The window-based performance circuit 308 can compare the flow value with the flow measurement result from the flow sensor 18. If the flow measurement result is outside the predetermined acceptable range of the model flow value, the window-based performance circuit 308 is configured to use the estimated flow value from the model as part of the reductant concentration calculation, or apply a correction to the flow measurement result from the flow sensor 18. In other cases, if the flow measurement result is within the predetermined acceptable range of the model flow value, the window-based performance circuit 308 is configured to use the measurement result from the flow sensor 18 as part of the calculation, for example.

[0107] In some implementations, the window-based performance circuit 308 may detect or receive an indication of the amount of ammonia released downstream of or from the SCR catalyst 50 (e.g., ammonia slip). The window-based performance circuit 308 may determine or receive an indication of the amount of ammonia slip as discussed herein. If the ammonia slip is greater than or equal to a predetermined threshold, the window-based performance circuit 308 may determine that the aftertreatment system 22 is operating outside of desired or acceptable parameters (e.g., thresholds, conditions, or limitations).

[0108] In some implementations, the window-based performance circuit 308 may detect or receive an indication of the amount of unreacted NOx measured downstream of the SCR catalyst 50 (e.g., NOx slip). The NOx slip may be measured by the NOx sensor 12 (or virtual NOx sensor) located downstream of the SCR catalyst 50. If the NOx slip is greater than or equal to a predetermined threshold, the window-based performance circuit 308 may determine that the aftertreatment system 22 is operating outside of expected or acceptable parameters. Based on the screening conditions, ammonia slip, NOx slip, or other parameters associated with the operation of the aftertreatment system 22, the window-based performance circuit 308 may determine whether the aftertreatment system 22 is operating as expected or desired (e.g., within an expected range).

[0109] If the operating state of one or more components of the aftertreatment system 22 is unacceptable (e.g., the components are operating outside of expected parameters), the controller 100 may provide a notification to an operator or service entity via the operator I / O device 120. In other cases, if the operating state of the aftertreatment system 22 is satisfactory or acceptable (e.g., the components of the aftertreatment system 22 are operating as desired or expected), the window-based performance circuit 308 is configured to perform a reductant concentration calculation based on at least a conversion value for the catalyst (e.g., conversion efficiency) and a value (e.g., ratio or ANR) regarding the amount of ammonia relative to the NOx value (e.g., the amount of NOx from upstream of the catalyst).

[0110] The window-based performance circuit 308 is configured to calculate the reductant concentration of each conversion efficiency data point and the ANR data point associated with the conversion efficiency data point (e.g., corresponding to a similar time instance). The window-based performance circuit 308 can group the calculated reductant concentrations into different reductant concentration sets. Each set corresponds to a time window with a predefined size, such as when the calculation is performed by moving the time window.

[0111] In various implementations, the window-based performance circuit 308 is configured to transmit a result (e.g., a calculated reductant concentration) to the real-time UC circuit 310 in response to a trigger condition. The trigger condition may include an indication of ammonia slip or an indication of NOx slip, among others. For example, if at least one of ammonia slip greater than or equal to a first threshold (e.g., a maximum acceptable ammonia slip) or NOx slip greater than or equal to a second threshold (e.g., a maximum acceptable NOx slip) is established, the window-based performance circuit 308 is configured to store or send the calculated result to the real-time UC circuit 310. In some cases, ammonia slip or NOx slip may be an indicator of relatively high sulfur content in the SCR catalyst 50 (or other components of the aftertreatment system 22), so that the window-based performance circuit 308 may stop calculating during the NOx slip or ammonia slip time range. Depending on the configuration, the window-based performance circuit 308 may, for example, start calculating during the NOx slip or ammonia slip time range. The window-based performance circuit 308 may provide results as separate sets of reductant concentrations, where each set corresponds to a time window. By providing results to the real-time UC circuit 310, the window-based performance circuit 308 may allow the results to be aggregated or accumulated, thereby smoothing fluctuations and potential noise in the data to improve the accuracy of the calculations.

[0112] The window-based performance circuit 308 may provide other information related to the calculated reductant concentration to the real-time UC circuit 310, such as upstream NOx measurements (e.g., engine output NOx (EONOx)), downstream NOx measurements (e.g., SCR-output NOx (SONOx)), and ANR. The window-based performance circuit 308 may provide an indication of ammonia slip as an indicator for performing operations of the real-time UC circuit 310. In some cases, the window-based performance circuit 308 may send an indication of NOx slip as an indicator for performing operations of the real-time UC circuit 310. In some implementations, the window-based performance circuit 308 may send an indication to the real-time UC circuit 310 to update the stored reductant concentration with the additional calculated reductant concentration. In order to update the stored reductant concentration, the window-based performance circuit 308 may perform ammonia slip detection. If ammonia slip is detected (e.g., when ammonia slip is detected), the window-based performance circuit 308 may not update or provide information (e.g., EONOx, SONOx, ANR, etc.) to the real-time UC circuit 310. If ammonia slip is not detected, the window-based performance circuit 308 may update or provide at least one of additional information (including EONOx, SONOx, ANR, reductant dosing rate, etc.) to the real-time UC circuit 310 .

[0113] The real-time UC circuit 310 is configured to receive the reductant concentration calculated by the window-based performance circuit 308. The real-time UC circuit 310 may receive data related to the calculation of the reductant concentration from the window-based performance circuit 308, such as upstream and downstream NOx measurements (e.g., used to determine a conversion value), ANR and indications of ammonia slip (e.g., the amount of ammonia measured downstream from the catalyst), etc. The real-time UC circuit 310 is configured to perform long-term window calculations by accumulating or aggregating short-term window calculations.

[0114] The real-time UC circuit 310 is configured to aggregate multiple reductant concentrations calculated by the window-based performance circuit 308. For example, the real-time UC circuit 310 can aggregate the reductant concentrations calculated for each time window. If each time window includes 10 data points (e.g., 10 reductant concentrations), the real-time UC circuit 310 can determine the average (or mean or median, etc.) of the 10 data points. The real-time UC circuit 310 can aggregate multiple individually calculated reductant concentrations to increase the stability of the output. Increasing the stability of the output refers to reducing the fluctuation of the calculated reductant concentration, minimizing the variability (e.g., noise) in the data, etc.

[0115] In some implementations, the real-time UC circuit 310 may aggregate a predetermined number of reductant concentrations (or data points) calculated by the window-based performance circuit 308. For example, if the predetermined number is configured as 5 data points, the real-time UC circuit 310 may determine an average of every 5 reductant concentrations. In some cases, the predetermined number of reductant concentrations may correspond to a window size. The real-time UC circuit 310 may output an aggregated reductant concentration based on the aggregation of multiple reductant concentrations or data points.

[0116] In some implementations, the real-time UC circuit 310 can calculate the aggregated reductant concentration by accumulating variables used to calculate the reductant concentration. For example, the real-time UC circuit 310 can accumulate upstream NOx values, downstream NOx values, and values ​​regarding the amount of ammonia relative to the NOx value (e.g., upstream NOx value). The real-time UC circuit 310 can calculate a cumulative conversion value (e.g., conversion efficiency) based on the accumulated upstream and downstream NOx values. Subsequently, the real-time UC circuit 310 can calculate the aggregated (or cumulative) reductant concentration based on the cumulative conversion value and the cumulative value regarding the amount of ammonia relative to the NOx value (e.g., cumulative ANR). In this example, the calculation of the aggregated reductant concentration may include at least dividing the aggregated conversion value by the cumulative ANR.

[0117] In various configurations, the real-time UC circuit 310 is configured to output the aggregated reductant concentration to the final UC determination circuit 318. The real-time UC circuit 310 is configured to output the aggregated reductant concentration in response to or after the enable circuit 107 triggers an enable state / condition. In this case, triggering the enable state includes the enable state being "turned on" or activated. By transmitting the aggregated reductant concentration, the aggregated reductant concentration can be stored in the final UC determination circuit 318.

[0118] When the enable state is "off", the reductant sensor circuit 306 may disable at least one of the pre-refill circuit 312, the action circuit 314, the post-refill circuit 316, or the final UC determination circuit 318. When the enable state is "off", the reductant sensor circuit 306 may not perform, for example, the operation of at least one of the circuits 312-318. In response to the enable state being in the "on" state or activated, the reductant sensor circuit 306 may perform the operation of at least one of the circuits 312-318. The activated enable state indicates, for example, outputting or determining the reductant concentration for providing to an operator or a service entity via the operator I / O device 120.

[0119] The pre-refill circuit 312 is configured to store historical data or historical states of the system 10 (e.g., the engine 21 or the aftertreatment system 22) before a tank refill event occurs. For example, the pre-refill circuit 312 is configured to record and store conversion values ​​(e.g., NOx conversion efficiency or upstream and downstream NOx values ​​used to calculate conversion values), errors indicating relatively high sulfur content (e.g., high sulfur errors), errors indicating relatively low conversion values ​​(e.g., low conversion efficiency errors), reductant concentrations calculated before the tank refill event (or aggregated reductant concentrations), etc. The historical data may include a timestamp indicating when the variable was recorded, calculated, or determined. The pre-refill circuit 312 may provide an indication of pre-refill high sulfur content (preHiS) to the final UC determination circuit 318.

[0120] In some implementations, the pre-refill circuit 312 may receive calculated reductant concentrations from the window-based performance circuit 308, or receive aggregated reductant concentrations from the real-time UC circuit 310. The pre-refill circuit 312 may store these reductant concentrations, for example, in the memory 103 of the controller 100. The pre-refill circuit 312 may not store reductant concentrations calculated or aggregated after a tank refill event. The reductant concentration may be considered pre-refill based on the timestamp associated with the data point of the reductant concentration. For example, any reductant concentration determined within a predefined duration prior to at least a tank refill event may be stored by the pre-refill circuit 312 and considered a pre-refill reductant concentration (e.g., preUC).

[0121] In another example, the reductant concentration considered to be the reductant concentration after a first tank refill event (e.g., the post-refill reductant concentration) may be considered to be the pre-refill reductant concentration relative to a second or next tank refill event. The pre-refill circuit 312 may provide the pre-refill reductant concentration to the final UC determination circuit 318, along with other variables related to the historical state of the system 10 prior to the tank refill event, such as to determine the reductant concentration to be output for presentation to an operator.

[0122] In some implementations, the pre-refill circuit 312 may determine or receive information about whether the catalyst has aged (e.g., pre-aged) prior to the tank refill event, for example, based on the conversion efficiency of the catalyst being below a predetermined conversion efficiency threshold. The pre-refill circuit 312 may provide an indication of whether the catalyst has aged (e.g., "1" for aged and "0" for not aged) to the final UC determination circuit 318.

[0123] The action circuit 314 is configured to initiate or perform at least one action after detecting a tank refill event. The action circuit 314 can perform an action by sending a command to one or more components of the system 10. For example, after detecting a tank refill event, the action circuit 314 can determine whether the catalyst (e.g., SCR catalyst 50) has aged, or whether a relatively high sulfur fuel has been detected (e.g., detected by a sulfur dioxide sensor). High sulfur fuel can be an indicator of a relatively high sulfur content accumulated in the catalyst. The action circuit 314 determines whether the catalyst has aged based on the conversion value. If the conversion value is less than the conversion threshold, the action circuit 314 can determine that the catalyst has aged and is operating outside the desired operating parameters.

[0124] If at least one of high sulfur fuel or aged catalyst has been detected, the action circuit 314 is configured to start a regeneration operation of the catalyst. The action circuit 314 can activate the regeneration of the catalyst to remove noise that causes conversion efficiency loss due to at least an aged catalyst or sulfur accumulated in the catalyst. For example, the action circuit 314 can activate regeneration by sending a command to an injector (e.g., a hydrocarbon injector) indicating a predefined amount of hydrocarbons to be injected into the aftertreatment system 22 (e.g., upstream of the DPF 40). The hydrocarbons can react with oxygen from the exhaust gas of the engine 21, thereby generating heat to burn off particulate matter from the catalyst, thereby restoring or regenerating the performance of the catalyst.

[0125] In some implementations, the action circuit 314 is configured to perform an action before receiving an enable state of "1" (e.g., an "on" enable condition). For example, the action circuit 314 may perform a regeneration before identifying a tank refill event. In some cases, the action circuit 314 may determine that the catalyst has aged or high sulfur fuel is present and perform a regeneration in response to receiving an activated enable state.

[0126] The post-refill circuit 316 is configured to store a calculated or aggregated reductant concentration (or aggregated reductant concentration) after a tank refill event. In some arrangements, a tank refill event may correspond to or refer to when an enable condition switches from a "0" to a "1" or from an inactive enable state to an active enable state. As discussed herein, for purposes of providing examples herein, the aggregated reductant concentration may be used by the pre-refill circuit 312 and the post-refill circuit 316, for example, in place of a separately calculated reductant calculation.

[0127] In response to receiving an active enable state, the post-refill circuit 316 is configured to determine whether to send an update including an aggregated reductant concentration determined after the tank refill event, or to maintain the aggregated reductant concentration determined before the tank refill event (e.g., by avoiding or skipping sending updates). For example, the post-refill circuit 316 is configured to obtain or receive at least one aggregated reductant concentration (e.g., post-refill reductant concentration (postUC)) from the real-time UC circuit 310 in response to receiving an enable condition "1" indicating the occurrence of a tank refill event or a predefined time period after the tank refill event has occurred. The post-refill circuit 316 is configured to compare the pre-refill reductant concentration with the post-refill reductant concentration. If the difference between the pre-refill and post-refill reductant concentrations is greater than or equal to a threshold value (e.g., a 5% or 10% deviation), the post-refill circuit 316 is configured to send an update including the post-refill reductant concentration. Based on the update, the post-refill circuit 316 can allow the final UC determination circuit 318 to output the desired reductant concentration result for the operator or service entity.

[0128] The final UC determination circuit 318 is configured to receive at least one of an indication of high sulfur fuel prior to a tank refill event, catalyst aging (e.g., conversion efficiency) prior to a tank refill event, a pre-refill reductant concentration, or an update from one or more circuits of the reductant sensor circuit 306 (e.g., pre-refill circuit 312, action circuit 314, or post-refill circuit 316). The final UC determination circuit 318 may receive other inputs from the reductant sensor circuit 306 or one or more circuits of the controller 100.

[0129] In various implementations, the final UC determination circuit 318 is configured to output an indication of at least one of the pre-refill reductant concentration or the post-refill reductant concentration. The final UC determination circuit 318 may output the indication based on an update (or lack of update) from the post-refill circuit 316. For example, in response to receiving the pre-refill reductant concentration, the final UC determination circuit 318 is configured to output an indication of the pre-refill reductant concentration to the operator I / O device 120 for presentation to the operator. If the final UC determination circuit 318 receives an update indicating that the post-refill reductant concentration deviates from the pre-refill reductant concentration by at least a predetermined threshold (e.g., a deviation greater than 5%), the final UC determination circuit 318 is configured to output the post-refill reductant concentration to the operator I / O device 120. In some cases, the final UC determination circuit 318 may receive an update indicating that the pre-refill reductant concentration is maintained. In this case, the final UC determination circuit 318 may maintain the pre-refill reductant concentration for transmission to the operator I / O device 120.

[0130] In some implementations, the final UC determination circuit 318 is configured to determine which of the reductant concentrations before or after refilling to output based on a comparison between the two reductant concentrations. For example, the final UC determination circuit 318 is configured to receive an update indicating the reductant concentration after refilling. The final UC determination circuit 318 is configured to compare the reductant concentrations before and after refilling. If the difference is greater than or equal to a predetermined threshold, the final UC determination circuit 318 is configured to output the reductant concentration after refilling. Otherwise, the final UC determination circuit 318 is configured to output or maintain the reductant concentration before refilling.

[0131] In certain configurations, when the pre-refill reductant concentration is maintained, the final UC determination circuit 318 may send an output status of "0" indicating that the previous calculation of the reductant concentration was acceptable, satisfactory, or similar to the calculation after the tank refill event. For example, the final UC determination circuit 318 may send an output status of "1" to indicate that the previous calculation has been changed to the post-refill reductant concentration.

[0132] In some configurations, the reductant sensor circuit 306 (or other circuitry of the controller 100) is configured to send a notification to the operator via the operator I / O device 120 based on the reductant concentration calculation. For example, the final UC determination circuit 318 can send an indication to indicate that the reductant concentration is being calculated. For example, the final UC determination circuit 318 can send an indication to indicate that the determined reductant concentration is within an acceptable range, such as within an expected concentration range of 25%-40%. In some cases, the final UC determination circuit 318 can send an alarm indication to indicate that the determined reductant concentration is outside of the acceptable range, such as a concentration less than 25% or greater than 40%. As a result, the operator or service entity can replace the reductant, fluid tank, or other maintenance procedures.

[0133] In various configurations, indications of high sulfur levels and / or catalyst aging may be used by the final UC determination circuit 318 to maintain or discard certain data / information. For example, if at least one of a high sulfur level pre-refill event and / or a catalyst aging pre-refill event is not present or detected, and if the difference between the (e.g., currently determined) postUC and preUC is less than a delta threshold (e.g., less than a 5% difference), the final UC determination circuit 318 may maintain the same preUC value, e.g., to minimize or mitigate potential measurement errors. In this case, the postUC may be discarded.

[0134] In another example, if at least one of a high sulfur content pre-refill event and / or a catalyst aged pre-refill event is not present or detected, and if the difference between postUC and preUC is greater than or equal to the delta threshold, the final UC determination circuit 318 may use the reductant concentration determined or calculated after the tank refill event (e.g., current postUC). In this case, preUC may be discarded. In yet another example, if at least one of a high sulfur content pre-refill event and / or a catalyst aged pre-refill event is present or detected, the final UC determination circuit 318 may determine that the preUC value is unreliable (e.g., inaccurate), such that the final UC determination circuit 318 is configured to use the postUC value, for example.

[0135] Figure 4 Depicted is a method for using a Figure 1-Figure 3B Flowchart of method 400 for executing virtual UQS by a controller. Method 400 may be performed by Figure 1-Figure 3B 4. The components of method 400 are performed so that they can be referenced to help explain method 400. As discussed below, method 400 includes processes 402-422 for determining a reductant value (e.g., a reductant concentration) and other processes (or other operations). In various implementations, certain processes may be performed before or after each other. In some implementations, one or more processes of method 400 may be performed in conjunction with Figure 1-Figure 3B At least one of the operations or features described in may be performed similarly, additionally or alternatively.

[0136] At process 402, the controller 100 (e.g., the processing circuit 101) may determine whether the NOx sensor 12 is operating as expected. The NOx sensor 12 includes at least one of a NOx sensor 12 upstream of a catalyst (e.g., an SCR catalyst 50) or a NOx sensor 12 downstream of a catalyst. For example, the controller 100 is configured to determine whether the NOx sensor 12 is operating as expected or desired based on a comparison of a NOx measurement result from the NOx sensor 12 with a NOx value output by a virtual NOx sensor (e.g., a model). If the NOx measurement result (e.g., an average value of the NOx measurement result) is within a predetermined range of the NOx value (e.g., an average value of the NOx value output from the virtual NOx sensor), the controller 100 determines that the NOx sensor 12 is operating as expected. In this case, the controller 100 may proceed to process 406.

[0137] In other cases, if the NOx measurement is outside of a predefined range of NOx values ​​from the virtual NOx sensor, the controller 100 may proceed to process 404. The predefined range may be a minimum or maximum deviation amount, a minimum or maximum ratio between the measured NOx value and the generated NOx value (e.g., between 0.8 and 1.2 for measured NOx relative to generated NOx values).

[0138] At process 404, the controller 100 (e.g., the processing circuit 101) may perform a NOx model correction to calibrate the NOx sensor 12. The controller 100 is configured to perform a correction on the NOx sensor 12 using a ratio between the measured NOx from the NOx sensor 12 and the NOx value generated by the virtual NOx sensor. For example, the controller 100 may apply the ratio to the NOx measurement results for correction. In another example, the controller 100 may use a virtual NOx output instead of a NOx sensor measurement result.

[0139] At process 406, the controller 100 (e.g., enabling circuit 107, 302) may determine whether a (fluid) tank refill event has been detected. The controller 100 is configured to determine that a tank refill event has occurred in response to an increase in the amount of reductant stored in the tank, as discussed herein. In some implementations, the controller 100 may determine whether the tank has been refilled based on the reductant level in the tank before and after an engine idle event (e.g., when the system 10 is not moving). If the controller 100 detects a tank refill event, the controller 100 may proceed to process 408. Otherwise, the controller 100 may continue to monitor the tank refill event or continue to monitor the status of the NOx sensor 12.

[0140] In process 408, the controller 100 (e.g., the action circuit 314) can determine whether the catalyst (e.g., the SCR catalyst 50) has aged or detected high sulfur fuel. Catalyst aging can be based on a conversion value (e.g., the conversion efficiency of the catalyst). High sulfur fuel detection can be based on a sensor configured to trigger an error in response to high sulfur fuel detection. In some cases, the controller 100 determines the high sulfur content in the catalyst based on whether the exhaust flow rate measured around the catalyst location is within an expected range based on the operating characteristics of the engine 21 (e.g., compared to the expected exhaust flow rate determined based on the operating characteristics of the engine 21). If the exhaust flow rate is outside the range, the controller 100 can determine that there is a restriction (e.g., soot accumulation) caused by high sulfur fuel in the catalyst. If at least one of an aged catalyst or high sulfur fuel is detected, the controller 100 can proceed to process 410. Otherwise, the controller 100 can proceed to process 412.

[0141] In process 410, the controller 100 (e.g., the action circuit 314) can perform regeneration on the catalyst. The controller 100 can perform regeneration by commanding the hydrocarbon injector to inject hydrocarbons into the exhaust gas flow of the aftertreatment system 22. By regenerating the catalyst, the controller 100 can minimize or mitigate noise from catalyst aging or high sulfur fuel, which can minimize changes used to calculate at least the conversion value or in some cases the ratio of the amount of ammonia to the NOx value (e.g., ANR).

[0142] At process 412, the controller 100 (e.g., the abort circuit 108, 304) may determine whether an abort condition has been met / reached. The abort condition may include at least one of a temperature of the aftertreatment system 22 (or catalyst) or a reductant flow rate (e.g., a reductant dosing rate), as well as other conditions indicative of desired operating parameters of the aftertreatment system 22. In this case, by meeting or reaching the abort condition, the controller 100 is configured to set the abort state to "0" (e.g., deactivate the abort state). When the abort condition is not met, the controller 100 may maintain or set the abort state to "1".

[0143] In some implementations, the controller 100 is configured to determine that the suspension condition is satisfied based on at least one of the temperature of the catalyst satisfying a predetermined temperature range (e.g., between 250 degrees Celsius and 400 degrees Celsius) or the reductant flow satisfying a predetermined flow range (e.g., at or above a minimum dosing rate). In response to satisfying the suspension condition, the controller 100 is configured to deactivate the suspension state (e.g., set to "0") and proceed to process 414.

[0144] At process 414, the controller 100 (e.g., the reductant sensor circuit 109, 306 or the window-based performance circuit 308) may determine whether a filter condition is satisfied. The filter condition may include at least an operating state of one or more components (e.g., a doser, a sensor, etc.) of the aftertreatment system 22, such as whether the component is operating as expected (e.g., within acceptable operating parameters). If the filter condition is satisfied, the controller 100 may proceed to process 416. In other cases, the controller 100 may continue to monitor the filter condition, perform corrections or updates to one or more components of the aftertreatment system 22 to operate as expected, or provide an operator with an alert about the state of one or more components of the aftertreatment system 22 via the operator I / O device 120.

[0145] At process 416, the controller 100 (e.g., the window-based performance circuit 308) may perform a short window performance calculation. The short window performance calculation may include or correspond to a reductant concentration calculation using a moving time window. For example, with respect to the operation of the window-based performance circuit 308, the controller 100 may perform the following: Figure 3BThe controller 100 may be configured to calculate a reductant value (e.g., reductant concentration) based on at least the received or determined conversion efficiency and ANR. The controller 100 may perform calculations for at least one predetermined time window. Each time window may be associated with one or more calculated reductant concentrations.

[0146] At process 418, the controller 100 (e.g., the window-based performance circuit 308) may determine whether ammonia slip (or in some cases NOx slip) has been detected. The controller 100 may perform the determination or identification of ammonia slip while performing the short window performance calculations. Ammonia slip (or NOx slip) may be detected based on the measured ammonia (or NOx) exceeding a corresponding predetermined threshold. In response to the detection, the controller 100 may continue to monitor ammonia slip. In response to the measured ammonia being below a predetermined threshold (e.g., no ammonia slip is detected), the controller 100 may proceed to process 420. The controller 100 may stop or pause the short window performance calculations in response to the detection. In some implementations, the controller 100 may continue the short window performance calculations once ammonia slip (or NOx slip) is detected.

[0147] At process 420, the controller 100 (e.g., the window-based performance circuit 308) can determine whether there are enough samples (e.g., a sufficient number of data points). The controller 100 is configured to determine whether there are enough samples by comparing the number of reductant concentrations (data points) to a sample threshold (e.g., indicating a minimum acceptable sample). If the number of reductant concentrations is greater than or equal to the threshold, the controller 100 can proceed to process 422. Otherwise, the controller 100 can continue to perform and collect calculations or results from the short window performance calculations (at process 416), such as when no ammonia slip is detected.

[0148] At process 422, the controller 100 (eg, the real-time UC circuit 310) may perform a long window performance calculation. This may be similar to at least in conjunction with Figure 3B The operation of the real-time UC circuit 310 is used to describe the process of the long window performance calculation. For example, the controller 100 is configured to perform the long window performance calculation by aggregating or accumulating the calculated reductant concentrations from the short window performance calculation. The controller 100 is configured to aggregate multiple reductant concentrations within a given time window. Therefore, the controller 100 can determine or generate an aggregated reductant concentration. At this stage, the aggregated reductant concentration can be considered as the post-refill reductant concentration. If another tank refill event is detected, the aggregated reductant concentration can be considered as the pre-refill reductant concentration relative to the next / subsequently determined aggregated reductant concentration (e.g., the previous post-refill reductant concentration).

[0149] Figure 5is the use according to the example embodiment Figure 1-Figure 3B A flowchart of a method for a controller to determine a reductant concentration through a virtual UQS. The method 500 may be performed by Figure 1-Figure 3B 500 is performed by components of the method 500 so that they can be referenced to help explain the method 500. As discussed below, the method 500 includes processes 502-504 for determining a reductant value (e.g., a reductant concentration) and other processes (or other operations). In various implementations, certain processes may be performed before or after each other. For example, one or more processes of the method 500 may be performed similarly, additionally, or alternatively to certain processes of the method 400.

[0150] In process 502, the controller 100 is configured to receive an indication of a fluid tank refill event (sometimes referred to as a tank refill event). The fluid tank refill event may indicate the refilling of a tank storing a reductant. In order to identify a fluid tank refill event, the controller 100 may determine a first amount of reductant stored in the fluid tank before the engine idle event (e.g., a first reductant level). The controller 100 may determine a second amount of reductant stored in the fluid tank after the engine idle event (e.g., a second reductant level). The controller 100 may compare the first amount of reductant and the second amount of reductant to determine a difference. If the difference between the first amount and the second amount of reductant is greater than or equal to a predefined threshold, such as an increase of 30%, 50%, or 70%, the controller 100 may identify the occurrence of a fluid tank refill event.

[0151] In some implementations, before or after executing one or more routines described herein, for example, before determining a conversion value or a value regarding the amount of ammonia relative to a NOx value, the controller 100 may identify at least one noise factor that affects the aftertreatment system. The noise factor may refer to certain aspects of the operation of the aftertreatment system 22 that may affect the calculation of the reductant value (e.g., reductant concentration). In response to identifying the noise factor, the controller 100 may initiate at least one action to address (e.g., minimize or mitigate) the noise factor that affects the aftertreatment system 22 or the calculation of the reductant value.

[0152] For example, the noise factor may include or correspond to the accuracy of a NOx sensor upstream or downstream of the catalyst. In this case, in order to initiate at least one action, the controller 100 may use a model (e.g., a virtual NOx sensor) to calculate a virtual NOx value upstream or downstream of the catalyst based on one or more operating characteristics of the engine 21, as discussed herein. The virtual NOx value refers to a model output obtained by processing the operating characteristics of the engine 21 used as model input. Based on the relative location of the NOx sensor, the virtual NOx value may be upstream or downstream of the catalyst. For example, an upstream virtual NOx value may be compared to a NOx value measured by an upstream NOx sensor 12. Similarly, a downstream virtual NOx value may be compared to a NOx value measured by a downstream NOx sensor 12.

[0153] The controller 100 may determine a value regarding a difference between a virtual NOx value and a NOx value measured by a NOx sensor. Based on whether the value regarding a difference between a virtual NOx value and a NOx value measured by a NOx sensor satisfies a threshold, the controller 100 may use a value (or measurement result) from one of the model or the NOx sensor. For example, if the difference is greater than or equal to a threshold (e.g., does not satisfy the threshold), the controller 100 may use a virtual NOx value or calculate a correction factor to adjust the NOx value from the physical NOx sensor 12. If the difference is less than a threshold (e.g., satisfies the threshold), the controller 100 may use the NOx value from the NOx sensor 12.

[0154] In another example, at least one noise factor may include or correspond to catalyst aging or a limitation in the catalyst (e.g., relatively high sulfur content or soot in the catalyst, or in some cases, high sulfur fuel detection). If the noise factor corresponds to catalyst aging, the controller 100 is configured to compare the conversion value (e.g., conversion efficiency) to a threshold. In response to the conversion value being less than the threshold, the controller 100 is configured to initiate an action including a catalyst regeneration event.

[0155] If the noise factor corresponds to a restriction in the catalyst (e.g., high sulfur fuel detection), the controller 100 may receive a value from a sensor (e.g., a sulfur dioxide sensor) indicating a first flow rate (e.g., exhaust gas flow rate) measured at or upstream of the catalyst. The controller 100 may determine a second flow rate based on one or more operating conditions of the engine 21, where the second flow rate corresponds to a virtual flow rate. If the difference between the first flow rate (e.g., measured by the flow sensor 18) and the virtual flow rate is greater than or equal to a threshold, the controller 100 may initiate a regeneration event for the catalyst, such as to burn off particulate matter of the catalyst that may cause the restriction.

[0156] At process 504, the controller 100 is configured to receive an indication of a conversion value of a catalyst of the aftertreatment system 22 or determine a conversion value of a catalyst of the aftertreatment system 22. The controller 100 may receive the indication after receiving an indication of a tank refill event. In some cases, the controller 100 may receive the indication before the tank refill event has occurred (e.g., periodically or continuously receive the indication), such that the reductant value may represent, for example, a pre-refill reductant value.

[0157] To receive the indication of the conversion value, the controller 100 may be configured to receive a first NOx value measured by a first sensor upstream of the catalyst (e.g., NOx sensor 12). The controller 100 may receive a second NOx value from a second sensor downstream of the catalyst (e.g., another NOx sensor 12). The controller 100 may determine the conversion value of the catalyst based on the first NOx value and the second NOx value, for example, based on a difference or ratio between the first NOx value and the second NOx value.

[0158] At process 506, the controller 100 is configured to receive an indication of a reductant characteristic of the reductant stored in the fluid tank. The reductant characteristic may correspond to or include at least one of a dosing flow rate or a reductant flow rate (e.g., a dosing rate). At least in part, the controller 100 is configured to use the reductant characteristic to determine an amount of reductant to be dosed into the aftertreatment system 22, such as based on at least one of a frequency, duration, or volume of dosing or an exhaust flow rate that carries or transports the reductant through the aftertreatment system 22.

[0159] In some implementations, to receive an indication of the reductant characteristic of the reductant, the controller 100 may control a reductant doser (e.g., doser 56) to selectively dose the reductant in the aftertreatment system 22 based at least on the NOx value measured by the NOx sensor 12 upstream of the catalyst. In this case, the controller 100 is configured to send a command including the reductant characteristic (e.g., the amount of reductant) to the reductant doser to initiate dosing. The controller 100 is configured to identify or determine the reductant characteristic of the reductant dosed in the aftertreatment system 22 based on the control / command to the reductant doser.

[0160] In process 508, the controller 100 is configured to determine the amount of reductant based on the reductant characteristics. For example, the amount of reductant can be included in the command from the controller 100 to the doser 56. The amount of reductant can be associated with the NOx value (e.g., the amount of NOx) output by the engine 21. For example, a greater amount of NOx produced by the engine 21 can reflect a greater amount of reductant dosing into the aftertreatment system 22. Similarly, the controller 100 is configured to determine the amount of ammonia based on the amount of reductant dosing into the aftertreatment system 22. Therefore, the controller 100 is configured to determine the amount of ammonia based on the reductant characteristics.

[0161] In process 510, the controller 100 is configured to receive a value regarding the amount of ammonia relative to the NOx value. In some cases, receiving the value may refer to determining the value. For example, the controller 100 is configured to determine a value regarding the amount of ammonia relative to the NOx value based on or corresponding to the ratio between the amount of ammonia and the NOx value measured from the first sensor upstream of the catalyst. In this example, the ratio (corresponding to the value) may be an ANR for calculating the reductant value. For simplicity and for purposes of illustration, the value (or ratio) may be an ANR, although other types of values ​​indicating the amount of ammonia relative to the amount of NOx may be used herein.

[0162] In process 512, the controller 100 is configured to determine a reductant value. The controller 100 may determine the reductant value based on the conversion value and a value (e.g., ANR) about the amount of ammonia relative to the NOx value. The reductant value may include or correspond to the reductant concentration of the reductant stored in the fluid tank (e.g., the reductant source 54). The controller 100 is configured to calculate the reductant value, for example, at least by dividing the conversion value by the ANR. The controller 100 is configured to process noise factors before performing the calculation of the reductant value.

[0163] In various implementations, the controller 100 is configured to determine or calculate a reductant value (e.g., a first reductant value) at a first time instance within a time window of a moving time window. The controller 100 may receive an indication of a second conversion value of a catalyst of the aftertreatment system at a second time instance. The controller 100 may receive a second value about the amount of ammonia relative to the NOx value at a second time instance. Based on the second conversion value and the second value about the amount of ammonia relative to the NOx value, the controller 100 is configured to determine a second reductant value at a second time instance. The second time instance may be in the same time window as the first time instance or in a different time window. In this case, the second reductant value represents, for example, another data point corresponding to the reductant concentration.

[0164] The controller 100 is configured to perform a moving time window calculation on a plurality of data points (e.g., a certain number of calculated reductant concentrations). For example, the controller 100 may detect an amount of ammonia or an amount of NOx measured downstream of the catalyst that is greater than or equal to a threshold, the amount of ammonia or the amount of NOx representing ammonia slip or NOx slip, respectively. In response to the detection, the controller 100 is configured to aggregate a first reductant value, a second reductant value, and other reductant values ​​over a duration (e.g., a window) including various time instances. Aggregating reductant values ​​may include determining an average, mean, median, or other data accumulation techniques.

[0165] In some implementations, the aggregated reductant value can be a reductant value used as an output by the controller 100, as discussed herein. In some cases, the determination of the reductant value is performed at least a predetermined duration after identification of a fluid tank refill event. For example, after detecting a tank refill event, the controller 100 is configured to perform the calculation (determine the reductant value) after a predetermined duration from the detection period.

[0166] In some implementations, the controller 100 may perform or abort the determination of the reductant value based on whether at least one of the catalyst temperature or the reductant characteristic meets a threshold. For example, if at least one of the catalyst temperature (e.g., the bed temperature of the SCR catalyst 50) or the reductant characteristic (e.g., the reductant flow rate) does not meet their respective thresholds, the controller 100 is configured to abort the operation for performing the reductant value calculation or determination. If at least one of the catalyst temperature or the reductant characteristic meets the corresponding threshold, the controller 100 may perform the determination. In some other cases, the controller 100 is configured to perform the determination when two conditions (e.g., temperature and reductant characteristic) meet their respective thresholds.

[0167] In process 514, the controller 100 is configured to output an indication of a reductant value. The reductant value to be output may be individual data points calculated in response to receiving or determining the conversion value and the ANR. In some cases, the reductant value to be output may be an aggregated / accumulated reductant value performed using a moving time window (e.g., a moving power window calculation technique). Thus, in response to the determination of the reductant value, the controller 100 is configured to output an indication of the reductant value for display, such as via the operator I / O device 120, and other devices of an operator, service entity, or administrator.

[0168] It should be understood that any claim element herein cannot be interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the phrase "device for ... " is used to expressly describe the element. The above-mentioned schematic flow chart and method schematic diagram are usually described as logical flow charts. Therefore, the depicted order and marked steps indicate representative embodiments. Other steps, sequences and methods that are equivalent to one or more steps or parts thereof of the method shown in the schematic diagram in function, logic or effect can be envisioned. In addition, reference to "one embodiment", "embodiment", "example embodiment" or similar language throughout the specification means that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present invention. Therefore, the phrases "in one embodiment", "in an embodiment", "in an example embodiment" and similar language throughout this specification may, but not necessarily, refer to the same embodiment.

[0169] In addition, the format and symbols adopted are provided to explain the logical steps of the schematic diagram, and are understood to not limit the scope of the method shown by the schematic diagram. Although various arrow types and line types can be adopted in the schematic diagram, they are understood to not limit the scope of the corresponding method. In fact, some arrows or other connectors can only be used to indicate the logical flow of the method. For example, an arrow can indicate a waiting or monitoring cycle of unspecified duration between the enumerated steps of the method shown. In addition, the order in which a particular method occurs may or may not strictly comply with the order of the corresponding steps shown. In addition, various steps can be included or omitted from the described method or process, and still fall within the scope of the present disclosure.

[0170] Many of the functional units described in this specification are labeled as circuits in order to more particularly emphasize their implementation independence. For example, the circuits may be implemented as hardware circuits, including custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The circuits may also be implemented in programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0171] As described above, circuits may also be implemented in a machine-readable medium for use by, for example, Figure 2The identified circuit of the executable code may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, processes, or functions. However, the executable file of the identified circuit does not need to be physically located together, but may include different instructions stored in different locations, which, when logically connected together, constitute the circuit and achieve the purpose of the circuit. In fact, the circuit of the computer readable program code may be a single instruction or multiple instructions, and may even be distributed over several different code segments, between different programs, and across several memory devices. Similarly, operating data may be identified and shown in the circuit herein, and may be embodied in any suitable form and organized in any suitable type of data structure. Operating data may be collected as a single data set, or may be distributed over different locations, including different storage devices, and may exist in a system or network at least in part only as electronic signals.

[0172] A computer-readable medium (also referred to herein as a machine-readable medium or machine-readable content) may be a tangible computer-readable storage medium storing computer-readable program code. A computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, device or apparatus, or any suitable combination of the foregoing. As described above, examples of computer-readable storage media may include, but are not limited to, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that may contain and / or store a computer-readable program code used by and / or associated with an instruction execution system, device or apparatus.

[0173] Computer-readable media may also be computer-readable signal media. A computer-readable signal medium may include a propagation data signal having a computer-readable program code contained therein, for example, in baseband or as part of a carrier wave. Such propagation signals may take any of a variety of forms, including but not limited to electrical, electromagnetic, magnetic, optical, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium that is not a computer-readable storage medium, and may transmit, propagate, or transmit computer-readable program code for use by an instruction execution system, device, or equipment or in combination with an instruction execution system, device, or equipment. In addition, as described above, the computer-readable program code embodied in a computer-readable signal medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the foregoing. In one embodiment, a computer-readable medium may include a combination of one or more computer-readable storage media and one or more computer-readable signal media. For example, a computer-readable program code may be transmitted as an electromagnetic signal through an optical fiber cable for execution by a processor, or may be stored on a RAM storage device for execution by a processor.

[0174] The computer readable program code for performing the operations of various aspects of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, etc., and traditional procedural programming languages ​​such as the "C" programming language or similar programming languages. The computer readable program code may be executed entirely on the user's computer (e.g., by Figure 1 and Figure 2 The controller 100 of the present invention may be executed partially on the user's computer, as a separate computer-readable package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0175] The program code may also be stored in a computer-readable medium, which may direct a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the computer-readable medium produce an article of manufacture including instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram block or multiple blocks.

[0176] Therefore, the present disclosure may be implemented in other specific forms without departing from its spirit or essential characteristics. The described embodiments are considered to be illustrative in all respects only and not restrictive. Therefore, the scope of the present disclosure is indicated by the appended claims rather than by the foregoing description. All changes within the equivalent meaning and scope of the claims should be included within their scope.

Claims

1. A computing system comprising: at least one processing circuit comprising one or more memory devices coupled to the one or more processors, the one or more memory devices being configured to store instructions that, when executed by the one or more processors, cause the processing circuit to: receiving an indication of a fluid tank refill event; receiving an indication of a conversion value of a catalyst of an aftertreatment system after receiving an indication of a refill event of the fluid tank; receiving an indication of a reductant property of a reductant stored in a fluid tank; determining an amount of ammonia based on a reducing agent characteristic of the reducing agent; receiving a value regarding the amount of ammonia relative to a NOx value; determining a reductant value based on the converted value and a value regarding the amount of ammonia relative to the NOx value; as well as In response to the determination of the reductant value, an indication of the reductant value is output for display.

2. The computing system of claim 1, wherein: To receive an indication of the conversion value of the catalyst, the instructions, when executed by the one or more processors, further cause the at least one processing circuit to: receiving a first NOx value from a first sensor upstream of the catalyst of the aftertreatment system; receiving a second NOx value from a second sensor downstream of the catalyst of the aftertreatment system; as well as A conversion value for the catalyst is determined based on the first NOx value and the second NOx value.

3. The computing system of claim 2, wherein: The value for the amount of ammonia relative to the NOx value corresponds to the ratio between the amount of ammonia and the first NOx value from the first sensor upstream of the catalyst.

4. The computing system of claim 1, wherein: The reductant characteristic includes at least one of a dosing flow rate or a reductant flow rate.

5. The computing system of claim 1, wherein: To receive an indication of a reductant property of the reductant, the instructions, when executed by the one or more processors, further cause the at least one processing circuit to: controlling a reductant doser to selectively dose the reductant in the aftertreatment system based at least on the NOx value measured by a NOx sensor upstream of the catalyst; and Based on the control of the reductant doser, a reductant characteristic of the reductant dosed in the aftertreatment system is determined.

6. The computing system of claim 1, wherein: The reductant value is determined at a first time instance, wherein the reductant value is a first reductant value, and wherein the instructions, when executed by the one or more processors, further cause the at least one processing circuit to: receiving, at a second time instance, an indication of a second conversion value of a catalyst of the aftertreatment system; receiving, at the second time instance, a second value regarding the amount of ammonia relative to the NOx value; as well as A second reductant value is determined based on the second converted value and the second value regarding the amount of ammonia relative to the NOx value at the second time instance.

7. The computing system of claim 6, wherein: The instructions, when executed by the one or more processors, further cause the at least one processing circuit to: detecting that one of an amount of ammonia or an amount of NOx measured downstream of the catalyst is greater than or equal to a threshold; and In response to the detecting, at least the determined first reductant value and the determined second reductant value are aggregated over a time duration including a plurality of time instances.

8. The computing system of claim 1, wherein: The determination of the reductant value is performed at least a predetermined duration after identification of the fluid tank refill event.

9. The computing system of claim 1, wherein: The fluid tank refill event indicates a refill of a tank storing the reductant, and wherein to identify the fluid tank refill event, the instructions, when executed by the one or more processors, cause the at least one processing circuit to: determining a first amount of the reductant stored in the fluid tank prior to an engine idling event; determining a second amount of the reductant stored in the fluid tank after the engine idling event; and The fluid tank refill event is identified in response to a difference between the second amount of reductant and the first amount of reductant being greater than or equal to a threshold.

10. The computing system of claim 1, wherein: Prior to determining the conversion value or the value regarding the amount of ammonia relative to the NOx value, the instructions, when executed by the one or more processors, further cause the at least one processing circuit to: identifying at least one noise factor affecting the aftertreatment system; and At least one action is initiated in response to identifying the at least one noise factor affecting the aftertreatment system.

11. The computing system of claim 10, wherein: The at least one noise factor corresponds to an accuracy of a NOx sensor upstream or downstream of the catalyst, and wherein to initiate the at least one action, the instructions, when executed by the one or more processors, cause the at least one processing circuit to: calculating a virtual NOx value upstream or downstream of the catalyst using a model based on one or more operating characteristics of the engine, wherein the virtual NOx value is upstream or downstream of the catalyst based on a location of the NOx sensor; determining a value regarding a difference between the virtual NOx value and the NOx value measured by the NOx sensor; as well as Based on whether a value regarding a difference between the virtual NOx value and the NOx value measured by the NOx sensor satisfies a threshold, a plurality of values ​​from one of the model or the NOx sensor are used.

12. The computing system of claim 10, wherein: The at least one noise factor corresponds to aging of the catalyst, and wherein to initiate the at least one action, the instructions, when executed by the one or more processors, cause the at least one processing circuit to: comparing the converted value to a threshold value; as well as In response to the converted value being less than the threshold, a regeneration event of the catalyst is initiated.

13. The computing system of claim 10, wherein: The at least one noise factor corresponds to a limitation in the catalyst, and wherein to initiate the at least one action, the instructions, when executed by the one or more processors, cause the processing circuit to: receiving, from a sensor, a value indicative of a first flow rate measured at or upstream of the catalyst; determining a second flow rate based on one or more operating conditions of the engine; as well as In response to a difference between the first flow rate and the second flow rate being greater than or equal to a threshold, a regeneration event of the catalyst is initiated.

14. The computing system of claim 1, wherein: The instructions, when executed by the one or more processors, further cause the processing circuitry to: Determining the reducing agent value according to at least one of the temperature of the catalyst or the reducing agent characteristic satisfying a threshold; or Determination of the reducing agent value is aborted in response to at least one of the temperature of the catalytic converter or the reducing agent property not satisfying a threshold value.

15. A method comprising: receiving, by a processing circuit including one or more memory devices coupled to one or more processors, an indication of a fluid tank refill event; receiving, by the processing circuit, an indication of a conversion value of a catalyst of an aftertreatment system after receiving an indication of the fluid tank refill event; receiving, by the processing circuit, an indication of a reductant characteristic of a reductant, the reductant being stored in a fluid tank; determining, by the processing circuit, an amount of ammonia based on the reductant characteristic; receiving, by the processing circuit, a value regarding the amount of ammonia relative to a NOx value; determining, by said processing circuitry, a reductant value based on said converted value and a value relating to said amount of ammonia relative to said NOx value; and In response to the determination of the reductant value, an indication of the reductant value is output by the processing circuit for display.

16. The method according to claim 15, wherein: Receiving an indication of the conversion value of the catalyst further comprises: receiving, by the processing circuit, a first NOx value from a first sensor upstream of the catalyst of the aftertreatment system; receiving, by the processing circuit, a second NOx value from a second sensor downstream of the catalyst of the aftertreatment system; and A conversion value for the catalyst is determined by the processing circuit based on the first NOx value and the second NOx value.

17. The method according to claim 16, wherein: The value for the amount of ammonia relative to the NOx value corresponds to the ratio between the amount of ammonia and the first NOx value from the first sensor upstream of the catalyst.

18. A processing circuit comprising: one or more processors; as well as one or more memory devices coupled to the one or more processors, the one or more memory devices storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving an indication of a fluid tank refill event; receiving an indication of a conversion value of a catalyst of an aftertreatment system after receiving an indication of a refill event of the fluid tank; receiving an indication of a reductant property of a reductant stored in a fluid tank; determining an amount of ammonia based on the reducing agent characteristics; receiving a value regarding the amount of ammonia relative to a NOx value; determining a reductant value based on the converted value and a value regarding the amount of ammonia relative to the NOx value; as well as In response to the determination of the reductant value, an indication of the reductant value is output for display.

19. The processing circuit according to claim 18, wherein: The reductant characteristic includes at least one of a dosing flow rate or a reductant flow rate.

20. The processing circuit of claim 18, wherein: To receive an indication of a reductant property of the reductant, the instructions, when executed by the one or more processors, further cause the processing circuit to: controlling a reductant doser to selectively dose the reductant in the aftertreatment system based at least on the NOx value measured by a NOx sensor upstream of the catalyst; and Based on the control of the reductant doser, a reductant characteristic of the reductant dosed in the aftertreatment system is determined.