Supported device types and versions
Communication line configuration
Line protocol parameters
Communication station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions
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#, 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 a network based on its IP address.
Note on the d2knx module:
The d2knx module is an application that needs ".NET Core 3.1" installed to run. We recommend that you test its functionality by running it manually from the command line.
When started without parameters, it displays help and a list of available KNX USB devices and then exits.
The required parameters are:
Examples of manually running d2knx:
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
A dialog window of communication line configuration - Protocol parameters tab.
They influence some optional protocol parameters.
The following line protocol parameters are defined:
Parameter | Meaning | Unit / Size | Default value |
---|
Parameter | Meaning | Unit / Size | Default value |
---|---|---|---|
KNX Driver Program | 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:
Note: The protdll directory also contains sample startup scripts for Windows (d2knx.bat) and Linux/Raspberry PI (d2knx). | - | #PROTDIR#d2knx #HOST# #PORT# |
KNX Interface Type | Type of KNX adapter that the d2knx module opens and with which it communicates via the KNX bus:
| - | USB interface by position |
KNX Interface ID | 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 |
IP Interface Port | 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 |
IP Interface Protocol | 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 |
IP Interface NAT | 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 Interface Address (x.y.z) | KNX address that can be set on the KNX interface after opening it. If not specified, the existing KNX interface address is used. | - | - |
Security Keys | 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:
| - | - |
Security Password | A password to access the security key file. | - | - |
Driver Debug | This parameter activates the d2knx module debugging information. Zapnutie ladiacich informácii modulu d2knx. | YES/NO | NO |
Full Debug | This parameter activates the debugging information about the read/written values. | YES/NO | NO |
Station address:
GROUP - The I/O tags on a station with the GROUP address will receive all values of the Group address type values from the communication.
area.line.device - Address of a specific KNX device (e.g. 1.3.99), where the area is 0..15, the line is 0..15, the device is 0..255. I/O tags on a station with a specific address will only receive values if they have been received from a KNX device with a specified address.
Note: it is possible to configure several stations with the same address (with a specific address or with a GROUP address), e.g. to set various time parameters for reading individual I/O tags.
The following station parameters can be set:
Parameter | Meaning | Unit / Size | Default value |
---|---|---|---|
Read Group Addresses | Method of explicit reading of I/O tags of type Group address:
| Never Once Always | Once |
Read Group Priority | Reading priority used for explicit reading of I/O tags of type Group address:
| - | Low |
Read Group Timeout | Timeout for the response when explicitly reading I/O tags of type Group address. Allowed values are 0-60000 ms. | ms | 0 |
Possible I/O tag types: TxtI, Di, Ai, Ci, TiR, TiA, TxtO, Dout, Ao, Co, ToR, ToA, Qi
Individual components of the address:
Group address: group address (16-bit number). It has three possible formats:
Attribute: which attribute of the received message with a group value is published in the I/O tag:
Note: when explicitly reading I/O tags of the Group address type, only those that have Attribute=Value configured are read. In addition to the value, other attributes are extracted from the received response.
Note: when processing spontaneous messages with group values, the attributes Flags, Source Address, Priority, Size, and finally, Value are processed one after the other.
Value type (reading): for Attribute=Value it specifies a way of interpreting the received value:
Value subtype (writing): for Attribute=Value, how to encode the value when writing:
Browse
For the I/O tags, it is possible to discover the list of objects and their data types, as long as the KOM process is running and communication with an outstation is established.
Clicking the Browse button opens the KNX Item Browser window and displays a list of objects that have been read so far. The object list is created dynamically as a result of received messages (responses read requests as well as spontaneously arrived values).
The list of objects is dynamic, i.e. when a new value arrives in the KOM process, it is updated. Filtering in individual columns is also supported, asterisks can be used in the mask (eg 0/0/*).
Double-clicking on a particular line will cause the Group address parameter to be inserted into the configuration of the I/O tag from which the KNX Item Browser window was opened.
The Refresh button clears the list of values in both the CNF and the KOM process.
The Value column contains the received value interpreted as an unsigned integer, a signed integer (only if different from an unsigned integer), and a real number (if it is 16/32/64 bits long), or as text (if it is 14*8 bits long).
https://en.wikipedia.org/wiki/KNX_(standard)
-