> For the complete documentation index, see [llms.txt](https://docs.motion4sim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motion4sim.com/software/dashboard.md).
# Dashboard
The Dashboard is the control center — connect, monitor and configure your rig.
The **Dashboard** is the control center for your Motion4Sim rig. From here you connect to the controller, watch the live rig status, adjust gain and filters, and open the full rig configuration. It also launches the **Motionsystem** motion-cueing engine.
## What you can do here
| Area | Page |
| ------------------------------------------- | ---------------------------------------------------------------- |
| Install the app and connect the controller | [Installation & Connecting](/software/dashboard/installation.md) |
| Understand the main screen and switch skins | [Main Screen](/software/dashboard/main-screen.md) |
| Language, theme, skin, updates | [Settings (⚙)](/software/dashboard/settings.md) |
| Rig geometry, actuators, network, firmware… | [Configuration](/software/dashboard/configuration.md) |
{% hint style="info" %}
**Download:** the Dashboard installer is available at [m4s-service.motion4sim.com/m4sdashboard](https://m4s-service.motion4sim.com/m4sdashboard/download.php). See [Installation & Connecting](/software/dashboard/installation.md) for details.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.motion4sim.com/software/dashboard.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.
