Bug report SrvD_SetExternalInputs

[TianyuanWangi]

Bug description

For the new version of OpenFAST, v5.0.0, (SUBROUTINE FAST_Solution0_T), SrvD_SetExternalInputs is only used for a single wind turbine. Does this overlook the multiple-rotor cases?

To Reproduce

Steps to reproduce the behavior:

1. Compile with '...'
2. Run '...' case with '...' settings
3. Open '...' output
4. See the error

Expected behavior

Screenshots, if applicable

OpenFAST Version

**************************************************************************************************
 OpenFAST

 Copyright (C)  National Renewable Energy Laboratory
 Copyright (C)  Envision Energy USA LTD

 This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
 See the "LICENSE" file distributed with this software for details.
 **************************************************************************************************

 OpenFAST-v2.0.0
 Compile Info:
  - Architecture: 64 bit
  - Precision: double
  - Date: Nov 27 2018
  - Time: 17:19:38
 Execution Info:
  - Date: 11/29/2018
  - Time: 10:52:28-0700

System Information (please complete the following information):

• OS: <e.g. Ubuntu 14.04 or macOS 10.12>
• Compiler: <e.g. GFortran 4.4>
• Compiler settings: <e.g. CMake flags or other settings>

Additional context

[andrew-platt]

Dear @TianyuanWangi,

Thanks for bringing this to our attention. There is a discrepancy in the code with the the calls to SrvD_SetExternalInputs. During initialization, only external inputs for ServoDyn on the first rotor is getting set. In the later calls, it is set per rotor.

However, there is a broader context here that is important to keep in mind. The external inputs are only used when OpenFAST is coupled to SimuLink and ServoDyn PCMode=4. At present, it is not possible to use the Simulink interface with multiple rotors.

To clear up confusion on this, we will do the following:

• add rotor loop around first call to SrvD_SetExternalInputs
• add error about multirotor not being available with the SimuLink interface

Regards,