Devices in a project will be configured via KNX product databases (see Parameter). They contain - by KNX certified - data (e.g. application version, manufacturer and other) to ensure uniqueness and finally to ensure always the compatibility at the KNX system.
Despite of this there are also exists data sets in a KNX product database which are - in view of above mentioned compatibility - uncritical, e.g. help texts, parameter texts and their translations plus more (e.g. bus current). Beginning from ETS5 onwards there is the possibility to update this data in a ETS project respectively in the project/ product memory (assumed an manufacturer provides this data in a newer version).
The main use case is here to add new languages respectively the correction of existing translations. But also the case of correct calculation of bus current in a line is affected here (keyword; prediction on missing consumption data of a device).
The associated function for this is available in the catalog in the list view via context menu. They can only be used /active when the ETS App Online KNX Product Catalog is available and active. Multiple Selection in catalog activates the function if at least one of the selected devices an update exists.
1.In the ETS in the product memory is a device existing (e.g. imported locally) or in ETS project there is a device already in use
2.A manufacturer provides for this device a new KNX product database via the KNX Online Product Catalog. Also an direct (local) import of the new product database for this device is possible.
KNX product database contains for the so called non registration relevant data an internal version indication (see notes). The ETS compares:
1.the version of local product memory with those in Online KNX Product Catalog
2.the version of local product memory with those in ETS project
Does the ETS realize an higher (or equal*) version the data of device with lower/ equal version will be updated (in case 1 in local product memory, in case 2 in ETS project, or if any both cases one after the other). But the Online KNX Produkt Catalog itself will not be updated (if there would be locally a higher version â not a good case, new data should be available online first).
•The version of non registration relevant data from a KNX product data base is not visible in the ETS user interface
•The version of non registration relevant data from a KNX product data base is available at the application, but even at the catalog entry or at the hardware program. Besides the above mentioned use case it is therefore also possible to update these areas (e.g. texts in catalog entry or assembly width)
* Explicitly for ETS3 created KNX product data bases do not have any version control (historically caused). Here the ETS5 assumes implicitly always an unique (permanent remaining) version of non registration relevant data, hence this only from ETS4/5 native products onwards version control can be used effectively.
The behavior of ETS3 on import is always (e.g. the compatible behavior of ETS5 when using ETS3 products) â copy always source data over the destination data on a existing application. Hence this (and without any version control on ETS3 KNX product data base entries) the behavior of ETS3 must be emulated in ETS5 with the comparison <higher or equal>.
The ETS updates also non registration relevant data on in principle identical application, but with different Fingerprint