[jabulani]

Hi All,

I'm attempting to use Diesel Unsteady Flamelet for Diesel engine combustion case with CHEMKIN reaction mechanism imports. There is however an error message (shown below) when I attempt to initialise the case. Much appreciated if anyone can explain or help out.

================================================== ==

Error Object: #f
Tox = 313 K, Tfu = 313 K, <X> = 0 /s, <p> = 101325 Pa
Initializing unsteady flamelet
Failed to calculate stochiometric mixture fraction: Assume fsto=0.5
Done.

Generating PDF lookup table
Type of the PDF Table: Nonadiabatic Table with Single Flamelet Model (Two Streams)
Calculating table .....

Error:
FLUENT received fatal signal (ACCESS_VIOLATION)
1. Note exact events leading to error.
2. Save case/data under new name.
3. Exit program and restart to continue.
4. Report error to your distributor.

Error:
FLUENT received fatal signal (ACCESS_VIOLATION)
1. Note exact events leading to error.
2. Save case/data under new name.
3. Exit program and restart to continue.
4. Report error to your distributor.
Error Object: #f

==================================================

[AbolfazlJalalabadi]

Originally Posted by jabulani

Hi All,

I'm attempting to use Diesel Unsteady Flamelet for Diesel engine combustion case with CHEMKIN reaction mechanism imports. There is however an error message (shown below) when I attempt to initialise the case. Much appreciated if anyone can explain or help out.

================================================== ==

Error Object: #f
Tox = 313 K, Tfu = 313 K, <X> = 0 /s, <p> = 101325 Pa
Initializing unsteady flamelet
Failed to calculate stochiometric mixture fraction: Assume fsto=0.5
Done.

Generating PDF lookup table
Type of the PDF Table: Nonadiabatic Table with Single Flamelet Model (Two Streams)
Calculating table .....

Error:
FLUENT received fatal signal (ACCESS_VIOLATION)
1. Note exact events leading to error.
2. Save case/data under new name.
3. Exit program and restart to continue.
4. Report error to your distributor.

Error:
FLUENT received fatal signal (ACCESS_VIOLATION)
1. Note exact events leading to error.
2. Save case/data under new name.
3. Exit program and restart to continue.
4. Report error to your distributor.
Error Object: #f

==================================================

I have this exact problem, I'd be glad to know if you got this over with somehow, thanks