Problems with export 2D mesh from ICEM to FLUENT
Hi guys,
I have been trying to export a 2D mesh from ICEM to FLUENT V6 but constantly received the errors message as "FLUENT received fatal signal" and the mesh .msh file could not be opened in the program.. I did not have this problems when using a 3D mesh but this problem always appeared when I want to export a 2D mesh... Would appreciate it very much if you could please advise how I could solve this problem... Thanks a lot! |
2D boundaries...
In 3D, you need shell elements to form the boundary all around your 3D volume elements. In 2D, you need line elements to form the boundary all around your 2D volume elements.
I have found that this is one of the most common mistakes users make, particularly for 2D Hexa. Go back and check your mesh... Turn on all your parts and turn on line elements but turn off shells... You should have line elements around the perimeter and between any two shell parts... If not, then that is your problem. The uncovered faces check should also find these. The fix, if using ICEM CFD Hexa, is to go back and associate edges to curves... When an edge is associated to a curve, line elements form in the part name of the curve... No association, no line elements, no boundaries for fluent... |
Hi,
For fluent 2d simulations, the geometry must be in XY plane. Otherwise you will get error. If you made the geometry in XY plane, then check mesh and quality as Simon said |
Hi Simon and JSM,
Thanks for your suggestions! I did miss that step in my previous attempt... |
Hi,
I have the same problem... and I get "diagnostics: uncovered" around my airfoil (2d) even if I have LINE elements to form the boundary around it. Any idea please? many thanks Alberto |
It may be something else, but it is something you need to fix.
Uncovered just means that you have elements that do not have a proper boundary around them... Every CFD code requires each fluid volume to have a boundary, so it is a critical problem to fix.
For a 2D mesh, it could be shell elements with no other elements next to them, such as no other shell elements in the same PART or no line elements to form the boundary... Or it could be shell elements next to other shell elements in a different part. For instance, some users like to create Prism elements in a different part than the original FLUID. The solver will want some sort of boundary between these "different" fluids, so it will complain. If this is your problem, just right click on your FLUID part and Add to Part... In the selection toolbar, you can select all the 2D elements in the model (it is one of the last options on the right side), or you could just select by part and grab the Prism part from the list... This is my first guess. It may be something else, but it is something. If that is not it, please run the check, create a subset, right click to add a few layers and take a snapshot so we can see what is really going on. |
Thank you Simon,
the problem was due to a rotation of the mesh...I have not understood why actually, but I can handle it in another way, that doesn't lead to a such "error". So thanks anyway... regards Alberto |
Quote:
Thanks a lot! |
@Bollogna
Quote:
Quote:
When you convert from pre-meshing to meshing, it actually extracts the node locations and connectivity for all the surface and volume elements and builds an actual unstructured mesh. This is the kind of mesh needed by most modern solvers (such as Fluent or CFX). |
Thanks for your reply Simon.
Now I've managed to fix that error, but I'm getting a new one when importing my 2d hex mesh into fluent. The error message is the following: Cell centroid is xc 0.00000 yc 0.00000 WARNING: no face with given nodes. Thread 11, cell 6224 Clearing partially read grid Error: Build Grid: Aborted due to ritical error. Error Object: #f How can I fix that? Thanks a lot in advance! |
Not sure, it seems to be saying that an element is missing.
Have you run thru all your mesh checks in ICEM CFD before exporting? Go to Edit mesh and check your mesh. This may be something I could solve if I could look at it, or send it in to ANSYS Tech support. |
After some searching in the forum I tried the check mesh, and it seems to have fixed many stuff (much of it I haven't understood). But now I'm facing a new error when I try to open the mesh in fluent, it says:
Skipping zone (not referenced by grid) I've tried to solve it with no result, and I don't find any useful tip in the forum. Your help will be much appreciated. I'm attaching in this link my icem files in case you wanna have a look. Thanks a lot! https://dl.dropbox.com/u/6986695/PS_2D_12_12.zip |
The "skipping zone" shouldn't have stopped you. It is just an informational thing. You probably had a part (aka Zone in Fluent) that had no elements in it. Fluent saw the name, realized it had no elements in it, and skipped it.
It is only a problem if you expected elements in that zone. I am having a bit of trouble with my winzip. I will re-install and try again later. |
|
bollongo , i'm off for today, here is something you can do, there are curve that represent your fine plate. name those curves "wall" and do the associations again. there are no element on the fine plate even if you see a mesh there. LINE ELEMENTS has to be associated with the WALL CURVES you created. also because of your very dense mesh you have negative volume. give less element so you can track this error, or re-do the blocking, always starts by some few elements see if everything goes good then refine and apply the bunching law...
|
1 Attachment(s)
I found a few issues.
First, I noticed that you had the fluid part set to internal wall instead of fluid. You also had a part for internal wall, which you didn't need. (i just un-associated all those edges). Then I saw that you had some strange index stuff going on... Are you familiar with the index control in hexa? Take a look at "I" between 2 and 4... There are some strangely squished indices. For this model you really only need 5 indices in the I direction, you have 2 extra. To see what I am looking at, try the following steps. Open index control, reduce "I" down to 0:1. This should just show the inlet edge. Then increase the Min index so the range for I is "2:2". This should show the split ahead of your plate... It should show the whole split, but just shows the middle section of it. Then increase again, you see the left side. increase again, you see both sides, but not the middle... Increase again, you see the top and right side... Increase again, you see the outlet... This shows me that you didn't use the proper top down approach. You didn't create your split properly and you have "implied splits". To clean this up... 1) Reset index control 2) Split Block => Extend Split => All Edges (you will see the extra splits revealed) 3) Merge Vertices (turn on option to "propagate merge") select a pair of verts that need to be merged away... 4) Confirm "delete station" (this removes the unnecessary indices, you should see the I index Max decrease to "5") 5) fix any lost projections... (this is why you still had an uncovered face, the tiny edge may not have been properly associated). 6) New premesh, new unstructured mesh, check mesh, output (2D), etc. For check mesh (all defaults), you should only get "single edges" (which are fine), but no other complaints. I was able to read this final mesh into Fluent without any problems... I will attach my "fixed" blocking file and fbc file (along with a tin and prj file), you can easily regenerate the uns and msh from that... Best regards, |
balogna.zip :D funny how you could remember the name...
|
Quote:
Figured he would forgive as long as his mesh is fixed ;) |
Quote:
I'll try your steps 1) to 6) to get more used to Icem. Quote:
Thanks a lot for your help! I'll let you know if I can follow all the steps correctly. |
All steps went fine! I managed to get my mesh right! by the way, where can I learn all this checking options? Is there any good advanced tutorial?
Thanks a lot again! |
It is usually better to split all the way rather than try to split only selected blocks... It keeps things less messy.
You can always merge blocks later if you need to clean it up. For the checking options, there may be a tutorial, but you really just need to look in the help to see what each one does. |
There's only something weird, when I'm connecting curves to edges, inlet and outlet curves seem to be somehow associated. I didn't care for that, but then in fluent I see that there's no inlet boundary, just to outlets! I've tried to fix that with no success... Any suggestions?
|
No idea, it worked properly for me. :confused:
|
Quote:
i think this happens if you do association of multiple edge with multiple curve. You need to UNGROUP the curve then you will be able to associate each one of them |
I've managed to unrelate the curves and reassociate them. I've reassigned BC but in fluent Inlet boundary is still as outlet. I've also tried fixing the mesh again with no results. I can continue working with Simon's mesh, but I'd like to learn how to solve that issue. Anymore thing to try?
Thanks a lot guys! |
What are the issues with your mesh? did you solve them? I assume you are now working with Simon's blocking.
|
Well, I did all the steps Simon told me, and everything went fine untill I loaded the mesh in fluent. The problem is there is no inlet BC, just two outlet BCs. I checked it on Icem and everything was okay. That wasn't happening to Simon's mesh. I can upload the icem files in case you wanna check it out.
https://dl.dropbox.com/u/6986695/PS_12_12.rar |
Post # 10 & 12
I am talking about the blocking issues at post # 10 and 12. Did you solve them or moved with new blocking as suggested by the Simon. Because I just took look on those files (post 12) and worked around half an hour :( and finally found the fault besides the blocking problems as described in detail by Simon. Wanna know the reason :rolleyes:
PS: I have recorded all into one video clip too, where you can see my frustrution :D |
Quote:
There are lot of problems in the attached ICEM project as already mentioned by Simon. But i worked Ab_initio, I still got problem......... In which blocking you have the inlet problem? can you attach that? |
1 Attachment(s)
|
All the problematic files are in the link I posted. I don't know which block was the one causing trouble. I'm sorry for your lost time.
|
1 Attachment(s)
Quote:
Then the blocking issues were solved by Simon's six steps Quote:
Case A: (https://dl.dropbox.com/u/68746918/ballogona.mp4) 1. Started the blocking from scratch that is I did not use the six steps by Simon. Instead I went o create block > 2d planner block 2. Deleted the unwanted geometric entities such as internal curves and points. Also deleted the symmetry curves and recreated them. 3. Made the splits according to geometry. 4. Associated the all edge to appopriate curves and points to vertices. 5. Edge mesh parameters (roughly specified) 6. Pre-mesh and then unstructured mesh . 7. Solver selection and boundary condition specification as usual. 8. Mesh output and read into Fluent 9. Bingo error. No matching of nodes. Zero nodes. Non positive volume 10. repeated again and again..................... every time failure. 11 Finally went to boundary condition panel and deleted boundary conditions for the Fluid and interior. 12. Got the mesh working. :cool: Case B: (https://dl.dropbox.com/u/68746918/final.mp4) 1. Deleted boundary conditions, geometry parts and blocking. 2. recreated the some curves. 3. Initialized new blocking, made splits and associated 4. Edge mesh parameters, pre mesh and conversion to unstructured mesh. 5. solver selection, boundary conditions, and output mesh 6. Read in Fluent. Every thing went fine. PS: Your case had multiple injuries ;) |
Wow! Thanks a lot Far, people like you make CFD less cryptic!
|
Case 3 - same blocking and same geometry
1 Attachment(s)
Here is the case - Minimum changes from original geometry and blocking. (https://dl.dropbox.com/u/68746918/case3.mp4)
Steps: 1. Start ICEM CFD 2. Load first tin and then blocking. 3. edge mesh parameter on the lower symmetry centre edge were set. Just changed scheme to uniform from geometric. 4. Used extend split > all edges. 5. Delete internal curves. Disassociate (remove association) the corresponding edges. 5. recompute pre-mesh, convert to unstructured meshing, boundary conditions (if needed) and output 2d meshing. 6. Read mesh in Fluent. |
2 Attachment(s)
Hello again guys,
I've been trying a different mesh for the same case but I've encountered some trouble with my blocking edges. It seems that when more than 4 edges arrive to a vertex there are some extra edges collapsed into the corners which I cannot erase, in the attached picture the edge count is displayed, and there are some extra numbers in the corners.The desired blocks are also shown in a picture. I've tried to extend split and then merging nodes and erasing extra blocks but it didn't worked, and it messed everything up. How can I avoid that "collapsed" edges? Thanks! |
1 Attachment(s)
I've also checked the faces of each blocks and there are some missing ones, I don't know why. In the picture blocks are pink and faces black.
|
check out this ..........
http://www.youtube.com/watch?v=IuOCRmNyPQM http://www.youtube.com/watch?v=3bAKfxSL6Es |
Thanks Far, but I already did a mesh like the one in the videos. The problem isn't this specific mesh but how to solve this "collapsed" edges for any mesh.
|
attach files so that I can take look of them......
|
Hi, vertex 61 is an example of the issue with the edge. I solved the case with a different blocking, but I'd like to know how to solve that. Thanks.
http://dl.dropbox.com/u/6986695/PS_2D_19_12.zip |
All times are GMT -4. The time now is 01:21. |