> For the complete documentation index, see [llms.txt](https://userguide.wlanpi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.wlanpi.com/hardware/wlan-pi-pro-eos/getting-started/front-panel-menu-system-fpms.md).

# Front Panel Menu System (FPMS)

{% hint style="success" %}
This is a 'homegrown' name, it came from the development team

FPMS refers to the screen & the buttons
{% endhint %}

### Display

1.5 inch Color OLED display

#### All the things it can display:

#### Header / top menu bar

* Time
* Internet status globe
* Bluetooth status
* Wireless interface status
* Battery status

#### Main Page

* Operating Mode
* Ethernet IP address
* Link connection speed
* Additional interface IP addresses
  * USB
  * Bluetooth

#### Footer

WLAN Pi hostname

### Buttons

You have 5x buttons at your disposal

* We think of this array as 4x navigational buttons up, down, left right
* Centre button is the 'enter action'

### What can I do with this FPMS?

* `System > About`
* `Battery`
* `Date / Time`
* `Summary`
* `Reboot`
* `Shutdown`


---

# 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://userguide.wlanpi.com/hardware/wlan-pi-pro-eos/getting-started/front-panel-menu-system-fpms.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.