KNXnet/IP Router Communication

Small-sized KNX Installation

Message routing configuration

  • Add dummy devices at KNX line 1.1.0 to which all the Desigo CC needed group addresses of the other KNX lines will be linked. In this way, the ETS generates the correct filter tables automatically.
  • Do not use the option “forward all”.
  • If filtered message routing is activated on the KNXnet/IP routers, in the KNX adapter, you must configure one KNXnet/IP router only.

 

NOTICE
Communication overload

Message forwarding must be set suitably in order to avoid traffic overload and a collapse of the KNX line and KNX adapter due to message increase.

 

Medium or Large KNX Installation with Multicast Routing Between KNX Lines

Message routing configuration

  • The connection between Desigo CC and the KNXnet/IP routers works through the KNXnet/IP tunneling connection.
  • No configuration for forwarding telegrams through ETS is necessary (no check of “Pass Through Line Coupler” option), since this functionality relates exclusively to forwarding messages through the multicast connection.
  • Always use the option “filter” and not “forward all”.
  • If the filter option for multicast routing is activated on the KNXnet/IP routers, in the KNX adapter, you must configure as many KNXnet/IP routers as required.
    The KNX adapter will receive the forwarded messages from the KNXnet/IP routers configured in the routing table that have the group address to which the message refers.

 

NOTICE
Communication overload

Message forwarding must be set suitably in order to avoid traffic overload and a collapse of the KNX line and KNX adapter due to message increase.

 

Medium or Large KNX Installation without Multicast Routing Between KNX Lines

Message routing configuration

  • KNX installation with separate, independent KNX lines that do not use multicast routing between KNX lines.
  • If message routing is disabled on the KNXnet/IP routers, in the KNX adapter, you must configure as many KNXnet/IP routers as required.