Id
The Id field shows the internal number under which the interface is stored. When creating a new interface, the field is empty. The type of the interface is displayed next to it. Both parts are for display and information only.
Name
The name of the interface. The name is displayed in selection lists and, where applicable, to users in notifications about the interface.
Comment
The comment field is for free use by the integrator. It serves exclusively to document the configuration. You can enter information here, e.g. the purpose of the interface, any special features, etc.
Options
Here you will find a single checkbox: Disabled. If you set this checkbox, the interface is disabled as far as possible. Channels of the interface remain available in the system, but write accesses are no longer passed on to the hardware, and read accesses return no value or the last available value.
Disabling an interface can be useful if the hardware is no longer connected or is defective, or if you want to try something out without addressing physical devices.
Type
Here you select the type of interface to communicate with and which medium the interface uses.
Network Adapter
Normally this field is empty. You only need to fill it in if the KNX IP gateway cannot be reached via the default network interface ( more… ).
IP Gateway Address
Enter the IP address of the KNX IP gateway this interface communicates with. This IP address should be permanently assigned to the IP gateway ( more… ). This field is only used if you have selected an IP type as the interface type.
IP Secure
Click the "Import ETS keyring" button. Then select the keyring file and enter the password (file extension: ".knxkeys"; it must be exported from ETS). A selection of the user numbers/device addresses for which keys exist in the keyring appears. Select the device address whose key X2B should use. The required fields (see below) are then filled in automatically with the correct data. X2B only stores the keys for the device address/user you select, but not the password. To select a different device address/user, the file must be imported again.
Manual configuration: For IP Secure operation, the fields Device Address, User Id, User Key and Auth Key must be filled in with the keys and the matching user number/device address. The user number is a number from 1 to 127; both keys must be entered in hexadecimal notation (32 characters each, 0-9, A-F). Note: You cannot determine this information yourself from a .knxkeys file without additional tools, as the data there is encrypted (import the .knxkeys file directly, see above).
Port
The port number on which the KNX IP gateway communicates. If you leave the field empty, the default port 3671 is used, to which IP gateways are normally preconfigured. This field is only used if you have selected an IP type as the interface type.
USB Stick
Here you select the USB stick that establishes the KNX connection. This field is only used if you have selected a USB type as the interface type.
Only supported USB sticks that were plugged in at the time you opened the configuration are displayed. Reload the browser window (F5 key in most Windows browsers) to update the selection of USB sticks.
Device Address
Optional. Here you can specify the KNX device address from which X2B sends telegrams. Leave the field empty to let the IP gateway select an address automatically. If you want to assign a device address yourself, make sure the address is not already used by another device. Do not confuse the device address with a group address (example device address: 1.2.0). A device address you specify can make it easier to recognize/filter X2B telegrams in the bus monitor/ETS.
This field is only used by the interface types IP/IPSecure and USB/RF. USB/TP does not support selecting the device address.
Domain Address
This field is only required in connection with KNX/RF. Enter the domain address of the RF network to communicate with (if this address is missing, no telegrams can be sent to RF devices, or the devices do not respond to them). The address must be specified in the same format as in ETS.
NAT Mode
Controls the IP gateway in NAT mode. This option corresponds to the option of the same name in ETS. Normally you do not need NAT mode, as the X2B Visu and the IP gateway are (or should be) located in the same network. If you need NAT mode because you are controlling an IP gateway via router tricks/port forwarding etc., you most likely have a serious security problem in your network!
No GroupRead
In a new installation where status addresses are programmed properly and correctly, leave the checkbox unchecked. This option only exists for installations in which GroupRead causes problems. These should be resolved by correcting the programming. If that is not possible, this option can help avoid problems, but with disadvantages for the visualization.
At startup, the KNX interface normally tries to read the state of all group addresses declared as readable via a GroupRead request on the bus. If this checkbox is set, reading at startup is skipped. The state of the Visu may then not be fully consistent with the state in the KNX network. This can be useful if reading causes side effects or excessive bus load (two group addresses are read per second). For outdated installations without status addresses, you should set the checkbox.
Log Telegrams
If this checkbox is set, all activity on the KNX bus is written to the general log file. This can help with troubleshooting but should be disabled again once troubleshooting is complete, as it can greatly increase the size of the log file; hundreds of additional entries per minute can occur.