Initiating preparations for engine autostop prior to vehicle stop

Abstract

A stop/start vehicle includes at least one controller that, in response to predicting a vehicle stop, initiates an engine pre-shutdown protocol such that vehicle subsystems begin to prepare for engine shutdown prior to a speed of the vehicle reaching approximately zero to reduce time between the speed of the vehicle reaching approximately zero and engine shutdown.

Claims

1. A vehicle comprising: an engine; a vehicle component; and at least one controller configured to, in response to predicting a vehicle stop, initiate an engine pre-shutdown protocol for the vehicle component, prior to a speed of the vehicle reaching zero and prior to receiving a command to initiate engine auto-shutdown, at a time selected to permit completion of the engine pre-shutdown protocol prior to the speed reaching zero, and initiate the engine auto-shutdown after the speed reaches approximately zero.

2. The vehicle of claim 1 wherein the vehicle component is an intake manifold in fluid communication with the engine and wherein initiating the engine pre-shutdown protocol includes initiating a purge of the intake manifold.

3. The vehicle of claim 1 wherein the vehicle component is an electrical bus and wherein initiating the engine pre-shutdown protocol includes initiating a reduction of a voltage on the electrical bus to a predetermined value.

4. The vehicle of claim 1 wherein the vehicle component is an automatic transmission mechanically coupled with the engine and wherein initiating the engine pre-shutdown protocol includes initiating a shifting of gears of the automatic transmission.

5. The vehicle of claim 1 wherein the vehicle component is an electric pump and wherein initiating the engine pre-shutdown protocol includes initiating an activation of the electric pump.

6. A stop/start method comprising: in response to predicting a vehicle stop, initiating engine pre-shutdown preparations for at least one vehicle component, prior to vehicle speed reaching zero and prior to receiving a command to shut down the engine, at a time selected to permit completion of the engine pre-shutdown preparations prior to the vehicle speed reaching zero; and in response to the vehicle speed reaching approximately zero, shutting down the engine.

7. The method of claim 6 wherein the at least one vehicle component is an intake manifold in fluid communication with the engine and wherein initiating engine pre-shutdown preparations includes initiating a purge of the intake manifold.

8. The method of claim 6 wherein the at least one vehicle component is an electrical bus and wherein initiating engine pre-shutdown preparations includes initiating a reduction in voltage on the electrical bus to a predetermined value.

9. The method of claim 6 wherein the at least one vehicle component is an automatic transmission mechanically coupled with the engine and wherein initiating engine pre-shutdown preparations includes initiating a shifting of gears of the automatic transmission.

10. The method of claim 6 wherein the at least one vehicle component is an electric pump and wherein initiating engine pre-shutdown preparations includes initiating an activation of the electric pump.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a block diagram of a stop/start vehicle.

(2) FIGS. 2, 3 and 4 are flowcharts illustrating portions of algorithms for controlling a stop/start vehicle.

DETAILED DESCRIPTION

(3) Embodiments of the present disclosure are described herein. It is to be understood, however, that the disclosed embodiments are merely examples and other embodiments can take various and alternative forms. The figures are not necessarily to scale; some features could be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention. As those of ordinary skill in the art will understand, various features illustrated and described with reference to any one of the figures can be combined with features illustrated in one or more other figures to produce embodiments that are not explicitly illustrated or described. The combinations of features illustrated provide representative embodiments for typical applications. Various combinations and modifications of the features consistent with the teachings of this disclosure, however, could be desired for particular applications or implementations.

(4) Vehicle systems that are directly or indirectly influenced by operation of an engine are often prepared for an engine shutdown. That is, certain vehicle systems perform specified activities prior to engine shutdown. For example, an intake manifold may be purged to improve subsequent engine restart smoothness, a voltage on an electrical bus may be ramped down to reduce power consumption by electrical loads during engine off, an automatic transmission may shift gears in anticipation of vehicle launch after engine restart, an electric pump may be activated to maintain transmission line pressure during engine off, etc. Certain of these activities, such as purging the intake manifold, can be performed in fractions of a second while others, such as ramping down the voltage of the electrical bus, can take several seconds to complete. Hence, if these activities are initiated after vehicle speed has reached zero, valuable engine off time could be lost to pre-engine shut down protocols. Put another way, increasing the duration of time during which the engine is stopped while vehicle speed zero can increase fuel savings and emissions reductions.

(5) Certain systems, methods, algorithms, etc. disclosed herein can predict vehicle stops during a drive cycle and initiate engine pre-shutdown protocols prior to vehicle speed reaching zero so that the engine can be off for longer periods of time while the vehicle speed is zero.

(6) Referring to FIG. 1, an automotive vehicle 10 includes an engine 12, a transmission 14 and an alternator 16 each mechanically coupled with the engine 12 as indicated by heavy solid line. The vehicle 10 also includes an intake manifold 18 in fluid communication with the engine 12, an electric pump 20 in fluid communication with the transmission 14, and a fluid reservoir 22 in fluid communication with electric pump 20 as indicated by heavy dashed line. The vehicle 10 further includes a battery 24, an electrical bus 26, electrical loads 28 (e.g., a resistive heating element, infotainment systems, etc.), an accelerator pedal 30, a brake pedal 32, vehicle speed sensors 34, and one or more controllers 36. The alternator 16, electric pump 20, battery 24, and electrical loads 28 are electrically connected with the electrical bus 26 as indicated by thin dashed line. The engine 12, transmission 14, manifold 18, battery 24, electrical bus 26, accelerator pedal 30, brake pedal 32, and speed sensors 34 are in communication with/under the control of the controllers 36 as indicated by thin solid line. Other vehicle arrangements, of course, are also possible.

(7) The controllers (or stop/start system) 36 can issue auto stop commands (e.g., commands to stop the engine 12 during a drive cycle) and auto start commands (e.g., commands to start the engine 12 during a drive cycle). The engine 12 will be shutdown in response to auto stop commands and will be started in response to auto start commands as known in the art.

(8) Referring to FIGS. 1 and 2, it is determined whether vehicle speed is less than a threshold speed at operation 38. The controllers 36, for example, can compare speed data from the sensors 34 to some predetermined speed such as 5 miles per hour. If no, the algorithm returns to operation 38. If yes, it is determined whether an accelerator pedal is released or a brake pedal is pressed at operation 40. The controllers 36, for example, can determine whether position data associated with the accelerator pedal 30 and brake pedal 32 indicates that the accelerator pedal 30 is released or the brake pedal 32 is pressed. If no, the algorithm returns to operation 38. If yes, it is determined if there are any inhibit auto stop conditions present at operation 42. For example, the controllers 36 can check if any flags have been set to indicate that an auto stop of the engine 12 should be precluded. It may be determined in one instance that power demands by various vehicle subsystems exceed that which can be supported by the battery 24 alone. An auto stop inhibit flag is set in response. Other suitable/known auto stop inhibit conditions are also contemplated. If yes, the algorithm returns to operation 38.

(9) Referring to FIGS. 1 and 3, if no, engine pre-shutdown protocols for various vehicle components and a timer are initiated at operation 44. The controllers 36, for example, can cause the intake manifold 18 to be purged, the voltage on the electrical bus 26 to be reduced to some target value, the transmission 14 to be shifted, the electric pump 20 to be activated, etc. as mentioned above. Additionally, the controllers 36 can initiate a counter. At operation 46, it is determined whether the engine pre-shutdown protocols are complete. If no, the algorithm returns to operation 46. If yes, it is determined whether vehicle speed is approximately 0 at operation 48. For example, the controllers 36 can examine data from the sensors 34 to determine if it suggests that speed of the vehicle 10 is approximately 0. If yes, the engine is shutdown at operation 50. For example, the controllers 36 can cut fuel to the engine 12 and take other necessary steps to stop the engine 12 as known in the art. If no, it is determined whether the timer has expired or an auto stop inhibit condition is present at operation 52. The controllers 36, for example, can compare a current value of the counter to a threshold value. The controllers 36 also, for example, can check if any flags have been set to indicate that an auto stop of the engine 12 should be precluded as discussed above. If no, the algorithm returns to operation 48. If yes, the vehicle components affected by the engine pre-shutdown protocols are reset at operation 54. For example, the controllers 36 can cause the voltage on the electrical bus 26 to increase to the value it had prior to initiation of the engine pre-shutdown protocols, etc. The algorithm then returns to operation 38 (FIG. 2).

(10) In other implementations, all of the operations of FIG. 2 need not be performed prior to initiating engine pre-shutdown protocols. Operations 40 and 42, as an example, could be omitted. Operation 40, as another example, could be omitted, etc. A similar comment applies to FIG. 3. A timer, for example, need not be used. Other scenarios are also possible. Referring to FIG. 4, for example, it is determined whether vehicle deceleration is greater than a threshold at operation 38. For example, the controllers 36 can derive deceleration based on speed data from the sensors 34 and compare it to a threshold value such as 10 meters per second. If no, the algorithm returns to operation 38. If yes, time to vehicle stop is predicted at operation 40. The controllers 36, for example, can derive predicted time to stop based on the speed data and the deceleration (e.g., current vehicle speedcurrent vehicle deceleration=predicted time to vehicle stop). At operation 42, it is determined whether predicted time to vehicle stop is less than or equal to time to complete engine pre-shutdown protocol. Testing, simulation, etc. may be used to determine the time required to complete the engine pre-shutdown protocol for each affected vehicle component. As an example, the time required to reduce the voltage on the electrical bus from a current value to the desired value may be measured. As another example, the time to purge the intake manifold 18 may be measured. The vehicle component requiring the longest time to complete engine pre-shutdown activities may be used as the time to complete engine pre-shutdown protocol. The controllers 36 can, for example, compare the predicted time to vehicle stop to the time to complete engine pre-shutdown protocol. If no, the algorithm returns to operation 38. If yes, the algorithm proceeds to operation 44 (FIG. 3).

(11) The processes, methods, or algorithms disclosed herein may be deliverable to/implemented by a processing device, controller, or computer, which may include any existing programmable electronic control unit or dedicated electronic control unit. Similarly, the processes, methods, or algorithms may be stored as data and instructions executable by a controller or computer in many forms including, but not limited to, information permanently stored on non-writable storage media such as ROM devices and information alterably stored on writeable storage media such as floppy disks, magnetic tapes, CDs, RAM devices, and other magnetic and optical media. The processes, methods, or algorithms may also be implemented in a software executable object. Alternatively, the processes, methods, or algorithms may be embodied in whole or in part using suitable hardware components, such as Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), state machines, controllers or other hardware components or devices, or a combination of hardware, software and firmware components.

(12) While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms encompassed by the claims. The words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the disclosure. As previously described, the features of various embodiments can be combined to form further embodiments of the invention that may not be explicitly described or illustrated. While various embodiments could have been described as providing advantages or being preferred over other embodiments or prior art implementations with respect to one or more desired characteristics, those of ordinary skill in the art recognize that one or more features or characteristics can be compromised to achieve desired overall system attributes, which depend on the specific application and implementation. These attributes may include, but are not limited to cost, strength, durability, life cycle cost, marketability, appearance, packaging, size, serviceability, weight, manufacturability, ease of assembly, etc. As such, embodiments described as less desirable than other embodiments or prior art implementations with respect to one or more characteristics are not outside the scope of the disclosure and can be desirable for particular applications.