fluent udf环境变量的设置.doc

ANSYS 15.0 fluent udf环境变量的设置初学udf,还没进入主题就被udf问题搞死了，摸索了一两天终于让我搞出了点名堂，本人用的是ANSYS 15.0和vc 10.0.不多说，先把ANSYS 和vc都装上，网上有教程安装的，一步步来别跳步。最好把vc6也装一下，因为里面有的东西设置环境变量要用到。先不要打开软件。设置环境变量：1. C:Program FilesANSYS Incv150fluentntbinwin64目录下双击setenv和remenv2.设置环境变量：INCLUDEC:Program Files (x86)Microsoft Visual Studio 10.0VCinclude;C:Program Files (x86)Microsoft SDKsWindowsv7.0AInclude;LIBC:Program Files (x86)Microsoft Visual Studio 10.0VClibamd64;C:Program Files (x86)Microsoft SDKsWindowsv7.0ALibx64;C:Program Files (x86)Microsoft Visual Studio 10.0VCatlmfclib;PATHC:Program Files (x86)Microsoft Visual Studio 10.0VCbinamd64;C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDE;找个udf文件，注意udf是支持三维还是二维的，打开fluent , 设置工作目录。如下：接着就是编译了，不用打开case的，直接就可以define .如果出现什么 xcopy.我们找到C:WindowsSystem32里面的xcopy复制到C:Program Files (x86)Microsoft Visual Studio 10.0VCbin；C:Program Files (x86)Microsoft Visual Studio 10.0VCbinamd64；如果出现“size_t”: 重定义；不同的基类型，可能是你的udf文件有问题。如果实在不行，按照下面的环境变量重新设置一下，重启电脑。INCLUDE C:Program Files (x86)Microsoft Visual Studio 10.0VCinclude;C:Program Files (x86)Microsoft SDKsWindowsv7.0AInclude;LIB C:Program Files (x86)Microsoft Visual Studio 10.0VClibamd64;C:Program Files (x86)Microsoft SDKsWindowsv7.0ALibx64; C:Program Files (x86)Microsoft Visual Studio 10.0VCatlmfclib;PATH C:Program Files (x86)Microsoft Visual Studio 10.0VCbin;C:Program Files (x86)Microsoft Visual Studio 10.0VCbinamd64;C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDE;C:Program Files (x86)Microsoft Visual Studio 10.0Common7Tools;c:program filesansys incv150fluentntbinwin644.1 Problem with nmakeAccording to the manual, I wrote a C code, saved it in my working folder, added it, clicked Build. and then I saw this:(system copy C:PROGRA1ANSYSI1v140fluentfluent14.0.0sr cmakefile_nt.udf examplewin642dmakefile )1 file(s) copied.(chdir example)()(chdir win642d)()nmake is not recognized as an internal or external command,operable program or batch file.nmake is not recognized as an internal or external command,operable program or batch file.Done.4.2 Solution to the nmake problemWithout any detail, the problem is caused because nmake.exe cannot be found. The solution is to start Fluent from the x64 version of the Visual Studio 2013 Command Prompt:1. Open theStart screen(press Windows button on your keyboard)2. Type Visual Studio Tools, click the folder.3. In the folder click and start VS2013 x64 Cross Tools Command Prompt4. Navigate to your working folder, i.e. the folder where your case and data files are (.cas & .dat).5. Start Fluent with C:Program FilesANSYS Incv140fluentfluent14.0.0launcherwin64 (quotation signs included, in case of standard installation6. Make sure that on the Environment tab Setup Compilation Environment for UDF is ticked. The default address is fine.Starting Fluent this way should solve the nmake problem and the compilation message should look like this:(system copy C:PROGRA1ANSYSI1v140fluentfluent14.0.0sr cmakefile_nt.udf exexwin642dmakefile )1 file(s) copied.(chdir exex)()(chdir win642d)()# Generating ud_io1.hvelocity_profile.c# Generating udf_names.c because of makefile velocity_profile.objudf_names.c# Linking libudf.dll because of makefile user_nt.udf udf_names.obj velocity_profile.objMicrosoft (R) Incremental Linker Version 10.00.30319.01Copyright (C) Microsoft Corporation. All rights reserved.Creating library libudf.lib and object libudf.expDone.5.1 Problem with x64 systemIn case you do not have Microsoft Visual Studio 2013 Express then likely you tried starting Fluent from the Visual Studio Command Prompt (2010) or any other previous version of VS command prompt. It is likely that you encountered a problem when clicking Load, specifically this one:The UDF library you are trying to load (libudf) is not compiled for 2d on the curent platform (win64).The system cannot find the file specified.X:libudfwin642dlibudf.dllThe reason of this error is that previous versions of Visual Studio are 32bit and do not work with your x64 version of Fluent. You probably googled the problem and found advice to start Fluent from the command promt of the SDK (Software Development Kit) 7.0/7.1 instead, or from the command prompt of the .NET Framework. Unfortunately, as Microsoft states on their website at theWindows SDK 8.1 download page:The Windows SDK no longer ships with a complete command-line build environment. You must install a compiler and build environment separately. If you require a complete development environment that includes compilers and a build environment, you can download Visual Studio 2013, which includes the appropriate components of the Windows SDK.Older versions of the .NET Framework and SDK do not seem to work properly on Windows 8.1 (citation needed, just my experience). I also found out that with a working x64 SDK installed you can start the simple windows command prompt (cmd.exe) with the proper environmental variables using a cmd.exe /k command, which I failed to get to work.5.2 Solution to the problem of x64 systemThe solution to this is to start Fluent from the x64 command prompt VS2013 x64 Cross Tools Command Prompt as described in (4.1) instead of previous versions of VS or SDK/.NET command prompts.6.1 Problem with math.hAnother problem occurred even after I had everything set up. This problem was reported by cfd-online user KITetima as well inthis forum topic.The very simple c code to initialize the velocity on the inlet boundary to a given velocity profile did not compile, and the following error message appeared:C:Program Files (x86)Microsoft Visual Studio 12.0VCINCLUDEmath.h(482) : error C2059: syntax error : ,C:Program Files (x86)Microsoft Visual Studio 12.0VCINCLUDEmath.h(482) : error C2143: syntax error : missing ) before constantC:Program Files (x86)Microsoft Visual Studio 12.0VCINCLUDEmath.h(482) : error C2143: syntax error : missing before constantC:Program Files (x86)Microsoft Visual Studio 12.0VCINCLUDEmath.h(482) : error C2059: syntax error : constantC:Program Files (x86)Microsoft Visual Studio 12.0VCINCLUDEmath.h(482) : error C2059: syntax error : )Done.I could not figure out exactly what is the problem, but it seems that the header file math.h provided by VS2013 has some mistakes, or somehow isnt compatible with Fluent 14 (and Fluent 14.5).First I tried to give the math.h header file for the UDF myself in the Header section (see Figure above), however, the compiler still used the math.h file that is located in C:Program Files (x86)Microsoft Visual Studio 12.0VCinclude.6.2 Solution to the problem with math.h1. Keep the software installed on your computer, but also installMicrosoft Visual C+ 2010 Express2. Go to the following folder:C:Program Files (x86)Microsoft Visual Studio 10.0VCinclude3. From this folder copy the math.h file toC:Program Files (x86)Microsoft Visual Studio 12.0VCinclude4. Start Fluent as described above in (4.2). Now you will be using VS2013 as compiler but the math.h file from VS2010, which worked fine for me.7. Setting the Environmental VariablesMany pages that you find dealing with the problem give suggestions like make sure your environmental variables are set. However, it is not clear how to do that. I succeeded finally at making it work, however, before that I managed to ruin my Windows and I needed a network registry operation to fix it, so first of all:0.DO NOT DELETE OR MODIFY WHAT IS ALREADY IN THE PATH VARIABLE.1. Right click onMy computer/This PCand clickProperties2. On the left side of the screen clickAdvanced system settings3. On the bottom clickEnvironmental variables4. In the bottom box look for the Variable namedPath, select it and clickEdit5. Be careful not to modify anything that is already there.6. At the end, put a semicolon ( ; ) and after that paste the address of your Fluent executable, i.e. add to the end of the Path variable;C:7. Add to the end the folder where the vcvarsx86_amd64.bat file of your Visual Studio 12 is found. By default this is:;C:Program Files (x86)Microsoft Visual Studio 12.0VCbinx86_amd648. Click OK and OK your way out of the My computer properties. You are all set hopefully.This will enable you to start fluent by simply typing the command fluent in your command prompt. You can also add the 2D and 3D executables separately to the Path variable.8. Remarks and disclaimerI would like to emphasize that I am in no way an expert in CFD/C+/UDFs/Windows SDK, only a beginner user. I do not take any responsibility for anything described or suggested on this page, or any damage caused by following these steps. This is merely a summary of my experiences with my system, and I cannot guarantee that the solutions will work in any other setup (or with this setup on other systems).However, I do hope that some will find it useful and some people will save many hours of searching for the solutions.Kind regards,用户变量FLUENT_INCc:program filesansys incv140fluentICEM_ACNC:Program FilesANSYS Incv140icemcfdwin64_amdincluded:Program Files (x86)Microsoft Visual Studio 10.0VCinclude;C:Program Files (x86)Microsoft SDKsWindowsv7.0AInclude;libd:Program Files (x86)Microsoft Visual Studio 10.0VClibamd64;C:Program Files (x86)Microsoft SDKsWindowsv7.0ALibx64MSDevDirD:Program Files (x86)Microsoft Visual StudioCommonMSDev98Pathd:Program Files (x86)Microsoft Visual Studio 10.0VCbinamd64;d:Program Files (x86)Microsoft Visual Studio 10.0Common7IDE;PVX_INSTALL_DIRD:proe_GB_kuMONLibsTEMP%USERPROFILE%AppDataLocalTempTMP%USERPROFILE%AppDataLocalTemp系统变量ADSK_3DSMAX_x64_2014C:Program FilesAutodesk3ds Max 2014ANSYS_SYSDIRwinx64ANSYS_SYSDIR32win32ANSYS140_DIRC:Program FilesANSYS Incv140ANSYSANSYSLIC_DIRC:Program FilesANSYS IncShared FilesLicensingAWP_LOCALE130en-usAWP_ROOT140C:Program FilesANSYS Incv140CADOE_DOCDIR140C:Program FilesANSYS Incv140CommonFileshelpen-ussolviewerCADOE_LIBDIR140C:Program FilesANSYS Incv140CommonFilesLanguageen-usCM2014DIRC:Program Files (x86)Common FilesAutodesk SharedMaterialsComSpec%SystemRoot%system32cmd.exeD:Program Files (x86)Microsoft Visual StudioVC98Bin;C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDE;D:Program Files (x86)Microsoft Visual StudioVC98Lib;C:Program Files (x86)Microsoft SDKsWindowsv7.0ALibx64DEVMGR_SHOW