> For the complete documentation index, see [llms.txt](https://docs.voltera.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltera.io/docs/v-one/learn-v-one/drill-attachment/custom-drill-bit-sizes.md).
# Custom Drill Bit Sizes
The V-one comes with a 10-piece set of high-precision PCB drill bits, containing the most common drill bit sizes:
* 2x - 0.70mm
* 2x - 0.80mm
* 2x - 0.90mm
* 2x - 1.00mm
* 2x - 1.60mm
### Custom bit sizes
The V-One drill will accept 1/8" shank drill bits which are the correct length — 38.1mm or 1.5 inches long.
{% hint style="warning" %}
You can off-road with other sizes at your own risk — poor height tolerances can lead to stuck/damaged bits. It’s also possible that the V-One won’t be able to probe properly if your drill bit is too short.
{% endhint %}
If you need a drill bit size that’s not included with your V-One, we often recommend these folks for [purchasing bits](https://www.precisebits.com/products/carbidebits/drills.asp?tsPT=!!!MetricDrillBits!!!!) that will fit the V-One. Make sure you’re buying bits **without the spacer**.
The V-One software won’t be able to compensate for a difference in bit size, so make sure that you’re certain that the bit size matches the holes you’re drilling.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.voltera.io/docs/v-one/learn-v-one/drill-attachment/custom-drill-bit-sizes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
