A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present disclosure relates to electrical control boxes; more specifically, an electrical control box with a sliding screen.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description section. This summary does not identify required or essential features of the claimed subject matter. The innovation is defined with claims, and to the extent this Summary conflicts with the claims, the claims should prevail.
Embodiments disclosed herein provide systems and methods for controllers with sliding screens.
In embodiments, a building system controller is disclosed, that comprises: a housing adapted to store a plurality of modules, the housing with computing hardware and programmable memory attached; the housing having a front surface comprising a moveable interactive display moveably connected to the housing; the housing having a controller connector attached to an inside surface, the controller connector providing a connection point for an external resource; the housing adapted for setup or maintenance of the controller connector when the moveable interactive display is in an open position; and the moveable interactive display adapted for setup or maintenance of controller interaction with the external resource when the moveable interactive display is in a closed position.
In embodiments, a module with a module connector and a resource connector is disclosed, wherein the module connector is operationally able to connect the resource connector to wiring for the external resource.
In embodiments, the resource connector is operationally able to provide voltage monitoring.
In embodiments, the resource connector is operationally able to provide power monitoring.
In embodiments, the resource connector is operationally able to provide fault detection.
In embodiments, there are multiple controller connectors and wherein representations of the multiple controller connectors are displayed on the moveable interactive display.
In embodiments, the moveable interactive display is operationally able to allow a user to determine a protocol for the controller connector.
In embodiments, the moveable interactive display is operationally able to update when a new resource is attached to the controller connector.
In embodiments, the moveable interactive display is operationally able to move to display the controller connector and a screen associated with the moveable interactive display simultaneously.
In embodiments, a second controller is disclosed, and the building system controller is connected to the second controller.
In embodiments, mains power is disclosed, and the mains power is shut off when the moveable interactive display is in the open position.
In embodiments, a hook tab is disclosed that is operationally able to load a spring of a module operationally able to attach to the building system controller.
In embodiments, a spring bar is disclosed that is operationally able to load a spring of a module operationally able to attach to the building system controller.
In embodiments, a wiring terminal attachment block is disclosed that is operationally able to attach to a module with resource connectors that are operationally able to attach to a resource.
In embodiments, the mains power is shut off when the moveable interactive display is in the open position.
In embodiments, a housing adapted to store a plurality of modules is disclosed, the housing with computing hardware and programmable memory attached; the housing having a front surface comprising a moveable interactive display moveably connected to the housing, the moveable interactive display operationally able to display a controller setup and maintenance screen; the housing having a controller connector attached to an inside surface, the controller connector providing a connection point for a module, the module comprising a module connector and a resource connector; and the housing adapted for maintenance of the resource connector when the moveable interactive display is in the open position.
In embodiments, the moveable interactive display is adapted for viewing a controller setup when the moveable interactive display is in closed position.
In embodiments, the resource connector comprises current monitoring, voltage monitoring, power monitoring, or fault detection.
In embodiments, a building controller assembly is disclosed, comprising: a housing, a plurality of controller connectors attachments operably connected to the housing, the plurality of controller connectors supported by said housing; a processing circuit supported by said housing, the processing circuit programmed into at least one memory device to perform displaying, on a moveable interactive display associated with the housing, a resource associated with a controller connector; the memory also comprising resource installation information identifying resource input protocols for the controller connector, wherein the processing circuit operably receives at least one input value from at least one of the plurality of controller connectors and operably provides at least one output value based on the resource installation information.
In embodiments, the at least one output value is one of current is correct, voltage is correct, power is correct, or fault is not detected.
Non-limiting and non-exhaustive embodiments of the present embodiments are described with reference to the following FIGURES, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified.
Corresponding reference characters indicate corresponding components throughout the several views of the drawings. Skilled artisans will appreciate that elements in the FIGURES are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments.
Disclosed below are representative embodiments of methods, computer-readable media, and systems having particular applicability to modules used in electrical controllers. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present embodiments. It will be apparent, however, to one having ordinary skill in the art that the specific detail need not be employed to practice the present embodiments. In other instances, well-known materials or methods have not been described in detail in order to avoid obscuring the present embodiments. “one embodiment”, “an embodiment”, “one example” or “an example” means that a particular feature, structure or characteristic described in connection with the embodiment or example is included in at least one embodiment of the present embodiments. Thus, appearances of the phrases “in one embodiment”, “in an embodiment”, “one example” or “an example” in various places throughout this specification are not necessarily all referring to the same embodiment or example. Modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of the disclosure. For example, the components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses disclosed herein may be performed by more, fewer, or other components and the methods described may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, article, or apparatus.
Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present). “Program” is used broadly herein, to include applications, kernels, drivers, interrupt handlers, firmware, state machines, libraries, and other code written by programmers (who are also referred to as developers) and/or automatically generated.
Additionally, any examples or illustrations given herein are not to be regarded in any way as restrictions on, limits to, or express definitions of any term or terms with which they are utilized. Instead, these examples or illustrations are to be regarded as being described with respect to one particular embodiment and as being illustrative only. Those of ordinary skill in the art will appreciate that any term or terms with which these examples or illustrations are utilized will encompass other embodiments which may or may not be given therewith or elsewhere in the specification and all such embodiments are intended to be included within the scope of that term or terms.
The technical character of embodiments described herein will be apparent to one of ordinary skill in the art, and will also be apparent in several ways to a wide range of attentive readers. Some embodiments address technical activities that are rooted in computing technology, such as providing a module interface to more easily correlate devices and the controllers that they will be wired to. This allows easy changes to controllers during the construction process, as equipment is often moved around, controllers are moved, etc., without requiring days or weeks of effort to determine if the correct wire is connected to the correct controller wiring location. Buildings can also be constructed more efficiently as benefits that are not apparent until the construction process can be implemented with little down-time, as equipment with different wiring requirements can be newly installed in a controller by changing modules. Further, as a building or other physical space can build its controller wiring diagram completely within a single controller (or multiple controllers networked only to each other) the entire system has a level of security unable to be reached with systems that are connected to the greater internet. In a multiple controller system, the different controllers may be self-federating, such that they can choose a master controller, can choose a different master controller if the original master has problems, can chunk computer programs to run on multiple controllers, etc. Other advantages based on the technical characteristics of the teachings will also be apparent to one of skill from the description provided.
I. Overview
A building controller is an interface between equipment associated with a defined space and sensors that monitor the building state. In some embodiments, it may replace building control panels in whole or in part. In an illustrative example, a controller 100 is shown that may be used with any of the disclosed embodiments. The controller 100 comprises a housing 105 with a moveable display screen 130. When the moveable screen is opened, the wiring of the controller 115 is displayed allowing installation, real-time wiring feedback, live testing, and protocol changes on the fly. Using these embodiments may reduce install time by half, and project time significantly. When the screen 130 is shut, the controller wiring can no longer be seen. However, the display screen can still be used to view the contents of the controller and details about resources connected to the controller, and change the devices, the protocols of the device, the specific wiring of a device, etc. The resources may comprise devices of many types, such as sensors or equipment. Different modules connect with a different mix of hardware, and provide a different mix of interfaces, although there may be overlap.
In an embodiment, the controller is an interface between equipment associated with the building and sensors that monitor the building state. In some embodiments, it may replace building control panels in whole or in part. In an illustrative example, the controller comprises a housing with a moveable screen; the moveable screen may be a sliding screen. When the moveable screen is opened, the modules of the controller that are wired to various resources in the building are displayed. When the screen is shut, the controller can be used to view building diagrams, resource allocation, etc. Unlock the screen and slide out of the way, and the controller may transform into an installer control center. Real-time wiring feedback, live testing, protocol changes may be made on the fly.
The controller may combine your automation needs into one pre-manufactured control panel—wiring modules, setup interface, user access point, power supply and bussing. This may reduce install time by half, and project time by as much as 90%. The screen may be able to be locked and unlocked. When the unlocked screen is moved out of the way of the housing, the controller can transform into an installer control center. Real-time wiring feedback, live testing, and protocol changes on the fly, to name a few functions, may be easily be performed. The controller may have a housing that can be embedded in a wall just deep enough so that the screen is free to move outside the wall, such that the contents of the controller can be displayed when the screen is opened.
II. Systems
A controller computing environment may have additional features. For example, the controller computing environment 400 includes storage 440, one or more input devices 450, one or more output devices 455, one or more network connections (e.g., wired, wireless, etc.) 460, as well as other communication connections 470. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing environment 400. Typically, operating system software (not shown) provides an operating environment for other software executing in the controller computing environment 400, and coordinates activities of the components of the computing environment 400. The computing system may also be distributed; running portions of the software 485 on different CPUs.
The storage 440 stores instructions for the software 485 to implement controller artificial intelligence software.
The input device(s) 450 may be a device that allows a user or another device to communicate with the computing environment 400, such as a interactive device such as a keyboard, video camera, a microphone, mouse, pen, or trackball, and a scanning device, touchscreen, an LCD touchscreen, a moveable interactive device, and/or another device that provides input to the computing environment 400. The moveable interactive device may be a touchscreen that can slide up and down, back and forth, swivel from a corner, etc. For audio, the input device(s) 450 may be a sound card or similar device that accepts audio input in analog or digital form, or a CD-ROM reader that provides audio samples to the computing environment. The output device(s) 455 may be a display, printer, speaker, CD-writer, network connection that allows email, or another device that provides output from the controller computing environment 400.
The communication connection(s) 470 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, compressed graphics information, or other data in a modulated data signal. Communication connections 470 may comprise input devices 450, output devices 455, and input/output devices that allows a client device to communicate with another device over network 460. A communication device may include one or more wireless transceivers for performing wireless communication and/or one or more communication ports for performing wired communication. These connections may include network connections, which may be a wired or wireless network such as the Internet, an intranet, a LAN, a WAN, a cellular network, spanning tree IP support, on-board bluetooth mesh, or another type of network. Network 460 may be a combination of multiple different kinds of wired or wireless networks. The network 460 may be a distributed network, with multiple computers, which might be building controllers acting in tandem. In some embodiments, distributed along the controllers may be an in-building computer cluster with connectivity to at least some of the other controllers in a building. This connectivity may be wired (such as Ethernet) or wireless. The controllers may be self-federating in that they self-assemble into a network. At startup (or a different time), controllers vote to elect a leader. If the network is damaged, such that the current leader can no longer lead, a new leader is elected by at least some of the undamaged controllers. This provides built-in redundancy. When a computer program is to be run to help with or to control building automation (or for another reason) the leader controller determines how to divide the work load among the controllers.
A communication connection 470 may be a portable communications device such as a wireless handheld device, a cell phone device, a room scanning device, and so on.
Computer-readable media 465—any available non-transient tangible media that can be accessed within a computing environment—may also be included. By way of example, and not limitation, with the controller computing environment 400, computer-readable media include memory 420, storage 440, communication media, and combinations of any of the above. Computer readable storage media 465 which may be used to store computer readable media comprises instructions 475 and data 480. Data Sources may be computing devices, such as general hardware platform servers configured to receive and transmit information over the communications connections 470. The controller computing environment 400 may be an electrical controller that is directly connected to various resources, such as HVAC resources, and which has CPU 410, a GPU 415, Memory 420, input devices 450, communication connections 470, and/or other features shown in the controller computing environment 400. The controller computing environment 400 may be a series of distributed computers. These distributed computers may comprise a series of connected electrical controllers. If the network is damaged, such that the current leader can no longer lead, a new leader is elected by at least some of the undamaged controllers. This provides built-in redundancy. When a computer program is to be run to help with or to control resource connection location with a controller (or for another reason) the leader controller determines how to divide the work load among the controllers.
The controller computing environment may also have specific-purpose chips, such as a fault detection chip 487 that detects if there is a fault on a wire, a voltage monitoring chip 489, a current monitoring chip 491, a power monitoring chip 493, etc.
In some embodiments, a module 540 comprises a module computing environment that may be able to make decisions at the module, and change the message that the controller connector 525A, 530A sends to the resource 575A. The Module computing environment may comprise a central processing unit, a memory, and chips that allow specific functions such as, e.g., fault detection, voltage monitoring, current, monitoring and power monitoring.
In an embodiment, when a module 725 is slid into a controller module bay 735, there are two springs in the module that become loaded; a front spring and a back spring. When the module slides in, the module catches on a hook tab 715, which loads the module front spring and a module ejector button 705. At this time, the back spring also becomes loaded by a spring bar 710. The spring bar 710 pushes the module spring as the module 725 is pushed into place. When the module ejector button 705 is pushed, it moves the hook tab 715 down. The force from the module back spring pushes the module 725 out of the module bay.
A module 725 may comprise resource connectors 730 that comprise one or more of: a universal port, a thermistor, a 0-10 V input/output, a 0-20 mA Input/Output, a 0-48 VAX input, a 24 VAC output. A module associated with a resource connector 730 may be operationally able to use a Modbus/RS485 interface. A module may comprise resource connectors 730 that themselves comprise zero or more 2× power control blocks, zero or more 120/240 VAX output—2 amps, zero or more 24 VAC output—2 amps, zero or more AC motor controls, and zero or more dimmable lighting connectors. Some module resource connectors, no matter what protocol is used, may have real-time current monitoring, real-time voltage monitoring, real-time fault detection, and/or real time power monitoring.
A module 725 may comprise resource connectors 730 that comprise one or more of: a 2× DC motor control block, a 12/24 VDC motor driver, a PWN speed control, real-time current monitoring, real-time voltage monitoring, overcurrent/torque protection, and tachometer feedback.
A module 725 may comprise resource connectors 730 that comprise one or more of: a 2× dry contact block, SPDT relays (10A), up to 240 VDC/VAC, real-time current monitoring, real-time voltage monitoring, and overcurrent protection.
One controller connector option—pogo pins 745—is shown, which operably connects the controller to a module. Other connectors can be used as well. In the illustrative embodiment, twelve pins are shown on the controller connector block 720, with twelve pins also on a matching module connector, but different numbers of pins can be used, without restriction. The number of resource connectors per module 725 can also be varied. They may be varied per module in a controller. For example, a controller may have some modules with two resource connectors and some modules with 5 resource connectors, etc. In the instant embodiment, there are six resource connectors per module.
A resource connector 730 and/or a wiring terminal attachment pin 745 may have one or more of built in voltage monitoring, built-in current monitoring, built-in power monitoring, and built-in fault-detection. These functions may be provided by chips in the controller computing environment 400, such as a fault detection chip 487, a voltage monitoring chip 489, a current monitoring chip 491, or a power monitoring chip 493. These functions may be provided in a module computing environment 580A. In some embodiments, these functions are provided by a module computing environment associated with a resource connector 730. These functions may be provided on the module using similar fault detection chips 487, voltage monitoring chips 489, current monitoring chips 491, and power monitoring chips 493. Some resource connectors 730 and/or wiring terminal attachment pins 745 may also provide overcurrent protection, dimmable lighting, AC motor control, 12/24 VDC motor drivers, PWM speed control, tachometer feedback, and/or SPDT relays (10A). A single wiring terminal attachment pin 745 or resource connector 730 may be able to accommodate one or more of a wide variety of protocols, such as BACNet, 24 VAC, 0-20 ma, 402-ma, 0-10 v, 2-10 v, RTD, and/or 1-wire.
The external resources that are to be wired to the controller are shown as resource icons attached to their respective module connecters. At 910, for example, we can see that the external resource icon is a Three Way Valve, with a 24 VAC (3-wire) protocol. It is attached to module 1925, and has three resource wires, with wire parameters of type (−) 930, (O) 950, and (C) from left to right, and which are in three distinct locations on the controller. When, for example, a resource wire is wired to the lower leftmost connection 820 of the controller, the controller knows that it is to be a wire on a Three-Way Valve, with protocol 24 VAC (3-WIRE) and the specific wire is to be of type (−). Using this information, the controller can see what information is on the wire when connected, what signals the wire accepts, and what signals the wire is expected to return, etc. When the wire is connected to the controller, the controller understands what to do to test if the correct wire has been connected to that direct controller location, e.g., using the controller computing environment 400.
If resource wires have been swapped on a resource (for example, the (−) and (O) wires are swapped such that the (O) wire is in the far lower left position 930, when expected to be in position 950, as expected, the controller may be able to determine this, as it has the information about what signals can be expected to be sent and received on the different resource wires. If the correct resource wire has been connected, then the controller may send a message to the module to tell an indicator 740 on a module 725 to signal that the correct wire is in place. In some embodiments, a controller connector directly tells an indicator state of the resource. In some embodiments, the indicator may indicate that the wire is correct with a light, such as a green LED light, a noise, etc. In some embodiments, the indicator may indicate that the wire is incorrect with a light, such as a red LED light, a noise, etc. An illustrative embodiment is shown in
Once a controller has been wired with resources, the moveable interactive display may display the nature of the devices that are attached to the controller, where they are attached, information about the devices, information about the specific device wires, information about the current state of the device, etc.
A controller, e.g., may have databases of common resources stored within its memory 420 that a user can choose to add resources to the controller. The database may be distributed amongst controllers belonging to a distributed controller system. Users may be able to add resources to the database.
The user can also move devices around on the controller representation screen 900, which resets controller expectations of what each controller wire connection expects. A user may also swap wires on a specific device representation on the moveable interactive display, which will change the types of wires that the controller expects at the specific locations where the wires were swiped on the moveable interactive display. For example, the (−) wire 930 representation may be swapped with the (0) wire representation 950 next to it. This will change the protocol that the controller expects on those wires, and that is checked for when the device is wired to the controller. Whole devices can be moved. The three-way valve representation 910 can be moved by a user to, for example, three open slots on module 2915 or module 7945, etc. These changes will change the protocol that the controller expects on the eventual wires that the device representation is moved to. In some embodiments, the controller may send a signal through the module connector to the resource connector without making any changes. Similarly, in some implementations, a resource may send a signal to the controller through the module without the module making any changes.
In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope and spirit of these claims.
The present application hereby incorporates by reference the entirety of, and claims priority to, U.S. Provisional Patent Application Ser. No. 63/070,460 filed 26 Aug. 2020.
Number | Name | Date | Kind |
---|---|---|---|
4353653 | Zimmerman | Oct 1982 | A |
5208765 | Turnbull | May 1993 | A |
5530643 | Hodorowski | Jun 1996 | A |
5787133 | Marchetto et al. | Jul 1998 | A |
6275962 | Fuller et al. | Aug 2001 | B1 |
6301341 | Gizara et al. | Oct 2001 | B1 |
6349235 | Gibart et al. | Feb 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6606731 | Baum et al. | Aug 2003 | B1 |
6645066 | Gutta et al. | Nov 2003 | B2 |
6813777 | Weinberger et al. | Nov 2004 | B1 |
6891838 | Petite et al. | May 2005 | B1 |
7102502 | Autret | Sep 2006 | B2 |
7304855 | Milligan et al. | Dec 2007 | B1 |
7578135 | Mattheis | Aug 2009 | B2 |
7587250 | Coogan et al. | Sep 2009 | B2 |
7729882 | Seem | Jun 2010 | B2 |
7734572 | Wiemeyer et al. | Jun 2010 | B2 |
7835431 | Belge | Nov 2010 | B2 |
7865629 | Tantos et al. | Jan 2011 | B1 |
7917232 | McCoy et al. | Mar 2011 | B2 |
8024054 | Mairs et al. | Sep 2011 | B2 |
8099178 | Mairs et al. | Jan 2012 | B2 |
8503183 | Hamilton et al. | Aug 2013 | B2 |
8503943 | Spanhake | Aug 2013 | B2 |
8628239 | Merrow et al. | Jan 2014 | B2 |
8643476 | Pinn et al. | Feb 2014 | B2 |
8749959 | Riley et al. | Jun 2014 | B2 |
8782619 | Wu et al. | Jul 2014 | B2 |
8925358 | Kasper | Jan 2015 | B2 |
9441847 | Grohman | Sep 2016 | B2 |
9521724 | Berry et al. | Dec 2016 | B1 |
9544209 | Gielarowski et al. | Jan 2017 | B2 |
9602301 | Averitt | Mar 2017 | B2 |
9664400 | Wroblewski et al. | May 2017 | B2 |
9678494 | Hyde et al. | Jun 2017 | B2 |
9740385 | Fadell et al. | Aug 2017 | B2 |
9791872 | Wang et al. | Oct 2017 | B2 |
9843229 | Leabman | Dec 2017 | B2 |
9857238 | Malhotra et al. | Jan 2018 | B2 |
9860961 | Chemel et al. | Jan 2018 | B2 |
9952573 | Sloo et al. | Apr 2018 | B2 |
10042730 | Zebian | Aug 2018 | B2 |
10094586 | Pavlovski et al. | Oct 2018 | B2 |
10135295 | Leabman | Nov 2018 | B2 |
10223721 | Bhatia | Mar 2019 | B1 |
10333305 | Imai et al. | Jun 2019 | B2 |
10334758 | Ramirez et al. | Jun 2019 | B1 |
10512143 | Ikehara et al. | Dec 2019 | B1 |
10515177 | Ruehl et al. | Dec 2019 | B1 |
10528016 | Noboa | Jan 2020 | B2 |
10557889 | Montoya et al. | Feb 2020 | B2 |
10558183 | Piaskowski et al. | Feb 2020 | B2 |
10558248 | Adrian | Feb 2020 | B2 |
10627124 | Walser et al. | Apr 2020 | B2 |
10640211 | Whitten et al. | May 2020 | B2 |
10650336 | Kopp | May 2020 | B2 |
10672293 | Labutov et al. | Jun 2020 | B2 |
10687435 | Adrian et al. | Jun 2020 | B2 |
10736228 | Kho et al. | Aug 2020 | B2 |
10775824 | Main et al. | Sep 2020 | B2 |
10892946 | Correia e Costa et al. | Jan 2021 | B2 |
10900489 | Rendusara et al. | Jan 2021 | B2 |
10942871 | Cawse et al. | Mar 2021 | B2 |
10943444 | Boyd et al. | Mar 2021 | B2 |
10966068 | Tramiel et al. | Mar 2021 | B2 |
10966342 | Lairsey et al. | Mar 2021 | B2 |
10969133 | Harvey | Apr 2021 | B2 |
11088989 | Gao et al. | Aug 2021 | B2 |
11229138 | Harvey et al. | Jan 2022 | B1 |
11294254 | Patterson et al. | Apr 2022 | B2 |
20040236547 | Rappaport et al. | Nov 2004 | A1 |
20050040247 | Pouchak | Feb 2005 | A1 |
20060103545 | Tsou | May 2006 | A1 |
20070096902 | Seeley et al. | May 2007 | A1 |
20070162288 | Springhart et al. | Jul 2007 | A1 |
20080222584 | Habib et al. | Sep 2008 | A1 |
20080270951 | Anand et al. | Oct 2008 | A1 |
20080277486 | Seem et al. | Nov 2008 | A1 |
20090189764 | Keller et al. | Jul 2009 | A1 |
20090217063 | Tomita | Aug 2009 | A1 |
20100005218 | Gower et al. | Jan 2010 | A1 |
20100025483 | Hoeynck et al. | Feb 2010 | A1 |
20100131933 | Kim et al. | May 2010 | A1 |
20100162037 | Maule et al. | Jun 2010 | A1 |
20100237891 | Lin et al. | Sep 2010 | A1 |
20110087988 | Ray et al. | Apr 2011 | A1 |
20110125930 | Tantos et al. | May 2011 | A1 |
20120102472 | Wu et al. | Apr 2012 | A1 |
20120221986 | Whitford et al. | Aug 2012 | A1 |
20130343207 | Cook et al. | Dec 2013 | A1 |
20130343388 | Stroud et al. | Dec 2013 | A1 |
20130343389 | Stroud et al. | Dec 2013 | A1 |
20130343390 | Moriarty et al. | Dec 2013 | A1 |
20130346987 | Raney et al. | Dec 2013 | A1 |
20140088772 | Lelkens | Mar 2014 | A1 |
20140101082 | Matsuoka et al. | Apr 2014 | A1 |
20140215446 | Araya et al. | Jul 2014 | A1 |
20140215450 | Salisbury | Jul 2014 | A1 |
20140277757 | Wang et al. | Sep 2014 | A1 |
20140280960 | Paramasivam et al. | Sep 2014 | A1 |
20140358291 | Wells | Dec 2014 | A1 |
20140364985 | Tiwari et al. | Dec 2014 | A1 |
20150081928 | Wintzell et al. | Mar 2015 | A1 |
20150198938 | Steele et al. | Jul 2015 | A1 |
20150234381 | Ratilla et al. | Aug 2015 | A1 |
20160016454 | Yang et al. | Jan 2016 | A1 |
20160062753 | Champagne | Mar 2016 | A1 |
20160073521 | Marcade et al. | Mar 2016 | A1 |
20160086242 | Schafer et al. | Mar 2016 | A1 |
20160092427 | Bittmann | Mar 2016 | A1 |
20160132308 | Muldoon | May 2016 | A1 |
20160195856 | Spero | Jul 2016 | A1 |
20160205784 | Kyle et al. | Jul 2016 | A1 |
20160209868 | Hartman et al. | Jul 2016 | A1 |
20160248251 | Tinnakornsrisuphap et al. | Aug 2016 | A1 |
20160285715 | Gielarowski et al. | Sep 2016 | A1 |
20160295663 | Hyde et al. | Oct 2016 | A1 |
20160088438 | O'Keeffe | Dec 2016 | A1 |
20170075323 | Shrivastava et al. | Mar 2017 | A1 |
20170097259 | Brown et al. | Apr 2017 | A1 |
20170131611 | Brown et al. | May 2017 | A1 |
20170149638 | Gielarowski et al. | May 2017 | A1 |
20170169075 | Jiang et al. | Jun 2017 | A1 |
20170176034 | Hussain et al. | Jun 2017 | A1 |
20170217390 | Curtis et al. | Aug 2017 | A1 |
20170322579 | Goparaju et al. | Nov 2017 | A1 |
20170342920 | Pirjaberi et al. | Nov 2017 | A1 |
20170365908 | Hughes et al. | Dec 2017 | A1 |
20180005195 | Jacobson | Jan 2018 | A1 |
20180075168 | Tiwari et al. | Mar 2018 | A1 |
20180089172 | Needham | Mar 2018 | A1 |
20180123272 | Mundt et al. | May 2018 | A1 |
20180202678 | Ahuja et al. | Jul 2018 | A1 |
20180262573 | Przybylski et al. | Sep 2018 | A1 |
20180266716 | Bender et al. | Sep 2018 | A1 |
20180307781 | Byers et al. | Oct 2018 | A1 |
20190087076 | Dey et al. | Apr 2019 | A1 |
20190138704 | Shrivastava et al. | May 2019 | A1 |
20190146429 | Nayak et al. | May 2019 | A1 |
20190156443 | Idle | May 2019 | A1 |
20190173109 | Wang | Jun 2019 | A1 |
20190278442 | Liang | Sep 2019 | A1 |
20190294018 | Shrivastava et al. | Sep 2019 | A1 |
20200003444 | Yuan et al. | Jan 2020 | A1 |
20200018506 | Ruiz et al. | Jan 2020 | A1 |
20200050161 | Noboa | Feb 2020 | A1 |
20200133257 | Cella et al. | Apr 2020 | A1 |
20200150508 | Patterson et al. | May 2020 | A1 |
20200167442 | Roecker et al. | May 2020 | A1 |
20200187147 | Meerbeek et al. | Jun 2020 | A1 |
20200221269 | Tramiel et al. | Jul 2020 | A1 |
20200226223 | Reichl | Jul 2020 | A1 |
20200228759 | Ryan et al. | Jul 2020 | A1 |
20200255142 | Whitten et al. | Aug 2020 | A1 |
20200279482 | Berry et al. | Sep 2020 | A1 |
20200284883 | Ferreira et al. | Sep 2020 | A1 |
20200287786 | Anderson et al. | Sep 2020 | A1 |
20200288558 | Anderson et al. | Sep 2020 | A1 |
20200342526 | Ablanczy | Oct 2020 | A1 |
20200379730 | Graham et al. | Dec 2020 | A1 |
20200387041 | Shrivastava et al. | Dec 2020 | A1 |
20200387129 | Chandaria | Dec 2020 | A1 |
20210073441 | Austern et al. | Mar 2021 | A1 |
20210081504 | Mccormick et al. | Mar 2021 | A1 |
20210081880 | Bivins et al. | Mar 2021 | A1 |
20210003830 | Harvey | Apr 2021 | A1 |
20210157312 | Cella et al. | May 2021 | A1 |
20210182660 | Amirguliyev et al. | Jun 2021 | A1 |
20210366793 | Hung et al. | Nov 2021 | A1 |
20210383041 | Harvey et al. | Dec 2021 | A1 |
20210400787 | Abbo et al. | Dec 2021 | A1 |
20220066722 | Harvey et al. | Mar 2022 | A1 |
20220069863 | Harvey | Mar 2022 | A1 |
20220070293 | Harvey et al. | Mar 2022 | A1 |
Number | Date | Country |
---|---|---|
103926912 | May 2014 | CN |
206002869 | Aug 2016 | CN |
206489622 | Sep 2017 | CN |
6301341 | Mar 2018 | JP |
200420980 | Oct 2004 | TW |
2008016500 | Mar 2008 | WO |
WO2012019328 | Feb 2012 | WO |
2014025511 | Feb 2014 | WO |
Entry |
---|
BigLadder Software Full Ref, Occupant Thermal Comfort: Engineering Reference, 2014, the Board of Trustees of the University of Illinois and the Regents of the University of California through the Ernest Orlando Lawrence Berkeley National Laboratory (Year: 2014). |
Hagentoft et al. Full Reference, Assessment Method of Numerical Prediction Models for Combined Heat, Air and Moisture Transfer in Building Components: Benchmarks for One-dimensional Cases, Journal of Thermal Env. & Bldg. Sci., vol. 27, No. 4, Apr. 2004. |
U.S. Appl. No. 15/995,019 Office Action mailed Jul. 26, 2019. |
U.S. Appl. No. 15/995,019 Office Action mailed Oct. 8, 2020. |
U.S. Appl. No. 15/995,019 Office Action mailed Apr. 15, 2020. |
De Meester et al., SERIF:A Semantic Exercise Interchange FormatConference: Proceedings of the 1st International Workshop on LINKed EDucation, Oct. 2015. |
Kalagnanam et al., “A System for Automated Mapping of Bill-of_Materials Part Numbers”, KDD '04: Proceedings of the tenth ACM SIGKDD international conference on Knowledge discovery and data mining, Aug. 2004, pp. 805-810. |
Mouser Electronics News Release, Aug. 16, 2018. |
Ouf et al., Effectiveness of using WiFi technologies to detect and predict building occupancy, Sust. Buildi. 2, 7 (2017). |
Radiomaze, Inc., “WiFi signals enable motion recognition throughout the entire home,” Dec. 4, 2017. |
Sensorswarm, 2018. |
Siano, P, “Demand response and smart grids—A survey”, Renewable and Sustainable Energy Reviews 30 (2014) 461-478. |
Wang et al., “A Practical Multi-Sensor Cooling Demand Estimation Approach Based on Visual Indoor and Outdoor Information Sensing,” Sensors 2018, 18, 3591; doi: 10.3390. |
Yegulap, Serdar, “What is LLVM? The power behind Swift, Rust, Clang, and more,” Infoworld, Mar. 11, 2020. |
Serale G., et al., Model Predictive Control (MPC) for Enhancing Building and HVAC System Energy Efficiency: Problem Formulation, Applications and Opportunities, Energies 2018, 11, 631; doi: 10.3390, Mar. 12, 2018. |
Amin, Massoud, “Toward self-healing energy infrastructure systems,” IEEE Computer Applications in Power 14.1 (2002): pp. 20-28. |
Gou, Wenqi, and Mengchu Zhou, “An emerging technology for improved building automation control,” 2009, IEEE International Conference on Systems, Man and Cybernetics, IEEE, 2009, pp. 337-342. |
Gungor et al., “Industrial Wireless Sensor Networks: Challenges, Design Principles, and Technical Approaches,” IEEE Transactions on Industrial Electronics, vol. 56, No. 10, Oct. 2009. |
Gou, Wendy et al., “Wireless mesh networks in intelligent building automation control: a survey.” International Journal of Intelligent Control and Systems, vol. 16, No. 1, Mar. 2011, 28-36. |
Kastner, Wolfgang, et al., “Building Automation System Integration into the Internet of Things, the IoT6 Approach, Its Realization and Validation,” Proceedings of the 2014 IEEE Emerging Technology and Factory Automation (ETFA), IEEE, 2014, pp. 1-9 (Year:2014). |
Shailendra, Eshan et al., “Analyzing home automation and networking technologies,” IEEE Potentials 37.1 (2018): pp. 27-33, (Year: 2018). |
Number | Date | Country | |
---|---|---|---|
20220066722 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
63070460 | Aug 2020 | US |