> 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/h1.m300/feldbus-protokolle/application.md). # Application Verwendung von Serial Ports in installierten Applications ## Application Mode: Funktionsweise & Nutzen Die seriellen Ports können den installierten [User-Applications](/hub/applications/available-apps.md) zugeordnet werden. So können beispielsweise die User-Application [CODESYS](/hub/applications/available-apps/codesys.md) oder der [HVAC Cloud Adapter](/hub/applications/available-apps/hvac-cloud-adapter.md) die seriellen Ports verwenden. #### Auswahl für Application Modus * Der serielle Port kann einer Application zugeordnet werden, wenn die Application gestoppt ist. * Wenn die Application läuft, kann der serielle Port nicht verändert werden. * Die Einstellungen des seriellen Ports, wie Baudrate etc., erfolgen in der gewählten Application.

Auswahl des seriellen Ports für eine installierte Application

#### Beispiel Application Modus 1.) Falls die Application nicht gestoppt ist muss diese unter **Applications** -> **Installed powerIO packages** gestoppt werden.

2.) Unter Serial Settings, den jeweiligen Port der Application zuordnen.

3.) Application erneut starten **Applications** -> **Installed powerIO packages**

4.) Port in Application verwenden. Der zugeordnete Port steht in der Application unter dem gleichen Gerätepfad zur Verfügung (z. B. `/dev/ttyPort2`).

Serial Port 2 in Application HVAC Cloud Adapter

--- # 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/h1.m300/feldbus-protokolle/application.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.