KNX - The Idiots Guide
Well, I've been looking into using KNX for Home Automation for a while now but still couldn't get my head around it. I subsequently decided to put some money into it and purchased a basic set of kit but found I wasn't able to get it to work. The key goal, press a button and it turns on a light, I never got working......:(
I had the opportunity this week to travel to London on a few days holidays and linked up with a KNX trainer for a day. I subsequently found a small configuration issue that caused my problems and having brought over a subset of my KNX kit, was able to apply this knowledge and got it to work!
What I hope to do here now is show you how to create a basic KNX setup from scratch and configure a basic lighting setup. A KNX course is probably still the best way to go but if you have the time and inclination this stuff is possible to learn and figure your way around.
To start with you'll need a switch, an Ethernet Interface and a DHCP server to offer the KNX IP Interface an IP. You can use a simple windows service like
http://www.dhcpserver.de/ and make sure you let it disable the necessary firewall interfaces and if you've more than one network card, setup the service on the correct one. Once configured you will see it running in the systray down the bottom right and when you power on the KNX IP Interface it will offer an IP to the MAC Address printed on the KNX IP Interface. That's all you can really do with that device. I wouldn't bother fixing a static IP on it at this stage.
In ETS5, go to the Bus section and select the Discovered Interface and then Click Select to make it the current interface. You can also test it here by clicking the test button.
Now you can create a new Project. The most important thing here and where I went wrong is selecting the right bus interface - SELECT TP HERE EVERYWHERE!
This step cost me 4 weeks! Thankfully in London I was able to see a working setup and having brought over some of my own kit, get that configured to my satisfaction too. This gave me confidence to go back home and setup my lab correctly.
In ETS change the view to the Project Root. This gives you all the different views you need in one section. Now you need to ensure all your devices are imported & listed. Due to differences in available devices depending on the Language chosen some devices may not be listed automatically. Also note that you may need to enable certain Apps:
I went for compatibility mode and the Online Catalog which are free but require tinkering with the myknx.org licensing portal to activate. Bit of a pain to be honest. They also offer more advanced apps which look useful but come at a cost. If you're using ETS regularly consider them but for a once off home build project, I'd suggest you can get by without!
So, I purchased several devices from
http://www.eibmarkt.com and found none were listed in the online catalog as this company chooses NOT to publish them there at all?!! Well, I wanted a reality check by buying real kit and got one! There are lots of KNX manufacturers but the KNX Organization appears to want to keep the knowledge very private so it's hard to know in advance what will work easiest without having a mentor or guide. Anyway, it won't stop you but it can be confounding! My own order consisted of the following items. I've been subsequently told that the power supply I used which comes in 3 parts could be replaced with a single unit if I'd known what I was doing!
|
Push button 1 make
contact (NO) white 242134 - Special sale - 1 pce. Available
Product No.: AA0819148
Manufacturer: Elso
Manufacturer no.: 242134
|
|
EIB KNX IP Interface
PoE, with up to 5 tunneling connections
Product No.: N000401
Manufacturer: EIBMARKT
Manufacturer no.: N000401
|
|
EIB KNX 360° Presence
Detector KLR incl. bus coupling unit!
Product No.: N000530
Manufacturer: EIBMARKT
Manufacturer no.: N000530
|
|
EIB KNX Voltage supply
29.5 VDC with 1 choke 640mA (SV-2/DR1)
Product No.: N000601-DR1
Manufacturer: EIBMARKT
Manufacturer no.: SV-2/DR1
|
|
EIB/KNX Push Button
8-fold, White matt finish - BE-TA5508.01
Product No.: N760052
Manufacturer: MDT
Manufacturer no.: BE-TA5508.01
|
|
I/O device for bus
system 4 In/ 12 Out US/U12.2 - special offer
Product No.: N780113
Manufacturer: ABB Stotz S&J
Manufacturer no.: US/U12.2
|
|
EIB KNX bus cable ring
100m green EIB-Y(St)Y 2x2x0,8
Product No.: NS0140116
Manufacturer: Verschiedene-Diverse
Manufacturer no.: EIB-Y(St)Y 2x2x0,8
|
|
DIN rail 247mm steel
UZ01B4
Product No.: NS0661480
Manufacturer: HAGER
Manufacturer no.: UZ01B4
|
|
Push button 1 make
contact (NO) grey 5TD4701
Product No.: NS0850394
Manufacturer: Siemens Indus.Sector
Manufacturer no.: 5TD4701
|
|
Switch actuator for
bus system 16-ch 5WG1567-1AB22
Product No.: NS6508387
Manufacturer: Siemens Indus.Sector
Manufacturer no.: 5WG1567-1AB22
|
So if you want to use the above as a benchmark go ahead! The IP Interface is an OEM unit and you'll see several other Manufacturers use & rebrand it too. I purchased a bit of MDF from B&Q and proceeded to wire everything together. I used a local Electrical merchant for the bulbs, fittings, electrical cable etc and put a functioning system together to learn the various options and how they work. See the picture of my kit below.
So, I want now to import my actuator which controls power to the light socket. I found merely attaching this device to the KNX bus was not sufficient, it also requires it's own 230VAC supply! I can test the bulb in manual mode fine. To import it try the online catalog first in ETS. I found all the Siemens Industrial Products here:
I searched the contents link and found the actuator. It should come down in a knxprod file which indicates it's received some attention lately, a vd5 or lower extension means a much older catalog file and might not be that useful. Now you can import it into KNX in the Catalogs section:
You can choose to import everything or just what you want. I imported everything which then installed some extra plugin content and got subsequently stuck, so I went back and just installed a single device!
Here is my search for "567" showing the device up correctly.
Now we can check the knx push button 8 fold switch is there:
So, now we go back to our Project and link this all up! I've created some building objects as follows:
Then searched for my Switching Actuator:
Now I can add this into a particular area of my building, in this case my Utility Room, I added the push button to my Living Room too as shown below.
Next I add the switch into the living room
I can customize the devices before going further. This is to enable/disable particular buttons or parts of the device to make it simpler to configure. If you've an 8 button switch, the MDT one disabled all 8 buttons by default in my setup whereas the Siemens actuator enables all 16 connections! Set this up now and you won't have too many options to ignore later.
I'll start by enabling the top two buttons on the MDT knx switch as follows:
And change the behaviour of the buttons as follows:
ETS has automatically added the devices to appropriate "lines" so next we'll join them under Group Addresses. We'll need to create a topology here. An example is shown below:
This should be sufficient for our needs to turn a bulb on and off and change the status LED on the push button. Under Topology you can right click the "Button 1 - Switch" and choose "Link with" and select "1/0/1 Light 1". Do the same with Button 2 to Light 2.
You can now associate the Actuator Channel H in my case with light 1
Now it's time to program the devices. There are two steps here per device. One is to "Download individual address" and the second "Download Application".
Note: the 20 device limit in ETS Lite means each device uses a license, so my 16 port actuator is ONE license, the KNX push button 8 fold is ONE license etc. This should be ok for a home setup but add a weather sensor, presence sensor and multiple push buttons in each room and you'll quickly run out!
Make sure all your connections are firm - my KNX bus wire to the actuator was loose and the programming light wouldn't come on. I next found my ABB binary input device already on 1.1.1 so changed the addresses by incrementing them by 1. I was then able to program the actuator fine.
Next you "Download Application" and if all goes well you hear it reboot and you see this:
If you use the wrong device download you can damage the device. We saw the display on a temperature sensor fail in the lab I attended as an example.
Next I did the push button switch, The issue I found was there was no obvious programming button. With these it's best to get the manuals as sometimes there are particular button presses required to activate programming mode.
This is a good example of a KNX device manual - there are LOADS of options to play with. It turns out it does have a programming button but it's not easy to spot!
So, now we should be able to actuate the lightbulb if I've done my configuration correctly. It works! I can use Diagnostics to verify the bus operations:
My physical setup is as follows:
It's not tidy but it works. Each bus connector has 4 connectors for red and black so you can daisy chain away or connect back multiple devices if you wish. Wiggling the cables out again is hard. The KNX cable uses SOLID copper, whereas alarm cable uses thin strands. Don't try to use the wrong cable here - I'll use alarm cable for the ABB binary inputs but KNX bus interface cable will always be taken from the green KNX cabling I purchased with a solid core. I stripped out the colours I needed to make it easier to work with in my lab.
So, that will give you a quick intro to KNX. I can't get the push button LEDs to function but will resolve at some point. I've a POE switch for power but you can power the IP interface off the KNX bus if you prefer. I hope to have a few IP Cameras so it makes more sense to get the POE in now. Hope this helps you get the light bulb working, believe me, once you get the first one turned on, mark the date, as it's onwards and upwards from there!