PowerScene 2.2.0 has been released.

PowerScene 2.2.0 fixes issues found in previous versions and improves system stability and performance.

The changes in version 2.2.0 are listed below.

# HMI

- Fixed an issue where widgets on a canvas were positioned incorrectly after switching to full-screen mode.

- Added a minimum zoom limit to prevent a canvas from being scaled smaller than the display area. This keeps the canvas properly fitted to the screen when zooming out.

- Added support for transparent canvas widget backgrounds. Transparent or semi-transparent backgrounds can now be used when placing a canvas over another screen or widget.

- Fixed an issue that caused the application to terminate unexpectedly when the onTime property of a device was connected through a data link.

- Fixed an issue where image button data links in canvases created with older versions could not be loaded correctly in the current version.

- Added the getDataByIndex() and getLastClickedBar() script APIs to the Generic Data Chart.

# PowerScene Studio

- Improved project publishing and update synchronization. Changes between server and local projects can now be identified more accurately when publishing or downloading a project.

- Added an option to select whether locally modified files should be overwritten when updating from a server project. This allows users to replace only the required files with server versions while protecting local files currently being edited.

- Fixed an issue where an “Invalid Project” error was displayed in the editor and HMI when no project had been published to the server. Unnecessary error messages are no longer displayed on new systems or in environments where a project has not yet been published.

# Data Exchange

- Fixed an issue where Data Exchange system load increased when communication status points were assigned to multiple DNP virtual devices and communication fault states changed periodically.

- Added an event trigger mode setting for event scripts and trigger controls. Users can choose whether an event is executed only when the overall expression first becomes true or whenever an individual condition becomes true.

For example, consider the following event expression:

A == 1 OR B > 30

■ When the overall expression becomes true

- The event is triggered when the overall expression changes from False to True.

- If B > 30 is already true, changing A from 0 to 1 does not trigger the event again because the overall expression remains True.

■ When an individual condition becomes true

- The event is triggered whenever any individual condition in the expression changes from False to True.

- Even if B > 30 is already true, changing A from 0 to 1 triggers the event because another individual condition has become true.

- Removed the legacy web system and consolidated web functionality into the new web system.

- Configured ports 80 and 8080 as the default service ports for the new web system.

Thank you.