Basic Documentation

253/332
Siemens Universal controllers RMU710B, RMU720B, RMU730B CE1P3150en
Building Technologies Heat demand 03.10.2011
25 Heat demand
The heat demand function collects heat requests.
These heat requests occur internally or come from consumers of a heat distribution
zone via the bus. The collected heat requests can be routed to a zone (basic type
C only) or further handled as a resulting setpoint condition (temperature request
signal, heating flow setpoint) in the form of a continuous or digital signal.
25.1 Activate block (basic types A, P, U)
S1 S1 S1
S2 S2
x
S2
S3
QYd
123
Controller
Supervision
Heat demand
To activate the "heat demand" function, the function must be assigned the
sequence with heating coil or heating surfaces configured.
Sequence 1 for controller 1 control the heat recovery
Sequence 2 for controller 1 control heating coil valve
Required setting: Controller 1: Sequence 2.
Main menu > Commissioning > Extra configuration > Aggregates > Heat demand >
Operating line Adjustable values / remarks
Controller 1 ---, Seq 1, Seq 2, Seq 3
Controller 2 ---, Seq 1, Seq 2
Controller 3 ---, Seq 1, Seq 2
Heat demand can be transmitted via communication when communication is
activated (see section 28 "Communication"). The heat distribution zone must be set
to generate a
heat demand signal that is processed by another device on KNX.
Main menu > Commissioning > Communication > Distribution zones >
Operating line Range Factory setting
Heat distribution zone 1…31 1
Heat demand is sent as a load signal (0...100% load) via communication. At the
same time, the primary controller receives information whether or not heat is called
for. This means that the primary controller is switched on and off depending on
demand.
25.2 Activate block (basic type C)
QY
d
Heat demand
For basic type C, the heat demand block together with the heating/cooling
changeover (section 27) is required.
Configuration example
Configuration
Heat distribution zone
Load signal