Downgrade not possible because the internal database structure has been changed.
What’s new in this version?
To run ibaHD-Server v3.4.x the EUP date of 2024-11-20 or later is needed.
General information:
The time-period configuration is not allowing ‘.’ as part of the configured name of columns and display names. New configurations containing the symbol ‘.’ as part of field names for display or column names will not be applicable. This check will be reversed in the next bug fix version.
New Features
ibaHD-Server supports the storage of non-equidistant signal data. A new profile type to record signals as non-equidistant data has been added to the ibaPDA data store configuration. Signals assigned to be recorded as non-equidistant are stored at raw level with a time stamp and value as tuple. As no data compression is possible at raw data level, the data volume for non-equidistant data can be higher than for conventionally equidistant recorded signal data. The use of non-equivalent data requires ibaPDA v8.9.0 or later. For detailed information please refer to the ‘New Feature’ document or the manual of ibaHD-Server v3.4.0, chapter 1. Non-equidistant data can be helpful for various applications, especially for the energy sector.
With ibaPDA v8.9.0 or higher, it is possible to define custom-specific aggregation profiles. Instead of the standard aggregation mode, in which 40 signal values are aggregated to minimum, maximum and average values in the next higher aggregation level, individual time ranges can be assigned. The aggregation factor from one level to the next level can be changed within certain limits to fulfil the required data analysis purpose.
Limitations are:
a maximum of 5 aggregation levels can be defined
at least one level with timebase > 1 minute
timebases must be < 7 days
each layer must be a multiplication of the level below. E.g. level 1 with timebase 500ms and level 2 with timebase 20.35 seconds is not allowed.
The aggregation levels are now guaranteed to remain equidistant across gaps. In previous versions, the first point after a gap introduced by restarting the new (or changed signal configuration) was the point that defined the equidistant grid afterwards. This could result in data being shifted e.g. in ibaAnalyzer to draw the entire graph equidistant across the gaps. Combined with custom-defined aggregation profiles, the data used in analyses and reports will now be more precise.
When applying the store configuration, the total required disk space is checked. In previous versions only the disk space for each store individual was taken into account. Disabled stores are excluded from the disk space resource check.
Important Improvements
An error code with further information is returned to the ibaPDA, if the writer configuration cannot be applied. With this information, the client can decide whether it makes sense to try to start the same writer configuration again after a certain waiting time. A missing license, for example, is one such reason.
When configuring backup jobs or selecting existing backups to be mounted or attached, it is possible to select mapped network drives using the folder selection dialog. As Windows assigns mapped drives only to the current user, the selected mapped drives are automatically changed to UNC paths and the login credentials must be entered. A restart after the installation of ibaHD-Server is required to obtain this feature.
Improved handling of stores related to detection of invalid configurations:
HD stores are loaded and listed in the overview and configuration, instead of being skipped or in removed in rare cases.
HD stores are highlighted to indicate their invalid configuration.
ibaHD-API supports the request of non-equidistant data.
ibaHD-API supports the query of time-period requests by a new parameter ‘limit’ to reduce the total amount of returned query results.
Request messages from ibaAnalyzer or ibaHD-API read requests are stored in separate log files located at the new introduced ‘Request’ folder.
Bugfixes
In rare situations it could happen that after an acquisition stop and start (creation of a small gap in the data) the aggregation layers could contain bad or missing data from the gap. In the worst case, no aggregation data is available until the next acquisition stop.
When creating backups of store indices, it was not checked whether enough disk space was available. This could lead to bad index backup files, which can cause problems during restart the system when free disk space is available.
A corrupted index file, segment file or a complete backup could cause crashes of the ibaHD-Server service when this backup is added to the ibaHD-Server.
Backup: Bit decoder signals where not included in backup. This could lead to incomplete backups. Recommendation is to create a new full backup with this version.
Annotations were not counted for the pareto count in event table.
Restore backup tasks that had a UNC path selected as the user-defined working directory always failed.
ibaHD-API:
Vectors had an incorrect group type.
Vector data were not always returned in time.
Applications using the gRPC connection to read vector data need to update the schema requests to support vector requests according to the corrected structure.
OPC UA: Bit decoder signals returned wrong values in both live and historical requests.
For full reference on other included new features, improvements and bugfixes please download this new version and check the included version history document.
Registered users can download this new version in our download area.
