Low voltage battery consumption detection system for vehicle

Abstract

A consumption detection system for a vehicle includes a sensor configured to detect a parameter of a low voltage battery of the vehicle and collect battery data including the parameter when the vehicle is off; a telematics module; and a control module configured to i) receive battery data from the sensor when the vehicle is on, ii) transmit the battery data via the telematics module to a network device positioned remotely from the vehicle, iii) receive an alert message from the network device indicative of parasitic consumption on the low voltage battery, and iv) execute a first countermeasure in response to the alert message.

Description

[0001] introduction The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section, and aspects of this description that may not otherwise qualify as prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art against the present disclosure.

[0002] The present disclosure relates to energy management systems for vehicles, and more particularly to drain detection systems for batteries of vehicles.

[0003] Conventional vehicles that include an internal combustion engine (ICE) also include a low voltage (e.g., 12V) battery. The low voltage (LV) battery is used to start the ICE and to power various loads in the vehicle. The LV battery is charged via an alternator that converts mechanical energy from the ICE into electrical energy to charge the LV battery.

[0004] Electric vehicles (such as all-electric vehicles, battery electric vehicles (BEVs), and hybrid electric vehicles including plug-in hybrid electric vehicles (PHEVs)) include a high voltage (HV) battery pack and a LV battery. The HV battery pack provides power to the HV direct current (DC) load and the auxiliary power module, which converts the high voltage into a low voltage to charge the low voltage (LV) power source (or battery). The LV battery is used to power the LV DC load. The HV load may include a motor for propulsion purposes and other HV loads. The LV load may include, for example, lights, window and seat motors, door locks, infotainment system equipment, etc. The HV battery pack may have terminals at, for example, 400V or 800V. The LV battery may have terminals at, for example, 12V or 48V. When the electric vehicle is started, the LV battery may be used to close the HV contactor to allow power from the HV battery pack to be supplied to the motor and other HV loads. Summary of the invention

[0005] A consumption detection system for a vehicle is disclosed. The consumption detection system includes: a sensor configured to detect parameters of a low-voltage battery of the vehicle when the vehicle is turned off and collect battery data including the parameters; a telematics module; and a control module configured to: i) receive the battery data from the sensor when the vehicle is turned on, ii) transmit the battery data to a network device remotely located from the vehicle via the telematics module, iii) receive an alert message indicating parasitic consumption on the low-voltage battery from the network device, and iv) execute a first countermeasure in response to the alert message.

[0006] In other features, the low voltage battery is configured to close contactors for the high voltage battery pack or to start the internal combustion engine.

[0007] In other features, the battery data includes a state of charge of the low voltage battery. The state of charge is at least due to parasitic consumption. The alarm message is generated based on the state of charge.

[0008] In other features, the battery data includes a rate of consumption of the low voltage battery. The rate of consumption is at least due to parasitic consumption. The alert message is generated based on the rate of consumption.

[0009] In other features, the battery data includes a current draw of the low voltage battery. The current draw is at least due to parasitic consumption. The alarm message is generated based on the current draw.

[0010] In other features, the battery data indicates a low state of charge of a high-voltage battery pack of the vehicle. The warning message is generated based on the low state of charge of the high-voltage battery pack.

[0011] In other features, a consumption detection system for a vehicle is disclosed. The consumption detection system includes: a sensor configured to detect a parameter of a low-voltage battery of the vehicle when the vehicle is off and collect battery data including the parameter; and a control module configured to: i) receive the battery data from the sensor when the vehicle is on, ii) detect parasitic consumption on the low-voltage battery based on the battery data, and iii) execute a countermeasure in response to detecting the parasitic consumption.

[0012] In other features, the low voltage battery is configured to close contactors for the high voltage battery pack or to start the internal combustion engine.

[0013] In other features, the battery data includes a state of charge of the low voltage battery. The state of charge is at least due to parasitic consumption. The countermeasure is executed based on the state of charge.

[0014] In other features, the battery data includes a consumption rate of the low voltage battery. The consumption rate is at least due to parasitic consumption. The countermeasure is executed based on the consumption rate.

[0015] In other features, the battery data includes a current draw of the low voltage battery. The current draw is due to at least parasitic consumption. The countermeasure is performed based on the current draw.

[0016] In other features, the battery data indicates a low state of charge of a high-voltage battery pack of the vehicle. The countermeasure is performed based on the low state of charge of the high-voltage battery pack.

[0017] In other features, a network device for a consumption detection system of a first vehicle. The network device includes: a transceiver configured to receive battery data from the first vehicle, the battery data including parameters of a low-voltage battery of the first vehicle and collected when the first vehicle is off and transmitted to the network device when the first vehicle is on; and a control module configured to: detect parasitic consumption on the low-voltage battery based on the battery data, and in response to detecting the parasitic consumption, transmit an alert message indicating the parasitic consumption to the first vehicle, and cause the first vehicle to perform a first countermeasure due to the presence of the parasitic consumption.

[0018] In other features, the transceiver is configured to receive battery data from a plurality of vehicles including the first vehicle and transmit a second alert message to the second vehicle based on the battery data collected at the first vehicle.

[0019] In other features, the battery data indicates at least one of a state of charge of the low-voltage battery, a rate of drain of the low-voltage battery, a current draw from the low-voltage battery, and a low state of charge of a high-voltage battery pack of the first vehicle. The control module is configured to execute a first countermeasure based on at least one of the state of charge of the low-voltage battery, the rate of drain of the low-voltage battery, the current draw from the low-voltage battery, and the low state of charge of the high-voltage battery pack.

[0020] In other features, the battery data indicates a state of charge of the low-voltage battery, a rate of drain of the low-voltage battery, a current draw from the low-voltage battery, and a low state of charge of a high-voltage battery pack of the first vehicle. The control module is configured to execute a first countermeasure based on the state of charge of the low-voltage battery, the rate of drain of the low-voltage battery, the current draw from the low-voltage battery, and the low state of charge of the high-voltage battery pack.

[0021] In other features, the control module is configured to: determine, based on the battery data, that a first trigger condition indicative of the presence of parasitic drain is satisfied; and execute a first countermeasure in response to determining the presence of the first trigger condition.

[0022] In other features, the control module is configured to: based on the battery data, determine that a second trigger condition indicating the presence of parasitic consumption is met, the second trigger condition is different from the first trigger condition; and in response to determining the presence of the second trigger condition, execute a second countermeasure, the second countermeasure is different from the first countermeasure.

[0023] In other features, the control module is configured to: based on the battery data, determine that a third trigger condition indicating the presence of parasitic consumption is met, the third trigger condition is different from the first trigger condition and the second trigger condition; and in response to determining the presence of the third trigger condition, execute a third countermeasure, the second countermeasure is different from the first countermeasure and the second countermeasure.

[0024] In other features, the control module is configured to: determine, based on the battery data, that first and second trigger conditions indicating the presence of parasitic consumption are satisfied; and execute a first countermeasure in response to determining the presence of the first and second trigger conditions.

[0025] The present application provides the following embodiments: 1. A consumption detection system for a vehicle, the consumption detection system comprising: a sensor configured to detect a plurality of parameters of a low-voltage battery of the vehicle when the vehicle is turned off and collect battery data including the plurality of parameters; Telematics module; and A control module is configured to: i) receive battery data from a sensor when the vehicle is turned on, ii) transmit the battery data to a network device remotely located from the vehicle via a telematics module, iii) receive an alert message from the network device indicating parasitic drain on a low voltage battery, and iv) execute a first countermeasure in response to the alert message.

[0026] 2. The consumption detection system of embodiment 1, wherein the low voltage battery is configured to close a contactor for a high voltage battery pack or to start an internal combustion engine.

[0027] 3. The consumption detection system of embodiment 1, wherein: Battery data includes the state of charge of low-voltage batteries; The state of charge is due to at least parasitic consumption; and An alert message is generated based on the state of charge.

[0028] 4. The consumption detection system of embodiment 1, wherein: Battery data includes the rate at which low-voltage batteries are depleted; The consumption rate is at least due to parasitic consumption; and An alert message is generated based on the consumption rate.

[0029] 5. The consumption detection system of embodiment 1, wherein: Battery data includes current draw from low-voltage batteries; The current draw is due to at least parasitic consumption; and An alarm message is generated based on the current draw.

[0030] 6. The consumption detection system of embodiment 1, wherein: The battery data indicates a low state of charge of a high voltage battery pack of the vehicle; and The warning message is generated based on the low state of charge of the high voltage battery pack.

[0031] 7. A consumption detection system for a vehicle, the consumption detection system comprising: a sensor configured to detect a plurality of parameters of a low voltage battery of the vehicle when the vehicle is turned off and collect battery data including the plurality of parameters; and A control module is configured to: i) receive battery data from a sensor when the vehicle is turned on, ii) detect parasitic drain on a low voltage battery based on the battery data, and iii) execute a countermeasure in response to detecting the parasitic drain.

[0032] 8. A consumption detection system according to embodiment 7, wherein the low voltage battery is configured to close a contactor for a high voltage battery pack or start an internal combustion engine.

[0033] 9. The consumption detection system of embodiment 7, wherein: Battery data includes the state of charge of low-voltage batteries; The state of charge is due to at least parasitic consumption; and The countermeasures are performed based on the state of charge.

[0034] 10. The consumption detection system of embodiment 7, wherein: Battery data includes the rate at which low-voltage batteries are depleted; The consumption rate is at least due to parasitic consumption; and The countermeasures are performed based on the consumption rate.

[0035] 11. The consumption detection system of embodiment 7, wherein: Battery data includes current draw from low-voltage batteries; The current draw is due to at least parasitic consumption; and The countermeasures are performed based on the current draw.

[0036] 12. The consumption detection system of embodiment 7, wherein: The battery data indicates a low state of charge of a high voltage battery pack of the vehicle; and The countermeasures are performed based on a low state of charge of the high voltage battery pack.

[0037] 13. A network device for a consumption detection system of a first vehicle, the network device comprising: a transceiver configured to receive battery data from a first vehicle, the battery data including a plurality of parameters of a low-voltage battery of the first vehicle and being collected when the first vehicle is turned off and transmitted to the network device when the first vehicle is turned on; and a control module configured to detect parasitic consumption on the low-voltage battery based on the battery data, and in response to detecting the parasitic consumption, transmit an alarm message indicating the parasitic consumption to the first vehicle, and cause the first vehicle to execute a first countermeasure due to the presence of the parasitic consumption.

[0038] 14. The network device of embodiment 13, wherein the transceiver is configured to receive battery data from a plurality of vehicles including a first vehicle, and transmit a second alert message to a second vehicle based on the battery data collected at the first vehicle.

[0039] 15. The network device of embodiment 13, wherein: The battery data indicates at least one of a state of charge of the low voltage battery, a rate of drain of the low voltage battery, a current draw from the low voltage battery, and a low state of charge of a high voltage battery pack of the first vehicle; and The control module is configured to execute a first countermeasure based on at least one of a state of charge of the low-voltage battery, a rate of drain of the low-voltage battery, a current draw from the low-voltage battery, and a low state of charge of the high-voltage battery pack.

[0040] 16. The network device of embodiment 13, wherein: The battery data indicates a state of charge of the low voltage battery, a rate of drain of the low voltage battery, a current draw from the low voltage battery, and a low state of charge of a high voltage battery pack of the first vehicle; and The control module is configured to execute a first countermeasure based on a state of charge of the low-voltage battery, a drain rate of the low-voltage battery, a current draw from the low-voltage battery, and a low state of charge of the high-voltage battery pack.

[0041] 17. The network device of embodiment 13, wherein the control module is configured to: Based on the battery data, determining that a first trigger condition is met, the first trigger condition indicating the presence of parasitic consumption; and In response to determining the presence of a first trigger condition, a first countermeasure is executed.

[0042] 18. The network device of embodiment 17, wherein the control module is configured to: determining, based on the battery data, that a second trigger condition is satisfied, the second trigger condition indicating the presence of parasitic consumption; the second trigger condition being different from the first trigger condition; and In response to determining that a second trigger condition exists, a second countermeasure is executed, the second countermeasure being different from the first countermeasure.

[0043] 19. The network device of embodiment 18, wherein the control module is configured to: determining, based on the battery data, that a third trigger condition is satisfied, the third trigger condition indicating the presence of parasitic consumption; the third trigger condition being different from the first trigger condition and the second trigger condition; and In response to determining that a third trigger condition exists, a third countermeasure is executed, the third countermeasure being different from the first countermeasure and the second countermeasure.

[0044] 20. The network device of embodiment 13, wherein the control module is configured to: determine, based on the battery data, that a first trigger condition and a second trigger condition indicating parasitic consumption are satisfied, and execute a first countermeasure in response to determining the presence of the first trigger condition and the second trigger condition.

[0045] Further areas of applicability of the present disclosure will become apparent from the detailed description, claims, and drawings.The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The present disclosure will become more fully understood from this detailed description and the accompanying drawings, in which: Figure 1 is a functional block diagram of an example vehicle including at least a portion of a LV battery depletion detection system according to the present disclosure; Figure 2 is a functional block diagram of an example LV battery drain detection system for detecting and evaluating battery information collected while a vehicle is turned off according to the present disclosure, the LV battery drain detection system including a back office and a vehicle; Figure 3 illustrates an example battery data collection method according to the present disclosure; Figure 4 illustrates a battery drain detection and response method for a vehicle having an ICE according to the present disclosure; and Figure 5 illustrates a battery drain detection and response method for an electric vehicle according to the present disclosure; In the drawings, reference numerals may be repeated to identify similar and / or identical elements. DETAILED DESCRIPTION

[0047] In an electric vehicle, a LV battery (e.g., a 12V, 24V, or 48V battery) can be used to power certain LV loads when the vehicle is turned off. For example, the LV battery can power an intelligent battery sensor (IBS) to allow the IBS to monitor the state of charge (SOC) of the LV battery. The IBS can be connected to the negative terminal of the LV battery and monitor the current draw and voltage of the LV battery to, for example, determine when the LV battery should be recharged. If the SOC of the LV battery drops below a predetermined SOC, a no start condition may occur. A no start condition refers to when the vehicle is unable to start because the SOC of the LV battery is too low to close the HV contactors of the HV battery pack to charge the LV battery 108 and / or power the HV loads.

[0048] As used herein, the SOC of a power source refers to the charge level of the power source relative to the capacity of the power source. For example, the SOC of a cell and / or a battery module may refer to the voltage, current, and / or amount of available energy stored in the cell and / or battery module. During operation, parameters such as the voltage, current, and temperature of the battery module (or battery pack) and the cell may be monitored to determine the SOX value of the battery pack and the cell. The acronym "SOX" refers to state of charge (SOC), state of health (SOH), state of power (SOP), and / or state of function (SOF). The SOC of a cell and / or a battery may refer to the voltage, current, and / or amount of available power stored in a cell and / or a battery. The SOH of a cell and / or battery pack may refer to: age (or number of operating hours); the presence of short circuits; the presence of loose wires or poor connections; the temperature, voltage, power level, and / or current level supplied to or from the cell and / or battery pack during certain operating conditions; and / or other parameters describing the health of the cell and / or battery pack. The SOF of a cell and / or battery pack may refer to the current temperature, voltage, and / or current level supplied to or from the cell and / or battery pack, and / or other parameters describing the current functional state of the cell and / or battery pack.

[0049] When the vehicle is turned off, parasitic consumption of the LV battery can cause the SOC of the LV battery to drop below a level where a no-start condition exists. This can occur in both electric vehicles and conventional vehicles with an ICE, in which case the LV battery is unable to start the ICE. Parasitic consumption refers to the consumption (or load) on the LV battery when the vehicle is turned off (i.e., the HV contactor is open in an electric vehicle and the ICE is not running in a conventional vehicle). Parasitic consumption is a load that is not a design intent load. When designing a vehicle, certain loads (e.g., an IBS) are intentionally designed to draw power when the vehicle is turned off. When the current drawn from the LV battery increases to exceed the design intent loading when the vehicle is turned off, the LV battery is consumed at a faster rate than intended, which may result in a no-start condition if the LV battery is not charged and / or the parasitic consumption is not detected and addressed. Parasitic consumption may cause rapid discharge of the LV battery and reduce the life of the LV battery.

[0050] Proactive detection of the SOC of the LV battery and an alarm indicating that the SOC of the LV battery is low focus on the status of the LV battery rather than the cause of the low SOC of the LV battery.

[0051] Examples described herein include an LV battery drain detection system for detecting the presence of parasitic drain that may cause the LV battery to discharge. The LV battery drain detection system monitors parameters of the LV battery and evaluates whether certain conditions exist. The presence of certain conditions is used as a trigger for executing a countermeasure (such as generating an alarm, executing a selected vehicle operation, etc.), which trigger is further described below.

[0052] In some example embodiments, a cloud-based approach is used to utilize information collected from a vehicle control module (e.g., a vehicle mission manager) via a telematics control module (TCM) of a host vehicle. The information includes LV battery information, such as voltage, current draw, SOC, etc. The information is collected at a back office (or other central monitoring station) and evaluated outside the host vehicle. An alert message is transmitted from the back office to the host vehicle so that the vehicle can execute one or more countermeasures, as further described below. The back office may also use the collected information and its evaluation results to: i) detect problems at other vehicles, ii) evaluate data from other vehicles, and iii) warn other vehicles and / or their users. The data collection and evaluation may occur during the manufacture of the host vehicle as well as after the manufacture of the host vehicle.

[0053] In other example embodiments, the vehicle control module of the host vehicle evaluates the information and executes countermeasures. This is done on the vehicle without external intervention. In other example embodiments, the information is shared externally and evaluated at both the back office and the host vehicle. The back office provides an alert to the host vehicle, and the host vehicle determines whether and which countermeasures should be executed based on the alert and onboard evaluation results.

[0054] As an example, the back office and / or vehicle control module can process the data collected on the vehicle and generate one or more alerts to proactively identify the presence of parasitic consumption and the specific triggers associated with the detection. In this way, one or more triggers associated with parasitic consumption are isolated (i.e., identified). In a cloud-based system, vehicles with parasitic consumption are identified, and the collected information is used to determine which vehicles are experiencing the same problem, which helps determine the cause(s) of the parasitic consumption.

[0055] Figure 1 A vehicle 100 is shown including a LV battery depletion detection system 102 that collects LV battery information when the vehicle 100 is turned off. The vehicle 100 can be a traditional style vehicle with an ICE, an electric vehicle, or a hybrid vehicle. The LV battery information can be evaluated on the vehicle 100 and / or off the vehicle 100 to detect parasitic depletion. The LV battery depletion detection system 102 includes a vehicle control module 104, an IBS 106, a LV battery 108, and a telematics control module (TCM) 110, also referred to as a telematics module. The vehicle control module 104 monitors battery data collected from the IBS 106, which, in one embodiment, is connected to the negative terminal of the LV battery 108.

[0056] The battery data may include voltage data, current data, temperature data, etc. The voltage data and current data indicate the voltage of the LV battery 108 and the current drawn from the LV battery 108. The temperature data indicates the temperature of the LV battery 108. The battery data may include the SOC of the LV battery 108. The battery data and other battery information, designated 111, may be stored in a memory 112.

[0057] The IBS 106 is a smart sensor that includes logic for determining parameters of the LV battery 108 and a memory 114 for storing the parameters and other battery data, including raw battery data. When the vehicle 100 is turned on and the vehicle control module 104 is powered on, the battery data stored in the memory 114 is transferred to the vehicle control module 104. The IBS 106 detects the open circuit voltage (OCV), current draw, temperature, and / or other parameters of the LV battery 108. The IBS 106 can determine the capacity and / or SOC of the LV battery 108 based on these parameters.

[0058] As a few examples, the LV battery 108 can be a 12V, 24V, or 48V battery. As mentioned herein, a LV battery refers to a battery having a voltage less than or equal to 96V. The LV battery 108 can be used to close the contactor 118 of the control circuit 120 to supply power from the HV battery pack 121 to one or more HV loads 122 (such as one or more motors 124). As mentioned herein, the HV battery pack 121 refers to a battery pack having a voltage greater than or equal to 200V. When the vehicle 100 is turned on, the contactor 118 is closed. This may occur via the ignition switch 126, or remotely via a mobile access device (such as a key fob or a mobile phone that wirelessly communicates with the vehicle control module 104).

[0059] The vehicle control module 104 includes a LV depletion detection module 127 that is configured to evaluate received battery data to determine if certain trigger conditions exist. Examples of trigger conditions are included in Table 1. In one embodiment, the vehicle control module 104 transmits battery data to a back office via the TCM 110. Figure 2 An example back office is shown in . The back office then evaluates the battery data and sends an alert message to the vehicle control module 104 when certain trigger conditions (such as those in Table 1) are met. The TCM 110 includes one or more transceivers 116 for remote communication with the back office.

[0060] The vehicle 100 may be a non-autonomous, partially autonomous, or fully autonomous vehicle. The vehicle 100 may be a non-electric, hybrid, or fully electric vehicle. The vehicle 100 further includes a steering system 132, a brake control system 133, a lighting system 134, a heating, ventilation, and air conditioning system 135, accessories 136, a power source 137 including a LV battery 108 and a HV battery pack 121, and a propulsion system 138. The vehicle 100 may further include an infotainment module 140 and other modules 141. The power source 137 includes one or more battery packs (one HV battery pack 121 is shown) and a control circuit 120.

[0061] Sensors 123 may include various vehicle sensors, such as an accelerator sensor, a steering wheel sensor, a vehicle speed sensor, a brake actuator sensor, one or more accelerometers, and other sensors. Steering system 132 may include one or more front wheel steering actuators and one or more rear wheel steering actuators. The front wheel steering actuator turns the front wheels of vehicle 100, and the rear wheel steering actuator turns the rear wheels of vehicle 100.

[0062] The modules 104, 110, 140, 141 may communicate with each other and have access to the memory 114 via one or more buses and / or network interfaces. An example network interface (or bus) 142 is shown. The network interface (or bus) 142 may include a controller area network (CAN) bus, a local interconnect network (LIN) bus, an automotive network communication protocol bus, and / or other network buses.

[0063] The vehicle control module 104 controls the operation of the vehicle systems. The vehicle control module 104 may include a mode selection module 144, a parameter adjustment module 146, a LV consumption detection module 127, and a countermeasure module 149. The mode selection module 144 may select a vehicle operating mode, such as any of the modes mentioned herein, including an on mode, an off mode, and a sleep mode, as well as other modes, such as a driving mode, an autonomous or partially autonomous mode, etc. The parameter adjustment module 146 may be used to adjust, obtain, and / or determine parameters of the vehicle 100 based on, for example, signals from the sensors 123 and / or other devices and modules mentioned herein.

[0064] The vehicle 100 may further include a display 150 and an audio system 152, which may be used to provide an alert to a user and / or driver of the vehicle 100. The display 150 and / or the audio system 152 may be implemented as part of an infotainment system together with the infotainment module 140. The display 150 and / or other interfaces may be used to select an operating mode. This allows a user to set the operating mode of the vehicle 100. The display 150 and / or the audio system 152 may also be used to indicate a status message. Messages indicating the operating mode may be generated, and / or messages may be generated when, for example, one or more specific trigger conditions have been met. A message may be generated to indicate that the vehicle 100 should be plugged into a charging station to charge the HV battery pack 121. The HV battery pack of an electric vehicle is charged by connecting the electric vehicle to an off-board charging station. During a charging event, the charging completion target is met for a specific SOC (e.g., 96%).

[0065] When the SOC of the LV battery 108 is below a threshold, a message may be generated and may indicate that the vehicle 100 should be started to charge the LV battery 108. This may occur, for example, when there is a problem with the control circuit 120 and / or the vehicle control module 104 such that the control circuit 120 is unable to automatically charge the LV battery 108 via the HV battery pack 121 when the SOC of the LV battery is below a threshold for automatic charging. Various other messages may be generated, some of which are described below.

[0066] The vehicle 100 may further include a global positioning system (GPS) receiver 160. The GPS receiver 160 may provide vehicle speed and / or vehicle direction (or heading) and / or global clock timing information. The GPS receiver 160 may also provide vehicle location information.

[0067] The memory 114 may store battery data and information 111, tables 170, sensor data 172, vehicle parameters 178, and applications 180. The tables 170 may include relationships between parameters such as open circuit voltage (OCV), temperature of the LV battery 108, and SOC of the LV battery 108. A lookup table may be used to determine the SOC of the LV battery 108 based on the detected OCV and temperature of the LV battery 108. The sensor data 172 includes data collected from the sensors 123. The vehicle parameters 178 may include parameters to be set and / or the current state of parameters of the vehicle 100.

[0068] Applications 180 may include applications executed by modules 104, 140, 141. Although memory 114 and vehicle control module 104 are shown as separate devices, memory 114 and vehicle control module 104 may be implemented as a single device. Memory 114 may be accessible to LV consumption detection module 127 and / or countermeasure module 149.

[0069] The vehicle control module 104 may control the operation of the systems 132, 133, 134, 135, accessories 136, engine 181, converter / generator 182, transmission 184, and / or electric motor 124 according to parameters set by the modules 104, 140, 141. The vehicle control module 104 may set some of the vehicle parameters 178 based on signals received from the sensors 123.

[0070] The vehicle control module 104 may receive power from a power source 137, which may be provided to systems 132, 133, 134, 135, accessories 136, engine 181, converter / generator 182, transmission 184, and / or electric motor 124, among others. Some of the vehicle control operations may include enabling fuel and spark for the engine 181, starting and running the electric motor 124, powering any of the systems 132, 133, 134, 135, and / or performing other operations as further described herein.

[0071] The steering system 132 , brake control system 133 , engine 181 , converter / generator 182 , transmission 184 , and / or electric motor 124 may include actuators controlled by the vehicle control module 104 to, for example, adjust fuel, spark, air flow, steering wheel angle, throttle position, pedal position, motor torque, etc. This control may be based on the output of the sensors 123 , the GPS receiver 160 , and the above data and information stored in the memory 114 .

[0072] The vehicle control module 104 may determine various parameters including vehicle speed, engine speed, steering wheel angle, yaw rate of the vehicle 100, lateral acceleration of the vehicle 100, accelerator position, brake actuator position, engine torque, gear state, accelerometer position, brake pedal position, amount of regenerative (charging) power, whether a diagnostic fault code is set, and / or other information. This information may be determined by and / or shared with the modules 104, 110.

[0073] Figure 2 LV battery drain detection system 200 is shown for detecting and evaluating battery information collected while a vehicle 204 is turned off, and includes a back office network device 202 (referred to as back office 202) and vehicles 204. Each of vehicles 204 may be associated with Figure 1 The back office 202 may be implemented the same or similarly to the vehicle 100 of the present invention. The back office 202 may include a transceiver 210, a control module 212, and a memory 214 including one or more databases 216. The database 216 may store vehicle information, such as model, vehicle identification number (VIN), year, etc. The database 216 may also store battery data and information collected from the vehicle 204. The control module 212 may evaluate the vehicle information and send an alert message to one or more of the vehicles 204 when, for example, one or more of the vehicles 204 meet one or more of the trigger conditions mentioned herein. The trigger condition may be met at a first vehicle, and the alert message may be sent to other vehicles based on the condition met at the first vehicle.

[0074] The vehicle 204 may include a TCM (or telematics module) 220, a vehicle control module 222, other loads 224, and a power source 226. The TCM 220 communicates wirelessly with the transceiver 210. The vehicle control module 222 communicates with the Figure 1 The vehicle control module 104 is similarly configured and operated. Other loads 224 may refer to Figure 1 Any of the loads shown and described may also be included on the vehicle 204 and / or other loads. The power source 226 may include a LV battery, an IBS, a HV battery pack, and control circuits.

[0075] Although the following Figure 3-5 Shown to illustrate different methods, but two or more of these methods may be performed together as a single method. Figure 3 The method can be executed Figure 4-5 In one embodiment, for a vehicle having an ICE, Figure 4 , and for vehicles having an electric motor, Figure 5 .

[0076] Figure 3 The battery data collection method is shown. The following operations can be performed iteratively. Although the following operations are mainly about Figure 1 However, these operations are applicable to other embodiments of the present disclosure.

[0077] At 300, the LV consumption detection module 127 determines whether the network bus 142 is to be awakened. This can be determined based on, for example, a schedule for the vehicle control module 104 to wake up and perform a predetermined operation. The network bus 142 is up (or active) when there is traffic on the network bus 142. This occurs when the vehicle control module 104 is up (or turned on) and transmits data to and / or receives data from one or more devices of the vehicle 100. The vehicle control module 104 can wake up when the vehicle receives a signal via, for example, the TCM 110. If the network bus 142 is up (or active), operation 302 is performed.

[0078] At 302 , the LV depletion detection module 127 is configured to determine the SOC of the LV battery 108 . This may be provided by the IBS 106 .

[0079] At 304 , the LV depletion detection module 127 is configured to determine whether the SOC of the LV battery 108 is less than a threshold value (eg, 5-20%). If so, operation 308 may be performed, otherwise operation 302 may be performed.

[0080] At 306 , the LV depletion detection module 127 is configured to determine if a periodic period has passed since the last time battery data was collected for the LV battery 108 . If so, operation 308 is performed. The vehicle control module 104 is periodically awakened and performs predetermined operations, such as collecting battery data from the IBS 106 .

[0081] At 308, the LV depletion detection module 127 is configured to collect battery data from the IBS 106 and / or the memory 114. The battery data may include voltage, current, and temperature data, and whether one or more trigger conditions (such as any of the trigger conditions in Table 1) have been met. At 310, the LV depletion detection module 127 transmits the collected battery data via the TCM 110. The battery data may be transmitted to the back office 202.

[0082] Some examples of battery data collected and / or generated by IBS 106 are included in Table 1. Table 1 includes some example trigger conditions that are part of the rule-based logic. The examples include trigger names, descriptions of corresponding trigger conditions, and logic for detecting when one or more of the trigger conditions are met. In Table 1, X1-X9, Y1-Y5, and Z are thresholds. When the following is executed Figure 4-5 Table 1 may be used when operating with . Table 2 includes example ranges and values ​​for each of the thresholds X1-X9, Y1-Y5, and Z. Other ranges and values ​​may be implemented.

[0083] Table 1 - Consumption detection triggers Table 2 - Example thresholds and values

[0084] In BSM 1, a first set of operations is not allowed and / or restricted. In BSM 2, a second set of operations is not allowed and / or restricted. The second set of operations may include the first set of operations and / or be different from the first set of operations. This may be true for each of the BSM modes. As an example, in BSM 5, it may be determined whether the current draw of the LV battery 108 is greater than 500 mA. As another example, in BSM 7, it may be determined whether the voltage across the positive and negative terminals of the LV battery 108 is less than 11 V.

[0085] The ASD trigger condition is used to determine if there are excessive net amp-hours discharged between ignition off and ignition on (sleep cycle) where the ASD is X2 for more than Y2% of the time (or a predetermined number of data sample points). A trigger condition when the IBS sensor does not learn may occur when the IBS 106 is unable to relearn the LV battery SOC due to current draw greater than X4mA (e.g., 250mA) and / or the RVC SOC is equal to X5% for more than Y3% of the time (or number of data sample points). When the vehicle 100 is turned off, the IBS 106 operates based on the OCV of the LV battery 108. As an example, the IBS 106 may wait for a predetermined period of time (e.g., 3 hours) after the vehicle 100 is turned off to allow the voltage of the LV battery 108 to stabilize and be at a steady-state voltage. The IBS 106 then measures the OCV and temperature of the LV battery 108 when the LV battery 108 is at a steady-state voltage, and determines the SOC of the LV battery 108 based on the OCV and temperature.

[0086] The BCH is a histogram having bars with corresponding sleep current levels and the number of instances and / or time periods during which the sleep current consumption of the LV battery 108 was at the sleep current levels of those bars. When there are X6 consecutive unique instances of BCH (or sleep current) greater than Y4 from any bucket, where Y4 is greater than Z1-Z2mA, then the BCH flag is set to HIGH. When the IBS 106 is unable to relearn the LV battery 108 due to a current consumption greater than X4mA, the SOC error increases. The SOC error is related to whether the IBS 106 is able to relearn the LV battery 108. If the IBS 106 is unable to learn because there are parasitic consumption, then the SOC error increases over time because the IBS is losing confidence in the current estimated SOC of the LV battery 108. When the SOC error is greater than X7%, then the SOC error flag is set to HIGH. When the HV SOC of the HV battery pack 121 is less than a predetermined EBSM threshold (or HV SOC %), the low HV SOC is set to HIGH and the enhanced battery support mode is disabled. The EBSM mode refers to when the HV battery pack 121 is charging the LV battery 108 .

[0087] In one embodiment, the vehicle control module 104 is configured to send battery data (e.g., diagnostic data) to the back office 202 periodically (e.g., daily) and / or any time the network bus 142 has activity when the vehicle is off (referred to as power-off mode), including the status of the trigger condition flag. In one embodiment, the battery diagnostic data is sent when the LV battery SOC flag is HIGH. This is done to prevent and / or minimize additional drain on the LV battery 108 when in power-off mode. This enables the battery data to be collected while the vehicle control module and / or one or more other modules and devices are transmitting data over the network bus 142. The network bus activity can be driven by the vehicle control module 104 and / or one or more other modules and devices and / or by a user. The battery data can be sent back to the back office 202 during periods of active battery drain for early detection of parasitic drain and, in one embodiment, for identifying the ECU (or processor) causing the parasitic drain. The identification is based on one or more triggering conditions being met and may be determined using a stored lookup table relating parasitic consumption, triggering conditions, and a vehicle processor.

[0088] Figure 4 A battery drain detection and response method for a vehicle having an ICE is shown. The method may be used in a vehicle (e.g., Figure 1 Vehicles 100 or Figure 2 204), or performed outside the vehicle, such as in Figure 2 Some or all of the operations may be performed by any of the modules 104, 212, 222 and are represented by "control modules" in the following operations. Any generated alert messages may be transmitted from the back office 202 to the vehicle 100 and / or generated at the vehicle 100 and indicated via, for example, the display 150, the audio system 152, and / or other alerting devices.

[0089] At 400, the control module and / or the LV depletion detection module 127 are configured to determine parameters of the LV battery 108 and / or collect battery data of the LV battery 108. The battery data may include the voltage, current level, temperature of the LV battery 108, and / or whether any trigger conditions have been met. This may be provided by the IBS 106 and / or may be used Figure 3 method to provide.

[0090] At 402, the control module and / or the LV consumption detection module 127 is configured to determine whether one or more first trigger conditions are met. When a trigger condition is met, the corresponding flag is set to 1 in the memory, otherwise the corresponding flag for the trigger condition remains at 0. If so, operation 404 can be performed, otherwise the method can end. As an example, an example first trigger condition can be whether the battery current histogram (BCH) indicates that there have been X6 consecutive unique instances when the current draw has been greater than ZmA (e.g., 50-150mA).

[0091] At 404, the control module and / or the LV consumption detection module 127 is configured to determine whether one or more second trigger conditions are met. If so, operation 406 may be performed, otherwise the method may end. As an example, the second trigger condition may include determining whether a low SOC flag is set to 1 and whether an ADR flag is set to 1. If so, operation 406 is performed, otherwise the method may end.

[0092] At 406, the control module and / or the countermeasure module 149 may execute one or more countermeasures. This may include: generating one or more warning messages; automatically transitioning to charging the LV battery 108; automatically transitioning to charging the HV battery pack 121; autonomously starting the vehicle 100 to charge the LV battery 108; starting the vehicle 100 (if not already started) and driving the vehicle 100 to a service station; limiting the amount of load on the LV battery 108, etc. The warning message may include instructions for: starting the vehicle 100 to charge the LV battery 108; driving the vehicle 100 to a service station; making an appointment for the vehicle 100 to be inspected; alerting the driver or user of the vehicle 100 that there is a slow drain of the LV battery 108; plugging the vehicle 100 in to charge the HV battery pack 121; etc. The countermeasures may include storing information about the trigger condition that was met, such as the name of the trigger condition, the time and duration of occurrence, the vehicle identification number, etc., for future use with respect to the vehicle 100 and / or other vehicles.

[0093] Many different combinations of trigger conditions may be implemented for operations 402 and / or 406. Using a combination of trigger conditions may prevent and / or minimize the number of false positives and false negatives.

[0094] Figure 5 A battery drain detection and response method for an electric vehicle is shown. The method may be used in a vehicle (e.g., Figure 1 Vehicles 100 or Figure 2 204), or performed outside the vehicle, such as in Figure 2Some or all of the operations may be performed by any of the modules 104, 212, 222 and are represented by "control modules" in the following operations. Any generated alert messages may be transmitted from the back office 202 to the vehicle 100 and / or generated at the vehicle 100 and indicated via, for example, the display 150, the audio system 152, and / or other alerting devices.

[0095] At 500, the control module and / or the LV depletion detection module 127 are configured to determine parameters of the LV battery 108 and / or collect battery data of the LV battery 108. The battery data may include the voltage, current level, temperature of the LV battery 108, and / or whether any trigger conditions have been met. This may be provided by the IBS 106 and / or may be used Figure 3 method to provide.

[0096] At 501, the control module and / or the LV consumption detection module 127 is configured to determine whether one or more first trigger conditions are met. As an example, a BCH flag may be checked. If yes, operation 502 may be performed, otherwise operation 504 may be performed.

[0097] At 502, the control module and / or countermeasure module 149 executes a first one or more countermeasures. As an example, the back office 202 may generate an alert message and transmit the alert message to the vehicle 100, which may then provide the alert message to the driver and / or user of the vehicle 100. The alert message may indicate: that the LV battery 108 has a parasitic drain; that there is a slow parasitic drain on the LV battery 108; whether the LV battery 108 is being serviced; that a visit to a dealer and / or service station for the vehicle 100 is scheduled; the level of risk to the ability to start the vehicle 100; and the like. The alert message may be generated at the vehicle 100 without receiving the alert message from the back office 202. Other countermeasures may be executed, such as limiting the amount of load on the LV battery 108.

[0098] At 504, the control module and / or the LV consumption detection module 127 is configured to determine whether one or more second trigger conditions are met. As an example, an ASD flag and / or a SOC error flag may be checked. In one embodiment, both flags are checked, and if both flags are HIGH (or 1), operation 506 is performed, otherwise operation 508 may be performed.

[0099] At 506, the control module and / or countermeasure module 149 executes a second one or more countermeasures. As an example, the back office 202 may send an alert message to the vehicle 100, and / or the vehicle 100 may generate an alert message that instructs the driver and / or user of the vehicle 100 to start the vehicle 100 as soon as possible. In one embodiment, the vehicle control module 104 may start the vehicle 100. This allows the vehicle 100 to charge the LV battery 108 via the HV battery pack 121 and reset one or more electronic control units (ECUs), including resetting the vehicle control module 104. In doing so, the ECU (or processor) that is "stuck" (i.e., operating in an infinite loop) is reset and no longer operates in an infinite loop. The alert message may indicate that the LV battery 108 has a high parasitic consumption. Other countermeasures may be executed, such as limiting the amount of load on the LV battery 108.

[0100] At 508, the control module and / or the LV depletion detection module 127 is configured to determine whether one or more third trigger conditions are met. As an example, the SOC flag and the low HV SOC flag are checked for the LV battery 108 and the HV battery pack 121. If yes, operation 510 may be performed, otherwise the method may end.

[0101] At 510, the control module and / or countermeasure module 149 executes a third one or more countermeasures. As an example, the back office 202 may send an alert message to the vehicle 100, and / or the vehicle 100 may generate an alert message that instructs the driver and / or user of the vehicle 100 to start the vehicle 100 or plug in the vehicle 100 to charge the LV battery 108 and / or the HV battery pack 121. The alert message may indicate that the LV battery 108 has a low SOC and / or the HV battery pack 121 has a low SOC. The SOCs of the LV battery 108 and the HV battery pack 121 may be indicated. If the vehicle is already plugged in, the control module and / or countermeasure module 149 may automatically begin charging the vehicle 100. Other countermeasures may be executed, such as limiting the amount of load on the LV battery 108.

[0102] Figure 3-5 The above operations are meant as illustrative examples. Depending on the application, these operations may be performed sequentially, synchronously, simultaneously, continuously, during overlapping time periods, or in a different order. In addition, depending on the implementation and / or sequence of events, any of these operations may not be performed or skipped.

[0103] The examples disclosed herein include using cloud-based analytics throughout the vehicle lifecycle. This includes checking and detecting parasitic consumption on-board (locally) as well as off-board (remotely). These examples help prevent "walk-home" events by detecting LV battery parasitic consumption and alerting the vehicle to LV battery parasitic consumption. These examples isolate which trigger conditions are met and execute countermeasures to address the satisfied trigger conditions. This helps isolate LV parasitic consumption rather than simply focusing on the state of the LV battery.

[0104] LV parasitic consumption detection can reduce replacement and warranty costs and improve customer satisfaction. These examples provide rapid detection of satisfied trigger conditions associated with one or more LV parasitic consumption of the LV battery by proactively servicing the vehicle when parasitic consumption exists. These examples utilize data available in the vehicle. These examples allow monitoring of a certain model, brand and / or type of vehicle and / or vehicles in a fleet. This can be done during manufacturing and / or during use to determine whether the vehicle exhibits similar behavior and / or exhibits similar problems. The collected battery data can be analyzed by algorithms at the vehicle, at the back office, at the dealer or service station, and at the manufacturing plant, and can be used by customers and / or manufacturers.

[0105] The foregoing description is merely illustrative in nature and is by no means intended to limit the present disclosure, its application or use. The broad teachings of the present disclosure can be implemented in a variety of forms. Therefore, although the present disclosure includes specific examples, the true scope of the present disclosure should not be so limited, because other modifications will become apparent when studying the drawings, the specification and the following claims. It should be understood that, without changing the principles of the present disclosure, one or more steps in the method can be performed in different orders (or simultaneously). In addition, although each embodiment is described above as having certain features, any one or more of those features described with respect to any embodiment of the present disclosure can be implemented in the features of any other embodiment and / or combined with the features of any other embodiment, even if the combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and one or more embodiments and each other's permutation (permutation) are still within the scope of the present disclosure.

[0106] Spatial and functional relationships between elements (e.g., between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including "connected," "engaged," "coupled," "adjacent," "immediately adjacent," "on," "above," "below," and "disposed." Unless explicitly described as "direct," when describing a relationship between a first and a second element in the above disclosure, the relationship may be a direct relationship in which no other intervening elements exist between the first and second elements, but may also be an indirect relationship in which one or more intervening elements (either spatially or functionally) exist between the first and second elements. As used herein, the phrase "at least one of A, B, and C" should be interpreted to mean a logical (A or B or C) using a non-exclusive logical "or," and should not be interpreted to mean "at least one of A, at least one of B, and at least one of C."

[0107] In the various figures, the direction of the arrow, as indicated by the arrow head, generally indicates the flow of information (such as data or instructions) of interest to the illustration. For example, when element A and element B exchange various information, but the information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. The unidirectional arrow does not imply that no other information is transmitted from element B to element A. In addition, for information sent from element A to element B, element B may send a request or a receipt confirmation of the information to element A.

[0108] In this application, including the definitions below, the term "module" or the term "controller" may be replaced with the term "circuit". The term "module" may refer to, be part of, or include: an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or grouped) that executes code; a memory circuit (shared, dedicated, or grouped) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0109] The module may include one or more interface circuits. In some examples, the interface circuit may include a wired or wireless interface connected to a local area network (LAN), the Internet, a wide area network (WAN), or a combination thereof. The functions of any given module of the present disclosure may be distributed among multiple modules connected via the interface circuit. For example, multiple modules may allow load balancing. In a further example, a server (also referred to as a remote or cloud) module may implement some functions on behalf of a client module.

[0110] The term "code" as used above may include software, firmware, and / or microcode, and may refer to a program, a routine, a function, a class, a data structure, and / or an object. The term "shared processor circuit" covers a single processor circuit that executes some or all code from multiple modules. The term "group processor circuit" covers a processor circuit that executes some or all code from one or more modules in conjunction with an additional processor circuit. References to multiple processor circuits cover multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term "shared memory circuit" covers a single memory circuit that stores some or all code from multiple modules. The term "group memory circuit" includes a memory circuit that stores some or all code from one or more modules in conjunction with additional memory.

[0111] The term "memory circuit" is a subset of the term "computer-readable medium". The term "computer-readable medium" as used herein does not encompass non-transitory electrical or electromagnetic signals propagated through a medium (such as on a carrier wave); therefore, the term "computer-readable medium" may be considered to be tangible and non-transitory. Non-limiting examples of non-transitory tangible computer-readable media are non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or mask read-only memory circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog or digital magnetic tape or hard disk drives), and optical storage media (such as CDs, DVDs, or Blu-ray discs).

[0112] The apparatus and method described in the present application can be implemented in part or in whole by a special-purpose computer, which is created by configuring a general-purpose computer to perform one or more specific functions embodied in a computer program. The functional blocks, flow chart components and other elements described above act as software specifications, which can be translated into computer programs by the routine work of skilled technicians or programmers.

[0113] The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include or rely on stored data. The computer program may include a basic input / output system (BIOS) that interacts with the hardware of the special-purpose computer, device drivers that interact with specific devices of the special-purpose computer, one or more operating systems, user applications, background services, background applications, etc.

[0114] A computer program may include: (i) descriptive text to be parsed, such as HTML (Hypertext Markup Language), XML (Extensible Markup Language), or JSON (JavaScript Object Notation), (ii) assembly code, (iii) object code generated by a compiler from source code, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. By way of example only, source code may be written using syntax from languages ​​including: C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Fortran, Perl, Pascal, Curl, OCaml, HTML5 (Hypertext Markup Language Version 5), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Visual Lua, MATLAB, SIMULINK, and

Claims

1. A consumption detection system for a vehicle, the consumption detection system comprising: a sensor configured to detect a plurality of parameters of a low-voltage battery of the vehicle when the vehicle is turned off and collect battery data including the plurality of parameters; Telematics module; as well as A control module is configured to: i) receive battery data from a sensor when the vehicle is turned on, ii) transmit the battery data to a network device remotely located from the vehicle via a telematics module, iii) receive an alert message from the network device indicating parasitic drain on a low voltage battery, and iv) execute a first countermeasure in response to the alert message.

2. The consumption detection system of claim 1, wherein the low voltage battery is configured to close a contactor for the high voltage battery pack or to start an internal combustion engine.

3. The consumption detection system according to claim 1, wherein: Battery data includes the state of charge of low-voltage batteries; The state of charge is due to at least parasitic consumption; and An alert message is generated based on the state of charge.

4. The consumption detection system according to claim 1, wherein: Battery data includes the rate at which low-voltage batteries are depleted; The consumption rate is at least due to parasitic consumption; and An alert message is generated based on the consumption rate.

5. The consumption detection system according to claim 1, wherein: Battery data includes current draw from low-voltage batteries; The current draw is due to at least parasitic consumption; as well as An alarm message is generated based on the current draw.

6. The consumption detection system according to claim 1, wherein: The battery data indicates a low state of charge of a high voltage battery pack of the vehicle; and The warning message is generated based on the low state of charge of the high voltage battery pack.

7. A consumption detection system for a vehicle, the consumption detection system comprising: a sensor configured to detect a plurality of parameters of a low-voltage battery of the vehicle when the vehicle is turned off and collect battery data including the plurality of parameters; as well as A control module is configured to: i) receive battery data from a sensor when the vehicle is turned on, ii) detect parasitic drain on a low voltage battery based on the battery data, and iii) execute a countermeasure in response to detecting the parasitic drain.

8. The consumption detection system of claim 7, wherein the low voltage battery is configured to close a contactor for the high voltage battery pack or to start an internal combustion engine.

9. The consumption detection system according to claim 7, wherein: Battery data includes the state of charge of low-voltage batteries; The state of charge is due to at least parasitic consumption; and The countermeasures are performed based on the state of charge.

10. The consumption detection system according to claim 7, wherein: Battery data includes the rate at which low-voltage batteries are depleted; The consumption rate is at least due to parasitic consumption; and The countermeasures are performed based on the consumption rate.

Images