How To Draw Campbell Diagram In Excel

Thanks for the explanation @ebranlard. ya.. I should take a closer look at the posts above. You mentioned previously, sometimes the modes can be hard to interpret. I'll go with "1st drivetrain torsional mode" then.

For the plotCampbellData script, I had a go on the Matlab one for the .lin file generated from the r-test example "5MW_Land_ModeShapes", and got the following error message:

Index exceeds matrix dimensions.
Error in Plot_CampbellData (line 93)
CampbellPlotData.lineLabels = txt(2: nLines+1, 1);

What might be the problem? If I understand it right from the comments in fx_mbc3.m, campbell_diagram_data.m and Plot_CampbellData.m, I would already have (the data for plotting) a Campbell Diagram, by running the following lines in Matlab? and the content of the excel file should look like the one I posted above, right?

[mbc_data] = fx_mbc3('5MW_Land_ModeShapes.1.lin');
BladeLen = 61.191;
TowerLen = 85.410;
[CampbellData] = campbell_diagram_data(mbc_data, BladeLen, TowerLen,'MBC3_transformed_data.xlsx');
[num,txt,CampbellPlotData] = Plot_CampbellData('MBC3_transformed_data.xlsx','Modes_Data','Campbell Diagram');

By the way, I'm also getting the following warnings from the "fx_mbc3()" function, I'm guessing it's no big deal as all 3 blades sheared one same input file. But does it matters?

Running mbc3 (v2.0, 29-Jan-2018)
Rotating channel "ED OoPDefl1, (m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED IPDefl1, (m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED TwstDefl1, (deg)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED BldPitch1, (deg)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED Spn2MLxb1, (kN-m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED Spn2MLyb1, (kN-m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootFxb1, (kN)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootFyb1, (kN)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootFzb1, (kN)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootMxb1, (kN-m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootMyb1, (kN-m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Rotating channel "ED RootMzb1, (kN-m)" does not form a unique blade triplet. Blade(s) not found: 2 3
Multi-Blade Coordinate transformation completed

Another thing is, I found an old post by Dr. Jason Jonkman back in 2011, where he provided a CampbellDiagram.xls spreadsheet for extracting Eigen information etc. Within the file, I found an example of Campbell Plot looks like below. I noticed that the frequencies of each mode are set to be not dependent on the rotor speed. Is it a legitimate simplifying approach for wind turbines? If so, I presume it'd be OK if I manually identify each mode required on the Campbell Diagram (as I have shown for the "1st drivetrain torsional mode" above) and plot the corresponding undamped frequency values as horizontal lines on Campbell Diagram and call it a day?

The third thing - very sorry for my clumsiness and the long message - after I went through the r-test "5MW_Land_ModeShapes" (from which the result above was obtained), I intend to practice the mode shape extraction procedure for a monopile offshore wind turbine, based on the r-test example: "5MW_OC3Mnpl_DLL_WTurb_WavesIrr".

as I turned SubDyn feature ON (CompSub=1) and ran the analysis, the following error message showed up, which seems to indicate SubDyn does not yet support linearisation?

"FAST_InitializeAll:FAST_Init:ValidateInputData:Linearization is not implemented for the any of
the substructure modules. "

On the other hand, if SubDyn is turned OFF, of course the model is then not connected properly to the seabed or indeed anything , and error messages regarding "SkewedWakeCorrection" and "small angle assumption" show up.

Does this mean, based on the current OpenFAST, it is not yet possible to perform a linearisation + mode visualisation for a monopile-OWT?

Sorry if the stuff I mentioned is considered basic. I really appreciate your help..