Battery management system for a battery powered device

Abstract

A battery pack includes a housing, a plurality of rechargeable battery cells, a connection interface, a near field communication (NFC) reader, a battery management system, and a communication gateway. The connection interface in communication includes a plurality of data pins, a positive terminal, and a negative terminal. The battery management system is in communication with the NFC reader and is configured to receive information including an NFC tag identification from the NFC reader, then retrieve stored parameters corresponding to the NFC tag identification, and configure at least one of the plurality of data pins based on the stored parameters corresponding to the NFC tag identification.

Description

[0001] Cross-reference to related applications This application claims priority to U.S. Provisional Patent Application No. 62 / 960,549, filed January 13, 2020, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0002] This invention generally relates to the field of indoor and outdoor power equipment, and more specifically, to the field of battery-powered indoor and outdoor power equipment. Summary of the Invention

[0003] According to one exemplary embodiment, a battery pack is disclosed. The battery pack includes a housing, a plurality of rechargeable battery cells located within the housing, a connection interface, a near-field communication (NFC) reader, a battery management system, and a communication gateway. The connection interface communicates with the plurality of rechargeable battery cells and includes a plurality of data pins, a positive terminal, and a negative terminal. The NFC reader is located within the housing. The battery management system communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader. The battery management system is further configured to then retrieve storage parameters corresponding to the NFC tag identification (e.g., from local or remote memory), and then configure at least one of the plurality of data pins based on the storage parameters corresponding to the NFC tag identification. The communication gateway communicates with the battery management system and is configured to receive and transmit information via a communication protocol with a frequency exceeding 14 MHz. The battery management system is configured to monitor operating parameters of the rechargeable battery cells and data received via the plurality of data pins, and to transmit the operating parameters of the rechargeable battery cells and data received via the plurality of data pins via the communication protocol.

[0004] According to another exemplary embodiment, a battery pack is disclosed. The battery pack includes a housing, a plurality of rechargeable battery cells located within the housing, a connection interface, a near-field communication (NFC) reader, a battery management system, and a communication gateway. The connection interface communicates with the plurality of rechargeable battery cells. The connection interface includes an electrical connection having a positive terminal, a negative terminal, and a plurality of data pins. The NFC reader is located within the housing. The battery management system communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader. The battery management system is further configured to retrieve stored parameters corresponding to the NFC tag identification and configure at least one of the plurality of data pins based on the stored parameters corresponding to the NFC tag identification. The communication is with the battery management system and is configured to transmit and receive information via Bluetooth. The battery management system is configured to monitor operating parameters of the rechargeable battery cells and data received via the plurality of data pins, including data related to the operating performance of a device connected to the battery pack. The battery management system is further configured to use the communication gateway to transmit the operating parameters of the rechargeable battery cells and data received via the plurality of data pins via Bluetooth.

[0005] According to another exemplary embodiment, a battery pack is disclosed. The battery pack includes a housing, a plurality of rechargeable battery cells located within the housing, a connection interface, a near-field communication (NFC) reader, a battery management system, and a communication gateway. The connection interface communicates with the plurality of rechargeable battery cells. The connection interface includes an electrical connection having a positive terminal, a negative terminal, and a plurality of data pins. The NFC reader is located within the housing. The battery management system communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader. The battery management system is further configured to retrieve stored parameters corresponding to the NFC tag identification, and then at least one of the plurality of data pins can be configured based on the stored parameters corresponding to the NFC tag identification. The communication gateway communicates with the battery management system and is configured to transmit and receive information via a communication protocol with a frequency exceeding 14 MHz. The battery management system is configured to monitor operating parameters of the rechargeable battery cells and data received via the plurality of data pins, and to transmit the operating parameters of the rechargeable battery cells and data received via the plurality of data pins via the communication protocol. At least one of the plurality of data pins can be configured to communicate between a controller area network (CAN) bus and the battery management system. Attached Figure Description

[0006] The invention will be more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, wherein: Figure 1A This is a schematic diagram illustrating the communication between the battery management system and its components. Figure 1BIt is a perspective view of a battery system used in conjunction with the user interface of a management system on a power equipment and mobile device; Figure 1C It has a Near Field Communication (NFC) reader and tag. Figure 1B A perspective view of the battery pack and device interfaces; Figure 1D It can be merged. Figure 1C A perspective view of the public connector of the battery pack; Figure 1E yes Figure 1D A top view of the public connection interface; Figure 1F It can be merged. Figure 1C In the battery pack or Figure 1B A perspective view of the female connection interface in the power equipment; Figure 1G yes Figure 1F Top view of the female connection interface; Figure 2 This is the front view of the user interface for adding the battery system to the management system; Figure 3 This is a front view of the user interface for another method of adding a battery system to the management system; Figure 4 It is the front view of the user interface that displays a list of multiple battery systems monitored by the management system; Figure 5 It is a front view depicting the user interface of various projects in the management system; Figure 6 This is the front view of the user interface for creating a new product in the management system. Figure 7 It is the front view of the user interface on the management system used to configure data pins for new products; Figure 8 This is the front view of the user interface on the management system used to select the pin function type for the data pins of new products; Figure 9 It is a front view of the user interface on the system that manages the options for the programmable data pin input pin functions; Figure 10 This is the front view of the user interface in the management system used to program NFC tags after selecting the pin function for each data pin; Figure 11 This is a front view of the user interface depicting the instructions on the management system for writing data pin functionality to NFC tags; Figure 12 It is the front view of the user interface on the management system that displays product information and the product's activity history; Figure 13It is the front view of the user interface that displays information about the power equipment being monitored on the management system; Figure 14 It is an enlarged view of a part of the user interface depicting information about the battery connected to a power device on the management system; Figure 15 It is a front view of another user interface that displays information about the power equipment being monitored on the management system; Figure 16 It is a magnified view of part of the user interface on the management system used to edit the schedule for operating power equipment; and Figure 17 It is used with a set of devices. Figures 1A to 1G Front view of the battery management system. Detailed Implementation

[0007] Before turning to the accompanying drawings, which detail exemplary embodiments, it should be understood that this application is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology is for descriptive purposes only and should not be considered limiting.

[0008] Referring generally to the accompanying drawings, a battery management system for battery packs is disclosed. The battery management system can monitor and track information about removable and replaceable battery packs and can be used to power various types of indoor and outdoor power equipment, as well as portable site equipment and light electric vehicles and passenger cars. Outdoor power equipment includes lawnmowers, ride-on tractors, snowplows, pressure washers, tillers, log splitters, zero-turn radius mowers, walk-behind lawnmowers, ride-on lawnmowers, upright lawnmowers, road surface preparation devices, industrial vehicles (e.g., forklifts), multi-purpose vehicles, commercial turf equipment (e.g., blowers), vacuum cleaners, chip loaders, cross-seeders, power rakes, ventilation systems, sod cutters, brush mowers, portable generators, etc. Indoor power equipment includes floor sanders, floor dampers and polishers, vacuum cleaners, etc. Portable site equipment includes portable lighthouses, mobile industrial heaters, and portable light stands.

[0009] A battery management system can be incorporated into a general-purpose (e.g., general-purpose, multi-purpose) battery pack with one or more data pins configured to communicate with indoor and outdoor power devices, site equipment, etc. The battery management system communicates with one or more data pins and can configure these pins based on the detected type of device requesting power. Before receiving a power request from a power device, the battery pack may not have predefined functions or characteristics mapped to each data pin. However, after reading an NFC tag from a solution interface (e.g., the interface of a power device) and identifying the type of device requesting power (e.g., from an NFC tag reader), the battery management system can allow for specific configuration of the general-purpose battery pack to function fully and uniquely with the connected product (e.g., a portable lighthouse, blower, etc.). The battery management system can access local or remote memory to retrieve operating parameters or output characteristics optimized for the specific type of identified power device associated with the NFC tag. With this information, the battery management system can configure (or reconfigure) the data pins on the battery pack based on these preferred parameters. Advantageously, this pairing between the general-purpose battery pack and the product can be accomplished without requiring firmware updates to the battery pack. Typically, original equipment manufacturers (OEMs) need to choose between using "non-smart" generic battery packs or fully customized solutions. Each of these trade-offs severely limits the opportunities available to OEMs. However, by using the battery management system described in this article, OEMs can still advantageously have smart, customizable battery packs without needing to update firmware to configure unique features for battery packs with connected products.

[0010] refer to Figure 1AThe diagram illustrates a battery pack 100 in a battery management system 101 according to an exemplary embodiment. The battery pack 100 can be used to power various products, such as a power device 105. In some embodiments, the battery pack 100 is used in design testing environments (e.g., using development kits). The battery pack 100 is communicatively connected to a mobile device 110 (e.g., a tablet computer) to provide battery and tool information via a communication network 112. For example, the mobile device 110 can be a laptop, desktop computer, smartphone, tablet, etc. When a user operates the power device 105, information is transmitted to the mobile device 110 to be presented to the user of the battery management system 101 (e.g., an OEM). Therefore, the performance of the battery pack 100 and the device 105 can be easily transmitted to the user, allowing the user to design, test, track, and improve products based on a continuous monitoring system that includes both the battery pack 100 and the device 105. Thus, the OEM can understand how the system is operating more quickly, enabling more efficient updates or changes. Therefore, using the battery management system 101 makes it easier to design power products for long-term solutions because real-time feedback on battery and device performance can be received. Each battery pack 100 in the battery management system 101 includes a unique identifier (e.g., a serial number) for tracking the battery management system 100 (e.g., tracking a group of devices 105 connected to the battery pack 100).

[0011] In some implementations, the battery pack 100 communicates via communication protocol 116 (e.g., NFC communication) through an NFC reader of the battery pack 100. Figure 1C 106 as shown) and the device interface (e.g., device interface 132) installed on device 105. Figure 1B NFC tags in )) (such as Figure 1CAs shown in 134, the battery pack 100 communicates with device 105. The battery pack 100 then relays information related to device 105 to various gateways, such as dedicated gateway 126, charger gateway 124, and / or mobile gateway 128. The battery pack 100 can communicate with the gateway via communication protocol 118. The communication protocol can operate at frequencies higher than NFC (e.g., higher than 13.56 MHz). In some embodiments, communication protocol 118 is the Bluetooth protocol. The gateway can transmit data to communication network 112 and fleet management system 114 via communication protocol 120 (which may include Ethernet, Wi-Fi, or cellular protocols). In other embodiments, the battery pack 100 can communicate directly with the communication network 112 of the battery management system 101 (e.g., cloud, fleet management system 114) using a gateway installed in the battery pack 100 (e.g., shown by dashed line 130). For example, the network interface 104 of the battery pack 100 may include a gateway for sending and receiving cellular transmissions. The communication network 112 can then transmit information to the mobile device 110 via communication protocol 122 (which may also include Ethernet, Wi-Fi, or cellular protocols). In some implementations, the fleet management system 114 administrators use the mobile device 110 to monitor and track the use of the device 105.

[0012] Battery pack 100 includes management circuitry 102, which includes diagnostic circuitry and a communication interface. Management circuitry 102 is embedded within the battery pack of battery pack 100. In some embodiments, management circuitry 102 is configured to monitor battery status, including current, voltage, temperature, etc., and to provide charge and discharge protection for battery pack 100, such as preventing fast charging of the battery when it may affect the health of battery pack 100. For example, management circuitry 102 prevents fast charging when the health of battery pack 100 or when the charge level of battery pack 100 is below a certain threshold. Management circuitry 102 is further configured to extend the lifespan of battery pack 100 and provide reliability by monitoring and controlling various battery conditions. Management circuitry 102 may include one or more circuits configured to monitor the status of battery pack 100 or other aspects of the device 105 used with battery pack 100. Management circuitry 102 may be further configured to monitor battery status to predict the number of times the battery can be started.

[0013] The management circuitry 102, which can be considered part of the broader battery management system (BMS) within the battery pack 100, can be further configured to monitor other characteristics of the connected electrical equipment 105 by communicating with sensors and monitoring devices such as level sensors, temperature sensors, pressure sensors, timers, blade speed sensors, etc. The management circuitry 102 can output data related to the information received from the sensors and monitoring devices to a display, such as a user interface integrated into the battery pack 100, or a user interface or dashboard (e.g., dashboard 115) on the mobile device 110. Figure 17 The display shows the data on the device and battery pack 100. Therefore, the display can transmit various operating data related to the device and battery pack 100 to the OEM. For example, in addition to operating information received from the connected power unit 105, the management circuit 102 can output information such as operating time, battery charge, or battery temperature to the display. Additionally, the management circuit 102 can monitor the temperature of the battery pack 100 via input from a temperature sensor. If the battery temperature is too low for normal battery use, temperature monitoring can be used to warn the operator (e.g., via the user interface of the mobile device 110).

[0014] In some implementations, battery pack 100 includes a network interface 104. In some arrangements, network interface 104 includes the hardware and logic necessary for communication via multiple data communication channels. For example, network interface 104 may include a Wi-Fi interface, a cellular modem, a Bluetooth transceiver, a Bluetooth beacon, an RFID transceiver, an NFC transceiver, an Ethernet transceiver, or a combination thereof. Network interface 104 facilitates data communication with battery pack 100 (and therefore with device 105 using battery pack 100). Battery pack 100 can wirelessly communicate with multiple other devices (including another battery pack 100) in a mesh network or Internet of Things (IoT) system. In this way, battery pack 100 can transmit and receive status and usage information, as well as configuration data. For example, battery pack 100 can receive software updates over a network via network interface 104. In some implementations, the external device with which battery pack 100 communicates is a charging station, via a wireless gateway of the charging station. According to some implementations, battery pack 100 can communicate with the charging station information about the status of battery pack 100 (e.g., current charge level, fully charged, ready for use, held back, etc.). In other embodiments, the battery pack 100 can communicate with the wireless gateway 124 in the portable charger. In other embodiments, the network interface 104 is a communication interface that allows the battery pack 100 to serially communicate with external devices via SPI (Serial Peripheral Interface), I2C (Internal Integrated Circuit), USB (Universal Serial Bus), or any other serial communication protocol. In some embodiments, the network interface 104 is a communication interface that includes an IoT gateway.

[0015] refer to Figure 1A-1G The battery pack 100 also includes an NFC reader 106 (e.g., embedded in the core or housing of the battery pack 100) configured to communicate with an NFC tag 134 (e.g., an electrical connector with an NFC sticker) on the interface 132 of the device 105. In some embodiments, the NFC reader 106 is integrated with a network interface 104. Communication between the NFC tag 134 on the device interface 132 and the NFC reader 106 allows the battery pack 100 to determine the type of device / tool ​​that powers its operation. Therefore, the battery pack 100 is configured to wirelessly identify tools or devices via the NFC tag 134 on the device interface 132. Once battery pack 100 is inserted into device interface 132 to connect to device 105 (e.g., using male and female connectors 219, 183), battery pack 100 (e.g., via NFC reader 106) reads information from NFC tag 134 on device interface 132 (which may include device serial number, type, battery slot location, and / or logic for how the power device turns battery pack 100 on and off) and associates battery pack 100 usage data with that specific tool or power device 105. Battery pack 100 can also reconfigure data pins for tool-specific applications. If the tool has multiple battery slots (e.g., a device that consumes more power during operation can be connected to more than one battery pack 100), NFC tag 134 can also be used to identify the slot into which battery pack 100 is inserted. Battery pack 100 can also be configured to read fault codes using mobile device 110. Mobile device 110 can receive fault codes via NFC communication. In this way, battery pack 100 can still communicate with mobile device 110 even if communication network 112 is turned off. Furthermore, Controller Area Network (CAN) type communication is not required for communication with the battery pack 100. In some embodiments, the battery pack 100 uses Radio Frequency Identification (RFID) to identify tools or equipment. In a further embodiment, data pins are configured such that inputs on the power equipment (e.g., light switches, power commands, ignition switches, etc.) can communicate via the data pins to request and / or activate the battery pack 100 to provide power. In some embodiments, the battery pack 100 can be used as a controller to provide different functions to the power equipment 105. For example, a battery management system on the battery pack 100 can provide pulse width modulation (PWM) dimming, for example, to a portable lighthouse. Therefore, the device 105 can be manufactured with simpler electronics, which can further reduce the cost of producing the power equipment.

[0016] In some embodiments, battery pack 100 does not include cellular communication capabilities (e.g., a base station), thus requiring a separate gateway (e.g., a dedicated gateway 126, another battery pack 100 with cellular communication capabilities, or a mobile gateway 128) to communicate via communication network 112. In some embodiments, battery pack 100 includes cellular communication capabilities and acts as a gateway (e.g., an IoT gateway). Therefore, communication network 112 can facilitate data communication between battery pack 100 and mobile device 110 (e.g., an endpoint device) in various combinations. In some arrangements, communication network 112 includes a cellular transceiver. In another arrangement, communication network 112 includes the Internet. In yet another arrangement, communication network 112 includes a local area network (LAN) or a wide area network (WAN). Communication network 112 can be facilitated by short-range and / or long-range communication technologies including Bluetooth transceivers, Bluetooth beacons, RFID transceivers, NFC transceivers, Wi-Fi transceivers, cellular transceivers, wired network connections, etc. Therefore, in one embodiment, communication between the mobile device 110 and the battery pack 100 can be facilitated by a cloud-based system and connected to the cloud-based system via RFID and Wi-Fi connectivity on the battery pack 100. In another embodiment, communication can be facilitated by a cloud-based system and connected to the cloud-based system solely via Wi-Fi. In yet another embodiment, communication can be facilitated by a cloud-based system and connected to the cloud-based system via a cellular transceiver. In still another embodiment, communication can be facilitated by a cloud-based system and connected to the cloud-based system via Bluetooth and a cellular transceiver. In all such embodiments, the cloud-based system can be accessed by third parties, such as consumers and / or rental companies.

[0017] refer to Figure 1BAccording to one exemplary embodiment, a perspective view of a battery pack 100 used with a power device 105 and a battery management system 101 is shown. The battery pack 100 is removable and rechargeable. The battery pack 100 is configured to connect to or insert (e.g., lower, place, or lower down) into a receiver integrated with device 105 and / or a charging station via a device interface 132 removably mounted on a device. The battery pack 100 can be mounted vertically, horizontally, and / or at any angle into a device. The battery pack 100 is a lithium-ion battery. However, other battery types are contemplated, such as nickel-cadmium (NiCD), lead-acid, nickel metal hydride (NiMH), lithium polymer, etc. The battery pack 100 produces a voltage of approximately 48 volts (V) and a capacity of 1400 watt-hours (Wh). In other embodiments, the battery pack 100 may be configured to produce higher or lower voltages. Other sizes of battery packs are also contemplated. In some embodiments, battery pack 100 is capable of providing approximately 2,000 charge / discharge cycles, approximately 5,000 W of continuous power (13 amps (A) per cell), 9,000 W of peak power (25 A per cell), and 14,000 W of instantaneous power (40 A per cell). In other embodiments, battery pack 100 may have more or less continuous, instantaneous, and peak power. The total weight of battery pack 100 is less than approximately 25 pounds, thereby allowing for easy carrying, removal, and replacement. Battery pack 100 is also hot-swappable, meaning that a depleted battery pack 100 can be replaced with a new battery pack 100 without completely disconnecting the connected device. This eliminates downtime between battery pack 100 replacements. Other structural aspects of battery pack 100 are shown and described in co-owned PCT / US202 / 043981, filed July 29, 2020, entitled “Battery System and Related Management System,” the contents of which are incorporated herein by reference in their entirety.

[0018] Battery pack 100 can be removed from a piece of equipment 105 by the operator without the use of tools and recharged using a charging station. This allows the operator to power the equipment using a second rechargeable battery with sufficient charge, while simultaneously allowing the first battery to be recharged. Additionally, battery pack 100 can be used on various types of equipment 105, including indoor, outdoor, and portable site equipment. Due to its compatibility with various equipment, battery pack 100 can also be used as part of a rental system, where rental companies that traditionally rent equipment can also rent battery packs 100 for use on these devices. Operators can rent battery packs 100 for use on various types of equipment or vehicles that they may own and / or rent, and then return the battery packs 100 for use by other operators as needed. Furthermore, multiple battery packs 100 can be combined to provide sufficient power to equipment that may require more than a single battery pack.

[0019] Battery pack 100 is configured to be selectively electrically connected to a device 105 and / or a charging station (e.g., Figure 1A The device 105 or charging station 124 shown in the diagram includes a receiver with electrical terminals that are selectively electrically connected to the battery pack 100 without the use of tools. For example, an operator can insert (and electrically connect) the battery pack 100 to a device 105 and remove (and electrically disconnect) the battery pack from the device (e.g., from the terminals of the receiver) without the need for tools. The device interface 132 and / or the receiver may include a planar mounting surface having at least one hole for receiving a threaded fastener, and the device interface 132 and / or the receiver may be connected to the device via a threaded fastener.

[0020] The battery pack 100 may also include a user interface configured to display various states and fault indications of the battery pack 100. The user interface may use light-emitting diodes (LEDs), liquid crystal displays, or the like to display various colors or other indications. The LED display of the battery pack 100 may provide battery charging status and may flash or display battery fault codes. The LCD display may provide additional information about the battery pack 100, including status, tool-specific data, usage data, faults, custom settings, etc. For example, battery indications may include, but are not limited to, charging status, faults, battery health status, battery life, capacity, lease time, battery mode, unique battery identifier, link system, etc. The user interface may be a customized version of a user interface tailored to a specific tool, purpose, or operator.

[0021] Now for reference Figure 1C-1G The image shows a perspective view of a battery pack 100 and a device interface 132 according to an exemplary embodiment. The device interface 132 includes two vertical walls and a receptacle between them. The battery pack 100 is configured to slide into the receptacle and lock into place on the device interface 132. The device interface 132 includes a male connector (e.g., ...). Figure 1D and 1E The male connector 219 shown is configured to connect to the port of the battery pack 100 (e.g., in the mounting position of the battery pack 100 on the device interface 132) at the mounting location of the battery pack 100. Figure 1F and 1G The female connector 183 shown mates with the battery pack 100. The battery pack 100 slides downwards into the device interface 132 until the male connector and port are connected to the mating portion of the battery pack 100 and the horizontal member on the device interface 132 connects to the slot on the battery pack 100. (As shown) Figure 1BAs shown, device interface 132 is mounted to a device 105, and battery pack 100 is detachably inserted into device interface 132 to connect to and power device 105. Battery pack 100 includes an NFC reader 106 embedded within a housing of battery pack 100. In some embodiments, NFC reader 106 is located near a mating portion of battery pack 100, where battery pack 100 connects to a male connector of device interface 132. Figure 1C A device interface 132 is shown, with an embedded NFC tag 134 near a mating portion of the device interface 132. In some embodiments, the NFC tag 134 is a sticker placed in or on the male connector portion of the device interface 132, near the location where the battery pack 100 is directly connected to the device interface 132. In other embodiments, the battery pack 100 also includes an NFC tag.

[0022] Now for reference Figure 1D-1G According to one exemplary embodiment, male and female connectors 219, 183 forming a connection interface within device interface 132 are shown. Male connector 219 may be positioned on battery pack 100 to electrically connect battery pack 100 to an external device (e.g., a power device). Male connector 219 typically includes a positive terminal 220, a negative terminal 222, and a data terminal 224. Positive terminal 220 and negative terminal 222 each have a separate, dedicated electrical connection extending from connector 219 into a battery cell within battery pack 100. Positive terminal 220 and negative terminal 222 are configured to selectively supply power from the battery cell to an external device connected to battery pack 100. In some embodiments, positive terminal 220 and negative terminal 222 are configured to limit the output current from battery pack 100 to approximately 20 amperes, while the input current through data terminal 224 is limited to approximately 2 A.

[0023] Data terminal 224 is located between positive terminal 220 and negative terminal 222 and is configured to create a wired connection to a corresponding data terminal on an external device. Data terminal 224 houses a series of data pins 208 configured to receive and transmit data between battery pack 100 and an external device connected to battery pack 100. The data pins 208 can be configured based on the type of external device connected to battery pack 100. For example, some or all of the data pins 208 may have different purposes or functions when battery pack 100 is connected to a zero-turn radius lawnmower instead of a pressure washer. Data pins 208 can be configured to monitor various aspects of the external device, including runtime, health status, battery usage, and other characteristics. Data pins 208 can also be configured to generate a user interface (e.g., on user interface 705, as discussed below) that can be used to control or monitor external devices separate from their dedicated control panels. Thus, battery pack 100 can provide a digital control panel or digital dashboard for devices that would not otherwise present any performance-based data. The number of data pins 208 present in data terminal 224 can vary depending on the required level of control and functionality. In some embodiments, data terminal 224 accommodates eight data pins 208.

[0024] The male connector 219 on the battery pack 100 is configured to mate with the female connector 183 on the device interface 132. The female connector 183 includes three dedicated female terminals or connectors 185, 187, and 198, which are configured to mate with the positive terminal 220, negative terminal 222, and data terminal 224 on the first male connector 219. Figure 1F and 1G As shown, terminal 198 can accommodate and support multiple data pins 209 for connection and communication with data pin 208. To mount battery assembly 100 onto the device interface, terminals 220, 222, and 224 are first aligned with dedicated female terminals 185, 187, and 198 on device interface 132. Pushing terminals 220, 222, and 224 toward the three dedicated female terminals 185, 187, and 198 creates a removable connection between terminals 220, 222, and 224 and female terminals 185, 187, and 198, which also establishes electrical communication between battery assembly 100 and external devices supporting device interface 132. In the mounted position, female connector 198 receives data terminal 224, which creates a wired data connection between data pins 208 and data pins 209. Applying a threshold force in the opposite direction (e.g., pulling terminals 220, 222, 224 away from the external device) will cause connector 219 to release device interface 132 and cause battery assembly 100 to detach from the external device supporting device interface 132.

[0025] Now for reference Figure 2According to some embodiments, a user interface 205 on mobile device 110 is shown. User interface 205 can be displayed after logging into management system 101 and selecting an active "Add" button. Upon selecting the "Add" button, a pop-up window is generated and displayed on the display screen of mobile device 110. The "Add New Item" pop-up window allows the user of the management system to add an item or product (e.g., battery pack, blower, lighthouse, other types of power equipment products, etc.) to the management system by scanning a barcode in scanner window 215 (e.g., via the camera of mobile device 110). The generated pop-up window also includes an active button that allows the user to choose to manually enter a product-specific identification (ID) number.

[0026] Figure 3 A user interface 305 on the display screen of a mobile device 110 according to some embodiments is depicted. In some embodiments, the user interface 305 is generated and displayed on the mobile device 110 after a link on the user interface 205 is selected to manually enter a product ID number. The user interface 305 includes a generated pop-up window for adding a new item via a unique product ID number (e.g., a unique serial number located near a barcode on the product). The "Add New Item" window includes, but is not limited to, an input 310 for the product ID number, an input 315 for the new item name, and an active button 320 for completing the addition of the new item. The user interface 305 also includes an active link for saving the new item (e.g., a battery-powered device product) and directly adding another new product. Additionally, the user can select an icon to return to the user interface 205 to add a new product by scanning a barcode using the mobile device 110.

[0027] Now for reference Figure 4According to some embodiments, a user interface 405 on mobile device 110 is shown. User interface 405 can be displayed when the “My Projects” tab is selected in the management system's taskbar. The taskbar may also include options for a “Home” tab, a “Program” tab, and an “Account” tab for editing user profiles (e.g., OEM profile page, rental service user profile, etc.). User interface 405 includes a map indicating the locations 410 of projects added by the user to the management system. According to one embodiment, the current projects being tracked and monitored by the management system are displayed in a product list 415 on the left side of user interface 405. Each location 410 corresponds to one project in product list 415. In response to the selection of one of the locations 410, the project in product list 415 can be highlighted and / or expanded to display more information to the user about the product corresponding to the selected location. For example, when selecting location 410 where a lighthouse and a blower are currently located and operating, a summary of information about the current operation of the blower and the lighthouse can be displayed. The summary may include, but is not limited to, the name of the item in product list 415, the name of the battery connected to the item, the remaining charge in the connected battery, the battery status of the device (e.g., good battery health, fault detected in the battery, poor battery health, etc.), the amount of remaining voltage used for the item (e.g., 11.2 volts (V)), the temperature of the item, the product ID number, the address of the item's location, and the amount of time the item has been running (i.e., powered on using battery power).

[0028] According to some implementation plans Figure 5A user interface 505 is depicted on a mobile device 110 within the management system 101 for viewing current programs and adding new programs. The user interface 505 includes a "My Programs" list 510 of ongoing programs monitored by the management system. For example, programs using battery-powered devices (such as lawnmowers) may display an icon representing the product type used in the program. The image of the product type running for the program (such as a lawnmower) also includes the program time. In some implementations, the program time displays the number of days that have elapsed since the program began. In other implementations, the time displayed in the program icon may include the program start date, the number of hours the program has been running, the number of days remaining in the program schedule, etc. The user interface 505 also includes a "Sample Programs" list 515, which may display several types of programs being tested (e.g., products used in demonstrations, products under development, etc.). Users of the management system 101 can delete all programs loaded and displayed in the "Programs" tab via a "Clear" activated link. Furthermore, users (such as OEM managers) can add new programs via a "New Program" activated button or view a user's (such as an OEM's) current program list by selecting a "View More" activated button. Therefore, OEMs can effectively manage and track a large number of programs and various products (e.g., outdoor power equipment manufactured by the OEM) through a management system. For example, if an OEM rents out power equipment to other users, the OEM can track the current location of the rented equipment by selecting the appropriate rental program.

[0029] Now for reference Figure 6 According to one embodiment, the user interface 605 on the display of the mobile device 110 displays input options for adding a new product to the management system. The user interface 605 can be generated after selection on the user interface 505 to create a new scheme in the management system. In some embodiments, the pop-up window of the user interface 605 includes inputs for a product name 610, a model number 615, a description 620, and an image 625. After selecting image input 625, the mobile device 110 can display a user image for taking a photo using the mobile device's camera. Once the product details are filled in for the new product, a "Save" activation button 630 can be selected to store the new product in the "Scheme" column of the management system. In other embodiments, the pop-up window on the user interface 605 may include inputs for other product details, such as manufacturing date, rental date, the name of the OEM that owns and rents the product, etc.

[0030] Figure 7 Describing the use of in Figure 1AUser interface 705 on management system 101 configures the data pins of new products. In some embodiments, user interface 705 is displayed after product details are entered for the new product and the “Save” button 630 of user interface 705 is activated. User interface 705 includes a pin function library on the left and a new product connection interface with eight data pins. In other embodiments, the management system configures functions for more or fewer than eight data pins. Data pins 715 are not yet programmed. Once a function of one of the data pins 715 is programmed using the pin function library, the appearance of the data pin icon can change color and display a check mark. The programmed data pin can also display the selected function of the data pin, such as a data pin for enabling battery pack 100 or a data pin for CAN protocol communication. In some embodiments, the battery has a CAN identification that can be updated according to the device type or the location where battery pack 100 is connected. User interface 705 can be used to select available pin locations on a map representing the connection interface of the new product. In response to the selection of one of the unprogrammed data pins 715, a list of available functions can be accessed via user interface 805. Figure 8 The data pins can be used as input / output (I / O) modules to transmit information to and from the battery management system 101 of the battery pack 100. In some embodiments, the programmable data pins are included in a small programmable module manufactured by an OEM. The programmable module can be mounted to the interface 132 of the power equipment. The programmable module is capable of receiving mechanical and electrical connections with the battery pack 100. In some embodiments, the programmable module has an electrical connection of at least 1 kW with the connected battery pack 100.

[0031] Programmable data pins allow users to configure device 105 to extract data and manage power equipment 105 according to their needs. For example, a customer can program the data pin as an analog input and receive the pin's output through the user interface of management system 101. The dynamic programming capability of the data pins and management system 101 provides users with a user interface for the management system (e.g., dashboard 115). Figure 17 The management system offers multiple options. It can be used to test new products for OEMs or for on-site use while powering equipment. Users can optimize the use of battery pack 100 according to their needs. Furthermore, users can remotely view diagnostics of products (such as lawnmowers or blowers) and can select which diagnostics of battery pack 100 to track. Users can also remotely control products (e.g., blowers) via the connected battery pack 100. For example, the functionality of data pins can be programmed to instruct the connected battery pack 100 to power off, thereby shutting down devices connected to the battery pack 100. In some embodiments, different data pin configurations can be stored within an NFC tag 134 located on the power equipment 105.

[0032] Now for reference Figure 8 According to one embodiment, the user interface 805 on the mobile device 110 displays several options for programming one of the data pins 715. After selecting one of the data pins 715, a pin function library can display options for various functions of the data pin. In some embodiments, these functions include CAN protocol, pack enable, digital input, and analog input. Each option displayed in the pin function library may include an information link for users (e.g., OEMs) to view a description of the pin function type. For example, information about the CAN protocol function may be displayed in a pop-up window on the user interface 805. The pin function information indicates that the Controller Area Network (CAN bus) is a robust vehicle bus standard designed to allow microcontrollers and devices to communicate with each other's applications without a host computer. The CAN protocol is an information-based protocol.

[0033] Now for specific reference Figure 9 According to an exemplary embodiment, in response to the selection of one of the available options for a pin function on the user interface 805, the mobile device 110 may display a user interface 905 depicting the pin function options for managing data pins on the system. For example, if digital input is selected as the function of the data pin selected on the graph of data pin 715, an input options window 910 is displayed. The input options window 910 may include several inputs corresponding to the digital input function, such as display name, minimum value, maximum value, controller type (e.g., switch, button, slider, stepper), on and off labels, minimum on and off values, maximum on and off values, and write interval (e.g., 100 ms). The write interval may be the amount of time between transferring data from the digital input data pin to the cloud of the IoT system. The user interface 905 also includes an active button 915 for removing the selection of a data pin function and an active button 920 for saving the selection of a data pin function (e.g., digital input, battery enable, etc.).

[0034] refer to Figure 10 And refer to Figure 1A-1CAccording to some embodiments, a user interface 1005 is shown for programming an NFC tag 134 after selecting a pin function for each data pin. The user interface 1005 displays the selection of data pin functions and a window for authorizing the programming of the NFC tag 134 to the device interface 132. In some embodiments, if the user enters an incorrect authorization token more than a predetermined number of times (e.g., three attempts), the management system 101 can lock for a time interval. An activatable button 1010 can be selected to program the NFC tag 134 to select functions for the data pins to configure a new product. In response to the selection of the activatable button 1010, the user interface 1105 ( Figure 11 The NFC tag 134 can be displayed on the mobile device 110. The user interface 1105 may include instructions to the user (e.g., an OEM) to bring the mobile device 110 within a specific distance of the NFC tag 134. In some embodiments, the user interface 1105 illustrates the process of writing to the NFC tag 134, and once completed, configuring a status notification for a new product by writing programmable data pin functionality to the NFC tag 134. After writing to the NFC tag 134 is complete, the management system may allow the user to view information in the "My Items" tab (e.g., as shown in user interface 405). Figure 4 View the newly configured product in the interface shown in Figure 1005. The management system can also provide an activatable button to return to a user interface similar to 1005. Figure 10 The user interface 1005 allows users to change the configuration of data pins, test new products and record data, change product settings (e.g., product name, product description, etc.), program another NFC tag 134 for the product, and / or view the records of created products using options in the upper right corner of the user interface 1005. In other implementations, the data pins are programmed, for example, by scanning a barcode, CAN communication, RS485 communication, or USB connection, instead of writing the functionality of the programmable data pins into the NFC tag 134.

[0035] Now for reference Figure 12 According to some implementations, a user interface 1205 is shown on the management system 101 displaying product / equipment information and the activity history of product or equipment 105. In response to the selection of one of the items in the "My Items" tab of the management system 101 for configuration and tracking, the user interface 1205 can be displayed on a mobile device 110, such as... Figure 4As shown. For example, selecting a blower item in item list 415 allows the management system to display details of the tracked blower to the user. In some embodiments, user interface 1205 includes an activity history window 1210, battery charge level 1215, estimated run time 1220, summary window 1225, location window 1230, battery label 1235, and battery summary window 1240. Battery label 1235 may be optional to provide further details about the battery connected to the power unit (e.g., the blower monitored by management system 101). Activity history window 1210 may include a list of runs associated with the blower, such as power cycles, product renaming, battery connected, battery charged, battery depleted, detected faults, etc. The list of runs displayed in activity history window 1210 may also include a time stamp for each activity, such as date, time, or number of days elapsed since the activity occurred. In some embodiments, an option to clear the activity history is presented in activity history window 1210.

[0036] The Project Summary window 1225 may include general information about the power equipment. For example, information in the Project Summary window 1225 may include, but is not limited to, the product name (e.g., blower, lawnmower, pressure washer, etc.), product ID number (e.g., project serial number), product image, the time when a report was last generated for the product, product status (e.g., normal, healthy, at risk, faulty, charging, etc.), and the number of current alarms for the product. In some embodiments, any alarms generated for the product are displayed in the Activity History window 1210. The Location window 1230 may display the location of the tracked power equipment. In some embodiments, the location of the power equipment is detected by a GPS sensor in the management circuitry 102 of the connected battery pack 100 and then transmitted to the OEM's cloud data system via the network interface 104 of the battery pack 100. The Estimated Runtime window 1220 may display the remaining amount of time the device can operate on the connected battery. The remaining time and an indicator showing device usage over time may be displayed. When configuring a new product for the battery management system, the modules shown in the user interface 1205 may be configured by an operator (e.g., the OEM).

[0037] According to an exemplary implementation, Figure 13Another user interface 1305 displays information about the power equipment being monitored on the management system. User interface 1305 shows alternative implementations of the types of data that can be displayed for the tracked power equipment. For example, the blower tracked in user interface 1305 is not connected to a battery. User interface 1305 includes the same information modules as user interface 1205, such as the project summary window 1225, location window 1230, and estimated run time window 1220, as well as additional data modules for controlling the blower power. Therefore, the OEM may be able to shut down the tracked power equipment without directly connecting it to the power equipment. In other implementations, the toggle button of power button 1310 is a slider that allows the operator to change the amount of electricity used by the equipment during operation (e.g., by dimming the lighthouse brightness). Once the battery is physically and electrically connected to the equipment (e.g., the blower shown in summary window 1225), management system 101 can display power details of the connected battery pack 100.

[0038] refer to Figure 14 According to some embodiments, an enlarged view 1405 of a portion of a user interface depicting details of a connected battery pack 100 is shown. For example, view 1405 can be displayed on a mobile device 110 when the connected battery label 1235 is selected on user interface 1205. View 1405 is shown as including a battery charge level 1215 of the connected battery and a battery summary window 1240. The battery summary window 1240 may include a power meter 1415, a temperature measurement 1420, and a current measurement 1425 of a battery physically and electrically connected to an outdoor power device. The battery summary window 1240 also includes an automatic shutdown option 1410. Thus, the OEM can wirelessly shut down the battery to stop the operation of the power device connected to the battery pack 100. Additional information that may be included in the battery summary window 1240 includes, but is not limited to, the last reported time, battery status, number of battery alarms, manufacturing date, number of charge cycles, etc. The power meter 1415, temperature measurement 1420, and current measurement 1425 may be determined by sensors in the battery pack 100. Measurements from battery pack 100 can be transmitted to the management system via a cloud system through the communication interface of battery pack 100 (e.g., network interface 104).

[0039] In some implementations, the user interface 1405 remotely displays data received from the battery pack 100. Among other data, the user interface 1405 displays information related to battery runtime, battery health, and battery location (e.g., using a GPS system on the battery pack 100). The user interface 1405 may allow employees and / or operators to remotely lock the battery pack 100, preventing it from providing power. In this way, if it is determined that theft may have occurred, the battery pack 100 can be tracked and shut down. Furthermore, by using remote tracking and operation, employees of the rental company can lock the battery pack 100 upon the expiration of the rental period. The operator of the battery pack 100 can then be prompted via an application on their own mobile device whether they wish to extend the rental period, and the rental can be done remotely. By interacting with the application displayed on the operator's mobile device, the operator can also preemptively extend the rental period, sending notifications to the rental company and / or its employees.

[0040] User interface 1405 displays battery pack charging and health status data. Rental service operators or employees can use the battery management system 101 via user interface 1405 to track the battery charging levels of multiple battery packs 100 to determine which battery pack 100 can be fully charged and ready for use and / or rental. Furthermore, battery packs 100 can be selected for certain devices based on various parameters associated with them, such as state of health (SoH), state of charge (SoC), battery charge level, etc. For example, a device requiring less battery charge can use a battery pack 100 with less charge compared to a device that actually requires a fully charged battery. Rental companies can track the charge level of battery packs 100 to determine whether to rent a specific battery pack 100 to a customer based on which device the operator wishes to use it for. User interface 1405 may also display other health characteristics, such as which battery packs 100 may not be charging correctly. In some implementations, a warning light is displayed on the user interface of the battery pack 100 or mobile device 110 when the charge level of the battery pack falls below a certain threshold (e.g., 15%). In other implementations, if the battery pack 100's charge level falls below a threshold, an alarm can be generated and displayed on the user interface 1405. The user can program the warning light to turn on or generate a notification at what charge level using the management system and programmable data pins. The user interface 1405 can also display power data, such as how quickly the connected battery pack 100 is depleted if the device 105 operates at full power for a certain period.

[0041] According to one implementation plan, Figure 15Another user interface 1505 is shown for displaying information about the monitored power equipment via a mobile device 110. In one embodiment, the project summary window 1225 includes information about the tracked equipment (e.g., lighthouses) being leased to customers. The location window 1230 can display the current location of the lighthouse. The management system can receive the location of the lighthouses via a network connected to the power equipment fleet, such as a cloud system (e.g., Figure 1A The fleet management system 114 shown is illustrated. The user interface 1505 also includes a color temperature window 1510, an activatable power button 1515, a brightness window 1520, an estimated run time window 1220, and a scheduling window 1525. The data modules displayed in the user interface 1505 can be configured by the user to control different functions of the power equipment. For example, a user (e.g., an OEM testing the power equipment or a customer renting the power equipment) can use a slider in the brightness window 1520 to change the brightness of the lighthouse. In another embodiment, the color temperature window 1510 can be used to test the temperature of the light emitted by the lighthouse. The scheduling window 1525 may include an activatable toggle switch to operate the lighthouse according to a predetermined schedule, as referenced below. Figure 16 Further description. In other embodiments, the user interface 1505 includes different data and control modules, depending on the desires and needs of the customer using the product or the OEM testing the product.

[0042] Now for reference Figure 16 According to one embodiment, an enlarged view 1605 of a portion of a user interface for editing the operating schedule of a power device is shown. The edit schedule window 1610 can be configured to change the operating schedule of a power device. In some embodiments, different schedule types can be provided, such as “dawn to dusk,” “custom time and duration,” and “custom start and stop.” For example, if a user selects the “dawn to dusk” option in the edit schedule window 1610, a power device (e.g., a lighthouse) connected to the battery pack 100 can be turned on from sunset to sunrise. In other embodiments, the user can enter the time for the device to turn on and / or off, or the duration of the device's operation. Therefore, time spent by the user traveling to a construction site or test location to turn the device on and off can be saved, as the user can perform these controls remotely using the battery management system described herein.

[0043] Now for reference Figure 17 And refer to Figure 1A-1CAccording to one embodiment, a system 1700 is shown that connects to a battery pack 100 connected to device 105 in an outdoor power equipment fleet. The battery pack 100 is communicatively connected to a remote management system (e.g., management system 101), which includes a dashboard 115 presented on an interface of a computing device (e.g., a desktop computer, mobile device 110). In some embodiments, the battery pack 100 may be part of an IoT system. The battery pack 100 may not include cellular communication capabilities, thus requiring a separate gateway (e.g., a dedicated gateway or mobile gateway) for network communication. In other embodiments, the battery pack 100 includes cellular communication capabilities and acts as a gateway, such as an IoT gateway. Therefore, data communication between the battery pack 100, mobile device 110, and other computing devices can be facilitated by a network (e.g., a Wi-Fi network). This network may include cellular transceivers, the Internet, a local area network (LAN), or a wide area network (WAN). Networking between battery pack 100, mobile device 110, device 105 (e.g., via NFC tag 134 on interface 132 of device 105), and other computing devices can be facilitated by short-range and / or long-range communication technologies. Short-range and / or long-range communication technologies may include, but are not limited to, Bluetooth transceivers, Bluetooth beacons, RFID transceivers, NFC transceivers, Wi-Fi transceivers, cellular transceivers, wired network connections, etc. Therefore, in one embodiment, communication between mobile device 110, other computing devices (e.g., a desktop computer displaying dashboard 115), and battery pack 100 can be facilitated by a cloud-based system and connected to that cloud-based system via RFID and Wi-Fi connectivity on battery pack 100. In other embodiments, communication can be facilitated by a cloud-based system and connected to that cloud-based system solely via Wi-Fi. In yet another embodiment, communication can be facilitated by a cloud-based system and connected to that cloud-based system via a cellular transceiver. In still another embodiment, communication can be facilitated by a cloud-based system and connected to that cloud-based system via Bluetooth and a cellular transceiver. In all these implementations, the cloud-based system can be accessed by third parties, such as consumers and / or leasing companies (e.g., OEM companies).

[0044] The various connectivity environments described herein allow communication across battery pack 100 and across devices by integrating communication capabilities into the battery, rather than the device itself. Therefore, the battery pack 100 described herein is standardized and can be used on all platforms, regardless of the type of device powered by the battery pack 100. The battery pack 100 can also advantageously receive software updates wirelessly from cloud-based IoT systems. Furthermore, the use of IoT allows for the direct integration of data into usage and analytics systems, enabling companies (such as OEMs) to better understand how the use of the battery pack 100 impacts their business and / or how to manage the use of the battery pack 100 or certain devices.

[0045] Furthermore, the product-side IoT system allows the storage of runtime data, location data, configuration data, and other usage data of the battery pack 100 and power unit 105 in the cloud of the management system 101. This improves data storage and security. The IoT system can verify the data in the cloud using relevant data from each battery pack 100. The IoT system can help track which battery packs 100 are connected to the power unit 105 and which are not currently connected (e.g., connected to a charging station or portable charger). Therefore, OEMs can determine which battery packs 100 are available for lease to other users. Additionally, using the battery packs 100 described herein and various connectivity environments, the operation and management of products (such as lighthouses, pumps, etc.) can be performed remotely. In the leasing system, the use of IoT allows the battery pack 100 and / or the device to be disabled and enabled based on the lease period. For example, if a user uses the battery pack 100 for a longer period than the allocated lease time, the battery pack 100 can be remotely powered off (e.g., via automatic shutdown option 1410). Figure 14 In this way, the leasing company saves time on tracking the location and usage of the battery pack 100.

[0046] While this specification contains numerous details of specific implementations, these details should not be construed as limiting the scope of the claims, but rather as descriptions of the specific features of particular implementations. Certain features described in the context of different implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may be implemented individually or in any suitable sub-combination in multiple implementations. Furthermore, while some features may have been described above as functioning in certain combinations and even initially claimed in this manner, one or more features in a claimed combination may be removed from that combination in certain circumstances, and the claimed combination may involve sub-combinations or variations thereof.

[0047] It should be understood that although the use of words such as “suitable” or “desirable” in the foregoing description indicates that a feature described in this way may be more desirable, the feature may not be necessary, and embodiments lacking such features may be considered within the scope of the invention, as defined by the appended claims. When reading the claims, the use of words such as “a,” “an,” “one,” or “at least one” is not intended to limit the claims to only one, unless expressly stated to the contrary in the claims.

[0048] It should be noted that certain paragraphs of this invention may use terms such as "first" and "second" in conjunction with "side" and "end" to identify or distinguish one from another, or one from several others. These terms are not intended to associate entities (e.g., first side and second side) merely in time or according to sequence, although in some cases these entities may include such a relationship. These terms also do not limit the number of possible entities (e.g., sides or ends) that can operate in the system or environment.

[0049] As used herein, the terms “coupled” and “connected” refer to two components joining each other directly or indirectly. Such joining can be fixed (e.g., permanent) or movable (e.g., removable or releasable). Such joining can be achieved by the two components, or the two components and any other intermediate components, being integrally formed into a single unit, or by the two components, or the two components and any other intermediate components, being connected to each other.

[0050] As used herein, the term "circuit" can include hardware configured to perform the functions described herein. In some embodiments, each corresponding "circuit" can include a machine-readable medium for configuring the hardware to perform the functions described herein. A circuit can be embodied as one or more circuit components, including but not limited to processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some embodiments, a circuit can take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (ICs), discrete circuits, system-on-a-chip (SOC) circuits, etc.), telecommunications circuits, hybrid circuits, and any other type of "circuit". In this respect, "circuit" can include any type of component for implementing or facilitating the implementation of the operations described herein. For example, a circuit described herein can include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, etc.

[0051] The “circuit” may also include one or more processors communicatively connected to one or more memories or storage devices. In this regard, the one or more processors may execute instructions stored in the memory, or may execute instructions otherwise accessible to the one or more processors. In some embodiments, the one or more processors may be embodied in various ways. The one or more processors may be constructed in a manner sufficient to perform at least the operations described herein. In some embodiments, the one or more processors may be shared by multiple circuits (e.g., circuit A and circuit B may contain or otherwise share the same processor, and in some example embodiments, the processor may execute instructions stored or otherwise accessed through different regions of memory). Alternatively or additionally, the one or more processors may be configured to perform or otherwise perform certain operations independently of one or more coprocessors. In other exemplary embodiments, two or more processors may be connected via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution. Each processor may be implemented as one or more general-purpose processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components configured to execute instructions provided by memory. The one or more processors may take the form of a single-core processor, a multi-core processor (e.g., a dual-core processor, a triple-core processor, a quad-core processor, etc.), a microprocessor, etc. In some embodiments, the one or more processors may be external to the device; for example, the one or more processors may be remote processors (e.g., cloud-based processors). Alternatively or additionally, the one or more processors may be internal to the device and / or local. In this regard, a given circuit or its components may be located locally (e.g., as part of a local server, a local computing system, etc.) or at a remote location (e.g., as part of a remote server (e.g., a cloud-based server)). For this purpose, a “circuit” as described herein may include components distributed across one or more locations.

Claims

1. A battery pack comprising: case; Multiple rechargeable battery cells are located within the housing; A connection interface that communicates with the plurality of rechargeable battery cells, the connection interface including a plurality of data pins, a positive terminal and a negative terminal; A near field communication (NFC) reader is located within the housing; A battery management system that communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader, retrieve storage parameters corresponding to the NFC tag identification, and configure at least one of the plurality of data pins based on the storage parameters corresponding to the NFC tag identification; as well as A communication gateway that communicates with the battery management system, the communication gateway being configured to transmit and receive information via a communication protocol with a frequency exceeding 14 MHz; The battery management system is configured to monitor the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins, and to transmit the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins through the communication protocol.

2. The battery pack of claim 1, wherein the data pin is reconfigurable to receive a first dataset when the NFC reader provides a first NFC tag identification to the battery management system, and wherein the data pin receives a second dataset when the NFC reader provides a second NFC tag identification to the battery management system that is different from the first NFC tag identification.

3. The battery pack according to claim 2, wherein the first NFC tag identifies a first type of power device, and the second NFC tag identifies a second type of power device.

4. The battery pack of claim 2, wherein when the NFC reader provides identification of the first NFC tag to the battery management system, the data pin is configured to transmit an instruction from a power device to the battery management system, and wherein upon receiving the instruction, the battery management system adjusts the position of the contacts to interrupt power transfer between the rechargeable battery cell and the positive and negative terminals.

5. The battery pack of claim 2, wherein when the NFC reader provides identification of the first NFC tag to the battery management system, the data pin is configured to transmit an instruction from a power device to the battery management system, and wherein upon receiving the instruction, the battery management system adjusts the position of the contacts to initiate power transfer between the rechargeable battery cell and the positive and negative terminals.

6. The battery pack of claim 2, wherein the first dataset includes one of blade speed, temperature, power-on command, power-off command, health status, or number of blade rotations from the power device associated with the identification of the first NFC tag.

7. The battery pack of claim 2, wherein the data pin is configured to transmit a third dataset when the NFC reader provides identification of the first NFC tag to the battery management system, and wherein the data pin is configured to transmit a fourth dataset when the NFC reader provides identification of the second NFC tag to the battery management system.

8. The battery pack of claim 7, wherein the third dataset includes one of battery life, battery health status, battery state, or battery temperature.

9. The battery pack according to claim 1, wherein the data pin is an input / output (I / O) module.

10. The battery pack of claim 1, wherein the communication protocol is Bluetooth.

11. The battery pack of claim 1, wherein the battery management system, communication gateway, and NFC reader form an Internet of Things (IoT) module on the battery pack, the IoT module being able to communicate from outside the battery pack using the plurality of data pins, the NFC reader, and the communication protocol, and wherein the IoT module is connected to a management circuit that monitors the operating parameters of the rechargeable battery cell.

12. A battery pack comprising: case; Multiple rechargeable battery cells are located within the housing; A connection interface that communicates with the plurality of rechargeable battery cells, the connection interface including an electrical connector having a positive terminal, a negative terminal and a plurality of data pins; A near field communication (NFC) reader is located within the housing; A battery management system that communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader, retrieve storage parameters corresponding to the NFC tag identification, and configure at least one of the plurality of data pins based on the storage parameters corresponding to the NFC tag identification; as well as A communication gateway that communicates with the battery management system, the communication gateway being configured to transmit and receive information via Bluetooth; The battery management system is configured to monitor the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins, and to transmit the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins via Bluetooth.

13. The battery pack of claim 12, wherein the plurality of data pins are reconfigurable in response to receiving a signal from a mobile device communicating via Bluetooth.

14. The battery pack of claim 12, wherein the battery is further configured to communicate via a controller area network (CAN).

15. The battery pack of claim 12, wherein the battery management system is further configured to monitor at least one of the health status and operating status of the power equipment connected to the connection interface using information received through at least one of the plurality of data pins.

16. The battery pack of claim 15, wherein the battery management system is configured to transmit at least one of the health status and the operating status of the power device connected to the connection interface via Bluetooth.

17. The battery pack of claim 15, wherein the battery management system is configured to monitor at least one of the blade speed of the power unit, the temperature of the power unit, and the power request status of the power unit.

18. The battery pack of claim 12, wherein the data pin can be configured to function as a controller area network (CAN), battery pack enable, digital input, and / or analog input.

19. The battery pack of claim 12, wherein when at least one of the plurality of data pins is configured based on the storage parameters corresponding to the NFC tag identification, at least one input on the battery pack is configured to adjust the operating parameters of the power equipment associated with the NFC tag identification.

20. The battery pack of claim 19, wherein when the power device is a lighthouse, the at least one input is configured to adjust the brightness of the lights inside the lighthouse.

21. The battery pack of claim 20, wherein the at least one input is configured to use pulse width modulation to adjust the brightness of the light within the lighthouse.

22. The battery pack of claim 12, wherein when at least one of the plurality of data pins is configured based on the storage parameters corresponding to the NFC tag identification, at least one input on the battery pack is configured to adjust one of a current input limit and a current output limit.

23. The battery pack of claim 22, wherein the current input through the plurality of data pins is limited to approximately 2 amps, and the current output through the positive and negative terminals is limited to approximately 20 amps.

24. The battery pack of claim 12, wherein the battery management system, communication gateway, and NFC reader form an Internet of Things (IoT) module on the battery pack, the IoT module being able to communicate from outside the battery pack using the plurality of data pins, the NFC reader, and the Bluetooth transmission, and wherein the IoT module is connected to the management circuitry of the battery management system that monitors the operating parameters of the rechargeable battery cells.

25. A battery pack comprising: case; Multiple rechargeable battery cells are located within the housing; A connection interface that communicates with the plurality of rechargeable battery cells, the connection interface including a plurality of data pins, a positive terminal and a negative terminal; A near field communication (NFC) reader is located within the housing; A battery management system that communicates with the NFC reader and is configured to receive information including NFC tag identification from the NFC reader, retrieve storage parameters corresponding to the NFC tag identification, and configure at least one of the plurality of data pins based on the storage parameters corresponding to the NFC tag identification; as well as A communication gateway that communicates with the battery management system, the communication gateway being configured to transmit and receive information via a communication protocol with a frequency exceeding 14 MHz; The battery management system is configured to monitor the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins, and to transmit the operating parameters of the rechargeable battery cell and the data received through the plurality of data pins through the communication protocol. At least one of the plurality of data pins is configured to communicate with the Controller Area Network (CAN) bus and the battery management system.

26. The battery pack of claim 25, wherein the battery pack is configured to detect the location of an accessory of the battery pack using the at least one data pin configured to communicate with the CAN bus.

27. The battery pack of claim 26, wherein the battery management system adjusts one of the maximum output current and the maximum input current based on the detected accessory position of the battery pack.

28. The battery pack of claim 25, wherein the plurality of data pins are configured to communicate with physical inputs on the battery pack, and wherein the physical inputs on the battery pack are capable of communicating with power devices associated with the NFC tag identification.

29. The battery pack of claim 25, wherein the battery pack is configured to receive software via the communication gateway, the software comprising at least one or more scripts configured to define the function of one of the plurality of data pins.

30. The battery pack of claim 29, wherein the software is provided to the battery management system via the communication gateway.

31. The battery pack of claim 29, wherein the software includes instructions for the battery management system, the instructions including the identification of at least one operating parameter of the battery pack for monitoring and transmission via the communication gateway.

32. The battery pack of claim 29, wherein the software includes an update to existing software written into the battery management system.

33. The battery pack of claim 25, wherein the battery management system, communication gateway, and NFC reader form an Internet of Things (IoT) module on the battery pack, the IoT module being able to communicate from outside the battery pack using the plurality of data pins, the NFC reader, and the communication protocol.

34. The battery pack of claim 33, wherein the IoT module is connected to a management circuit of the battery management system of the IoT module that monitors the operating parameters of the rechargeable battery cell and transmits the operating parameters of the rechargeable battery cell to the IoT module.

Images