História stránky

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 # - Upto version D2000 v22, it will be replaced be replaced by the path to the protdll directory in the D2000 installation, where d2knx is located by default (e.g. D:\D2000\D2000.EXE\protdll)
  Starting with version D2000 v23, due to the support of several Falcon SDK versions (5 and 6), new symbolic names #PROTDIR5# and #PROTDIR6# are created, which are replaced by the path to the directories protdll\knx5 or protdll\knx6, replacing #PROTDIR# with protdll\knx5 (e.g. D:\D2000\D2000.EXE\protdll\knx5).
• # BINDIR # - it will be replaced with the path to the bin directory (bin64 in the 64-bit version of D2000 on Windows) in the D2000 installation
• # HOST # - it will be replaced by the IP address configured on the line (in case of the configuration of several IP addresses, these will be used alternately)
• # PORT # - it will be replaced by the TCP port number configured on the line

Note: The protdll directory also contains sample startup scripts for Windows (d2knx.bat) and Linux/Raspberry PI (d2knx).

Type of KNX adapter that the d2knx module opens and with which it communicates via the KNX bus:

• USB interface by position - from the list of available KNX USB devices, the device at the position defined by the KNX Interface ID parameter (number 0, 1, 2, etc.) is selected
• USB interface by name - a device whose name contains the text entered by the KNX Interface ID parameter (e.g. "Tapco") is selected from the list of available KNX USB devices
• USB interface by path - from the list of available KNX USB devices, a device whose path contains the text specified by the KNX Interface ID parameter is selected (e.g. "4d1e55b2")
• IP interface (IP address, port, protocol, NAT) - the device whose IP address is in the KNX Interface ID parameter is used

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.

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.

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 detection (default)
• UDP - UDP protocol will be used
• TCP - TCP protocol will be used

Automatic
UDP
TCP

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.

KNX address that can be set on the KNX interface after opening it. If not specified, the existing KNX interface address is used.
The KNX address has the format area.line.device (e.g. 1.3.99) where the area is 0..15, the line is 0..15, the device is 0..255.

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:

• # APPDIR # - it will be replaced by the path to the application directory (e.g. D:\D2000\D2000.APP\myapp\)
  Examples:
  #APPDIR#myfile.knxkeys
  D:\keys.knxkeys

A password to access the security key file.
Note: If secure communication is used, both Security Keys and Security Password must be specified.

This parameter activates the d2knx module debugging information.

Zapnutie ladiacich informácii modulu d2knx.

This parameter activates the debugging information about the read/written values.