The present disclosure relates generally to compressor systems utilized in heating, ventilation, and air conditioning (HVAC) applications and more particularly, but not by way of limitation, to methods and systems for balancing pressure across a rotary compressor or any high-side compressor utilizing a pressure-equalization valve and an internal power circuit.
Compressor systems are commonly utilized in HVAC applications. Many HVAC applications utilize high-side compressors that include rotary compressors. Rotary compressors are not tolerant to liquid intrusion into the compression mechanism. Additionally, high-side compressors, such as rotary compressors, have difficulty starting when a pressure differential across the compressor is greater than approximately 7 psi. Many high-side compressors, such as rotary compressors, utilize very large accumulators in combination with an additional fluid reservoir to prevent liquid intrusion into the compression mechanism. Presently, no design exists that facilitates pressure equalization across the high-side compressor.
In one aspect, the present disclosure relates to a rotary compressor system. The rotary compressor system includes a compressor housing. A compression mechanism is disposed within the compressor housing. An accumulator is fluidly coupled to the compressor housing via a pressure-equalization tube. A pressure-equalization valve is disposed in the pressure-equalization tube. The pressure-equalization valve closes access to the pressure-equalization tube responsive to an electrical current being applied to the pressure-equalization valve. The pressure-equalization valve is electrically coupled to the compression mechanism such that interruption of electrical current to the compression mechanism interrupts electrical current to the pressure-equalization valve thereby opening the pressure-equalization valve.
In another aspect, the present disclosure relates to a method of equalizing pressure in a rotary-compressor system. The method includes fluidly coupling a compressor housing to an accumulator via a pressure-equalization tube and arranging a pressure-equalization valve to limit refrigerant flow through the pressure-equalization tube. The pressure-equalization valve closes responsive to an electrical current being applied to the pressure-equalization valve. The pressure-equalization valve is electrically connected such that an interruption of electrical current to a compression mechanism interrupts electrical current to the pressure-equalization valve thereby causing the pressure-equalization valve to open. Pressure across a compressor housing is balanced through the pressure-equalization tube.
In another embodiment, the present disclosure relates to a rotary compressor system. The rotary compressor system includes a compressor housing. A compression mechanism is disposed within the compressor housing. An accumulator is fluidly coupled to the compressor housing via a pressure-equalization tube. A pressure-equalization valve is disposed in the pressure-equalization tube. The pressure-equalization valve closes access to the pressure-equalization tube responsive to an electrical current being applied to the pressure-equalization valve. An overload protection switch is electrically coupled to the compression mechanism and to the pressure-equalization valve. The overload protection switch interrupts electrical current to the compression mechanism and to the pressure-equalization valve thereby opening the pressure-equalization valve.
For a more complete understanding of the present disclosure and for further objects and advantages thereof, reference may now be had to the following description taken in conjunction with the accompanying drawings in which:
Various embodiments will now be described more fully with reference to the accompanying drawings. The disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.
The HVAC system 1 includes a circulation fan 10, a gas heat 20, electric heat 22 typically associated with the circulation fan 10, and a refrigerant evaporator coil 30, also typically associated with the circulation fan 10. In a typical embodiment, the circulation fan 10 may be, for example a single-speed circulation fan or a variable-speed circulation fan. The circulation fan 10, the gas heat 20, the electric heat 22, and the refrigerant evaporator coil 30 are collectively referred to as an “indoor unit” 48. In a typical embodiment, the indoor unit 48 is located within, or in close proximity to, an enclosed space. The HVAC system 1 also includes a compressor 40 and an associated condenser coil 42, which are typically referred to as an “outdoor unit” 44. In a typical embodiment, the compressor 40 may be, for example a fixed-speed compressor or a variable-speed compressor. In various embodiments, the outdoor unit 44 is, for example, a rooftop unit or a ground-level unit. The compressor 40 and the associated condenser coil 42 are connected to an associated evaporator coil 30 by a refrigerant line 46. In a typical embodiment, the compressor 40 is, for example, a single-stage compressor, a multi-stage compressor, a single-speed compressor, or a compressor. Also, as will be discussed in more detail below, in various embodiments, the compressor 40 may be a compressor system including at least two compressors of the same or different capacities. The circulation fan 10, sometimes referred to as a blower, is configured to operate at different capacities (i.e., variable motor speeds) to circulate air through the HVAC system 1, whereby the circulated air is conditioned and supplied to the enclosed space.
Still referring to
The HVAC controller 50 may be an integrated controller or a distributed controller that directs operation of the HVAC system 1. In a typical embodiment, the HVAC controller 50 includes an interface to receive, for example, thermostat calls, temperature setpoints, blower control signals, environmental conditions, and operating mode status for various zones of the HVAC system 1. In a typical embodiment, the HVAC controller 50 also includes a processor and a memory to direct operation of the HVAC system 1 including, for example, a speed of the circulation fan 10.
Still referring to
In a typical embodiment, the HVAC system 1 is configured to communicate with a plurality of devices such as, for example, a monitoring device 56, a communication device 55, and the like. In a typical embodiment, the monitoring device 56 is not part of the HVAC system. For example, the monitoring device 56 is a server or computer of a third party such as, for example, a manufacturer, a support entity, a service provider, and the like. In other embodiments, the monitoring device 56 is located at an office of, for example, the manufacturer, the support entity, the service provider, and the like.
In a typical embodiment, the communication device 55 is a non-HVAC device having a primary function that is not associated with HVAC systems. For example, non-HVAC devices include mobile-computing devices that are configured to interact with the HVAC system 1 to monitor and modify at least some of the operating parameters of the HVAC system 1. Mobile computing devices may be, for example, a personal computer (e.g., desktop or laptop), a tablet computer, a mobile device (e.g., smart phone), and the like. In a typical embodiment, the communication device 55 includes at least one processor, memory and a user interface, such as a display. One skilled in the art will also understand that the communication device 55 disclosed herein includes other components that are typically included in such devices including, for example, a power supply, a communications interface, and the like.
The zone controller 80 is configured to manage movement of conditioned air to designated zones of the enclosed space. Each of the designated zones include at least one conditioning or demand unit such as, for example, the gas heat 20 and at least one user interface 70 such as, for example, the thermostat. The zone-controlled HVAC system 1 allows the user to independently control the temperature in the designated zones. In a typical embodiment, the zone controller 80 operates electronic dampers 85 to control air flow to the zones of the enclosed space.
In some embodiments, a data bus 90, which in the illustrated embodiment is a serial bus, couples various components of the HVAC system 1 together such that data is communicated therebetween. In a typical embodiment, the data bus 90 may include, for example, any combination of hardware, software embedded in a computer readable medium, or encoded logic incorporated in hardware or otherwise stored (e.g., firmware) to couple components of the HVAC system 1 to each other. As an example and not by way of limitation, the data bus 90 may include an Accelerated Graphics Port (ACIP) or other graphics bus, a Controller Area Network (CAN) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component interconnect (PCI) bus, a PCI-Express PCI-X) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or any other suitable bus or a combination of two or more of these. In various embodiments, the data bus 90 may include any number, type, or configuration of data buses 90, where appropriate, in particular embodiments, one or more data buses 90 (which may each include an address bus and a data bus) may couple the HVAC controller 50 to other components of the HVAC system 1. In other embodiments, connections between various components of the HVAC system 1 are wired. For example, conventional cable and contacts may be used to couple the HVAC controller 50 to the various components. In some embodiments, a wireless connection is employed to provide at least some of the connections between components of the HVAC system such as, for example, a connection between the HVAC controller 50 and the circulation fan 10 or the plurality of environment sensors 60.
Still referring to
Still referring to
Still referring to
Still referring to
Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. Although certain computer-implemented tasks are described as being performed by a particular entity, other embodiments are possible in which these tasks are performed by a different entity.
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, the processes described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of protection is defined by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This patent application claims priority to, and incorporates by reference for any purpose the entire disclosure of, U.S. Provisional Patent Application No. 62/437,975, filed on Dec. 22, 2016.
Number | Name | Date | Kind |
---|---|---|---|
4286438 | Clarke | Sep 1981 | A |
4820130 | Eber et al. | Apr 1989 | A |
5167491 | Keller, Jr. | Dec 1992 | A |
5186613 | Kotlarek | Feb 1993 | A |
6945073 | Matsumoto | Sep 2005 | B2 |
7086244 | Yamasaki | Aug 2006 | B2 |
7976287 | Hwang | Jul 2011 | B2 |
9458848 | Dreiman | Oct 2016 | B2 |
20110023535 | Morimoto | Feb 2011 | A1 |
20110094752 | Hudson et al. | Apr 2011 | A1 |
20150128629 | Kawano et al. | May 2015 | A1 |
Number | Date | Country |
---|---|---|
1750348 | Feb 2007 | EP |
S59147959 | Aug 1984 | JP |
H09196479 | Jul 1997 | JP |
Entry |
---|
Ullrich, Brandon, “U.S. Appl. No. 15/495,061”, filed Apr. 24, 2017. |
Number | Date | Country | |
---|---|---|---|
20180180047 A1 | Jun 2018 | US |
Number | Date | Country | |
---|---|---|---|
62437975 | Dec 2016 | US |