RealTime release notes

monitoredPoint_struct

ignoreRTNHoldOff

New field.

doas_privilege

collect

Description changed to "deprecated field".

Case–N/A

(Defect–3446699)

This defect fix involved enhancing the Alarm Inhibit dialog box for status and analog records such that, when a command fails, a pop-up window now opens and indicates the cause of the failure.

Case–N/A

(Defect–3513164)

This defect fix addresses an issue where a temporary increase in handle count during startup or after a failover exceeded the limits in the DataExportEngine process. Now, if a message such as the following appears, increase the processHandleWarning and processHandleCritical limits by following the steps in the "Override Process Monitor settings (Example)" section of the AVEVA Enterprise SCADA Tools Administrator documentation:
Process DataExportEngine exceeds handle count critical limit of 30,000...

Case–N/A

(Defect–3563681)

This defect fix addresses an issue where the upgraded system and non-upgraded system were not able to synchronize.

Case–N/A

(Defect–3728275)

This defect fix involved adding additional fields to the RealTime_Nom2XML.json file to enable the override of the following, previously non-overridable fields:

• PointCodePrefix

• FileFormatType

• DebugLevel

For further information, refer to "Configure the Realtime_Nom2XML.json file" in volume 2 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Case–N/A

(Defect–3610137)

This defect fix addresses an issue where the tag message line length was not limited to one line and 132 characters, which in turn caused other fields to become corrupt.

Case–N/A

(User Story–3717534)

This story addresses an issue where changing a base message of an analog, a multistate, or a rate point to a new message that has a different number of messages in the message set resulted in the current message not being updated on the non-owing system.

Case–960386954

(Defect–3307418)

This defect fix addresses an issue where unacknowledged station alarms were not displaying the correct alarms in the easy eXtended Operator Station (ezXOS) Station Summary window when the system removed an active alarm.

Case–960392531

(Defect–3251007)

This defect fix addresses an issue where, when a Controller cleared the alarm inhibit checkboxes on the Alarm Inhibit dialog, the system re-selected the Normal Alarm check box on the corresponding display in the Advanced Database Editor (ADE).

Case–960427246

(Defect–3478468)

This defect fix involved improving the existing user documentation description of the Scale Factor and Integration Scale Factor fields.

For further information, refer to "Rate Row Edit: Averages and Integration Tab" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Case–960429175

(Defect–3419790)

This defect fix addresses an issue where the system generated log entries in reverse order after the Timed Alarm Inhibit timer expired.

Case–960434622

(Defect–3429840)

This defect fix involved improving the existing user documentation on changing baseline enumerations.

For further information, refer to "Enable severity enumeration - none (example)" in the AVEVA Enterprise SCADA RealTime Developer documentation.

Case–960446426

(Defect–3488467)

This defect fix addresses an issue where the body of a text message was corrupted when an alarm email was converted to SMS. The encoding of the body was changed to UTF-8 from UTF-16.

Case–960452216

(Defect–3520733)

This defect fix addresses an issue where the output states of status or multistate records were not available for selection in the Flextag Control dialog's State field.

Case–960460890

(Defect–3545330)

This defect fix involved removing the obsolete "Job Scheduler Scripts" section from volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Case–960472188

(Defect–3611897)

This defect fix addresses an issue where tables were not unlocked when exiting a function.

Case–960474193

(Defect–3593950)

This defect fix addresses an issue where incorrect dqFlags values were reported for exception collection points in TimeSeries after a mode switch.

Case–960476926

(Defect–3595748)

This defect fix involved addressing incomplete user documentation on the AlarmFilterString Business Logic Tier (BLT).

For further information, refer to the following:

• "AlarmFilterString" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation

• "AlarmFilterString" in the AVEVA Enterprise SCADA RealTime Developer documentation

Case–960483359

(Defect–3615140)

This defect fix involved improving the existing user documentation description for when the system generates non-covered Area Of Responsibility (AOR) alarms.

For further information, refer to "Non-Covered Area Alarm" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Case–960483416

(Defect–3686069)

This defect fix addresses an issue where DPdirect was not transferring data to the destination system.

As part of this fix, documentation was added in regards to the RSConnectTimeout setting. For further information, refer to "DPdirect fails to connect" in the AVEVA Enterprise SCADA Historical Administrator documentation.

Case–960484987

(Defect–3619235)

This defect fix addresses an issue where the system ignored the process name parameter when an Administrator entered the parameter into the SpoolMsg BLT.

Case–960488949

(Defect–3682687)

This defect fix addresses an issue where the RealTime synchronization fails between the owning and non-owning system when source to destination configuration is enabled.

Important: If the RealTime synchronization issue continues to persist after installing, or upgrading to, AVEVA Enterprise SCADA 2025, you can increase the value of the CMXREP_REVERSE_COMMAND_DELAY_MS configuration setting to resolve the issue. The default value is 10000 ms.

Case–960502648

(Defect–3788016)

This defect fix involved adding detailed information on the pwrinit field.

For further information, refer to "Remote table details" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Case–960502121

(Defect–3650835)

This defect fix addresses an issue where the system recorded inconsistent values for the lastStatus field in the RealTime database (RTDB) collect table when a collect record was configured to collect data by exception for points with high rate and flatline alarms.

For further information, refer to "Data collection by exception" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Important: As part of this fix, the system will trigger exception collection based on the flag.alarm field, in addition to the four pre-defined data qualities.

Case–960505615

(Defect–3673190)

This defect fix addresses an issue where the system did not correctly calculate the FlowTotal after an Administrator made changes to the associated FlowTotalJoin record in ADE.

Case–960511363

(Defect–3684306)

This defect fix addresses an issue where the RTDB lastDQ field values were incorrect when the FIELDTIME_AS_TIME_IN_COLLECT setting was set to true.

Important: The ExportRecord Application Programming Interface (API) signature has been modified. If you have developed a custom High Performance Data Export Framework (HPDEF) plugin, you must refactor the plugin code. For more information, refer to "Developer scenarios for the High Performance Data Export Framework (HPDEF) Application Programming Interface (API)" in the AVEVA Enterprise SCADA HPDEF API Reference documentation.

Case–960532583

Case–960538104

(Defect–3732882)

This defect fix involved updating the documentation in numerous places with information on limitations when using SchemaConverter to expand the RealTime database (RTDB).

For more information, refer to the AVEVA Enterprise SCADA RealTime Developer documentation.

Case–960544797

(Defect–3790193)

This defect fix addresses an issue that prevented indefinite alarm inhibition when an Administrator configured the maximum inhibit timeout.

There is a known issue in AVEVA Enterprise SCADA 2025 wherein Developers are unable to compile the sample C++ Software Development Kit (SDK) projects on a development computer with Visual Studio installed.

Contact AVEVA Customer Support to request copies of the missing CPP .props files.