2023年11月29日发(作者：)

CitectSCADA Version 6.00 r1 Service Pack A

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 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.

Service Pack Installation

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.

Updated Files

The following files have been updated by this Service Pack.

Issues Resolved in This Service Pack

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

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("", 2), incorrectly returns an empty string.

(NB: 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("", 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

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 format in Graphics Builder is slow

AfAfter upgrading to CitectSCADA v6.00r1 from a previous version, Graphics Builder may appear unresponsive or

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

''. 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.