Table of Contents

Thinknx Server with KNXnet/IP Interface

Introduction

Enabling KNXnet/IP on the server allows you to program and connect to the KNX bus over IP. In addition to the normal operation of the server as a visualization tool, and depending on the configuration, it can be used as a:

Thinknx server with KNXNet/IP interface

Figure 1: Thinknx server with KNXNet/IP interface

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 KNXnet/IP service is only available on servers using firmware 1.1.10.13 or up.

Enabling KNXNet/IP interface

This service can be enabled from Thinknx UP Configurator (version 1.3.0.11 or up) or by accessing the server's web page and overriding the project's configuration.

Using UP Configurator

Go to the System tab, and click on System. The below parameters are available to edit in the Properties window:

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.

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

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.

Enabling KNXNet/IP Interface from Configurator

Figure 2: Enabling KNXNet/IP Interface from Configurator

Using the webpage

Click on Server, and select Network and KNX. This page will allow you to modify the network and KNX settings of the server.

Accessing Network and KNX

Figure 3: Accessing Network and KNX

Scroll down to reach the “KNX Settings”. By default, the web page will show the KNX configuration uploaded with the Thinknx project.

Viewing the KNX settings

Figure 4: Viewing the KNX settings

If you wish to override these settings, click on “Overridden”.

Editing the KNX settings

Figure 5: Editing the KNX settings

The below parameters are available to configure:

When using the server as a KNX/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.

The “Clients Physical Address base” and “Client number” are only available to be used with Thinknx Envision

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.

Application 1: Thinknx server as KNXnet/IP Interface

This option permits to use the Thinknx Server as a visualization server as well as a KNXNet/IP interface (without routing).

Scanning server from ETS

Figure 6: Scanning server from ETS

Application 2: Thinknx server as KNXnet/IP Router

This option permits to use the Thinknx Server as a visualization server as well as a KNXNet/IP router, combining two devices in one, as seen in the diagram below.

Installation without KNXNet/IP routing

Figure 7-a: Installation without KNXNet/IP routing

Installation with KNXNet/IP routing

Figure 7-b: Installation with KNXNet/IP routing

To use the server as KNXNet/IP router:

Be aware of the KNX physical address to be given to your Thinknx server. It should follow the topology of your KNX installation.