US 7,290,398 B2Grant
Refrigeration control system
Issue Date:2007-11-06
•56 Claims
•2 Drawing Sheets
Abstract
A refrigeration system and method includes a refrigeration component and an electronics module preconfigured with a data set for the refrigeration component. The electronics module stores the data set including identification and configuration parameters of the refrigeration component. A refrigeration system controller that communicates with the electronics module to copy the data set and to regulate operation of the refrigeration component within the refrigeration system.
Metadata
Assignee
- Computer Process Controls, Inc.
Inventors
- John G. Wallace
- David R. Rohn
- Alan E. Mayne
- Nagaraj Jayanth
- Troy W. Renken
Application Information
Application Number:US 10/925,899
Filing Date:2004-08-25
Priority Date:2003-08-25
Art Unit:3744
Classifications
IPC:
G05D23/32F28D5/00G01K13/00F25B19/00
Patent Drawings (2 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the benefit of U.S. Provisional Application No. 60/497,616, filed on Aug. 25, 2003, the disclosure of which is incorporated herein by reference.
Field of the Invention
[0002] The present invention relates to refrigeration control systems, and more particularly to integrated control and monitoring of refrigeration system compressors.
Background of the Invention
[0003] Refrigeration systems typically include a compressor, a condenser, an expansion valve, and an evaporator, all interconnected to form a fluid circuit. Cooling is accomplished through evaporation of a liquid refrigerant under reduced temperature and pressure. Vapor refrigerant is compressed to increase its temperature and pressure. The vapor refrigerant is condensed in the condenser, lowering its temperature to induce a state change from vapor to liquid.
[0004] The pressure of the liquid refrigerant is reduced through an expansion valve and the liquid refrigerant flows into the evaporator. The evaporator is in heat exchange relationship with a cooled area (e.g., an interior of a refrigeration case). Heat is transferred from the cooled area to the liquid refrigerant inducing a temperature increase sufficient to result in vaporization of the liquid refrigerant. The vapor refrigerant then flows from the evaporator to the compressor.
[0005] The refrigeration system can include multiple evaporators such as in the case of multiple refrigeration cases and multiple compressors connected in parallel in a compressor rack. The multiple compressors can be controlled individually or as a group to provide a desired suction pressure for the refrigeration system.
[0006] A system controller monitors and regulates operation of the refrigeration system based on control algorithms and inputs relating to the various system components. Such inputs include, but are not limited to, the number of compressors operating in the refrigeration system and the details of individual compressors, including compressor capacity and setpoints. During initial assembly of the refrigeration system, these inputs must be manually entered into the memory of the refrigeration controller. If a compressor is replaced, the inputs for the removed compressor must be manually erased from the memory and new inputs for the replacement compressor manually entered into the memory. Such manual entry of the inputs is time consuming and prone to human error.
Summary of the Invention
[0007] Accordingly, the present invention provides a refrigeration system includes a refrigeration component and an electronics module that is attached to the refrigeration component. The electronics module stores a data set including identification and configuration parameters of the refrigeration component. A refrigeration system controller communicates with the electronics module to obtain the data set and to regulate operation of the refrigeration component within the refrigeration system.
[0008] In one feature, the refrigeration component is operable in a normal operating state and is inoperable in a lock-out state. The refrigeration system controller monitors occurrences of the refrigeration component in the lock-out state.
[0009] In still another feature, the refrigeration component communicates initial configuration information to the refrigeration system controller upon assembly of the refrigeration component into the refrigeration system. The initial information includes operating parameters and component identity.
[0010] In yet another feature, the refrigeration component is a compressor. The controller regulates compressor capacity based on rated compressor capacity and current operating conditions of the compressor. The operating conditions include suction pressure, suction temperature, discharge pressure and discharge temperature.
[0011] Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
Brief Description of the Drawings
[0012] The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:
[0013] FIG. 1 is a schematic illustration of a refrigeration system according to the present invention.
Detailed Description of the Preferred Embodiments
[0014] 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.
[0015] Referring now to FIG. 1 , an exemplary refrigeration system 100 includes a plurality of refrigerated food storage cases 102. It will be appreciated that the hereindescribed refrigeration system 100 is merely exemplary in nature. The refrigeration system 100 may vary as particular design requirements dictate.
[0016] As shown, the refrigeration system 100 includes a plurality of compressors 102 piped together with a common suction manifold 106 and a discharge header 108 all positioned within a compressor rack 110. A discharge output 112 of each compressor 102 includes a respective temperature sensor 114. An input 116 to the suction manifold 106 includes both a pressure sensor 118 and a temperature sensor 120. Further, a discharge outlet 122 of the discharge header 108 includes an associated pressure sensor 124.
[0017] The compressor rack 110 compresses refrigerant vapor that is delivered to a condenser 126 where the refrigerant vapor is liquefied at high pressure. The condenser 126 includes an associated ambient temperature sensor 128 and an outlet pressure sensor 130. This high-pressure liquid refrigerant is delivered to a plurality of refrigeration cases 131 by way of piping 132. Each refrigeration case 131 is arranged in separate circuits optionally including multiple refrigeration cases 131 that operate within a certain temperature range. FIG. 1 illustrates four (4) circuits labeled circuit A, circuit B, circuit C and circuit D. Each circuit A, B, C, D is shown to include four (4) refrigeration cases 131. Those skilled in the art, however, will recognize that any number of circuits, as well as any number of refrigeration cases 131 within a circuit, may be included. As indicated, each circuit will generally operate within a certain temperature range. For example, circuit A may be for frozen food, circuit B for dairy, circuit C for meat, and circuit D for produce.
[0018] 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 131. The pressure regulators 134 can be electronically or mechanically controlled. Each refrigeration case 131 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 131. 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 131 moves across the evaporator 136 and cools the refrigerated space, 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. The condenser 126 provides a high pressure liquid that flows to the expansion valve 138, starting the refrigeration cycle again.
[0019] 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 such as an Einstein 2 (E2) controller offered by CPC, Inc. of Atlanta, Ga., U.S.A., 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 electronics module 160, which may include relay switches to turn the compressors 102 on and off to provide the desired suction pressure. A case controller 142, such as a CC-100 case controller, also offered by CPC, Inc. of Atlanta, Ga., U.S.A., may be used to control the superheat of the refrigerant to each refrigeration case 131, via an electronic expansion valve in each refrigeration case 131 by way of a communication network or bus 152. 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 152. The communication bus 152 may operate using any communication protocol, e.g., an 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 131.
[0020] Each refrigeration case 131 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 131. Each refrigeration case 131 in the circuit B may have a separate temperature sensor 146 to take average/minimum/maximum temperatures or a single temperature sensor 146 in one refrigeration case 131 within circuit B may be used to control each refrigeration case 131 in circuit B because all of the refrigeration cases 131 in a given circuit generally operate within a similar temperature range. These temperature inputs are provided to the main refrigeration controller 140 via the communication bus 152.
[0021] Additionally, further sensors can be provided and correspond with each component of the refrigeration system 100 and are in communication with the refrigeration controller 140. Energy sensors 150 are associated with the compressors 104 and condenser 126 of the refrigeration system 100. The energy sensors 150 monitor energy consumption of their respective components and communicate that information to the refrigeration controller 140.
[0022] The refrigeration controller 140 is configured to control and monitor system components such as suction groups, condensers, standard circuits, analog sensors, and digital sensors. The systems are monitored real-time. For suction groups, setpoints, status, capacity percentages, and stage activity for each suction group are displayed by an output of the refrigeration controller 140, such as a display screen 154. For circuits, circuit names, current status, and temperatures are displayed. For condensers, information on discharge setpoint and individual fan states is provided. The refrigeration controller 140 also includes a data table with default operating parameters for most commercially available refrigeration case types. By selecting a known case type, the refrigeration controller 140 automatically configures the default operating parameters, such as the setpoint, the number of defrosts per day and defrost time for the particular case type.
[0023] The compressors 102 include the embedded intelligence boards or electronics modules 160 that communicate compressor and system data to the refrigeration controller 140, as explained in further detail herein. Traditional I/O boards are replaced by the electronics modules 160, which communicate with the refrigeration controller 140. More specifically, the electronics modules 160 perform the I/O functions. The refrigeration controller 140 sends messages to the individual electronics modules 160 to provide control (e.g., compressor ON/OFF or unloader ON/OFF) and receives messages from the electronics modules 160 concerning the status of the electronics module 160 and the corresponding compressor 102.
[0024] The refrigeration controller 140 monitors the operating conditions of the compressors 102 including discharge temperature, discharge pressure, suction pressure and suction temperature. The compressor operating conditions influence the capacity of the individual compressors 102. The refrigeration controller 140 calculates the capacity of each compressor 102 using a compressor model based on the compressor Air-Conditioning and Refrigeration Institute (ARI) coefficients, discharge temperature, discharge pressure, suction pressure and suction temperature. The calculated capacities are then processed through a suction pressure algorithm to determine which compressors 102 to switch on/off to achieve the desired suction pressure.
[0025] Exemplary data received by the refrigeration controller 140 includes the number of compressors 102 in the refrigeration system 100, horsepower of each compressor, method of oil control/monitoring of the compressors, method of proofing the compressors 102 and the I/O points in the refrigeration controller 140 used to control the compressors 102. Much of the data is resident in the electronics module 160 of each of the compressors 102, as described in detail below and is therefore specific to that compressor. Other data is mined by the refrigeration controller 140 and is assembled in a controller database. In this manner, the refrigeration system 140 communicates with the individual electronics modules 160 to automatically populate the controller database and provide an initial system configuration. As a result, time consuming, manual input of these parameters is avoided.
[0026] The electronics module 160 of the individual compressors 102 further includes compressor identification information, such as the model and serial numbers of the associated compressor 102, which is communicated to the refrigeration controller 140. The compressor identification information is described in further detail below. The refrigeration controller 140 populates an asset management database 162 that is resident on a remote computer or server 164. The refrigeration controller 140 communicates with remote computer/server 164 to automatically populate the asset management database 162 with information provided by the electronics module 160. In this manner, the asset management database 162 is continuously updated and the status of each component of the refrigeration system 100 is readily obtainable.
[0027] The compressor data from the electronics module 160 includes compressor identification information and compressor configuration information. The compressor identification information and the compressor configuration information includes, but is not limited to, the information respectively listed in Table 1 and Table 2, below:
[0028]
| TABLE 1 | |
|---|---|
| Compressor Identification Data | |
| Compressor Model Number | Standard compressor model number |
| Compressor Serial Number | Standard compressor serial number |
| Customer ID Code | Standard customer ID code |
| Location | Identifies customer site |
| Application Code | Standard high-temp, med-temp, low-temp |
| Application Temperature | Standard high-temp, med-temp, low-temp |
| Range | |
| Refrigerant Code | Refrigerant type |
| Oil Code | Oil type at time of manufacture |
| Oil Charge | Oil amount at time of manufacture or service |
| System Oil Code | Oil type in customer application |
| Display Unit Present | Indicates that a display is attached |
| Expansion Board Present | Indicates that an expansion board is |
| attached to the base board | |
| Expansion Board ID Code | Type of expansion board |
| Expansion Board Software | Version number of expansion board software |
| or version number of expansion board driver | |
| module for the processor on the base board. | |
| Controller Software | Version number of expansion board |
| software for processor on base board. | |
| Controller Model Number | Controller board part number |
| Compressor Configuration | Provides special configuration status outside |
| Code | the scope of the compressor model number |
[0029]
The compressor data is preconfigured during manufacture (i.e., factory settings) and is retrieved by the refrigeration system controller 140 upon initial connection of the compressor 102 and its corresponding electronics module. The compressor data can be updated with application-specific settings by the refrigeration system controller or by a technician using the refrigeration system controller 140. The updated compressor data is sent back to and is stored in the electronics module 160. In this manner, the preconfigured compressor data can be updated based on the requirements of the specific refrigeration system 100.
| TABLE 2 | |
|---|---|
| Compressor Configuration | |
| Anti Short Cycle Time | Enables additional time over minimum OFF time |
| between cycles. | |
| Discharge Pressure Cut-In | Pressure cut-in limit when operating with a discharge |
| pressure transducer. | |
| Discharge Pressure Cut-Out | Pressure limit when operating with a discharge pressure |
| transducer. | |
| Discharge Temp. Trip Reset Time | Hold period after the discharge temperature probe in the |
| compressor indicates a discharge temperature trip has | |
| cleared. | |
| Discharge Press. Transducer Select | Identifies pressure reading source |
| Suction Press. Transducer Select | Identifies pressure reading source |
| Suction Pressure Cut-Out | Pressure cut-out limit when operating with a suction |
| pressure transducer | |
| Suction Pressure Cut-In | Pressure limit when operating with a suction pressure |
| transducer | |
| Suction Pressure Multiplier3 | Scales transducer reading to proper units. |
| Suction Pressure Divider3 | Scales transducer reading to proper units. |
| Discharge Pressure Multiplier3 | Scales transducer reading to proper units. |
| Discharge Pressure Divider3 | Scales transducer reading to proper units. |
| Shake Limit | Displacement limit to protect the compressor against a |
| shake condition | |
| Oil Add Set Point | Level to add oil |
| Oil Stop Add Set Point | Level to stop adding oil |
| Oil Trip Set Point | Level at which to turn compressor OFF due to lack of |
| lubrication | |
| Oil Add Initial Duty Cycle | Starting point for fill duty cycle in an adaptive algorithm |
| for oil fill | |
| Oil Add Max Duty Cycle | Limit on fill duty cycle for the adaptive algorithm for oil |
| fill. | |
| Enable Reverse Phase Correction | Readout of the signal that originates on the expansion |
| board when a Reverse Phase Correction output module | |
| is used | |
| Oil Level or Pressure Protection Flag | Type of active oil protection is active |
| Motor PTC or NTC | Type of sensors embedded in motor windings |
| Enable Welded Contactor Single | Readout of the signal that originates on the expansion |
| Phase Protection | board when a Single Phase Protection output module is |
| used | |
| Internal or External Line Break | Sets the controller to work with either an internal motor |
| protector or external motor protection via S1-S3 sensors | |
| S1, S2, S3 Configuration | Sets the operation mode of the S1-S3 inputs |
| Enable Discharge Temperature Trip | Enables lockout rather than trip on high discharge |
| Lockout | temperature. |
| S1 Trip Percent | Trip and reset activation points for the S1-S3 sensors |
| S1 Reset Percent | |
| S2 Trip Percent | |
| S2 Reset Percent | |
| S3 Trip Percent | |
| S3 Reset Percent | |
| Enable Discharge Pressure Trip | Enables lockout rather than trip on high discharge |
| Lockout | pressure. |
| Enable Oil Level Trip Lockout | Enables lockout rather than trip on low oil level. |
| Discharge Temperature Probe | Setting (series or separate) used in External Motor |
| Temperature Protection, Discharge Temperature | |
| Protection and Discharge Temperature Control | |
| Liquid Injection Control | Indicates that a Liquid/Vapor Injection output module is |
| used | |
| Discharge Pressure Sensor | Enables or disables the chosen discharge pressure |
| source | |
| Suction Pressure Sensor | Enables or disables the chosen suction pressure source |
| Position X Control | Indicates that an output module is plugged into Position |
| X on the board | |
| Oil Level Control | Indicates that an Oil Level Control output module is |
| used | |
| Discharge Temperature Limit | Discharge temperature cut-out point |
| Discharge Temperature Cut-In | Point below which compressor can be restarted |
| Liquid Inject Temperature | Point above which to start the Liquid/Vapor Injection |
| Liquid Inject Stop Temperature | Point below which to stop injecting Liquid/Vapor |
| TOil Sensor | Enables or disables the given expansion board input |
| TM1 Sensor | |
| TM2 Sensor | |
| TM3 Sensor | |
| TM4 Sensor | |
| T_Spare Sensor | |
| Zero Crossing Detection | Disabled prevents the controller from looking for zero |
| crossings to detect voltage drop-outs | |
| Condensing Fan Control | Sets the control mode for condensing fan |
| Position X Control Source | Sets the control mode for Position X on the expansion |
| board | |
| Modulation Type | Readout of the signal from the expansion board when |
| one or more modulation output module is/are used | |
| Oil Level Sensors | Sets the mode of operation for one or two oil level |
| sensors | |
| Disable Reversed Phase Check | Enables reversed phase detection to be disabled |
| Failsafe Mode | Sets the failsafe mode of the electronics module |
| Crankcase Heat Ontime Lockout | Time to remain OFF after a system power up |
The compressor data is preconfigured during manufacture (i.e., factory settings) and is retrieved by the refrigeration system controller 140 upon initial connection of the compressor 102 and its corresponding electronics module. The compressor data can be updated with application-specific settings by the refrigeration system controller or by a technician using the refrigeration system controller 140. The updated compressor data is sent back to and is stored in the electronics module 160. In this manner, the preconfigured compressor data can be updated based on the requirements of the specific refrigeration system 100.
[0030] The refrigeration controller 140 monitors the compressors 102 for alarm conditions and maintenance activities. One such example is monitoring for compressor oil failure, as described in further detail below. Because the refrigeration controller 140 stores operating history data, it can provide a failure and/or maintenance history for the individual compressors 102 by model and serial number.
[0031] The refrigeration controller 140 is responsible for addressing and providing certain configuration information for the electronics modules 160. This occurs during first power up of the refrigeration system (i.e., finding all electronics modules 160 in the network and providing appropriate address and configuration information for the electronics modules 160), when a previously addressed and configured electronics module 160 is replaced by a new electronics module 160 and when an electronics module 160 is added to the network. During each of these scenarios, the refrigeration controller 140 provides a mapping screen that lists the serial numbers of the electronics modules 160 that are found. The screen will also list the name of each electronics module 160 and the firmware revision information.
[0032] In general, a technician who replaces or adds an electronics module 160 is required to enter a network setup screen in the refrigeration controller 140 and inform the refrigeration controller 140 that an electronics module 160 has been added or deleted from the network. When an electronics module 160 is replaced, the technician enters the network setup screen for the electronics modules 160 and initiates a node recovery. During the node recovery, existing electronics modules 160 retain their setup information and any links that the technician has established to the corresponding suction groups. The results are displayed on the network setup screen. The technician has the capability to delete the old electronics module 160 from the refrigeration controller 140.
[0033] A cell is created in the refrigeration controller 140 to act as an interface to each electronics module 160. The cell contains all inputs, outputs and configuration setpoints that are available on the particular electronics module 160. In addition, the cell contains event information and a text string that represents the current display code on the electronics module 160. The cell data includes status information, configuration information, control data, event data, ID reply data, ID set data and summary data.
[0034] The status information is provided in the form of fields, which include, but is not limited to, display code, compressor running, control voltage low, control voltage dropout, controller failure, compressor locked out, welded contactor, remote run available, discharge temperature, model number, serial number, compressor control contact, liquid injection contact and error condition outputs. The control data enables the technician to set the data that is sent to the electronics module 160 for control. The control data includes, but is not limited to, compressor run request, unloader stage 1 and unloader stage 2. The compressor run request controls the run command to the compressor 102. This is typically tied to a compressor stage in the suction group cell.
[0035] With regard to event data, the refrigeration controller 140 has the capability to retrieve and display all of the event codes and trip information present on the particular electronics module 160. The cell provides correlation between the event code, a text display representing the code and the trip time. The screen will also display the compressor cycle information (including short cycle count) and operational time. The summary data is provided on a summary screen in the refrigeration controller 140 that lists the most important status information for each electronics module 160 and displays all electronics modules.
[0036] Each electronics module 160 can generate a trip event and/or a lockout event. A trip event is generated when an event occurs for a temporary period of time and generally clears itself. An example of a trip occurs when the motor temperature exceeds the a threshold for a period of time. The electronics module 160 generates a motor temperature trip signal and clears the trip when the motor temperature returns to a normal value. A lockout event indicates a condition that is not self clearing (e.g., a single phase lockout).
[0037] The refrigeration controller 140 polls the status of each. electronics module 160 on a regular basis. If the electronics module 160 is in a trip condition, the refrigeration controller 140 logs a trip in an alarm log. Trips are set up as notices in the alarm log. If the electronics module 160 is in a lockout condition, the refrigeration controller 140 generates a lockout alarm in the alarm log. The cell has the capability to set priorities for notices and alarms. It is also anticipated that a lockout can be remotely cleared using the refrigeration controller 140.
[0038] When a technician either resets or otherwise acknowledges an alarm or notice associated with the electronics module 160, the appropriate reset is sent to the electronics module 160 to clear the trip or lockout condition. The trips include, but are not limited to, low oil pressure warning, motor protection, supply voltage, discharge pressure, phase loss, no three phase power, discharge temperature and suction pressure. The lockouts include, but are not limited to low oil pressure, welded contactor, module failure, discharge temperature, discharge pressure and phase loss.
[0039] With particular regard to the low oil pressure lockout, the electronics module 160 communicates the number of oil resets that have been performed to the refrigeration controller 140. If the number of resets exceeds a threshold value, a problem with the refrigeration system 100 may be indicated. The refrigeration controller 140 can send an alarm or initiate maintenance actions based on the number of lockout resets.
[0040] The welded contactor lockout provides each electronics module 160 with the ability to sense when a contactor has welded contacts. It does this by monitoring the voltage applied by the contactor based on whether the electronics module 160 is calling for the contactor to be ON or OFF. If a single phase (or 2 phases) are welded in the contactor and the contactor is inadvertently turned off, this condition can lead to compressor damage. It also affects the ability of the suction pressure control algorithm since the refrigeration controller 140 could be calling for the compressor 102 to be OFF, but the compressor continues to run. To mitigate the problems caused by this condition, the suction pressure algorithm in the refrigeration controller 140 is adapted to recognize this condition via the electronics module 160. When a welded contactor condition is detected, the associated compressor 102 is held ON by the suction group algorithm and the appropriate alarm condition is generated, which avoids damage to the compressor motor.
[0041] The technician can readily connect an electronics module equipped compressor 102 into a suction group. All pertinent connections between the electronics module 160 and suction group cells are automatically established upon connection of the compressor 102. This includes the type (e.g., compressor or unloader), compressor board/point (i.e., application/cell/output) and proof of board/point. A screen similar to the mapping screen enables the technician to pick which electronics modules 160 belong to a suction group.
[0042] It is further anticipated that additional features can be incorporated into the refrigeration system 100. One feature includes an electronics module/refrigeration controller upload/download, which provides the capability to save the parameters from an electronics module 160 to the refrigeration controller 140. If the saved electronics module 160 is replaced, the parameters are downloaded to the new electronics module 160, making it easier to replace an electronics module in the field.
[0043] Another feature includes cell data breakout, which provides a discrete cell output for each trip or alarm condition. The cell output would enable these conditions to be connected to other cell's for analysis or other actions. For example, the discharge temperature lockout status from multiple electronics modules 160 could be connected to a super-cell that reviews the status and diagnoses a maintenance action based on how many electronics modules 160 have a discharge temperature trip and the relative timing of the trips.
[0044] Still another feature includes an automatic reset of the lockout conditions in the event of a lockout. More specifically, the refrigeration controller 140 automatically attempts a reset of a lockout condition (e.g., an oil failure lockout) when the condition occurs. If the reset attempt repeatedly fails, an alarm would then be generated.
[0045] Yet another feature includes phase monitor replacement. More specifically, a phase monitor is traditionally installed in a compressor rack. The electronics modules 160 can be configured to generate a phase monitor signal, removing the need for a separate phase monitor. If all the electronics modules 160 on a given rack signal a phase loss, a phase loss on the rack is indicated and an alarm is generated.
[0046] 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.
Claims
What is claimed is:
1. A method comprising:
preconfiguring a data set for a refrigeration component, said data set including identification and configuration parameters of said refrigeration component;
storing said data set in an electronics module associated with said refrigeration component;
copying said data set to a refrigeration system controller in communication with said electronics module;
initially configuring a refrigeration system based on said copied data set; and
monitoring an occurrence of one of a trip state and a lockout state of said refrigeration component set by said electronics module.
2. The method of claim 1 further comprising generating an updated data set based on said data set and storing said updated data set in said electronics module.
3. The method of claim 1 wherein said initially configuring a refrigeration system includes communicating said data set for said refrigeration component to said refrigeration system controller upon assembly of said refrigeration component into said refrigeration system.
4. The method of claim 1 further comprising copying at least a portion of said data set to an asset management database from said refrigeration system controller.
5. The method of claim 1 further comprising replacing said electronics module with a replacement electronics module and copying said data set for said electronics module to said replacement electronics module.
6. The method of claim 1 further comprising providing a graphical display of a layout of said refrigeration system including identification information of said electronics module.
7. The method of claim 1 further comprising generating a cell associated with said electronics module, wherein said cell includes inputs, outputs and configuration setpoints related to said refrigeration component.
8. The method of claim 1 further comprising regulating operation of said refrigeration component based on said data set.
9. The method of claim 1 further comprising initiating said lockout state based on one of a voltage and a current condition to said refrigeration component.
10. The method of claim 9 further comprising indicating a welded electrical contact based on said voltage and said current condition.
11. The method of claim 1 further comprising temporarily suspending operation of said refrigeration component until said trip state clears.
12. The method of claim 1 further comprising suspending operation of said refrigeration component until said lockout state is reset.
13. The method of claim 12 further comprising resetting said lockout state by said refrigeration system controller.
14. The method of claim 1 further comprising logging one of said trip state and said lockout state with an associated timestamp.
15. The method of claim 1 further comprising monitoring occurrences of each of said trip state and lockout state.
16. The method of claim 15 further comprising initiating an alarm when one of said trip state and said lockout state has occurred a threshold number of times.
17. The method of claim 1 further comprising basing said trip state on one of a low pressure, a motor temperature, an electronics module voltage supply, a discharge pressure, a phase loss, a discharge temperature and a suction pressure.
18. The method of claim 1 further comprising basing said lockout state on one of a low oil pressure, a welded contactor, an electronics module failure, a discharge temperature, a discharge pressure and a phase loss.
19. In a refrigeration system, a refrigeration component associated with an electronics module including a memory storing a data set specific to said refrigeration component, said data set including identification parameters and configuration parameters of said refrigeration component, a refrigeration system controller in communication with said electronics module to copy said data set from said electronics module and regulate operation of said refrigeration component within said refrigeration system based on said data set, said refrigeration system controller monitoring occurrences of said refrigeration component in one of a trip state and a lockout state.
20. The system of claim 19 wherein said refrigeration system controller is operable to generate an updated data set and transmit said updated data set to said memory of said electronics module.
21. The system of claim 19 wherein said refrigeration system controller is operable to initiate remedial action when said refrigeration component is in said lockout state.
22. The system of claim 21 wherein said remedial action includes at least one of attempting to reset said lock-out state and triggering an alarm if said reset fails.
23. The system of claim 19 wherein said electronics module is operable to communicate said data set to said refrigeration system controller upon assembly of said refrigeration component into a refrigeration system.
24. The system of claim 19 further comprising an asset management database, wherein said refrigeration system controller is operable to update an asset management database based on said data set.
25. The system of claim 19 wherein said refrigeration system controller is operable to query a replacement electronics module that replaces said electronics module upon association of said replacement electronics module with said refrigeration component.
26. The system of claim 25 wherein a replacement data set from said refrigeration system controller is stored in a memory of said replacement electronics module.
27. The system of claim 26 wherein said replacement data set is a copy of said data set from said electronics module being replaced.
28. The system of claim 19 further comprising a display screen associated with said refrigeration system controller and providing a graphical display of a layout of the refrigeration system, including identification information of said refrigeration component.
29. The system of claim 19 wherein said refrigeration system controller generates a cell associated with said electronics module, wherein said cell includes inputs, outputs and configuration setpoints related to said refrigeration component associated with said respective electronics module.
30. The system of claim 19 wherein said electronics module initiates one of a trip event and a lockout event based on an operating condition of said refrigeration component.
31. The system of claim 30 wherein said lockout event indicates potential damage to said refrigeration component and is initiated based on one of a voltage and a current condition to said refrigeration component.
32. The system of claim 31 wherein said one of a voltage and a current condition indicate a welded electrical contact.
33. The system of claim 30 wherein said refrigeration system controller temporarily suspends operation of said refrigeration component during said trip event until a trip condition clears.
34. The system of claim 30 wherein said refrigeration system controller suspends operation of said refrigeration component during said lockout event until a lockout condition is reset.
35. The system of claim 34 wherein said refrigeration system controller is operable to reset said lockout condition.
36. The system of claim 30 wherein said refrigeration system controller is operable to log said trip events and said lockout events and record an associated timestamp.
37. The system of claim 30 wherein said refrigeration controller is operable to monitor occurrences of each of said trip and lockout events and initiate an alarm when at least one of said trip and lockout events has occurred a threshold number of times.
38. The system of claim 30 wherein said trip event is based on at least one of a low pressure, a motor temperature, an electronics module voltage supply, a discharge pressure, a phase loss, a discharge temperature and a suction pressure.
39. The system of claim 30 wherein said lockout event is based on at least one of a low oil pressure, a welded contactor, an electronics module failure, a discharge temperature, a discharge pressure and a phase loss.
40. The system of claim 19 further comprising a plurality of refrigeration components and a plurality of electronics modules, each said electronics module associated with one of said plurality of refrigeration components, said memory of each of said electronics modules storing said data set including identification and configuration parameters of a respective refrigeration component, and wherein said refrigeration system controller receives said data sets from each of said electronics modules and regulates operation of each of said refrigeration components within said refrigeration system.
41. The system of claim 40 wherein each of said electronics modules communicates its respective data set to said refrigeration system controller upon assembly of said associated refrigeration component into said refrigeration system.
42. The system of claim 40 wherein said refrigeration system controller queries a replacement electronics module that replaces one of said electronics modules upon connection of said replacement electronics module into said refrigeration system.
43. The system of claim 42 wherein said refrigeration system controller generates a replacement data set and said replacement data set is stored in a memory of said replacement electronics module.
44. The system of claim 42 wherein said replacement data set is a copy of said data set from said electronics module being replaced.
45. The system of claim 40 wherein said refrigeration system controller generates a cell associated with each of said electronics modules, wherein said cell includes inputs, outputs and configuration setpoints related to said refrigeration component.
46. The system of claim 40 wherein said refrigeration system controller regulates operation of each of said refrigeration components based on said respective data set.
47. In a refrigeration system, a refrigeration component associated with an electronics module including a memory storing a data set specific to said refrigeration component, said data set including identification parameters and configuration parameters of said refrigeration component, a refrigeration system controller in communication with said electronics module to copy said data set from said electronics module and regulate operation of said refrigeration component within said refrigeration system based on said data set, said electronics module initiating one of a trip event and a lockout event based on an operating condition of said refrigeration component.
48. The system of claim 47 wherein said lockout event indicates potential damage to said refrigeration component and is initiated based on one of a voltage and a current condition to said refrigeration component.
49. The system of claim 48 wherein said one of a voltage and a current condition indicate a welded electrical contact.
50. The system of claim 47 wherein said refrigeration system controller temporarily suspends operation of said refrigeration component during said trip event until a trip condition clears.
51. The system of claim 47 wherein said refrigeration system controller suspends operation of said refrigeration component during said lockout event until a lockout condition is reset.
52. The system of claim 51 wherein said refrigeration system controller is operable to reset said lockout condition.
53. The system of claim 47 wherein said refrigeration system controller is operable to log said trip events and said lockout events and record an associated timestamp.
54. The system of claim 47 wherein said refrigeration controller is operable to monitor occurrences of each of said trip and lockout events and initiate an alarm when at least one of said trip and lockout events has occurred a threshold number of times.
55. The system of claim 47 wherein said trip event is based on at least one of a low pressure, a motor temperature, an electronics module voltage supply, a discharge pressure, a phase loss, a discharge temperature and a suction pressure.
56. The system of claim 47 wherein said lockout event is based on at least one of a low oil pressure, a welded contactor, an electronics module failure, a discharge temperature, a discharge pressure and a phase loss.
Patent Citations (264)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2296822(A) | 1942-09-01 | Wolfert | Applicant |
| US3232519(A) | 1966-02-01 | Long | Applicant |
| US3513662(A) | 1970-05-01 | Golber | Applicant |
| US3585451(A) | 1971-06-01 | Day | Applicant |
| US3653783(A) | 1972-04-01 | Sauder | Applicant |
| US3735377(A) | 1973-05-01 | Kaufman | Applicant |
| US3767328(A) | 1973-10-01 | Ladusaw | Applicant |
| US3783681(A) | 1974-01-01 | Hirt et al. | Applicant |
| US3924972(A) | 1975-12-01 | Szymaszek | Applicant |
| US4060716(A) | 1977-11-01 | Pekrul et al. | Applicant |
| US4090248(A) | 1978-05-01 | Swanson et al. | Applicant |
| US4102150(A) | 1978-07-01 | Kountz | Applicant |
| US4102394(A) | 1978-07-01 | Botts | Applicant |
| US4112703(A) | 1978-09-01 | Kountz | Applicant |
| US4132086(A) | 1979-01-01 | Kountz | Applicant |
| US4151725(A) | 1979-05-01 | Kountz et al. | Applicant |
| US4281358(A) | 1981-07-01 | Plouffe et al. | Applicant |
| US4345162(A) | 1982-08-01 | Hammer et al. | Applicant |
| US4372119(A) | 1983-02-01 | Gillbrand et al. | Applicant |
| US4384462(A) | 1983-05-01 | Overman et al. | Applicant |
| US4390321(A) | 1983-06-01 | Langlois et al. | Applicant |
| US4390922(A) | 1983-06-01 | Pelliccia | Applicant |
| US4399548(A) | 1983-08-01 | Castleberry | Applicant |
| US4420947(A) | 1983-12-01 | Yoshino | Applicant |
| US4425010(A) | 1984-01-01 | Bryant et al. | Applicant |
| US4429578(A) | 1984-02-01 | Darrel et al. | Applicant |
| US4434390(A) | 1984-02-01 | Elms | Applicant |
| US4463576(A) | 1984-08-01 | Burnett et al. | Applicant |
| US4467613(A) | 1984-08-01 | Behr et al. | Applicant |
| US4470092(A) | 1984-09-01 | Lombardi | Applicant |
| US4479389(A) | 1984-10-01 | Anderson, III et al. | Applicant |
| US4494383(A) | 1985-01-01 | Nagatomo et al. | Applicant |
| US4497031(A) | 1985-01-01 | Froehling et al. | Applicant |
| US4502842(A) | 1985-03-01 | Currier et al. | Applicant |
| US4502843(A) | 1985-03-01 | Martin | Applicant |
| US4505125(A) | 1985-03-01 | Baglione | Applicant |
| US4506518(A) | 1985-03-01 | Yoshikawa et al. | Applicant |
| US4510576(A) | 1985-04-01 | MacArthur et al. | Applicant |
| US4520674(A) | 1985-06-01 | Canada et al. | Applicant |
| US4540040(A) | 1985-09-01 | Fukumoto et al. | Applicant |
| US4555910(A) | 1985-12-01 | Sturges | Applicant |
| US4563878(A) | 1986-01-01 | Baglione | Applicant |
| US4575318(A) | 1986-03-01 | Blain | Applicant |
| US4580947(A) | 1986-04-01 | Shibata et al. | Applicant |
| US4604036(A) | 1986-08-01 | Sutou et al. | Applicant |
| US4614089(A) | 1986-09-01 | Dorsey | Applicant |
| US4630670(A) | 1986-12-01 | Wellman et al. | Applicant |
| US4653280(A) | 1987-03-01 | Hansen et al. | Applicant |
| US4655688(A) | 1987-04-01 | Bohn et al. | Applicant |
| US4660386(A) | 1987-04-01 | Hansen et al. | Applicant |
| US4715792(A) | 1987-12-01 | Nishizawa et al. | Applicant |
| US4755957(A) | 1988-07-01 | White et al. | Applicant |
| US4787213(A) | 1988-11-01 | Gras et al. | Applicant |
| US4798055(A) | 1989-01-01 | Murray et al. | Applicant |
| US4831560(A) | 1989-05-01 | Zaleski | Applicant |
| US4831832(A) | 1989-05-01 | Alsenz | Applicant |
| US4838037(A) | 1989-06-01 | Wood | Applicant |
| US4856286(A) | 1989-08-01 | Sulfstede et al. | Applicant |
| US4877382(A) | 1989-10-01 | Caillat et al. | Applicant |
| US4881184(A) | 1989-11-01 | Abegg, III et al. | Applicant |
| US4882747(A) | 1989-11-01 | Williams | Applicant |
| US4884412(A) | 1989-12-01 | Sellers et al. | Applicant |
| US4885707(A) | 1989-12-01 | Nichol et al. | Applicant |
| US4904993(A) | 1990-02-01 | Sato | Applicant |
| US4909076(A) | 1990-03-01 | Busch et al. | Applicant |
| US4913625(A) | 1990-04-01 | Gerlowski | Applicant |
| US4928750(A) | 1990-05-01 | Nurczyk | Applicant |
| US4949550(A) | 1990-08-01 | Hanson | Applicant |
| US4964060(A) | 1990-10-01 | Hartsog | Applicant |
| US4974427(A) | 1990-12-01 | Diab | Applicant |
| US4985857(A) | 1991-01-01 | Bajpai et al. | Applicant |
| US5009074(A) | 1991-04-01 | Goubeaux et al. | Applicant |
| US5018357(A) | 1991-05-01 | Livingstone et al. | Applicant |
| US5022234(A) | 1991-06-01 | Goubeaux et al. | Applicant |
| US5051720(A) | 1991-09-01 | Kittirutsunetorn | Applicant |
| US5056036(A) | 1991-10-01 | Van Bork | Applicant |
| US5058388(A) | 1991-10-01 | Shaw et al. | Applicant |
| US5071065(A) | 1991-12-01 | Aalto et al. | Applicant |
| US5073862(A) | 1991-12-01 | Carlson | Applicant |
| US5076067(A) | 1991-12-01 | Prenger et al. | Applicant |
| US5086385(A) | 1992-02-01 | Launey et al. | Applicant |
| US5088297(A) | 1992-02-01 | Maruyama et al. | Applicant |
| US5099654(A) | 1992-03-01 | Baruschke et al. | Applicant |
| US5109222(A) | 1992-04-01 | Welty | Applicant |
| US5109700(A) | 1992-05-01 | Hicho | Applicant |
| US5115406(A) | 1992-05-01 | Zatezalo et al. | Applicant |
| US5119466(A) | 1992-06-01 | Suzuki | Applicant |
| US5131237(A) | 1992-07-01 | Valbjorn | Applicant |
| US5156539(A) | 1992-10-01 | Anderson et al. | Applicant |
| US5181389(A) | 1993-01-01 | Hanson et al. | Applicant |
| US5203178(A) | 1993-04-01 | Shyu | Applicant |
| US5203179(A) | 1993-04-01 | Powell | Applicant |
| US5209076(A) | 1993-05-01 | Kauffman et al. | Applicant |
| US5209400(A) | 1993-05-01 | Winslow et al. | Applicant |
| US5224835(A) | 1993-07-01 | Oltman | Applicant |
| US5226472(A) | 1993-07-01 | Benevelli et al. | Applicant |
| US5243827(A) | 1993-09-01 | Hagita et al. | Applicant |
| US5265434(A) | 1993-11-01 | Alsenz | Applicant |
| US5279458(A) | 1994-01-01 | DeWolf et al. | Applicant |
| US5282728(A) | 1994-02-01 | Swain | Applicant |
| US5284026(A) | 1994-02-01 | Powell | Applicant |
| US5299504(A) | 1994-04-01 | Abele | Applicant |
| US5303560(A) | 1994-04-01 | Hanson et al. | Applicant |
| US5311451(A) | 1994-05-01 | Barrett | Applicant |
| US5316448(A) | 1994-05-01 | Ziegler et al. | Applicant |
| US5335507(A) | 1994-08-01 | Powell | Applicant |
| US5362206(A) | 1994-11-01 | Westerman et al. | Applicant |
| US5381692(A) | 1995-01-01 | Winslow et al. | Applicant |
| US5415008(A) | 1995-05-01 | Bessler | Applicant |
| US5416781(A) | 1995-05-01 | Ruiz | Applicant |
| US5423190(A) | 1995-06-01 | Friedland | Applicant |
| US5423192(A) | 1995-06-01 | Young et al. | Applicant |
| US5426952(A) | 1995-06-01 | Bessler | Applicant |
| US5431026(A) | 1995-07-01 | Jaster | Applicant |
| US5435145(A) | 1995-07-01 | Jaster | Applicant |
| US5440890(A) | 1995-08-01 | Bahel et al. | Applicant |
| US5440891(A) | 1995-08-01 | Hindmon, Jr. et al. | Applicant |
| US5440895(A) | 1995-08-01 | Bahel et al. | Applicant |
| US5446677(A) | 1995-08-01 | Jensen et al. | Applicant |
| US5450359(A) | 1995-09-01 | Sharma et al. | Applicant |
| US5452291(A) | 1995-09-01 | Eisenhandler et al. | Applicant |
| US5454229(A) | 1995-10-01 | Hanson et al. | Applicant |
| US5460006(A) | 1995-10-01 | Torimitsu | Applicant |
| US5467264(A) | 1995-11-01 | Rauch et al. | Applicant |
| US5481481(A) | 1996-01-01 | Frey et al. | Applicant |
| US5483141(A) | 1996-01-01 | Uesugi | Applicant |
| US5509786(A) | 1996-04-01 | Mizutani et al. | Applicant |
| US5511387(A) | 1996-04-01 | Tinsler | Applicant |
| US5519301(A) | 1996-05-01 | Yoshida et al. | Applicant |
| US5528908(A) | 1996-06-01 | Bahel et al. | Applicant |
| US5546756(A) | 1996-08-01 | Ali | Applicant |
| US5546757(A) | 1996-08-01 | Whipple, III | Applicant |
| US5548966(A) | 1996-08-01 | Tinsler | Applicant |
| US5570085(A) | 1996-10-01 | Bertsch | Applicant |
| US5570258(A) | 1996-10-01 | Manning | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5596507(A) | 1997-01-01 | Jones et al. | Applicant |
| US5602757(A) | 1997-02-01 | Haseley et al. | Applicant |
| US5610339(A) | 1997-03-01 | Haseley et al. | Applicant |
| US5630325(A) | 1997-05-01 | Bahel et al. | Applicant |
| US5641270(A) | 1997-06-01 | Sgourakes et al. | Applicant |
| US5655379(A) | 1997-08-01 | Jaster et al. | Applicant |
| US5655380(A) | 1997-08-01 | Calton | Applicant |
| US5694010(A) | 1997-12-01 | Oomura et al. | Applicant |
| US5707210(A) | 1998-01-01 | Ramsey et al. | Applicant |
| US5713724(A) | 1998-02-01 | Centers et al. | Applicant |
| US5715704(A) | 1998-02-01 | Cholkeri et al. | Applicant |
| US5741120(A) | 1998-04-01 | Bass et al. | Applicant |
| US5743109(A) | 1998-04-01 | Schulak | Applicant |
| US5752385(A) | 1998-05-01 | Nelson | Applicant |
| US5875430(A) | 1999-02-01 | Koether | Applicant |
| US5875638(A) | 1999-03-01 | Tinsler | Applicant |
| US5900801(A) | 1999-05-01 | Heagle et al. | Applicant |
| US5904049(A) | 1999-05-01 | Jaster et al. | Applicant |
| US5924295(A) | 1999-07-01 | Park | Applicant |
| US5939974(A) | 1999-08-01 | Heagle et al. | Applicant |
| US5946922(A) | 1999-09-01 | Viard et al. | Applicant |
| US5947693(A) | 1999-09-01 | Yang | Applicant |
| US5953490(A) | 1999-09-01 | Wiklund et al. | Applicant |
| US5956658(A) | 1999-09-01 | McMahon | Applicant |
| US5975854(A) | 1999-11-01 | Culp, III et al. | Applicant |
| US5984645(A) | 1999-11-01 | Cummings | Applicant |
| US6006171(A) | 1999-12-01 | Vines et al. | Applicant |
| US6035661(A) | 2000-03-01 | Sunaga et al. | Applicant |
| US6038871(A) | 2000-03-01 | Gutierrez et al. | Applicant |
| US6047557(A) | 2000-04-01 | Pham et al. | Applicant |
| US6081750(A) | 2000-06-01 | Hoffberg et al. | Applicant |
| US6098893(A) | 2000-08-01 | Berglund et al. | Applicant |
| US6125642(A) | 2000-10-01 | Seener et al. | Applicant |
| US6129527(A) | 2000-10-01 | Donahoe et al. | Applicant |
| US6153993(A) | 2000-11-01 | Oomura et al. | Applicant |
| US6176686(B1) | 2001-01-01 | Wallis et al. | Applicant |
| US6179214(B1) | 2001-01-01 | Key et al. | Applicant |
| US6191545(B1) | 2001-02-01 | Kawabata et al. | Applicant |
| US6213731(B1) | 2001-04-01 | Doepker et al. | Applicant |
| US6215405(B1) | 2001-04-01 | Handley et al. | Applicant |
| US6240733(B1) | 2001-06-01 | Brandon et al. | Applicant |
| US6240736(B1) | 2001-06-01 | Fujita et al. | Applicant |
| US6244061(B1) | 2001-06-01 | Takagi et al. | Applicant |
| US6266968(B1) | 2001-07-01 | Redlich | Applicant |
| US6276901(B1) | 2001-08-01 | Farr et al. | Applicant |
| US6290043(B1) | 2001-09-01 | Ginder et al. | Applicant |
| US6324854(B1) | 2001-12-01 | Jayanth | Applicant |
| US6378315(B1) | 2002-04-01 | Gelber et al. | Applicant |
| US6393848(B2) | 2002-05-01 | Roh et al. | Applicant |
| US6397606(B1) | 2002-06-01 | Roh et al. | Applicant |
| US6453687(B2) | 2002-09-01 | Sharood et al. | Applicant |
| US6471486(B1) | 2002-10-01 | Centers et al. | Applicant |
| US6502409(B1) | 2003-01-01 | Gatling et al. | Applicant |
| US6526766(B1) | 2003-03-01 | Hiraoka et al. | Applicant |
| US6553774(B1) | 2003-04-01 | Ishio et al. | Applicant |
| US6601397(B2) | 2003-08-01 | Pham et al. | Applicant |
| US6609078(B2) | 2003-08-01 | Starling et al. | Applicant |
| US6662584(B1) | 2003-12-01 | Whiteside | Applicant |
| US6675591(B2) | 2004-01-01 | Singh et al. | Applicant |
| US6892546(B2) | 2005-05-01 | Singh et al. | Applicant |
| US6996441(B1) | 2006-02-01 | Tobias | Applicant |
| US7024870(B2) | 2006-04-01 | Singh et al. | Applicant |
| US2001/0025349(A1) | 2001-09-01 | Sharood et al. | Applicant |
| US2001/0054291(A1) | 2001-12-01 | Roh et al. | Applicant |
| US2002/0000092(A1) | 2002-01-01 | Sharood et al. | Applicant |
| US2002/0020175(A1) | 2002-02-01 | Street et al. | Examiner |
| US2002/0029575(A1) | 2002-03-01 | Okamoto | Applicant |
| US2002/0082924(A1) | 2002-06-01 | Koether | Applicant |
| US2002/0118106(A1) | 2002-08-01 | Brenn | Applicant |
| US2002/0161545(A1) | 2002-10-01 | Starling et al. | Applicant |
| US2002/0163436(A1) | 2002-11-01 | Singh et al. | Applicant |
| US2004/0239266(A1) | 2004-12-01 | Lee et al. | Applicant |
| US2004/0261431(A1) | 2004-12-01 | Singh et al. | Applicant |
| US2005/0204756(A1) | 2005-09-01 | Dobmeier et al. | Applicant |
| CH173493 | 1934-11-01 | Applicant | |
| DE842351 | 1952-06-01 | Applicant | |
| DE764179 | 1953-04-01 | Applicant | |
| DE1144461 | 1963-02-01 | Applicant | |
| DE1403516 | 1968-10-01 | Applicant | |
| DE1403467 | 1969-09-01 | Applicant | |
| DE3133502 | 1982-06-01 | Applicant | |
| DE3422398 | 1985-12-01 | Applicant | |
| EP85246 | 1983-08-01 | Applicant | |
| EP254253 | 1988-01-01 | Applicant | |
| EP351833 | 1989-07-01 | Applicant | |
| EP410330 | 1991-01-01 | Applicant | |
| EP419857 | 1991-04-01 | Applicant | |
| EP453302(A1) | 1991-10-01 | Applicant | |
| EP479421 | 1992-04-01 | Applicant | |
| EP557023 | 1993-08-01 | Applicant | |
| EP579374(A1) | 1994-01-01 | Applicant | |
| EP660213(A2) | 1995-06-01 | Applicant | |
| EP747598(A2) | 1996-12-01 | Applicant | |
| EP877462(A2) | 1998-11-01 | Applicant | |
| EP982497(A1) | 2000-03-01 | Applicant | |
| EP1087142 | 2001-03-01 | Applicant | |
| EP1138949 | 2001-10-01 | Applicant | |
| EP1139037 | 2001-10-01 | Applicant | |
| EP1187021(A2) | 2002-03-01 | Applicant | |
| EP1209427(A1) | 2002-05-01 | Applicant | |
| EP1241417(A1) | 2002-09-01 | Applicant | |
| FR2582430 | 1986-11-01 | Applicant | |
| FR2589561 | 1987-07-01 | Applicant | |
| FR2628558 | 1989-09-01 | Applicant | |
| FR2660739 | 1991-10-01 | Applicant | |
| GB2062919(A) | 1981-05-01 | Applicant | |
| GB2064818 | 1981-06-01 | Applicant | |
| GB2116635 | 1983-09-01 | Applicant | |
| JP56-10639 | 1981-03-01 | Applicant | |
| JP59-145392 | 1984-08-01 | Applicant | |
| JP61-046485 | 1986-03-01 | Applicant | |
| JP2110242 | 1990-04-01 | Applicant | |
| JP2294580 | 1990-12-01 | Applicant | |
| JP4080578 | 1992-03-01 | Applicant | |
| JP6058273 | 1994-03-01 | Applicant | |
| JP8-284842 | 1996-10-01 | Applicant | |
| JP2005241089 | 2005-09-01 | Applicant | |
| JP2005345096 | 2005-12-01 | Applicant | |
| WO8601262 | 1986-02-01 | Applicant | |
| WO8703988 | 1987-07-01 | Applicant | |
| WO8802527 | 1988-04-01 | Applicant | |
| WO9718636 | 1997-05-01 | Applicant | |
| WO9917066 | 1999-04-01 | Applicant | |
| WO2/14968 | 2002-02-01 | Applicant | |
| WO2/090840 | 2002-11-01 | Applicant | |
| WO2/090913 | 2002-11-01 | Applicant | |
| WO2005/022049 | 2005-03-01 | Applicant | |
| WO2006/091521 | 2006-08-01 | Applicant |
Non-Patent Literature (20)
- European Search Report for EP 01 30 1752; Mar. 26, 2002; 4 Pages.Applicant
- European Search Report for EP 82306809.3; Apr. 28, 1983; 1 Page.Applicant
- European Search Report for EP 91 30 3518; Jul. 22, 1991; 1 Page.Applicant
- European Search Report for EP 01 30 7547; Feb. 20, 2002; 1 Page.Applicant
- European Search Report for EP 96 30 4219; Dec. 1, 1998; 2 Pages.Applicant
- European Search Report for EP 99 30 6052; Dec. 28, 1999; 3 Pages.Applicant
- European Search Report for EP 94 30 3484; Apr. 3, 1997; 1 Page.Applicant
- European Search Report for EP 93 30 4470; Oct. 26, 1993; 1 Page.Applicant
- European Search Report for EP 02 25 0266; May 17, 2002; 3 Pages.Applicant
- European Search Report for EP 98 30 3525; May 28, 1999; 2 Pages.Applicant
- International Search Report; International Application No. PCT/IB96/01435; May 23, 1997; 1 Page.Applicant
- International Search Report; International Application No. PCT/US98/18710; Jan. 26, 1999; 1 Page.Applicant
- First Office Action from the Patent Office of the People's Republic of China dated Jun. 8, 2007, Application No. 200480027753.6.Applicant
- Translation of the First Office Action from the Patent Office of the People's Republic of China dated Jun. 8, 2007. Application No. 200480027753.6 (provided by CCPIT Patent and Trademark Law Office).Applicant
- International Search Report, International Application No. PCT/US2006/040964, dated Feb. 15, 2007, 2 Pages.Applicant
- European Search Report for EP 02 73 1544, Jun. 18, 2004, 2 Pages.Applicant
- European Search Report for EP 02 72 9050, Jun. 17, 2004, 2 Pages.Applicant
- International Search Report, International Application No. PCT/US02/13456, dated Aug. 22, 2002, 2 Pages.Applicant
- International Search Report, International Application No. PCT/US2004/027654, dated Aug. 25, 2004, 4 Pages.Applicant
- Pin Carmen, Baranyi Jozsef, Predictive Models as Means to Quantify the Interactions of Spoilage Organisms, International Journal of Food Microbiology, ol. 41, No. 1, 1998, pp. 59-72, XP-002285119.Applicant