Skip to content

Issues with TMD in ServoDyn-Stc #3189

@RBergua

Description

@RBergua

I'm trying to model a wave energy converter (WEC) in OpenFAST as follows:
Image

I tried modeling the hull as the platform in ElastoDyn and the internal reaction mass (IRM) as a TMD in ServoDyn as part of the structural control module (StC).

For reference, the hull represents 80% of the total system mas, and the IRM represents 20% of the mass.

I started doing some tests in still water conditions without mooring lines.

When modeling the system without IRM, I'm obtaining the expected behavior in heave (e.g., in this case the device moves upwards because it is missing the weight of the IRM).
Image

As part of this verification phase, I also locked the 6 rigid body platform motions in ElastoDyn and looked at the behavior of the IRM. As expected, the ElastoDyn platform stays in place and there is a constant hydrostatic force upwards due to the buoyancy. Looking at he IRM, we can see that it moves 1.63 m downwards due to the gravity acceleration. This behavior is the expected one. For reference, I also include the velocity and the force that the spring of the TMD does in the vertical direction.
Image

Unfortunately, if I try to combine the platform with heave motion and the TMD, the solver experiences a numerical instability. For reference, I'm using OpenFAST dev-tc (https://github.com/OpenFAST/openfast/tree/dev-tc).
Image
Image

As can be observed, the solver does not converge and I get a heave displacement of 3E12 m. I tried using several correction iterations (NumCrctn = 3) and dropping the time step (dt = 1E-3 s). But the results didn't improve.

I understand that this could be a limitation of the loose coupling of ServoDyn within OpenFAST. I tried reducing the IRM mass ratio from 20% to 10%. In this case, I can make it run if I only enable the heave DOF for the platform.
Image

But I have convergence issues again if I enable the 6 platform DOFs (despite the system only moving in the z direction in these tests).

I guess one way to overcome this loose coupling limitation would be modeling the IRM (i.e., spring/dashplot-mass) in SubDyn taking advantage of the spring elements (#1889 (comment)). Although setting up the proper damping in the different directions may be a bit challenging.

Any thoughts or suggestions?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions