Patent Grant
11610444
This disclosure relates generally to movable barrier operator systems having imminent motion notification apparatuses, more specifically, to movable barrier operator systems having selectively operable imminent motion notification apparatuses.
Movable barrier operators for controlling various types of barriers such as garage doors, gates, and the like are well known in the art. Some users operate these movable barrier operators using a local remote control, such as a handheld transmitter, to send a command message to open or close a movable barrier. Movable barrier operators may also receive command messages from a remote server computer via the internet in response to receiving a state change request from a remote device to allow for remote operation by a user. For example, a user may control a movable barrier operator through a website accessed by a computing device or via an application installed on the user's smartphone.
When a user operates a movable barrier operator using a remote device via a network, such as the internet, the operation is typically classified as an unattended operation. Given the potential distance between the user operating a movable barrier operator through a remote device and the movable barrier itself, the user may be unaware of any individuals or pets located near the movable barrier prior to an open or close operation. In such systems, an unattended operation initiated by a remote device includes an imminent motion notification apparatus of the movable barrier operator outputting an imminent motion notification during a delay in operation, and the movable barrier operator moving the movable barrier after expiration of the delay. The imminent motion notification may be at least one of a flashing light and a sound alert to warn nearby individuals that the movable barrier will open or close.
Additionally, if a user operates a movable barrier using a local transmitter, the operation is classified as an attended operation which does not entail an imminent motion notification. Given the typically short radio range of a local transmitter, an imminent motion notification is generally thought to be unnecessary because the user is likely in view of the movable barrier when actuating the transmitter.
However, such methods do not account for the possibility that a user may operate the movable barrier operator when the user is near the movable barrier using a remote device via a network, which would typically require an imminent motion notification. For example, a user may attempt to open or close a garage door using a smartphone or vehicle infotainment system while in a driveway, or inside the associated garage. In these situations, the movable barrier operator system would automatically classify the operation as an unattended close (because the request to open or close the movable barrier was received via a network) such that one or more of delayed operation of the movable barrier operator, flashing a light, and generating a sound alert occur, which may result in frustration by or inconvenience to a user because the light and/or sound notification is not required.
Further, a delivery associate may attempt to deliver a package intended for the user within a user's garage using a portable electronic delivery device (e.g., the delivery associate's phone or tablet), but the request to move the movable barrier is likewise received via the network and typically classified as an unattended close. As a result, the request to access the garage to deliver the package would cause an imminent motion notification, thus requiring the delivery associate to wait for expiration of the delay and/or the notification to finish thereby increasing the amount of time to deliver the package.
Elements in 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 to improve understanding of various embodiments of the present teachings. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present teachings. Certain actions and/or operations 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 intended to be limiting.
Referring now to the drawings, and more particularly
The communication circuitry 22 (see
The remote controls 44 may communicate directly with the movable barrier operator 12, such as with radio frequency signals as described above. Additionally or alternatively, one or more of the remote controls 44 may be configured to communicate with the movable barrier operator 12 via a wired approach (see, for example, wall control keypad 50 shown in
The movable barrier operator 12 may additionally be configured to communicate with one or more peripheral devices. For example, the communication circuitry 22 of the movable barrier operator 12 may include various wired or wireless connections to communicate with other devices, and the communication circuitry 22 may be configured to receive information from the one or more sensors 27 associated with the movable barrier 12 such as the optical sensor 26 (e.g., the optical emitter 28 and optical detector 30 in
During installation of the movable barrier operator 12, a user may electronically pair the user's portable electronic device 46 to the movable barrier operator 12 to facilitate an initial setup procedure. The initial setup procedure may include the user device 46 communicating network credentials to the communication circuitry 22 of the movable barrier operator 12, and the controller 24 storing the credentials in a memory 25, such that the movable barrier operator 12 may be configured to wirelessly communicate via, for example, the network 56 over the internet. For example, the credentials may include a local Wi-Fi network name and password. So configured, the movable barrier operator 12 may be configured to wirelessly communicate with the user device 46 and to receive state change commands from the remote server computer 58 via the network 56.
Regarding
Upon the movable barrier operator 12 receiving a state change command from the remote server computer 58, the imminent motion notification apparatus 14 is typically configured to provide an imminent motion notification that includes a visual alert, a sound alert, a partial movement of the barrier, or a combination thereof, followed by or concurrent with delayed movement of the movable barrier 18. In one embodiment, the controller 24 of the movable barrier operator 12 initiates a timer to delay operation of the motor 20 for a short period of time upon receiving the state change command from the server computer 58, for example, five seconds or more before a change of state of the movable barrier 18. Additionally, the imminent motion notification apparatus 14 may include an acoustic transducer such as a speaker 15 of the movable barrier operator 12 for emitting an audible alert for a short period of time, for example, five seconds or more before a change of state of the movable barrier 18. For example, the audible alert may include a continuous high-pitched tone, an intermittent beeping, a pre-recorded message, or the like, that may be heard by nearby individuals. The imminent motion notification apparatus 14 may include an overhead light 60 of the movable barrier operator 12 and the imminent motion notification apparatus 14 provides a visual alert by illuminating the overhead light 60 of the movable barrier operator 12. For example, the visual alert may include flashing or strobing the overhead light 60 for a short period of time, for example, five seconds or more before a change of state of the movable barrier 18. So configured, the imminent motion notification apparatus 14 provides an imminent motion notification to alert individuals near the movable barrier 18 prior to a change of state operation.
Regarding
As provided herein, the remote server computer 58 communicates different types of state change commands for causing operation, or inhibiting operation, of the imminent motion notification apparatus 14, based at least in part on a determination of whether a sensor check or inspection has been performed for the movable barrier operator system 10. For example, if a sensor check has been completed, the remote server computer 58 is configured to communicate an attended state change command (as opposed to an unattended state change command), which is indicative of various features of the movable barrier operator system 10 having been tested and are operating correctly, to the movable barrier operator 12 to inhibit or bypass operation of the imminent motion notification apparatus 14 (e.g., by not effecting operation of some or all aspects of an imminent motion notification), as described in further detail below, so as to reduce potential frustration caused by the delay associated with an imminent motion notification. In some forms, the determination of whether a sensor check or inspection has been performed for the movable barrier operator system may be executed by one or a combination of the remote server computer 58, the movable barrier operator 12, and the remote control 44.
As shown in
The processor 64 of the remote server computer 58 may be configured to execute computer-readable instructions stored on the memory 66. The network interface 62 is configured to communicate with the various client applications or devices that constitute the movable barrier operator system 10 such as the movable barrier operator 12 and the remote controls 44 via the network 56, such as the internet or a local area network, and may also receive a state change request from some remote controls 44, such as the portable electronic device 46. When the network interface 62 receives a state change request from one of the remote controls 44 associated with a particular movable barrier operator 12, the processor 64 is configured to cause the network interface 62 to communicate a message or signal regarding the state change command to the movable barrier operator 12 of that system 10.
The processor 64 may be configured to cause communication of different types of state change commands for effecting different operations of the movable barrier operator system 10. For example, the processor 64 may be configured to cause the network interface 62 to communicate either an attended state change command or an unattended state change command based at least in part on a determination of whether a sensor check has been completed to test functionality and operation of various sensors associated with a specific movable barrier operator system. An example sensor check method to be performed (including various example testing protocols and prompts and/or instructions thereof) is described in further detail hereinafter with respect to
Upon a determination by the processor 64 that a sensor check was performed successfully for a specific movable barrier operator 12, as noted by the indication such as a flag set on the user account stored in the memory 66 (or alternatively, as indicated by a signal received from the remote control 44 and/or movable barrier operator 12 indicating that the sensor check was performed successfully), the processor 64 causes the network interface 62 to communicate an attended state change command configured to effect a change in state of the movable barrier 18 without causing operation of the imminent motion notification apparatus 14 in response to receiving a state change request. Otherwise, the processor 64 after checking the memory 66 and determining an absence (or staleness—indicative of the sensor check not being performed within a threshold period of time) of the indication/flag causes communication of an unattended state change command configured to effect a change in state of the movable barrier 18 in combination with operation of the moving-barrier imminent motion notification apparatus 14 to alert individuals proximate the movable barrier.
Additionally or alternatively, in an embodiment where the indication that the sensor check has been completed is stored in the memory of the remote control 44, a processor of the remote control 44 may be configured to determine whether the sensor check has been performed successfully for a specific movable barrier operator 12, as noted by the indication stored in the memory, and may be configured to communicate, in connection with a state change command, a signal to the remote server computer 58 and/or the movable barrier operator 12 indicating that the sensor check either has or has not been performed. In some forms, a signal indicating that the sensor check has been performed may be configured to inhibit operation of the moving-barrier imminent motion notification apparatus 14 and a signal indicating that the sensor check has not been performed may be configured to cause operation of the moving-barrier imminent motion notification apparatus 14 in connection with a change of state of the movable barrier.
In still further forms where the indication that the sensor check has been completed is stored in the memory 25 of the movable barrier operator 12, the remote server computer 58 and/or the remote control 44 may be configured to communicate a state change command to the movable barrier operator 12 and the controller 24 may be configured to determine whether the sensor check has been performed successfully for that movable barrier operator 12. In such embodiments, upon a determination that the sensor check has been performed successfully based on the indication stored in the memory 25, the controller 24 may refrain from causing operation of an imminent motion notification, and upon a determination that the sensor check has not been performed successfully, the controller 24 may cause operation of an imminent motion notification in connection with a change of state of the movable barrier.
So configured, a user or owner of the movable barrier operator system 10 may be permitted to inhibit, prevent, or bypass operation of the imminent motion notification apparatus 14 in connection with movement of the movable barrier 18 based at least in part on the sensor check being performed to test and ensure sensors associated with the movable barrier operating system 10 (e.g., optical sensor 26 and force reversal sensor 31) are properly functioning. If the sensors associated with the movable barrier operator system 10 are confirmed to be functioning properly, the imminent motion notification apparatus 14 may not be actuated when using a remote control 44 that communicates directly and/or indirectly with the movable barrier operator 12 via the remote server computer 58 such that the user is not required to wait for the delay associated with an imminent motion notification when the movable barrier 18 is opened or closed.
Referring again to
The optical sensor 26 is configured to detect the presence of potential obstructions in the path of travel of the movable barrier 18 between the open position and the closed position. For example, in an embodiment including the optical emitter 28 and optical detector 30, an obstruction may be detected based at least in part on the optical detector 30 failing to detect a light beam emitted from the optical emitter 28 across an opening 19 of a garage 16 (see
Similarly, the force reversal sensor 31 is configured to detect a force applied to the movable barrier 18 during movement thereof to determine if an obstruction is present in the path of travel. For example, the force sensor 31 may be integral with the movable barrier operator 12 and configured to detect a motor load of the motor 20 by measuring a mechanical and/or electrical parameter or characteristic of the motor 20 such as one or more of output torque, motor shaft speed/RPM, the amount of current or power being consumed. An obstruction being contacted by the movable barrier 18 during an operation may correspondingly increase the motor load, and if a motor load detected by the force reversal sensor 31 exceeds a threshold amount, the controller 24 of the movable barrier operator 12 may be configured to stop and/or reverse movement of the movable barrier 18. In alternative forms, the force reversal sensor 31 may be a pressure actuated switch or other mechanical sensor positioned, for example, at a lower edge of the movable barrier 18. Furthermore, in some instances the force sensor 31 may not directly detect a force that is being experienced by the motor 20 or by the movable barrier 18. That is, the force sensor 31 may be alternatively implemented substantially as software, firmware or other computer-readable instructions that may be executed or otherwise performed by the controller 24 in order to indirectly determine force(s) based on one or more electrical, mechanical, and historical factors or parameters that may be measured, calculated or inferred.
Referring now to
Specifically, another example movable barrier operator system 10′ is illustrated that is similar to movable barrier operator system 10 such that any differences will be described hereinafter. Structures of the movable barrier operator system 10′ that are similar to structures of the movable barrier operator system 10 are designated with similar reference numerals. The movable barrier operator system 10′ is illustrated including a movable barrier operator 12′ having a motor 20′, communication circuitry 22′, and a controller 24′. In addition, the movable barrier operator system 10′ includes an operator enhancement device 92 having a controller 93, communication circuitry 94, and a memory 95. The communication circuitry 94 of the operator enhancement device 92 may permit the operator enhancement device 92 to communicate over a network, such as the internet. The communication circuitry 22′ of the movable barrier operator 12′ is configured to receive signals output by the operator enhancement device 92, and in some forms, the movable barrier operator 12′ may be wired or wirelessly coupled to the operator enhancement device 92 to communicate various operating conditions of the movable barrier operator 12′ thereto. For example, the movable barrier operator 12′ may be configured to communicate signals indicating whether the motor 20′ is operating, whether an overhead light is on, among other operating conditions.
The movable operator system 10′ also includes an imminent motion notification apparatus 14′ that is configured to output an imminent motion notification similar to the imminent motion notification apparatus 14. The imminent motion notification apparatus 14′ of
The movable barrier operator 12′ includes communication circuitry 22′ to receive local communications from remote controls 44 such as a local keypad 50 and an RF transmitter 52 for changing a state of a movable barrier 18′. However, the communication circuitry 22′ is not configured for communicating with the remote server computer 58 and receiving a state change command therefrom via a network such as the internet. Instead, the remote server computer 58 may communicate a state change command to the operator enhancement device 92, and the operator enhancement device 92 may communicate a radio frequency signal to operate the movable barrier operator 12′ upon the operator enhancement device 92 receiving the state change command.
For example, upon the operator enhancement device 92 receiving a state change command from the remote server computer 58, the operator enhancement device 92 may send a signal, (e.g., a 300 MHz on-off keying signal) to the movable barrier operator 12′ that is configured to cause the motor 20′ of the movable barrier operator 12′ to change a state of the movable barrier 18′. So configured, the operator enhancement device 92 permits the movable barrier operator 12′ that is otherwise not able to communicate via a network to indirectly receive remote state change commands from the remote server computer 58.
The memory 95 of the operator enhancement device 92 may be configured to store data or information concerning the operation(s) of the movable barrier operator 12′, and additionally may be configured to store an indication that a sensor check has been completed as described in further detail herein. For example, the operator enhancement device 92 may store a list of known transmitters or remote controls 44 in the memory 95 or may store other information such as information from sensors associated with the movable barrier operator system 10′ as needed. Such information may likewise be communicated through the network 56 to the remote server computer 58.
In the illustrated form, a position sensor 33′ is communicatively coupled to the operator enhancement device 14′ and is configured to detect whether the movable barrier 18′ is in an open position or a closed position. For example, the position sensor 33′ may be a tilt switch, gyroscope, or accelerometer coupled to or associated with the movable barrier 18′ to detect a position thereof. Alternatively, the position sensor 33′ may be a camera configured to detect images of the movable barrier 18′ and/or opening 19 for determining if the movable barrier 18′ is open or closed. So configured, the operator enhancement device 14′ may be configured to determine, based on the output from the position sensor 33′, whether the movable barrier operator 12′ has opened or closed the barrier according to a radio frequency signal output from the operator enhancement device 14′ upon receipt of a state change command from the remote server computer 58.
In some embodiments, an optical sensor 26′ and a force reversal sensor 31′ may additionally or alternatively be communicatively coupled to the operator enhancement device 92 such that an indication that a sensor check has been completed may be stored in the memory 95 and/or the information received from the sensors 26′, 31′, such as signals indicating a detected obstruction, may nonetheless be wirelessly communicated to the remote server computer 58 for use in connection with the sensor check methods described hereinafter.
Referring now to
In one aspect, the steps of the testing protocols 100, 200, 300 may be administered or otherwise facilitated via a mobile application 400 (see
Referring again to
The testing protocol 100 of the sensor check is configured to determine whether the optical sensor 26, such as the optical emitter 28 and optical detector 30, is properly installed such as being positioned at a proper height with respect to a floor of the garage 16 in which the movable barrier 18 is installed. In one form, the optical emitter 28 and optical detector 30 are recommended to be placed at about six inches above the floor proximate the path of travel of the movable barrier 18, and the testing protocol 100 is configured to confirm that the optical emitter and detector 28, 30 are placed at the recommended height. To do so, the application 400 may provide an instruction to the user via the user interface 76 of the user device 46 to confirm that the optical emitter and detector 28, 30 are positioned at the proper height (communication 102). The user interface 76 may present an option such as a “confirm” button for the user to press after manually measuring the height at which the emitter and detector 28, 30 are positioned.
Additionally or alternatively, the application 400 may entail the user employing the user device 46 and/or the application 400 to take one or more pictures of the emitter and detector 28, 30 as installed in the garage 16 to be used for determining if the emitter and detector 28, 30 are positioned at the proper height. Moreover, the testing protocol 100 may entail an electronic measurement (e.g., facilitated by another application or functional module such as the iOS “Measure” application) of the optical emitter and detector 28, 30 to verify their installation at the recommended height. Alternatively, a camera 35 (see
The testing protocol 200 of the sensor check is configured to determine whether the optical emitter and detector 28, 30 are functioning properly. That is, the testing protocol 200 is configured to determine if the optical emitter 28 is properly emitting a light beam and the optical detector 30 is properly detecting that light beam during ordinary operation. As an initial step, the application 400 may provide an instruction or prompt to the user via the user interface 76 of the user device 46 to place an object six inches or taller between the optical emitter and detector 28, 30 and within a path of travel of the movable barrier 18 (communication 202). Once finished, the user may manually confirm in the app that the object has been placed in the desired position as prompted. Additionally or alternatively, the camera 35 (see
Once the object is confirmed to be placed in the desired position (either manually by the user confirming in the app, or as detected by a camera 35 associated with the movable barrier operator system 10) (communication 204), a state change request may be communicated to attempt to close the movable barrier 18 (communication 206). The state change request may be manually communicated by the user using, for example, the portable electronic device 46, or may be automatically communicated to remote server computer 58. If the emitter and detector 28, 30 are functioning properly, an obstruction will be detected and the movable barrier 18 will either reverse after beginning to close or the movable barrier operator 12 will not actuate to close the barrier 18. Similarly, upon the movable barrier operator 12 sensing the obstruction, the communication circuitry 22 of the movable barrier operator 12 may communicate a confirmation indicating that the optical emitter 28 and the optical detector 30 are functioning properly (communication 208) to the remote server computer 58 (e.g., through the application 400 on the portable electronic device 46). In an alternative implementation the user is prompted or instructed to move an object (e.g., a wood two-by-four, the user's hand/arm or foot/leg, etc.) between the emitter and detector to momentarily interrupt the optical beam during closure of the movable barrier, in response to which the movable barrier operator 12 is configured to reverse movement of the movable barrier and communicate the perceived momentary obstruction to the remote server computer 58.
Another testing protocol 300 of the sensor check is configured to determine whether the force reversal sensor 31 is functioning properly. As an initial step, the application 400 may provide an instruction or prompt to the user via the user interface 76 of the user device 46 to place an object within a path of travel of the movable barrier 18 (communication 302). In one example, the application 400 may instruct the user to place a two-by-four plank of wood or other common object on the ground in the path of travel. Once the object is confirmed to be placed in the desired position (either by the user, or as detected by the camera 35 associated with the movable barrier operator system 10 as described in further detail above) (communication 304), a state change request may be communicated to attempt to close the movable barrier 18 (communication 306). The state change request may be manually communicated by the user using, for example, the portable electronic device 46, or may be automatically communicated via the application 400. The movable barrier 18 will begin to move from the open position to the closed position until contacting the object. As the movable barrier 18 contacts the object, the motor load of the motor 20 will increase and be detected by the force reversal sensor 31. If the force reversal sensor 31 is functioning properly, upon the motor load exceeding a predetermined threshold, the controller 24 of the movable barrier operator 12 will cause the motor 20 to reverse the movable barrier 18 and return the movable barrier 18 to the open position. The communication circuitry 22 of the movable barrier operator 12 may then communicate a confirmation indicating that the force reversal sensor 31 is functioning properly (communication 308) to the remote server computer 58 (e.g., through the application 400 on the portable electronic device 46).
Various other sensors may also be included with the movable barrier operator system 10 and such sensors may be tested in a similar manner using testing protocols administered at least in part by instructions and/or prompts provided by the application 400. For instance, in an embodiment where the optical sensor 26 includes a camera, the application 400 may provide an instruction to guide a user through a process of testing to ensure the camera is functioning as intended such as the garage door opening 19 being within the field of view of the camera. Additionally or alternatively, the sensors 27 such as the force reversal sensor 31 and the optical sensor 26 may be tested to detect other operating conditions thereof, such as detecting if sufficient power is being supplied to the sensors.
Although the testing protocols shown in
The portable electronic device 46 and the movable barrier operator 12, either alone or in combination with one another, may be configured to communicate the confirmation to the remote server computer 58 indicating proper functionality of the sensors 26, 31 associated with the movable barrier operator system 10 either during or after the sensor check has been completed. For example, in one form, the movable barrier operator 12 may communicate a confirmation to the remote server computer 58, and upon receipt of the confirmation, the remote server computer 58 may be configured to communicate an attended state change command to the movable barrier operator 12 when a subsequent state change request is received. In another form, the movable barrier operator 12 may communicate the confirmation to the user's portable electronic device 46, and the device 46 may communicate that confirmation to the remote server computer 58 via the communication circuitry 72. Upon receiving the confirmation indicative of the sensor check being completed, the remote server computer 58 may be configured to communicate an attended state change command to the movable barrier operator 12 when a subsequent state change request is received, and the attended state change command is configured to inhibit operation of the imminent motion notification apparatus 14 in connection with a change of state of the movable barrier 18. In other forms, the portable electronic device 46 and/or the movable barrier operator 12 may store an indication in a respective memory thereof that the sensor check has been performed as an alternative or in addition to communication of the confirmation to the remote server computer 58.
In some embodiments, such as the movable barrier operator system 10′ shown in
In some forms, the remote server computer 58, the remote control 44, the movable barrier operator 12, or another computing device may be configured to store data or other information indicating that the user has performed a sensor check by completing the testing protocols for a specific movable barrier operator system in a memory, such as the memory 66 of the remote server computer 58. For example, the remote server computer 58 may store an indication such as a “flag” associated with a user account in the memory 66, and presence of the flag for the user account is used to determine whether or not a sensor check has been performed for a specific movable barrier operator system. Additionally or alternatively, the flag associated with the user account may be set in the memory 66 of the remote server computer 58 and the application 400 installed on the user device 46, or the flag may also be set in a memory of the movable barrier operator 12. In an embodiment where the flag is set in the memory 66 of the remote server computer 58, upon receiving a state change request from a remote control 44, the processor 64 of the remote server computer 58 may be configured to determine whether a flag has been set for a user account associated with the movable barrier operator system to be operated via the state change request, and if so, causes communication of an attended state change command. Otherwise, if determined that a flag has not been set, the remote server computer 58 communicates an unattended state change command.
In some embodiments, the indication that the sensor check has been performed for a specific movable barrier operator system, such as the flag, may only be stored in the memory 66 (or other memory in which the indication is stored) temporarily. The remote server computer 58 or another device in which the indication is stored may further be configured to automatically remove the indication that a sensor check has been performed from a specific user's account based on a number of different predetermined conditions. Alternatively, the indication may be removed manually by the user or an administrator having access to the user account. Once the indication has been removed, the user is required to re-perform the sensor check to compensate for changes that may occur to the sensors over time. So configured, the user may be prompted to re-perform the sensor checks on a periodic basis.
In one embodiment, the processor 64 of the remote server computer 58 may be configured to automatically remove the indication that the sensor check has been performed after a predetermined period of time, and the user must then re-perform the sensor check if the user desires to inhibit use of the imminent motion notification apparatus 14 in connection with a change of state of the movable barrier 18. In one example, an indication associated with a user account may be stored in the memory 66 including an associated time stamp or date stamp identifying when the indication was set (e.g., see
In another example, the processor 64 of the remote server computer 58 may be configured to automatically remove the data indicating that the sensor check has been performed based at least in part on weather conditions associated with the location where a specific movable barrier operator system 10 is located. For example, in areas where there may be an especially harsh winter or other frequently extreme weather conditions, it may be beneficial to request of the user to re-perform the sensor check including the testing protocols 100, 200 and 300 when specific weather conditions have been detected to ensure proper continued operation of each of the sensors 26, 31. Such weather condition information may be detected using one or more sensors (e.g., a temperature sensor) communicatively coupled to the movable barrier operator system 10 or may alternatively be retrieved from a weather reporting service by the server computer 58.
In yet another example, the processor 64 of the remote server computer 58 may be configured to automatically remove the indication that the sensor check has been performed based at least in part on a number of obstructions detected by the sensors 26, 31 associated with the movable barrier operator system 10 exceeding a threshold number. In one form, the movable barrier operator 12 may be configured to communicate information to the remote server computer 58 indicating that an obstruction has been detected by one or more sensors 26, 31. In one example, if more than five obstructions are detected by either the optical sensor 26 or the force reversal sensor 31 in a specified time period (e.g., a day), it may be assumed that obstructions may frequently occur for the respective movable barrier operator system 10 and it would be encouraged to perform sensor checks more often so that operation of the sensors 26, 31 is more frequently assessed.
Although the remote server computer 58 may be automatically configured to communicate attended state change commands to the movable barrier operator 12 once the sensor check has been completed, the processor 58 may additionally be configured determine whether the user has manually enabled an “attended mode” via the application 400 on the portable electronic device 46. For example, once the sensor check including the testing protocols has been completed, and the sensors 26, 31 are determined to be functioning as intended, the user may be presented with an option in the user interface 76 to enable an “attended mode” to inhibit a portion of, or all of, the imminent motion notification provided by the imminent motion notification apparatus 14 when a state change command is received by the movable barrier operator 12 (see, e.g.,
Referring now to
In one aspect, the remote server computer 58 or other device may only be permitted to communicate an attended state change command to a specific movable barrier operator system if both a sensor check has been completed for the sensors of that movable barrier operator system and if the user has enabled the attended mode. With reference to the data structure of
In alternative forms where the indication and/or enabling of the attended mode has been stored in a memory of the remote control 44 or the movable barrier operator 12, the foregoing determinations may be performed by a respective processor of the remote control 44 or of the movable barrier operator 12 to determine whether to inhibit or cause operation of an imminent motion notification.
As discussed in further detail above, the data indicating that the sensor check has been completed (e.g., the flag stored in column 82 of the data structure 80 associated with the user's account) may be removed by the processor 64 of the remote server computer 58 or another device after a predetermined period of time. For example, the data structure 80 may include a column 83 including a date stamp identifying when the flag in column 82 was initially set, and the processor 64 may be configured to detect whether a predetermined amount of time has passed since the flag was set, thus indicating whether the set flag is stale and whether sensor check should be re-performed. In a similar manner, the processor 64 may be configured to automatically disable the attended mode for a user account based on one or more of the conditions described above. If the user desires to re-enable the attended mode, the user is required to re-perform the sensor check including the various testing protocols 100, 200, 300 to test the sensors 26, 31 before being permitted to re-select the attended mode in the application 400.
The determination by the remote server computer 58 of whether to communicate an attended or unattended command message may also be based at least in part on whether the remote control 44 communicating the state change request is determined to be located within a predetermined proximity of a location associated with the movable barrier operator system 10. For example, even though the sensor check has been completed and/or the user has enabled the attended mode feature, the remote server computer 58 may nonetheless be configured to communicate an unattended state change command to cause operation of the imminent motion notification apparatus 14 if the remote control 44 that the state change request is received from is not within a predetermined proximity of the movable barrier operator system 10. Such a predetermined proximity could be set by the entity operating the remote server computer 58 and may be set as a threshold distance, such as a radius of about fifty meters. If a determination indicates that the remote control 44 is within the predetermined proximity, the remote server computer 58 sends the attended state change command to the movable barrier operator 12. In some forms, the proximity determination may be performed by the processor 64 of the remote server computer 58, by a processor of the remote control 44 (e.g., processor 70 of the portable electronic device 46), and/or by the controller 24 of the movable barrier operator 12 and communicated to the remote server computer 58 for use in a determination of whether an attended or unattended state change command should be sent.
The proximity determination may be based on one or more of the following methods for obtaining proximity-related information of the remote control 44 communicating the state change request including, but not limited to, dead reckoning determinations, angle of arrival measurements, time of flight determinations, received signal strength indication (RSSI) thresholding, comparison of global navigation satellite system (GNSS) data such as global positioning satellite (GPS) data, analysis of data obtained via remote sensors (e.g., a camera configured to detect image data including physical characteristics of a user), LiDAR scanning, or a combination thereof. In addition, the proximity determination may be based on a determination of whether the remote control 44 sending the state change request is within a geofenced area associated with the movable barrier operator system 10, such as a geofence surrounding a driveway associated with a garage. Determining whether the remote control 44 is within a predetermined proximity to the movable barrier operator system 10 before communicating an attended state change command may be desirable in some applications.
In some forms, a determination of whether the remote control 44 is within the predetermined proximity to the movable barrier operator system 10 may be based on time-related factors and the remote server computer 58 may implement a time-based restriction as opposed to calculating a raw distance from the movable barrier operator system 10 or comparing GPS coordinates to a geofenced area such as described above. In other forms, the proximity determination already described may be used in connection with the time-based restrictions as now described to achieve a greater confidence that the user communicating the state change request is proximate the movable barrier. For example, the remote server computer 58 may be configured to determine if the remote control 44 is within a predetermined proximity based on a time interval measured since a prior state change request was received. For instance, a user may arrive home and communicate a state change request to open movable barrier 18 to park a vehicle in garage 16. Shortly thereafter, the user may communicate a subsequent state change request to close the movable barrier 18 (e.g., after the vehicle has been parked within the garage 16). Upon a determination by the processor 64 that the subsequent state change request was received before a threshold time limit is exceeded (e.g., about thirty seconds to about one minute), the remote server computer 58 may be permitted to communicate an attended state change command and inhibit operation of the imminent motion notification apparatus 14 based upon a likelihood that the user is still proximate the movable barrier 18.
In a similar manner, the remote server computer 58 may be permitted to communicate an attended state change command based on a measured amount of time a vehicle proximate the garage 16 has been turned on. In embodiments where the user's vehicle 17 (
The testing protocols 100, 200, 300 and sensor check provided herein may be useful for effecting delivery of certain items to the user via a delivery associate, such as an Amazon or UPS delivery person, who may be granted temporary access to a user's garage for securely delivering a package therein. In an example where the movable barrier 18 is a garage door and the movable barrier operator 12 is a garage door opener, the delivery associate may request access to the user's garage 16 to deliver a package therein using a portable electronic delivery device 47 (
Referring now to
In
In
In
In
In
Referring now to
The terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein. The word “or” when used herein shall be interpreted as having a disjunctive construction rather than a conjunctive construction unless otherwise specifically indicated. Further uses of singular terms such as “a,” and “an,” are intended to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms. It is intended that the phrase “at least one of” as used herein be interpreted in the disjunctive sense. For example, the phrase “at least one of A and B” is intended to encompass A, B, or both A and B.
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 instance, although the described embodiments include a garage having a garage door, various types of movable barrier systems can employ these teachings, for example, swinging gates, rolling gates, rising gates, and the like. It is intended for the present invention to cover all the modifications, alterations, and combinations which fall within the scope of the appended claims. Such modifications, alterations, and combinations are intended to be viewed as being within the ambit of the inventive concept.
This application claims the benefit of U.S. Provisional Patent App. No. 63/128,919 filed Dec. 22, 2020, which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6476732 | Stephan | Nov 2002 | B1 |
| 6856820 | Kolls | Feb 2005 | B1 |
| 7272497 | Koshiji | Sep 2007 | B2 |
| 7532965 | Robillard | May 2009 | B2 |
| 10837217 | Cate | Nov 2020 | B2 |
| 10873828 | Lau | Dec 2020 | B2 |
| 20030055557 | Dutta | Mar 2003 | A1 |
| Entry |
|---|
| LiftMaster—UL 325 Standards & Compliance; Safety & Security; https://www.liftmazster.cvom/about-liftmaster/safety 17 Pages, Dated Dec. 16, 2020. |
| Non-Patent Literature Document Disclosing YouTube Video entitled “How to do a Garage Door Safety Test” https://www.youtube.com/watch?v=Z31AB1ilygo; published May 3, 2013; 10 pages; Disclosing Screen Captures and Audio Transcription. |
| UL Standard for Safety for Door, Drapery, Gate, Louver, and Window Operators and Systems, UL 325 Fifth Edition, Dated Jun. 7, 2002; pp. 1-186. |
| Number | Date | Country | |
|---|---|---|---|
| 20220198857 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63128919 | Dec 2020 | US |
