[bahar]

Hello everybody,
I'm working on a 3D helical H-rotor wind turbine and using moving mesh to simulate fluid.
I received this warning during mesh checking:
''cannot create surface from sliding interface zone'', Is it important enough to notice?
What should I do so?
p.s: domain picture is attached.

Thank you in advance for your attention
Bahar

[sondinho]

Originally Posted by bahar

Hello everybody,
I'm working on a 3D helical H-rotor wind turbine and using moving mesh to simulate fluid.
I received this warning during mesh checking:
''cannot create surface from sliding interface zone'', Is it important enough to notice?
What should I do so?
p.s: domain picture is attached.

Thank you in advance for your attention
Bahar

I've got the same message while simulating dynamic motion of valve. But the results are ok so I would ignore that in your case.

[bahar]

Dear sondinho,
Thank you in advance for your attention.

I have serious problem by residuals. Really, in unsteady flow Epsilon residual began to fluctuate until all residuals increase tremendous and finally solution diverge; however, in steady case didn't appear any problem.

Again, I appreciate your attendance.

[jamalf64]

I think interfaces are very important for moving mesh(sliding mesh) but when you are using MRF and you have conformal mesh they are not important.
if you show me your geometry without mesh, maybe I can halep you but I dont sure.

Be Success.

[bahar]

Dear Jamal,
Thank you in advance!
I've already attached an obvious picture of blades, I have defined required surfaces as interface but I cannot understand why such a problem appear?
Be success.

[-mAx-]

did you create interfaces-couple in Fluent? (grid/interfaces)
Once it is done, you can re-check the mesh and then the warning should disappear

[bahar]

Dear mAX,
Thank you for your attention!

Already, I have defined all sliding surfaces as ''Grid Interfaces''! but I recieve this warning in both 2D and 3D flow!

Best Regards,
Bahar

[kunvd]

Hello bahar, have you got the solution to the problem ?

[bahar]

Hello kunvd,

This warning did not disappear in my solution while checking results showed that it do not have critical effect on solution.

[vasava]

Did you name the walls related to the interface? If you did, you can delete the name and then import the the mesh. Just to check if fluent can deal with the 'un-named' faces itself.

[CFDiran]

Hi
Your warning is not very important.
I think that this warning is due to differences in the size of the element in sides of interface.

[kunvd]

This is my experience...During the interface creation, empty 'wall' s are created. So, while displaying the mesh, if these empty 'wall's are selected, the warning appears.

P.S. Empty in the sense, these boundary conditions are not applied in your mesh.

[Gowrav]

yes i got the same..