KNX Development Header

Certification of KNX Devices

The certification of a future KNX device must be planned in advance, so that the different aspects that involve the certification are naturally integrated into the development process. Some degree of certification will affect the development (except for OEM devices, which are already fully certified) and will depend on the KNX System components selected for the future device:

Physical Layer

Except for devices which communication media is IP (where Wi-FI or Ethernet Physical Layers are utilized), a certified KNX Physical Layer is required. The most popular approach for KNX Members is using existing system components to trust the access to the communication media. This releases the manufacturers from developing and certifying their own Physical Layer, which otherwise makes sense for very large manufacturers or microcontroller manufacturers.

Communication Stack

The KNX Stack is responsible for the bidirectional communication between the transmission media (via the Physical Layer) and the application. It basically wraps the information generated by the Application Program into a KNX telegram (as well it deconstructs the telegram for the Application Program to access the data). Manufacturers can develop their own one (with the development effort involved) based on the KNX Specifications, for what certification is required. Only KNX Test Labs accredited for such purpose can carry out tests towards KNX Stack certification. Once the stack is certified, the KNX Member can use it for all future KNX devices.

Application Program

Besides the certified stack that is being used (either by developing one, by licensing it from a provider or by acquiring chipsets with the stack embedded), the only aspect to keep into account towards certification is the Application Program. This is the most conventional type of certification, and all KNX Test Labs are accredited to carry out the Interworking Tests involved with Application Programs. The goal is to produce a database entry for ETS, so that all KNX devices in the market can be programmed from a unique tool (ETS). Manufacturer Tool is required for manufacturers aiming developing an Application Program.

Therefore the KNX System components available in the market play an important role regarding the cost per unit as well the time to the market, following an inverse correlation between these 2 factors:

Application Program

EITT (Interworking Test Tool) is also available to KNX Member, so that pretesting of KNX devices can be carried out. This is of great help:

  • It saves time towards KNX certification in the selected Test Lab.
  • It helps to debug the KNX device thanks to the creation of sequences. 

Chek the EITT presentation on the right side of this page to see how EITT works and what its main features are.

KNX Presentation

Handling the Certification Paperwork

Handling the Certification Paperwork

EITT (Interworking Test Tool)

EITT (Interworking Test Tool)

KNX Documents

Scale of Fees

KNX Test Labs

Test Labs