This section provides settings and information in order to configure the connection between a computer and a KNX installation. There are 3 subsections here, which are the following:
Current Interface
Shows the currently active bus connection. The Settings in the right-hand window can be used to set the local Individual Address of this connection.
Configured Interfaces
List of all configured connections (regardless of their current availability). The following buttons are available:
Button | Description |
---|---|
Creates a new connection | |
Deletes one single selected connection | |
Imports configured interfaces (see here) | |
Exports configured interfaces (see here) |
The list may contain the following information:
Icon | Connection type | Name/IP Address |
---|---|---|
USB |
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. |
|
KNXnet/IP tunneling |
||
EibLib/IP |
||
KNXnet/IP area line detected |
||
KNX IP Secure secured area line detected
|
A red dot () right after the icon above indicates that the interface is in Programming Mode (refreshes every ~3 seconds).
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.
KNXnet/IP tunneling
Property | Description |
---|---|
Name | Name of the interface |
Server | Desired IP address of the interface (if interface is self-defined) or name, server for resolution of an IP address (text input) |
IP address | IP address found for the interface |
Port | 3671 (default) |
Host Individual Address | Individual Address of the host device |
Individual Address | Further available Individual Addresses of the host device; for details, see |
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. |
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) |
Port | 3671 (default); always permanent for routing and consequently, cannot be changed. |
Routing 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 |
USB
Property | Description |
---|---|
Name | Name of the interface |
Manufacturer | Manufacturer of the interface |
Medium | Medium to which the USB interface is connected to |
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. |
Discovered Interfaces
Here you will see a list of all existing connections unless they are already in the Configured Connections list.
USB and IP routing interfaces are recognized and displayed automatically by ETS5, they do not need to be created. A not recognized interface cannot be used by ETS even if it is manually created.