KNX Development Header

How To Start?

The starting point is the KNX Specifications , which can be downloaded for free. You can develop the following within the KNX ecosystem:

Videos about KNX Development

KNX Devices

There are three different approaches when developing KNX Devices:

Approach Description Required efforts

Full development   Cost: low 

Time to market: slow

The Manufacturer opts to develop entirely the KNX product on his own. This implies that the only basis for his development is the KNX specifications and that all parts of the product (Physical Layer, Communication Stack, Application Program as well as ETS product entry) need to be developed and certified. This is not an option if one wishes a quick time to market. This however has the advantage that one is totally independent from any supplier. This scenario is thus more suitable for larger companies with a big development capacity aiming at a larger product range.

Engineering, software development, testing and admin work.


Partial development   Cost: medium 

Time to market: relatively quick

The most ideal case for starting manufacturers developing new products is to take recourse to available KNX certified system components (see “System components” on this Website) and/or stacks or even platforms including certified runtime application blocks. In this way, the development is limited to the design of an application program and the preparation of an ETS product entry. Also only these parts are subject of KNX certification. KNX even offers a Development Cookbook with examples based on existing system components as part of the KNX Standard (Volume 2).

Partial engineering & software development. Easy testing and admin work.


Acquisition of OEM equipment                                  Cost: high 

Time to market: quick

The Manufacturer opts to relabel existing KNX end devices of another KNX member with his own brand name. The development effort in this particular case is reduced to nearly zero, as it is limited to the reregistration of existing ETS application programs in the name of the reselling manufacturer. This is an administrative procedure and does not require retesting of the products.

Administrative work

c1
c2
c3
c4
 
Step Description

1. Select a profile (KNX Specifications, Volume 6)

The KNX standard foresees a number of KNX system flavours, which amongst others determine the extent of run-time functionality as well as how the device is configured. These are called profiles and are described in Volume 6 of the KNX Specifications. So, depending on the desired functionality and how it shall be configured, the manufacturer has to make a selection of the adequate profile. The selected profile will in turn determine the type of microcontroller platform one is able to use for one’s development of the communication stack.

2. Get right development tools and system components according to KNX media

Once the profile is fixed, the development of the hardware of the device can start, as well as the software called ‘application program’. One will need to find the necessary development tools corresponding to the chosen microcontroller platform (e. g. compiler). The developer will also have to decide on the type of KNX medium the device will use for communication, i. e. Twisted Pair, Powerline, Radio Frequency or IP, the four available KNX media.

3. Create Application Program (ETS database entry)

As the binary code of the application program resulting from the above development cannot be handled by an end user (typically a contractor), the code needs to be ‘wrapped up’ into a format that is readable by the end user and can be read by ETS. For this, the manufacturer needs to get hold of the KNX Manufacturer Tool through MyKNX. As any device that is handled by the ETS shall be submitted to KNX certification, it is highly recommended that during the development stage appropriate input is prepared for the later certification test campaign. For this, KNX offers the KNX Interworking Test Tool, also available via MyKNX.

4. Registration, Testing and Certification

Once conformity has been sufficiently checked by the manufacturer himself, the application program can be submitted to KNX for registration. When registering the application program, it will be signed by KNX. Only signed files can be imported into the ETS end user tool and submitted to the KNX accredited test houses for formal KNX certification conformity testing. From registration onwards, the manufacturer is able to market the product branded with the KNX trademark.

KNX IoT

Check out the KNX IoT Webinar recording in 4 languages:

Webinar also available in: German - Spanish - French

Steps to start your KNX IoT development research

Resources Description

1. Install the ETS App “KNX Web service exporter”

The KNX Web service exporter ETS App (free of charge) allows creating a XML file with the KNX information model from an ETS project. The exported project can be used with the KNX Web Service gateway demo.

2. Download the Proof of Concept: KNX Web service gateway demo

Download the proof of concept implementation of the KNX Web services: a technology demo gateway oBIX implementation. Includes an image to be used on a Raspberry Pi 2, can import an information model created by the ETS App “KNX Web service exporter”. Free of charge.

ETS Apps

ets_apps

Steps to develop an ETS App

Step Description

1. Start your ETS App development

Create an account in My KNX and download the ETS Software Development Kit (ETS SDK) and the Tutorial for using the ETS App Validation Tool.

2. Download the Proof of Concept: KNX Web service gateway demo

When you are ready to test your ETS App, apply to KNX in order to change your status to ETS App Developer and get access to ETS App Validation Tool.

3. Upload & Validate your ETS App

Once your ETS App has been finalized, upload it and ask for validation in order for the App to become available in My KNX. Only validated ETS Apps can be installed and used in the ETS. That prevents from unauthorized use of your ETS Apps. However, when your ETS App is validated, you can either select to keep it ‘private’; i.e. only for your own use, or make it ‘public’, so that everybody is able to download and use it.

4. Start selling your ETS App

From now on, you can offer your ETS App amongst others via My KNX!

KNX Association support

KNX Members, in addition to having access to the tools required for developing KNX Devices, KNX IoT and ETS Apps, will be informed on a regular basis about the latest technological news that concern to the industry. The trimestral Technology eNews is sent to Product Managers, Certification Coordinators, Hardware Developers and Software Developers from all the members of the KNX Association. In addition to this, special Webinars and events are organised exclusively for KNX Members.

Download the KNX Cookbook!

Could you use some help or inspiration with your KNX device development? This KNX Cookbook for developers gives some practical examples of how to implement the KNX standard with different devices. Simply fill in this form and we will send you a link to download the cookbook.

KNX IoT 1.0

Web services

Web services

KNX Specifications

Version 2.1

Finding your way in the KNX Standard

Finding your way in the KNX Standard

KNX Technology

Read more about KNX Technology here

KNX Technology