Skip navigation

Which services are offered by the KNX-accredited testing laboratory?

  • You register your hard- or software with the KNX Association and may then begin marketing immediately.
  • You then submit a positive test report to the KNX Association (within 6 months). To do this you place a test order with us and send a test sample (it must be a serial device). In order to ensure that the six-month deadline is met, place your test order immediately after successful registration.
  • We test hard- and software in accordance with the KNX Association guidelines (see current handbook). 
  • After successful completion of a positive test you and the KNX Association will simultaneously receive the test report as a .pdf file. 
  • If we detect a fault, you have the opportunity to remedy this. We interrupt the test und continue when the fault has been remedied. 
  • We return the test sample to you.
  • A registered ETS database 
  • Data sheet for hardware 
  • Data sheet for software 
  • Description of device 
  • PIXIT or PIXIT header and a software description comparable to a PIXIT for each application. Please ensure that all communication objects and parameters are described in full. 
  • Description of behaviour of the device after programming. 
  • Description of the behaviour after loss and return of bus voltage
  • Because of the complexity of the devices a specialist, who is not involved in the development process, is required to test the device before market launch. If faults or errors are detected (and this is the rule), an error report is sent to the developer who then remedies the fault. This process continues until the preliminary test is completed successfully. 
  • Unlike KNX certification tests, preliminary tests can be carried out on unregistered samples and pre-serial products. 
  • The scope of the preliminary tests (and thus the costs) can be fixed beforehand. As a rule, the test should be restricted to typical test scenarios since a 100% test is cost- and time- intensive. 
  • We recommend applying for preliminary tests and the KNX certification test together. In this way costs, time and effort can be reduced.
  • Stack testing is always required if, during the development of the device, you do not use an already certified bus couple but implement the protocol stack yourself in any available processor. 
  • In this case, or if the system stack is modified, testing must be done according to the method prescribed by the KNX Association.
  • Management Services 
  • Application (Interface) Layer 
  • Transport Layer 
  • Network Layer 
  • Link Layer, Data Part 
  • if applicable User Management Services, EMI/IMI Services, a so-called Witness Test of the Physical Layer (Coding, Decoding and Collision) and of the Link Layer (Physical Part) f TP1 Stacks, which are superimposed on a certified ASIC.
  • KNX products are becoming more and more complex. This is especially true for display and operating devices such as screens, touch panels, visualizations, etc. In addition Windows special software, so-called plugins, are used more and more frequently to programme these devices.
  • Benefit from our testing experience in other fields. We would be pleased to test any software-based products, not only those implemented in the technical sub-sections of buildings.
  • Conformity tests according to the KNX Handbook Chapter 9/2. It is not only necessary for KNX devices to be interoperable at the software level und meet the KNX standard. The hardware must also fulfil certain requirements before it may bear the KNX logo. 

There are two possiblities: 

1. The customer may conduct the hardware tests himself in accordance with the KNX handbook which are submitted to us together with an EMV/CE test. We then validate the test results received, and, if completed successfully, issue a positive test report. This can then be submitted to the KNX Association for certification.

2. If you do not wish to conduct these tests yourself, we can perform the required measurements for you according to the KNX handbook. In this case, all you need to do is send us an EMV/CE test for your device.

What to pay attention to...before the test:

According to the KNX specifications only registered product databases may be used for the application test »Interworking and Functionality«.

  • For stack tests unregistered products (e.g. development boards) may also be tested with an unregistered application. The test samples and applications are then archived at the testing centre as back-up samples for any retesting by the KNX Association (refer to KNX manual , vol. 5).
  • Complex parameters, complex functions, many interdependencies, inert device performance etc. significantly increase the time and effort required for the test. 
  • A fast testing procedure is only possible if the function and description of the device, the device combination and/or the software are fault-free. 
  • Please check for any deviations from the EIB/KNX standard before the test is started. Any modifications should be confirmed in writing by the KNX Association in order to avoid delay and additional costs. 
  • To keep costs to a minimum:
    - Only use those functions in an application which are absolutely necessary.
    - Before launching the product on the market, perform sufficient tests so that as many faults as possible have been eliminated.
    - Before placing the order, ensure that all documentation and devices are available.
  • In principle the manufacturer may provide his own test sequences. 
  • The benefit is that this may reduce the testing costs depending on the type of device and / or application. 
  • Disadvantages are, for example, that the test engineer must first become acquainted with the test structure of the sequences and validate the test sequences. This means, however, that there is no longer an independent evaluation of the product, and it may be that any missing test components have to be integrated into the test sequences at a later stage.
  • If, according to Vol. 5 of the KNX manual, the same application and the same firmware are used for devices with fewer channels and only non-existent channels or functions in ETS are hidden or deactivated in the device, then it is only necessary to test the master device. For all other devices in the product family it is only necessary to fill in the KNX form »Modification Declaration« and submit this to KNX. 
  • Enter your complete address in the first section. 
  • We then require details of the scope of the tests required. 
  • For each test required please indicate which testing regulation was followed during the development of the device or software. 
  • If you use an additional application controller and deactivate parts of the stack in BCU or BIM and reimplement them in the controller, additional tests of the implemented layers are required. If you use additional management functions such as User Management Services, then these must also be tested. 
  • Please enter what is to be tested in the device and application fields. Please fill in all the appropriate fields. 
  • Please tick which documents you have submitted with the test application. Also enter how many test samples are included. At least one device from serial production is required (preferably two devices, in case a fault arises).
  • In order to process your request for testing, we require your written order, preferably using our form »Test order«. 
  • If possible, please use our form »Test order« when submitting an order. Should you submit your order informally, please make sure that we receive all the necessary test devices, details, documents etc. together with your order.
  • If, for example, in a device family, devices are listed in the test report which do not need to be tested.
  • In case of an error in a stack test, when only one layer needed to be corrected and other layers are not influenced by this correction.

What to pay attention to...during the test:

  • The test can be interrupted or cancelled at any time at the customer's request. In case of cancellation the hours required up to this time will be invoiced.
  • KNX must be notified of any modification of the firmware using the KNX form »Modification Declaration«. Under certain circumstances it may be necessary to test the device or the applications again. This is decided individually by the KNX Association.
  • We contact you to clarify if the behaviour observed is a fault. If a fault does in fact exist, then, in serious cases, you can decide whether it makes sense to continue the test in order to detect further faults or whether to interrupt the test. You can then remedy or correct the fault. The type of correction is dependent among other things on the type of fault. Should you need more than 3 weeks for the correction, then, in accordance with our terms and conditions we will issue an interim invoice. According to KNX regulations a repeat test must be performed f the application or the firmware is modified. 
  • This depends on many factors e.g. complexity of the application or device, possible errors in documentation, possible faults in device or application, number of orders in hand, possible duration of correction by developer.
  • A simple device can be processed within a few days. For a more complex device with faults/errors, the process may take several weeks.

What to pay attention to...after the test:

  • If all the steps of the test have been completed without fault or error, you will receive a positive test report in electronic form. This will be sent to you and the KNX Association via email simultaneously. When you receive the test report you can have your product promoted at the KNX Association to the status of »certified«.
  • When you receive the test report you can submit this to the KNX Association and your product can then be promoted at the KNX Association from the status »registered« to the status »certified«.
  • As well as all the data for the device, a positive test report includes a detailed documentation of the configuration settings performed on the device and the EITT tracing record so that reproducibility of the test situation is possible at any time.