> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/cartographer-probe/features/axis-twist-compensation.md).

# Axis Twist Compensation

<br>

{% hint style="warning" %}
This requires Scan Calibration AND Touch Calibration
{% endhint %}

We can automate axis twist compensation calibration using touch to get the nozzle offset. Simply run `CARTOGRAPHER_AXIS_TWIST_COMPENSATION` and let Cartographer do the rest. Remember to run `SAVE_CONFIG` to persist the change.

You MUST ensure that your Twist Axis is within your probe boundaries.<br>

{% hint style="success" %}
You can pass an axis to compensate along both axes, using `AXIS=Y`.
{% endhint %}

{% hint style="success" %}
If your axis twist is dependent on chamber temperature, you can run `CARTOGRAPHER_AXIS_TWIST_COMPENSATION` as part of your start print macro.\
\
Just remember to run it *after* leveling your bed and *before* bed mesh calibrate.
{% endhint %}

**Unknown command "CARTOGRAPHER\_AXIS\_TWIST\_COMPENSATION"**

You will need to enable the `axis_twist_compensation` function by adding the below section in your printer config. For [Klipper](https://www.klipper3d.org/Config_Reference.html?h=axis_#axis_twist_compensation) it can be empty, for [Kalico](https://docs.kalico.gg/Config_Reference.html#axis_twist_compensation) you need to define some fields.<br>

```
[axis_twist_compensation]
```


---

# 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.cartographer3d.com/cartographer-probe/features/axis-twist-compensation.md?ask=<question>&goal=<user_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.