Chemical reaction failed to add

At present, I am using the CFD-DEM model to simulate the reactor. I was wrong when I tried to add a chemical reaction. Specifically, when I want to read the usr _ rates _ des.file, it shows the error in the figure.


In addition, when I try to build the solver, I show the error in the figure.

How should I solve these problems?

  1. You should always attach your project files when looking for help here - go to the main menu, select “Submit bug report”, and that will create a ZIP file you can upload here.

  2. I’m not sure what you were doing, but it looks like you were trying to load a Fortran file as chemical reaction file. Loading chemical reactions from a file means loading a file with reaction definitions in the form described here in the MFiX manual: 4.14.2. Setting up chemical reaction cases — MFiX 24.4 documentation - a file of reaction definitions that looks like this:

@(RXNS)                      
CH4_Combustion {              
chem_eq = "CH4 + 2O2 --> CO2 + 2H2O"                  
}                            
@(END)

The reactions themselves are defined in the reactions file. You can also add the reactions using the GUI which will create the reactions data block for you. This is the more common method of setting up reactions. Importing from a file is a special feature for users who have a large number of reactions and are importing from another system, such as Chemkin.

The reaction rates are either defined in the usr_rates.f Fortran file, which must be compiled (custom solver), or, as of MFiX 24.4 the built-in Arrhenius model can be used, sparing you from having to write and compile Fortran code for the reaction rates. To enable this, use the Chemistry/Options pane:

MFiX will warn you if these options are enabled and you have a usr_rates.f file.

To help with the second error (compilation failure) I need to see your code.

– Charles

Thank you for your answer. This is my relevant documents.
usr1_rates_des.f (3.0 KB)
MIDREX.mfx (20.7 KB)
when I try to build the solver, I show the error in the figure.