Skip to content

ServoDyn-StC: StC_SA_MODE validation logic#3348

Open
RBergua wants to merge 2 commits into
OpenFAST:devfrom
RBergua:ServoDyn_StC_logic
Open

ServoDyn-StC: StC_SA_MODE validation logic#3348
RBergua wants to merge 2 commits into
OpenFAST:devfrom
RBergua:ServoDyn_StC_logic

Conversation

@RBergua
Copy link
Copy Markdown
Contributor

@RBergua RBergua commented May 24, 2026

This PR is ready to be merged

Feature or improvement description
I have been using the Structural Control (StC) module and observed that the Semi_Active control mode (StC_SA_MODE) was validated unconditionally.

For example, using the Active Control Mode through user subroutine (StC_CMODE = 3), the code would still check for a valid Semi Active Control Mode:
image
And OpenFAST aborts if no valid mode is selected:
image

To avoid this friction for the user, the source code has been updated and the validation logic for the semi-active control mode only applies if StC_CMODE = 1.

In addition, the input files have been updated to clarify this (see PR in r-test: OpenFAST/r-test#181):
1 StC_SA_MODE - Semi-Active control mode {1: velocity-based ground hook control; 2: Inverse velocity-based ground hook control; 3: displacement-based ground hook control 4: Phase difference Algorithm with Friction Force 5: Phase difference Algorithm with Damping Force} [used only when StC_CMODE=1]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant