knxnet_ip

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
knxnet_ip [2020/01/14 19:04] – ingridknxnet_ip [2020/01/28 08:40] (current) – wikiadmin
Line 12: Line 12:
   * **KNX/IP interface** without routing, allowing KNX programming over IP.   * **KNX/IP interface** without routing, allowing KNX programming over IP.
   * **KNX IP router**, allowing KNX programing as well as connecting different parts of a KNX system together over IP, much like a line coupler.    * **KNX IP router**, allowing KNX programing as well as connecting different parts of a KNX system together over IP, much like a line coupler. 
 +
 +{{ :knxnet_ip_6.png?direct800 |Thinknx server with KNXNet/IP interface}}
 +<WRAP center 60%> <WRAP centeralign> Figure 1: Thinknx server with KNXNet/IP interface</WRAP> </WRAP>
  
 The Thinknx server can also communicate with other KNXNet/IP interfaces instead of using its own embedded bus connection to communicate with the KNX bus. The Thinknx server can also communicate with other KNXNet/IP interfaces instead of using its own embedded bus connection to communicate with the KNX bus.
Line 28: Line 31:
   * **Client number** number of supported client tunnel connections.   * **Client number** number of supported client tunnel connections.
 <WRAP important center round 80%> When using the server as a KNXnet/IP interface, it is important to define the "client physical address base" and "clients number", and reserve these KNX physical addresses in the ETS project instead of assigning them to other devices. </WRAP> <WRAP important center round 80%> When using the server as a KNXnet/IP interface, it is important to define the "client physical address base" and "clients number", and reserve these KNX physical addresses in the ETS project instead of assigning them to other devices. </WRAP>
-<WRAP important center round 80%> The "Clients Physical Address base" and "Client number" are only available to be used with Thinknx Envision </WRAP>+<WRAP important center round 80%> The "Clients Physical Address base" and "Client number" are only available to be used with Thinknx Envision. On the other servers the KNX tunnel connections will share same primary physical address </WRAP>
   * **KNXNet/IP router** If enabled, the server will also route traffic from TP to multicast IP and vice versa, allowing to connect different parts of a KNX system together over IP.   * **KNXNet/IP router** If enabled, the server will also route traffic from TP to multicast IP and vice versa, allowing to connect different parts of a KNX system together over IP.
 <WRAP important center round 80%> Be careful to avoid loops that may result from connecting 2 Thinknx servers with KNXNet/IP router enabled on the same network and same TP line. </WRAP> <WRAP important center round 80%> Be careful to avoid loops that may result from connecting 2 Thinknx servers with KNXNet/IP router enabled on the same network and same TP line. </WRAP>
  
 {{ :knxnet_ip_1.png?direct800 |Enabling KNXNet/IP Interface from Configurator}} {{ :knxnet_ip_1.png?direct800 |Enabling KNXNet/IP Interface from Configurator}}
-<WRAP center 60%> <WRAP centeralign> Figure 1: Enabling KNXNet/IP Interface from Configurator </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 2: Enabling KNXNet/IP Interface from Configurator </WRAP>  </WRAP>
  
 ==== Using the webpage ==== ==== Using the webpage ====
Line 39: Line 42:
  
 {{ :knxnet_ip_2.png?direct800 |Accessing Network and KNX}} {{ :knxnet_ip_2.png?direct800 |Accessing Network and KNX}}
-<WRAP center 60%> <WRAP centeralign> Figure 2: Accessing Network and KNX</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 3: Accessing Network and KNX</WRAP>  </WRAP>
  
 Scroll down to reach the "KNX Settings". By default, the web page will show the KNX configuration uploaded with the Thinknx project.  Scroll down to reach the "KNX Settings". By default, the web page will show the KNX configuration uploaded with the Thinknx project. 
  
 {{ :knxnet_ip_3a.png?direct800 |Viewing the KNX settings}} {{ :knxnet_ip_3a.png?direct800 |Viewing the KNX settings}}
-<WRAP center 60%> <WRAP centeralign> Figure 3: Viewing the KNX settings</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 4: Viewing the KNX settings</WRAP>  </WRAP>
  
 If you wish to override these settings, click on "Overridden". If you wish to override these settings, click on "Overridden".
  
 {{ :knxnet_ip_3.png?direct800 |Editing the KNX settings}} {{ :knxnet_ip_3.png?direct800 |Editing the KNX settings}}
-<WRAP center 60%> <WRAP centeralign> Figure 4: Editing the KNX settings</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 5: Editing the KNX settings</WRAP>  </WRAP>
  
 The below parameters are available to configure: The below parameters are available to configure:
Line 73: Line 76:
  
 {{ :knxnet_ip_4.png?direct800 |Scanning server from ETS}} {{ :knxnet_ip_4.png?direct800 |Scanning server from ETS}}
-<WRAP center 60%> <WRAP centeralign> Figure 5: Scanning server from ETS</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 6: Scanning server from ETS</WRAP>  </WRAP>
  
 ===== Application 2: Thinknx server as KNXnet/IP Router ===== ===== Application 2: Thinknx server as KNXnet/IP Router =====
Line 80: Line 83:
 <WRAP column half> <WRAP column half>
 {{ :knxnet_ip_5b.png?direct500 |Installation without KNXNet/IP routing}} {{ :knxnet_ip_5b.png?direct500 |Installation without KNXNet/IP routing}}
-<WRAP center 60%> <WRAP centeralign> Figure 6-a: Installation without KNXNet/IP routing</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 7-a: Installation without KNXNet/IP routing</WRAP>  </WRAP>
 </WRAP> </WRAP>
 <WRAP column half> <WRAP column half>
 {{ :knxnet_ip_5c.png?direct500 |Installation with KNXNet/IP routing}} {{ :knxnet_ip_5c.png?direct500 |Installation with KNXNet/IP routing}}
-<WRAP center 60%> <WRAP centeralign> Figure 6-b: Installation with KNXNet/IP routing</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 7-b: Installation with KNXNet/IP routing</WRAP>  </WRAP>
 </WRAP> </WRAP>
 </WRAP> </WRAP>
  • knxnet_ip.txt
  • Last modified: 2020/01/28 08:40
  • by wikiadmin