WO2016168532A1

WO2016168532A1 - Portable electronic device having low battery indication

Info

Publication number: WO2016168532A1
Application number: PCT/US2016/027660
Authority: WO
Inventors: Walter P. PAYACK, Jr.; Robert Strong; Brendon ALLEN
Original assignee: Stanley Security Solutions, Inc.
Priority date: 2015-04-17
Filing date: 2016-04-15
Publication date: 2016-10-20

Abstract

A method for determining a battery status of a battery in a portable electronic device includes storing a baseline cycle count in memory of the portable electronic device, the baseline cycle count value being an empirically determined number of actuations that results in a requisite amount of battery depletion to achieve a low battery condition; determining an actual cycle count corresponding to an actual number of actuations of the portable electronic device; comparing the actual cycle count to the baseline cycle count to determine whether the low battery condition exists; and if the low battery condition exists, then notifying a user of the low battery condition.

Description

PORTABLE ELECTRONIC DEVICE HAVTNG LOW BATTERY TNDTCATTON Cross-Reference To Related Applications

[0001] This application claims priority to U.S. provisional patent application serial no. 62/149,050 entitled "Low Battery Indication of Fob and Other Handheld Battery Operated Components" filed April 17, 2015, which is incorporated herein by reference.

Technical Field

[0002] The present invention relates to portable electronic devices, and, more particularly, to a portable electronic device having low battery indication.

Background Art

[0003] An electronic device may include a low battery detection circuit to provide a warning of a low battery condition. As used herein, the term "low battery" means a predetermined voltage or current level of the battery where operation integrity of the electronic device in which the battery is being used may be jeopardized.

[0004] Some electronic devices include a low battery detection circuit primary designed to accommodate alkaline batteries. Alkaline batteries have a sloped-mostly-linear battery life curve. This slope of the curve is appreciable and very predictable and can be characterized at any point by doing a closed-circuit voltage (CCV) measurement to determine where on the curve it may be to predict remaining battery life with a relatively high degree of accuracy and confidence. The low battery detection circuit may be configured to measure the battery voltage and set thresholds for low battery indication, such as for example, between 25 percent and 10 percent life remaining. This allows the user to change the batteries without the surprise of sudden failure to function. If the batteries are not replaced, there can be a secondary threshold indication, e.g., the device operates only after a 5 second delay, to urge the user to change the batteries. If the batteries are not changed and the CCV reaches the cut-out point, the circuit is programmed to no longer operate because there is insufficient voltage to drive the power circuit and irregular operation may result.

[0005] With the advent of the use of lithium powered devices, such as electronic fobs, the dynamic for predicting battery level depletion has changed. For lithium batteries, the slope of the curve is relatively flat for the life of the battery. In particular, the slope is very flat until nearly the end of life. This makes for difficulty in measuring CCV for predictable battery life estimates, and battery life estimates based on CCV may not be accurate until just before the failure point.

[0006] What is needed in the art is a low battery detection apparatus and method suitable for use with a portable electronic device, and which may provide an accurate prediction of the life remaining in a battery, including a lithium battery.

Summary of Invention

[0007] The present invention provides a low battery detection apparatus and method suitable for use with a battery powered portable electronic device, and which provides an accurate prediction of the life remaining in the battery, including a lithium battery. The present invention incorporates an operations counter into the device logic and circuitry, e.g., a microcontroller, so as to count the number of actuations, i.e., the actual cycle count of the portable electronic device, e.g., the number of button presses of a fob. The actual cycle count data will then be compared to empirical data determined in a prior laboratory test. The empirical data represents the typical battery life of a battery of a particular type operated under voltage and current loads corresponding to those experienced by the battery of the portable electronic device. The empirical data is provided in terms of a baseline cycle count, e.g., the number of button presses that results in the depletion of the battery. The actual number of actuations of the portable electronic device may thus be correlated directly to the typical number of baseline total cycles representative of a full battery depletion, or representative of a percentage of battery life remaining. Thus, when the actual cycle count reaches the baseline cycle count, a programmed response may be initiated to direct the attention of the user to a battery condition, e.g., low battery. It is contemplated that the cycle count may be used alone, or may be supplemented with CCV readings, in determining the condition of the battery. For example, the CCV readings may be helpful in establishing a secondary threshold for alerting the user of pending battery failure with similar programmed responses to get user attention.

[0008] The invention in one form is directed to a method for determining a battery status of a battery in a portable electronic device, including establishing a predetermined amount of battery depletion to correspond to a low battery condition for a family of electronic devices, the portable electronic device being a member of the family of electronic devices; determining a baseline cycle count corresponding to the predetermined amount of battery depletion, the baseline cycle count being an empirically determined average number of actuations of electronic devices of the family that results in the predetermined amount of battery depletion; storing the baseline cycle count in memory of the portable electronic device; determining an actual cycle count corresponding to an actual number of actuations of the portable electronic device; comparing the actual cycle count to the baseline cycle count to determine whether a low battery condition exists; and if the low battery condition exists, then notifying a user of the low battery condition.

[0009] Supplemental thereto, the invention may further establish a second

predetermined amount of battery depletion to correspond to a critical battery condition, such that the user may be further notified of the critical battery condition. [0010] The invention in another form is directed to a method for determining a battery status of a battery in a portable electronic device, including storing a baseline cycle count in memory of the portable electronic device, the baseline cycle count value being an empirically determined number of actuations that results in a requisite amount of battery depletion to achieve a low battery condition; determining an actual cycle count corresponding to an actual number of actuations of the portable electronic device;

comparing the actual cycle count to the baseline cycle count to determine whether the low battery condition exists; and if the low battery condition exists, then notifying a user of the low battery condition.

[0011] Supplemental thereto, the invention may further store a second predetermined amount of battery depletion to correspond to a critical battery condition, such that the user may be further notified of the critical battery condition.

[0012] Advantageously, aspects of the present invention may be utilized with all battery types for determining a battery state, and then notifying the user and/or a remote administrator of a battery event, such as a low battery condition and/or a critical battery condition.

Brief Description of Drawings

[0013] The above-mentioned and other features and advantages of this invention, and the manner of attaining them, will become more apparent and the invention will be better understood by reference to the following description of an embodiment of the invention taken in conjunction with the accompanying drawings, wherein:

[0014] Fig. 1 is diagrammatic depiction of a wireless lockdown system in accordance with an embodiment of the present invention. [0015] Fig. 2 is a block diagram of an electronic fob used to initiate a lockdown in the wireless lockdown system of Fig. 1.

[0016] Fig. 3 is a flowchart of a method for determining a battery condition of a battery in a portable electronic device, such the fob of Fig. 2.

[0017] Fig. 4 is a flowchart of method for determining whether a critical battery condition has occurred, which is supplemental to the method of Fig. 3.

[0018] Corresponding reference characters indicate corresponding parts throughout the several views. The exemplifications set out herein illustrate an embodiment of the invention, and such exemplifications are not to be construed as limiting the scope of the invention in any manner.

Description of Embodiments

[0019] Referring now to the drawings, and more particularly to Fig. 1, there is shown a diagrammatic illustration of a wireless lockdown system 10 having a plurality of electromechanical locks 12-1, 12-2, 12-3, 12-4, a gateway 14, a repeater 16, a plurality of fobs 18, 20, and a remote computer 22. Each of the plurality of electromechanical locks 12-1, 12-2, 12-3, 12-4, gateway 14, repeater 16, and the plurality of fobs 18, 20 includes a respective transceiver to facilitate wireless communications.

[0020] Wireless lockdown system 10 is configured for wireless communication using, for example, the 915 MHz ISM band, and may be facilitated using the IEEE 802.15 communication protocol. Wireless lockdown system 10 is configured in a star network configuration, wherein gateway 14 is the master control point and is the primary coordinator of the radio frequency (r.f.) over-the-air traffic (represented by dashed lines) with each of the plurality of electromechanical locks 12-1, 12-2, 12-3, 12-4, repeater 16, and fobs 18, 20. Gateway 14 also serves to aggregate all transmitted data. Thus, in wireless lockdown system 10, there is no cross-communication as between the end nodes, e.g., electromechanical locks 12-1, 12-2, 12-3, 12-4 and/or fobs 18, 20, but rather, all wireless communication is routed through gateway 14. Repeater 16 is configured to extend the range of any device in wireless communication with it. In the example of Fig. 1, each of electromechanical lock 12-4 and fob 20 communicates with gateway 14 via repeater 16.

[0021] There are two types of wireless links in wireless lockdown system 10: static and mobile. Static links are formed between objects that are installed in a fixed location (e.g., gateway 14, repeater 16, and electromechanical locks 12-1, 12-2, 12-3, 12-4). Links to/from fobs 18, 20 are mobile links. Gateway 14 may maintain a routing table for all static links, whereas no routing knowledge is assumed on the mobile links. Rather, the mobile links may be dynamically determined through the use of pre-assigned data channels.

[0022] Gateway 14 communicates with remote computer 22 via the internet 24.

Gateway 14 may be connected to the internet, e.g., via a cable modem, and by wired or wireless connection. The remote computer 22 may be configured to provide data services, such as remote storage of data, and administrative services. Computer 22 may execute program instructions to initiate an advanced preventative maintenance (PM) self-test of components of wireless lockdown system 10. The remote PM is facilitated by having electromechanical locks 12-1, 12-2, 12-3, 12-4 and fobs 18, 20 coupled with wireless network infrastructure devices (e.g., gateway 14 directly, or indirectly via a repeater) and internet connectivity via gateway 14.

[0023] Each of fobs 18, 20 is configured as a handheld portable electronic device.

Moreover, each fob, such as fobs 18, 20, of wireless lockdown system 10 is a critical device in wireless lockdown system 10 because it is the fobs that are depended upon and utilized to initiate a lockdown of electromechanical locks 12-1, 12-2, 12-3, 12-4 during an emergency condition.

[0024] Thus, it is desirable for the fob users, and system administrators at remote computer 22 or other remote locations, to have access into the state of fobs 18, 20 in wireless lockdown system 10, so as to maintain fobs 18, 20 in view of the criticality of the fobs to wireless lockdown system 10. Of particular interest is the battery condition of the respective battery in each fob of wireless lockdown system 10, which in the present example, includes fobs 18, 20.

[0025] Fobs 18, 20 are identically configured, and thus for brevity, only fob 18 will be described in detail below with respect to the fob configuration and the use of the fobs in wireless lockdown system 10.

[0026] Fig. 2 is a block diagram of fob 18. Fob 18 includes a microcontroller 30, a transceiver 32, an electromechanical vibrator 34, a sound generator 36, a low battery indicator light emitting diode (LED) 38, a critical battery indicator LED 40, an alarm notice button 42, a self-test button 44, a battery 46, and, optionally, a battery voltage detection circuit 48. A lockdown event for wireless lockdown system 10 is initiated by a primary input, e.g., alarm notice button 42, on fob 18 and a self-test of fob 18 is initiated via a secondary input, e.g., self-test button 44 on fob 18.

[0027] Microcontroller 30 includes a non-transitory electronic memory 30-1 to facilitate program and data storage. Non-transitory electronic memory 30-1 may include one or more types of digital data memory, such as random access memory (RAM), non-volatile RAM (NVRAM), read only memory (ROM), and/or electrically erasable programmable read-only memory (EEPROM). [0028] Microcontroller 30 is communicatively connected via hard-wired, or bus, connection to each of transceiver 32, electromechanical vibrator 34, sound generator 36, low battery indicator LED 38, critical battery indicator LED 40, alarm notice button 42, self-test button 44, and (optionally) battery voltage detection circuit 48. Battery 46 is connected via a hard-wired connection to each of microcontroller 30, transceiver 32, electromechanical vibrator 34, sound generator 36, low battery indicator LED 38, critical battery indicator LED 40, alarm notice button 42, and self-test button 44, so as to provide direct current (DC) electrical power to each device. Battery 46 may be, for example, a CR2032 or equivalent battery.

[0029] Microcontroller 30 may be, for example, an EFM32™ microcontroller available from Silicon Laboratories, Inc. having headquarters in Austin, Texas. In the present embodiment, microcontroller 30 is configured to execute program instructions to receive input signals from each actuation of alarm notice button 42 and self-test button 44, and optionally, to receive an input signal from battery voltage detection circuit 48. Also, microcontroller 30 is configured to execute program instructions to selectively send output signals to each of electromechanical vibrator 34, sound generator 36, low battery indicator LED 38, and critical battery indicator LED 40. Microcontroller 30 is communicatively coupled to transceiver 32 for bi-directional communication. Transceiver 32 may be, for example, a LoRa™ SX1276 transceiver available from Semtech Corporation of Caniarillo, California.

[0030] In accordance with an aspect to the invention, the battery condition of the battery of a portable electronic device, such as fob 18, is assessed. The battery condition may then be provided to the user of the portable electronic device, and may also be provided to a remote location, such as web-based database 22-1 of computer 22. [0031] For example, fob 18 provides a local indication of a low battery condition that is evident to the user of fob 18 through one or more of visual LED feedback via low battery indicator LED 38, audible feedback via sound generator 36, or haptic feedback via electromechanical vibrator 34. Likewise, fob 18 may optionally further provide a local indication of a critical battery condition (a special case of a low battery condition) that is evident to the user of fob 18 through either visual LED feedback via critical battery indicator LED 40, audible feedback via sound generator 36, or haptic feedback via electromechanical vibrator 34.

[0032] The audible feedback may be in the form of a predetermined number of tones, beeps, or other sounds or messages to indicate the present battery condition to the fob user. The haptic feedback may be in the form of a predetermined number and/or duration of vibrations or pulsations to indicate the present battery condition to the fob user.

[0033] Those skilled in the art will recognize that fob 18 may be constructed with only one, two, three, or all, of any combination of low battery indicator LED 38, critical battery indicator LED 40, electromechanical vibrator 34, and sound generator 36, depending on such factors as a perceived preference of the user, the effectiveness in conveying the battery condition to the user, manufacturing cost considerations, etc.

[0034] Additionally, a fob battery status (e.g., low battery and/or critical battery) of fob battery 46 may be reported to remote computer 22 along with any RF transmission generated and transmitted by microcontroller 30 and transceiver 32. The fob battery status of each of fob 18 and fob 20 may be stored in a web-based database 22-1, which in turn may be accessed by web-based software operating of any of a plurality of computing devices, such as a laptop computer, tablet, smart phone, computer 22, etc., for viewing by administrative personnel. Web-based database 22-1 may include mass data storage in one or more of the electronic memory forms described above, or on a computer hard disk drive or optical disk.

[0035] In accordance with an aspect of the present invention, the battery status of battery 46 of fob 18 may be determined by a cycle count, alone or in combination with a battery cell voltage (CCV) of battery 46.

[0036] Fig. 3 is a flowchart of a method for determining a battery status of a battery in a portable electronic device, such as fob 18. In the method of Fig. 3, further described below, steps S 100 and S 102 are performed in a laboratory environment, whereas step S 104 is a preparatory step that may be performed at the time of manufacture, and steps S 106 through S 112 are performed by the execution of program instructions by

microcontroller 30 of fob 18.

[0037] At step S 100, a predetermined amount of battery depletion is established to correspond to a low battery condition for a family of electronic devices, wherein a portable electronic device of interest is a member of the family of electronic devices.

[0038] Assume, for example, that for a family of fobs for use in wireless lockdown system 10, it is decided that a battery depletion to a level of 25 percent of full charge will be used as the level that indicates a low battery condition for the fobs, e.g., fobs 18, 20, of the fob family. Such a selection may be arbitrary, but preferably is in a range of 15 to 25 percent of full charge of the battery.

[0039] At step S 102, a baseline cycle count corresponding to the predetermined amount of battery depletion is determined for the family of electronic devices. The baseline cycle count is an empirically determined average number of actuations of the electronic devices of the family that results in the predetermined amount of battery depletion. [0040] For example, representative samples of the fob family may be selected for testing, with each sample fob being powered with identical respective new batteries. For each sample fob, the number of actuations, i.e., button pushes, is counted until the battery in the electronic device is depleted to the predetermined amount of battery depletion, e.g., battery depletion to a level of 25 percent of full charge. This process may be repeated for each of a plurality of sample fobs, and the respective cycle counts that result in the predetermined amount of battery depletion are averaged to arrive at the base cycle count for the family of fobs.

[0041] At step S 104, the baseline cycle count is stored in memory of the portable electronic device. In the present example, the baseline cycle count determined in step S 102 is stored in memory 30-1 of fob 18.

[0042] At step S 106, an actual cycle count is determined that corresponds to an actual number of actuations of the portable electronic device. In the present example, the number of actuations of alarm notice button 42 and self-test button 44 are counted by a counter subroutine executed by microcontroller 30, and recorded in memory 30-1. In other words, each time one of alarm notice button 42 and self-test button 44 is depressed by the user of fob 18, the actual cycle count will be incremented in a counter established in microcontroller 30.

[0043] At step S 108, the actual cycle count is compared to the baseline cycle count to determine whether a low battery condition exists for the portable electronic device.

[0044] At step S 110, it is determined whether the low battery condition exists. In the present example, assume that the baseline cycle count stored at step S 104 is 500. Once the actual cycle count of fob 18 determined at step S 106 reaches 500 actuation (depressions) of alarm notice button 42 and self-test button 44, then it is determined that a low battery condition exists, and the process proceeds to step SI 12.

[0045] At step S 112, the user of the portable electronic device is notified of the low battery condition. In the present example, the user of fob 18 is notified of the low battery condition.

[0046] The low battery condition is reported locally to the fob user via at least one of visual LED feedback, audible feedback, or haptic feedback. In particular, microcontroller 30 may execute program instructions to actuate one or more of electromechanical vibrator 34, sound generator 36, and low battery indicator LED 38.

[0047] The haptic feedback provided by electromechanical vibrator 34 that is representative of the low battery condition may be in the form of a predetermined number and/or duration of vibrations or pulsations to indicate the present battery condition to the fob user. The audible feedback provided by sound generator 36 that is representative of the low battery condition may be in the form of a predetermined number of tones, beeps, or other sounds or messages to indicate the present battery condition to the fob user. The visual feedback provided by low battery indicator LED 38 that is representative of the low battery condition may be in the form of a predetermined number, pattern, and/or duration of light flashes. Alternatively, low battery indicator LED 38 may be operated in a continuous actuation.

[0048] It is contemplated that the method described above may include a second baseline count associated with a critical battery condition, wherein the critical battery condition is closer to a total battery depletion than the low battery condition. With such a modification, after the low battery condition has occurred, the actual cycle count of fob 18 is compared to the second baseline count, and if the critical battery condition exists, then the fob user is notified of the critical battery condition.

[0049] The critical battery condition is reported locally to the fob user via at least one of visual LED feedback, audible feedback, or haptic feedback. In particular, microcontroller 30 may execute program instructions to actuate one or more of electromechanical vibrator 34, sound generator 36, and critical battery indicator LED 40.

[0050] The haptic feedback provided by electromechanical vibrator 34 that is representative of the critical battery condition may be in the form of a predetermined number and/or duration of vibrations or pulsations to indicate the present battery condition to the fob user. The audible feedback provided by sound generator 36 that is

representative of the critical battery condition may be in the form of a predetermined number of tones, beeps, or other sounds or messages to indicate the present battery condition to the fob user. The visual feedback provided by critical battery indicator LED 40 that is representative of the critical battery condition may be in the form of a predetermined number, pattern, and/or duration of light flashes. Alternatively, critical battery indicator LED 40 may be operated in a continuous actuation.

[0051] Supplemental to the method of Fig. 3, it is contemplated that the low battery condition may further be determined by a combination of the determination based on the baseline cycle count as in the method of Fig. 3 and a determination based on a low battery voltage threshold, as may be performed by battery voltage detection circuit 48 depicted in Fig. 2. Battery voltage detection circuit 48 may be configured as a closed-circuit voltage (CCV) measurement circuit, as is known in the art. Operation of battery voltage detection circuit 48 may be triggered by actuation of alarm notice button 42 and/or self-test button 44, and an actual voltage value may be generated and supplied to microcontroller 30. [0052] In such an arrangement, if microcontroller 30 determines that at least one of the base cycle count and the low battery voltage threshold has been reached, then the user is notified of the low battery condition in a manner as described above.

[0053] Fob 18 is configured to report a battery status of battery 46 to the database 22-1, which in turn may be accessed by a web-based user interface, such as a web-based interface operating on one or more of computer 22 and/or a laptop computer, tablet, smart phone, etc. In particular, microcontroller 30 executes program instructions to generate a data packet containing the battery status information, which is forwarded to transceiver 32, which in turn transmits the data packet to gateway 14. Gateway 14 then responds by sending the data packet to database 22- 1 via internet 24 for remote storage of data. The battery status of battery 46 may be reported in terms of at least one of a percentage of battery life remaining and an occurrence of the low battery condition event. Such evaluation and reporting of the battery life/condition may occur automatically with any button actuation of the portable electronic device, e.g., fob 18.

[0054] Fig. 4 is a flowchart of a supplemental method for determining whether a critical battery condition has occurred.

[0055] At step S200, a second predetermined amount of battery depletion is established to correspond to a critical battery condition for the family of electronic devices. The critical battery condition is defined to be closer to a total battery depletion than the low battery condition. For example, if the low battery condition is indicated when the battery depletion has reached 25 percent of full charge, then another level less than that amount, e.g., 10 percent, is selected to represent the critical battery condition. Such a selection may be arbitrary, but preferably is in a range of 5 to 15 percent of full charge of the battery. [0056] At step S202, a critical voltage threshold value for the battery is established that corresponds to the critical battery condition. For example, assuming a CR2032 3-volt battery, then 10 percent of full charged defines a critical voltage threshold value of 0.3 volts.

[0057] At step S204, the critical voltage threshold value is stored in memory of the portable electronic device. In the present example, the critical voltage threshold value determined in step S202 is stored in memory 30-1 of fob 18, such as at the time of manufacture.

[0058] At step S206, an actual voltage of the battery in the portable electronic device is measured. In the present example, the actual voltage of battery 46 is measured by battery voltage detection circuit 48. To insure minimal power consumption by battery voltage detection circuit 48, microcontroller 30 may only enable battery voltage detection circuit 48 for a predetermined amount of time following an actuation of one of alarm notice button 42 or self-test button 44.

[0059] In the present embodiment, a testing for the critical battery condition is performed only after the low battery condition was previously determined. Referring to Fig. 3 and 4, for example, following the notification of the user of the low battery condition at step S 112 of Fig. 3, the process may advance to step S206 of Fig. 4 to begin monitoring for the critical battery condition.

[0060] At step S208, the actual voltage determined at step S206 is compared to the critical voltage threshold value stored at step S204, so as to determine whether the critical battery condition exists.

[0061] At step S210, it is determined whether the critical battery condition exists. In the present example, assume that the critical voltage threshold value stored at step S204 is 0.3 volts. Once the actual voltage of battery 46 is depleted to 0.3 volts, then it is determined that a critical battery condition exists, and the process proceeds to step S212.

[0062] At step S212, the user of the portable electronic device is notified of the critical battery condition. In the present example, the user of fob 18 is notified of the critical battery condition.

[0063] The critical battery condition is reported locally to the fob user via at least one of visual LED feedback, audible feedback, or haptic feedback. In particular, microcontroller 30 may execute program instructions to actuate one or more of electromechanical vibrator 34, sound generator 36, and critical battery indicator LED 40.

[0064] Fob 18 is configured report a battery status of battery 46 to the database 22-1, which in turn may be accessed by a web-based user interface, such as a web-based interface operating on one or more of computer 22 and/or a laptop computer, tablet, smart phone, etc. In particular, microcontroller 30 executes program instructions to generate a data packet containing the battery status information, which is forwarded to transceiver 32, which in turn transmits the data packet to gateway 14. Gateway 14 then responds by sending the data packet to database 22-1 via internet 24 for remote storage. The battery status of battery 46 may be reported in terms of at least one of a percentage of battery life remaining, an occurrence of the low battery condition event, and an occurrence of a critical battery condition. Such evaluation and reporting of the battery life/condition may occur automatically with any button actuation of the portable electronic device, e.g., fob 18.

[0065] In accordance with another aspect of the invention, it is contemplated that web- based database 22-1 may be accessed by web-based software to perform web-based preventive maintenance of fobs 18, 20. The web-based preventive maintenance may include weekly tests that may be run and logged in web-based database 22-1, with the respective battery cycle count and CCV information of fobs 18, 20 being collected digitally. Also, it is contemplated that the weekly tests of the preventive maintenance may be expanded to include other battery operated devices in wireless lockdown system 10, such as for example, electromechanical locks 12-1, 12-2, 12-3, 12-4. The preventive maintenance report may then indicate which devices in wireless lockdown system 10 may need battery replacement.

[0066] Also, preventive maintenance may be initiated for a fob by the respective fob. For example, preventive maintenance may be initiated for fob 18 by depressing self-test button 44 of fob 18.

[0067] While this invention has been described with respect to at least one embodiment, the present invention can be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains and which fall within the limits of the appended claims.

Claims

Claims What is claimed is:

1. A method for determining a battery status of a battery in a portable electronic device, comprising:

establishing a predetermined amount of battery depletion to correspond to a low battery condition for a family of electronic devices, the portable electronic device being a member of the family of electronic devices;

determining a baseline cycle count corresponding to the predetermined amount of battery depletion, the baseline cycle count being an empirically determined average number of actuations of electronic devices of the family that results in the predetermined amount of battery depletion;

storing the baseline cycle count in memory of the portable electronic device; determining an actual cycle count corresponding to an actual number of actuations of the portable electronic device;

comparing the actual cycle count to the baseline cycle count to determine whether a low battery condition exists; and

if the low battery condition exists, then notifying a user of the low battery condition.

2. The method of claim 1, wherein the low battery condition is determined by a combination of a determination based on the baseline cycle count and a determination based on a low battery voltage threshold, wherein if at least one of the base cycle count and the low battery voltage threshold has been reached, then the user is notified of the low battery condition.

3. The method according to claim 1 or 2, wherein the low battery condition is reported locally to the user via at least one of visual LED feedback, audible feedback, or haptic feedback.

4. The method of claim 1, further comprising establishing a second predetermined amount of battery depletion to correspond to a critical battery condition for the family of electronic devices, the critical battery condition being closer to a total battery depletion than the low battery condition.

5. The method of claim 4, wherein a testing for the critical battery condition is performed only after the low battery condition was previously determined.

6. The method of claim 5, wherein the testing for the critical battery condition comprises:

establishing a critical voltage threshold value for the battery that corresponds to the critical battery condition;

storing the critical voltage threshold value in memory of the portable electronic device;

measuring an actual voltage of the battery in the portable electronic device;

comparing the actual voltage to the critical voltage threshold value to determine whether a critical battery condition exists; and

if the critical battery condition exists, then notifying a user of the critical battery condition.

7. The method according to claims 4, 5, or 6, wherein at least one of the low battery condition and the critical battery condition is reported locally to the user via at least one of visual LED feedback, audible feedback, or haptic feedback.

8. The method according to claims 1 or 2, further comprising reporting a battery status of the battery on a web-based user interface in terms of at least one of a percentage of battery life remaining and an occurrence of the low battery condition.

9. The method of claim 8, wherein the battery life and the low battery condition are evaluated and reported automatically within any button actuation of the portable electronic device.

10. The method according to claims 4, 5, or 6, further comprising reporting a battery status of the battery on a web-based user interface in terms of at least one of a percentage of battery life remaining, an occurrence of the low battery condition, and an occurrence of the critical battery condition.

11. The method of claim 10, wherein each of battery life and battery condition is evaluated and reported automatically within any button actuation of the portable electronic device.

12. The method according to claims 1, 2, 4, 5, or 6, wherein the portable electronic device is a handheld fob or other portable lockdown initiation device.

13. The method of claim 1, wherein the step of determining the actual cycle count is a counting of the number of depressions of at least one of an alarm notice button and a self-test button of a fob.

14. The method of claim 1, wherein a lockdown event is initiated by a primary input of the portable electronic device and a self-test is initiated via a secondary input on the portable electronic device.

15. A method for determining a battery status of a battery in a portable electronic device, comprising: storing a baseline cycle count in memory of the portable electronic device, the baseline cycle count value being an empirically determined number of actuations that results in a requisite amount of battery depletion to achieve a low battery condition;

determining an actual cycle count corresponding to an actual number of actuations of the portable electronic device;

comparing the actual cycle count to the baseline cycle count to determine whether the low battery condition exists; and

16. The method of claim 15, wherein the low battery condition is determined by a combination of a determination based on the baseline cycle count and a determination based on a low battery voltage threshold, wherein if at least one of the base cycle count and the low battery voltage threshold has been reached, then the user is notified of the low battery condition.

17. The method according to claim 15 or 16, wherein the low battery condition is reported locally to the user via haptic feedback.

18. The method of claim 15, further comprising establishing a second

predetermined amount of battery depletion to correspond to a critical battery condition for the family of electronic devices, the critical battery condition being closer to a total battery depletion than the low battery condition.

19. The method of claim 18, wherein a testing for the critical battery condition is performed only after the low battery condition was previously determined.

20. The method of claim 19, wherein the testing for the critical battery condition comprises: establishing a critical voltage threshold value for the battery that corresponds to the critical battery condition;

measuring an actual voltage of the battery in the portable electronic device;

21. The method according to claims 18, 19, or 20, wherein at least one of the low battery condition and the critical battery condition is reported locally to the user via at least one of visual LED feedback, audible feedback, or haptic feedback.

22. The method according to claims 15 or 16, further comprising reporting a battery status of the battery on a web-based user interface in terms of at least one of a percentage of battery life remaining and an occurrence of the low battery condition.

23. The method of claim 22, wherein the battery life and the low battery condition are evaluated and reported automatically within any button actuation of the portable electronic device.

24. The method according to claims 18, 19, or 20, further comprising reporting a battery status of the battery on a web-based user interface in terms of at least one of a percentage of battery life remaining, an occurrence of the low battery condition, and the occurrence of the critical battery condition.

25. The method of claim 24, wherein the battery life and the battery condition are evaluated and reported automatically within any button actuation of the portable electronic device.

26. The method according to claims 15, 16, 18, 19, or 20, wherein the portable electronic device is a handheld fob or other portable lockdown initiation device.

27. The method of claim 15, wherein the step of determining the actual cycle count is a counting of the number of depressions of at least one of an alarm notice button and a self-test button of a fob.

28. The method of claim 15, wherein a lockdown event is initiated by a primary input of the portable electronic device and a self-test is initiated via a secondary input on the portable electronic device.