KNX-IP Router / Interface PLess

Zennio KNX-IP Router PLess
Zennio KNX-IP Interface PLess
ZSY-IPR-PL
ZSY-IPI-PL
Application Program version Zennio KNX-IP Router PLess: [1.1]
Application Program version Zennio KNX-IP Interface PLess: [1.0]
User Manual version: [1.1]_a
www.zennio.com
USER MANUAL
Enrutador and Interface KNX to IP
Zennio KNX-IP Router / Interface PLess
CONTENTS
Contents ................................................................................................................................ 2
Document Updates................................................................................................................ 3
1
2
Introduction .................................................................................................................. 4
1.1
Zennio KNX-IP Router/Interface PLess .................................................................. 4
1.2
Installation ............................................................................................................. 6
1.3
Using the Device as a Programr ............................................................................ 7
1.3.1
Parallel Downloads ............................................................................................ 7
1.3.2
Limitations ......................................................................................................... 8
Description .................................................................................................................... 9
2.1
KNX to IP Interface ................................................................................................ 9
2.2
Line or area coupler .............................................................................................. 9
2.3
Telegram Filtering ............................................................................................... 11
2.4
LED Indicators ...................................................................................................... 13
2.5
Manual Function Button ..................................................................................... 16
2.5.1
Manual Operation Mode................................................................................. 16
2.5.2
Hard Reset to Factory Defaults ....................................................................... 17
2.6
3
Web Interface...................................................................................................... 18
2.6.1
Device Info ....................................................................................................... 18
2.6.2
KNX .................................................................................................................. 19
2.6.3
Firmware Update ............................................................................................ 21
ETS Parameterisation .................................................................................................. 23
3.1
General ................................................................................................................ 25
3.2
IP Configuration................................................................................................... 27
3.3
KNX Multicast Address ........................................................................................ 28
3.4
Main Line ............................................................................................................. 29
3.5
Line ...................................................................................................................... 31
http://www.zennio.com
Technical Support: http://support.zennio.com
2
Zennio KNX-IP Router / Interface PLess
DOCUMENT UPDATES
Version
Changes
Page(s)
Changes in the Zennio KNX-IP Router PLess application
program:
[1.1]_a
-
Character restriction for “Host Name” parameter.
-
Internal code optimisation.
Changes in the document
-
http://www.zennio.com
Minor corrections
Technical Support: http://support.zennio.com
3
Zennio KNX-IP Router / Interface PLess
1 INTRODUCTION
1.1 ZENNIO KNX-IP ROUTER/INTERFACE PLESS
Zennio KNX-IP Router PLess and Zennio KNX-IP Interface PLess are the solution from
Zennio for the interconnection of KNX twisted-pair lines and Ethernet medium with
no need of external power.
The main differences between the two devices are:
Zennio KNX-IP Interface PLess: simple KNX to IP interface solution.
Zennio KNX-IP Router PLess: can be used as line or area coupler to
provide data connection between the upper KNXnet/IP line and the lower
KNX twisted-pair bus line.
Backbone line
Main line
LC
AC
LC
Device
Device
Line
LR
Line
Device
Device
Figure 1. Context (Topology)
Both also provide a connection point for ETS to enable programming (up to four
parallel connections) and monitoring the KNX line via IP.
These are the most outstanding features of these two devices:
Support for long messages (up to 250 bytes).
Support for group addresses in the range 14 to 31.
Up to 4 parallel connections from ETS for programming and monitoring.
http://www.zennio.com
Technical Support: http://support.zennio.com
4
Zennio KNX-IP Router / Interface PLess
No external power required.
High capacity buffer for the reception of telegrams from the Ethernet
network.
Web interface to display the device settings, to switch to the programming
mode and for firmware updates.
.7 lighting indicators (LEDs): two bus state indicators per line (with
detection
of
abnormal
situations:
excessive
bus
load,
message
retransmissions, etc.), one more indicator per line for the state of the filtering
function, and one additional indicator for the programming mode.
Only in Zennio KNX-IP Router PLess:
 Use as an area or line coupler with a LAN as main line or main area line,
offering a fast communication medium for telegram exchange.
 Traffic filtering according to the project topology and to the built-in
address table.
 Telegram dropping.
 Blocking of device-configuration telegrams (telegrams destined to
physical addresses).
 Customisable Function pushbutton for triggering the manual mode,
useful at runtime and for set-up and troubleshooting purposes.
http://www.zennio.com
Technical Support: http://support.zennio.com
5
Zennio KNX-IP Router / Interface PLess
1.2 INSTALLATION
1. Main line (LAN) connector.
2. Main line (LAN) status LED.
3. Main line (LAN) traffic LED.
4. Group address filter status LED.
1
5. Manual function button.
2
6. Secondary line (KNX) status LED.
7. Secondary line (KNX) traffic LED.
8. Physical address filter status.
6
3
4
7
8
5
9. Programming LED.
10. Programming button.
9
10
11. Secondary line (KNX) connector.
12. DIN rail clamp.
11
12
Figure 2 Element Diagram
Figure 2 shows a scheme with all the LED indicators and required connections. This
device does not require an external power supply, it is powered through the KNX bus.
To couple a KNX twisted-pair (TP) line and a LAN, the KNX bus (11) and Ethernet (1)
cables must be connected. After the connection, the device can be conveniently
mounted on the DIN rail by the usual procedure
The programming button (10) shown in Figure 2 may be pressed to set Zennio KNX-IP
Router PLess in programming mode. After a short press, the programming LED (9)
will light in red.
The behaviour of the additional LEDs and the manual function button will be described
in sections 2.4 and 2.5.
For detailed information about the technical features of the device, as well as on
security and installation procedures, please refer to the device Datasheet, bundled
within the original packaging of the device and also available at http://www.zennio.com.
http://www.zennio.com
Technical Support: http://support.zennio.com
6
Zennio KNX-IP Router / Interface PLess
1.3 USING THE DEVICE AS A PROGRAMR
Zennio KNX-IP Router PLess and Zennio KNX-IP Interface PLess can be used in ETS
as a programming interface. In addition to an IP address, they must be assigned a
KNX individual address for this purpose.
Note: to detect the Zennio KNX-IP Router/Interface PLess as a programmer in ETS, it
needs to be connected to the same IP network as the PC.
1.3.1 PARALLEL DOWNLOADS
ETS offers the option to perform multiple parallel downloads within the same project.
This option is only available for connections via a KNX-IP router or a KNX-IP interface.
Certain conditions must be met:
Each download must be performed on a different line.
For each line, it is necessary to select one Zennio KNX-IP Router PLess or
one Zennio KNX-IP Interface to perform the download.
In ETS5 this is configured in the line properties.
Figure 3 ETS5 parallel downloads configuration.
http://www.zennio.com
Technical Support: http://support.zennio.com
7
Zennio KNX-IP Router / Interface PLess
In ETS4 this is configured by right-clicking on the line and, under "Set
Connection", selecting the desired connection.
Figure 4 ETS4 parallel downloads.
Note: once the connection has been selected, it will not be available for the other lines.
An additional restriction applies to parallel downloads: they are not available to
download physical addresses. When performing this type of downloads, the link
device used by ETS is not the one configured for the line but the general one.
1.3.2 LIMITATIONS
It is important to note that Zennio KNX-IP Router PLess and Zennio KNX-IP Interface
PLess, when being used as programrs, do not allow bus monitoring (the ETS bus
monitor will not be available).
Moreover, these devices do not allow being unloaded (unprogramd) from ETS.
Equivalently, they can be reset to the factory default state, as explained in section
2.5.2.
http://www.zennio.com
Technical Support: http://support.zennio.com
8
Zennio KNX-IP Router / Interface PLess
2 DESCRIPTION
2.1 KNX TO IP INTERFACE
As indicated before, Zennio KNX-IP Router / Interface PLess is an interface device
intended for the interconnection between a KNX bus and an Ethernet network (LAN).
Specifically, as a programming interface for ETS, it allows up to four simultaneous
connections for performing downloads or for bus monitoring.
On the other hand, Zennio KNX-IP Router / Interface PLess can be allocated within the
project topology in ETS, as any other device. This step can be omitted when it is going
to be used as interface, because there is no need to modify the default configuration.
However, when requiring to modify the configuration or to filter telegrams for the KNXIP Router an individual address should be assigned in order to download the
parameters.
2.2 LINE OR AREA COUPLER
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
Zennio KNX-IP Router PLess can be used as a line coupler (for coupling both a line to
a mainline) or as an area coupler (for coupling a main line to an area line, also
referred to as backbone line). The operation on both cases is analogous – being a line
coupler or an area coupler only depends on the location of the device within the
topology.
Figure 5 shows a typical scenario where Zennio KNX-IP Router PLess can be installed
as any of the nodes the nodes labelled as “AC” (area coupler) or “LC” (line coupler):
Coupling an area line and a main line requires an area coupler (AC). Zennio
KNX-IP Router PLess is intended for cases where the medium of the former
is Ethernet while the medium of the latter is TP.
Coupling a main line and a line requires a line coupler (LC). Zennio KNX-IP
Router PLess is intended for cases where the medium of the former is
http://www.zennio.com
Technical Support: http://support.zennio.com
9
Zennio KNX-IP Router / Interface PLess
Ethernet while the medium of the latter is TP. In such cases, the medium of
the area line (if any) is assumed to be Ethernet as well.
AC
Main Line
LC
4.1.0
LC
4.2.0
4.1.2
4.0.1
Line
Line
4.0.0
Main Line
LC
4.2.1
3.1.0
LC
3.2.0
3.0.0
3.1.2
3.0.1
3.1.1
Line
AC
Line
Area Line (backbone)
4.1.1
4.2.2
3.2.2
3.2.1
Figure 5 Line Coupling
On the other hand, Zennio KNX-IP Router PLess can be incorporated to the ETS
project topology as any other device. This step is not compulsory if the default
configuration meets the requirements of the integrator. However, should they require
modifying any parameters or filter table the device must be assigned a physical
address prior to downloading the new parameterisation.
Whatever the location in the topology, Zennio KNX-IP Router PLess offers an insulated
coupling interface with the possibility, in the particular case of the Router, of filtering
the traffic according to the topology or to group-address dependent criteria. In other
words, Zennio KNX-IP Router PLess will (or will not) let telegrams pass from one
medium to the other according to the parameterisation.
Note: the individual address of a line coupler needs to be of the form X.Y.0 (or X.0.0 in
case of working as a backbone coupler).
http://www.zennio.com
Technical Support: http://support.zennio.com
10
Zennio KNX-IP Router / Interface PLess
2.3 TELEGRAM FILTERING
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
Zennio KNX-IP Router PLess provides two complementary filter types:
Group address filtering: ETS automatically generates a group address table
for the project loaded. This table is transferred to the line coupler during
complete ETS downloads over it.
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
secondary 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 6). If so, then the line coupler will let it pass. Otherwise, it
won’t be transferred to the secondary line. The same would also apply to the
inverse case (a telegram originating in the secondary line).
Figure 6 ETS Option to Force Passing a Group Address through the Line Coupler
http://www.zennio.com
Technical Support: http://support.zennio.com
11
Zennio KNX-IP Router / Interface PLess
Physical address filtering: when the device 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 line.
Example: in the example shown in Figure 5, if the coupler with address 3.2.0
reads a telegram on the mainline destined to a device with individual address
3.1.2, it will compare both addresses and conclude that 3.1.2 does not belong
to the secondary line, and therefore not transmit it.
Notes:
 The device that sends a telegram needs to have been assigned a physical
address that really corresponds to its line. In Figure 5, if the device with
address 3.1.1 (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.
 As device programming consists in sending telegrams destined to a
physical address, in order to perform downloads to a device in a certain
line (for example, the device with address 4.1.1 in Figure 5) from a
programr not in that line, it is necessary that the line coupler is configured
to let pass all physical addresses from the main line.
http://www.zennio.com
Technical Support: http://support.zennio.com
12
Zennio KNX-IP Router / Interface PLess
2.4 LED INDICATORS
Zennio KNX-IP Router / Interface PLess incorporates seven LED lights on the top of
the device that make it easy to monitor the status of the buses and to detect typical
communication problems, as detailed next.
Figure 7 LEDs
Mainline (IP) Status LED: shows the status of the primary bus.
 OFF: error or mainline not connected or not powered.
 ON (green) = Ethernet connection OK.
 ON (orange) = manual function in execution or factory reset preparation.
Note: the LED colours are independent. It must be taken into account that
when the green and red colours are on at the same time, the result colour
is orange.
The update of the LED status can be delayed a few seconds after the
trigger event, e.g., after the disconnection of the main line.
KNX Line Status LED: shows the status of the secondary bus.
 OFF: error or secondary line not connected.
 ON (green): OK
 BLINKING (green): boot mode (see section 2.6.3).
http://www.zennio.com
Technical Support: http://support.zennio.com
13
Zennio KNX-IP Router / Interface PLess
 ON (red): factory reset in execution (see section 2.5.2).
Note: the LED colours are independent. It must be taken into account that
when the green and red colours are on at the same time, the result colour
is orange.
Mainline (IP) Traffic LED: shows the traffic status in the Ethernet.
 BLINKING (green): traffic.
 OFF: no traffic.
 ON (red): errors in the transmissions.
KNX Line Traffic LED: shows the traffic status in the secondary bus.
 BLINKING (green) = traffic.
 OFF = no traffic.
 BLINKING (red) = errors in the transmissions.
Group Address (GA) Filter Status LED: shows the current configuration of
the group address routing:
 OFF: different configuration for the Ethernet and the secondary lines.
 ON (green): filtering active.
 ON (red and green = orange): all group addresses routed (filtering
disabled).
 ON (red): all group addresses blocked.
Note: these LEDs are non-functional in Zennio KNX-IP Interface PLess.
Physical Address (PA) Filter Status LED: shows the current configuration
of the individual address routing:
 OFF: different configuration for the Ethernet and the secondary lines.
 ON (green): filtering active.
http://www.zennio.com
Technical Support: http://support.zennio.com
14
Zennio KNX-IP Router / Interface PLess
 ON (red and orange = yellow): all physical addresses routed (filtering
disabled).
 ON (dark orange): all physical addresses blocked.
Notes:
 These LEDs are non-functional in Zennio KNX-IP Interface PLess.
 Please be careful not to confuse yellow and dark orange.
Programing LED:
 OFF = normal operation.
 ON (red) = programing mode active.
 BLINKING (red) = Ethernet cable disconnected.
Please refer to section 3 for a detailed explanation of the different behaviours and
parameterisations of the Zennio KNX-IP Router / Interface PLess application
program.
http://www.zennio.com
Technical Support: http://support.zennio.com
15
Zennio KNX-IP Router / Interface PLess
2.5 MANUAL FUNCTION BUTTON
Zennio KNX-IP Router / Interface PLess features an additional pushbutton on the top
cover, next to the status LEDs (see (5) in Figure 2), which permits:
Activating the Manual Operation Mode (see section 2.5.1), only in Zennio
KNX-IP Router PLess.
Performing a hard reset to the factory defaults (see section 2.5.2).
Authorising a firmware update (see section 2.6.3).
2.5.1 MANUAL OPERATION MODE
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
A three-second press on this button will set the device in manual mode, which will
activate a customisable 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 three seconds (or if the
parameterised fall-back 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 the loss of the parameters or
filter tables previously downloaded.
In the application program of the device, the available manual functions are:
Disabled,
Pass all telegrams,
Pass physical telegrams,
Pass group telegrams.
Please refer to section 3 for the parameterisation in ETS of the manual function and for
a detailed description of the different options.
http://www.zennio.com
Technical Support: http://support.zennio.com
16
Zennio KNX-IP Router / Interface PLess
2.5.2 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. The
default parameters of the devices are:
Zennio KNX-IP Router PLess
 Physical address: 15.15.0.
 Host name: KNX-IP Router (see section 3.1).
 DHCP activated.
 KNX Multicast address: 224.0.23.12 (see section 3.3).
 “Transmit all” for group telegrams and physical telegrams.
Zennio KNX-IP Interface PLess
 Physical address: 15.15.255.
 Host name: KNX-IP Interface (see section 3.1).
 DHCP: activated.
These are the steps to restore the factory settings:
Press the manual function button for at least 15 seconds. The main line, KNX
line, and group filter state LEDs will light in orange (or red if they were not
green previously) and the physical address filter state LED will turn yellow (or
orange if it was not green previously).
Release the manual function button and press it again for about 3 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.
http://www.zennio.com
Technical Support: http://support.zennio.com
17
Zennio KNX-IP Router / Interface PLess
2.6 WEB INTERFACE
Zennio KNX-IP Router PLess / Interface PLess provides a web interface for
consulting the device configuration, activating the programming mode or
updating the firmware.
The web interface can be accessed through port 8080 of the IP address of the device.
For example, if the IP address is 192.168.1.222:
http://192.168.1.222:8080
The following URLs (where “xxxxxx” refers to the last six digits of the MAC address of
the device) will be equivalent:
Zennio KNX-IP Router PLess: http://KNX-IPrt-xxxxxx:8080.
Zennio KNX-IP Interface PLess: http://KNX-IPif-xxxxxx:8080.
The IP address of the device can be easily obtained in ETS as long as the device
belongs to the same LAN segment than the PC. On the other hand, the MAC address
must be printed on the cover of the device.
Note: Zennio KNX-IP Router PLess allows using port 80 instead of 8080 by enabling it
in parameters. In such case, it can be omitted from the access URL.
2.6.1 DEVICE INFO
The “Device Info” tab in the web interface contains general information about the
current settings of the device, as Figure 8 shows.
Figure 8 Web interface (Device Info).
http://www.zennio.com
Technical Support: http://support.zennio.com
18
Zennio KNX-IP Router / Interface PLess
2.6.2 KNX
Under the “KNX” tag, it is possible to obtain information about the KNX (TP) line and to
perform some actions (e.g.: activate the programming led).
Figure 9 Web interface (KNX line info)
Program Mode: shows whether the programming mode (and therefore the
programming LED) is on or off.
Change Program Mode: activates or deactivates the programming mode, and
therefore the programming LED.
Individual Address: shows the individual address of the device.
Tunneling Addresses. shows the additional individual addresses for the
tunneling function (see section 2.6.2.1).
Set Tunneling Addresses: allows defining additional individual addresses for
the tunneling function (see section 2.6.2.1).
Routing Multicast Address (only in Zennio KNX-IP Router PLess): shows
the IP address the KNX telegrams are sent to or received from in the LAN
network. It can be configured in ETS.
Serial number: shows the internal serial number of the device.
KNX Busload (only in Zennio KNX-IP Router PLess): shows a graph that
reflects the KNX bus load in the past 60 minutes; see Figure 10. The red
curve represents the local maximum while the green one indicates the local
average load on the KNX bus.
http://www.zennio.com
Technical Support: http://support.zennio.com
19
Zennio KNX-IP Router / Interface PLess
Note: this function requires a web browser that supports the SVG (Scalable
Vector Graphics) format.
Figure 10 Web interface (KNX bus load)
2.6.2.1 ADDICIONAL INDIVIDUAL ADDRESSES (TUNNELING ADDRESSES)
Zennio KNX-IP Router / Interface PLess requires a specific individual address when
acting as a programming interface (tunneling) other than the address of the device
itself. Up to four simultaneous connections are possible, which implies that up to four
different individual addresses must be configured.
The “KNX” tab in the web interface shows the four tunneling individual addresses
currently configured.
Figure 11 Set tunneling addresses in web interface.
The first tunneling address must be set in ETS as shown in Figure 12 for ETS4 or in
Figure 13 for ETS5. The following three addresses are automatically set with values
consecutive to the first.
http://www.zennio.com
Technical Support: http://support.zennio.com
20
Zennio KNX-IP Router / Interface PLess
Figure 12 Configuration of the first tunneling address in ETS4.
Figure 13 Configuration of the first tunneling address in ETS5.
2.6.3 FIRMWARE UPDATE
The “Update” section of the web interface permits updating the internal firmware of the
device
whenever
Zennio
releases
a
new
firmware
version
(through
the
http://www.zennio.com website) by following these steps (please see Figure 14):
Authorise the update:
http://www.zennio.com
Technical Support: http://support.zennio.com
21
Zennio KNX-IP Router / Interface PLess
 Set the device into the programming mode.
 Press the manual function button.
 Wait for the “update authorized” message on the screen.
Request the update:
 From the “Update” section, press the “Request Update” button, and wait
until the device reboots and enters Boot mode.
Upload the firmware:
 Browse for the hexadecimal file.
 Press the “Upload” button.
Figure 14 Web interface (firmware update).
After the second step (update request), the device switches to Boot mode, which
interrupts the normal device operation (telegram filtering, etc.), being no longer
possible to connect to it. It will remain in this mode for ten minutes to allow the
firmware update before returning to the normal mode.
During the Boot mode’ the TP line status LED indicator blinks in green.
Notes:
The Boot mode can be alternatively accessed by disconnecting the power
supply and re-connecting it while pressing the Programming or the Manual
Function buttons, or both together.
http://www.zennio.com
Technical Support: http://support.zennio.com
22
Zennio KNX-IP Router / Interface PLess
3 ETS PARAMETERISATION
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 (Zennio KNX-IP
Router PLess or Zennio KNX-IP Interface PLess application programs).
Figure 15 Properties of the Zennio KNX-IP Router PLess Application Program
Next, the device should be added to the project where desired.
When intending to use the device as a programming interface, it will be necessary to
access the ETS settings and select the desired interface
In the case of Zennio KNX-IP Router PLess, note that, depending on where the
device is placed, the upper levels of the topology need to be configured as KNXnet /
IP:
The backbone line, in case of working as an area coupler.
The backbone line and the main line of the area the device belongs to, in
case of working as a line coupler.
http://www.zennio.com
Technical Support: http://support.zennio.com
23
Zennio KNX-IP Router / Interface PLess
Figure 16 Zennio KNX-IP Router PLess as an Area Coupler.
Figure 17 Zennio KNX-IP Router PLess as a Line Coupler.
Finally, the configuration process begins by entering the Parameters tab of the device.
The following sections provide a detailed explanation about each of the different
parameters of the device.
Note: Zennio KNX-IP Router / Interface PLess does not require any communication
objects.
http://www.zennio.com
Technical Support: http://support.zennio.com
24
Zennio KNX-IP Router / Interface PLess
3.1 GENERAL
When entering the parameter edition of Zennio KNX-IP Router / Interface PLess for the
first time, a window similar to Figure 18 will be shown.
Figure 18 General.
As shown in Figure 18, this screen contains the following parameters:
Host Name: string of up to 30 characters to easily identify the device in ETS
or from a KNXnet/IP system.
Slow Tunneling Connections (only in Zennio KNX-IP Router PLess): allows
slow connections between ETS and the device.
Manual Function (only in Zennio KNX-IP Router PLess): sets the desired
function to be executed by the device while in the manual mode. The
available values are:
 “Disabled” (no action),
 “Transmit All Telegrams” (default option; the device will not filter/drop any
telegram transferred from one line the other),
 “Transmit Physical Addr. 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),
 “Transmit Group Addr. 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).
http://www.zennio.com
Technical Support: http://support.zennio.com
25
Zennio KNX-IP Router / Interface PLess
Duration of Manual Function (only in Zennio KNX-IP Router PLess): 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”.
In addition to the General screen, some additional tabs are available in the tree on the
left. The parameters they contain are described in the next sections.
http://www.zennio.com
Technical Support: http://support.zennio.com
26
Zennio KNX-IP Router / Interface PLess
3.2 IP CONFIGURATION
Figure 19 IP Configuration tab – DHCP: do not use.
Zennio KNX-IP Router / Interface PLess is provided with the DHCP protocol enabled
by default, and therefore can gain an IP address automatically as long as a DHCP
server is available in the local network. From ETS, it is possible to disable the use of
the DHCP and manually set an IP address for the device, as well as the subnet
mask, the IP address of the network gateway and that of the DNS server. Thus, it is
advisable to contact the manager of the local network.
Notes:
To make this configuration effective, after the download from ETS it is
necessary to interrupt the external power supply of the device for an
instant, and afterwards restore it.
A wrong configuration of these parameters (e.g., IP address “0.0.0.0” or
subnet mask “0.0.0.0”) may leave the device locked, with the LAN traffic
status LED lighting in red colour. To exit this status, it is necessary to
disconnect the Ethernet cable and restore the factory defaults (section 2.5.2).
In the particular case of Zennio KNX-IP Router PLess, an option is also provided to
select the desired access port to the web interface: “8080” (by default) or “80”.
http://www.zennio.com
Technical Support: http://support.zennio.com
27
Zennio KNX-IP Router / Interface PLess
3.3 KNX MULTICAST ADDRESS
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
Telegrams sent from the KNX bus to the IP network, or vice versa, travel through the
latter as multicast IP packets, addressed to port 3671 at IP address number
224.0.23.12 so that they reach all KNX-IP interfaces available on the network.
Such address is reserved by the IANA organisation for the KNXnet/IP protocol, and
should only be changed in parameters (Use Default Multicast Address = “No”) in case
the network configuration requires it or to create different, independent topologies
within the same IP network.
Otherwise, it should be left as is (Use Default Multicast Address = “Yes”)
Figure 20 KNX multicast address configuration tab.
http://www.zennio.com
Technical Support: http://support.zennio.com
28
Zennio KNX-IP Router / Interface PLess
3.4 MAIN LINE
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
Figure 21 Main Line tab.
This screen permits parameterising the behaviour of Zennio KNX-IP Router PLess
regarding the telegrams received from the main line (Ethernet).
The available parameters are described next:
Configuration: permits selecting a predefined set of parameters for the
mainline, or enabling the manual configuration of each parameter (option
“Custom”). The available options are:
 “Groups Addr.: Filter; Physical Addr.: Block” (enables the group address
filtering and drops all telegrams destined to physical addresses),
 “Groups Addr., Physical Addr.: Filter” (default option; enables both the
group address and the physical address filtering),
 “Groups Addr.: Route; Physical Addr.: Filter” (performs no blocking or
filtering over the group address but does filter telegrams destined to
physical addresses),
 “Groups Addr., Physical Addr.: Route” (performs no telegram filtering or
dropping at all).
Note: transmitting all telegrams (no telegram filtering or dropping) is intended
for diagnostic purposes and may cause risks or conflicts or generate a large
amount of traffic in the KNX installation if permanently activated.
http://www.zennio.com
Technical Support: http://support.zennio.com
29
Zennio KNX-IP Router / Interface PLess
(The following parameters will be locked unless “Configure” has been selected under
“Configuration”).
Group Addresses 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),
 “Filter” (default option; telegrams will be filtered, dropping only the
corresponding ones, according to the filter table; see section 2.3).
Note: transmitting all telegrams (no telegram filtering or dropping) is intended
for diagnostic purposes and may cause risks or conflicts or generate a large
amount of traffic in the KNX installation if permanently activated.
Group Addresses Telegrams > 13: sets the desired action to perform over
telegrams destined to group addresses beginning with “14” or greater (e.g.,
14/1/1). The options are “Filter”, “Transmit all” (default option) and “Block”.
Physical Addresses 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),
 “Filter”
(default
option;
telegrams
will
be
filtered,
dropping
the
corresponding ones; see section 2.3).
Note: transmitting all telegrams (no telegram filtering or dropping) is intended
for diagnostic purposes and may cause risks or conflicts or generate a large
amount of traffic in the KNX installation if permanently activated. However,
being able to perform downloads to devices in a different line than the
programr requires setting this option to “Transmit All”.
http://www.zennio.com
Technical Support: http://support.zennio.com
30
Zennio KNX-IP Router / Interface PLess
3.5 LINE
Note: this functionality does not apply to Zennio KNX-IP Interface PLess.
This screen permits parameterising the behaviour of Zennio KNX-IP Router PLess
regarding the telegrams received from the KNX line.
As shown in Figure 22, the available parameters are completely analogous to those in
the “Main line” tab.
Figure 22 KNX line configuration tab.
Please refer to section 3.4 for a detailed description of these parameters; taking into
account that section 3.4 applies to the main line instead of the line.
The following parameters are specific for the line (they are not available for the main
line):
Physical Addresses: Repetition if Errors on Line: sets the desired reaction
upon transmission errors in the line (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
three times),
http://www.zennio.com
Technical Support: http://support.zennio.com
31
Zennio KNX-IP Router / Interface PLess
 “Reduced” (the undelivered telegram will be re-sent once).
Group Addresses: Repetition if Errors on Line: sets the desired reaction
upon transmission errors in the line (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),
 “Reduced” (the undelivered telegram will be re-sent once).
Telegram Confirmations on Line: sets when the device should confirm (by
sending an immediate ACK message or IACK) the reception of telegrams.
 “If Routed” (default option) will make the device respond with an IACK
message only if the received telegram is routed towards the mainline,
 “Always” will make the device 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 of sending 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.
Configuration from Line: enables (default option) or disables performing
ETS downloads over the Zennio KNX-IP Router from the line. If disabled,
programming this device from ETS will only be possible via IP.
http://www.zennio.com
Technical Support: http://support.zennio.com
32
Join and send us your inquiries
about Zennio devices:
http://support.zennio.com
Zennio Avance y Tecnología S.L.
C/ Río Jarama, 132. Nave P-8.11
45007 Toledo (Spain).
Tel. +34 925 232 002
www.zennio.com
info@zennio.com
Download PDF
Similar pages