|
[Sponsors] |
Mesh deformation with wrong moving interfaces |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
August 20, 2013, 09:49 |
Mesh deformation with wrong moving interfaces
|
#1 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
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: 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 |
|
August 20, 2013, 20:00 |
|
#2 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
I do not understand your question. What are you asking?
|
|
August 21, 2013, 03:48 |
|
#3 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
||
August 21, 2013, 07:28 |
|
#4 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
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?
|
|
August 22, 2013, 02:44 |
|
#5 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
Yes I did the fsi tutorials (Im trying 1way FSI, not 2way). The solid part ist not moving according to defined movement.
|
|
August 22, 2013, 20:34 |
|
#6 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
Did the tutorials run as expected? Isn't your application similar to the tutorials?
|
|
August 23, 2013, 02:24 |
|
#7 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
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
Last edited by mo-ca; August 23, 2013 at 04:05. |
|
August 23, 2013, 15:12 |
|
#8 |
Senior Member
Bruno
Join Date: Mar 2009
Location: Brazil
Posts: 277
Rep Power: 21 |
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. |
|
August 23, 2013, 17:45 |
|
#9 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
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 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 ) |
|
September 26, 2013, 10:15 |
|
#10 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
anyone suggestions?
|
|
September 26, 2013, 14:11 |
|
#11 |
Senior Member
Join Date: Apr 2009
Posts: 531
Rep Power: 21 |
You've set displacement on side 1 of the interface. What about side 2?
|
|
September 29, 2013, 13:20 |
|
#12 |
New Member
Join Date: Aug 2013
Posts: 23
Rep Power: 13 |
yes ... the specific displacement is set within the solid and fluid part of the interface ...
|
|
Tags |
cfx, interface, mesh deformation |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Gambit problems | Althea | FLUENT | 22 | January 4, 2017 04:19 |
udf error | srihari | FLUENT | 1 | October 31, 2016 15:18 |
CFX interpolating to a mesh with deformation | martindg | CFX | 5 | October 17, 2012 06:52 |
CrankNicholson returns wrong dimensions and sound speed when mesh is moving | lillberg | OpenFOAM Bugs | 6 | May 4, 2009 18:53 |
How to control Minximum mesh space? | hung | FLUENT | 7 | April 18, 2005 10:38 |