> 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/codesys-hvac/hvac-knx-library/functionblocks/knx_read_data.md).

# KNX\_Read\_Data

## `KNX_Read_Data` (FB)

FUNCTION\_BLOCK KNX\_Read\_Data EXTENDS SlaveBasic

#### Überblick

Der KNX\_Read\_Data Funktionsbaustein dient zum Empfangen von KNX-Daten ohne spezifische DPT-Konvertierung. Er ist besonders nützlich für progressive Steuerungen, wie beispielsweise in der Beleuchtungssteuerung.

#### Eingänge

| Eingänge           | Initialwert | Beschreibung                  |
| ------------------ | ----------- | ----------------------------- |
| `byAdrGroup`       | *0*         | Gruppenadresse (0-255)        |
| `byAdrMiddleGroup` | *0*         | Mittlere Gruppenadresse (0-7) |
| `byAdrMainGroup`   | *0*         | Hauptgruppenadresse (0-31)    |

#### Ausgänge

* `abyDaten` (ARRAY\[0..38] OF BYTE): Empfangene Rohdaten

#### Verwendung

1. **Gruppenadresse konfigurieren**:
   * Setzen Sie `byAdrMainGroup` (0-31)
   * Setzen Sie `byAdrMiddleGroup` (0-7)
   * Setzen Sie `byAdrGroup` (0-255)
2. **Datenempfang**:
   * Der Baustein empfängt automatisch Daten, wenn sie an die konfigurierte Gruppenadresse gesendet werden.
   * Die empfangenen Daten werden im `abyDaten` Array gespeichert.
3. **Datenverarbeitung**:
   * Die empfangenen Daten im `abyDaten` Array können nach Bedarf weiterverarbeitet werden.
   * Da keine DPT-Konvertierung stattfindet, müssen Sie die Interpretation der Daten selbst vornehmen.

InOut:

| Scope       | Name                      | Type                   | Initial | Comment                                                                                            | Inherited from |
| ----------- | ------------------------- | ---------------------- | ------- | -------------------------------------------------------------------------------------------------- | -------------- |
| Input       | `itfKnxConnector`         | `IKnxConnector`        |         | <p>IMasterConnector interface input to register/unregister<br>the FB to the List on the Master</p> | SlaveBasic     |
| Input       | `xEnable`                 | `BOOL`                 | TRUE    |                                                                                                    | SlaveBasic     |
| Output      | `sPhysicallAddressDevice` | `STRING(15)`           |         |                                                                                                    | SlaveBasic     |
| Output      | `sGroupAddress`           | `STRING(15)`           |         |                                                                                                    | SlaveBasic     |
| Input Const | `byAdrGroup`              | `BYTE`                 | 0       | Groupaddress                                                                                       |                |
| Input Const | `byAdrMiddleGroup`        | `BYTE`                 | 0       | Middle-Group-Address                                                                               |                |
| Input Const | `byAdrMainGroup`          | `BYTE`                 | 0       | Main-Group-Adress                                                                                  |                |
| Output      | `abyDaten`                | ARRAY \[0..38] OF BYTE |         |                                                                                                    |                |


---

# 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/codesys-hvac/hvac-knx-library/functionblocks/knx_read_data.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.