KNX/EIB & iETS
Previous / Next | Search | Help / KNX/EIB & iETS
Contents
1.
IP port (Only KNX/EIB IP router (KNX/EIB IP routing))
2.
Net mask
In this mask the interface is defined via which the HS/FS accesses the KNX/EIB. In addition, the parameters for the iETS access can also be set.

KNX/EIB connection

The KNX/EIB device with which the HS/FS establishes the connection to the KNX/EIB is defined here.
Important
No automatic detection of the interface used!

Interface

The following interfaces are supported:
  • Gira BCU2/FT1.2 Article No. 645 00 and 504 00. Protocol: FT1.2
  • Gira IP router Gira Article No. 2167 00 Protocol: KNX/EIB IP router (KNX/EIB IP routing) (settings)
  • Gira IP router Gira Article No. 1030 00 Protocol: KNX/EIB IP router (KNX/EIB IP routing) (settings)
  • Feller FT1.2 interface Article No. 36520.FMI.61; Protocol: FT1.2
  • Feller KNX / IP router Feller Article No. 36130-00. DRA; Protocol: KNX/EIB IP router (KNX/EIB IP routing) (settings)
  • Schlaps+Partner KNX/EIB switch serial. Protocol: OPEN_EIB
  • Siemens IP router N146 Article No. 5WG1 146-1AB01. Protocol: KNX/EIB IP router (KNX/EIB IP routing) (settings)
  • BCU2/FT1.2 compatibility mode (used in the past - no longer contained in the next version!)
  • Gira KNX/USB data interface flush-mounted Article No. 1070 00
  • Gira KNX/USB data interface DRA Article No. 1080 00
  • Feller KNX/USB data interface flush-mounted Article No. 36530.USB.xxx
  • Feller KNX/USB data interface DRA Article No. 36180-00.REG
Note
In rare cases, the BCU2 must be separated from the KNX/EIB once after the BCU2/FT1.2 mode is used. For this purpose, the HS/FS must be reconfigured with this mode; wait until the HS/FS has started (3x dual tone sounds), now switch off the HS/FS and disconnect the BCU2 from the KNX/EIB for approx. 60 seconds. Then reconnect to the KNX/EIB and restart the HS/FS. The connection cable between the HS/FS and the BCU does not need to be disconnected for this purpose.

Limit telegrams

Yes: The HS/FS limits the sending rate to the value that can be set in the following field.
No: The HS/FS sends a maximum of 20 telegrams per second on the KNX/EIB.

Telegrams/second

Setting of the desired number.

Physical address (Only IP router N146 and BCU 2 *New mode*)

Important
The address must be unique, i.e., it may not occur in the KNX/EIB project. If the BCU 2 is used in the new mode, then the HS/FS sets the connected BCU on the physical address set here! Any address that may be present is overwritten in the process!!
When using the USB interface, it is not possible to make any entries, as the physical address of the BCU is used/exported.

IP Routing Multicast Address (Only KNX/EIB IP router (KNX/EIB IP routing))

The KNX/EIB telegrams are spread in the LAN via this Multicast IP address.
See your ETS project for the settings of the IP router.

Default IP address is: 224.0.23.12

1.IP port (only KNX/EIB IP router (KNX/EIB IP routing))

The IP router is addressed via this port. See your ETS project for the settings of the IP router. The default IP port is: 3671

Activate support for iETS

Yes: The programming of the KNX/EIB system can be carried out with the iETS client. The HS/FS is then the iETS server.
Note
During programming with the iETS client, the HS/FS continues to operate, KNX/EIB switching processes are carried out and KNX/EIB status changes are detected.
Note
Install the current patches of the ETS!
Important
In the iETS mode, the BCU2/FT1.2 (compatibility mode) and the S+P KNX/EIB switch must receive a physical address via the KNX/EIB! No "local" functions for the BCU connected to the HS/FS can be carried out with the iETS!
Important
Should the HS/FS be accessed via the Internet, then a valid default gateway must be entered in the network section. The following ports must be enabled in the Internet router and assigned to the HS/FS IP address. During the iETS access via the Internet, there must be a simultaneous connection to the HS via the browser/HS client, as otherwise the HS separates the connection after the timeout!
Note
Programming was tested with the ETS3 V1.00 and the ETS 2 V1.13.

IP Port 1

iETS Port 1, standard: 50000.
The port used here must match the settings of the iETS client.

IP Port 2

iETS Port 2, standard: 50001:
The port used here must match the settings of the iETS client.

IP Port 3

iETS Port 3, standard: 50002.
The port used here must match the settings of the iETS client.

Limit IP access

Yes: The access can be limited via a network address and net mask. iETS clients must then come from the address range configured further below.
No: There is no restriction as to the address range from which the iETS client conducts access.

IP address w/o IP network

IP/network address of the client which is to be granted access (see also http://en.wikipedia.org/wiki/Net_mask).

2.Net mask

Net mask of the client which is to be granted access (see also http://de.wikipedia.org/wiki/Netzmaske).

Opt. release object (1=open)

The iETS access can be enabled with this communication object assigned here.
If this object has the value 1, then it is possible to work with the iETS via the HS/FS.

Opt. status object (With access=1)

This communication object assigned here has the value 1 if iETS access takes place. Otherwise the value is zero.

Socket timeout

Socket timeout in seconds. The iETS server waits this time before a timeout occurs.