24.08.2013 Views

MODELING CHAR OXIDATION AS A FUNCTION OF PRESSURE ...

MODELING CHAR OXIDATION AS A FUNCTION OF PRESSURE ...

MODELING CHAR OXIDATION AS A FUNCTION OF PRESSURE ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7. Model Evaluation and Discussion<br />

The HP-CBK model, using the Langmuir rate equation, the effectiveness factor<br />

and the random pore model, was evaluated by comparison with five sets of pressure-<br />

dependent reactivity data: 1) graphite flake data (Ranish and Walker, 1993); 2) rough<br />

sphere combustion data (Banin et al., 1997a); 3) large particle oxidation data (Mathias,<br />

1996); 4) pulverized char drop-tube data (Monson, 1992); and 5) TGA and FFB data<br />

from this study.<br />

Proper values have to be assigned to the kinetic and pore structure parameters in<br />

order for the HP-CBK model to predict the char oxidation rates in agreement with<br />

experimental data. An optimization model, StepIt (Chandler, 1999) was used to adjust the<br />

kinetic parameters (A 1p, E 1p, A p, and E p) and pore structure parameters (r p1, r p2 and M)<br />

within pre-set ranges to best fit the experimental data. The optimum values of the<br />

parameters were used in the HP-CBK model. The HP-CBK model was then evaluated by<br />

comparing the model calculations to experimental data. In this sense the HP-CBK model<br />

unifies and explains experimental data with one different set of parameters for each set<br />

of data, rather than predicts the reaction rates. This is still a substantial contribution,<br />

since little is known about high-pressure char oxidation. The correlations between kinetic<br />

parameters (activation energies and pre-exponential factors) and measurable char<br />

properties are not yet possible, since experimental data at high pressures and<br />

87

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!