> For the complete documentation index, see [llms.txt](https://docs.sevenpens.com/drawtab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sevenpens.com/drawtab/process/measuring/measuring-hover.md).

# Measuring hover

## Overview

To more accurately assess hover height, I use a small "staircase" that goes up in 0.5 mm increments to test how hover works with tablets.

## The hover testing tool

<figure><img src="/files/ZGPMyxRTS2lIyDaehyx2" alt=""><figcaption></figcaption></figure>

## Testing process

* Overall, I move from low to high
* I begin with the pen placed on the first step which represents 0.5mm from the tablet surface.
* I then move up each step in 0.5 mm increments
* On each step I note
  * Whether the tablet detects the pen
  * If the tablet detects the pen, then whether there is any hover jitter. And how much hover jitter there is.
* I move up the steps until the pen is no longer detected by the tablet.

## 3D printing notes for tool

### Printing details

* Printer: Bambu X1C
* Nozzle: Bambu Lab X1 Carbon 0.4 nozzle
* Filament: Bambu Basic PLA
* Layer height: 0.2mm
* Initial layer height: 0.2mm
* Plate: Textured PEI Plate

### Accuracy

Because the layer height is 0.2mm:

* The whole number steps are very accurate
* The intermediate steps such as 1.5mm, 2.5mm are slightly thicker than they should be.

I measured the steps with a digital caliper and had these results:

* 1.0mm step = 1.04mm
* 1.5mm step = 1.63mm
* 2.0mm step = 2.04mm
* 2.5mm step = 2.63mm
* 5.0mm step = 5.04mm
* 5.5mm step = 5.65mm
* 10.0mm step = 10.04mm
* 10.5mm step = 10.64mm


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sevenpens.com/drawtab/process/measuring/measuring-hover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
