rxb (knx) applications library - fnc description of ... · pdf filerxb (knx) applications...

RXB (KNX) applications library

FNC Description of functions for FC-10, FC-11, FC-12

(FNC applications see document CM110672)

Supplementary documents

CM1Y9775 RXB Integration – S-Mode CM1Y9776 RXB / RXL Integration – Individual Addressing CM1Y9777 3rd Party Integration CM1Y9778 Synco Integration CM1Y9779 Working with ETS

CM110385en_07 08 Mar 2012 Building Technologies

2/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Contents 08 Mar 2012

Table of contents

1 Introduction ...................................................................................................6 1.1 Validity of the documentation ........................................................................6 1.2 Revision history.............................................................................................6 1.3 Copyright .......................................................................................................7 1.4 Quality assurance .........................................................................................7 1.5 Document use / request to the reader...........................................................8 1.6 Target audience, prerequisites......................................................................8 1.7 Bus supply for RXB controllers .....................................................................9 1.8 RXB Konnex controller communications.......................................................9 1.8.1 S-mode..........................................................................................................9 1.8.2 LTE mode....................................................................................................10 2 Definitions / Tools........................................................................................11 2.1 Signals and parameters (presentation) .......................................................11 2.2 Supported tools ...........................................................................................13 2.3 Parameter setting with ETS3 Professional..................................................13 2.4 Parameter setting in ACS............................................................................14 2.5 Parameter setting using the HandyTool ......................................................15 2.5.1 Operation of the HandyTool functions.........................................................16 2.5.2 "Limited" parameter setting using room unit QAX34.3 ................................16 2.5.3 "Extended" parameter setting using room unit QAX34.3 ............................18 2.5.4 Selection of the device address using room unit QAX34.3 .........................18 2.6 Upload/download parameters using room unit QAX34.3 ............................19 2.7 Test the periphery using room unit QAX34.3 ..............................................20 3 Select communication mode .......................................................................22 3.1 Zone addressing in LTE mode (in conjunction with Synco) .......................23 3.2 Geographical zone and time switch zone application example RXB

with RMB795...............................................................................................26 3.3 Implementation of application example.......................................................29 3.4 Heating and cooling demand zone..............................................................30 4 Applications, parameters.............................................................................31 4.1 Application selection ...................................................................................31 4.2 Parameter settings ......................................................................................32 5 Room operating modes...............................................................................33 5.1 Description ..................................................................................................33 5.2 Overview .....................................................................................................34 5.3 Determine the room operating mode in DESIGO (S-mode)........................35 5.3.1 Local control of room operating mode via a window contact .....................36 5.3.2 Central control of room operating mode via input from the Use

timeschedule ...............................................................................................37 5.3.3 Central and local control of room operating mode based on occupancy ....38 5.3.4 Central control of room operating mode via the Room operating mode

timeschedule ...............................................................................................41 5.3.5 Local control of room operating mode with a room unit ..............................41 5.3.6 Local control of room operating mode via the Temporary Comfort mode

input ............................................................................................................42

3/166


5.3.7 Effective room operating mode...................................................................43 5.3.8 DESIGO examples......................................................................................44 5.4 Determine the room operating mode with third-party products (S-mode)...47 5.4.1 Local control of room operating mode via the window contact input ..........48 5.4.2 Central control of room operating mode via the Room operating mode

timeschedule...............................................................................................49 5.4.3 Central control of room operating mode via the Use and Occupancy

timeschedules.............................................................................................50 5.4.4 Central and local control of room operating mode based on occupancy.... 50 5.4.5 Local control of room operating mode with a room unit .............................. 52 5.4.6 Local control of room operating mode via the Temporary Comfort mode

input ............................................................................................................53 5.4.7 Effective room operating mode...................................................................54 5.4.8 Third-party (S-mode) examples ..................................................................55 5.5 Determine the room operating mode with Synco (LTE mode)....................57 5.5.1 Local control of room operating mode via the window contact input ..........58 5.5.2 Central control of the room operating mode via Enable Comfort...............58 5.5.3 Central control of room operating mode via Room operating mode input .59 5.5.4 Local control of room operating mode via presence detector .....................60 5.5.5 Local control of room operating mode with a room unit .............................. 61 5.5.6 LTE-Mode Examples ..................................................................................62 5.6 Determine the room operating mode without a bus (stand-alone)..............64 5.6.1 Local control of room operating mode via the window contact input ..........65 5.6.2 Local control of room operating mode via a presence detector ..................65 5.6.3 Local control of room operating mode with a room unit .............................. 66 5.6.4 Stand-alone Example..................................................................................67 6 Setpoint calculation.....................................................................................69 6.1 Description..................................................................................................69 6.1.1 Bus output for current setpoints ..................................................................70 6.1.2 Bus output effective setpoints .....................................................................70 6.1.3 Bus outputs LTE mode ...............................................................................70 6.2 Set the setpoints with the tool .....................................................................71 6.3 Setpoint adjustment runtime .......................................................................72 6.4 Central setpoint shift ...................................................................................73 6.5 Local setpoint shift ......................................................................................74 7 Temperature measurement ........................................................................76 7.1 Room temperature measurement ...............................................................76 7.1.1 Local temperature sensor at PPS2 interface ..............................................76 7.1.2 Local temperature sensor at analog input ..................................................76 7.1.3 Averaging analog input & PPS2 interface...................................................77 7.1.4 Sensor correction........................................................................................78 7.1.5 Temperature sensor outputs on the Konnex bus........................................78 7.1.6 Temperature sensor input from Konnex bus...............................................79 7.2 Outside air temperature via Konnex bus (FNC10, FNC12, FNC18)........... 80 8 Control sequences......................................................................................81 8.1 Fan coils with valve control .........................................................................81 8.1.1 Four-pipe fan coils - With valve control.......................................................81 8.1.2 Two-pipe fan coils - With valve control .......................................................82 8.1.3 Heating/cooling output ................................................................................84 8.1.4 Actuator type selection ...............................................................................85 8.1.5 Values representing valve actuator positions .............................................89

4/166


8.1.6 Valve exercising feature..............................................................................91 8.1.7 Override valve actuators .............................................................................91 8.2 Fan coils with damper control .....................................................................92 8.2.1 Four-pipe fan coils with damper control (FNC20) .......................................92 8.2.2 Value representing damper actuator positions............................................93 8.2.3 Overriding the damper actuator ..................................................................94 8.3 Fan coils with an electric heating coil ..........................................................95 8.4 Fan coils with an electric reheater...............................................................95 8.4.1 4-pipe fan-coils with electric reheater..........................................................95 8.4.2 2-pipe fan-coils with electric reheater..........................................................96 8.4.3 The electric reheater ...................................................................................97 8.5 Fan-coils with LTHW radiator (FNC18) .....................................................100 8.5.1 Configuration and parameter setting.........................................................101 8.5.2 Position values for tediator valve actuators...............................................102 8.5.3 Heat demand.............................................................................................102 8.5.4 Radiator valve actuator override ...............................................................103 8.5.5 Downdraft compensation ..........................................................................103 8.6 Outside air damper fan coils ("Economizer", FNC10, FNC12)..................105 8.6.1 Configuration and parameterization ..........................................................106 8.6.2 Enabling of the function.............................................................................107 8.6.3 Position values for damper actuators........................................................108 8.6.4 Overriding the outside air damper.............................................................108 8.7 Room supply air cascade control (FNC08) ...............................................109 8.7.1 Parameterizing ..........................................................................................110 8.7.2 Supply air inputs / outputs.........................................................................111 9 Fan control ................................................................................................112 9.1 Description ................................................................................................112 9.2 Fan parameter setting ...............................................................................114 9.2.1 Fan speeds and control.............................................................................115 9.2.2 Minimum on time.......................................................................................116 9.2.3 Fan overrun time (switch-off delay) ...........................................................116 9.2.4 Periodic fan kick ........................................................................................116 10 Master/slave..............................................................................................118 10.1 S-mode......................................................................................................119 10.1.1 Window switch (S-Mode) ..........................................................................120 10.1.2 Presence detector (S-mode) .....................................................................120 10.2 LTE mode with zones................................................................................121 10.2.1 Window switch (LTE mode) ......................................................................122 10.2.2 Presence detector (LTE mode) .................................................................122 10.3 Peripheral functions ..................................................................................123 11 General and central functions ...................................................................124 11.1 Send heartbeat and receive timeouts .......................................................126 11.2 Digital inputs..............................................................................................127 11.3 Temporary Comfort mode .........................................................................127 11.4 Presence detector switch-on and switch-off delay ....................................127 11.5 Heating and cooling demand ....................................................................128 11.6 Heating/cooling signal output ....................................................................129 11.7 Special functions .......................................................................................129 11.8 Boost heating (Morning Warmup, 2) .........................................................130

5/166


11.9 Night purge (Night Purge, 4), (FNC10, FNC12)........................................131 11.10 Precooling (Precool, 5) .............................................................................132 11.11 Test mode (Test, 7)...................................................................................132 11.12 Emergency heating (Emergency Heat, 8).................................................133 11.13 Rapid ventilation (Fan only, 9) ..................................................................133 11.14 Free cooling (Freecool, 10).......................................................................134 11.15 Alarm.........................................................................................................135 11.15.1 S-mode .....................................................................................................135 11.15.2 LTE mode .................................................................................................136 11.16 Reset the setpoint shift .............................................................................136 11.17 Free inputs/outputs ...................................................................................137 11.17.1 Digital inputs on the KNX bus ...................................................................138 11.17.2 KNX signals on digital/analog outputs ......................................................138 11.17.3 Mapping the sensor B1 to the Konnex bus...............................................139 11.18 Software version .......................................................................................139 11.19 Device state ..............................................................................................139 12 Room unit .................................................................................................140 13 KNX information........................................................................................143 13.1 Reset and startup response......................................................................143 13.2 LED flashing pattern .................................................................................143 13.3 Startup delay.............................................................................................144 13.4 Bus load....................................................................................................144 13.5 S-mode communication objects for FNC ..................................................145 13.5.1 S-mode input communication objects.......................................................145 13.5.2 S-mode output communication objects.....................................................146 13.6 LTEmode communication objects.............................................................147 13.7 HandyTool parameters by number ...........................................................148 13.8 HandyTool parameters sorted alphabetically ...........................................150 13.9 HandyTool enumerations..........................................................................153 13.10 Data point type description .......................................................................154 14 FAQs.........................................................................................................156 15 Integrate RXB in DESIGO/Synco..............................................................159 15.1 Case 1: Integration into Synco..................................................................159 15.2 Case 2: Integration into DESIGO..............................................................160 15.3 Case 3: Display in DESIGO, with shared Synco time scheduler .............. 161 15.4 Case 4: Display in DESIGO/Synco, with shared Synco time scheduler ...162 15.5 Case 5: Display in DESIGO, and separate time schedulers.....................163 15.6 Case 6: Separate display, and separate time schedulers ........................164 15.7 Case 7: Separate display, and shared Synco time scheduler ..................165 16 Working with different tools.......................................................................166

6/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Introduction 08 Mar 2012

1 Introduction 1.1 Validity of the documentation

Devices with production date up to approx. December 2007

Devices with procuction date from approx. January 2008

RXB21.1/FC-10 Index A RXB21.1/FC-11 Index A RXB22.1/FC-12 Index A QAX34.3 Series A - C

RXB21.1/FC-10 Index B and higher RXB21.1/FC-11 Index B and higher RXB22.1/FC-12 Index B and higher QAX34.3 Series D and higher

– Documentation revisions _01 and _02 apply. – Use old device descriptions (for ACS) and old

product data (for ETS)!

– Documentation revisions _03 and higher apply. – Use new device descriptions (for ACS) and new

product data (for ETS)!

1.2 Revision history

CM110385en_07 08.03.2012 • 11.2 HandyTool Parameters 113, 114

CM110385en_06 15.09.2010 • 8.1.4 Electromechanic actuators, RXB21.1: Output Y3 not Y2 for Cooling

• 8.4.2 2-pipe fan-coils with electric reheater

• 9.1, 9.2.1 Prevent switching the fan off while el. re-heater is active

CM110385en_05 28.02.2009 • 7.1.3 Temperature averaging

• 8.5.5 Downdraft compensation

CM110385en_04 14.03.2008 • 5.3.3, 5.4.4 Presence detector

• 8.1.4 Offset in the case of mechanical actuators (3rd party)

• 10.1.3, 10.2.3 No dew point sensor in FNC

• 11.15.2 Alarm LTE: Alarm codes

• 13.9 Table "HandyTool enumerations"

CM110385en_03 30.11.2007 • 1 New section

• 1.7 Bus supply • 2.6 Parameter upload / download • 2.7 Periphery test • 5 Room operation mode • 6 Setpoint calculations • 7.1 Temperature measurement • 8.1.3 Heating/cooling output • 8.1.4 Actuator type selection • 8.1.6 Valve exercising feature • 8.5 Floor heating: the control parameters are not optimized. • 8.5.2 Downdraft compensation • 8.7 Room supply air cascade control (FNC08): figure • 9.2.1 Fan speeds and control • 10 Master/Slave (window switch, presence detector, dewpoint sensor) • 11.7 Disabling of the special functions • 11.12 Emergence heating • 11.17 Free inputs/outputs • 11.18,Software-version, 11.19 Device status • 13.1 Reset and startup response • 13.2 LED flashing pattern • 13.7, 13.8, 13.9 HandyTool parameters with page numbers and enumerations • 14 FAQ

7/166


CM110385en_02 20.09.2006 • New Section 1.3 • Moved note from 8.1.3 page 78 to 8.1.4 page 81 • Bus valve output heating/cooling actuator deleted (pages 78 and134) • 7.1.5 Konnex bus sensors: cyclic sending must be enabled • 8.1.4 page 81: deleted "Note!" • Pages 119 and 124: Rapid ventilation (Parameter 136) • 11.17: tables for free inputs/outputs • 13.6, 13.7: changes in parameter tables • Section 14: changes for slave window contact/presence detector contact • Section 16: new note

CM110385en_01 31.07.2006 First edition

1.3 Copyright

This document may be duplicated and distributed only with the express permission of Siemens, and may be passed only to authorized persons or companies with the required technical knowledge.

1.4 Quality assurance

These documents were prepared with great care. • The contents of all documents are checked at regular intervals. • Any corrections necessary are included in subsequent versions. • Documents are automatically amended as a consequence of modifications and

corrections to the products described. Please make sure that you are aware of the latest document revision date. If you find lack of clarity while using this document, or if you have any criticisms or suggestions, please contact your local point of contact in your nearest branch office. The addresses of the Siemens regional companies are available at www.siemens.com/sbt.

8/166


1.5 Document use / request to the reader

Before using our products, it is important that you read the documents supplied with or ordered at the same time as the products (equipment, applications, tools etc.) carefully and in full. We assume that persons using our products and documents are authorized and trained appropriately and have the technical knowledge required to use our products as intended. More information on the products and applications is available: • On the intranet (Siemens employees only) at

https://workspace.sbt.siemens.com/content/00001123/default.aspx • From the Siemens branch office near you www.siemens.com/sbt or from your

system supplier • From the support team at headquarters [email protected] if

there is no local point of contact Siemens assumes no liability to the extent allowed under the law for any losses resulting from a failure to comply with the aforementioned points or for the improper compliance of the same.

1.6 Target audience, prerequisites

This document assumes that users of the RXB Konnex controllers are familiar with the tools ETS3 Professional and/or Synco ACS and able to use them.

It also presupposes that these users are aware of the specific conditions associated with EIB/KNX.

In most countries, specific EIB/KNX know-how is transmitted through training centers certified by the EIBA (see www.eiba.com/ or www.konnex.org/).

For details concerning the Konnex bus see document CE1N3127.

For applications based on RXB in conjunction with Synco, please refer also to the Synco documentation:

• CE1N3121: Central Control Unit for use with RXB… room controllers • CE1P3127: Communication via Konnex bus

9/166


1.7 Bus supply for RXB controllers

RXB controllers can work without bus supply if the following conditions are adhered to:

• Parameterize only using the HandyTool (not with ETS3 or ACS). • No integration in a building automation and control system (e.g. DESIGO, Synco). • No changeover mode (sensor signal via bus). • No outdoor temperature via bus • No master/slave combinations. Otherwise, the Konnex bus, used by the RXB room controller for communication, requires a bus supply. Each controller consumes 5 mA. The supply has to be selected according to the number of controllers. We recommend the following products:

Manufacturer Type Designation Siemens Building Technologies ACX95.320/ALG Power supply 320 mA

Siemens Automation and Drives 5WG1 125-1AB01 Power supply 160 mA

5WG1 125-1AB11 Power supply 320 mA

5WG1 125-1AB21 Power supply 640 mA

1.8 RXB Konnex controller communications

RXB Konnex controllers support communication as per the Konnex specification.

Among the modes defined in this specification are the following:

• S-Mode = System mode

• LTE mode = Logical Tag Extended Mode This is a new mode which supports simpler engineering and is used in conjunction with Synco.

1.8.1 S-Mode

This mode corresponds to EIB communication. Connections are established via ETS3 Professional and group addresses.

This ensures a link to the existing EIB environment. For more details of this mode, refer to the EIB manual.

10/166


1.8.2 LTE mode

LTE mode was specifically designed to simplify engineering. Unlike with S-mode, there is no need to create the individual connections (group addresses) in the tool. The devices autonomously establish connections. In order to make this possible, the following circumstances are predefined:

• Every device or sub-device is located within a zone

• Every data point (input or output) is assigned to a zone

• Every data point (input or output) has a precisely defined "name".

Whenever an output and an input with the same "name" are located in the same zone, a connection is established automatically, as shown in the following diagram.

Controller

Valve

Sensor

Time switch zone 1. 1. 1

Outside temperature zone 3

Geogr. zone 2.5.1Geogr. zone 2.5.1

Heat distr zone 1

Cooling coil

Outside temperature

103

85Z

01e

n

Outside temperature

Cooling coil

Outside temperature zone 3

The following types of zone are defined:

• "Geographical" zones (Syntax: Apartment . Room . Subzone). The timeswitch zone is a "geographical" zone used for special purposes

• Outside temperature zones

• Heat distribution zones

For further details, refer to the Konnex specification.

Definitions

Types of zone

11/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Definitions / Tools 08 Mar 2012

2 Definitions / Tools 2.1 Signals and parameters (presentation)

The inputs, outputs and parameters of an application can be influenced in various ways. These are identified by the following symbols in this description of functions:

Parameters identified by this symbol are influenced by the room unit.

Parameters identified by this symbol are set using ETS3 Professional (EIB tool software).

The RXB Konnex controller parameters CANNOT be set with the ETS2 tool.

Parameters identified by this symbol are set with the ACS Service tool.

Parameters identified by this symbol are set with the HandyTool tool. Inputs and outputs identified by this symbol communicate with other KNX devices. They are called communication objects (CO). Graphical symbol for an S mode input communication object. Graphical symbol for an LTE input communication object. Graphical symbol for an S mode output communication object. Graphical symbol for an LTE output communication object. The communication objects of the RXB Konnex controllers work in part in S mode, in part in LTE mode and in part in both modes. These objects are described accordingly. The following table describes each communication object working in S-mode:

Time scheduler Use (Input communication object)

Flags

R W C T U

Type Receive timeout States

0 1 1 0 0 20.002

DPT_BuildingMode

yes 0 = In use 1 = Not in use 2 = Protection

(1) Communication object name

Flags: R Read W Write C Communication T Transmit U Update.

Type Konnex data type

Send heartbeat Yes = Cyclical send

Receive timeout Yes = Cyclical receive (timeout)

States or values Range of states or values which can be adopted by the send heartbeat communication object

A list of all S mode communication objects is located in section 13.5; a detailed description of the Konnex data types in section 0.

Room unit

ETS3 Professional

STOP Note!

ACS Service

HandyTool

KNXR

CO

S-mode communication objects

(1)

Key

Note

12/166


All communication objects which operate in LE-mode are described as follows:

Possible partner-function blocks 3)

Known partner devices 4)

HVACMode 1)

Timeswitch zone 2)

110 HVACS HVAC-Mode Scheduler

104 PMC Program to HVAC-Mode Conversion

Siemens Synco RM700

Key

1) Enter the name of the LTE communication object here.

2) Each LTE communication object is assigned to a zone. This is recorded here.

3) This is where suitable partner-function blocks are listed. They are described in the Konnex specification.

4) The devices listed here (manufacturer and type) are suitable partners for the communication object.

For a list of all LTE mode communication objects, refer to section 13.6. A detailed description of the Konnex data types in section 0. The left margin contains the symbol for the HandyTool next to a table containing the parameter number, short name and basic setting. The number has syntax *xxx, with xxx being a three-digit number.

HandyTool Parameter Short name Basic setting

*027 Setpoint additional heating 25.0°C

A list of the parameters by number and in alphabetical order is located in sections 13.7 and 13.8. A table of parameters with enumerations fort he HandyTool is shown in Section 13.9.

LTE-mode communication objects

Note

HandyTool

Note

13/166


2.2 Supported tools

The RXB Konnex controllers can be commissioned either with the Konnex tool ETS3 Professional, the Synco ACS Service too or the HandyTool.

• Be careful when using different tools. The following rule applies: Last one's right!

• If you use OCI700 as an interface, it is connected to the service plug of the controller or of the room unit. As long as the OCI700 is connected to the service plug, it must be supplied by the computer via the USB interface. Otherwise the LCD display of the room unit will turn dark and the controller will switch to addressing mode.

2.3 Parameter setting with ETS3 Professional

This manual does not describe how the physical address is defined. Refer to the EIB manual for more details. Open the project and select a device. To start the parameter setting, select Edit, Edit parameters.

STOP Note!

ETS3 Professional

14/166


2.4 Parameter setting in ACS

This manual does not describe how the physical address is defined. This information can be found in the ACS description. In the ACS Service program, select Plant, Open to open the plant. To start the parameter setting, select Applications, Parameter settings:

ACS Service

15/166


2.5 Parameter setting using the HandyTool

Tthe QAX34.3 room unit contains the function "HandyTool" allowing you to parameterize the RXB room controllers (from version 2.36). The following settings are possible in the room controllers:

• Parameter • Physical address • Zones Group addresses (bindings) cannot be assigned. This must be carried out in ETS. In addition to its room unit functionality, this device also allows for parameterizing the room controllers.

If the room controller was previously programmed (via ETS3, ACS or HandyTool). – Physical address – Zones (if in LTE mode) – Setpoints – Master/slave settings – All parameters. The parameter numbers and the functions are described in the sections below.

HandyTool

QAX34.3 room unit

"Limited" parameter setting

"Extended" parameter setting

Parameter

16/166


2.5.1 Operation of the HandyTool functions

Function of the buttons

1038

5Z7

0

+ = count/move up

– = count/move down

> = Escape (quit without acknowledgement)

< = Enter (Confirm)

Display • Parameter position e.g. P006 • Value to be adjusted e.g. 22.5 (a temperature)

or 250 (e.g. a particular actuator type) After modification of certain parameters (e.g. *063 Actuator type), the controller will perform a restart.

2.5.2 "Limited" parameter setting using room unit QAX34.3

Start parameter setting mode

• Press buttons < , > and – simultaneously for 2 s until the display goes dark • Release the buttons • Press – two times shortly

0 for Mode 0 is now displayed. Use buttons + and / or – to select between the following modes:

• 0 = Normal mode (normal room unit functions)

• 2 = Display mode: The parameters are displayed with prefix "d" (e.g. d015). +/– allows for finding the number and pressing < (Enter) confirms it. The corresponding value is displayed. Press < (Enter) or > (Escape) to return to the list.

• 3 = Parameter mode Some parameters (see below) can be set. They are displayed with prefix "P" +/– allows for finding the number and pressing < (Enter) confirms it. The corresponding value is displayed. +/– allows for modifying the value and pressing < (Enter) confirms it. > (Escape) returns to list without changing anything. Pressing Escape one more time opens the list with the modes. Pressing Escape a third time returns to the normal mode (room unit).

The parameter numbers are located in sections 13.7 and 13.8 as well as in the sections where the functions are described. A table of parameters with enumerations fort he HandyTool is shown in Section 13.9.

Restart after important parameter changes

Note

17/166


P001 Physical address (Area) P002 Physical address (Line) P003 Physical address (Device address) P008 Geographical zone (Apartment) (if LTE is preset) P009 Geographical zone (Room) (if LTE is preset) P010 Geographical zone (Subzone) (if LTE is preset) P011 Timeswitch zone (Apartment) (if LTE is preset) P012 Timeswitch zone (Room) (if LTE is preset) P013 Timeswitch zone (Subzone) (if LTE is preset) P014 Heat distr. zone heating coil (if LTE is preset) P015 Refr. distr. zone cooling coil (if LTE is preset) P016 Heat distr. zone heating surface (if LTE is preset) P018 Outside air temp zone (if LTE is preset) P021 Master/Slave P023 Master/Slave zone (group) (if LTE is preset) P031 Comfort cooling setpoint P032 Precomfort heating setpoint P033 Precomfort cooling setpoint P034 Economy heating setpoint P035 Economy cooling setpoint P036 Economy heating setpoint P038 Min supply air temperature P039 Max supply air temperature P240 Device state

Adjustable parameters (Parameter mode)

18/166


2.5.3 "Extended" parameter setting using room unit QAX34.3

This parameter setting also allows for adjusting critical values. In the worst case, this may destroy a device (controller / fan coil / actuators or other plant parts). Start parameter setting mode

• Press buttons < , > and – simultaneously for 2 s until the display goes dark • Release buttons • Press – two times shortly • Press + and – simultaneously for approx. 2s display goes dark • Press + two times shortly

0 for Mode 0 is now displayed. Use buttons + and / or – to select between the following modes:

• 0 = Normal mode (normal room unit functions) • 1 = Test mode (see 2.7) • 2 = Display mode: (see above) • 3 = Parameter mode: (see above) • 4 = Upload (see 2.6) • 5 = Download (see 2.6) • 6 = Service mode:

All parameters can be set. They are displayed with prefix "S". +/– allows for finding the number and pressing < (Enter) confirms it. The corresponding value is displayed. +/– allows for modifying the value and pressing < (Enter) confirms it. > (Escape) returns to list without changing anything. Pressing Escape one more time opens the list with the modes. Pressing Escape a third time returns to the normal mode (room unit).

The parameter numbers are located in sections 13.7 and 13.8 as well as in the sections where the functions are described. A table of parameters with enumerations fort he HandyTool is shown in Section 13.9.

2.5.4 Selection of the device address using room unit QAX34.3

The device address is defined in parameters *001, *002 and *003. *001 can be set to a value in the range 0 … 15 *002 can be set to a value in the range 0 … 15 *003 can be set to a value in the range 1 … 255 e.g. 0.2.27 Each address may occur once only in a given plant.

STOP Caution

Note

19/166


2.6 Upload/download parameters using room unit QAX34.3

This function requires a QAX34.3 with index D or higher!

The HandyTool can save 5 different controller parameter sets. These are uploaded from a fully parameterized controller using the Upload function. Download allows for transferring such a data set to one or several controllers (prerequisite: same controller type). The address, and for LTE, the zones must be adjusted (see ). Download allows for changing also critical values. As a worst case scenario, components (controllers/actuators or other plant parts) may be destroyed. Start parameterization mode:

• Press buttons < , > and – simultaneously for about 2 s until the display turns dark. • Release the buttons. • Press button – twice briefly. • Press buttons + and – simultaneously for approx. 2s The display goes dark. • Press button + twice briefly. The display now shows 0 (mode 0).

Use + and / or – to choose between the following modes:

• 0 = Normal mode (normal room unit functions). • 1 = Test mode (see 2.7). • 2 = Display mode (see 2.5.2). • 3 = Parameterization mode (see 2.5.2 ). • 4 = Uploading • 5 = Download • 6 = Service mode. If 4 or 5 is displayed, this mode can be selected via < (Enter). The storage number (c1) is displayed and can be changed via + / – . Select the desired storage (1 .. 5) via < (Enter).

• If storage is empty, upload begins and the display flashes. OK is displayed after successful upload.

• If the storage is full, "dEL" for "Delete?" is displayed. Pressing <(Enter) at this time overwrites the existing set. If you press > (Escape), the storage number which you can change via + / – is displayed.

• If the parameter set does not match the connected controller, error message "Err" is displayed. Press > (Escape) to return to the storage number and select a different number.

• If the parameter set matches the connected controller, start download (display flashes).

• If connected successfully, "P1" is displayed (see 2.5.2).

STOP Caution!

Uploading

Download

20/166


2.7 Test the periphery using room unit QAX34.3

This function requires a QAX34.3 with index D or higher!

The HandyTool allows you to test the connected field devices (sensors, actuators). This works only for the controller with the connected HandyTool; it does not work in master/slave mode.

An application must be selected and fully parameterized in the controller (address and zones can contain default values). Start parameterization mode:

• Press buttons < , > and – simultaneously for about 2 s until the display turns dark. • Release the buttons. • Press button – twice briefly. • Press buttons + and – simultaneously for approx. 2s The display goes dark. • Press button + twice briefly. The display now shows 0 (mode 0).

Use + and / or – to choose between the following modes:

• 0 = Normal mode (normal room unit functions). • 1 = Test mode • 2 = Display mode (see 2.5.2). • 3 = Parameterization mode (see 2.5.2 • 4 = Upload (see 2.6). • 5 = Download (see 2.6). • 6 = Service mode. The following positions can be selected depending on the type of parameterization. They are displayed with prefix "T". The list shows all theoretically possible positions. However, only positions that are available for selection based on the type of parameterization are displayed.

Theoretically possible positions for periphery testing:

T 01 Sensor input B1 9) Value of B1 in °C.

T 11 Digital input D1 9) True state of the contact at D1 (0 = open; 1 = closed).

T 12 Digital input D2 9) True state of the contact at D2 (0 = open; 1 = closed).

T 21 Heating valve 1) 2) 7) 8)

By considering the configuration (proportional; 100 = 100% pos. signal). (Also applies to damper in FNC20).

T 22 Cooling valve 1) 2) 7) 8)

By considering the configuration (proportional; 100 = 100% pos. signal). (Also applies to damper in FNC20).

T 23 El. Heating register 3)

7) Pulse to the electric register (value > 0 10 s pulse).

T 25 Heating surface 1) 4) 7) By considering the configuration (proportional; 100 = 100% pos. signal).

T 27 Damper 1) 4) 7) By considering the configuration (proportional; 100 = 100% pos. signal).

T 31 Fan relay 6) Speed control (%-value converted to speeds).

T 41 Relay Q14 6) (0 = Relay deenergized; 1 = energized).



Prerequisite

21/166


T 51 Triac Y1 6) (0 = Triac disabled; 1 = enabled).




1) Considering the configuration means:

– For thermal actuators, the output is clocked 1:1 during the first 400 s, then as per the % entry.

– Motorized actuators open at 100% 1.5 times the runtime, and close at 0% 1.5 times the runtime.

2) T21 and T22 have the same effect in changeover applications. 3) Only for RXB22.1/FC-12

If a digital input is used by a safety thermostat, the thermostat is considered. 4) Only for RXB21.1/FC-11 and RXB24.1/CC-02. 6) If not used by the application. 7) Only the I/Os of the controller and no bus actuators are controlled in test mode. 8) For FNC20, the different damper runtimes for heatin/cooling are not considered; for

test mode, the sum of the times are halfed 9) Values are correct when read, but will not automatically be updated.

The positions can be selected with < (Enter).

• The inputs are displayed • Outputs can be set via < (Enter) and + / –. To exit test mode, press >- (Escape) 2 - 3 times (depending on the situation). If no further button is pressed for 5 minutes, the controller automatically reassumes Normal mode and all physical outputs are switched back.

Monitor and operate

Exit test mode

22/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Select communication mode 08 Mar 2012

3 Select communication mode

As stated in section 1, the RXB Konnex room controllers operate either in S-mode or LTE mode. They are used in S-mode when networked with the DESIGO building automation and control system, and in LTE mode with the Synco system. The factory setting of all controllers and the basic setting of the tools is 0 = S-Mode. This minimizes the bus load. Exception: ACS Service changes the setting immediately to 1 = LTE + S. The ETS3 Professional is used in DESIGO networks. It can be used for operation in

– S-mode – LTE-mode and S-mode

The Send heartbeat and Receive timeout are described in Section 11.1.

Note

ETS3 Professional

23/166


In a Synco network the ACS Service tool is used. This has access to LTE mode only.

HandyTool Setting Mode

*006 communication mode 0 S-Mode 1 LTE- and S-Mode

3.1 Zone addressing in LTE mode (in conjunction with Synco)

This section applies only to LTE mode.

In cases where RXB Konnex controllers are used in LTE mode (e.g. in conjunction with Synco) zone addresses need to be allocated. These must be defined together with the Synco devices at the planning stage.

The zones to be defined are as follows:

Geographical zone (Apartment . Room Subzone) Apartment = ---, 1...126 Room = ---, 0...63 Subzone =---, 0...15

Zone in which an RXB Konnex controller is physically located. Other room-specific devices may also be located in this zone.

The designations "Apartment, Room and Subzone do not need to be taken literally. For example, Apartment can be used to refer to a group of rooms, floor or section of a building. "Room", however, really does refer to a room. Subzone is unlikely to be used much for HVAC devices – it is more relevant to other disciplines, such as lighting (keep the setting 1).

Timeswitch zone

(Apartment . Room Subzone) Apartment = ---, 1...126 Room = ---, 0...63 Subzone =---, 0...15

This zone has the same structure as the geographical zone. It indicates the source of the time schedule for the RXB Konnex controllers. The same zone must also contain a device (e.g. a Synco RMx7xx or RMB795) to deliver the time schedule.

In a Synco network, "Room" and "Subzone" must always be set to 1.

Heat distribution zone heating coil

Zone = ---, 1...31

Information related specifically to the hot water system in heating coils (heating registers) is exchanged within this zone. The zone also includes a Synco device to process the information (e.g. RMH7xx or RMU7xx with changeover).

Heat distribution zone heating surface (radiator)

Zone = ---, 1...31

Information related specifically to the hot water system of a radiator is exchanged within this zone (e.g. heating demand). This zone also includes a Synco device to process the information (e.g. RMH7xx or RMB7xx).

ACS Service

24/166


Refr. distribution zone cooling coil

Zone = ---, 1...31

Information related specifically to the chilled water system is exchanged within this zone (e.g. cooling demand). This zone also includes a Synco device to process the information (e.g. RMU7xx).

Outside air temperature zone

Zone = ---, 1...31

The outside air temperature (all Synco devices of series 700) is exchanged in this zone.

Master/slave zone

(Apartment . Room Subzone) Apartment = ---, 1...126 Room = ---, 0...63 Subzone =---, 0...15

In cases where RXB controllers are to be operated in master/slave mode, a master/slave zone must also be defined. For the master, it is usual to enter the "geographical" zone of the master. The same master/slave zone is used for the slave as for the master.

See also "Master/slave", page 118.

Select Communication.

ETS3 Professional

25/166


The zones are defined under Communication.

Individual zones can also be disabled via "Command" if they are not being used. This has the advantage of reducing the load on the bus.

HandyTool See Parameters in the last column of the table below

Short description Basic setting Parameter

Geographical zone (apartment) – 1 (out of service) *008

Geographical zone (room) 1 *009

Geographical zone (subzone) 1 *010

Time switch zone (apartment) 1 *011

Time switch zone (room) 1 *012

Time switch zone (subzone) 1 *013

Heat distr zone heating coil – 1 (out of service) *014

Heat distr zone cooling coil – 1 (out of service) *015

Heat distr zone heating surface – 1 (out of service) *016

Outside temperature zone 1 *018

• Value 0 means broadcast and is therefore prohibited. • If in the Geogr. zone or in the Time switch zone one of the values is = –1, the entire

zone is "Out of service".

ACS Professional

Reducing the bus load

Notes

26/166


3.2 Geographical zone and time switch zone application example RXB with RMB795

To explain the philosophy of the room group, we use the following example.

We assume to have a building with 3 floors accommodating a number of companies. The 2 following companies are located on the third floor: – Sport Ltd with a conference room and 2 offices – Logistics Ltd with 6 offices and 1 conference room

103

85Z

02

Each of the 2 companies wants to operate its room groups according to different operating modes, that is, with own – time programs – setpoints – fire and smoke extraction functions

The following floor plan shows usage of the rooms on the third floor by Logistics Ltd and Sport Ltd:

D: 101G: 4.1.1

D: 102G: 4.2.1

D: 103G: 3.1.1

D: 104G: 3.2.1

D: 105G: 3.3.1

D: 106G: 3.4.1

D: 107G: 3.5.1

D: 108G: 3.6.1

D: 109G: 3.7.1

D: 110G: 2.1.1

D: 111G: 2.2.1

D: 112G: 2.3.1

D: 113G: 2.4.1

D: 114G: 1.1.1

RMB795

301 302 303

304

305

306307

308

309

Logistics Ltd

Sport Ltd

103

85Z

03e

n

Office

Conferenceroom

Conference room Reception Office

OfficeOffice

Office

Office

D = device address, G = geographical zone (Apartment.Room.Subzone)

Subdivision of building

User requirements / operating modes

Floor plan of floor 3

Legend

27/166


For implementation of the application example, we focus on the floor plan of Sport Ltd. Due to company needs, a subdivision into 2 room groups or 2 “geographical zones (apartment)” is made: – Conference room (room group 1) – All the other rooms are offices (room group 2) The fan coils, all of which are equipped with RXB room controllers, are already shown on the floor plan, and the appropriate assignments by means of addresses have been made:

D: 110G: 2.1.1

D: 111G: 2.2.1

D: 112G: 2.3.1

D: 113G: 2.4.1

D: 114G: 1.1.1

RMB795309

308

307

x x x x x

Q Q

x x x

1 2

Raumgruppe 2

x x x x x

Q Q

x x x

1 2

Room group 1

SA EA

RelaySetpoint prio

EnableConference

Sport Ltd

103

85Z

04e

n

Room group 2 RelaySetpoint prio

SA EAEnableOffice

Office

Conferenceroom

Office

D = device address, G = geographical zone (Apartment.Room.Subzone)

The combination of several groups to 1 room group is made on the KNX bus by addressing the "Geographical zone". This address consists of 3 components:

Geographical zone: Apartment.Room.Subzone (e.g. 2.1.1)

A geographical zone must be assigned to: – Each RXB room controller – Each room group in the RMB795 central control unit All devices which, together, shall form one room group must be assigned the same apartment number.

Sport Ltd uses 2 room groups

Legend

Definition of room group

Important

28/166


On the RMB795 central control unit, only the room group, that is, the "Geographical zone (apartment)" can be set.

The room and the subzone use a fixed assignment (Room = 1, Subzone = 1).

This means that for setting a room group on the central control unit, following applies: Room group = geographical zone (apartment.1.1).

The RXB room controllers offer the following setting choices: – Geographical zone (apartment) – Geographical zone (room) – Geographical zone (subzone)

On HVAC applications using RXB… room controllers, it is only the "Geographical zone (apartment)" and the "Geographical zone (room)" that should be used.

Extension of addressing by the “Geographical zone (room) " leads to room control with RXB room controllers. This offers individual operational interventions (from an operator unit or the central control unit via bus), such as room setpoint readjustments from any of the rooms or devices.

The "Geographical zone (room)“ can be subdivided; for that, the RXB room controller offers the "Geographical zone (subzone). This subzone could be for use in plant where lighting conditions shall be taken into consideration if, for example, a "Geographical zone (room)" shall be divided into the 2 subzones “Lighting window side” and “Lighting corridor side”. For HVAC applications, the preset subzone = 1 should be left unchanged.

Suffixes (apartment), (room) and (subzone) are defined by Konnex, whereby (apartment) has nothing to do with a living space or an apartment in the proper sense.

Each KNX user requires an individual device address – on the floor plan of the preceding page shown as D:11x. The device addresses in our example were assigned in accordance with the bus’ topology.

Settings on the central control unit

Settings on the room controllers

Significance of subzone

Significance of suffixes

The device address

29/166


3.3 Implementation of application example

Using the "C3127_Planning and Commissioning Report, Communication Synco 700", the plant and the required communication settings can be represented in an easy-to-understand way. Proceed as follows:

1. Enter general information, such as plant name, device names, device types, applications, etc.

2. Transfer the device addresses of all bus users and the basic settings of communication from the floor plan.

3. Enter the "Geographical zone addresses" in agreement with the group formations made.

The following illustration shows the completed report for the plant of Sport Ltd:

Possible settings RMU RMH RMK OZW RMB RXB QAW 1 2 3 4 5 6 7

Plant Sport Ltd Sport Ltd Sport Ltd Sport Ltd Sport Ltd Sport Ltd Sport Ltd

Room number 309 307 308 308 308

Device name X X X - X X - Reception Conference Reception Office Office Office Office

Device typeRMU

7..RMH, RMZ

RMKOZW 771...

RMB 795

RXB ....

QAW 740

RMB795 RXB.. RMB795 [2] RXB.. RXB.. RXB.. RXB..

Plant type X X X - X X - B FC03 FC03 FC03 FC03 FC03

KNX-ID (Example ID: 00FD000016D5) X X X X X X X

Area [ 0...15 ] . Line [ 1; 2...15 ] . Device address [1..253;255]

X X X X X X X 0.2.10 0.2.114 0.2.110 0.2.111 0.2.112 0.2.113

Decentral bus power supply [ Off, On ] X X X - X - - Aus

Clock time operation [ Autonomous, Slave, Master ] X X X X X - - Autonom

Remote setting chlock slave [ No, Yes ] X X X X X - - Nein

Remote reset of fault [ No, Yes ] X X X - X - - Nein

Geographical zone (Apartment.Room.Subzone) (A.R.S) [ 1...126 ].[ 1...63 ]. [1]

X2 2X X - 10X X.X.1 X 1.1.1 1.1.1 2.1.1 2.1.1 2.2.1 2.3.1 2.4.1

(with own room sensor) X1 2X X - - X X X ---- X X X

Time switch operation [ Autonomous, Slave, Master ] X1 2X X - - - -

Time switch slave (apartment) [ 1...126 ] . 1 . 1 X1 2X X - - X.1.1 - 1.1.1 2.1.1 2.1.1 2.1.1 2.1.1

Temperature control [ Master, Slave ] - - - - - X - Master Master Master Master Master

* Control strategy [ Caskade, Constant, Alternating ] X4 - - - - - -

** Combination of room control [ Master, Slave external setpoint , Slave internal setpoint ]

- 2X X - - - -

Room group (name) - - - - 10X - - Conference Office

QAW operation zone (apartment) [ ---,1...126 ] . 1 . 1 - - - - 10X - -

Information

Room / Room group

Basic settings

Room group ConferenceApartment = 1

Room group OfficeApartment = 2

1

2

3

In agreement with the list created, the settings of the data points with the same names are to be made on the devices during commissioning.

Procedure for engineering

Example Sport Ltd

Implementation with commissioning

30/166


3.4 Heating and cooling demand zone

The building described above is equipped with Synco control equipment on the generation side.

RMH760 RMH760 RMB795

Konnex TP1

RXB...RXB...RXB...

T

T

T T

1

2

103

85Z

05e

n

Heat requistion

Heat demand

Heat distr zone 1

Heat source

Controller 1 Controller 2 Controller 3 Controller 4 Controller 5 Controller 6

Controller 1 Controller 2 Controller 3 Controller 4 Controller 5 Controller 6

Heating circuitfan coil

Fan coilroom A

Fan coilroom B

Fan coilroom C

DHW heating

Heat demandHeat demand

Heat demand

Heat demand

Heat requistion

Heat distr zone source side: 1

Heat distr zone 2 Heat distr zone 2 Heat distr zone 2 Heat distr zone 2

Setting values

In the case of a typical application, the individual RXB room controllers - when used with the RMB central control unit - signal their heat demand directly to the primary controller (in the above example to the RMH760).

(1) and (2) designate the numbers of the distribution zone.

• This type of application can analogously be applied to refrigeration distribution zones.

• If no 2-pipe fan coil is used, heat and refrigeration demand signals are sent simultaneously to the primary plant.

Explanation relating to the illustration

Notes

31/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Applications, parameters 08 Mar 2012

4 Applications, parameters 4.1 Application selection

Most of the RXB Konnex controllers store a number of software applications (e.g. RXB22.1/FC-12 with FNC03 and FNC05).

The tool is used to select the required application. ETS3 Professional and ACS differ greatly in this regard. The tool displays all applications as "devices". The required application is defined by adding a "device".

Select Engineering, Edit, Add device, then select one or several devices in the Product Finder and insert them in the line.

Alternatively: Select View, Open catalog. Select one or several devices, copy and insert them in the line.

ETS3 Professional

32/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Applications, parameters 08 Mar 2012

The application can be selected under Commissioning.

HandyTool Setting Application

*005 Plant type 1 FNC02 (FC-10) 2 FNC04 (FC-10) 3 FNC08 (FC-10) 4 FNC20 (FC-10)

1 FNC10 (FC-11) 2 FNC12 (FC-11) 3 FNC18 (FC-11)

1 FNC03 (FC-12) 2 FNC05 (FC-12)

4.2 Parameter settings

The following chapters describe how to set the parameters, which differs only slightly among the two PC tools. Only the display differs.

ACS Service

33/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Room operating modes 08 Mar 2012

5 Room operating modes 5.1 Description

The room operating modes available with DESIGO RXB are Comfort, Precomfort, Economy and Protection. In addition, there is a frost protection limit, at which, for example, an alarm can be triggered. Each room operating mode has separately adjustable heating and cooling setpoints.

Heating Cooling Y [%]

100

0 TR

103

85D

01

Comfort Precomfort Economy Protection Frost limit

Y Output signal (valve or damper actuator) TR Room temperature

Comfort is the room operating mode in an occupied room. In this mode, the room temperature is within the comfort range. The room controller operates in the heating or cooling sequence with the resulting Comfort setpoints. In Precomfort mode (in a vacant room), the controller operates with setpoints slightly below the Comfort setpoint in heating mode, and slightly above the Comfort setpoint in cooling mode.

In rooms that are unoccupied for any significant length of time (e.g. night setback based on a time scheduler (see pages 37, 49, and 59), the supply of energy to the room can be reduced substantially. In Economy mode, the controller operates with a setpoint slightly below the Precomfort setpoint in heating mode, and slightly above the Precomfort setpoint in cooling mode. If the building is unoccupied over a long period of time (e.g. holidays) the temperature setpoints can be reduced (or, in the case of cooling, raised) so that only sufficient heating or cooling energy is provided to protect the building fabric and its contents. If the room temperature or return air temperature falls below the Frost limit, an alarm is initiated for further processing in the building automation and control system. The room controller will continue to operate at the relevant setpoint (e.g. Protection, Economy, etc.). The alarm threshold in the controller is a fixed 5°C. In the case of applications incorporating an outside air damper, the value can be preset in the range 2 … 10°C.

Comfort

Precomfort

Economy

Protection

Frost limit

34/166


5.2 Overview

Sec

tio

n 5

.3

Sec

tio

n 5

.4

S

ecti

on

5.5

Sec

tio

n 5

.6

PP

S2

S

Pre

sen

ce d

etec

tor

Ro

om

un

it

Oc

cu

pan

cy

Bu

ildin

g u

se

Win

do

w c

on

tact

Ce

ntr

alL

oca

l

1. 2.

3.

SD

I

S S

S

DI

Eff

ecti

veR

oo

m o

per

atin

gm

od

e

S

Eff

ecti

veo

ccu

pan

cy

DE

SIG

O

3.

Co

ntr

olle

r

PP

S2

S

Cen

tral

Lo

cal

1.

3.

SD

I

S

S

DI

3rd

Par

ty (

S-M

od

e)

3.

Co

ntr

olle

r

1.

3.

Protection

PP

S2

Ce

ntr

alL

oca

l

1. 2.

3.

DI

LTE

DI

Sy

nco

(L

TE

-Mo

de

)

3.

Co

ntr

olle

r

1. 3.

En

able

Co

mfo

rt LTE

Pri

oP

rio

Pri

o

Lo

cal

1.

DI

DI

Sta

nd

-alo

ne

3.

Co

ntr

oll

er

3.

Pri

o

103

85Z

54e

n

Tem

po

rary

co

mfo

rt m

od

e

3.

S3.

S

PP

S2

S

Cen

tral

(A

CS

)

0.

(Syn

co c

on

tro

ller)

Ro

om

op

erat

ing

mo

de

Pre

sen

ce d

etec

tor

Ro

om

un

it

Tem

po

rary

co

mfo

rt m

od

e

Eff

ecti

veo

ccu

pan

cy

Eff

ecti

veR

oo

m o

per

atin

gm

od

e

Win

do

w c

on

tact

Win

do

w c

on

tact

Pre

sen

ce d

etec

tor

Ro

om

un

it

Protection

Win

do

w c

on

tact

Pre

sen

ce d

etec

tor

Ro

om

un

it

Ro

om

op

erat

ing

mo

de

35/166


5.3 Determine the room operating mode in DESIGO (S-mode)

In S-mode, the effective room operating mode of the room controller depends on the central Use and Occupancy time schedules and/or on local influences such as window contacts, presence detectors or a room unit.

The diagram below shows the priority of these influences and how they are processed by the room controller:

103

85Z

55

PPS2

S

Presence detector

Room unit

Occupancy

Building use

Window contact

Central Local

1.

2.

3.

SDI

S

S

S

DI

Effectiveroom op. mode

S

Effectiveoccupancy

3.

Controller

Prio

Temporary Comfort mode

3.S

• The effects of Priority 1 and Priority 2 are similar in nature to continuous states • The Priority 3 influences are treated as events.

The key factor is the moment at which the state changes (trigger edge). If the mode is later changed by another source of priority 3, the last change applies.

STOP Note!

36/166


5.3.1 Local control of room operating mode via a window contact

S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

Whenever a window is opened, the room controller always switches to the Protection room operating mode, i.e. the heating or cooling output is reduced to a minimum. If a window is opened outside the "building-in-use" period it is also possible, for example, to arrange for this to trip an alarm in the building automation and control system.

The table below shows the effective room operating mode as a function of the Window contact input. Status of window contact

Effective room operating mode

Window closed No effect. Operating mode is determined by inputs with a lower priority

Window open Protection mode

The window contact is connected directly to a digital input on the room controller (see page 127). Alternatively an EIB/KNX window contact (connected to the bus) may be used. The application evaluates both items of information (logic OR operation). Since EIB/KNX window contacts are available from a variety of manufacturers, the name of the S-mode output communication object varies accordingly.

Room controller RXB...

Window contact input

EIB / KNX window contact

10385Z10en

Window contact outputOR

Window contact on DI

The following S-mode communication object is used to integrate an EIB/KNX window contact:

Window contact input (Input communication object)

Flags

R W C T U


0 1 1 0 0 1.019

DPT_WindowDoor

No 0 = Closed

1 = Open


Window contact

KNXR

CO

37/166


The state of the room controller (result of the logic OR operation) is mapped to the building automation and control system via the following S-mode communication object:

Window contact output (Output communication object)

Flags

R W C T U

Type Send heartbeat States

1 0 1 1 0 1.019

DPT_WindowDoor

Yes 0 = Closed

1 = Open

Master/slave applications Bindings are required in S-mode, in order to transmit the slave window contact status to the master.

5.3.2 Central control of room operating mode via input from the Use time schedule

S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

This time schedule determines the overall period of time for which the entire building is in use. Typically, this schedule is used for night setback throughout the building, or for longer periods when the building is not in use.

Outside the “building-in-use” times, inputs from 3rd priority sources are disabled. This prevents demand signals from being sent to the primary plant when, for example, a security guard enters a room.

The table below shows the three possible occupancy states and the resulting effective room operating mode.

Switch state Description Effective room op. mode

Building in use • Full availability of all plant • Building enabled for use • Inputs of priority 3 are enabled (Occupancy time

schedule, presence detector, room unit, and Temporary Comfort mode)

As defined by Occupancy time schedule, presence detector or room unit

Building not in use • Reduced availability of plant • Inputs of priority 3 are disabled (Occupancy time

schedule, presence detector, room unit, and Temporary Comfort mode)

• Application: Building temporarily not in use The building must reach the Comfort temperature within hours

Economy

Building protection • Setpoints reduced to the minimum necessary to protect the building fabric.

• Inputs of priority 3 are disabled (Occupancy time schedule, presence detector, room unit, and Temporary Comfort mode)

• Application: Longer periods of non-use of the building

Protection mode

KNXR

CO

Note


38/166


The following S-mode communication object is applicable when using the time scheduler from a building automation and control system:

Time schedule Use (Input communication object)

Flags

R W C T U


0 1 1 0 0 20.002

DPT_BuildingMode

Yes 0 = In use 1 = Not in use 2 = Protection

5.3.3 Central and local control of room operating mode based on occupancy

S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

The effective occupancy is determined by the Occupancy time schedule and the presence detector. It controls the room operating mode of a room controller throughout the period when the building is in use.

The central time schedule transmits the anticipated occupancy of a room or group of rooms. It controls the room operating mode of a room controller throughout the period when the building is in use. Outside the building-in-use period, the time schedule is disabled.

The time schedule can be used, for example, by a building tenant to specify the occupancy times applicable to that tenant’s own rooms.

The Occupancy scheduler has three possible states:

State Description

Occupied • Occupants expected • The room controller switches to Comfort

Standby • Occupancy is probable; the room must be ready for use shortly (Comfort temperature)

• The room controller switches to Precomfort

Unoccupied • No occupants expected • The room controller switches to Economy

A presence detector detects the presence of people in a room.

It controls the room operating mode of a room controller throughout the period when the building is in use. Outside the building-in-use period, it is disabled.

KNXR

CO

Occupancy time schedule

Presence detector

39/166


The presence detector has two possible states:

State Description

Occupied • The room is occupied • The room controller switches to Comfort

Unoccupied • The room is not occupied • The room controller switches to Economy or Precomfort

The table below shows Effective occupancy as a function of the Occupancy time schedule and the presence detector. Principle: "Occupied" takes precedence over “Unoccupied“. If either the time schedule or the presence detector transmits Occupied then the room is Occupied.

Presence detector Occupancy time schedule Effective occupancy

No time schedule Occupied

Occupied Occupied

Standby Standby

No presence detector

Unoccupied Unoccupied

No time schedule Unoccupied

Occupied Occupied

Standby Standby

Unoccupied (No people present)

Unoccupied Unoccupied

No time schedule Occupied

Occupied Occupied

Standby Occupied

Occupied (People present)

Unoccupied Occupied

• The effective room operating mode can be changed by the effective occupancy only

during the building-in-use period (defined by the Use time schedule) • The change in the effective room operating mode is event-driven, the key factor

being the moment at which the effective occupancy changes. • The room unit or Temporary Comfort mode (both Priority 3) can cause the effective

room operating mode to change again the last command always applies. Effective occupancy Effective room operating mode

Occupied Comfort

Standby Precomfort

Unoccupied Economy

Key: “ Occupied" means: "Changes to Occupied" The following S-mode communication object is applicable when using the time scheduler from a building automation and control system:

Time scheduler Occupancy (Input communication object)

Flags R W C T U


0 1 1 0 0 20.003

DPT_OccMode

Yes 0 = Occupied

1 = Standby

2 = Unoccupied

Effective occupancy


KNXR

CO

40/166


The presence detector is connected directly to a digital input on the room controller (see page 127); alternatively an EIB/KNX presence detector connected to the EIB/KNX bus may be used (see diagram below). The two inputs are OR-linked: If one signals presence, presence applies. Since EIB/KNX presence detectors are available from a variety of manufacturers, the name of the S-mode output communication object varies accordingly.


Presence detector input

EIB / KNX presence detector

10385Z07en

Presence detector on DI

OR

Presence detector output

Delay on / off Without delay The following S-mode communication object is used to integrate a presence detector connected to the bus:

Presence detector input (Input communication object)

Flags

R W C T U


1 0 1 1 0 1.018

DPT_Occupancy

Yes 0 = Unoccupied

1 = Occupied

The state of the local presence detector on the digital input is mapped in the building automation and control system via the following S-mode output communication object:

Presence detector output (Output communication object)

Flags

R W C T U

Type Send hearbeat States

0 1 1 0 0 1.018

DPT_Occupancy

No 0 = Unoccupied

1 = Occupied

Master/slave applications: Bindings are required in S-mode, in order to transmit the slave presence detector status to the master.

Effective occupancy

S

Zentral Lokal

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

The output communication object Effective occupancy shows the occupancy status of the room (based on a combination of time schedule and presence detector). In the case of integration into a building automation and control system, the data is mapped to the following output communication object:

Presence detector

KNXR

CO

Note

41/166


Effective occupancy (Output communication object)

Flags

R W C T U Type Send hearbeat States

1 0 1 1 0 20.003

DPT_OccMode

Yes 0 = Occupied

1 = Standby

2 = Unoccupied

5.3.4 Central control of room operating mode via the Room operating mode time schedule

This type of time schedule is not supported in DESIGO. If it is nevertheless used, this can cause room controller errors.

5.3.5 Local control of room operating mode with a room unit

Room unit

S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

The /Auto button on the room unit can be used like an occupancy button. The room user can use it to decrease or increase the room temperature control.

The room unit is connected to the PPS2 interface on the room controller. It displays the effective room operating mode in a simplified form, and can also be used to change it:

State Description

Auto Effective room operating mode is Comfort

Reduced mode in the room, depending on the Priority 1, 2 and 3 influences: The effective room operating mode is Precomfort, Economy or Protection. (3rd priority: "last one wins ").

• The effective room operating mode can be changed via the room unit only during the

building-in-use period (defined by the Use time schedule) • The change in the effective room operating mode is event-driven, the key factor

being the moment when the button on the room unit is pressed. • The Effective occupancy or Temporary Comfort mode (both Priority 3) can cause the

effective room operating mode to change again the last command always applies.


42/166


The table below shows the effect of the /Auto button on the effective room operating mode of the room controller.

Existing effective room op. mode

Display on room unit

Manual operation of the / Auto button

New rffective room operating mode

Comfort Auto Precomfort if effective occupancy = Occupied or Standby Economy if effective occupancy = Unoccupied

Precomfort Auto Comfort

Economy Auto Comfort during Temporary Comfort period 1)

Protection mode Auto Protection, no change

Key: “ Auto" means: "changes to Auto" 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see page

127). The room controller then reverts to Economy.

5.3.6 Local control of room operating mode via the Temporary Comfort mode input

KNXR

CO S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

The communication object Temporary Comfort mode has an effect similar to that of the /Auto button on the room unit. However, the HVAC control system can only be "switched on", i.e. the room operating mode switches to Comfort only.

Any KNX/EIB switch (pulse switch) can be used for the input:

RXB... room controllerEIB / KNX button


10385Z59de The following S-mode communication object is used to integrate a bus switch:

Temporary comfort mode (Input communication object)

Flags Type Receive timeout States

R W C T U

0 1 1 0 0 1.017

DPT_Trigger

No 1 = Trigger

0 = Not used

KNXR

CO

43/166


The communication object Temporary Comfort mode has two possible states:

State Description

1 = Trigger Effective room operating mode is Comfort

0 = Not used Has no effect on the Effective room operating mode

• The change of effective room operating mode with the Temporary Comfort mode

during the building-in-use period (defined by the Use time schedule) • The change of effective room operating mode is event-driven, the key factor being

the moment when the communication object is received. • The Effective occupancy or room unit (both Priority 3) can cause the effective room

operating mode to change again the last command always applies. The table below shows the effect of the Temporary Comfort mode on the effective room operating mode of the room controller.



New effective room operating mode

Comfort 0 = Not used No effect

Precomfort 1 = Trigger Comfort

Economy 1 = Trigger Comfort during Temporary Comfort period 1)

Protection mode 1 = Trigger Protection, no change

Key: 1 means: "changes to 1" 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see page


5.3.7 Effective room operating mode

KNXR

CO S

Central Local

1.

2.

3.

SDI

S

S

S

DI

S

3.

ControllerPrio

PPS2

3.S

For the building automation and control system the resulting effective room operating mode is available to the building automation and control system as follows:

Effective room operating mode (Output communication object)

Flags Type Send heartbeat States

R W C T U

1 0 1 1 0 20.102

DPT_HVACMode

Yes 1 = Comfort

2 = Precomfort

3 = Economy

4 = Protection


44/166


The resultant Effective room operating mode is also available as 4 digital communication objects:

Effective room operating mode Comfort (output communication object) Effective room operating mode Precomfort (output communication object) Effective room operating mode Economy (output communication object) Effective room operating mode Protection (output communication object)

Flags

L S K Ü A

Typ Send Heartbeat Zustände

1 0 1 1 0 1.001

DPT_Switch

Ja 0 = Aus

1 = Ein

5.3.8 DESIGO examples

The following are examples of two typical applications of time schedules in conjunction with local control of the room operating mode. Rooms with neither a room unit nor a presence detector

The operating mode of Rooms 1 … 3 in a building is determined by the two time schedules Building use and Room occupancy. Window contacts are fitted in all rooms.

The following conditions are specified:

• Overall, the building is in use from 06.00 to 22.00 (Building use time schedule). Outside this period the opening of a window will trip an alarm (2).

• Rooms 1…3 are used by the same tenant and controlled by the same Occupancy time schedule. Night mode is to operate from 17.00 to 08.00 (Unoccupied) and the lunch break is from 12.00 to 13.00 (Standby).

• In Room 3 the window is opened briefly, once in the morning and once at night (1).

Example 1

45/166


Time schedule Use

Time schedule Occupancy Rooms 1 … 3 Window contact Room 3

Effective room operating mode Room 3

Building in use

Building not in use

Building protection

Occupied

Standby

Unoccupied

Window open

Window closed

Comfort

Precomfort

Economy

Protection mode

06:00 22:00

08:00 17:0013:0012:00

10385D02

1)

2)

1)

Rooms with a room unit ( /Auto button) or presence detector

The operating mode in Rooms 1 and 2 of a building is determined centrally by the Use and Occupancy time schedules. The Occupancy time schedule defines the period during which both rooms are required to be available (Standby). Comfort mode is then initiated locally via the room unit (Room 1) or presence detector (Room 2).


• Overall, the building is in use from 06.00 to 22.00 (Building use time schedule). • Rooms 1 and 2 must be available from 08.00 to 18.00 (Occupancy time schedule:

Standby) • The occupants of Room 1 continue working in the evening beyond the programmed

occupancy period. At the end of the programmed period of occupancy, the room operating mode changes to Economy, even if the room unit is set to Auto (1). Comfort mode can now be re-activated with the Auto switch on the room unit (2). Comfort remains active for the pre-defined Temporary Comfort mode period (see page 127). However, at the end of the "building-in-use" period the Temporary Comfort period is also overridden and the room operating mode reverts to Economy mode (3).

• In Room 2, in the evening, there are still people in the room beyond the "building-in-use" period (4). However, at the end of the building-in-use period the room operating mode still changes to Economy mode. An alarm can also be tripped, if required.

Example 2

46/166


Use time schedule Occupancy time schedule Room 1 and 2 / Auto button on the room unit Room 1 Effective room op. mode Room 1 Presence detector Room 2 Effective room op. mode Room 2

Building in use

Building not in use

Building protection

Occupied

Standby

Unoccupied

Auto

Comfort

Precomfort

Economy

Protection mode

Occupied

Unoccupied

Comfort

Precomfort

Economy

Protection mode

06:00 22:00

08:00 18:00

10385D03

1)

1)

2)

2)

3)

3)

4)

4)

47/166


5.4 Determine the room operating mode with third-party products (S-mode)

In S-mode the effective room operating mode of the room controller depends on the central Room operating mode time schedule and/or on local influences such as window contacts, presence detectors or room units.

The diagram below shows how these influences are processed by the room controller, and their priority:

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

Effectiveroom op. mode

3.

Controller

1.

3.

Room operating mode

Pro

tec

tio

n m

od

e

Window contact

Presence detector

Room unit

Prio

103

85

Z5

6

3.

TemporaryComfort mode

S

S

Effectiveoccupancy

• The effects of Priority 1 and Priority 2 are similar in nature to continuous states • The Priority 3 influences are treated as events.

The key factor is the moment at which the state changes (trigger edge). If the mode is later changed by another source of priority 3, the last change applies.

Note!

48/166


5.4.1 Local control of room operating mode via the window contact input

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S

Whenever a window is opened, the room controller always switches to the Protection room operating mode, i.e. the heating or cooling output is reduced to a minimum.

The table below shows the effective room operating mode as a function of the Window contact input. Status of window contact




The window contact is connected directly to a digital input on the room controller (see page 127). Alternatively an EIB/KNX window contact (connected to the bus) may be used. The application evaluates both items of information (logic OR operation). Since EIB/KNX window contacts are available from a variety of manufacturers, the name of the S-mode output communication object varies accordingly.


Window contact input

EIB / KNX window contact

10385Z10en

Window contact outputOR

Window contact on DI

The following S-mode communication object is used to integrate an EIB/KNX window contact:

Window contact input (Input communication object)

Flags Type Receive timeout States R W C T U

0 1 1 0 0 1.019

DPT_WindowDoor

No 0 = Closed

1 = Open


Window contact

KNXR

CO

49/166


The state of the room controller (result of the logic OR operation) is mapped to the building automation and control system via the following S-mode output communication object:

Window contact output (Output communication object)

Flags

R W C T U


1 0 1 1 0 1.019

DPT_WindowDoor Yes 0 = Closed

1 = Open

Master/slave applications Bindings are required in S-mode so that the status of the window contact connected to the slave can be communicated to the master.

5.4.2 Central control of room operating mode via the Room operating mode time schedule

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

Prio

3.S

S

3.

The room operating mode can be specified directly with the communication object Room operating mode.

The following S-mode communication object is used to control the Room operating mode from a building automation and control system:

Time schedule Room operating mode (Input communication object)

Flags

R W C T U Type Receive timeout States

0 1 1 0 0 20.102

DPT_HVACMode

Yes 1 = Comfort 2 = Precomfort 3 = Economy 4 = Protection

Room operating mode time schedule

Effective room operating mode of room controller

Comfort Comfort

Precomfort Precomfort

Economy Economy

Protection mode Protection mode

• For the room controller, the room operating modes Comfort, Precomfort and

Economy are Priority 3 and can therefore later be changed by a presence detector or room unit.

• The room operating mode Protection has first priority, and the presence detector and room units are therefore disabled.

KNXR

CO

Note

Priorities

50/166


5.4.3 Central control of room operating mode via the Use and Occupancy time schedules

These time schedules are not supported by third-party S-mode. If they are used nevertheless, this can cause room controller errors.

5.4.4 Central and local control of room operating mode based on occupancy

Presence detector

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S


It controls the room operating mode of a room controller throughout the period when the building is in use. Outside the building-in-use period, it is disabled.

The presence detector has two possible states:

State Description

Occupied • The room is occupied • The room controller switches to Comfort

Unoccupied • The room is not occupied • The room controller switches to Economy or Precomfort

• The change of effective room operating mode is event-driven, the key factor being

the moment when the effective occupancy changes. • The room unit or Temporary Comfort mode (both Priority 3) can cause the effective

room operating mode to change again the last command always applies. Presence detector New effective room operating mode

Unoccupied (people leave room)

Precomfort

Occupied (people enter room)

Precomfort if room operating mode from schedule = Comfort or Precomfort Economy if room operating mode from schedule = Economy.

Key: " Occupied" means: "Changes to Occupied" The presence detector is connected directly to a digital input on the room controller (see page 127); alternatively an EIB/KNX presence detector connected to the EIB/KNX bus may be used (see diagram below). The two inputs are OR-linked: If one signals presence, presence applies.


Presence detector

51/166


Since EIB/KNX presence detectors are available from a variety of manufacturers, the name of the S-mode output communication object varies accordingly.


Presence detector input

EIB / KNX presence detector

10385Z07en

Presence detector on DI

OR

Presence detector output

Delay on / off Without delay The following S-mode communication object is used to integrate a presence detector connected to the bus:

Presence detector input (Input communication object)

Flags R W C T U


1 0 1 1 0 1.018

DPT_Occupancy

Yes 0 = Unoccupied

1 = Occupied The state of the local presence detector on the digital input is mapped in the building automation and control system via the following S-mode output communication object:

Presence detector output (Output communication object)

Flags R W C T U


0 1 1 0 0 1.018

DPT_Occupancy

No 0 = Unoccupied

1 = Occupied

Master/slave applications: Bindings are required in S-mode, in order to transmit the slave presence detector status to the master.

Effective occupancy

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S

The output communication object Effective occupancy shows the occupancy status of the room (presence detector). In the case of integration into a building automation and control system, the data is mapped to the following output communication object:

Effective occupancy (Output communication objectg)

Flags R W C T U


1 0 1 1 0 20.003

DPT_OccMode

Yes 0 = Occupied

1 = Standby

2 = Unoccupied

KNXR

CO

Note

52/166



Room unit

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S

The /Auto button on the room unit can be used like an occupancy button. The room user can use it to switch the HVAC system "on" or "off".

The room unit is connected to the PPS2 interface on the room controller. It displays the effective room operating mode in a simplified form, and can also be used to change it.

State Description


Reduced mode in the room, depending on the Priority 1 and 2 influences as well as the Room operating mode schedule: The effective room operating mode is Precomfort, Economy or Protection.

• The change in the effective room operating mode is event-driven, the key factor

being the point at which the button on the room unit is pressed. • The Effective occupancy or Temporary Comfort mode (both Priority 3) can cause the

effective room operating mode to change again the last command always applies. The table below shows the effect of the /Auto button on the effective room operating mode of the room controller.



Manual operation of /Auto button


Comfort Auto Precomfort If room operating mode from time schedule = Comfort or Precomfort

Economy If room operating mode from time schedule = Economy



Protection mode Auto Protection mode, no change

Key: " Auto" means: "Changes to Auto" 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see

page 127). The room controller then reverts to Economy.


53/166


5.4.6 Local control of room operating mode via the Temporary Comfort mode input

KNXR

CO

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S

The communication object Temporary Comfort mode has an effect similar to that of the /Auto button on the room unit. However, the HVAC control system can only be "switched on", i.e. the room operating mode switches to Comfort only.

Any KNX/EIB switch (pulse switch) can be used for the input:

RXB... Room controllerEIB / KNX button

Temporary ComfortMode

10385Z59en The following S-mode communication object is used to integrate a bus switch:

Temporary comfort mode (Input communication object)

Flags R W C T U


0 1 1 0 0 1.017

DPT_Trigger

No 1 = Trigger

0 = Not used

The communication object Temporary Comfort mode has two possible states:

State Description

1 = Trigger Effective room operating mode is Comfort

0 = Not used Has no influence on the effective room operating mode


being the moment when the communication object is received. • The Effective occupancy or room unit (both Priority 3) can cause the effective room

operating mode to change again the last command always applies.

KNXR

CO


54/166


The table below shows the effect of the Temporary Comfort mode on the effective room operating mode of the room controller.




Comfort 0 = Not used No effect

Precomfort 1 = Trigger Comfort

Economy 1 = Trigger Comfort during Temporary Comfort mode 1)

Protection mode 1 = Trigger Protection, no change

Key: 1 means: "changes to 1" 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see


5.4.7 Effective room operating mode

PPS2

S

Central Local

1.

3.

SDI

S

S

DI

3.

Controller

1.

3.

Prio

3.S

S

For the building automation and control system the resulting effective room operating mode is available to the building automation and control system as follows:

Effective room operating mode (Output communication object)

Flags R W C T U


1 0 1 1 0 20.102

DPT_HVACMode

Yes 1 = Comfort

2 = Precomfort

3 = Economy

4 = Protection

The resultant Effective room operating mode is also available as 4 digital communication objects:

Effective room operating mode Comfort (output communication object) Effective room operating mode Precomfort (output communication object) Effective room operating mode Economy (output communication object) Effective room operating mode Protection (output communication object)

Flags

R W C T U


1 0 1 1 0 1.001

DPT_Switch

Yes 0 = Off

1 = On

55/166


5.4.8 Third-party (S-mode) examples

The following examples show two typical applications of time schedulers in conjunction with local control of the room operating mode. Rooms with neither a room unit nor a presence detector

The room operating mode in rooms 1…3 of a building is determined by the Room operating mode time schedule. Window contacts are installed in all the rooms. The following conditions are specified: • Overall, the building is in use from 06.00 to 20.00. • The rooms are used and controlled by the Room operating mode time schedule as

follows: – Night setback from 17.00 to 08.00, – Protection from 20.00 to 06.00 – Lunch break from 12.00 to 13.00 (Precomfort)


Room op. mode time schedule Window contact Room 3


Comfort

Precomfort

Economy

Protection

Window open

Window closed

Comfort

Precomfort

Economy

Protection

08:00 17:0013:0012:0010385D04

1)

06:00 20:00

1)


The room operating mode in Rooms 1 and 2 of a building is determined centrally by the Room operating mode time schedule. Comfort mode is then initiated locally via the room unit (Room 1) or presence detector (Room 2).


• Overall, the building is in use from 06.00 to 20.00 (Protection mode from 20.00 to 06.00 hours).

• Rooms 1 and 2 must be available from 08.00 to 18.00 hours (Precomfort)

Example 1

Example 2

56/166


• The occupant(s) of Room 1 are working overtime. At 18.00 hours the room operating mode changes to Economy, even if the room unit is set to Auto (1). Comfort mode can now be re-activated with the Auto switch on the room unit (2). Comfort remains active for the pre-defined Temporary Comfort mode period (see page 127). In Protection mode however, the Temporary Comfort period is also overridden and the room operating mode changes to Protection (3).

• In Room 2, in the evening, there are still people in the room beyond the "building-in-use" period (4). However, at the end of the building-in-use period the room operating mode still changes to Protection. An alarm can also be tripped, if required.

Time schedule room op. mode

Room with room unit

/Auto button on the room unit Room 1 Effective room op. mode Room 1

Room without room unit

Presence detector Room 2 Effective room op. mode Room 2

Comfort

Precomfort

Economy

Protection mode

Auto

Comfort

Precomfort

Economy

Protection mode

Occupied

Unoccupied

Comfort

Precomfort

Economy

Protection

08:00 18:00

10385D05

1)

1)

2)

2)

3)

3)

4)

4)

06:00 20:00

57/166


5.5 Determine the room operating mode with Synco (LTE mode)

In LTE-mode the effective room operating mode of the room controller depends on the central Room operating mode time schedule and/or on local influences such as window contacts, presence detectors or room units.


PPS2

Central Local

1.

2.

3.

DI

LTE

DI

3.

Controller

1.

3.

Enable Comfort

LTE

Prio

103

85Z

57en

Central (ACS)

0.

(Synco controller)

Window contact

Presence detector

Room unit

Pro

tect

ion

Room operatingmode

• If the room operating mode in the ACS (operating booklet) is AUTO, the priorities

1 to 3 apply. If the room operating mode in the ACS (operating booklet) is Comfort, Precomfort, Economy or Protection, these modes have absolute priority ("Prio 0").

• The effects of Priority 1 and Priority 2 are similar in nature to states, which apply continuously

• The Priority 3 influences are treated as events. The key factor is the moment at which the state changes (trigger edge). If the mode is later changed by another source of priority 3, the last change applies.

STOP

Note!

58/166



Window contact

PPS2

Central (Synco controller)

Local

1.

2.

3.

DI

DI

3.

Controller

3.

Prio

1.

Central (ACS)

0.


The table below shows the effective room operating mode as a function of the window contact input. Status of window contact




The window contact is connected directly to a digital input of the room controller (see page 127). Master/slave applications It is not possible in LTE mode to transmit the status of the slave window contact to the master.

5.5.2 Central control of the room operating mode via Enable Comfort

PPS2


Local

1.

2.

3.

DI

DI

3.

Controller

3.

Prio

1.

Central (ACS)

0.

A central operator station can use the Enable Comfort input to specify whether the room operating mode can be switched to a higher mode than Economy mode, i.e. whether Priority 3 influences (Room operating mode input, presence detector or room unit) are enabled.

In the room controller however, the Priority 3 influences can be enabled forcibly, by ignoring the Enable Comfort input (via the parameter Local Comfort mode).


Note

59/166


The following LTE-mode communication object is provided for central control:

Enable Comfort (input)

Possible partner-function blocks Known partner devices

EnableComfort

Timeswitch zone

110 HVACS HVAC-Mode Scheduler 104 PMC Programme to HVAC-Mode Conversion

Siemens: Synco RMB795

The states are:

State Description

Enabled Priority 3 influences (RoomOperatingMode, presence detector, room unit) are enabled

Disabled Priority 3 influences are disabled. The effective room operating mode is Economy.

Comfort and Precomfort are enabled locally in the controller with the following parameter in the Room unit menu, page 139:

Parameter: Local comfort mode Description HandyTool

Switch from Economy to Precomfort or Comfort mode *105

Enabled (basic setting) Means that Precomfort or Comfort can be disabled via the Enable Comfort input.

1

Disabled (ignore Enable Comfort input) In this case Precomfort or Comfort CANNOT be disabled via the Enable Comfort input

0

5.5.3 Central control of room operating mode via Room operating mode input

PPS2


Local

1.

2.

3.

DI

DI

3.

Controller

3.

Prio

1.

Central (ACS)

0.

The following LTE-mode communication object is used to control the room operating mode from a building automation and control system:

Room operating mode (input)

Possible partner-function blocks Known partner devices

HVACMode

Timeswitch zone

110 HVACS HVAC-Mode Scheduler 104 PMC Programme to HVAC-Mode Conversion

Siemens: Synco RMU710 / 20 / 30 RMH760 / RMB795

KNXR

CO

KNXR

CO

60/166


State Description

Room operating mode Effective room operating mode of room controller

Comfort Comfort

Precomfort Precomfort

Economy Economy

Protection mode Protection mode

• For the room controller, the room operating modes Comfort, Precomfort and Economy

are Priority 3 and can therefore be changed later by a presence detector or room unit. • The room operating mode Protection has first priority, and the presence detector and

room units are therefore disabled.

5.5.4 Local control of room operating mode via presence detector

Presence detector

PPS2


Local

1.

2.

3.

DI

DI

3.

Controller

3.

Prio

1.

Central (ACS)

0.


The presence detector is connected directly to a digital input of the room controller (see page 127). Master/slave applications It is not possible in LTE mode to transmit the status of the slave presence detector to the master. The table below shows the two possible occupancy states and the resulting effective room operating mode.

Switching state Effective room operating mode


Comfort


Precomfort if room operating mode = Comfort or Precomfort Economy if room operating mode = Economy

Key: Occupied means "changes to Occupied "

Priorities

Note


61/166



Room unit

PPS2


Local

1.

2.

3.

DI

DI

3.

Controller

3.

Prio

1.

Central (ACS)

0.



State Description


Reduced mode in the room, depending on the Priority 1, 2 and 3 influences: Effective room operating mode is Precomfort, Economy or Protection.

• The change in the effective room operating mode is event-driven, the key factor being the moment when the button on the room unit is pressed.

• The Effective occupancy can cause the effective room operating mode to change again the last command always applies.

The table below shows the effect of the /Auto button on the effective room operating mode of the room controller.



Manual operation of the /Auto button


Comfort Auto Precomfort If room operating mode from time schedule = Comfort or Precomfort

Economy If room operating mode from time schedule = Economy



Protection mode Auto Protection, no change

Key: Auto means: “changes to Auto” 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see



62/166


5.5.6 LTE-Mode Examples

The following examples show two typical applications of the time schedule in conjunction with local control of the room operating mode. Rooms with neither a room unit nor a presence detector

The room operating mode in Rooms 1 … 3 of a building is determined by the Room operating mode time schedule. Window contacts are fitted in all rooms.


• Overall, the building is in use from 06.00 to 20.00. • The rooms are used and controlled by the Room operating mode time schedule as

follows: – Night setback from 17.00 to 08.00, – Protection from 20.00 to 06.00 – Lunch break from 12.00 to 13.00 (Precomfort)


Time schedule Room operating mode Window contact Room 3


Comfort

Precomfort

Economy

Protection

Window open

Window closed

Comfort

Precomfort

Economy

Protection

08:00 17:0013:0012:0010385D04

1)

06:00 20:00

1)


The room operating mode in Rooms 1 and 2 of a building is determined centrally by the Room operating mode time schedule. Comfort mode is then initiated locally via the room unit (Room 1) or presence detector (Room 2).


• Overall, the building is in use from 06.00 to 20.00 (Protection mode from 20.00 to 06.00 hours).

• Rooms 1 and 2 must be available from 08.00 to 18.00 hours (Precomfort)

Example 1

Example 2

63/166


• The occupant(s) of Room 1 are working overtime. At 18.00 hours the room operating mode changes to Economy, even if the room unit is set to Auto (1). Comfort mode can now be re-activated with the Auto switch on the room unit (2). Comfort remains active for the pre-defined Temporary Comfort mode period (see page 127). In Protection mode however, the Temporary Comfort period is also overridden and the room operating mode changes to Protection (3).

• In Room 2, in the evening, there are still people in the room beyond the "building-in-use" period (4). However, at the end of the building-in-use period the room operating mode still changes to Protection. An alarm can also be tripped, if required.

Time schedule Room operating mode

Room with room unit

/Auto button on the room unitRoom 1 Effective Room operating mode Room 1

Room with presence detector

Presence detector Room 2 Effective Room op. mode Room 2

Comfort

Precomfort

Economy

Protection

Auto

Comfort

Precomfort

Economy

Protection

Occupied

Unoccupied

Comfort

Precomfort

Economy

Protection

08:00 18:00

10385D05

1)

1)

2)

2)

3)

3)

4)

4)

06:00 20:00

64/166


5.6 Determine the room operating mode without a bus (stand-alone)

If no bus is connected, the effective room operating mode of the room controller depends on local influences such as window contacts, presence detectors or room units.


PPS2

Local

1.DI

DI

3.

Controller

3.

Window contact

Presence detector

Room unit

Prio

103

85Z

58

• The effects of Priority 1 and Priority 2 are similar in nature to the states, which

apply continuously • The Priority 3 influences are treated as events.

The key point in time is the moment at which the state changes (trigger edge). If the mode is later changed by another source of priority 3, the last change applies.

If there is no bus connection, the controller assumes the following defaults:

• Use = Building in use • Occupancy = Occupied

STOP Note!

Note

65/166



Window contact

PPS2

Local

1.DI

DI

3.

Controller

3.

Prio


The window contact is connected directly to a digital input of the room controller (see page 127). The table below shows the effective room operating mode as a function of the window contact input. Status of window contact


No window contact Comfort (default)



5.6.2 Local control of room operating mode via a presence detector

Presence detector

PPS2

Local

1.DI

DI

3.

Controller

3.

Prio

A presence detector detects the presence of people in the room and controls the room operating mode of a room controller.

The presence detector is connected directly to a digital input of the room controller (see page 127). • The change in the effective room operating mode is event-driven, the key factor

being the point at which the effective occupancy changes. • The room unit (which is also Priority 3) can cause the effective room operating mode

to change again the last command always applies.



.

.

.

66/166


Presence detector New effective room operating mode

No presence detector Comfort (default)


Economy


Comfort

Key: " Occupied" means "changes to Occupied"


Room unit

PPS2

Local

1.DI

DI

3.

Controller

3.

Prio



State Description


Reduced mode in the room, depending on the Priority 1 or 3 influences: Effective room operating mode is Precomfort, Economy or Protection.


being the moment when the button on the room unit is pressed. • The presence detector (which is also Priority 3) can cause the effective room

operating mode to change again the last command always applies. The table below shows the effect of the /Auto button on the effective room operating mode of the room controller.



Manual operation of the /Auto-button


Comfort Auto Precomfort, if effective occupancy = Occupied

Economy, if effective occupancy = Unoccupied



Protection Auto Protection, unchanged


67/166


Key: Auto means: “changes to Auto” 1) Comfort mode is operative for the pre-defined Temporary Comfort period (see page


5.6.4 Stand-alone Example

The example below shows how local influences interact to affect the room operating mode. • Window contacts are fitted in all rooms.

When the window is opened (1), the room operating mode changes to Protection, and the room unit is switched to .

• Room 1 has a room unit.

As no presence detector is connected, the basic room operation mode is Precomfort; therefore, the timer (Temporary Comfort period: see page 127) is not available. The room unit can be used to switch the room operating mode between Comfort and Precomfort (2).

• Room 2 has a presence detector and a room unit..

If the room is unoccupied, the basic room operation mode is Economy. If it changes to occupied, the room operating mode becomes Comfort (3), and the room unit is switched to Auto. The room unit can be used to switch between Comfort and Precomfort (2).

• Room 3: In order to force the basic room operation mode to be Economy, one of the

open Digital inputs is parameterized as Occupied = Contact closed (see page 127), thus simulating a presence detector in state "unoccupied. Starting from Economy, the timer (Temporary Comfort period: see page 127) is available. The room has a room unit with the timer enabled. It can be used to set the room operating mode to Comfort (2). It reverts to Economy when the window is opened, (3) when the timer period expires (4), or when the /Auto switch is pressed again (5).

68/166


Window contact Room 1

/ Auto button on the room unit Room 1


Window open

Window closed

Auto

Comfort

Precomfort

Economy

Protection

10385D70

2)

1) 1)

2) 2) 2)

Window contact Room 2 Pres. detector Room 2

/ Auto button on room unit Room 2


Window open

Window closed

Occupied

Unoccupied

Auto

Comfort

Precomfort

Economy

Protection

3)

2)

1) 1)

10385D71

2)

Window contact Room 3

/ Auto button on the room unit Room 3


Window open

Window closed

Auto

Comfort

Precomfort

Economy

Protection

10385D72

1) 1)

2) 2)

3)

2)

4) 5)

69/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Setpoint calculation 08 Mar 2012

6 Setpoint calculation 6.1 Description

• Each room controller has 9 different room temperature setpoints: One heating and cooling setpoint for the room operating modes Comfort, Precomfort, Economy and Protection as well as a Frost limit value.

• The setpoints – are defined in the tool during engineering. – runtime-adjusted by the communication objects (DESIGO, Synco)

This does not apply to the Protection setpoints and the frost setpoint (page 33).

• The setpoints are shifted – Centrally via KNX bus from the building automation and control system

(only Comfort, Precomfort and Economy). – Locally via PPS2 by a room unit or a setpoint adjustment unit

(only Comfort and Precomfort). – The controller controls the values internally to ensure that sensible periods are

adhered to between the various room operating modes.

• The result is 8 present setpoints.

• The effective room operating mode selects one setpoint each for heating and cooling from the 8 setpoints. These are the effective setpoints to which the controller executes control.

Define Shift Tool 6.2 Runtime 6.3 Centrally 6.4 Locally 6.5

103

85Z

40e

nComfort heating setpoint

Comfort cooling setpoint

Precomfort heating setpoint

Precomfort cooling setpoint

Economy heating setpoint

Economy cooling setpoint

Protection heating setpoint

Protection cooling setpoint

Local setpoint shiftCentral setpoint shift heating

8 present setpoints

Effective heating setpoint SpH

Effective cooling setpoint SpC

H C

PPS2 KNX


Central setpoint shift cooling

Frost setpoint

KNX

KNX

KNX

KNX

PPS2

DI

KNX

KNX

(6.1.1)

(6.1.2)

70/166


6.1.1 Bus output for current setpoints

The present setpoints can be integrated in the building automation and control system via the following S-mode communication objects individually or as triplets:

Present Eco cooling setp (Output communication object) Present Precomf cooling setp (Output communication object) Present Comf cooling setp (Output communication object) Present Comf heating setp (Output communication object) Present Precomf heat setp (Output communication object) Present Eco heating setp(Output communication object)

Flags

R W C T U

Type Send

heartbeat

Values

1 0 1 1 0 9.001

DPT_Value_Temp

yes Floating point (°C)

Present setpoints heating (Output communication object) Present setpoints cooling (Output communication object)

Flags

R W C T U

Type Send

heartbeat

Values

1 0 1 1 0 222.100

DPT_TempRoomSetpSetF16[3]

yes 3 floating point values - Comfort (°C) - Precomfort (°C) - Economy (°C)

6.1.2 Bus output effective setpoints

For integration into a building automation and control system, the controller maps the effective setpoints associated with the effective room operating mode to the following communication object:

Effective setpoint (Output communication object) Effective setpoint heating (Output communication object) Effective setpoint cooling (Output communication object)

Flags

R W C T U

Type Send heartbeat Value

1 0 1 1 0 9.001

DPT_Value_Temp


If the room temperature is in the dead band, the Effective setpoint transmitted by the controller is either the heating or the cooling setpoint, depending on the controller's last activity.

6.1.3 Bus outputs LTE mode

In LTE-mode, the current and effective setpoints are not transmitted to the building automation and control system.

KNXR

CO

Note

71/166


6.2 Set the setpoints with the tool

A tool is used to set the temperature setpoints for the various room operating modes in each room controller. Select Room temperature setpoints.

The setpoints can be modified under Room temp setpoints:

ETS3 Professional

ACS Service

72/166



Name Basic setting Range 1) Resolution Parameter

Protection cooling setpoint 40 °C 10 ... 40 °C 0.5 K *030

Economy cooling setpoint 35 °C 10 ... 40 °C 0.5 K *031

Precomfort cooling setpoint 28 °C 10 ... 40 °C 0.5 K *032

Comfort cooling setpoint 24 °C 10 ... 40 °C 0.5 K *033

Comfort heating setpoint 21 °C 10 ... 40 °C 0.5 K *034

Precomfort heating setpoint 19 °C 10 ... 40 °C 0.5 K *035

Economy heating setpoint 15 °C 10 ... 40 °C 0.5 K *036

Protection heating setpoint 12 °C 10 ... 40 °C 0.5 K *037

Frost protection limit value *) 5 °C 2 ... 10 °C *) 0.5 K *040

1) ACS checks the values / ranges for intersection. There is no check in ETS and HandyTool.

2) The Frost protection limit can only be changed in applications with an outside air damper. In the other applications it is fixed at 5°C.

HandyTool: If setpoints are irrelevant for the application (e.g. heating setpoints for chilled ceiling), they are hidden, and they are set equal to the Protection setpoints internally. For reasons of symmetry, all communication objects are always available.

6.3 Setpoint adjustment runtime

The setpoints are stored in the EEPROM so that they are retained when the controller is reset. If a value different from a previous value is received on the communication objects setpoints for heating and setpoints for cooling, a write process is triggered in the EEPROM. The service life of the EEPROM depends on the number of Write cycles.

Separate heating and cooling setpoints for Comfort, Precomfort and Economy may also be defined via the bus, either individually or as triplets.

Economy cooling setpoint (Input communication object)

Precomfort cooling setpoint (Input communication object)

Comfort heating setpoint (Input communication object)

Comfort cooling setpoint (Input communication object)

Precomfort heating setpoint (Input communication object)

Economy heating setpoint (Input communication object)

Flags

R W C T U


0 1 1 0 0 9.001

DPT_Value_Temp

no Floating point (°C)

Setpoints heating (Input communication object) Setpoints cooling (Input communication object)

Flags

R W C T U


0 1 1 0 0 222.100

DPT_TempRoomSetp

SetF16[3]

no 3 floating point values - Comfort (°C) - Precomfort (°C) - Economy (°C)

Setpoints

STOP Note!

EEPROM service life

KNXR

CO

73/166


In LTE-mode, the central setpoint setting is transmitted via the following communication objects (triplets).

Setpoints heating (Input) Setpoints cooling (Input)

Possible partner

function blocks Known partner devices

TempRoomSetpSetHeat TempRoomSetpSetCool

Geographical zone

Siemens SBT proprietary Siemens: Synco RMB795

Setpoints that have been changed by a tool (e.g. HandyTool) are overwritten by PX-KNX during start-up of the room controller!

6.4 Central setpoint shift

• The Comfort, Economy and Precomfort setpoints can be adjusted centrally for heating and cooling via the building automation and control system.

Central setpoint shifts are used particularly e.g. for summer/winter compensation. Summer/winter compensation causes a gradual increase in room temperature as a function of the outside temperature. This prevents too great a difference between the indoor and outdoor temperature in summer and increases overall comfort in winter. Normally, only Comfort and Precomfort values are shifted. The room controller corrects the setpoints resulting from central shift by applying the following rules • Comfort setpoints:

The value for the spacing must not be below the original value A .

• Precomfort setpoints: The value for the spacing to Comfort setpoints must not be below the original values B .

Winter compensation Original Summer compensation

values Setpoints

Protection cooling

Economy cooling

Precomfort cooling

Comfort cooling

Comfort heating

Precomfort heating

Economy heating

Protection heating

103

85D

107

Sp [°C]

TOA

A

B

STOP Note!

Management station

Summer/winter compensation

Internal correction by controller

74/166


In a building automation and control system, the central setpoint shift can be influenced via the following S-mode communication objects (triplets):

Setpoint shift for heating (Input communication object) Setpoint shift for cooling (Input communication object)

Flags R W C T U


0 1 1 0 0 222.101

DPT_TempRoomSetp

SetShiftF16[3]

yes 3 floating point values

– Comfort (K) – Precomfort (K) – Economy (K)

In LTE-mode, the central setpoint shift is transmitted via the following communication objects (triplets):

Setpoint shift for heating (Input) Setpoint shift for cooling (Input)

Possible partner

function blocks Known partner devices

TempRoomSetpSetHeatShiftTempRoomSetpSetCoolShift

Geographical zone

115 HVACOPT

HVAC Optimizer

Siemens: Synco RMB795

6.5 Local setpoint shift

If setpoints are shifted locally and corrected by the controller, local shift is applied.

Two methods are available for local setpoint shift: – Using a series QAX... room unit (local PPS bus) providing a rotary button or rocker

switch to adjust the room temperature setpoint – or via EIB/KNX bus. If multiple sources command local setpoint shift, "last one wins" applies. The S-mode communication object is used for setpoint shift via the EIB/KNX bus:

Setpoint offset (input communication object)

Flags

R W C T U

Type Receive timeout Value

0 1 1 0 0 9.002

DPT_Value_Tempd

No Floating point (K)

The following communication object is used in LTE-mode:

Setpoint offset (input)

Possible partner

function blocks) Known partner devices

TempRoomSetpUserOffset

Geographical zone

384 UHRS

User HVAC

Room settings

Siemens:

Synco QAW740

KNXR

CO

KNXR

CO

75/166


• Comfort: – The Comfort setpoints for heating and cooling are shifted in parallel A .

– The original spacing heating – cooling is maintained. The room controller corrects the setpoints as follows following a local shift:

• Precomfort:: – The values are shifted in parallel to the Comfort values B .

– The cooling setpoint cannot be lowered following central shift C .

– The heating setpoint cannot be increased following central shift C .

• Economy: – The cooling setpoint cannot be lowered following central shift C .

– The heating setpoint cannot be increased following central shift C .

– The value is shifted together with the Precomfort value D .

• Protection: – Protection values are absolute E .

– A minimum spacing between Comfort heating and Comfort cooling of 0.5 K is maintained F .

Setpoints

Protection cooling

Economy cooling

Precomfort cooling

Comfort cooling

Comfort heating

Precomfort heating

Economy heating

Protection heating

103

85D

108

Sp [°C]

Offset [K]

A

0 +-

0.5 K

0.5 K

BC

D

F

E

C

D

F

Local setpoint shift

Upon a change from Comfort and Precomfort to Economy or Protection, the setpoint shift can be reset (see page 136). The Effective setpoint offset (last value of local shift via PPS2 / bus) is available in the following S-mode communication object:

Effective setpoint offset (output communication object)

Flags

R W C T U


1 0 1 1 0 9.002

DPT_Value_Tempd

Yes Floating point (K)

Function

Internal correction by controller

Note

KNXR

CO

76/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Temperature measurement 08 Mar 2012

7 Temperature measurement 7.1 Room temperature measurement

The value valid for temperature control can originate in various sources: – A room unit via PPS2 7.1.1 – An analog sensor via analog input B1 7.1.2 – Mean value of several sensors 7.1.3 – The bus. 7.1.6 If none of these sources supplies a valid room temperature, the following will happen: • the controller uses the mean value from the effective heating and cooling setpoints

for control until a valid measured value is again received • the controller issues an alarm "Room temp. sensor error" • the bus output sends 0°C • if slaves are connected, they receive an invalid temperatur (327.67°C) • if a room unit is connected to a slave, the slave uses the temperature value of its

room unit when two heartbeat periods have elapsed.

7.1.1 Local temperature sensor at PPS2 interface

PPS2 (CP+, CP-)QAX3...

RXB2...

1038

5Z1

2

If a QAX … room unit (with a PPS2 interface) is connected to the controller, the room temperature is measured by the temperature sensor built into the room unit.

7.1.2 Local temperature sensor at analog input

B1QAA24

RXB2...

1038

5Z1

3

Alternatively, an LG-Ni1000 sensor, type QAA24, may be connected to analog input B1 of the room controller.

The sensors connected to terminal B1 can be tasked with different functions:

Parameter setting Description Room Room indoor air sensor (can also be used for

averaging, see below). Return air Return air sensor

(refer also to Section 9.2.4, "Periodic fan kick") No sensor No sensor connected

(basic setting, except for FNC08) Only measured value acquisition

Uses the signal, see "analog input B1", page 139.

Supply air (cascade) Supply air temperature for cascade control. The sensor is automatically configured as a supply air sensor if application FNC08 is selected.

Sources

Invalid temperature

77/166


The sensor is parameterized under fan control for tool architectural reasons: Click Fan control, Temperature sensor B1 (see page 114).

Select Fan control, Temperature sensor B1 (see page 114).


Parameter Short name Basic setting

Temperature sensor No sensor FNC08: Supply air (cascade)

*092

Return air 0 Room 1 Supply air (cascade) 2 Only meas val acquisition 3 No sensor 255

Only meas val acquisition: Use of the the signal: see "analog input B1", page 139.

7.1.3 Averaging analog input & PPS2 interface

In large spaces it can be useful to measure the room temperature in two locations and to determine an average value. If both a QAX3… room unit and a QAA24 LG-Ni1000 sensor are connected to a controller, the measured room temperature is automatically based on the average value from both sensors. The automatic detection feature prevents miscalculation. A QAX34 / QAX84 will display this average value.

PPS2 (CP+, CP-)B1

QAX3...

RXB2...

QAA24

103

85Z

14

The average value is calculated from the two sensor readings.

• In order to determine the average value, the sensor must be configured as a room

temperature sensor

• The signal is not averaged in the case of return air sensors and KNX sensors.

Note

ETS3 Professional

ACS Service

Notes

78/166


In fan coils with a return air sensor (at B1), the controller must be configured accordingly (see page 116).

– The temperature sensor in the room unit is ignored in this process (the signal is not averaged).

– A QAX34.1 room unit displays the value of B1.

7.1.4 Sensor correction

The value of the local sensors (PPS2 and B1) can be corrected in the tools (see page 141), but not the value of a bus sensor.

7.1.5 Temperature sensor outputs on the Konnex bus

To map the local temperature measurement in a building automation and control system the following three output communication objects are used:

RXB... Room controller10385Z15en

R

O +

Return air temperature output

Effective room temperature

Room tempearture output

The values of the communication objects Room temperature output and Return air temperature output are unfiltered (not smoothed). Sending takes place only if room "Room" is parameterized for the temperature sensor B1. The value transmitted as the Effective room Temperature is the filtered (smoothed) value of the communication object Room temperature output or Return air temperature output, or the average (see 7.1.3): Room temperature output (Output communication object) Effective room temperature (Output communication object) Return air temperature output (Output communication object)

Flags

R W C T U


1 0 1 1 0 9.001

DPT_Value_Temp


Invalid temperatures are mapped to the bus as 0 °C.

Return air temperature

Note

79/166


In LTE mode, the room/return air temperature from directly connected sensors is mapped as follows:

Room temperature output (Output)

Possible partner function

blocks Known partner devices

TempRoom

Geographical zone

390 UHD

UserHVACDisplay

Siemens:

Synco RMH760 / RMB795

RMU710 / 20 / 30

Return air temperature output (Output)


blocks Known partner devices

TempReturnAir

Geographical zone

--- ---

7.1.6 Temperature sensor input from Konnex bus

The signal from the sensor connected to the bus takes priority. The signal is not averaged and no sensor correction (page 141) is done.

Since KNX temperature sensors are available from a variety of manufacturers, the name of the S-mode output communication object varies accordingly.

RaumTemperatur EffektiveRaumTemperatur

10385Z16en

Room temperaure Input Effective Room temperature

Effective Room Temperature

... or ...

Return air temperature Input

KNX temperatur sensor RXB... room controller

If the room temperature/return temperature is available as information on the bus, it can be read with one of the following S-mode communication objects:

Room temperature input (Input communication object) Return air temperature input (Input communication object)

Flags R W C T U


0 1 1 1 1 9.001

DPT_Value_Temp


Subject to the appropriate configuration and integration, the room temperature/return air temperature is read by the controller immediately after a reset.

For a Konnex sensor the send heartbeat must be set to "Cyclical sending enabled"

KNXR

CO

STOP Note!

80/166


The situation is slightly different in LTE mode: Here, each signal has its own specific name, and the room temperature and return air temperature therefore each have their own communication object. Room temperature (Input)

Possible partner function blocks Known partner devices

TempRoom

Geographical zone

321 RTS

Room Temperature Sensor

Siemens:

Synco RMH760

RMU710 / 20 / 30

QAW740

Return air temperature (Input)


TempReturnAir

Geographical zone

323 RNATS

Return Air Temperature Sensor

---

7.2 Outside air temperature via Konnex bus (FNC10, FNC12, FNC18)

For the FNC10, FNC12, and FNC18 applications, the outside air temperature must be available as a bus information. It can be read via the next S-mode communication object:

Outside air temperature input (Input communication object)

Flags

R W C T U


0 1 1 1 1 9.001

DPT_Value_Temp


Subject to the appropriate configuration and integration, the outside air temperature is read by the controller immediately after a reset.

In LTE mode, the outside air temperature is sent in a special zone. Outside air temperature input (Input)


TempOutside

Outside air

temperature zone

320 OTS

Room Temperature Sensor

Siemens:

Synco RMH760

RMU710 / 20 / 30

RMB795 / RMS705

KNXR

CO

81/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Control sequences 08 Mar 2012

8 Control sequences 8.1 Fan coils with valve control 8.1.1 Four-pipe fan coils - With valve control

The applications for 4-pipe fan coils each have a proportional heating and proportional cooling sequence. The controllers operate with a PI algorithm optimized for thermal or motorized valve actuators. (For simplicity, the diagrams below only show the P-control action).

T

B1

YC

YH

Q1

103

85S

01

The control sequences come into operation at the effective setpoints for heating and cooling (see page 69).

Y [%]

SpH SpC TR [°C]

H C

YH YC

100

0

103

85D

08

Y Output signal TR Room temperature SpH Effective heating setpoint SpC Effective cooling setpoint H Heating sequence C Cooling sequence YH Heating valve YC Cooling valve B1 Return air sensor Q1 Fan

Different applications support different valve actuators, and these do not all require the same number of outputs on the controller. The tool displays the actuators suitable for the selected application. Selection occurs at the engineering stage (see page 85).

Actuator type

82/166


8.1.2 Two-pipe fan coils - With valve control

Two-pipe fan coils have only one proportional control sequence. This may be configured for heating, cooling or changeover operation, as required. The controllers operate with a PI algorithm optimized for thermal or motorized valve actuators. (For simplicity, the diagrams below only show the P-control action).

103

85S

02

T

B1

Q1

YHC

The control sequence comes into operation at the effective setpoint for heating or cooling (see page 69).

Heating only

100

0TR [°C]

YHC

Y [%]

SpH

H

103

85D

09

Cooling only

100

0TR [°C]

YHC

Y [%]

SpC

C

103

85D

10

Changeover (heating or cooling)

100

0TR [°C]

YHCYHC

Y [%]

SpH SpC

H C

Change-over

103

85D

11

Y Output signal TR Room temperature SpH Effective heating setpoint SpC Effective cooling setpoint H Heating sequence C Cooling sequence YHC Heating or cooling valve B1 Return air sensor Q1 Fan

The control sequence must be selected when the controller is engineered: Heating only, Cooling only or Changeover.

Selecting the control sequence

83/166


Select Edit parameters, Sequences.

Select sequences under Parameter settings.


*050 Control sequence Cooling Only

Parameter Setting Description Handy-

Tool

Control Changeover Changeover signal via KNX bus 0

sequence Cooling only Cooling sequence only 1

Heating only Heating sequence only 2

Different applications support different valve actuators, and these do not all require the same number of outputs on the controller. The tool displays the actuators suitable for the selected application. The valve type must be selected at the engineering stage (see page 85).

ETS3 Professional

ACS Service

Actuator type

84/166


Changeover is only possible if the control sequence parameter is set to changeover. In this case, a changeover command (heating or cooling) is essential. In the absence of the required information (e.g. due to problems with data communication), the controller operates as follows:

– After a reset, the controller operates in heating mode until another changeover command is received.

– If the transfer of data is interrupted, the controller remains in the last valid room operating mode.

The changeover information must be transmitted to the bus and is integrated via the following communication object:

H/C changeover input (Input communication object)

Flags

R W C T U


0 1 1 0 0 1.100

DPT_Heat/Cool

yes 0 = Cooling

1 = Heating


H/C changeover (Input)


ChangeOverStatusWater

Distribution zone, heating

Distribution zone, cooling

342 WCOS

Water Changeover Status Sensor

Siemens:

Synco RMU710 / 20 / 30

RMB795 / RMS705

8.1.3 Heating/cooling output

The controller makes its status (heating or cooling) available via the following communication object:

Heating/cooling output (Output communication object)

Flags

R W C T U


1 0 1 1 0 1.100

DPT_Heat/Cool

yes 0 = Cooling

1 = Heating

The value of the Output as a function of the room temperature is shown in the following diagram:

0 = CoolTR

10

38

5D

20

1

SpH SpC

1 = Heat

Value

Changeover

KNXR

CO

85/166


8.1.4 Actuator type selection

All actuators have threads suitable for fitting to both normally-closed (push to open) and normally-open (pull-to-open) valves. However, the RX applications do not support inverse control, which means that only actuators with a pulling action can be used with "pull-to-open" valves and only actuators with a pushing action can be used with "push-to-open" valves. This is why, in RX applications, valves with mounted actuators are always closed when de-energized. Different applications support different valve actuators, and these do not all require the same number of outputs on the controller.

– Thermal actuators are driven with an AC 24 V PDM signal – Motorized actuators with an AC 24 V 3-position signal. – Electromechanical actuators (motors with spring return) have a special PDM

algorithm that ensures that 50 position changes per day are not exceeded. This causes a slower control behavior.

Thermal and electromechanic actuators thus require one output, motorized actuators two.

The table below shows the possible combinations:

System Actuator type

Controller Outputs required

Four-pipe fan coil (thermal) RXB21.1 RXB22.1 Heating

Cooling

80261

Y1

Y2

(motorized) RXB21.1 M

M

Heating

Cooling

Y1

Y2

Y3

Y4

80262

Electro-mechanic (ON / OFF)

RXB21.1

Heating

Cooling

Y1

Y3

M

M

RXB22.1 Heating

Cooling

Y1

Y2

M

M

Two-pipe fan coil (thermal) RXB21.1 RXB22.1

Heating or cooling

80263

Y1

(motorized) RXB21.1 RXB22.1 M Heating or cooling

Y1

Y2

80264

Electro-

mechanic (ON / OFF)

RXB21.1 RXB22.1 Y1 M Heating or cooling

The RXB2… room controllers also support the use of motorized EIB/KNX bus actuators. In the tool, select Bus motorized.

STOP Note!

Directly connected valve actuators

Motorized KNX/EIB bus actuators

86/166


• It is not possible to ensure exact parallel running of more than one thermal valve actuator. If several radiators are controlled by the same room controller, preference should be given to motorized actuators. If thermal actuators must nevertheless be controlled in parallel, third-party thermal must be parameterized regardless of manufacture. This applies also if an external power amplifier is used to drive the actuators.

• Thermal actuators operate at a raised temperature. To ensure a fast response, the actuators are continuously preheated to a slightly higher temperature (5% – 1 s ON / 19 s OFF). They therefore continue to receive pulses from the controller even when closed.

Möhlenhoff actuators have been tested successfully in our HVAC laboratory. Electromechanic third-party devices often have different runtimes for opening and closing. For optimal control, the longer of the two running times must be parameterized. When switching on the controller, after parameterization, after switching from test mode to normal mode and for valve protection (unblocking, see page 91), the actuators are synchronized:

• Thermal heating and cooling valve actuators are controlled with "Open" for 5 minutes (50% – 1 sec ON/ 1 sec OFF), then again for 5 minutes with "Close" (5% – 1 sec ON/ 19 sec OFF).

• Motorized actuators are first opened (110% of the runtime) and then closed (110% of the runtime).

The sequence starts after synchronization. The actuator type used must be defined at the engineering stage: Select Edit parameters, Sequences:

Thermal valve actuators

Thermal third party devices

Electromechanic third-party devices

Synchronize

Parameterization

ETS3 Professional

87/166


Select the valve actuator type from Sequences:

HandyTool

Parameter Short name Basic setting

*060 Actuator type heating / cooling valve STP72E (FNC08: SSP81)

Settings

STE71 1 SSA81 10 Motorized bus 14

STE72 2 SSB81 11 Electromech. 252

STA71 3 SQS81 12 third-party devices

STP71 4 SSC81 13 Thermal third-party devices 253

STA72E 5 SSP81 14 Motorized third-party devices 254

STP72E 6

With motorized actuators (conventional and bus actuators), third-party devices can also be connected. The actuator running time can be adapted and an offset set accordingly. The offset considers the time between the electric pulse and the actual mechanic movement of the actuator. This is especially important for fast running actuators.

For electromechanic actuators, the actuator running time can be adapted.

For fast actuators, select valve type "Motoric 3rd party devices ".

ACS Service

88/166


Select Sequences. After selection of third-party devices, a new window opens in which the heating and cooling runtimes can be set.

Select the actuator runtime from Sequences:


Motorized and electromechanic valves.

Parameters 4-pipe Basic setting Range Resolution HandyTool

Running time heating valve 150 s 0 ... 360 s 1 s *061

Running time cooling valve 150 s 0 ... 360 s 1 s *062

Offset heating valve 0 s 0 ... 360 s 1 s *071

Offset cooling valve 0 s 0 ... 360 s 1 s *072

ETS3 Professional

ACS Service

89/166


Parameter 2-pipe Basic setting Range Resolution HandyTool

Running time heating / cooling valve 150 s 0 ... 360 s 1 s *061 1)

Offset heating valve 0 s 0 ... 360 s 1 s

Offset cooling valve 0 s 0 ... 360 s 1 s

1) In the case of 2-pipe applications (changeover), the parameter *62 (Running time

cooling valve) is visible in the HandyTool, but has no effect. • For FNC: 10, 12, 18, electromechanic actuators are not allowed for load reasons. • Also, thermal valves do not have parallel operation of Y1 / Y2 and Y3 / Y4.

8.1.5 Values representing valve actuator positions

Valve positions are available in the following S-mode communication objects:

Heating coil output (Output communication object) Cooling coil output (Output communication object)

Flags

R W C T U


1 0 1 1 0 5.001

DPT_Scaling

yes 0...100% 0 = 0%

255 = 100%

• For DESIGO integration:

With FNC02 and FNC03 (changeover applications) in S-mode, the valve position is mapped only to heating coil output.

• If you use KNX / EIB bus actuators, check the flags: the reading permission of the actuator must be disabled!

Since EIB/KNX bus actuators are available from a variety of manufacturers, the name of their S-mode input communication object varies accordingly.

Notes

KNXR

CO

Notes

90/166


In LTE mode, the valve position is transmitted as follows:

Heating coil output (Output) Cooling coil output (Output)

Possible partner function blocks Known partner

devices

ActPosSetpHeatStageA ActPosSetpCoolStageA

Geographical zone

352 HVA

HVAC Valve Actuator

369 EHEA

Electric Heater Element Actuator

---

In LTE-mode, where directly connected actuators are used rather than bus valve actuators, the bus load can be reduced by disabling LTE communication for these outputs (see also page 144). Select Sequences.

The two fields at the bottom of the dialog box only appear if "LTE and S-mode" was selected under Communication. Select Sequences.

Reduce bus load

ETS3 Professional

Note

ACS Service

91/166



Short name Range Basic setting HandyTool

Bus valve heating output 0 = disabled / Off 1 = enabled / On

disabled (0) *085

Bus valve cooling output 0 = disabled / Off 1 = enabled / On

disabled (0) *087

8.1.6 Valve exercising feature

To prevent valves from seizing after long periods of inactivity (e.g. cooling valves in winter) the valves are operated from time to time. The valve actuators are operated in such a way as to waste as little heating or cooling energy as possible.

The valve exercise function is triggered if the valve has been closed for ca. 91 hours without interruption.

8.1.7 Override valve actuators

For test purposes, the valve actuators can each be overridden individually via the following communication objects: Heating valve override (Input communication object) Cooling valve override (Input communication object)

Flags

R W C T U


0 1 1 0 0 8.010

DPT_Percent_V16

no 0...100% 0 = 0%

+100 = +100%

+32767 = invalid

Before the valve actuators can be overridden, the “Test” mode must be activated via the communication object Application mode (see page 129).

The valve is operated in accordance with the settings shown below:

Heating value

Cooling value

Control

Invalid Invalid -----

Valid Invalid Heating

Invalid Valid Cooling

Valid Valid Thermal actuators: Heating and cooling alternately, with the Heating value

Motorized actuators: Heating and cooling valve driven to the Heating position

KNXR

CO

Note

92/166


8.2 Fan coils with damper control

In FNC20, a single damper actuator is used for control of both heating and cooling.

8.2.1 Four-pipe fan coils with damper control (FNC20)

In application FNC20, which uses a damper instead of a valve for modulating control of the room temperature, a constant volume of water flows through the two heat exchangers. Depending on the demand, the air flow is guided either through the heating coil or through the cooling coil, causing a change in the resulting mixed air temperature.

103

85D

12

100

TR [°C]

Y [%]

SpH SpC

YM

H C

0

N

Y Damper position TR Room temperature SpH Effective heating setpoint SpC Effective cooling setpoint H Heating sequence N Dead band (recirculated air) C Cooling sequence YM Damper actuator

The heat-exchanger configuration may call for asymmetric runtimes for heating and cooling; these can be set individually. At the mid-point where the air flow switches from heating to cooling, the time period associated with the mechanical dead band can also be preset.

Select Sequences.

ETS3 Professional

93/166


Select the damper actuator runtime from Sequences:


Parameter name Basic setting Range Resolution Parameter

Running time damper heating 150 s 0 ... 360 s 1 s *061

Running time damper cooling 150 s 0 ... 360 s 1 s *062

Changeover time damper 0 s 0 ... 360 s 1 s *070

8.2.2 Value representing damper actuator positions

The position value for the damper actuator is mapped to the same communication objects as the heating coil /cooling coil valve position (see page 89): Heating coil output and cooling coil output.

The value is the same on both communication objects, i.e. the previously determined damper stroke: e.g. 0 ... 40% damper stroke is equivalent to cooling from 100 …0%. 41 ... 54% damper stroke = neutral zone. 55 ... 100% damper stroke is equivalent to heating from 0 …100%.

Heating coil output (Output communication object) Cooling coil output (Output communication object)

Flags

R W C T U


1 0 1 1 0 5.001

DPT_Scaling

yes 0...100% 0 = 0%

255 = 100%

ACS Service

KNXR

CO

94/166


8.2.3 Overriding the damper actuator

For test purposes, the damper actuator can be overridden via the following communication objects:

Damper override (Input communication object)

Flags

R W K T U


0 1 1 0 0 8.010

DPT_Percent_V16

no 0...100% 0 = 0%

+100 = +100%

+32767 = invalid

Before the damper actuator can be overridden, “Test” mode must be activated via the communication object Application mode (see page 129).

The actuator is operated in accordance with the settings shown below:

Heating value

Cooling value

Control

Invalid Invalid -----

Valid Invalid Heating

Invalid Valid Cooling

Valid Valid The full travel of the damper is 0…100%. The actuator moves to the position defined by the heating value.

KNXR

CO

Note

95/166


8.3 Fan coils with an electric heating coil

This function will be implemented later.

8.4 Fan coils with an electric reheater

In addition to controlling heating and/or cooling valves, some applications also provide an output for the control of an electric heating coil. This is then operated as a reheater, i.e. it only comes into operation when the heating valve is fully open.

• With motorized actuators, the electric reheater is only enabled when the heating

valve is fully open.

• In the case of thermal actuators, the electric reheater is not enabled until the thermal actuator has been operated at maximum flow (100%) for at least 2 minutes.

• The switching differential is fixed at 1.0 K.

8.4.1 4-pipe fan-coils with electric reheater

T

B1

YC

YHQ1

D3YR

103

85S

07

Y Output signal TR Room temperature SpC Effective cooling setpoint SpH Effective heating setpoint H Heating sequence C Cooling sequence YH Heating valve YC Cooling valve YR Electric reheater D3 Safety thermostat B1 Return air sensor Q1 Fan

1-step Modulating

OFF

YR

ON

0%

Y

100%

YCYH

TR [°C]

YR

H1 K

SpH SpC

103

85D

54

YCYH

0%TR [°C]

YR, Y

100%H

SpH SpC

YR

103

85D

55

Notes

96/166


8.4.2 2-pipe fan-coils with electric reheater

T

B1

YHC

Q1

D3YR

103

85S

23

YHC Heating valve YR Electric reheater D3 Safety thermostat B1 Return air sensor Q1 Fan

The control mode must be selected at the engineering stage: heating only, cooling only or changeover The electric reheater also operates with "Cooling only" and "Change-over" in cooling mode. In this case, the heating setpoint (SpH) is used for control.

1-step Modulating

Heating only or c/o = Heating

OFF

YR

ON

0%

Y

100%

YHC

TR [°C]

YR

H1 K

SpH

103

85D

56

YHC

0%TR [°C]

YR, Y

100%H

SpH

YR

103

85D

57

Cooling only or c/o = Cooling

OFF

YR

ON

0%

Y

100%

YHC

TR [°C]

YR

H1 K

SpH SpC

C

103

58D

58

YHC

0%TR [°C]

YR, Y

100%H

SpH SpC

YR

C1

0385

D59

Changeover

OFF

YR

ON

0%

Y

100%

YHC

TR [°C]

YR

H1 K

SpH

107

85D

61

C

Change-over

SpC

YHC

0%TR [°C]

YR, Y

100%H

SpH

YR

107

85D

62

C

Change-over

SpC

Selection of the control mode

Electric reheater with cooling-only or changeover applications

97/166


Changeover with disabled electric heater (see page 98)

100

0TR [°C]

YHCYHC

Y [%]

SpH SpC

H C

Change-over

103

85D

60

Further details: see sections 8.1.3 through 8.1.7.

8.4.3 The electric reheater

In the case of the RXB22.1 room controller, the electric reheater is switched directly via output Q44 (max. 1.8 kW resistive). The controller output of the electric reheater can be disabled locally via a safety thermostat connected to one of the hardware inputs. The alarm input and the way in which it operates can be configured with the tool (see "Digital inputs", page 127).

When the safety thermostat trips, an alarm is generated, which is output via the communication object Alarm (see page 135). The "position" of the electric reheater is also mapped to the bus.

In S-mode, the following communication object is used for this purpose:

Heating output bus electric heating (Output communication object)

Flags

R W K T U


1 0 1 1 0 5.001

DPT_scaling

yes 0...100% 0 = 0%

255 = 100%

In LTE mode, the "position" of the electric reheater is transmitted as follows:

Heating output bus electric heating (Output)


devices

ActPosSetpHeatStageB

Geographical zone

352 HVA

HVAC Valve Actuator

369 EHEA

Electric Heater Element Actuator

---

If the LTE bus information is not required, it can be disabled (see pages 90 and 144 for notes on reducing the load on the bus).

HandyTool See parameters in the last column of the following table.


Heating outp bus el heating 0 = Disabled / Off 1 = Enabled / On

Disabled(0) *089

Controller output

Safety thermostat

Desired output

KNXR

CO


98/166


In applications involving an electric reheater, the latter can be disabled (e.g. for reasons associated with tariff regulations).

The communication objects are as follows:

Enable electric heating (Input communication object)

Flags

R W K T U


0 1 1 0 0 1.003

DPT_Enable

yes 0 = Disabled

1 = Enabled

Enable electric heating (Input)


devices

EnableHeat

Geographical zone

115 HVACOPT HVAC Optimizer

---

Single-stage or modulating control can be selected in the tool for the electric heater battery. Select Sequences, Electric heater.

Select Sequences, Electric Reheater:

Central disable signal

KNXR

CO

Type of electric heater

ETS3 Professional

ACS Service

99/166



Short name Basic setting Parameter

Electric heater Modulating *056

1-step 1 Modulating 254

If an electric reheater is used, the controller makes the present power demand available on the bus. In order for this to happen, the capacity of the heater battery must be written to the controller via the tool. Select Sequences, Power consumption el heater:

Select Sequences, Power consumption:

Power demand

ETS3 Professional

ACS Service

100/166



*057 Power consumption el heater 0 W

The power consumption is mapped to the following communication object:

Electric output (Output communication object)

Flags

R W K T U


1 0 1 1 0 9.024

DPT_Power

yes Floating point (kW)

8.5 Fan-coils with LTHW radiator (FNC18)

LTHW radiator applications have a proportional control sequence. The controllers operate with a PI algorithm optimized for thermal or motorized valve actuators. (For simplicity, the diagram below shows only the P-control action.)

The radiator sequence can also be used for other heating types, e.g. floor heating. However, the control parameters are not optimized for this.

The heater battery of the fan-coil operates in a cascade with the radiator.

The control sequences come into operation at the effective heating setpoint.

B1

YHC

Q1

YH

T

D3

B1

T

T

103

85S

08

100

0TR [°C]

Y [%]

SpH SpC

Change-over

YH

H C100

0TR [°C]

Y [%]

SpH SpC

Change-over

YHC

H C

103

85D

16

YHC

Y Output signal TR Room temperature SpH Effective heating setpoint H Heating sequence YH Heating valve (radiator) YHC Heating/cooling valve (fan coil) B1 Return air sensor Q1 Fan

KNXR

CO

101/166


8.5.1 Configuration and parameter setting

The radiator as an additional heating sequence has its own settings for the valve actuator and runtime. The principles are described in section 8.1.4. Select Sequences, Actuator type heating surface valve:

Select Sequences, Sequences, Act type heating surf valve:

ETS3 Professional

ACS Service

102/166



For the assignment actuator – Parameter number refer to page 87.

Parameter for LTHW radiator Basic setting Range Resolution HandyTool

Actuator type heating surface valve STA72E All actuators except STE72

-- *063

Running time heat surface valve (motorized actuators)

150s 0…360 s 1 s *064

Offset heating surface valve 0 s 0 ... 360 s 1 s *066

8.5.2 Position values for tediator valve actuators

The "position" of the radiator is mapped to the bus. See also section 8.1.5. The Heating surface output communication object must NOT be used for applications for thermal valve actuators to control KNX/EIB valve actuators. With these applications, the communications objects have theoretical valve positions only. In S-mode, the following communication object is used for this purpose:

Heating surface output (Output communication object)

Flags

R W K T U


1 0 1 1 0 5.001

DPT_scaling

yes 0...100% 0 = 0%

255 = 100%

In LTE mode, the "position" of the radiator is transmitted as follows:

Heating surface output (Output)


devices

ActPosSetpHeatStageB

Geographical zone

352 HVA

HVAC Valve Actuator

---


HandyTool See parameters in the last column of the following table.


Heating surface outp bus valve 0 = Disabled / Off 1 = Enabled / On

Disabled(0) *086

8.5.3 Heat demand

This application can have two different heat demand signals; one from the air-to-air heat exchanger and one from the radiator. In KNX –LTE mode, the demand signals are mapped as 2 bus signals (see 11.5, Heating and cooling demand). In S-mode, this demand is summarized in Heating demand room.

STOP Important!

KNXR

CO


103/166


8.5.4 Radiator valve actuator override

See also section 8.1.7. For test purposes, the radiator valve actuator can be overridden via the following communication objects:

Heating surface output override (Input communication object)

Flags

R W K T U


0 1 1 0 0 8.010

DPT_Percent_V16

no 00...100% 0 = 0%

+100 = +100%

+32767 = invalid

Before the radiator valve actuator can be overridden, “Test” mode must be activated via the communication object Application mode (see page 129).

8.5.5 Downdraft compensation

This function is only active in Comfort mode.

In situations where (owing to large internal heat gains) there is no heating demand from the room despite a low outdoor temperature (supplied via the bus), large window surfaces can impair indoor comfort (through radiated cold and the downward flow of cold air). A radiator located under the window can be used to “brake” the downward flow of cold air and compensate for cold radiation.

To achieve this, the radiator is switched on whenever the outdoor temperature drops below a predefined value (the Outdoor temp. 0% valve position).

The maximum heating output (set under Max. Valve Position) is reached at the "coldest outdoor temperature" (which can be set under Outdoor temp. max. valve position).

25%

100%

0% TOA

Heating output

Outdoor temp.max. valve position

Max. valve position

103

85D

17en

_01

Outdoor temp.0% valve position

ThermicMotoric

The controller adds the values representing the valve position for downdraft compensation and the valve position for the heating sequence. – If the room temperature rises as a result of the downdraft compensation feature, the

heating sequence reduces the opening of the associated valve, so correcting the room temperature.

– When the sequence reaches zero, the room temperature is increased by the residual heat from the downdraft compensation feature.

KNXR

CO

Note

Function

Note

104/166


The heat output calculated by the controller is achieved as follows:

LTHW radiators with motorized valve actuators

The valve is opened to the heat output value [%].

LTHW radiators with thermal valve actuators

• The minimum heat output is 25%: 400 seconds "OPEN" (1s On, 1 s Off) 1200 s "CLOSE" (1s On, 19 s Off)

• Heat output 50%: 400 seconds "OPEN" (1s On, 1 s Off) 400 s "CLOSE" (1s On, 19 s Off)

• Heat output 80%: 1600 seconds "OPEN" (1s On, 1 s Off) 400 s "CLOSE" (1s On, 19 s Off)

The long cycle time ensures that the valves are fully opened and closed.

In a network containing several room controllers, the opening of the Siemens thermic actuators is staggered to prevent the heating load from fluctuating.

In fan coils with parallel operation of a thermal radiator valve actuator and a thermal heating/cooling valve actuator, the valve actuators are driven alternately by the controller. Select Sequences, Other setpoints:

Select Sequences, Other setpoints:

Controller output

Note

ETS3 Professional

ACS Service

105/166



Parameter for downdraft compensation

Basic setting

Range

Resolution

HandyTool parameter

Outdoor temp.0% valve position 0 °C –30 … 10 °C 0.5 K *078

Outdoor temp. max. valve position

–10 °C –30 … 10 °C 0.5 K *079

Max. valve position 100 % 0 ... 100 % 1 % *080

The following conditions must be fulfilled:

– The room controller must be in Comfort mode – The radiator must not be disabled (e.g. by application mode = COOL).

8.6 Outside air damper fan coils ("Economizer", FNC10, FNC12)

The outside air damper mainly serves to provide the room with fresh outside air. In addition, the outside air can be used to cool the room.

The outside air damper is always operated in Comfort and Precomfort modes. In Economy mode, it is operated only in conjunction with the following special functions (see page 129 ff. for a description):

Pre-Cool, Free Cool, Night Purge and Fan-Only. The damper is controlled through a stroke model calculated from the runtime of the actuator.

The Economizer setpoint Outside air temp. min. damper pos. defines at which outside temperature the outside air damper is opened to an adjustable minimum position. This minimum position ensures a constant air supply below the outside air temperature.

The Outside air temp. min. damper pos. setpoint should be selected to ensure that there is at least a difference of 4 K between this value and the cooling setpoint and that, at the same time, no draught is caused by the inflow of cold outside air.

The Economizer setpoint should not be much lower than the Comfort heating setpoint, otherwise too much cool air would come into the room during the heating sequence.

Above the Outside air temp. min. damper pos. setpoint, the damper is opened beyond the minimum position if:

– the outside temperature is below the room temperature and – either the room controller is in Comfort or Precomfort room operating mode

or one of the special functions "Pre-Cool", "Free Cool", "Night Purge" or "Fan-Only" is active

Enabling the function

Control sequence, damper actuator

106/166


The damper is fully closed if:

– the outdoor temperature drops below the frost protection limit (see page 33) – the safty thermostat for the outdoor temperature is activated (see page 127) – the special function "Emergency Heat" is active in Economy mode – the outside air temperature is above the room temperature.

103

85D

18

Y [%]

100

min

0

SpFr SpEmc SpCTO [°C]

Y Position of damper actuator min Min. damper position TO Outside air temperature SpC Cooling setpoint SpEcm Economizer setpoint = Outdoor temp. min. damper position SpFr Frost protection limit value

8.6.1 Configuration and parameterization

Basic functions: see sections 8.1.1 through 8.1.7. The outside temperature is transmitted to the room controller via the KNX bus. See "Outside air temperature via Konnex bus (FNC10, FNC12, FNC18)", page 80 . Select Sequences, Other setpoints:

Select Sequences, Other setpoints:

Outside air temperature

ETS3 Professional

ACS Service

107/166



Parameter outside air supply

Basic setting

Range

Resolution

HandyTool parameter

Outdoor temp. min. damper pos. 16°C 10 °C...40°C *) 0,5°C *073

Outside air damper runtime 150s 0 ... 360s 1s *074

Min. damper position 0% 0 ... 100% 1% *075

*) By temporarily adjusting the setpoint if necessary, the application ensures that

there is a differential of at least 1K between the Outside air temp. min. damper pos. setpoint and the cooling setpoint of the effective room operating mode.

8.6.2 Enabling of the function

The function can be centrally disabled or enabled. Basic setting: the outside air damper is enabled. The following S-mode communication object is used to integrate the damper enabling:

Enable dampers (Input communication object)

Flags

R W K T U


0 1 1 0 0 1.003

DPT_Enable

yes 0 = Disable = damper closed

1 = Enable = automatic control


Enable dampers (Input)


DisableDamper

Geographical

zone

115 HVACOpt HVAC-Optimizer

Siemens: ---

The use of the outside-air damper can only be implemented in conjunction with the RXB21.1 controller. In this case, the AC 24 V 3-position damper actuator is connected to the outputs Y3 and Y4.

KNXR

CO

108/166


8.6.3 Position values for damper actuators

The position of the outside air damper is mapped to the bus.

In S-mode, the following communication object is used for this purpose:

Outside air damper (Output communication object)

Flags

R W K T U


1 0 1 1 0 5.001

DPT_scaling

yes 0...100% 0 = 0%

255 = 100%

In LTE mode, the "position" of the outside air damper is transmitted as follows:

Outside air damper (Output )


devices

ActPosSetpFreshAir

Geographical zone

362 ADA

Air Damper Actuator

---


8.6.4 Overriding the outside air damper

For test purposes, the outside air damper can be overridden via the following communication objects:

Damper override (Input communication object)

Flags

R W K T U


0 1 1 0 0 8.010

DPT_Percent_V16

no 0...100% 0 = 0%

+100 = +100%

+32767 = invalid

Before the outside air damper can be overridden, the test mode must be activated via the communication object Application mode (see page 129).

KNXR

CO

Note

KNXR

CO

Note

109/166


8.7 Room supply air cascade control (FNC08)

Room supply air cascade control makes it possible to reach the required room temperature very quickly. On the basis of the measured room temperature, the controller calculates a setpoint for the temperature at the air outlet of the fan coil. A limit value can be applied to this temperature to prevent the introduction of uncomfortably cold / warm air into the room.

This function is not available for electric heaters, as these cannot be controlled well enough with RXB controllers.

T T

Room

Fancoil

Room sensor Discharge airsensor

Room controller FNC08

Setpoints room

Controllerdisch. air

Actual room temp. Actualdisch. temp.

Setpoints disch. air (internal)

Controllerroom

Positioningsignals

Max. disch. airMin. disch. air

HC

H

C

1038

5z12

1en

This function is possible in conjunction with motorized valve actuators only.

STOP Note!

110/166


8.7.1 Parameterizing

Basic functions: see sections 8.1.1 through 8.1.7. Minimum supply air temperature and Maximum supply air temperature must be parameterized during engineering.

Select Edit parameters, Other setpoints:

Select Other setpoints.


Parameter Basic setting

Range Resolution HandyTool parameter

Minimum supply air temperature

16 °C 10 °C to Comfort heating setpoint 0.5 °C *038

Maximum supply air temperature

35 °C Comfort cooling setpoint to 40 °C 0.5 °C *039

ETS3 Professional

ACS Service

111/166


8.7.2 Supply air inputs / outputs

The supply air temperature sensor is connected to input B1 of the controller. The room temperature must be measured with the room sensor installed in the room unit.

Temperature sensor

Inputs required

Supply air temperature Room temperature

10385S09

B1

TCP+, CP–

The supply air temperature is mapped to the following S-mode output communication object:

Supply air temperature output (Output communication object)

Flags

R W K T U


1 0 1 1 0 9.001

DPT_Value_Temp


The supply air temperature can also be measured with a bus sensor. The following S-mode input communication object is used for this purpose:

Supply air temperature input (Input communication object)

Flags

R W K T U


0 1 1 1 1 9.001

DPT_Value_Temp


The bus signal has priority over the locally connected sensor! In LTE mode, the supply air temperature from directly connected sensors is mapped as follows:

Supply air temperature output (Output)


blocks

Known partner devices

TempSupplyAir

Geographical zone

390 UHD

UserHVACDisplay

Siemens:

Synco RMH760 / RMB795

RMU710 / 20 / 30

When "supply air " is configured, the controller retrieves this value after a reset.

KNXR

CO

Note

112/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Fan control 08 Mar 2012

9 Fan control 9.1 Description

All fan coil applications incorporate single-speed, two-speed or three-speed automatic fan control. The fan speeds are enabled and disabled via volt-free relay contacts. The controllers operate with an algorithm optimized for thermal or motorized valve actuators for each fan speed. Certain room units allow the user to select the fan speeds MANUALLY (in Comfort mode only).

There are two types of automatic mode: • “AUTO” applies to automatic operation at Comfort temperature setpoints.

• The symbol " " does not mean “Fan Off”, but "automatic operation at reduced setpoints", e.g. Precomfort mode. In the reduced room operating modes, the fan speeds CANNOT be selected manually.

In automatic mode, the fan speeds are controlled in accordance with the response of a PI controller to the control deviation. The relays are operated in alternation. Example: When the controller switches from Speed 1 to Speed 2, first the relay for Speed 1 switches off (A), and then, after a delay of 1 s, the relay for Speed 2 switches on (B). The same applies in reverse when switching down.

TR [°C]

Q

SpH

H

10385D19

C

Q14

Y

100%

SpC

Valve sequence

Fan

TR [°C]SpH SpC

10385D20

Q14

Q24(B)

(A)

100%

Y Q Ha

Ca

Relays switch alternately

Example:

(A) Speed 1 relay OFF

(B) Speed 2 relay ON

after delay of 1 s

TR [°C]

Q H

10285D21

C

Q14

Q24

Q34

SpH SpC

a a

Y

100%

Y Output signal TR Room temperature SpH Effective heating setpoint SpC Effective cooling setpoint H Heating sequence C Cooling sequence Q14 1. Fan speed 3 Q24 2. Fan speed 3 Q34 3. Fan speed 3

Room unit

Automatic mode

Single-speed (relay Q14)

2-speed (relays Q14, Q24)

Three-speed (relays Q14, Q24 and Q34)

113/166


The fan runs at fan speed 1 for as long as the heating/cooling valve remains partly open, or in the case of an electric heater, while the heater is in operation.

• It is enabled as soon as the controller specifies a valve position or an electric heating output greater than 0.

• It is disabled when the controller specifies a valve position or electric heating output equal to 0 and the minimum fan switch-on time has elapsed.

When the valve is fully open or the electric heater is operating at 100% (in the range marked "a"), a sequence controller enables fan speeds 2 and 3.

In addition to the control deviation, an integrator also comes into operation in the range marked "a". This ensures that the fan switches to speed 2 (and later to speed 3) if the control deviation has remained >0 for a period of time, even if the room temperature has not reached the switching point for fan speed 2.

The fan does not switch back down to speed 2 and later to speed 1 until there has been no control deviation for a period of time. If the room operating mode changes (Comfort, Economy etc.), the sequence controller is reinitialized by the application. This produces the following response: If the room temperature is within the dead band after the change of room operating mode, the controller specifies valve positions of 0%, or in the case of electric heaters, these are disabled, and the fan is switched off. However, any delay time (minimum switch-on time, switch-off delay in conjunction with electric heating coil / reheater or periodic fan kick) is allowed to expire first.

Controller Outputs required

RXB21.1 RXB22.1 3

Q1480283

Q24Q34

1. Stufe2. Stufe3. Stufe

1 ... 3-stufiger Ventilator

The fan can also be operated via the KNX bus. In S-mode, control is shared between two communication objects:

– Fan command value – Enable fan command value (activates input Fan command value). When Enable fan command value is disabled, the controller controls the fan automatically, and the Fan command value input is disabled. Enable fan command value (Input communication object)

Flags

R W K T U


0 1 1 0 0 1.003

DPT_Enable

no 0 = Disabled / Off

1 = Enabled / On

With FNC03 (electric re-heater) the fan must not be switched off while the re-heater is active, and a fan overrun must be parameterized, in order to avoid overheating. Fan command value (Input communication object)

Flags

R W K T U


0 1 1 0 0 5.001

DPT_Scaling

no 0...100% 0 = 0%

255 = 100%

Controller outputs

KNXR

CO

Warning!

114/166


The values have the following effect:

Value Description (required fan speed)

1-stage 2-stage 3-stage

0% Off Off Off

0.5 ... 33 % On 1 1

33,5 ... 66,5 % On 1 2

67 ... 100 % On 2 2

100 % On 2 3

If "fan= 0" is commanded via bus, the controller realizes this indirectly by setting the occupancy status to Standby ant thus the effective room operating mode to Precomfort or Economy. The room unit will indicate this as .

In rare cases the room temperature will exceed the setpoints of Standby / Eco, and the fan will start, despite the overrun command. The time between a bus command and the reaction of the fan may be up to 5-6 sec. The effective fan speed is available in the following S-mode output communication object:

Fan output (Output communication object)

Flags

R W K T U


1 0 1 1 0 5.001

DPT_Scaling

yes 0...100% 0 = 0%

255 = 100%

In LTE mode, the value for the fan is transmitted as follows:

Fan output (Output)


FanSpeed

Geographical zone

393 UFS

User Fan Speed Setting

---

9.2 Fan parameter setting

Select Fan control, Fan speeds.

Note

ETS3 Professional

9.2.1 9.2.2

7.1.2

9.2.4 9.2.3

115/166


Select Fan control:


Parameter (see 9.2.1 ff) Basic setting Range Resolution HandyTool

Fan speed 3-speed (see below) *094

Fan control Auto Manual, Auto *093

Temperature sensor B1 See 7.1.2

Minimum on time 6 min 1 ... 10 min 1 min *095

Fan overrun time 1 min 1 ... 10 min 1 min *098

Periodic fan kick Comfort OFF 0 ... 89 min ; Off 1 min *096 1)

Periodic fan kick Economy OFF 0 ... 359 min ; Off 1 min *097 1)

1) HandyTool: 90 min / 360 min = OFF

9.2.1 Fan speeds and control

The following settings can be selected:

Parameter Description HandyTool

Fan speeds *094

External fan control

No influence on fans by controller or room unit. The fan is e.g. operated manually at the fan coil. The controller switches on relay Q14 in operating state Comfort, thus allowing for enabling fan operation.

Note: For other operating states but Comfort, the fan is enabled by the fan algorithm. Warning! With FNC03 (electric re-heater) the fan must not be switched off while the re-heater is active, and a fan overrun must be assured, in order to avoid overheating.

0

1-speed Single-speed fan control with relay Q14. 1

2-speed Two-speed fan control with relays Q14 and Q24. 2

3-speed Three-speed fan control with relays Q14, Q24 and Q34. 3

ACS Service

9.2.1

9.2.2 7.1.2 9.2.4 9.2.3

116/166


Fan control *093

Auto Fan speeds are changed over automatically (by the room controller). Manual fan speed presetting is possible only in operating state Comfort.

1

Manual No automatic fan control. For example, the fan is operated manually on the fan coil itself and can be enabled via relay Q14 (relay Q14 is ON in Comfort mode).

0

The motors of some fans do not have a sufficiently powerful torque to set the fan in motion at the lowest speed. Multi-speed fans are, therefore, always started at the highest speed and then switched back to fan speed 1.

• This feature also applies to manual fan-speed control via the room unit. • The unused relay outputs are freely available for other purposes (see page 137)

9.2.2 Minimum on time

Each fan speed remains on for a pre-defined minimum period before switching to the next higher speed. This enables the controller to adjust to the fan speed

9.2.3 Fan overrun time (switch-off delay)

When switching off an electric reheater (FNC03, FNC05), it is essential to ensure that the residual heat from the electric heater battery is dissipated. For this reason, the fan is switched off only after a delay. The overrun time can be defined.

9.2.4 Periodic fan kick

If the room temperature is measured with a return air sensor in the fan coil (connected to input B1 at the room controller, see Section 7), the fan must be switched on to ensure that the effective room temperature is measured correctly.

The function "Periodic fan kick" is used for this purpose.

From version V2.36, a reduced functionality (without time values for Comfort and Economy) is available even if no return air sensor is parameterized. Note! For tool architecture reasons, those time values are visible and settable in ACS and in the HandyTool although not supported by the controller.

Fan startup behavior

Notes

Return air sensor

117/166


The fan can be enabled at the lowest speed at regular intervals. While the room temperature remains between the effective setpoints SpH and SpC, fan speed 1 is always on for the predefined minimum runtime after expiry of the duty cycle.

Y

t [h:mm]

Q14

0

10385D22en

Periodic fan kick Minimum on

time Periodic fan

kick Minimum on

time Parameter Basic setting Range Resolution

Periodic fan kick Comfort

OFF (90 min) 1) 0 ... 89 min ; Aus 1 min

Periodic fan kick Economy

OFF (360 min) 1) 0 ... 359 min ; Aus 1 min

1) HandyTool and ACS: 90 min / 360 min = OFF • If the Periodic fan kick is set to 0, then fan speed 1 remains on continuously between

the effective setpoints SpH and SpC.

• With a setting of 90 min. (or 360 min), the display changes to "Off". This indicates that the function is disabled.

• When the measured temperature moves outside the dead band, i.e. above or below the effective heating/cooling setpoint, the fan switches on before the periodic fan kick has expired.

• When the room operating mode switches from Economy to Precomfort or between Precomfort and Comfort, fan speed 1 is enabled for the minimum runtime and the periodic fan kick starts.

• A QAX34.1 room unit displays the value of B1.

Function

Notes

118/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Master/slave 08 Mar 2012

10 Master/slave

Example of a master/slave configuration: Several controllers are installed in an open-plan office. One controller (the master) measures the room temperature and controls the other controllers (slaves) via the KNX bus. This ensures that it will be possible to subdivide the room into smaller rooms, without the need to change the wiring.

BAT B

EIB / KNX-Bus

103

85Z

17

Master Slave Slave

Room 321 Room 322 Room 323

Controller A is configured as the master controller and controls the room temperature. Controllers B are configured as slaves and operate in parallel with Controller A.

• A slave controller may be controlled by one master controller only. A master,

however, can control any number of slaves, subject to the limits of the KNX system (topology, bus load etc.).

• Parallel operation of thermal valves among other factors primarily depends on the supplied voltage. We recommend to parameterize "3rd Party Thermic" for thermal valves regardless of make.

• Master/slave bindings are only possible between controllers with the same version (ASN), featuring the same applications and settings.

Parameter Description

Master Normal control.

Slave The slave controller is controlled by a master controller via the KNX bus. The master and slave controllers operate in parallel. The room temperature is measured only by the master.

STOP Note!

119/166


10.1 S-mode

Master

Slave 1

Slave 2

Slave n

GA1

GA3

GA2

GA4

M/S HVAC controller input

M/S Room unit input

M/S HVAC controller output

M/S Room unit output

103

85Z

18e

n


M/S Room unit input


M/S Room unit input


M/S Room unit input







The following S-mode input and output communication objects are used for the master/slave connection:

Master/Slave HVAC controller output (output comm'object) (Company Specific)

Master/Slave room unit output (output comm'object) (Company Specific)

Master/Slave HVAC controller input (input comm'object) (Company Specific)

Master/Slave room unit input (input comm'object) (Company Specific)

You need four group addresses (GA1 … GA4) independent of the number of slaves.

Select Master/Slave:

KNXR

CO

Note

ETS3 Professional

120/166


10.1.1 Window switch (S-Mode)

For master/slave mode, only the master's window switch is evaluated without special measures, which also influences the slave controllers.

If another window switch is also connected to the slave, it is NOT considered unless you create the following binding:

Master Slave

10385Z118en

DI DI

Window contact Input Window contact Output

This binding ensures that both controllers react when a window is opened. If several slaves are equipped with window switches, the correct evaluation is required for the logic block.

10.1.2 Presence detector (S-mode)

For master/slave mode, only the master's presence detector is evaluated without special measures, which also influences the slave controllers.

If another presence detector is also connected to the slave, it is NOT considered unless you create the following binding:

Master Slave

10385Z119en

DI DI

Presence detector Input Presence detector Output

This binding ensures that both controllers react when a presence detector becomes active. If several slaves are equipped with presence detectors, the correct evaluation is required for the logic block.

__

121/166


10.2 LTE mode with zones

The master/slave configuration is also possible in LTE mode. However, you do not need to create the individual bindings, but instead define the master/slave zone.

Here too, the following applies: The slaves must be controlled by only one master, and master/slave bindings are only possible between controllers with the same version (ASN) featuring the same applications and settings.

Select Master / Slave:

M S S Room 321 322 323

Geogr. zone 5.1.1 5.2.1 5.3.1

Master / Slave Master Slave Slave

M/S zone 5.1.1 5.1.1 5.1.1

Geogr. zone und M/S zones need not be the same. However, every day work is easier because you see directly to which master a slave belongs. Select Master/Slave:

ETS3 Professional

Example

Note

ACS Service

122/166


• The master/slave function requires that all 3 M/S zones have the same name • If the master/slave function is not required, the M/S zone should be disabled (to limit

the load on the bus).


*021 Master/Slave Master

*022 Master/Slave zone (apart.) 1

*023 Master/Slave zone (room) –1 (out of service)

*024 Master/Slave zone (subzone) 1

Parameter Setting HandyTool

*021 Master/Slave Master 1

Slave 0

10.2.1 Window switch (LTE mode)

For master/slave mode, only the master's window switch is evaluated without special measures, which also influences the slave controllers.

Window switches on the slaves are NOT considered.

10.2.2 Presence detector (LTE mode)

For master/slave mode, only the master's presence detector is evaluated without special measures, which also influences the slave controllers.

Presence detectors on the slaves are NOT considered.

Notes

123/166


10.3 Peripheral functions

The room controllers and room units can be configured as master or slave devices. A number of rules must be adhered to in this process.

When more than one room unit is used in a master/slave configuration, all such room units must be of the type with a button for setpoint adjustment. In the case of room units with a mechanical setpoint adjuster, only one room unit may be connected. (Room units with mechanical setpoint adjusters and those with pushbuttons for setpoint adjustment must not be combined.)

The same principle applies to the RXC10.1 room controller, which incorporates a temperature sensor and mechanical setpoint adjuster.

• Room units with pushbutton setpoint adjustment (more than one of this type allowed)

RXB... RXB... 10

385

Z23

QAX34.1

Master Slave

KNX / EIB

QAX34.1

• Room units with a mechanical setpoint adjustment (only one unit of this type allowed)

QAX31.1,QAX33.1

RXB... RXB...Master Slave

KNX / EIB

10

385

Z24

- +

Auto

Room units with a mechanical setpoint adjuster must NOT be used in configurations where the room unit is connected via the room controller to a building automation system and controlled via bus by Setpoint shift for heating / cooling (see page 74).

• Do not use more than one room unit with a mechanical setpoint adjuster

RXB... RXB...

- +

Auto

QAX33.1

Master Slave

KNX / EIB

- +

Auto

QAX33.1

10

385

Z25

• Do not combine room units with mechanical setpoint adjusters and room units with push-buttons for setpoint adjustment.

RXB... RXB...

- +

Auto

QAX33.1

Master Slave

KNX / EIB

QAX34.1

10

385Z

26

Room units in master / slave configurations

Permissible combinations

STOP Caution

Prohibited combinations

124/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies General and central functions 08 Mar 2012

11 General and central functions

The following functions are enabled or configured via Edit parameters, General functions or Central functions.

ETS3 Professional

11.1

See Section

2.6

11.2 11.3 11.4

11.5

11.8

11.10, 11.14

11.16

125/166


The following functions are enabled or configured under General or Central functions.

*) Room number and Device name do not influence the application; they are used only for plant documentation purposes. We recommend to use this feature.

HandyTool The general and central functions are set with parameters 117 – 137. For detailed information, refer to the individual sections.

ACS Service

11.2

11.3 11.4

*) 11.16

126/166


11.1 Send heartbeat and receive timeouts

In a KNX network, S-mode and LTE mode communication objects can be exchanged between individual devices. The Receive timeout defines the period of time within which all the communication objects requested from a device must have been received at least once. If a communication object is not received within this period, a predefined value is used and an error message is generated. This ensures that interruptions in communication are identified at an early stage.

Similarly, the Send heartbeat defines the period of time within which all the communication objects requested must be transmitted at least once.

The time intervals are based on the size of the network. Normally the basic setting can be retained. In the case of S-mode communication objects, shorter times may be selected for smaller networks or for test purposes. The Receive timeout must always be longer than the Send heartbeat. Parameter Basic setting Range Resolution

Receive timeout 60 min 0 ... 105 min 5 min

Send heartbeat 45 min 0 ... 105 min 5 min

(0 = Not enabled) Fixed times are specified, as follows:

– Receive timeout: 31 min – Send heartbeat: 15 min


*128 Receive timeout 60 min

*127 Send heartbeat 45 min

S-mode

LTE mode and S-mode

127/166


11.2 Digital inputs

The following volt-free contacts can be connected to digital inputs D1 and D2:

• Presence detector or window contact (for details of this function see Section 5). • Safety thermostat electric heating coil / reheater (for details of this function, see

page 95). • Safety thermostat outdoor temperature (for details of this function, see page 103).

Digital input Function Type of operation HandyTool

Input 1 Input 2

*113 *114

Not used by the application

Free: Bus = 1 = Contact closed Free: Bus = 1 = Contact open

0= Default1

(Contact may be used freely (see page 137 )

Occupancy Occupied = Contact closed Occupied = Contact open

2 3

Window Window open = Contact open Window open = Contact closed

45

Safety thermostat el. heating coil

Overtemp = Contact open Overtemp = Contact closed

16 17

Safety thermostat Outside temperature

OT < frost = Contact closed OT < frost = Contact open (applications with outside air damper only)

32 33

Do not connect the same type of sensor/functions to both digital inputs. The controller would ignore the second input.

11.3 Temporary Comfort mode

If the room controller is set to Economy mode and the associated room unit is switched to Auto (Comfort), the controller maintains Comfort mode for the period defined by the temporary occupancy override time (veto) and then switches to Economy.This function is only available if the room unit concerned has a /Auto switch (see also pages 42

and 53).

Parameter

Basic setting

Range

Resolution

HandyTool

Temporary Comfort mode 60 min 0 ... 360 min 1 min *117

11.4 Presence detector switch-on and switch-off delay

A switch-on or switch-off delay can be applied to the presence detector function. The room controller only switches to Comfort or to Precomfort or Economy mode when the delay time has expired.

Parameter

Basic setting

Range

Resolution

HandyTool

On delay occupancy detector 5 min 0 ... 90 min 1 min *119

Off-delay occupancy detector 5 min 0 ... 90 min 1 min *120

Note

128/166


11.5 Heating and cooling demand

To provide the required heating or cooling energy, the heating and/or cooling demand from each room is transmitted to the building automation and control system.

Refer to the application example in section 3.4 for more detailed information on heating/cooling demand. In the case of changeover applications the real demand is transmitted, independent from the state of the changeover input (therefore it might be that a controller demands heat, if c/o = cooling and room temp < SpH). With ETS3 Professional, this function can be disabled in the room controller. This parameter is not supported.

HandyTool See parameters in the last column of the table below


Heating demand signal Heating demand transmitted to the BAC system. *131

Cooling demand signal Cooling demand transmitted to the BAC system. *132

Parameter Range Basic setting

*131, *132 0 = disabled, 1 = enabled 1 = enabled

The heating or cooling demand can be evaluated via the following S-mode communication object.

Energy demand room (Output communication object)

Flags

R W C T U


1 0 1 1 0 6.001

DPT_Percent_V8

yes –100...100% : (-128 ... +127)

–100% = Full heat

+100% = Full cool

In LTE mode the energy demand is determined by two signals:

Heating coil energy demand (Output)


EnergyDemAH

Distr. zone, heating

154 AHDTTU

Air Heater Energy Demand

Transformer TU

Siemens:

Synco RMH760

RMU710 / 20 / 30

RMB795 / RMS705

Cooling coil energy demand (Output)


EnergyDemAC

Distr.zone, cooling

217 ACDTTU

Air Cooler Energy Demand

Transformer TU

Siemens:

Synco RMU710 / 20 / 30

RMB795 / RMS705

Note

ETS3 Professional

ACS Service

KNXR

CO

129/166


FNC18 generates an additional energy demand signal for the heating surface:

Energy demand heating surface (Output)


EnergyDemRD

Distr zone, heating

153 RHDTTU

Radiator Energy Demand

Transformer TU

Siemens:

Synco RMH760

RMU710 / 20 / 30

RMB795 / RMS705

The energy demand is independent of the changeover signal!

11.6 Heating/cooling signal output

The heating/cooling status display is mapped to a building automation and control system via the following S-mode communication object (applies to States 1, 3, 20):

Effective application mode (Output communication object)

Flags

R W C T U


1 0 1 1 0 20.105

DPT_HVACContrMode

yes 1 = Heat 3 = Cool 20 = No demand

11.7 Special functions

The special functions described in sections 11.8 ff are triggered by the following S-mode communication object:

Application mode (Input communication object)

Flags

R W C T U


0 1 1 0 0 20.105

DPT_HVACContrMode

yes 0 = Auto 1 = Heat 2 = Morning Warmup 3 = Cool 4 = Night Purge 5 = Precool 6 = Off 7 = Test *) 8 = Emergency Heat 9 = Fan Only 10 = Freecool Other states not used

*) Exit from Test mode (7) is only possible with sequence Off (6) + normal mode (0).

The following communication object is used in LTE mode:

Application mode (Input)


ContrMode

Timeswitch

zone

104 PMC Programs to HVAC-Mode Conversion

109 BOS Building/Occ-Mode Source 115 HVACOPT HVAC Optimizer

Siemens:

Synco RMB795

Note

KNXR

CO

KNXR

CO

130/166


State Description See section

Para-meter

0 = Auto Controller operating normally.

1 = Heat Controller can operate in heating mode only; cooling sequence disabled.

--

2 = Morning Warmup Boost heating. 11.8 *134

3 = Cool Controller can operate in cooling mode only; heating sequence disabled.

--

4 = Night Purge

Night purge: Precool room with fan (no cooling coil) (only FNC10, FNC12 with outside air damper)

11.9 *138

5 = Precool

Precool: Precool the room with fan, cooling coil and outside air damper.

11.10 *135

6 = Off The temperature control is disabled. The remaining functions are active. Communications are operating as normal.

--

7 = Test *) All functions disabled. Motorized valve and damper actuators synchronized. Outputs can be overridden via KNX bus.

11.11

8 = Emergency Heat Emergency heating (always enabled). 11.12

9 = Fan only Rapid ventilation (formerly Air flush) Max. ventilation using outside air (FNC10, FNC12 with outside air damper only).

11.13 *136

10 = Freecool Free cooling: • During Economy. Precool room using

cooling coil (low energy tariffs). • During Comfort normal mode.

11.14 *135

*) Exit from Test mode (7) is only possible with sequence Off (6) + normal mode (0). Triggering the special functions by the building automation and control system can be disabled in each room controller via tool.

ETS3 Professional Go to the Functions menu for the disable feature.

HandyTool See parameters in the last column of the above table.

11.8 Boost heating (Morning Warmup, 2)

This function is used to raise the temperature in a room as quickly as possible to the Precomfort heating setpoint at the end of the night setback period.

Objective: Preheat the room for heating.

Description of the various modes

Disable special functions

131/166


100

0TR

Y [%]

103

85D

23e

n

SpHPcf SpCPcf

Fan Heating coil

The following conditions must be fulfilled: – The room controller must be in Economy mode.

The function can be disabled in the room controller by means of the ETS3 tool. The function must be enabled via the building automation and control system (communication object Application mode, see page 129). The function is disabled via the building automation and control system.

11.9 Night purge (Night Purge, 4), (FNC10, FNC12)

This function is used to cool rooms to the Comfort cooling setpoint, in readiness for normal occupancy, using the outside air damper. Here, only the fan is active, not the cooling coil.

Objective: Save energy by using "free of charge", cold outside air.

100

TR0

Y [%]

SpHCmf SpCCmf

102

85D

24

Ventilator

The following condition must be fulfilled:

– FNC must have an outside air damper. – The outside air damper must not be disabled – The room controller must be in Economy mode. – The outside air temperature must be lower than the room temperature

(Hysteresis = 1K)

The function can be disabled in the room controller by means of the ETS3 tool; see Central functions, page 124. The function must be enabled via the building automation and control system (communication object Application mode, see page 129). – The function is disabled via the building automation and control system. – When the outside air damper is disabled


Initiating the function

Terminating the function




132/166


11.10 Precooling (Precool, 5)

This function is used to cool rooms to the Comfort cooling setpoint, in readiness for normal occupancy. The fan and cooling coil are used here to precool the rooms.

100

TR

103

85D

25

0

Y [%]

SpHCmf SpCCmf

Fan Cooling coil


– The room controller must be in Economy or Precomfort mode.

The function can be disabled in the room controller by means of the ETS3 tool , together with Free cooling, see central functions, page 124. The function must be enabled via the building automation and control system (communication object Application mode, see page 129). The function is disabled via the building automation and control system.

11.11 Test mode (Test, 7)

The following override functions are used to commission the controller and for service purposes, e.g. to test a valve actuator. The controller must first be switched to HVAC test mode by transmitting the value 7=TEST via Application mode.

To quit test mode, first transmit 6=OFF, and then 0=AUTO. In test mode, the valves, air dampers, electric heating coils and fans can be set to defined values via KNX bus signals. A soft reset is carried out when the controller exits from Test mode:

– Motorized valve actuators and dampers are synchronized. – Thermal valves are preheated (see page 86). – The control algorithm but not the complete application is restarted. Test mode is possible only with S-mode objects!




Test mode

Aggregates

Soft reset

Limitations

133/166


11.12 Emergency heating (Emergency Heat, 8)

This function is used for emergency heating when the room temperature or return air temperature drops below the frost protection setpoint. The function is independent of the effective room operating mode.

It affects the control of all installed heating equipment.

When using a radiator and a heated ceiling the valve opens 100 %. An electric radiator is switched to the highest stage and remains there until the temperature rises above the Protection heating setpoint again.

When the room temperature rises above the Protection setpoint, the controller reverts to the original room operation mode (see 129).

Normal operationTR

10

38

5D

26

SpFr SpHPrt

Emergency Heat


– The building temperature must be below the Frost setpoint.

The function can NOT be disabled in the room controller by means of the ETS3 tool. The function must be enabled via the building automation and control system (communication object Application mode, see page 129). – The function is disabled via the building automation and control system – When the room temperature rises above the Protection setpoint.

11.13 Rapid ventilation (Fan only, 9)

This function (formerly Air flush) is only used in Precomfort and Economy room operating modes.

The aim is to flush the building with as much outside air as possible to renew the room air.

To achieve the maximum air change rate, the outside air damper (if available) is opened fully (FNC10, FNC12).

Temperature control is switched off and the heating and cooling coils are disabled.

Outside air is only introduced if the room temperature is between the Economy heating and Economy cooling setpoints.




134/166


100

TR

10

38

5D

27

0

Y [%]

SpHEco SpCEco

0.5K

Fan


– The room controller must be in Economy or Precomfort mode.

The function can be disabled in the room controller by means of the ETS3 tool; see Central functions, page 124.

The function must be enabled via the building automation and control system (communication object Application mode, see page 129). The function is terminated:

– when the controller switches from Economy or Precomfort to another operating mode.

– when the function is disabled via the building automation and control system – when the safety thermostat in the outside air duct indicates frost (see also

"Alarming", below).

11.14 Free cooling (Freecool, 10)

This function is used to precool rooms to the Comfort cooling setpoint, in readiness for normal occupancy. It uses both fan and cooling coil. This function is meaningful only if low-tariff energy is available.

During occupancy (Comfort / Precomfort) normal mode applies.

100

TR

103

85D

28

0

Y [%]

SpHCmf SpCCmf

Fan Cooling coil

The function can be disabled in the room controller by means of the ETS3 tool , together with Pre-cooling, see central functions, page 124. The function must be enabled via the building automation and control system (communication object Application mode, see page 129). The function is disabled via the building automation and control system.







135/166


11.15 Alarm

Alarms differ in S-mode and LTE mode.

RXB controllers support different alarms:

• Room temperature frost If the room temperature or the return temperature in a fan-coil application drops below the fixed frost protection limit (5 °C or adjustable for outside air applications), an alarm is generated.

• Outside air temperature frost

In applications with outside air damper, a safety thermo-stat in the outside air duct can be connected to the digital input.

• Overheating alarm If the digital input of an RXB22.... controller is used as an overheating alarm (see page 95), the information is transmitted in this alarm message.

• Supply air sensor error, Room sensor error

Sensor fault or short circuit.

• PPS2 fault If the PPS2 communication between a controller and the room unit is interrupted, or the room unit has an internal fault, the information is transmitted in this alarm message.

11.15.1 S-mode

In S-mode, the above described alarms are provided as a common alarm.

The alarm message is mapped to the following S-mode output communication object:

Common alarm (Output communication object)

Flags

R W C T U


1 0 1 1 0 1.005

DPT_Alarm

yes 0 = No alarm

1 = Alarm

As soon as the cause of the alarm ceases to exist, the alarm message disappears. In addition, output Alarm info provides more detailed information:

Alarm info (Output communication object)

Flags

R W C T U

Type Send heartbeat Info

1 0 1 1 0 219.001

DPT_AlarmInfo

yes See Konnex specification

Output Alarm info can be enabled or disabled via another communication object: (this influences also the LTE-Mode alarm signal)

Enable alarm info (Input communication object)

Flags

R W C T U


0 1 1 0 0 1.003

DPT_Enable

Ja (fix 42 hours) 0 = Disabled

1 = Enabled

KNXR

CO

Note

136/166


11.15.2 LTE mode

Enable alarm info can be operated in LTE mode. Two further types of information are provided as outputs: AlarmInfo_CS and AlarmText_CS. Together with Synco, users do not need to note if the bindings are created automatically.

Here, the device listens on the bus and sends an alarm when it has highest alarm priority. This ensures that the management station does not miss any alarms.

AlarmInfo_CS (Output)


AlarmInfo_CS

Broadcast

Siemens Synco RMU710 / 20 / 30, RMH760, RMB795, RMS705

AlarmText_CS (Output)


AlarmText_CS

Broadcast


EnableAlarmInfo (Input)


EnableAlarmInfo

Broadcast


Error code Short name

4910 RXB room temp. sensor error

4920 RXB room temperature frost

4940 RXB outside temperature frost

4950 RXB el air heater overtemp

4960 RXB general fault

4925 RXB supply air temp sensor error

4970 RXB PPS fault

For more information on the alarm concept, see "Communication on the bus, Synco700 & RXB", CE1P3127.

11.16 Reset the setpoint shift

When the system changes from Comfort or Precomfort to Economy or Protection mode (see page 74), the setpoint shift can be canceled. This function can be enabled and disabled via Central functions. The setpoint adjustment can only be cancelled with the QAX34.1 and QAX84.1 room units, which have an LCD display. Enabling this function in room units with a mechanical setpoint adjuster (potentiometer) will cause errors in data transmission.

Display on a Synco device:

STOP Note!

137/166


HandyTool Parameter Description Range Basic setting

*137 Reset setpoint offset 0 = Disabled 1 = Enabled

Disabled

11.17 Free inputs/outputs

In a building automation and control system, the free I/Os can be used to interrogate switch states, for example, or for direct switch control of another device over the network. However, these functions are not suitable for time-critical processes (<1 s).

Free inputs can be defined as "open" or "closed" (see 11.2).

If not already in use, the following inputs and outputs can be used freely:

RXB21.1/FC-10 Appli-cation

Digital inputs

Outputs (Triac) Outputs (relay)

D1 D2 Y1 Y2 Y3 Y4 Q24 Q34

FNC02 ♦ ♦ • •

FNC04 ♦ ♦

FNC08 ♦ ♦

FNC20 ♦ ♦ X X • •

RXB21.1/FC-11 Appli-

cation Digital inputs

Outputs (Triac) Outputs (relay)

D1 D2 Y1 Y2 Y3 Y4 Q24 Q34

FNC10 ♦ ♦ X X

FNC12 ♦ ♦ X X

FNC18 ♦ ♦ ∅ 1) ∅ 1) 2) 2)

1) Heating surface valve 2) Fan-coil valve

RXB22.1/FC-12 Appli-cation

Digital inputs

Outputs (Triac) Outputs (Relay)

D1 D2 Y1 Y2 Q24 Q34 Q44

FNC03 ♦ ♦ X

FNC05 ♦ ♦ X

Digital inputs ♦ If "Not used" (see page 127), may be used freely for other

purposes. Triac outputs X Used by the application • May be used freely for other purposes Only freely usable with bus valve actuators

Only freely usable with bus valve actuators All combinations: see CM110672)

∅ Not freely usable

Relay outputs X Used by the application May be used freely in applications with single-speed or

2-speed fan, (see page 115). The setting of parameters for unused inputs is described in Section 11.2, page 127.

Key

138/166


11.17.1 Digital inputs on the KNX bus

D1

D2

RXB... Room controller

Digital input 1

Digital input 2

10385Z19en

The following S-mode input and output communication objects are used when taking advantage of spare inputs and outputs:

Digital input 1 (Output communication object) Digital input 2 (Output communication object)

Flags

R W C T U


1 0 1 1 0 1.001 DPT_Switch

no 0 (see 11.2) 1

Parameter setting in the tool Cause Digital input

Effect: Bus output

Not used: Bus = 1 = closed closed 1

open 0

Not used: Bus = 1 = open open 1

closed 0

11.17.2 KNX signals on digital/analog outputs

Y1

Q24


Triac Y1

Relay Q24

10385Z22en

Triac Y1 (Input communication object) Triac Y2 (Input communication object) Triac Y3 (Input communication object) Triac Y4 (Input communication object) Relay Q24 (Input communication object) Relay Q34 (Input communication object)

Flags R W C T U


0 1 1 0 0 1.001 DPT_Switch

no 0 = Off (voltage-free) 1 = On (AC 24V)

KNXR

CO

139/166


11.17.3 Mapping the sensor B1 to the Konnex bus

B1


Analog input B1

10385Z201en

Temperature sensor B1 can also be connected to the bus in S-mode as a universal temperature (e.g. outside temperature). To do this, the temperature sensor must be parameterized as "only meas value acquisition" (see page 76.)

Analog input B1 (Output communication object)

Flags

R W C T U


1 0 1 1 0 9.001 DPT_Value_Temp

Yes

11.18 Software version

The present software version can be read via the HandyTool (not available for devices with index A).

HandyTool

Parameter HandyTool

Application set *236 424 = RXB21.1/FC-10

425 = RXB21.1/FC-11

426 = RXB22.1/FC-12

427 = RXL21.1/FC-10

428 = RXL21.1/FC-11

429 = RXL22.1/FC-12

Application version *237 *)

Operating system version *238 *)

KNX interface version *239 *)

*) This information serves to identify the controller's software version. You can use it in

case of a service request.

11.19 Device state

If the application is ready (loaded and tested), parameter 240 is set to 1.

HandyTool

Parameter HandyTool

Device state *240

In Service mode the device state is always = 0 because the application is not running.

Hinweis

140/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Room unit 08 Mar 2012

12 Room unit

Select Room unit:

Select Room unit:


Short name Basic setting HandyTool

Measured value correction 0.0 K *101

Setpoint adjustment range ± 3 K *103

Local Comfort mode Enabled *105

Room unit (Handy tool: fixed as "With LCD") Without LCD --

Temperature unit (only room units with LCD) Degrees Celsius *108

Standard display (only room units with LCD) Room temperature *109

Standard display (only room units with LCD) Relative *110

ETS3 Professional

ACS Service

Parameters

141/166


The measured value of the built-in temperature sensor can be recalibrated to compensate for radiation from a cold wall, for example.

Parameter Basic setting Range Resolution HandyTool

Measured value correction 0 K – 3 ... 3 K 0,1 K *101

This correction is also valid for a sensor that is connected to the analog input B1 (but not for a bus sensor). The maximum setpoint adjustment range is as follows (see also page 74).

Parameter Basic setting Range Resolution HandyTool

Setpoint adjustment range ± 3 K ± 0 ... 10 K 1 K *103

A management station can use the communication object Enable Comfort (see page 59) to prevent the room operating mode from being higher than Economy (energy conservation). Local comfort mode can be ignored by setting the following parameter:


Local Comfort mode switch from Economy to Comfort or Precomfort mode *105

Enabled (basic setting). This means that Comfort or Precomfort may be disabled by the input Local comfort mode.

1

Disabled (Ignore Local comfort mode). Comfort or Precomfort may NOT be disabled by the input Local comfort mode.

2

You can choose if the room unit is equipped with an LCD display. If so, the parameters hereafter can also be set. The HandyTool has a fixed setting "With LCD".

Parameter Description Basic setting

Room unit Without LCD / With LCD Without LCD

The display of the heating and cooling symbols can be enabled or disabled. Note that this applies only to room units with an LCD display.

Symbols: Cooling sequence active

Heating sequence active

Parameter Description Basic setting

Heating/cooling symbol display

Heating and cooling symbols are displayed

Enabled

The room temperature can be displayed either in Celsius (°C) or Fahrenheit (°F). Note that this applies only to room units with an LCD display.

Parameter Value HandyTool

Temperature unit (only room units with LCD) *108

Celsius (°C) (basic setting) 1 Fahrenheit (°F) 0

Sensor correction

Note

Setpoint adjustment range

Local comfort mode (in LTE mode only)

Room unit

Displaying heating and cooling symbols (ETS only)

Selecting the temperature unit

142/166


In room units with an LCD panel, it is also possible to select the temperature value to be displayed. (Normal mode = setpoint not shifted or setpoint shift canceled).

Parameter LCD display HandyTool Standard display Basic setting: Room temperature

(only room units with LCD). *109

No display

Setpoint

Room temperature

Displays only the room operating mode and, if activated, the heating or cooling symbol.

Effective temperature setpoint (average value from heating and cooling setpoints) e.g. SpH = 21 °C and SpC = 24 °C.

Effective room temperature used as the input to the controller (basic setting)

96

48

2

In room units with an LCD, it is possible to define what is to be displayed in the event of a setpoint shift.

Parameter LCD display HandyTool Setpoint display (only room units with LCD). *110

Relative Shift value e.g. +3.0K (basic setting) 0 Absolute Effective temperature setpoint, e.g. 23.0 °C

(Mean value between heating and cooling setpoint). 4

If "Absolute setpoint adjustment" is selected, the LCD panel displays a scale which illustrates the adjustment as it happens:

10385Z20

To reset the setpoint shift, refer to page 136.

Temperature display in normal mode

Temperature display in the case of a setpoint shift

Note

143/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies KNX information 08 Mar 2012

13 KNX information 13.1 Reset and startup response

A reset is initiated under the following circumstances:

• Processor failure(e.g. watchdog). • After a power failure. • After a bus power failure. • Upon completion of a self test (using the communication object "StatusRequest"). • Via ETS (without a startup delay):

– After the download of the physical address. – After the download of the parameters. – Via ETS (Commissioning, Reset).

• After parameter setting in ACS. • After leaving the parameter setting mode in the HandyTool. • After test with the HandyTool. The application is restarted after every reset. Depending on the controller address, this may take 1 ... 255 s.

Then, the bus connection is opened and all connected valve actuators are synchronized. This takes the following time depending on application and actuator type: – Typically 170 s for closing (runtime + 10%) for motorized actuators. – 300 s ON and 300 s OFF (3rd party: 400 + 400 s) for thermal actuators. The application is placed in a safe state. Any outputs that are not synchronized are not operated (triac outputs = 0, and relay = open). Normal operation is resumed after synchronization. When the controller exist the test mode, only a soft reset is carried out: – The valve actuators and dampers are synchronized. – The control algorithm, but not the complete application, is restarted. • Each time the control sequence reaches 0% or 100%, a limit position

synchronization takes place. – For motorized actuators close or open during (runtime + 10%). – 300 s ON and 300 s OFF (3rd party: 400 s) for thermal actuators.

13.2 LED flashing pattern

An LED is located at the controller's bottom right indicating the operating state by various flashing patterns:

Green, flashing Normal operation. Red, flashing Programming mode for address assignment (ETS3 / ACS). Orange / green, flashing

• Startup phase (see above 13.1) • No application selected (see 4.1). • Loading. – Download from ETS3 or ACS. – Room unit QAX34.3 in HandyTool mode.

Reset

Note

144/166


Other patterns After switching on the operating voltage, the controller flashes for 3 to 5 seconds in different patterns. If other patterns appear during normal operation, this indicates an error.

13.3 Startup delay

After a reset, it takes up to 5 minutes for all the connected room controllers 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 controllers transmit data at the same time. The delay is determined by the controller's device address.

13.4 Bus load

In a large KNX system, the bus load can be a problem, especially with central commands which cause the controllers to send status information simultaneously. This can even result in the loss of data telegrams.

The management station is normally connected to the KNX bus via the area line. Special attention needs to be paid to the load on the bus to avoid a bottleneck on the area line. A bus load which may be acceptable on individual lines causes an overload on the main lines and the area line.

To avoid a KNX communications overload, note the following rules and precautions:

• Define a rational topology, divided into lines and areas.

• If possible, avoid functions across lines: Place sensors and actuators on the same line.

• Load filter tables for the line and area couplers so that the entire system is not burdened with information which is only required locally.

• Be rational about integration into a management station or display: Only integrate information which is genuinely needed.

• For status messages, automatic transmission is not necessary if the display device can actively read the values. The flags must be set accordingly in the ETS.

• Do not define too short an interval.

• Central commands which affect a large number of controllers should be divided over several group addresses, and transmission should be staggered.

• Each group address must have a receiver to acknowledge the telegram, otherwise unwanted repeat-telegrams are generated.

• For additional hints for reducing the bus load see pages 25 and 90.

145/166


13.5 S-mode communication objects for FNC 13.5.1 S-mode input communication objects

Flags: R Read T Transmit

W Write U Update

C Communication ) C.S. = Company-specific For internal use only

Name Flags: Data point type (KONNEX) Receive See

R W C T U timeout page Application mode 0 1 1 0 0 20.105 DPT_HVACContrMode yes 129 Comfort cooling setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Comfort heating setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Cooling valve override 0 1 1 0 0 8.010 DPT_Percent_V16 No 91 Damper override 0 1 1 0 0 8.010 DPT_Percent_V16 No 94, 108Economy cooling setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Economy heating setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Enable alarm info 0 1 1 0 0 1.003 DPT_Enable Yes 135 Enable electric heating 0 1 1 0 0 1.003 DPT_Enable Yes 98 Enable fan command value 0 1 1 0 0 1.003 DPT_Enable No 113 Fan command value 0 1 1 0 0 5.001 DPT_Scaling No 113 H/C changeover input 0 1 1 0 0 1.100 DPT_Heat/Cool Yes 84 Heating surface valve override 0 1 1 0 0 8.010 DPT_Percent_V16 No 103 Heating valve override 0 1 1 0 0 8.010 DPT_Percent_V16 No 91 Master/slave HVAC controller input

0 1 1 0 0 C.S. 1) 13 Byte Yes 119

Master/Slave room unit input 0 1 1 0 0 C.S. 1) 4 Byte Yes 119 Outside air temperature. 0 1 1 1 1 9.001 DPT_Value_Temp Yes 80 Precomfort cooling setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Precomfort heating setpoint 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Presence detector input 0 1 1 0 0 1.018 DPT_Occupancy No 40 Release dampers 0 1 1 0 0 1.003 DPT_Enable Yes 107 Relay Q24 0 1 1 0 0 1.001 DPT_Switch No 138 Relay Q34 0 1 1 0 0 1.001 DPT_Switch No 138 Return air temperature input 0 1 1 1 1 9.001 DPT_Value_Temp Yes 79 Room temperature input 0 1 1 1 1 9.001 DPT_Value_Temp Yes 79 Schedule occupancy 0 1 1 0 0 20.003 DPT_OccMode Yes 39 Schedule room operating mode

0 1 1 0 0 20.102 DPT_HVACMode Yes 49

Schedule usage 0 1 1 0 0 20.002 DPT_BuildingMode Yes 38 Setpoint offset 0 1 1 0 0 9.002 DPT_Value_Tempd No 74 Setpoint ... (6 indiv. values) 0 1 1 0 0 9.001 DPT_Value_Temp No 72 Setpoints cooling 0 1 1 0 0 222.100 DPT_TempRoomSetpSetF16[3] No 72 Setpoints heating 0 1 1 0 0 222.100 DPT_TempRoomSetpSetF16[3] No 72 Setpoint shift cooling 0 1 1 0 0 222.101 DPT_TempRoomSetpSetShiftF16[3] Yes 74 Setpoint shift heating 0 1 1 0 0 222.101 DPT_TempRoomSetpSetShiftF16[3] Yes 74 Status request 0 1 1 0 0 C.S. 1) 1 Byte No 143 Supply air temperature input 0 1 1 1 1 9.001 DPT_Value_Temp Yes 111 Temporary Comfort mode 0 1 1 0 0 1.017 DPT_Trigger No Triac Y1 0 1 1 0 0 1.001 DPT_Switch No 138 Triac Y2 0 1 1 0 0 1.001 DPT_Switch No 138 Triac Y3 0 1 1 0 0 1.001 DPT_Switch No 138 Triac Y4 0 1 1 0 0 1.001 DPT_Switch No 138 Window switch input 0 1 1 0 0 1.019 DPT_Window_Door No

146/166


13.5.2 S-mode output communication objects

Flags: R Read T Transmit

W Write U Update

C Communication 1) C.S. = Company specific For internal use only

Name Flags: Data point type (KONNEX) Send See

R W C T U heartbeat page Alarm info 1 0 1 1 0 219.001 DPT_AlarmInfo yes 135

Analog input B1 1 0 1 1 0 9.001 DPT_Value_Temp yes 139

Common alarm. 1 0 1 1 0 1.005 DPT_Alarm yes 135

Cooling coil output 1 0 1 1 0 5.001 DPT_Scaling yes 89, 93

Digital input 1 1 0 1 1 0 1.001 DPT_Switch no 138

Digital input 2 1 0 1 1 0 1.001 DPT_Switch no 138

Effective application mode 1 0 1 1 0 20.105 DPT_HVACContrMode yes 129

Effective occupancy 1 0 1 1 0 20.003 DPT_OccMode yes 41, 51

Effective room operating mode 1 0 1 1 0 20.102 DPT_HVACMode yes 43, 54

Effective room operating mode Comfort

1 0 1 1 0 1.001 DPT_Switch yes 43, 54

Effective room operating mode Economy

1 0 1 1 0 1.001 DPT_Switch yes 43, 54

Effective room operating mode Precomfort

1 0 1 1 0 1.001 DPT_Switch yes 43, 54

Effective room operating mode Protection

1 0 1 1 0 1.001 DPT_Switch yes 43, 54

Effective room temperature 1 0 1 1 0 9.001 DPT_Value_Temp yes 78

Effective setpoint 1 0 1 1 0 9.001 DPT_Value_Temp yes 70

Effective setpoint cooling 1 0 1 1 0 9.001 DPT_Value_Temp yes 70

Effective setpoint heating 1 0 1 1 0 9.001 DPT_Value_Temp yes 70

Effective setpoint offset 1 0 1 1 0 9.002 DPT_Value_Tempd yes 75

Electrical power 1 0 1 1 0 9.024 DPT_Power yes 100

Energy demand room 1 0 1 1 0 6.001 DPT_Percent_V8 yes 128

Fan output 1 0 1 1 0 5.001 DPT_Scaling yes 114

Heating coil output 1 0 1 1 0 5.001 DPT_Scaling yes 89, 93

Heating/cooling output 1 0 1 1 0 1.100 DPT_Heat/Cool yes 84

Heating outp bus el heating 1 0 1 1 0 5.001 DPT_Scaling yes 97

Heating surface output 1 0 1 1 0 5.001 DPT_Scaling yes 102

Master/slave HVAC controller output

1 0 1 1 0 C.S. 1) 13 Byte yes 119

Master/Slave room unit output 1 0 1 1 0 C.S. 1) 4 Byte yes 119

Outside air damper. 1 0 1 1 0 5.001 DPT_Scaling yes 108

Presence detector output 1 0 1 1 0 1.018 DPT_Occupancy yes 40

Present setpoint. 1 0 1 1 0 9.001 DPT_Value_Temp yes 70

Present setpoint ... (6 indiv. values)

1 0 1 1 0 9.001 DPT_Value_Temp yes

Present setpoints cooling 1 0 1 1 0 222.100 DPT_TempRoomSetpSetF16[3] yes 70

Present setpoints heating 1 0 1 1 0 222.100 DPT_TempRoomSetpSetF16[3] yes 70

Return air temperature output 1 0 1 1 0 9.001 DPT_Value_Temp yes 78

Room temperature output 1 0 1 1 0 9.001 DPT_Value_Temp yes 78

Status 1 0 1 1 0 C.S. 1) 2 Byte no 143

Supply air temperature output 1 0 1 1 0 9.001 DPT_Value_Temp yes 111

Window switch output 1 0 1 1 0 1.019 DPT_Window_Door yes 37, 49

147/166


103

85z2

1

13.6 LTEmode communication objects

Page Communication objects RXB fan-coil controller Communication objects Page

Time switch zone A.R.W

59 Room operating mode

59 Enable Comfort

129 Application mode

Geographical zone A.R.W

80 Room temperature Room temperature output 79

80 Return air temperature Return air temperature output 79

73 Setpoints heating Heating coil output 90

73 Setpoints cooling Cooling coil output 90

74 Setpoint adjustment Heating surface output 102

74 Setpoint shift heating Fan output 114

74 Setpoint shift cooling or electrical:

98 Enable electric heater Heating output bus electric 97 108 Outside air damper heating

107 Enable dampers Supply air temperature output 111

Outside air temp. zone

80 Outside air temperature input

Heat distr zone heating coil

Heating coil energy demand 128

84 H/C changeover input Refrig distr zone cooling coil zone

Cooling coil energy demand 128

Heat distr zone heating surface

Energy demand heating surface 129

Master/slave zone

121 M/S HVACcontroller input A.R.S M/S HVACcontroller output 121

121 M/S room unit input M/S room unit output 121

Broadcast

136 Enable alarm info Alarm info CS 136

Alarm text CS 136

The RXB2… fan-coil controllers incorporate the following Konnex function blocks:

– RSMHD 100 Room Setpoint Manager HVAC-Mode Driven – FCC 258 Fan Coil Control – RTS 321 Room Temperature Sensor – RNATS 323 Return Air Temperature Sensor – FSA 372 Fan Speed Actuator – ALSrc 1002 Alarm Source

Function blocks

148/166


13.7 HandyTool parameters by number

Visible FC-10 FC-11 FC-12

Par

amet

er N

o.

D

escr

iptio

n se

e pa

ge

Name

d =

Dis

play

(d

ispl

ay o

nly)

(

Mod

e 2

)

P =

Par

amet

er (

Mod

e 3

)

("

Lim

par

am. s

ettin

g")

S =

Ser

vice

(M

ode

6)

("

Ext

. par

am. s

ettin

g")

FN

C02

FN

C04

FN

C08

FN

C20

FN

C10

FN

C12

FN

C18

FN

C03

FN

C05

001 18 Physical address (area address) d P S X X X X X X X X X 002 18 Physical address (line address) d P S X X X X X X X X X 003 18 Physical address (device address) d P S X X X X X X X X X 005 32 Plant type d S X X X X X X X X X 006 23 Communications mode. d S X X X X X X X X X 008 25 Geographical zone (apartment) d P S X X X X X X X X X 009 25 Geographical zone (room) d P S X X X X X X X X X 010 25 Geographical zone (subzone) d P S X X X X X X X X X 011 25 Time switch zone (apartment) d P S X X X X X X X X X 012 25 Time switch zone (room) d P S X X X X X X X X X 013 25 Time switch zone (subzone) d P S X X X X X X X X X 014 25 Heat distribution zone air heater. d P S X X X X X X X X X 015 25 Cold distribution zone air cooler. d P S X X X X X X X X X 016 25 Heat distr zone heating surface d P S X

8) X 8)

X

018 25 Outside temperature zone d P S X X X 021 122 Master/slave. d P S X X X X X X X X X 022 122 Master/slave zone (apartment) d P S X X X X X X X X X 023 122 Master/slave zone (room) d S X X X X X X X X X 024 122 Master/slave zone (subzone) d S X X X X X X X X X 030 72 Protection cooling setpoint d S X X X X X X X X X 031 72 Economy cooling setpoint d P S X X X X X X X X X 032 72 Precomfort cooling setpoint d P S X X X X X X X X X 033 72 Comfort cooling setpoint d P S X X X X X X X X X 034 72 Comfort heating setpoint d P S X X X X X X X X X 035 72 Precomfort heating setpoint d P S X X X X X X X X X 036 72 Economy heating setpoint d P S X X X X X X X X X 037 72 Protection heating setpoint d S X X X X X X X X X 038 110 Minimum supply air temperature d P S X 039 110 Maximum supply air temperature d P S X 040 72 Risk of frost limit d S X X 050 83 Control sequence d S X X X X 056 99 Electric heater d S X X 057 100 Power consumption el heater d S X X 060 87 Actuator type H/C coil valve d S X X X X X X X X 061 88,

93 Running time damper heating d S X X X X

1) X X X X X

062 88, 93

Running time damper cooling d S X8)

X X X 2)

X 8)

X X 8)

X8)

X

063 102 Actuator type heat surf valve d S X 064 102 Running time heat surface valve d S X 066 102 Offset heating surface valve d S X X 070 93 Changeover time damper d S X 071 88 Offset heating valve d S X X 072 88 Offset cooling valve d S X X 073 107 Outside temp min damper pos d S X X 074 107 Running time outside air damper d S X X 075 107 Minimum damper position d S X X 078 105 Outside temp 0% valve pos d S X 079 105 Outside temp max valve pos d S X

149/166



Par

amet

er N

o.

D

escr

iptio

n se

e pa

ge

Name

d =

Dis

play

(d

ispl

ay o

nly)

(

Mod

e 2

)

P =

Par

amet

er (

Mod

e 3

)

("

Lim

par

am. s

ettin

g")

S =

Ser

vice

(M

ode

6)

("

Ext

. par

am. s

ettin

g")

FN

C02

FN

C04

FN

C08

FN

C20

FN

C10

FN

C12

FN

C18

FN

C03

FN

C05

080 105 Max valve position d S X 085 91 Heating outp bus valve

Heating coil outp bus valve d S X X X X X X

XX X

086 102 Heating surface output bus valve actuator

d S X

087 91 Cooling outp bus valve, Cooling coil outp bus valve

d S X X X X 5)

X X X

X X

089 97 Heating outp bus el heating d S X X 092 77 Temperature sensor. d S X X X

9) X X X X X X

093 115 Fan control d S X X X X X X X X X 094 115 Fan speeds d S X X X X X X X X X 095 115 Minimum on time d S X X X X X X X X X 096 115 Periodic fan kick Comfort d S X X X X X X X X X 097 115 Periodic fan kick Eco d S X X X X X X X X X 098 115 Fan overrun time d S X X 101 140,

141 Measured value correction d S X X X X X X X X X

103 140, 141

Setpoint offset range d S X X X X X X X X X

105 59, 140, 141

Local Comfort mode d S X X X X X X X X X

108 140, 141

Temperature unit d S X X X X X X X X X

109 140, 142

Standard display d S X X X X X X X X X

110 140, 142

Setpoint display d S X X X X X X X X X

113 127 Digital input 1 d S X X X X X X X X X 114 127 Digital input 2 d S X X X X X X X X X 117 127 Temporary Comfort mode d S X X X X X X X X X 119 127 On-delay occupancy detector d S X X X X X X X X X 120 127 Off-delay occupancy detector d S X X X X X X X X X 123 124 Room number 7) d S X X X X X X X X X 124 124 Device Name 7) d S X X X X X X X X X 127 126 Send heartbeat d S X X X X X X X X X 128 126 Receive timeout d S X X X X X X X X X 131 128 Heat demand signal d S X X X X X X X X X 132 128 Cooling demand signal d S X X X X X X X X X 134 130 Boost heating d S X X X X X X X X X 135 130 Preecooling (Precool),

Free cooling (Freecool) d S X X X X X X X X X

136 130 Rapid ventilation (earlier: air purge) d S X X X X X X X X X 137 137 Reset setpoint offset d S X X X X X X X X X 138 130 Night purge d S X X X X X X X X X 236 139 Application set d S X X X X X X X X X 237 139 Application version d S X X X X X X X X X 238 139 Operating system version d S X X X X X X X X X 239 139 KNX interface version d S X X X X X X X X X 240 139 Device state d P S X X X X X X X X X

1) HandyTool: In FNC20, runtime damper heating 2) HandyTool: In FNC20, runtime damper cooling

150/166


5) HandyTool: In FNC20, output bus damper actuator 7) HandyTool: Cannot be mapped 8) HandyTool: Visible, but not used by application 9) FNC08: always Supply air

13.8 HandyTool parameters sorted alphabetically


Par

amet

er N

o.

D

escr

iptio

n se

e pa

ge

Name

d =

Dis

play

(d

ispl

ay o

nly)

(

Mod

e 2

)

P =

Par

amet

er (

Mod

e 3

)

("

Lim

par

am. s

ettin

g")

S =

Ser

vice

(M

ode

6)

("

Ext

. par

am. s

ettin

g")

FN

C02

FN

C04

FN

C08

FN

C20

FN

C10

FN

C12

FN

C18

FN

C03

FN

C05

060 87 Actuator type H/C coil valve d S X X X X X X X X 063 102 Actuator type heat surf valve d S X 236 139 Application set d S X X X X X X X X X 237 139 Application version d S X X X X X X X X X 134 130 Boost heating d S X X X X X X X X X 070 93 Changeover time damper d S X 015 25 Cold distribution zone air cooler. d P S X X X X X X X X X 033 72 Comfort cooling setpoint d P S X X X X X X X X X 034 72 Comfort heating setpoint d P S X X X X X X X X X 006 23 Communications mode. d S X X X X X X X X X 050 83 Control sequence d S X X X X 132 128 Cooling demand signal d S X X X X X X X X X 087 91 Cooling outp bus valve,

Cooling coil outp bus valve d S X X X X

5) X X

X X X

124 124 Device Name 7) d S X X X X X X X X X 240 139 Device state d P S X X X X X X X X X 113 127 Digital input 1 d S X X X X X X X X X 114 127 Digital input 2 d S X X X X X X X X X 031 72 Economy cooling setpoint d P S X X X X X X X X X 036 72 Economy heating setpoint d P S X X X X X X X X X 056 99 Electric heater d S X X 093 115 Fan control d S X X X X X X X X X 094 115 Fan speeds d S X X X X X X X X X 098 115 Fan overrun time d S X X 135 130 Free cooling (Freecool)

Preecooling (Precool), d S X X X X X X X X X

008 25 Geographical zone (apartment) d P S X X X X X X X X X 009 25 Geographical zone (room) d P S X X X X X X X X X 010 25 Geographical zone (subzone) d P S X X X X X X X X X 131 128 Heat demand signal d S X X X X X X X X X 014 25 Heat distribution zone air heater. d P S X X X X X X X X X 016 25 Heat distr zone heating surface d P S X

8) X 8)

X

089 97 Heating outp bus el heating d S X X 085 91 Heating outp bus valve

Heating coil outp bus valve d S X X X X X X

X X X

086 102 Heating surface output bus valve actuator

d S X

239 139 KNX interface version d S X X X X X X X X X 105 59,

140, 141

Local Comfort mode d S X X X X X X X X X

021 122 Master/slave d P S X X X X X X X X X

151/166



Par

amet

er N

o.

D

escr

iptio

n se

e pa

ge

Name

d =

Dis

play

(d

ispl

ay o

nly)

(

Mod

e 2

)

P =

Par

amet

er (

Mod

e 3

)

("

Lim

par

am. s

ettin

g")

S =

Ser

vice

(M

ode

6)

("

Ext

. par

am. s

ettin

g")

FN

C02

FN

C04

FN

C08

FN

C20

FN

C10

FN

C12

FN

C18

FN

C03

FN

C05

022 122 Master/slave zone (apartment) d P S X X X X X X X X X 023 122 Master/slave zone (room) d S X X X X X X X X X 024 122 Master/slave zone (subzone) d S X X X X X X X X X 039 110 Maximum supply air temperature d P S X 080 105 Max valve position d S X 101 140,

141 Measured value correction d S X X X X X X X X X

075 107 Minimum damper position d S X X 095 115 Minimum on time d S X X X X X X X X X 038 110 Minimum supply air temperature d P S X 138 130 Night purge d S X X X X X X X X X 072 88 Offset cooling valve d S X X 066 102 Offset heating surface valve d S X X 071 88 Offset heating valve d S X X 120 127 Off-delay occupancy detector d S X X X X X X X X X 119 127 On-delay occupancy detector d S X X X X X X X X X 238 139 Operating system version d S X X X X X X X X X 018 25 Outside temperature zone d P S X X X 078 105 Outside temp 0% valve pos d S X 079 105 Outside temp max valve pos d S X 073 107 Outside temp min damper pos d S X X 096 115 Periodic fan kick Comfort d S X X X X X X X X X 097 115 Periodic fan kick Eco d S X X X X X X X X X 001 18 Physical address (area address) d P S X X X X X X X X X 003 18 Physical address (device address) d P S X X X X X X X X X 002 18 Physical address (line address) d P S X X X X X X X X X 005 32 Plant type d S X X X X X X X X X 057 100 Power consumption el heater d S X X 032 72 Precomfort cooling setpoint d P S X X X X X X X X X 035 72 Precomfort heating setpoint d P S X X X X X X X X X 135 130 Preecooling (Precool),

Free cooling (Freecool) d S X X X X X X X X X

030 72 Protection cooling setpoint d S X X X X X X X X X 037 72 Protection heating setpoint d S X X X X X X X X X 136 130 Rapid ventilation (earlier: air purge) d S X X X X X X X X X 128 126 Receive timeout d S X X X X X X X X X 137 137 Reset setpoint offset d S X X X X X X X X X 040 72 Risk of frost limit d S X X 123 124 Room number 7) d S X X X X X X X X X 062 88,

93 Running time damper cooling d S X

8) X X X

2) X 8)

X X8)

X8)

X

061 88, 93

Running time damper heating d S X X X X 1)

X X X X X

064 102 Running time heat surface valve d S X 074 107 Running time outside air damper d S X X 127 126 Send heartbeat d S X X X X X X X X X 110 140,

142 Setpoint display d S X X X X X X X X X

103 140, 141

Setpoint offset range d S X X X X X X X X X

109 140, 142

Standard display d S X X X X X X X X X

092 77 Temperature sensor. d S X X X 9)

X X X X X X

152/166


Visible FC-10 FC-11 FC-12P

aram

eter

No.

D

escr

iptio

n se

e pa

ge

Name

d =

Dis

play

(d

ispl

ay o

nly)

(

Mod

e 2

)

P =

Par

amet

er (

Mod

e 3

)

("

Lim

par

am. s

ettin

g")

S =

Ser

vice

(M

ode

6)

("

Ext

. par

am. s

ettin

g")

FN

C02

FN

C04

FN

C08

FN

C20

FN

C10

FN

C12

FN

C18

FN

C03

FN

C05

108 140, 141

Temperature unit d S X X X X X X X X X

117 127 Temporary Comfort mode d S X X X X X X X X X 011 25 Time switch zone (apartment) d P S X X X X X X X X X 012 25 Time switch zone (room) d P S X X X X X X X X X 013 25 Time switch zone (subzone) d P S X X X X X X X X X

1) HandyTool: In FNC20, runtime damper heating 2) HandyTool: In FNC20, runtime damper cooling 5) HandyTool: In FNC20, output bus damper actuator 7) HandyTool: Cannot be mapped 8) HandyTool: Visible, but not used by application 9) FNC08: always Supply air

153/166


13.9 HandyTool enumerations

No. Parameter CL

C /

RA

D

FN

C

1 - 3 Physical address X X

5 Plant type X X FC-10 FC-11 FC-12 CC-02

6 Communications mode. X X 0 = S-Mode 1 = FNC02 1 = FNC10 1 = FNC03 1 = CLC01

8 - 10 Geographical zone X X 1 = S+LTE-M 2 = FNC04 2 = FNC12 2 = FNC05 2 = CLC02

11 -13 Time switch zone X X 3 = FNC08 3 = FNC18 3 = RAD01

14 Heat distribution zone air heater. X 4 = FNC20

15 Refrig distribution zone air cooler. X

16 Heat distr zone heating surface X X

17 Refrig distr zone cooling surface X

18 Outside temperature zone X X

21 Master/slave. X X 0 = Slave

22 - 24 Master/slave zone X X 1 = Master

30 - 37 Setpoints X X C: Prot / Eco / Pre-C / Comf H: Comf / Pre-C / Eco / Prot

38 Minimum supply air temperature X

39 Maximum supply air temperature X

40 Risk of frost limit X

50 Control sequence X 0 = c/o / 1 = Cooling / 2 = Heating

51 Actuator type cool surf valve X VA VA = Valve actuators:

52 Running time cool surface valve X

54 Offset cooling surface valve X 1 = on/off 1 = STE71 10 = SSA81 250 = Mot BUS

56 Electric heater X 254 = continuous 3 = STA71 11 = SSB81 252 = El-mech 3rd

57 Power consumption el heater X 4 = STP71 12 = SQS81 253 = Therm. 3rd

60 Actuator type H/C coil valve X VA 5 = STA72E 13 = SSC81 254 = Mot. 3rd

61 Running time damper heating X 6 = STP72E 14 = SSP 81

62 Running time damper cooling X

63 Actuator type heat surf valve X X VA

64 Running time heat surface valve X X

66 Offset heating surface valve X X

70 Changeover time damper X

71 Offset heating valve X

72 Offset cooling valve X

73 Outside temp min damper pos X

74 Running time outside air damper X

75 Minimum damper position X

78 Outside temp 0% valve pos X X

79 Outside temp max valve pos X X

80 Max valve position X

85 Heating (coil) outp bus valve X

86 Heating surface output bus valve actuator X 0 = OFF

87 Cooling (coil) outp bus valve X 1 = ON

88 Cooling surface outp bus valve, X

89 Heating outp bus el heating X

92 Temperature sensor. X X 0 = Ret. air / 1 = Room / 3 = Meas. val. / 255 = No sensor

93 Fan control X 0 = manual / 1 = automatic

94 Fan speeds X 0 = automatic / 1 = 1-stage / 2 = 2-stage / 3 = 3-stage

95 Minimum on time X

96 Periodic fan kick Comfort X

97 Periodic fan kick Eco X

98 Fan overrun time X

101 Measured value correction X X

103 Setpoint offset range X X

105 Local Comfort mode X X 0 = disabled / 1 = enabled

108 Temperature unit X X 0 = °F / 1 = °C

109 Standard display X X 2 = Room temp. / 48 = Setpoint / 96 = No display

110 Setpoint display X X 0 = relative / 4 = absolute

113 Digital input 1 X X 0 = BUS 1 / Contact closed 8 = Dewpt. / Contact closed

114 Digital input 2 X X 1 = BUS 1 / Contact open 9 = Dewpt. / Contact open

117 Temporary Comfort mode X X 2 = Occup / Contact closed 16 = Overt. / Contact open

119 On-delay occupancy detector X X 3 = Occup / Contact open 17 = Overt. / Contact closed

120 Off-delay occupancy detector X X 4 = Wind. open / Contact open 32 = Frost / Contact closed

127 Send heartbeat X X 5 = Wind. open / Contact closed 33 = Frost / Contact open

128 Receive timeout X X

131 Heat demand signal X X

132 Cooling demand signal X X 0 = OFF

134 Boost heating X X 1 = ON

135 Preecooling / Free cooling X X

136 Rapid ventilation (earlier: air purge) X

137 Reset setpoint offset X X

138 Night purge X

236 Application set X X

237 Application version X X

238 Operating system version X X

239 KNX interface version X X

240 Device state X X

.

.

.

.

.

154/166


13.10 Data point type description

Instead of the previously referenced EIS data types, this document now makes reference to the new Konnex data point types. Where possible, the tables which follow do include a reference to the corresponding EIS type.

Data point types

ID Name Format Unit Range/Coding Corresp. to EIS 1.001 DPT_Switch B(1) Bit 0 = OFF

1 = ON EIS1

1.003 DPT_Enable B(1) Bit 0 = Disabled 1 = Enabled

EIS1

1.005 DPT_Alarm B(1) Bit 0 = No alarm 1 = Alarm

EIS1

1.017 DPT_Trigger B(1) Bit 0 = (not used) 1 = Trigger

EIS1

1.018 DPT_Occupancy B(1) Bit 0 = Unoccupied 1 = Occupied

EIS1

1.019 DPT_Window_Door B(1) Bit 0 = Closed 1 = Open

EIS1

1.100 DPT_HeatCool B(1) Bit 0 = Cooling 1 = Heating

EIS1

5.001 DPT_Scaling U(8) % 0...100% 0 = 0% 255 = 100%

EIS6

5.004 DPT_RelPosValve U(8) % 0...100% 0 = 0% 255 = 255%

EIS6

6.001 DPT_Percent_V8 V(8) % -100%...+100% -100 = -100% +100 = +100%

(EIS14)

8.010 DPT_Percent_V16 V(16) % -100%...+100% -10000 = -100% 0 = 0% +10000 = +100%

EIS10

9.001 DPT_Value_Temp F(16) °C Floating point EIS5 9.002 DPT_Value_Tempd F(16) K Floating point EIS5 9.024 DPT_Value_Tempd F(16) kW Floating Point EIS5 20.002 DPT_BuildingMode N(8) Enum. 0 = In use

1 = Not in use 2 = Protection

(EIS14)

20.003 DPT_OccMode N(8) Enum. 0 = Occupied 1 = Standby 2 = Unoccupied

(EIS14)

20.102 DPT_HVACMode N(8) Enum. 0 = Auto 1 = Comfort 2 = Precomfort 3 = Economy 4 = Protection

(EIS14)

20.105 DPT_HVACContr Mode

N(8) Enum. 0 = Auto 1 = Heat 2 = Morning Warmup 3 = Cool 4 = Night Purge 5 = Precool 6 = Off 7 = Test 8 = Emergency Heat 9 = Fan only 10 = Free Cool 11 = Ice 20 = noDem 255 = NUL Other: Reserved

(EIS14)

155/166


ID Name Format Unit Range/Coding Corresp. to EIS 219.001 DPT_AlarmInfo U(8)U(8)

N(8)N(8) B(8)B(8)

-- Alarm description --

222.100 DPT_TempRoom SetpSetF16[3]

F(16)F(16)F(16) °C 3 floating point values - Comfort - Precomfort - Economy

NEW (3 x EIS5)

222.101 DPT_TempRoom SetpSetShiftF16[3]

F(16)F(16)F(16) K 3 floating point values - Comfort - Precomfort - Economy

NEW (3 x EIS5)

156/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies FAQs 08 Mar 2012

14 FAQs

What happens if the parameter download process is interrupted? (power failure, bus failure etc.) The parameter set loaded into the controller will be incomplete. The controller will not start up properly. For example, the fan may run but the valves do not open. You will have to download the parameters again. Why does the controller fail to start after a parameter download? (Applies to HandyTool, ACS or ETS) Parameter download was probably interrupted or exposed to interference. Reload the controller with the entire parameter set (via HandyTool, ACS or ETS). Why does the controller not start after adjusting certain parameters? (applies to HandyTool.) Parameter download probably interrupted or fault, or controller unloaded via ETS. A complete parameter set must be loaded in the controller (via HandyTool, ACS or ETS). Why does the HandyTool not display parameter 1 upon quick quit and restart of the Display mode? Communication to the HandyTool is relatively slow. You need to wait a brief moment before reopening the Display mode. Why does the HandyTool display "uuuu"? The controller to which the HandyTool is connected does not support the Test mode (RXB2x controllers with index A). Other parameters have been changed so that the selected parameter became irrele-vant. Just continue your work;. the problem will disappear when the parameterization is started again. ACS: Why is reading back parameters so slow? Check to make sure that neither the operating booklet nor the plant image is active. Both applications cause a lot of bus traffic and thus slow down reading back parameters.

Question:

Answer:

Question:

Answer:

Question:

Answer:

Question:

Answer:

Question:

Answer 1:

Answer 2:

Question:

Answer:

157/166


ACS: Parameter download does not work, why? Make sure that the parameter tree is expanded prior to download.

Wrong Right

Download sometimes also works with a collapsed parameter tree. Why can I not parameterize the controller via HandyTool in service mode (n6)? There are two reasons: • Download (HandyTool, ACS or ETS) was not exited correctly (interrupted). • The controller was set to "unloaded" via ETS. Solution: Carry out a full download (via HandyTool, ACS or ETS). The parameter download was probably interrupted or exposed to interference. Download the parameters again. Why does a controller with thermal valves not respond immediately when it is enabled in the plant graphics in the ACS view and in the DESIGO graphics? After start-up, the thermal valves are preheated first. This is not shown in the plant graphics. However, if the room temperature is outside the dead band during this period, the fan switches to Speed 1. Why doesn’t the master/slave binding work? Master/slave zones must be identical for master and slave. Create master/slave group addresses and add communication object.

Question:

Answer:

Note

Question:

Answer:

Answer:

Question:

Answer:

Question:

Answer for LTE mode:

Answer for S-mode:

158/166


With master/slave configurations, why do the QAX34 room units not always show the same temperature values? The master-controller and slave-controller data is synchronized at regular intervals. If a value changes just after synchronization, it may differ for a few minutes until it is resynchronized. Why does the slave window contact/presence detector contact have no effect? For the window/presence detector contact, the slave can only be integrated via the CFC. Suitable compounds are available in the library: [WndStaDtr] and [OcStaDtr]. For one slave controller: Create group addresses for the window/presence detector contact and add the communication object of the master and slave. For one or multiple slave controllers : In CFC with the compounds [WndStaDtr] and [OcStaDtr].. Why do the ACS plant graphics not always display all values (e.g. room operating mode)? The controller is configured as a slave. These values are not available with slave controllers. Why doesn’t the ACS Operator Book show the current data? After a change of application (e.g. from FNC12 to FNC18) you first need to update the reference data points. Why doesn’t the ACS Operator Book show the current data? After a change of application (e.g. from FNC12 to FNC18) you first need to update the reference data points. Why doesn't an RXB controller transmit S-Mode communication objects that it has received? RXB controller do not work as bus relays. If a communication object is required, the binding must be to the source, not to the RXB controller. Example: an RXB controller receives the room temperature from a bus sensor. A bus display is used to display the room temperature. The display must get the signal directly from the bus sensor.

Question:

Answer:

Question:

Answer for LTE mode:

Answer for S-mode:

Question

Answer

Question

Answer

Question

Answer

Question

Answer

159/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Integrate RXB in DESIGO/Synco 08 Mar 2012

15 Integrate RXB in DESIGO/Synco

Combinations of RXB controllers with Synco and a DESIGO integration are possible and certainly make sense.

However, certain combinations must be excluded; for others, certain boundary conditions must be respected.

In the following sections the most common combinations are presented. Key

Display

Time scheduler

Heating demand Cooling demand

1038

5D6

9

15.1 Case 1: Integration into Synco

• Communication: – between controllers LTE mode via zones – with ACS: Individual addressing

• RXB display: ACS • Synco display: ACS • RXB time scheduler: from Synco • Energy demand: to Synco

Geographical zone

Geographical zone

Geographical zone Timeswitch zone Heating demand zone Cooling demand zone 1

0385

D61

RXB

RXB

RXB

Synco Synco Synco

ACS7..

FLNKonnex

Individual addressing

160/166


15.2 Case 2: Integration into DESIGO

• Communication: – between controllers S-Mode – with DESIGO: Individual addressing or S-Mode

• RXB display: DESIGO • RXB time scheduler: from DESIGO • Energy demand: to DESIGO

103

85

D63

PXC... PXC... PX KNX

RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

161/166


15.3 Case 3: Display in DESIGO, with shared Synco time scheduler

• Communication: – between controllers LTE mode via zones – with DESIGO: Individual addressing or S-Mode

• RXB display: DESIGO • Synco display: DESIGO • RXB time scheduler: from Synco • Energy demand: to Synco The DESIGO time scheduler must be disabled by a specialist. Reason: Integration by means of individual addressing treats the time scheduler and display as one package. They subsequently need to be separated.

Geographical zone Geographical zone Geographical zone Timeswitch zone Heating demand zone Cooling demand zone

103

85

D64


RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

Synco Synco Synco

STOP Important note

162/166


15.4 Case 4: Display in DESIGO/Synco, with shared Synco time scheduler

• Communication: – between controllers LTE mode via zones – with DESIGO: Individual addressing or S-Mode – with ACS: Individual addressing

• RXB display: DESIGO and ACS • Synco display: DESIGO and ACS • RXB time scheduler: from Synco • Energy demand: to Synco • The DESIGO time scheduler must be disabled by a specialist. • In theory simultaneous display via DESIGO and Synco is possible. However,

problems do arise with the manipulation of values (heartbeat, “last one rules”)

Geographical zone Geographical zone Geographical zone Timeswitch zone Heating demand zone Cooling demand zone 1

038

5D

65


RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

Synco Synco Synco

ACS7...

STOP Important note

163/166


15.5 Case 5: Display in DESIGO, and separate time schedulers

• Communication: – between controllers LTE mode via zones – with DESIGO: Individual addressing or S-Mode

• RXB display: DESIGO • Synco display: DESIGO • RXB time scheduler: from DESIGO • Energy demand: to Synco • The RXB controllers use the DESIGO time scheduler • The Synco controllers need a local Synco time schedule • The two schedules must be kept synchronous


038

5D

66


RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

Synco Synco Synco

STOP Important note

164/166


15.6 Case 6: Separate display, and separate time schedulers


• RXB display: DESIGO • Synco display: ACS • RXB time scheduler: from DESIGO • Energy demand: to Synco • The RXB controllers use the DESIGO time scheduler • The Synco controllers need a local Synco time schedule • The two schedules must be synchronous at all times

Geographical zone Geographical zone Geographical zone Timeswitch zone Heating demand zone Cooling demand zone

1038

5D67


RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

Synco Synco Synco

ACS7..

STOP Important note

165/166


15.7 Case 7: Separate display, and shared Synco time scheduler


• RXB display: DESIGO • Synco display: ACS • RXB time scheduler: from Synco • Energy demand: to Synco The DESIGO time scheduler must be disabled by a specialist.


038

5D

68


RXB

RXB

RXB

DESIGOINSIGHT

ALN

FLNKonnex


PXM20

Synco Synco Synco

ACS7..

STOP Important note

166/166

Siemens RXB (KNX) application library FNC Description of functions for FC-10, FC-11, FC-12 CM110385en_07 Building Technologies Working with different tools 08 Mar 2012

16 Working with different tools

It is possible to prepare the RXB controllers in the office by setting the parameters in advance, so that only the physical address has to be entered on site. The HandyTool contains a “limited” parameter-setting option which can be used for this purpose. The preparatory work would then probably be carried out with ACS or ETS rather than with the HandyTool. Special caution is required (in relation to data consistency) when using more than one tool.

Step 1 Step 2

HandyTool ACS Service ETS

HandyTool () * X **

ACS X **

ETS X *** X ***

* An upload is necessary to avoid losing the data from Step 1 ** No ETS project (therefore no upload possible) *** The ETS project is NOT updated If a controller has been commissioned with ETS in S-Mode and is now being used with ACS in LTE-Mode:

You must delete the group addresses separately with ETS; otherwise communication problems may occur.

Note