CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > ANSYS > FLUENT

unassigned interface zone warning in FLUENT

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree20Likes

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   April 27, 2013, 06:42
Question unassigned interface zone warning in FLUENT
  #1
New Member
 
Join Date: Apr 2013
Posts: 1
Rep Power: 0
hapsari devi is on a distinguished road
I am a beginner in using CFD Fluent, and when I am trying to check my mesh in fluent, it said that :
WARNING : unassigned interface zone detected for interface 6
WARNING : unassigned interface zone detected for interface 7
WARNING : unassigned interface zone detected for interface 11
would you please explain it for my why is it happen and how to solve it?
hapsari devi is offline   Reply With Quote

Old   April 29, 2013, 02:47
Default
  #2
Super Moderator
 
-mAx-'s Avatar
 
Maxime Perelli
Join Date: Mar 2009
Location: Switzerland
Posts: 3,297
Rep Power: 41
-mAx- will become famous soon enough
The reason is, you defined interface in Gambit (or another mesher), but you didn't set them in fluent (define/grid-interfaces)
__________________
In memory of my friend Hervé: CFD engineer & freerider
-mAx- is offline   Reply With Quote

Old   April 29, 2013, 03:26
Default
  #3
Senior Member
 
Paritosh Vasava
Join Date: Oct 2012
Location: Lappeenranta, Finland
Posts: 732
Rep Power: 22
vasava will become famous soon enough
In my opinion these errors are perfectly normal especially if you are simulating a case with interfaces.

The boundaries in two separate domains share one interface. Now these boundaries can not be declared as any other type (e.g. wall, inlet, outlet etc). If you declare them as e.g. wall then they can not be part of the interface. Thus when you bring your mesh to fluent it notices that you have not declared the type of boundary, and simply warns you about it.

So there is nothing wrong with the 'warning'. However you must ensure that the interface is properly set-up during meshing as well as in fluent.
anijg05 likes this.
vasava is offline   Reply With Quote

Old   April 29, 2013, 11:48
Default
  #4
Senior Member
 
OJ
Join Date: Apr 2012
Location: United Kindom
Posts: 473
Rep Power: 19
oj.bulmer will become famous soon enough
Just make sure you avoid any words like zone, surface, interface etc. while defining any surface in meshing program. FLUENT grabs these words and assigns the boundary conditions to it, though often you dont want it to.

OJ
oj.bulmer is offline   Reply With Quote

Old   July 29, 2014, 09:17
Default
  #5
New Member
 
viral nagar
Join Date: Jun 2014
Location: surat,gujarat
Posts: 8
Rep Power: 11
viralnagar5692 is on a distinguished road
my dear but taking the wall as in interface solution is not initialized fluent.[/QUOTE]
viralnagar5692 is offline   Reply With Quote

Old   July 30, 2014, 06:45
Default
  #6
New Member
 
viral nagar
Join Date: Jun 2014
Location: surat,gujarat
Posts: 8
Rep Power: 11
viralnagar5692 is on a distinguished road
Quote:
Originally Posted by vasava View Post
In my opinion these errors are perfectly normal especially if you are simulating a case with interfaces.

The boundaries in two separate domains share one interface. Now these boundaries can not be declared as any other type (e.g. wall, inlet, outlet etc). If you declare them as e.g. wall then they can not be part of the interface. Thus when you bring your mesh to fluent it notices that you have not declared the type of boundary, and simply warns you about it.

So there is nothing wrong with the 'warning'. However you must ensure that the interface is properly set-up during meshing as well as in fluent.
my dear frend,but i am facing the same problem in fluent and my solution is not initialized then how can i move ahead??
i have mentioned in mesh under named selction tool and also taken as interface in fluent
when i m going to initialize,error shows like-"Int. Flow-unassigned interface zone"
help me....
viralnagar5692 is offline   Reply With Quote

Old   September 15, 2014, 08:05
Default WARNING: Unassigned interface zone detected for interface
  #7
New Member
 
rahul kumar
Join Date: Jun 2014
Posts: 24
Rep Power: 11
R4RAHUL is on a distinguished road
same problem here, but when I change the interface zone to wall then it calculate the solution but when I assign it as a interface zone then it shows error why is it so???????
I want to do it as a interface zone.
R4RAHUL is offline   Reply With Quote

Old   September 15, 2014, 08:15
Default
  #8
Senior Member
 
ghost82's Avatar
 
Rick
Join Date: Oct 2010
Posts: 1,016
Rep Power: 26
ghost82 will become famous soon enough
Post some pictures of your interfaces.
ghost82 is offline   Reply With Quote

Old   September 16, 2014, 01:30
Default geometry attaching
  #9
New Member
 
rahul kumar
Join Date: Jun 2014
Posts: 24
Rep Power: 11
R4RAHUL is on a distinguished road
I am attaching the Image of my geometry.
the green part shown in geometry, causing the interference problem, there is a upper surface and a lower surface both when assigned interference shows error.
Attached Images
File Type: jpg Capture.jpg (24.7 KB, 515 views)
R4RAHUL is offline   Reply With Quote

Old   January 3, 2016, 17:05
Lightbulb For a cylindrical reactor
  #10
New Member
 
Amr Mohamed
Join Date: Dec 2015
Posts: 1
Rep Power: 0
amr2006 is on a distinguished road
Hi all,

I faced the same problem and I overcome it by changing the boundary condition type to be (symmetry) and it worked for me as I am using a cylinder. I am not sure if having symmetry will be logic for your geometry but I guess (after I saw your geometry) it is a valid assumption

Amr,
amr2006 is offline   Reply With Quote

Old   March 10, 2016, 08:24
Default unassigned interface zone detected for interface
  #11
New Member
 
djamal
Join Date: Jan 2016
Posts: 6
Rep Power: 10
didane is on a distinguished road
You may need to go to Mesh interface in FLUENT and create the interface by yourself might solve your problem...in case if it did not work go to MESH and suppress the contacts under connections.
didane is offline   Reply With Quote

Old   May 6, 2016, 06:28
Default cylinder interface
  #12
New Member
 
Sepi
Join Date: Apr 2016
Location: South Africa
Posts: 6
Rep Power: 9
sepi_705 is on a distinguished road
Hi all

I am also facing a similar problem. I got that error message when I tried to initialize my solution in Fluent.
My geometry is a simple cylinder with a fluid domain around it. I want to show the flow of air (and dust particles) over and into my cylinder, so I defined the outer area of my cylinder as 'wall' and called the top surface of my cylinder 'interface' so Fluent would recognize it as an interior. I subtracted my cylinder from my fluid domain to do the meshing.

Please help me! I am very confused

(here's a link to what I've managed so far if anyone wants to take a look: https://drive.google.com/open?id=0B9...jJxS09qaURraE0)

Last edited by sepi_705; May 6, 2016 at 06:39. Reason: added a link
sepi_705 is offline   Reply With Quote

Old   May 6, 2016, 08:52
Default
  #13
Senior Member
 
Join Date: Nov 2013
Posts: 1,965
Rep Power: 26
pakk will become famous soon enough
Quote:
Originally Posted by sepi_705 View Post
..and called the top surface of my cylinder 'interface' so Fluent would recognize it as an interior. ...
First of all: interior and interface are two different things. That is why they are also two different words.

Interface means, for Fluent at least, that it is a 'border' between two things. Graphically:

Code:
+--------------+
|              |
|    Zone A    |
|              |
+--Interface1--+
+--Interface2--+
|              |
|    Zone B    |
|              |
+--------------+
Interface1 is the boundary of zone A, and Interface2 is the boundary of zone B. In Fluent, you need to tell Fluent that Interface1 and Interface2 'touch' each other. After you have done that, both interfaces are 'assigned', and zones A and B are connected to each other.

If you don't tell Fluent that an interface is connected, it is unassigned. And Fluent will have a problem. If you make them walls, or symmetry, or something else, Fluent will not complain anymore that there are unassigned interfaces, but zones A and B will not be connected.


It looks like you (sepi_705) did the following:
Code:
+--------------+
|              |
|    Zone A    |
|              |
+--Interface1--+
You have one interface in your system. That does not make any sense for Fluent, Fluent does not understand what you want. An interface should always be assigned to a different interface, so you can not have 1 interface in your system.
And, not only Fluent is confused. I am also confused. Why are you making a system with one interface???
sumit.sh, edmondlam, lev and 5 others like this.
pakk is offline   Reply With Quote

Old   May 8, 2016, 09:57
Default
  #14
New Member
 
Sepi
Join Date: Apr 2016
Location: South Africa
Posts: 6
Rep Power: 9
sepi_705 is on a distinguished road
Quote:
Originally Posted by pakk View Post
First of all: interior and interface are two different things. That is why they are also two different words.

Interface means, for Fluent at least, that it is a 'border' between two things. Graphically:

Code:
+--------------+
|              |
|    Zone A    |
|              |
+--Interface1--+
+--Interface2--+
|              |
|    Zone B    |
|              |
+--------------+
Interface1 is the boundary of zone A, and Interface2 is the boundary of zone B. In Fluent, you need to tell Fluent that Interface1 and Interface2 'touch' each other. After you have done that, both interfaces are 'assigned', and zones A and B are connected to each other.

If you don't tell Fluent that an interface is connected, it is unassigned. And Fluent will have a problem. If you make them walls, or symmetry, or something else, Fluent will not complain anymore that there are unassigned interfaces, but zones A and B will not be connected.


It looks like you (sepi_705) did the following:
Code:
+--------------+
|              |
|    Zone A    |
|              |
+--Interface1--+
You have one interface in your system. That does not make any sense for Fluent, Fluent does not understand what you want. An interface should always be assigned to a different interface, so you can not have 1 interface in your system.
And, not only Fluent is confused. I am also confused. Why are you making a system with one interface???
Hi

I understand what you are saying, and I think that I may have names the faces incorrectly, but I think that I now have a situation where I have two different interfaces as shown in the image above, with the fluid in the cylinder and the fluid in the domain being separate.
Do I have to connect these two interfaces to get flow both within my fluid domain and cylinder?
If so, how do I achieve this?

I have uploaded a document showing some of the images I generated.
https://drive.google.com/open?id=0B9...FAyTldZYmFRMzA

Thank you for the help
sepi_705 is offline   Reply With Quote

Old   October 22, 2016, 09:43
Default
  #15
New Member
 
Roya.TR
Join Date: Feb 2014
Posts: 9
Rep Power: 12
Roya.TR is on a distinguished road
dear pakk
i have this problem too,
how acn i trell to fluent that interfaces touch each other?
Roya.TR is offline   Reply With Quote

Old   October 24, 2016, 11:28
Default
  #16
Senior Member
 
Join Date: Nov 2013
Posts: 1,965
Rep Power: 26
pakk will become famous soon enough
Give the two interfaces the type "interface".
Select the menu "Create/Edit Mesh Interfaces".
For "Interface Zones Side 1", select one side, for "Interface Zones Side 2" the other side.
sumit.sh, Ajay Vincent and azores like this.
pakk is offline   Reply With Quote

Old   July 3, 2017, 10:53
Default
  #17
New Member
 
AnsysUser
Join Date: Jul 2016
Posts: 9
Rep Power: 9
Shreman is on a distinguished road
Thanks..I solved unassigned interface error changing a name from "interface" to some other like ¨intfr¨ .It worked.Merci
Shreman is offline   Reply With Quote

Old   July 3, 2017, 10:59
Default
  #18
Senior Member
 
Join Date: Nov 2013
Posts: 1,965
Rep Power: 26
pakk will become famous soon enough
I assume you did that in the mesher, because if you did it in Fluent it makes no sense.

What happened then was that Fluent made this a wall. Your liquid will not go this surface anymore.

If you really wanted the surface to be an interface (such that liquid can go through), you did not solve the problem. You simply got rid of the error message.
pakk is offline   Reply With Quote

Old   December 7, 2017, 07:37
Default interface in the heat exchanger
  #19
Senior Member
 
sivakumar selvaraju
Join Date: Mar 2009
Location: India
Posts: 205
Rep Power: 18
sivakumar is on a distinguished road
Send a message via Skype™ to sivakumar
Hi All,
I am working on the finned tube heat ex-changer, I just followed the tutorial in the youtube.

I am using Gambit for pre-processing and I have defined the BC's there itself.

Defined the Zones as hotFluid, coldFluid and tube.

The fins thickness is 3 mm, the inner cylinder and fins I consider as tube. The hot fluid and cold fluid are separated by the tube (cylinder with fins)

I have problem with the interfaces between hot fluid and cold fluid, I have defined tube inner as interface1, tube outer as interface2.

I exported the mesh to fluent, while checking the mesh I am getting the following error.

Checking mesh............... Error: interface zone 6 has two adjacent cell zones.


Error: interface zone 7 has two adjacent cell zones.
.........
WARNING: Unassigned interface zone detected for interface 6
WARNING: Unassigned interface zone detected for interface 7............
Done.


WARNING: Mesh check failed.


Error: interface zone 6 has two adjacent cell zones.


Error: interface zone 7 has two adjacent cell zones.


Error: interface zone 6 has two adjacent cell zones.


Error: interface zone 7 has two adjacent cell zones.


Error: interface zone 6 has two adjacent cell zones.


Error: interface zone 7 has two adjacent cell zones.


I tried to define the interface in the mesh interface section but no success. I couldn't see any connected faces.


Please help me to fix the issue.


Thanks in advance,


Sivakumar
Attached Images
File Type: jpg interface.jpg (98.7 KB, 65 views)
sivakumar is offline   Reply With Quote

Old   December 11, 2017, 02:25
Default
  #20
Super Moderator
 
-mAx-'s Avatar
 
Maxime Perelli
Join Date: Mar 2009
Location: Switzerland
Posts: 3,297
Rep Power: 41
-mAx- will become famous soon enough
You need to define the interface in Gambit (you did it), and then you need to assign the "coupling" in fluent.
Once this last point will be achieved in fluent, the check mesh will be sucessfull.
According to your picture, the tube_inner and tube_outer interfaces should be exactly the same surfaces, except one belongs to cold fluid domain, and the other to the hot one..
__________________
In memory of my friend Hervé: CFD engineer & freerider
-mAx- is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[blockMesh] non-orthogonal faces and incorrect orientation? nennbs OpenFOAM Meshing & Mesh Conversion 7 April 17, 2013 06:42
[Gmsh] discretizer - gmshToFoam Andyjoe OpenFOAM Meshing & Mesh Conversion 13 March 14, 2012 05:35
latest OpenFOAM-1.6.x from git failed to compile phsieh2005 OpenFOAM Bugs 25 February 9, 2010 05:37
[OpenFOAM] Paraview command not found hardy ParaView 7 September 18, 2008 05:59
[blockMesh] BlockMeshmergePatchPairs hjasak OpenFOAM Meshing & Mesh Conversion 11 August 15, 2008 08:36


All times are GMT -4. The time now is 06:43.