> 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/misc/faq-and-trouble-shooting.md).

# FAQ & Trouble Shooting

## Common Questions

<mark style="color:blue;">Q: What tread is recommended?</mark>

A: We recommend using the Molded (High Grip) for the best user experience. These wheels provided the easiest tread swaps. The lack of bolts to attach the tread also helps prevent damaging carpet. These wheels were designed with the team's experience in mind.

<mark style="color:blue;">Q: Can I use other motors besides the KrakenX60?</mark>

A: Other motors can be used but the Kraken X60 is the recommended motor.

<mark style="color:blue;">Q: Why is the wheel not spinning smoothly?</mark>

A: Ensure that the 45T Bevel Gear that was installed during the wheel installation process is fully seated.

<mark style="color:blue;">Q: How do I set up a Swerve Drivetrain?</mark>

A: Refer to the [CTR Swerve Project Generator](https://v6.docs.ctr-electronics.com/en/stable/docs/tuner/tuner-swerve/index.html) for detailed instructions on how to set up your drivetrain.


---

# 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/misc/faq-and-trouble-shooting.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.