Fault monitoring method, device and system and wind power generation system

Abstract

The invention provides a fault monitoring method, device and system and a wind power generation system. The fault monitoring method comprises the steps of receiving current fault information of a monitored object; a target fault category corresponding to the current fault information is determined based on a fault corresponding relation between the fault information and fault categories, the fault categories comprise universal fault categories, and in the fault corresponding relation, each universal fault category corresponds to multiple kinds of fault information; and sending the target fault category to a second control system, so that the second control system performs fault monitoring on the monitored object. According to the fault monitoring method, device and system and the wind power generation system, the problem that the data processing pressure of a traditional control system is large is solved, the processing pressure of the second control system can be relieved, the fault response speed of the second control system can be increased, and normal operation of the monitored equipment can be guaranteed.

Description

Technical Field

[0001] The present disclosure relates to the field of wind power generation, and more specifically, to a fault monitoring method, device, system and wind power generation system. Background Art

[0002] With the continuous development of technologies in various fields, the complexity of equipment systems has gradually increased, and the number of failures that need to be monitored and addressed has also increased accordingly.

[0003] In order to ensure the normal operation of equipment systems, the perception systems used to monitor faults are becoming more and more complex, and the data processing work is becoming more and more arduous. However, with the increase in perception systems and fault information, the computing power of traditional control systems may be far from meeting the needs of data processing. For example, with the increasing application of visual perception systems in monitoring, traditional control systems may find it difficult to complete the processing of video data alone, which may lead to a decrease in the response speed to faults, which is not conducive to ensuring the normal operation of equipment systems. Summary of the invention

[0004] In view of the problem of high data processing pressure of traditional control systems in existing fault monitoring solutions, the present disclosure provides a fault monitoring method, device, system and wind power generation system.

[0005] A first aspect of the present disclosure provides a fault monitoring method, which is executed in a first control system, and includes: receiving current fault information of a monitored object; determining a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information; and sending the target fault category to a second control system so that the second control system can perform fault monitoring on the monitored object.

[0006] Optionally, the general fault category includes a reserved fault category, wherein the fault monitoring method further includes: obtaining new fault information to be added to the fault corresponding relationship; and determining the new fault information to correspond to the reserved fault category.

[0007] Optionally, the fault category is divided into shared category and non-shared category, wherein the fault monitoring method further includes: in response to the target fault category being a shared category, storing the current fault information locally in the first control system and executing the step of sending the target fault category to the second control system; in response to the target fault category being a non-shared category, storing the current fault information in the first control system.

[0008] Optionally, the step of sending the target fault category to the second control system includes: in response to the current fault information including multiple fault information, filtering out reported fault information from the multiple fault information, wherein the number of reported fault information is less than the number of the multiple fault information; and sending the target fault category corresponding to the reported fault information to the second control system.

[0009] Optionally, the step of filtering out reported fault information from the multiple fault information includes: determining the first n fault information among the multiple fault information as the reported fault information in the time order of receiving the multiple fault information, wherein n is a positive integer greater than or equal to 1; and / or, determining the first m fault information among the multiple fault information as the reported fault information in the order of the fault handling priority of the multiple fault information from high to low, wherein m is a positive integer greater than or equal to 1.

[0010] Optionally, the fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, the first correspondence represents the correspondence between fault information and the fault identifier, and the second correspondence represents the correspondence between the fault category and the fault identifier, wherein in the first correspondence and the second correspondence, the first control system stores both the first correspondence and the second correspondence, and the second control system only stores the second correspondence.

[0011] Optionally, in the fault correspondence, the fault category is represented by a fault identifier, wherein the step of sending the target fault category to the second control system includes: writing the fault identifier of the target fault category into a preset variable to obtain a fault variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to the fault identifiers in the fault correspondence; and sending the fault variable to the second control system.

[0012] Optionally, the current fault information is received from multiple data sources, and there are multiple second control systems, wherein the fault monitoring method further includes: determining different fault correspondence relationships for different second control systems.

[0013] Optionally, the first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

[0014] A second aspect of the present disclosure provides a fault monitoring method, which is executed in a second control system, and the fault monitoring method includes: receiving a target fault category corresponding to current fault information of a monitored object from a first control system; and performing fault monitoring on the monitored object based on the target fault category, wherein the target fault category is determined by the first control system by receiving current fault information of the monitored object and based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information.

[0015] Optionally, the general fault category also includes a reserved fault category, and the reserved fault category is used to correspond to the newly added fault information to be added to the fault corresponding relationship.

[0016] Optionally, the fault category is divided into shared category and non-shared category, wherein the fault monitoring method further includes: when the target fault category is a shared category, executing the step of receiving the target fault category corresponding to the current fault information of the monitored object from the first control system; when the target fault category is a non-shared category, the current fault information is stored in the first control system.

[0017] Optionally, the step of receiving the target fault category from the first control system includes: when the current fault information includes multiple fault information, receiving the target fault category corresponding to the reported fault information from the first control system, wherein the reported fault information is obtained by filtering the first control system from the multiple fault information, and wherein the number of reported fault information is less than the number of the multiple fault information.

[0018] Optionally, the reported fault information is screened from the multiple fault information in the following manner: according to the time order in which the first control system receives the multiple fault information, the first n fault information among the multiple fault information are determined as the reported fault information, wherein n is a positive integer greater than or equal to 1; and / or, according to the order of the fault handling priority of the multiple fault information from high to low, the first m fault information among the multiple fault information are determined as the reported fault information, wherein m is a positive integer greater than or equal to 1.

[0019] Optionally, the fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, the first correspondence represents the correspondence between fault information and the fault identifier, and the second correspondence represents the correspondence between the fault category and the fault identifier, wherein in the first correspondence and the second correspondence, the first control system stores both the first correspondence and the second correspondence, and the second control system only stores the second correspondence.

[0020] Optionally, in the fault correspondence, the fault category is represented by a fault identifier, wherein the step of receiving the target fault category from the first control system includes: receiving a fault variable from the first control system, wherein the fault variable is obtained by the first control system writing the fault identifier of the target fault category into a preset variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to multiple fault identifiers in the fault correspondence.

[0021] Optionally, the current fault information is received by the first control system from multiple data sources, and there are multiple second control systems, wherein the fault correspondence is different for different second control systems.

[0022] Optionally, the first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

[0023] The third aspect of the present disclosure provides a fault monitoring device, which is applied to a first control system, and includes: a fault receiving unit, which is used to receive current fault information of a monitored object; a determination unit, which is used to determine a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information; a category sending unit, which is used to send the target fault category to a second control system so that the second control system can perform fault monitoring on the monitored object.

[0024] The fourth aspect of the present disclosure provides a fault monitoring device, which is applied to a second control system, and includes: a category receiving unit, which is used to receive a target fault category corresponding to current fault information of a monitored object from a first control system; a monitoring unit, which is used to perform fault monitoring on the monitored object based on the target fault category, wherein the target fault category is determined by the first control system by receiving current fault information of the monitored object and based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information.

[0025] The fifth aspect of the present disclosure provides a fault monitoring system, which includes a first control system and a second control system, wherein the first control system receives current fault information of a monitored object; the first control system determines a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information; the first control system sends the target fault category to the second control system; and the second control system performs fault monitoring on the monitored object based on the target fault category.

[0026] A sixth aspect of the present disclosure provides a wind power generation system, comprising the fault monitoring system according to the exemplary embodiment of the present disclosure.

[0027] A seventh aspect of the present disclosure provides an electronic device, comprising: a processor; a memory, the memory storing computer executable instructions, wherein the computer executable instructions, when executed by the processor, prompt the processor to execute the fault monitoring method according to the exemplary embodiment of the present disclosure.

[0028] An eighth aspect of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is prompted to execute the fault monitoring method according to the exemplary embodiment of the present disclosure.

[0029] According to the fault monitoring method, device, system and wind power generation system disclosed in the present invention, the current fault information can be processed by the first control system to determine the target fault category corresponding to the current fault system, and the target fault category can be sent to the second control system, thereby allowing the second control system to perform fault monitoring based on the target fault category. Among them, the fault information processing of the first control system can allow multiple fault information to be mapped to common fault categories, simplifying the representation of fault information, thereby reducing the processing pressure of the second control system, improving the fault response speed of the second control system, and ensuring the normal operation of the monitored equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 is a schematic diagram illustrating an example application scenario of a fault monitoring method according to an exemplary embodiment of the present disclosure.

[0031] Figure 2 is a schematic flow chart illustrating an example of a fault monitoring method according to an exemplary embodiment of the present disclosure.

[0032] Figure 3 is a schematic flow chart showing the steps of adding a new fault correspondence relationship in a fault monitoring method according to an exemplary embodiment of the present disclosure.

[0033] Figure 4 is a schematic block diagram illustrating a first control system and a second control system according to an exemplary embodiment of the present disclosure.

[0034] Figure 5 is a schematic flowchart illustrating another example of a fault monitoring method according to an exemplary embodiment of the present disclosure.

[0035] Figure 6 is a schematic block diagram illustrating an example of a fault monitoring device according to an exemplary embodiment of the present disclosure.

[0036] Figure 7 is a schematic block diagram illustrating another example of a fault monitoring device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0037] The following specific embodiments are provided to help the reader obtain a comprehensive understanding of the methods, devices and / or systems described herein. However, after understanding the disclosure of the present application, various changes, modifications and equivalents of the methods, devices and / or systems described herein will be clear. For example, the order of operations described herein is only an example and is not limited to those orders set forth herein, but can be changed as will be clear after understanding the disclosure of the present application, except for operations that must occur in a specific order. In addition, for greater clarity and simplicity, the description of features known in the art may be omitted.

[0038] The features described herein can be implemented in different forms and should not be construed as being limited to the examples described herein. Rather, the examples described herein have been provided to illustrate only some of the many possible ways to implement the methods, devices, and / or systems described herein, which will be clear after understanding the disclosure of the present application.

[0039] As used herein, the term "and / or" includes any one of the associated listed items and any combination of any two or more.

[0040] Although terms such as "first", "second", and "third" may be used herein to describe various members, components, regions, layers, or portions, these members, components, regions, layers, or portions should not be limited by these terms. Instead, these terms are only used to distinguish one member, component, region, layer, or portion from another member, component, region, layer, or portion. Therefore, without departing from the teachings of the examples described herein, the first member, first component, first region, first layer, or first portion referred to in the examples may also be referred to as the second member, second component, second region, second layer, or second portion.

[0041] In the specification, when an element (such as a layer, a region, or a substrate) is described as being “on”, “connected to”, or “coupled to” another element, the element may be directly “on”, “connected to”, or “coupled to” another element, or one or more other elements may be present therebetween. Conversely, when an element is described as being “directly on”, “directly connected to”, or “directly coupled to” another element, there may be no other elements present therebetween.

[0042] The terms used herein are only used to describe various examples and are not intended to limit the disclosure. Unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. The terms "comprise", "include" and "have" indicate the presence of the described features, quantities, operations, components, elements and / or combinations thereof, but do not exclude the presence or addition of one or more other features, quantities, operations, components, elements and / or combinations thereof.

[0043] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by a person of ordinary skill in the art to which the present disclosure belongs after understanding the present disclosure. Unless explicitly defined as such herein, terms (such as those defined in a general dictionary) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and should not be interpreted in an idealized or overly formal manner.

[0044] Furthermore, in the description of examples, when it is considered that a detailed description of a well-known related structure or function would cause vague interpretation of the present disclosure, such a detailed description will be omitted.

[0045] As mentioned earlier, as the complexity of equipment systems increases, the number of failures that need to be monitored and addressed also increases accordingly.

[0046] Here, taking wind power generation technology as an example, the trend of large-scale wind turbines is becoming more and more obvious. The cabin height of some units has reached 170 meters. In order to ensure the operation of the units, the perception system is becoming more and more complex and the data processing work is becoming more and more arduous.

[0047] For example, the sensor signal sources in the unit can include vibration, sound, laser, image, electromagnetic, photoelectric, etc. There are dozens of sensor types and hundreds of them. Various perception systems need to operate normally and participate in the control of the unit in real time.

[0048] However, the computing power of traditional unit control systems may not be able to meet the data processing requirements of these perception systems. For example, with the increasing application of visual perception systems in unit monitoring, traditional unit control systems may find it difficult to complete the processing of video data alone, which may lead to a decrease in the response speed to faults and is not conducive to ensuring the normal operation of wind power generation systems.

[0049] The following will describe a fault monitoring method, a fault monitoring device, a fault monitoring system, a wind power generation system, an electronic device, and a computer-readable storage medium provided according to exemplary embodiments of the present disclosure with reference to the accompanying drawings to solve or alleviate at least one of the above-mentioned problems.

[0050] According to a first aspect of the present disclosure, a fault monitoring method is provided. The fault monitoring method can be performed by a device with a computing and analysis function, which can be a terminal device or a server, wherein the terminal device can be a tablet computer, a laptop computer, a digital assistant, etc.; the server can be an independent server, a server cluster, a cloud computing platform, or a virtualization center.

[0051] The following will refer to Figure 1 An example application scenario of the fault monitoring method according to an exemplary embodiment of the present disclosure is described.

[0052] like Figure 1 As shown, the fault monitoring method according to the exemplary embodiment of the present disclosure can be applied to the first control system 110 and the second control system 120. The first control system 110 can communicate with the second control system 120, for example, through the network 130.

[0053] The first control system 110 may receive current fault information of the monitored object, and may determine the target fault category corresponding to the current fault information based on the fault correspondence between the fault information and the fault category. Here, the fault category may include a general fault category, and in the fault correspondence, each general fault category corresponds to a plurality of fault information. The monitored object may be software or hardware, for example, any system, device, component, software, program, etc.

[0054] The first control system 110 may also send the target fault category to the second control system 120 so that the second control system 120 can perform fault monitoring on the monitored object.

[0055] The first control system 110 and the second control system 120 may be control systems for any equipment system. For example, the two may be control systems for different parts of the equipment system, or may be control systems for different control levels of the equipment system. Taking the application scenario of a wind power generation system as an example, the wind power generation system may include a wind farm formed by one or more wind turbines. The first control system 110 may be an auxiliary control system of the wind turbine, and the second control system 120 may include the main control system of the wind turbine and / or the field-level control system of the wind farm where the wind turbine is located. The auxiliary control system may communicate with the main control system and / or the field-level control system to implement the above-mentioned fault monitoring process.

[0056] Here, if Figure 1 As shown, the first control system 110 and the second control system 120 can both be run on any terminal device such as a server, a portable terminal or a desktop computer terminal. The network 130 can be any suitable network, which can include but is not limited to the Internet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wired network such as an optical fiber network and a coaxial cable, and a wireless network such as WIFI, a cellular network, and Bluetooth.

[0057] It should be noted that although the fault monitoring scheme is described here and below using the application scenario of a wind power generation system as an example, the application scenario of the fault monitoring scheme according to the embodiment of the present disclosure is not limited to this. For example, it can also be applied to automated assembly line production equipment systems, etc.

[0058] In the above scenario, by adopting the fault monitoring method according to the embodiment of the present disclosure, the current fault information of the monitored object received can be processed by the first control system, the target fault category corresponding to the current fault system can be determined, and the target fault category can be sent to the second control system. The second control system can perform fault monitoring based on the target fault category. The fault information processing of the first control system can allow multiple fault information to be mapped to common fault categories, simplifying the representation of fault information, thereby reducing the processing pressure of the second control system, improving the fault response speed of the second control system, and ensuring the normal operation of the monitored equipment.

[0059] The following will refer to Figures 2 to 4 A fault monitoring method according to a first aspect of an exemplary embodiment of the present disclosure is described in detail. The fault monitoring method may be executed in a first control system.

[0060] like Figure 2 As shown, the fault monitoring method may include the following steps:

[0061] In step S210, current fault information of the monitored object may be received.

[0062] Here, the monitored object can be hardware or software, which can include but is not limited to device hardware, system software, sensing devices for collecting device hardware information, applications installed in the software system, etc.

[0063] Taking the wind power generation system as an example, the monitored objects may include, but are not limited to: device hardware such as CPU, memory, and hard disk; system software such as Linux system software and sensor data acquisition (hereinafter referred to as "data acquisition") software; sensing devices such as sensors, acquisition boards and channels, and operating condition acquisition measurement points; and application programs such as diagnostic models for diagnosing wind turbine faults.

[0064] However, the monitored object is not limited to the above examples, and the monitored object may be other software or hardware according to actual application scenarios and / or application requirements, and the present disclosure does not impose any particular limitation on this.

[0065] The first control system may acquire current fault information of the monitored object from any process, system or data source. For example, the current fault information may be received from multiple data sources.

[0066] As an example, the first control system may include a fault data center, which may receive and aggregate fault information of each monitored object from different data sources. In addition, the fault data center may also send the received fault information to the second control system, which will be referred to below. Figure 4 Detailed description.

[0067] The current fault information may include detailed information of the fault currently occurring in the monitored object. Here, the fault information is related to the monitored object, which may be determined according to the actual application scenario and / or application needs, and the present disclosure does not impose any particular limitation on this.

[0068] Taking the wind power generation system as an example, the current fault information may include, but is not limited to: the CPU or memory load in the wind turbine generator set exceeds the upper limit, the hardware temperature exceeds the upper limit, the hard disk usage rate exceeds the upper limit, the sensor data acquisition program is abnormal, the working condition data acquisition is abnormal, the working condition data acquisition process does not exist, the diagnostic model scheduler is abnormal, the scheduler process does not exist, the system is abnormal, the vibration sensor X-axis or Y-axis of each blade is abnormal, the tower top sensor X-axis or Y-axis fails, the basic sensor X-axis or Y-axis fails, the main bearing horizontal or vertical vibration sensor fails, the main bearing axial vibration sensor fails, the rear bearing vertical vibration sensor fails, the stator horizontal vibration sensor fails, the vibration sensor channel X-axis or Y-axis of each blade fails, the main bearing horizontal or vertical vibration sensor channel fails, the main bearing axial vibration sensor channel fails, the rear bearing vertical vibration sensor channel fails, the stator horizontal vibration sensor channel fails, the communication of each board card is abnormal, the hub network connection fails, the system-level diagnostic model package runs abnormally, the working condition variable acquisition is abnormal, the data reading fails, the communication between the control systems is abnormal, etc.

[0069] In step S220, the target fault category corresponding to the current fault information may be determined based on the fault correspondence relationship between the fault information and the fault category.

[0070] According to the embodiments of the present disclosure, fault information can be classified to obtain a fault category corresponding to each fault information, and the fault category can, for example, represent a summary of the fault information. For example, when the fault information is "blade vibration sensor channel X-axis failure", the fault category can be "blade vibration sensor or acquisition channel failure".

[0071] The fault correspondence relationship can be given in advance, which can characterize the correspondence between the fault information and the fault category. For example, the fault correspondence relationship can indicate that: the fault information "blade vibration sensor channel X-axis failure" corresponds to the fault category "blade vibration sensor or acquisition channel failure"; the fault information "tower top sensor X-axis failure" corresponds to the fault category "tower top sensor abnormality".

[0072] As an example, the fault correspondence relationship may be, but is not limited to, represented in the form of a table, a graph, or a model, as long as the fault category to which each fault information belongs can be determined according to the fault correspondence relationship. An example of the fault correspondence relationship will be described in detail below with reference to Tables 1 to 3.

[0073] In an embodiment of the present disclosure, the fault category may include a general fault category, and in the fault correspondence relationship, each general fault category may correspond to a variety of fault information.

[0074] For example, there may be fault information a1 "blade vibration sensor channel X-axis failure" and fault information a2 "blade vibration sensor channel Y-axis failure", both of which are related to the blade vibration sensor. For this, a general fault category A "blade vibration sensor or acquisition channel failure" may be constructed, and the general fault category A corresponds to both fault information a1 and fault information a2. When the current fault information is fault information a1 or fault information a2, the target fault category is determined to be fault category A.

[0075] In addition, the fault category may also include a non-general fault category. In the fault correspondence, each non-general fault category may correspond to a unique fault information. For example, there may be fault information b "hard disk usage rate exceeds the upper limit", which may correspond to the non-general fault category B "disk usage exceeds the threshold alarm".

[0076] In this way, the complexity of fault details and fault types can be taken into account, and the fault categories can be trimmed to ensure compatibility with most fault information while minimizing the types of faults sent to the second control system and reducing the pressure on the second control system.

[0077] In addition, as an example, there may be multiple second control systems, and the fault monitoring method may further include: determining different fault correspondences for different second control systems.

[0078] For example, in different fault correspondences, the degree to which the fault category summarizes the same fault information may be different.

[0079] Taking the wind power generation system as an example, the second control system that requires fault information may include the PLC of the unit's main control system and the field-level control system (or field-level server). The display requirements of different systems may be different. For example, the information displayed in the PLC of the main control system needs to be highlighted, and the information displayed in the field-level control system needs to be more generalized than that of the main control system.

[0080] In this regard, for the fault information "blade vibration sensor channel X-axis failure", for the main control system, the fault correspondence relationship can be expressed as: the fault information corresponds to the fault category "blade vibration sensor or acquisition channel failure"; for the field-level control system, the fault correspondence relationship can be expressed as: the fault information corresponds to the fault category "blade sensor failure".

[0081] Although it is described here that the degree of generalization of fault categories in different fault correspondences is different, the embodiments of the present disclosure are not limited to this, and the fault categories may also be different in other aspects. For example, in different fault correspondences, the fault categories may summarize the same fault information differently, such as using different fault codes.

[0082] In this way, by setting different fault correspondences for different second control systems, different second control systems can be distinguished and different fault categories (such as different degrees of summarization of fault information) can be provided to meet the fault monitoring needs of different second control systems.

[0083] In step S230, the target fault category may be sent to the second control system so that the second control system can perform fault monitoring on the monitored object.

[0084] Here, the second control system can be a control system different from the first control system. Taking the wind power generation system as an example, the second control system can be the main control system of the wind turbine generator set such as a programmable logic controller (PLC) or a field-level control system of the wind farm. The first control system can be an auxiliary control system in the wind turbine generator set, which can be used to assist the control of the second control system and reduce the data processing pressure of the second control system.

[0085] In this step, the first control system may send the target fault category to the second control system, so that the second control system may receive summary information of the current fault information, namely, the target fault category, and thus perform fault monitoring on the monitored object.

[0086] According to such a fault monitoring method, the first control system can first analyze and classify the current fault information, and then send the target fault category to the second control system. This makes it unnecessary for the second control system to process and analyze specific fault information, but can directly receive the general fault category. For example, in the case of an abnormality in the X-axis of a blade vibration sensor, the first control system can determine that the blade vibration sensor has an abnormality and inform the second control system. The second control system does not need to know the specific abnormality of the vibration sensor, but only needs to receive the information that "the vibration sensor is abnormal", and can notify the maintenance personnel to maintain the vibration sensor.

[0087] In this way, compared with the traditional control scheme that only analyzes and processes all fault data through the second control system, the above-mentioned fault monitoring method can realize layered or step-by-step processing of fault data by setting up the first control system and the corresponding data processing process, thereby reducing the pressure on the second control system and improving the fault monitoring capability.

[0088] Refer to above Figure 2 An example of a fault monitoring method according to an embodiment of the present disclosure is described, and an example of constructing a fault correspondence relationship will be described in detail below.

[0089] In one example, the fault category may be represented by a fault identifier, which may be, for example, but not limited to, a fault code. Each fault code may represent a fault category, and information on the corresponding fault category may be transmitted by sending the fault code.

[0090] In this example, the fault correspondence may include a first correspondence and a second correspondence. The first correspondence may represent a correspondence between fault information and a fault identifier, and the second correspondence may represent a correspondence between a fault category and a fault identifier.

[0091] Here, in the first correspondence relationship and the second correspondence relationship, the first control system may store both the first correspondence relationship and the second correspondence relationship, and the second control system may store only the second correspondence relationship.

[0092] As an example, the first corresponding relationship and the second corresponding relationship may be in the form of a table, a graph, a model, etc., and the present disclosure does not impose any particular limitation on this. The following description will be made using a table as an example.

[0093] When constructing the first correspondence table, the fields in the table may be determined first. The fields may include an identity document (ID) of a fault code and fault information, thereby allowing the correspondence between each fault code and fault information to be defined in the table. In addition, other fields may be added to the first correspondence table as required, such as but not limited to the ID of the monitored object, the brief name of the fault information, and remarks information.

[0094] Table 1 below gives an example of a field definition table for constructing a first correspondence. As shown in Table 1, the table of the first correspondence may include a "monitoring point ID" field, a "fault code ID" field, a "fault abbreviated name" field, a "fault information" field, and a "remarks" field, wherein the "monitoring point ID" field is used to record the ID of the monitored object; the "fault code ID" field is used to record the ID of the fault code; the "fault abbreviated name" field is used to record the brief name of the monitoring point fault; the "fault information" field is used to record the fault description of the monitoring point; and the "remarks" field is used to record other remark information related to the fault.

[0095] Table 1

[0096]

[0097] In addition, in the field definition table, you can also define the type of each field and the field notes of each field. The field notes can record information related to the field.

[0098] For example, the "monitoring point ID" field may be a unique identifier in the first correspondence table, which may be obtained, for example, by subscribing to data in a system alarm item in a control system.

[0099] The "fault code ID" field can correspond to the fault code ID in the second correspondence table. For example, the fault code ID of the second correspondence table can be determined first, and then the fault code ID of the second correspondence table can be used as the fault code ID of the first correspondence table. The process of determining the fault code ID of the second correspondence table will be described below.

[0100] The "monitoring point abbreviation name" field can be used to conveniently display the fault name in the terminal interface. It can be generated from the channel of the configuration table based on the content of the control system's drive table. For example, it can be named in the format of "Model+_+VarName", where "Model" represents the model ID or channel definition in the drive table, and "VarName" can represent any given variable value. For example, for the fault information "blade 1# vibration sensor X-axis abnormality", the monitoring point abbreviation name can be "BLADE1_X", where "BLADE1" is the name of the blade 1# vibration sensor in the drive table, and "X" can represent the X-axis.

[0101] The "monitoring point description" field can be predefined according to the monitored objects such as core hardware and system software. For example, the sensor part can come from the varname_all variable in the control program, and the diagnostic model can come from the name_ch variable in the model.ini file of the control program.

[0102] It should be noted that Table 1 shown above is only an example for constructing a first correspondence table, and the fields and field notes therein are all examples. Fields and field notes can also be added, deleted or modified according to actual needs. It is also possible not to construct the above Table 1 and directly construct the first correspondence table, as long as the first correspondence table can represent the correspondence between fault information and fault identification.

[0103] Here, taking the fields defined in the above Table 1 as an example, in the application scenario of a wind power generation system, the first corresponding relationship may be in the form of the following Table 2, for example.

[0104] Table 2

[0105]

[0106]

[0107]

[0108] The above Table 2 can be used as a fault monitoring information table, which gives the corresponding relationship between each fault information and the fault code ID. For example, the fault information "CPU load exceeds the upper limit" corresponds to the fault code ID "0".

[0109] In addition, when constructing the second correspondence table, the fault category can be determined first, and the fault code corresponding to each fault category can be determined. As an example, the second correspondence can have the form of the following Table 3. The table can be used as a fault code table to display the fault category description, and the table can be stored in both the first control system and the second control system.

[0110] Table 3

[0111]

[0112] As shown in Tables 2 and 3 above, the first correspondence table and the second correspondence table can be associated through the fault code ID, which represents the fault category, wherein each general fault category can correspond to multiple fault information, as shown in Table 2, the fault code IDs "0", "8", "9", etc. representing general fault categories can correspond to multiple fault information, and the general fault categories represented by these fault code IDs are recorded in Table 3, for example, the fault code ID "8" represents the general fault category "No. 1 blade sensor or acquisition channel abnormality".

[0113] In this way, by storing both the first correspondence and the second correspondence in the first control system and only storing the second correspondence in the second control system, and linking the first correspondence and the second correspondence through a fault identifier, the fault information of the first control system and the second control system can be synchronized, and by separately establishing the first correspondence and the second correspondence, when the fault information needs to be modified or deleted, such as when the drive table is upgraded, the diagnostic model is updated and deleted, only the first correspondence can be modified without modifying the second correspondence, thereby eliminating the need to perform an update at the second control system, further simplifying the operation of the second control system.

[0114] However, the exemplary embodiments of the present disclosure are not limited thereto. In another example, the fault category may also be a text description. For example, the fault correspondence may include a "fault category" field and a "fault information" field. The fault correspondence may be stored only in the first control system, but not in the second control system. After the first control system determines the target fault category corresponding to the current fault information according to the fault correspondence, it may send the target fault category to the second control system, and the second control system may directly display the content of the target fault category. In this example, the management of the fault correspondence is more flexible and convenient. The second control system may directly obtain the fault category without analyzing the content received from the first control system, which may further reduce the processing pressure of the second control system.

[0115] The above describes an example in which the fault correspondence is in a table format, however, the format is not limited thereto, and may be, for example, a graph or a model.

[0116] For example, the nodes in the graph can represent "fault category" and "fault information", and the edges between the nodes can connect the corresponding "fault category" and "fault information" to represent the corresponding relationship between the two. As an example, the above Table 2 and Table 3 can be converted into a graph to obtain the first corresponding relationship and the second corresponding relationship in the graph form.

[0117] For another example, a relational model may be pre-built, where the input of the relational model may be fault information, and the output of the relational model may be a fault category. The relational model may be a rule model developed based on expert experience, or a machine learning model obtained through training, such as a classification model for classifying fault information.

[0118] In addition, according to an embodiment of the present disclosure, when the fault category is represented by a fault identifier, in the above step S330, the fault identifier of the target fault category can be written into a preset variable to obtain a fault variable, and the fault variable is sent to the second control system.

[0119] Here, the preset variable may have multiple bits, and the multiple bits may correspond one-to-one to the fault identifiers in the fault correspondence relationship.

[0120] As an example, the preset variable may be a dword variable, which may have 64 bits, and the value of each bit may be "0" or "1", and the number of fault identifiers may be limited to 64, so that each bit of the dword variable corresponds to a fault identifier, that is, corresponds to a type of fault information, and all fault identifiers may be represented by a dword variable, and faults occurring simultaneously may all be represented by a dword variable. For example, the fault identifiers of simultaneous faults may be "1", "2", and "3", and in this regard, the first, second, and third bits in the dword variable may be set to "1", and the other 61 bits may be set to "0" to indicate that the fault identifiers of the faults occurring are "1", "2", and "3".

[0121] In this way, by using multiple bits of a variable to represent the fault identifier in a one-to-one correspondence, the first control system only needs to send fault data (for example, a fault variable) once, thereby ensuring the high efficiency of the system.

[0122] It should be noted that the preset variable is not limited to the above examples, and may also be other variables, such as a 32-bit variable, as long as all fault identifiers can be represented by one variable.

[0123] Relevant examples of general fault categories are described above. In addition, according to the embodiments of the present disclosure, fault categories for newly added faults may be reserved in the general fault categories.

[0124] For example, the general fault category may include a reserved fault category, and the reserved fault category may be used to correspond to the newly added fault information.

[0125] like Figure 3 As shown, the fault monitoring method may further include: step S310, obtaining new fault information to be added to the fault corresponding relationship; step S320, determining the new fault information as corresponding to the reserved fault category.

[0126] Specifically, with the update or operation needs of the equipment system, the monitored objects in the equipment system may change, and some monitored objects and corresponding fault information may be added. For example, sensors, boards and channels in hardware, applications in software, diagnostic models, etc. may change, such as new items in the driver table, new diagnostic models, etc. In this regard, reserved fault categories corresponding to these newly added fault information can be set in the fault correspondence, so that the dynamic update of fault monitoring items can be realized, which greatly improves the flexibility of fault monitoring.

[0127] Here, the reserved fault category can be one or more, and according to the fault category of the newly added fault information, it can be mapped to the corresponding reserved fault category. For example, taking the above Table 3 as an example, the reserved fault category can include "other core software abnormalities", "other blade abnormalities", "other tower abnormalities", etc. In the case where the newly added fault information is related to the blade, the newly added fault information can be determined as corresponding to the reserved fault category "other blade abnormalities". In this way, even if the fault in the first control system comes from different data sources and the data source is variable, it is possible to realize the addition of new data sources and related fault data by setting the reserved fault category in the fault correspondence, thereby improving the flexibility of fault monitoring.

[0128] In addition, in the exemplary embodiments of the present disclosure, on the one hand, a distinction is made between general fault categories and non-general fault categories, so that specific fault categories, i.e., non-general fault categories, can be given for some critical or core software and hardware, while for some general and universal faults, multiple faults can be combined into one fault category. For example, as shown in Tables 2 and 3, for software faults, only three fault code IDs "0", "1" and "2" can be assigned, which can be used to represent multiple software faults; and for relatively important working condition data acquisition anomalies and working condition data acquisition process non-existence, a fault code ID "5" can be assigned separately; for diagnostic model scheduler anomalies and scheduler process non-existence, a fault code ID "6" can be assigned separately. On the other hand, reserved fault categories can be further designed in the general fault category, so that while taking into account the core faults, as many faults that really need attention as possible are described.

[0129] In addition, according to the embodiments of the present disclosure, the fault category may be selectively sent according to actual needs.

[0130] For example, fault categories can be divided into shared categories and non-shared categories. In this case, the fault monitoring method may also include: in response to the target fault category being a shared category, the current fault information may be stored locally in the first control system, and the step of sending the target fault category to the second control system may be executed; in response to the target fault category being a non-shared category, the current fault information may be stored in the first control system.

[0131] Here, the shared category may be a fault category that is sent from the first control system to the second control system, and the non-shared category may be a fault category that is not sent from the first control system to the second control system.

[0132] In the above steps, "storing the current fault information in the first control system" may mean storing the current fault information in the first control system without performing the step of transmitting the target fault category to the second control system.

[0133] Taking Tables 2 and 3 above as an example, the fault category "general system abnormality" can be a non-shared category, and its fault code ID is "0". Therefore, even if the first control system receives the fault information "CPU load exceeds the upper limit" or "memory load exceeds the upper limit", the corresponding fault category (for example, fault code ID "0") will not be sent to the second control system, but the fault information will be stored in the first control system.

[0134] The other fault categories in Table 2 and Table 3 may be shared categories. When the first control system determines that the target fault category corresponding to the current fault information is a shared category, the current fault information may be stored locally in the first control system, and the target fault category may be sent to the second control system.

[0135] Through the above method, fault categories can be distinguished, and fault categories related to the second control system can be sent, while fault categories unrelated to the second control system or fault categories that do not need to be monitored by the second control system may not be shared with the second control system, thereby optimizing the coordination between different control systems. In particular, when there are multiple second control systems, fault categories can be sent according to the needs of each second control system to avoid meaningless communication and waste of communication resources.

[0136] In addition, as an example, the current fault information described above may include one or more fault information. When the current fault information is one, the target fault category corresponding to the current fault information may be sent to the second control system. When the current fault information is multiple, the target fault category corresponding to a portion of the multiple fault information may be sent to the second control system.

[0137] Specifically, in step S230, in response to the current fault information including multiple fault information, reported fault information can be screened out from the multiple fault information, and the target fault category corresponding to the reported fault information can be sent to the second control system. Here, the number of reported fault information can be less than the number of multiple fault information.

[0138] In an equipment system, multiple faults that occur simultaneously may be related. For example, the operating status of a faulty device may affect the status of associated devices in its lower layer or subsequent processes, which may cause fault alarms on associated devices. In fact, the associated device itself may not be abnormal. In this regard, after the fault of the faulty device is eliminated, the fault alarms on the associated devices will disappear accordingly, and there is no need to perform any maintenance on the associated devices.

[0139] The above screening process can avoid wasting maintenance resources by troubleshooting all alarm devices when associated faults occur, reduce the frequent triggering of faults, increase the triggering logic and quantity limit, and reduce the processing pressure on the second control system.

[0140] For example, assuming that 10 faults occur in the equipment system, accordingly, the current fault information may include 10 fault information. The first control system may only send the fault categories of 3 of the fault information to the second control system. The second control system only needs to handle 3 faults. After handling these 3 faults, the alarms for the other 7 faults may also disappear. Therefore, the second control system does not need to adopt a processing strategy for the other 7 faults, thereby reducing the workload of the second control system and saving fault maintenance resources.

[0141] In the above screening process, the step of screening out reported fault information from multiple fault information may include: determining the first n fault information among the multiple fault information as reported fault information in the time order of receiving the multiple fault information, wherein n is a positive integer greater than or equal to 1; and / or, determining the first m fault information among the multiple fault information as reported fault information in the order of the fault handling priority of the multiple fault information from high to low, wherein m is a positive integer greater than or equal to 1.

[0142] Specifically, in one example, the target fault categories of n fault information received first can be sent to the second control system according to the order in which the fault information is received by the first control system; alternatively or additionally, in another example, the target fault categories of m fault information with higher priority can be sent to the second control system according to the priority of the fault information received by the first control system.

[0143] In this way, determining the reported fault information according to the time sequence and / or priority can help locate the critical or core faults. Other faults may be related faults of the critical or core faults. By giving priority to solving such critical or core faults, other faults may also disappear accordingly, thereby eliminating the current multiple faults as quickly and accurately as possible.

[0144] It should be noted that, although it is described above that the reported fault information is determined according to the time sequence and / or priority, the embodiments of the present disclosure are not limited to this, and the reported fault information can also be determined according to other methods, or the reported fault information can be randomly screened out. Since the number of reported fault information is less than the number of all fault information, the workload of the second control system can be reduced.

[0145] The above describes the fault monitoring method according to the exemplary embodiment of the present disclosure. Figure 4An example fault monitoring system to which the method is applied is described.

[0146] like Figure 4 As shown, the fault monitoring system may include a first control system 110 and a second control system 120. The first control system 110 may include a first control system operation and maintenance tool, a fault data center, a hardware resource monitoring process, a model scheduling program, a working condition data collection process, and other core processes. The second control system 120 may include a main control system PLC of a wind turbine generator set and a field-level control system of a wind farm.

[0147] Here, the first control system operation and maintenance tool can be a display terminal of the first control system 110, which can be used by maintenance personnel to operate the first control system. The hardware resource monitoring process, the model scheduling program, the working condition data collection process and other core processes can be used to collect or record the operating status of the monitored object, such as whether a fault occurs.

[0148] The fault data center can receive fault monitoring content from different processes. For example, the monitoring of core hardware and system software requires special monitoring software monitoring and fault alarm, the monitoring of sensors can be monitored by data acquisition software, the monitoring of working condition acquisition points can be monitored by working condition acquisition programs, and the operation monitoring of diagnostic models can be monitored by schedulers, etc. The fault data center can be used as a fault management module to manage all faults, and provide fault data for other applications or systems that need to understand the operation of the system itself.

[0149] by Figure 4 For example, the fault data center can receive current fault information from the hardware resource monitoring process, the model scheduling program, the working condition data collection process and other core processes, and can process the fault information, such as executing the above-mentioned fault monitoring method, and then send the processed information to the first control system operation and maintenance tool and the second control system, for example, the current fault information can be sent to the first control system operation and maintenance tool, and the above-mentioned target fault category can be sent to the second control system. As an example, the fault data center can be implemented by the Redis system, which is a key-value storage system that can be used to store and publish fault information to ensure timely updating and publishing of fault messages.

[0150] like Figure 4 As shown, by setting up a fault data center in the first control system 110, data from different processes and different systems can be shared, and the data source, data center and data user can be completely decoupled, and the three-layer components of data storage, fault monitoring program and data display can be decoupled, which is convenient for subsequent program design and allows arbitrary addition and deletion of data sources and data display programs.

[0151] After detecting an abnormal fault, the fault information can be saved locally in the fault data center to facilitate later problem tracking, and the fault information can also be obtained by subscribing to the fault data center through other systems for real-time viewing. Fault information can be published once each time it is triggered, and can be recorded locally after checking that the abnormality disappears, and the fault list is updated. Among them, the abnormal signals detected by the system and the equipment abnormalities discovered by the diagnostic model through the diagnostic algorithm are independent of each other and do not interfere with each other.

[0152] As described above, the first control system can receive current fault information from multiple data sources, and can provide processed fault information to multiple second control systems, thereby realizing coordination from multiple data sources to multiple control systems, and can send data according to the needs of each second control system, thereby improving data transmission efficiency.

[0153] According to an exemplary embodiment of the present disclosure, the current fault information is processed by the first control system, the target fault category corresponding to the current fault system is determined, and the target fault category is sent to the second control system, thereby reducing the processing pressure of the second control system, improving the fault response speed of the second control system, and ensuring the normal operation of the monitored equipment.

[0154] In addition, according to the fault monitoring method of the exemplary embodiment of the present disclosure, the first corresponding relationship and the second corresponding relationship can be designed separately, which can allow the first corresponding relationship to be updated without changing the second corresponding relationship. In this way, the need for dynamic transformation of fault information is solved and the communication pressure between the first control system and the second control system is alleviated.

[0155] In addition, according to the fault monitoring method of the exemplary embodiment of the present disclosure, the first control system can send the fault category of the current fault information to the second control system, so that the fault data of different control systems can be displayed synchronously. For example, taking the wind power generation system as an example, the field level, the unit main control system, and the auxiliary control terminal can be displayed synchronously, which provides the possibility to discover and solve the fault as soon as possible.

[0156] According to a second aspect of the present disclosure, a fault monitoring method is provided, which can be executed in a second control system. Figure 5 As shown, the fault monitoring method may include the following steps:

[0157] In step S510, a target fault category corresponding to current fault information of a monitored object may be received from a first control system.

[0158] In step S520, fault monitoring may be performed on the monitored object based on the target fault category.

[0159] Here, the target fault category is determined by the first control system by receiving current fault information of the monitored object and based on the fault correspondence between the fault information and the fault category. The fault category includes a general fault category, in which each general fault category corresponds to multiple fault information.

[0160] As an example, the general fault category also includes a reserved fault category, and the reserved fault category is used to correspond to the newly added fault information to be added to the fault corresponding relationship.

[0161] As an example, fault categories are divided into shared categories and non-shared categories, wherein the fault monitoring method further includes: when the target fault category is a shared category, executing the step of receiving a target fault category corresponding to current fault information of the monitored object from the first control system; when the target fault category is a non-shared category, the current fault information is stored in the first control system.

[0162] As an example, the step of receiving a target fault category from the first control system includes: when the current fault information includes multiple fault information, receiving a target fault category corresponding to the reported fault information from the first control system, wherein the reported fault information is obtained by screening the first control system from multiple fault information, and wherein the number of reported fault information is less than the number of multiple fault information.

[0163] As an example, reported fault information is screened from multiple fault information in the following manner: according to the time order in which the first control system receives the multiple fault information, the first n fault information among the multiple fault information is determined as reported fault information, where n is a positive integer greater than or equal to 1; and / or, according to the order of fault handling priority of the multiple fault information from high to low, the first m fault information among the multiple fault information is determined as reported fault information, where m is a positive integer greater than or equal to 1.

[0164] As an example, the fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, the first correspondence represents the correspondence between the fault information and the fault identifier, and the second correspondence represents the correspondence between the fault category and the fault identifier, wherein, in the first correspondence and the second correspondence, the first control system stores both the first correspondence and the second correspondence, and the second control system only stores the second correspondence.

[0165] As an example, in the fault correspondence relationship, the fault category is represented by a fault identifier, wherein the step of receiving the target fault category from the first control system includes: receiving a fault variable from the first control system, wherein the fault variable is obtained by the first control system writing the fault identifier of the target fault category into a preset variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to the multiple fault identifiers in the fault correspondence relationship.

[0166] As an example, the current fault information is received by the first control system from multiple data sources, and there are multiple second control systems, wherein the fault correspondence is different for different second control systems.

[0167] As an example, the first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

[0168] In this exemplary embodiment, the various steps and functions in the fault monitoring method are the same as those in the above reference Figures 1 to 4 The embodiments described are similar / identical, so they will not be described again here.

[0169] According to a third aspect of the present disclosure, a fault monitoring device is provided, the fault monitoring device being applied to a first control system, such as Figure 6 As shown, the fault monitoring device includes a fault receiving unit 610 , a determining unit 620 and a category sending unit 630 .

[0170] The fault receiving unit 610 is used to receive current fault information of the monitored object.

[0171] The determination unit 620 is used to determine the target fault category corresponding to the current fault information based on the fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information.

[0172] The category sending unit 630 is used to send the target fault category to the second control system so that the second control system can perform fault monitoring on the monitored object.

[0173] As an example, the general fault category includes a reserved fault category, wherein the fault monitoring device further includes: a new fault acquisition unit, used to obtain new fault information to be added to the fault correspondence relationship; an information corresponding unit, used to determine the new fault information as corresponding to the reserved fault category.

[0174] As an example, fault categories are divided into shared categories and non-shared categories, wherein, in response to the target fault category being a shared category, the category sending unit 630 is used to store the current fault information locally in the first control system and execute the step of sending the target fault category to the second control system; in response to the target fault category being a non-shared category, the category sending unit 630 is used to store the current fault information in the first control system.

[0175] As an example, the category sending unit 630 is also used to: in response to the current fault information including multiple fault information, filter out reported fault information from the multiple fault information, wherein the number of reported fault information is less than the number of multiple fault information; and send the target fault category corresponding to the reported fault information to the second control system.

[0176] As an example, the category sending unit 630 is also used to: determine the first n fault information among the multiple fault information as reported fault information in the time order in which the multiple fault information are received, where n is a positive integer greater than or equal to 1; and / or, determine the first m fault information among the multiple fault information as reported fault information in the order of the fault handling priority of the multiple fault information from high to low, where m is a positive integer greater than or equal to 1.

[0177] As an example, the fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, the first correspondence represents the correspondence between the fault information and the fault identifier, and the second correspondence represents the correspondence between the fault category and the fault identifier, wherein, in the first correspondence and the second correspondence, the first control system stores both the first correspondence and the second correspondence, and the second control system only stores the second correspondence.

[0178] As an example, in the fault correspondence relationship, the fault category is represented by a fault identifier, wherein the category sending unit 630 is also used to: write the fault identifier of the target fault category into a preset variable to obtain a fault variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to the fault identifiers in the fault correspondence relationship; and send the fault variable to the second control system.

[0179] As an example, the current fault information is received from multiple data sources, and there are multiple second control systems, wherein the fault monitoring device further includes: a correspondence determination unit, which is used to determine different fault correspondences for different second control systems.

[0180] As an example, the first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

[0181] Regarding the device in the above embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

[0182] According to a fourth aspect of the present disclosure, a fault monitoring device is provided, the fault monitoring device being applied to a second control system, such as Figure 7 As shown, the fault monitoring device includes a category receiving unit 710 and a monitoring unit 720 .

[0183] The category receiving unit 710 is used to receive a target fault category corresponding to current fault information of the monitored object from the first control system.

[0184] The monitoring unit 720 is used to perform fault monitoring on the monitored object based on the target fault category.

[0185] Here, the target fault category is determined by the first control system by receiving current fault information of the monitored object and based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, in which each general fault category corresponds to a plurality of fault information.

[0186] As an example, the general fault category also includes a reserved fault category, and the reserved fault category is used to correspond to the newly added fault information to be added to the fault corresponding relationship.

[0187] As an example, fault categories are divided into shared categories and non-shared categories, wherein, when the target fault category is a shared category, the category receiving unit 710 is used to execute the step of receiving a target fault category corresponding to the current fault information of the monitored object from the first control system; when the target fault category is a non-shared category, the current fault information is stored in the first control system.

[0188] As an example, the category receiving unit 710 is also used to: when the current fault information includes multiple fault information, receive the target fault category corresponding to the reported fault information from the first control system, wherein the reported fault information is obtained by screening the first control system from multiple fault information, and wherein the number of reported fault information is less than the number of multiple fault information.

[0189] As an example, reported fault information is screened from multiple fault information in the following manner: according to the time order in which the first control system receives the multiple fault information, the first n fault information among the multiple fault information is determined as reported fault information, where n is a positive integer greater than or equal to 1; and / or, according to the order of fault handling priority of the multiple fault information from high to low, the first m fault information among the multiple fault information is determined as reported fault information, where m is a positive integer greater than or equal to 1.

[0190] As an example, the fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, the first correspondence represents the correspondence between the fault information and the fault identifier, and the second correspondence represents the correspondence between the fault category and the fault identifier, wherein, in the first correspondence and the second correspondence, the first control system stores both the first correspondence and the second correspondence, and the second control system only stores the second correspondence.

[0191] As an example, in the fault correspondence relationship, the fault category is represented by a fault identifier, wherein the category receiving unit 710 is also used to: receive a fault variable from the first control system, wherein the fault variable is obtained by the first control system writing the fault identifier of the target fault category into a preset variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to the multiple fault identifiers in the fault correspondence relationship.

[0192] As an example, the current fault information is received by the first control system from multiple data sources, and there are multiple second control systems, wherein the fault correspondence is different for different second control systems.

[0193] As an example, the first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

[0194] Regarding the device in the above embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

[0195] According to a fifth aspect of the present disclosure, a fault monitoring system is provided. As an example, the fault monitoring system may be as follows: Figure 1 and Figure 4 The system shown.

[0196] The fault monitoring system may include a first control system and a second control system.

[0197] The first control system can receive current fault information of the monitored object, and determine the target fault category corresponding to the current fault information based on the fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to multiple fault information.

[0198] The first control system may send the target fault category to the second control system.

[0199] The second control system may perform fault monitoring on the monitored object based on the target fault category.

[0200] In this exemplary embodiment, the structures of the first control system and the second control system and the methods and functions performed are the same as those described above. Figures 1 to 4 The embodiments described are similar / identical, so they will not be described again here.

[0201] According to a sixth aspect of the present disclosure, a wind power generation system is provided. The wind power generation system may include a fault monitoring system according to an exemplary embodiment of the present disclosure.

[0202] For example, the wind power generation system may include a wind farm, which may include at least one wind turbine generator set. The first control system may be an auxiliary control system of the wind turbine generator set, and the second control system may include a main control system of the wind turbine generator set and / or a field-level control system of the wind farm.

[0203] According to a seventh aspect of the present disclosure, an electronic device is provided, the electronic device comprising: a processor; a memory, the memory storing computer executable instructions, wherein the computer executable instructions, when executed by the processor, prompt the processor to execute the fault monitoring method described in the exemplary embodiment of the present disclosure.

[0204] As an example, the electronic device can be a PC computer, a tablet device, a personal digital assistant, a smart phone or other devices capable of executing the above-mentioned instruction set. Here, the electronic device is not necessarily a single electronic device, but can also be any device or circuit that can execute the above-mentioned instruction (or instruction set) individually or jointly. The electronic device can also be a part of an integrated control system or a system manager, or can be configured to be a portable electronic device interconnected with an interface locally or remotely (for example, via wireless transmission). In addition, the electronic device can also include a video display (such as, a liquid crystal display) and a user interaction interface (such as, a keyboard, a mouse, a touch input device, etc.). All components of the electronic device can be connected to each other via a bus and / or a network.

[0205] The processor may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller or a microprocessor. As an example and not limitation, the processor may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, etc.

[0206] The processor can execute instructions or codes stored in the memory, wherein the memory can also store data. Instructions and data can also be sent and received through the network via the network interface device, wherein the network interface device can adopt any known transmission protocol.

[0207] The memory may be integrated with the processor, for example, RAM or flash memory is arranged within an integrated circuit microprocessor or the like. In addition, the memory may include a separate device, such as an external disk drive, a storage array, or any other storage device that can be used by a database system. The memory and the processor may be operatively coupled, or may communicate with each other, such as through an I / O port, a network connection, etc., so that the processor can read files stored in the memory.

[0208] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor, the processor is prompted to execute the fault monitoring method according to the exemplary embodiment of the present disclosure.

[0209] Specifically, the fault monitoring method according to the embodiment of the present disclosure can be written as a computer program and stored on a computer-readable storage medium. Examples of computer-readable storage media include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disk storage, hard disk drive (HDD), solid state drive (SSD), card storage (such as, multimedia card, secure digital (SD) card or extreme digital (XD) card), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid state disk and any other device, any other device is configured to store computer program and any associated data, data files and data structures in a non-transitory manner and provide the computer program and any associated data, data files and data structures to a processor or computer so that the processor or computer can execute the computer program. In one example, the computer program and any associated data, data files and data structures are distributed on a networked computer system so that the computer program and any associated data, data files and data structures are stored, accessed and executed in a distributed manner by one or more processors or computers.

[0210] The specific implementation methods of the present disclosure have been described in detail above. Although some embodiments have been shown and described, those skilled in the art should understand that these embodiments may be modified and varied without departing from the principles and spirit of the present disclosure, the scope of which is defined by the claims and their equivalents. These modifications and variations should also be within the scope of protection of the claims of the present disclosure.

Claims

1. A fault monitoring method, characterized in that: The fault monitoring method is executed in the first control system, and the fault monitoring method includes: Receive current fault information of the monitored object; Determine a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to a plurality of fault information; The target fault category is sent to a second control system so that the second control system can perform fault monitoring on the monitored object.

2. The fault monitoring method according to claim 1, characterized in that: The general fault category includes a reserved fault category, wherein the fault monitoring method further includes: Acquire new fault information to be added to the fault corresponding relationship; The newly added fault information is determined to correspond to the reserved fault category.

3. The fault monitoring method according to claim 1, characterized in that: The fault categories are divided into shared and non-shared categories. Wherein, the fault monitoring method further includes: In response to the target fault category being a shared category, storing the current fault information locally in the first control system, and performing the step of sending the target fault category to a second control system; In response to the target fault category being a non-shared category, the current fault information is stored in the first control system.

4. The fault monitoring method according to claim 1, characterized in that: The step of sending the target fault category to the second control system comprises: In response to the current fault information including a plurality of fault information, filtering out reported fault information from the plurality of fault information, wherein the number of reported fault information is less than the number of the plurality of fault information; The target fault category corresponding to the reported fault information is sent to the second control system.

5. The fault monitoring method according to claim 4, characterized in that: The step of filtering out the reported fault information from the multiple fault information includes: According to the time sequence of receiving the multiple fault information, determine the first n fault information among the multiple fault information as the reported fault information, where n is a positive integer greater than or equal to 1; and / or According to the order of the fault processing priorities of the multiple fault information from high to low, first m fault information among the multiple fault information are determined as the reported fault information, where m is a positive integer greater than or equal to 1.

6. The fault monitoring method according to claim 1, characterized in that: The fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, wherein the first correspondence represents a correspondence between fault information and the fault identifier, and the second correspondence represents a correspondence between the fault category and the fault identifier. Among them, in the first corresponding relationship and the second corresponding relationship, the first control system stores both the first corresponding relationship and the second corresponding relationship, and the second control system only stores the second corresponding relationship.

7. The fault monitoring method according to claim 1, characterized in that: In the fault correspondence, the fault category is represented by a fault identifier, wherein the step of sending the target fault category to the second control system includes: Writing the fault identifier of the target fault category into a preset variable to obtain a fault variable, wherein the preset variable has a plurality of bits, and the plurality of bits correspond one-to-one to the fault identifiers in the fault correspondence relationship; The fault variable is sent to the second control system.

8. The fault monitoring method according to claim 1, characterized in that: The current fault information is received from multiple data sources, the second control system is multiple, wherein the fault monitoring method further includes: Different fault corresponding relationships are determined for different second control systems.

9. The fault monitoring method according to any one of claims 1 to 8, characterized in that: The first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

10. A fault monitoring method, characterized in that: The fault monitoring method is executed in the second control system, and the fault monitoring method includes: receiving, from the first control system, a target fault category corresponding to current fault information of the monitored object; Based on the target fault category, performing fault monitoring on the monitored object, The target fault category is determined by the first control system by receiving current fault information of the monitored object and based on a fault correspondence relationship between the fault information and the fault category. The fault categories include general fault categories, and in the fault correspondence, each general fault category corresponds to multiple types of fault information.

11. The fault monitoring method according to claim 10, characterized in that: The general fault category also includes a reserved fault category, and the reserved fault category is used to correspond to the newly added fault information to be added to the fault corresponding relationship.

12. The fault monitoring method according to claim 10, characterized in that: The fault categories are divided into shared and non-shared categories. Wherein, the fault monitoring method further includes: In the case where the target fault category is a shared category, performing the step of receiving, from the first control system, a target fault category corresponding to current fault information of the monitored object; In a case where the target fault category is a non-shared category, the current fault information is stored in the first control system.

13. The fault monitoring method according to claim 10, characterized in that: The step of receiving the target fault category from the first control system comprises: In the case where the current fault information includes a plurality of fault information, receiving a target fault category corresponding to the reported fault information from the first control system, The reported fault information is obtained by screening the first control system from the multiple fault information, wherein the number of the reported fault information is less than the number of the multiple fault information.

14. The fault monitoring method according to claim 13, characterized in that: The reported fault information is obtained by screening from the multiple fault information in the following manner: According to the time sequence in which the first control system receives the multiple fault information, determining the first n fault information among the multiple fault information as the reported fault information, wherein n is a positive integer greater than or equal to 1; and / or According to the order of the fault processing priorities of the multiple fault information from high to low, first m fault information among the multiple fault information are determined as the reported fault information, where m is a positive integer greater than or equal to 1.

15. The fault monitoring method according to claim 10, characterized in that: The fault category is represented by a fault identifier, and the fault correspondence includes a first correspondence and a second correspondence, wherein the first correspondence represents a correspondence between fault information and the fault identifier, and the second correspondence represents a correspondence between the fault category and the fault identifier. Among them, in the first corresponding relationship and the second corresponding relationship, the first control system stores both the first corresponding relationship and the second corresponding relationship, and the second control system only stores the second corresponding relationship.

16. The fault monitoring method according to claim 10, characterized in that: In the fault correspondence, the fault category is represented by a fault identifier, wherein the step of receiving the target fault category from the first control system includes: receiving a fault variable from said first control system, The fault variable is obtained by the first control system writing the fault identifier of the target fault category into a preset variable, wherein the preset variable has multiple bits, and the multiple bits correspond one-to-one to multiple fault identifiers in the fault correspondence relationship.

17. The fault monitoring method according to claim 10, characterized in that: The current fault information is received by the first control system from multiple data sources, and there are multiple second control systems, wherein the fault correspondence is different for different second control systems.

18. The fault monitoring method according to any one of claims 10 to 17, characterized in that: The first control system is an auxiliary control system of the wind turbine generator set, and the second control system includes a main control system of the wind turbine generator set and / or a field-level control system of a wind farm where the wind turbine generator set is located.

19. A fault monitoring device, characterized in that: The fault monitoring device is applied to the first control system, and the fault monitoring device comprises: A fault receiving unit, used for receiving current fault information of the monitored object; a determination unit, configured to determine a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to a plurality of fault information; The category sending unit is used to send the target fault category to the second control system so that the second control system can perform fault monitoring on the monitored object.

20. A fault monitoring device, characterized in that: The fault monitoring device is applied to the second control system, and the fault monitoring device comprises: A category receiving unit, configured to receive a target fault category corresponding to current fault information of the monitored object from the first control system; a monitoring unit, configured to perform fault monitoring on the monitored object based on the target fault category, The target fault category is determined by the first control system by receiving current fault information of the monitored object and based on a fault correspondence relationship between the fault information and the fault category. The fault categories include general fault categories, and in the fault correspondence, each general fault category corresponds to multiple types of fault information.

21. A fault monitoring system, characterized in that: The fault monitoring system includes a first control system and a second control system. The first control system receives current fault information of the monitored object; The first control system determines a target fault category corresponding to the current fault information based on a fault correspondence relationship between the fault information and the fault category, wherein the fault category includes a general fault category, and in the fault correspondence relationship, each general fault category corresponds to a plurality of fault information; The first control system sends the target fault category to a second control system; The second control system performs fault monitoring on the monitored object based on the target fault category.

22. A wind power generation system, characterized in that: The wind power generation system comprises the fault monitoring system according to claim 21.

23. An electronic device, characterized in that: The electronic device comprises: processor; a memory storing computer executable instructions, Wherein, when the computer executable instructions are executed by the processor, the processor is prompted to execute the fault monitoring method as described in any one of claims 1-18.

24. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is prompted to perform the fault monitoring method according to any one of claims 1 to 18.

Images