Patent Grant
12018852
The present disclosure relates to environmental comfort systems and more particularly to monitoring of residential and light commercial environmental comfort systems.
A residential or light commercial HVAC (heating, ventilation, or air conditioning) system controls environmental parameters, such as temperature and humidity, of a building. The target values for the environmental parameters, such as a temperature setpoint, may be specified by a user or owner of the building, such as an employee working in the building or a homeowner.
In
The thermostat 116 may direct that the circulator blower 108 be turned on at all times or only when a heat request or cool request is present (automatic fan mode). In various implementations, the circulator blower 108 can operate at one or more discrete speeds or at any speed within a predetermined range. For example, the control module 112 may actuate one or more switching relays (not shown) to control the circulator blower 108 and/or to select a speed of the circulator blower 108.
The thermostat 116 provides the heat and/or cool requests to the control module 112. When a heat request is made, the control module 112 causes a burner 120 to ignite. Heat from combustion is introduced to the return air provided by the circulator blower 108 in a heat exchanger 124. The heated air is supplied to the building and is referred to as supply air.
The burner 120 may include a pilot light, which is a small constant flame for igniting the primary flame in the burner 120. Alternatively, an intermittent pilot may be used in which a small flame is first lit prior to igniting the primary flame in the burner 120. A sparker may be used for an intermittent pilot implementation or for direct burner ignition. Another ignition option includes a hot surface igniter, which heats a surface to a temperature high enough that gas introduced to the heated surface will combust. Fuel for combustion, such as natural gas, may be provided by a gas valve 128.
The products of combustion are exhausted outside of the building, and an inducer blower 132 may be turned on prior to ignition of the burner 120. In a high efficiency furnace, the products of combustion may not be hot enough to have sufficient buoyancy to exhaust via convection. Therefore, the inducer blower 132 creates a draft to exhaust the products of combustion. The inducer blower 132 may remain running while the burner 120 is operating. In addition, the inducer blower 132 may continue running for a set period of time after the burner 120 turns off.
A single enclosure, which will be referred to as an air handler unit 136, may include the filter 104, the circulator blower 108, the control module 112, the burner 120, the heat exchanger 124, the inducer blower 132, an expansion valve 140, an evaporator 144, and a condensate pan 146. In various implementations, the air handler unit 136 includes an electrical heating device (not shown) instead of, or in addition to, the burner 120. When used in addition to the burner 120, the electrical heating device may provide backup or secondary (extra) heat.
In
A control module 156 receives a cool request from the control module 112 and controls the compressor 148 accordingly. The control module 156 also controls a condenser fan 160, which increases heat exchange between the condenser 152 and outside air. In such a split system, the compressor 148, the condenser 152, the control module 156, and the condenser fan 160 are generally located outside of the building, often in an enclosure referred to as a condensing unit 164.
In various implementations, the control module 156 may include a run capacitor, a start capacitor, and a contactor or relay. In various implementations, the start capacitor may be omitted, such as when the condensing unit 164 includes a scroll compressor instead of a reciprocating compressor. The compressor 148 may be a variable-capacity compressor and may respond to a multiple-level cool request. For example, the cool request may indicate a mid-capacity call for cooling or a high-capacity call for greater cooling. The compressor 148 therefore varies its capacity according to the cool request.
The electrical lines provided to the condensing unit 164 may include a 240V mains power line (not shown) and a 24V switched control line. The 24V control line may correspond to the cool request shown in
The background description provided here is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
A monitoring system for monitoring a heating, ventilation, and air conditioning (HVAC) system of a building is disclosed. The monitoring system includes at least one processor and a computer-readable medium that includes instructions executable by the at least one processor. The instructions include: determining a capacity of a filter of the HVAC system based at least on dimensions of the filter; determining a threshold based on the capacity of the filter; monitoring a state of a circulator blower of the HVAC system; and calculating a filter usage based on the state of the circulator blower and one of (i) a current consumed by the circulator blower and (ii) an operation mode of the HVAC system. The instructions also include generating, in response to the filter usage exceeding the threshold, an alert suggesting replacement of the filter. In further features, the instructions include reporting the filter usage as a percentage.
In other features, the instructions include accumulating, in response to receiving a power signal indicative of the power consumed by the circulator blower, a cumulative power value based on the power signal. The instructions also include calculating the filter usage based on the power value.
In other features, the monitoring system includes a current sensor configured to measure a current indicative of the power consumed by the circulator blower. Calculating the filter usage includes periodically increasing the filter usage based on the measured current.
In further features, increasing the filter usage includes adding an average current consumed by the circulator blower calculated over a predetermined period of time to the filter usage. In other features, increasing the filter usage includes a stepwise increase for each increment of time in which the state of the circulator blower indicates that the circulator blower is running.
In yet other features, the instructions include determining, in response to the circulator blower being on, the operation mode of the HVAC system. Calculating the filter usage includes periodically increasing the filter usage based on the operation mode of the HVAC system. In further features, determining the operation mode of the HVAC system includes receiving power data associated with the HVAC system from an energy monitor that measures power consumed by all electrical appliances in the building and determining the operation mode of the HVAC based on the power data.
In other features, the instructions include adding, in response to determining the operation mode of the HVAC system is a cooling mode, a first period of time to the filter usage. In further features, the instructions include in response to determining the operation mode of the HVAC system is a second cooling mode, adding a product of the first period of time and a first adjustment factor to the filter usage and in response to determining the operation mode of the HVAC system is a heating mode, adding a product of the first period of time and a second adjustment factor to the filter usage. In yet further features, the instructions include in response to determining the operation mode of the HVAC system is a second heating mode, adding a product of the first period of time and a third adjustment factor to the filter usage and in response to determining the operation mode of the HVAC system is a fan only mode, adding a product of the first period of time and a fourth adjustment factor to the filter usage.
In other features, the instructions include determining a remaining life of the filter based on a length of time that the filter has been installed in the HVAC system, the filter usage, and the capacity of the filter. The alert suggesting replacement of the filter includes the remaining life of the filter.
In yet other features, the instructions include generating, in response to the filter usage equaling or exceeding the capacity of the filter, an alert indicating that the filter needs to be replaced.
In yet other features, generating the alert suggesting replacement of the filter includes generating the alert only once per predetermined period. The predetermined period is greater than or equal to one day.
A monitoring system for monitoring an HVAC system of a building is disclosed. The monitoring system includes at least one processor and a computer-readable medium that includes instructions executable by the at least one processor. The instructions include: determining a capacity of a filter of the HVAC system based at least on dimensions of the filter; determining a threshold based on the capacity of the filter; and calculating a filter usage based on a speed of a circulator blower of the HVAC system. The speed of the circulator blower is one of two non-zero speeds. The instructions further include generating, in response to the filter usage exceeding the threshold, an alert suggesting replacement of the filter.
In other features, the instructions further include measuring a current consumed by a motor of the circulator blower and determining the speed of the circulator blower based on the measured current.
In yet other features, the instructions further include measuring a power consumed by a motor of the circulator blower and determining the speed of the circulator blower based on the measured power.
In other features, the instructions further include receiving data from a thermostat of the HVAC system. The data includes an operation mode of the HVAC system. The instructions also include determining the speed of the circulator blower based on the operation mode.
In yet other features, the instructions further include receiving power data from an energy monitor of the building. The power data indicates an operation mode of the HVAC system. The instructions further include determining the speed of the circulator blower based on the operation mode indicted by the power data.
A method for monitoring an HVAC system of a building includes: determining a capacity of a filter of an HVAC system based at least on dimensions of the filter; determining a threshold based on the capacity of the filter; monitoring a state of a circulator blower of the HVAC system; and calculating a filter usage based on the state of the circulator blower and one of (i) a power consumed by the circulator blower and (ii) an operation mode of the HVAC system. The method also includes generating, in response to the filter usage exceeding the threshold, an alert suggesting replacement of the filter. In further features, the method includes reporting the filter usage as a percentage.
In other features, the method includes accumulating, in response to receiving a power signal indicative of the power consumed by the circulator blower, a cumulative power value based on the power signal. The method further includes calculating the filter usage based on the power value.
In other features, the method includes measuring current indicative of power consumed by the circulator blower using a current sensor and periodically increasing the filter usage based on the measured current. In further features, increasing the filter usage includes adding an average current consumed by the circulator blower calculated over a predetermined period of time to the filter usage.
In yet other features, increasing the filter usage includes a stepwise increase for each increment of time in which the state of the circulator blower indicates that the circulator blower is running.
In other features, the method includes determining, in response to the circulator blower being on, the operation mode of the HVAC system. Calculating the filter usage includes periodically increasing the filter usage based on the operation mode of the HVAC system.
In yet other features, the method includes receiving power data associated with the HVAC system from an energy monitor that measures power consumed by all electrical appliances in the building. The method further includes determining the operation mode of the HVAC based on the power data.
In other features, the method includes adding, in response to determining the operation mode of the HVAC system is a cooling mode, a first period of time to the filter usage. In further features, the method incudes in response to determining the operation mode of the HVAC system is a second cooling mode, adding a product of the first period of time and a first adjustment factor to the filter usage and in response to determining the operation mode of the HVAC system is a heating mode, adding a product of the first period of time and a second adjustment factor to the filter usage. In yet further features, the method includes in response to determining the operation mode of the HVAC system is a second heating mode, adding a product of the first period of time and a third adjustment factor to the filter usage and in response to determining the operation mode of the HVAC system is a fan only mode, adding a product of the first period of time and a fourth adjustment factor to the filter usage.
In other features, the method includes determining a remaining life of the filter based on a length of time that the filter has been installed in HVAC system, the filter usage, and the capacity of the filter. The alert suggesting replacement of the filter includes the remaining life of the filter.
In yet other features, the method includes generating, in response to the filter usage equaling or exceeding the capacity of the filter, an alert indicating that the filter needs to be replaced.
In further features, generating the alert suggesting replacement of the filter includes generating the alert only once per predetermined period. The predetermined period is greater than or equal to one day.
A computer-readable medium includes processor-executable instructions. The instructions include: determining a capacity of a filter of an HVAC system based at least on dimensions of the filter; determining a threshold based on the capacity of the filter; and monitoring a state of a circulator blower of the HVAC system. Instructions also include calculating a filter usage based on the state of the circulator blower and one of (i) power consumed by the circulator blower and (ii) an operation mode of the HVAC system and generating, in response to the filter usage exceeding the threshold, an alert suggesting replacement of the filter.
A monitoring system for an HVAC system of a building is disclosed. The monitoring system includes at least one processor and a computer readable medium that includes instructions executable by the at least one processor. The instructions include: determining a capacity of a filter of the HVAC system based at least on dimensions of the filter; determining a threshold based on the capacity of the filter; determining a total power value based on power consumed by a circulator blower of the HVAC system since the filter was installed; and calculating a filter usage based on the total power value. The instructions also include generating, in response to the filter usage exceeding the threshold, an alert suggesting replacement of the filter.
In further features, the instructions include receiving data from a power measurement chip of the HVAC system. The data indicates a present power consumed by the circulator blower. The instructions further include increasing the total power value based on the received data.
In other features, the instructions include generating, in response to the filter usage equaling or exceeding the capacity of the filter, an alert indicating that the filter needs to be replaced. In further features, generating the alert suggesting replacement of the filter includes generating the alert only once per predetermined period. The predetermined period is greater than or equal to one day.
Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims, and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.
The present disclosure will become more fully understood from the detailed description and the accompanying drawings.
In the drawings, reference numbers may be reused to identify similar and/or identical elements.
According to the present disclosure, a monitoring system can be integrated with a residential or light commercial HVAC (heating, ventilation, or air conditioning) system of a building. The monitoring system can provide information on the status, maintenance, and efficiency of the HVAC system to customers and/or contractors associated with the building. For example, the building may be a single-family residence, and the customer may be the homeowner, a landlord, or a tenant. In other implementations, the building may be a light commercial building, and the customer may be the building owner, a tenant, or a property management company.
As used in this application, the term HVAC encompasses all environmental comfort systems in a building, including heating, cooling, humidifying, dehumidifying, air exchanging, and purifying. Environmental comfort systems include devices such as furnaces, heat pumps, humidifiers, dehumidifiers, ventilators, and air conditioners. In this application, the term HVAC system includes components that perform at least one of heating, ventilation, or air conditioning.
In split HVAC systems with an air handler unit (often, located indoors) and a condensing unit (often, located outdoors), an air handler monitor module and a condensing monitor module, respectively, can be used. The air handler monitor module and the condensing monitor module may be integrated by the manufacturer of the HVAC system, may be added at the time of the installation of the HVAC system, and/or may be retrofitted to an existing HVAC system.
In heat pump systems, the function of the air handler unit and the condensing unit are reversed depending on the mode of the heat pump. As a result, although the present disclosure uses the terms air handler unit and condensing unit, the terms indoor unit and outdoor unit could be used instead in the context of a heat pump. The terms indoor unit and outdoor unit emphasize that the physical locations of the components stay the same while their roles change depending on the mode of the heat pump. In a heat pump system, a reversing valve selectively reverses the flow of refrigerant from what is shown in
The air handler monitor module and the condensing monitor module (collectively, monitor modules) monitor operating parameters of associated components of the HVAC system. For example, the operating parameters may include power supply current, power supply voltage, current through a motor of the circulator blower, operating and ambient temperatures of inside and outside air, refrigerant temperatures and pressures at various points in the refrigerant loop, fault signals, control signals, and humidity of inside and outside air.
The monitor modules may communicate data between each other. One or both of the monitor modules may upload data to a remote location. The remote location may be accessible via any suitable network, including the Internet.
The remote location includes one or more computers, which will be referred to as servers. The servers execute a monitoring system on behalf of a monitoring company. The monitoring system receives and processes the data from the monitor modules of customers who have such systems installed. The monitoring system can provide performance information, diagnostic alerts, and error messages to a customer and/or third parties, such as designated HVAC contractors.
A server of the monitoring system includes a processor and memory. The memory stores application code that processes data received from the monitor modules and determines existing and/or impending failures, as described in more detail below. The processor executes this application code and stores received data either in the memory or in other forms of storage, including magnetic storage, optical storage, flash memory storage, etc. While the term server is used in this application, the application is not limited to a single server.
A collection of servers may together operate to receive and process data from the monitor modules of multiple buildings. A load balancing algorithm may be used between the servers to distribute processing and storage. The present application is not limited to servers that are owned, maintained, and housed by a monitoring company. Although the present disclosure describes diagnostics and processing and alerting occurring in a remote monitoring system, some or all of these functions may be performed locally using installed equipment and/or customer resources, such as on a customer computer or computers.
Customers and/or HVAC contractors may be notified of current and predicted issues affecting effectiveness or efficiency of the HVAC system, and may receive notifications related to routine maintenance. The methods of notification may take the form of push or pull updates to an application, which may be executed on a smart phone or other mobile device or on a standard computer. Notifications may also be viewed using web applications or on local displays, such as on a thermostat or other displays located throughout the building or on a display (not shown) implemented in one of the monitor modules. Notifications may also include text messages, emails, social networking messages, voicemails, phone calls, etc.
The monitor modules may each sense an aggregate current for the respective unit without measuring individual currents of individual components. The aggregate current data may be processed using frequency domain analysis, statistical analysis, and state machine analysis to determine operation of individual components based on the aggregate current data. This processing may happen partially or entirely in a server environment, remote from the customer's building or residence. Combined with voltage, the aggregate current data at the monitor modules can be used to determine apparent power consumed by the air handler unit and the condensing unit, respectively. The voltage may be measured one time or repeatedly by one or both of the monitor modules. Alternatively, the customer may specify the voltage of the HVAC system—for example, based on a measured value or simply by making a binary choice between 120V and 240V.
The frequency domain analysis may allow individual contributions of HVAC system components to be determined. Some of the advantages of using an aggregate current measurement may include reducing the number of current sensors that would otherwise be necessary to monitor each of the HVAC system components. This reduces bill of materials costs, as well as installation costs and potential installation problems. Further, providing a single time-domain current stream may reduce the amount of bandwidth necessary to upload the current data. Nevertheless, additional current sensors may be used—for example, a circulator blower motor current sensor.
Based on measurements from monitor modules, the monitoring company can determine whether HVAC components are operating at their peak performance and can advise the customer and the contractor when performance is reduced. This performance reduction may be measured for the system as a whole, such as in terms of efficiency, and/or may be monitored for one or more individual components.
For example, filter usage may be determined based on the measured current through the motor of the circulator blower. Alternatively, filter usage may be determined based on the length of use of specific modes of the HVAC system, such as cooling, extra cooling, heating, extra heating, and fan only modes. Since the determined filter usage is based on operational conditions of the HVAC system, the monitoring system may notify a user when the filter needs to be changed rather than requiring the user to rely on less accurate, conventional filter replacement schedules.
In addition, the monitoring system may detect and/or predict failures of one or more components of the system. When a failure is detected, the customer can be notified and potential remediation steps can be taken immediately. For example, components of the HVAC system may be shut down to prevent or minimize damage, such as water damage, to HVAC components. The contractor can also be notified that a service call will be required. Depending on the contractual relationship between the customer and the contractor, the contractor may immediately schedule a service call to the building.
The monitoring system may provide specific information to the contractor, including identifying information of the customer's HVAC system, including make and model numbers, as well as indications of the specific part numbers that appear to be failing. Based on this information, the contractor can allocate the correct repair personnel that have experience with the specific HVAC system and/or component. In addition, the service technician is able to bring replacement parts, avoiding return trips after diagnosis.
Depending on the severity of the failure, the customer and/or contractor may be advised of relevant factors in determining whether to repair the HVAC system or replace some or all of the components of the HVAC system. For example only, these factors may include relative costs of repair versus replacement, and may include quantitative or qualitative information about advantages of replacement equipment. For example, expected increases in efficiency and/or comfort with new equipment may be provided. Based on historical usage data and/or electricity or other commodity prices, the comparison may also estimate annual savings resulting from the efficiency improvement.
As mentioned above, the monitoring system may also predict impending failures. This allows for preventative maintenance and repair prior to an actual failure. Alerts regarding detected or impending failures reduce the time when the HVAC system is out of operation and allows for more flexible scheduling for both the customer and contractor. If the customer is out of town, these alerts may prevent damage from occurring when the customer is not present to detect the failure of the HVAC system. For example, failure of heat in winter may lead to pipes freezing and bursting.
Alerts regarding potential or impending failures may specify statistical timeframes before the failure is expected. For example only, if a sensor is intermittently providing bad data, the monitoring system may specify an expected amount of time before it is likely that the sensor effectively stops working due to the prevalence of bad data. Further, the monitoring system may explain, in quantitative or qualitative terms, how the current operation and/or the potential failure will affect operation of the HVAC system. This enables the customer to prioritize and budget for repairs.
For the monitoring service, the monitoring company may charge a periodic rate, such as a monthly rate. This charge may be billed directly to the customer and/or may be billed to the contractor. The contractor may pass along these charges to the customer and/or may make other arrangements, such as by requiring an up-front payment upon installation and/or applying surcharges to repairs and service visits.
For the monitor modules, the monitoring company or contractor may charge the customer the equipment cost, including the installation cost, at the time of installation and/or may recoup these costs as part of the monthly fee. Alternatively, rental fees may be charged for the air handler monitor and condensing monitor modules, and once the monitoring service is stopped, the air handler monitor and condensing monitor modules may be returned.
The monitoring service may allow the customer and/or contractor to remotely monitor and/or control HVAC components, such as setting temperature, enabling or disabling heating and/or cooling, etc. In addition, the customer may be able to track energy usage, cycling times of the HVAC system, and/or historical data. Efficiency and/or operating costs of the customer's HVAC system may be compared against HVAC systems of neighbors, whose buildings will be subject to the same or similar environmental conditions. This allows for more direct comparison of HVAC system and overall building efficiency because environmental variables, such as temperature and wind, are controlled.
The installer can provide information to the remote monitoring system including identification of control lines that were connected to the monitor modules. In addition, information such as the HVAC system type, year installed, manufacturer, model number, BTU rating, filter type, filter size, tonnage, etc.
In addition, because the condensing unit may have been installed separately from the furnace, the installer may also record and provide to the remote monitoring system the manufacturer and model number of the condensing unit, the year installed, the refrigerant type, the tonnage, etc. Upon installation, baseline tests are run. For example, this may include running a heating cycle and a cooling cycle, which the remote monitoring system records and uses to identify initial efficiency metrics. Further, baseline profiles for current, power, and frequency domain current can be established.
The server may store baseline data for the HVAC system of each building. The baselines can be used to detect changes indicating impending or existing failures. For example only, frequency-domain current signatures of failures of various components may be pre-programmed, and may be updated based on observed evidence from contractors. For example, once a malfunction in an HVAC system is recognized, the monitoring system may note the frequency data leading up to the malfunction and correlate that frequency signature with frequency signatures associated with potential causes of the malfunction. For example only, a computer learning system, such as a neural network or a genetic algorithm, may be used to refine frequency signatures. The frequency signatures may be unique to different types of HVAC systems but may share common characteristics. These common characteristics may be adapted based on the specific type of HVAC system being monitored.
The installer may collect a device fee, an installation fee, and/or a subscription fee from the customer. In various implementations, the subscription fee, the installation fee, and the device fee may be rolled into a single system fee, which the customer pays upon installation. The system fee may include the subscription fee for a set number of years, such as 1, 2, 5, or 10, or may be a lifetime subscription, which may last for the life of the home or for the duration of ownership of the building by the customer.
The monitoring system can be used by the contractor during and after installation and during and after repair (i) to verify operation of the air handler monitor and condensing monitor modules and (ii) to verify correct installation of the components of the HVAC system. In addition, the customer may review this data in the monitoring system for assurance that the contractor correctly installed and configured the HVAC system. In addition to being uploaded to the remote monitoring service (also referred to as the cloud), monitored data may be transmitted to a local device in the building. For example, a smartphone, laptop, proprietary portable device, or building management system may receive monitoring information to diagnose problems and receive real-time performance data. Alternatively, data may be uploaded to the cloud and then downloaded onto a local computing device, such as via the Internet from an interactive web site.
The historical data collected by the monitoring system may allow the contractor to properly specify new HVAC components and to better tune configuration, including dampers and setpoints of the HVAC system. The information collected may be helpful in product development and assessing failure modes. The information may be relevant to warranty concerns, such as determining whether a particular problem is covered by a warranty. Further, the information may help to identify conditions, such as unauthorized system modifications, that could potentially void warranty coverage.
Original equipment manufacturers may subsidize partially or fully the cost of the monitoring system and air handler and condensing monitor modules in return for access to this information. Installation and service contractors may also subsidize some or all of these costs in return for access to this information or, as another example, in exchange for being recommended by the monitoring system. Based on historical service data and customer feedback, the monitoring system may provide contractor recommendations to customers.
In many systems, the air handler unit 136 is located inside the building, while the condensing unit 164 is located outside the building. The present disclosure is not limited, and applies to other systems including, as examples only, systems where the components of the air handler unit 136 and the condensing unit 164 are located in close proximity to each other or even in a single enclosure. The single enclosure may be located inside or outside of the building. In various implementations, the air handler unit 136 may be located in a basement, garage, or attic. In ground source systems, where heat is exchanged with the earth, the air handler unit 136 and the condensing unit 164 may be located near the earth, such as in a basement, crawlspace, garage, or on the first floor, such as when the first floor is separated from the earth by only a concrete slab.
In
When installing the air handler monitor module 200 in the air handler unit 136, power is provided to the air handler monitor module 200. For example, a transformer 212 can be connected to an AC line in order to provide AC power to the air handler monitor module 200. The air handler monitor module 200 may measure voltage of the incoming AC line based on this transformed power supply. For example, the transformer 212 may be a 10-to-1 transformer and therefore provide either a 12V or 24V AC supply to the air handler monitor module 200 depending on whether the air handler unit 136 is operating on nominal 120V or nominal 240V power. The air handler monitor module 200 then receives power from the transformer 212 and determines the AC line voltage based on the power received from the transformer 212. In various implementations, the air handler monitor module 200 may scale the received power by a turns ratio of the transformer 212 to account for the voltage being stepped down by the transformer 212. For example, when the turns ratio of the transformer 212 is 10-to-1, the air handler monitor module 200 may multiply the measured voltage by 10 to determine the AC line voltage.
For example, frequency, amplitude, RMS voltage, and DC offset may be calculated based on the measured voltages. Information about when the voltage crosses zero may be used to synchronize various measurements and to determine frequency of the AC power based on counting the number of zero crossings within a predetermined time period. In situations where 3-phase power is used, the order of the phases may be determined.
A current sensor 216 measures incoming current to the air handler unit 136. The current sensor 216 may include a current transformer that snaps around one power lead of the incoming AC power. The current sensor 216 may alternatively include a current shunt or a hall effect device. In various implementations, a power sensor (not shown) may be used in addition to or in place of the current sensor 216. For example, the power sensor may output a real power signal corresponding to the power consumed by the current-consuming components of the air handler unit 136. The real power may be equivalent to an instantaneous dot product of voltage and current, as well as to the product of apparent power (voltage multiplied by current) and power factor of the air handler unit 136.
A circulator blower current sensor 218 measures the current through a motor of the circulator blower 108. The circulator blower current sensor 218 may include a current transformer that snaps around one power lead supplying AC power to the motor of the circulator blower 108. The circulator blower current sensor 218 may alternatively include a current shunt or a hall effect device.
In various other implementations, electrical parameters (such as voltage, current, and power factor) may be measured at a different location, such as at an electrical panel that distributes power from the electrical utility to part or all of the building. For example, the air handler monitor module 200 may receive information from a whole home energy monitor connected to the electrical panel. The whole home energy monitor measures a current consumed by an entire building, such as a house, and may also measure voltage. Based on measured electrical parameters, the whole home energy monitor can determine the total power consumed by all of the electrical appliances in the building, including an HVAC system. The whole home energy monitor may use machine learning to automatically identify and monitor the electrical consumption of individual appliances.
For simplicity of illustration, connections between the control module 112 and various components and sensors of the air handler unit 136 are not shown. In addition, routing of the AC power to various powered components of the air handler unit 136, such as the gas valve 128 and the inducer blower 132, are also not shown for simplicity. The current sensor 216 measures the current entering the air handler unit 136 and therefore represents an aggregate current of the current-consuming components of the air handler unit 136.
The control module 112 controls operation in response to signals from the thermostat 208 received over control lines. The air handler monitor module 200 monitors the control lines. The control lines may include a call for cool, a call for heat, and a call for fan. The control lines may include a line corresponding to a state of a reversing valve in heat pump systems.
The control lines may further carry calls for secondary heat and/or secondary cooling, which may be activated when the primary heating or primary cooling is insufficient. In dual fuel systems, such as systems operating from either electricity or natural gas, control signals related to the selection of the fuel may be monitored. Further, additional status and error signals may be monitored, such as a defrost status signal, which may be asserted when the compressor is shut off and a defrost heater operates to melt frost from an evaporator.
The control lines may be monitored by attaching leads to terminal blocks at the control module 112 at which the fan and heat signals are received. These terminal blocks may include additional connections where leads can be attached between these additional connections and the air handler monitor module 200. Alternatively, leads from the air handler monitor module 200 may be attached to the same location as the fan and heat signals, such as by putting multiple spade lugs underneath a single screw head.
In various implementations, the cool signal from the thermostat 208 may be disconnected from the control module 112 and attached to the air handler monitor module 200. The air handler monitor module 200 can then provide a switched cool signal to the control module 112. This allows the air handler monitor module 200 to interrupt operation of the air conditioning system, such as upon detection of water by one of the water sensors. The air handler monitor module 200 may also interrupt operation of the air conditioning system based on information from the condensing monitor module 204, such as detection of a locked rotor condition in the compressor.
A condensate sensor 220 measures condensate levels in the condensate pan 146. If a level of condensate gets too high, this may indicate a plug or clog in the condensate pan 146 or a problem with hoses or pumps used for drainage from the condensate pan 146. The condensate sensor 220 may be installed along with the air handler monitor module 200 or may already be present. When the condensate sensor 220 is already present, an electrical interface adapter may be used to allow the air handler monitor module 200 to receive the readings from the condensate sensor 220. Although shown in
Additional water sensors, such as a conduction (wet floor) sensor may also be installed. The air handler unit 136 may be located on a catch pan, especially in situations where the air handler unit 136 is located above living space of the building. The catch pan may include a float switch. When enough liquid accumulates in the catch pan, the float switch provides an over-level signal, which may be sensed by the air handler monitor module 200.
A return air sensor 224 is located in a return air plenum 228. The return air sensor 224 may measure temperature and may also measure mass airflow. In various implementations, a thermistor may be multiplexed as both a temperature sensor and a hot wire mass airflow sensor. In various implementations, the return air sensor 224 is upstream of the filter 104 but downstream of any bends in the return air plenum 228.
A supply air sensor 232 is located in a supply air plenum 236. The supply air sensor 232 may measure air temperature and may also measure mass airflow. The supply air sensor 232 may include a thermistor that is multiplexed to measure both temperature and, as a hot wire sensor, mass airflow. In various implementations, such as is shown in
A differential pressure reading may be obtained by placing opposite sensing inputs of a differential pressure sensor (not shown) in the return air plenum 228 and the supply air plenum 236, respectively. For example only, these sensing inputs may be collocated or integrated with the return air sensor 224 and the supply air sensor 232, respectively. In various implementations, discrete pressure sensors may be placed in the return air plenum 228 and the supply air plenum 236. A differential pressure value can then be calculated by subtracting the individual pressure values.
A filter camera 238 may be located in the return plenum 228 near the filter 104. The filter camera 238 captures images of the filter 104. A light source (not shown) may illuminate the filter 104. The air handler monitor module 200 receives the images from the filter camera 238 and may determine a condition of the filter 104—for example, a usage level of the filter—based on the received images. In various implementations, a reflectance or transmittance photosensor (and light source) may be used in place of the filter camera 238.
The air handler monitor module 200 also receives a suction line temperature from a suction line temperature sensor 240. The suction line temperature sensor 240 measures refrigerant temperature in the refrigerant line between the evaporator 144 of
The air handler monitor module 200 may include one or more expansion ports to allow for connection of additional sensors and/or to allow connection to other devices, such as a home security system, a proprietary handheld device for use by contractors, or a portable computer.
The air handler monitor module 200 also monitors control signals from the thermostat 208. Because one or more of these control signals is also transmitted to the condensing unit 164 of
The air handler monitor module 200 may transmit frames of data corresponding to periods of time. For example only, 7.5 frames may span one second (in other words, 0.1333 seconds per frame). Each frame of data may include voltage, current, temperatures, control line status, and water sensor status. Calculations may be performed for each frame of data, including averages, powers, RMS, and FFT. Then the frame is transmitted to the monitoring system.
The voltage and current signals may be sampled by an analog-to-digital converter at a certain rate, such as 1920 samples per second. The frame length may be measured in terms of samples. When a frame is 256 samples long, at a sample rate of 1920 samples per second, there will be 7.5 frames per second.
The sampling rate of 1920 Hz has a Nyquist frequency of 960 Hz and therefore allows an FFT bandwidth of up to approximately 960 Hz. An FFT limited to the time span of a single frame may be calculated for each frame. Then, for that frame, instead of transmitting all of the raw current data, only statistical data (such as average current) and frequency-domain data are transmitted. This conserves substantial bandwidth compared to transmitting all of the raw data.
This gives the monitoring system current data having a 7.5 Hz resolution, and gives frequency-domain data with approximately the 960 Hz bandwidth. The time-domain current and/or the derivative of the time-domain current may be analyzed to detect impending or existing failures. In addition, the current and/or the derivative may be used to determine which set of frequency-domain data to analyze. For example, certain time-domain data may indicate the approximate window of activation of a hot surface igniter, while frequency-domain data is used to assess the state of repair of the hot surface igniter.
In various implementations, the air handler monitor module 200 may only transmit frames during certain periods of time. These periods may be critical to operation of the HVAC system. For example, when thermostat control lines change, the air handler monitor module 200 may record data and transmit frames for a predetermined period of time after that transition. Then, if the HVAC system is operating, the air handler monitor module 200 may intermittently record data and transmit frames until operation of the HVAC system has completed.
The air handler monitor module 200 transmits data measured by both the air handler monitor module 200 itself and the condensing monitor module 204 over a wide area network 248, such as the Internet (referred to as the Internet 248). The air handler monitor module 200 may access the Internet 248 using a router 252 of the customer. The customer router 252 may already be present to provide Internet access to other devices (not shown) within the building, such as a customer computer and/or various other devices having Internet connectivity, such as a DVR (digital video recorder) or a video gaming system.
The air handler monitor module 200 communicates with the customer router 252 using a proprietary or standardized, wired or wireless protocol, such as Bluetooth, ZigBee (IEEE 802.15.4), 900 Megahertz, 2.4 Gigahertz, or WiFi (IEEE 802.11). In various implementations, a gateway 256 is implemented, which creates a wired (such as powerline) or wireless connection to the air handler monitor module 200. The gateway 256 may interface with the customer router 252 using a wired or wireless protocol, such as Ethernet (IEEE 802.3).
The thermostat 208 may also communicate with the customer router 252 using WiFi.
Alternatively, the thermostat 208 may communicate with the customer router 252 via the gateway 256. In various implementations, the air handler monitor module 200 and the thermostat 208 do not communicate directly. However, because they are both connected through the customer router 252 to a remote monitoring system, the remote monitoring system may allow for control of one based on signals from the other. For example, various faults identified based on information from the air handler monitor module 200 may cause the remote monitoring system to adjust temperature setpoints of the thermostat 208 and/or display warning or alert messages on the thermostat 208.
In various implementations, the transformer 212 may be omitted, and the air handler monitor module 200 may include a power supply that is directly powered by the incoming AC power. Further, power-line communications may be conducted over the AC power line instead of over lower-voltage HVAC control lines.
In various implementations, the current sensor 400 may be omitted, and instead a voltage sensor (not shown) may be used. The control module 112 includes an internal transformer that provides the power (e.g., 24 Volts) for the thermostat control signals as well as for other components of the air handler unit 136, such as relays and valves.
The voltage sensor measures the voltage of an output of a transformer internal to the control module 112. The air handler monitor module 200 may measure the voltage of the incoming AC power and calculate a ratio of the voltage input to the internal transformer to the voltage output from the internal transformer. As the current load on the internal transformer increases, the impedance of the internal transformer causes the voltage of the output power to decrease. Therefore, the current draw from the internal transformer can be inferred from the measured ratio (also called an apparent transformer ratio). The inferred current draw may be used in place of the directly measured aggregate current draw described in the present disclosure.
In
A current sensor 264 measures current entering the condensing unit 164. The condensing monitor module 204 may also measure voltage from the supply provided by the transformer 260. Based on measurements of the voltage and current, the condensing monitor module 204 may calculate power and/or may determine power factor. In various implementations, a power sensor (not shown) may be used in addition to or in place of the current sensor 264. The power sensor may provide readings of real power consumed by the current-consuming components of the condensing unit 164.
A liquid line temperature sensor 266 measures the temperature of refrigerant traveling from the condenser 152 to the air handler unit 136. In various implementations, the liquid line temperature sensor 266 is located prior to any filter-drier, such as the filter-drier 154 of
In various implementations, the condensing monitor module 204 may receive ambient temperature data from a temperature sensor (not shown). When the condensing monitor module 204 is located outdoors, the ambient temperature represents an outside ambient temperature. The temperature sensor supplying the ambient temperature may be located outside of an enclosure of the condensing unit 164. Alternatively, the temperature sensor may be located within the enclosure, but exposed to circulating air. In various implementations the temperature sensor may be shielded from direct sunlight and may be exposed to an air cavity that is not directly heated by sunlight. Alternatively or additionally, online (including Internet-based) weather data based on a geographical location of the building may be used to determine sun load, outside ambient air temperature, precipitation, and humidity.
In various implementations, the condensing monitor module 204 may receive refrigerant temperature data from refrigerant temperature sensors (not shown) located at various points, such as before the compressor 148 (referred to as a suction line temperature), after the compressor 148 (referred to as a compressor discharge temperature), after the condenser 152 (referred to as a liquid line out temperature), and/or at one or more points along a coil of the condenser 152. The location of temperature sensors may be dictated by a physical arrangement of the condenser coils. Additionally or alternatively to the liquid line out temperature sensor, a liquid line in temperature sensor may be used. An approach temperature may be calculated, which is a measure of how close the condenser 152 has been able to bring the liquid line out temperature to the ambient air temperature.
During installation, the location of the temperature sensors may be recorded. Additionally or alternatively, a database may be maintained that specifies where temperature sensors are placed. This database may be referenced by installers and may allow for accurate remote processing of the temperature data. The database may be used for both air handler sensors and compressor/condenser sensors. The database may be prepopulated by the monitoring company or may be developed by trusted installers, and then shared with other installation contractors.
As described above, the condensing monitor module 204 may communicate with the air handler monitor module 200 over one or more control lines from the thermostat 208. In these implementations, data from the condensing monitor module 204 is transmitted to the air handler monitor module 200, which in turn uploads the data over the Internet 248.
In various implementations, the transformer 260 may be omitted, and the condensing monitor module 204 may include a power supply that is directly powered by the incoming AC power. Further, power-line communications may be conducted over the AC power line instead of over lower-voltage HVAC control lines.
In
In various implementations, a current sensor 280 is implemented to measure one or more currents of the control signals. The current sensor 280 may measure an aggregate current of all the control lines arriving at the condensing unit 268. The aggregate current may be obtained by measuring the current of a common control return conductor. The aggregate current measured by the current sensor 280 may be used to determine the state of multiple heat pump control signals, such as signals that control operation of defrosting functions and the reversing valve. The aggregate current measured by the current sensor 280 may also be used to determine the state of calls for varying levels of compressor capacity. While not shown in
In
The filter monitor module 306 receives HVAC data, such as power data from an energy monitor, that indicates whether the circulator blower of the HVAC system is running and indicates a speed of the circulator blower. For example, the mode in which the HVAC system is operating (heating, cooling, fan-only) may indicate the speed of the circulator blower. The speed of the circulator blower may also be inferred from the power draw of the circulator blower or even from the power draw of the air handler unit because the power draw of the circulator blower is such a large contributor to overall power draw.
The energy monitor may be a whole-building energy monitor installed at an electrical distribution panel, also referred to as a current or power de-aggregator device. In various implementations, the filter monitor module 306 may be based on a simplified implementation of the air handler monitor module and in fact may be a depopulated (certain components not placed on a printed circuit board) version of the air handler monitor module 200.
The remote monitoring system 304 includes a monitoring server 308 that receives data from the air handler monitor module 200 and the thermostat 208 and maintains and verifies network continuity with the air handler monitor module 200. The remote monitoring system may also receive data from the filter monitor module 306. The monitoring server 308 executes various algorithms to identify problems, such as failures or decreased efficiency, and to predict impending faults.
The monitoring server 308 may notify a review server 312 when a problem is identified or a fault is predicted. This programmatic assessment may be referred to as an advisory. Some or all advisories may be triaged by a technician to reduce false positives and potentially supplement or modify data corresponding to the advisory. For example, a technician device 316 operated by a technician is used to review the advisory and to monitor data (in various implementations, in real-time) from the air handler monitor module 200 via the monitoring server 308.
The technician using the technician device 316 reviews the advisory. If the technician determines that the problem or fault is either already present or impending, the technician instructs the review server 312 to send an alert to either or both of a contractor device 320 or a customer device 324. The technician may determine that, although a problem or fault is present, the cause is more likely to be something different than specified by the automated advisory. The technician can therefore issue a different alert or modify the advisory before issuing an alert based on the advisory. The technician may also annotate the alert sent to the contractor device 320 and/or the customer device 324 with additional information that may be helpful in identifying the urgency of addressing the alert and presenting data that may be useful for diagnosis or troubleshooting.
In various implementations, minor problems may be reported to the contractor device 320 only so as not to alarm the customer or inundate the customer with alerts. Whether the problem is considered to be minor may be based on a threshold. For example, an efficiency decrease greater than a predetermined threshold may be reported to both the contractor and the customer, while an efficiency decrease less than the predetermined threshold is reported to only the contractor.
In some circumstances, the technician may determine that an alert is not warranted based on the advisory. The advisory may be stored for future use, for reporting purposes, and/or for adaptive learning of advisory algorithms and thresholds. In various implementations, a majority of generated advisories may be closed by the technician without sending an alert.
Based on data collected from advisories and alerts, certain alerts may be automated. For example, analyzing data over time may indicate that whether a certain alert is sent by a technician in response to a certain advisory depends on whether a data value is on one side of a threshold or another. A heuristic can then be developed that allows those advisories to be handled automatically without technician review. Based on other data, it may be determined that certain automatic alerts had a false positive rate over a threshold. These alerts may be put back under the control of a technician.
In various implementations, the technician device 316 may be remote from the remote monitoring system 304 but connected via a wide area network, such as the Internet 248. For example only, the technician device 316 may include a computing device such as a laptop, desktop, or tablet.
With the contractor device 320, the contractor can access a contractor portal 328, which provides historical and real-time data from the air handler monitor module 200. The contractor using the contractor device 320 may also contact the technician using the technician device 316. The customer using the customer device 324 may access a customer portal 332 in which a graphical view of the system status as well as alert information is shown. The contractor portal 328 and the customer portal 332 may be implemented in a variety of ways according to the present disclosure, including as an interactive web page, a computer application, and/or an app for a smartphone or tablet.
In various implementations, data shown by the customer portal may be more limited and/or more delayed when compared to data visible in the contractor portal 328. In various implementations, the contractor device 320 can be used to request data from the air handler monitor module 200, such as when commissioning a new installation.
In various implementations, some or all of the functionality of the remote monitoring system 304 may be local instead of remote from the building. For example only, some or all of the functionality may be integrated with the air handler monitor module 200 or the condensing monitor module 204. Alternatively, a local controller, such as a building management system, may implement some of all of the functionality of the remote monitoring system 304.
Detection of various faults and calculation of filter usage may require knowledge of which mode the HVAC system is operating in, and more specifically, which mode has been commanded by the thermostat. For example, when a call for heat is made, the furnace will progress through a sequence of states. For example only, the sequence may begin with activating the inducer blower, opening the gas valve, igniting the gas, and turning on the circulator blower. Each of these states may be detectable in current data, although frequency-domain as well as time-domain data may be necessary to reliably determine certain states. When this sequence of states appears to indicate that the furnace is restarting, a fault may be declared. A furnace restart may be detected when the measured current matches a baseline current profile for a certain number of states and then diverges from the baseline current profile for the next state or states.
Filter usage may be estimated based on power consumed by the motor of the circulator blower 108. The power consumption is determined based on measured parameters such as voltage supplied to the motor, current through the motor, and elapsed time. Additionally or alternatively, a dirty filter may be detected based on changes in power, current, and power factor coupled with a decrease in temperature split and reduced pressure. The power, current, and power factor may be dependent on motor type. When a mass airflow sensor is available, the mass airflow sensor may be able to directly indicate a flow restriction in systems using a permanent-split capacitor motor.
Returning back to
Further, because connecting leads may require removing and reattaching control lines from the control module, the loose connection may even affect normal operation of the HVAC system, such as the ability of the thermostat 208 to control certain aspects of the control module 112. Further, a location at which the control lines are accessible may be difficult for an installer to reach without removing other components of the HVAC system, which increases installation time and also increases the risk of introducing problems.
With multiple connections, even when the control lines are successfully connected, there is a risk that the connections will be misidentified—for example, leading the monitoring system to believe that a call for cool has been made by the thermostat 208 when, in fact, a call for heat was instead made. Some HVAC systems may use those control lines in a non-standard way. Again, this may lead to misinterpretation of the control signals by the monitoring system. A further complication is introduced by “communicating systems,” which do not rely on standard HVAC control lines and instead multiplex multiple signals onto one or more control lines. For example only, in a communicating system, the thermostat 208 and the control module 112 may perform bidirectional digital communication using two or more lines. As a result, individual control lines corresponding to each mode of operation of the HVAC system may not be present.
The present disclosure presents an alternative to individually sensing the control lines and this alternative may eliminate or mitigate some or all of the issues identified above. When the thermostat 208 makes a call for heat, one or more components of the HVAC system will draw a current to service the call for heat. For example, a relay (not shown) may be energized to open the gas valve 128. Meanwhile, when a call for cool is made by the thermostat 208, other components may draw a current—for example, a relay may control the control module 156.
The current consumed by these various devices may be different. For example, the current required to close a switch of the control module 156 may be greater than the current required to open the gas valve 128. An aggregate control line current may therefore uniquely indicate various modes of operation. In
In some HVAC systems, the difference in current between two different modes may not be distinguishable with sufficient accuracy. For these situations, additional sensing may be required. For example, a sensor may be connected to a specific control line to provide additional information so that the mode of operation can be disambiguated.
In
When a call for heating is combined with a call for fan, both control lines, “W” and “G” are activated, resulting in an aggregate line current of 150 mA. When a call for cool is made, control lines “Y” and “G” are activated with a resulting control line current of 600 mA.
Note that for the heating mode, the “W” control line can be activated by itself (without requiring activation of the “G” line). This is because in some HVAC systems, such as used for
Note that the control line currents for activation of the “W” and “G” control lines independently do not add up to equal the control line current when the “W” and “G” lines are activated together. The inability to calculate the aggregate control line current by linear superposition may be a common feature in HVAC systems. For example, various components activated by the “W” control line and the “G” control line may be common so that when both the “W” and “G” control lines are activated, those common components only contribute once to the aggregate control line current.
In
In systems without cooling, the “Y” line may be omitted and, in systems without heating, the “W” line may be omitted. Further, the “G” line may be omitted in systems where the fan is only actuated automatically. Additional control lines that may be present include a “Y2” line that indicates a second stage call for cool. For example, the “Y2” line may indicate that the cooling should be greater or lesser than for the “Y” line. An adjustment in the amount of cooling may be accomplished by adjusting how many compressors are used to provide cooling and/or by adjusting a capacity of a compressor, such as with an unloader valve, a variable speed drive, etc.
A “W2” line may provide for second stage heating, which in a heat pump may include an electric secondary heating element. An “O/B” line may be used to control a mode of the heat pump. The heat pump systems may include additional control lines such as an EMR (Energy Management Recovery) line or an auxiliary heat line. Additional and alternative control lines may be present in various other HVAC systems for which the monitoring system is used.
While the letter of each control line may indicate a commonly-used color for the shielding of the wire, the actual colors and labels of the control lines may differ in real world systems. For this reason, the aggregate current may be a more reliable indicator of mode than the state of individual, unspecified control lines.
In
In
Control continues at 608 where a new current measurement is received. Control continues at 612 where, if an absolute value of the difference between the present current and the stored old current is greater than a threshold, control transfers to 616; otherwise, control transfers to 620. At 616, a timer is started at a value of zero and the present current is stored as the old current. Control then returns to 608.
The timer may be implemented to force a wait interval for the aggregate current value to stabilize at a steady state value. When the mode of the HVAC system changes, the value of the current may initially take a period of time to stabilize. At 620, if the timer is running, indicating that a large change in current had occurred, implying a potential change in mode, control transfers to 624; otherwise, control returns to 608.
At 624, the timer was started and, therefore, the present value of the timer is compared to a predetermined stable period of time. If the timer exceeds that predetermined stable period, control transfers to 628; otherwise, control returns to 608. At 628, the timer is stopped and at 632 the current, which is the most recent value of the current and represents a steady state current, is looked up in an operational table.
For example only, the operational table may be similar in concept to that shown in
In various implementations, the operational table may be predefined based on the identity of the HVAC system. The current levels may be empirically determined and/or specified by the manufacturer for a specific model and configuration of HVAC system. This table may be stored in the monitoring system and accessed based on an identifier associated with the installed HVAC system. In other implementations, the operational table may be generated as part of a calibration routine, which may be performed by an installer of the monitoring system and/or a customer.
In various implementations, the thermostat may have a predetermined calibration routine to allow this table to be generated by cycling through each of the modes in a predetermined order. In implementations where the operational table is predefined, a determination that the current is not present in the operational table signals an error. This may be reported to the customer and/or an HVAC contractor as either the table needs to be updated or a fault is causing the current to deviate from what is predefined in the table.
In the example shown in
Further, the supply air temperature may indicate whether heating or cooling is being performed. And specifically, a difference between the supply air temperature and the return air temperature indicates whether heat is being added to or removed from circulating air. In situations where the supply air and return air temperatures differ by only a small amount, an airflow sensor may be able to determine whether the fan-only mode is engaged. Meanwhile, when the supply air and return air temperatures differ by only a small amount and there is an indication of minimal air low (such as from an airflow sensor), the system is likely in an idle state.
Various other heuristics may be used, such as an inference that a control line current that is more than ten times a lowest measured current corresponds to a cooling mode. This is because the contactor for an air conditioning compressor may draw significantly more current than the components active in an idle system. The time of year and geographical location of the HVAC system may inform the mode inference. For example, a current level that is first seen in October, in a colder climate of the Northern hemisphere, is likely to be related to a call for heating.
In addition, system current data (i.e., the measured currents from current sensors 216 and 264) can be used to infer the operating mode of the HVAC system. Air conditioning, gas furnace, electric heater, and fan-only modes may exhibit distinct system current patterns. For example, air conditioning and fan-only modes may have the same indoor current pattern (including just the blower motor). However, the air conditioning mode will exhibit a significant outdoor system current draw.
A gas furnace has a distinctive system current profile that starts with inducer fan operation, followed by ignition, then a purging (or waiting) period to allow the heat exchanger to heat up, then blower operation. Meanwhile, an electric heater generally draws significantly greater indoor system current than does a gas-powered furnace and also does not have the initial steps (inducer fan, ignition, etc.) associated with a gas furnace.
After the mode is inferred, control continues at 648, where the current level and mode are added to the operational table. Control then continues at 640. At 640, control reports the operational mode that is determined from the table. The reported operational mode may be reflected on the contractor portal 328 or the customer portal 332 of the remote monitoring system 304.
In addition, the table may be updated with information regarding how the present current differs from the stored current level. For example, if, over time, all of the current levels associated with the heating mode are five percent higher than the nominal current level stored in the operational table, the operational table may be adjusted so that the measured current falls in the middle of the range of the stored current level. This may allow for small drifts in current as the HVAC system ages.
At 652, control determines a system condition of the HVAC system. The system condition may include detections of various faults, including those described above. The system condition may include predictions of various faults, as described above. The system condition may also include a reduction in performance or efficiency—while such a condition may also be characterized as a fault, it may be treated separately from a fault when there is no corresponding system component that has actually failed. Control then returns to 604.
Control begins at 704 of
At 712, control sets a capacity of the air filter (Filter_Capacity) using equation 1 below.
Filter_Capacity=cooling tonnage*filter thickness*multiplier1 (1)
Multiplier1 is a predetermined value, such as 150, that represents an adjustment factor specific to permanent-split capacitor motors. In some implementations, control may adjust the calculated capacity of the air filer (Filter_Capacity) based on a minimum efficiency reporting value (MERV) rating of the air filter. For example, control may decrease the value of Filter_Capacity for a filter with a high rating—such as MERV 11—and increase the value of Filter_Capacity for a filter with a low rating—such as MERV 5. Control then continues with 720.
At 716, control sets the capacity of the air filter (Filter_Capacity) using equation 2 below.
Filter_Capacity=cooling tonnage*filter thickness*multiplier2 (2)
Multiplier2 is a predetermined value, such as 90, that represents an adjustment factor specific to electronically commutated motors. In some implementations, control may adjust the calculated capacity of the air filer (Filter_Capacity) based on the MERV rating of the air filter. Control then continues with 720.
At 720, control determines whether the monitoring system was installed in an existing HVAC system. If so, control progresses to 724; otherwise, the installation of the monitoring system was part of an installation of a new HVAC system and control transfers to 728. At 724, control determines whether a new air filter has been installed. For example, the air handler monitor module 200 may use the filter camera 238 to compare the color of an image of the installed filter to the color of a new filter. In other implementations, the monitoring system may use the remote monitoring system 304 to instruct an operator of the HVAC system to confirm that a new filter has been installed. If presence of a new filter is identified at 724, control continues with 728; otherwise, control transfers to 732. At 728, control sets a cumulative value, in watt-hours, for the filter (Total_WH) to zero. Control then continues with 736.
At 732, control sets Total_WH to a value based on the condition of the installed filter. In an example implementation, the air handler monitor module 200 may use the filter camera 238 to determine the condition of the filter based on the color or light transmittance of the filter. For example, the air handler monitor module 200 may compare the color of the image of the installed filter to colors of filters with known total watt-hours. In other implementations, the monitoring system may use the remote monitoring system 304 to instruct the operator of the HVAC system to provide the condition of the installed filter. For example, the remote monitoring system 304 may display a set of images of filters on the contractor device 320 and/or the customer device 324 and prompt the operator to select the image that most closely matches the installed filter—for example, an image with the same or similar color as the installed filter. Based on the operator's selection, the monitoring system sets Total_WH to a value associated with the selected image. Control then continues with 736.
At 736, control initializes a counter to zero. Control then continues with 740 of
At 752, control starts and resets a timer to zero, measures a current through the motor of the circulator blower 108, and initializes a value indicating average RMS current through the motor of the circulator blower 108 (Avg_C) to the measured current. Control then continues with 760 where control determines whether the timer is greater than or equal to the predetermined period of time (T). If so, control progresses to 764; otherwise, control transfers to 768 where control measures the current through the circulator blower motor and updates the average current through the circulator blower motor (Avg_C) based on the measured current. Control then returns to 760.
At 764, control increases Total_WH using equation 3 below.
Total_WH+=Avg_C*Voltage*T (3)
Voltage is the nominal RMS voltage supplied to the motor of the circulator blower 108. Control then continues with 772.
Equation 3 above is based on the presence of a typical level of particulate matter in air returned to the air handler unit 136. The monitoring system may adjust the value added to the total of watt-hours of the filter each cycle based on a particulate matter level specific to the HVAC system. For example, the monitoring system may multiply the quantity (Avg_C*Voltage*T) by a correction factor. The correction factor is a ratio of the particulate matter level specific to the HVAC system to the typical particulate matter level. In other words, if the particulate matter level specific to the HVAC system is 50% greater than the nominal level, the correction factor will be 1.5. In various implementations, the monitoring system may use a particulate matter sensor located within the building to measure the particulate matter level specific to the HVAC system. The particulate matter level may be measured and the correction factor adjusted each time the monitoring system updates the total watt-hours of the filter (Total_WH). In other implementations, the monitoring system may prompt the operator to provide the particulate matter level specific to the HVAC system. In such implementations, the correction factor is only adjusted in response to the operator providing a new particulate matter level. This level may be supplied to the operator by a sensor or determined subjectively by the operator, such as based on how quickly dust accumulates on a surface.
At 772, control determines whether the filter has reached a predetermined usage level, such as 90% of the capacity of the filter. In other words, control may determine if Total_WH is greater than or equal to 90% of Filter_Capacity. If so, control progresses to 776; otherwise, control transfers to 780. At 776, control determines if the filter is full. For example, control determines whether the total of watt-hours of the filter (Total_WH) is greater than or equal to the capacity of the filter (Filter_Capacity). If so, control progresses to 784; otherwise, control transfers to 788. At 784, control selectively generates an alert indicating the filter is full and needs to be changed. Control then continues with 780. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 784 each day. In other implementations, control may generate the alert every time control reaches 784.
At 788, control determines a remaining life of the filter (Remaining_Time) based on the capacity of the filter and past filter usage. For example, control may calculate Remaining_Time using equation 4 below.
The product of the predetermined period of time and the counter (T*Counter) represents the total length of time that the filter has been installed. Control then continues with 792 where control selectively generates an alert that indicates the filter is near capacity and includes the remaining life of the filter (Remaining_Time). Control then continues with 780. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 792 each day. In other implementations, control may generate the alert every time control reaches 792.
At 780, control determines if a new filter has been installed. If so, control progresses to 728 of
Control begins at 803 of
Filter_Capacity=Filter_Area*filter thickness*multiplier (5)
The multiplier is a predetermined value based on an average filter life, such as 750 hours, divided by an average filter area, such as 150 in2. In some implementations, control may adjust the calculated capacity of the air filer (Filter_Capacity) based on a MERV rating of the air filter. Control then continues with 812.
At 812, control determines whether the monitoring system was installed into an existing HVAC system. If so, control progresses to 815; otherwise, the installation of the monitoring system was part of an installation of a new HVAC system and control transfers to 818. At 815, control determines whether a new air filter has been installed. For example, the air handler monitor module 200 may use the filter camera 238 to compare the color of an image of the installed filter to the color of a new filter. In other implementations, the monitoring system may use the remote monitoring system 304 to instruct an operator of the HVAC system to confirm that a new filter has been installed. If presence of a new filter is identified at 815, control progresses to 818; otherwise, control transfers to 821. At 818, control sets a filter usage (Filter_Hours) to zero. Control then continues with 824.
At 821, control sets the filter usage (Filter_Hours) to a value based on the condition of the installed filter. In an example implementation, the air handler monitor module 200 may use the filter camera 238 to determine the condition of the filter based on the color of the filter. For example, the air handler monitor module 200 may compare the color of the image of the installed filter to colors of filters with known total watt-hours. In other implementations, the monitoring system may use the remote monitoring system 304 to instruct the operator of the HVAC system to provide the condition of the installed filter. For example, the remote monitoring system 304 may display a set of images of filters on the contractor device 320 and/or the customer device 324 and prompt the operator to select the image that most closely matches the installed filter—for example, an image with the same or similar color as the installed filter. Based on the operator's selection, the monitoring system sets the filter usage (Filter_Hours) to a value associated with the selected image. Control then continues with 824.
At 824, control initializes a counter to zero. Control then continues with 827 of
At 839, control determines the present operation mode of the HVAC system. For example, control may determine the operation mode based on control line current using the method disclosed in
At 851, control determines whether the current mode is “Cool_2”—for example secondary or extra cooling. If so, control progresses to 854; otherwise, control transfers to 857. At 854, control updates the filter usage (Filter_Hours) by adding the product of the predetermined period of time (T) and a first adjustment factor, such as 1.2, to the present value of Filter_Hours. Control then continues with 842.
At 857, control determines whether the current mode is “Heat.” If so, control progresses to 860; otherwise, control transfers to 863. At 860, control updates the filter usage (Filter_Hours) by adding the result of dividing the predetermined period of time (T) by the first adjustment factor to the present value of Filter_Hours. Control then continues with 842.
At 863, control determines whether the current mode is “Heat_2”—for example, secondary or extra heating. If so, control progresses to 866; otherwise, control transfers to 869. At 866, control updates the filter usage (Filter_Hours) by adding the product of the predetermined period of time (T) and a second adjustment factor, such as 1.1, to the present value of Filter_Hours. Control then continues with 842. At 869, control updates the filter usage (Filter_Hours) by adding the result of dividing the predetermined period of time (T) by the second adjustment factor to the present value of Filter_Hours. Control then continues with 842.
In elements 848, 854, 860, 866, and 869 of
At 842, control determines whether the filter has reached a predetermined usage level, such as 90% of the capacity of the filter. In other words, control may determine if Filter_Hours is greater than or equal to 90% of Filter_Capacity. If so, control progresses to 872; otherwise, control transfers to 875. At 872, control determines if the filter is full. For example, control determines whether the filter usage (Filter_Hours) is greater than or equal to the capacity of the filter (Filter_Capacity). If the filter is full, control progresses to 878; otherwise, control transfers to 881. At 878, control selectively generates an alert indicating the filter is full and needs to be changed. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 878 each day. In other implementations, control may generate the alert every time control reaches 878. Control then continues with 875.
At 881, control determines a remaining life of the filter (Remaining_Time) based on the capacity of the filter and past filter usage. For example, control may calculate Remaining_Time using equation 6 below.
The product of the predetermined period of time and the counter (T*Counter) represents the total length of time that the filter has been installed. Control then continues with 884 where control selectively generates an alert that indicates the filter is near capacity and includes the remaining life of the filter (Remaining_Time). In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 884 each day. In other implementations, control may generate the alert every time control reaches 884. At 875, control determines if a new filter has been installed. If so, control progresses to 818 of
Control begins at 904 of
At 912, control sets a capacity, in watt-hours, of the air filter (Filter_Capacity) using equation 1, as discussed with respect to
At 920, control determines whether the monitoring system was installed in an existing HVAC system. If so, control progresses to 924; otherwise, the installation of the monitoring system was part of an installation of a new HVAC system and control transfers to 928. At 924, control determines whether a new air filter has been installed. If presence of a new filter is identified at 924, control continues with 928; otherwise, control transfers to 932. At 928, control sets a cumulative value, in watt-hours, for the filter (Total_WH) to zero and sets a timer (Filter_Timer) to zero. The timer is used to track the length of time that the filter has been installed in the HVAC system. Control then continues with 936.
At 932, control sets Total_WH to a value based on the condition of the installed filter and sets the timer (Filter_Timer) to a value that equals an installation length that corresponds to the condition of the installed filter. Control then continues with 936.
At 936, control starts the timer. Control then continues with 940 of
Control then continues with 944 where control increases Total_WH using equation 7 below.
Total_WH+=power consumed*T (7)
Equation 7 above is based on the presence of a typical level of particulate matter in air returned to the air handler unit 136. As discussed above, the monitoring system may adjust the value added to the total watt-hours of the filter (Total_WH) based on a particulate matter level specific to the HVAC system. Control then continues with 948.
At 948, control determines a remaining life of the filter (Remaining_Time) based on the capacity of the filter and past filter usage. For example, control may calculate Remaining_Time using equation 8 below.
Filter_Timer represents the length of time that the filter has been installed in the HVAC system. Control may also report the remaining time for an operator or contractor to view, such as in a mobile phone application. Control then continues with 952.
At 952, control determines whether the filter has reached a predetermined usage level, such as 90% of the capacity of the filter. In other words, control may determine if Total_WH is greater than or equal to 90% of Filter_Capacity. If so, control progresses to 956; otherwise, control transfers to 960. At 956, control determines if the filter is full. For example, control determines whether the total of watt-hours of the filter (Total_WH) is greater than or equal to the capacity of the filter (Filter_Capacity). If so, control progresses to 964; otherwise, control transfers to 968. At 964, control selectively generates an alert indicating the filter is full and needs to be changed. Control then continues with 960. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 964 each day. In other implementations, control may generate the alert every time control reaches 964.
At 968, control selectively generates an alert that indicates the filter is near capacity and includes the remaining life of the filter (Remaining_Time). Control then continues with 960. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 968 each day. In other implementations, control may generate the alert every time control reaches 968. At 960, control determines if a new filter has been installed. If so, control progresses to 928 of
The remaining life of the filter (Remaining_Time) may be made available to an operator of the HVAC system, regardless of the value of the total of watt-hours of the filter (Total_WH). For example, Remaining_Time may be presented to the operator in the contractor portal 328 and/or the customer portal 332. Additionally or alternatively, a filter usage, such as a percentage, based on the total of watt-hours of the filter (Total_WH) and the capacity of the filter (Filter_Capacity) may be presented to the operator in the contractor portal 328 and/or the customer portal 332.
Control begins at 1003 of
At 1012, control determines whether the monitoring system was installed into an existing HVAC system. If so, control progresses to 1015; otherwise, the installation of the monitoring system was part of an installation of a new HVAC system and control transfers to 1018. At 1015, control determines whether a new air filter has been installed. If presence of a new filter is identified at 1015, control progresses to 1018; otherwise, control transfers to 1021. At 1018, control sets a filter usage (Filter_Hours) to zero. Control also records the date and time that the filter was installed as Install_Time. Control then continues with 1024.
At 1021, control sets the filter usage (Filter_Hours) to a value based on the condition of the installed filter and estimates the installation date and time of the filter (Install_Time) based on the condition of the installed filter. Control then continues with 1024.
At 1024, control sets a previous mode of operation (Prior_Mode) and a new/current mode of operation (New_Mode) of the HVAC system to “Off.” At 1024, control also initializes a timer to zero and then starts the timer. Control then continues with 1027 of
At 1027 of
At 1033, control determines whether the previous mode of operation (Prior_Mode) is “Cool.” If so, control progresses to 1036; otherwise, control transfers to 1039. At 1036, control updates the filter usage (Filter_Hours) by adding the value of the timer to the present value of Filter_Hours. Control then continues with 1030.
At 1039, control determines whether the previous mode of operation (Prior_Mode) is “Cool_2”—for example secondary or extra cooling. If so, control progresses to 1042; otherwise, control transfers to 1045. At 1042, control updates the filter usage (Filter_Hours) by adding the product of the value of the timer and a first adjustment factor, such as 1.2, to the present value of Filter_Hours. Control then continues with 1030.
At 1045, control determines whether the previous mode of operation (Prior_Mode) is “Heat.” If so, control progresses to 1048; otherwise, control transfers to 1051. At 1048, control updates the filter usage (Filter_Hours) by adding the result of dividing the value of the timer by the first adjustment factor to the present value of Filter_Hours. Control then continues with 1030.
At 1051, control determines whether the previous mode of operation (Prior_Mode) is “Heat_2”—for example, secondary or extra heating. If so, control progresses to 1054; otherwise, the present operation mode is a fan only mode and control transfers to 1057. At 1054, control updates the filter usage (Filter_Hours) by adding the product of the value of the timer and a second adjustment factor, such as 1.1, to the present value of Filter_Hours. Control then continues with 1030. At 1057, control updates the filter usage (Filter_Hours) by adding the result of dividing the value of the timer by the second adjustment factor to the present value of Filter_Hours. Control then continues with 1030.
In elements 1036, 1042, 1048, 1054, and 1057 of
At 1030, control resets the timer to zero. Control then continues with 1063. At 1063, control determines and reports a remaining life of the filter (Remaining_Time) based on the capacity of the filter and past filter usage. For example, control may calculate Remaining_Time using equation 9 below.
Control then continues with 1066.
At 1066, control determines whether the filter has reached a predetermined usage level, such as 90% of the capacity of the filter. In other words, control may determine if Filter_Hours is greater than or equal to 90% of Filter_Capacity. If so, control progresses to 1069; otherwise, control transfers to 1072. At 1069, control determines if the filter is full. For example, control determines whether the filter usage (Filter_Hours) is greater than or equal to the capacity of the filter (Filter_Capacity). If so, control progresses to 1075; otherwise, control transfers to 1078.
At 1075, control selectively generates an alert indicating the filter is full and needs to be changed. In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 1075 each day. In other implementations, control may generate the alert every time control reaches 1075. Control then continues with 1072.
At 1078, control selectively generates an alert that indicates the filter is near capacity and includes the remaining life of the filter (Remaining_Time). In various implementations, control may only generate the alert once per day—for example, the first time that control reaches 1078 each day. In other implementations, control may generate the alert every time control reaches 1078. Control then continues with 1072.
At 1072, control determines if a new filter has been installed. If so, control progresses to 1018 of
At 1084, control determines whether HVAC data has been received. In various implementations, control may receive HVAC data—for example, a present operation mode of the HVAC system—from a thermostat, such as the thermostat 208. Alternatively, control may receive HVAC power data that corresponds to the present operation mode of the HVAC system from an energy monitor, such as a whole home energy monitor. If control determines that HVAC data has been received, control progresses to 1087; otherwise, control transfers to 1090. At 1087 control sets the new operation mode (New_Mode) to a value based on the received data. For example, control may set New_Mode to “Cool,” “Cool_2,” “Heat,” “Heat_2,” “Off,” or to a value that represents a fan only operation mode, such as “Fan.” Control then continues with 1027.
At 1090, control determines whether the value of the timer is greater than a timeout threshold—for example, one hour. This may indicate that communications have been lost with the thermostat or energy monitor. If the timer exceeds the threshold, control progresses to 1093; otherwise, control returns to 1084. At 1093, control sets both the previous mode of operation (Prior_Mode) and the new mode of operation (New_Mode) to “Off” This encodes the assumption that the HVAC system turned off soon after the last communication was received. Other assumptions may instead be encoded, such as that the HVAC system turned off after a period of time, such as 30 minutes, or that the HVAC system is still running in its prior mode. Control then continues with 1027.
Elements 1104, 1108, 1112, 1116, 1120, 1124, 1132, 1128, and 1136 may be implemented similarly to elements 904, 908, 912, 916, 920, 924, 932, 928, and 936, respectively, of
In
At 1141 in
In various implementations, the data that represents the consumed power may be transmitted in a frame of data that includes other data associated with operation of the HVAC system—such as voltages, currents, temperatures, and control line status. Frames of data may be transmitted to the external system at a first rate for a predetermined period of time following a new call for heat or cool. For example, frames of data may be transmitted 7.5 times a second for the first 105 seconds following a new call for heat or cool. After the predetermined period of time, a frame of data may be transmitted at a slower rate, such as once every 5 seconds.
In other implementations, the rate at which the frames of data are transmitted is variable. For example, the air handler monitor module 200 may only transmit a frame of data to the remote monitoring system 304 when presently measured or calculated values represent a significant change from the most recently transmitted frame.
As an example, the air handler monitor module 200 may determine significant change based on a comparison of present values to values most recently transmitted. In various implementations, the air handler monitor module 200 determines, for each element (such as a voltage, a temperature, a current, etc.) to be transmitted in a frame, a difference between a present value of the element and the value of the element in the most recently transmitted frame. The air handler monitor module 200 then weights the differences by multiplying each of the differences by a corresponding scalar. The weights may be predetermined and based on the significance of the information represented by the data. The air handler monitor module 200 then calculates the root mean square (RMS) value of all of the weighted differences.
The RMS value is an indicator of how substantially different present values of data are from the last transmission. If the RMS value is greater than a threshold, the air handler monitor module 200 transmits the frame of data that includes the present values; otherwise, the air handler monitor module 200 waits for new values and repeats the process to determine whether to transmit a frame of data that includes the new values.
In some implementations, the threshold may be a variable value that is inversely proportional to the time since the last frame of data was transmitted. For example, the threshold may decrease logarithmically or linearly over time. In other words, as the length of time since the last frame of data was transmitted increases, so does the probability that small determined differences will trigger transmission of a new frame of data. In yet other implementations, the threshold may be a predetermined value.
Control then continues at 1143. If the time since the last sample was received exceeds a threshold, such as 15 minutes, control transfers to 1158, skipping updating the Total_WH value; otherwise, control continues at 1145. The reason for skipping updating the Total_WH is that the likelihood of the new power measurement (Power_New) being applicable to the entire preceding period of the sample timer (which is longer than 15 minutes) is low. Therefore, instead of adding a potentially spurious value, no change is made to Total_WH.
At 1145, control increases the total watt-hours of the filter (Total_WH). For example, control may use equation 10 below to update Total_WH, which relies on the average of Power_New and Power_Old.
In some implementations, control may increment Total_WH based on Power_New and Sample_Timer, exclusive of Power_Old. In other implementations, control may increment Total_WH based on Power_Old and Sample_Timer, exclusive of Power_New.
The increases to Total_WH are based on the presence of a typical level of particulate matter in air returned to the air handler unit 136. As previously discussed, the monitoring system may adjust the value added to Total_WH based on a particulate matter level specific to the HVAC system (such as a measured value). Control then continues with 1148.
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements.
As used in this application, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.” The term subset does not necessarily require a proper subset. In other words, a first subset of a first set may be coextensive with (equal to) the first set.
In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.
In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
The module may include one or more interface circuits. In some examples, the interface circuit(s) may implement wired or wireless interfaces that connect to a local area network (LAN) or a wireless personal area network (WPAN). Examples of a LAN are Institute of Electrical and Electronics Engineers (IEEE) Standard 802.11-2016 (also known as the WiFi wireless networking standard) and IEEE Standard 802.3-2015 (also known as the ETHERNET wired networking standard). Examples of a WPAN are the BLUETOOTH wireless networking standard from the Bluetooth Special Interest Group and IEEE Standard 802.15.4.
The module may communicate with other modules using the interface circuit(s). Although the module may be depicted in the present disclosure as logically communicating directly with other modules, in various implementations the module may actually communicate via a communications system. The communications system includes physical and/or virtual networking equipment such as hubs, switches, routers, and gateways. In some implementations, the communications system connects to or traverses a wide area network (WAN) such as the Internet. For example, the communications system may include multiple LANs connected to each other over the Internet or point-to-point leased lines using technologies including Multiprotocol Label Switching (MPLS) and virtual private networks (VPNs).
In various implementations, the functionality of the module may be distributed among multiple modules that are connected via the communications system. For example, multiple modules may implement the same functionality distributed by a load balancing system. In a further example, the functionality of the module may be split between a server (also known as remote, or cloud) module and a client (or, user) module.
Some or all hardware features of a module may be defined using a language for hardware description, such as IEEE Standard 1364-2005 (commonly called “Verilog”) and IEEE Standard 1076-2008 (commonly called “VHDL”). The hardware description language may be used to manufacture and/or program a hardware circuit. In some implementations, some or all features of a module may be defined by a language, such as IEEE 1666-2005 (commonly called “SystemC”), that encompasses both code, as described below, and hardware description.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.
The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The functional blocks and flowchart elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
The computer programs include processor-executable instructions that are stored on at least one non-transitory computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language), XML (extensible markup language), or JSON (JavaScript Object Notation), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, JavaScript®, HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, LabVIEW, and Python®.
This application is the U.S. National Phase Application under 35 U.S.C. 371 of International Application No. PCT/US2019/028409 filed on Apr. 19, 2019, which claims the benefit of U.S. Provisional Application No. 62/660,905, filed Apr. 20, 2018 and U.S. Provisional Application No. 62/664,040, filed Apr. 27, 2018. The entire disclosures of the applications referenced above are incorporated by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2019/028409 | 4/19/2019 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2019/204791 | 10/24/2019 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 4135370 | Hosoda et al. | Jan 1979 | A |
| 4136529 | McCarty | Jan 1979 | A |
| 4735054 | Beckey | Apr 1988 | A |
| 4922808 | Smith | May 1990 | A |
| 4977818 | Taylor et al. | Dec 1990 | A |
| 5067394 | Cavallero | Nov 1991 | A |
| 5129234 | Alford | Jul 1992 | A |
| 5259553 | Shyu | Nov 1993 | A |
| 5267897 | Drees | Dec 1993 | A |
| 5303561 | Bahel et al. | Apr 1994 | A |
| 5351855 | Nelson et al. | Oct 1994 | A |
| 5394934 | Rein et al. | Mar 1995 | A |
| 5428964 | Lobdell | Jul 1995 | A |
| 5598715 | Edmisten | Feb 1997 | A |
| 5707005 | Kettler et al. | Jan 1998 | A |
| 5832411 | Schatzmann et al. | Nov 1998 | A |
| 5887784 | Haas | Mar 1999 | A |
| 5892690 | Boatman et al. | Apr 1999 | A |
| 5904896 | High | May 1999 | A |
| 6161764 | Jatnieks | Dec 2000 | A |
| 6187263 | Nielsen | Feb 2001 | B1 |
| 6230980 | Hudson | May 2001 | B1 |
| 6251344 | Goldstein | Jun 2001 | B1 |
| 6288646 | Skardon | Sep 2001 | B1 |
| 6358374 | Obee et al. | Mar 2002 | B1 |
| 6369716 | Abbas et al. | Apr 2002 | B1 |
| 6377858 | Koeppe | Apr 2002 | B1 |
| 6391102 | Bodden et al. | May 2002 | B1 |
| 6392536 | Tice et al. | May 2002 | B1 |
| 6394427 | Guetersloh et al. | May 2002 | B1 |
| 6406367 | Chou et al. | Jun 2002 | B1 |
| 6406506 | Moredock et al. | Jun 2002 | B1 |
| 6423118 | Becerra et al. | Jul 2002 | B1 |
| 6448896 | Bankus et al. | Sep 2002 | B1 |
| 6466133 | Skardon | Oct 2002 | B1 |
| 6493638 | McLean et al. | Dec 2002 | B1 |
| 6494053 | Forkosh et al. | Dec 2002 | B1 |
| 6494940 | Hak | Dec 2002 | B1 |
| 6503462 | Michalakos et al. | Jan 2003 | B1 |
| 6557365 | Dinnage et al. | May 2003 | B2 |
| 6578770 | Rosen | Jun 2003 | B1 |
| 6582295 | Abouchaar | Jun 2003 | B1 |
| 6588250 | Schell | Jul 2003 | B2 |
| 6622993 | Mulvaney | Sep 2003 | B2 |
| 6691526 | Gether et al. | Feb 2004 | B2 |
| 6698219 | Sekhar et al. | Mar 2004 | B2 |
| 6711470 | Hartenstein et al. | Mar 2004 | B1 |
| 6752713 | Johnson, Jr. | Jun 2004 | B2 |
| 6790136 | Sharp et al. | Sep 2004 | B2 |
| 6826920 | Wacker | Dec 2004 | B2 |
| 6843068 | Wacker | Jan 2005 | B1 |
| 6848266 | Sheehan | Feb 2005 | B1 |
| 6884399 | Reisfeld et al. | Apr 2005 | B2 |
| 6898960 | Bodnar | May 2005 | B1 |
| 6902592 | Green et al. | Jun 2005 | B2 |
| 6916239 | Siddaramanna et al. | Jul 2005 | B2 |
| 6919809 | Blunn et al. | Jul 2005 | B2 |
| 6920874 | Siegel | Jul 2005 | B1 |
| 6924326 | Meyer et al. | Aug 2005 | B2 |
| 6926079 | Kensok et al. | Aug 2005 | B2 |
| 6941193 | Frecska et al. | Sep 2005 | B2 |
| 6952715 | Kronz | Oct 2005 | B1 |
| 7016791 | Carnegie et al. | Mar 2006 | B2 |
| 7048776 | Moore et al. | May 2006 | B2 |
| 7059400 | Sekhar et al. | Jun 2006 | B2 |
| 7114343 | Kates | Oct 2006 | B2 |
| 7151264 | Ehlers, Sr. | Dec 2006 | B2 |
| 7178350 | Shah | Feb 2007 | B2 |
| 7186290 | Sheehan et al. | Mar 2007 | B2 |
| 7222494 | Peterson et al. | May 2007 | B2 |
| 7241326 | Han et al. | Jul 2007 | B2 |
| 7253743 | Liang et al. | Aug 2007 | B2 |
| 7255831 | Wei et al. | Aug 2007 | B2 |
| 7261762 | Kang et al. | Aug 2007 | B2 |
| 7266960 | Shah | Sep 2007 | B2 |
| 7267017 | Bodnar | Sep 2007 | B1 |
| RE39871 | Skardon | Oct 2007 | E |
| 7291206 | Kiern et al. | Nov 2007 | B1 |
| 7291315 | Obee et al. | Nov 2007 | B2 |
| 7302313 | Sharp et al. | Nov 2007 | B2 |
| 7306650 | Slayzak et al. | Dec 2007 | B2 |
| 7325748 | Acker, Jr. | Feb 2008 | B2 |
| 7326388 | Uslenghi et al. | Feb 2008 | B2 |
| 7357828 | Bohlen | Apr 2008 | B2 |
| 7366588 | Kim et al. | Apr 2008 | B2 |
| 7368003 | Crapser et al. | May 2008 | B2 |
| 7369955 | Lee | May 2008 | B2 |
| 7378064 | Uslenghi et al. | May 2008 | B2 |
| 7381244 | Tyndall et al. | Jun 2008 | B2 |
| 7389158 | Desrochers et al. | Jun 2008 | B2 |
| 7398821 | Rainer et al. | Jul 2008 | B2 |
| 7407624 | Cumberland et al. | Aug 2008 | B2 |
| 7413594 | Paterson et al. | Aug 2008 | B2 |
| 7434413 | Wruck | Oct 2008 | B2 |
| 7475828 | Bartlett et al. | Jan 2009 | B2 |
| 7552030 | Guralnik et al. | Jun 2009 | B2 |
| 7552635 | Chang et al. | Jun 2009 | B2 |
| 7574871 | Bloemer et al. | Aug 2009 | B2 |
| 7621985 | Kuo | Nov 2009 | B1 |
| 7632178 | Meneely, Jr. | Dec 2009 | B2 |
| 7632340 | Brady et al. | Dec 2009 | B2 |
| 7635845 | Jensen et al. | Dec 2009 | B2 |
| 7645323 | Massenbauer-Strafe et al. | Jan 2010 | B2 |
| 7651256 | Lee et al. | Jan 2010 | B2 |
| 7721560 | Carpenter | May 2010 | B2 |
| 7740184 | Schnell et al. | Jun 2010 | B2 |
| 7748639 | Perry | Jul 2010 | B2 |
| 7758408 | Hagentoft | Jul 2010 | B2 |
| 7765792 | Rhodes et al. | Aug 2010 | B2 |
| 7780092 | Ahmed | Aug 2010 | B2 |
| 7789951 | Sung et al. | Sep 2010 | B2 |
| 7811363 | Zhang | Oct 2010 | B2 |
| 7836712 | Sasao et al. | Nov 2010 | B2 |
| 7837958 | Crapser et al. | Nov 2010 | B2 |
| 7839275 | Spalink et al. | Nov 2010 | B2 |
| 7857884 | Bohlen | Dec 2010 | B2 |
| 7857890 | Paterson et al. | Dec 2010 | B2 |
| 7918407 | Patch | Apr 2011 | B2 |
| 7932490 | Wang et al. | Apr 2011 | B2 |
| 7938896 | Paterson et al. | May 2011 | B2 |
| 7951327 | Reisfeld et al. | May 2011 | B2 |
| 7966104 | Srivastava et al. | Jun 2011 | B2 |
| 7979163 | Terlson et al. | Jul 2011 | B2 |
| 8024982 | Pettit et al. | Sep 2011 | B2 |
| 8024986 | Pettit et al. | Sep 2011 | B2 |
| 8066558 | Thomle et al. | Nov 2011 | B2 |
| 8079575 | Novotny et al. | Dec 2011 | B2 |
| 8083398 | Doll | Dec 2011 | B2 |
| 8086407 | Chan et al. | Dec 2011 | B2 |
| 8097067 | Fox et al. | Jan 2012 | B2 |
| 8118236 | Lestage et al. | Feb 2012 | B2 |
| 8147302 | Desrochers et al. | Apr 2012 | B2 |
| 8172154 | Figley et al. | May 2012 | B1 |
| 8190367 | Bassa | May 2012 | B2 |
| 8219249 | Harrod et al. | Jul 2012 | B2 |
| 8231112 | Cao et al. | Jul 2012 | B2 |
| 8231716 | Poon | Jul 2012 | B2 |
| 8239066 | Jennings et al. | Aug 2012 | B2 |
| 8267164 | Lestage et al. | Sep 2012 | B2 |
| 8292270 | Terlson et al. | Oct 2012 | B2 |
| 8318084 | Johnson et al. | Nov 2012 | B2 |
| 8328910 | Mulholland | Dec 2012 | B2 |
| 8333816 | Kummer et al. | Dec 2012 | B2 |
| 8335593 | Johnson et al. | Dec 2012 | B2 |
| 8347643 | Taras et al. | Jan 2013 | B2 |
| 8392025 | Orfield | Mar 2013 | B2 |
| 8397522 | Springer et al. | Mar 2013 | B2 |
| 8398917 | Itzhak et al. | Mar 2013 | B2 |
| 8398923 | Mole | Mar 2013 | B2 |
| 8402815 | Marra | Mar 2013 | B2 |
| 8423192 | Liu | Apr 2013 | B2 |
| 8428901 | Hsieh | Apr 2013 | B2 |
| 8442694 | Jang | May 2013 | B2 |
| 8467977 | Xia et al. | Jun 2013 | B2 |
| 8473429 | Cheng et al. | Jun 2013 | B2 |
| 8479560 | Cobianu et al. | Jul 2013 | B2 |
| 8492722 | Chang et al. | Jul 2013 | B2 |
| 8496514 | Kim et al. | Jul 2013 | B2 |
| 8496735 | Jones et al. | Jul 2013 | B2 |
| 8529830 | Zhou et al. | Sep 2013 | B2 |
| 8544288 | MacDonald | Oct 2013 | B2 |
| 8554375 | Nerling | Oct 2013 | B2 |
| 8555662 | Peterson et al. | Oct 2013 | B2 |
| 8560126 | Vass et al. | Oct 2013 | B2 |
| 8567204 | Seem | Oct 2013 | B2 |
| 8574343 | Bisson et al. | Nov 2013 | B2 |
| 8615327 | Takagi et al. | Dec 2013 | B2 |
| 8640970 | Dorendorf | Feb 2014 | B2 |
| 8651391 | Patch | Feb 2014 | B2 |
| 8683845 | Fleischer et al. | Apr 2014 | B2 |
| 8689572 | Evans et al. | Apr 2014 | B2 |
| 8691144 | Garfield et al. | Apr 2014 | B2 |
| 8696800 | Storm | Apr 2014 | B2 |
| 8700227 | Vass et al. | Apr 2014 | B2 |
| 8726721 | Minges | May 2014 | B2 |
| 8734565 | Hoglund et al. | May 2014 | B2 |
| 8744629 | Wallaert et al. | Jun 2014 | B2 |
| 8755942 | Bonilla et al. | Jun 2014 | B2 |
| 8757154 | Schuller | Jun 2014 | B2 |
| 8758262 | Rhee et al. | Jun 2014 | B2 |
| 8761945 | Hadzidedic | Jun 2014 | B2 |
| 8768521 | Amundson et al. | Jul 2014 | B2 |
| 8797159 | Kirkpatrick et al. | Aug 2014 | B2 |
| 8813583 | Kilps et al. | Aug 2014 | B2 |
| 8838037 | Niederberger et al. | Sep 2014 | B2 |
| 8852501 | Hedman | Oct 2014 | B2 |
| 8860569 | Hruska et al. | Oct 2014 | B2 |
| 8880224 | Eaton et al. | Nov 2014 | B2 |
| 8883083 | Law et al. | Nov 2014 | B2 |
| 8886785 | Apte et al. | Nov 2014 | B2 |
| 8889079 | Zahedi | Nov 2014 | B2 |
| 8892797 | Grohman | Nov 2014 | B2 |
| 8899055 | Kuenzel et al. | Dec 2014 | B2 |
| 8900518 | Seck | Dec 2014 | B2 |
| 8907803 | Martin | Dec 2014 | B2 |
| 8920537 | Seike | Dec 2014 | B2 |
| 8922971 | Abate et al. | Dec 2014 | B2 |
| 8930030 | Bester et al. | Jan 2015 | B2 |
| 8955761 | Malloy | Feb 2015 | B2 |
| 8958918 | Voysey | Feb 2015 | B2 |
| 8961881 | Hagh et al. | Feb 2015 | B2 |
| 8963728 | Kates | Feb 2015 | B2 |
| 8973845 | Kanaya et al. | Mar 2015 | B2 |
| 8978445 | Bergsten | Mar 2015 | B2 |
| 8986427 | Hauville et al. | Mar 2015 | B2 |
| 9010172 | Xia et al. | Apr 2015 | B2 |
| 9019111 | Sloo et al. | Apr 2015 | B1 |
| 9023304 | Nikles | May 2015 | B2 |
| 9040007 | Hui et al. | May 2015 | B2 |
| 9040008 | Zahedi | May 2015 | B2 |
| 9061230 | Barakat | Jun 2015 | B2 |
| 9073009 | Vanderspurt et al. | Jul 2015 | B2 |
| 9078082 | Gill et al. | Jul 2015 | B2 |
| 9080784 | Dean-Hendricks et al. | Jul 2015 | B2 |
| 9091497 | Schwendinger et al. | Jul 2015 | B2 |
| 9092040 | Fadell et al. | Jul 2015 | B2 |
| 9095636 | Schmidt et al. | Aug 2015 | B2 |
| 9097432 | Kreft et al. | Aug 2015 | B2 |
| 9101904 | Yates et al. | Aug 2015 | B2 |
| 9103557 | Choi et al. | Aug 2015 | B2 |
| 9109981 | Sharp | Aug 2015 | B2 |
| 9109989 | Hamann et al. | Aug 2015 | B2 |
| 9121618 | Fisher et al. | Sep 2015 | B2 |
| 9121837 | Chan et al. | Sep 2015 | B2 |
| 9143344 | Cho et al. | Sep 2015 | B2 |
| 9157647 | Leen et al. | Oct 2015 | B2 |
| 9164519 | Holloway | Oct 2015 | B2 |
| 9166992 | Stickle et al. | Oct 2015 | B1 |
| 9175872 | Mckie et al. | Nov 2015 | B2 |
| 9182751 | Reeder | Nov 2015 | B1 |
| 9186609 | Sherman, III et al. | Nov 2015 | B2 |
| 9200804 | Park et al. | Dec 2015 | B2 |
| 9208676 | Fadell et al. | Dec 2015 | B2 |
| 9234667 | Ito et al. | Jan 2016 | B2 |
| 9250633 | Chen et al. | Feb 2016 | B2 |
| 9254459 | Miller | Feb 2016 | B2 |
| 9261290 | Storm | Feb 2016 | B2 |
| 9278304 | Lee | Mar 2016 | B2 |
| 9280884 | Schultz et al. | Mar 2016 | B1 |
| 9286779 | Shaw et al. | Mar 2016 | B2 |
| 9304511 | Blount et al. | Apr 2016 | B2 |
| 9304521 | Kates | Apr 2016 | B2 |
| 9308492 | Obee et al. | Apr 2016 | B2 |
| 9310088 | Melikov et al. | Apr 2016 | B2 |
| 9311807 | Schultz et al. | Apr 2016 | B2 |
| 9316410 | Meirav et al. | Apr 2016 | B2 |
| 9317659 | Balinski et al. | Apr 2016 | B2 |
| 9323895 | Balinski et al. | Apr 2016 | B2 |
| 9325516 | Pera et al. | Apr 2016 | B2 |
| 9328936 | Meirav et al. | May 2016 | B2 |
| 9332322 | Niemeyer et al. | May 2016 | B2 |
| 9344753 | Yerli | May 2016 | B2 |
| 9347678 | Stakutis et al. | May 2016 | B2 |
| 9347860 | Lalain et al. | May 2016 | B1 |
| 9347925 | Shen et al. | May 2016 | B2 |
| 9353964 | Kates | May 2016 | B2 |
| 9353966 | Finkam | May 2016 | B2 |
| 9360229 | Modi et al. | Jun 2016 | B2 |
| 9366448 | Dean-Hendricks et al. | Jun 2016 | B2 |
| 9372010 | Jung et al. | Jun 2016 | B2 |
| 9375672 | Meirav et al. | Jun 2016 | B2 |
| 9377768 | Grohman | Jun 2016 | B2 |
| 9390388 | Drees et al. | Jul 2016 | B2 |
| 9395096 | Fisher et al. | Jul 2016 | B2 |
| 9399187 | Meirav et al. | Jul 2016 | B2 |
| 9400119 | Malloy | Jul 2016 | B2 |
| 9404666 | Terlson et al. | Aug 2016 | B2 |
| 9405301 | Montero et al. | Aug 2016 | B2 |
| 9410752 | Wallace | Aug 2016 | B2 |
| 9416987 | Ragland et al. | Aug 2016 | B2 |
| 9417005 | Roth et al. | Aug 2016 | B1 |
| 9417637 | Matsuoka et al. | Aug 2016 | B2 |
| 9423144 | Evans et al. | Aug 2016 | B2 |
| 9423146 | Bruce et al. | Aug 2016 | B2 |
| 9427728 | Sidheswaran et al. | Aug 2016 | B2 |
| 9449491 | Sager et al. | Sep 2016 | B2 |
| 9459606 | Takayama et al. | Oct 2016 | B2 |
| 9463339 | Nozaki | Oct 2016 | B2 |
| 9464818 | Holm et al. | Oct 2016 | B2 |
| 9498555 | Hingorani et al. | Nov 2016 | B2 |
| 9520250 | O'Keeffe | Dec 2016 | B2 |
| 9522210 | Worrilow | Dec 2016 | B2 |
| 9523665 | Fleischer et al. | Dec 2016 | B2 |
| 9535407 | Durham et al. | Jan 2017 | B2 |
| 9537670 | Cho et al. | Jan 2017 | B2 |
| 9557069 | Matsui et al. | Jan 2017 | B2 |
| 9568445 | Klein et al. | Feb 2017 | B2 |
| 9593859 | Niazi | Mar 2017 | B2 |
| 9593861 | Burnett | Mar 2017 | B1 |
| 9597627 | Zhang | Mar 2017 | B2 |
| 9599353 | Cur et al. | Mar 2017 | B2 |
| 9599357 | Vogel | Mar 2017 | B2 |
| 9612188 | Johnston et al. | Apr 2017 | B2 |
| 9618224 | Emmons et al. | Apr 2017 | B2 |
| 9638434 | Alston | May 2017 | B2 |
| 9638436 | Arensmeier et al. | May 2017 | B2 |
| 9643117 | Rahlin et al. | May 2017 | B2 |
| 9645112 | Chan | May 2017 | B2 |
| 9677777 | Karamanos et al. | Jun 2017 | B2 |
| 9694309 | Weatherman et al. | Jul 2017 | B2 |
| 9696049 | Metteer | Jul 2017 | B2 |
| 9696735 | Matsuoka et al. | Jul 2017 | B2 |
| 9709291 | Dostmann | Jul 2017 | B2 |
| 9714844 | Stamatakis et al. | Jul 2017 | B1 |
| 9715242 | Pillai et al. | Jul 2017 | B2 |
| 9723380 | Patel et al. | Aug 2017 | B2 |
| 9726579 | Han et al. | Aug 2017 | B2 |
| 9729945 | Schultz et al. | Aug 2017 | B2 |
| 9737842 | Matlin et al. | Aug 2017 | B2 |
| 9752789 | Staniforth et al. | Sep 2017 | B2 |
| 9759437 | Kim et al. | Sep 2017 | B2 |
| 9764623 | Fruehsorger et al. | Sep 2017 | B2 |
| 9789436 | Meirav et al. | Oct 2017 | B2 |
| 9797620 | Matsugi et al. | Oct 2017 | B2 |
| 9797812 | Hamann et al. | Oct 2017 | B2 |
| 9803877 | Yun | Oct 2017 | B2 |
| 9810441 | Dean-Hendricks et al. | Nov 2017 | B2 |
| 9816724 | Phannavong et al. | Nov 2017 | B2 |
| 9821260 | Stoner, Jr. et al. | Nov 2017 | B2 |
| 9833734 | Fox et al. | Dec 2017 | B2 |
| 9835348 | Storm et al. | Dec 2017 | B2 |
| 9839872 | Spartz | Dec 2017 | B2 |
| 9851299 | Bertaux | Dec 2017 | B2 |
| 9854335 | Patel et al. | Dec 2017 | B2 |
| 9856883 | Olsen | Jan 2018 | B1 |
| 9857301 | Nourbakhsh et al. | Jan 2018 | B1 |
| 9890969 | Martin | Feb 2018 | B2 |
| 9986313 | Schwarzkopf et al. | May 2018 | B2 |
| 9990842 | Zribi et al. | Jun 2018 | B2 |
| 10976065 | Kohn et al. | Apr 2021 | B2 |
| 11371726 | Pham et al. | Jun 2022 | B2 |
| 11543147 | Rite | Jan 2023 | B1 |
| 20010045159 | Johnson | Nov 2001 | A1 |
| 20030070544 | Mulvaney et al. | Apr 2003 | A1 |
| 20040006886 | Lee et al. | Jan 2004 | A1 |
| 20040109800 | Pahlman et al. | Jun 2004 | A1 |
| 20050098495 | Hughes | May 2005 | A1 |
| 20050277381 | Banerjee et al. | Dec 2005 | A1 |
| 20060055547 | DiMaggio | Mar 2006 | A1 |
| 20060267756 | Kates | Nov 2006 | A1 |
| 20070013534 | DiMaggio | Jan 2007 | A1 |
| 20070082601 | Desrochers et al. | Apr 2007 | A1 |
| 20070155305 | Heidel et al. | Jul 2007 | A1 |
| 20080014857 | Spadafora et al. | Jan 2008 | A1 |
| 20080022705 | Clearman | Jan 2008 | A1 |
| 20080182506 | Jackson et al. | Jul 2008 | A1 |
| 20090079098 | Ezra | Mar 2009 | A1 |
| 20090126382 | Rubino et al. | May 2009 | A1 |
| 20090179338 | Cottier | Jul 2009 | A1 |
| 20090204262 | Nishimura | Aug 2009 | A1 |
| 20110010071 | Rhodes et al. | Jan 2011 | A1 |
| 20110052453 | McLarnon et al. | Mar 2011 | A1 |
| 20110125044 | Rhee et al. | May 2011 | A1 |
| 20110151766 | Sherman et al. | Jun 2011 | A1 |
| 20110184250 | Schmidt et al. | Jul 2011 | A1 |
| 20120095684 | Chan et al. | Apr 2012 | A1 |
| 20120323374 | Dean-Hendricks | Dec 2012 | A1 |
| 20130014522 | Lukasse et al. | Jan 2013 | A1 |
| 20130144527 | Kuhnreichi | Jun 2013 | A1 |
| 20130226352 | Dean-Hendricks et al. | Aug 2013 | A1 |
| 20130287626 | Benedek et al. | Oct 2013 | A1 |
| 20130289778 | Ishizaka | Oct 2013 | A1 |
| 20130323781 | Moularat et al. | Dec 2013 | A1 |
| 20130344609 | Mayer et al. | Dec 2013 | A1 |
| 20140020559 | Meirav et al. | Jan 2014 | A1 |
| 20140053586 | Poecher et al. | Feb 2014 | A1 |
| 20140079564 | Becerra et al. | Mar 2014 | A1 |
| 20140083292 | Weiden | Mar 2014 | A1 |
| 20140109649 | Fleischer et al. | Apr 2014 | A1 |
| 20140129004 | Takayama et al. | May 2014 | A1 |
| 20140139342 | Brown | May 2014 | A1 |
| 20140190679 | Roosli et al. | Jul 2014 | A1 |
| 20140207693 | Horst et al. | Jul 2014 | A1 |
| 20140217185 | Bicknell | Aug 2014 | A1 |
| 20140241970 | Smyrniotis et al. | Aug 2014 | A1 |
| 20140244043 | Foster | Aug 2014 | A1 |
| 20140262837 | Sidheswaran et al. | Sep 2014 | A1 |
| 20140266755 | Arensmeier et al. | Sep 2014 | A1 |
| 20140313048 | Sabata et al. | Oct 2014 | A1 |
| 20140346237 | Mirza et al. | Nov 2014 | A1 |
| 20140354976 | Evenstad et al. | Dec 2014 | A1 |
| 20140365017 | Hanna et al. | Dec 2014 | A1 |
| 20140370800 | Ansari | Dec 2014 | A1 |
| 20150011154 | Holm et al. | Jan 2015 | A1 |
| 20150032264 | Emmons et al. | Jan 2015 | A1 |
| 20150046179 | Kang | Feb 2015 | A1 |
| 20150050876 | Sakai et al. | Feb 2015 | A1 |
| 20150052975 | Martin | Feb 2015 | A1 |
| 20150077737 | Belinsky et al. | Mar 2015 | A1 |
| 20150088786 | Anandhakrishnan | Mar 2015 | A1 |
| 20150140919 | Zwijack | May 2015 | A1 |
| 20150153061 | Riberon et al. | Jun 2015 | A1 |
| 20150153317 | Krebs | Jun 2015 | A1 |
| 20150168003 | Stefanski et al. | Jun 2015 | A1 |
| 20150168964 | Wu et al. | Jun 2015 | A1 |
| 20150202563 | Spartz | Jul 2015 | A1 |
| 20150241318 | Hamann et al. | Aug 2015 | A1 |
| 20150246150 | De Koster et al. | Sep 2015 | A1 |
| 20150256355 | Pera et al. | Sep 2015 | A1 |
| 20150285524 | Saunders | Oct 2015 | A1 |
| 20150285755 | Moss et al. | Oct 2015 | A1 |
| 20150289802 | Thomas et al. | Oct 2015 | A1 |
| 20150298043 | Meirav et al. | Oct 2015 | A1 |
| 20150301513 | Sager et al. | Oct 2015 | A1 |
| 20150306271 | Willette | Oct 2015 | A1 |
| 20150323206 | Chan et al. | Nov 2015 | A1 |
| 20150323427 | Sharp | Nov 2015 | A1 |
| 20150330650 | Abiprojo et al. | Nov 2015 | A1 |
| 20150330817 | Law et al. | Nov 2015 | A1 |
| 20150330861 | Alsaleem | Nov 2015 | A1 |
| 20150335834 | Anandhakrishnan | Nov 2015 | A1 |
| 20150347910 | Fadell et al. | Dec 2015 | A1 |
| 20150348400 | Zribi et al. | Dec 2015 | A1 |
| 20150354848 | Abel et al. | Dec 2015 | A1 |
| 20150369503 | Flaherty et al. | Dec 2015 | A1 |
| 20150369507 | Flaherty et al. | Dec 2015 | A1 |
| 20150370986 | Hayward | Dec 2015 | A1 |
| 20150375187 | Yates et al. | Dec 2015 | A1 |
| 20160015277 | Dumoulin et al. | Jan 2016 | A1 |
| 20160015278 | Campo et al. | Jan 2016 | A1 |
| 20160015314 | Dusanter et al. | Jan 2016 | A1 |
| 20160015315 | Auphan et al. | Jan 2016 | A1 |
| 20160026201 | Vellanki et al. | Jan 2016 | A1 |
| 20160029805 | Arens et al. | Feb 2016 | A1 |
| 20160041074 | Pliskin | Feb 2016 | A1 |
| 20160048143 | Chan et al. | Feb 2016 | A1 |
| 20160054023 | Baker et al. | Feb 2016 | A1 |
| 20160061472 | Lee et al. | Mar 2016 | A1 |
| 20160061794 | Schultz et al. | Mar 2016 | A1 |
| 20160078751 | Sloo et al. | Mar 2016 | A1 |
| 20160088438 | O'Keeffe | Mar 2016 | A1 |
| 20160089089 | Kakkar et al. | Mar 2016 | A1 |
| 20160091216 | Tran et al. | Mar 2016 | A1 |
| 20160107114 | Fu et al. | Apr 2016 | A1 |
| 20160110782 | Tadajewski | Apr 2016 | A1 |
| 20160116181 | Aultman et al. | Apr 2016 | A1 |
| 20160125714 | Kates et al. | May 2016 | A1 |
| 20160132031 | Kozura et al. | May 2016 | A1 |
| 20160133108 | Bucsa et al. | May 2016 | A1 |
| 20160139038 | Oldsen et al. | May 2016 | A1 |
| 20160147506 | Britt et al. | May 2016 | A1 |
| 20160153674 | Lancaster | Jun 2016 | A1 |
| 20160153884 | Han et al. | Jun 2016 | A1 |
| 20160161137 | Chen et al. | Jun 2016 | A1 |
| 20160169544 | Fischer et al. | Jun 2016 | A1 |
| 20160169545 | Mangsuli et al. | Jun 2016 | A1 |
| 20160178586 | Stark | Jun 2016 | A1 |
| 20160209065 | Hagstrom et al. | Jul 2016 | A1 |
| 20160209070 | Hrejsa et al. | Jul 2016 | A1 |
| 20160209316 | Buseyne et al. | Jul 2016 | A1 |
| 20160228809 | Meirav et al. | Aug 2016 | A1 |
| 20160228811 | Meirav et al. | Aug 2016 | A1 |
| 20160231014 | Ro et al. | Aug 2016 | A1 |
| 20160238527 | Tseng et al. | Aug 2016 | A1 |
| 20160245784 | Matocha et al. | Aug 2016 | A1 |
| 20160256590 | Taghipour | Sep 2016 | A1 |
| 20160263263 | Robert | Sep 2016 | A1 |
| 20160263268 | Kirschman | Sep 2016 | A1 |
| 20160292781 | Nahmad et al. | Oct 2016 | A1 |
| 20160313290 | Forzani et al. | Oct 2016 | A1 |
| 20160332170 | Wennerstrom | Nov 2016 | A1 |
| 20160334121 | Oobayashi | Nov 2016 | A1 |
| 20160348938 | Simon et al. | Dec 2016 | A1 |
| 20160356511 | Messinger et al. | Dec 2016 | A1 |
| 20160363332 | Blackley | Dec 2016 | A1 |
| 20160363339 | Blackley | Dec 2016 | A1 |
| 20160370021 | Wiley et al. | Dec 2016 | A1 |
| 20160370029 | Kurelowech | Dec 2016 | A1 |
| 20160377305 | Kwa | Dec 2016 | A1 |
| 20170007954 | Ehdaie | Jan 2017 | A1 |
| 20170010006 | Kim et al. | Jan 2017 | A1 |
| 20170021298 | Williams et al. | Jan 2017 | A1 |
| 20170080373 | Engelhard | Mar 2017 | A1 |
| 20170089810 | Novaro | Mar 2017 | A1 |
| 20170095762 | Wolowicz | Apr 2017 | A1 |
| 20170097165 | Yasuda et al. | Apr 2017 | A1 |
| 20170098230 | Orangkhadivi | Apr 2017 | A1 |
| 20170108231 | Hasegawa et al. | Apr 2017 | A1 |
| 20170130981 | Willette et al. | May 2017 | A1 |
| 20170159964 | Arai et al. | Jun 2017 | A1 |
| 20170167743 | Dempsey et al. | Jun 2017 | A1 |
| 20170189844 | McLeod et al. | Jul 2017 | A1 |
| 20170193788 | Kim et al. | Jul 2017 | A1 |
| 20170193792 | Bermudez Rodriguez et al. | Jul 2017 | A1 |
| 20170234570 | Livchak et al. | Aug 2017 | A1 |
| 20170248332 | Wright et al. | Aug 2017 | A1 |
| 20170268797 | Mowris et al. | Sep 2017 | A1 |
| 20170273256 | Hutzel | Sep 2017 | A1 |
| 20170273845 | Phillips et al. | Sep 2017 | A1 |
| 20170292432 | Hall et al. | Oct 2017 | A1 |
| 20170314812 | Hurley | Nov 2017 | A1 |
| 20170323550 | Patil et al. | Nov 2017 | A1 |
| 20170328591 | Kelly et al. | Nov 2017 | A1 |
| 20170333838 | Bender et al. | Nov 2017 | A1 |
| 20170341001 | Jousma et al. | Nov 2017 | A1 |
| 20170341002 | Cama et al. | Nov 2017 | A1 |
| 20170343227 | Mowris | Nov 2017 | A1 |
| 20170347499 | Ross et al. | Nov 2017 | A1 |
| 20170350610 | Michielsen et al. | Dec 2017 | A1 |
| 20170350611 | Su et al. | Dec 2017 | A1 |
| 20170356670 | Zhang et al. | Dec 2017 | A1 |
| 20170368488 | Wall | Dec 2017 | A1 |
| 20180001249 | Sher | Jan 2018 | A1 |
| 20180017275 | Merrill | Jan 2018 | A1 |
| 20180017278 | Klein et al. | Jan 2018 | A1 |
| 20180017513 | Le Neel et al. | Jan 2018 | A1 |
| 20180017536 | Le Neel et al. | Jan 2018 | A1 |
| 20180021613 | Li | Jan 2018 | A1 |
| 20180023831 | Ha et al. | Jan 2018 | A1 |
| 20180023834 | Hatch et al. | Jan 2018 | A1 |
| 20180050302 | Kamiyama et al. | Feb 2018 | A1 |
| 20180073759 | Zhang et al. | Mar 2018 | A1 |
| 20180119974 | Kotake et al. | May 2018 | A1 |
| 20180135877 | Seiler | May 2018 | A1 |
| 20180148180 | Fagundes et al. | May 2018 | A1 |
| 20190023099 | Li et al. | Jan 2019 | A1 |
| 20210041119 | Pham et al. | Feb 2021 | A1 |
| 20230070313 | Douglas et al. | Mar 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 102019120 | Apr 2011 | CN |
| 102353751 | Feb 2012 | CN |
| 102393882 | Mar 2012 | CN |
| 202792383 | Mar 2013 | CN |
| 203090662 | Jul 2013 | CN |
| 104089361 | Oct 2014 | CN |
| 203949322 | Nov 2014 | CN |
| 104359815 | Feb 2015 | CN |
| 104534617 | Apr 2015 | CN |
| 103958976 | Nov 2016 | CN |
| 106196506 | Dec 2016 | CN |
| 107676931 | Feb 2018 | CN |
| 107940682 | Apr 2018 | CN |
| 10108274 | Sep 2002 | DE |
| 0893657 | Jan 1999 | EP |
| 1402935 | Mar 2004 | EP |
| 1904905 | Apr 2008 | EP |
| 2450640 | May 2012 | EP |
| 2134556 | Jul 2012 | EP |
| 2368616 | Dec 2012 | EP |
| 2564114 | Mar 2013 | EP |
| 2713159 | Apr 2014 | EP |
| 2891019 | Jul 2015 | EP |
| 2937961 | Oct 2015 | EP |
| 3040948 | Jul 2016 | EP |
| 3073883 | Oct 2016 | EP |
| 3121524 | Jan 2017 | EP |
| H05180487 | Jul 1993 | JP |
| 09-280640 | Oct 1997 | JP |
| 2007083106 | Apr 2007 | JP |
| 5231476 | Jul 2013 | JP |
| 2014208343 | Nov 2014 | JP |
| 2015152175 | Aug 2015 | JP |
| 100355352 | Sep 2002 | KR |
| 20030016787 | Mar 2003 | KR |
| 20040061677 | Jul 2004 | KR |
| 100509332 | Aug 2005 | KR |
| 20050120911 | Dec 2005 | KR |
| 20070072787 | Jul 2007 | KR |
| 100819077 | Apr 2008 | KR |
| 100930346 | Dec 2009 | KR |
| 20100089605 | Aug 2010 | KR |
| 20110074222 | Jun 2011 | KR |
| 20110093329 | Aug 2011 | KR |
| 101199180 | Nov 2012 | KR |
| 101566592 | Nov 2015 | KR |
| 101765454 | Aug 2017 | KR |
| 101771053 | Aug 2017 | KR |
| 20170122043 | Nov 2017 | KR |
| 20180007381 | Jan 2018 | KR |
| 92350 | Jul 2015 | LU |
| WO-9409324 | Apr 1994 | WO |
| WO-2005110580 | Nov 2005 | WO |
| WO-2013163612 | Oct 2013 | WO |
| WO-2015078672 | Jun 2015 | WO |
| WO-2016102337 | Jun 2016 | WO |
| WO-2016139544 | Sep 2016 | WO |
| WO-2017146637 | Aug 2017 | WO |
| Entry |
|---|
| “Clean Your Air with Keen Home Smart Filters”, Keen Home, Inc., <https://keenhome.io/pages/smart-filter> 2018. |
| “Home Comfort: Digital, App-Based Climate Control”, Ecovent Systems Inc., <https://www.ecoventsystems.com/> 2018. |
| “Meet the Keen Home Zoning System—How It Works”, Keen Home, Inc., <https://keenhome.io/pages/how-it-works> 2018. |
| Doty, Steve, et al., “Building Operations: Balancing Energy Efficiency with Indoor Air Quality”, 2009. |
| El Mankibi, Mohamed, “Indoor air quality control in case of scheduled or intermittent occupancy based building: Development of a scale model”, 2009. |
| Emmerich, Steven, et al., “Indoor air quality impacts of residential HVAC systems, phase 1 report: Computer simulation plan”, NISTIR 5346: Building and Fire Research Laboratory; National Institute of Standards and Technology: http://www.researchgate.net/profile/Steven_Emmerich/publication/236454476_Indoor_air_quality_impacts_of_residential_HVAC_systems_phase_1_report_Computer_simulation_plan/links/565f5f2308ae1ef929854780.pdf; Feb. 1994; 108 Pages. |
| Footbot; Product Specifications; www.footbot.io. Accessed Sep. 13, 2017. |
| Herberger, Simone, et al., “Indoor Air Quality Monitoring Improving Air Quality Perception”, 2012. |
| International Search Report of the ISA/KR regarding International Application No. PCT/US2018/062190 dated Mar. 21, 2019. |
| Shaw, C. Y., “Maintaining acceptable air quality in office buildings through ventilation”, Construction Technology Updated No. 3, Institute for Research in Construction, National Research Council of Canada, Jan. 1997; 4 Pages. |
| Turner, William J.N., et al., “Energy and IAQ implications of residential ventilation cooling”, ResearchGate: http://www.researchgate.net/profile/William_Turner10/publication/278961832_Energy_and_IAQ_implications_of_residential_ventilation_cooling/links/5587e12608aef58c03a06547.pdf, Aug. 2014; 52 pages. |
| Written Opinion of the ISA/KR regarding International Application No. PCT/US2018/062190 dated Mar. 21, 2019. |
| Zhong, Lexuan, et al., “Ozonation Air Purification Technology in HVAC Applications”, Concordia University: http://www.researchgate.net/profile/Lexuan_Zhong/publication/260363850_Ozonation_Air_Purification_Technology_in_HVAC_Applications/links/0a85e530e28d98ecf4000000, 2014; 8 Pages. |
| Non-Final Office Action regarding U.S. Appl. No. 17/078,031 dated Oct. 20, 2021. |
| U.S. Appl. No. 17/078,031, filed Oct. 22, 2020, Stuart K. Morgan. |
| U.S. Appl. No. 17/048,866, filed Oct. 19, 202, Hung M. Pham. |
| U.S. Appl. No. 17/048,910, filed Oct. 19, 2020, Hung M. Pham. |
| Non-Final Office Action for U.S. Appl. No. 17/048,866 dated Jul. 20, 2023. |
| Non-Final Office Action for U.S. Appl. No. 17/048,910 dated Jul. 27, 2023. |
| Notice of Allowance regarding U.S. Appl. No. 17/078,031 dated Feb. 22, 2022. |
| International Search Report of the ISA/KR regarding International Application No. PCT/US2019/028398 dated Aug. 6, 2019. |
| International Search Report of the ISA/KR regarding International Application No. PCT/US2019/028400 dated Aug. 9, 2019. |
| International Search Report of the ISA/KR regarding International Application No. PCT/US2019/028409 dated Aug. 9, 2019. |
| Written Opinion of the ISA/KR regarding International Application No. PCT/US2019/028398 dated Aug. 6, 2019. |
| Written Opinion of the ISA/KR regarding International Application No. PCT/US2019/028400 dated Aug. 9, 2019. |
| Written Opinion of the ISA/KR regarding International Application No. PCT/US2019/028409 dated Aug. 9, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20210239345 A1 | Aug 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62664040 | Apr 2018 | US | |
| 62660905 | Apr 2018 | US |
