Patent Grant
10318266
The present disclosure relates generally to thermostats and more particularly to the improved control of a building or space's heating, ventilating, and air conditioning (HVAC) system through the use of a multi-function, multi-touch, thermostat.
A thermostat is, in general, a component of an HVAC control system. Traditional thermostats sense the temperature of a system and control components of the HVAC in order to maintain a setpoint. A thermostat may be designed to control a heating or cooling system or an air conditioner. Thermostats are manufactured in many ways, and use a variety of sensors to measure temperature and other desired parameters of a system.
Conventional thermostats are configured for one-way communication to connected components, and to control HVAC systems by turning on or off certain components or by regulating flow. Each thermostat may include a temperature sensor and a user interface. The user interface typically includes display for presenting information to a user and one or more user interface elements for receiving input from a user. To control the temperature of a building or space, a user adjusts the setpoint via the thermostat's user interface.
One implementation of the present disclosure is a thermostat. The thermostat includes a motherboard, a first modular board, and a display. The motherboard is configured to perform a thermostat function and generate a user interface a user interface including information relating to the thermostat function. The first modular board is configured to be added to the thermostat by coupling the first modular board to the motherboard and to be removed from the thermostat by decoupling the first modular board from the motherboard. The first modular board is configured to supplement the thermostat function performed by the motherboard when the first modular board is coupled to the motherboard. The display is communicably coupled to the motherboard. The display is configured to display the user interface. The motherboard is configured to adaptively reconfigure the user interface to include supplemental information provided by the first modular board in response to coupling of the first modular board to the motherboard.
Another implementation of the present disclosure is a system for operating a thermostat. The system includes a thermostat and an external device, the thermostat for interacting with a building automation system. The thermostat is configured to provide a user interface that facilitates user interaction with the building automation system. The thermostat includes a first modular board, a display, and an equipment model. The first modular board is configured to perform a thermostat function. The first modular board is configured to be removable from the thermostat. The display is configured to display the user interface. The equipment model defines a variable used by the thermostat and is configured to facilitate interactions between the thermostat and the building automation system. The equipment model is based on the thermostat function. The external device is configured to communicate with the thermostat. The external device contains a library of equipment model updates. The thermostat is configured to adaptively reconfigure the user interface to remove supplemental information provided by the first modular board in response to removal of the first modular board.
Another implementation of the present disclosure is a method for reconfiguring a thermostat. The method includes connecting a modular board to the thermostat, the modular board configured to perform a thermostat function. The method also includes receiving, by the thermostat, a signal from the modular board, the signal including information about the modular board. The method also includes transmitting, by the thermostat, an equipment model update request based on the signal from the modular board. The method also includes receiving, by the thermostat, an equipment model update in response to the equipment model update request, the equipment model update based on the signal from the modular board. The method also includes applying, by the thermostat, the equipment model update to an equipment model of the thermostat. The equipment model defines a variable used by the thermostat and is configured to facilitate interactions between the thermostat and a building automation system.
Overview
Referring generally to the FIGURES, a modular multi-function, multi-touch thermostat is shown, according to various exemplary embodiments. The modular thermostat described herein may be used in any HVAC system, room, environment, or system within which it is desired to control and/or observe environmental conditions (e.g., temperature, humidity, etc.). In traditional HVAC systems, a thermostat may be adjusted by a user to control the temperature of a system. A traditional thermostat is not intended to be upgraded by a user once installed in an application. Rather, traditional thermostats are intended to be replaced after the thermostat has either failed (i.e., the thermostat is no longer operable for its intended purpose) or has outdated and undesirable capabilities (e.g., the user wishes to have more control over the thermostat, the user wishes to have a greater precision of control over the thermostat, etc.).
The modular thermostat is intended to provide the user with an unparalleled ability to upgrade, repair, or replace individual components of the modular thermostat without replacing the entire modular thermostat. The modular thermostat may include a multitude of modular boards, each of which may provide the modular thermostat with different capabilities which may be utilized by the user. For example, the modular thermostat may include a display, a motherboard, a networking board, an occupancy detection board, a humidity board, a near field communications (NFC) board, a temperature board, an energy harvesting board, a battery board, and/or any other type of modular board. Each board is intended to include some form of memory for storing commands, data, or other useful information. In the future, as technology advances, other types of modular boards may be developed which may, in turn, be included with or added to the modular thermostat. The modular thermostat may be directly controlled by a user, or may autonomously control the parameters of a system according to stored user specified parameters.
The various components within the modular thermostat each serve a specified purpose within the modular thermostat. For example, the display may display information to a user regarding the desired parameters of a system, such as temperature, humidity, etc. The display may be touch-sensitive, such that a user may easily manipulate objects on the display. The motherboard may be configured to interact with the modular thermostat and the various modular boards. The humidity board may be configured to measure the humidity of a system and to transmit the measured humidity information to the modular thermostat. The NFC board may be configured to allow communications between the modular thermostat and an external device through NFC. The temperature board may be configured to measure the temperature of a system and to transmit the measured temperature information to the modular thermostat. The energy harvesting board may be configured to interact with an energy harvesting apparatus in the system. The networking board may be configured to allow the modular thermostat to communicate with other devices through the internet, Bluetooth, Wi-Fi, or other suitable communications platform. The occupancy detection board may be configured to monitor the occupancy of a system (i.e., how many people are in a room) and adjust the controls of the modular thermostat accordingly. The battery board may include a supplementary battery system intended to provide backup power to the modular thermostat in the event of a power outage.
As future technologies develop, other modular boards will be made available for use with the modular thermostat. The modular thermostat is intended to be used with any combination of the listed modular boards or any other modular board to provide additional functionality. For example, the modular thermostat may only include the temperature board. In addition, the modular boards may each be upgraded independently of the modular thermostat. For example, the modular thermostat may include a temperature board which has an out-of-date sensor. A user may wish to increase the capabilities of the sensor without replacing the entire modular thermostat. In this case, the user may simply replace and upgrade the temperature board to provide the requested capability.
Building with HVAC System and Thermostat
Air handlers 18 are coupled to ductwork 20 that is adapted to distribute air between the air handlers and may receive air from an outside intake (not shown). Air handlers 18 include heat exchangers that circulate cold water from chiller 12 and hot water from boiler 14 to provide heated or cooled air. Fans, within air handlers 18, draw air through the heat exchangers and direct the conditioned air to environments within building 10, such as spaces, apartments, or offices, to maintain the environments at a designated temperature. A control device 22, shown here as including a thermostat, may be used to designate the temperature of the conditioned air. Control device 22 also may be used to control the flow of air through and from air handlers 18 and to diagnose mechanical or electrical problems with the air handlers 18. Other devices may, of course, be included in the system, such as control valves that regulate the flow of water and pressure and/or temperature transducers or switches that sense the temperatures and pressures of the water, the air, and so forth. Moreover, the control device may communicate with computer systems that are integrated with or separate from other building control or monitoring systems, and even systems that are remote from the building.
When the system shown in
Outdoor unit 30 draws in environmental air through its sides as indicated by the arrows directed to the sides of the unit, forces the air through the outer unit coil using a fan (not shown), and expels the air as indicated by the arrows above the outdoor unit. When operating as an air conditioner, the air is heated by the condenser coil within the outdoor unit and exits the top of the unit at a temperature higher than it entered the sides. Air is blown over indoor coil 32 and is then circulated through residence 24 by means of ductwork 20, as indicated by the arrows entering and exiting ductwork 20. The overall system operates to maintain a desired temperature as set by system controller 22. When the temperature sensed inside the residence is higher than the set point on the thermostat (with the addition of a relatively small tolerance), the air conditioner will become operative to refrigerate additional air for circulation through the residence. When the temperature reaches the set point (with the removal of a relatively small tolerance), the unit will stop the refrigeration cycle temporarily.
When the unit in
The operation of indoor and outdoor units 28 and 30 is controlled by control circuits 48 and 46, respectively. The control circuits 46 and 48 may execute hardware or software control algorithms to regulate the HVAC system. In some embodiments, the control circuits may include one or more microprocessors, analog to digital converters, non-volatile memories, and interface boards. In certain embodiments, the control circuits may be fitted with or coupled to auxiliary control boards that allow conventional 24 VAC wiring to be controlled through serial communications.
The control circuits 46 and 48 may receive control signals from control device 22 and transmit the signals to equipment located within indoor unit 28 and outdoor unit 30. For example, outdoor control circuit 46 may route control signals to a motor 50 that powers a fan 52 and to a motor 54 that powers a compressor 56. Indoor control circuit 48 may route control signals to a motor 58 that powers a fan 60. The control circuits also may transmit control signals to other types of equipment such as valves 62 and 64, sensors, and switches.
In some embodiments, control device 22 may communicate with control circuits 46 and 48 by transmitting communication packets over a serial communication interface. Control device 22 may function as the master system controller while control circuits 46 and 48 operate as slave devices. In certain embodiments, control device 22 may send a ping message to discover connected slave devices and their properties. For example, control circuits 46 and 48 may transmit an acknowledgement message in response to receiving a ping message from control device 22. Control circuits 46 and 48 also may transmit information, in response to requests from control device 22, identifying the type of unit and specific properties of the unit. For example, control circuit 46 may transmit a signal to control device 22 indicating that it controls a two-stage heat pump with auxiliary heat and a bonnet sensor. Control circuits 46 and 48 also may transmit signals identifying terminal connections and jumper settings of the control circuits.
Control device 22 may operate to control the overall heating and cooling provided by indoor and outdoor units 28 and 30. Indoor and outdoor units 28 and 30 include coils 66 and 32, respectively, that both operate as heat exchangers. The coils may function either as an evaporator or a condenser depending on the heat pump operation mode. For example, when heat pump system 42 is operating in cooling (or “AC”) mode, outside coil 32 functions as a condenser, releasing heat to the outside air, while inside coil 66 functions as an evaporator, absorbing heat from the inside air. When heat pump system 42 is operating in heating mode, outside coil 32 functions as an evaporator, absorbing heat from the outside air, while inside coil 66 functions as a condenser, releasing heat to the inside air. A reversing valve may be positioned on closed loop 44 to control the direction of refrigerant flow and thereby to switch the heat pump between heating mode and cooling mode.
Heat pump system 42 also includes two metering devices 62 and 64 for decreasing the pressure and temperature of the refrigerant before it enters the evaporator. The metering devices also regulate the refrigerant flow entering the evaporator so that the amount of refrigerant entering the evaporator equals, or approximately equals, the amount of refrigerant exiting the evaporator. The metering device used depends on the heat pump operation mode. For example, when heat pump system 74 is operating in cooling mode, refrigerant bypasses metering device 62 and flows through metering device 64 before entering inside coil 66, which acts as an evaporator. In another example, when heat pump system 42 is operating in heating mode, refrigerant bypasses metering device 64 and flows through metering device 62 before entering outside coil 32, which acts as an evaporator. According to other exemplary embodiments, a single metering device may be used for both heating mode and cooling mode. The metering devices typically are thermal or electronic expansion valves, but also may be orifices or capillary tubes.
The refrigerant enters the evaporator, which is outside coil 32 in heating mode and inside coil 66 in cooling mode, as a low temperature and pressure liquid. Some vapor refrigerant also may be present as a result of the expansion process that occurs in metering device 62 or 64. The refrigerant flows through tubes in the evaporator and absorbs heat from the air changing the refrigerant into a vapor. In cooling mode, the indoor air flowing across the multichannel tubes also may be dehumidified. The moisture from the air may condense on the outer surface of the multichannel tubes and consequently be removed from the air.
After exiting the evaporator, the refrigerant flows into compressor 56. Compressor 56 decreases the volume of the refrigerant vapor, thereby, increasing the temperature and pressure of the vapor. The compressor may be any suitable compressor such as a screw compressor, reciprocating compressor, rotary compressor, swing link compressor, scroll compressor, or turbine compressor.
From compressor 56, the increased temperature and pressure vapor refrigerant flows into a condenser, the location of which is determined by the heat pump mode. In cooling mode, the refrigerant flows into outside coil 32 (acting as a condenser). Fan 52, which is powered by motor 50, draws air across the tubes containing refrigerant vapor. According to certain exemplary embodiments, the fan may be replaced by a pump that draws fluid across the multichannel tubes. The heat from the refrigerant is transferred to the outside air causing the refrigerant to condense into a liquid. In heating mode, the refrigerant flows into inside coil 66 (acting as a condenser). Fan 60, which is powered by motor 58, draws air across the tubes containing refrigerant vapor. The heat from the refrigerant is transferred to the inside air causing the refrigerant to condense into a liquid.
After exiting the condenser, the refrigerant flows through the metering device (62 in heating mode and 64 in cooling mode) and returns to the evaporator (outside coil 32 in heating mode and inside coil 66 in cooling mode) where the process begins again.
In both heating and cooling modes, motor 54 drives compressor 56 and circulates refrigerant through reversible refrigeration/heating loop 44. The motor may receive power either directly from an AC or DC power source or from a variable speed drive (VSD). The motor may be a switched reluctance (SR) motor, an induction motor, an electronically commutated permanent magnet motor (ECM), or any other suitable motor type.
The operation of motor 54 is controlled by control circuit 46. Control circuit 46 may receive control signals from control device 22. In certain embodiments, control device may receive information from a sensor 68 that measures the ambient indoor air temperature. Control device 22 then compares the air temperature to the temperature set point (which may be input by a user) and engages compressor motor 54 and fan motors 50 and 58 to run the cooling system if the air temperature is above the temperature set point. In heating mode, control device 22 compares the air temperature from sensor 68 to the temperature set point and engages motors 50, 54, and 58 to run the heating system if the air temperature is below the temperature set point.
The control circuit 46 and control device 22 also may initiate a defrost cycle when the system is operating in heating mode. When the outdoor temperature approaches freezing, moisture in the outside air that is directed over outside coil 32 may condense and freeze on the coil. Sensors may be included within outdoor unit 30 to measure the outside air temperature and the temperature of outside coil 32. These sensors provide the temperature information to the control circuit 46 which determines when to initiate a defrost cycle.
Referring now to
Thermostat 404 communicates with a controller 412. In various embodiments, controller 412 may be integrated with thermostat 404 or may exist as a separate controller (e.g., a field and equipment controller, a supervisory controller, etc.) that receives input from thermostat 404. Thermostat 404 may send temperature measurements and user-defined temperature setpoints to controller 412. Controller 412 uses the temperature measurements and the setpoints to generate a control signal for HVAC equipment 414. The control signal causes HVAC equipment 414 to provide heating and/or cooling for building space 402.
Referring now to
Modular Thermostat
Referring now to
In
A number of receiving slots 74 included within modular thermostat 600 may come in various shapes and of various dimensions in order to suit application needs. For example, according to some embodiments and as shown in
Motherboard 818 may be a printed circuit board (PCB) and may contain a central processing unit (CPU) and memory, as well as also providing a number of connectors for various peripherals such as a number of modular boards 1925 and display 802. Motherboard 818 may be produced in a variety of computer form factors, such as, but not limited to, Neo-ITX, Pico-ITX, Mobile-ITX, Nano-ITX, Mini-ITX, Extended ATX (ETAX), LPX, Mini-LPX, SWTX, UTX, Enhanced Extended ATX (EEATX), SSI CEB, SSI EEB, SSI MEB, CoreExpress, COM Express Basic, COM Express Compact, COM Express Mini, PCI/104-Express, PCIe/104, PC/104-Plus, PC/104, ETX, BTX, MicroBTX, PicoBTX, FlexATX, NLX, WTX, ATX, Baby-AT, AT, XT, HPTX, smartModule, Mini-ATX, DTX, Mini-DTX, XTX, and microATC. A person having ordinary skill in the art would understand that various computer form factors are possible and that motherboard 818 may easily be adapted for future computer form factors. According to various embodiments, motherboard 818 may include any number and combination of disk controllers, integrated graphics controllers supporting 2D and/or 3D graphics, an integrated sound card, a fast Ethernet network controller, a SATA connector, a nSATA connector, an IDE connector, a DIMM memory slot, a CPU fan, a PCI slot, an integrated audio codec chip, a CPU fan and heat sink mount, a power connector, a super IO chip, a USB 2.0 and USB 3.0, or similar, connectivity, IrDA controller for infrared data communication, temperature, voltage, and fan-speed sensors, or other suitable computing, graphics, or audio components. Motherboard 818 may include a basic input output system (BIOS) stored in an EEPROM chip soldered to or socketed on motherboard 818, used to boot an operating system.
Receiving bay 836 may include any number of connectors for structurally and electronically connecting to any number of modular boards 1925. The connectors may operate similarly to expansion slots, such as PCI slots, of a traditional motherboard 818. According to various embodiments, receiving bay 836 does not include processor 702 and serves to provide an infrastructure for the interconnection of the modular boards 1925 with each other and additional components of modular thermostat 600, such as display 802. However, in some embodiments, receiving bay 836 may optionally include processor 702.
Receiving slots 74 are intended to receive any one of the compatible modular boards 1925. In one embodiment, when inserting the modular board 1925 into modular thermostat 600, the user first inserts the board into rails 72 disposed at the desired location. Next, the modular board 1925 is guided along rails 72 until the modular board 1925 connects to the receiving slot. The connection of the modular board 1925 to the receiving slot is not only structural but electrical as well. For example, inserting humidity board 824 into a receiving slot and connecting it may allow the user to measure the humidity of a space. Depending on the receiving slot, the modular board 1925 may snap or lock into place. For example, certain connector holds and press-fit mechanisms exist that could be utilized by the receiving slot and modular board. While it is envisioned that all modular boards 1925 may be compatible with all receiving slots 74, it is possible that only some modular boards 1925 are compatible with some receiving slots 74. For example, as technology becomes more advanced, modular thermostat 600 may have more than one version (e.g., generation) of receiving slot, such as motherboard 818 or a receiving bay 836. The new version receiving slot may provide added capability and therefore may require different modular boards 1925. While the modular boards 1925 and receiving slots 74 illustrated are generally square or rectangular in shape, in other various embodiments modular thermostat 600 may accept boards of all shapes and of all dimensions. As modular boards 1925 become more advanced, other physical configurations may prove to be advantageous over traditional modular board 1925 design. For example, in order to maximize space, modular boards 1925 may become cylindrical and would connect to corresponding cylindrical receiving slots 74 within modular thermostat 600.
Rails 72 included within modular thermostat 600 may come in various shapes and of various dimensions in order to suit application needs. For example, in some embodiments, server rack rails 72 may be used. Rails 72 of modular thermostat 600 may be sized to accept a plurality of modular boards 1925, which will be discussed in greater detail herein. Rails 72 are intended to provide a universal receiving mechanism for all modular boards 1925.
According to various embodiments, other suitable holding mechanisms may be alternatively used. For example, rather than sliding the modular boards 1925 into and out of rails 72, the user may simply place them into a different holding mechanism, such as a number of shelves, or, alternatively, one continuous shelf. Other holding mechanisms include pegs, slots, etc. As shown in
While
In terms of material construction, modular thermostat 600 may be constructed out of any suitable structural material or grouping thereof. According to one embodiment, modular thermostat 600 may be constructed from plastic or another polymeric blend. In other embodiments, modular thermostat 600 may be constructed from a metallic material such as aluminum.
In some applications, modular thermostat 600 may provide another distinct advantage over a conventional thermostat. During building construction, a thermostat installation requires a joint effort between HVAC installers as well as the building construction service due to the various connections that need to be made. Using modular thermostat 600 allows installation of the thermostat to be completed after building construction. First, the building construction service simply pre-wires modular thermostat 600 to a power source. Second, after the installation of the building has been completed, the rest of the necessary installation can be performed by the HVAC installers.
According to various embodiments, modular thermostat 600 may include display 802, as shown in
Referring to
Display 802 may include many different components. In some embodiments, display 802 includes a frame partially or completely surrounding display 802. Display 802 may also take various functional forms.
Display 802 may define a front face of modular thermostat 600. Display 802 may be mounted substantially flush with wall 70 such that modular thermostat 600 is entirely contained within wall 70. By mounting display 802 flush with wall 70, modular thermostat 600 may be more aesthetically pleasing then conventional thermostats that extend from a wall. As shown in
In some applications, integrated sensor 1100 is integrated into display 802. In these applications, integrated sensor 1100 may be connected to any modular board 1925, motherboard 818, and/or receiving bay 836. In other applications, integrated sensor 1100 is integrated into any modular board 1925, motherboard 818, and/or receiving bay 836. In these applications, display 802 may include a portion (e.g., hole, etc.) through which integrated sensor 1100 may protrude or through which integrated sensor 1100 may project a sensor beam through.
According to various embodiments, display 802 may be of various sizes and thicknesses. According to some embodiments, display 802 may be oversized relative to the opening on modular thermostat 600.
According to various embodiments, modular thermostat 600 may include additional components disposed on modular thermostat 600. For example, modular thermostat may include a security device. According to other embodiments, display 802 may be smaller than the face of modular thermostat 600, meaning that there is a certain spacing between display and the frame. In some embodiments, this spacing may be occupied by buttons. In other embodiments, the security device such as a keypad entry, a tumbler, a biometric device, a retinal scanner, an iris recognition device, or other suitable security device may be disposed in this spacing.
Referring still to
Device 3304 may provide additional capabilities to modular thermostat 600. In some embodiments, device 3304 contains communications means which modular thermostat 600 does not otherwise have. For example, modular thermostat 600 may only have communications electronics which are configured for Bluetooth communications. Device 3304 may contain communications electronics which allow modular thermostat 600 to communicate over Wi-Fi, expanding the network of devices and applications with which modular thermostat 600 can interact. In one embodiment, a previous model of thermostat may be retrofit with device 3304 to gain functionality of features of modular thermostat 600.
Any number of fasteners 812 may be used to secure front plate 810 to modular thermostat 600. Further, there is no requirement that all fasteners 812 be of the same variety. For example, front plate 810 could be fastened to modular thermostat 600 using two Torx fasteners 812 and two security Torx fastener. Alternatively, front plate 810 may simply be snapped in to modular thermostat 600, or magnetically coupled to modular thermostat 600, or affixed to modular thermostat 600 through the use of an adhesive. Front plate 810 may be made of any desired material. For example, front plate 810 may be made to match the surface of wall 70 modular thermostat 600 is mounted to. In other embodiments, front plate 810 may have indicia 816 printed, engraved, or otherwise inscribed on it. In other embodiments, a sticker containing indicia 816 may be placed on front plate 810. The indicia 816 may include warnings printed in a language, instructions, graphical images, or other suitable communications languages. For example, front plate 810 may be red in color and have “DO NOT OPEN” inscribed on it to discourage unauthorized individuals from tampering with modular thermostat 600.
According to some embodiments, front plate 810 may include a number of locks 814 to secure front plate 810 to modular thermostat 600 and prevent tampering or use by unauthorized users. These locks 814 may be key locks 814, tumbler locks 814, or other suitable locking mechanisms. In some embodiments, front plate 810 may include a dedicated security device may be configured to lock and unlock front plate 810. The dedicated security device may be a keypad entry, a tumbler, a biometric device, a retinal scanner, an iris recognition device, or other suitable security device.
In some embodiments, display 802 provides a security interface (e.g., lock screen, authorization request, etc.). For example, display 802 may request a security key (e.g., a person identification number, a biometric identifier, a key card, an RFID badge, a password, etc.) from a user before providing the user with access to various features of modular thermostat 600 such as configuration and set-up features. In some applications, this may allow an authorized maintenance worker to adjust the settings of modular thermostat 600 while preventing an unauthorized occupant from doing so. According to various embodiments, display 802 is configured to display information (e.g., temperature, humidity, occupancy, date, time, etc.) to users without requiring entry of the security key. In this way, modular thermostat 600 may achieve a more aesthetically pleasing external appearance compared to conventional thermostats which are often encased in supplemental, tamper-proof enclosures to prevent unauthorized modifications.
While front plate 810 has been discussed as attaching to modular thermostat 600 through fastening or other attachment mechanisms, it is also envisioned that front plate 810 could be of the sliding door variety. For example, according to one embodiment, front plate 810 may be flexible, may move through slots disposed on modular thermostat 600 or wall 70, and may have a lock that the user can articulate to secure the door to modular thermostat 600 or to open modular thermostat 600. According to some embodiments, front plate 810 may also include a dedicated hardware interface 808. The dedicated hardware interface 808 may be configured to accept USB, micro-USB, Firewire, Thunderbolt, Ethernet, VGA, or any other suitable communications connection. In various embodiments, the dedicated hardware interface 808 may be connected directly to any number of modular boards 1925. In other embodiments, the dedicated hardware interface 808 may be directly connected to motherboard 818 or receiving bay 836. In still other embodiments, the dedicated hardware interface 808 may be connected directly to any number of modular boards 1925 and motherboard 818 or receiving bay 836. Depending on the configuration of modular thermostat 600, some, or all of the features on the dedicated hardware interface 808 may be active (i.e., some of the ports may not be connected to a modular board/motherboard 818/receiving bay 836. Different dedicated hardware interfaces 808 and dedicated security devices may be interchanged (e.g., swapped, replaced, upgraded, updated, etc.) by the user throughout the life of the modular interface without the need for rewiring. In some embodiments, front plate 810 may be a thin sheet or film attached to modular thermostat 600 configured only to prevent the modular boards 1925 or other internal components of modular thermostat 600 from encountering undesirable particulates. According to various embodiments, the user may utilize modular thermostat 600 without display 802 or front plate 810. In some applications, it may not be necessary for modular thermostat 600 to be covered or constant accessibility to the modular boards 1925 is desired.
In some applications, it may be desirable for front plate 810 or display 802 to be sealed. For example, various types of seals such water proof, water tight, water resistant, air tight, impact resistant, corrosion resistant, or to have other suitable seals can be attained. It is envisioned that front plate 810 and/or display 802 could be easily adapted to meet these needs. For example, in some applications modular thermostat 600 may be installed in a high-humidity environment such as a green house or laboratory. In such environments, condensation build-up may be an issue. As such, various sealing mechanisms such as gaskets, seals, epoxies, and other suitable sealing mechanisms may prevent condensation from penetrating modular thermostat 600. In some applications, such as marine applications, it may desirable to have complete water protection of modular thermostat 600. In these situations, more robust sealing mechanisms may be necessary. In some applications, front plate 810 may be included with modular thermostat 600 to provide the necessary sealing mechanism.
Further, according to the exemplary embodiment shown in
Modular Boards
In some embodiments, modular boards 1925 communicate with modular thermostat using an encrypted communication. In these embodiments, only authorized modular boards 1925 may be communicable (i.e., capable of communicating) with modular thermostat 600. For example, pirated (e.g., counterfeit, etc.) components may not be communicable with motherboard 818. The encrypted communication may be updated and/or supplemented at regular intervals for both modular thermostat 600 and modular boards 1925. Alternatively, modular boards 1925 may include an authentication chip is required for recognition by, and communication with, modular thermostat 600.
As will be described according to various embodiments, various configurations and combinations of modular boards 1925 within modular thermostat 600 are possible. For example, modular thermostat 600 may include any combination of display 802, motherboard 818, networking board 820 including memory, occupancy detection board 822 including memory, humidity board 824 including memory, NFC board 826 including memory, temperature board 828 including memory, an energy harvesting board 830 including memory, and battery board 832 including memory. Additional modular boards 1925 may be included within modular thermostat 600 as needed for a given application.
According to various embodiments, motherboard 818 adaptively reconfigures (e.g., displays relevant information, hides non-essential information, etc.) user interface 406 displayed on display 802 based on which modular boards 1925 are included in modular thermostat 600. For example, if modular thermostat 600 includes humidity board 824 and temperature board 828, motherboard 818 may configure user interface 406 that is displayed (e.g., provided, etc.) on display 802 to display temperature information and humidity information. Following this example, if humidity board 824 is interchanged with occupancy detection board 822, motherboard 818 may adaptively reconfigure user interface 406 displayed on display 802 to display occupancy information rather than humidity information. In other examples, motherboard 818 may configure user interface 406 provided on display 802 to display battery information (e.g., current battery level, time to charge battery, battery cell life, etc.) if battery board 832 is included in modular thermostat 600, motherboard 818 may configure user interface 406 provided on display 802 to display energy harvesting information (e.g., amount of energy harvested, amount of money saved through energy harvesting, etc.) if energy harvesting board 830 is included in modular thermostat 600, motherboard 818 may configure user interface 406 displayed on display 802 to include NFC information (e.g., number of nearby NFC devices, etc.) if NFC board 826 is included in modular thermostat 600, and motherboard 818 may configure user interface 406 to include network information (e.g., network name, network speed, etc.) if modular thermostat 600 includes networking board 820.
The cross-sectional structural views illustrated in
As shown in
Equipment model 1922 may be implemented in a provisioning system (e.g., auto-provisioning system, etc.) where modular thermostat is interacted with differently by a BAS depending on the modular boards 1925 coupled to modular thermostat 600. Through the use of equipment model 1922, modular thermostat 600 may appear differently to the BAS depending on the thermostat functions available to modular thermostat 600 through the modular boards 1925 coupled to modular thermostat 600. For example, if humidity board 824 is coupled to modular thermostat 600, equipment model 1922 may have a variable that indicates to the BAS that modular thermostat 600 is capable of obtaining humidity measurements. However, if occupancy detection board 822 is also coupled to modular thermostat 600, equipment model 1922 may have a variable that indicates to the BAS that modular thermostat 600 is capable of obtaining humidity and occupancy measurements.
In some embodiments, memory 1930 contains a database with attributes, capabilities, and configuration information for various modular boards 1925. In these embodiments, when modular board recognizer 1920 receives a signal from modular board 1925 when modular board 1925 first becomes communicable with motherboard 818, modular board recognizer 1920 transmits the identification and/or type to memory 1930. Memory 1930 then searches the database for the attributes, capabilities, and configuration information corresponding to that identification and/or type. Memory 1930 then flags the corresponding attributes, capabilities, and configuration information as associated with modular board 1925. Memory 1930 may be periodically updated such that the database is updated. In this way, memory 1930 may recognize additional modular boards 1925.
Modular board recognizer 1920 then stores all of the information from the signal in memory 1930 such that the information remains associated with the modular board 1925 from which it was transmitted. Modular board recognizer 1920 may then reconfigure modular thermostat 600 based on information stored in memory 1930 or based on information obtained from an external device. For example, modular board recognizer 1920 may recognize that a new networking board 820 has been connected to modular thermostat 600. Modular board recognizer 1920 may reconfigure modular thermostat 600 based on information (e.g., communication protocols, power consumption requirements, etc.) stored in memory 1930, or may download that information from an external device (e.g., personal electronic device, computer, smart phone, server, cloud network, mobile device, etc.).
Based on the attributes, capabilities, and configuration information for all modular boards 1925 communicable with modular thermostat 600, modular thermostat 600 may be operated differently. For example, when temperature board 828 is connected to modular thermostat 600 and becomes communicable with motherboard 818, motherboard 818 may adaptively reconfigure user interface 406 displayed on display 802 to display temperature information. Similarly, when humidity board 824 is removed and is no longer communicable with motherboard 818, motherboard 818 may adaptively reconfigure user interface 406 displayed on display 802 to remove any humidity information.
Memory 1930 includes a module for gathering data 1940, a module for processing data 1950, a module for transmitting data 1960, a module for storing data 1970, a module for securing data 1980, and a module for analyzing data 1990. Gathering data module 1940 may be utilized to obtain data from modular boards 1925. For example, gathering data module 1940 may periodically request data from any modular boards 1925 communicable with motherboard 818. Processing data module 1950 may process data obtained by gathering data module 1940 to make various determinations. For example, processing data module 1950 may compare the temperature provided by temperature board 828 and the humidity provided by humidity board 824 to determine if modular thermostat 600 should instruct an air conditioning system to be turned on to provide cooling.
Transmitting data module 1960 may transmit data from modular thermostat to an external device (e.g., personal electronic device, computer, smart phone, server, cloud network, mobile device, etc.). For example, transmitting data module 1960 may transmit temperature information provided by temperature board 828 to a smart phone associated with a user so that the user can visualize temperature in real time on the smart phone. In some applications, transmitting data module 1960 may transmit a push notification to a user, potentially causing a display on a person electronic device associated with the user to activate. According to various embodiments, transmitting data module 1960 is utilized to update motherboard 818 for a new modular board 1925. Transmitting data module 1960 may communicate with an external device (e.g., via NFC, via RFID, via Bluetooth, via Bluetooth low energy, etc.). The external device may upload attributes, capabilities, and configuration information corresponding to the new modular board 1925 to motherboard 818. The new modular board 1925 may then be connected to modular thermostat 600. In applications where an existing modular board 1925 is replaced by a new modular board 1925, transmitting data module 1960 may transmit various information (e.g., settings, configurations, etc.) from the old modular board 1925 to the external device (e.g., via NFC, via RFID, via Bluetooth, via Bluetooth low energy, etc.). The external device may then transmit the various information received from transmitting data module 1960 to the new modular board 1925 (e.g., via NFC, via RFID, via Bluetooth, via Bluetooth low energy, etc.).
Storing data module 1970 may be utilized by motherboard 818 to store information received from modular boards 1925 and to store identifications, types, attributes, capabilities, and configuration information corresponding to various modular boards 1925. For example, storing data module 1970 may periodically store temperature information provided by temperature board 828 (e.g., to develop a chronological temperature plot, etc.). In another example, storing data module 1970 may be periodically updated to increase the database of modular boards 1925 that modular board recognizer 1920 can search. Securing data module 1980 may encrypt and decrypt signals between, for example, motherboard 818 and modular boards 1925. Securing data module 1980 may determine if a module board communicable with motherboard 818 is an authentic (i.e., non-counterfeit, non-pirated, etc.) modular board 1925. Further, securing data module 1980 may encrypt and decrypt transmissions between motherboard 818 and external devices. In some embodiments, securing data module 1980 is contained in modular board 1925. In this way, different encryptions and security protocols can be selectively employed by modular thermostat 600. In some applications, securing data module 1980 may be certified (e.g., by a government agency, etc.) for use in certain applications. Analyzing data module 1990 may independently determine interactions between modular thermostat 600 and, for example, surrounding building management systems. In one example, a user programs modular thermostat 600 to maintain a target set point temperature. Analyzing data module 1990 may analyze temperature readings from temperature board 828 and then adjust various building management system components to achieve the target set point temperature.
According to the embodiment shown in
Collectively, processing board 1910, networking board 820, occupancy detection board 822, humidity board 824, NFC board 826, temperature board 828, the energy harvesting board 830, and battery board 832 are referred to as the “modular boards” or, can individually be generally referred to as a “modular board” where the type of modular board 1925 may be selected from the foregoing list of modular boards 1925. Collectively, memory 1820, memory 1822, memory 1824, memory, 1826, memory 1828, memory 1830, memory 1834, and memory 1930, if applicable, is referred to as “the memory.” The memory may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memory may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memory may be communicably connected to processor 702 via processing circuit and may include computer code for executing (e.g., by processor 702) one or more processes described herein. When processor 702 executes instructions stored in the memory for completing the various activities described herein, processor 702 generally configures modular thermostat 600 (and more particularly processing circuit) to complete such activities.
Any of the modular boards 1925, the hardware interface 808, display 802, receiving bay 836, and modular thermostat 600 may optionally include a processing circuit. For example, as shown in
Each modular board 1925 may perform a different thermostat function or may provide modular thermostat 600 with the ability to perform a different thermostat function. Thermostat functions may be broadly defined as operations performed by any of modular boards 1925 as described herein. Each of processing board 1910, networking board 820, occupancy detection board 822, humidity board 824, NFC board 826, temperature board 828, the energy harvesting board 830, and battery board 832 may perform various thermostat functions or provide various thermostat functions to modular thermostat 600.
For example, processing board 1910 may perform the thermostat functions of processing data, storing data, transmitting data, analyzing data, adaptively reconfiguring user interface 406, and other similar functions. In another example, networking board 820 may perform the thermostat functions of communicating (e.g., transmitting information to, receiving information from, etc.) with an external device (e.g., an intermediate device, a BAS, another modular thermostat, etc.) and other similar functions. Occupancy detection board 822 may perform the thermostat functions of determining an occupancy in a target location (e.g., room, building, zone, etc.), tracking of individuals (e.g., tracking of a target individual, etc.), transmitting occupancy information, analyzing recorded occupancy information (e.g., to determine thermal loads from occupants, etc.), and other similar functions.
In one example, humidity board 824 performs the thermostat functions of measuring humidity in a target location (e.g., room, building, zone, etc.), analyzing humidity data, transmitting humidity data, determining other variables (e.g., temperature, occupancy, etc.) based on humidity data, and other similar functions. NFC board 826 may perform the thermostat functions of facilitate communication with another device over NFC. For example, NFC board 826 may perform the thermostat functions of receiving information over NFC, transmitting information over NFC, preparing transmission for transmission over NFC, and other similar functions. In some examples, temperature board 828 performs the thermostat functions of measuring temperature in a target location (e.g., room, building, zone, etc.), analyzing temperature data, transmitting temperature data, determining other variables (e.g., humidity, occupancy, etc.) based on temperature data, and other similar functions. Energy harvesting board 830 may perform the thermostat functions of harvesting energy from a location (e.g., room, building, zone, etc.), analyzing harvest energy (e.g., voltage, current, efficiency, etc.), identifying energy sources (e.g., rooms, buildings, zones, etc.) suitable for energy harvesting, providing harvested energy to modular thermostat 600, providing harvested energy to the BAS, and other similar functions. In some examples, battery board 832 may perform the thermostat functions of providing electrical energy to modular boards 1925 and modular thermostat 600, determining an amount of remaining electrical energy available to modular boards 1925 and modular thermostat 600, providing an active or passive back-up system for modular boards 1925 and modular thermostat 600, and other similar functions.
As shown in
Next, modular board recognizer 1920 reconfigures equipment model 1922 (e.g., changes the variable defined by equipment model 1922, etc.). Modular board recognizer 1920 requests, in step 2030, an equipment model update from memory 1930, the equipment model update corresponding to the signal received from modular board 1925. According to process 2000, memory 1930 contains a library of various equipment model updates for various modular boards 1925 sorted by, for example, identification, type, attributes, capabilities, and configuration information. This library may be updated periodically, such as through the use of networking board 820. In step 2040, memory 1930 identifies the equipment model update based on at least a portion of the signal and transmits the equipment model update to modular board recognizer 1920. Modular board recognizer 1920, in step 2050, then updates equipment model 1922 based on the equipment model update. Updating equipment model 1922 may include deleting or overwriting obsolete information, such as that corresponding to modular boards 1925 that were removed from modular thermostat 600. After step 2050, process 2000 is complete and modular thermostat 600 is fully capable of interacting with the BAS using modular board 1925.
As shown in
In some implementations of process 2100, modular board recognizer 1920 may request an equipment model update from memory 1930, in step 2030. For example, memory 1930 may be configured to have several pre-loaded equipment model updates. If memory 1930 contains the requested equipment model update, process 2100, similar to process 2000, proceeds with step 2040 and step 2050. However, in the event that memory 1930 does not contain the requested equipment model update, memory 1930 may transmit, in step 2110, a signal to modular board recognizer 1920 indicating that the requested equipment model update was not found.
In step 2120, modular board recognizer 1920 requests the equipment model update from external device 2102. External device 2102 may include a memory 2104 that contains a library of various equipment model updates for various modular boards 1925 sorted by, for example, identification, type, attributes, capabilities, and configuration information. This library may be updated periodically, for example, as new (e.g., new models, new version, etc.) modular boards 1925 are produced or as new features (e.g., new firmware, etc.) are released for existing modular boards 1925. In some implementations, process 2100 moves directly from step 2020 to step 2120. In these implementations, memory 1930 may not contain any equipment model updates. This may allow memory 1930 to operate more efficiently. In step 2130, the external device identifies the requested equipment model update and transmits the equipment model update to the modular board recognizer 1920. Process 2100 concludes with step 2050 as previously described.
As shown in
In some implementations of process 2200, step 2030 and step 2110 are performed as described in process 2100. In step 2210, modular board recognizer 1920 requests the equipment model update from intermediate device 2202. This may cause a notification (e.g., prompt, message, image, etc.) to be pushed to the intermediate device. For example, a user may be requested to open an application (e.g., configuration application, etc.) associated with modular thermostat 600. In some implementations, step 2210 may occur via NFC, Bluetooth, Bluetooth low-energy, and other similar communication protocols. In step 2220, intermediate device 2202 routes the request to external device 2102. In some applications, step 2220 includes utilizing intermediate device 2202 to retransmit the request to external device 2102. In step 2230, external device 2102 identifies the requested equipment model update and transmits the equipment model update back to intermediate device 2202. Then, in step 2240, intermediate device 2202 routes the equipment model update back to modular board recognizer 1920. Similarly to process 2100, process 2200 concludes with step 2050 as previously described.
After the information from the old modular board 1925 is copied to external device 2102, the user places a new modular board 1925 proximate external device 2102 and, in step 2330, external device 2102 transmits the copied information to the new modular board 1925. For example, in the step 2330, the user may utilize an application on a smart phone and select a “Transfer Mode” within the application. The transfer of information to the new modular board 1925 may be accomplished over the same or similar communication protocols described for step 2320. Typically, process 2300 terminates with the user inserting (e.g., connecting, coupling, etc.) the new modular board 1925 in modular thermostat 600. In some implementations of process 2300, step 2310 and/or step 2340 is eliminated and step 2320 and/or step 2330 occur while the modular board 1925 is in modular thermostat 600. For example, in step 2320, information may be copied from an old modular board 1925 while the old modular board 1925 is still inside modular thermostat 600. This may allow modular board 1925 to utilize various capabilities of modular thermostat 600 to facilitate information transfer to and from external device 2102. For example, modular board 1925 may receive electrical power from modular thermostat 600 that modular board 1925 may utilize to power communications devices that facilitate communication with external device 2102.
In some applications, process 2300 is implemented in conjunction with process 2000, process 2100, and/or process 2200. In this way, settings may be “cloned” from an old modular board 1925 to a new modular board 1925 and the equipment model 1922 may be dynamically updated with the capabilities of the new modular board 1925. In other applications, process 2300 may be implemented without any of process 200, process 2100, and/or process 2200. For example, if a new modular board 1925 has the same capabilities as an old modular board 1925 that it is replacing, there may only be a need to copy information to the new modular board 1925 and no need to update equipment model 1922. Similarly, equipment model 1922 may need to be updated (e.g., via process 2000, via process 2100, via process 220, etc.) when an old modular board 1925 is replaced with a new modular board 1925 without the need to copy information from the old modular board 1925 to the new modular board 1925. For example, equipment model 1922 may be updated such that the information for the new modular board 1925 is built into equipment model 1922.
Now referring to
Memory 704 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. Memory 704 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 704 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 704 may be communicably connected to processor 702 via processing circuit 134 and may include computer code for executing (e.g., by processor 702) one or more processes described herein. When processor 702 executes instructions stored in memory 704 for completing the various activities described herein, processor 702 generally configures modular thermostat 600 (and more particularly processing circuit 608) to complete such activities.
Memory 704 is shown to include data analyzer 712 and system analyzer 714. However, according to some embodiments, processing circuit 608 may not include data analyzer 712 or system analyzer 714. It is to be understood that depending on the implementation of the processing circuit (e.g., on a particular modular board), that memory 704 may include additional devices specific to that implementation. For example, a processing circuit included on the occupancy detection board 822 may have a memory that includes occupancy detector, occupancy identifier, occupancy predictor, and voice recognition modular devices.
Processing circuit 608 is also shown to include a data logger 720. However, according to some embodiments, processing circuit 608 may not include data logger 720. System 700 is shown to include remote data storage 718. Data logger 720 may record data in memory 704. In some embodiments, processing circuit 608 may store data in remote data storage 718. While storing data locally may reduce access time, the cost of providing suitable storage space may discourage user adoption.
Referring now to
Equipment model 1922 defines corresponding BACnet objects 2600, view definitions, schedules, trends, and the associated value objects (e.g., analog value, binary value, multistate value, etc.) that are used for integration with other systems. Equipment model 1922 can include a collection of point objects that provide information about modular thermostat 600 (e.g., location of modular thermostat 600, network address of modular thermostat 600, model number of modular thermostat 600, etc.) and store present values of variables or parameters used by modular thermostat 600 as attributes of equipment model 1922. For example, equipment model 1922 can include point objects that store the values of input variables accepted by modular thermostat 600 (e.g., setpoint, control parameters, etc.), output variables provided by modular thermostat 600 (e.g., temperature measurements, occupancy measurements, feedback signals, etc.), configuration parameters used by modular thermostat 600 (e.g., operating mode, user settings, tuning parameters, etc.). The point objects in equipment model 1922 can be mapped to variables or parameters stored within modular thermostat 600 to expose those variables or parameters to external systems or devices in the BAS.
In
As shown in
In
By updating equipment model 1922, modular thermostat 600 may interact differently with the BAS via BACnet objects 2600. As shown in
Temperature and Humidity Boards
In some embodiments, modular thermostat 600 includes temperature board 828. Temperature board 828 may be configured to monitor the temperature of a space through internal thermal sensors 1995 included on temperature board 828 or through externally mounted thermal sensors 1995. Both internal and external thermal sensors 1995 could be either contact or non-contact sensors. For example, contact sensors such a thermocouples, thermistors, resistance thermometers, liquid in glass thermometers, filled system thermometers, semiconductor temperature sensors, and other suitable sensors may be used. In addition, thermal imaging of a space could be performed and the image could be analyzed to determine a temperature of the space. For example, in an embodiment where modular thermostat 600 included at least temperature board 828 and networking board 820, several external thermal sensors 1995 could be set up within a space. In this example, the external thermal sensors 1995 could wirelessly, or through the use of wires, relay information back to modular thermostat 600.
According to various embodiments, modular thermostat 600 may also include humidity board 824. Humidity board 824 would operate in a manner similar to temperature board 828, substituting humidity for temperature. In some embodiments, humidity board 824 of modular thermostat 600 may control, vary, measure, and sense humidity, and operate in a manner similar to that of temperature board 828.
Networking Board
In some embodiments, modular thermostat 600 includes a networking board 820. Networking board 820 may enable modular thermostat 600 to connect to various other devices, to various other modular thermostats 600, the internet, a satellite network, a cellular network (e.g., as 3G, 4G, 4G LTE, etc.), Wi-Fi, ZigBee, cloud networks, or other suitable networks, may be desired. In order to provide connectivity, modular thermostat 600 may include networking board 820. Networking board 820 may include wireless internet, Bluetooth, infrared, radio, and other communications antennas. In addition, networking board 820 may allow modular thermostat 600 to connect to a network with other appliances, computers, and electronic devices. In some embodiments, networking board 820 may permit interconnectivity of multiple modular thermostats 600. Networking board 820 may also allow modular thermostat 600 to be capable of bi-directional communication with equipment through a data communications interface. In some embodiments, modular thermostat 600 may be able to communicate directly with devices. In the forthcoming disclosure, it is understood that if the modular thermostat 600 is said to “connect,” “communicate,” or otherwise interact with a system, device, or service, that modular thermostat 600 either connects directly (i.e., through a wire), or through the use of networking board 820.
According to these embodiments, the interconnected modular thermostats 600 may all be controlled by a central controller. Alternatively, modular thermostats 600 may be configured to be individually controlled but are configured to upload data to a central source. This central source could provide data logging for a wide range of modular thermostats 600 and could provide post-processing analysis of the entire data source that may be useful for users to optimize HVAC operations. Additionally, this post processing analysis could provide a useful tool to help users determine which modular thermostats 600 may benefit from a modular board 1925 upgrade, which modular board 1925 to upgrade, and what the estimated benefits of that upgrade would be. The post processing analysis may also allow users to determine HVAC system performance and may inform the user of, for example, suggested maintenance. According to some embodiments, networking board 820 may allow modular thermostat 600 to store data on a cloud network, rather than on-board memory such as that provided by motherboard 818 or processing circuit.
Networking board 820 may allow modular thermostat 600 to communicate via the internet. In some embodiments, a network-based application may be used instead of a web-based application, and may allow users to control modular thermostat 600 through any device which is connected to a local area network (LAN), regardless of Internet connectivity.
Through the use of networking board 820, modular thermostat 600 may be capable of communicating with a variety of devices, such as light system, refrigerator, security system, blinds or windows, door, fitness tracker or other wearable, either directly or through an intermediary. Modular thermostat 600 may also communicate directly with connected HVAC equipment. Modular thermostat 600 may also communicate with services such as a weather service, utility provider, network, or server. In some embodiments, networking board 820 of modular thermostat 600 communicates with devices through a router to which the devices are connected. In other embodiments, networking board 820 modular thermostat 600 communicates with devices through the network with which the devices are connected. User-owned portable electronic devices with which modular thermostat 600 through networking board 820 may communicate include devices, laptops, or tablets. It is to be understood that the resources with which modular thermostat 600 through networking board 820 is shown to be connected are not meant to be limiting, and that modular thermostat 600 through networking board 820 may be connected with any number of devices, services, and systems. Communication may occur over any of a number of protocols; for example, communication may occur over wired or wireless venues.
Networking board 820 may receive data from a weather service, as mentioned previously. In some embodiments, modular thermostat 600 may show the forecast on display 802. Networking board 820 may be able to send the forecast to a user's phone on a schedule or upon check-in with modular thermostat 600.
Networking board 820 may communicate with commercial storage solutions such as Dropbox, Google Docs, or Amazon Cloud. Networking board 820 may store data in such places in order to record trends and make data and analytic reports more accessible to users. Storing data in places other than local memory will also reduce the cost of modular thermostat 600 as a unit and promote sales.
Networking board 820 may communicate with the network to receive firmware updates. In some embodiments, the firmware updates are for connected equipment. For example, modular thermostat 600 may receive a notification that the AC unit has an available firmware update. Modular thermostat 600 may show a prompt on display 802 with a message such as: “A firmware update is available for your AC unit. Would you like to call your dealer to schedule a space visit?”
Networking board 820 may communicate with a user's utility provider. System performance data may be integrated with utility data in order to monitor a space's level of energy usage and inform users of their usage habits.
In some alternative embodiments, networking board 820 may facilitate connection with radio frequency identification (RFID) beacons. Through this connection, networking board 820 may identify locations of RFID beacons and provide the locations to modular thermostat 600. In this way, networking board 820 may facilitate tracking of the beacons (e.g., inventory tracking, patient tracking, etc.).
Occupancy Detection Board
In some embodiments, modular thermostat 600 includes an occupancy detection board 822. Occupancy detection board 822 adds further capabilities to modular thermostat 600, such as the ability to detect occupancy of the space in which modular thermostat 600 is located. In some embodiments, the occupancy detection board 822 may allow modular thermostat 600 to dynamically adjust the temperature of the space depending on the number of people in the space. The occupancy detection board 822 may include a number of sensors to determine the number of people in the space. According to some embodiments, the sensors may be motion sensors, thermal sensors, carbon dioxide (CO2) sensors, cameras, microphones, capacitive sensors, or any number of other sensors suitable for detecting a person or a number of people in a space. According to some embodiments, the sensors may be cameras which detect heat signatures. According to other embodiments, the sensors may detect separate objects and distinguish between people and other objects. In some embodiments, the sensors could be any suitable transducer which detects some characteristic of their respective environment and surroundings. In one embodiment, occupancy detection board 822 is coupled to a CO2 sensor that determines the amount of CO2 in a given environment and occupancy detection board 822 correlates that amount of CO2 to an occupancy of the environment.
According to some embodiments, occupancy detection board 822 may internally process data received from the sensors to determine whether occupancy has been detected. According to other embodiments, occupancy detection board 822 may utilize an external processor 702, such as that on motherboard 818, receiving bay 836, processing board 1910, a different modular board 1925, or externally through networking board 820. The memory 1822 of occupancy detection board 822 may include an occupancy identifier which is configured to process occupancy data collected to determine which user or users are in a space. The memory 1822 of occupancy detection board 822 may include an occupancy predictor which is configured to process calendar and scheduling data to determine when a user or users will be in a space, and the estimated demands of the HVAC system for the corresponding situation.
Determining the occupancy of a space allows modular thermostat 600 to make energy efficient operating decisions by reducing conditioning and power consumption when a space is unoccupied. User comfort may be increased when modular thermostat 600 is able to anticipate occupancy and condition the space to user preferences by the time the space is occupied. Occupancy based operation and control of an HVAC system allows users to conserve energy while adjusting a space to a comfortable environment without requiring a large amount of effort on the part of the user.
NFC Board
In some embodiments, modular thermostat 600 includes a NFC board 826. NFC board 826 enables modular thermostat 600 to communicate via NFC. Modular thermostat 600 may be able to base control and operation decisions on data obtained through near field communication (NFC). For example, a user may bring a personal electronic device within range of an NFC on NFC board 826. Modular thermostat 600 may receive identifying information through NFC. This information may include preferred settings for modular thermostat 600. Upon authentication and identification of the user through the electronic device, modular thermostat 600 may be receptive to commands. In some embodiments, modular thermostat 600 may provide an audible indication that the scan has occurred. For example, modular thermostat 600 may beep to let users know that scanning has been completed. In other embodiments, modular thermostat 600 may provide visual feedback that scanning has occurred. For example, modular thermostat 600 may flash display. In another embodiment modular thermostat 600 may communicate to the device to provide an indication, such as beeping, flashing, or vibrating, that scanning has occurred. Modular thermostat 600 may alert the user that scanning has occurred in any number of ways not limited to those enumerated. Upon receiving a command via NFC, modular thermostat 600 may transmit the command to connected equipment.
In some embodiments, modular thermostat 600 may automatically execute commands communicated through NFC. Users may be able to queue commands to modular thermostat 600 on their electronic device and transmit them through the use of NFC. In some embodiments, a user may send commands directly through user interface 406. In other embodiments, a user may send commands through the electronic device.
Energy Harvesting Board
Modular thermostat 600 may further include an energy harvesting board 830. In some embodiments, it may desirable for modular thermostat 600 to provide an energy harvesting (e.g., power harvesting, energy scavenging, etc.) capability. In particular, as energy harvesting technology advances and becomes more efficient, there will be many applications where integrating energy harvesting capabilities directly within the modular thermostat 600 is desirable. Energy harvesting board 830 may be inserted into modular thermostat 600 in a manner similar to the other modular boards 1925. Energy harvesting board 830 may be configured to harvest energy from solar power, wind energy, salinity gradients, kinetic energy, and other suitable external sources.
Energy harvesting board 830 may include any number of storage modules such as capacitors, super capacitors, and batteries. In some embodiments, energy harvesting board 830 may be configured to store energy on another modular board 1925 such as, for example, battery board 832. In some embodiments, energy harvesting board 830 may further include wireless transmitters for wirelessly communicating with other devices, or for transmitting power to various devices. In some embodiments, energy harvesting board 830 may be configured to communicate with networking board 820 to transmit energy from energy harvesting board 830, through modular thermostat 600, and from networking board 820 to various devices. In still other embodiments, energy harvesting board 830 may be configured to store energy on battery board 832, and networking board 820 may be configured to draw energy from battery board 832 and transmit that energy to various devices.
Battery Board
Modular thermostat 600 may further include battery board 832. Battery board 832 may be configured to provide energy to any number of modular boards 1925, sensors, external loads, internal components, or other suitable electrical loads. Battery board 832 may include a memory, a processor 702, a number of battery cells, a number of current sensors, a number of voltage sensors, a number of impedance sensors, and other suitable electrical components and hardware. Battery board 832 may include any type of battery cells such as alkaline, aluminum-air, aluminum ion, atomic, chromic acid, galvanic, lithium, lithium air, mercury, molten salt, nickel oxyhydroxide, oxyride, silver-oxide, solid-state, zinc-air, zinc-carbon, zinc-chloride, lead-acid, nickel-cadmium, nick-zinc, and other suitable battery cells may be used. In some embodiments, capacitors may be included with battery board 832, in addition to or in place of, the battery cells.
Battery board 832 may be configured to provide energy to modular thermostat 600 during routine operation, or in a backup-power mode. In some embodiments, when a failure of the surrounding power grid that modular thermostat 600 is connected to occurs, battery board 832 may provide energy to modular thermostat 600 the connection to the surrounding power grid has been reestablished. In some embodiments, battery board 832 may be configured to be constantly connected to modular thermostat 600 such that, in the event that a failure of the surrounding power grid occurs, battery board 832 will provide a coherent transition from the surrounding power grid to battery board 832. In some applications, such as medical, scientific, and engineering applications, it may be critical that modular thermostat 600 does not lose power. By utilizing the coherent transition, modular thermostat 600 may never lose power.
Battery board 832 may be configured to include wireless transmitters for communicating with other devices and/or modular boards 1925. Battery board 832 may be configured to wireless transmit energy to various devices. In some embodiments, battery board 832 may be in communication with energy harvesting board 830.
Configuration of Exemplary Embodiments
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors 702, or by a special purpose computer processor 702 for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with processor 702. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with processor 702. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62/260,141, filed Nov. 25, 2015, the entire disclosure of which is incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4107464 | Lynch et al. | Aug 1978 | A |
| 4942613 | Lynch | Jul 1990 | A |
| 5052186 | Dudley et al. | Oct 1991 | A |
| 5062276 | Dudley | Nov 1991 | A |
| 5797729 | Rafuse et al. | Aug 1998 | A |
| 6121885 | Masone et al. | Sep 2000 | A |
| 6164374 | Rhodes et al. | Dec 2000 | A |
| 6169937 | Peterson | Jan 2001 | B1 |
| 6227961 | Moore et al. | May 2001 | B1 |
| 6260765 | Natale et al. | Jul 2001 | B1 |
| 6314750 | Ishikawa et al. | Nov 2001 | B1 |
| 6351693 | Monie et al. | Feb 2002 | B1 |
| 6435418 | Toth et al. | Aug 2002 | B1 |
| 6487869 | Sulc et al. | Dec 2002 | B1 |
| 6557771 | Shah | May 2003 | B2 |
| 6641054 | Morey | Nov 2003 | B2 |
| 6726112 | Ho | Apr 2004 | B1 |
| 6726113 | Guo | Apr 2004 | B2 |
| 6810307 | Addy | Oct 2004 | B1 |
| 6824069 | Rosen | Nov 2004 | B2 |
| 6851621 | Wacker et al. | Feb 2005 | B1 |
| 6874691 | Hildebrand et al. | Apr 2005 | B1 |
| 6888441 | Carey | May 2005 | B2 |
| 6995518 | Havlik et al. | Feb 2006 | B2 |
| 7028912 | Rosen | Apr 2006 | B1 |
| 7083109 | Pouchak | Aug 2006 | B2 |
| 7099748 | Rayburn | Aug 2006 | B2 |
| 7140551 | De Pauw et al. | Nov 2006 | B2 |
| 7146253 | Hoog et al. | Dec 2006 | B2 |
| 7152806 | Rosen | Dec 2006 | B1 |
| 7156317 | Moore | Jan 2007 | B1 |
| 7156318 | Rosen | Jan 2007 | B1 |
| 7159789 | Schwendinger et al. | Jan 2007 | B2 |
| 7159790 | Schwendinger et al. | Jan 2007 | B2 |
| 7167079 | Smyth et al. | Jan 2007 | B2 |
| 7188002 | Chapman et al. | Mar 2007 | B2 |
| 7212887 | Shah et al. | May 2007 | B2 |
| 7225054 | Amundson et al. | May 2007 | B2 |
| 7232075 | Rosen | Jun 2007 | B1 |
| 7261243 | Butler et al. | Aug 2007 | B2 |
| 7274972 | Amundson et al. | Sep 2007 | B2 |
| 7287709 | Proffitt et al. | Oct 2007 | B2 |
| 7296426 | Butler et al. | Nov 2007 | B2 |
| 7299996 | Garrett et al. | Nov 2007 | B2 |
| 7306165 | Shah | Dec 2007 | B2 |
| 7308384 | Shah et al. | Dec 2007 | B2 |
| 7317970 | Pienta et al. | Jan 2008 | B2 |
| 7331187 | Kates | Feb 2008 | B2 |
| 7343751 | Kates | Mar 2008 | B2 |
| 7383158 | Krocker et al. | Jun 2008 | B2 |
| 7402780 | Mueller et al. | Jul 2008 | B2 |
| 7434744 | Garozzo et al. | Oct 2008 | B2 |
| 7442012 | Moens | Oct 2008 | B2 |
| 7469550 | Chapman et al. | Dec 2008 | B2 |
| 7475558 | Perry | Jan 2009 | B2 |
| 7475828 | Bartlett et al. | Jan 2009 | B2 |
| 7556207 | Mueller et al. | Jul 2009 | B2 |
| 7565813 | Pouchak | Jul 2009 | B2 |
| 7575179 | Morrow et al. | Aug 2009 | B2 |
| 7584897 | Schultz et al. | Sep 2009 | B2 |
| 7592713 | Bryan | Sep 2009 | B2 |
| 7614567 | Chapman et al. | Nov 2009 | B2 |
| 7624931 | Chapman et al. | Dec 2009 | B2 |
| 7633743 | Barton et al. | Dec 2009 | B2 |
| 7636604 | Bergman et al. | Dec 2009 | B2 |
| 7638739 | Rhodes et al. | Dec 2009 | B2 |
| 7641126 | Schultz et al. | Jan 2010 | B2 |
| 7645158 | Mulhouse et al. | Jan 2010 | B2 |
| 7667163 | Ashworth et al. | Feb 2010 | B2 |
| 7726581 | Naujok et al. | Jun 2010 | B2 |
| 7731096 | Lorenz et al. | Jun 2010 | B2 |
| 7731098 | Butler et al. | Jun 2010 | B2 |
| 7740184 | Schnell et al. | Jun 2010 | B2 |
| 7748225 | Butler et al. | Jul 2010 | B2 |
| 7748639 | Perry | Jul 2010 | B2 |
| 7748640 | Roher et al. | Jul 2010 | B2 |
| 7755220 | Sorg et al. | Jul 2010 | B2 |
| 7765826 | Nichols | Aug 2010 | B2 |
| 7774102 | Butler et al. | Aug 2010 | B2 |
| 7775452 | Shah et al. | Aug 2010 | B2 |
| 7784291 | Butler et al. | Aug 2010 | B2 |
| 7784704 | Harter | Aug 2010 | B2 |
| 7802618 | Simon et al. | Sep 2010 | B2 |
| 7832221 | Wijaya et al. | Nov 2010 | B2 |
| 7832652 | Barton et al. | Nov 2010 | B2 |
| 7845576 | Siddaramanna et al. | Dec 2010 | B2 |
| 7861941 | Schultz et al. | Jan 2011 | B2 |
| 7867646 | Rhodes | Jan 2011 | B2 |
| 7908116 | Steinberg et al. | Mar 2011 | B2 |
| 7908117 | Steinberg et al. | Mar 2011 | B2 |
| 7918406 | Rosen | Apr 2011 | B2 |
| 7938336 | Rhodes et al. | May 2011 | B2 |
| 7941294 | Shahi et al. | May 2011 | B2 |
| 7954726 | Siddaramanna et al. | Jun 2011 | B2 |
| 7963454 | Sullivan et al. | Jun 2011 | B2 |
| 7979164 | Garozzo et al. | Jul 2011 | B2 |
| 7992794 | Leen et al. | Aug 2011 | B2 |
| 8010237 | Cheung et al. | Aug 2011 | B2 |
| 8032254 | Amundson et al. | Oct 2011 | B2 |
| 8078326 | Harrod et al. | Dec 2011 | B2 |
| 8082065 | Imes et al. | Dec 2011 | B2 |
| 8083154 | Schultz et al. | Dec 2011 | B2 |
| 8089032 | Beland et al. | Jan 2012 | B2 |
| 8091794 | Siddaramanna et al. | Jan 2012 | B2 |
| 8099195 | Imes et al. | Jan 2012 | B2 |
| 8108076 | Imes et al. | Jan 2012 | B2 |
| 8131506 | Steinberg et al. | Mar 2012 | B2 |
| 8141791 | Rosen | Mar 2012 | B2 |
| 8167216 | Schultz et al. | May 2012 | B2 |
| 8180492 | Steinberg | May 2012 | B2 |
| 8190296 | Alhilo | May 2012 | B2 |
| 8195313 | Fadell et al. | Jun 2012 | B1 |
| 8196185 | Geadelmann et al. | Jun 2012 | B2 |
| 8209059 | Stockton | Jun 2012 | B2 |
| 8239066 | Jennings et al. | Aug 2012 | B2 |
| 8276829 | Stoner et al. | Oct 2012 | B2 |
| 8280536 | Fadell et al. | Oct 2012 | B1 |
| 8289182 | Vogel et al. | Oct 2012 | B2 |
| 8289226 | Takach et al. | Oct 2012 | B2 |
| 8299919 | Dayton et al. | Oct 2012 | B2 |
| 8321058 | Zhou et al. | Nov 2012 | B2 |
| 8346396 | Amundson et al. | Jan 2013 | B2 |
| 8387891 | Simon et al. | Mar 2013 | B1 |
| 8393550 | Simon et al. | Mar 2013 | B2 |
| 8412488 | Steinberg et al. | Apr 2013 | B2 |
| 8429566 | Koushik et al. | Apr 2013 | B2 |
| 8456293 | Trundle et al. | Jun 2013 | B1 |
| 8473109 | Imes et al. | Jun 2013 | B1 |
| 8476964 | Atri | Jul 2013 | B1 |
| 8489243 | Fadell et al. | Jul 2013 | B2 |
| 8504180 | Imes et al. | Aug 2013 | B2 |
| 8510255 | Fadell et al. | Aug 2013 | B2 |
| 8511576 | Warren et al. | Aug 2013 | B2 |
| 8511577 | Warren et al. | Aug 2013 | B2 |
| 8517088 | Moore et al. | Aug 2013 | B2 |
| 8523083 | Warren et al. | Sep 2013 | B2 |
| 8523084 | Siddaramanna et al. | Sep 2013 | B2 |
| 8527096 | Pavlak et al. | Sep 2013 | B2 |
| 8532827 | Stefanski et al. | Sep 2013 | B2 |
| 8544285 | Stefanski et al. | Oct 2013 | B2 |
| 8549658 | Kolavennu et al. | Oct 2013 | B2 |
| 8550368 | Butler et al. | Oct 2013 | B2 |
| 8554374 | Lunacek et al. | Oct 2013 | B2 |
| 8555662 | Peterson et al. | Oct 2013 | B2 |
| 8558179 | Filson et al. | Oct 2013 | B2 |
| 8560127 | Leen et al. | Oct 2013 | B2 |
| 8560128 | Ruff et al. | Oct 2013 | B2 |
| 8571518 | Imes et al. | Oct 2013 | B2 |
| 8594850 | Gourlay | Nov 2013 | B1 |
| 8596550 | Steinberg et al. | Dec 2013 | B2 |
| 8600564 | Imes et al. | Dec 2013 | B2 |
| 8606409 | Amundson et al. | Dec 2013 | B2 |
| 8613792 | Ragland et al. | Dec 2013 | B2 |
| 8620841 | Filson et al. | Dec 2013 | B1 |
| 8622314 | Fisher et al. | Jan 2014 | B2 |
| 8626344 | Imes et al. | Jan 2014 | B2 |
| 8630741 | Matsuoka et al. | Jan 2014 | B1 |
| 8630742 | Stefanski et al. | Jan 2014 | B1 |
| 8644009 | Rylski et al. | Feb 2014 | B2 |
| 8659302 | Warren et al. | Feb 2014 | B1 |
| 8671702 | Shotey et al. | Mar 2014 | B1 |
| 8674816 | Trundle et al. | Mar 2014 | B2 |
| 8689572 | Evans et al. | Apr 2014 | B2 |
| 8695887 | Helt et al. | Apr 2014 | B2 |
| 8706270 | Fadell et al. | Apr 2014 | B2 |
| 8708242 | Conner et al. | Apr 2014 | B2 |
| 8712590 | Steinberg | Apr 2014 | B2 |
| 8718826 | Ramachandran et al. | May 2014 | B2 |
| 8726680 | Schenk et al. | May 2014 | B2 |
| 8727611 | Huppi et al. | May 2014 | B2 |
| 8738327 | Steinberg et al. | May 2014 | B2 |
| 8746583 | Simon et al. | Jun 2014 | B2 |
| 8752771 | Warren et al. | Jun 2014 | B2 |
| 8754780 | Petite et al. | Jun 2014 | B2 |
| 8766194 | Filson et al. | Jul 2014 | B2 |
| 8770490 | Drew | Jul 2014 | B2 |
| 8770491 | Warren et al. | Jul 2014 | B2 |
| 8788103 | Warren et al. | Jul 2014 | B2 |
| 8802981 | Wallaert et al. | Aug 2014 | B2 |
| 8830267 | Brackney | Sep 2014 | B2 |
| 8838282 | Ratliff et al. | Sep 2014 | B1 |
| 8843239 | Mighdoll et al. | Sep 2014 | B2 |
| 8850348 | Fadell et al. | Sep 2014 | B2 |
| 8855830 | Imes et al. | Oct 2014 | B2 |
| 8868219 | Fadell et al. | Oct 2014 | B2 |
| 8870086 | Tessier et al. | Oct 2014 | B2 |
| 8870087 | Pienta et al. | Oct 2014 | B2 |
| 8880047 | Konicek et al. | Nov 2014 | B2 |
| 8893032 | Bruck et al. | Nov 2014 | B2 |
| 8903552 | Amundson et al. | Dec 2014 | B2 |
| 8918219 | Sloo et al. | Dec 2014 | B2 |
| 8942853 | Stefanski et al. | Jan 2015 | B2 |
| 8944338 | Warren et al. | Feb 2015 | B2 |
| 8950686 | Matsuoka et al. | Feb 2015 | B2 |
| 8950687 | Bergman et al. | Feb 2015 | B2 |
| 8961005 | Huppi et al. | Feb 2015 | B2 |
| 8978994 | Moore et al. | Mar 2015 | B2 |
| 8998102 | Fadell et al. | Apr 2015 | B2 |
| 9014686 | Ramachandran et al. | Apr 2015 | B2 |
| 9014860 | Moore et al. | Apr 2015 | B2 |
| 9020647 | Johnson et al. | Apr 2015 | B2 |
| 9026232 | Fadell et al. | May 2015 | B2 |
| 9033255 | Tessier et al. | May 2015 | B2 |
| RE45574 | Harter | Jun 2015 | E |
| 9074784 | Sullivan et al. | Jul 2015 | B2 |
| 9075419 | Sloo et al. | Jul 2015 | B2 |
| 9077055 | Yau | Jul 2015 | B2 |
| 9080782 | Sheikh | Jul 2015 | B1 |
| 9081393 | Lunacek et al. | Jul 2015 | B2 |
| 9086703 | Warren et al. | Jul 2015 | B2 |
| 9088306 | Ramachandran et al. | Jul 2015 | B1 |
| 9092039 | Fadell et al. | Jul 2015 | B2 |
| 9098279 | Mucignat et al. | Aug 2015 | B2 |
| 9116529 | Warren et al. | Aug 2015 | B2 |
| 9121623 | Filson et al. | Sep 2015 | B2 |
| 9122283 | Rylski et al. | Sep 2015 | B2 |
| 9125049 | Huang et al. | Sep 2015 | B2 |
| 9127853 | Filson et al. | Sep 2015 | B2 |
| 9134710 | Cheung et al. | Sep 2015 | B2 |
| 9134715 | Geadelmann et al. | Sep 2015 | B2 |
| 9146041 | Novotny et al. | Sep 2015 | B2 |
| 9151510 | Leen | Oct 2015 | B2 |
| 9154001 | Dharwada et al. | Oct 2015 | B2 |
| 9157764 | Shetty et al. | Oct 2015 | B2 |
| 9164524 | Imes et al. | Oct 2015 | B2 |
| 9175868 | Fadell et al. | Nov 2015 | B2 |
| 9175871 | Gourlay et al. | Nov 2015 | B2 |
| 9182141 | Sullivan et al. | Nov 2015 | B2 |
| 9189751 | Matsuoka et al. | Nov 2015 | B2 |
| 9191277 | Rezvani et al. | Nov 2015 | B2 |
| 9191909 | Rezvani et al. | Nov 2015 | B2 |
| 9194597 | Steinberg et al. | Nov 2015 | B2 |
| 9194598 | Fadell et al. | Nov 2015 | B2 |
| 9194600 | Kates | Nov 2015 | B2 |
| 9207817 | Tu | Dec 2015 | B2 |
| 9213342 | Drake et al. | Dec 2015 | B2 |
| 9215281 | Iggulden et al. | Dec 2015 | B2 |
| 9222693 | Gourlay et al. | Dec 2015 | B2 |
| 9223323 | Matas et al. | Dec 2015 | B2 |
| 9234669 | Filson et al. | Jan 2016 | B2 |
| 9244445 | Finch et al. | Jan 2016 | B2 |
| 9244470 | Steinberg | Jan 2016 | B2 |
| 9261287 | Warren et al. | Feb 2016 | B2 |
| 9268344 | Warren et al. | Feb 2016 | B2 |
| 9279595 | Mighdoll et al. | Mar 2016 | B2 |
| 9282590 | Donlan | Mar 2016 | B2 |
| 9285134 | Bray et al. | Mar 2016 | B2 |
| 9285802 | Arensmeier | Mar 2016 | B2 |
| 9286781 | Filson et al. | Mar 2016 | B2 |
| 9291359 | Fadell et al. | Mar 2016 | B2 |
| 9292022 | Ramachandran et al. | Mar 2016 | B2 |
| 9298196 | Matsuoka et al. | Mar 2016 | B2 |
| 9298197 | Matsuoka et al. | Mar 2016 | B2 |
| 9319234 | Davis | Apr 2016 | B2 |
| D763707 | Sinha et al. | Aug 2016 | S |
| 9589459 | Davis | Mar 2017 | B2 |
| D790369 | Sinha et al. | Jun 2017 | S |
| 9762408 | Davis | Sep 2017 | B2 |
| 9857238 | Malhotra | Jan 2018 | B2 |
| 9887887 | Hunter et al. | Feb 2018 | B2 |
| 10021801 | Deros | Jul 2018 | B2 |
| 20010015281 | Schiedegger et al. | Aug 2001 | A1 |
| 20030034897 | Shamoon et al. | Feb 2003 | A1 |
| 20030034898 | Shamoon et al. | Feb 2003 | A1 |
| 20030136853 | Morey | Jul 2003 | A1 |
| 20030177012 | Drennan | Sep 2003 | A1 |
| 20040074978 | Rosen | Apr 2004 | A1 |
| 20040125940 | Turcan et al. | Jul 2004 | A1 |
| 20040249479 | Shorrock | Dec 2004 | A1 |
| 20040262410 | Hull | Dec 2004 | A1 |
| 20050040943 | Winick | Feb 2005 | A1 |
| 20050083168 | Breitenbach | Apr 2005 | A1 |
| 20050119794 | Amundson et al. | Jun 2005 | A1 |
| 20050156049 | Van Ostrand et al. | Jul 2005 | A1 |
| 20050194456 | Tessier et al. | Sep 2005 | A1 |
| 20050195757 | Kidder et al. | Sep 2005 | A1 |
| 20050270151 | Winick | Dec 2005 | A1 |
| 20050270735 | Chen | Dec 2005 | A1 |
| 20060038025 | Lee | Feb 2006 | A1 |
| 20060113398 | Ashworth | Jun 2006 | A1 |
| 20060192022 | Barton et al. | Aug 2006 | A1 |
| 20060226970 | Saga et al. | Oct 2006 | A1 |
| 20060260334 | Carey et al. | Nov 2006 | A1 |
| 20070013532 | Ehlers | Jan 2007 | A1 |
| 20070045431 | Chapman et al. | Mar 2007 | A1 |
| 20070050732 | Chapman et al. | Mar 2007 | A1 |
| 20070057079 | Stark et al. | Mar 2007 | A1 |
| 20070114295 | Jenkins | May 2007 | A1 |
| 20070198099 | Shah | Aug 2007 | A9 |
| 20070228182 | Wagner et al. | Oct 2007 | A1 |
| 20070228183 | Kennedy et al. | Oct 2007 | A1 |
| 20070241203 | Wagner et al. | Oct 2007 | A1 |
| 20080015740 | Osann | Jan 2008 | A1 |
| 20080048046 | Wagner et al. | Feb 2008 | A1 |
| 20080054084 | Olson | Mar 2008 | A1 |
| 20080099568 | Nicodem et al. | May 2008 | A1 |
| 20080120446 | Butler et al. | May 2008 | A1 |
| 20080161978 | Shah | Jul 2008 | A1 |
| 20080216495 | Kates | Sep 2008 | A1 |
| 20080223051 | Kates | Sep 2008 | A1 |
| 20080227430 | Polk | Sep 2008 | A1 |
| 20080280637 | Shaffer et al. | Nov 2008 | A1 |
| 20080289347 | Kadle et al. | Nov 2008 | A1 |
| 20080290183 | Laberge et al. | Nov 2008 | A1 |
| 20080294274 | Laberge et al. | Nov 2008 | A1 |
| 20080295030 | Laberge et al. | Nov 2008 | A1 |
| 20090140065 | Juntunen et al. | Jun 2009 | A1 |
| 20090143880 | Amundson et al. | Jun 2009 | A1 |
| 20090143918 | Amundson et al. | Jun 2009 | A1 |
| 20090144015 | Bedard | Jun 2009 | A1 |
| 20090251422 | Wu et al. | Oct 2009 | A1 |
| 20090276096 | Proffitt et al. | Nov 2009 | A1 |
| 20100070092 | Winter et al. | Mar 2010 | A1 |
| 20100084482 | Kennedy et al. | Apr 2010 | A1 |
| 20100131884 | Shah | May 2010 | A1 |
| 20100145536 | Masters et al. | Jun 2010 | A1 |
| 20100163633 | Barrett et al. | Jul 2010 | A1 |
| 20100163635 | Ye | Jul 2010 | A1 |
| 20100171889 | Pantel et al. | Jul 2010 | A1 |
| 20100182743 | Roher | Jul 2010 | A1 |
| 20100190479 | Scott et al. | Jul 2010 | A1 |
| 20100204834 | Comerford et al. | Aug 2010 | A1 |
| 20100212879 | Schnell et al. | Aug 2010 | A1 |
| 20100250707 | Dalley et al. | Sep 2010 | A1 |
| 20110006887 | Shaull et al. | Jan 2011 | A1 |
| 20110067851 | Terlson et al. | Mar 2011 | A1 |
| 20110088416 | Koethler | Apr 2011 | A1 |
| 20110128378 | Raji | Jun 2011 | A1 |
| 20110132991 | Moody et al. | Jun 2011 | A1 |
| 20110181412 | Alexander et al. | Jul 2011 | A1 |
| 20110264279 | Poth | Oct 2011 | A1 |
| 20120001873 | Wu et al. | Jan 2012 | A1 |
| 20120007555 | Bukow | Jan 2012 | A1 |
| 20120048955 | Lin et al. | Mar 2012 | A1 |
| 20120061480 | Deligiannis et al. | Mar 2012 | A1 |
| 20120093141 | Imes et al. | Apr 2012 | A1 |
| 20120095601 | Abraham et al. | Apr 2012 | A1 |
| 20120101637 | Imes et al. | Apr 2012 | A1 |
| 20120126020 | Filson et al. | May 2012 | A1 |
| 20120126021 | Warren et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120165993 | Whitehouse | Jun 2012 | A1 |
| 20120179727 | Esser | Jul 2012 | A1 |
| 20120181010 | Schultz et al. | Jul 2012 | A1 |
| 20120191257 | Corcoran et al. | Jul 2012 | A1 |
| 20120193437 | Henry et al. | Aug 2012 | A1 |
| 20120229521 | Hales et al. | Sep 2012 | A1 |
| 20120230661 | Alhilo | Sep 2012 | A1 |
| 20120239207 | Fadell et al. | Sep 2012 | A1 |
| 20120252430 | Imes et al. | Oct 2012 | A1 |
| 20120259470 | Nijhawan et al. | Oct 2012 | A1 |
| 20120298763 | Young | Nov 2012 | A1 |
| 20120303165 | Qu et al. | Nov 2012 | A1 |
| 20120303828 | Young et al. | Nov 2012 | A1 |
| 20120310418 | Harrod et al. | Dec 2012 | A1 |
| 20120315848 | Smith et al. | Dec 2012 | A1 |
| 20130002447 | Vogel et al. | Jan 2013 | A1 |
| 20130054758 | Imes et al. | Feb 2013 | A1 |
| 20130057381 | Kandhasamy | Mar 2013 | A1 |
| 20130087628 | Nelson et al. | Apr 2013 | A1 |
| 20130090767 | Bruck et al. | Apr 2013 | A1 |
| 20130099008 | Aljabari et al. | Apr 2013 | A1 |
| 20130099009 | Filson et al. | Apr 2013 | A1 |
| 20130123991 | Richmond | May 2013 | A1 |
| 20130138250 | Mowery et al. | May 2013 | A1 |
| 20130144443 | Casson et al. | Jun 2013 | A1 |
| 20130151016 | Bias et al. | Jun 2013 | A1 |
| 20130151018 | Bias et al. | Jun 2013 | A1 |
| 20130158721 | Somasundaram et al. | Jun 2013 | A1 |
| 20130163300 | Zhao et al. | Jun 2013 | A1 |
| 20130180700 | Aycock | Jul 2013 | A1 |
| 20130190932 | Schuman | Jul 2013 | A1 |
| 20130190940 | Sloop et al. | Jul 2013 | A1 |
| 20130204408 | Thiruvengada et al. | Aug 2013 | A1 |
| 20130204441 | Sloo et al. | Aug 2013 | A1 |
| 20130204442 | Modi et al. | Aug 2013 | A1 |
| 20130211600 | Dean-Hendricks et al. | Aug 2013 | A1 |
| 20130215058 | Brazell et al. | Aug 2013 | A1 |
| 20130221117 | Warren et al. | Aug 2013 | A1 |
| 20130228633 | Toth et al. | Sep 2013 | A1 |
| 20130234840 | Trundle et al. | Sep 2013 | A1 |
| 20130238142 | Nichols et al. | Sep 2013 | A1 |
| 20130245838 | Zywicki et al. | Sep 2013 | A1 |
| 20130261803 | Kolavennu | Oct 2013 | A1 |
| 20130261807 | Zywicki et al. | Oct 2013 | A1 |
| 20130268125 | Matsuoka | Oct 2013 | A1 |
| 20130268129 | Fadell et al. | Oct 2013 | A1 |
| 20130271670 | Sakata et al. | Oct 2013 | A1 |
| 20130292481 | Filson et al. | Nov 2013 | A1 |
| 20130297078 | Kolavennu | Nov 2013 | A1 |
| 20130318217 | Imes et al. | Nov 2013 | A1 |
| 20130318444 | Imes et al. | Nov 2013 | A1 |
| 20130325190 | Imes et al. | Dec 2013 | A1 |
| 20130338837 | Hublou et al. | Dec 2013 | A1 |
| 20130338839 | Rogers et al. | Dec 2013 | A1 |
| 20130340993 | Siddaramanna et al. | Dec 2013 | A1 |
| 20130345882 | Dushane et al. | Dec 2013 | A1 |
| 20140000861 | Barrett et al. | Jan 2014 | A1 |
| 20140002461 | Wang | Jan 2014 | A1 |
| 20140031989 | Bergman et al. | Jan 2014 | A1 |
| 20140034284 | Butler et al. | Feb 2014 | A1 |
| 20140039692 | Leen et al. | Feb 2014 | A1 |
| 20140041846 | Leen et al. | Feb 2014 | A1 |
| 20140048608 | Frank | Feb 2014 | A1 |
| 20140052300 | Matsuoka et al. | Feb 2014 | A1 |
| 20140058806 | Guenette et al. | Feb 2014 | A1 |
| 20140070919 | Jackson et al. | Mar 2014 | A1 |
| 20140081466 | Huapeng et al. | Mar 2014 | A1 |
| 20140112331 | Rosen | Apr 2014 | A1 |
| 20140114706 | Blakely | Apr 2014 | A1 |
| 20140117103 | Rossi et al. | May 2014 | A1 |
| 20140118285 | Poplawski | May 2014 | A1 |
| 20140129034 | Stefanski et al. | May 2014 | A1 |
| 20140149270 | Lombard et al. | May 2014 | A1 |
| 20140151456 | McCurnin et al. | Jun 2014 | A1 |
| 20140152631 | Moore et al. | Jun 2014 | A1 |
| 20140156087 | Amundson | Jun 2014 | A1 |
| 20140158338 | Kates | Jun 2014 | A1 |
| 20140165612 | Qu et al. | Jun 2014 | A1 |
| 20140175181 | Warren et al. | Jun 2014 | A1 |
| 20140188288 | Fisher et al. | Jul 2014 | A1 |
| 20140191848 | Imes et al. | Jul 2014 | A1 |
| 20140207291 | Golden et al. | Jul 2014 | A1 |
| 20140207292 | Ramagem et al. | Jul 2014 | A1 |
| 20140214212 | Leen et al. | Jul 2014 | A1 |
| 20140216078 | Ladd | Aug 2014 | A1 |
| 20140217185 | Bicknell | Aug 2014 | A1 |
| 20140217186 | Kramer et al. | Aug 2014 | A1 |
| 20140228983 | Groskreutz et al. | Aug 2014 | A1 |
| 20140231530 | Warren et al. | Aug 2014 | A1 |
| 20140244047 | Oh et al. | Aug 2014 | A1 |
| 20140250399 | Gaherwar | Sep 2014 | A1 |
| 20140262196 | Frank et al. | Sep 2014 | A1 |
| 20140262484 | Khoury et al. | Sep 2014 | A1 |
| 20140263679 | Conner et al. | Sep 2014 | A1 |
| 20140267008 | Jain et al. | Sep 2014 | A1 |
| 20140277762 | Drew | Sep 2014 | A1 |
| 20140277769 | Matsuoka et al. | Sep 2014 | A1 |
| 20140277770 | Aljabari et al. | Sep 2014 | A1 |
| 20140299670 | Ramachandran et al. | Oct 2014 | A1 |
| 20140309792 | Drew | Oct 2014 | A1 |
| 20140312129 | Zikes et al. | Oct 2014 | A1 |
| 20140312131 | Tousignant et al. | Oct 2014 | A1 |
| 20140312694 | Tu et al. | Oct 2014 | A1 |
| 20140316585 | Boesveld et al. | Oct 2014 | A1 |
| 20140316586 | Boesveld et al. | Oct 2014 | A1 |
| 20140316587 | Imes et al. | Oct 2014 | A1 |
| 20140317029 | Matsuoka et al. | Oct 2014 | A1 |
| 20140319231 | Matsuoka et al. | Oct 2014 | A1 |
| 20140319236 | Novotny et al. | Oct 2014 | A1 |
| 20140320282 | Zhang | Oct 2014 | A1 |
| 20140321011 | Bisson et al. | Oct 2014 | A1 |
| 20140324232 | Modi et al. | Oct 2014 | A1 |
| 20140330435 | Stoner et al. | Nov 2014 | A1 |
| 20140346239 | Fadell et al. | Nov 2014 | A1 |
| 20140358295 | Warren et al. | Dec 2014 | A1 |
| 20140367475 | Fadell et al. | Dec 2014 | A1 |
| 20140376530 | Erickson et al. | Dec 2014 | A1 |
| 20140376747 | Mullet et al. | Dec 2014 | A1 |
| 20150001361 | Gagne et al. | Jan 2015 | A1 |
| 20150002165 | Juntunen et al. | Jan 2015 | A1 |
| 20150016443 | Erickson et al. | Jan 2015 | A1 |
| 20150025693 | Wu et al. | Jan 2015 | A1 |
| 20150039137 | Perry et al. | Feb 2015 | A1 |
| 20150041551 | Tessier et al. | Feb 2015 | A1 |
| 20150043615 | Steinberg et al. | Feb 2015 | A1 |
| 20150045976 | Li | Feb 2015 | A1 |
| 20150053779 | Adamek et al. | Feb 2015 | A1 |
| 20150053780 | Nelson et al. | Feb 2015 | A1 |
| 20150053781 | Nelson et al. | Feb 2015 | A1 |
| 20150058779 | Bruck et al. | Feb 2015 | A1 |
| 20150061859 | Matsuoka et al. | Mar 2015 | A1 |
| 20150066215 | Buduri | Mar 2015 | A1 |
| 20150066216 | Ramachandran | Mar 2015 | A1 |
| 20150066220 | Sloo et al. | Mar 2015 | A1 |
| 20150081106 | Buduri | Mar 2015 | A1 |
| 20150081109 | Fadell et al. | Mar 2015 | A1 |
| 20150081568 | Land | Mar 2015 | A1 |
| 20150088272 | Drew | Mar 2015 | A1 |
| 20150088318 | Amundson et al. | Mar 2015 | A1 |
| 20150100166 | Baynes et al. | Apr 2015 | A1 |
| 20150100167 | Sloo et al. | Apr 2015 | A1 |
| 20150115045 | Tu et al. | Apr 2015 | A1 |
| 20150115046 | Warren et al. | Apr 2015 | A1 |
| 20150124853 | Huppi et al. | May 2015 | A1 |
| 20150127176 | Bergman et al. | May 2015 | A1 |
| 20150140994 | Partheesh et al. | May 2015 | A1 |
| 20150142180 | Matsuoka et al. | May 2015 | A1 |
| 20150144706 | Robideau et al. | May 2015 | A1 |
| 20150145653 | Katingari et al. | May 2015 | A1 |
| 20150148963 | Klein et al. | May 2015 | A1 |
| 20150153057 | Matsuoka et al. | Jun 2015 | A1 |
| 20150153060 | Stefanski et al. | Jun 2015 | A1 |
| 20150156631 | Ramachandran | Jun 2015 | A1 |
| 20150159893 | Daubman et al. | Jun 2015 | A1 |
| 20150159899 | Bergman et al. | Jun 2015 | A1 |
| 20150159902 | Quam et al. | Jun 2015 | A1 |
| 20150159903 | Marak et al. | Jun 2015 | A1 |
| 20150159904 | Barton | Jun 2015 | A1 |
| 20150160691 | Kadah et al. | Jun 2015 | A1 |
| 20150163945 | Barton et al. | Jun 2015 | A1 |
| 20150167995 | Fadell et al. | Jun 2015 | A1 |
| 20150168002 | Plitkins et al. | Jun 2015 | A1 |
| 20150168003 | Stefanski et al. | Jun 2015 | A1 |
| 20150168933 | Klein et al. | Jun 2015 | A1 |
| 20150176854 | Butler et al. | Jun 2015 | A1 |
| 20150176855 | Geadelmann et al. | Jun 2015 | A1 |
| 20150198346 | Vedpathak | Jul 2015 | A1 |
| 20150198347 | Tessier et al. | Jul 2015 | A1 |
| 20150204558 | Sartain et al. | Jul 2015 | A1 |
| 20150204561 | Sadwick et al. | Jul 2015 | A1 |
| 20150204563 | Imes et al. | Jul 2015 | A1 |
| 20150204564 | Shah | Jul 2015 | A1 |
| 20150204565 | Amundson et al. | Jul 2015 | A1 |
| 20150204569 | Lorenz et al. | Jul 2015 | A1 |
| 20150204570 | Adamik et al. | Jul 2015 | A1 |
| 20150205310 | Amundson et al. | Jul 2015 | A1 |
| 20150219357 | Stefanski et al. | Aug 2015 | A1 |
| 20150233594 | Abe et al. | Aug 2015 | A1 |
| 20150233595 | Fadell et al. | Aug 2015 | A1 |
| 20150233596 | Warren et al. | Aug 2015 | A1 |
| 20150234369 | Wen et al. | Aug 2015 | A1 |
| 20150241078 | Matsuoka et al. | Aug 2015 | A1 |
| 20150245189 | Nalluri et al. | Aug 2015 | A1 |
| 20150248118 | Li et al. | Sep 2015 | A1 |
| 20150249605 | Erickson et al. | Sep 2015 | A1 |
| 20150260424 | Fadell et al. | Sep 2015 | A1 |
| 20150267935 | Devenish et al. | Sep 2015 | A1 |
| 20150268652 | Lunacek et al. | Sep 2015 | A1 |
| 20150276237 | Daniels et al. | Oct 2015 | A1 |
| 20150276238 | Matsuoka et al. | Oct 2015 | A1 |
| 20150276239 | Fadell et al. | Oct 2015 | A1 |
| 20150276254 | Nemcek et al. | Oct 2015 | A1 |
| 20150276266 | Warren et al. | Oct 2015 | A1 |
| 20150277463 | Hazzard et al. | Oct 2015 | A1 |
| 20150277492 | Chau et al. | Oct 2015 | A1 |
| 20150280935 | Poplawski et al. | Oct 2015 | A1 |
| 20150287310 | Deiiuliis et al. | Oct 2015 | A1 |
| 20150292764 | Land et al. | Oct 2015 | A1 |
| 20150292765 | Matsuoka et al. | Oct 2015 | A1 |
| 20150293541 | Fadell et al. | Oct 2015 | A1 |
| 20150300672 | Fadell et al. | Oct 2015 | A1 |
| 20150312696 | Ribbich et al. | Oct 2015 | A1 |
| 20150316285 | Clifton et al. | Nov 2015 | A1 |
| 20150316286 | Roher | Nov 2015 | A1 |
| 20150316902 | Wenzel et al. | Nov 2015 | A1 |
| 20150323212 | Warren et al. | Nov 2015 | A1 |
| 20150327010 | Gottschalk et al. | Nov 2015 | A1 |
| 20150327084 | Ramachandran et al. | Nov 2015 | A1 |
| 20150327375 | Bick et al. | Nov 2015 | A1 |
| 20150330654 | Matsuoka | Nov 2015 | A1 |
| 20150330658 | Filson et al. | Nov 2015 | A1 |
| 20150330660 | Filson et al. | Nov 2015 | A1 |
| 20150332150 | Thompson | Nov 2015 | A1 |
| 20150338117 | Henneberger et al. | Nov 2015 | A1 |
| 20150345818 | Oh et al. | Dec 2015 | A1 |
| 20150348554 | Orr et al. | Dec 2015 | A1 |
| 20150354844 | Kates | Dec 2015 | A1 |
| 20150354846 | Hales et al. | Dec 2015 | A1 |
| 20150355371 | Ableitner et al. | Dec 2015 | A1 |
| 20150362208 | Novotny et al. | Dec 2015 | A1 |
| 20150362926 | Yarde et al. | Dec 2015 | A1 |
| 20150362927 | Giorgi | Dec 2015 | A1 |
| 20150364135 | Kolavennu et al. | Dec 2015 | A1 |
| 20150370270 | Pan et al. | Dec 2015 | A1 |
| 20150370272 | Reddy et al. | Dec 2015 | A1 |
| 20150370615 | Pi-Sunyer | Dec 2015 | A1 |
| 20150370621 | Karp et al. | Dec 2015 | A1 |
| 20150372832 | Kortz et al. | Dec 2015 | A1 |
| 20150372834 | Karp et al. | Dec 2015 | A1 |
| 20150372999 | Pi-Sunyer | Dec 2015 | A1 |
| 20160006274 | Tu et al. | Jan 2016 | A1 |
| 20160006577 | Logan | Jan 2016 | A1 |
| 20160010880 | Bravard et al. | Jan 2016 | A1 |
| 20160018122 | Frank et al. | Jan 2016 | A1 |
| 20160018127 | Gourlay et al. | Jan 2016 | A1 |
| 20160020590 | Roosli et al. | Jan 2016 | A1 |
| 20160026194 | Mucignat et al. | Jan 2016 | A1 |
| 20160036227 | Schultz et al. | Feb 2016 | A1 |
| 20160040903 | Emmons et al. | Feb 2016 | A1 |
| 20160047569 | Fadell et al. | Feb 2016 | A1 |
| 20160054022 | Matas et al. | Feb 2016 | A1 |
| 20160054792 | Poupyrev | Feb 2016 | A1 |
| 20160054988 | Desire | Feb 2016 | A1 |
| 20160061471 | Eicher et al. | Mar 2016 | A1 |
| 20160061474 | Cheung et al. | Mar 2016 | A1 |
| 20160069582 | Buduri | Mar 2016 | A1 |
| 20160069583 | Fadell et al. | Mar 2016 | A1 |
| 20160077532 | Lagerstedt et al. | Mar 2016 | A1 |
| 20160088041 | Nichols | Mar 2016 | A1 |
| 20160107820 | MacVittie et al. | Apr 2016 | A1 |
| 20160249437 | Sun et al. | Aug 2016 | A1 |
| 20160327298 | Sinha et al. | Nov 2016 | A1 |
| 20160327299 | Ribbich et al. | Nov 2016 | A1 |
| 20160327300 | Ribbich et al. | Nov 2016 | A1 |
| 20160327301 | Ribbich | Nov 2016 | A1 |
| 20160327302 | Ribbich et al. | Nov 2016 | A1 |
| 20160327921 | Ribbich et al. | Nov 2016 | A1 |
| 20160330084 | Hunter et al. | Nov 2016 | A1 |
| 20160377306 | Drees et al. | Dec 2016 | A1 |
| 20170041454 | Nicholls et al. | Feb 2017 | A1 |
| 20170074536 | Bentz et al. | Mar 2017 | A1 |
| 20170074537 | Bentz et al. | Mar 2017 | A1 |
| 20170074539 | Bentz et al. | Mar 2017 | A1 |
| 20170074541 | Bentz et al. | Mar 2017 | A1 |
| 20170075510 | Bentz et al. | Mar 2017 | A1 |
| 20170075568 | Bentz et al. | Mar 2017 | A1 |
| 20170076263 | Bentz et al. | Mar 2017 | A1 |
| 20170102162 | Drees et al. | Apr 2017 | A1 |
| 20170102433 | Wenzel et al. | Apr 2017 | A1 |
| 20170102434 | Wenzel et al. | Apr 2017 | A1 |
| 20170102675 | Drees | Apr 2017 | A1 |
| 20170103483 | Drees et al. | Apr 2017 | A1 |
| 20170104332 | Wenzel et al. | Apr 2017 | A1 |
| 20170104336 | Elbsat et al. | Apr 2017 | A1 |
| 20170104337 | Drees | Apr 2017 | A1 |
| 20170104342 | Elbsat et al. | Apr 2017 | A1 |
| 20170104343 | Elbsat et al. | Apr 2017 | A1 |
| 20170104344 | Wenzel et al. | Apr 2017 | A1 |
| 20170104345 | Wenzel et al. | Apr 2017 | A1 |
| 20170104346 | Wenzel et al. | Apr 2017 | A1 |
| 20170104449 | Drees | Apr 2017 | A1 |
| 20170122613 | Sinha et al. | May 2017 | A1 |
| 20170122617 | Sinha et al. | May 2017 | A1 |
| 20170123391 | Sinha et al. | May 2017 | A1 |
| 20170124838 | Sinha et al. | May 2017 | A1 |
| 20170124842 | Sinha et al. | May 2017 | A1 |
| 20170131825 | Moore et al. | May 2017 | A1 |
| 20170263111 | Deluliis et al. | Sep 2017 | A1 |
| 20170292731 | Matsuoka et al. | Oct 2017 | A1 |
| 20170295058 | Gottschalk et al. | Oct 2017 | A1 |
| 20180023833 | Matsuoka et al. | Jan 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2466854 | Apr 2008 | CA |
| 2633200 | Jan 2011 | CA |
| 2633121 | Aug 2011 | CA |
| 2818356 | May 2012 | CA |
| 2818696 | May 2012 | CA |
| 2853041 | Apr 2013 | CA |
| 2853081 | Apr 2013 | CA |
| 2812567 | May 2014 | CA |
| 2886531 | Sep 2015 | CA |
| 2894359 | Dec 2015 | CA |
| 10 2004 005 962 | Aug 2005 | DE |
| 2 283 279 | Feb 2011 | EP |
| 2 738 478 | Jun 2014 | EP |
| 2 897 018 | Jul 2015 | EP |
| 2 988 188 | Feb 2016 | EP |
| 2 519 441 | Apr 2015 | GB |
| WO 0022491 | Apr 2000 | WO |
| WO-2006041599 | Jul 2006 | WO |
| WO 2009006133 | Jan 2009 | WO |
| WO-2009058127 | May 2009 | WO |
| WO-2009036764 | Jan 2010 | WO |
| WO-2010059143 | May 2010 | WO |
| WO 2010078459 | Jul 2010 | WO |
| WO 2010088663 | Aug 2010 | WO |
| WO-2012042232 | Apr 2012 | WO |
| WO 2012068436 | May 2012 | WO |
| WO 2012068495 | May 2012 | WO |
| WO 2012068503 | May 2012 | WO |
| WO-2012068507 | May 2012 | WO |
| WO 2012068517 | May 2012 | WO |
| WO 2012068526 | May 2012 | WO |
| WO 2013033469 | Mar 2013 | WO |
| WO-2013052389 | Apr 2013 | WO |
| WO 2013052905 | Apr 2013 | WO |
| WO 2013058933 | Apr 2013 | WO |
| WO-2013058934 | Apr 2013 | WO |
| WO-2013058968 | Apr 2013 | WO |
| WO 2013058969 | Apr 2013 | WO |
| WO 2013059684 | Apr 2013 | WO |
| WO 2012142477 | Aug 2013 | WO |
| WO-2013153480 | Dec 2013 | WO |
| WO 2014047501 | Mar 2014 | WO |
| WO 2012068437 | Apr 2014 | WO |
| WO 2012068459 | Apr 2014 | WO |
| WO-2013058932 | Apr 2014 | WO |
| WO 2014051632 | Apr 2014 | WO |
| WO-2014051635 | Apr 2014 | WO |
| WO-2014055059 | Apr 2014 | WO |
| WO-2013052901 | May 2014 | WO |
| WO-2014152301 | Sep 2014 | WO |
| WO 2014152301 | Sep 2014 | WO |
| WO-2015012449 | Jan 2015 | WO |
| WO-2015039178 | Mar 2015 | WO |
| WO 2015054272 | Apr 2015 | WO |
| WO 2015057698 | Apr 2015 | WO |
| WO-2015099721 | Jul 2015 | WO |
| WO 2015127499 | Sep 2015 | WO |
| WO-2015127566 | Sep 2015 | WO |
| WO 2015134755 | Oct 2015 | WO |
| WO 2015195772 | Dec 2015 | WO |
| WO 2016038374 | Mar 2016 | WO |
| Entry |
|---|
| Written Opinion for Singapore Application No. 11201708996V, dated Dec. 27, 2017, 6 pages. |
| Written Opinion for Singapore Application No. 11201708997W, dated Jan. 10, 2018, 9 pages. |
| U.S. Appl. No. 15/179,894, filed Jun. 10, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/207,431, filed Jul. 11, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,777, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,784, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,788, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,793, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,844, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,869, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,872, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,873, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,875, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,879, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,880, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,881, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,883, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,885, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/247,886, filed Aug. 25, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/217,788, filed Sep. 11, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,131, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,231, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,233, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,245, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,246, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| U.S. Appl. No. 62/239,249, filed Oct. 8, 2015, Johnson Controls Technology Company. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030291, dated Sep. 7, 2016, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030827 dated Sep. 7, 2016, 13 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030829, dated Sep. 7, 2016, 15 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030835, dated Sep. 7, 2016, 13 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030836, dated Sep. 7, 2016, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/030837, dated Sep. 7, 2016, 13 pages. |
| Unknown, National Semiconductor's Temperature Sensor Handbook, Nov. 1, 1997, retrieved from the Internet at http://shrubbery.net/˜heas/willem/PDF/NSC/temphb.pdf on Aug. 11, 2016, pp. 1-40. |
| Written Opinion for Singapore Application No. 11201709002Y, dated Feb. 7, 2018, 5 pages. |
| Office Action for U.S. Appl. No. 15/260,294, dated Feb. 16, 2018, 19 pages. |
| Office Action for U.S. Appl. No. 15/260,297, dated Feb. 9, 2018, 17 pages. |
| Office Action for U.S. Appl. No. 15/260,301, dated Feb. 9, 2018, 9 pages. |
| Office Action for U.S. Appl. No. 15/336,789, dated Feb. 22, 2018, 15 pages. |
| Office Action for U.S. Appl. No. 15/336,791, dated Mar. 2, 2018, 13 pages. |
| Notice of Allowance for U.S. Appl. No. 15/146,649, dated Feb. 27, 2018, 7 pages. |
| Examination Report for Australian Application No. 2016257458, dated May 7, 2018, 4 pages. |
| Examination Report for Australian Application No. 2016257459, dated May 4, 2018, 3 pages. |
| Office Action for U.S. Appl. No. 15/146,134, dated May 14, 2018, 21 pages. |
| Office Action for U.S. Appl. No. 15/260,295, dated Apr. 18, 2018, 16 pages. |
| Office Action for U.S. Appl. No. 15/336,792, dated Mar. 29, 2018, 12 pages. |
| Office Action for U.S. Appl. No. 15/146,749, dated Mar. 19, 2018, 11 pages. |
| U.S. Appl. No. 15/338,215, filed Oct. 28, 2016, Johnson Controls Technology Company. |
| U.S. Appl. No. 15/338,221, filed Oct. 28, 2016, Johnson Controls Technology Company. |
| Search Report for International Application No. PCT/US2016/051176, dated Feb. 16, 2017, 20 pages. |
| Search Report for International Application No. PCT/US2017/012217, dated Mar. 31, 2017, 14 pages. |
| Search Report for International Application No. PCT/US2017/012218, dated Mar. 31, 2017, 14 pages. |
| Search Report for International Application No. PCT/US2017/012221, dated Mar. 31, 2017, 13 pages. |
| Search Report for International Application No. PCT/US2017/030890, dated Jun. 21, 2017, 13 pages. |
| Notice of Allowance for U.S. Appl. No. 15/146,763, dated Oct. 4, 2017, 8 pages. |
| Office Action for U.S. Appl. No. 15/146,649, dated Oct. 6, 2017, 6 pages. |
| Office Action for U.S. Appl. No. 15/146,749, dated Oct. 4, 2017, 9 pages. |
| Office Action for U.S. Appl. No. 15/336,789, dated Aug. 10, 2017, 14 pages. |
| Office Action for U.S. Appl. No. 15/336,792, dated Oct. 10, 2017, 12 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170146260 A1 | May 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62260141 | Nov 2015 | US |
