Zennio Touch-MyDesign Display One User manual

KNX Capacitive Touch Switch
with 4/6/8 buttons
ZN1VI-TPTMD4
ZN1VI-TPTMD6
USER MANUAL
ZN1VI-TPTMD8
Application Program Version: [1.0]
User Manual Version: [1.0]_a
www.zennio.com

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
2
Contents
1 Introduction ............................................................................................................................. 3
1.1 Touch-MyDesign............................................................................................................... 3
1.2 Installation........................................................................................................................ 4
2 Configuration ........................................................................................................................... 7
2.1 General Configuration ...................................................................................................... 7
2.2 Touch Panel ...................................................................................................................... 7
3 ETS Parameterization............................................................................................................. 10
3.1 Default Parameterization ............................................................................................... 10
3.2 General ........................................................................................................................... 11
3.3 Main Buttons.................................................................................................................. 18
3.3.1 Pair.......................................................................................................................... 20
3.3.2 Individual ................................................................................................................ 23
3.4 Additional Buttons.......................................................................................................... 27
3.4.1 Disabled .................................................................................................................. 28
3.4.2 Setpoint Temperature ............................................................................................ 29
3.4.3 1-byte Control (unsigned int) ................................................................................. 29
3.4.4 1-byte Control (scaling) .......................................................................................... 30
3.4.5 Individual Buttons................................................................................................... 30
3.4.6 Individual Indicators ............................................................................................... 31
3.5 Inputs.............................................................................................................................. 32
3.5.1 Push Button ............................................................................................................ 33
3.5.2 Switch/Sensor......................................................................................................... 37
3.5.3 Temperature Probe ................................................................................................ 38
3.5.4 Movement Detector ............................................................................................... 40
3.6 Thermostat ..................................................................................................................... 41
ANNEX I: Communication objects ............................................................................................... 42

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
3
1INTRODUCTION
1.1 TOUCH-MYDESIGN
Touch-MyDesign, the KNX capacitive touch switch from Zennio, is a multifunction
and fully customizable solution for room control, including hotel rooms, offices or any
other environment where user control is required for climate systems, lighting, blinds,
scenes, etc. The versatility of all these functions is enhanced by the built-in
analogue/digital inputs, temperature sensor and thermostat function, and by an elegant
and fully customizable design of the front glass: consumers can choose the button
icons, the texts, the colours and even personalize the background with their pictures,
logos, etc.
Figure 1 Touch-MyDesign (6-button model)
The most outstanding features of Touch-MyDesign are shown next.
Fully customizable design of the front glass.
4 / 6 / 8 main touch buttons (configurable individually or in pairs).
5 additional touch buttons (configurable individually or jointly).
Horizontal or vertical orientation.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
4
Light indicator (LED) for every button or control, with the possibility of
making the light status depend on the control status.
Buzzer for an audible acknowledgement of user actions, with the possibility of
disabling it either by parameter or by object.
Possibility of locking / unlocking the touch panel through binary orders or
scenes, and of setting a timed/automatic locking of the device.
Welcome Back object (binary or scene), which will be sent to the bus on the
first press of the touch panel after a long standby period.
Two analogue/digital inputs (for movement sensors, temperature probes,
additional switches, etc.).
Thermostat function.
Built-in temperature sensor.
1.2 INSTALLATION
Figure 2 Touch-MyDesign. Installation process.
To install the device, it is first necessary to mount the metallic plate into a
square/round standard appliance box through the corresponding screws. Next, Touch-
MyDesign is connected to the KNX bus through the corresponding terminal on the rear
side of the device, and then the input terminal is as well connected to the rear of the
device.
1
2
3
4

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
5
Once the input terminal and the KNX terminal are connected, the device can be easily
mounted on the metallic plate by the action of the built-in magnets. After that, it is
necessary to slide Touch-MyDesign downwards to fix it through the security anchorage
system.
Finally, it is advisable to check that the device is properly installed, and that only the
profile of the device becomes visible from above, from below and from both sides (the
metallic plate should be completely hidden).
This device does not need any external power supply since it is powered through the
KNX bus.
Figure 3 Touch-MyDesign. Element diagram.
The programming button (5) shown in Figure 3may be pressed with the help of a thin
screw to set Touch-MyDesign in programming mode. After a short press, the
programming LED will light in red. Note that if this button is held while plugging the
device into the KNX bus, the device will enter the secure mode. The LED will then
blink in red.
Note: whenever the device recovers the bus power, an immediate self-calibration
process of the touch panel takes place. Please ensure to avoid making pressure over
the front glass while powering the device. If undesired effects arise during use, please
1
2
3
4
5
6
1. Magnet.
2. Internal temperature probe.
3. KNX clamp.
4. Analogue/digital input clamp.
5. Programming button.
6. Programming LED.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
6
disconnect the device from the bus and connect it again, making sure that the front
glass is not touched during this process.
For detailed information about the technical features of Touch-MyDesign, as well as
information on security and on the installation process, please refer to the Datasheet
included within the original packaging of the device and also available at
http://www.zennio.com.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
7
2CONFIGURATION
2.1 GENERAL CONFIGURATION
Zennio Touch-MyDesign lets the user control and monitor a set of functionalities
within a domotic environment, in an easy and intuitive manner. The inexistence of a
screen, menus or complex user interaction beyond button presses confers the device a
notable ease of use.
To make the device perform the desired functions, several options need to be
parameterized, both in relation to the general behaving (horizontal/vertical orientation,
locking procedure of the touch panel, buzzing for action confirmation, welcome back
object…) and button-specific (function to be performed, behaviour of its
corresponding LED, etc.).
On the other hand, Touch-MyDesign features 2 opto-coupled inputs, each of which
may be independently configured as a switch/sensor, a push-button, a movement
detector, or a temperature probe. And depending on the selection, a series of
external elements may be connected to the input terminal of Touch-MyDesign. In the
particular case of an external temperature probe (such as model ZN1AC-NTC68 from
Zennio), it will be possible to use it independently of the temperature sensor built-in in
the device, which implements its own communication objects and may or may not be
enabled by parameter.
2.2 TOUCH PANEL
Touch-MyDesign features 4, 6 or 8 ‘main’ capacitive buttons (depending on the
model) at the user’s disposal for the execution of actions. 5 more ‘additional’ buttons
can be found at the bottom of the front touch panel (or at the right side of the front
touch panel, in case of mounting the device horizontally). All of them will perform
specific and permanent functionalities at any time, since functions are not grouped into
alternating menus, pages...

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
8
Figure 4 Touch panel (6-button model)
As Figure 4shows, two areas can be distinguished in the touch panel:
The main buttons, grouped in pairs, all over most of the touch panel surface.
The additional buttons, as an aligned panel, separate from the main buttons.
All the main buttons are identical, and also every additional button is identical to the
others, which makes it possible to configure all of them for user-defined applications.
Each of the mentioned buttons incorporates a central LED which, by default, will turn
on for a brief instant whenever the button is touched, although alternative LED
behaviours may be configured for every button, depending on the parameterized
function:
Regular lighting: the LED will light for only an instant after the button is
touched. LEDs behave this way by default.
State-dependent lighting: the LED will or will not light depending on the
value of the communication object that corresponds to the function
implemented by the button. The exact relation between the different values of
Pair A
Pair B
Pair C
1
2
Main
Buttons
Additional
Buttons

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
9
the object and the different states of the LED may be slightly different from
one type of control to another, so it will be explained in later sections.
State-dependent lighting (both LEDs): only applies to main buttons that are
configured as pair-button controls. The two LEDs of the pair-button control will
light or not depending on the value of the related object and on the particular
control type parameterized for that pair of buttons. The only difference
compared to the previous case is that, under the “both LEDs” case, the two
LEDs will always turn off or on simultaneously, as if it were a unique state
indicator consisting of two LEDs.
Apart from the behaviour of the LEDs, beeping can be activated or deactivated as an
acoustic feedback for the user when an action is performed after a button touch.
Enabling and disabling the buzzer can be done by parameter or by object, being also
possible to define by parameter whether this function should be initially enabled or not.
Finally, a specific object has also been included for externally triggering a brief beep at
any time, provided that the beeping function has not been disabled.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
10
3ETS PARAMETERIZATION
To begin with the parameterization process of the device, it is necessary, once
the ETS program has been opened, to import the database of the product (Touch-
MyDesign application program).
Next, the device should be added to the project where desired. And then, one right-
click on the device will permit selecting "Edit parameters", in order to start the
configuration.
In the following sections a detailed explanation can be found about each of the different
functionalities of Touch-MyDesign in ETS.
3.1 DEFAULT PARAMETERIZATION
This section shows the default configuration from which the device
parameterization starts.
Figure 5shows the communication objects displayed by default: “[General] Scene:
receive” (intended for the reception of scene values from the bus), “[General] Scene:
send” (destined to send scene values to the bus), “[General] Buzzer enabling” (for
enabling or disabling the beeping functionality, which may also be set by parameter,
although disabling it by parameter will have a permanent effect and will hide this object)
and “[General] Buzzer” (which makes it possible to externally triggering a brief beep at
any time –beyond the usual behaviour of these beeps as action confirmations–
whenever the state of the “[General] Buzzer enabling” object permits it).
Figure 5 Default topology
When entering the parameter edition of Touch-MyDesign for the first time, a window
similar to Figure 6will be shown, where three main sections are available: General,
Main buttons and Additional buttons, which are described next.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
11
3.2 GENERAL
The windows under the “General” tab permits configuring the basics of the device.
The only of them that is active by default is “Configuration”.
Figure 6 Configuration (General)
Touch-MyDesign orientation. Defines the orientation (horizontal / vertical)
of the device, with the aim of implementing a logical behaviour in the buttons.
Figure 7 Orientation of the device
Next to “Touch-MyDesign Orientation”, a second parameter is shown, “Pair
button behaviour”. The selectable values for this parameter will depend on the
selection made for the former parameter. Table 1shows the possible behaviours
of the pair buttons. The option selected here will affect every button configured as
a pair control. Note that if the device is mounted with a layout inverted to what is

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
12
shown by Figure 7(i.e., with the additional buttons on the left or on the top), the
meaning of the words “left” and “right” should be assumed inverted as well.
Note: this parameterization does not alter the names of the touch buttons or of
their objects. It does not affect the behaviour of the non-pair buttons (such as the
additional buttons) either.
Orientation Pair Button behaviour
Vertical
Left: off / decrease
Right: on / increase
Left: on / increase
Right: off / decrease
Horizontal
Down: off / decrease
Up: on / increase
Down: on / increase
Up: off / decrease
Table 1 Orientation vs. pair button behaviour
LED lighting. In addition to the specific behaviour of every LED regarding its
own button (see section 2.2), it is possible to define certain general attributes that
will affect all the LEDs. For that purpose, this parameter provides two options:
Default: the LEDs will assume the default light levels for the “on” and “off”
states (maximum level and minimum level, respectively).
Custom: permits the definition of custom light levels for the “on” and “off”
states of the LEDs, as well as enabling complementary functionalities, like
the night mode or the LED flashing object. For that purpose, after selecting
this option a new screen will come up (LED lighting; see Figure 8), where the
following parameters can be found:
Normal mode: this section is provided for defining the desired lighting
level (“max” or “min”) for the “on” state of the LEDs under normal
condition, and, analogously, the desired level (“off”, “min” or “max”) for
the “off” state of the LEDs, under normal condition. The default values
are respectively “max” and “off”.
In addition to this normal mode it is also possible to implement a night
mode with its own light parameterization (equal or different to that of

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
13
the normal mode), so that the device can switch from one mode to
another upon a certain event (if the “night mode” functionality has been
enabled, the “Activation” parameter will be displayed, among the
aforementioned parameters of the “normal mode”, as described
below). Note, however, that an equal parameterization for both modes
does not mean an equal effective light level; e.g., “on=max” will imply a
higher luminosity for normal mode than for night mode. Night mode
implements by itself an additional attenuation of the light levels.
Figure 8 Lighting with the night mode and the flash object enabled
Night mode: permits enabling (“Yes”) or disabling (“No”) the
functionality of the “night mode”, i.e., a light level configuration
complementary to the one of the “normal mode”. The “night mode”
functionality is disabled by default. When enabled, two binary objects
are shown: “[General] LEDs: night mode” and “[General] LEDs: normal
mode”, as well as the following parameters:
•“ON level”: defines, for the night mode, the luminosity level
(“max” or “min”) that will be assumed for the “on” state of the
LEDs.
•“OFF level”: defines, for the night mode, the luminosity level
(“off”, “min” or “max”) that will be assumed for the “off” status of
the LEDs.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
14
•“Activation”: this parameter (as well as the analogous
parameter for the normal mode that comes up after enabling the
night mode function) permits selecting the desired procedure for
switching between the normal and the night modes and vice
versa, which can consist in the reception of a certain binary value
(“0” or “1”, configurable) through the object “[General] LEDs:
night mode” (or “[General] LEDs: normal mode”, for normal
mode), or in the reception of a certain scene (1 to 64,
configurable) through the “[General] Scene: receive”. Note that,
being these modes mutually exclusive, the device will leave one
mode as soon as it receives the order to enter the other mode.
Note, as already stated, that night mode implements by itself a general
attenuation of the light levels. For example, the “max” light level in the
normal mode will be brighter than the “max” light level in the night
mode. Even the “min” light level in the normal mode will be.
Note: due to hardware reconfiguration, switching from one mode to the
other causes that for 2-3 seconds the touch buttons do not react to
presses. The application program and the bus order reception are,
however, not affected.
“LEDs flash object”: permits, by selecting “Yes”, making use of a
binary object (“[General] Flash LEDs”) so that when the value “1” is
received, every LED in the device will turn into the “on” state and
maintain it during a certain time (configurable through the “Flash Time”
parameter, which accepts input values between 1 and 20 seconds;
note that the flash time counter will be reset if the value “1” is received
again during the flash time), after which it will recover the
corresponding state. This function is not enabled by default.
Note: during the flash time, the LEDs will remain on, ignoring their
usual behaviour. However, the device will still react to presses and bus
orders, so when the flash time ends the LEDs will acquire their
corresponding states.
Note: the flash function is interrupted on bus failures.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
15
Touch locking. This function permits locking (i.e., making them useless) or
unlocking the touch buttons of the touch panel, with the possibility of setting the
following fields (from the “Touch locking” screen, which will become visible after
enabling this function; see Figure 9):
Locking method: defines the desired procedure for entering into the
“locked” state. This can consist in a 1-bit object (“[General] Touch Lock”,
which will lock the touch buttons when it receives the values “1” or “0”,
according to the parameterization), the reception of a scene (values 1 to 64,
configurable) through “[General] Scenes: receive”; or an Auto (timed)
triggering which will require setting (through the “Time to lock” parameter, in
seconds) how much time the device must stay idle since the last button
touch before entering into the “locked” state.
Unlocking method: defines the procedure for leaving the “locked” state of
the touch panel. This can consist in a 1-bit object (“[General] Touch Unlock”,
which will proceed with the unlock on the arrival of the values “1” or “0”,
according to parameterization) or in the reception of a scene (values 1 to 64,
configurable) through “[General] Scenes: receive”.
Figure 9 Touch locking (General)
Welcome Back object. This function permits sending a certain value (binary
or scene) to the KNX bus when the user performs a touch on any of the touch
buttons after a standby period. This makes possible, for example, lighting up a
room after several hours of darkness with only a random touch over the touch
panel. If enabled, this function will make the “[General] Welcome Back object”
object visible, as well as a new window (see Figure 10) from where it is possible to
parameterize its behaviour.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
16
Figure 10 Welcome Back object (General)
Downtime to enable: defines the minimum time that must pass since the
last touch before the device assumes that the next touch will be associated
to the sending of the welcome back object. The allowed values are [5 –
65535] seconds.
Object type: this parameter selects the type of sending that is desired to be
performed. By default, it will be a 1-bit value (“0” or “1”, configurable), but it is
also possible to select “Scene” (1 – 64, configurable). In the case of selecting
the latter, the “[General] Welcome back object” object will become hidden,
since the sending will be performed through the “[General] Scene: send”
object.
Sending delay: time (between 0 and 255 seconds) that Touch-MyDesign will
wait since the touch takes place and the welcome back object is effectively
sent.
Note:if combining the welcome back function with the automatic (timed) touch
lock function, it is important to take into account that the delay of the sending of
the welcome back object should not exceed the timed self-lock. For instance, if
an automatic lock after 60 seconds has been parameterized, the welcome back
object will actually not be sent if the sending delay exceeds those 60 seconds
(the device will lock before the sending is performed). This is particularly
important if linking the welcome back object to the unlocking object.
Buzzer: permits enabling or disabling the audible beeps that the device can
generate. Disabling them by parameter entirely prevents their use, while enabling
them, apart from activating an audible acknowledgment for the actions triggered
by button touches (see section 2.2), will also bring up the objects “[General]
Buzzer” (which permits externally triggering the generation of a short beep at any
time by sending the value “1”) and “[General] Buzzer enabling” (which permits

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
17
enabling and disabling, by object, any audible indication generated by the buzzer,
including those due to the sending of a “1” through “[General] Buzzer”). By
default, beeping is enabled both by parameter and by object. However, even
being enabled by parameter, it is also possible to define (through the “Initial
status (after programming)” parameter) the desired initial state of the “[General]
Buzzer enabling” object. Note, however, that if the buzzer is disabled by
parameter, the two objects related to this function will disappear, which will make
it impossible to enable it afterwards.
Internal temperature sensor: enabling (“Yes”) this parameter will bring up a
new object (“[Internal sensor] Current temperature”), as well as a new
parameterizable window (see Figure 11), from where it is possible to define the
following:
Figure 11 Internal temperature sensor (General)
Temperature sensor calibration: this option permits implementing a
correction (by adding or subtracting some tenths of a degree) to the
measured temperature in case of a deviation between it and the real
temperature in the room. The allowed values are [-50, 50], i.e., from -5 to 5
ºC.
Temperature sending period: permits performing a cyclical sending of the
temperature value to the KNX bus through the corresponding object. This
parameter is intended to define the desired cycle time, between 1 and 100
tens of a second. The value “0” will turn off the cyclical sending.
Example:to have the temperature of the internal sensor sent every 30
seconds, this parameter should be set to “3”.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
18
Send with a temperature change: permits performing an automatic sending
of the temperature value whenever it suffers a change (an increase or a
decrease) greater than a certain amount of degrees, which should be defined
through this parameter (in tenths of a degree). The allowed values are “0”
(disabled) to “200” (20ºC). Note that this function is independent from the
cyclical sending already described.
Example: to have the temperature sent to the bus whenever a change
of 5ºC or more is detected between two consecutive measurements,
the value “50” is used.
Temperature protection: the internal temperature sensor implements a
protection function against overheating, overcooling or overheating and
overcooling which may be enabled through this parameter. Depending on the
selected type of protection, one or two binary objects will become visible:
“[Internal sensor] Overheating” and “[Internal sensor] Overcooling”, which will
send the value “1” as soon as the temperature reaches the limit
corresponding to each case, and the “0” as soon as such situation ends. It is
therefore necessary to define the limit temperature (in Celsius degrees) for
overheating, for overcooling, or for both. Moreover, it is possible to define a
hysteresis (from 1 to 80 tenths of a degree) to avoid a consecutive re-
sending when the temperature fluctuates around the defined limit.
Inputs: permits enabling and configuring each of the two inputs available in
the device (see section 2.1), individually. For that purpose, after selecting the
value “Enabled”, ETS will bring up a new tab with the name “Inputs”, which will be
explained in detail in section 3.5.
Thermostat: permits enabling and configuring the thermostat function. For
that purpose, after selecting the value “Enabled”, ETS will bring up a new tab with
the name “Thermostat”, which will be described in detail in section 3.6.
3.3 MAIN BUTTONS
This tab, which permits defining the specific functions that will be performed by the
main buttons of the device (see section 2.2), is itself divided into a series of windows,
among which the only one visible by default is Configuration.

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
19
Figure 12 Configuration (Main buttons)
From the Configuration window it is possible to assign to every pair of buttons (named
A, B and C, in the case of Touch-MyDesign 6) a behaviour as such (option “Pair”,
which will bring up a new parameterizable window with the name “Pair X”, where X will
be “A”, “B” or “C”), or a mutually independent behaviour of its two buttons (option
“Individual”, which will bring up two new parameterizable windows with the names
“Button X1” and “Button X2”, where X will be “A”, “B” or “C”). It is also possible to
entirely disable each pair of buttons (and its LEDs) through the option “Disabled”.
In short, the following functions are available for the main buttons, depending on the
behaviour (“Disabled”, “Pair” or “Individual”) parameterized for each pair of buttons:
Disabled (non functional buttons; inactive LEDs).
Pairs:
Switch.
Dimmer.
Shutter.
Individual:
Disabled.
1 bit.
1 bit (hold & release).
Scene.
1-byte constant (unsigned int).
1-byte constant (scaling).
2-byte constant (unsigned int).
2-byte constant (float).
Dimmer.
Shutter.
The options under “Pair” and “Individual” are explained in detail in sections 3.3.1 and
3.3.2.
Note: disabling a pair of buttons from the “Configuration” window implies that none of
the buttons and the LEDs in the pair will be functional. Alternatively, it is possible to
select the option “Individual” for the pair of buttons and, afterwards, actually setting or
not a functionality to each of them (and/or to its respective LED) from the “Button”
window (see section 3.3.2).

Touch-MyDesign
http://www.zennio.com Technical Support:http://zennioenglish.zendesk.com
20
3.3.1 PAIR
In the case of selecting the option “Pair” in any of the drop-down lists from the
“Configuration” page of the “Main buttons” tab, a new page (“Pair A”, “Pair B”, “Pair C”,
as corresponding) from where it will be possible to set the desired functionality of the
buttons and LEDs that constitute the corresponding pair.
Note:figures in this section may refer to the case of “Pair A”. Any other cases should
be analogous.
Figure 13 Pair A (Main buttons)
The parameters that are shown here by default are Function (with the options “Switch”,
“Dimmer” and “Shutter”) and LED Lighting, being the latter conditioned by the option
that has been selected for the former, as described next:
Switch: selecting this option brings up the (“[X] Binary control”) object,
through which the values “0” or “1” will be sent to the KNX bus depending on user
touches over the buttons of the pair. The particular correspondence between
each button in the pair and the value sent is subject to the general parameters
“Touch-MyDesign orientation” and “Pair button behaviour” (see section 3.2).
When the “Switch” option has been selected, the parameter LED lighting
permits, for its part, three alternatives:
Regular: the LED of each button in the pair will behave in the usual way:
when a touch on its button is detected, it will light (according to the custom
“ON” level, in parameterized) for an instant and it will then turn off again
(according to the custom “OFF” level, if parameterized).
State-dependent: the light state of the LEDs in the pair will depend on the
current value of the “[X] Binary control” object, so there will always be one
of the LEDs in the “ON” status (but never both at the same time). This
way, the LEDs will behave as a state indicator (one of the LEDs will light