Patent Application
20160186672
Emissions regulations for internal combustion engines have become more stringent over recent years. For example, the Environmental Protection Agency of the United States has been phasing in stricter emissions standards regarding hydrocarbon, particulate matter, and nitrogen oxide emissions for the last few years and will continue to do so. Environmental concerns have motivated the implementation of these stricter emission requirements for internal combustion engines throughout much of the world.
Many engine manufacturers have developed extensive aftertreatment systems that work to ‘clean-up’ the exhaust gas emitted from combustion cylinders so that the constituents of the exhaust gas leaving the tailpipe of an engine system (e.g., a vehicle or a generator) comply with the emissions standards. Filters and catalysts have been implemented, for example, to trap particulate matter, oxidize hydrocarbons, and reduce nitrogen oxides. However, many of these aftertreatment components are highly temperature dependent such that they are much more effective when maintained at a certain temperature.
When the temperature of the aftertreatment system is too low, several negative consequences may occur. First, the general efficiency and effectiveness of the aftertreatment system will diminish and emissions from the tailpipe may contain excessive amounts of harmful pollutants. Additionally, these pollutants, before exiting the aftertreatment system, may adsorb onto the surface of the various components (the filters and catalysts), thus reducing the active and effective surface area of those components. For example, a reduction catalyst may become clogged with adsorbed hydrocarbons. The adsorption of pollutants onto the various components of an aftertreatment system not only decreases the effectiveness of the system, but the clogged components may require repeated ‘regeneration’ procedures that require extra time and fuel. For example, a user may have to wait, without using the engine for a desired purpose, while the regeneration process occurs. Still further, adsorbed pollutants on the aftertreatment components, such as hydrocarbons adsorbed on a selective reduction catalyst, may eventually and suddenly burn off when the temperature of the system rises, thus resulting in an exothermic chain reaction that causes drastic temperature increases that can potentially damage components of the system.
The subject matter of the present disclosure has been developed in response to the present state of the art. Accordingly, the subject matter of the present disclosure has been developed to provide an apparatus, system, and method for thermal management of an exhaust gas aftertreatment system via cylinder deactivation based on an engine operating state and the time within which the engine has been in that operating state.
One embodiment relates to an apparatus for an engine. The apparatus includes an engine load module structured to detect an engine operating state of the engine and generate an engine status report; a timing module structured to receive the engine status report and generate a cylinder request after the engine has been in a certain engine operating state for a certain period of time; and a cylinder module structured to receive the cylinder request and generate a cylinder command to be sent to the engine to deactivate a portion of combustion cylinders based on the engine operating state existing for the certain period of time. In one embodiment, the timing module determines a low load operating state existing for a certain period of time and generates a cylinder request to deactivate a portion of the combustion cylinders. In turn, the activated cylinders increase their power output to compensate for the deactivated cylinders which lead to an increase in combustion temperatures and, therefore, exhaust gas temperatures. The increased exhaust gas temperatures substantially prevent particulate matter accumulation, ammonia accumulation, hydrocarbon formation, and other unwanted effects in the exhaust aftertreatment system that may occur when the exhaust gas temperatures are relatively low.
Another embodiment relates to an engine system for changing the temperature of an exhaust gas stream. The system includes a plurality of combustion cylinders in an engine; an exhaust gas aftertreatment sub-system fluidly connected downstream of the plurality of combustion cylinders; an engine load module structured to detect an engine operating state of the engine and generate an engine status report; a timing module structured to receive the engine status report and generate a cylinder request after the engine has been in a certain engine operating state for a certain period of time; and a cylinder module structured to receive the cylinder request and generate a cylinder command to be sent to the engine to activate or deactivate a portion of the combustion cylinders, wherein activating or deactivating a portion of the combustion cylinders changes the temperature and hydrocarbon content of an exhaust gas stream in the exhaust gas aftertreatment sub-system.
Still another embodiment relates to method of increasing the exhaust gas temperature based on an engine operating state existing for a predetermined amount of time. The method includes detecting an engine operating state of an engine; timing how long the engine has been in a certain engine operating state; and deactivating a portion of combustion cylinders of the engine after the engine has been in the certain operating state for a certain period of time.
The described features, structures, advantages, and/or characteristics of the subject matter of the present disclosure may be combined in any suitable manner in one or more embodiments and/or implementations. In the following description, numerous specific details are provided to impart a thorough understanding of embodiments of the subject matter of the present disclosure. One skilled in the relevant art will recognize that the subject matter of the present disclosure may be practiced without one or more of the specific features, details, components, materials, and/or methods of a particular embodiment or implementation. In other instances, additional features and advantages may be recognized in certain embodiments and/or implementations that may not be present in all embodiments or implementations. Further, in some instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the subject matter of the present disclosure. The features and advantages of the subject matter of the present disclosure will become more fully apparent from the following description and appended claims, or may be learned by the practice of the subject matter as set forth hereinafter.
In order that the advantages of the subject matter may be more readily understood, a more particular description of the subject matter briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the subject matter and are not therefore to be considered to be limiting of its scope, the subject matter will be described and explained with additional specificity and detail through the use of the drawings, in which:
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the subject matter of the present disclosure should be or are in any single embodiment of the subject matter. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the subject matter of the present disclosure. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment.
As described above, conventional aftertreatment systems have been implemented with many engine systems to reform exhaust gas emitted from the combustion cylinders. However, when the temperature of the aftertreatment system falls below a certain threshold, the engine system is plagued with various problems, as discussed above. Specifically, the effectiveness of the aftertreatment system decreases, hydrocarbon pollutants adsorb and build-up on the surface of the aftertreatment components, and the potential for destructive exothermic chain reactions increases. These problems are most prevalent when the engine is running in light load operation, which results in a comparatively lower exhaust gas temperature. The present disclosure relates to a controller apparatus, a system, and a method for managing the temperature of the exhaust gas via cylinder deactivation/reactivation. Throughout the present disclosure, many details are included referring to deactivating combustion cylinders to increase exhaust gas temperature (see below). As used herein, when one or more combustion cylinders are deactivated, the engine is operating in a combustion cylinder deactivation mode.
Although not discussed in as much detail, the same general principles apply for reactivating the deactivated combustion cylinders. For example, if the demand placed on the engine exceeds what the engine with deactivated cylinders is able to generate, then the controller, system, and method of the present disclosure may also be implemented to reactivate the cylinders. At which point, the engine is operating in a normal operation mode (i.e., no combustion cylinder deactivations).
The aftertreatment subsystem 60 is structured to receive exhaust gas from the engine 50 and reduce the pollutants (e.g., nitrogen oxides, particulate matter, hydrocarbons, etc.) in the exhaust gas to thereby expel a relatively less pollutant exhaust gas into the environment. The aftertreatment subsystem 60 may include a variety of components. For example, the aftertreatment subsystem 60 may include a particulate filter, an oxidation catalyst, and a selective reduction catalyst, among other components. As described above, the activity and effectiveness of the various components are often highly dependent on temperature. At relatively higher temperatures (e.g., greater than 500 degrees Celsius), the following events tend to occur: ammonia, used to reduce nitrogen oxide (NOx) emissions to NO2 and other less harmful products, is decomposed (e.g., burned off from the higher temperatures); NOx conversion to less harmful products, such as NO2, increases; accumulated particulate matter is more likely to be regenerated (e.g., burned away); and the rate at which hydrocarbon, particulate matter, and/or water is collected or adsorbed by the system is reduced. At relatively lower exhaust gas temperatures (e.g., less than 250 degrees Celsius), ammonia is less likely to be decomposed; particulate matter, hydrocarbons, and water are more likely to collect within the system; and NOx conversion efficiency decreases. Thus, the successful and efficient conversion of harmful pollutants exiting the cylinders 52 of the engine 50 as exhaust gas 58 into non-toxic chemicals, such as water vapor, carbon dioxide, and nitrogen, is largely dependent on the temperature of the exhaust gas stream 58 itself. The modules 110, 120, 130 of the controller 100 are configured to control the exhaust gas temperature via cylinder deactivation.
The engine load module 110 interacts with the engine 50 to determine an engine operating state 112. The engine operating state 112 may include any information relating to the operating condition of the engine 50. For example, the engine load module 110 may interact with detectors and/or sensors to monitor the speed—revolutions-per-minute (RPM)—of the engine. In one embodiment, the engine load module 110 may also detect other operating variables, such as fuel rail pressure, charge flow, injection timing, etc. In another embodiment, the engine load module 110 may not use physical or actual measuring devices but may instead receive information from the main electronic control module of the engine. For example, torque demands, acceleration demands, torque limits, and other requests from the main electronics control module may be received by the engine load module 110 to determine the engine operating state 112. In a further embodiment, the engine load module 110 may be configured to continually and periodically take measurements or receive information. In another embodiment, the engine load module 110 may be configured to only monitor the engine conditions when a user has indicated such monitoring via a user interface.
The engine operating state 112 may include a low load operating condition of the engine 50. The low load operating condition may indicate that at least one of an engine torque and an engine speed (actual or demanded) are below a preset threshold. In another embodiment, the low load operating condition may indicate that the load on the engine itself (measured, determined, estimated, etc.) is below a preset threshold. Based on the engine used, the preset thresholds are likely to vary application-to-application. As mentioned above, values indicative of a low load operating state (e.g., engine speed, engine torque, load itself) may be measured, determined via one or more algorithms, processes, models, look-up tables, and/or otherwise estimated based on operation of the engine. In addition to engine torque, engine speed, and the load itself, other operating conditions may also be used to indicate that the engine is in a low load operating condition. In one embodiment, the gear or transmission setting may be used to indicate a low load operating state. For example, if the transmission setting is neutral, the engine load module 110 may determine that the engine is in a low load operating condition. In another embodiment a vehicle embodiment, if the vehicle speed is below a preset threshold (e.g., 5 miles-per-hour), the engine load module 110 may determine that the engine is in a low load operating condition. In still another embodiment, the engine load module 110 module may receive the fueling commands for the engine 50 and determine the engine is in a low load operating state based on the fueling commands. For example, if the fueling rate and/or amount are below a threshold. In still other embodiments, a combination of the aforementioned parameters (and others) may be used to determine that the engine is in a low load operating condition. For example, the speed of the engine 50, the injection timing, and the rate of fuel delivery into the combustion cylinders 52, may collectively indicate a low load operating condition. According to another embodiment, the engine load module 110 may indicate a low load′ status 114 that is based solely on, for example, one parameter (e.g., when the engine is operating at lower than 700 RPM). Thus, many parameters may be used to indicate a low load operating condition with such designations being configurable based on the application. Accordingly, it should be also understood that many other parameters may also be used to indicate a low load operating condition with all such parameters intended to be within the spirit and scope of the present disclosure.
In addition to a low load operating condition, the engine operating state 112 may also include ‘medium’ and/or ‘high load’ operating conditions (and any operating condition there between; thus, a spectrum may be used in some embodiments). Like the low load operating condition, the medium and/or high load operating conditions may be demarcated based on preset thresholds using one or more parameters like that described above. For example: engine speeds greater than 1,200 RPM may indicate a high load condition; engine torques between 250 pound-foots and 400 pound-foots may indicate a medium load condition; engine loads greater than 250 horsepower may indicate a high load condition; etc. The values used above are for example purposes only. Based on the application, these values are likely to change such that many different thresholds may be used to indicate operating states of the engine 50.
The engine load module 110 is also structured to generate an engine status report 114 that is sent to the timing module 120 (described below). The engine status report 114 may include interpretations, analyses, and the like based on the engine operating state 112. Thus, the engine status report 114 describes a determination of the current load placed on the engine 50, whether actual or demanded. As described above, the description of the current load may be based on a variety of different parameters that, in some embodiments, are compared against preset thresholds indicative of an operating state, such as a low load operating state (e.g., the fueling rate/amount is below a threshold, the engine torque is below a threshold, etc.). The threshold designations may be based on the application and configurable (e.g., a user may set certain operating conditions that when experienced, indicate a certain operating state of the engine).
In certain other embodiments, the controller 100 may also include an aftertreatment condition module that functions in a similar manner as the engine load module 110. But, instead of receiving/detecting information about the operation of the engine (e.g., engine operating state 112), the aftertreatment condition module receives/detects information about the operation of the aftertreatment subsystem 60. For example, the aftertreatment module may monitor component surface temperatures, catalyst bed temperatures, fluid flow temperatures, etc. Based on the monitoring, the aftertreatment condition module may generate an aftertreatment status report, instead of an engine status report 114, which is sent to the timing module 120. If one or more of the temperatures are below a threshold for a certain amount of time, the controller 100 may generate a command to initiate a combustion cylinder deactivation mode (and, in some embodiments, provide one or more other thermal management commands) to increase the exhaust gas temperature. This structure and functionality is analogous to that of the engine load module 110, timing module 120, and cylinder module 130 but is instead focused on the aftertreatment system itself. The aftertreatment module, like described above, may be used to complement the function and structure of the controller 100 to aid efficient operation of the aftertreatment system. Accordingly, some embodiments may include this aftertreatment condition module while others may not.
The timing module 120 is structured to receive the engine status report 114 from the engine load module 110. Based on the engine status report 114, the timing module 120 generates a cylinder request 122 that is provided to the cylinder module 130. The timing module 120 is structured to determine when, if at all, cylinder activation/deactivation should be implemented (e.g., when combustion cylinder deactivation mode should be initiated). The timing module 120 monitors the period of time during which the engine 50 is operating under a certain status (i.e., in a certain state). For example, the engine status report 114 may indicate that the engine 50 is currently operating under a low load′ condition. The timing module 120 receives such information and begins a timer to monitor how long the engine has been operating in such a condition. If the timing module 120 determines the engine 50 has been under a certain operating condition for a certain period of time, the timing module 120 may then generate a cylinder request 122 to be sent to the cylinder module 130.
In one embodiment, the cylinder request 122 calls for a portion 54 of the combustion cylinders 52 to be deactivated. The portion requested to be deactivated may be based on the engine configuration (e.g., inline, v-formation, etc.) and may be configurable. In one embodiment, a default deactivation strategy may be fifty percent of the combustion cylinders. For example, in a sixteen cylinder engine, the number of cylinders deactivated may be eight cylinders. In other embodiments, greater than or less than half of the combustion cylinders may be requested to be deactivated. In the sixteen cylinder engine, for example, two, four, six, eight, ten, etc., cylinders may be deactivated depending on the specifics of a given application.
The cylinder request 122 may be based upon a predetermined or a configurable timing variable. In other words, the timing module 120 may include predetermined timing parameters pertaining to each different operating status 114 of the engine 50. For example, if the status report 114 indicates that the engine is in low load′ operation for a certain time period (as determined or timed by the timing module 120), the timing module 120 may then send a request 122 to the cylinder module 130 to deactivate a portion of the combustion cylinders. In one embodiment, the certain time period may be zero seconds. Thus, if the engine status report 114 indicates a certain condition (i.e., low load′), the timing module 120 may immediately request a portion of the cylinders to deactivate. In another embodiment, the certain time period may be greater than zero seconds, such as 30 seconds. In yet another embodiment, the certain time period may be a matter of minutes or longer (depending on the specific purpose/use of the engine). If the timing module 120 determines that a certain operating state (e.g., low load) has existed for that certain time period, the cylinder request 122 calls for a portion of the combustion cylinders to be deactivated.
In one embodiment, the certain time period may be configurable or programmable according to user input or may be application specific. For example, if a user is contemplating a situation where the engine will experience oscillating or constantly fluctuating demand, the user may set the time period for a longer time (e.g., thirty seconds) so as to not introduce cylinder deactivation prematurely (e.g., to avoid cylinder deactivation during transient events). In another embodiment, depending on the specific application of an engine, a technician may calibrate the timing module 120 to correspond with the dynamic conditions that the engine is expected to experience during the engine's operational lifetime. In yet another embodiment, the timing module may also take into consideration engine governors and secondary engine systems, such as upper and lower torque limits. For example, the timing module 120 may automatically and temporarily extend the certain time period to infinity (i.e., prevent cylinder deactivation) due to a low torque limit imposed upon the engine by a secondary engine system.
In one embodiment, the cylinder command 132 includes additional thermal management commands. The additional thermal management commands are structured to complement the cylinder deactivation mode and increase a temperature of the exhaust gas. The additional thermal management commands may include, but are not limited to, a valve actuation command that alters the opening and closing of a fuel valve or the opening and closing of the intake and exhaust valves in an engine; retarding an injection timing to ensure a relatively greater amount of compression and therefore temperature in the cylinder; internal hydrocarbon dosing; external hydrocarbon dosing; post injection of fuel after the combustion event in the cylinder; a wastegate opening to control a speed of the turbocharger; closing an intake throttle; closing an exhaust throttle; adjusting a turbocharger to increase restriction across a turbine; adjusting a turbocharger to lower a speed of the turbocharger; increasing a speed of the engine; and the like. The additional thermal management commands may also include other actuation instructions, such as altering the pushrod and/or camshaft dynamics, in order to prevent fuel flow into the deactivated cylinders 54. As briefly stated above, the additional thermal management commands included with the cylinder command 132 may also include actuation instructions relating to the still-active cylinders 53 as well. For example, in order to maintain the power supply, the cylinder command 132 may call for an increase in fuel to be injected into the still active cylinders 53 or for the RPM rate to increase. Other parameters, including those mentioned above, may also be adjusted, such as injection timing, and fuel injection pressure to increase the exhaust gas temperature. It should be understood that the aforementioned list is not meant to be limiting as other commands may also be included that are structured to increase the temperature of the exhaust gas. All such commands are intended to be within the spirit and scope of the present disclosure.
In one embodiment, the rate of fuel injected into the active cylinders 53 is increased relative to the rate that was provided in a time period immediately preceding the deactivation request (i.e., when no cylinders were deactivated). In one embodiment, the rate of fuel injected is double what was originally being provided during a time period immediately preceding the deactivation request where no combustion cylinders were deactivated in order to meet the power demand/load placed on the engine. The time period preceding the deactivation request may be predefined and configurable. To ensure that operation of the engine continues smoothly when entering a cylinder deactivation mode, the time period may be relatively short (e.g., one minute). In other embodiments, a distance period may be used in place of the time period (e.g., past one mile). In either configuration, the increase in fuel rate may correspond with the power output in the immediately preceding period. Thus, the power from the engine following the deactivation request may correspond with the power substantially needed right before the deactivation request. As such, when embodied in a vehicle, the operator may be relieved from feeling a change in operating conditions as the power output stays relatively constant. In another embodiment, the fueling rate may increase based on the number of cylinders deactivated relative to the total number of cylinders. For example, if fifty percent of cylinders are deactivated, the rate of fuel injected may double (i.e., (percent of cylinders deactivated)×2); if forty percent of cylinders are deactivated, the fuel rate may be increased by eighty percent; etc. In this regard, the fuel rate injected is constant relative to the period immediately preceding the deactivation request. In another embodiment, the fuel rate may be adjusted to maintain the engine torque output relative to the engine torque output provided in the period immediately preceding the output request. An engine torque sensor may be utilized to ensure that fueling is increased until the current torque output from the engine reaches that of the period immediately preceding the request. The torque output from the preceding period may be an average experienced, a minimum, a median value, a maximum, and any other chosen parameter indicative of the torque of preceding period (e.g., most recently experienced prior to deactivation mode or most recently experienced torque level prior to the low load operating state being determined).
With a higher fuel injection rate in the still active cylinders 53, the temperature of the exhaust gas increases due to an increased chemical energy input (e.g., the fuel) that causes a higher power output with corresponding exhaust temperatures. This may result in the hydrocarbon content in the exhaust gas decreasing. In one embodiment, the decrease in the hydrocarbon content may be an indirect result caused by the increased temperature. In other words, as the temperature increases, any remaining hydrocarbons in the exhaust gas are oxidized, either in the combustion cylinders themselves or later in the exhaust conduits before reaching some of the aftertreatment components.
In one embodiment, once the engine has been switched to a combustion cylinder deactivation mode, the cylinder module 130 may be configured to switch the referenced fuel table in a main electronic control module to a ‘deactivated’ cylinder fuel table. In one embodiment, there may be multiple fuel tables available for reference depending on the specifics of a given application and the details relating to the number of cylinders deactivated. Additionally, the cylinder module 130 may alternate which cylinders 52 are to be deactivated. For example, the cylinder module 130 may switch back and forth between which half of cylinders are deactivated each time a new cylinder request 122 is received from the timing module 120. In another embodiment, the cylinder module 130 may include a timing element of its own and may periodically and systematically switch the active cylinders without waiting for a request from the timing module 120. By switching/toggling the active bank of cylinders, the cylinders wear evenly, thus preventing any potential problems that may arise if one bank or one half of the cylinders is more frequently deactivated. As described above, the engine cylinders 52 may be in an inline configuration, a V configuration, or any other cylinder configuration (e.g., a W configuration). Accordingly, fuel tables corresponding with the active portion of combustion cylinders may be referenced by the cylinder module 130 to enable efficient operation of the engine.
An example operation of the controller apparatus 100 may be described in regard to
At process 502, an engine operating state is detected. The engine operating state may correspond with a load experienced by the engine. In some embodiments, the operating state may include, but is not limited to, a low load operating condition, a medium load operation condition, and a high load operating condition. In other embodiments, a spectrum may be used that represents a gamut of for loads experienced by the engine. As described above, the operating state may be determined based on one or more operating parameters (e.g., engine torque, engine load (determined, measured, estimated, etc.), engine speed, fueling commands, etc.). The determined, measured, and/or estimated operating parameters may be compared against preset thresholds indicative of each operating state for the engine. In the example of FIG. 4, the engine load module 110 determines that the engine is operating in a low load condition. In
After the operating state has been determined, at process 504, it is timed how long the engine has been in that operating state. This is performed by the timing module 120. In regard to
In certain embodiments, switching of the activated/deactivated portion of the combustion cylinders may also occur during process 506, which corresponds with the cylinder deactivation mode. In turn, combustion cylinder wear may be spread relatively evenly amongst all the combustion cylinders. In one embodiment, switching is based on a time duration (e.g., every five seconds). As mentioned above, switching may also be based on when each cylinder request 122 is received, such that each request switches the combustion cylinders between activated and deactivated. Although only two switching strategies are described above, it should be understood that many switching strategies are possible with all such strategies intended to be within the spirit and scope of the present disclosure.
Finally, a return to a normal operating mode (e.g., disengagement of the cylinder deactivation mode) may be based on a variety of parameters. This step may be included as part of process 506. One parameter may include a time duration. For example, there may be preprogrammed times for how long cylinder deactivation mode can last (e.g., ten minutes). Another parameter may be a change in operating conditions. For example, the engine load module 110 may continuously measure, estimate, or otherwise determine the load on the engine. If the load (or other parameter, such as fueling rate) indicates that a low load operating state is no longer present, the cylinder request 122 may be to return to normal operating mode because the exhaust gas temperatures may be likely or will be likely sufficient to prevent accumulation of particulate matter and other harmful effects that occur during low temperature exhaust gas situations. Still another parameter may be temperature measurements made in the exhaust gas aftertreatment system. In this embodiment, cylinder deactivation mode may continue until the temperature reaches a certain threshold. Although described as independent, these parameters may be also examined collectively. For example, the cylinder request 122 may be to continue cylinder deactivation mode until the temperature measurement in the exhaust gas reaches a certain threshold or the engine is no longer in a low load operating state, whichever occurs first. Thus, many parameters may be used to designate a return to normal operating mode.
Accordingly, referring back to
At point 410, the controller changes the engine calibration, which indicates that the fuel tables and any other commands (e.g., closing of deactivated combustion cylinder intake valves) are implemented (or are in the process of being implemented) to begin the cylinder deactivation mode. These commands correspond with commands to run the cylinder deactivation mode (e.g., an increase or decrease to a common rail pressure). In
As shown in
As mentioned above, at point 410, cylinder deactivation mode is commanded by the cylinder module 130. Point 410 corresponds with a particular exhaust gas temperature threshold on the y-axis. This exhaust gas temperature threshold may correspond with when cylinder deactivation mode is initiated after a certain engine operating condition (e.g., low load) has been detected for a certain amount of time. The exhaust gas temperature threshold may be preset based on the application (e.g., engine-aftertreatment system) and/or estimated/predicted/modeled using one or more look up tables, formulas, algorithms, and the like based on one or more pieces of engine operation data (e.g., fuel type, engine speed, engine torque, fuel-to-air ratio, etc.). In other embodiments, the exhaust gas temperature threshold may be determined in real time based on one or more engine parameters (e.g., below a temperature that causes or is likely to cause engine knock). Upon reaching this threshold, cylinder deactivation mode may be initiated by module 130. As mentioned above, the exhaust gas temperature threshold may vary for any engine-exhaust gas aftertreatment system combination, such that many temperature thresholds are possible based on the application.
According to one embodiment, thermal management commands are provided until the exhaust gas temperature threshold is reached (point 410 in
As mentioned above, according to various other embodiments, cylinder deactivation mode may be initiated immediately after determining that a certain engine operating condition exists for a certain amount of time. In these instances, no threshold engine exhaust gas temperature preset may be used. As such, any additional thermal management commands may be used to increase the rate at which the exhaust gas temperatures rise without regard to an exhaust gas temperature threshold. All such variations are intended to fall within the spirit and scope of the present disclosure.
It should be understood that
In the above description, certain terms may be used such as “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
Additionally, instances in this specification where one element is “coupled” to another element can include direct and indirect coupling. Direct coupling can be defined as one element coupled to and in some contact with another element. Indirect coupling can be defined as coupling between two elements not in direct contact with each other, but having one or more additional elements between the coupled elements. Further, as used herein, securing one element to another element can include direct securing and indirect securing. Additionally, as used herein, “adjacent” does not necessarily denote contact. For example, one element can be adjacent another element without being in contact with that element.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the subject matter of the present disclosure. Appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment. Similarly, the use of the term “implementation” means an implementation having a particular feature, structure, or characteristic described in connection with one or more embodiments of the subject matter of the present disclosure, however, absent an express correlation to indicate otherwise, an implementation may be associated with one or more embodiments.
The schematic flow chart diagrams included herein are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of one embodiment of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of computer readable program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of computer readable program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the computer readable program code may be stored and/or propagated on in one or more computer readable medium(s).
The computer readable medium may be a tangible computer readable storage medium storing the computer readable program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples of the computer readable medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, and/or store computer readable program code for use by and/or in connection with an instruction execution system, apparatus, or device.
The computer readable medium may also be a computer readable signal medium. A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electrical, electro-magnetic, magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and 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 on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), or the like, or any suitable combination of the foregoing
In one embodiment, the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums. For example, computer readable program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.
Computer readable program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
The subject matter of the present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application is a continuation of International Application No. PCT/US2014/054241, filed Sep. 5, 2014, entitled “THERMAL MANAGEMENT OF EXHAUST GAS VIA CYLINDER DEACTIVATION,” which claims the benefit of priority of U.S. Provisional Patent Application No. 61/874,868, filed Sep. 6, 2013, entitled “THERMAL MANAGEMENT OF EXHAUST GAS VIA CYLINDER DEACTIVATION,” both of which are incorporated herein by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| 61874868 | Sep 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2014/054241 | Sep 2014 | US |
| Child | 15061516 | US |
