[samolcue]

I want to solve the following problem, how affects an airfoil the attachment of one cylinder with blades that redirects the airflow toward the airfoil.

First, I'm trying to solve it as a 2D problem but I'm having some problems when I have to put the "Boundary Conditions".

How can I impose that the cylinder with blades can move because of the airflow and this affect the airfoil?

This is an image of what I'm trying to explain:



If anyone can explain me I will be so grateful.

[Far]

How can I impose that the cylinder with blae.des can move because of the airflow and this affect the airfoil?

This cannot be done. However you can adopt the approach of turbomachinery, where you simulate the case for different condition i.e. specifying the inlet velocity, rpm of blade disk and check the results. Got it? I can tell you how to set interfaces for the both domains.

[samolcue]

Originally Posted by Far

This cannot be done. However you can adopt the approach of turbomachinery, where you simulate the case for different condition i.e. specifying the inlet velocity, rpm of blade disk and check the results. Got it? I can tell you how to set interfaces for the both domains.

First of all, thanks for you reply.

When you say that it cannot be done, do you mean in GAMBIT-FLUENT or in all kind of CFD software?

In that case if you can explain me how to implement the two different conditions and I will make some calculations...

Is necesary to make a dynamic mesh in order to implement that?

[-mAx-]

what about sliding mesh with rotor-stator?
you can draw a circle around your impeller, split your domain with this circle.
Then you disconnect the disk (with impeller) from domain, assign interfaces on both fluid domains.
Then in Fluent set up moving mesh with rigid body motion (rotation) and for sure you can describe rotation from torque with a udf

[Far]

How can I impose that the cylinder with blades can move because of the airflow and this affect the airfoil?

When you say that it cannot be done, do you mean in GAMBIT-FLUENT or in all kind of CFD software?

It cannot be done in all softwares that you just give inlet velocity and it rotates the disk or blades. You have to separately specify the inlet velocity and RPM and that should be based on some preliminary calculations for rough idea.

Another important point is that bladed disk center should be placed at origin or otherwise you will have to specify the offset in the solver. So better idea is to put the disk center at origin.

what about sliding mesh with rotor-stator?
you can draw a circle around your impeller, split your domain with this circle.
Then you disconnect the disk (with impeller) from domain, assign interfaces on both fluid domains.

Thats the method and -mAx- described it very nicely.

Then in Fluent set up moving mesh with rigid body motion (rotation) and for sure you can describe rotation from torque with a udf

But how we will define the torque? Or in other words without specifying the RPM how can we determine the torque?

[-mAx-]

Originally Posted by Far

But how we will define the torque? Or in other words without specifying the RPM how can we determine the torque?

There is a 6DOF udf : pressure force/torque is computed on body and with twice integration you get the displacement/angle for your motion.

[samolcue]

Originally Posted by -mAx-

what about sliding mesh with rotor-stator?
you can draw a circle around your impeller, split your domain with this circle.
Then you disconnect the disk (with impeller) from domain, assign interfaces on both fluid domains.
Then in Fluent set up moving mesh with rigid body motion (rotation) and for sure you can describe rotation from torque with a udf

Ok, I'm gonna try doing this the problem is that I don't have much knowdledge of GAMBIT and I don't know if I'm doing any error. So is possible that when I have it done I attached it and you check things are done as you said?

Originally Posted by Far

Another important point is that bladed disk center should be placed at origin or otherwise you will have to specify the offset in the solver. So better idea is to put the disk center at origin.

This is not a problem, I have it placed at the origin.

Originally Posted by -mAx-

There is a 6DOF udf : pressure force/torque is computed on body and with twice integration you get the displacement/angle for your motion.

So I understand that I can solve this problem (as I say at the beginning) without impossing a RPM speed to the disc. Is that correct?

Thanks all 2 of you

[-mAx-]

Originally Posted by samolcue

Ok, I'm gonna try doing this the problem is that I don't have much knowdledge of GAMBIT and I don't know if I'm doing any error. So is possible that when I have it done I attached it and you check things are done as you said?

Originally Posted by samolcue

So I understand that I can solve this problem (as I say at the beginning) without impossing a RPM speed to the disc. Is that correct?

I don't have Fluent anymore
I would advice you to test the mdm first with a simple rotor-stator, and with a fixed rpm.
Then try the 6dof, and finally introduce your airfoil

[samolcue]

Originally Posted by -mAx-

what about sliding mesh with rotor-stator?
you can draw a circle around your impeller, split your domain with this circle.
Then you disconnect the disk (with impeller) from domain, assign interfaces on both fluid domains.
Then in Fluent set up moving mesh with rigid body motion (rotation) and for sure you can describe rotation from torque with a udf

Max, I thing that I have done all that you said to me correctly, but I don't know if here I could made some error because when I go to Fluent I don't have the Mesh Interfaces options.

Please correct me if I have done something wrong

1.Import impeler geometry (face)
2.Domain Geometry(face)
3.Circle around impeler.(face)
4.Split Domain face with circle
5.Substract Circle face with impeller.
6.Mesh
7.BC
8.Define 2 cell zones as fluids

I think that I'm doing it correctly but I just wanna be sure, because I don't know if when you said "Then you disconnect the disk (with impeller) from domain" it is well done with my procedure.

Thanks

[-mAx-]

important is that your rotor and stator domain aren't connected.
For that try to move (not copy!) the rotor domain with any vector.
If you are able to do it, then both domains are disconnected
If not, then copy the rotor domain with any vector, delete the original rotor domain, and move back(not copy) the rotor domain.
Take the advantage from this "move" procedure to pick and define the interfaces (else it is more obscur, since they are superposed)