Français:Utiliser l'eipPort comme interface de programmation
From bab-tec.de wiki
Using eibPort V3 as programming-interface
Contrary to previous generations of eibPort (2.0,2.1) , eibPort release 3 will no longer work with Eiblib/IP protocol, but with the modern KNXnet/IP protocol for programming. The KNXnet/IP protocol offers some new features:
- The eibPort will execute all other services also during your programming tasks.
- For communication only one port has to be forwarded.
- Line overlapping programming will be possible also as a coupler.
Basics of KNXnet/IP protocol
KNXnet/IP will be divided in two different connection procedures
- KNXnet/IP Routing: The KNXnet/IP telegrams will be transferred through the network by so called multicast-data packets. This means that it doesn`t exist one decidedly connection between participants, but all will send to a multicast group (22.214.171.124) and every member of this group can handle the packets. Because multicast packets will not transferred by routers, “Routing” will work only within a subnet. KNXnet/IP Routing will be applied primarily for coupling various KNX-lines with the help of one so called “IP-Router”.
- KNXnet/IP tunneling: Telegrams will be sent by UDP Unicast to a defined subscriber. In doing so, one participant will work as a server (eibPort) and the other one acts as a client (ETS). Data packets also will be transferred to a defined recipient, validation takes place on KNX layer. Therefore this connection is designed for transporting data over several networks (Internet), too. The “Tunneling”-protocol is used for work of programming or purpose of remote maintenance and control. (For example ETS group monitoring or Apps of mobile devices)
Enabling KNXnet/IP Tunneling in the eibPort
To enable KNXnet/IP Tunneling protocol in the eibPort, please proceed as follows:
- Check the correct physical addressing:
Please open menu “System” > “Configuration” > “General” and check the entry arrays “Physical address of BCU” and “ indiv. addr. for KNXnet/IP Tunneling”. These both addresses have to correspond to the cast-in-place of eibPort and they are not allowed to be the same.
|Example:||In case the eibPort is a subscriber of line 1.1.x, addresses could be for example 1.1.200 and 1.1.201. If several KNXnet/IP Tunneling connections will be required simultaneously, addresses could be entered one after another in the array “Indiv.Adr. für KNXnet/IP Tunneling” by using semicolons for separation. Certainly all adapted addresses in eibPort should be unutilized by another subscriber.|
- After that, please open in menu “Configuration” the menu item “Extended EIB (yabus) settings”, scroll down the configuration window to the bottom and enable the check box in line “KNXnet/IP Tunneling”. In doing that “Tunneling” will be enabled!
Settings in ETS
- Open the communication settings in the ETS. ETS 3: “Extras”>”Options”>”Communication”>”Interface Configuration” ETS 4: “Settings”>Communication”.
- Please choose “New” and define the name of your connection and select the protocol type “KNXnet/IP”. In menu item “Communication parameters” the necessary input arrays will appear:
- Enter the internal IP-address of eibPort into the array “IP-Address”, for example “192.168.1.222”. The setting for “Port” has to be “3671”. If you want to install an remote connection (from the internet) to eibPort, you have to enter the external IP-address or hostname of your internet connection in the array “IP-Address”. Additionally it requires enabling the check box “NAT-mode” then. Naturally you have to define a corresponding forwarding -rule of the port in your router/firewall (UDP Port 3671).
Click on “OK” to save the connection und check out its function by the “test”-button in the overview window of your established connections. In case your test will be confirmed with “OK”, the connection is successfully installed.
- Please take care of up-to-date firmware on your eibPort. By using older firmware releases, programming KNX-devices may cause problems.
- Please check out the release of your falcon driver. This is the windows-driver, which is responsible for establishing the connections and it has to be at least software version 2. You can check release of the driver by calling up the attributes of the file “falcon.exe.”, which you can find under (WIN 7): “Programs”>”Shared files”>”EIBA sc”>”Falcon”.
- If “Physical Address of BCU” and “indiv. addr. of KNXnet/IP Tunneling” are the same, the programming procedure will not been execute correctly because two similar physical addresses exist.
- In case you have activated KNXnet/IP Routing simultaneously and a IP-router is located on the same line, a telegram loop will be created and the ETS will report, that several units with the same physical address are located in the system.