Back to ETS. With your own ETS.

Why this program exists

ETS checks the signature of a project file when importing it. It rejects a project written by KNX Atlas with “project file has no valid signature”.

The signature uses a key that is part of ETS. KNX Atlas does not extract it and does not use it. So your own ETS takes over this step: it imports the file in the background into an isolated, temporary project store and exports it with its own exporter, which writes the signatures.

Back in five steps

1. 1

   Choose the file

   Drop the .knxproj file on the window or choose it. Below, the program shows the ETS it found and whether its version is tested.

   
2. 2

   Enter the password

   Only for protected projects. The password goes to ETS in memory only; the new file is protected with the same password.

   
3. 3

   Set the destination

   The new file is called “<name> (ETS).knxproj” and sits next to the original. An existing file is replaced only after you confirm.

   
4. 4

   Let ETS do its work

   ETS imports the project, exports and signs it, then the signatures are checked. Large projects take a few minutes.

   
5. 5

   Check the result and import

   Devices, certificate, signature check and ETS’s messages at a glance. Then import the file in ETS 6 with File › Import project.

   

The pictures show the program window with demo data.

What it does – and what it doesn’t

Certificate and licence

ETS writes a certificate into the file when its exporter is given a licence. The program picks it the same way ETS’s own export does. Start ETS 6 once beforehand so that it finds your licence reliably.

Without a certificate, an ETS without a support licence imports at most five devices of the file – the result window says so clearly. A project with more devices than your licence allows per project is refused, just as ETS itself would not open it.

When the program writes nothing

If ETS dropped devices during the import, the topology lacks the backbone or main line, or ETS rejects the password, no output file is written. The program explains why and takes you back to the right step.

The resulting file has the same project content but is not byte-identical: ETS writes it with its own serialiser and, as with every export, adds the master and product data the project needs.

On the command line too

The same function is available for scripts. The password is read only from an environment variable, never from the command line. Exit code 0 means: written and accepted by ETS’s signature check.

KnxAtlasEtsExport.exe --input House.knxproj [--output "House (ETS).knxproj"]
                      [--password-env NAME] [--result-file result.json]
KnxAtlasEtsExport.exe --detect-ets

Frequently asked questions