Fault mitigation system for electric vehicle

Abstract

A computer-implemented method, when executed by data processing hardware, causes the data processing hardware to perform operations. Operations include: receiving battery data of a vehicle battery at a monitoring application; detecting, via the monitoring application, a battery event based on the received battery data; and estimating a severity level of the battery event via a fault mitigation algorithm, the severity level being one of the first level and the second level. Operations also include; performing, via a fault mitigation algorithm, a mitigation action based on the estimated severity level; and communicating, via the communication system, the fault state and the mitigation plan based on the performed mitigation action.

Description

Technical Field

[0001] This disclosure generally relates to fault mitigation systems for electric vehicles. Background Technology

[0002] The information provided in this section is intended to provide a general overview of the background of this disclosure. To the extent described in this section, the work of the currently named inventors, and aspects of the description that may not conform to the prior art at the time of submission, are neither explicitly nor implicitly acknowledged as prior art relative to this disclosure.

[0003] Electric vehicles (EVs) are equipped with batteries connected to the EV's control system. The control system is configured to monitor various battery states, including state of charge, battery temperature, and potential battery malfunctions. In some cases, the control system can detect thermal runaway events caused by battery failure. A thermal runaway event occurs when the battery enters a self-heating state, causing the rapidly increasing battery temperature to release energy and continuously rise. Different levels of thermal runaway events may occur. For example, the battery may exhibit signs of a thermal runaway event before it progresses. It is beneficial to alert passengers to potential thermal runaway events.

[0004] In addition, many vehicles utilize various navigation and telecommunications systems for route planning during operation. These systems track the vehicle's location and provide feedback to the driver about the vehicle's surroundings. Vehicles are also typically equipped with a user interface that conveys information about the vehicle to the driver or other passengers. For example, the user interface can notify the driver of tire pressure changes or recommend an oil change. While traditional vehicle systems provide information to the driver, they typically do not take action in response to thermal runaway notifications.

[0005] Other traditional systems provide communication capabilities between telecommunications systems and external providers. For example, in response to a service notification, a driver can use a telecommunications system to contact an external provider to request service for their vehicle. In cases of emergency service needs, a driver can steer their vehicle off the main road to contact a service provider for assistance. Traditional telecommunications systems typically operate in response to input from the driver or passengers, but rarely operate independently of driver intervention. Summary of the Invention

[0006] In some aspects, a computer-implemented method, when executed by data processing hardware, causes the data processing hardware to perform operations. The operations include receiving battery data from a vehicle battery at a monitoring application, detecting battery events via the monitoring application based on the received battery data, and estimating the severity level of the battery event via a fault mitigation algorithm, the severity level being one of a first level and a second level. The operations also include performing mitigation actions based on the estimated severity level via the fault mitigation algorithm, and communicating the fault status and mitigation plan via a communication system based on the performed mitigation actions.

[0007] In some examples, the severity level may be Level 1, and performing mitigation actions may include, in response to the Level 1 severity level, combining the energy consumption of the driving task with the energy load of the mitigation action. In some cases, performing a mitigation plan may include estimating available mileage based on the combined energy consumption. Optionally, performing a mitigation plan may include generating a new navigation route based on available mileage. Operations may also include identifying service center locations via a navigation application, identifying remaining route distances based on vehicle and destination locations via the navigation application, and comparing the estimated available mileage with the service distance to the service center location and the remaining route distance.

[0008] In some cases, mitigation actions may include activating the cooler and discharging the battery at least once. Optionally, communicating the fault status may include issuing an alert at the vehicle's infotainment system. In other cases, estimating the severity level may include determining that the severity level is level two. In a further example, performing mitigation actions may include reducing the vehicle's speed, and communicating the fault status and mitigation actions may include issuing an alert to stop the vehicle and leaving the vehicle.

[0009] In other aspects, a fault mitigation system for a vehicle includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. These operations include receiving battery data from a vehicle battery at a monitoring application, detecting battery events based on the received battery data via the monitoring application, and estimating the severity level of the battery event via a fault mitigation algorithm, wherein the severity level is one of a first level and a second level. The operations also include performing mitigation actions based on the estimated severity level via the fault mitigation algorithm, and communicating the fault status and mitigation plan via a communication system based on the performed mitigation actions.

[0010] In some examples, the severity level may be Level 1, and performing mitigation actions may include, in response to Level 1 severity, combining the energy consumption of the driving task with the energy load of the mitigation action. Optionally, performing a mitigation plan may include estimating available mileage based on the combined energy consumption. In other cases, performing a mitigation plan may include generating a new navigation route based on available mileage. Operations may include identifying a service center location via a navigation application, identifying the remaining route distance based on the vehicle's location and destination location via the navigation application, and comparing the estimated available mileage with the service distance to the service center location and the remaining route distance. In some cases, mitigation actions may include activating the cooler and discharging the battery at least one of these. Optionally, communicating the fault status may include issuing an alert at the vehicle's infotainment system. In a further example, estimating the severity level may include determining that the severity level is Level 2. In a further example, performing a mitigation action may include reducing the vehicle's speed, and communicating the fault status and mitigation actions may include issuing an alert to stop the vehicle and leave the vehicle.

[0011] In a further aspect, a fault mitigation system for a vehicle includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. These operations include receiving battery data of the vehicle battery at a monitoring application, detecting battery events based on the received battery data via the monitoring application, and estimating the severity level of the battery event via a fault mitigation algorithm, the severity level being one of a first level and a second level. The operations also include performing mitigation actions based on the estimated severity level via the fault mitigation algorithm, estimating available mileage based on combined energy consumption, and identifying service center locations via a navigation application. Furthermore, the operations include identifying route distances based on the vehicle location and destination location via the navigation application, comparing the route distances with service distances to service center locations and the estimated available mileage, generating new navigation routes based on the available mileage, and communicating the fault status and mitigation plan via a communication system based on the executed mitigation actions.

[0012] In some examples, estimating the severity level may include determining the severity level as Level 2, and performing mitigation actions may include reducing the vehicle's speed, communicating the fault status, and mitigation actions may include issuing an alarm to stop the vehicle and leaving the vehicle. Attached Figure Description

[0013] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure.

[0014] Figure 1 This is a schematic diagram of a vehicle equipped with the fault mitigation system according to the present invention;

[0015] Figure 2 This is an exemplary block diagram of a fault mitigation system according to the present disclosure;

[0016] Figure 3 This is another exemplary block diagram of a fault mitigation system according to the present disclosure;

[0017] Figure 4 This is an exemplary flowchart of a fault mitigation system according to this disclosure; and

[0018] Figure 5 This is another exemplary flowchart of a fault mitigation system according to the present disclosure.

[0019] In all the accompanying drawings, the corresponding reference numerals indicate the corresponding parts. Detailed Implementation

[0020] The example configuration will now be described more fully with reference to the accompanying drawings. The example configuration is provided so that this disclosure will be thorough and will fully communicate the scope of this disclosure to those skilled in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configuration of this disclosure. It will be apparent to those skilled in the art that the specific details are not required, that the example configuration may be implemented in many different forms, and that the specific details and exemplary configuration should not be construed as limiting the scope of this disclosure.

[0021] The terminology used herein is for the purpose of describing specific exemplary configurations only and is not intended to be limiting. As used herein, the singular articles “a,” “an,” and “the” may also be intended to include plural forms unless the context clearly indicates otherwise. The terms “comprising,” “including,” “containing,” and “having” are inclusive, thus specifying the presence of features, steps, operations, elements, and / or components, but not excluding the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein should not be construed as requiring them to be performed in the specific order discussed or shown, unless specifically identified as such. Additional or alternative steps may be employed.

[0022] When an element or layer is referred to as “on another element or layer,” “joined to,” “connected to,” “attached to,” or “linked to” another element or layer, it may be directly on, joined to, connected to, attached to, or linked to the other element or layer, or there may be intermediate elements or layers present. Conversely, when an element is referred to as “directly on another element or layer,” “directly joined to,” “directly connected to,” “directly attached to,” or “directly linked to” another element or layer, there may be no intermediate elements or layers present. Other terms used to describe relationships between elements should be interpreted in a similar manner (e.g., “between” vs. “directly between,” “adjacent” vs. “directly adjacent,” etc.). As used herein, the term “and / or” includes any and all combinations of one or more of the related listed items.

[0023] The terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers, and / or parts. These elements, components, regions, layers, and / or parts should not be limited by these terms. These terms are used only to distinguish individual elements, components, regions, layers, or parts. Terms such as “first,” “second,” and other numerical terms do not imply order or sequence unless the context clearly indicates otherwise. Therefore, the first element, component, region, layer, or part discussed below may be referred to as the second element, component, region, layer, or part without departing from the teachings of the example configuration.

[0024] In this application, including the following definitions, the term "module" may be replaced by the term "circuit". The term "module" may refer to or be a part of an application-specific integrated circuit (ASIC), or include ASICs; digital, analog, or mixed-signal analog / digital discrete circuits; digital, analog, or mixed-signal analog / digital integrated circuits; combinational logic circuits; field-programmable gate arrays (FPGAs); processors (shared, dedicated, or grouped) that execute code; memory (shared, dedicated, or grouped) that stores code executed by the processor; other suitable hardware components that provide the functions described; or some or all of the above, such as in a system-on-a-chip.

[0025] The term "code" as used above can include software, firmware, and / or microcode, and can refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor, in conjunction with an additional processor, that executes some or all of the code from one or more modules. The term "shared memory" includes a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory, in conjunction with additional memory, that stores some or all of the code from one or more modules. The term "memory" can be a subset of the term "computer-readable medium." The term "computer-readable medium" does not include transient electrical and electromagnetic signals propagating through the medium and can therefore be considered tangible, non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, including non-volatile memory, magnetic memory, and optical memory.

[0026] The apparatus and methods described in this application may be implemented, in whole or in part, by one or more computer programs executed by one or more processors. The computer program includes processor-executable instructions stored on at least one non-transitory tangible computer-readable medium. The computer program may also include and / or depend on stored data.

[0027] A software application (i.e., a software resource) can refer to computer software that enables a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "app," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and game applications.

[0028] Non-transitory memory can be a physical device used for temporary or permanent storage of programs (e.g., instruction sequences) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used in firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase-change memory (PCM), and magnetic disks or magnetic tapes.

[0029] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0030] Various implementations of the systems and techniques described herein can be implemented in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (Application-Specific Integrated Circuits), computer hardware, firmware, software, and / or combinations thereof. These different implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system, the programmable system including at least one programmable processor, at least one input device, and at least one output device, the programmable processor being dedicated or general-purpose, coupled to receive data and instructions from and send data and instructions to the storage system.

[0031] The processes and logic flows described in this specification can be executed by one or more programmable processors, also known as data processing hardware, which execute one or more computer programs to perform functions by manipulating input data and generating output. These processes and logic flows can also be executed by special-purpose logic circuits, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits). For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer. Typically, the processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Typically, a computer will also include or be operatively coupled to one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from or transfer data to, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor storage devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. Processors and memory may be supplemented or incorporated therein by dedicated logic circuitry.

[0032] To provide interaction with the user, one or more aspects of this disclosure can be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touchscreen, and optional keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and input from the user can be received in any form, including sound, speech, or tactile input. Furthermore, the computer can interact with the user by sending documents to and receiving documents from the device used by the user; for example, by sending a webpage to a web browser on the user's client device in response to a request received from a web browser.

[0033] refer to Figure 1-3The fault mitigation system 10 for vehicle 100 includes a controller 12 configured to execute a fault mitigation algorithm 14 in response to a battery event 102 of battery 104 of vehicle 100. For example, vehicle 100 may be an electric vehicle (EV) 100 and / or a hybrid vehicle 100, which uses battery 104 during operation of vehicle 100. Controller 12 receives battery data 106 from battery 104 and, in response to battery event 102, is configured to execute fault mitigation algorithm 14. Controller 12 includes data processing hardware 16 and memory hardware 18 in communication with data processing hardware 16. Memory hardware 18 stores instructions that, when executed on data processing hardware 16, cause data processing hardware 16 to perform the operations described herein.

[0034] The controller 12 also includes a monitoring application 20 configured to monitor battery data 106 for potential battery events 102. For example, battery event 102 may include, but is not limited to, a thermal runaway event in which battery 104 enters a self-heating state. Battery data 106 may include, but is not limited to, state of charge 106a, temperature 106b, and task load 106c. Task load 106c may be related to various driving tasks 108 of the vehicle 100, which may utilize battery 104 as an energy source. Monitoring application 20 is configured to monitor battery data 106 and detect battery event 102 based on battery data 106. If battery event 102 is detected, monitoring application 20 may send a notification 22 to fault mitigation algorithm 14.

[0035] Data processing hardware 14 is configured to execute fault mitigation algorithm 14 in response to notification 22. Notification 22 typically includes information related to battery event 102, including battery data 106. Fault mitigation algorithm 14 is configured to execute mitigation action 24 in response to notification 22. Mitigation action 24 may include, but is not limited to, activating the cooler 110 of vehicle 100, discharging battery 104, and changing the driving task 108 of vehicle 100. For example, the speed 108a of vehicle 100 may be reduced as part of mitigation action 24. Fault mitigation algorithm 14 determines which mitigation actions 24 to execute based on an estimated severity level 26 of battery event 102.

[0036] Severity level 26 includes a first level 26a and a second level 26b. The first level 26a can be associated with a lower severity level compared to the second level 26b. For example, a battery event 102 classified as first level 26a can correspond to an early thermal runaway battery event 102. An early thermal runaway battery event 102 may occur when battery 104 is not in a thermal runaway state, but battery data 106 shows signs that a thermal runaway battery event 102 may occur without intervention. Therefore, first level 26a can correspond to a precursor to a thermal runaway battery event 102 because it is less severe than second level 26b. Second level 26b typically corresponds to an active or impending thermal runaway battery event 102. In some cases, second level 26b can have sub-ranges of severity that can be collectively classified within second level 26b. For example, fault mitigation algorithm 14 is configured to perform mitigation actions 24, such as stopping the movement of vehicle 100 and issuing an alarm 28 to notify passengers to leave vehicle 100, which will be described in more detail below.

[0037] As described above, the monitoring application 20 of the fault mitigation system 10 can detect battery event 102 based on received battery data 106, and the fault mitigation algorithm 14 estimates the corresponding severity level 26 of battery event 102. Based on the severity level 26, the fault mitigation algorithm 14 can combine the energy consumption 112 of driving task 108 with the energy load 30 of mitigation action 24. For example, energy consumption 112 can be determined based on task load 106c of battery data 106, since task load 106c corresponds to the energy consumption 112 of the corresponding driving task 108. The fault mitigation algorithm 14 uses the combination of energy consumption 112 of driving task 108 and energy load 30 of mitigation action 24 to determine the available range 40 of battery 104. The mitigation action 24 can be adjusted based on the estimated available range 40 to extend the life of battery 104 during battery event 102 (i.e., activate cooler 110 and / or reduce vehicle speed 108a).

[0038] If severity level 26 is determined to be level 26b, then after communicating fault status 32 and mitigation plan 34 to the passenger, fault mitigation algorithm 14 may execute mitigation action 24 to reduce the speed 108a of vehicle 100 to a stop. For example, mitigation plan 34 may include issuing an alarm 28 to stop vehicle 100 and exit vehicle 100 in the event of level 26b of battery event 102. Vehicle 100 may be configured to autonomously decelerate to a stop, or may be manually operated by the passenger to maneuver vehicle 100 to a safe position before stopping and exiting vehicle 100. In some examples, available mileage 40 may be used to identify a distance range that the passenger can utilize to identify a safe location to maneuver vehicle 100 before stopping and exiting vehicle 100.

[0039] Still referencing Figure 1-3 The fault mitigation system 10 also includes a navigation system 200 configured to monitor vehicle location 202 and identify service center location 204. The navigation system 200 communicates navigation data 206 with the controller 12 for use in the fault mitigation algorithm 14. For example, the fault mitigation algorithm 14 may use the navigation data 206 to evaluate available mileage 40 by comparing it with vehicle location 202, service center location 204, and destination location 208, thereby generating a mitigation plan 34. Each of the vehicle location 202, service center location 204, and destination location 208 can be transmitted to the fault mitigation algorithm 14 as navigation data 206. For example, the fault mitigation algorithm 14 may identify service center location 204 by communicating with the navigation system 200.

[0040] Fault mitigation algorithm 14 is configured to evaluate available mileage 40 by comparing it to an estimated driving distance, which includes the remaining route distance 42 in the current route 210 of vehicle 100 and the service distance 44 to the nearest service center location 204. For example, fault mitigation algorithm 14 may identify the remaining route distance 42 based on vehicle location 202 and destination location 208. Available mileage 40 is estimated based on combined energy consumption 112. In some cases, as part of performing mitigation action 24, fault mitigation algorithm 14 estimates available mileage 40 based on combined energy consumption 112. Available mileage 40 is compared to a combination of remaining route distance 42 and service distance 44. If available mileage 40 exceeds the combination of remaining route distance 42 and service distance 44, fault mitigation algorithm 14 may determine that vehicle 100 can continue on the current route 210.

[0041] In some cases, the available mileage 40 may be less than the combination of the remaining route distance 42 and the service distance 44. As a result, as part of mitigation action 24 and / or mitigation plan 34, fault mitigation algorithm 14 may estimate and execute a new navigation route 212 based on the available mileage 40. Navigation data 206 may also include cloud-source data 300 from cloud server 302, such as traffic patterns, weather, and road conditions, which can also be used by fault mitigation algorithm 14 to estimate the new navigation route 212. Fault mitigation algorithm 14 is configured to continuously receive cloud-source data 300 from cloud server 302 to continuously improve the estimation of available mileage 40.

[0042] Figure 4An exemplary flowchart of a fault mitigation system 10 performing navigation functions is shown. At 400, fault mitigation algorithm 14 estimates available mileage 40. At 402, fault mitigation algorithm 14 compares available mileage 40 with the remaining route distance 42 and the service distance 44 to service center location 204. At 404, fault mitigation algorithm 14 determines whether available mileage 40 is greater than the remaining route distance 42 and the service distance 44 to service center location 204. If available mileage 40 is greater than the combined remaining route distance 42 and service distance 44, fault mitigation algorithm 14 prompts the passenger at 406 to confirm whether to complete route 210. If the passenger confirms, vehicle 100 completes route 210 at 408 and then proceeds to service center location 204 at 410. For example, vehicle 100 could be an autonomous vehicle 100 that can drop off the passenger at destination location 208 and proceed to service center location 204.

[0043] If the available mileage 40 is less than the combined route distance 42 and service distance 44, then fault mitigation algorithm 14 determines at 412 whether the available mileage 40 is greater than the route distance 42. If the available mileage 40 is greater than the route distance 42, then fault mitigation algorithm 14 prompts the passenger at 414 to confirm whether to complete route 210. If the passenger confirms, then vehicle 100 can complete route 210 at 416. After route 210 is completed, fault mitigation system 10 can arrange for vehicle 100 to be towed from destination location 208 at 418.

[0044] If the available mileage 40 is less than the route distance 42, or if the passenger has not confirmed completion of route 210, the fault mitigation system 10 defines an alighting location 214 at 420 and updates the available mileage 40 at 422. For example, the fault mitigation algorithm 14 may subtract the mileage to reach the alighting location 214 to determine the updated available mileage 40. The passenger alights at 422, and the fault mitigation system 10 may continue towing vehicle 100 at 418, or it may continue to service center location 204 at 410, depending on the available mileage 40.

[0045] Refer again Figure 1-3The fault mitigation system 10 also includes a communication system 120 for the vehicle 100. The fault mitigation system 10 utilizes the communication system 120 to communicate each mitigation action 24, fault status 32, and / or mitigation plan 34 to the passengers of the vehicle 100. For example, the communication system 120 may include an infotainment system 122, which includes an audio system 122a and a display 122b for the vehicle 100. The fault mitigation algorithm 14 can audibly announce the fault status 32 via the audio system 122a and can display the mitigation action 24 on the display 122b. The fault status 32 may be communicated to the passengers via lights, audio notifications, haptic notifications, or any other feasible notification method. For example, the fault status 32 may be communicated to the passengers via an alarm 28 issued at the infotainment system 122 by the fault mitigation algorithm 14.

[0046] As described above, the fault mitigation system 10 may present prompts to passengers at the infotainment system 122 based on mitigation action 24 and / or mitigation plan 34. Passengers may be informed of the mitigation action 24 performed by the fault mitigation system 10 and may provide input regarding the mitigation plan 34. For example, when prompted by the fault mitigation algorithm 14, passengers may indicate whether to continue the current route 210. Therefore, the fault mitigation system 10 notifies passengers of battery event 102 via alarm 28 and fault status 32. In some cases, the fault mitigation system 10 may utilize a cloud server 302 to communicate with the passenger's user device, allowing alarm 28 to be delivered via telephone and text message.

[0047] refer to Figure 2-5 , Figure 5 An exemplary flowchart of fault mitigation system 10 is shown. Fault mitigation system 10 monitors the severity level 26 of battery event 102 at 500. Fault mitigation algorithm 14 can detect a first level 26a of severity level 26 at 502 and can activate cooler 110 at 504. In other examples, fault mitigation algorithm 14 can activate or perform other mitigation actions 24 at 504, as described above. Fault mitigation algorithm 14 recalculates the available mileage 40 of battery 104 at 506 and calculates the route distance 42 by combining it with the service distance 44 at 508. Fault mitigation algorithm 14 determines at 510 whether the available mileage 40 is greater than the remaining route distance 42 and service distance 44. If the available mileage 40 is less than the combined remaining route distance 42 and service distance 44, fault mitigation algorithm 14 issues an alarm 28 and a mitigation plan 34 at 512. Fault mitigation system 10 can then proceed to service center location 204 at 514.

[0048] If the available mileage 40 is greater than the route distance 42 and the service distance 44, the fault mitigation system 10 may prompt the passenger at 516 to confirm whether to complete the current route 210. If the passenger refuses the prompt to continue, the fault mitigation system 10 may proceed to the service center location 204 at 514. If the passenger confirms to continue on the current route 210, the fault mitigation system 10 may determine at 518 whether to discharge the battery 104. If the fault mitigation system 10 determines not to discharge the battery 104, the fault mitigation system 10 may complete the route 210 at 520.

[0049] If the fault mitigation system 10 determines to discharge battery 104, it discharges battery 104 at 522 and continues to recalculate available range 40 at 506. After discharging battery 104, the decision path of the fault mitigation system 10 is shown as a dashed line to depict the optional nature of the path. As described above, the fault mitigation system 10 continues with steps 506-510. Once at decision step 510, after discharging battery 104, if the available range 40 is greater than the combined route distance 42 and service distance 44, the fault mitigation system 10 may optionally continue to complete route 210 at 520. Otherwise, the fault mitigation system 10 continues to issue alarm 28 and mitigation plan 34 at 512 before proceeding to service center location 204 at 514.

[0050] In other examples, fault mitigation system 10 may detect at 530 a second level 26b of severity level 26 for battery event 102. In response, fault mitigation system 10 may issue an alert 28 to passengers at 532 to leave vehicle 100. Fault mitigation system 10 may place vehicle 100 in a parked position at 534, allowing passengers to safely exit vehicle 100. Figure 5 The steps described herein are exemplary and can be used in conjunction with... Figure 4 The steps described herein are combined, wherein fault mitigation system 10 evaluates and generates a new navigation route 212. Steps 400-424, 500-534 can be performed in a sequence consistent with the general order described throughout the disclosure. Therefore, fault mitigation system 10 is not limited to... Figure 4 and Figure 5 The sequence of operations is illustrated in the exemplary flowchart.

[0051] Refer again Figure 1-5The fault mitigation system 10 advantageously identifies battery event 102 and implements mitigation plan 34 in response to it. For example, fault mitigation algorithm 14 estimates available mileage 40 and performs the various mitigation actions 24 described above based on available mileage 40. Furthermore, the fault mitigation system 10 utilizes navigation system 200 to generate a new navigation route 212 based on available mileage 40 and service center location 204. The new navigation route 212 may be presented to the user on infotainment system 122 and / or via alert 28 on the passenger's user device. Thus, the passenger is notified and informed of battery event 102, and it is ensured that fault mitigation system 10 has identified and determined mitigation plan 34 based on fault state 32, including mitigation actions 24. The fault mitigation system 10 advantageously provides automatic adjustment of the current route 210 and takes action to mitigate battery event 102 while keeping the passenger informed.

[0052] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of this disclosure. Therefore, other embodiments are also within the scope of the following claims.

[0053] The foregoing description has been provided for purposes of illustration and description. It is not intended to be exhaustive or limiting of this disclosure. Individual elements or features of a particular configuration are generally not limited to that particular configuration, but where applicable, they are interchangeable and can be used in selected configurations, even if not specifically shown or described. This can also be varied in many ways. Such variations should not be considered as departing from this disclosure, and all such modifications are intended to be included within the scope of this disclosure.

Claims

1. A computer-implemented method that, when executed by data processing hardware, causes the data processing hardware to perform operations comprising: receiving, at a monitoring application, battery data for a vehicle battery; detecting, via the monitoring application, a battery event based on the received battery data; estimating, via a fault mitigation algorithm, a severity level for the battery event, the severity level being one of a first level and a second level; performing, via the fault mitigation algorithm, a mitigation action based on the estimated severity level; and communicating, via a communication system, a fault status and a mitigation plan based on the performed mitigation action. the severity level is the first level, and performing the mitigation action includes consolidating an energy consumption of a driving task with an energy load of the mitigation action in response to the first level severity level.

2. The method of claim 1, wherein, performing the mitigation plan includes estimating available mileage based on the consolidated energy consumption.

3. The method of claim 2, wherein, performing the mitigation plan includes generating a new navigation route based on the available mileage.

4. The method of claim 3, wherein, 5. The method of claim 3, further comprising: identifying, via the navigation application, a service center location; identifying, via the navigation application, a remaining route distance based on the vehicle location and the destination location; and comparing the estimated available mileage to a service distance to the service center location and the remaining route distance. the mitigation action includes at least one of activating a chiller and discharging the battery. communicating the fault status includes sounding an alarm at an infotainment system of the vehicle.

6. The method of claim 1, wherein, estimating the severity level includes determining that the severity level is the second level.

7. The method of claim 1, wherein, performing the mitigation action includes reducing a speed of the vehicle, and communicating the fault status and mitigation action includes sounding an alarm to stop the vehicle and exit the vehicle.

8. The method of claim 1, wherein, 10. A vehicle equipped with a fault mitigation system configured to perform the method of claim 1.

9. The method of claim 8, wherein, ​ ​

Images