1 of 93

KNX Introduction

Tomas Nordström

Connected Living Training

2020.12

Confidential Property of Schneider Electric

2 of 93

Agenda

Confidential Property of Schneider Electric |

Page 2

KNX in general
Application examples
KNX components
KNX installation
How does KNX work?
KNX configuration and commissioning

3 of 93

1. KNX in general

Confidential Property of Schneider Electric |

Page 3

4 of 93

KNX is a bus system for home and building control

All devices, sensors and actuators, can communicate with �each other via a data cable – the ‘Bus’

KNX devices available for a wide range of applications like

Lighting, Sun protection, Heating/Cooling/Ventilation/Air conditioning �Energy management, Metering, Alarm/Signaling and monitoring, audio/video control, �interface with building management systems and other specialized systems, ….

KNX is a world standard

More than 500 manufacturers and thousands of products

KNX offers flexibility, safety, comfort and cost efficiency

For planners, system integrators, installers, building owners and end users

What is KNX?

Summary

Confidential Property of Schneider Electric |

Page 4

So what is KNX,

It is a system for home and building control.�All devices in a KNX system, like sensors and actuators, can exchange data via a common bus network. KNX brings benefits in every type of building; from office complex to the average household�

There are KNX devices for a wide range of applications on the market, like lighting, sun protection, HVAC, energy management, metering, alarm, signaling and monitoring, audio&video control and a lot gateways and interfaces to other systems, like building management systems via BACnet, to modbus, to DALI and to other specialised systems.

KNX is world standard and more than 500 KNX member companies manufacture products according to the KNX standard. Because the technology is standardised, KNX products are all mutually compatible and KNX installations can be easily modified or extended at a later stage.

KNX offers flexibility, safety, comfort and cost efficiency for all parties using it, so for planners, system integrators, installers, building owners and end users.

That are the main four points that concludes what KNX is.

5 of 93

1990 - Constitution of the EIBA (European Installation Bus Association) based in Brussels:

to define technical guidelines, certification and awarding of the EIB trademark, preparing of European and international standards (DIN VDE 0829 and EN 50090) and coordination of the EIBA-member activities.

1999 – The EIBA merged with two other European organizations:

BatiBUS Club International (BCI)
European Home Systems Association (EHSA)

As a result of this merger, the name was changed to KNX Association

History of KNX

Confidential Property of Schneider Electric |

Page 5

+

1990

1999

2006

It may be interesting to know how this all started.

It was in the late 80ties, there were five companies Merten, Gira, Berker, Jung and Siemens, all German companies.

They come togehter to develop a new system for the electrical installation trade, so for installers and electricians.�It should be a bus system and it should be easy and flexible for electricians to install and configure.

In 1990 they had developed a system called EIB, European Installation Bus.

And then more companies wanted to join, so European Installation Bus Association or EIBA was founded, so that more companies could join and develop products for the system.

EIBA defined technical guidlines, certification program and awarding of the EIB tradermark, coordinated EIBA-member activities and they were also preparing European and International standards.

This standardisation work didn’t go so well.

So in 1999 EIBA merged with two other smaller European systems organisations, BatiBus Club International and European Home Systems Assoiuation.

And the result of this merger lead to KNX and the name of the association was changed to KNX Association.

In 2006 KNX became a standard

KNX is the name of the system, KNX is not an abreviation for something, it was in the beginning, but not anymore.

6 of 93

The association is non-profit-oriented organization with headquarters�in Brussels and governed by Belgian Law and is

The owner of the worldwide standard KNX
The owner of the KNX trademark logo worldwide

Members of the association

Manufacturers developing devices for many applications for home and building control based on KNX
Also service providers (utilities, telecon, …) can become a member of the association

Partnership for others, e.g.

National groups (local associations of KNX stakeholders that promote the use of KNX solutions on the market)
Partners (e.g. system integrators & installers having acquired a KNX certificate)
User clubs (users of KNX: SI, planners, installers, .., to share experience and “push” manufacturers)
Training centers (that offers KNX certification trainings)
Test labs (that carry out the software testing of KNX devices)
Scientific partners (universities and technical institutes active in KNX research)�

KNX Association

Confidential Property of Schneider Electric |

Page 6

The KNX Association is a non-profit-orientated organization with headquarters in Brussels (and governed by Belgian Law) and it is

the owner of the worldwide standard KNX and the owner of the KNX trademark logo worldwide.

Members of the association are manufacturers developing devices for the system.

Members can also be service providers, but it can not be system integrators, installers or other types of companies.

For those there are other types of partnerships

There are national groups, like KNX Sweden, KNX Germany, etc, and these are local organization's of KNX stakeholders, most often companies selling KNX products and that promote the use of KNX solutions and they do things like marketing activities, fairs, conferences, seminars, translate training documentation and create guidelines for their local market.
Then we have partners, which typically are system integrators, installers and electricians that have passed the KNX certification training. So basically, any person who has passed this training will become a partner, which give them the benefit of appearing in a database and for use of the partner logo in their marketing.
Then there are User clubs, which are organization's of planners, system integrater, installers.
Then there are certified training centres offering the certification traning’s
All KNX devices that are obliged to be certified must be tested by a certified test lab. And only those device can be labelled with KNX.�Note that not all KNX devices can be certified, for example visualization software and web severs, and they consequently doesn't have the KNX logo.
And then there are Scientific partners which are universities and technical institute's working with KNX research.

7 of 93

The further technical development and the promotion of the KNX standard together with the KNX member companies
The further development of the common design and commissioning tool software called ETS �(Engineering Tool Software)
Sales and support of ETS via “My KNX” portal (https://my.knx.org/)
Managing certification of products which guarantees system compatibility, interworking and interoperability
Promotion of KNX training measures through the certification of training centers and by making available training documentation and exams
National and international Standardization activities
Encouraging the setup of national KNX groups
Promotion of “Scientific partnerships” with technical institutes or universities in order to promote the KNX system amongst students and for research
Technical support for manufacturers developing KNX compatible solutions
Definition of testing and quality standards together with the KNX member companies
Promotional activities (web site, trade fairs, brochure etc)

�

KNX Association

Activities

Confidential Property of Schneider Electric |

Page 7

Here we have the main activites of the KNX Association and its working groups, whic consists of prople from the member companies.

They develop the system further with new specifications and also keeping up with the rapid changes in the IoT world.

Further development of the common design and commisioning tool software ETS.

They are also selling and supporting the software through their home page, and this is the only way you can purchase it.

They are managing the certification of products.

They are developing the training material and the exams to be used by certified training centres.

These are are the most important activities to know about.

------------------------------------------------------------------------------

Ofcourse national and international standardisation activites.

They encourige the setup of national KNX groups and support them in their activities.

They also promote Scientific partnership with technical institutes and universities in order to promote the KNX system amongs students and for research to implmement new features.

They give technical support to member companies developing KNX devices and also define testing and quality standards.

And ofcourse propotional activities like the web site, trade fairs, broschure and guidelines.

8 of 93

General Assembly

One seat per member
Approval of budget

Executive board

Elected by the members �(approx. 15 seats)
Technical and marketing strategy

Marketing Board and Technical� board

Assisted by working groups and Task forces in which all shareholders can take part��

KNX Association

Structure

Confidential Property of Schneider Electric |

Page 8

9 of 93

Worldwide building automation standard�

KNX deployment around the world (2020.11.01)

KNX is the Standard

EN 50090

The only European Standard for Home & Building Electronic Systems

EN 13321-1

The European Standard for Building Automation based on KNX

14543-3

The World’s only Standard for Home Electronic Systems (HES)

GB/T 20965

Chinese Standard for Home and Building Control based on KNX

US Standard

ANSI/ASHRAE 135 as the US Standard for building HVAC system

45

500

in 44 Countries

93000

in 168 Countries

515

in 72 Countries

10 of 93

KNX System Architecture

Accessory

Power Supply

Coupler/Router

Gateways

System Components

Sensors – WDE related

Sensors - Others

Actuators

Cloud

Gateway

Apps/SW

3^rd Party

Connectivity

KNX interoperable portfolio (> 8000 products)

KNX@SchneiderElectric

So lets look at an overview of the system architecture.

To the left you see Schneider Electric products, grouped according to their main function in the system.

Starting from the buttons we have

system components and actuators, and then sensors that are wiring device dependent, like push-buttons and displays that are matching the design of our other electrical equipment like socket outlets, and then we have sensors that are not design releated, like presence detectors for ceiling mount or weather stations.

On the top we have gateways and other connectivity products to connect to other systems, to cloud, offering visualisations and so on.

While the components of the other groups are always present in every KNX project, members of this group is only present if required.

On the market are more than 8000 certified KNX products available for the customers to choose from.

Below you see some of our main competitors, because they have the same ambition as we have, they have products in all these groups to the left, with the aim to be able to supply most of the products in any project.

Then there are many other companies only focusing on their own speciallity, only doing push-buttons, only doing presence detectors, only doing gateways. etc.

And we are working togehter with some of these specialised companies in different ways to complement our product range.

11 of 93

Actuators and loads

All the different loads, like lighting, sun blinds, socket outlets, �valve actuators, are connected to appropriate actuators

Sensors

Different types of sensors can be used to control the �actuators, for example push-buttons, thermostats, �movement detectors, brightness sensors and time�switches

Bus

The actuators and sensors are connected to a low voltage�twisted pair cable for power supply and communication

Communication

Sensors and actuators communicate with each other by sending telegrams on the bus
Which sensors and actuators that should “talk” to each other is defined by addresses that are configured by configuration software (and not by physical wiring)�

Functional principle of KNX

Confidential Property of Schneider Electric |

Page 11

Bus

230 V

Let’s see the functional principle of KNX.

First, we have actuators and loads

The different loads that should be controlled, for example lighting, blinds, valve actuators for heating/cooling, socket outlets, are connected to different types of actuators. Actuators are connected to the KNX bus and in most cases, also to 230V depending on the loads they are controlling.

Different types of sensors can be used to control the actuators via the KNX bus, for example push-buttons, thermostats, movement detectors, brightness sensors and time switches. Sensors most often only requires connection to the KNX bus.

The so-called bus is a low-voltage twisted pair cable which connects the actuators and sensor’s together. Via the bus the devices get their power supply and can communicated with each other.

Sensors and actuators communicate with each other by sending telegrams on the bus. Which devices that should “talk” to each other is defined by addresses that are configured by configuration software (and not by physical wiring).

All KNX bus devices have their own “intelligence” in the form of a microcontroller, and therefore there is no need for a central control unit. However, to realise very specialised applications sometimes a separate controller might be required.

12 of 93

Separation of information and energy
Only one cable (the bus) for all information

less control cables

Functions depends on programming

logical connections between inputs and outputs �replaces physical connections

Change of functions without touching the installation
Multiple use of single devices
Interactions between different functions�and trades are easy
Distributed intelligence, no central unit

Advantages of a bus system

Compared to conventional methods (contactors, switch relays, PLC)

Confidential Property of Schneider Electric |

Page 12

Bus

230 V

The bus technology brings several advantages compared to conventional installation technology including contactors, relays and PLC’s

Separation of energy and information�The electrical planning and installation is simple and straight forward even by complex functionality.�

Only one cable (the bus) for all information�The amount of cabling is reduced, especially when bus devices are arranged in a decentralized way.�

Functions depends on programming�Logical connections between inputs and outputs replaces physical connections. Therefore, change of functions without touching the installation is often possible.�

Multiple use of single devices�For example, a sensor can include thermostat function and have push-buttons to control lights and blinds; a movement detector can control the light and tell the thermostat to activate comfort mode.

Complex interactions between different functions and trades are easy�As KNX is used for all different trades (e.g. lighting, sun protection temperature) it is easy to create interactions between them.

Distributed intelligence�means that if one device fails, the others continue to function. Only those applications dependent on the failed device will be interrupted.

13 of 93

KNX was developed specifically to meet the needs�of electrical installations in buildings
KNX is well-established and proven and can accommodate �a huge range of functions
There are several thousand KNX-certified products�available on the market from more than 500 manufacturers
KNX products are tested for conformity by independent�third party test laboratories
KNX products are compatible with products from all �manufacturers (interworking)
KNX products are programmed with a common software platform
KNX is standardized in Europe, USA, China and internationally

Advantages of KNX

Facts of KNX

Confidential Property of Schneider Electric |

Page 13

Here we have the main advantages of choosing KNX in front of other systems.

KNX was developed specifically to meet the needs of electrical installations in buildings. KNX is based on 30 years of experience in the market including the predecessor systems EIB, EHS and BatiBus.�

KNX is well-established and proven and can accommodate a huge range of functions.�

There are several thousand KNX-certified products available on the market from more than 500 manufacturers

KNX products are tested for conformity by independent third-party test laboratories

KNX products are compatible with products from all manufacturers (interworking)�

KNX products are programmed with a common software tool

The ETS (Engineering Tool Software) is the PC software tool to design, configure and commission installations of KNX-certified products from any manufacturer.

Other tools, like eConfigure KNX lite, can be used in conjunction with ETS, to facilitate the work.

KNX is standardized in Europe, USA, China and internationally

14 of 93

KNX System Specification

Confidential Property of Schneider Electric |

Page 14

Extended �protocol/ �KNX secure

This slide shows an overview of the KNX system specification.

In the standard or specification are 4 different media.

It is twisted pair, power line, RF and IP.

On top of theses media there can run a standard protocol, which is what is mostly used and what was also used from the beginning.

In parallel there can also run an extended protocol that can carry more data and a secure encrypted protocol called KNX secure.

Then we have the different ways of configuration, most used is system mode, which means PC and the software ETS, but there is also something called easy mode.

It is a configuration method without any PC, so the configuration is done via some kind of controller or mobile app as you can see to the right.

The devices must be developed for easy mode and with easy mode devices simpler applications and projects can be realized.

Schneider Electric doesn’t support easy mode, only a few companies do, like Hager.

On top we have the group objects with standardized Data Point Types. The group objects are inputs and outputs towards the bus that exchange data with other devices via telegrams.

15 of 93

Areas of application for various media

Confidential Property of Schneider Electric |

Page 15

Medium	Transmission via	Preferred areas of application
Twisted pair (TP)	Separate control cable	New installations and extensive renovations – highest level of transmission reliability
Power line (PL110)	Existing network �(neutral conductor must be available)	In places where an additional control cable can not be installed and 230 V cable is available
Radio Frequency (RF)	Radio line	In places where cables cannot be installed or are not wanted
IP	Ethernet/WiFi	In large installations where a fast backbone is needed. For communication with mobile devices

16 of 93

KNX Easy Mode - Easy installation techniques (E-Mode):

Configuration is done without the help of a PC but with a central controller, push-buttons,...
Easy compatible products normally have limited functionality and are intended for small and medium sized installations
Not many manufacturer has products for Easy Mode. Schneider has no offer.

KNX System Mode - System installation techniques (S-Mode):

Design of the installation and configuration is done via a PC with the installed ETS Software, whereby the manufacturers‘ product data are imported in ETS.
This is the standard way of configuring KNX installations regardless of size and functionality

The two techniques cannot be used in the same installation

Types of configuration

Confidential Property of Schneider Electric |

Page 16

17 of 93

Devices from different manufacturers and functional areas that are labeled with the KNX/EIB trademark and using the same configuration mechanism can be linked to form a functioning installation thanks to the KNX standardization of:

Telegrams

Devices usually use standard telegrams for transmission, �but in exceptional cases they also use telegrams with extended�length for the transmission of bulky data

Useful data in telegrams

For various functions (amongst others switching, dimming, �shutter control, HVAC…), predetermined formats need to �be used in KNX certified devices.

Note: the functions and features of KNX devices are not�standardized, manufacturers are free to implement �any functions/features they like (above a certain minimum)

Interworking

Confidential Property of Schneider Electric |

Page 17

, incl. functions/features

Devices from different manufacturers and functional areas that are labelled with the KNX trademark and using the same configuration mechanism can be linked to form a functioning installation thanks to the KNX standardization of telegrams and useful data in the telegrams.

Standardisation of telegrams means that devices can send and receive telegrams to/from each other containing useful information.

Standardisation of the useful data means that devices interprets the data in the telegram in the same way, for example blind down, dim up, temperature value.

It is not allowed for a manufacturer to invent his own data types, but there are hundreds of standardised data types available.

Manufacturer’s can also suggest new data types to the KNX working group handling this and they can decide to include it in the specification.

Even though the way of communication is standardised, the functions and features of the devices are not standardised.�Manufacturer's can implement any functions they like, as long as communication with other devices is done using standardised data types.

18 of 93

Switching and diming lights
Drive sun blinds and other electrical drives
Room control of heating/cooling/ventilation
Switching other electrical consumers
Surveillance and Alarms
Measuring/Metering
Functions of other systems via gateways

Usual building functions

handled by KNX

Confidential Property of Schneider Electric |

Page 18

19 of 93

Control via different types of sensors

Manual control, e.g. push-buttons, touch panels, mobile devices
Movement/Presence dependent
Time dependent
Brightness dependent
Temperature dependent
Others sensors/contacts connected to input devices

Way of control

Locally/Centrally/Remotely
Individually/Group
Scene control

Control and monitoring via

Visualisation systems (touch panels, mobile devices, PC)
Building management systems

Control and monitoring of the building functions

Confidential Property of Schneider Electric |

Page 19

20 of 93

Private houses/apartments
Office buildings
Schools and public buildings
Commercial buildings
Airports and train stations
Hotels
Restaurants
Laboratories/Industries
Hospital and retirement homes
Leisure Facilities / Sport arenas
Churches
Cinemas
Museums and galleries
Animal breeding farms

Any type of building is suitable for KNX

Confidential Property of Schneider Electric |

Page 20

KNX is suitable for any type of building, from the average household or animal breeding farm, via offices and schools up to fully fledged luxiary hotels, hospitals and airports.

It is not the building type or size, but the functionallity in the building that is decisive if conventional installation, KNX or any other type of speciallised system is the best solution.

KNX can provide solutions that can only be realized with considerable effort and costs with conventional installation techniques. KNX also brings cost savings in the planning and installation phase as well as easy implementable functions for energy savings, safety, increased comfort and convenience.

He we see examples of buildings types that KNX often is installed in,

Office buildings

Private houses/appartments

Shools and publiuc buildings

Commercial building like shops and malls

Airport and train stations, for example Heathrow in London and Arlanda in Sweden

Hotels, some also in the guest rooms others in the common areas.

Restaurants

Industries

Hospitals and retirement homes

Leisure Facilities, for example many hockey arenas in Sweden, national fotboll stadium in Sweden, the Olympic area Bird Nest in China and Tottenham stadium in London.

Churches

Cinemas

Museums and galleries

Anamial breeding farms and labroatories to simulate the daily lighting rythm.

21 of 93

Manufacturer independent PC tool to design, configure and commission a KNX installation to the full extent of KNX
ETS is designed and has a table based method of working to

be able to handle projects with a large number of devices
include any certified KNX product from any manufacturer
make use of all available device functions and parameters to create customer specific functions
enable linking of different device functions (group objects) by the use of user created group addresses

Training in form of KNX Basic course with certification (5 days) is recommended to efficiently learn the features of the software
KNX Product trainings are also recommended to be able to fulfill more complex applications

Configuration tool ETS Professional

Engineering Tool Software

Confidential Property of Schneider Electric |

Page 21

The manufacturer-independent Engineering Tool Software, ETS, is used to design, configure and commission KNX-installations to the full extent of KNX.�

Product data (application programs) of KNX-certified products from any manufacturer can be imported and used in the projects.�

ETS Professional is designed and has a method of working (table based) to handle projects with many devices (theoretically more than 50.000, organised according to a specific topology) and make use of all the functions and parameters of the KNX devices to also fulfil complex applications.�

Device functions, so called group objects, are linked together with help of group addresses, which must be freely created and structured�

Training in the form of KNX Basic course with certification is recommended to efficiently learn the features of the software. �

KNX product trainings are also recommended to learn about the extensive range of functions and parameter settings of the individual devices. �

ETS can only be purchased from KNX Association via Internet and the My KNX portal (https://my.knx.org).

Different types of licenses are available, also a free of charge demo version for 5 devices.

We come back to details of ETS later in the presentation.

22 of 93

Configuration tool ETS Professional

Engineering Tool Software

Confidential Property of Schneider Electric |

Page 22

23 of 93

eConfigure is a graphical KNX configuration tool

for residential and smaller commercial installations with a �maximum of 250 KNX devices
only common basic functions are supported
only Schneider Electric KNX products are supported

eConfigure enables simple and fast design, configuration �and commissioning of a KNX project

the visible parameters and device functions of the KNX �devices are limited compared to ETS
linking of device functions are done by “drawing” lines, i.e. �addressing is made automatically in the background
configuration work is done faster than with ETS for the same functions

A special ETS license is included in eConfigure but is running in the background. �The project configuration data can later be used in ETS Professional if required

Configuration tool eConfigure KNX Lite

KNX made easy from Schneider Electric

Confidential Property of Schneider Electric |

Page 23

Then maybe you have heard about the configuration tool eConfigure. This is a purly Schneider invention.

It is a big inventment for an installer or electrician to enter the KNX world, he must buy the ETS software and it is strongly recommended to take the 5 day certification course.

For a first small project this might be a too big inventment, when he perhaps also is not sure that KNX is for him or her.

For this reason, we developed eConfigure KNX Lite which is an easier to handle software.

In contrast to the ETS user interface, eConfigure is a graphical KNX configuration tool, however running on top of the ETS.

It is intended for residential and smaller commercial installations with a maximum of 250 devices.

Only common basic functions and only Schneider Electrric devices are supported.

eConfigure enables simple and fast design, configuration and commissioning of a KNX project with common basic functions

In eConfigure the parameters and functions of the KNX products are limited compared to ETS Professional, hence the user must check that the available functions are sufficient to fulfil the project requirements.

Linking of device functions are done by drawing lines between the devices; the group addressing is done automatically in the background.

A special ETS license is included in eConfigure but running in the background. The project configuration data can later be used in ETS Professional if required.

eConfigure can be downloaded from Schneider Electric home page for free. Without a USB-dongle license it possible to design, configure and generate a bill of material. However, to commission real devices a license has be purchased from a wholesaler or other places where KNX products are sold.�There are no limitations to the number of projects that can be realised with one single license.

We come back also to eConfigure later in the presentation.

24 of 93

Configuration tool eConfigure KNX Lite

KNX made easy from Schneider Electric

Confidential Property of Schneider Electric |

Page 24

25 of 93

Flexibility

Planning, Installation, Adaptation, Use �

Safety and security

Monitoring, Alarm, Fire load, Future-proof�

Comfort

Easiness, Automatic, Scenes, Design �

Cost efficiency

Energy efficiency, Adaptations, Maintenance

Benefits of using KNX

Confidential Property of Schneider Electric |

Page 25

Here is a summary of the benefits of using KNX

Flexibility

Highly flexible and time-efficient planning and electrical installation due to modular system and clear wiring and cable routing

Simple and economic adaptation of the building functions to changing requirements (also during installation)

System can be extended in stages and is use-oriented, making it possible to tailor solutions in modular fashion

Safety and security

Monitoring of windows/doors, temperature, water leakage, technical alarms

Switch on lights and raise shutters/blinds in case of fire

Panic buttons to switch on all lights at night in case of intrusion

Reduced risk of fire by switching off all unnecessary consumers when the building is unoccupied or when going to bed

Less electromagnetic fields

Future-proof standardized technology

Comfort and convenience

Innovative and nice design of control interfaces for easy control

Automatic, scene and central functions

Local and remote control and monitoring via mobile devices

Cost efficiency

Short installation times thanks to clear wiring and cable routing

Cost savings thanks to energy management/monitoring and energy saving function’s, e.g. by using movement, brightness and time dependent control of lighting and temperature

Short rebuilding and construction time by changing requirements and adaptations

26 of 93

2. Application examples

Confidential Property of Schneider Electric |

Page 26

27 of 93

Lighting Areas, Technology and Control type

Different room types have different requirements

Example of room types

Residential
Single office rooms/Open space office
Hotel rooms
Conference rooms, classrooms
Restaurants
Health care rooms
Common areas

Entrances, Lobbies
Pool, Gym,
Waiting areas
Corridors and staircases �with/without windows

Outdoor

Confidential Property of Schneider Electric |

Page 27

Technology

Switching

10 A / 16 A / Higher (contactor)

Dimming

230 V phase cut
1-10V analog dimming
DALI digital dimming
DMX digital dimming
Zigbee (smartbulb)

Colour control

Tuneable white / Human Centric Lighting
RGB(W)

Control types

Manual control via push-buttons

Individual control
Group control
Scene control

Automatic control

Presence
Scheduler
Timer
Brightness threshold
Constant light control
Presence simulation
Sequence, light effects

Let’s start with Lighting.

Lighting is controlled in all KNX projects, this is the main application.

The ways customers want to control the light is strongly related to different types of rooms on one hand, and on comfort and cost efficiency on the other.

The examples of room types you see here often require different type of lighting control.

>

Then we have the technology to control the lighting, so the actuator side.

We can chose to do just switching on/off using switch actuators with relays.

We can do dimming, with 230 V phase cut, 1-10V, DALI, DMX or Zigbee.

So these are the common technologies to dim light.

And now with the LED revolution, colour control also comes into play, with tuneable white, so different tones of white and RGB for effect lighting.

This colour control we mainly realise using DALI.

>

And finally how to control the lighting.

As mentioned before, manual control and/or different types of automatic control, often in combination like presence, brightness and scheduler dependent control�

28 of 93

Drive up/down/stopp and step slats, positioning

Individual control with any number of push-buttons
Automatic control with brightness sensor
Sun position tracking (adjustment of height and slat position depending of sun elevation)
Heating/Cooling support when room is unoccupied
Scene / Group control / Central control
High priority functions

Wind/rain sensor for protection of blinds/awnings
Alarm function, e.g fire alarm
Window cleaning function
Movment range limit, e.g. open window/doors in the movement path

Drive control

Blinds/Shutters/Projector screens/Windows (230 V / 24 V)

Confidential Property of Schneider Electric |

Page 28

Next application to look at is drive control.�This concerns sun protection, in form of blinds, shutters and awnings, but also other motorized applications like projector screens, windows, partition walls, dampers, etc.

Such drives are controlled in two directions using blind actuators with relays.

Control can be done manually with push-buttons.

We can do it automatically with brightness sensor.�We can do it with sun position tracking, so that depending on the sun elevation (or sun position on the sky), the slats of blinds or the height of the sun protection is automatically adjusted.

We can support heating/cooling when the room is unoccupied, to either make use of the sun or block the sun completly when the room is empty.

Of course, drives can be integrated in scenes.

And we have higher priority functions to protect the sun protection in case of strong wind or rain, incase of fire alarm you want to position them so that they don’t cover the windows so you can get out, window cleaning function, etc.

29 of 93

Room temperature controller (RTC)

Manual setpoint adjustment
Display of setpoint and/or actual temperature
4 operation modes (pre-definied setpoints) �(comfort, eco/standby, night and protection) �changeable locally and via the bus
Scene

Heating and cooling valve control

Thermoelectric valve drives via heating actuator,�e.g. for floor heating
KNX powered valve drive
Fan coil actuator
VAV-controller

Room temperature control

Heating and cooling

Confidential Property of Schneider Electric |

Page 29

W�i�n�d�o�w

R�a�d�i�a�t�o�r

Cooler

Window contact

Bus

M

Room example

30 of 93

Recall of stored scenes with individual settings for each load (example).

Switching
Dimming
Drive
Heating operation mode/temperature

Possible to easily adjust values of the loads in a scene for the end users

Scenes

Confidential Property of Schneider Electric |

Page 30

Scenes is a very comfortable and powerful functionally that is in the core in KNX.

Scenes means that by the press of a single button, you recall predefined stated for the different loads and functions.

For example, in a conference room in case of a presentation, the projector screen runs down, the whiteboard lights switch off and other lights are dimmed.

You can imagine scenes in all kinds of areas where you want to change the moode by adjusting several loads at the same time.

in residential it could be good morning, welcome home, watching TV or cleaning.

In restaurants: breakfast, lunch or dinner service, or entertainment

It is also possible for an end-user to easily change the values in a scene. By a short press of the button the scene is recalled and by a long press the scene is stored.

So the end-user can do this by himself, if it is prepared.

Scenes can ofcourse also be recalled in other ways, like by scheduler.

31 of 93

Meetings room, offices, sport facilities, schools might have flexible partition walls to adjust the space depending on activity
The electrical functions can automatically be adjusted to the wall configuration, either automatically via contacts connected to binary inputs, or manually via prepared�visualisation software

Dynamic control of functions

Flexible partition walls

Confidential Property of Schneider Electric |

Page 31

The applications mentioned so far are commonly used, even if many variations and special requirements exist.

But there exist often also quite specific requirements in each project and KNX can of course handle also this, even though a controller may be required.

An example of a special requirement that is actually not that unusual, is dynamic control of functions depending on flexible partition walls.

This variable space concept you can find in meeting rooms, offices, sport arenas and schools, to adjust the space depending on activity.

Let’s take a conference room as an example. A rather big room can be devided into two smaller conference rooms by a moveable partition wall.

The electrical functions, like lighting, blinds, projector screens and perhaps temperature should then follow the current one or two room configuration caused by the position of the wall. The logic is programmed in a controller who get the state of the wall and then knows if for example the ceiling light should be controlled for the big room or for one of the small rooms, when the button is pressed.

Even more partion walls can be part of such a solution, I have seen up to 4 walls.

32 of 93

Visualisation (local and remote)

Control and monitoring of functions via PC, mobile devices and touch panels

Messaging

E-mail, SMS, push-notification in case of alarms or distrubances

Voice control

E.g. Amazon (Alexa), Google Home, (Siri shortcuts)

Logic

Programming of special functions

Communication with external systems

Philips Hue (Lighting), Sonos (Audio), Revox (Audio)
Via Modbus (meters, SmartLink, PLC, displays)
Via BACnet (BMS systems)

Additional control and monitoring functions

Examples of controller functions

Confidential Property of Schneider Electric |

Page 32

33 of 93

3. KNX components

Confidential Property of Schneider Electric |

Page 33

34 of 93

System components

Components to build the communicating network, �e.g. power supply, line couplers

Sensors

Detects an external event
Transform it to KNX-information
Sends the information as telegram on the bus

Actuators

Receives telegram from the bus
Processes the information
Execute the function

Controllers

Processes information between sensors and actuators

Which components does a KNX system consist of?

Main groups

Confidential Property of Schneider Electric |

Page 34

35 of 93

Which component types does a KNX system consist of?

Examples of devices

Confidential Property of Schneider Electric |

Page 35

Sensors

Actuators

Controllers & Gateways

System Components

Here we have the main groups of components or device types.

System components are components needed to build the communicating network, for example power supply, and interfaces (e.g. USB) for configuration software. These components don’t bring any user functionality, but are required for the rest to work.

�Sensors are the inputs to the system.

They detect an external event, for example a push of a button, change of temperature or a movement, transform it into KNX-information and sends the information as a telegram on the bus.�

Actuators receives telegrams from the bus, process the information and execute the function, for example switch on the light or close the heating valve.��Devices which acts as both sensors and actuators can be called controller’s and perform different types of tasks. �A logic controller receive information from the bus, performs operations/calculations and send the result back to the bus. �Other tasks a controller might have are visualisation for control and monitoring of functions, logging data, time scheduling, gateway to other system’s, etc.

36 of 93

Power supplies
Line/Backbone coupler
KNX/IP router
KNX/IP interface
USB interface

KNX Components

Examples of System Components

Confidential Property of Schneider Electric |

Page 36

37 of 93

Push-buttons
Movement/Presence detectors
Room temperature controllers
Binary inputs
Sensors for wind, rain temperature and brightness
Time switches
Analogue inputs
CO2 sensors

KNX Components

Examples of Sensors

Confidential Property of Schneider Electric |

Page 37

38 of 93

Switch actuators
Blind actuators
Dimming actuators
DALI gateways
Valve drives
Fan coil actuators
Analog outputs
VAV controllers

KNX Components

Examples of Actuators

Confidential Property of Schneider Electric |

Page 38

39 of 93

Function: These products act both as ”sensors” and actuators”

Logic module
App interface
Visualsiation server
Modbus gateway
BACnet gateway
IoT gateway
Touch panels

KNX Components

Gateways, Visualsiation and Logic controllers

Confidential Property of Schneider Electric |

Page 39

Wiser for KNX

spaceLYnk

40 of 93

KNX Components

Schneider SpaceLogic KNX Product catalog (LSB02779)

Confidential Property of Schneider Electric |

Page 40

41 of 93

4. KNX installation

Confidential Property of Schneider Electric |

Page 41

42 of 93

Bus topology within one bus line segment

Example

Confidential Property of Schneider Electric |

Page 42

10/16 A

L1

L2

L3

10/16 A

N

PE

Power supply

Switch actuator

Dimming actuator

Shutter actuator

Binary input

Valve drive

Bus cable

M

Multi-functional touch display

Push-button

Bus line segment consists of

KNX power supply�(max in total 1280 mA)
max. 256 bus devices
max. 1000 m bus cable
max. 350 m between �power supply and device
max. 700 m between two bus devices
free topology (mix of line,�tree and star, but no loop)

First we talk about a bus line segment.�A bus line segment is twisted pair cable segements that is galvanically, or electrically, connected to each other.

The total bus cable length in a bus line segment may be up to 1000m.

The bus power supply to power the devices, may deliver a maximum nominal current of 1280 mA at 30 V DC.

The maxium number of KNX devices you can connect to a bus line segment is 256. This is quite new, before it was 64, but since some 6-7 years another tranceiver, meaning the electronic part closes to the bus, is used and it allows 256 bus devices.

But this is today anyway a theoretical number, because a KNX device consumes in average 10-13 mA. And as the max current is 1280, the practical maximum number is somewhere between 100 and 128 devices. The consumption of each single device should anyway be taken into account when designing the project, or a safe margin should be observed.

You must also observe the cable distance between any KNX device and the power supply, it is max 350 meters.�And the maximum between any two devices is 700 m.

43 of 93

The topologies line, star and tree can be combined
Rings have to be avoided
KNX does not require terminating resistors

Bus cable installation (twisted pair, TP)

Free topology

Confidential Property of Schneider Electric |

Page 43

44 of 93

The KNX bus is SELV

SELV - Safety Extra Low Voltage

Confidential Property of Schneider Electric |

Page 44

SELV network�for KNX DC 30 V

Mains network

230/400 V

Basic insulation

Double insulation

Other networks

e.g. tele, data

PE

no insulation

45 of 93

Safety transformer
Voltage range less than/identical to 120 V / AC 50 V DC
Safe insulation, e.g. to 230 / 400 V AC
SELV may not be earthed

Safety Extra Low Voltage

Confidential Property of Schneider Electric |

Source: KNX standard, part 4/1 ”Hardware requirements for KNX products”

Relevant voltage	Mains type	Creepage/�Clearance	Test voltage
230/400 V AC	TN/TT	5,5/5,5 mm	AC 4,0 kV
400 V AC	IT	8,0/8,0 mm	AC 6,0 kV
24 V AC	-	2,0/1,5 mm	AC 1,8 kV
Ground	-	1,3/1,0 mm	AC 1,0 kV

46 of 93

E.g. HCHM 2x2x0,8 or J-H(St)H 2x2x0,8 EIB (also other designations)

Halogen free, different installations conditions exist (e.g. in-/outdoor, dry, wet)

Typically exist in green (standard), grey or white color
A certified cable is marked with KNX- or EIB-logo
There also exist cables which are ”recognised” by KNX Association but not �certified (no KNX/EIB-logo). List of certified/recognised cables: www.knx.org -> Downloads

Bus cable

Certified or recognised

Confidential Property of Schneider Electric |

Page 46

Jacket/Sheath

(PVC or halogen free)

Drain wire

Bus Red +

Bus Black –

Yellow +

White –

Polyester tape

Labelling

text or logo

Aluminium shield

Spare pair

Not any cable can be used as bus cable.

Because the absence of interference during the transmission of data between the individual bus devices depends on what cable is used, the KNX standard includes precise stipulations about what bus cables are acceptable.

The standard certified KNX TP cable has:

a green jacket which is labelled KNX/EIB
has a foil screen and a drain wire. This shielding must not be contacted through or connected to earth on any side. It functions purely as a metal cage.
two twisted pairs of solid conductors with a diameter of 0.8 mm. The red/black pair is used for KNX (power supply and communication) and the yellow/white pair is a spare pair.

Rules for this free spare pair is:

- only extra-low voltages (SELV/PELV) are permitted

max 2.5 A continuous current, overload protection is required
It cannot be used as a circuit for public telecommunications network

The most common use of this pair is to provide separate power supply for particularly power-intensive KNX-devices.�So devices that are requiring more current than is allowed to take from the bus itself.

We strongly recommend to use KNX certified cables for all parts of the bus line, meaning also inside cabinets. There are many cable manufacturers that offers KNX TP cables on the market and it is not an especially expensive cable. Besides the standard green cable for indoor use, there also exist approved or recognised cables with additional characteristics, for example for outdoor use, duct grade, armored, white or grey jacket and with only one twisted pair (meaning without the yelllow/white pair). With only the bus pair the cable is obviously thinner, and this is really good if you install it in pipes in an existing installation together with other wires, like 230V wires.

47 of 93

Red/Black

Supplied with almost all bus devices
Mechanical protection against reverse polarity
Disconnection of device without breaking the bus line
4 plug-in terminals per wire
Should also be used for branch off in junction boxes

Yellow/White

Branch terminal for the spare pair
4 plug-in terminals per wire

Bus connection terminal / Spare pair branch terminal

Confidential Property of Schneider Electric |

Page 47

Holes for connection �pins on the devices

To connect the bus cable to the bus devices there is a standardized red and black bus connection terminal, which is supplied with each device.�It has 4 plug-in terminals for each wire, and they are matched to the 0.8 mm solid wires of the bus cable.

Anyway, it happens sometimes cabinet builders or other players using incorrect cables like stranded wires or too thinn wires and this is not good as it gives bad contact and may lead to communication problems.

A big advantage is that the connection terminal can be removed from the device and then disconnect it from the bus, without breaking the bus line. For example, if the device should be replaced och being reset.

Anyway, if you want to remove a wire from the connection terminal, you need to apply a twist and pull operation, there is no ”release button”.

The bus connection terminal shall also be used for branch off in junction boxes, so when the cable is split up.

It should also be used when entering a cabinet. Screw terminals is a point of failure as the solid wires may get damaged, which then may lead to disturbed communication. The bus connection terminal is available as a separate referense for this reason.

If the yellow and white spare pair is used and connected through in junction boxes, there is a yellow/white version of the connection terminal.

48 of 93

Bus cable installation

Confidential Property of Schneider Electric |

Page 48

The metal foil shield is removed. The shield/drain wires are not earthed and are not integrated in the equipotential bonding. �The shields are not interconnected in the cable run either.

Example of labelling: KNX line 1.1

The yellow/white wires (unless they are used) are bent back and isolated (not cut)

Example of connection of a push-button interface

Source: KNX Handbook, section 6.6

49 of 93

Insulated wire cores of 230 V AC may be installed next to the sheath of the bus cable without any clearance
However, a minimum clearance space of 4 mm must be observed between the insulated wire cores of the bus and insulated wire cores of 230 V AC

When branching the bus cable in junction boxes, the clearance and creepage distances between the bus cable cores and other cables must be ensured (e.g. 5,5 mm), e.g. by branching in separate boxes or in a box with compartments (partition wall)

Bus cable installation

SELV - Safety Extra Low Voltage

Confidential Property of Schneider Electric |

Page 49

KNX

The requirements for the installation of bus cables are generally the same as for the installation of 230/400 V AC networks. Bus cables should ideally be laid together with the mains and hence in the standard installation zones.

�Insulated wire cores of sheathed mains cables and KNX TP bus cables may be installed next to each other without any clearance space. As can be seen in picture 1.

A minimum clearance space of 4 mm must be observed between the insulated wire cores of KNX TP bus cables and those of sheathed 230 V AC mains cables. So as soon as the jacket of the bus cable is opened these 4 mm must be observed.��Alternatively, the wire cores must be provided with an equivalent insulation, such as a spacer or insulation sleeving. This also applies to wire cores of other cables that are not part of SELV/PELV circuit, they must be separated.

As SELV circuits require double or reinforced insulation between mains and bus voltages, branching of the bus cable cannot be done in the same junction box as other cables without measures. Junctions can be done in separate boxes or in a common box with a partition [ensuring the clearance and creepage distances, for example 5,5 mm towards 230 / 400 V AC TN/TT networks].

50 of 93

Requirements

Use of standard distribution board �(EN 50022 35x7,5 mm DIN rails)
Install bus cables with sheath up to the device terminal
Use bus cable also within the distribution board and respect the SELV requirements
Do not install bus devices above mains devices with�significant power losses (heat rises upwards)

Bus devices in distribution boards/cabinets

Confidential Property of Schneider Electric |

Page 50

Any commercial, standardised electric power distribution board equipped with standard [EN 50022 35x7.5 mm] DIN rails may be used to install KNX DIN rail mounted devices

If the mains section is separated from the bus installation, no special installation requirements need to be observed.

If the mains section is not separated from the bus installation, the bus cables must be sheathed up to the terminals,

Incoming bus cable(s) should be connected directly to the bus connection terminal of a device, so not be branched in the cabinets (screw) terminals as 230 V cables normally are.

Possible contact between mains cores and bus cable cores must be prevented by adequate wiring and/or mounting, again follow SELV rules.

Bus devices should not be mounted above mains devices with significant power losses, as this could cause excessive heat development in the installation.

51 of 93

In case

More the 1280 mA is needed
Cable distance limitations are reached

Maximum 4 line segments

3 line repeaters in parallel
Each one with one power supply

Good practice

Line segments follow the building structure if possible

More bus line segments (twisted pair)

In systems with a maximum of 250 devices / Use of eConfigure KNX Lite

Confidential Property of Schneider Electric |

Page 51

DVC

1

PS

LR

64

DVC

61

PS

LR

128

LR

192

DVC

x

DVC

65

DVC

127

DVC

x

PS

DVC

129

DVC

191

DVC

x

PS

DVC

193

DVC

255

DVC

x

PS = Power supply

DVC = Device

LR = Coupler as � Line repeater

Line segement 2

Line segement 3

Line segement 4

Line segement 1

52 of 93

KNX Topology

Twisted pair only

Confidential Property of Schneider Electric |

7,5

Area 15

Page 52

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

BC

1.15.0

Area 2

BC

1.15.0

PS = Power supply

DVC = Device

LC = TP Coupler as � Line Coupler

BC = TP Coupler as Backbone Coupler�

Individual address:�<area>.<line>.<device>

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

Area 1

PS

Main line

Max 256 DVC

PS

DVC

1.1.1

DVC

1.1.255

DVC

1.1.x

PS

BC

1.0.0

LC

1.1.0

LC

1.2.0

PS

DVC

1.2.1

DVC

1.2.255

DVC

1.2.x

Backbone line

KNX TP, �max 1000 m total �max 350 from PS

DVC

1.0.1

Line 1

Line 2

PS

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

LC

1.15.0

Line 15

Now let us take a look on the topology when we have more than one bus line segment.

>

So here we have what we talked about before, one bus line segment with a power supply, up to 256 devices and 1000m bus cable.

>

If you need more devices you can add a second line with its own power supply, 256 devices and 1000m bus cable.

>

You of course need to link these two lines together and you do that with line couplers.

>

And the line couplers are connected togehter by another bus line segment called the main line.

A line coupler have two purposes, It galvanically separates the main line from the subline. The information is transfered using opto coplers and that is the reason you always need power supplies on both sides of the line coupler. The second purpose is that it is acting as a router, so it is filtering telegfram trafic to and from the line to avoid bus trafic overload.�This main line is like any of the other two lines. It has its power supply and up to 256 device and 1000m bus cable can be connected.

Infact, if a project can do with two lines only, then line 1 and the main line is used. Line 2 is then not needed and one power supply and one line coupler can be saved. However, in bigger systems, the main line is most often used as the link between sublines and contain only few devices.

>

Up to 15 lines can be connected to a main line.�The main line and the 15 sublines are called an Area.

>

Next step in size is to add a second area.�The areas are connected with backbbone couplers to a backbone line with its own power supply.

The line couplers LC and backbone couplers BC are the exact same physical device, which we in the catalog simply call Coupler. �We use different name here because they have different position in the topology drawing.

>

Then it is possible to add up to 15 areas to the backbone line. And this is the maximum theoretical size of a KNX installation.

What we also can see here is one of the two types of addressing that is used in KNX.�It is called individual address and it is a unique address that each device must have. You can say it is the id or name of the device.

It is divided in three parts or numbers separated with a dot. The first number comes from the area which the deivce is installed in. The second number is the line of that area and the third number is the device number of that line.

So therefore you see on area one and line one, the line coupler has address 1.1.0, because 0 is reserved for the coupler and then the rest of the devices has address 1.1.1 up to 1.1.255

The backbone coupler of area 1 start with 1 and then 0 because it is connected to the main line which has line number 0 and then again 0 becuase it is a coupler, so 1.0.0.

As I said, this size of a twisted-pair-only project is pure theoretical. There is no KNX installation that uses this structure fully, meaning 15 areas each with 16 lines with twisted pair only.

The reason is that in such big systems there is always a Building Management System on top, which means all data should go to this BMS system and the backbone line would be overloaded; the amount of data to transfer today is much higher than it was in the 90’s when this was invented.��

53 of 93

KNX Topology

Twisted pair + KNX/IP backbone

7,5

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

BC

1.15.0

Area 15

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

BC

1.15.0

Area 2

Area 1

Backbone line

BC

1.0.0

IP Network (switch/router)

KNX TP, �max 1000 m total �max 350 from PS

IP cable,

max 100 m

PS = Power supply

DVC = Device

LC = TP Coupler as � Line Coupler

BC = KNX/IP router as Backbone Coupler�

Individual address:�<area>.<line>.<device>

PS

DVC

1.15.1

DVC

1.15.255

DVC

1.15.x

LC

1.15.0

PS

Main line

PS

DVC

1.1.1

DVC

1.1.255

DVC

1.1.x

LC

1.1.0

LC

1.2.0

PS

DVC

1.2.1

DVC

1.2.255

DVC

1.2.x

DVC

1.0.1

Line 1

Line 2

Line 15

54 of 93

KNX Topology

Twisted pair + KNX/IP backbone

Confidential Property of Schneider Electric |

Page 54

PS

DVC

x.y.1

DVC

x.y.255

DVC

x.y.z

LC

x.y.0

LC

1.1.0

PS

DVC

1.1.1

DVC

1.1.255

DVC

1.1.x

IP Network (switch/router)

LC

1.2.0

PS

DVC

1.2.1

DVC

1.2.255

DVC

1.2.x

Up to15x15 = 225 lines

Backbone line

PS = Power supply

DVC = Device

LC = KNX/IP router as Line Coupler�

Individual address:�<area>.<line>.<device>

KNX TP, �max 1000 m total �max 350 from PS

IP cable,

max 100 m

Line 1.1

Line 1.2

Line x.y

55 of 93

Example of topology

In a medium-sized project

Confidential Property of Schneider Electric |

Page 55

56 of 93

Example of topology (TP)

In a medium-sized project

Confidential Property of Schneider Electric |

Page 56

57 of 93

Example of topology (TP + IP)

In a medium-sized project

Confidential Property of Schneider Electric |

Page 57

58 of 93

All actuators are placed centralized in the distribution board with cables going to each consumer
Sensors are placed decentralized and bus cable is going from one sensor to another

Example of cable run in a residential building

Confidential Property of Schneider Electric |

Page 58

59 of 93

Each KNX-device receives a unique address �in the system via the configuration tool; �the assignment is part of the first commissioning
The individual address provides the device �with a name, in the from of numbers
It is divided into Area, Line and Device number�Example:

Area Line Device

1.1.15

The KNX device must be labelled with the individual �address when it has been programmed
The individual address is used for programming and service
The address of an unprogrammed device is 15.15.255

Individual address

Confidential Property of Schneider Electric |

Page 59

Programming button for programming �the individual address from the �configuration tool

As mentioned, each device must have a unique individual address in the system.

The address consists of area number, line number and device number.

Out of the box, all devices have the same individual address, which is 15.15.255.

The assignment of the actual address is part of the commissioning of the device from the ETS or eConfigure configurations tools.

Each device has got a programming button and a red programming LED indicating programming mode is on.

From the configuration tool you initiate a ”program individual address” command and then you must press the button of the correct device.�When the LED goes out the address is programmed.

The device should then be labelled with the given individual address. There are dedicated labels or space for that on the devices.

The assingment of this address can be done after installation but it can also be done before in a workshop. And this is how it is done in bigger projects.�All that is needed then is an USB interface to connect the PC, a power supply and the device to be programmed.

It is then of course important to install the device in the building where it belongs.

So the device must be labelled with the individual address and the installer or cabinet builder must be informed where it should be installed and which device it is according to the drawings. So a logistic operation. �[Imagine if two switch actuators are mixed up, then controlling the wrong loads. Or if two sensors are mixed up, controlling loads in another part of the building. ]

Programming of the individual address is a one-time operation. The devices must also be programmed with configuration, but this doesn’t require pressing the programming button so this is always done after installation.�

60 of 93

A KNX power supply is required on each bus line segment

Supplies the KNX devices with power at DC 30 V�(the minimum voltage for a KNX device to work is DC 21 V)
The power supplies includes the choke that is required for the communication between devices to work
Some power supplies have an un-choked output that can feed �devices that requires external supply
Most power supplies has no address and is not programmable

KNX power supplies with different current delivery

320 mA, 640 mA or 1280 mA (nominal, at DC 30 V)
Typical current consumption of a KNX device is 10 mA (note that some �takes more, check the product documentation or config software)
Max. two power supplies per line and total max. 1280 mA

Connections

Phase (L), neutral (N) and Protective earth (PE): prevents static charging
Bus via bus connection terminal under isolation cover

Bus power supply

In general

Confidential Property of Schneider Electric |

Page 60

Power supply with backup battery

Power supply with additional �DC 30 V output

As you know now each bus line requires its own power supply.

The nominal voltage is 30 V DC.

It must be KNX power supplies. A normal transformer will not work as the power supply include a choke which has a passive part in the analog signaling on the bus.

Some power supplies has an unchoked 30 V output, which can be used to feed devices that requires external power supply.

The new SpaceLogic power supplies has got this additional output.

Another difference between power supplies is the maximum current delivery.�There are 320, 640 and 1280 mA power supplies, of course with different prices.�The one to chose of course depends on the current consumption of the connected bus devices. In really small installations or main and backbone lines with almost no devices, 320 mA may be enough.�As mentioned, the average current consumption of a bus device is around 10 to 13 mA, in worst case up to 30 mA, so check the product documentation.

A maximum of two power supplies of the same type can be connected to one line, but this only concerns the 320 and 640 mA versions, as 1280 mA is the total maximum. The reason for two power supplies could be that the line is extended with more devices or that redundancy is wanted.

61 of 93

Indicators

Green Operation RUN LED
Red Over-current LED (I > Imax)

��

Reset button with LED

Button to restart all devices on the bus line
When the button is pressed (Reset LED switched on) the bus power is switched off for approx. 20 s and then automatically switched on again

Bus power supply

Indicators and operating elements

Confidential Property of Schneider Electric |

Page 61

RUN LED	I > Imax LED	Meaning
ON	OFF	Power supply ready for operation
ON	ON	Power supply ready for operation, �output current too high
OFF	ON	Short circuit on the bus line
OFF	OFF	No mains voltage

62 of 93

The coupler is used to connect bus line segments together

The coupler guarantees galvanic separation of the two line segments, hence each line segment requires its own power supply
The device takes its operating power from the line segment connected to the “main line” connection (superordinate line)

Connections

One bus connection terminal for each line segment under isolation cover

Upper LED Main and lower LED Sub – indicating

Green - KNX power and telegram traffic (flicker)
Red (shortly) - Communication error on the KNX bus (telegram repetition, NACK, BUSY)

Two push-buttons and the middle Mode LED

Pass GA button: Forward all group telegrams, i.e. bypass filter or block function
Pass IA button: Forward all individual addressed telegrams, i.e bypass filter or block function
LED: Indicate the different manual modes by a blinking pattern �

Coupler

Line repeater / Line Coupler / Backbone Coupler

Confidential Property of Schneider Electric |

Page 62

63 of 93

Coupler function:

forwarding of telegrams between different lines through a LAN (IP) as a fast backbone (KNXnet/IP routing)

LAN-programming interface:

PC-access (e.g. with ETS5) to the KNX bus via LAN (KNXnet/IP tunnelling/routing)

IP-addressing

Automatic assignment via a DHCP-server
Manual configuration (ETS-parameters)

Power supply

Powered solely by KNX TP�

KNX/IP router

Coupler and Interface

Confidential Property of Schneider Electric |

Page 63

64 of 93

KNX Planning

Confidential Property of Schneider Electric |

Page 64

65 of 93

To plan any KNX installation it is necessary to

for each room decide what is going to be controlled (e.g. a light),�in which way (e.g. switching or dimming) and power (e.g. 10 A or �250 W)
Decide in which cabinet the actuator channel can be placed �(flush-mounted installation in the room is also possible)
For each room decide which functions to control in this room and in other rooms and how (e.g. push-button, movement detector)
From this you get the type and quantity of devices required

Planning a KNX installation

Which KNX devices are required

Confidential Property of Schneider Electric |

Page 65

66 of 93

Actuators

All acutaotrs are placed centralized in the�distribution board and cables run from there to the loads
More distribution boards reduces the cable lengths, e.g. one per floor

Sensors

Sensors are placed decentralized in the rooms and the bus cable is going from one sensor to the other in the best suitable way

Planning a KNX installation

Example of cable run i a private home

Confidential Property of Schneider Electric |

Page 66

67 of 93

5. How does KNX work?

Confidential Property of Schneider Electric |

Page 67

68 of 93

KNX is a decentralized and event-controlled bus system, i.e. no central unit, and the bus is idle (free) if nothing happens or changes
All connected bus devices can exchange data between each other, packed into telegrams and sent over the bus (serial transmission of “1” and “0”), e.g. from a sensor (the command output) to one or more actuators (the command receiver)
Which devices that should speak with each other is defined by group addresses in ETS
CSMA/CA (Carrier Sense Multiple Access / Collision Avoidance) is used for bus access and collision handling
Transmission rate: 9600 bit/s
Average transmission time for sending and confirmation of a telegram is approx. 25 ms

Bus access and data exchange

Confidential Property of Schneider Electric |

Page 68

Bus access and data exchange

KNX is a decentralised system, so no central unit, each bus device has its own microcontroller and intelligence and knows what to do, doesn’t have to ask anybody else. The system is also event-driven, which means the bus is free if nothing happens or changes.

All connected bus devices can exchange data between each other, packed in telegrams and sent over the bus, so serial transmission of 1 and 0.

Which devices that should speak with each other is defined by group addresses in ETS or eConfigure�

The bus access method used in KNX is called CSMA/CA, which stands for Carrier Sense Multiple Access / Collision Avoidance.

The first part means that any bus device can start sending a telegram as soon as it detects the bus is free, they always listen to the bus.�Collision Avoidance means that if two or more devices start sending at the same time, all except one will detect this and stop their sending.�The one who didn’t detect the others, will finish sending. After that the others try to send their message again.�This is a very bandwidth efficient way of communicating.

The transmission rate is 9600 bits/s, which is quite low with todays standards, but it is also good as the communication is very robust and not easily disturbed.�A telegram takes between 20 ms and 40 ms to transfer within a bus line, depending how much useful data that is transfered. The maximum useful data that can be sent is 14, 1 4, bytes, in the standard protocol.�The average telegram takes 25 ms, which means that 40 telegrams can be sent per second.

69 of 93

Principal comparisson conventional vs bus

A

B

C

D

A

B

D

C

Sensor, e.g push-button

Actuator, e.g. relay

Conventional

A

B

C

D

A

B

D

C

KNX

Terminals -> Group Object

Cable -> Group Addresses

So how does it then really work?

Here is a principal comparission between conventional and bus.

So conventionally a push-button with 4 buttons controlling 4 relays or contactors.�Each button has an output connection terminal, and each relay has an input connection terminal and these are linked togehter with a cable.

So how does it then work in KNX.

Here is a cable between the device, but it is the bus cable. The bus cable only makes it possible for the devices to communicate, but it doesn’t give the function that button A should control relay A, like in the conventional example.

Instead of physical input and output terminals, the devices has logical inputs and outputs in their application softwares.

And these are called group objects. And instead of cables, the group objects are linked together with group addresses, which infact are the names of the telegrams being sent on the bus.

70 of 93

All communications between devices in runtime is done via group objects and group addresses

Group objects are the inputs and/or outputs of the device towards the bus
Group addresses are the addresses linking group objects together��
Object characteristics

A group object represents a memory location with a value in the bus device.
The value can be changed from the bus and/or from the device itself.
A group object can be of a size between 1 bit and 14 bytes (defined by the manuf.) depending on the related function
Only group objects of the same size can be linked together
A group object can listen to many group addresses (last received decides the value)
A group object with send capability can only send ONE group address (the so called sending address)

Group objects

Logical inputs and outputs

Confidential Property of Schneider Electric |

Page 70

Push-button with 4 buttons

Switch actuator with 4 relay channels

We can see that there. This comes from ETS which I will show soon.

The push-button with 4 buttons has one group object per button. Infact a button can have more than one group object depending on which functionallity it is configured for. Now each button can toggle on and off, and then only one group object is required.�On the switch actuator with 4 relay contacts, you also see a group object per channel.

You can then see that push-button 1 is linked to channel 1 of the actuator using group address 1/1/1.

>

There are some charateristics you can say about these group objects.

The group object represents a memory location with a value. So a group object always has a value.

And this value can be changed from the bus or the device itself. We come back to this soon.

A group object can be of a size between 1 bit and 14 bytes and this is definied by the manufacturer depending on the related function.

In the example you see the group objects are of size 1 bit so it can have two values 0 or 1, which is all that is needed to switch on/off.�To do dimming for example we need other data formats.

Only group objects of the same size can be linked together with the same group address, and the ETS or eConfigure makes sure this rule is kept.

A group object can listen to many group addresses and the last received telegram decides the value of the object.

For example, if all the 4 channels of the switch actuator should be controlled by another push-button that switch them all off, a second group address is required.

And the final charateristic is that a group object with send capability, like a push-button, can only send one group address.

So if I would connect more group addresses to the push-button 1, only the first one would be sent.�This restriction is due to the bandwidth. If you were able to connect many group addresses and when you press the button all these would be sent one after each other, you would very soon overload the system. This is anyway not a limitation; you must just think the otherway around, that a group object can listen to many group addresses.

�

71 of 93

Communication between devices is carried out via group addresses
A group address represents a function in the installation, e.g. ”Switch on/off lamp 1” or �”Switch off all”
Group addresses are generated in order to determine the logical connections between group objects (channels or functions) of different devices
The address range is 16 bits = 65536 addresses. For easier handling and structuring they are divided into 2 or 3 levels (free group address style is also possible)
Example 3-level group address:�Main group / Middle group / Sub group�Level / Function type / Function�1st floor / Lighting / Room 101 Lamp group 1 On/Off

Group addresses

Group address 3-level style (main-/middle-/sub group)

15

14

13

12

11

10

9

8

7

6

5

4

3

2

1

0

0-255

0-7

0-31

16 bits (65 536 addresses)

So a group address, what is it?

It is s 2 byte or 16 bit long address as can be seen as the name of a telegram on the bus.

A 2 byte number can have a value between 0 and 65536. So that is the maximum number of addresses or infact functions that a system can contain, as each function has a group address.

In ETS you can name the group addresses with text so that you know which function it is representing.

Instead of having a long one level list from 0 to 65536, the 16 bits are divided into 3 groups.

In this way you can structure your functions in 3 levels

The first 5 bits are called main group. It can have a value between 0 and 31

The next group is called middle group and has 3 bits, a value between 0 and 7.

And the last group which is the real function is called subgroup and has 8 bits, which means a value between 0 and 255.

So now it is possible to structure the addresses and it is free for the planner, or the one doing the project in ETS how to structure it.

You can and should name each main group, each middle group and each subgroup.

You can see the main group and middle groups as structure elements, like folders in Windows, and the subgroups are the real functions.

72 of 93

Main group / Middle group / Sub group�Level / Function type / Function�1st floor / Lighting / R101 Light group 1 Switch

Group addresses

Examples 3-level style

Main group / Middle group / Sub group�Function type / Location / Function�Lighting / Kitchen / Kitchen Ceiling light On/Off

Here I have two examples:

To the left, the main groups are representing floors in the building.�First we have central functions for the whole building, next main group is 1st floor, the next is probably 2nd floor.

The middle groups are representing function types, like lighting, blinds, temperature, etc.

And inside the middle groups we have the subgroups which are the real functions like R101 light switch, or R101 Light dim.

To the right it is a residential project.

Here is decided that each main group represents a function, like lighting, heating/cooling, blinds etc.

The middle groups represents here rooms.

So it is completely free how to create the structure and also how to name them. Each person seems to have their own way of doing this.

I however have a recommendation of how to name the subgroups.

And it is following the rule where, what, how.

So first in the subgroup name you have the room name, then what is controlled for example the light and finally how or which function that is used.

It can be quite time consuming to write all this, but there are ways to copy/paste and also to create a structure in excel which may be faster.

Abbreviations is also a way to speed it up.

But names are important and saves time when changes are going to be made later on, or when you are going to find out why it doesn’t work as you or the user expect.�Also if controllers are going to be configured outside of ETS, these addresses with names are exported and then useful names are quite helpful.�

73 of 93

In the software ETS it is possible to chose a 2-level group address style.
This format comes from the first generation of ETS, where this was the only format to use.
Normally 3-level notification is used
Example:�Main group / Sub group�Level / Function�1st floor / Room 101 Lamp group 1 On/Off

Group addresses

Group adress 2-level style (main-/subgroup

15

14

13

12

11

10

9

8

7

6

5

4

3

2

1

0

0-2047

0-31

16 bits (65 536 addresses)

74 of 93

From ETS4 it is also possible to chose a free level group address style. This style allows to structure group addresses in nearly unlimited levels. Levels are only a “Visual divider“ to organize group addresses, the addresses are expressed as sub group addresses only (0 - 65536)
This format is new from ETS4
At the moment not all products with ETS plug-in�support this format. For this reason usage of this�format should be carefully evaluated before use.

Group addresses

Group address free style (sub-group)

15

14

13

12

11

10

9

8

7

6

5

4

3

2

1

0

0-65536

16 bits (65 536 addresses)

75 of 93

The telegram consists of bus specific data and useful data, which provides information about the event (e.g. pressing a push-button).
The entire information is transmitted in the form of 8-bit long characters.

Telegram structure

8 bit

Up to 16 x 8

4

3

16 + 1 bit

16 bit

8 bit

Control field

Source address

Target address

Routing counter

Useful data

Check byte

Length

8 bit

Source address: is always the individual address of the sender

Target address: is an individual address in case of programming or service,

is a group address during normal operation, i.e. communication between bus devices

Useful data: bus command (e.g. “write” or “read”) and � value (e.g. ”1” or ”0” for ”switch on” or ”switch off”)

This is how the telegram on the bus is structured.

It starts with a control field, and then the source address, which always is the individual address of the sender of the telegram.

Then comes the target address, which is a group address if the telegram comes from a KNX device.�If it comes from ETS it is an individual address.

So if ETS downloads data, it will be to a specific device and then the target is the unique individual address of the device.

However, when KNX devices exchange data, they always do it via group addresses.

As you know, both types of addresses are 16 bits, and then there is 1 bit indicating whether the address is an individual address or a group address.�Then comes a routing counter which has to do with couplers. �And then we have the length which indicatate how many bytes of useful data that will follow.

And then comes the actual useful data, meaning the information that the sender wants to send to its receivers, could be on, off, up, down, dimming value, temperature value, etc.

The telegram is ending with a check byte so that the receivers can check that the bits have not been changed by any disturbance or interference on its way.

[The low level bus commands that a KNX device can use in runtime are ”write to the bus”, ”read from the bus”, meaning reading a value from another device, or answering to a read request. So there are these 3 low level commands and these can be seen if you record telegrams with ETS.]

76 of 93

Push-button with toggling on/off function. �Separate buttons for on and off is also possible, but would require double amount of buttons.

Practical example

Physical connection

Lamp 1

Lamp 2

Lamp 3

Lamp 4

1.1.1

1.1.2

Bus

77 of 93

Group objects

Configuration in ETS

Drag&Drop

78 of 93

Command sender

When Button 1 is pressed a telegram with group address 1/1/1 will be sent on the bus via the Switch object
The function and thereby the value in the telegram is pre-defined in the parameters, e.g. toggle-function = the actual object value is inverted and sent on the bus, i.e. every press sends alternately ON- and OFF-telegrams
The telegram will be received by all the sensors and actuators on the bus

Group objects

Runtime communication

Push-button 2-gang

Bus

Command receiver

When telegram 1/1/1 comes to the actuator it will be evaluated and control the relay of Channel 1. If the value is 1 (ON) the relay will close and if the value is 0 (OFF) the relay will open.
The actuator sends an acknowledge telegram �(low level Link Layer ACK)
Other actuators and sensors which does not have the group address 1/1/1 assigned will not evaluate and acknowledge the telegram

Switch actuator 4x230/16

0

So this is how it looks if we could see inside of the devices in runtime.

>

In the parameters of this push-button is deciced that the buttons should have a toggling function.

It means the first time I press, I want to switch on and the second time I press I want to switch off.

All products have parameters you can set to chose how they should behave.

In this case, for the push-button I could also have chosen that the button always only switch on and then for another button chose only to switch off.

But that consumes two buttons, and to reduce the number of buttons the toggling function is most often used.

So I press the button. As the object value is 0 in the beginning it will be inverted or toggled and then sent as value 1 using group address 1/1/1.

>

The telegram goes to the bus and is received by all devices on the bus.

All devices will analyse the telegram and see if it is for them, or not. If it is not for them, they through it away.

But this actuator see that group address 1/1/1 is linked to channel 1, so he will take it and send an acknowledge back so that the sender knows it is received OK.

If a sender doesn’t get an acknowledge or he gets a not ackcknowledge, meaning the telegram was distorted on the way, it can rpeat the telegram up to 3 times.�After that he gives up.

So this telegram will now change the object value of channel 1 to value 1, which will cause the relay to close by the application program.

So this is how it really works.

79 of 93

Group objects

Runtime communication (logical connection diagram, not in ETS)

PB1 Switch obj 1 Bit Toggle

Push-button 2-gang

PB2 Switch obj 1 Bit Toggle

PB3 Switch obj 1 Bit Toggle

PB4 Switch obj 1 Bit Toggle

Ch 1 Switch object 1 Bit

Ch 2 Switch object 1 Bit

Ch 3 Switch object 1 Bit

Ch 4 Switch object 1 Bit

Switch actuator 4-gang

1/1/1

1/1/3

1/1/5

1/1/7

0

1

0

1

0

80 of 93

Group objects

Runtime communication (logical connection diagram, not in ETS)

PB1 Switch obj 1 Bit Toggle

Push-button 2-gang

PB2 Switch obj 1 Bit Toggle

PB3 Switch obj 1 Bit Toggle

PB4 Switch obj 1 Bit Toggle

Ch 1 Switch object 1 Bit

Ch 2 Switch object 1 Bit

Ch 3 Switch object 1 Bit

Ch 4 Switch object 1 Bit

Switch actuator 4-gang

1/1/1

1/1/3

1/1/5

1/1/7

0

1

0

1

0

1

0

PB1 Switch obj 1 Bit ON

Push-button 1-gang

PB2 Switch ob 1 Bit OFF

1/1/0

1

0

1

0

Now let’s say we want to have a central function.

We want to switch all the four channels at the same time.

So I have another push-button, actually I’m having two buttons, one switching only on and one switching only off.

So I press the central-on button, it will send value 1 on group address 1/1/0, which will be received by all channels, so all switch on.

Now I press the first button of the first push-button unit.

What happens. It turns to one 1. So it switch on an already switched-on light.

What the user would have expected by pressing this button is that the light would switched off, because it is on and it is a toggling function.�>

So now the user must press the button again to switch off, so in total two times.

Also the status LEDs of the push-button will show the wrong status.

This we must fix.

81 of 93

Group objects�Run-time communication (logical connection diagram, not in ETS)

Group objects

Runtime communication (logical connection diagram, not in ETS)

PB1 Switch obj 1 Bit Toggle

Push-button 2-gang

PB2 Switch obj 1 Bit Toggle

PB3 Switch obj 1 Bit Toggle

PB4 Switch obj 1 Bit Toggle

Ch 1 Switch object 1 Bit

Ch 2 Switch object 1 Bit

Ch 3 Switch object 1 Bit

Ch 4 Switch object 1 Bit

Switch actuator 4-gang

1/1/1

1/1/3

1/1/5

1/1/7

0

PB1 Switch obj 1 Bit ON

Push-button 1-gang

PB2 Switch ob 1 Bit OFF

1/1/0

1

0

1

Ch 1 Status feedback obj 1 Bit

Ch 2 Status feedback obj 1 Bit

Ch 3 Status feedback obj 1 Bit

Ch 4 Status feedback obj 1 Bit

0

1

1/1/2

1/1/4

1/1/6

1/1/8

1

0

1

0

1

0

The reason we got this problem is that the first push-button didn’t know that the second push-button was controlling the actuator.

So what we need to do to really make this toggling function work, is that each channel of the actuator sends its status to the individual push-buttons.

And this is done via status feedback objects of the actuator and four new group addresses, which are linked as a second group address to each button.

So what will now happen?

I switch on, all channels switch on.

Now every channel wants to send their new status as it has changed.

And they are sent one by one. Updating the values in the push-buttons.

For button 1 the sending group address is 1/1/1 and the group address 1/1/2 is a second and thereby a receiving group address.

So the values of the push-buttons are updated or synchronized with the actuator, which means that when I press the first button now, it will send a switch-off as expected.

This synchronization procedure is only needed when toggling functions are used, but toggling is very often used both for switching and dimming.

So now you should have an understanding that the communication is all about manipulating the input object values of the application program of each device and this is done with group address telegrams instead of physical wires.

82 of 93

6. KNX Configuration and commissioning with ETS

Confidential Property of Schneider Electric |

Page 82

83 of 93

ETS (Engineering Tool Software)

The manufacturer independent tool to design and commission the KNX-project.

Product database

Contains the application programs which finally shall be downloaded into the products. Available for on manufacturers home page or in the KNX online catalog (directly accseible from within ETS, but Internet access without blocking firewall is required).

Planning and function description
KNX-products

When the design is finished the configuration data are downloaded into the products

Necessary for design and commissioning with ETS

Confidential Property of Schneider Electric |

Page 83

84 of 93

The manufacturer independent Engineering Tool Software enables to design, configure, commission and diagnose a KNX installation.
The device-function related application programs are part of the free available manufacturer product databases.
By commissioning they are loaded into the devices by the ETS via USB or IP interface of a PC and the bus.
No limitations as regards to number of installable devices or number of projects for ETS Professional
ETS can only be obtained from KNX Association via Internet in the My KNX portal (https://my.knx.org)

ETS runs in demo mode without license (limited to 5 KNX devices)
Licenses in form of a USB-dongle for Lite (20 KNX devices), �Professional (unlimited) and Supplementary (unlimited) must be purchased in My KNX (for each Professional you can purchase 2 supplementary with a huge discount).

Configuration tool ETS Professional

Engineering Tool Software

Confidential Property of Schneider Electric |

Page 84

Current generation: ETS5

The manufacturer-independent Engineering Tool Software is used to design, configure and commission KNX-installations to the full extent of KNX.

It also provides diagnostic functions.

As it is manufacturer independent, it must be loaded with product data as in from of application programs and these comes from free available product databases or from the KNX online catalog as mentioned.

[downloadable from the manufacturers home pages. Many manufacturers, like Schneider, are also offering the product data in the ETS online-catalog managed by KNX Association, so that they can be downloaded directly in ETS via Internet.]

ETS Professional has no limitation as regards to the number of installable devices or number of projects. So you buy this, it is 1000 Euro without discount, and then you can create as many and as big projects as you like.��ETS can only be obtained and purchased from KNX Association via my.knx.org. So you create an account there, free of charge of course, and then you can download the software and purchase licenses in the online shop. Without a license the ETS runs in demo mode with the only limitation that you can only include 5 devices in each project.

There are a Lite license for 20 devices and 150 Euro, which is good for really small projects, training centres and testing.

To work with real projects you need the professional or supplementatry license. The supplementary is the same as professional and just a way to give discount in case you need several licenses. For each professional you can buy 2 supplementary for 150 Euro each, so 3 licenses then cost 1300 Euro instead of 3000 Euro.

85 of 93

Planning documentation

Building drawings/floor plans

room designations
which KNX devices are installed where
bus cable layout (topology structure)

Actuator scheme/Cabinet drawings

Which KNX actuators are installed where and what electrical consumer are connected to each of their outputs

Function description

What and how should things be controlled

Necessary for project design with ETS

Confidential Property of Schneider Electric |

Page 85

86 of 93

Creation of the building structure (e.g. floors, rooms, cabinets)

Configuration steps in the ETS

Building structure

Confidential Property of Schneider Electric |

Page 86

87 of 93

Creation of the topology (i.e. areas and lines)

Configuration steps in the ETS

Topology view

Confidential Property of Schneider Electric |

Page 87

88 of 93

Insertion of products in the building structure by drag & drop from the product catalog
Assignment of individual addresses to the different devices (for the unique identification of a sensor or actuator in the KNX installation)

Can be handled automatically by ETS

Configuration steps in the ETS

Insert products in the Building view

Confidential Property of Schneider Electric |

Page 88

89 of 93

Selection and setting (parameterisation) of the appropriate application software for sensors and actuators
The parameter settings have influence on which group object that will be available

Configuration steps in the ETS

Set parameters of the devices

Confidential Property of Schneider Electric |

Page 89

Parameter settings of Switch actuator 4-gang with current detection

90 of 93

Create a group address structure and individual group addresses
It is possible to import a group address structure, �e.g from another project
Group addresses can also be exported, edited in Excel and re-imported

Configuration steps in the ETS

Create group addresses

Confidential Property of Schneider Electric |

Page 90

91 of 93

Configuration steps in the ETS

Link group addresses to group objects

Confidential Property of Schneider Electric |

Page 91

92 of 93

Commissioning of KNX devices can be done before (one by one) or after installation in the project

Connect the PC to a bus interface �(USB interface or IP-network with a KNX/IP inteface or W4K/sL)
Select device(s) to commission in ETS
If a device has not been programmed before, its individual addresses must first be downloaded (one time action).�ETS will ask you to press the programming button of the device to assign the address. Download time 5s.
Download the application program (incl. parameters and group addresses). Download time depends on device, most takes 30-45 s.

Tip: Program first the individual address of all devices (before or after installation), then after installation, start download action of application programs for several or all devices (and take a coffee break)

Configuration steps in the ETS

Commissioning

Confidential Property of Schneider Electric |

Page 92

Programming �button and LED

All that we have seen so far can be done offline, with no connection to the devices.

The commissioning or programming of the devices can be done before installation one by one or after installation.

Connect the PC to a bus interface; could be a USB interface or a KNX IP device on the network.

Select device to commission in ETS

If the device has not been programmed before, its individual address must first be downloaded.

You must then press the programming button of the device to download the address from ETS. It only takes a few seconds.

Then download the aplication program with the parameters and group addresses. It takes between 30 and 45 s

The most efficient way is to first download the individual address of all devices one by one.�Then after installation, start the download action of application programs for several or all devices, and take a coffe break.