Systems and methods for selectively enabling regeneration of exhaust aftertreatment system components

Abstract

A system includes a controller coupled to an aftertreatment system. The controller is configured to identify a request for a regeneration process associated with a component of the aftertreatment system based on receiving input at an operator input device or receiving data about the aftertreatment system from a sensor. The controller is configured to receive a latched state from the memory device. The controller is configured to receive a time value from the memory device in response to the latched state being a first latched state. The controller is configured to, in response to the time value being at or above a threshold, modify the latched state to a second latched state such that the regeneration process is enabled. The controller is configured to prevent the regeneration process in response to the time value being below the threshold.

Description

Technical Field

[0001] This disclosure relates to selectively enabling the regeneration of exhaust aftertreatment system components. Background Technology

[0002] Many engines are coupled to exhaust aftertreatment systems that reduce harmful emissions such as nitrogen oxides (NOx), sulfur oxides, particulate matter, etc. Components of the exhaust aftertreatment system (such as particulate filters) may require regeneration to remove deposits (such as particulate matter) from the component. Regeneration of this component may require changes to the operation of the engine, the aftertreatment system, or both. Summary of the Invention

[0003] One embodiment relates to a system. The system includes a controller coupled to an aftertreatment system in exhaust gas receiving communication with an engine. The controller includes at least one processor and at least one memory device storing instructions therein that, when executed by the at least one processor, cause the controller to perform operations. The operations include: identifying a request for a regeneration process associated with a component of the aftertreatment system based on at least one of receiving input at an operator input device or receiving operational data about the aftertreatment system from one or more sensors; receiving from the at least one memory device a latch state associated with an operator interface device, the latch state including one of a first latch state or a second latch state; receiving a time value associated with user input from the at least one memory device in response to the latch state being the first latch state; modifying the latch state to the second latch state in response to the time value being at or above a predetermined threshold, such that the regeneration process is enabled in response to receiving the request for the regeneration process; blocking the regeneration process in response to the time value being below the predetermined threshold; and setting the time value to a predetermined value in response to the latch state being the second latch state.

[0004] In some embodiments, the user input is a first user input. In some embodiments, receiving the latch state associated with the operator interface device is in response to: receiving the first user input at the operator interface device; and in response to receiving the first user input at the operator interface device, receiving a first signal from the operator interface device, the first signal indicating that the latch state is the first latch state.

[0005] In some embodiments, the time value is set to the predetermined value in response to the latching state being the second latching state in response to: receiving the second user input at the operator interface device after receiving the first user input and before the time value is at or above the predetermined threshold; and receiving a second signal from the operator interface device in response to receiving the second user input at the operator interface device, the second signal indicating that the latching state is the second latching state.

[0006] In some embodiments, when executed by the at least one processor, the instruction causes the controller to perform further operations, the further operations including: determining a power state based on information received from at least one sensor associated with the engine indicating a power state associated with the engine, the power state including one of a first power state or a second power state; receiving a latched state from the at least one memory device in response to the power state being the first power state; and modifying the latched state to the second latched state in response to the power state being the second power state.

[0007] In some embodiments, when executed by the at least one processor, the instruction causes the controller to perform further operations, the further operations including setting the time value to the predetermined value in response to a change in the power state from the first power state to the second power state.

[0008] In some embodiments, when executed by the at least one processor, the instruction causes the controller to perform further operations, the further operations including: receiving an operational value from the one or more sensors regarding the operating conditions of at least one of the aftertreatment system or the engine in response to the latching state being the second latching state; implementing the regeneration process in response to the operational value being at or above the predetermined threshold; and preventing the regeneration process in response to the operational value being below the predetermined threshold.

[0009] In some embodiments, the time value is the amount of time between the current time value and the previous time value corresponding to the user input. In some embodiments, the predetermined threshold is a calibrable value. In some embodiments, the regeneration process is an active regeneration process. In some embodiments, the predetermined value is zero.

[0010] Another embodiment relates to a method. The method includes: identifying a request for a regeneration process based on at least one of receiving input at an operator interface device or receiving operational data about the post-processing system from one or more sensors; receiving a latch state associated with the operator interface device from the at least one memory device, the latch state including one of a first latch state or a second latch state; receiving a time value associated with user input from the at least one memory device in response to the latch state being the first latch state; modifying the latch state to the second latch state in response to the time value being at or above a predetermined threshold, such that the regeneration process is enabled in response to receiving the request for the regeneration process; blocking the regeneration process in response to the time value being below the predetermined threshold; and setting the time value to a predetermined value in response to the latch state being the second latch state.

[0011] In some embodiments, the user input is a first user input. In some embodiments, the method further includes: receiving the first user input at the operator interface device; and in response to receiving the first user input at the operator interface device, receiving a first signal from the operator interface device, the first signal indicating that the latching state is the first latching state, wherein receiving the latching state is based on receiving the first signal.

[0012] In some embodiments, the method further includes: receiving a second user input at the operator interface device after receiving the first user input and before the time value is at or above the predetermined threshold; and receiving a second signal from the operator interface device in response to receiving the second user input at the operator interface device, the second signal indicating that the latching state is the second latching state, wherein the time value is set to the predetermined value in response to receiving the second signal.

[0013] In some embodiments, the method further includes: determining a power state based on receiving information indicating a power state associated with the engine from at least one sensor associated with the engine, the power state including one of a first power state or a second power state; receiving a latched state from the at least one memory device in response to the power state being the first power state; and modifying the latched state to the second latched state in response to the power state being the second power state. In some embodiments, the method further includes: setting a time value to the predetermined value in response to the power state changing from the first power state to the second power state. In some embodiments, the method further includes: receiving an operational value from the one or more sensors regarding operating conditions of at least one of the aftertreatment system or an engine coupled to the aftertreatment system in response to the latched state being the second latched state; implementing the regeneration process in response to the operational value being at or above the predetermined threshold; and preventing the regeneration process in response to the operational value being below the predetermined threshold. In some embodiments, the operational value includes at least one of the following: a component temperature value regarding a component of the aftertreatment system; an exhaust gas temperature value regarding exhaust gases emitted by the engine; or a speed value regarding the speed of the engine.

[0014] Another embodiment relates to an apparatus. The apparatus includes at least one processor and at least one memory device storing instructions therein that, when executed by the at least one processor, cause the at least one processor to perform operations. The operations include: identifying a request for a regeneration process based on at least one of receiving input at an operator input device or receiving operational data about the post-processing system from one or more sensors; receiving from the at least one memory device a latch state associated with an operator interface device, the latch state including one of a first latch state or a second latch state; receiving, in response to the latch state being the first latch state, a time value associated with user input from the at least one memory device; modifying the latch state to the second latch state in response to the time value being at or above a predetermined threshold, such that the regeneration process is enabled in response to receiving the request for the regeneration process; blocking the regeneration process in response to the time value being below the predetermined threshold; and setting the time value to a predetermined value in response to the latch state being the second latch state.

[0015] In some embodiments, the user input is a first user input. In some embodiments, the instruction, when executed by the at least one processor, causes the at least one processor to perform further operations, the further operations including: receiving the first user input at the operator interface device; and in response to receiving the first user input at the operator interface device, receiving a first signal from the operator interface device, the first signal indicating that the latch state is the first latch state, wherein receiving the latch state is based on receiving the first signal.

[0016] In some embodiments, the instruction, when executed by the at least one processor, causes the at least one processor to perform further operations, the further operations including: receiving a second user input at the operator interface device after receiving the first user input and before the time value is at or above the predetermined threshold; and receiving a second signal from the operator interface device in response to receiving the second user input at the operator interface device, the second signal indicating that the latching state is the second latching state, wherein the time value is set to the predetermined value in response to receiving the second signal.

[0017] In some embodiments, the instruction, when executed by the at least one processor, causes the at least one processor to perform further operations, the further operations including: determining a power state based on receiving information indicating a power state associated with the engine from at least one sensor associated with the engine, the engine power state including one of a first power state or a second power state; receiving a latched state from the at least one memory device in response to the power state being the first power state; modifying the latched state to the second latched state in response to the power state being the second power state; and setting a time value to the predetermined value in response to the power state changing from the first power state to the second power state.

[0018] Numerous specific details are provided to fully understand embodiments of the subject matter of this disclosure. The features described in this disclosure may be combined in any suitable manner in one or more embodiments and / or implementations. In this regard, one or more features of one aspect of the invention may be combined with one or more features of different aspects of the invention. Furthermore, additional features may be recognized in some embodiments and / or implementations but are not present in all embodiments or implementations. Attached Figure Description

[0019] Figure 1 This is a schematic diagram of a transportation system according to an example embodiment.

[0020] Figure 2 According to the example embodiment Figure 1 Block diagram of the controller.

[0021] Figure 3 Selective enabling according to the example embodiment Figure 1 A flowchart of a method for the regeneration process in an exhaust aftertreatment system. Detailed Implementation

[0022] The following is a more detailed description of various concepts and implementations of methods, apparatus, computer-readable media, and systems for selectively enabling the regeneration of components of an exhaust aftertreatment system. Before the accompanying drawings, which illustrate certain exemplary embodiments in detail, it should be understood that this disclosure is not limited to the details or methodologies set forth in the specification or illustrated in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered limiting.

[0023] As used herein, the term "operational data" and similar terms are used to refer to data relating to the operation of a system or component, such as an engine system or a component thereof. In some embodiments, operational data may include settings, values, or other information relating to the operation of the system. In some embodiments, operational data may be measured (e.g., by one or more physical sensors) and / or may be estimated or determined (e.g., by one or more virtual sensors, or by a computer device or processing circuitry).

[0024] As described herein, an engine system may include an engine and an exhaust aftertreatment system, the exhaust aftertreatment system being in exhaust gas receiving communication with the engine. The engine may be an internal combustion engine (ICE) configured to burn fuel. The exhaust aftertreatment system may include one or more components, such as a particulate filter configured to remove particulate matter (such as soot) from exhaust gas flowing in an exhaust duct system, a metering module (e.g., a meterer) configured to supply a metered fluid to the exhaust gas flowing in the exhaust system, and components configured to facilitate the removal of exhaust gas components (e.g., nitrogen oxides, NOx). x One or more catalytic devices that convert elements into less harmful elements (e.g., water, nitrogen), such as oxidation catalysts, selective catalytic reduction (SCR) systems, three-way catalysts, etc.

[0025] Over time, particulate matter may accumulate on the particulate filter, reducing its effectiveness (e.g., decreasing its ability to remove particulate matter from exhaust gas). The control system can activate a "regeneration process" whereby the temperature of the exhaust gas (e.g., exhaust gas temperature) increases to or above a predetermined threshold. When the exhaust gas temperature is at or above the predetermined threshold, at least a portion of the particulate matter accumulated on the particulate filter is burned off, thereby reducing the amount of particulate matter on the filter. Active regeneration occurs via specific commands designed to regenerate the aftertreatment system or its components (e.g., commanding high power output, activating the electric heater, commanding fuel to be supplied to the oxidation catalyst upstream of the particulate filter so that the fuel is oxidized by the oxidation catalyst, etc.). For example, active regeneration is triggered by user input (via operator I / O devices) and / or automatically commanded by the controller in various operational instances, such as during prolonged idling (e.g., at rest stops, etc.). Passive regeneration may be triggered by system operation that causes the aftertreatment system temperature to rise (e.g., high-load operating conditions resulting in high exhaust gas temperatures that regenerate components). In this way, active regeneration requires specific commands, while passive regeneration does not.

[0026] The control system or controller can facilitate the regeneration process by, for example, generating and providing commands to implement the regeneration process (in this case, the active regeneration process). Operator input / output devices coupled to the controller may include at least one operator interface device, such as a button, momentary switch, etc. In this way, the operator interface device refers to the component and / or system that interfaces with the operator of system 100. In response to receiving input through the operator interface device, the controller can disable the active regeneration process (e.g., by preventing the active regeneration process from being triggered by commands generated and / or provided by the user through the operator interface device and / or automatically generated and / or provided by the controller (e.g., without user input)). When the active regeneration process is disabled, the operation of the engine and / or exhaust aftertreatment system does not change because, for example, no specific commands are generated or provided for changing the operation of the engine and / or exhaust aftertreatment system. However, the particulate filter may continue to accumulate particulate matter, thereby reducing the performance of the particulate filter (e.g., increasing the pressure drop across the particulate filter, reducing the amount of particulate matter removed from the exhaust gas per unit time or unit volume of exhaust gas, etc.).

[0027] As described herein, a control system or controller can implement one or more controls to automatically reactivate the active regeneration process. As described herein, a control system can, in response to the deactivation of the active regeneration process, implement one or more controls to automatically reactivate the active regeneration process after at least one predefined condition is met.

[0028] In one example, the control system can reactivate the active regeneration process after a predetermined amount of time. For instance, the control system can determine that the time value associated with user input at the operator interface device is at or above a predefined threshold. That is, the control system can determine that the amount of time (e.g., the "time value") since the user input was received at the operator interface device is at or above the predefined threshold. The control system can reset the time value in response to receiving a second user input at the operator interface device. In this way, subsequent user input at the operator interface device (e.g., a third user input) causes the active regeneration process to be disabled again. When the third user input disables the active regeneration process, the regeneration process is disabled for a period of time at or below the predetermined amount of time.

[0029] In another example, the control system may reactivate the active regeneration process in response to receiving and / or determining a “power state” associated with the engine. In one embodiment, a “power state” includes either a first power state or a second power state. The first power state is the engine being “on”, in which the engine is consuming fuel (e.g., idling, generating mechanical power, etc.). The second power state is the engine being “off”, in which the engine is not consuming fuel. In some embodiments, the power state is received via user input at a power device associated with the engine (such as a keyless ignition system, keyless ignition, etc.). For example, a user may insert a key into a keyless ignition switch and turn the key in a first direction to change the power state from the second power state (e.g., off) to the first power state (e.g., on). The user may then turn the key in a second direction to change the power state from the first power state (e.g., on) to the second power state (e.g., off). In some embodiments, the control system may receive the power state in response to a change from the first power state to the second power state. Advantageously, the control system can reset the time value in response to receiving an indication that the power state has changed from a first power state to a second power state, such that subsequent user input at the operator interface device causes the regeneration process to be disabled for a predetermined amount of time.

[0030] Technically and advantageously, the systems and methods described herein relate to automatically enabling a regeneration process after a user (e.g., a vehicle operator) has disabled it. That is, the systems and methods described herein provide a technical solution to at least the technical problem of automatically (e.g., without user input) re-enabling a regeneration process after a user has disabled it. Specifically, this technical solution includes a controller receiving a latch state associated with an operator interface device. This latch state is a first latch state (e.g., "on") or a second latch state (e.g., "off"). When the latch state is the first latch state, the controller receives a time value associated with user input in response to the latch state being the first latch state. The controller can automatically modify the latch state to the second latch state in response to the time value being at or above a predetermined threshold, thereby enabling the regeneration process in response to a request for it. Advantageously, re-enabling the regeneration event can mitigate the undesirable accumulation of particulate matter (e.g., soot) within the post-processing system. In other words, if the regeneration event is not automatically reactivated, it will not occur without user input (e.g., a second user input setting the latch state to a second latch state), and particulate matter may accumulate, potentially leading to poor performance of the aftertreatment system and / or poor emission characteristics (e.g., NOx levels exceeding a predefined threshold). These features and benefits, as well as others, are described more fully below.

[0031] Now for reference Figure 1 The diagram illustrates a block diagram of a transportation system 100 according to an example embodiment. System 100 includes an engine 101 and an aftertreatment system 120, which is in exhaust gas receiving communication with the engine 101. System 100 may also include a controller 140 (e.g., Figure 2 (as shown) and operator input / output (I / O) devices (also as shown) Figure 2 As shown), the controller 140 is communicatively connected to each of the aforementioned components. Figure 1 In this configuration, system 100 is included in a vehicle. The vehicle can be any type of on-road or off-road vehicle, including but not limited to wheel loaders, forklifts, long-haul trucks, medium-haul trucks (e.g., pickup trucks), cars, sports cars, tanks, aircraft, boats, and any other type of vehicle. In another embodiment, system 100 may be embodied in fixed equipment, such as a generator or generator set. All such variations are intended to fall within the scope of this disclosure.

[0032] Engine 101 can be any type of internal combustion engine that produces exhaust gases, such as a gasoline engine, a natural gas engine, or a diesel engine and / or any other suitable engine. In the depicted example, engine 101 is part of a diesel engine system. In other embodiments, engine 101 is part of a hybrid engine system that combines an internal combustion engine and at least one electric motor coupled to at least one battery. In some embodiments, the hybrid engine system can be configured as a mild hybrid system, a parallel hybrid system, a series hybrid system, or a series-parallel hybrid system.

[0033] like Figure 1 As shown, an intake air throttle (IAT) valve 102, a fuel module 103, and an oil system 104 are connected to an engine 101. The IAT valve 102 is configured to control the amount of air supplied to the engine 101. The fuel module 103 is configured to supply fuel (e.g., from a fuel source) to the engine 101. The fuel module 103 can control one or more fueling parameters, including fuel quantity, fuel pressure, fuel injection timing, etc. The oil system 104 is configured to supply lubricant (e.g., lubricating oil) to the engine 101.

[0034] IAT valve 102 is a valve located at the air intake of engine 101. IAT valve 102 can be actuated between an open position and a closed position (e.g., by an actuator controlled by controller 140). In the open position, IAT valve 102 allows the maximum amount of air to flow from the air intake to engine 101. In the closed position, IAT valve 102 allows the minimum amount of air to flow from the air intake to engine 101. Controller 140 can selectively actuate IAT valve 102 (e.g., by controlling an actuator) between and / or in multiple positions including open and closed positions to regulate the amount of air received by engine 101.

[0035] The aftertreatment system 120 is in exhaust gas receiving communication with the engine 101. In the depicted example, the aftertreatment system includes a first catalyst component (shown as diesel oxidation catalyst (DOC) 121), a filter (e.g., a particulate filter) (shown as diesel particulate filter (DPF) 122), and a second catalyst component (shown as selective catalytic reduction (SCR) system 123). In some embodiments, the aftertreatment system 120 includes a third catalyst component (shown as ammonia leak catalyst (ASC) 128). DOC 121, DPF 122, and SCR 123 can be fluidly connected via an exhaust gas duct. DOC 121 is configured to receive exhaust gas from the engine 110 and oxidize one or more exhaust gas components (e.g., hydrocarbons, carbon monoxide, etc.) in the exhaust gas. DPF 122 is arranged or positioned downstream of DOC 121 and is configured to remove particulate matter (such as soot) from the exhaust gas flowing in the exhaust gas stream. The DPF 122 includes an inlet and an outlet, where exhaust gas is received and discharged after substantially filtering particulate matter from the exhaust gas. In some implementations, the DPF 122 or other components may be omitted, and / or other components may be added (e.g., a second SCR system with additional metering units or modules, multiple DOCs, etc.). Furthermore, although... Figure 1 The diagram shows a specific arrangement of the post-processing system 120, but the arrangement of components within the post-processing system 120 may be different in other embodiments (e.g., DPF 122 is located downstream of SCR 123 and ASC).

[0036] The aftertreatment system 120 may also include a reducing agent delivery system, which may include a decomposition chamber (e.g., a decomposition reactor, reactor piping, decomposition tube, reactor tube, etc.) to convert the reducing agent into ammonia, shown as a metering module or unit 124. The reducing agent may be, for example, urea, diesel exhaust fluid (DEF). Urea aqueous solution (UWS), water-soluble urea solution (e.g., AUS32, etc.), and other similar liquids. The metering module 124 may include a reservoir, a pump, and a nozzle (and potentially other components or devices). The reservoir may be configured to store the reducing agent. The pump may be fluidly coupled to the reservoir and the nozzle via a metering conduit and configured to pump the reducing agent from the reservoir to the nozzle. The nozzle may supply the reducing agent to the exhaust gas within the exhaust gas duct. Adding the reducing agent fluid to the exhaust gas stream aids in catalytic reduction. Figure 1As shown, the reducing agent can typically be injected upstream of the SCR 123 (or specifically, the SCR catalyst) via the metering module 124, causing the SCR catalyst to receive the mixture of the reducing agent and the exhaust gas. The reducing agent droplets then undergo evaporation, thermal decomposition, and decomposition processes to form gaseous ammonia within the decomposition chamber, the SCR catalyst, and / or the exhaust gas duct system, which exits the aftertreatment system 120.

[0037] DOC 121 is fluidly connected to an exhaust gas duct system to oxidize one or more gaseous components (e.g., hydrocarbons, carbon oxides, etc.) in the exhaust gas. To properly facilitate the oxidation of one or more gaseous components, DOC 121 may need to be at a specific operating temperature. In some embodiments, this specific operating temperature is approximately between 200 and 500°C. In other embodiments, this specific operating temperature is the temperature at which the conversion efficiency of DOC 121 exceeds a predefined threshold (e.g., the conversion of hydrocarbons to less harmful compounds, referred to as hydrocarbon conversion efficiency).

[0038] SCR 123 is configured to help reduce NOx emissions by accelerating the NOx reduction process between ammonia and NOx in exhaust gas, reducing it to diatomic nitrogen (N2) and water (H2O). If the SCR catalyst is not at or above a specific temperature, the acceleration of the NOx reduction process will be limited, and the SCR 123 may not operate at the desired conversion efficiency (i.e., a value indicating the amount of NOx emission reduction, also known as “NOx removal efficiency”). In some embodiments, this specific temperature is approximately 200–600°C. The SCR catalyst can be made from a combination of inactive materials and an active catalyst, such that the inactive material (e.g., a ceramic substrate) directs the exhaust gas to the active catalyst, which is any kind of material suitable for catalytic reduction (e.g., metal-exchanged zeolites (Fe or Cu / zeolite), base metal oxides such as vanadium, molybdenum, and tungsten).

[0039] When ammonia in the exhaust gas does not react with the SCR catalyst (because SCR 123 is below operating temperature, or because the amount of ammonia significantly exceeds the amount of NOR), unreacted ammonia may bind with the SCR catalyst and be stored in SCR 123. As SCR 123 heats up, this stored ammonia can be released from SCR 123, which can cause problems if the amount of ammonia released is greater than the amount of NOx flowing through (i.e., more ammonia than the amount of NOx required, which could lead to ammonia leakage). In some embodiments, ASC 128 is included and configured to address ammonia leakage by removing at least some of the excess ammonia from the treated exhaust gas before it is released into the atmosphere. As the exhaust gas flows through ASC 128, some of the remaining unreacted ammonia in the exhaust gas (i.e., unreacted with NOx) is partially oxidized to NOx, which then reacts with the remaining unreacted ammonia to form N2 gas and water. However, similar to SCR catalysts, the acceleration of the NH3 reduction process is limited if ASC 128 is not at or above a certain temperature, and ASC 128 may not be able to operate at the efficiency levels required by regulations or desired parameters. In some embodiments, this specific temperature is approximately 250-300°C.

[0040] As shown in the figure, multiple sensors 125 are included in the aftertreatment system 120. The number, arrangement, and type of sensors included in the aftertreatment system 120 are shown for illustrative purposes only. That is, in other configurations, the number, arrangement, and type of sensors may differ. Sensors 125 may be gas composition sensors (e.g., NOx sensors, oxygen sensors, etc.), temperature sensors, particulate matter (PM) sensors, flow sensors (e.g., mass flow sensors, volumetric flow sensors, etc.), other exhaust gas emission component sensors, pressure sensors, certain combinations thereof, etc. Gas composition sensors may include oxygen sensors configured to acquire data indicating the presence of oxygen in the exhaust gas. Data from the oxygen sensor can be used to estimate the AFR value. Flow sensors may include mass air flow (MAF) sensors configured to acquire data indicating the mass flow rate of the exhaust gas. Temperature sensors are configured to acquire data indicating the temperature value at each location where a temperature sensor is located.

[0041] Sensor 125 may be located in or near engine 101, after engine 101 and before aftertreatment system 120, after aftertreatment system 120, in the aftertreatment system as shown (e.g., connected to DPF and / or DOC, connected to SCR, etc.), upstream of engine 101, etc. It should be understood that the sensor location may vary. In one embodiment, sensor 125 may be present both before and after aftertreatment system 120. In one embodiment, at least one sensor is configured as an exhaust gas composition sensor (e.g., CO, NOx, PM, SOx, etc.). In another embodiment, at least one sensor of sensor 125 is configured as a non-exhaust gas composition sensor for estimating exhaust emissions (e.g., temperature, flow rate, pressure, etc.). Additional sensors may also be included in system 100. Sensors may include engine-related sensors (e.g., torque sensor, speed sensor, pressure sensor, flow sensor, temperature sensor, etc.). For example, in some embodiments, at least one sensor of sensor 125 is configured as an oil temperature sensor for detecting and / or determining engine oil temperature. Sensors may also include sensors associated with other components of the vehicle (e.g., speed sensors for turbochargers, fuel quantity and injection rate sensors, fuel rail pressure sensors, etc.).

[0042] Sensor 125 can be physical or virtual (i.e., a non-physical sensor configured as program logic in controller 140, performing various estimations or determinations). For example, an engine speed sensor can be a physical or virtual sensor arranged to measure or otherwise acquire data, values, or information indicating the speed of engine 101 (typically expressed in revolutions per minute). The sensor is coupled to the engine (when configured as a physical sensor) and configured to transmit a signal indicating the speed of engine 101 to controller 140. When configured as a virtual sensor, controller 140 can use at least one input in an algorithm, model, lookup table, etc., to determine or estimate engine parameters (e.g., power output, etc.). Any of the sensors 125 described herein can be physical or virtual.

[0043] The controller 140 is coupled to the sensor 125, and specifically communicatively coupled to the sensor. Therefore, the controller 140 is configured to receive data from one or more of the sensors 125 and to provide instructions / information to one or more of the sensors 125. The controller 140 can use the received data to control one or more components in the system 100, and / or for monitoring and thermal management purposes.

[0044] Operator input / output (I / O) device 130 can be coupled to controller 140, enabling the exchange of information between controller 140 and I / O device 130, wherein this information can be compared with... Figure 1 The determination of one or more components or controller 140 (described below) is related to this. Operator I / O device 130 enables the operator of system 100 to interact with controller 140 and... Figure 1 The system 100 communicates with one or more components. For example, operator input / output devices may include, but are not limited to, interactive displays, touchscreen devices, one or more buttons and switches, voice command receivers, etc. In this way, operator input / output device 130 can provide the operator with one or more instructions or notifications, such as fault indicator lights (MIL). Additionally, the vehicle may include a port that allows controller 140 to connect to or couple to the scanning tool so that fault codes and other information about the vehicle can be obtained.

[0045] In some embodiments, the operator I / O device 130 includes an operator interface device. In some embodiments, the operator interface device is a button or switch, such as a momentary switch. In other embodiments, the operator interface device is a graphical user interface or part thereof provided on the display of the operator I / O device 130. For example, the operator interface device may be an interactive icon or similar element of a graphical user interface, which a user can select via touch input or with another device, such as a keyboard or mouse. In some embodiments, the operator I / O device 130 includes processing circuitry that enables communication (e.g., wired and wireless connections) between the operator interface device and the controller 140.

[0046] The controller 140 is configured to at least partially control the operation of the system 100 and associated subsystems (such as the engine 101 and operator I / O device 130). Communication between components can be made via any number of wired or wireless connections. For example, wired connections may include serial cables, fiber optic cables, CAT5 cables, or any other form of wired connection. In contrast, wireless connections may include the Internet, Wi-Fi, cellular networks, radio, etc. In one embodiment, a controller local area network (CAN) bus provides the exchange of signals, information, and / or data. The CAN bus includes any number of wired and wireless connections. Because the controller 140 is communicatively coupled to... Figure 1 The system and components, therefore the controller 140 is constructed from Figure 1 One or more of the components shown receive data. The structure and function of controller 140 will be combined Figure 2 Further description.

[0047] because Figure 1The components are shown as being embodied in a vehicle, so the controller 140 can be configured as one or more electronic control units (ECUs), such as one or more microcontrollers. The controller 140 can be separate 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, etc.

[0048] Now for reference Figure 2 This illustrates an example embodiment. Figure 1 A schematic diagram of the controller 140 of system 100 is shown. As illustrated, controller 140 includes at least one processing circuit 202 having at least one processor 204 and at least one memory device 206, a regeneration management circuit 212, and a communication interface 216. Controller 140 is configured to selectively enable and / or disable the regeneration process (e.g., an active regeneration process). As described herein, enabling the regeneration process allows it to occur when certain conditions are met, such as exhaust gas temperature values ​​being at or above an exhaust gas temperature threshold, aftertreatment system component temperatures being at or above a component temperature threshold, engine speed values ​​being at or above a speed threshold, etc. Disabling the regeneration process prevents the regeneration process from occurring by, for example, preventing the operation of engine 101 and / or aftertreatment system 120 from being modified to achieve the operating conditions described above, such as preventing exhaust gas temperature values ​​from exceeding exhaust gas temperature thresholds, preventing aftertreatment system component temperatures from exceeding component temperature thresholds, preventing engine speed values ​​from exceeding speed thresholds, etc.

[0049] In one configuration, the regeneration management circuit 212 is embodied as a machine- or computer-readable medium storing instructions executable by a processor (such as processor 204). As described herein and for other uses, the machine-readable medium facilitates the execution of certain operations to achieve the reception and transmission of data. For example, the machine-readable medium can provide instructions (e.g., commands, etc.) to, for example, acquire data. In this respect, the machine-readable medium may include programmable logic defining the frequency of data acquisition (or data transmission). The computer-readable medium instructions may include code that can be written in any programming language, including but not limited to Java and any conventional procedural programming language, such as the "C" programming language or similar programming languages. The computer-readable program code can be executed on one processor or multiple remote processors. In the latter case, the remote processors can be connected to each other via any type of network (e.g., CAN bus, etc.).

[0050] In another configuration, the regenerative management circuit 212 is embodied as one or more hardware units, such as one or more electronic control units. Therefore, the regenerative management circuit 212 can be embodied as one or more circuit components, including but not limited to processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, the regenerative management circuit 212 can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-a-chip (SoC) circuits, microcontrollers, etc.), telecommunication circuits, hybrid circuits, and any other type of "circuit". In this respect, the regenerative management circuit 212 can include any type of component for performing or facilitating the implementation of the operations described herein. For example, the circuitry described herein can 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. The regenerative management circuit 212 can also include or be programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. The regeneration management circuit 212 may include one or more memory devices for storing instructions executable by a processor of the regeneration management circuit 212. The one or more memory devices and the processor may have the same definitions provided below with respect to memory device 206 and processor 204. In some hardware unit configurations, the regeneration management circuit 212 may be geographically distributed across various locations within the vehicle. Alternatively, and as shown, the regeneration management circuit 212 may be embodied in or within a single unit / housing, which is shown as controller 140.

[0051] In the example shown, controller 140 includes processing circuitry 202 having processor 204 and memory device 206. Processing circuitry 202 may be constructed or configured to execute or implement the instructions, commands, and / or control processes described herein with respect to regeneration management circuitry 212. The depicted configuration indicates that regeneration management circuitry 212 is embodied as a machine or computer-readable medium storing instructions. However, as mentioned above, this illustration is not intended to be limiting, as other embodiments of regeneration management circuitry 212 being configured as a hardware unit are contemplated in this disclosure. All such combinations and variations are intended to fall within the scope of this disclosure.

[0052] Processor 204 may be implemented as one or more single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and / or suitable processors (e.g., other programmable logic devices, discrete hardware components, etc.) to perform the functions described herein. The processor may be a microprocessor, a set of processors, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, one or more processors may be shared by multiple circuits (e.g., regeneration management circuitry 212 may include or otherwise share the same processor, which in some example embodiments may execute instructions stored or otherwise accessed via different regions of memory). Alternatively or additionally, one or more processors may be constructed to perform or otherwise perform certain operations independently of one or more coprocessors. In other example embodiments, two or more processors may be connected via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution. All such variations are intended to fall within the scope of this disclosure.

[0053] Memory device 206 (e.g., memory, memory cell, storage device) may include one or more means (e.g., RAM, ROM, flash memory, hard disk storage device) for storing data and / or computer code used to perform or facilitate the various processes, layers, and modules described herein. For example, memory device 206 may include dynamic random access memory (DRAM). Memory device 206 may be communicatively coupled to processor 204 to provide processor 204 with computer code or instructions for performing at least some of the processes described herein. Furthermore, memory device 206 may be or include tangible, non-transient volatile memory or non-volatile storage. Therefore, memory device 206 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein.

[0054] Communication interface 216 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 configured to enable in-vehicle communication (e.g., between vehicle components) and out-of-vehicle communication (e.g., using a remote server). For example, and regarding out-of-vehicle / system communication, communication interface 216 may include Ethernet cards and ports for transmitting and receiving data over Ethernet-based communication networks and / or Wi-Fi transceivers for communication over wireless communication networks. Communication interface 216 may be configured to communicate over local area networks or wide area networks (e.g., the Internet) and may use various communication protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, near-field communication).

[0055] In some embodiments, controller 140 and / or one or more components thereof (such as regeneration management circuitry 212) are configured to facilitate an active regeneration process. For example, controller 140 may generate one or more commands to increase the temperature of the exhaust gas (e.g., exhaust gas temperature) to or above a predetermined threshold. When the exhaust gas temperature is at or above the predetermined threshold, at least a portion of the particulate matter accumulated on DPF 122 is burned off, thereby reducing the amount of particulate matter on DPF 122. In some embodiments, one or more commands for facilitating the active regeneration process include causing engine 101 (and particularly the refueling system) to discharge a predetermined amount of fuel into aftertreatment system 120 via controller 140. DOC 121 may facilitate fuel oxidation. Fuel oxidation is an exothermic reaction that increases the temperature of the exhaust gas. In some embodiments, controller 140 may generate one or more commands to increase the engine speed of engine 101. Increased engine speed may result in higher combustion temperatures and thus higher exhaust gas temperatures. In some embodiments, controller 140 may enable a cylinder deactivation mode, thereby deactivating one or more combustion cylinders of engine 101. The remaining active cylinders of engine 101 may consume a greater amount of fuel to meet the power output required by engine 101. Higher fuel consumption leads to higher combustion temperatures, and therefore higher exhaust gas temperatures. In some embodiments, controller 140 may generate one or more commands to activate or increase the heat output of one or more heaters (e.g., electric heaters, ceramic heaters, etc.). In one example, one or more heaters are configured to heat exhaust gas (e.g., downstream of engine 101 and upstream of DPF 122), which may result in an increase in exhaust gas temperature. In another example, one or more heaters are configured to heat intake air (e.g., upstream of engine 101). The increased intake air temperature may result in higher combustion temperatures, and therefore higher exhaust gas temperatures. In other embodiments, one or more heaters may directly or indirectly heat components of the system, such as components of the aftertreatment system. Heated components may promote desired activities, such as the catalytic activity of SCR.

[0056] In some embodiments, controller 140 and / or one or more components thereof (such as regeneration management circuitry 212) are configured to facilitate the disabling of the active regeneration process. For example, controller 140 may receive user input via operator I / O device 130, or more specifically, via operator interface device. In some embodiments, controller 140 is configured to disable the regeneration process when user input is received at the operator interface device. When controller 140 disables the regeneration process, controller 140 may prevent the generation and implementation / execution of one or more commands described above, which represent a non-exhaustive list of regeneration commands. For example, controller 140 may prevent the generation of one or more commands for increasing the temperature of the exhaust gas.

[0057] In various embodiments, controller 140 and / or one or more components thereof (such as regeneration management circuitry 212) are configured to selectively enable or disable the active regeneration process. In some embodiments, controller 140 may disable the regeneration process in response to receiving a first user input at the operator interface device. Controller 140 may re-enable the regeneration process in response to receiving a second user input at the operator interface device. Advantageously, controller 140 is also configured to automatically (e.g., without user input) re-enable the regeneration process based on one or more predefined conditions. The process for automatically re-enabling the regeneration process is described in more detail herein.

[0058] In an example embodiment, controller 140 is configured to receive a request for a regeneration process. The regeneration process may be associated with components of post-processing system 120, such as DPF 122.

[0059] Controller 140 is configured to receive and / or determine latch states associated with components of operator I / O device 130, such as operator interface devices. A “latch” refers to a data element (e.g., discrete data or information). In some embodiments, a data element is a value, such as a binary value (e.g., 0 or 1). In other embodiments, a data element is a string (e.g., “on” or “off”, “true” or “false”) or other suitable data type. Therefore, a “latch state” can be a value indicating the state of a latch (in the case of a string, it can be a numeric, alphabetic, and / or alphanumeric value). For example, when a latch is provided as a binary value, the “latch state” can be 0 or 1. In another example, when a latch is provided as a string, the latch state can be “on” or “off”. The latch state can be stored and updated in memory 206 of controller 140.

[0060] In some embodiments, the latch state indicates the state or most recent state of the operator interface device. More specifically, the latch state may indicate whether the user has manipulated (e.g., pressed, toggled, selected, etc.) the operator interface device. For example, before the user interacts with the operator interface device, the latch state is "0" or "off". When the user interacts with the operator interface device, the latch state changes to "1" or "on" (when the latch state is constructed as a binary representation). Subsequent interactions with the operator interface device cause the latch state to change between "0" and "1" or "on" and "off". That is, the latch state changes in response to receiving user input at the operator interface device (e.g., from "0" to "1", or from "1" to "0"). Alternatively, and as described in more detail below, the controller 140 may change the latch state automatically.

[0061] In one embodiment, the latch state is received via operator I / O device 103 and provided to controller 140. The latch state may be retrievably stored in memory device 206, and controller 140 retrieves the latch state from memory device 206. The latch state includes either a first latch state or a second latch state.

[0062] The first latch state corresponds to the "on" state of a component of the operator interface device. The value of the latch corresponding to the first latch state can be "1" or "on". The latch state can be the first latch state when a first user input is received at the operator interface device. In the example embodiment, the first user input corresponds to a user activating the operator interface device to disable the active regeneration process. Therefore, when the latch state is the first latch state, the controller 140 can disable the regeneration process.

[0063] The second latch state includes the "off" state of a component of the operator interface device. The value of the latch corresponding to the second latch state can be "0" or "off". The latch state can be the second latch state when a second user input is received at the operator interface device, and / or when the controller 140 automatically sets the latch state to the second latch state. In an example embodiment, the second user input corresponds to a user deactivating the operator interface device to re-enable the active regeneration process. Additionally and / or alternatively, the controller 140 is configured to automatically set the latch state to the second latch state based on one or more predetermined conditions, which will be described in more detail below. Therefore, when the latch state is the first latch state, the controller 140 can disable the regeneration process.

[0064] In an example embodiment, controller 140 receives, retrieves, identifies, and / or otherwise determines the latch state in response to receiving either a first user input at the operator interface device or a second user input at the operator interface device. In another example embodiment, controller 140 receives, identifies, retrieves, and / or determines the latch state in response to receiving a different input, such as a “power state”. The power state will be described in more detail below.

[0065] Controller 140 is configured to receive, identify, or determine a time value associated with a first user input. The time value is the amount of time between the current time and a previous time value corresponding to the user input. In other words, the time value is the amount of time between the current time and the time when the first user input was received. For example, the time value can be measured in minutes and seconds. That is, the time value can be less than one hour, less than two hours, etc. The time value can be measured by one or more computer-implemented timing devices, such as clocks, stopwatches, timers, etc., which in some embodiments are embodied by virtual sensors 125. The time value can be stored in the memory device 206 of controller 140. In one embodiment, controller 140 can receive the time value in response to a latching state being a first latching state.

[0066] Controller 140 is configured to change the latch state from a first latch state to a second latch state in response to a time value being at or above a predetermined threshold. Controller 140 is also configured to prevent the active regeneration process in response to a time value being below a predetermined threshold. The predetermined threshold may be a calibrable threshold. For example, the predetermined threshold may be set by a user (such as the operator of system 100 or another user). For example, the predetermined threshold may be greater than one minute. Specifically, the predetermined threshold may be greater than one minute but less than one hour. For example, the predetermined threshold may be 30 minutes.

[0067] Controller 140 is configured to set a time value to a predetermined value in response to a latch state being a second latch state. For example, controller 140 may set the time value to a predetermined value in response to changing the latch state from a first latch state to a second latch state. In another example, controller 140 may set the time value to a predetermined value in response to receiving second user input at operator interface device 130 after receiving first user input and before the time value is at or above a predetermined threshold. In yet another example, controller 140 may set the time value to a predetermined value in response to receiving a second signal indicating that the latch state is a second latch state, the reception of which is in response to receiving second user input at operator interface device 130. The predetermined value may be, for example, zero minutes.

[0068] In some embodiments, controller 140 is configured to receive a power state associated with engine 101. As described above, the power state includes either a first power state or a second power state. In one embodiment, controller 140 receives information indicating the power state from one or more sensors 125. For example, the information indicating the power state may include an engine speed value received from a speed sensor associated with the engine or an engine torque value received from a torque sensor associated with the engine. When the engine speed or engine torque is zero, controller 140 may determine that the power state is a second power state (e.g., off). When the engine speed or engine torque is greater than zero, controller 140 may determine that the power state is a first power state (e.g., on). In these embodiments, controller 140 determines the power state based on the received information indicating the power state.

[0069] In another embodiment, information indicating the power state is received from the ignition system (e.g., keyed ignition, push-button ignition, etc.). For example, when the ignition system is activated (e.g., keyed on or otherwise activated), the controller 140 may determine that the power state is a first power state (e.g., on). When the ignition system is deactivated (e.g., keyed off or otherwise deactivated), the controller 140 may determine that the power state is a second power state (e.g., off).

[0070] In some embodiments, controller 140 is configured to receive a latched state in response to a first power state. For example, controller 140 may receive a latched state when system 100 is powered on. In some embodiments, controller 140 is configured to modify the latched state to a second latched state in response to a second power state. In some embodiments, controller 140 is configured to modify the latched state to a second latched state in response to a change in power state from a first power state to a second power state. For example, controller 140 may set the latched state to the second latched state when system 100 is powered off, and / or when system 100 changes from an on state to an off state.

[0071] In some embodiments, controller 140 is configured to set a time value to a predetermined value in response to a change in power state from a first power state to a second power state. For example, controller 140 may set the time value to the predetermined value when system 100 changes from an on state to an off state.

[0072] In some embodiments, controller 140 is configured to receive operational values ​​regarding operating conditions of at least one of the aftertreatment system 120 or engine 101 in response to a latching state being a second latching state. For example, controller 140 may receive one or more temperature values ​​regarding exhaust gases at or near engine 101 or in aftertreatment system 120. In another example, controller 140 may receive engine speed values ​​or other values ​​associated with the operation of engine 101. In yet another example, controller 140 may receive component temperatures regarding components of aftertreatment system 120.

[0073] In some embodiments, controller 140 is configured to initiate an active regeneration process in response to an operating value being at or above a predetermined threshold. For example, controller 140 may initiate an active regeneration process when one or more temperature values ​​are at or above a predetermined temperature threshold. In another example, controller 140 may initiate an active regeneration process when an engine speed value is at or above an engine speed threshold. In yet another example, controller 140 may initiate an active regeneration process when a component temperature value is at or above a component temperature threshold.

[0074] In some embodiments, controller 140 is configured to prevent the active regeneration process in response to an operating value falling below a predetermined threshold. For example, controller 140 may prevent the active regeneration process when one or more temperature values ​​fall below a predetermined temperature threshold. In another example, controller 140 may prevent the active regeneration process when an engine speed value falls below an engine speed threshold. In yet another example, controller 140 may prevent the active regeneration process when a component temperature value falls below a component temperature threshold.

[0075] Figure 3 This is a flowchart of a method 300 for selectively enabling a regeneration process according to an example embodiment. Specifically, a controller 140 and / or one or more components thereof (such as regeneration management circuitry 212) are configured to perform method 300. In some embodiments, one or more processes in method 300 are optional. For example, processes 340 and / or 342 are optional and may be omitted from method 300. In still other embodiments, one or more processes in the process may be combined with one or more other depicted processes, and furthermore, additional processes may be added to method 300 without departing from the spirit and scope of this disclosure.

[0076] At process 302, controller 140 receives or identifies a regeneration request. In some embodiments, controller 140 may receive or identify a regeneration request in response to, for example, a predefined time period since the most recent regeneration process (e.g., the most recent active regeneration process and / or the most recent passive regeneration process). In some embodiments, controller 140 may receive or identify a regeneration request in response to pressure changes on one or more components of the post-treatment system 120 (e.g., DOC 121 or DPF 122 being at or above a predetermined threshold) or another indicator of particulate matter accumulation in the post-treatment system (e.g., sensed flow rate being at or below a predefined threshold). In this way, controller 140 receives information indicating a regeneration request from sensor 125 (e.g., a pressure sensor, flow sensor, or other suitable sensor) and identifies the regeneration request based on operational data about the post-treatment system (e.g., pressure values, flow rates, etc.). In another embodiment, controller 140 identifies a regeneration request based on received user input (via I / O device 130).

[0077] At process 304, controller 140 receives user input. The user input may be received at operator interface device 130. In some embodiments, the user input is a first user input that sets the latch state to a first latch state. In some embodiments, the user input is a second user input that sets the latch state to a second latch state. The second user input may be received after the first user input.

[0078] At process 306, controller 140 receives a latch state. As described herein, the latch state may be a first latch state or a second latch state. In some embodiments, controller 140 receives the latch state in response to receiving user input at process 304. In some embodiments, controller 140 receives the latch state in response to receiving a power state and / or in response to executing process 330. In some embodiments, controller 140 receives, retrieves, or otherwise identifies and / or determines the latch state from memory device 206. In other embodiments, controller 140 receives the latch state from operator I / O device 130, or more specifically, from operator interface device (i.e., operator I / O device 130 may store the latch state itself).

[0079] At process 308, controller 140 identifies or determines whether the latching state is a first state (or receives an indication of it from, for example, a sensor). In some embodiments, controller 140 may determine whether the latching state is a first latching state in response to receiving a regeneration request at process 302. In response to the latching state being a first latching state, controller 140 may proceed to process 310. In response to the latching state being a second latching state, controller 140 may proceed to process 320.

[0080] At process 310, controller 140 compares the time value with a predetermined threshold. In some embodiments, controller 140 may receive the time value at process 310. For example, controller 140 may receive the time value from memory device 206 and / or sensor 125. As described above, the predetermined threshold may be a calibrable threshold. In an example embodiment, the predetermined threshold is greater than one minute. Specifically, the predetermined threshold may be greater than one minute but less than one hour. For example, the predetermined threshold may be 30 minutes. In other embodiments, the predetermined threshold may be greater than 30 minutes or less than 30 minutes. In response to a time value being at or above the predetermined threshold, controller 140 may proceed to process 312. In response to a time value being below the predetermined threshold, controller 140 may proceed to process 314.

[0081] At process 312, controller 140 sets the latch state to a second latch state. Specifically, controller 140 modifies the value of the latch stored in memory device 206 (which may be an alphanumeric value) to a value corresponding to the second latch state, such as "0" or "off". Controller 140 sets the latch state to the second latch state in response to a time value being at or above a predetermined threshold. In some embodiments, after process 312, controller 140 may continue to process 340.

[0082] At process 314, controller 140 disables or prevents the active regeneration process. In some embodiments, preventing or disabling the regeneration process includes preventing the generation of one or more commands. Typically, these commands correspond to increasing exhaust gas and / or aftertreatment system temperature. For example, preventing the automatic generation of one or more commands in response to determining or identifying one or more conditions that would otherwise trigger the active regeneration process. For example, a pressure value from a pressure sensor may indicate that the pressure drop across the particulate filter of aftertreatment system 120 is at or below a threshold, which typically results in triggering the regeneration process when feasible (e.g., at the next idle or parked state). As another example, operational data may indicate that the amount of time since the most recent regeneration process is at or above a predefined threshold. Typically, this would cause controller 140 to generate one or more commands for the active regeneration process (e.g., activating the aftertreatment system heater, increasing engine power output, etc.) to regenerate components when feasible (e.g., at a parked or idled state). However, controller 140 may prevent such one or more commands. In other embodiments, preventing or disabling the regeneration process includes disabling user input devices for initiating the active regeneration process. For example, controller 140 may disable icons on a touchscreen or prevent physical buttons or switches from being activated. In other embodiments, controller 140 may disable one or more heaters so that these heaters cannot heat the exhaust gas flowing toward / through the aftertreatment system 120.

[0083] At process 320, controller 140 may set the time value to a predetermined value. Controller 140 may set the time value to the predetermined value in response to the latch state being a second latch state. In some embodiments, the predetermined value is zero. In some embodiments, after process 320, controller 140 may continue to process 340.

[0084] At process 330, controller 140 determines whether the power state is a second power state. In some embodiments, controller 140 may receive the power state at process 330. As described above, the first power state corresponds to the "on" state of engine 101, and the second power state corresponds to the "off" state of engine 101. In some embodiments, controller 140 may execute process 330 after process 306 and in response to a change in the power state (e.g., from the first power state to the second power state, or from the second power state to the first power state). In response to the power state being the first power state, controller 140 may return to process 306. In response to the power state being the second power state, controller 140 may continue to process 332. In some embodiments, controller 140 may continue to process 332 in response to a change in the power state from the first power state to the second power state.

[0085] At process 332, controller 140 sets the latch state to the second latch state and sets the time value to a predetermined value. For example, controller 140 may set the latch state to the second latch state and set the time value to a predetermined value in response to the power state being the second power state and / or in response to the power state changing from the first power state to the second power state.

[0086] At process 340, controller 140 determines, identifies, and / or receives indications regarding whether one or more operating values ​​are at or above corresponding thresholds. In some embodiments, controller 140 may receive one or more operating values ​​at process 340. As described above, one or more operating values ​​may include one or more temperature values ​​of exhaust gas at or near engine 101 or in aftertreatment system 120, engine speed values, or other values ​​associated with the operation of engine 101, and / or component temperatures of components of aftertreatment system 120. In response to determining that one or more operating values ​​are at or above corresponding thresholds, controller 140 may proceed to process 342, in which controller 140 enables the regeneration process. In response to determining that one or more operating values ​​are below corresponding thresholds, controller 140 may proceed to process 314.

[0087] At process 342, controller 140 generates and provides one or more commands to heat the exhaust gas emitted by engine 101. This text is in contrast to... Figure 2A command for heating exhaust gas is described. The heated exhaust gas may cause particulate matter (such as soot) to be burned off from one or more components of the aftertreatment system 120 (such as DPF 122). In response to determining that soot has been burned off from DPF 122, controller 140 may determine that the regeneration process is complete. Controller 140 may determine that soot has been burned off from DPF 122 based on, for example, a pressure change on DPF 122 being at or below a predetermined value. For example, controller 140 may receive a first pressure value of exhaust gas upstream of DPF 122 and a second pressure value of exhaust gas downstream of DPF 122. Controller 140 may compare the difference between the first and second pressure values ​​with a predetermined threshold. Controller 140 may determine that soot has been burned off from DPF 122 based on a pressure change on DPF 122 being at or below a predetermined threshold.

[0088] Based on the foregoing, an example of operation can be described as follows. Controller 140 receives a regeneration request. Controller 140 receives a latch state in response to receiving the regeneration request. If the latch state is a second latch state, controller 140 enables the regeneration event. If the latch state is a first latch state (that is, the user has activated the operator interface device), controller 140 disables the regeneration event and starts a timer. When the timer is at or above a threshold (e.g., 30 minutes), controller 140 sets the latch state to the second latch state, thereby re-enabling the regeneration event. Advantageously, re-enabling the regeneration event can mitigate undesirable soot buildup in or on the post-processing system (such as on DPF 122). That is, if the regeneration event is not automatically re-enabling, it will not occur without user input (e.g., a second user input that sets the latch state to the second latch state).

[0089] Additionally, controller 140 may optionally set the latch state to a second latch state in response to an engine shutdown event. That is, controller 140 re-enables the regeneration event after the engine shutdown event. In this way, the regeneration event can occur after the engine shutdown event, such as after a subsequent engine start event. Advantageously, re-enabling the regeneration event can mitigate undesirable soot buildup on DPF 122. In other words, if the regeneration event is not automatically re-enabling after the engine shutdown event, the regeneration event will not occur without user input (e.g., a second user input setting the latch state to the second latch state).

[0090] As used herein, the terms “about,” “approximately,” “substantially,” and similar terms are intended to have a broad meaning and are consistent with common and accepted usage by one of ordinary skill in the art to which the subject matter of this disclosure pertains. Those skilled in the art who read this disclosure will understand that these terms are intended to allow for the description of certain features described and claimed, without limiting the scope of these features to the precise numerical ranges provided. Therefore, these terms should be interpreted as indicating that non-substantial or irrelevant modifications or alterations to the described and claimed subject matter are considered to fall within the scope of this disclosure as set forth in the appended claims.

[0091] It should be noted that the term "exemplary" and its variations used herein to describe various embodiments are intended to indicate that such embodiments are possible examples, representations or illustrations of possible embodiments (and such terms are not intended to indicate that such embodiments are necessarily extraordinary or best examples).

[0092] As used herein, the term "connection" and its variations refer to the direct or indirect engagement of two components with each other. Such engagement can be fixed (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such engagement can be achieved by directly connecting two components to each other, by connecting two components to each other using one or more separate intermediate components, or by connecting two components to each other using an intermediate component that forms a single whole with one of the two components. If "connection" or its variations are modified by an additional term (e.g., direct connection), the general definition of "connection" provided above is modified by the common linguistic meaning of the additional term (e.g., "direct connection" means the engagement of two components without any separate intermediate component), resulting in a narrower definition than the general definition of "connection" provided above. Such connections can be mechanical, electrical, or fluid. For example, a circuit A communicatively "connected" to circuit B can mean that circuit A communicates directly with circuit B (i.e., without an intermediary) or indirectly with circuit B (e.g., through one or more intermediaries).

[0093] References to the position of elements herein (e.g., “top,” “bottom,” “above,” “below”) are used only to describe the orientation of the various elements in the accompanying drawings. It should be noted that the orientation of the various elements may differ according to other exemplary embodiments, and such variations are intended to be covered by this disclosure.

[0094] Although Figure 2Various circuits with specific functions are illustrated herein, but it should be understood that controller 140 may include any number of circuits to perform the functions described herein. For example, the activities and functions of regeneration management circuit 212 may be combined in multiple circuits or as a single circuit. Additional circuits with additional functions may also be included. Furthermore, controller 140 may control other activities beyond the scope of this disclosure.

[0095] As mentioned above, and in one configuration, the "circuit" can be implemented in a machine-readable medium for execution by one or more processors of various types, such as... Figure 2 The processor 204. Executable code may, for example, comprise one or more physical or logical blocks of computer instructions, which may be organized, for example, into objects, procedures, or functions. However, an executable program need not be physically located together, but may comprise different instructions stored in different locations, which, when logically joined together, constitute a circuit and implement the stated purpose of the circuit. In practice, the circuitry of computer-readable program code may be a single instruction or multiple instructions, and may even be distributed across several different code segments, different programs, and multiple memory devices. Similarly, operational data may be identified and described within the circuitry, may be embodied in any suitable form, and may be organized within any suitable type of data structure. Operational data may be collected as a single dataset, or may be distributed across different locations, including different storage devices, and may exist at least partially as electronic signals on a system or network.

[0096] While the term "processor" has been briefly defined above, the terms "processor" and "processing circuitry" should be interpreted broadly. At this point, and as mentioned above, a "processor" can be implemented as one or more processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components constructed to execute instructions provided by memory. One or more processors can take the form of a single-core processor, a multi-core processor (e.g., a dual-core processor, a triple-core processor, a quad-core processor, etc.), a microprocessor, etc. In some embodiments, one or more processors can be located external to the device; for example, one or more processors can be remote processors (e.g., cloud-based processors). Alternatively or additionally, one or more processors can be internal to the device and / or local. At this point, a given circuitry or its components can be located locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud-based server). For this purpose, a "circuitry" as described herein can include components distributed in one or more locations.

[0097] Embodiments within the scope of this disclosure include program products comprising computer- or machine-readable media for carrying or having computer- or machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available medium accessible to a computer. A computer-readable medium can be a tangible computer-readable storage medium storing computer-readable program code. A computer-readable storage medium can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable media may include, but are not limited to, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable optical disc read-only memory (CD-ROM), digital versatile optical disc (DVD), optical storage devices, magnetic storage devices, holographic storage media, micromechanical storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that may contain and / or store computer-readable program code for use by and / or in conjunction with an instruction execution system, device, or apparatus. Machine-executable instructions include, for example, instructions and data that cause a computer or processing machine to perform a specific function or group of functions.

[0098] Computer-readable media can also be computer-readable signal media. Computer-readable signal media can include propagated data signals embodying computer-readable program code, for example, in baseband or as part of a carrier wave. Such propagated signals can 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 can be any computer-readable medium that is not a computer-readable storage medium and can convey, propagate, or transmit computer-readable program code for use by or in conjunction with an instruction execution system, device, or apparatus. The computer-readable program code embodied on a computer-readable signal medium can be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, radio frequency (RF), or any suitable combination thereof.

[0099] 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, computer-readable program code may be transmitted as an electromagnetic signal via an optical fiber cable for execution by a processor, or it may be stored on a RAM storage device for execution by a processor.

[0100] Computer-readable program code used to perform the operations of various aspects of this disclosure may be written in any combination of one or more other 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 execute entirely on the user's computer, partially on the user's computer, as a standalone computer-readable package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be established on an external computer (e.g., using the Internet provided by an Internet service provider).

[0101] The program code may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing apparatus or other means to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing including instructions that implement the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

[0102] Although the accompanying drawings and description may show a specific order of method steps, the order of these steps may differ from the order depicted and described unless otherwise specified. Similarly, unless otherwise specified, two or more steps may be performed simultaneously or partially simultaneously. Such variations may depend on, for example, the chosen software and hardware system and the designer's choices. All such variations are within the scope of this disclosure. Likewise, the software implementation of the described method can be accomplished using standard programming techniques, leveraging rule-based logic and other logic, to perform various connection steps, processing steps, comparison steps, and decision steps.

[0103] It is important to note that the construction and arrangement of the devices and systems shown in the various exemplary embodiments are merely illustrative. Furthermore, any element disclosed in one embodiment may be incorporated into or used in conjunction with any other embodiment disclosed herein.

Claims

1. A system for selectively activating the regeneration of components in an exhaust aftertreatment system, the system comprising: A controller, connected to an aftertreatment system in exhaust gas receiving communication with the engine, includes at least one processor and at least one memory device storing instructions that, when executed by the at least one processor, cause the controller to perform operations, including: A request for a regeneration process associated with a component of the post-processing system is identified based on at least one of receiving input at an operator input device or receiving operational data about the post-processing system from one or more sensors; Receive latch states associated with operator interface devices from the at least one memory device, the latch states including one of a first latch state or a second latch state; In response to the latching state being the first latching state, a time value associated with user input is received from the at least one memory device; In response to the time value being at or above a predetermined threshold, the latch state is modified to the second latch state, such that the regeneration process is enabled in response to receiving the request for the regeneration process; In response to the time value falling below the predetermined threshold, the regeneration process is stopped; and In response to the latching state being the second latching state, the time value is set to a predetermined value.

2. The system of claim 1, wherein the user input is a first user input, and wherein receiving the latch state associated with the operator interface device in response to: The first user input is received at the operator interface device; and In response to receiving the first user input at the operator interface device, a first signal is received from the operator interface device, the first signal indicating that the latching state is the first latching state.

3. The system according to claim 2, wherein, The step of setting the time value to the predetermined value in response to the latching state being the second latching state is in response to: After receiving the first user input and before the time value is at or above the predetermined threshold, a second user input is received at the operator interface device; as well as In response to receiving the second user input at the operator interface device, a second signal is received from the operator interface device, the second signal indicating that the latching state is the second latching state.

4. The system of claim 1, wherein the instructions, when executed by the at least one processor, cause the controller to perform further operations, the further operations including: The power state is determined based on information received from at least one sensor associated with the engine, indicating the power state associated with the engine, the power state including one of a first power state or a second power state; In response to the power state being the first power state, the latch state is received from the at least one memory device; and In response to the power state being the second power state, the latch state is modified to the second latch state.

5. The system of claim 4, wherein the instructions, when executed by the at least one processor, cause the controller to perform further operations, the further operations including: In response to the power state changing from the first power state to the second power state, the time value is set to the predetermined value.

6. The system according to any one of claims 1-5, wherein the instructions, when executed by the at least one processor, cause the controller to perform further operations, the further operations including: In response to the latching state being the second latching state, operational values ​​regarding the operating conditions of at least one of the one or more sensors are received from the sensors. The regeneration process is implemented in response to the operating value being at or above the predetermined threshold; and The regeneration process is blocked in response to the operating value falling below the predetermined threshold.

7. The system according to any one of claims 1-5, wherein the time value is the amount of time between the current time value and a previous time value corresponding to the user input.

8. The system according to any one of claims 1-5, wherein the regeneration process is an active regeneration process.

9. The system according to any one of claims 1-5, wherein the predetermined value is zero.

10. A method for selectively enabling the regeneration of components of an exhaust aftertreatment system, the method comprising: The request for the regeneration process is identified based on at least one of receiving input at the operator interface device or receiving operational data about the post-processing system from one or more sensors; Receive a latch state associated with the operator interface device, the latch state including one of a first latch state or a second latch state; In response to the latching state being the first latching state, a time value associated with the user input is received; In response to the time value being at or above a predetermined threshold, the latch state is modified to the second latch state, such that the regeneration process is enabled in response to receiving the request for the regeneration process; In response to the time value falling below the predetermined threshold, the regeneration process is stopped; and In response to the latching state being the second latching state, the time value is set to a predetermined value.

11. The method of claim 10, wherein the user input is a first user input, and wherein the method further comprises: The first user input is received at the operator interface device; as well as In response to receiving the first user input at the operator interface device, a first signal is received from the operator interface device, the first signal indicating that the latching state is the first latching state, wherein receiving the latching state is based on receiving the first signal.

12. The method of claim 11, further comprising: After receiving the first user input and before the time value is at or above the predetermined threshold, a second user input is received at the operator interface device; as well as In response to receiving the second user input at the operator interface device, a second signal is received from the operator interface device, the second signal indicating that the latching state is the second latching state, wherein in response to receiving the second signal, the time value is set to the predetermined value.

13. The method of claim 10, further comprising: The power state is determined based on information received from at least one sensor associated with the engine, indicating the power state associated with the engine, the power state including one of a first power state or a second power state. In response to the power state being the first power state, the latch state is received from the at least one memory device; and In response to the power state being the second power state, the latch state is modified to the second latch state.

14. The method according to claim 13, further comprising: In response to the power state changing from the first power state to the second power state, the time value is set to the predetermined value.

15. The method according to any one of claims 10-14, further comprising: In response to the latching state being the second latching state, operating values ​​regarding the operating conditions of at least one of the one or more sensors are received from the aftertreatment system or the engine coupled to the aftertreatment system. The regeneration process is implemented in response to the operating value being at or above the predetermined threshold; and The regeneration process is blocked in response to the operating value falling below the predetermined threshold.

16. The method of claim 15, wherein the operating value includes at least one of the following: Regarding the component temperature values ​​of the components of the post-processing system; Regarding the exhaust temperature value of the exhaust gas emitted by the engine; or The speed value is related to the speed of the engine.

17. An apparatus for selectively activating the regeneration of components of an exhaust aftertreatment system, the apparatus comprising: At least one processor; and At least one memory device storing instructions therein, the instructions causing the at least one processor to perform operations when executed by the at least one processor, the operations including: A request for the regeneration process is identified based on at least one of receiving input at an operator input device or receiving operational data about the post-processing system from one or more sensors; Receive latch states associated with operator interface devices from the at least one memory device, the latch states including one of a first latch state or a second latch state; In response to the latching state being the first latching state, a time value associated with user input is received from the at least one memory device; In response to the time value being at or above a predetermined threshold, the latch state is modified to the second latch state, such that the regeneration process is enabled in response to receiving the request for the regeneration process; In response to the time value falling below the predetermined threshold, the regeneration process is stopped; and In response to the latching state being the second latching state, the time value is set to a predetermined value.

18. The device of claim 17, wherein the user input is a first user input, and wherein the instruction, when executed by the at least one processor, causes the at least one processor to perform further operations, the further operations including: The first user input is received at the operator interface device; as well as In response to receiving the first user input at the operator interface device, a first signal is received from the operator interface device, the first signal indicating that the latching state is the first latching state, wherein receiving the latching state is based on receiving the first signal.

19. The apparatus of claim 18, wherein the instructions, when executed by the at least one processor, cause the at least one processor to perform further operations, the further operations including: After receiving the first user input and before the time value is at or above the predetermined threshold, a second user input is received at the operator interface device; as well as In response to receiving the second user input at the operator interface device, a second signal is received from the operator interface device, the second signal indicating that the latching state is the second latching state, wherein in response to receiving the second signal, the time value is set to the predetermined value.

20. The apparatus according to any one of claims 17-19, wherein the instructions, when executed by the at least one processor, cause the at least one processor to perform further operations, the further operations including: The power state is determined based on information received from at least one sensor associated with the engine, indicating the power state associated with the engine, the engine power state including one of a first power state or a second power state. In response to the power state being the first power state, the latch state is received from the at least one memory device; In response to the power state being the second power state, the latch state is modified to the second latch state; as well as In response to the power state changing from the first power state to the second power state, the time value is set to the predetermined value.

Images