Replies: 2 comments
-
Hi Zollhafen, I'm also quite new to using FLOWUnsteady for wind turbine simulations and am facing some issues with setting up the simulation. Did you succeed in setting up this simulation? If yes, could you please share the .jl file you used or perhaps help me set up a new one? The main problem I'm encountering seems to be related to the turbine_flag and geometry generation. I've set both the CW_flag and the turbine_flag to true, but the geometry I get appears incorrect: the leading edge (LE) of the lattice is not facing the flow, and at the root, the elements collapse. After several attempts, I managed to create a correct geometry, but only by setting the turbine_flag to false and the CW_flag to true (I compared the lattice I obtained with the one shown in QBlade). However, I think this approach is completely wrong because it treats the turbine as a propeller. Thank you in advance for your help. Best regards |
Beta Was this translation helpful? Give feedback.
-
Hey, sorry for the late answer. You can see my Setup file at the end. Even though I had to make some canges to the FLOWVLM Package. I flipped the sign of the effective angle of attack before the c_l value is pulled from the Polar. (in FLOWVLM_rotor.jl in the function _calc_distributedLoads_lookuptable I changed Effective angle of attack (rad)
to then get the right c_l I also flipped the sign of my Polar to negative. I don't know if this is because I did not apply the Turbine Flag correctly or whats the cause for this, but I noticed that's the way I get the correct c_l and c_d values across the blade. Following, some things to look at: -To check if the c_l and c_d values are correct for you case, I recommend passing the debug=true flag in the uns.run_simulation. This will show you the spanwise c_l and c_d values at every timestep in your Blade result files -Your geometry problem could result from the fact that as far as I can remember the Turbine Flag does not change the geometry of your Blade. (Turn the Flag on and off and check if the Geometry changes). That way when you adjust your geometry so that it fits the Windturbine and you turn on the Flag it will behave as a Propeller. (Not sure anymore about this point, as you say you can only model the geometry correctly without the turbine_flag, so you might have to double check my answer to that) -For my case, my polars already included Hub and Tip losses and Mach and 3D corrections. The latter two cannot be disabled via a Flag in FLOWUnsteady and you have to disable them manually if you want to do so (FLOWVLM roto_ccb.jl FLOWVLM2OCCBlade) I hope I could help. import FLOWUnsteady as uns #config wHUB_postwist_negcl_turbon_woALLcorrection_negtheta_posalpha Height VonTopVerlauf_sign_revrun_name = "Wind_turbine" # Name of this simulation save_path = joinpath(".", run_name) # Adjust the path accordingly paraview = false # Whether to visualize with Paraview ----------------- GEOMETRY PARAMETERS ----------------------------------------Rotor geometryrotor_file = "WindTurbine.csv" # Rotor geometry NOTE: If
|
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
I am configuring a setup for a WindTurbine simulation, with precalculated aifoilpolars and contours.
I already know that this is possible through the validation studies made by Ed Alvarez.
For the WEA the suction and pressure side of the rotor need to be reversed compared to the classical case. But would this mean I also need to inverse the calculation of lift or C_l?
You see I am encountering some issues because I am not yet completely familiar with the calculation process in the rVPM.
Before diving into it I wanted to check if someone has already successfully put FLOWUnsteady in "Power generation" mode and can pinpoint at what locations I need to make adjustments or if there are already implemented parameters that adjust the solver to this.
Thank you and best regards
Beta Was this translation helpful? Give feedback.
All reactions