As of ETS5, the Project/Product Memory replaces the previously used method of storing KNX projects and products using a database (engine). Essentially, this means that as of ETS5, no (SQL) database is used at all any more for any type of data storage. Consequently, the following points in connection with the database, the SQL database installation for ETS installation (100 MB) and the installation of a continuously-operating database service are no longer used.
1.The Project/Product Memory: a normal, local PC directory that is empty at first and in which later all (1..n) imported projects, KNX product database entries (catalog entries) and restore points (if enabled) are saved; all three areas are set up in the directory so that they are logically separated.
2.The Project/Product Memory does not have to be installed.
3.The path for the project memory is configurable in ETS.
4.The path for the product memory is configurable in ETS.
5.Files (plural!) contained in the Project/Product Memory are projects / KNX product database entries (catalog entries) that have been "prepared" for quick access.
6.The Project/Product Memory structure and the file content are not (and will not be) documented publicly; the exported project represents a public and documented interface!
7.The Project/Product Memory and the files contained there are protected against manipulation (signature).
•The Project/Product Memory cannot be installed directly on removable storage media or network drives for simultaneous access. This also applies for normal USB flash drives as well as the KNX dongle with the integrated USB memory.
In order to prevent simultaneous access to the data from more than one ETS5 (e.g. computer A with ETS5 and computer B with ETS5 accessing project/product memory on network drive XY at the same time), a feature which blocks this kind of access has been integrated in ETS5. The project archive function is provided for the editing of projects by more than one user (not simultaneously).
The use of synchronization services (such as Drop Box) for the Project / Product Memory (regardless of whether it is located on a network drive or removable storage medium or directly on the HDD) is entirely at your own risk and is very strongly discouraged, because these services operate in a file-oriented manner. ETS works with various, individual files, for example, for one and the same project, as in point 5 above. This would not preclude the possibility that one part of the project would have been synchronized with a different, external state (because it was updated by a second, external ETS user) even though the local ETS wants to read/write using the original data (race condition).
Copying the Project/Product Memory between computer A and computer B (bypassing the project export function to possibly save time) is forbidden because any possible plug-ins installed on a computer are not copied at the same time and the project data created for the project by these plug-ins is ignored (this data is only added to the exported project by the plug-ins during a project export procedure).
One reason for this is that ETS first of all checks the local data in the Project/Product Memory when creating it or after an import of projects for its current XML Schema and, if needed, converts imported projects to match. A simple copy operation outside of ETS does not provide for this.
ETS recognizes and prevents the opening of projects if the Project/Product Memory or parts of it (individual projects) are from a different ETS or computer or were copied from there. A corresponding message is issued and the operation is canceled.
Relocation or moving of complete projects/ product memories from computer A to computer B (e.g. after reinstallation of ETS) can be performed either using Project Export/ Project Import or by working with the project archive function (check in from computer A to the archive, check out from the archive to computer B).
•An empty product memory contains no KNX product database entries from manufacturers (devices/applications). In order to add a device, you must import the corresponding KNX product catalog for at least one device.