> 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/controller-and-firmware/how-the-system-works.md).

# How the System works

Here's the translated and formatted text for GitBook:

***

## System States and Operation

### System States

The Motion4Sim Controller system operates in multiple states:

1. **Controller Boot & Initialization**
2. **Start Menu**
3. **Homing**
4. **Transition to Online State**
5. **Motion State**
6. **Transition to Park**
7. **Shutdown**

### User Input and Control

The system can be controlled through various user input methods:

* **LCD Display with Encoder** – Directly on the controller or via a handheld device
* **Button Boxes** – External hardware controls
* **Software Commands** – Control through software-based commands
* **Web Interface** *(Planned)* – Future implementation for remote access

The operation and configuration via the **LCD display and encoder** are managed through a menu system built directly into the firmware.

{% content-ref url="/pages/NIHbkJmkEwbWwRDIVffv" %}
[Firmware Menusystem](/controller-and-firmware/how-the-system-works/firmware-menusystem.md)
{% endcontent-ref %}


---

# 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/controller-and-firmware/how-the-system-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.