EIB/iETS
Back Forward | Help / Project / EIB/iETS
The interface that the HomeServer uses to access the EIB is set here as well as the parameters for iETS access via the HomeServer to the EIB.
EIB
EIB- connection
The device that the HomeServer uses to establish the connection to the EIB is defined here. Attention: The set interface is not automatically detected!

The following interfaces are supported:
 Comment:
In rare cases, the connection between the BCU2 and the EIB must be terminated once after using the BCU2/FT1.2 mode. To do this, you must reprogram the HomeServer with this mode, wait until the HomeServer has started (a double beep is emitted three times), then switch off the HomeServer and disconnect the BCU2 from the EIB for approx. 60 seconds. Then reconnect to the EIB and restart the HomeServer. You do not have to disconnect the connection cable between the HomeServer and the BCU.
Limit EIB telegrams
Yes: The HomeServer limits the transmission rate to the following number per second.
No: The HomeServer transmits with a maximum of 20 telegrams per second to the EIB.
Telegram/Seconds
The HomeServer limits transmission to the number set here.
Multicast IP address (only for Siemens IP Router N146)
The EIB telegrams are distributed throughout the LAN via this multicast IP address.
The settings of the IP router and contained in your ETS project.

The standard IP address is: 224.0.23.12


Example from ETS 2 V1.3 parameter N146
IP port (only for Siemens IP Router N146)
The IP router is addressed via this port. The settings of the IP router and contained in your ETS project. The standard IP port is: 3671
Physical address of the HomeServer. (Only for Siemens IP Router N146 and BCU 2 *New mode*)
ATTENTION: The address must be unique, i.e. it must not exist within the EIB project. If the BCU 2 has been used in new mode then the HomeServer sets the connected BCU to the physical address set here! Any already existing address is thereby overwritten!!
iETS
Activate support for iETS
Yes: The EIB system can be programmed via the iETS client. The HomeServer is then the iETS server.

When programming with the iETS client, the HomeServer keeps running, EIB switching procedures are carried out and changes in EIB states are detected.

Attention: In iETS mode, BCU2/FT1.2 (compatibility mode) and S+P EIB router must both receive a physical address via the EIB!!
No "local" functions can be carried out with the iETS for the BCU connected to the HomeServer!!
The programming has been tested with the ETS3 V1.00 and the ETS 2 V1.13.
Important: Install the current patches - these have been used during the test!


Settings from the ETS3 menu item Tools/Options/Communication/Configure interface.
In this example, the HomeServer has IP address 192.168.0.81.


The basic connection to the HomeServer as an iETS server can be tested via
the ETS3 menu item Tools/Options/Communication/Test


ATTENTION: If the internet is to be accessed via the HomeServer, then a default gateway must be entered in the network section (compulsory). The following ports must be unblocked in the internet router and the HomeServer IP address must be assigned.
During iETS access via the internet, there must simultaneously be a
connection via the browser/HS client, otherwise the HS terminates the connection after the timeout!
IP port 1
iETS port 1, standard: 50000.
The port used here must agree with the settings in the iETS client.
IP port 2
iETS port 2, standard: 50001:
The port used here must agree with the settings in the iETS client.
IP port 3
iETS port 3, standard: 50002.
The port used here must agree with the settings in the iETS client.
Restrict IP access
Yes: Access can be restricted by means of a network address and network mask. The iETS clients must then be from this address area.
No: There is no restriction regarding the address area from which the iETS client gains access.
Enable
You can enable iETS access via the communication object assigned here.
If the value of this object is one then the iETS can be worked with via the HomeServer.
Status
The communication object assigned here has the value 1 when there is an iETS access. Otherwise the value is zero
Socket timeout
Socket timeout in seconds. The iETS server waits for this time until there is a timeout.