Zennio Linecoupler ZN1SY-LCTP User manual

Linecoupler
KNX-TP Line Coupler & Repeater
ZN1SY-LCTP
USER MANUAL
Application Program version: [1.1]
User Manual version: [1.1]_a
www.zennio.com

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
2
Contents
Document Updates............................................................................................................3
1 Introduction ..............................................................................................................4
1.1 Zennio Linecoupler.............................................................................................4
1.2 Installation.........................................................................................................6
2 Configuration.............................................................................................................7
2.1 General Configuration........................................................................................7
2.1.1 Zennio Linecoupler as a Line Coupler..............................................................7
2.1.2 Zennio Linecoupler as a Repeater.................................................................11
2.2 Manual Function Button ..................................................................................12
2.2.1 Hard Reset to Factory Defaults.....................................................................12
3 ETS Parameterisation (Linecoupler) .........................................................................13
3.1 Default Parameterisation .................................................................................13
3.2 General............................................................................................................14
3.3 Main Line.........................................................................................................14
3.4 Sub-Line...........................................................................................................17
4 ETS Parameterisation (Linerepeater)........................................................................18
4.1 Default Parameterisation .................................................................................18
4.2 General............................................................................................................19
4.3 Main Line.........................................................................................................19
4.4 Sub-Line...........................................................................................................21

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
3
DOCUMENT UPDATES
Version Modifications Page(s)
[1.1]_a
Changes in the application program:
•Downloads are now forced to be complete, to ensure
the filter table is always transferred to the device.
-
Minor details about the group address filtering. 8

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
4
1INTRODUCTION
1.1 ZENNIO LINECOUPLER
Figure 1 Zennio Linecoupler
Zennio Linecoupler is the KNX line-coupling and line-repeating solution from Zennio.
This device is intended to couple two KNX twisted-pair lines together. Its flexibility
makes it possible to connect a KNX sub-line to a KNX mainline or a KNX mainline to a
KNX backbone line (line coupler mode), or to simply link together two sub-line
segments (line repeater mode).
Figure 2 Context (Topology)

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
5
These are the most outstanding features of the device:
Low Power Consumption.
Galvanic Insulation of the connected lines.
Traffic Filtering according to the project topology and to the built-in address
table.
Telegram Dropping.
Blockage of Device-Configuration Telegrams (telegrams destined to
physical addresses).
Support for Long Messages (up to 250 bytes).
Customizable Pushbutton for triggering the manual mode, useful at runtime
and for set-up and troubleshooting purposes.
6 Lighting Indicators (LEDs) for accurately showing the bus status of each
line, making the detection of abnormal situations (excessive bus load,
message retransmissions, etc.) easier.
Two alternative application programs permit configuring the device as a Line
Coupler or as a Repeater.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
6
1.2 INSTALLATION
Figure 3 Element Diagram
As shown in Figure 3 each of the two KNX lines to be coupled must be connected to
one of the two KNX bus connectors available (6, 11). After the connection, the line
coupler can be conveniently mounted on the DIN rail by the usual procedure.
This device does not need any external power supply since it is entirely powered
through the main KNX bus (6).
Note: each line (or line segment) being coupled requires a dedicated power supply. No
power pass from one line to another is performed.
The programming button (10) shown in Figure 3 may be pressed to set Linecoupler in
programming mode. After a short press, the programming LED will light in red.
The behaviour of the additional LEDs and the manual function button will be described
in section 2.2.
For detailed information about the technical features of Linecoupler, 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.
6
11
10
5
9
8
7
4
3
2
1
1. Main line status LED.
2. Main line traffic LED.
3. Group address filter table status.
4. Manual function button.
5. Programming LED.
6. Main line KNX connector.
7. Secondary line status LED.
8. Secondary line traffic LED.
9. Physical address filter table status.
10. Programming button.
11. Secondary line KNX connector.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
7
2CONFIGURATION
2.1 GENERAL CONFIGURATION
Zennio Linecoupler can be used as a line coupler (for coupling both a sub-line to a
mainline, or a mainline to a backbone line; the latter is normally referred to as
“backbone coupler”) or as a repeater (for coupling two sub-line segments). A different
application program is provided for each purpose.
2.1.1 ZENNIO LINECOUPLER AS A LINE COUPLER
Figure 2 shows a typical scenario where Linecoupler can be installed. As a line
coupler, the device may perform line coupling in the nodes marked as “LC”, where a
sub-line connects to a mainline or a mainline connects to a backbone line. In both
cases, Linecoupler offers an insulated coupling interface with the possibility of filtering
the traffic according to the topology in the installation or to group-oriented criteria. In
other words, Linecoupler will (or will not) let telegrams pass from one line to the other
according to the parameterisation.
Another scenario is shown in Figure 4.
Figure 4 Line Coupling Scenario
3.0.0
4.0.0
3.1.0
4.1.0
4.2.0
3.2.0
4.2.1
3.2.1
4.1.1
4.1.2
3.1.1
3.1.2
4.0.1
3.0.1

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
8
Note: the individual address of a line coupler needs to be of the form X.Y.0 (or X.0.0 in
the case of working as a backbone coupler).
Regarding telegram filtering, the line coupler implements two complementary (and
optional) filters:
Group address filtering: ETS automatically generates a group address table
for the project loaded. This table is transferred to the line coupler during
complete downloads. When a telegram containing a group address in the
“destination address” field arrives, the line coupler will look up if such address
exists in the group table, and eventually transmit the telegram to the other
side –if the address is found–or drop (block) it –if it is not–.
Note: making further changes to a project (addresses, etc.) requires
downloading the updated filter table to the line coupler.
Example:if the line coupler has been parameterised to filter group
addresses from both lines, when it receives a telegram from the
mainline destined to a group address (e.g., 2/5/13) it will check that
there is a device in the sub-line with objects that have been assigned
such group address (or that such address has at least been marked in
ETS to pass through the line coupler; see Figure 5). If so, then the line
coupler will let it pass. Otherwise, it won’t be transferred to the sub-line.
The same would also apply to the inverse case (a telegram originating
in the sub-line).
Figure 5 ETS Option to Force Passing a Group Address through the Line Coupler

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
9
Physical address filtering: when the line coupler receives a telegram where
the destination address is a physical/individual address (for example, during
downloads), it will compare such address with its own physical address (no
particular filter table is required for physical address filtering, but a simple
comparison). The physical address of the line coupler determines the line it
belongs to, which then, and according to the parameterisation, determines if
the telegram will be routed or eventually dropped (blocked). This can be
parameterised separately for the mainline and for the sub-line.
Example: in the example shown in Figure 4, if the line coupler with
address 3.2.0 reads a telegram on the mainline destined to the device
with physical address 3.1.2, it will compare both addresses and
conclude that 3.1.2 is not an address belonging to its line and will
therefore not transmit it to its secondary line.
Note: the device that sends a telegram needs to have been assigned a
physical address that really corresponds to its line. In Figure 4, if the device
with address 3.1.1 (let it be a KNX programmer, for instance) changes its
address to 7.7.255, it will not be able to send telegrams to, for example, the
device with address 4.0.1.
For their part, the LED lights on the top of the device make it easy to monitor the status
of the buses and to detect typical communication problems, as detailed next.
Figure 6 LEDs

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
10
Mainline Status LED: shows the status of the primary bus.
oOFF = error: mainline not connected or not powered
oON (green) = OK.
oON (orange) = manual function in execution.
Sub-line Bus Status LED: shows the status of the secondary bus.
oOFF = error or secondary line not connected.
oON (green) = OK
Mainline Traffic LED: shows the traffic status in the primary bus.
oBLINKING (green) = traffic.
oOFF = no traffic.
oBLINKING (red) = errors in the transmissions.
Sub-line Traffic LED: shows the traffic status in the secondary bus.
oBLINKING (green) = traffic.
oOFF = no traffic.
oBLINKING (red) = errors in the transmissions.
Group Address (GA) Filter Status LED: shows the current configuration of
the group address routing:
oOFF = different routing for the main and the secondary lines.
oON (green) = filtering active.
oON (orange) = all group addresses routed.
oON (red) = routing blocked.
Physical Address (PA) Filter Status LED: shows the current configuration
of the individual address routing:
oOFF = different routing for the main and the secondary lines.
oON (green) = filtering active.
oON (yellow-orange) = all individual addresses routed.
oON (dark orange) = routing blocked.
Note: please be careful not to confuse yellow-orange and dark orange.
Please refer to section 3 for a detailed explanation of the different behaviours and
parameterisations of the line coupler application program.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
11
2.1.2 ZENNIO LINECOUPLER AS A REPEATER
Figure 2 also includes a particular case where a repeater (marked as “LR”) is required:
two separate sub-line segments (one of which with no other connection to the
installation, in order to prevent forbidden situations such as in Figure 7), both
containing devices, need to be linked for extending the sub-line. Linecoupler offers
such linking interface, with proper electrical insulation for the connections.
Figure 7 Forbidden Situation: Segment with Two Connections to the Bus
Line repeaters do not implement filter tables. As the name suggests, any telegram
on one of the buses will be repeated to the other bus. It is therefore irrelevant whether
the telegram originates on one side or another and whether it is destined to one side or
another: both segments melt together. Therefore, the Linerepeater application program
will only let transmitting or dropping every telegram destined to physical addresses,
while no drop or filter options are provided for those destined to group addresses.
Note: while the individual address of a line coupler does, the individual address of a
repeater does not have particular restrictions, apart from belonging to the address
range of the corresponding sub-line.
In the case of the line repeater application program, the LED lights on the top of the
device follow the pattern already described for the line coupler application program
(see section 2.1.1), although the GA status LED will always show in orange (no option
for group address blocking or filtering is available in the line repeater), while the PA
status LED will never turn green (no option for individual address filtering is available in
the line repeater).
3.0.0
3.3.0
3.3.42
3.3.43
3.3.44
3.3.45
3.3.46
3.3.47
3.3.49
3.3.48
3.3.41

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
12
Please refer to section 4 for a detailed explanation of the different behaviours and
parameterisations of the line repeater application program.
2.2 MANUAL FUNCTION BUTTON
Zennio Linecoupler features an additional pushbutton on the top cover, next to the
status LEDs (see (4) in Figure 3). A 3-second press on this button will set the device in
manual mode, thus activating a customizable manual function, and will turn the main
bus status LED orange or red (depending on the previous status of the LED: green or
off). Depending on the parameterised manual function, other LEDs may also change
their colours.
If the manual function button is pressed again for 3 seconds (or if the parameterised
fallback timer expires), the device will leave the manual mode and recover the normal
mode. Note that switching from the normal mode to the manual mode and then back to
the normal mode does not cause a loss of the previously downloaded parameters.
For both the line repeater and the line coupler application programs, the selectable
manual functions are: disabled, pass all telegrams, pass physical telegrams and pass
group telegrams. Please refer to sections 3.2 and 4.2 for the parameterisation in ETS
of the manual function and for a detailed description of the different options.
2.2.1 HARD RESET TO FACTORY DEFAULTS
The manual function button permits performing a hard reset of the device, which will
set it back to the factory default state, including the initial individual address.
These are the steps:
Press the manual function button for at least 15 seconds. After that, all the
LEDs will light in red.
Release the manual function button and press it again for some more
seconds. The device will be then automatically reset.
Note: keep in mind that, before entering the reset mode (~15s press), the device will
first enter the manual function mode, which will also make some LEDs change.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
13
3ETS PARAMETERISATION (LINECOUPLER)
To begin with the parameterisation process of the device, it is necessary, once the ETS
program has been opened, to import the database of the product (Linecoupler
application program).
Figure 8 Properties of the Linecoupler Application Program
Next, the device should be added to the project where desired. And then, one click on
the device with the secondary mouse button will permit selecting "Edit parameters", in
order to start the configuration.
The following sections provide a detailed explanation about each of the different
parameters of the device.
3.1 DEFAULT PARAMETERISATION
When entering the parameter edition of Linecoupler for the first time, a window similar
to Figure 9 will be shown, where three main tabs are available: General, Main line and
Sub-line. Note that this application program does not implement communication
objects.
Figure 9 General

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
14
3.2 GENERAL
As shown in Figure 9, this screen contains two parameters, both related to the manual
mode of the device (see section 2.2):
Fallback Time for Manual Operation: sets the maximum operation time for
the manual mode. Once exceeded, the device will automatically leave manual
mode and return to normal mode. The available values are: 10 minutes, 1
hour (default), 4 hours and 8 hours.
Manual Function: sets the desired function to be executed by the device
while in the manual mode. The available values are: disabled (no action),
pass all telegrams (default option; the device will not filter/drop any telegram
transferred from one line the other), pass physical telegrams (the device will
not filter/drop physical addresses; in other words, all telegrams destined to
physical addresses will be transmitted while in manual mode; on the other
hand, group telegram filtering will stay the same as in normal mode) and pass
group telegrams (the device will not filter/drop group addresses; in other
words, the group address filter table will stay disabled while in manual mode;
on the other hand, physical address filtering will stay the same in normal
mode).
3.3 MAIN LINE
This screen permits parameterising the behaviour of the line coupler regarding the
mainline, that is, when the telegrams are being transferred towards the mainline.
Figure 10 Mainline

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
15
The available parameters are described next:
Configuration: permits selecting a general preset for the mainline, or
enabling the manual configuration of each parameter (option “Configure”).
The available presets are: “Groups: filter; Physical: block” (enables the group
address filtering and drops all telegrams destined to physical addresses),
“Groups, Physical: filter” (default option; enables both the group address and
the physical address filtering), “Groups: route; Physical: filter” (performs no
blocking or filtering over the group address but does filter telegrams destined
to physical addresses) and “Groups, Physical: route” (performs no telegram
filtering or dropping at all).
Note: transmitting all the telegrams (no telegram filtering or dropping) is only
intended for testing purposes and may cause risks or conflicts in the KNX
installation if permitted permanently.
(The following parameters will be locked unless “Configure” has been
selected under “Configuration”).
Group Telegrams: sets the behaviour of the device regarding telegrams
destined to group addresses. The available options are “Transmit all” (no
telegram filtering or dropping), “Block” (all telegrams will be dropped) and
“Filter” (default option; telegrams will be filtered, dropping only the
corresponding ones, according to the filter table; see section 2.1.1).
Note: transmitting all the telegrams (no telegram filtering or dropping) is only
intended for testing purposes and may cause risks or conflicts in the KNX
installation if permitted permanently.
Main Group Telegrams 14/15:sets whether telegrams destined to a group
address in groups 14 and 15 (e.g., 14/1/1) will be dropped or transmitted. The
options are “Transmit all” (default option) and “Block”. Note that group
addresses 14.X.Y and 15.X.Y are not included in the filter table by ETS.
Physical Telegrams: sets the behaviour of the device regarding telegrams
destined to individual addresses. The available options are “Transmit all” (no
telegram filtering or dropping), “Block” (all telegrams will be dropped) and

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
16
“Filter” (default option; telegrams will be filtered, dropping the corresponding
ones; see section 2.1.1).
Note: transmitting all the telegrams (no telegram filtering or dropping) is only
intended for testing purposes and may cause risks or conflicts in the KNX
installation if permitted permanently.
Physical: Repetition if Errors on Main Line: sets the desired reaction upon
transmission errors in the mainline (e.g.: busy receiver, acknowledgement not
received, negative acknowledgement, etc.) of telegrams destined to physical
addresses. The options are “No” (the undelivered telegram will not be re-
sent), “Normal” (default option; the undelivered telegram will be re-sent up to
3 times) and “Reduced” (the undelivered telegram will be re-sent once).
Group: Repetition if Errors on Main Line: sets the desired reaction upon
transmission errors in the mainline (e.g.: busy receiver, acknowledgement not
received, negative acknowledgement, etc.) of telegrams destined to a group
address. The options are “No” (the undelivered telegram will not be re-sent),
“Normal” (default option; the undelivered telegram will be re-sent up to three
times) and “Reduced” (the undelivered telegram will be re-sent once).
Telegram Confirmations on Line: sets when the line coupler should confirm
(by sending an immediate ACK message) the reception of telegrams.
Selecting “If routed” (default option) will make the line coupler respond with
an IACK message only if the received telegram is routed towards the
mainline, while “Always” will make the line coupler send a confirmation for
every telegram it receives, even if not routed to the line on the other side.
Send Confirmation on Own Telegrams: permits enabling (“Yes”) or
disabling (“No”; default option) self-acknowledgment. This extra feature offers
the possibility to send an ACK to the destination line immediately after
passing the telegram itself, so the telegram will show as confirmed on it
(therefore preventing repetitions in case of faulty projects, etc.) even if no
device is receiving it. In case of reception errors on the destination line,
negative ACKs sent by the devices will overwrite this ACK, so having this
parameter enabled will cause no damage or information loss.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
17
3.4 SUB-LINE
This screen permits parameterising the behaviour of the line coupler regarding the sub-
line, that is, when telegrams are being transferred towards the sub-line.
As shown in Figure 11, the available parameters are completely analogous to those in
the “Main line” tab.
Figure 11 Sub-Line
Please refer to section 3.3 for a detailed description of these parameters, taking into
account that section 3.3 applies to the mainline instead of the sub-line.

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
18
4ETS PARAMETERISATION (LINEREPEATER)
To begin with the parameterisation process of the device, it is necessary, once the ETS
program has been opened, to import the database of the product (Linerepeater
application program).
Figure 12 Properties of the Linerepeater 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
parameters of the device.
4.1 DEFAULT PARAMETERISATION
When entering the parameter edition of Zennio Linecoupler for the first time, a window
similar to Figure 13 will be shown, where three main tabs are available: General, Main
line and Line. Note that this application program does not implement communication
objects.
Figure 13 General

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
19
4.2 GENERAL
As shown in Figure 13, this screen contains two parameters, both related to the manual
mode of the device (see section 2.2):
Fallback Time for Manual Operation: sets the maximum operation time for
the manual mode. Once exceeded, the device will automatically leave manual
mode and return to normal mode. The available values are: 10 minutes, 1
hour (default), 4 hours and 8 hours.
Manual Function: sets the desired function to be executed by the device
while in the manual mode. The available values are: disabled (no action),
pass all telegrams (default option; the device will not filter/drop any telegram
transferred from one line to the other), pass physical telegrams (the device
will not filter physical addresses; in other words, all telegrams destined to
physical addresses will be transmitted while in manual mode) and pass group
telegrams (the device will not filter group addresses –note that this has no
practical effect; the line repeater does always let group telegrams pass in
normal mode– while, on the other hand, physical address filtering will stay the
same in normal mode).
4.3 MAIN LINE
This screen permits parameterising the behaviour of the line repeater regarding the
mainline (i.e., when the telegrams travel towards the bus connected to the terminal on
the left; see Figure 3). Note that in the case of the line repeater both lines belong to the
same hierarchical range, although they will still be referred here to as “mainline” and
“sub-line”, in order to distinguish them.
Figure 14 Mainline

Zennio Linecoupler
http://www.zennio.com Technical Support: http://zennioenglish.zendesk.com
20
The available parameters are described next:
Configuration: as in the Linecoupler application program, this parameter
permits selecting a general preset for the mainline, or enabling the manual
configuration of each parameter (option “Configure”). However, the only
available preset in the Linerepeater application program is “Groups, Physical:
route (default option; performs no telegram filtering or dropping at all).
(The following parameters will be locked unless “Configure” has been
selected under “Configuration”).
Physical Telegrams: sets the behaviour of the device regarding telegrams
destined to individual addresses. The available options are “Transmit all”
(default option; no telegram filtering or dropping) and “Block” (all telegrams
will be dropped).
Physical: Repetition if Errors on Main Line: sets the desired reaction upon
transmission errors in the mainline (e.g.: busy receiver, acknowledgement not
received, negative acknowledgement, etc.) of telegrams destined to physical
addresses. The options are “No” (the undelivered telegram will not be re-
sent), “Normal” (the undelivered telegram will be re-sent up to three times)
and “Reduced” (default option; the undelivered telegram will be re-sent once).
Group: Repetition if Errors on Main Line: sets the desired reaction upon
transmission errors in the mainline (e.g.: busy receiver, acknowledgement not
received, negative acknowledgement, etc.) of telegrams destined to a group
address. The options are “No” (the undelivered telegram will not be re-sent),
“Normal” (the undelivered telegram will be re-sent up to three times) and
“Reduced” (default option; the undelivered telegram will be re-sent once).
Telegram Confirmations on Line: sets when the line repeater should
confirm (by sending an immediate ACK –or IACK– message) the reception of
telegrams. Selecting “If routed” (default option) will make the line repeater
respond with an IACK message only if the received telegram is routed
towards the sub-line, while “Always” will make the line repeater send a
confirmation for every telegram it receives, even if not routed to the line on
the other side.