1.KNX connection
The interface used by the HS/FS to communicate with the KNX is defined on this input screen. The parameters for the iETS access can also be set.
KNX® by KNX Association cvba
KNX® by KNX Association cvba
Important
No automatic detection of the interface used!
- BCU2 / FT1.2
- S&P
- KNXnet/IP routing (without KNX Secure support)
- BCU2 / FT1.2 -compatibility mode-
- USB (until 2019, without KNX Secure support)
- USB (without KNX Secure support)
- KNXnet/IP routing (with KNX Secure support)
- KNXnet/IP tunnelling (with KNX Secure support)
- USB (with KNX Secure support)
The following list contains all supported interfaces. In addition, the additional options available on the input screen are specified for each interface.
The option to limit the telegrams to a certain number is available for all interfaces!
The option to limit the telegrams to a certain number is available for all interfaces!
| Interfaces | Available settings |
|---|---|
| BCU2 / FT1.2 Supported data interfaces:
Note In rare cases, the BCU2 must be separated from the KNX once after the BCU2/FT1.2 mode is used. For this purpose, the HS/FS must be reconfigured with this mode; wait until the HS/FS has started (3x dual tone sounds), now switch off the HS/FS and disconnect the BCU2 from the KNX for approx. 60 seconds. Then reconnect to the KNX and restart the HS/FS. The connection cable between the HS/FS and the BCU does not need to be disconnected for this purpose. | |
| S&P Supported data interfaces:
| |
| KNXnet/IP routing (without KNX Secure support) Supported data interfaces:
| |
| BCU2 / FT1.2 -compatibility mode- Supported data interfaces:
| |
| USB (until 2019, without KNX Secure support) Supported data interfaces:
| |
| USB (without KNX Secure support)Supported data interfaces: Supported data interfaces:
| |
| KNXnet/IP routing (with KNX Secure support) Supported data interfaces:
| |
| KNXnet/IP tunnelling (with KNX Secure support) Supported data interfaces:
| |
| USB (with KNX Secure support)Supported data interfaces: Supported data interfaces:
| - |
Yes: The HS/FS limits the sending rate to the value that can be set in the following field.
No: The HS/FS sends a maximum of 20 telegrams per second on the KNX.
No: The HS/FS sends a maximum of 20 telegrams per second on the KNX.
Important
The address must be unique within the KNX installation!
- KNXnet/IP tunneling
The physical address of the KNXnet/IP tunneling interface, which is configured in the ETS, must be entered here. - KNXnet/IP routing (with and withoutKNX Secure support)
The HS/FS uses the address entered here as the sender address. The address must correspond to the physical address of the dummy application in the ETS. - BCU2 (new mode)
The HS/FS sets the connected BCU to the physical address set here. Any existing address is overwritten in the process. - USB (without KNX Secure support)
The physical address configured in the ETS must be entered here.
The multicast address and IP port for KNXnet/IP routing are defined here.
You can find the IP router settings in your ETS project.
The default multicast address is: 224.0.23.12 The default IP port is: 3671
You can find the IP router settings in your ETS project.
The default multicast address is: 224.0.23.12 The default IP port is: 3671
The IP address and IP port for KNXnet/IP tunnelling are specified here.
You can find the IP router settings in your ETS project.
The default IP port is: 3671
You can find the IP router settings in your ETS project.
The default IP port is: 3671
The password for the commissioning of IP Secure may be found at your ETS project.
The authentication code for the commissioning of IP Secure may be found at your ETS project.
When projecting a static IP address, the given link directly opens the page for managing the key ring in the browser.
The page can generally be reached at the following address:
The page can generally be reached at the following address:
https://[HS-IP]/hsknxkeys2.Activating support for iETS
Note
The support of iETS depends on the set interface!
Yes: The programming of the KNX system can be carried out with the iETS client. The HS/FS is then the iETS server. The iETS Client is available as an app for ETS5.
Note
During programming with the iETS client, the HS/FS continues to operate, KNX switching processes are carried out and KNX status changes are detected.
Install the current version of the ETS!
Programming was tested with ETS5 V5.6.6 using the EIBlib/IP-ETSApp, ETS3 V1.00 and ETS 2 V1.13.
Install the current version of the ETS!
Programming was tested with ETS5 V5.6.6 using the EIBlib/IP-ETSApp, ETS3 V1.00 and ETS 2 V1.13.
iETS Port 1, standard: 50000.
The port used here must match the settings of the iETS Client.
Some reserved ports must not be used!
The port used here must match the settings of the iETS Client.
Some reserved ports must not be used!
iETS Port 2, standard: 50001:
The port used here must match the settings of the iETS client.
Some reserved ports must not be used!
The port used here must match the settings of the iETS client.
Some reserved ports must not be used!
iETS Port 3, standard: 50002.
The port used here must match the settings of the iETS Client.
Some reserved ports must not be used!
The port used here must match the settings of the iETS Client.
Some reserved ports must not be used!
Yes: The access can be limited via a network address and net mask. iETS clients must then come from the address range configured further below.
No: There is no restriction as to the address range from which the iETS client conducts access.
No: There is no restriction as to the address range from which the iETS client conducts access.
IP/network address of the client which is to be granted access (see also this Wikipedia entry).
Net mask of the client which is to be granted access (see also this Wikipedia entry).
The iETS access can be enabled with this communication object assigned here.
If this object has the value 1, then it is possible to work with the iETS via the HS/FS.
If this object has the value 1, then it is possible to work with the iETS via the HS/FS.
This communication object assigned here has the value 1 if iETS access takes place. Otherwise the value is zero.