Coolant distribution unit control system

Abstract

A method of operating a coolant distribution unit, the method comprising: receiving measurements from a plurality of sensors; comparing each of the received measurement values, and comparing each of the received measurement values with each of the received measurement values; based on the comparison, determining whether a subset of the received measurements differ from a majority of the received other measurements by more than a predetermined threshold; in response to determining that no one of the received measurements differs from a majority of the other received measurements by more than the predetermined threshold, generating an average measurement from all the received measurements; in response to determining that the subset of the received measurements differ from a majority of the received other measurements by more than the predetermined threshold, generating an average measurement from the received measurements that do not include the subset of the measurements; and operating the component in accordance with the average measurement.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 709,257, filed October 18, 2024, and U.S. Provisional Patent Application No. 63 / 709,247, filed October 18, 2024, the entire contents of each of which are incorporated herein by reference. Background Technology

[0003] Computer systems / data centers employ various cooling / heat dissipation methods to maintain environmental conditions suitable for the operation of information technology (IT) equipment, such as servers, network switches, routers, storage devices, and other computing hardware. Some data centers may utilize liquid cooling systems, where a liquid coolant is used to absorb heat generated from high-power equipment.

[0004] The liquid cooling system includes one or more coolant distribution units (CDUs) configured to actively distribute liquid coolant to various components within the data center. Each CDU includes a primary flow loop / return and a secondary flow loop / return. The primary flow loop / return is configured to supply liquid coolant to the heat-absorbing side of a heat exchange technology (e.g., a liquid-to-liquid heat exchanger) located within or outside the CDU itself. The secondary flow loop / return is configured to receive heated (“used”) liquid coolant at the heat-dissipating side of the heat exchange technology and return cooled liquid coolant to the equipment's liquid cooling network. Within the cooling network of the secondary flow loop, liquid coolant is supplied via one or more feed lines to cooling modules (e.g., single or series of cooling plates or radiators) near or within the IT equipment, absorbing heat from the equipment through these feed lines. The heated liquid coolant then flows through one or more return feed lines across the heat-dissipating side of the heat exchange technology within or outside the CDU, thereby dissipating heat from the liquid coolant. The cooled liquid coolant is then recirculated back to the information technology equipment via one or more feed lines.

[0005] Within the primary flow loop, the used liquid coolant from the heat exchange technology is cooled by one or more secondary cooling methods (e.g., coolers, cooling towers, etc.). The cooled liquid coolant is then recirculated back through the heat dissipation side of the heat exchange technology.

[0006] The Cooling Duct (CDU) operates via a pump system that circulates liquid coolant through a network of pipes or channels. The CDU integrates additional components such as valves, filters, and monitoring mechanisms to optimize cooling efficiency and system reliability. Precisely calibrated valves allow for dynamic coolant distribution adjustments tailored to the needs of individual equipment / components, while filters (e.g., within the primary flow loop) remove impurities and contaminants. Equipped with sensors, the CDU continuously monitors coolant parameters such as temperature, flow rate, and pressure levels, enabling real-time intervention to maintain peak thermal performance and reliability in complex environments. Summary of the Invention

[0007] In one aspect, this disclosure provides a method for operating a component of a coolant distribution unit (CDU), the method comprising: receiving measurement values ​​from each of a plurality of sensors; comparing each of the received measurement values; determining, based on the comparison, whether a subset of the received measurement values ​​differs from a majority of the other received measurement values ​​by more than a predetermined threshold; generating an average measurement value based on all the received measurement values ​​in response to determining that none of the received measurement values ​​differs from a majority of the other received measurement values ​​by more than the predetermined threshold; generating an average measurement value based on the received measurement values ​​excluding the subset of the received measurement values ​​in response to determining that the subset of the received measurement values ​​differs from a majority of the other received measurement values ​​by more than the predetermined threshold; and operating the component based on the average measurement value.

[0008] In another aspect, this disclosure provides a coolant distribution unit (CDU) comprising: a cabinet supporting a fluid coolant flow system including a heat exchanger, a primary circuit, and a secondary circuit, the heat exchanger being supported in the cabinet, the primary circuit being fluidly connected to a first side of the heat exchanger, the primary circuit including one or more sensors configured to provide sensor information and one or more valves, the secondary circuit being fluidly connected to a second side of the heat exchanger, the secondary circuit including one or more valves, one or more pumps, one or more sensors configured to provide sensor information, and one or more filters; and a controller supported by the cabinet, the controller being configured to control one or more components of the primary circuit and the secondary circuit based on sensor information from one or more sensors configured to monitor the condition of one or more of the primary circuit and the secondary circuit.

[0009] In another aspect, this disclosure provides a method for operating a coolant distribution unit (CDU), the method comprising: monitoring the condition of the CDU by an electronic processor; determining by the electronic processor whether the condition exceeds a threshold; and generating an alarm.

[0010] For larger data centers, reliable CDU operation can be critical to prevent overheating and ensure equipment performance and lifespan. Therefore, the embodiments described herein provide various control methods and systems for CDU fault detection and mitigation. Attached Figure Description

[0011] Figure 1A A coolant distribution unit (CDU) according to some embodiments is shown.

[0012] Figure 1B Illustrations based on some embodiments Figure 1A CDU.

[0013] Figure 1C Illustrations based on some embodiments Figure 1A CDU.

[0014] Figure 2A According to some embodiments Figure 1A The first part of the schematic diagram of the liquid coolant system of the CDU.

[0015] Figure 2B According to some embodiments Figure 2A The second part of the schematic diagram of the liquid coolant system.

[0016] Figure 3 This is a block diagram of an electronic controller for a CDU according to some embodiments.

[0017] Figure 4 A device cooling network according to some embodiments is shown. Figure 1A CDU.

[0018] Figure 5 This is a side view of a CDU according to some embodiments.

[0019] Figure 6 It is according to some embodiments for operation by Figure 3 The electronic controller implements Figure 1A A flowchart of the method for the components of the CDU.

[0020] Figure 7 This indicates that the operation according to some embodiments is... Figure 3 The electronic controller implements Figure 1A A schematic diagram of the method for constructing components of a CDU.

[0021] Figure 8 According to some embodiments, including Figure 1A The data center cooling communication network of the CDU. Detailed Implementation

[0022] The embodiments described herein relate to a coolant distribution unit (CDU).

[0023] Before explaining any embodiment in detail, it should be understood that the embodiments are not limited in their application to the details of the configuration and arrangement of the components set forth in the following description or shown in the accompanying drawings. Embodiments can be practiced or implemented in various ways. Moreover, it should be understood that the wording and terminology used herein are for descriptive purposes and should not be considered limiting. The use of “comprising,” “including,” or “having,” and variations thereof is intended to cover the items listed thereafter and their equivalents, as well as additional items. Unless otherwise stated or limited, the terms “installation,” “connection,” “support,” and “linkage,” and variations thereof are used broadly and cover direct and indirect installation, connection, support, and linking.

[0024] Additionally, it should be understood that embodiments may include hardware, software, and electronic components or modules, which, for the purposes of discussion, may be shown and described as if most components were implemented solely in hardware. However, those skilled in the art, and upon reading this detailed description, will recognize that in at least one embodiment, the electronic aspects may be implemented in software (e.g., stored on a non-transitory computer-readable medium) capable of being executed by one or more processing units, such as microprocessors and / or application-specific integrated circuits (“ASICs”). Therefore, it should be noted that embodiments may be implemented using multiple hardware and software-based devices and multiple different structural components. For example, “server,” “computing device,” “controller,” “processor,” etc., described in the specification may include one or more processing units, one or more computer-readable medium modules, one or more input / output interfaces, and various connectors (e.g., system buses) for connecting components.

[0025] Relative terms used in conjunction with quantities or conditions, such as “about,” “approximately,” “basically,” etc., will be understood by a person skilled in the art to include the stated value and have a meaning defined by the context (e.g., the term includes at least the degree of error associated with measurement accuracy, tolerances associated with a particular value [e.g., manufacturing tolerances, assembly tolerances, usage tolerances, etc.]). Such terms should also be considered to disclose a range defined by the absolute values ​​of the two endpoints. For example, the statement “from about 2 to about 4” also discloses a range “from 2 to 4.” Relative terms may refer to the indicated value plus or minus a percentage (e.g., 1%, 5%, 10% or more).

[0026] It should be understood that although some of the accompanying figures illustrate hardware and software located within a particular device, these depictions are for illustrative purposes only. Functions described herein as being performed by one component can be performed by multiple components in a distributed manner. Similarly, functions performed by multiple components can be combined and performed by a single component. In some embodiments, the illustrated components can be combined or divided into separate software, firmware, and / or hardware. For example, instead of being located within and executed by a single electronic processor, logic and processing can be distributed among multiple electronic processors. Regardless of how they are combined or divided, hardware and software components can reside on the same computing device or can be distributed among different computing devices connected by one or more networks or other suitable communication links. Similarly, components described as performing specific functions can also perform additional functions not described herein. For example, a device or structure "configured" in a certain way is configured at least in that way, but can also be configured in ways not explicitly listed.

[0027] For ease of description, some or all of the example systems presented herein are illustrated using a single example of each of their component sections. Some examples may not describe or show all the components of the system. Other examples may include more or fewer of each of the components shown, may combine some components, or may include additional or alternative components.

[0028] Other aspects of the embodiments will become apparent from consideration of the detailed description and accompanying drawings.

[0029] Figures 1A to 1C An example coolant distribution unit (CDU) 100 is shown. The CDU 100 specifically includes an electronic controller 300 (described below). Figure 3 (Described in more detail), multiple pumps (e.g., fill and replenish pump 102, variable frequency drive (VFD) pump 104, and secondary pump 106), multiple valves (e.g., primary control valve 108, pump check valve 110, isolation valve 112), and multiple sensors (e.g., temperature sensor 114, pressure sensor 116, flow meter 118). The CDU 100 also includes a reservoir 120, an expansion tank 122, and a liquid-liquid heat exchanger 124. The CDU also includes a housing or cabinet 50 supporting the controller 300 and other components of the CDU 100.

[0030] Cabinet 50 is a rectangular metal enclosure having: a frame 78; side panels (not shown) that can be selectively removed from frame 78; and a top panel 86. Frame 78 supports a user interface (e.g., input / display 90, emergency stop button, or other interface) that may include controller 300. Cabinet 50 includes other structures (e.g., casters, not shown, attached to the bottom of the frame; eye bolts, attached to the top of frame 78) to facilitate movement of CDU 10. Secondary supply lines 54 and 58 of secondary circuit 202B, and primary return lines 66 and 70 of primary circuit 202A exit cabinet 50 through holes 92 in the top panel 86 of cabinet 50. Figure 1A As shown, each hole 92 has an edge 94 that rises a distance 96 above the basic planar portion 98 of the top panel 86 (e.g., between 1 / 4 inch and 1 inch, such as 1 / 2 inch). It should be understood that if a small amount of water or other liquid has accumulated on the top panel 86 of the cabinet 50, the raised edge 94 limits the amount of water that can enter the cabinet 50.

[0031] Figures 2A to 2B This is a schematic diagram illustrating a fluid coolant flow system 200 of a CDU 100 according to some embodiments. System 200 includes a primary fluid flow path (referred to herein as primary loop 202A) for liquid coolant on a first (heat absorption) side of heat exchanger 124 and a secondary flow path (referred herein as secondary loop 202B) for liquid coolant on a second (heat dissipation) side of heat exchanger 124. Primary loop 202A includes an inlet valve J3 and an outlet valve J2 (… Figure 1A and Figure 1B Isolation valve 112). Secondary circuit 202B includes input valve J1 and output valve J4 ( Figure 1A and Figure 1B (Isolation valve 112). Heat exchanger 124 receives cooled liquid coolant from primary circuit 202A to dissipate heat from the liquid coolant received in secondary circuit 202B on the heat-absorbing side of heat exchanger 124. The cooled liquid coolant in secondary circuit 202B is then (at valve J4) output (e.g., output to equipment coolant network 400, as discussed below). Figure 4The description describes a system 400 where heated liquid coolant is provided for cooling one or more information technology (IT) devices, such as servers, network switches, routers, storage devices, and other computing hardware. Heated liquid coolant from network 400 is then returned to system 200 (at valve J1). Simultaneously, heated liquid coolant in primary circuit 202A is recirculated and cooled (e.g., via a secondary cooling / heat transfer system (not shown) that receives heated liquid coolant output at valve J2 and provides cooled liquid coolant back to CDU 100 at the input of valve J3). In some embodiments, CDU 100 may include additional components / subsystems for additional cooling of the liquid coolant.

[0032] Figure 4 This is an example device cooling network 400 for cooling multiple IT devices according to some embodiments. The device cooling network 400 includes a feed line 402A configured to receive a cooled liquid coolant output from CDU 100 (i.e., Figure 2B The output of valve J4). Feed line 402A is connected to one or more secondary pipes (not shown) of equipment racks / housings 404, each of which includes one or more IT devices. The secondary pipes of racks / housings 404 may extend along one or more heat transfer surfaces of racks / housings 404 (or the IT devices themselves) to absorb heat generated from the respective IT devices. From each rack / housing 404, the warmed coolant is returned to CDU 100 (in) via return line 402B. Figure 2B (At the input of valve J3) to recool and recirculate within the equipment cooling network 400.

[0033] Return to Figures 2A to 2BAs shown in the figure, the primary circuit 202A includes multiple valves V17, V19, J2, and J3, and sensors (e.g., temperature sensors T4 and T5, pressure sensors P10, P12, and P13, and flow meter FM1). The secondary circuit 202B also includes multiple valves V1-V16, V18, V20, J1, and J4, pumps PMP1-PMP4, and sensors (e.g., temperature sensors T1-T3 and T6-T8, pressure sensors P1-P9, P11, and P14, and flow meter FM2). The controller 300 is communicatively coupled to each of the multiple valves V1-V20 and pumps PMP1-PMP4, and controls the operation of each of the multiple valves V1-V20 and pumps PMP1-PMP4 based on sensor information from one or more of the various sensors in the system 200. The controller 300 can also receive sensor information about the environment inside the housing 50 of the CDU 100 (e.g., via a relative humidity sensor RH1 and an ambient temperature sensor T9) and sensor information about the environment outside the housing of the CDU 100 (e.g., via a relative humidity sensor RH2 and a temperature sensor T10). For ease of description, the sensors of the flow system 200 are collectively referred to herein as the plurality of sensors 204, the valves of the flow system 200 are collectively referred to herein as the plurality of valves 208, and the pumps of the flow system 200 are collectively referred to herein as the plurality of pumps 206. In some embodiments, one or more different types of sensors (and their functions) of the system 200 may be combined into a single sensor (e.g., a combined temperature and humidity sensor, a combined pressure and water flow sensor, etc.). The system 200 may include more than Figures 2A to 2B The number of sensors shown may be more or less.

[0034] The fluid coolant flow system 200 may include additional components (e.g., filters FIL1-FIL3, screens ST1-ST4, automatic vents, and pressure relief valves), which will not be described in detail here for the sake of brevity.

[0035] refer to Figure 5In another embodiment, CDU 500 also includes a CDU heat exchanger assembly 502 (shown schematically) to control the temperature of CDU 500 (e.g., CDU electronics). As discussed above, CDU 500 may be located in a room 42 separate from (IT) equipment and may not require temperature control. The operation of CDU 500 generates heat, and the temperature of CDU components may exceed optimal operating conditions without cooling the components of CDU 500. CDU heat exchanger assembly 502 is configured as a liquid-air heat exchanger assembly, which includes a liquid heat exchanger 506 and a fan 510 that directs airflow through the liquid heat exchanger 506. A liquid heat exchanger 506 may be coupled to the primary circuit 202a, and a fan 510 generates an airflow of ambient air around the CDU room above the liquid heat exchanger 506. Cooled primary coolant from an external heat exchanger (e.g., a building-mounted heat exchanger) is returned through this airflow to cool the ambient air, which is then directed into the CDU 500, for example, toward sensitive components such as controller 300 or other electronic devices. In some embodiments, only a portion of the primary coolant in the primary circuit 202a flows through the liquid heat exchanger. In other embodiments, the CDU heat exchanger assembly may be coupled to a secondary supply line or another line within the CDU.

[0036] Continue to refer to Figure 5 The CDU 500 receives operating power via power input line 514. The CDU 500 also includes a battery pack 518 (e.g., a 24-volt battery pack schematically shown) configured to supply power during intermittent periods if operating power via power input line 514 is interrupted and before a secondary power source (e.g., a backup generator) begins supplying power to the CDU 500. Alternatively, other voltage or battery pack configurations may be used.

[0037] Figure 3This is a block diagram of an electronic controller 300 of a CDU 100 according to some embodiments. The electronic controller 300 includes multiple electrical and electronic components that facilitate power supply, operational control, and protection of components and modules within the electronic controller 300. The electronic controller 300 particularly includes an electronic processor 305 (such as a programmable electronic microprocessor, microcontroller, or similar device), a memory 310 (e.g., a non-transitory computer-readable storage device), and an input / output interface 315. The electronic processor 305 is communicatively connected to the memory 310 and the input / output interface 315. The electronic processor 305, together with the memory 310 and the input / output interface 315, is cooperatively configured to implement the methods described herein, etc. It should be understood that some or all components of the controller 300 (including additional components) may be remote / dispersed from each other and / or located away from the CDU 100 within the CDU 100.

[0038] The memory 310 may consist of one or more non-transitory computer-readable media and includes at least a program storage area and a data storage area. The program storage area and data storage area may include combinations of different types of memory, such as read-only memory (“ROM”), random access memory (“RAM”), flash memory, or other suitable memory devices. An electronic processor 305 is coupled to the memory 310 and the input / output interface 315.

[0039] Electronic processor 305 (e.g., from memory 310 and / or input / output interface 315) sends and receives information and processes the information by executing one or more software instructions or modules that can be stored in memory 310 or another non-transitory computer-readable medium. The software may include firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. Electronic processor 205 is configured to retrieve from memory 310 and execute software for automatically detecting / predicting anomalies within CDU 100 and for performing methods as described herein.

[0040] In some cases, the electronic controller 300 may be implemented in several independent controllers (e.g., programmable electronic controllers), each configured to perform a specific function or sub-function. For example, one or more components of the controller 300 may be located remotely from the CDU 100 (e.g., part of a remote server, not shown, communicatively connected to the CDU 100). Additionally, the electronic controller 300 may include submodules comprising additional electronic processors, memories, or circuitry for handling input / output functions, signal processing, and applying the methods listed below. In other cases, the electronic controller 300 includes additional, fewer, or different components. Therefore, the program may also be distributed across one or more processors.

[0041] Input / output interface 315 (e.g., via one or more wired and / or wireless connections) transmits and receives information from devices external to electronic controller 300, such as components of CDU 100. Input / output interface 315 receives input from multiple sensors 204 (e.g., to one or more of the multiple valves 208 and / or the multiple pumps 206, transceiver 325 and / or HMI 330, etc.) and provides system output. Input / output interface 315 may also include other input and output mechanisms, which are not described herein for brevity and may be implemented in hardware, software, or a combination of both.

[0042] In some cases, controller 300 also includes transceiver 325 and / or human-machine interface (HMI) 330. Transceiver 325 includes a radio transceiver that transmits data over one or more wireless communication networks (e.g., cellular networks, satellite networks, terrestrial mobile radio networks, etc.). Transceiver 325 also provides in-vehicle wireless communication using appropriate network modes (e.g., Bluetooth™, Near Field Communication (NFC), Wi-Fi™, etc.). Thus, transceiver 325 communicatively connects the electronic controller 300 and other components of CDU 100 to networks or electronic devices inside and outside CDU 100. For example, using transceiver 325, electronic controller 300 can communicate with one or more devices (e.g., other CDU 100s) via a communication system (not shown) to send and receive data, commands, and other information. Transceiver 325 includes other components that enable wireless communication (e.g., amplifiers, antennas, baseband processors, etc.), which are not described herein for brevity and can be implemented in hardware, software, or a combination of both. Some instances involve multiple transceivers or separate transmit and receive components (e.g., transmitter and receiver) rather than a combined transceiver.

[0043] The HMI 330 provides visual outputs, such as graphic indicators (i.e., fixed or animated icons), lights, colors, text, images, and combinations thereof. The HMI 330 includes suitable display mechanisms for displaying the visual outputs, such as instrument clusters, center console displays (e.g., touchscreens or other suitable mechanisms), etc. In some cases, the HMI 330 displays a graphical user interface (GUI) that allows the driver or passenger to interact with the CDU 100 (e.g., generated by the electronic processor 302 and presented on a display screen). The HMI 330 may also provide audio outputs to the driver via speakers included in or separate from the HMI 330, such as ringtones, buzzers, voice outputs, or other suitable sounds. In some cases, the HMI 330 provides a combination of visual and audio outputs.

[0044] As will be described in further detail below, in some cases, memory 310 includes, in particular, computer-executable instructions for the detection and mitigation of component and measurement faults. In some cases, the computer-executable instructions include instructions for training a deep learning system to detect / predict one or more anomalies associated with one or more components of CDU 100.

[0045] In some cases, the electronic controller 300 uses one or more machine learning methods (e.g., artificial intelligence algorithms) to analyze sensor information from sensor 204 to identify / predict anomalies within CDU 100 (as described herein). Machine learning generally refers to the ability of a computer program to learn without being explicitly programmed. In some cases, the computer program (e.g., a learning engine) is configured to build algorithms based on inputs. Supervised learning involves presenting a computer program with example inputs and their expected outputs. The computer program is configured to learn general rules that map inputs to outputs based on the training data it receives. Example machine learning engines include decision tree learning, association rule learning, artificial neural networks, classifiers, edge computing, inductive logic programming, support vector machines, clustering, Bayesian networks, reinforcement learning, representation learning, similarity and metric learning, sparse dictionary learning, and genetic algorithms. Using these approaches, the computer program is able to ingest, parse, and understand data and progressively refine algorithms for data analysis.

[0046] The system performance of the flow system 200 is particularly dependent on the proper operation of the pumps 206. In some embodiments, each pump includes a corresponding pump fault sensor (e.g., a fault sensor integrated into the pump). When the pump fault sensor indicates a fault, the sensor is configured to provide a fault signal to the electronic controller 300. In response, the electronic controller 300 may accordingly generate an alarm to the user (e.g., via HMI 330), stop or adjust the operation of one or more pumps 206, or both. However, there may be cases where the pump fault sensor itself is faulty. In such cases, the pump fault sensor may output a fault signal to the controller 300 even when the corresponding pump is operating normally. This may cause the controller 300 to provide false alarms and / or unnecessary modifications / shutdowns to one or more operations of the system 200.

[0047] Therefore, it may be expected that the electronic controller 300 performs additional steps to verify that one or more of the pumps are operating correctly, including evaluating the accuracy of measurements from one or more of the sensors 204.

[0048] As mentioned above, erroneous fault detection can impair the system performance of the CDU. Such erroneous fault detection can be caused by inaccurate measurements and / or faulty sensors. Therefore, it may be advantageous to verify the measurements from the sensors by comparing measurements from multiple (redundant) sensors of a common type located near each other to determine if any sensors are inaccurate. This can be beneficial for components with a limited number of inputs for sensor measurements. For example, the VFD pump 206 may include a single input for receiving pressure measurements. In this case, the accuracy of the received measurements may be important.

[0049] Figure 6 This is a flowchart illustrating a method 600 for operating components of CDU 100 (e.g., one of the plurality of pumps 206 or one of the plurality of valves 208) according to some embodiments. Method 600 may be modified or performed differently from the specific example provided. As an example, method 600 is described as being performed by electronic controller 300 and, in particular, by electronic processor 305. However, it should be understood that in some cases, certain parts of method 600 may be performed by other devices or subsystems of CDU 100. For ease of description, the method is described in relation to a single component of CDU 100. However, it should be understood that method 600 may be implemented for more than one component of CDU 100. It should also be understood that method 600 may be implemented for any number of more than three sensors.

[0050] At box 602, electronic processor 305 receives measurements from each of a plurality of sensors (e.g., three or more sensors from said plurality of sensors 204). The sensors are all of the same type (e.g., temperature sensors or pressure sensors) and are positioned close to / adjacent to each other within the flow system 200 of CDU 100 (e.g., Figure 2A Flowchart 200 Temperature Sensor T1-T3 or Figure 2B The flowchart for pressure sensors P1-P3 in 200 is shown. Each received measurement value is of the same type (e.g., temperature value, pressure value, etc.).

[0051] At block 604, the electronic processor 305 performs a comparison of each received measurement value. At block 606, the electronic processor 305 determines whether a subset of the measurement values ​​(e.g., at least one) differs from a majority of the other measurement values ​​(e.g., at least two) by more than a predetermined threshold. The electronic processor 305 generates an average measurement value based on the received measurement values ​​excluding the subset of measurement values ​​(block 608), and operates the component based on the average measurement value (block 610). If no measurement value is determined to differ from a majority of the measurement values ​​by more than the predetermined threshold, the electronic processor 305 generates an average measurement value based on all received measurement values ​​(block 612). Then, at block 612, the electronic processor 305 operates the component based on the average measurement value (block 612).

[0052] In some embodiments, as described above, the component is one of the plurality of pumps 206. For example, in some embodiments, the pump is a VFD pump (e.g., Figures 1A to 1B Pump 104 or Figure 2A (One of the pumps, PMP3 or PMP4). In some embodiments (e.g., an embodiment where the component is a pump such as a VFD pump), the controller 300 can be configured to provide an average temperature measurement to the pump.

[0053] In some embodiments, the component is one of the plurality of valves 208. For example, in some embodiments, the valve is an electronically pressure-independent control valve (EPICV) (e.g., Figure 2B (Valve V17). In some embodiments (e.g., embodiments of valves such as EPICV), controller 300 can be configured to provide an average pressure measurement to the pump.

[0054] In some embodiments, the electronic processor 305 is configured to predict component failures / maintenance of one or more components of the system 200. Figure 7An exemplary method is illustrated, executed by a controller to predict component failure or maintenance needs. For example, in a first step 702 of method 700, electronic processor 305 may be configured to monitor conditions in the CDU, such as pressure drop / differential pressure on a filter of system 200. Electronic processor 305 receives data from one or more sensors (e.g., temperature sensor 114, pressure sensor 116, flow meter 118) indicating the condition of the monitored component (e.g., pump, filter, etc.). In the next step 704, electronic processor 305 determines when the differential pressure exceeds a threshold. For example, the temperature of one or more pumps may exceed a normal operating threshold temperature. In another case, the coolant flow rate may be reduced, indicating blockage due to a clogged filter or the need for filter maintenance. In yet another example, the coolant pressure may exceed a threshold, indicating blockage. In the next step 706, electronic processor 305 generates an alarm (e.g., an alarm indication to replace the filter) to the user via HMI 330. As another example, the electronic processor 305 can be configured to determine pump failure based on an increase in the pump's revolutions per minute (RPM) relative to measurements of equivalent performance (e.g., based on flow rate and / or pressure determination at a specific point in system 200). In response, the electronic processor 305 can generate an alarm for the user indicating that the pump requires maintenance. The electronic processor 305 can monitor other sensor information (e.g., flow rate, motor current, motor temperature, motor vibration, etc.) to determine if components may be faulty and / or require maintenance.

[0055] refer to Figure 8 IT device 802A is connected to the device cooling network 400 of CDU 100 (e.g., via the above-mentioned...). Figure 4 The aforementioned rack / housing 404) cools the electronic equipment. For ease of description, the communication network 800 is described with respect to a single IT device 802A. It should be understood that in some embodiments, the network 800 includes more than one IT device 802A communicatively connected to a CDU 100. It should also be understood that the network 800 may include more than one CDU 100, each CDU 100 communicatively connected to one or more corresponding IT devices 802A.

[0056] In some embodiments, CDU 100 is configured to receive information (e.g., temperature information, operating information, etc.) from IT device 802A and adjust the operation of one or more of pumps 206 and / or valves 208, for example, to optimize the energy use of CDU 100 based on the received information. Additionally or alternatively, in some embodiments, CDU 100 is configured to adjust the operation of one or more of pumps 206 and / or valves 208 based on information received from BIM system 802B.

[0057] In some embodiments, the electronic controller 300 (and its components) is mounted on a single circuit board.

[0058] In some embodiments, the controller 300 is also configured to operate one or more pumps 206 (e.g., one or more EPICV pumps) of the system 200 based on a proportional-integral-derivative (PID) loop (e.g., based on the pressure detected within the system 200).

Claims

1. A method for operating components of a coolant distribution unit (CDU), the method comprising: Receive measurement values ​​from each of the multiple sensors; Each of the received measurement values ​​is compared; Based on the comparison, it is determined whether a subset of the received measurement values ​​differs from most of the other received measurement values ​​by more than a predetermined threshold. In response to determining that none of the received measurements differs from most of the other received measurements by more than the predetermined threshold, an average measurement is generated based on all the received measurements. In response to determining that the subset of the received measurements differs from most of the other received measurements by more than the predetermined threshold, an average measurement is generated based on the received measurements excluding the subset of the received measurements. as well as The component is operated based on the average measurement value.

2. The method according to claim 1, wherein, The received measurement value is a temperature measurement value.

3. The method according to claim 2, wherein, The component in question is a pump.

4. The method according to claim 3, wherein, The component is a variable frequency drive (VFD) pump.

5. The method according to claim 1, wherein, The received measurement value is a pressure measurement value.

6. The method according to claim 5, wherein, The component in question is a valve.

7. The method according to claim 6, wherein, The component is an electronically pressure-independent control valve (EPICV).

8. A coolant distribution unit (CDU), comprising: The server rack supports a fluid coolant flow system, which includes... A heat exchanger, which is supported in the cabinet; A primary circuit, which is in fluid communication with a first side of the heat exchanger, includes one or more sensors configured to provide sensor information and one or more valves. A secondary circuit, which is in fluid communication with a second side of the heat exchanger, includes one or more valves, one or more pumps, one or more sensors configured to provide sensor information, and one or more filters. as well as A controller, supported by the cabinet, is configured to control one or more components of the primary and secondary circuits based on sensor information from one or more sensors configured to monitor the conditions of one or more of the primary and secondary circuits.

9. The coolant distribution unit according to claim 8, wherein, The controller is configured to perform a method for detecting component failures.

10. The coolant distribution unit according to claim 9, wherein, The controller is configured to perform a method for detecting when component maintenance is required.

11. The coolant distribution unit of claim 8, further comprising a battery pack configured to provide a power supply.

12. The coolant distribution unit according to claim 11, wherein, The battery pack is located inside the cabinet.

13. The coolant distribution unit of claim 8 further includes a second heat exchanger supported in the cabinet and coupled to the primary circuit, the second heat exchanger including a fan that generates a cooling airflow at least partially within the cabinet.

14. The coolant distribution unit according to claim 8, wherein, The cabinet includes a top panel defining a plurality of holes, through which at least a portion of the primary circuit and at least a portion of the secondary circuit extend, each hole defining a raised edge.

15. The coolant distribution unit according to claim 14, wherein, The raised edge defines the height relative to the top panel.

16. The coolant distribution unit according to claim 15, wherein, The height is 1 / 2 inch.

17. A method for operating a coolant distribution unit, the method comprising: The status of the coolant distribution unit is monitored by an electronic processor; The electronic processor determines whether the condition exceeds a threshold. as well as Generate an alert.

18. The method according to claim 17, wherein, The condition is one of temperature, pressure, or flow rate.

19. The method of claim 17, wherein, The human-machine interface generates an alarm.

20. The method of claim 17, further comprising: Receive measurement values ​​from each of the multiple sensors; Each of the received measurement values ​​is compared; Based on the comparison, it is determined whether a subset of the received measurement values ​​differs from most of the other received measurement values ​​by more than a predetermined threshold. In response to determining that none of the received measurements differs from most of the other received measurements by more than the predetermined threshold, an average measurement is generated based on all the received measurements. In response to determining that the subset of the received measurements differs from most of the other received measurements by more than the predetermined threshold, an average measurement is generated based on the received measurements excluding the subset of the received measurements. as well as The component is operated based on the average measurement value.

Images