PowerScene version 2.2.1 has been released.
PowerScene 2.2.1 fixes issues found in previous versions and improves system stability and performance.
The changes in version 2.2.1 are listed below.
# Data Explorer
- Improved lists with many columns, including status, analog, and text points and formulas, by freezing the columns through the name column. You can now keep item names visible while scrolling horizontally to edit data.
- Improved existing-table registration so that users can select from a list that excludes system tables and internal PowerScene tables.
- Added support for registering tables from external databases configured in the project's database connection settings as user tables.
- Added user table structure editing. You can view, add, modify, and delete column, index, and foreign key definitions in the editor.
- Fixed an issue where moving rows did not work correctly in certain situations or the changed row order was not retained after saving.
# PowerScene Studio
- Fixed an issue where an image button's image disappeared when the button was resized.
- Added DB tags to link database values to graphic objects through data links. In addition to point and device information, you can now retrieve and display database information, such as equipment details, using data links.
How to Use DB Tags
1. Register a User Table Before using DB tags, register the table you want to query as a user table in Data Explorer. In a DB tag, use the display name specified when registering the user table.
2. Link a DB Tag to a Graphic Object Select the graphic object that will display the data, then enter a DB tag in its data link settings. Use the following format.
Format: @USER_DB::User table name.[Row condition].[Column to display]
Example: @USER_DB::Equipment.[device_id=1].[device_names] This tag retrieves the device_names value from the row where device_id is 1 in the user table registered as Equipment and displays it on the screen.
3. Reuse One Screen for Multiple Devices By including variables in the query condition, you can substitute device-specific values when loading the screen. Example: @USER_DB::Equipment.[DEVICE_ID=$device_id].[DEVICE_NAMES] Use the following script to assign a device ID to $device_id. canvas.replacePointName(['$device_id:%d' % 1]) Running this script replaces $device_id with 1, changing the tag as follows. @USER_DB::Equipment.[DEVICE_ID=1].[DEVICE_NAMES] By changing only the device-specific query condition, you can reuse one screen for multiple devices. For string conditions, include the required quotation marks directly in the tag. The following example retrieves the energy purpose using the equipment name. @USER_DB::Equipment.[DEVICE_NAMES='$device_name'].[ENERGY_PURPOSE] Use the following script to assign an equipment name to $device_name. canvas.replacePointName(['$device_name:L-M_전기 메인']) After substitution, the tag becomes: @USER_DB::Equipment.[DEVICE_NAMES='L-M_전기 메인'].[ENERGY_PURPOSE] The tag retrieves the ENERGY_PURPOSE value for the specified equipment and displays it on the screen. Substitution uses the supplied text exactly as entered. It does not automatically add or adjust quotation marks. |
# HMI
- Fixed an issue where historical reports displayed instantaneous values instead of the selected data type. Reports now display the selected data type, such as interval changes.
- Fixed an issue where calculated results were saved incorrectly in certain historical data group configurations because source points registered in another historical data group were not referenced correctly when saving summation or formula result points.
This concludes the release notes.
Thank you.
