NWTC

I don't have any experience building Simulink models for real-time simulation. I have read some comments about it in the MATLAB/Simulink documentation that I sent you. I do not think you have to modify the header file; I think you need to make sure MATLAB is setting the appropriate preprocessor flag...

It looks like you've got multiple definitions of the header files that are needed for the build process. I am not sure why it would be looking for files in both the extern/include and rtw/c/src directories. Did you modify anything in the build process? Or any of the include paths? When you build usi...

The error you are showing indicates that the path to FAST_Library.h is not correct in the mex command. That said, the OpenFAST interface to Simulink has not worked after NREL moved from FAST8 to OpenFAST (the error messages in your attachment refer to this problem). I initiated a pull request to fix...

Hi, Charlie. I am not exactly sure what the problem is, but the warning message indicates that it thinks there is a variable called "!" in the template that has a value of "20.0000 0.6300 0.6300 0 0 0 0 0 0 0 0 0 0". Perhaps it's not reading a table correctly? Do you get this pro...

Joseph,

My script assumes you have installed the OpenFAST matlab-toolbox.

1. Yes 2. Using the Matlab toolbox, I think the following code should do what you want. It reads the primary TurbSim file called 'TurbSim.inp' , sets the wind speed to 5 m/s, and writes a new TurbSim file called 'NewTurbSimFile.inp', using the format in a template TurbSim file called 'TurbSim_templa...

My guess is that the controller you are using (or some other part of the code that didn't come from NREL) is trying to read from a file named 'U:\git\VAero\windturbineframework_mreich\fort.86', which doesn't exist.

I have run the Matlab code with the file you attached, and it runs. I did notice a problem with how it reads the rotating frame column (i.e., it assumes nothing is in the rotating frame with this version of the .lin file), so I've submitted a pull request for that here: https://github.com/OpenFAST/m...

I suspect that the code isn't linking with the new compiled version of the FAST_types.f90/ElastoDyn_Types.f90 files, which is what causes the access violations. (I have had this problem before, myself. I am not sure if this is a Visual Studio problem or if there is something wrong in the way the FAS...

Your TIMESR input is rotated 180 from the mean wind direction. The mean u component should almost always be positive, but you've defined them to all be negative in your input file. TurbSim's output is actually equivalent to your input file, though. It uses the convenction that u is positive in the m...

Anup,

Is the wind direction at the hub 0 degrees? You should be able to see this in the TurbSim summary file.

If it is 0, I would not expect any difference in the wind time series output, including the sign.

Hi, Paul. I don't see anything in your code that would be problematic. I suspect that the code isn't linking with the new compiled version of the FAST_types.f90 files, which is what causes the access violations. (I have had this problem before, myself. I am not sure if this is a Visual Studio proble...

Juan, You need to tell the compiler to preprocess the source file. With gfortran, you add the "-cpp" option to the build command that you used (on Intel Fortran, you use '-fpp'): gfortran -cpp -c -fPIC DISCONChanges.f90 In these particular source files, though, the preprocessor directives ...

Hi Anup, You should get exactly the same time series output at the single point that you input; I would assume that you set that point to be at the hub. If you are not getting that output, check the time-series input file to make sure your measurement point is exactly on a grid point and that it's r...

Hi, Jan. I think this bug has been fixed in the latest version of OpenFAST (https://github.com/openfast/openfast). It might be in the master branch, but I'm pretty certain it was merged into the dev branch. Let me know if that doesn't fix the problem. When you set nComp to 2, though, it just sets w ...