To configure a found bus interface or to manage (create, edit, delete) a bus interface, click the respective cog icon.
In the interfaces list, it is possible to find back the following information:
| Icon | Connection type | Name/IP Address |
|---|---|---|
|
|
KNX/USB |
|
|
|
KNXnet/IP tunneling |
Shows the user-defined Name and if the connection type is IP, the assigned IP address (as well as MAC address, address will be accepted when the connection is established/configured). The user- defined Name on KNXnet/IP tunneling (devices) is downloaded into the device later on. The length limitation in the device itself is 30 chars (fixed by the KNX Specifications). When the device/interface is "discovered" later by ETS the name out of the device with maximal 30 chars is shown. |
|
|
EIBlib/IP |
|
|
|
KNXnet/IP area line detected |
|
|
|
KNX IP Secure secured area line detected
|
Properties
The properties are shown in the right-hand window. For the current interface, next to the individual address field there is a button to test whether the given individual address is free.
| Property | Description |
|---|---|
| Name | User friendly name for the connection (for KNXnet/IP connections, its is shown as 'user friendly name', the name - from device properties/sidebar of interface from the ETS project) |
The following information is displayed depending on the interface type that has been selected.
Parameter modification is only possible if the interface has been manually created.
USB
| Property | Description |
|---|---|
| Name | Name of the interface |
| Manufacturer | Manufacturer of the interface |
| Medium | Medium to which the USB interface is connected |
| Individual Address | The interface's individual address, as well as a button to test whether the given individual address is free. |
| APDU length | The maximum data length within a telegram that the interface can handle. |
When using a USB interface, the required driver is installed directly the first time a connection is made to the PC. If you change the port to which your USB interface is connected, the driver will be installed again.
KNXnet/IP Tunneling
| Property | Description |
|---|---|
| Name | Name of the interface |
| Individual Address | Device's Individual Address |
| Server | Desired IP-address of the interface (if interface is self-defined) or name, server for resolution of an IP address (text input) |
| Port | 3671 (default) |
| IP address | IP address found for the interface |
| Network Address Translation |
Enables/Disables Network Address Translation. NAT is only necessary when creating an interface if it cannot be automatically found. If an interface is found by ETS automatically, the NAT option does no longer needs to be set explicitly. |
| Secured |
To be selected if the bus interface is securely configured. |
KNXnet/IP Routing
| Property | Description |
|---|---|
| Name | Name of the interface |
| Individual Address |
Individual Address of the (local) interface; preselection for the area line (0.0.1) |
| Multicast Address |
224.0.23.12 (default)
|
| MAC Address | MAC Hardware address of the interface. |
EIBlib/IP
| Property | Description |
|---|---|
| Name | Name of the interface |
| Server |
IP address of the interface |
| Protocol |
TCP or UDP |
| Port | Configuration/read/write port (5000x) |
| COM | COM connection number |
Configure a found interface
The local individual address must be set in such a way, that the area and line number match the current installation location of the interface. The device number must be an address not in use in the project. E.g., '255' is the most suitable device number, as this high number is probably not present in the installation.
Should a flush-mounted USB interface be mounted on a Bus Coupling Unit and later removed (after which e.g. a push button sensor is mounted instead), one shall immediately set the individual address intended for the later push button sensor.
Manage Configured Interfaces
A configured connection is necessary if ETS cannot detect the bus interface automatically, either because the network does not support IP Multicast, or the interface is behind a NAT router (*), or the interface uses the EIBlib/IP protocol.
(*)Warning: Exposing a KNX interface to the public internet is a major security risk! Act responsibly and allow access only via a secure channel (VPN) instead.
The following buttons are available:
| Button | Description |
|---|---|
 |
Creates a new connection, but only of the type IP Tunneling and EIBlib/IP |
 |
Toggle Use for this Project, selects the interface for this specific project. |
 |
Deletes one single selected connection |
 |
Imports configured interfaces |
 |
Exports configured interfaces |
EIBlib/IP
This type of communication is only supported after having installed the respective ETS App "EIBlib/IP".
IP Tunneling
KNXnet/IP Tunneling
KNX telegrams are wrapped into TCP/IP and sent by the ETS to the IP-Tunneling interface, which again removes the TCP/IP envelope and routes the telegram to the lower TP area or TP line.
KNXnet/IP Routing
For KNXnet/IP routing, one uses the IP connection of an IP-router or a pure KNXnet/IP device (not having a connection to TP).
In case where an IP router is used, one shall make sure that the individual address is reset to a value that suits its function as a coupler (e.g. 1.1.0) if having changed it to another value (e.g. 1.1.255).