Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

TABLE OF CONTENTS

Plant SCADA 2023 R2 Monthly Updates

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedFeb 10, 2026
  • 44 minute read

Monthly updates are available for Plant SCADA 2023 R2 (see Manage Updates).

The following monthly updates require a full installation of Plant SCADA 2023 R2. You can download the product installer from the Products page on the AVEVA Knowledge & Support Center.

Notes

  • Update 17 (or later)

    If you have not installed Update 17 (or later), then an update will perform an upgrade to the alarm system database version. Prior to applying this, project users should ensure they back up the data directory in addition to the normal practice of backing up the project.

  • Update 05

    There are key changes included since Update 05. This is to update components to use Microsoft .NET 8, as .NET 6 went out of support on 12 November 2024. This will be applied to all AVEVA components apart from Industrial Graphics, which will be dealt with in a future update.

    From Update 05, the size of the update will be significantly larger than earlier updates. This is because the updates now include Microsoft .NET 8 runtimes, as well as updated versions of several AVEVA common components. Details of the new versions of these components are contained in the release notes.

    Since Update 05, the format of an update has been changed. Previously, the zip file downloaded from this page contained a self extracting executable containing the update files. Now the zip contains the update files directly, but the process to install the update has not changed. After extracting the zip, run the exe "AVEVA Plant SCADA 2023 R2 Update <n>" and follow the on-screen instructions.

    Since Update 05, new versions of the CTAPI 32 bit and 64 bit redistributable packages accompany an update. These packages contain various Microsoft dependencies updated to .NET 8, and it is recommended you apply the new redistributables to your CTAPI applications.

  • Update 09

    Note: AVEVA Plant SCADA 2023 R2 Updates 05 to 08 contained an issue that prevented the 64-bit version of the alarm server dlls being updated. Updates 06 to 08 only contained very targeted edge case fixes for the 64-bit alarm server.

    This issue is resolved in Update 09, but in order to correctly update the files these updates must first be removed. This will be handled automatically when Update 09 or later is installed, but you may see some dialogs referring to earlier updates during the install process - this is expected.

    If Update 09 is removed for any reason, the system will be returned to the state of the latest of Update 01 to 04 that was installed (or the base release version if no such update was installed).

Note: Please ensure that the CTAPI redistributables (CtApi.x64.Redist and CtApi.Win32.Redist) are only applied to your CTAPI clients (if applicable). Do not copy them to the "AVEVA Plant SCADA\Bin" directory as this will prevent the Plant SCADA runtime from starting.

Update 18 (Feb 10, 2026)

Client

  • 4354994 - The tooltip on a second monitor moves to the incorrect location

    A tooltip for an object would display in the incorrect location on a second monitor in a dual monitor profile. The tooltip would display correctly on the main monitor. The tooltip will now display in the correct location relative to the object on any monitor.

Deployment

  • 4385455 - Deployment Client plugin displays incorrect warning state in Configurator

    Since Plant SCADA 2023 R2 Update 15, the Deployment Client plugin in Configurator would use the incorrect client ID to check if it was registered with its System Management Server. This would display a warning state in Configurator and stop the deployment client service. The Deployment Client Configurator plugin has now been corrected.

Equipment Editor

  • 3316976 - The Update Equipment operation removes non-automated fields

    When renaming an equipment name using the Equipment Editor, only a few of the equipment related tables would be updated. Other tables that had references to the equipment would remain with the old equipment name. This caused the Update Equipment operation to re-generate records for the referenced tables, causing any manually entered data in the fields to be lost. This has been addressed via changes to cascading updates in the Equipment Editor. It should be noted that applying renames via the Equipment Editor can take a long time depending upon the number of records impacted.

Licensing

  • 3804075 - A server process may shut down when two nodes have the same name and the kernel 'Tran' table does not show the connecting component

    If a remote client node was inadvertently configured with the same name as a server node, there was a possibility that the server process may be forced to shut down due to a Software Protection Failure. This will no longer occur. Diagnostics improvements were also made as part of this fix. A trace will now be provided on the server's syslog when two nodes are using the same name. Additionally, the kernel 'Tran' table now lists the component of the connecting tran, and the 'Service' column has been renamed to 'Peer'. It now lists the peer component on the other side of the respective tran connection for both client and server connection types.

Runtime

  • 4129539 - Calling TaskNew with mode 8 does not reject a new task when the same function is already running

    If a Cicode function with a name longer than 31 characters was already running, calling TaskNew with mode 8 for the same function would launch a new task and not maintain uniqueness as intended. From this update, regardless of the length of the function name, calling the same function again using TaskNew with mode 8 while it is already running will reject the call to maintain uniqueness.

  • 4424367 - I/O server cannot create a task due to standalone mode despite a redundant I/O server being declared

    If redundant I/O devices were configured with their I/O server names in a different case (capital vs non-capital letters) in the I/O server view, the I/O server runtime would raise a message at startup that the application could not create a task and runtime would stop. This issue has been addressed by allowing case insensitive configuration of server names.

Update 17 (Dec 09, 2025)

Alarm Server

  • 3467899 - Alarms may disappear from SOE and Alarm Summary when TLS 1.3 is enabled

    When Transport Layer Security (TLS) 1.3 is enabled in the operating system, the alarm server may lose its connection to the backend database in some circumstances. For example, if a user has been logged on for a long time, the SOE and Alarm Summary displays may go blank. Alarms should display correctly when TLS 1.3 is enabled.

Deployment

  • 3956599 - The Deployment Server Service takes a long time to start

    The Plant SCADA Deployment Server Service was taking over a minute to start. This was noticeable while configuring the deployment server in Configurator, which would show an error message indicating the service could not be started. However, when launched again, the Configurator would appear correctly configured reflecting the delayed startup. This was resolved by updating the SQLite component, which improved the startup time.

  • 4139254 - Improvements required for deployment operations logging

    Verbose mode of logging has been improved for deployment operations so information about underlying issues are more easily identified.

Graphics Builder

  • 4354771 - Graphics Builder's 'Recent Pages' menu behaves incorrectly when additional entries are added

    If the [CtDraw.Pages] section in the Citect.ini file is manually edited to add more than four parameters, the 'Recent Pages' entries in the File menu in Graphics Builder will behave incorrectly. Now only the first four parameters are read from the Citect.ini.

Runtime

  • 4119756 - Additional properties are added to CtAPI Alarm and related tables

    The properties MilliSec, AckDate, AckTime, AckMilli and UserName are now available in Alarm and other tables for specific types of alarm tags when making ctFindFirst or ctFindFirstEx CtAPI calls from external applications. For the AlarmSummary table, the MilliSec and AckMilli properties are also available.

  • 4347003 - The Cicode function UserEditForm tries to set an empty password on the server

    If a user tries to change a user password using the form launched by the Cicode function UserEditForm, it will unexpectedly try to empty the password of the specified user on the server computer via an MsgRPC call. In addition, if the old password specified is incorrect, it may cause the client to stop responding. The form will set new password correctly. If the old password is specified incorrectly, a dialog will pop up to alert the user and the client will continue to work as expected.

  • 4367062 - Mouse can move unexpectedly when opening pages if [AnmCursor]MouseSnapToCursor=1

    During page open, the initial focus cursor is set to the graphical element nearest the mouse cursor that has an input animation. In some cases, this may be some distance away if the area under the mouse is generated dynamically and is initially empty (for example, the page menu of an SxW project). This can cause the mouse to move unexpectedly when [AnmCursor]MouseSnapToCursor=1, so this setting is now ignored during page open. Subsequent movement of the cursor using the arrow keys will still cause the mouse to be moved to the new focused item as expected.

  • 3827013 - Kernel diagnostics are not correct for some fields on IO Device 'unit' page

    In the Kernel, the units from another I/O server now only show fields taken from the project configuration. Note that these 'peer' units are only displayed in verbose mode. To view all diagnostic unit fields for a 'peer' unit, switch to the Kernel on the corresponding I/O server. Additionally, the subscription statistics have been simplified down to just the subscription state and the number of active subscriptions.

General

  • 3871795 - Update to the alarm server database engine

    The alarm server database engine has been updated to the latest version.

  • 4280735 - Update to AVEVA components

    This update will upgrade AVEVA Enterprise Licensing (AEL) to version 4.2

  • 4305342 - Update to AVEVA components

    This update will upgrade Platform Common Services to 8.2.1.

Update 16 (Nov 11, 2025)

I/O Server

  • 4216153 - I/O server running in single process mode stops working

    In some circumstances, an I/O server running in single process mode would have an unhandled exception when it lost the connection to its redundant peer. This will no longer occur.

  • 4289086 - Stopping an I/O server during startup causes an unexpected shutdown

    In some circumstances, during an I/O server startup, stopping the I/O server from the Runtime Manager could cause the I/O server to stop working. This will no longer occur.

Licensing

  • 3412547 - Minor licensing issues updated

    Licensing scenarios have been reviewed and minor issues resolved as part of this update. It is recommended that users test their application with their license before deploying this update. Please contact support if you detect any issues.

Plant SCADA Studio

  • 4325596 - Plant SCADA Studio displays an error on startup on non-English installations

    On a non-English installation, Plant SCADA Studio will display an error message "Error (25) : String Type : NORMAL Missing" (or a similar localized version of that text). If the master.dbf file does not exist in the User folder, an additional message will also be displayed, "A severe error has occurred. Process will terminate". Apart from this, Plant SCADA Studio will continue to run but other issues will be encountered (for example, graphics cannot be opened, and Equipment Editor will stop working). This is caused by an invalid form definition file (citect.frm) in the Bin folder for non-English installations. The form definition file has been corrected, and these errors will no longer be displayed.

Runtime

  • 4286721 - Cursor jumps to the top-left of a window

    This occurred when the INI param [AnmCursor]MouseSnapToCursor was set to 1. When the mouse was moved over the display client window while it was inactive (i.e. when another application was the active window), then the mouse would jump to the top-left corner of the display client window when moved over certain graphics objects. [AnmCursor]MouseSnapToCursor now only takes effect when the display client window is active.

Third Party Components

  • 4150032 - Update to AVEVA components

    This update will improve the installation experience of Operations Control Logger (OCL) 23.4 where there is a Windows restart pending following an operating system update, or if some installer files are blocked by the operating system due to security or file property settings.

Update 15 (Oct 14, 2025)

Alarm Server

  • 3889486 - AlarmAck and AlarmClear Cicode functions are slow when used with large groups of categories

    The performance of the AlarmAck and AlarmClear Cicode functions when using modes 2 and 3 and passing a group handle as the value has been improved dramatically when the specified group has a large number of values. To enable this, upgrade all alarm servers and display clients to this update, then set the INI parameter [Alarm]UseINOperatorForGroupCommands to 1 on the display client machines and restart the display client process. You only need to set this if you use AlarmAck or AlarmClear in this manner and are experiencing performance issues. AlarmEnable and AlarmDisable functions are also affected by this parameter but with minimal performance impact. CAUTION: Do not set this parameter to 1 unless all alarm servers in your system have been upgraded to this update or later (including redundant servers). If you set this parameter and an AlarmAck, AlarmClear, AlarmEnable or AlarmDisable command is sent to an alarm server that does not have this update, then all alarms on that server will be impacted e.g. all alarms will be acknowledged regardless of whether they are in specified categories/priorities.

Deployment

  • 3959458 - Logging on to the deployment server is not successful with a domain user

    When logging on to the deployment server with a domain user that is a member of many user groups, a login error message would sometimes appear. This would occur when the string length of the groups that the user is a member of exceeds the size of the header in the user's token. This could be worked around by configuring a filter for the required security groups in the appsettings.json on the System Management Server (SMS). However, this workaround (mentioned in Knowledge Base Article number 000052142 on the AVEVA Knowledge and Support Center) is no longer required. IMPORTANT: To ensure deployment works with large numbers of user groups, the Deployment Server and all Deployment Clients must be upgraded and re-connected to the SMS within the Configurator (green tick) of each respective machine. Update and reconnect the Deployment Server first (including its own client if configured on same machine) to support backwards compatibility with deployment clients running on older versions or previous updates.

Install

  • 4110828 - The update installer cannot be run on an incorrect base version of Plant SCADA

    A user could previously run a monthly update on an incorrect base installation version of Plant SCADA. Following this fix, a monthly update can only be run on the correct base installation. Attempting to install over the incorrect base version will, in silent mode, return error code 1638, or in interactive mode it will display a message "<Update version> cannot be applied as a different version of AVEVA Plant SCADA is installed." Unfortunately, we are unable to determine if a machine with only common components was part of an 8.40 installation, so running the patch will still upgrade prerequisites in that case.

Plant SCADA Studio

  • 4289101 - Plant SCADA Studio occasionally stops working when creating a new project

    Plant SCADA Studio would occasionally stop working when a new project was created without using a starter project. This will no longer occur.

General

  • 4285059 - New parameter and procedure to uninstall and disable AVEVA Industrial Graphics

    For security reasons, the Plant SCADA version of Industrial Graphics is being deprecated. It is advised to cease using Industrial Graphics. The feature will not be supported in future versions and updates. To stop using AVEVA Industrial Graphics within Plant SCADA, you should perform the following procedure on any computer where Plant SCADA is installed:1) Determine if AVEVA Industrial Graphics Web Server is installed. 2) If detected, uninstall the Industrial Graphics Web Server. In both cases, disable remaining Industrial Graphics components by setting the [General]EnableIndustrialGraphics to 0 in the citect.ini for all engineering and runtime computers. It defaults to 1 to allow existing systems to continue running. This procedure is presented in more detail in the Knowledge Base article number 000103614 on the AVEVA Knowledge and Support Center.

  • 4293845 - Security updates and compliance

    Resolved multiple high-severity issues identified through static code analysis and refactored code to align with internal coding rulesets. These changes are extensive across most components and while no functional impact is expected, we strongly encourage thorough testing of your applications before deployment to ensure compatibility and stability in your environment.

Update 14 (Sept 09, 2025)

Alarm Server

  • 4083517 - Add additional diagnostics for [Alarm]UseConfigLimits

    On startup of the alarm server, additional diagnostics will be logged for the [Alarm]UseConfigLimits ini parameter.

Alarms

  • 3946105 - Client may be prevented from starting while showing Alarm Summary or SOE page

    In rare circumstances that involved modified Cicode, a client could not start correctly while displaying the Alarm Summary or SOE page. A client will now work as expected under these circumstances.

Runtime

  • 3613895 - Client connections to a server running many clusters may be delayed

    This situation could occur for projects with many clusters of servers configured on the same computer. If an active server were to shut down, it would take the clients a long time to reconnect to all the servers on the standby machine. The delay was partly contributed to by multiple server processes on the same machine all racing to get data from the secure data storage. The access to the secure data storage is now streamlined to reduce unnecessary delays.

  • 3887818 - Client process restarts when calling DspInfoField

    Calling the Cicode function DspInfoField with a tag name that ends with ']' character without a matching '[' character, or an empty string, may cause the Plant SCADA process to terminate. Argument checks for these problematic string values have been added to resolve this.

Third Party Components

  • 4101638 - Update to AVEVA Components

    This update will upgrade Operations Control Logger (OCL) to 23.4. Be aware that the installation of OCL 23.4 may not be successful if a Windows restart is pending following an operating system update, or if some installer files are blocked by the operating system due to security or file property settings. In both cases, restarting the system and running the installation again will resolve this.

General

  • 4054878 - Slow connection and browsing to OPC UA server when logging is enabled

    Operations Control Logger (OCL) v23.3 had a performance issue that effected the consuming applications' response times, such as an OPC UA connection and AEL license acquisition. When the trace log was enabled for Plant SCADA OPC UA, an OPC UA client would experience slow connection and response times from the OPC UA server due to more messages being processed by OCL. This could cause connection and operation timeouts. The update to OCL v23.4 has now resolved this.

Update 13 (Aug 12, 2025)

Alarm Server

  • 4003810 - Alarm server doesn't always update dynamic properties on restart when UseConfigLimits=1

    When using redundant alarm server servers with UseConfigLimits=1, changes made to the dynamic alarm properties in Plant SCADA Studio (limits, delays, paging, category, custom fields) would not be updated to runtime in the case where the alarm servers are restarted one by one. If both servers were stopped at the same time, or the server reload command was used, then the properties would be updated to runtime correctly. This is now fixed and the property values from Studio will be updated to runtime on restart of a single server, unless the properties have been changed at runtime AFTER the project was last compiled (e.g. via AlarmSetThresold function or a tag write to an alarm property tag).

    Note that only one server now needs to be restarted for the updated dynamic properties to be reflected on both servers, but it is recommended to still restart both servers as soon as possible (or use the server reload command) in order to pick up any other changes made in Plant SCADA Studio (e.g. new alarms added).

  • 3871889 - Alarm server occasionally stops working when logging on from a display client

    The alarm server would stop working when logging on from a display client with a user that does not yet exist on the alarm sever. The evidence of this was numerous "Auth: User Added, Failed, <username>, Remote, Invalid User..." messages logged in the syslog file of the alarm server. The situation could cause the alarm server to stop working with a NullReferenceException. The alarm server will now start as expected under these circumstances.

Cicode

  • 3955956 - The width of a tooltip does not change when the text changes

    The width of a tooltip box would not change when the text changed. If the text was updated with a longer string, the text would be truncated. Tooltips will now display correctly.

Compiler

  • 3885351 - A compiler error message is required when an event name contains a space and/or comma

    If an event was created using a name with a space or comma, the event would not be enabled and no error message was shown during compilation. A compile error message is now shown whenever an event name is created that contains a space or a comma

  • 3758443 - Compiler stops after reaching a 4GB memory limit

    When compiling a large project, the compiler could use a significant amount of memory when processing variable tags. The compiler has now been optimized to support reduced memory usage during certain phases of the compilation process, which prevents the compiler from reaching the 4GB memory limit of a 32 bit process.

CtAPI

  • 4069482 - Using ctGetLicenseInfoString to retrieve license information takes a long time

    The CtApi function ctGetLicenseInfoString was getting licence information by reinitializing the protection provider, checking out the licenses and then releasing them. This process was taking a lot of time. Now, it will get license information from a running client rather than initializing and checking out licenses via a protection provider.

Update 12 (Jul 15, 2025)

Compiler

  • 3924224 - A compiler error message is required if the array size of a local variable exceeds 32768

    When a local variable is created with a two-dimensional array size that is more than 32768, an unhandled exception is thrown at runtime. This has now been changed to show a compiler error when a project has a local array variable that is greater in size than 32768 for both one- and two-dimensional arrays. Additionally, the compiler will raise an error if the array size contains an alphanumeric value or if a two-dimensional array has zero defined as a dimension.

Deployment

  • 3632865 - Deployment is stopping with error "An internal error occurred while deploying a project version onto a remote node"

    During the deployment of large projects, if the deployment operation time period went beyond a user session timeout interval it would not be successful due to the user session becoming unauthorized. Now a deployment operation will remain active by refreshing the user session before its timeout.

Equipment Editor

  • 3825039 - Equipment update unsuccessful due to Equipment Type configuration parameters

    When editing the Equipment Type in Equipment Editor, the entry of the parameter default value is not validated while saving, which means the next Equipment Update may not be successful. This issue has been addressed and the parameter default value will now be validated when saving the Equipment Type.

General

  • 3947491 - Alarm server occasionally stops working when trying to send data ready message

    The alarm server may stop working when it tries to send a message to display clients with an invalid set of clusters. This issue has now been fixed and a log message has been added to tracelog to detect when this issue occurs. This can be enabled by adding severity "Information" to the [Debug]SeverityFilter INI parameter and making sure the category "AlarmServerComms" is not excluded by the [Debug]CategoryFilter INI settings.

  • 3882497 - Possible false fleeting "IO Device Offline" hardware alarm generated at start up

    When an I/O device was slow to come online at start up, it was possible to receive a false "IO Device Offline" hardware alarm even before the I/O device had reported its online status. This has now been corrected.

  • 3940378 - Update to AVEVA Components

    This update will upgrade Platform Common Services to 8.1.5, as well as upgrading Microsoft .NET 8 Runtimes to 8.0.17 if they are not already updated by Windows Update.

Update 11 (Jun 10, 2025)

Compiler

  • 3787006 - Port name checking required in Compiler

    Port name checking has been added to the Compiler. This will raise an error message if a duplicated combination of a server name and port name are detected in the Ports table, or if any undefined port names are detected in I/O Devices table. Note that this will cause a compiler error for an existing project if the compiler detects one of these scenarios after the update is applied.

Computer Setup Wizard

  • 3926321 - CPU Setup page in Setup Wizard shows empty CPU column for a process

    When modifying the CPUs for a Plant SCADA process in the Computer Setup Wizard, if the "All CPUs" option is selected then the list of processes is now updated to show "All" instead of empty in the CPU column. Note this was a cosmetic issue only, the correct value was always written to the INI file even when All CPUs was selected.

Runtime

  • 3453429 - High CPU usage observed on a report server when calling EquipGetProperty

    When calling the Cicode function EquipGetProperty using cache modes (i.e. mode 1 or 3), it returns the cache value immediately and at the same time will make a request to the report server to refresh the cache value. If the function is called repeatedly, such as via an animation on a graphic page, refresh requests will be sent to the report server continually. If many calls are configured, it can cause high CPU loading on the report server. This is evident with high CPU% observed on the "<ReportServerName><ClusterName>_proxy.KernelTaskQueue\sem" task in the Kernel Tasks page of the report server. The cache modes of the Cicode function are now modified to only refresh value when necessary. For non-runtime properties, refresh only occurs when the report server is reloaded or recovers from network disruption. For runtime properties, cache timeout (configurable via [Client]EquipCacheTimeout INI parameter with default value of 0 millisecond) is introduced. Value refresh is only sent to report server after the value is kept in cache beyond the timeout limit.

  • 3720592 - DspGetMouseOver can return an incorrect result when DspArrayByAn is called

    If an animation in a Genie that is displayed in an array list using DspArrayByAn contains a call to DspGetMouseOver, then DspGetMouseOver can briefly return an incorrect result while the array list is being updated (for example, when ArraySetIsDirty is called). This can result in unexpected animation behaviour and is most noticeable when the mouse is positioned over the first row in the array list. This will result in DspGetMouseOver briefly returning 1 for all rows in the list. DspGetMouseOver will now return the correct value during DspArrayByAn refresh.

Plant SCADA Studio

  • 3889502 - Grid view scrolling via PgUp and PgDn keys in Plant SCADA Studio does not work correctly

    When using the grid view in Plant SCADA Studio, pressing the Page Up and Page Down keys would scroll more than a page of records and skip some records. The calculation of the number of rows displayed in a table in Plant SCADA Studio has now been corrected.

Third Party Components

  • 3942024 - Microsoft Visual C++ redistributables require update

    Recent security updates have been applied to the Microsoft Visual C++ redistributables included with Plant SCADA.

General

  • 3821011 - Update to AVEVA Components

    This update will upgrade Operations Control Logger to 23.3.

Update 10 (May 13, 2025)

CtAPI

  • 3848213 - ctFindFirstEx requires support for 254 characters for cluster names

    When comma-separated multiple clusters were passed to the szCluster argument of ctFindFirstEx, it would only allow up to 30 characters. More than 30 characters would result in a 403 error message (cluster not found). This has now been changed to allow up to 254 characters in the szCluster argument for tables that used to only support 30 characters.

Graphics Builder

  • 3854102 - Cannot paste a bitmap from MS Paint into Graphics Builder on Windows 11

    On Windows 11, MS Paint and the Windows screen clipping tool copy images to the clipboard as 32-bit bitmaps (i.e. with alpha channel), unlike Windows 10 which copies 24-bit bitmaps. Graphics Builder did not support pasting 32-bit bitmaps properly, so pasting from Paint on Windows 11 would result in an image with all pixels 100% transparent. This is now fixed, and images can be copied from Paint and the screen clipping tool on Windows 11, as well as Paint.NET which always copied as 32-bit bitmaps on both OS versions.

Install

  • 3795033 - Service configuration is reset to default after installing an update

    When installing an update, any changes made to AVEVA Plant SCADA services (for example, Startup Type) would be reset to the default. With this update, any changes will now be preserved.

Licensing

  • 3818055 - AEL license provider takes too long to acquire licenses

    The AVEVA Enterprise Licensing (AEL) license provider has been improved to reduce the time required for license acquisitions.

Runtime

  • 3770003 - New Cicode function required to set focus to an ActiveX control on a page

    A new Cicode function "ObjectSetFocus" has been added to set keyboard focus to an ActiveX control on a page if it is supported by the control (for example, the CiTextBox control). The function takes the AN of the control. It returns 0 if successful, or an error code if the AN is invalid or not associated with an ActiveX control. Like other object functions, this function should not be called from an On Page Entry event as controls are not guaranteed to be initialized. Instead, use the On Page Shown event if required.

Runtime Manager

  • 3662718 - The Runtime Manager needs to display whether an alarm server is main or standby

    The Runtime Manager will now display whether an alarm server process is running as main (Alarm DB: Main) or standby (Alarm DB: Standby). The information will only be displayed when the alarm server is in a "Running" state.

Update 09 (Apr 15, 2025)

Compiler

  • 3652299 - Compiler stops working when incremental compile is enabled if equipment contains a space

    If an equipment name contained a space before or after the dot separating the parts of the full equipment name, this was normally ignored. However, if the Equipment field for an alarm contained such a space, this would stop an incremental compile. This would occur when there were no changes to the alarm database since the last good compile. The incremental compile will now work as expected under these circumstances.

Compiler/Runtime

  • 3307732 - The service display client gives a software protection failure notification when you run Plant SCADA as a service

    If a Plant SCADA user was configured with no password set, logging on to a display client with this user would cause the client to server login to be unsuccessful. When logging on with this user on a display client at startup, the client would not be able to connect to SystemServices to retrieve a license. This would result in a software protection failure notification. This has been addressed by allowing a user with no password to login from a display client to the servers for backwards compatibility. However, as good security practice, we recommend that all users defined in the project should have their passwords not set to empty.

Graphics Builder

  • 3580015 - Graphics Builder stops working after undoing text alignment change

    This issue would occur in Graphics Builder when a text object's alignment was changed using the properties dialog, then the dialog was closed. If the alignment was then undone via the Undo command, the next time the properties dialog for the object was displayed, Graphics Builder would stop working. The properties dialog will now display as expected under these circumstances.

Licensing

  • 3679813 - CtAPI licence count requires control by [CTAPI]MaxConnections in more scenarios

    When a user or control client license is requested from a remote node, additional CtAPI licenses have always been provided to the node. The number of CtAPI licenses provided is no longer fixed at 10 for users and 2 for control clients. It is instead now controlled by the [CTAPI]MaxConnections INI parameter on that node. Note that additional CtAPI licenses are never provided in response to a View Only Client license request. When Plant SCADA starts in traditional demo mode, the number of CtAPI licenses available is no longer fixed at 2. It is instead now also controlled by the [CTAPI]MaxConnections INI parameter. This change makes the allocation of CtAPI licenses consistent across all scenarios.

Update 08 (Mar 11, 2025)

Licensing

  • 3340914 - Plant SCADA is unable to acquire a license from AEL and runs in demo mode

    After restarting the operating system, Plant SCADA was unable to acquire a license from AVEVA Enterprise Licensing (AEL) and would run in demo mode instead. This would occur if Plant SCADA was configured to run as a Windows service. The license timeout or poll interval has been increased to allow AEL licenses to be acquired in time to prevent this scenario.

OPC DA Server

  • 3569803 - Loading the OPC DA Server with large memory usage

    The OPC DA Server has been made large address aware, which resolves some issues that have been observed when the server uses large amounts of memory.

Runtime

  • 2838121 - Display problem on client when swapping from standby I/O server to primary

    When the primary I/O server is starting up, it loads and initializes all of its connected I/O devices. For large projects, this process can have a heavy impact on system performance especially for Cicode devices. During this phase, the client tag subscriptions would switch from standby devices to primary devices as soon as the client was connected to the primary server. This behaviour would add even more load to the server, which could cause the display client to show invalid data on graphics pages during this period of time.

    To reduce the impact to the data displayed while the primary server is starting, a change has been introduced that delays the primary server from switching to an 'online' state. During this delay, the client remains connected to the standby server which means there is no need to switch to the primary server before it is ready to serve data. In addition to the delay switch, when the I/O server starts it will prepopulate all calculated variables so that any associated Cicode can be executed. This means projects such as Example_SA will pre-create the user maps as the server is starting up. This will reduce the load when the server needs to serve the client subscriptions, making runtime more stable.

    To set up the delay switch, there are two new INI parameters introduced on all the I/O server machines.

    [PubSub] CicodeDeviceDelayOnlineTime - Time (in seconds) to delay the switching of Cicode devices to an online state. This parameter is set on the target I/O server. During the startup phase, the I/O server will initialize each Cicode device and wait until this time has elapsed before it is set to an online state. When set to the default value (0), the delay is disabled. To enable the delay, set a value of 1 or higher (up to 32767). Allowable values: 0 - 32767 Default value: 0

    [PubSub] CicodeDeviceDelayOnlineInterval - Time (in seconds) to delay the switching for each primary device. The I/O server will set its Cicode devices to an 'online' state one at a time using the specified time interval, thereby reducing the peak load and allowing for performance tuning. This will occur after the time specified in CicodeDeviceDelayOnlineTime has expired. Allowable values: 0 - 32767 Default value: 0

    To tune the delay parameters, different project configurations require different settings for these delay parameters. You should initially start the primary I/O server with smaller delay and interval times. If the I/O server start up issues still impact the correct data being display on the client, then try to increase the delay time and/or interval time until the impact is reduced to a minimum.

Runtime Manager

  • 3746642 - Unsupported Kernel menu item appears in Runtime Manager when running in Service Mode

    The Kernel menu item would incorrectly display in the Runtime Manager when running in Service Mode, despite this being unsupported in versions of Plant SCADA before 2023 R2. The Kernel menu item will now only be displayed in Runtime Manager in Service Mode in versions from 2023 R2.

Third Party Components

  • 3752040 - AVEVA Help update

    The AVEVA Help component that hosts the help content has been updated to the latest version. Note this does not contain an update to the content itself.

  • 3464750 - CEF/Chromium security updates

    The third-party component Chromium Embedded Framework has been updated to version 133.4.3. This version has the following changes in behaviour: - When [Security]DeleteWebContentProfile=1, web content profiles are now deleted when the display client is closed instead of when the user logs out. This is because of a limitation in the latest version of CEF. - HTTP Basic Authentication is supported. - Debugging of Web Content using the Chrome Dev Tools is now fixed. The way to access the Dev Tools has changed in this version:

    1) Set [Debug]ChromiumDevToolsPort to an unused port (same as before).
    2) Open Google Chrome and enter 'chrome://inspect' into the address bar.
    3) Under 'Devices', ensure 'Discover network targets' is checked and click 'Configure...'.
    4) Enter 'localhost:<port>' into the 'Target discovery settings' dialog, where <port> is the port configured in citect.ini, then click 'Done'. This step only needs to be performed the first time you debug for a particular install of Chrome, or if you change the port configured in citect.ini.
    5) Under 'Remote Target', a list of the URLs displayed in the Web Content instances currently open in the display client should be shown. This list may take a few seconds to populate.
    6) Click 'inspect' under the instance you wish to debug, a new window with the debugging tools should open. Note each Web Content instance will appear in the list twice, however the 'inspect' option will only work for the first instance.

    Warning: Do not click the 'Close' option listed here. This will close the Web Content instance in the display client, and it cannot be opened again unless the current Plant SCADA page is re-opened.

General

  • 3767488 - The I/O server will not shutdown correctly when two or more I/O devices have misconfigured ports

    After applying an update from August 2024 or later, when two or more I/O devices were configured with port names that did not exist in the list of Ports, the I/O Server would not shutdown correctly. This could occur by incorrectly entering the port name in the I/O Device or Port, or by deleting the Port entry. This misconfiguration will trigger a dialog warning for COMX and TCPIP ports at start up, but dialogs may not occur for board drivers such as ABCLX. Logging traces for misconfigured ports will always be provided by the corresponding driver via its failed Open Channel command.

Update 07 (Feb 11, 2025)

Alarms

  • 3680251 - Data is missing from SOE after switchover if the project contains a user with no role assigned

    If the project contains one or more users with no role assigned, then on changeover of alarm server, data will disappear from the SOE for users that do have a role assigned. In all versions, user events added via SOEEventAdd and system events such as "Logged On" will disappear. In Plant SCADA 2023 and earlier, events for alarms without an area configured will disappear, and events for alarms with an area will display a blank 'User Location' field. This is now fixed and no events or values will disappear from the SOE. Note that the events would reappear if both alarm servers were stopped simultaneously then restarted. In addition, the changes for this fix mean that it is now possible to add new roles to a project, recompile, then restart the standby server followed by the main server to make the new roles available in runtime. Previously only new users could be added in this way, and adding new roles required both servers to be stopped at the same time.

Equipment Editor

  • 3700502 - The Migration Tool does not upgrade equipment parameters if only types in Include Projects need upgrading.

    The "requiring upgrade" state of the Include Projects wasn't passed to the parent project properly. With the fix, the Migration Tool is now checking the types in Include Projects recursively to upgrade equipment parameters. In addition, the equipment editor will now display a maximum of 5000 root level equipment instances in the tree control (under the project node). This prevents an out of memory error for projects with a large number of instances with no hierarchy (i.e. all instances at the same level). The additional instances can still be viewed and edited in Plant SCADA Studio

Update 06 (Dec 10, 2024)

Cicode

  • 3579780 - The tag name used in Super Genie tooltips is not resolved when AssWinReplace is called

    The tag name used in Super Genie tooltips will now resolve correctly when using the Cicode function AssWinReplace.

Equipment Editor

  • 3632444 - Equipment Editor shows an equipment type multiple times

    If an equipment type existed in an include project that was itself included in multiple include projects, then it would appear multiple times in the Equipment Editor. Equipment Editor will now check if an equipment type has previously been loaded.

Runtime

  • 3656647 - Zip files are not created when an exception occurs in a runtime process

    When an exception occurred in a runtime process and a dump file was created, the usual zip file containing the dump and relevant logs was not created. The user was also not notified of the exception in Runtime Manager. This was due to the CiExceptionMailer.exe not launching, which stopped the process that creates the zip and sends the notifications. Exception zips are now created as expected and the user notified of the exception.

Time Synchronization Configuration

  • 3603601 - Time Synchronization Configuration cannot establish a connection with the time server

    The Time Synchronization Configuration would establish and then close a connection to the time server to get the remote time for display. This occurred every second, which constantly added ports in TIMETWAIT state. This would potentially exhaust the TCP dynamic ports resulting in the configuration tool having an unhandled exception. This has been fixed by maintaining the connection to the time server while the configuration tool is open.

Various applications including Plant SCADA Studio

  • 3446533 - Plant SCADA Studio and other applications will not start when the TEMP folder does not exist

    If the TEMP folder did not exist while starting up various Plant SCADA applications, an error was displayed and the application would not start. This fix attempts to recreate the missing TEMP directory to allow the applications to open normally. Please note that if the directory creation is not successful, an error is logged in Operations Control Logger and the application will still not to start. Also, if the directory is created, it will inherit permissions from its parent.

Update 05 (Nov 12, 2024)

Cicode

  • 3391607 - Using time arithmetic in Cicode can interfere with events execution

    When using Cicode time functions such as DateAdd in your application, the internal time used to measure when events are triggered would also be updated and therefore would be incorrect. This could mean that events would not fire at the correct time as it would seem that the time is different from the actual time. The time functions have been updated so that they will not interfere with the event system.

Runtime

  • 3523945 - Priority filtering buttons on the 1080HD Situational Awareness alarm pages display incorrectly

    On the 1080HD Situational Awareness alarm pages, the icons for the priority filters spill out of the buttons they appear on. The genies that implement the priority symbols and the filter buttons are now aligned and centred correctly. The affected alarm pages in the ExampleSA and the SA_Style_1_MultiRes starter projects are updated as well. For customers that use these genies directly on their pages, please re-save those pages or run the Update Pages command in Graphics Builder. For customers that use the alarm priority genies or the filter button genies separately (for example, displaying the priority genie with their own version of buttons or defining their own priority genies and displaying them with the provided filter button genies), they may need to adjust the position of the priority symbols.

General

  • 3377212 - Update to .NET 8

    This update will upgrade Microsoft .NET 6 to .NET 8. This will include updates to the following common components: Platform Common Services (8.1.2), AVEVA Enterprise Licensing (4.1.0) and Operations Control Logger (23.2). AVEVA Industrial Graphics will continue to use .NET 6, so you should not uninstall .NET 6 from your computer.

    Note: If you are installing this update on a computer that has Historian installed, some configuration of Historian will be required before you commence installation. See the document 'Plant SCADA 2023 R2 Update 05 - Historian Configuration Requirements.pdf' for more information. This document is available from the Plant SCADA 2023 R2 download page on the AVEVA Knowledge & Support Center 'Product Hub'.

    In the event that Plant SCADA 2023 R2 Update 05 needs to be uninstalled and reverted to the previous update (or the original release), computers that have both Plant SCADA Runtime and AVEVA Enterprise License Server installed will not be able to launch Configurator. This is due to an incompatibility between the latest AEL 4.1.0 release and the original release of Plant SCADA 2023 R2.

    To prevent this, please follow the steps below.

    Note: These steps will prevent enabling Secure mode for AVEVA Enterprise License Server, so consider enabling this before uninstalling Update 05.

    1) Open the Registry Editor (regedit) and navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Wonderware\Archestra\Plugins\AVEVA Enterprise Licensing\Secure
    2) Right click on the value 'Location' and select the 'Rename' option from the context menu.
    3) Rename the value to 'Location_' and press Enter to confirm.
    4) Confirm that Configurator can now be started successfully.

    If Update 05 or later is subsequently reinstalled, rename the value back to 'Location' to enable the 'Secure' plugin again. Alternatively, uninstall Plant SCADA 2023 R2 and all AVEVA Enterprise Licensing components, then reinstall the original release and Update 04 (or earlier) including AVEVA Enterprise Licensing 4.0.1 components.

Update 04 (Oct 08, 2024)

Cicode

  • 3466432 - ClipCopy function appends newline characters to the specified string

    The ClipCopy Cicode function appends newline characters (carriage return + line feed) to the specified string when copying to the Windows clipboard. This is by design, but it prevents the copied text from being pasted into the search fields that do not accept newline characters (for example, the Process Analyst's Add Pens dialog). A new optional argument 'bAppendNewLine' has been added to ClipCopy. Pass FALSE to omit the newline characters, allowing the copied text to be pasted into the Add Pens dialog (default value is TRUE).

Compiler

  • 3487139 - Trend file names are not checked for invalid characters by compiler

    If a trend file name contained invalid characters (* ? | / " < >) or a double backslash (except at the start for UNC paths), the trend file would not be created at runtime. An error would be logged in syslog.dat, but there was no compiler error. Such paths will now result in compiler error "E2121 Invalid path".

Deployment

  • 3455908 - Deployment server performance impacted on a domain environment without an internet connection

    The deployment server configuration and its operation were slow when a client used a domain controller and both the client and domain controller were not connected to the internet. The Configurator will now launch quickly under these circumstances, and the deployment server configuration and deployment operations will respond promptly.

Licensing

  • 3512545 - ctGetLicenceInfoString CtAPI function returns 0 when runtime is using AEL licenses

    When Plant SCADA runtime is using AVEVA Enterprise Licensing (AEL) licenses, calling the ctGetLicenceInfoString CtAPI function returns 0, which is incorrect information. The AEL provider now returns the appropriate string value, "AEL" instead of "0".

Update 03 (Sept 10, 2024)

Equipment Editor

  • 3199152 - Equipment Configuration Parameters are deleted when using Save All command in Equipment Editor

    If the Save All command in Equipment Editor was used after modifying an equipment type's configuration parameters (for example, adding a new parameter), then all configured parameter values for all instances of that type were deleted from the Configuration Parameters database (eqconfig.dbf). This occurred if Save All was used directly, or indirectly by answering 'Yes' to the 'Do you want to save changes' dialog when closing the Equipment Editor with unsaved changes. To resolve this, changes made to an equipment type are only reflected in open instances when the type is saved. To avoid conflicts, instance editors are made read only when the instance's type is open with unsaved changes, and type editors are made read only when any instances of the type are open with unsaved changes. Other changes such as creating an instance of a type with unsaved changes are also prevented. The Configuration Parameters database will also now be updated appropriately when a type's parameters are changed (for example, add new rows with default value for newly added parameters, remove or update rows for deleted and renamed parameters).

  • 3035505 - Equipment shows as 'no type' in Equipment Editor if type is defined in higher-level project

    When creating an equipment instance in Equipment Editor, it was possible to create an instance of any type defined in the top-level (active) project (or its includes), and to create the instance in any of the same projects. However, if you created an instance of a type that was not defined in the same project as the instance or its includes (i.e. in a higher level or sibling project), then re-opening that instance after restarting the Equipment Editor would show the type as 'No type'. Saving the instance would clear the type field stored in the equipment database, preventing Update Equipment from creating tags for this equipment. Equipment can now be opened and saved successfully regardless of which project its type is defined in.

Runtime

  • 3431989 - Plant SCADA Runtime only runs on first 32 CPUs

    For computers with more than 32 logical CPUs, the CPU Setup page in the Setup Wizard would only list 32 CPUs with runtime processes set to only run on the first 32 (processor affinity). The CPU Setup page is now disabled on machines with more than 32 logical CPUs with an appropriate warning. The CPU affinity cannot be configured. Runtime processes will always run on all CPUs, they will not have their processor affinity set.

  • 3442808 - Display client does not reconnect to server after a restart from a non-responsive state

    If a Plant SCADA server process stopped responding and restarted, a display client would not be able to reconnect to the server after this occured. The client process needed to be restarted to reestablish communication. The client will now retry connecting to SCADA servers until communication is re-established.

  • 3072295 - TagSubscribe triggers extra callback functions

    When the Cicode function TagSubscribe used its callback function, it could not log the tag value update accurately from the callback due to only one argument being passed to the subscription handle. This would cause the different value updates to have duplicate log entries from the callback because the callback function could only retrieve the tag's current cache value which was the latest value update (not the update when the callback was queued). Runtime now passes additional 'VQT' parameters to the callback. The TagSubscribe callback function has been changed to accept additional arguments as follows:

    Callback([INT handle] [, STRING value] [, QUALITY quality] [, TIMESTAMP timestamp])

    Where: handle = tag subscription handle; value = tag value; quality = value quality; timestamp = value timestamp

  • 3409385 - Tool tip content not updating at runtime

    Tool tips can now be updated dynamically when a value is changed in the background.

Third Party Components

  • 3458412 - Microsoft Visual C++ redistributables require update

    Recent security updates have been applied to the Microsoft Visual C++ redistributables included with Plant SCADA.

Update 02 (Aug 13, 2024)

Compiler

  • 3382144 - Alarm Delay fields do not support 24:00:00 at compile time

    If an alarm tag's Delay field (including HHDelay etc.) was set to 24:00:00 in Plant SCADA Studio, at runtime the value of the delay property would be 0 (no delay) instead of 86400 seconds as expected. A delay of 24:00:00 can now be set at compile time. Note this is still the maximum value for an alarm delay.

  • 2963642 - BACNet schedule is not working after migrating to v8.40

    When migrating a Plant SCADA project from version 8.30 (or earlier) to version 8.40, the runtime scheduler would not display BACNet devices in the Scheduler due to there being no parameter data in the equipment runtime database. The compiler now copies the equipment configuration parameters to the equipment runtime database. The compiler warning (W1052 - Parameter name is empty) will be raised if an empty parameter name is detected in a configuration parameters table that is linked to a piece of equipment.

IOServer

  • 3041452 - I/O server unit initialization possible during shutdown

    In some circumstances, during an I/O server shutdown, it was possible for a device to be initialized as if it was meant to come online. This will no longer occur.

Runtime

  • 3385273 - Calling DevAppend for devices with long lines causes runtime to stop working

    If the Cicode function DevAppend was called for an ASCII device where the output line length exceeded 4093 characters, runtime would stop working. The output line length is the sum of the widths of all the fields, plus separators, in the device's format string. The maximum length of a line has now been increased to 10,000 characters. If this is exceeded, a message will be logged to the syslog.dat file on startup.

Runtime Client

  • 3427447 - Client process shuts down unexpectedly on Cicode redirection

    Calling Cicode from multiple server processes that need to redirect to other servers simultaneously could cause the client process to stop working. This was due to the client only tracking a single request at a time. This has been addressed in this update.

Tag Import

  • 3312851 - Tag Import for OFSOPC device does not detect a running OFS server

    When doing a Tag Import for an OFSOPC device, the OPC Data Access Server Parameters dialog would not list the running OFS server, preventing the import from taking place. The OFS server will now be displayed in the dialog (if OFS is installed).

Update 01 (Jul 09, 2024)

Alarm Server

  • 3282585 - Setting [Alarm]ArchiveAfter to 0 impacts the alarm summary and SOE

    If [Alarm]ArchiveAfter was set to 0 (either explicitly, or by setting [Alarm]KeepOnlineFor to 1 and ArchiveAfter to greater or equal to KeepOnlineFor), this would impact the alarm summary and SOE as data would only be writable for one hour. This logic has been modified to prevent ArchiveAfter from being set to 0 and to allow it to be set equal to KeepOnlineFor. It will also be automatically set equal to KeepOnlineFor when out of range. A maximum value of 5200 (100 years) has also been added to both settings.

Alarms

  • 3045403 - Changes made to writable alarm properties are not synchronised on redundant servers

    This would occur when [Alarm]UseConfigLimits was set to 1. If changes were made to writable alarm properties (such as thresholds or delays) while one server was offline, they would not be synchronised when a server restart occurred. Alarm property changes are now correctly synchronised and persisted to the relevant DBF files when the server is restarted (assuming the other server is still running). If both servers are stopped and the one that was offline when the changes were made is started first, the changes will be lost.

  • 2894379 - AlarmFilterEdit Cicode functions stop working with Chinese, Japanese or Korean characters

    When an alarm filter contains an expression part (section delimited by semi-colons) that is longer than 254 characters and it contains Chinese, Japanese or Korean characters (or other multi-byte code page characters), then the Cicode functions AlarmFilterEditFirst/Next/Prev/Last would stop working when called to retrieve the long part. This will now work as expected.

Cicode

  • 2965061 - Support required for retrieving encryption status via Cicode

    You can now retrieve encryption status via the Cicode function CitectInfo using a new "Security" group name. Set sGroup to 'Security' and sType to '0' to determine the current encryption status.

    For example, CitectInfo("Security", "", 0).

    The following will be returned: 0 = insecure, 1 = mixed, 2 = encrypted.

  • 2639759 - The Cicode function ServerInfoEx returns '1' on both primary and standby servers when starting up

    When running the ServerInfoEx function as a startup function on both primary and standby servers, it returns '1' in both servers. Now only the primary server will return '1', the standby server will return '0'.

Client

  • 3244776 - A large number of menu items causes unexpected behaviour when running the client

    Plant SCADA was previously not able to support menu items in excess of 30000. This has been updated so that it will now support a very large number of items (in excess of 2 billion).

Deployment

  • 2864853 - Deployment activity keeps refreshing when using a domain user

    The deployment authorization logic has been simplified to improve performance and correct a token timeout calculation that would cause constant refreshing.

  • 3047818 - Deployment status disappears from the deployment server Computers view

    During deployment of large projects, if the deployment operation went beyond a user session timeout interval it would not be successful due to the user session becoming unauthorized. Now when a deployment operation commences, it will remain active even after the user session expires.

  • 2968800 - Target and Profile columns on the Computers view occasionally revert to their previous values

    A background operation to refresh the Computers view of the Deployment screen will now be suppressed after the Target or Profile dropdown control has been pressed. The background operation will be restored when the process completes.

  • 3290142 - Deployment Server password unable to contain double quotes and semi-colon characters

    The Deployment Server has been updated to permit passwords containing double quote and semi-colon characters.

Graphics

  • 2890232 - CiMenuBar control only supports 15 items

    The number of items supported by the CiMenuBar ActiveX control has been increased to 20. Also, an issue where the last item in the menu could not be clicked has been fixed.

  • 3054320 - Input cursor does not move to graphic object when it is enabled if mouse is over the object

    When a graphic object with an input command becomes enabled (for example, when its "Disable When" animation changes to FALSE), and the mouse pointer is over the object, the input cursor is now correctly moved to the object and its input command can be executed without moving the mouse again.

Graphics Builder

  • 3244685 - Arrow keys in Graphics Builder move selected items instead of mouse cursor

    In 2018 R2, the behaviour of the arrow keys in Graphics Builder was changed to move or resize the selection (when there are selected items) instead of moving the mouse cursor. Support has now been added to move the mouse cursor when there are selected items by holding the ALT key down.

  • 3364335 - Objects within a Genie instance could be moved individually using the arrow keys

    Moving objects which are part of a Genie using the arrow keys will now be prevented by detecting whether the target object is the child of another object. The Genie instance itself will still be able to be moved using the keyboard arrow keys.

Kernel

  • 3025559 - Kernel for a server process does not open for a Windows user when runtime is not running as service

    When a server process was not running as service, the windows local user could not login to the server's Kernel window. The Kernel now functions as expected.

OPCUA Server

  • 2930329 - Plant SCADA OPCUA server does not publish a value when the monitoring mode changes

    If the monitoring mode for a Plant SCADA OPCUA server was initially set to disabled and then changed to reporting at a later stage, the subscribed tag item would not get the value update until the tag value changed. This was caused by the OPCUA server not being aware of the tag item activate event. This has been addressed in the patch update.

Plant SCADA Studio

  • 3305960 - Pages with a full stop in their name do not open properly from Plant SCADA Studio

    A new page with one or more full stops in its name will now open successfully in Plant SCADA Studio.

Process Analyst

  • 2843503 - Process Analyst's Navigation Toolbar needs to be hidden

    The Process Analyst's Navigation Toolbar can now be hidden via the PA automations interface, using the existing Visible property on the appropriate Toolbar object (index 2 of the Toolbars collection). Note that Navigation Toolbar will still be automatically hidden when the chart contains no pens.

  • 3066068 - Infinite values in trend data cause Process Analyst trend line to disappear

    If a trend tag that uses Floating Point (8-byte) storage contained a floating point infinity value in its data, displaying that value in the Process Analyst would cause the trend line to disappear completely. The line could not be recovered until the Process Analyst page was reloaded. The trend server has now been modified to return an infinity value as 0 with Bad/Not Available quality. The Process Analyst will display the value the same as any other value with that quality, depending on how the pen is configured (for example, display a gap in the trend line by default).

  • 2848782 - Process Analyst labels jump left when refreshing a page

    When refreshing or switching back to a page that included a Process Analyst control, all the Process Analyst labels would relocate and become aligned to the left. Labels positions are now correctly maintained when a page refresh occurs.

Runtime

  • 3074292 - The free full user license is not given to service display client in service mode

    When runtime is running in service mode with a full user license, one free user license is now given to service display client to maintain software protection. The Kernel window now shows the free license details when runtime acquires full user license in service mode.

  • 3284501 - Periodic events and reports stop executing because the system is out of Cicode threads

    If the execution of a periodic event or report was not successful because the system was out of Cicode threads, then the event/report would get stuck and not fire again. This could be due to a large number of TaskNew calls at the time the event/report fires. The event/report will now continue to execute as scheduled once there are free threads for it to run on. An error is logged to syslog and a hardware alarm is raised when the execution does not occur. The diagnostics for event/report state in the Kernel window have also been improved.

  • 2912835 - Incremental compile impacting view areas behavior for Roles

    During a runtime start-up or reload, the Users and Roles RDB time is now considered to trigger an alarm export to the alarming backend. This means the alarms will be shown in SOE page as per the view areas setting at design time on the Roles page.

  • 2889703 - SCADA runtime process not running if Local Language is set to locale with a long time extension

    Given a computer is set to display time in 12-hour format with extension (tt) and the project is set up with language of time extension longer than 7 characters (for example, variants of Serbian (Latin)), when the user logs in to Plant SCADA with this language the SCADA process will stop working. On the other hand, if the INI parameter [Language]LocalLanguage is set to this language, the SCADA process cannot be started. The SCADA process will now continue to work when local language is set to a language that uses a long time extension. For many of the unofficially supported languages (such as variants of Serbian (Latin)), the localized time extension will also be displayed.

  • 2927142 - Hardware alarms are triggered when logging in or out of a Situational Awareness trend page

    When logging in or out of a trend page created from a Situational Awareness Starter project, the UpdateCommand event handler for the Process Analyst (PA) would be invoked. However, by the time the Cicode function had executed, the page would have refreshed which meant the original PA object was already released. To prevent the event handler operating on a released object, the event handler Cicode function Trend_PA_UpdateCommand() has been modified to call the ObjectIsValid() Cicode function to check whether the PA object is still valid before proceeding further. To facilitate this, the ObjectIsValid() Cicode function will now also take into account whether an object is released.

  • 3296680 - Run/Copy mode displays "Failed to open file" error message

    When Run/Copy mode was enabled, if page graphic files (.ctg & .ctf) or screen profiles (.cts) were missing from the Run folder, they were not copied from the Copy folder and an error message was displayed. Run/Copy mode now works as expected.

Security

  • 3056438 - Using the Setup Wizard to add a folder to the Data directory does not work

    If the Data directory was set to a non-existent folder path on the General Options Setup page of the Setup Wizard, then the runtime applications would not be able to create the Data directory. Similarly, if the Data or Logs folder did not exist, some applications (for example, Plant SCADA Studio) would not start as the startup checks would not succeed if any of the mandatory folder paths were not found. Applications are now able to start even if Logs or Data folders do not exist.

Third Party Components

  • 3371476 - CEF/Chromium: security updates

    CEF/Chromium security updates.

Trends

  • 2895257 - Cicode function TrnGetPenComment and TrendDspCursorComment truncate trend comment to 48 characters

    If you displayed trend tags using a trend object and tried to get a trend comment using the Cicode function TrnGetPenComment() or TrendDspCursorComment(), the trend comment would be truncated to its first 48 characters. This is now addressed. When both the trend server and client are running with the patched version, the Cicode function will return the full trend comment as configured in Plant SCADA Studio. For backward compatibility, if an old version of a client or trend server is running in your network setup, the trend comment will be truncated as before. For machines updated to the latest patch, the comment returned may now be longer than before. If your page uses the above Cicode functions to display text on screen, they may overlap with other objects on the page. You can use the StrTruncFont or StrLeft family of Cicode functions to truncate the text returned as required.

  • 2904946 - Trend folder created even if a file name points to a disk drive that does not exist

    A fix has been put in place to prevent the creation of a trend folder when the drive specified in a trend tag file name property does not exist.

  • 3334496 - Process Analyst control in a template is not displaying at the correct position

    The position of the Process Analyst control for the SinglePA SxW_Style template (resolution HD1080) was incorrect. The position for Process Analyst control has now been adjusted so that the control appears at correct position. Please run the "Update pages in Active and Included Projects" option in Graphics Builder if any customer projects are created based on SxW_Style template.

Web Content

  • 3188233 - Multiple display clients will not run on a computer if Web Content is enabled

    If a second display client process was started on the same computer under the same Windows user account as another client process, the second process would not start if the Web Content feature was enabled. Multiple client processes can now be started. A similar issue that existed for Computer Setup Editor has also been fixed.

  • 3388687 - Web Content profile is not deleted when client process exits

    When [Security]DeleteWebContentProfile=1, the logged-on user's Web Content profile was not deleted when the display client process would exit. This is now fixed, and the profile is deleted as expected. There was no issue with deleting a user's Web Content profile when logging out.

In This Topic
TitleResults for “How to create a CRG?”Also Available in