Basic Documentation
Table Of Contents
- 1 About this document
- 2 Overview
- 3 Notes
- 4 Functions
- 4.1 Temperature control
- 4.2 Operating modes
- 4.3 Room temperature setpoints
- 4.4 Application overview
- 4.5 Power supply selection for RDG200KN
- 4.6 Additional functions
- 4.7 Control sequences
- 4.7.1 Sequence overview (setting via P001)
- 4.7.2 Application mode
- 4.7.3 2-pipe fan coil unit
- 4.7.4 2-pipe fan coil unit with electric heater
- 4.7.5 2-pipe fan coil unit with radiator or floor heating
- 4.7.6 2-stage heating and cooling
- 4.7.7 4-pipe fan coil unit
- 4.7.8 4-pipe fan coil unit with electric heater
- 4.7.9 Chilled/heated ceiling and radiator applications
- 4.7.10 Compressor applications
- 4.7.11 Applications with external AQR sensor or QMX room operator unit
- 4.7.12 Setpoints and sequences
- 4.8 Control outputs
- 4.9 Fan control
- 4.10 Multifunctional input, digital input
- 4.11 Handling system faults
- 4.12 KNX communications
- 4.12.1 S-Mode
- 4.12.2 Master/slave configuration in KNX S-Mode
- 4.12.3 LTE-Mode
- 4.12.4 Zone addressing in LTE-Mode (with Synco)
- 4.12.5 Master/slave configuration in LTE-Mode
- 4.12.6 Example of heating and cooling demand zones
- 4.12.7 Send heartbeat and receive timeout
- 4.12.8 Startup
- 4.12.9 Heating and cooling demand
- 4.12.10 Fault and alarms function on KNX
- 4.13 Communication objects
- 4.14 Communication objects (LTE-Mode)
- 4.15 Control parameters
- 5 Supported KNX tools
- 6 Connection
- 7 Technical data
- 8 Dimensions
- Index
Functions
Additional functions
4
A6V11545892_en--_b
65 | 170
4.6.8.2 Master/slave communication in LTE-Mode
The master thermostat shares the configuration with its slaves for the following:
● Room temperature and humidity value
● Operating mode
● Manual fan speed
● Current room setpoint and ChangeOverWaterStatus
If any of the above value is changed on the master, the change is synchronized to
all slaves within the same zone. For master/slave configuration, see Master/slave
configuration in LTE-Mode [➙ 113].
After initial power-on, without changes on the HMI, synchronization between
master and slave may take up to 15 min.
Every change on the master HMI, e.g. setpoint, op. mode, etc, is immediately sent
and updated on the slave.
A heartbeat function communicates between master and slave objects.
The function ensures that information is synchronized and correct between master
and slaves. See Send heartbeat and receive timeout [➙ 115].
4.6.8.3 Master/slave communication in KNX S-Mode
The master thermostat shares the following values with the slaves:
● Room temperature and humidity value
● Operating mode
● Manual fan speed
● Current room setpoint and ChangeOverWaterStatus
If any one of the above values changed on the master, the changes are
synchronized to all units within the group. See Master/slave configuration in KNX
S-Mode [➙ 108].
● Users change operating mode, comfort setpoint, control sequence, and manual
fan speed on the master thermostat. The data is then transmitted to the slaves.
● The changes are synchronized to all slaves.
S-Mode objects master
S-Mode objects slave
Setpoint:
[90]
[91]
[27]
Room temp: Current cooling
setpoint (send)
Room temp: Current heating
setpoint (send)
Room temp: Comfort setpoint abs
(send)
[93]
[92]
[26]
Room temp: Current cooling
setpoint (receive)
Room temp: Current heating
setpoint (receive)
Room temp: Comfort setpoint abs
(receive)
Room temperature:
[37]
Built-in room temperature value
[36]
External room temperature value
Room humidity:
[77]
Built-in room relative humidity value
[%r.h.]
[78]
External room relative humidity
value [% r.h.]
Operation mode:
[17]
Room operating mode: Status
[94]
Room operating mode: Status
(receive)
ChangeOverWater:
[95]
ChangeOverWater status
[96]
ChangeOverWater status
Fan speed:
[97]
[51]
Manual Fan command value (send)
FanStatus
[52]
[50]
Fan command value
FanManual
A heartbeat function communicates between master and slave objects.
The function ensures that information is synchronized and correct between master
and slaves. See Send heartbeat and receive timeout [➙ 115].
User case:
Note
Note










