Embodiments described herein provide systems and methods for providing notifications related to battery pack charging status.
Charging systems described herein include a battery charger and an external device. The battery charger includes a housing, a battery pack interface, a wireless communication controller, and a charger controller. The battery pack interface is configured to receive a plurality of power tool battery packs. The wireless communication controller is configured to communicate with the external device. The charger controller is connected to the battery pack interface and the wireless communication controller. The charger controller is configured to receive status information associated with each of the plurality of power tool battery packs and transmit, with the wireless communication controller, the status information to an external device. The external device includes a display and an external device controller connected to the display. The external device controller is configured to receive the status information from the charger controller and control the display to display the status information via a user interface.
Methods for notifying battery pack status described herein include receiving, with a battery pack charger, status information associated with a plurality of power tool battery packs connected to the battery pack charger, wherein the battery pack charger includes a housing, transmitting, with a wireless communication controller, the status information to an external device, receiving, with the external device, the status information from the charger controller, and controlling, with the external device, a display to display the status information via a user interface.
Battery chargers described herein include a housing, a display, a battery pack interface, and a charger controller. The battery pack interface is configured to receive a power tool battery pack. The charger controller is connected to the battery pack interface and the display. The charger controller is configured to receive status information associated with the power tool battery pack and provide, one the display, a plurality of indicators indicative of the status information.
Before any embodiments are explained in detail, it is to be understood that the embodiments are not limited in its application to the details of the configuration and arrangement of components set forth in the following description or illustrated in the accompanying drawings. The embodiments are capable of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having” and variations thereof are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Unless specified or limited otherwise, the terms “mounted,” “connected,” “supported,” and “coupled” and variations thereof are used broadly and encompass both direct and indirect mountings, connections, supports, and couplings.
In addition, it should be understood that embodiments may include hardware, software, and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware. However, one of ordinary skill in the art, and based on a reading of this detailed description, would recognize that, in at least one embodiments, the electronic-based aspects may be implemented in software (e.g., stored on non-transitory computer-readable medium) executable by one or more processing units, such as a microprocessor and/or application specific integrated circuits (“ASICs”). As such, it should be noted that a plurality of hardware and software-based devices, as well as a plurality of different structural components, may be utilized to implement the embodiments. For example, “servers” and “computing devices” described in the specification can include one or more processing units, one or more computer-readable medium modules, one or more input/output interfaces, and various connections (e.g., a system bus) connecting the components.
Other features and aspects will become apparent by consideration of the following detailed description and accompanying drawings.
At least one of the side surfaces includes at least one port 320. The illustrated ports 320 are AC pass-through ports. The AC pass-through ports 320 are connectable to tools and/or equipment including an AC connector. In the illustrated embodiments, the battery pack charger 300 includes two AC pass-through ports 320. However, in alternative embodiments, the battery pack charger 300 may include fewer or additional AC pass-through ports 320. The side surface(s) and top surface additionally include an aperture 325 extending therethrough. The aperture 325 is shaped and sized to receive a cord. Specifically, the aperture 325 on the side surface is positioned at a height which allows the exiting cord to clear a bottom lip of the mobile work cart. This configuration reduces potential safety hazards for a user (e.g., tripping). The bottom surface of the main body includes several feet (not shown) mounted to the surface. The feet provide clearance between the bottom surface and the bottom of the cart.
With continued reference to
Alternatively, when a user opens the doors 410, the tabs 418 disengage the charging bays 420, thereby causing the charging bays 420 to pivot downward to an angled position. When in the angled position, battery packs positioned on the charging bays 420 are prevented from slipping off of the charging bays 420. The pivoting charging bays 420 allow for compact storage (e.g., when the doors 410 are closed and the charging bays 420 are in the stored position), and allow for easy access for the user (e.g., when the doors 410 are open and the charging bays 420 are in the angled position). In the illustrated embodiments, the storage chamber 415 includes four charging bays 420. However, in other embodiments, the storage chamber 415 may include fewer or additional charging bays 420.
An upper surface of the working surface includes charging bays 530 configured to receive various battery packs. Specifically, the working surface shown in
Distal ends of the base and the working surface include legs 535 extending therefrom and configured to support the charging module 505 on the ground. Specifically, when the charging module 505 is removed from the mobile work cart 510, the user may pivot the working surface away from the base 515 and position the legs 535 on the ground to support the charging module 505 in an upright, self-supporting position.
The controller 600 includes a plurality of electrical and electronic components that provide power, operational control, and protection to the components and modules within the controller 600 and/or battery pack charger 100-500. For example, the controller 600 includes, among other things, a processing unit 640 (e.g., a microprocessor, a microcontroller, an electronic controller, an electronic processor, or another suitable programmable device), a memory 645, input units 650, and output units 655. The processing unit 640 includes, among other things, a control unit 660, an arithmetic logic unit (“ALU”) 665, and a plurality of registers 670 (shown as a group of registers in
The memory 645 is a non-transitory computer readable medium and includes, for example, a program storage area and a data storage area. The program storage area and the data storage area can include combinations of different types of memory, such as a ROM, a RAM (e.g., DRAM, SDRAM, etc.), EEPROM, flash memory, a hard disk, an SD card, or other suitable magnetic, optical, physical, or electronic memory devices. The processing unit 640 is connected to the memory 645 and executes software instructions that are capable of being stored in a RAM of the memory 645 (e.g., during execution), a ROM of the memory 645 (e.g., on a generally permanent basis), or another non-transitory computer readable medium such as another memory or a disc. Software included in the implementation of the battery pack charger 100-500 can be stored in the memory 645 of the controller 600. The software includes, for example, firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The controller 600 is configured to retrieve from the memory 645 and execute, among other things, instructions related to the control processes and methods described herein. In other constructions, the controller 600 includes additional, fewer, or different components.
The one or more sensors 615 are configured to sense operational parameters of the battery pack 685. For example, the one or more sensors 615 may include voltage sensors configured to sense a charge voltage of the battery pack 685. The one or more sensors 615 may include current sensors configured to sense a charging current provided to the battery pack 685. The one or more sensors 615 may include temperature sensors configured to sense a temperature of the battery pack 685. In embodiments where multiple battery packs 685 are connected to the battery pack charger 100, 200, 300, 400, 500, the controller 600 may receive information associated with operational parameters of each battery pack 685 connected to the battery pack charger 100, 200, 300, 400, 500 via the battery pack interface 690.
The battery pack interface 690 includes a combination of mechanical components (e.g., rails, grooves, latches, etc.) and electrical components (e.g., one or more terminals) configured to and operable for interfacing (e.g., mechanically, electrically, and communicatively connecting) the battery pack charger 100-500 with a battery pack 685. The battery pack interface 690 may be, for example, a combination of an electrical battery pack interface and a physical battery pack interface. The battery pack interface 690 is also configured to communicatively connect to the controller 600 via a communications line 680. For example, the battery pack 685 may communicate charging parameters and operational parameters to the controller 600 via the communications line 680.
In the illustrated embodiment, the wireless communication controller 630 is a Bluetooth® controller. The Bluetooth® controller communicates with the external device 800 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 800 and the battery pack charger 100-500 are within a communication range (i.e., in proximity) of each other while they exchange data. In other embodiments, the wireless communication controller 630 communicates using other protocols (e.g., Wi-Fi, ZigBee, a proprietary protocol, etc.) over different types of wireless networks. For example, the wireless communication controller 630 may be configured to communicate via Wi-Fi through a wide area network such as the Internet or a local area network, or to communicate through a piconet (e.g., using infrared or NFC communications).
In some embodiments, the network is a cellular network, such as, for example, a Global System for Mobile Communications (“GSM”) network, a General Packet Radio Service (“GPRS”) network, a Code Division Multiple Access (“CDMA”) network, an Evolution-Data Optimized (“EV-DO”) network, an Enhanced Data Rates for GSM Evolution (“EDGE”) network, a 3GSM network, 4GSM network, a 4G LTE network, 5G New Radio, a Digital AMPS (“IS-136/TDMA”) network, or an Integrated Digital Enhanced Network (“iDEN”) network, etc.
The wireless communication controller 630 is configured to receive data from the controller 600 and relay the information to the external device 800 via the antenna and transceiver 710. In a similar manner, the wireless communication controller 630 is configured to receive information (e.g., configuration and programming information) from the external device 800 via the antenna and transceiver 710 and relay the information to the controller 600.
The RTC 715 increments and keeps time independently of the other components. Having the RTC 715 as an independently powered clock (e.g., by coin cell battery) enables time stamping of operational data (stored in memory 705 for later export).
Using the external device 800, a user can access operational parameters of the battery pack charger 100-500 and battery packs 685 that are coupled to the battery pack charger 100-500. The operational parameters may include whether the battery pack 685 is being charged, a tool connected to the battery pack 685, a charge status (e.g., a charge level) of the battery pack 685, a number of tool operations remaining for a tool connected to the battery pack 685, a temperature of the battery pack 685, a temperature of the charger 100-500, and the like. The external device 800 can also transmit data to the battery pack charger 100-500 for charger configuration, firmware updates, or to send commands. The external device 800 also allows a user to set operational parameters, safety parameters, select other operational modes, and the like for the battery pack charger 100-500.
The external device 800 is, for example, a smart phone (as illustrated), a laptop computer, a tablet computer, a personal digital assistant (PDA), a smart watch, a buzzer, or another electronic device capable of communication wirelessly with the battery pack charger 100-500 and providing a user interface. The external device 800 includes a controller (similar to controller 600 and including a processing device and a memory) and provides the user interface and allows a user to access and interact with the battery pack charger 100-500. The external device 800 can receive user inputs to determine operational parameters, enable or disable features, and the like. The user interface of the external device 800 provides an easy-to-use interface for the user to control and customize operation of the battery pack charger 100-500. The external device 800, therefore, grants the user access to the operational data of the battery pack charger 100-500, and provides a user interface such that the user can interact with the controller 600 of the battery pack charger 100-500.
In addition, as shown in
In some embodiments, the charger 100-500 includes a display or screen integrated on its housing.
The display 900 may provide diagnostic information related to each battery pack 685 coupled to the charger 100-500. For example, each battery pack 685 may have a plurality of fault indicators (e.g., the fourth graphical indicator 920), such as temperature indicators, overcharge indicators, and the like. The display 900 may further provide a detailed fault message 930 describing the fault in more detail than provided by the fourth graphical indicator 920. The display 900 may also include a number of charge cycles, charger power consumption, an average power use, a number of previous faults, and other diagnostic information for each battery pack 685 and the charger 100-500.
In some embodiments, information regarding the battery pack(s) 685 and the charger 100-500 is provided via a mobile application of the external device 800. For example,
The first user interface 1005 provides a plurality of individual battery packs 685 that are registered with the mobile application. The first user interface 1005 may also display, for each battery pack 685, a battery pack type, a name of the battery pack 685, and an identification number associated with each battery pack 685. In some embodiments, the first user interface 1005 also provides similar information for any charger 100-500 that is registered with the mobile application.
Selection of one of the battery packs 685 displayed on the first user interface 1005 may result in a transition to the third user interface 1015. The third user interface 1015 provides the selected battery pack 685, a charge status (e.g., a charge level) of the selected battery pack 685 (provided by charge indicator 1016), and a remaining period of time until the selected battery pack 685 is completely charged (provided by time indicator 1017). In some embodiments, the battery pack 685 may be coupled to a power tool. Accordingly, the third user interface 1015 may also provide information related to the connected power tool (provided by tool indicator 1019). The third user interface 1015 may also show a remaining number of tool operations until the battery pack 685 is completely discharged (provided by capacity indicator 1018). In such embodiments, the battery pack 685 includes a wireless communication controller 630 for communicating with the external device 800 as previously described. In some embodiments, a user may select a specific power tool registered with the mobile application to observe a remaining number of tool operations for the selected power tool.
Selection of a charger 100-500 displayed on the first user interface 1005 may result in a transition to the second user interface 1010. The second user interface 1010 provides information related to the selected charger 100-500 and any battery packs 685 coupled to the selected charger 100-500. For example, in the illustrated example, the second user interface 1010 provides a first battery pack 1011 and a second battery pack 1012 coupled to the charger 100. The second user interface 1010 also provides the charge status and remaining charge time for each battery pack 685 coupled to the charger 100-500. In the illustrated example of the second user interface 1010, a first charge indicator 1013 provides the charge status and remaining charge time for the first battery pack 1011, and a second charge indicator 1014 provides the charge status and remaining charge time for the second battery pack 1012.
In some embodiments, a user of the external device 800 may be able to customize notifications and operations of the charger 100-500 and/or the battery pack 685 using the mobile application. For example, fourth user interface 1020 provides a settings window in which notifications may be toggled (e.g., turned on or off) and customized via a toggle input graphic. For example, using the fourth user interface 1020, a user may toggle all notifications using a first toggle input graphic 1021. A user may toggle, using the fourth user interface 1020, receiving notifications when a battery pack 685 is charged using a second toggle input graphic 1022. In some embodiments, a user may toggle a setting to receive notifications when a battery pack 685 is at 50% charge instead of or in addition to receiving a notification when the battery pack 685 is fully charged. Additionally, using the fourth user interface 1020, users may toggle temperature notifications and fault notifications using a third toggle input graphic 1023.
At block 1115, the external device 800 receives the status information from the controller 600. At block 1120, the external device 800 controls a display to display the status information. For example, the external device 800 implements a mobile application to provide the first user interface 1005, the second user interface 1010, the third user interface 1015, or the fourth user interface 1020, as previously described.
Thus, embodiments provided herein describe, among other things, systems and methods for providing notifications regarding battery pack charging status.
This application claims the benefit of U.S. Provisional Patent Application No. 63/190,401, filed May 19, 2021, the entire content of which is hereby incorporated by reference.
Number | Date | Country | |
---|---|---|---|
63190401 | May 2021 | US |