General

Mode: This section displays the KNX connection mode. By default, the controller comes with a built-in TP-UART interface. The various modes include:

TP-UART: This is a twisted pair connection via a black/red plug. It has a transfer rate of 9.6 kB/s.
EIBnet/IP tunneling: This is an IP connection that is 1,000 times faster than TP-UART. In this mode, the controller behaves as a server, allowing unicast and acknowledged data exchange, with an additional individual address per tunneling connection.
EIBnet/IP tunneling (NAT mode): Also known as Network Address Translation mode, this allows multiple devices to connect to the public network using the same public IPv4 address. It modifies the IP address information in the IPv4 headers while in transit across a traffic routing device.
EIBnet/IP routing: This mode allows multicast and unacknowledged data transfer. In this mode, the controller behaves as a line or a backbone coupler.
ACK all group telegrams: If the controller communicates directly with another KNX device, it has to acknowledge received telegrams. Unselect this option if the controller operates as a sniffer of group addresses only.

KNX address: This is the individual KNX address of the device.

Enable IP routing: This option allows the receiving/sending of telegrams from/to IP routing (multicast).

Pass individual telegrams via IP routing: This option allows the receiving/sending of individual telegrams from/to IP routing. You must also enable IP routing (for example, for commissioning KNX devices).

Accept IP tunneling connections: This option allows the acceptance of IP tunneling (unicast) connections. This is most often used for commissioning from ETS or diagnostics. For example, you can also create a tunnel from a second controller in IP tunneling mode.

Multicast IP: This is the Multicast IP address.

Multicast TTL: The default value is 1, which allows communication between different sub-networks.

Maximum telegrams in queue: This is the count of maximum telegrams in the queue.

TOS priority level: This is the priority of KNX telegrams, ranging from 0 to 7.

Backbone key (encryption): This is the backbone key for decrypting secured telegrams for IP routing. The backbone key can be exported from ETS software in Reports → Project security. You can import the backbone key during the KNXPROJ import process.

Enable only secure communication: This option disables tunnelling and non-secure routing.

NOTE: The device will reboot after applying the changes.