Id #
The Id field shows the internal number of the interface under which it is saved. When creating a new interface, the field is empty. The type of interface is displayed behind it. Both parts are for information purposes only.
Name #
The name of the interface. The name is displayed in selection lists and may also be displayed to users in interface notifications.
Comment #
The comment field is for free use by the integrator. It is used 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: Deactivated. If you set this checkbox, the interface is deactivated as far as possible. Channels of the interface are still 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.
Deactivating an interface can be helpful if the hardware is no longer connected/defective, or if you want to try something out without the physical devices being addressed.
Type #
Here you select the type of interface to be used for communication and which medium the interface uses.
Network adapter #
This field is normally empty. You only need to fill it in if the KNX IP gateway is not accessible via the standard network interface ( more… ).
IP gateway address #
Enter the IP address of the KNX IP gateway with which this interface communicates. 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 on the “Import ETS keyring” button. You must then select the keyring file and enter the password (file extension: “.knxkeys”, this must be exported from ETS). A selection of user numbers/device addresses for which keys are available in the keyring appears. Select the device address whose key X2B should use. The required fields (see below) are then automatically filled in with the correct data. X2B only saves 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.
Configure manually: For IP Secure operation, the Device address, User ID, User key and Auth key fields must be filled in with the keys and the corresponding user number/device address. The user number is a number 1-127, the two keys must be entered in hexadecimal notation (32 characters each 0-9, A-F). Attention: You cannot determine this information yourself from a .knxkeys file without additional auxiliary programs, as the information is encrypted there (import the .knxkeys 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 on 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 inserted at the time you called up the configuration are displayed. Reload the browser window (F5 key in most Windows browsers) to update the selection of USB sticks.
Device address #
Optional. The KNX device address from which telegrams are sent by X2B can be specified here. Leave the field empty so that the IP gateway automatically selects an address. If you want to assign a device address yourself, make sure that the address is not already being used by another device. Do not confuse the device address with a group address (example device address: 1.2.0). A device address defined by you can be helpful to recognize/filter telegrams from X2B in the bus monitor/ETS more easily.
This field is only used by the interface types IP/IPSecure and USB/RF. USB/TP does not support the selection of the device address.
Domain address #
This field is only required in connection with KNX/RF. The domain address of the RF network with which communication is to take place must be entered here (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 entered in the same format as in the ETS.
NAT mode #
Controls the IP gateway in NAT mode. This option is analogous to the option of the same name in the ETS. Normally, you do not need NAT mode, as the X2B Visu and the IP gateway are (should be) 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 #
For a new installation in which status addresses are properly and correctly programmed, leave the checkbox unchecked. This option only exists for installations in which GroupRead causes problems. These should be resolved by correcting the programming. If this is not possible, this option can help to avoid problems, but with disadvantages for the visualization.
At startup, the KNX interface normally attempts to read the status of all group addresses that are declared as readable by means of a GroupRead request on the bus. If this checkbox is set, reading does not take place at startup. The status of the Visu may then not be completely consistent with the status in the KNX network. This can be useful if reading causes side effects or too high a bus load (two group addresses are read per second). For outdated installations that have no status addresses, you should set the checkbox.
Log telegrams #
If this checkbox is set, all activities on the KNX bus are written to the general log file. This can help with troubleshooting, but should be deactivated again once troubleshooting is complete, as it can greatly increase the size of the log file, resulting in hundreds of additional entries per minute.
