|
[Sponsors] |
July 21, 2017, 13:46 |
Overset mesh issiue
|
#1 |
New Member
Antonio Ercoli
Join Date: Jul 2017
Posts: 2
Rep Power: 0 |
Hi guys , I'm a new member here . I have already seen some thread about the overset mesh, however, I'm not able to solve my problem. I'll explain better. I have to simulate wipers' motion over the windscreen and to do this I used an overset mesh that contains the wipers. The problem is that even if I have made a similar mesh for the background (windscreen) and for the overset boundary, it gives me back the error: "Found 64799 Inactive Faces in Region "Domain". This might be due to too fine or too coarse mesh. Please check cells with Overset Error Status: 30".
There is anyone that can explain to me what problem could it be? Thank you very much for the help! |
|
July 22, 2017, 07:51 |
|
#2 |
Senior Member
|
This is may be due to boundary of your overset region is close to boundary of background mesh. Try not to move your overset mesh very close to boundary of background mesh. Increase the boundary of background mesh.
Sent from my Redmi Note 3 using CFD Online Forum mobile app |
|
July 23, 2017, 14:15 |
|
#3 | |
New Member
Antonio Ercoli
Join Date: Jul 2017
Posts: 2
Rep Power: 0 |
Thank you for the answer, but I don't understand what do you mean with
Quote:
1. in the first one I have used an overset that contains only the blade of the wiper; 2. in the second one I have used an overset that contains all the wiper starting from the hinge. I have set the "Morphing Specification" for the overset to "Displacement", while I impose a "Constraint" for the sliding part of the overset that slides over the windscreen. Using as "Overset topology" the "Direction" option, none of them was initialized correctly. So I have used an "Automatic" topology option and for the first case, it worked, but not for the second. Do you have any idea of what problem could it be? I have added some photos to allow to understand better the problem. Thank you very much for the help! [IMG] https://drive.google.com/open?id=0B2...lg4REdYNjNRYkU [/IMG] [IMG] https://drive.google.com/open?id=0B2...lNVVVhib2o2S2s [/IMG] [IMG] https://drive.google.com/open?id=0B2...GZHNnpXczZyd0U [/IMG] |
||
July 25, 2017, 15:46 |
|
#4 |
Senior Member
|
Sorry... I did not go such deep into overset mesh.... Increasing boundary means boundary of overset mesh and boundary of background mesh should not be very close. They say that there should be atleast 3 cells between these.
Sent from my Redmi Note 3 using CFD Online Forum mobile app |
|
Tags |
overset, overset issiue, overset mesh, overset problem |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
decomposePar problem: Cell 0contains face labels out of range | vaina74 | OpenFOAM Pre-Processing | 37 | July 20, 2020 06:38 |
Overset Mesh error : no startcell found ! | Cris ZC | STAR-CCM+ | 4 | September 9, 2019 11:43 |
Is overset mesh required? | ahildershavn@yahoo.no | OpenFOAM Running, Solving & CFD | 2 | August 4, 2017 04:23 |
[mesh manipulation] Importing Multiple Meshes | thomasnwalshiii | OpenFOAM Meshing & Mesh Conversion | 18 | December 19, 2015 19:57 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 22:11 |