Charging control system for charging unit of battery pack

Abstract

The controller (40) may receive charging information related to the battery pack (20) before initiating charging of the battery pack (20) by the charging unit (14). The controller (40) may determine whether charging the battery pack (20) will comply with the charging guidelines by comparing the charging information with the charging guidelines. The controller (40) may output a request to the operator input indicating whether to initiate charging of the battery pack (20) in response to the determination that charging the battery pack (20) will violate the charging guidelines. The controller (40) may initiate charging of the battery pack (20) in response to the operator input indicating to initiate charging.

Description

Technical Field

[0001] This disclosure relates generally to batteries, and for example to a charging control system for a charging unit of a battery pack. Background Technology

[0002] The machine may include one or more battery packs to provide power to machine components such as lights, computer systems, and / or motors. The battery packs may be associated with a modular design that includes multiple battery modules. Each battery module may include multiple battery cells. The state of charge (SOC) of the battery pack decreases with machine use, and the charging of the battery pack can be determined by the machine operator. Therefore, the operator may charge the battery pack in suboptimal ways, such as charging it too frequently, charging it before it is fully depleted, or allowing it to reach extremely low charge levels before charging. Suboptimal charging patterns can adversely affect the health of the battery pack, thereby reducing its productivity and lifespan.

[0003] EP application number 4191743A1 ('743 application) discloses an electric work machine including a secondary battery, a battery management unit for managing the secondary battery, and a controller for controlling normal charging or diagnostic charging of the secondary battery. The controller determines whether to recommend diagnostic charging based on the operating history of the secondary battery output from the battery management unit, and when determining whether to recommend diagnostic charging, it determines whether to perform the diagnostic charging based on the state of the secondary battery output from the battery management unit, the estimated charging cycle required for diagnostic charging, and the on-site work plan including the work start time.

[0004] The controlled charging of the battery described in application '743' is based on the battery's operating history and state. However, application '743 does not disclose charging control based on the battery's optimal charging behavior. Therefore, the technology described in application '743' can provide charging control based on suboptimal charging modes, which reduces battery pack productivity and lifespan, as mentioned above.

[0005] The charging control system disclosed herein solves one or more of the problems described above and / or other problems in the prior art. Summary of the Invention

[0006] A charging control system may include a contactor configured to control current flow in a charging unit, and a controller. The controller may be configured to receive charging information related to the battery pack from a battery management system of the battery pack before initiating charging of the battery pack by the charging unit. The controller may be configured to identify whether charging the battery pack would comply with the charging guidelines based on a comparison of the charging information with the charging guidelines. The controller may be configured to output a request for operator input indicating whether to initiate charging of the battery pack in response to the identification that charging the battery pack would violate the charging guidelines. The controller may be configured to initiate charging of the battery pack in response to the operator input indicating to initiate charging.

[0007] A method may include receiving charging information related to the battery pack by a controller before initiating charging of the battery pack by a charging unit. The method may include the controller identifying whether charging the battery pack would comply with the charging guidelines based on a comparison of the charging information with those guidelines. The method may include the controller outputting a request for operator input indicating whether to initiate charging of the battery pack in response to the identification that charging the battery pack would violate the charging guidelines. The method may include the controller initiating charging of the battery pack in response to the operator input indicating to initiate charging.

[0008] The charging unit may include a display and a controller. The controller may be configured to receive charging information related to the battery pack from the battery management system of the battery pack before initiating charging of the battery pack by the charging unit. The controller may be configured to determine whether charging the battery pack would comply with the charging guidelines by comparing the charging information with the charging guidelines. The controller may be configured to output a request for operator input indicating whether to initiate charging of the battery pack in response to the determination that charging the battery pack would violate the charging guidelines and for display purposes. The controller may be configured to initiate charging of the battery pack in response to the operator input indicating to initiate charging. Attached Figure Description

[0009] Figure 1 A perspective view of an exemplary machine charging system is shown.

[0010] Figure 2 This is a diagram of an exemplary charging control system.

[0011] Figure 3 This is a flowchart of an exemplary process associated with charging a battery pack.

[0012] Figure 4This is a flowchart of an exemplary process associated with charging a battery pack. Detailed Implementation

[0013] This disclosure relates to a charging control system suitable for any machine that uses power supplied by a battery. For example, the machine may perform operations associated with industries such as mining, construction, agriculture, transportation, or any other sector.

[0014] Figure 1 A perspective view of an exemplary machine charging system 10 is shown. The machine charging system 10 includes a machine 12, a charging unit 14 (e.g., a power station), and one or more cables 16 electrically connecting the machine 12 and the charging unit 14.

[0015] Machine 12 can be a work-related machine. For example, machine 12 can perform earthmoving, excavation, or another operation associated with industries such as mining. For instance, as... Figure 1 As shown, machine 12 is a wheel loader. However, machine 12 can be another type of machine, such as a compactor, paver, cold milling machine, grader, backhoe loader, harvester, excavator, automatic grader, skid steer loader, mining machine, tractor, or bulldozer, etc.

[0016] Machine 12 is an electrically driven machine (e.g., an electric vehicle). For example, machine 12 may be a fully electric vehicle or a partially electric vehicle (e.g., a hybrid vehicle including a battery and an engine). Machine 12 includes a frame 18. Machine 12 includes a battery pack 20 (e.g., one or more battery packs 20) supported by the frame 18. Battery pack 20 can power a motor 22 supported by the frame 18 and / or other components of machine 12 (e.g., lights, electronics, temperature control systems, etc.). Battery pack 20 may include a housing that accommodates (e.g., connected in series and / or parallel) one or more battery modules, and each battery module may include (e.g., connected in series and / or parallel) one or more battery cells. Each battery cell is associated with a chemistry type, such as lithium-ion (Li-ion) (e.g., lithium-ion polymer (Li-ion polymer), lithium iron phosphate (LFP) and / or nickel manganese cobalt (NMC)), nickel metal hydride (NiMH), or nickel cadmium (NiCd), etc.

[0017] Battery pack 20 may include a battery management system (BMS) 38. BMS 38 may include one or more controllers. For example, BMS 38 may include a corresponding module controller for each battery module and / or a battery pack controller for battery pack 20. The battery pack controller may have a corresponding communication link with each module controller. Furthermore, BMS 38 may include one or more sensors communicatively connected to one or more controllers. Sensors may include current sensors, voltage sensors, temperature sensors, and / or humidity sensors, etc. BMS 38 may be configured to control the startup and / or shutdown processes of battery pack 20, rebalance battery cells and / or battery modules, monitor the current and / or voltage of battery cells, battery modules, and / or battery pack 20, monitor the state of charge (SOC) of battery cells, battery modules, and / or battery pack 20, monitor the resistance and / or impedance of battery cells, battery modules, and / or battery pack 20, and / or monitor the temperature and / or humidity of battery cells, battery modules, and / or battery pack 20, etc.

[0018] Machine 12 may include a charger connector 24. Charger connector 24 may receive a mounting portion 26 of cable 16 to connect charging unit 14 to machine 12. Charger connector 24 and mounting portion 26 may form a snap-fit ​​connection or otherwise facilitate connection of cable 16 to machine 12. In one example, charging unit 14 may (e.g., by connecting the mounting portion 26 of cable 16 to charger connector 24) deliver direct current (DC) to battery pack 20.

[0019] Frame 18 may be supported by one or more ground engagement elements 30 driven by motor 22. For example, ground engagement elements 30 may include wheels, tracks, etc., as shown. Machine 12 may include a cab 28 from which one or more operators may operate and / or control one or more operations of machine 12. Furthermore, machine 12 may include one or more implements 32 (e.g., buckets) that are coupled to and / or movable relative to frame 18 via one or more hydraulic systems 36, comprising one or more sets of levers and cylinders that can be operated by movement and / or pressurization of hydraulic fluid via one or more pumps. Battery pack 20 may (e.g., via hydraulic system 36) power implements 32.

[0020] The charging unit 14 may be a portable charger (e.g., mobile around the work site) or a permanently located charger. The charging unit 14 is a power source. For example, the charging unit 14 may be a high-voltage power source (e.g., 500 volts (V) or higher), or another voltage power source. The charging unit 14 (e.g., its internal battery) may be charged or otherwise powered by connection to one or more of the power grid, a generator or generator set, solar panels, a wind turbine or wind power source, a water power source, and / or another power source (e.g., an AC or DC current source). The charging unit 14 may include a power output for connecting the machine 12 to the charging unit 14 via cable 16. In this way, the charging unit 14 may supply power to the battery pack 20 via cable 16.

[0021] Cable 16 may include one or more conductive cables or wires configured to electrically and / or communicatively connect charging unit 14 and machine 12. Cable 16 may be configured to deliver a high voltage (e.g., 500V) or another voltage from charging unit 14 to machine 12. In some examples, charging unit 14 may include cable 16 (e.g., cable 16 may be fixedly coupled to the output of charging unit 14). Alternatively, charging unit 14 may include a charger connector (not shown) to provide a removable connection between cable 16 and charging unit 14 in a manner similar to that described above.

[0022] The charging unit 14 may include a controller 40 (e.g., one or more controllers). The controller 40 may be configured (e.g., via instructions, software, firmware, etc.) to perform one or more operations described herein related to controlling the charging unit 14. The controller 40 may be coupled to a display 42 (e.g., a touchscreen display) of the charging unit 14 and / or one or more operator controls 44 of the charging unit 14.

[0023] Controller 40 may include one or more processors and / or one or more memories. The processor may include a central processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or another type of processing unit. The processor may be implemented in hardware, firmware, and / or a combination of hardware and software. In some embodiments, the processor may include one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein. The memory may include volatile and / or non-volatile memory. For example, the memory may include random access memory (RAM), read-only memory (ROM), and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). The memory may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus). The memory may be a non-transitory computer-readable medium. The memory may store information relating to the operation of battery pack 20, battery module, and / or battery cell, one or more instructions, and / or software (e.g., one or more software applications). The memory may include one or more memories, such as those coupled (e.g., communicatively coupled) to the processor via a bus. Communication coupling between the processor and memory enables the processor to read and / or process information stored in memory and / or store information in memory.

[0024] As mentioned above, Figure 1 Provided as an example. Other examples may be provided with reference to [the relevant information]. Figure 1 The examples described are different.

[0025] Figure 2 This is a diagram of an exemplary charging control system 50. As shown, the charging control system 50 may include a controller 40, a display 42, a contactor 52, and / or a cable 16. For example, the controller 40 may have a communication link with the display 42, the controller 40 may have electrical connections and / or communication links with the cable 16 and the contactor 52, and the cable 16 may have an electrical connection with the contactor 52. The charging control system 50 may be configured to control the charging of the battery pack 20 of the machine 12 by the charging unit 14.

[0026] When battery pack 20 is connected to charging unit 14 via cable 16, controller 40 and / or BMS 38 may detect the charging connection (e.g., based on detecting current in one or more monitoring contacts). Furthermore, when battery pack 20 is connected to charging unit 14 via cable 16 (e.g., when a charging connection is detected), controller 40 and BMS 38 may exchange information before initiating charging of battery pack 20 by charging unit 14 (e.g., during signal transmission in a handshake procedure). For example, controller 40 may receive identification information and / or charging information from BMS 38 (e.g., after establishing a connection between battery pack 20 and charging unit 14, but before initiating charging of battery pack 20). In some examples, controller 40 may indicate a request for identification information and / or charging information to BMS 38, and controller 40 may receive identification information and / or charging information in response to such request.

[0027] Identification information may indicate the identifier of battery pack 20 (e.g., battery pack serial number), the specifications of battery pack 20 (e.g., manufacturer of battery pack 20, model of battery pack 20, power capacity of battery pack 20, service life of battery pack 20, etc.), and / or the identifier of machine 12 (e.g., machine serial number), etc. Charging information may relate to battery pack 20. Charging information may relate to the state of battery pack 20 at the time battery pack 20 is connected to charging unit 14. Charging information may indicate the current SOC of battery pack 20, the current temperature of battery pack 20, etc. In some embodiments, if the identification information indicates that the manufacturer of battery pack 20 is a specific manufacturer, controller 40 may use the charging information in conjunction with operation to evaluate whether to initiate charging of battery pack 20 as described herein. Otherwise, if the manufacturer of battery pack 20 is not a specific manufacturer, controller 40 may cause charging of battery pack 20 to be initiated without using the charging information.

[0028] The controller 40 can identify whether historical charging information related to the battery pack 20 is available based on identification information (e.g., the identifier of the battery pack 20). For example, the controller 40 can use the identification information (e.g., the identifier of the battery pack 20) ​​to retrieve historical charging information related to the battery pack 20. For instance, the controller 40 can compare the identification information with a set of historical charging information (e.g., in a database) to retrieve historical charging information related to the battery pack 20, and / or the controller 40 can send the identification information in a request to a service that provides historical charging information and receive historical charging information related to the battery pack 20 from that service. The availability of historical charging information related to the battery pack 20 indicates that the battery pack 20 has been previously charged. The unavailability of historical charging information related to the battery pack 20 indicates that the battery pack 20 has not been previously charged (or no previous charge was recorded for the battery pack 20).

[0029] The set of historical charging information can be stored locally at the charging unit 14, or it can be stored in another device (e.g., a cloud device), and the controller 40 can be configured to communicate with that other device. When stored locally at the charging unit 14, the set of historical charging information may only relate to charging performed at the charging unit 14 and / or may relate to charging performed at other charging units 14. For example, multiple charging units 14 can communicate with each other to exchange historical charging information captured at each charging unit 14, or historical charging information captured at multiple charging units 14 can be transmitted to a central node, which distributes the historical charging information to the multiple charging units 14.

[0030] If historical charging information related to battery pack 20 is unavailable (e.g., this is the first charge of battery pack 20), controller 40 may cause charging of battery pack 20 to be initiated, as described below. If historical charging information related to battery pack 20 is available, controller 40 may determine whether charging of battery pack 20 should be initiated, as described herein. Historical charging information may indicate data related to one or more previous charging instances of battery pack 20. For example, data from a previous charging instance may indicate the initial SOC and / or temperature of battery pack 20 before the start of the previous charging instance, the final SOC and / or temperature of battery pack 20 after the completion of the previous charging instance, and / or the timestamp of the previous charging instance (e.g., when the previous charging instance was initiated and / or completed), etc.

[0031] Controller 40 may be equipped with charging guidelines (e.g., controller 40 may store them in memory). The charging guidelines may indicate one or more best practices for charging the battery pack. Best practices may be practices for charging the battery pack that, if followed, will increase the battery pack's lifespan (e.g., relative to if best practices are not followed). For example, charging guidelines may indicate the minimum SOC for charging the battery pack, the maximum SOC for charging the battery pack, the SOC range in which the battery pack should be charged, the minimum battery temperature for charging the battery pack, the maximum battery temperature for charging the battery pack, the battery temperature range in which the battery pack should be charged, and / or the frequency between charging the battery pack (e.g., the delay that should be observed between charging the battery pack), etc. In some implementations, the charging guidelines may be generated using historical charging data and historical battery life data as input to an artificial intelligence model (e.g., by controller 40).

[0032] In some implementations, the controller 40 may select a specific charging guideline associated with the battery pack 20 (e.g., from a set of charging guidelines). For example, the selected charging guideline may be specific to the model of the battery pack 20, the power capacity of the battery pack 20, and / or the service life of the battery pack 20. Alternatively, the controller 40 may adjust a baseline charging guideline based on the model of the battery pack 20, the power capacity of the battery pack 20, and / or the service life of the battery pack 20.

[0033] Controller 40 can compare charging information with charging guidelines (e.g., selected and / or adjusted charging guidelines). For example, controller 40 can compare charging information with charging guidelines in response to the availability of historical charging information related to battery pack 20 (e.g., this is not the first charge of battery pack 20). As an example, controller 40 can compare charging information with charging guidelines to identify whether the current SOC of battery pack 20 is above the minimum SOC, below the maximum SOC, and / or within the SOC range. As another example, controller 40 can compare charging information with charging guidelines to identify whether the current temperature of battery pack 20 is above the minimum battery temperature, below the maximum temperature, and / or within the battery temperature range. Therefore, controller 40 can determine (e.g., at the current time) whether charging battery pack 20 conforms to charging guidelines (e.g., whether charging conforms to best practices) based on the comparison of charging information with charging guidelines.

[0034] The controller 40 can also compare historical charging information with charging guidelines. For example, the controller 40 can compare historical charging information with charging guidelines to identify whether the elapsed time since the previous charging instance of the battery pack 20 adheres to the charging frequency. Therefore, the controller 40 can identify (e.g., at the current time) whether charging the battery pack 20 conforms to the charging guidelines (e.g., whether the charging conforms to best practices) based on the comparison between historical charging information and charging guidelines.

[0035] In response to recognizing that charging battery pack 20 conforms to charging guidelines, controller 40 may cause charging of battery pack 20 to be initiated, as described below. Otherwise, in response to recognizing that charging battery pack 20 would violate charging guidelines, controller 40 may output an indication that charging battery pack 20 would violate charging guidelines. For example, controller 40 outputting this indication may cause information indicating that charging battery pack 20 would violate charging guidelines (e.g., indicating a violation of best practices) to be displayed on display 42. In some examples, this information may indicate one or more charging guidelines that would be violated when charging battery pack 20. In some examples, controller 40 may also output information indicating whether historical charging information conforms to charging guidelines. For example, controller 40 may output an indication of one or more historical violations of charging guidelines, and the information displayed on display 42 may also indicate one or more historical violations of charging guidelines.

[0036] Additionally, in response to recognizing that charging battery pack 20 would violate charging guidelines, controller 40 may cause a notification indicating a violation to be transmitted to off-board charging unit 14. For example, this notification may be received at the user device of the supervisor associated with machine 12. Alternatively, controller 40 may combine historical violations of charging guidelines indicated by historical charging information to determine whether the current violation of charging guidelines indicates a repeat violation (e.g., a threshold number of repeat violations), and controller 40 may cause a notification to be transmitted in response to determining a repeat violation. Repeat violations may be counted for a single operator of machine 12 or multiple operators of machine 12. For example, historical charging information may indicate the identity of the operator of machine 12 for each previous charging instance. Therefore, controller 40 may cause a notification to be transmitted in response to determining a repeat violation (e.g., a threshold number of repeat violations) associated with a single operator of machine 12 (e.g., the operator currently operating machine 12). Thus, the notification may indicate the operator's identity.

[0037] Furthermore, in response to the detection that charging battery pack 20 would violate charging guidelines, controller 40 may output a request for a first operator input indicating whether charging should be initiated. For example, outputting this request by controller 40 may cause information requesting operator input on display 42 to indicate whether charging should be initiated. This information may, for example, include one or more virtual buttons that the operator can select to indicate whether charging should be initiated. In some examples, controller 40 may output the request for the first operator input when the charging information indicates that the current SOC of the battery pack at least meets the minimum SOC, but not when the charging information indicates that the current SOC of the battery pack is below the minimum SOC (e.g., because charging should be initiated when the current SOC is below the minimum SOC, even if doing so violates charging guidelines).

[0038] Therefore, even after notifying the operator that charging battery pack 20 would violate charging guidelines, the operator can still be offered the option to continue charging battery pack 20. In some embodiments, charging unit 14 may require authentication input (e.g., from a supervisor) to continue charging even in violation of guidelines. Authentication input may include passwords, access codes, physical keys, key fobs, etc. Therefore, controller 40 can allow charging of battery pack 20 to continue even in violation of guidelines based on authentication of the authentication input.

[0039] In response to a first operator input instruction to initiate charging, controller 40 may output information (e.g., display this information on display 42) indicating a battery life prediction (e.g., remaining lifespan prediction) of battery pack 20 resulting from charging battery pack 20 in violation of charging guidelines. Controller 40 may determine the battery life prediction using a prediction algorithm that considers charging behavior (e.g., SOC at charging initiation, charging frequency, etc.) and / or using a machine learning model that uses inputs of charging behavior to output the battery life prediction. The battery life prediction may be based on the model of battery pack 20, the power capacity of battery pack 20, and / or the age of battery pack 20, or adjusted according to a baseline prediction based on the model of battery pack 20, the power capacity of battery pack 20, and / or the age of battery pack 20.

[0040] Furthermore, in response to a first operator input indicating that charging should be initiated, the controller 40 can output a request for a second operator input indicating whether charging should be initiated, in a manner similar to that described above. Therefore, after informing the operator of the impact on battery life resulting from charging the battery pack 20 in violation of charging guidelines, the operator can still be provided with the option to continue charging the battery pack 20. As mentioned above, the charging unit 14 may require authentication input (e.g., from a supervisor, etc.) to continue charging in violation of guidelines.

[0041] In response to an operator input instructing charging to be initiated (e.g., a first operator input and / or a second operator input), controller 40 can cause charging of battery pack 20 to be initiated. To cause charging of battery pack 20 to be initiated, controller 40 can cause contactor 52 to close (e.g., contactor 52 may have a normally open configuration). For example, controller 40 can output a control signal to contactor 52 to cause contactor 52 to close. Contactor 52 may be an electrical switching device configured to control the flow of current in charging unit 14. Therefore, when contactor 52 is closed, current can flow in charging unit 14 to provide charging of battery pack 20 via cable 16. Conversely, when contactor 52 is open, current is prevented from flowing in charging unit 14, thus preventing charging of battery pack 20.

[0042] In response to an operator input (e.g., a first operator input and / or a second operator input) instructing not to initiate charging, controller 40 may output information (e.g., to cause information to be presented on display 42). This information may indicate a recommended State of Charge (SOC) of battery pack 20 at which charging of battery pack 20 is performed and / or a recommended frequency between charging of battery pack 20 to be used. The recommended SOC and / or recommended frequency between charging may be based on charging guidelines. In some examples, the recommended SOC and / or recommended frequency between charging may be based on the model of battery pack 20, the power capacity of battery pack 20, and / or the lifespan of battery pack 20, or adjusted according to a baseline recommendation based on the model of battery pack, the power capacity of battery pack, and / or the lifespan of battery pack. Alternatively or additionally, controller 40 may determine a battery life prediction (e.g., remaining usable life prediction) of battery pack 20 resulting from charging battery pack 20 according to (a plurality of) recommendations, and this information may indicate the battery life prediction. Furthermore, in response to an operator input (e.g., a first operator input and / or a second operator input) instructing that charging should not be initiated, controller 40 may limit charging of battery pack 20. To limit charging of battery pack 20, controller 40 may keep contactor 52 open (or open if the contactor has a normally closed configuration).

[0043] After initiating charging (e.g., in any of the scenarios described herein) or limiting charging, controller 40 may generate log entries indicating the initial SOC of battery pack 20 before charging and the final SOC of battery pack 20 after charging is complete (e.g., generating historical charging data related to battery pack 20). Completion of charging of battery pack 20 may include situations where battery pack 20 is actually charged (e.g., the SOC of battery pack 20 increases) or situations where battery pack 20 is connected to charging unit 14 but is not actually charged (e.g., because operator input indicates that charging should not be initiated). Log entries may also indicate timestamps associated with charging (or charging attempts), the temperature of battery pack 20, etc. In addition, after initiating charging (e.g., in any of the initiation charging scenarios described herein) or limiting charging, controller 40 may output a list indicating previous charges to battery pack 20 (e.g., which may now include current charges that have been completed) and information on whether these previous charges comply with or violate charging guidelines (e.g., to make the information appear on display 42), thereby providing an overview of how battery pack 20 is handled over time.

[0044] As mentioned above, Figure 2 Provided as an example. Other examples may be provided with reference to [the relevant information]. Figure 2 The examples described are different.

[0045] Figure 3 This is a flowchart of an exemplary process 300 associated with charging a battery pack. Figure 3 One or more process frames can be executed by a controller (e.g., controller 40). Alternatively or concurrently, Figure 3 One or more process blocks may be executed by another device or a group of devices separate from or including the controller (e.g., another device or components inside or outside the charging unit 14).

[0046] like Figure 3 As shown, process 300 may include detecting that the battery pack is connected to the charging unit (block 305), as described herein. For example, the battery pack may be connected to the charging unit to initiate charging of the battery pack by the charging unit. Process 300 may include identifying whether the charging of the battery pack is the first charging of the battery pack (block 310), as described herein. Based on the identification that the charging is the first charging of the battery pack (block 310—Yes), process 300 may include initiating charging of the battery pack (block 315), as described herein.

[0047] Based on the identification that this charge is not the first charge of the battery pack (box 310—No), process 300 may include obtaining the initial SOC of the battery pack (box 320), as described herein. For example, the initial SOC may be indicated in charging information transmitted by the battery pack's BMS, as described herein. Process 300 may include comparing the initial SOC with a previous SOC of the battery pack (box 325). For example, comparing the initial SOC with a previous SOC may enable the identification of trends in charging behavior associated with the battery pack. Process 300 may include comparing the initial SOC with a charging guideline (box 330), as described herein.

[0048] Process 300 may include identifying whether charging the battery pack will comply with charging guidelines (box 335), as described herein. Based on the identification that the charging complies with the charging guidelines (box 335—Yes), process 300 may include initiating charging of the battery pack (box 315), as described herein. Based on the identification that the charging will not comply with the charging guidelines (box 335—No), process 300 may include outputting a warning for violating the charging guidelines (box 340), as described herein.

[0049] Process 300 may include receiving an input indicating whether charging should be initiated (box 345), as described herein. Based on the input indicating whether charging should be initiated (box 345—Yes), process 300 may include outputting a battery life prediction resulting from charging the battery pack in violation of charging guidelines (box 350), as described herein. Process 300 may include receiving additional input indicating whether charging should be initiated (box 355), as described herein. Based on the additional input indicating whether charging should be initiated (box 355—Yes), process 300 may include initiating charging of the battery pack (box 315), as described herein. In some examples, if authentication input (e.g., password, passcode, physical key, key fob, etc.) is provided when additional input indicates whether charging should be initiated (e.g., simultaneously or sequentially), charging may be initiated (e.g., in violation of charging guidelines). Process 300 may include obtaining the initial SOC of the battery pack (if not already obtained) and the final SOC of the battery pack (e.g., after charging) (box 360), as described herein.

[0050] Based on an input indicating that charging should not be initiated (box 345—No) and / or an additional input indicating that charging should not be initiated (box 355—No), process 300 may include outputs a recommended SOC at which charging is performed, a recommended frequency between charging sessions, and / or a battery life prediction resulting from following one or more of these recommendations (box 365), as described herein. Process 300 may include recording data related to charging (or attempted charging) (box 370), as described herein. Process 300 may include outputs a list indicating previous charging sessions and information on whether they violated charging guidelines (box 375), as described herein.

[0051] although Figure 3 An exemplary block of process 300 is shown, but in some implementations, it is different from... Figure 3 Compared to the boxes depicted, process 300 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes of process 300 may be executed in parallel.

[0052] Figure 4 This is a flowchart of an exemplary process 400 associated with charging a battery pack. Figure 4 One or more process frames can be executed by a controller (e.g., controller 40). Alternatively or concurrently, Figure 4 One or more process blocks may be executed by another device or a group of devices separate from or including the controller (e.g., another device or components inside or outside the charging unit 14).

[0053] like Figure 4As shown, process 400 may include receiving charging information related to the battery pack before initiating charging of the battery pack by the charging unit (block 410). For example, the controller may receive charging information related to the battery pack before initiating charging of the battery pack by the charging unit, as described above. The charging information may indicate the current SoC of the battery pack.

[0054] like Figure 4 As also shown, process 400 may include identifying whether charging the battery pack will conform to the charging guidelines based on a comparison of charging information and charging guidelines (box 420). For example, the controller may identify whether charging the battery pack will conform to the charging guidelines based on a comparison of charging information and charging guidelines, as described above. The charging guidelines may indicate one or more of the minimum SoC used to charge the battery pack, the maximum SoC used to charge the battery pack, or the frequency between charging the battery pack.

[0055] like Figure 4 As also shown, process 400 may include outputting a request for operator input indicating whether to initiate charging of the battery pack in response to the recognition that charging the battery pack would violate charging guidelines (box 430). For example, the controller may output a request for operator input indicating whether to initiate charging of the battery pack in response to the recognition that charging the battery pack would violate charging guidelines, as described above.

[0056] Process 400 may include, in response to an operator input instruction not to initiate charging of the battery pack, outputting a recommendation for the frequency between charging the battery pack's SoC (System-on-a-Chip) or charging the battery pack to be used, and information on the battery pack's battery life prediction generated by charging the battery pack according to said recommendation. Process 400 may also include, in response to an operator input instruction to initiate charging of the battery pack, outputting information on the battery pack's battery life prediction generated by charging the battery pack in violation of charging guidelines. Process 400 may include, in conjunction with the information on the battery pack's battery life prediction generated by charging the battery pack in violation of charging guidelines, outputting an additional request for additional operator input indicating whether to initiate charging of the battery pack.

[0057] like Figure 4 As also shown, process 400 may include initiating charging of the battery pack in response to an operator input instruction to initiate charging (block 440). For example, the controller may initiate charging of the battery pack in response to an operator input instruction to initiate charging, as described above. In some examples, initiating charging of the battery pack may be in response to both operator input and additional operator input instructions to initiate charging.

[0058] although Figure 4 An exemplary block of process 400 is shown, but in some implementations, it is different from... Figure 4 Compared to the boxes depicted, process 400 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes of process 400 may be executed in parallel.

[0059] Industrial applicability

[0060] The charging control system described herein can be used with any charging unit or charger that provides battery charging. For example, the charging control unit can be used with a charging unit that provides charging for the battery pack of a machine. Typically, the charging of the battery pack can be decided by the machine operator. Therefore, the operator may charge the battery pack in a suboptimal manner, such as charging it too frequently, charging it before it is fully depleted, or allowing it to reach an extremely low charge level before charging. Suboptimal charging modes can adversely affect the health of the battery pack, thereby reducing its productivity and lifespan.

[0061] The charging control system described herein can be used to improve the charging patterns of battery packs. Specifically, the charging control system can use charging information associated with the battery pack (e.g., SOC, charging frequency, etc.) to monitor whether the battery pack's charging behavior conforms to charging guidelines (e.g., charging guidelines indicating best practices). In this way, the charging control system can allow charging that conforms to the guidelines but prevent charging that violates them. Therefore, the charging control system can improve the overall health of the battery pack, thereby improving its productivity and lifespan.

Claims

1. A charging control system (50), comprising: Contactor (52), the contactor being configured to control the current flow in the charging unit (14); as well as Controller (40), the controller is configured to: Before starting the charging of the battery pack (20) by the charging unit (14), charging information related to the battery pack (20) is received from the battery management system (38) of the battery pack (20); Based on the comparison between the charging information and the charging guidelines, it is determined whether charging the battery pack (20) will comply with the charging guidelines; In response to the recognition that charging the battery pack (20) would violate the charging guidelines, a request is output for operator input indicating whether to initiate charging of the battery pack (20); as well as In response to the operator input instruction to start charging, charging of the battery pack (20) is initiated.

2. The charging control system (50) according to claim 1, wherein the charging information indicates the state of charge of the battery pack (20).

3. The charging control system (50) according to any one of claims 1-2, wherein the controller (40) is configured to receive the charging information and an identifier of the battery pack (20) for receiving the charging information, and The controller (40) is further configured to: Use the identifier of the battery pack (20) to retrieve historical charging information related to the battery pack (20); and Output information indicating whether the historical charging information conforms to the charging guidelines.

4. The charging control system (50) according to any one of claims 1-3, wherein the controller (40) is further configured to: In response to the operator input instruction to initiate charging of the battery pack (20), an output is provided indicating information on the predicted battery life of the battery pack (20) resulting from charging the battery pack (20) in violation of the charging guidelines; and The output includes an additional request for operator input indicating whether to initiate charging of the battery pack (20). The controller (40) is configured to initiate charging of the battery pack (20) in response to the operator input and the additional operator input indicating to initiate charging.

5. The charging control system (50) according to any one of claims 1-4, wherein the controller (40) is configured to initiate charging of the battery pack (20) as follows: The contactor (52) is closed.

6. The charging control system (50) according to any one of claims 1-5, wherein the controller (40) is further configured to: In response to the operator input instruction not to initiate charging of the battery pack (20), charging of the battery pack (20) is restricted.

7. The charging control system (50) according to any one of claims 1-6, wherein the charging unit (14) includes a display (42).

8. A method comprising: The controller (40) receives charging information related to the battery pack (20) before initiating charging of the battery pack (20) by the charging unit (14); The controller (40) determines whether charging the battery pack (20) will comply with the charging guidelines based on a comparison of the charging information and the charging guidelines. The controller (40) outputs a request to the operator input indicating whether to initiate charging of the battery pack (20) in response to the recognition that charging the battery pack (20) would violate the charging guidelines; as well as The controller (40) initiates charging of the battery pack (20) in response to the operator input instruction to start charging.

9. The method of claim 8, wherein the charging guide indicates one or more of the following: The minimum state of charge for charging the battery pack (20), The maximum state of charge used to charge the battery pack (20), or The frequency between charging of the battery pack (20).

10. The method according to any one of claims 8-9, further comprising: In response to the operator input instruction not to initiate charging of the battery pack (20), the following information is output: The recommended frequency between the state of charge of the battery pack (20) at which charging of the battery pack (20) is performed or between charging of the battery pack (20) to be used, and The battery life prediction of the battery pack (20) is generated by charging the battery pack (20) according to the recommendation.

Images