Vehicle with a low-voltage battery and method for automatically charging a low-voltage battery

DE102017126648B4Active Publication Date: 2026-09-03FORD GLOBAL TECH LLC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
DE102017126648
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2016-11-15
Filing Date
2017-11-13
Publication Date
2026-09-03
Estimated Expiration
2037-11-13

AI Technical Summary

Technical Problem

Hybrid electric vehicles (HEVs) face issues with low voltage (LV) batteries becoming discharged or faulty, leading to inability to move, and autonomous vehicles may lack sufficient power to reach a safe location due to inadequate LV battery state of charge (SoC), resulting in undriveable conditions and potential battery damage during storage.

Method used

Implementing a system with a high voltage (HV) battery, a converter, and a system controller to automatically charge the LV battery when it falls below a predefined threshold, using wireless messaging and energy transfer from HV to LV, and notifying users or dealers through cellular or local area networks.

Benefits of technology

Ensures adequate LV battery SoC, preventing undriveable conditions and battery damage, allowing vehicles to reach safe locations and reducing warranty costs by providing automated recharging and notification systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Vehicle (100), comprising: a low-voltage battery (114); a high-voltage battery (110); a converter (126) that reduces the voltage supplied to the low-voltage battery (114) by the high-voltage battery (110); and a control unit (128, 130, 132, 134) programmed to use the converter (126) in an ignition key off-cycle to automatically charge the low-voltage battery (114) a calibrated number of times in the ignition key off-cycle that the low-voltage battery (114) falls below a predefined charge status threshold, wherein the calibrated number of times in the ignition key off-cycle is at least one;and in response to the low-voltage battery (114) falling below the charge status threshold after the calibrated number of times in the ignition key off cycle has occurred, sending a wireless message indicating a low charge state of the low-voltage battery (114) to a contact address (15) for the vehicle (100).
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL AREA

[0001] Aspects of the disclosure generally concern a battery recharge notification and automatic battery recharging. GENERAL STATE OF THE ART

[0002] A hybrid electric vehicle (HEV) can include a high-voltage (HV) battery system and a low-voltage (LV) battery system. The HV battery system may include a traction battery used to power electric motors to propel the vehicle. The low-voltage system may include a low-voltage battery used for headlights, door actuators, and other electrical systems of the vehicle unrelated to the drive motor. Many HEVs rely on the LV battery system to operate the electrical contacts that connect the HV battery to the electrified powertrain. In some situations, if the LV battery is discharged or faulty, the HEV may be unable to move. SUMMARY

[0003] In one or more illustrative embodiments, a vehicle includes a low-voltage battery; a high-voltage battery; a converter that reduces the voltage supplied to the low-voltage battery by the high-voltage battery; and a control system programmed to use the converter in an ignition key off-cycle to charge the low-voltage battery a calibrated number of times the low-voltage battery falls below a predefined charge status threshold, and to send a wireless message at a later time when the low-voltage battery falls below the threshold.

[0004] In one or more illustrative embodiments, a method includes sending a message to a predefined contact address in response to a regularly calculated charge status of a vehicle's low-voltage battery falling below a predefined threshold; and using a converter that reduces the voltage supplied to the low-voltage battery from a vehicle's high-voltage battery to charge the low-voltage battery in response to receiving a response from the contact address indicating confirmation of charging.

[0005] In one or more illustrative embodiments, a non-transitory, computer-readable medium comprising instructions which, when executed by a processor, cause the processor, in response to the identification that the vehicle is connected to the Local Area Network, to send a message over a Local Area Network to a user address of a vehicle indicating that a low-voltage battery has fallen below a threshold; in response to the identification that the vehicle is connected to the Wide Area Network but not to the Local Area Network, to use a cellular modem of the vehicle to send the message over a Wide Area Network to the address;and to reduce, by means of a converter, the voltage supplied to the low-voltage battery by a high-voltage battery of the vehicle in order to charge the low-voltage battery in response to receiving a response from the contact address indicating confirmation of charging. List of characters Fig. Figure 1 illustrates an exemplary hybrid electric vehicle (HEV) according to an embodiment of the present disclosure; Fig. Figure 2 illustrates an exemplary process for taking into account conditions in which the charge status of the low-voltage battery is at a low level; Fig. Figure 3 illustrates an exemplary process for function initialization and detection of a low battery charge status; Fig.Figure 4 illustrates an exemplary process for reporting the need to recharge the low-voltage battery and requesting permission to use an energy transfer from the low-voltage battery to the high-voltage battery to recharge the low-voltage battery; Fig. Figure 5 illustrates an exemplary process for reporting the need to remotely start the vehicle's combustion engine to recharge the low-voltage battery; and Fig. Figure 6 illustrates an example process for reporting a connection to an external charging device. DETAILED DESCRIPTION

[0006] Depending on the requirements, detailed embodiments of the present invention are disclosed here; however, it is understood that the disclosed embodiments are merely exemplary for the invention, which can be implemented in different and alternative forms. The figures are not necessarily to scale; some features may be enlarged or reduced to show details of certain components. Accordingly, the specific structural and functional details disclosed here are not to be understood as limiting, but merely as a representative basis for teaching those skilled in the art the diverse uses of the present invention.

[0007] HEVs may be unable to start if the low-voltage battery has discharged to a low state of charge (SoC). Should this occur, the vehicle is considered undrivable, and the customer (or dealer) must jump-start the vehicle or tow it to a repair shop.

[0008] Furthermore, autonomous vehicles rely on the low-voltage battery for electrical power if a DC / DC converter from the high-voltage system to the low-voltage system fails. Under such a condition, the low-voltage battery must provide sufficient power to allow the vehicle to reach a safe location. To ensure this, the low-voltage battery's state of charge (SoC) must be above a specific level, and its condition must be adequate. If this is not the case, there may not be enough battery power to supply the autonomous systems to reach a safe location. If the SoC falls below this minimum threshold (or the battery's state of charge is inadequate), the vehicle may be prohibited from using it until the low-voltage battery is recharged (or replaced); therefore, a notification is required.The autonomous vehicles can be kept in a depot where there may be dozens or hundreds of vehicles, so automated reporting can be significant.

[0009] Real-world customer usage patterns can also lead to a chronically low state of charge (SoC) of the low-voltage battery. This can occur because some HEV customers predominantly drive short distances. The duration of these driving cycles may be too short to allow the vehicle's electrical system to recharge the low-voltage battery after it has been discharged during an ignition key off event. Over time, multiple cycles of ignition key off events followed by short driving cycles can reduce the low-voltage battery's SoC to a low level. Eventually, even a single short ignition key off cycle can reduce the battery's SoC to a level where closing the high-voltage battery contactors becomes problematic.

[0010] Additionally, deep discharge during extended vehicle storage at the assembly plant and / or dealership can potentially damage the low-voltage batteries of HEVs. This can result from typical dealer handling of HEVs before delivery to the customer. When the vehicle is parked for a prolonged period, electrical loads from the ignition being switched off can discharge the battery to a low state of charge (SoC). This occurs in assembly plants and dealerships because the combination of post-production storage, vehicle transport, and dealer storage can lead to extended periods (several weeks) during which the vehicle remains switched off. If the low-voltage battery is deep discharged during this time, it can cause irreversible damage, reducing the battery's capacity.Should this be the case, the vehicle may be delivered to the customer with a compromised battery with reduced capacity and unfavorable electrical characteristics (e.g., low charge acceptance), which may lead to an early service repair under warranty.

[0011] To address these issues, existing communication devices in the vehicle can be used to provide alerts to the dealer and / or customer, warning them and / or the fleet operator when the low-voltage battery's state of charge (SoC) is low. The dealer, customer, or fleet operator can then take action to recharge the battery. As an example, if the vehicle has been delivered to a customer, the customer can start the vehicle for a short period (e.g., 20-30 minutes). Alternatively, for PHEVs and BEVs, the customer can connect the vehicle to a high-voltage battery charger (which also charges the low-voltage battery).In another example scenario, if the vehicle remains at the dealership, is stored in an assembly plant, or is part of a fleet, the LV battery can be recharged additionally or alternatively using an external LV battery charging device.

[0012] Providing these alerts offers customers, rental car companies, dealers, fleet operators, and vehicle assembly plants a simple and effective means of preventing low-voltage batteries from having an unusable low state of charge (SoC) or poor low-voltage battery condition. Ensuring adequate SoC for LV batteries reduces situations where a vehicle becomes undrivable due to an inability to close the low-voltage contactors (HEVs) or use the starter motor (conventional vehicles). Furthermore, ensuring adequate low-voltage battery SoC and battery condition allows autonomous vehicles to proceed to a safe location if the autonomous vehicle's DC / DC converter system is unable to power its autonomous systems.

[0013] In one example, the notifications and other operations described herein can be implemented using existing vehicle hardware by adding software similar to that used for in-vehicle notifications by message centers, clusters, and multi-purpose displays. The cost of detecting and correcting deep discharged low-voltage batteries is reduced for operations managing large numbers of vehicles (e.g., dealerships, rental car companies, and vehicle assembly plants) by providing an automated means of recharging the battery using in-vehicle resources. Vehicle warranty costs are reduced by avoiding deep discharged or empty battery events when the vehicle is left unattended for extended periods (e.g., allowing the battery to fully discharge can cause hidden damage leading to premature warranty returns).Further aspects of the revelation are described in detail below.

[0014] Fig. Figure 1 illustrates an example hybrid electric vehicle (HEV) 100 according to one embodiment of the present disclosure. Fig. Figure 1 illustrates representative relationships among the components. The physical arrangement and orientation of the components in the vehicle can vary. The vehicle 100 includes a gearbox 102 and is powered by at least one electric machine 104 , 106 with selective support from an internal combustion engine 108 powered. As shown, the gearbox can 102 have a power-split configuration in which the transmission 102 the first electric machine 104 and a second electric machine 106This includes the following: The electric machine(s) 104, 106 can be, in an example, alternating current (AC) electric motors. The electric machine 104 The second electric machine receives electrical power and provides torque for vehicle propulsion. 106 It also functions as a generator to convert mechanical power into electrical power and optimize the power flow through the gearbox. 102 In other embodiments, the gearbox has 102 It does not have a power-split configuration and can only use a single electric machine for drive and generation. It is understood that this is in Fig. The diagram shown is merely exemplary and not intended to be restrictive. In fact, other configurations of the internal combustion engine exist. 108 and the electrical machines 104 , 106 for the transmission of power through the gearbox 102considered.

[0015] The vehicle 100 includes an energy storage device such as a traction high-voltage battery 110 for storing electrical energy. In the case of the traction battery. 110 It is a high-voltage battery capable of delivering electrical power to power electric machines. 104 , 106 to operate. The HV battery 110 It also receives electrical power from the electric machines 104 , 106 , when they operate as generators. The HV battery 110 This is a battery pack consisting of several (not shown) battery modules, each containing a multitude of battery cells (not shown). A high-voltage bus connects the HV battery. 110 by Sagittarius 112 electrically with the electric machines 104 , 106 , so that the HV battery 110 with the electric machines104 , 106 is connected when the shooter 112 are electrically coupled, and from the electric machines 104 , 106 is separated when the shooter 112 are electrically disengaged.

[0016] The vehicle 100 It also includes a low-voltage battery. 114 , which is connected to a low-voltage bus that carries low-voltage loads 116 of the vehicle 100 operates. Some examples include low-voltage loads. 116 a mobile modem 118 , a WiFi modem 120 and a BLUETOOTH modem 122 include a battery monitoring sensor. 124 is connected to the low-voltage battery 114 connected and provides a voltage measurement signal that can be used to determine the SoC of the low-voltage battery 114 to measure and / or calculate. A temperature sensor 136 will also be inside the vehicle 100provided to supply a signal indicating the ambient temperature of the LV battery 114 and / or the vehicle 100 indicates.

[0017] The vehicle 100 It also includes a DC / DC converter. 126 or a variable voltage converter (VVC). The converter 126 is electrically between the high-voltage bus (which powers the traction battery) 110 and the first electric machines 104 , 106 connects) and the low-voltage bus, which is powered by the low-voltage battery 114 is operated, connected. The converter 126 decreases or reduces the voltage potential of the electrical power supplied to the low-voltage battery. 114 from the high-voltage battery 110 is provided. The converter 126 It can also determine the voltage potential of the electrical power supplied by the low-voltage battery. 114is provided, intensify or increase to the side of the high-voltage battery 110 of the converter 126 to operate in some embodiments.

[0018] The vehicle 100 It also includes various controls configured to manage the operation of the vehicle's drive components. 100 to manage. As shown, the vehicle includes 100 a powertrain control unit (PCU) 128 configured to control the internal combustion engine 108 to control; a hybrid powertrain control module (HPCM) 130, configured to control the transmission 102 to control; a high-voltage battery electronic control module (BECM) 132, configured to control the high-voltage battery 110 , the archer 112and to control other high-voltage components; and a Body Control Module (BCM) 134 configured to control additional low-voltage functions of the vehicle 100 , such as headlights or door locks, to manage.

[0019] While each of these controls is illustrated as independent controls, the PCM 128 , the HPCM 130 , the BECM 132 and the BCM 134 Each may be part of a larger control system and may be independent of each other or of various other control systems throughout the vehicle. 100 to be controlled. It is therefore understood that the PCM 128 , the HPCM 130 , the BECM 132 and the BCM 134and one or more other control units can be collectively referred to as a "system control unit". The system control unit controls various actuators in response to signals from different sensors to control functions such as starting / stopping the combustion engine. 108 , Operating the electrical machines 104 , 106 , to provide wheel torque or the high-voltage battery 110 to charge, gear shifts with the gearbox 102to select or schedule, etc. The controller(s) may include a microprocessor or a central processing unit (CPU) connected to various types of computer-readable storage devices or media. Computer-readable storage devices or media can include volatile and non-volatile memory, for example, in read-only memory (ROM), random-access memory (RAM), and keep-alive memory (KAM). KAM is persistent or non-volatile memory that can be used to store various operating variables while the CPU is shut down.Computer-readable storage devices or media may be implemented using a number of known storage devices, such as PROM (programmable solid-state memory), EPROM (electronic PROM), EEPROM (electronic erasable PROM), flash memory, or any other electronic, magnetic, optical, or combined storage devices capable of storing data, some of which represent executable instructions used by the control unit to control the internal combustion engine or vehicle.

[0020] The system control unit communicates with various combustion engine / vehicle sensors and actuators via an input / output (I / O) interface, which can be implemented as a single integrated interface providing various raw data or signal conditioning, processing, and / or conversion, short-circuit protection, and the like. Alternatively, one or more dedicated hardware or firmware chips can be used to condition and process specific signals before they are provided to the CPU. Although not explicitly illustrated, the system control unit can send and / or receive signals to and / or from the transmission. 102 , the electric machines 104 , 106 , the internal combustion engine 108 , the shooter 112 , the converter 126 and the battery monitoring sensor 124communicate. Representative examples of parameters, systems, and / or components that can be directly or indirectly controlled using control logic executed by the system controller include the injection timing, injection quantity, and injection duration; the throttle position; the ignition timing of the spark plugs (in spark-ignition internal combustion engines); the timing and duration of intake and exhaust valves; V-belt (front-end accessory drive - FEAD) components, such as an alternator, an air conditioning compressor, a battery charging device, regenerative braking, engine / generator operation, and clutch pressures for the transmission. 102and the like. Sensors that communicate inputs via the I / O interface can be used to measure, for example, boost pressure, crankshaft position (PIP), engine speed (rpm), wheel speeds (WS1, WS2), vehicle speed (VSS), coolant temperature (ECT), intake manifold pressure (MAP), accelerator pedal position (PPS), ignition switch position (IGN), throttle position (TP), ambient air temperature (TMP), exhaust oxygen content (EGO) or the concentration or content of any other exhaust gas component, intake airflow (MAF), transmission gear, ratio or mode, transmission oil temperature (TOT), transmission turbine speed (TS), and torque converter lock-up clutch status. 34 (TCC), to display the braking or gear-changing mode (MDE).

[0021] The control logic or the functions performed by the system controller can be represented in one or more figures by flowcharts or similar diagrams. These figures provide representative control strategies and / or logic that can be implemented using one or more processing strategies, such as event-driven, interrupt-driven, multitasking, multithreading, and the like. Accordingly, different illustrated steps or functions can be performed in the illustrated sequence or in parallel, or in some cases, omitted. Although not always explicitly illustrated, the average person will recognize that one or more of the illustrated steps or functions can be executed repeatedly, depending on the specific processing strategy used.Similarly, the processing sequence is not necessarily required to achieve the features and benefits described herein, but is intended to facilitate illustration and description. The control logic can be implemented primarily in software executed by a microprocessor-based vehicle, internal combustion engine, and / or powertrain control system, such as the PCM. 128In an example, the control logic can, of course, be implemented in software, hardware, or a combination of both, depending on the specific application, within one or more controllers. If implemented in software, the control logic can be provided in one or more computer-readable storage devices or media containing data representing code or instructions that are executed by a computer to control the vehicle or its subsystems. These computer-readable storage devices or media can include one or more of a number of known physical devices that use electrical, magnetic, and / or optical storage to retain executable instructions and associated calibration information, operating variables, and the like.

[0022] The Fig. 2- Fig.6 illustrate exemplary processes for considering conditions under which the SoC of the low-voltage battery 114 is at a low level. Fig. 2 illustrates an overview process 200 , in which each of the processes 202 - 210 of the process 200 in relation to one of the processes 300 - 600 the Fig. 3- Fig. Section 6 below is described in detail. The processes 200 - 600 can be implemented using the system control described in detail above.

[0023] During the process 202 The system control initiates and monitors the function of the low-voltage battery's SoC. 114 um. During the process 204 The system control carries out a notification of a determination to the LV battery. 114to recharge, and requests permission to use an energy transfer from the low-voltage battery to the high-voltage battery to recharge the LV battery 114 to recharge. Aspects of the processes 202 and 404 will be discussed in detail during the process 300 out of Fig. 3 described.

[0024] The processes 206 , 208 and 210 This includes various possible measures if reporting is desired. The process 206 includes HV-LV energy transfer and is used in the process 400 out of Fig. 4 described in detail. The process 208 This includes remote starting of the combustion engine and is described in detail in the process. 500 out of Fig. 5 described. The process 210 The customer action includes the vehicle 100 to connect to an external charging device and is explained in detail in the process 600 out of Fig.6 described. It is understood that these measures may be presented to the customer sequentially when implementing these functions (e.g., requesting permission for HV-LV transmissions and, if this is refused, requesting permission for a remote start of the combustion engine) or essentially simultaneously.

[0025] For the sake of explanation, Table 1 illustrates a number of variables that are used in the description of the Fig. 3- Fig. 6. Each variable is defined by a name, a purpose describing the user of the variable, and an indication of whether the variable is used by a user or owner of the vehicle. 100It is specified whether the variables are calibratable or configurable. It is understood that the variables described herein may be stored on one or more of the various types of computer-readable storage devices or media described herein and may communicate with the one or more microprocessors or CPUs of the system control. Table 1 - Variables r. name Purpose Calibratable? 1 customerdealer_batt_charge_notification_enable d Logical attribute indicating whether the low SoC (State of Charge) notification for the low-voltage battery is enabled. J 2 LV_SoC_monitor_timer Timer used to control the frequency at which the low-voltage battery's state of charge (SoC) is checked to determine if a customer notification is required. N 3 LV_SoC_monitor_interval Interval at which the state of charge (SoC) of the low-voltage battery is checked when the vehicle is switched off. J 4 current_LV_battery_SoC Charging status of the low-voltage battery, as measured by the battery monitoring sensor. N 5 request_LV_battery_recharge_t hreshold State of charge (SoC) of the low-voltage battery, which triggers the start of the notification process. J 6 remote_energy_transfers_enabl ed Logical attribute used by the control panel to enable / disable the use of power transfers from the high-voltage battery to the low-voltage battery. J 7 remote_start_batt_charging_ena bled Logical attribute used by the control unit to enable / disable the use of remote starts of the internal combustion engine to charge the low-voltage battery. J to recharge. 8 cellular_modem_notifications_e nabled Logical attribute used by the control panel to enable / disable the use of the cellular modem to send messages to the customer. J 9 text_message_notifications_ena bled Logical attribute used by the control panel to enable / disable the use of the cellular modem to send text message notifications to the customer. J 10 voice_mail_notifications_enabl ed Logical attribute used by the control panel to enable / disable the use of the cellular modem to send voice message messages to the customer. J 11 WiFi_notifications_enabled Logical attribute used by the control panel to enable / disable the use of WiFi. J Sending text message notifications to the customer. 12 notification_timer Timer used by the control panel to send messages to the customer regularly if the customer has not responded to previous message notifications. J 13 notification_count Indicates the number of message messages sent. J 14 max_notification_count Sets the maximum number of notification messages to the customer. J 15 contact_address Includes a phone number, email address, or other contact information to receive messages. J

[0026] Fig. Figure 3 illustrates an example process 300 for function initialization and detection of a low battery charge status. 302 Does the vehicle 100 into ignition key off mode. For example, the system control can be adjusted according to the inputs to the BCM. 134 , which indicates the status of the ignition key, identify that the vehicle 100 is in ignition key off mode.

[0027] At 304The system control determines whether the low-voltage battery notification function is activated or deactivated. For example, the customer and dealer have the option to control this function through the vehicle's user interface. 100 to deactivate. This user interface may include one or more message centers, audio systems, telematics system screens (such as that of the SYNC system provided by Ford Motor Company), or similar devices. As another example, the message function in the vehicle assembly plant or dealer service area may be accessed through an in-vehicle diagnostic connector. 100 (e.g. via OBD-II) can be activated or deactivated.

[0028] To determine whether the low-voltage battery notification function is enabled or disabled, the control panel, in one example, accesses the logical attribute `customer-dealer_batt_charge_notification_enabled`, which is set to a first value (e.g., TRUE) to enable the low-voltage battery state of charge (SoC) notification and to a second value (e.g., FALSE) to disable the notification. If the low-voltage battery notification function is enabled, the control panel proceeds to [action]. 306 over. Otherwise, the process ends. 300 .

[0029] At 306The control unit initializes the low-voltage battery's message function. For example, the low-voltage battery's message function can have various options, the operation of which can be configured through initialization. These options might include, for instance, recharging the low-voltage battery using energy transfers from the high-voltage battery to the low-voltage battery via the converter. 126 to activate or deactivate.

[0030] Regarding the configuration of the energy transfer capability, the control unit can be configured to determine, for each ignition key off-event, whether the HV-LV energy transfers should be used as a mechanism for recharging the LV battery. 114 to be activated. Factors in this determination can affect the state of charge (SoC) of the high-voltage battery. 110 and the ambient temperature of the vehicle 100This includes the ambient temperature, as the charge acceptance of the LV battery may be low at low temperatures, thus reducing energy transfer to the LV battery. 114 may be of little or no effective benefit.

[0031] Alternatively, the vehicle assembly plant may temporarily disable the function for all ignition cycles if low-voltage battery state of charge (SoC) reporting is not desired or required at the assembly plant. Or, a dealer may temporarily disable the function for all ignition cycles if low-voltage battery reporting is not desired or required at the dealership. This could be because the dealer has a vehicle battery charging schedule. 100 at the dealer.

[0032] Similar options may be available for the use of remotely controlled starts of the internal combustion engine to charge the LV battery.114 to recharge. 100 If the device is located in an enclosed space, remote startup events can be overridden to be disabled by the control panel.

[0033] Regarding initialization, the system controller can use a variable HV_LV_batt_energy_transfer_count, which represents the number of energy transfers from the HV battery. 110 to the LV battery 114 via the converter 126 initialize to zero. The control panel can also use a variable `Remote_start_LV_batt_charge_count`, which records the number of remote vehicle starts. 100 initialize to zero.

[0034] At 308The system control resets the timer for the LV battery's SoC. For example, the system control can reset a variable or object called LV_SoC_monitor_timer and can further reset LV_SoC_monitor_timer to resume counting. 310 The control unit determines whether the low-voltage battery (LV) SoC monitoring timer has reached a monitoring interval at which the SoC of the low-voltage battery is checked when the vehicle is switched off. For example, the control unit can compare the LV_SoC_monitor_timer to determine if it exceeds a specified LV_SoC_monitor_interval. The timing of the LV_SoC_monitor_interval can be configured by the driver / customer and / or dealer. If the LV_SoC_monitor_timer does not exceed the specified LV_SoC_monitor_interval, the control unit remains in its current state. 310 If the LV_SoC_monitor_timer exceeds the LV_SoC_monitor_interval, the controller proceeds to the next operation. 312 above.

[0035] At 312 The system control reads the current SoC of the LV battery. 114 In one example, the system control can be directed to the battery monitoring sensor. 124 access to receive a SoC value (e.g., via the BCM) 134 The SoC value can be, for example, a voltage value that can be used alone or in combination with other factors (e.g., ambient temperature) to calculate the SoC.

[0036] At 314 The system control determines whether the current SoC of the LV battery 114a threshold is reached. In one example, the control unit reads the threshold from the variable `request_LV_battery_recharge_threshold`. The SoC threshold at which the notification process begins can be calibrated. Calibration can be used to adjust the duration between the time the customer is first notified to recharge the battery and the time the vehicle can no longer be started. During this period, a series of messages can be sent to the customer. This battery recharge countdown provides the customer with advance notice of a potential problem and gives them sufficient time to take appropriate measures to resolve it. When the current SoC falls below the threshold, the control unit proceeds with the recharge process. 316 over. If this is not the case, the system control reverts to priority. 308back.

[0037] At 316 The system control determines whether the ambient temperature allows energy transfer to the LV battery. 114 supported. In one example, the system control can be accessed via the temperature sensor. 136 access to check the temperature of the LV battery 114 and / or the environment. Based on the temperature, the control unit determines whether to charge the LV battery. 114 This is possible because extremely cold or warm temperatures can affect the charge acceptance of the LV battery. 114 can reduce this. For an example lead-acid low-voltage battery. 114 Charging may not be available below -20° Celsius or above 50° Celsius. If the LV battery... 114 When the device is at a temperature at which charging is acceptable, the controller proceeds to the process. 318 over. If this is not the case, the control system returns to the previous process. 308back. This return to the process 308 This can be done, for example, to suppress charging warnings to private customers when the temperature is too low to correct the low charge level.

[0038] At 318 The control panel determines whether remote energy transfers are enabled. For example, the control panel accesses a logical attribute `remote_energy_transfers_enabled`, which is set to a first value (e.g., TRUE) to enable energy transfers from the high-voltage battery to the low-voltage battery, and to a second value (e.g., FALSE) to disable energy transfers from the high-voltage battery to the low-voltage battery. When transfers are enabled, the control panel proceeds to the operation 402 of the process 400 If this is not the case, the control system proceeds to the next step. 320 above.

[0039] At 320 The control unit determines whether battery charging via remote start is enabled. For example, the control unit accesses a logical attribute `remote_start_batt_charging_enabled`, which is set to a first value (e.g., `TRUE`) to enable the use of remote combustion engine starts to charge the low-voltage battery, and to a second value (e.g., `FALSE`) to disable the use of remote combustion engine starts to charge the low-voltage battery. When remote starts are enabled, the control unit proceeds to the process. 602 of the process 600 over. If this is not the case, the control system will proceed. 502 of the process 500 above.

[0040] Fig. Figure 4 illustrates an example process. 400 Regarding the notification about recharging the LV battery 114and requesting permission to use an energy transfer from the low-voltage battery to the high-voltage battery to power the LV battery 114 to recharge.

[0041] At 402 The system control determines whether mobile modem notifications are enabled. If a vehicle 100 a mobile modem 118 This function can provide text messages and / or voice messages, and that the LV battery 114 requires charging. In one example, the control panel accesses a logical attribute `cellular_modem_notifications_enable`, which is set to a first value (e.g., TRUE) to enable the use of the cellular modem to send notifications to the customer, and to a second value (e.g., FALSE) to disable the use of the cellular modem to send notifications to the customer. When cellular notifications are enabled, the control panel proceeds to the operation. 404If this is not the case, the control system proceeds to the next step. 412 above.

[0042] At 404 The system control panel determines whether text message notifications are enabled. For example, the system control panel accesses a logical attribute `text_message_notifications_enable`, which is set to an initial value (e.g., `TRUE`) to enable the use of the cellular modem. 118 To enable text message notifications to the customer, and to disable the use of the cellular modem for sending text message notifications to the customer, the control proceeds to the process. 406 If this is not the case, the control system proceeds to the next step. 408 above.

[0043] At 406 The control panel sends a text message message using the mobile modem. 118In one example, the control panel accesses the variable or parameter `contact_address` to receive the phone number, email address, or other contact information for the user. The text message may include an indication that the LV battery... 114 of the vehicle 100 It should be recharged within a specific period of time (e.g., within three days) to keep the vehicle running. 100 to allow the vehicle to continue starting. The message may also indicate that this is a normal occurrence and does not require a visit to the dealership for maintenance. The message may also include instructions on how to perform the recharging process. These instructions may include, for example, restarting the internal combustion engine. 108 of the vehicle 100to run for a specified period (e.g., thirty minutes). For plug-in hybrid (PHEV) and battery electric (BEV) vehicles, the instructions may instruct the user to start the vehicle. 100 to connect to an external battery charger. If a remote starter is available, it can be used to charge the LV battery. 114 to recharge when the vehicle 100 in an open space. In car dealerships and vehicle assembly plants, the instructions can tell the user how to operate the vehicle. 100 with an external charging device for the LV battery 114 to connect. The message may also include a statement that the LV battery is being recharged. 114 enables the vehicle 100 to provide support for a selected number of days before the LV battery 114requires recharging. The message may also indicate that the HV-LV battery energy transfers will reduce the vehicle's fuel efficiency for a short period. After the process 406 The control process goes to [unclear] 408 above.

[0044] At 408 The control panel determines whether voicemail notifications are enabled. For example, the control panel accesses a logical attribute `voice_mail_notifications_enable`, which is set to a first value (e.g., TRUE) to enable the use of the cellular modem to send voicemail notifications to the customer, and to a second value (e.g., FALSE) to disable the use of the cellular modem for sending voicemail notifications to the customer. If voicemail notifications are enabled, the control panel proceeds to the operation. 410 If this is not the case, the control system proceeds to the next step. 412above.

[0045] At 410 The control panel sends a voice message using the mobile modem. 118 The voice message can contain content similar to that described above for the text message. After the process... 410 The control process goes to [unclear] 412 above.

[0046] At 412 The control panel determines whether WiFi notifications are enabled. For example, the control panel accesses a logical attribute `WiFi_notifications_enabled`, which is set to a first value (e.g., `TRUE`) to enable the use of WiFi to send text message notifications to the customer, and to a second value (e.g., `FALSE`) to disable the use of WiFi to send text message notifications to the customer. If WiFi notifications are enabled, the control panel proceeds to the next step. 414If this is not the case, the control system proceeds to the next step. 416 above.

[0047] At 414 The control panel sends a text message notification using the WiFi modem 120. The WiFi text message notification can contain content similar to that described above regarding the mobile text message notification of the process. 406 After the process 414 The control process goes to [unclear] 416 above.

[0048] At 416The control panel resets the notification timer and the notification count. In one example, the control panel resets a variable or parameter `notification_timer`, which it uses to send notifications to the customer periodically if the customer has not responded to previous notification messages, to zero. In another example, the control panel increments a `notification_count` that is set to the number of consecutive notification messages that have been sent.

[0049] At 418 The control panel determines whether a response has been received from the merchant or customer. For example, the control panel can monitor responses to messages. If a response is received, the control panel proceeds to the next step. 420 over. Otherwise, the control proceeds to process. 426 above.

[0050] At 420The system control determines whether the response indicates approval of the transfer. For example, if a positive response is received from the recipient of the message (e.g., a dealer or customer), the transfer is approved and the LV battery is charged. 114 is being recharged. If the response indicates authorization to perform the transfer, the controller proceeds to the operation. 422 over. Otherwise, the process ends. 400 In other examples, the process reverses. 400 to the process 304 of the process 300 back, instead of ending.

[0051] During the process 422 The control system performs a transfer of power from the HV battery. 110 to the LV battery 114 This transmission can be demonstrated using a DC / DC converter. 126 be carried out. After the process 422 The control process goes to [unclear] 424 above.

[0052] At424 The control unit updates the customer notification logic. After an HV-LV notification event, several next steps are possible depending on the event's outcome. For example, if an HV-LV energy transfer has occurred, the control unit can decide whether to allow further transfers. The control unit can be calibrated to allow energy transfers when the HV battery is... 110 Energy is available for a set number of times or only once. If the transfer was rejected and remote starts of the combustion engine are not possible, the following applies: 108 If possible, the control unit can proceed by asking the customer for permission to remotely start the combustion engine. 108to perform, request. If the transmission is rejected and remote starts are not possible or enabled, the control unit can send a final message to the customer to start the combustion engine (e.g., for 30 minutes) or to stop the vehicle. 100 to connect to an external charging device. If no response is received, the control panel can select to perform a retry strategy. One or more of these actions can be performed during these operations, but for brevity, they are not shown as a single process. After the operation 424 The control returns to the process 304 of the process 300 back.

[0053] At 426The control panel determines whether the notification time has exceeded the notification interval. The control panel can access a variable or parameter called `notification_interval` to retrieve the timer value for the notification interval. For example, if no response is received within the time the `notification_timer` exceeds the notification interval, the control panel proceeds to the next step. 428 If the notification_timer has not yet expired, the process continues. 418 above.

[0054] At 428The control panel determines whether the notification count has exceeded the maximum notification count. For example, notifications can be resent a calibratable number of times. The control panel can access a variable or parameter `max_notification_count` to retrieve the maximum number of notification messages to the customer and can access a variable or parameter `notification_count` to retrieve the current number of notification messages to the customer. If `notification_count` exceeds `max_notification_count`, the control panel proceeds to the next step. 424 over, to provide an update. Otherwise, the controller returns to the previous process. 402 back.

[0055] Fig. Figure 5 illustrates an example process. 500 to report the combustion engine 108 of the vehicle 100 to start remotely to charge the LV battery 114to recharge. It goes without saying that the processes 502 - 528 of the process 500 the processes 400 - 428 of the process 400 correspond, with the exception that the process 522 the LV battery 114 using the remote start of the combustion engine 108 instead of via transmission from the HV battery 110 charges.

[0056] Fig. Figure 6 illustrates an example process. 600 Regarding the notification for the connection to an external charging device. It is understood that the processes 602 - 618 and 624 - 628 the processes 400 - 428 of the process 500 correspond, with the exception that the specified measure consists of asking the customer to switch on the internal combustion engine 108 to restart the vehicle 100 with an external charging device (e.g. the HV battery) 110or the LV battery 114 ) to connect. Therefore, the procedures regarding the approval of the transfer and the execution of the transfer are not applicable.

[0057] By using the system controls and processes described herein, the dealer and / or the customer can be warned when the state of charge (SoC) of the low-voltage battery is low. This functionality allows certain higher-level strategies to be additionally implemented to further protect the LV battery. 114 to recharge. For example, the control unit can, in a given ignition key switch-off event, perform a configurable number of automatic recharges of the low-voltage battery. 114 perform (e.g., one, two, five, once a week, etc.), whereby if more charges are required, the user can be warned of these additional low SoC states.

[0058] The computing devices described herein generally include computer-executable instructions, the instructions being capable of being executed by one or more computing devices, such as those listed above. Computer-executable instructions may be assembled or interpreted by computer programs created using a variety of programming languages ​​and / or technologies, including, but not limited to, either alone or in combination, Java™, C, C++, C#, Visual Basic, JavaScript, Perl, etc. In general, a processor (e.g., a microprocessor) receives instructions, e.g., from memory, a computer-readable medium, etc., and executes those instructions, thereby carrying out one or more processes, including one or more of the processes described herein. Such instructions and other data may be stored and transmitted using a variety of computer-readable media.

[0059] Although exemplary embodiments have been described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the terms used in the description are descriptive rather than limiting, and it is understood that various modifications can be made without deviating from the spirit and scope of the invention. Furthermore, the features of different implemented embodiments can be combined to form further embodiments of the invention.

Claims

[1] Vehicle, comprising: a low-voltage battery; a high-voltage battery; a converter that reduces the voltage supplied to the low-voltage battery by the high-voltage battery; and a control system programmed to use the converter in an ignition key off cycle to charge the low-voltage battery a calibrated number of times the low-voltage battery falls below a predefined charge status threshold, and to send a wireless message at a later time when the low-voltage battery falls below the threshold. [2] Vehicle according to claim 1, wherein the control system is further programmed to use a mobile cellular modem of the vehicle to send a text message via a Wide Area Network to an address of a user of the vehicle indicating that the low voltage battery has fallen below the threshold. [3] Vehicle according to claim 1, wherein the control system is further programmed to use a mobile cellular modem of the vehicle to send a voice message via a Wide Area Network to an address of a user of the vehicle indicating that the low voltage battery has fallen below the threshold. [4] Vehicle according to claim 1, wherein the control system is further programmed to: to identify that the vehicle is connected to a user's local area network; and to send a message via the Local Area Network to an address of a user of the vehicle, indicating that the low-voltage battery has fallen below the threshold. [5] Vehicle according to claim 1, wherein the control system is further programmed to: to regularly calculate the charge status of the low-voltage battery, and to send a wireless message to a user in response to the charging status. [6] Vehicle according to claim 1, wherein the message includes instructions on how to perform a recharging event and that the recharging event does not require vehicle service. [7] Vehicle according to claim 1, wherein the message includes instructions for a user to confirm that the vehicle is outside an enclosed area before an internal combustion engine of the vehicle is started to charge the low-voltage battery. [8] Vehicle according to claim 1, wherein the message includes information indicating that a transfer of energy from the high-voltage battery to the low-voltage battery temporarily reduces the vehicle's fuel efficiency. [9] Vehicle according to claim 1, wherein the calibrated number of times is one. [10] Vehicle according to claim 1, wherein the calibrated number of times is two. [11] Procedure, encompassing: Sending a message to a predefined contact address in response to a regularly calculated charge status of a vehicle's low-voltage battery that falls below a predefined threshold; and Using a converter that reduces the voltage supplied to the low-voltage battery by a high-voltage battery of the vehicle in order to charge the low-voltage battery in response to receiving a response from the contact address indicating confirmation of charging. [12] Method according to claim 11, further comprising using a mobile communication modem of the vehicle to send the message as a text message via a Wide Area Network to an address of a user of the vehicle indicating that the low voltage battery has fallen below the threshold. [13] Method according to claim 11, further comprising using a mobile communication modem of the vehicle to send the message as a voice message via a Wide Area Network to an address of a user of the vehicle indicating that the low voltage battery has fallen below the threshold. [14] Method according to claim 11, further comprising sending the message as a message via a Local Area Network to an address of a user of the vehicle indicating that the low voltage battery has fallen below the threshold, in response to the identification that the vehicle is connected to a Local Area Network of a user of the vehicle.

Citation Information

Patent Citations

  • Systems and methods for preventing the complete discharge of a battery in a vehicle

    DE102013212857A1

  • predictive BATTERY LOW VOLTAGE ALERT FOR ELECTRIFIED VEHICLE

    DE102016106347A1