> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/controllers/test-a-controller.md).

# Test a controller

See every button and stick live, test rumble and lights, and recalibrate motion.

Open **Settings › Controllers**. Under **Test a controller** there's a row for every seated player. Press **A** on one to start testing it, and **A** again to stop.

While it's testing you see:

* both sticks and both triggers, moving live;
* every button, lit while you hold it (Select shows as **View** and Start as **Menu**);
* **Motion (°/s)**, how fast the controller is turning, and **Tilt (g)**, which way is down.

And you can try:

* **Rumble:** a short buzz.
* **Light:** flashes the controller's light, if it has one.
* **Recalibrate motion:** put the controller on a flat surface first. Kouch shows **Hold still…** for about a second.

If the controller can't do one of these, Kouch says **This controller can't do that right now.** Nobody seated? Connect a controller and press **A** on it.

## During a game

Hold **Select + Start** and choose **Controller tools** in the Quick Menu. **Rumble test**, **Recalibrate motion** and **Disconnect** act on the controller that opened the menu. **Disconnect** is a red button: hold **A** to confirm.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kouch.dev/controllers/test-a-controller.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.