Are you like Alex ?

1. How IT Came to Be: ETS, short for Engineering Tool Software, was created as a manufacturer-independent software tool for planning, configuring, and commissioning KNX installations. Before KNX became one common standard, Europe had different building automation systems such as EIB, BatiBUS, and EHS. These systems were developed by different groups, which made the market more separated and less universal. In 1999, the organisations behind these systems joined together to form the KNX Association, with the goal of creating one open and reliable standard for smart home and building automation. Instead of every manufacturer using its own programming software, ETS made it possible to import certified product data, set parameters, create group addresses, connect communication objects, and download the configuration to KNX devices. This helped make KNX more professional, flexible, and manufacturer-independent.

2. Versions: ETS1 was born in 1993 as the first ETS version for early EIB/KNX programming. It was mainly focused on creating projects and programming devices with one common tool. ETS2 was born in 1996 and improved project handling, device management, and the general workflow for professional installers. ETS3 was born in 2004 and became more powerful for larger KNX projects, with better product support and a more practical structure. ETS4 was born in 2010 and brought a more modern user interface, better database handling, and improved project organization. ETS5 was born in 2014 and became one of the most widely used versions because it supported modern KNX projects better, including ETS Apps, improved diagnostics, and KNX Secure support. ETS6 was born in 2021 and is the current major generation, with a more modern workflow, better usability, improved security, cloud-based licensing, and stronger support for newer KNX technologies such as KNX RF and KNX IoT.

1. For example: when you install a KNX push button and a KNX actuator, they do not automatically know each other. ETS helps you tell the push button: “When someone presses you, send a command.” Then you tell the actuator: “When you receive that command, switch the light on or off.”

2. You create a project: This project is like the digital plan of the building. It can contain rooms, floors, electrical panels, KNX lines, devices, group addresses, and all programming settings.

3. You add KNX devices: For example: Push button > The user Presses it. Motion detector > Detects movement . Switch actuator > Switches lights or sockets. Blind actuator > Controls shutters or blinds. Heating actuator > Controls heating valves.

4. You give every device a physical address: Every KNX device needs its own physical address. example : 1.1.10. Think of this like the personal ID card of the device. ETS uses this address to know exactly which real device it is programming. Simple example: 1.1.10 = Push button in living room 1.1.20 = Light actuator in distribution board

5. You set the parameters: Parameters are the settings of the device. This is where you decide how the device should behave. Example for a push button: Should the button switch a light? Should it dim a light? Should it control blinds? Should it call a scene? So parameters are like the settings menu of the device.

6. ETS shows the communication objects: A communication object is the connection point of a KNX device function in ETS. For example, a push button has a communication object for switching. A switch actuator also has a communication object for switching. When both objects are connected to the same group address, they can communicate. So the communication object is not the group address itself. The communication object is the function inside the device, and the group address is the communication channel that connects those functions. Example: Button object: Switch Actuator object: Channel A Switch.

7. You create group addresses: A group address connects one function from one device to one function from another device. For example, a push button and a switch actuator do not communicate because they are physically wired together. They communicate because both are connected to the same group address in ETS. When you press the button, the button sends a KNX telegram to the group address 1/1/1. The actuator is also connected to 1/1/1, so it receives the telegram and switches the lamp. Think of a group address like a “room chat” Imagine a WhatsApp group. Everyone inside the group can receive the message. A group address works almost the same way: Group address: 1/1/1 Living room light switching The push button sends: ON. The actuator listens and reacts: Lamp ON. So the group address is not a device. It is the communication channel for one function.

8. You connect objects with group addresses: connecting communication objects with group addresses is like putting people into a WhatsApp group. You create a WhatsApp group called: Living Room Light Switching Then you add these people: Push button and Switch actuator Now when the push button sends a message in that group that says " Turn ON", The switch actuator receives the message and reacts: " Okay, I switch the lamp ON ". So in KNX/ETS: WhatsApp group = Group address, People in the group = Communication objects, Message = KNX telegram. you only have to create group address and go to communication object of device and drag its object and drop it into it and do that for all communication objects of different devices you want to communicate together.

9. You download the programming to the real devices: After everything is set in ETS, you send the configuration to the real KNX devices. This is called download. Without download, the device does not know the new settings. So ETS sends the instructions from your computer into the KNX installation. AND You test if everything works After downloading, you test the function.