This article covers the following topics:
Development options
There are three different approaches when developing KNX Devices:
Full development
Cost:
Low
Time to market:
Slow
Description:
The manufacturer opts to develop the entire KNX product from scratch. This implies that the only basis for its development is the KNX Specifications and that all parts of the product: i.e. Physical Layer, Communication Stack, Application Program, need to be developed from scratch and certified. This option will no allow a quick time to market, it however has the advantage that the manufacturer is totally independent. This option is thus most suitable for companies with adequate development capacity aiming large production numbers.
Required efforts:
Hardware engineering, software development, testing and administration.
Partial development
Cost:
Medium
Time to market:
Relatively quick
Description:
This option is most suitable for companies starting as KNX Member, because it allows to develop new products based on available and already KNX certified system components and/or KNX certified communication stacks or KNX certified modules including the (KNX certified) Application Program. In this way, the development is in 'worst case' limited to the development of the Application Program. Also the certification is in 'worst case' limited to the Application Program. KNX even offers a Development Cookbook (see 'Downloads' in MyKNX available after login) with examples based on KNX certified system components. The Development Cookbook is part of the KNX Standard (Volume 2).
Required efforts:
Partial hardware engineering & software development. Simplified testing and (less) administrative work.
Acquisition of OEM equipment
Cost:
High
Time to market:
Quick
Description:
The Manufacturer opts to re-label an already certified KNX device developed by another KNX member. With this option the development effort is nearly reduced to zero, only the Application Program(s) need to be registered in the name of the reselling manufacturer. This is a pure administrative procedure and does hence not require any (re)testing of the device.
Required efforts:
Administrative work
Recommended steps
Step 1: Select a profile (KNX Specifications, Volume 6)
Description:
The KNX Specifications foresee in a numerous amount of device features, these features have because of the sake of compatibility/manageability been 'grouped' into a number of KNX system profiles, which determine the run-time functionality and the way the device is configured (by e.g. ETS). These profiles are described in Volume 6 of the KNX Specifications. I.e. depending on the desired device functionality and how it shall be configured, the adequate profile shall be selected, which will also determines the type of microcontroller that can be used in order to development the communication stack.
Step 2: Select the system components according to KNX media
Description:
Once the profile is fixed, the development of the device hardware can start, the required decision to be taken is about the desired KNX medium that the device shall apply for its communication: Twisted Pair, Powerline, Radio Frequency or IP. The chosen KNX medium type determines the type of system components that can be used in order to develop the hardware of the device.
Step 3: Develop the Application Program (ETS product entry)
Description:
Once the device hardware is ready, its software called 'Application Program' can be developed. Such application program typically will be loaded into the device by ETS. In order to make Application Programs available in ETS, i.e. to create its 'ETS product entry', another tool needs to be used. This tool is called the 'KNX Manufacturer Tool', which KNX members can retrieve through MyKNX. As any device that is handled by ETS shall be submitted to KNX certification, it is highly recommended to prepare the appropriate input for the certification tests during development. For this yet another tool is available for KNX members, i.e. KNX offers the KNX Interworking Test Tool (EITT) also via MyKNX.
Step 4: Registration, Testing and Certification
Description:
Once conformity has been sufficiently checked by the KNX member (during development), the Application Program can be submitted to KNX for registration. The Application Program will upon registration be signed by KNX. Only signed Application Programs can be imported into ETS and submitted to KNX accredited test houses for formal KNX certification conformity testing. The KNX member is after registration allowed to brand the device with the KNX trademark, i.e. in order to e.g. commercialize it.