> For the complete documentation index, see [llms.txt](https://help.gramctrl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gramctrl.com/readme.md).

# GRAM Help Desk

## **Howdy, Partner!**

Welcome to the GRAM Fam! This site will walk you through all the steps you need to get started playing on your new GRAM Digital Controller. Here, you can download the latest firmware, understand game modes, and learn all the features your GRAM comes with. We also have some helpful tips for troubleshooting, modifications, and repairs.\
\
Need more help, or want to chat with other GRAM players? It's highly recommended to join our [Discord Server](https://discord.gg/gramctrl) to connect with our lovely open-source community or open a support ticket.

### Which Controller do you have?

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GRAM SLIM</strong></td><td>21-button controller for Platform fighters.</td><td></td><td></td><td><a href="/getting-started/gram-slim.md">GRAM SLIM</a></td></tr><tr><td><strong>GRAM FGC</strong></td><td>14-button controller for traditional fighters.</td><td></td><td></td><td><a href="/getting-started/gram-fgc.md">GRAM FGC</a></td></tr></tbody></table>


---

# 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://help.gramctrl.com/readme.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.