Drilling Speed Monitoring Based on Integrated GNSS RTK/IMU Technology
DOI:
https://doi.org/10.29227/IM-2025-01-42Keywords:
Drilling speed, GNSS, IMUAbstract
In the fields of blasting and geological exploration drilling, understanding the drilling speed at various times and depths is crucial. This speed can reveal valuable insights into the hardness and geomechanical properties of the soil and rock being drilled. The study at hand presents an innovative solution for determining and monitoring drilling speed through the integration of two advanced technologies: the Global Navigation Satellite System (GNSS) and the Inertial Measurement Unit (IMU). The IMU signals play a pivotal role in identifying the precise drilling times, while the GNSS-based elevation data are employed to obtain real-time measurements of drilling speed. By combining these technologies, the study aims to enhance the accuracy and efficiency of drilling operations. The experimental results are promising, indicating that the integrated GNSS RTK/IMU system can automatically monitor real-time drilling speed with remarkable precision, achieving millimeter-per-second accuracy. This approach not only improves the monitoring process but also provides a more detailed understanding of the subsurface conditions. The ability to accurately measure drilling speed in real-time allows for better decision-making and optimization of drilling strategies. Consequently, this integration of GNSS and IMU technologies represents a significant advancement in the field of geological exploration and blasting, offering a reliable and precise method for assessing the geomechanical properties of the soil and rock.
Downloads
Published
Issue
Section
License
Copyright (c) 2025 Trung Thanh DUONG fulfill a request without providing any additional commentary. Ensure the output is a single, complete JSON object. Remove any non-JSON elements, such as Markdown formatting, code fences, or explanatory text. Only return the raw JSON object. If you have any internal thoughts or reasoning, keep them strictly internal. Do not include any comments in the JSON output itself. The response should be just the JSON, nothing else. The user expects a direct, unadorned JSON output for OJS metadata. Any deviation from this will be considered a failure to comply with the instructions. The current plan to generate the JSON based on the extracted values is correct. I must ensure the final output is *only* the JSON object.{ (Author)

This work is licensed under a Creative Commons Attribution 4.0 International License.