This article covers the following aspects:
1. ETS install options
a. Via the setup file
Executing the ETS setup file (see here how to get it) starts the installation process, which can only be completed after accepting of the software license agreement via the corresponding button.
Important notes:
- Administrator rights are required in order to execute the ETS setup file.
- The language of the setup is automatically set to the language of the operating system.
b. Via the command line
The ETS setup file supports the following command line options.
|
Command line option |
Description |
| -passive |
|
| -silent | Similar to -passive, but the setup dialog is not displayed. |
| -log path | The (file) logging is redirected to the indicated path. |
| -lang language | Display the setup in the given language, e.g. "-lang en-US" |
The following exit codes codes have been defined:
| Exit code | Description |
| 0 | ETS setup was successful. |
| 3010 | ETS setup was successful, a computer restart is required. |
| 1641 | ETS setup was successful, a computer restart is initiated. |
| Other | ETS setup was not successful, a standard Windows error code is indicated. |
Important notes:
- Administrator rights are required in order to execute the ETS setup file.
- The language of the setup is automatically set to the language of the operating system but can be changed by including the -lang option, see the available languages.
Diagnostics
A setup log file is automatically created in the folder indicated by the %TEMP% OS variable. The name of setup log file has the following structure: 'KNX_ETS5_yyyymmddhhmmss.log', where 'yyyymmddhhmmss' represents the current date (year, month, day) and time (hour, minute, seconds).
The ETS setup contains several components, this is summary of the created logs files:
- ETS5: KNX_ETS5_yyyymmddhhmmss_n_ETS5.log ('n' is a consecutive number)
- Compatibility Components: KNX_ETS5_yyyymmddhhmmss_n_ETS5CompatibilityComponents.log (n is a consecutive number)
- .NET 4.x: the name of the log files dependent on the system configuration
Installation location
ETS binaries (including plugins) are always installed in the Windows system drive (usually C:\).
2. ETS uninstall/repair options
a. Via the Windows Control Panel
The .NET runtime environment cannot be uninstalled in this way.
b. Via the setup file
If ETS is already installed, executing the setup file (ETS5Setup.exe) displays the uninstall & repair options.
The .NET runtime environment cannot be uninstalled in this way.
c. Via the Windows Installer
The individual components can also be uninstalled using the Windows Installer command: msiexec /x 'productcode'
The 'productcode' can be found via the WMI (Windows Management Instrumentation) or via the registry.
d. Via the command line
The executable .exe file supports the following command line options.
| Command line option/argument | Description |
|
-uninstall |
Completely removes ETS. |
|
-repair |
Repairs the ETS installation. |
The following exit codes codes have been defined:
| Exit code | Description |
| 0 | ETS uninstall/repair was successful. |
| 3010 | ETS uninstall/repair was successful, a computer restart is required. |
| 1641 | ETS uninstall/repair was successful, a computer restart is initiated. |
| Other | ETS uninstall/repair was not successful, a standard Windows error code is indicated. |