[ghorrocks]

1) Yes, the sliding interface is transient rotor stator.
2, 3) 1 and 2 are moving mesh domains (but stationary frame of reference). 3 is a stationary frame of reference with no moving mesh.
4) No, do not select any solid motion options. Use moving mesh on a solid domain. Do not use a rigid body model.
5) 1 and 2 have mesh deformation on.
6) interface 1 to 2 is stationary I think, if that does not work then TRS. 2 to 3 is TRS.

[Martin_Sz]

I have another question
Where do I finf frame of reference option ?
Best regards

[ghorrocks]

Frame of reference is where you choose either stationary or rotating. The default is stationary so leave it at the default for all domains.

[Martin_Sz]

Hello Glenn,
So I make simulation with idea which You wrote on the lasts posts and I have another problem.
On the solver only six steps go on and on the seventh error jump in with information
cNWDIST
At least one highly skewed element has been detected on a wall boundary, leading to unreliable near-wall distance calculation for the turbulent wall functions. The solver will continue to execute, but convergence and/or accuracy may be affected. Please consider improving the mesh quality. the coordinates of the element face are...
So what can I do at that moment to fix this error ??
Best regards

[ghorrocks]

This tells me you have got the mesh motion wrong.

Re-run the simulation saving a results file on each time step which includes the mesh. Then have a look at the time step before it crashes at the location it specifies. If you cannot work out what the problem is post an image of it on the forum.

[Martin_Sz]

I increase mesh quality and simulation goes on to the 14th step.
and crashes with element volume error.
The strangest thing is that. On the 14th step and other steps before I haven't got heat transfer on the tube (on moving area of the tube).
When I define moving interface on domain 2, i need to define wall velocity ??
Best regards

[ghorrocks]

The error has nothing to do with mesh quality. Have you done what I recommend in my last post?

The error is most probably due to the mesh motion settings you are using. You need to define a displacement function (versus time) and apply that to all the boundaries of the moving domain. If you miss a boundary you can get the error you got - and that includes interface boundaries so I bet you missed one of them.

[Martin_Sz]

So on the attachments I'm sending You what i define on interfaces of domains
Best regards

[ghorrocks]

I cannot tell much about what is happening from the screen dumps. Please your CCL.

But even more important is the post I put up #25 about how to debug this. It should allow you to identify exactly what the problem is.

[Martin_Sz]

can You verify my defined interfaces which I send on the last post (attachments )
Best regards

[ghorrocks]

I said:

I cannot tell much about what is happening from the screen dumps.

The next sentence meant to say: Please attach your CCL.

But even better: if you do the images I said in post #25 I think we will be able to identify the problem straight away.

[Martin_Sz]

I'm sending a ccl of the simulation
Best regards

[Martin_Sz]

I change mesh deformation to initial boudaries on subdomain option
Then 13 steps go on and on the 14th pop up an error (attachment)
Best regards

[ghorrocks]

As I thought - you have not defined the mesh motion parameters on many boundary surfaces on mesh movement domains.

Boundaries which need it are:
kostka subdom Side 2
subdomena Default

Also the Walek domain (which appears to be your solid) looks like it has no mesh deformation. You need to use mesh deformation on this domain as well.

[Martin_Sz]

Hello Glenn,
Thanks for reply
Where can I change on solid domain mesh deformation ??
I dont see this option on solid domain (attachment)
Best regards

[ghorrocks]

What version of CFX are you using?

[Martin_Sz]

v15
And I have another question.
On Your schematic which domain is moving 1 or 2 ??

[ghorrocks]

1 and 2 are stationary frame of reference, moving mesh domains.

OK, good. V15 is the only version which supports motion in solid domains. I am pretty sure you can do moving mesh on solid domains. You might need to edit the CCL to do this, rather than doing it in CFX-Pre. Copy the format used in your moving mesh fluid domain.

[Martin_Sz]

So for the first time solution goes on.
And I have interesting results.
Interface between walek and subdomain go on the direction which I defined in mesh motion but solid domain on the end of simulation is on the start position. Only interfaces walek-subdomena with empty area inside goes on.
I dont know what to define mesh deformation on solid. ccl copy paste from fluid domain doesnt work. What can I do ??
Best regards

[ghorrocks]

Actually, you might need to use the solid motion options for the solid domain. Have you tried that?