Page Comparison

...

Info
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)

Image Added

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 KNX IP Router 752 secure 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.