Are you using an UDF? Such error message shows up only when you are trying to access some internal variables of FLUENT solver in the UDF which are not actually accessible from the respective macro routine program.

it hard to say about this error because this comes in most of the cases when their is some error so i suggested you that please go through fluent manual and try to figure out you mistake. you may follow my earlier post that might be help you.

https://www.researchgate.net/post/Does_anyone_have_experience_with_Fluent_UDF_Error_received_a_fatal_signal_Segmentation_fault?_tpcectx=qa_overview_recent&_trid=540ae947d2fd6497578b45c9_4

Ask someone to modify you model and UDF if it's your first time to deal with phase change or meet this dialog.

I don't know if possible in your case, but try running your problem without UDF first, So that you will be sure if the problem is due to the UDF or not.

Am not actually using UDF in my case. Am solving a problem which involves melting, evaporation and gas phase reaction. I have enabled multiphase VOF, melt & solidification and species transport. When i input all my parameters and i begin to run the simulation, i get that error.  I have attached a link to my case file to this comment. Pls feel to have a download and have a look. Your technical suggestions are welcomed. Thank you.

https://www.dropbox.com/sh/5gb63plzy86mg4g/AADZJ4kokOGX63PzDmNcOXrEa?dl=0

I am working with DPM and  using UDF. Without UDF my model is working good. When I compiled my UDF I got a warning (image attached) but opened the file. After compilation when I run the simulation, it stopped with n fatal signal error.  Here is my UDF

/**************************************************************************************/

/* UDF for computing cell co-ordinates */

/**************************************************************************************/

#include "udf.h"

#include "sg.h"

#include "prop.h"

#include "dpm.h"

#include "surf.h"

#define WALL_ID 8

DEFINE_DPM_SCALAR_UPDATE(particle_coords, c, ct, initialize, p)

{

real A[ND_ND];

int n;

face_t f;

Thread *ft;

c_face_loop(c, ct, n)

{

f=C_FACE(c, ct,n);

ft=C_FACE_THREAD(c, ct, n);

if (NNULLP(ft))

{

if (THREAD_ID(ft)== WALL_ID)

{

p->user[0] = p->state.pos[0];

p->user[1] = p->state.pos[1];

p->user[2] = p->state.pos[2];

}

}

}

}

DEFINE_DPM_OUTPUT(Particle_coords_output, header, fp, p, thread, plane)

{

char name[100];

if (header)

{

if (NNULLP(thread))

fprintf(fp,"(%s %d)\n",THREAD_HEAD(thread)-> dpm_summary.sort_file_name,3);

else

fprintf(fp,"(%s %d)\n",plane->sort_file_name,3);

fprintf(fp,"(%10s %10s %10s %s)\n",

"X", "Y", "Z");

}

else

{

sprintf(name,"%s:%d",p->injection->name,p->part_id);

fprintf(fp,

"((%10.6g %10.6g %10.6g) %s)\n", p->state.pos[0], p->state.pos[1], p->state.pos[2]);

}

}

 Could you please help me?

Saeed

Hello Saidul, wish i could be of great help with regard to your UDF. I will however advice that before you build, load the function and finally hook the UDF, you fish out every error in C file. The image attached to your message shows some error ie (9)(10). Check the corresponding lines of your UDF and make the correction using visual studio. 

Hello Daniel, I got the same error but when I tried adapting the mesh. any help please?

have solved this problem?? I come across the same problem

Actually, what types of UDF you are using? May be I can help you out. You can share your UDF and then I will have a look.

 Hi Everybody,

Have you solved this problem? I get this problem when I try to use C_WALL_DIST(c,t); in UDF. No interpretation error but FLUENT fails to initialize.

For this is the code I am trying to interpret.

#include "udf.h"

DEFINE_PROFILE(wall_d_bc,t,i)

{

Thread *t0;

face_t f;

cell_t c, c0;

double F_x,area,A[ND_ND],yplus,wshear;

begin_f_loop(f,t)

{

c0 = F_C0(f,t);

t0 = THREAD_T0(t);

yplus = C_STORAGE_R(f,t,SV_WALL_YPLUS_UTAU); /* Y+*/

F_x = F_STORAGE_R_N3V(f,t,SV_WALL_SHEAR)[0];

F_AREA(A, f, t);

area = NV_MAG(A);

wshear=-1*F_x/area;

/* wshear = C_MU_L(c0,t0)*C_U(c0,t0)/C_WALL_DIST(c0,t0); wall shear stress */

F_PROFILE(f,t,i) = 6.*wshear/(0.075*C_MU_L(c0,t0)*SQR(yplus));

}

end_f_loop(f,t)

}

Thanks,

Pratik.

For your information that there's another report said that someone changed to "enhanced wall treatment" instead of "standard wall functions" and succeeded.

Patrick, Did you solve this problem? Does initialization necessarily solves the issue?

Ikrima, did you find any solution for the problem reported with adopting the mesh?

I solved this problem by reinstalling ANSYS. I got a fresh copy from the representative in Middle East and Africa as my school has an academic license and I stopped having the problem.

Oladapo,

You mean you can use C_WALL_DIST with no problem?

 Hi Pratik,

i am new to this coding and i want to know why have you used

t0 = THREAD_T0(t); instead of t0 = F_C0_THREAD(f,t);and what is the use of it .??

Hi,

I want to inquire about the following error, please;

Error: %cx-set-label: wta[1](widget)

Error Object: #f

I got similar error.

"Error: token too large

Error Object: ()"

I think my error came because I set a contour as one of my solution animations and, allowed fluent to save a file for every iteration. Fluent saved numerous animation case files in the requisite fluent directory. I could see step by step progress during my simulation but, soon ran into the above mentioned error.

Different cases will report different errors. Therefore, users should:

a. endeavor to understand the cause of the error.

b. "Save the workbench file, close it and then reopen it and try to run Fluent"

c. check the case file and error message which should be in -userfile-filename-dp0-FFF-fluent (by default).

I also got same problem.

Situation: When i am trying to read case and then data file

Error type: "Error: received a fatal signal (Segmentation fault).

Error Object: #f"

Solution: After reading your case file, initialize your case. Then read data file.

This will solve your problem. Please feel free to email me if you find something that suits your interests and/or have further questions.

The segmentation fault means that you try to access a variable, which is not saved. please refer to:

https://www.cfd-online.com/Forums/fluent-udf/140631-fluenterror-received-fatal-signal-segmentation-fault.html