This online form shall be filled out for registration of any new Main product. It contains amongst others information on the product scope, test requirement class, used physical layer and stack, connector type etc. used in the product to be submitted for registration.
| Field | Explanation |
| Hardware Serial number | Fetched from *.knxei file. This is not the KNX Serial Number. |
| Hardware Serial version | Fetched from *.knxei file. |
| Product scope | Declare whether this product is fit for use in either the Home or Industry environment. If selecting Industry environment, this means that this product also complies with the Home environment. |
| Used standards for KNX hardware certification |
State whether the product complies with at least:
in conjunction with an appropriate product standard. More information can be found in Volume 4/1. |
| Product family and type | Select the product family and type. Only product families and types established by KNX Association can be selected here. Product can be found back with this specific product family/type on the KNX website. |
| Bus current |
Bus current in mA For Power supply units, this is the maximum deliverable current, for other devices this is the mean current drawn from the bus. This field is only applicable to TP devices. More information can be found in Volume 4/1. |
| Test class | Select one of the product test classes according to Volume 8/1. |
| Deactivation of layers used bus access unit | State whether all layers of the bus access unit are used or not. |
| Physical Layer certified | State which physical layer (chip) you have used in your product. |
| Stack certified on used microcontroller |
|
| Additional processor | State whether there is an additional processor next to the normal KNX processor. |
| Support of user management | State whether the device (i.e. the integrated microprocessor) is loaded via User Management Services. This is typically required when there are two microcontrollers inside one product. |
| Compliance to circuit diagram + component tolerances in case of certified chipset use | State whether, in case of use of a certified chipset, the chip (transceiver) complies with the circuit diagram and component tolerance guidelines as delivered with the data sheet of the chipset. If checked, this means that you use the chip within the specified limitations as regards tolerances in the specific circuitry. |
| KNX connector type for bus connection | Select the type of bus connection used as explained in Volume 9/1 of the KNX Specifications. Select "own solution but compliant with the minimum requirements" if you have opted for your own solution. |
| Type used for connection to application module | Select the PEI type used for connection to the application module as explained in Volume 9/1 of the KNX Specifications. |
| Connection to other non-KNX medium | State which medium the product can also be connected with which does not comply with the KNX requirements (e.g. IP (not KNXnet/IP), DALI etc.). |
| Direct coupling of SELV circuit to KNX |
Normally, all SELV circuits in a device must be separated from each other. It could however be that there are other SELV circuits (with similar voltage ranges as KNX) are connected to the KNX SELV. Specify in this case if SELV ancillary circuits in the device are directly connected to KNX, as per Volume 4/1 of the KNX Specifications. |