The present application relates generally to barrier operators and more specifically to adding features to pre-installed barrier operators.
Barrier operators of various kinds have been known and used for many years. Examples of such barrier operators include gate operators, rolling shutter operators, garage door operators, and the like. In one example, garage door operators are mounted within a garage to automate the process of opening and closing a garage door. Such garage door operators are designed to last for many years. In its simplest form, a garage door operator includes a motor connected to move a barrier between an open position and a closed position and control circuitry configured to control the motor. Such garage door operators can last and reliably operate a garage door for many years with basic maintenance.
More recently, however, barrier operators have begun evolving to include additional features beyond the simple task of opening and closing the barrier. For example, barrier operators can monitor the force during operation thereof. Force is an accurate measure of a movable barrier system's smooth operation, but force is not available as part of a retrofit solution. Specifically, a retrofit solution likely cannot know the force of older or competitive barrier operators because the retrofit would not have access to the barrier operator's firmware.
When the counter balance mechanism or guiderails of the movable barrier system become misaligned or wear, the barrier operator has to increase its force applied to ensure a consistent and smooth open or close action. Failures to maintain a smooth door operation can result in wear on the operator when opening, possible overrun speed when going down, and eventually motor burn out.
Generally speaking, and pursuant to these various embodiments, a barrier sensor device and associated control device is designed to monitor operation of barrier operator systems. The barrier sensor device is configured to monitor operation of barrier operators, such as previously-installed, older generation, or operators where force cannot be easily measured, for undesirable amounts of strain without barrier operator force as an input. Instead, the barrier sensor device is configured to detect both motion and tilt of a barrier. By monitoring these two aspects of barrier operation, the barrier sensor device compiles data that can be analyzed by the control device and compared to un-strained barrier operator data to determine whether the barrier operator system requires service.
The above needs are at least partially met through provision of the barrier operator feature enhancement described in the following detailed description, particularly, when studied in conjunction with the drawings wherein:
Skilled artisans will appreciate the elements and the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help improve understanding of various embodiments. Also, common but well understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted to facilitate a less obstructive view of these various embodiments. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions and a person skilled in the technical field as set forth above, except where different specific meanings have otherwise been set forth herein.
A barrier sensor device 10 as described herein advantageously provides monitoring of a movable barrier system 12, which can include a barrier operator 14, a movable barrier 16, a counter-balance mechanism 18, and guidance structure 20, such as guiderails. In one approach, the barrier sensor device 10 is secured to the barrier 16 and includes one or more sensing devices 21 that are configured to obtain position and movement data regarding operation of the movable barrier system 12 without communication with the barrier operator 14.
More specifically, the barrier sensor device 10 monitors and reports the position of the barrier 16, such as with a tilt sensor 22 or the like, to determine whether the barrier 16 is in an open or a closed position. Next, the barrier sensor 10 detects and reports motion of the barrier 16, such as with an accelerometer or vibration sensor 24 or the like. Combined together, these functionalities allow the barrier sensor device 10 to determine the amount of time it takes for the barrier 16 to travel from the open position to the closed position or from the closed position to the open position. The combination of two different sensing components that provide complimentary information allows the barrier sensor device 10 to know the status, whether open, closed, or moving, of the barrier 16 at all times. The barrier sensor device 10 can be a transmit-only device that transmits position and movement information in response to any change of the position of the barrier 16. In an alternative approach, the barrier sensor device 10 can be a bidirectional communication device allowing other devices to request information about the position and movement data of the barrier 16.
In one example, the data can be utilized by a control device 30 in communication with the barrier sensing device 10 to determine whether the barrier operator 14 is under strain as a result of mechanical problems of the barrier operator 14, wear of the counter-balance mechanism 18, wear or misalignment of the barrier guidance structure 20, or the like.
Referring now to the drawings and, in particular, to
The barrier sensor device 10 is configured to be secured to the barrier 16 by any suitable method, including, for example, fasteners (such as screws, etc.), adhesive, or the like. So configured, the barrier sensor device 10 moves with the barrier 16 and, in the example of
Additional details of one example barrier sensor device 10 will now be described with reference to
By one approach, the electronic assembly 106 includes a circuit board 108 having the tilt sensor 20 and accelerometer sensor 22 mounted thereto. The circuit board 108 is disposed within the housing 100 and secured thereto, such as by adhesive, fasteners, or the like. The circuit board 108 includes a power source bay or compartment 110 mounted thereto and sized to frictionally receive a coin cell battery 112 therein to provide power to the electronic assembly 106. Other power sources, both rechargeable and replaceable, can also be utilized, and can be coupled to the circuit board using wiring or the like. A circuit diagram of one exemplary circuit board is shown as element 108 in
The tilt sensor 22 may comprise a microelectromechanical (MEMS) switch, an optical sensor, or other physical switch that is mounted to detect the barrier's 16 orientation. For example, the tilt sensor 22 is mounted on the barrier 16 to determine the barrier's 16 vertical or horizontal orientation and based on that information, a determination can be made as to whether the door is open, i.e., the barrier is horizontally disposed, or closed, i.e., the barrier is vertically disposed. A circuit diagram of one exemplary tilt sensor is shown as element 22 in
The accelerometer 24 may be piezo electric based or may be a MEMS switch, as known in the art. A circuit diagram of one exemplary accelerometer is shown as element 24 in
In the illustrated example, the barrier sensor device 10 is remote from the control device 30 and, as such, the barrier sensor device 10 includes a processing device 114, such as a PIC16LF1824, illustrated as PIC in
The electronic assembly can further include a switch device 120 that may be mounted to the circuit board 108. The switch device 120 can take any suitable form, such as a push-button switch device as shown, a slide switch, a rotary switch, or the like. The switch device 120 can be utilized for user interaction and input into the operation of the barrier sensing device 10. The switch device 120 can be configured to perform various functions for the barrier sensing device 10. One such function is causing the barrier sensor device to initiate a learn sequence, which will be discussed in greater detail below. Another function is testing operation of the barrier sensor device 10, such as testing whether the power source has sufficient capacity for continued operation, testing communication with the control device 30, manually causing the barrier sensor device 10 to report barrier position, or the like. A circuit diagram of one switch device is shown as element 120 in
As shown in
Additionally, the electronic assembly can include a light source 132, such as a surface mount LED mounted to the circuit board 108 as shown, that is configured to provide a visual indication of operation of the barrier sensor device 10. For example, the processing device 114 can cause the LED 132 to energize upon depression of the switch device 120, during movement of the barrier 16, during transmission or reception of communications with the control device 30, or the like. As shown, in
So configured, the processing device 114 can be responsible for one or more of the following functions: monitoring the tilt sensor 22, monitoring and controlling the accelerometer sensor 24, monitoring the switch device 120, illuminating the LED 132, controlling a power circuit that provides power to the communication processor 116 and its associated memory 117, such as the circuit shown as element 134; storing rolling code data, storing settings for the tilt sensor 22 and/or the accelerometer sensor 24; storing cycle count; storing paired Controller BLUETOOTH Device Addresses; providing battery brown out protection for the barrier sensor device 10; providing a timer to communicate the barrier status and/or the position and movement data to the communication processor 116, which can be any desired interval, such as hourly, twice a day, daily, twice a week, etc.; and providing communication to the communication processor 116 for transmission to the control device 30. One example language is universal asynchronous receiver/transmitter (UART) that translates data between parallel and serial forms. As such, the communication processor 116 can be responsible for connectivity with the control device 30, storing pairing and encryption data for any paired devices in its associated memory 117, and providing UART communication to the processing device 114.
The processing device 114 can be configured to manipulate and store one or more parameters for the tilt sensor 22 and the accelerometer sensor 24. Advantageously, the parameters can be configurable by a signal from the control device 30, which can be utilized to avoid excessive battery drain and false notifications of barrier movement. Employing the radio link between the control device 30 and the barrier sensor device 10 allows the monitoring algorithm to be continuously adjusted and fine-tuned without physical adjustments to the sensors, and allows for software updates after sale. More specifically, the parameters can include one or more of: a tilt switch debounce setting configured to account for, and preferably eliminate, contact bounce or chatter; wake up intervals for presence reporting; X, Y, and/or Z axis acceleration interrupt change values; and a battery life warning setting.
The processing device memory 115 can be configured to store one or more of: the address of the control device 30, a rolling code to communicate with the control device 30; a threshold of the accelerometer sensor 24, a monitor period of the accelerometer sensor 24, a minimum count of interrupts per monitor period to correspond to movement of the barrier 16, a maximum count of interrupts per monitor period to correspond to non-movement of the barrier 16, a debounce time of the tilt sensor 22, a cycle count of barrier close events via the tilt sensor 22, a cycle count of barrier open events via the tilt sensor 22, a BLUETOOTH advertising channel map, a transmit power, and one or more setup registers for the accelerometer sensor 24.
The processing device 114 can operate software that is configured to monitor the other elements of the electronic assembly 106. For example, the software can monitor the tilt sensor 22 and the timer via polling. By another example, the software can monitor the accelerometer sensor 24 and the switch device 120 via a hardware interrupt on state change.
The barrier sensor device 10 can be configured to minimize power consumption and, therefore, maximize the life of the battery 112. For example, the processing device 114 can be configured to remain in its lowest power state unless higher power states are required for event processing. Likewise, the communication processor 116 can be powered off until and unless a connection with the control device 30 or other peripheral device is required.
Control Device
As set forth above, the barrier sensor device 10 is in communication with the control device 30, so that the control device 30 can analyze the position and movement data to track the operation and status of the movable barrier system 12. It will be understood that the control device 30 can be mounted at any desirable location to communicate with the barrier sensor device 10. For example, the control device 30 can be disposed within a common housing of and/or integral with the barrier sensor device 10 and attached to the barrier 16. Alternatively, and as shown in
The control device 30 is configured to receive communications from and/or send communications to the barrier sensor device 10. These communications can be performed by a number of different physical layer structures. In one example, the communication can be carried via a wired or bus connection or via a wireless radio communication. The wireless communication can follow any protocol including single frequency, spread spectrum, Wi-Fi, BLUETOOTH, and the like. In one example, the control device 30 is configured to establish a BLUETOOTH connection with the communication processor 116.
Additionally, the control device 30 can be configured to identify and/or ignore data collected during error operations, such as when sensor eyes are tripped during an operation. To identify the error operations, the control device 30 can be configured to receive communications from an obstacle detector 155 or can compare the error operation time to a previously measured time for an operation that had been included in the data set.
For example and with reference to
In yet another approach, the control device is configured to receive communications from at least one peripheral device including a network adapter 240 to effect a connection to the Internet. As illustrated in
So configured, example operation of the barrier sensor device 10 can include one or more of: the processing device 114 monitoring inputs from the tilt sensor 22, the accelerometer sensor 24, and the switch device 120; assessing whether a tilt, door motion, or button event has occurred; obtaining and transferring the relevant sensor information to the communication processor 116; and instructing the communication processor 116 to establish a connection with the control device 30. Once the connection is established, example operation of the control device 30 can include one or more of: the control device 30 reading data collected by the tilt and accelerometer sensors 22, 24; analyzing a current strain state of the movable barrier system 12; and writing or altering sensor parameters. Then, the example operation of the barrier sensor device 10 can further include one or more of: the communication processor 116 sending any messages from the control device 30 to the processing device 114; the processing device 114 monitoring for additional events for a given time period, such as 10 seconds, 30 seconds, 1 minute, 5 minutes, or the like; the processing device causing the connection to the control device 30 to be re-established if another event occurs; and the processing device 114 powering off the communication processor 116 if another event is not detected.
Example Sensor Operation
One specific operation flow will now be described with reference to
At step 405 of loop A, the watchdog timer is set to 0.5 seconds, and an interrupt is set on a change for the accelerometer sensor and for the switch device. The process then sleeps 410 until a change is detected or the watchdog timer times out. If the watchdog timer did not wake the processing device, it must correspond 420 to an interrupt or event change and the process goes to loop B or the interrupt loop, shown in
With the interrupt loop 500, the processing device determines 505 whether the tilt debounce has started. If yes, the processing device processes 510 the tilt debounce and sets a flag for the tilt event if both the debounce is done and the tilt sensor has changed states. After that, or if the tilt debounce has not started, the processing device determines 515 whether the accelerometer filter has started. If yes, the processing device processes 520 the accelerometer filter, sets a flag for the accelerometer event if the filter is done and the motion state has changed. After that, or if the accelerometer filter has not started, the processing device increments 525 the software watchdog and exits processing if timed out.
With loop B 600, in step 602 the processor clock is set to 8 Mhz, a 20 ms Periodic Timer is set, the software watchdog is started, and the brown-out detection is started. The processing device first determines 604 whether there is an event to process. If no, the process is sent 606 back to loop A. If yes, the processing device determines 608 whether the periodic update event needs to be sent. If yes, the periodic update is started and the event flag is cleared 610. After that, or in response to the event not needing to be sent, the processing device checks 612 if the tilt sensor processing needs to be started. If yes, the tilt sensor debounce process is started 614. After that, or in response to the tilt sensor processing not needing to start, the processing device checks 616 if a tilt switch event needs to be sent. If yes, the tilt switch is updated and the event flags are cleared 618. After that, or in response to the tilt switch event not needing to be sent, the processing device checks 620 if the accelerometer processing needs to be started. If yes, the accelerometer filter process is started 622. After that, or if the accelerometer processing does not need to be started, the processing device determines 624 whether an accelerometer event needs to be sent. If yes, the processing device starts the accelerometer update and clears event flags 626. After that, or if an accelerometer event does not need to be sent, the processing device determines 628 if the switch device has been actuated. If yes, the processing device starts 630 the switch test event or the learn event. After that, or if the switch device has not been actuated, the processing device determines 632 whether a character has been received from the communication processor. If no, the processing device determines 634 if the processing flag is set and, if it is, the processing device sends 636 the next transmit state message. After that, or if the processing flag is not set, the process is sent back to start up at loop B. If a character is received from the communication processor, the processing device processes 638 the character. If the processing device does not reach 640 the end of the message, the process is sent back to start up at loop B. If the end of the message is processed, the processing device determines 642 whether the message should be flagged for transmission. If no, the process is sent back to start up at loop B. If yes, the processing device sets 644 the transmit flag and the process is sent back to start up at loop B.
As discussed above, the control device 30 can be configured to communicate with the mobile communication device 215. This relationship can be utilized by a user to control operation of the control device 30 and the barrier sensor device 10. More specifically, after analysis of the position and movement data, if the control device 30 determines that there is an issue or potential issue with the barrier operator system, the control device can send a service signal to the mobile device 215. The control device 30 can also be configured to send a “normal” operation signal to the mobile device 215 to update a user of the barrier system that everything is operating normally. In one example, the signals sent to the mobile device 215 can include: “Normal Operation”, “Strained Garage Door Operation: Recommend Service Review” and “Garage Door/Operator Requires Service Attention As Soon As Possible”. Additionally, the user can instruct the control device 30 with the mobile device 215 to update parameters and configure the barrier sensor device 10.
Data Analysis Examples
Analysis of the data collected by the barrier sensor device 10 will now be discussed with respect to
In one specific example, the control device, or a server device in communication with the control device 10, can utilize a barrier open time to, the time to move the barrier 16 from a closed position to an open position, and a barrier close time tc, the time to move the barrier 16 from an open position to a closed position, to monitor whether the barrier operator 14 is experiencing strain, whether from a mechanical issue with the operator itself, the guiderails, or the counter-balance mechanism.
More specifically, in one approach, the control device utilizes a ratio of the barrier open time over the barrier close time. Because a properly balanced door and ideal guidance structure provides a barrier with smooth and consistent operation, an acceptable range or value for the ratio can be determined. Once a baseline acceptable range or value is established, subsequent measured values exceeding the acceptable value is a result of added operation time created by gravity and friction in some manner. Accordingly, a specific barrier's ratio values over time can provide a trend line that can track a prediction to failure. If desired, the control device can consider a set of factors for each operation when building a moving average of a barrier system or a norm for a plurality of barrier systems to revise or classify the collected data. These factors can include one or more of: door metrics (such as width, height, material, etc.), weather, number of total operations, and the like. For example, the data can be adjusted or annotated to allow higher strain for relatively larger barriers, such as a higher strain for two car doors v. one car doors. In another example, the control device 30 can access or receive local weather conditions to adjust or annotate data to allow for higher strain for windy or humid conditions. In yet another example, the data can be adjusted or annotated to allow for higher strain along with the increasing number or operations performed by a barrier operator.
In an ideal environment movable barrier environment, the ratio of to/tc would be 1. Any amount over 1, therefore, can be viewed as an increment of the optimal efficiency of operation and can be expressed as 1+Y. In this equation, Y is a stress value accounting for the extra time introduced by gravity and friction in excess of normal operation.
In one example, a “normal” barrier operator system, including a barrier operator, barrier, guiderails, and counter-balance mechanism, installed according to the instructions in a garage-type environment was compared to a similarly-installed “strained” barrier operator system strained with 10 lbs. of extra weight, which simulates any of the strains on such a system. The test ran the normal system through 10 cycles of opening and closing. While the range of specific operations was inconsistent, 1.0021755-1.0321873, averaging the ratio values of these 10 cycles provided a normal or target operation average of 1.016, with an average of the Y values, Z, being 0.016. The test then ran the strained system through 7 cycles of opening and closing, the value being less than 10 because the barrier operator overheated. The range of 1.0159305-1.0634328 for the strained system provided a strained average of 1.032, with a Z value of 0.032. Accordingly, the strained door had a Z value about two times the Z value of the normal door. The control device 30, for example, can be configured to generate and send the service signal in response to determining that a measured Y value exceeds the target operation data by 2 or more times.
Due to the inconsistencies in the ratio from operation to operation, a barrier system can more accurately be analyzed when a rolling average thereof is viewed over a series of operations, such as 5, 10, 20, or other number of previous operations. Moreover, by segmenting increased values of Z, the control device 30 can track the increased values over time.
In the above example, a threshold of 70% over the normal Z value was determined to provide an indication of strained when viewed over a series of operations. More specifically, deviations of each operation from the rolling average can be calculated and compared to the target operation data.
By one approach, the target operation data is the Z value of the rolling average. In the above example, only one of the ten “normal” operations produced a Y value more than 70% of the “normal” Z value. In comparison, five of the seven “strained” operations produced a Y value more than 70% of the “normal” Z value. While 70% was utilized in this example, other values can also be utilized to compare newly obtained data to “normal” or benchmark data. Further, the threshold can be fine-tuned by analyzing a plurality of door operators' data. Thus, the control device 30 can be configured to generate and send the service signal in response to determining that a preset number, such as 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90%, or 100%, of the measured operations exceed the threshold.
The data can be analyzed in a number of ways. In a first example, the control device 30 can simply compare measured Y values to the rolling average Z. Upon a preset number of Y values within a range being greater than a threshold percentage of Z, the control device 30 can generate the service signal and transmit the signal to one of the peripheral devices with which it is in communication, such as the mobile device 215.
A second approach utilizes a first-in, first-out (FIFO) data evaluation process so that the barrier system, and the Y value thereof, can be viewed over the most recent series of operations, such as the previous 5, 10, 20, or more operations. This approach can also be utilized when data storage is limited. Moreover, benchmark or normal operation values can also be stored, and the FIFO values can be compared against these benchmark values. This provides added protection because a rolling average can increase slightly over time and eventually reach a breaking point. Alternatively, an acceptable range or value for Y can be provided to the control device 30 and the barrier values compared with this acceptable range or value. For example, a database of data can be compiled from a plurality of barrier operator systems to determine the acceptable range or value.
A third approach includes providing a “diagnostic mode” functionality for the barrier sensor device 10 and the control device 30. This diagnostic mode would allow a dealer or consumer to put the barrier sensor device 10 into the “diagnostic mode” and run a series of open and close commands, such as 5, 10, 20, or the like, and have the control device 30 analyze the data to compare to a database of acceptable performance. As such, the control device would not have to store operational data. Instead, the analysis would be triggered on command from time to time.
In addition, an absolute value for Y can be provided to the control device 30. The Y absolute value would correspond to a value where it is clear that barrier operation is outside of any recommended tolerance. For example, a user can adjust barrier force to compensate for a poor operating door. In order to avoid this scenario, the barrier sensor device 10 can include a “door operation verification process” mode that is configured to operate upon installation. This mode can include running a series of opening and closing operations and collecting measurements therefrom. These measurements can then be compared to the Y absolute value by the control device 30 to ensure that the barrier system is operating in an acceptable tolerance range before completing installation.
Those skilled in the art will recognize that a wide variety of modifications, alterations, and combinations can be made with respect to the above described embodiments without departing from the scope of the invention. For example, although the barrier sensor device and control device are described largely in the context of a garage in use with a garage door opener, such devices can be applied in other barrier operator contexts, such as gate operators and the like. Moreover, the retro-fit features described herein can be incorporated into a movable barrier operator. Such modifications, alterations, and combinations are to be viewed as being within the ambit of the inventive concept.
Number | Name | Date | Kind |
---|---|---|---|
4175431 | DeTournay | Nov 1979 | A |
4583081 | Schmitz | Apr 1986 | A |
5193506 | Ironside | Mar 1993 | A |
5402105 | Doyle | Mar 1995 | A |
5402108 | Tabin | Mar 1995 | A |
5412297 | Clark | May 1995 | A |
6543583 | Lence Barreiro | Apr 2003 | B1 |
6597291 | Tsui | Jul 2003 | B2 |
6667591 | Mullet | Dec 2003 | B2 |
6724316 | Addy | Apr 2004 | B2 |
6998977 | Gregori | Feb 2006 | B2 |
7017302 | Brookbank | Mar 2006 | B2 |
7017312 | Mueller | Mar 2006 | B1 |
7113090 | Saylor | Sep 2006 | B1 |
7113091 | Script | Sep 2006 | B2 |
7260917 | Brookbank | Aug 2007 | B2 |
7263802 | Fitzgibbon | Sep 2007 | B2 |
7493726 | Fitzgibbon | Feb 2009 | B2 |
7554445 | Script | Jun 2009 | B2 |
7592767 | Rodriguez | Sep 2009 | B2 |
7679301 | Gregori | Mar 2010 | B2 |
7689293 | Weik, III et al. | Mar 2010 | B2 |
7729807 | Guillemot | Jun 2010 | B2 |
8179275 | Jankovsky | May 2012 | B2 |
8384557 | Gunton | Feb 2013 | B2 |
20030071739 | Addy | Apr 2003 | A1 |
20050022451 | Fitzgibbon | Feb 2005 | A1 |
20050253710 | Eskildsen | Nov 2005 | A1 |
20060220834 | Maeng | Oct 2006 | A1 |
20070000622 | Reed | Jan 2007 | A1 |
20100019916 | Jankovsky | Jan 2010 | A1 |
20100032332 | Davis | Feb 2010 | A1 |
20130277437 | Longyear | Oct 2013 | A1 |
20130290191 | Dischamp | Oct 2013 | A1 |
Entry |
---|
http://www.liftmaster.com/lmcv2/pages/productmodeldetail.aspx?modelId=9570; showing product available as soon as Aug. 25, 2011. |
http://www.liftmaster.com/lmcv2/pages/productmodeldetail.aspx?modelid—9571; showing product available as soon as Mar. 17, 2011. |
Number | Date | Country | |
---|---|---|---|
20150077219 A1 | Mar 2015 | US |