find choking range in orifice
Hi all
I'm trying to simulate flow in orifice plate. How can i find when orifice will be choked? for capture choking steady state solution is better or transient solution? Best regards 
Not too much experience with this, but from what I read, a choked flow is a flow where, for fixed inlet pressure, any decrease in outlet pressure will not result in increase in mass flow rate. Now, this should involve series of simulations to find this minimum outlet pressure.
I would start with steady compressible flow (ideal gas density, since choked flow velocities reach Mach 1 region) with relatively coarse mesh to simulate the initial physics to get it right. Once you get an approaximate outlet pressure beyond which any decrease will not result in significant increase in mass flow, you may want use a proper refined mesh and then choose pressures close to this value to get even better estimation for the threshold pressure. In case if you find the solution not converging to your satisfaction, you may want to try transient. But it would be cheaper to use steady state solution to arrive at approaximate range of choking outlet pressure, before switching to transient. Regards OJ 
You should be able to estimate the choking pressure using simple compressible flow analytical equations.

Thank you for your replies dear oj.bulmer and ghorrocks
i'm trying to investigate some parameters such as thickness of orifice(or length of orifice), multi holes orifice, multi stage orifice, and simple compressible flow analytical equations are not usefull. What is the accurate or valid boundary condition? i use inlet pressure and outlet pressure to compare massflow rate at each boundary but overflow errors accure, when i use massflow rate in inlet boundary and pressure outlet convergence reach difficultly but maximum mach number is 4.5. inlet pressure is 150 bar with massflow rate 5.71 kg/sec and outlet pressure is 7 bar. i trying to simulate it as transient method but overflow errors accures. Best regards. 
The best boundary condition for this type of simulation is a total pressure inlet and a pressure outlet. But convergence of these type of simulations is tricky, use a bit of local tiem scale factor to start off and after it has converged a little switch to physical time step.

Glenn,
I have a fundamental query about local timescales. I learn that for the local timescale, it is the number of cells that intersect a typical flow path from the inlet to the outlet that is significant. For subsonic flow speeds, pressure information propagates upstream from the outlet to the inlet. The CFX manual only warns about using the local timestep because you need to ensure you have run for enough iterations to reach a steady solution and for all the boundary information to have propagated throughout the mesh. A local timestep of 5 with 80 iterations implies that the maximum distance any information could have travelled across the mesh is 5*80 = 400 cells. If this is the case, and if we are working with a mesh of, say 3 million, would local timescales be any economical? OJ. 
Yes, I frequently use local time scale for tricky to converge simulations, especially transonic ones. Your understanding of local time scale does not seem correct  local time scale simply uses a time scale set at each element (Courant number I suspect) and that means high courant number elements get a small time step to aid convergence and low courant number elements get a bigger time step to speed convergence, up until all elements are running with a similar courant number. There is nothing special about solutions wandering upstream or downstream or anything like that.
The implications of this variable time step is that some parts of the flow may have only advanced a very small amount of time, but the rest of the flow has advanced a lot. So things which often take a while to converge in physical time (eg heat balance) will be inaccurate. To fix this you run a few time steps of physical time stepping at the end to make sure everything has run a minimum amount of physical time. 
* CFX is a coupled solver and does not use SIMPLE. Your analysis is based around a SIMPLE solver.
* CFX uses a multigrid solver which achieves rapid convergance (most of the time :) ) even on fine grids * CFX is pretty robust against skewed cells. So your analysis is not very relevant to CFX. 
Agreed, I understand it is a coupled, and hence rapid (relatively smaller iterations) solver as compared to segregated solvers. But I was just getting my head around the implementation of local timescale factor in CFX, and not trying to generalize the CFX's solving algorithms. Recall that CFX did have a default SIMPLEC based solver previously. Is it fair to say that though they changed it to multigrid coupled solver later, they retained the implementation of local timescale factor (perhaps as illustrated in the paper about SIMPLE algorithm)?
Also, I agree it handles skewed cells pretty well compared to FLUENT, but these have very high ap value and hence a reasonable value of E is yet not enough to advance them in time as we'd wish, again in the context of local timescales. We still assemble the implicitly coupled linear equations to solve, but then, the pace of solution in its entirety, is limited by these slow fine regions. Especially if you have relatively nonuniform mesh, switching to physical timescale earlier than appropriate time will still pour convergence difficulties :) 
CFX3 and 4 used SIMPLEC as a default solver. CFX5 (which is the first in the current series of solvers) used the fundamental solver technology developed in TASCFlow (ie coupled solver). CFX has had multigrid linear solvers for all releases I can recall. SIMPLE, SIMPLEC or any of its derivatives is not an available option in any recent CFX releases.

I use local time scale and overflow error doesn't appear. convergence is too difficult. by local time scales in order 0.01 there is a notification about high mach number about 400 with small time scale this notification does not appear. after convergence i probe massflow rate at inlet and outlet boundary...these are equal...but how can i understand flow is choked or not?
I would like to study the effect of thickness and bore size of orifice on choking range of it with constant mass flow and pressure at inlet boundary.... Best regards. 
Local time scale factors of 5 are the range you normally use. If you are using 0.01 with Mach 400 somehwere then soemthing is seriously wrong with your setup.
If you have a transonic simulation then you will need very good mesh quality. Can you post a picture of your mesh? Even better, put the residuals in the results file and use them to indentify where in the simulation the high residuals occur. That shows you what area you need to improve  by meshing the area better. 
1 Attachment(s)
Thank you for your attention dear Glenn
attached file is a picture of mesh, there is about 462235 element. There is a pipe with 82.804 mm diameter and orifice with 17.14 mm bore diameter. thickness of orifice is about 12.7 mm. Upstream pressure is 150 bar and down stream pressure is 7 bar. mass flow rate of CH4 is 5.712 kg\s. setup of this problem seems to be simple, have you any comment about it? Best regards. 
I presume this simulation is axisymmetric? You should model a thin wedge in that case. Shame CFX does not have a true 2D model like Fluent, that would be very useful for this case.
You may need to extend the downstream boundary further downstream at this Mach/Re number. The separation is going to be huge and you probably have back flow where you currently have it. 
With better mesh quality i can finally improve rate of convergence. Know my basic question is: How can i find flow is choked of don't? if not how can i find choking range to study effect fo other parameter on choking?
Best regards. 
Increase the pressure ratio. If the flow rate does not change it is choked.

Yes it is axisymmetric , but for include turbulence effect i simulate whole 3 D of model. the max. of mach number is 4.58. i haven't any data about experimental investigation and don't know is this mach number is physically correct or not.

Quote:

Read what I wrote earlier:
Quote:
Quote:
OJ 
All times are GMT 4. The time now is 21:53. 