Topology EN0223a

KNX TP Topology
KNX Association
KNX BASIC COURSE
Table of Contents
1 Introduction ...............................................................................................................................4
2 Topology - Overall view .............................................................................................................5
3 Topology – Line segment ...........................................................................................................6
4 Topology – Area.............................................................................................................................7
4 Topology - Several areas (Network) ...........................................................................................8
5 Individual address ......................................................................................................................9
6 Coupler - Gate function ............................................................................................................10
7 Coupler - Block diagram ...........................................................................................................11
8 Coupler - Fields of application ..................................................................................................12
9 Connecting several lines...........................................................................................................14
10 Practical example for explanation of functionality ..................................................................15
11 Internal line telegram ..............................................................................................................16
12 Line-crossing telegram .............................................................................................................17
13 Area-crossing telegram ............................................................................................................18
14 Coupling unit: Routing counter ................................................................................................19
15 Topology –Structure in building ...............................................................................................20
16 Backbone- /Line coupler classical structure .............................................................................21
17 KNX - Internal and external interfaces .....................................................................................22
18 Taking into account higher telegram rates: IP Network ..........................................................23
19 Line couplers replaced by KNXnet/IP routers ...........................................................................25
20 Limits to the use of KNXnet/IP routers .....................................................................................26
21 Segment Coupler......................................................................................................................27
21.1 Reasons for the introduction of segment couplers ..........................................................27
21.2 Main differences..............................................................................................................27
21.3 Further repercussions on ETS ..........................................................................................30
KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

KNX TP Topology 0043bdec533bf31501a00df812f6cfa296071fc1b47d7815c95194699eddf8aa 2/34
KNX BASIC COURSE
In this chapter, the following abbreviations are used:
BC = Backbone coupler
LC = Line coupler
DVC = Bus device
LR = Line repeater
PS/Ch = Power supply with choke
S = Brightness sensor
RC = Routing counter

KNX BASIC COURSE
1 Introduction
A distinction shall be made between KNX installations that were planned and commissioned up to
2018 and those that were planned and commissioned later, i.e. from 2019 onwards.
1990
… 2018 2019
64 TP devices can be mounted in one line segment 256 TP devices can be mounted in one line
segment
Line segment can be extended with 3 other line Line repeaters not required if cable length
segments thereby using KNX line repeaters is max. 1000 m.
If cable length is beyond 1000 m., then it

is allowed to mount 256 TP devices
distributed over the several line segments
(by using max. 3 line repeaters)
Until 2018 (including):

Only 64 TP devices can be mounted in one line segment. A segment can however be extended by 3
other line segments thereby using 3 line repeaters so that a line consists of up to 4 line segments.
After that
In newer installations, it is also allowed to mount 256 TP devices in one line without the use of line
repeaters.
Important notes:
 If you can install all 256 TP devices on a cable length of 1000 m, then there is no need to install
any line repeaters. If, however, your installation requires a cable length longer than 1000 m., (for
these 256 devices), then you have to install for every further line segment of 1000 m., a line
repeater (max. 3 line repeaters, max. cable length = 4000 m in total).
 If a line is split into several parts by means of line repeaters, then this is referred to as “line
segments”. Up to 4 line segments form a “line”.
 The topology of installations that were erected before 2019 shall be left untouched and no
additional devices beyond 64 shall be installed in one line segment.
 A line repeater is the same hardware as a line- /backbone coupler. It is the loaded application
program and its corresponding individual address that determine whether the hardware
becomes a “line repeater”, a “line coupler” or a “backbone coupler”.
 Newer products are regarded to be “TP-256” compliant, meaning that they allow 256 TP devices
to be mounted in one line segment. Older products are not necessarily TP256 compliant. This
explains the reason for distinguishing older installations from newer installations. It is not
possible to read from the label, whether the product is TP64 or TP256 compliant.

KNX BASIC COURSE
The number of devices that can be installed in one line also depends on the power consumption of
every installed device. The power consumption of all mounted devices may not exceed the output
current of the installed power supply unit.
From ETS6 onwards, the new concept of segment couplers is introduced.
In the below, the explanation focuses on explaining the regular cases, which are either:
 Installations with:
o Lines that do not consist of multiple line segments
 All 256 devices are mounted in one single line segment.
 Or installations with:
o Several line repeaters:
 Dividing the 256 devices over several line segments.
Clause 21 then focuses on explaining the differences introduced by the segment coupler.
2 Topology - Overall view
Backbone line
BC DVC 1 DVC BC
x.0.0 241 15.0.0
Main line
BC LC
x.x.0 x.x.0
DVC 1 DVC 1
x.x.1 x.x.1
Maximum Maximum
255 devices 255 devices
DVC 255 DVC 255

x.x.255 x.x.255
Figure 1: Maximum topological size of a KNX TP installation
In the above figure, the maximum topological size of a KNX-TP installation that is realized after 2019
is shown.
In the below illustrations, the details of a KNX TP installation are described one by one.
In the below explanation and in several other chapters of this course documentation, the following
terminology is used:
KNX BASIC COURSE
 Primary line: this term refers to the upper segment of a line or backbone coupler, the “North”
side, e.g., in case of
 a line coupler, this is the main line;
 an IP router, this is the IP side.
 Secondary line: this term refers to the lower segment of a line or backbone coupler, the “South”
side, sometimes also referred to as the sub line, e.g., in case of
 a line coupler, this is the line itself.
 an IP router, this is the TP side.
3 Topology – Line segment
DVC DVC
256
DVC 1 DVC
Line segment
DVC
Ps/Ch DVC
DVC DVC DVC
Figure 2: Topology - line segment
Maximum 256 devices can be mounted in one line segment.
By means of telegrams, each bus device (DVC) can exchange information with any other device. Each
line segment requires its own appropriate power supply1.
The actual number of devices per line segment depends on the power supply selected and the power
required by the individual devices. The bus cable can be branched at any place.
The following structural types are allowed: star, line (also called daisy chain) and tree structures (also
in combination). A ring structure (also called loop) is however not allowed. A tree structure allows
saving wiring material.
The smallest unit in the TP topology is the line segment.
1 This chapter assumes the use of centralized power supply units only. For decentralized power supply units,
consult chapter “Installation”.

KNX BASIC COURSE
4 Topology – Area
Main line = line 0

Ps/Ch
LC 1 LC 15
DVC 0 DVC
0
Ps/Ch Ps/Ch
DVC 1 DVC 1
DVC DVC
255 255
Line 1 Line 15
Figure 3: Topology – area
If more devices have to be mounted than one can fit into one line, then up to 15 lines can be
connected to a main line via line couplers (LC). This line structure is called an area.
As the line couplers used topologically belong to the secondary line, the maximum number of bus
devices in the main line decreases – due to the energy consumption – by the number of mounted
line couplers (see

KNX BASIC COURSE
Coupler - Block diagram).
This means that it is possible to topologically address and connect a maximum of 256 bus devices on
the main line, including the mounted line- or backbone couplers (maximum 16).
Each line and also the main line requires its own KNX power supply unit.
In this topology, more than 4,000 devices can be installed.
Line repeaters may not be used in main lines, also not in installations before 2019.

KNX BASIC COURSE
4 Topology - Several areas (Network)
Area 15
BC 15
Area 2
BC 2
Area 1
BC 1
PS/Ch
Main line
PS/Ch
DVC 1
LC 1 LC 1
DVC 0 DVC 0
DVC 1
DVC
PS/Ch PS/Ch
255
DVC 1 DVC 1 Line 15

DVC
255
Line 15
DVC DVC
255 255
Line 1 Line 15
Line 15
Line 1
Figure 4: Topology - several areas
If even more devices have to be mounted in a KNX installation, then the TP installation can be
extended by mounting backbone couplers (BC) to the backbone line.
As the used backbone couplers belong topologically to the secondary (main) lines, the maximum
number of bus devices on the backbone line decreases – due to the energy consumption – by the
number of mounted backbone couplers (see

KNX BASIC COURSE
Coupler - Block diagram).
Line repeaters may not be used on backbone lines, also not in installations before 2019. The
backbone line requires its own KNX power supply unit.
Even in the backbone it is possible to create lines that are directly coupled to the backbone (e.g., line
0.1 to 0.15 respectively). However, this should be avoided in the case where the installation contains
also other areas.
By dividing the KNX TP installation into lines and areas, the functional reliability is increased
considerably.
This means that it is possible to topologically address maximum 256 bus devices including the
mounted backbone couplers on the backbone line
In this topology, more than 61,000 devices can be installed in a complete TP-Network.
5 Individual address
PS/Ch
Backbone line
BC 1 DVC BC 15
1.0.0 0.0.>0 15.0.0
DVC
1.0.>0
PS/Ch
Main line
LC 1 LC 15
1.1.0 1.15.0
PS/Ch PS/Ch
DVC 1 DVC 1
1.1.1 1.15.1
Line 15
Line 1
DVC 255 DVC 255

AREA LINE 1.1.255 BUS DEVICE 1.15.255
A A A A L L L L B B B B B B B B
0...15 0...15 0...255
Figure 5: Individual address (situation showing an installation planned and commissioned after 2019)

KNX BASIC COURSE
The individual address serves to clearly identify the bus device and describes its location within the
topology.
A = 1…15 addresses the areas 1…15

A = 0 addresses the bus devices on the backbone line
L = 1…15 addresses the lines 1…15 in the areas defined by A

L = 0 addresses the main line of the respective area
B = 1…255 addresses the bus devices on the line defined by L

B = 0 addresses the line coupler in the respective line
The individual address of an unloaded bus device is 15.15.255.
New bus devices are typically delivered ex-factory with the individual address 15.15.255.

KNX BASIC COURSE
6 Coupler - Gate function
Primary line
Line coupler or backbone

coupler
Filter table
Secondary line
Figure 6: Coupler: gate function
If a coupler (line -/ or backbone coupler2) is used in the installation and the correct individual
addresses are assigned to the corresponding couplers, a filter table will be automatically created in
ETS for the respective couplers during the planning and design stage.
This filter table contains the active line-crossing group addresses (i.e., all group addresses that are
linked to bus devices on both sides of the coupler).
The coupler routes all received group addresses if these are listed in its filter table.
In this way, each line works independently. Only line-crossing telegrams are routed.
The yellow LEDs on the coupler flicker when a telegram is received on the respective line.
The line repeater passes on all telegrams. Line repeaters do not have a filter table.
2 This also applies for the segment coupler. See clause 21.

KNX BASIC COURSE
7 Coupler - Block diagram
Primary line on bus connector
Coupling
Flash-ROM
Filter table
Controller
RAM Electrical
Telegram buffer insulation 1000 V
LC/BC
2 1
Coupling Secondary line Primary line
Secondary line on bus connector
Figure 7: Line coupler: Block Diagram
The coupler is designed for DIN rail mounting. The primary line as well as the secondary line are
connected via standardized bus connectors.
The line coupler can be programmed both from the primary line as well as from the secondary line.
The couplers can be supplied from the primary or secondary line and only have one controller. If
supplied by the primary line, this has the advantage that the coupler can report a secondary line
power failure.
The couplers are equipped with Flash ROM memory. The couplers galvanically isolate the lines from
each other.

KNX BASIC COURSE
8 Coupler - Fields of application3
Individual address
AREA LINE BUS DEVICE
The coupler is used

as for
>0 =0 =0 Backbone coupler Backbone line / Main line
>0 >0 =0 Line coupler Main line / Secondary line
>0 >0 >0 Line repeater Line extension
Figure 8: Coupler: fields of application
Backbone couplers, line couplers and line repeaters are identical devices. Their tasks depend on the
location and the corresponding assigned individual address.
The coupler can be used as:
Backbone coupler BC  Connection between: backbone line – main line
Line coupler LC  Connection between: main line – secondary line
Line repeater LR  For extending a line by a maximum of 3 line segments with up to 64

additional bus devices and an additional cable length of 1,000 m
(used in installations before 2019)
 For extending a line by a maximum of 3 line segments if the
available max. cable length of 1000 m. is not sufficient for mounting
256 devices (for installations after 2019)
Backbone couplers and line couplers only forward line-crossing telegrams.
The line repeater does not have a filter table and therefore passes on all telegrams.
3 For differences introduced by the segment coupler, see clause 21

KNX BASIC COURSE
It is the assigned individual address that determines a coupler either as a backbone coupler, a line
coupler or a line repeater. The address 1.1.0, for example, defines the device as the line coupler of
line 1 in area 1.
The line coupler monitors the data communication between the main line and the secondary line and
vice versa. Only the telegrams of which the group addresses are stored in its filter table are routed.
Note that in case of individually addressed telegrams, e.g., when ETS downloads a specific device,
backbone as well as line couplers will also know on the basis of their own individual address, whether
the addressed device is supposed to be in its area or line. For instance, in the case where a message
is sent towards device 1.2.20, the line coupler with address 1.3.0 will know that this device cannot be
mounted in its line and will not forward this into its own line. Hence, it is very important that devices
are mounted in the correct line or devices have a correct address belonging to the line in which they
are mounted.

KNX BASIC COURSE
9 Connecting several lines
Switch
PS/Ch Actuator
Line 0
SV/Dr
Switch
PS/Ch LC Actuator
Line 1
2 1
SV/Dr
Switch
PS/Ch LC Actuator
Line 2
2 1
Figure 9: connecting several lines
In an installation consisting of several lines, each line and each line segment must have its own
power supply unit and choke.
The above figure shows power supply units with integrated chokes as well as the line couplers.
Both lines, the secondary line (e.g., line 1) as well as the primary line (line 0) are connected to a line
coupler via standardized bus connectors.

KNX BASIC COURSE
10 Practical example for explanation of functionality
L23
L12
L22
L13
L11
L21
L11 L21 Group addresses
0/2/11 0/2/11
S1
S 5/2/66 5/2/66 5/2/66
P
1
1
P2
5/2/67 5/2/67 5/2/67
L12 L22
Main groups: Middle groups:
0 = central functions 2 = Lighting
5 = e.g. floor 5
L13 L23
P1 P2
P = Push button
L = Lights
S = Brightness sensor
Figure 10: Practical example
The push button P1 shall switch the lights L11, L12 and L13. During configuration, group address
5/2/66 is attributed to the push button. The same group address is also attributed to the actuators
controlling the lamps.
The push button P2 shall switch the lights L21, L22 and L23. During configuration the group address
5/2/67 is assigned to it. Again, the same group address is attributed to the actuators controlling
these lamps.
The brightness sensor S1 shall also switch the lights next to the window (L11 and L21). Group address
0/2/11 is therefore attributed to the sensor as well as to the actuators controlling the window lights
(L11 and L21).
The window lights can therefore be switched via the push button as well as the brightness sensor.

KNX BASIC COURSE
11 Internal line telegram
KNX
5/2/66 5/2/67
P1 5/2/66 L11 L21
0/2/11 0/2/11
P2 5/2/67 L12 5/2/66 L22 5/2/67
S1 0/2/11 L13 5/2/66 L23 5/2/67
Figure 11: Internal line telegram
Pressing push button P1, sends a telegram with the group address 5/2/66.
Although all bus devices listen in when the telegram is transmitted, only the actuators of lamps L11,
L12 and L13 with the same group address 5/2/66 execute the command.
If the brightness sensor (S1) sends the group address 0/2/11, all the bus devices on this line listen in
but only the actuators of the window lights L11 and L21 execute the command.

KNX BASIC COURSE
12 Line-crossing telegram
Main Line
LC 1 LC 2
P1 5/2/66 L13 5/2/66
S1 0/2/11
5/2/67
P2 5/2/67 L21 0/2/11
5/2/66
L11 L22 5/2/67
0/2/11
L12 5/2/66 L23 5/2/67
Figure 12: Line-crossing telegram
If the brightness sensor (S1) is not connected in the same line as the lamp it has to control, it is
necessary to transmit its telegrams via the main line.
By its parameterization, the line coupler LC 2 is aware of the fact that there are bus devices outside
its own “line 2” responding to telegrams transmitted by the brightness sensor. LC 2 therefore routes
the group telegram 0/2/11 onto the main line.
Line coupler LC 1 is aware of bus devices on its “line 1” that respond to the group telegram 0/2/11
and therefore transmits the telegram into its line.
All bus devices on this line listen to the telegram from the brightness sensor but only the actuators
controlling the lights L11 and L21 execute the command.

KNX BASIC COURSE
13 Area-crossing telegram
Backbone line
BC BC
1 2
Main line
LC 1 LC 2
5/2/66 5/2/67
L 11 0/2/11
L 21 0/2/11
P1 5/2/66 0/2/11
S1
L 12 5/2/66 L 22 5/2/67
P2 5/2/67
L 13 5/2/66 L 23 5/2/67
Figure 13: Area-crossing telegram
If brightness sensor S1 is mounted in another area, it can still address all bus devices via the
backbone line.
If the group address 0/2/11 is assigned to the brightness sensor, the telegram is routed to line 1 via
the backbone couplers BC 1 and BC 2 and line coupler LC 1.
The actuators controlling lights L11 and L21 in area 1, line 1 then execute the command.

KNX BASIC COURSE
14 Coupling unit: Routing counter
RC = 3
BC BC
RC = 4 RC = 2
LC LC
RC = 5 RC = 1
LR LR
RC = 6 RC = 0
DVC DVC
Figure 14: Routing counter
The telegram transmitted by the sending device contains a routing counter, of which the initial count
value is 6.
Each line - /backbone coupler or line repeater decrements the routing counter and passes on the
telegram as long as the value has not reached 0. It goes without saying that the filter table entries
are taken into account before the telegram is passed on.
In case of (unintentional) loops in the installation, the routing counter limits the number of circling
telegrams.
If a service device (e.g., ETS), however, transmits a telegram containing a routing counter with the
value of 7, the coupler will not alter this value4. In this case, the filter table is ignored and all couplers
in the installation will route the telegram. It finally reaches the bus devices it is intended for, no
matter which line they are connected to.
4 Newer couplers (as of 2019) may also decrement this value.

KNX BASIC COURSE
15 Topology –Structure in building

Area Line
Area Area No. Comment No. Comment

Line Line 0 Area 0 0 Backbone line
1 2
1.5 Floor 2.5 0 Main line West
5 1 1st floor
Line Line 2 2nd floor
1.4 2.4 1 West wing
3 3rd floor
Line 4 Line
4 4th floor
1.3 2.3
5 5th floor
Line 3 Line
0 Main line East
1.2 2.2
2 1 1st floor
Line Line 2 2nd floor
1.1 2.1 2 East wing
3 3rd floor
1
1 4 4th floor
West East
5 5th floor
wing wing
Figure 15: Division of lines in a medium sized project (example)
After the above theoretical introduction, some practical information.
In an ideal installation, a building planned and commissioned from 2019 will have no more than 256
bus devices per floor (in installations prior to 2018 no more than 64 installed bus devices per floor is
ideal). This means the topology can be structured to match the physical layout of the building with
line numbers corresponding to floor numbers and area numbers corresponding to building – or wing
numbers. Whilst this ideal situation is not always possible, using the building layout to influence the
topology ensures a straightforward installation and increases reliability due to the function, line
couplers performance and the requirement to have a KNX power supply on each line, main line and
backbone line.

KNX BASIC COURSE
16 Backbone- /Line coupler classical structure
Backbone-/ Line coupler

classic
Line 1.5 LC LC Line 2.5
1.5.0 Floor 5 2.5.0

1.4.0 Floor 4 2.4.0

Main line 1.0
Floor 3
Main line 2.0

1.3.0 2.3.0

1.2.0 Floor 2 2.2.0

1.1.0 Floor 1 2.1.0
Area 1 BC BC Area 2
(West wing) 1.0.0 Backbone line 0.0 2.0.0
(East wing)
Figure 16: Backbone- /Line coupler classical structure

KNX BASIC COURSE
17 KNX - Internal and external interfaces
PS/Ch
Backbone line
BC 1 Gateway
PS/Ch Other
Main line = Line 0 systems
LC 1 LC 15
PS/Ch PS/Ch
DVC 1 DVC 1
Line 15
Line 1
DVC DVC
255 255
Figure 17: KNX - internal and external interfaces
KNX is open to be linked to any other system. The backbone line (or any other line) can be connected
via a gateway to e.g., AV system, logic controller, Building Management System, Visualization,
Internet for remote access.
The gateway unit converts the protocol bi-directionally.
By placing gateway devices on the highest line in topology ensures the least amount of traffic is
required on each line to get messages to the external interface.
It is also possible to connect to other systems via serial interfaces or binary inputs and binary
outputs.
In a similar way KNX media couplers are used to connect different types of KNX media (e.g. TP and RF
or IP and TP). It is even possible to connect parts of KNX installation via optical fiber which offers
electrical separation and greater cable lengths.

KNX BASIC COURSE
18 Taking into account higher telegram rates: IP Network
LAN
Router
Network - Switch
KNXnet/ KNXnet/ KNXnet/

IP-Router IP-Router IP-Router
1.1.0 1.2.0 1.1.0
PS/Ch PS/Ch PS/Ch
DVC DVC DVC

1.1.1 1.2.1 1.3.1
DVC DVC DVC

1.1.2 1.2.2 1.3.2
Figure 18: IP Network: higher telegram rates
As explained in the previous paragraph, gateways to other systems can be installed on all levels.
Increasingly, this is requested in projects because of the benefits of integrating systems to KNX or the
customer’s request for centralized control, visualization and remote access. This can lead to an
increased telegram load as control and status feedback of all devices need to be possible from the
highest topology layer. Depending on the size of the project and number of devices, a pure TP
topology may be overloaded as transmission speeds on the main- and backbone lines is limited to
9.600 bits per second.
It is also becoming increasingly important to adapt the KNX topology to connect to IP networks as
more and more external systems allow the connection to KNX over IP. The IP network then takes the
place of main or backbone lines, enabling significantly faster transmission rates for line-crossing
communication (Using “Gigabit” switches, it is possible to transmit data 100.000 times faster). This is
achieved by replacing line - and backbone couplers with KNXnet/IP routers.
As you can see from the above picture, the main line has been replaced by an IP network. This has
the decisive advantage that the bidirectional vertical communication between an external system
and a KNX TP line can run at full speed of 9.600 bit/s. This access rate by the external system is simply
multiplied by the number of parallel KNX TP lines in this scenario. The standardized type of
communication applied here is called “Tunneling” which is commonly used by ETS for programming
over IP. A building control system can be connected simultaneously to several gateways, multiplying
the total data rate.

KNX BASIC COURSE
KNX IP interfaces also offer this functionality however they are installed as a standard line device i.e.,
not at the ‘coupler’ address. Most devices will support multiple ‘Tunneling’ connections, refer to
manufacturer information for the details.
IP can also be used as the direct communication between the individual KNX lines which is often
required on larger projects where greater distances need to be covered or to manage higher bus
loads. The KNXnet/IP router makes use of a procedure that is called “routing”, or the actual line
coupler function.
Principally it works in the same way as routing across a TP main line:
A KNXnet/IP router wanting to send a line-crossing telegram, will send this telegram with a so-called
“Multicast” IP address into Ethernet. All other KNXnet/IP routers are connected to this multicast
address and are able to receive and evaluate this telegram. The normal line coupler function is now
again applied, i.e.
- the comparison with the filter table (group telegrams) or

- the check of the line address (individual addressed telegrams)
resulting in the blocking or routing of telegrams, depending on the case.
Please note the following with regard to multicast addresses:
a) There is a dedicated worldwide registered KNX multicast address, which is pre-programmed

in the software of the KNXnet/IP router. This multicast address can be changed within the
limits of the available address range for IP communication.
b) The network switch and IP router in the LAN network must be fit to handle multicast
telegrams. In case of doubt, you should discuss this matter in advance with your network
administrator.
c) The multicast addresses cannot be used across Internet, except across a VPN connection.
KNX IP interfaces don’t support the Routing function, only KNX IP Routers support both Tunneling
and Routing Connections.
There are also KNX devices designed for remote access which provide a secure connection via a cloud
portal where you can log in to remotely access the system for service/maintenance or visualization
purposes. These devices generally connect to a line as an IP device and don’t offer routing functions.
Most will offer tunneling (includes remote programming) in addition to remote access (group
communication only).

KNX BASIC COURSE
19 Line couplers replaced by KNXnet/IP routers
Line coupler replaced by KNXnet/IP

Router KNXnet/
Line 1.5 KNXnet/ Line 2.5
IP-Router IP-Router
1.5.0
Floor 5 2.5.0
KNXnet/ KNXnet/
Line 1.4 Line 2.4
IP-Router
1.4.0
Floor 4 IP-Router
2.4.0
Line 1.3 KNXnet/ KNXnet/ Line 2.3

IP-Router
1.3.0
Floor 3 IP-Router
2.3.0
KNXnet/
Line 1.2 KNXnet/ Line 2.2
IP-Router
1.2.0
Floor 2 IP-Router
2.2.0
KNXnet/ KNXnet/
Line 1.1 IP-Router
Line 2.1
IP-Router
1.1.0 Floor 1 2.1.0
Area 1 Area 2
Network
(West wing) (East wing)
(LAN)
Figure 19: Our picture again: line couplers have been replaced by KNXnet/IP routers. This picture
represents the underneath explained case 1.
The KNXnet/IP router can be used as a line coupler as well as a backbone coupler. If the KNXnet/IP
router replaces the line coupler, all main lines and basically also the backbone line are replaced by
Ethernet (Case 1).
If backbone couplers are replaced by KNXnet/IP routers, the normal line couplers can remain, as only
the backbone line is replaced by Ethernet (Case 2).
Which case is more appropriate depends on the telegram rate requirements on main – and backbone
lines or may be based on the physical installation requirements.
Theoretically, a third case is possible, as a combination of case 1 and 2, with normal TP areas with a
KNXnet/IP router on top and also with lines with IP routers instead of line couplers. This option
should however be chosen in exceptional cases. The topic is described in more detail in the KNX
advanced course.

KNX BASIC COURSE
20 Limits to the use of KNXnet/IP routers

Even if the high bit rate on the Ethernet enables high telegram rates and minimizes telegram losses,
one should not thoughtlessly program bus devices with telegram transmission rates that are too
high. The higher speed of Ethernet will not help if, for instance, telegrams are sent out
simultaneously from all lines into one single line.
To explain it with a metaphor: the case would be similar to all cars accessing a 1.000 lane motorway
via 100 entries but all of them also wanting to exit via a single lane exit.
This is a common problem of all mesh structured data networks; it is not limited to KNX.
By placing devices correctly in the topology, using filter tables in ‘coupler’ devices and considering
the impact of feedback telegrams and cyclical transmissions, you will be able to prevent a very
unlikely but still possible loss of data.

KNX BASIC COURSE
21 Segment Coupler
21.1 Reasons for the introduction of segment couplers
- When one wishes to extend a TP installation with some RF devices, especially in the case of
existing installations, until the introduction of segment couplers this requires that the media
coupler is installed in the main line. In the case one only has a single line (typically 1.1), a main
line does not even exist. Hence, the need was seen that a TP line can be branched off, to include
a couple of RF devices.
- In case you wanted to connect many smaller TP islands, each with only a handful of devices, this
was previously only possible via an IP backbone line. However, this limited the number of such
TP islands to not more than 240 (all IP routers of all lines from 1.1 result in 225, plus all IP routers
below the backbone line, i.e. 0.1.0, 0.2.0 etc. = 15 more). This is referred to as the “hotel
scenario”.
- The introduction of filters between different segments of a line, which does not exist when using
TP line repeaters.
21.2 Main differences

In theory the concept of segment couplers for TP already existed, i.e., the TP repeaters. These
repeaters allowed to physically subdivide a line into a main segment and up to three subsegments.
However, these line repeaters have two limitations:
- They are unaware whether or not a device with a specific address is located in its own
subsegment or not;
- Therefore, there is also no possibility for such devices to forward messages only to devices
that are located in their subsegment. They simply forward all traffic, even if no one is
listening to these messages in their segments. There is no filter table in repeaters. All traffic
of all devices - even if located in different segments - can be heard by all others in that line.
Since ETS6 introduced the concept of segment couplers, each line has
- Exactly one main segment;

- any number of subsegments that are:
o coupled to the main segment by a segment coupler;
o can be of the same or even a different medium type.
For instance, an RF subsegment can in this way be coupled to the TP main segment.
This implies that a device with individual address 1.1.44 can now be an RF device that
is sitting in an RF subsegment, behind a TP-RF segment coupler, which is in itself
coupled to the main TP segment.
In the main segment, one can add one single coupler (backbone or line coupler with device address
0) as well as any additional devices (with device address different from 0)5.
5 Because of this new rule, ETS5 converted projects not respecting this rule must be corrected if you wish to
copy such lines.

KNX BASIC COURSE
To all subsegments you can add exactly one segment coupler and any number of additional devices
(which then all have device addresses different from 0), thereby taking into account the maximum
number of bus devices for lines.
When adding a coupler to a line that has line/segment coupler functionality, this will automatically
create a main segment. If adding a second or third such device to the same line, this will
automatically create a subsegment.
If adding a TP/RF segment coupler to a main segment, ETS will automatically create an RF
subsegment. If the segment coupler type does not match the medium, naturally such devices can
then not be added.
Devices are explicitly attributed to a particular segment. Specific address ranges for different
segments are not imposed, meaning that devices 1.1.77 and 1.1.90 could be part of the first
segment, while device with address 1.1.85 could be part of the second segment.
Although one can create any number of subsegments, needless to say that also overall in a line not
more than 256 devices (including all couplers) can be placed.
Installation
Installation
Area
Main Line
BC Line
a.0.0
a.0
.0 Line
LC a.l
a.l.0
.0
Main Segment
Sub-Segment
Sub-
SC Segment
Segment
a.l.x
a.l
.x
Backbone
Backbo
SC
a.l
a.l.y
ne
.y
Figure 20: Segment coupler and segments

KNX BASIC COURSE
For segment couplers, the table as shown in clause 8 needs to be extend to:
Individual address
AREA LINE BUS DEVICE
A L B Coupler used as Coupler used for GA Filter IA Filter
>0 =0 =0 Backbone coupler Backbone line/Main Line Yes Yes (implicit)
>0 >0 =0 Line coupler Main Line/Secondary Line Yes Yes (implicit)
>0 >0 >0 Line Repeater Line Extension No No
>0 >0 >0 Segment Coupler Extra segment Yes Yes
Figure 21: Total overview of all coupler types
The above table implies that:
- for group addressed telegrams, there is indeed the need to also download a filter table in a
segment coupler. As for other coupler types, this table will be prepared in the background by
ETS, as ETS keeps track of which group addresses are linked to which devices in which
segment;
- for individual addressed telegrams (e.g., ETS towards a device to be downloaded), the
segment coupler also has the knowledge of which devices with which individual addresses
are located in its own segment. Backbone or line couplers know this because of their area
and line codes, segment couplers will be loaded with this knowledge by ETS depending on
whether or not you have placed devices in their subsegment in the topology. Hence, each
time you add a new device to its subsegment or would change its individual address, you
need to reload the segment coupler. In the case where you temporarily connect an interface
to a segment (e.g., for diagnostic reasons), ETS will also temporarily add its own address to
the individual addresses to be (temporarily) filtered in the segment coupler.
Please note that naturally in case of TP, every segment continues to need the required power supply,
to supply the devices in that segment.

KNX BASIC COURSE
21.3 Further repercussions on ETS
Figure 22: ETS Topology View with segment couplers
There is now an explicit color coding used from ETS6 onwards to distinguish the medium type of the
different segments: green for TP, orange for RF and blue for IP.
When selecting a line from ETS6 onwards, not only the devices will be displayed, but now there is
also an explicit Tab with the segments belonging to that line.
In the device info of the segment couplers, it is now also possible to preview the group address filter
table and the physical address filter table.
The below shows a TP Line (green rectangle) containing a number of devices (red rectangle)
connected to the TP main segment, in which there is also an RF segment 1 with a number of RF
devices, including the TP/RF segment coupler (orange rectangle).

KNX BASIC COURSE
Figure 23: TP Line with TP devices and an RF subsegment
The below shows a TP area, with a number of lines, of which the 1.2 line contains a line coupler 1.2.0
(red rectangle) and also a number of segments: by dragging and dropping a coupler with repeater
functionality on this line, another segment is created, and the repeater is added to that (green
rectangle).
Figure 24: Adding repeater to TP line automatically creates subsegment
The below shows a TP Segment directly sitting in the IP backbone with an IP-TP segment coupler
added to it (red rectangle). In the case where devices are placed into this segment, one can then
copy the entire segment and use the “paste special” function (copying it x times) in the backbone and
thus realize the “hotel scenario” use case that is mentioned in clause 21.1.

KNX BASIC COURSE
Figure 25: Realizing the “hotel scenario” use case


Topology EN0223a

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Topology EN0223a

Uploaded by

Copyright:

Available Formats

KNX TP Topology

2 Topology - Overall view .............................................................................................................5

3 Topology – Line segment ...........................................................................................................6

4 Topology - Several areas (Network) ...........................................................................................8

5 Individual address ......................................................................................................................9

6 Coupler - Gate function ............................................................................................................10

7 Coupler - Block diagram ...........................................................................................................11

8 Coupler - Fields of application ..................................................................................................12

9 Connecting several lines...........................................................................................................14

10 Practical example for explanation of functionality ..................................................................15

11 Internal line telegram ..............................................................................................................16

12 Line-crossing telegram .............................................................................................................17

13 Area-crossing telegram ............................................................................................................18

14 Coupling unit: Routing counter ................................................................................................19

15 Topology –Structure in building ...............................................................................................20

16 Backbone- /Line coupler classical structure .............................................................................21

17 KNX - Internal and external interfaces .....................................................................................22

18 Taking into account higher telegram rates: IP Network ..........................................................23

19 Line couplers replaced by KNXnet/IP routers ...........................................................................25

20 Limits to the use of KNXnet/IP routers .....................................................................................26

21.1 Reasons for the introduction of segment couplers ..........................................................27

21.2 Main differences..............................................................................................................27

21.3 Further repercussions on ETS ..........................................................................................30

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

In this chapter, the following abbreviations are used:

DVC = Bus device

PS/Ch = Power supply with choke

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

If cable length is beyond 1000 m., then it

Until 2018 (including):

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

From ETS6 onwards, the new concept of segment couplers is introduced.

2 Topology - Overall view

DVC 255 DVC 255

Figure 1: Maximum topological size of a KNX TP installation

 a line coupler, this is the main line;

 an IP router, this is the IP side.

 a line coupler, this is the line itself.

 an IP router, this is the TP side.

3 Topology – Line segment

DVC DVC DVC

Figure 2: Topology - line segment

Maximum 256 devices can be mounted in one line segment.

The smallest unit in the TP topology is the line segment.

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

Main line = line 0

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

Coupler - Block diagram).

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

4 Topology - Several areas (Network)

DVC 1 DVC 1 Line 15

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

Coupler - Block diagram).

DVC 255 DVC 255

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

A = 1…15 addresses the areas 1…15

L = 1…15 addresses the lines 1…15 in the areas defined by A

B = 1…255 addresses the bus devices on the line defined by L

The individual address of an unloaded bus device is 15.15.255.

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

6 Coupler - Gate function

Line coupler or backbone

KNX: Smart home and building solutions –Global.Secure.Connected KNX Association

7 Coupler - Block diagram