1.KNX connection
In this mask, the interface is defined via which the HS/FS communicates with the KNX. 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!
Interface
- BCU2/ FT1.2
- S&P
- KNXnet/IP routing (without KNX Secure support)
- BCU2/ FT1.2 -compatibility mode-
- USB (up to 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 option to limit the telegrams to a specific 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 (up to 2019, without KNX Secure support) Supported data interfaces:
| |
| USB (without KNX Secure support) 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:
| - |
Limit telegrams
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.
Physical address
Important
The address must be unique within the KNX installation!
- KNXnet/IP tunnelling
The physical address of the KNXnet/IP tunnelling interface configured in the ETS must be entered here, via which the connection is to be established. - KNXnet/IP routing (with and without KNX Secure support)
The address entered here is used as the sender address by the HS/FS. The address must match the physical address of the dummy application in the ETS. - BCU2 (new mode)
The HS/FS sets the connected BCU to the physical address specified 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.
Multicast address/ IP port
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
IP address/ IP port
The IP address and IP port for KNXnet/IP tunnelling are defined 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
Authentication code
Please refer to your ETS project for the authentication code for commissioning IP Secure.
Key ring for KNX Secure
Once you have configured an IP address for your HS/FS, the specified link leads directly to the page from which the key ring for KNX Secure can be uploaded:
The key ring help file can be accessed directly from this page.
https://[HS_IP_ADR]/hsknxkeysThe key ring help file can be accessed directly from this page.
2.Activate support for iETS
Note
iETS support depends on the specified interface!
Yes: The programming of the KNX system can be carried out with the iETS client. The HS/FS is then the iETS server. With the ETS5, the iETS client is available as an app.
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 the ETS5 V5.6.6 using the EIBlib/IP ETS app, the ETS3 V1.00 and the ETS 2 V1.13.
Install the current Version of the ETS!
Programming was tested with the ETS5 V5.6.6 using the EIBlib/IP ETS app, the ETS3 V1.00 and the ETS 2 V1.13.
IP Port 1
iETS Port 1, standard: 50000.
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
IP Port 2
iETS Port 2, standard: 50001:
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
IP Port 3
iETS Port 3, standard: 50002.
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
The port used here must match the settings of the iETS client.
Some reserved ports may not be used:
Limit IP access
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 address w/o IP network
IP/network address of the client which is to be granted access (see also this Wikipedia entry).
Net mask
Net mask of the client which is to be granted access (see also this Wikipedia entry).
Opt. release object (1=open)
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.