Wind turbine event recording method, device, system and storage medium

Abstract

The present application provides a method, apparatus, system, and storage medium for recording events of a wind turbine. The method for recording events of a wind turbine includes obtaining variable information of input variables of the wind turbine; determining whether the input variables can be registered as variables to be monitored according to the variable information; in the case where it is determined according to the variable information that the input variables can be registered as variables to be monitored, monitoring whether the variables to be monitored are modified during the operation of the wind turbine; and in the case where it is monitored that the variables to be monitored are modified, recording the event that the variables to be monitored are modified to monitor the state of the wind turbine. In this way, the monitored variables are not fixed and the flexibility is relatively high.

Description

Technical Field

[0001] The present invention relates to the technical field of wind power generation, and particularly to a method, device, system and storage medium for recording events of a wind turbine. Background Art

[0002] Wind power generation technology is the main technical means for obtaining new clean energy. The wind turbine converts wind energy into mechanical work, uses the mechanical work to drive the rotor to rotate, and finally outputs alternating current electrical energy. During the long-term operation of the wind turbine, the equipment components themselves will wear, and in severe cases, irreparable losses will be caused. Therefore, it is particularly important to monitor the state of the wind turbine. The wind turbine includes the control system of the wind turbine.

[0003] In the related art, first, when the core developers at the back end of the control system define the variables to be monitored through program code. Then, most wind turbines monitor whether the defined variables are modified during operation. Generally, when the state of the wind turbine changes and the defined variables are modified, at this time, the events of the modified variables of the wind turbine are recorded to monitor the operating state of the wind turbine. In this way, the monitored variables are fixed and the flexibility is low. Summary of the Invention

[0004] The present application provides a method, device, system and storage medium for recording events of a wind turbine, and the monitored variables of the method are not fixed, so the flexibility is relatively high.

[0005] The present application provides a method for recording events of a wind turbine, which is applied to a fan control system. The method for recording events of the wind turbine includes:

[0006] Obtain the variable information of the input variables of the wind turbine;

[0007] Determine whether the input variable can be registered as a variable to be monitored according to the variable information;

[0008] When it is determined according to the variable information that the input variable can be registered as a variable to be monitored, during the operation of the wind turbine, monitor whether the variable to be monitored is modified;

[0009] When it is monitored that the variable to be monitored is modified, record the event that the variable to be monitored is modified to monitor the state of the wind turbine.

[0010] Further, the obtaining of the variable information of the input variables of the wind turbine includes:

[0011] Obtain the identifier of the input variable of the wind turbine;

[0012] Obtain the variable information of the input variable according to the identifier of the input variable.

[0013] Further, determining whether the input variable can be registered as a variable to be monitored according to the variable information includes:

[0014] Check whether the variable information is missing;

[0015] Determine whether the data volume of the variable information exceeds a predetermined data volume;

[0016] Determine the input variables with missing variable information and / or data volume exceeding the predetermined data volume as variables that cannot be registered;

[0017] Determine that the input variables with non-missing variable information and data volume not exceeding the predetermined data volume can be registered as variables to be monitored.

[0018] Further, checking whether the variable information is missing includes:

[0019] Check whether the variable information contains a variable type, a variable length, and a variable address bit;

[0020] If the variable information contains one or two of the variable type, the variable length, and the variable address bit, determine that the variable information is missing;

[0021] If the variable information contains all three of the variable type, the variable length, and the variable address bit, determine that the variable information is not missing.

[0022] Further, monitoring whether the variable to be monitored is modified includes:

[0023] Determine whether the variable to be monitored is modified according to the data modification determination condition.

[0024] Further, determining whether the variable to be monitored is modified according to the data modification determination condition includes:

[0025] According to the refresh period, compare whether the content of the variable to be monitored before refreshing changes with the content of the variable to be monitored after refreshing;

[0026] If there is no change, determine that the variable to be monitored has not been modified;

[0027] If there is a change, determine that the variable to be monitored has been modified.

[0028] Further, recording the event that the variable to be monitored is modified includes: recording the event that the variable to be monitored is modified in the cache.

[0029] Further, recording the event that the variable to be monitored is modified in the cache includes:

[0030] Recording the event that the variable to be monitored is modified in the same predetermined file in the cache.

[0031] Further, after recording the event that the variable to be monitored is modified in the same predetermined file in the cache when it is monitored that the variable to be monitored is modified, the method further includes: when the file export condition is reached, exporting the same predetermined file to a predetermined storage location in a unified file format.

[0032] Further, the method further includes: when it is monitored that a user logs in to the wind turbine control system through the human-machine interface, recording the event of the user's operation behavior, where the event of the user's operation behavior includes one or more of user management information, user operation information, and parameter information of the user modifying the wind turbine.

[0033] Further, the user management information includes one or more of user login time information, user logout time information, adding user information, deleting user information, locking user information, and modifying user level information;

[0034] The user operation includes the shielding operation of the status code.

[0035] Further, after recording the event of the user's operation behavior when it is monitored that a user logs in to the wind turbine control system through the human-machine interface, the method further includes: recording the event of the user's operation behavior in the cache.

[0036] Further, the method further includes: when the file export condition is reached, exporting the event of the user's operation behavior to a predetermined storage location in a unified file format.

[0037] The present application provides a wind turbine event recording device, which is applied to a wind turbine control system. The wind turbine event recording device includes:

[0038] An acquisition data module, configured to acquire variable information of an input variable of a wind turbine;

[0039] A data verification module, configured to determine whether the input variable can be registered as a variable to be monitored;

[0040] A monitoring data module, configured to monitor whether the variable to be monitored is modified during the operation of the wind turbine when it is determined according to the variable information that the input variable can be registered as a variable to be monitored;

[0041] An event recording module, configured to record an event that the variable to be monitored is modified when it is monitored, so as to monitor the status of the wind turbine.

[0042] The present application provides a wind turbine event recording system, including one or more processors, configured to implement the method described in any one of the above.

[0043] The present application provides a computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, the method described in any one of the above is implemented.

[0044] In some embodiments, for the method of wind turbine event recording in the present application, variable information of an input variable of the wind turbine is obtained, and it is determined whether the input variable can be registered as a variable to be monitored. When it is determined according to the variable information that the input variable can be registered as a variable to be monitored, during the operation of the wind turbine, it is monitored whether the variable to be monitored is modified. When it is monitored that the variable to be monitored is modified, an event that the variable to be monitored is modified is recorded, so as to monitor the status of the wind turbine. In this way, the input variable in the present application can be opened for the operator to input, and then, it can be automatically determined whether the input variable can be registered as a variable to be monitored. During the operation of the wind turbine, the event that the variable to be monitored is modified is automatically recorded to monitor the status of the wind turbine. In this way, the input variable is not fixed and has high flexibility. Description of the Drawings

[0045] Figure 1 The figure shows a schematic flowchart of the wind turbine event recording method provided by an embodiment of the present application;

[0046] Figure 2 As shown in Figure 1 The robust graph model of the wind turbine event recording method shown;

[0047] Figure 3 As shown in Figure 1 The figure shows a schematic flowchart of step 120 in the wind turbine event recording method;

[0048] Figure 4 As shown in Figure 1 The figure shows the internal processing flowchart of the wind turbine event recording method applied to a wind turbine control system;

[0049] Figure 5 The figure shows a schematic structural diagram of the wind turbine event recording device provided by an embodiment of the present application;

[0050] Figure 6 The figure shows a module block diagram of the wind turbine event recording system provided by an embodiment of the present application. Detailed Description of the Embodiments

[0051] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0052] It should be noted that: In other embodiments, the steps of the corresponding methods are not necessarily executed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step for description in other embodiments.

[0053] To solve the technical problem that the variables recorded by a wind turbine are limited and the flexibility is poor, an embodiment of the present application provides a method for recording wind turbine events, which obtains the variable information of the input variables of the wind turbine and determines whether the input variables can be registered as variables to be monitored. When it is determined according to the variable information that the input variables can be registered as variables to be monitored, during the operation of the wind turbine, it is monitored whether the variables to be monitored are modified. When it is monitored that the variables to be monitored are modified, the event that the variables to be monitored are modified is recorded to monitor the state of the wind turbine. In this way, the input variables of the present application can be opened for the operator to input, and then, it can be automatically determined whether the input variables can be registered as variables to be monitored. During the operation of the wind turbine, the event that the variables to be monitored are modified is automatically recorded to monitor the state of the wind turbine. In this way, the input variables are not fixed and the flexibility is relatively high.

[0054] The method for recording wind turbine events can be applied to a wind turbine control system. Among them, the wind turbine control system refers to a wind turbine control system. The wind turbine control system includes a front end and a back end. The front end may include an HMI (Human Machine Interface), which is used for the operator to input information. The back end includes a server, which is used for the development of core developers.

[0055] The main control system includes a controller of the wind turbine, simply referred to as a wind turbine controller. The wind turbine controller can write the code of the "method for recording wind turbine events" in a PLC (Programmable Logic Controller) in advance to record the events that the variables to be monitored are modified and the events of user behavior to monitor the state of the wind turbine.

[0056] Figure 1 The figure shows a schematic flowchart of the wind turbine event recording method provided by an embodiment of the present application. Figure 2 As shown Figure 1 in the robust graph model of the wind turbine event recording method shown

[0057] As Figure 1 and Figure 2 shown, the wind turbine event recording method includes the following steps 110 to 140.

[0058] Step 110: Obtain the variable information of the input variables of the wind turbine.

[0059] The input variables may include variables input by front-end operators and variables input by back-end developers. These input variables do not require verification by back-end developers. Whether this input variable can be registered as a variable to be monitored is subsequently verified through the templatized process of step 120 below. This reduces the need for professional operations by back-end developers for each input variable and also reduces the difficulty when a new variable is input each time, facilitating subsequent automation.

[0060] The above step 110 may further include: Step 1, obtain the identifier of the input variable of the wind turbine. The identifier may be the variable name. Step 2, according to the identifier of the input variable, obtain the variable information of the input variable. The variable information includes one or more of the variable type, variable length, and address bits. In this way, it is beneficial to quickly obtain the variable information of the input variable using the identifier of the input variable.

[0061] In the specific implementation process, in combination with Figure 2 the process of the example (1) shown, 1), the PLC (programmable logic controller) is powered on. 2), obtain the name of the input variable of the wind turbine from the file system. 3), according to the name of the input variable, obtain the variable information of the input variable.

[0062] Step 120: Determine whether the input variable can be registered as a variable to be monitored according to the variable information.

[0063] Among them, if the input variable can be registered, register the input variable as a variable to be monitored. If the input variable cannot be registered, the input variable can be called an abnormal variable to facilitate subsequent reporting to the diagnosis and monitoring system.

[0064] Figure 3 As shown Figure 1 in the schematic flowchart of step 120 in the wind turbine event recording method shown

[0065] As Figure 3As shown, in some embodiments, the above 120 further includes checking whether the variable information is abnormal and / or whether the data volume exceeds a predetermined data volume. Further, in step 121, it is checked whether the variable information is missing. In step 122, it is determined whether the data volume of the variable information exceeds the predetermined data volume. In step 123, the input variables with missing variable information and / or data volume exceeding the predetermined data volume are determined as variables that cannot be registered. In step 124, the input variables with non-missing variable information and data volume not exceeding the predetermined data volume are determined to be registerable as variables to be monitored. The predetermined data volume can be determined according to user requirements. Such checking can register the input variables with non-missing variable information and data volume not exceeding the predetermined data volume as variables to be monitored. In this way, the subsequent monitoring and recording processes can ensure the normal progress of the process and avoid system crashes caused by excessive data volume of a single input variable.

[0066] Among them, the data volume not exceeding the predetermined data volume means that the data volume of a single input variable does not exceed the predetermined data volume of the input variable. The above step 121 further includes checking whether the variable information contains a variable type, a variable length, and variable address bits. If the variable information contains one or both of the variable type, the variable length, and the variable address bits, it is determined that the variable information is missing. If the variable information contains all three of the variable type, the variable length, and the variable address bits, it is determined that the variable information is not missing. In this way, the accuracy of the checking is improved.

[0067] Combined with Figure 2 Regarding the process of the example (2) shown, 1) Check the variable information to obtain a check result. 2) Send the check result to the diagnosis and monitoring system. The details are as follows. In one case, the above input variables may include at least one input variable, and multiple input variables can be registered as variables to be monitored. Then, the input variables that can be registered as variables to be monitored are used to continue executing step 130. And, the method further includes generating a first check result, where the first check result is used to indicate the result that all variables are successfully registered and continue to execute the recording, and sending the first check result to the diagnosis and monitoring system.

[0068] The above input variables may include multiple input variables. In some cases, where the multiple input variables include those that can be registered as variables to be monitored and those that cannot be registered as variables to be monitored, the input variables that can be registered as variables to be monitored are used to continue with step 130. Further, the method also includes generating a second test result, which is used to indicate that variable registration has failed and the result of continuing with the recording, and sending this second test result to the diagnostic and monitoring system. In other cases, where none of the multiple input variables can be registered as variables to be monitored, the process ends. Further, the method also includes generating a third test result, which is used to indicate that variable registration has failed and it is not possible to execute the recording, and sending this third test result to the diagnostic and monitoring system. The first test result, the second test result, and the third test result can be referred to as three diagnostic types. The second test result and the third test result can be determined as two failure types. The above first test result, second test result, and third test result can be collectively referred to as test results.

[0069] The diagnostic and monitoring system is used to receive the test results, and generate corresponding fault logs for the variable names of the variables that cannot be registered as variables to be monitored and the reasons for variable registration failure in the second test result and the third test result. The reasons for variable registration failure include, for example, missing variable information and / or input variables whose data volume exceeds a predetermined data volume.

[0070] Step 130, in the case where, based on the variable information, it is determined that the input variable can be registered as a variable to be monitored, during the operation of the wind turbine, monitor whether the variable to be monitored is modified.

[0071] Being modified means that when a change event occurs, the key variable values of the program have changed. The change in the key variable values may include the result of automatic execution of the program. The change event may include one or more of user operation behavior events and wind turbine control events. User operation behavior events include one or more of logging in and out, modifying parameters, and masking fault codes. Wind turbine control events include one or more of yawing, starting, stopping, generating electricity, grid connection, grid disconnection, and power limitation. Thus, when a wind turbine control event occurs during the operation of the wind turbine, it will cause the variable to be monitored to be modified.

[0072] Among them, the method of further monitoring the variable to be input may further include monitoring the input variables and variable information of the wind turbine line by line, where one line includes variable information. Specifically, when subsequently monitoring the variable to be monitored, the specific variable to be monitored is read through the variable address bit for monitoring. According to the variable length, determine whether the variable to be monitored has been read completely. Then, after reading this variable to be monitored, the variable length can be offset to the next variable to be monitored and reading can continue starting from the variable address bit of the next variable to be monitored for monitoring.

[0073] Combining the above content, determining whether the variable to be monitored is modified in step 130 further includes determining whether the variable to be monitored is modified according to the data modification determination condition. In this way, it is possible to automatically determine whether the variable to be monitored is modified, improving the automation of the determination process.

[0074] The above data modification determination condition includes a refresh period. The above determining whether the variable to be monitored is modified according to the data modification determination condition further includes: First, compare whether the content of the variable to be monitored before refreshing changes with the content of the variable to be monitored after refreshing according to the refresh period. Second, if there is no change, determine that the variable to be monitored has not been modified. Third, if there is a change, determine that the variable to be monitored has been modified. In this way, refreshing the variable to be monitored according to the refresh period improves the effect of automatically determining whether the variable to be monitored is modified. Among them, these refresh periods can be the refresh period of the CPU (Central Processing Unit). The range of this refresh period is from 10 milliseconds to 20 milliseconds. Of course, the refresh period range can also be 50 milliseconds, 100 milliseconds, which is not limited here. In some other embodiments, the data modification determination condition includes the generation of an event of user operation behavior or the occurrence of a wind turbine control event.

[0075] Combined with Figure 2 the process of the example (3) shown, determining whether the variable to be monitored is modified in step 130 can further include: First step, put the variable to be monitored into the monitoring character text. Second step, monitor whether the variable to be monitored changes. Third step, if the variable to be monitored does not change, determine that the variable to be monitored has not been modified, and return to the second step to continue execution. Fourth step, if the variable to be monitored changes, determine that the variable to be monitored has been modified, modify the monitoring flag bit of the variable to be monitored, and update the monitoring flag bit of the variable to be monitored to the monitoring character text. This monitoring flag bit is used to reflect when the variable to be monitored is modified. In this way, the monitoring flag bit can be recorded, facilitating the search for the modified variable to be monitored, and being conducive to recording the event of the variable to be monitored being modified subsequently.

[0076] Among them, the above modifying the monitoring flag bit of the variable to be monitored further includes updating the Audit monitoring character text, adding the event of the variable to be monitored being modified to the monitoring character text, and opening a cache in the memory for the Audit monitoring character text. This cache is used to record data such as the monitoring flag bit. Configure the monitoring string number, splice the read monitoring flag bit with the description of the event of the variable to be monitored being modified, and put it into the monitoring string array to achieve dynamic configuration.

[0077] Step 140, in the case of monitoring that the variable to be monitored is modified, record the event of the variable to be monitored being modified to monitor the state of the wind turbine.

[0078] Among them, the events of recording the modification of the variables to be monitored include the event type, event identifier Event ID, event name Event Name, and event description Event text. The method further includes recording the wind turbine state switching. The wind turbine state switching includes one or more of the states of the wind turbine cut-in wind speed, the wind turbine cut-out wind speed, yawing, and pitch control.

[0079] The above 140 further includes, when it is monitored that the variable to be monitored is modified, recording the event of the modification of the variable to be monitored in the cache. In this way, when the variable to be monitored is modified, the event of the modification of the variable to be monitored can be recorded in the cache in time, avoiding the loss of the event of the modification of the variable to be monitored.

[0080] In some embodiments, the above recording the event of the modification of the variable to be monitored in the cache may further include recording the event of the modification of the variable to be monitored in the same predetermined file in the cache. The predetermined file may be the above-mentioned monitored character text. In this way, it can be uniformly recorded in the same predetermined file, and the events of the modification of the variable to be monitored can be uniformly monitored, which is convenient for management. In other embodiments, the above recording the event of the modification of the variable to be monitored in the cache may further include recording the event of the modification of the variable to be monitored in the cache in a unified file format. In this way, the event of the modification of the variable to be monitored can be recorded in the cache according to the unified file format.

[0081] Combined with Figure 2 The process of the example (4) shown, the above recording the event of the modification of the variable to be monitored in the cache when it is monitored that the variable to be monitored is modified may further include a first step of determining whether the file export condition is met when it is monitored that the variable to be monitored is modified. The second step is to record the event of the modification of the variable to be monitored in the cache when the file export condition is not met. After the above step 140, that is, the third step, when the file export condition is met, the same predetermined file is exported to the predetermined storage location in a unified file format. In this way, the same predetermined file is exported in a unified file format, standardizing the data, facilitating the unified management of the data at the predetermined storage location, and reducing the cost of managing files.

[0082] Among them, the file export condition is used to reflect whether it is necessary to export the file recording the event first or record it in the cache when the variable to be monitored is modified, avoiding the situation of exporting immediately after writing the record into the cache and reducing unnecessary operations. The file export condition may include one or more of the file quantity reaching the preset quantity, receiving the instruction of the user to export, and reaching the scheduled export time point.

[0083] The unified file format may include one of the xml format, database file format, and tst format. The predetermined storage location may be the file system, and file management is realized through the file system. Combined withFigure 2 In the process of the example (5) shown, the above-mentioned monitored character text is exported to a predetermined storage location in xml format.

[0084] Recording the event that the variable to be monitored is modified in the cache in step 140 above may further include writing an event that the variable to be monitored is modified into the cache each time when it is determined that a variable to be monitored is modified, so as to ensure no data loss and improve the accuracy of recording.

[0085] In the embodiment of the present application, the input variable can be opened for the operator to input. Then, it can be automatically determined whether the input variable can be registered as a variable to be monitored. During the operation of the fan, the event that the variable to be monitored is modified is automatically recorded to monitor the state of the wind turbine. In this way, the input variable is not fixed and has high flexibility. Moreover, in the present application, monitoring the modification of the variable to be monitored and recording the event that the variable to be monitored is modified do not require the developer to modify the program of the fan control system, decoupling from the wind turbine control system, and the operator can be allowed to input variables, so that more input variables can be monitored and recorded, increasing the comprehensiveness of monitoring and recording input variables.

[0086] The recording of the modification of the variable to be monitored above in the present application and the recording of the user behavior below can belong to two parallel execution processes, which can be executed independently of each other without affecting each other. The recording of the modification of the variable to be monitored above in the present application can be executed before or after the recording of the user behavior below. This is not limited here. The detailed description of the recording of the specific user behavior is as follows.

[0087] Combined with Figure 2 In the process of the example (6) shown, the method further includes recording the event of the user operation behavior when it is monitored that the user logs in to the fan control system through the human-machine interface. The event of the user operation behavior includes user management information, user operation information, and the parameter information of the user modifying the wind turbine. Moreover, the user management information, user operation information, and the parameter information of the user modifying the wind turbine can reflect the user operation behavior after the user logs in to the fan control system. Recording the association between the user operation behavior and the fan control system in this way facilitates tracing back to the source.

[0088] Among them, the user management information includes one or more of user login time information, user logout time information, adding user information, deleting user information, locking user information, and modifying user level information. The user operation information may include the masking operation information of the status code. Exemplarily, the status code is a fault code. The user-modified parameters include the parameters of the wind turbine modified by the user. The parameter information of the wind turbine modified by the user includes the parameters of the components in the wind turbine modified by the user. Exemplarily, the parameters of the gearbox in the wind turbine. Exemplarily, the pressure parameter of the oil pump in the wind turbine, and the pressure parameter of the oil pump in the wind turbine increases from 2.96 pounds to 3 pounds, for example.

[0089] For the above-mentioned recording of user management information, user operations, and parameter information of the wind turbine modified by the user, it can be achieved through the following steps: When logging in to the wind turbine control system through the human-machine interface and passing the login authentication, record the time when the user logs in; monitor whether the parameters of the wind turbine are modified; in the case of monitoring that the parameters are modified, record the event that the parameters are modified; when logging out of the wind turbine control system through the human-machine interface, record the time when the user logs out. By recording the user login time and logout time, and the event that the parameters are modified in this way, the comprehensiveness of the recorded events is improved.

[0090] After recording the event of the user operation behavior in the above case of monitoring that the user logs in to the wind turbine control system through the human-machine interface, record the event of the user operation behavior in the cache. In this way, the event of the user operation behavior can be recorded in the cache in a timely manner, avoiding the loss of the event of the user operation behavior.

[0091] In some embodiments, the method further includes receiving a login request for logging in to the wind turbine control system, where the login request includes a username and a password. In response to the login request, verify the login request. In the case of successful verification, determine that the user logs in to the wind turbine control system. In the case of failed verification, reject the user from logging in to the wind turbine control system. In this way, the security of the user logging in to the wind turbine control system can be improved, and at the same time, it is convenient to record the event of the user operation behavior starting from when the user logs in to the wind turbine control system. Moreover, the user operation behavior between the user logging in and logging out of the wind turbine control system can be obtained, and the event of the user operation behavior can be obtained more comprehensively.

[0092] In some embodiments, the event of recording the user operation behavior in the cache includes recording the event of the user operation behavior in the same specified file in the cache. In this way, it is convenient to separately record the events of the user operation behavior through the same specified file, and when it is necessary to trace the source, the same specified file can be conveniently used separately. In some other embodiments, the same specified file and the same predetermined file can be merged into the same file. In this way, the same file is used to record both the events of the user operation behavior and the events of the monitored variables being modified. This improves the comprehensiveness of recording the change information, so as to comprehensively grasp the development trend of the wind turbine and more effectively monitor the operating state of the wind turbine. When a fault occurs, the fault problem can be located in time to ensure the stable and reliable operation state of the wind turbine. Among them, the same specified file and the same predetermined file are saved according to the date respectively, which is convenient for maintenance personnel or the host computer system to read and parse.

[0093] In some embodiments, the method further includes exporting the event of the user operation behavior to a predetermined storage location in a unified file format when the file export condition is met.

[0094] In some embodiments, the method further includes clearing the cache when the cache clearing condition is met. The cache clearing condition may include one or more of clearing at regular intervals, clearing when the data volume reaches a predetermined threshold, and receiving a user clearing instruction. In this way, the cache can be released in time to reduce resource occupancy.

[0095] Figure 4 As shown Figure 1 The internal processing flow chart of the wind turbine event recording method shown in the figure is applied to the fan control system.

[0096] Such as Figure 4 As shown, in the initialization stage, the event recording system in the fan control system calls the configuration information of the input variables from the file system. The configuration information is such as variable names and event descriptions. Obtain the variable information in the configuration information of the input variables. Convert the variable information into a wide string variable. According to the wide string variable, check the variable information. According to the variable information, determine whether the input variable can be registered as a monitored variable. If it is determined that the input variable cannot be registered as a monitored variable, that is, there are variables that cannot be registered, then determine the fault type and the variable name that cannot be registered as a monitored variable, and send the fault type and the variable name that cannot be registered as a monitored variable to the diagnosis and monitoring system, generate corresponding fault logs, and can be displayed correspondingly on the HMI. If the variable information is checked to be normal, the process continues and the input variable verification is completed.

[0097] During the operation phase, MpAudit runs the variables to be monitored. It monitors whether the variables to be monitored are modified. If no variable to be monitored is modified, it returns to the step of MpAudit running the variables to be monitored. If it is monitored that a variable to be monitored is modified, it records the event of the variable to be monitored being modified in the cache. It determines whether the file export condition is met. If the file export condition is not met, it returns to the step of recording the event of the variable to be monitored being modified in the cache. If the file export condition is met, it exports the same predetermined file, and the exported same predetermined file is an XML file. It sends the XML file to the file system, and the file system completes file management. After sending the XML file to the file system, it determines whether the condition for clearing the cache at zero o'clock is met. If the condition for clearing the cache at zero o'clock is not met, it returns to the step of recording the event of the variable to be monitored being modified in the cache. If the condition for clearing the cache at zero o'clock is met, it clears the cache.

[0098] Users can log in to the fan control system through the HMI, and can modify the parameters of the wind turbine and the status code of the wind turbine. For example, users can shield fault codes and other user operation information. Users can log in to the user system and manage user information to obtain user management information. The user management information, user operation information, and the information of the parameters modified by the user for the wind turbine are used to execute a monitoring and recording process similar to that of the variables to be monitored.

[0099] Figure 5 The figure shows a schematic structural diagram of a wind turbine event recording device provided by an embodiment of the present application.

[0100] As Figure 5 shown, a wind turbine event recording device provided by an embodiment of the present application is applied to a fan control system and includes:

[0101] An acquisition data module 21, configured to acquire variable information of input variables of a wind turbine;

[0102] A data verification module 22, configured to determine whether an input variable can be registered as a variable to be monitored;

[0103] A monitoring data module 23, configured to monitor whether a variable to be monitored is modified during the operation of the wind turbine when it is determined according to the variable information that the input variable can be registered as a variable to be monitored;

[0104] An event recording module 24, configured to record the event of the variable to be monitored being modified when it is monitored that the variable to be monitored is modified, so as to monitor the status of the wind turbine.

[0105] The implementation processes of the functions and roles of each module in the above device are specifically detailed in the implementation processes of the corresponding steps in the above method, and will not be repeated here.

[0106] The wind turbine event recording system provided by the embodiment of the present application includes the above-mentioned wind turbine event recording device.

[0107] Figure 6 The block diagram of the wind turbine event recording system 30 provided by the embodiment of the present application is shown. The wind turbine event recording system 30 includes one or more processors 31, which are used to implement the wind turbine event recording method as described above.

[0108] In some embodiments, the wind turbine event recording system 30 may include a computer-readable storage medium 39. The computer-readable storage medium 39 may store a program that can be called by the processor 31, and may include a non-volatile storage medium. In some embodiments, the wind turbine event recording system 30 may include a memory 38 and an interface 37. In some embodiments, the wind turbine event recording system 30 may also include other hardware according to actual applications.

[0109] The computer-readable storage medium 39 of the embodiment of the present application stores a program thereon. When the program is executed by the processor 31, it is used to implement the wind turbine event recording method described above.

[0110] The present application may be in the form of a computer program product implemented on one or more computer-readable storage media 39 (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing program code. The computer-readable storage medium 39 includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information may be computer-readable instructions, data structures, program modules, or other data. Examples of the computer-readable storage medium 39 include but are not limited to: phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0111] The above are only the preferred embodiments of this specification and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included within the scope of protection of this specification.

[0112] It should also be noted that the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, commodity or device comprising said element.

Claims

1. A method for recording events of a wind turbine, characterized in that, Applied to a wind turbine control system, the method for recording wind turbine events includes: Obtaining variable information of input variables of a wind turbine; the variable information includes one or more of variable type, variable length, and address bits; Determining whether the input variable can be registered as a variable to be monitored only based on the variable information; in the case where it is determined that the input variable can be registered as a variable to be monitored only based on the variable information, during the operation of the wind turbine, monitoring whether the variable to be monitored is modified; In the case where it is monitored that the variable to be monitored is modified, recording the event that the variable to be monitored is modified to monitor the state of the wind turbine.

2. The method for recording wind turbine events according to claim 1, wherein The obtaining of the variable information of the input variables of the wind turbine includes: Obtaining the identifier of the input variable of the wind turbine; Obtaining the variable information of the input variable according to the identifier of the input variable.

3. The method for recording wind turbine events according to claim 2, wherein, The determining whether the input variable can be registered as a variable to be monitored only based on the variable information includes: Checking whether the variable information is missing; Determining whether the data volume of the variable information exceeds a predetermined data volume; Determining the input variables with missing variable information and / or data volume exceeding the predetermined data volume as variables that cannot be registered; Determining that the input variables with non-missing variable information and data volume not exceeding the predetermined data volume can be registered as variables to be monitored.

4. The method for recording wind turbine events according to claim 3, wherein The checking whether the variable information is missing includes: Checking whether the variable information contains variable type, variable length, and variable address bits; If the variable information contains one or two of the variable type, the variable length, and the variable address bit, determining that the variable information is missing; If the variable information contains all three of the variable type, the variable length, and the variable address bit, determining that the variable information is not missing.

5. The method for recording wind turbine events according to claim 1, characterized in that, The monitoring whether the variable to be monitored is modified includes: Determining whether the variable to be monitored is modified according to the data modification determination condition.

6. The method for recording wind turbine events according to claim 5, characterized in that, The determining whether the variable to be monitored is modified according to the data modification determination condition includes: Comparing whether the content of the variable to be monitored before refreshing and the content of the variable to be monitored after refreshing changes according to the refresh period; If there is no change, determining that the variable to be monitored is not modified; If there is a change, determining that the variable to be monitored is modified.

7. The method for recording wind turbine events according to claim 1, characterized in that, The recording of the event that the variable to be monitored is modified includes: Recording the event that the variable to be monitored is modified in a cache.

8. The method for recording wind turbine events according to claim 7, wherein The recording of the event that the variable to be monitored is modified in the cache includes: Recording the event that the variable to be monitored is modified in the same predetermined file in the cache.

9. The method for recording wind turbine events according to claim 8, wherein, After the event that the variable to be monitored is modified is recorded in the same predetermined file in the cache in the case where it is monitored that the variable to be monitored is modified, the method further includes: When the file export condition is reached, exporting the same predetermined file to a predetermined storage location in a unified file format.

10. The method for recording wind turbine events according to any one of claims 1 to 9, characterized in that, The method further includes: When it is monitored that a user logs in to the wind turbine control system through the human-machine interface, an event of the user's operation behavior is recorded, and the event of the user's operation behavior includes one or more of user management information, user operation information, and parameter information of the user modifying the wind turbine.

11. The method for recording wind turbine events according to claim 10, wherein The user management information includes one or more of user login time information, user logout time information, adding user information, deleting user information, locking user information, and modifying user level information; The user operation includes masking operation of the status code.

12. The method for recording wind turbine events according to claim 10, wherein, After recording the event of the user's operation behavior when it is monitored that a user logs in to the wind turbine control system through the human-machine interface, the method further includes: Recording the event of the user's operation behavior in the cache.

13. The method for recording wind turbine events according to claim 10, characterized in that, The method further includes: When the file export condition is met, exporting the event of the user's operation behavior to a predetermined storage location in a unified file format.

14. A wind turbine event recording device, characterized in that, Applied to the wind turbine control system, the wind turbine event recording device includes: An acquisition data module, configured to acquire variable information of an input variable of the wind turbine; the variable information includes one or more of variable type, variable length, and address bit; A data verification module, configured to determine whether the input variable can be registered as a variable to be monitored; A monitored data module, configured to monitor whether the variable to be monitored is modified during the operation of the wind turbine when it is determined that the input variable can be registered as a variable to be monitored only according to the variable information; An event recording module, configured to record the event that the variable to be monitored is modified when it is monitored that the variable to be monitored is modified, so as to monitor the status of the wind turbine.

15. A wind turbine event recording system, characterized in that, Including one or more processors for implementing the method according to any one of claims 1-13.

16. A computer-readable storage medium, characterized in that, Stored thereon is a program which, when executed by the processor, implements the method according to any one of claims 1-13.

Images