Dear @Emanuel.Rergis,
What I noticed in the source code was that when Use_F_TBL = TRUE, the linear TMD stiffness and stop spring stiffness and damping are not used.
Best regards,
Dear @Emanuel.Rergis,
What I noticed in the source code was that when Use_F_TBL = TRUE, the linear TMD stiffness and stop spring stiffness and damping are not used.
Best regards,
Dear Dr. @Jason.Jonkman
I hope you’re doing well. Thanks for your reply. Following your comment regarding the StrcCtrl module, you mentioned that when Use_F_TBL = TRUE, the linear TMD stiffness and stop spring stiffness and damping are not used. However, based on the attached snapshot, it seems that this might not be entirely the case, or I must have misunderstood your previous messages.
In my test, I set the stiffness values (k) in the x and y directions to zero, yet OpenFAST aborted during the initialisation stage with the following messages:
StC_ValidatePrimaryData: StC_X_K must be > 0 when StC_X_DOF is enabled
StC_ValidatePrimaryData: StC_Y_K must be > 0 when StC_Y_DOF is enabled
Could you please clarify under which conditions Use_F_TBL = TRUE actually disables or bypasses the linear stiffness and damping parameters?
It would help me better understand whether the observed behaviour is expected or if additional configuration is required.
I’ve attached a screenshot showing the output for your reference.
Thank you very much for your time and guidance.
Best regards,
**Emanuel M. Rergis
**
Dear @Emanuel.Rergis,
Yeah, the core StC code was not developed at NREL and there are clearly some things that need to be cleaned up when reviewing the source code. You can see that when Use_F_TBL is enabled, the linear TMD stiffness and stop spring stiffness and damping are not used, even if their values are checked for physical correctness, which should not be the case.
Best regards,