Use direct IP connection when available
If this option is activated, direct IP connections to IP devices will be established in order to execute online operations (e.g. a direct device download via IP). For this purpose, a so-called device “discovery” is carried out at the beginning in which elementary device properties (SN, KNX Secure status, etc.) are queried online.
- The device is found via IP, i.e. ETS and IP device communicate with the same Multicast address.
- The KNX Serial Number of the device found matches the device in the project (if the KNX Serial Number of the device is available in the project)
- In this mode...
- ... telegram recordings are not possible.
- ... the local address of the connection matches that of the device to be loaded.
- Devices without KNX Secure (i.e. also KNX Secure devices with KNX Secure disabled on the device) are loaded unsecured via IP.
- Devices with KNX Secure enabled are loaded securely via IP.
- Enabled KNX Secure online found on the device (feedback from the discovery) - Use of the associated security passwords (if available) from the ETS project for this device, otherwise no download.
- Enabled KNX Secure on the device found in the project (status on the device) - Use of the associated security passwords (must be available) from the ETS project for this device.
Use project connection if defined
When this option is selected, the default project connection is selected. The default project connection is only used by the project and is not used by the bus or group monitoring.
- ETS uses a user-defined, project connection for bus operations instead of the connection under Currently Selected.
- If no project connection is specified in an active project, the connection specified under Currently Selected is used.
- If a project connection is specified in an active project but is not available, the user will be warned.
See below for information on the priority when using interfaces.
- The specified connection found in the bus/connection tab under Currently Selected will be used.
Disconnect connection after use
When this option is enabled, all online connections used (e.g. in the monitor) are closed immediately after completion of the "online" operation. Consequently, they are immediately available for any other possible ETS online function. This prevents the ETS message stating that the interface is (still) in use (because it was not explicitly closed by the ETS user) even though the actual ETS function has long since been completed.
KNX interfaces of the first generations require more time for connection setup due to system constraints (boot-up time). For interfaces like this, it is helpful to disable this option; in this case, the connection is kept open (the voltage supply from the (PC) USB Client page is not switched off).
If the option is enabled, on Tunneling connections a so called "heartbeat" serves for the "keep alive" of current connection (no new connection request needed, performance asset). Valid for UDP and also (secure) TCP connections.
Port Usage Priority
ETS uses three priority levels for selecting bus connections, provided they are defined:
- PRIO0: If active, a direct KNX IP connection will be used for downloading for detected IP devices (no tunneling and therefore faster).
- PRIO1: line connections, offer the possibility to establish a line connection and parallel downloading.
- PRIO2: project connections, which shall be defined in the topology root element.
- PRIO3: the currently selected connection as defined in the settings.
The priority rules imply, that a project oriented connection can be replaced by a line oriented connection. These priority rules imply that project connections can be overruled by line connections, but they do not imply that if one of these connections is currently not available, there will be an automatic switch* to a different (available) connection.
* There would be a risk here that a connection via another available (PRIO3) connection could unintentionally download the project to a completely different installation.