EAE IPR200 KNX IP Router Instruction Manual

EAE IPR200 KNX IP Router

Product Information

Specifications

• Power Supply: DC 21-30V SELV, 15 mA
• Connections: RJ45 socket, Bus connection terminal
• Ethernet: 10Mbit/s
• Supported Protocols: ARP, ICMP, IGMP, UDP/IP, DHCP, Auto IP
• KNX Line: KNX bus approx…
• KNX IP Tunneling Connections: 5 simultaneous connections
• Operating Temperature Range: 0-31 degrees Celsius
• Degree of Protection: IP20
• Dimensions: Width in units (18 mm modules)
• Weight: 40g
• Housing: Plastic (PC)

Product Usage Instructions

Installation and Connection
The KNX IP Router 200 is designed for installation on a DIN rail with a width of 1 unit (18mm). It features various controls and displays such as:

• KNX Bus Connector
• LED for Programming Mode (red)
• Button for Programming Mode
• LED KNX (multicolor)
• LED Mode (multicolor)
• LED IP (multicolor)
• Button Pass GAs
• Button Pass IAs
• Ethernet/LAN Connector

The KNX IP Router 200 is powered by the KNX bus. Ensure the KNX bus power is active for the device to function properly.

KNX Programming Mode
The KNX programming mode can be activated/deactivated by pressing the flushed KNX programming button or by simultaneously pressing specific buttons as indicated in the manual.

Status Display
The KNX LED lights up green when powered by the KNX bus and flickers to indicate telegram traffic. Communication failures are indicated by a short change of LED color to red.

General

• The KNX IP Router 200 allows forwarding of telegrams between different lines (TP) through a LAN (IP) as a fast backbone (KNXnet/IP Routing). The KNX IP Router can also be used as an router for accessing the bus via IP (KNXnet/IP Tunneling).
• The device supports 5 simultaneous KNXnet/IP Tunneling connections.
• The IP address can be obtained by a DHCP server or by manual configuration (ETS) respectively. Power is supplied via the KNX bus.

Technical Data

Bus connection terminal

Ethernet| 10 Base T| 10Mbit/s
| Supported internet protocols| ARP, ICMP, IGMP, UDP/IP, DHCP and Auto IP
| KNXnet/IP Tunneling connections| 5
KNX| Medium| IP/TP
| Extended filter table for main group| 0…31
| Interface protocols| cEMI
| Max. APDU length| 55
| Device model| 0x091A
Display elements| LED KNX (Multicolor) LED Mode (Multicolor) LED IP (Multicolor)

LED RED for program. mode

|
Operating elements| 2 Function Button

Programming Button

|
Installation| DIN rail mount|
Type of protection| IP20| EN 60529
Degree of Pollution| 2| IEC 60664-1
Overvoltage class| III| IEC 60664-1
Temperature range| Operation| -5° C + 45° C non-condensing
| Storage| -25° C + 70° C
Humidity| | %5 to 93 % no moisture condensation
Dimensions| Width W in units (18 mm modules)|
Weight| 40 g|
Box| Housing plastic (PC)|

CE

| §   EMC directive 2014 / 30 / EU

§   RoHS directive 2011 / 65 / EU

§   EN 63000: 2018

EN 63044-3: 2018

| §   EN 50491-5-1: 2010

EN 50491-5-2: 2010

EN 50491-5-3: 2010

§   EN 61000-6-2: 2019

EN 61000-6-3: 2007 + A1: 2011

NOTE : Device default physical address is 15.15.255. In order to configure KNX Presence detector, ETS application file “.knxprod” is needed. It’s possible to download the file on EAE website. ETS is required for programming the device. Parameter settings and related group addresses can be changed by ETS. Learn more by reading ETS help file.

Installation and Connection
The KNX IP Router 200 is designed for installation on a DIN rail with a width of 1 unit (18mm). It features the following controls and displays:

1. KNX Bus Connector
2. LED for Programming Mode (red)
3. Button for Programming Mode
4. LED KNX (multicolor)
5. LED Mode (multicolor)
6. LED IP (multicolor)
7. Button Pass GAs
8. Button Pass IAs
9. Ethernet/LAN Connector

The KNX IP Router 200 is powered by the KNX bus. An external power supply is not necessary. The device is not working without KNX bus power.

KNX Programming Mode
The KNX programming mode is activated/deactivated either by pressing the flushed KNX programming button ❸ or by simultaneously pressing the buttons ❼ and ❽.

Status display
The KNX LED ❹ lights up green if the device is successfully powered by the KNX bus. This LED indicates telegram traffic on the KNX bus by flickering.
Communication failures (e.g. repetitions of telegrams or telegram fragments) are indicated by a short change of the LED color to red.
Overview of the different indications of the KNX LED ❹:

The IP LED ❻ lights up when an Ethernet link is active. This LED is green if the device has valid IP settings (IP address, Sub net and Gateway). With invalid or nonexistent IP settings the LED is red. This is also the case if e.g. the device has not yet received the IP settings by a DHCP server. This LED indicates IP telegram traffic by flickering. Overview of the different indications of the IP LED ❻:

settings.
LED lights red| The device has an active Ethernet link and invalid IP settings or not

yet received the IP settings by a DHCP server.

LED flickers green| IP telegram traffic

• For testing purposes (for example, during commissioning) the configured routing settings (filter or block) can be bypassed via manual operation.
• With the button Pass GAs ❼ the forwarding of group addressed telegrams can be activated.
• With the button Pass IAs ❽ the forwarding of individually addressed telegrams can be activated.
• This is visualized with a single flash of the Mode LED ❺ (orange). If both modes are activated the Mode LED ❺ flashes two times.
• Pressing button Pass GAs ❼ or button Pass IAs ❽ again these settings can be selected and deselected on demand. Via the Escape function (Esc) the manual operation can be stopped by simultaneously pressing the buttons Pass GAs ❼  and Pass IAs❽.
• If neither programming mode nor manual mode are active the LED ❺ can visualize configuration errors.

Overview of the different indications of the Mode LED:

LED flashes 1x orange

| Programming mode is not active. Manual operation is active.

Forwarding IA or GA

LED flashes 2x orange

| Programming mode is not active. Manual operation is active.

Forwarding IA and GA

LED flashes red

| Programming mode is not active. Manual operation is not active.

The device is not properly loaded e.g.

after an interrupted download.

Factory Default Settings

Factory default configuration

Individual device address| 15.15.255
Number of configured KNXnet/IP tunneling configuration| 1
Individual address of tunneling configuration| 15.15.250
IP address assignment| DHCP

Reset to factory device Settings

It is possible to reset the device to its factory settings:

• Disconnect the KNX Bus connector ❶ from device
• Press the KNX programming button ❸ and keep it pressed down
• Reconnect the KNX Bus connector ❶ of device
• Keep the KNX programming button ❸ pressed for at least another 6 seconds
• A short flashing of all LEDs (❷❹❺❻) visualizes the successful reset of the device to factory default settings.

Interface settings with ETS

• Within the ETS KNX router can be selected and set up via the ETS menu “Bus router”
• The ETS can access configured KNX IP Routers even without a database entry. If the setup of the KNX IP Router does not comply with the conditions of the KNX installation it must be configured via an ETS project. See the ETS database section for more information.
• As factory default the assignment of the IP address is set to “automatically via DHCP” and thus no further settings are necessary. To use this feature a DHCP server on the LAN must exist (e.g. many DSL routers have an integrated DHCP server).
• After connecting the KNX IP Router to the LAN and the KNX bus, it should automatically appear in the ETS within the menu “Bus” under “Discovered interfaces”.
• By clicking on the discovered interface it is selected as the current interface. On the right side of the ETS window all specific information and options of the connection appear.
• The indicated device name and the “Host Individual Address” (individual address of the device) can be changed within your ETS project then.
• Like all programmable KNX devices the KNX IP Router 200 has an individual address which can be used to access the device. This is used, for example, of the ETS when downloading to the KNX IP Router via the bus.
• For the interface function the device contains additional individual addresses that can be set in the ETS (ETS 4.2 or higher). When a client (e.g. ETS) sends via the KNX IP Router telegrams to the bus, they contain a sender address as one from the additional addresses. Each address is associated with a connection. Thus response telegrams can be clearly transmitted to the respective client.
• The additional individual addresses must be selected from the address range of the bus line in which the interface is installed and may not be used by another device.

Example:

Device address

|

15.15.255

|

(address within ETS topology)

---|---|---
Connection 1| 15.15.2| (1. additional address)
Connection 2| 15.15.3| (2. additional address)
Connection 3| 15.15.4| (3. additional address)
Connection 4| 15.15.5| (4. additional address)
Connection 5| 15.15.6| (5. additional address)

The section “Individual Address” enables you to change the individual KNX address of the currently used KNXnet/IP Tunneling connection. To check if the address you want to assign is unique within your KNX installation you can click the button “Address free?”

The individual KNX device address and the individual KNX addresses for additional tunneling connections can be changed within the ETS project, after the device has been added to the project.

Coupler function (KNXnet/IP Routing)

The KNX IP Router 200 operates as a line or backbone coupler. In both cases, the LAN (IP) is used as a backbone.

The following table shows the application possibilities of the KNX IP Router compared to the classic topology:

| Classical Topology (without IP)| IP coupling of areas (IP

area coupl.)

| IP coupling of lines (IP

line coupler)

---|---|---|---
Area (Backbone)| TP| IP| IP
Coupling| KNX Line Coupler (max. 15 Pcs.)| KNX IP Router (max. 15 Pcs.)| Directly via LAN Switch
Main line| TP| TP| IP
Coupling| KNX Line Coupler

(max. 15×15 Pcs.)

| KNX Line Coupler

(max. 15×15 Pcs.)

| KNX IP Router

(max. 225 Pcs..)

Line| TP| TP| TP

The individual address assigned to the KNX IP Router 200 determines whether the device operates as a line or area coupler. If the individual address is in the form of x.y.0 (x, y: 1..15), the router operates as a line coupler. If it is in the form of x.0.0 (x: 1..15), the router acts as a backbone coupler.

• If the KNX IP Router 200 is used as a area coupler (x.0.0), there must not be a KNX IP Router in the topology beneath it. For example, if a KNX IP Router has the individual address 1.0.0, there must be no KNX IP Router with the address 1.1.0.
• If the KNX IP Router 200 is used as a line coupler (x.y.0), there must not be a KNX IP Router in the topology above it. For example, if a KNX IP Router has the individual address 1.1.0, there must be no KNX IP Router with the address 1.0.0.

• The KNX IP Router has a filter table and thus contributes to reducing the bus load. The filter table (8kB) supports the extended group address range and is automatically generated by the ETS.
• Because of the speed difference between the Ethernet (10 Mbit/s) and KNX TP (9.6 kbit/s), a far greater number of telegrams can be transmitted on IP. If several consecutive telegrams are transmitted for the same line, they must be buffered in the router to avoid telegram loss. The KNX IP Router 200 has a memory for 150 telegrams (from IP to KNX).

ETS Database

The ETS database (for ETS 4.2 and ETS 5) can be downloaded from the product website of the KNX IP Router 200 (www.eaetechnology.com).
When using the ETS® product database for ETS 4 / 5 some settings are displayed in addition to the parameter dialog of the Properties dialog (on the right side of the ETS window). So the IP settings can be done here. In the ETS 4 also the additional individual addresses will appear. In the ETS 5 those addresses appear in the topology view.

Each individual KNX address can be changed by clicking on the list entry and typing in the desired address into the “Individual Address” text field. If the text field frame switches to color red after entering the address, the address is already taken within your ETS project.

Make sure that none of the addresses above are already present in your KNX installation.
If the physical KNX addresses of the tunneling connections have been assigned via the ETS project, a manual address setting on the device is not allowed.

• By clicking on the KNX IP Router 200 device entry within your ETS projects topology view, an information column ‘Properties’ will appear on the right side of the ETS window. Within the ‘Settings’ overview, you can change the name of the device.
• Within the “IP” overview the IP network-specific options of the KNX IP Router 200 can be changed.
• By changing “obtain an IP address automatically (via DHCP)” to “Use a static IP address” (static IP address) the IP address, subnet mask, and default gateway can be set freely.

All changes in the properties menu become effective only after a successful application download.

IP Address
Here the IP address of the KNX IP Router 200 can be entered. This is used to address the device via the IP network (LAN). The IP addressing should be coordinated with the administrator of the network.

Subnet Mask
Enter the subnet mask here. The device uses the values entered in this mask to determine whether there is a communication partner in the local network. If there is no partner in the local network, the device will not send the telegrams directly to the partner but to the gateway that routes the telegram.

Default Gateway
Enter the IP address of the gateway here, e.g. the DSL router of the installation

Routing Multicast Address
This address is used for routing telegrams on IP. The multicast IP address 224.0.23.12 was reserved (KNXnet/IP) at the IANA (Internet Assigned Numbers Authority) for this purpose. If a different multicast IP address is required, it must be within the range of 239.0.0.0 to 239.255.255.255.

Example of assigning IP addresses

A PC is to be used to access the KNX IP Router 200

IP address of the PC| 192.168.1.30
A subnet of the PC| 255.255.255.0

The KNX IP Router 200 is located in the same LAN, i.e. it uses the same subnet. The subnet constrains the IP addresses that can be assigned. In this example, the IP address of the KNX IP Router must be 192.168.1.xx, where xx can be a number from 1 to 254 (with the exception of 30, which is already taken by the client PC). It must be ensured that no IP addresses are assigned twice.

IP address of the IP Router:| 192.168.1.31
Subnet of the IP Router:| 255.255.255.0

Multicast Address Change
Multicast address assignment can be configured.

ETS parameter dialogue

The following parameters can be set using the ETS.

General settings

Programming mode on the device front

In addition to the normal programming button ❸ the device allows activating the programming mode on the device front without opening the switchboard cover. The programming mode can be activated and deactivated via pressing simultaneously both buttons❼ and ❽ This feature can be enabled and disabled via the parameter “Prog. mode on device front”. The recessed programming button (❸next to the Programming LED ❷) is always enabled and not influenced by this parameter.

Manual operation on device

This parameter sets the duration of the manual mode. Upon completion the normal display mode is restored.

Routing (KNX - > IP) 

Group telegrams (main group 0 to 13)

Block:| No group telegrams of this main group are routed to IP.
Route:| All group telegrams of this main group are routed to IP independent of the filter table. This setting is for test purposes only.
Filter:| The filter table is used to check whether or not the received group telegram should be routed to IP.
Group telegrams (main group 14 to 31)

Block:| No group telegrams of main groups 14 to 31 are routed to IP.
Route:| All group telegrams of main groups 14 to 31 are routed to IP.
Filter:| The filter table is used to check whether or not the received group telegram should be routed to IP.
Individually addressed telegrams

Block:| No individually addressed telegrams are routed to IP.
Route:| All individually addressed telegrams are routed to IP.
Filter:| The individual address is used to check whether the received individually addressed telegram should be routed to IP.
Broadcast telegrams

Block:| No received broadcast telegrams are routed to IP.
Route:| All received broadcast telegrams are routed to IP.
Acknowledge (ACK) of group telegrams

Always:| A acknowledge is generated for every received group telegram (from KNX).
Only if routed:| A acknowledge is only generated for received group telegrams (from KNX) if they are routed to IP.
Acknowledge (ACK) of individually addressed telegrams

Always:| A acknowledge is generated for every received individual addressed telegram (from KNX).
Only if routed:| A acknowledge is only generated for received individually addressed group telegrams (from KNX) if they are routed to IP.

Answer           with NACK:

| Every received individually addressed telegram (from KNX) is responded to with NACK (Not acknowledge). This means that communication with individually addressed telegrams on the corresponding KNX line is not possible. Group communication (group telegrams) is not affected. This

setting can be used to block attempts at manipulation.

When using “Answer with NACK” an access to the device via KNX TP is no longer possible. The configuration must be performed via IP.

Routing (IP - > KNX)

Group telegrams (main group 0 to 13)

Block:| No group telegrams of these main groups are routed to KNX.
Route:| All group telegrams of this main group are routed to KNXG independent of the filter table. This setting is used for testing purposes only.
Filter:| The filter table is used to check whether the received group telegram should be routed to KNX.
Group telegrams (main group 14 to 31)

Block:| No group telegrams of main groups 14 to 31 are routed to KNX.
Route:| All group telegrams of the main groups 14 to 31 are routed to KNX.
Filter:| The filter table is used to check whether the received group telegram should be routed to KNX.
Individually addressed telegrams

Block:| No individually addressed telegrams are routed to KNX.
Route:| All individually addressed telegrams are routed to KNX.
Filter:| The individual address is used to check whether the received individually addressed telegram should be routed to KNX.
Broadcast telegrams

Block:| No received broadcast telegrams are routed to KNX.
Route:| All received broadcast telegrams are routed to KNX.
Repetition of group telegrams

Disabled:| The received group telegram is not resent to KNX in case of a fault.
Enabled:| The received group telegram is resent up to three times in case of a fault.
Repetition of individually addressed telegrams

Disabled:| The received individually addressed telegram is not resent to KNX in case of a fault.
Enabled:| The received individually addressed telegram is resent up to three times in case of a fault.
Repetition of broadcast telegrams

Disabled:| The received broadcast telegram is not resent to KNX in case of a fault.
Enabled:| The received broadcast telegram is resent up to three times in case of a fault.

Programing

Via KNX Bus
The device only needs to be connected to the KNX bus. The ETS requires an additional interface (for example, USB) to have access to the bus. Via this way both the individual address and the entire application including IP configuration can be programmed. Programming via the bus is recommended if no IP connection can be established.

Via KNXnet/IP Tunneling
No additional interface is required. Programming via KNXnet/IP Tunneling is possible if the device already has a valid IP configuration (e.g. via DHCP). In this case the device is displayed in the interface configuration of the ETS and must be selected. The download is executed via the ETS project as with many other devices.

Via KNXnet/IP Routing
Programming via KNXnet/IP Routing is possible if the device already has a valid IP configuration (e.g. by using DHCP or Auto IP). In the ETS, the routing interface appears if at least one device on the network which supports routing is available. The name of the network interface appears in the PC as description. If routing is selected as interface, the programming done from the ETS project as like with other devices. In this case LAN is used as a KNX medium like TP. There is no additional interface device required.

Via KNXnet/IP Routing
While KNXnet/IP Tunneling and KNXnet/IP Routing is limited to the speed of KNX TP the device can be loaded via a direct IP connection at high speed. The direct IP connection is possible if the device already has a valid IP configuration as well as an individual address. To do this select “Use direct IP connection if available” in the ETS menu “Bus – Connections – Options”. The download is then directly performed in the device and is not visible in the ETS group monitor.

Due to the significantly shorter transmission times it is recommended to perform downloads via IP.

WARNING

• The device must be mounted and commissioned by an authorized electrician.
• The prevailing safety rules must be heeded.
• The device must not be opened.
• For the planning and construction of electric installations, the relevant guidelines, regulations and standards of the respective country are to be considered.

www.eaetechnology.com

FAQ

Q: How can I obtain the IP address for the KNX IP Router 200?
A: The IP address can be obtained either through a DHCP server or by manual configuration using ETS.

Q: How many simultaneous KNXnet/IP Tunneling connections does the device support?
A: The device supports up to 5 simultaneous KNXnet/IP Tunneling connections.

References

• EAE Technology – KNX Akıllı Ev Sistemi, Aydınlatma Otomasyonu
• EAE Technology – KNX Akıllı Ev Sistemi, Aydınlatma Otomasyonu

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>