Systems and Methods for Air Handler Systems with a Backwards Curved Centrifugal Fan or Mixed Flow Fan

TECHNICAL FIELD

The present disclosure is generally in the field of air handlers and fan coil units. For example, systems and methods are provided herein for air handlers with backwards curved centrifugal and mixed flow fans.

BACKGROUND

Air handlers and heat pump systems heat and/or cool air for residential and/or commercial structures. Air handlers for residential purposes may be positioned in an attic area or utility closet, for example, and may include one or more heating and/or or cooling systems. For example, air handlers may include a heat exchanger including a plurality of coils designed to receive a fluid such a refrigerant that may be heated and may be circulated through the coils to heat air within an air handler. The coils may be connected to a heat pump system such that condenser coils may be positioned within the air handler and evaporator coils may be positioned elsewhere, or vice versa. The air handler may include other heat pump components such as an expansion valve.

As the condenser coils may be limited in their ability to heat surrounding air, an electric or hydronic heating system may be added to the air handler. For example, resistive coils may be positioned within the air handler together with the condenser coils. Alternatively, the air handler may only include the electric heating system. Alternatively, or additionally, the air handler may include hydronic heating coils configured to circulate heated water for heat exchange (e.g., with airflow). To distribute the conditioned air throughout the structure, a fan such as blower is typically positioned near an outlet of the air handler. However blowers such as forward curved centrifugal fans that are commonly used with air handlers include motor and control components positioned within the airflow path of the air handler, obstructing the airflow and reducing the efficiency of the air handler. For example, many applications include a forward curved blower with a motor mounted at the inlet of the blower, severely obstructing airflow into the blower.

Accordingly, there is a need for improved methods and systems for distributing conditioned (e.g., heated or cooled air) out of the air handler and throughout a building or structure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an air handler system within a residential structure in communication with remote computing devices and a remote server in accordance with one or more example embodiments of the disclosure.

FIGS. 2A-2B are exploded and perspective views of a fan assembly including a backwards curved centrifugal fan in accordance with one or more example embodiments of the disclosure.

FIG. 3 is a cross-sectional view a fan assembly including a backwards curved centrifugal fan in accordance with one or more example embodiments of the disclosure.

FIGS. 4A and 4B are exploded and perspective views of a fan assembly including a mixed flow fan in accordance with one or more example embodiments of the disclosure.

FIG. 5 is a cross-sectional view a fan assembly including a mixed flow fan in accordance with one or more example embodiments of the disclosure.

FIG. 6 is a schematic block diagram of a controller of air handler system in accordance with one or more example embodiments of the disclosure.

DETAILED DESCRIPTION

Improved air handler systems have been developed which include a backwards curved centrifugal fan or mixed flow fan for directing air through an air handler system. The fan may redirect airflow around a backside of the fan. A motor of the fan may be positioned on the backside of the fan. Additionally, a controller and/or control circuitry and hardware may be positioned on the backside of the fan. An enclosure may house the motor, controller and/or any control circuity and hardware. It is understood that the air handler systems described herein may be fan coil systems.

The fan may redirect the airflow around the backside of the fan such that there is little to no airflow on the backside of the fan. The air handler system may further include a heat exchanger including coils for exchanging thermal energy with the air moving through the air handler and/or an electrical heating system including one or more resistive heating elements and/or a hydronic heating coils. The heat exchanger coils may be in communication with a heat pump system including a second set of heat exchanger coils, a compressor and/or an expansion valve.

Referring now to FIG. 1, an air handler including a fan is illustrated. As shown in FIG. 1, air handler system 100 may include air handler 102, which may be positioned within or on a structure (e.g., structure 104), such as a residential structure or alternatively a commercial structure. In the example illustrated in FIG. 1, air handler 102 is installed in an attic area of structure 104. Air handler system 100 may be controlled by controller 105 and may include further remote controller 108, remote controller 112 and/or remote server 106. Controller 105 may be any type of computing device with a processor. Remote controller 108, remote controller 112 and/or remote server 106 may be in communication with controller 105.

Controller 128 may control fan assembly 135 and similarly may be any type of computing device with a processor. Controller 128 may be in communication with controller 105 via a wired or wireless connection. Remote controller 108 and/or remote controller 112 may be any type of computing device with a processor. For example, remote controller 108 and/or remote controller 112 may be tablet, laptop, desktop computer, smart phone or the like. In one example, remote controller 108 may be a wall mounted touch screen device and/or remote controller 112 may be a smartphone.

User 110 may use remote controller 108 and/or remote controller 112 to communicate with controller 105 of air handler system 100 and/or to control air handler system 100. For example, user 110 may communicate a desired temperature (e.g., 73 degrees) for interior space 115 of structure 104. It is understood that air handler system 100 may include fewer components than those shown in FIG. 1. For example, air handler system 100 may only include one of remote controller 108 and remote controller 112.

Remote controller 108 and/or remote controller 112 may communicate directly with controller 105 and/or may communicate with controller 105 via remote server 106. For example, controller 105 may communicate with remote controller 108 and/or remote controller 112 via any well-known wired or wireless system (e.g., Bluetooth, Bluetooth Low Energy (BLE), near field communication protocol, Wi-Fi, cellular network, etc.) and/or controller 105 may communicate with remote server 106 via any well-known wireless system (e.g., cellular, Internet, satellite, etc.). Controller 105 may communicate with controller 128, which may communicate with motor 124 via a wired or wireless connection. Controller 105 may send operational instructions to controller 128.

As shown in FIG. 1, air handler 102 may include housing 125 which may be generally rectangular in shape or may be any another shape. Housing 125 may include inlet 114 at one end and outlet 136 at an opposite end. Housing 125 may define air channel 127, which may be positioned within an interior of housing 125 between inlet 114 and outlet 136. Housing 125 may guide air from inlet 114, through housing 125 and ultimately out outlet 136. Inlet 114 and/or outlet 136 may be connected to ducting throughout structure 104 or alternatively a commercial structure.

Air handler 102 may include fan assembly 135, which may be positioned within housing 125 and may be secured to housing 125 such that fan assembly 135 is positioned within air channel 127. Fan assembly 135 may include fan 118 and motor 124 and optionally may include controller 128 and/or fan enclosure 126. While controller 128 may be positioned within fan enclosure 126 as shown in FIG. 1, it is understood that controller 128 may be positioned at location 134 or location 142, may be positioned together with controller 105 and/or incorporated into controller 105, and/or may be positioned at any other location within or outside of housing 125.

Motor 124 may be any well-known type of electric motor configured to power and move the fan blades of fan 118. For example, motor 124 may include metallic coils and/or windings and magnets for causing rotation of the fan blades in response to an electric current. Controller 128 may control fan assembly 135 and may optionally control other components of air handler system 100 such as electric heating system 130. Alternatively, heat exchanger coils 116 and/or electric heating system 130 may include separate controllers that may be disposed within or on air handler 102 and may be in communication with controller 128.

Fan 118 may be any type of fan and/or impeller having fan blades that rotate about a central axis of fan 118 and airflow 120, an opening on front-side 138 and designed to output airflow 122 in a direction perpendicular or at least partially perpendicular to airflow 120. For example, airflow 120 is generally parallel to air channel 127 and may be received by fan 118 and redirected into airflow 122. The term at least partially perpendicular is used throughout to mean perpendicular to the direction of the flow of airflow 120, which is parallel to longitudinal axis 111 of housing 125, or a direction or angle between the direction of the flow of airflow 120 and a direction perpendicular to the flow of airflow 120.

As shown in FIG. 1, airflow 122 may be directed away from backside 144 of fan 118 such that backside 144 receives little to no airflow. In this manner, airflow 120 received by fan 118 is redirected around backside 144 and components positioned on backside 144 (e.g., motor 124, controller 128, and/or enclosure). Housing 125 and/or additional structure such as an airflow shroud may cause airflow 122 to be further directed towards outlet 136.

In one example, fan 118 may be a backwards curved fan having fan blades that are oriented to receive airflow 120 at front-side 138 of fan 118 and redirect the airflow perpendicularly into airflow 122. FIGS. 2A-2B illustrate the fan as a backwards curved centrifugal fan. It is understood that fan 118 may alternatively be any other centrifugal fan that redirects airflow 120 into an at least partially perpendicular direction.

In another example, centrifugal fan 118 may be a mixed flow fan and may redirect an airflow 120 at least partially perpendicularly into airflow 122. For example, mixed flow centrifugal fan may redirect airflow at an angle diagonal from airflow 120, causing airflow to move in a perpendicular direction over a length of airflow channel 127. FIGS. 4A-4B illustrate the fan as a mixed flow fan.

Air handler 102 may include one or more heat exchangers to heat and/or cool the air traveling through air handler 102. For example, air handler 102 may include heat exchanger coils 116 which may be designed to receive and recirculate a fluid, such as a refrigerant. The refrigerant may be heated or cooled and heat exchanger coils 116 may exchange thermal energy with the airflowing through air channel 127 to heat or cool the air.

In one example, air handler system 100 may further include a heat pump system including heat exchanger coils 116 as well as a second set of heat exchanger coils, a compressor, and/or an expansion valve. The second set of heat exchanger coils, the compressor, and/or the expansion valve may be located outside of housing 125. Alternatively, the second set of heat exchanger coils, the compressor, and/or the expansion valve may be located within housing 125. It is understood heat exchange coils 116 may be condenser coils and/or evaporator coils and the refrigerant may be heated or cooled via the heat pump system.

Air handler system 100 may further include electric heating system 130. Electric heating system 130 may include one or more resistive heating elements for heating airflowing through air handler 102. For example, electrical heating system 130 may include an annular shaped resistive heating element. Electric heating system 130 may supplement heating of the airflow provided by heat exchanger coils 116. Alternatively, electric heating system 130 may be the only source of heating in air handler 102.

Electric heating system 130 may be secured and/or mounted to backside 144 of fan 118. For example, electric heating system 130 may be mounted to fan enclosure 126 using an electrically and/or thermally insulating mounting structure. In one example, controller 128 may also control electric heating system 130 and/or a separate controller for controlling electric heating system 130 may be included in fan enclosure 126 and may be in communication with controller 128 and/or controller 105.

Referring now to FIGS. 2A-2B, exploded and perspective views of fan assembly 200 are illustrated. Fan assembly 200 may be the same or similar to fan assembly 135 of FIG. 1. Fan assembly 200 may include backwards curved fan 218, which may be a centrifugal backwards curved fan. Backwards curved fan 218 may include fan housing 220 which may include inlet 228 on front-side 215. Inlet 228 may be circular in shape.

Backwards curved fan 218 may include fan blades 222 which may be backwards curved. Fan blades 222 may be rotationally connected to fan housing 220 such that fan blades 222 may rotate about a central axis of fan housing 220. Alternatively, fan housing 220 may be rigidly attached to fan blades 222 and fan housing 220 may be designed to rotate together with fan blades 222. Fan assembly 200 may include backside 225. While backside 225 is illustrated with an opening in FIG. 2A, it is understood that backside 225 may be closed such that airflows through inlet 228 and out outlets 227.

Fan blades 222 are curved backwards with respect to fan housing 220 such that airflow enters inlet 228 and is redirected by fan blades 222 to move out openings 227 between fan blades. In this manner, air exiting openings 227 exits fan assembly 218 in a direction perpendicular to the direction of air entering inlet 228. It is understood that fan blades 222 may have a different shape, size, and/or structure and/or that a different number of fan blades than those shown in FIGS. 2A-2B may be used.

Fan enclosure 224 may optionally be positioned onto and secured to fan housing 225. Fan enclosure 224 may house a motor secured to backside 225 and/or a controller for controlling the motor. The motor may be designed to power backwards curved fan 218 and otherwise cause fan blades 222 to rotate. The controller may be secured to the motor or otherwise secured to backside 225 and may control the motor.

Fan enclosure 224 may be cylindrical and/or domed shaped. Alternatively, fan enclosure 224 may take any other shape such as rectangle or cone. In one example, fan enclosure 224 may be metallic. However, fan enclosure may be made of any other material such as plastic. Fan enclosure 224 may include thermal and/or electrical insulation for protecting fan enclosure 224, the motor and/or controller. Alternatively, fan assembly 200 may not include fan enclosure 224.

Fan enclosure 224 and/or backside 225 may be secured to electric heating system 226. Electric heating system 226 may include mounts 228 and resistive heating coil 230. Resistive heating coil 230 may be annular in shape and may emit thermal energy (e.g., heat) when a current is applied to resistive heating coil 230. It is understood that resistive heating coil 230 may have a different shape (e.g., cube) and/or more than resistive heating coil may be used.

Mounts 228 may secure resistive heating coil 226 to fan enclosure 224 and/or backside 225. Mounts may include thermal and/or electrical insulation to prevent damage to enclosure 224, the motor and/or controller. The motor and/or controller may receive power from an energy source in the residential structure and electric heating system 226 may receive power from the motor, controller and/or the same power source. Additionally, or alternatively, hydronic coils may be similarly secured to fan enclosure 224 (e.g., via mounts 228).

Referring now to FIG. 3, a cross-sectional view of air handler 300 is illustrated. Air handler system 300 may be the same as or similar to air hander 102 of FIG. 1. As shown in FIG. 3, air handler 300 may include fan assembly 302 and housing 304. Housing 304 may define air channel 340. It is understood that air handler 300 may further include heat exchanger coils and/or an electric heating system, not shown in FIG. 3.

Fan assembly 302 may include fan 306 which may be any known backwards curved fan having backwards curved blades 308 which are designed to rotate about a central axis of fan 306. Fan assembly 302 and fan 306 may be the same or similar to fan assembly 235 and fan 218 of FIGS. 2A-2B. Alternatively, fan 306 may be any known backwards curved centrifugal fan.

Fan assembly 306 may further include motor 310, which may power fan 306 and cause fan blades 308 rotate at one or more speeds. For example, motor 310 may be any type of well-known electric motor and may include metallic (e.g., copper) coils and/or windings and may further include magnetic components 312. Motor 310 may include a driveline that is connected to fan blades 308 and causes fan blades 308 to rotate.

Motor 310 may be secured to backside 309 of fan 306 via any well-known technique (e.g., welding, adhesive, threaded connection). Motor 310 may be powered via a wired connection to an external power source (e.g., standard power outlet). Controller 318 may optionally be secured to motor 310 and/or backside 309 via any well-known technique. Controller 318 may be the same as or similar to controller 128 of FIG. 1. Controller 318 may control operation of motor 310 and/or control operation of other systems or components of air handler system 300 (e.g., electrical heating system). Controller 318 may be wired to the same power source as motor 310. It is understood that controller 318 may be positioned elsewhere in or on air handler 304.

Circuitry and/or hardware for motor 306 and/or controller 302 may similarly be housed in optional compartment 320 and/or optional compartment 322. In another example, circuitry, hardware, and/or a controller for an electric heating system may be housed by optional compartments 320 and/or 322. It is understood that greater or fewer compartments may be positioned on backside 309.

Enclosure 316 may optionally be positioned over motor 310, controller 318, and/or compartments 320 and/or 322. Enclosure 316 may be cylindrical and/or domed shaped or may be any other shape. Enclosure 302 may be metallic or may be made from any other material (e.g., rigid plastic). Enclosure 316 may protect motor 310, controller 318, and/or compartments 320 and/or 322. For example, enclosure 316 may include thermal insulation 317 on an interior of enclosure 316.

Thermal insulation 317 may be reflective thermal insulation or any other known insulation. Enclosure 316 may additionally, or alternatively, include any other known thermal and/or electrical insulation to prevent damage to controller 318, motor 310, and/or fan 306 by heat from the electric heating system and/or heat exchanger coils. Motor 312 and/or controller 318 may additionally or alternatively include thermal and/or electrical insulating materials.

As shown in FIG. 3, fan assembly 302 may be supported by airflow shroud 330. Airflow shroud 330 may extend from air handler 304 and may be curved towards the exit of air handler 304 to cause air exiting the fan blades 308 of fan 306 to be guided towards the outlet of air handler 304. Airflow shroud 330 may optionally connect to compartment 307 which may be positioned between airflow shroud 330 and fan 306. Compartment 307 may be a housing or compartment which may house and/or include components such as a control board (e.g., for controlling fan and/or components in enclosure 316), a transformer (e.g., low voltage transformer), a thermal block (e.g., for connecting a thermostat to air handler), a protection plate which may be made of material to protect against electrical shock and/or may be heat resistant, and/or any other suitable components for operating air handler 304. In one example, compartment 307 and/or the protection plate may be made of and/or include a dampening material to reduce vibration transferred between fan 306 and airflow shroud 330. Alternatively, or additionally, a dampening structure such as a grommet (e.g., rubber grommet) may be positioned between airflow shroud 330 and compartment 307 (e.g., between airflow shroud 330 and the protection plate). The protection plate may optionally be formed into a base and/or cover of compartment 307 or may be a standalone component of compartment 307. Compartment 307 may include a central void such that airflow can flow through compartment 307 to fan 306.

For example, airflow 350 may enter fan 306 through an inlet positioned at front-side 335 of fan 306. Fan 306 may cause, via fan blades 308, airflow 350 to be redirected out of outlet 342 between fan blades 308 in a direction perpendicular to the direction of airflow 350.

Airflow 360 may exit outlet 342 between fan blades 308 and may be guided by airflow shroud 330 to move toward the outlet of air handler 304. For example, as shown in FIG. 3, airflow 360 may be guided from a horizontal orientation to a vertical orientation by outflow shroud 330. Outflow shroud may further provide structural support to fan assembly 302 and/or may be used to deliver a power supply connection between air handler 304 and fan assembly 302.

Referring now to FIGS. 4A-4B, exploded and perspective views of fan assembly 400 are illustrated. Fan assembly 400 may be the same or similar to fan assembly 135 of FIG. 1. Fan assembly 400 may include fan 418, which may be a mixed flow fan. Fan 418 may include fan housing 420 which may include inlet 428 on front-side 415. Inlet 428 may be circular in shape. Mixed flow fan 418 may include fan blades 422.

Fan housing 420 may be rotationally attached to fan blades 422 such that fan blades 422 may rotate about a central axis of fan housing 420. Alternatively, fan housing 420 may be designed to rotate together with fan blades 422. Fan assembly 400 may include backside 425. While backside 425 is illustrated with an opening in FIG. 4A, it is understood that backside 425 will be closed such that air enters inlet 428 and exits outlet 427.

Fan blades 422 are both angled and positioned forward with respect to fan housing 420 such that airflow enters inlet 428 and is redirected by fan blades 422 to exit openings 427 in an angled direction at least partially perpendicular to the direction at which the airflow entered inlet 428. It is understood that fan blades 422 may have a different shape, size, or structure and/or that a different number of fan blades than those shown in FIGS. 4A-4B may be used.

Fan enclosure 424 may optionally be positioned onto and secured to fan housing 425. Fan enclosure 424 may house a motor secured to backside 425 and/or a controller for controlling the motor. The motor may be designed to control fan 418 and otherwise cause fan blades 422 to rotate. The controller may be secured to the motor or otherwise secured to backside 425. Fan enclosure 424 may be the same as or similar to fan enclosure 224 of FIG. 2.

Fan enclosure 424 and/or backside 425 may be secured to electric heating system 426. Electric heating system 426 may include mounts 428 and resistive heating coil 430. Electric heating system 426, mounts 428 and/or resistive heating coil 430 may be the same as or similar to electric heating system 226, mounts 228, and/or resistive heating coil 430 of FIGS. 2A-2B. Additionally, or alternatively, hydronic coils may be similarly secured to fan enclosure 424 (e.g., via mounts 428).

Referring now to FIG. 5, a cross-sectional view of air handler 500 is illustrated. Air handler 500 may be the same as or similar to air hander 502 of FIG. 1. As shown in FIG. 5, air handler 500 may include fan assembly 502 and housing 504. Housing 504 may define air channel 540. It is understood that air handler 500 may further include heat exchanger coils and/or an electric heating system, not shown in FIG. 5.

Fan assembly 502 may include fan 506 which may be any mixed flow fan having angled blades 508 which, similar to a centrifugal fan, are designed to rotate about a central axis of fan 506. However, fan 506 may create airflow 560 which is angled with respect to airflow 550 entering fan 506, such that airflow 560 moves in a manner at least partially perpendicular to airflow 550 as the air moves along housing 504. Fan assembly 502 and fan 506 may be the same or similar to fan assembly 400 and centrifugal fan 418 of FIGS. 4A-4B.

Fan assembly 506 may further include motor 510, which may power fan 506 and specifically fan blades 508. For example, motor 510 may be the same as or similar to motor 310 of FIG. 3. Motor 310 may be secured to backside 509 of fan 506 via any known technique (e.g., welding, adhesive, threaded connection). Motor 510 may be powered via a wired connection to an external power source. Controller 518 may optionally be secured to motor 510 and/or backside 509 via any known technique. Controller 518 may be the same as or similar to controller 318 of FIG. 3.

Circuitry and/or hardware for motor 506 and/or controller 502 may similarly be housed in optional compartment 520 and/or optional compartment 522. In another example, circuitry, hardware, and/or a controller for an electric heating system may be housed by optional compartments 520 and/or 522. It is understood that greater or fewer compartments may be positioned on backside 509.

Enclosure 516 may optionally be positioned over motor 510, controller 518, and/or compartments 520 and/or 522. Enclosure 516 may be the same as or similar to enclosure 316 of FIG. 3. Fan assembly 502 may be supported by support structure 530, which may extend from housing 504 and may be secured to fan assembly 502. Support structure 530 may be used to deliver a power supply connection between air handler 504 and fan assembly 502. Alternatively, fan assembly 502 may include and be secured by an airflow shroud. In one example, support structure 530 may optionally be connected to compartment 507 and compartment 507 may connect support structure 530 to fan 506. Compartment 507 may be the same as or similar to compartment 307.

Referring now to FIG. 6 a schematic block diagram of an illustrative controller of an air handler system with a backwards curved centrifugal or mixed flow fan is illustrated. Specifically controller 600 may be incorporated into an air handler in accordance with one or more example embodiments of the disclosure. Controller 600 may be the same or similar to controller 105 of FIG. 1 or otherwise may be one or more of the controllers of FIGS. 1-5.

Controller 600 may be configured to communicate with a controller of the centrifugal or mixed flow fan, one or more remote controllers, servers, mobile devices, user devices, other systems, or the like. Controller 600 may be configured to communicate via one or more networks. Such network(s) may include, but are not limited to, any one or more different types of communications networks such as, for example, cable networks, public networks (e.g., the Internet), private networks (e.g., frame-relay networks), wireless networks, cellular networks, telephone networks (e.g., a public switched telephone network), or any other suitable private or public packet-switched or circuit-switched networks.

In an illustrative configuration, controller 600 may include one or more processors 602, one or more memory devices 604 (also referred to herein as memory 604), one or more input/output (I/O) interface(s) 606, one or more network interface(s) 608, one or more transceiver(s) 612, one or more antenna(s) 634, and data storage 620. The controller 600 may further include one or more bus(es) 618 that functionally couple various components of the controller 600.

The bus(es) 618 may include at least one of a system bus, a memory bus, an address bus, or a message bus, and may permit exchange of information (e.g., data (including computer-executable code), signaling, etc.) between various components of the controller 600. The bus(es) 618 may include, without limitation, a memory bus or a memory controller, a peripheral bus, an accelerated graphics port, and so forth. The bus(es) 618 may be associated with any suitable bus architecture including.

The memory 604 may include volatile memory (memory that maintains its state when supplied with power) such as random access memory (RAM) and/or non-volatile memory (memory that maintains its state even when not supplied with power) such as read-only memory (ROM), flash memory, ferroelectric RAM (FRAM), and so forth. Persistent data storage, as that term is used herein, may include non-volatile memory. In various implementations, the memory 604 may include multiple different types of memory such as various types of static random access memory (SRAM), various types of dynamic random access memory (DRAM), various types of unalterable ROM, and/or writeable variants of ROM such as electrically erasable programmable read-only memory (EEPROM), flash memory, and so forth.

The data storage 620 may include removable storage and/or non-removable storage including, but not limited to, magnetic storage, optical disk storage, and/or tape storage. The data storage 620 may provide non-volatile storage of computer-executable instructions and other data. The memory 604 and the data storage 620, removable and/or non-removable, are examples of computer-readable storage media (CRSM) as that term is used herein. The data storage 620 may store computer-executable code, instructions, or the like that may be loadable into the memory 604 and executable by the processor(s) 602 to cause the processor(s) 602 to perform or initiate various operations. The data storage 620 may additionally store data that may be copied to memory 604 for use by the processor(s) 602 during the execution of the computer-executable instructions. Moreover, output data generated as a result of execution of the computer-executable instructions by the processor(s) 602 may be stored initially in memory 604, and may ultimately be copied to data storage 620 for non-volatile storage.

The data storage 620 may store one or more operating systems (O/S) 622; one or more optional database management systems (DBMS) 624; and one or more program module(s), applications, engines, computer-executable code, scripts, or the like such as, for example, one or more implementation modules 626, temperature control modules 627, operational control modules 629, and one or more communication modules 628. Some or all of these modules may be sub-modules. Any of the components depicted as being stored in data storage 620 may include any combination of software, firmware, and/or hardware. The software and/or firmware may include computer-executable code, instructions, or the like that may be loaded into the memory 604 for execution by one or more of the processor(s) 602. Any of the components depicted as being stored in data storage 620 may support functionality described in reference to correspondingly named components earlier in this disclosure.

Referring now to other illustrative components depicted as being stored in the data storage 620, the O/S 622 may be loaded from the data storage 620 into the memory 604 and may provide an interface between other application software executing on the controller 600 and hardware resources of the controller 600. More specifically, the O/S 622 may include a set of computer-executable instructions for managing hardware resources of the controller 600 and for providing common services to other application programs (e.g., managing memory allocation among various application programs). In certain example embodiments, the O/S 622 may control execution of the other program module(s) to for content rendering. The O/S 622 may include any operating system now known or which may be developed in the future including, but not limited to, any server operating system, any mainframe operating system, or any other proprietary or non-proprietary operating system.

The optional DBMS 624 may be loaded into the memory 604 and may support functionality for accessing, retrieving, storing, and/or manipulating data stored in the memory 604 and/or data stored in the data storage 620. The DBMS 624 may use any of a variety of database models (e.g., relational model, object model, etc.) and may support any of a variety of query languages. The DBMS 624 may access data represented in one or more data schemas and stored in any suitable data repository including, but not limited to, databases (e.g., relational, object-oriented, etc.), file systems, flat files, distributed datastores in which data is stored on more than one node of a computer network, peer-to-peer network datastores, or the like.

The optional I/O interface(s) 606 may facilitate the receipt of input information by the controller 600 from one or more I/O devices as well as the output of information from the controller 600 to the one or more I/O devices. The I/O devices may include any of a variety of components such as a display or display screen having a touch surface or touchscreen; an audio output device for producing sound, such as a speaker; an audio capture device, such as a microphone; an image and/or video capture device, such as a camera; and so forth. Any of these components may be integrated into the controller 600 or may be separate.

The controller 600 may further include one or more network interface(s) 608 via which the controller 600 may communicate with any of a variety of other systems, platforms, networks, devices, and so forth. The network interface(s) 608 may enable communication, for example, with one or more wireless routers, one or more host servers, one or more web servers, and the like via one or more of networks.

The antenna(s) 634 may include any suitable type of antenna depending, for example, on the communications protocols used to transmit or receive signals via the antenna(s) 634. Non-limiting examples of suitable antennas may include directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, or the like. The antenna(s) 634 may be communicatively coupled to one or more transceivers 612 or radio components to which or from which signals may be transmitted or received. Antenna(s) 634 may include, without limitation, a cellular antenna for transmitting or receiving signals to/from a cellular network infrastructure, an antenna for transmitting or receiving Wi-Fi signals to/from an access point (AP), a Global Navigation Satellite System (GNSS) antenna for receiving GNSS signals from a GNSS satellite, a Bluetooth antenna for transmitting or receiving Bluetooth signals including BLE signals, a Near Field Communication (NFC) antenna for transmitting or receiving NFC signals, a 900 MHz antenna, and so forth.

The transceiver(s) 612 may include any suitable radio component(s) for, in cooperation with the antenna(s) 634, transmitting or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by the controller 600 to communicate with other devices. The transceiver(s) 612 may include hardware, software, and/or firmware for modulating, transmitting, or receiving—potentially in cooperation with any of antenna(s) 634—communications signals according to any of the communications protocols discussed above including, but not limited to, one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the IEEE 802.11 standards, one or more non-Wi-Fi protocols, or one or more cellular communications protocols or standards. The transceiver(s) 612 may further include hardware, firmware, or software for receiving GNSS signals. The transceiver(s) 612 may include any known receiver and baseband suitable for communicating via the communications protocols utilized by the controller 600. The transceiver(s) 612 may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, a digital baseband, or the like.

Referring now to functionality supported by the various program module(s) depicted in FIG. 6, the implementation module(s) 626 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, overseeing coordination and interaction between one or more modules and computer executable instructions in data storage 620, determining user selected actions and tasks, determining actions associated with user interactions, determining actions associated with user input, initiating commands locally or at remote devices, and the like.

The temperature control module(s) 627 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, determining a temperature set point, managing temperature schedules, determining whether a temperature in an interior space satisfies a set point temperature.

The communication module(s) 628 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, communicating with one or more devices, for example, via wired or wireless communication, communicating with remote controllers, mobile devices, communicating with servers (e.g., remote servers), communicating with remote datastores and/or databases, sending or receiving notifications or commands/directives, communicating with cache memory data, communicating with user devices, and the like.

The temperature control module(s) 627 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to controlling and communicating with controllers to control operation of components and systems of the air handler system to achieve a desired temperature.

Although specific embodiments of the disclosure have been described, one of ordinary skill in the art will recognize that numerous other modifications and alternative embodiments are within the scope of the disclosure. For example, any of the functionality and/or processing capabilities described with respect to a particular device or component may be performed by any other device or component. Further, while various illustrative implementations and architectures have been described in accordance with embodiments of the disclosure, one of ordinary skill in the art will appreciate that numerous other modifications to the illustrative implementations and architectures described herein are also within the scope of this disclosure.

Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to example embodiments. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by execution of computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some embodiments. Further, additional components and/or operations beyond those depicted in blocks of the block and/or flow diagrams may be present in certain embodiments.

Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

Program module(s), applications, or the like disclosed herein may include one or more software components, including, for example, software objects, methods, data structures, or the like. Each such software component may include computer-executable instructions that, responsive to execution, cause at least a portion of the functionality described herein (e.g., one or more operations of the illustrative methods described herein) to be performed.

A software component may be coded in any of a variety of programming languages. An illustrative programming language may be a lower-level programming language such as an assembly language associated with a particular hardware architecture and/or operating system platform. A software component comprising assembly language instructions may require conversion into executable machine code by an assembler prior to execution by the hardware architecture and/or platform.

Another example programming language may be a higher-level programming language that may be portable across multiple architectures. A software component comprising higher-level programming language instructions may require conversion to an intermediate representation by an interpreter or a compiler prior to execution.

Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database query or search language, or a report writing language. In one or more example embodiments, a software component comprising instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form.

A software component may be stored as a file or other data storage construct. Software components of a similar type or functionally related may be stored together such as, for example, in a particular directory, folder, or library. Software components may be static (e.g., pre-established or fixed) or dynamic (e.g., created or modified at the time of execution).

Software components may invoke or be invoked by other software components through any of a wide variety of mechanisms. Invoked or invoking software components may comprise other custom-developed application software, operating system functionality (e.g., device drivers, data storage (e.g., file management) routines, other common routines, and services, etc.), or third-party software components (e.g., middleware, encryption, or other security software, database management software, file transfer or other network communication software, mathematical or statistical software, image processing software, and format translation software).

Software components associated with a particular solution or system may reside and be executed on a single platform or may be distributed across multiple platforms. The multiple platforms may be associated with more than one hardware vendor, underlying chip technology, or operating system. Furthermore, software components associated with a particular solution or system may be initially written in one or more programming languages, but may invoke software components written in another programming language.

Computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that execution of the instructions on the computer, processor, or other programmable data processing apparatus causes one or more functions or operations specified in the flow diagrams to be performed. These computer program instructions may also be stored in a CRSM that upon execution may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement one or more functions or operations specified in the flow diagrams. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process.

Additional types of CRSM that may be present in any of the devices described herein may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the information and which can be accessed. Combinations of any of the above are also included within the scope of CRSM. Alternatively, computer-readable communication media (CRCM) may include computer-readable instructions, program module(s), or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, CRSM does not include CRCM.

Although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment.

Systems and Methods for Air Handler Systems with a Backwards Curved Centrifugal Fan or Mixed Flow Fan

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATION

Provisional Applications (1)