Operating Instructions
Table Of Contents
- RXB (KNX) applications library
- CLC and RAD description of functions for CC-02
- Table of contents
- 1 Introduction
- 2 Definitions / Tools
- 3 Select communications mode
- 4 Applications / Parameters
- 5 Room operating modes
- 5.1 Description
- 5.2 Overview
- 5.3 Determine the room operating mode with DESIGO (S-mode)
- 5.3.1 Local control of room operating mode via a window contact
- 5.3.2 Central control of room operating mode via input from the Use schedule
- 5.3.3 Central and local control of room operating modebased on occupancy
- 5.3.4 Central control of room operating mode via room operating mode schedule
- 5.3.5 Local control of room operating mode with a room unit
- 5.3.6 Local control of room operating mode via the Temporary Comfort mode input
- 5.3.7 Effective room operating mode
- 5.3.8 DESIGO examples
- 5.4 Determine the room operating mode with third-party products (S-mode)
- 5.4.1 Local control of room operating mode via window contact input
- 5.4.2 Central control of room operating mode with an input from the room operating mode schedule
- 5.4.3 Central control of the room operating mode via the schedules Use and Occupancy
- 5.4.4 Central and local control of room operating mode based on occupancy
- 5.4.5 Local control of room operating mode with a room unit
- 5.4.6 Local control of room operating mode via the Temporary Comfort mode input
- 5.4.7 Effective room operating mode
- 5.4.8 Third-party (S-mode) examples
- 5.5 Determine the room operating mode with Synco (LTE mode)
- 5.5.1 Local control of room operating mode via window contact input
- 5.5.2 Central room operating mode control via Enable Comfort
- 5.5.3 Central control of room operating mode via room operating mode input
- 5.5.4 Local control of room operating mode via presence detector
- 5.5.5 Local control of room operating mode with a room unit
- 5.5.6 LTE mode examples
- 5.6 Determine the room operating mode without a bus (stand-alone)
- 6 Setpoint calculation
- 7 Temperature measurement
- 8 Control sequences
- 9 Master/slave
- 10 General / central functions
- 10.1 Send heartbeat and Receive timeout
- 10.2 Digital inputs
- 10.3 Temporary Comfort mode
- 10.4 Presence detector switch-on and switch-off delay
- 10.5 Heating and cooling demand
- 10.6 Heating/cooling signal output
- 10.7 Special functions
- 10.8 Morning boost (Morning Warmup, 2)
- 10.9 Precooling (Precool, 5)
- 10.10 Test mode (Test, 7)
- 10.11 Emergency heat (8)
- 10.12 Free cooling (Freecool, 10)
- 10.13 Alarm
- 10.14 Reset setpoint shift
- 10.15 Free inputs/outputs
- 10.16 Software version
- 10.17 Device state
- 11 Room unit
- 12 KNX information
- 12.1 Reset and startup response
- 12.2 LED flashing pattern
- 12.3 Startup delay
- 12.4 Bus load
- 12.5 S-mode communication objects for RAD/CLC
- 12.6 LTE-mode communication objects
- 12.7 HandyTool parameters by number
- 12.8 HandyTool parameters, alphabetical
- 12.9 HandyTool enumerations
- 12.10 Data point type description
- 13 FAQ
- 14 Integration of RXB in DESIGO/Synco
- 14.1 Case 1: Integration in Synco
- 14.2 Case 2: Integration in DESIGO
- 14.3 Case 3: Display in DESIGO, with shared Synco schedule
- 14.4 Case 4: Display in DESIGO/Synco, with shared Synco schedule
- 14.5 Case 5: Display in DESIGO, separate schedules
- 14.6 Case 6: Separate display, separate schedules
- 14.7 Case 7: Separate display, shared Synco schedule
- 15 Working with different tools
118/140
Siemens RXB (KNX) Applications library CLC and RAD description of functions for CC-02 CM110384en_04
Building Technologies KNX information 21 Sep 2010
12.3 Startup delay
After a reset, it takes up to 5 minutes for all connected room controllers to restart. This
is designed to avoid overloading the mains power supply at startup. 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 device address of the controller.
12.4 Bus load
In a large KNX system, bus load can be a problem especially with central commands
which cause the controllers to send state 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. This
line thus requires special attention on bus load, as it can become the system’s
bottleneck: The bus load acceptable on individual lines results in overload on the main
lines and area line.
To avoid a KNX communications overload, note the following rules and precautions:
Define a rational topology, divided into lines and areas.
Avoid cross-line functions: place sensor and actuators on the same line if possible.
Load filter tables for the line and area couplers so that local information does not
burden the entire system.
Meaningful integration in management station or visualization: Integrate only
information that is really required.
For state 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 between heartbeats.
Divide central commands which affect a large number of controllers over several
group addresses, and stagger transmission.
Each group address must have a recipient to acknowledge the telegram, otherwise
unwanted repeat-telegrams are generated.
Further notes on reducing bus load, see pages 23 and 83.