KNX application examples - Metasys - LIT-12013148 - System Integration - KNX Vendor Integration - 13.0

Network Engine Commissioning for KNX Vendor Integration Application Note

Brand
Metasys
Product name
KNX Vendor Integration
Document type
Application Note
Document number
LIT-12013148
Version
13.0
Revision date
2023-10-18
Language
English

The maximum number of field buses, devices per trunk, objects, KNX group address, KNX multicast addresses, and KNX IP gateways per network engine depends on the specific network engine model series. Refer to Table 1 for specific details.

The KNX integration supports two connection modes:

  • For Tunneling mode, use a KNX IP interface. Depending on the interface that you use, this mode can support simultaneous KNXnet/IP tunneling connections. Refer to Table 1 for guidelines and limitations.
  • For Routing mode, use a KNX IP router that acts as a line or area coupler using the multicast KNXnet/IP function.

In Tunneling mode, the KNX integration connects to a specific KNX IP device and monitors group addresses on the KNX line connected to that KNX IP device. Each device in the KNX integration represents a single, unique KNX IP device. See Figure 1 for an example of tunneling mode.

Figure 1. Devices connected to an SNC25150-0 using a KNX IP interface - Tunneling mode

In Routing mode, the KNX integration is not connected to a specific KNX IP device, but to a network of KNX IP routers. The network engine uses the KNX multicast IP address to access group addresses on all KNX lines on the network. See Figure 2 for an example of routing mode.

Note: Because the engines are connected to a multicast IP address and not to a specific device, it does not indicate if the Ethernet or KNX line connection fails.
Figure 2. Devices connected to an SNC25150-0 using KNX IP routers - Routing mode