The CitectSCADA Runtime Manager interface is described below.
Each individual process on the workstation is represented by a line item in the monitoring pane. Every line item (process) has several columns showing the following information:
Column | Description |
---|---|
CPU |
The CPU on which the process is running. |
ProcessID |
The Windows ProcessID. |
Process |
Lists each CitectSCADA component running in the process. Where CitectSCADA is running in single process mode and all components are sharing a process, they appear comma-separated on a single line in this column. |
Type |
The Type of process (Alarm, Report, Trend, I/O Server or Client). Where CitectSCADA is running in single process mode and all components are sharing a process, the type is known as `MIXED'. |
Status |
The status of each process. See Monitoring Runtime Processes for a list of each status reported by CitectSCADA Runtime Manager. |
Message |
Displays message information relevant to the status of each process, such as the date and time of project compilation, as well as project name. For example, during startup of each process the verbose startup message appears in this column. |
The CitectSCADA Runtime Manager interface also includes the following buttons:
Once a CitectSCADA process is running, this button becomes Shutdown All, which shuts down CitectSCADA Runtime Manager. (For details see Shutting Down CitectSCADA Runtime Manager).
Note: It is recommended that the ServerGetProperty cicode function be used with the LibRDBMemTime and LibRDBDiskTime properties to check if there is a change to the Cicode library before attempting a reload. Following a reload please check the corresponding server's syslog.dat file for any reload messages. The cicode changes will not be reloaded, therefore a restart may be more appropriate.
|
UNINTENDED EQUIPMENT OPERATION Restart the server process if a "Cicode library timestamp differs" error is detected. The library mismatch is indicated on the server in either the hardware alarm or the server's syslog.dat file. Failure to follow these instructions can result in death, serious injury, or equipment damage. |
Note: A message in the Syslog.dat file and hardware alarm of "Cicode library timestamp differs" (error code 454) will be raised if the Cicode library used by one or more server runtime databases is different from the one in memory. The timestamps will be different if the project has been fully recompiled (with or without Cicode modification), or if the project has been incrementally recompiled after any Cicode has been modified.
After clicking "Reload", the "Status" column will change to indicate that a reload is in progress. Once the reload completes (successfully or otherwise), the "Message" column describes the result of the operation:
Message | Description |
---|---|
Reload could not start because another reload was being commenced. |
|
The last reload was completed at {0}, on {1}. |
{0} represents the time of the day, and {1} represents the date. |
Reload could not start because the requested components in this process are disabled. |
All components in the selected process are disabled due to licence restrictions or using citect.ini (for example, [Trend]Disable is set to 1). |
Server reload failed. Please check Citect syslog for more information. |
|
Unknown error: {0} |
{0} represents the unknown error code returned from Citect system when reloading RDB files. |