Is it possible to run AeroDyn, excluding the tower influence on the fluid local to the blade nodes, and the tower drag and similarly for ElastoDyn.
In other word just considering the rotor. If it is possible can someone provide an example of XXXXX_Aerodyn.dat and XXXXX_ElastoDyn.dat
It appears that AeroDyn thinks AF00_Coords.txt is the airfoil data file, not the airfoil shape file. Have you changed the names of the airfoil data files in the AeroDyn primary input file (AFNames) to point to AF00_Coords.txt instead of the actual airfoil data file, e.g. RotorSE_FAST_IEA_landBased_RWT_AeroDyn15_Polar_00.dat?
In the AeroDyn Primary file I point to the Polar_OX.dat files and inside the polar files I point to the coordinates files:
@“AF00_Coords.txt” NumCoords ! The number of coordinates in the airfoil shape file. Set to zero if coordinates not included.
AF00_BL.txt BL_file ! The file name including the boundary layer characteristics of the profile. Ignored if the aeroacoustic module is not called.
1 NumTabs ! Number of airfoil tables in this file. Each table must have lines for Re and Ctrl.
please make sure that the openfast version that you are calling is 2.5.0. When you call OF from the terminal, this should appear on screen
If OF is not 2.5.0, please shift to OF 2.5.0, the latest release
If OF is 2.5.0, please make sure that you are calling this OF model github.com/OpenFAST/r-test/tree … oAcoustics
This must run successfully
Once this runs, try introducing your changes one by one and see when OF breaks.
Another good test is to try turning off the BLMod flag in the aeroacoustic module github.com/OpenFAST/r-test/blob … ut.dat#L14
I received your e-mail. Overall, the files you sent look OK to me, except I see one issue. You have set InclUAdata in the airfoil data file to False, but you still include the 30 UA parameters in the file. Does setting InclUAdata = True solve your problem?
We’ll, I’m really not sure then. For the specific model you are running now, all I can suggest is that you compile in debug mode and run the simulation through the debugger. This should help you isolate the error.
Can you run any OpenFAST simulation (e.g., using one of the sample models from the r-test) without error?