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

unassigned interface zone warning in FLUENT

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

Like Tree1Likes
  • 1 Post By -mAx-

Reply
 
LinkBack Thread Tools Display Modes
Old   April 27, 2013, 05: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, 01:47
Default
  #2
Super Moderator
 
-mAx-'s Avatar
 
Maxime Perelli
Join Date: Mar 2009
Location: Switzerland
Posts: 2,972
Rep Power: 30
-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)
mahdi_izadi likes this.
__________________
In memory of my friend Hervé: CFD engineer & freerider
-mAx- is offline   Reply With Quote

Old   April 29, 2013, 02:26
Default
  #3
Senior Member
 
Paritosh Vasava
Join Date: Oct 2012
Location: Lappeenranta, Finland
Posts: 545
Rep Power: 12
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.
vasava is offline   Reply With Quote

Old   April 29, 2013, 10:48
Default
  #4
Senior Member
 
OJ
Join Date: Apr 2012
Location: United Kindom
Posts: 475
Rep Power: 11
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, 08:17
Default
  #5
New Member
 
viral nagar
Join Date: Jun 2014
Location: surat,gujarat
Posts: 7
Rep Power: 3
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, 05:45
Default
  #6
New Member
 
viral nagar
Join Date: Jun 2014
Location: surat,gujarat
Posts: 7
Rep Power: 3
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, 07:05
Default WARNING: Unassigned interface zone detected for interface
  #7
New Member
 
rahul kumar
Join Date: Jun 2014
Posts: 23
Rep Power: 3
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, 07:15
Default
  #8
Senior Member
 
ghost82's Avatar
 
Daniele
Join Date: Oct 2010
Location: Italy
Posts: 908
Rep Power: 15
ghost82 will become famous soon enough
Post some pictures of your interfaces.
ghost82 is offline   Reply With Quote

Old   September 16, 2014, 00:30
Default geometry attaching
  #9
New Member
 
rahul kumar
Join Date: Jun 2014
Posts: 23
Rep Power: 3
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, 45 views)
R4RAHUL is offline   Reply With Quote

Reply

Thread Tools
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 On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
non-orthogonal faces and incorrect orientation? nennbs OpenFOAM Native Meshers: blockMesh 7 April 17, 2013 05:42
discretizer - gmshToFoam Andyjoe Open Source Meshers: Gmsh, Netgen, CGNS, ... 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
Paraview command not found hardy OpenFOAM Paraview & paraFoam 7 September 18, 2008 04:59
BlockMeshmergePatchPairs hjasak OpenFOAM Native Meshers: blockMesh 11 August 15, 2008 07:36


All times are GMT -4. The time now is 19:48.