-
-
June 30, 2020 at 3:49 pm
dk89
SubscriberHi all,
I have successfully validated the air flow field around a compressor rotor blade. My computational domain consists of an inlet duct, the rotor domain (hub, blade, and shroud) and an outlet duct. There are two interfaces between the inlet duct-rotor domain and rotor domain-outlet duct. I use the frozen rotor approach for the two interfaces. I inject some inert particles using the DPM. Most particles are tracked, but after some DPM iterations I get the message 'Warning: couldn't find neighbor across sliding interface 12 type 24, reflecting'. The sliding interface 12 corresponds to one side of the interface between the inlet duct and rotor domain. Moreover, I don't specify a DPM boundary condition in this interface since it is not a wall. Could you please help me with that? Thank you for your time.
-
July 2, 2020 at 10:39 pm
ai0013
SubscriberI think you have set up the "reflect" boundary condition for your interface if that's the case. Shouldn't it be "interior"? Try looking at the DPM bcs at your interface 12, and see if that Is enabled. If you want to specify other DPM bc's than the default ones, then you have to use UDF for that.
-
July 3, 2020 at 8:07 am
dk89
SubscriberHi,
Thank you for your answer. I have not defined a DPM boundary condition at the interface 12 because it is not a wall. You can see the interface 12 in the attached image. The side with the ID 12 is one of the two sides of the frozen rotor interface (inlet duct-rotor blade domain). The R1-S2 interface (rotor blade domain-outlet duct) is a similar frozen rotor interface, but I didn't get any warning for this interface during the DPM tracking.
Regards
-
July 3, 2020 at 8:33 am
Rob
Ansys EmployeeAre you losing many particles?
-
July 3, 2020 at 9:02 am
dk89
SubscriberHi,
I track 350 particles totally (I know it's a small number), 348 of them escape, whereas two of them are incomplete. Thank you.
-
July 3, 2020 at 9:27 am
Rob
Ansys EmployeeThen don't worry about it. It means a couple of streams have got confused at the interface. This usually means they've hit a node at an odd angle and potentially then tried to enter two cells at once.
-
- You must be logged in to reply to this topic.

Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.

Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.

Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- Suppress Fluent to open with GUI while performing in journal file
- Floating point exception in Fluent
- What are the differences between CFX and Fluent?
- Heat transfer coefficient
- Getting graph and tabular data from result in workbench mechanical
- The solver failed with a non-zero exit code of : 2
- Difference between K-epsilon and K-omega Turbulence Model
- Time Step Size and Courant Number
- Mesh Interfaces in ANSYS FLUENT
- error in cfd post
-
3694
-
2564
-
1765
-
1234
-
590
© 2023 Copyright ANSYS, Inc. All rights reserved.