> 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/downloads/en/codesys-hvac-templates/template-start.md).

# Project template - Start empty

Download and changelog page for the project template "Start empty"

### Documentation

<a href="https://support.powerio.com/hub/codesys-hvac/en/codesys-projects/template-start.md" class="button secondary" data-icon="books">To the documentation</a>

### Current version

<details>

<summary>2.2.0.4 - CODESYS 3.5.21.2_C - <a href="https://dl.powerio.com/downloads/HVAC-Startprojekt-LEER-powerIO-(CDS3.5.21.2_C)-2.2.0.4.projectarchive" class="button primary" data-icon="arrow-down-to-line">Download</a></summary>

Release Date 21.08.2026

**New features and changes**

* Visu 'Start\_Meldungen': the color variable in the 'Test Alarm' button changed to PRG.SSK.xTest\_SM
* the two settings for alarm email sending added again on the Visu page Settings-Service-Settings
* visual adjustments on the Visu page Settings-Service-Settings
* GLT-Jump added as a variable. Configurable on the Visu page Settings-Service-Settings
* Value for library parameter MAX\_DATA\_STRING\_SIZE in the Library powerIO Json Library in the Library powerIOhw increased from 100 to 1000
* Adjustment to configuration file C
* Display triangle for current language removed on the Visu page 'Start', since the current language can no longer be read directly
* Object button: DisplayAutoHand replaced with DisplayAutoHandHint
* Frame added on the network page

</details>

***

### Older versions

<details>

<summary>2.2.0.1 - CODESYS 3.5.21.2 - <a href="https://dl.powerio.com/downloads/Startprojekt-LEER-powerIO-(CDS3.5.21.2_A)-2.2.0.1.projectarchive">Download</a></summary>

Release Date 19.01.2026

**New features and changes**

* Various changes and adjustments
* Template optimized and adapted for CODESYS version ≥ 3.5.21.2

</details>

<details>

<summary>2.1.0.5 - CODESYS 3.5.17.2 - <a href="https://dl.powerio.com/downloads/Startprojekt%20LEER%20powerIO(CDS%203.5.17.2_A)%202.1.0.5.projectarchive">Download</a></summary>

**New features and changes**

* Various changes and adjustments - as well as the latest libraries

</details>

<details>

<summary>2.0.1.0 - CODESYS 3.5.17.2 - <a href="https://dl.powerio.com/downloads/HVAC-Startprojekt-LEER-powerIO-(CDS3.5.17.2_A)-2.0.1.0.projectarchive">Download</a></summary>

**New features and changes**

* Updated to CODESYS version 3.5.17.2
* The Modbus IO Visu page was added under the menu item "SERVICE".

</details>

<details>

<summary>2.0.0.2 - CODESYS 3.5.14.0 - <a href="https://dl.powerio.com/downloads/HVAC-Startprojekt-LEER-powerIO-(CDS3.5.14.0)-2.0.0.2.projectarchive">Download</a></summary>

**New features and changes**

* Base project for CODESYS 3.5.14.0

</details>


---

# 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/downloads/en/codesys-hvac-templates/template-start.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.
