Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| system_objs [2020/01/14 10:12] – [System] ingrid | system_objs [2020/01/14 20:37] – [System] ingrid | ||
|---|---|---|---|
| Line 84: | Line 84: | ||
| * **Server client port** Number of the TCP port needed to remotely connect with the server (outside the server network). The default port is 7550. | * **Server client port** Number of the TCP port needed to remotely connect with the server (outside the server network). The default port is 7550. | ||
| * **Local IP address** IP address (for example 192.168.X.X) needed to connect with the server from clients that operate in the server LAN. | * **Local IP address** IP address (for example 192.168.X.X) needed to connect with the server from clients that operate in the server LAN. | ||
| - | * **KNXNet/IP interface** if enabled, the Thinknx server can be used as a KNXNet/IP interface, allowing KNX programming from the ETS software for example. | + | * **KNXNet/IP interface** if enabled, the Thinknx server can be used as a KNXNet/IP interface, allowing KNX programming from the ETS software for example. More information are available on the [[knxnet_ip| KNXnet/IP]] guide. |
| * **KNXNet/IP different IP** if enabled, permits to choose a different KNXNet/IP interface to connect and access the KNX bus. | * **KNXNet/IP different IP** if enabled, permits to choose a different KNXNet/IP interface to connect and access the KNX bus. | ||
| * **Clients Ph. Address Base** base physical address for the clients connections. | * **Clients Ph. Address Base** base physical address for the clients connections. | ||
| * **Client number** number of supported client tunnel connections. | * **Client number** number of supported client tunnel connections. | ||
| - | * **KNXNet/IP router** If enabled, the server will also route traffic from TP to multicast IP and thus can be used the same way as a line coupler. | + | * **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. More information are available on the [[knxnet_ip| KNXnet/IP]] guide. |
| * **System name** Name to identify the project once it has been uploaded to the server. | * **System name** Name to identify the project once it has been uploaded to the server. | ||
| * **Location** Name of the location where the system is installed. | * **Location** Name of the location where the system is installed. | ||