The present application generally relates to evaporative emissions (EVAP) systems and, more particularly, to diagnostic techniques for monitoring purge flow and detecting vapor canister leaks.
Conventional evaporative emissions (EVAP) systems include a vapor canister that evaporates from liquid fuel (e.g., gasoline) stored in a fuel tank of the vehicle. Engine vacuum is utilized to deliver the fuel vapor from the vapor canister to the engine through vapor transport lines and into intake ports of the engine. Vehicles are typically required to perform diagnostic routines on various components of the EVAP system to detect malfunctions (leaks, blockages, etc.). If unaddressed, malfunctions of the EVAP system could result in fuel vapor being released into the atmosphere.
Conventional EVAP system diagnostic routines, however, are typically intrusive. That is, these diagnostic routines are forced during engine operation, even at the expense of performance/fuel economy. Some conventional diagnostic routines also utilize additional testing components, such as passive mechanical devices, which potentially increases costs. Accordingly, while such EVAP systems work for their intended purpose, there remains a need for improvement in the relevant art.
According to a first aspect of the invention, a diagnostic system for an evaporative emissions (EVAP) system configured to control a flow of a fuel vapor is presented. In one exemplary implementation, the system includes a control valve connected between a vapor canister of the EVAP system and an air filter connected to an atmosphere, the control valve being configured to control an amount of air drawn through the air filter and the vapor canister; a pressure sensor configured to measure pressure in the EVAP system at a point (i) in the vapor canister, (ii) in a first vapor transport line between the vapor canister and a fuel tank, or (iii) in a second vapor transport line between the vapor canister and the control valve; and a controller configured to detect an engine idle-to-off transition and, in response to detecting the engine idle-to-off transition: receive a first pressure from the pressure sensor; after receiving the first pressure, (i) fully open a purge valve connected between the vapor canister and an intake port of an engine and (ii) fully close the control valve; after fully opening the purge valve and fully closing the control valve, monitor one or more second pressures received from the pressure sensor; and detect a malfunction of the EVAP system based on the first pressure, at least one of the one or more second pressures, and a diagnostic threshold.
According to a second aspect of the invention, a diagnostic method for an EVAP system configured to control a flow of a fuel vapor is presented. In one exemplary implementation, the method includes detecting, by a controller, an engine idle-to-off transition; and in response to detecting the engine idle-to-off transition: receiving, by the controller and from a pressure sensor, a first pressure, the pressure sensor being configured to measure pressure in the EVAP system at a point (i) in a vapor canister of the EVAP system, (ii) in a first vapor transport line between the vapor canister and a fuel tank, or (iii) in a second vapor transport line between the vapor canister and a control valve connected between the vapor canister and an air filter connected to an atmosphere; after receiving the first pressure, (i) fully opening, by the controller, a purge valve connected between the vapor canister and an intake port of an engine and (ii) fully closing, by the controller, the control valve, the control valve being configured to control an amount of air drawn through the air filter and the vapor canister; after fully opening the purge valve and fully closing the control valve, monitoring, by the controller, one or more second pressures received from the pressure sensor; and detecting, by the controller, a malfunction of the EVAP system based on the first pressure, at least one of the one or more second pressures, and a diagnostic threshold.
In some implementations, the malfunction is a blockage in the EVAP system. In some implementations, the controller is further configured to: determine a pressure difference between the first measured pressure and one of the one or more second measured pressures; and detect the blockage in the EVAP system when the pressure difference is less than the diagnostic threshold, wherein the diagnostic threshold is indicative of a minimum acceptable pressure difference for a properly functioning EVAP system. In some implementations, the blockage is in a third vapor transport line between the vapor canister and the purge valve.
In some implementations, the malfunction is a leak in the vapor canister. In some implementations, the controller is further configured to: determine a pressure decay rate based on the first pressure and the one or more second pressures; and detect the vapor canister leak when the pressure decay rate is greater than the diagnostic threshold, wherein the diagnostic threshold is indicative of a maximum acceptable pressure decay rate for a properly functioning EVAP system.
In some implementations, the engine idle-to-off transition is a transition from an engine idle period to an engine-off period in response to a key-off event. In some implementations, a throttle valve of the engine is fully-closed during the engine idle period such that substantial engine vacuum builds in an intake manifold of the engine that is connected to the intake port. In some implementations, opening the purge valve causes the substantial engine vacuum to be transferred into the EVAP system.
Further areas of applicability of the teachings of the present disclosure will become apparent from the detailed description, claims and the drawings provided hereinafter, wherein like reference numerals refer to like features throughout the several views of the drawings. It should be understood that the detailed description, including disclosed embodiments and drawings referenced therein, are merely exemplary in nature intended for purposes of illustration only and are not intended to limit the scope of the present disclosure, its application or uses. Thus, variations that do not depart from the gist of the present disclosure are intended to be within the scope of the present disclosure.
As previously mentioned, conventional diagnostics for evaporative emissions (EVAP) systems are intrusive and/or require additional componentry. Accordingly, improved diagnostic techniques are presented for detecting malfunctions of an EVAP system. These techniques leverage the transition from engine idle to engine-off. At engine idle, a throttle valve is fully closed and there is a large vacuum in an intake manifold of the engine. At the transition to engine-off, this vacuum is “transferred” to the EVAP system for diagnostic purposes. More particularly, a purge valve at an intake port of the engine is opened, which causes a pressure differential to be created in the EVAP system. This pressure differential is then utilized as part of a diagnostic routine for a component of the EVAP system, such as a leak or blockage in the vapor canister or one of the vapor transport lines.
Referring now to
Intake valves (not shown) control the flow of the air or air/fuel mixture into the cylinders 120. The air/fuel mixture is compressed by pistons (not shown) within the cylinders 120 and combusted (e.g., by spark plugs (not shown)) to drive the pistons, which rotate a crankshaft (not shown) to generate drive torque. Exhaust gas resulting from combustion is expelled from the cylinders 120 via exhaust valves/ports (not shown) and into an exhaust treatment system 132. The exhaust treatment system 132 treats the exhaust gas before releasing it into the atmosphere. An EVAP system 136 selectively provides fuel vapor to the engine 104 via the intake ports 124. While delivery via the intake ports 124 is shown and discussed herein, it will be appreciated that the fuel vapor could be delivered to the engine 104 directly into the cylinders 120.
The EVAP system 136 includes at least a vapor canister (not shown), a pressure sensor (not shown), and a control valve (not shown). The EVAP control system 136 is monitored and controlled by a controller 140. The controller 140 is any suitable controller or control unit for communicating with and commanding the EVAP system 136. In one exemplary implementation, the controller 140 includes one or more processors and a non-transitory memory storing a set of instructions that, when executed by the one or more processors, cause the controller 140 to perform a specific diagnostic technique. The controller 140 is configured to receive information from one or more vehicle sensors 144. Examples of the vehicle sensors 144 include a key on/off sensor for detecting key-on and key-off events.
Referring now to
The EVAP control system 136 includes a vapor canister 152 that traps fuel vapor that evaporates from liquid fuel stored in a fuel tank 156. This fuel vapor can be directed from the fuel tank 156 to the vapor canister 152 via a first vapor transport line 154, which could also be referred to as an evaporation line or duct. In one exemplary implementation, the vapor canister 152 includes (e.g., is lined with) activated carbon (e.g., charcoal) that adsorbs the fuel vapor. The fuel vapor trapped in the vapor canister 152 is selectively delivered to the intake port 124 of the engine 104 via the purge valves 148 and a third vapor transport line 162. As previously discussed, EVAP control systems utilize engine vacuum to draw fresh air (and trapped fuel vapor) through the EVAP system 136 for engine delivery.
Thus, the vapor canister 152 is also associated with a control valve 160 or other suitable controlled venting device that allows fresh air to be drawn through an air filter 164 and the vapor canister 152, thereby pulling the trapped fuel vapor with it. The vapor canister 152 and the control valve 160 are connected via a second vapor transport line 166. One example of the control valve 160 is a latching valve or a latching solenoid valve. Such valves require minimal current to remain in a specific state, and thus could be ideal for power consumption purposes. In one exemplary implementation, the control valve 160 is a device that is further configured to measure pressure in the second vapor transport line 166. Thus, in such implementations, a pressure sensor 168 could be eliminated.
The pressure sensor 168 is any suitable pressure sensor configured to measure a pressure a point in the EVAP system 136. This measurement point should be a point in the EVAP system 136 that is near the vapor canister 152, but is not in the third vapor transport line 166 between the vapor canister 152 and the engine 104. The reasoning for this is because engine vacuum is effectively transferred to the EVAP system 136 from the engine 104 for diagnostic purposes, and leaks/blockage are then monitored for at one of these other nearby measurement points, which is described in greater detail below. Non-limiting examples of the measurement point include (i) in the second vapor transport line 166, as described above, (ii) in the first vapor transport line 154, and (iii) within the vapor canister 152.
The controller 140 can control operation of the EVAP system 136 to perform the diagnostic techniques of the present disclosure. First, the controller 140 detects an engine idle-to-off transition. As previously discussed herein, at engine idle, there is a substantial engine vacuum (e.g., 40-50 kilopascals, or kPa) in the intake manifold 108 of the engine 104 compared to atmospheric pressure. This is because the throttle valve 116 is fully closed during the engine idle period. The intake manifold 108 is fluidly connected to the intake ports 124. Thus, by opening the purge valves 148, this engine vacuum is effectively transferred to the EVAP system 136 for diagnostic purposes. Thus, upon detecting a subsequent key-off event (e.g., using sensor 144), the controller 140 fully opens the purge valve 148 to create a pressure differential in the EVAP system 136. By doing so at the engine-off transition, this process is non-intrusive to engine operation.
Along with fully opening the purge valve 148, the controller 140 fully closes the control valve 160. By fully closing the control valve 160, the EVAP system 136 is fully closed off from the atmosphere, which provides for better diagnostic accuracy. After the engine idle-to-off transition, fully opening the purge valve 148, and fully closing the control valve 160, one or both of the diagnostic routines of the present disclosure are executable. As previously mentioned herein, the first diagnostic routine has to do with monitoring purge flow for verification or, in other words, detecting flow blockage in the EVAP system 136 (e.g., in the third vapor transport line 166). The second diagnostic routine, on the other hand, has to do with detecting leakage of the vapor canister 152 or its associated vapor transport lines 154, 162, 166.
The first diagnostic routine involves the controller 140 obtaining a first pressure from the pressure sensor 168 at a time at or before fully opening the purge valve 148 and fully closing the control valve 160. After a period of time, the controller 140 obtains a second pressure from the pressure sensor 168. During this period of time, a pressure differential has been created in the EVAP system 136. Due to blockage, however, the pressure in the EVAP system 136 could change less than expected. Thus, a pressure difference between the first and second pressures is determined by the controller 140 and compared to a diagnostic threshold. This diagnostic threshold is indicative of a minimum acceptable pressure difference for a properly functioning EVAP system 136. This diagnostic threshold could be preset or dynamically calibrated over time. When the pressure difference does not exceed this diagnostic threshold, the controller 140 detects a blockage malfunction of the EVAP system 136.
The second diagnostic routine similarly involves the controller 140 obtaining the first pressure from the pressure sensor 168 at a time at or before fully opening the purge valve 148 and fully closing the control valve 160. Over the following period of time, however, the controller 140 obtains at least one second pressure from the pressure sensor 168 as part of determining a pressure decay rate. This period, for example, could be much longer than the period for the first diagnostic routine. Preferably, the controller 140 also obtains a plurality of second pressures from the pressure sensor 168 over the period. These second pressure(s) are then used to determine a pressure decay rate in the EVAP system 136. The controller 140 then compares the pressure decay rate to the diagnostic threshold. For this routine, the diagnostic threshold is indicative of a maximum acceptable pressure decay rate for a properly functioning EVAP system 136. When the pressure decay rate exceeds this diagnostic threshold, the controller 140 detects a leakage in the vapor canister 152 or one of its associated vapor line 154, 162, 166.
Upon detecting one of the malfunctions discussed above, the controller 140 could perform some sort of action. One example action is setting a fault, such as by activating a malfunction indicator lamp (not shown). Another example action is adjusting operation of the engine 104, such as disabling the EVAP system 136 or commanding some sort of limp-home mode so the vehicle is able to reach a service center. It will be appreciated that other actions could be taken by the controller 140. It will also be appreciated that the controller 140 could implement some sort of bookkeeping process by which a number of malfunctions are counted and, once a threshold is reached, action is then taken by the controller 140. These diagnostic routines are also very robust and more accurate because they are executable during each operation cycle (engine off→on→off), as opposed to conventional techniques that operated periodically (e.g., only on cold starts).
Referring now to
At 320, the controller 140 detects a malfunction of the EVAP system 136 based on the first pressure, at least one of the one or more second pressures, and a diagnostic threshold. For the first diagnostic routine, blockage in the EVAP system 136 is detected when the pressure difference is less than the diagnostic threshold indicative of a minimum acceptable pressure difference for a properly functioning EVAP system 136. For the second diagnostic routine, on the other hand, vapor canister or associated vapor line leakage in the EVAP system 136 is detected when the pressure decay rate is greater than the diagnostic threshold indicative of a minimum acceptable pressure decay rate for a properly functioning EVAP system 136. The method 300 then ends or returns to 304 for one or more additional cycles (e.g., after a subsequent engine-on event).
As previously discussed, it will be appreciated that the term “controller” as used herein refers to any suitable control device or set of multiple control devices that is/are configured to perform at least a portion of the techniques of the present disclosure. Non-limiting examples include an application-specific integrated circuit (ASIC), one or more processors and a non-transitory memory having instructions stored thereon that, when executed by the one or more processors, cause the controller to perform a set of operations corresponding to at least a portion of the techniques of the present disclosure. The one or more processors could be either a single processor or two or more processors operating in a parallel or distributed architecture.
It should be understood that the mixing and matching of features, elements, methodologies and/or functions between various examples may be expressly contemplated herein so that one skilled in the art would appreciate from the present teachings that features, elements and/or functions of one example may be incorporated into another example as appropriate, unless described otherwise above.
Number | Name | Date | Kind |
---|---|---|---|
3888223 | Mondt | Jun 1975 | A |
5390645 | Cook et al. | Feb 1995 | A |
6318345 | Weber et al. | Nov 2001 | B1 |
6321727 | Reddy et al. | Nov 2001 | B1 |
6659087 | Reddy | Dec 2003 | B1 |
7077112 | Mitani et al. | Jul 2006 | B2 |
7566358 | Hart et al. | Jul 2009 | B2 |
8689613 | Perry | Apr 2014 | B2 |
9752521 | Dudar | Sep 2017 | B2 |
20030110836 | Cho | Jun 2003 | A1 |
20050240336 | Reddy | Oct 2005 | A1 |
20150019066 | Dudar et al. | Jan 2015 | A1 |
20150083089 | Pearce et al. | Mar 2015 | A1 |
20150322901 | Kragh | Nov 2015 | A1 |
20160194999 | Hakeem | Jul 2016 | A1 |
20170082038 | Dudar | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
2015049157 | Apr 2015 | WO |
Entry |
---|
U.S. Appl. No. 15/164,470, filed May 25, 2016, Roger C. Sager et al. |
U.S. Appl. No. 15/164,464, filed May 25, 2016, Joseph Dekar et al. |
U.S. Appl. No. 15/164,462, filed May 25, 2016, Joseph Dekar et al. |
Number | Date | Country | |
---|---|---|---|
20170342946 A1 | Nov 2017 | US |