Download

Tools

eScada development and run-time packages

Current version: v25.10.1 - September 2026

The development suite is free of charge; you will pay only for the run-time licence.
See the release notes for the list of changes.
Previous versions are available on GitHub: eScada releases.

By downloading and using eScada you accept the terms of the licence agreement: eula.pdf

Package Architecture Download
eScada for Windows x64 x64 eScada-msw_25-10-1.zip
eScada for Windows ARM64 ARM64 eScada-mswarm_25-10-1.zip

Windows users general information:

  • desktop versions (64 bit): from Windows 10 to Windows 11
  • server versions (64 bit): from Windows 2016 to Windows 2022
  • embedded versions (64 bit): Windows 10 and Windows 11 IoT Enterprise
  • Windows on ARM
  • earlier versions also run from Windows 7 and Windows Server 2008 R2

(previous versions are not published on this page and must be explicitly requested through the support channel)

Dependencies Architecture Download
Microsoft Edge WebView2 Runtime x64 WebView2RuntimeInstallerX64
Microsoft Edge WebView2 Runtime ARM64 WebView2RuntimeInstallerARM64

Note: in the current version, the eScada tools for Windows require the Microsoft Edge WebView2 Runtime only when your HMI pages use the integrated HTML 5.0 browser. Since the runtime is not preinstalled on some Windows versions, we recommend running the installer for your architecture from the Dependencies table above anyway: it is the quickest check, as it either reports that the runtime is already present or installs it.

Package Architecture Download
eScada for Linux x64 x64 eScada-lnx64_25-10-1.tar.gz
eScada for Linux ARM32 ARM32 eScada-arm32_25-10-1.tar.gz
eScada for Linux ARM64 ARM64 eScada-arm64_25-10-1.tar.gz

Linux x64 users general information:

  • the executable property must be set for all executable files provided.
  • supported distributions (64 bit): mint, ubuntu, debian
  • x64 glibc version 2.27 or above, GTK 3

Linux ARM users general information:

These are example utilities only, provided to help with the final deployment of an HMI solution. They are free of charge and free to use in your own installations, but being examples they will certainly need to be adapted to the model of your own solution.

Note: the examples assume the folder layout suggested in the eScada.Development.Start document, with a single working folder named "workspace" holding the eScada binaries, the projects and the exchange folders. Adopting the same layout makes the scripts usable with minimal changes to their parameters.

Microsoft Windows

  • hmimswcfg Single PowerShell script that prepares a Windows 10 or 11 PC as an HMI station, entirely from the command line and without touching the Windows control panels. It sets the PC name, workgroup and time, keeps the PC always on with automatic updates disabled, removes notifications, sounds, lock screen and other disturbances, locks down Windows keys, gestures and touch keyboard, enables Remote Desktop, FTP and the firewall rules for the industrial protocols, and configures automatic logon with the HMI started at logon. Every step is proposed as a question and can be run in test mode first. Includes the language files and the user manual in five languages.
  • escada-startup-msw Example of automatic eScada startup on Windows, made of two files. escada.vbs launches escada.cmd with a hidden window, so nothing appears on the screen; the batch waits an optional delay, creates the public exchange folder if missing, moves the files dropped there by the maintenance staff (project, recipes, user and binary files) into the project tree, and finally starts the eScada server. The batch ends with two start variants, chosen by commenting one out: the start after the user log-on, where the batch launches the server and exits at once, and the start as a Windows service, where the batch waits for the server so that the service manager can monitor and stop it. The parameters to adapt (project name, working folder, paths) are grouped at the top of the batch.
  • escada-service-msw Example of running eScada as a Windows service, so that the server starts with the PC before any user logs on. The service is created with NSSM, included in the archive: escada-service-install.cmd installs it, sets its description and the log-on account. The service program is the escada.cmd of the escada-startup-msw example with its service start variant enabled, never escada.vbs, which exits at once and would make the service restart in a loop. A one page note lists the commands needed afterwards: start, stop and query the service, change the executable path or the log-on account, uninstall it and view it from a remote PC.
  • taskbar-msw TaskBar Hider v1.3, a small third-party freeware by IT Samples that hides and shows the Windows taskbar, either with a hotkey or from the command line: see its readme.txt for the usage. Its intended use is from the escada.cmd script of the escada-startup-msw example, which already contains a commented-out section that calls it: uncomment that section, after copying the program to the path it expects, to hide the taskbar before the HMI starts. Distributed as is with its readme and licence: it may be redistributed only in its entirety and must not be modified.

Test certificates for the OPC UA server component: opcua.zip

The archive contains eScada.OPCUA.STDSEC_cert.der/.pem and eScada.OPCUA.STDSEC_key.der/.pem, provided in both DER and PEM formats for your convenience, but only one format can be used at a time.

Warning: these certificates are provided for test purposes only and do not include specific details such as your own DNS names or IP addresses. Generate your own certificates for production use.