Answers are grounded in this paper and cite their sources.
Analysis reveals improved torque predictions in full-face rock tunnel boring machines, indicating enhanced accuracy for engineering applications.
A full-face rock tunnel boring machine (TBM) has two main parameters: cutterhead thrust and cutterhead torque. Cutterhead thrust can be predicted numerically using different methods, such as the rated thrust of the disc cutter, the indentation test of the disc cutter, a linear breaking experiment, or applying statistical models based on field data. However, cutterhead torque prediction still lacks the necessary and sufficient theoretical analysis and corresponding research. Consequently, we studied the rock-breaking characteristics of the disc cutter on the cutterhead and found a difference between the lateral friction resistance and the inner and outer rock breaking. We then proposed the cutterhead torque composition of the full-face rock tunnel boring machine, shoveling and transporting ballast torque, rolling resistance torque, lateral friction resistance torque, and disc cutter lateral imbalance torque, and established the corresponding theory. Through practical engineering verification, we found that the relative error between the cutterhead torque value calculated by the theory and the actual value was only 0.51 %. If the lateral friction resistance moment of the disc cutter rock breaking and the lateral imbalance moment of the disc cutter are not considered, the relative error between the calculated value of cutterhead torque and the actual value is 7.48 %. Therefore, the accuracy of the established cutterhead torque theory is 6.97 % higher than that of the disc cutter linear rolling crushing rock test theory. The research results provide an important reference for determining the cutterhead torque of a full-face rock tunnel boring machine.
No takes yet. Share an insight, caveat, or question.
Zhang et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: