Issue
The processes associated with PowerSCADA Expert.
Product Line
PowerSCADA Operations, PSO
PowerSCADA Expert, PSE
PowerLogic SCADA, PLS
Environment
Runtime Manager
Task Manager
Cause
In cases that a project does not start or shut down properly, it is advised to check the processes. In the case the project did not shut down properly, the process can be killed manually using Windows Task Manager. This way upon a restart of Runtime Manager, the project starts without any problem.
As such it is important to know the associated processes.
Resolution
The example below shows a project with six I/O Servers (numbered 2, 4, 6, 8, 10 and 12), a Trend Server, one Alarm Server and a Client (represents the main project); a total of 9 processes as shown in Runtime Manager.
NOTE: While the screenshot below applies to older version of SCADA, the same analogy applies to newer versions.
The processes above can be verified in Windows Task Manager as shown below. There is an entry for each of the above 9 processes, each labeled Citect32.exe *32. Note the one-to-one correspondence among the Process IDs in Task Manager and Process IDs in Runtime Manager. For example PID 22716 in Task Manager corresponds to IOServer6 as show in the above picture.
NOTE: The last three processes in the above screenshot applies to PSE 8.1 and older; more explanation below.
In case SCADA application is open for editing a project, there will be additional processes. Process names and their corresponding application are shown below. Depending on the version, different applications open.
1. SCADA version 8.1 and older:
CtDraw32.exe *32 Citect Graphics Builder
CtEdit32.exe *32 Citect Project Editor
CtExplor.exe *32 Citect Explorer
2. SCADA version 8.2:
PowerSCADA Studio (32 bit) PowerSCADA Studio
Example of a PowerSCADA 8.2 project with 5 process and PowerSCADA Studio open for editing:
1. Runtime Manager:
2. Task Manager (Details tab):
