-
-
July 27, 2021 at 10:10 amRajasSubscriber
Dear all,
I have been trying to mesh a complex CAD geometry in ANSYS Workbench Fluent, but could not succeed due to some errors. I used an additive manufacturing software (uses Open Cascade kernel) to generate the geometry, imported in .STEP format and performed all the repair functions in SpaceClaim before using ANSYS Meshing. I also have access to Autodesk Inventor, but I am not sure if I can perform any repairs therein.
I have attached images of the error and my geometry below. I heartily appreciate anyone's help in performing the repairs or finding a way out.
Thank you in advance.
Error - "Overflow or underflow in the arithmetic operation"
July 27, 2021 at 11:20 amKarthik RemellaAdministratorHello Are you able to load the geometry in SpaceClaim? If so, right-click on the part and perform the check geometry operation. What does it show?
Also, try resetting your Meshing instance and see if this clears out the message.
Karthik
July 28, 2021 at 7:54 pmRajasSubscriberHi Karthik Yes, I am using SpaceClaim to load and repair the geometry. I have made some modifications to my geometry (Fig.1). I have performed the Check Geometry operation and there were no problems shown. I have also checked for other repair options (Stitch, Gaps, Extra Edges, etc) but everything seems well and no faults were found. I think I'm missing some subtle details.
Could you please elaborate more on the meshing instance, do you mean changing the size of elements?
I appreciate your help in all regards. Thank you!
Rajas
Fig. 1:
July 29, 2021 at 10:33 amRobForum ModeratorHow many volumes have you got? The tree suggests you have one but the display is colouring the helical tube suggesting there are more.
August 2, 2021 at 3:12 pmRajasSubscriberHi Rob I initially had multiple faces (I believe) which on stitching formed a single volume. Yet the coloring is different. Apologies, I am using SpaceClaim for the first time and I am unaware of the significance of coloring.
However, I tried building a simpler geometry (Fig.1) and importing it with different import options (Fig.2) in Design Modeler. Default meshing is now possible (Fig.3). I'm not sure if this was the only cause for the meshing issue.
Nevertheless, the next big hurdle is to eliminate the extra edges causing the faces to separate. I assume this could cause problems with meshing and CFD analysis later.
I will be grateful to receive any guidance on the same, perhaps signposting to a similar thread? Thanks in advance.
Fig. 1: Single flow path geometry
Figure 2: Import options for Design Modeler
Fig. 3: Meshed geometry
August 3, 2021 at 1:33 pmRobForum ModeratorI wouldn't worry about the extra edges, they shouldn't cause any problems for the tet mesher. I would be looking at curvature size functions and the growth rates plus inflation on the tube: the mesh above isn't good.
Viewing 5 reply threads- The topic ‘Meshing issues with imported CAD geometries for CFD Analysis’ is closed to new replies.
Ansys Innovation SpaceTrending discussions- Non-Intersected faces found for matching interface periodic-walls
- Unburnt Hydrocarbons contour in ANSYS FORTE for sector mesh
- Help: About the expression of turbulent viscosity in Realizable k-e model
- Script error Code: 800a000d
- Cyclone (Stairmand) simulation using RSM
- Fluent fails with Intel MPI protocol on 2 nodes
- error udf
- Diesel with Ammonia/Hydrogen blend combustion
- Mass Conservation Issue in Methane Pyrolysis Shock Tube Simulation
- Script Error
Top Contributors-
1241
-
543
-
523
-
225
-
209
Top Rated Tags© 2024 Copyright ANSYS, Inc. All rights reserved.
Ansys does not support the usage of unauthorized Ansys software. Please visit www.ansys.com to obtain an official distribution.
-
The Ansys Learning Forum is a public forum. You are prohibited from providing (i) information that is confidential to You, your employer, or any third party, (ii) Personal Data or individually identifiable health information, (iii) any information that is U.S. Government Classified, Controlled Unclassified Information, International Traffic in Arms Regulators (ITAR) or Export Administration Regulators (EAR) controlled or otherwise have been determined by the United States Government or by a foreign government to require protection against unauthorized disclosure for reasons of national security, or (iv) topics or information restricted by the People's Republic of China data protection and privacy laws.