> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/relaykeys/installation/checking-it-works.md).

# Checking it works

1. Open up something on the second computer that you can enter text into. E.g. Notes on the iPad, Notepad on Windows or Notes on a mac
2. On your server computer (the one with RelayKeys attached) run "RelayKeys" (search for it in your Windows search bar). Alternatively find it in `C:\Program Files(x86)\Ace Centre\RelayKeys\relaykeys-qt.exe`
3. With the window having focus - type into it. You should see the keystrokes appear on the second computer

## Using it with your AAC software

You can get going by using one of these example files that work with your AAC Software:

* [The Grid 3](/products/relaykeys/using-relaykeys/guides/grid3.md)
* [MindExpress](/products/relaykeys/using-relaykeys/guides/mindexpress.md)
* [Tobii Communicator](/products/relaykeys/using-relaykeys/guides/communicator.md)
* [Tobii Dynavox Snap](/products/relaykeys/using-relaykeys/guides/snap-corefirst.md)

When you are ready, [have a read of how to integrate the features you need](https://github.com/AceCentre/RelayKeys/blob/master/guides/basic-principles.html).

***

👍 You've successfully installed and setup RelayKeys! Now you may want to use the CLI or QT program. Read on to find out how these work.

😞 Got a problem? Dang! See our [troubleshooting](/products/relaykeys/troubleshooting.md) guide.


---

# 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://docs.acecentre.org.uk/products/relaykeys/installation/checking-it-works.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.