Error in creating a .msh file
 

Hi guys,

I have been strugling in creating a .msh file with ANSYS Meshing - a task that shouldn't be too arduous. I'm running Workbench environment R16.2 on Win7 and I have created quite many .msh files for my current project using more or less similar cases as this troublesome case. I have only slightly changed the geometry for this case and most of the determiations for mesh size, methods etc. are identical to the previous cases that were succesfull.

Additionally, I have checked that topology is shared well (green tick in DM ShareTopology tool). There are also no overlapping named selections present and I haven't found any overlapping volumes that could mess things up (this should become evident with the ShareTopology tool).

I'm grinding my teeth here trying to figure out what could possibly have gone wrong but I haven't found any mistakes thus far. Has any of my fellow CFD-onliners encountered anything similar to this before?


-d

post some images that might be useful for us to understand

what error are you getting?

Thanks for your replies!

@nuj: Although I fully understand the interest for visualization, I'm hesitant to give you pics of the case because of the sensitive nature of the case in our company.

Kapi: ”The mesh file exporter failed during translation. Please send your data to your support provider.” Funny thing was that Meshing could export any other form (including .meshdat), which was stunning in some sense.

I think I got through the wall today as I tried to narrow down possible causes for errors. I tried to export only part of the complete mesh by systematically excluding one volume at the time, and by doing this I found a not-so-perfect cell zone. This cell zone had one (1) cell, which was extremely poor in orthogonal quality, which seemed to forbid me from exporting the mesh. This was surpising because I was using the very same definition succesfully before in a similar case. So I enhanced the cell zone and got forward with work.

That was a rookie mistake if I ever saw one! One should always consider the quality aspects if something seems to be amiss. Usually I encounter this kind of problems in Fluent but it seems that low quality can be a nuisance even with exporting the mesh itself. Hopefully someone learns something from this :)