> 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/wcp-throughbore-by-cancoder-1-2-hex/overview-and-features.md).

# Overview and Features

The WCP ThroughBore by CANcoder (1/2" Hex) is a product developed in conjunction with Cross the Road Electronics. This rotary sensor allows teams to measure relative or absolute position of a shaft installed through the rotation portion of the device. Designed to make integration into standard FRC ecosystems a breeze, there are countless ways to utilize this sensor.

<figure><img src="https://1560170492-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlWSBoSocMCLG7fQxSoe%2Fuploads%2FFQv9NmxM3GfoEovgQJzv%2FThroughBore%20Encoder%20(Update)%20-%20Cover.svg?alt=media&amp;token=bf524fef-2c9b-47d8-8d58-4443bfb12a1c" alt="" width="563"><figcaption></figcaption></figure>

### Features

* Off-axis encoding technology
* No backlash between sensor and sensing element
* Small footprint, fits in the shadow of 1” wide structure
* Mechanical zero that aligns to both notches of the hex bore and the outer case
* LED light pipe to display state of the encoder
* Latching Molex SL connector, with cable included
* Compatible with CTR software and Phoenix Pro

{% hint style="success" %}
For CAN ID Setup and Troubleshooting, refer to the [CTR documentation](https://v6.docs.ctr-electronics.com/en/stable/index.html).
{% endhint %}


---

# 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/wcp-throughbore-by-cancoder-1-2-hex/overview-and-features.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.