PowerScene version 2.1.6 has been released.

This version includes fixes for issues found in previous releases as well as several functional enhancements.

The changes in version 2.1.6 are as follows:

# Communication Drivers

 - Fixed an issue where the driver program terminated abnormally when receiving invalid packets in the DNP driver.

 - Fixed an issue where reloading a channel due to data changes or via the Driver Monitor affected all channels within the same channel group, causing communication to malfunction.

# PowerScene Script

 - Fixed an issue where the replacePointName function did not execute correctly when the function argument was passed as a string type.

# System

 - Improved the initial loading speed by changing the system startup process to retrieve only required fields for status points and analog points, instead of querying all fields.

 - Improved slow initial loading of the SCADA server in projects using an MSSQL database when a large amount of historical data was stored.

 - Fixed an issue where alarms were generated during system restart even though point values had not changed. 

 - Modified the behavior so that unchanged data is not saved when storing data snapshots and historical data, improving performance.

 - Fixed an issue where the program terminated abnormally due to a synchronization problem during table version query function calls when starting the SCADA server.

 - Fixed an issue where the program terminated abnormally due to a GIL-related problem when calling app.wait in calculation script code.

 - Fixed an issue where analog historical data was not stored after a failure occurred while retrieving historical data via RPC.

# NMS

 - Enhanced MSSQL mirroring monitoring in NMS by extending it from project databases only to include external databases as well.

 - Fixed an issue where the screen of an externally registered application did not appear when the application was launched via Remote Desktop.

Thanks