> For the complete documentation index, see [llms.txt](https://8bitmods.gitbook.io/manuals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://8bitmods.gitbook.io/manuals/bitlink-dc-adapter/webui/bluetooth-mapping.md).
# Bluetooth gamepad mapping
On the adapter, the **Mapping** page sets which gamepad output each Dreamcast button drives in Bluetooth gamepad mode. In 2.4G and wired modes the dongle's mapping is used instead.
The built-in default
1. Pick an output from the list next to each Dreamcast button: gamepad buttons 1 to 16, or a D-pad direction. The change works straight away and is kept.
2. To keep this layout as a preset, select **Save as...**, enter a name of up to 23 characters and select **Save**.
Choose a preset from the list to load it, or **Built-in default** for the standard layout. **Revert** undoes your edits and **Delete** removes the loaded preset. The adapter holds up to 8 presets.
## Built-in default
| Dreamcast | Gamepad output |
| ------------ | ------------------ |
| A, B, X, Y | Buttons 1, 2, 3, 4 |
| Start | Button 8 |
| D-pad | D-pad (hat) |
| L trigger | Z axis |
| R trigger | Rz axis |
| Analog stick | X and Y axes |
## Notes
* The analog stick always drives the X and Y axes.
* A trigger drives an analog axis, or a button that presses past half travel.
* Two Dreamcast buttons set to the same output both press it. They are marked in amber.
* C, Z and D (Arcade Stick only) use buttons 9 to 11.
* Computers number buttons differently. Linux and Android read buttons 1 to 15 as A, B, C, X, Y, Z, L1, R1, L2, R2, Select, Start, Mode, L3, R3.
---
# 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://8bitmods.gitbook.io/manuals/bitlink-dc-adapter/webui/bluetooth-mapping.md?ask=&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.
