KNX interface 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, however a KNX IP router cannot replace the controller. When the KNX interface is enabled, all variables up to address 31/7/255 are automatically sent to the KNX bus and KNX telegrams are received. Tip: From image version 3 an internal IP gateway can be enabled in the web interface of the controller. If this is enabled, this block must be set to KNX-IP gateway onboard, since the gateway occupies the 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 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). |
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 2 minutes); here the output briefly switches between 3 and 9. |
| RX | Received | Number of telegrams received. |
| TX | Sent | Number of telegrams sent. |
| FA | Error count | Number of communication errors. |
| FU | Monitoring error | Number of telegram monitoring errors when the input KNX monitoring is connected to an address. |
Parameters |
||
| Type | Type of interface:
|
|
| Telegram pause time | Minimum wait time between two telegrams | |
| IP address | IP address (KNX-IP gateway external only) | |
| Port | IP port (KNX-IP gateway external only) | |
| 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. 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. | |