KNX protocol
Supported device types and versions
Communication line configuration
Line protocol parameters
Communication station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions
| Kotva | ||||
|---|---|---|---|---|
|
...
The KNX protocol is an open standard used in building automation. The KNX implementation uses the Falcon SDK developed by the KNX association. Since this SDK is developed in C #C#, the connection to the D2000 KOM process is handled by a separate module d2knx, which by default is located in the protdll directory and communicates with the D2000 KOM process via a TCP connection.
For each communication line on which there are stations with KNX protocol, it is necessary to run one instance of the d2knx module, which requires a separate KNX interface. The KNX interface can be connected via the USB interface or can be accessed via network based on its IP address.
...
Examples of manually running d2knx:
- d2knx 127.0.0.1 4011 debug
- d2knx 0.0.0.0 4012
Example output (if start without parameters):
EIB/KNX interface module
(c) 2020 Ipesoft
Usage : knx ListenIP ListenPort [debug]
Example: knx 127.0.0.1 4011
Available interfaces:
Device 0 Path \\?\hid#vid_16d0&pid_0490#6&34ad9346&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, Name Tapko USB Interface
...
| Parameter | Meaning | Unit / Size | Default value |
|---|
| Parameter | Meaning | Unit / Size | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Configuration of starting the d2knx module by the D2000 KOM process. If this parameter is empty, the d2knx module will not be started (another starting mechanism is assumed). The parameter contains the following symbolic names:
| - | #PROTDIR#d2knx #HOST# #PORT# | ||||||
| Type of KNX adapter that the d2knx module opens and with which it communicates via the KNX bus:
| - | USB interface by position | ||||||
| Identification of the KNX adapter to be opened, which depends on the selected KNX interface type - see the description of the KNX Interface Type parameter. This can be the serial number of the USB interface, part of its name or path, or the IP address of the KNX router. | - | 0 | ||||||
| If KNX Interface ID = "IP interface", then this parameter specifies the port number (TCP or UDP) on which the KNX router communicates. The default port number is 3671. | - | 3671 | ||||||
| If KNX Interface ID = "IP interface", then this parameter indicates whether UDP or TCP protocol is used for communication with the KNX router:
| Automatic | Automatic | ||||||
| If KNX Interface ID = "IP interface" and communication goes via the UDP protocol, this parameter specifies whether address translation (NAT) is to be used for communication. | YES/NO | NO | ||||||
| KNX address that can be set on the KNX interface after opening it. If not specified, the existing KNX interface address is used. | - | - | ||||||
| The name of the security key file. If secure group communication is used, this file (so-called keyring file - * .knxkeys) can be exported from the ETS configuration tool, which is available on the KNX asociácie's website. The parameter contains the following symbolic names:
| - | - | ||||||
| A password to access the security key file. | - | - | ||||||
| This parameter activates the d2knx module debugging information. Zapnutie ladiacich informácii modulu d2knx. | YES/NO | NO | ||||||
| This parameter activates the debugging information about the read/written values. | YES/NO | NO |
| Kotva | ||||
|---|---|---|---|---|
|
...
The following station parameters can be set:
| Parameter | Meaning | Unit / Size | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Method of explicit reading of I/O tags of type Group address:
| Never Once Always | Once | ||||||
| Reading priority used for explicit reading of I/O tags of type Group address:
| - | Low | ||||||
| Timeout for the response when explicitly reading I/O tags of type Group address. Allowed values are 0-60000 ms. | ms | 0 |
| Kotva | ||||
|---|---|---|---|---|
|
...