the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Obtaining fatigue-based frequency domain specifications for the design of controllers in wind turbines
Abstract. This work presents a methodology to (i) estimate fatigue using linear models and (ii) generate control specifications directly linked to the mechanical fatigue caused by driving loads for a wind turbine applications. The method is intended for frequency domain controller design techniques such as QFT or H∞ and is based on Dirlik’s method for fatigue assessment. The main advantage of using frequency domain approach is that the need of computationally expensive processess such as the generation of turbulent wind fields or aeroelastic simulations is reduced. As a consequence, the controller design method becomes more agile. The method has been validated by designing controllers for the reference 15 MW wind turbine based on fatigue specifications, obtaining simulation results with OpenFAST and comparing the fatigue results from a rainflow algorithm with the linear estimation. Fatigue has been reduced by 22 % to 35 % at different wind speeds corresponding to above rated operation. The mean fatigue estimation error is 1.07 %, proving the method is suitable for a wind turbine control application.
- Preprint
(1391 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 25 Dec 2024)
-
RC1: 'Comment on wes-2024-154', Anonymous Referee #1, 12 Dec 2024
reply
General comments
This work aims to help close the gap between controller design in the frequency domain and fatigue assessment which is done using nonlinear time-domain simulations. The proposed method uses Dirlik's fatigue estimation based on linear models and uses numerical differentiation to estimate the sensitivity of fatigue to the closed-loop performance of the linear system. This sensitivity can then be used to inform the control design in two ways: Which frequencies are important for fatigue reduction and estimate the change in fatigue based on a change in the controller (specification). The method is applied to improve the fatigue alleviation of the collective pitch and active tower damper controller.
Running nonlinear time-domain simulations over multiple wind seeds, as the IEC standards prescribe for fatigue analysis, takes a long time and prohibits fast iterations in the controller design. This method can reduce the iteration time between controller design and (simplified) analysis before a full nonlinear analysis is run. This makes this work scientifically relevant. However, I see two main improvements for this manuscript:
- The objective of the method is not aligned between the title, abstract, introduction, method, validation, and conclusion. Reading the method and validation section, I understand that this method estimates fatigue based on a controller or controller specification. However, from the introduction and conclusion, it seems like the control designer can specify how much fatigue reduction is desired and, based on this, make a control specification to achieve this. It's a subtle difference, but it makes the whole manuscript sometimes difficult to follow.- Dirlik's fatigue estimation method requires a regression to estimate the parameters G1, G2, and G3. However, it is not discussed how this regression is done. This requires (expensive) time-domain simulations to obtain data, making this slow. There is currently no discussion on the trade-off between first doing a slow calibration of Dirlik's method followed by fast control iterations (of which they only require a single iteration in this work) and the 'conventional' method of only using the slow time-domain simulations.
Overall, I think this work is suitable for wind energy science and could be accepted after revisions.Specific comments
I have summarized my interpretation of the objective from different sections, to highlight the misalignment.
- Title: The title signals that you can obtain controller specifications but the method shows that rather you can use controller specifications to generate a fatigue estimation, so the other way around.
- Abstract: "This work presents a methodology to (i) estimate fatigue using linear models and (ii) generate control specifications directly linked to the mechanical fatigue caused by driving loads for a wind turbine applications."
- I find 'linked' too vague, and (like was the case for the title) if I look at eq (9), you don't strictly generate control specifications based on fatigue but rather calculate the fatigue based on control specifications (similar to the title).
- Introduction: "The proposed method has two main characteristics: (1) it allows to identify the range of frequencies in which the specification contributes more to the overall fatigue and (2) it allows to quantify the expected fatigue decrease when a change in the specification or the controller is introduced."
- I think this is the clearest stated objective of the work that is also in line with the method and validation. Compared to the introduction, however, a new characteristic is introduced (identifying frequencies of interest).
- Method: The method section describes the method to estimate the sensitivity of the fatigue with respect to the output spectrum (eq 5) and the change in fatigue based on the control specification (eq 9).
- The validation section first uses eq (5) to identify frequencies of interest. I think it is then too vague about applying eq (9) to generate control specifications. The specification for desired fatigue reduction is only shown all the way at the end of this section.
- Conclusion: "This work has presented a method for the estimation of mechanical fatigue based on the use of the linear model of a wind turbine and its controllers and a numerical calculation of the variation of the damaged with the load spectrum. Then, this method has been used for the design of control specifications."
- This section again presents the objective in a slightly different way.
I think that aligning these different sections will greatly help readers in understanding the objective of the work and also in how the proposed method works and is applied. This will also make it much easier for readers to use your method in their own work. My recommendation would be to clearly define and give meaningful names to fatigue specification (percentage of desired fatigue reduction), control specification, linear prediction of fatigue based on the control specification, and linear prediction of fatigue based on the actual linear controller used in closed-loop. And subsequently clearly use these throughout the document and align the objectives stated in the different sections.Introduction:
- I think the argumentation is strong but but could benefit by adding references to related scientific work.
- "This work" line 29: The first time reading this, it was unclear whether this referred to your work or to Tibaldi (2016).Frequency domain assessment of mechanical fatigue
- Line 58: $\Delta D_{NB}$ is not defined in the text. The sentence introducing this equation says that "it estimates the number of stress cycles and their respective amplitudes..." making it seem like there are two outputs. By continuing the paper, it eventually becomes clear what it means, but it would be better if it was defined here.
- I didn't know much about this subfield and feel that this provided a great overview.Using linear models for the estimation of fatigue and the generation of control specifications
- Line 90-91: It would be nice to have a reference to literature talking about models of rotor effective wind speed.
- Line 97: In these steps, I miss doing a regression to find G1, G2, and G3 for Dirlik's method that you use. It's fine if you want to specify that elsewhere if you don't consider it to be part of your main method. But also for the results section, it is unclear how you obtained G1, G2, and G3.
- Line 100: Make it more specific by specifying 'the output spectrum'. In hindsight, it makes sense that it should be the output spectrum, but I think specifying it here already would just make it easier for readers to understand.
- Line 111: 'shows that higher frequencies lead to higher fatigue'. I don't see that as the highest frequencies don't have a high $\Delta D_\%$.
- Line 116: 'which has been tested via simulation' is a slightly weak claim since you don't provide those results. But indeed, from your final results, we see that the estimation is quite accurate. Maybe you can make this claim stronger by providing these simulation results or referring forward to your results.
- Out of curiosity, why do you express $\Delta D$ and $\Delta S$ as percentages instead of absolute sensitivities/derivatives? If that is significant, it could be a nice insight to add to the method. (If not, also totally fine to leave out.)
- Why did you choose to do a numerical differentiation of the fatigue damage rather than take the analytical derivative of Dirlik's fatigue formula? Again, if that is significant, it could be a nice insight to add to the method. (If not, also totally fine to leave out.)Validation for the 15MW reference wind turbine
- Line 138-139: ROSCO also has the option for tip speed ratio tracking control in below-rated, so the statement '...in which a quadratic control law is used...' can be more nuanced.
- Figure 2: It would be nice if the x-limits were the same between Figures 1, 2, and 4 for easier comparison as a reader.
- Line 190: Very nice explanation, but it might be stronger if you specify beforehand what the desired reduction of fatigue is. If I understand it correctly, your method can be used to know which frequencies are important for the control specification (this is also nicely illustrated here) _and_ to estimate a priori how much fatigue reduction you can expect, and design for. This latter point is not made in this section until Table 3 all the way at the end of this section. I think you can show this aspect of your method by showing how you design the controller for a specific fatigue reduction.
- Line 197-199: You say that since the ROSCO specification is used, your controller is expected to outperform ROSCO. If the specification is equal to ROSCO, I would expect that they perform about the same. Why do you expect something else?
- Figures 5 and 6: There is no legend for the black line and the different circles. It would be good to add that.
- Figures 5 and 6: I haven't used Nichols plots myself, so maybe this is easy to interpret for someone with more experience with them, but visually, it seems like there is too much going on, and it is difficult to see what the different lines do and represent. Do you think it would be possible to improve the visualization in these figures by decluttering them?
- Table 2: The 'mean' column is empty.
- Line 244-246 and Table 3: You use the standard deviation of the collective pitch signal to assess the pitch activity. I think this unfairly favors your method since the standard deviation doesn't penalize your higher frequency activity with the pitch actuators. I think you should use the actuator duty cycle, which is also more closely related to actuator wear.
- Table 3: I think the paper would gain clarity when you consistently and throughout the whole paper refer to fatigue specification (percentage of desired fatigue reduction), control specification, linear prediction of fatigue based on the control specification, and linear prediction of fatigue based on the actual linear controller used in closed-loop. Maybe thinking of clear terms for these and defining them in the introduction or at the first mentioned place would help readers' understanding.
- Figure 9: The legend of this figure is missing. Could you add one in addition to (or instead of) specifying the lines in the caption? This will also help colorblind people distinguish the lines.
- Figure 10: This figure is also not colorblind friendly and uses quite a convoluted way to represent your data, in my opinion. I would suggest putting the wind speed on the x-axis, the fatigue reduction on the y-axis, and using colors to compare the frequency and time domain results.
- The acronym ATD is not defined on its first use.
- It is unclear how the linearized models are obtained. Could you add a paragraph explaining how you obtained them?
- What is the turbulence intensity of the simulation?Conclusions
- Is it fair to claim an improvement over the ROSCO controller without mentioning here again that the ROSCO controller does not have ATD?
- Line 276: The sentence starting with 'Besides' doesn't make complete sense to me. 'Besides' signals a contradiction which is seemingly not present.
- Is another contributing factor to the difference between the actual and the estimated fatigue your assumption on linearity (on line 116)?Technical corrections
- Line 45: undefined citation
- Line 130: Spelling correction: System
- Line 158: Spelling correction: wind turbine
- Line 221: Spelling corrections: met most of the time
- Line 253: Referencing correction: Table 3
- Line 258: Spelling correction: table
- Line 266: Spelling correction: damage
- Line 287: Spelling correction: businessCitation: https://doi.org/10.5194/wes-2024-154-RC1
Viewed
HTML | XML | Total | BibTeX | EndNote | |
---|---|---|---|---|---|
74 | 19 | 2 | 95 | 2 | 2 |
- HTML: 74
- PDF: 19
- XML: 2
- Total: 95
- BibTeX: 2
- EndNote: 2
Viewed (geographical distribution)
Country | # | Views | % |
---|
Total: | 0 |
HTML: | 0 |
PDF: | 0 |
XML: | 0 |
- 1