|
[Sponsors] |
July 25, 2012, 05:23 |
Turbomode of CFX
|
#1 |
Member
Domenico
Join Date: Sep 2009
Location: Cranfield
Posts: 48
Rep Power: 17 |
Dear all,
I'm trying to post-process in CFX and use the turbomode of CFX. I've got a compressor fan having a certain number of blades and I'm interested to see and compare trends of quantities along the span location averaged along the circumferential domain of each blade passage. By default, the initialization in turbomode take into account the full annulus and the initialization can be done only if the option '360 Case without Periodics' is enabled. Then, I used to define the sub-domains (hub, shroud, blade, inlet, and outlet), referred to only one specific blade passage. However there are no differences against the full annulus solution. In fact, if I try to plot the Turbo chart 'Hub to Shroud' the trend of a quantity (which is averaged along the circumferential direction) along the span is always the same. It seems that the limit of the circumferential location over which the average of the quantity is done is always from 0 to 360 degree, even though the Turboregions are referred to a specific blade passage. Does anyone knows how I can solve this problem instead of creating matlab codes to divide the information between blades? Thank you in advance for your collaboration |
|
July 26, 2012, 08:38 |
|
#2 |
New Member
Ismael
Join Date: Nov 2011
Posts: 13
Rep Power: 14 |
Hello.
Is your geometry a periodic of the fan or the full geometry? 360° I mean. Can you post an Isometric view of your fan? |
|
July 26, 2012, 08:53 |
Turbomode
|
#3 |
Member
Domenico
Join Date: Sep 2009
Location: Cranfield
Posts: 48
Rep Power: 17 |
It is a full annulus. You can see from the picture. The mesh was originally created by means of Turbogrid and automatically for each blade there are the sub-domains defined. Do you have then an idea how to separate the post-processing according to the blade passage?
Thank you in advance for your collaboration |
|
July 26, 2012, 09:02 |
|
#4 |
New Member
Ismael
Join Date: Nov 2011
Posts: 13
Rep Power: 14 |
I usually separate the blade passage when I draw on CAD software.
In the POST, do you try to initialize just the impeller? What error do you get when you try to initialize? Maybe you can try to look the regions that the software is trying to create and then indicate just the Hub, Shroud and the blades,not doing the automatic initialization and specifying as 1 passage only. Did you try something like this? |
|
July 26, 2012, 09:15 |
|
#5 |
Member
Domenico
Join Date: Sep 2009
Location: Cranfield
Posts: 48
Rep Power: 17 |
I tried exactly like that. I took the subdomains referred to one passage only (inlet, hub, shroud, blade and finally the periodics which you must select in the turboregions without having any error). Although you do not have error the solution is the same as the full annulus one. Does it seem right for you?
Thank you for your collaboration |
|
July 26, 2012, 09:26 |
|
#6 |
New Member
Ismael
Join Date: Nov 2011
Posts: 13
Rep Power: 14 |
The solution won't change, it should be the same, the only difference is the way you are plotting it.
So it seems right. Did you create your turbo surface at 0.5 spam without problem? |
|
July 26, 2012, 09:52 |
|
#7 |
Member
Domenico
Join Date: Sep 2009
Location: Cranfield
Posts: 48
Rep Power: 17 |
Yes, I plotted and I was expecting that the turbosurface was referred only to a single passage, but it consider always the full annulus. Is it possible that I cannot split the information according to the blade passage? So far I used to create table where the number of lines was that of the number of blade. Then along the column I calculated a specific quantity referred to each blade passage. In my case I want a trend referred to each passage. This means that I want per each blade a 1D post-processing (where the dimension involved is for example the radial direction), rather than 0D (when for example you do simply an area or mass flow average).
I do not see why it does not work that. I tried even to submit a request to Ansys, but since yesterday they are not replying. Thank you for your time, really! I hope you have understood my point and you have the solution in your hands. Cheers |
|
July 26, 2012, 12:19 |
|
#8 |
New Member
Ismael
Join Date: Nov 2011
Posts: 13
Rep Power: 14 |
'Yes, I plotted and I was expecting that the turbosurface was referred only to a single passage, but it consider always the full annulus. Is it possible that I cannot split the information according to the blade passage?'
You won't be able to split now, you need to do this at the start in the geometry. You can split the geometry,prepare, run, view results. Viewing the results of a periodic you can fill to "complete" the geometry, I think you cannot do the inverse in CFX post, drawing, preparing and running the 360°, then split in the post. To get information of a single blade, as I understood, would be better to split that fan. Like, I think you have 22 blades, couldn't count well. Get your geometry and split in 22 parts, modeling just one blade and run a periodic simulation, then you will be able to plot 1 blade or the fan. I have to say, I didn't understand very well what you want to know, but I think you want to plot the information for one blade, right? Streamlines, direction vectors, velocity, velocity in stn frame. I didn't understand what you mean as 1D and 0D post processing. I work with pumps and I use do what I told you. I hope someone can help your better, I guess I did what I could. |
|
April 26, 2016, 03:26 |
|
#9 | |
Member
ngoc tran bao
Join Date: Jan 2016
Posts: 35
Rep Power: 10 |
Quote:
|
||
April 26, 2016, 03:46 |
|
#10 |
Senior Member
Maxim
Join Date: Aug 2015
Location: Germany
Posts: 415
Rep Power: 13 |
Is your rotation axis the z-axis? I know that TurboGrid needs the z-axis as axis of rotation - maybe Turbo in Post needs that as well.
Turbo Tab can work with full geometries - which is bad since we can evaluate single blades anymore - that's what we also discuss here |
|
April 26, 2016, 04:13 |
|
#11 | |
Member
ngoc tran bao
Join Date: Jan 2016
Posts: 35
Rep Power: 10 |
Quote:
Yes, the rotation axis is z, as shown on this picture. |
||
April 26, 2016, 04:51 |
|
#12 |
Senior Member
Maxim
Join Date: Aug 2015
Location: Germany
Posts: 415
Rep Power: 13 |
sorry I can't help you here any further since I use a "turbo rotation" in PRE and therefore I don't use a real 360° model.
I would try the bruteforce method I no one else can help you: strip down your simulation to only the important parts to make sure that nothing else interferes. Maybe even set up a simplified case. And/or check out the tutorials. Maybe you forgot a simple thing... |
|
May 7, 2020, 12:51 |
|
#13 | |
New Member
Luca
Join Date: Jun 2017
Location: Italy
Posts: 5
Rep Power: 9 |
Quote:
I'm post-processing full annulus results of an axial rotor in CFD-Post, and the inlet conditions are not uniform. Therefore, for each rotor passage, I want to export circumferentially-averaged spanwise profiles of inlet and outlet variables, in order to obtain for example the spanwise distribution of pressure ratio of one passage. In the Turbo menu, I initialize the domain considering the mesh regions of one passage, and I set a Turbo Chart in order to create the area average spanwise profile of a variable (e.g. Total Pressure in Stn Frame ACA on Hub to Shroud Line). However, for different passages, the exported spanwise profiles are always the same, so I think that CFD-Post is still averaging over the 360° and not over the domain that I specified. Did you manage to find a workaround? Thank you! |
||
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CFX Treatment of Laminar and Turbulent Flows | Jade M | CFX | 18 | September 15, 2022 07:08 |
High Resolution (CFX) vs 2nd Order Upwind (Fluent) | gravis | ANSYS | 3 | March 24, 2011 02:43 |
CFX pressure in Simulations problem | nasdak | CFX | 1 | April 14, 2010 13:22 |
PhD using CFX | Rui | CFX | 9 | May 28, 2007 05:59 |
FSI using CFX and ANSYS | Bi Chang | CFX | 2 | May 10, 2005 04:47 |