> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/powerio-r-system/en/applications/overview.md).

# Overview

{% hint style="info" %}
[To the applications download area](https://support.powerio.com/hub/downloads/en/user-applications/codesys.md)
{% endhint %}

## Overview

As **Applications** are referred to as software components, which can be installed on the powerIO® controller H1.M100 and on the powerIO® Box T1.B100.\
The **Applications** are installed via the web interface of the powerIO® controller H1.M100 or powerIO® Box T1.B100.

By splitting **Applications** and **Firmware** you, as a user, benefit from being able to flexibly install different versions and, among other things, expand your hardware with additional functions. This means that, for example, in addition to the CODESYS® installation, you can also install a Cloud Adapter and are thus (I)IoT-ready.

The **Applications** are constantly being expanded and updated.

{% hint style="info" %}
If you have a requirement that you need a specific **Application** need, please do not hesitate to let us know. We can then review the requirements for the system and your individual **Application** create.
{% 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://support.powerio.com/hub/powerio-r-system/en/applications/overview.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.
