Maed212tp en V2.1.0 Ekinex Spa PDF

Application manual
Wall mounting KNX Pushbuttons

with Thermostat
EK-ED2-TP 2-4 rockers Series ‘FF
EK-E12-TP 1-4 rockers Series ’71
Application manual
KNX pushbutton interfaces with thermostat EK-ED2-TP/ EK-E12-TP
Summary
1 Scope of the document.................................................................................................................................. 5
2 Product description ........................................................................................................................................ 6
2.1 Completion of the device ....................................................................................................................... 6
2.2 Rocker functions .................................................................................................................................... 9
2.3 LED indicators ........................................................................................................................................ 9
2.4 Customization of rocker plates .............................................................................................................. 9
3 Switching, display and connection elements ...............................................................................................10
4 Configuration ...............................................................................................................................................12
5 Commissioning ............................................................................................................................................12
6 Function description ....................................................................................................................................13
6.1 Offline operation ...................................................................................................................................13
6.2 Online operation ...................................................................................................................................13
6.3 Software working cycle ........................................................................................................................14
6.4 Pushbutton inputs ................................................................................................................................14
6.4.1 Pushbutton input events ...............................................................................................................14
6.4.2 Lock function ................................................................................................................................14
6.4.3 State variables (communication objects) .....................................................................................14
6.4.4 Binding between Events and Communication objects .................................................................15
6.4.5 Repeated send .............................................................................................................................15
6.4.6 Input coupling ...............................................................................................................................15
6.4.7 Single or independent input mode ...............................................................................................16
6.4.8 Coupled input mode .....................................................................................................................16
6.4.9 Dimming function .........................................................................................................................18
6.4.10 Shutter / venetian blind function ...................................................................................................20
6.5 LED indicators ......................................................................................................................................23
6.5.1 General parameters .....................................................................................................................23
6.5.2 Individual parameters ...................................................................................................................23
6.5.3 Technical Alarm indicator .............................................................................................................23
6.6 Temperature sensor .............................................................................................................................24
6.6.1 Temperature sensor .....................................................................................................................24
6.7 Room thermostat .................................................................................................................................25
6.7.1 Use of sensors .............................................................................................................................25
6.7.2 Applications ..................................................................................................................................25
6.7.3 Control algorithms ........................................................................................................................25
6.7.3.1 Two-point control with hysteresis .............................................................................. 26
6.7.3.2 Continuous Proportional-Integral control .................................................................. 27
6.7.3.3 PWM Proportional-Integral control ............................................................................ 29
6.7.4 Setpoint management ..................................................................................................................30
6.7.5 Operating modes ..........................................................................................................................31
6.7.6 Heating/cooling switch over .........................................................................................................32
6.7.7 Window switch management .......................................................................................................33
6.7.8 Valve protection function ..............................................................................................................33
6.7.9 Temperature control alarm ...........................................................................................................33
6.8 Logic functions .....................................................................................................................................35
Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

© EKINEX S.p.A. – All rights reserved Pag. 2
Application manual
7 Application program for ETS .......................................................................................................................38

7.1 About EK-ED2-TP and EK-E12-TP .....................................................................................................39
7.2 General settings ...................................................................................................................................40
7.3 Internal sensors ...................................................................................................................................45
7.3.1 Temperature sensor .....................................................................................................................45
7.4 Rockers configuration ..........................................................................................................................47
7.4.1 Independent or single: send values or sequences.......................................................................48
7.4.2 Independent or single: dimming ...................................................................................................48
7.4.3 Independent or single: shutter or venetian blind ..........................................................................49
7.4.4 Independent or single: scene .......................................................................................................49
7.4.5 Coupled: switch ............................................................................................................................50
7.4.6 Coupled: dimming ........................................................................................................................50
7.4.7 Coupled: shutter or venetian blind ...............................................................................................50
7.5 Rocker x: Function A/B configuration ...................................................................................................50
7.5.1 Independent or single ...................................................................................................................50
7.5.2 Independent or single: Lock function enabled .............................................................................52
7.5.3 Independent or single: send values or sequences.......................................................................53
7.5.4 Independent or single: dimming ...................................................................................................56
7.5.5 Independent or single: shutter or venetian blind ..........................................................................57
7.5.6 Independent or single: scene .......................................................................................................58
7.5.7 Coupled ........................................................................................................................................59
7.5.8 Coupled: Lock function enabled ...................................................................................................59
7.5.9 Coupled: switch ............................................................................................................................59
7.5.10 Coupled: dimming ........................................................................................................................60
7.5.11 Coupled: shutter or venetian blind ...............................................................................................61
7.6 LED configuration ................................................................................................................................62
7.7 Temperature control .............................................................................................................................64
7.7.1 Settings ........................................................................................................................................64
7.7.2 Monitoring and remote control of the conduction mode ...............................................................66
7.7.3 Remote operative mode modification ..........................................................................................67
7.7.4 Remote Setpoint modification ......................................................................................................68
7.7.5 Sensors from bus .........................................................................................................................69
7.7.6 Weighted temperature value ........................................................................................................70
7.7.7 Heating .........................................................................................................................................71
7.7.8 Cooling .........................................................................................................................................73
7.8 Logic functions .....................................................................................................................................76
7.8.1 Parameter and communication object tables ...............................................................................76
8 Appendix ......................................................................................................................................................78
8.1 Summary of KNX communication objects ...........................................................................................78
8.2 Warning ................................................................................................................................................81
8.3 Other information .................................................................................................................................81

Application manual
Notes for EK-ED2-TP
Revision Modifications Date

2.1.0 Deleted all references to light sensor 09/03/2020
2.0.0 Updating of the internal temperature controller with related structure of c.o. database. 16/05/2017
1.1.0 Updating of the c.o. indexes in internal database. 30/01/2017
1.0.0 Emission. 23/03/2016
Notes for EK-E12-TP
Revision Modifications Date

2.1.0 Deleted all references to light sensor 09/03/2020
2.0.0 Updating of the internal temperature controller with related structure of c.o. database. 16/05/2017
1.1.0 Updating of the c.o. indexes in internal database. 30/01/2017
1.0.4 Adding of cross reference to the versions with BG (blue-green) and RW (red-white) LED 04/09/2015
Adding of logic functions. In the 4 rectuangular rockers configuration, it was reintroduced the
1.0.3 28/08/2015
possibility to control each rocker as a unique rocker, with function A in parallel to function B.
1.0.2 Updating of temperature control, continuous regulator. 04/08/2015
1.0.1 First emission. 04/05/2015

Application manual
1 Scope of the document

This application manual describes application details for ekinex® pushbutton interface EK-ED2-TP (2-4
rockers) and for ekinex® pushbutton interface EK-E12-TP (1-4 rockers).
The document is aimed at the system configurator as a description and reference of device features and
application programming. For installation, mechanical and electrical details of the device please refer to the
technical description datasheet.
Application manual and application programs for ETS are available for download at www.ekinex.com.
Item File name (## = release) Version Device rel. Update

Product datasheet STEKED32TP_EN.pdf EK-ED2-TP
Application manual MAEKED12TP_EN.pdf EK-ED2-TP A2.0 06/2017
Application program APEKED2TP##.knxprod EK-ED2-TP
Item File name (## = release) Version Device rel. Update

Product datasheet STEKE122TP_EN .pdf EK-E12-TP
Application manual MAEKED12TP_EN.pdf EK-E12-TP A2.0 06/2017
Application program APEKE12TP##.knxprod EK-E12-TP
You can access the most up-to-date version of the full documentation for the device using following QR codes:
2-4 rocker interface EK-ED2-TP: 1-4 rocker interface EK-E12-TP:

Application manual
2 Product description
The ekinex® KNX 4-rocker pushbutton unit is a wall-mounting device for on/off switching of loads, dimming of
lighting devices, control of motor drives or other programmable switching and control functions. The pushbutton
is equipped with an integrated temperature sensor and can act as a room probe or thermostat, both in heating
and cooling mode. When acting as a room thermostat, the device is not equipped with a user interface for
displaying room conditions and modifying the setpoint temperature; therefore, it must be paired with an external
supervision device. Terminals such as radiators, electrical radiators and radiant panels can be controlled.
This unit is equipped with an integrated KNX bus communication module and is designed for wall installation;
commands are constituted by rockers with 2 active plus a neutral rest position. The device has also two
programmable LEDs for each function which can be used for instance as a status signal or orientation
nightlight.
For final use, this unit must be completed with frontal plates for commands and a frame, which must be ordered
separately in order to obtain the desired aesthetic look; regardless of the detail, several kinds of plates are
available (square or rectangular) which can be combined in order to obtain different rockers’ combinations.
The device is powered by the KNX bus line with a 30 VDC SELV voltage and does not require auxiliary power.
Number and type of

Product code Rocker size Frame
rockers
EK-ED2-TP (blue-green led couples) Form or Flank
EK-ED2-TP-RW (red-white led couples) series
2 rectangular vertical 40 x 80 mm
EK-ED2-TP-BG-NF (no frame line, blue- 4 square 40 x 80 mm
green led couples)
4 rectangular horizontal 80 x 20 mm No frame
EK-ED2-TP-RW-NF (no frame line, red-
white led couples)
Number and type of

Product code Rocker size Frame
rockers
EK-E12-TP (blue-green led couples) Form or Flank
EK-E12-TP-RW (red-white led couples) 1 single square 60x60 mm series
2 rectangular vertical 30x60 mm
EK-E12-TP-BG-NF (no frame line, blue-
green led couples) 4 square 30x30 mm
No frame
EK-E12-TP-RW-NF (no frame line, red- 4 rectangular horizontal 15x60 mm
white led couples)
The supply includes, inside the box:

 1 adapter;
 1 metallic support;
 2 pairs of fixing screws;
 1 KNX terminal block for the connection of the bus line.
2.1 Completion of the device

For full installation and operation, the unit must be completed with:
 A rocker faceplate (according to the chosen number and disposition);

Application manual
 An ekinex® Form or Flank series 1-place square or 2-place rectangular frame (with the exception of
the rocker interfaces of No Frame series NF);
 An ekinex® 1-window square or 2-window rectangular plate
Rocker placement for EK-ED2-TP
Combining the 3 available models of rockers (rectangular vertical, square horizontal and rectangular
horizontal) different configurations are allowed, as shown in the following picture.
Figure 1A - Rocker combination for EK-ED2-TP

Application manual
Rocker placement for EK-E12-TP
Combining the 4 available models of rockers (square single, rectangular vertical, square horizontal and
rectangular horizontal) different configurations are allowed, as shown in the following picture.
Figure 2B - Rocker combination for EK-E12-TP

Application manual
2.2 Rocker functions

Each one of two active positions of the rockers (side for rectangular rockers, superior and inferior for square
ones) corresponds to an action, i.e. an input, or physical pushbutton, of the device. Such actions, in relation to
a single rocker, will be labelled with letters A and B.
When one side of a rocker is pressed, the device sends on the KNX bus the telegram (or sequence) associated
to the corresponding function according to how the device is programmed.
In the most common situation, for instance, one side of the rocker might send an “ON” telegram for a lighting
unit, while the other side would send the “OFF” telegram for the same unit. Another typical application would
be for one side of the rocker to increase the brightness of a dimmed light (and respectively decrease it for the
opposite side), or to raise / lower a curtain or blind and so on.
The two functions associated with a rocker can also be programmed to perform exactly the same operation,
thereby effectively causing one rocker to act as a single pushbutton.
Note for EK-ED2-TP

The use of the entire activation surface of the rocker as if it is a single rocker is programmed by
defining the function B as “in parallel with function A as a single function”. This use is configurable
only in combinations a), b) and c) (see Figure 1 in the previous page): for instance, it is possible to
i link only one function to combination a) with a single square rocker.
In combination d) with 4 rectangular horizontal rockers it is possible to link only functions other than
function A and function B.
2.3 LED indicators

Each one of the 2 rocker sides is equipped with 4 high efficiency couple of LEDs with different color
combinations blue/green and red/white, which can be freely programmed (also with functions not related to
the rockers’ functions) e.g. as status feedbacks of the loads or as orientation nightlight.
For a more detailed description of LED position and related settings please refer to the application section of
this manual.
2.4 Customization of rocker plates

Rocker plates can be customized with predefined symbols and texts. On request, a customization is also
possible with symbols and texts chosen by the customer. For more information see the standard library on the
ekinex® catalogue or the website www.ekinex.com.
For further technical information, please also refer to the product datasheet available on the
i website www.ekinex.com.

Application manual
3 Switching, display and connection elements

The front side of the device is fitted with mounting hooks for the rocker faceplates; between the hooks there
are the pushbuttons and on the lateral sides the LEDs for status indication are placed.
On the rear side, the device is equipped with a programming pushbutton, a programming status LED and
terminals for connecting the KNX bus line.
Fig. 2A - Switching, display and connection elements for EK-ED2-TP
1. Rocker faceplate hooks

5. Programming LED
2. LED diffusers
6. Terminal block for KNX bus line
3. Temperature sensor
7. Adapter
4. Programming pushbutton

Application manual
Fig. 2B- Switching, display and connection elements for EK-E12-TP
1. Rocker faceplate hooks

5. Programming LED
2. LED diffusers
6. Terminal block for KNX bus line
3. Temperature sensor
7. Adapter
4. Programming pushbutton

Application manual
4 Configuration
The exact functionality of the device depends on the software settings.
In order to configure and commission the device you need ETS4 or later releases and the ekinex® application
program, (namely APEKED2TPxx.knxprod for EK-ED2-TP and APEKE12TPxx.knxprod for EK-E12-TP);
which can be downloaded from the ekinex website www.ekinex.com.
The application program allows the configuration of all working parameters for the device.
The device-specific application program has to be loaded into ETS or, as alternative, the whole ekinex®
product database can be loaded; at this point, all the instances of the selected device type can be added to
the project.
For every single device, ETS allows to set the operating parameters separately for each function as described
in detail in the following chapters.
The configuration can, and usually will, be performed completely offline; the actual transfer of the programmed
configuration to the device takes place in the commissioning phase.
Communication Group
No. of ETS application software
Product code EAN objects addresses
channels (## = release)
(max no.) (max no.)
EK-ED2-TP 8 APEKED2TP##.knxprod 229 254
Communication Group
No. of ETS application software
Product code EAN objects addresses
channels (## = release)
(max no.) (max no.)
EK-E12-TP 8 APEKE12TP##.knxprod 229 254
Configuration and commissioning of KNX devices require specialized skills; to acquire these
i skills, you should attend training courses at a training centre certified by KNX.
For further information: www.knx.org.
5 Commissioning
After the device has been configured within the ETS project according to user requirements, the commissioning
of the device requires the following activities:
 electrically connect the device, as described in the product datasheet, to the bus line on the final
network or through a purposely setup network for programming;
 apply power to the bus;
 switch the device operation to programming mode by pressing the programming pushbutton located
on the rear side of the housing. In this mode of operation, the programming LED is turned on steady;
 upload the configuration (including the physical address) to the device with the ETS program.
At the end of the upload, the operation of the device automatically returns to normal mode; in this mode the
programming LED is turned off. Now the device is programmed and ready for use on the bus.

Application manual
6 Function description
After switching on the bus, which also acts as a power supply, the device becomes fully functional after a very
short time needed for reinitialization. A delay is programmable for the device to become active on the bus in
order to avoid a bus traffic overload during the first moments of start-up of the whole network.
In case of a bus power failure (voltage lower than 19 V for 1 s or more), the device becomes unreactive: before
the power supply becomes insufficient, the status is internally stored. The timing functions are not active,
neither are the programmed group addresses.
As soon as the bus voltage is restored, the device will resume operation in its previous state (which is saved
on power fail), unless different initialization settings are programmed.
6.1 Offline operation

A fully unprogrammed device does not operate in standby mode. Since the operation relies entirely on the
exchange of information through communication objects, there is no part of the device that can operate
independently from a KNX bus.
6.2 Online operation

In general the device works like a configurable digital sensor that is listening to own inputs or outputs of other
devices. On input events the device performs output functionality over KNX bus like sending values or
controlling external devices like KNX actuators.

Application manual
6.3 Software working cycle

The main purpose of the software is following:
 Handle user pushbutton presses and generate bus telegrams according to the assigned functions;
 Implement pushbutton interlock and timing functions;
 Handle incoming bus messages in order to update the status of pushbutton activations and LED
indicators;
 Respond to bus messages requesting feedback on the status of the inputs.
The status of the device and specifically of its entities (input activation status and LED indicators) relies on
KNX communication objects, which can be freely defined and bound in various ways to the physical elements
of the device; these communication objects acts as state variables for the device.
There are also special events on which it is possible to trigger additional features. These events are the bus
failure and recovery, and the download of a new configuration with ETS.
6.4 Pushbutton inputs

The press of a pushbutton can be bound to different effects on a state variable.
6.4.1 Pushbutton input events
A button press can be handled either as an “on-off” event (“on” means when the button is pushed, “off” when
it is released), or as a “short press - long press” event (whereby a time period can be defined to discriminate
the duration of the “long” from the “short” press).
In both cases, for each of the two available events a separate action can be assigned that operates on a
selected variable (actually, more than one; see below for details).
6.4.2 Lock function
For each input (or channel if inputs are coupled, see below), a lock feature can be enabled which allows to
block the operation of an input through a message on a communication object.
When in a locked state, the input is effectively disabled.
A value (for each transition) can be specified to be assigned to the communication object upon entering or
exiting the locked state.
The locked state can also be automatically activated when the bus is connected.
6.4.3 State variables (communication objects)
The variable that is changed by the input events can be one of the types available for KNX communication
objects, i.e. for instance a 1-bit value (on-off), a 2-bit value or an integer value of larger size.
In all cases, each of the two events can:
 change the value of the variable to one of two definable values within its range (which is trivial in the
case of the 1-bit value);
 toggle between the two defined values
 do nothing (value is unaffected)

Application manual
This state variable, once assigned a group address, is actually a KNX communication object; as such, it
undergoes the usual rules for communication objects, among which – for instance – the effect of flags to
determine how the change of value affects the transmission of the objects.
6.4.4 Binding between Events and Communication objects
The above description is a little simplified in order to ease comprehension; as a matter of fact, to each event
can be assigned not just one, but several communication objects (up to 8), even of different types. Each of
these communication objects can have its own behaviour and its own associated value set.
6.4.5 Repeated send
For most features, is it possible to set the device to send a telegram not just when a value changes as a
consequence of an input transition, but also at regular intervals whenever that value setting is active.
This behaviour, also referred to as Cyclical Transmission, can be set separately for each of the two values that
are associated to an input (or both, or none of them).
If an input is set to “send values or sequences” mode, repeated send is not available if more than 1
Communication Object is assigned to that input.
6.4.6 Input coupling
The 8 pushbutton inputs described can be considered, and used, as independent; however, due to the physical
structure of the device and the nature of the functions it most frequently performs, these inputs can be naturally
grouped in pairs, which in the application program are referred to as channels. Each channel is made of a pair
of inputs, and is physically associated to a rocker.
Since the channels of the device are labelled 1 to 4, the inputs are labelled 1A / 1B for channel 1, 2A / 2B for
channel 2 and so on. The same numbering is used whether the channel pairing is used or not.
In order to specify channel pairings, each rocker can be configured in two ways: single mode and coupled
mode. This setting appears among rocker-level settings rather than input-level settings, because only inputs
belonging to the same rocker can be coupled. The only combinations allowed for coupling are in fact 1A with
1B, 2A with 2B, and so on.
 In single or independent mode, each input operates independently, has its own parameters and
communication objects. This is the mode of operation described so far.
 In coupled mode, 2 inputs operate logically grouped under a channel in order to perform a common
functionality; therefore, they operate on shared communication objects.
It is possible to configure some of the inputs in single or independent mode and the others in coupled mode,
with the pairing constraints just described.
It must be mentioned that there is actually a third way to configure an input pair, which lies somehow halfway
between the two modes above (although it is considered as a variation of the single mode): each second input,
i.e. inputs 1B, 2B, 3B etc., can be configured to perform exactly the same function as its first input. In this
fashion, both pushbuttons associated with a rocker are effectively operated “in parallel”, so as to operate the
whole rocker as a single, larger control (either pushbutton or switch, according to programmed operation).
Following there is a description of all possible features of the channels. Single or independent and coupled
modes have a similar functionality, but differ for the configuration and will be therefore be treated separately.

Application manual
6.4.7 Single or independent input mode
Each single input can be configured for one of following different features:
1. Send values or sequences
An event triggers the transmission on the bus of configurable values or sequence of values.
These values can be of a logical type or a numerical type with a different size.
A sequence of values can be made of up to 8 communication objects of different value types.
Time delays can set between values in the sequence.
2. Dimmer control
This mode is intended to be used with dimming actuators for the control of lighting devices.
The functionality is triggered on short press and long press events.
On short press events, the device sends on/off telegrams to the dimming actuator.
On long press events, the dimming percentage is varied up or down until the button is released.
3. Shutter or Venetian blind control
This mode is intended to be used together with actuators for the control of motorized blinds, shutters
and similar devices. These actuators have functions for blind opening and closing; two movement types
are selectable, i.e. continuous movement and stepwise movement. On input events, the device sends
operation telegrams to the actuators.
The operation is configurable through following parameters:
 If toggle mode is enabled, on each activation of the same input the movement direction is
inverted; if it is disabled, the movement direction is fixed and it can be set to “up” or “down”.
 If blinds mode is enabled, the device sends “full movement” telegrams on long press and “step”
telegrams on short press; if it is disabled, the device sends “full movement” telegrams on long
press and “stop” telegrams on short press.
4. Scene function output

This mode is intended to be used together with several KNX actuators that support using a scene
function; this function allows storing and recalling a communication object value on an actuator.
In this mode, the role of the device is to send a “store / recall scene” telegram to the actuator on a long
/ short press event.
This mode has two possible configurations:
 Activate pre-set scene on short press, and store current setting as scene value on long press
 Activate two different scenes on long and short press.
6.4.8 Coupled input mode
Each pair of coupled inputs, corresponding to the two sides of a same rocker, can be configured for one of
following different features (only the differences from the single mode are highlighted):
1. Switch control
Both inputs in a pair are bound to the same communication object; unlike single mode, the object can
only be of the 1-bit type (on-off), therefore building a conventional switching behaviour.
The user can configure which of the two inputs sets the “off” or resp. “on” value.
2. Dimmer control
The functionality is triggered on short press and long press events of the inputs in the pair.
The user can configure which of the two inputs sets the “up” or resp. “down” value.
On short press events, the input configured as “up” sends an “on” switching telegram to the dimming
actuator; while the “down” input sends an “off” telegram.

Application manual
On long press events, the dimming percentage is varied up or down until the button is released.
3. Shutter or Venetian blind control
The two inputs of a pair are assigned to opposite movement directions; these can be assigned to inputs
as desired, i.e. A up / B down or the other way around.
The blinds mode can also be set, and it works exactly as in single mode.
In coupled mode, there is no provision for a scene control feature.

Application manual
6.4.9 Dimming function
The dimming function is a device application profile included in KNX specifics. Those specifics define the basic
requirements for interface mechanisms, in addition to which some aspects regarding the operating modes,
peculiar for each device (for both command or actuation devices) are to be considered.
All the information contained in this section have the purpose of illustrating specific device
functions, and therefore are not to be necessarily considered exhaustive or applicable to
i other cases. In order to obtain a complete or generally applicable documentation, please

refer to the official KNX documentation.
For further information, visit the website www.knx.org.
The dimmer control type is essentially based on a 4-bit communication object, whose data has the following
format:
The transmission of telegrams containing data of such format tells the actuator to perform an increase or a
decrease, by an amplitude equal to the specified step, or to stop an ongoing variation.
The increase or decrease of an intensity value by the actuator is not instantaneous but gradual; therefore, an
increase / decrease command with interval equal to the maximum allowed value has the effect of starting the
intensity variation in the desired direction, which will continue until the maximum (or minimum) value has been
reached. Such variation can be stopped, once the desired intensity value has been reached, by sending a
“stop” command.
It is normally possible, and desirable, to have the possibility to instantly switch on or off the load (i.e. to
instantaneously bring its value from 0% to 100%). In order to achieve that, an “On / Off” command based on
another object is used; this is the same object used for the normal load switch, which is present also in absence
of a dimming mechanism.
The command device – in this case, the rocker unit – will define the operations to generate a sequence of
commands with an opportune order and time interval, in order to achieve the desired command effect.

Application manual
In case of unit EK-Ex2-TP, the defined operations and related commands are the following:
Figure 3 - Dimmer mode command sequence
 Short press: instantaneous switch on / off (toggle on / off on a switch object);

 Long press: increase / decrease value until 100% / 0%;
 Release: stop increase / decrease.
Please note that the same mechanism can be applied to the shutter or venetian blind control (in that case,
“maximum / minimum” is substituted with “open / close”). For this purpose, the data type (DPT) 3.008 exists,
whose structure and values are identical to those already described; in order to control a shutter with the
same mode, it is possible to connect a communication object type 3.007 command side, to an object type
3.008 actuator side (if foreseen). In this case, obviously, the object type “On / Off” which allows
instantaneous switch on / off is not used.

Application manual
6.4.10 Shutter / venetian blind function
The “Shutter / venetian blind” function is a bundle of application profiles included in KNX specifics. As for
dimming function, such specifics define basic requirements related to interface mechanisms, in addition to
which some aspects regarding the operating modes, peculiar for each device (for both command or actuation
devices) are to be considered.
All the information contained in this section have the purpose of illustrating specific device
functions, and therefore are not to be necessarily considered exhaustive or applicable to
i other cases. In order to obtain a complete or generally applicable documentation, please

refer to the official KNX documentation.
For further information, visit the website www.knx.org.
In case of shutters, the actuator brings a mechanic component from one point to another in a gradual way, with
possibility to stop at intermediate points; the command is carried out by 2 lines which, when activated (one line
at a time) make the actuator move in the corresponding direction.
A venetian blind is essentially a shutter that, in addition to the up / down movement, is also equipped with slats
that can be opened / closed same way as a shutter (gradual movement between extreme points). The
peculiarity is that normally the slat’s movement and the up / down movement are controlled by the same two
lines; therefore, the activation of the electromechanic device must be carried out according to a specific
sequence. For further detail please check the actuator’s documentation; in this document all we need to point
out is that, command side, the control sequences can be considered as independent from these aspects.
The basic control for a shutter or a venetian blind is essentially based on three 1-bit communication objects:
 [1.008] Move Up/Down
 [1.007] Stop – Step Up/Down
 [1.017] Dedicated Stop
The effect of the commands linked to these objects is the following:
 The command “Move”, when received, starts the movement of the shutter in the indicated
direction.
 The command “Stop – Step” has two functions: if the shutter is stopped, it moves by one step in
the indicated direction (the duration is set in the actuator), if not, it stops the ongoing movement
without doing anything else.
 The command “Stop” just stops the ongoing movement.
In addition, other types of control objects are normally available (“dimmer” type, absolute position, etc.) but
they are not part of the basic control on which this manual is about; for further information please refer to the
actuators’ manual or KNX specifics.
In the simplest version, on command side:
 In order to control a shutter at least the objects “Move” and “Stop” are required (and present).
 In order to control a venetian blind at least the objects “Move” and “Stop – Step” are required (and
present).
On actuator side – whether it is a shutter or a venetian blind – the presence of objects “Move” and “Stop –
Step” must be guaranteed, while the presence of the object “Stop” is optional (but usually present).

Application manual
As for the operations to perform on the command device, in our specific case the rocker unit, in order to
generate a sequence of these commands with the proper order and time interval, there are multiple
possibilities.
In case of ekinex input devices, two modes are available – indicated as “Shutter” and “Venetian blind” based
on their typical destination – which are illustrated in the following figure.
Figure 4 - “Shutter” mode command sequence
In “Shutter” mode, when a rocker is pressed – or a digital input is activated – the shutter starts moving in the
corresponding direction (which can be alternatively in the two directions if the rocker is in independent mode
and has been configured as toggle).
If the rocker is released quickly, the shutter will continue its run until full opening or closing; it is still possible to
stop it by pressing again the rocker with a long press.
If the rocker is pressed with a long press, when it is released – which will be in correspondence with the desired
position – the shutter will stop.

Application manual
Figure 5 - “Venetian blind” mode command sequence
In “Venetian blind” mode, on release of a rocker after a short press, the venetian blind performs a step; this
operation, normally – i.e. even if the actuator is indeed configured for a venetian blind – is used for the slats
regulation.
If the rocker is pressed with a long press, when the threshold time is reached, a “Move” command is issued,
which will bring the venetian blind to full open or close. In order to stop it at an intermediate position, the rocker
needs to be pressed again (short press).

Application manual
6.5 LED indicators

The LED indicators associated with each input are two (first colour and second colour) and can be singularly
addressed, even if the corresponding inputs are coupled.
6.5.1 General parameters
All LEDs have a common intensity value, which can be set from the bus through a communication object or
with a fixed setting from 0 to 100% in 10% steps.
6.5.2 Individual parameters
Each LED can be driven in one of following ways:

 Fixed value (always on or always off);
 Lit when the corresponding input is activated. In this option, an additional off-delay can be
specified after the button is released;
 Status set from the bus through a communication object. In this case, the LED can be set to be
flashing when active (with a choice of different on/off time combinations), and the on/off light
status can be inverted with respect to the communication object status (so as to have the LED
on when the CO has an “off” value).
6.5.3 Technical Alarm indicator
The device has a peculiar indicator feature called Technical Alarm: if it is enabled, all LEDs at the four corners
of the device can be activated flashing through a KNX bus telegram. In particular, the activation of the technical
alarm generates the blue LEDs activation in BG version (colour of the LEDs: green and blue), while the red
LEDs activation in RW version (colour of the LEDs: red and white). For further information about the LEDs
position and configuration parameters please refer to the application section of this manual.
This feature is meant as an indicator for a generic alarm condition, but it can be used in a custom way as the
user sees fit.
The typical purpose of this indication is to warn about an alarm condition, but can be also used for any other
indication.

Application manual
6.6 Temperature sensor

The value from the embedded temperature sensor, unless it is disabled, can be read from the bus by other
devices. In addition, their behaviour can be modified through following parameters:
6.6.1 Temperature sensor
The raw value read from the sensor can be corrected with a small offset (-5 °C to +5 °C in steps of 0.5 °C), in
order to compensate for environmental factors and achieve a better precision.
The sensor value can periodically be sent on the bus with a specified transmission interval, and whenever a
specified variation occurs.

Application manual
6.7 Room thermostat
6.7.1 Use of sensors
The temperature controller integrated inside the pushbutton allows the room temperature acquisition in the
following ways:
1) from the temperature sensor integrated inside the device;
2) via bus from another KNX device, e.g. another ekinex® pushbutton
In order to optimize or correct the temperature regulation in particular cases (big rooms, when there is a strong
asymmetry in temperature distribution, when the pushbutton is installed in wrong or unsuitable positions, etc.)
the device can use a weighted mean between two temperature values. The weights are assigned according
to the Relative weight parameter, which assigns a proportion to the values.
Note on mounting position
If the integrated temperature regulator is used, the device must be preferably installed on an internal wall, at 1,5 m of height
i and at least 0,3 m of distance from doors. The device cannot be installed near heat sources such as radiators or domestic
appliances or in positions subjected to direct solar irradiation. If necessary, for the regulation can be used a weighted mean
value between the measured temperature acquired by the integrated sensor and a value received via bus from another
KNX device.
6.7.2 Applications
The applications that can be configured are peculiar to thermal plants with a single stage and concern the
following terminals: radiators, electric radiators and radiant panel systems.
The temperature control can be:
 two point control with hysteresis, ON-OFF command type;
 proportional-integral, with ON-OFF command, PWM or continuous type.
6.7.3 Control algorithms
The picture below shows the components of a common generic control system for ambient temperature. The
room thermostat measures the actual temperature of the air mass (T eff) and constantly compares it to the
setpoint value (Tset).
Solar radiation Presence of people

Appliance Dispersioni
Room thermostat Actuator control
Tset
+ Control Actuator Heating body
algorithm (e.g. relay output – (e.g. radiator, fan- Ambient
valve motor etc) coil, radiant panel)
-
Teff

Application manual
The control algorithm, basing on the difference between T set and Teff, processes a command value which can
be analogue or On / Off type; the command is represented by a CO that is transmitted via bus, periodically or
event based, to a KNX actuator device.
The output of the actuator device is the driving variable of the control system, which can be e.g. a flow rate of
water or air. The control system realized by the room thermostat is of feedback type, namely the algorithm
takes into account the effects on the system in order to change the control action on the same entity.
6.7.3.1 Two-point control with hysteresis

This control algorithm, which is also known as On / Off, is the most classic and popular. The control provides
for the on / off switching of the system following a hysteresis loop, i.e. two threshold levels are considered for
the switching instead of a single one.
ON ON
Thysteresis Thysteresis
OFF OFF
T ambient T ambient
Tset Tset
Heating mode: when the measured temperature is lower than the value of the difference (Tset – ΔThysteresis),
whereby ΔThysteresis identifies the differential adjustment of the boilers, the device activates the heating system
by sending a message or KNX telegram to the actuator that handles the heating system; when the measured
temperature reaches the desired temperature (Setpoint), the device disables the heating system by sending
another message. In this way, there are two decision thresholds for activation and deactivation of the heating,
the first being the level (T set – ΔThysteresis) below which the device activates the system, whereas the second is
the desired temperature above which the heating system is deactivated.
Cooling mode: When the measured temperature is higher than the value of the difference (T set + ΔThysteresis),
whereby ΔThysteresis identifies the differential adjustment of the cooler, the device activates the air conditioning
system by sending a message or KNX telegram to the actuator that handles it; when the measured temperature
falls below the desired temperature Tset the device turns off the air conditioning system by sending another
message. In this way, there are two decision thresholds for activation and deactivation of the cooling: the first
being the level (Tset + ΔThysteresis) above which the device activates the system, whereas the second is the
desired temperature below which the air conditioning system is deactivated. In the ETS application program,
two different parameters are available for the hysteresis value for both heating and cooling: the values usually
differ depending on the system type and its inertia.
In those applications where floor or ceiling radiant panels are present, it is possible to realize a different 2-point
room temperature control. This type of control must be paired either to a proper regulation system for flow
temperature that takes into account all internal conditions or an optimizer that exploits the thermal capacity of
the building to adjust the energy contributions. In this type of control the hysteresis (ΔThysteresis) o the room
temperature high limit (Tset + ΔThysteresis) represent the maximum level of deviation that the user is willing to
accept during plant conduction.

Application manual
ON ON
hysteresis Thysteresis
OFF OFF
T ambient T ambient
Tset Tset
Heating mode – When the measured temperature is lower than the desired temperature T set, the device
activates the heating system by sending a message or KNX telegram to the actuator that handles it; when the
measured temperature reaches the value (T set + ΔThysteresis), whereby ΔThysteresis identifies the differential
adjustment of the boilers the device disables the heating system by sending another message. In this way,
there are two decision thresholds for activation and deactivation of the heating, the first being the desired
temperature Tset below which the device activates the system, whereas the second is the value (Tset +
ΔThysteresis), above which the heating system is deactivated.
Cooling mode – When the measured temperature is higher than the desired temperature T set, the device
activates the air conditioning system by sending a message or KNX telegram to the actuator that handles it;
when the measured temperature reaches the value (T set - ΔThysteresis), whereby ΔThysteresis identifies the
differential adjustment of the air conditioning system, the device disables the air conditioning system by
sending another message. In this way, there are two decision thresholds for activation and deactivation of the
air conditioning system: he first being the desired temperature T set above which the device activates the
system, whereas the second is the value (T set - ΔThysteresis) below which the air conditioning system is
deactivated.
In the ETS application program, two different parameters are available for the hysteresis value for both heating
and cooling: the values usually differ depending on the system type and its inertia.
In the ETS application program, the default 2-point hysteresis control algorithm foresees inferior hysteresis for
heating and superior for cooling. If Heating and/or cooling type = floor radiant panels or ceiling radiant panels,
it is possible to select the hysteresis position according to the described second mode, i.e. with superior
hysteresis for heating and inferior for cooling.
The desired temperature (T set) is generally different for each one of the 4 operating modes and for
heating/cooling modes. The different values are defined for the first time during ETS configuration and can be
modified later on. In order to optimize energy saving (for each extra degree of room temperature, outbound
dispersions and energy consumption go up 6%), it is possible to take advantage of the multi-functionality of
the domotic system, for example with:
• Hour programming with automatic commutation of the operating mode by means of KNX supervisor;
• Automatic commutation of the operating mode according to presence of people in the room;
• Automatic commutation of the operating mode according to window opening for air refreshment;
• Circuit deactivation when desired temperature is reached;
• Flow temperature reduction in case of partial load.
6.7.3.2 Continuous Proportional-Integral control

The continuous proportional-integral (PI) controller is described by the following equation:
𝑡
𝑐𝑜𝑛𝑡𝑟𝑜𝑙 𝑣𝑎𝑟𝑖𝑎𝑏𝑙𝑒(𝑡) = 𝐾𝑝 × 𝑒𝑟𝑟𝑜𝑟(𝑡) + 𝐾𝑖 × ∫ 𝑒𝑟𝑟𝑜𝑟(𝜏)𝑑𝜏
0

Application manual
whereby:
𝑒𝑟𝑟𝑜𝑟(𝑡) = (𝑆𝑒𝑡𝑝𝑜𝑖𝑛𝑡 − 𝑀𝑒𝑎𝑠𝑢𝑟𝑒𝑑 𝑡𝑒𝑚𝑝𝑒𝑟𝑎𝑡𝑢𝑟𝑒) 𝑖𝑛 ℎ𝑒𝑎𝑡𝑖𝑛𝑔
𝑒𝑟𝑟𝑜𝑟(𝑡) = (𝑀𝑒𝑎𝑠𝑢𝑟𝑒𝑑 𝑡𝑒𝑚𝑝𝑒𝑟𝑎𝑡𝑢𝑟𝑒 − 𝑆𝑒𝑡𝑝𝑜𝑖𝑛𝑡) 𝑖𝑛 𝑐𝑜𝑜𝑙𝑖𝑛𝑔
𝐾𝑝 = 𝑝𝑟𝑜𝑝𝑜𝑟𝑡𝑖𝑜𝑛𝑎𝑙 𝑐𝑜𝑛𝑠𝑡𝑎𝑛𝑡
𝐾𝑖 = 𝑖𝑛𝑡𝑔𝑟𝑎𝑙 𝑐𝑜𝑛𝑠𝑡𝑎𝑛𝑡
The control variable is composed by 2 numbers, one depending proportionally from the error and one
depending from the integral of the error itself.
Practically, some more intuitive values are used:

100
𝑃𝑟𝑜𝑝𝑜𝑟𝑡𝑖𝑜𝑛𝑎𝑙 𝐵𝑎𝑛𝑑 𝐵𝑃 [𝐾] =
𝐾𝑝
𝐾𝑝
𝐼𝑛𝑡𝑒𝑔𝑟𝑎𝑙 𝑇𝑖𝑚𝑒 𝑇𝑖 [𝑚𝑖𝑛] =
𝐾𝑖
The Proportional Band is the error value that determines the maximum span of the control variable at 100%.
For example, a controller with Proportional Band = 5 K regulates at 100% when Setpoint = 20°C and Measured Temperature is ≤
15 °C in heating mode; in cooling mode, it regulates at 100% when Setpoint = 24°C and Measured Temperature is ≥ 29°C. As shown
in figure, a controller with a narrow Proportional Band provides higher control variable values for smaller errors compared to a
controller with a wider Proportional Band.
Wide Proportional Band
100%
Narrow Proportional Band
50%
0%
Wide Proportional Band
100%
Narrow Proportional Band

50%
0%
T Setpoint T ambiente [°C]
Integral Time is the amount of time necessary to repeat the value of the control variable of a purely proportional controller,
when error is constant. For example, with a purely proportional controller with Proportional Band = 4 K, if Setpoint = 20°C and
Measured Temperature = 18°C, the control variable will be 50%. If Integral Time = 60 minutes, if error remains constant, the control
variable will be 100% after 1 hour, i.e. the controller will add to the control variable a contribution equal to the value due to its
proportional part.

Application manual
In heating and air conditioning systems, a purely proportional controller cannot guarantee reaching the Setpoint. An integral action is
mandatory in order to reach the Setpoint: for this reason, the integral action is also called automatic reset.
6.7.3.3 PWM Proportional-Integral control

The proportional-integral PWM (Pulse Width Modulator) controller uses an analogue control variable to
modulate the duration of the time intervals in which a binary output is in the On or Off state. The controller
operates in a periodic manner over a cycle, and in each period it maintains the output to the On value for a
time proportional to the value of the control variable. As shown in the figure, by varying the ratio between the
ON time and the OFF time, the average time of activation of the output varies, and consequently the average
intake of heating or cooling power supplied to the environment.
Cycle period
ON
T ON
T OFF
OFF
Time [min]
T ON = T OFF
ON
Mean ON time = 50%
OFF
Time [min]
T ON = ½ T OFF
ON
Mean ON time = 25%
OFF
Time [min]
This type of controller is well suited for use with On / Off type actuators, such as relays and actuators for zone
valves, which are less expensive (both for electrical and mechanical components) than proportional actuators.
A distinctive advantage of this type of controller, compared with the raw On / Off controller already described,
is that it eliminates the inertia characteristics of the system: it allows significant energy savings, because you
avoid unnecessary interventions on the system introduced by the 2-point control with hysteresis and it only
provides the power required to compensate for losses in the building.
Every time the user or the supervisor changes the desired temperature setpoint, the cycle time is interrupted,
the control output is reprocessed and the PWM restarts with a new cycle: this allows the system to reach its
steady state more quickly.
Terminal type Proportional Band [K] Integral Time [min] Cycle Period [min]
Radiators 5 150 15-20
Electrical heaters 4 100 15-20
Fan-coil 4 90 15-20
Floor radiant panels 5 240 15-20
Guidelines for choosing the proper parameters of a PMW Proportional-Integral controller:

Application manual
 Cycle time: for low-inertial systems such as heating and air conditioning systems, short cycle times must be chosen (10-15 minutes)
to avoid oscillations of the room temperature.
 Narrow proportional band: wide and continuous oscillations of the room temperature, short setpoint settling time.
 Wide proportional band: small or no oscillations of the room temperature, long setpoint settling time.
 Short integral time: short setpoint settling time, continuous oscillations of the room temperature.
 Long integral time: long setpoint settling time, no oscillations of the room temperature.
6.7.4 Setpoint management
The pushbutton is not equipped with any local interface to control the integrated room thermostat, therefore
the temperature setpoint modifications need to be managed through communication objects coming from a
supervisory device.
Five setpoint management modes are foreseen:
 Single setpoint
 Relative setpoints, heating/cooling switch over from bus
 Relative setpoints, automatic heating/cooling switch over
 Absolute setpoints, heating/cooling switch over from bus
 Absolute setpoints, automatic heating/cooling switch over
Single setpoint mode

In this mode, a unique communication object is exposed (Input Setpoint) to modify the desired temperature.
This object can be updated cyclically or on event of change by the supervisory device. If power goes down,
the last value is retained into the pushbutton’s non-volatile memory. In case the object is not updated, the
temperature controller acts anyway on default setpoints (both heating and cooling) set in the application
program during commissioning.
If a temperature controller is set on both heating and cooling mode, it is necessary that the
i supervisory device also updates the input seasonal mode object (Heating/cooling status in, [1.100]
DPT_Heat_Cool) in order to coherently switch over the controller’s action.
If window contacts for energy saving are used, when detecting an open window the input setpoint freezes and
the pre-set building protection setpoint is activated (the relative communication object is exposed and is
different in heating or cooling mode).
Relative setpoints, heating/cooling switch over from bus

In this mode, 4 communication objects are exposed, one for each operating mode:
 Comfort setpoint
 Stand-by offset
 Economy offset
 Building protection setpoint

Application manual
Stand-by and economy setpoints are represented as attenuations to the comfort setpoint in order to facilitate
the supervisor management: by uniquely modifying the comfort setpoint, references for attenuated modes are
automatically transferred. The values modified from bus are retained in the pushbutton’s non-volatile memory.
With this mode, the supervisory device can develop an hour-based time scheduling by sending to the
pushbutton the current operating mode (comm. obj. HVAC mode in [20.102] DPT_HVACMode). The default
value for HVAC mode in corresponds to the comfort setpoint value.
Same as single setpoint management, if the temperature controller is set as both heating and cooling mode,
it is necessary that the supervisory device also updates the input seasonal mode object (Heating/cooling status
in, [1.100] DPT_Heat_Cool) in order to coherently switch over the controller’s action.
Relative setpoints, automatic heating/cooling switch over

In this mode, 3 communication objects are exposed, for all operating modes:
 Comfort heating setpoint
 Building protection heating setpoint
 Building protection cooling setpoint
Stand-by and economy setpoints are represented as attenuations to the comfort setpoint and can only be
modified in the application program during commissioning: by uniquely modifying the comfort setpoint,
references for attenuated modes and for comfort cooling setpoint mode (through switch over dead band) are
automatically transferred. The values modified from bus are retained in the pushbutton’s non-volatile memory.
With this mode, the supervisory device can develop an hour-based time scheduling by sending to the
pushbutton the current operating mode (comm. obj. HVAC mode in [20.102] DPT_HVACMode). The default
value for HVAC mode in corresponds to the comfort setpoint value.
The switch over between operating modes is automatic and the information can be sent to other devices
through communication object Heating/cooling status out, [1.100] DPT_Heat_Cool). Please refer to the
section about heating/cooling switch over to learn more about switch over modes.
6.7.5 Operating modes
In Single Setpoint mode, 2 levels for each operating mode are available:
 Temperature setpoint
 Building protection setpoint
Time scheduling for attenuation can be realized by the supervisor, by directly modifying the temperature
setpoint.
In Relative Setpoint mode, 4 different operating modes are available, which are mutually exclusive to one
another:
 comfort;
 stand-by;
 economy;
 building protection.
Through ETS application program, it is possible to assign 2 different setpoint values to each operating mode,
for comfort and building protection level, and two different attenuation levels for stand-by and economy,

Application manual
corresponding to both heating and cooling. Stand-by and economy setpoints are represented as attenuations
to the comfort setpoint in order to facilitate the supervisor management: by uniquely modifying the comfort
setpoint, references for attenuated modes are automatically transferred.
Each setpoint, except when automatic heating/cooling switch over is active, is exposed through communication
objects. Setpoints and attenuations can be modified remotely through the exposed communication objects.
The building protection setpoint intervention must be planned in ETS application program, as these parameters
concern the safety and protection of the plant’s components (especially during heating).
6.7.6 Heating/cooling switch over
The switch over between both heating and cooling mode can take place in 2 ways:
1. from KNX bus, through a communication object;
2. automatically, through a command from the internal logic of the device;
Switchover from bus

In mode 1, the switch over command is issued through KNX bus and therefore it is performed by a different
KNX device, e.g. the ekinex® Touch&See unit. The integrated temperature controller acts as a “slave”: the
switch over is carried out by input communication object [DPT 1.100 heat/cool].
Automatic switch over

Mode 2 is suitable for applications with heating / cooling systems with a 4-pipe configuration (e.g. fan-coils or
radiant ceiling panels). Also in this case the information can be transmitted on the bus through an output
communication object [DPT 1.100 heat/cool]; the difference with mode 1 is that the switch over is performed
automatically by the machine, basing on the values of current temperature and setpoint. The automatic switch
over is achieved by introducing a dead band as shown in the following figure.
The figure shows that, as long as the actual measured temperature is below the heating mode setpoint, the
heating mode is selected; similarly, if the value is greater than the cooling setpoint, then cooling mode is

Application manual
selected. If the value is within the dead band, the operation mode remains unchanged until the value itself
passes over the threshold value associated with the opposite mode.
The 4 setpoints for heating mode and the 4 setpoints for cooling mode are not exposed through
communication objects to avoid inconsistencies between the different levels of temperature. In this
i case, a single communication object is published, which corresponds to the comfort heating
setpoint. Every time this parameter is changed, the whole dead band changes with it, as well as all
setpoints related to the 4 operating modes: the automatic switch over is then triggered outside the
defined dead band.
6.7.7 Window switch management
Window switch management is an optional feature, oriented to energy saving, which becomes available only
if the Temperature control function is enabled in the application program.
Whenever a condition of opened window is detected, the operating mode is forced to “building protection” and
it remains forced as long as the open window condition is active. The program provides a time delay parameter
for detection, in order to discriminate between an occasional short-term opening (e.g. to provide air exchange
in the room) from an unintentional opening that justifies the power-saving function to be recalled.
The operating mode determined from Window switch management has priority on all operating mode settings
imposed by the scheduler (in case Setpoint management = relative setpoint)
The physical detection of window openings is normally performed through switches that can be connected to
KNX input devices; the pushbutton exposes up to 2 1-bit communication objects (Temperature control tab 
External sensors) which can be synchronized to the switches’ states.
The internal logic performs a logical OR operation of the acquired contacts: the energy saving function is
therefore activated if at least one window switch activation is detected. In order to determine the physical state
of the contact corresponding to the “open window” state, two different options can be selected:
 NC (normally closed): open contact stands for closed window, closed contact stands for open window;
 NO (normally open): open contact stands for open window, closed contact stands for closed window;
6.7.8 Valve protection function
The function is suitable for both heating and cooling systems that use water as thermal conveying fluid and
are provided with motorized valves for the interception of a zone or of a single room. Long periods of inactivity
of the system can lead to the blockage of valves: to prevent this, the room temperature controller may
periodically send a command to open / close the valve in the period of inactivity of the system. This possibility
is further defined by the frequency and duration of the valve control.
6.7.9 Temperature control alarm
The integrated temperature controller can stop the internal control algorithm for one of the following reasons:
 For an external event, which can be configured and linked to the Thermal generator lock
communication object;
 For an internal temperature sensor’s fault (measured room temperature too low while NTC resistance
value is too high or vice versa);

Application manual
 For a timeout (data not updated by the bus) when a weighted mean between the internal sensor’s
value and an auxiliary external sensor’s value is used.
When one of these events occur, the internal controller stops the control algorithm and the command output is
taken to complete closing position (OFF or 0%): this state is signalled through the communication object
Temperature control alarm.

Application manual
6.8 Logic functions

The KNX pushbutton allows to use some useful logic functions (AND, OR, NOT and exclusive OR) in order
to implement complex functions in the building automation system.
You can configure:
 8 channels of logical functions

 4 inputs for each channel
Each object value, if desired, can be individually inverted by inserting a NOT logic operator.
The inputs created by the objects are then logically combined as shown in the following figure:
Figure 6 – Logic combination function
The logic block on the right side of the figure has the following function, based on the selected operation:
 OR – the output is ON if at least one input is ON;
 AND – the output is ON if all inputs are ON;
 XOR – the output is ON if an odd number of inputs is ON;
This last function is more intuitive when there are only 2 inputs: in this case, the output is ON when one input
or the other one is ON, but not the two of them simultaneously.
Please note that in this description, with “input” and “output” we refer only to the logic block; for the device
operation, the effective “inputs” are given by communication objects, so also the possible activation of NOT
logic operators has to be considered.

Application manual
The following figures show the basic logic functions, assuming 2 inputs and only one logic communication
object:
Figure 7 – Logic function OR
Figure 8 – Logic function AND

Application manual
Figure 9 – Logic function Exclusive OR (XOR)
For each channel, a parameter Delay after bus voltage recovery is available: this parameter represents the
time interval between the bus voltage recovery and the first reading of the input communication objects for
evaluating the logic functions.
The communication function representing the logic function output is sent on the bus on event of change;
alternatively, a cyclic sending can be set.

Application manual
7 Application program for ETS

In the following chapters, there is the list of folder, parameters and communication objects of the application
program.
Every channel, and every input or input pair under a channel, offers the same set of communication objects
and parameters, but they may all be independently configured.
Hereafter, all channel-specific settings are listed grouped by channel; a generic channel number is referenced
as “x” (where x = 1…4), while a generic input is referenced as “xx” (xx = 1A, 1B, 2A, ... 4B).
i The parameter values highlighted in bold represent the default value.
The device settings are divided in two main groups: the general settings and the channel-specific settings. The
settings are grouped in folders. The following figure shows the tree structure of the application program, with
the main folders:
Info su EK-EX2-TP
Generale
Sensori interni
Sensore di temperatura
Configurazione tasti
Tasto 1
Funzione A
Oggetto 1
Funzione B
Oggetto 1
....
Tasto 4
LED
Controllo temperatura
Impostazioni
Sensori dal bus
Valore temperatura pesata
Riscaldamento
Raffreddamento
Funzioni logiche

Application manual
In order to use the device as a temperature sensor or as a room temperature controller it is sufficient to enable
the temperature sensor in the Internal sensors folder. Consequently, also the Temperature control folder is
activated: therefore, it is possible to select an auxiliary temperature sensor to perform a weighted mean with
the main sensor and it is possible to configure the controller’s options for room temperature.
7.1 About EK-ED2-TP and EK-E12-TP

The folder About EK-ED2-TP is for information purposes only and does not contain parameters to be set. The
information given is:
© Copyright SBS S.p.A. 2017
Application software for ETS4
Version 2.00 (or later)
2-4 rockers pushbutton
SBS S.p.A.
Via Circonvallazione s/n
I-28010 Miasino (NO) Italy
www.ekinex.com
info@ekinex.com
The folder About EK-E12-TP is for information purposes only and does not contain parameters to be set. The
information given is:
© Copyright SBS S.p.A. 2017
Application software for ETS4
Version 3.00 (or later)
KNX pushbutton series 71
SBS S.p.A.
Via Circonvallazione s/n
I-28010 Miasino (NO) Italy
www.ekinex.com
info@ekinex.com

Application manual
7.2 General settings

The parameters in this section define the overall behaviour of the device, including the setting that defines
which and how many channels are available.
Parameter name Conditions Values

See Fig. 9 and 10
Rockers configuration
for available options
Specifies the configuration of installed rocker plates, thereby determining how physical
pushbuttons will be associated to logical inputs and coupled in rocker pairs.
Leds intensity from bus - yes / no
Specifies whether the intensity value of LEDs should be set through a communication object.
Leds intensity Leds intensity from bus = no 0%..100% (50%)
Fixed intensity value of LEDs.
hh:mm:ss.fff
Delay after bus voltage recovery -
(00:00:04.000)
Delay before bus telegrams can be sent after a recovery of the bus voltage. The delay time
affects the transmission generated by an event as well as the cyclical transmission. For the
cyclical transmission: after the delay time finished, the cycle restarts and the first telegram will
be sent after the cycle time.
Technical alarm - enabled / disabled
Enables a communication objects that activates an alarm indication through a bus telegram. The
indication is made by flashing the four LEDs at the corners of the device.
This indication is made available to the user for any purpose he sees fit (not necessarily an
actual alarm).
Room temperature controller enabled / disabled
Enables the folder containing the parameters for room temperature control.
Logic functions enabled / disabled
Enables the folders to configure AND, OR e XOR logic functions and their relative input and
output communication objects.
Object name Conditions Size Flags DPT No. Comm. Obj.

Technical alarm Technical alarm = enabled 1 bit C–W-- [1.005] alarm 0
Temperature sensor = [9.001]

Temperature value 2 Byte CR–T- 3
enabled temperature (°C)

Application manual
Figure 10A – ‘BG version rockers’ combination version for EK-ED2-TP
Figure 11A – ‘RW’ version rockers’ combination version for EK-ED2-TP

Application manual
The rockers’ configuration is equivalent in BG (green and blue leds) and in RW (red and white).
Available rocker plate configuration options for 2-4 rocker pushbutton:

a. 2 vertical rectangular rockers
b. 4 square rockers
c. 4 rectangular horizontal rockers

Application manual
Figure 9B – ‘BG version rockers’ combination version for EK-E12-TP
Figure 12B – ‘RW version rockers’ combination version for EK-E12-TP

Application manual
The rockers’ configuration is equivalent in BG (green and blue leds) and in RW (red and white).
Available rocker plate configuration options for 1-4 rocker pushbutton:

d. 1 single square rocker*
e. 2 vertical rectangular rockers
f. 4 square rockers
g. 4 rectangular horizontal rockers

Application manual
7.3 Internal sensors

Temperature sensor disabled / enabled
Enables the temperature sensor by making the corresponding communication
object available.

Temperature sensor = [9.001]
Temperature value 2 Byte CR–T- 3
enabled temperature (°C)
7.3.1 Temperature sensor

low
Filter type Temperature sensor = enabled average
high
Low = average value every 4 measurements
Average = average value every 16 measurements
High = average value every 64 measurements
0°C
Measured temperature correction Temperature sensor = enabled
[range -2,5°C … +2,5°C]
Offset steps are 0.1°C in order to perform a more effective sensor calibration.
0,5
Minimum change of value to send [K] Temperature sensor = enabled
[range 0 … 5]
If the parameter is set to 0, no value is sent for change
no sending
Cyclic sending interval Temperature sensor = enabled
[other values in range 30 s … 120 min]
not active
Threshold 1 Temperature sensor = enabled below
above
Temperature sensor = enabled, 7

Value [°C]
Threshold 1 = above or below [range 0 … 50]
not active
Threshold 2 Temperature sensor = enabled below
above
Temperature sensor = enabled, 45

Value [°C]
Threshold 2 = above or below [range 0 … 50]
Temperature sensor = enabled,

0,4 K
Hysteresis Threshold 1 e/o Threshold 2 =
[other values in range 0,2 K ... 3 K]
above or below
Temperature sensor = enabled,

no sending
Cyclic sending interval Threshold 1 e/o Threshold 2 =
above or below

Application manual
No. Comm.
Object name Conditions Dim. Flags DPT
Obj.
Temperature threshold 1 - Temperature sensor = enabled,
1 Bit CR-T-- [1.001] switch 162
Switch Threshold 1 = above or below
Temperature threshold 2 - Temperature sensor = enabled,

1 Bit CR-T-- [1.001] switch 163
Switch Threshold 2 = above or below

Application manual
7.4 Rockers configuration

disabled
independent or single
Rocker x -
coupled
copy parameters from rocker*
Set operation mode for inputs corresponding to Rocker x.
The identification of which Rocker and associated input pushbuttons are corresponding to a given
number (e.g. 1A – 2B – 4A etc.) is done according to parameter “General / Rockers configuration”.
* This option is only available for rockers no. 2 and above. If selected, the corresponding rocker can be
made to perform the exact same kind of function as another specified rocker, but basing on different
communication objects.
This allows sparing time in configuring the device, at the same time assuring that there is no
inconsistency between two rockers that are meant to be configured in exactly the same way.
To assign the same configuration is just a shortcut for the selection of configuration options; it is in no
way implied that the two rockers share any of the involved communication objects (each rocker has its
own independent objects).
Function A Rocker x = independent or single enabled / disabled
Enables or disables the capability to generate events for the first pushbutton of the rocker.
send values or sequences
Rocker x = independent or single dimming
Type
Function A = enabled shutter or venetian blind
scene
Determines the kind of function performed by the FIRST rocker input.
Further parameters for the selected function will appear in the individual rocker configuration sections
(see below).
disabled
Function B Rocker x = independent or single enabled
in parallel with function A, as a single function
copy parameters from function A
Enables or disables the capability to generate events for the second pushbutton of the rocker.
If not disabled, the pushbutton can be given an own independent function (enabled),used as an “alias”
of the first input (in parallel), or perform the exact same kind of function as first input (copy parameters),
but possibly basing on a different communication object.
send values or sequences
Rocker x = independent or single dimming
Type
Function B = enabled shutter or venetian blind
scene
Determines the kind of function performed by the SECOND rocker input.
(see below).
switch
Type Rocker x = coupled dimming
shutter or venetian blind
Determines the kind of function performed by the FIRST and SECOND rocker input.
(see below).
Rocker x = copy parameters from
Rocker to copy from rocker 1..4*
(x > 1)
* The values that can be chosen obviously do not include the number of the rocker for which the
selection is made.

Application manual
7.4.1 Independent or single: send values or sequences

Rocker x = independent or 5, 22 (1A, 1B)
according to
Rocker x – single according to the
the 43, 60 (2A, 2B)
Switching status [type], object Function x = enabled CRWTU configuration
configuration 81, 98 (3A, 3B)
n Type = send values or ([1.001] switch)
(1-bit) 119, 136 (4A, 4B)
sequences
Up to 8 objects can be defined for binding with the same event.
The listed CO numbers are those referring to object nr.1; the COs for each subsequent object are
following in sequence.
To obtain the CO numbers for object number n, just add (n-1) to the listed numbers.
E.g.: COs associated to input 3A (of Rocker 3) have numbers from 81 to 89. The number of CO
no. 5 is therefore 81+(5-1) = 85.
The size and type of the individual objects can be configured as described in following
sections.
7.4.2 Independent or single: dimming

Rocker x – single [1.001] 47, 64 (2A, 2B)
1 bit CRWTU
Switching command Function x = enabled switch 81, 98 (3A, 3B)
Type = dimming 115, 132 (4A, 4B)
Send a command to a dimming actuator to switch the light on or off.
The command is triggered by a short press on the input.
The value sent can be a fixed value or it can be toggled at each input activation.

Rocker x –
single [3.*] 48, 65 (2A, 2B)
Dimming up / down / stop 4 bit CR-T-
Function x = enabled 3-bit control 82, 99 (3A, 3B)
command
Type = dimming 116, 133 (4A, 4B)
Send a command to a dimming actuator to change dimming intensity (brighter or darker).
Three values are used which mean start increase, start decrease or stop the change.
Increase/decrease values are sent when a long press action occurs and stop value on press
release.
The value sent can be a fixed value or it can be toggled at each input activation.

Application manual
7.4.3 Independent or single: shutter or venetian blind

single
Rocker x – [1.017] 47, 64 (2A, 2B)
Function x = enabled 1 bit CRWTU
Dedicated stop command trigger 81, 98 (3A, 3B)
Type = shutter or venetian
blind 115, 132 (4A, 4B)
Immediately stop any movement of the blind. The object is sent on a short press if the blind
mode is disabled and at the end of a long press if the venetian blind mode is enabled.
Rocker x = independent or
single 16, 33 (1A, 1B)
Rocker x – Function x = enabled [1.007] 50, 67 (2A, 2B)
1 bit CR-T-
Stop – step up/down command Type = shutter or venetian step 84, 101 (3A, 3B)
blind 118, 135 (4A, 4B)
Blind mode = enabled
Move the blind to fully open or fully closed position. The object is sent at the end of a long
press.
single
Rocker x – [1.008] 51, 68 (2A, 2B)
Function x = enabled 1 bit CRWTU
Move up / down command up/down 85, 102 (3A, 3B)
Type = shutter or venetian
blind 119, 136 (4A, 4B)
Increase or decrease the opening of the blind stepwise.
The object is sent on a short press.
7.4.4 Independent or single: scene
Rocker x = independent or [17.*] 18, 35 (1A, 1B)

Rocker x – single Scene number 52, 69 (2A, 2B)
1 Byte CR-T-
Scene number Function x = enabled [18.*] 86, 103 (3A, 3B)
Type = scene Scene control 120, 137 (4A, 4B)
Store or recall a scene. The lowest 6 bits in the byte form the code of the scene, while the
highest bit is the operation code (store or recall).

Application manual
7.4.5 Coupled: switch

Rocker x = coupled
Rocker x – [1.001]
Function x = enabled 1-bit CRWTU 13, 47, 81, 115
Switching command switch
Type = switch
7.4.6 Coupled: dimming

Rocker x = coupled
Rocker x – [1.001]
Function x = enabled 1 bit CRWTU 13, 47, 81, 115
Switching command switch
Type = dimming
See notes for independent input.
Rocker x = independent or
Rocker x –
single [3.*]
Dimming up / down / stop 4 bit CR-T- 14, 48, 82, 116
Function x = enabled 3-bit control
command
Type = dimming
7.4.7 Coupled: shutter or venetian blind

Rocker x = coupled
Function x = enabled
Rocker x – [1.017]
Type = shutter or venetian 1 bit CRWTU 13, 47, 81, 115
Dedicated stop command trigger
blind
Blind mode = disabled
Rocker x = coupled
Function x = enabled
Rocker x – [1.007]
Type = shutter or venetian 1 bit CR-T- 16, 50, 84, 118
Stop – step up/down command step
blind
Blind mode = enabled
Rocker x = coupled
Rocker x – Function x = enabled [1.008]
1 bit CRWTU 17, 51, 85, 119
Move up / down command Type = shutter or venetian up/down
blind
7.5 Rocker x: Function A/B configuration
7.5.1 Independent or single
For the independent or single channel setting, all parameters listed below are referred to either Function A or
Function B (whichever are enabled).

Application manual
In the following sections, it is implicitly understood that for the listed parameters to appear, the corresponding
functions xA and/or xB must be enabled.
The entries assigned to “Object n” are repeated so many times as the number of configured objects according
to the Number of Communication Objects parameter.
For all Type values:

Lock function - enabled / disabled
Enables or disables the capability of locking the input through a remote command (telegram).
Lock function – Rocker x = independent or single
not inverted / inverted
Invert lock device signal Type = send values or sequences
Allows interpreting a “lock activate” telegram as unlock and vice-versa.
Lock function – Rocker x = independent or single
no / yes
Lock after bus recovery Type = send values or sequences
If active, after returning from a bus failure or power-off the device will retain the lock status it had
before. Otherwise (in the default case), the device will restart in the non-locked condition.

Application manual
7.5.2 Independent or single: Lock function enabled
Rocker x = Independent or 4, 21 (1A, 1B)

Rocker xx – single [1.003] 38, 55 (2A, 2B)
1 bit C-W--
Lock function Lock function = enabled enable 72, 89 (3A, 3B)
106, 123 (4A, 4B)
When the lock function is enabled, for each input or rocker the user can define an action to execute when a
lock or unlock command is received.
Details are shown in the following sections; a resume of all options is shown in the table below.
Behaviour Behaviour at
Channel mode Input type
at locking unlocking
independent none
send values or
as close or short press
sequences
as open or long press
switching none none

coupled off off
independent on on
dimming toggle as previous
coupled
independent none
scene send first scene
send second scene
independent none
shutter or venetian
up
coupled blind
down

Application manual
7.5.3 Independent or single: send values or sequences

Number of communication Rocker x = independent or single 1…8
objects Type = send values or sequences (1)
Number of communication objects configured in association with the button event.
Lock function – Rocker x = independent or single none
Behaviour at locking Type = send values or sequences as open or long press
Allows performing the operation associated to the specified event when a locking command is
received. You can choose between operations linked to two possible closing (or short press,
depending on the configuration) or opening (or long press) events.
Behaviour at unlocking Type = send values or sequences as open or long press
Allows performing the operation associated to the specified event when an unlocking command is
received. You can choose between operations linked to two possible closing (or short press,
depending on the configuration) or opening (or long press) events.
Rocker x = independent or single close / open contact
Event
Type = send values or sequences short / long press
Type of event that should be used as trigger for an action.
Rocker x = independent or single
hh:mm:ss.fff
Long press time Type = send values or sequences
(00:00:03.000)
Event = short / long press
Minimum push time for a press in order to be recognized as a long press.
Object n – Rocker x = independent or single hh:mm:ss.ff
Send delay Type = send values or sequences (00:00:00.00)
Delay before the object is transmitted on the bus.
By defining a delay after the event occurs and before the object value is sent, it is possible to
associate a time defined sequence of values to an input event.
Rocker x = independent or single none
Object n – off / value 1
Type = send values or sequences on / value 2
Send cyclically
Number of communication objects = 1 both off and on / both values
Defines which of the values, if any, must be cyclically retransmitted whenever activated.
The cyclical transmission is only available if the number of communication objects to link is 1.
Object n – Type = send values or sequences hh:mm:ss
Cyclic sending interval Number of communication objects = 1 (00:02:00)
Send cyclically ≠ none
Interval between cyclical transmissions.
1 bit value
2 bits value
1 byte unsigned value
Object n – Rocker x = independent or single 1 byte percentage
send dimension Type = send values or sequences 1 byte signed value
2 bytes unsigned value
2 bytes signed value
2 bytes floating value
Defines size and type of the values to be sent when an event occurs.
Object n – on
Type = send values or sequences
Close or Short press off
send dimension = 1 bit toggle

Application manual

none
disable
Rocker x = independent or single enable off / up
Type = send values or sequences enable on / down
send dimension = 2 bit enable off / up ↔ disable
enable on / down ↔ disable
enable off / up ↔ enable on / down
Type = send values or sequences send value 1
send value 2
send dimension = any byte value send value 1 ↔ send value 2
Value change behaviour caused by either a Close or a Short Press event (according to event
configuration)

on
Type = send values or sequences off
send dimension = 1 bit toggle
none
disable
Object n – enable off / up
Type = send values or sequences enable on / down
Open or Long press
send dimension = 2 bit enable off / up ↔ disable
enable on / down ↔ disable
enable off / up ↔ enable on / down
Type = send values or sequences send value 1
send value 2
send dimension = any byte value send value 1 ↔ send value 2
Value change behaviour caused by either an Open or a Long Press event (according to event
configuration)
0...255 (1 byte unsigned value)
Rocker x = independent or single 0…100 (1 byte percentage)
Object n – -128...127 (1 byte signed value)
Type = send values or sequences 0...65535 (2 bytes unsigned value)
Value 1
send dimension = any byte value -32768... 32767 (2 bytes signed value)
-671088.64...670760.96 (2 bytes floating value)
First value available for association in send events
Object n –
Type = send values or sequences same as value 1
Value 2
send dimension = any byte value
Second value available for association in send events

Rocker x = Independent or 5, 22 (1A, 1B)
Rocker xx – single See table See table 39, 56 (2A, 2B)
CR-TU
Switching status [type] Object n Type = send values or below below 73, 90 (3A, 3B)
sequences 107, 124 (4A, 4B)
The listed CO numbers are those referring to object nr.1; the COs for each subsequent object
are following in sequence.
To obtain the CO numbers for object number n, just add (n-1) to the listed numbers.
E.g.: COs associated to input 3A (of Rocker 3) have numbers from 81 to 89. The number of CO
no. 5 is therefore 81+(5-1) = 85.

Application manual
Sizes and DPTs are as follows:
Size DPT
1 bit [1.001] switch
2 bit [2.*] 1-bit controlled
[4.*] character
1 byte unsigned value [5.*] 8-bit unsigned value
[20.*] 1-byte
[4.*] character
1 byte percentage [5.*] 8-bit unsigned value
[20.*] 1-byte
1 byte signed value [6.*] 8-bit signed value
2 bytes unsigned value [7.*] 2-byte unsigned value
2 bytes signed value [8.*] 2-byte signed value
2 bytes floating value [9.*] 2-byte float value

Application manual
7.5.4 Independent or single: dimming

Rocker x = independent or single hh:mm:ss.fff
Long press time
Type = dimming (00:00:03.000)
Toggle mode enabled / disabled
Type = dimming
When enabled, causes the short press to toggle the on-off status of the destination CO; otherwise, a
fixed status can be assigned to the short press.
Rocker x = independent or single darker
Long action Type = dimming brighter
Toggle mode = enabled darker ↔ brighter
Defines the function to be assigned to the long press. If the toggle mode is enabled, the Short press
action is already defined as toggle.
Rocker x = independent or single off / darker
Short / Long action Type = dimming on / brighter
off / darker ↔ brighter
Toggle mode = disabled on / darker ↔ brighter
Defines the function to be assigned to the long and short press.
none
Rocker x = independent or single off / value 1
Send cyclically
Type = dimming on / value 2
both off and on / both values
Cyclic sending interval Type = dimming hh:mm:ss (00:02:00)
none
Lock function – Rocker x = independent or single off
Behaviour at locking Type = dimming on
toggle
Value to be assigned to the object when a locking command is received.
none
Lock function – Rocker x = independent or single off
Behaviour at unlocking Type = dimming on
as previous
Value to be assigned to the object when an unlocking command is received.

Application manual
7.5.5 Independent or single: shutter or venetian blind

Rocker x = independent or single hh:mm:ss.fff
Long press time
Type = shutter or venetian blind (00:00:03.000)
Toggle mode enabled / disabled
Type = shutter or venetian blind
When enabled, causes the short press to toggle the on-off status of the destination CO; otherwise, a
fixed status can be assigned to the short press.
Type = shutter or venetian blind up
Up / Down action
down
Toggle mode = disabled
Defines the movement direction to be assigned to the button press.
Blind mode enabled / disabled
If blinds mode is enabled, the device sends “full movement” telegrams on long press and “step”
telegrams on short press; if it is disabled, the device sends “full movement” telegrams on long press
and “stop” telegrams on short press.
up
Behaviour at locking Type = shutter or venetian blind down
Operation to perform when a locking command is received.
up
Behaviour at unlocking Type = shutter or venetian blind down
Operation to perform when an unlocking command is received.

Application manual
7.5.6 Independent or single: scene

Rocker x = independent or single 1…64
First scene number
Type = scene (1)
Main scene number to be assigned to button press. It is named “first” for the case that an
alternative scene number is used.
Learning mode enabled / disabled
Type = scene
When enabled, a long key press can be used to program the selected scene by storing the current
parameters.
hh:mm:ss.fff
Long press time Type = scene
(00:00:03.000)
Learning mode = enabled
Type = scene send first scene only
Scene activation
toggle between two scenes
Learning mode = disabled
Allows the key to be used to alternate between two different scenes.
Type = scene
1…64
Second scene number Learning mode = disabled
(2)
Scene activation = toggle between two
scenes
Alternate scene number to be assigned to button press.
send first scene
Behaviour at locking Type = scene send second scene
send first scene
Behaviour at unlocking Type = scene send second scene

Application manual
7.5.7 Coupled
For a coupled channel, all the parameters are referred to the single menu entry for Function xA and xB.
In the following sections, it is implicitly understood that for the listed parameters to appear, the corresponding
functions xA and xB must be enabled.
For all Type values:
Lock function Rocker x = coupled enabled / disabled
Enables or disables the capability of locking the input through a remote command (telegram).
7.5.8 Coupled: Lock function enabled

Rocker x = coupled
Rocker xx – [1.003]
Lock function = enabled 1 bit C-W-- 4, 38, 72, 106
Lock function enable
7.5.9 Coupled: switch

Rocker x = coupled A on, B off
xA and xB use
Type = switch A off, B on
Allows to invert side A and side B functionalities
none
Rocker x = coupled off / value 1
Send cyclically
Type = switch on / value 2
Rocker x = coupled
hh:mm:ss
Cyclic sending interval Type = switch
(00:02:00)
none
Lock function – Rocker x = coupled on
Behaviour at locking Type = switch off
toggle
none
Behaviour at unlocking Type = switch off
as previous

Application manual
7.5.10 Coupled: dimming

Rocker x = coupled hh:mm:ss.fff
Long press time
Type = dimming (00:00:03.000)
Rocker x = coupled A increases, B decreases
xA and xB use
Type = dimming A decreases, B increases
none
Rocker x = coupled off / value 1
Send cyclically
Type = dimming on / value 2
Rocker x = coupled
hh:mm:ss
Cyclic sending interval Type = dimming
(00:02:00)
Send cyclically ≠ no
none
Behaviour at locking Type = dimming off
toggle
none
Behaviour at unlocking Type = dimming off
as previous

Application manual
7.5.11 Coupled: shutter or venetian blind

Rocker x = coupled hh:mm:ss.fff
Long press time
Type = shutter or venetian blind (00:00:03.000)
Rocker x = coupled A up, B down
xA and xB use
Type = shutter or venetian blind A down, B up
Rocker x = coupled
Blind mode enabled / disabled
If blinds mode is enabled, the device sends “full movement” telegrams on long press and “step”
telegrams on short press; if it is disabled, the device sends “full movement” telegrams on long press
and “stop” telegrams on short press.
Lock function – Rocker x = coupled none
up
Behaviour at locking Type = shutter or venetian blind down
Lock function – Rocker x = coupled none
up
Behaviour at unlocking Type = shutter or venetian blind down
For other communication objects related to coupled mode, please refer to the general Rockers Configuration
section.

Application manual
7.6 LED configuration

Following parameters are repeated for each of the available LEDs.
LED parameters settings are always listed grouped by rocker (regardless whether the inputs are coupled or
not): for each rocker x, available LEDs are marked as LED First Colour (green in BG version, red in RW)
and LED Second Colour (blue in BG version, white in RW).
Figure 13A - Number convention for LED couples EK-ED2-TP and EK-E12-TP

fixed
LED X First
- when contact closed
colour/Second colour
status from bus
Always LED X First colour/Second colour = fixed on / off

Status for a fixed LED condition
LED X First colour/Second colour = when hh:mm:ss.ff

Off delay
contact closed (00:02:00.00)
Delay before LED goes off
LED X First colour/Second colour = status
Blinking no / yes
from bus
LED X First colour/Second colour = status

Signal from bus not inverted / inverted
from bus
Specifies whether the LED status from the bus should be inverted, i.e. LED on when an “off” command
is received on the communication object.
This feature is useful because the condition for the LED to switch on can be linked to a communication
object related to the state of another device, which may have an opposite logic.

LED X – LED first colour 1 = status from 140, 142, 144, 146,
1 bit CRWTU- [1.001] switch
First colour bus 148, 150, 152, 154
LED X - LED second colour 1 = status from 141, 143, 145, 147,
1 bit CRWTU- [1.001] switch
Second colour bus 149, 151, 153, 155

Application manual
Rocker combinations
LED a) b) c) d)
Independent A/B functions 1A 1A 1A 1A
1
Parallel A/B functions 1A 1A 1A not allowed
Independent A/B functions 1A 1A 1B 2A
Parallel A/B functions 2
1A 1A 1A not allowed
Independent A/B functions 1B 1B 3A 3A
Independent A/B functions 1B 1B 3B 4A
Parallel A/B functions
4
Independent A/B functions 1A 2A 2A 1B
Independent A/B functions 1A 2A 2B 2B
Independent A/B functions 1B 2B 4A 3B
Parallel A/B functions
7
Independent A/B functions 1B 2B 4B 4B
This table shows the LEDs (according to the adopted convention) activated with a press on the areas,
according to the adopted rocker combination.

Application manual
7.7 Temperature control

The Temperature control folder allows the pushbutton to be configured as a room temperature controller and
also allows filtrating, through a weighted mean average, the reading from the internal sensor with the reading
from an auxiliary sensor added on the bus.
The folder is active only if the room temperature sensor has been enabled: Internal sensors  Temperature
sensor = enabled.
It includes the following secondary folders:
 Settings
 Sensors from bus
 Weighted temperature value
 Heating
 Cooling
7.7.1 Settings
The Settings includes the parameters to perform the basic configuration of the room temperature controller:
 Heating and cooling function
 Setpoint management mode: single or relative
 Separated actuator command or common in heating/cooling
 Heating/cooling switch over type
 Valve protection function activation
This folder is always active.

disabled
heating
Thermostat function
cooling
both heating and cooling
Single setpoint
Setpoint management Absolute setpoints
Relative setpoints
In case the option “Single setpoint” in selected and Thermostat function = heating,
the temperature controller acts on heating mode; in case Thermostat function =
cooling, the temperature controller acts on cooling mode.
In case Thermostat function = both heating and cooling, the current seasonal mode
needs to be specified by the proper communication object.
Thermostat function = both heating
Command Communication Object separated / unique
and cooling
Thermostat function = both heating

and cooling,
Heating–cooling switch over from bus / automatic
Setpoint management = Relative
setpoints
In case Setpoint management = single setpoint, the heating-cooling switch over
must be carried out from bus.

Application manual

no sending
Cyclic sending interval setpoint
In case Setpoint management = single setpoint, the actual setpoint value takes only
into account the actual state of the contacts window (if the corresponding function is
enabled).
In case Setpoint management = relative setpoints, the actual setpoint value also
depends on the operating mode set manually by the user or automatically by another
KNX supervising device with the possibility of time scheduling.
Setpoint management = Absolute till first telegram from bus
End of manual operation
setpoints or Relative setpoints [other values in the range 30 min…48 h]
It defines the end of manual operation modes.
Valve protection function disabled / enabled
It enables the function that activates the drive for the valve control during periods of
inactivity of the system.
once a day,
Frequency Valve protection function = enabled once a week,
once a month
10 s
Time interval Valve protection function = enabled
All communication object are active only if parameter Settings  Thermostat function ≠ disabled
No.
Object name Conditions Dim. Flags DPT Comm.
Obj.
Thermal generator lock 1 Bit -WC--- [1.001] switch 160
Temperature control alarm 1 Bit CR-T- [1.005] alarm 161
Actual setpoint 2 Byte CR-T-- [9.001] temperature (°C) 175
Heating / cooling status out Always exposed 1 Bit CR-T-- [1.100] heating/cooling 168
The communication object is sent over the bus after an internally elaborated switching event.
[1.100] DPT Heat/Cool 1 Bit
0 = CoolT
ambiente [°C]
1 = HeatingT
Thermostat function = both Setpoint
heating and cooling,
Heating / cooling status in 1 Bit C-W--- [1.100] heating/cooling 169
Heating–cooling switch
over = from bus
The communication object is received from the bus. At the switching event the internal regulator
switches the conduction mode.

Application manual
No.
Obj.
Setpoint management =
HVAC mode in Absolute setpoints or 1 Byte C-W--- [20.102] HVAC mode 170
Relative setpoints
Bits 5, 8 are reserved.
[20.102] DPT HVAC Mode 1 Byte
AUTO COMFORT STAND-BY
0 0 0 0 0 0 0 1 0 0 1 0
ECONOMY PROTECTION
0 0 1 1 0 1 0 0
HVAC forced mode in Absolute setpoints or 171
Relative setpoints
HVAC manual mode Absolute setpoints or 1 Byte C-W--- [20.102] HVAC mode 172
Relative setpoints
Chrono active status Absolute setpoints or 1 Bit CRWTU- [1.011] state 173
Relative setpoints
HVAC mode out Absolute setpoints or 1 Byte C-W--- [20.102] HVAC mode 174
Relative setpoints
7.7.2 Monitoring and remote control of the conduction mode
The communication objects indicated in the block diagram allows monitoring and modifying the current
conduction mode forced on the temperature controller. The object Heating/cooling status out is always
exposed, even when the thermostat function is set on heating or cooling only. When the function is set on both
heating and cooling, the cyclic sending on bus can be enabled; anyway, the information about the actual
conduction mode can be acquired with a reading request to this commiunication object.
The object Heating/cooling status in is exposed only when the function is both heating and cooling and the
switching among the different modes is performed by the bus.
169 - Heating / cooling status in [1.100]
168 - Heating / cooling status out [1.100]

Application manual
7.7.3 Remote operative mode modification
The communication objects shown in figure allow to monitor the operating mode (comfort, standy, economy
and building protection) modifications performed locally by the user when interacting with the LCD display and
the touch buttons of the room thermostat, or the operating mode forced by chrono program.
HVAC mode in [20.102]
HVAC manual mode [20.102]
HVAC out mode [20.102]
Chrono active status [1.011 state]
The C.O. HVAC mode in is associated to the chrono program. The C.O.s HVAC mode out and HVAC chrono
active status allow the remote supervisor to discern the operating mode currently active on the room
thermostat and also allow to understand if the chrono program is active or if attenuation is handled manually
or not. The supervisor can set at any time a manual operating mode through C.O. HVAC manual mode; to
start the chrono program remotely, the C.O. HVAC manual mode is to be set on value 0 = Automatic.

Application manual
7.7.4 Remote Setpoint modification
These communication objects allow to perform the same modifications remotely, for example from a supervisor
software.
Input setpoint [9.001 temperature]
Actual setpoint [9.001 temperature]
Manual setpoint [9.001 temperature]
Actual setpoint [9.001 temperature]
Manual/forced setpoint active status [1.011 state]
Those objects are about the Setpoint forced modification: alternatively, the supervisor can act directly on the
operating mode setpoints. The value of the C.O. Actual setpoint represents the current operative setpoint
which the control algorithms are based on. The C.O. Manual/forced setpoint active status indicates (read
request mode) if the forced mode is active (symbol M on the LCD display present). The supervisor can force
at any time the actual setpoint by writing a new value directly into the C.O. Manual setpoint. The C.O.
Manual/forced setpoint active status can also be used in writing to exit the active forced mode.

Application manual
7.7.5 Sensors from bus
Sensors from bus are KNX devices (or traditional sensors interfaced to the bus by means of KNX devices)
which send values or states to the pushbutton via bus. The folder allows activating an auxiliary temperature
sensor and 2 window contacts to automatically recall the building protection setpoint: the automatic recall
function must be individually configured for the 2 conduction modes in Heating and/or Cooling folder.
The internal pushbutton control system cyclically monitors the updating status of the values of the
external sensors (from bus) when the timeout setting expires. In case no updated value has been
i received, the regulation function is suspended and the actuation valves are closed. An alarm is
issued on the bus through communication object Temperature control alarm (please refer to
Settings folder).
The folder is always active.

Room temperature (from bus) disabled / enabled
Enables a temperature bus sensor. The measured value can be used to
calculate a weighted mean average with the integrated temperature sensor.
00:05:00 hh:mm:ss
Analog sensor timeout (from bus)
[range 00:00:00 … 18:12:15]
The field has format hh:mm:ss (hours : minutes : seconds): the default value
00:05:00 corresponds to a timeout of 5 minutes. The value 00:00:00 means
that the timeout of the analogic sensors is disabled.
Window contact 1 disabled / enabled
It enables a bus sensor for detecting the state of opening / closing of a window
or a door.
Signal Window contact 1 = enabled not inverted / inverted
Window contact 2 disabled / enabled

It enables a bus sensor for detecting the state of opening / closing of a window
or a door.
Signal Window contact 2 = enabled not inverted / inverted
No. Comm.
Object name Conditions Dim. Flags DPT
Obj.
[9.001]
Room temperature (from bus) enabled 2 Byte C-W--- 164
temperature (°C)
Windows contact sensor 1 (from [1.019]

enabled 1 Bit C-W--- 165
bus) window/door
Windows contact sensor 2 (from [1.019]

enabled 1 Bit C-W--- 166
bus) window/door

Application manual
7.7.6 Weighted temperature value
The Weighted temperature value folder allows calculating a weighted mean average between the integrated
temperature sensor value and the temperature sensor from bus value. The calculated temperature is then
used as main temperature value in the integrated room temperature controller’s algorithm.
The folder is active if: Sensors from bus  Room temperature (from bus) = enabled.

100% main sensor
90% / 10%
80% / 20%
70% / 30%
60% / 40%
Relative weight 50% / 50%
40% / 60%
30% / 70%
20% / 80%
10% / 90%
100% sensor from bus
The main sensor is always the integrated sensor; the sensor from bus needs to be
activated in Sensors from bus folder.
0,5
Minimum change of value to send [K]
[other values in range 0 … 5 K]
If the parameter is set to 0, no value is sent for change
no sending
Cyclic sending interval
No.
Obj.
Cyclic sending interval ≠ no [9.001]
Weighted temperature 2 Byte CR-T-- 167
sending temperature °C

Application manual
7.7.7 Heating
The Heating folder allows setting:

 The default value for single and relative setpoints (comfort, standby and economy setpoints);
 Control algorithm type (2-point hysteresis, PWM or continuous) and internal parameters;
 Building protection mode activation based on up to 2 window contacts’ status.
Conditions of activation: Settings  Thermostat function = heating or both heating and cooling.

21
Temperature setpoint [°C] Setpoint management = Single setpoint
[range 10 … 50]
Setpoint management = Relative 21

Comfort temp. setpoint [°C]
setpoints [range 10 … 50]
Setpoint management = Relative - 30

Standby temp. offset [0,1 K]
setpoints [range -10 … -50]
Setpoint management = Relative -50

Economy temp. offset [0,1 K]
setpoints [range -10 … -50]
7
Building protection temp. setpoint [°C]
[range 2 … 10]
2 point hysteresis,
Control type PWM (pulse width modulation)
continuous
0,3 K
Hysteresis Control type = 2 point hysteresis
[other values in range 0,2 K … 3 K]
below
Hysteresis position Control type = 2 point hysteresis
above
The above hysteresis is suitable in case of special applications requiring mixing group
control.
Control type = 2 point hysteresis, no sending
continuous [other values in range 30 s … 120 min]
10
Min. change of value to send [%] Control type = continuous
[range 0 … 100]
Control type = PWM (pulse width 15 min

PWM cycle time
modulation) [range 5 … 240 min]

Application manual

Min control value [%] Control type = PWM and continuous 15 % [range 0 %…30 %]
Max control value [%] Control type = PWM and continuous 85 % [range 70 %…100 %]
radiators (5 K / 150 min)

electric (4 K / 100 min)
Heating type Control type = continuous or PWM floor radiant panels (5 K / 240 min)
ceiling radiant panels (5 K / 180 min)
other
Control type = continuous or PWM, 40

Proportional band [0,1 K]
Heating type = other [range 5 … 100]

Integral time [min]
Heating type = other [range 0 … 255 min]
Sensors from bus  Window contact 1 =

Use window contacts to activate building enabled, or
disabled / enabled
protection mode Sensors from bus  Window contact 2 =
enabled
Parameter enabling window contact function.
Waiting time before activating building Use window contacts to activate building 00:01:00 hh:mm:ss
protection mode protection mode = enabled [range 00:00:00 … 18:12:15]
Time interval before the device automatically switches to building protection mode.
All communication objects are active if Settings  Thermostat function = heating or both heating and cooling.
No.
Obj.
Setpoint management = Single [9.001] temperature
Input setpoint 2 Byte CRWTU- 178
setpoint (°C)
Heating comfort setpoint Setpoint management = 2 Byte CRWTU-

[9.001] temperature
179
Relative setpoints (°C)
Relative setpoints, [9.002] temperature
Heating standby offset 2 Byte CRWTU- 181
Heating/cooling switch over = difference (K)
manual
Relative setpoints, [9.002] temperature
Heating economy offset 2 Byte CRWTU- 183
manual
Heating building protection [9.001] temperature

2 Byte CRWTU- 185
setpoint (°C)
Control type = 2 point hysteresis

Heating out command 1 Bit CR-T-- [1.001] switch 187
or PWM
[5.001] percentage
Heating out command Control type = continuous 1 Byte CR-T-- 187
(0..100%)

Application manual
7.7.8 Cooling
The Cooling folder allows setting:

 The default value for single and relative setpoints (comfort, standby and economy setpoints) in case
of manual heating/cooling switch over;
 The default value for the switch over dead band and for standby and economy attenuation in case of
automatic heating/cooling switch over;
 Control algorithm type (2-point hysteresis, PWM or continuous) and internal parameters;
 Building protection mode activation based on up to 2 window contacts’ status.
Conditions of activation: Settings  Thermostat function = heating or both heating and cooling.
Parameter name Conditions Valori

23
Temperature setpoint [°C] Setpoint management = Single setpoint
[campo 10 … 50]

Switch over dead band setpoints,
[campo 10 … 40]
Heating/cooling switch over = automatic

Comfort temp. setpoint [°C] setpoints,
[campo 10 … 50]
Heating/cooling switch over = from bus

Standby temp. offset [0,1 K]
setpoints [campo 10 … 50]

Economy temp. offset [0,1 K]
setpoints [campo 10 … 80]
36
Building protection temp. setpoint [°C]
[campo 30 … 50]
isteresi a 2 punti,
Command for both heating and cooling = PWM (modulazione ad ampiezza
Control type
separated d’impulso),
continuo
If in Settings the parameter Thermostat function = both heating and cooling and
Command communication object = unique, the parameter Cooling type is bound to the
choice done for Heating.
0,3 K
Hysteresis Control type = 2 point hysteresis
[altri valori nel campo 0,2 K … 3 K]
superiore
Hysteresis position Control type = 2 point hysteresis
inferiore
The below hysteresis is suitable in case of special applications requiring mixing group
control.
Control type = 2 point hysteresis, nessun invio
continuous [altri valori nel campo 30 s … 120 min]
10
Min. change of value to send [%] Control type = continuous
[campo 0 … 100]

Application manual
Parameter name Conditions Valori

Control type = PWM (pulse width 15 min
PWM cycle time
modulation) [campo 5 … 240 min]
Min control value [%] Control type = PWM 15 [campo 0…30]
Max control value [%] Control type = PWM 85 [campo 70…100]
pavimento radiante (5 K / 240 min)

Cooling type Control type = continuous or PWM soffitto radiante (5 K / 180 min)
altro

Proportional band [0,1 K]
Cooling type = other [campo 5 … 100]

Integral time [min]
Cooling type = other [campo 0 … 255 min]
Sensors from bus  Window contact 1 =

Use window contacts to activate building enabled, or
disabilitato / abilitato
protection mode Sensors from bus  Window contact 2 =
enabled
Parameter enabling window contact function.
Waiting time before activating building Use window contacts to activate building 00:01:00 hh:mm:ss
protection mode protection mode = enabled [campo 00:00:00 … 18:12:15]
Time interval before the device automatically switches to building protection mode.
All communication objects are active if Settings  Thermostat function = heating or both heating and cooling.
No.
Obj.
Setpoint management = Single
Input setpoint 2 Byte CRWTU- [9.001] temperature (°C) 178
setpoint

setpoints,
Cooling comfort setpoint 2 Byte CRWTU- [9.001] temperature (°C) 180
Heating/cooling switch over =
from bus

setpoints, [9.002] temperature
Cooling standby offset 2 Byte CRWTU- 182
from bus

setpoints, [9.002] temperature
Cooling economy offset 2 Byte CRWTU- 184
from bus
Cooling building protection

2 Byte CRWTU- [9.001] temperature (°C) 186
setpoint
Control type = 2 point hysteresis or

Cooling out command 1 Bit CR-T-- [1.001] switch 188
PWM

Application manual
No.
Obj.
[5.001] percentage
Cooling out command Control type = continuous 1 Byte CR-T-- 188
(0..100%)

Application manual
7.8 Logic functions

The pushbutton interfaces EK-ED2-TP and EK-E12-TP allow to use some useful logic functions (AND, OR,
NOT and exclusive OR) in order to implement complex functions in the building automation system.
You can configure:
 8 channels of logical functions

 4 inputs for each channel
Each object value, if desired, can be individually inverted by inserting a NOT logic operator.
For each channel, a parameter Delay after bus voltage recovery is available: this parameter represents the
time interval between the bus voltage recovery and the first reading of the input communication objects for
evaluating the logic functions.
In case of uncorrect connection of the input communication object or electrical trouble on bus
i resulting in a failed input reading request, the logic output of the corresponding channel can be
calculated by setting the input values to default.
The communicaton function representing the logic function output is sent on the bus on event of change;
alternatively, a cyclic sending can be set.
7.8.1 Parameter and communication object tables

The following condition has to be true: General  Logic functions = enabled.

Logic function disabled / enabled
Logic operation Logic function = enabled OR / AND / XOR

XOR (eXclusive OR)
00:00:04.000 hh:mm:ss.fff
Delay after bus voltage recovery
[range 00:00:00.000 … 00:10:55.350]
Time interval between the bus voltage recovery and the first reading of the input
communication objects for evaluating the logic functions
no sending
Output cyclic transmission delay
[other value in range 30 s … 120 min]
No sending means that the output state of the logic function is updated on the bus
only on change. Different values imply cyclic sending on the bus of the output state.
Logic object x disabled / enabled
Negated Logic object x = enabled no / yes

Negando lo stato logico dell’ingresso corrispondente, è possibile realizzare logiche
combinatorie articolate. Esempio: Output=(NOT(Oggetto logico 1) OR Oggetto logico
2).
Read at startup Logic object x = enabled no / yes
Default value Logic object x = enabled none / off / on

Application manual
Object name Conditions Dim. Flags DPT Comm. Obj. No.
Logic function X – Input Logic function X = enabled 189, 194, 199, 204,
1 Bit C-W-- [1.001] switch
1 Logic object 1 = enabled 209, 214, 219, 224
Logic function X – Logic function X = enabled 190, 195, 200, 205,

Input 2 Logic object 2 = enabled 210, 215, 220, 225
Logic function X – Input Logic function X = enabled 191, 196, 201, 206,
3 Logic object 3 = enabled 211, 216, 221, 226
Logic function X – Logic function X = enabled 192, 197, 202, 207,

Input 4 Logic object 4 = enabled 212, 217, 222, 227
Logic function X – 193, 198, 203, 208,

Logic function X = enabled 1 Bit C-W-- [1.001] switch
Output 213, 218, 223, 228

Application manual
8 Appendix
8.1 Summary of KNX communication objects

The following list contains the KNX communication objects for all corresponding Data Point Types (DPT)
defined by the application program according to the performed configurations.
The list is ordered by object number; if the same object is linked to different inputs, the first input or rocker is
referenced.
Object name Size Flags DPT No. Comm. Obj.

Technical alarm 1 Bit C-W-- [1.5] DPT_Alarm 0
Temperature value 2 Byte CR-T- [9.1] DPT_Value_Temp 3
Rocker xx – 4, 21, 38, 55,

1 Bit C-W-- [1.3] DPT_Enable
Lock function 72, 89, 106, 123
5..12,
22.. 29,
39.. 46,
See
56.. 63,
table CR-TU See table A1
73.. 80,
A1
90.. 97,
Rocker x –
Switching status [type], object n* 107.. 114,
124.. 131
* The numbers of listed C.O.s are referred to the first of 8 objects (for each
input); the next C.O.s are sequential. In order to obtain the C.O. number for
the n-th object, simply add (n-1) to the referred numbers.
E.g.: he C.O.s linked to input 3A have numbers starting from 81. The number
of the 5th C.O. linked to that input will be 81+ (5-1) = 85.
Rocker xx –
13, 30, 47, 64,
Switching command 1 Bit CRWTU [1.1] DPT_Switch
81, 98, 115, 132
Rocker xx – 13, 30, 47, 64,

1 Bit CRWTU [1.17] DPT_Trigger
Dedicated stop command 81, 98, 115, 132
Rocker xx – [3.*] DPT_Control_Dimming, 14, 31, 48, 65,

4 Bit CR-T-
Dimming up / down / stop command DPT_Control_Blinds 82, 99, 116, 133
Rocker xx – 16, 33, 50, 67,

1 Bit CR-T- [1.7] DPT_Step
Stop – step up/down command 84, 101, 118, 135
Rocker xx – 17, 34, 51, 68,

1 Bit CRWTU [1.8] DPT_UpDown
Move up / down command 85, 102, 119, 136
Rocker xx – [17.1] DPT_SceneNumber 18, 35, 52, 69,

1 Byte CR-T-
Scene number [18.1] DPT_SceneControl 86, 103, 120, 137
LED X – 140, 142, 144, 146,
1 Bit CRWTU [1.1] DPT_Switch
First colour 148, 150, 152, 154
LED X – 141, 143, 145, 147,

1 Bit CRWTU [1.1] DPT_Switch
Second colour 149, 151, 153, 155
Thermal generator lock 1 Bit -WC--- [1.1] DPT_Switch 160
Temperature control alarm 1 Bit CR-T- [1.5] DPT_Alarm 161
Temperature threshold 1 – Switch 1 Bit CR-T- [1.1] DPT_Switch 162
Temperature threshold 2 – Switch 1 Bit CR-T- [1.1] DPT_Switch 163

Application manual
Object name Size Flags DPT No. Comm. Obj.

Room temperature (from bus) 2 Byte CR-T- [9.1] DPT_Value_Temp 164
Windows contact sensor 1 (from bus) 1 Bit -WC--- [1.19] DPT_Window_Door 165
Windows contact sensor 2 (from bus) 1 Bit -WC--- [1.19] DPT_Window_Door 166
Weighted temperature 2 Byte CR-T- [9.1] DPT_Value_Temp 167
Heating / cooling status out 1 Bit R-CT-- [1.100] DPT_Heat_Cool 168
Heating / cooling status in 1 Bit -WC--- [1.100] DPT_Heat_Cool 169
HVAC mode in 1 Byte -WC--- [20.102] DPT_HVACMode 170
HVAC forced mode in 1 Byte -WC--- [20.102] DPT_HVACMode 171
HVAC manual mode 1 Byte -WC--- [20.102] DPT_HVACMode 172
Chrono active status 1 Bit RWCTU- [1.11] DPT_State 173
HVAC mode out 1 Byte R-CT-- [20.102] DPT_HVACMode 174
Actual setpoint 2 Byte R-CT-- [9.1] DPT_Value_Temp 175
Manual setpoint 2 Byte R-CT-- [9.1] DPT_Value_Temp 176
Manual/forced setpoint active status 1 Bit RWCTU- [1.11] DPT_State 177
Input setpoint 2 Byte -WC--- [9.1] DPT_Value_Temp 178
Heating comfort setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 179
Cooling comfort setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 180
Heating standby offset 2 Byte RWCTU- [9.2] DPT_Value_Tempd 181
Heating standby setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 181
Cooling standby offset 2 Byte RWCTU- [9.2] DPT_Value_Tempd 182
Cooling standby setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 182
Heating economy offset 2 Byte RWCTU- [9.2] DPT_Value_Tempd 183
Heating economy setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 183
Cooling economy offset 2 Byte RWCTU- [9.2] DPT_Value_Tempd 184
Cooling economy setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 184
Heating building protection setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 185
Cooling building protection setpoint 2 Byte RWCTU- [9.1] DPT_Value_Temp 186
Heating out command 1 Byte R-CT-- [5.1] DPT_Scaling 187
Heating out command 1 Bit R-CT-- [1.1] DPT_Switch 187
Both heating and cooling out command 1 Bit R-CT-- [1.1] DPT_Switch 187
Both heating and cooling out command 1 Byte R-CT-- [5.1] DPT_Scaling 187
Cooling out command 1 Byte R-CT-- [5.1] DPT_Scaling 188
Cooling out command 1 Bit R-CT-- [1.1] DPT_Switch 188
189, 194, 199, 204,
Logic function X – Input 1 1 Bit -WCTU- [1.1] DPT_Switch
209, 214, 219, 224
190, 195, 200, 205,
210, 215, 220, 225
191, 196, 201, 206,
211, 216, 221, 226
192, 197, 202, 207,
212, 217, 222, 227
193, 198, 203, 208,
Logic function X – Output 1 Bit R-CT-- [1.1] DPT_Switch
213, 218, 223, 228

Application manual
Table A1. Dimensions e DPT for C.O.s with independent inputs:

Size DPT
1 bit [1.001] switch
2 bit [2.*] 1-bit controlled
[4.*] character
1 byte unsigned value [5.*] 8-bit unsigned value
[20.*] 1-byte
[4.*] character
1 byte percentage [5.*] 8-bit unsigned value
[20.*] 1-byte
1 byte signed value [6.*] 8-bit signed value
2 bytes unsigned value [7.*] 2-byte unsigned value
2 bytes signed value [8.*] 2-byte signed value
2 bytes floating value [9.*] 2-byte float value

Application manual
8.2 Warning
• Installation, electrical connection, configuration and commissioning of the device can only be carried out by
qualified personnel.
• Opening the housing of the device causes the immediate end of the warranty period.
• ekinex® KNX defective devices must be returned to the manufacturer at the following address:
EKINEX S.p.A. Via Novara 37, I-28010 Vaprio d’Agogna (NO) Italy.
8.3 Other information

• This application manual is aimed at installers, system integrators and planners
• For further information on the product, please contact the ekinex® technical support at the e-mail address:
support@ekinex.com or visit the website www.ekinex.com
• KNX® and ETS® are registered trademarks of KNX Association cvba, Brussels
© EKINEX S.p.A. The company reserves the right to make changes to this documentation without notice.


Maed212tp en V2.1.0 Ekinex Spa PDF

Uploaded by

Copyright:

Available Formats

Maed212tp en V2.1.0 Ekinex Spa PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maed212tp en V2.1.0 Ekinex Spa PDF

Uploaded by

Copyright:

Available Formats

Application manual

Wall mounting KNX Pushbuttons

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

7 Application program for ETS .......................................................................................................................38

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Notes for EK-ED2-TP

Revision Modifications Date

Notes for EK-E12-TP

Revision Modifications Date

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

1 Scope of the document

Item File name (## = release) Version Device rel. Update

Item File name (## = release) Version Device rel. Update

2-4 rocker interface EK-ED2-TP: 1-4 rocker interface EK-E12-TP:

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Number and type of

Number and type of

The supply includes, inside the box:

2.1 Completion of the device

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Rocker placement for EK-ED2-TP

Figure 1A - Rocker combination for EK-ED2-TP

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Rocker placement for EK-E12-TP

Figure 2B - Rocker combination for EK-E12-TP

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

2.2 Rocker functions

Note for EK-ED2-TP

2.3 LED indicators

2.4 Customization of rocker plates

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

3 Switching, display and connection elements

Fig. 2A - Switching, display and connection elements for EK-ED2-TP

1. Rocker faceplate hooks

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Fig. 2B- Switching, display and connection elements for EK-E12-TP

1. Rocker faceplate hooks

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

6.1 Offline operation

6.2 Online operation

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

6.3 Software working cycle

6.4 Pushbutton inputs

6.4.1 Pushbutton input events

6.4.2 Lock function

6.4.3 State variables (communication objects)

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

6.4.4 Binding between Events and Communication objects

6.4.5 Repeated send

6.4.6 Input coupling

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

6.4.7 Single or independent input mode

4. Scene function output

6.4.8 Coupled input mode

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

Revision 2.1.0 - Updated: 09/03/2020 MAEKED212TP_EN

6.4.9 Dimming function

i other cases. In order to obtain a complete or generally applicable documentation, please