Learning Forum

[Aswathy Nair Kondath]

Hello,

We are a fluid dynamics research group, and our simulations require the ICEM-CFD meshing and Ansus Fluent solver utilities. We were using the Ansys Workbench student version for our simulations and are familiar with its environment. We needed the capabilities of the Ansys Workbench Pro version and installed the Ansys Fluids 2023 package in our lab's local machine using the licence entitlement Ansys Academic Multiphysics Campus Solution issued to our university under the instructions from our university's computing services support. However, after installation, we encountered two issues:

(1) We could not find the ICEM-CFD meshing utility, which we learnt after discussing with the Ansys Academic Program Manager that it is now integrated into the meshing tools in Ansys Fluent.

(2) The installed version of Ansys Workbench is missing the "Fluid Flow (Fluent)" component. I am attaching a screenshot of the Workbench window below. We tried the suggestions in the following links but could not install the "Fluid Flow (Fluent)" component.

How to: Fix ANSYS Workbench Missing Tools | John Kaiser Calautit (wordpress.com)

https://forum.ansys.com/forums/topic/missing-analysis-systems-from-toolbox/

 

 

Screenshot of the Ansys Workbench window

 

 

Please help us resolve the issue.

 

We appreciate any help you can provide.

Aswathy

[NickFL]

Yes ICEM has basically be discontinued. It's legacy lives on in ANSYS Multizone meshing and some in Fluent meshing.

As for your other problem with the components not showing up, are you able to run Fluent in stand-alone mode? The typical installation would install it at: C:\Program Files\ANSYS Inc\v231\fluent\ntbin\win64, so if you navigate to this directory and then find the fluent executable, does it run and find the license ok? 

[Aswathy Nair Kondath]

Thank you, NickFL. Yes, it was a licensing issue. We worked with our Computing Support and Ansys Support teams to get it fixed. Thank you for pointing out that it could be a license issue. The problem was that the local machine was not recognizing the license server.