> 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/electronics/kraken-x44/kraken-x44-+-talonfx/overview-and-features/wiring-and-modularity.md).

# Wiring & Modularity

## Wiring & Modularity

The Kraken X44 comes with full thread high-engagement #6-32 Power Terminals and #4-40 CAN Terminals providing modularity and user serviceability.

<figure><img src="https://2359625104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR9cY14Bki2Dxl9M3KzOO%2Fuploads%2Fko1WdfqnYgZLosTCDnGc%2FKraken%20X44%20-%20Wiring%20%26%20Modularity.svg?alt=media&amp;token=7bc2bd24-861c-4c7a-8745-13b1633718fc" alt="" width="563"><figcaption></figcaption></figure>

Each Kraken X44 comes with 1 set of 18” Long 10AWG Power Leads and 22AWG Twisted CAN Cables pre-crimped with ring terminals. Teams can utilize the included wires or make their own (or replace the wires over and over without ever worrying about cutting them too short).

We recommend (and include) these larger gauge power leads (10AWG) to reduce resistance, reduce voltage drop, and maximize motor performance.

### Screw Terminal Specs

{% hint style="danger" %}
DO NOT use longer screws in either location. Use of longer screws may damage the controller.
{% endhint %}

| Location        | Screw Size   | Driver Size | Torque Value |
| --------------- | ------------ | ----------- | ------------ |
| Power Terminals | #6-32 x 1/4" | IP10 or T10 | 0.9 N\*m     |
| CAN Terminals   | #4-40 x 1/4" | IP8 or T8   | 0.6 N\*m     |


---

# 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/electronics/kraken-x44/kraken-x44-+-talonfx/overview-and-features/wiring-and-modularity.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.