Q5110 CitectSCADA Version 6.00 r1 Service Pack A

ArticleID: Q5110
Created: 2/10/2008
Last Updated: 2/10/2008

This document describes the modifications and fixes made in CitectSCADA version 6.00 Service Pack A as well as providing installation information.

Important: All projects must be upgraded and recompiled after installing this Service Pack. Failure to do so will result in conflicting database size messages. To force an upgrade, edit the Citect.ini file and set [CTEDIT] UPGRADE=1. Ensure that the Incremental Compile menu option is not checked, or set [CTEDIT] INCREMENTALCOMPILE=0.

Note: If you already have hot fixes installed on v6.00 r1, you should review this document carefully to ensure that the hot fixes, you have installed, are included in this Service Pack. In the event of a discrepancy contact your regional support office for assistance.

Note: For general information about service packs, see Knowledge Base article Q2181.

The procedure for installing Service Pack A depends on whether you are an existing user of CitectSCADA 6.0 or a new user.

Existing CitectSCADA v6.00R1 Users

1. Install v6.00 Service Pack A.
2. Open Citect Explorer, wait until upgrade has completed, and then close Explorer.

New CitectSCADA v6.00 Users

1. Install CitectSCADA v6.00R1.
2. Open Citect Explorer for the first time and then close.
3. Install v6.00 Service Pack A.
4. Open Citect Explorer, wait until the upgrade has completed, and then close Explorer.

Web Client/Server Users

1. Perform installation as per one of the two scenarios above
2. In the CitectSCADAWeb Deployment Configuration
   1. Select the CitectSCADAWebClient_6_0_227.cab from the Client Control drop down menu.
   2. Save the deployment by selecting the action to save deployment.
3. On any machine that is currently using web client, delete the %windir%\system32\citect\webclient\600 directory. NB: %windir% indicates the default windows installation directory.

The following files have been updated by this Service Pack.

ctVersion.xml

Citect32.exe

CtDraw32.exe

CtCmp32.exe

CiTrendArchiveFileOffset.dll

CiTrendArchiveFileOffset8Byte.dll

CSV_MultiMonitors.ci

CSV_WinUtl.ci

CSV_navigation.ci

CtOpc32.dll

CtOpc32.exe

Ciusafe.exe

ctdraw32.tlb

rscite32.exe

analyst.dll

CitectSCADAWebClient_6_0_227.cab

This Service Pack resolves the issues described below.

20689 Error on inserting an ActiveX control onto a graphics page.

When trying to insert an ActiveX object onto a Citect Graphics Builder page, the client receives the error:

"Runtime Error 380", "Invalid Property Value".

20874 The CicodeCallOpen() function does not return when called from an ActiveX event handler.

If you use the CicodeCallOpen() function in CitectSCADA VBA functions that are called by ActiveX events, the function/event will only work the first time it is used. The problem is that the function that you call from the event does not finish which can be seen from the kernel page, "Page Table Cicode".

21239 The CitectSCADA runtime cannot be cleanly shutdown when Windows is directly shutdown

When Windows receives a user shutdown request and CitectSCADA runtime is still running, the CitectSCADA runtime process cannot be cleanly shutdown. The only available CitectSCADA ini parameters are:

[Kernel] WinShutdown:

WinShutdown=0 Does not allow windows to shutdown
WinShutdown=1 Kills the CitectSCADA process before shutting Windows

The following values are required to allow a clean runtime shutdown

[Kernel] WinShutdown:

WinShutdown=2 ! Perform Windows reboot by default
WinShutdown=3 ! Perform Windows shutdown by default
WinShutdown=4 ! Shutdown CitectSCADA but do not let Windows shutdown

22316 Alarm description changes are not reflected at runtime after changing them in the Project Editor.

When making a change to an alarm description via project editor, the runtime displays the original description if that alarm was in the active state the last time runtime was shutdown. Even if the alarm state has been cleared (off, acknowledged) and re-triggered during runtime, the new description will not be displayed until the alarm state is off and acknowledged and runtime is restarted.

22701 A runtime crash may occur during the persistence of the IOServer cache

CitectSCADA will sometimes crash while saving the cached IOServer data to disk. This is often indicated by the message:

I/O Device Unit Cache File -- Ve [rsion]

in the debug.log file.

23290 Corrupted I/O server persistence cache may cause CitectSCADA to crash.

When the CitectSCADA I/O server loads saved cache files at start up, it does not verify the saved cache to avoid loading corrupted data. If the data has been corrupted this may cause the runtime to crash.

24911 Multi-state symbol configurations disappear when scrolling through them.

When you try to scroll across symbols to the right of the default view, they disappear, reappear when you click on them, and jump unexpectedly to a different combo location.

24998 Projects built on the CSV style templates, may receive "foreground cicode running too long" hardware alarms if running on a slow network

If you are using the CSV include project templates, you may get hardware alarms stating "foreground Cicode running too long". This is most noticeable on slower networks. Symptoms are navigation buttons on graphics pages fail to work, or having incorrect status. In addition, if using the Citect FTP server with a CitectSCADA Internet Display Client, the server may run out of sessions and hang. This will also cause the client to hang.

25424 ServerInfo cannot get the CitectSCADA computer name for redundant trend or report server client connections.

Using the Cicode function ServerInfo("<conn_number>", 2), incorrectly returns an empty string.

(NB: <conn_number> refers to a redundant server connection ID. This is the server side ID of a redundant server connection)

25425 ServerInfo() returns a client login name even though client has logged out.

ServerInfo("<ClientNo>", 1) will return the last logged in username even after the user has logged out.

25822 CitectSCADA may crash on shutdown

A memory corruption may occur if a project has multiple channels defined that are not used. This may cause a subsequent crash on shutdown.

25932 CitectSCADA may crash on hyper threaded or multi-processor systems

CitectSCADA is required to run on a single CPU but does not automatically get locked to run on a single processor in a multi-processor system.

A new INI file parameter [General]LockToProcessor=x (where x is the processor number starting and defaulting at 1) is required that allows locking the CitectSCADA process affinity to an individual processor. By default CitectSCADA should bind to the first processor or an alternate processor if specified by [General]LockToProcessor. The affinity settings should be visible in the general statistics kernel window.

NB: From version 6.1 CitectSCADA will provide multi processor support.

25957 CitectSCADA may display incorrect values on startup if using the Citect OPC client

On Startup of the Citect OPC Client most values display "0.00" or "OFF" and only sometimes variables display the correct value. Once the tag value has changed (on either side) communications work perfectly for that tag from then on.

26228 CitectSCADA fails to locate "include" projects stored below the main project folder on a fileserver

If you have a project directory hierarchy that has your include projects below your main project then attempting to run the main project from a fileserver will result in a failure to locate any of the files in the included projects.

26311 CitectSCADA Process Analyst retains trend scales in saved views.

When a Process Analyst view is persisted to a “pav” file and subsequently restored, the trend scales used at the time of the save are also restored overwriting changes made after the save.

Upgrade Note: To update existing views, select a pen and click the 'Edit Vertical Scale' button. Select 'Engineering scale', click OK, and resave the view.

26431 CIUSafe cannot handle authorisation codes with more than 256 characters

CIUSafe can only handle authorisation codes with less than 257 characters. This means that an authorisation code that includes both CitectSCADA and CitectP2B (which results in a string longer than 256) can not be programmed into a key.

26469 Graphics Builder may crash when saving a page

Occasionally, after making changes to a page, Citect Graphics Builder will crash while conducting a "Save" or "Save As" operation.

27097 The performance of CtAPI function calls has diminished significantly.

Simple CtAPI function calls may take up to 15 times longer compared to previous CitectSCADA versions.

27127 Modems in a dial up pool may become permanently unusable

If you have more than one modem configuration, different data rate or frame, and all of one configuration type have connection failures, (busy, no answer etc.) then they never become available until all modems of all configuration types have had connection failures.

27133 After disconnecting, remote dialup I/O goes #COM

When CitectSCADA disconnects from a remote device, the tags representing that PLC will display #com.

27300 The display of numeric objects with the <default> format in Graphics Builder is slow

AfAfter upgrading to CitectSCADA v6.00r1 from a previous version, Graphics Builder may appear unresponsive or slow to update the screen when editing some pages. In particular, pages containing numeric objects with '<default>' as the display format will exhibit the problem.

27303 Using the CSV_Include project may cause a "Foreground cicode run too long" hardware alarm.

For projects based on the CSV_Include templates, a timing issue when using the [Page]Startup and [MultiMonitors]StartupPage1 parameters (e.g. to perform a splash screen) may result in a hardware alarm.

27410 The close button 'X' is disabled for popup windows in the Web Client

All Web Client child windows have the 'X' (close) button disabled, regardless of the value for the [Debug]Shutdown INI parameter. The close button should be enabled for all child windows on the Web Client.

27436 Client fails to connect to primary I/O Device

Sometimes a client fails to connect to the primary I/O Device even though it is talking to the I/O Server and the I/O Server reports the I/O Device as running. This affects tag-based drivers like OPC and ABCLX.

27595 Disabled alarms are not displayed as dotted lines in the Process Analyst.

A solid pen line is displayed in the Process Analyst for alarms that are disabled. A dotted line should be displayed whenever an alarm is disabled.

27686 Time Stamped Alarm DESC field may display incorrect results

Time Stamped Alarm DESC field displays static text when configured to display the result of a Cicode function or a variable tag.

27689 The "ON Action" in alarm categories does not work for "Time Stamped" alarms

The "ON Action" in alarm Categories no longer works in CitectSCADA v6.0r1 but worked on prior versions.

27721 CitectSCADA has slow response and trend data may fail to be written to disk

When the Trend system attempts to rollover the files of a trend that has a sample period which does not divide evenly into its file period, it causes slow response times for CitectSCADA and stops any trend data from being written to disk.

27906 A project with remapped variable tags causes a compile error.

If you use remapped variable tags in your project, it causes the compile error 'Cannot open file' with a context of 'Remap.DBF'. This compile error does not indicate any problem with the project configuration, and was not present in previous versions.

28180 Graphics Builder automation functions are incompatible with Microsoft Visual Basic 6

The Citect Graphics Builder automation interface methods introduced in version 6.0 for true color used unsigned variable types to represent colors. Unsigned variables are incompatible and therefore unusable by Visual Basic 6.

28434 Display anomalies can occur during trend redundancy backfill.

Sometimes, during redundancy backfill, a trend will display incorrectly. Recent data collected for a trend may be missing from the trend display until backfilling completes.

28435 Trend redundancy backfilling may cause high CPU Usage.

Trend redundancy backfilling is significantly more CPU intensive than in previous versions of CitectSCADA. This is particularly evident on large projects with many fast trends.

28916 The Login and Logout Cicode functions cause pages to be re-opened

The Login and Logout Cicode functions cause pages to be re-opened. This re-sets the page display count, re-sets page strings/ints, runs the On Page Exit command and then the On Page Entry command.

28918 Time Stamped Alarm DESC field may display incorrect results

The "Time Stamped Alarm" DESC field only returns the first two characters when configured to display the result of a Cicode function where the parameter and return value are a string.

29089 Trend Redundancy Backfilling can take a long time to complete

Trend redundancy backfilling for large projects can take much longer to complete than in previous versions of CitectSCADA.