System and method for selectively enabling the regeneration of exhaust gas aftertreatment system components

Abstract

To provide a system and method for selectively enabling the regeneration of exhaust gas aftertreatment system components. [Solution] The system includes a controller connected to the post-processing system. The controller is configured to identify requests for components of the post-processing system and associated regeneration processes based on receiving inputs from an operator input device or receiving data about the post-processing system from a sensor. The controller is configured to receive a latch state from a memory device. The controller is configured to receive a time value from the memory device in response to a latch state which is a first latch state. The controller is configured to modify the latch state to a second latch state in response to a time value which is a threshold or above a threshold, so that the regeneration process can be enabled.

Description

Technical Field

[0001] The present disclosure relates to selectively enabling regeneration of exhaust aftertreatment system components.

Background Art

[0002] Many engines are connected to an exhaust aftertreatment system that reduces harmful exhaust gas emissions (e.g., nitrous oxide (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 the component may require changes during operation of the engine, the aftertreatment system, or both.

Summary of the Invention

Means for Solving the Problems

[0003] One embodiment relates to a system. The system comprises an engine and a controller connected to a post-treatment system that communicates with the engine to receive exhaust gases. The controller comprises at least one processor and at least one memory device that, when executed by the at least one processor, internally stores instructions that cause the controller to perform an operation. The operation includes identifying a request for a regeneration process associated with a component of a post-processing system, based on at least one of receiving an input at an operator input device or receiving operational data relating to the post-processing system from one or more sensors; receiving a latch state associated with an operator interface device from at least one memory device, wherein the latch state includes one of a first latch state or a second latch state; receiving a time value associated with user input from at least one memory device in response to the latch state being the first latch state; modifying the latch state to a second latch state in response to a time value that is or exceeds a predetermined threshold, so that the regeneration process can respond to receiving a request for the regeneration process; preventing the regeneration process in response to a time value that falls below a 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 a latch state associated with an operator interface device is in response to receiving a first user input in the operator interface device and receiving a first signal from the operator interface device indicating that the latch state is a first latch state in response to receiving a first user input in the operator interface device.

[0005] In some embodiments, setting a time value to a predetermined value in response to a latch state which is a second latch state corresponds to receiving a second user input in the operator interface device after receiving a first user input and before a time value that is or exceeds a predetermined threshold, and receiving a second signal from the operator interface device indicating that the latch state is a second latch state in response to the operator interface device receiving the second user input.

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

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

[0008] In some embodiments, the instruction, when executed by at least one processor, causes a controller to perform further operations including receiving an operational value from one or more sensors relating to at least one operating condition of a post-processing system or engine in response to a latch state which is a second latch state; implementing a regeneration process in response to an operational value that is or exceeds a predetermined threshold; and preventing a regeneration process in response to an operational value that falls below a 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 user input. In some embodiments, the predetermined threshold is a calibrable value. In some embodiments, the playback process is a forced playback process. In some embodiments, the predetermined value is zero.

[0010] Another embodiment relates to a method. The method includes identifying a request for a replay process based on at least one of receiving an input in an operator interface device or receiving operational data relating to a post-processing system from one or more sensors; receiving a latch state associated with the operator interface device from 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 a user input from at least one memory device in response to the latch state which is the first latch state; modifying the latch state to a second latch state in response to a time value which is or above a predetermined threshold, so that the replay process can respond to receiving a request for a replay process; preventing the replay process in response to a time value which is below a predetermined threshold; and setting the time value to a predetermined value in response to the latch state which is the second latch state.

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

[0012] In some embodiments, the method also includes receiving a second user input in the operator interface device after receiving a first user input and before a time value that is or exceeds a predetermined threshold, and receiving a second signal from the operator interface device indicating that the latch state is a second latch state in response to the operator interface device receiving the second user input, and setting the time value to a predetermined value in response to receiving the second signal.

[0013] In some embodiments, the method also includes determining a power state associated with an engine based on receiving information from at least one sensor associated with the engine indicating a power state including one of a first power state or a second power state; receiving a latch state from at least one memory device in response to the power state being the first power state; and modifying the latch state to a second latch state in response to the power state being the second power state. In some embodiments, the method also includes setting a time value to a predetermined value in response to a power state changing from a first power state to a second power state. In some embodiments, the method also includes receiving an operation value from one or more sensors in response to a latch state being the second latch state, relating to one or more operating conditions of a after-processing system or an engine connected to the after-processing system; implementing a regeneration process in response to an operation value that is or exceeds a predetermined threshold; and preventing a regeneration process in response to an operation value that falls below a predetermined threshold. In some embodiments, the operating value includes at least one of the following: a component temperature value relating to a component of the aftertreatment system, an exhaust gas temperature value relating to exhaust gas discharged by the engine, or a speed value relating to the engine speed.

[0014] Another embodiment relates to a device, which comprises at least one processor and at least one memory device that, when executed by the at least one processor, internally stores instructions causing the at least one processor to perform an operation. The operation includes identifying a request for a replay process based on at least one of receiving input in an operator input device or receiving operation data relating to a post-processing system from one or more sensors; receiving a latch state associated with an operator interface device from at least one memory device, wherein the latch state includes one of a first latch state or a second latch state; receiving a time value associated with user input from at least one memory device in response to the latch state which is the first latch state; modifying the latch state to a second latch state in response to a time value that is or exceeds a predetermined threshold, so that the replay process can respond to receiving a request for a replay process; preventing the replay process in response to a time value that falls below a predetermined threshold; and setting the time value to a predetermined value in response to the latch state which is the second latch state.

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

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

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

[0018] Numerous specific details are provided to provide a complete understanding of the embodiments of the subject matter of this disclosure. In one or more embodiments and / or embodiments, features of the details of the subject matter of this disclosure can be combined in any preferred manner. In this regard, one or more features of one aspect of the invention can be combined with one or more features of different aspects of the invention. Furthermore, additional features that may not be present in any embodiment or embodiment can be recognized in certain particular embodiments and / or embodiments. The present invention provides, for example, the following items: (Item 1) It is a system, A controller connected to an engine and an after-treatment system that communicates with the engine to receive exhaust gases, the controller comprising at least one processor, and when executed by the at least one processor, the controller In an operator input device, the operator identifies a request for a regeneration process associated with a component of the post-processing system based on at least one of receiving an input or receiving operational data relating to the post-processing system from one or more sensors, Receiving a latch state associated with an operator interface device from at least one of the memory devices, wherein the latch state includes one of a first latch state or a second latch state. Receiving a time value associated with user input from at least one memory device in response to the latch state, which is the first latch state, The playback process is made capable of responding to the receiving of the request to the playback process by modifying the latch state to a second latch state that responds to the time value which is a predetermined threshold or exceeds a predetermined threshold, In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A system comprising a controller, which internally stores instructions for performing an operation including setting the time value to a predetermined value in response to the latch state, which is the second latch state. (Item 2) The user input is a first user input, and receiving the latch state associated with the operator interface device is The operator interface device receives the first user input, The system described above, wherein the latch state responds to the operator interface device receiving a first signal from the operator interface device indicating that the latch state is the first latch state, in response to the operator interface device receiving the first user input. (Item 3) Setting the time value to the predetermined value in response to the latch state, which is the second latch state, After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The system according to any one of the above items, wherein the latch state responds to the operator interface device receiving a second signal from the operator interface device indicating that the latch state is the second latch state, in response to the operator interface device receiving the second user input. (Item 4) When the above instruction is executed by the at least one processor, Determining the power state associated with the engine based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine, Receiving the latch state from at least one memory device in response to the power state which is the first power state, The system according to any one of the above items, wherein the controller is instructed to perform a further operation, which includes modifying the latch state to a second latch state in response to the power state, which is the second power state. (Item 5) The system according to any one of the above items, wherein the instruction, when executed by the at least one processor, causes the controller to perform further operations, including setting the time value to a predetermined value in response to the power state changing from the first power state to the second power state. (Item 6) When the instruction is executed by the at least one processor, receive, from the one or more sensors, an operating value related to at least one operating condition of the post-processing system or the engine in response to the latch state that is the second latch state; implement the playback process in response to the operating value that is the predetermined threshold value or exceeds the predetermined threshold value; cause the controller to perform further operations including preventing the playback process in response to the operating value that is less than the predetermined threshold value, the system according to any one of the above items. (Item 7) The time value is an amount of time between a current time value and a previous time value corresponding to the user input, the system according to any one of the above items. (Item 8) The playback process is a forced playback process, the system according to any one of the above items. (Item 9) The predetermined value is zero, the system according to any one of the above items. (Item 10) A method comprising: identifying a request for a playback process based on at least one of receiving an input at an operator interface device or receiving operation data related to a post-processing system from one or more sensors; receiving a latch state associated with the operator interface device, the latch state including one of a first latch state or a second latch state; receiving a time value related to a user input in response to the latch state that is the first latch state; modifying the latch state to the second latch state that responds to the time value that is a predetermined threshold value or exceeds the predetermined threshold value so that the playback process can respond to receiving the request for the playback process; In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A method comprising setting the time value to a predetermined value in response to the latch state, which is the second latch state. (Item 11) The user input is a first user input, and the method is The operator interface device receives the first user input, The method according to any one of the above items, further comprising receiving a first signal from the operator interface device indicating that the latch state is the first latch state in response to the operator interface device receiving the first user input, wherein receiving the latch state is based on receiving the first signal. (Item 12) After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The method of any one of the above items, further comprising receiving a second signal from the operator interface device indicating that the latch state is the second latch state in response to the operator interface device receiving the second user input, and setting the time value to a predetermined value in response to receiving the second signal. (Item 13) Determining the power state associated with the engine based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine, Receiving the latch state from at least one memory device in response to the power state which is the first power state, The method according to any one of the above items, further comprising modifying the latch state to a second latch state in response to the power state which is a second power state. (Item 14) The method according to any one of the above items, further comprising setting the time value to a predetermined value in response to a change in the power state from the first power state to the second power state. (Item 15) The system receives an operating value from one or more sensors in response to the latch state, which is the second latch state, relating to one or more operating conditions of the after-processing system or an engine connected to the after-processing system. The regeneration process is implemented in response to the operation value which is a predetermined threshold or exceeds the predetermined threshold. The method according to any one of the above items, further comprising preventing the regeneration process in response to the operation value falling below a predetermined threshold. (Item 16) The aforementioned operating value is, The component temperature values ​​relating to the components of the post-processing system, The exhaust gas temperature value relating to the exhaust gas discharged by the aforementioned engine, or The method according to any one of the above items, comprising at least one speed value relating to the speed of the engine. (Item 17) It is a device, At least one processor, When executed by the at least one processor, the at least one processor, Identifying a request for a replay process based on at least one of the following: receiving input from an operator input device, or receiving operational data related to the post-processing system from one or more sensors; Receiving a latch state associated with an operator interface device from at least one of the memory devices, wherein the latch state includes one of a first latch state or a second latch state. Receiving a time value associated with user input from at least one memory device in response to the latch state, which is the first latch state, The playback process is made capable of responding to the receiving of the request to the playback process by modifying the latch state to a second latch state that responds to the time value which is a predetermined threshold or exceeds a predetermined threshold, In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A device comprising: at least one memory device that internally stores instructions for performing an operation including setting the time value to a predetermined value in response to the latch state, which is the second latch state. (Item 18) The user input is a first user input, and when the instruction is executed by the at least one processor, the at least one processor is, The operator interface device receives the first user input, The apparatus according to any one of the above items, wherein the latch state causes the operator interface device to perform a further operation, which includes receiving a first signal from the operator interface device indicating that the latch state is in response to the operator interface device receiving the first user input, and the receiving of the latch state is based on receiving the first signal. (Item 19) When the above instruction is executed by the at least one processor, the at least one processor will be instructed to: After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The apparatus according to any one of the above items, wherein the latch state is caused to perform a further operation, which includes receiving a second signal from the operator interface device indicating that the latch state is in response to the operator interface device receiving the second user input, and setting the time value to a predetermined value in response to receiving the second signal. (Item 20) When the above instruction is executed by the at least one processor, the at least one processor will be instructed to: Determining the power state associated with the engine based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine, Receiving the latch state from at least one memory device in response to the power state which is the first power state, The latch state is modified to the second latch state in response to the second power state, The apparatus according to any one of the above items, which causes the apparatus to perform further operations, including setting the time value to a predetermined value in response to a change in the power state from the first power state to the second power state. (Summary) The system includes a controller connected to the post-processing system. The controller is configured to identify requests for components of the post-processing system and associated regeneration processes based on receiving inputs from an operator input device or receiving data about the post-processing system from sensors. The controller is configured to receive latch states from a memory device. The controller is configured to receive time values ​​from the memory device in response to a latch state, which is a first latch state. The controller is configured to correct the latch state to a second latch state in response to a time value that is or exceeds a threshold, so that the regeneration process can be enabled. The controller is configured to prevent the regeneration process in response to a time value that falls below a threshold. [Brief explanation of the drawing]

[0019] [Figure 1] This is a schematic diagram of a block diagram of a vehicle system according to an exemplary embodiment. [Figure 2] This is a block diagram of the controller shown in Figure 1, according to an exemplary embodiment. [Figure 3] This is a block diagram of a method for selectively enabling the regeneration process in the exhaust gas aftertreatment system shown in Figure 1, according to an exemplary embodiment. [Modes for carrying out the invention]

[0020] The following describes various ideas, as well as more detailed embodiments thereof, relating to methods, apparatus, computer-readable media, and systems for selectively enabling the regeneration of components of exhaust gas aftertreatment systems. Before moving to drawings illustrating certain exemplary embodiments in detail, it should be understood that this disclosure is not limited to the details or methodologies described in the specification or shown in the drawings. It should also be understood that the terms used herein are for illustrative purposes only and should not be perceived as limiting.

[0021] 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 its components. 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 determined (e.g., by one or more real sensors) and / or estimated or determined (e.g., by one or more virtual sensors, or by a computer device or processing circuit).

[0022] As described herein, an engine system may comprise an engine and an exhaust aftertreatment system communicating with the engine to receive exhaust gases. The engine may be an internal combustion engine (ICE) configured to burn fuel. The exhaust aftertreatment system comprises one or more components, such as a particulate filter, configured to remove particulate matter, such as soot, from the exhaust gases flowing through an exhaust gas conduit system, and a dosing module (e.g., a doser) configured to supply a dosing fluid to the exhaust gases flowing through the exhaust gas system, and the exhaust gases (e.g., nitrogen oxides, NOx). x The system may also include one or more catalytic devices configured to facilitate the conversion of the elements to less harmful elements (e.g., water, nitrogen), such as oxidation catalysts, selective catalytic reduction (SCR) systems, and three-way catalysts.

[0023] Over time, particulate filters can accumulate particulate matter, reducing their effectiveness (for example, reducing their ability to remove particulate matter from exhaust gases). The control system can enable a “regeneration process” when the exhaust gas temperature (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 some of the particulate matter accumulated in the particulate filter burns, reducing the amount of particulate matter on the filter. A forced regeneration process can result from specific commands intended to regenerate the aftertreatment system or its components (e.g., commanding high power output, activating an electric heater, commanding fuel to be supplied to an oxidation catalyst upstream of the particulate filter so that the fuel is oxidized by the oxidation catalyst, etc.). For example, a forced regeneration process can be triggered by user input (via an operator I / O device) and / or automatically commanded by the controller through various operational instances during idle periods (e.g., during shutdowns). Passive regeneration processes can arise from system operations that cause an increase in after-treatment system temperature (e.g., high-load operating conditions that result in the generation of high exhaust gas temperatures that regenerate components). In this way, forced regeneration is specifically directed while passive regeneration is occurring, without any specific input / command.

[0024] The control system or controller can facilitate the regeneration process, for example, by generating and providing commands to implement the regeneration process (in this case, the forced regeneration process). An operator input / output device connected to the controller may include at least one operator interface device, such as a button or instantaneous switch. Thus, the operator interface device refers to a component and / or system that interfaces with the operator of system 100. In response to receiving input from the operator interface device, the controller can disable the forced regeneration process (for example, by not generating commands and / or by being provided by the user via the operator interface device and / or by the controller automatically triggering the forced regeneration process (for example, without user input). Even if the forced regeneration process is disabled, the operation of the engine and / or exhaust aftertreatment system does not change, for example, because no specific commands are generated or provided to change the operation of the engine and / or exhaust aftertreatment system. However, particulate filters may continue to accumulate particulate matter, degrading their performance (for example, by increasing the pressure drop across the particulate filter, or by reducing the amount of particulate matter removed from the exhaust gas per unit time or unit volume of exhaust gas).

[0025] As described herein, a control system or controller may implement one or more controls to automatically enable the forced regeneration process again. As described herein, a control system may implement one or more controls to automatically enable the forced regeneration process again in response to the deactivation of the forced regeneration process, after at least one predetermined condition is met.

[0026] In one embodiment, the control system can enable the forced regeneration process again after a predetermined amount of time. For example, the control system can determine that the time value associated with user input in the operator interface device is at or above a predetermined threshold. That is, the control system can determine that the amount of time (e.g., "time value") since the user input was received in the operator interface device is at or above a predetermined threshold. The control system can reset the time value in response to receiving a second user input in the operator interface device. In this way, subsequent user input in the operator interface device (e.g., a third user input) results in the forced regeneration process being disabled again. When the forced regeneration process is disabled by the third user input, the regeneration process is disabled for a certain period of time, or less than a predetermined amount of time.

[0027] In another example, the control system may enable the forced regeneration process again in response to receiving and / or determining an engine-related “power state”. In one embodiment, the “power state” may be one of a first power state or a second power state. The first power state is the engine “on” state, where the engine consumes fuel (e.g., idle, generating mechanical force). The second power state is the engine “off” state, where the engine does not consume fuel. In some embodiments, the power state is received via user input in a drive device associated with the engine, such as a key-operated ignition switch or a keyless ignition switch. For example, the user may insert a key into a key-operated ignition switch and turn the key in a first direction to change the power state from a second power state (e.g., off) to a first power state (e.g., on). The user can then rotate the key in a second direction to change the power state from a first power state (e.g., on) to a second power state (e.g., off). In some embodiments, the control system can receive a power state in response to the power state changing from the first power state to the second power state. Advantageously, the control system can reset a time value in response to receiving an indicator that the power state has changed from the first power state to the second power state, thereby disabling subsequent user input in the operator interface device for up to a predetermined amount of time.

[0028] Technically and beneficially, 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 the technical problem of automatically re-enabling the regeneration process (e.g., without user input) after a user has disabled it. In particular, a technical solution involves a controller receiving a latch state associated with an operator interface device. The latch state is either 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 may automatically correct the latch state to a second latch state in response to a time value that is or exceeds a predetermined threshold, so that the regeneration process can respond to requests for the regeneration process. Advantageously, by enabling regeneration events again, an undesirable increase in particulate matter (e.g., soot) in the after-treatment system can be mitigated. That is, without automatically enabling regeneration events again, regeneration events 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 increase, which may lead to undesirable performance of the after-treatment system and / or undesirable emission characteristics (e.g., NOx levels exceeding a predetermined threshold). These and other features and advantages are described more fully below in this specification.

[0029] Referring now to Figure 1, a schematic block diagram of a vehicle system 100 according to an exemplary embodiment is shown. The system 100 comprises an engine 101 and a post-treatment system 120 communicating with the engine 101 to receive exhaust gases. The system 100 may also comprise a controller 140 (shown in Figure 2) and operator input / output (I / O) devices (also shown in Figure 2), the controller 140 being communicatively connected to each of the above-mentioned components. In the configuration of Figure 1, the system 100 is housed in a vehicle. The vehicle can be any type of on-road or off-road vehicle, including but not limited to wheel loaders, forklift trucks, long-haul trucks, medium-haul trucks (e.g., pickup trucks), sedans, coupes, tanks, aircraft, boats, and any other type of vehicle. In another embodiment, the system 100 may be embodied in a stationary piece of the device, such as a generator or generator set. All such variations are intended to fall within the scope of this disclosure.

[0030] Engine 101 may be any type of internal combustion engine and / or any other suitable engine that produces gasoline, natural gas, or diesel engine fuel. In the embodiments described, engine 101 is part of a diesel engine system. In other embodiments, engine 101 is part of a hybrid engine system having a combination of an internal combustion engine and at least one electric motor connected to at least one battery. In some embodiments, the hybrid engine system can be configured as a mild hybrid powertrain, a parallel hybrid powertrain, a series hybrid powertrain, or a series parallel powertrain.

[0031] As shown in Figure 1, an intake air throttle (IAT) valve 102, a fuel module 103, and an oil system 104 are connected to the 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 to the engine 101 (for example, from a fuel source). The fuel module 103 can control one or more fuel supply parameters, including fuel quantity, fuel pressure, and fuel injection timing. The oil system 104 is configured to supply a lubricant (for example, lubricating oil) to the engine 101.

[0032] The IAT valve 102 is a valve located next to the air intake of the engine 101. The IAT valve 102 can be operated between an open position and a closed position (for example, by an actuator controlled by the controller 140). In the open position, the IAT valve 102 allows the maximum amount of air to flow from the air intake to the engine 101. In the closed position, the IAT valve 102 allows the minimum amount of air to flow from the air intake to the engine 101. The controller 140 can selectively operate the IAT valve 102 (for example, by controlling the actuator) in multiple positions, including open and closed positions, and / or multiple positions including open and closed positions, to adjust the amount of air received by the engine 101.

[0033] The aftertreatment system 120 is in communication with the engine 101 to receive exhaust gas. In the illustrated example, the aftertreatment system comprises a first catalytic component, shown as a diesel oxidation catalyst (DOC) 121; a filter (e.g., a particulate filter), shown as a diesel particulate filter (DPF) 122; and a second catalytic component, shown as a selective catalytic reduction (SCR) system 123. In some embodiments, the aftertreatment system 120 comprises a third catalytic component, shown as an ammonia slip catalyst (ASC) 128. The DOC 121, DPF 122, and SCR 123 may be fluidically connected by an exhaust gas conduit. The DOC 121 receives exhaust gas from the engine 110 and is structured to oxidize one or more exhaust gas components (e.g., hydrocarbons, carbon monoxide, etc.) in the exhaust gas. The DPF122 is positioned downstream of the DOC121 and is structured to remove particulate matter or fine particles such as soot from the exhaust gas flowing through it. The DPF122 comprises an inlet from which the exhaust gas is received and an outlet from which the exhaust gas exits after the particulate matter has been substantially filtered out of the exhaust gas. In some embodiments, the DPF122 or other components may be omitted, and / or other components (e.g., a second SCR system having additional dosing units or modules; multiple DOCs, etc.) may be added. Furthermore, although Figure 1 shows only a specific arrangement with respect to the aftertreatment system 120, the arrangement of components within the aftertreatment system 120 may differ in other embodiments (e.g., the DPF122 is positioned downstream of the SCR123 and ASC).

[0034] The post-treatment system 120 may further comprise a reducing agent delivery system, which may include a decomposition chamber (e.g., decomposition reactor, reactor pipe, decomposition tube, reactor tube, etc.) for converting a reducing agent to ammonia, as shown as a dosing module or unit 124. The reducing agent may be, for example, urea, diesel exhaust fluid (DEF), Adblue®, aqueous urea solution (UWS), aqueous urea solution (e.g., AUS32, etc.), and other similar fluids. The dosing module 124 may comprise a reservoir, a pump, and a nozzle (and optionally other components or devices). The reservoir may be structured to store the reducing agent. The pump may be fluidically connected to the reservoir and nozzle by a dosing conduit, and may be structured to pump the reducing agent from the reservoir to the nozzle. The nozzle may deliver the reducing agent to the exhaust gas in the exhaust gas conduit. The reducing agent fluid is added to the exhaust gas flow to assist catalytic reduction. As shown in Figure 1, the reducing agent can be injected upstream of the SCR 123 (or specifically, the SCR catalyst) by the dosing module 124 so that the SCR catalyst accepts a mixture of the reducing agent and exhaust gas. The reducing agent droplets then undergo the processes of evaporation, thermal decomposition, and hydrolysis to form gaseous ammonia in the decomposition chamber, the SCR catalyst, and / or the exhaust gas conduit system, and the gaseous ammonia leaves the aftertreatment system 120.

[0035] DOC121 is fluidically coupled to the exhaust gas conduit system to oxidize one or more gaseous components of the exhaust gas (e.g., hydrocarbons, carbon oxides, etc.). To adequately assist in the oxidation of one or more gaseous components, DOC121 may require being at a specific operating temperature. In some embodiments, this specific operating temperature is approximately 200–500°C. In other embodiments, the specific operating temperature is the temperature at which the conversion efficiency of DOC121 (e.g., the conversion of hydrocarbons to less harmful compounds, known as hydrocarbon conversion efficiency) exceeds a predetermined threshold.

[0036] SCR123 is configured to assist in the reduction of NOx emissions by accelerating the NOx reduction process of ammonia and NOx in exhaust gases to diatomic nitrogen (N2) and water (H2O). If the SCR catalyst is not at, or does not exceed, a certain temperature, the acceleration of the NOx reduction process is limited, and the SCR123 may not be able to operate at a certain level of desired conversion efficiency (i.e., a value indicating the amount of NOx emissions reduced, also called "deNOx efficiency"). In some embodiments, this certain temperature is approximately 200–600°C. The SCR catalyst may also be made of a combination of an inert material and an active catalyst, where the inert material (e.g., a ceramic substrate) directs the exhaust gas to the active catalyst, and the active catalyst is any type of material suitable for catalytic reduction (e.g., metal exchange zeolite (Fe or Cu / zeolite); base metal oxides such as vanadium, molybdenum, tungsten, etc.).

[0037] If ammonia in the exhaust gas does not react with the SCR catalyst (either because the SCR123 is below its operating temperature, or because the amount of ammonia administered significantly exceeds the amount of NOR), the unreacted ammonia may combine with the SCR catalyst and be stored in the SCR123. This stored ammonia is released from the SCR123 when it warms up, and can cause problems (potentially leading to ammonia slip) if the amount of ammonia released is much greater than the amount of NOx passing through (i.e., more ammonia than is needed relative to the amount of NOx). In some embodiments, an ASC128 is included and structured to address ammonia slip by removing at least some excess ammonia from the treated exhaust gas before the treated exhaust gas is released into the atmosphere. As the exhaust gas passes through the ASC128, some of the unreacted (i.e., not reacted with NOx) ammonia remaining in the exhaust gas is partially oxidized to NOx, which then subsequently reacts with the remaining unreacted ammonia to form N2 gas and water. However, similar to SCR catalysts, if ASC128 is not at, or does not exceed, a certain temperature, the acceleration of the NH3 reduction process is limited, and ASC128 cannot operate at a certain level of efficiency to meet the restrictions or desired parameters. In some embodiments, this certain temperature is approximately 250–300°C.

[0038] As shown, multiple sensors 125 are included in the post-processing system 120. The number, arrangement, and types of sensors included in the post-processing system 120 are shown for illustrative purposes only. That is, in other configurations, the number, arrangement, and types of sensors may differ. Sensors 125 may include gas component sensors (e.g., NOx sensors, oxygen sensors, etc.), temperature sensors, particulate matter (PM) sensors, flow velocity sensors (e.g., mass flow sensors, volumetric flow sensors, etc.), other exhaust gas emission component sensors, pressure sensors, or some combinations thereof. An example of a gas component sensor is an oxygen sensor configured to acquire data indicating the presence of oxygen in the exhaust gas. The AFR value can be estimated using data from the oxygen sensor. An example of a flow velocity sensor is a mass airflow (MAF) sensor configured to acquire data indicating the mass flow rate of the exhaust gas. A temperature sensor may be configured to acquire data indicating the temperature value at each position where the temperature sensor is located.

[0039] Sensor 125 can be located in or near the engine 101, after the engine 101 and before the aftertreatment system 120, after the aftertreatment system 120, within the aftertreatment system as shown (e.g., connected to the DPF and / or DOC, connected to the SCR, etc.), upstream of the engine 101, etc. It should be understood that the position of the sensor may vary. In one embodiment, there may be sensors 125 located both before and after the aftertreatment system 120. In one embodiment, at least one of the sensors takes the form of an exhaust gas component sensor (e.g., a sensor for CO, NOx, PM, SOx, etc.). In another embodiment, at least one of the sensors 125 takes the form of a non-exhaust gas component sensor used to estimate exhaust gas emissions (temperature, flow velocity, pressure, etc.). Additional sensors may also be provided in the system 100. Examples of sensors include engine-related sensors (e.g., torque sensor, speed sensor, pressure sensor, flow velocity sensor, temperature sensor, etc.). For example, in some embodiments, at least one of the sensors 125 takes the form of an oil temperature sensor used to detect and / or determine the engine oil temperature. Other examples of sensors include those associated with other components of the vehicle (e.g., turbocharger speed sensors, fuel quantity and injection speed sensors, fuel rail pressure sensors, etc.).

[0040] Sensor 125 may be real or virtual (i.e., a non-physical sensor that takes the form of program logic within a controller 140 that performs various estimations or determinations). For example, an engine speed sensor may be a real or virtual sensor configured to determine, or otherwise acquire, data, values, or information indicating the speed of engine 101 (typically expressed in revolutions per minute). If the sensor takes the form of a real sensor, it may be connected to the engine and transmit a signal to a controller 140 indicating the speed of engine 101. If the sensor takes the form of a virtual sensor, the controller 140 may use at least one input, such as an algorithm, model, or reference table, to determine or estimate engine parameters (e.g., power output). Any of the sensors 125 described herein may be real or virtual.

[0041] The controller 140 is connected to the sensors 125, and in particular, is communicatively coupled to the sensors 125. Thus, the controller 140 is structured to receive data from one or more of the sensors 125 and 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.

[0042] The operator input / output (I / O) device 130 can be connected to the controller 140 so that information can be exchanged between the controller 140 and the I / O device 130, and the information can relate to one or more components of Figure 1, or to the controller 140's (details described later) decisions. The operator I / O device 130 enables the operator of system 100 to communicate with the controller 140 and one or more components of system 100, as shown in Figure 1. Examples of operator input / output devices include, but are not limited to, an interactive display, a touchscreen device, one or more buttons and switches, and a voice command receiver. In this way, the operator input / output device 130 can provide the operator with one or more indicators or notifications, such as a malfunction indicator lamp (MIL). Furthermore, the vehicle may have a port that allows the controller 140 to be connected to or coupled with a scanning tool, making fault codes and other information about the vehicle available.

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

[0044] The controller 140 is structured to control, at least in part, the operation of the system 100 and related subsystems such as the engine 101 and the operator I / O device 130. Communication between and between components may be via any number of wired or wireless connections. For example, wired communication may include serial cables, fiber optic cables, CAT5 cables, or any other form of wired connection. In comparison, wireless connections may include the Internet, Wi-Fi, mobile, and wireless. In one embodiment, a controller area network (CAN) bus provides the exchange of signals, information, and / or data. The CAN bus may include any number of wired and wireless connections. Since the controller 140 is communicatively connected to the system and components of Figure 1, the controller 140 is structured to receive data from one or more of the components shown in Figure 1. The structure and function of the controller 140 are further described in Figure 2.

[0045] Since the components in Figure 1 are shown as they would be embodied in a vehicle, the controller 140 can take the form of one or more electronic control units (ECUs), such as one or more microcontrollers. The controller 140 can be separate from or included with at least one of the following: a transmission control unit, an exhaust aftertreatment control unit, a powertrain control module, an engine control module, etc.

[0046] Referring now to Figure 2, a schematic diagram of the controller 140 of the system 100 of Figure 1 according to an exemplary embodiment is shown. As shown, the controller 140 comprises 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. The controller 140 is configured to selectively enable and / or disable the regeneration process (e.g., a forced regeneration process). As described herein, enabling the regeneration process makes it possible for the regeneration process to occur when certain conditions are met, such as the exhaust gas temperature value being at or above the exhaust gas temperature threshold; the after-treatment system component temperature value being at or above the component temperature threshold; or the engine speed value being at or above the speed threshold. By disabling the regeneration process, the regeneration process is prevented from occurring, for example, by preventing the operation of the engine 101 and / or the aftertreatment system 120 from being modified to achieve the aforementioned operating conditions, such as preventing the exhaust gas temperature value from exceeding the exhaust gas temperature threshold, preventing the aftertreatment system component temperature value from exceeding the component temperature threshold, or preventing the engine speed value from exceeding the speed threshold.

[0047] In one configuration, the playback management circuit 212 is embodied as a machine- or computer-readable medium that stores instructions executable by a processor such as the processor 204. As described herein, and in other uses, the machine-readable medium facilitates the performance of a particular operation and enables the reception and transmission of data. For example, the machine-readable medium can provide instructions (e.g., commands) for acquiring data. In this regard, the machine-readable medium can be programmable logic that defines the acquisition (or transmission) of data. Instructions in the computer-readable medium can be 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 by a single processor or by multiple remote processors. In the latter case, the remote processors can be connected to each other through any type of network (e.g., a CAN bus).

[0048] In an alternative configuration, the regeneration management circuit 212 is embodied as one or more hardware units, such as one or more electronic control units. Thus, the regeneration management circuit 212 can be embodied as one or more circuit component elements, including but not limited to processing circuit elements, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, the regeneration management circuit 212 can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-chip (SOC) circuits, microcontrollers, etc.), telecommunication circuits, hybrid circuits, and any other kind of “circuit.” In this regard, the regeneration management circuit 212 may comprise any kind of component for achieving or facilitating the operations described herein. For example, circuits described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and the like. The regeneration management circuit 212 may also be, or may be, programmable hardware devices such as field-programmable gate arrays, programmable array logic, or programmable logic device programs. The regeneration management circuit 212 may include one or more memory devices for storing instructions that can be executed by the processor(s) of the regeneration management circuit 212. The one or more memory devices and processor(s) may have the same definitions as shown below with respect to the memory device 206 and processor(s) 204. In some hardware unit configurations, the regeneration management circuit 212 can be geographically distributed across separate locations within the vehicle. Alternatively, as shown, the regeneration management circuit 212 can be implemented in, or within, a standalone unit / housing, shown as the controller 140.

[0049] In the example shown, the controller 140 comprises a processing circuit 202 having a processor 204 and a memory device 206. The processing circuit 202 is structured, or can be configured, to execute or implement the instructions, commands, and / or control processes described herein to the regeneration management circuit 212. The configuration shown represents the regeneration management circuit 212, which is embodied as a machine or computer-readable medium for storing instructions. However, as stated above, this illustration is not limiting, as the disclosure envisions other embodiments in which the regeneration management circuit 212 is configured as a hardware unit. All such combinations and variations are intended to fall within the scope of the disclosure.

[0050] The processor 204 can 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, separate hardware components, etc., for performing the functions described herein). The processor may also be a microprocessor, a group of processors, etc. The processor can also be implemented as a combination of computer 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 (for example, the playback management circuit 212 may, in some exemplary embodiments, comprise the same processor, or may be shared, that can execute instructions stored, or, in other cases, accessed, via different memory regions). Alternatively, one or more processors may be structured to perform, or, in other cases perform, certain operations independently of one or more coprocessors. In other exemplary embodiments, two or more processors may be connected via a bus to enable the execution of independent, parallel, piped, or multithreaded instructions. All such variations are intended to fall within the scope of this disclosure.

[0051] The memory device 206 (e.g., memory, memory unit, storage device) may be one or more devices (e.g., RAM, ROM, flash memory, hard disk storage) for storing data and / or computer code to complete or facilitate the various processes, layers, and modules described herein. For example, the memory device 206 may be dynamic random access memory (DRAM). The memory device 206 may be communicatively connected to the processor 204 to provide the processor 204 with computer code or instructions to perform at least some of the processes described herein. Furthermore, the memory device 206 may be, or include, tangible, non-transient volatile memory or non-volatile memory. Thus, the memory device 206 may be a database component, an object code component, a script component, or any other type of information structure to support the various activities and information structures described herein.

[0052] The communication interface 216 can be any combination of wired and / or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wired terminals) for data communication by various systems, devices, or networks, enabling in-vehicle communication (e.g., between and between vehicle components) and communication with the outside of the vehicle (e.g., using a remote server). For example, with respect to in-vehicle / out-of-system communication, the communication interface 216 may include Ethernet® cards and ports for sending and receiving data over an Ethernet®-based communication network, and / or Wi-Fi transceivers for communication over a wireless communication network. The communication interface 216 can be configured to communicate over a local area network or a wide area network (e.g., the Internet), and can use various communication protocols (e.g., IP, LON, Bluetooth®, Zigbee®, radio, mobile, short-range communication).

[0053] In some embodiments, the controller 140 and / or one or more of its components, such as the regeneration management circuit 212, are configured to facilitate a forced regeneration process. For example, the controller 140 can generate one or more commands to increase the exhaust gas temperature (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 some of the particulate matter accumulating in the DPF 122 burns, reducing the amount of particulate matter on the DPF 122. In some embodiments, one or more commands to facilitate the forced regeneration process include the controller 140 instructing the engine 101 (and in particular the fuel supply system) to discharge a predetermined amount of fuel into the aftertreatment system 120. The DOC 121 can facilitate fuel oxidation, which is an exothermic reaction that increases the exhaust gas temperature. In some embodiments, the controller 140 can generate one or more commands to increase the engine speed of the engine 101. The increased engine speed can result in a higher combustion temperature and, therefore, a higher exhaust gas temperature. In some embodiments, the controller 140 can enable a cylinder deactivation mode in which one or more combustion cylinders of the engine 101 are deactivated. The remaining active cylinders of the engine 101 consume more fuel, allowing the engine 101 to keep up with the required amount of power output. The increased fuel consumption can result in higher combustion temperatures and, therefore, higher exhaust gas temperatures. In some embodiments, the controller 140 can 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 embodiment, one or more heaters are configured to heat the exhaust gas (e.g., downstream of the engine 101 and upstream of the DPF 122), thereby resulting in an increase in exhaust gas temperature. In another embodiment, one or more heaters are configured to heat the intake air (e.g., upstream of the engine 101).The increased intake temperature can result in a higher combustion temperature and, consequently, a higher exhaust gas temperature. In other embodiments, one or more heaters can directly or indirectly heat components of the system, such as a post-treatment system. The heated components can promote desired activities, such as the catalytic activity of an SCR.

[0054] In some embodiments, the controller 140 and / or one or more of its components, such as the regeneration management circuit 212, are configured to facilitate the deactivation of the forced regeneration process. For example, the controller 140 can receive user input via the operator I / O device 130, or more specifically, via the operator interface device. In some embodiments, when user input is received by the operator interface device, the controller 140 is configured to deactivate the regeneration process. When the controller 140 deactivates the regeneration process, the controller 140 may prevent one or more of the aforementioned commands, which represent a limited list of regeneration commands, from being generated and implemented / executed. For example, the controller 140 may prevent one or more commands that increase the exhaust gas temperature from being regenerated.

[0055] In various embodiments, the controller 140 and / or one or more of its components, such as the regeneration management circuit 212, are configured to selectively enable or disable the forced regeneration process. In some embodiments, the controller 140 can disable the regeneration process in response to receiving a first user input in the operator interface device. The controller 140 can re-enable the regeneration process in response to receiving a second user input in the operator interface device. Advantageously, the controller 140 is also configured to automatically re-enable the regeneration process (e.g., without user input) based on one or more predetermined conditions. The process for automatically re-enables the regeneration process is described in further detail herein.

[0056] In an exemplary embodiment, the controller 140 is configured to receive requests for a regeneration process. The regeneration process may be associated with a component of the post-processing system 120, such as the DPF 122.

[0057] The controller 140 is configured to receive and / or determine the latch state associated with the components of the operator I / O device 130, such as the operator interface device. “Latch” refers to a data element (e.g., a specific piece of data or information). In some embodiments, the data element is a value such as a binary value (e.g., 0 or 1). In other embodiments, the data element is a string (e.g., “on” or “off”, “true” or “false”), or another preferred data type. Thus, the “latch state” may be a value indicating the state of the latch (in the case of a string, it may be a digit, letter, and / or an alphanumeric value). For example, when a fastening bolt is provided as a binary value, the “latch state” may be 0 or 1. In another embodiment, when the latch is provided as a string, the latch state may be “on” or “off”. The latch state is stored in the controller 140’s memory 206, where it can be updated.

[0058] In some embodiments, the latch state indicates a certain or recent state of the operator interface device. More specifically, the latch state can indicate whether the user has operated the operator interface device (e.g., pressed, toggled, selected, etc.). 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" (if the latch state takes the form of a binary representation). Subsequent interaction with the operator interface device causes the latch state to change between "0" and "1", or between "on" and "off". That is, the latch state changes (e.g., from "0" to "1", or from "1" to "0") in response to receiving user input in the operator interface device. Alternatively, and as will be described in more detail later, the controller 140 can automatically change the latch state.

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

[0060] The first latch state corresponds to the "on" state of a component of the operator interface device. The latch value 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 by the operator interface device. In an exemplary embodiment, the first user input corresponds to a user activating the operator interface device to disable the forced regeneration process. Thus, while the latch state is in the first latch state, the controller 140 can disable the regeneration process.

[0061] A second latch state is the "off" state of a component of the operator interface device. The latch value 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 by the operator interface device and / or when the controller 140 automatically sets the latch state to the second latch state. In an exemplary embodiment, the second user input corresponds to a user deactivating the operator interface device to enable the forced regeneration process again. Furthermore, 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 in this specification. Thus, while the latch state is in the first latch state, the controller 140 can disable the regeneration process.

[0062] In an exemplary embodiment, the controller 140 receives, retrieves, identifies, and / or, otherwise determines a latch state in response to receiving one of a first user input or a second user input in the operator interface device. In another exemplary embodiment, the controller 140 receives, identifies, retrieves, and / or determines a latch state in response to receiving a different input, such as a "power state." The power state is described in further detail below in this specification.

[0063] The 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 value and the 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. The time value can be determined, for example, 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 determined by one or more computer-implemented time management devices, such as a clock, stopwatch, or timer, which in some embodiments are embodied by a virtual sensor 125. The time value can be stored in the memory device 206 of the controller 140. In one embodiment, the controller 140 can receive the time value in response to a latch state, which is a first latch state.

[0064] The controller 140 is configured to correct the latch state from a first latch state to a second latch state in response to a time value that is or exceeds a predetermined threshold. The controller 140 is configured so that the forced regeneration process does not respond to a time value that falls below the predetermined threshold. The predetermined threshold may be a calibrated threshold. For example, the predetermined threshold can be set by a user, such as the operator of the system 100 or another user. The predetermined threshold can be, for example, greater than one minute. In particular, the predetermined threshold can be greater than one minute but less than one hour. For example, the predetermined threshold can be 30 minutes.

[0065] The controller 140 is configured to set a time value to a predetermined value in response to a latch state, which is a second latch state. For example, the controller 140 can set a time value to a predetermined value in response to modifying the latch state from a first latch state to a second latch state. In another embodiment, the controller 140 can set a time value to a predetermined value in response to receiving a second user input in the operator interface device 130 after receiving a first user input and before a time value that is or exceeds a predetermined threshold. In yet another embodiment, the controller 140 can set a time value to a predetermined value in response to receiving a second signal indicating that the latch state is in response to receiving a second user input in the operator interface device 130. The predetermined value may be, for example, 0 minutes.

[0066] In some embodiments, the controller 140 is configured to receive a power state associated with the engine 101. As previously mentioned, the power state may be one of a first power state or a second power state. In one embodiment, the controller 140 receives power state information from one or more sensors 125. For example, power state information 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, the controller 140 can determine that the power state is a second power state (e.g., an off state). When the engine speed or engine torque is greater than zero, the controller 140 can determine that the power state is a first power state (e.g., an on state). In these embodiments, the controller 140 determines the power state based on the information it receives.

[0067] In another embodiment, information indicating the power state is received from an ignition system (e.g., a key-operated ignition, a button-operated ignition, etc.). For example, when the ignition system is activated (e.g., turned on by a key or activated by another method), the controller 140 can determine that the power state is a first power state (e.g., the ON state). When the ignition system is deactivated (e.g., turned off by a key or deactivated by another method), the controller 140 can determine that the power state is a second power state (e.g., the OFF state).

[0068] In some embodiments, the controller 140 is configured to receive a latch state in response to a power state, which is a first power state. For example, the controller 140 may receive a latch state when the system 100 is energized and turned on. In some embodiments, the controller 140 is configured to modify the latch state to a second latch state in response to a power state, which is a second power state. In some embodiments, the controller 140 is configured to modify the latch state to a second latch state in response to a power state that changes from a first power state to a second power state. For example, when the system 100 is turned off and / or when the system 100 changes from an on state to an off state, the controller 140 may set the latch state to a second latch state.

[0069] In some embodiments, the controller 140 is configured to set a time value to a predetermined value in response to a power state changing from a first power state to a second power state. For example, when the system 100 changes from an ON state to an OFF state, the controller 140 can set the time value to a predetermined value.

[0070] In some embodiments, the controller 140 is configured to receive an operating value relating to one operating condition of the aftertreatment system 120 or the engine 101 in response to a latch state, which is a second latch state. For example, the controller 140 may receive one or more temperature values ​​relating to exhaust gas in or near the engine 101 or within the aftertreatment system 120. In another embodiment, the controller 140 may receive an engine speed value or other values ​​relating to the operation of the engine 101. In yet another embodiment, the controller 140 may receive component temperatures relating to components of the aftertreatment system 120.

[0071] In some embodiments, the controller 140 is configured to implement a forced regeneration process in response to an operating value that is at or above a predetermined threshold. For example, the controller 140 can implement a forced regeneration process when one or more temperature values ​​are at or above a predetermined temperature threshold. In another embodiment, the controller 140 can implement a forced regeneration process when the engine speed value is at or above an engine speed threshold. In yet another embodiment, the controller 140 can implement a forced regeneration process when the component temperature value is at or above a component temperature threshold.

[0072] In some embodiments, the controller 140 is configured so that the forced regeneration process does not respond to operating values ​​below a predetermined threshold. For example, the controller 140 can prevent the forced regeneration process when one or more temperature values ​​are below a predetermined temperature threshold. In another embodiment, the controller 140 can prevent the forced regeneration process when the engine speed value is below an engine speed threshold. In yet another embodiment, the controller 140 can prevent the forced regeneration process when the component temperature value is below a component temperature threshold.

[0073] Figure 3 is a flow diagram of Method 300, which selectively enables the regeneration process according to an exemplary embodiment. Specifically, the controller 140 and / or one or more of its components, such as the regeneration management circuit 212, are structured to implement Method 300. In some embodiments, one or more of the processes of Method 300 are optional. For example, processes 340 and / or 342 are optional and can be omitted from Method 300. In yet other embodiments, one or more of the processes can be combined with one or more other illustrated processes, and furthermore, additional processes can be added to Method 300 without departing from the spirit and scope of this invention.

[0074] In process 302, the controller 140 receives or identifies a regeneration request. In some embodiments, the controller 140 may receive or identify a regeneration request in response to a predetermined period of time elapsed since the most recent regeneration process (e.g., the most recent forced regeneration process and / or the most recent passive regeneration process). In some embodiments, the controller 140 may receive or identify a regeneration request in response to a pressure change across one or more components of the after-treatment system 120 (e.g., DOC 121 or DPF 122 at or above a predetermined threshold), or to another indicator of particulate matter accumulation in the after-treatment system (e.g., a sensed flow velocity at or below a predetermined threshold). In this way, the controller 140 receives information indicating a regeneration request from the sensor 125 (e.g., a pressure sensor, a flow velocity sensor, or other suitable sensor) and identifies the regeneration request based on operational data relating to the after-treatment system (e.g., pressure values, flow velocity values, etc.). In another embodiment, the controller 140 identifies a playback request based on receiving user input (via the I / O device 130).

[0075] In process 304, the controller 140 receives user input. User input can be received by the 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 can be received after the first user input.

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

[0077] In process 308, the controller 140 identifies or determines whether the latch state is a first state (or, for example, receives an indicator from a sensor). In some embodiments, the controller 140 can determine whether the latch state is a first latch state in response to receiving a replay request in process 302. In response to a latch state that is a first latch state, the controller 140 can proceed to process 310. In response to a latch state that is a second latch state, the controller 140 can proceed to process 320.

[0078] In process 310, the controller 140 compares a time value with a predetermined threshold. In some embodiments, the controller 140 can receive time values ​​in process 310. For example, the controller 140 can receive time values ​​from the memory device 206 and / or the sensor 125. As described above, the predetermined threshold can be a calibrated threshold. In exemplary embodiments, the predetermined threshold is greater than one minute. In particular, the predetermined threshold can be greater than one minute but less than one hour. For example, the predetermined threshold can be 30 minutes. In other embodiments, the predetermined threshold can be greater than 30 minutes or less than 30 minutes. In response to a time value that is at or above the predetermined threshold, the controller 140 can proceed to process 312. In response to a time value that is below the predetermined threshold, the controller 140 can proceed to process 314.

[0079] In process 312, the controller 140 sets the latch state to a second latch state. Specifically, the controller 140 modifies the latch value (which may be an alphanumeric value) stored in the memory device 206 to a value corresponding to the second latch state, such as "0" or "off". The controller 140 sets the latch state to the second latch state in response to a time value that is or exceeds a predetermined threshold. In some embodiments, after process 312, the controller 140 may proceed to process 340.

[0080] In process 314, the controller 140 disables or prevents the forced 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 an increase in exhaust gas and / or a rise in aftertreatment system temperature. For example, one or more commands are prevented from being automatically generated in response to determining or identifying one or more conditions, for example, that otherwise trigger the forced regeneration process. For example, a pressure valve from a pressure sensor may indicate that a pressure drop across the particulate filter of the aftertreatment system 120 is at or below a threshold, which typically triggers the regeneration process if feasible (for example, under the next idle or parking condition). In another embodiment, operational data may indicate that the amount of time since the most recent regeneration process is at or above a predetermined threshold. Typically, this causes the controller 140 to generate one or more commands for a forced regeneration process (e.g., activating after-treatment system heaters, increasing engine power output, etc.) during available time (e.g., while parked or idling) to regenerate the component(s). However, the controller 140 can prevent one or more of these commands. In other embodiments, preventing or disabling a regeneration process includes disabling a user input device used to initiate a forced regeneration process. For example, the controller 140 may disable an icon on a touchscreen or prevent a physical button or switch from being activated. In yet another embodiment, the controller 140 may disable one or more heaters so that they cannot heat exhaust gases flowing toward / through the after-treatment system 120.

[0081] In process 320, the controller 140 can set the time value to a predetermined value. The controller 140 can set the time value to a predetermined value in response to a latch state, which is a second latch state. In some embodiments, the predetermined value is zero. In some embodiments, after process 320, the controller 140 can proceed to process 340.

[0082] In process 330, the controller 140 can determine whether the power state is a second power state. In some embodiments, the controller 140 can receive a power state in process 330. As described above, the first power state corresponds to the "on" state of the engine 101, and the second power state corresponds to the "off" state of the engine 101. In some embodiments, the controller 140 can perform process 330 after process 306 and in response to a change in the power state (for example, from the first power state to the second power state, or from the second power state to the first power state). In response to a power state that is the first power state, the controller 140 can return to process 306. In response to a power state that is the second power state, the controller 140 can proceed to process 332. In some embodiments, in response to a power state that changes from the first power state to the second power state, the controller 140 can proceed to process 332.

[0083] In process 332, the controller 140 sets the latch state to a second latch state and the time value to a predetermined value. For example, the controller 140 can set the latch state to a second latch state and the time value to a predetermined value in response to a power state which is a second power state, and / or in response to a power state which changes from a first power state to a second power state.

[0084] In process 340, the controller 140 determines, identifies, and / or receives an indicator of whether one or more operating values ​​are at or above a corresponding threshold. In some embodiments, the controller 140 may receive one or more operating values ​​in process 340. As described above, one or more operating values ​​may include one or more temperature values ​​relating to exhaust gas in or near the engine 101 or within the aftertreatment system 120; engine speed values ​​or other values ​​related to the operation of the engine 101; and / or component temperatures relating to components of the aftertreatment system 120. In response to determining that one or more operating values ​​are at or above a corresponding threshold, the controller 140 may proceed to process 342, enabling the regeneration process. In response to determining that one or more operating values ​​are below a corresponding threshold, the controller 140 may proceed to process 314.

[0085] In process 342, the controller 140 generates and provides one or more commands to heat the exhaust gas emitted by the engine 101. Commands for heating the exhaust gas are described herein with reference to Figure 2. The heated exhaust gas may cause particulate matter, such as soot, to burn one or more components of the aftertreatment system 120, for example, the DPF 122. In response to determining that soot has burned the DPF 122, the controller 140 can determine that the regeneration process is complete. For example, the controller 140 can determine that soot has burned the DPF 122 based on a pressure change across the DPF 122 that is at or below a predetermined value. For example, the controller 140 can receive a first pressure value for the exhaust gas upstream of the DPF 122 and a second pressure value for the exhaust gas downstream of the DPF 122. The controller 140 can compare the difference between the first and second pressure values ​​with a predetermined threshold. Based on pressure changes across the DPF122 that are at or below a predetermined threshold, the controller 140 can determine that soot has burned in the DPF122.

[0086] Based on the above, an example of operation can be described as follows: Controller 140 receives a regeneration request. In response to receiving the regeneration request, Controller 140 receives a latch state. If the latch state is the second latch state, Controller 140 enables the regeneration event. If the latch state is the first latch state (i.e., the state in which the user has activated the operator interface device), Controller 140 disables the regeneration event and starts the timer. When the timer is at or exceeds a threshold (e.g., 30 minutes), Controller 140 sets the latch state to the second latch state, thereby enabling the regeneration event again. Advantageously, enabling the regeneration event again can mitigate an undesirable increase in soot in or on the after-processing system, for example, on the DPF 122. That is, without automatically enabling the regeneration event again, the regeneration event will not occur without user input (e.g., a second user input setting the latch state to the second latch state).

[0087] Furthermore, the controller 140 can optionally set the latch state to a second latch state in response to an event in which the engine turns off. That is, the controller 140 enables the regeneration event again after the event in which the engine turns off. In this way, the regeneration event may cause the engine to turn off again after a subsequent event in which the engine turns on. Advantageously, enabling the regeneration event again can mitigate an undesirable increase in soot from the DPF 122. That is, without automatically enabling the regeneration event again after an event in which the engine turns off, the regeneration event will not occur without user input (for example, a second user input to set the latch state to a second latch state).

[0088] As used herein, the terms “approximately,” “about,” “substantially,” and similar terms are intended to have a broad meaning consistent with the general and acceptable use by those skilled in the art to which the subject matter of this disclosure belongs. It should be understood by those skilled in the art reviewing this disclosure that these terms are intended to enable the description of certain features described and claimed without limiting the scope of those features to the exact number provided. Accordingly, these terms should be construed as indicating that any imaginary or non-material modifications or changes to the subject matter described and claimed are deemed to fall within the scope of this disclosure as enumerated in the appended claims.

[0089] It should be noted that the term “exemplary” and its variations as used herein to describe various embodiments are intended to indicate possible examples, representations, or illustrations of possible embodiments (and not intended to imply that such embodiments necessarily constitute remarkable or unparalleled examples).

[0090] As used herein, the term “linked” and its variations mean joining two members to each other, directly or indirectly. Such joining may be static (e.g., permanent or fixed) or movable (e.g., removable or detachable). Such joining may be achieved by two members directly linked to each other, by two members linked to each other using one or more separately intervening members, or by two of two members using an intervening member integrally formed as a single, integrated body. When “linked” or its variations are modified by additional terms (e.g., “directly linked”), the general definition of “linked” above is modified by the explicit linguistic meaning of the additional terms (e.g., “directly linked” means joining two members without any separate intervening members), resulting in a narrower definition than the general definition of “linked” above. Such joining may be mechanical, electrical, or fluid. For example, circuit A "connected" to circuit B in a communicative manner can represent either circuit A communicating directly (i.e., without intermediaries) or circuit B communicating indirectly (for example, through one or more intermediaries).

[0091] In this specification, references to the position of elements (e.g., “top,” “bottom,” “up,” “down”) are used solely to describe the orientation of various elements in the drawings. It should be noted that the orientation of various elements may differ in other exemplary embodiments, and such variations are intended to be covered by this disclosure.

[0092] Although various circuits with specific functionalities are shown in Figure 2, it should be understood that the controller 140 may comprise any number of circuits to complete the functions described herein. For example, the activities and functionalities of the regeneration management circuit 212 may be combined by multiple circuits or may be a single circuit. Further circuits with further functionalities may also be included. Furthermore, the controller 140 may further control other activities beyond the scope of this disclosure.

[0093] As described above, and in one configuration, “circuit” can be implemented in a machine-readable medium for execution by one or more processors of various types, such as processor 204 in Figure 2. Executable code can include, for example, one or more physical or logical blocks of computer instructions, which can be organized as, for example, objects, procedures, or functions. Nevertheless, executables do not need to be physically located together and can include asymmetric instructions stored in different locations, which, when physically joined together, constitute a circuit and achieve the purposes mentioned. In fact, a circuit of computer-readable program code can be a single instruction or many instructions. It can also be distributed across different programs and across several memory devices and several different code segments. Similarly, operational data can be embodied in any preferred form and organized in any preferred type of data structure, which can be identified and illustrated within a circuit as used herein. Operational data can be collected as a single dataset, distributed across different locations including different storage devices, and at least partially exist on a system or network simply as electronic signals.

[0094] Although the term “processor” is defined concisely above, the terms “processor” and “processing circuit” are meant to be interpreted broadly. In this regard, as stated above, “processor” can be interpreted 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 that have a structure that executes 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 external to the device; for example, one or more processors can be remote processors (e.g., cloud-based processors). Alternatively, or further, one or more processors can be internal to the device and / or local to the device. In this regard, a given circuit, or its components, can be located locally (e.g., as part of a local server, a local computer system, etc.) or remotely (e.g., as part of a remote server, such as a cloud-based server). For this purpose, the “circuit” described herein may include components distributed across one or more locations.

[0095] Embodiments within the scope of this disclosure include program products including a computer or machine-readable medium for carrying or having instructions or data structures stored therein that can be implemented by a computer or machine. Such a machine-readable medium can be any available medium accessible by a computer. The computer-readable medium can be a tangible computer-readable storage medium for storing computer-readable program code. The computer-readable storage medium can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of computer-readable mediums include, but are not limited to, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (ROM or flash memory), portable compact disc read-only memory (CD-ROM), digital multifunction discs (DVDs), optical storage devices, magnetic storage devices, holographic storage media, micromechanical storage devices, or any suitable combination thereof. In the context of this specification, a computer-readable storage medium can be any tangible medium that contains and / or can store computer-readable program code for use by and / or in connection with an instruction execution system, apparatus, or device. Examples of machine-executable instructions include instructions and data that cause a computer or processing machine to perform a particular function or a set of functions.

[0096] A computer-readable medium can also be a computer-readable signal medium. A computer-readable signal medium can include propagated data signals, for example, in the baseband or as part of a carrier wave, along with computer-readable program code embodied therein. Such propagated signals can take any of a variety of forms, including but not limited to electronic, electromagnetic, magnetic, optical, or any preferred combination thereof. A computer-readable signal medium can be any computer-readable medium, rather than a computer-readable storage medium, that can communicate, propagate, or transport computer-readable program code for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable program code embodied in a computer-readable signal medium can be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cables, radio frequency (RF), or any preferred combination thereof.

[0097] In one embodiment, the 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 both propagated by a processor as electromagnetic signals through fiber optic cables for execution and stored in a RAM storage device for execution by the processor.

[0098] For the purposes of this disclosure, computer-readable program code for performing operations may be written in any combination of a conventional procedural programming language, such as the C programming language or a similar programming language, and one or more other programming languages, including object-oriented programming languages ​​such as Java®, Smalltalk, and C++. The computer-readable program code may run entirely on the user's computer, as a standalone computer-readable package, partially on the user's computer, on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, via the Internet using an Internet service provider).

[0099] Program code can also be stored in a computer-readable medium that can issue instructions to a computer, other programmable data processing device, or other device to function in a particular way, such that the instructions stored in the computer-readable medium generate a manufactured article containing instructions to implement functions / operations specified in a schematic flowchart diagram and / or one or more schematic block diagram blocks.

[0100] While the figures and specifications may describe a specific order of method steps, such order of steps may differ from that described and described unless otherwise specified above. Furthermore, unless otherwise specified above, two or more steps may be performed simultaneously or partially simultaneously. Such variations may depend, for example, on the software and hardware systems selected, as well as on the designer's choice. All such variations are within the scope of this disclosure. Similarly, software embodiments of the described methods can be achieved by standard programming techniques using rule-based logic and other logic to accomplish various connection, processing, comparison, and decision steps.

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

Claims

1. It is a system, A controller connected to an engine and an after-treatment system that communicates with the engine to receive exhaust gas, the controller comprising at least one processor, and when executed by the at least one processor, the controller In an operator input device, the operator identifies a request for a regeneration process associated with a component of the post-processing system based on at least one of receiving an input or receiving operational data relating to the post-processing system from one or more sensors. Receiving a latch state associated with an operator interface device from at least one of the memory devices, wherein the latch state includes one of a first latch state or a second latch state. Receiving a time value associated with user input from at least one memory device in response to the latch state, which is the first latch state, The playback process is modified to a second latch state that responds to a time value that is a predetermined threshold or exceeds a predetermined threshold, so that the playback process can respond to receiving the request to the playback process. In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A system comprising a controller, which internally stores instructions for performing an operation including setting the time value to a predetermined value in response to the latch state, which is the second latch state.

2. The user input is a first user input, and receiving the latch state associated with the operator interface device is The operator interface device receives the first user input, The system according to claim 1, wherein the latch state responds to the operator interface device receiving a first signal from the operator interface device indicating that it is in the first latch state, in response to the operator interface device receiving the first user input.

3. Setting the time value to the predetermined value in response to the latch state, which is the second latch state, After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The system according to claim 2, wherein the latch state responds to the operator interface device receiving the second user input, and receiving a second signal from the operator interface device indicating that it is in the second latch state.

4. When the above instruction is executed by the at least one processor, The power state associated with the engine is determined based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine. Receiving the latch state from at least one memory device in response to the power state which is the first power state, The system according to claim 1, wherein the controller is instructed to perform a further operation, which includes modifying the latch state to a second latch state in response to the second power state.

5. The system according to claim 4, wherein the instruction, when executed by the at least one processor, causes the controller to perform further operations, including setting the time value to a predetermined value in response to the power state changing from the first power state to the second power state.

6. When the above instruction is executed by the at least one processor, Receiving an operating value from one or more of the sensors in response to the latch state, which is the second latch state, relating to at least one operating condition of the after-processing system or the engine, The regeneration process is implemented in response to the operation value which is a predetermined threshold or exceeds the predetermined threshold. The system according to claim 1, wherein the controller is instructed to perform a further operation, which includes preventing the regeneration process in response to the operation value falling below the predetermined threshold.

7. The system according to claim 1, wherein the time value is the amount of time between the current time value and the previous time value corresponding to the user input.

8. The system according to claim 1, wherein the regeneration process is a forced regeneration process.

9. The system according to claim 1, wherein the predetermined value is zero.

10. It is a method, Identifying a request for a regeneration process based on at least one of the following: receiving input in an operator interface device, or receiving operational data related to a post-processing system from one or more sensors; Receiving a latch state associated with the operator interface device, wherein the latch state includes one of a first latch state or a second latch state. In response to the latch state, which is the first latch state, the system receives a user input and a time value associated with that latch state. The playback process is modified to a second latch state that responds to a time value that is a predetermined threshold or exceeds a predetermined threshold, so that the playback process can respond to receiving the request to the playback process. In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A method comprising setting the time value to a predetermined value in response to the latch state, which is the second latch state.

11. The user input is a first user input, and the method is The operator interface device receives the first user input, The method according to claim 10, further comprising receiving a first signal from the operator interface device indicating that the latch state is the first latch state in response to the operator interface device receiving the first user input, wherein receiving the latch state is based on receiving the first signal.

12. After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The method according to claim 11, further comprising receiving a second signal from the operator interface device indicating that the latch state is the second latch state in response to the operator interface device receiving the second user input, and setting the time value to a predetermined value is in response to receiving the second signal.

13. Determining the power state associated with the engine based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine, Receiving the latch state from at least one memory device in response to the power state which is the first power state, The method according to claim 10, further comprising modifying the latch state to the second latch state in response to the power state which is the second power state.

14. The method according to claim 13, further comprising setting the time value to a predetermined value in response to the power state changing from the first power state to the second power state.

15. The system receives an operating value from one or more sensors in response to the latch state, which is the second latch state, relating to one or more operating conditions of the after-processing system or an engine connected to the after-processing system. The regeneration process is implemented in response to the operation value which is a predetermined threshold or exceeds the predetermined threshold. The method according to claim 10, further comprising preventing the regeneration process in response to the operation value falling below the predetermined threshold.

16. The aforementioned operating value is, The component temperature values ​​relating to the components of the post-processing system, The exhaust gas temperature value relating to the exhaust gas discharged by the aforementioned engine, or The method according to claim 15, comprising at least one speed value relating to the speed of the engine.

17. It is a device, At least one processor, When executed by the at least one processor, the at least one processor will Identifying a request for a replay process based on at least one of the following: receiving input from an operator input device, or receiving operational data related to the post-processing system from one or more sensors; Receiving a latch state associated with an operator interface device from at least one of the memory devices, wherein the latch state includes one of a first latch state or a second latch state. Receiving a time value associated with user input from at least one memory device in response to the latch state, which is the first latch state, The playback process is modified to a second latch state that responds to a time value that is a predetermined threshold or exceeds a predetermined threshold, so that the playback process can respond to receiving the request to the playback process. In response to the time value falling below the predetermined threshold, the regeneration process is prevented. A device comprising: at least one memory device that internally stores instructions for performing an operation including setting the time value to a predetermined value in response to the latch state, which is the second latch state.

18. The user input is a first user input, and when the instruction is executed by the at least one processor, the at least one processor is, The operator interface device receives the first user input, The apparatus according to claim 17, wherein the latch state is caused to perform a further operation, which includes receiving a first signal from the operator interface device indicating that the latch state is in response to the operator interface device receiving the first user input, and the receiving of the latch state is based on receiving the first signal.

19. When the above instruction is executed by the at least one processor, the at least one processor will: After receiving the first user input, and before the time value is the predetermined threshold or exceeds the predetermined threshold, the operator interface device receives a second user input. The apparatus according to claim 18, wherein the latch state is caused to perform a further operation, which includes receiving a second signal from the operator interface device indicating that the latch state is in response to the operator interface device receiving the second user input, and setting the time value to a predetermined value is in response to receiving the second signal.

20. When the above instruction is executed by the at least one processor, the at least one processor will: Determining the power state associated with the engine based on receiving information indicating a power state, including one of a first power state or a second power state, from at least one sensor associated with the engine, Receiving the latch state from at least one memory device in response to the power state which is the first power state, The latch state is modified to the second latch state in response to the second power state, The apparatus according to claim 17, which causes the device to perform a further operation including setting the time value to a predetermined value in response to a change in the power state from the first power state to the second power state.

Images