|June 14, 2013, 05:07||
Moving Mesh with no gaps
Join Date: Sep 2009
Posts: 65Rep Power: 8
I've been working on a model using AMI to achieve a moving mesh. This seems to be working now, ie the mesh moves, which is great. The problem I am facing now is that the model I put together was just a quickie example to get to know how to use AMI etc. the actual model requires that the moving wall slides, physically touching, over the static wall. I am trying to model a quarter turn ball valve which means that in the closed position the valve must hold back the upstream fluid.
When I try to create the mesh for this model I now find that I cannot approach the AMI interface patches close enough for the leakage to be insignificant. I am meshing the moving and static geometries separately end then merging them. This gives me the best looking mesh in 2D. I'm finding that for an external facing AMI patch (on the moving zone) I can get to about 0.3 units, but with an internally facing patch (static) I can only get to about 0.5 units. When I convert to mm scale this obviously gives about 0.8mm gap around the valve.... no use!
Is there any way to physically slide two walls over each other, effectively in contact with each other? IS there something in the AMI approach I am missing?
All the AMI models in the tutorials are essentially stator/rotor models which have spaces between the rotor or stator and the AMI interface patches.
Hope someone can shed some light here.
|Thread||Thread Starter||Forum||Replies||Last Post|
|How to let the mesh motion solver just solve a small region near a moving boundary?||zhajingjing||OpenFOAM Running, Solving & CFD||9||April 28, 2016 04:15|
|SnappyHexMesh for internal Flow||vishwa||OpenFOAM Native Meshers: snappyHexMesh and Others||23||August 6, 2014 03:50|
|Resisting torque on a moving mesh||floooo||OpenFOAM||3||March 29, 2010 20:18|
|external flow with snappyHexMesh||chelvistero||OpenFOAM||11||January 15, 2010 20:43|
|Gambit problems||Althea||FLUENT||21||February 6, 2001 08:05|