> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/gearboxes/wcp-swerve-x2/overview-and-features/zeroing-module.md).

# Zeroing Module

The Zeroing Blocks below will be used to help align the wheel to the module so that a zero can be set in code.

{% file src="/files/H5KR2e6EbcAFHB0nHAgJ" %}

{% file src="/files/j0ZgeZRXIRkv4rkkvYYD" %}

Once you have your Blocks printed, zeroing the module will be a breeze. Simply align the block with the Wheel Fork and ensure the top of the block is flush with the Swerve X2 plate.

{% hint style="info" %}
This method will set the modules at 45 degrees from straight. This must be accounted for in the code.
{% endhint %}

{% hint style="warning" %}
Make sure that the flat of the fork is aligned with the Zeroing Block.
{% endhint %}

<figure><img src="https://4022448544-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv3U1blZmAL1arpmYDPqt%2Fuploads%2FwozF761wc1DXVtxxk1RB%2FSwerve%20X2%20-%20Zeroing%20Module.svg?alt=media&amp;token=be38a55a-d8f9-448c-9469-e0e89d1f8c0a" alt=""><figcaption></figcaption></figure>


---

# 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.wcproducts.com/welcome/gearboxes/wcp-swerve-x2/overview-and-features/zeroing-module.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.