JUBAIL INDUSTRIAL COLLEGE

KNX Automation System

( Students Manual)
Presented as Senior Project 381# by:

Jehad Almateeq – 362900846

Abdullah Alalwan – 362901004
Abdullah Alabbad – 362900996

Supervised by: Mr. Shadi Mansi

 Experiment 1
Introduction to Building Automation System / KNX

1.1 The KNX BUS in a Nutshell

KNX is a standardized communication protocol for intelligent buildings. KNX is the successor of
three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European
Installation Bus (EIB or Instabus).

In contrast to a standard electric installation, there is no hard-wired connection between the control
units and the power supply, for example, a light switch is not directly connected with the respective light.
Instead, devices and electric assets are connected via the BUS, which runs on 28 Volts. All BUS devices can
be programmed with one common tool, thus, the KNX BUS allows an easy and very flexible installation,
and even subsequent changes can be done easily without changing the wiring.

A KNX system requires the following components, see Figure 1.1:

 Power Supply for the power of the installation

 Sensors (push buttons, thermostats, air speed meters, etc.) that generate commands as telegrams
 Actuators (switch relays for lights, blinds, etc.) that receive the telegrams and perform certain
actions
 The BUS that connects all Sensors and Actuators

Figure 1.1: KNX components

 As a result, the building automation provides a variety of control and power management to any
facility. This includes Lighting, building, and shutters, security, energy management, HVAC, monitoring,
remote control, metering, audio/video control, appliances. Figure 1.2 illustrate all of these items with their
symbols

Lighting Blinds & Shutters Security Energy Management HVAC

Metering Audio/Video
Monitoring Remote Appliances
Control
Control

Figure 1.2: KNX application

KNX Communication Medias

KNX is designed to be independent of any particular hardware platform. In the easiest

possible way, an 8-bit microcontroller can realize the desired function, for more complex
functionalities a PC may be necessary, according to the needs of a particular implementation. The
most common transmission medium in KNX are twisted pair, but KNX also provides another
physical communication medium as shown in Figure 1.3:

Figure 1.3: KNX Communication Media

 It is possible to combine - by default normally incompatible media - via KNX media couplers.

1.3 BUS Topology

Each bus device (DVC) can exchange information with any other device using telegrams.
One line consists of a maximum of 4 line segments, each with a maximum of 64 bus devices. Each
segment requires an appropriate power supply. The actual number of devices is dependent on the
power supply selected and the power input of the individual devices.

1.3.1 Area

The smallest entity within the KNX topology is a line segment; it is called a line for short. A line can
contain a maximum of 64 devices. This number is enough for most small scale projects. For larger scale
projects, up to 15 lines can be combined with one area - connected via the main line. Different lines may be
connected to the main line with a Line Coupler to create one area as seen in Figure 1.4.

Main line = line 0

PS/Ch

LC 1 LC 15

PS/Ch PS/Ch

DVC 1 DVC 1

DVC 63 DVC 63

Line 1 Line 15
1st line segment 1st line segment

Figure 1.4: KNX Topology for one area with 15 lines.

Moreover, if it is needed to add more devices in a certain line, then it is possible to do so by adding
Line Repeater (LR) at the end the line. Since it is agreed that the line can handle up to 64 devices, then the
repeater will be considered as the device number 64, and it will accommodate extra 64 devices that will
correspond to the original line. In this case, this original line will have 63 (64- repeater) + 64 = 127 devices.
The maximum line repeaters that can be added to one line are three. Up to 255 KNX end devices may be
addressed in any sub- network. KNX end devices may be numbered from 1 to 255, see Figure 1.5.
 Backbone line

BC BC
DVC 1 DVC 49
x.0.0 15.0.0

Main line
LC
LC
x.x.0

DVC 1
DVC 1
Maximum x.x.1
64 devices
DVC 63 Secondary line (1st line segment)
x.x.63

LR LR LR
DVC 63
x.x.64 x.x.128 x.x.192

3x DVC 65 DVC 129 DVC 193

maximum x.x.65 x.x.129 x.x.193
64 devices

DVC 127 DVC 191 DVC 255

x.x.127 x.x.191 x.x.255

Figure 1.5: One line is extended up to 255 devices.

1.3.2 Several Areas

It is also possible to connect up to 15 areas to a backbone. Single areas are connected to the
backbone line via a Backbone Coupler (BC). KNX end devices may be connected anywhere in this
topology, Figure 1.6. Within a maximum of 15 functional areas, more than 58,000 bus devices can
be connected to the bus system. By dividing the KNX TP1 installation into lines and areas, the
functional reliability is increased considerably.
Area 15

BC 15

Hauptlinie Area 2
SV/Dr
BC 2

Hauptlinie Area 1
SV/Dr LK 1 LK 15
BC 1
PS/Ch
SV/Dr Main line SV/Dr
PS/Ch LK 1 LK 15

TLN 1 DVC 1

SV/Dr SV/Dr
LC 1 LC 15

TLN 1 DVC 1

PS/Ch PS/Ch
TLN 63 DVC 63
DVC 1 DVC 1
Linie 1 Line 15
1. Liniensegment 1st line segment
TLN 63 DVC 63

Linie 1 Line 15
1. Liniensegment 1st line segment
DVC 63 DVC 63

Line 1 Line 15
1st line segment 1st line segment

Figure 1.6: KNX Topology for 15 areas with 15 lines each.

 1.4: Simple Example

A very straightforward example of a lighting control is the engaging of a single light. The first device
we need to install is the power supply. A KNX BUS needs to be provided with a 28 V direct current. The
actual circuit breakers are called actuators. They typically come as multi-channel switch actuators, for
example as a 4-fold switch actuator that is equipped with 16-ampere relays. As BUS media, a twisted pair
cable is used to connect all KNX devices to the BUS. Then, a push-buttons sensors consist of a universal
flush-mounted bus coupler and an end bus device. Both devices have to be from the same manufacturer.
This System is shown in Figure 1.7, where its symbol shown in Figure 1.8.

Figure 1.7: A simple example of a power supply connected to switching actuator via a bus system.

Figure 1.8: Symbol diagram for Figure 1.7.

The push button is put onto the bus coupler. The connection is established by a 10-pin connector, the
so-called "Physical External Interface", Figure 1.9.

Figure 1.9: Push-Button is connected to the Bus-Coupler in one package.

 Last but not least, it is needed to connect the high voltage current. The power supply, as well as the
switch actuator, gets wired to the power circuit, as shown in Figure 1.10.

Figure 1.10: A complete example of using KNX components to control a light.

1.5: Physical Address

Each device connected to a certain topology needs to be uniquely identified by an address. This
address is called Individual Address or “Physical Address”. The individual address serves to identify
clearly the bus device and describes its location within the topology. The address has three parts. The first
part corresponds to the area number. Where the middle part is related to the line number. The final part is
for the device number in the line. For example, a switching actuator has an address (5.3.12) means that this
device located in area 5, connected to line 3 of that area, and the device number in that line is 12. Figure
1.11 illustrates the physical address for all devices connected to an area.

Figure 1.11: One area topology with devices addresses.

 It is important to mention in this stage that the area has no physical address. Usually, it is identified
by its individual number from 1 up to 15. On the other hand, the power supply will have two parts to
describe its address, such as (1.1). The first part is for the area number, and the other part is for the line
number in the said area. There is no device number for the power supply as it should be for the devices
connected to the line. Furthermore, line couplers’ address will have three parts as any other device,
however, its device number should be 0, such as (1.1.0). Finally, the Line Repeater will have the device
number 64 as it is the last device will be connected to the line, see Figures 1.5 and 1.11.

1.6 Group Address

A Group address has totally different function compared to the physical address. A Group address is
used to give the devices the ability to communicate with each other by sending information and
instructions only to the assigned device/s. Let us recall the example illustrated in Figure 1.10. Obviously,
the system has one power supply to create a line with a physical address (1.1). One switch (called sensor) to
control a light. One switch actuator to power On/OFF the light.

The first thing a designer should consider is to give a physical address to each device so that they can
be identified in the bus system, see Figure 1.12. Remember, each address has to be unique. The suggested
topology that has a power supply, a sensor, and an actuator will have the addresses (5.6), (5.6.1), and (5.6.2)
respectively. On the other hand, assigning group address will have a different purpose.

The group number (1/1) will be assigned to link between the switch and the actuator. So, when the
switch is depressed, it sends a telegram to the bus. All devices connected to the system will receive the
telegram. However, only the device/s with the correct group address will take the action. In this example,
the actuator will be switched ON.

Figure 1.12: Assigning physical and Group addresses.

 There are three structures (formats) to describe the group address as seen in Figure 1.13:

1. Three-Level Structure.
2. Two-Level Structure.
3. Free Structure.

Figure 1.13: Group address structure.

In this course, it is strongly recommended to use the Two-Level structure. On the coming experiments
the following main groups are strongly suggested to be used:

Main group Sub-Group example

(1) for lighting 1 – 10 lights numbers 1/1 or 1/2 … 1/10
(2) for Dimming 1-4 Lights Numbers 2/1 or 2/2 … 2/4
(3) for Central Switch 1 -2 Switch Number 3/1 or 3/2
(4) for Shutter 1-4 Shutter Number 4/1 or 4/2 … 4/2
(5) for Heater 1 -2 heaters 5/1 or 5/2
 1.7 Experiment Set-up:

KNX basic panel

1. Mains input, 230V AC (at rear)

2. Bus power supply, 230V AC / 28V DC

3. USB port, KNX

4. Switch/dimmer actuators, pair

5. 8-pin binary output

6. Blind actuator, pair

7. Dimmer actuator outputs

8. Power supply for modules, 230 V AC

9. Binary switching outputs

10. Blind actuator outputs

11. Bus connection for additional modules

12. Set of 2 universal interfaces, buttons/switches

13. Two push-buttons with bus coupler, programmable: 612x/01

14. Set of 4 push-buttons with bus coupler, programmable: 612x/01

15. Mains switch, 230 V AC with phase tester

KNX room simulation, CO3209-9J

1. Power supply 230V AC

2. Light terminals

3. Dimmer light

4. Terminals for blinds A, B, C, D

 Experiment 2

KNX Project Design Using ETS 4

2.1 Introduction

The project planning, designing, and commissioning of a KNX installation requires a

software tool for building designers and electrical installers. This software should be simple to use
and well structured. KNX Association designed ETS software to do this job. ETS Stands for
Engineering Tool Software (ETS). The version we have in the lab is version 4. However, you may
find updated version in the net. You can only obtain ETS from KNX Association via the internet in
the KNX online shop (address https://onlineshop.knx.org.).
There are four different types of versions available of ETS program. All are a PC-dependent key
or nonPC-dependant dongle (except for the demo):

1. Demo: Full functionality, max. Three devices per project, this version is free of charge.
2. Lite: Full functionality, max. 20 devices per project.
3. Professional: Full functionality, no restrictions as regards number of devices which can be
installed and the number of projects that can be created
4. There is also the Supplementary version. This version is intended as an additional license
for the Professional full version on a second PC (commissioning PC/Notebook).

2.2 ETS Dashboard Window

You can start the ETS by clicking its icon on the desktop. The dashboard is the first window to
appear. From there you can navigate the program setting and configuration, create new projects, check the
devices added to the system, and many other things that will be explained to you later in this experiment.

2.1.1 Dashboard, Overview Tab.

When ETS opened, the Dashboard window appears. The Overview tab is selected by default so that
the fields displayed in Figure 2.1 are visible in the workspace.
You can navigate all old project in the sub-window Project overview and then you can select the
project that need to be edited. In the version Identification sub-window, you access the licensing feature. If
you have an existing connection to the internet, current news about the KNX Association is shown in the
others windows, KNX news, and KNX Products Industries.
 Figure 2.1: Dashboard, Overview selected.

2.1.2 Dashboard, Projects Tab.

All the information related to the old projects can be found on this tab. Moreover, this tab is the place
where you can start a new project by clicking on new as illustrated in figure 2.2

Figure 2.2: Dashboard, Projects Tab.

 2.1.3 Dashboard, Catalogs tab.
The product data of the manufacturers is managed under Catalogs. After the installation, the ETS database
is empty. To be able to work with ETS, product data from the manufacturers must be imported into this
database. The import function of ETS is used for this purpose. The manufacturers’ product databases can
be obtained free of charge on a CD or via the internet. The window that is shown after selecting the
Catalogs tab is displayed again during the project design stage when selecting devices. Figure 2.3 shows all
the manufacturers data imported already to the station

Figure 2.3: Dashboard, Catalogs Tab.

2.1.4 Dashboard, Quick Action Tab.

In the left side of the dashboard window, you will find the Quick Action board. Frequent functions are
available to quick action certain functions, see Figure 2.4. A user can open new projects from this point with
different options. You can simply click on the new project to do so, or you can open the new project with
the assistance of the wizard helper.

Or, you can diagnose you your program and installation as well from the Diagnostics list of options. For
Example, to can check if a certain device is already connected to the bus system by simply clicking the
Individual Address options. A popup window appears as shown in Figure 2.5.

Moreover, you can import an already designed project with all its features from the Import
Project option in the Import Data. The importing process includes building the structure,
comments, group addresses, individual addresses, etc. of the corresponding project. Also, all
required product data of the devices contained in this project is imported as well. You can
retrieve the project import function on the Dashboard via the “Quick Actions” bar and under the
Projects tab via the Import….button.
 Figure 2.4: Dashboard, Quick Actions Board.

Figure 2.5: Individual Address Diagnostic window.

 2.3 Create New Project
A new project can be created on the dashboard via the New Project function of the “Quick
Actions”. The New Project dialog appears on the screen as shown in Figure 2.6. A name must be
entered in this dialog window. The medium that has been used is also specified here (TP for
Twisted Pair, PL for Powerline and IP for Ethernet). If you have selected the function Create Line
1.1, the area 1, main line 1.0 and line 1.1 are created immediately. Otherwise, the project has no
topology structure. Finally, one can set the group address style.

Figure 2.6: New Project window.

2.4 Project Design View

When you open up a project, you access the project design view of ETS. The following screenshot, Figure
2.7, shows the elements of this view.

Figure 2.7: Project Design View.

 The numbers in the screenshot designate the following elements:
1. Menu bar
2. Toolbar
3. Panels
4. Navigation bar (side bar)
5. Status bar

2.5 Topology Window

It is suggested to start any new project with configuring the system topology as a first step in the
designing process. The Topology window is used to define the actual bus structure and the assignment of
individual addresses to the devices. This view can be used simultaneously with other views and displays
the KNX project as regards bus structure. The view shows the devices as they are assigned to the different
lines. Twisted Pair, Powerline and IP lines, and areas are represented with different symbols. This step can
be initiated by selecting the Topology window either from the Workspace option in the options bar or
choosing the topology from the each sub-window options.
Following are the step by step procedures to create a topology for the example discussed in
Experiment 1.

1. To start a topology, you need to

define the area and give it an
assigned number. You start a
new area by clicking on +Add
Area Button.

2. The New Area window

appears. You can give a name
for the area, suggested Area 1,
and the area number.

3. Go to Properties option at the

extreme left of the topology
window and select the area
address. As suggested in
Example 1 of Experiment 1, the
area is selected to be 5.
4. Back to topology tree, click on
Area 1 and then click on +Add
Lines option. A popup window
appears, from there assign an
address to the line. (address 6
for our example), then click OK.

The next step is to choose the devices which will be connected to the bus. To do so, back to
topology tree click on the line you have already created and then click on + Add Devices. The catalog
window appears and from there you can choose the devises you will use by double clicking on the right
device, see Figure 2.8. The devices used in the example are a 6195/31 switch actuator and solo 612X01
switch. The next step is to assign the correct physical address to each new device. In the example, the
addresses are (5.6.2) and (5.6.5) respectively, Figure 2.8.

Figure 2.8: Topology and the catalog configuration windows.

2.6 Group Address Window

The next suggested step in the designing process is to assign the group addressing. Following are
the step by step procedure to assign the Group Addressing.

1. Choose the Group Address

window

2. To start a Group Addressin, you

need to define the main group
and give it an assigned number.
On the Group Address tree,
click on +Add Main Groups
Button.
3. The Add Main Groups window
appears. You can give a name
for the new Main Group, as
suggested in the example
Lighting with the number (1).

4. To select the subgroup address,

go to the Group tree again.
While you are on the new main
group which you have already
created, Lighting, click on +Add
Group Address.

5. The Add Groups Addresses

window appears. You can give
a name for the new sub Group,
We will choose H1 with the
number (1). .

The final Group Address window will look as illustrated in Figure 2.9.

Figure 2.9: the Group Address window after adding the group and the subgroup address.

6. Go to Devices then click on the switch

(5.6.5). After that, move to Parameter
and click on open parameter

7. Choose the number of fold (switch) that

you want to use.
8. Choose 1 fold switch as shown in figure 2.10 because we only need to control one light.
Then, close the page returning to the ETS workplace.

Figure 2.10: The parameter for the switch

9. Drag from switching actuator the binary output that you'll use from the KNX Panel
(Assume: Output A) to the group address H1.

10. Drag from the Switch the rocker switch 1 to the group address H1.
11. Connect the safety lead from binary output A to H1 ( Light Terminal 1) as shown in figure
2.11

Figure 2.11: KNX Panel

12. Navigate to each device that you have (in our experiment we have two devices 5.6.2 &5.6.5)
then right click from the mouse and choose Download then Download Application. See
figure 2.12 below

Figure 2.12: KNX workplace

Note:
Immediately after each download for the application press by specific screw the button of the intended
device that you choose from the KNX panel in order to start the process. See figure 2.13

Figure 2.13: KNX Panel, Pressing the button of the actuator

13. Press the switch to Turn ON the light H1.

 Experiment 3
Application on Building Automation System / KNX

Now you are familiar with the KNX system and you have done example to control one light. Below you
have many applications to do, read each application carefully and build your project.

1.2 Control one light from two different locations.

1.3 Extend your control to be from three locations.

2.1 Control two lights using one switch.

2.2 Extend your connections to add another switch to control the same light.

3.1 Control one light using two different buttons. (Use One Fold)

3.2 Change your indication LED to be:

 ON - Green Light
 OFF - Red Light

4.1 Control two lights using two different push-button. (Use One Fold)

4.2 Change your indication LED to be:

 ON - Red Light
 OFF - Green Light

5.1 Control the lights by using the following procedure: (One Project)

 One light to be controlled by rocker switch.

 Two lights to be controlled from push-button.
 One light to be controlled by one button.
 One rocker switch to turn all the lamps on.
 Experiment 4
Assigning Physical Addresses For Different Devices.

4.1 : Abstract

Every device in a KNX system is assigned a unique number. In order to ensure that sensors
actuators, and devices know which of their command is to be received to realize a specific
function, the device addresses must be assigned.

This address is called “Physical address” and it can be assigned and determined by the user and
then loaded into the device.

In this experiment, you will learn the basics of how to create a new configuration of your
workplace and then to program any application using ETS4 based on your preference.

4.2: The Individual Address:

Any individual address must be unique within a KNX installation. The individual address is
configured as shown above.

It has the following format: Area . Line . Bus device

 The first number denotes the number of the area.

 The second number denotes the number of the line
 The third number is a sequential number indicating
the device’s position in the line.

For example, a device with (5.6.2) address is located in Area 5 and connected to Line 6, Bus 2.

Now this device is identified.

4.3: Set up

1- Make sure your local USB is connected to the module gateway you want to assign address
for its devices.

4.4: Procedures on ETS 4

1- Create a new project.

2- Create a new area start with the number you like. Here we have used Area starting with 5,
which means all the devices that are going to be used in this area will start with the number
5 as an address.
 3- Create a new line start with the number you like. Here we have used line start with 7,
which means all the devices that are going to be connected in this line will start with the
number 7 as an address.

4- Because of the change we have made, the USB local cannot be identified and
communicated properly with the ETS 4 so it has to be redefined. From top taps, go to Settings
and then Communication.

5- Press Local Settings for the first choice.

( It is clear from the figure that the USB local is still using the old address which is “5.6.100” which
is our case is not the correct address)

6- Change the individual address of the USB local to the correct address. ( We already have chosen
the area to be 5, and the line to be 7) We can use 100 as “bus number” to allow a large space for us
and to give the USB local interface a unique address. You can use any number you like.
 7- The next step is to choose the devices which will be connected to the bus. To do so, refer
to experiment 2.
The device used in the example is a UD/S 2.300.2 The Universal Dim Actuator.

8- After connecting the device to the line, the new (area & line) addresses is directly
determined. However you need to check the bus number and give it any special number you like.
Say 1.

Then, Right click on the device < Download < Download Individual Address

Right click on the device

2 1

9- The system now is at pairing mode “see figure below” . The new adjusted address
(5.7.1) is ready to be assigned to any device in your KNX panel. In our case, we chose UD/S
2.300.2 The Universal Dim Actuator to hold (5.7.1) individual address.
10- In the meantime, press by specific screw the button of the intended device that you choose in
order to complete the process.

11- If the process is succeeded, you will notice an indication telling you that the physical address is
loaded to the device.
 Note: Now you can do the same procedure from step 7 to other devices.
After you finish, you can diagnose your program and installation as well from the Diagnostics list of
options. For Example, to can check if a certain device is already connected to the bus system by simply
clicking the Individual Address options. A popup window appears as shown below:

1
 Experiment 5
Simulation of Line Coupling

5.1: Introduction To Couplers

A coupler is a device used to link two lines, or two areas in a same installation to extend the total devices
number. It can also be used as a repeater to extend the device number in one single line.
In this expiremnt, you will simulate a line coupler that links two floors of the same building.

Refer to the topology (Figure 5.1.1), couplers are always supplied by the main line. However, after
couplers there is always a power supply providing voltage to the secondary line. Note that the line
coupler’s address will be always (x.x.0)

Figure 5.1.1 : Topology

ABB Coupler Device

5.2: Line Coupler Simulation Procedures

As mentioned above, in this experiment you

will be able to simulate a coupling of two
floors in the same building using the concept
of KNX Line Coupler.

Refer to the topology (Figure 5.2.1):

You have to know how many power

supplies do you need. A simple line
coupling can be made by using one
main power supply for both lines, two
line couplers devices, and one power
supply for each LC device.

Figure 5.2.1 : Topology

 5.3: Hardware Set-up

1- Connect your circuit to look like this:

2- Turn on the main power supply.

If your connection is correct, you will notice that LC devices and

the power supply unit for each floor are receiving power. (Two
Yellow LEDs indication)
 5.4: Procedures on ETS4

3- Now you are done with the hardware. The next step is the programming using ETS4.

4- From your computer, go to ETS4 and create a new project and name it as ( Line Coupler
Experiment )

5- Create an area Starting with 5 (We will use only one area at this stage) and two lines.

Let the first line starts with 6, which means all the devices that are going to be connected in this line will
start with 5.6.x as an address. Make sure you assign an address for the second line exactly as we did
previously in Experiment 4.

6- Add Coupler for both lines (both floors). Search from Catalogs, the coupler's device name is
6187-104.
6- Now you must identify each coupler with its own line (floor). This can be done by Assigning
Addresses.

Reminder: Couplers’ address will be always (x.x.0). In this example, we used area 5, line 6. So
the first coupler’s address should be 5.6.0 and it belongs to line 6, where the second coupler’s
address should be 5.7.0 and it belongs to line 7.

2
3 3 1

4
3
By doing so, we assign this coupler to be Line 6 ’s
Make sure you assign the correct coupler which depends upon your connection and your
previous assigning for the line.

If these leads which are going out of the coupler are going to line 6 (based on your assigning of the
line module), then this is the right coupler.

LINE 6

7- Do the same thing with the second coupler but time it should be specified to Line 7.
 Experiment 6
Applications on Line Coupling
Now you are familiar with line coupler’s experiment and you have done many examples to
control one light from one line. Below you have applications to do, read them carefully and build
your project.

Q6.1/ Use the concept of line coupler to control the light 4 in room simulation through the
actuator located on line 7 by the solo switch on Line 6 .

The Actuator device number is (6195/31)

The Solo Switch device number is (612x01 solo) – Use 1fold.

Hint: Refer to 2.6 Group Address.

Q6.2/ A. Control any light through the actuator located on line 6 by 1fold solo switch on Line 7
through output A. Use 1fold for the solo switch.

B. And control any light through the actuator located on line 7 by 4fold solo switch on
Line 6 through output B.
 Experiment 7
Simulation of Area Coupling

7.1: Introduction to Area Coupling

KNX systems racing on offer intelligent solutions for networking and controlling home
appliances. Nowadays central control and linking of various functions are needed. Thanks to
KNX technology which provides more comfort, security and energy efficiency in the building.

Previously, we were able to connect two lines/floors in the same building.

There is not much difference between the line coupler and the area coupler except that the area
coupler is more advanced network. It links two KNX areas/buildings to each other for data
transfer. At the end, by dividing the installation into lines and areas, the functional reliability is
increased considerably

7.2: Topology

In practice, area coupler is typically performed using Line Couplers parameterized as area
couplers. The area line is also called the backbone, so it also needs its own power supply (Figure
7.2.1)

Figure 7.2.1 : Topology of Area Coupler

From the topology, The KNX bus can be expanded by means of a backbone line.
The backbone coupler (BC) connects its area to another backbone line in order to expand to
another area.

By doing so, and within a maximum of 15 areas, more than 58,000 bus devices can be
connected to form a complete system and can be controlled independently.
Important: Area Main Line (Backbone Coupler) physical address will be always (x.0.0).

7.3: Guidance Before Building The Project

It is important to look at the topology of your project before starting to build it and before
doing any step. The idea is to know how many power supplies, couplers, etc.. do you need to
construct the project and also to be familiar with the hardware connection.

As discussed earlier, area coupler experiment is typically performed using Line Couplers
parameterized as area couplers.

From previous experiments, you have already constructed a full area consists of devices, line
couplers and you assigned different physical addresses for each of them. Simply, the idea behind
the area coupler is to do the same thing with another area and then you just link/couple both of
the two areas.

Remember that coupling areas together means you will need a backbone coupler for each area
which is basically an additional MAIN LINE with its own coupler and its own power supply.

Caution: Addresses must be specified and assigned correctly as a preliminary part of the experiment
 7.4: Apparatuses and Construction

2 Areas ( Two KNX Panels )

7 Units of Power Supply (This includes one main power supply for each area, two for each Line
Coupler unit, one for Area/Backbone Coupler )
6 Units of Coupler [ 4 for Line Couplers, 2 for Area Couplers (Backbone Couplers) ]
Leads

7.5: Hardware Set-up

1- Connect line coupler experiment for the first area ( Area 4 )

Area 4 has Line 6 and Line 7 as shown:

So far, We used only two units of couplers (4.6.0, 4.7.0). They are line couplers.

We still have 4 couplers left.

 2- Connect line coupler experiment for the second area ( Area 5 )
Area 5 has Line 6 and Line 7 as shown:

So far, we used four units of couplers (4.6.0, 4.7.0 and 5.6.0, 5.7.0). They are line couplers.

We still have 2 couplers left for the area coupling.

 You are done with the construction of the line coupler for each area and what is left now is to couple both
of these areas together.

3- Almost this is how your station and your connection should look like:

Now we will integrate both areas to our network. From the above illustration, we can notice that we will
use normal couplers just like the ones we used with line couplers. However, they are called Backbone
Couplers since they connect two areas.

The only difference between Line Couplers and Area Couplers is the address
Area Coupler address is (x.0.0); Where x is the number of the area.

In any case, follow up until the end of the procedures to clearly understand the idea of addressing.
4- Connect the main power supply of area 5 to the first Backbone Coupler as following:

5- Connect the second Backbone Coupler to the main power supply of Area 4 OR first Line Coupler 4.6.0 (
Same Wire”Figure 7.5.1”) as following:
 Figure 7.5.1: Same wire from the first line coupler to the main power supply of area 4

6- Connect each backbone coupler with Power Supply.

7.6: Addressing

1- In case of an application; for both areas, all controlling devices such as actuators, sensors, switches.. etc
should be address assigned or at least only the devices that you are going to use. Their address is (x.x.x)

2- Line couplers’ address must be (x.x.0), whereas Backbone couplers’ address must be (x.0.0)
3- Sometimes you may encounter an error during assigning address especially between couplers. In order
to avoid this error, start with sequence. For instance, if you want to assign address for 4.7.0, put your USB
local to the gateway of the 4.7.0. After you finish you can do the same thing to 4.6.0.
However, if you want to start with 4.6.0 then there is no gateway for this coupler, so you are forced at first
to put your USB Local to (the main power supply of Area 4)’s gateway. Now since your wires comes out
from the power supply to the 4.6.0 coupler, you are required to start assigning address for 4.6.0 at first, and
then 4.7.0.
“The first x indicates number of the Area, the second x indicates the number of the line, the third x indicates the device
number.”

7.7: Procedures on ETS4

1- Open ETS4, create new project and name it as Area Coupler Experiment.

2- Create the first area, and name it as shown in the figure. Assume it to be Area 4.

3- Add two lines for area 4, the first line is line 4.6 and the second line is 4.7 and make sure you assign the
specific address for each line as we did previously in Experiment 1.
4- Add Coupler 6187-104 and solo 612x/01 switch for both lines.

5- Assign addresses for both couplers in both lines. The line 4.6 should hold a coupler with an address of
4.6.0, and the line 4.7 should hold a coupler with an address of 4.7.0

6- Create the second area, and name it as Area 5.

7- Add two lines for area 5, the first line is line 5.6 and the second line is 5.7 and make sure you assign the
specific address for each line as we did previously in Experiment 1.

8- Add Coupler 6187-104 and solo 612x/01 switch for both lines.
9- Now we will add Backbone coupler for both lines in both areas. Add Coupler 6187-104 to line 6 as
shown:

Drag and drop

10- Change the address of the Backbone Coupler of Area 4 to 4.0.0 from properties. Do not press Park just
left click anywhere in the software.

11- A massage will appear to you asks if you want to create a Main Line. Press Yes.
A main line is created where backbone couplers are located. The figure shows the topology and where
exactly the backbone coupler of Area 4 is located.

12- Repeat procedure 9 to 11 for Area 5.

This is how your topology should look like:

will be completed in experiment 8

 Experiment 8
Application on Coupling
Experiments without applications are meaningless. In this experiment we will review an application
relate to line and area coupler.

8.1: Scenario

Since we have already built a project, we will use it to do the application.

Figure 8.1.1

Group addresses can be used to arrange our desire and to control the required devices without any
miscommunication.

The first main group is related to Area 4 Line Coupling only but not Area Coupling. This falls into one
sub-group which has Actuator from Line 6 and Solo Switch from Line 7 to control a Load through Some
Output.

The second main group is related to Area 5 Line Coupling only but not Area Coupling. This falls into one
sub-group which has Actuator from Line 6 and Solo Switch from Line 7 to control a Load through Some
Output.

The third main group is related to Area Coupling. This falls into two sub-groups. The first one is Area 4
controls Area 5 and the second one is Area 5 control Area 4.
 Figure 8.1.2

Remember from experiment 7; “In case of an application; for both areas, all controlling devices such as
actuators, sensors, switches.. etc should be address assigned or at least only the devices that you are going
to use. Their address is (x.x.x)”

As we can see from the figure 8.1.2, Rocker Switch 4.6.4 2fold is used to control the Actuator 4.6.2 in the
same area to energize a load through output A

Figure 8.1.3

Figure 8.1.3, shows Rocker Switch 5.7.5 2fold is used to control the Actuator 5.6.2 in the same area to
energize a load through output A

Figure 8.1.4
Figure 8.1.4, shows the second Rocker Switch 4.7.5 2fold in Area 4 is used to control the Actuator 5.6.2 in
Area 5 to energize a load through output B
 Figure 8.1.5

Figure 8.1.5, shows the second Rocker Switch 5.7.5 2fold in Area 5 is used to control the Actuator 4.6.2 in
Area 4 to energize a load through output B

Download application for the topology.

Wait and Test.

 Experiment 9

LAN Interface With Line Coupler

9.1: KNX IP Interface

The KNX IP Interface is used as an interface for connecting between the Ethernet network and the KNX system..
This connection is made through Local Area Network (IP).

Connection to the data network allows you to control your devices through tablets/smart phones. It also
allows you to program the Bus over the Internet.

In this experiment, K-BUS IP Interface is used with line coupler to control devices through LAN by using
Android system.

LAN

K-BUS IP Interface Figure 9.1.1: Topology

9.2: Circuit Diagram

1 LAN LINK ON, indicate that network connect normally.

LAN LINK flashing, indicate that telegram traffic is ongoing.
Network activity is indicate by the LED.

2 EIB LINK ON, indicate that KNX bus connect normally.

EIB LINK flashing, indicate that telegram traffic is ongoing, which is
indicate by the LED.

3 Auxiliary power supply connection.

2

4 LAN connection.
3
2
5 Programming LED, LED red light up for assignment
3 of physical address, LED green flashes for indicator of the
Figure 9.2.1: Construction of K-BUS
2 device running normally.

6 Programming Button (For assigning address)

7 KNX bus connection

9.3: Requirements and Installation

- Requirements
1- IP Interface/Router
2. Android 1.6 and above
3- GVS app
4- SD card or flash SD car
5- Internet router/modem
6- Ethernet cable

Installation on Android
1. Run GVS.apk or GVS.phone.apk to Install
2. Create a folder named GVS in the root directory of SD card then copy the file named
config.xml to this folder.
 3- Run the program, then the program will do the initialization (as figure 9.3.2 showing), this will take a
few seconds.

Figure 9.3.1: GVS Program

Figure 9.3.2: Installation of GVS Program

4. The system will try to connect to server, if failed, a dialog box will be show as figure 9.3.3.
If succeed, will be show as figure 9.3.4

Figure 9.3.4: Succeeded connection

Figure 9.3.2: Failed connection

9.3: Requirements and Installation

Installation on your PC :

A program called Mobile Phone Configuration System is already on your PC. This program supports the
use of mobile phone control software .

After assigning group addresses to the KNX devices via ETS4, you can use mobile phone configuration
system to configure the various functions and copy the configuration file which is generated by the
software to the SD card of the mobile phone and then, you can control KNX devices via the mobile control
system.

9.4: Identifying The K-BUS IP Interface

KNX system is compatible with any other devices from different manufacturers. The first step of any KNX
project is to make sure that the ETS product data of all KNX devices that you intend to use in these projects
are imported in ETS Catalog.

K-BUS IP Interface device’s package comes with a file identification.

You will have to go to the ETS Catalogue panel, and choose Import.

The file selection dialog will appear in which you can choose the appropriate KNX product file. KNX
Product files can also be downloaded from the website of the appropriate manufacturer.

9.5: Hardware Set-up

1- First we need to connect two lines in one area. (Line coupling) . Refer to experiment 5,
connect two lines. (5.6 and 5.7)

2- Place your IP Interface in your panel. Connect the power supply input of IP Interface that
is 3 in the circuit diagram to an external power supply.
2
3- Connect KNX bus input of IP Interface that is 7 in the circuit diagram to any line coupler
leads of the two lines.

4- Connect your LAN that is 1 in the circuit diagram to your Router Internet/modem.
Almost this is how your station and your connection should look like:
9.6: Procedures in ETS4:

1- Create a new project.

2- Create an Area and two lines (5.6 and 5.7)
3- Add line coupler, solo switch, actuator devices for both lines
4- Add IP Interface device for the line that you connect your leads to its module. In our
example, we connected KNX bus connection lead to 5.6.

Do not forget to assign the right address for each device.

Figure 9.6.1

5- Create two sub-groups. The first one ( Figure 9.6.1), shows Rocker Switch 5.6.5 is used to control the
Actuator 5.7.2 to energize load 4 in room simulation through output A
 Figure 9.6.2

6- The second subgroup ( Figure 9.6.2), shows Rocker Switch 5.7.5 is used to control the Actuator 5.6.2 to
energize load 1(or 2 or 3..) in room simulation through output B

7- Download your application.

8- Go to config tool in your PC.

Click to File -< New. This command will allow you to create a new configuration file.

Choose the same settings as following.

This command is used to add a new room. When the command is selected, a room window will pop up
and then you can set the room parameters via the window.

Fill in the room name in the room window then press OK.

Add a function. We will use only Light Control.

After the menu “Add a Function ->Light Control ” is selected, a blank light control window will pop up, as
shown in Figure 9.6.3.

Figure 9.6.3: Blank light control window

Add the addresses of both loads(lights) and name them.

Save as your configurations to your desktop. The default name should be “config”

In your Android, create a folder named GVS in the root directory of SD card then copy the new file named
config.xml in your desktop to this folder.

9- Connect your Android Wi-Fi to the internet router.

10- Open GVS.apk

Control your devices