Skip to main content

Serial UDF on Windows OS



UDF has to be compiled, can’t be interpolated

Steps

For ansys 16.x, launch Fluent from the Command Line using the VS2015 x86 x64 Cross Tools Command Prompt (not x64 x86 cross tools)
2)     Navigate to your working folder, i.e. the folder where your case and data files are (.cas & .dat).
3)     Type “fluent” in the command window to launch Fluent  or  C:\Program Files\ANSYS Inc\v161\fluent\ntbin\win64\fluent.exe (quotation signs included, in case of standard installation; fluent version: 16.1).
4)     Make sure that on the Environment tab 'Setup Compilation Environment for UDF' is ticked. The default address is fine.
1.      Read mesh/cas file
2.      Setup turbulence model/boundary conditions, etc.
3.      Compilation
a.      Define/user-defined/functions/compiled, load
4.      Hook UDF file to velocity component at inlet
a.      Boundary condition/inlet/x or y component velocity/udf

5.      Setup point monitors at inlet
Create a point at inlet and monitor the velocity at the defined point
a)      Define a point at inlet:
Create a point at inlet BC
Surface/point


b)       Solution--monitors--surface--fill your information to dialog table
Report type: vertex average
Field variable: velocity, velocity magnitude/component;
Surface: a point at inlet BC
6.      Setup time step size, 0.002s, save cas file
a.      Time step, 1/100 period of wave
b.      1 degree per time step, 0.001s, 360 time step per circle of turbine rotation

If ω=14.34, TSR=5.5, T=0.44,
U(m/s)
TSR
r(m)
Angular velocity
T(s)
time step size
0.6
5.5
0.23
14.34782609
0.437919
0.001216



7.      Initialisation, compute from inlet
Calculation, 200 time steps


Comments

Popular posts from this blog

TUI Fluent

‎ Table of Contents 1. TUI 1.1. Examples 1.1.1. Steady 1.1.2. Unsteady 1.2. discretization schemes 1.3. Turbulence model 1.4. Reference 1.5. Save residual 1.6. Journal 1.6.1. record journal GUI 1.6.2. The interactive TUI inside Fluent helps: 1.7. define 1.7.1. boundary-conditions 1.8. change rotational velocity of moving reference frame 1.8.1. batch model 1.8.2. interactive console TUI 1.9. set background color 1.9.1. invalid command [background] 1.10. syntax 1.11. Batch model 1.12. Boundary condition 1.12.1. Inlet BC 1.13. Animation/residual/monitor on cluster 1.14. Solver 1.15. Change pressure-velocity-coupling model in batch mode 1.16. time step size 1.17. Modifying the View 1.18. initialization 1.19. discretization schemes 1.20. Set under relaxation 1.21. log of execute makefile 1 TUI keywords: Background Execution on Linux Systems, journal file Programming language : Scheme , as a Lisp dial

Fluent Error FAQ

  Process 1928: Received signal SIGSEGV. Running on windows Mesh size, 12M serial     Error:  received a fatal signal (Segmentation fault).     Error Object: #f parallel     select 4 processors         error information     Node 0: Process 1928: Received signal SIGSEGV.         Node 5: Process 2824: Received signal SIGSEGV.     MPI Application rank 0 exited before MPI_Finalize() with status 2      The fl process could not be started.         Reason         This is primarily a Windows issue.                 If running Fluent with -t1 or higher number of processes and leave the session for an extended period of time (2-20 hours), it receives the following message in the console:                 The fl process could not be started.                 No other information about what timed out is provided, and only the cortex process is left running. This issue becomes more significant in light of the switch from serial to -t1.         IP interfaces on the machine

Turbulent viscosity limited to viscosity ratio of 1e+05

** Turbulent viscosity limited to viscosity ratio of 1e+05 *** reason The possible *causes* for large turbulent viscosity ratio include: - Bad initial conditions for the turbulence quantities (k and e) - Improper turbulent boundary conditions - Skewed cells *** solution If the problem is not caused by *bad mesh*, then *the beginning of the phenomena* can usually be avoided by: -Turn off solving *turbulence equations* for the first 100-200 iterations -Turn on turbulence and continue iterations If the problem occurs *in the middle of the iteration process*, then use the following procedure: - Stop the iteration - Turn *off* all equations except the *turbulence equations* - Increase turbulence under relaxation factors (URFs) (k and e) to 1 and iterate for 20-50 iterations - *Turn back all equations* and reduce the turbulence URFs to 0.5-0.8 and then continue iterations - Repeat the above steps for several times For *faster convergence*, it might be useful to obtain an initial solution wit