Overview KNX interface



With this function block the onboard KNX interface or IP gateways are configured.

There may only be one block for the onboard interface; several IP gateways can be inserted. Several IP gateways can connect different KNX networks to the controller. The controller sends its telegrams to all networks, but does not forward telegrams from one network to the others - so it does not replace a KNX IP router or line coupler between these networks.

When the KNX interface is enabled, all addresses up to address 31/7/255 are automatically sent to the KNX bus and KNX telegrams are received.


Tip: From image version 4 an internal IP gateway is integrated in the controller. It is controlled by the type of this block: with KNX-IP gateway onboard the controller starts the gateway, with any other type (including TP-UART onboard) it stops it. The gateway therefore no longer has to be switched on or off by hand; it occupies the onboard KNX interface.

Note ETS programming: Via the internal IP gateway KNX devices can also be programmed with the ETS. For programming with ETS 6.1 or newer, the image version of the controller must be at least 4.011. The internal IP gateway is third-party software, on whose development we have no influence. Therefore, functionality with future ETS versions cannot be guaranteed.

The internal IP gateway only works with a KNX bus connected. If the bus or the bus voltage is missing, it shuts itself down after a few seconds and is restarted over and over again. Neither the ETS nor the controller itself then get a stable connection, it drops again after one or two seconds. A test without a KNX bus, e.g. in the office, is therefore not possible.

The physical addresses reserved by the block (see parameter Phys. address count) must not be used by any KNX device on the bus. If the message "Incompatible BCU version" appears during programming in the ETS, a device other than the expected one is answering. The cause is usually a physical address assigned twice or an incorrect or outdated catalog entry in the ETS project (device with a newer hardware generation).

Note KNX Secure: The internal IP gateway does not support KNX IP Secure; the connection of the ETS to the gateway is unencrypted. In addition, the interface only supports the standard APDU length of 15. Devices whose download requires longer telegrams — in particular the secure commissioning of KNX Data Secure devices — cannot be programmed via the internal IP gateway. In this case the ETS reports "Insufficient APDU length (limited to 15 by the capabilities of the bus interface)". For such devices, either secure commissioning must be disabled in the ETS or an external IP interface must be used. Furthermore, the controller cannot — regardless of the interface type — communicate with group addresses encrypted with Data Secure. Group objects that are linked to the controller must be set to unencrypted in the ETS (Data Secure can be disabled per group address).

An external IP interface with KNX IP Secure can be connected via the type KNX-IP gateway external (Secure). This only applies to the connection between the controller and the interface, see parameters.


Inputs

KU KNX monitoring Optional monitoring of the KNX connection. If an address is connected here, it is read out cyclically and monitored for whether a response arrives. Reading must be enabled at the actuator for this. If the response is missing, the output Error is set and the KNX connection is reinitialized. The address is read at an interval of 10 seconds, the timeout is 30 seconds.

Outputs

ST Status Status. For onboard 0 not connected, 1 connected.

For IP gateway the connection status:

less than 8 = connection is being established.
9 = connection OK

The connection to the gateway is checked cyclically (approx. every minute); here the output briefly switches between 3 and 9.

Important for the IP gateway: The linked address must use at least the data type "EIS 14: counter value (1 byte)". New addresses are preset to "EIS 1: switch bit (bit)", which can only carry 0 or 1, so every value other than 0 is truncated to 1. The output then keeps switching between 9 and 1 although the connection is fine.
RX Received Number of telegrams received.

The linked address requires the data type "EIS 11: counter value 32 bit (4 bytes)", because the counter goes far beyond 255.
TX Sent Number of telegrams sent.

The linked address requires the data type "EIS 11: counter value 32 bit (4 bytes)", because the counter goes far beyond 255.
FA Error count Number of communication errors.

Data type of the linked address: "EIS 11: counter value 32 bit (4 bytes)".
FU Monitoring error Number of telegram monitoring errors when the input KNX monitoring is connected to an address.

Data type of the linked address: "EIS 11: counter value 32 bit (4 bytes)".

Parameters


Type Type of interface:
  • TP-UART onboard: Built-in KNX interface. Only via this interface are all error messages from the KNX bus (for example telegram checksum errors) reported. A running internal IP gateway is stopped by the controller itself so that the interface is free.
  • KNX-IP gateway external: External IP gateway
  • KNX-IP gateway external (Secure): External IP gateway with KNX IP Secure (secure tunnelling). The connection between the controller and the interface is encrypted; the controller logs on with a user ID and a tunnel password. To do this, create a separate tunnel for the controller on the interface in the ETS. This only encrypts the connection to the interface; the controller still cannot process group addresses encrypted with Data Secure.
  • KNX-IP gateway onboard: Internal IP gateway. From image version 4 an internal IP gateway is integrated. With this type the controller starts the gateway itself; it occupies the onboard interface, so no other block may be set to TP-UART onboard. When the type is changed, the controller first closes the previous interface and then opens the new one. If no IP gateway is required, TP-UART onboard should preferably be used. If the internal IP gateway accepts no connection for one minute, the controller restarts it automatically (at most every five minutes). Without a KNX bus connected the internal IP gateway cannot work and keeps terminating itself. The controller then restarts it at growing intervals (up to 30 seconds) and reports this once in the diagnostic area; after the bus is plugged in again the connection is back within 30 seconds at most. See also Note ETS programming above.

Telegram pause time Minimum wait time between two telegrams

IP address IP address (KNX-IP gateway external only, also Secure)

Port IP port (KNX-IP gateway external only, also Secure)

IP address backup controller Optional (KNX-IP gateway external only, also Secure). IP address of a second KNX-IP gateway that is used exclusively by a controller on which "Use as backup control" is active.

Not filled in: the backup controller uses the same gateway as the primary controller - the previous behaviour.

If an address is entered it is always used, that is also while the primary controller is still running and the backup controller only runs along. The connection is therefore already established before a takeover, the second gateway is continuously checked and a tunnel slot remains free on the first gateway.

On the primary controller this parameter has no effect. See also Backup controller.

Port backup controller Optional (KNX-IP gateway external only, also Secure). IP port of the second gateway, default 3671. Only takes effect if "IP address backup controller" is filled in as well.

Secure user ID KNX-IP gateway external (Secure) only. User ID of the tunnel the controller uses on the interface. Each tunnel of a secure interface has its own user ID and its own password in the ETS. The controller should get a tunnel of its own that nobody else uses. Default 2 (user ID 1 belongs to the management of the interface).

Secure tunnel password KNX-IP gateway external (Secure) only. Password of the tunnel from the ETS. The field does not show the password. Without a password or with a wrong password no connection is established; the diagnostics area (footer - message/error) then shows "KNX SECURE: NO TUNNEL PASSWORD SET" or "KNX SECURE: AUTHENTICATION FAILED". After a rejected logon the controller tries again after one minute at the earliest.

Secure device code Optional (KNX-IP gateway external (Secure) only). Device authentication code of the interface from the ETS. If entered, the controller checks when connecting whether it is connected to the right interface. If the code does not match, it reports "KNX SECURE: INTERFACE NOT AUTHENTIC" and does not connect. Empty: this check is skipped.

Keyring KNX-IP gateway external (Secure) only. The button Import from ETS keyring enters the user ID, tunnel password and device code from a keyring exported in the ETS (file .knxkeys), so they do not have to be typed in by hand.

In the dialog choose the file, enter the export password that was set during the export and press Read. The list shows all tunnels in the file with interface, tunnel address and user ID. Select the tunnel the controller is to use and press Apply. A wrong password is detected immediately.

The export password is only used for decryption and is not stored; afterwards the project only holds the three secure fields (user ID, tunnel password, device code). If the file contains no device code, the field is cleared and the check of the interface is skipped. The group keys for Data Secure contained in the file are not used. The IP address of the interface is not part of the keyring and still has to be entered.

Phys. address Physical address. This address is used when telegrams are sent from the controller.

Phys. address count Physical address count (IP gateway onboard only). Number of addresses occupied by the IP gateway; these are assigned consecutively starting from the start address.

Example:

Physical address = 1.1.60
Physical address count = 5

Telegrams from the controller are sent with physical address 1.1.60. The internal IP gateway itself occupies the address 1.1.61, the addresses 1.1.62 - 1.1.64 are assigned to tunnel connections (runtime, ETS). A count of at least 4 must be set and free (1x controller, 1x gateway, 1x client runtime, 1x client ETS), the default is 4. A count of 5 is recommended so that an additional address is free when group monitor and programming run in parallel in the ETS or a client does not disconnect correctly.

If the count is lower than 4, the controller reports this at startup in the diagnostic area (footer - message/error) with “KNXD: PHYS. ADDRESS COUNT … TOO LOW”. If the IP gateway gets no connection to the KNX bus, “KNXD: NO RESPONSE FROM KNX BUS” is shown there. If all tunnel connections are in use, e.g. by the ETS, the controller reports “KNXD: ALL TUNNELS IN USE” and has no connection to the KNX bus itself until one is released. The controller starts and stops the IP gateway itself according to the selected type. The switch under Controller – Services or in the web interface therefore only takes effect as long as the project contains no KNX block; without the IP gateway use the type “TP-UART onboard”.

Important: The entire reserved address range (in the example 1.1.60 - 1.1.64) must not be occupied by any KNX device on the bus.

Note: If the function Backup controller is used, the physical address is set in the settings for the backup controller.

Router function Router function (IP gateway onboard only). With this option the onboard IP gateway works as a KNX IP router. If several controllers are in the same network, this function may only be enabled on one of them.

TP-UART timeout Timeout for acknowledge from the KNX bus, default 500 ms. This time is waited for the acknowledge from the KNX bus.

TP-UART ACK error Show acknowledge errors. With this option the error message missing acknowledge can be hidden. The acknowledge is missing, for example, when a KNX address is sent on the bus that is not connected to any actuator. If this option is active, missing acknowledges are counted as errors and after 64 errors a reset of the KNX TP-UART block is performed.




See also common parameters of all function blocks.