The KNX standard foresees a number of KNX system flavours, which amongst others determine the extent of runtime functionality as well as how the device is configured. These are called profiles. 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.

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.

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.

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.