Wind turbine generator set gas-electric control full-dynamic joint simulation method and system
By using OpenFAST and Simulink to run independently in wind turbine simulation and utilizing scheduler and process blocking technology to achieve data exchange, the problems of difficult synchronous exchange of simulation data and weak program scalability in existing technologies are solved, realizing efficient and low-cost simulation of the entire dynamic process of wind turbines.
Patent Information
- Application Number
- CN202411571278.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-06
- Publication Date
- 2026-05-08
AI Technical Summary
Existing wind turbine simulation software platforms struggle to achieve efficient joint simulation of aerodynamic, mechanical, control, and electrical components. In particular, when studying the impact of grid dynamics on the mechanical vibration of wind turbines, existing technologies suffer from problems such as difficulty in synchronously exchanging simulation data, weak program scalability, and high investment costs.
Two simulation software programs, OpenFAST and Simulink, are used to run independently. Data exchange and process blocking techniques are implemented through a scheduler to ensure that data interaction occurs at the same time. DLL and TCP/IP modules are used for communication to achieve full dynamic joint simulation of pneumatic, mechanical, control and electrical components.
It achieves efficient, low-cost, and flexible simulation of the entire dynamic process of wind turbine units, ensuring data synchronization and simulation efficiency, and improving the program's scalability and independent operation capability.
Smart Images
Figure CN121995785A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of new energy power generation technology, specifically to a method and system for full dynamic joint simulation of wind turbine and electronic control. Background Technology
[0002] To fully simulate the dynamic characteristics of wind turbines, building a relevant computer simulation platform is crucial. Wind turbines comprise at least aerodynamic, mechanical, control, and electrical components. Currently, mainstream wind turbine simulation software primarily focuses on the aerodynamic and mechanical parts (such as the industry-recognized Bladed and OpenFAST software), while the modeling of the control and electrical parts is generally relatively simple. However, with the further development of wind power generation technology, the control and electrical components of wind turbines are becoming increasingly important. For example, the control system is typically used for wake optimization and damping mechanical oscillations, while the electrical system interacts with the power grid through power electronic converters, performing various functions such as inertia extraction, load shedding frequency regulation, and fault ride-through. However, refined models of the control and electrical parts are usually simulated in another software (such as Simulink), which significantly simplifies the mechanical and aerodynamic components. It is evident that, in current technology, different physical dynamics of wind turbines are simulated by different software. While this can adapt to general scenarios, current simulation software platforms cannot provide adequate solutions for high-level research needs (such as studying the impact of grid dynamics on the mechanical vibration of wind turbines). A dedicated co-simulation platform is needed to simulate multiple physical dynamics simultaneously to address current requirements.
[0003] In this regard, several relevant technical solutions already exist, which achieve joint simulation of "pneumatic-mechanical-electrical-control" through the following mechanisms:
[0004] 1. OpenFAST software generates data through simulation in advance, and then inputs the data into Simulink;
[0005] 2. The Simulink software calls the OpenFAST software through a program interface at each step.
[0006] 3. OpenFAST works in conjunction with RTDS by being invoked in real time on the Linux system.
[0007] Among the publicly disclosed technical solutions, the first solution is not a joint simulation, and the Simulink signal is not transmitted back to OpenFAST as a control quantity, so it cannot reflect the impact of the electronic control dynamics on the turbine dynamics; the second solution's OpenFAST does not run independently, has weak scalability, and is difficult to compile into an independent program to run; the third technology requires the real-time simulation platform RTDS, which is relatively expensive and cannot be used at low cost. Summary of the Invention
[0008] To address the shortcomings of existing technologies, the purpose of this application is to provide a full dynamic co-simulation method for wind turbines, which can simulate the full dynamic process of wind turbines and features data synchronization and interaction, high flexibility, low cost, and high efficiency.
[0009] One aspect of this application provides a method for full dynamic co-simulation of wind turbine and electronic control systems, characterized by comprising:
[0010] Start the pre-established scheduler and wait to establish a communication connection with the simulation software;
[0011] The first simulation software and the second simulation software are started, and communication connections are established with the scheduler respectively, and they run independently; the first simulation software is used to simulate the aerodynamic and mechanical parts of the wind turbine, and the second simulation software is used to simulate the electrical and control parts of the wind turbine.
[0012] Determine if the data exchange time has been reached. If so, execute the data exchange through the scheduler and block the processes of the first and second simulation software. If not, continue to wait.
[0013] Determine if the first simulation software has finished. If it has, then the simulation is considered complete; otherwise, continue running.
[0014] Furthermore, the first simulation software includes OpenFAST, which is used to perform aerodynamic and mechanical simulations in wind turbine units;
[0015] The second simulation software includes Simulink, which is used to perform electrical and control simulations in wind turbine units.
[0016] Furthermore, the determination of whether the data exchange time has been reached, and if so, the data exchange is executed through the scheduler, and the blocking of the first simulation software and the second simulation software processes is controlled, including:
[0017] The scheduler obtains the first simulation data and the second simulation data that the first simulation software and the second simulation software need to interact with at this moment.
[0018] Control the blocking of the first and second simulation software processes;
[0019] The scheduler forwards the first simulation data received at this moment to the second simulation software, and the second simulation data is forwarded to the first simulation software.
[0020] Furthermore, the process blocking refers to the process of controlling the first and second simulation software to pause execution during data exchange.
[0021] Furthermore, after the scheduler forwards the first simulation data received at this moment to the second simulation software, and the second simulation data is forwarded to the first simulation software, the process further includes determining whether the data exchange is complete. If so, the first simulation software and the second simulation software are controlled to continue running independently. If not, the process continues to wait.
[0022] Further, determining whether the first simulation software has ended, and if so, determining that the simulation has ended, includes:
[0023] The scheduler receives the termination information sent by the first simulation software;
[0024] The scheduler forwards the termination information to the second simulation software, and the scheduler and the second simulation software terminate the process and end the simulation based on the termination information.
[0025] Furthermore, the step of launching the first simulation software and the second simulation software, and establishing communication connections with the scheduler respectively, includes:
[0026] The first simulation software establishes a communication connection with the scheduler through the first process communication channel;
[0027] The second simulation software establishes a communication connection with the scheduler through the second process communication channel.
[0028] Furthermore, the first simulation software establishes a communication connection with the scheduler through a first process communication channel, including embedding a dynamic link library (DLL file) in the first simulation software, and the first simulation software establishes an MPI communication connection with the scheduler by calling the dynamic link library (DLL file);
[0029] The second simulation software establishes a communication connection with the scheduler through a second process communication channel, including the second simulation software establishing a communication connection with the scheduler by calling the TCP / IP module.
[0030] A second aspect of this application provides a fully dynamic co-simulation system for wind turbine generators, comprising:
[0031] The first simulation software is used to perform aerodynamic-mechanical simulations in wind turbine units;
[0032] The second simulation software is used to perform control-electrical simulations in wind turbine units;
[0033] The scheduler module is used to establish communication connections with the first simulation software and the second simulation software, and to execute the data exchange between the first simulation software and the second simulation software when the system reaches the data exchange time.
[0034] Furthermore, the first simulation software and the second simulation software run independently on the same or different computers;
[0035] When the data exchange between the first simulation software and the second simulation software is executed by the scheduler, the first simulation software and the second simulation software enter a blocked state.
[0036] Compared with the prior art, this application has at least one of the following beneficial effects:
[0037] (1) This application achieves synchronization between two software programs by adding process blocking technology during the data exchange process, ensuring that the two platforms interact with data at the same time node, avoiding the problems of data inconsistency and simulation delay, improving the efficiency of simulation, and running the first simulation software and the second simulation software independently, ensuring that each program plays its full role, and improving the flexibility and scalability of program development, realizing joint simulation of the two software programs, thereby simulating the full dynamic process of wind turbine "gas-machine-electric-control", overcoming the problems of difficult synchronous exchange of simulation data, weak program scalability, and high investment cost in the existing technology.
[0038] (2) This application enables OpenFAST and Simulink to run independently on the same or different computers by running the first simulation software and the second simulation software independently, instead of through program calls. This not only ensures that each program can perform its full functions, but also improves the flexibility and scalability of program development.
[0039] (3) By embedding a communication module in OpenFAST as a DLL, this application can solve the problem of data interaction between OpenFAST and other programs, so that OpenFAST can run independently in co-simulation instead of being called through a program interface (API) with limited functions.
[0040] (4) This application can solve the problem of synchronous data interaction between OpenFAST and Simulink by setting process blocking during data interaction. Different modules of the wind turbine are run in the two software (OpenFAST runs the aerodynamic and mechanical parts, and Simulink runs the control and electrical parts), and data is exchanged at each data exchange time. Then they run independently at the same time until the next data exchange time, ensuring that the data exchange and simulation process of the two independent software are synchronized. Attached Figure Description
[0041] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:
[0042] Figure 1 This document presents a software configuration method and communication architecture diagram for a wind turbine generator set's full dynamic joint simulation implementation scheme, as described in one embodiment of this application.
[0043] Figure 2 This is a flowchart of a wind turbine generator's full dynamic joint simulation method for air turbine and electronic control, as described in one embodiment of this application.
[0044] Figure 3 This is a detailed flowchart of a wind turbine generator's full dynamic co-simulation method for air turbine and electrical control, as described in one embodiment of this application.
[0045] Figure 4 This is a communication architecture diagram of the first simulation software and the second simulation software in one embodiment of this application.
[0046] Figure 5 This is a diagram showing the simulation step size and data exchange step size definition of OpenFAST and Simulink in one embodiment of this application. Detailed Implementation
[0047] The present application will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any way. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application. These all fall within the protection scope of the present application.
[0048] Reference Figure 1 and Figure 2 The image shows an embodiment of a wind turbine's air turbine-electric control full-dynamic co-simulation method, comprising:
[0049] S100. Start the pre-established scheduling program and wait to establish a communication connection with the simulation software; S200. Start the first simulation software and the second simulation software, establish communication connections with the scheduling program respectively, and run independently; the first simulation software is used to simulate the aerodynamic and mechanical parts of the wind turbine, and the second simulation software is used to simulate the electrical and control parts of the wind turbine; S300. Determine whether the data exchange time has been reached. If so, execute the data exchange through the scheduling program and control the processes of the first simulation software and the second simulation software to be blocked. If not, continue to wait; S400. Determine whether the first simulation software has ended. If so, determine that the simulation has ended. If not, continue to run.
[0050] This application incorporates process blocking technology during data exchange to achieve synchronization between two software programs. This ensures that the two platforms interact with data at the same time, avoiding data inconsistency and simulation delays, thus improving simulation efficiency. Furthermore, the first and second simulation software programs run independently, simulating the aerodynamic and mechanical components and electrical and control components of the wind turbine generator, respectively. This ensures that each program performs its full functionality and enhances the flexibility and scalability of program development. It enables joint simulation of the two software programs, thereby simulating the entire dynamic process of the wind turbine generator's "aero-mechanical-electrical-control" system. This overcomes the problems of existing technologies, such as difficulty in synchronizing simulation data exchange, weak program scalability, and high investment costs.
[0051] During operation, the scheduler is first started, followed by the first and second simulation software, which establish communication connections with the scheduler. The first simulation software independently runs the simulation of the aerodynamic and mechanical parts of the wind turbine, while the second simulation software independently runs the simulation of the electrical and control parts. At each data exchange time, the first and second simulation software simultaneously send their respective exchange data to the scheduler. After receiving the data, the scheduler forwards it to the other party in the first and second simulation software. After sending is complete, the first and second simulation software run independently again. During data interaction, both software remain in a blocked state, waiting for the data interaction to complete. When the first simulation software is determined to have finished running, it sends an end message to the scheduler. The scheduler forwards the end message to the second simulation software, terminating the process with the end message. The second simulation software also terminates its simulation with the end message.
[0052] In some possible embodiments, the first simulation software includes OpenFAST for performing aerodynamic and mechanical simulations of the wind turbine; the second simulation software includes Simulink for performing electrical and control simulations of the wind turbine.
[0053] In this application, OpenFAST and Simulink run independently on the same or different computers, rather than through program calls, ensuring that each program performs its full functionality and improving the flexibility and scalability of program development. The problem of data synchronization between OpenFAST and Simulink is solved through a scheduler. The two software programs run different modules of the wind turbine (OpenFAST runs the aerodynamic and mechanical parts, and Simulink runs the control and electrical parts), exchanging data at each data exchange point, and then running independently again until the next data exchange point. This ensures that the data exchange and simulation process of the two independent software programs are synchronized, achieving joint simulation of OpenFAST (simulating aerodynamic and mechanical dynamics) and Simulink (simulating control and electrical dynamics), thereby simulating the full dynamic process of the wind turbine's "aero-mechanical-electrical-control" system. This overcomes the problems of existing technologies, such as difficulty in synchronizing simulation data exchange, weak program scalability, and high investment costs.
[0054] like Figure 3 As shown, in some specific embodiments, it is determined whether the data exchange time has been reached. If so, the data exchange is performed by the scheduler, and the processes of the first simulation software and the second simulation software are blocked. This includes: the scheduler obtaining the first simulation data and the second simulation data that the first simulation software and the second simulation software need to exchange at this time; controlling the processes of the first simulation software and the second simulation software to be blocked; the scheduler forwarding the first simulation data received at this time to the second simulation software, and the second simulation data forwarding to the first simulation software.
[0055] Specifically, during operation, when data exchange is required, the scheduler first receives the exchange data sent by the first and second simulation software. After the exchanged data is transmitted to the scheduler, the scheduler sends the data to be exchanged to the first and second simulation software respectively. The scheduler then terminates after completing the transmission. During this process, the process communication between the first and second simulation software uses blocking communication, waiting for the data exchange to complete before running independently until the next data exchange time. This ensures that the data exchange and simulation process of the two independent software programs are synchronized, improving data accuracy and consistency.
[0056] For example, consider OpenFAST and Simulink. OpenFAST and Simulink are two different software platforms, and their computational speeds are generally difficult to keep synchronized. For instance, within the same time period, a wind turbine section running for 1 second in OpenFAST might only have its electrical control section running for 0.5 seconds in Simulink. Data interaction between these two different time points can lead to erroneous simulation results. Process blocking technology can be used to synchronize the two software programs, ensuring that the two platforms interact with data at the same time points.
[0057] Among them, process blocking is used to control the first and second simulation software to pause their operation during data exchange.
[0058] In some specific embodiments, after the scheduler forwards the first simulation data received at this moment to the second simulation software, and the second simulation data is forwarded to the first simulation software, the method further includes determining whether the data exchange is complete. If so, the first simulation software and the second simulation software are controlled to continue to run independently. If not, the process continues to wait.
[0059] After the scheduler sends the data to be exchanged to the corresponding first and second simulation software, the system will then determine whether the subsequent simulation process is complete. After completion, the first and second simulation software will simultaneously and independently execute their respective running programs. Then the system will wait for the next data exchange time to ensure that the data exchange and simulation process of the two independent software are synchronized.
[0060] like Figure 3 As shown, in some specific embodiments, determining whether the first simulation software has ended, and if so, determining that the simulation has ended, includes: the scheduler receiving the end information sent by the first simulation software; the scheduler forwarding the end information to the second simulation software; and the scheduler and the second simulation software terminating the process and ending the simulation through the end information.
[0061] When the simulation ends, the system determines whether the first simulation software has finished. After the first simulation software finishes, it sends an end message to the scheduler. The scheduler then forwards the end message to the second simulation software. The scheduler terminates the process using the end message, and the second simulation software also terminates the simulation using the end message.
[0062] In some possible embodiments, the first simulation software and the second simulation software are started and establish communication connections with the scheduler respectively, including: the first simulation software establishes a communication connection with the scheduler through a first process communication channel; the second simulation software establishes a communication connection with the scheduler through a second process communication channel.
[0063] like Figure 4As shown, this application includes a scheduler that interacts with the first simulation software (OpenFAST) and the second simulation software (Simulink) through different inter-process communication channels. The first simulation software achieves inter-process communication by calling dynamic link libraries (DLL files) and establishes inter-process communication with the scheduler to exchange data.
[0064] Specifically, the first simulation software establishes a communication connection with the scheduler through a first process communication channel, including embedding a dynamic link library (DLL file) in the first simulation software, and the first simulation software establishes an MPI communication connection with the scheduler by calling the dynamic link library (DLL file).
[0065] By embedding a communication module as a DLL in OpenFAST, the problem of data interaction between OpenFAST and other programs can be solved, enabling OpenFAST to run independently in co-simulation, rather than being called through a program interface (API) with limited functionality.
[0066] The method proposed in this application enables OpenFAST to run as standalone software, ensuring the integrity of OpenFAST's functionality to the greatest extent and facilitating future expansion of its capabilities. It also allows OpenFAST and Simulink to run on different computers.
[0067] The second simulation software establishes a communication connection with the scheduler through the second process communication channel, including the second simulation software establishing a communication connection with the scheduler by calling the TCP / IP module.
[0068] like Figure 1 As shown, for example, taking OpenFAST as the first simulation software and Simulink as the second simulation software, specifically, OpenFAST (DISCON.dll): Before running OpenFAST, the ServoDyn configuration file (.dat) needs to be modified to specify the control modes for pitch, speed, and yaw (the names are for example only):
[0069] Select the DLL control mode: "5:user-defined from Bladed-style DLL".
[0070] Specify the input file for the DLL, such as DISCON.dll.
[0071] Specify the function name to be called in DISCON.dll, such as DISCON.
[0072] Specify the call step size for DISCON.dll, such as DT = 0.005s.
[0073] The DISCON.dll program should be located in the directory specified in the above configuration file and must meet the following input / output parameter specifications:
[0074]
[0075] DISCON.dll uses MPI (message passing interface) technology to achieve information exchange with the scheduler.
[0076] DISCON.dll is obtained by writing C / Fortran source code and then compiling and linking it using gcc. Its key logic is as follows:
[0077] 1. During the OpenFAST initialization phase, DISCON.dll first initializes the MPI and then establishes an MPI connection with the scheduler.
[0078] 2. Variable data in OpenFAST is passed to DISCON.dll through the avrSwap array. In each DISCON.dll call step, the DISCON function extracts the data to be passed to Simulink from the avrSwap array and sends the data to the scheduler through MPI_Send.
[0079] 3. The DISCON program automatically enters a blocked state by calling the MPI_Recv function, waiting for information sent by the scheduler. When it receives data from Simulink sent by the scheduler, it updates the corresponding data in the avrSwap array and returns aviFail=0.
[0080] The scheduler is also created by writing C source code and then compiling and linking it using gcc. Its key logic is as follows:
[0081] 1. During the scheduler initialization phase, MPI and TCP communication ports are established sequentially and connections are waited for. Then, communication connections are established with OpenFAST (DISCON.dll) and Simulink respectively.
[0082] 2. Once the above communication connection is established, data from OpenFAST (DISCON) and Simulink are waited for via MPI_Recv and TCP_Recv respectively.
[0083] 3. Upon receiving data, the data from OpenFAST is sent to Simulink via TCP_Send, and then the data from Simulink is sent to OpenFAST via MPI_Send.
[0084] 4. Returning to step 2, since both MPI_Recv and TCP_Recv are blocking wait operations, the scheduler is blocked, waiting for the next data interaction cycle.
[0085] In addition, servo control (including pitch control, speed control, and yaw control) and circuit models are run in Simulink, and communication with the scheduler is achieved by calling the TCP / IP module of the communication toolblx.
[0086] The sampling step size of the TCP / IP receiving module is the same as the DISCON.dll call step size (DT). It receives information from OpenFAST forwarded by the scheduler and uses it as input for servo control and circuit models. At the same time, the sampling step size of the TCP / IP sending module is also the same as the DISCON.dll call step size (DT), and sends the relevant data required by OpenFAST to the scheduler.
[0087] like Figure 5 As shown, in one implementation scheme, the simulation step size and data exchange step size of OpenFAST and Simulink are defined. OpenFAST and Simulink can be set to different simulation step sizes. The simulation step size of OpenFAST is Ts = 0.0125s, the simulation step size of Simulink is Ts = 0.005s, and the data exchange step size is DT = 0.05s. DT is an integer multiple of Ts. OpenFAST performs a data exchange every 4 simulation steps, and Simulink performs a data exchange every 10 steps. OpenFAST and Simulink align the simulation time through process blocking communication during data exchange.
[0088] A second aspect of this application provides a wind turbine full-dynamic co-simulation system, comprising: a first simulation software for performing aerodynamic-mechanical simulation of the wind turbine; a second simulation software for performing control-electrical simulation of the wind turbine; and a scheduler module for establishing a communication connection with the first and second simulation software, and executing data exchange between the first and second simulation software through the scheduler when the system reaches the data exchange time.
[0089] By integrating the first simulation software (responsible for aerodynamic-mechanical simulation) and the second simulation software (responsible for control-electrical simulation) and using the scheduler module to realize data exchange between the two, the accuracy and comprehensiveness of wind turbine simulation are greatly improved. The joint simulation mechanism proposed in this application is based on the free and open-source software OpenFAST and the general-purpose commercial simulation software MATLAB / Simulink that most research institutions have purchased. It has the advantage of low cost without the need to purchase additional hardware platforms. By customizing the data interaction time to reduce communication overhead, the simulation speed can be improved.
[0090] During operation, the scheduler in the scheduler module is first started, followed by the first and second simulation software, which establish communication connections with the scheduler. Then, aerodynamic-mechanical simulation and control-electrical simulation are performed separately. When the system reaches the preset data exchange time, the scheduler module triggers the data exchange process. The scheduler module obtains aerodynamic-mechanical simulation data from the first simulation software and sends it to the second simulation software; at the same time, the scheduler module obtains control-electrical simulation data from the second simulation software and sends it to the first simulation software. Then, they run independently until the next data exchange time, ensuring that the data exchange and simulation process of the two independent software are synchronized. This achieves joint simulation of OpenFAST (simulating aerodynamic and mechanical dynamics) and Simulink (simulating control and electrical dynamics), thereby simulating the full dynamic process of wind turbine "aero-mechanical-electrical-control". This overcomes the problems of existing technologies, such as difficulty in synchronizing simulation data exchange, weak program scalability, and high investment costs.
[0091] In some specific embodiments, the first simulation software and the second simulation software run independently on the same or different computers; when the data exchange between the first simulation software and the second simulation software is executed by the scheduler, the first simulation software and the second simulation software enter a blocked state.
[0092] In this application, the first simulation software and the second simulation software run independently on the same or different computers, instead of being implemented through program calls. This not only ensures that each program performs its full functions, but also improves the flexibility and scalability of program development. At the same time, the first simulation software and the second simulation software use the same data interaction cycle, and both processes use blocking communication to achieve process blocking communication and data synchronization.
[0093] The specific embodiments of this application have been described above. It should be understood that this application is not limited to the specific embodiments described above, and those skilled in the art can make various modifications or variations within the scope of the claims, which do not affect the substantive content of this application. The above-described preferred features can be used in any combination without conflict.
Claims
1. A method for full dynamic joint simulation of wind turbine and electronic control systems, characterized in that, include: Start the pre-established scheduler and wait to establish a communication connection with the simulation software; The first simulation software and the second simulation software are started, and communication connections are established with the scheduler respectively, and they run independently; the first simulation software is used to simulate the aerodynamic and mechanical parts of the wind turbine, and the second simulation software is used to simulate the electrical and control parts of the wind turbine. Determine if the data exchange time has been reached. If so, execute the data exchange through the scheduler and block the processes of the first and second simulation software. If not, continue to wait. Determine if the first simulation software has finished. If it has, then the simulation is considered complete; otherwise, continue running.
2. The wind turbine-electric control full dynamic joint simulation method according to claim 1, characterized in that, The first simulation software includes OpenFAST, which is used to perform aerodynamic and mechanical simulations in wind turbine units; The second simulation software includes Simulink, which is used to perform electrical and control simulations in wind turbine units.
3. The wind turbine-electric control full dynamic joint simulation method according to claim 1, characterized in that, The determination of whether the data exchange time has been reached, and if so, the data exchange is executed through the scheduler, and the processes of the first simulation software and the second simulation software are blocked, including: The scheduler obtains the first simulation data and the second simulation data that the first simulation software and the second simulation software need to interact with at this moment. Control the blocking of the first and second simulation software processes; The scheduler forwards the first simulation data received at this moment to the second simulation software, and the second simulation data is forwarded to the first simulation software.
4. The wind turbine-electric control full dynamic joint simulation method according to claim 3, characterized in that, The process blocking refers to the process of controlling the first and second simulation software to pause and wait during data exchange.
5. The wind turbine-electric control full dynamic joint simulation method according to claim 3, characterized in that, After the scheduler forwards the first simulation data received at this moment to the second simulation software, and the second simulation data is forwarded to the first simulation software, the process further includes determining whether the data exchange is complete. If so, the first simulation software and the second simulation software are controlled to continue to run independently. If not, the process continues to wait.
6. The wind turbine-electric control full dynamic joint simulation method according to claim 1, characterized in that, The step of determining whether the first simulation software has ended, and if so, determining that the simulation has ended, includes: The scheduler receives the termination information sent by the first simulation software; The scheduler forwards the termination information to the second simulation software, and the scheduler and the second simulation software terminate the process and end the simulation based on the termination information.
7. The wind turbine-electric control full dynamic joint simulation method according to claim 1, characterized in that, The process of starting the first and second simulation software and establishing communication connections with the scheduler includes: The first simulation software establishes a communication connection with the scheduler through the first process communication channel; The second simulation software establishes a communication connection with the scheduler through the second process communication channel.
8. The wind turbine-electric control full dynamic joint simulation method according to claim 7, characterized in that, The first simulation software establishes a communication connection with the scheduler through a first process communication channel, including embedding a dynamic link library (DLL file) in the first simulation software, and the first simulation software establishes an MPI communication connection with the scheduler by calling the dynamic link library (DLL file); The second simulation software establishes a communication connection with the scheduler through a second process communication channel, including the second simulation software establishing a communication connection with the scheduler by calling the TCP / IP module.
9. A fully dynamic joint simulation system for the air turbine and electrical control of a wind turbine generator set, characterized in that, include: The first simulation software is used to perform aerodynamic-mechanical simulations in wind turbine units; The second simulation software is used to perform control-electrical simulations in wind turbine units; The scheduler module is used to establish communication connections with the first simulation software and the second simulation software, and to execute the data exchange between the first simulation software and the second simulation software when the system reaches the data exchange time.
10. A wind turbine generator set gas turbine-electric control full dynamic joint simulation system according to claim 9, characterized in that, The first simulation software and the second simulation software run independently on the same or different computers; When the data exchange between the first simulation software and the second simulation software is executed by the scheduler, the first simulation software and the second simulation software enter a blocked state.