Patent Grant
9291359
This patent specification relates to a thermostat user interface. For some embodiments, this patent specification relates to a thermostat user interface of a thermostat that controls and monitors a heating, cooling, and air conditioning (HVAC) system.
While substantial effort and attention continues toward the development of newer and more sustainable energy supplies, the conservation of energy by increased energy efficiency remains crucial to the world's energy future. According to an October 2010 report from the U.S. Department of Energy, heating and cooling account for 56% of the energy use in a typical U.S. home, making it the largest energy expense for most homes. Along with improvements in the physical plant associated with home heating and cooling (e.g., improved insulation, higher efficiency furnaces), substantial increases in energy efficiency can be achieved by better control and regulation of home heating and cooling equipment. By activating heating, ventilation, and air conditioning (HVAC) equipment for judiciously selected time intervals and carefully chosen operating levels, substantial energy can be saved while at the same time keeping the living space suitably comfortable for its occupants.
Historically, however, most known HVAC thermostatic control systems have tended to fall into one of two opposing categories, neither of which is believed be optimal in most practical home environments. In a first category are many simple, non-programmable home thermostats, each typically consisting of a single mechanical or electrical dial for setting a desired temperature and a single HEAT-FAN-OFF-AC switch. While being easy to use for even the most unsophisticated occupant, any energy-saving control activity, such as adjusting the nighttime temperature or turning off all heating/cooling just before departing the home, must be performed manually by the user. As such, substantial energy-saving opportunities are often missed for all but the most vigilant users. Moreover, more advanced energy-saving settings are not provided, such as the ability to specify a custom temperature swing, i.e., the difference between the desired set temperature and actual current temperature (such as 1 to 3 degrees) required to trigger turn-on of the heating/cooling unit.
In a second category, on the other hand, are many programmable thermostats, which have become more prevalent in recent years in view of Energy Star (US) and TCO (Europe) standards, and which have progressed considerably in the number of different settings for an HVAC system that can be individually manipulated. Unfortunately, however, users are often intimidated by a dizzying array of switches and controls laid out in various configurations on the face of the thermostat or behind a panel door on the thermostat, and seldom adjust the manufacturer defaults to optimize their own energy usage. Thus, even though the installed programmable thermostats in a large number of homes are technologically capable of operating the HVAC equipment with energy-saving profiles, it is often the case that only the one-size-fits-all manufacturer default profiles are ever implemented in a large number of homes. Indeed, in an unfortunately large number of cases, a home user may permanently operate the unit in a “temporary” or “hold” mode, manually manipulating the displayed set temperature as if the unit were a simple, non-programmable thermostat.
At a more general level, because of the fact that human beings must inevitably be involved, there is a tension that arises between (i) the amount of energy-saving sophistication that can be offered by an HVAC control system, and (ii) the extent to which that energy-saving sophistication can be put to practical, everyday use in a large number of homes. Similar issues arise in the context of multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space having one or more HVAC systems. Other issues arise as would be apparent to one skilled in the art upon reading the present disclosure.
It is to be appreciated that although exemplary embodiments are presented herein for the particular context of HVAC system control, there are a wide variety of other resource usage contexts for which the embodiments are readily applicable including, but not limited to, water usage, air usage, the usage of other natural resources, and the usage of other (i.e., non-HVAC-related) forms of energy, as would be apparent to the skilled artisan in view of the present disclosure. Therefore, such application of the embodiments in such other resource usage contexts is not outside the scope of the present teachings.
Provided according to some embodiments is a thermostat user interface for a thermostat. The thermostat includes a frustum-shaped shell body having a circular cross-section and a sidewall extending between first and second ends, the second end being user-facing when the thermostat is wall-mounted; a circular rotatable ring being user rotatable for adjusting a setting of the thermostat; and a circular cover including a clear circular center portion surrounded by a painted outer portion. The clear circular center portion permits a corresponding circular portion of a non-circular dot-matrix color display element to be visible through the circular cover and the painted outer portion masks a remaining portion of the non-circular dot-matrix color display element so as to create a circular graphical user interface.
Provided according to some embodiments is a thermostat for controlling an HVAC system. The thermostat includes a frustum-shaped shell body, a circular rotatable ring, a circular cover, and a non-circular dot-matrix color display element. According to some embodiments, the frustum-shaped shell body includes a circular cross-section and a central axis generally perpendicular to a wall when the thermostat is wall-mounted and a sidewall that extends along a length of the central axis between first and second ends of the frustum-shaped shell body. The first end of the frustum-shaped shell body is wall-facing when the thermostat is wall-mounted, and the second end of the frustum-shaped shell body is user-facing when the thermostat is wall-mounted. The first end of the frustum-shaped shell body has a first diameter and the second end of the frustum-shaped shell body has a second, larger diameter. The sidewall includes inside and outside surfaces, where the inside surface defines an interior for housing components of the thermostat.
According to some embodiments, the circular rotatable ring is mounted proximate the second end of the frustum-shaped shell body, and the circular rotatable ring includes an axis of rotation generally perpendicular to the wall when the thermostat is wall-mounted. The circular rotatable ring is user rotatable about the axis of rotation, and such user rotation of the circular rotatable ring results in user input for adjusting a setting of the thermostat. According to some embodiments, the circular cover is mounted proximate the second end of the frustum-shaped shell body, and the circular cover includes a central axis generally perpendicular to the wall when the thermostat is wall-mounted. The circular cover also includes a clear circular center portion surrounded by a painted outer portion.
According to some embodiments, the non-circular dot-matrix color display element is mounted at a location between the second end of the frustum-shaped shell body and the circular cover. The clear circular center portion of the circular cover permits a corresponding circular portion of the non-circular dot-matrix color display element to be visible through the circular cover and the painted outer portion of the circular cover masks a remaining portion of the non-circular dot-matrix color display element so as to create a circular graphical user interface, the non-circular dot-matrix color display element and the circular cover do not rotate with the circular rotatable ring.
According to some embodiments the thermostat also includes a temperature sensor for use in determining an ambient air temperature, a plurality of HVAC wire connectors configured for receiving a corresponding plurality of HVAC control wires associated with the HVAC system, an audio-output device to output sound, and a processing system provided in operative communication with the plurality of HVAC wire connectors, the circular rotatable ring, the non-circular dot-matrix color display element, and the temperature sensor. According to some embodiments, the processing system configured to cause the non-circular dot-matrix color display element to display a visually prominent digital numerical value representative of a temperature value, wherein the digital numerical value representative of the temperature value is viewable through the clear circular center portion of the circular cover; cause the audio-output device to output synthesized audible ticks in correspondence with user rotation of the circular rotatable ring; determine a user-selected setpoint temperature value based on user rotation of the circular rotatable ring; send a control signal to the HVAC system via one or more of the plurality of HVAC wire connectors based at least in part on a comparison of a user-selected temperature value and the determined ambient air temperature; indicate a status of the thermostat by causing the non-circular dot-matrix color display element to display an animated sweep of radial marks arcuately arranged on the non-circular dot-matrix color display element to correspond with a perimeter of the clear circular center portion of the circular cover; and indicate an operation mode of the thermostat by causing the non-circular dot-matrix color display element to display orange-red colored elements when the thermostat is operating in a heating mode and bluish colored elements when the thermostat is operating in a cooling mode.
According to some embodiments a method is provided for a thermostat interacting with a user. The method is implemented in a thermostat that includes a frustum-shaped shell body having a circular cross-section and a central axis generally perpendicular to a wall when the thermostat is wall-mounted. The frustum-shaped shell body includes a sidewall that extends along a length of the central axis between first and second ends of the frustum-shaped shell body. The first end of the frustum-shaped shell body is wall-facing when the thermostat is wall-mounted, and the second end of the frustum-shaped shell body is user-facing when the thermostat is wall-mounted. The first end of the frustum-shaped shell body has a first diameter and the second end of the frustum-shaped shell body has a second, larger diameter. The sidewall includes inside and outside surfaces, where the inside surface defines an interior for housing components.
According to some embodiments, the method includes detecting user presence at the thermostat. Responsive to detecting user presence, the method includes activating a non-circular dot-matrix color display element mounted proximate the second end of the frustum-shaped shell body of the thermostat; informing the user of an operational mode of the thermostat by displaying on the non-circular dot-matrix color display orange-red elements when the thermostat is in a heating mode and bluish elements when the thermostat is in a cooling mode; indicating, via a circular graphical user interface, a temperature value by displaying a digital numerical value representative of the temperature value on a circular portion of the non-circular dot-matrix color display element that aligns with a clear circular center region of a circular cover. The circular cover includes a painted region that surrounds the clear circular center region and that masks a remaining portion of the non-circular dot-matrix color display element so as to create the circular graphical user interface.
According to some embodiments, the method includes enabling the user to select a setpoint temperature value by providing a circular rotatable ring mounted proximate the second end of a frustum-shaped shell body of the thermostat. The circular rotatable ring includes an axis of rotation generally perpendicular to the wall when the thermostat is wall-mounted, and the circular rotatable ring is configured to be user rotatable about the axis of rotation. User rotation of the circular rotatable ring results in user input for selecting the setpoint temperature value. The method further includes outputting synthesized audible ticks in correspondence with user rotation of the circular rotatable ring, and determining a user-selected setpoint temperature value by tracking user rotation of the circular rotatable ring.
According to some embodiments a method is provided for a thermostat interacting with a user. The method is includes displaying, on a non-circular electronic display, a plurality of radial marks arcuately arranged in alignment with a perimeter of a clear circular center region of a cover mounted near a user-facing end of a frustum-shaped shell body of the thermostat. The clear circular center region being surrounded by a painted outer region to mask portions of the non-circular electronic display. The method further includes displaying, on the non-circular electronic display, a numerical representation of a temperature value, where the numerical representation is displayed at a location that aligns with the clear circular center region of the circular cover mounted near the user-facing end of the frustum-shaped shell body of the thermostat. The method further includes displaying, on the non-circular electronic display, a color having a red and/or orange shade when the thermostat is calling for heating from the HVAC system, and, displaying on the non-circular electronic display, a color having a bluish shade when the thermostat is calling for cooling from the HVAC system.
Provided according to some embodiments is programmable device, such a thermostat, for controlling an HVAC system. The programmable device includes high-power consuming circuitry adapted and programmed to perform while in an active state a plurality of high power activities including interfacing with a user, the high-power consuming circuitry using substantially less power while in an inactive state or sleep state. The device also includes low-power consuming circuitry adapted and programmed to perform a plurality of low power activities, including for example causing the high-power circuitry to transition from the inactive to active states; polling sensors such as temperature and occupancy sensors; and switching on or off an HVAC functions. The device also includes power stealing circuitry adapted to harvest power from an HVAC triggering circuit for turning on and off an HVAC system function; and a power storage medium, such as a rechargeable battery, adapted to store power harvested by the power stealing circuitry for use by at least the high-power consuming circuitry such that the high-power consuming circuitry can temporarily operate in an active state while using energy at a greater rate than can be safely harvested by the power stealing circuitry without inadvertently switching the HVAC function. Examples of the high power activities includes wireless communication; driving display circuitry; displaying a graphical information to a user; and performing calculations relating to learning.
According to some embodiments, the high-power consuming circuitry includes a microprocessor and is located on a head unit, and the low-power consuming circuitry includes a microcontroller and is located on a backplate.
The subject matter of this patent specification relates to the subject matter of the following commonly assigned applications, each of which is incorporated by reference herein: U.S. Ser. No. 12/984,602 filed Jan. 4, 2011; U.S. Ser. No. 12/987,257 filed Jan. 10, 2011; U.S. Ser. No. 13/033,573 filed Feb. 23, 2011; U.S. Ser. No. 13/034,666 filed Feb. 24, 2011; U.S. Ser. No. 13/034,674 filed Feb. 24, 2011; U.S. Ser. No. 13/034,678 filed Feb. 24, 2011; U.S. Ser. No. 13/038,191 filed Mar. 1, 2011; U.S. Ser. No. 13/038,206 filed Mar. 1, 2011; U.S. Ser. No. 13/199,108, filed Aug. 17, 2011; U.S. Ser. No. 13/267,871 filed Oct. 6, 2011; U.S. Ser. No. 13/267,877 filed Oct. 6, 2011; U.S. Ser. No. 13/269,501, filed Oct. 7, 2011; U.S. Ser. No. 13/275,307 filed Oct. 17, 2011; U.S. Ser. No. 13/275,311 filed Oct. 17, 2011; U.S. Ser. No. 13/317,423 filed Oct. 17, 2011; U.S. Ser. No. 13/279,151 filed Oct. 21, 2011; U.S. Ser. No. 13/317,557 filed Oct. 21, 2011; and International Application No. PCT/US12/30084 filed 22 Mar. 2012. One or more of the above-referenced commonly assigned applications claims the benefit of U.S. Prov. Ser. No. 61/415,771 filed Nov. 19, 2010 and U.S. Prov. Ser. No. 61/429,093 filed Dec. 31, 2010, each of which is incorporated by reference herein. The above-referenced patent applications are collectively referenced herein as “the commonly assigned incorporated applications.”
Provided according to one or more embodiments are systems, methods, computer program products, and related business methods for controlling one or more HVAC systems based on one or more versatile sensing and control units (VSCU units), each VSCU unit being configured and adapted to provide sophisticated, customized, energy-saving HVAC control functionality while at the same time being visually appealing, non-intimidating, elegant to behold, and delightfully easy to use. Each VSCU unit is advantageously provided with a selectively layered functionality, such that unsophisticated users are only exposed to a simple user interface, but such that advanced users can access and manipulate many different energy-saving and energy tracking capabilities. Importantly, even for the case of unsophisticated users who are only exposed to the simple user interface, the VSCU unit provides advanced energy-saving functionality that runs in the background, the VSCU unit quietly using multi-sensor technology to “learn” about the home's heating and cooling environment and optimizing the energy-saving settings accordingly.
The VSCU unit also “learns” about the users themselves, beginning with a congenial “setup interview” in which the user answers a few simple questions, and then continuing over time using multi-sensor technology to detect user occupancy patterns (e.g., what times of day they are home and away) and by tracking the way the user controls the set temperature on the dial over time. The multi-sensor technology is advantageously hidden away inside the VSCU unit itself, thus avoiding the hassle, complexity, and intimidation factors associated with multiple external sensor-node units. On an ongoing basis, the VSCU unit processes the learned and sensed information according to one or more advanced control algorithms, and then automatically adjusts its environmental control settings to optimize energy usage while at the same time maintaining the living space at optimal levels according to the learned occupancy patterns and comfort preferences of the user. Even further, the VSCU unit is programmed to promote energy-saving behavior in the users themselves by virtue of displaying, at judiciously selected times on its visually appealing user interface, information that encourages reduced energy usage, such as historical energy cost performance, forecasted energy costs, and even fun game-style displays of congratulations and encouragement.
Advantageously, the selectively layered functionality of the VSCU unit allows it to be effective for a variety of different technological circumstances in home and business environments, thereby making the same VSCU unit readily saleable to a wide variety of customers. For simple environments having no wireless home network or internet connectivity, the VSCU unit operates effectively in a standalone mode, being capable of learning and adapting to its environment based on multi-sensor technology and user input, and optimizing HVAC settings accordingly. However, for environments that do indeed have home network or internet connectivity, the VSCU unit operates effectively in a network-connected mode to offer a rich variety of additional capabilities.
When the VSCU unit is connected to the internet via a home network, such as through IEEE 802.11 (Wi-Fi) connectivity, additional capabilities provided according to one or more embodiments include, but are not limited to: providing real time or aggregated home energy performance data to a utility company, VSCU data service provider, VSCU units in other homes, or other data destinations; receiving real time or aggregated home energy performance data from a utility company, VSCU data service provider, VSCU units in other homes, or other data sources; receiving new energy control algorithms or other software/firmware upgrades from one or more VSCU data service providers or other sources; receiving current and forecasted weather information for inclusion in energy-saving control algorithm processing; receiving user control commands from the user's computer, network-connected television, smart phone, or other stationary or portable data communication appliance (hereinafter collectively referenced as the user's “digital appliance”); providing an interactive user interface to the user through their digital appliance; receiving control commands and information from an external energy management advisor, such as a subscription-based service aimed at leveraging collected information from multiple sources to generate the best possible energy-saving control commands or profiles for their subscribers; receiving control commands and information from an external energy management authority, such as a utility company to whom limited authority has been voluntarily given to control the VSCU in exchange for rebates or other cost incentives (e.g., for energy emergencies, “spare the air” days, etc.); providing alarms, alerts, or other information to the user on their digital appliance (and/or a user designee such as a home repair service) based on VSCU-sensed HVAC-related events (e.g., the house is not heating up or cooling down as expected); providing alarms, alerts, or other information to the user on their digital appliance (and/or a user designee such as a home security service or the local police department) based on VSCU-sensed non-HVAC related events (e.g., an intruder alert as sensed by the VSCU's multi-sensor technology); and a variety of other useful functions enabled by network connectivity as disclosed in one or more of the examples provided further hereinbelow.
It is to be appreciated that while one or more embodiments is detailed herein for the context of a residential home, such as a single-family house, the scope of the present teachings is not so limited, the present teachings being likewise applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space having one or more HVAC systems. It is to be further appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons who are interacting with the VSCU unit or other device or user interface in the context of some particularly advantageous situations described herein, these references are by no means to be considered as limiting the scope of the present teachings with respect to the person or persons who are performing such actions. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, and is also one of the users of the unit and is a customer of the utility company and/or VSCU data service provider. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. Importantly, while the identity of the person performing the action may be germane to a particular advantage provided by one or more of the embodiments—for example, the password-protected temperature governance functionality described further herein may be particularly advantageous where the landlord holds the sole password and can prevent energy waste by the tenant—such identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those particular individuals having those particular identities.
As used herein, “set point” or “temperature set point” refers to a target temperature setting of a temperature control system, such as one or more of the VSCU units described herein, as set by a user or automatically according to a schedule. As would be readily appreciated by a person skilled in the art, many of the disclosed thermostatic functionalities described hereinbelow apply, in counterpart application, to both the heating and cooling contexts, with the only different being in the particular set points and directions of temperature movement. To avoid unnecessary repetition, some examples of the embodiments may be presented herein in only one of these contexts, without mentioning the other. Therefore, where a particular embodiment or example is set forth hereinbelow in the context of home heating, the scope of the present teachings is likewise applicable to the counterpart context of home cooling, and vice versa, to the extent such counterpart application would be logically consistent with the disclosed principles as adjudged by the skilled artisan.
By virtue of user rotation of the outer ring 106 (referenced hereafter as a “ring rotation”) and the inward pushing of the outer ring 106 (referenced hereinafter as an “inward click”) responsive to intuitive and easy-to-read prompts on the circular display monitor 102, the VSCU unit 100 is advantageously capable of receiving all necessary information from the user for basic setup and operation. Preferably, the outer ring 106 is mechanically mounted in a manner that provides a smooth yet viscous feel to the user, for further promoting an overall feeling of elegance while also reducing spurious or unwanted rotational inputs. For one embodiment, the VSCU unit 100 recognizes three fundamental user inputs by virtue of the ring rotation and inward click: (1) ring rotate left, (2) ring rotate right, and (3) inward click. For other embodiments, more complex fundamental user inputs can be recognized, such as “double-click” or “triple-click” inward presses, and such as speed-sensitive or acceleration-sensitive rotational inputs (e.g., a very large and fast leftward rotation specifies an “Away” occupancy state, while a very large and fast rightward rotation specifies an “Occupied” occupancy state).
Although the scope of the present teachings is not so limited, it is preferred that there not be provided a discrete mechanical HEAT-COOL toggle switch, or HEAT-OFF-COOL selection switch, or HEAT-FAN-OFF-COOL switch anywhere on the VSCU unit 100, this omission contributing to the overall visual simplicity and elegance of the VSCU unit 100 while also facilitating the provision of advanced control abilities that would otherwise not be permitted by the existence of such a switch. It is further highly preferred that there be no electrical proxy for such a discrete mechanical switch (e.g., an electrical push button or electrical limit switch directly driving a mechanical relay). Instead, it is preferred that the switching between these settings be performed under computerized control of the VSCU unit 100 responsive to its multi-sensor readings, its programming (optionally in conjunction with externally provided commands/data provided over a data network), and/or the above-described “ring rotation” and “inward click” user inputs.
The VSCU unit 100 comprises physical hardware and firmware configurations, along with hardware, firmware, and software programming that is capable of carrying out the functionalities described in the instant disclosure. In view of the instant disclosure, a person skilled in the art would be able to realize the physical hardware and firmware configurations and the hardware, firmware, and software programming that embody the physical and functional features described herein without undue experimentation using publicly available hardware and firmware components and known programming tools and development platforms. Similar comments apply to described devices and functionalities extrinsic to the VSCU unit 100, such as devices and programs used in remote data storage and data processing centers that receive data communications from and/or that provide data communications to the VSCU unit 100. By way of example, references hereinbelow to one or more preinstalled databases inside the VSCU unit 100 that are keyed to different ZIP codes can be carried out using flash memory technology similar to that used in global positioning based navigation devices. By way of further example, references hereinbelow to machine learning and mathematical optimization algorithms, as carried out respectively by the VSCU unit 100 in relation to home occupancy prediction and set point optimization, for example, can be carried out using one or more known technologies, models, and/or mathematical strategies including, but not limited to, artificial neural networks, Bayesian networks, genetic programming, inductive logic programming, support vector machines, decision tree learning, clustering analysis, dynamic programming, stochastic optimization, linear regression, quadratic regression, binomial regression, logistic regression, simulated annealing, and other learning, forecasting, and optimization techniques.
In either case, the VSCU unit 100 can advantageously serve as an “inertial wedge” for inserting an entire energy-saving technology platform into the home. Simply stated, because most homeowners understand and accept the need for home to have a thermostat, even the most curmudgeonly and techno-phobic homeowners will readily accept the simple, non-intimidating, and easy-to-use VSCU unit 100 into their homes. Once in the home, of course, the VSCU unit 100 will advantageously begin saving energy for a sustainable planet and saving money for the homeowner, including the curmudgeons. Additionally, however, as homeowners “warm up” to the VSCU unit 100 platform and begin to further appreciate its delightful elegance and seamless operation, they will be more inclined to take advantage of its advanced features, and they will furthermore be more open and willing to embrace a variety of compatible follow-on products and services as are described further hereinbelow. This is an advantageous win-win situation on many fronts, because the planet is benefitting from the propagation of energy-efficient technology, while at the same time the manufacturer of the VSCU unit and/or their authorized business partners can further expand their business revenues and prospects. For clarity of disclosure, the term “VSCU Efficiency Platform” refers herein to products and services that are technologically compatible with the VSCU unit 100 and/or with devices and programs that support the operation of the VSCU unit 100.
Notably, the example of
Referring now to
For one embodiment, the VSCU unit 100 is designed to be entirely silent unless a user has walked up and begun controlling the unit. Advantageously, there are no clicking-type annoyances when the heating or cooling units are activated as with conventional prior art thermostats. Optionally, the VSCU unit 100 can be configured to synthesize artificial audible clicks, such as can be output through a piezoelectric speaker, to provide “tick” feedback as the user dials through different temperature settings.
For one embodiment, the VSCU unit 100 is programmed to provide a software lockout functionality, wherein a person is required to enter a password or combination before the VSCU unit 100 will accept their control inputs. The user interface for password request and entry can be similar to that shown in
For another example shown in
For some embodiments, the VSCU unit 100 is manufactured and sold as a single, monolithic structure containing all of the required electrical and mechanical connections on the back of the unit. For some embodiments, the VSCU 100 is manufactured and/or sold in different versions or packaging groups depending on the particular capabilities of the manufacturer(s) and the particular needs of the customer. For example, the VSCU unit 100 is provided in some embodiments as the principal component of a two-part combination consisting of the VSCU 100 and one of a variety of dedicated docking devices, as described further hereinbelow.
For the initial installation process, the customer (or their handyman, or an HVAC professional, etc.) first installs the HVAC-coupling wall dock 702, including all of the necessary mechanical connections to the wall and HVAC wiring connections to the HVAC wiring 298. Once the HVAC-coupling wall dock 702 is installed, which represents the “hard work” of the installation process, the next task is relatively easy, which is simply to slide the VSCU unit 100 thereover to mate the electrical connectors 704/705. Preferably, the components are configured such that the HVAC-connecting wall dock 702 is entirely hidden underneath and inside the VSCU unit 100, such that only the visually appealing VSCU unit 100 is visible.
For one embodiment, the HVAC-connecting wall dock 702 is a relatively “bare bones” device having the sole essential function of facilitating electrical connectivity between the HVAC wiring 298 and the VSCU unit 100. For another embodiment, the HVAC-coupling wall dock 702 is equipped to perform and/or facilitate, in either a duplicative sense and/or a primary sense without limitation, one or more of the functionalities attributed to the VSCU unit 100 in the instant disclosure, using a set of electrical, mechanical, and/or electromechanical components 706. One particularly useful functionality is for the components 706 to include power-extraction circuitry for judiciously extracting usable power from the HVAC wiring 298, at least one of which will be carrying a 24-volt AC signals in accordance with common HVAC wiring practice. The power-extraction circuitry converts the 24-volt AC signal into DC power (such as at 5 VDC, 3.3 VDC, etc.) that is usable by the processing circuitry and display components of the main unit 701.
The division and/or duplication of functionality between the VSCU unit 100 and the HVAC-coupling wall dock 702 can be provided in many different ways without departing from the scope of the present teachings. For another embodiment, the components 706 of the HVAC-coupling wall dock 702 can include one or more sensing devices, such as an acoustic sensor, for complementing the sensors provided on the sensor ring 104 of the VSCU unit 100. For another embodiment, the components 706 can include wireless communication circuitry compatible with one or more wireless communication protocols, such as the Wi-Fi and/or ZigBee protocols. For another embodiment, the components 706 can include external AC or DC power connectors. For another embodiment, the components 706 can include wired data communications jacks, such as an RJ45 Ethernet jack, an RJ11 telephone jack, or a USB connector.
The docking capability of the VSCU unit 100 according to the embodiment of
Provided in accordance with one or more embodiments related to the docking capability shown in
As used herein, the term “primary VSCU unit” refers to one that is electrically connected to actuate an HVAC system in whole or in part, which would necessarily include the first VSCU unit purchased for any home, while the term “auxiliary VSCU unit” refers to one or more additional VSCU units not electrically connected to actuate an HVAC system in whole or in part. An auxiliary VSCU unit, when docked, will automatically detect the primary VSCU unit and will automatically be detected by the primary VSCU unit, such as by Wi-Fi or ZigBee wireless communication. Although the primary VSCU unit will remain the sole provider of electrical actuation signals to the HVAC system, the two VSCU units will otherwise cooperate in unison for improved control heating and cooling control functionality, such improvement being enabled by virtue of the added multi-sensing functionality provided by the auxiliary VSCU unit, as well as by virtue of the additional processing power provided to accommodate more powerful and precise control algorithms. Because the auxiliary VSCU unit can accept user control inputs just like the primary VSCU unit, user convenience is also enhanced. Thus, for example, where the tabletop docking station and the auxiliary VSCU unit are placed on a nightstand next to the user's bed, the user is not required to get up and walk to the location of the primary VSCU unit if they wish to manipulate the temperature set point, view their energy usage, or otherwise interact with the system.
A variety of different VSCU-compatible docking stations are within the scope of the present teachings. For example, in another embodiment there is provided an auxiliary wall dock (not shown) that allows an auxiliary VSCU unit to be mounted on a wall. The auxiliary wall dock is similar in functionality to the tabletop docking station in that it does not provide HVAC wiring connections, but does serve as a physical mounting point and provides electrical power derived from a standard wall outlet.
For one embodiment, all VSCU units sold by the manufacturer are identical in their core functionality, each being able to serve as either a primary VSCU unit or auxiliary VSCU unit as the case requires, although the different VSCU units may have different colors, ornamental designs, memory capacities, and so forth. For this embodiment, the user is advantageously able, if they desire, to interchange the positions of their VSCU units by simple removal of each one from its existing docking station and placement into a different docking station. Among other advantages, there is an environmentally, technically, and commercially appealing ability for the customer to upgrade to the newest, latest VSCU designs and technologies without the need to throw away the existing VSCU unit. For example, a customer with a single VSCU unit (which is necessarily serving as a primary VSCU unit) may be getting tired of its color or its TFT display, and may be attracted to a newly released VSCU unit with a different color and a sleek new OLED display. For this case, in addition to buying the newly released VSCU, the customer can buy a tabletop docking station to put on their nightstand. The customer can then insert their new VSCU unit into the existing HVAC-coupling wall dock, and then take their old VSCU unit and insert it into the tabletop docking station. Advantageously, in addition to avoiding the wastefulness of discarding the old VSCU unit, there is now a new auxiliary VSCU unit at the bedside that not only provides increased comfort and convenience, but that also promotes increased energy efficiency by virtue of the additional multi-sensor information and processing power provided.
For other embodiments, different VSCU units sold by the manufacturer can have different functionalities in terms of their ability to serve as primary versus auxiliary VSCU units. This may be advantageous from a pricing perspective, since the hardware cost of an auxiliary-only VSCU unit may be substantially less than that of a dual-capability primary/auxiliary VSCU unit. In other embodiments there is provided distinct docking station capability for primary versus auxiliary VSCU units, with primary VSCU units using one kind of docking connection system and auxiliary VSCU units using a different kind of docking connection system. In still other embodiments there is provided the docking station capability of
In still other embodiments, all VSCU units are provided as non-docking types, but are interchangeable in their abilities as primary and auxiliary VSCU units. In still other embodiments, all VSCU units are provided as non-docking types and are non-interchangeable in their primary versus auxiliary abilities, that is, there is a first set of VSCU units that can only serve as primary VSCU units and a second set of VSCU units that can only serve as auxiliary VSCU units. For embodiments in which primary VSCU units are provided as non-docking types, their physical architecture may still be separable into two components for the purpose of streamlining the installation process, with one component being similar to the HVAC-coupling wall dock 702 of
The HVAC-coupling wall dock 702′ is configured and designed in conjunction with the VSCU unit 100, including both hardware aspects and programming aspects, to provide a DIY installation process that is simple, non-intimidating, and perhaps even fun for many DIY installers, and that further provides an appreciable degree of foolproofing capability for protecting the HVAC system from damage and for ensuring that the correct signals are going to the correct equipment. For one embodiment, the HVAC-coupling wall dock 702′ is equipped with a small mechanical detection switch (not shown) for each distinct input port, such that the insertion of a wire (and, of course, the non-insertion of a wire) is automatically detected and a corresponding indication signal is provided to the VSCU 100 upon initial docking. In this way, the VSCU 100 has knowledge for each individual input port whether a wire has, or has not been, inserted into that port. Preferably, the VSCU unit 100 is also provided with electrical sensors (e.g., voltmeter, ammeter, and ohmmeter) corresponding to each of the input wiring ports 851. The VSCU 100 is thereby enabled, by suitable programming, to perform some fundamental “sanity checks” at initial installation. By way of example, if there is no input wire at either the Rc or Rh terminal, or if there is no AC voltage sensed at either of these terminals, further initialization activity can be immediately halted, and the user notified on the circular display monitor 102, because there is either no power at all or the user has inserted the Rc and/or Rh wires into the wrong terminal. By way of further example, if there is a live voltage on the order of 24 VAC detected at any of the W, Y, and G terminals, then it can be concluded that the user has placed the Rc and/or Rh wire in the wrong place, and appropriate installation halting and user notification can be made.
One particularly advantageous feature from a safety and equipment preservation perspective provided according to one embodiment relates to automated opening versus automated shunting of the Rc and Rh terminals by the VSCU unit 100. In many common home installations, instead of there being separate wires provided for Rc (24 VAC heating call switch power) and Rh (24 VAC cooling call switch power), there is only a single 24 VAC call switch power lead provided. This single 24 VAC lead, which might be labeled R, V, Rh, or Rc depending on the unique history and geographical location of the home, provides the call switch power for both heating and cooling. For such cases, it is electrically necessary for any thermostat to have its Rc and Rh input ports shunted together so that the power from that single lead can be respectively accessed by the heating and cooling call switches. However, in many other common home installations, there are separate 24 VAC wires provided for Rc and Rh running from separate transformers and, when so provided, it is important not to shunt them together to avoid equipment damage. These situations are resolved historically by (i) the professional installer examining the HVAC system and ensuring that a shunting lead (or equivalent DIP switch setting) is properly installed or not installed as appropriate, and/or (ii) the historical presence on most thermostats of a discrete user-toggled mechanical or electromechanical switch (e.g., HEAT-OFF-COOL) to ensure that heating and cooling are never simultaneously activated. Notably, it is desired to omit any discrete mechanical HEAT-OFF-COOL in most embodiments and to eliminate the need for a professional installer for the instant DIY product version environment. Advantageously, according to an embodiment, the VSCU 100 is advantageously equipped and programmed to (i) automatically test the inserted wiring to classify the user's HVAC system into one of the above two types (i.e., single call power lead versus dual call power leads), (ii) to automatically ensure that the Rc and Rh input ports remain electrically segregated if the if the user's HVAC system is determined to be of the dual call power lead type, and (iii) to automatically shunt the Rc and Rh input ports together if the user's HVAC system is determined to be of the single call power lead type. The automatic testing can comprise, without limitation, electrical sensing such as that provided by voltmeter, ammeters, ohmmeters, and reactance-sensing circuitry, as well as functional detection as described further below.
Also provided at installation time according to an embodiment, which is particularly useful and advantageous in the DIY scenario, is automated functional testing of the HVAC system by the VSCU unit 100 based on the wiring insertions made by the installer as detected by the small mechanical detection switches at each distinct input port. Thus, for example, where an insertion into the W (heating call) input port is mechanically sensed at initial startup, the VSCU unit 100 actuates the furnace (by coupling W to Rh) and then automatically monitors the temperature over a predetermined period, such as ten minutes. If the temperature is found to be rising over that predetermined period, then it is determined that the W (heating call) lead has been properly connected to the W (heating call) input port. However, if the temperature is found to be falling over that predetermined period, then it is determined that Y (cooling call) lead has likely been erroneously connected to the W (heating call) input port. For one embodiment, when such error is detected, the system is shut down and the user is notified and advised of the error on the circular display monitor 102. For another embodiment, when such error is detected, the VSCU unit 100 automatically reassigns the W (heating call) input port as a Y (cooling call) input port to automatically correct the error. Similarly, according to an embodiment, where the Y (cooling call) lead is mechanically sensed at initial startup, the VSCU unit 100 actuates the air conditioner (by coupling Y to Rc) and then automatically monitors the temperature, validating the Y connection if the temperature is sensed to be falling and invalidating the Y connection (and, optionally, automatically correcting the error by reassigning the Y input port as a W input port) if the temperature is sensed to be rising. In view of the present disclosure, the determination and incorporation of other automated functional tests into the above-described method for other HVAC functionality would be achievable by the skilled artisan and are within the scope of the present teachings. By way of example, for one embodiment there can be a statistical study done on the electrical noise patterns associated with the different control wires and a unique or partially unique “noise fingerprint” associated with the different wires, and then the VSCU unit 100 can automatically sense the noise on each of the existing control wires to assist in the automated testing and verification process.
Also provided at installation time according to an embodiment, which is likewise particularly advantageous in the DIY scenario, is automated determination of the homeowner's pre-existing heat pump wiring convention when an insertion onto the O/B (heat pump) input port is mechanically sensed at initial startup. Depending on a combination of several factors such as the history of the home, the geographical region of the home, and the particular manufacturer and installation year of the home's heat pump, there may be a different heat pump signal convention used with respect to the direction of operation (heating or cooling) of the heat pump. According to an embodiment, the VSCU unit 100 automatically and systematically applies, for each of a plurality of preselected candidate heat pump actuation signal conventions, a cooling actuation command and a heating actuation command, each actuation command being followed by a predetermined time period over which the temperature change is sensed. If the cooling command according to the presently selected candidate convention is followed by a sensed period of falling temperature, and the heating command according to the presently selected candidate convention is followed by a sensed period of rising temperature, then the presently selected candidate convention is determined to be the actual heat pump signal convention for that home. If, on the other hand, the cooling command was not followed by a sensed period of cooling and/or the heating command was not followed by a sensed period of heating, then the presently selected candidate convention is discarded and the VSCU unit 100 repeats the process for the next candidate heat pump actuation signal convention. For one example, a first candidate heat pump actuation signal convention is (a) for cooling, leave O/B open and connect Y to Rc, and (b) for heating, connect O/B to Rh, while a second candidate heat pump actuation signal convention is (a) for cooling, connect O/B to Rc, and (b) for heating, leave O/B open and connect W to Rh. In view of the present disclosure, the determination and incorporation of other candidate heat pump actuation signal conventions into the above-described method would be achievable by the skilled artisan and are within the scope of the present teachings.
Many advantageous capabilities are programmed into the VSCU units 100 and 100′ to leverage their communication and multi-sensing capabilities such that they jointly, in a cooperative manner, perform the many VSCU unit functionalities described herein (e.g., “learning” about the home HVAC environment, performing occupancy sensing and prediction, “learning” user comfort preferences, etc.) that do not require Internet access. By way of simple example, in one embodiment the primary VSCU unit 100 receives temperature data from the auxiliary VSCU unit 100′ and computes an average of the two temperatures, controlling the HVAC system 299 such that the average temperature of the home 201 is maintained at the current temperature set point level. One or more additional auxiliary VSCU units (not shown) may also be positioned at one or more additional locations throughout the home and can become part the ad hoc “home VSCU network.” The scope of the present teachings not being limited to any particular maximum number of auxiliary VSCU units. Among other advantages, adding more auxiliary VSCU units is advantageous in that more accurate occupancy detection is promoted, better determination of spatial temperature gradients and thermal characteristics is facilitated, and additional data processing power is provided.
Preferably, the primary/auxiliary VSCU units 100/100′ are programmed to establish a master/slave relationship, wherein any conflicts in their automated control determinations are resolved in favor of the master VSCU unit, and/or such that any user inputs at the master unit take precedence over any conflicting user inputs made at the slave VSCU unit. Although the primary VSCU unit 100 will likely be the “master” VSCU unit in a beginning or default scenario, the status of any particular VSCU unit as a “master” or “slave” is not dictated solely by its status as a primary or auxiliary VSCU unit. Moreover, the status of any particular VSCU unit as “master” or “slave” is not permanent, but rather is dynamically established to best meet current HVAC control needs as can be best sensed and/or predicted by the VSCU units. For one preferred embodiment, the establishment of “master” versus “slave” status is optimized to best meet the comfort desires of the human occupants as can be best sensed and/or predicted by the VSCU units. By way of example, if each VSCU unit is sensing the presence of multiple occupants in their respective areas, then the primary VSCU unit is established as the master unit and controls the HVAC system 299 such that the average temperature reading of the two VSCU units is maintained at the current set point temperature according to a currently active template schedule (i.e., a schedule of time intervals and set point temperatures for each time interval). However, if no occupants in the home are sensed except for a person in the bedroom (as sensed by the auxiliary VSCU unit 100′ which is positioned on a nightstand in this example), then the auxiliary VSCU unit 100′ becomes the “master” VSCU unit, which commands the “slave” VSCU unit 100 to control the HVAC system 299 such that the temperature in the bedroom, as sensed by the “master” unit, stays at a current set point temperature.
Many other automated master/slave establishment scenarios and control determinations based on human behavioral studies, statistical compilations, and the like are within the scope of the present teachings. In one example, the master-slave determination can be made and/or influenced or supported based on an automated determination of which thermostat is in a better place to more reliably govern the temperature, based on historical and/or testing-observed cycling behavior or other criteria. For example, sensors that are immediately over a heat register will not be reliable and will keep cycling the furnace too often. Nodes that are in bathrooms and in direct sunlight are also less reliable. When there are multiple sensors/nodes, there is an algorithm that determines which one is more reliable, and there is master-slave determination based on those determinations. For some related embodiments, VSCU units automatically determined to be near bathrooms and dishwashers can be assigned custom templates designed to at least partially ameliorate the adverse effects of such placement.
The establishment of master-slave status for the primary/auxiliary VSCU units 100/100′ can also be based upon human control inputs. By way of example, if each VSCU unit is sensing the presence of multiple occupants in their respective areas, and then a user manually changes the current set point temperature on one of the two units, that VSCU unit can output the question, “Master Override?” on its circular display monitor 102 (analogous to the query capability shown at
Also provided according to an embodiment is an ability for the multiple VSCU units to judiciously share computing tasks among them in an optimal manner based on power availability and/or circuitry heating criteria. Many of the advanced sensing, prediction, and control algorithms provided with the VSCU unit are relatively complex and computationally intensive, and can result in high power usage and/or device heating if carried out unthrottled. For one embodiment, the intensive computations are automatically distributed such that a majority (or plurality) of them are carried out on a subset of the VSCU units known to have the best power source(s) available at that time, and/or to have known to have the highest amount of stored battery power available. Thus, for example, because it is generally preferable for each primary VSCU unit not to require household AC power for simplicity of installation as well as for equipment safety concerns, the primary VSCU unit 100 of
Referring now to
It is to be appreciated that there are other multiple-thermostat scenarios that exist in some homes other than ones for which each thermostat controls a distinct HVAC system, and that multiple VSCU unit installations capable of controlling such systems are within the scope of the present teachings. In some existing home installations there may only be a single furnace or a single air conditioning unit, but the home may still be separated into plural “zones” by virtue of actuated flaps in the ductwork, each “zone” being controlled by its own thermostat. In such settings, two primary VSCU units can be installed and configured to cooperate, optionally in conjunction with one or more auxiliary VSCU units, to provide optimal HVAC system control according to the described embodiments.
For one embodiment that is particularly advantageous in the context of non-network-connected VSCU units, the VSCU unit is configured and programmed to use optically sensed information to determine an approximate time of day. For a large majority of installations, regardless of the particular location of installation in the home (the only exceptions being perhaps film photography development labs or other purposely darkened rooms), there will generally be a cyclical 24-hour pattern in terms of the amount of ambient light that is around the VSCU unit. This cyclical 24-hour pattern is automatically sensed, with spurious optical activity such as light fixture actuations being filtered out over many days or weeks if necessary, and optionally using ZIP code information, to establish a rough estimate of the actual time of day. This rough internal clock can be used advantageously for non-network-connected installations to verify and correct a gross clock setting error by the user (such as, but not limited to, reversing AM and PM), or as a basis for asking the user to double-check (using the circular display monitor 102), or to establish a time-of-day clock if the user did not enter a time.
According to one embodiment, each VSCU unit provides external data access at two different functionality levels, one for user-level access with all of the energy gaming and home management functionality described herein, and another for an installer/vendor (“professional”) that lets the professional “check in” on your system, look at all the different remote sensing gauges, and offer to provide and/or automatically provide the user with a service visit.
Provided according to some embodiments is a direct e-mail or text message command functionality for the remote user, such that they can send a brief control command to an e-mail address of the VSCU unit without being required to perform the full remote login and enter the command using the more complete user interfaces of
As could be realized by a person skilled in the art upon reading the present disclosure and based on system components and methods disclosed hereinabove and illustrated in the accompany drawings, provided in conjunction with the VSCU 100 and/or the VSCU Efficiency Platform are one or more devices, features or functionalities as described further hereinbelow.
According to some embodiments, various systems and methods for detecting occupancy of an enclosure, such as a dwelling, are provided by one or more of the installed VSCU units in the manner described in Ser. No. 12/881,430, supra. Examples include: detecting motion, monitoring communication signals such as network traffic and/or mobile phone traffic, monitoring sound pressure information such as in the audible and/or ultrasonic ranges, monitoring utility information such powerline information or information from Smart Meters, monitoring motion in close proximity to the sensor, monitoring infrared signals that tend to indicate operation of infrared controllable devices, sudden changes in ambient light, and monitoring indoor air pressure (to distinguish from pressure mats used in security applications) information which tends to indicate occupancy.
According to one embodiment that represents a combination of business method and technical method, acoustic monitoring is used to facilitate detect occupancy sensing, but the acoustic-to-electrical transducer equipment is purposely hampered in its ability to convert the acoustic energy of human speech into electrical form in a way that the actual human speech could be extracted therefrom. Stated differently, while the acoustic monitoring would be able to detect the presence of audible human activity, including speech, there would be no possibility of any actual words be “heard” by the VSCU unit even if those acousto-electric patterns were somehow recorded. In this way, privacy concerns of occupants and civil liberty groups are not problematic to the rollout and acceptance of the VSCU units and the VSCU Efficiency Platform. In one business method, this feature is actually used as a selling point for the product, being marketed with a moniker such as “privacy-preserving pressure wave sensing technology” or the like.
Particular examples of the above-described occupancy detection methods are now presented by way of example and not by way of limitation. One occupancy detection method is to incorporate a Wi-Fi sniffer capability into the VSCU units, i.e., when a lot of data traffic is seen on the user's home network, a conclusion can be made or supported that the house is occupied. Conversely, if the VSCU units are receiving remote control commands or other communications from a known user using a data communication device whose IP address is different than that of the home network, or a cell phone whose GPS location is different than that of the house, then a determination can be made or supported that that known user is not in the house. Other local electromagnetic signals associated with local user activity, such as cordless phone signals in the 900 MHz and 5.8 GHz, can also be used to make or support a determination that the house is occupied. Another occupancy detection method incorporated into the VSCU units is to sense infrared television remote control radiation as emitted from television remote control units. Another occupancy detection method uses the temperature and humidity readings of the VSCU units themselves. For example, a temperature/humidity change accompanies a pressure change, it is more likely that somebody opened an outside door and is therefore entering or leaving the building. Another occupancy detection method includes the consideration of user controls onto the VSCU units themselves. In a simplest example, if someone just adjusted the thermostat, there is certainly someone present in the house. In a more complex example, if a user just turned down the thermostat temperature in wintertime, and this is followed by a sensed sudden pressure change, then a determination can be made or supported that the occupants are leaving the building for some period of time. Also, if there are controls being made over the internet, by a cell phone or laptop or whatever, and the IP address corresponds to that of the home network, that you can conclude that the user is entering that information from inside the home, and therefore that the house is occupied.
For some embodiments, current energy-saving decisions based on current outside temperatures and predicted outside temperatures are provided. For example, if it is a really hot day but it is predicted that the outside temperature will be going down precipitously quite soon, the set point temperature may be raised at that time, or the amount of permissible swing raised or other action that causes a reduction in the number of cycles per hour. As another example, for a place like Arizona, if it is 40 degrees outside at 6 AM but it is expected that the outside temperature will be 100 degrees at 10 AM, the heat is not turned on at 6 AM even if the inside temperature is below the heating set point.
For some embodiments, anticipatory heating or cooling based on expected energy cost changes is provided. If a determination is made that the instantaneous cost of electricity will go up in a few hours based on current weather patterns and/or other aggregated data, the immediate cooling set point is lowered, and the set points for the subsequent hours are raised (and/or the acceptable swing is increased) so that more energy is used now and less energy is used later. Another concrete example is “spare the air” days which can be anticipated based on stored information and the recent and forecasted outside temperatures.
For some embodiments, centralized web-based communication with internet-connected VSCU units is provided to avoid blackouts during a heat wave. For “opt-in” VSCU-enabled customers who have so elected in exchange for financial incentives, the utility company (or VSCU data service provider on their behalf, optionally for a negotiated fee) can automatically issue a command that those VSCU units raise their set point temperatures by 5 degrees and it will automatically happen.
For some embodiments, there is provided user control over energy saving aggressiveness. Regarding the internal decisions made by the VSCU units, (e.g., weather-specific set points, anticipatory heating/cooling, compliance with external overrides, etc.), the user can be allowed to set this aggressiveness level during their setup interview, and also can be allowed change it later on. The setting can be “very aggressive savings,” “moderate savings”, “none”, and so forth. One example of automated weather-specific set point is that, for relatively cool days in which the outside temperature might be 84, the cooling set point is automatically set to 78, whereas if the outside temperature is greater than 95, the cooling set point is automatically set to 82. For some embodiments, the need for an increased (or decreased) level of aggressiveness can be automatically detected by the VSCU units and recommended to the user (e.g., on the circular user display 102 or on the remote control interface). In further embodiments, the level of aggressiveness can be automatically increased (or decreased) by the VSCU units, which then simply notify the user (e.g., on the circular user display 102 or on the remote control interface) that the aggressiveness change has been implemented.
According to some embodiments, the VSCU unit(s) installed in any particular home (or more generally “enclosure”) are automatically able to characterize its HVAC-related characteristics such as thermal mass, heating capacity, cooling capacity, and thermal conductivity metrics between the inside and the outside, for example using one or more methods described in Ser. No. 12/881,463, supra. For one embodiment, this characterization is made by operating the HVAC in various predetermined heating and cooling modes for predetermined time intervals at initial system installation testing, or at some other point in time, and then processing (i) the resultant temperature (and optionally humidity) profiles as sensed at the one or more VSCU units in conjunction with (ii) extrinsic information, such as building size, square footage, and so forth as provided by (a) the user during the congenial setup interview (or a separate interview) and/or (b) automatically scraped from public data sources, such as zillow.com, based on the home address as provided by the user. The installed VSCU units, optionally in conjunction with information provided by a VSCU data service provider, are configured to model the thermal and thermodynamic behavior of the enclosure for use in optimizing energy usage while also keeping the occupants comfortable. According to some embodiments, weather forecast data predicting future weather conditions for a region including the location of the enclosure are received. A model for the enclosure that describes the behavior of the enclosure for use by the control system is updated based on the weather forecast data. The HVAC system for the enclosure is then controlled using the updated model for the enclosure.
According to some embodiments, the weather forecast data includes predictions more than 24 hours in the future, and can include predictions such as temperature, humidity and/or dew point, solar output, precipitation, wind and natural disasters. According to some embodiments the model for the enclosure is updated based also on historical weather data such as temperature, humidity, wind, solar output and precipitation. According to some embodiments, the model for the enclosure is updated based in part on the occupancy data, such as predicted and/or detected occupancy data. The model for the enclosure updating can also be based calendar data. According to some embodiments, the model for the enclosure is updated based also on the data from the one or more weather condition sensors that sense current parameters such as temperature, humidity, wind, precipitation, and/or solar output. According to some embodiments, the locations of the weather condition sensors can be automatically detected. According to some embodiments, the model for the enclosure is updated based also on an enclosure model stored in a database, and/or on enclosure information from a user.
According to some embodiments, the enclosure modeling includes actively inducing a change in the internal environment of the enclosure, measuring a response of the internal environment of the enclosure from the induced change, and updating a model for the enclosure that describes behavior of the enclosure for use by the control system based at least in part on the measurement of the response from the induced change. According to some embodiments the change is actively induced primarily for purposes of updating the model for the enclosure, rather than for conditioning the internal environment of the enclosure. The change can be actively induced in response to input by a user, or it can be induced automatically by the VSCU units for example due to the type of enclosure or a change in season. The change is preferably induced at a time when the enclosure is likely to be unoccupied.
As used herein the term “model” refers generally to a description or representation of a system. The description or representation can use mathematical language, such as in the case of mathematical models. Examples of types of models and/or characteristics of models, without limitation, include: lookup tables, linear, non-linear, deterministic, probabilistic, static, dynamic, and models having lumped parameters and/or distributed parameters. As used herein the terms “profile,” “structure profile,” “structure model,” “enclosure profile,” “enclosure model,” “building profile,” “building model” and the like refer to any numerical or mathematical description or models of at least some of thermodynamic behavioral characteristics of a building, enclosure and/or structure, for example for use in HVAC applications. As used herein the term “sensor” refers generally to a device or system that measures and/or registers a substance, physical phenomenon and/or physical quantity. The sensor may convert a measurement into a signal, which can be interpreted by an observer, instrument and/or system. A sensor can be implemented as a special purpose device and/or can be implemented as software running on a general-purpose computer system. As used herein the term “structure” includes enclosures and both non-buildings and buildings. As used herein the term “enclosure” means any structure having one or more enclosed areas, and also includes any building. Examples of structures and enclosures include, but are not limited to: residential buildings, commercial buildings and complexes, industrial buildings, sites and installations, and civil constructions. As used herein the term “thermodynamic” includes all state variables that can be used to characterize a physical system. Examples of thermodynamic variables include, but are not limited to: pressure, temperature, airflow, humidity, and particulate matter.
According to some embodiments, the VSCU units are configured and programmed to automatically determine, based on sensed performance data, when one or more air filters of the HVAC system (see, for example, filter 246 of
For other embodiments, similar automated detection, customer alerting, and maintenance event triggering as described in the preceding paragraph is provided for any type of HVAC system anomaly such as, but not limited to, the general failure of the house to heat or cool to the set point temperature or the clogging of a particular duct in the house (e.g., its airflow readings are grossly different than that of other sensors in other ducts). For one embodiment, acoustic signature sensing can be used to detect system anomalies, which takes advantage of the fact that a system's heating and cooling start up and shut down activity will often be characterized by unique yet repeatable noise signatures (e.g., fan noises, particular creaks and moans for older installations, etc), and that an onset of a variation in these noise signatures can be indicative of a system anomaly. In still other embodiments, baseline electrical noise patterns can be associated with each different HVAC control wire and stored, and then the VSCU unit 100 can automatically detect a potential system anomaly by sensing a significant variation in the noise pattern of one or more of the HVAC control wires.
For still other embodiments, other types of auxiliary sensors related to HVAC functionality, including both self-powering energy-harvesting sensors and those that get their power from other sources such as AC or batteries, are provided that are capable of ZigBee communication and are compatible with the VSCU Efficiency Platform, and used to sense system anomalies and/or maintenance-related information that the VSCU units can then act upon. In one example, a replacement cap for an outside propane or heating oil tank is provided that is capable of wirelessly sending fuel levels to the VSCU units, the cap optionally being powered by energy harvesting from the wind. In another example, a replacement cap for a coolant loop check valve is provided that is capable of wirelessly sending coolant loop pressure readings or a low-coolant alarms to the VSCU units, the cap optionally being powered by energy harvesting from compressor vibrations or other air conditioning system vibrations.
According to some embodiments, the initial setup interview includes the following interactive questioning flow. The VSCU unit display format will look similar to
According to some embodiments, the ZIP code of the household or business is asked at a point near the beginning of the setup interview, and then different setup interview questions can be asked that are pre-customized for different geographical regions based on the ZIP code. This is useful because the best set of interview questions for Alaskan homes or businesses, for example, will likely be different than the best set of interview questions for Floridian homes, for example.
According to some embodiments, the user's responses to the questions at the initial setup interview are used to automatically “snap” that household onto one of a plurality of pre-existing template schedules, i.e. a schedule of time intervals and set point temperatures for each time interval, stored in the VSCU unit and corresponding to some of the most common household or business paradigms. Examples of different household paradigms, each of which can have its own pre-existing template schedule, can include: working couple without kids; working couple with infants or young children; working family; working spouse with stay-at-home spouse; young people with active nightlife who work freelance from home; retired couple; and solo retiree. The template schedules to which the household is “snapped” at system initialization based on the setup interview (or at some other time upon user request) serve as convenient starting points for the operational control of the HVAC system for a large number of installations. The users can then modify their template schedules (e.g., using the user on the VSCU unit itself, the web interface, or smart phone interface, etc.) to suit their individual desires. The VSCU units may also modify these template schedules automatically based on learned occupancy patterns and manual user temperature control setting patterns. By way of nonlimiting example, a typical template schedule for a working family would be, for heating in wintertime “Mo Tu We Th Fr: [7:00 68] [9:00 62] [16:00 68] [22:00 62] Sa Su [7:00 68] [22:00 62]” (meaning that, for all five weekdays the set point temperatures will be 68 degrees from 7 AM-9 AM, then 62 degrees from 9 AM-4 PM, then 68 degrees from 4 PM-10 PM, then 62 degrees from 10 PM-7 AM, and that for both weekend days the set point temperatures will be 68 degrees from 7 AM-10 PM, then 62 degrees from 10 PM-7 AM), and for cooling in summertime, “Mo Tu We Th Fr: [7:00 75] [9:00 82] [16:00 78] [22:00 75] Sa Su [7:00 75] [9:00 78] [22:00 75].” In other embodiments, permissible swing temperature amounts, humidity ranges, and so forth can also be included in the template schedules.
For one embodiment, template schedules can be shared, similar to the way iTunes music playlists can be shared, optionally in a social networking context. For example, a user can post their template schedule on their Facebook or MySpace page for other people to download. Custom or standardized template schedules can be provided based on house size or ZIP code. Templates schedules will preferably be calendar-based (e.g., scheduled differently for Christmastime when more people are home). This is superior to prior art scheduling in which all customers everywhere are given the same schedule or the same set of strictures within which to program their schedule.
For one embodiment, customized installation instructions can be provided to the user based on their previously installed thermostat model. The user can go to the VSCU manufacturer's web site and enter their current thermostat make and model, and then a custom set of instructions based on the known wiring pattern of that model are provided for viewing, download, and printing. Optionally, customized videos on the user's computer or smart phone are provided. For one more advanced preferred embodiment, the user can take a photo of their current thermostat and submit it to the VSCU manufacturer's web site where its make and model will be automatically determined using machine vision techniques, so that the user does not need to figure out their current make and model.
For one embodiment, the VSCU units are configured and programmed to automatically detect and correct for exposure of one or more VSCU units to direct sunlight. Although users are advised, as with any thermostat, to avoid placing the VSCU units in areas of direct sunlight, it has been empirically found that many will place a VSCU unit where it will get direct sunlight for at least part of the day during at least a part of the year. Direct sunlight exposure can substantially confound HVAC system effectiveness because the temperature will be sensed as being incorrectly high, for example, the VSCU unit will measure 80 degrees when it is really only 68 degrees in the room. According to an embodiment, the one or more VSCU units are programmed to detect a direct sunlight exposure situation, such as by temperature tracking over periods of several days to several weeks and then filtering for periodic behaviors characteristic of direct sunlight exposure, and/or filtering for characteristic periodic discrepancies between multiple VSCU units. Correction is then implemented using one more correction methods.
By way of example and not by way of limitation, one simple method for correction for heating and cooling is to apply a direct numerical bias to the sunlight-bathed sensor reading during the direct sunlight interval based on knowledge from ambient light sensor reading, current time, current exact or approximate date, previous heat/cool cycle duration, temperature changes, and humidity changes. The VSCU unit learns from the first couple of occurrences the time and duration at which the sunlight falls on the device. For example, if the sunlight hit the sensor between 9:00-9:15 AM the day before in the spring, it will look for the sunlight occurrence around 8:58-9:13 AM the next day. If the heat/cool cycle is not needed during this time, one way to correct it would be to make an estimate of the temperature when the effect of the direct sunlight diminishes and make an interpolation between the current temperature and the predicted temperature between 8:58-9:13 AM. If the heat/cool cycle needs to be on, it learns from the previous cycles and make an estimate of cycle duration and temperature changes. It may use humidity and other sensors (in the device itself or in another device nearby) to verify the heat/cool cycle is on and remains on for an appropriate amount of time.
For some embodiments, the VSCU units provide optimal yet energy saving control based on human comfort modeling. In one example, if the user keeps turning up the thermostat above the set points provided in the template schedule, then VSCU units learn that and increase the set points in their template schedule. By way of further example, if the outside temperature has been 80 degrees for many days, and then for one day it is suddenly 60 degrees, the VSCU unit will keep the house at a warmer set point than if the outside temperature has been 60 degrees for many days. The reason is that humans are known to get accustomed to outside weather patterns that have been prevailing for a period of time, and so are more sensitive to sudden temperature changes than to longer term temperature changes. For example, if it has been 60 degrees for many days, the people will be more likely to dress warmer on an ongoing basis (put on sweatshirts and the like) and so the set point can be gradually lowered and/or the amount of swing can be gradually raised to save energy.
As another example of optimal yet energy saving control based on human comfort modeling, for one embodiment the VSCU is configured to perform in an advantageous way based on a predicted return time of the occupant. For this embodiment, the idea is to purposely pre-heat (or pre-cool in a counterpart example) the house, but only to a limited extent, perhaps only 60% of the difference between the “Away” and “Occupied” set points, until there is actually an occupancy detection event. For example, if the “Away” set point temperature is 64, and the “Occupied” set point temperature is 74, then the VSCU units start heating the house 20 minutes before the expected home arrival time, but only do so until the house heats up to 70 degrees. Then, when the occupant walks through the door, the remaining 4 degree heat-up is triggered by the VSCU units. In addition to saving energy, this can also be pleasing to the senses of the returning occupant, because the heat will be blowing, which gives a sense of hominess and of feeling welcome, a sense of “it is great to be home, it is so nice.” Moreover, it has been found that people are a lot more tolerant to the lower temperature immediately after they have walked through door than if they have been home for a while.
As another example of optimal yet energy saving control provided by the VSCU units, there is a control algorithm found to provide good results for situations of extended but finite opening of an external door, such as cases in which an occupant is bringing in the Christmas Tree or the groceries. In particular, if it usually takes 5 minutes to heat from 68 to 72, and it suddenly has taken 5 minutes just to heat from 68 to 69 or there has been no change at all from 68 in 5 minutes of heating, the VSCU unit will immediately turn off the heat for 10-15 minutes, and then try again to raise the temperature back to 72, under the possibility that the anomaly was temporary. And if it was indeed temporary, then the situation has resolved itself. But if the failure to heat up happens again, then there can be an alarm (or text message) that requests the user's attention, and if there is no response from the user the system is shut down because there is obviously something wrong. An e-mail message can be sent to the user such as “We have ruled out these things x-y-z from our sensor logs, maybe there is an outside door open or a-b-c is wrong.”
For another embodiment, there is provided a combined business and technical method relating to the “learning” process of the VSCU unit 100. The VSCU units are programmed to provide substantial “learning” about user occupancy and temperature control patters. The user will be advised at various times, such as by remote access, e-mail, SMS, VSCU unit display, etc., regarding the progress of the learning (e.g., “your occupancy information is 60 percent learned”). However, there will also be an ability for the users to turn off the learning function because they might not be comfortable with in. In one embodiment, the VSCU system will “act” like it is not learning (such as by stopping the progress messages), but will actually still be learning in the background, running in a simulation mode and continue to compile the learning data. Then, after some period has passed, the VSCU unit can compute the energy cost difference between the actual model it was running, versus the simulation model it was running in the background. If there is a substantial difference of “X” dollars, the user can be shown or sent a message such as, “You could have saved $44 if you had enabled learning-driven control, are you sure that you do not want to turn it on now?”
For another embodiment, there is provided a combined business and technical method in which users are offered a subscription service by a VSCU data service provider. As the VSCU data service provider comes up with new types of algorithms, they can offer VSCU unit customers a subscription to an external control/optimization service. As part of the offering process, the VSCU data service provider can run the new algorithms on the historical internal and external temperature data for that customer, and then say to them (by VSCU unit display or remote access display, for example), “If you had subscribed to this optimization service, you would have saved $88 last year”. Similar offerings can be made for discrete firmware version upgrades, e.g., “If you had purchased VSCU unit software version 2.0 instead of staying with version 1.0, you would have saved $90. Would you like to buy version 2.0 now for $20?”
For another embodiment, there is provided a combined business and technical method in which users are given advisory messages (by VSCU unit display or remote access display, for example) such as follows: “A VSCU-capable house in your ZIP code having the same size as your house spent $1000 for heating and cooling, whereas you spent $2000. You may have a leak or weather-stripping problem. You may wish to call ABC HVAC Service Company at 650-555-1212 who can do an energy audit to help you figure out what is wrong.”
For another embodiment, the VSCU units are programmed and configured to provide the user with the ability to control their HVAC system exclusively on the basis of an HVAC budget rather than on target temperature settings. The user simply enters a dollar amount per month that they want to spend on HVAC, and the VSCU automatically adjusts the settings such that the selected amount will be spent, in the most comfortable (or least uncomfortable) manner possible according to the user's known occupancy patterns and preferences. Optionally, the user can manually turn the set temperature up or down from the VSCU-established schedule, but if they do so, the VSCU unit will immediately display the difference in cost that will occur (For example, “Extra $5 per day: Continue? {Yes} {No}”. The calculations can take into account seasonal weather patterns, what month it is now, weather forecasts, and so forth. For another embodiment, the VSCU unit can ask the user, on its own initiative, “Do you want to save $100 this month by having VSCU manage your settings? {Yes} {No}” (as opposed to just asking “how about reducing temperature one degree”).
For another embodiment, the VSCU units are programmed and configured to provide the user with “pre-paid HVAC” and/or “pay as you go HVAC”. Based on a pre-paid amount or a pre-budgeted amount, the VSCU display will show the dollar amount that is remaining from that pre-paid or budgeted amount. This can be particularly useful in landlord-tenant environments or property management environments, wherein the landlord can program in the amount, and the tenant can see how much is left at any particular point in time. This can also be useful for vacation homes, allowing property managers to remotely manage power usage and settings. As part of this, the software locking mechanism described previously can determine who is using the thermostat based on personal codes, so the VSCU will know the identity of the user. This can still be useful in a single-family home setting, where certain targets can be set and the family can dynamically see a running tally as to how well they are performing relative to that target. The money amounts can be a set of default estimates, or can be based on actual usage as accessed from a utility company database using, for example, smart-meter readings.
For another embodiment, the VSCU units are programmed and configured to provide temperature setting governance based on user identity. The software locking functionality is used to ensure that only people with passcodes can change the VSCU temperature settings, and the VSCU unit furthermore recognizes a separate landlord (or other “governor”) password and one or more separate tenant (or other “governee”) passwords. The landlord can then login and set a maximum set temperature, such as 75. Thereafter, although the tenant can make temperature changes, the VSCU unit will not allow the tenant to set the temperature above 75 degrees. Various tamper-proofing mechanisms can be provided. As a default tamper-proofing mechanism, the landlord would be able to access the VSCU data service provider web site to ensure that the VSCU unit is reporting in at regular intervals with its usage data, to request weather data, and so forth.
For another embodiment, with reference to the hotel 1202 of
Further provided by the VSCU units is an automated override or overwriting of template schedule set point levels or time interval definitions that the user may have manually specified to the VSCU unit, either by remote control or direct entry into the VSCU unit (such as during the setup interview), based on their actual control behaviors after those inputs were made. For example, if the user specified in the setup interview that they come home at 5 PM every day, but then there are multiple days in a row (for example, 2 days or 3 days in a row) that the temperature was turned up from 62 to 65 at 4:30 PM, this is used to weight the schedule and turn the set point up to 65 at 4:20 PM thereafter, such that the temperature will be preheated to 65 by 4:30 PM when the user is expected to walk through the door. The automatic changes made by the VSCU units to the template schedule to conform around the actual occupancy behavior of the user, rather than the user's own estimates of their occupancy behavior, can take place gradual over a period of many days, or can be immediately effective on a single day, without departing from the scope of the present teachings.
For another embodiment, the VSCU units are programmed and configured to automatically switch over from heating to cooling functionality by resolving any ambiguity in user intent based on sensed information. Part of the elegance of the VSCU unit 100 of
For some embodiments, which are particularly applicable in view of ongoing improvements in automated sensing, a personalized control paradigm is promoted by the VSCU units, that is, the VSCU units function to automatically detect and identify individual users in the home and attempt to identify their current and upcoming individual needs and desires with respect to VSCU-related functionality. For one example, the VSCU units are programmed with a “fingerprinting” functionality to recognize a particular user who is making a current control adjustment at the face of the unit, and then adjusting its response if appropriate for that user. For example, the particular way the user has turned the VSCU unit outer ring, or where they put their fingers on the VSCU unit dial or body (using touch sensors), how much pressure they exert for an inward click, and how close their body is to the VSCU unit dial (using a proximity sensor) can be used as their “fingerprint”. In one example, each user can be identified and initially “fingerprinted” in a separate question-and-answer session, and their personal preferences can thereafter be learned by virtue of their control inputs to the VSCU units from both remote locations and on the dial. At first, most of the fingerprinting can be done via user's commands from their mobile phone as well as the web. People will be controlling the thermostat a lot from their phone before getting home, or after they have left. Also, if they are somewhere else with an easier access to a computer (or even at home computer), they will use the web. Personalized control from VSCU units can be based on multiple maps of a “user comfort model” for the identified person. A model is built on what their preference/physical comfort zone is like. But if there are multiple users who have very different preferences, there may be a benefit in building two (or more) different models than to completely average them. The VSCU can learn to implement a comfortable temperature based on one model or the other based on who is at home, for example, based on which mobile device is at home (or other signatures) or which user is away by virtue of having accessed the system from a remote IP address. A web service can be used to inform these differences, which is informative to the user (and may result in the user telling their spouse to put on a sweater). For one concrete example of individualized occupancy detection and set point adjustment according to an embodiment, the VSCU units can make a conclusion that a first occupant “M” likes it cooler, while a second occupant “W” likes it warmer based on their settings and their remote and direct controls to the VSCU units. When the system determines that “W” is home and “M” is not at home, then the temperature is set higher, or otherwise follows a separate template schedule customized for “W”. The presence of “W” and the absence of “M” can be detected, for example, using IP traffic analysis methods to determine that “M” is still at work while the home is sensed to have an occupant, which must be “W”.
Provided according to some embodiments is a gesture-based user interface for the VSCU units. For one embodiment, a touch-sensitive display is provided in which sliding touch controls are enabled, similar to swipe controls and other gestures used by the iPad and iPhone. Alternatively, a small camera can be placed on the VSCU unit, which is programmed with the ability to process the optical input information such that it can recognize hand gestures (clockwise hand rotation to turn up the temperature, counterclockwise to turn down the temperature), similar to the way that the Microsoft Kinect™ sensor works in conjunction with the Xbox 360® video gaming console to provide controller-free, gesture-based user inputs (i.e., inputs based on hand, foot, or body motion without requiring the user to hold a controller device or to otherwise have a hardware input device on their person).
Provided according to some embodiments is an VSCU unit, which can function as either an auxiliary VSCU unit or primary VSCU unit, having a network-only user interface such that the physical unit itself has no controls whatsoever. The user must have a data appliance to access it and control it. The network-only VSCU unit may be useful for many situations such as college dormitories, or can be a very low-cost starter VSCU unit for a young but technically savvy apartment dweller.
Provided according to some embodiments is the use and functionality of installed VSCU units to serve as an HVAC-centric home energy hub based on the VSCU Energy Efficiency Platform with which many common home appliances will be compatible under license or other business arrangement with the VSCU unit manufacturer and/or VSCU data service provider. The VSCU units are functional as central “energy hub” for the whole house. The VSCU unit is a good way to instantiate such a “home energy network” because people need a thermostat anyway, and once it is installed it can be the core for such a network. For example, using wireless communications the VSCU unit can communicate with the dishwasher, or the refrigerator. If the user walks up to the dishwasher and attempts to start it, there can be a display on the dishwasher that says “Would you like to start the load now for $1, or wait until 2 AM and do the load for 20 cents?” The VSCU units serve and the conduit and core for such a platform. In one example of many advantages, with occupancy sensing the VSCU unit can sense when the occupants are not home, and automatically command the refrigerator to turn up its set point by 2 degrees, and then command it to return to normal after the VSCU has sensed that the occupants have returned. Similar functionalities can be provided in conjunction with any hot water heaters, hot tubs, pool heaters, and so forth that are equipped and licensed to be compatible with the VSCU Energy Efficiency Platform.
For some embodiments, business methods are provided for effective commercial introduction and rollout of the VSCU units and the evolution of the VSCU Efficiency Platform. At a start date of first product introduction, the simpler DIY packages of VSCU units are made available at a retail level including both online stores and brick-and-mortar stores. For buying a first primary VSCU unit, the customer gets free web access to the online tools of the VSCU data service provider (who can be the same entity as, or a partner entity to, the manufacturer of the VSCU unit), including for example the web-based remote control functionality as shown in
Provided in one embodiment is a filterless HVAC system. Instead of using a disposable filter, which can reduce HVAC efficiency when it starts to get clogged, the HVAC system is equipped with a filtering system similar to those used in one or more bagless vacuum cleaners and identified by various trade names such as “cyclonic” or “tornado” or “wind tunnel”, for example the Dyson DC25 Upright Vacuum cleaner, the Hoover Windtunnel II Bagless Upright Vacuum Cleaner, the Bissell 5770 Healthy Home Bagless Upright Vacuum, the Electrolux EL 7055A Twin Clean Bagless Canister Vacuum, and/or the Hoover UH70010 Platinum Collection Cyclonic Bagless Upright Vacuum Cleaner. By designing the filter out of the HVAC system altogether, the homeowner simply needs to change a canister once in a while, and the HVAC system does not lose efficiency over time like a regular filter does.
Provided in some embodiments are VSCU units into which are integrally provided other essential home monitoring device functionalities combined smoke detection, heat detection, motion detection, and CO2 detection. As an optional business method, such VSCU units can be sold at a deep discount or given away for free, with revenue being generated instead by subscriptions to the data services of the VSCU data service provider. Alternatively, they can be given away for free or heavily subsidized by a utility company that is partnered with the VSCU data service provider in exchange for customer “opt in” to voluntary data collection and/or remote VSCU setting programs applicable during periods of energy shortage or other energy emergency.
Provided according to some embodiments are algorithms for automated setpoint determination based on a setpoint temperature schedule and manual user setpoint modifications. As an ongoing rule for any manual user setpoint change, any setpoint entered by the user at a primary or auxiliary VSCU user interface will take effect for a maximum of four hours, at which point operation is then returned to the normal setpoint schedule. In the event that the normal setpoint schedule would call for a scheduled temperature change within that four hour interval (for example, a scheduled change to a sleeping temperature at 10:00 PM), then that scheduled temperature setpoint overrides the manual user setpoint input at that time.
Provided according to some embodiments are algorithms for setpoint schedule departure and/or setpoint schedule modification based on sensed enclosure occupancy and user setpoint modification behaviors. One example of such a setpoint schedule departure algorithm, termed herein an “auto away/auto arrival” algorithm, is described further hereinbelow.
In accordance with a preferred “auto away” algorithm, an enclosure occupancy state is continuously and automatically sensed using the VSCU multi-sensing technology, the currently sensed state being classified as occupied (or “home” or “activity sensed”) or unoccupied (or “away” or “inactive”). If the currently sensed occupancy state has been “inactive” for a predetermined minimum interval, termed herein an away-state confidence window (ASCW), then an “auto-away” mode of operation is triggered in which an actual operating setpoint 1504 is changed to a predetermined energy-saving away-state temperature (AST), regardless of the setpoint temperature indicated by the normal thermostat schedule 1502. The purpose of the “auto away” mode of operation is to avoid unnecessary heating or cooling when there are no occupants present to actually experience or enjoy the comfort settings of the schedule 1502, thereby saving energy. The AST may be set, by way of example, to a default predetermined value of 62 degrees for winter periods (or outside temperatures that would call for heating) and 84 degrees for summer periods (or outside temperatures that would call for cooling). Optionally, the AST temperatures for heating and cooling can be user-settable.
The away-state confidence window (ASCW) corresponds to a time interval of sensed non-occupancy after which a reasonably reliable operating assumption can be made, with a reasonable degree of statistical accuracy, that that there are indeed no occupants in the enclosure. For most typical enclosures, it has been found that a predetermined period in the range of 90-180 minutes is a suitable period for the ASCW, to accommodate for common situations such as quiet book reading, stepping out to the corner mailbox, short naps, etc. in which there is no sensed movement or related indication for the occupancy sensors to sense.
In the example of
The “auto-away” mode can be terminated based on sensed events, the passage of time, and/or other triggers that are consistent with its essential purpose, the essential purpose being to save energy when no occupant, to a reasonably high statistical degree of probability, are present in the enclosure. For one embodiment, the “auto-away” mode of operation maintains the setpoint temperature at the energy-saving AST temperature until one of the following occurs: (i) a manual corrective input is received from the user; (ii) an “auto-return” mode of operation is triggered based on sensed occupancy activity; (iii) normal occupant sleeping hours have arrived and a determination for a “vacation” mode has not yet been reached; or (iv) the subsequent day's “wake” or “at home” interval has arrived and a determination for a “vacation” mode has not yet been reached.
Thus, shown in
Preferably, the user is provided with an ability (e.g., during initial setup interview, by the Web interface, etc.) to vary the ASCW according to a desired energy saving aggressiveness. For example, a user who selects a “highly aggressive” energy saving option can be provided with an ASCW of 45 minutes, with the result being that the system's “auto-away” determination will be made after only 45 minutes of inactivity (or “away” or “unoccupied” sensing state).
Various methods for sub-windowing of the ASCW time period and filtering of sensed activity can be used to improve the reliability of the triggering of the “auto-away” mode. Various learning methods for “understanding” whether sensed activity is associated with human presence versus other causes (pets, for example) can also be used to improve the reliability of the triggering of the “auto-away” mode. For one embodiment, a “background” level of sensed activity (i.e., activity that can be attributed to sensed events that are not the result of human occupancy) can be interactively learned and/or confirmed based on the absence of corrective manual setpoint inputs during an “auto-away” mode period. For example, if there are no corrective manual setpoint changes for a period of time following after the “auto-away” mode is triggered, and such absence of corrective input repeats itself on several different occasions, then it can be concluded that the type and/or degree of sensed activity associated with those intervals can be confirmed as being “background” levels not associated with human presence, the reasoning being that if a human were indeed present, there would have been some type of corrective activity on one or more of such occasions.
In a manner similar to the “auto-away” occupancy evaluation, the triggering of an “auto-return” mode of operation is likewise preferably based on sub-windowed time windows and/or filtering of the sensed activity, such that spurious events or other events not associated with actual human presence do not unnecessarily trigger the “auto-return” mode. For one example, the sensing process involves separately evaluating 5-minute subwindows (or subwindows of other suitable duration) of time in terms of the presence or absence of sensed activity during those subwindows. If it is found that a threshold amount of activity is sensed in two adjacent ones of those time subwindows, then the “auto-return” mode is triggered (see, for example, the time interval 1508 of
Provided according to one embodiment is an algorithm for setpoint schedule modification based on occupancy patterns and/or corrective manual input patterns associated with repeated instances of “auto-away” mode and/or “auto-arrival” mode operation. Occupancy and/or corrective manual input behaviors associated with “auto-away/auto-arrival” mode are continuously monitored and filtered at multiple degrees of time periodicity in order to detect patterns in user occupancy that can, in turn, be leveraged to “trim” or otherwise “tune” the setpoint temperature schedule to better match actual occupancy patterns. By filtering at multiple levels of time periodicity, it is meant that associated patterns are simultaneously sought (i) on a contiguous calendar day basis, (ii) on a weekday by weekday basis, (iii) on a weekend-day by weekend-day basis, (iv) on a day-of-month by day-of-month basis, and/or on the basis of any other grouping of days that can be logically linked in terms of user behavior. Thus, for example, if a particular occupancy and/or corrective manual input behavior associated with “auto-away/auto-arrival” is observed for a series of successive Fridays, then the setpoint temperature schedule for Fridays is adjusted to better match the indicated occupancy pattern. If a particular occupancy and/or corrective manual input behavior associated with “auto-away/auto-arrival” is observed for both a Saturday and Sunday, and then for the next Saturday and Sunday, and then still for the following Saturday and Sunday, then the setpoint temperature schedule for Saturdays and Sundays is adjusted to better match the indicated occupancy pattern detected. As yet another example, if a particular occupancy and/or corrective manual input behavior associated with “auto-away/auto-arrival” is observed for the 2nd through 7th day of the month for several months in a row, then the setpoint temperature schedule for the 2nd through 7th day of the month is adjusted, and so on.
Importantly, if there had occurred a corrective user input (which can be called a “punishing” user input) on one of the days illustrated in
Whereas the “auto away/auto arrival” algorithm of the above-described embodiments is triggered by currently sensed occupancy information, in another embodiment there is provided automated self-triggering of “auto away/auto arrival” algorithm based on an empirical occupancy probability time profile that has been built up by the VSCU unit(s) over an extended period of time. For one embodiment, the empirical occupancy probability time profile can be expressed as a time plot of a scalar value (an empirical occupancy probability or EOP) representative of the probability that one or more humans is occupying the enclosure at each particular point in time. Any of a variety of other expressions (e.g., probability distribution functions) or random variable representations that reflect occupancy statistics and/or probabilities can alternatively be used rather than using a single scalar metric for the EOP.
For one embodiment, the VSCU unit is configured to self-trigger into an “auto-away” mode at one or times during the day that meet the following criteria: (i) the normal setpoint schedule is indicative of a scheduled “at home” time interval, (ii) the empirical occupancy probability (EOP) is below a predetermined threshold value (e.g., less than 20%), (iii) the occupancy sensors do not sense a large amount of activity that would unambiguously indicate that human occupants are indeed present in the enclosure, and (iv) the occupancy sensors have not yet sensed a low enough level of activity for a sufficiently long interval (i.e., the away-state confidence window or ASCW) to enter into the “auto away” mode in the “conventional” manner previously described. Once these conditions are met and the “auto-away” mode has been self-triggered, reversion out of the “auto away” mode can proceed in the same manner (e.g., by “auto-arrival” triggering, manual corrective user input, etc.) as for the “conventional” auto-away mode. Automated tuning of the setpoint temperature schedule based on the “lessons learned” (i.e., based on occupancy patterns and/or corrective manual input patterns associated with repeated instances of “auto-away” mode) can be based on the combined observations from the “conventionally” triggered auto-away mode and the self-triggered auto-away mode algorithms.
The above-described self-triggering of the “auto-away” mode, which is based at least in part on empirical occupancy probability (EOP), has been found to provide for more complete and more statistically precise “tuning” of the setpoint temperature schedule when capered to tuning that is based only on the “conventional” auto-away triggering method in which only current, instantaneous occupancy information is considered. One reason relates to the large number of activity-sensing data samples used in generating the EOP metric, making it a relevant and useful basis upon which to perform the occupancy “test” afforded by the “auto-away” process. From one perspective, the “auto-away” process can be thought of as a way to automatically “poke” or “prod” at the user's ecosystem to learn more detail about their occupancy patterns, without needing to ask them detailed questions, without needing to rely on the correctness of their responses, and furthermore without needing to rely exclusively on the instantaneous accuracy of the occupancy sensing hardware.
Although being formed from a single lens-like piece of material such as polycarbonate, the cover 1814 has two different regions or portions including an outer portion 1814o and a central portion 1814i. According to some embodiments, the cover 1814 is painted or smoked around the outer portion 1814o, but leaves the central portion 1814i visibly clear so as to facilitate viewing of an electronic display 1816 disposed thereunderneath. According to some embodiments, the curved cover 1814 acts as a lens that tends to magnify the information being displayed in electronic display 1816 to users. According to some embodiments the central electronic display 1816 is a dot-matrix layout (individually addressable) such that arbitrary shapes can be generated, rather than being a segmented layout. According to some embodiments, a combination of dot-matrix layout and segmented layout is employed. According to some embodiments, central display 1816 is a backlit color liquid crystal display (LCD). An example of information displayed on the electronic display 1816 is illustrated in
Motion sensing as well as other techniques can be use used in the detection and/or predict of occupancy, as is described further in the commonly assigned U.S. Ser. No. 12/881,430, supra. According to some embodiments, occupancy information is used in generating an effective and efficient scheduled program. Preferably, an active proximity sensor 1870A is provided to detect an approaching user by infrared light reflection, and an ambient light sensor 1870B is provided to sense visible light. The proximity sensor 1870A can be used to detect proximity in the range of about one meter so that the thermostat 1800 can initiate “waking up” when the user is approaching the thermostat and prior to the user touching the thermostat. Such use of proximity sensing is useful for enhancing the user experience by being “ready” for interaction as soon as, or very soon after the user is ready to interact with the thermostat. Further, the wake-up-on-proximity functionality also allows for energy savings within the thermostat by “sleeping” when no user interaction is taking place our about to take place. The ambient light sensor 1870B can be used for a variety of intelligence-gathering purposes, such as for facilitating confirmation of occupancy when sharp rising or falling edges are detected (because it is likely that there are occupants who are turning the lights on and off), and such as for detecting long term (e.g., 24-hour) patterns of ambient light intensity for confirming and/or automatically establishing the time of day.
According to some embodiments, for the combined purposes of inspiring user confidence and further promoting visual and functional elegance, the thermostat 1800 is controlled by only two types of user input, the first being a rotation of the outer ring 1812 as shown in
According to some embodiments, the thermostat 1800 includes a processing system 1860, display driver 1864 and a wireless communications system 1866. The processing system 1860 is adapted to cause the display driver 1864 and display area 1816 to display information to the user, and to receiver user input via the rotatable ring 1812. The processing system 1860, according to some embodiments, is capable of carrying out the governance of the operation of thermostat 1800 including the user interface features described herein. The processing system 1860 is further programmed and configured to carry out other operations as described further hereinbelow and/or in other ones of the commonly assigned incorporated applications. For example, processing system 1860 is further programmed and configured to maintain and update a thermodynamic model for the enclosure in which the HVAC system is installed, such as described in U.S. Ser. No. 12/881,463, supra. According to some embodiments, the wireless communications system 1866 is used to communicate with devices such as personal computers and/or other thermostats or HVAC system components, which can be peer-to-peer communications, communications through one or more servers located on a private network, or and/or communications through a cloud-based service.
To more accurately determine the ambient temperature, the temperature taken from the lower thermal sensor 330b is taken into consideration in view of the temperatures measured by the upper thermal sensor 330a and when determining the effective ambient temperature. This configuration can advantageously be used to compensate for the effects of internal heat produced in the thermostat by the microprocessor(s) and/or other electronic components therein, thereby obviating or minimizing temperature measurement errors that might otherwise be suffered. In some implementations, the accuracy of the ambient temperature measurement may be further enhanced by thermally coupling upper thermal sensor 330a of temperature sensor 330 to grille member 1990 as the upper thermal sensor 330a better reflects the ambient temperature than lower thermal sensor 334b. Details on using a pair of thermal sensors to determine an effective ambient temperature is disclosed in U.S. Pat. No. 4,741,476, which is incorporated by reference herein.
In accordance with the teachings of the commonly assigned U.S. Ser. No. 13/269,501, supra, the commonly assigned U.S. Ser. No. 13/275,307, supra, and others of the commonly assigned incorporated applications, the thermostat 1800 represents an advanced, multi-sensing, microprocessor-controlled intelligent or “learning” thermostat that provides a rich combination of processing capabilities, intuitive and visually pleasing user interfaces, network connectivity, and energy-saving capabilities (including the presently described auto-away/auto-arrival algorithms) while at the same time not requiring a so-called “C-wire” from the HVAC system or line power from a household wall plug, even though such advanced functionalities can require a greater instantaneous power draw than a “power-stealing” option (i.e., extracting smaller amounts of electrical power from one or more HVAC call relays) can safely provide. By way of example, the head unit microprocessor 2402 can draw on the order of 250 mW when awake and processing, the LCD module 1960 can draw on the order of 250 mW when active. Moreover, the Wi-Fi module 2410 can draw 250 mW when active, and needs to be active on a consistent basis such as at a consistent 2% duty cycle in common scenarios. However, in order to avoid falsely tripping the HVAC relays for a large number of commercially used HVAC systems, power-stealing circuitry is often limited to power providing capacities on the order of 100 mW-200 mW, which would not be enough to supply the needed power for many common scenarios.
The thermostat 1800 resolves such issues at least by virtue of the use of the rechargeable battery 1944 (or equivalently capable onboard power storage medium) that will recharge during time intervals in which the hardware power usage is less than what power stealing can safely provide, and that will discharge to provide the needed extra electrical power during time intervals in which the hardware power usage is greater than what power stealing can safely provide. In order to operate in a battery-conscious manner that promotes reduced power usage and extended service life of the rechargeable battery, the thermostat 1800 is provided with both (i) a relatively powerful and relatively power-intensive first processor (such as a Texas Instruments AM3703 microprocessor) that is capable of quickly performing more complex functions such as driving a visually pleasing user interface display and performing various mathematical learning computations, and (ii) a relatively less powerful and less power-intensive second processor (such as a Texas Instruments MSP430 microcontroller) for performing less intensive tasks, including driving and controlling the occupancy sensors. To conserve valuable power, the first processor is maintained in a “sleep” state for extended periods of time and is “woken up” only for occasions in which its capabilities are needed, whereas the second processor is kept on more or less continuously (although preferably slowing down or disabling certain internal clocks for brief periodic intervals to conserve power) to perform its relatively low-power tasks. The first and second processors are mutually configured such that the second processor can “wake” the first processor on the occurrence of certain events, which can be termed “wake-on” facilities. These wake-on facilities can be turned on and turned off as part of different functional and/or power-saving goals to be achieved. For example, a “wake-on-PROX” facility can be provided by which the second processor, when detecting a user's hand approaching the thermostat dial by virtue of an active proximity sensor (PROX, such as provided by a Silicon Labs SI1142 Proximity/Ambient Light Sensor with I2C Interface), will “wake up” the first processor so that it can provide a visual display to the approaching user and be ready to respond more rapidly when their hand touches the dial. As another example, a “wake-on-PIR” facility can be provided by which the second processor will wake up the first processor when detecting motion somewhere in the general vicinity of the thermostat by virtue of a passive infrared motion sensor (PIR, such as provided by a PerkinElmer DigiPyro PYD 1998 dual element pyrodetector). Notably, wake-on-PIR is not synonymous with auto-arrival, as there would need to be N consecutive buckets of sensed PIR activity to invoke auto-arrival, whereas only a single sufficient motion event can trigger a wake-on-PIR wake-up.
Shown in
According to some embodiments for further enhancing the user experience at initial setup, further automation and selectable automation is programmed into the thermostat 100 as follows. For one embodiment, the user is not bothered with being required to select between which particular mode (heating versus cooling) will be used for the O/B orientation test, but rather this decision is made automatically by the thermostat based on one or more extrinsic and/or sensed criteria. In one example, based on the ZIP code and current date which has been received and/or downloaded, the thermostat can make an educated guess as to whether to use heating or cooling as the first O/B orientation test. In another example, the current outside weather (as received from the cloud based on ZIP code, for example) is used in conjunction with the current room temperature to make the determination. In yet another example that has been found particularly useful, just the current room temperature is used to make the decision based on a predetermined threshold temperature such as 70 degrees F., wherein the heating mode is first used during the O/B orientation test if the current temperature is below 70 degrees F., and the cooling mode is first used during the O/B orientation test if the current temperature is above 70 degrees F.
Notably, the fully automated O/B orientation test can take some time to finish, since it can take some time to reliably determine the actual temperature trend in the room. According to one preferred embodiment, at the outset of the automated O/B orientation test, the user is presented with the screen of
In one optional embodiment, since it has been found that most users will indeed intervene to provide the right answer and shorten the test anyway, and since a large majority of systems are indeed of the “O” convention, the thermostat 100 can be programmed to default to the “O” convention in the event there is an indeterminate outcome in the automated test (due to an open window, for example, or thermostat internal electronic heating) when the user has indeed chosen not to intervene. This is because the “O” answer will indeed be correct in most cases, and so the number of actual incorrect determinations will be very small, and even then, it is generally not a determination that will cause damage but rather will be readily perceived by the user in relatively short order, and this very small number of users can call customer support to resolve the issue upon discovery. In other embodiments, an indeterminate outcome can raise a warning flag or other alarm that instructs the user to either manually intervene in the test, or to call customer support. In still other alternative embodiments, the “O” configuration is simply assumed to be the case if the user has not responded to the query of
Provided according to one preferred embodiment is a method for selectively displaying the emotionally encouraging “leaf” described above in the instant application, to encourage the user when they are practicing good energy saving behavior. This algorithm has been found to provide good results in that it can be intuitive, rewarding, and encouraging for different kinds of users based on their individual temperature setting behaviors and schedules, and is not a straight, absolute, one-size-fits-all algorithm. These rules can be applied, without limitation, for walk-up manual dial setpoint changes, when the user is interacting over a remote network thermostat access facility, and when the user is adjusting setpoint entries using a scheduling facility (either walk-up or remote access). When an example is given for heating, it can be assumed that the same rule applies for cooling, except that the direction is opposite and the numerical threshold will be different. One useful set of rules is as follows. A set of judiciously selected predetermined constants for setting forth the rules is first described. Let a heat occupied default setting be H_od=68 F (representing a generally good “occupied” heat setting to be at or below). Let a cool occupied default setting be C_od=76 F (representing a generally good cool “occupied” setting to be at or above). Let a heat away default be H_ad=H_od−6 F=62 F (representing a generally good heat “away” setting to be at or below). Let a cool away default be C_ad=C_od+6 F=82 F (representing a generally good cool “away” setting to be at or above). Let a heat occupied wasting default be H_ow=H_od+6 F=74 F (representing a generally bad heat “occupied” setting to be above). Finally, let a cool occupied wasting be C_ow=C_od−6 F=70 F (representing a generally bad cool “occupied” setting to be below).
When the thermostat is new out of the box (“OOB”) and has just been installed, there is a default single setpoint of H_od=68 F for heating and C_od=76 F for cooling. For the first 7 days of operation, or some other default initial “OOB” period, if the user keeps the setting at or below H_od (heat) or at or above C_od (cool), the leaf will be shown, in order to encourage initial familiarity with the concept and feelings conveyed. Thus, if the user keeps a heat setpoint at 68 F or below in the first 7 days, then the leaf will be displayed. Preferably, as the user changes the setpoint temperature gradually above 68 F (for heating), the leaf will fade out gradually over the first degree F. such that it disappears as 69 F is reached. Similar fadeout/fade-in behavior is preferably exhibited for all of the thresholds described herein.
Subsequent to the 7 day period, a set of steady state leaf display rules can apply. Any time the user changes the current setpoint to a temperature that is 2 degrees F. less “energetic” (i.e., 2 degrees F. cooler if heating or 2 degrees warmer if cooling) than the currently scheduled temperature setpoint, then the leaf will be displayed. Likewise, if the user creates a setpoint using the scheduling facility that is 2 degrees less energetic than the existing, previously effective setpoint in the schedule, the leaf will be displayed. Preferably, certain limits are overlaid onto these rules. First, any time the temperature setpoint is below H_ad=62 F for heat or above C_ad=82 F for cooling, or moved to these ranges, the leaf will always be displayed. Second, any time the temperature the setpoint is above H_ow=74 F for heat or below C_ow=70 F for cooling, the leaf will never be displayed. The second “limit” rule can be omitted in some embodiments.
Provided according to one preferred embodiment is a self-qualification algorithm by which the thermostat 1800 determines whether it can, or cannot, reliably go into an auto-away state to save energy, i.e., whether it has “sensor confidence” for its PIR activity. For one preferred embodiment, the auto-away facility is disabled for a predetermined period such as 7 days after device startup (i.e., initial installation or factory reset). On days 5, 6, and 7 from startup (or other empirically predetermined suitable sample time period), the PIR activity is tracked by discrete sequential “time buckets” of activity, such as 5-minute buckets, where a bucket is either empty (if no occupancy event is sensed in that interval) or full (if one or more occupancy events is sensed in that interval). Out of the total number of buckets for that time period (24×12×3=864 for 5-minute buckets), if there is greater than a predetermined threshold percentage of buckets that are full, then “sensor confidence” is established, and if there is less than that percentage of full buckets, then there is no sensor confidence established. The predetermined threshold can be empirically determined for a particular model, version, or setting of the thermostat. In one example, it has been found that 3.5% is a suitable threshold, i.e., if there are 30 or more full buckets for the three-day sample, then “sensor confidence” is established, although this will vary for different devices models and settings.
Provided according to another preferred embodiment is a method for the automated computation of an optimal threshold value for the active proximity detector (PROX) of the thermostat 1800, by virtue of additional occupancy information provided by its PIR sensor. In order to conserve power and extend the lifetime of the LCD display and the rechargeable battery, as well as for aesthetic advantages in preventing the thermostat from acting as an unwanted nightlight, the PROX detector is integrated into the thermostat 1800 and polled and controlled by the backplate microcontroller (hereinafter “BPμC”) on a consistent basis to detect the close proximity of a user, the LCD display being activated only if there is a walk-up user detected and remaining dark otherwise. Operationally, the PROX is polled by the BPμC at regular intervals, such as every 1/60th of a second, and a PROX signal comprising a DC-removed version of the PROX readings (to obviate the effects of changes in ambient lighting) is generated by the BPμC and compared to a threshold value, termed herein a “PROX threshold”. If the PROX signal is greater than the PROX threshold, the BPμC wakes up the head unit microprocessor (“hereinafter “HUμP”), which then activates the LCD display. It is desirable for the PROX threshold to be judiciously chosen such that (i) the PROX facility is not overly sensitive to noise and background activity, which would lead to over-triggering of the PROX and unnecessary waking of the power-intensive HUμP and LCD display, but that (ii) the PROX is not overly insensitive such that the quality of the user experience in walk-up thermostat use will suffer (because the user needs to make unnatural motion, for example, such as waving their hand, to wake up the unit).
According to one preferred embodiment, the PROX threshold is recomputed at regular intervals (or alternatively at irregular intervals coincident with other HUμP activity) by the HUμP based on a recent history of PROX signal readings, wherein PIR data is included as a basis for selecting the historical time intervals over which the PROX signal history is processed. It has been found that the best PROX thresholds are calculated for sample periods in which the noise in the PROX signal is due to “natural” background noise in the room (such as household lamps), rather than when the PROX signal is cluttered with occupant activity that is occurring in the room which, generally speaking, can cause the determined PROX threshold to be higher than optimal, or otherwise sub-optimal. Thus, according to a preferred embodiment, the HUμP keeps a recent historical record of both PIR activity (which it is collecting anyway for the auto-away facility) as well as PROX signal readings, and then periodically computes a PROX threshold from the recent historical PROX data, wherein any periods of PIR-sensed occupant activity are eliminated from the PROX data sample prior to computation of the PROX threshold. In this way, a more reliable and suitably sensitive, but not overly sensitive, PROX threshold is determined. For one embodiment, the BPμC keeps one sample of the PROX signal data for every 5 minutes, and transfers that data to the HUμP each time the HUμP is woken up. For one embodiment, the HUμP keeps at least 24 hours of the PROX signal data that is received from the BPμC, and recomputes the PROX threshold at regular 24 hour intervals based on the most recent 24 hours of PROX data (together with a corresponding 24 hours of PIR-sensed occupancy data, such as the above-described auto-away “buckets” of activity). For another embodiment, the PROX threshold is recomputed by the HUμP every time it is about to enter into a sleep state. The recomputed PROX threshold is transferred to the BPμC, which then uses that new PROX threshold in determining whether a PROX event has occurred. In other preferred embodiments, the thermostat is further configured to harness the available ALS (ambient light sensor) data to generate an event better PROX threshold, since it is known that ambient light can add to the background PROX signal noise as well as to the DC value of the PROX readings.
Studies have shown that people (segmentations) react very differently to different styles of “nudges” or prompts to change their energy behavior. For one preferred embodiment, there is provided a way on the thermostat 1800 (and on the corresponding web facility) to measure people's responses to different energy prompts. Not only can this provide the right energy saving prompts for an individual over time, but in aggregate, the data can be an enormously useful resource to drive greater efficiency nationwide. By prompt, it is meant that some people are motivated to act by comparing them to their neighbors, some by estimating the money they have lost by not taking certain steps (such as insulation), some by estimating numbers of barrels of oil saved, etc. According to a preferred embodiment, tracking software and algorithms for grouping different prompts are provided in conjunction with the thermostat 1800 (much like web portals use to target advertising or anticipate search results). By understanding what characterizes groups of people who respond to similar prompts, there could be achieved: save more energy for learning thermostat customers, further the marketing potential of the thermostat units, and contribute to some of the biggest questions governments, nonprofits, academics and utilities are dealing with today which is how to change behavior to save energy or otherwise affect the greater good?
The presently described embodiments relate to “closing the loop” on the visual reinforcement algorithms provided by the thermostat by detecting, monitoring, and measuring what the user is doing—if anything—responsive to the operation of the visual reinforcement algorithm. Data can then be collected for a large number of users, and then analyzed to see if the visual reinforcement algorithm is effective. Correlations can be made between particular groupings of users (including but not limited to age, number of people in household, income, location, etc.) and particular visual reinforcement algorithms. Based on correlations that have been found to be successful, the visual reinforcement algorithms can then be changed or “tuned” for each individual household or other applicable customer grouping.
In one example, provided is a thermostatic control system with closed-loop management of user interface features that encourage energy saving behaviors. In a simplest example of the invention, the thermostat can operate according to the following steps: (1) Carry out a first visual reinforcement algorithm, such as the “leaf algorithm”. (2) When the customer earns a reward, display to them the “reward leaf”. (3) For the first minute (or hour, or day) after showing the “reward leaf”, monitor the customer's inputs (if any) and report those inputs to the central Nest server over the internet. (4) Analyze the customer's inputs (either separately or in conjunction with a similar group of customers) to determine if the basic “leaf algorithm” was a “success” for that customer (or that group of customers). (5) If the basic leaf algorithm was not a “success” for that customer or grouping of customers, then automatically download a different visual reinforcement algorithm to that customer's thermostat (or grouping of customer thermostats). By way of a hypothetical example, if the positive-reinforcement “leaf algorithm” was not successful, the replacement visual reinforcement algorithm could be a negative-reinforcement “smokestack” algorithm. (6) Repeat steps (2)-(5) as needed to optimize energy saving behavior according to some optimization criterion.
In one more complex embodiment of the invention, the thermostats can operate according to the following steps: (1) Over a population of different installations, carry out many different visual reinforcement algorithms for many different customers, on a random basis or according to some predetermined distribution scheme; (2) Each time a user is shown a “reward” (or “punishment”) according to their particular visual reinforcement algorithm, monitor the customer's inputs (if any) for the first minute (or hour, or day) after showing the “reward” (or “punishment”), and report those inputs to the central Nest server over the internet;
(3) Analyze the collected data to determine correlations between the success of certain visual reinforcement algorithms and the classifications of customers, geographies, etc. for which they are successful; (4) Automatically download the successful visual reinforcement algorithms for the corresponding customers, geographies, etc. for which they are successful. (5) When commissioning new thermostat installations, automatically program in the particular visual reinforcement algorithms most likely to be successful for that particular customer (e.g., based on the setup interview, purchase data, customer address, and so forth).
For some embodiments, what can be measured is the result of efficiency “infosnacks” shown on the thermostat display, like “You are using 40% more energy than your neighbors” or “Nest has calculated that your home would be X % more efficient with proper insulation” or “By not using the AC one day a week you would save 120$ a month.” What people act on, what people ignore, what people want to get more information about can begin to be discovered. Messages could be sent to each user depending on what they respond to and in aggregate conclusions could be drawn about the kinds of efficiency information folks respond to and why. Studies have shown that when given timely and relevant information about their energy use, consumers can reduce their energy use by 4%-15%. The trouble is, no one quite sure what makes this info relevant and therefore effective. With all the data that can be gotten from users, the thermostat 1800 including its surrounding ecosystem as described hereinabove can help answer that question.
Platform Architecture. According to some embodiments, further description regarding platform architecture for a VSCU unit will now be provided. The VSCU is a powerful, flexible wall-mounted energy management solution. The hardware platform is open and extensible, allowing the system to be used in many applications besides the ones that have been targeted initially.
Overview. The VSCU unit is split into two halves. (1) A head unit: this unit contains the main processor, storage, local area wireless networking, display and user interface. Also included are a range of environmental sensors plus a rechargeable battery and power management subsystems. It is removable by the user and can be connected to a computer for configuration; and (2) a backplate: this unit installs on the wall and interfaces with the HVAC wiring. It provides power to the head unit and also facilitates control of the attached HVAC systems. Optionally, it may also include a cellular wireless interface. This split allows significant flexibility in terms of installation type whilst allowing the most complex part of the system to remain common and be mass-produced.
Head Unit. The VSCU head unit is a powerful self-contained ARM Linux system, providing ample compute resource, local storage, and networking in addition to an elegant user interface. The design has been optimized for low power operation, taking advantage of processor power saving modes and mDDR self-refresh to reduce power consumption to minimal levels when the system isn't actively being used. The main sections of the head unit are as follows.
Processor and Memory. A Texas Instruments AM3703 system-on-chip is used as the CPU. This provides: (1) ARM Cortex A8 core with 32 k I-Cache, 32 k D-Cache and 256 k of L2, running at up to 800 MHz at 1.3 v. The intended operation point for this part is however 300 MHz/1.0 v in order to conserve power; and (2) mDDR interface, connected to a 32 Mb×16 mDDR (64 MBytes). When not actively in use, the processor will be forced into a STANDBY mode (likely Standby 1). This power and clock gates most of the SoC to minimize both leakage and dynamic power consumption whilst retaining DDR contents and being able to wake on any GPIO event or timer tick. In this mode, the SoC and memory are expected to dissipate less than 5 m W of power.
Power Management. The AM3703 is powered by a TI TPS65921 PMU. This part is closely coupled to the CPU and provides power for the CPU, SoC, mDDR and 10. Peripherals that do not run from 1.8V are powered off discrete low dropout voltage regulators (LDOs) as this PMU is not intended to power the rest of the system. The PMU also provides a USB2-HS PHY which connects to the USB-mini-B connector on the back of the head unit, used for PC-based configuration.
Mass Storage. A single 256 MB/512 MB SLC NAND flash chip is used to provide the system's mass storage. SLC flash is used to ensure data integrity—we do not want to suffer from boot failures due to data degradation or read disturb. Most SLC flash retains data for 10 years and up to 100,000 cycles. In order to ensure that pages do not get worn out, MTD/JFFS2 is expected to be used for the partitions that are rewritten frequently—this is not required for area that are just read such as X-Loader, U-Boot, etc. Redundant copies of U-Boot, kernel and root file system are stored on the NAND to provide a fallback should a software update go awry.
Display & User Interface. A memory-mapped RGB color display with 320×320 pixel resolution and LED backlight provides the primary user interface. The backlight brightness can be adjusted with a CPU-driven PWM and can be automatically adjusted based on light sensed by the ambient light sensor. To deal with situations where the head unit is not running (e.g.: head unit hardware failure, battery discharged, etc.), a single tricolor LED connected to the backplate MCU provides a secondary means of informing the user about the device state. A rotary control with push actuation provides user input functionality. If the device is pushed in for 10 seconds, the head unit will reboot; this is a hardcoded feature provided by the TI PMU.
Wireless Communications. The primary communications interface is an 802.11b/g Wi-Fi module based on the TI WL1271 chip, connected via MMC2. Through this interface the VSCU unit can communicate with the server farm and provide secure remote control of the HVAC system in addition to updating temperature and climate models, reporting problems and updating software. In addition to Wi-Fi, a ZigBee transceiver is provided to communicate both with other products (such as auxiliary thermostats, other VSCU head units, baseboard heater controllers) and also with Smart Energy profile devices. The ZigBee interface is capable of running as a coordinator (ZC) if there is sufficient power available. ZigBee uses the TI CC2533 ZigBee transceiver/controller and is connected to UART2.
Configuration Interface. A mini-B USB socket, only visible when the head unit is removed from the backplate, is provided to allow configuration of the device from a PC or Mac. The device will appear to be a USB-MSC device when connected, so no drivers are required on the host side.
Reset. The head unit can be reset by the MCU if required.
Sensors. Most sensors are located in the backplate, and are read over the serial interface; this allows more flexibility with PD to ensure that they are ideally located. However, one sensor is located on the head unit as it needs to be in close proximity to the display—the Ambient Light Sensor/Proximity. A Silicon Labs ALS/proximity sensor senses ambient light (to adjust LCM backlighting) and also near-field proximity to activate the UI when a user approaches the device. The interrupt line of this device is capable of waking the CPU from standby modes.
Backplate Unit. The backplate unit interfaces with the HV AC system, providing control of attached HV AC components and also supplying power to the head unit.
Power supplies. A high voltage LDO provides a 3.1 v bootstrap for the MCU; this can be disabled under MCU control but it is expected that this will be left enabled to provide a “safety net” if the head unit supply vanishes for any reason—such as the head unit being removed unexpectedly. The input to this LDO is provided by diode-OR'ing the heat 1, cool 1 and common wire circuits together. In normal operation, a 3.3 v LDO on the head unit powers the backplate circuitry; because of the high input voltage to this LDO, it cannot supply significant current without a lot of heat dissipation. The second supply in the backplate is the high voltage buck. The input to this supply can be switched to heat 1, cool 1 or the common wire under MCU control—only one input is expected to be selected at a time. The HV buck can supply a maximum of 100 mA at 4.5 v.
The output current of the buck is not limited; however, the input on the head unit is current limited and can be set to one of 3 valid configurations: (1) 20 mAJ4.5 v (90 mW)-low setting for troublesome HVAC systems (FORCE_100 mA low, DOUBLE_CURRENT low); (2) 40 mAJ4.5 v (180 m W)—default setting for power stealing (FORCE 100 mA low, DOUBLE CURRENT high); and (3) 100 mAJ4.5 v (450 mW)—highest setting, forced by backplate to bring a head unit with low battery back to operational state (FORCE_100 mA high, DOUBLE_CURRENT low).
The voltage on the buck's input capacitor can be measured by the MCU, allowing it to momentarily open the WI or YI contacts during an “enabled” phase in order to recharge the buck input cap and continue to power steal. This would only be used in a single circuit system (1 heat OR 1 cool). When used with two circuits (heat and cool), the system would power steal from the non-shorted circuit; with a common wire circuit, the system would not power steal at all.
Switching. The user install backplate provides switching for 1 heat (WI), 1 cool (YI), fan (G), aux heat (AUX) plus heat pump changeover control (O/B). The pro backplate adds secondary heat (W2), secondary cool (Y2), emergency heat (E), plus dry contacts for a humidifier and dehumidifier. The regular HV AC circuits are switched using source-to-source NFETs with transformer isolated gate drive, giving silent switching. The dry contact circuits use bistable relays with two coils (set and reset) to open and close the circuits.
Sensors. Several sensors arc connected to the MCU so that the device can sense the local environment. Temp/Humidity and pressure sensors are connected via the I2C bus and three PIR sensors are also connected on the development board (one analog, two digital). (1) Temperature and humidity: a Sensirion SHT21 sensor provides accurate temperature and humidity sensing whilst taking less than 150 uW of power (150 uW=1 reading per second). (2) Pressure: a Freescale MEMS pressure sensor allows measurement of air pressure whilst taking less than 40 u W of power (˜1 high resolution reading per second). Fast air pressure changes can indicate occupancy (and HVAC activity). (3) Passive Infra-red movement sensors: three PIR sensors are present on the board according to some embodiments: (a) Murata PIR with filter/preamp: this part is fed into an analog input on the MCU, and also to a window comparator to provide a digital output. The analog circuitry effectively provides the filtering required to remove the DC bias and provide a motion sense output to the MCU; and (b) Two Perkin-Elmer digital PIRs: these are connected to the MCU and are bit-banged to read the internal ADCs. This raw value has no DC offset but still requires software filtering to reveal motion activity.
MCU. The backplate MCU processor is a TI MSP 430F5529 CPU, providing: (1) 12 ADC channels for: (a) Voltage measurement/presence detect for common wire and 8 HV AC circuits; (b) Voltage measurement of HV buck input capacitor; and (c) Head unit VBAT measurement; (2) 3 PWM channels for driving the tricolor LED on the head unit (backplate emergency status); (3) 1 PWM channel to provide the ˜5 MHz transformer drive needed to switch HV AC circuits; (4) 8 GPIOs to enable the HVAC switches once the PWM is running; (5) 4 GPIOs to set and reset the two dry contact relays; (6) 3 GPIOs to select the HV buck's input source; (7) 2 GPIOs to enable/disable the LDO and HY buck; (8) 2 I2C buses, one for the temp/humidity sensor and one for the pressure sensor; (9) 1 GPIO connected to the pressure sensors end of conversion output; (10) 3 GPIOs for PIR connection; (11) 1 GPIO to detect head unit presence; (12) 1 GPIO to reset the head unit; (13) 1 GPIO to force the head unit's charger to take 100 MA; (14) One UART for head unit communication; and (15) One UART for debug (e.g. for a development board).
Reset and watchdog. The backplate MCU uses a watchdog to recover from any crashes or instabilities (eg: ESD related events that destabilize the MCU). In addition, the head unit can reset the backplate MCU under software control by driving the RESET_BACKPLATE line high. This signal is RC filtered to prevent false triggers from transient events.
Head unit—backplate interface. The interface between the two parts of the system consists of 20 pins: (1) Power input (2 pins): power is supplied from the backplate to the head unit to nm the system and charge the head unit's local battery, which provides both a buffer for high current peaks (including radio operation) and also battery-backup for continued operation during power failures; (2) Power output (3 pins): power is supplied from the head unit to the backplate to enable high current consumption when required (for example, switching a bistable relay). The VBAT supply is intended only for use by a cellular communication device and for MCU monitoring; (3) Signal ground (2 pins): ground reference for signaling; (4) Low speed communications (2 pins): a UART interface is used for head unit-backplate communications in all configurations. This interface provides identification/authentication, sensor sampling, and control. Typically, this interface runs at 115,200 bps and is connected to a small MCU in the backplate; (5) High speed communications (3 pins): a USB1.1 12 Mbps host interface is also presented by the head unit. This can be used by advanced backplates to enable high performance networking or HV AC control, at a small power penalty above and beyond what is required for the low speed interface. Advanced backplates are not typically power-limited; (6) Detection (2 pins): one grounded at the backplate and one grounded at the head unit, allow each end to detect mating or disconnection and behave appropriately; (7) Head and backplate reset signals (active high: NFET gate drive via RC filter to pull reset lines low); (8) LED cathode connections for RGB LED mounted in head unit; and (9) 5× current limit switch to force fast charging in low battery situations
Boot Scenarios. Some common boot scenarios will now be described, according to some embodiments:
Scenario 1: Out of box experience (battery not empty): (1) User has wired backplate up correctly. MCU LDO has booted MCU; (2) User connects head unit (battery PCM in protection mode); (3) Default 20 mA limit in charger resets PCM protection mode, VBAT recovers to ˜3.7 v; (4) PMUturns on; (5) MCU measures VBAT, releases head unit reset; and (6) Communications established with MCU.
Scenario 2: Out of box experience (battery empty): (1) User has wired backplate up correctly. MCU LDO has booted MCU; (2) User connects head unit (battery PCM in protection mode); (3) Default 20 mA limit in charger resets PCM protection mode, VBAT is <3 Av; (4) PMU samples battery voltage but it is below the EEPROM-stored VMBCH_SEL value of 3 Av so does not power on; (5) MCU measures VBAT, sees low voltage. MCU forces 100 mA charge and turns on indicator LED; (6) When VBAT passes VMBCH_SEL voltage of 3 Av, head unit will power up; (7) Communications established with MCU; and (8) Head unit asks MCU to turn off LED.
Scenario 3: Head unit crashed: (1) Head unit in zombie state, not talking to MCU, battery voltage ok; (2) MCU notes no valid commands within timeout period; (3) MCU turns HV buck off to cut power, then asserts head unit reset; (4) MCU turns HV buck on again, releases reset; and (5) Communications established with MCU.
Scenario 4: Backplate unit crashed: (1) Backplate unit in zombie state, not replying to SoC; (2) SoC resets MCU; and (3) Communications established with MCU.
Scenario 5: Head unit VI lockup: (1) Head unit UI locked up, but lower levels are functioning (MCU comms still active, so MCU will not reset UI); (2) User notices no screen activity, presses and holds button for 10 seconds causing SoC reboot; and (3) Communications established with MCU.
Power Consumption. The system's average power consumption is determined by a few variables: (1) Power in standby mode; (2) Power in active mode; and (3) Power in interactive mode.
Standby Mode. This mode is the one in which the system will reside “most of the time”. The definition of “most of the time” can vary, but it should be able to reside in this state for >95% of the product's life. In this mode, the MCU is running but the head unit is in standby mode. HVAC circuits can be active, and the head unit can be woken into active mode by several events: (1) Proximity sensor or rotary event: The interrupt line from the prox is directly connected to the SoC and so can cause a wake directly. (2) Wi-Fi: The WL IRQ line, connected to the SoC, can wake the head unit when a packet arrives over Wi-Fi (presumably, the chipset would be programmed to only interrupt the SoC on non-broadcast packets when it was in standby); (3) ZigBee: Data from the ZigBee chip can wake the SoC (eg: incoming ZigBee packets); (4) Timer: The system can wake from the RTC timer. This is likely to be used for periodic events such as maintenance of push connections over Wi-Fi and data collection; and (5) Backplate comms: Incoming communications from the backplate will wake the head unit. This could be sensor data or alarm notifications from HV AC monitoring.
The MCU is expected to enter power saving states itself regularly in order to reduce power drain—even if it is waking at 10 Hz to sample the pressure sensor, for example. Because this part of the system is always powered, improvements in efficiency here can make more difference than optimization of rarely used head unit states. The expected ballpark for head unit power consumption in this mode is: 4 mW for CPU/DDR, 2 mW for PMU, 4 mW for Wi-Fi (estimated based on other known chip sets), 2 mW for other items=11 mW. The expected ballpark for backplate power consumption in this mode (with no HVAC loads switched) is ˜5 m W, but will change slightly depending on what frequency sensors are polled.
Active Mode (display off). In active mode, the head unit is powered up, but the display is off. This mode is expected to be in use hundreds of times per day, but for very short periods of time (hopefully <10 seconds each event). Typical reasons the system would transition to active mode include: (1) User activity: active mode would be transitioned through on the way to interactive mode; (2) Sensor data collection: the backplate may have buffered environmental data that needs to be fed to the control algorithm and processed in order to determine whether a response is needed; (3) Push connection: in order to maintain a TCP connection through most NAT routers, data must be transferred periodically. The head unit would use active mode to perform this connection maintenance; and (4) Website-initiated action: here, a user requested action on the servers would result in data being sent over the push connection, causing the Wi-Fi module to wake the SoC to process the data and perform any necessary actions.
Given the relatively high power nature of this mode, care should be taken to ensure that any action is completed and “tided up” before the system is put back into standby mode. For example, if a command if sent to the MCU which generates a response, the response should be gathered before the standby transition is made, otherwise the system may end up bouncing between active and standby mode, wasting power unnecessarily. The same type of problem could also occur with network connections (e.g.: TCP closes). Average power dissipated in this mode could be in the 200 mW range depending on Wi-Fi activity and processor loading.
Interactive Mode (display on): This is the mode in which the user actually interacts with the device. Given that the system is fully active—screen on, backlight on, low latency performance desired—the power footprint is the largest of any of the operational modes. However, because user interactions are likely to be brief and infrequent—especially if the device is performing as intended—their impact on average system power is expected to be very low. It is expected that interactive mode will have a relatively long timeout (maybe as much as 60 seconds) before the unit transitions into active mode and then to standby. It would be worth having the unit stay in active mode for a significant time—maybe 30 seconds or more—on the way down so that if the user starts to interact with the device again, the response is instantaneous. Average power in this mode is likely to be greater than 300 mW depending on Wi-Fi activity, processor loading, and display backlight brightness.
Example Power Consumption Calculation. Table 1 shows how the total system power consumption might be calculated.
As can be seen from Table 1, the dominant power is that of standby, though waking the head unit 8 times per hour (192 times per day) is also not insignificant. Switching each HVAC zone also takes power, estimated at ˜1 mA @ 3.3 v (i.e., 4.5 mW of power at the HV buck output assuming the battery is full). We are likely to be switching multiple circuits concurrently—at least 1H/1C+fan. This can significantly increase our power consumption and hence also needs to be optimized appropriately.
Power Supply. From surveys, it would appear that we are likely to be able to draw 40 mA @ 5 vdc from the HV buck; as this is a switching converter, this 200 mW power should translate directly to 44 mA@ 4.5 vdc in our system. Initially, it was thought that we may only be able to take 100 m W or less from the HV AC circuits, so this is good news. Note that in any system that has both heat and cool (but NOT heat pump), the system can power steal from the non-activated circuit ensuring that we have 200 mW of power available at all times.
Whereas many alterations and modifications of the present invention will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description, it is to be understood that the particular embodiments shown and described by way of illustration are in no way intended to be considered limiting. Therefore, reference to the details of the preferred embodiments are not intended to limit their scope.
This patent application is a continuation of U.S. Ser. No. 13/656,189, filed Oct. 19, 2012, which is a non-provisional patent application claiming priority to U.S. Prov. Ser. No. 61/627,996, filed Oct. 21, 2011. Priority to each of the above-listed applications is claimed. Each of the above-listed applications is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2558648 | Gausmann | Jun 1951 | A |
| 3991357 | Kaminski | Nov 1976 | A |
| 4157506 | Spencer | Jun 1979 | A |
| 4223831 | Szarka | Sep 1980 | A |
| 4308991 | Peinetti et al. | Jan 1982 | A |
| 4316577 | Adams et al. | Feb 1982 | A |
| 4335847 | Levine | Jun 1982 | A |
| 4408711 | Levine | Oct 1983 | A |
| 4460125 | Barker et al. | Jul 1984 | A |
| 4613139 | Robinson, II | Sep 1986 | A |
| 4615380 | Beckey | Oct 1986 | A |
| 4621336 | Brown | Nov 1986 | A |
| 4669654 | Levine et al. | Jun 1987 | A |
| 4674027 | Beckey | Jun 1987 | A |
| 4685614 | Levine | Aug 1987 | A |
| 4695246 | Beilfuss et al. | Sep 1987 | A |
| 4741476 | Russo et al. | May 1988 | A |
| 4751961 | Levine et al. | Jun 1988 | A |
| 4768706 | Parfitt | Sep 1988 | A |
| 4842510 | Grunden et al. | Jun 1989 | A |
| 4847781 | Brown, III et al. | Jul 1989 | A |
| 4872828 | Mierzwinski et al. | Oct 1989 | A |
| 4897798 | Cler | Jan 1990 | A |
| 4948044 | Cacciatore | Aug 1990 | A |
| 4955806 | Grunden et al. | Sep 1990 | A |
| 4971136 | Mathur et al. | Nov 1990 | A |
| 4997029 | Otsuka et al. | Mar 1991 | A |
| 5005365 | Lynch | Apr 1991 | A |
| D321903 | Chepaitis | Nov 1991 | S |
| 5065813 | Berkeley et al. | Nov 1991 | A |
| 5088645 | Bell | Feb 1992 | A |
| 5115967 | Wedekind | May 1992 | A |
| 5127464 | Butler et al. | Jul 1992 | A |
| 5158477 | Testa et al. | Oct 1992 | A |
| 5175439 | Haerer et al. | Dec 1992 | A |
| 5211332 | Adams | May 1993 | A |
| 5224648 | Simon et al. | Jul 1993 | A |
| 5224649 | Brown et al. | Jul 1993 | A |
| 5240178 | Dewolf et al. | Aug 1993 | A |
| 5244146 | Jefferson et al. | Sep 1993 | A |
| 5255179 | Zekan et al. | Oct 1993 | A |
| D341848 | Bigelow et al. | Nov 1993 | S |
| 5294047 | Schwer et al. | Mar 1994 | A |
| 5303612 | Odom et al. | Apr 1994 | A |
| 5347982 | Binzer et al. | Sep 1994 | A |
| 5352930 | Ratz | Oct 1994 | A |
| 5395042 | Riley et al. | Mar 1995 | A |
| 5415346 | Bishop | May 1995 | A |
| 5422808 | Catanese, Jr. et al. | Jun 1995 | A |
| 5460327 | Hill et al. | Oct 1995 | A |
| 5462225 | Massara et al. | Oct 1995 | A |
| 5476221 | Seymour | Dec 1995 | A |
| 5482209 | Cochran et al. | Jan 1996 | A |
| 5485954 | Guy et al. | Jan 1996 | A |
| 5499196 | Pacheco | Mar 1996 | A |
| 5506569 | Rowlette | Apr 1996 | A |
| 5544036 | Brown, Jr. et al. | Aug 1996 | A |
| 5555927 | Shah | Sep 1996 | A |
| 5570837 | Brown et al. | Nov 1996 | A |
| 5603451 | Helander et al. | Feb 1997 | A |
| 5611484 | Uhrich | Mar 1997 | A |
| 5627531 | Posso et al. | May 1997 | A |
| 5673850 | Uptegraph | Oct 1997 | A |
| 5686896 | Bergman | Nov 1997 | A |
| 5690277 | Flood | Nov 1997 | A |
| 5697552 | McHugh et al. | Dec 1997 | A |
| 5736795 | Zuehlke et al. | Apr 1998 | A |
| 5761083 | Brown, Jr. et al. | Jun 1998 | A |
| D396488 | Kunkler | Jul 1998 | S |
| 5779143 | Michaud et al. | Jul 1998 | A |
| 5782296 | Mehta | Jul 1998 | A |
| 5808294 | Neumann | Sep 1998 | A |
| 5808602 | Sellers | Sep 1998 | A |
| 5816491 | Berkeley et al. | Oct 1998 | A |
| 5902183 | D'Souza | May 1999 | A |
| 5903139 | Kompelien | May 1999 | A |
| 5909378 | De milleville | Jun 1999 | A |
| 5918474 | Khanpara et al. | Jul 1999 | A |
| 5924486 | Ehlers et al. | Jul 1999 | A |
| 5931378 | Schramm | Aug 1999 | A |
| 5959621 | Nawaz et al. | Sep 1999 | A |
| 5973662 | Singers et al. | Oct 1999 | A |
| 5977964 | Williams et al. | Nov 1999 | A |
| 6020881 | Naughton et al. | Feb 2000 | A |
| 6032867 | Dushane et al. | Mar 2000 | A |
| 6060719 | DiTucci et al. | May 2000 | A |
| 6062482 | Gauthier et al. | May 2000 | A |
| 6066843 | Schererneta | May 2000 | A |
| 6072784 | Agrawal et al. | Jun 2000 | A |
| D428399 | Kahn et al. | Jul 2000 | S |
| 6084518 | Jamieson | Jul 2000 | A |
| 6093914 | Diekmann et al. | Jul 2000 | A |
| 6095427 | Hoium et al. | Aug 2000 | A |
| 6098893 | Berglund et al. | Aug 2000 | A |
| 6122603 | Budike, Jr. | Sep 2000 | A |
| 6164374 | Rhodes et al. | Dec 2000 | A |
| 6166633 | Wang | Dec 2000 | A |
| 6206295 | LaCoste | Mar 2001 | B1 |
| 6211921 | Cherian et al. | Apr 2001 | B1 |
| 6213404 | Dushane et al. | Apr 2001 | B1 |
| 6216956 | Ehlers et al. | Apr 2001 | B1 |
| 6222719 | Kadah | Apr 2001 | B1 |
| 6275160 | Ha | Aug 2001 | B1 |
| 6286764 | Garvey et al. | Sep 2001 | B1 |
| 6298285 | Addink et al. | Oct 2001 | B1 |
| 6311105 | Budike, Jr. | Oct 2001 | B1 |
| D450059 | Itou | Nov 2001 | S |
| 6318639 | Toth | Nov 2001 | B1 |
| 6349883 | Simmons et al. | Feb 2002 | B1 |
| 6351693 | Monie et al. | Feb 2002 | B1 |
| 6356038 | Bishel | Mar 2002 | B2 |
| 6356204 | Guindi et al. | Mar 2002 | B1 |
| 6370894 | Thompson et al. | Apr 2002 | B1 |
| 6415205 | Myron et al. | Jul 2002 | B1 |
| 6438241 | Silfvast et al. | Aug 2002 | B1 |
| 6453687 | Sharood et al. | Sep 2002 | B2 |
| D464660 | Weng et al. | Oct 2002 | S |
| 6478233 | Shah | Nov 2002 | B1 |
| 6502758 | Cottrell | Jan 2003 | B2 |
| 6509838 | Payne et al. | Jan 2003 | B1 |
| 6513723 | Mueller et al. | Feb 2003 | B1 |
| 6519509 | Nierlich et al. | Feb 2003 | B1 |
| D471825 | Peabody | Mar 2003 | S |
| 6566768 | Zimmerman et al. | May 2003 | B2 |
| 6574581 | Bohrer et al. | Jun 2003 | B1 |
| 6595430 | Shah | Jul 2003 | B1 |
| 6619055 | Addy | Sep 2003 | B1 |
| 6622925 | Carner et al. | Sep 2003 | B2 |
| D480401 | Kahn et al. | Oct 2003 | S |
| 6636197 | Goldenberg et al. | Oct 2003 | B1 |
| 6641054 | Morey | Nov 2003 | B2 |
| 6641055 | Tiernan | Nov 2003 | B1 |
| 6643567 | Kolk et al. | Nov 2003 | B2 |
| 6644557 | Jacobs | Nov 2003 | B1 |
| 6645066 | Gutta et al. | Nov 2003 | B2 |
| 6657418 | Atherton | Dec 2003 | B2 |
| D485279 | DeCombe | Jan 2004 | S |
| 6726112 | Ho | Apr 2004 | B1 |
| D491956 | Ombao et al. | Jun 2004 | S |
| 6743010 | Bridgeman et al. | Jun 2004 | B2 |
| 6769482 | Wagner et al. | Aug 2004 | B2 |
| 6785630 | Kolk et al. | Aug 2004 | B2 |
| 6794771 | Orloff | Sep 2004 | B2 |
| 6798341 | Eckel et al. | Sep 2004 | B1 |
| D497617 | Decombe et al. | Oct 2004 | S |
| 6814299 | Carey | Nov 2004 | B1 |
| 6824069 | Rosen | Nov 2004 | B2 |
| 6851621 | Wacker et al. | Feb 2005 | B1 |
| D503631 | Peabody | Apr 2005 | S |
| 6886754 | Smith et al. | May 2005 | B2 |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6909921 | Bilger | Jun 2005 | B1 |
| 6951306 | DeLuca | Oct 2005 | B2 |
| D511527 | Hernandez et al. | Nov 2005 | S |
| 6975958 | Bohrer et al. | Dec 2005 | B2 |
| 6990821 | Singh et al. | Jan 2006 | B2 |
| 7000849 | Ashworth et al. | Feb 2006 | B2 |
| 7024336 | Salsbury et al. | Apr 2006 | B2 |
| 7028912 | Rosen | Apr 2006 | B1 |
| 7035805 | Miller | Apr 2006 | B1 |
| 7038667 | Vassallo et al. | May 2006 | B1 |
| 7055759 | Wacker et al. | Jun 2006 | B2 |
| 7083109 | Pouchak | Aug 2006 | B2 |
| 7108194 | Hankins, II | Sep 2006 | B1 |
| 7109970 | Miller | Sep 2006 | B1 |
| 7111788 | Reponen | Sep 2006 | B2 |
| 7114554 | Bergman et al. | Oct 2006 | B2 |
| 7135965 | Chapman, Jr. et al. | Nov 2006 | B2 |
| 7140551 | De Pauw et al. | Nov 2006 | B2 |
| 7141748 | Tanaka et al. | Nov 2006 | B2 |
| 7142948 | Metz | Nov 2006 | B2 |
| 7149729 | Kaasten et al. | Dec 2006 | B2 |
| 7152806 | Rosen | Dec 2006 | B1 |
| 7156318 | Rosen | Jan 2007 | B1 |
| 7159789 | Schwendinger et al. | Jan 2007 | B2 |
| 7159790 | Schwendinger et al. | Jan 2007 | B2 |
| 7181317 | Amundson et al. | Feb 2007 | B2 |
| 7188482 | Sadegh et al. | Mar 2007 | B2 |
| 7200467 | Schanin et al. | Apr 2007 | B2 |
| 7222494 | Peterson et al. | May 2007 | B2 |
| 7222800 | Wruck | May 2007 | B2 |
| 7225054 | Amundson et al. | May 2007 | B2 |
| 7225057 | Froman et al. | May 2007 | B2 |
| D544877 | Sasser | Jun 2007 | S |
| 7258280 | Wolfson | Aug 2007 | B2 |
| D550691 | Hally et al. | Sep 2007 | S |
| 7264175 | Schwendinger et al. | Sep 2007 | B2 |
| 7274972 | Amundson et al. | Sep 2007 | B2 |
| 7287709 | Proffitt et al. | Oct 2007 | B2 |
| 7289887 | Rodgers | Oct 2007 | B2 |
| 7299996 | Garrett et al. | Nov 2007 | B2 |
| 7302642 | Smith et al. | Nov 2007 | B2 |
| 7333880 | Brewster et al. | Feb 2008 | B2 |
| 7346467 | Bohrer et al. | Mar 2008 | B2 |
| D566587 | Rosen | Apr 2008 | S |
| 7379791 | Tamarkin et al. | May 2008 | B2 |
| RE40437 | Rosen | Jul 2008 | E |
| 7418663 | Pettinati et al. | Aug 2008 | B2 |
| 7427926 | Sinclair et al. | Sep 2008 | B2 |
| 7434742 | Mueller et al. | Oct 2008 | B2 |
| 7451937 | Flood et al. | Nov 2008 | B2 |
| 7455240 | Chapman, Jr. et al. | Nov 2008 | B2 |
| 7460690 | Cohen et al. | Dec 2008 | B2 |
| 7469550 | Chapman, Jr. et al. | Dec 2008 | B2 |
| 7476988 | Mulhouse et al. | Jan 2009 | B2 |
| D588152 | Okada | Mar 2009 | S |
| 7509753 | Nicosia et al. | Mar 2009 | B2 |
| 7510126 | Rossi et al. | Mar 2009 | B2 |
| D589792 | Clabough et al. | Apr 2009 | S |
| D590412 | Saft et al. | Apr 2009 | S |
| D593120 | Bouchard et al. | May 2009 | S |
| 7537171 | Mueller et al. | May 2009 | B2 |
| D594015 | Singh et al. | Jun 2009 | S |
| D595309 | Sasaki et al. | Jun 2009 | S |
| 7555364 | Poth et al. | Jun 2009 | B2 |
| D596194 | Vu et al. | Jul 2009 | S |
| D597101 | Chaudhri et al. | Jul 2009 | S |
| 7558648 | Hoglund et al. | Jul 2009 | B2 |
| D598463 | Hirsch et al. | Aug 2009 | S |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7571865 | Nicodem et al. | Aug 2009 | B2 |
| 7575179 | Morrow et al. | Aug 2009 | B2 |
| D599810 | Scalisi et al. | Sep 2009 | S |
| 7584899 | De Pauw et al. | Sep 2009 | B2 |
| 7600694 | Helt et al. | Oct 2009 | B2 |
| D603277 | Clausen et al. | Nov 2009 | S |
| D603421 | Ebeling et al. | Nov 2009 | S |
| D604740 | Natheny et al. | Nov 2009 | S |
| 7614567 | Chapman et al. | Nov 2009 | B2 |
| 7620996 | Torres et al. | Nov 2009 | B2 |
| D607001 | Ording | Dec 2009 | S |
| 7624931 | Chapman, Jr. et al. | Dec 2009 | B2 |
| 7634504 | Amundson | Dec 2009 | B2 |
| 7641126 | Schultz et al. | Jan 2010 | B2 |
| 7644869 | Hoglund et al. | Jan 2010 | B2 |
| 7667163 | Ashworth et al. | Feb 2010 | B2 |
| D613301 | Lee et al. | Apr 2010 | S |
| D614194 | Guntaur et al. | Apr 2010 | S |
| D614196 | Guntaur et al. | Apr 2010 | S |
| 7693582 | Bergman et al. | Apr 2010 | B2 |
| 7702424 | Cannon et al. | Apr 2010 | B2 |
| 7703694 | Mueller et al. | Apr 2010 | B2 |
| D614976 | Skafdrup et al. | May 2010 | S |
| D615546 | Lundy et al. | May 2010 | S |
| D616460 | Pearson et al. | May 2010 | S |
| 7721209 | Tilton | May 2010 | B2 |
| 7726581 | Naujok et al. | Jun 2010 | B2 |
| D619613 | Dunn | Jul 2010 | S |
| 7755220 | Sorg et al. | Jul 2010 | B2 |
| 7761189 | Froman et al. | Jul 2010 | B2 |
| 7784704 | Harter | Aug 2010 | B2 |
| 7802618 | Simon et al. | Sep 2010 | B2 |
| D625325 | Vu et al. | Oct 2010 | S |
| D625734 | Kurozumi et al. | Oct 2010 | S |
| D626133 | Murphy et al. | Oct 2010 | S |
| 7823076 | Borovsky et al. | Oct 2010 | B2 |
| RE41922 | Gough et al. | Nov 2010 | E |
| 7845576 | Siddaramanna et al. | Dec 2010 | B2 |
| 7848900 | Steinberg et al. | Dec 2010 | B2 |
| 7854389 | Ahmed | Dec 2010 | B2 |
| 7861179 | Reed | Dec 2010 | B2 |
| D630649 | Tokunaga et al. | Jan 2011 | S |
| 7890195 | Bergman et al. | Feb 2011 | B2 |
| 7900849 | Barton et al. | Mar 2011 | B2 |
| 7904209 | Podgomy et al. | Mar 2011 | B2 |
| 7904830 | Hoglund et al. | Mar 2011 | B2 |
| 7908116 | Steinberg et al. | Mar 2011 | B2 |
| 7908117 | Steinberg et al. | Mar 2011 | B2 |
| 7913925 | Ashworth | Mar 2011 | B2 |
| D638835 | Akana et al. | May 2011 | S |
| D640269 | Chen | Jun 2011 | S |
| D640273 | Arnold et al. | Jun 2011 | S |
| D640278 | Woo | Jun 2011 | S |
| D640285 | Woo | Jun 2011 | S |
| D641373 | Gardner et al. | Jul 2011 | S |
| 7984384 | Chaudhri et al. | Jul 2011 | B2 |
| D643045 | Woo | Aug 2011 | S |
| 8010237 | Cheung et al. | Aug 2011 | B2 |
| 8019567 | Steinberg et al. | Sep 2011 | B2 |
| 8037022 | Rahman et al. | Oct 2011 | B2 |
| D648735 | Arnold et al. | Nov 2011 | S |
| D651529 | Mongell et al. | Jan 2012 | S |
| 8090477 | Steinberg | Jan 2012 | B1 |
| 8091375 | Crawford | Jan 2012 | B2 |
| 8091794 | Siddaramanna et al. | Jan 2012 | B2 |
| 8131207 | Hwang et al. | Mar 2012 | B2 |
| 8131497 | Steinberg et al. | Mar 2012 | B2 |
| 8131506 | Steinberg et al. | Mar 2012 | B2 |
| 8136052 | Shin et al. | Mar 2012 | B2 |
| D656950 | Shallcross et al. | Apr 2012 | S |
| D656952 | Weir et al. | Apr 2012 | S |
| 8156060 | Borzestowski et al. | Apr 2012 | B2 |
| 8166395 | Omi et al. | Apr 2012 | B2 |
| D658674 | Shallcross et al. | May 2012 | S |
| D660732 | Bould et al. | May 2012 | S |
| 8174381 | Imes et al. | May 2012 | B2 |
| 8180492 | Steinberg | May 2012 | B2 |
| 8185164 | Kim | May 2012 | B2 |
| 8195313 | Fadell et al. | Jun 2012 | B1 |
| D663743 | Tanghe et al. | Jul 2012 | S |
| D663744 | Tanghe et al. | Jul 2012 | S |
| D664559 | Ismall et al. | Jul 2012 | S |
| 8219249 | Harrod et al. | Jul 2012 | B2 |
| 8223134 | Forstall et al. | Jul 2012 | B1 |
| 8234581 | Kake | Jul 2012 | B2 |
| D664978 | Tanghe et al. | Aug 2012 | S |
| D665397 | Naranjo et al. | Aug 2012 | S |
| 8243017 | Brodersen et al. | Aug 2012 | B2 |
| 8253704 | Jang | Aug 2012 | B2 |
| 8253747 | Niles et al. | Aug 2012 | B2 |
| 8265798 | Imes | Sep 2012 | B2 |
| 8280536 | Fadell et al. | Oct 2012 | B1 |
| 8281244 | Neuman et al. | Oct 2012 | B2 |
| 8292494 | Rosa et al. | Oct 2012 | B2 |
| D671136 | Barnett et al. | Nov 2012 | S |
| 8316022 | Matsuda et al. | Nov 2012 | B2 |
| D673171 | Peters et al. | Dec 2012 | S |
| D673172 | Peters et al. | Dec 2012 | S |
| 8341557 | Pisula et al. | Dec 2012 | B2 |
| D677180 | Plitkins et al. | Mar 2013 | S |
| 8406816 | Marul et al. | Mar 2013 | B2 |
| 8415829 | Di Cristofaro | Apr 2013 | B2 |
| 8442693 | Mirza et al. | May 2013 | B2 |
| 8442695 | Imes et al. | May 2013 | B2 |
| 8442752 | Wijaya et al. | May 2013 | B2 |
| 8446381 | Molard et al. | May 2013 | B2 |
| 8489243 | Fadell et al. | Jul 2013 | B2 |
| 8689572 | Evans et al. | Apr 2014 | B2 |
| 8706270 | Fadell et al. | Apr 2014 | B2 |
| 20020022991 | Sharood et al. | Feb 2002 | A1 |
| 20020074865 | Zimmerman et al. | Jun 2002 | A1 |
| 20030034898 | Shamoon et al. | Feb 2003 | A1 |
| 20030037555 | Street et al. | Feb 2003 | A1 |
| 20030042320 | Decker | Mar 2003 | A1 |
| 20030064335 | Canon | Apr 2003 | A1 |
| 20030090243 | Atherton | May 2003 | A1 |
| 20030112262 | Adatia et al. | Jun 2003 | A1 |
| 20030231001 | Bruning | Dec 2003 | A1 |
| 20040015504 | Ahad et al. | Jan 2004 | A1 |
| 20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
| 20040055446 | Robbin et al. | Mar 2004 | A1 |
| 20040067731 | Brinkerhoff et al. | Apr 2004 | A1 |
| 20040074978 | Rosen | Apr 2004 | A1 |
| 20040095237 | Chen et al. | May 2004 | A1 |
| 20040120084 | Readio et al. | Jun 2004 | A1 |
| 20040164238 | Xu et al. | Aug 2004 | A1 |
| 20040209209 | Chodacki et al. | Oct 2004 | A1 |
| 20040245349 | Smith | Dec 2004 | A1 |
| 20040249479 | Shorrock | Dec 2004 | A1 |
| 20040256472 | DeLuca | Dec 2004 | A1 |
| 20040260427 | Wimsatt | Dec 2004 | A1 |
| 20040262410 | Hull | Dec 2004 | A1 |
| 20050040250 | Wruck | Feb 2005 | A1 |
| 20050043907 | Eckel et al. | Feb 2005 | A1 |
| 20050055432 | Rodgers | Mar 2005 | A1 |
| 20050071780 | Muller et al. | Mar 2005 | A1 |
| 20050090915 | Geiwitz | Apr 2005 | A1 |
| 20050103875 | Ashworth et al. | May 2005 | A1 |
| 20050119766 | Amundson et al. | Jun 2005 | A1 |
| 20050119793 | Amundson et al. | Jun 2005 | A1 |
| 20050120181 | Arunagirinathan et al. | Jun 2005 | A1 |
| 20050128067 | Zakrewski | Jun 2005 | A1 |
| 20050150968 | Shearer | Jul 2005 | A1 |
| 20050159847 | Shah et al. | Jul 2005 | A1 |
| 20050189429 | Breeden | Sep 2005 | A1 |
| 20050192915 | Ahmed et al. | Sep 2005 | A1 |
| 20050194456 | Tessier et al. | Sep 2005 | A1 |
| 20050195757 | Kidder et al. | Sep 2005 | A1 |
| 20050204997 | Fournier | Sep 2005 | A1 |
| 20050279840 | Schwendinger et al. | Dec 2005 | A1 |
| 20050279841 | Schwendinger et al. | Dec 2005 | A1 |
| 20050280421 | Yomoda et al. | Dec 2005 | A1 |
| 20050287424 | Schwendinger et al. | Dec 2005 | A1 |
| 20060000919 | Schwendinger et al. | Jan 2006 | A1 |
| 20060092012 | Kaiser et al. | May 2006 | A1 |
| 20060102731 | Mueller et al. | May 2006 | A1 |
| 20060124759 | Rossi et al. | Jun 2006 | A1 |
| 20060184284 | Froman et al. | Aug 2006 | A1 |
| 20060186214 | Simon et al. | Aug 2006 | A1 |
| 20060196953 | Simon et al. | Sep 2006 | A1 |
| 20060206220 | Amundson | Sep 2006 | A1 |
| 20070001830 | Dagci et al. | Jan 2007 | A1 |
| 20070045430 | Chapman et al. | Mar 2007 | A1 |
| 20070045433 | Chapman et al. | Mar 2007 | A1 |
| 20070045444 | Gray et al. | Mar 2007 | A1 |
| 20070050732 | Chapman et al. | Mar 2007 | A1 |
| 20070057079 | Stark et al. | Mar 2007 | A1 |
| 20070084941 | de Pauw et al. | Apr 2007 | A1 |
| 20070114295 | Jenkins | May 2007 | A1 |
| 20070114848 | Mulhouse et al. | May 2007 | A1 |
| 20070115902 | Shamoon et al. | May 2007 | A1 |
| 20070132503 | Nordin | Jun 2007 | A1 |
| 20070157639 | Harrod | Jul 2007 | A1 |
| 20070158442 | Chapman et al. | Jul 2007 | A1 |
| 20070158444 | Naujok et al. | Jul 2007 | A1 |
| 20070173978 | Fein et al. | Jul 2007 | A1 |
| 20070177857 | Troost et al. | Aug 2007 | A1 |
| 20070220907 | Ehlers | Sep 2007 | A1 |
| 20070221741 | Wagner et al. | Sep 2007 | A1 |
| 20070225867 | Moorer et al. | Sep 2007 | A1 |
| 20070227721 | Springer et al. | Oct 2007 | A1 |
| 20070228183 | Kennedy et al. | Oct 2007 | A1 |
| 20070241203 | Wagner et al. | Oct 2007 | A1 |
| 20070246553 | Morrow et al. | Oct 2007 | A1 |
| 20070257120 | Chapman et al. | Nov 2007 | A1 |
| 20070278320 | Lunacek et al. | Dec 2007 | A1 |
| 20070296280 | Sorg et al. | Dec 2007 | A1 |
| 20080006709 | Ashworth et al. | Jan 2008 | A1 |
| 20080015740 | Osann | Jan 2008 | A1 |
| 20080015742 | Kulyk et al. | Jan 2008 | A1 |
| 20080048046 | Wagner et al. | Feb 2008 | A1 |
| 20080054082 | Evans et al. | Mar 2008 | A1 |
| 20080054084 | Olson | Mar 2008 | A1 |
| 20080094010 | Black | Apr 2008 | A1 |
| 20080099568 | Nicodem et al. | May 2008 | A1 |
| 20080117067 | Abel et al. | May 2008 | A1 |
| 20080133956 | Fadell | Jun 2008 | A1 |
| 20080147242 | Roher et al. | Jun 2008 | A1 |
| 20080155915 | Howe et al. | Jul 2008 | A1 |
| 20080191045 | Harter | Aug 2008 | A1 |
| 20080215240 | Howard et al. | Sep 2008 | A1 |
| 20080221737 | Josephson et al. | Sep 2008 | A1 |
| 20080245480 | Knight et al. | Oct 2008 | A1 |
| 20080256475 | Amundson et al. | Oct 2008 | A1 |
| 20080273754 | Hick et al. | Nov 2008 | A1 |
| 20080290183 | Laberge et al. | Nov 2008 | A1 |
| 20080317292 | Baker et al. | Dec 2008 | A1 |
| 20090001180 | Siddaramanna et al. | Jan 2009 | A1 |
| 20090001181 | Siddaramanna et al. | Jan 2009 | A1 |
| 20090024927 | Schrock et al. | Jan 2009 | A1 |
| 20090099699 | Steinberg et al. | Apr 2009 | A1 |
| 20090125151 | Steinberg et al. | May 2009 | A1 |
| 20090140056 | Leen | Jun 2009 | A1 |
| 20090140057 | Leen | Jun 2009 | A1 |
| 20090140060 | Stoner et al. | Jun 2009 | A1 |
| 20090140064 | Schultz et al. | Jun 2009 | A1 |
| 20090143916 | Boll et al. | Jun 2009 | A1 |
| 20090143918 | Amundson et al. | Jun 2009 | A1 |
| 20090158188 | Bray et al. | Jun 2009 | A1 |
| 20090171862 | Harrod et al. | Jul 2009 | A1 |
| 20090194601 | Flohr | Aug 2009 | A1 |
| 20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
| 20090215534 | Wilson et al. | Aug 2009 | A1 |
| 20090259713 | Blumrich et al. | Oct 2009 | A1 |
| 20090261174 | Butler et al. | Oct 2009 | A1 |
| 20090263773 | Kotlyar et al. | Oct 2009 | A1 |
| 20090273610 | Busch et al. | Nov 2009 | A1 |
| 20090283603 | Peterson et al. | Nov 2009 | A1 |
| 20090297901 | Kilian et al. | Dec 2009 | A1 |
| 20090327354 | Resnick et al. | Dec 2009 | A1 |
| 20100000417 | Tetreault et al. | Jan 2010 | A1 |
| 20100019051 | Rosen | Jan 2010 | A1 |
| 20100025483 | Hoeynck et al. | Feb 2010 | A1 |
| 20100050004 | Hamilton, II et al. | Feb 2010 | A1 |
| 20100070084 | Steinberg et al. | Mar 2010 | A1 |
| 20100070085 | Harrod et al. | Mar 2010 | A1 |
| 20100070086 | Harrod et al. | Mar 2010 | A1 |
| 20100070089 | Harrod et al. | Mar 2010 | A1 |
| 20100070093 | Harrod et al. | Mar 2010 | A1 |
| 20100070234 | Steinberg et al. | Mar 2010 | A1 |
| 20100070907 | Harrod et al. | Mar 2010 | A1 |
| 20100076605 | Harrod et al. | Mar 2010 | A1 |
| 20100076835 | Silverman | Mar 2010 | A1 |
| 20100084482 | Kennedy et al. | Apr 2010 | A1 |
| 20100084918 | Fells et al. | Apr 2010 | A1 |
| 20100106305 | Pavlak et al. | Apr 2010 | A1 |
| 20100106322 | Grohman | Apr 2010 | A1 |
| 20100107070 | Devineni et al. | Apr 2010 | A1 |
| 20100107076 | Grohman et al. | Apr 2010 | A1 |
| 20100107103 | Wallaert et al. | Apr 2010 | A1 |
| 20100163633 | Barrett et al. | Jul 2010 | A1 |
| 20100167783 | Alameh et al. | Jul 2010 | A1 |
| 20100168924 | Tessier et al. | Jul 2010 | A1 |
| 20100179704 | Ozog | Jul 2010 | A1 |
| 20100198425 | Donovan | Aug 2010 | A1 |
| 20100211224 | Keeling et al. | Aug 2010 | A1 |
| 20100262298 | Johnson et al. | Oct 2010 | A1 |
| 20100262299 | Cheung et al. | Oct 2010 | A1 |
| 20100273610 | Johnson | Oct 2010 | A1 |
| 20100280667 | Steinberg | Nov 2010 | A1 |
| 20100282857 | Steinberg | Nov 2010 | A1 |
| 20100289643 | Trundle et al. | Nov 2010 | A1 |
| 20100308119 | Steinberg et al. | Dec 2010 | A1 |
| 20100318227 | Steinberg et al. | Dec 2010 | A1 |
| 20110001812 | Kang et al. | Jan 2011 | A1 |
| 20110015797 | Gilstrap | Jan 2011 | A1 |
| 20110015798 | Golden et al. | Jan 2011 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110016017 | Carlin et al. | Jan 2011 | A1 |
| 20110022242 | Bukhin et al. | Jan 2011 | A1 |
| 20110025257 | Weng | Feb 2011 | A1 |
| 20110029488 | Fuerst et al. | Feb 2011 | A1 |
| 20110046756 | Park | Feb 2011 | A1 |
| 20110046792 | Imes et al. | Feb 2011 | A1 |
| 20110046805 | Bedros et al. | Feb 2011 | A1 |
| 20110046806 | Nagel et al. | Feb 2011 | A1 |
| 20110054710 | Imes et al. | Mar 2011 | A1 |
| 20110057806 | Gonzales | Mar 2011 | A1 |
| 20110077758 | Tran et al. | Mar 2011 | A1 |
| 20110077896 | Steinberg et al. | Mar 2011 | A1 |
| 20110082594 | Dage et al. | Apr 2011 | A1 |
| 20110106328 | Zhou et al. | May 2011 | A1 |
| 20110151837 | Winbush, III | Jun 2011 | A1 |
| 20110152024 | Kuehl | Jun 2011 | A1 |
| 20110160913 | Parker et al. | Jun 2011 | A1 |
| 20110166828 | Steinberg et al. | Jul 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110185895 | Freen | Aug 2011 | A1 |
| 20110282937 | Deshpande et al. | Nov 2011 | A1 |
| 20110290893 | Steinberg | Dec 2011 | A1 |
| 20110307103 | Cheung et al. | Dec 2011 | A1 |
| 20110307112 | Barrilleaux | Dec 2011 | A1 |
| 20120017611 | Coffel et al. | Jan 2012 | A1 |
| 20120026726 | Recker et al. | Feb 2012 | A1 |
| 20120036250 | Vaswani et al. | Feb 2012 | A1 |
| 20120053745 | Ng | Mar 2012 | A1 |
| 20120065783 | Fadell et al. | Mar 2012 | A1 |
| 20120065935 | Steinberg et al. | Mar 2012 | A1 |
| 20120066168 | Fadell et al. | Mar 2012 | A1 |
| 20120085831 | Kopp | Apr 2012 | A1 |
| 20120086562 | Steinberg | Apr 2012 | A1 |
| 20120089523 | Hurri et al. | Apr 2012 | A1 |
| 20120101637 | Imes et al. | Apr 2012 | A1 |
| 20120125559 | Fadell et al. | May 2012 | A1 |
| 20120125592 | Fadell et al. | May 2012 | A1 |
| 20120126019 | Warren et al. | May 2012 | A1 |
| 20120126020 | Filson et al. | May 2012 | A1 |
| 20120126021 | Warren et al. | May 2012 | A1 |
| 20120128025 | Huppi et al. | May 2012 | A1 |
| 20120130546 | Matas et al. | May 2012 | A1 |
| 20120130547 | Fadell et al. | May 2012 | A1 |
| 20120130548 | Fadell et al. | May 2012 | A1 |
| 20120130679 | Fadell et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120158350 | Steinberg et al. | Jun 2012 | A1 |
| 20120179300 | Warren et al. | Jul 2012 | A1 |
| 20120186774 | Matsuoka et al. | Jul 2012 | A1 |
| 20120191257 | Corcoran et al. | Jul 2012 | A1 |
| 20120199660 | Warren et al. | Aug 2012 | A1 |
| 20120203379 | Sloo et al. | Aug 2012 | A1 |
| 20120221151 | Steinberg | Aug 2012 | A1 |
| 20120229521 | Hales, IV et al. | Sep 2012 | A1 |
| 20120233478 | Mucignat et al. | Sep 2012 | A1 |
| 20120239207 | Fadell et al. | Sep 2012 | A1 |
| 20120239221 | Mighdoll et al. | Sep 2012 | A1 |
| 20120252430 | Imes et al. | Oct 2012 | A1 |
| 20120296488 | Dharwada et al. | Nov 2012 | A1 |
| 20130014057 | Reinpoldt et al. | Jan 2013 | A1 |
| 20130024799 | Fadell et al. | Jan 2013 | A1 |
| 20130046397 | Fadell et al. | Feb 2013 | A1 |
| 20130090767 | Bruck et al. | Apr 2013 | A1 |
| 20130099011 | Matsuoka et al. | Apr 2013 | A1 |
| 20140005837 | Fadell et al. | Jan 2014 | A1 |
| 20140358293 | Fadell et al. | Dec 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 0207295 | Jan 1987 | EP |
| 434926 | Jul 1991 | EP |
| 196069 | Dec 1991 | EP |
| 720077 | Jul 1996 | EP |
| 802471 | Oct 1997 | EP |
| 1065079 | Jan 2001 | EP |
| 1184804 | Mar 2002 | EP |
| 1731984 | Dec 2006 | EP |
| 1283396 | Mar 2007 | EP |
| 2157492 | Feb 2010 | EP |
| 1703356 | Sep 2011 | EP |
| 2769275 | Aug 2014 | EP |
| 2212317 | May 1992 | GB |
| 2294828 | May 1996 | GB |
| 59106311 | Jun 1984 | JP |
| 01252850 | Oct 1989 | JP |
| 09298780 | Nov 1997 | JP |
| 10023565 | Jan 1998 | JP |
| 2002087050 | Mar 2002 | JP |
| 2003054290 | Feb 2003 | JP |
| 1020070117874 | Dec 2007 | KR |
| 1024986 | Jun 2005 | NL |
| 0248851 | Jun 2002 | WO |
| 2005019740 | Mar 2005 | WO |
| 2008054938 | May 2008 | WO |
| 2009073496 | Jun 2009 | WO |
| 2010033563 | Mar 2010 | WO |
| 2011128416 | Oct 2011 | WO |
| 2011149600 | Dec 2011 | WO |
| 2012024534 | Feb 2012 | WO |
| 2012068436 | May 2012 | WO |
| 2012068437 | May 2012 | WO |
| 2012068453 | May 2012 | WO |
| 2012068459 | May 2012 | WO |
| 2012068495 | May 2012 | WO |
| 2012068503 | May 2012 | WO |
| 2012068507 | May 2012 | WO |
| 2012068447 | Jan 2013 | WO |
| 2013052389 | Apr 2013 | WO |
| 2013058820 | Apr 2013 | WO |
| 2013059671 | Apr 2013 | WO |
| Entry |
|---|
| Gao et al., “The Self-Programming Thermostat: Optimizing Setback Schedules Based on Home Occupancy 72 Patterns”, Proceedings of the First ACM Workshop on Embedded Sensing Systems for Energy-Efficiency in Buildings, Association for Computing Machinery, Nov. 2009, pp. 67-72. |
| International Patent Application No. PCT/US2012/030084, International Search Report & Written Opinion, issued Jul. 6, 2012, 7 pages. |
| International Patent Application No. PCT/US2012/030084, International Preliminary Report on Patentability, issued Apr. 22, 2014, 5 pages. |
| International Preliminary Report on Patentability mailed Apr. 8, 2014 for International Patent Application No. PCT/US2012/058207 filed Sep. 30, 2012, 8 pages. |
| Advanced Model Owner's Manual, Bay Web Thermostat, manual [online], [retrieved on Nov. 7, 2012]. Retrieved from the Internet: <URL:http://www.bayweb.com/wp-content/uploads/BW-WT4-2DOC.pdf>, Oct. 6, 2011, 31 pages. |
| Honeywell CT2700, An Electronic Round Programmable Thermostat—User's Guide, Honeywell, Inc., 1997, 8 pages. |
| Honeywell CT8775A,C, The digital Round Non-Programmable Thermostats—Owner's Guide, Honeywell International Inc., 2003, 20 pages. |
| Honeywell T8700C, An Electronic Round Programmable Thermostat—Owner's Guide, Honeywell, Inc., 1997, 12 pages. |
| Honeywell T8775 The Digital Round Thermostat, Honeywell, 2003, 2 pages. |
| Honeywell T8775AC Digital Round Thermostat Manual No. 69-1679EF-1, www.honeywell.com/yourhome, Jun. 2004, pp. 1-16. |
| ICY 3815TT-001 Timer-Thermostat Package Box, ICY BV Product Bar Code No. 8717953007902, 2009, 2 pages. |
| Introducing the New Smart Si Thermostat, Datasheet [online]. Ecobee, Mar. 2012 [retrieved on Feb. 25, 2013]. Retrieved from the Internet: <URL: https://www.ecobee.com/solutions/home/smart-si/>, Mar. 12, 2012, 4 pages. |
| The Clever Thermostat, ICY BV Web Page, http://www.icy.nl/en/consumer/products/clever-thermostat, ICY BV, 2012, 1 page. |
| The Clever Thermostat User Manual and Installation Guide, ICY BV ICY3815 Timer-Thermostat, 2009, pp. 1-36. |
| U.S. Appl. No. 60/512,886, Volkswagen Rotary Knob for Motor Vehicle—English Translation of German Application filed Oct. 20, 2003, all pages. |
| Arens et al., “Demand Response Electrical Appliance Manager—User Interface Design, Development and Testing”, Poster, Demand Response Enabling Technology Development, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2005—6GUiposter.pdf, 2005, 1 page. |
| Arens et al., “Demand Response Enabled Thermostat—Control Strategies and Interface”, Demand Response Enabling Technology Development Poster, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2004—11 CEC—TstatPoster.pdf, 2004, 1 page. |
| Arens et al., “Demand Response Enabling Technology Development”, Phase I Report: Jun. 2003-Nov. 2005, Jul. 27, P:/DemandRes/UC Papers/DR-Phase1 Report-Final DraftApril24-26.doc, University of California Berkeley, pp. 1-108. |
| Arens et al., “New Thermostat Demand Response Enabling Technology”, Poster, University of California Berkeley, Jun. 10, 2004. |
| Auslander et al., “UC Berkeley DR Research Energy Management Group”, Power Point Presentation, DR ETD Workshop, State of California Energy Commission, Jun. 11, 2007, pp. 1-35. |
| Chen et al., “Demand Response-Enabled Residential Thermostat Controls”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Mechanical Engineering Dept. and Architecture Dept., University of California Berkeley, 2008, pp. 1-24 through 1-36. |
| Green, “Thermo Heat Tech Cool”, Popular Mechanics Electronic Thermostat Guide, Oct. 1985, pp. 155-158. |
| Meier et al., “Thermostat Interface Usability: A Survey”, Ernest Orlando Lawrence Berkeley National Laboratory, Environmental Energy Technologies Division, Berkeley California, Sep. 2010, pp. 1-73. |
| International Patent Application No. PCT/US2011/061470, International Search Report & Written Opinion, mailed Apr. 3, 2012, 11 pages. |
| International Patent Application No. PCT/US2011/061470, International Preliminary Report on Patentability, mailed May 30, 2013, 10 pages. |
| International Patent Application No. PCT/US2012/058207, International Search Report & Written Opinion, mailed Jan. 11, 2013, 10 pages. |
| Peffer et al., “A Tale of Two Houses: The Human Dimension of Demand Response Enabling Technology from a Case Study of Adaptive Wireless Thermostat”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Architecture Dept. and Mechanical Engineering Dept., University of California Berkeley., 2008, pp. 7-242 through 7-253. |
| Peffer et al., “Smart Comfort at Home: Design of a Residential Thermostat to Achieve Thermal Comfort, and Save Money and Peak Energy”, University of California Berkeley, Mar. 2007, 1 page. |
| Salus, “S-Series Digital Thermostat Instruction Manuai-ST620 Model No. Instruction Manual”, www.salus-tech.com, Version 005, Apr. 29, 2010, 24 pages. |
| Sanford, “iPod (Click Wheel) (2004)”, www.apple-history.com [retrieved on Apr. 9, 2012]. Retrieved from: http://applehistory.com/ipod, Apr. 9, 2012, 2 pages. |
| Wright et al., “DR ETD—Summary of New Thermostate, TempNode, & New Meter (UC Berkeley Project)”, Power Point Presentation, Public Interest Energy Research, University of California Berkeley. Retrieved from: http://dr.berkeley.edu/dream/presentations/2005—6CEC.pdf, 2005, pp. 1-49. |
| Aprilaire Electronic Thermostats Model 8355 User's Manual, Research Products Corporation, Dec. 2000, 16 pages. |
| Braeburn 5300 Installer Guide, Braeburn Systems, LLC, Dec. 9, 2009, 10 pages. |
| Braeburn Model 5200, Brae burn Systems, LLC, Jul. 20, 2011, 11 pages. |
| Ecobee Smart Si Thermostat Installation Manual, Ecobee, Apr. 3, 2012, 40 pages. |
| Ecobee Smart Si Thermostat User Manual, Ecobee, Apr. 3, 2012, 44 pages. |
| Ecobee Smart Thermostat Installation Manual, Jun. 29, 2011, 20 pages. |
| Ecobee Smart Thermostat User Manual, May 11, 2010, 20 pages. |
| Electric Heat Lock Out on Heat Pumps, Washington State University Extension Energy Program, Apr. 2010, pp. 1-3. |
| Honeywell Installation Guide FocusPRO TH6000 Series, Honeywell International, Inc., Jan. 5, 2012, 24 pages. |
| Honeywell Operating Manual Focus Pro TH6000 Series, Honeywell International, Inc., Mar. 25, 2011, 80 pages. |
| Honeywell Prestige IAQ Product Data 2, Honeywell International, Inc., Jan. 12, 2012, 126 pages. |
| Honeywell Prestige THX9321 and TXH9421 Product Data, Honeywell International, Inc., 68-0311, Jan. 2012, 126 pages. |
| Honeywell Prestige THX9321-9421 Operating Manual, Honeywell International, Inc., Jul. 6, 2011, 120 pages. |
| Hunter Internet Thermostat Installation Guide, Hunter Fan Co., Aug. 14, 2012, 8 pages. |
| Lennox ComfortSense 5000 Owners Guide, Lennox Industries, Inc., Feb. 2008, 32 pages. |
| Lennox ComfortSense 7000 Owners Guide, Lennox Industries, Inc., May 2009, 15 pages. |
| Lennox iComfort Manual, Lennox Industries, Inc., Dec. 2010, 20 pages. |
| Lux PSPU732T Manual, LUX Products Corporation, Jan. 6, 2009, 48 pages. |
| NetX RP32-WI FI Network Thermostat Consumer Brochure, Network Thermostat, May 2011, 2 pages. |
| NetX RP32-WIFI Network Thermostat Specification Sheet, Network Thermostat, Feb. 28, 2012, 2 pages. |
| RobertShaw Product Manual 9620, Maple Chase Company, Jun. 12, 2001, 14 pages. |
| RobertShaw Product Manual 9825i2, Maple Chase Company, Jul. 17, 2006, 36 pages. |
| SCE Energy$mart Thermostat Study for Southern California Edison—Presentation of Study Results, Population Research Systems, Project #1010, Nov. 10, 2004, 51 pages. |
| SYSTXCCUIZ01-V Infinity Control Installation Instructions, Carrier Corp, May 31, 2012,20 pages. |
| T8611G Chronotherm IV Deluxe Programmable Heat Pump Thermostat Product Data, Honeywell International Inc., Oct. 1997, 24 pages. |
| TB-PAC, TB-PHP, Base Series Programmable Thermostats, Carrier Corp, May 14, 2012, 8 pages. |
| The Perfect Climate Comfort Center PC8900A W8900A-C Product Data Sheet, Honeywell International Inc, Apr. 2001, 44 pages. |
| TP-PAC, TP-PHP, TP-NAC, TP-NHP Performance Series AC/HP Thermostat Installation Instructions, Carrier Corp, Sep. 2007, 56 pages. |
| Trane Communicating Thermostats for Fan Coil, Trane, May 2011, 32 pages. |
| Trane Communicating Thermostats for Heat Pump Control, Trane, May 2011, 32 pages. |
| Trane Install XL600 Installation Manual, Trane, Mar. 2006, 16 pages. |
| Trane XL950 Installation Guide, Trane, Mar. 2011, 20 pages. |
| Venstar T2900 Manual, Venstar, Inc., Apr. 2008, 113 pages. |
| Venstar T5800 Manual, Venstar, Inc., Sep. 7, 2011, 63 pages. |
| VisionPRO TH8000 Series Installation Guide, Honeywell International, Inc., Jan. 2012, 12 pages. |
| Vision PRO TH8000 Series Operating Manual, Honeywell International, Inc., Mar. 2011, 96 pages. |
| VisionPRO Wi-Fi Programmable Thermostat, Honeywell International, Inc. Operating Manual, Aug. 2012, 48 pages. |
| White Rodgers (Emerson) Model 1 F81-261 Installation and Operating Instructions, White Rodgers, Apr. 15, 2010, 8 pages. |
| White Rodgers (Emerson) ModeiiF98EZ-1621 Homeowner's User Guide, White Rodgers, Jan. 25, 2012, 28 pages. |
| Allen, et al., “Real-Time Earthquake Detection and Hazard Assessment by ElarmS Across California”, Geophysical Research Letters, vol. 36, LOOB08, 2009, pp. 1-6. |
| Bourke, Server Load Balancing, O'Reilly & Associates, Inc., Aug. 2001, 182 pages. |
| De Almeida, et al., “Advanced Monitoring Technologies for the Evaluation of Demand-Side Management Programs”, Energy, vol. 19, No. 6, 1994, pp. 661-678. |
| Deleeuw, “Ecobee WiFi Enabled Smart Thermostat Part 2: The Features Review”, Retrieved from <URL: http://www. homenetworkenabled. com/content. ph p? 136-ecobee-Wi Fi-enabled-Smart-Thermostat -Part-2-The Features-review>, Dec. 2, 2011, 5 pages. |
| Detroitborg, Nest Learning Thermostat: Unboxing and Review, [online], retrieved from the Internet: URL:http://www.youtube.com/watch?v=KrgcOL4oLzc [retrieved on Aug. 22, 2013], Feb. 10, 2012, all pages. |
| Gevorkian, “Alternative Energy Systems in Building Design”, 2009, pp. 195-200. |
| Hoffman, et al., “Integration of Remote Meter Reading, Load Control and Monitoring of Customers' Installations for Customer Automation with Telephone Line Signaling”, Electricity Distribution, 1989. CIRED 1989. 10th International Conference on, May 8-12, 1989, pp. 421-424. |
| Levy, R., “A Vision of Demand Response—2016”, The Electricity Journal, vol. 19, Issue 8, Oct. 2006, pp. 12-23. |
| Loisos, et al., “Buildings End-Use Energy Efficiency: Alternatives to Compressor Cooling”, California Energy Commission, Public Interest Energy Research, Jan. 2000, 80 pages. |
| Lopes, “Case Studies in Advanced Thermostat Control for Demand Response”, AEIC Load Research Conference, St. Louis, MO, Jul. 2004, 36 pages. |
| Lu, et al., “The Smart Thermostat: Using Occupancy Sensors to Save Energy in Homes”, In Proceedings of the 8th ACM Conference on Embedded Networked Sensor Systems, Nov. 3-5, 2010, pp. 211-224. |
| Martinez, “SCE Energy$mart Thermostat Program”, Advanced Load Control Alliance, Oct. 5, 2004, 20 pages. |
| Matty, “Advanced Energy Management for Home Use”, IEEE Transaction on Consumer Electronics, vol. 35, No. 3, Aug. 1989, pp. 584-588. |
| Motegi, et al., “Introduction to Commercial Building Control Strategies and Techniques for Demand Response”, Demand Response Research Center, May 22, 2007, 35 pages. |
| Mozer, “The Neural Network House: An Environmental that Adapts to it's Inhabitants”, AAAI Technical Report SS-98-02, 1998, pp. 110-114. |
| White, et al., “A Conceptual Model for Simulation Load Balancing”, Proc. 1998 Spring Simulation Interoperability Workshop, 1998, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20140358293 A1 | Dec 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61627996 | Oct 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13656189 | Oct 2012 | US |
| Child | 14463550 | US |
