> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/mouse-and-keyboard/connect-and-configure.md).

# Connect & Configure

Get your mouse and keyboard working with the Cronus Zen™.

{% hint style="warning" %}
Once your mouse and keyboard are connected to the Cronus Zen™, they act as a controller. You will not be able to use them on your PC any more unless you switch them back manually.

Plan for a **second set** of mouse and keyboard, or a **USB-powered MK Switch** to toggle between PC and Zen.
{% endhint %}

{% stepper %}
{% step %}

#### Turn off scripts

Before connecting anything, press the right blue **Memory Slot** button on the Cronus Zen™ and cycle through until the Collective Minds logo appears on the OLED screen.

That means no GamePacks or scripts are active.
{% endstep %}

{% step %}

#### Connect your devices

| Port          | Device           |
| ------------- | ---------------- |
| **A1**        | Controller       |
| **A2**        | Keyboard         |
| **A3**        | Mouse            |
| **PROG USB**  | Cable to your PC |
| {% endstep %} |                  |

{% step %}

#### Check device detection

Open Zen Studio on your PC, go to the **Device** tab, and look under **Connected Devices**. Your mouse and keyboard should appear.

{% hint style="info" %}
A device shown with a question mark still works — it only means Zen Studio has no icon for that model.
{% endhint %}
{% endstep %}

{% step %}

#### Test the input

In Zen Studio, open **Tools → Device Monitor**.

| Test              | What you should see                                                      |
| ----------------- | ------------------------------------------------------------------------ |
| Move the mouse    | **RX / RY** values change — your mouse is read as right stick movement   |
| Press **W A S D** | **LX / LY** values change — your keyboard is read as left stick movement |
| Press **Space**   | Confirms additional mappings are working                                 |
| {% endstep %}     |                                                                          |
| {% endstepper %}  |                                                                          |


---

# 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://guide.cronuszen.com/mouse-and-keyboard/connect-and-configure.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.
