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
KNX communications
4
116 | 170
A6V11545892_en--_b
Fixed times are specified as follows:
● Receive timeout: 31 minutes
● Send heartbeat: 15 minutes
Object [KNX obj. no.]
I/O
Minutes
Default value
Room operating mode:
Time switch [13]
Receive
31
Comfort
Application mode [48]
Receive
31
Auto
Heating/Cooling mode status
[46]
Receive
31
Heating
Individual zones can also be disabled (out of service) via control parameter if they
are not being used. In disabled zones, the LTE signal no longer sends periodically
and therefore reduces bus load.
4.12.8 Startup
The application is restarted after every reset, so that all the connected motorized
valve actuators are synchronized (see Control outputs [➙ 91]).
After a reset, it takes up to 5 minutes for all the connected room thermostats to
restart. This is designed to avoid overloading the mains power supply when
restarting. At the same time, it reduces the load on the KNX network, as not all
thermostats transmit data at the same time. The delay (T
WaitDevice
) is determined by
the thermostat's device address. The device starts to send after the delay.
4.12.9 Heating and cooling demand
Together with Synco, the heating and/or cooling demand from each room is
transmitted to the BACS to provide the required heating or cooling energy.
An example for LTE-Mode is described in Example of heating and cooling demand
zones [➙ 115].
In S-Mode, the current state signals of the control outputs are available.
4.12.10 Fault and alarms function on KNX
A fault is sent on the bus in the event of a fault occur (for example, digital fault
input, Dewpoint, communication configuration, etc.).
An RDG2..KN room thermostat monitors the bus and sends its fault, if the fault has
the highest alarm priority. This ensures that the management station does not miss
any alarms.
The alarm with the highest priority is displayed first and sent over the bus if alarms
occur at the same time.
Fault transmission is different in LTE-Mode and S-Mode:
S-Mode
LTE-Mode
Fault state
Alarm info (error code + internal
information)
Fault information (internal information)
Alarm text (default text can be edited
with ACS tool)
LTE-Mode/S-Mode
Reducing the bus load
Startup response
Startup delay
Heating output primary
Heating output secondary
Cooling output primary
Cooling output secondary