Patent Grant
10488897
The present invention relates to fan devices, and more particularly, to methods and apparatus for controlling and/or powering devices using different interfaces, e.g., an Alternating Current (AC) Interface, an RF interface, and a Wifi interface.
Ceiling fans are often mounted in rooms to improve air circulation and/or provide cooling. In some cases lights are mounted on the fan. While the ability to separately control a fan motor and light are desirable, such control if implemented using standard wired switches requires separate switches for the light and the fan motor.
In many cases, fans are mounted where a ceiling light was previously located and thus while power, e.g., 120V, may be available at the location where the fan is being mounted connections to multiple switches may not be available. In such cases, the combined ceiling fan and light fixture may receive power via a single wall switch with the power being provided to both the light and fan motor at the same time. In order to allow separate control of the light and fan motor switches pull cords may be included in the fan assembly with one switch being used to control the light fixture and another being used to control the fan motor.
While the use of pull cord controls of a fan and light are common, they are not only unsightly but can pose potential safety issues. Dangling cords can accidently get caught on objects, people and/or even get entangled in the moving fan blades. With advancements in LED lighting it is often desirable to support variable lighting levels rather than a simple on/off light control. Similarly the ability to control the speed of a ceiling fan motor rather than simply turn the motor on and off can be desirable.
In the interest of energy efficiency it can be desirable to support fan and/or light control according to a schedule which takes into consideration calendared events, work schedules and/or other conditions so that a fan and/or light is not run needlessly when no one is around. To the extent that a schedule could be supported, it would be desirable if the schedule could be entered and implemented without the need for a wired wall controller to provide control signals via a wire to the fan and/or light unit since wires can be difficult and/or costly to run.
Additionally, known DC motor fan systems, e.g., fan systems using DC brushless motors, that are available experience problems when controlled over the same power run, e.g., when three fans are daisy chained together so that power is connected to a first fan and from the first fan to a second fan and then a third fan, the third fan typically does not operate properly it experiences being off kilter in time and speed on start up.
In view of the above it should be appreciated that there is a need for improved methods of controlling a fan and/or ceiling light. It would be desirable if at least some of the improved methods and/or apparatus could avoid the need for multiple wall switches wired separately to a fan and a light. While not necessary for all embodiments it would be desirable if fan and/or light control could support a wide range of functions such as fan speed, fan direction, and/or light intensity in addition to simple light and/or fan on/off operations.
In some cases in addition to being able to control a fan and/or light without the need for separate hardwired switches to the individual fan or light, it would be desirable if a safety shut off mechanism were supported. For example, it would be desirable if in at least some embodiments rather than relying on commands or controls to turn off a fan and/or light a safety mechanism was available to quickly disable the fan motor and/or light in the event of a safety concern. In at least some such cases it would be desirable if power to the fan and/or light unit could be fully cut off to quickly stop motor operation even in the event of erroneous control signals being sent to the fan and/or an error on a fan controller that is responsible for controlling the fan. In the case where a wall unit may include a controller which sends commands to one or more fan units it would be desirable if the safety mechanism could also disable the wall control unit's ability to send commands so that all portions of the fan system are reliably disabled.
In further view of the above, it should also be appreciated that there is a need new and/or improved fan systems that utilize DC motors, e.g., DC brushless motors, so that smooth control of fan operation in each of the DC motors can be achieved. Furthermore, there is a need for new and/or improved apparatus that can power and/or control DC brushless motors so as to provide smooth control of fan motor operation without use of an optical sensor, optical encoder, magnetic encoder, e.g., resolver or synchro, or Hall effect sensor in the motor control unit which add to the cost of the fan device and overall system.
Various embodiments are directed to solving one or more of the above referenced problems. Various fan system embodiments are directed to systems including one or more fan devices that utilize DC motors, e.g., DC brushless motors, that utilize control apparatus, e.g., circuits that provide smooth control of fan operation in each of the DC motors in the one or more fan devices of the system. Some embodiments are directed to power control circuits which convert AC power to DC power which is supplied to a DC brushless fan motor in a manner that provides smooth control of fan motor operation without the use of an optical sensor, optical encoder, magnetic encoder, e.g., resolver or synchro, or Hall effect sensor in the motor control unit.
Various embodiments are directed to apparatus for controlling fan system operation including one or more fan devices that include a DC fan motor and circuitry for powering and controlling the DC fan motor so that it provides smooth operation without being off kilter in time or speed when multiple fan devices powered from the same AC power supply line are started concurrently. An exemplary system includes one or more fan devices including a DC fan motor, an AC power interface circuit that provides AC filter power to a DC power supply circuit that provides power to the DC fan motor. The AC power interface circuit including: AC signal and ground input connections, an AC filtering circuit, and AC signal output connections. The DC fan motor may be brushless without an optical sensor and the AC filtering circuit may include: a varistor, a common mode choke, an X capacitor, and two Y capacitors.
Various embodiments are directed to use of an RF and WiFi control in the fan device to control fan status and speed and/or fan light on/off status and intensity. The fan device includes both an RF interface and a WiFi interface. The customer premises includes a WiFi router through which WiFi communications can be sent from a WiFi capable device, e.g., a cell phone, to control the fan device and its various functions. While WiFi control is via a WiFi router in the home, the control signals normally do not traverse the Internet or another external network. Accordingly, WiFi control is possible without the need for a connection to an external network or server. In addition to WiFi control, control of the fan device can be via an RF control device, e.g., a wall mounted controller. In some embodiments 120V power is supplied to the fan device via the wall mounted controller. While 120V power may be supplied via the wall controller, control signals from the wall mounted controller are transmitted using RF signals to the RF interface of the fan device. The RF interface uses a different frequency band than the frequency band used for WiFi signals sent to/from the WiFi router. In some embodiments the RF interface uses an unlicensed frequency spectrum which is different than that used for WiFi signals.
Since the RF and WiFi control signals need not pass over an external communications network as in the case of systems where commands must first be sent to a network server outside a customer premises and then sent from the network server to the device to be controlled, the fan device can be controlled either by the wall controller or a WiFi device even if a connection to the Internet or another external network is not available.
In some, but not necessarily all embodiments, the fan device reports its state and/or changes in state due to received commands to a server, e.g., located outside the customer premises. The communication with the external server may be, and sometimes is, via a WiFi router and Internet connection. The server logs the state information of one or more devices at each customer premises it is associated with. The server generates, e.g., automatically, a recommended normal schedule based on historical device state information including device on/off times, fan speed information and/or light intensity information. Machine learning and historical device state information may be, and sometimes is, used for generating the recommended schedule for a customer premises. The recommended normal control schedule is communicated to an individual, e.g., a customer at the customer premises to which the schedule relates. The communication of the proposed schedule may be, and sometimes is, from the server via the Internet and WiFi router at the customer premises to which the schedule relates. The customer can approve the recommended schedule and/or provide a revised normal schedule to be used by the server to control devices at the customer premises.
In addition to generating a normal control schedule for a customer premises, an away schedule to be used when a customer indicates that the customer premises is in an away state is generated. An away state corresponds to when the normal occupants of the customer premises are away from the customer premises. The away schedule is generated based on a random function so that devices will be turned on at somewhat randomized times making it difficult for a potential burglar to determine whether the devices are being controlled by an automated system or by a human present at the premises. In some embodiments historical device use information is taken into consideration when the server automatically generates the away schedule with the on/off times being somewhat random but remaining within a reasonable time, e.g., 30 minutes or an hour, of when the devices are turned on and off when a human is present.
While a user can control the devices while in the home via the RF controller or a WiFi controller without having to send commands outside the home, remote control of devices is also supported. A user can login to the control server and once authenticated is allowed to send control commands to devices at the home via the control server and the WiFi router. In this way a user can control devices while away from the home. In the case of commands sent via the server, the server can, and sometimes does, update device state information based on the commands sent from the server to the device to be controlled thereby eliminating the need for the device to report a state change to the server. While in some embodiments devices do not report state changes to the server which are in response to commands communicated by the server to the device being controlled, in other embodiments the devices being controlled, e.g., fan devices, routinely report a state change to the control server regardless of whether the command was from the server, wall controller or WiFi device in the home.
The customer to which a home corresponds can enable/disable use of a control schedule by the server. For example the user can send a signal to the control server to indicate that the normal control schedule should be used or the away schedule should be used or that no control schedule should be used. The signal may indicate automated control is to be set to off for the home, automated control should be on and, when the automated control is on whether an away state is indicated indicating that the away schedule should be used or that the premises is in a normal state and thus the normal schedule should be used.
An exemplary control method, in accordance with some embodiments, comprises: receiving, at a fan device including a radio frequency signal receiver and a WiFi interface, a first radio frequency (RF) control signal from a control unit, said fan device and said control unit being located at a customer premises; implementing, at the fan device, an operation in response to a first command communicated by the first RF control signal; and operating the fan device to communicate to a server located outside the customer premises, via the WiFi interface, information indicating the operation implemented in response to the first command.
In various embodiments a controller with an RF interface is used to control a fan device which includes a fan motor and may also include a lighting device. The controller in some embodiments is in the form of a wall control module which may be, and sometimes is, mounted in a standard electrical wall box in a room in which the fan device to be controlled is located. To simplify installation and avoid the need for more than the normal 120V power line used to power an outlet, from a 120V AC prospective the controller acts as a simple pass through device through which AC power is supplied to the fan device unit. As a safety, the controller includes an AC disconnect which can be used to cut all power to the fan unit. The disconnect switch may be in the form of a push or pull switch or a pull tab which can interrupt the power to the fan device.
Control of the fan device is via an RF interface included in the wall controller. In some embodiments activation of the safety disconnect switch will cut power to the RF interface of the wall controller in addition to power to the fan device. In this way, in some but not necessarily all embodiments, the safety cut off serves as a physical kill switch integrated into the wall controller for both the wall controller and the fan device.
The wall controller includes inputs for controlling fan on/off operations, light on/off operation, fan speed, e.g., up/down, and/or light intensity, e.g., fan device light output up/down. In some embodiments light output and fan speed can be smoothly controlled, e.g., with light intensity being controlled in a smooth fashion over a wide range of intensity values as opposed to simply a few discrete output levels. The wall controller transmits RF control signals to implement or communicate commands that are generated based on the pressing or altering of the control inputs on the wall controller. The control signals are transmitted to the fan device using a RF frequency band which is different from that used for WiFi signals at the customer premise where the controller is located.
An exemplary fan device controller, in accordance with some embodiments, includes: an AC voltage input; an AC output for supplying power to a fan device; an RF signal interface including an RF signal transmitter for transmitting commands to a device to be controlled; an RF controller for controlling the RF signal interface to send control signals including one or more commands to said fan device; and a disconnect switch for disconnecting said AC output from said AC input when said disconnect switch is switched to a disconnect state from a connect state.
While various embodiments have been discussed in the summary above, it should be appreciated that not necessarily all embodiments include the same features and some of the features described above are not necessary but can be desirable in some embodiments. Numerous additional features, embodiments and benefits of various embodiments are discussed in the detailed description which follows.
Wall control unit 1 114 includes RF interface 1 124, light on/off switch 126, fan on/off switch 128, fan reverse switch 130, and safety switch (SS) 132. Wall control unit 1 114 is installed in electrical box 190 of wall 191. In some embodiments, fan device 1 110 and wall control unit 114 are both located in a first room in customer premises 1 102. Wall control unit N 116 includes RF interface 2 134, light on/off switch 136, fan on/off switch 138, fan reverse switch 140, and safety switch (SS) 142. Wall control unit N 116 is installed in electrical box 192 of wall 193. In some embodiments, fan device N 112 and wall control unit N 116 are both located in a second room in customer premises 1 102, the second room being a different room than the first room. Fan device state information includes fan state information for fan motors and light state information for fan lights.
Control server 108 includes customer premises information corresponding to a plurality of customer premises (CP 1 information 144, . . . , CP M information 146) being controlled by the control server 108. Exemplary customer premises 1 114 information includes, e.g., historical state information corresponding to fan devices located within customer premises 1 102, an approved normal device control schedule for CP1, and a generated away device control schedule for CP1.
120 V input power is received by the power panel 122 via 120V power source input lines 148, 150. The received input power is routed through power panel 122, e.g., passes through a circuit breaker, and is output from the power panel 122, via lines 152, 154, which are input to the safety shutdown switches (132, . . . 142) of the wall control units (114, . . . , 116) of CP 1 102.
The output of safety switch 132, when the switch is in a closed position, powers the internal circuitry on wall control unit 114 and is fed, via lines (156 and 164, 158 and 166) to the input of fan device 1 110. The output of safety switch 142, when the switch is in a closed position, powers the internal circuitry on wall control unit N 116 and is fed, via lines (160 and 168, 162 and 170) to the input of fan device N 112.
RF interface 1 124 of wall control unit 1 114 communicates with fan device 1 110 via RF signals 172. Fan device 1 110 communicates with WIFI router 118 via WiFi signals 176. RF interface N 134 of wall control unit N 116 communicates with fan device N 112 via RF signals 174. Fan device N 112 communicates with WIFI router 118 via WiFi signals 178.
WT 1 120 communicates with WiFi router 118 via WiFi signals 180. In some embodiments, e.g., embodiments supporting Wi-Fi direct, WT 1 120 may directly communicate with fan device 1 110 and fan device N 112 using WiFi signals. WT 1 120 may, and sometimes does, communicate with devices, e.g., control server 108, via the Internet and/or via another WiFi router or a base station when outside customer premises 1 102.
WiFi router 118 includes a WiFi interface, including a WiFi transmitter 196 and a WiFi receiver 195, a network interface includes a receiver 197 and a transmitter 198, a processor 199 and memory coupled together via a bus over which the various elements may interchange data and information. WiFi router 118 communicates with WiFi devices (110, 112, 120) at CP 1 102 via its WiFi interface using WiFi receiver 195 and WiFi transmitter 196. WiFi Router 118 of CP 1 102 communicates with the Internet via the network interface and link 182. A WiFi Router of CP M 104 communicates with the Internet via link 184. Internet 106 is coupled to control server 108 via communications link 186.
Control panel 204 includes a light on/off switch 214, a fan on/off switch 216, a fan reverse switch 218, a light up switch 220, a light down switch 222, a fan speed up switch 224, and a fan speed down switch 226. Light on/off switch 214, e.g., a push button switch, is a light control input for turning a light, e.g., a light in a fan device, on or off. Light on/or switch 214 is coupled to controller 212 via line 248. Fan on/off switch 216, e.g., a push button switch, is a fan control input for turning a fan, e.g., a fan in a fan device, on or off. Fan on/off switch 216 is coupled to controller 212 via line 250. Fan reverse switch 218, e.g., a push button switch, is a fan reverse input for changing the rotation direction of a fan in a fan device. Fan reverse switch 218 is coupled to controller 212 via line 252. Fan speed up switch 224, e.g., a push button switch, is a fan speed up input for increasing the speed of a fan in a fan device. Fan speed down switch 226, e.g., a push button switch, is a fan speed down input for decreasing the speed of a fan in a fan device. Light up switch 220, e.g., a push button switch, is a light up input for increasing the light output from a light in a fan device. Light down switch 222, e.g., a push button switch, is a light down input for decreasing the output of a light in a fan device. Fan speed up switch 224, fan speed down switch 226, light up switch 220, and light down switch 222 are coupled to controller 212 via lines (258, 260, 254, 256), respectively.
RF interface 208 includes an RF transmitter 228 and, in some embodiments, an RF receiver 230, which are coupled to antenna 232, via which the wall control 202 may transmit and, in some embodiments, receive RF signals, e.g., to or from a fan device. Exemplary transmitted RF signals include, e.g., an RF control signal communicating a command. In some embodiments, the command is one of: a fan power state change command, a fan speed up command, a fan speed down command, a fan direction change command, a light power state change command, a light increase command, or a light decrease command. An exemplary received RF signal includes, e.g., an acknowledgment of a transmitted command.
In various embodiments, the RF control signals which are sent by control unit 202 to a fan device use an RF frequency which is not used for WiFi signals. In some embodiments, the RF control signals which are sent by control unit 202 to a fan device use a different frequency band and a different protocol than the WiFi signals which are received by the fan device.
120 V Input power lines 234, 236 are coupled, via AC input interface 237, to the input of safety switch 206, e.g., a disconnect switch. The outputs of safety switch 206 are coupled to the input of DC power supply 210 and to lines 238, 240, which are coupled, via AC output interface 241, to a fan device via lines 242, 244. In
DC power supply 210, when receiving input AC power, generates and outputs DC supply output 246, e.g., 3 VDC, which is input to and used by RF interface 208 and controller 212. In some embodiments, the DC power supply 210 generates and outputs multiple DC voltages, e.g., 3 VDC, 5 VDC, 15 VDC and −15 VDC, which are used by the controller 212 and the RF interface 208. The DC power supply 210 is connected to switch 206 and to the RF controller 212. The DC power supply 206 receives AC power from the disconnect switch 206 when switch 206 is in the closed position, and the DC power supply 210 generates DC power from the received AC power and supplies the DC power to the controller 212. If an operator switches the disconnect switch 206 to a disconnect state, power is cut off to both AC output 241 and to the DC power supply 210 at the same time.
Controller 212, e.g., an RF controller, controls the RF interface 208 including RF signal transmitter 228 to generate and transmit RF control signals over line 262 in response to detected control panel input button depressions. Lines can be, for example, wires or traces over which electrical signals can be communicated. RF signal transmitter 228 transmits commands to a device, e.g., a fan device, being controlled. Controller 212, e.g., an RF controller, includes a processor 213 configured to generate a command, e.g., (a light power state change command, a fan power state change command, a fan direction change command, a light increase command, a light decrease command, a fan speed up command, a fan speed down command) in response to received input via an input (light control input 214, fan control input 216, fan reverse input 218, light up input 220, light down input 222, fan speed up input 224, or fan speed down input 226), respectively, and control the RF interface 208 to transmit said generated command in a generated RF signal to a fan device.
WiFi interface 312, RF interface 314, fan motor control circuit 308, light control circuit 310, processor 316 and memory 318 are coupled together via a bus 320 over which the various elements may interchange data and information. Fan motor control circuit 308 includes an On/Off control circuit 326, a fan direction control circuit 328, and a fan speed control circuit 330. In some embodiments, the fan motor control circuit 308 includes an Insulated Gate Bipolar Transistor (IGBT) module, a processor, and analog feedback circuitry. The fan motor control circuit 308 is coupled to fan motor 308 via cable 350. Fan motor shaft 338 couples the fan motor to the fan blades 336. Light control circuit 310 includes an On/Off control circuit 332 and an Up/Down control circuit 334. The light control circuit 310 is coupled to light 306 via cable 352. Fan on/off control circuit 326 controls whether or not power is applied to fan motor 304, e.g., in response to received fan power state change control commands, fan power on control commands, and fan power off control commands. Fan direction control circuit 328 controls the direction fan motor 304 turns, e.g., in response to received fan direction change commands, and fan direction commands. Fan speed control circuit 330 controls the speed of fan motor 304, e.g., in response to received fan speed up commands, fan speed down commands, and fan speed setting level commands. In various embodiments, the fan motor control circuit 308 is configured to control the fan to operate at a predetermined speed and direction when initially commanded to power on from an off state, unless specified otherwise, e.g., in a schedule or by a command. Light on/off control circuit 332 controls whether or not power is applied to light 306, e.g., in response to a received light power state change control commands, light power on control commands, and light power off control commands. Light up/down control circuit 334 controls the light output level of light 306, e.g., in response to received light increase commands, light decrease commands, and light level setting commands. In some embodiments, the light level is changed by changing the voltage or current supplied to a light or a set of lights. In some embodiments, the light level is changed by changing the number of lights to which power is applied in a set of lights. In various embodiments, the light control circuit 310 is configured to control the light 306 to operate at a predetermined output level when initially commanded to power on from an off state, unless specified otherwise, e.g., in a schedule or by a command.
Input AC, e.g., 120 VAC, is received from a wall control unit via inputs 340, 342. AC power interface 322 conditions the received AC, e.g., performing filtering, and outputs conditioned AC power on lines 344, 346, which are used as input by other elements within fan device 300, e.g., the fan motor 304 or fan motor control circuit 308, the light 306 or the light control circuit 310, and the DC power supply 324. DC power supply 324 generates and outputs one or more DC voltages, e.g., 170 VDC, 3.3 VDC, 16 VDC, 3 VDC, +5 VDC, 15 VDC, and/or −15 VDC from the input AC power received via lines 344, 346. Output DC power is via DC power bus 448 and the DC voltages are referenced with respect to DC ground 349. In some embodiments, the DC power supply includes one of more current supplies in addition to one or more voltage supplies. DC power from DC power supply 324 is supplied to and used by processor 316, memory 318, WiFi interface 312, RF interface 314, fan motor control circuit 308, light control circuit 310, and in some embodiments, light 306 and/or fan motor 304. While known DC motor fan systems that are available experience problems when controlled over the same the same power run, e.g., when three fans are daisy chained together so that power is connected to a first fan and from the first fan to a second fan and then a third fan, the third fan typically does not operate properly it experiences being off kilter in time and speed on start, use of the circuitry shown in
Processor 316 is configured to control the RF interface 314 including RF receiver 360 to receive RF control signals, recover the control command or commands being communicated and communicate the recovered control command or commands to the fan motor control circuit 308 and/or light control circuit 310 or send information to the fan motor control circuit 308 and/or light control circuit 310 to be used to implement the recovered control command or commands. Processor 316 is further configured to control the WiFi interface 312 including WiFi receiver 356 to receive WiFi signals including messages communicating control commands, recover the control command or commands being communicated and communicate the recovered control command or commands to the fan motor control circuit 308 and/or light control circuit 310 or send information to the fan motor control circuit 308 and/or light control circuit to be used to implement the recovered control command or commands. Processor 316 is further configured to generate device status reporting messages and to control the WiFi interface including transmitter 354 to transmit WiFi signals including the device status reporting messages communicating device state information. In various embodiments, processor 316 is configured to generate and send a device status reporting message, e.g., in response to a received and implemented RF control signal or a received and implemented WiFi control message. In some embodiments, the processor 316 is configured to limit time intervals between successive device status reporting messages, e.g., to prevent excessive status reporting messages such as where an individual is pushing an input button on a wall control unit 202 multiple times in very short time interval. In one exemplary embodiment, a device status reporting message is sent to a control server at most once per predetermined time interval, e.g., once per two second time interval or once per two minute time interval. In some embodiments, device status reporting messages to the control server communicates a change from a previously communicated device status reporting message. In various embodiments, a device status reporting message can, and sometimes does, include an aggregate of multiple received and implemented commands. In various embodiments, a generated device status reporting message includes time tag information, e.g., a transmission time tag and/or a time tag or time tags corresponding to an implemented state change or changes implemented at the fan device. In some embodiments, the fan device includes a single circuit board that includes the WIFI interface 312, RF interface 314, fan motor control circuit 308, light control circuit 310, AC power interface 322, DC power supply 324, memory 318 and processor 316.
In one exemplary embodiment, fan device 1 110 and wall control unit 1 116 are located in a first room, and fan device N 116 and wall control unit N 116 are located in a second room, which is a different room from the first room. In some embodiments, the fan devices 110, 112, each include a RF interface and a WiFi interface, while the wall control units 114, 116 each include a RF interface but do not include a WiFi interface. In one exemplary embodiment, wall control unit 1 114, is a wall mounted unit, which supplies power to fan device 1 110; and wall control unit N 116, is a wall mounted unit, which supplies power to fan device N 112.
In some embodiments, the RF and WiFi interfaces while both being wireless interfaces are different interfaces and use different frequency bands and different communications protocols. In some embodiments, the RF interfaces use a sub-GHz frequency band, e.g., 315 MHz or 433 Mhz, and the WiFi interfaces use a 2.4 GHz frequency band. In some embodiments, the RF interfaces use ON OFF KEYING (OOK) 2 kSymbols/sec, Manchester Encoded protocol. In some embodiments, the WiFi interfaces use a 802.11 b/g/n protocol.
Drawing 400 is an exemplary signaling diagram illustrating exemplary signaling between the various devices and exemplary operations performed by the devices in accordance with an exemplary method.
In step 402 WC 1 114 generates and sends radio frequency (RF) control signal 404, e.g., a wireless RF signal, to fan unit 1 110 commanding fan unit 1 110 to change the power state of its fan. In some embodiments, the RF control signal 404 is sent using an RF signal which is not used for WiFi signals. In step 406 fan unit 1 110 receives signal 404 and recovers the communicated command. Consider that the fan in fan device 1 110 is currently off. In response to the received recovered command in RF signal 404, in step 408 fan unit 1 110 turns on its fan, which is fan 1. In step 410, fan device 1 110 generates and sends a reporting message 412 to WiFi router 1 114 reporting that fan 1 is on.
In one exemplary embodiment, the reporting message 412 includes: an identifier identifying fan device being controlled, which in this example is fan device 1 110, information indicating the time the command was implemented, information indicating the operation performed by the fan device, which in this example is turning on the fan in fan device 1 110, and information identifying the customer premises, which in this example is CP1 102. Other reporting messages described in this signaling flow diagram may also use this exemplary reporting format. The reporting allows the server 108, which is the intended end point recipient of the reporting message information, to create a log of the state of fan device 1 and create a history of the state of the device. Recorded state information corresponding to multiple fan devices at CP1 may be used to facilitate learning of use patterns and thereby allow for automated schedule generation for both normal and away schedules both of which may be, and sometimes are, machine learning based on the information reported to the control server 108 in system 100.
In step 414 WiFi router 118 receives message 412 and recovers the communicated information. In step 416 WiFi router 118 generates reporting message 418, indicating that fan 1 is on, and sends message 418, via the Internet 106, to control server 108. In step 420 control server 108 receives message 418 and recovers the communicated information, originally sourced from fan device 1, which indicates that the fan 1 in fan device 1 is on. In step 421 control server 108 updates the customer premises 1 (CP1) information to record that fan 1 is on and the time.
In step 422 WC 1 114 generates and sends RF control signal 424 to fan device 1 110 commanding fan unit 1 110 to change the power state of its light, which is light 1. In step 426 fan unit 1 110 receives RF signal 424 and recovers the information communicated. Consider that light 1 is in an OFF state. In response to the recovered command of signal 424, in step 428 fan device 1 110 turns on light 1. In step 430, fan device 1 110 generates and sends a reporting message 432 to WiFi router 1 118 reporting that light 1 is on. In step 434 WiFi router 118 receives message 432 and recovers the communicated information. In step 436 WiFi router 118 generates reporting message 438, indicating that light 1 is on, and sends message 438, via the Internet 106, to control server 108. In step 440 control server 108 receives message 438 and recovers the communicated information, originally sourced from fan device 1, which indicates that light 1 is on. In step 441 control server 108 updates the customer premises 1 (CP1) information to record that light 1 is on and the time.
In step 442 WC 1 114 generates and sends RF signal 444 to fan device 1 110 commanding fan device 1 110 to perform a fan power state change. In step 446 fan device 1 110 receives signal 444 and recovers the information communicated, and in response in step 448 fan device 1 110 turns off fan 1. In step 450, fan device 1 110 generates and sends a reporting message 452 to WiFi router 1 118 reporting that fan 1 is off. In step 454 WiFi router 118 receives message 452 and recovers the communicated information. In step 456 WiFi router 118 generates reporting message 458, indicating that fan 1 is off, and sends message 458, via the Internet 106, to control server 108. In step 460 control server 108 receives message 458 and recovers the communicated information, originally sourced from fan device 1 110, which indicates that fan 1 is off. In step 462 control server 108 updates the customer premises 1 (CP1) information to record that fan 1 is off and the time.
In step 464 WC 1 114 generates and sends RF signal 466 to fan device 1 110 commanding fan device 1 110 to perform a power state change of its light, which is light 1. In step 468 fan device 1 110 receives signal 466 and recovers the information communicated, and in response in step 470 fan device 1 110 turns off light 1. In step 472, fan device 1 110 generates and sends a reporting message 474 to WiFi router 1 118 reporting that light 1 is off.
In step 476 WiFi router 118 receives message 474 and recovers the communicated information. In step 478 WiFi router 118 generates reporting message 480, indicating that light 1 is off, and sends message 480, via the Internet 106, to control server 108. In step 482 control server 108 receives message 480 and recovers the communicated information, originally sourced from fan device 1 which indicates that light 1 is off. In step 484 control server 108 updates the customer premises 1 (CP1) information to record that light 1 is off and the time.
In step 486 WT 1 120, which is a device supporting WiFi communications, generates and sends WiFi control signal 487 to WiFi router 118 commanding fan device 1 110 to turn on its light, which is light 1. In step 488 WiFi router 118 receives signal 487 and recovers the information communicated. In step 489 WiFi router 118 generates and sends WiFi signal 490 to fan device 1 110 communicating the command to turn on its light. In step 491 fan device 1 110 receives signal 490 and recovers the information communicated, and in response in step 492 fan device 1 110 turns on light 1. Thus the control command of signal 487 is communicated from WT 1 120, which is a WiFi device currently located within CP1 102, to fan device 110, located at CP1 102, via WiFi router 118, also located at CP1 102, without the command traversing a network outside the customer premises CP1 102. Thus in some embodiments, at least some times, the communication of a command, e.g., in a WiFi signal, to a fan device does not depend or involve communication over a network outside the customer premises, and the fan device can be controlled from within the CP, e.g., house, via WiFi even if an Internet or server connection to the server is not present or available.
In step 494, fan device 1 110 generates and sends a reporting message 496 to WiFi router 1 118 reporting that light 1 is on. In step 498 WiFi router 118 receives message 496 and recovers the communicated information. In step 500 WiFi router 118 generates reporting message 502, indicating that light 1 is on, and sends message 502, via the Internet 106, to control server 108. In step 504 control server 108 receives message 502 and recovers the communicated information, originally sourced from fan device 1 110, which indicates that light 1 is on. In step 506 control server 108 updates the customer premises 1 (CP1) information to record that light 1 is on and the time.
In step 508 WT 1 120 generates and sends WiFi signal 509 to WiFi router 118 commanding fan device 1 110 to turn on its fan. In step 510 WiFi router 118 receives signal 509 and recovers the communicated information. In step 511, WiFi router 118 generates and sends WiFi signal 512 to fan device 1 110 communicating the fan 1 on command. In step 513 fan unit 1 110 receives signal 512 and recovers the information communicated, and in response in step 514 fan device 1 110 turns on fan 1. In step 516, fan device 1 110 generates and sends a reporting message 518 to WiFi router 1 114 reporting that fan 1 is on. In step 520 WiFi router 118 receives message 518 and recovers the communicated information. In step 522 WiFi router 118 generates reporting message 524, indicating that fan 1 is on, and sends message 524, via the Internet 106, to control server 108. In step 526 control server 108 receives message 524 and recovers the communicated information, originally sourced from fan device 1 110, which indicates that fan 1 is on. In step 528 control server 108 updates the customer premises 1 (CP1) information to record that fan 1 is on and the time. Although the control messages and reporting message, corresponding to fan device 1 110, have been shown for on/off examples, in some embodiments, the control messages which are sent may control other operations, e.g., increase light intensity of light 1, decrease light intensity of light 1, increase fan speed of fan 1, decrease fan speed of fan 1, change fan direction of fan 1, and the reporting messages may report device status or device status change in response to those commands.
Exemplary on/off device control signaling, state changes, reporting, and recording of device status in control server 108, has been shown over time, for a few examples, for fan device 1 110 including fan 1 and light 1. It should be appreciated that similar signaling and operations are performed with regard to the other fan devices, e.g., fan device N 112, located at customer premises 1 102, and control server 108 also records and builds up a historical record corresponding to status including state information of the other fan devices located at CP1 102, e.g., fan device N 112, over time.
In step 530, the control server 108 generates a proposed normal device control schedule for customer premises 1 102, e.g., based on historical recorded information. The generated proposed normal control schedule for CP1 is a fan and lighting control schedule for controlling the fan devices at CP1 including, e.g., on/off fan control schedule, on/off light control schedule, fan speed schedule, fan direction schedule, and light intensity schedule. In some embodiments, the proposed normal device control schedule is generated based on stored information including the state of one or more fan devices (fan device 1 110, . . . , fan device N 112) at CP1 102 over a period of time, e.g., two or more weeks, e.g., based on collected stored reporting messages from the fan devices (110, . . . , 112) over the time period. In step 532, the control server generates a message 533 communicating the generated proposed normal device control schedule and sends the generated message to WiFi router 118, via Internet 106.
In step 534 the control server 108 generates an away device control schedule for CP1 102, e.g., random based or based on historical use with randomization. In various embodiments, server 108 generates the away schedule to be used to control one or more fan devices (110, . . . , 112) at CP1 102 when the customer indicates that they are away from the customer premises 102. In some embodiments, operating the control server 108 to generate an away schedule includes generating said away schedule as a function of a random function used to at least partially randomize the on or off times of one or more devices. In some embodiments, operating the server 108 to generate the away schedule includes using information about past device on and off status in combination with said random function to control the on and off times as a function of at least one device, said on and off times deviating from historical on and off times by an amount of time which does not exceed a set maximum amount of time, e.g., 30 minutes, and which is determined by said random function. For example, once the historical on/off times of a light on the fan device are known the random function is used to change the on/off time in a random function but keep it within 30 minutes or so of the normal on/off time so that the on/off pattern is not identical from day to day but within an expected normal range that might occur to a human getting home or moving around the home which would not be identical each day but might not deviate greatly, e.g., by more than an hour, from day to day. In step 535 control server 108 stores the generated away device control schedule for CP1 102.
In step 536, WiFi router 118 receives message 533 and recovers the information in message 533 including the proposed normal device control schedule. In step 538, WiFi router 118, generates a message 540 including the proposed normal device control schedule and sends the message 540 to WT 1 120. Thus the generated proposed normal device control schedule has been communicated from control server 108, via the Internet 106 and WiFi router 118, located at CP1, to device WT 1 120 corresponding to the first customer premises. WT 1 120 is, e.g., the cell phone, e.g., a smartphone, of a user who is located at the first customer premises 102.
In step 542, WT 1 120 receives message 540 recovers the proposed normal control schedule and presents the proposed normal device control schedule to the user of WT 1 120. In some embodiments, the user of device 1 120 may decide to revise the proposed normal device control schedule. In step 544, WT 1 120 receives user input revisions and generates a revised normal device control schedule. In step 546, WT 1 120 generates a message 548 communicating user authorization for the proposed normal device control schedule or a revised normal device control schedule and sends message 548 to WiFi router 118. In step 550, WiFi router 118 receives message 550 and recovers the communicated information. In step 552 WiFi router 118 generates message 554 communicating the user authorization for the proposed normal device control schedule or the user revised normal device control schedule and sends message 554 via Internet 106 to control server 108.
In step 556, the control server receives message 554 and recovers the communicated user authorization for the proposed normal device control schedule or the communicated revised normal device control schedule. If user authorization is received for the suggested normal control schedule, the control server 108 designates the generated suggested control schedule as a normal approved device control schedule. If a revised normal device control schedule is received, the control server 108 designates the received revised schedule as the normal approved device control schedule. In step 557 the control server stores the approved normal control schedule.
In step 558, the control server 108 starts operating in accordance with the approved normal device control schedule, e.g., to automatically control operations at fan device 1 110 and fan device N 112 of CP1 102. In various embodiments, operating the control server 108 in accordance with the stored approved normal control schedule includes operating the server 108 to control one or more of the fan devices (110, . . . , 112) at CP1 102 based on the normal approved device control schedule including transmitting a control signal from control server 108 to fan device 1 110 via the Internet 106 and WiFi router 118 to control fan device 1 to take an action at a time indicated in the normal approved device control schedule, e.g., to control the fan of fan device 1 110 to turn on at a time indicated by the normal approved device control schedule.
In some embodiments, the control server 108 will switch to automatic operations in accordance with the approved normal device control schedule based on the reception of message 554, e.g., once the proposed schedule is approved the control server starts using the approved normal device control schedule.
In some embodiments, the control server 108 will not switch to automatic operations in accordance with the approved normal device control schedule until receiving an additional message, e.g., a normal device control schedule activation message from a user, e.g., the user which approved the proposed normal schedule or sent the revised normal schedule. In some embodiments, the user may send server 108, e.g., from device WT 1 120, a message communicating one or more time intervals in which the control server 108 is to operate in accordance with the approved normal device control schedule and/or one or more time intervals in which the control server 108 is to operate in accordance with the away schedule and/or one or more time intervals in which the control server 108 is not to use either the normal schedule or the away schedule but is to allow just wall control units and user devices such as WT 1 to control the fan devices at CP1.
In step 559, the control server 108, operating in accordance with the normal approved control schedule, generates and sends control signal 560 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan 1 and/or light 1 of fan device 1 110 based on the normal authorized device control schedule. In step 561 the control server 108 updates fan device 1 state information based on the control commands sent in message 560. In step 562, the WiFi router 118 receives control signal 560 and recovers the communicated information, e.g., control command or commands directed to fan device 1 110. In step 564, the control server generates and sends control signal 566 to automatically control fan 1 and/or light 1 of fan device 1 110. In step 568, fan device 1 110 receives control signal 566 and recovers the control information communicated. In step 569 fan device 1 110 performs an action or actions in response to one or more recovered control commands in the received WiFi signal 566, e.g., turns off fan 1, turns off light 1, reverses the direction of fan 1, increases fan 1 speed, decreases fan 1 speed, sets fan 1 speed to a particular value, increases light 1 intensity, decreases light 1 intensity, sets light 1 intensity to a particular level, etc.
In step 570, the control server 108, operating in accordance with the normal approved control schedule, generates and sends control signal 572 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan N and/or light N of fan device N 112 based on the normal approved device control schedule. In step 571 the control server 108 updates fan device N state information based on the control commands sent in message 572. In step 574, the WiFi router 118 receives control signal 572 and recovers the communicated information. In step 576, the WiFi router 118 generates and sends control signals 578 to automatically control fan N and/or light N to fan unit N 112. In step 580, fan unit N 112 receives control signals 578, recovers the control information, e.g., control command or commands communicated in signal 578. In step 581 fan device N 112 performs an action or actions in response to the one or more received and recovered control commands in WiFi control signal 578, e.g., turns on fan N, turns off fan N, turns on light N, turns off light N, reverses the direction of fan N, increases fan N speed, decreases fan N speed, increase light N intensity, decreases light N intensity, sets the speed of fan N to a particular level, sets the light output level of light N to a particular level, etc.
Although only one arrow is shown for control signal 560, and corresponding forwarded control signal 566, to illustrate one example, it should be appreciated that many different control signals, e.g., individual control signals may be, and in some embodiments, are sent at different times to achieve different desired states of operation of fan unit 1, in accordance with the normal authorized device control schedule. Although only one arrow is shown for control signals 572, and corresponding forwarded control signals 578, it should be appreciated that many different control signals, e.g., individual control signals may be, and in some embodiments, are sent at different times to achieve different desired states of operation of fan unit N, in accordance with the normal authorized schedule.
In step 582, based on received user input, WT 1 120 generates a signal 584 indicating that the away device control schedule should be used to control the fan units at customer premises 1, and WT 1 120 sends the signal 584 to WiFi router 118. In some embodiments, signal 584 conveys an away status indicator from the user of user device WT 1 120. In step 586, WiFi router 118 receives signal 584, recovers the communicated information. In step 588 WiFi router 118 generates and sends signal 590 including information indicating that the control server should use the away schedule for customer premises 1, via Internet 106, to control server 108. In step 592 control server 108 receives signal 590 and recovers the communicated information, e.g., the away status indicator, indicating that the away schedule should now be used for CP1. In step 594, in response to received message 590, the control server 108 switches to automatic control of the fan units at customer premises 1 based on the away device control schedule. Thus the control server 108 switches from using the stored approved normal schedule to using the stored away schedule to control the one of more fan devices (110, . . . , 112) at the first customer premises.
In step 596, the control server 108, operating in accordance with the away device control schedule, generates and sends control signal 598 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan 1 and/or light 1 of fan device 1 110 based on the away device control schedule. In step 599 the control server 108 updates fan device 1 state information based on the control commands sent in message 598. In step 600, the WiFi router 118 receives control signal 598 and recovers the communicated information, e.g., control command or commands directed to fan device 1 110. In step 602, the control server 108 generates and sends control signal 604 to automatically control fan 1 and/or light 1 of fan device 1 110. In step 606, fan device 1 110 receives control signal 604, recovers the control information communicated. In step 607 fan device 1 110 performs an action or actions in response to one or more recovered control commands in the received WiFi control signal 606, e.g., turns off fan 1, turns off light 1, reverses the direction of fan 1, increases fan 1 speed, decreases fan 1 speed, sets fan 1 speed to a particular value, increases light 1 intensity, decreases light 1 intensity, sets light 1 intensity to a particular level, etc, said recovered control commands having been originally sent from control server 108.
In step 608, the control server 108, operating in accordance with the away device control schedule, generates and sends control signal 610 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan N and/or light N of fan device N 112 based on the away device control schedule. In step 611 the control server 108 updates fan device N state information based on the control commands sent in message 610. In step 612, the WiFi router 118 receives control signal 610 and recovers the communicated information. In step 614, the control server generates and sends control signals 616 to automatically control fan N and/or light N to fan unit N 112. In step 618, fan unit N 112 receives control signals 616, recovers the control information, e.g., control command or commands communicated in signal 616. In step 619 fan device N 112 performs an action or actions in response to the one or more received and recovered control commands in WiFi control signal 578, e.g., turns on fan N, turns off fan N, turns on light N, turns off light N, reverses the direction of fan N, increases fan N speed, decreases fan N speed, increases light N intensity, decreases light N intensity, sets the speed of fan N to a particular level, sets the light output level of light N to a particular level, etc, said recovered control commands having been originally sent from control server 108.
Although only one arrow is shown for control signal 598, and corresponding forwarded control signal 604, to illustrate one example, it should be appreciated that many different control signals, e.g., individual control signals may be, and in some embodiments are, sent at different times to achieve different desired states of operation of fan unit 1, in accordance with the away device control schedule. Although only one arrow is shown for control signal 610, and corresponding forwarded control signal 616, it should be appreciated that many different control signals, e.g., individual control signals may be, and in some embodiments are, sent at different times to achieve different desired states of operation of fan unit N, in accordance with the away schedule.
In step 620, based on received user input, WT 1 120 generates a signal 622 indicating that the away device control schedule, used to control the fan units at customer premises 1, and WT 1 120, should be disabled and that the approved normal device control schedule should be used again, sends the generated signal 622 to WiFi router 114. In step 624, WiFi router 118 receives signal 622, recovers the communicated information. In step 626 WiFi router 118 generates and sends signal 628 including information indicating that the control server should disable use of the away schedule for customer premises 1 and resume using the approved normal device control schedule, via Internet 106, to control server 108. In step 630 control server 108 receives signal 628 and recovers the communicated information indicating that the away schedule should no longer be used for CP1 102 and that the normal schedule should now be used. In step 632, in response to received message 628, the control server 108 switches to automatic control of the fan devices 110, 112 at customer premises 1 102 based on the normal authorized approved device control schedule.
In step 634, the control server 108, operating in accordance with the normal approved control schedule, generates and sends control signal 635 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan 1 and/or light 1 of fan device 1 110 based on the normal authorized device control schedule. In step 636 the control server 108 updates fan device 1 state information based on the control commands sent in message 635. In step 638, the WiFi router 118 receives control signal 635 and recovers the communicated information, e.g., control command or commands directed to fan device 1 110. In step 640, the WiFi router 118 generates and sends control signal 642 to automatically control fan 1 and/or light 1 of fan device 1 110. In step 644, fan device 1 110 receives control signal 642, recovers the control information communicated. In step 645 fan device 1 110 performs an action or actions in response to one or more recovered control commands in the received WiFi signal 642, e.g., turns off fan 1, turns off light 1, reverses the direction of fan 1, increases fan 1 speed, decreases fan 1 speed, sets fan 1 speed to a particular value, increases light 1 intensity, decreases light 1 intensity, sets light 1 intensity to a particular level, etc.
In step 646, the control server 108, operating in accordance with the normal approved control schedule, generates and sends control signal 647 including one or more control commands, via Internet 106, to WiFi router 118 to automatically control fan N and/or light N of fan device N 112 based on the normal approved device control schedule. In step 648 the control server 108 updates fan device N state information based on the control commands sent in message 647. In step 650, the WiFi router 118 receives control signal 647 and recovers the communicated information. In step 652, the control server generates and sends control signals 656 to automatically control fan N and/or light N to fan unit N 112. In step 658, fan unit N 112 receives control signals 656, recovers the control information, e.g., control command or commands communicated in signal 656. In step 659 fan device N 112 performs an action or actions in response to the one or more received and recovered control commands in WiFi control signal 656, e.g., turns on fan N, turns off fan N, turns on light N, turns off light N, reverses the direction of fan N, increases fan N speed, decreases fan N speed, increases light N intensity, decreases light N intensity, sets the speed of fan N to a particular level, sets the light output level of light N to a particular level, etc.
In
In step 672, WiFi router 118 receives device control signal 670. In step 674 WiFi router 118 generates and sends device control signal 676, which includes the received command or commands being relayed, to fan device 1 110, thus communicating the control command or command in signal 662, to fan device 1 110. In step 678 fan device 1 110 receives signal 676, recovers the communicated command or commands. In step 679 fan device 1 110 implements the received recovered command or commands, e.g., turns on light 1 of fan device 1 110. In some embodiments, fan device 1 110 in step 680 generates and sends acknowledgment signal 681 to server 108, which is received in step 682. Some embodiments include step 683, in which the control server 108 updates fan device 1 state information based on the commands in transmitted signal 670 and the reception of acknowledgment signal 681, in response to receiving the acknowledgment signal 681 in step 682. In step 684, server 108 generates and sends acknowledgment signal 685, which is a forwarded version of acknowledgment signal 681, to WT 1 120. In step 686 WT 1 120 receives acknowledgment signal 685 and has confirmation that the command of signal 662 has been received and/or acted upon.
Memory 706 includes an assembly of components 716, e.g., an assembly of software components, e.g., software modules. Data/information 718 includes information corresponding to a plurality of customer premises (customer premises 1 information 720, . . . , customer premises M information 722). Customer premises 1 information 720 includes received fan device 1 reporting messages 724, . . . , received fan device N reporting messages 726, a generated proposed normal device control schedule for CP1 728, and a generated away device control schedule for CP1 730. In some embodiments, CP1 data/information 720 includes a revised normal device control schedule 732, e.g., based on user revisions to the proposed schedule. CP1 information 720 further includes fan device 1 state information 736, fan device N state information 738, a current control mode of operation with regard to controlling the fan devices at CP1 740, e.g., use the approved normal device control schedule, use the away device control schedule, or do not perform automatic control at the current time, a received message 742 indicating user selection of mode, or a user command to switch modes, or user communicated indicator indicating whether or not the user is away which is utilized to determine mode selection. CP 1 information further includes a received control message 744, e.g., from a WT of an authorized user, to be forwarded to a fan device indicated in the received message to control the fan device, and a generated control message 746 in accordance with (JAW) the normal or away schedule, said generated message to be sent to a fan device at an appropriate time in accordance with the normal or away schedule.
Exemplary WT 800 includes a WiFi interface 802, a cellular wireless interface 804, a wired interface 806, a processor 808, memory 810, an I/O interface 812 coupled to display 814, e.g., a touchscreen display, keypad 816, and an assembly of components 818, e.g., an assembly of hardware components 818, e.g., an assembly of circuits. The various elements 802, 804, 806, 808, 810, 812, 818 are coupled together via a bus 820 over which the various elements may interchange data and information.
WiFi interface 802 includes a WiFi transmitter 832 and a WiFi receiver 834 coupled to antennas (833, 835), respectively, via which the WT 800 may transmit and receive WiFi signals. Cellular wireless interface 804 includes a wireless transmitter 836 and a wireless receiver 838 coupled to antennas (837, 839), respectively, via which the WT 800 may transmit and receive wireless cellular signals. In some embodiments, the same antenna is used for one or more transmitters and/or receivers. Wired interface 806 includes network transmitter 840 and a network receiver 842 via which the WT 800 may transmit and receive signals, e.g., via a wired connection to the Internet and/or to other nodes.
Memory 810 includes routines 822 and data/information 824. Routines 822 includes a wireless terminal control routine 826, and a fan device control application 828. Fan device control application 828 includes an assembly of components 830, e.g., an assembly of software components, for performing different functions related to fan device control, fan device status monitoring, setup and initialization, user authorization, communications with a fan device, communications with a control server, user interfaces, etc. Fan device control application 828 controls WT 800 to present one or more custom interfaces to the user of WT 800, e.g., via smartphone display 814, which allows the user to control fan devices. In some embodiments, one exemplary control display simulates the input of control panel 204 of wall control unit 202, e.g., accepting inputs for: an on/off fan power transition command, a fan reverse command, a fan speed increase command, a fan speed decrease command, an on/off light power transition command, a light output increase command, and a light output decrease command. In some embodiments, one exemplary control display is configured to accept inputs for the following commands: a fan on command, a fan off command, a light on command, a light off command, a fan reverse command, a fan direction selection input command, a fan speed level setting command, a light intensity level setting command, a fan speed increase command, a fan speed decrease command, a light intensity increase command, a light intensity decrease command, a light intensity change rate command, e.g., allowing a smooth gradual light intensity specified change over a specified time period, and a fan speed change rate command, e.g., allowing a smooth gradual fan speed level change over a specified time period. In various embodiments, the fan device control application 828 receives user command inputs, generates control messages and sends the control messages to either the fan device, e.g., via WiFi signaling, or to a control server for forwarding to the fan device to be controlled, e.g., depending on the location of the WT 800. Fan device control app 828 is further configured to operate WT 800 to: receive a proposed normal device control schedule from a control server, present the received proposed schedule to a user, receive user approval of the schedule, receive user revisions, generate a revised schedule incorporating the revisions, and generate and send an approval message or a revised schedule to the control server. Fan device control app 828 is further configured to operate the WT 800 to: receive user input indicating that a user desires that one or more fan devices be controlled in accordance with the normal approved device control schedule, the away schedule, or manually via WT 800 input and/or a wall control panel, e.g., for a specified period of time, and communicate the user input to the control server, e.g., to control switching between normal schedule automatic device control, away schedule automatic device control, and no automatic control. In some embodiments, the application 828 generates and sends indicators, e.g., an away indicator or a home indicator, e.g., based on user input, to control switching between normal and away device control schedules. Fan device control app 828 is further configured to control WT 800 to send a request for fan device status, e.g. fan device state information such as on/off status of a fan, on/off status of a light, light intensity output level, fan direction, and fan speed, to a fan device and/or to the control server, to receive fan device status information, and to present the received fan device status information to a user of WT 800, e.g., on display 814. In some embodiments, current fan device status information is presented concurrently with an input control interface on the display, e.g., on the smartphone screen display.
Assembly of components 900 may be included in an exemplary server, e.g., control server 700. The components in the assembly of components 900 can, and in some embodiments are, implemented fully in hardware within a processor, e.g., processor 704, e.g., as individual circuits. The components in the assembly of components 900 can, and in some embodiments are, implemented fully in hardware within the assembly of hardware components 708, e.g., as individual circuits corresponding to the different components. In other embodiments some of the components are implemented, e.g., as circuits, within processor 704 with other components being implemented, e.g., as circuits within assembly of components 708, external to and coupled to the processor 704. As should be appreciated the level of integration of components on the processor and/or with some components being external to the processor may be one of design choice. Alternatively, rather than being implemented as circuits, all or some of the components may be implemented in software and stored in the memory 706 of the server 700, with the components controlling operation of server 700 to implement the functions corresponding to the components when the components are executed by a processor e.g., processor 704. In some such embodiments, the assembly of components 900 is included in the memory 706 as assembly of software components 716. In still other embodiments, various components in assembly of components 900 are implemented as a combination of hardware and software, e.g., with another circuit external to the processor providing input to the processor which then under software control operates to perform a portion of a component's function.
When implemented in software the components include code, which when executed by a processor, e.g., processor 704, configure the processor to implement the function corresponding to the component. In embodiments where the assembly of components 900 is stored in the memory 706, the memory 706 is a computer program product comprising a computer readable medium comprising code, e.g., individual code for each component, for causing at least one computer, e.g., processor 704, to implement the functions to which the components correspond.
Completely hardware based or completely software based components may be used. However, it should be appreciated that any combination of software and hardware, e.g., circuit implemented components may be used to implement the functions. As should be appreciated, the components illustrated in
Assembly of components 900 includes a component 902 configured to receive reporting messages sent from fan devices, e.g., communicating fan device identification information, customer premises identification information, commands received at the fan device, operations performed at the fan device in response to received commands, fan device status information, e.g., fan device state information, e.g., fan on or fan off, fan speed, fan direction, light on or off, light intensity level, etc., and time information, e.g., time a command was received at the fan device, time an operation was performed in response to a received command, time information corresponding to state information included in the reporting message, and/or transmission time corresponding to reporting message. In some embodiments, a reporting message may, and sometimes does include aggregated information corresponding to multiple commands. Assembly of components further includes a component 904 configured to store information communicated in received reporting messages from the fan devices. In some embodiments, as part of receiving a reporting message the message reception time is also recorded and stored.
Assembly of components 900 further includes a component 906 configured to generate a proposed normal device control schedule from stored information indicating the state of one or more devices at a customer premises over a period of time, e.g., over two or more weeks, a component 908 configured to send a generated proposed normal device control schedule for a customer premises to device corresponding to the customer premises, and a component 912 configured to generate an away schedule to be used to control one or more devices at a customer premises when the customer indicates that they are away from the customer premises. In some embodiments, component 912 includes a component 914 configured to generate said away schedule as a function of a random function used to at least partially randomize the on or off times of one or more devices. In some embodiments, component 914 includes a component 916 configured to use the information about past device on and off status in combination with said random function to control the on and off times for at least one device, said on and off times deviating from historical on and off times by an amount of time which does not exceed a maximum amount of time, e.g., 30 minutes, and which is determined by the random function. Assembly of components 900 further includes a component 918 configured to store a generated away device control schedule corresponding to a customer premises, a component 920 configured to receive a message indicating approval of a proposed normal device control schedule or a revised normal device control schedule, and a component 922 configured to store an approved normal device control schedule for a customer premises, said approved schedule being either the proposed normal device control schedule or the received revised normal device control schedule.
Assembly of components 900 further includes a component 924 configured to control one or more devices at a customer premises based on the stored approved normal device control schedule corresponding to the customer premises. Component 924 includes a component 926 configured to identify and send a command to a fan device at the customer premises via the internet and a WiFi router to control the fan device based on the normal approved device control schedule. Assembly of components 900 further includes a component 928 configured to control one or more devices at a customer premises based on the stored away device control schedule corresponding to the customer premises. Component 928 includes a component 930 configured to identify and send a command to a fan device at the customer premises via the internet and a WiFi router to control the fan device based on the away device control schedule.
Assembly of components 900 further includes a component 932 configured to update information about the state of a fan device at a customer premises based on a command communicated to the fan device in accordance with an approved normal device control schedule or an away device control schedule, a component 934 configured to update information about the state of a fan device at a customer premises based on a command, e.g., a received command from a user device of an authorized user who is currently located outside the customer premises, said command being forwarded to the fan device by the control server acting as a relay device. Assembly of components 900 further includes a component 936 configured to receive a signal from a user indicating an away status corresponding to a customer premises and a component 938 configured to switch from using a stored normal device control schedule to using a stored away device control schedule based on a received away status indicator.
Wall control unit 1 114′ of system 100′ of
In system 100 of
In contrast, in system 100′ of
In addition, in system 100′ of
In one exemplary embodiment N=6, and wall control unit 1 114′ can, and sometimes does, control 6 fan devices (fan device 1 110′, fan device 2, fan device 3, fan device 4, fan device 5, fan device 6 112′) to turn on their fans, at the same time, via a command, e.g., a command communicated in an RF control signal sent from wall control unit 1 114′. In some such embodiments, all 6 fans are being powered from the same AC line, e.g., the same 20 A AC input power line. In some such embodiments, the 6 fans, e.g., Brushless DC motor fans, do not include an optical encoder, magnetic encoder, e.g., resolver or synchro, or Hall effect sensor. In various embodiments, (fan device 1 110′, fan device 2, fan device 3, fan device 4, fan device 5, fan device 6 112′), which can be, and sometimes are, turned on concurrently while on the same input power line, each include an exemplary AC power interface including: a varistor, a common mode choke, an X capacitor, and two Y capacitors. In some embodiments, the AC power interface of each fan device includes a multi-layer board, e.g., a 4 layer circuit board, in which one copper layer is connected to earth ground. In some embodiments, the 6 fan devices may, and sometimes do, include one or more 10 ft ceiling fans. In some embodiments, each of the 6 fan devices includes a 10 ft ceiling fan.
In another embodiment, N=10, and wall control unit 1 114′ can, and sometimes does, control 10 fan devices (fan device 1 110′, . . . , fan device 10 112′) to turn on their fans, at the same time, via a command, e.g., a command communicated in an RF control signal sent from wall control unit 1 114′. In some such embodiments, all 10 fans are being powered from the same AC line, e.g., the same 20 A AC input power line. In some such embodiments, the 10 fans, e.g., Brushless DC motor fans, do not include an optical encoder, magnetic encoder, e.g., resolver or synchro, or Hall effect sensor. In some embodiments, the 10 fan devices may, and sometimes do, include one or more 10 ft ceiling fans. In some embodiments, each of the 10 fan devices includes a 10 ft ceiling fan.
AC power, e.g., 90-264 VAC 47-63 Hz input via 16 AWG wires, is input via L terminal 342, and N (Neutral) terminal 340, and G (ground) terminal 343 is connected to earth ground. The line connected to L terminal 342 is referred to a Line IN 1003 and Line IN is fused, with fuse F1 1002, e.g., a 3.15 A fuse. After the fuse F1 1002, there are several components, varistor RV1 1004, common mode choke L1 1006, and capacitors C5 1008, C7 1010 and C11 1012, which contribute to the AC filtering, and produce a filtered AC. The neutral line 1005 is connected to the neutral terminal 340. In some embodiments, the fuse 1002 is not used in such cases the line 1003 connects the input terminal 342 to common mode choke input connection 1023 which is also connected to an input connection on the varistor 1004.
The AC power interface circuitry 322′ includes AC filtering circuit 370 which includes a varistor 1004, common mode choke 1006, a first X capacitor 1008, a first Y capacitor 1010, and a second Y capacitor 1012.
Varistor RV1 1004 is, e.g., a 510V 2.5 KA DISC 10 MM varistor, suppresses voltage spikes. Varistor 1004 has a first and a second connection. The first connection of the varistor is connected to the input line 1003. The second connection of the varistor 1004 is connected to the neutral line 1005. Common mode choke L1 1006, e.g., a 15 MH 1 A 2LN TH common mode choke, plays an important role in the system in that it that actually helps with line noise entering and exiting the fan device 300, which includes receivers. Line noise is coupled within the choke 1006 to remove the noise from the AC line. Common mode choke 1006 has two input connections 1023 and 1025 and two connections 1033 and 1035. Input connection 1023 is connected to input line 1003. Input connection 1025 is connected to neutral line 1005. Output connection 1033 is connected to line 1007 and output connection 1035 is connected to line 1009.
Capacitors C5 1008, C7 1010, and C11 1012 suppress high frequency noise, e.g., EMI (electromagnetic interference)/RFI (radio-frequency interference) ranging from approximately 2 kilohertz to 30 MHz and/or Radiated RFI which is typically found in the frequency range from 30 MHz to 10 GHz. Capacitor C5 1008, which is a X capacitor, shunts the high frequency noise across the input filtered AC lines (L 1007, N 1009). Capacitor C7 1010, which is a Y capacitor, shunts the high frequency noise on the AC filtered L line 1007 to earth ground 1031 via conductor 1030 which is connected to ground terminal 343. Connection point 1011 on copper conductor layer 1030 may be, and sometimes is used for connecting component(s) to the copper conductor layer, e.g., components C7 1010 and C11 1012. Capacitor C11 1012, which is a Y capacitor, shunts the high frequency noise on the AC filtered N line 1009 to earth ground 1031 via conductor 1030 which is connected to ground terminal 343. In one exemplary embodiment, C5 1008, C7 1010, and C11 1012 are 0.22 UF 20% 760 RAD capacitors. In another embodiment, C5 is a 220 micro Farad 275 VAC capacitor; C7 is a 820 pF 1000V capacitor and C11 is a 820 pF 1000V capacitor. The X capacitor is a class X capacitor (also known as an across the line capacitor) and the Y capacitor is a class Y capacitor (also known as a Y to ground capacitor). The X capacitor when it fails, e.g., from an overvoltage condition, shorts causing the fuse 1002 to open thereby preventing an electrical shock to users. When the Y capacitor fails it fails to an open condition which prevents electric shock hazard which otherwise would occur if the capacitor shorted on failure resulting in the loss of the ground connection.
DC power supply 324′ includes full bridge rectifier BR1 1014, capacitors C6 1016, C4 1018, and DC/DC converter circuits and filters 1020, which are coupled together as shown in
In various embodiments, the exemplary AC power interface 322′ coupled to an exemplary DC power supply 324′ of
In some embodiments, fan device 300 including the AC power interface 322′ and DC power interface 324′, uses a four layer board and the AC power interface section 322′ has an internal layer, e.g., a copper internal layer, referenced to earth ground. Having an adjacent copper layer like this, which is reference to earth ground, also helps to couple noise out of the system.
Various aspects and/or features of some, but not necessarily all, embodiments, are further discussed below.
Various embodiments are directed to use of an RF and WiFi control in a fan device, e.g., fan device 300, to control fan 303 status and speed and/or fan light 306 on/off status and intensity. The fan device 300 includes both an RF interface 314 and a WiFi interface 312. The customer premises, e.g., customer premises 1 102, includes a WiFi router 118 through which WiFi communications can be sent from a WiFi capable device, e.g., a cell phone 120, to control the fan device 300 and its various functions. While WiFi control is via a WiFi router 118 in the home, the control signals normally do not traverse the Internet 106 or another external network. Accordingly, WiFi control is possible without the need for a connection to an external network or server 108. In addition to WiFi control, control of the fan device 300 can be via an RF control device 200, e.g., a wall mounted controller. In some embodiments 120V power is supplied to the fan device 300 via the wall mounted controller 202. While 120V power may be supplied via the wall controller 202, control signals from the wall mounted controller 202 are transmitted using RF signals to the RF interface 314 of the fan device 300. The RF interface 314 uses a different frequency band than the frequency band used for WiFi signals sent to/from the WiFi router 118. In some embodiments the RF interface 314 uses an unlicensed frequency spectrum which is different than that used for WiFi signals.
Since the RF and WiFi control signals need not pass over an external communications network as in the case of systems where commands must first be sent to a network server outside a customer premises, e.g., CP1 102, and then sent from the network server to the device to be controlled, the fan device 300 can be controlled either by the wall controller 202 or a WiFi device even if a connection to the Internet or another external network is not available.
In some, but not necessarily all embodiments, the fan device 300 reports its state and/or changes in state due to received commands to a server, e.g., control server 108, e.g., located outside the customer premises 102. The communication with the external server 108 may be, and sometimes is, via a WiFi router 118 and Internet 106 connection. The server 108 logs the state information of one or more devices, e.g., fan device 1 110 and fan device N 112, at each customer premises it is associated with. The server 108 generates, e.g., automatically, a recommended normal schedule based on historical device state information including device on/off times, fan speed information and/or light intensity information. Machine learning and historical device state information may be, and sometimes is, used for generating the recommended schedule for a customer premises. The recommend normal control schedule is communicated to an individual, e.g., a customer at the customer premises to which the schedule relates. The communication of the proposed schedule may be, and sometimes is, from the server 108 via the Internet 106 and WiFi router 118 at the customer premises, e.g., CP 1 102, to which the schedule relates. The customer can approve the recommended schedule and/or provide a revised normal schedule to be used by the server 108 to control devices at the customer premises.
In addition to generating a normal control schedule for a customer premises, an away schedule to be used when a customer indicates that the customer premises is in an away state is generated. An away state corresponds to when the normal occupants of the customer premises are away from the customer premises. The away schedule is generated based on a random function so that devices, e.g. fan device 1 110, . . . , fan device N 112, will be turned on at somewhat randomized times making it difficult for a potential burglar to determine whether the devices are being controlled by an automated system or by a human present at the premises, e.g., CP 1 102. In some embodiments historical device use information is taken into consideration when the server, e.g., control server 108, automatically generates the away schedule with the on/off times being somewhat random but remaining within a reasonable time, e.g., 30 minutes or an hour, of when the devices are turned on and off when a human is present.
While a user can control the devices, e.g., a fan device 300, while in the home via the RF controller 202 or a WiFi controller, e.g., including in WT 1 120, without having to send commands outside the home, remote control of devices, e.g., fan devices, is also supported. A user can login to the control server 108 and once authenticated is allowed to send control commands to devices, e.g., fan devices 110, 112 at the home via the control server 108 and the WiFi router 118. In this way a user can control devices, e.g., fan devices 110, 112, while away from the home. In the case of commands sent via the server 108, the server 108 can, and sometimes does, update device state information based on the commands sent from the server 108 to the device, e.g., device 110, to be controlled thereby eliminating the need for the device, e.g., device 110 to report a state change to the server 108. While in some embodiments devices, e.g., fan devices 110, 112, do not report state changes to the server 108 which are in response to commands communicated by the server 108 to the device, e.g., fan device 110, being controlled, in other embodiments the devices being controlled, e.g., fan devices 110, 112, routinely report a state change to the control server 108 regardless of whether the command was from the server 108, wall controller 202 or WiFi device, e.g., WT 120, in the home.
The customer to which a home corresponds can enable/disable use of a control schedule by the server 108. For example the user can send a signal, e.g., via WT 1 120, to the control server 108 to indicate that the normal device control schedule should be used or the away device control schedule should be used or that no control schedule should be used. The signal may indicate automated control is to be set to off for the home, automated control should be set to on for the home, and, when the automated control is on whether an away state is indicated indicating that the away schedule should be used or that the premises is in a normal state and thus the normal schedule should be used.
In various embodiments a controller, e.g., wall control unit 202, with an RF interface 208 is used to control a fan device, e.g., fan device 300, which includes a fan motor 304 and may also include a lighting device, e.g., light 306. The controller 202 in some embodiments is in the form of a wall control module which may be, and sometime is, mounted in a standard electrical wall box, e.g., box 190, in a room in which the fan device, e.g., fan device 300, to be controlled is located. To simplify installation and avoid the need for more than the normal 120 v power line used to power an outlet of light, from a 120V AC perspective the controller 202 acts as a simple pass through device through which AC power is supplied to the fan device unit 300. As a safety, the controller 202 includes an AC disconnect 206 which can be used to cut all power to the fan device unit 300. The disconnect switch 206 may be in the form of a push or pull switch or a pull tab which can interrupt the power to the fan device 300.
Control of the fan device 300 is via an RF interface 208 included in the wall controller 202. In some embodiments activation of the safety disconnect switch 206 will cut power to the RF interface 208 of the wall controller 202 in addition to power to the fan device 300. In this way, in some but not necessarily all embodiments, the safety cut off 206 serves as a physical kill switch integrated into the wall controller 202 for both the wall controller 202 and the fan device 300.
The controller 202 includes inputs (216, 214, 224, 226, 220, 222, 218) for controlling fan on/off operations, light on/off operations, fan speed, e.g., up/down, and/or light intensity, e.g., fan device light output up/down, and fan direction. In some embodiments light output and fan speed can be smoothly controlled, e.g., with light intensity being controlled in a smooth fashion over a wide range of intensity value as opposed to simply a few discrete output levels. The wall controller 202 transmits RF control signals to implement or communicate commands that are generated based on the pressing or altering of the control inputs (214, 216, 218, 220, 222, 224, 226) on the wall controller 202. The control signals are transmitted to the fan device 300 using a RF frequency band which is different from that used for WiFi signals at the customer premises where the controller 202 is located.
In some embodiments, the wireless terminal 120 is not a mobile device but is instead a wall mounted device which is mounted in the customer premises in which one or more fan devices, e.g., fan devices 1 110, . . . , fan device N 112 are located. The wall mounted wireless terminal, may, and in some embodiments does, include a touch screen display upon which menus are presented to a user through which the user can select options to control the operation of one or more functions of the fan devices located at the customer premises, such as the light intensity, fan speed, fan direction, light on/off, fan on/off for one or more of the fans located at the customer premises.
In some embodiments, a full calendar year (e.g., 365 day) scheduler application in the control server allows a user to store settings, instructions and commands for the operation of one or more of a set of fans devices included on a customer premises with the fan devices then being automatically controlled by the control server in accordance with the user inputted settings, e.g., timing as to when to turn on and off the fan, turn on and off the light, set direction of the rotation of the fan blades, setting of the light intensity, setting of the fan speed, etc.
In some embodiments as previously discussed, the control server includes software instructions which when executed by a processor of the control server operate the control server to generate a recommended customer fan device schedule for an upcoming time period, e.g., one or more days, one or more weeks, or one or months, for controlling the operation of one or more functions or events, e.g., light on/off, light intensity, fan on/off, fan speed, fan direction, for one or more fan devices located at a customer premises based on historical fan device state information gathered over a time frame, e.g., a plurality of days, weeks, or months. The generated recommended customer fan device schedule, e.g., a weekly schedule of fan device events, is then transmitted by the control server to the fan device via the Internet. The fan device receives and stores the generated customer fan device schedule on its memory. A copy of the fan device recommended schedule also being retained in the memory of the control server. A user may then access the local copy of the recommended fan device schedule, e.g., the weekly fan device event schedule, residing in the fan device from a wireless terminal via WiFi and determine whether to accept or modify the recommended schedule. To the extent that the user modifies the recommended schedule the modifications to the schedule are transmitted from the fan device to the control server to update the weekly schedule for the fan device in the control server. The processor of the fan device will then automatically operate the fan device to perform the functions/events on the weekly schedule which have been approved by the user, that is if the user opt in to the recommended schedule. The fan device functions/events perform include for example, turning the fan on on a specific day at a specific time, turning off the fan on a specific day at a specific time, turning on the lights on specific days at specific times, setting the light intensity to a specific level when the light is turned on, setting the fan speed and direction when the fan is turned on, or turning off the light on a specific day at a specific time. A user may also decide to not opt in to the recommended schedule or to modify the schedule but to instead leave the fan device in a manual mode of operation for certain days of the week or the whole week. Storing a weekly schedule of fan device events on the device that may be automatically executed by the fan device if chosen by a user to operate in an automatic mode of operation provides the benefit that if the WIFI router or internet connection to the control server becomes disabled the processor of the fan device can still operate the fan device in accordance with the automated weekly schedule as selected or programmed by the user whereas if the control server is the only device to maintain the weekly schedule then when the connection between the control server and the fan device is interrupted or fails the processor of the fan device will not properly operate the fan device in accordance with the user approved weekly schedule.
A few exemplary embodiments of how the control server identifies patterns of events and uses machine learning to generate recommended schedules will now be discussed.
For example, the control server will be operated to identify patterns of events, e.g., light on, light off, light intensity setting, fan on, fan off, fan speed, fan direction, occurring a specified number of times N within a time frame, where N is an integer number, e.g., 3. The time frame may be, and in some embodiments is, a plurality of consecutive weeks such as for example 3 weeks. Identification of patterns of daily events may be, and in some embodiments are, based on the same event occurring at the same time or approximately the same time (e.g., within a time window such as +/−15 minutes) on a number M of consecutive days to not become intrusive, where M is integer number, e.g., M=3. Weekly events will be identified over the course of the time frame, e.g., three week period. For example, if the fan device is controlled to perform a particular function or event, e.g., the fan of the fan device is turned on at 8 p.m. Tuesday of week one of the time frame, the fan of the fan device is turned on at 8:06 p.m. Tuesday of week two of the time frame, and the fan of the fan device is turned on at 7:54 p.m. on week three of the time frame then the control server after analyzing the historical fan device state data for the 3 week period time frame identifies the function or event as being a pattern, e.g., turning on the fan of the fan device at approximately 8:00 p.m. on Tuesday as the fan device's fan is turned on within a 15 minute window of 8 p.m. each Tuesday, 8 p.m. being the average of the fan turn on time of the three repetitive events identified by the control server. The control server generates a recommendation that the fan for the fan device whose state data was analyzed to determine the event pattern is to be turned on at Tuesday at 8 p.m. The recommendation of time fan turn on of 8 p.m. being the average of the time of the fan turn on event occurrence for the three events identified in the pattern.
In another example, a fan of a fan device is turned on Monday at 8 p.m., Tuesday at 9:00 p.m. and Wednesday at 7 p.m. of the same week, that is on three consecutive days. The control server after analyzing the historical state data for the fan device will identify the turn on of the fan of the fan device on the three consecutive days as a pattern of event fan turn on of the fan device. In the case of identifying a pattern of events for consecutive days, the time window for the same event to occur on consecutive days may be, and in some embodiments is, different than the window for an event occurring on the same day for consecutive weeks as discussed in the previous example. In this example instead of a 15 minute window, an exemplary 60 minute window is used. The control server on determining that a pattern of turning on the fan of the fan device on three consecutive days within a 60 minute window has occurred generates a recommendation that the fan of the fan device be turned on at 8 p.m. as an option for a daily schedule. The 8:00 p.m. time of the fan turn on recommendation being generated based on the time of occurrence of the events forming the identified pattern which occurred on the three consecutive days. In this example, the 8:00 p.m. time recommended for fan turn on of the fan device being the average of the 8:00 p.m., 9:00 p.m. and 7:00 p.m. fan turn on event times of the three events in the identified pattern.
In yet another example, the fan of a fan device is turned on every Monday, Wednesday and Friday at 8:00 p.m. The same happens on week two and three of the three week time frame. The control server identifies the fan turn on events as a pattern and generates a recommended schedule based on the pattern of turning on the fan on the days and at the times the fan was turned on. For example, the control server recommends in a weekly schedule to turn on the fan of the fan device on Monday, Wednesday and Friday at 8:00 p.m. in a succeeding week.
In some, but not all, embodiments, the control server waits till the end of the time frame, e.g., 3 weeks, to analyze the fan device historical status information, identify patterns of events and generate a recommended schedule, e.g., a weekly recommended schedule of events for the fan device, based on the identified pattern of events. In some other embodiments, the control server identifies patterns of events on an on-going basis over the time frame, e.g., 3 weeks, as events are occurring using current and historical event status data for the fan device to identify fan device event patterns. The control server can then either generate a recommended schedule on an on-going basis or wait till end of the time frame to generate a recommended schedule. In some embodiments, after the first time frame, e.g., 3 weeks, expires, the control server uses a sliding time frame window to identify new event patterns and generate a new recommended schedule. For example, with the expiration of the first 3 week time frame, the control server identifies fan device event patterns and generates a recommended schedule. With a sliding time frame window of one week, the second time frame will consist of the last two weeks of the first time frame and the first week after the expiration of the first time frame. In this way, the control server will identify event patterns and generate a second recommended schedule at the end of a fourth consecutive week based on the historical event status data for the fan device of the three most recent weeks. In this way, recommended schedules are generated on a weekly basis using the three most recent weeks fan device even status data.
As previously discussed, in most, but not all embodiments, the recommended weekly schedule for each of the fan devices in a customer premises after being generated is transmitted from the control server to the fan device to which the weekly schedule pertains for customer review and/or modification and/or approval. This assumes that the customer has opted into using a weekly schedule to control the operation of the fan device and has selected to review a recommended schedule of fan device events. The automated weekly schedule and the recommended schedule can be cancelled at any time by the user through the input of a cancellation request via a control menu presented on the remote wireless WiFi control device. While the generation of recommended schedules and the operation of an automated schedule of events for a single fan device has been discussed, the control server also generates recommended schedules of events for groups of fan devices. The automated schedules for a time period, e.g., a weekly schedule is also available to automatically control the operation of groups of fans. For example, in a manufacturing facility a group of fans of a set of fan devices may be automatically turned on before the beginning of the work day. E.g., starting up fans of each device of a group of fan devices concurrently at 6:30 p.m. at a particular speed, then turning on the lights at 6:45 p.m. before the workers arrive at 7:00 a.m. and turning off the fans and lights at 8:00 p.m. after the manufacturing facility is closed for the day. Similarly, the automated weekly schedule set the fan schedules to off on Saturday, Sunday and identified holidays.
In addition to automated operation of the fan device based on a pre-programmed schedule of fan device events, e.g., a weekly 7-day schedule or 365 day (366 on leap year) schedule of fan device events, in some embodiments, the fan device can also be programmed to take actions in response to the fan device receiving one or more inputs, e.g., signals from one or more sensors or devices that provide data on the current environmental conditions of the customer premises such as for example the temperature of the customer premises and/or the room in which the fan device is located, whether the air conditioning system is on or off, or whether the heating system is on or off. For example, the fan device may be, and in some embodiments does, offer two modes of automatic operation of the fan device in connection with the HVAC system on the customer premises. In the first mode of operation, the fan device turns on the fan automatically a specified time, e.g., five minutes, after the fan device receives a message or signal indicating that the heating or air conditioning system is turned off, e.g., HVAC turns off five minutes after the fan device turns the fan on to a preset speed and direction set by the user. In a second mode of operation, the fan of the fan device is turned on to a preset speed and direction automatically when the fan device receives a message or signal indicating that the heating or air conditioning system has turned on and the fan of the fan device turns the fan off automatically after a preset amount of time, e.g., five minutes, after receiving a message or a signal that the heating or air conditioning system has turned off. The use of the fan device assists the distribution of either the cold or hot air provided by the HVAC system.
In some embodiments, the fan device is set to turn on or off automatically based on the temperature in the customer premises. For example after receiving a signal or message indicating a temperature in or on the customer premises, the processor of the fan device or the control server compares the temperature to a temperature threshold value, e.g., 80 degrees Fahrenheit, and if temperature exceeds the temperature threshold value the fan device is operated to turn on the fan if it is not already on. In some additional embodiments, the speed and direction of the fan of the fan device is also automatically set when temperatures corresponding to fan speed threshold are exceeded. For example when 80 degrees Fahrenheit is exceed the fan speed is set to low, when 85 degrees Fahrenheit is exceeded the fan speed is increased, when 90 degrees Fahrenheit is exceeded the fan speed is increased again.
In some embodiments, the control server receives messages indicating the environmental conditions at the customer premises and/or the activation or deactivation of the heating or air conditioning system, compares the environmental conditions and/or state of the heating or air conditioning system, and sends one or more commands/messages to the fan device to turn on or off the fan of the fan device and set the speed and direction of the fan thereby automatically controlling the fan device in accordance with settings of the fan device inputted by a user without the fan device requiring separate sensor inputs.
In some embodiments, the fan device is configured to be updateable via over the air (OTA) updates allowing for future features and enhancements to be downloaded into the fan device from the control server or another device. Similarly the applications being executed on the wireless WiFi terminals may be updated over the air.
As previously discussed in some embodiments, multiple fan devices are grouped together allowing for the control of all of the fan devices in the group at one time. For example, a first set of fan devices at a customer premises may be placed in a first group, e.g., fan devices on the first floor of a house may be placed in a first group such as fan devices in a living room, kitchen, hall way and dining room. These fan devices may all be mated or paired to a first wall control unit so that any RF messages sent from the first wall control unit (e.g., light on/off, fan on/off, etc.) will be received an acted upon by all of the fan devices in the first group in unison. Additionally, the control server will identify all of these fan devices as being in the first group and will allow the user to control the multiple fan devices in the first group at the same time. For example, a user may input via the wireless terminal device a group instruction to turn on all of the fans of the group in which case, all of the fans of the group will be turned on at the same time or concurrently. A customer premise may include one or more groups of fan devices. For example, while a first group of fan devices allow for the control of the fan devices in the first group such as those fan devices on the first floor or a house, a second fan group can be used to control the fan devices on the second floor of the house which are included in a second fan device group. In addition to the fan devices in a group being controlled as a group, the fan devices of the group can also still be controlled as individual fan devices. For example, at a first time the fan device group lights on event command may be given and all of the lights on the fan devices in the group will have their lights turned on. At a second later time a fan device light off command may be given to turn off a particular light on one of the fan devices in the group. While the light on that particular fan will turn off the lights on the remaining fan devices of the group will remain on. If a fan device group command to turn the lights off in the group is give the light for the individual fan device that is off will remain off while the lights on the remaining fan devices in the group will turn off. In this way, fan devices can be controlled both as a group and individually.
In some embodiments, control of one or more fan devices at a customer premise may be shared with one or more users. For example, control of fan devices at a customer premise can be shared by parents and children, employees, and guests. In an exemplary embodiment a guest is given permission to control one or more fan devices in a customer premises. The owner or operator selects which fan devices the guest can control and inputs this information into the control server and/or the fan device. The owner or operator of the customer premises at which the fan devices are located then sends an invite message to a guest's mobile device. In response to the invite the guest via his or her mobile device would, after authentication such as entry of a password provided by the owner or operator of the customer premises to the guest, be allowed to login to an application running on the control server or the fan device from which the guest could operate the fan device using the guest's mobile device. As previously discussed, the guest's access may be restricted to certain fan devices at the customer premises such as for example allowing the guest to control the fan device(s) in the guest bedroom and/or living room while being restricted from controlling the fan devices in other areas of the customer premises. The owner or operator of the customer premises also concurrently having the ability to control the same devices as the guest. In this way, multiple users may control the same fan devices. When the owner or operator of the customer premises decides to end the guest's access to the system and control of the fans device(s) the owner or operator of the customer premises inputs a request or command to the control server and/or fan device(s) indicating that the guest is no longer allowed to access the system and/or control the fan devices upon which the control server and/or fan device prevents the guest from accessing the system, e.g., by no longer accepting the login credentials, e.g., user id or password, of the guest.
In some embodiments, the fan devices include a sleep mode in which the user can set independent timers for when the fan of the fan device and when light of the fan device can be turned off e.g., after 45 minutes after activation of sleep mode, so that when the sleep timer for the fan expires the fan of the fan device turns off and when the sleep timer for the light of the fan device expires, the light of the fan device will automatically turn off. Additionally, a synch command activated from a menu presented to the user on the WiFi mobile device allows the independent sleep mode timer for the fan and light of the fan device to be synchronized so that if they are set to different time values they will synchronized and will both turn off at the same time. The independent sleep timers being synchronized to the shorter time period of either the fan sleep timer value or the light sleep timer value of the sleep timer values being synchronized.
A control method comprising: receiving, at a fan device including a radio frequency signal receiver and a WiFi interface, a first radio frequency (RF) control signal from a control unit, said fan device and said control unit being located at a customer premises; implementing, at the fan device, an operation in response to a first command communicated by the first RF control signal; and operating the fan device to communicate to a server located outside the customer premises, via the WiFi interface, information indicating the operation implemented in response to the first command. (For example, the fan device sends a report identifying itself, i.e., the fan device being controlled, the time the command was implemented, the operation performed and identifies the customer premises to allow the server to create a log of the state of the fan device and create a history record of the state, e.g., on/of and intensity of the various devices at the customer premises to facilitate learning of use patterns and thereby allow for automated schedule generation for both a normal and away schedule both of which maybe and sometimes are machined learned based on the information reported to the server in the network).
The method of Method Embodiment 1, wherein said fan device and said control unit are located in the same room.
The method of Method Embodiment 1, wherein said control unit is a wall mounted unit through which power is supplied to the fan device, said first RF control signal being a wireless signal transmitted from an RF transmitter in the control unit to an RF receiver in the fan device.
The method of Method Embodiment 3, wherein the control unit does not include a WiFi interface.
The method of Method Embodiment 1, wherein said first command is one of: a fan on command, a fan off command, a fan power state change command, a fan speed up command, a fan speed down command, a fan direction change command, a light on command, a light off command, a light power state change command, a light increase command, a light decrease command.
The method of Method Embodiment 1, wherein said RF control signal is sent using an RF frequency which is not used for WiFi signals. It should be appreciated that the RF and WiFi interfaces while both being wireless interfaces are different interfaces and use different frequency bands and different communications protocols.
The method of Method Embodiment 6, further comprising: operating a WiFi router located at the customer premises to receive a first WiFi control signal from a wireless terminal (e.g., cell phone) located at the customer premises, said first WiFi control signal communicating a second command used to control the fan device; operating the WiFi router to communicate, via a WiFi signal, the second command to the fan device; and operating the fan device to implement the second command.
The method of Method Embodiment 7, further comprising: operating the fan to communicate to the server located outside the customer premises, via the WiFi interface, information indicating the operation implemented in response to the second command.
The method of Method Embodiment 8, wherein the second command is communicated from the wireless terminal to the fan device via the WiFi router located in the customer premises without said second command traversing a network outside the customer premises. (Thus, in at least some embodiments communication of the second command does not depend or involve communication over a network outside the customer premises and the fan device can be controlled from within the house via WiFi even if an Internet or server connection to the server is not present or available.)
The method of Method Embodiment 9, further comprising: operating the server to receive a third command directed to the first fan device; and operating the server to communicate the third command via the Internet and said WiFi router to the fan device. (For example, method embodiment 10 relates to cases in which it is intended to report control of the fan device via a remotely located device, e.g., a WT such as a cell phone outside the first customer premises, which sends control signals through the server for delivery to the first fan device, in the case where the control signals pass through the server the fan device being controlled may not send back a message reporting implementation of the communicated command and the sever can update the state information based on the knowledge that the fan was instructed to perform the operation and/optionally, an acknowledgement from the device indicating that the control message was successfully received and/or acted upon.)
The method of Method Embodiment 10, further comprising: operating the server to update information about the state of one or more devices at the first customer premises based on the third command communicated to the fan device.
The method of Method Embodiment 11, wherein said updating of the information about the state of one or more devices at the first customer premises is performed in response to transmitting the third command from the server (without receiving a report of the command being implemented at the fan device).
The method of Method Embodiment 9, further comprising: operating the server to generate a proposed normal device control schedule for the first customer premises (e.g., fan and/or lighting control schedule including speed and/or light intensity schedule) from stored information indicating the state of one or more devices at the first customer premises over a period of time (e.g., two or more weeks); communicate from the server (e.g., via the Internet and WiFi router located at the first customer premises) the proposed device control schedule to a device corresponding to the first customer premise (e.g., cell phone of a user who is located at the first customer premises); receive at the server a message indicating approval of the proposed normal device control schedule for the first customer premises or a revised schedule for the first customer premises; and storing as an approved normal control schedule for the first customer premises the approved proposed normal device control schedule or the revised schedule.
The method of Method Embodiment 13, further comprising: operating the server to control one or more devices at the first customer premises based on the stored approved normal device control schedule, said one or more devices including the first fan device.
The method of Method Embodiment 14, wherein operating the server to control one or more devices at the first customer premises based on the stored approved normal device control schedule includes transmitting a control signal from the server to the first fan device via the Internet and WIFi router to control the fan device to turn on at a time indicated by said approved normal control schedule.
The method of Method Embodiment 13, further comprising: operating the server to generate an away schedule to be used to control one or more device at the first customer premises when the customer indicates they are away from the customer premises.
The method of Method Embodiment 16, wherein operating the server to generate an away schedule includes generating said away schedule as a function of a random function used to at least partially randomize the on or off times of one or more devices.
The method of Method Embodiment 17, wherein operating the server to generate the away schedule includes using information about past device on and off status in combination with said random function to control the on and off times of at least one device, said on and off times deviating from historical on and off times by an amount of time which does not exceed a set maximum amount of time (e.g., 30 minutes) and which is determined by said random function. (E.g., once the historical on/off times of a light on the fan device are known, the random function is used to change the on/off time in a random function but keep it within 30 minutes or so of the normal on/off time so that the on/off pattern is not identical from day to day but within an expected normal range that might occur to a human getting home or moving around the home which would not be identical each day but might not deviate greatly, e.g., by more than an hour, from day to day.)
The method of Method Embodiment 16, further comprising; receiving, at the server, a signal from a user indicating an away status; and switching, at the server, from using the stored approved normal schedule to using the stored away schedule to control the one or more devices at the first customer premises.
A system (100) comprising: a fan device (110) comprising: a fan motor (304); a radio frequency (RF) signal receiver (360) configured to receive radio frequency (RF) control signals from a control unit (114), said fan device (110) and said control unit (114) being located at a customer premises (102); a WiFi interface (312); a fan motor control circuit (308) configured to control the fan motor (304) in response to a received first radio frequency control signal, said first radio frequency control signal communicating a first command; and a first processor (316) configured to communicate to a server (108), located outside the customer premises (102), via the WiFi interface (312), information indicating an operation implemented in response to the first command.
The system of System Embodiment 1, wherein said fan device further comprises: a light (306); and a light control circuit (310) configured to control the light (306) in response to a received second radio frequency control signal, said second radio frequency control signal communicating a second command; and wherein said first processor (316) is further configured to communicate to said server (108), via the WiFi interface (312), information indicating an operation implemented in response to said second command.
The system (100) of System Embodiment 1a, wherein said fan device (110) and said control unit (114) are located in the same room.
The system (100) of System Embodiment 1a, further comprising said control unit (114); wherein said control unit (114) includes an RF transmitter (228); and wherein said control unit (114) is a wall mounted unit through which power is supplied to the fan device (110), said first RF control signal and said second RF control signal being wireless signals transmitted from said RF transmitter (228) in the control unit (114) to said RF signal receiver (360) in the fan device (110).
The system (110) of System Embodiment 1B, wherein the control unit (114) does not include a WiFi interface.
The system (100) of System Embodiment 1A, wherein said first RF control signal communicates one of: a fan on command, a fan off command, a fan power state change command, a fan speed up command, a fan speed down command, a fan direction change command; and wherein said second RF control signal communicates one of: a light on command, a light off command, a light power state change command, a light increase command, a light decrease command.
The system (100) of System Embodiment 1a, wherein said first RF control signal and said second RF control signal are sent using RF frequencies which are not used for WiFi signals.
The system (100) of System Embodiment 3, further comprising: a WiFi router (118) located at the customer premises, said WiFi router (118) comprising: a receiver (195) configured to receive a first WiFi control signal from a wireless terminal (120) located at the customer premises (102), said first WiFi control signal communicating a third command used to control the fan device (110); a transmitter (196) configured to communicate, via a WiFi signal, the third command to the fan device (110); and wherein said first processor (316) is configured to control at least one of the fan motor control circuit (308) or the light control circuit (310) to implement the third command.
The system (100) of System Embodiment 4, further comprising: wherein said first processor (316) is configured to control the WiFi interface (312) in said fan device (110) to send information indicating the operation implemented in response to the third command.
The system (100) of System Embodiment 5, further comprising: said wireless terminal (120), wherein said wireless terminal (120) includes: a WiFi interface (802); and a fan device control application (828) configured to generate said third command in response to user input; and wherein the third command is communicated from the wireless terminal (120) to the fan device (110) via the WiFi router (108) located in the customer premises (102) without said third command traversing a network outside the customer premises (102).
The system (100) of System Embodiment 6, further comprising: said server (108), wherein said server (108) includes a second processor (704) configured to: operating the server (108) to receive a fourth command directed to the first fan device (110); and operating the server (108) to communicate the fourth command via the Internet (106) and said WiFi router (118) to the fan device (110).
The system (100) of System Embodiment 7, wherein said second processor (704) is further configured to: operating the server (108) to update information about the state of one or more devices at the first customer premises (102) based on the fourth command communicated to the fan device (110).
The system (100) of System Embodiment 8, wherein said updating of the information about the state of one or more devices at the first customer premises is performed in response to transmitting the fourth command from the server (108).
The system (100) of System Embodiment 6, wherein said second processor (704) is further configured to: operating the server (108) to generate a proposed normal device control schedule for the first customer premises (102) from stored information indicating the state of one or more devices (110, 112) at the first customer premises over a period of time; operate the server (108) to send (e.g., via the Internet (106) and WiFi router (118) located at the first customer premises (102)) the proposed device control schedule to a device (120) corresponding to the first customer premise (102) (e.g., cell phone of a user who is located at the first customer premises); operate the server (108) to receive a message indicating approval of the proposed normal device control schedule for the first customer premises (102) or a revised schedule for the first customer premises (102); and operate the server (108) to store as an approved normal control schedule for the first customer premises the approved proposed normal device control schedule or the revised schedule.
The system (100) of System Embodiment 10, wherein said second processor (704) is further configured to: operating the server (108) to control one or more devices (110, 112) at the first customer premises (102) based on the stored approved normal device control schedule, said one or more devices (110, 112) including the first fan device (110).
The system (100) of System Embodiment 11, wherein said second processor (704) is configured to: operate the server (108) to send a control signal from the server (108) to the first fan device (110) via the Internet (106) and WIFi router (110) to control the fan device (110) to turn on at a time indicated by said approved normal control schedule, as part of being configured to operate the server (108) to control one or more devices (110, 112) at the first customer premises (102) based on the stored approved normal device control schedule.
The system (100) of System Embodiment 10, wherein said second processor (704) is further configured to: operate the server (108) to generate an away schedule to be used to control one or more device (110, 112) at the first customer premises (102) when the customer indicates they are away from the customer premises (102).
The system (100) of System Embodiment 13, wherein said second processor (704) is configured to: generate said away schedule as a function of a random function used to at least partially randomize the on or off times of one or more devices, as part of being configured to operate the server to generate an away schedule.
The system (100) of System Embodiment 14, wherein said second processor (704) is configured to use information about past device on and off status in combination with said random function to control the on and off times of at least one device, said on and off times deviating from historical on and off times by an amount of time which does not exceed a set maximum amount of time (e.g., 30 minutes) and which is determined by said random function, as part of being configured to operate the server to generate the away schedule. (E.g., once the historical on/off times of a light on the fan device are known the random function is used to change the on/off time in a random function but keep it within 30 minutes or so of the normal on/off time so that the on/off pattern is not identical from day to day but within an expected normal range that might occur to a human getting home or moving around the home which would not be identical each day but might not deviate greatly, e.g., by more than an hour, from day to day.)
The system (100) of System Embodiment 13, wherein said server (108) further comprises: a receiver (714) configured to receive a signal from a user indicating an away status; and wherein said second processor (704) is further configured to control the server (108) to switch from using the stored approved normal schedule to using the stored away schedule to control the one or more devices (110, 112) at the first customer premises (102).
A system (100) comprising: one or more fan devices (110, 112), said one or more fan devices including a first fan device (110, 300), said first fan device (110, 300) including: a first Direct Current (DC) fan motor (304); a first Alternating Current (AC) power interface circuit (322, 322′) including: first AC signal and ground input connections (342, 340, 343); a first AC filtering circuit (370); and AC signal output connections (1111, 1113); a first Direct Current (DC) power supply circuit (324, 324′) connected to the AC signal output connections (1111, 1113) of the first AC power interface circuit (322′) that provides power to the first DC fan motor (304).
The system (100) of system embodiment 1, wherein said first DC fan motor (304) is a brushless DC fan motor.
The system (100) of system embodiment 2, wherein said first DC fan motor does not include an optical sensor, an optical encoder, a magnetic encoder, a resolver, a synchro, or a Hall effect sensor.
The system (100) of system embodiment 3, wherein said first AC signal and ground input connections (342, 340, 343) include three terminals, said three terminals including: a first terminal (342) which is a line input terminal, a second terminal (340) which is a neutral terminal, and a third terminal (343) which is a ground terminal, said first and second terminals being for receiving an AC input signal and said third terminal for connection to earth ground (1031), said line input terminal 342 being coupled to an AC input line (1003) of the first AC power interface (322′), said neutral terminal (340) being coupled to a neutral line (1005) of the first AC power interface (322′).
The system (100) of system embodiment 4 wherein the first AC filtering circuit (370) includes: a varistor (1004) that suppresses voltage spikes, said varistor (1004) being connected across the AC input line (1003) and the neutral line (1005) connected to said neutral terminal (340); a common mode choke (1006) with a first input connection (1023) connected to the AC input line (1003) and a second input connection (1025) connected to the neutral line (1005), said common mode choke (1006) suppressing noise; a first X capacitor (1008) coupled across output connections (1033, 1035) of the common mode choke (1006), said first X capacitor (1008) suppressing high frequency noise by shunting high frequency noise across filtered AC lines (1007, 1009) of said first AC power interface (322′), said filtered AC lines (1007, 1009) including a filtered AC input line (1007) and a filtered AC neutral line (1009); a first Y capacitor (1010) connected across the filtered AC input line (1007) and a conductor (1030) connected to the ground terminal (343) of said AC power interface circuit (322′) that suppresses high frequency noise by shunting high frequency noise on the filtered AC neutral line (1007) to the earth ground (1031); and a second Y capacitor (1012) connected across the filtered AC neutral line (1009) and the conductor (1030) connected to the ground terminal (343) that shunts high frequency noise on the filtered AC neutral line (1009) to earth ground (1031).
The system of system embodiment 5 wherein the first AC power interface circuit (322′) includes a multi-layer board in which the conductor connected to the ground terminal (343) is an internal layer (1030) of the multi-layer board made of copper that couples noise out of the system and decreases signal interference, said first Y capacitor (1010) and second Y capacitor (1012) being coupled to said earth ground via said copper layer (1030).
The system of system embodiment 5 wherein the first AC power interface circuit (322 or 322′) does not include a Negative Temperature Coefficient (NTC) InRush Protection device.
The system of system embodiment 7 wherein said first DC power supply circuit (324 or 324′) includes: a full bridge rectifier (1014), a plurality of capacitors (1016, 1018) connected in parallel across output connections (1015, 1017) of the full bridge rectifier (1014); and a DC/DC converter circuit (1020) with filtering circuitry; a plurality of output connections (Vbus 1022, DC voltage out 1 1024, DC voltage out N 1026) on which a plurality of different DC output voltages are supplied.
The system (100) of system embodiment 8, wherein said first fan device (110, 300) further includes: a first fan motor control circuit (308) configured to control the fan motor (304) in response to a received first radio frequency control signal, said first radio frequency control signal communicating a first command.
The system (100) of system embodiment 9, wherein said first fan motor control circuit (308) includes an Insulated Gate Bipolar Transistor (IGBT) module, a processor, and analog feedback circuitry.
The system (100) of system embodiment 8, wherein said first AC power interface circuit (322′) further includes a fuse (1002) connected between said first terminal (342) and a connection of the varistor (1004), said fuse coupling said first terminal to said varistor (1004) and an input (1023) of said common mode choke (1006).
The system (100) of system embodiment 9, wherein said first fan device (110) is one of a plurality of fan devices (110, 112) powered from the same AC source which when started concurrently do not experience being off kilter in time or speed.
The system (100) of system embodiment 9, wherein said plurality of fan devices includes three fan devices (110, 111, 112), said first fan device (110), a second fan device (111), and a third fan device (112); wherein the first fan device (110), the second fan device (111) and the third fan device (112) are daisy changed together so that power is connected to the first fan device (110) and from the first fan device (110) to the second fan device (111) and from the second fan device to the third fan device (112); wherein operating the three fan devices (110, 111, 112) currently does not result in any of the three fan devices being off kilter in time or speed upon concurrent start up of said first, second and third fan devices; wherein said second fan device (111) includes: a second Direct Current (DC) fan motor (304); a second Alternating Current (AC) power interface circuit (322, 322′) including: second AC signal and second ground input connections (342, 340, 343); a second AC filtering circuit (370); and second AC signal output connections (1111, 1113); a second Direct Current (DC) power supply circuit (324, 324′) connected to the second AC signal output connections (1111, 1113) of the second AC power interface circuit (322′) that provides power to the second DC fan motor (304); and wherein said third fan device (112) includes: a third Direct Current (DC) fan motor (304); a third Alternating Current (AC) power interface circuit (322, 322′) including: third AC signal and third ground input connections (342, 340, 343); a third AC filtering circuit (370); and third AC signal output connections (1111, 1113); a third Direct Current (DC) power supply circuit (324, 324′) connected to the third AC signal output connections (1111, 1113) of the third AC power interface circuit (322′) that provides power to the third DC fan motor (304).
The system of system embodiment 13, wherein said second AC filtering circuit (370) of the second fan device (111) includes:
a second varistor (1004) that suppresses voltage spikes, said second varistor (1004) being connected across a second AC input line (1003) connected to a second input line terminal (342) of the second AC power interface circuit and a second neutral line (1005) connected to a second neutral terminal (340) of the second AC power interface circuit; a second common mode choke (1006) with a first input connection (1023) connected to the second AC input line (1003) and a second input connection (1025) connected to the second neutral line (1005), said second common mode choke (1006) suppressing noise;
a second X capacitor (1008) coupled across output connections (1033, 1035) of the second common mode choke (1006), said second X capacitor (1008) suppressing high frequency noise by shunting high frequency noise across second filtered AC lines (1007, 1009) of said second AC power interface (322′), said second filtered AC lines (1007, 1009) including a second filtered AC input line (1007) and a second filtered AC neutral line (1009); a third Y capacitor (1010) connected across the second filtered AC input line (1007) and a second conductor (1030) connected to the second ground terminal (343) of said second AC power interface circuit that suppresses high frequency noise by shunting high frequency noise on the second filtered AC neutral line (1007) to the earth ground (1031); and a fourth Y capacitor (1012) connected across the second filtered AC neutral line (1009) and the second conductor (1030) connected to the second ground terminal (343) of the second AC power interface circuit that shunts high frequency noise on the second filtered AC neutral line (1009) to earth ground (1031); and wherein said third AC filtering circuit (370) of the third fan device (112) includes: a third varistor (1004) that suppresses voltage spikes, said third varistor (1004) being connected across a third AC input line (1003) connected to a third input terminal (342) of the third AC interface circuit and a third neutral line (1005) connected to a third neutral terminal (340) of the third AC interface circuit; a third common mode choke (1006) with a first input connection (1023) connected to the third AC input line (1003) and a second input connection (1025) connected to the third neutral line (1005), said third common mode choke (1006) suppressing noise; a third X capacitor (1008) coupled across output connections (1033, 1035) of the third common mode choke (1006), said third X capacitor (1008) suppressing high frequency noise by shunting high frequency noise across third filtered AC lines (1007, 1009) of said third AC power interface (322′), said third filtered AC lines (1007, 1009) including a third filtered AC input line (1007) and a third filtered AC neutral line (1009); a five Y capacitor (1010) connected across the third filtered AC input line (1007) and a third conductor (1030) connected to the third ground terminal (343) of said third AC power interface circuit (322′) that suppresses high frequency noise by shunting high frequency noise on the third filtered AC neutral line (1007) to the earth ground (1031); and a sixth Y capacitor (1012) connected across the third filtered AC neutral line (1009) and the third conductor (1030) connected to the third ground terminal (343) that shunts high frequency noise on the third filtered AC neutral line (1009) to earth ground (1031).
A system comprising: a set of fan devices (110, 111, 112) connected to a single AC power supply source; each of said fan devices (110, 111, 112) in the set of fan devices including: a Direct Current (DC) fan motor (304), said DC fan motor (304) being a brushless DC fan motor that does not include an optical sensor, an optical encoder, a magnetic encoder, a resolver, a synchro, or a Hall effect sensor; an Alternating Current (AC) power interface circuit (322 or 322′) including: AC signal and ground input connections (342, 340, 343); an AC filtering circuit (370), said AC filtering circuit (370) including: a varistor (1004) that suppresses voltage spikes, said varistor (1004) being connected across an AC input line (1003) connected to an input terminal (342) and a neutral line (1005) connected to a neutral terminal (340); a common mode choke (1006) with a first input connection (1023) connected to the AC input line (1003) and a second input connection (1025) connected to the neutral line (1005), said common mode choke (1006) suppressing noise; a first X capacitor (1008) coupled across output connections (1033, 1035) of the common mode choke (1006), said first X capacitor (1008) suppressing high frequency noise by shunting high frequency noise across filtered AC lines (1007, 1009) of said first AC power interface (322′), said filtered AC lines (1007, 1009) including a filtered AC input line (1007) and a filtered AC neutral line (1009); a first Y capacitor (1010) connected across the filtered AC input line (1007) and a conductor (1030) connected to the ground terminal (343) of said AC power interface circuit (322′) that suppresses high frequency noise by shunting high frequency noise on the filtered AC neutral line (1007) to the earth ground (1031); and a second Y capacitor (1012) connected across the filtered AC neutral line (1009) and the conductor (1030) connected to the ground terminal (343) that shunts high frequency noise on the filtered AC neutral line (1009) to earth ground (1031); and AC signal output connections (1111, 1113); and a Direct Current (DC) power supply circuit (324 or 324′) connected to the AC signal output connections (1111, 1113) of the AC power interface circuit (322′) that provides power to the DC fan motor (304).
The system (100) of system embodiment 14 wherein the lines comprise electrically conductive material.
The system (100) of system embodiment 14 wherein the lines are metallic traces.
The system (100) of system embodiment 15 wherein the lines comprise electrically conductive material.
The system (100) of system embodiment 15 wherein the lines are metallic traces.
The system of system embodiment 15 wherein the AC power interface circuit (322′) includes a multi-layer board in which the conductor connected to the ground terminal (343) is an internal layer (1030) of the multi-layer board made of copper that couples noise out of the system and decreases signal interference, said first Y capacitor (1010) and second Y capacitor (1012) being coupled to said earth ground via said copper layer (1030).
The system of system embodiment 20 wherein the AC power interface circuit (322 or 322′) does not include a Negative Temperature Coefficient (NTC) InRush Protection device.
The system of system embodiment 21 wherein said DC power supply circuit (324 or 324′) includes: a full bridge rectifier (1014), a plurality of capacitors (1016, 1018) connected in parallel across output connections (1015, 1017) of the full bridge rectifier (1014); and a DC/DC converter circuit (1020) with filtering circuitry; a plurality of output connections (1022, 1024, 1026) on which a plurality of different DC output voltages are supplied.
The system (100) of system embodiment 22, wherein each of said fan devices (110, 300) further includes: a fan motor control circuit (308) configured to control the fan motor (304) in response to a received first radio frequency control signal, said first radio frequency control signal communicating a first command.
The system (100) of system embodiment 23, wherein said fan motor control circuit (308) includes an Insulated Gate Bipolar Transistor (IGBT) module, a processor, and analog feedback circuitry.
The system of system embodiment 8, wherein said plurality of capacitors consists of two electrolytic capacitors (C4 1016, C6 1018)
The system of system embodiment 5 wherein said first AC power interface (322′) operates over an input AC voltage range of 90 VAC to 264 VAC with a frequency of 47 Hertz to 63 Hertz and wherein said DC power supply circuit 324′ produces a DC voltage bus (1022) output voltage of 170 Volts DC that is used to directly power the fan motor (304).
The system of system embodiment 5 wherein said first AC power interface (322′) operates over an input AC voltage range of 90 VAC to 264 VAC with a frequency range of 47 Hertz to 63 Hertz and wherein said DC power supply circuit (324′) produces a DC voltage bus (1022) output voltage of 170 Volts DC (or approximately 170 Volts DC).
The system of system embodiment 5 wherein said fan motor (304) is part of a fan 303 which includes a fan shaft 338 and a fan blade unit 336.
The system of system embodiment 8 wherein said first AC power interface (322′) operates over an input AC voltage range of 90 VAC to 264 VAC (or approximately 90 VAC to 264 VAC) with a frequency range of 47 Hertz to 63 Hertz and wherein said DC power supply circuit (324′) produces a DC voltage bus (1022) output voltage of 170 Volts DC (or approximately 170 Volts DC), 16 V DC output voltage, and a 3.3 VDC output.
A fan device controller (202) including: an AC voltage input (237); an AC output (241) for supplying power to a fan device (300); an RF signal interface (208) including an RF signal transmitter (228) for transmitting commands to a device (300) to be controlled; an RF controller (212) for controlling the RF signal interface (212) to send control signals including one or more commands to said fan device (300); and a disconnect switch (206) for disconnecting said AC output (241) from said AC input (237) when said disconnect switch (206) is switched to a disconnect state from a connect state.
The fan device controller (200) of Apparatus Embodiment 1, further comprising: a fan control input (216) for turning a fan (304) on or off; and a light control input (214) for turning a light (306) on or off.
The fan device controller (202) of Apparatus Embodiment 2, further comprising: a light up input (220) coupled to said RF controller (212); and a light down input (222) coupled to said RF controller (212).
The fan device controller (202) of Apparatus Embodiment 3, further comprising: a fan speed up input (224) coupled to said RF controller (212); and a fan speed down input (226) coupled to said RF controller (212).
The fan device controller (202) of Apparatus Embodiment 4, further comprising: a fan reverse input (218) coupled to said RF controller (212).
The fan device controller (202) of Apparatus Embodiment 5, further comprising: a DC power supply (210) connected to said disconnect switch (206) and to said RF controller (212), said DC power supply (206) receiving AC power from said disconnect switch (206) and supplying DC power generated from said AC power to the RF controller (212).
The fan device controller (202) of Apparatus Embodiment 6, wherein switching the disconnect switch to a disconnect state cuts power to both the AC output (243) and to said DC power supply (210) thereby cutting power to a fan device (300) coupled to said fan device controller (202) and to the RF controller (212) at the same time.
The fan device controller (202) of Apparatus Embodiment 7, wherein said RF controller (212) includes a processor (213); and wherein said processor (213) is configured to: generate commands in response to input received via one of the inputs (214, 216, 218, 220, 222, 224 or 226) included in said fan device controller (202); and control said RF interface (208) to transmit said commands in RF signals to the fan device (300).
The fan device controller (202) of Apparatus Embodiment 8, wherein said fan device controller (202) is configured to fit in an electrical box (190) in a wall (191) of a customer premises (102).
The techniques of various embodiments may be implemented using software, hardware and/or a combination of software and hardware. Various embodiments are directed to apparatus, e.g., fan devices, control server, WiFi router, control units, mobile devices. Various embodiments are also directed to methods, e.g., method of controlling and/or operating devices, e.g., control server device, mobile device, control units. Various embodiments are also directed to machine, e.g., computer, readable medium, e.g., ROM, RAM, CDs, hard discs, etc., which include machine readable instructions for controlling a machine to implement one or more steps of a method. The computer readable medium is, e.g., non-transitory computer readable medium.
It is understood that the specific order or hierarchy of steps in the processes and methods disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes and methods may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented. In some embodiments, one or more processors are used to carry out one or more steps or elements of the described methods.
In various embodiments each of the steps or elements of a method are implemented using one or more processors. In some embodiments, each of the steps or elements are implemented using hardware circuitry.
In various embodiments elements described herein are implemented using one or more components to perform the steps corresponding to one or more methods, for example, generating, sending, comparing, determining and/or transmission steps. Thus, in some embodiments various features are implemented using components or in some embodiments logic such as for example logic circuits. Such components may be implemented using software, hardware or a combination of software and hardware. Many of the above described methods or method steps can be implemented using machine executable instructions, such as software, included in a machine readable medium such as a memory device, e.g., RAM, floppy disk, etc. to control a machine, e.g., general purpose computer with or without additional hardware, to implement all or portions of the above described methods, e.g., in one or more elements. Accordingly, among other things, various embodiments are directed to a machine-readable medium, e.g., a non-transitory computer readable medium, including machine executable instructions for causing a machine, e.g., processor and associated hardware, to perform one or more of the steps of the above-described method(s). Some embodiments are directed to a device, e.g., fan device, mobile device, WiFi device, wall unit controller, including a processor configured to implement one, multiple or all of the steps of one or more methods of the invention.
In some embodiments, the processor or processors of one or more devices, e.g., control server, fan device, mobile device, wall control unit are configured to perform the steps of the methods described as being performed by the devices. The configuration of the processor may be achieved by using one or more components, e.g., software components, to control processor configuration and/or by including hardware in the processor, e.g., hardware components, to perform the recited steps and/or control processor configuration. Accordingly, some but not all embodiments are directed to a device, e.g., fan device, control unit device, mobile server, control server, WiFi router, with a processor which includes a component corresponding to each of the steps of the various described methods performed by the device in which the processor is included. In some but not all embodiments a device, e.g., fan device, control unit device, mobile server, control server, WiFi router, includes a component corresponding to each of the steps of the various described methods performed by the device in which the processor is included. The components may be implemented using software and/or hardware.
Some embodiments are directed to a computer program product comprising a computer-readable medium, e.g., a non-transitory computer-readable medium, comprising code for causing a computer, or multiple computers, to implement various functions, steps, acts and/or operations, e.g. one or more steps described above. Depending on the embodiment, the computer program product can, and sometimes does, include different code for each step to be performed. Thus, the computer program product may, and sometimes does, include code for each individual step of a method, e.g., a method of controlling a fan device, control unit device, mobile server, control server, WiFi router. The code may be in the form of machine, e.g., computer, executable instructions stored on a computer-readable medium, e.g., a non-transitory computer-readable medium, such as a RAM (Random Access Memory), ROM (Read Only Memory) or other type of storage device. In addition to being directed to a computer program product, some embodiments are directed to a processor configured to implement one or more of the various functions, steps, acts and/or operations of one or more methods described above. Accordingly, some embodiments are directed to a processor configured to implement some or all of the steps of the methods described herein. The processor may be for use in, e.g., a fan device, a communications device such as a WiFi mobile device, a control unit, control server or other device described in the present application.
Numerous additional variations on the systems, methods and apparatus of the various embodiments described above will be apparent to those skilled in the art in view of the above description and the claims which follow. Such variations are to be considered within the scope of the invention.
The present application is a continuation in part of U.S. patent application Ser. No. 15/871,047 filed Jan. 14, 2018, a continuation in part of U.S. patent application Ser. No. 15/871,044 filed Jan. 14, 2018, claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 62/617,152 filed on Jan. 12, 2018 and claims the benefit of U.S. Provisional Patent Application Ser. No. 62/617,274 filed on Jan. 14, 2018 with each of the listed applications hereby being expressly incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9589461 | Byrne et al. | Mar 2017 | B1 |
| 20070110192 | Steiner | May 2007 | A1 |
| 20130073431 | Suro et al. | Mar 2013 | A1 |
| 20140101082 | Matsuoka et al. | Apr 2014 | A1 |
| 20140177900 | Berkman et al. | Jun 2014 | A1 |
| 20140270714 | Osminer et al. | Sep 2014 | A1 |
| 20150351203 | Shen et al. | Dec 2015 | A1 |
| 20170104426 | Mills | Apr 2017 | A1 |
| 20190219059 | Stefankiewicz et al. | Jul 2019 | A1 |
| 20190219060 | Stefankiewicz et al. | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2017151682 | Sep 2017 | WO |
| Entry |
|---|
| Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration with the International Search Report and the Written Opinion from International application No. PCT/US 2019/013389 dated May 13, 2019, pp. 1-23. |
| Number | Date | Country | |
|---|---|---|---|
| 20190220071 A1 | Jul 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62617274 | Jan 2018 | US | |
| 62617152 | Jan 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15871044 | Jan 2018 | US |
| Child | 16246453 | US | |
| Parent | 15871047 | Jan 2018 | US |
| Child | 15871044 | US |
