HVAC SYSTEM WITH FAULT DETECTION AND ALERT SYSTEM

Abstract

Systems and methods utilized to create and perform an alert system in a heating, ventilation, and air conditioner (HVAC) system. One implementation includes a visual alert system to alert of a fault in the HVAC system. The system includes one or more LED lights indicating the fault and disposed on an exterior surface of a housing of the HVAC system. The system includes a programmable logic relay (PLR) having one or more relay outputs configured to activate, based on a type of the fault and according to fault/error codes, an alert notification. The alert system can operate without another device having a display for input and output, the other device displaying one or more parameters of the HVAC system. The system includes at least one of a high pressure switch, a low pressure switch, a differential air pressure switch, or an access panel switch.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application No. 63/482,380 filed Jan. 31, 2023, the entirety of which is herein incorporated by reference.

BACKGROUND

The present disclosure relates generally to the field of the heating, ventilation, and air conditioner (HVAC) systems, and more specifically to the alert systems indicating HVAC maintenance and/or repair needs. Typically, the exterior HVAC systems, for example, the wall-mount air conditioner units, communicate with a user through a secondary device or thermostat that is oftentimes located a certain distance away from the HVAC system itself. However, the user who is near the HVAC system cannot readily identify whether the HVAC system requires maintenance or repair.

SUMMARY OF THE INVENTION

The visual alert system of the present disclosure displays alerts via LED lights disposed on the exterior surface of the HVAC system (or an air conditioner) utilizing various colors and speeds of blinking to facilitate a quick indication if the air conditioner is experiencing maintenance and/or service needs without the use of a thermostat or another secondary device.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of the present disclosure is particularly pointed out and distinctly claimed in the concluding portion of the specification. A more complete understanding of the present disclosure, however, is best be obtained by referring to the detailed description and claims when considered in connection with the drawing figures, wherein like numerals denote like elements.

FIG. 1 is an illustration of a heating, ventilating and air-conditioning (HVAC) system in which a fault detection and alert system is employed to advantage.

FIG. 2 is a detail view of a portion of the fault detection and alert system.

FIG. 3 is another detail view of a portion of the fault detection and alert system.

FIG. 4 is an illustration of an embodiment of a user interface of the fault detection and alert system of FIGS. 1-3.

DETAILED DESCRIPTION

FIG. 1 illustrates a heating, ventilation and air-conditioning (HVAC) system 10 in which a fault detection and alert system 12 is employed to advantage. According to some embodiments, the HVAC system 10 includes heating, ventilating, and/or air conditioning systems, environmental management systems, and/or combinations thereof that are operable to adjust and regulate aspects (e.g., temperature, etc.) in an environment such as in a building, a home or other enclosure (for example, an electrical enclosure). In some embodiments, the fault detection and alert system 12 is used in connection with the HVAC system 10 for managing the environment of the electrical enclosure (e.g., the HVAC system 10 for cooling the electrical enclosure), however, it should be understood that the HVAC system 10 may be otherwise used for any type of enclosure. According to some embodiments, the HVAC system 10 is supported or otherwise coupled to an external wall of an enclosure for cooling the interior thereof.

The HVAC system 10 includes components such as, for example, a blower, a compressor, a fan, a control system, and other heating and cooling components, each being disposed within a housing 14. In the embodiment illustrated in FIG. 1, the housing 14 includes one or more walls/access panels: a front wall/panel 16, a rear wall/panel 18, a top wall/panel 20, a bottom wall/panel 22, and side wall/panels 24 and 26 to form and otherwise enclose an interior area for housing the components of the HVAC system 10 therein.

Referring to FIG. 1, the fault detection and alert system 12 includes a user interface 27 (or a display) disposed on the front wall 16 to alert or otherwise communicate to a user a fault/error or other conditions of the HVAC system 10. In the embodiment illustrated in FIG. 1, the user interface 27 includes one or more light emitting diodes (LEDs) disposed on the front wall 16 to illuminate in response to and/or to otherwise communicate the detection of a fault/error or other operating condition of the HVAC system 10. In FIG. 1, the user interface 27 includes a first and second sections 28 and 30 that spell the words “RUN” and “WELL”, respectively. In operation and as discussed in greater detail below, the first and second sections 28 and 30 illuminate or otherwise flash in a series of pre-coded patterns to communicate a fault/error or other conditions. In addition and/or in lieu of each word illuminating, each letter, pairs of letters, or other grouping of letters can separately illuminate to facilitate communications. In addition to illuminating patterns, each letter, word or combinations thereof can illuminate in a predetermined color and/or patterns of different colors in order to communicate the fault or other conditions. It should be understood that user interface 27 may be otherwise configured. For example, instead of letters and/or words such as RUN and WELL, numbers, shapes, or visual indicators can be used. For example, the user interface 27 or any portion of it can represent a company identifier, for example, a logo and/or a brand of the company. Further, in addition to visual indicators, sounds and such as, for example, bell sounds, tones, sirens, prerecorded audible messages and/or combinations thereof can be displayed or otherwise communicated by the user interface 27 of the fault detection and alert system 12.

Referring now to FIGS. 2 and 3, schematic diagrams of the electric and electromechanical components of the HVAC system 10 and the fault detection and alert system 12 are illustrated. According to the embodiment illustrated in FIGS. 2 and 3, the HVAC system 10 includes a capacitor 124, a contactor 122, a transformer 120, an LED power source 118, a relay block 36, a programmable logic relay (PLR) 32, and expansion module 34, each disposed within the housing 14.

In operation, the capacitor 124 stores sufficient power to start the HVAC system 10. In FIGS. 2 and 3, the capacitor 124 includes a wired connection 126 communicatively coupling the capacitor 124 to a compressor. In some embodiments, the capacitor 124 can include a wired connection 128 communicatively coupling the capacitor 124 to ground. In still other embodiments, the capacitor 124 can include a wired connection 130 communicatively coupling the capacitor 124 to an outdoor fan motor. In operation, the transformer 120 transforms or otherwise steps-down higher voltages to lower voltages that are needed for smaller and more sensitive controllers. For example, the contactor 122, a blower, a fan, and/or the capacitor, each operate in 120 and 240 volts of alternate current (AC) or in a range therebetween; for example, they can operate in 120, 140, 230, and/or 240 volts AC. The controllers, such as the PLR 32, the expansion module 34, and/or the relay block 36 operate in 24 volts AC.

In the embodiment illustrated in FIGS. 2 and 3, the contactor 122 controls the power transmission to various components of the HVAC system 10. As illustrated in FIGS. 2 and 3, the contactor 122 includes two poles: the first pole L1 and the second pole L2 (138 and 140, respectively) that communicatively and/or electrically couple the contactor 122 to an AC power source. The contactor 122 can include wired connections 132 and 134 communicatively coupling the contactor 122 to the compressor. In the illustrated embodiment, the contactor 122 includes a wired connection 136 communicatively and/or electrically coupling the contactor 122 to an outdoor fan motor.

According to some embodiments, the HVAC system 10 can be disposed on a wall, on a ground, or other support surface, or on a roof of a building. In operation and as described above, the user interface 27 illuminates or otherwise outputs a message to notify a user of a fault or other condition of the HVAC system 10. For example, routine maintenance may be required or the condition of one or more components may require repair or replacement. Using various fault/error codes described in greater detail below, the user can identify a specific fault, maintenance and/or repair item. For example, a user can be notified about the maintenance or repair issues by visual indication via the first and second sections 28 and 30 of the LED lights blinking different fault/error patterns.

In addition to first and second sections 28 and 30 of the LED lights, FIG. 2 illustrates the PLR 32 and/or one or more expansion modules 34. In some embodiments, the fault detection and alert system 12 includes the relay block 36. The first and second sections 28 and 30 of the LED lights can be communicatively coupled to the PLR 32 and the expansion module 34 and the relay block 36. The first and second sections 28 and 30 of the LED lights are communicatively coupled by a connector 146 to the connection 144 of the LED power source 118. According to some embodiments, the LED power source 118 can be a source of electrical power supplied from the wall and/or a floor electrical socket. Alternatively or optionally, the power source can be a stand-alone battery.

According to some embodiments, the first section of the LED lights 28 can have two colors: the first color LED light 38 and the second color LED light 40. The first color LED light 38 for the first section 28 can be, for example, a red color. The second color 40 of the LED lights for the first section 28 can be, for example, a blue color. The second section 30 can have two colors of LED lights: the first color LED lights 42 and the second color LED lights 44. The first color LED lights 42 can be, for example, a red color. The second color LED light 44 can be, for example, a blue color. The LED lights 38, 40, 42, and 44 are communicatively and/or electrically coupled to the PLR 32 and/or expansion modules 34.

In some embodiments, the relay block 36 can include inputs and outputs. The inputs can include, for example: a compressor input 46, a security alarm input 48, a differential pressure switch input 50, a low pressure (LP) switch input 52, a high pressure (HP) switch input 54, a condenser fan input 56, and an R thermostat input 60. The outputs of the relay block 36 can include the outputs for the LED lights one through four (e.g., 62 through 68) that are associated with the colors of the LED lights 38 through 44 of the first and second sections 28 and 30 of the LED lights, respectively.

In some embodiments, the PLR 32 and the expansion module 34 include inputs and outputs. The inputs can include, for example: future use inputs 70 and 72, a Z thermostat input, a security alarm input 76, a high pressure switch input 78, a low pressure switch input 80, a differential pressure switch input 82, a compressor input 84, a condenser fan input 86, an evaporator fan input 88, a W2 thermostat input 90, a W1 thermostat input 92, a Y2 thermostat input 94, a Y1 thermostat input 96, and a G thermostat input 98. The outputs of the PLR 32 and/or the expansion module 34 can include, for example, the outputs for a blower speeds one and two (e.g., 100 and 102, respectively), a speed selector output 104, outputs for two normally open (N/O) contacts of the relay (e.g., 106 and 108, respectively), two normally closed (N/C) contacts of the relay (e.g., 114 and 116, respectively), and two auxiliary outputs (e.g., 110 and 112, respectively).

A more detailed reference is now made to the LED power source 118, the transformer 120, the contactor 122, and the capacitor 124. The LED power source 118 provides power to the first and second sections 28 and 30 of the LED lights via the cable 144, that is connected to 146 of the first and second sections 28 and 30 of the LED lights. In the embodiment illustrated, the LED power source 118 includes a wired connection 142 to communicatively and/or electrically couple the LED power source 118 to the ground.

In some embodiments the transformer 120 is communicatively and/or electrically coupled to the relay block 36 via a connection 148 that is coupled to a relay block connection 150 as well as a connection 152 that is coupled to a relay block connection 154. In some embodiments the LED power source 118 is coupled to the relay block 36 via a connection 156 that is coupled to a relay block connection 158.

In the illustrated embodiment, the contactor 122 is coupled to the relay block 36 via the connection 160, which is connected to a relay block connection 162. In some embodiments, the contactor 122 is connected to the PLR 32 and/or the expansion module 34 via a connection 164 that is communicatively and/or electrically coupled to a connection 166 of the PLR 32 and/or the expansion module 34. In some embodiments, the capacitor 124 is electrically and/or communicatively coupled to the contactor 122. In some embodiments, the contactor 122 is communicatively and/or electrically coupled to the transformer 120. In some embodiments the contactor 122 is communicatively and/or electrically coupled to the LED power source 118.

Referring now to FIG. 4, various fault codes may be output via the user interface 27. For example, the inputs of the PLR 32 and/or the expansion module 34 determine presence of power or lack thereof. In particular, when the state of inputs change, the PLR 32 and/or expansion module 34 can control the output relays. For example, in some embodiments, the outputs of the relay block 36, such as outputs 62 through 68, can be controlled by the PLR 32 and/or expansion module 34. For instance, the output for the LED lights 38 of a first color (depicted as color pattern 176) for the first section 28 (for example, red color LED lights 38 of the “Run” section) can be controlled by the output 62 of the relay block 36. The relay output 62 sends a signal to the first color LED lights 38 of the first section 28 (for example, the red color LED lights 38 for the “Run” section) to be illuminated.

According to some embodiments, the output for the LED lights 40 of a second color (depicted as color pattern 178) for the first section 28 (for example, the blue color LED lights 40 of the “Run” section) can be controlled by the output 64 of the relay block 36. The relay output 64 sends a signal to the second color LED lights 40 of the first section 28 (for example, a blue color LED lights 40 for the “Run” section), to be illuminated.

In some embodiments, the output for the LED lights 42 of the first color for the second section 30 (for example, the red color LED lights 42 of the “Well” section) can be controlled by the output 66 of the relay block 36. The relay output 66 sends a signal to the first color LED lights 42 of the second section 30 (for example, a red color LED lights 42 for the “Well” section), to be illuminated.

In some embodiments, the output for the LED lights 44 of the second color for the second section 30 (for example, the blue color LED lights 44 of the “Well” section) can be controlled by the output 68 of the relay block 36. The relay output 68 sends a signal to the second color LED lights 44 of the second section 30 (for example, a blue color LED lights 44 for the “Well” section), to be illuminated.

In some embodiments, the PLR 32 and/or expansion module 34 can be programmed by a software assigning logic codes via, for example, a flash memory, for example, NAND, 3D NAND, NOR, 3D NOR and/or other various gates. A user can access, via a user device and/or computing systems communicatively and/or electrically coupled to a network, settings of the PLR 32 and/or expansion module 34. In some embodiments, the PLR 32 and/or expansion module 34 can have a web server embedded into them. The web server can be communicatively and/or electrically coupled to the network, which can be further electrically and/or communicatively coupled to the Internet. When the PLR 32 and/or expansion module 34 are coupled to the network, then the PLR 32 and/or expansion module 34 operations can be viewed and programmed remotely. Therefore, the PLR 32 and/or expansion module 34 can be customized and their settings changed to correspond to the preference of a user. Typically, for the alert systems that have embedded circuit boards, the customization and modification can be more time consuming and more complex than the alert system 12 utilizing the PLR 32 and/or the expansion module 34.

For example, in some embodiments, the alert system 12 facilitates a faster and more convenient observation of possible maintenance or repair needs by observing the visual and/or audio notifications issued by the fault detection and alert system 12, when a user observes the HVAC system 10 within a certain distance from the HVAC system 10 (for example, within a visibility range), because the alert system 12 is disposed at the HVAC system 10 and the exterior thereof. In some embodiments, the LED lights 38 through 44 can have LED diffusers; the LED diffusers can have an extended range of visibility.

In some embodiments, the fault code 168 represents a security or anti-theft alert. When the fault code 168 is activated, the first and second sections 28 and 30 of the LED lights can both be illuminated in a first color of the LED lights 38. For example, in a red color. During such fault notification, the first color of LED lights 38 for the first section 28 (for example, the red color LED lights) and the first color of the LED lights 42 for the second section 30 (for example, the red color LED lights) can be both activated by the PLR 32 and/or expansion module 34. Therefore, in the fault code 168, both sections 28 and 30 are illuminated in the first color of the LED lights 38 and 42, respectively, (for example, in the red color) and there can be an audio sound alerting about a potential theft or security breach. The security or anti-theft alert 168 can include the fast blinking or fast intermittent flashing of the LED lights 38 of the first color of the first section 28 of the LED lights, and the first color LED lights 42 of the second section 30 of the LED lights. Thus, during the security or anti-theft alert 168, the first color LED lights 38 of the first section of LED lights 28 and the first color LED lights 42 for the second section 30, can blink or intermittently flash.

For example, the anti-theft alarm 168 can be actuated as described hereinafter. Each panel or door to the housing 14 may include a microswitch. The microswitch has a spring-loaded plunger. All microswitches are connected in series to the PLR 32 and/or the expansion module 34. When a door is closed, for example, the plunger of the microswitch is depressed configuring the microswitch to be in a closed state. All microswitches of all doors can be communicatively and/or electrically coupled in series with one wire. If any door (or any panel having the microswitch) is opened, then the circuit of the series of the microswitches breaks and this circuit break triggers the anti-theft alarm 168.

An alert or fault 170 for high pressure can have both the first section of LED lights 28, and the second section 30 of LED lights in the first color (for example, in red). For example, the first color LED lights 38 of the first section 28, and the first color of LED lights 42 for the second section 30, can be in red color. For example, the alert 170 for high pressure can blink or intermittent flash in a slow speed or frequency.

In some embodiments, the high pressure alert 170 can be activated because of the high pressure within the HVAC system 10 causing the high pressure switch to get activated. For example, such condition can be because of blocking or substantially closing a metering device measuring a volume of the refrigerant in a refrigeration system of the HVAC system 10. The high pressure alert 170 indicates the high pressure switch in the HVAC system 10 and indicates that the compressor is in an inoperable condition.

A low pressure alert 172 can have the first section 28 and the second section 30 of the LED lights to be in the second color (for example, in the blue color). For example, the second color LED lights 40 for the first section of LED lights 28 and the second color LED lights 44 for the second section 30 of the LED lights can be turned on. In some embodiments, the low pressure alert indicates a significant refrigerant leak, and during such alert, the alert system 12 indicates to the user that the HVAC system 10 is out of order.

In some embodiments, a low pressure (LP) switch can used in operation of the HVAC system 10. The low pressure switch is disposed on the suction line of the HVAC system 10. For example, in some embodiments, one end of the sensor line is connected to a power source. In some embodiments, the LP switch can be turned from a closed to an open position to break the circuit. This state is determined on the input of the PLR 32 and/or expansion module 34. In some embodiments, the logic of the PLR 32 and/or expansion module 34 can send a corresponding signal to the LED lights 40 for the second color for the first section 28 of the LED lights (for example, the blue color LED lights 40 of the “Run” section) and the second color LED lights 44 for the second section 30 (for example, the blue color LED lights 44 for the “Well” section). Then, the low pressure alert 172 is activated by blinking or intermittently flashing the LED lights 40 and 44.

A filter alert 174 can include the first color LED light 38 for the first section 28 of the LED lights, and the second color LED light 44 for the second section 30 of the LED lights. For example, such colors can have the slow blinking or intermittent flashing of the LED lights 38 and 42. For example, the first section 28 of the LED lights (e.g., for the “Run” section) can be in the first color LED lights 38 (for example, a red color). The second section 30 of the LED light (e.g., for the “Well” section) can be in the second color LED lights 44 (for example, a blue color). One or both of the first section 28 of the LED light and the second section 30 can be blinking with a slow frequency of speed or intermittent flashing.

In some embodiments, the high pressure switch can correspond at least partially in one or more structure and operation to a low pressure switch of the fault detection and alert system 12. In some embodiments, the low pressure switch can actuate the alarm 172 when the pressure reaches 10 psi. In some embodiments, the high pressure switch, the PLR 32 and/or expansion module 34 can turn off the compressor. In some embodiments, the high pressure (HP) switch opens and this opening indicates that there is no power going through the circuit to the compressor. Therefore, the compressor is shut off.

In some embodiments, the differential sensor is actuated when an air filter gets excessive dust and partially or fully blocked by debris. When the differential sensor is actuated, the PLR 32 and/or expansion module 34 sends the signals for the first color LED light 38 for the first section 28 of LED lights (for example, the red color LED light 38 for the “Run” section) and the second color LED light 44 for the second section 30 (for example, the blue color LED light 44 for the “Well” section). Then, the filter alert 174 is activated by blinking or intermittently flashing the LED lights 38 and 44.

In some embodiments, the differential filter includes a diaphragm that senses changes in low pressure. For example, the diaphragm can include a plastic material which can be disposed inside the HVAC system 10. For example, the diaphragm can be used to compare pressure values on both sides of the diaphragm. If there is a predetermined differential value between the two values on two sides of the diaphragm, then the filter switch can be closed, which can cause a signal to be sent for the alert system 12 to indicate the filter alert 174. When the filter switch closes, then the filter alert 174 is actuated. Unlike the high pressure alert 170, the low pressure alert 172, and the security/anti-theft alert 168, during the actuation of the filter alert 174 the compressor is not shut down.

The sensors of the air filter sense the actual pressure differential on both sides of the diaphragm indicating dirtiness of the HVAC system 10. For example, in some embodiments, once a certain level of uncleanliness is reached, the alarm 174 is actuated. In a typical thermostat, reminders to change the filter after a certain period of time passes is set by a factory or a user.

If an attempt to break into the HVAC system 10 is made, and if the pipes (which can be formed of the copper material) are attempted to be taken from the HVAC system 10, then the low pressure alert 172 actuates and shuts down the compressor because the low pressure switch is activated by the alert system 12. In some embodiments, the fault detection and alert system 12 can include the current sensors on an evaporator fan, on a condenser fan, and on a compressor. For example, the alert system 12 can also include a dry contact switch. The dry contact is switched by a different power source than the main power source that supplies power to the main components of the HVAC system 10 (such main components as the compressor, the fan, the blower, and the like). The dry contact can be closed once any of the alerts (168, 170, 172, or 174) is activated.

In some embodiments, the PLR 32 and/or expansion module 34 sends a signal to the compressor to be on, but the compressor has not been turned on. In this instance, the feedback from the power wire is sent back and the PLR 32 and/or expansion module 34 will be notified that the compressor has not been turned on. For example, if the compressor was supposed to be on, but it is not running, then the alert system 12 will trigger a fault by the dry contact sending feedback to the PLR 32 and/or the expansion module 34 signaling that the compressor is not turned on. This signal can be sent because the dry contact relay switch that closes is on because the compressor was supposed to be turned on but is not turned on.

The alert system 12 can be more efficient than typical alert systems that include a separate device having a display for input and output. For example, the other device (e.g., a thermostat) can display one or more parameters of the HVAC system 10. There is no requirement that the fault detection and alert system 12 need a separate controller (such as, the external thermostat) to control the operation of the alarms (168, 170, 172, and 174). Such notifications of the fault or errors can be controlled by the PLR 32 and/or the expansion module 34 communicatively and/or electrically coupled to the relay block 36.

In some embodiments, the fault detection and alert system 12 can include a fire/smoke alarm system, a water leak alarm system, and other alarms suitable for faults/errors in the operation of the HVAC system 10. The fire/smoke alarm system, the water leak alarm system, and the other alarms correspond at least partially in one or more of structure and operation to the alerts (or alarms) 168, 170, 172, and/or 174.

FIGS. 1-4 illustrate the LED lights of the first and second sections 28 and 30, respectively, to indicate the alert notifications of the alert system 12. However, one of ordinary skill in the art appreciates that the alarm system 12 may indicate the alarms via any number of sections (for example, one section, three sections, etc.). FIGS. 1-4 illustrate the LED lights of the first and second colors 38, 42 and 40, 44, respectively, to represent the red and blue colors, respectively, to indicate the alert notifications of the alarm system 12. However, one of ordinary skill in the art appreciates that the alarm system 12 may indicate the alarms via any number of colors (for example, white, green, yellow, etc.).

It should be understood that no claim element herein is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase “means for.”

The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

As used herein, the term “circuit” may include hardware structured to execute the functions described herein. In some embodiments, each respective “circuit” may include machine-readable media for configuring the hardware to execute the functions described herein. The circuit may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, and/or sensors. In some embodiments, a circuit may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOC) circuits), telecommunication circuits, hybrid circuits, and any other type of “circuit.” In this regard, the “circuit” may include any type of component for accomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring.

The “circuit” may also include one or more processors communicatively coupled to one or more memory or memory devices. In this regard, the one or more processors may execute instructions stored in the memory or may execute instructions otherwise accessible to the one or more processors. In some embodiments, the one or more processors may be embodied in various ways. The one or more processors may be constructed in a manner sufficient to perform at least the operations described herein. In some embodiments, the one or more processors may be shared by multiple circuits (e.g., circuit A and circuit B may include or otherwise share the same processor which, in some example embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory). Alternatively or additionally, the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other example embodiments, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multi-threaded instruction execution. Each processor may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory. The one or more processors may take the form of a single core processor, multi-core processor (e.g., a dual core processor, triple core processor, quad core processor), microprocessor. In some embodiments, the one or more processors may be external to the apparatus, for example the one or more processors may be a remote processor (e.g., a cloud based processor). Alternatively or additionally, the one or more processors may be internal and/or local to the apparatus. In this regard, a given circuit or components thereof may be disposed locally (e.g., as part of a local server, a local computing system) or remotely (e.g., as part of a remote server such as a cloud based server). To that end, a “circuit” as described herein may include components that are distributed across one or more locations.

An exemplary system for implementing the overall system or portions of the embodiments might include general purpose computing devices in the form of computers, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. Each memory device may include non-transient volatile storage media, non-volatile storage media, non-transitory storage media (e.g., one or more volatile and/or non-volatile memories), etc. In some embodiments, the non-volatile media may take the form of ROM, flash memory (e.g., flash memory such as NAND, 3D NAND, NOR, 3D NOR), EEPROM, MRAM, magnetic storage, hard discs, optical discs, etc. In other embodiments, the volatile storage media may take the form of RAM, TRAM, ZRAM, etc. Combinations of the above are also included within the scope of machine-readable media. In this regard, machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions. Each respective memory device may be operable to maintain or otherwise store information relating to the operations performed by one or more associated circuits, including processor instructions and related data (e.g., database components, object code components, script components), in accordance with the example embodiments described herein.

The terms “data processing system” or “processor” encompass all kinds of apparatus, devices, and machines for processing data, including by way of example, a programmable processor, a computer, a system on a chip, or multiple ones, or combinations of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a circuit, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more subsystems, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example, semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

It should also be noted that the term “input devices,” as described herein, may include any type of input device including, but not limited to, a keyboard, a keypad, a mouse, joystick or other input devices performing a similar function. Comparatively, the term “output device,” as described herein, may include any type of output device including, but not limited to, a computer monitor, printer, facsimile machine, or other output devices performing a similar function.

For example, to provide for interaction with a user, arrangements of the subject matter described in this specification can be carried out using a computer having a display device, e.g., a QLED (quantum dot display), OLED (organic light-emitting diode), or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, tactile input, or other biometric information. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

Arrangements of the subject matter described in this specification can be carried out using a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an arrangement of the subject matter described in this specification, or any combination of one or more such backend, middleware, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some arrangements, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.

While this specification contains many specific arrangement details, these should not be construed as limitations on the scope of the present disclosure or of what may be claimed, but rather as descriptions of features specific to particular arrangements of the present disclosure. Certain features that are described in this specification in the context of separate arrangements can also be carried out in combination or in a single arrangement. Conversely, various features that are described in the context of a single arrangement can also be carried out in multiple arrangements, separately, or in any suitable sub combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub combination or variation of a sub combination.

Additionally, features described with respect to particular headings may be utilized with respect to and/or in combination with illustrative arrangement described under other headings; headings, where provided, are included solely for the purpose of readability and should not be construed as limiting any features provided with respect to such headings.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the arrangements described above should not be understood as requiring such separation in all arrangements, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products embodied on tangible media.

Thus, particular arrangements of the subject matter have been described. Other arrangements are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily need the particular order shown, or sequential order, to achieve desirable results. In certain arrangements, multitasking and parallel processing may be advantageous

In the foregoing description of certain embodiments, specific terminology has been resorted to for the sake of clarity. However, the disclosure is not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes other technical equivalents which operate in a similar manner to accomplish a similar technical purpose. Terms such as “left” and right”, “front” and “rear”, “above” and “below” and the like are used as words of convenience to provide reference points and are not to be construed as limiting terms.

In this specification, the word “comprising” is to be understood in its “open” sense, that is, in the sense of “including”, and thus not limited to its “closed” sense, that is the sense of “consisting only of”. A corresponding meaning is to be attributed to the corresponding words “comprise”, “comprised” and “comprises” where they appear.

In addition, the foregoing describes only some embodiments of the invention(s), and alterations, modifications, additions and/or changes can be made thereto without departing from the scope and spirit of the disclosed embodiments, the embodiments being illustrative and not restrictive.

Furthermore, invention(s) have been described in connection with what are presently considered to be the most practical and preferred embodiments and it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the invention(s). Also, the various embodiments described above may be implemented in conjunction with other embodiments, e.g., aspects of one embodiment may be combined with aspects of another embodiment to realize yet other embodiments. Further, each independent feature or component of any given assembly may constitute an additional embodiment.

Claims

1. A fault detection and alert system to display a fault in a heating, ventilation, and air conditioner (HVAC) system, the system comprising:

a plurality of LED lights indicating the fault and disposed on an exterior surface of a housing of the HVAC system; and

a programmable logic relay (PLR) having one or more relay outputs configured to activate, based on a type of the fault and according to fault codes, an alert notification having a pattern;

wherein the alert system operates without another device having a display for input and output, the other device displaying one or more parameters of the exterior HVAC system.

2. The system of claim 1, further comprising at least one of a high pressure switch, a low pressure switch, a differential air pressure switch, or an access panel switch.

3. The system of claim 2, wherein at least one of the PLR relay outputs is activated to control the LED lights in response to corresponding activation of at least one of a high pressure switch, a low pressure switch, a differential air pressure switch, or an access panel switch.

4. The system of claim 1, wherein the alert notification pattern further comprises:

at least one of switching a color of the LED light and an intermittent blinking of the LED light.

5. The system of claim 1, wherein the PLR relay output performs at least one of turning on, turning off, or pulsating the PLR relays at a predetermined interval of time.

6. The system of claim 5, wherein the predetermined interval of time is at least one of 1 second or 0.5 seconds.

7. The system of claim 1, further comprising an LED power source.

8. The system of claim 1, further comprising a filter having a sensor configured to indicate that a predetermined level of uncleanness is reached within the housing of the HVAC system.

9. The system of claim 1, wherein the fault is a security threat.

10. The system of claim 1, wherein the alert system indicates at least one of a high pressure, a low pressure, a dirty filter, or a security threat.

11. The system of claim 1, further comprising one or more diffusers, the diffusers covering the LED lights.

12. The system of claim 11, wherein the diffuser has an extended range of visibility.

13. The system of claim 1, wherein the housing is water tight.

14. The system of claim 1, further comprising more than one separate sections for disposing the LED lights therewithin.

15. The system of claim 1, wherein at least some portion the LED lights can be formed in a shape of a company logo.