Patent Application
20200300492
This application is directed, in general, to heating, ventilation, and air conditioning systems (HVAC) and, more specifically, to systems and methods for ensuring that sensed data from a sensor logically paired with the compressor, from among a set of two, or more, compressors configured for tandem operation, to which the sensor is physically coupled.
Some HVAC systems utilize one or more tandem compressor arrangements. Tandem compressors may share common refrigerant piping. Specifically, the suction pipe leg for each compressor configured for tandem operation may fork off from a single, common suction pipe. Similarly, the discharge pipe leg for each compressor configured for tandem operation may merge into a single, common discharge pipe. The tandem compressor arrangement may allow for efficient HVAC system operation by providing greater ability to match partial load demands on the HVAC system while still allowing for high overall system capacity during full load operation.
One disadvantage of the tandem compressor arrangement is that the shared piping among the tandem compressors, and attendant merged refrigerant flow, can make monitoring specific compressor operation and identifying specific compressor failures difficult. For example, the tandem compressor arrangement can render a discharge pressure switch incapable of identifying the specific failing compressor among the tandem compressors when an over-pressure condition is sensed. This may be due to the merged discharge piping among the tandem compressors. The discharge pressure switch may sense the combined pressure from all compressors configured for tandem operation, and lack a means for discerning the specific compressor, or compressors, causing the failure condition.
In HVAC systems utilizing a tandem compressor arrangement, it is critical for individual monitoring of the performance and operation of each compressor of tandem compressor arrangement that the refrigerant discharge temperature exiting each of the tandem compressors be accurately sensed. The HVAC systems provided with tandem compressors commonly place a temperature sensor at, or near, the discharge port of each compressor of the tandem compressor arrangement to sense the refrigerant discharge temperature specific to each compressor of the tandem compressor arrangement.
Unfortunately, the proximity of tandem compressors to one another within the compressor section of an HVAC system creates the possibility that these discharge temperature sensors may be installed on the incorrect compressor. Incorrect installation may destroy the ability of the HVAC system to monitor the performance the individual compressors configured for tandem operation since the temperature sensor and compressor pairing in the HVAC system control logic will not match the physical pairing of the components.
In accordance with the present invention, a method and apparatus for verifying one or more couplings of compressors with sensors within an HVAC system having more than one compressor configured to share common refrigerant piping are provided.
A first apparatus is provided for verifying one or more sensors are coupled to an associated compressor of an HVAC system. The HVAC system may comprise a first compressor having a first discharge pipe leg coupled to a discharge port of the first compressor and a second compressor having a second discharge pipe leg coupled to a discharge port of the second compressor, wherein the second discharge pipe leg merges with the first discharge pipe leg to form a common discharge pipe shared by the first and second compressors. The HVAC system may further comprise a first sensor coupled to the first discharge pipe leg, the first sensor configured to transmit a first signal directly or via one or more intermediate devices to a location remote to the first sensor. The first signal may indicate one or more temperatures of refrigerant within the first discharge pipe leg. A controller may be operably coupled to switch each of the first and second compressors between energized and de-energized states and to receive the first signal which may indicate one or more temperatures of refrigerant within the first discharge pipe leg of the first compressor. The controller may cause a temperature increase of the refrigerant within the first discharge pipe leg of the first compressor. The controller may receive from the first sensor the first signal which may indicate one or more temperatures of refrigerant within the first discharge pipe legs. The controller may determine whether the first signal indicates one or more temperatures above a threshold value. If the first signal indicates one or more temperatures above the threshold value, the controller may generate a first pairing signal to indicate that the first sensor is coupled with the first compressor. If the first signal indicates one or more temperatures below the threshold value, the controller may generate a second pairing signal to indicate that the first sensor is not coupled with the first compressor.
A first method of verifying the couplings of one or more sensors to an associated compressor of an HVAC system is provided. A first discharge pipe leg may couple to a discharge port of a first compressor. A second discharge pipe leg may couple to a discharge port of a second compressor. The first and second discharge pipe legs may couple to a common discharge pipe shared by the first and second compressors. A first sensor may couple to the first discharge pipe leg, the first sensor may transmit a first signal directly or via one or more intermediate devices to a location remote to the first sensor. The first signal may indicate one or more temperatures of refrigerant within the first discharge pipe leg. A controller may operably couple to the first and second compressors to switch each of the first and second compressors between energized and de-energized states. The controller may couple to the first sensor to receive the first signal which may indicate one or more temperatures of refrigerant within the first discharge pipe leg. The controller may cause a temperature increase of the refrigerant within the first discharge pipe leg of the first. The controller may receive the first signal from the first sensor which may indicate one or more temperatures of refrigerant within the first discharge pipe leg. The controller may determine whether the first signal indicates one or more temperatures above a threshold value. If the first signal indicates one or more temperatures above the threshold value, the controller may generate a first pairing signal indicating the first sensor is paired with the first compressor. If the first signal indicates one or more temperatures below the threshold value, the controller may generate a second pairing signal indicating the first sensor is not paired with the first compressor.
Advantageously, the apparatus and method provided may prevent data received from a system sensor, for use in monitoring compressor performance, from being associated to the wrong compressor from among the compressors comprising a tandem compressor group. Pairing the data provided by a sensor with the correct compressor ensures that HVAC system safeguards for protecting the compressors from operation in unsafe conditions will be effective. Further, implementation of the methods provided may provide a diagnostic function, identifying inoperative, or improperly coupled, components within the HVAC system.
For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following Detailed Description taken in conjunction with the accompanying drawings, in which:
A compressor section of an HVAC system 100 that may implement the methods provided herein is shown in
The HVAC system 100 components shown may be part of a system of components configured for vapor compression cycle operation, comprising, at least, a condenser, a metering device, and an evaporator. The HVAC system 100 may provide heating, ventilation, or cooling supply air to a space. The HVAC system 100 may be used in residential or commercial buildings, and in refrigeration. The HVAC system 100 is not necessarily capable of all of heating, ventilation, and air conditioning operations.
The HVAC system 100 may be configured to operate in response to both full load and partial load demands. Full load demand may require operation of both of the compressors 104A. B while partial load demand may require operation of only one of among the compressors 104A, B. In an embodiment, during partial load operation, the HVAC system 100 may be configured to energize only a particular compressor, the compressor 104A perhaps. In such embodiments, the compressor 104A may be described as the partial load compressor. In alternative embodiments, the HVAC system 100 may not be provided with a particular compressor 104A, B designated for use in response to all partial load demand. In such alternative embodiments, either of the compressors 104A of 104B may be energized in response to a partial load demand on the HVAC system 100.
As shown in
The HVAC system 100 may comprise a controller 102 for controlling, monitoring, and configuring the HVAC system 100 components and operations. The controller 102 may selectively energize, or de-energize, the HVAC system 100 components. The controller 102 may be configured to alert users of operational statuses, conditions, and component failures of the HVAC system 100. The controller 102 may be connected to the HVAC system 100 components via a wired or wireless connection. The controller 102 may be provided with hardware, software, or firmware.
In an embodiment, the controller may be provided with one, or more, internal components configured to perform one, or more, of the functions of a memory, a processor, and/or an input/output (I/O) interface. The controller 102 memory may store computer executable instructions, operational parameters for system components, predefined ranges, or threshold values for HVAC system 100 operational conditions, and the like. The controller 102 processor may execute instructions stored within the controller 102 memory. The controller 102 I/O interface may operably connect the controller 102 to the HVAC system 100 components, such as the compressors 104A, B, the temperature sensors 116A, B, the pressure sensor 118, the crank case heaters 106A. B, as well as other components that may be provided.
The controller 102 may be provided with logic for monitoring operation and performance of the HVAC system 100 components. The controller 102 may be provided with logic for comparing received data that may be sensed, or calculated, by one or more sensors 116, 118. The data received by the controller 102 may comprise signals from one or more remote devices, such as the temperature sensors 116A, B and 118, described below. The data received by the controller 102 may be received directly from one or more remote devices or may be received indirectly through one or more intermediate devices, such as a signal converter, a processor, an input/output interface, an amplifier, a conditioning circuit, a connector, and the like.
The controller 102 may be provided with logic for reconfiguring aspects of the HVAC system 100 operation in response to the outcome of the comparisons of received data from among multiple sensors 116, 118. For example, the controller 102 may be configured to receive data from one, or more, of the sensors 116 and/or 118 for use in monitoring the compressor, or compressors, 104A, B operation and performance.
Alternatively, or additionally, the controller 102 may be provided with predefined threshold values and/or predefined ranges of values defining safe and/or unsafe operating conditions for the HVAC system 100 and system components. The controller 102 may be implemented with logic for use in controlling the HVAC system 100 in response to the outcome of comparisons between the data received by the controller 102 from one or more sensors 116A. B, and 118 and the predefined threshold values and/or predefined ranges defining safe operating conditions for the HVAC system 100 stored within the controller 102. In such an embodiment, the controller 102 may reconfigure aspects of the HVAC system 100 operations based on the results of the comparisons. Additionally, in such an embodiment, the controller 102 may reconfigure aspects of the logic used by the controller 102 for monitoring operation and performance of the HVAC system 100 components based on the results of data comparisons.
Referring to
In an embodiment, the controller 102 may be configured to use the data received from the temperature sensors 116A, B, in conjunction with other sensed, or calculated data, to calculate, measure, or approximate, operating conditions of the HVAC system 100. For example, the controller may use temperature data received from the temperature sensors 116A, B, along with other data, to calculate compressor sump superheat (CSSH), refrigerant operating pressures, saturation pressures and temperatures, and the like. Methods for calculating, or determining, operational conditions of this sort are known by those of ordinary skill in the relevant art and, thus, are not described herein. The controller may monitor performance of the HVAC system 100, and components thereof, by comparing the operating condition values to tolerance values, or tolerance ranges. The controller 102 may be configured to take some corrective action, or actions, if a tolerance value, or range, is exceeded.
The compressors 104A, B may compress received refrigerant as part of a vapor compression cycle. The compressors 104A, B may be compressors of any type comprising the prior art, such as reciprocating compressors, scroll compressors, and the like. The compressors 104A, B may be single speed or variable speed compressors.
In an embodiment, the compressors 104A, B may be configured to operate as tandem compressors, sharing the common suction pipe 108 and the common discharge pipe 114, as shown in
The compressors 104A, B may each receive refrigerant from the common suction pipe 108, whereby the refrigerant present in each discharge pipe leg 112A, B may be at substantially the same temperature and pressure. During operation, one, or both, of the compressors 104A, B may compress the refrigerant and discharge the refrigerant through the common discharge pipe 114. From the common discharge pipe 114, the refrigerant may flow through a condenser, an expansion device, and an evaporator before returning to the common suction pipe 108.
As shown in the embodiment of
In an embodiment, the HVAC system 100 may be implemented with the temperature sensors 116A, B for directly sensing, calculating, or determining from sensed data through known methods, the HVAC system 100 refrigerant temperature within the portion of refrigerant piping to which the temperature sensors 116A, B are affixed. The temperature sensors 116A, B may be operably connected to the controller 102 via a wired or wireless connection and may communicate sensed data to the controller 102. In an embodiment, the temperature sensors 116A, B may be thermistors. In an alternative embodiment, the temperature sensors 116A, B may be thermocouples, resistive temperature devices, infrared sensors, thermometers, or the like.
In an embodiment, the temperature sensors 116A, B may transmit analog or pneumatic signals either directly, or indirectly, to the controller 102. In such an embodiment, the signals transmitted by the temperature sensors 116A, B may be converted to digital signals prior to use by the controller 102. Alternatively, in an embodiment, the temperature sensors 116A, B may transmit digital signals to the controller 102. In such an embodiment, the digital signals transmitted by the temperature sensors 116A, B may be processed prior to use by the controller 102 to convert the signals to a different voltage, to remove interference from the circuits, to amplify the signals, or other similar forms of digital signal processing. For each alternative described, herein, the signals of the temperature sensors 116A, B may be transmitted to the controller 102 directly or indirectly, such as through one or more intermediary devices.
The temperature sensor 116A may be located on the discharge pipe leg 112A at a point before the discharge pipe leg 112A merges with the discharge pipe leg 112B to form the common discharge pipe 114. Similarly, the temperature sensor 116B may be located on the discharge pipe leg 112B at a point before the discharge pipe leg 112B merges with the discharge pipe leg 112A to form the common discharge pipe 114. In this arrangement, the temperature sensor 116A may sense the temperature of the refrigerant leaving the compressor 104A through the discharge pipe leg 112A, while the temperature sensor 116B may sense the temperature of the refrigerant leaving the compressor 104B through the discharge pipe leg 112B.
As shown in
The pressure sensor 118 may be located on the common suction pipe 108, as shown in
In the embodiment shown, for example, data sensed by the temperature sensors 116A, B may be used in conjunction with data from the pressure sensor 118 to calculate the CSSH for the compressors 104A, B, respectively, according to known methods. The CSSH value, or values, may be used by the controller 102 to monitoring the operating conditions and performance of one, or both, of the compressors 104A, B to ensure operation in safe conditions, only.
Referring to
The method 200 may be executed by the controller 102 to pair, within the controller 102 logic, each among the tandem compressors 104A, B with the particular temperature sensor 116A or 116B to which the compressor 104A, B is operably coupled, whereby the controller 102 may associate the data received from the temperature sensor 116A or 116B to the correct compressor 104A or 104B. The method 200 may ensure that the compressors 104A, B operation monitoring logic within the controller 102 is configured to match the actual temperature sensors 116A, B to compressors 104A, B physical couplings within the HVAC system 100.
In some embodiments, prior to execution of the method 200, the controller 102 may be provided with logic predefining one, or more, default logical couplings of temperature sensors 116A, B and compressors 104A, B. In such embodiments, the default couplings may be based on the physical locations of the electrical couplings, such as contactors, connection ports, or the like, to which each temperature sensor 116A, B is coupled. In such embodiments, each of the temperature sensors 116A, B may be logically paired, by default, with the compressor 104A or 104B disposed closest to the location of the electrical coupling to which the temperature sensor 116A or 116B is coupled. In such embodiments, and in instances where the default logical couplings are found to match the actual physical couplings present in the HVAC system 100, the method 200 may verify the default logical couplings.
In instances where the default logical couplings are found to not match the actual physical couplings present in the HVAC system 100, the method 200 may set the logical couplings to match physical couplings present in the HVAC system 100. In such instances, the controller 102 may be configured to alert the user, indicating that one, or more, of the temperature sensors 116A, B is incorrectly placed or, alternatively, disconnected from both of the compressors 104A, B.
In alternative embodiments, prior to execution of the method 200, the controller 102 may not be provided with logic predefining one, or more, default logical couplings of temperature sensors 116A, B and compressors 104A, B. In such embodiments, the method 200 may be used to set the logical couplings of temperature sensors 116A, B and compressors 104A, B to match physical couplings present in the HVAC system 100. The controller 102 may alert the user when any logical temperature sensor 116 and compressor 104 coupling of the HVAC system 100 is verified, or set, using the method 200.
At the step 201, the controller 102 may receive input triggering verifying, or setting, of the logical couplings of the temperature sensors 116A, B and the compressors 104A, B of the HVAC system 100 to correspond to the physical couplings present in the HVAC system 100. The controller 102 may receive such input from a user or from control logic within the controller 102. A user may initiate the method 200 by commanding the HVAC system 100 controller 102 to perform a system diagnostic routine.
The method 200 may be initiated by the controller 102 in response to a partial load demand on the HVAC system 100 requiring operation of one among the compressors 104A, B. The partial load demand may follow a period of no demand upon the HVAC system 100 in which none of the compressors 104A, B were operating. Alternatively, the partial load demand may follow a period demand upon the HVAC system 100 requiring operation of both of the compressors 104A, B. In a further alternative, the method 200 may be initiated by the controller 102 in response to power on of the HVAC system 100 such as during commissioning of the HVAC system 100 or after maintenance requiring removal of power from the HVAC system 100. The method 200, regardless of the triggering event initiating commencement, may, at any time in the method, be abandoned by the controller 102 in response to changes in demand of the HVAC system 100, such as the detection of a full load demand on the HVAC system 100, for example.
At the step 202, the controller 102 may energize one compressor from among the compressors 104A, B while the remaining compressor 104A, B is de-energized, causing heating of the refrigerant within the compressor 104A or 104B energized and within the discharge pipe leg 112A or 112B corresponding to the energized compressor 104A or 104B. The specific compressor amongst the compressors 104A, B energized at the step 202 may depend on the HVAC system 100 configuration and the triggering input initiating the method 200. If the method 200 is initiated in response to a partial load demand on the HVAC system 100, the designated partial load compressor, if provided, may be the compressor 104A, B energized. If the method 200 is initiated in response to another triggering input, either compressor from among the compressors 104A, B that remains unpaired within the controller 102 logic through execution of a first pass through the method 200 may be the compressor 104A, B energized at the step 202.
The energized compressor 104A or 104B may compress the refrigerant passing through it, discharging heated gaseous refrigerant into the corresponding discharge pipe leg 112A, B. The temperature increase of the heated refrigerant may be sensed by the temperature sensor 116A or 116B that is physically coupled to the discharge pipe leg 112A or 112B through which the heated refrigerant is flowing.
At the step 203, the controller 102 may receive data sensed by the temperature sensors 116A, B. In an embodiment, at the step 203, the controller 102 may be configured to receive the data from the temperature sensors 116A, B only after a period of time elapses following the energizing of the compressor 104A or 104B at step 202. This wait time may allow for the heated discharge refrigerant from the energized compressor 104A, B to be sensed by the temperature sensors 116A, B. Additionally, or alternatively, the wait time may allow for cooling of the refrigerant in the discharge pipe leg 112A, B corresponding to the de-energized compressor from among the compressors 104A, B in instances where the method 200 is initiated following a period of full load operation of the HVAC system 100.
In embodiments in which the controller 102 is configured to wait for a defined period of time to elapse before receiving data from the temperature sensors 116A, B at the step 203, the wait time may be a predefined period of time. For example, the controller 102 may be configured to wait for ten minutes following energizing of the compressor 104A, B before receiving data from the temperature sensors 116A, B at the step 203. In alternative embodiments, the predefined wait time may be a period of time in the range of between two and twenty minutes.
If, at the expiration of the predefined wait time, the controller 102 does not receive data from one, or both, of the temperature sensors 116A, B indicating a rise in refrigerant temperature or, alternatively, a temperature differential between the data received, one, or both, of the temperature sensors 116A, B may be diagnosed as inoperable or disconnected. The controller 102 may generate a signal to cause an alert, indicating to the user of a fault condition. The controller may, further, discontinue execution of the method 200 at the step 208.
In alternative embodiments, the controller 102 may be configured to receive, and continuously monitor, data from one, or both, of the temperature sensors 116A, B as soon as the compressor 104A, B is energized at the step 202. In such embodiments, the controller 102 may use received data from one, or both, of the temperature sensors 116A, B for use at the step 204 immediately upon detection of data indicating that a predefined threshold value, which may be a temperature value or a temperature differential, is exceeded. Advantageously, according to such alternative embodiments, faster execution of the method 200 may be possible, as the wait time at the step 203 may be reduced.
In such alternative embodiments, the controller 102 may be implemented with logic defining a timeout period, which may be ten minutes. Alternatively, the timeout period may be within a range of between two and twenty minutes. If, by the expiration of timeout period, the controller 102 has not received data from at least one of the temperature sensors 116A, B indicating that the threshold value is exceeded, one, or both, of the temperature sensors 116A, B may be diagnosed as being inoperable or disconnected. The controller 102 may generate a signal causing an alert, indicating the temperature sensor 116A, B fault condition. The controller may, further, discontinue execution of the method 200 at the step 208.
At the step 204, the controller may compare the data received from one, or both, of the temperature sensors 116A, B. In an embodiment, the data received from the temperature sensor 116A may be compared to the data received from the temperature sensor 116B to determine the temperature sensor 116A, B sensing the higher refrigerant temperature. Alternatively, the controller 102 may compare the data received from one, or both, of the temperature sensors 116A, B to a predefined threshold value which may be stored within the controller 102 memory.
At the step 205, the controller 102 may generate one or more pairing signals which may indicate verified couplings, or non-couplings, and may set operational control and monitoring logic for the HVAC system 100. The temperature sensor 116A, B identified as sensing the greater refrigerant temperature and the currently energized compressor, from among the compressors 104A, B, may be identified as corresponding to a verified physical coupling of a particular compressor 104A or 104B and a particular temperature sensor 116A or 116B within the HVAC system 100. The controller 102 may generate a pairing signal indicating a particular temperature sensor 116A or 116B is coupled to a particular compressor 104A or 104B. The pairing signal may set operational control and monitoring logic of the HVAC system 100 to be in accordance with the set or verified coupling indicated by the pairing signal. The controller 102 may use the data from the particular temperature sensor 116A or 116B identified at the step 204 to monitor operation and performance of the particular compressor 104A or 104B energized at the step 202 in response to the non-pairing signal.
Alternatively, or additionally, the controller 102 may generate a non-pairing signal at the step 205 to indicate a particular temperature sensor 116A or 116B is not coupled to a particular compressor 104A or 104B. The non-pairing signal may delete, or alter, existing operational control and monitoring logic to be in accordance with the non-coupled indicated by the non-pairing signal. The controller 102 may not use the data from the particular temperature sensor 116A or 116B identified at the step 204 to monitor operation and performance of the particular compressor 104A or 104B energized at the step 202 in response to the non-pairing signal.
In an embodiment, having verified, or set, a first temperature sensor 116A or 116B and compressor 104A or 104B first coupling at the step 205, the controller 102 may be configured to automatically generate a second pairing signal for setting operational control and monitoring logic to be in accordance with a second coupling of the HVAC system 100. The second coupling may be assumed by process of elimination in light of the verified first coupling. In such embodiments, the particular temperature sensor 116A or 116B not identified at the step 204 and the particular compressor 104A or 104B not energized at the step 202, may be identified as the second coupling within the HVAC system 100.
In an embodiment, the controller 102 may be configured to automatically set the second coupling, as described above, only in instances where the method 200 was initiated in response to a partial load demand on the HVAC system 100. Advantageously, according to such an embodiment, the step 207 may be effectively bypassed since no additional unpaired compressors may be present in the HVAC system at the step 206. Therefore, the controller 102 may return the HVAC system 100 to normal operation at the step 210 to continue meeting the demand on the HVAC system 100 if a demand on the HVAC system is detected at the step 209. During normal operation of the HVAC system 100, the controller 102 may monitor the operation and performance of the compressors 104A, B using data from the temperature sensors 116A, B, respectively.
In embodiments in which the second coupling is not automatically configured, the controller 102 may determine whether an additional unpaired compressor 104A, B, or an unverified default coupling is present in the HVAC system 100 at the step 206. The controller 102 may de-energize the energized compressor 104A, B at the step 207 if an unpaired compressor 104 or unverified default coupling is present in the HVAC system 100 and return to the step 202 to verify, or set, the remaining coupling, as described above.
Alternatively, if the controller determines at the step 206 that no unpaired compressor 104A, B, or unverified default coupling remains, the controller 102 may check for a current demand on the HVAC system 100 requiring energizing of one, or more, of the compressors 104A, B at the step 209. If a demand exists, the controller 102 may return the HVAC system 100 to normal operation to respond to the demand at the step 210. During normal operation of the HVAC system 100, the controller 102 may monitor the operation and performance of the compressors 104A, B using data from the temperature sensors 116A, B, respectively.
If no current demand is detected by the controller 102 at the step 209 the controller 102 may de-energize the compressor 104A, B and, in an embodiment, may proceed to step 301 of the method 300 for verifying, or setting, the crank case heater 106A, B and the compressor 104A, B couplings. In alternative embodiments, the controller 102 may be configured to return the HVAC system 100 to normal operation regardless of whether a demand on the HVAC system is present. In such embodiments, the method 200 may proceed directly to step 210 once all of the compressors 104 are paired, bypassing the step 209.
Referring to
The steps 301-307 of the method 300 may closely mirror the steps 201-207 of the method 200. At the step 301, the method 300 may be initiated from triggering inputs similar to those discussed above, and in reference to the step 201 of the method 200. Additionally, the method 300 may be initiated by logic within the controller 102 commanding execution of the method 300 following completion of the method 200 in instances where no demand on the HVAC system 100 is detected at the step 209 of the method 200. Regardless of the triggering input initiating commencement of the method 300, however, the controller 102 may, at any point in the execution of the method 300, discontinue execution of the method 300 in response to a demand placed on the HVAC system 100 requiring energizing of at least one of the compressors 104A, B.
At the step 302, the controller 102 may selectively energize one crank case heater 106A, B to cause heating of the refrigerant within the compressor 104A or 104B to which the energized crank case heater 106A or 106B is coupled as well as the refrigerant within the discharge pipe leg 112A or 112B corresponding to the compressor 104A or 104B to which the energized crank case heater 106A or 106B is coupled. The refrigerant temperature increase may be sensed by the temperature sensors 116A or 116B which is coupled to the discharge pipe leg 112A or 112B of the compressor 104A or 104B to which the energized crank case heater 106A or 106B is coupled.
At the step 303, the controller may receive sensed data from one, or both, of the temperature sensors 116A, B. The controller 102 may be configured to receive the sensed data only after the expiration of a defined period of time before to allow for cooling and/or heating of the refrigerant within the discharge port legs 112A, B. If unexpected data is sensed, such as, for example, the temperature sensors 116A, B sensing data indicating that the temperature of the respective discharge port legs 112A, B closely match one another, the controller 102 may generate an alert signal indicating a crank case heater 106A, B failure and may terminate the method 300 at the step 308. Similarly, and as described in reference to the steps 203 and 208 above, if the controller 102 times out before receiving acceptable data from the temperature sensors 116A, B, the controller 102 may generate an alert signal indicating a crank case heater 106A, B failure and may terminate the method 300 at the step 308.
At the step 304, the controller 102 may compare the sensed temperature data from the temperature sensors 116A, B to determine the temperature sensor 116A or 116B sensing the higher refrigerant temperature. The controller 102 may, at the step 305, generate one or more pairing signals which may indicate verified couplings, or non-couplings, and may set operational control and monitoring logic for the HVAC system 100. The controller 102 may set or verify the coupling of the energized crank case heater 106A or 106B within the operational and control logic to correspond to the physical coupling identified within the HVAC system 100. The energized crank case heater 106A or 106B may be set, or verified, as being coupled with the compressor 104A or 104B to which the temperature sensor 116A or 116B, identified as sensing the higher temperature data, is coupled. The controller 102 may generate a control signal for setting operational logic to be in accordance with the verified coupling. Alternatively, or additionally, the controller 102 may generate a control signal not setting operational logic to be in accordance with an unverified coupling. The controller 102 may check for additional unpaired crank case heaters 106A, B at the step 306. If additional unpaired crank case heaters 106 are detected, the controller 102 may de-energize any energized crank case heaters 106A, B at the step 307 and return to the step 302.
Alternatively, in an embodiment, having verified, or set, a first crank case heater 106A, B coupling at the step 305, the controller 102 may be configured to automatically set the second crank case heater 106A, B coupling of the HVAC system 100. In such embodiments, the unpaired crank case heater 106A, B may be paired to the paired compressor 104A, B and temperature sensor 116A, B which includes the temperature sensor 116A, B not identified as sensing the higher temperature data at the step 304. The controller 102 may set operational monitoring logic to be in accordance with the second coupling.
Once all of the crank case heaters 106A, B are paired, the controller 102 may return the HVAC system 100 to normal operation at the step 309, which may require energizing, or de-energizing of one, or more of the crank case heaters 106A, B.
Those skilled in the art will appreciate that it may be desirable to bypass, or interrupt, execution of the method 300 in certain instances. For example, if a heating or cooling demand is placed on the HVAC system 100, it may be desirable to forego the method 300 to avoid interruption, or delay, of the HVAC system 100 in meeting the heating or cooling demand. The controller 102 may be implemented with logic for bypassing, or discontinuing, the method 300 at such times.
An HVAC system, such as the HVAC system 100 shown in
The HVAC system 100 may receive input initiating verifying, or setting, of temperature sensor and compressor couplings upon the HVAC system receiving a partial load demand for cooling supply air. The HVAC system 100 controller 102 may energize a first compressor 104A from among the tandem compressors. The controller 102 may wait until a predefined period of time has elapsed, perhaps ten minutes, to allow for the refrigerant flowing within the discharge port leg 112A to be heated. The heated refrigerant within the discharge port leg 112A may be sensed by the temperature sensor 116A when the temperature sensor 116A is coupled to the discharge port leg 112A. The controller 102 may receive data from the temperature sensors 116A, B at the expiration of the waiting time.
The controller 102 may compare the data received to determine that the temperature sensor 116A as sensing a higher refrigerant temperature. The controller 102 may then configure the compressor 104A operation and performance monitoring logic to associate the data received from the temperature sensor 116A identified as sensing a higher refrigerant temperature to the compressor 104A. The controller 102 may then determine that an unpaired compressor, the compressor 104B, is present in the HVAC system 100.
The controller 102 may de-energize the compressor 104A, stopping flow of heated gaseous refrigerant through the discharge port leg 112A. The controller 102 may energize the compressor 104B. The controller 102 may wait for predefined period of time to elapse, perhaps ten minutes, allowing the discharge port leg 112B to be heated by the heated gas refrigerant flowing through the discharge port leg 112B. The discharge port leg 112A may cool during the waiting time. The controller 102 may receive data from the temperature sensors 116A, B upon expiration of the wait time. The controller 102 may compare the data received and may determine the temperature sensor 116A or 116B sensing a higher refrigerant temperature, the temperature sensor 116B, perhaps. The controller 102 may then configure the compressor 104B operation and performance monitoring logic to associate the data received from the temperature sensor 116B to the compressor 104B.
The controller 102 may determine that no remaining unpaired compressors 104 are present in the HVAC system 100 and may return the HVAC system 100 to normal operation to meet a demand on the HVAC system 100. The controller 102 may return the HVAC system 100 to normal operation without continuing to the method 300. This may be desirable to avoid interruption to the HVAC system 100 operation in response to a heating or cooling demand, as execution of the method 300 may require de-energizing the HVAC system 100 compressors 104A, B.
Alternatively, the HVAC system 100 controller 102 may continue to the method 300 if the controller 102 determines that no remaining unpaired compressors 104 are present in the HVAC system 100 and there is no current demand on the HVAC system 100. Additionally, the controller 102 may be configured to continue to execution of the method 300 following completion of the method 200 following initial power on of the HVAC system 100.
Once the controller 102 returns the HVAC system 100 to normal operation following execution of the method 200, or following the methods 200 and 300, the controller 102 may utilize the data received from the temperature sensor 116A, B to monitor the operation and performance of the compressors 104A, B, respectively. The controller 102 may associate the data received from the temperature sensor 116A to the compressor 104A, while the data received from the temperature sensor 116B may be associated to the compressor 104B, in accordance with the logical coupling configuration resulting from the controller 102 executing the method 200. In the HVAC system 100, for example, provided with a suction pressure transducer, the pressure sensor 118, that may be disposed on the common suction pipe 108, the controller 102 may use the data received from the temperature sensors 116A, B, along with the sensed suction pressure data received from the pressure sensor 118 to calculate the CSSH for the compressors 104A, B, individually, for independent monitoring of the operation and performance of the compressors 104A, B.
In the previous discussion, numerous specific details are set forth to provide a thorough understanding of the present invention. However, those skilled in the art will appreciate that the present invention may be practiced without such specific details. In other instances, well-known elements have been illustrated in schematic or block diagram form in order not to obscure the present invention in unnecessary detail. Additionally, for the most part, details concerning well-known features and elements have been omitted inasmuch as such details are not considered necessary to obtain a complete understanding of the present invention, and are considered to be within the understanding of persons of ordinary skill in the relevant art.
Having thus described the present invention by reference to certain of its preferred embodiments, it is noted that the embodiments disclosed are illustrative rather than limiting in nature and that a wide range of variations, modifications, changes, and substitutions are contemplated in the foregoing disclosure and, in some instances, some features of the present invention may be employed without a corresponding use of other features. Many such variations and modifications may be considered desirable by those skilled in the art based upon a review of the foregoing description of preferred embodiments.
This application is a continuation of U.S. patent application Ser. No. 14/642,728, filed on Mar. 9, 2015. U.S. patent application Ser. No. 14/642,728 are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14642728 | Mar 2015 | US |
| Child | 16898834 | US |
