Free Software Download Center
Software for industrial data collection, monitoring, and analysis.
After installation, shortcuts for EOS SCADA Runtime are created both on the desktop and under the Application Shortcut Folder. The software can be started using one of these shortcuts.
During the first run, SCADA operations cannot be performed until the user logs in using a Password and/or USB Key. However, data collection and archiving functions configured according to the project settings start and continue in the background.
When a project is opened, the user is presented with an organized workspace that facilitates process monitoring and control operations.
| Area | Main Function |
|---|---|
| Main Menu | Provides access to basic Runtime and SCADA functions. |
| Quick Access Buttons | Provides quick access to frequently used operations. |
| Login / Logout Area | The section where user session operations are performed. |
| SCADA Workspace | The main area where SCADA screens and tool panels are displayed. |
| Status Bar | Displays software and system status information and messages. |
EOS SCADA Runtime uses a Multiple Document Interface window structure. Multiple child windows are managed within a single main window. SCADA screens can be hidden, displayed, minimized, or maximized. The use of common menus and toolbars helps make efficient use of the available screen area.
To perform operations in EOS SCADA Runtime, the user must first log in with an authorized user account. Menu and button elements are enabled according to the user's authorization level.
Runtime supports dual user login to facilitate operation in shift-based environments. Two different authorized personnel can be logged in simultaneously. The highest authorization level among these users is applied. When one of the users logs out, the other can continue monitoring and management activities without interruption.
The same steps can be performed for the second user by using the LOGIN (2nd USER) button.
Any USB flash drive can be configured as a user's authorization key using EOS SCADA Editor or Runtime. When an authorized drive is inserted, automatic login is performed according to the defined authorization level. Removing the drive automatically logs the user out.
A logged-in user can log out of the system by clicking the user name displayed in the upper-right corner of the screen and selecting LOG OUT from the menu that opens.
When logged in with a USB key, removing the flash drive also triggers automatic logout.
A logged-in user can select CHANGE PASSWORD from the menu that opens by clicking the user name in the upper-right corner.
After a successful update, the DB LED turns green. It appears red if an error occurs. The system uses a password security algorithm that does not accept weak passwords. The window can be closed using the CLOSE button.
To view the identification information of the logged-in plant operator, simply place the mouse pointer over the user icon next to the user name.
Since EOS SCADA Runtime is designed for process control, data collection, and archiving, it is expected to operate continuously, 24/7, under normal operating conditions.
After logging in, an authorized user can use the CLOSE button in the upper-right corner or select Program > EXIT PROGRAM. Unauthorized users cannot close the program through the normal menu paths.
When Runtime starts, the active project is automatically selected and the project configuration files are loaded. During normal operation, the user does not need to select a project separately.
An authorized user can close the current project from the PROGRAM menu or by using the CLOSE PROJECT button on the Quick Access Button Bar. The user can then select OPEN PROJECT to activate another project from among the loaded projects.
Project closing and activating a different project can only be performed by authorized users.
SCADA screens can be opened in two ways: through the SCREEN > OPEN SCREEN option under the Main Menu or by using the OPEN SCREEN button on the Quick Access Button Bar.
Each user can open screens within the scope of their authorization. The maximum number of screens that can be opened simultaneously for each screen is defined in the project settings.