Skip to content

[FEATURE] Structural Aeroelasticity #28

@MOLOCH-dev

Description

@MOLOCH-dev

Problem Statement

@RaphZufferey and I are working on a Flapping wing robot with flexible wings. Using PteraSoftware, we aim towards "closing the loop" in the UVLM solver by adding aeroelastic structural effects due to wing flexibility. We have a model that describes structural effects of the wing as wing torsion around the leading edge.
Currently, PteraSoftware predefines the movement of the wing cross-sections, wings and the airplane as a whole before the UVLM solver is called. The overall aim of our solver is to enable redefinition of the wing with dynamic movement parameters (such as wing twist) at every timestep. This will enhance the capabilities of PteraSoftware and introduce the potential framework for adding feedback loops within simulations.
Integrating this aeroelasticity solver in PteraSoftware this would require some changes to the current structuring of the "Movement" class, which would allow for the redefinition of wing movement at every timestep. We have implemented this change and would like to have an open discussion about whether this method seems feasible or if there are any other approaches currently being investigated.

Proposed Solution

We would like to add the Aeroelasticity Solver as another feature within the Unsteady Ring Vortex Lattice Solver. The deformation we are trying to express is a "Wing Cross-section Twist" that can be redefined at every timestep. To implement this, I have mirrored the existing logic of the "Movement" class in PteraSoftware. A short diagram explaining my implementation can be found below :
MovementChange

This solution is stable and convergent upto a certain extent. At large "twist" angles, the solver is unable to keep up with the sudden deformation. So we plan to further add a convergence layer to interpolate the twist till a stable solution is achieved. We will update you on our progress with the same.

To this end, I have created some bugs/issues in PteraSoftware regarding some force outputs that don't make physical sense, #27. I will like to actively work on this issue as well and am open to your ideas/suggestions on this implementation. I will be able to take on some work to implement the changes/additional features.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions