K-BUS BNIPR-00/00.1 User manual

KNX IP Router_V1.3
BNIPR-00/00.1
KNX/EIB Home and Building Control System
User Manual

Attentions
1. Please keep devices away from strong magnetic field, high temperature,
wet environment;
2. Do not fall the device to the ground or make them get hard impact;
3. Do not use wet cloth or volatile reagent to wipe the device;
4. Do not disassemble the devices.

Contents
Chapter 1 Summary -----------------------------------------------------------------------------------------------------1
1.1 Function overview ----------------------------------------------------------------------------------------------- 2
1.2 Tunneling --------------------------------------------------------------------------------------------------------- 3
1.3 Routing ------------------------------------------------------------------------------------------------------------3
1.4 KNX IP Routers ---------------------------------------------------------------------------------------------------3
Chapter 2 Technical Data & Dimension and Connection Diagram ------------------------------------------------- 4
2.1 Technical data ----------------------------------------------------------------------------------------------------4
2.2 Dimension diagram ---------------------------------------------------------------------------------------------- 6
2.3 Connection diagram --------------------------------------------------------------------------------------------- 6
Chapter 3 Planning and Application -----------------------------------------------------------------------------------8
3.1 Operation Modes -------------------------------------------------------------------------------------------------8
3.1.1 LED indication -----------------------------------------------------------------------------------------------8
3.1.2 The Function Button ----------------------------------------------------------------------------------------8
3.1.3 The Programming Button and LED ------------------------------------------------------------------------9
3.2 IP router application --------------------------------------------------------------------------------------------- 9
3.2.1 KNX Telegrams in the IP Network -----------------------------------------------------------------------10
3.2.2 The IP Router in a Network Installation -----------------------------------------------------------------11
3.2.3 The IP Router as an Area Coupler ----------------------------------------------------------------------- 11
3.2.4 The IP Router in a Mixed System ------------------------------------------------------------------------11
3.2.5 The IP Router as A Line Coupler -------------------------------------------------------------------------13
Chapter 4 Parameter setting description in the ETS ---------------------------------------------------------------14
4.1 Physical Address Assignment -------------------------------------------------------------------------------- 14
4.2 General ---------------------------------------------------------------------------------------------------------- 15
4.3 IP Configuration ------------------------------------------------------------------------------------------------ 16
4.4 KNX Multicasting Address ------------------------------------------------------------------------------------ 17
4.5 Main Line -------------------------------------------------------------------------------------------------------- 18
4.6 Sub Line --------------------------------------------------------------------------------------------------------- 19
Chapter 5 Web Front-end --------------------------------------------------------------------------------------------- 22
5.1 Accessing the Web Front-end ---------------------------------------------------------------------------------22
5.1.1 Via windows Network UPnP ------------------------------------------------------------------------------23
5.1.2 Via IP Address ---------------------------------------------------------------------------------------------24
5.1.3 Via MAC Address ------------------------------------------------------------------------------------------25
5.2 Device Info ------------------------------------------------------------------------------------------------------ 26
5.3 KNX -------------------------------------------------------------------------------------------------------------- 27
5.4 Firmware Update / Boot Mode -------------------------------------------------------------------------------- 28
5.5 IP Tunneling Address Assignment --------------------------------------------------------------------------- 30
Chapter 6 State of Delivery ------------------------------------------------------------------------------------------- 32

KNX/EIB KNX IP Router
1
Chapter 1 Summary
The IP Router can be used as line or backbone coupler. It provides a data connection between
the upper KNXnet/IP line (main line or backbone) and the lower TP KNX bus line (sub line). The
basic functionality of the IP Router is to couple the Ethernet with one or more KNX-TP lines. The IP
Router features a galvanic isolation between the Ethernet and the KNX-TP line(s). Due to its
flexibility the IP Router can be used as a line coupler e.g. to connect several KNX TP lines via
Ethernet. And it can be used as a backbone coupler to connect several TP areas or different TP
installation systems via Ethernet.
The main task of the IP Router is filtering the traffic according to the installation hierarchy. For
group oriented communication the traffic is filtered according to the built-in filter tables.
With the ETS or any other KNX compatible commissioning tool the IP Router can be used as
the programming interface. For this purpose the device provides up to 4 additional physical
addresses that can be used for tunneling. The IP Router has no KNX communication objects for
itself.
The IP Router is a Tunneling and Routing device. These features are described in the following
sections in detail. The device front panel consists of seven LEDs and two buttons as illustrated
below. The device offers a detailed internal diagnosis by displaying all operational states in
different Operation Modes with three pairs of LEDs. The LEDs show the variety of device states like
Bus OK, traffic, errors/faulty communication NACK, BUSY on the bus, state of the filter table, and
etc.
The IP Router is a modular installation device. It can be installed in the distribution board on
35mm mounting rails according to EN 60715.
This manual provides the technical information about the IP Router as well as assembly and
programming in detail for users, and explains how to use the interface device by the application
examples.

KNX/EIB KNX IP Router
2
1.1 Function overview
The IP Router has the follow functions:
The IP Router supports extended frames and long telegrams up to 240 bytes APDU
length. In combination with the line coupler and the long messages are made possible
(e.g. for energy metering applications and visualization purposes).
The IP Router favorably replaces a line coupler or an area coupler. Using LAN as a fast
medium to exchange telegrams between lines and/or areas is the great advantage.
The IP Router works without external power supply.
Providing tunneling protocols and a connection point for the ETS (or any other tool to
enable commissioning and monitoring) the ETS address for tunneling is not necessarily
the one that is already configured. Four parallel connections are possible, one separate
address for each and every connection.
IACK sending on sent out messages is ETS configurable
After no IACK response on a sent message the IP Router can repeat it up to three times.
For physically addressed or for group addressed telegrams this can be configured via
ETS independently. In case of an IACK response there will be no repetition. The failure
mechanism of a negative IACK or BUSY is still maintained hereby.
Programmable automatic switch on of the filter table after timeout.
For a predefined amount of time (ETS configurable) it is possible to switch off the filter
table with pressing a button on the device. So, without re-configuring the device with the
ETS the filter table can be switched off by a button press which is necessary for running
fast diagnostics on site. Filtering of messages can temporarily be disabled by pressing
the “Function” button. This eases commissioning and debugging of the system. Without
an ETS download a temporary access to other lines is possible. After the timeout an
automatic switching the filter table on is implemented (the timeout is configurable in the
ETS). This avoids forgetting to reactivate the filter.

KNX/EIB KNX IP Router
3
UPnP is available to discover the device in the IP network. That is only possible with a
proper network installation in terms of topology. With the KNXnet/IP Search Request the
ETS can recognize the device as a communication interface.
For networks with a high bus load a high internal amount of communication buffers is
suitable.
The IP Router is featuring a high internal amount of communication buffers being
capable of smoothing peeks in the communication load course.
The IP Router’s ETS database entries are available for the ETS3.0f and upward.
The IP Router supports KNXnet/IP, ARP, ICMP, IGMP, HTTP, UPnP discovery, UDP/IP,
TCP/IP, DHCP and Auto IP.
1.2 Tunneling
The presence of the Internet Protocol (IP) has led to the definition of KNXnet/IP. KNXnet/IP
provides the means for point-to-point connections like “KNXnet/IP Tunneling” for ETS and/or
between a supervisory system and a KNX installation.
The KNXnet/IP Device Management provides configuring KNXnet/IP devices via the KNX
network effectively. Additionally, with this the time required for network configurations is reduced.
1.3 Routing
Routing is the way of interconnecting KNX lines or areas via IP network(s) using KNXnet/IP. In
IP networks the KNXnet/IP Routing defines how KNXnet/IP routers communicate with each other.
1.4 KNX IP Routers
The IP Router is a KNX IP router. KNX IP routers are highly similar to TP line couplers. The only
exception is that they use the communication medium Ethernet as their main line. However, it is
also possible to integrate KNX end devices via IP directly. This makes the Ethernet a KNX medium.

KNX/EIB KNX IP Router
4
Chapter 2 Technical Data & Dimension and Connection Diagram
2.1 Technical data
Power supply
Operation voltage
21-30V DC, via the KNX bus
Current consumption
<20 mA
Connections
KNX
Via bus connection terminal (red/black)
LAN
RJ45 socket for 100 Mbit and 10 Mbit
BaseT, IEEE 802.3 networks
Operating and
display
Bus State IP LED
(main line)
Green on: IP line OK;
Off: IP line error or not connected;
Orange on: Manual function active.
Bus State TP LED
(sub line)
Green on: Sub line OK;
Off: Sub line not connected.
Traffic on IP LED
(main line)
Green blinking: Telegram traffic on IP line ;
Off: No telegram traffic;
Red blinking: Transmission error on IP line.
Traffic on TP LED
(sub line)
Green blinking: Telegram traffic on sub line;
Off: No telegram traffic;
Red blinking: Transmission error on sub
line.
GA LED
Off: Routing of Group Telegrams is different
on main line and sub line;
Green on: Filter table active;
Orange on: Route all;
Red on: Block.
PA LED
Off: Routing of Physical telegrams is
different
on main line and sub line;
Green on: Filter table active;
Orange on: Route all;
Red on: Block

KNX/EIB KNX IP Router
5
Programming button and LED
For assignment of the physical address
Function button
Switch to manual function or execute to the
factory reset
Temperature
Operation
–5 °C ... + 45 °C
Storage
–25 °C ... + 55 °C
Transport
– 25 °C ... + 70 °C
Relative
humidity
5%~93% (non-condensing)
Design
Modular installation device, on 35mm mounting rail
Dimensions
90 mm×36 mm×71mm
Weight
0.1KG
Housing, colour
Plastic PA66 housing, grey
Protection
IP 20, to EN 60529
CE mark
In accordance with EMC and low voltage guidelines
Markings
KNX/EIB

KNX/EIB KNX IP Router
6
2.2 Dimension diagram
1 SU = 18mm
2.3 Connection diagram

KNX/EIB KNX IP Router
7
Number
Element
Indication Description
1
Bus State IP LED
(Main line)
Green on: IP line OK
Orange on: Manual overwrite active
Off: IP line error or not connected
2
Bus State TP LED
(Sub line)
Green on: Sub line line OK
Off: Sub line not connected
3
Traffic on IP LED
(Main line)
Green blinking: Telegram traffic extent indicated
Off: No telegram traffic
4
Traffic on TP LED
(Sub line)
Green blinking: Telegram traffic extent indicated
Red blinking: Transmission error
Off: No telegram traffic
5
GA LED (Group Address
Routing)
Green on: Filter table active
Orange on: Route all
Red on: Block all
Off: Routing of Group Telegrams is different on main line
and sub line
6
PA LED (Physical
Address Routing)
Green on: Filter table active
Orange on: Route all
Red on: Block all
Off: Routing of Physical telegrams is different on main line
and sub line
7
Programming LED
Red on: device in boot mode or addressing mode ;
Red blinking: No IP connection
Upon receiving the physical address the device
automatically returns from addressing mode to normal
operating mode.
A
Ethernet connector
B
Function button
During normal operation a rather short press (≈3 sec)
activates and deactivates the Manual Function.
A long press (≈15 sec) soon followed by a short press (≈3
sec) executes the Factory Reset. After the second press,
all parameters will be set to factory default (incl. Individual
Address)
C
Programming button
Learning button for switching between normal operating
mode and addressing mode for assigning the physical
address
D
KNX-Bus connection

KNX/EIB KNX IP Router
8
Chapter 3 Planning and Application
According either to the factory default settings or the latest parameter settings downloaded
from ETS (also other tools) in normal operating mode the IP Router operates as it is supposed to.
The IP Router features two different modes, the “Normal Mode” and the “Boot Mode”.
3.1 Operation Modes
3.1.1 LED indication
Refer to the description in section 2.3 above.
3.1.2 The Function Button
The function button is used for two purposes; either to switch to manual function or to do a
factory reset. It depends on the current operation mode of the IP Router and the duration of time
this button is being pressed.
3.1.2.1 Switch to Manual function
Long press (≈3 sec) in “Normal Mode”
The default function is set by the LAN line and the (KNX) line parameters. Manual function is
configured in “General parameters”.
Note: The latest downloaded settings (parameters) and filter table are still available after
switching back from “Manual operation” to “Normal operation”.

KNX/EIB KNX IP Router
9
3.1.2.2 Factory Reset
Very long press (≈15s) in “Normal Mode”
A factory reset is carried out by pressing the button for about 15 seconds (Bus State IP/TP
LED light orange). After release, pressing it again for 3 seconds resets all the parameters to factory
default (incl. physical address). Subsequently, LED indicate normal operation again.
3.1.3 The Programming Button and LED
In “Normal Mode”:
To download the desired physical address and/or a full ETS settings download the
programming button needs to be pressed. Successive pressing on the programming button will
lead to turn on and off the programming LED, i.e. LED 7 which is lighting red. The blinking red
programming LED indicates that the Ethernet cable is not properly connected.
The boot mode, which is entered by a wed front-end, is used to upgrade the firmware program.
See Chapter 5 for details.
3.2 IP router application
In network installations IP Router is used as KNX IP line/area coupler to couple KNX IP and
KNX TP. After connecting to KNX TP, IP Router operates with its default settings. Setting the
correct physical address is necessary to include IP Router in the present KNX bus system. Only
physical addresses x.y.0 are allowed to be set.

KNX/EIB KNX IP Router
10
3.2.1 KNX Telegrams in the IP Network
The IP Router sends telegrams from/to the KNX to/from the IP network in accordance with
the KNXnet/IP protocol specification. According to the default setting these telegrams are sent as
multicast telegrams to the multicast IP address 224.0.23.12 port 3671. The multicast IP address
224.0.23.12 is the defined address for the KNXnet/IP from the KNX Association in conjunction
with the IANA. This address should be preserved and used as defined. Only if it becomes
necessary due to the existing network, it could be changed in the “General Parameters” as
described in KNX Multicasting Address. During commissioning, it is important to note:
All KNX IP devices that are intended to communicate with each other via IP network
must have the same IP multicast address
Multicast IP address 224.0.23.12 may need to be changed corresponding to the type of
network and the setting of the network components
IGMP (Internet Group Management Protocol) is used for the IP configuration to establish
multicast group memberships
If the IP address is changed from the IP side, it may sometimes happen that the ETS
does not recognize the device anymore and the connection can no longer be established
(tunneling uses IP address)
As a precaution, always run a restart or change the address from the TP side
Please ask your administrator if problems occur for the IP Address assignment
According to the topology, the additional physical addresses (for tunneling) always have
to be assigned in the range of sub line addresses. For more information about the
additional tunneling addresses please refer to Tunneling addresses (Additional Phys.
Addresses).
If a KNX/USB or KNX/IP interface is used to program a device of another line connected
to a KNX IP Router, you should pay close attention to have the correct topology!

KNX/EIB KNX IP Router
11
3.2.2 The IP Router in a Network Installation
In a network installation the IP Router can either be used as a KNX area coupler or as a KNX
line coupler.
3.2.3 The IP Router as an Area Coupler
The IP Router can replace an area coupler in a KNX network. For this purpose it must receive
the physical address of an area coupler (X.0.0, 1≤X≤15). In the ETS up to 15 areas can be defined
with area couplers.
3.2.4 The IP Router in a Mixed System
If it is necessary in a KNX system to use the IP Router at one point as an area coupler, e.g.
office or home complex, and at another point as a line coupler, e.g. a remote underground garage
or a pool; this is possible. It is only necessary to ensure that the IP Router used as a line coupler
uses a line coupler address from a free addressing area. The following picture best illustrates the
topology with IP Router routers as area and/or line couplers. Special attention needs to be paid
that if a IP Router area coupler with address “1.0.0” already exists in the installation, no other IP
Router line coupler (or any other KNX IP router) with address “1.X.0, 1≤X≤15” is allowed to be used
in that network, and of course vice versa, if a IP Router line coupler with address “1.1.0” already
exists in the installation, no other IP Router area coupler (or any other KNX IP router) with address
“1.0.0” is allowed to be used in that network.
A direct connection between two IP Routers is possible as well. In this case, the auto IP will
assign each IP Router an IP address and the two IP Routers will communicate over either a normal
or a crossed network cable.

KNX/EIB KNX IP Router
12
Mixed system
IP-L: Backbone (IP) line
KNX-L: KNX line
AC: Area Coupler
LC: Line Coupler
ML: Main line
SL: Sub line

KNX/EIB KNX IP Router
13
3.2.5 The IP Router as A Line Coupler
The IP Router of a KNX network can assume the functionality of a line coupler. For this
purpose it must have the physical address of a line coupler (X.Y.0, 1≤X & Y ≤15). In the ETS up to
225 lines can be defined (from 1.1.0 to 15.15.0).
When the coupler receives telegrams (for example during commissioning) that use physical
addresses as destination addresses, it compares the physical addresses of the receiver with its
own physical address and then decides whether it has to route the telegrams or not.
Due to telegrams with group addresses the coupler reacts in accordance with its parameter
settings. During normal operation (default setting), the coupler only routes those telegrams whose
group addresses have been entered in its filter table.
If the coupler routes a telegram and does not receive an acknowledgement, or if a bus device
discovers a transmission error, the coupler repeats the telegram up to three times (depending on
the corresponding parameter that is set to the device through the last ETS download). With the
parameters „Repetitions if errors...“, this behaviour can be set separately for both lines. These
parameters should stay with the default setting.
The ETS does not provide an unload procedure for the application of the IP-Router !
In the following description we describe parameters using screenshots created in the ETS.

KNX/EIB KNX IP Router
14
Chapter 4 Parameter setting description in the ETS
All screen shots in this chapter represent the IP Router´s database entry in ETS.
4.1 Physical Address Assignment
Fig.4.1: Properties window
To download the desired physical address and/or a full ETS setting into the device, during the
procedure the programming button needs to be pressed.
(The programming button is used to put the device into “Program Mode”). With the ETS the
physical address can be assigned to the device by setting the desired address in the properties
window of the ETS, starting the download and pressing the programming button. After assignment
the device restarts itself. (A blinking red LED 5 indicates that the Ethernet cable is not properly
connected.)
To commission the device a PC with ETS and an interface connection (IP, USB) to the data
bus is required.

KNX/EIB KNX IP Router
15
4.2 General
Fig. 4.2: General
ETS-Text
Selection
Comment
Host name
KNX IP Router
Field to enter the device name (30 signs
max.) providing an easy search of the
device with the ETS or with a KNXnet/IP
visualization system.
Slow tunneling
connections
support
Yes
No
Enable to support slow tunneling
connections.
Switch-off time for
Manual Function
10min,1hour,4hours,8hours
After expiry of this time period the Manual
Function is switched off automatically.
Manual Function
Disabled
Pass all telegrams
Pass all physical telegrams
Pass all Group telegrams
Configuration setting for telegram routing
when the Manual Function is active.
Please note that commissioning straight at delivery status (default settings) means:
①The IP coupler does block all telegrams because the filter table is not defined
②The fall-back time after manual operation is 120 min
③The physical address is 15.15.0.

KNX/EIB KNX IP Router
16
4.3 IP Configuration
Fig 4.3: IP configuration
ETS-Text
Selection
Comment
HTTP port
80
8080
Select one of the two official system ports.
DHCP
Do not use
Use
If DHCP is not used, following parameters are to
be set (see table below).
If DHCP is used, no further IP parameters have
to be set.
IP address
0-255.0-255.0-255.0-255
IP Byte 1 to 4: manual input.
Subnet mask
0-255.0-255.0-255.0-255
SM Byte 1 to 4: manual input.
Default gateway
0-255.0-255.0-255.0-255
DG Byte 1 to 4: manual input.
DNS server
0-255.0-255.0-255.0-255
DNS Byte 1 to 4: manual input.

KNX/EIB KNX IP Router
17
4.4 KNX Multicasting Address
The multicast address 224.0.23.12 is the defined address for the KNXnet/IP from the KNX
Association in conjunction with the IANA. This address shall only be changed if it becomes
necessary due to the existing network.
Fig. 4.4: KNX multicast address
ETS-Text
Range
Comment
System multicast
Do not use
Use
If “do not use” is selected, the
address is to be defined physically.
If “use”, the system multicast is
224.0.23.12
Byte 1
(of the IP routing multicast address)
This range is reserved for the
IP multicast address.
System: [224]
Physical: [239]
If System multicast address is used,
"224" is permanently set.
If Physical multicast address is used,
"239" is permanently set.
Byte 2 [0 - 255]
(of the IP routing multicast address)
0-255
Can only be set manually if a physical
multicast address is used.
Byte 3 [0 - 255]
(of the IP routing multicast address)
0-255
Can only be set manually if a physical
multicast address is used.
Byte 4 [0 - 255]
(of the IP routing multicast address)
0-255
Can only be set manually if a physical
multicast address is used.
Note: During commissioning it should be regarded that all KNX IP devices intended to
communicate with each other via IP must use the same IP routing multicast address. To ensure
proper functioning, execute a manual restart after changing the multicast address.