Stats

More Content

Creating a FNMB between a solid blade domain and a fluid domain within a turbo configuration simulation

KBBKBB

Hi,

currently, I want to perform a CFD CHT calculation of a turbo-configuration, where the blade is considered as a solid domain. The mesh of the fluid domain of the turbo configuration (using the row wizard) and the mesh of the solid domain (using HexPress) are already generated. Currently, I am using OMNIS 5.2.

This webinar comes pretty close to what I am trying to achieve, although I do not have such a complex tip geometry and I do not use FIDELITY pointwise:

How to Efficiently Mesh Complex Turbomachinery Blade Tips with High Accuracy | Engineering.com

I was wondering how exactly Mr Teixeira managed to connect the blade solid domain with the fluid domain. 

Within the "connection manager" in the "domain context", the boundaries of the blade, which are part of the fluid domain, cannot be selected to be part of a FNMB. But somehow, a connection between the solid blade and the surrounding fluid was created in the above linked webinar.

I could not find any contact info of Mr Teixeira, but given that he is principal application engineer at cadance, I was hoping somebody could provide me an answer for this issue or his maybe his contact info.

Many thanks

Paul

Parents
  • KBBKBB
    0

    Hi, thanks for the answer.
    I am using Fidelity.
    I know how to use the connection mager for CFD CHT in general.
    My problem is (still) the one I have written in my original post:

    "Within the "connection manager" in the "domain context", the boundaries of the blade, which are part of the fluid domain, cannot be selected to be part of a FNMB."

    THe boundaries of the blade are automatically created while using the turbo wizard.

    Many thanks

    Paul

  • domen
    +1 in reply to KBBKBB

    Hi Paul, it's a known limitation, unfortunately.

    We are going to work on it in the following versions of Fidelity, but as you found out, in 2023.1 we can't use the blade boundaries that are generated by the Wizard/geomTurbo. One workaround is to import the IGG project (exported from Fidelity, for example): the boundaries of the blade are going to be available there.

  • domen
    0 in reply to domen

    Hi again, we are going to fix this in FI 2023.2, if you want to give it a try again.

Reply
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.