> 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-x60/kraken-x60-motor/overview-and-features/physical-specifications.md).

# Physical Specifications

The Kraken X60 is designed to be a drop in replacement for a CIM/MiniCIM/NEO/Falcon. This means the size, weight, and mounting are similar to these motors. 

<figure><img src="https://782947646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG5VCf9egrd5oqXAIKxwT%2Fuploads%2FpGkHf5cNIyS62ywGQqkD%2FKraken%20X60%20-%20General%20Dimensions.svg?alt=media&amp;token=9eef425d-1bbb-4a05-beea-9bd7229febb8" alt="" width="563"><figcaption></figcaption></figure>

## Diameter

<table><thead><tr><th width="294.3333333333333">Description</th><th width="378">Value</th></tr></thead><tbody><tr><td>Diameter</td><td>60mm / 2.37in</td></tr><tr><td>Effective Diameter w/ Bump</td><td>63.5mm / 2.50in</td></tr></tbody></table>

{% hint style="info" %}
**What is the bump?**

The bump is where the internal motor's stator wires are routed to the back of the motor. This feature was added to allow there to be enough clearance so the wires couldn't contact the motor's rotor.
{% endhint %}

## Length

The length of the Kraken X60 depends on the version

| Part Number | Description           | Value        |
| ----------- | --------------------- | ------------ |
| WCP-0940    | Kraken X60 + Talon FX | 75mm / 2.96" |

## Weight

The weight of the Kraken X60 depends on version

| Part Number | Description           | Value   |
| ----------- | --------------------- | ------- |
| WCP-0940    | Kraken X60 + Talon FX | 1.2 Lbs |

## Mounting Holes

Kraken X60 has (11x) #10-32 mounting holes on a 2" bolt circle, spaced 30 degrees apart.&#x20;

The reason for the added mounting holes is to allow the Kraken to mount on the traditional 2-hole CIM mounting pattern, as well as applications that use the 6 and 8 hole patterns of the Falcon and NEO.

<figure><img src="https://782947646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG5VCf9egrd5oqXAIKxwT%2Fuploads%2F2bbKzDdVZS3gJPCJTu9x%2FKraken%20X60%20-%20Mounting%20Holes.svg?alt=media&amp;token=7e4dd1f2-800b-47eb-b3ca-44a396ac7cb5" alt="" width="563"><figcaption></figcaption></figure>

### Blind Holes

Each mounting hole is blind, meaning it doesn't go through the mounting plate. By using blind mounting holes, teams cannot lock the motor's internal rotor by using too long of a screw.&#x20;

<figure><img src="https://782947646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG5VCf9egrd5oqXAIKxwT%2Fuploads%2FjvZl75A4JTIsQ3oVKfkl%2FKraken%20X60%20-%20Blind%20Holes.svg?alt=media&amp;token=073bea51-c435-40e4-ab43-c13115ddf373" alt="" width="563"><figcaption></figcaption></figure>

### Pilot Boss

The Kraken X60 also has the same 3/4" diameter pilot boss that the CIM/MiniCIM/NEO/Falcon has. This pilot boss extends 0.1875" past the motor face.

<figure><img src="https://782947646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG5VCf9egrd5oqXAIKxwT%2Fuploads%2FBiaN7ocjQ2xquxC3Pr82%2FKraken%20X60%20-%20Pilot%20Boss.svg?alt=media&amp;token=1ba64cc2-635e-481a-8dcc-08303ebce517" alt="" width="563"><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/electronics/kraken-x60/kraken-x60-motor/overview-and-features/physical-specifications.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.