search

OpenFAST / openfast

Main repository for the NREL-supported OpenFAST whole-turbine and FAST.Farm wind farm simulation codes.
http://openfast.readthedocs.io
Apache License 2.0
648 stars 447 forks source link

I have a problem in trying to calculate the 15MW wind turbine for the IEA, the calculation appears to abort automatically after more than a second, the error is reported as follows, what should I do to resolve the fatal error #1718

Open lin990316 opened 11 months ago

lin990316 commented 11 months ago

Microsoft Windows [版本 10.0.22000.2176] (c) Microsoft Corporation。保留所有权利。

C:\Users\lin>cd E:\IEA-15-240-RWT-master\OpenFAST\IEA-15-240-RWT-UMaineSemi - lintest

C:\Users\lin>E:

E:\IEA-15-240-RWT-master\OpenFAST\IEA-15-240-RWT-UMaineSemi - lintest>openfast_x64.exe IEA-15-240-RWT-UMaineSemi.fst

OpenFAST

Copyright (C) 2023 National Renewable Energy Laboratory Copyright (C) 2023 Envision Energy USA LTD

This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY. See the "LICENSE" file distributed with this software for details.

OpenFAST-Unversioned from e8ec53f9c7f9d3f6a13bfb61dba12a0ca04d8a2f Compile Info:

OpenFAST input file heading: IEA 15 MW offshore reference model on UMaine VolturnUS-S semi-submersible floating platform

Running ElastoDyn. Running AeroDyn. Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 1) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 2, blade 1) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 4, blade 1) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 5, blade 1) Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 2) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 2, blade 2) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 4, blade 2) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 5, blade 2) Warning: Turning off Unsteady Aerodynamics because polar has constant data. (node 1, blade 3) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 2, blade 3) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 4, blade 3) Warning: Turning off Unsteady Aerodynamics because C_nalpha is 0. (node 5, blade 3) Running InflowWind. Running HydroDyn. Generating incident wave kinematics and current time history. Reading in WAMIT output with root name ".\HydroData/IEA-15-240-RWT-UMaineSemi". Computing radiation impulse response functions and wave diffraction forces. Calculating second order difference-frequency force using the full quadratic transfer function. Running MoorDyn (v2.0.0, 2022-12-08). This is MoorDyn v2, with significant input file changes from v1. Copyright: (C) 2022 National Renewable Energy Laboratory, (C) 2019 Matt Hall Parsing MoorDyn input file: .\IEA-15-240-RWT-UMaineSemi_MoorDyn.dat Created mooring system: 3 lines, 6 points, 0 rods, 0 bodies. Finalizing initial conditions using dynamic relaxation. t=60 FairTen 1: 2.43287E+06, 2.44526E+06, 2.43537E+06 Fairlead tensions did not converge within TMaxIC=60 seconds. MoorDyn initialization completed. Running ServoDyn. Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows). Using legacy Bladed DLL interface. Time: 0 of 6000 seconds. The BEM solution is being turned off due to low TSR. (TSR = 0). This warning will not be

Running ROSCO-v2.7.0 A wind turbine controller framework for public use in the scientific field Developed in collaboration: National Renewable Energy Laboratory Delft University of Technology, The Netherlands

Generator speed: 0.0 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 10.0 m/s

FAST_Solution:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOut put(node 3, blade 1):UA_CalcOutput:UA_BlendSteady:Temporarily turning off UA due to high angle of attack or low relative velocity. This warning will not be repeated though the condition may persist.

FAST_Solution:FAST_AdvanceStates:AD_UpdateStates:BEMT_UpdateStates:UpdatePhi(node 28, blade 2):BEMT_UnCoupledSolve:There is no valid value of phi for these operating conditions: Vx = 3.36591E-02, Vy = -1.5645, rlocal = 68.256, theta = 4.28567E-02, geometric phi = 3.1201. This warning will not be repeated though the condition may persist. (See GeomPhi output channel.)

FAST_Solution:FAST_AdvanceStates:ED_ABM4:ED_CalcContStateDeriv:SetCoordSy:Small angle assumption violated in SUBROUTINE SmllRotTrans() due to a large tower deflection (ElastoDyn SetCoordSy). The solution may be inaccurate. Simulation continuing, but future warnings from SmllRotTrans() will be suppressed. Additional debugging message from SUBROUTINE SmllRotTrans(): 1.3 s FAST_Solution:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOut put(node 42, blade 1):UA_CalcOutput:Mach number exceeds 0.3. Theory is invalid. This warning will not be repeated though the condition may persist.

Warning: SkewedWakeCorrection encountered a large value of chi (90.395 deg), so the yaw correction will be limited. This warning will not be repeated though the condition may persist. See the AD15 chi output channels, and consider turning off the Pitt/Peters skew model (set SkewMod=1) if this condition persists.

FAST_Solution:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOut put(node 3, blade 1):UA_CalcOutput:Mach number exceeds 1.0. Equations cannot be evaluated.

OpenFAST encountered an error at simulation time 1.4 of 6000 seconds. Simulation error level: FATAL ERROR

Aborting OpenFAST.

E:\IEA-15-240-RWT-master\OpenFAST\IEA-15-240-RWT-UMaineSemi - lintest>

jjonkman commented 11 months ago

Dear @lin990316,

It looks like your simulation is numerically unstable. I first see a warning that TSR = 0, which suggests that you've initialized the rotor speed to zero; is that correct? With active control enabled, we generally recommend initializing the model with the rotor speed and blade-pitch angles set to their expected (mean) value conditioned on the mean hub-height wind speed you are simulating. Does that solve the issue?

Best regards,

lin990316 commented 8 months ago

First of all, thank you for your answer, the above problem I have been in accordance with your guidance to solve, but also very sorry to forget to express my gratitude to you after the solution, recently in the calculation of the IEA-15MW wind turbine, I encountered a similar problem in the calculation of the shutdown state of 33m/s wind speed, change the angle of the incoming wind level to 60 degrees, in the calculation of the error and stop calculating, in the angle of the incoming wind for the 0, 30, 90 degrees can be calculated to the completion of the normal, may I ask what the setup is incorrect, and what methods can be used to resolve the problem, look forward to replying to the, thank you!

Time: 1600 of 4000 seconds. Estimated final completion at 15:10:42.

FAST_Solution:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOut put(node 40, blade 1):UA_CalcOutput:Mach number exceeds 0.3. Theory is invalid. This warning will not be repeated though the condition may persist.

FAST_Solution:FAST_AdvanceStates:ED_ABM4:ED_CalcContStateDeriv:SetCoordSy:Small angle assumption violated in SUBROUTINE SmllRotTrans() due to a large blade deflection (ElastoDyn SetCoordSy). The solution may be inaccurate. Simulation continuing, but future warnings from SmllRotTrans() will be suppressed. Additional debugging message from SUBROUTINE SmllRotTrans(): 1608.9 s Generator speed: 0.4 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.5 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.6 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.7 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.8 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.8 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Generator speed: 0.3 RPM, Pitch angle: 0.0 deg, Power: 0.0 kW, Est. wind Speed: 0.5 m/s Time: 1670 of 4000 seconds. Estimated final completion at 15:10:46.

FAST_Solution:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOut put(node 38, blade 2):UA_CalcOutput:Mach number exceeds 1.0. Equations cannot be evaluated.

OpenFAST encountered an error at simulation time 1675.2 of 4000 seconds. Simulation error level: FATAL ERROR

Aborting OpenFAST.

E:\IEA-15-240-RWT-master\OpenFAST\IEA-15-240-RWT-UMaineSemi - lintest - new计算>

jjonkman commented 8 months ago

Dear @lin990316,

I'm not sure I understand what you are asking. If you are modeling the wind turbine in a parked or idling state in high winds, I would have expected that you'd disable the wake and unsteady airfoil aerodynamics models in AeroDyn, as well as the controller in ServoDyn, but it doesn't appear that you've done that.

Best regards,

lin990316 commented 8 months ago

Okay Dr., I tried to change the settings according to your instruction, and after disabling those models, the calculation starts normally but stops at 1870 seconds with the error "tower strike", does it mean that the wind turbine will be destroyed in that condition? Or is there something else I have set up incorrectly? I would appreciate your guidance. Thank you for your help.

Time: 0 of 4000 seconds.

FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:AD_CalcOutput:RotCalcOutput:BEMT_CalcOu tput(node 2, blade 1):UA_CalcOutput:UA_BlendSteady:Temporarily turning off UA due to high angle of attack or low relative velocity. This warning will not be repeated though the condition may persist. Time: 240 of 4000 seconds. Estimated final completion at 03:17:17.

FAST_Solution:FAST_AdvanceStates:ED_ABM4:ED_CalcContStateDeriv:SetCoordSy:Small angle assumption violated in SUBROUTINE SmllRotTrans() due to a large blade deflection (ElastoDyn SetCoordSy). The solution may be inaccurate. Simulation continuing, but future warnings from SmllRotTrans() will be suppressed. Additional debugging message from SUBROUTINE SmllRotTrans(): 246.9 s Time: 1870 of 4000 seconds. Estimated final completion at 03:17:37.

WARNING: Tower strike. This warning will not be repeated though the condition may persist.

FAST_Solution:FAST_AdvanceStates:AD_UpdateStates:SetDisturbedInflow:TwrInfl:Tower strike.

OpenFAST encountered an error at simulation time 1877 of 4000 seconds. Simulation error level: FATAL ERROR

Aborting OpenFAST.

jjonkman commented 8 months ago

OpenFAST will trigger this "tower strike" error if a blade aerodynamic analysis node ends up within the cylindrical volume that makes up the tower, when one of the tower influence models in AeroDyn is enabled. In a real wind turbine, a tower strike is likely catastrophic. But you haven't provided enough information to know if this result is expected for the simulation set up you are using.

Best regards,