NREL / ROSCO

A Reference Open Source Controller for Wind Turbines
https://rosco.readthedocs.io/en/latest/
Apache License 2.0
105 stars 91 forks source link

runFAST Matlab/Simulink problem #263

Open Viper19103 opened 11 months ago

Viper19103 commented 11 months ago

When running the runfast.m file in ROSCO, what is the reason for the following error? 屏幕截图 2023-10-10 202619

dzalkind commented 11 months ago

Hi, I cannot tell what the issue is without more information about your setup.

What example are you trying to run? What branch or version of ROSCO? Have there been any changes?

Have you been able to review the solutions here? https://github.com/NREL/ROSCO/issues/231

Best, Dan

Viper19103 commented 11 months ago

I am running the ROSCO controller that came with ROSCO2.4.1, unchanged, and this problem occurred after running runfast.m

dzalkind commented 11 months ago

It's difficult for us to support older versions of the code. Please update and try some of the solutions proposed by others in the issue I cited. Most of the solutions involved the setting up of the OutList variable in the matlab script before Simulink was run.

We regularly test other examples in ROSCO not involving Matlab/Simulink.

Viper19103 commented 11 months ago

This is also a problem with the latest version

Melancho7ee commented 6 months ago

Dear @Viper19103 ,

I encountered similar errors as you did. Although I have added this variable BldPitch1 to the output of ElastoDyn, I still get the same error as you did after running runFAST.m.

I recommend to do as follows (The following is based on ROSCO 2.8.0 I am using):

  1. Starting from line 36 of runFAST.m, comment out the codes afterwards.
    
    %% Premake OutList for Simulink

OutList = {'Time'}; OutList = [OutList; Param.IWP.OutList; Param.EDP.OutList; Param.ADP.OutList; Param.SvDP.OutList; ];



2. After completing the above processing, run `runFAST.m`.
3. Directly open the `ROSCO.mdl`, then run it at least twice.
4. Note the error messages that appear during these Simulink runs. They may be the true errors that you need to solve.

Personally, I can solve this problem after performing the above debugging process. However, I'm not sure if your problem is the same as mine. The above contents are for your reference.

Best regards,