1. EOS SCADA Program Folder Structure

Directly below the SCADA program folder are EXE files used to run the software, DLL libraries, the license file, general configuration files, and folders serving different purposes.

Folder / Component Primary Function
EXE files Program files that run EOS SCADA applications.
DLL libraries Runtime libraries required by the software for different functions.
License file Software licensing information.
General configuration files General operating and configuration information for the software.
DATAFILE User control template libraries.
GROUPS User control group libraries.
HTML Content containing HTML-based information such as maps.
IMAGES Image files.
IMGLIB Image library files.
LANGUAGES Language library files.
LOGS Log records generated by the software.
PROJECTS Main folder containing SCADA projects, with a separate folder structure for each project.
ROOT Root directory for the program's web server.
runtimes Libraries required by the embedded HTML Client.
SES Sound files.
tr Turkish DLL for the graphics library.
win32 Folder containing Firebird database tools.

Important distinction: The program folder and the project folder are not the same thing. The program folder contains the general EOS SCADA runtime infrastructure, while the PROJECTS folder is the primary project area where project-specific files and folders are stored.

2. PROJECTS Folder and Project Structure

The PROJECTS folder located under the EOS SCADA program folder is the main file-system directory for SCADA projects. Under PROJECTS, a separate folder named after each project is created.

PROJECTS
↓
BORCKA
↓
Project designs + images + scripts + TAG files + other project information

For example, if the project name is BORCKA, its project folder is: [EOS SCADA PROGRAM FOLDER]\PROJECTS\BORCKA\

This folder keeps many supporting items required by the project together within the file system. Therefore, copying only the project database may not be sufficient to transfer all files associated with the project.

3. Structure Under the Project Folder

Each project folder under PROJECTS contains subfolders that organize information belonging to different aspects of the project.

Subfolder Information Contained
BACKUP Information related to project backups.
DESIGNS Information related to project screen designs.
DIAGDATA DIAGNOSTICS data downloaded from the controller.
GROUPS Information related to user control groups within the project.
ICONS Icon information used within the project.
IMAGES Image files belonging to the project.
NOTES Operator note archives.
NSHAPE Screen background designs.
RECIPES SCADA Recipe definitions.
SCRIPTS Python, Visual Basic, and Visual C# scripts used in SCADA.
SLIDESHOW Images used by the Slideshow user control.
TAGS Files related to data definitions.

4. Project Database and Project Folder

The file-system structure of an EOS SCADA project requires the project database and the project folder under PROJECTS with the project name to be considered together.

Example for the BORCKA project:

[DATABASE FOLDER]\BORCKA.FDB

[EOS SCADA PROGRAM FOLDER]\PROJECTS\BORCKA\

Here, BORCKA.FDB represents the project database, while PROJECTS\BORCKA represents the project folder containing files, images, designs, and other supporting information associated with the project.

Attention: An EOS SCADA project should not be considered to consist of only a single .FDB file. For a project to be transferred correctly, the project database and the project folder bearing the project name must be handled together.

5. Transferring Project Information Between Computers

When a user wants to manually transfer a project from one computer to another, the basic transfer operation is to move both the project database file and the corresponding project folder under PROJECTS to the new computer.

  1. Identify the project name. For example, BORCKA.
  2. Locate the project database. For example, [DATABASE FOLDER]\BORCKA.FDB.
  3. Locate the project folder. [EOS SCADA PROGRAM FOLDER]\PROJECTS\BORCKA\.
  4. Back up both components. It is recommended to create an additional backup of the existing project before starting the transfer.
  5. Prepare the appropriate EOS SCADA runtime environment on the new computer. The required software, dependent DLLs, Windows/.NET Framework, and Firebird environment must be ready.
  6. Move the database to the appropriate location. The project database should be transferred to the location where it will be used on the new system.
  7. Move the project folder to the appropriate location under PROJECTS. The folder structure created with the project name must be preserved.
  8. Check the project with EOS SCADA Editor. After opening the project, verify screens, images, TAGs, scripts, and other project components.

6. Points to Consider During Transfer

  • The relationship between the project folder name and the project database name must be preserved.
  • The structure under PROJECTS\[PROJECT NAME] should not be changed unless necessary.
  • Project images and screen designs must not be omitted during the transfer.
  • The Python, Visual Basic, and Visual C# scripts located in the SCRIPTS folder must be preserved when transferring the project.
  • TAGS, RECIPES, NOTES, and other project folders should be transferred together according to project requirements.
  • Compatibility between the EOS SCADA version used on the new computer and the project structure must be checked.
  • The project on the existing computer should always be backed up before the transfer.

Important: When transferring a project, it is safer to preserve the integrity of the entire project folder rather than copying only the images visible on screen or a few individual files. Designs, scripts, TAG files, and other supporting project data should be carefully checked.

7. Separating the Program Folder from the Project Folder

One of the most important concepts in EOS SCADA troubleshooting and manual transfer operations is separating program files from project files.

Area Main Content Example
SCADA Program Folder EXE, DLL, license, general settings, and shared software resources. SCADA\
PROJECTS Main folder for projects. SCADA\PROJECTS\
Project Folder Designs, images, scripts, TAGs, and other information belonging to a specific project. SCADA\PROJECTS\BORCKA\
Project Database Database file associated with the project. [DATABASE FOLDER]\BORCKA.FDB

8. Conclusion and Summary

The EOS SCADA folder structure is designed to store the software's different functions and project information in an organized manner. Shared libraries and resources in the program folder and project-specific files under PROJECTS serve different purposes.

SCADA PROGRAM FOLDER
↓
PROJECTS
↓
BORCKA
↓
DESIGNS • IMAGES • SCRIPTS • TAGS • RECIPES • NOTES • ...

+

BORCKA.FDB
↓
EOS SCADA PROJECT

This structure keeps project information within a defined folder organization. When manually transferring a project to another computer, the basic requirement is to transfer the project database file together with the PROJECTS folder bearing the project name. After the transfer, the EOS SCADA runtime environment and required dependencies on the new computer must also be prepared appropriately.

← Back to Previous Content