CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   CFX (http://www.cfd-online.com/Forums/cfx/)
-   -   Mesh deformation with wrong moving interfaces (http://www.cfd-online.com/Forums/cfx/122454-mesh-deformation-wrong-moving-interfaces.html)

mo-ca August 20, 2013 08:49

Mesh deformation with wrong moving interfaces
 
1 Attachment(s)
Hi,
Im trying to compute a pressure driven movement of a simple steel beam and facing the problem, that both sides of one interface (solid - fluid) move differently.

I enclosed a picture for better understanding:
http://www.cfd-online.com/Forums/att...1&d=1377002618

Both sides share the same expression of my defined movement and as one can see, it moves quite the expected way. But if you look closer, youll see the "original" position, which is the other part of the interface (solid).

I tried different meshing methods and definition of movements, but nothing really worked.

Its ansys cfx 14.5.

Thanks in advance

ghorrocks August 20, 2013 19:00

I do not understand your question. What are you asking?

mo-ca August 21, 2013 02:48

Quote:

Originally Posted by ghorrocks (Post 446999)
I do not understand your question. What are you asking?

Sorry if I didnt made my self clear enough.
The main problem is, that both sides of modelled interface move differently while having the same definition and I need some hints to find my error ..

ghorrocks August 21, 2013 06:28

Do you mean the FEA bit of the simulation is moving but the mesh of the CFD is not moving? Have you done the FSI tutorials which come with CFX and the ones available on the ANSYS customer site?

mo-ca August 22, 2013 01:44

Yes I did the fsi tutorials (Im trying 1way FSI, not 2way). The solid part ist not moving according to defined movement.

ghorrocks August 22, 2013 19:34

Did the tutorials run as expected? Isn't your application similar to the tutorials?

mo-ca August 23, 2013 01:24

4 Attachment(s)
the tutorial uses a 2way fsi, so cfx computes the fluid with resulting pressure forces and mechanical tries to deform you solid and returns the displacement, which is passed back to cfx for mesh deformation / displacement. what im trying to do is 1way fsi because of the computation time. so cfx is doing all the work (its a beta feature to deform solids using cfx).

during my runs it seems, that the not moving interface may be caused due to some meshing issue. if the mesh is coarse, sometimes it runs perfectly, but if you simply increase the number of elements, the simulation failes. unfortunately there is no "best practice" guideline. i tried using edge sizing, so that both sides of the interface do have the same amount of elements and spacing, but it didnt really help.

[edit]
I enclosed 4 images ... same geometry, meshing method and pre-setup was used
  1. Mesh with Relevance 100; Solid part of interface blue; colored: fluid part
  2. same as 1; other viewing angle
  3. Mesh with Relevance 0; Solid part of interface
  4. same as 3; fluid part of interface
I dont really understand, why the interface moves correctly with a coarse mesh and not with a fine one ...

brunoc August 23, 2013 14:12

I'm guessing you're talking about the mesh deformation feature that's been in CFX for years.

If that's the case, how are you modelling the plate movement? Are you calculating it using forces and CEL Expressions? Or are they just moving based on a pre-set equation?

Either way, you probably have something wrong with your expressions. Post them here so we can see what you're doing and please share more information from your model.

mo-ca August 23, 2013 16:45

hi and thanks for your help to this point.

within each side of my interface youll find the following displacement:
Code:

FLOW: Flow Analysis 1
  DOMAIN: Lamelle
    &replace BOUNDARY: INTF_Lamelle_Fluid Side 1
      Boundary Type = INTERFACE
      Interface Boundary = On
      Location = INTF_Lamelle_Fluid
      BOUNDARY CONDITIONS:
        HEAT TRANSFER:
          Option = Conservative Interface Flux
        END
        MESH MOTION:
          Option = Specified Displacement
          DISPLACEMENT:
            Displacement X Component = 0 [m]
            Displacement Y Component = Biegelinie2
            Displacement Z Component = 0 [m]
            Option = Cartesian Components
          END
        END
      END
      NONOVERLAP CONDITIONS:
        Boundary Type = WALL
        BOUNDARY CONDITIONS:
          HEAT TRANSFER:
            Option = Adiabatic
          END
          MESH MOTION:
            Option = Specified Displacement
            DISPLACEMENT:
              Displacement X Component = 0 [m]
              Displacement Y Component = Biegelinie2
              Displacement Z Component = 0 [m]
              Option = Cartesian Components
            END
          END
        END
      END
    END
  END
END

and the corresponding expressions:
Code:

      Biegelinie2 = -.75 [N] * Lamellenlaenge / (6 * YoungModulus * Flaechentraegheitsmoment)*(zTransformiert)^2*(3-zTransformiert/Lamellenlaenge)
      KoordTransfWinkel = -90 [deg]
      Flaechentraegheitsmoment = Lamellenhoehe^3 * Lamellenbreite / 12
      Lamellenbreite = 45 [mm]
      Lamellenhoehe = 0.5 [mm]
      Lamellenlaenge = 90 [mm]
      Mesh Stiffness = Aspect Ratio^2 / max(0.01 [mm],Wall Distance) + volcvol ^(-1/3)
      YoungModulus = 2.06e5 [MPa]
      maxLamellenverformung = maxVal( Total Mesh Displacement )@REGION:Lamellenflaeche
      zTransformiert = -sin(KoordTransfWinkel) * (xGlobal - -0.024 [m]) + (zGlobal) * cos( KoordTransfWinkel )

the mentioned problem does also exist, if im using a specific displacement of 1 mm

mo-ca September 26, 2013 09:15

anyone suggestions?

stumpy September 26, 2013 13:11

You've set displacement on side 1 of the interface. What about side 2?

mo-ca September 29, 2013 12:20

yes ... the specific displacement is set within the solid and fluid part of the interface ...


All times are GMT -4. The time now is 15:34.