US20230032735A1

US20230032735A1 - Next generation touchless building controls

Info

Publication number: US20230032735A1
Application number: US17/390,279
Authority: US
Inventors: Richard David Friend; Adam Grabowski
Original assignee: Johnson Controls Tyco IP Holdings LLP
Current assignee: Tyco Fire and Security GmbH
Priority date: 2021-07-30
Filing date: 2021-07-30
Publication date: 2023-02-02

Abstract

A control device for a conditioned space includes a first face and a second face. The first face is configured to be mounted on a surface at a height accessible by a user. The second face has a display. A first axis normal to the display is angularly offset by an angular amount from a second axis normal to the surface. The first axis normal to the display is substantially parallel with a line of sight associated with the user at an access distance from the control device.

Description

BACKGROUND

The present disclosure relates generally to control systems that control environmental conditions of a building. More particularly, the present disclosure relates to a touchless building control device of a building system.
Systems of a building may include various controllers configured to generate control decisions for heating or cooling equipment or systems. The controllers can, in some cases, be thermostats. Thermostats can be utilized in both residential and commercial building systems. Thermostats can receive, or themselves measure, environmental conditions such as temperature and generate control decisions based on setpoints and/or the measured temperature for operating the heating or cooling equipment or systems.
Building control devices include physical displays for presenting measured or control information to a user and for receiving input from the user, e.g., a user desired setpoint or operating schedule. Building control devices typically include physical buttons or touch sensitive surfaces for interacting with the building control device. However, in some cases, the physical buttons and touch sensitive surfaces are prone to signs of use (e.g., wear, smudges, finger prints, etc.) and may be difficult to keep clean, ultimately contributing to the spread of disease and an unsightly control device. Traditional displays on building control devices are parallel to the mounting surface, and consume large amounts of power. In some cases, the building control device is mounted high on a wall that is not easily accessible by all users. Furthermore, typical building control devices often require the use of a physical lock box to selectively provide access to the thermostat, with varying levels of success.

SUMMARY

In one implementation of the present disclosure, a control device for a conditioned space includes a first face and a second face. In some embodiments, the first face is configured to be mounted on a surface at a height accessible by a user. In some embodiments, the second face has a display. In some embodiments, a first axis normal to the display is angularly offset by an angular amount from a second axis normal to the surface. In some embodiments, the first axis normal to the display is substantially parallel with a line of sight associated with the user at an access distance from the control device.
In some embodiments, the angular amount is greater than or equal to 15 degrees and less than or equal to 45 degrees.
In some embodiments, the control device includes a sensor and a processing circuit. In some embodiments, the sensor is configured to detect an identifier associated with the user. In some embodiments, the processing circuit is in communication with the first sensor, the display, and heating, ventilating, or air conditioning (HVAC) equipment.
In some embodiments, the processing circuit is configured to detect the identifier associated with the user with the sensor, compare the identifier to a list of authorized identifiers to selectively provide access, and receive an input from the user based on the identifier associated with the user. In some embodiments, the input is associated with the conditioned space.
In some embodiments, the control device includes a second sensor in communication with the processing circuit. In some embodiments the second sensor is configured to detect a motion of the user within a detectable range associated with the second sensor. In some embodiments, the processing circuit is configured to selectively receive the input from the second sensor.
In some embodiments, the control device includes a light emitting device in communication with the processing circuit. In some embodiments, the light emitting device is configured to emit light toward a perimeter of the first face.
In some embodiments, the processing circuit selectively receives the input from a user device. In some embodiments, the user device is wirelessly connected to the processing circuit.
In some embodiments, the processing circuit is configured to output an access code on the display prior to selectively receiving the input from the user.
In some embodiments, the control device includes a sensor configured to detect a presence of the user. In some embodiments, the third face is associated with the sensor.
In some embodiments, the display is an electrophoretic display.
In some embodiments, the control device includes a sensor configured to detect a motion of the user. In some embodiments, the sensor in communication with a processing circuit. In some embodiments, the processing circuit is in communication with the display and the sensor. In some embodiments, the processing circuit is configured to receive an input from the sensor.
In some embodiments, the control device includes a light emitting device. In some embodiments, the light emitting device is configured to emit a visible light on the surface.
Another implementation of the present disclosure is a user interface system for controlling a conditioned space, according to some embodiments. In some embodiments, the system includes a first display, a first sensor, a second sensor, and a first processing circuit. In some embodiments, the first display is angularly offset by a first angular amount from a mounting surface. In some embodiments, the first sensor is configured to identify a first user within a first detectable range associated with the first sensor. In some embodiments, the second sensor is configured to detect a first motion of the first user within a second detectable range associated with the second sensor. In some embodiments, the first processing circuit is in communication with the first display, the first sensor, and the second sensor. In some embodiments, the processing circuit is configured to identify the first user within the first detectable range associated with the first sensor, and selectively receive a first input from the first user by at least one of the second sensor and a user device. In some embodiments, the user device is wirelessly connected to the first processing circuit. In some embodiments, the processing circuit is configured to transmit the first input to a HVAC system.
In some embodiments, the user interface system includes a second display, a third sensor, and a second processing circuit. In some embodiments, the second display is angularly offset by a second angular amount from a second mounting surface. In some embodiments, the third sensor is configured to identify a second user within a third detectable range associated with the third sensor. In some embodiments, the second processing circuit is communicably coupled to the second display and the third sensor. In some embodiments, the second processing circuit is configured to identify the second user within the third detectable range associated with the third sensor, selectively receive a second input from the second user from a second user device associated with the second user based on an identifier of the second user. In some embodiments, the second user device is wirelessly connected to the second processing circuit. In some embodiments, the first processing circuit is in communication with the second processing circuit. In some embodiments, the first processing circuit is configured to receive the second input from the second processing circuit. In some embodiments, the first processing circuit is configured to transmit the second input to the HVAC system.
In some embodiments, the first angular amount is between 5 degrees and 90 degrees.
In some embodiments, the user interface system includes a third sensor. In some embodiments the third sensor is configured to detect a user within a third detectable range associated with the third sensor. In some embodiments the processing circuit is configured to update the first display upon the third sensor detecting the user.
Another implementation of the present disclosure is a method for adjusting a characteristic of a conditioned space, according to some embodiments. In some embodiments, the method includes identifying a user based on a first sensor configured to detect an identifier associated with the user, determining a user authorization based on the identifier associated with the user, displaying information on an a display being angularly offset by an angular amount from a mounting surface, receiving a user input, and commanding a HVAC equipment based on the user input to adjust the characteristic of the conditioned space.
In some embodiments, determining a user authorization includes loading a user profile based on the identifier associated with the user.
In some embodiments, receiving a user input includes a user input generated by a third sensor configured to detect a touchless motion of the user.
In some embodiments, receiving a user input includes the user input received by a user device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with an HVAC system, according to some embodiments.

FIG. 2 is a schematic of a waterside system which can be used as part of the HVAC system of FIG. 1 , according to some embodiments.

FIG. 3 is a block diagram illustrating an airside system which can be used as part of the HVAC system of FIG. 1 , according to some embodiments.

FIG. 4A is a block diagram of an on-site thermostat configured to adjust an operation of HVAC equipment for a conditioned space, according to some embodiments.

FIG. 4B is a block diagram of a controller configured to adjust an operation of HVAC equipment for a conditioned space, according to some embodiments.

FIG. 5 is a perspective view of a building control device on a mounting surface, according to some embodiments.

FIG. 6 is a perspective view of the building control device of FIG. 5 , according to some embodiments.

FIG. 7 is a perspective view of the building control device of FIG. 5 , according to some embodiments.

FIG. 8 is a side view of the building control device of FIG. 5 , according to some embodiments.

FIG. 9 is a schematic representation of users nearby the building control device of FIG. 5 , according to some embodiments.

FIG. 10 is a schematic representation of a user having an example identifier nearby the building control device of FIG. 5 , according to some embodiments.

FIG. 11 is a schematic representation of a user interacting with the building control device of FIG. 5 , according to some embodiments.

FIG. 12 is a schematic representation of a user interacting with the building control device of FIG. 5 , according to some embodiments.

FIG. 13 is a schematic representation of a user interacting with the building control device of FIG. 5 using a user device, according to some embodiments.

FIG. 14 is an example graphical user interface deployed on the user device of FIG. 13 interacting with the building control device of FIG. 5 , according to some embodiments.

FIG. 15 is a perspective view of a building control device configured to interact with the building control device of FIG. 5 , according to some embodiments.

FIG. 16 is a schematic representation of the building control device of FIG. 15 connected to the building control device of FIG. 5 , according to some embodiments.

FIG. 17 is a perspective view of the second building control device of FIG. 15 in an emergency operational mode, according to some embodiments.

FIG. 18 is a flow diagram of an example method of the building control device of FIG. 5 interacting with a user, according to some embodiments.

FIG. 19 is a block diagram of the building control device of FIG. 15 communicating with the building control device of FIG. 5 , according to some embodiments.

FIG. 20 is a block diagram showing example components of the building control device of FIG. 5 and an example user device, according to some embodiments.

FIG. 21 is a block diagram of an example HVAC system connected to the building control device of FIG. 5 , according to some embodiments.

FIG. 22 is a flow diagram of an example method for control of the HVAC system of FIG. 21 using the building control device of FIG. 5 , according to some embodiments.

DETAILED DESCRIPTION

Overview
Referring generally to the FIGURES, systems and methods are shown for a touchless building control device, according to various embodiments. A touchless building control device may be a thermostat or other control device that does not require a user to touch the device. For example, the touchless building control device may include sensors to detect touchless motion, and connections to equipment or connections to a remote device or connections to a network but includes no touch controls on the interface for allowing a user to interact with the touchless building control device.
HVAC System
Referring now to FIGS. 1-3 , an exemplary HVAC system in which the systems and methods of the present disclosure can be implemented are shown, according to an exemplary embodiment. While the systems and methods of the present disclosure are described primarily in the context of a building HVAC system, it should be understood that the control strategies described herein may be generally applicable to any type of control system that optimizes or regulates a variable of interest. For example, the systems and methods herein may be used to optimize an amount of energy produced by various types of energy producing systems or devices (e.g., power plants, steam or wind turbines, solar panels, combustion systems, etc.) and/or to optimize an amount of energy consumed by various types of energy consuming systems or devices (e.g., electronic circuitry, mechanical equipment, aerospace and land-based vehicles, building equipment, HVAC devices, refrigeration systems, etc.).
In various implementations, such control strategies may be used in any type of controller that functions to achieve a setpoint for a variable of interest (e.g., by minimizing a difference between a measured or calculated input and a setpoint) and/or optimize a variable of interest (e.g., maximize or minimize an output variable). It is contemplated that these control strategies can be readily implemented in various types of controllers (e.g., motor controllers, power controllers, fluid controllers, HVAC controllers, lighting controllers, chemical controllers, process controllers, etc.) and various types of control systems (e.g., closed-loop control systems, open-loop control systems, feedback control systems, feed-forward control systems, etc.) as may be suitable for various applications. All such implementations should be considered within the scope of the present disclosure.
Referring particularly to FIG. 1 , a perspective view of a building 10 is shown. Building 10 may generally include a building management system (e.g., a system of devices configured to control, monitor, and manage equipment in or around building 10). The building management system can include, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof.
Building 10 is served by an HVAC system 100. HVAC system 100 can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 can provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 can use the heated or chilled fluid to heat or cool an airflow provided to building 10.
HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 can use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and can circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 can be located in or around building 10 (as shown in FIG. 1 ) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid can be heated in boiler 104 or cooled in chiller 102, depending on whether heating or cooling is required in building 10. Boiler 104 can add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller 102 can place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 can be transported to AHU 106 via piping 108.
AHU 106 can place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 can transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid can then return to chiller 102 or boiler 104 via piping 110.
Airside system 130 can deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and can provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 can receive input from sensors located within AHU 106 and/or within the building zone and can adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve set-point conditions for the building zone.
Referring now to FIG. 2 , a block diagram of waterside system 120 is shown, according to an exemplary embodiment. Waterside system 120 can include a subset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller 102, pumps, valves, etc.) and can operate to supply a heated or chilled fluid to AHU 106. The HVAC devices of waterside system 120 can be located within building 10 (e.g., as components of waterside system 120) or at an offsite location such as a central plant.
In FIG. 2 , waterside system 120 is shown as a central plant having a plurality of subplants 202-212. Subplants 202-212 are shown to include a heater subplant 202, a heat recovery chiller subplant 204, a chiller subplant 206, a cooling tower subplant 208, a hot thermal energy storage (TES) subplant 210, and a cold thermal energy storage (TES) subplant 212. Subplants 202-212 consume resources (e.g., water, natural gas, electricity, etc.) from utilities to serve the thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example, heater subplant 202 can be configured to heat water in a hot water loop 214 that circulates the hot water between heater subplant 202 and building 10. Chiller subplant 206 can be configured to chill water in a cold water loop 216 that circulates the cold water between chiller subplant 206 and the building 10. Heat recovery chiller subplant 204 can be configured to transfer heat from cold water loop 216 to hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop 218 can absorb heat from the cold water in chiller subplant 206 and reject the absorbed heat in cooling tower subplant 208 or transfer the absorbed heat to hot water loop 214. Hot TES subplant 210 and cold TES subplant 212 can store hot and cold thermal energy, respectively, for subsequent use.
Hot water loop 214 and cold water loop 216 can deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building 10 to serve the thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.
Although subplants 202-212 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) can be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants 202-212 can provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system 120 are within the scope of the present invention.
Each of subplants 202-212 can include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.
Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.
Hot TES subplant 210 is shown to include a hot TES tank 242 configured to store the hot water for later use. Hot TES subplant 210 can also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242. Cold TES subplant 212 is shown to include cold TES tanks 244 configured to store the cold water for later use. Cold TES subplant 212 can also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244.
In some embodiments, one or more of the pumps in waterside system 120 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in waterside system 120 include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system 120. In various embodiments, waterside system 120 can include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system 120 and the types of loads served by waterside system 120.
Referring now to FIG. 3 , a block diagram of an airside system 130 is shown, according to an exemplary embodiment. Airside system 130 can include a subset of the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers, etc.) and can be located in or around building 10. Airside system 130 can operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by waterside system 120.
In FIG. 3 , airside system 130 is shown to include an economizer-type air handling unit (AHU) 302. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 302 can receive return air 304 from building zone 306 via return air duct 308 and can deliver supply air 310 to building zone 306 via supply air duct 312. In some embodiments, AHU 302 is a rooftop unit located on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1 ) or otherwise positioned to receive return air 304 and outside air 314. AHU 302 can be configured to operate an exhaust air damper 316, mixing damper 318, and outside air damper 320 to control an amount of outside air 314 and return air 304 that combine to form supply air 310. Any return air 304 that does not pass through mixing damper 318 can be exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.
Each of dampers 316-320 can be operated by an actuator. For example, exhaust air damper 316 can be operated by actuator 324, mixing damper 318 can be operated by actuator 326, and outside air damper 320 can be operated by actuator 328. Actuators 324-328 can communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 can receive control signals from AHU controller 330 and can provide feedback signals to AHU controller 330. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators 324-328. AHU controller 330 can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum-seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 324-328.
Still referring to FIG. 3 , AHU 302 is shown to include a cooling coil 334, a heating coil 336, and a fan 338 positioned within supply air duct 312. Fan 338 can be configured to force supply air 310 through cooling coil 334 and/or heating coil 336 and provide supply air 310 to building zone 306. AHU controller 330 can communicate with fan 338 via communications link 340 to control a flow rate of supply air 310. In some embodiments, AHU controller 330 controls an amount of heating or cooling applied to supply air 310 by modulating a speed of fan 338.
Cooling coil 334 can receive a chilled fluid from waterside system 120 (e.g., from cold water loop 216) via piping 342 and can return the chilled fluid to waterside system 120 via piping 344. Valve 346 can be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.
Heating coil 336 can receive a heated fluid from waterside system 120 (e.g., from hot water loop 214) via piping 348 and can return the heated fluid to waterside system 120 via piping 350. Valve 352 can be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.
Each of valves 346 and 352 can be controlled by an actuator. For example, valve 346 can be controlled by actuator 354 and valve 352 can be controlled by actuator 356. Actuators 354-356 can communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 can receive control signals from AHU controller 330 and can provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 can also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.
In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a set-point temperature for supply air 310 or to maintain the temperature of supply air 310 within a set-point temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller 330 can control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination thereof.
Still referring to FIG. 3 , airside system 130 is shown to include a BMS controller 366 and a client device 368. BMS controller 366 can include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for airside system 130, waterside system 120, HVAC system 100, and/or other controllable systems that serve building 10. BMS controller 366 can communicate with multiple downstream building systems or subsystems (e.g., HVAC system 100, a security system, a lighting system, waterside system 120, etc.) via a communications link 370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMS controller 366 can be separate (as shown in FIG. 3 ) or integrated. In an integrated implementation, AHU controller 330 can be a software module configured for execution by a processor of BMS controller 366.
In some embodiments, AHU controller 330 receives information from BMS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 can provide BMS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.
Client device 368 can include one or more human-machine interfaces or client interfaces (e.g., graphical operator interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system 100, its subsystems, and/or devices. Client device 368 can be a computer workstation, a client terminal, a remote or local interface, or any other type of operator interface device. Client device 368 can be a stationary terminal or a mobile device. For example, client device 368 can be a desktop computer, a computer server with an operator interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 can communicate with BMS controller 366 and/or AHU.
Referring now to FIGS. 4A-4B, system 400 is shown, according to some embodiments. System 400 includes conditioned space 402, according to some embodiments. Conditioned space 402 may be a room, an area, a floor of a building, etc., or any other space to which heating ventilating and/or cooling and other control is provided and monitored. System 400 includes HVAC equipment 404 configured to provide heating, ventilation, or cooling to conditioned space 402, according to some embodiments. HVAC equipment 404 may be configured to provide heating, ventilation, and/or cooling to conditioned space 402 via one or more ducts, vents, fans, etc. Conditioned space 402 may have a temperature distribution throughout various areas of conditioned space 402. For example, conditioned space 402 may have a temperature T₁near HVAC equipment 404, and a temperature T₂near a window or door 409. If HVAC equipment 404 is in an operating state to provide cooling to conditioned space 402, T₂may be greater than T₁. Likewise, if HVAC equipment 404 is in an operating state to provide heating to conditioned space 402, T₂may be less than T₁. Conditioned space 402 may have an average temperature (e.g., an average with respect to area of conditioned space 402) T_avg.
As shown in FIG. 4A, system 400 includes a building control device (e.g., building controller, control device, etc.), shown as thermostat 406, according to some embodiments. Thermostat 406 is configured to adjust an operation of HVAC equipment 404 by providing HVAC equipment 404 with manipulated variable u, according to some embodiments. In some embodiments, manipulated variable u is a command to transition HVAC equipment 404 between an on state and an off state. In some embodiments, manipulated variable u is a command to transition HVAC equipment 404 between a cooling state, a heating state, and an off state. For example, if HVAC equipment 404 includes equipment configured to provide heating to conditioned space 402, thermostat 406 may provide the heating equipment of HVAC equipment 404 configured to provide heating to conditioned space 402 with manipulated variable u_Hwhich indicates a command to transition the heating equipment of HVAC equipment 404 between an on state (i.e., a state which causes the heating equipment to operate to provide heating to conditioned space 402) and an off state (i.e., a state which causes the heating equipment to be in-operational or to not provide heating to conditioned space 402). Likewise, if HVAC equipment 404 includes cooling equipment configured to provide cooling to conditioned space 402, thermostat 406 may be configured to provide the cooling equipment with a manipulated variable u_Cto transition the cooling equipment between an on state (i.e., a state which causes the cooling equipment to operate to provide cooling to conditioned space 402) and an off state (i.e., an in-operational state of the cooling equipment). In some embodiments, manipulated variable u represents either u_Hor u_C.
In some embodiments, thermostat 406 includes sensor 410 and controller 408. In some embodiments, sensor 410 is configured to measure a performance variable y of conditioned space 402. For example, sensor 410 may be a temperature sensor (e.g., a negative temperature coefficient thermistor, a resistance temperature detector, a thermocouple, a semi-conductor based temperature sensor, etc.) configured to measure a temperature of conditioned space 402. In some embodiments, sensor 410 is configured to measure a temperature of conditioned space 402 near thermostat 406. In some embodiments, sensor 410 is configured to measure the average temperature T_avgof conditioned space 402. In some embodiments, multiple sensors 410 are disposed about conditioned space 402 and are configured to measure the temperature or other ambient condition of conditioned space 402 in multiple locations. In some embodiments, the temperature measured by sensor 410 is the performance variable y. In some embodiments, sensor 410 is configured to measure an indoor air quality (e.g., concentration of airborne particulate in ppm), a humidity sensors configured to measure humidity of conditioned space 402, etc., or any other sensor configured to measure one or more conditions of conditioned space 402. In some embodiments, sensor 410 represents a plurality of the same type of sensors, or a plurality of various types of sensors.
Controller 408 of thermostat 406 is configured to determine values of the manipulated variable u to transition HVAC equipment 404 between various states (e.g., an on state and an off state, a cooling state and a heating state, etc.) based on the performance variable y measured by sensor 410, according to some embodiments. In some embodiments, controller 408 is configured to determine the manipulated variable u based on the performance variable y and a setpoint r. The setpoint r may indicate a desired temperature or a desired value of the performance variable y of conditioned space 402. In some embodiments, setpoint r is received via user interface 412 of thermostat 406. For example, a user may input a desired temperature of conditioned space 402 (e.g., 70 degrees Fahrenheit), and controller 408 may use the setpoint r, one or more values of the performance variable y, and a control algorithm to determine u to achieve the setpoint r for conditioned space 402.
In some embodiments, controller 408 receives the setpoint r from user interface 412. In some embodiments, controller 408 displays the performance variable y at user interface 412. In some embodiments, controller 408 is configured to determine a filtered, smoothed, or adjusted value z of performance variable y and provide value z at user interface 412. The filtered, smoothed, or adjusted value z of performance variable y may represent a time averaged value of performance variable y which may advantageously reduce minor fluctuations of performance variable y from displaying on the user interface 412, according to some embodiments. In some embodiments, the reduced number of fluctuations of value z may reduce the required refresh rate of a display in the user interface 412.
Referring now to FIG. 4B, system 400 is shown, according to some embodiments. System 400 as shown in FIG. 4B operates similarly to or the same as system 400 of FIG. 4A, however, controller 408 is positioned remotely from conditioned space 402. For example, controller 408 may be positioned at HVAC equipment 404, at a remote server, in a back room, in a hallway, etc. In some embodiments, controller 408 receives the performance variable y from sensor 410, the setpoint r, from user interface 412. In some embodiments, controller 408 is configured to operate similarly as described above in greater detail with reference to FIG. 4A. In some embodiments, controller 408 is configured to provide the filtered value z of the performance variable y to user interface 412 for display. In some embodiments, the controller 408 is configured to receive inputs from the user interface 412 and to supply commands to building device 411 (e.g., IoT device, smart device, smart hub, etc.) to control a characteristic of the conditioned space 402 (e.g., light intensity, sound intensity, etc.).

Touchless Building Controller

Referring now to FIGS. 5-8 , a touchless building control device 500 for controlling building equipment is shown, according to some embodiments. In some embodiments, touchless building control device 500 may be similar to thermostat 406. In some embodiments, the touchless building control device 500 is mounted to a mounting surface 502 (e.g., wall, vertical surface, etc.) on a first face, shown as mounting face 504. In some embodiments, mounting surface 502 has an axis (e.g., direction, vector, etc.) normal to (e.g., perpendicular to, etc.) the mounting surface 502, shown as mounting surface normal axis 503. The touchless building control device 500 is shown to include a display 505 on a second face, shown as display face 507. In some embodiments, display 505 includes an axis (e.g., direction, vector, etc.) normal to (e.g., perpendicular to, etc.) a face of the display 505. In some embodiments, display 505 is an electrophoretic display (e.g., electronic ink, electronic paper, etc.). In some embodiments, display 505 may be backlit, or may reflect ambient light such that a user can view information on the display. In some embodiments, display 505 is an electrophoretic display that uses a single pigment system such as the E Ink JustTint™ one pigment ink system, a dual pigment system, a three pigment system such as the E Ink Spectra™ 3000 three pigment ink system, a four pigment system such as the E Ink Spectra™ 3100 four pigment ink system, or any number of pigment system. In some embodiments, the display may use a variety of display technologies such as light emitting diode (LED), organic light emitting diode (OLED), liquid crystal display (LCD), organic light-emitting transistor (OLET), surface-conduction electron-transmitter display (SED), field emission display (FED), digital light processing (DLP), liquid crystal on silicon (LCoC), or any other display technologies known in the art. In some embodiments, display 505 includes a touch sensitive surface configured to receive an input from a user to allow the user to interact with the touchless building control device 500 and provide a user input to the touchless building control device 500. In some embodiments, display 505 is configured to present visual media without requiring a backlight. As shown, display 505 is an electrophoretic display which uses energy only when changing state (e.g., when changing the visual media on display 505), and thereby uses significantly less energy than a backlit display. In some embodiments, display 505 is an electrophoretic display which significantly reduces the power requirements of the touchless building control device 500 when compared to other display technologies used in the art.
In some embodiments, display face 507 is angularly offset from the mounting surface 502 and mounting face 504 by an angle, shown as display angle 509, according to some embodiments. In some embodiments, the display angle 509 is selected based on the dimensions of the display 505, Americans with Disabilities Act (ADA) standards, and other codes or regulatory standards. For example, in some embodiments, the distal end 511 of display face 507 should not exceed 4 inches from the mounting surface 502 to comply with an ADA standard. In some embodiments, the display angle 509 is between 5 degrees and 90 degrees. In some embodiments, the display angle 509 is between 20 degrees and 35 degrees. In some embodiments, the display angle 509 is 33 degrees. In some embodiments, the protrusion distance 512 is defined between the mounting surface 502 to the furthest portion of touchless building control device 500 from mounting surface 502. In some embodiments, touchless building control device 500 is configured so that protrusion distance 512 is less than 4 inches. In some embodiments, protrusion distance 512 is equal to or greater than 4 inches. As shown in FIGS. 5-8 , the display angle 509 is 33 degrees, the display 505 is a 7.8 inch electrophoretic display, and distal end 511 is less than 4 inches from the mounting face 504 to comply with an ADA standard, according to some embodiments. A person having ordinary skill in the art will appreciate that a number of possible dimensions of display 505 and combinations with display angle 509 exist which comply with ADA standards, according to some embodiments. In some embodiments, distal end 511 extends beyond 4 inches (e.g., 5 inches, 6 inches, 1 foot, etc.) from mounting surface 502.
Still referring to FIGS. 5-8 , touchless building control device 500 is shown to further include a third face, shown as sensor face 515. In some embodiments, sensor face 515 is angularly offset from mounting face 504 by sensor angle 517. As shown, the sensor face 515 and the sensor face 515 are angularly offset by an angle, shown as outer angle 519. In some embodiments, the sum of display angle 509, sensor angle 517, and outer angle 519 is 180 degrees. In some embodiments, outer angle 519 is 90 degrees. In some embodiments, outer angle 519 is less than or greater than 90 degrees to comply with codes and standards (e.g., current ADA standards, etc.), or to accommodate a desirable sensor angle 517 and a desirable sensor angle 509. For example, a sensor angle 517 of 57 degrees may advantageously allow sensors disposed in sensor face 515 to detect a user within a desirable proximity to the touchless building control device 500. In some embodiments, the intersection between display face 507 and sensor face 515 is curved or rounded, shown as outer radius 520. In some embodiments, display face 507 and sensor face 515 are joined by one or more intermediate faces or radii. As shown, the side profile of the touchless building control device 500 is substantially triangular (see, e.g., FIG. 8 ). In some embodiments, the side profile of the touchless building control device 500 is substantially trapezoidal shaped, or may have a different profiles such that the display 505 is angularly offset from the mounting face 504.
In some embodiments, sensor face 515 includes an aperture, window, or other material for a first sensor, shown as occupancy sensor 530 (e.g., proximity sensor, motion detector, etc.), to sense within the local environment. Occupancy sensor 530 may be one or more of a passive infrared sensor (PIR sensor), passive infrared detector (PID), ultrasonic sensor, radar sensor, microwave sensor, camera-based sensor, tomographic motion detector, or still another suitable sensor or detector for detecting a user nearby the touchless building control device 500 or within the conditioned space (e.g., conditioned space 402). In some embodiments, the occupancy sensor 530 is configured to filter the motion detected by occupancy sensor 530 within the detectable range of occupancy sensor 530. In some embodiments, the touchless building control device 500 may be in communication with one or more occupancy sensors 530 configured to monitor occupancy within the environment controlled by touchless building control device 500 (e.g., conditioned space 402).
Referring now to FIG. 6 , sensor face 515 is shown to further include a second sensor, shown as identification sensor 532, and a photonic device (e.g., light manipulating device, light generating device, etc.), shown as light emitting device 534, according to some embodiments. In some embodiments, identification sensor 532 is configured to detect an identifier or identifiable characteristic of the user. For example, identification sensor 532 may be configured to identify a user by one or more of radio-frequency identification (RFID), facial recognition, retina scanning, a short range wireless technology such as Bluetooth, barcode scanner, QR scanner, or other touchless identification methods. In some embodiments, the user carries a transmitter, transponder, beacon, or other wirelessly identifiable device (e.g., passive RFID tag, active RFID Tag, short range wireless beacon, wireless transmitter, etc.) configured to interact with or be detected by identification sensor 532. In some embodiments, identification sensor 532 is configured for radio-frequency identification and includes RFID reader software and hardware (e.g., one or more scanning antenna coupled to one or more transceiver). In some embodiments, user identification is associated with a passive transponder carried by the user. In some embodiments, the identification sensor 532 detects one or more identifiers or identifiable characteristics about a user (e.g., a RFID transponder and a short range wireless beacon). In some embodiments, the touchless building control device 500 includes one or more identification sensor 532. For example, touchless building control device 500 may include an identification sensor 532 on the sensor face 515 for identifying a user using RFID, and a second identification sensor 532 on the display face 507 for identifying a user using facial recognition or retina scanning. In some embodiments, identification sensor 532 may be used to determine occupancy (e.g., presence of a user) in place of or in combination with occupancy sensor 530.
In some embodiments, light emitting device 534 is one or more of a light emitting diode (LED), laser diode, or other light emitting source. In some embodiments, light emitting device 534 is configured to emit various spectra of light. In some embodiments, light emitting device 534 is configured to emit various colors of visible light. For example, light emitting device 534 may produce visible light having a wavelength between approximately 400 nanometers and 700 nanometers, according to some embodiments. For example, the light emitting device may be configured to emit red, orange, yellow, blue, green, purple, and other colors of visible light. In some embodiments, light emitting device 534 is a series of addressable LEDs (e.g., a LED strip, LED string, LED panel, LED array, etc.) such that each LED can vary in color and intensity independently of the other LEDs.
In some embodiments, touchless building control device 500 includes a ring 540 which extends around display face 507 and sensor face 515. Ring 540 may include materials such as glass, plastic, metal, or any other suitable material. In some embodiments, ring 540 surrounds a protective element (e.g., cover), shown as cover 542. Cover 542 may extend across display face 507 and sensor face 515 to cover (e.g., shield, protect, etc.) display 505, occupancy sensor 530, identification sensor 532, and/or light emitting device 534, according to some embodiments. In some embodiments, cover 542 is at least one of a glass, plastic, or other transparent or translucent material. In some embodiments, cover 542 may protect the display 505 and sensors 530, 532 and light emitting device 534 from damage (e.g., scratching, gouging, debris, etc.). In some embodiments, cover 542 is configured to detect a user applying a force or touching the display face 507 of the touchless building control device 500. In such embodiments, the cover 542 may include a resistive interactive surface (e.g., resistive touchscreen, resistive touchpad), surface acoustic interactive surface, capacitive interactive surface (e.g., capacitive touch button, capacitive touchscreen, etc.), surface capacitance interactive surface, touchpad, or still another sensor suitable to detect a user touching or applying a force to cover 542. In some embodiments, cover 542 includes a touch-sensitive panel. In some embodiments, touchless building control device 500 is configured to indicate that display 505 is not a touchscreen in response to a user touching cover 542. In some embodiments, display 505 is a touchscreen and is configured to receive inputs from a user providing touch inputs to the display 505. In some embodiments, cover 542 includes apertures for one or more buttons, switches, or other user input sensors (e.g., cameras, infrared sensors, etc.).
Still referring to FIG. 6 , a portion of ring 540 near display 505 on display face 507 covers or includes a number of touchless sensors, shown as gesture sensors 544, according to some embodiments. Gesture sensors 544 may be configured to detect general or specific motions (e.g., gestures, etc.) of a user proximate touchless building control device 500, according to some embodiments. In some embodiments, gesture sensors 544 include one or more of a miniature radar system, camera, and electrical near-field sensor. In some embodiments, gesture sensor 544 is an electrical near field proximity sensor and ring 540 is a nonconductive material. In some embodiments, ring 540 includes one or more apertures to accommodate one or more cameras to detect one or more motions of a user nearby the touchless building control device 500 (e.g., gestures). For example, a user may provide an input to the touchless building control device 500 by moving a portion of their body (e.g., a hand, an arm, a prosthetic appendage, etc.) in a specific motion (e.g., across, away from, upward, downward, etc.) near touchless building control device 500 and gesture sensors 544 may be configured to detect and identify the motion of the user. Motion detected and identified by gesture sensors 544 may be a user input to the touchless building control device 500, according to some embodiments.
In some embodiments, ring 540 includes apertures for one or more buttons (e.g., buttons, switches, push-buttons, toggle buttons) which allow a user to interact with and provide a user input to the touchless building control device 500. In some embodiments, touchless building control device 500 includes one or more dials, knobs, switches, and touch-sensitive surfaces which are positioned and configured to allow a user to interact with and/or provide a user input to the touchless building control device 500.
In some embodiments, touchless building control device 500 includes a fourth sensor, shown as microphone 546 configured to detect auditory signals (e.g., vocalizations, clapping, snapping, etc.) generated by a user. In some embodiments, microphone 546 is disposed on ring 540. In some embodiments, touchless building control device 500 includes one or more microphone 546 configured to detect a position of a user.
Now referring to FIG. 8 , ring 540 includes a second photonic device, shown as light emitting portion 550. Light emitting portion 550 may be one or more light emitting diode (LED), laser diode, or other light emitting device. In some embodiments, the light emitting portion 550 is configured to emit light onto mounting surface 502. Light emitting portion 550 may extend around touchless building control device 500 on a surface of ring 540, according to some embodiments. In some embodiments, light emitting portion 550 may direct light through a portion of touchless building control device 500 (e.g., through ring 540). In some embodiments, light emitting portion 550 may direct light onto mounting surface 502 near the perimeter of mounting face 504. In some embodiments the light emitting portion 550 may extend along a surface of ring 540. In some embodiments, the light emitting portion 550 may be similar to light emitting device 534 and may include one or more of an addressable and/or multicolored LED array. In some embodiments, light emitting portion 550 may be located on an internal surface of the touchless building control device 500 such that light emitted from light emitting portion 550 is directed through or towards a portion of touchless building control device 500 (e.g., through ring 540, cover 542, etc.). In some embodiments, the light emitting portion 550 and light emitting device 534 is configured to indicate (e.g., by a color of light, by an intensity of light, etc.) a status or state of sensors 530, 532, 544, 546. For example, light emitting portion 550 and light emitting device 534 may emit various colored light having various intensity near a portion of the touchless building control device 500 nearest the user providing an input. In such example, light emitting portion 550 and light emitting device 534 may emit a color or intensity of light which indicates, follows, or mimics (i) the motion detected by gesture sensors 544, (ii) the location, intensity or volume of a sound detected by one or more microphones 546, (iii) a proximity or presence of a user detected by occupancy sensor 530, and/or (iv) a status or state of the identification sensor (e.g., scanning, identifier detected, etc.).
Referring now to FIGS. 5-8 , touchless building control device 500 is shown to include sidewalls 560. Sidewalls 560 may be integrally formed with mounting face 502, according to some embodiments. In some embodiments, sidewalls 560 are made from a metal. In some embodiments, sidewalls 560 are made from a heat conducting material which may transfer heat (e.g., heat generated by electronics within touchless building control device 500, etc.) away from the interior of the touchless building control device 500. In some embodiments, sidewalls 560 include a number of apertures (e.g., holes, through holes, slotted holes, etc.), shown as slots 562, which allow surrounding gasses (e.g., air) to pass through. In some embodiments, touchless building control device 500 includes one or more sensors for sensing ambient conditions (e.g., temperature, humidity, ambient light, etc.), shown as ambient condition sensor 563. In some embodiments, ambient condition sensor 563 may determine an ambient condition of gasses and fluids passing through slots 562. In some embodiments, slots 562 are configured to allow for convention (e.g., free convection, forced convection, etc.) of excess heat away from heat generating sources (e.g., electronics, a processor, a memory, a sensor, a resistor, etc.) contained between sidewalls 560. In some embodiments, touchless building control device 500 includes one or more audio output devices, shown as speaker 564. In some embodiments, speaker 564 is configured to produce auditory tones, sounds, messages, and other auditory signals perceivable by the user. In some embodiments, speaker 564 allows the touchless building control device 500 to provide feedback to the user in the form of auditory tones, sounds, messages, and or other forms of auditory signals. In some embodiments, speaker 564 is positioned between sidewalls 560. In some embodiments, speaker 564 may be disposed on display face 507, sensor face 515, or any intermediate surface therebetween.
In some embodiments, touchless building control device 500 includes a graphical user interface 570. Graphical user interface 570 includes an ambient condition, shown as temperature indication 572, a building equipment status, shown as HVAC system status 574, date and time information 576, and a logo 578 and touchless building control device location information 580. In some embodiments, temperature indication 572 indicates a temperature sensor value within the conditioned space. In some embodiments, HVAC system status 574 indicates the HVAC mode (e.g., heating, cooling, etc.) and a setpoint (e.g., 70 degrees, 60 degrees, etc.). In some embodiments, date and time information 576 includes a current date and time, which is updated periodically to reduce the required refresh rate of display 505. In some embodiments, logo 578 is the logo of the building the touchless building control device is deployed on. In some embodiments, the touchless building control device location information 580 is the location the touchless building control device is mounted within a building (e.g., a room, a building name, a floor, etc.).
Referring now to FIG. 9 , a pair of touchless building control devices 500 are mounted to a mounting surface 502, according to some embodiments. As shown, a first person, shown as tall user 902, a second person, shown as short user 904, and a seated person, shown as seated user 906 are all positioned on a horizontal surface, shown as floor 910. As shown, seated user 906 is seated in a chair, shown as wheelchair 908. In some embodiments, each user has a first facial plane, shown as eye level plane 901, a second facial plane, shown as head center plane 903. In some embodiments, eye level plane 901 is defined as a plane though a user's eyes extending from the front of the user's eyes to the back of the user's eyes. In some embodiments, head center plane 903 is defined as a plane through the center of the user's head and perpendicular to eye level plane 901. In some embodiments, a line of sight 905 (e.g., an effective line of sight, etc.) extends from an intersection between head center plane 903 and eye level plane 901 towards the display 505 of the touchless building control device 500. In some embodiments, display angle 509 is selected to position display axis 508 in a parallel direction to line of sight 905 for a wide range of users within a user access distance 907. In some embodiments, user access distance 907 is defined as a horizontal distance between head center plane 903 and the mounting surface 502. In some embodiments, user access distance 907 is defined as a distance wherein the touchless building control device is within an arm's reach (e.g., 1 feet, 2 feet, 3 feet, 4 feet, etc.) of the user. In some embodiments, user access distance 907 is not within an arm's reach of the BCD and may be determined based on the gesture detectable range 1104. For example, if gesture sensors 544 are cameras capable of detecting user motions at a distance of up to 10 feet away from the cameras, the user access distance 907 may be up to 10 feet. As shown in FIG. 9 , a user eye height 909 is defined between the eye level plane 901 and a plane containing outer radius 520 parallel to the floor 910. In some embodiments, tall user 902 is the height of a 95^thpercentile male (e.g., approximately 74 inches tall). In some embodiments, short user 904 is the height of a 5^thpercentile female (e.g., approximately 59 inches tall). In some embodiments, mounting height is defined as a distance between outer radius 520 and floor 910. In some embodiments, touchless building control device 500 is mounted at a first mounting height, shown as upper height 912. Upper height 912 may be approximately 60 inches, according to some embodiments. Upper height 912 may be suitable for tall user 902 and short user 904, but not for seated user 906, according to some embodiments. In some embodiments, a version of touchless building control device 500 may be configured to have a small (e.g., 1 degree, 5 degree, 10 degree, 13 degree, etc.) display angle 509 for mounting at upper height 912.
In some embodiments, touchless building control device 500 is mounted at a second mounting height, shown as accessible height 914. Accessible height 914 may be between 15 inches and 48 inches, according to some embodiments. In some embodiments, accessible height 914 is 36 inches. Accessible height 914 may be suitable for tall user 902, short user 904 and seated user 906. In some embodiments, accessible height 914 allows tall user 902, short user 904 and seated user 906 to view the display 505, and provide motion inputs (e.g., gesture inputs, gesture control, etc.) using a distal end 920 of a user's upper appendage 922. In some embodiments, display angle 509 is approximately 33 degrees when mounted at accessible height 914. In some embodiments, display angle 509 is equal to or greater than 15 degrees and less than or equal to 45 degrees. In some embodiments, display angle 509 is selected to allow a plane containing display 505 (e.g., display face 507) to be easily viewable by a variety of users (e.g., users 902, 904, 906, etc.). For example, in some embodiments, a display angle of approximately 33 degrees at an accessible height 914 of 36 inches may cause the display 505 to be substantially perpendicular when viewed by a variety of users (e.g., users 902, 904, 906) at a common distance (e.g., within an arm's reach, 3 feet, 2 feet, 4 feet, etc.) from the touchless building control device 500.
In some embodiments, touchless building control device 500 is mounted at a third mounting height, shown as lower height 916. Lower height 916 may be 15 inches, according to some embodiments. Lower height 916 may be suitable for seated user 906 and less suitable for tall user 902 and short user 904. In some embodiments, lower height 916 allows tall user 902, short user 904, and seated user 906 to view the display 505, and provide motion inputs (e.g., gesture inputs, gesture control, etc.) using a distal end 920 of a user's upper appendage 922 or a distal end 924 of a user's lower appendage 926 (e.g., a foot on a leg, etc.). As shown, touchless building control device 500 may be configured to have a large display angle 509 (e.g., 90 degree, 80 degree, 75 degree, etc.) to facilitate a user 902, 904, 906 viewing display 505 while the user 902, 904, 906 is in a standing or seated position near touchless building control device 500.
A person having ordinary skill in the art will appreciate that display angle 509 and display axis 508 are related, according to some embodiments. For example, modifying display angle 509 will change the direction of display axis 508 relative to mounting surface 502. In some embodiments, display angle 509 is selected for an average user at a user access distance 907 where the user does not need to strain (e.g., tilt their head, bend down, crouch, etc.) to view display 505. In some embodiments, an optimal display angle 509 can be determined based on an equation including variables representing user access distance 907, user eye height 909, and characteristics of line of sight 905 (e.g., a desirable angular offset amount of line of sight 905 from floor 910). In some embodiments, an optimal display angle 509 is selected for a representative average user (e.g., a user having an average height, arm length, etc.). In some embodiments, display angle 509 is selected so that line of sight 905 is substantially parallel to display axis 508 (e.g., within ±5 degrees, etc.). In some embodiments, display angle 509 is selected so that line of sight 905 is substantially parallel to display axis 508 when a user is at a user access distance 907 and has a comfortable head position. In some embodiments, a comfortable head position is defined as a position when eye level plane 901 is approximately parallel to the floor 910 (e.g., ±15 degrees, etc.).
Referring now to FIG. 10 , a touchless building control device 500 is mounted to a mounting surface 502. As shown, a user 1002 is within an occupancy detectable range 1004 of occupancy sensor 530. In some embodiments, the touchless building control device 500 is configured to activate (e.g., enable) identification sensor 532 upon the occupancy sensor 530 detecting an object (e.g., a user, animal, etc.) within occupancy detectable range 1004. As shown, user 1002 has a first identifiable object, shown as first transponder 1006 attached to a lanyard, a second identifiable object, shown as second transponder 1008 attached to a belt clip or in a front pocket, and a third identifiable object, shown as third transponder 1010 in a back pocket, wallet or bag. As shown in FIG. 10 , user 1002 is within identification detectable range 1012 of identification sensor 532. As shown, identification detectable range 1012 extends equally in all directions from touchless building control device 500. In some embodiments, identification detectable range 1012 does not extend equally in all directions from touchless building control device 500. In some embodiments, touchless building control device 500 is mounted to mounting surface 502 at accessible height 914 to position identification sensor 532 near the positions of transponders 1006, 1008, and 1010 (i.e. common locations of transponders on a user 1002), in addition to the various user accessibility conditions discussed herein.
Referring now to FIGS. 11 and 12 , a touchless building control device 500 is shown with a distal end of a user's appendage, shown as hand 1102, providing an input to the touchless building control device 500, according to some embodiments. In some embodiments, a user provides an input to the touchless building control device 500 by one or more detectable motions (e.g., gestures, movements, body positons, body orientations, etc.), shown as user motion 1204, within gesture detectable range 1104. As shown in FIG. 11 , hand 1102 is moved in a gesture detectable range 1104 of gesture sensors 544 in direction 1106. The gesture detectable range 1104 is a cumulative detection range including the detection range of each gesture sensor 544 disposed in ring 540, according to some embodiments. As shown, the gesture detectable range 1104 extends above, below, on top of, and to the sides of touchless building control device 500. Gesture detectable range 1104 is shown to have a left side 1108, a right side 1110, a top side 1112, a bottom side 1114, according to some embodiments. As shown, gesture detectable range 1104 extends into three dimensional space. Gesture detectable range 1104 may have one or more sides relating to a depth of the gesture detectable range (e.g., a side offset from the plane containing the display 505, etc.). In some embodiments, hand 1102 moves between left side 1108, right side 1110, top side 1112, and bottom side 1114 to interact with the touchless building control device 500. For example, as shown in FIG. 11 , hand 1102 may move horizontally in direction 1106 between left side 1108 and right side 1110 within gesture detectable range 1104 to supply an input to the touchless building control device 500.
In some embodiments, the touchless building control device 500 is configured to scroll between selectable options 1120 on graphical user interface 1124 displayed on display 505 when hand 1102 is moved between the right side 1110 and the left side 1108. For example, when hand 1102 is moved from left side 1108 to right side 1110 the graphical user interface 1124 may scroll the selectable options 1120 to the right (e.g., direction 1106). In some embodiments, the graphical user interface 1124 may display a cursor and a user may be able to manipulate the cursor position on graphical user interface 1124 using motion control (e.g., by moving hand 1102 within gesture detectable range 1104). As shown in FIG. 11 , graphical user interface 1124 includes motion suggestions, shown as gesture suggestions 1121. Gesture suggestions 1121 may be located on graphical user interface 1124 to instruct a user on how to interact with the gesture sensors 544. In some embodiments, touchless building control device 500 is configured to select a selectable option 1120 when hand 1102 moves from the bottom side 1114 to top side 1112 near the middle of the gesture detectable range 1104 (e.g., centered between left side 1108 and right side 1110). In some embodiments, touchless building control device 500 is configured to exit a selectable option 1120 or return to a menu display when hand 1102 is moved from top side 1112 to bottom side 1114 near the middle of the gesture detectable range 1104. In some embodiments, touchless building control device 500 is configured to adjust a temperature setting (e.g., setpoint r of FIG. 4A and FIG. 4B), when hand 1102 moves between top side 1112 and bottom side 1114 near left side 1108 or right side 1110. For example, touchless building control device 500 may be configured to lower a selectable value (e.g., temperature setting, humidity setting, light setting, etc.) when hand 1102 moves from top side 1112 to bottom side 1114 in the direction 1202 near left side 1108. In some embodiments, touchless building control device 500 is configured to raise a selectable value (e.g., temperature setting, humidity setting, light setting, etc.) when hand 1102 moves from bottom side 1114 to top side 1112 near the left side 1108 and/or right side 1110. A person having ordinary skill in the art will appreciate that a large number of gestures (e.g., motions of hand 1102) may be identifiable within gesture detectable range 1104, each of which configured to supply a desired input to touchless building control device 500. In some embodiments, gesture sensors 544 may comprise one or more camera (e.g., depth aware camera, time-of-flight camera, etc.), and gesture detectable range 1104 may be shaped differently than shown in FIG. 12 . In some embodiments, gesture sensors 544 may be a pair of stereo cameras which may detect light (e.g., visible light, invisible light) reflected off a portion of a user (e.g., user's skin, user's osseous matter, etc.) to detect one or more motions, positions, and or orientations of a user (e.g., a hand 1102 in a pointing or first position, an distal end 920 raised or pointed near touchless building control device 500, etc.).
In some embodiments, light emitting device 534 and/or light emitting portion 550 may emit light of varying intensity and color near hand 1102. For example, as shown in FIG. 11 , light emitting portion 550 is emitting a scrolling light 1130. In some embodiments, scrolling light 1130 may be a green colored light that is emitted along a top surface of the touchless building control device 500 by one or more light emitting portion 550. In some embodiments, the scrolling light 1130 may include a portion of high intensity which moves along the top surface of the touchless building control device 500 as hand 1102 moves across gesture detectable range 1104. For example, as shown in FIG. 11 , scrolling light 1130 has a high intensity portion 1132 and a standard intensity portion 1134. In such example, high intensity portion 1132 follows hand 1102 in the direction 1106. In some embodiments, touchless building control device 500 may be configured to cause light emitting portion 550 to flash or display colors to indicate a selection of a selectable option 1120. In some embodiments, touchless building control device 500 may be configured to display a blue colored light when a selectable value (e.g., temperature setting, humidity setting, light setting, etc.) is lowered. For example, touchless building control device 500 may be configured to display blue light of varying intensity along a left side of touchless building control device 500 with functionality similar to scrolling light 1130. In some embodiments, touchless building control device 500 may be configured to display light of one or more color on one or more sides of the touchless building control device 500 to provide feedback to the user of recognition of a gesture (e.g., motion of hand 1102) received by touchless building control device 500.
Referring now to FIG. 13 , a touchless building control device 500 is configured to receive a user input via a user device 1302, according to some embodiments. As shown, touchless building control device 500 is displaying an access code, shown as QR code 1304 on display 505. A user 1306 may scan QR code 1304 using a camera or scanning device (e.g., barcode scanner, etc.) on or coupled to user device 1302. In some embodiments, user 1306 scans QR code 1304 to enable wireless access to touchless building control device 500 using user device 1302. In some embodiments, user device 1302 can include any user-operable computing device such as smartphones, tablets, laptop computers, desktop computers, wearable devices (e.g., smart watches, smart wrist bands, smart glasses, etc.), and/or any other computing device. In some embodiments, user device 1302 may include hardware such as a touch-sensitive surface 1308, a processor, a memory, a device display 1310, a microphone, a button 1312, a camera 1314, a speaker 1316, a ambient condition sensor (e.g., ambient light sensor 1318), and other internal measurement sensors (e.g., gyroscopic sensor, accelerometer, magnometer, GPS, etc.). In some embodiments, speaker 1316 includes a speaker and a microphone. In some embodiments, device display 1310 may be configured to display images and/or text to a user 1306. In some embodiments, display 1310 is one or a combination of a CRT display, an LCD display, a plasma display, and/or an OLED display.
In some embodiments, wireless communication modules 1320, 1322 establish a direct connection (e.g., using a Bluetooth connection, wireless local access network, etc.) upon user device 1302 processing the information displayed by QR code 1304. For example, a user device 1302 may automatically open an application installed on the user device 1302 (e.g., in response to the QR code 1304 being read by the user device 1302) or may modify settings of the user device 1302 (e.g., wireless connection settings), to wirelessly connect with touchless building control device 500. In some embodiments, the user device 1302 opens a browser application installed on user device 1302 to view an interactive page hosted by touchless building control device 500. In some embodiments, a user supplies inputs to the user device 1302 to wirelessly receive, communicate, and manipulate data stored on touchless building control device 500 or associated with touchless building control device 500 (e.g., a temperature setting, a condition or state or setting of a HVAC system communicably coupled to the touchless building control device 500, an ambient condition state or setting, an access setting, a user setting, a user preference setting, etc.).
In some embodiments, wireless communication modules 1320, 1322 may establish a connection between touchless building control device 500 and user device 1302 using a network, shown as building network 1330. In some embodiments, building network 1330 includes a connection over a Wi-Fi network, a wired Ethernet network, a Zigbee network, a Bluetooth network, and/or any other wireless network. In some embodiments, building network 1330 may be a local area network or a wide area network (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.). The building network 1330 may include routers, modems, and/or network switches. Furthermore, the building network 1330 may be a combination of wired and wireless networks. For example, touchless building control device 500 may be wired to building network 1330, shown as wired connection 1321, and wirelessly connected, shown as wireless connection 1334. In some embodiments, wireless communication modules 1320, 1322 may establish a connection using a cellular network. The cellular network may be separate from the building network 1330 and may be a network for 2G, 3G, 4G, 5G, wireless communication. In some embodiments, building network 1330 may be configured to communicate with a cellular network.
Referring now to FIG. 14 , a user device 1302 is configured to receive a user input 1402, according to some embodiments. As shown, user device 1302 includes a device graphical user interface 1404 on device display 1310. Device graphical user interface 1404 includes selectable options 1410 which may be configured to display changes made by user input 1402 according to some embodiments. In some embodiments, user input 1402 is applied to the screen of the user device 1302, to a microphone of the user device 1302, a camera of the user device 1302, or a button of the user device 1302. In some embodiments, selectable options 1410 may be the same as or substantially similar to selectable options 1120. As shown in FIG. 14 , selectable options 1410 include a category system, including building-level selectable options 1412, zone-level selectable options 1414, and condition-level options 1416, according to some embodiments. In some embodiments, building-level selectable options 1412 include selectable options for a building, floor, zone, space, area, corridor, or other monitored, controlled, and/or conditioned locations. Each building-level selectable option 1412 has zone-level selectable options 1414, according to some embodiments.
In some embodiments, zone-level selectable options 1414 may include a thermal condition option, shown as temperature selectable option 1418, a ventilation condition option, shown as fan/ventilation option 1420, a humidity condition option 1422, an access/occupancy condition option 1424, a lighting condition option, shown as lights 1426, a motorized window condition option, shown as shades 1428, and still other suitable zone-level options. In some embodiments, each zone-level option 1414 may include condition-level options 1416. Condition-level options 1416 include condition specific adjustable parameters, according to some embodiments. For example, as shown in FIG. 14 , the temperature condition option 1418 includes a HVAC system status icon 1430, an environment condition status, shown as temperature 1432, an up button 1434, and a down button 1436. In some embodiments, a user may interact with up button 1434 and down button 1436 to provide a user input 1402 to the touchless building control device 500. In some embodiments, a user may interact with HVAC system status icon 1430 to provide a user input 1402 to the touchless building control device 500. In some embodiments, a user may interact with various building devices in communication with the touchless building control device 500 using user device 1302. In some embodiments, a user may manipulate various building devices (e.g., light devices, building appliances, smart devices, motorized equipment, IoT devices, HVAC equipment and devices, etc.) by interacting with condition-level options 1416.
Referring now to FIG. 15 , a satellite touchless building control device 1500 is shown, according to some embodiments. In some embodiments, satellite touchless building control device 1500 is substantially similar to or the same as touchless building control device 500. In some embodiments, satellite touchless building control device 1500 includes a display 1505, a display face 1507, a sensor face 1515, an outer radius 1520, which may be similar to or the same as display 505, display face 1507, sensor face 515, and outer radius 520, respectively. In some embodiments, occupancy sensor 1530, identification sensor 1532, light emitting device 1534, ring 1540 and cover 1542 are the same as or different than occupancy sensor 530, identification sensor 532, light emitting device 534, ring 540, and cover 1542. In some embodiments, satellite touchless building control device may be mounted or deployed within a same or different conditioned space (e.g., zone) as touchless building control device 500. In some embodiments, satellite touchless building control device 1500 is configured to monitor and control a conditioned space (e.g., zone) independently of touchless building control device 500. As shown, satellite touchless building control device 1500 has different proportions than touchless building control device 500. In some embodiments, display 1505 has a 4.3 inch electrophoretic display. In some embodiments, satellite touchless building control device 1500 has the same proportions as touchless building control device 500. In some embodiments, satellite touchless building control device 1500 does not include one or more of the features (e.g., gesture sensors 544, light emitting portions 550, microphone 546) described with respect to the touchless building control device 500 to reduce the size, material cost, manufacturing cost, power draw, and complexity of the satellite touchless building control device 1500, according to some embodiments. It is contemplated that one or more elements, features, or functions discussed with respect to touchless building control device 500 may be present in satellite touchless building control device 1500. Likewise, it is contemplated that one or more elements, features or functions discussed with respect to satellite touchless building control device 1500 may be present in touchless building control device 500.
In some embodiments, satellite touchless building control device 1500 includes a graphical user interface 1502 displayed on display 1505. The graphical user interface 1502 may display ambient condition information (e.g., temperature, air quality, humidity, etc.), building status information, HVAC system status information, or other information as desired by the user. As shown in FIG. 15 , graphical user interface 1502 includes temperature status 1504, a HVAC system status 1506, a fan condition 1508, a humidity status 1510, an air quality status 1512, and a ventilation status 1514. In some embodiments, graphical user interface 1502 displays one or more characteristics about other relevant information (e.g., a local weather, an upcoming schedule of the controlled room, etc.).
Referring now to FIG. 16 , a schematic diagram of network of touchless building control devices 500 and satellite touchless building control devices 1500 configured to monitor a building environment. As shown, first satellite touchless building control device 1500A and second satellite touchless building control device 1500B are communicably connected to a first touchless building control device 500A. In some embodiments, first satellite touchless building control device 1500A and second satellite touchless building control device 1500B are wirelessly connected to first touchless building control device 500A. In some embodiments, first satellite touchless building control device 1500A and second satellite touchless building control device 1500B are connected by a wired connection to first touchless building control device 500A. As shown, first satellite touchless building control device 1500A and second satellite touchless building control device 1500B are wirelessly connected to first touchless building control device 500A, indicated by a dashed line. As shown, third satellite touchless building control device 1500C is wirelessly connected to second touchless building control device 500B. In some embodiments, first touchless building control device 500A and second touchless building control device 500B are communicably connected to wireless network 1602 which may be the same as or different than building network 1330. In some embodiments, first touchless building control device 500A is connected to second touchless building control device 500B, or any number or combination of other touchless building control devices 500 and satellite touchless building control device's 1500. As shown, first touchless building control device 500A and second touchless building control device 500B are communicably coupled to building device 1604, according to some embodiments. Building device 1604 may be the same as or different than building device 411. In some embodiments, building device 1604 is one or more of a smart device connected to the wireless network 1602, a heating device or system, a ventilating device or system, a cooling device or system, a server, a database, a light emitting device, a sound emitting device, an IoT device, etc.
In some embodiments, a user may provide a satellite user input 1606 to the satellite touchless building control devices 1500A, 1500B, 1500C. Satellite user input 1606 may involve a user supplying a user input (e.g., a user input 1402) to a user device 1302 which communicates the input to the satellite touchless building control device 1500A, according to some embodiments. In some embodiments, satellite user input 1606 is communicated to the touchless building control device 500. In some embodiments, satellite user input 1606 is communicated to the wireless network 1602 and/or directly to a building device 1604. Satellite user input 1606 is received by a user device 1302 In some embodiments, first touchless building control device 500A, and second touchless building control device 500B, receive user input 1612. User input 1612 may be one or more inputs from a user motion 1614, a user device 1302, or an auditory command, shown as voice control 1616, according to some embodiments. In some embodiments, user device 1302 may include an application having mode and setpoint settings to change one or more ambient conditions based on a user's physical interaction with the user device 1302 or through other interaction including voice control (e.g., Google Home, Amazon Alexa). In some embodiments, user device 1302 tracks the location of a user using a GPS or other positioning system, and sends commands to the touchless building control device 500 and/or satellite touchless building control device 1500 based on system settings (e.g., a command to turn on lights upon user device 1302 entering a specific zone associated with a satellite touchless building control device 1500 or touchless building control device 500). User motions 1614 may be the same as or different than user motions 1204 and other motions discussed with respect to FIGS. 11 and 12 .
Referring now to FIG. 17 , a satellite touchless building control device 1500 is shown in an emergency operational mode 1700, according to some embodiments. As shown, graphical user interface 1702 may be the same as or different than graphical user interface 1124. In some embodiments, graphical user interface 1702 displays emergency information 1704 on display 1505. Emergency information 1704 is one or a combination of shapes, images, icons, and text about an emergency, according to some embodiments. For example, during an emergency (e.g., fire, natural disaster, power outage, lockdown, etc.) graphical user interface 1702 may display emergency information 1704 (e.g., instructions for occupants within the space associated with the satellite touchless building control device, status of the emergency, location of nearest exit, location of nearest shelter, etc.). In some embodiments, light emitting device 1534 outputs a visible light 1706 during an emergency. In some embodiments, satellite touchless building control device 1500 includes an internal power source or electrical energy storage device (e.g., battery, nickel-cadmium battery, lead-acid battery, lithium-ion battery, one or more capacitor, etc.), shown as battery 1708. Battery 1708 may be configured to supply power to the satellite touchless building control device 1500 during a loss of power. In some embodiments, satellite touchless building control device 1500 outputs an auditory instruction during operational mode 1700. Although emergency operational mode 1700 has been described with respect to satellite touchless building control device 1500, it is contemplated that emergency operational mode 1700 may be deployed on touchless building control device 500.
Referring now to FIG. 18 , a method 1800 of using a touchless building control device 500 is shown, according to some embodiments. In some embodiments, method 1800 includes an initiation step, shown as Receive Indication Of A User Located In The Conditioned Area step 1802, a display refresh step, shown as Update Electrophoretic Display step 1804, an identification step, shown as Identify User step 1806, a data retrieval step, shown as Load User Profile step 1808, a determining step (e.g., a comparative step), shown as Is User Authorized step 1810, an indication step following authorization, shown as Indicate User Is Authorized step 1812, an indication step following unsuccessful authorization, shown as Indicate User Is Unauthorized step 1814, a user input step, shown as Receive User Input step 1816, a processing step, shown as Process User Input step 1818, an output step, shown as Command Building Device 1820, and a update display step, shown as Display Conditioned Area Information On Electrophoretic Display step 1822.
At 1802, method 1800 may include detecting a user (e.g., user 902, 904, 906, 1002) using one or more sensors (e.g., occupancy sensor 530, identification sensor 532, gesture sensors 544, cover 542, etc.) which provide an indication (e.g., signal to a processing circuit) that a user 1002 is nearby the touchless building control device 500. For example, at least one of either occupancy sensor 530 and identification sensor 532 detect a user 1002 within occupancy detectable range 1004, or identification detectable range 1012, according to some embodiments. In some embodiments, touchless building control device 500 detects a user using the occupancy sensor 530. In some embodiments, light emitting device 534 and light emitting portions 550 may be configured to emit a visible light upon a user 1002 being detected.
At 1804, method 1800 may include updating graphical user interface 1124 on display 505 (e.g., an electrophoretic display) to display a status or condition of the conditioned area. For example, display 505 may be an electrophoretic display and may be configured to only refresh if a user is within the conditioned space or within a viewable range of display 505 to save power. In some embodiments, light emitting device 534 and light emitting portions 550 are configured to emit a visible light upon a user 1002 being detected to indicate a status or condition of the device (e.g., scanning condition, emergency operational mode, locked condition, etc.) to the user 1002.
At 1806, method 1800 may include activating identification sensor 532 to detect an identifier. In some embodiments, identification sensor 532 is configured to detect a RFID transponder, Bluetooth beacon, short range wireless beacon, wireless transmitter, a user's face, a user's retina, a physical characteristic of a user, etc. In some embodiments, identification sensor 532 includes one or more camera configured to gather a digital image of the user's face and transmit the image to a processing circuit which is configured to compare the digital image to a database of stored images associated with a user to identify the user.
At 1808, method 1800 may include loading a user profile (e.g., user settings, user preferences, user history, etc.) from a local or remote memory device (e.g., a memory device within building network 1330. The user profile includes settings for graphical user interface 1124 such as language settings, display unit settings (e.g., imperial or metric), text settings (e.g., font, font size, color), specific gestures or motion settings, color settings, light settings (e.g., from light emitting device 534 and light emitting portion 550) informational settings, a user's credentials, and other user specific or group specific information, according to some embodiments.
In some embodiments, an identifier (e.g., transponder 1006, 1008, 1010) is detected which does not have a user profile associated. In some embodiments, information about the detected identifier (e.g., transponder 1006, 1008, 1010) may be stored in a local or remote memory and may be associated with related data (e.g., a date and time the user was detected, information about the touchless building control device 500 and/or satellite touchless building control device 1500 that detected the identifier, etc.).
At 1808, method 1800 may include determining if a user is authorized to access touchless building control device 500. Touchless building control device 500 may compare the profile of the identified user to a local or remote database of user's authorized to access the touchless building control device 500. In some embodiments, access to touchless building control device 500 is granted to users though a tiered system, with each tier having access to a different set of building controls (e.g., building-level controls 1412, zone-level controls 1414, and condition-level controls 1416. For example, user having a highest level of access (e.g., tier 1 access) is able to access all of the building-level controls 1412, zone-level controls 1414, condition-level controls 1416, and administrative settings (e.g., settings for modifying a list of authorized users, settings for locking a touchless building control device 500, settings for manipulating touchless building control device 500 software such as updates, etc.), according to some embodiments. In some embodiments, a user having a second highest level of access (e.g., tier 2 access) is able to access building-level controls 1412, zone-level controls 1414, condition-level controls 1416, but not administrative controls. In some embodiments, a user having a third highest level of access (e.g., tier 3 access) may be able to access zone-level controls 1414 and condition-level controls 1416. In some embodiments, a user having a fourth highest level of access (e.g., tier 4 access) may be able to access only specific zone level controls such as lights 1426 and shades 1428. In some embodiments, a user having a lowest level of access (e.g., tier 5 access), may not be able to access building-level controls 1412, zone-level controls 1414, or condition-level controls 1416, but is able to view the current status, state, and criteria of the conditioned area and can submit requests to a user having higher level access (e.g., tier 1 access) to have touchless building control device 500 settings changed (e.g., temperature 1432).
In some embodiments, a user is not associated with a touchless building control device 500 system. In some embodiments, a non-associated user (e.g., a user is identified but no user profile exists within the touchless building control device system) is denied access to touchless building control device 500. For example, a building visitor, an intruder, or an unauthorized user may attempt to interact with touchless building control device 500. In such example, identification sensor 532 gathers an identifiable characteristic (e.g., RFID badge, Bluetooth beacon information, short range wireless beacon information, etc.) from the user and the touchless building control device 500 system determines that the user is unauthorized, and may refuse to unlock the touchless building control device 500. In some embodiments, the touchless building control device 500 compares the identifiable characteristic to a database of user information and associated identifiers.
In some embodiments, touchless building control device 500 is configured to receive an input from all users without identifying the user. In some embodiments, the touchless building control device 500 is configured to receive an input from all users and determines and stores an identifiable characteristic (e.g., an image of the user's face, a Bluetooth beacon, a RFID transponder, etc.) for each user that interacts with the touchless building control device 500.
At 1812, method 1800 may include the touchless building control device 500 producing an indication that the user identified in step 1806 is authorized, and unlocking the touchless building control device 500. Unlocking the touchless building control device 500 may involve enabling the BCD to receive a user input. The indication that the user identified in step 1806 is authorized includes light emitting device 534 and/or light emitting portions 550 emitting visible light, an auditory signal being emitted from the speaker 564, and/or graphical user interface 1124 being updated, according to some embodiments. In some embodiments, graphical user interface 1124 is updated with instructions (e.g., gesture suggestions 1121) or a unique access code (e.g., QR code 1304) and/or control options (e.g., selectable options 1120), according to some embodiments.
At 1814, method 1800 may include the touchless building control device 500 producing an indication that the user identified in step 1806 is not authorized. The indication that the user identified in step 1806 is not authorized includes light emitting device 534 and/or light emitting portions 550 emitting visible light, an auditory signal being emitted from the speaker 564, and graphical user interface 1124 being updated with instructions (e.g., contact information of a user with administrative rights), according to some embodiments.
At 1816, method 1800 includes the touchless building control device 500 activating gesture sensors 544 to monitor and record motion within the gesture detectable range 1104, communicating with user device 1302, and/or receiving auditory signals (e.g., voice commands) from the user, according to some embodiments.
At 1818, method 1800 may include the touchless building control device 500 processing user input 1612. In some embodiments, processing user input 1612 involves storing the user input in a local or remote memory, outputting an indication of the user input being received (e.g., emitting a visible light from light emitting device 534 and/or light emitting portion 550 near hand 1102), and/or processing the user input using a learning device (e.g., lighting scheduling system, HVAC scheduling system, etc.). In some embodiments, the touchless building control device 500 compiles a number of commands for a building device 1604 received by a number of touchless building control devices 500 or satellite touchless building control devices 1500. For example, first touchless building control device 500A, may compile a number of user inputs received by satellite touchless building control device 1500A and/or satellite touchless building control device 1500B.
At 1820, method 1800 may include the touchless building control device 500 outputting a command to a building device 1604. In some embodiments, the command is a setpoint and may be sent by a wired and/or wireless connection. In such embodiments, the setpoint may be processed by a circuit on the building device 1604 receiving the setpoint (e.g., a HVAC unit, smart lighting device, smart device, Iot device, etc.) to generate commands to achieve the desired setpoint. In some embodiments, the setpoint is processed on a circuit within the touchless building control device 500 and commands are sent from the touchless building control device 500 to the building device 1604.
At 1822, method 1800 may include the touchless building control device 500 updating display 505 (e.g., electrophoretic display), to display conditioned area information (e.g., temperature 1432, lighting condition, etc.) or a setpoint value received by the touchless building control device 500.

HVAC System and Building Device Control Using Touchless Building Control Devices

Referring now to FIG. 19 , a system 1900 including the satellite touchless building control device 1500, a touchless building control device 500, a HVAC unit 1912, and a building device 1604 is shown, according to an exemplary embodiment. The satellite touchless building control device 1500 may wirelessly communicate with devices of the system 1900 and/or may not be configured to, communicate with the HVAC unit 1912. In some embodiments, the satellite touchless building control device 1500 is configured to communicate wirelessly via a network, with the touchless building control device 500.
The HVAC unit 1912 can be equipment configured to heat and/or cool a building. For example, the HVAC unit 1912 can be the HVAC equipment 404 described in relation to FIGS. 4A and 4B. The satellite touchless building control device 1500 can wirelessly provide a control signal to the touchless building control device 500 which the touchless building control device 500 can be configured to utilize to operate the HVAC unit 1912. The satellite touchless building control device 1500 can utilize a sensed temperature, sensed by the satellite touchless building control device 1500 or by another sensor, e.g., sensor data received wirelessly from the remote sensors 1914, and generate a control decision for the HVAC unit 1912. The decision may be to turn on one or multiple heating or cooling stages, turn on or off a fan, etc. The touchless building control device 500 can be configured to receive the commands and operate the HVAC unit 1912.
In some embodiments, the touchless building control device 500 can receive sensor data from remote sensors 1914 (or the satellite touchless building control device 1500) and/or a setpoint from the user device 1302. In this regard, the touchless building control device 500 can be configured to generate control decisions and operate the HVAC unit 1912 based on the control decisions.
In some embodiments, as described herein, a user can provide a setpoint or other operating setting to the satellite touchless building control device 1500, or touchless building control device 500 wirelessly via the user device 1302. Furthermore, the user device 1302 can provide the setpoint and/or other operating setting to the remote platform 1911 via a cellular network 1916 and/or via any other kind of wireless and/or wired communication. The remote platform 1911 can be configured to process the setpoint and/or any other environmental data collected by the satellite touchless building control device 1500 and/or the remote sensor 1914 and generate control decisions for operating the HVAC unit 1912. The remote platform 1911 can be configured to communicate the control decisions to the touchless building control device 500 and the touchless building control device 500 can be configured to implement the control decisions by operating the HVAC unit 1912.
The touchless building control device 500 includes an online controller 1904, an offline controller circuit 1906, a local network radio circuit 1908, and a cellular network radio circuit 1910. FIG. 19 is shown to include dashed and dotted lines between the devices of the system 1900. The dashed lines may indicate a building network which may or may not have access to an external network e.g., the Internet. The building network may be a Wi-Fi network, a wired Ethernet network, a Zigbee network, a Bluetooth network, and/or any other wireless network. The building network may be a local area network or a wide area network (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.). The building network may include routers, modems, and/or network switches. Furthermore, the network may be a combination of wired and wireless networks. The dotted lines indicate communication with a cellular network 1916. The cellular network 1916 may be separate from the building network and may be a network for 2G, 3G, 4G, 5G, wireless communication. The local network radio circuit 1908 can be configured to cause the touchless building control device 500 to communicate via the building network while the cellular network radio circuit 1910 can be configured to cause the touchless building control device 500 to communicate via the cellular network 1916.
The online controller 1904 can be configured to control the HVAC unit 1912 when the touchless building control device 500 is online, i.e., it is connected to the building network. The online controller 1904 can be configured to implement control signals received from the satellite touchless building control device 1500, control signals determined by and received from the user device 1302, control signals determined by and/or received from the remote platform 1911, and/or control signals received from sensors on the touchless building control device 500. Furthermore, the online controller 1904 can be configured to generate control signals based on sensor data and/or operating parameters (e.g., setpoints) received from the remote sensor 1914, the satellite touchless building control device 1500, the user device 1302, and/or the cellular network 1916 (e.g., the remote platform 1911).
The offline controller circuit 1906 can be configured to act as a logic backup when the building network and/or the cellular network 1916 and/or the cellular network radio circuit 1910 is not operating properly or is not present. The offline controller circuit 1906 can include control logic for operating the HVAC unit 1912.
In some embodiments, the touchless building control device 500 can be configured to communicate with the cellular network 1916 to receive control signals, setpoints, and/or environmental conditions for operating the HVAC unit 1912. The cellular network radio circuit 1910 can be a data metered device such that only when the cellular network radio circuit 1910 is communicating with the cellular network 1916 does a cellular network provider incur costs. In this regard only in the event of an emergency may the cellular network radio circuit 1910 be operated by the offline controller circuit 1906 to collect data required to operate the HVAC unit 1912. In some embodiments, the offline controller circuit 1906 receives an outdoor ambient temperature from the remote platform 1911 via the cellular network 1916 via the cellular network radio circuit 1910 and performs and estimation of an indoor temperature based on a length of known time that the HVAC unit 1912 has been operating and at what operating parameters. Based on the estimate, the offline controller circuit 1906 can operate the HVAC unit 1912 to be at a comfortable (e.g., at a setpoint) or safe environmental condition.
Furthermore, in the event of an outage of the building network, the user device 1302 can provide control signals, setpoints, and/or temperature measurements to the touchless building control device 500 directly, e.g., via the cellular network 1916. For example, the user device 1302 can provide a setpoint directly to the touchless building control device 500 or can provide the setpoint to the remote platform 1911 which can in turn communicate the setpoint to the touchless building control device 500 via the cellular network 1916. In some embodiments, the touchless building control device 500 is included directly with the HVAC unit 1912 so that the devices of the system 1900 can communicate directly with the HVAC unit 1912. In some embodiments, the touchless building control device 500 is separate from the HVAC unit 1912 is connected to the HVAC unit 1912 via one or more physical control wires.
Referring now to FIG. 20 , the touchless building control device 500 and the user device 1302 are shown in greater detail to implement collection and display of building control device data, according to some embodiments. The touchless building control device 500 includes a processing circuit 2002, a processor 2004, and a memory 2006. The processor 2004 can be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. The processor 2004 may be configured to execute computer code and/or instructions stored in the memory 2006 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).
The memory 2006 can 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 2006 can 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 2006 can 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 2006 can be communicably connected to processor 2004 via the processing circuit 2002 and can include computer code for executing (e.g., by the processor 2004) one or more processes described herein.
The user device 1302 is shown to include a processing circuit 2020. The processing circuit 2020 may be the same as and/or similar to the processing circuit 2002. Furthermore, the processing circuit 2020 includes a processor 2022 and a memory 2024. The processor 2022 may be the same as and/or similar to the processor 2004. Furthermore, the memory 2024 may be the same as and/or similar to the memory 2006.
The memory 2006 is shown to include an HVAC controller 2008. The HVAC controller 2008 is configured to operate building equipment (e.g., the HVAC unit 1912, building devices 1917), in some embodiments. The HVAC controller 2008 is configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control the building equipment. The control decisions determined by the HVAC controller 2008 can be transmitted to the building equipment via the wireless radio circuit 2014. In some embodiments, the wireless radio circuit 2014 includes one or more receivers, transceivers, and/or transmitters and can communicate with building equipment (e.g., with the touchless building control device 500).
The memory 2006 can include a building control device data manager 2010. The building control device data manager 2010 is configured to collect data for the touchless building control device 500 (e.g., sensor measurements of the satellite touchless building control device 1500 and touchless building control device 500, e.g., temperature, humidity, air quality, user settings, user profiles, lists of authorized users and associated identifiers, etc.). The building control device data manager 2010 can further be configured to collect operational data (e.g., control decisions, fault data, etc.) and/or settings (e.g., received set points, user inputs, user profiles changes, user settings, user credentials, authorized user database settings, etc.).
The building control device data manager 2010 is configured to transmit touchless building control device data to the wireless network 2000 via the wireless radio circuit 2014. The touchless building control device data may be any of the data collected by the building control device data manager 2010. In some embodiments, the building control device data manager 2010 periodically transmits the touchless building control device data to the wireless network 2000. In some embodiments, the building control device data manager 2010 transmits touchless building control device data in response to receiving a confirmation indication for the user device 1302 indicating that the user device 1302 is present and communicating via the wireless network 2000.
In some embodiments, the building control device data manager 2010 divides the touchless building control device data into multiple packages. The building control device data manager 2010 can be configured to broadcast the packages one at a time at a predefined interval. In this regard, the user device 1302 can listen for the broadcast, collect the packages, and reconstruct the original touchless building control device data. The memory 2006 includes an identifier transmitter 2012. The identifier transmitter 2012 can be configured to cause the wireless radio circuit 2014 to transmit a unique identifier by broadcasting the identifier. The unique identifier can be broadcast by the identifier transmitter 2012 at a predefined interval. In some embodiments, the user device 1302 utilizes the identifier to communicate with the remote platform 1911 to authenticate with the remote platform and/or retrieve touchless building control device data of the touchless building control device 500. The building control device data manager 2010 can be configured to send the touchless building control device data to the remote platform 1911 via the wireless network 2000. The remote platform 1911 can be configured to store the wireless data associated with the identifier of the touchless building control device 500 and provide the thermostat data to the user device 1302 upon request.
In some embodiments, the memory 2006 includes an input manager 2009. The input manager 2009 may manage sensors on the touchless building control device 500 such as the occupancy sensor 530, identification sensor 532, and gesture sensors 544. In some embodiments, the input manager is configured to processing signals from the sensors on the touchless building control device 500 into specific inputs (e.g., process a user motion into a change on graphical user interface 1124), and outputting status indications of the touchless building control device 500 on output devices such as the display 505, graphical user interface 1124, light emitting device 534, light emitting portion 550, and speaker 564. In some embodiments, input manager 2009 manages the sensors communicably coupled to the processing circuit 2002 such as the occupancy sensor 530, identification sensor 532, gesture sensors 544, and microphone 546.
The memory 2024 includes the thick client 2028, the server client 2030, the thin client 2032, the filter 2034, and an interface manager 2036, according to some embodiments. The thick client 2028 can be configured to receive the touchless building control device data broadcast by the touchless building control device 500 on the wireless network 2000 over time and reconstruct the original package deconstructed by the touchless building control device 500. The thin client 2032 includes the filter 2034 which can filter data broadcast by multiple different touchless building control device 500 (or satellite touchless building control device 1500).
In some embodiments, the user device 1302 includes a user interface 2016. The user interface 2016 is one or a combination of a CRT display, an LCD display, an LED display, a plasma display, and/or an OLED display, according to some embodiments. In some embodiments, the user interface 2016 is a capacitive touch screen display and/or a resistive touch screen display. The memory 2024 is shown to include an interface manager 2036 configured to receive the thermostat data from the thick client 2028, the server client 2030, and/or the thin client 2032. Based on the received data, the interface manager 2036 can be configured to generate an interface and cause the user interface 2016 to display the interface. In some embodiments, the interface allows for input of various setpoint and/or setting changes. The interface manager 2036 can cause the wireless radio circuit 2018 to transmit the setpoint and/or setting changes to the touchless building control device 500, according to some embodiments. In some embodiments, the touchless building control device 500 receives the setpoint and/or setting changes and operates based on the received data.
Referring to FIG. 21 , an HVAC system 2100 for a building 2190 is shown. The HVAC system 2100 may include an HVAC unit 2110 configured to control an ambient condition of the one or more rooms of the building 2190 based on information from one or more sensors 2150 and a touchless building control device 500. In an example, an ambient condition may be a temperature or a humidity level of one or more rooms of the building 2190. As shown by FIG. 21 , the HVAC unit 2110 may be external to the building 2190. Alternatively, in some aspects, one or more components (e.g., air conditioning (A/C) unit 2112, furnace 2114, blower 2116, humidifier/dehumidifier 2118, communications component 2130, or controller 2140) may be located in different locations including inside the building 2190. The building may be a home, office, or any other structure that includes uses an HVAC system for controlling one or more ambient conditions of the structure.
In an aspect, the HVAC system 2100 may include supply ducts 2120 and return ducts 2124 installed within the building 2190 and coupled with the HVAC unit 2110. The supply ducts 2120 may supply air to the building 2190, and the return ducts 2124 may return air from the building 2190. The supply ducts 2120 may receive supply air through one or more of intakes 2128 that provide outside air to the HVAC system 2100 and/or may recycle return air from the return ducts 2124. The supply ducts 2120 may output the supply air at one or more of the rooms of the building 2190 via one or more supply vents 2122. The return ducts 2124 may receive return air from the building 2190 via the return ducts 2124 to balance air within the building 2190. The return air may be input into the return ducts 2124 via one or more return vents 2126.
The HVAC unit 2110 may include one or more of an air conditioning unit 2112, a furnace 2114, a blower 2116, a humidifier/dehumidifier 2118, or any other component (e.g., heat pump) for adjusting an ambient condition of a room of the building 2190. The air conditioning unit 2112 may be configured to cool the supply air by passing the supply air through or around one or more cooled pipes (e.g., chiller pipes) to lower a temperature of the supply air. The furnace 2114 may be configured to warm the supply air by passing the supply air through or around one or more warmed pipes (e.g., heating coils) to raise a temperature of the supply air. The blower 2116 may be configured to blow the supply air through the supply ducts 2120 to the building 2190 and pull the return air from the building 2190. The humidifier 2118 may be configured to add moisture to the supply air. A dehumidifier 2118 may be configured to reduce moisture in the supply air. While the humidifier/dehumidifier 2118 is shown as a single unit, these units may be separate units. Alternatively to a dehumidifier 2118, aspects of dehumidification may be performed through other methods including use of the air conditioning unit 2112 to dehumidify the supply air.
The HVAC unit 2110 may also include a communications component 2130 configured to communicate with the one or more sensors 2150 and/or one or more touchless building control device 500. In an aspect, the communications component 2130 may communicate with the one or more sensors 2150 and/or the touchless building control device 500 via one or more communications links 2132. In an example, the communications component 2130 may include one or more antennas, processors, modems, radio frequency components, and/or circuitry for communicating with the sensor 2150 and/or the touchless building control device 500. The one or more communications links 2132 may be one or more of a wired communication link or a wireless communication link.
The HVAC system 2100 may also include the sensors 2150 located within one or more rooms of the building 2190 and/or within or near the supply vents 2122. One or more sensors 2150 may be configured to detect an ambient condition such as a temperature or a humidity level of the room where the sensor 2150 is located. Each of the sensors 2150 may provide sensor information 2180 to the HVAC unit 2110. Examples of a sensor 2150 may include a temperature sensor, a humidity sensor, or any sensor configured to detect an ambient condition of one or more rooms of the building 2190.
The HVAC system 2100 may also include the touchless building control device 500 configured to communicate with the HVAC unit 2110. The touchless building control device 500 may include an HVAC application 2162 configured to display, adjust, and store setpoint information (“info”) 2164 indicating desired user settings for one or more rooms of the building 2190. In an example, the setpoint information 2164 may include heating/cooling settings 2166 indicating one or more desired temperatures (e.g., minimum and/or maximum room temperatures) for one or more rooms of the building and/or humidity settings 2168 indicating a desired humidity level for one or more rooms of the building 2190. The touchless building control device 500 may provide the setpoint information 2164 to the HVAC unit 2110.
The HVAC unit 2110 may also include a controller 2140 configured to control the air conditioning unit 2112, the furnace 2114, the blower 2116, and the humidifier/dehumidifier 2118, based on the sensor information 2180 received from the sensor 2150 and the setpoint information 2164 received from the touchless building control device 500. The controller 2140 may communicate with the communications component 2130, the air conditioning unit 2112, the furnace 2114, the blower 2116, and/or the humidifier/dehumidifier 2118 via a communications bus 2134. The controller 2140 may include logic to operate the air conditioning unit 2112, the furnace 2114, the blower 2116, and the humidifier/dehumidifier 2118, based on the sensor information 2180 and the setpoint information 2164. The operation of the components of the HVAC unit 2110 may include one or more of an initiation time, a stop time, a run time, a power state, speed level, a heating/cooling level, and/or any other operational state of one or more of these components of the HVAC unit 2110.
In an aspect, the controller 2140 may include an operation control component 2142 to perform the logic of the controller 2140. The operation control component 2142 may include a monitoring component 2170 configured to monitor for and compare the setpoint information 2164 and the sensor information 2180. In an example, the monitoring component 2170 may include an information receiver 2172 configured to receive one or more of the setpoint information 2164 or the sensor information 2180. The monitoring component 2170 may also include a comparer 2174 configured to receive one or more of the setpoint information 2164 or the sensor information 2180 from the information receiver 2172 and determine a difference between the setpoint information 2164 (or stored setpoint information) and the sensor information 2180.
In an aspect, the operation control component 2142 may also include a system operator 2176 configured to determine one or more operational states for controlling one or more functions of the components (e.g., air conditioning unit 2112, furnace 2114, blower 2116, humidifier/dehumidifier 2118) of the HVAC unit 2110 and control the components based on the determined operations. For example, the system operator 2176 may determine one or more of an initiation time, a stop time, a run time, a power state, speed level, or a heating/cooling level, of one or more of the components and control the components according to the operational state(s).
In an example, the system operator 2176 may receive information on the difference between the setpoint information 2164 (or stored setpoint information) and the sensor information 2180 from the comparer 2174 and determine an operational state of the components. The system operator 2176 may compare the difference between the setpoint information 2164 (or stored setpoint information) and the sensor information 2180 and determine whether the difference is within a threshold range. The system operator 2176 may determine operational states based on a result of the determination.
Although HVAC unit 2110 has been described as having the controller 2140, in some embodiments, touchless building control device 500 includes the controller 2140, operation control component 2142, monitoring component 2170, information receiver 2172, comparer 2174, and system operator 2176, as described herein.
Referring to FIG. 22 , an example of a method 2200 for controlling an ambient condition of an area (e.g., one or more rooms of building 2190) by one or more components of the HVAC unit 2110 is provided. The method 2200 may implement the functionality described herein with reference to FIG. 21 and may be performed by one or more components of the HVAC unit 2110 as described herein with reference to FIG. 21 . In an example, the one or more components may include the air conditioning unit 2112, the furnace 2114, the blower 2116, or the humidifier/dehumidifier 2118.
At 2202, the method 2200 may include receiving sensor information from a wired or wireless sensor located in the area, the sensor information indicating the ambient condition of the area. For example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, or information receiver 2172) of the HVAC unit 2110 may receive the sensor information 2180 from the one or more sensors 2150, the sensor information 2180 may indicate an ambient condition (e.g., current temperature or humidity level of one or more rooms of building 2190) of an area (e.g., one or more rooms of building 2190) corresponding to a location of each sensor 2150. In an example, the HVAC unit 2110 may receive the sensor information 2180 from the one or more sensors 2150 wirelessly. In some embodiments, the HVAC unit 2110 receives sensor information 2180 from a sensor location on one or more touchless building control device 500 or satellite touchless building control device 1500.
At 2204, the method 2200 may also include receiving setpoint information from a touchless building control device, the setpoint information indicating a desired condition of the area. For example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or information receiver 2172) of the HVAC unit 2110 may receive setpoint information 2164 from the touchless building control device 500, the setpoint information 2164 may indicate a desired condition of the area. In an example the setpoint information 2164 may include heating/cooling settings 2166 and/or humidity settings 2168 indicating desired conditions of one or more rooms of the building 2190 as set by a user. In an example, the HVAC unit 2110 may receive the setpoint information 2164 from the touchless building control device 500 wirelessly.
At 2206, the method 2200 may include determining a difference between the ambient condition and the desired condition. For example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or comparer 2174) of the HVAC unit 2110 may determine a difference between the ambient condition and the desired condition. As an example, the one or more components of the HVAC unit 2110 may determine a difference between a current temperature or humidity level of a room of the building 2190 where the sensor 2150 is located and a heating/cooling setting 2166 or humidity setting 2168 received from the touchless building control device 500. In some embodiments, touchless building control device 500 may determine a difference between the ambient condition and the desired condition.
At 2208, the method 2200 may also include controlling the one or more components of the HVAC unit to adjust the ambient condition of the area based on the difference. For example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or system operator 2176) of the HVAC unit 2110 may control one or more components of the HVAC unit 2110 to adjust the ambient condition of one or more rooms of the building 2190 based on the difference.
In an aspect, the method 2200 may further include determining whether the difference is within a threshold range, and controlling the one or more components further based on whether the difference is within the threshold range. In an example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or system operator 2176) of the HVAC unit 2110 may determine whether the difference is within a threshold range, and control the one or more components (e.g., air conditioning unit 2112, the furnace 2114, the blower 2116, or the humidifier/dehumidifier 2118) further based on whether the difference is within the threshold range.
In some aspects, the method 2200 may also include determining an operational state, including one or more of an initiation time, a stop time, a run time, a power state, speed level, or a heating/cooling level, of the one or more components, and controlling the one or more components further based on the operational state. In an example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or system operator 2176) of the HVAC unit 2110 may determine an operational state, including one or more of an initiation time, a stop time, a run time, a power state, speed level, or a heating/cooling level, of the one or more components (e.g., air conditioning unit 2112, the furnace 2114, the blower 2116, or the humidifier/dehumidifier 2118), and control the one or more components further based on the operational state.
In another aspect, the method 2200 may include storing the setpoint information, in response to receiving of the setpoint information from the mobile device, determining second setpoint information, indicating a second desired condition of the area, was not received from the touchless building control device, and controlling the one or more components of the HVAC unit to adjust the ambient condition of the area in response to the second setpoint information not being received and based on the stored setpoint information. In an example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or system operator 2176) of the HVAC unit 2110 may store the setpoint information 2164, in response to receiving of the setpoint information 2164 from touchless building control device 500, determine second setpoint information 2164, indicating a second desired condition of the area, was not received from the touchless building control device 500, and control the one or more components (e.g., air conditioning unit 2112, the furnace 2114, the blower 2116, or the humidifier/dehumidifier 2118) of the HVAC unit to adjust the ambient condition of the area in response to the second setpoint information 2164 not being received and based on the stored setpoint information 2164.
In another aspect, the method 2200 may include receiving second sensor information from the mobile device, the second sensor information indicating a second ambient condition of the area, determining a second difference between the second sensor information and the stored setpoint information, and controlling the one or more components of the HVAC unit to adjust the ambient condition of the area further based on the second difference. In an example, one or more components (e.g., processor, memory, operation control component 2142, monitoring component 2170, and/or system operator 2176) of the HVAC unit 2110 may receive second sensor information 2180 from the touchless building control device 500, the second sensor information 2180 indicating a second ambient condition of the area, determine a second difference between the second sensor information 2180 and the stored setpoint information 2164, and control the one or more components (e.g., air conditioning unit 2112, the furnace 2114, the blower 2116, or the humidifier/dehumidifier 2118) of the HVAC unit 2110 to adjust the ambient condition of the area further based on the second difference.

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, or by a special purpose computer processor 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 a processor. By way of example, such machine-readable media can include 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 a processor. 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.

Claims

What is claimed is:

1. A control device for a conditioned space, the control device comprising:

a first face configured to be mounted on a surface at a height accessible by a user;

a second face having a display; and

wherein a first axis normal to the display is angularly offset by an angular amount from a second axis normal to the surface, and wherein the first axis normal to the display is substantially parallel with a line of sight associated with the user at an access distance from the control device.

2. The control device of claim 1, wherein the angular amount is greater than or equal to 15 degrees and less than or equal to 45 degrees.

3. The control device of claim 1, further comprising:

a sensor configured to detect an identifier associated with the user; and

a processing circuit in communication with the sensor, and the display, and heating, ventilating or air conditioning (HVAC) equipment.

4. The control device of claim 3, wherein the processing circuit is configured to:

detect the identifier associated with the user with the sensor;

compare the identifier to a list of authorized identifiers to selectively provide access; and

receive an input from the user based on the identifier associated with the user, wherein the input is associated with the conditioned space.

5. The control device of claim 4, further comprising a second sensor in communication with the processing circuit, the second sensor configured to detect a motion of the user within a detectable range associated with the second sensor, wherein the processing circuit is configured to selectively receive the input from the second sensor.

6. The control device of claim 5, further comprising a light emitting device in communication with the processing circuit and configured to emit light toward a perimeter of the first face.

7. The control device of claim 4, wherein the processing circuit selectively receives the input from a user device, wherein the user device is wirelessly connected to the processing circuit.

8. The control device of claim 4, wherein the processing circuit is configured to output an access code on the display prior to selectively receiving the input from the user.

9. The control device of claim 1, further comprising a sensor configured to detect a presence of the user, wherein a third face is associated with the sensor.

10. The control device of claim 1, wherein the display is an electrophoretic display.

11. The control device of claim 1, further comprising a sensor configured to detect a motion of the user, the sensor in communication with a processing circuit, wherein the processing circuit is in communication with the display and the sensor, wherein the processing circuit is configured to receive an input from the sensor.

12. The control device of claim 11, further comprising a light emitting device, wherein the light emitting device is configured to emit a visible light on the surface.

13. A user interface system for controlling a conditioned space, the user interface system comprising:

a first display being angularly offset by a first angular amount from a mounting surface;

a first sensor configured to identify a first user within a first detectable range associated with the first sensor;

a second sensor configured to detect a first motion of the first user within a second detectable range associated with the second sensor; and

a first processing circuit in communication with the first display, and the first sensor, the second sensor, the first processing circuit configured to:

identify the first user within the first detectable range associated with the first sensor;

selectively receive a first input from the first user by at least one of the second sensor and a user device, wherein the user device is configured to be wirelessly connected to the first processing circuit; and

transmit the first input to a HVAC system.

14. The user interface system of claim 13, further comprising:

a second display being angularly offset by a second angular amount from a second mounting surface;

a third sensor configured to identify a second user within a third detectable range associated with the third sensor;

a second processing circuit communicably coupled to the second display and the third sensor, the second processing circuit configured to:

identify the second user within the third detectable range associated with the third sensor;

selectively receive a second input from the second user from a second user device associated with the second user based on an identifier of the second user, wherein the second user device is wirelessly connected to the second processing circuit; and

wherein the first processing circuit is in communication with the second processing circuit, the first processing circuit configured to receive the second input from the second processing circuit, wherein the first processing circuit is configured to transmit the second input to the HVAC system.

15. The user interface system of claim 13, wherein the first angular amount is between 5 degrees and 90 degrees.

16. The user interface system of claim 13, further comprising a third sensor configured to detect a user within a third detectable range associated with the third sensor, wherein the first processing circuit is further configured to update the first display upon the third sensor detecting the user.

17. A method for adjusting a characteristic of a conditioned space, the method comprising:

identifying a user based on a first sensor configured to detect an identifier associated with the user;

determining a user authorization based on the identifier associated with the user;

displaying information on a display being angularly offset by an angular amount from a mounting surface;

receiving a user input; and

commanding a HVAC equipment based on the user input to adjust the characteristic of the conditioned space.

18. The method of claim 17, wherein determining a user authorization further comprises loading a user profile based on the identifier associated with the user.

19. The method of claim 17, wherein the receiving a user input further comprises the user input generated by a third sensor configured to detect a touchless motion of the user.

20. The method of claim 17, wherein the receiving a user input further comprises the user input received by a user device.