ETS configuration of router

Interface settings with ETS

Within the ETS KNX interfaces can be selected and set up via the ETS menu "Bus Interfaces".

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 NETx KNX IP Secure Router 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. 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 1.1.0 (address within ETS topology)
Connection 1 1.1.240 (1. additional address)
Connection 2 1.1.241 (2. additional address)
Connection 3 1.1.242 (3. additional address)
Connection 4 1.1.243 (4. additional address)
Connection 5 1.1.244 (5. additional address)
Connection 6 1.1.245 (6. additional address)
Connection 7 1.1.246 (7. additional address)
Connection 8 1.1.247 (8. additional address)

The section “Individual Address” enables you to select the individual KNX address of the currently used KNXnet/IP tunneling connection.

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.

ETS database

The ETS database (ETS 5.7 or higher) can be downloaded via the KNX online catalog.

If the first product is inserted into a project with KNX Security, the ETS prompts you to enter a project password.

This password protects the ETS project from unauthorized access. This password is not a key that is used for KNX communication. The entry of the password can be bypassed with "Cancel", but this is not recommended for security reasons.

ETS requires a device certificate for each device with KNX Security that is created in the ETS. This certificate contains the serial number of the device as well as an intangible key (FDSK = Factory Default Setup Key).

The certificate is printed as text on the device. It can also be conveniently scanned from the printed QR code via a webcam.

The list of all device certificates can be managed in the ETS Overview - Projects - Security window.

This initial key is required to safely put a device into operation from the start. Even if the ETS download is recorded by a third party, the third party has no access to the secured devices afterwards. During the first secure download, the initial key is replaced by the ETS with a new key that is generated individually for each device.

This prevents persons or devices who may know the initial key from accessing the device. The initial key is only reactivated after a master reset.

The serial number in the certificate enables the ETS to assign the correct key to a device during a download.

In the ETS, some settings are displayed in addition to the parameter dialog in the properties dialog (at the edge of the screen). The IP settings can be made here. The additional addresses for the interface connections are displayed 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.

By clicking on the 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.

If secure tunneling is activated, a unique password will be created automatically for each tunnel. These passwords can be displayed under the "Settings" overview, when a tunnel is selected.

Within the "IP" overview the IP network specific options of the router 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.

Parameter	Description
IP address	Here the IP address of the NETx KNX IP Secure Router 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.
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 NETx KNX IP Secure Router.

IP address of the PC: 192.168.0.30
Subnet of the PC: 255.255.255.0

The NETx KNX IP Secure Router 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.0.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 KNX IP Router 192.168.0.10
Subnet of the KNX IP Router: 255.255.255.0

ETS parameter dialogue

The following parameters can be set using the ETS.

General settings

Parameter

Description

Prog. mode on 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)

Parameter	Description
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)

Parameter	Description
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 KNX 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. 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.
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.

Programming

The NETx KNX IP Secure Router can be programmed in different ways by the ETS:

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 direct IP connection

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.