Battery state of charge control using route preview data

• US 9,809,214 B2
• Filed: 05/06/2015
• Issued: 11/07/2017
• Est. Priority Date: 05/06/2015
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: Liang, Wei, Zhao, Yanan, Kuang, Ming Lang
• Primary Examiner(s): BUTLER, RODNEY ALLEN
• Application Number:
  US14/705,314
• Publication Number:
  US 20160325726A1
• Time in Patent Office: 916 Days
• CPC Class Codes: B60K 6/48 Parallel type
• CPC Class Codes: B60W 10/06 including control of combustion engines
• CPC Class Codes: B60W 10/08 including control of electric propulsion units, e.g. motors or generators
• CPC Class Codes: B60W 20/12 using control strategies taking into account route information estimation or calculation of non-directly measurable driving parameters B60W40/00
• CPC Class Codes: B60W 2510/244 Charge state
• CPC Class Codes: B60W 2556/50 of positioning data, e.g. GPS [Global Positioning System] data
• CPC Class Codes: Y02T 10/62 Hybrid vehicles
• CPC Class Codes: Y10S 903/93 Conjoint control of different elements

Abstract

A vehicle includes an engine and at least one controller. A first engine cycling command based on route information and a second engine cycling command independent of route information are generated. The engine transitions state according to the first engine cycling command when the second engine cycling command permits the transition. When a first engine cycling profile based on route information includes at least a number of engine cycles, the engine is cycled according to the first engine cycling profile, otherwise, the engine is cycled according to an engine cycling state derived independent of route information. The vehicle includes a traction battery. A state of charge of the traction battery is controlled according to a target state of charge that is derived using route information and a base battery power reference that is independent of route information.

Claims

1. A vehicle comprising:

a navigation system configured to provide predicted speed and grade profiles;

a traction battery;

an engine; and

a controller programmed to (i) generate engine commands including engine off requests and commands permissive of engine off requests, and, in response to a first engine cycling command based on the profiles being an engine off request and a second engine cycling command derived independent of the profiles being permissive of engine off requests while the engine is on, cause the engine to transition to off and (ii) generate a target state of charge for the traction battery based on the profiles and a base battery power reference independent of the profiles, and, in response to the first engine cycling command defining at least a predetermined number of engine cycles over a route, charge and discharge the traction battery based on the target state of charge and the base battery power reference.

2. The vehicle of claim 1 wherein the engine cycling commands further includes engine on requests and commands inhibiting engine off requests and the second engine cycling command is permissive of the engine off request when the second engine cycling command is not an engine on request and the second engine cycling command is not a command inhibiting engine off requests.

3. The vehicle of claim 1 wherein the engine cycling commands further include engine on requests and commands permissive of engine on requests, and the controller is further programmed to, in response to the first engine cycling command being an engine on request and the second engine cycling command being permissive of engine on requests while the engine is off, cause the engine to transition to on.

4. The vehicle of claim 1 wherein the target state of charge for the traction battery is within a first predetermined state of charge range.

5. The vehicle of claim 4 wherein the base battery power reference is a power level selected to control a state of charge of the traction battery within a second predetermined state of charge range that includes the first predetermined state of charge range.

6. The vehicle of claim 4 wherein the controller is further programmed to, in response to the first engine cycling command defining less than the predetermined number of engine cycles over the route, charge and discharge the traction battery according to the base battery power reference, wherein the base battery power reference is based on a present driver power demand, a state of charge of the traction battery and battery maintenance state of charge limits.

7. The vehicle of claim 1 wherein the controller is further programmed to, in response to the first engine cycling command defining less than a predetermined number of predicted engine cycles over a route, operate the engine according to the second engine cycling command.

8. The vehicle of claim 7 wherein the first engine cycling command defines less than a predetermined number of engine cycles when one or more of (i) a predicted vehicle speed profile is greater than a predetermined speed over a route, and (ii) a predicted driver power demand profile is greater than a predetermined power over the route.

9. A vehicle comprising:

an engine; and

a controller programmed to receive a predicted power demand profile from a navigation system and, in response to generating an engine cycling profile from the predicted power demand profile having a number of engine on/off cycles greater than a predetermined number, cycle the engine according to the engine cycling profile, and otherwise, cycle the engine according to an engine cycling state derived from a present driver power demand.

10. The vehicle of claim 9 wherein the controller is further programmed to command the engine according to the engine cycling state when the engine cycling state inhibits a transition requested by the engine cycling profile.

11. The vehicle of claim 9 wherein the controller is further programmed to command the engine according to the engine cycling state when the engine cycling state requests an engine state having greater priority than the engine cycling profile.

12. The vehicle of claim 9 further comprising a traction battery and wherein the controller is further programmed to, in response to the engine cycling profile having the number of engine on/off cycles greater than the predetermined number, charge or discharge the traction battery according to a target state of charge profile derived from the predicted power demand profile, and otherwise, charge or discharge the traction battery according to a battery power reference derived from the present driver power demand.

13. The vehicle of claim 12 wherein the controller is further programmed to, in response to the engine cycling profile having the number of engine on/off cycles greater than the predetermined number, output an engine power request that is based on a difference between the target state of charge profile and a present state of charge of the traction battery.

14. A method comprising:

receiving, by a controller, predicted speed and grade profiles from a navigation system;

receiving, by the controller, engine cycling commands including engine off requests and commands permissive of engine off requests;

stopping, by the controller, an engine in response to a first engine cycling command that is based on the profiles being an engine off request and a second engine cycling command that is independent of the profiles being permissive of the engine off request while the engine is on; and

outputting, by the controller, a target state of charge for a traction battery based on the profiles and a battery power reference independent of the profiles, and charging and discharging the traction battery according to the target state of charge in response to the first engine cycling command defining at least a predetermined number of engine cycles over a route.

15. The method of claim 14 wherein the engine cycling commands further include commands non-permissive of engine off requests, and further comprising operating the engine according to the second engine cycling command in response to the second engine cycling command being non-permissive of the engine off request.

16. The method of claim 14 wherein the engine cycling commands further include engine on requests and commands permissive of engine on requests, and further comprising outputting, by the controller, an engine on command in response to the first engine cycling command including an engine on request and the second engine cycling command being permissive of the engine on request while the engine is off, and operating the engine according to the engine on command.

17. The method of claim 14 further comprising operating the engine according to the second engine cycling command in response to the first engine cycling command defining less than a predetermined number of predicted engine cycles over a route.

18. The method of claim 14 further comprising operating the engine according to the second engine cycling command in response to the second engine cycling command having greater priority than the first engine cycling command.