> For the complete documentation index, see [llms.txt](https://cookiebunker.gitbook.io/cookiebunker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cookiebunker.gitbook.io/cookiebunker/dma/km-box/km-box-b+-setup.md).

# KM Box B+ Setup

{% stepper %}
{% step %}

### Connect the KM Box

* **Port #1** → Connect to your **second PC** using the included USB cable.
* **Port #2** → Connect to your **main PC** using the included USB cable.
* **Port #3 or #4** → Connect your **keyboard or mouse** (either port works).<br>

  <div align="left" data-with-frame="true"><figure><img src="/files/78803b9ee078e1b0d95dc5b41b6bf678a000eda2" alt="" width="375"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Find a Mouse to Emulate

1. Go to [**http://www.linux-usb.org/usb.ids**](http://www.linux-usb.org/usb.ids).
2. Browse the list to find the mouse you want your KM Box to mimic.
3. Note down its **Product ID (PID)** and **Vendor ID (VID)** for later use.
   {% endstep %}

{% step %}

### Prepare the KM Box Script

1. Connect your **KM Box** to your **second PC**.
2. Download and run [**`upycraft.exe`**](https://randomnerdtutorials.com/install-upycraft-ide-windows-pc-instructions/).
   * If a **"Font"** message appears, ignore it and proceed by clicking **Board** or **Serial** under the **Tools** menu.
3. In the script:
   * Locate the **dynamic PID and VID** command lines and `device.enable(1)`.
   * Remove the `#` from the start of these three lines.
   * *(See Picture #1 for before, and Picture #2 for after)*.
   * \#1

     <div align="left" data-with-frame="true"><figure><img src="/files/392aa23c6faf74c80f1ac8d975931e676108a33a" alt="" width="563"><figcaption></figcaption></figure></div>
   * \#2

     <div align="left" data-with-frame="true"><figure><img src="/files/546e4f1d45dafa5f27d12b1c9abfac7e0f218e1b" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Set Static PID & VID

1. Locate the static PID and VID values `(046d, c07d)` in the script.
2. Replace them with the **PID** and **VID** you noted in Step 2.
3. Remove the `#` comment symbol if present.
   {% endstep %}

{% step %}

### Save & Upload the Script

1. Press **Ctrl + S** to save changes.
2. In the **Tools** menu, click **Download and Run**.
   {% endstep %}

{% step %}

### Reboot the KM Box

1. Unplug both **blue USB cables** to power down the KM Box until the screen turns off.
2. Plug them back in.
3. Your main PC should now detect a **new mouse** and begin installing it, along with the updated **VID/PID**.
   {% endstep %}
   {% endstepper %}

***

### ✅ You're Done

{% hint style="success" %}
Your KM Box B+ is now setup and ready to use!
{% 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 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://cookiebunker.gitbook.io/cookiebunker/dma/km-box/km-box-b+-setup.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.