Method, system and equipment for processing data of wind generating set and medium

Abstract

The invention provides a wind generating set data processing method, and relates to the technical field of wind power generation, the processing method comprises the following steps: obtaining a file generation task request, the file generation task request comprising an identifier of a file generation task and corresponding data demand range information; matching the obtained identifier of the file generation task with preset identification codes of a plurality of file generation tasks, and obtaining a variable table and a template file associated with the successfully matched file generation task; according to the variable table and the data demand range information, screening a plurality of basic data files in a preset database to obtain screened data; and generating a target data file based on the template file and the screening data. According to the method, data recording and file generation are decoupled, file generation operation is processed in a non-real-time, triggering and configuration mode, the memory occupancy rate and the operation load of the controller are reduced, and reliable operation of the wind generating set is guaranteed.

Description

Technical Field

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

[0002] During the operation of a wind turbine generator set, a large amount of operation data will be generated. These data need to be recorded in various types and formats according to different business requirements. Currently, the processing of data files in a wind power generation system is based on the cyclic task period in a controller. However, this method will cause excessive memory occupation and increased CPU load of the controller, and the file writing operation may not be completed within the task period. This may not only lead to the failure of control logic execution and communication interruption, but also cause problems such as controller downtime, thus seriously affecting the reliable operation of the wind turbine generator set. Therefore, there is room for improvement. Summary of the Invention

[0003] In view of the above-mentioned disadvantages of the prior art, the purpose of the present invention is to provide a method, system, device and medium for processing data of a wind turbine generator set, which is used to solve the technical problem that when processing data files based on a cyclic task period in the prior art, it causes excessive memory occupation and heavy CPU load of the controller, thus seriously affecting the reliable operation of the wind turbine generator set.

[0004] To achieve the above purpose and other related purposes, the present invention provides a method for processing data of a wind turbine generator set, including:

[0005] Obtain a file generation task request, where the file generation task request includes an identifier of the file generation task and corresponding data requirement range information;

[0006] Match the obtained identifier of the file generation task with a plurality of preset recognition codes of file generation tasks, and obtain a variable table and a template file associated with the successfully matched file generation task;

[0007] According to the variable table and the data requirement range information, perform screening processing on a plurality of basic data files in a preset database to obtain screened data;

[0008] Generate a target data file based on the template file and the screened data.

[0009] In an embodiment of the present invention, the basic data file is generated according to the following steps:

[0010] Regularly create new basic data files at preset time intervals;

[0011] During each cyclic task period, continuously collect the operation data of the wind turbine generator set, and write the collected operation data into the current latest basic data file according to a preset format.

[0012] In an embodiment of the present invention, after continuously collecting the operation data of the wind turbine generator set during each cyclic task period and writing the collected operation data into the current latest basic data file according to a preset format, the following steps are further included:

[0013] Statistically calculate the total storage occupancy value of all basic data files, and compare the total storage occupancy value with a preset storage threshold;

[0014] When the total storage occupancy value is greater than the storage threshold, delete at least one of the earliest generated basic data files.

[0015] In an embodiment of the present invention, the step of obtaining a file generation task request includes:

[0016] Real-time monitor the operation data of the wind turbine generator set, and when a certain sensor value in the operation data reaches a preset trigger threshold, generate a corresponding file generation task request.

[0017] In an embodiment of the present invention, the step of obtaining a file generation task request includes:

[0018] Receive an external input instruction and perform parsing and processing on it to generate a corresponding file generation task request.

[0019] In an embodiment of the present invention, the variable table is configured according to the following steps:

[0020] Configure the attribute information of the variable set associated with each file generation task, and the attribute information includes variable name, data type, unit, and sampling frequency;

[0021] Generate a corresponding variable table according to the attribute information corresponding to each file generation task.

[0022] In an embodiment of the present invention, the template file is configured according to the following steps:

[0023] Set the file format corresponding to each file generation task;

[0024] Generate a template file corresponding to each file generation task according to the file format and the variable name in the attribute information of the corresponding variable set.

[0025] The present invention also provides a processing system for wind turbine generator set data, including:

[0026] A request module, configured to obtain a file generation task request, where the file generation task request includes an identifier of a file generation task and corresponding data requirement range information;

[0027] A matching module, configured to match the obtained identifier of the file generation task with identification codes of a plurality of preset file generation tasks, and obtain a variable table and a template file associated with the successfully matched file generation task;

[0028] A screening module, configured to perform a screening process on a plurality of basic data files in a preset database according to the variable table and the data requirement range information to obtain screened data;

[0029] A generation module, configured to generate a target data file based on the template file and the screened data.

[0030] The present invention further provides an electronic device, where the electronic device includes:

[0031] One or more processors;

[0032] A storage device, configured to store one or more programs, and when the one or more programs are executed by the one or more processors, enable the electronic device to implement the method for processing wind turbine generator set data as described in any one of the above.

[0033] The present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor of a computer, enable the computer to execute the method for processing wind turbine generator set data as described in any one of the above.

[0034] As described above, the method, system, device, and medium for processing wind turbine generator set data of the present invention have the following beneficial effects: By decoupling data recording and file generation, and processing file generation operations in a non-real-time, trigger-based, and configuration-based manner, the present invention solves a series of problems such as high controller memory occupancy rate, high CPU operation load, and inability to complete writing files within a task cycle caused by the original file generation operation, and ensures the reliable operation of the wind turbine generator set. Description of the Drawings

[0035] Figure 1 It is a schematic flowchart of the method for processing wind turbine generator set data provided by an embodiment of the present invention;

[0036] Figure 2 It is a structural block diagram of the system for processing wind turbine generator set data provided by an embodiment of the present invention;

[0037] Figure 3 It is a schematic structural diagram of an electronic device provided by an embodiment of the present invention. Detailed Embodiments

[0038] The following describes the implementation manners of the present invention through specific examples. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, without conflict, the following embodiments and the features in the embodiments can be combined with each other.

[0039] It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present invention in a schematic manner. Therefore, only the components related to the present invention are shown in the diagrams, rather than being drawn according to the number, shape, and size of the components in actual implementation. The types, quantities, and proportions of the components in actual implementation can be arbitrarily changed, and the component layout type may also be more complex.

[0040] In the following description, a large number of details are explored to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0041] First of all, it should be noted that a large amount of operation data generated during the operation process of a wind turbine needs to be recorded in various types and formats according to different business requirements (such as the uses and scenarios of data files). Specifically, the log file adopts the TXT format; the waveform recording file adopts the CSV format; and the action record file adopts the PDF format.

[0042] Please refer to Figure 1 , the present invention provides a method for processing wind turbine data, which may include the following steps:

[0043] Step S100: Obtain a file generation task request, where the file generation task request includes an identifier of the file generation task and corresponding data requirement range information;

[0044] Step S200: Match the obtained identifier of the file generation task with a plurality of preset identification codes of file generation tasks, and obtain the variable table and template file associated with the successfully matched file generation task;

[0045] Step S300: Screen a plurality of basic data files in a preset database according to the variable table and the data requirement range information to obtain screened data;

[0046] Step S400: Generate a target data file based on the template file and the screened data.

[0047] In an embodiment of the present invention, when step S100 is executed, that is, a file generation task request is obtained. The file generation task request includes an identifier of the file generation task and corresponding data requirement range information. Specifically, first, when a user or a controller needs to generate a specific type of file, a file generation task request will be initiated. This request not only includes an identifier (ID) for identifying and differentiating different tasks, but also includes information such as the start time and end time of the required data, that is, the data requirement range information.

[0048] In an embodiment of the present invention, the file generation task request can be generated by the controller in response to an external instruction such as a number, or can be generated by the controller when a trigger condition is activated. In this embodiment, obtaining the file generation task request may specifically include real-time monitoring of the operation data of the wind turbine generator set, and generating a corresponding file generation task request when a certain sensor value in the operation data reaches a preset trigger threshold, or may include receiving an external input instruction and parsing and processing it to generate a corresponding file generation task request. The external input instruction may be a data file, an API request, a user operation, etc. Taking the waveform recording file as an example, the corresponding waveform recording file can be generated by manual trigger; or when a fault occurs, the corresponding waveform recording file can be automatically activated and generated.

[0049] In an embodiment of the present invention, when step S200 is executed, the identifier of the obtained file generation task is matched with the identification codes of a plurality of preset file generation tasks, and the variable table and template file associated with the successfully matched file generation task are obtained. Specifically, the identifier of the obtained file generation task is matched with the identification codes of a plurality of preset file generation tasks to determine the specific file generation task to be executed. In this embodiment, the plurality of file generation tasks can be classified, for example, into log file generation tasks, waveform recording file generation tasks, action record file generation tasks, etc., and each file generation task is preset with a unique identification code. Then, according to the determined file generation task, the corresponding variable table and template file can be retrieved from a pre-configured directory or database. The variable table and template file are preset files associated with the file generation task, and the controller will load these files to continue the file generation process. Among them, the variable table is a file containing variable names and variable values, which can be used to describe the data items used in the file generation process. The variable table includes the specific numerical values or parameters to be replaced in the template, which are used to fill the content when generating the file. The template file is a preset file format, which contains the framework structure of the generated file. The template file usually contains placeholders, which will be replaced by the data in the variable table during file generation, and finally generate the file required by the user. Once the required variable table and template file are obtained, the controller will check whether their contents are complete and valid. Further, some preprocessing can also be performed on them, such as parsing, formatting, or verification, etc., to ensure that the next file generation operation can be carried out smoothly.

[0050] In an embodiment of the present invention, the variable table is configured according to the following steps:

[0051] Step S510: Configure the attribute information of the variable set associated with each file generation task, where the attribute information includes variable name, data type, unit, and sampling frequency;

[0052] Step S520: Generate the corresponding variable table according to the attribute information corresponding to each file generation task.

[0053] In an embodiment of the present invention, when step S510 is executed, that is, the attribute information of the variable set associated with each file generation task is configured. The attribute information includes variable name, data type, unit, and sampling frequency. Specifically, each file generation task may contain multiple variables, and these variables will be part of the file content. Each variable needs to have a unique name so that it can be accurately referenced during the subsequent file generation process. For example, if the generated file type is a log file, the variables may include wind speed (wind_speed), power output (power_output), etc. The variable names need to follow a unified naming rule to ensure that there are no duplicate or conflicting variables during the file generation process.

[0054] In this embodiment, each variable needs to define its data type so that it can be correctly interpreted during processing and calculation. Common data types include integer (Integer), floating decimal (Float), string (String), boolean (Boolean), etc. If the variable involves a measured value, its unit needs to be further clarified. This is to accurately display or convert the unit during file generation. For example, the unit of wind speed is "m / s". The sampling frequency is the time attribute of the variable, that is, data is selected at a certain time interval in the basic data. The value set for the sampling frequency is used to determine how often a basic data is selected, so as to serve as the data source for generating the file.

[0055] In one embodiment of the present invention, when step S520 is executed, that is, according to the attribute information corresponding to each file generation task, a corresponding variable table is generated. Specifically, after determining the attribute information corresponding to each file generation task, the controller will use this attribute information to generate the corresponding variable table. In this embodiment, the controller will create an initial variable table, such as a table file or a database entry. Each file generation task will have a corresponding variable table. This table contains multiple fields, specifically including: variable name, data type, unit, and sampling frequency. According to the attribute information obtained in the previous step, the image of each variable is filled into the initial variable table. Finally, the filled initial variable table is saved as a file, such as in CSV, JSON, XML, etc. formats, for subsequent file generation operations. According to preset requirements, the file structure of the variable table will have certain specifications to ensure that the controller can correctly read and use this variable information in subsequent steps. The variable table usually contains column headers and data rows, where each row represents the detailed information of a variable. In addition, each generated variable table will be associated with a specific file generation task to correctly call and replace the variables in the template during the actual file generation process. For example, if the generation type is a log file and the variable table contains information such as wind speed and power generation, then the generated file will replace these variables into the predefined template file. In this embodiment, the configured variable table can be saved in a preset folder for the controller to call, such as / ahci00:1 / eFast1 / VarList / .

[0056] In one embodiment of the present invention, the template file is configured according to the following steps:

[0057] Step S610: Set the file format corresponding to each file generation task;

[0058] Step S620: Generate the template file corresponding to each file generation task according to the file format and the variable name in the attribute information of the corresponding variable set.

[0059] In an embodiment of the present invention, when step S610 is executed, that is, the file format corresponding to each file generation task is set. Specifically, the file format is the basis for template generation and determines the final output form of the file. For example, it may be formats such as CSV, TXT, XML, JSON, PDF, etc. For different file generation tasks, such as log files, waveform recording files, action record files, etc., each type will adopt a different file format. According to the actual requirements of each file generation task, a suitable file format is selected. For example, log files usually require less storage space and usually adopt the TXT format; waveform recording files are generally in the CSV format for easy data analysis; while action record files have requirements for traceability and anti-tampering, so they usually adopt the PDF format. According to the requirements of different file generation tasks, a suitable file format is selected to ensure that the generated files meet the expected standards and requirements.

[0060] In an embodiment of the present invention, when step S620 is executed, that is, according to the variable names in the file format and the attribute information of the corresponding variable set, a template file corresponding to each file generation task is generated. Specifically, first, according to the file format selected for each file generation task (such as CSV, XML, etc.) and the attribute information of the variable set, the controller generates a template file. The template file is a structured file that contains specific placeholders, which will be replaced by variable values during actual file generation. The variable set corresponding to each file generation task contains the attribute information of multiple variables, including variable names, data types, units, sampling frequencies, etc. Then, when generating the template, these variables are inserted into the template as placeholders. For files of different formats, the specific structure of the template will be different. For example, the template in CSV format will contain fields separated by commas, while the template in XML format will have custom tags to wrap the variables. According to the above steps, a template file corresponding to each file generation task is generated. The template file is saved to a preset storage location. The user can set the storage path of the template file. For example, the path can be a certain folder in the controller's storage medium, such as " / ahci00:1 / eFast1 / Templates / ". This path points to the specific location where the template file is stored.

[0061] In this embodiment, the template file also indicates the path where the basic data file to be read is located (for example, / ahci00:1 / eFast1 / RawData / ) and the path where the generated target file is planned to be stored (for example, / ahci00:1 / eFast1 / BufferData / ) and other information.

[0062] In an embodiment of the present invention, when step S300 is executed, that is, according to the variable table and the data requirement range information, multiple basic data files in the preset database are screened to obtain the screened data. Specifically, according to the variable table obtained in the previous step and the data requirement range information from the original request, the controller screens multiple basic data files stored in the preset database. The goal of this step is to extract a data subset that meets the requirements of the current task from a large amount of data, that is, the screened data. This can ensure that only the most relevant data is used in the subsequent file generation process. Among them, the data requirement range information defines the start time and end time of the required data. Based on the variable names, data types, and other attributes provided in the variable table, the controller screens the relevant data from the basic data files within the corresponding time range. For example, if the data requirement range information requires extracting data for the most recent 24 hours, and the variable table requires extracting data on wind speed and power generation, the controller will screen the data columns of these two variables from the basic data files within the corresponding time range. Then, according to the sampling frequency specified in the variable table, multiple operating data are sequentially selected at intervals of the set sampling frequency to obtain the required screened data.

[0063] In an embodiment of the present invention, the basic data file is generated according to the following steps:

[0064] Step S710: Regularly create new basic data files at preset time intervals;

[0065] Step S720: During each cyclic task period, continuously collect the operating data of the wind turbine generator set and write the collected operating data into the current latest basic data file in a preset format.

[0066] In an embodiment of the present invention, when steps S710 to S720 are executed, specifically, the controller of the wind turbine generator set continuously collects the operating data of the wind turbine generator set during each of its cyclic task periods and writes the collected operating data into the current basic data file in a preset format. Among them, the cyclic task period means that the controller executes tasks at a fixed time interval. During each cyclic task period, the controller obtains the operating data of the wind turbine generator set from various sensors and controller modules, and these operating data include but are not limited to parameters such as wind speed, blade speed, power generation, voltage, and current.

[0067] In one embodiment of the present invention, each piece of operation data is recorded in a preset format. For example, it is saved in a basic data file in the form of timestamp + variable name + variable value. The timestamp can be used to identify the data collection moment for subsequent further processing. The variable name represents the name of the data source or sensor. For example, "wind_speed" (wind speed), "power_output" (power generation), etc. They are used to identify what the collected data specifically represents. The variable value is the measured value of the data source at this time point. For example, the wind speed may be 12.5 m / s and the power generation may be 120 kW. The recording format of the basic data file belongs to raw data, that is, an unprocessed data file, which maintains the original state and basic information of the operation data and can be used as the basis for subsequent processing and analysis. The basic data file will be stored in the storage medium of the controller, usually in a specific folder in the local storage of the controller. For example, the storage path of the basic data file can be set to / ahci00:1 / eFast1 / RawData / .

[0068] In one embodiment of the present invention, the number of basic data files stored locally in the controller can be multiple. As a continuous recording carrier of operation data, instead of generating a new file for each loop task cycle, the data is continuously accumulated. As time goes by, new basic data files will be regularly generated according to preset time nodes and continuously record the operation data of the wind turbine generator set. In this embodiment, the basic data file can be created regularly at preset time intervals. For example, new basic data files can be created at time intervals such as "every day", "every hour", or "N loop cycles". The controller collects operation data in each loop task cycle and appends the operation data to the current basic data file in a preset format.

[0069] In one embodiment of the present invention, the controller will perform storage management on all basic data files, which specifically includes the following steps:

[0070] Step S730: Calculate the total storage occupancy value of all basic data files and compare the total storage occupancy value with a preset maximum storage occupancy value;

[0071] Step S740: When the total storage occupancy value is greater than the maximum storage occupancy value, delete multiple earliest generated basic data files.

[0072] In an embodiment of the present invention, when steps S730 to S740 are executed, specifically, first, management policy parameters of the basic data file are determined, such as: the maximum storage occupancy value allowed, the size limit of each file, or the storage time, etc. Then, within a set time interval (for example, every few seconds or minutes), a scanning task is started to check all the basic data files currently existing in the specified directory, so as to collect relevant information of each basic data file, such as file name, creation time, modification time, file size, etc. The controller uses an accumulation algorithm to calculate the total space occupancy value of all the basic data files in the current folder, and compares it with the preset maximum storage occupancy value to determine whether it exceeds the set upper limit. If the total storage occupancy value does not reach or is equal to the maximum storage occupancy value, there is no need to delete files, and the controller continues to record data normally. If the total storage occupancy value exceeds the preset maximum storage occupancy value, it indicates that the storage space may be insufficient, and at this time, cleaning is required.

[0073] In this embodiment, the basic data files are managed using the First-In-First-Out (FIFO) method. Specifically, the controller first sorts all the files in the order of generation according to the creation time of the basic data file or the time stamp in the file name. Then, according to the FIFO principle, the earliest generated N basic data files are identified as the targets to be deleted. The core concept of FIFO is that the data stored first should be removed first to maintain the efficient operation of the controller and the reasonable utilization of resources. Finally, the controller performs a deletion operation on the selected earliest generated basic data files to ensure that the files are completely removed from the storage medium.

[0074] Furthermore, if the size differences between the basic data files are small, the controller can also count the total number of all the basic data files and compare the total number of files with the preset maximum number of files, so as to achieve more flexible management of the basic data files.

[0075] Through the above steps, the controller can effectively manage the basic data files using the FIFO mechanism, ensuring that data recording is not affected by insufficient storage space during the continuous accumulation of data, and at the same time, it can also ensure that the latest data is saved for subsequent analysis.

[0076] In an embodiment of the present invention, when step S400 is executed, that is, based on the template file and the filtered data, a target data file is generated. Specifically, according to the previously obtained template file, the filtered data is arranged in the format in the template. For example, if the template requires generating a CSV format, the controller will put the filtered data into the CSV file according to the specified header and field order, and ensure that the data delimiter, line break, etc. meet the template requirements. The placeholder defined in the template file (such as variable name) will be replaced by the value of the filtered data. For example, the log file may require inserting the wind speed and power generation, and the controller will fill in the specific wind speed and power generation values obtained by filtering into the corresponding positions to generate the required target data file. The target data file will be saved to the specified path or location and named according to the preset format.

[0077] Furthermore, since the generated target data file may contain sensitive information or key data, during storage or transmission, it also needs to be encrypted and protected. An encryption algorithm can also be used to encrypt the target data file to prevent unauthorized access and tampering. In this embodiment, encryption algorithms such as base64 and AES can be used to protect the target file.

[0078] It can be understood that the present invention decouples data recording and file generation, and processes file generation operations in a non-real-time, trigger-based, and configuration-based manner, solving a series of problems caused by the original file generation operation, such as high memory occupancy rate of the controller, high CPU operation load, and inability to complete file writing within the task cycle, ensuring the reliable operation of the wind turbine generator.

[0079] Please refer to Figure 2 , the present invention also provides a processing system for wind turbine generator data, which corresponds one-to-one with the processing method in the above embodiment. The processing system may include a request module 11, a matching module 12, a filtering module 13, and a generating module 14. The detailed description of each functional module is as follows:

[0080] The request module 11 can be used to obtain a file generation task request, and the file generation task request includes an identifier of the file generation task and corresponding data requirement range information. Further, the request module 11 can be specifically used to initiate a file generation task request when the user or the controller needs to generate a specific type of file. This request not only includes an identifier (ID) for identifying and distinguishing different tasks, but also includes information such as the start time and end time of the required data, that is, the data requirement range information.

[0081] The matching module 12 can be used to match the identifier of the obtained file generation task with the identification codes of multiple preset file generation tasks, and obtain the variable table and template file associated with the successfully matched file generation task. Further, the matching module 12 can be specifically used to match the identifier of the obtained file generation task with the identification codes of multiple preset file generation tasks to determine the specific file generation task to be executed. In this embodiment, multiple file generation tasks can be classified into, for example, log file generation tasks, waveform recording file generation tasks, action record file generation tasks, etc., and each file generation task is preset with a unique identification code. Then, according to the determined file generation task, the corresponding variable table and template file can be retrieved from the preconfigured directory or database. The variable table and template file are preset files associated with the file generation task, and the controller will load these files to continue the file generation process. Among them, the variable table is a file containing variable names and variable values, which can be used to describe the data items used in the file generation process. The variable table includes the specific values or parameters that need to be replaced in the template, and is used to fill the content when generating the file. The template file is a preset file format that contains the framework structure of the generated file. The template file usually contains placeholders, which will be replaced with the data in the variable table during file generation, and finally generate the file required by the user.

[0082] The screening module 13 can be used to screen and process multiple basic data files in the preset database according to the variable table and data requirement range information to obtain the screened data. Further, the screening module 13 can be specifically used to screen the multiple basic data files stored in the preset database according to the variable table obtained in the previous step and the data requirement range information from the original request. The goal of this step is to extract a data subset that meets the current task requirements from a large amount of data, that is, the screened data. This can ensure that only the most relevant data is used in the subsequent file generation process. Among them, the data requirement range information defines the start time and end time of the required data. Based on the variable names, data types and other attributes provided in the variable table, the controller screens out the relevant data from the basic data files within the corresponding time range. For example, if the data requirement range information requires extracting data for the last 24 hours, and the variable table requires extracting data on wind speed and power generation, the controller will screen out the data columns of these two variables from the basic data files within the corresponding time range. Then, according to the sampling frequency specified in the variable table, multiple running data are sequentially selected at intervals of the set sampling frequency to obtain the required screened data.

[0083] The generation module 14 can be used to generate a target data file based on a template file and filtered data. Further, the generation module 14 can be specifically used to arrange the filtered data in the format in the template according to the previously obtained template file. For example, if the template requires generating a CSV format, the system will put the filtered data into the CSV file according to the specified table headers and field order, and ensure that the data delimiters, line breaks, etc. meet the template requirements. The placeholder defined in the template file (such as variable name) will be replaced by the value of the filtered data. For example, the log file may require inserting the wind speed and power generation, and the system will fill in the specific wind speed and power generation values obtained by filtering into the corresponding positions to generate the required target data file. The target data file will be saved to the specified path or location and named according to the preset format.

[0084] For the specific limitations of the data processing system of the wind turbine, reference can be made to the limitations of the processing method in the above text, which will not be elaborated here. Each module in the above processing system can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in the processor in the computer device in hardware form or independent of it, or stored in the memory in the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0085] An embodiment of the present invention also provides an electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, enabling the electronic device to implement the processing method of the wind turbine data provided in the above embodiments.

[0086] Please refer to Figure 3 , the electronic device 2 may include a memory 21, a processor 22 and a bus, and may also include a computer program stored in the memory 21 and operable on the processor 22, such as a processing program for wind turbine data.

[0087] Among them, the memory 21 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 21 can be an internal storage unit of the electronic device 2, such as the mobile hard disk of the electronic device 2. In some other embodiments, the memory 21 can also be an external storage device of the electronic device 2, such as a plug-in mobile hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the electronic device 2. Further, the memory 21 can also include both the internal storage unit and the external storage device of the electronic device 2. The memory 21 can be used not only to store application software installed on the electronic device 2 and various types of data, such as the code for processing wind turbine generator data, etc., but also to temporarily store data that has been output or will be output.

[0088] In some embodiments, the processor 22 can be composed of integrated circuits. For example, it can be composed of a single packaged integrated circuit, or can be composed of multiple integrated circuits with the same or different functions packaged together, including a combination of one or more Central Processing Units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips, etc. The processor 22 is the control core (Control Unit) of the electronic device 2, connecting various components of the entire electronic device 2 through various interfaces and lines, and by running or executing programs or modules stored in the memory 21 (such as the training program of the fatigue prediction model, etc.), and calling the data stored in the memory 21, to execute various functions of the electronic device 2 and process data.

[0089] The processor 22 executes the operating system of the electronic device 2 and various installed application programs. The processor 22 executes the application program to implement the steps in the above-mentioned method for processing wind turbine generator data.

[0090] Exemplarily, the computer program can be divided into one or more modules, and the one or more modules are stored in the memory 21 and executed by the processor 22 to complete this application. The one or more modules can be a series of computer program instruction segments capable of completing specific functions, and this instruction segment is used to describe the execution process of the computer program in the electronic device 2. For example, the computer program can be divided into a request module 11, a matching module 12, a screening module 13, and a generating module 14.

[0091] The integrated unit implemented in the form of software functional modules described above can be stored in a computer-readable storage medium, which can be non-volatile or volatile. The above software functional modules are stored in a storage medium and include several instructions for causing a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to execute part of the functions of the method for processing wind turbine generator set data according to various embodiments of the present application.

[0092] In summary, a method, a system, a device, and a medium for processing wind turbine generator set data disclosed by the present invention relate to the technical field of wind power generation and can optimize the generation efficiency of multiple types and formats of files in a wind power generation system. By decoupling data recording and file generation, the present invention processes file generation operations in a non-real-time, trigger-based, and configuration-based manner, fully considering the performance of the controller and the flexibility of configuring multiple types and formats of files, and solves a series of problems caused by the original file generation operations, such as high memory occupancy rate of the controller, high CPU operation load, and inability to complete file writing within the task cycle, ensuring the reliable operation of the wind turbine generator set. Therefore, the present invention effectively overcomes various disadvantages in the prior art and has high industrial utilization value.

[0093] The above embodiments are only illustrative of the principles and effects of the present invention and are not used to limit the present invention. Any person familiar with this technology can modify or change the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by those with ordinary knowledge in the technical field without departing from the spirit and technical ideas disclosed by the present invention should still be covered by the claims of the present invention.

Claims

1. A method for processing wind turbine generator set data, characterized in that: include: Obtaining a file generation task request, wherein the file generation task request includes an identifier of the file generation task and corresponding data requirement range information; Matching the obtained identifier of the file generation task with the identification codes of the preset multiple file generation tasks, and obtaining the variable table and template file associated with the successfully matched file generation task; According to the variable table and the data requirement range information, a plurality of basic data files in a preset database are screened to obtain screened data; A target data file is generated based on the template file and the screening data.

2. The method for processing wind turbine generator set data according to claim 1, characterized in that: The basic data file is generated according to the following steps: Create new basic data files regularly at preset time intervals; In each cyclic task period, the operation data of the wind turbine generator set is continuously collected, and the collected operation data is written into the current latest basic data file according to a preset format.

3. The method for processing wind turbine generator set data according to claim 2, characterized in that: The method further includes: continuously collecting the operation data of the wind turbine generator set in each cyclic task period, and writing the collected operation data into the current latest basic data file according to a preset format; Counting the total storage occupancy value of all basic data files, and comparing the total storage occupancy value with a preset storage threshold; When the total storage occupancy value is greater than the storage threshold, at least one basic data file generated earliest is deleted.

4. The method for processing wind turbine generator set data according to claim 1, characterized in that: The step of obtaining a file generation task request comprises: The operation data of the wind turbine generator set is monitored in real time, and when a certain sensor value in the operation data reaches a preset trigger threshold, a corresponding file generation task request is generated.

5. The method for processing wind turbine generator set data according to claim 1, characterized in that: The step of obtaining a file generation task request comprises: Receive external input instructions and parse them to generate corresponding file generation task requests.

6. The method for processing wind turbine generator set data according to claim 1, characterized in that: The variable table is configured according to the following steps: Configuring attribute information of a variable set associated with each file generation task, wherein the attribute information includes variable name, data type, unit, and sampling frequency; Generate a corresponding variable table based on the attribute information corresponding to each of the file generation tasks.

7. The method for processing wind turbine generator set data according to claim 6, characterized in that: The template file is configured according to the following steps: Set the file format corresponding to each file generation task; A template file corresponding to each file generation task is generated according to the file format and the variable name in the attribute information of the corresponding variable set.

8. A wind turbine generator data processing system, characterized in that: include: A request module, used to obtain a file generation task request, wherein the file generation task request includes an identifier of the file generation task and corresponding data requirement range information; A matching module, used to match the obtained identifier of the file generation task with the identification codes of the preset multiple file generation tasks, and obtain the variable table and template file associated with the successfully matched file generation task; A screening module, used for screening a plurality of basic data files in a preset database according to the variable table and the data requirement range information to obtain screening data; A generating module is used to generate a target data file based on the template file and the screening data.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, enables the electronic device to implement the method for processing wind turbine generator set data as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is enabled to execute the method for processing wind turbine generator set data as claimed in any one of claims 1 to 7.

Images