Fault identification method and device, terminal equipment and storage medium

Abstract

According to the fault identification method and device, the terminal equipment and the storage medium provided by the embodiment of the invention, the state information of the liquid cooling pump is received, the information type of the state information is judged, the corresponding preset relation is matched based on the information type, and the state information is processed through the preset relation; therefore, the fault mode of the liquid cooling pump can be quickly identified, and the monitoring efficiency of the upper computer on the liquid cooling pump is improved.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of liquid cooling, and particularly relates to a fault identification method and device, a terminal device and a storage medium. BACKGROUND

[0002] At present, with the development of supercomputing data centers and the continuous improvement of the computing capacity of supercomputing centers, the unit power consumption of servers gradually increases, and the heat dissipation demand of supercomputing data centers is increasingly strong.

[0003] Generally, the existing supercomputing data centers generally adopt air cooling heat dissipation, that is, the cooling liquid is pumped to the corresponding pipeline by the liquid cooling pump, and due to the flow of the cooling liquid, the cold air is formed around the pipeline, and the cold air around the pipeline is blown into the server cabinet by the fan, so as to realize heat dissipation.

[0004] The applicant finds that if the liquid cooling pump of a certain node fails, the heat dissipation of part of the server cabinet cannot be guaranteed, so the monitoring of the liquid cooling pump is particularly important. SUMMARY

[0005] The purpose of the embodiments of the present application is to provide a fault identification method, device, terminal device and storage medium, and to provide a method for identifying the fault of a liquid cooling pump.

[0006] To achieve the above purpose, the technical solution adopted by the present application is: In a first aspect, the present application provides a fault identification method, comprising: receiving state information of a liquid cooling pump; determining the information type of the state information; matching a preset relationship based on the information type; determining the fault mode of the liquid cooling pump according to the state information and the preset relationship.

[0007] In a second aspect, the present application provides a fault identification device, comprising: a receiving module for receiving state information of a liquid cooling pump; a judging module for determining the information type of the state information; a matching module for matching a preset relationship based on the information type; and a fault determining module for determining the fault mode of the liquid cooling pump according to the state information and the preset relationship.

[0008] In a third aspect, the present application provides a terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of the first aspect when executing the computer program.

[0009] In a fourth aspect, the present application provides a storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method of the first aspect.

[0010] The application has the beneficial effect that the fault identification method, device, terminal equipment and storage medium provided by the embodiments of the application can quickly identify the fault mode of the liquid cooling pump by receiving the state information of the liquid cooling pump, judging the information type of the state information, matching the corresponding preset relationship based on the information type, and processing the state information through the preset relationship, thereby improving the efficiency of monitoring the liquid cooling pump by the upper computer. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments or exemplary technical description. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0012] Figure 1 The schematic diagram of the technical background of the embodiments of the present application; Figure 2 The flowchart of the fault identification method of the embodiments of the present application; Figure 3 The waveform diagram of the state information of an embodiment of the embodiments of the present application; Figure 4 The waveform diagram of the state information of another embodiment of the embodiments of the present application; Figure 5 The waveform diagram of the state information of another embodiment of the embodiments of the present application; Figure 6 The structural schematic diagram of the fault identification device of the embodiments of the present application; Figure 7 The structural schematic diagram of the terminal equipment of the embodiments of the present application. DETAILED DESCRIPTION

[0013] In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0014] It should be noted that when a component is referred to as "fixed to" or "set on" another component, it can be directly or indirectly attached to that other component. When a component is referred to as "connected to" another component, it can be directly or indirectly connected to that other component. The terms "upper," "lower," "left," "right," etc., indicate orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, and are for ease of description only, not to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Those skilled in the art can understand the specific meaning of the above terms according to the specific circumstances. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features. "A plurality" means two or more, unless otherwise explicitly defined.

[0015] Before describing the technical solutions provided in the embodiments of this application, the technical background of this application will be explained, such as... Figure 1 As shown, multiple liquid cooling pumps are controlled by a host computer. For example, if the host computer detects that the temperature of a certain area is higher than that of other areas through a temperature sensor, it will increase the speed of the liquid cooling pump in that area.

[0016] It is understood that this type of liquid-cooled pump is generally a brushless water pump. The internal circuit board of a brushless water pump has pre-loaded embedded software. The circuit board can have four hardware interfaces: VCC, FG, PWM (optional), and GND. The VCC interface is used to connect to an external power supply; the FG interface can output under the control of the embedded software (e.g., outputting a square wave representing the pump's rotational speed during operation); the PWM interface can adjust the pump's rotational speed; and the GND interface is used for grounding. It should be noted that the FG interface on the circuit board can output a square wave representing the pump's fault mode, not just a rotational speed square wave. The pre-installed embedded software controls the output of the FG interface, thus issuing corresponding status information when the pump malfunctions.

[0017] Please refer to the above scenarios. Figures 1-2 This application provides a fault identification method applied to a host computer, including: S1, Receive the status information of the liquid cooling pump.

[0018] In this step, the host computer can receive FG interface output information, such as the waveform output from the FG interface. The output waveform contains the status information of the liquid cooling pump. This status information can include the pump's rotational speed and fault mode. In some possible examples, the status information may also include the pump's serial number. In some optional examples, the liquid cooling pump's status information can be received periodically, thereby reducing the occupancy of the output interface.

[0019] S2. Determine the information type of the status information.

[0020] In this step, since the waveform output by the FG interface can be pre-configured via embedded software, the host computer can classify different waveforms into different information types to prepare for subsequent fault mode identification.

[0021] S3. Matching preset relationships based on information type; In this step, because different types of status information are processed in different ways, the host computer needs to match the corresponding preset relationship after determining the information type of the status information in order to process the status information.

[0022] S4. Determine the failure mode of the liquid cooling pump based on the status information and preset relationships.

[0023] In this step, the status information is mapped to relevant fault modes through preset relationships, thereby enabling rapid identification of fault modes. Some possible examples include fault modes such as undervoltage, overvoltage, overcurrent, temperature, short circuit, and phase loss.

[0024] In summary, the fault identification method provided by the embodiments of the present invention receives the status information of the liquid cooling pump, determines the information type of the status information, matches the corresponding preset relationship based on the information type, and processes the status information through the preset relationship, thereby enabling rapid identification of the fault mode of the liquid cooling pump and improving the efficiency of the host computer's monitoring of the liquid cooling pump.

[0025] It should be noted that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0026] The technical solution of this application will be described below with reference to some specific examples.

[0027] Step S2 includes: determining the information type of the state information based on the waveform of the state information. The information type includes periodic waves and non-periodic waves. It can be understood that by classifying the information type into periodic waves and non-periodic waves, the variety of information types can be increased, and the corresponding preset relationships between periodic waves and non-periodic waves are also different, increasing the means of processing state information and making it suitable for fault identification in various complex scenarios.

[0028] In the first possible example, when it is necessary to output the fault mode but not the speed information, the following example can be used for fault identification: In this scenario, the state information is transmitted via a periodic wave, so the information type is a periodic wave. For example, as shown... Figure 3 (A) and such Figure 3 As shown in (B), periodic waves can include simple harmonic waves and square waves, etc., and can be selected according to the specific scenario.

[0029] Step S3 in this embodiment includes: determining the first period of the state information and obtaining the corresponding first frequency for the first period; and invoking a first preset relationship based on the first frequency. For example... Figure 3 As shown in (A), the first period can be obtained by selecting any period on the state information. Based on the relationship between period and frequency, the first frequency can be obtained from the first period.

[0030] As shown in Table 1 below, in this example, the first preset relationship can be retrieved from the corresponding relational database by using frequency as the keyword. The first preset relationship can be used to match the first frequency with the fault mode.

[0031] Step S4 of this embodiment includes: searching for the fault mode corresponding to the first frequency within the first preset relationship. As shown in Table 1 below, when the first frequency is 1kHz, the fault mode is undervoltage; when the first frequency is 2kHz, the fault mode is stall; and when the first frequency is 3kHz, the fault mode is overvoltage.

[0032] Frequency Fault mode 1 KHZ Under voltage 2 KHZ Stall 3 KHZ Over voltage …… …… Table 1 The relatively large frequency intervals in Table 1 above facilitate rapid differentiation of fault modes, improving the efficiency of fault mode identification. It should be noted that the correspondence between the frequencies and fault modes described above is not unique. The examples above are merely illustrative of the principles of this embodiment and do not limit the invention. Those skilled in the art can choose the appropriate correspondence based on specific scenarios; for example, 1kHz may correspond to overvoltage, or 1.5kHz may correspond to stall.

[0033] In summary, the fault diagnosis method of this embodiment corresponds the frequency of the periodic wave carrying the state information to the fault mode, thereby quickly determining the fault mode of the liquid cooling pump. Since the periodic wave in this scenario is not necessarily a square wave, this embodiment is suitable for scenarios where the state of the liquid cooling pump is checked periodically.

[0034] In the second possible example: when it is necessary to output the fault mode and the speed information, the following example can be used for fault identification: the status information of this scenario is transmitted through a periodic square wave, that is, the information type is a periodic square wave.

[0035] like Figure 4 (A) and such Figure 4 As shown in (B), step S3 of this embodiment includes: determining the second period of the periodic square wave and the proportion of high level occupancy within the second period; and invoking a second preset relationship based on the proportion. It can be understood that the second period can be obtained by selecting any period from the state information. The proportion of high level occupancy within the second period can be obtained by measuring the duration of the high level within the second period.

[0036] In this example, by using the proportion of high-level signals as keywords, a second preset relationship can be retrieved from the corresponding relational database. Through the second preset relationship, the proportion of high-level signals can be correlated with the fault mode.

[0037] Step S4 of this embodiment includes: searching for the fault mode corresponding to the proportion within the second preset relationship. As shown in Table 2 below, when the proportion of high level in the cycle is 10%, the fault mode is undervoltage; when the proportion of high level in the cycle is 20%, the fault mode is stalled; and when the proportion of high level in the cycle is 10%, the fault mode is overvoltage.

[0038] Proportion of high level within a cycle Fault mode 10% Under voltage 20% Stall 30% Over voltage …… …… Table 2 The relatively large intervals between the proportions in Table 2 above facilitate rapid differentiation of fault modes and improve the efficiency of fault mode identification. It should be noted that the correspondence between the proportion of high levels within the above cycle and the fault mode is not unique. The above examples are only for illustrating the principle of this embodiment and do not limit the invention. Those skilled in the art can choose the corresponding relationship according to specific scenarios; for example, a 10% proportion can also correspond to overvoltage, or 1.5% can correspond to stall.

[0039] In this embodiment, since the high-level ratio of the square wave in the second cycle is used as the corresponding parameter of the fault mode, it can both output the normal speed square wave (the speed is determined by the frequency and is independent of the high-level ratio) and determine the fault mode, thus making it applicable to the normal operation scenario of the liquid cooling pump.

[0040] In a third possible example: when other information besides fault mode information (such as the liquid cooling pump number) is needed, the following example can be used: In this example, the status information is a non-periodic square wave.

[0041] Step S3 of this embodiment includes: when the square wave is at a high level, the holding time of the high level is recorded sequentially to form a value group, wherein if the holding time is greater than a preset threshold, the high level is recorded as a first value; if the holding time is less than the preset threshold, the high level is recorded as a second value; and a third preset relationship is called based on the value group.

[0042] In some possible examples, the first N bits of the numerical group can be used as the starting segment for waveform recognition, where N is a positive integer. For example, if the first 5 bits are all 0, waveform recognition can start from the sixth bit.

[0043] like Figure 5 As shown, since square waves are non-periodic, they are distinguished based on the duration of their high-level signal. For example, when the duration (threshold) is greater than 0.01 seconds, the high-level signal is recorded as the first value 1; when the duration is less than 0.01 seconds, the high-level signal is recorded as the second value 0. The value groups can be obtained by following the chronological order. It should be understood that the above threshold is only an example, and those skilled in the art can flexibly set the threshold.

[0044] For example, the numerical group could be 001000001 (excluding the aforementioned starting segment). The first three digits of the numerical group can be designated as the liquid cooling pump number, with the remaining digits corresponding to the fault mode. As shown in Table 3 below, the first three digits (001) of the numerical group are taken as the liquid cooling pump number, allowing for rapid identification of the faulty liquid cooling pump within the liquid cooling pump network. The last three digits (001) of the numerical group are taken as the liquid cooling pump fault mode. It should be noted that since there are many different ways to arrange the numerical combinations, any number of digits in any position can be used to form an array to represent information. Therefore, the currently listed method is not limited. For example, the middle three digits (000) can be used as the verification digit to separate the preceding and following arrays.

[0045] First three digits of the number group Liquid cooled pump number 001 1 010 2 011 3 …… …… Table 3 Step S4 in this embodiment includes: searching for the fault mode corresponding to the numerical group within the third preset relationship.

[0046] As shown in Table 4 below, 001 can represent undervoltage, 010 can represent stall, and 011 can represent overvoltage.

[0047] Last three digits of the number group Fault mode 001 Under voltage 010 Stall 011 Over voltage …… …… Table 4 It should be noted that the correspondence between the first three digits of the above numerical group and the liquid cooling pump number is not unique. Alternatively, the first N digits of the numerical group can be used to correspond to the liquid cooling pump number, where N is a positive integer. The above example is only for illustrating the principle of this embodiment and does not limit the present invention. Those skilled in the art can choose the correspondence according to specific scenarios.

[0048] It should be noted that the correspondence between the last three digits of the above numerical group and the fault mode is not unique. For example, 001 can also correspond to overpressure, or 001 can correspond to stall. Those skilled in the art can select the correspondence according to the specific scenario.

[0049] It is understandable that other information, such as temperature information or manufacturing date, can be transmitted through combinations of numerical values. This is achieved simply by selecting a preset number of digits in the numerical value group that corresponds to the temperature information (or manufacturing date). This application only requires the output interface of the liquid cooling pump to achieve complex information transmission, eliminating the need for additional interfaces and making it convenient to use.

[0050] It is understood that this embodiment utilizes the high-level holding time of a non-periodic square wave to sequentially present the liquid cooling pump's serial number information and fault information, thereby accurately locating the fault of the liquid cooling pump, which is suitable for scenarios where multiple liquid cooling pumps form a network.

[0051] In summary, this invention demonstrates through three parallel embodiments how this application can determine the failure mode of a liquid cooling pump using status information, achieving rapid identification of failure modes without additional hardware.

[0052] In one possible example, the steps following step S4 include: displaying the failure mode.

[0053] For example, a display unit can be used to show the failure modes of the liquid cooling pump. The display unit may include a display panel, which can optionally be configured as a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Understandably, the operator can identify the failure modes of the liquid cooling pump through the information displayed on the display panel.

[0054] For example, a sound unit can be used to announce the fault modes of the liquid cooling pump. By converting the fault modes into audio data, then converting the audio data into electrical signals, and transmitting them to a speaker, which then outputs a sound signal, the tester can determine the fault mode of the liquid cooling pump by sound without having to look up.

[0055] Corresponding to the fault identification method in the above embodiments, the figure shows a structural block diagram of the fault identification device provided in the embodiments of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0056] like Figure 6 As shown, the fault identification device includes: a receiving module 1, a judging module 2, a matching module 3, and a fault determination module 4.

[0057] Receiver module 1 is used to receive the status information of the liquid cooling pump; Module 2 is used to determine the information type of the status information; Matching module 3 is used to match preset relationships based on information type; and Fault determination module 4 is used to determine the fault mode of the liquid cooling pump based on status information and preset relationships.

[0058] A terminal device includes a memory 61, a processor 60, and a computer program stored in the memory 61 and executable on the processor 60, wherein the processor 60 executes the computer program to implement the method described above.

[0059] Figure 7 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 6 in this embodiment includes: at least one processor 60 ( Figure 7 (Only one is shown in the diagram) a processor, a memory 61, and a computer program 62 stored in the memory 61 and executable on at least one processor 60, wherein the processor 60 executes the computer program 62 to implement the steps in any of the above method embodiments.

[0060] Terminal device 6 can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. This terminal device may include, but is not limited to, a processor 60 and a memory 61. Those skilled in the art will understand that... Figure 7 This is merely an example of terminal device 6 and does not constitute a limitation on terminal device 6. It may include more or fewer components than shown in the figure, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0061] The processor 60 can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0062] In some embodiments, memory 61 may be an internal storage unit of terminal device 6, such as a hard disk or memory of terminal device 6. In other embodiments, memory 61 may be an external storage device of terminal device 6, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD) card, flash card, etc., equipped on terminal device 6. Furthermore, memory 61 may include both internal storage units and external storage devices of terminal device 6. Memory 61 is used to store operating system, application programs, bootloader, data, and other programs, such as program code of computer programs. Memory 61 can also be used to temporarily store data that has been output or will be output.

[0063] A storage medium storing a computer program that, when executed by a processor, implements the methods of the various embodiments described above.

[0064] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0065] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0066] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0067] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0068] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0069] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0070] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0071] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0072] The above are merely optional embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A fault identification method, characterized in that, include: Receive status information from the liquid cooling pump; Determine the information type of the status information; Match a preset relationship based on the information type; The failure mode of the liquid cooling pump is determined based on the status information and the preset relationship.

2. The fault identification method as described in claim 1, characterized in that: Determining the information type of the state information includes: determining the information type of the state information based on the waveform of the state information, wherein the information type includes periodic waves and non-periodic waves.

3. The fault identification method as described in claim 2, characterized in that: If the information type is a periodic wave; the matching of a preset relationship based on the information type includes: Determine the first period of the state information and obtain the corresponding first frequency for the first period; The first preset relationship is invoked based on the first frequency; Determining the failure mode of the liquid cooling pump based on the status information and the preset relationship includes: Search for the fault mode corresponding to the first frequency within the first preset relationship.

4. The fault identification method as described in claim 2, characterized in that: If the information type is a periodic square wave; the matching of a preset relationship based on the information type includes: Determine the second period of the periodic square wave and the proportion of high level occupancy within the second period; The second preset relationship is invoked based on the aforementioned ratio; Determining the failure mode of the liquid cooling pump based on the status information and the preset relationship includes: Search for the fault mode corresponding to the ratio within the second preset relationship.

5. The fault identification method as described in claim 2, characterized in that: If the state information is a non-periodic square wave, the matching of a preset relationship based on the information type includes: When the square wave is at a high level, the holding time of the high level is recorded sequentially to form a numerical group. If the holding time is greater than a preset threshold, the high level is recorded as a first value; if the holding time is less than the preset threshold, the high level is recorded as a second value. The third preset relationship is invoked based on the numerical group.

6. The fault identification method as described in claim 5, characterized in that: Determining the failure mode of the liquid cooling pump based on the status information and the preset relationship includes: Search for the fault mode corresponding to the value group within the third preset relationship.

7. The fault identification method according to any one of claims 1-6, characterized in that: The step of determining the failure mode of the liquid cooling pump based on the status information and the preset relationship, and subsequent steps include: The aforementioned failure modes are demonstrated.

8. A fault identification device, characterized in that: include: The receiving module is used to receive the status information of the liquid cooling pump; The judgment module is used to determine the information type of the status information; The matching module is used to match a preset relationship based on the information type; as well as The fault determination module is used to determine the fault mode of the liquid cooling pump based on the status information and the preset relationship.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as claimed in any one of claims 1 to 7.

10. A storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as claimed in any one of claims 1 to 7.

Images