EOS SCADA Dependencies and Runtime Environment

EOS SCADA • EVENT RECORDER • DLL LIBRARIES • WINDOWS • .NET FRAMEWORK • FIREBIRD

EOS SCADA and Event Recorder software perform a wide range of functions, including communication with field devices through different protocols, data reading and writing, database recording, alarm and event management, graphics, analysis, and various visual and audio presentations.

To provide such a broad set of functions, the applications require various software libraries (DLLs) and runtime environment components. Although these libraries are supplied with the software packages, older dependencies installed on the computer may become incompatible with the current software after new versions or additional features are introduced.

For this reason, the EOS SCADA Software Center provides dependency library packages prepared for different versions. It is important to use the package corresponding to the EOS SCADA version in use.

Library Packages

EOS SCADA dependency DLL libraries and runtime environment

1. Why Are Dependency Libraries Required?

Modern SCADA and Event Recorder software brings together many different technologies within the same system. Therefore, in addition to the main application files, it also uses numerous supporting software components.

Reading data from devices through different communication protocols.
Writing data to devices and sending control commands.
Recording data and events in different types of databases.
Creating and processing alarms and events.
Presenting real-time data as graphs, gauges, and tables.
Running visual and audio alarm/notification functions.
Performing trending, analysis, and reporting operations.

Each of these functions may require different software components. Therefore, for EOS SCADA to operate reliably, the application files and dependency libraries must be available in compatible versions.

2. Dependency DLL Libraries

EOS SCADA packages include various DLL (Dynamic Link Library) files required by the software. These files contain some of the components necessary for communication, database, graphics, analysis, and other application functions.

Important: It is not recommended to copy DLL files from random internet sources or from a package belonging to a different EOS SCADA version. Version compatibility between dependencies should be maintained, and whenever possible, the package corresponding to the relevant EOS SCADA version should be used.

Especially after a software update, some dependency libraries may remain at an older version even though the main application files have been updated. This may prevent the application from starting or cause errors only in specific functions.

3. Version-Specific Dependency Library Packages

The EOS SCADA Software Center provides different dependency library packages for different versions. The package corresponding to the EOS SCADA version in use should be selected.

Package	Applicable Version	Description	Download
VERSION 2026 Dependency Libraries	EOS SCADA 2026	DLL libraries required for proper software operation.	Download
VERSION 2024 Dependency Libraries	EOS SCADA 2024	DLL libraries required for proper software operation.	Download
VERSION 2023 Dependency Libraries	EOS SCADA 2023	DLL libraries required for proper software operation.	Download

Version compatibility: Do not apply the DLL package prepared for 2026 to an older EOS SCADA version, or an older-version package to a newer version arbitrarily. Use the package that matches the EOS SCADA version you are using.

4. After Software Updates

When upgrading to a new EOS SCADA version, updating only the main application files may not be sufficient. Dependencies that have changed or been added with new features must also be up to date.

Verify the EOS SCADA version in use.
Check that the dependency DLL package for the relevant version is available.
If necessary, download the relevant DLL package from the Software Center.
Update the dependencies using the appropriate package.
Check the Windows and .NET Framework runtime environment.
Check that the Firebird database version is compatible with the EOS SCADA version in use.
Restart and test the Editor, Runtime, and Event Recorder components.

5. Windows and .NET Framework Runtime Environment

Keeping the DLL libraries up to date is not sufficient by itself. The computer must also have the Windows runtime environment and the relevant .NET Framework components required by EOS SCADA and Event Recorder.

WINDOWS + .NET FRAMEWORK + EOS SCADA DLLs + FIREBIRD
↓
EOS SCADA / EVENT RECORDER RUNTIME ENVIRONMENT

A missing runtime environment component may prevent the application from starting or certain features from being used, even when the DLL files are present on the computer.

6. Firebird Database Dependency

Because EOS SCADA uses a database infrastructure to store project and system information, the relevant Firebird version must be installed.

Important: Using a different database technology for archive data does not eliminate the need for the Firebird installation required by EOS SCADA's own project and runtime infrastructure. The Firebird version required by the EOS SCADA version in use must be installed separately.

The Firebird version should be evaluated according to the EOS SCADA version. Therefore, during installation and updating, the documentation for the relevant version and the package information provided in the Software Center should be used as the basis.

7. Symptoms of Dependency Problems

A missing or incompatible component may not always appear directly as a “missing DLL” error. It may be useful to check the dependencies in the following situations:

The application does not start at all.
A DLL or runtime error occurs at startup.
A specific communication protocol does not work.
A database connection cannot be established.
Graphics, analysis, or visualization functions generate errors.
A feature that previously worked no longer works after an update.
Event Recorder or supporting modules cannot be started.

In such cases, instead of randomly replacing a single DLL, a better approach is to check the integrity of the application + DLL + Windows/.NET Framework + Firebird environment as a whole.

8. Recommended Check Sequence

Identify the EOS SCADA version. Check the versions of Editor, Runtime, and Event Recorder.
Check the Windows environment.
Check the .NET Framework environment.
Install Firebird. Use the Firebird package required by the version in use.
Install or update EOS SCADA.
Check the dependency DLL package. Download the correct version from the Software Center.
Test the applications. Verify that the Editor, Runtime, and Event Recorder functions operate correctly.

9. Conclusion

EOS SCADA and Event Recorder are comprehensive systems that bring together many different technologies and functions within the same software ecosystem. Therefore, their reliable operation depends not only on installing the main application files, but also on providing all runtime dependencies in the correct versions.

EOS SCADA / EVENT RECORDER
↓
DEPENDENCY DLL LIBRARIES
↓
WINDOWS + .NET FRAMEWORK
↓
FIREBIRD DATABASE
↓
RELIABLE RUNTIME ENVIRONMENT

Especially when troubleshooting problems encountered after software updates, the main application files should be checked together with the DLL dependencies, Windows/.NET Framework environment, and Firebird installation.

← Back to Previous Content