Systems and methods pertaining to optimally initiating low battery indication in battery-powered and battery backup alarms are provided.
Alarm devices are used in home and office locations to notify occupants and personnel of problems or conditions at the location. For example, an alarm device can detect the presence of smoke and initiate an audible smoke alarm.
Many such alarm devices are capable of operating with low amounts of power and can be powered, at least in part or as backup, by one or more batteries. Accordingly, even in the event of power loss to a building an alarm device can continue to operate effectively.
Given that many alarm devices run on battery power or utilize a battery backup, it is important that batteries installed in alarm devices are replaced regularly. Accordingly, many alarm devices include functionality for notifying users when the power level of a battery is low. For example, many alarm devices utilize a “low-battery chirp,” which can be a regularly-intervaled sound emitted by the alarm device.
However, battery levels may be detected as lower when the ambient temperature around the alarm device is cooler, and cooler ambient temperatures usually occur during the nighttime hours. Accordingly, low battery chirps tend to begin during the nighttime hours.
Low battery chirps during the nighttime hours can be an annoyance to users, especially on alarm devices installed at a residence, and are more likely to be disabled by users without replacing the low battery. Accordingly, there is a need for systems and methods for optimizing low battery indication by delaying low battery indication until the daytime hours.
According to embodiments, an alarm apparatus is disclosed. In certain embodiments, the apparatus is configured to monitor one or more batteries for power levels. The apparatus is further configured to initiate a wait state for a predetermined period of time upon detection of a low power battery. The apparatus can check the power level of the battery regularly during the wait state. If a low battery power level is not detected during one or more of the wait state power level checks, the alarm can return to normal operation. If a low battery power level remains detected during the wait state checks, the alarm can initiate a low battery indication upon the conclusion of the wait state.
In additional embodiments, the apparatus is configured to regularly record battery levels and determine average battery levels over set periods of time. The apparatus is further configured to estimate a time of day based on the determined average battery levels. If a low power battery is detected, the apparatus is configured to wait until a specified time of day before initiating a low battery indication.
In further embodiments, the apparatus is configured to detect levels of ambient light and compare the levels to previously recorded levels to estimate a time of day. If a low battery power is detected, the apparatus is configured to wait until a specified time of day before initiating a low battery chirp.
In additional embodiments, the apparatus is configured to perform a battery power level check at set intervals. If the battery power level check indicates a low power battery, a low battery indication is not initiated. If the battery power level check indicates a low battery power on a second consecutive check, a low battery indication can be initiated.
In further embodiments, the apparatus is configured to determine that a user-initiated event occurred and set a timer based on the user-initiated event. If a low power battery is detected, the apparatus can determine whether to initiate a low battery indication based on the set timer.
The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed embodiments, and explain various principles and advantages of those embodiments.
With reference now to the various drawing figures in which identical elements are numbered identically throughout, a description of the embodiments will now be provided.
In embodiments, alarm 100 can include a signal component 102. Signal component 102 can include functionality such as, but not limited to: audible signaling, using one or more speakers; and visual signaling, using lights and/or displays.
Alarm 100 can further include a timing component 104. Timing component 104 can be connected to signal component 102 and can include one or more clocks or any other type of component capable of estimating the current time or the passage of time.
Further, alarm 100 can include a power source 106. Power source 106 can be connected to signal component 102 and timing component 104. In certain embodiments, power source 106 can be connected to a central power system and can power alarm 100 via the central power system.
Additionally, in other embodiments, power source 106 may not be connected to a central power system, and can include one or more batteries. In further embodiments, power source 106 can draw power from a central power system and from one or more batteries, or can draw power from one or more batteries in the event of a power failure in the central power system.
The one or more batteries can include one or more electrochemical cells capable of converting stored chemical energy into electrical energy. The one or more batteries can be disposable batteries and/or rechargeable batteries of types including, but not limited to, nickel-metal hydride (NiMH), low self-discharge NiMH, nickel-zinc, alkaline, rechargeable alkaline, high-drain alkaline, lithium, and carbon zinc. Additionally, battery sizes of the one or more batteries can include, but are not limited to, AAA cell, AA cell, D cell, nine-volt, and micro cell sizes.
In certain embodiments, alarm 100 can include circuitry and/or functionality for monitoring the power and/or voltage level of one or more batteries utilized by power source 106. Such monitoring can be continuous or at regular intervals. For example, alarm 100 can test and/or record the power and/or the voltage level of the one more batteries every minute, or, as an additional example, alarm 100 can test and/or record the power and/or the voltage level of the one or more batteries every twelve (12) hours. The above time intervals and any time intervals discussed herein are merely for the purpose of illustration and are not intended to be limiting. Battery monitoring can be performed at regular time intervals of any length and such time intervals do not have to be of a constant length.
As an example, alarm 100 can include circuitry for detecting low voltage levels in an attached battery. Alarm 100 can monitor the attached battery and determine if the voltage level per cell is low based on a preset threshold. If the voltage level per cell drops below the preset threshold, alarm 100 can initiate a low battery state.
In some implementations, after the initiation of a low battery state, alarm 100 can initiate a signal using signal component 102. For example, signal component 102 can initiate an audible high-pitched “chirp.” However, in certain disclosed embodiments, the low battery chirp may not begin immediately upon detection of the low battery state, as discussed below.
Alarm 110 can additionally include a processor 118 communicating with a memory 119, such as electronic random access memory, or other forms of transitory or non-transitory computer readable storage mediums. Processor 118 can be interconnected with signal component 112 and power source 116. Further processor 118 can execute control logic and perform data processing to perform the functions and techniques as discussed herein. For example, processor 118 can compare battery levels over periods of time, estimate the current time of day, and set timing component 114 based on the estimated current time of day, as disclosed below. In certain embodiments, processor 118 can include timing component 114, while, in further embodiments, timing component 114 can be connected to and/or operate independently of processor 118.
While
Referring to
The method begins when the alarm device performs a battery check on power and/or voltage levels of one or more batteries attached to the alarm device (200). The alarm device can perform the battery check at regular intervals, such as every hour, which can be monitored using a timing component. If, at 210, the alarm device determines that no batteries are in a low power state, for example, having a voltage per cell above a set threshold, the alarm device can wait until the start of the next interval period before performing the battery check again (200).
If, at 210, the alarm device determines that one or more batteries are in a low power state, for example, having a voltage per cell below a set threshold, the alarm device can initiate a wait period using the timing component (220). As an example, if an initial low battery state is expected to occur during nighttime hours due to lower surrounding temperatures, the alarm device can be set to initiate a wait period of twelve (12) hours. Accordingly, the wait period would end during daytime hours.
During the wait period, the alarm device can perform a series of battery checks at regular intervals on the battery. If, at 230, a predetermined number of battery checks show that the battery's power level has increased to above a threshold power level, the wait period can be canceled and the alarm device can wait until the start of a next interval period before performing another battery check (200).
If, at 230, the predetermined number of checks showing the battery's power level has increased to above the threshold power level has not been met, the alarm device can initiate a low battery indicator (240). For example, the alarm device can initiate a low battery chirp using one or more sound devices.
In additional embodiments, during the series of battery checks at regular intervals, the alarm device can determine that the one or more batteries have a voltage per cell below a second set threshold, and the alarm device can initiate a low battery indicator before the end of the wait period.
Referring to
The method begins when the alarm device records battery power levels of one or more batteries at set intervals of time (300). For example, the alarm device can record battery power levels of the one or more batteries every minute. Based on recorded battery levels, the alarm device can determine average battery levels for set periods of time (310). For example, the alarm device can determine the average battery levels for every hour of a twenty-four (24) hour period.
Based on the average battery levels, the alarm device can estimate a current time of day (320). For example, batteries tend to have the lowest power level at the coldest time of night. Accordingly, if the coldest time of night is preset to be at or around 3:00 AM, the alarm device can be configured to set an hour with a lowest average battery level to be at or around 3:00 AM.
Then, alarm device can detect that a power level of one or more of the one or more batteries has fallen below a certain threshold and initiate a low power state (330). If, at 340, the alarm device determines that an estimated time of day is during the daytime hours, for example, 9:00 AM to 9:00 PM, the alarm device can initiate a low battery indicator, such as a low battery chirp (360). If, at 340, the alarm device determines that the estimated time of day is not during daytime hours, the alarm device can wait until the estimated time of day is during daytime hours (350) before initiating the low battery indicator (360).
In additional embodiments, the method can begin when the alarm records battery power levels of one or more batteries at set intervals of time. For example, the alarm device can record battery power levels of the one or more batteries every hour. Based on the recorded battery levels, the alarm device can determine a running average for set periods of time. For example, the alarm device can determine the running average battery levels for every hour of a twenty-four (24) hour period.
The alarm device can then compare a current sample of the battery power levels of the one or more batteries with the running average battery power levels for the current set period of time, for example, the last twenty-four hours. If the current sample is below the running average, the alarm device can return to an initial state. If the current sample is equal to or above the running average, the alarm device can initiate a low battery indictor.
In further embodiments, the alarm device can compare the current sample of the battery power levels of the one or more batteries not only with the running average battery power level for the current set period of time but additionally to one or more previous set periods of time, such as previous twenty-four (24) hour periods.
Referring to
The method begins when the alarm device detects an amount ambient light in a room using one or more light sensors attached to the alarm device (400). The alarm device can, in certain embodiments, detect the amount of ambient light continuously, while, in other embodiments, the alarm device can detect the amount of light at the end of predetermined time intervals. Based on the amount of ambient light detected, the alarm device can estimate a current time of day.
In some embodiments, the alarm device can record the amount of ambient light and determine a twenty-four (24) hour cycle of ambient light patterns (410). If, at 420, any light detections do not statistically fit with determined ambient light patterns, they can be discarded as outliers (425).
Based on the determined ambient light patterns, the alarm device can estimate a current time of day (430). For example, the alarm device can determine that when an amount of ambient light is low compared to an average amount of light, then the current time of day is likely during nighttime. Accordingly, the alarm device can map a twenty-four (24) hour clock to the ambient light patterns.
The alarm device can then detect that one or more attached batteries are in a low power state (440). The alarm device can use the mapped twenty-four clock to determine the current time of day. If, at 450, the alarm device determines that the current time of day is during daytime hours, the alarm device can initiate a low battery indicator, such as a low battery chirp (470). If, at 450, the alarm device determines that the current time of day is during nighttime hours, the alarm device can wait until daytime hours before initiating the low battery indicator (460).
Referring to
The method begins when the alarm device performs a regularly scheduled battery check (500). For example, the alarm device can perform a battery check every twelve (12) hours. If, at 510, the alarm device determines that no attached batteries are in a low power state, the alarm device can remain in a normal functioning state and wait until a next scheduled battery check. If, at 510, the alarm device determines that one or more batteries are in a low power state, the alarm device can record power levels of the one or more batteries and wait until a next scheduled battery check.
At the next scheduled battery check, the alarm device can retest power levels of the one or more batteries (520). If, at 530, the alarm device determines that the power levels of the one or more batteries are greater than the power levels determined in 500, the alarm device can return to a normal functioning state. If, at 530, the alarm device determines that one or more batteries have power levels that are less than or equal to the power levels determined in 500, the alarm device can initiate a low battery indicator, such as a low-battery chirp (540).
In further embodiments, the alarm device can perform two or more scheduled battery checks after an initial low power state is detected before initiating a low battery indictor. For example, an alarm device can be configured to perform a battery check every four (4) hours. If, during a regularly scheduled battery check, the alarm device determines that one or more batteries are in a low power state, the alarm device can perform two (2) more battery checks and, if the low power state remains detected, initiate a low battery indicator. If, conversely, the low power state no longer is detected or power levels of the one or more batteries rises above previous levels, the alarm device can return to a normal functioning state.
Referring to
The method begins when the alarm device detects the occurrence a user-initiated event (600). Such user-initiated events can include, but are not limited to, an installation of the alarm device, a user-initiated test of the alarm device, and a user-initiated powering on of the alarm device.
The alarm device can set a timer or clock based on the user-initiated event (610). For example, the alarm device can set a twenty-four hour clock based on the user-initiated event.
The alarm device can then detect that one or more batteries are in a low power state (620). If, at 630, the alarm device determines that a current time of day is not an acceptable time of day for a low battery indicator, the alarm device can wait until an acceptable time of day (635) before initiating a low battery indicator, such as a low battery chirp (640). For example, the alarm device can determine that the time of day of the user-initiated event is an acceptable time of day for the low battery indicator. Accordingly, the alarm device can use a twenty-four hour clock and wait until a time of day equivalent to that of the user-initiated event before initiating the low battery indicator.
It has been shown how the present embodiments have been attained. Modification and equivalents of the disclosed concepts are intended to be included within the scope of the claims, which are appended hereto.
This application claims the benefit of Provisional U.S. Patent Application No. 61/671,605, filed Jul. 13, 2012, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5087908 | Sanders, Jr. | Feb 1992 | A |
5568129 | Sisselman et al. | Oct 1996 | A |
5686885 | Bergman | Nov 1997 | A |
5686896 | Bergman | Nov 1997 | A |
5886638 | Tanguay | Mar 1999 | A |
5896091 | Soderlund | Apr 1999 | A |
5912626 | Soderlund | Jun 1999 | A |
5933078 | O'Donnell | Aug 1999 | A |
5966078 | Tanguay | Oct 1999 | A |
5966079 | Tanguay | Oct 1999 | A |
5969600 | Tanguay | Oct 1999 | A |
5990797 | Zlotchenko et al. | Nov 1999 | A |
6081197 | Garrick et al. | Jun 2000 | A |
6121874 | O'Donnell | Sep 2000 | A |
6624750 | Marman et al. | Sep 2003 | B1 |
7265678 | Chapman et al. | Sep 2007 | B2 |
7508314 | Andres et al. | Mar 2009 | B2 |
7817048 | Rouse et al. | Oct 2010 | B2 |
7893825 | Gonzales | Feb 2011 | B2 |
7961088 | Watts et al. | Jun 2011 | B2 |
20050151636 | Chapman et al. | Jul 2005 | A1 |
20060176167 | Dohrmann | Aug 2006 | A1 |
20080117029 | Dohrmann | May 2008 | A1 |
20090102672 | Petek et al. | Apr 2009 | A1 |
20090212962 | Chekal et al. | Aug 2009 | A1 |
20100073172 | Lax | Mar 2010 | A1 |
20100238036 | Holcombe | Sep 2010 | A1 |
20110095883 | Watts et al. | Apr 2011 | A1 |
Number | Date | Country |
---|---|---|
2346638 | Apr 2000 | CA |
2640016 | Apr 2009 | CA |
101413992 | Apr 2009 | CN |
1119837 | Aug 2001 | EP |
1803105 | Jul 2007 | EP |
2051221 | Apr 2009 | EP |
2363844 | Sep 2011 | EP |
2325802 | Feb 1998 | GB |
9001759 | Feb 1990 | WO |
9738406 | Oct 1997 | WO |
9906980 | Feb 1999 | WO |
0021053 | Apr 2000 | WO |
2006044750 | Apr 2006 | WO |
2010036511 | Apr 2010 | WO |
2012031213 | Mar 2012 | WO |
Number | Date | Country | |
---|---|---|---|
20140015682 A1 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
61671605 | Jul 2012 | US |