Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - william

Pages: 1 ... 5 6 [7] 8 9 ... 11
91
Using a Beta functionality of ANSYS CFX, it is possible to set up a Euler-Euler 2-phase flow simulation with additional particles that will be tracked
in one of the 2 Euler phases only (here in the water phase). Use the following procedure:

1. Set the expert parameter "pt multiphase = t" to enable the support for Euler-Euler 2-phase flow setups with particle tracking
2. Set the expert parameter "pt multiphase min volfrc = 0.5" to define the limit in the Euler-phase volume fraction, for which the tracking
of particles will be stopped. As a result, tracking particles will be stopped whenever they reach areas with volume fraction of water being
smaller than 50% (i.e. when the particles are leaving the water jet).
3. Set up the 2-phase Euler flow plus particles tracking as usual in CFX-Pre, write out the DEF file.
4. In the CCL of the DEF file, delete or comment out the the lines that are defining the interaction of particles with the air phase, for example:

# FLUID PAIR: Air at 25 C | Sand Fully Coupled
# Particle Coupling = Fully Coupled
# SURFACE TENSION MODEL:
# Option = None
# END
# END

92
The gradient of temperature is not a standard variable but it can be represented by a vector Additional Variable (AV) which is created in CFX-Pre. The components of the AV are defined as the components of the gradient, as shown in the excerpt of CCL below:

LIBRARY:
ADDITIONAL VARIABLE: GradT
Option = Definition
Tensor Type = VECTOR
Units = [K m^-1 ]
Variable Type = Unspecified
END
END
FLOW:
DOMAIN: MyDomain
FLUID MODELS:
ADDITIONAL VARIABLE: GradT
Option = Vector Algebraic Equation
Vector xValue = Temperature.Gradient X
Vector yValue = Temperature.Gradient Y
Vector zValue = Temperature.Gradient Z
END
END
END
END

93
Change the Domain Interface to use a GGI connection rather than Automatic or 1-to-1. Also running the CFX Solver in double precision can sometimes help.

94
The CFX 11.0 FORTRAN code CTS.F that simulates conducting thin surfaces will not run in parallel
The workaround is to model the thin conducting surfaces in CFX 12 Beta using the alternate interface model.
Fluid to FLuid interfaces with conservative interface flux can now be made to behave like a thin amount of material (user-specified thickness and material = properties)

95
Turn on beta features in CFX-Pre. Typically people turn radiation off in a porous domain since the photons wouldn't see the domain's porosity. But if there is a fluid domain next to the porous domain, the standard interface boundary condition of "Conservative Interface Flux" would cause all the photons to be lost across the interface. In CFX-11 and CFX-12 the user must turn on beta features in CFX-Pre to be able to set the interface boundary to be opaque to radiation. Even with beta features turned on, CFX-Pre does not automatically detect the presence of a non radiating fluid/porous domain next to a radiating fluid/porous domain. The user must manually set the interface boundary to be opaque to radiation.

Beta features can be turned on in CFX-Pre by selecting the menu Edit->Options->General.
Enable beta features and make sure that constant domain physics is turned off and automatic interfaces is turned on. In version 12 you may also have to turn on "show interface boundaries in outline tree" to be able to select them.

96
Set the expert parameter 'export property tables to file' to t.

At the end of the run, the solver will write the property data for a number of variables (density, specific enthalpy, specific entropy) to a set of csv files (comma delimited excel file) in the run directory.

The data are presented as (X, Y, Z, Property) and can be imported into CFD-Post using File/Import for display.

X is normally the normalized temperature for the table: (T - Tmin)/(Tmax - Tmin), Y the normalized pressure (P - Pmin)/(Pmax - Pmin) and Z the normalized property and the last column is the absolute value of the property itself.

If the table is set up with 100 points, there will be 100^2 or 10,000 entries in the table.

97
To avoid the problem choose names for the fluids which are not the same as the names of the cell zones.

98
Turbulent Prandtl Number for Enthalpy:

The turbulent Prandtl number for enthalpy transport can be controlled by means of the TURBULENT FLUX CLOSURE singleton located under HEAT TRANSFER MODEL:
FLOW:

DOMAIN:

FLUID MODELS:
HEAT TRANSFER MODEL:
Option =
TURBULENT FLUX CLOSURE:
Option = Eddy Diffusivity
Turbulent Prandtl Number = <real> # default=0.9
END
END

END

END

END

The value specified here also applies to component mass fractions, unless overridden as described below.

99
CFX / Re: How do I model a shell and tube heat exchanger in CFX?
« on: May 11, 2012, 09:32:31 PM »
The most efficient method is not to resolve the pipe thickness with the mesh. Instead, create fluid domains for the regions inside and outside the piping - with no gap in between the two. Now create a fluid-fluid domain interfaces to connect the two domains. When creating the domain interface, on the Additional Models tab panel set the Mass and Momentum option to No Slip Wall, set the Heat Transfer option to Conservative Interface Flux and use the Thin Material option providing a material and thickness.
Both fluid domains will see the interface as a thin wall. A 1D conduction assumption is used to model heat transfer through the wall (no in-plane conduction) using the thickness provided. The thermal conductivity and specific heat capacity is picked up from the material properties of the specified material.

100
CFX / Re: How to activate thermal heat fluxes in CFX?
« on: May 11, 2012, 09:29:19 PM »
This is done by editing the CCL. The following options are available for the heat transfer model:

constant turbulent heat fluxes
FLOW:
DOMAIN: Domain 1
FLUID MODELS:
HEAT TRANSFER MODEL:
Option = Thermal Energy
TURBULENT FLUX CLOSURE:
Option = User Defined
uh = 1. [m^3 s^-3]
vh = 2. [m^3 s^-3]
wh = 3. [m^3 s^-3]
END
END
END
END
END

Transport equation for turbulent heat fluxes:
FLOW:
DOMAIN: Domain 1
FLUID MODELS:
HEAT TRANSFER MODEL:
Option = Thermal Energy
TURBULENT FLUX CLOSURE:
Option = Transport Equation
END
END
END
END
END

No boundary values can be set. Inlet values are by default at zero.

101
Go to the Report -> Volume integral -> sum -> Discrete Phase Model, then calculate the sum for:

DPM mass source
DPM enthalpy source

the DPM mass source sum should be algebraically equal to the mass imbalance in the Report->flux panel
the DPM enthalpy source sum should be algebraically equal to the energy imbalance in the Report->flux panel

Of course, this happens at convergence. For large combustion problems, this energy balance can take longer to achieve and is a better indication of convergence than only relying on residuals.

102
Fluent / Re: How to enable Pressure work in Fluent
« on: May 11, 2012, 10:57:36 AM »
When Viscous heating is turned on, Pressure work must also be turned on. We know h = u + P/rho. where h = specific enthalpy; u = specific internal energy; P = pressure; rho = density.Hence delta(h) = delta(u) + delta (p/rho) = delta (u) + P.delta(1/rho) + (1/rho).delta(P).
For incompressible liquids with constant density , P.delta(1/rho) = 0 but we need to account for (1/rho).delta(P). For gases both incompressible and compressible, depending upon whether it is constant volume or constant pressure process, the appropriate pressure work remains.

When viscous heating is turned on, the increase in enthalpy needs to be accounted for by the pressure work term. Otherwise, you will see a fictitious drop in exit temperature to satisfy the enthalpy balance.

Here is how you turn on Pressure Work?

In the text interface Define->Models->Energy; FLUENT will prompt you for inclusion of viscous dissipation term, pressure work term, kinetic energy term.

103
This is the standard error caused by FLUENT trying to access data that has not been allocated.

There are several causes discussed below.

For example, in a UDF, you may probe the cell temperature using the macro C_T(c,t). However, if you have not turned the energy equation ¿on¿, then there is NO temperature stored, and you will get an ACCESS_VIOLATION.

To check a Thread for whether a variable is stored on it, you can use the THREAD_STORAGE(t, SV_XXX) macro, where SV_XXX is the storage variable for the equation of interest. For the energy equation, you would use SV_T. This macro returns a pointer to the data. The value is NULL if the data is not available. See ¿storage.h¿ for a complete list of storage variables.

Another cause for the macro is that your case has a UDF hooked, but you do not have the UDF available. The solution is to make sure you have the UDF directory in the correct location relative to the case file.

104
Fluent / How the heat transfer coefficient is computed in Fluent?
« on: April 25, 2012, 10:52:21 AM »
Just wanted to share some information on how the heat transfer coefficient is computed in Fluent:

The heat transfer coefficient is a characteristic of the flow. It is used to measure the ability of a flow to convect energy from walls. HTC=qwall/(Twall-Tref)

For forced convection flows, HTC is traditionally conceived to be a function of velocity (flow rate), fluid properties, and geometry. i.e. NU =HTC/KL = NU(Re,Pr); it is not thought in terms of wall boundary conditions. This is true only if Tref is a bulk (or "mixing cup", or mass-averaged) fluid temperature. For constant properties, by this definition, HTC becomes independent of thermal field.

There are at least 3 methods in calculating HTC in Fluent. The first two uses heat flux to get HTC, which requires a converged thermal field. In these two methods, HTC is determined by measuring the affect of it in the thermal field - by measuring heat flux. The 3rd method does not require to run the thermal field.

1. HTC=qwall/(Twall-Tref)

Tref is defined by the user in the Report->Reference Values. This HTC is a Fluent variable; it can directly be selected under 'Wall Fluxes'. This cannot be used if the bulk temperature changes along the flow direction, which gives it a limited usage. For example, it can't be used for flow inside a heated duct or a pipe, because the bulk temperature changes along the pipe. In these cases, this HTC becomes a fictitious value; it may be good only for that reference temperature. If it is going to be applied as boundary condition for another simulation or FEA analysis, it may only be used with that reference temperature - a fixed thermal boundary condition.

But it can be used for flow over a flat-plate, where the reference temperature far away from the plate remains unchanged in the flow direction. (For flat
plate, the bulk temperature turns out to be temperature at infinity.)


2. HTC = qwall/(Twall-Tcell)
In this definition, Tcell is the adjacent cell temperature. This definition is
much better than a fixed reference temperature for most complicated geometries.
In most cases, if wall functions are used and Y+ is obeyed, the adjacent cell
temperature becomes close to the bulk temperature. (Note that when using
standard wall functions, the Y+ at adjacent cell, ideally, should be between 30
and 60, mostly depending on the application.)


This definition cannot be applied for two-layer model where the first node is
too close to the wall. In this case the adjacent cell temperature will be much
higher than the should-be-used bulk temperature. This will over-predict HTC.

In practice, one may apply a constant wall temperature - value that is close
to actual value, and a fluid inlet temperature. Converge the thermal and the
flow field and then extract this HTC.

Two ways to get this HTC in Fluent:

This HTC can be exported into RADTHERM by typing in the text command:
(ti-write-radtherm)

Enter the filename.
Enter desired output surfaces' names, one at a time.
Hit Enter to exit out.

*Note* For double sided walls, you only need to select one of a
wall-shadow pair. The heat transfer info will be written
for both sides of it.


The output file is in Patran format and contains Packet 16, 17, and 18
information.
16: V_x, V_y, V_z on both sides of the wall.
17: Heat Transfer Coefficients based on T_cell.
18: T_cell


HTC = ('Total Surface Heat Flux' - 'Radiation Heat Flux')/('Wall Temperature
(outer surface)' - 'Static Temperature'). You can perform contour plot of this
CFF without the node values. Without the node value 'Static Temperature' will
grab the adjacent cell temperature.

Note that in order to use q"/(Twall - Tcell), there has to be sufficient flux through the wall.


3. Another method to obtain HTC is to get it directly from wall functions. Note that this method can be used even if there is no flux through the wall!

For segregated solver, incompressible flow, and Ystar > Ystar_T:
Tstar=(Twall-Tcell)*Density * cp * Cmu^.25 * kcell^.5/qwall = Prt * [1/k *
ln (E * ystar) + P]

HTC = qwall/(Twall-Tcell) = Density * cp * Cmu^.25 * kP^.5 / {Prt * [1/k *
ln (E * ystar) + P]}

For segregated solver, incompressible flow, and Ystar>Ystar_T:
Tstar=(Twall-Tcell)*Density * cp * Cmu^.25 * kcell^.5/qwall = Pr * ystar

HTC = Density * cp * Cmu^.25 * kP^.5 / (Pr * ystar)

where P = (pi/4)/sin(pi/4) * (A/k)^.5 * (Pr/Prt - 1) * (Prt/Pr) ^.25

How to get this:

In Fluent6.1.x:
File -> Export
-select RADTHERM under 'File Type'
-select the walls under 'Surfaces'
-select 'Wall Function' under 'Heat Transfer Coef.'
-click on Write
-etc

You can also write a UDF to do this.

105
The emissivity is the most representative radiative property and it has to be entered in the boundary condition panel for heat transfer. At inlets and outlets the default emissivity/absorptivity is 1 (all the radiation exiting the domain does not return). From experiments, the non-metals have an emissivity between 0.8 and 1 for most polar angles. Metals emissivity is between 0.04 and 0.06 increasing rapidly for polar angles larger than 50 degrees with the normal.

You have to distinguish between the internal and external emissivity. The internal emissivity is used to compute the radiative exchange inside the computational domain whereas external emissivity refers to radiation exchange with the exterior. Ideally, electromagnetic wave theory can be used to predict all radiative properties. But this theory neglects the effects of surface conditions. Consequently most of the data available today is from experiments in the 1950s and 1960s. Any radiation book has a number of references on such properties.

Pages: 1 ... 5 6 [7] 8 9 ... 11