The present invention relates to refrigeration systems and more particularly to predictive maintenance and equipment monitoring of a refrigeration system.
Produced food travels from processing plants to retailers, where the food product remains on display case shelves for extended periods of time. In general, the display case shelves are part of a refrigeration system for storing the food product. In the interest of efficiency, retailers attempt to maximize the shelf-life of the stored food product while maintaining awareness of food product quality and safety issues.
The refrigeration system plays a key role in controlling the quality and safety of the food product. Thus, any breakdown in the refrigeration system or variation in performance of the refrigeration system can cause food quality and safety issues. Thus, it is important for the retailer to monitor and maintain the equipment of the refrigeration system to ensure its operation at expected levels.
Refrigeration systems generally require a significant amount of energy to operate. The energy requirements are thus a significant cost to food product retailers, especially when compounding the energy uses across multiple retail locations. As a result, it is in the best interest of food retailers to closely monitor the performance of the refrigeration systems to maximize their efficiency, thereby reducing operational costs.
Monitoring refrigeration system performance, maintenance and energy consumption are tedious and time-consuming operations and are undesirable for retailers to perform independently. Generally speaking, retailers lack the expertise to accurately analyze time and temperature data and relate that data to food product quality and safety, as well as the expertise to monitor the refrigeration system for performance, maintenance and efficiency. Further, a typical food retailer includes a plurality of retail locations spanning a large area. Monitoring each of the retail locations on an individual basis is inefficient and often results in redundancies.
Accordingly, the present invention provides a system for monitoring a remote refrigeration system. The system includes a plurality of sensors that monitor parameters of components of the refrigeration system and a communication network that transfers signals generated by each of the plurality of sensors. A management center receives the signals from the communication network and processes the signals to determine an operating condition of at least one of the components. The management center generates an alarm based on the operating condition.
In one feature, the management center evaluates each of the signals to determine whether each of the signals is within a useful range, to determine whether each of the signals is dynamic and to determine whether each of the signals is valid.
In other features, the system further includes a temperature sensor monitors a temperature of a refrigerant flowing through the refrigeration system and generates a temperature signal. The management center calculates a pressure, a density and an enthalpy of the refrigerant based on the temperature and based on whether the refrigerant is in one of a saturated liquid phase and a saturated vapor phase.
In other features, the system further includes a pressure sensor that monitors a pressure of a refrigerant flowing through the refrigeration system and that generates a pressure signal. The management center calculates a temperature, a density and an enthalpy of the refrigerant based on said pressure and based on whether the refrigerant is in one of a saturated liquid phase and a saturated vapor phase.
In other features, the system further includes a temperature sensor that monitors a temperature of a refrigerant at a suction side of a compressor of the refrigeration system and generates a temperature signal. A pressure sensor monitors a pressure of a refrigerant at the suction side of the compressor and generates a pressure signal. The management center determines an occurrence of a floodback event based on the temperature signal and the pressure signal. The management center determines a superheat temperature of the refrigerant based on the temperature signal and the pressure signal and processes the superheat through a pattern analyzer to determine whether the floodback event has occurred.
In still other features, the system further includes a temperature sensor that monitors a temperature of a refrigerant at a discharge side of a compressor of the refrigeration system and that generates a temperature signal. A pressure sensor monitors a pressure of a refrigerant at the discharge side of the compressor and generates a pressure signal. The management center determines an occurrence of a floodback event based on the temperature signal and the pressure signal. The management center determines a superheat temperature of the refrigerant based on the temperature signal and the pressure signal and processes the superheat through a pattern analyzer to determine whether the floodback event has occurred.
In yet other features, the system further includes a contactor associated with one of the components. The contactor is cycled between an open position and a closed position to selectively operate the component. The management center monitors cycling of the contactor and generates an alarm when one of a cycling rate is exceeded and a maximum number of cycles is exceeded.
In still another feature, the system further includes an ambient condenser temperature sensor that generates an ambient temperature signal, a condenser pressure sensor that generates a pressure signal, a compressor current sensor that generates a compressor current signal and a condenser current sensor that generates a condenser current signal. The management center determines an operating condition of the condenser based on the ambient temperature signal, the pressure signal, the compressor current signal and the condenser current signal.
In yet another feature, the system further includes a discharge pressure sensor that monitors a pressure of a refrigerant at a discharge side of the compressor and that generates a discharge pressure signal. A suction pressure sensor monitors a pressure of a refrigerant at a suction side of the compressor and generates a suction pressure signal. The management center determines loss of refrigerant based on the discharge pressure and the suction pressure.
The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:
The following description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
With reference to
The compressor rack 110 compresses refrigerant vapor that is delivered to a condenser 126 where the refrigerant vapor is liquefied at high pressure. Condenser fans 127 are associated with the condenser 126 to enable improved heat transfer from the condenser 126. The condenser 126 includes an associated ambient temperature sensor 128 and an outlet pressure sensor 130. This high-pressure liquid refrigerant is delivered to the plurality of refrigeration cases 102 by way of piping 132. Each refrigeration case 102 is arranged in separate circuits consisting of a plurality of refrigeration cases 102 that operate within a certain temperature range.
Because the temperature requirement is different for each circuit, each circuit includes a pressure regulator 134 that acts to control the evaporator pressure and, hence, the temperature of the refrigerated space in the refrigeration cases 102. The pressure regulators 134 can be electronically or mechanically controlled. Each refrigeration case 102 also includes its own evaporator 136 and its own expansion valve 138 that may be either a mechanical or an electronic valve for controlling the superheat of the refrigerant. In this regard, refrigerant is delivered by piping to the evaporator 136 in each refrigeration case 102.
The refrigerant passes through the expansion valve 138 where a pressure drop causes the high pressure liquid refrigerant to achieve a lower pressure combination of liquid and vapor. As hot air from the refrigeration case 102 moves across the evaporator 136, the low pressure liquid turns into gas. This low pressure gas is delivered to the pressure regulator 134 associated with that particular circuit. At the pressure regulator 134, the pressure is dropped as the gas returns to the compressor rack 110. At the compressor rack 110, the low pressure gas is again compressed to a high pressure gas, which is delivered to the condenser 126, which creates a high pressure liquid to supply to the expansion valve 138 and start the refrigeration cycle again.
A main refrigeration controller 140 is used and configured or programmed to control the operation of the refrigeration system 100. The refrigeration controller 140 is preferably an Einstein Area Controller offered by CPC, Inc. of Atlanta, Ga., or any other type of programmable controller that may be programmed, as discussed herein. The refrigeration controller 140 controls the bank of compressors 104 in the compressor rack 110, via an input/output module 142. The input/output module 142 has relay switches to turn the compressors 104 on an off to provide the desired suction pressure.
A separate case controller (not shown), such as a CC-100 case controller, also offered by CPC, Inc. of Atlanta, Ga. may be used to control the superheat of the refrigerant to each refrigeration case 102, via an electronic expansion valve in each refrigeration case 102 by way of a communication network or bus. Alternatively, a mechanical expansion valve may be used in place of the separate case controller. Should separate case controllers be utilized, the main refrigeration controller 140 may be used to configure each separate case controller, also via the communication bus. The communication bus may either be a RS-485 communication bus or a LonWorks Echelon bus that enables the main refrigeration controller 140 and the separate case controllers to receive information from each refrigeration case 102.
Each refrigeration case 102 may have a temperature sensor 146 associated therewith, as shown for circuit B. The temperature sensor 146 can be electronically or wirelessly connected to the controller 140 or the expansion valve for the refrigeration case 102. Each refrigeration case 102 in the circuit B may have a separate temperature sensor 146 to take average/min/max temperatures or a single temperature sensor 146 in one refrigeration case 102 within circuit B may be used to control each refrigeration case 102 in circuit B because all of the refrigeration cases 102 in a given circuit operate at substantially the same temperature range. These temperature inputs are preferably provided to the analog input board 142, which returns the information to the main refrigeration controller 140 via the communication bus.
Additionally, further sensors are provided and correspond with each component of the refrigeration system and are in communication with the refrigeration controller 140. Energy sensors 150 are associated with the compressors 104 and the condenser 126 of the refrigeration system 100. The energy sensors 150 monitor energy consumption of their respective components and relay that information to the controller 140.
Referring now to
The processing center 160 collects data from the refrigeration controller 140, the case controllers and the various sensors associated with the refrigeration system 100. For example, the processing center 160 collects information such as compressor, flow regulator and expansion valve set points from the refrigeration controller 140. Data such as pressure and temperature values at various points along the refrigeration circuit are provided by the various sensors via the refrigeration controller 140. More specifically, the software system is a multi-tiered system spanning all three hardware levels. At the local level (i.e., refrigeration controller and case controllers) is the existing controller software and raw I/O data collection and conversion.
A controller database and the ProAct CB algorithms reside on the site-based controller 161. The algorithms manipulate the controller data generating notices, service recommendations, and alarms based on pattern recognition and fuzzy logic. Finally, this algorithm output (alarms, notices, etc.) is served to a remote network workstation at the processing center 160, where the actual service calls are dispatched and alarms managed. The refined data is archived for future analysis and customer access at a client-dedicated website.
Referring now to
The present invention provides control and evaluation algorithms in the form of software modules to predict maintenance requirements for the various components in the refrigeration system 100. These algorithms include signal conversion and validation, saturated refrigerant properties, watchdog message, recurring notice or alarm message, flood back alert, contactor cycling count, compressor performance, condenser performance, defrost abnormality, case discharge versus product temperature, data pattern recognition, condenser discharge temperature and loss of refrigerant charge. Each is discussed in detail below. The algorithms can be processed locally using the refrigeration controller 140 or remotely at the remote processing center 160.
Referring now to
In step 500, the input registers read the measurement signal of a particular sensor. In step 502, it is determined whether the input signal is within a range that is particular to the type of measurement. If the input signal is within range, the SCV algorithm continues in step 504. If the input signal is not within the range an invalid data range flag is set in step 506 and the SCV algorithm continues in step 508. In step 504, it is determined whether there is a change (Δ) in the signal within a threshold time (tthresh). If there is no change in the signal it is deemed static. In this case, a static data value flag is set in step 510 and the SCV algorithm continues in step 508. If there is a change in the signal a valid data value flag is set in step 512 and the SCV algorithm continues in step 508.
In step 508, the signal is converted to provide finished data. More particularly, the signal is generally provided as a voltage. The voltage corresponds to a particular value (e.g., temperature, pressure, current, etc.). Generally, the signal is converted by multiplying the voltage value by a conversion constant (e.g., ° C/V, kPa/V, A/V, etc.). In step 514, the output registers pass the data value and validation flags and control ends.
Referring now to
Referring now to
With particular reference to
In step 706, it is determined whether the refrigerant is in a saturated vapor state. If the refrigerant is in the saturated vapor state, the RPFT algorithm continues in step 710. If the refrigerant is not in the saturated vapor state, the RPFT algorithm continues in step 712. In step 712, the data values are cleared, flags are set and the RPFT algorithm continues in step 714. In step 710, the RPFT algorithm selects the saturated vapor curve from the thermal property curves for the particular refrigerant type and continues in step 708. In step 708, data values for the refrigerant are determined. The data values include pressure, density and enthalpy. In step 714, the RPFT algorithm outputs the data values and flags.
Referring now to
With particular reference to
In step 906, it is determined whether the refrigerant is in a saturated vapor state. If the refrigerant is in the saturated vapor state, the RPFP algorithm continues in step 910. If the refrigerant is not in the saturated vapor state, the RPFP algorithm continues in step 912. In step 912, the data values are cleared, flags are set and the RPFP algorithm continues in step 914. In step 910, the RPFP algorithm selects the saturated vapor curve from the thermal property curves for the particular refrigerant type and continues in step 908. In step 908, the temperature of the refrigerant is determined. In step 914, the RPFP algorithm outputs the temperature and flags.
Referring now to
Referring now to
Referring now to
The recurring notice or alarm message algorithm includes a notice/alarm message generator 1200, configuration parameters 1202, input parameters 1204 and output parameters 1206. The configuration parameters 1202 include message frequency. The input 1204 includes a notice/alarm message and the output parameters 1206 include a regenerated notice/alarm message. The notice/alarm generator 1200 regenerates the input alarm message at the indicated frequency. Once the notice/alarm condition is resolved, the input 1204 will indicate as such and regeneration of the notice/alarm message terminates.
Referring now to
The saturated vapor temperature for the compressor suction is calculated from the suction pressure. The superheat is calculated for each refrigeration and compressor by subtracting the return temperature from the saturated vapor temperature. Similarly, assuming a saturated liquid, the superheat for each compressor discharge is calculated by subtracting the compressor discharge temperature from the discharge saturated liquid temperature.
Referring now to
Referring now to
Alternative embodiments of the flood back alert algorithm will be described in detail. In a first alternative embodiment, the superheat is compared to a threshold value. If the superheat is greater than or equal to the threshold value then a flood back condition exists. In the event of a flood back condition an alert message is generated.
More particularly, TSAT is determined by referencing a look-up table using Ps and the refrigerant type. An alarm value (A) and time delay (t) are also provided as presets and may be user selected. An exemplary alarm value is 15° F. The suction superheat (SHSUC) is determined by the difference between Ts and TSAT. An alarm will be signaled if SHSUC is greater than the alarm value for a time period longer than the time delay. This is governed by the following logic:
In another alternative embodiment, the rate of change of Ts is monitored. That is to say, the temperature signal from the temperature sensor 118 is monitored over a period of time. The rate of change is compared to a threshold rate of change. If the rate of change of Ts is greater than or equal to the threshold rate of change, a flood back condition exists.
The contactor cycling count algorithm monitors the cycling of the various contacts in the refrigeration system 100. The counting mechanism can be one of an internal or an external nature. With respect to internal counting, the refrigeration controller 140 can perform the counting function based on its command signals to operate the various equipment. The refrigeration controller 140 monitors the number of times the particular contact has been cycled (NCYCLE) for a given load. Alternatively, with respect to external counting, a separate current sensor or auxiliary contact can be used to determine NCYCLE. If NCYCLE per hour for the given load is greater than a threshold number of cycles per hour (NTHRESH), an alarm is initiated. The value of NTHRESH is based on the function of the particular contactor.
Additionally, NCYCLE can be used to predict when maintenance of the associated equipment or contactor should be scheduled. In one example, NTHRESH is associated with the number of cycles after which maintenance is typically required. Therefore, the alarm indicates maintenance is required on the particular piece of equipment the contact is associated with. Alternatively, NCYCLE can be tracked over time to estimate a point in time when it will achieve NTHRESH. A predicative alarm is provided indicating a future point in time when maintenance will be required.
The cycle count for multiple contactors can be monitored. A group alarm can be provided to indicate predicted maintenance requirements for a group of equipment. The groups include equipment whose NCYCLE count will achieve their respective NTHRESH'S within approximately the same time frame. In this manner, the number of maintenance calls is reduced by performing multiple maintenance tasks during a single visit of maintenance personnel.
Referring now to
In step 1710, the algorithm determines whether NCYCLE exceeds NCYCMAX. If NCYCLE does not exceed NCYCLEMAX, the algorithm continues in step 1712. If NCYCLE exceeds NCYCMAX, an alarm is generated in step 1714 and the algorithm continues in step 1712. In step 1712, the algorithm determines whether NCYCRATE exceeds NCYCRATELIM. If NCYCRATE does not exceed NCYCRATELIM, the algorithm loops back to step 1700. If NCYCRATE exceeds NCYCRATELIM, an alarm is generated in step 1716 and the algorithm loops back to step 1700.
The compressor performance algorithm compares a theoretical compressor energy requirement (ETHEO) to an actual measurement of the compressor's energy consumption (EACT). ETHEO is determined based on a model of the compressor. EACT is directly measured from the energy sensors 150. A difference between ETHEO and EACT is determined and compared to a threshold value (ETHRESH). If the absolute value of the difference is greater than ETHRESH an alarm is initiated indicating a fault in compressor performance.
Referring now to
For each compressor rack with at least one compressor running the discharge saturation temperature (TDSAT) is calculated based on Pd. For each compressor running in the rack SH is calculated by subtracting TDSAT from Td. The SH data once each minute for 30 minutes using the pattern analyzer. If the accumulated data indicates an abnormal condition an alarm is generated. Alternatively, Ts and Ps can be monitored and compared to compressor performance curves. For this, a block similar to RPFP and RPFT can be created to perform the performance curve calculations for comparison. Specific deviations from the performance curve would generate maintenance notices.
With particular reference to
Referring now to
In an alternative embodiment, the compressor fault detection algorithm compares the actual Td to a calculated discharge temperature (Tdcalc). Td is measured by the temperature sensors 114 associated with the discharge of each compressor 102. Measurements are taken at approximately 10 second intervals while the compressors 102 are running. Tdcalc is calculated as a function of the refrigerant type, Pd, suction pressure (Ps) and suction temperature (Ts), each of which are measured by the associated sensors described above. An alarm value (A) and time delay (t) are also provided as presets and may be user selected. An alarm is signaled if the difference between the actual and calculated discharge temperature is greater than the alarm value for a time period longer than the time delay. This is governed by the following logic:
Dirt and debris gradually builds up on the condenser coil and condenser fans can fail, impairing condenser performance. As these events occur, condenser performance degrades, inhibiting heat transfer to the atmosphere. The condenser performance algorithm is provided to determine whether the condenser 126 is dirty, which would result in a loss of energy efficiency or more serious system problems. Trend data is analyzed over a specified time period (e.g., several days). More specifically, the average difference between the ambient temperature (Ta) and the condensing temperature (TCOND) is determined over the time period. If the average difference is greater than a threshold (TTHRESH) (e.g., 25° F.) a dirty condenser situation is indicated and a maintenance alarm is initiated. Ta is directly measured from the temperature sensor 128.
Referring specifically to
With particular reference to
where K is a system constant and Io is a calibration value. For example, Io can be set equal to 10% of the current consumption when all condenser fans are on. In step 2106, U is processed through the pattern analyzer and an alarm maybe generated in step 2108 based on the results. As U varies from ideal, condenser performance may be impaired and an alarm message will be generated.
The defrost abnormality algorithm learns the behavior of defrost activity in the refrigeration circuits A, B, C, D. The learned or average defrost behavior is compared to current or past defrost conditions. More specifically, the defrost time (tDEF), maximum defrost time (tDEFMAX) and defrost termination temperature (TTERM) are monitored. If tDEF achieves tDEFMAX for a number of consecutive defrost cycles (NDEF) (e.g., 5 cycles) and the particular case or circuit is set to terminate defrost at TTERM, an abnormal defrost situation is indicated. An alarm is initiated accordingly. The defrost abnormality algorithm also monitors TTERM across cases within a circuit to isolate cases having the highest TTERM.
The case discharge versus product temperature algorithm compares the air discharge temperature (TDISCHARGE) to the case's set point temperature (TSETPOINT) and the product temperature (TPROD) to TDISCHARGE. The case temperature (TCASE) is also monitored. If TDISCHARGE is equal to TSETPOINT, and TPROD is greater than TCASE plus a tolerance temperature (TTOL) a problem with the case is indicated. An alarm is initiated accordingly.
Refrigerant level within the refrigeration system 100 is a function of refrigeration load, ambient temperatures, defrost status, heat reclaim status and refrigerant charge. A reservoir level indicator (not shown) reads accurately when the system is running and stable and it varies with the cooling load. When the system is turned off, refrigerant pools in the coldest parts of the system and the level indicator may provide a false reading. The refrigerant loss detection algorithm determines whether there is leakage in the refrigeration system 100. The liquid refrigerant level in an optional receiver (not shown) is monitored. The receiver would be disposed between the condenser 126 and the individual circuits A, B, C, D. If the liquid refrigerant level in the receiver drops below a threshold level, a loss of refrigerant is indicated and an alarm is initiated.
Referring now to
Referring now to
Referring now to
In step 2612, the algorithm determines whether the duration has expired. If the duration has not yet expired, the algorithm waits for the defined interval in step 2614 and loops back to step 2608. If the duration has expired, the algorithm populates the output table in step 2616. In step 2618, the algorithm determines whether the results are normal. In other words, the algorithm determines whether the population of a each band is below the alarm limit for that band. If the results are normal, messages are cleared in step 2620 and the algorithm ends. If the results are not normal, the algorithm determines whether to generate a notification or an alarm in step 2622. In step 2624, the alarm or notification message(s) is/are generated and the algorithm ends.
The description of the invention is merely exemplary in nature and, thus, variations that do not depart from the gist of the invention are intended to be within the scope of the invention. Such variations are not to be regarded as a departure from the spirit and scope of the invention.
This application claims the benefit of U.S. Provisional Application No. 60/466,637, filed on Apr. 30, 2003. The disclosure of the above application is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4325223 | Cantley | Apr 1982 | A |
4510576 | MacArthur et al. | Apr 1985 | A |
4611470 | Enstrom | Sep 1986 | A |
4630572 | Evans | Dec 1986 | A |
4768346 | Mathur | Sep 1988 | A |
4841734 | Torrence | Jun 1989 | A |
4939909 | Tsuchiyama et al. | Jul 1990 | A |
5181389 | Hanson et al. | Jan 1993 | A |
5209076 | Kauffman et al. | May 1993 | A |
5460006 | Torimitsu | Oct 1995 | A |
5555195 | Jensen et al. | Sep 1996 | A |
5586446 | Torimitsu | Dec 1996 | A |
5802860 | Barrows | Sep 1998 | A |
5875430 | Koether | Feb 1999 | A |
5946922 | Viard et al. | Sep 1999 | A |
6215405 | Handley et al. | Apr 2001 | B1 |
6393848 | Roh et al. | May 2002 | B2 |
6397606 | Roh et al. | Jun 2002 | B1 |
6549135 | Singh et al. | Apr 2003 | B2 |
6609078 | Starling et al. | Aug 2003 | B2 |
20010054291 | Roh et al. | Dec 2001 | A1 |
20020000092 | Sharood et al. | Jan 2002 | A1 |
20020029575 | Okamoto | Mar 2002 | A1 |
20020082924 | Koether | Jun 2002 | A1 |
20020161545 | Starling et al. | Oct 2002 | A1 |
20040144106 | Douglas et al. | Jul 2004 | A1 |
Number | Date | Country |
---|---|---|
1 187 021 | Mar 2002 | EP |
62-116844 | May 1987 | JP |
WO 0214968 | Feb 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20040261431 A1 | Dec 2004 | US |
Number | Date | Country | |
---|---|---|---|
60466637 | Apr 2003 | US |