Change log

2016 – 2017 – 2018 – 2019 – 2020 – 2021 – 2022 – 2023 – Current

10.04.2024

In the language selection, the heading has been changed to “Language & Region” to make it clear that not only the language is selected, but also the region. Changing the region affects in particular how numbers and dates are displayed.

Under certain circumstances it was possible that the automatic export stopped working at the end of the month.
The max values were missing in interval data diagrams in reports.
The pages did not load correctly for browsers in Italian.

14.03.2024

When creating a new assignment, it is no longer necessary to set an end for the existing assignment beforehand. This is now done automatically.
New “Blasting table” evaluation. In contrast to the previous blasting tables in reports, this evaluation can also be used in the evaluation view of a measuring point. The table cannot yet be parameterized and is currently in a test phase.

The suggested standard texts when creating alert definitions have been revised and the name of the project has been added in most places.

There was an error in the blasting table for ÖNORM S 9020. The relative values of VSS 40312 were displayed in the relative values column. However, if this standard was not configured within the measuring point, the values were shown as 0.
When importing inclinometer measurements in xml format, an error could occur under certain circumstances if the description of the measuring point was empty.

14.02.2024

Importing Sisgeo data is now possible. Because the various Sisgeo export formats do not specify the relevant unit, the channel names must conform to a certain convention if units are to be recognized correctly. Alternatively, the data can still be imported and the unit must then be set manually when creating a measuring point assignment.
Exporting third-octave band data is now also possible for all three axes simultaneously.

XMR and BMR files are no longer processed immediately, but are first added to the inbox queue as with all other data sources.
For user-defined threshold values, the variable “fMax” is no longer the maximum of the three dominant frequencies, but the dominant frequency of the maximum peak.
Gap detection in diagrams can now also be switched off for vibration measuring points.

It was possible that a measurement with an inclinometer probe was not imported if it had already been imported once and then deleted again.
An error had unfortunately crept in to the new function that allows you to filter event tables and vibration statistics by trigger mode. Under certain circumstances this led to some events being omitted in the report and on the web, although all events should have been displayed. This applied above all to common trigger events and those that were triggered manually. “Normal” events were not affected and were always displayed.
Under certain circumstances, it was possible that the online status of a measuring point was considered OFFLINE, although the associated data source was ONLINE.
It was possible that not all events were displayed when “Last available data” was displayed.

11.01.2024

When creating a blasting entry, it is now possible to create a vibration event that corresponds to the blast. This is created from existing events.
Deleting “blasting events”
The event table and vibration statistics can now be filtered according to the type of event. These options are available:
All, “Common trigger” events (Menhir only) and created events (blasting, see above)

Changes since export with the “Since last export” mode:
The end date of an export is no longer set as the time at which the export was carried out, but the last exported time stamp. Moreover the status of an export is set as “Failed”, if no data is exported.
The legends Min, Max and Average are now also displayed in vibration statistics.
If you wish to set a certain alert definition as the new standard value, you are no longer required to first deselect the old alert definition.
When hiding events, all background channels are set to 0 – previously this was only the case for peaks and vector sums.

When changing the time period of a measuring point assignment, the times in the log entry were false.