September 4, 2019 at 6:59 amMrRioesSubscriber
I'm running into a strange problem. I am running a transient flow simulation in Fluent. In this simulation there is a moving flap in the outflow of a pipe. For the moving part I am using dynamic meshing. I played around with the settings and the initial mesh, so that it seemed appropriate for the dynamic meshing.
When I preview the dynamic meshing process in Fluent, everything seems to be ok. No faults or errors and the mesh looks fine. But when I start the calculation process (same time step as in the preview process) after 40 to 50 time steps, I get the error message of negativ cell volume. This doesn't happen in the preview process. There the mesh behaves fine for 500 time steps.
What could that be ?
September 4, 2019 at 9:34 amDrAmineAnsys Employee
Does the motion depend on flow field/properties etc..?
September 5, 2019 at 1:09 pmMrRioesSubscriber
No the motion doesn't depend on the flow etc.
September 5, 2019 at 1:19 pmDrAmineAnsys Employee
Quite weird: which release version are you using?
Have you tried reducing time step size with flow ON?
September 6, 2019 at 6:34 amMrRioesSubscriber
I am working in Fluent 19R2.
Now I tried a few things, i've seen the mesh motion in all but the last step is fine. So I played around with some more parameters, and now it works. Don't know why, but it works.....
I will attach some pictures where you can see the problem.
This is while preview, the time step is 0.001s and it goes till step 22
Here the mesh while calculation, same time step of 0.001s and step 22
September 6, 2019 at 12:26 pmDrAmineAnsys Employee
What have you changed so that is working now?
September 13, 2019 at 1:19 pmMrRioesSubscriber
sorry for the late response but i was a bit busy.
To get it running i seperated the boundary mesh form the rest of the mesh. Then i defined for this mesh the same rigid body movement as for the moving wall. So it wouldn't "blow up" anymore.
September 13, 2019 at 2:13 pmDrAmineAnsys Employee
Thanks for updating the group. Please mark this then as "is Solved". There is an option to deform adjacent boundary layer zone to keep the mesh quality safe. You might try that if it resolves the issue. But still weird that the you require that only when flow is solved.
Anyway happy to see progressing.
- You must be logged in to reply to this topic.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- Suppress Fluent to open with GUI while performing in journal file
- Floating point exception in Fluent
- What are the differences between CFX and Fluent?
- Heat transfer coefficient
- Getting graph and tabular data from result in workbench mechanical
- The solver failed with a non-zero exit code of : 2
- Difference between K-epsilon and K-omega Turbulence Model
- Time Step Size and Courant Number
- Mesh Interfaces in ANSYS FLUENT
- error in cfd post
© 2023 Copyright ANSYS, Inc. All rights reserved.