# THERMOKON\_WRF07\_TEMP\_HUM\_AO2V\_REV\_A\_H
## `THERMOKON_WRF07_TEMP_HUM_AO2V_REV_A_H` (FB)
`FUNCTION_BLOCK` THERMOKON\_WRF07\_TEMP\_HUM\_AO2V\_REV\_A\_H
### Representation
### General
> By the setpoint / parameter `eDeviceMode` currently only the formation of the room setpoint temperature (29.10.2024) `rSetpTemp` as well as the setpoint temperature offset `rOffset` is influenced.
> The configuration registers (R2 - R46) or coils (C0 - C6) are always set for operation of the WRF07 as a pure room operating device (i.e. without its own internal control).
> Setpoint / Parameter `rOffsetRange`: A change is transmitted immediately without error, but the new offset is only used after a cold start of the WRF07.
> This function block can be used for all device types except the variant `4DI` .
> Depending on the function code, only a certain maximum number of resources may be read/written:
> Read registers: <= 20 registers Write registers: <= 20 registers Read coils: <= 16 coils Write coils: <= 8 coils
> There is only one temperature sensor !!!
> **\* Device configuration \***
> **\* Thermokon - Configuration Software \***
> The configuration can be read and written independently of this function block using Thermokon's software ‘WRF07-RS485-MODBUS Version 1.7’. The recorded configuration data can be stored in a readable file and transferred to a new device.
> **\* Function block \***
> In this function block, the configuration is read (see function 1) and, if necessary, the parameters defined here are written again (function 2). Parameters not defined here remain unchanged. The default values according to the documentation can be restored by function 3.
> **\* Function 1 \***
> The current configuration of the device is stored in registers 0 - 46 or in coils 0 - 6.
> This is read a) once at restart b) once on each rising edge at the input `xUpdateConfigRead` c) cyclically (time interval `tTimeUpdateConfigRead`) d) before each write operation (see function 2)
> read (FC03, FC01) and stored in the arrays `_arwKonfiguration_0`, `_arwKonfiguration_1`, `_arwKonfiguration_2` and `arbyKonfiguration_3` stored. In addition, the selected outputs are updated.
> **\* Function 2 \***
> During operation, registers 2 - 46 or coils 0 - 6 are written a) once at restart b) on each change in value of the relevant parameters c) once on each rising edge at the input `xUpdateConfigWrite`
> written (FC16, FC15)(arrays `_arwKonfiguration_4`, `_arwKonfiguration_5`, `_arwKonfiguration_6` and `arbyKonfiguration_7`).
> This write access must not be cyclical, as the number of write accesses is limited (EEPROM).
> **\* Function 3 \***
> The device configuration cannot be reset to the factory state; in the arrays `_arwKonfiguration_8`, `_arwKonfiguration_9`, `_arwKonfiguration_10` and `_arbyKonfiguration_11` the default values are stored and can be loaded / written into the device via input `xResDefault` (rising edge) can be loaded into / written to the device.
> **\* Setpoints of the device \***
> **\* Thermokon - Configuration Software \***
> The setpoints can be read and written independently of this function block using Thermokon's software ‘WRF07-RS485-MODBUS Version 1.7’. The recorded setpoints can be stored in a readable file and transferred to a new device.
> **\* Function block \***
> In this function block, the setpoints are read (see function 1) and, if necessary, the setpoints defined here are written again (function 2). Setpoints not defined here remain unchanged.
> **\* Function 1 \***
> The current setpoints of the device are stored in registers 512 - 517 or in coils 256 - 264.
> These are a) once at restart b) once on each rising edge at the input `xUpdateActual` c) cyclically (time interval `tTimeUpdateActual`) d) before each write operation (see function 2)
> read (FC03, FC01) and stored in the arrays `_arwIstwerte_1`, `arbyIstwerte_2` and `arbyIstwerte_3` stored. In addition, the selected outputs are updated.
> **\* Function 2 \***
> During operation, registers 512 - 517 or coils 256+ - 264 are a) once at restart b) once on each rising edge at the input `xUpdateSetp` c) cyclically (time interval `tTimeUpdateSetp`) d) on each change in value of the relevant setpoints
> written (FC16, FC15)(arrays `_arwSollwerte_0`, `arbySollwerte_1` and `arbySollwerte_2`).
InOut:
| Scope | Name | Type | Initial | Comment |
| ----------- | ----------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) |
| Input | `byUnitId` | `BYTE` | 0 | Device address (1 .. 247) (1 .. 31 via DIP switch, 1 .. 247 via Modbus commands) |
| Input | `xUpdateActual` | `BOOL` | FALSE |
Updating the actual values (at every rising edge ) (range: operation)
Setpoint temperature - night setback (relative) (Address 19) ( important for forming the effective setpoint temperature rSetpTemp at eDeviceMode = INTERNAL\_REGULATIOM)
Setpoint temperature - deadband between heating and cooling operation (Address 20) (important for forming the effective setpoint temperature rSetpTemp at eDeviceMode = INTERNAL\_REGULATIOM)
Setpoint temperature - offset (Address 512) (important for the formation of the effective setpoint temperature rSetpTemp at eDeviceMode = INTERNAL\_REGULATIOM)
General operating mode of the device (ROOM\_CONTROL\_UNIT: device serves as RBG, INTERNAL\_REGULATION: setpoint formation / temperature control in the device)
Update interval for the processes influenced by the input xUpdateActual influenced
|
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/thermokon/thermokon_wrf07_temp_hum_ao2v_rev_a_h.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.