- In tachymetric data sources, the raw data from device measuring points can now be exported in the original format.
- Exporting background data is no longer done per device, but rather per device measuring point. This allows you to control the export in more detail and fixes several problems related to different configurations of the device measuring points (type of background data, interval, etc.)
- Exporting background data via the web API has not functioned since version 4.11.0.
- When switching language in the web interface, the formatting of event tables did not immediately adapt.
- SFTP servers are now also supported as export targets.
- Along with the possibility of downloading files individually, there is now also the option to download all files in a list as a Zip archive. This is of particular interest for export orders, in order to download all export data at once.
- Loading the web pages now happens more quickly.
- When using the “English – USA” language setting, an error occurred in some circumstances when entering time points.
- Further evaluations are now available: “Value/value diagram” and “Value/value table”.
- Optional validation of input data in tachymetric measurements.
- Retrospectively sorting certain columns in an event table no longer functioned correctly and led to an error.
- The “Last available data” option in SmartFilter did not function correctly in some circumstances.
- Imported one-third-octave band data was 1000x too large upon export.
- Imports from https://www.pegelonline.wsv.de/ no longer functioned reliably via http and is now carried out via https. Errors that occur during retrievals from the web service are now displayed in the device log.
- The export from measuring points displaying one-third-octave band data sometimes did not function.
- When importing one-third-octave band data, the import only worked on the next day after changing the Menhir settings.
- Deleting devices and data sources can now be done faster. Checking whether a device can be deleted has been standardized for all types. Generally the following applies: If a device or data source is used in a measuring point, it is notpossible to delete it. All assignments must be removed beforehand.
- The calculation for the “SmartDike-Chain – Borehole trajectory” function block has been revised.
Note: This block is still in the beta phase.
- When exporting location-value diagrams as tables, the selection of measurements was not correctly taken over for the table in some circumstances
- Another choice of interval data has been added to the data export of vibration measurements: “Peaks”, KbfTi” and “Dominant Frequencies” can now be exported together in one file.
- New “3D Chain” function block for Glötzl SmartSINC data evaluations.
- The representation of vibration events in interval data diagrams has been simplified. The start and end time point of the event is no longer marked, only the trigger time point. This keeps the representation of multiple events plainer and clearer.
- When importing inclinometer measurements, “Data import successful” was displayed in the log, even if individual measurements could not be imported.
- An optional label can now be addd to location/value tables, like in location/value diagrams. This is displayed in the “Location” column of the table along with the concrete location value.
- An error has been removed that caused the import of data to fail if the data to be imported was structured in a certain way.
- Importing and exporting octave band data from the Menhir measurement device is now completely supported.
- When exporting interval data, you can now select which data should be exported. All types of interval data are now available to export again.
- An error that occured when saving user groups has been fixed.
- The storage of interval data has been revised internally, creating a new architecture with which SDC can react more flexibly to changes (e.g. to new types of interval data).
- The export of interval data has been restricted to peaks and vector sums. The export process will be fully available again in the next version.
- Before carrying out an immediate export, the start and end of the export as well as the name can be changed.
- It is now possible to change the color scale used in location-value diagrams, or o select the color yourself. Moreover, the line thickness and the marking of data points can also be set.
- When exporting automatically, the same settings can be made when choosing the user-defined CSV format as when directly exporting a table.
- The sequential color palette has been extended and the colors are now significantly different from each other.
- The time period displayed in the event table did not always match the time period set in the measuring point time filter.
- An error has been fixed which caused the vertical gridlines in time-value diagrams to not be positioned exactly at the beginning/end of years, if time periods greater than 8 years were being represented.
- Diagrams can now also be exported as CSV format files. Previously, diagrams could only be exported as image files.
- For the “Glötzl SINC Chain Link (Vertical)” function block, another output channel “Torsion to north” has been added.
- During automatic report generation, some charts were not generated due to invalid chart sizes.
- In certain circumstances, it was possible that input data for a data source was processed only with a considerable delay.
- In blasting folders, you can now set which notification is displayed when no event is found within the selected blast detection interval. The text can be freely chosen and can contain up to 70 characters. The trigger threshold of the previous event can be inserted anywhere using the placeholder #Event.TriggerLevel#.
- The usage statistics have been completely revised and following statistics are now created:
- Data usage by month as diagram and table
- Statistics for notifications via email, SMS or telephone
- Statistics for documents and document measuring points
- Email alert notifications now always contain a link to the alert next to the project link.
- The “File list” evaluation no longer functioned.
- When uploading an export to an FTP server, invalid characters in the file name were not adequately recognized and automatically replaced.
- When generating reports, it was possible that diagrams were missing due to an invalid width or height. The limits for the validation of valid diagram sizes had been too narrow here.
- For alerting, there is now the possibility to import alerts directly from the device or data source, provided that the device and the import format used support this. Alerts will then not be set by analyzing the measured data in SDC, but rather taken directly from the imported data.
- Alerts in measuring point channels can now be deleted not only individually, but also within a certain period of time.
- When importing inclinometer measurements, a success notification appeared that was visible to all users active at that moment. This notification no longer appears. To check the success of an import, you can find a detailed entry related to each import in the device log.
- Event tables did not load for users without admin rights.
- When deleting measurements from an inclinometer probe, an error message appeared after the deletion – although the deletion was successful.
- Tachymeter module: When displaying a measurement, the measured values of all three axes appeared the same in the table.
- It is now possible to automatically export data from SDC, e.g. to an FTP server, according to a configurable schedule.
- When exporting measured value tables from an inclinometer probe, there is now the option to also export head data.
- When loading event tables with a large number of vibration events, it was possible that the website became inoperable. We have now greatly optimized the way that event tables load, so that tables with many events now load quicker.
- An error has been fixed that occured when calculating and evaluating Glötzl Smart Inclinometer Chains (SINC).
- After creating a new user, in some cases it was not possible for this new user to log in.
- An error has been fixed that prevented users with the correct rights from duplicating measuring points.
- In the dialog for hiding alerts, the date could only be entered manually due to an error. Now a calendar popup can also be used.
- In the case of interval data (vibration module), the maximums are now displayed in the legend.
- Further options are now available for communication channels.
- Along with email and SMS, receiving alerts via voice call is now officially available.
- In global evaluations, a further function block is now available for inclinometer chains, in order to calculate and display the borehole trajectory alongside the deformation.
- When hiding folders in the project tree, it is now also possible to hide all subelements of the folder. Previously, all measuring points and folders had to be hidden individually.
- If a voice call for an alert must be confirmed, the confirmation link is no longer automatically added like in email or SMS notifications. The alert via voice call can be confirmed using the voice menu.
- The CSV export of a table did not function in evaluation measuring points.
- Deleting user groups failed in some circumstances.
- An error that occasionally occured during the import of Menhir background data has been fixed. It was possible that the data of a device could not be imported for some hours and so the device was shown as offline – even though data had been sent.
- Notification via voice call
Notifications in the case of alerts were previously possible via email or SMS. Now there is also the option to receive notifications via voice call.
This function is still in the test phase and will be described in more detail in a later version.
- Text fields in reports are now correctly placed and displayed.
- An error has been fixed, which could cause an invalid time period error message when using SmartFilter.
- Occasionally, devices attempt to import data “from the future” due to an error or an incorrect setting. These are now rejected by SDC, if the data is more than 6 hours in the future.
- For Menhir interval data (vibration measurement), only the “Secondary airborne noise” and not the A-weighted vibration acceleration is displayed.
- Previously, input elements could only be displayed per project when importing. Now it is also possible to display these per device. The processing time for input elements is now also displayed in a diagram next to the table, so that a much better analysis is possible.
- The import process for logger data as been revised and optimized in several places, so that even when mass importing data for a data source, the new data is always been processed first.
- “Minimal required number of threshold value violations” is now limited in alert definitions.
- In tachymeter measuring points, an offset value can be set when assigning to a data source. An error has been fixed, in which correct measurement data was supplied, but an incorrect value was displayed in the “Last measurement” column in the input channel overview table.
- Deleting created reports now functions correctly again.
- Duplication with prefix replacement for “Global evalulation” measuring points: “Global evaluation” measuring points now also offer the option to automatically replace the existing prefix with a new one. The same process as for logger measuring points. You can find a more detailed description of this function here.
- For location-value evaluations, creating up to 50 channels in one evaluation is now possible.
- It is now obligatory to enter a name for an evaluation view in order to save it.
- Import of Campbell TOA5 format
Data logger files from Campbell Scientific in TOA5 format can now be imported into SDC. This means that is now possible to integrate Campbell devices, such as the CR1000X , into an SDC system.
- New data source – MQTT data source
With this data source, Glötzl-LoRa-Funk-Sensoren can now be evaluated in SDC.
- Edge steepness and 55 dB limit for secondary airborne sound diagrams
For secondary airborne sound diagrams in the vibration measurement module, a line with the limit value 55 dB can now be displayed. If the secondary airborne noise exceeds this limit, the edge steepness is also displayed as an indicator for the speed of the rise in noise.
- Assignment of cost centers to SDC objects
The following SDC objects can now be assigned a so-called cost center: alert definitions, user groups, report templates, document measuring points, as well as vibration measurement, logger, inclinometer and tachymeter devices. This information can be used to create statistics, for example for accounting purposes. This can be used, for example, to determine how many alert SMS message the cost centers send in a certain period of time etc.
- Creating reports from user-defined document templates did not function correctly in all cases. This has been corrected.
- When calculating edge steepness, depending on the signal curve, values occurred that were too small. The calculation process has been changed.
- Secondary airborne noise and Wm-weighted vibration acceleration now displayable in an event table : In the event table of a vibration measuring point, secondary airborne noise and Wm-weighted vibration acceleration can now be displayed as additional columns. To display the new values, click on “Edit” in the context menu of the relevant measuring point. Extend the corresponding “event table” in the “Evaluations” tab. You find find all the displayable values here. Open the desired category by clicking on the “Plus” icon and mark the values to be displayed. Save the changes.
- The columns of the report template table were not displayed in full length in rare cases. This should now be fixed.
- Reference measurements in logger or tachymeter measuring points could not be deleted in some circumstances.
- Additional information for blasting operations export: When exporting blasting operations in Excel format, further identification data is displayed concerning vibration events that have occured. In addition to the maximum vector sum, the secondary airborne sound and the edge steepness (= slope between the point where the secondary airborne sound exceeds 55dbA for the first time and the maximum), as well as the Wm-weighted vibration acceleration are exported.
- When analyzing vibration events: Instead of “A-weighted vibration acceleration”, the secondary airborne noise is now displayed. This is obtained by adding 6dB from the previous calculation. What exactly is calculated is theestimated level of secondary airborne noise from vibration measurement according to ONR 199005
- The “Manage measuring points” page can now be opened as specified.
- When deleting channels for which alerts with SMS or email notifications were set up, the process was terminated with an error message. This no longer happens. If an attempt is now made to delete a channel with alerts set up, a warning message appears to indicate that the alert will also be deleted, but the deletion process can be continued by confirming this.
- “Global evaluation” measuring points can now be duplicated.
- When exporting vibration events of a measuring point, the comment field can now be used for filtering: If you export the vibration events of a measuring point, you can use a filter to restrict which events are exported. To do this, select the “Events” element in the report definition. Set a check mark by “Only events with comment” here. Events without a comment will not be exported. If the check mark is set, a text field appears. Text can be entered into it and this will then only export events that also contain the entered string.
- Automatic prefix replacement for duplicated channel assignments: When duplicating measuring points and their assignments, there is now the possibility to automatically convert a certain prefix (the beginning of the channel name) into another prefix that can be determined beforehand. In this way, a measuring point can be quickly created that refers to other channels of a device that has already been set up (provided that the channels are named accordingly). To understand this better, see the example below. To use the automatic prefix change, click on “Duplicate” in the row of the desired measuring point in the measuring point overview (in the menu that opens by clicking on the arrow icon on the right). Set a check mark by “Duplicate assignments”. Then set another check mark by “Replace device channels’ names with…” In the first field, the value that should be changed can be entered. In the second field, the value to be used can be set.
- When setting up logger or tachymeter measuring points, an error message appeared if an optional name field was not filled out. This has been corrected.
- Existing assignments in the logger or tachymeter module could not be edited later; this is now possible again.
- Saving log entries (even when successful) no longer leads to an error message page.
- If log entries are sorted according to start time, this is now done chronologically correctly (no longer by the order of numerical values).
- After a maintenance announcement on the SDC interface, an error message appeared when French was set as the language. This has been corrected.
- An error has been removed, which meant that files uploaded as an attachment to a measuring point or folder could not be reopened in certain cases.
- When re-importing inclinometer data previously exported as a CSV file, measured value columns were sometimes skipped. This has been corrected.
- Several channels can be assigned to one measuring point at once: If several channels need to be assigned to a measuring point, this can be done with one action.
- Modified channels search : The interface has been adjusted; searching for channels is now clearer and easier.
- New function blocks for SINCs (vertical): With this new function block for the logger module, vertical Smart Inclinometer Chains (SINC) can now be used in SDC. The “Glötzl SINC chain link” function block requires a separate licence.
- Text blocks: There is now the option in all modules to add continuous text in evaluation views. This text is then displayed in reports or directly in the interface at freely selectable points. The exception is the vibration measurement module. Here, evaluations for reports must still be manually set up.
- When evaluating vibration events and their assesment according to DIN 4150-2, the time points for the start of day and night can now be viewed and freely defined.
- When saving “Alert for log messages” alert definitions, a check is now carried out whether rules have been defined, when the “Notify a start of alert” option has been selected.
- Previously there were long load times even for simple operations. This has been fixed through a performance optimization. The page load times have been greatly reduced with this version. Folders and measuring points now also load much more quickly. Working with SDC in general should now be much quicker.
- In the case of vibration measurement diagrams, the display when outputting as a file or report has been adjusted so that it now visually corresponds to the display in the browser.
- Dropdown fields to select a user group (such as when configuring alert definitions or report templates) now contain lists that are sorted alphabetically.
- Vibration events can now also be analyzed by users that only have read-only rights.
- An error has been removed by which the changeover from day to night values in the evaluation of vibration events according to DIN 4150-2 either directly in SDC or in reports did not work synchronously.
- Creating a report in the inclinometer module failed when it contained evaluations, in which the “Description” field in a measurement was empty.
- In blasting operation reports and lists, a modified information text is now displayed if no corresponding event could be determined for a blasting operation (“Trigger operation not fulfilled”).
- Vibration measuring points that were deleted by a user now no longer appear as selectable measuring points in report definitions.
- Export blasting operations: A list of blasting operations can now be exported as an Excel file. As well as the attributes for each blasting operation, there are further columns with information on the measuring point and a field for the maximum vector sum. Here, the maximum vector sum of any possible event is entered for each measuring point of the folder in which the blasting operations are located. The Excel export can be found in the view of the relevant blasting operation folder. By clicking on the context menu (folder icon ), the “Export blasting operations to Excel” point can be selected to begin the export.
- Display of timestamp of a data point in the Quick Info: If you hover with the mouse over one of the data points of a time/value diagram, the date of the timestamp is now given. This only functions if the time range of the diagram extends over more than one day.
- Improved color representation in the output of diagrams: If a digram is output as a file or in within a report, its representation now corresponds to the SDC view in the web interface. Previously there were differences between the two, for example in the representation of colors.
- Multiple measuring points can be added to a measuring station at once: Since many measuring points often need to be assigned to a measuring station at once, it is now possible to do this.
- The user interface for assigning measuring points to tachymeter measuring stations has been made clearer : Measuring points are now displayed in a table and can be searched for by name.
- Create track monitoring formula block via configuration file: The creation of function blocks for track monitoring previously required more effort. To simplify the process, it is now possible to upload a configuration file and the function blocks can then be automatically created.
- Performance optimisization : Diagrams and tables in the logger and tachymeter modules are now displayed more quickly, espcially when several channels are represented in one diagram/table with different measuring times. In the case of global evaluations, channels can now be calculated and displayed more quickly.
- If data import in the logger, tachymeter or inclinometer module fails due to an incorrect file format, the user is now notified of this error. The notification is given via an entry in the log of the device to which the data is assigned.
- The evaluation view elements “Diagram” and “Table” have been renamed. They are now known as “Time/value diagram” and “Time/value table”.
- The function blocks for user-defined formulae now have instructions for use.
- In the vibration measurement module, the display of the “Trigger threshold” point has been amended in the vibration events view. Spaces have been added between the entries for individual components.
- If the time axis of a diagram is divided into whole days by SmartFilter, the vertical gridlines are now correctly placed at 00:00.
- Vector graphics now also function in reports.
- Extended validation of “user-defined formulae” : In the “Logger” and “Global evaluations” modules, the validation of “user-defined formulae” function blocks has been extended when saving. This points out an incorrect specification of the formula to the user.
- New function blocks for inclinometer chains: In the “Global evaluations” module, there are now the two function blocks “Inclinometer chain – differential deformation” and “Inclinometer chain – deformation”. These are used to evaluate the data of an inclinometer chain, similar to the function blocks with the same names in the “Logger” module.
- Company name in heading of SDC interface : To further adapt the SDC interface according to customer requirements, the character string that is displayed in the heading (topmost horizontal menu bar with black background) can be specified by a privileged user (super-administrator). Standard text (as before): “SMART DATA CENTER”.
- Data export in JSON format : The SDC API has been extended, so that data from a logger measuring point or from a “global evaluation” can be exported in JSON format.
- SINC function block :New function block for evaluating Glötzl SINC chain links (Smart Inclinometer Chain) for the vertical case of application. Warning: This is still a pre-release version.
- When deleting an online status alert, the start time of the alert must be given in order confirm the deletion. An error that prevented the deletion even when the correct start time was entered has been fixed.
- In the list view of a user group, entered mobile telephone numbers of users are now visible again.
- In the “Notifications” table of alerts that have taken place, more rows were displayed than specified in the settings for table length. This has been corrected.
- Evaluation views can now be fully deleted again.
- When exporting vibration events in XMR format, the overall duration was rounded. This had no effect on the time representation, but could somewhat distort the representation in frequency space for very short events. Complete values are now displayed again.
- In some cases, the graduation marks on the Y axis of a diagram were not shown.
- Vdv background data from Menhir measurement devices were incorrectly scaled during import (factor 1000).
- The formula for adding Vdv values has been corrected.
- Diagram channels for time/value diagrams with compatible units are no longer rejected as “uncompatible”.
- If the start and end of an alert were very close in time, additional alert notifications (SMS and email) were sent, although the corresponding setting was disabled.
- Tachymeter module: if defective measured values should be displayed in a location/value diagram, the location axis minimum was falsely defined in some circumstances.
- Tachymeter module: In some circumstances, the location axis of a location/value diagram was not correctly scaled, which led to orthogonal lines being incorrectly positioned.
- Additional input channels for formula function blocks: Up to eight input channels can now be selected for the “Formula” function block.
- More detailed legends for inclinometer diagrams: The legends on diagrams for inclinometer data are now more detailed, similar to those in the GLNP software. The legend is now displayed in tabular form, whether online, when exporting images or in reports.
- Subsequent editing of inclinometer measurements: It is now possible to subsequently manually edit inclinometer measurement. For this purpose, it can be exported as a CSV file (click on the context menu of the desired measurement ( icon on the right) and select “ Export”). The CSV file can be opened and edited. Then the file can be imported back into SDC. Select the point “ Upload data” from the context menu in the selected import measuring point. It is important to empty the GUID field of the CSV if the file to be created as a new measurement. Otherwise the GUID can be left in the CSV and the original measurement deleted in SDC. It is only important that a GUID is not in the file being imported and the SDC at the same time, otherwise the export aborts and the original measurement is deleted in SDC. The values in brackets in the third column on the CSV are only intended as an explanation for the user and are not technically necessary.
- SmartFilter settings remain permanently saved: SmartFilter settings remain permanently saved for each user, even after closing SDC or logging out.
- Table length settings remain permanently saved: Above each table is a dialog field which can used to specify how many elements of a table are displayed at once on one page. This setting will now be saved permanently. There are three different types of tables. for each of which a length can be saved: for vibration events, for inclinometer tables and for all other tables (logger, tachymeter and global evaluations).
- When an import measuring point is displayed, all available data is now displayed without time-based restrictions via SmartFilter.
- Alert limits are now correctly and completely displayed in diagrams. Even if measured values are over the limit for the main alert, the limits for the alert and pre-alert are still visible.
- The name of a project folder can now no longer be changed independently of the name of the associated project. If the name of a project is changed, the name of the corresponding project folder is also automatically changed.
- In some cases, “No data” was displayed in vector graphics, even though data was available. This has been corrected.
- An error has been corrected, in which entries from lists could not be clicked on larger screens.
- When deleting measurements from a tachymeter data source, the associated measurement data is also properly deleted.
- In some circumstances, variables were inadvertently replaced with the actual values.
- Importing Solexperts data is now possible: With immediate effect, data from Solexperts devices can now be imported into SDC .
- Extended configuration options for the position axis for position-value diagrams: In the logger, tachymeter and comprehensive evaluation modules, there is now a new option field for “Graduation markings and grid lines” in the Edit mode for position-value diagrams. It can be used to control how the position axis of the diagram is labeled. If desired, the grid lines of the diagram can be hidden here, or the labeling of the axis can be adjusted. You can choose from the following options as before (“Auto”), without labeling and grid lines (“no labeling”), or labeling analogous to that under “Position / value pairs” or “Channels” (for loggers and joint evaluations) defined labels (“according to location labels”).
- Import and export of inclinometer measurements in CSV format : Inclinometer measurements can now be exported in the form of a CSV file and then imported again. This allows, for example, further editing or correction of a measurement in a spreadsheet program (e.g. Microsoft Excel).
- Automatic, context-dependent naming of CSV files when exporting an inclinometer measurement : If an inclinometer measuring is exported as a CSV file, it is named automatically. The file name contains various pieces of context information, in order to simplify the sorting of files. The file is named according to the following model: Example with ‘_’ as a separator:Testproject_ResevoirDam_M001_2020-10-03 10:40_Deformation.csv
- The spanish Die spanische vibration standard UNE 22-381 is now available in SDC.
- Adjustable value ranges for inclinometer diagrams: In the case of of inclinometer measurements diagrams, it is now possible to set the value range manually, as well as to set the intervals of the graduation lines (grid lines) yourself. The settings can be made in the corresponding diagram under “Horizontal axis” or “Vertical axis”.
- Colour and line thickness is now configurable for each individual measurement in inclinometer diagrams: Select the desired diagram in the edit view of the corresponding evaluation view. All measurements of the diagram are displayed when you click on the point “Measurements”. Five settings fields are found across two columns for each measurement. In the first column, use the field in the second line to specify the line thickness of the measurement. Use the field in the third line to change the colour of the line.
- Improved display for missing data in location-value diagrams. If no data is available for certain position-values, the line on the diagram is now disrupted. Previously the neighboring data points were connected together.
- The color description “Auto” has been renamed to “Auto (divergent colors)”.
- If the visualization of a folder is being edited, the automatic refresh of the page is paused and clickable links on the visualization (such as towards measuring point pages) are deactivated. These two points previously led to inadvertently leaving the visualization being edited and thereby losing the unsaved changes. This change means that this will not happen in future.
- The reference measurement of the corresponding measuring point is now taken for determining location coordinates in location-value diagrams in the tachymeter module. Previously the current measurement was used.
- In inclinometer module measuring points, reference measurements are now defined per assignment to an import measuring point. This means that multiple reference measurements can now be defined, each valid for the period of the assignment. Previously only one reference measurement per measuring point could be selected.
- After a project was deleted, the deleted project remained active. This error has been removed.
- Correction of an error which meant that when editing an evaluation view that was selected as the default web view, the identification of it as the default view was no longer set after saving the change.
- If the formatting of a header level was subsequently modified in a report definition in the vibration measurement module, there were issues in some cases with the associated sub-header levels. This has been corrected.
- Introduction of the inclinometer module: The inclinometer module is introduced with this version. Inclinometer devices can now be added to SDC, monitored and evaluated.
- New setting options for the time range in evaluations: Along with the two previous modes “Auto” and “Fixed”, there is now also the new “Fixed start” mode. While “Auto” is set according to the SmartFilter, a fixed start and end time can be set under “Fixed”. By using “Fixed start”, a fixed start time can be given. The end time is then set according to the SmartFilter. The new option can be selected in all evaluations in which the time interval can be defined by the user.
- Direct link to edit the current standard evaluation view: In the context menu of a measuring point (icon on the right of the measuring point page), there is now the “Edit current evaluation view” point. This leads directly to the edit view of the evaluation view that is currently set as standard.
- Show/hide gridlines in position/value diagrams: In the settings for position/value diagrams, there is now the option to “Show gridlines” under the “Location axis” point. This allows you to hide or show the gridlines of the corresponding diagram.
- If columns for “Amplitude spectrum” were selected during the creation of an event table for a vibration measuring point, e.g. “Peak value (frequency) X”, incorrect values were shown that actually belonged to other channels. This has been corrected.
- In the usage statistics for logger alert definitions, all available alerts were shown.
- In some cases in the visualization, unusually large gaps appeared between the marker of a folder measuring point and its label. This has been corrected.
- When exporting event tables in the vibration measurement module, an error occured when the “DIN4150-2” norm was selected in the Evaluation column but was not applied in the measuring point.
- If a device was added and deleted directly after saving without having correctly entered a device name, an error occured. This has been corrected.
- In the case of location/value evaluations (diagrams and tables) of global evaluation measuring points, incorrect times were displayed in the legend as the time zone was not correctly taken into account. This now functions again correctly.
- For charts and tables with a fixed time range, the time zone of the start time is now correct again.
- Reports can now be created in tachymeter, logger or global evaluation measuring points: In the folder view, when creating or editing a report template under “Definition” in the “Reports” tab, measuring points of the above-mentioned modules can now also be added. To do this, an evaluation view must also be available for the respective module (more information on this in the following entry) Note: The creation of vector graphics is not yet possible in reports of the newly added modules at the moment.
- New intermediate level “Evaluation view” added in Edit mode of logger, global evaluation or tachymeter measuring points. : Here, several “evaluations” can be configured, each of which corresponds in its functionality to the previous “Evaluations” tab. From among these views, you can now always choose the respective one that is most suitable for the current situation. For example, one report can be created with an evaluation view, and another that requires different content can be created with different evaluation view. Instead of having to manually modify evaluations for different requirements, a separate view can be created for each situation. Switching between these views is simple. Views that have already been created can be duplicated, so that they can serve as a basis for new views. The effort required is therefore reduced to a minimum. You will find more information on evaluation views here
- A new version of the “Track monitoring” function block has been added to the tachymeter module.
- Extended upload status for document templates: When a document template is uploaded, the upload status window now displays a feedback message after the process is completed, indicating whether the process was successful. Moreover, eventual error messages are shown here in detail. Notes are also shown, if required elements are missing in the template. If possible, missing elements are now also automatically added by the system.
- There is now also the possibility to create location-value diagrams for “Global evaluations”. When creating or editing assignments, the placement coordinates of the selected logger channel (if specified) can be taken over if desired.
- For location-value diagrams, labels can now also be added to the time data . These are then noted in the diagram at the corresponding entry in the diagram legend.
- In the settings for location-value diagrams, the item “Channels” is replaced by the new entry “Location/value pairs” . This now makes it possible to assign any channel to a desired measuring point. A freely selectable text can be entered in the “Label” field, which is then displayed in the corresponding position. In addition, you can configure whether the position is marked by an orthogonal line or how thick this line is. An offset for the position labeling can also be specified.
- New possibility to create global variables and measuring point variables: To create global variables, open the project folder page, click on the house icon on the right-hand side and select “Edit project settings”. Here, new variables can be created or existing ones can be edited in the text field of the “Global variables” tab. A variabl can be entered into an input field of a function block or an evaluation, like a normal value (include $ in the entry). The SDC then reads in the value that was assigned to the variable. This means that a value that is required in several places in a project only needs to be entered in one place. It can then be used as often as necessary and can be changed quickly and centrally if necessary. Individual variables can be created for measuring points, but in contrast to global variables, these can only be used in the input fields of the respective measuring point. To create this, right click on the icon in the corresponding measuring point and select “Edit”. In the “Settings” tab you will find the “Variables” sub-tab. Syntax for creating variables:$VariableName = ValueVariable. More information here.
- In the blasting module, the strength of the triggering impulse (trigger level) is only displayed in the blasting table if it is above the value 0.
- Standard users with the appropriate authorization can now properly duplicate measuring points again.
- In the measuring point management view, measuring points can now be duplicated as intended.
- If different SDC projects were opened in several tabs in a browser, it was possible that when editing and saving a logger measuring point, it was assigned to the wrong project. This has been corrected.
- Hourly mean of the A-weighted rapid sound level now works correctly again.
- New settings option: SSL encryption of the API interface.
- In the menu bar, under “Setup”, you can now set whether or not the API interface requires SSL encryption. To do this, set the “SSL required” field in the “API” tab to either “Yes” or “No”.
- For projects in which no coordinate system was previously set, the “ETRS89_UTM” coordinate system is now selected as the standard. The error messages resulting from a non-set coordinate system when changing project data will no longer appear.
- Tables with a previously defined, fixed time interval now correctly display the data of the set interval, even if a different period is set for the measuring point via the “Smart Filter” function ( ).
- In the list of alarm definitions, the decimal separators were inconsistent; these have now been standardized.
- Also under the iOS operating system version 13.4.1. or higher, project lists are now loaded properly again.
- Duplicating measuring points is now always possible again without an error message.
- The problem with the error messages appearing on the “Manage measuring points” page has been resolved.
- The quick access button to return to the current project folder (house icon) is no longer visible on SDCs with a Basic or Connect license. Using folders is only possible with a Pro license.
- The paragraph settings in the format template for reports have been corrected.
- The shortcut menu on the left has been expanded to include the project folder point (house icon). Click on the icon to get to the project folder from anywhere in SDC. The top node in the hierarchy of folders and measuring points is called the project folder. The project properties can now be edited easily via the context menu of the project folder, without having to open the project list.
- When creating a report, it is now checked whether the required Word format templates are available in the report template in SDC. If this is not the case, a warning is generated and the missing format templates are automatically inserted into the generated report.
- The entry in the context menu for showing or hiding alerts is now available in all views in which alerts are displayed in lists. It is now possible to show or hide the alerts on all pages on which lists with alerts are displayed. To do this, simply click on the icon at the top right on the relevant page and select the desired option in the context menu that appears.
- Two new placeholders have been added for alert definition message texts: With Alert.StartTime and Alert.EndTime, the absolute start or end time of an alert can now be used in the notifications of triggered alerts.
- For every project that should contain tachymeter data, an associated coordinate system must now be stored. If data is to be imported from a new tachymeter device, it is first checked whether the coordinate system stored in the device data matches that of the project. If this is not the case, the import is not carried out and an error is noted in the device log. In order to carry out a data import, the user may now have to correct the device coordinate system and then start the import again.
- In the case of online status alerts, the time since the last contact is no longer displayed by default, but rather the absolute time when the device last sent data. Existing message texts were automatically adapted, provided they had not been changed by the user.
- Error when exporting background data from a vibration measurement device has been corrected. In certain cases, SDC had falsely claimed that there was no background data.
- If data from several channels was displayed in one table, there was a display error if one or more channels contained no data within the time period represented. No measured value lines were displayed even for channels with data. Moreover, the diagram could not be exported as an image file without errors.
- New quick overview of recently triggered alerts In a folder view (“Folder/measuring point” tab), the number of warnings and errors that occurred in the last 7 days is now displayed in the overview table in the “Alerts” column. If you hover with the mouse over this value, how this value is composed is displayed in detail.
- In the “Alert definitions” area , there is now a usage statistic for each alert definition. Here, you will see how often the corresponding alert definition was used at which locations (e.g. device, measured value channe). The usage statistic is found in the list entry of the alert definition next to the “Edit” button () in the dropdown menu (arrow icon ).
- Es können nun mehrere Alarme auf einmal über einen frei definierbaren Zeitraum ausgeblendet werden.Dafür einfach bei der Übersicht über die aufgetretenen Alarme (Ausklappbares Menü über das Pfeil-Icon () in der Zeile der Alarmdefinition, dann Alarme“) rechts auf das „Alarmdefinition“-Icon () klicken „Alarme ausblenden“ () wählen. Hidden alerts are ignored for display purposes, but are not deleted and can be displayed again via “Show alerts”.
- The buttons in measuring point evaluations now have tooltips.
- If a new device is assigned to a vibration measurement measuring point, the “Last transfer” field is updates automatically and no longer contains the previous value.
- Tachymeter and logger data: In time-value diagrams with circular markers and gaps in the measured value series, the start and end markers of the corresponding curve are now correctly and completely hidden when the curve is hidden.
- Users with the required authorization now see the “Archived devices” link again as intended.
- Vibration measuring points with evaluations can now be duplicated without error messages being produced.
- New overview of all alerts that occured via an alert definition. In the list of alert definitions, there is now an arrow icon () next to each alert definition. Clicking this opens a menu, where the “Alerts” point can be selected. This opens a new page containing all the alerts that occured due to the selected alert definition.
- New overview of all alerts that occured via a channel. For each channel of a measuring point, a table can now be displayed containing all the alerts that occured via this channel. To do this, click on the icon in the detail view of a measuring point and select “Edit” . Then select the desired channel under either “Input channel” or “Output channel”. The alert table can be found under “Measured value alerts” under the channel icon .
- If the channels selected in the device change when importing background data (vibration measurement module), the changes are now immediately applied to the SDC, no longer the next day.
- For logger and tachymeter device channels, the “Channel assignments” table now contains the “Filter” column. In the case of logger devices, the “Channel name” column has been removed from the same table.
- Calling up the logbook is now also possible via the regular, dropdown menu on the left-hand side, as well as via the button in the symbol bar.
- In the project overivew (“Project management” ), the “Setup properties” in each project is now only visible to super administrators.
- The online state of vibration measuring points now updates itself as intended.
- If a non-admin assigns access rights for a folder (in the Edit view of a folder under the Folder Access Rights tab) without specifying at least one group to which they themself belong (and would thus theoretically lock themself out of the folder) and tries to save the changes, a corresponding error message now appears under “Folder Access Rights”, so that the user can identify the source of the error more clearly than with the previous error message.
- Users that belong to a user group of an archived project can now be edited again as intended.
- The data export of device background data in the vibration measurement module no longer aborts incorrectly when data is available.
- When visualizing on iOS devices, background images and tables now load again without errors.
- When editing measuring point assignments (vibration measurement module) in the French language version, the dropdown menu could not be used. This has been corrected.
- Formulas in assignments (logger): Error codes resulting from the formula calculation (e.g. division by 0) are now passed on to the result data set.
- Formulas with if-condition are now evaluated correctly even if a unit unequal to the base unit is specified within a condition. Example formula:
if(m1[cm] < 200; 1; 0)
- Channal overview added. In the “Data Logger”, “Tachymeter” and “Global Evaluations” modules, you can now display a channel overview for each input or output channel (if you have the corresponding rights). To do this, simply click on the relevant channel in the channel table in the Edit view of a measuring point. On the page that now opens, all recently measured data is displayed as a graphic or as a table. The channel view of an output channel has more tabs, one tab for each inbound channel + a general view.
- New units for hail added. Two new units for hail (hits/cm²) and hail intensity (hits/cm²h) are now available.
- Importing Glötzl CSV files in the data logger module is now possible without station name and channel number.
- Visibility of evaluations can be set In the Edit mode of measuring points, it is now possible to specify for each evaluation whether it is visible in the respective measuring point view for every user (default setting), or only for users with the right “Measuring points – Edit” (Admins).
- For tachymeter and logger measuring points, the “Filter” column in the “Assignments” tab now shows not only the selected filter, but also the parameters used for the filter.
- Logger device channels can now be properly deleted again, even if their name contains a backslash (“\”).
- If measured value gaps occur in diagram evaluations, the measured value line that continues after the gap is now displayed again with the correct, originally set formatting with regard to line thickness, marker, etc.
- If the export of data from a vibration measuring point fails because no data was available in the selected time period, this is now specified in the error message that appears.
- When exporting background data from a vibration measurement point, if the start time was set exactly to midnight (00:00:00), not all data of the selected time period was exported. This has been corrected.
- The alert table now also displays alerts for which only the end time is within the defined observation period, i.e. alerts that started before the start of the observation period but continue into it are now also taken into account again.
- If a folder is being edited and the modification is saved, the user reamins in the Edit view of the folder, rather than being redirected to the page that was visited before opening the Edit view.
- For users with the right to access document templates, the corresponding button is now properly displayed again.
- For users with the right to access document templates, the corresponding button is now properly displayed again.
- The calculation process for octave band evaluations has been corrected in the vibration measurement module.
- When assigning tachymeter channels to global evaluations, the channels are now correctly named according to the settings previously selected by the user.
- In the vibration measurement module, in the case of alerts that need to be confirmed or released, those that were already confirmed or released were also displayed at the measuring point. This was caused due to the cache not being updated and has been fixed.
- In the “Manage measuring points” view, folders were wrongly displayed alongside measuring points.
- When modifying and saving the basis folder in the folder hierarchy (i.e. the order which contains all other folders), an error occurred.
- In case of an alert that had already been acknowledged, the acknowledgement could be cancelled by a user with admin rights who did not have the permission to do so.
- The vector graphic evaluation is now available for data loggers. On the view page of a data logger measuring point, a vector graphic can be added under “Evaluations” and then under “Edit”. Here, measured values in the form of vectors can be visualized on an imported image file (such as the plan of a building site).
- Cache for loading lists. Due to the introduction of a cache, measuring point and folder lists are now loaded considerably faster.
- Log with details of errors when creating reports. If generating reports leads to warnings/errors, you will now find a corresponding entry with the generated message for each error/warning on the detail page of the respective report under “Log”, so that the reason for the incorrectly executed creation is now visible even without opening the document.
- Measuring points and folders are now displayed together in one list in the folder view , no longer in separate lists.
- The list of user groups to which a user belongs (Edit view of a user) is now grouped according to project.
- The names of created reportscan now be modified.
- For vector graphics, user input is now checked. When adding a vector graphic, a check of the user’s input is now carried out, analogous to the checks that are performed when adding other evaluations.
- Even for devices that have not yet transmitted any vibration events, the columns of alert tables can now be displayed as they have been configured. Before it was necessary that data was available from the device.
- The display of errors for location-value diagrams has been made clearer and easier to understand.
- After successfully saving a change to a folder, the user is now redirected to the page of the folder above the changed folder in the page hierarchy (example: If the changed folder is a subfolder of the folder “Measurement”, you will end up in the folder “Measurement” after the change). Previously, you were directed to the page visited before the change.
- In the assignment list of device channels, the transmission formula of the assignment is now displayed instead of the offset.
- If a diagram is to be added to “Evaluations”, the first channel must now be occupied, otherwise there will be an error message.
- If a new assignment is created in “Global evaluations”, the units that can be selected in the “Unit category” field via the drop-down menu are now sorted alphabetically.
- When displaying the WM-weighted vibration acceleration, the values were previously too large by a factor of 9.81. The change does not apply retroactively to data that has already been imported. If necessary, please contact Support: firstname.lastname@example.org.
- The tachymeter or logger channel can now be properly calculated using formulas again.
- In vibration measuring points with a high number of recorded events, there were unusually long loading times. This has been corrected.
- Measuring points where at least one channel is currently being used in a global evaluation can no longer be deleted.
- If a measurement channel was displayed once as a diagram and once as a table, the time stamps of the same entry in the table and the diagram might differ. These are now identical again.
- All location-value diagrams are now displayed with correct values again.
- For non-admin users that have the right to modify measuring points, errors were shown in some tabs when modifying measuring points. This has been corrected.
- A user group can now no longer be accidentally assigned to the currently active project when a change is made.
- Alert notifications from “Global evaluations” now contain the measuring point names.
- When connecting to the web interface of Menhir measurement devices, the assignment of port numbers is now assigned according to a different scheme.
- Inclinometer chain function block: Measured values are only calculated when input values show no error codes.
- Under certain circumstances (if background data packets were larger than 3 days) it was possible that for MR3000 devices, no background data was displayed in diagrams if a relatively small time interval was selected.
- When assigning channels to global evaluations, several channels at once can now be assigned.
- The selected unit for “Online status” and “Vibration events” alert definitions was lost after saving.
- With a certain setting (trigger on vector sum) of the Menhir vibration meter, no more vibration events could be imported.
- Vector graphics are now also available for “global evaluations“..
- In the Edit mode of measuring points, under the “Evaluations” tab, setting options for the display of measured values in diagrams has been expanded under “Value axes” (Logger, Tachymeter and Global evaluations). You can now specify for each channel whether no lines or lines of various thickness are displayed between measured value points, and/or if markers (circles) are to be displayed at the measured value points, along with the color of the lines and/or markers. Default settings are: “Line” (as before, lines are displayed), “No markers” (as before, no markers are displayed), or “Automatic” (the colors are assigned, as before, according to the order of the channels).
- Display of user group when editing users. When editing users (only for admins), it is now also displayed in which user groups the currently edited user is currently a member. When editing user groups, you can now also display which users are members of the current user group, by moving the mouse over the number of members.
- Detection of gaps in measuring points can be turned off. The detection of gaps and the associated gray coloring can now be switched off per measuring point. To do this, switch to the advanced settings of the measuring point.
- Selecting the unit in alert definitions is now easier, by now first selecting the unit category and thus making the list of available units more clearly arranged.
- In the case of log entries from alerts and reports, the time stamp was the same for all entries, namely the time of the last saving of the alarm or report in each case. This has been fixed in this update – however, it is possible that with old alerts/reports, the timestamps are still the same because they were incorrectly saved in the past. This is especially true for alerts that require release or confirmation.
- If very small SmartFilter time periods were used, it was possible that there was a small discrepancy between the time grid of a diagram and the time stamp of the data points (displayed via Tooltip). This has been corrected.
- Tables were not correctly loaded, if they were organised in groups/registers.
- The Details popup for alerts in measuring point and folder lists was only correctly displayed on the first page of the table.
- The channel list of device measuring points of vibration measurement devices was only properly displayed for admins. An error appeared for non-admins.
- Event tables can now, in addition to the CSV export, be created in reports and are configured there in the same way as in measuring points. The event table can be selected in the “Events” area, the complete structure in the report definition is as follows: Measuring points / Measuring point / Events / Event table.
- New “File list” evaluation : This allows files of a specified folder (relative to the project directory) to be displayed as a table in a measuring point view. If a date is included in the file name and the pattern is recognized, the files are sorted and filtered according to this date. If no date is recognized, the creation date of the files is used.
- Users can now also be archived. They are then no longer shown in the list of users and can also no longer be added as a member of a user group, but logging in is still possible.
- The unit of the value axis of a diagram can be optionally selected (value axis / unit). Previously, the unit of the previous channel was always used as the unit for the diagram.
- For line charts (logger & tachymeter), the measured values can now optionally be drawn as points and the display of a line can also optionally be switched off.
- The definition of channels in diagrams is now found under “Value axis” and no longer on the first level. The reason for this change is that in future, several value axes in one diagram will be possible.
- In global evaluations, location-value diagrams and location-value tables can be created as evaluations – however this was not supported.
- It is now possible to connect and calculate measured values from different modules’ measuring points (logger & tachymeter). This happens in the so-called Global evaluations. These serve as a kind of virtual measuring point, in which channels can be assigned and function blocks and evaluations can be created. The only difference is that channels are not connected with devices, but rather with channels from other measuring points.
- For an evaluation (diagram or table), a fixed time range can now optionally be defined in the parameters, which overwrites the set time range from SmartFilter.
- “kOhm” has been added as as a valid resistance unit alias name.
- For location-value diagrams and location-value tables, up to 22 location/value pairs can be specified. (measuring point-channel pairs; tachymeter)
- The process of “cloning” has been renamed everywhere as “Duplicating” .
- The parameter representation of diagrams has been revised. Channel assignments can now be found under the “Value axis” group. The reason behind this change is that in future, more than one value axis should be possible within one diagram.
- The number of possible measuring points (tachymeter) in a location-value diagram has been increased to 22.
- The parameters for diagrams and tables could be sorted differently in some cases. This has been standardized.
- For formula function blocks, entering the unit category is now required along with the unit itself. Please note that the category cannot be changed once the function block has been created.
- When duplicating measuring points with images in an evaluation, the connected image files were not copied too.
- Alerts can be hidden (for example in the case of false alerts). Hidden alerts remain visible in the alert table, but are marked as hidden. They no longer appear in the folder and measuring point lists.
- Alerts can be deleted. If an alert is deleted, this is logged in the measuring point log with the given reason.
- Releasing alerts: you can now specify that alerts must first be released before alert notifications can be sent. Only users with the corresponding rights can see released alerts.
- The representation of alerts in folder and measuring point lists has been revised and is now more detailed.
- The context menu of devices and measuring points has been revised, standardized and now also contains icons.
- An alert table no longer shows all alerts from a measuring point or a device, but rather only the selected type (such as measuring point alerts, service alerts etc.)
- Measuring point assignments in tachymeter measuring points may no longer overlap in time.
- When duplicating measuring points, manually set reference values were not included in the copy.
- The validation of function blocks failed when certain country settings were active.
- The new version of ÖNORM has been integrated and can be used optionally for the evaluation of vibration events. In the measuring point properites, you can select whether the old version ÖNORM:1986 or the new version ÖNORM:2015 should be used.
- Along with the blasting reports for DIN 4150-2/3 and SN 640 312A, a blasting report is now also available for ÖNORM.
- The dBm unit (performance level) is now included in the unit list. With this, the signal strength of the cell reception of a MCC can be represented in a diagram, for example.
- Alerts can now be retroactively given a comment, for example in order to document the cause of an alert. In order to comment on an alert, you must have the corresponding right.
- The licence overview (only for admins) has been revised and now also shows the time period of the available licences. Another new feature is the individual licence view for devices, which can be reached via the context menu in the Devices view (Licence entry).
- When defining assignments in the Logger module, a formula can be specified as a transfer function, so that the measured values of the channel included in the assignment are subjected to a corresponding conversion. With this, an offset value can be taken into consideration or other calculations can be carried out (corrections, complex unit conversions etc.). The variable for the measured values of the (only) channel entering the formula is the string
- The previous possibility of entering an offset value in Logger module assignments has been replaced by the option to enter a general formula (compare with the new feature above related to assignments). To specify the offset
<Offset-Wert>, enter the following formula in the “Transfer function” text field:
m1 + <Offset-Wert>. Note: Existing assignments will be automatically converted.
- Individual rights groups for measured value alerts and service alerts have been introduced to user group rights. This means that you can control both the visibility and the modification of alerts. The previous “Read only (including alerts) rights for measuring points and devices have been removed and are now known as the “Measured value alerts / Read only” or “Service alerts / Read only” rights. Note : During the update, the rights are automatically set based on the old rights.
- Channel lists in measuring points are now listed alphabetically throughout.
- Assigning vibration measurement devices to measuring points is now more tolerant with regard to the existing background data channels.
- Moving the position of function blocks for a better overview is once again possible.
- The scaling of measured values was incorrect for devices with acceleration sensors.
- When importing very large csv files (> 40MB), the coding was not properly recognized and this led to special characters being falsely interpreted.
- When displaying the trigger level of a vibration event, the values were given in the wrong unit.
- Alert definitions can be created by duplicating (cloning) existing alert definitions.
- Report templates can be created by duplicating (cloning) existing report templates. Any folder can be selected as the “target” for the copy.
- Report templates can be moved to any folder.
- It is now possible to output the beginning and/or end of the reporting period of a report within the report document. See: Placeholders for report templates.
- For device measuring points of vibration measurement devices, the available channels of background data are displayed in a list.
- New background data channels from a Menhir measurement device are now supported: Wm-weighted vibration acceleration and A-weighted particle velocity level. These can be displayed as diagrams.
- For A-weighted particle velocity level, the hourly average can also be displayed in the settings of the corresponding evaluation.
- New evaluations for vibration events (in the analysis view of an event): Wm-weighted vibration acceleration and A-weighted particle velocity level.
- The alert limits of an alert definition (vertical or horizontal) can now also be displayed in location/value diagrams in the Logger module.
- The SDC Api has been extended, in order to be able to export background data from a vibration measuring point in CSV format.
- In the formula printout of existing formula function blocks, the base unit of the respective input channel is now automatically added after each measured value variable without unit.
- For tachymeter data function blocks of type “Slope”, the handling of the unit of an output channel (slope change amount horizontal) has been corrected so that the alert definition provided for this unit can now be selected for it.
- The values calculated by interpolation at the limits of diagram evaluations were calculated incorrectly under certain circumstances.
- When automatically generating reports, daylight saving time was not correctly taken into account regarding the time of the next report generation.
- When defining the reporting period, the option “7 days” selected a period that was too large by one day.
- Specifying a fixed time period as a report time period is again possible (the entry fields for start and end can be edited again).
- Exporting diagram evaluations as image file: For location/value diagrams, the measured value lines are now drawn over the alert limits of an alert definition (instead of the other way around as before; previously only affected the Tachymeter module).
- In the Analysis view of a vibration event, there was an error in the calculation of the acceleration and VDV values. The VDV peaks of previous events in the event table are therefore incorrect and require recalculation where necessary. If required, please contact Support.
- Despite the maintenance mode, data from measurement devices was still received but not processed. Due to this, it was possible that data from a measurement devices was properly uploaded but could not be seen in SDC.
- An error that occured when exporting a vibration event as an MKA file has been corrected. The export only functioned when the event had previously been exported in a different format.
- There is now a view for reports which contains further details, a creation log and a list of notifications. This view can be opened by clicking on a report (previously clicking on a report started a download). The download can now be initiated via a separate button in the report view.
- During an import, you can use the project settings to ignore certain file types (super-administrators only).
- Alert definitions are now sorted alphabetically in lists.
- Administrators can call up a usage statistic concerning the size of the data bank and the number of sent emails/SMS messages.
- Navigating to the Start view previously only worked directly after logging in.
- The “Link to project” in an alert message could lead to an unexpected error message due to missing permissions of a user.
- In certain circumstances it was possible that new alerts could not be created. This resulted in an already existing alert being ended “several times”.
- Alert definitions can now be duplicated (cloned).
- Reports can now be automatically created by using a defined time plane . Once a report has been completed, users belonging to a user group can be notified.
- Reports: It is now possible to include comments from vibration events in reports. See: Placeholder to transfer comments stored for an event
- Adding and modifying reference measurements (also for individual channels) is now noted in the measuring point log.
- Folder view, “Reports” tab: The previous lists of report templates (previously on the left) and of completed reports (previously on the right) are now also available as tables that you can search and sort.
- Edit view of report templates: For all general settings and the report definition settings, separate “Settings” and “Definition” tabs have been added. Under “Settings”, the settings required for automatic report generation (see above) have been added as additional tabs.
- Formula function block: If no units were specified with the variables, they are now automatically added.
- When exporting diagrams, the resolution and size of the existing screen area were previously taken into account for the width and height of a diagram, which could lead to values that did not make sense. Now sensible standard values are given for the export, and values that are too small are rejected.
- Deleting logger device channels is rejected if it is already assigned to a measuring point.
- Users without admin rights could not assign devices or channels to a logger measuring point.
- Re-imported vibration events triggered alerts again (if alerts were configured). Now, if alerts have already been detected for a vibration event, the alerts will not be triggered again.
- The color classification of events according to the DIN 4150-3 standard in the event table only worked if DIN 4150-2 was also activated.
- The sorting of notifications in the alert view was not correct.
- In diagrams with several data rows, individual lines can now be hidden or shown by clicking on the legend.
- In Logger and Tachymeter measuring points, line sections in diagrams are colored gray, when the chronological interval between the data points is bigger than the tolerance interval for raw values. Make sure that value suitable to your measurement cycles (one that is big enough) has been set!
- Constant input channels from function blocks are now given as a function block parameter.
- Duplication measuring points : Reference measured values were only correctly displayed after updating the browser window.
- Device log: SmartFilter was not properly taken into account.
- When displaying the last measured values of output channels of a tachymeter measuring point, the measured values were displayed in an incorrect unit.
- The parameter for entering an offset was missing in location/value tables for logger data.
- Support for the new data format for Menhir vibration measurement devices. (Only affects event data).
- Mistakenly created data logger device channels can now be manually deleted.
- A “Not enough data for filtering” error code that may have been set by filteringis now retained when outputting to tables.
- Exporting diagrams : Alert labels are now also exported.
- In the Edit mode of the Project Properties, the FTP Credentials tab has been replaced with the Administrator Info tab.
- The frequency axis of an amplitude spectrum now begins with 0Hz.
- Report templates were not able to be deleted in some cases.
- Rights administration: Standard users with the “Dashboard – Realy only” right could not see the dashboard button.
- Filtered vibration events were not represented as filtered in a report.
Version 2.14.1902.6 – 05.02.2019
- You can now freely select the file format when exporting diagrams.
- You can now freely select the file format when exporting diagrams.
- There is now a maintenance mode in SDC, intended for administrative maintenance work (installing new SDC versions or safety updates). When the maintenance mode is active, no service alerts are generated for devices. A notice is also displayed to the user to inform them if and when maintenance is planned.
- New vector graphic diagram type for tachymeter measuring points.
- Logger and tachymeter measured values can now be filtered. See Filtering Tachymeter and Logger Data!
- New function block for calculating a general formula.
- New function block for evaluating water level gauge data.
- When editing function blocks and evaluations, the entry is now checked as it is being saved. This means that eventual errors are immediately identified.
- Dutch can now be selected as a region – this only affects the formatting of numbers and dates. A translation is not currently planned.
- The event table has been fundamentally revised and improved with regard to sorting and searching. The coloring according to selected norms can now be configured with the help of alert definitions. See Migrations Guide for Version 2.14.
- Evaluations for the Vibration Measurement module such as the event table can now be configured more extensively as before and adapted to your individual needs. For newly created vibration measuring points, the most common evaluations are created automatically by default.
- Function blocks for inclinometer chains now support chains with up to 20 links.
- The input check for measuring point properties has been greatly improved. The position of incorrect entries is now displayed with pinpoint accuracy.
- For location-value diagrams and location-value tables, up to 20 channels (Logger) or 13 location/value pairs (measuring point-channel pairs; Tachymeter) can now be specified.
- The number of decimal points in location values for location-value diagrams and location-value tables can now be configured. In location-value tables, a title for the location column can now be given.
- New diagram type Vibration statistics
- Vibration, tachymeter and logger measuring points can now also be created by duplicating (cloning) exisiting measuring points.
- New evaluation “Location-value table“
- New evaluation “Image“. Warning : This new feature removes the possibility of uploading an image as “visualization” in a tachymeter measuring point.
- Automatic adjustment to screen size of height and width of diagrams , so that the diagrams are totally visible (no scrolling necessary).
- API for SDC (primarily intended as an analysis tool from Semex EngCon).
- Fine-grained alerting settings options per user.
- When defining a logger assignment: Channels are sorted by name.
- When defining a tachymeter assignment from measuring points: Device measuring stations and measuring points are sorted by name.
- Expansion of alerting: Optional notification, when an alert that requires confirmation is confirmed (acknowledged).
- When exporting interval data, the export failed when several measurement device assignments were available on one day.
- Location-value diagrams can now be created.
- Function blocks for evaluating inclinometer chain data introduced.
- Global device overview across projects
- New “Vibration statistics” evaluation: Over a period of time, the peaks of all vibration events that occured are displayed in a digram. You can choose whether the permitted threshold values from the relevant norms are shown.
- In all interval data diagrams, there is now the possibility to draw all axes in one diagram.
- New device type: Generic data logger.
- Additional interval data (Vdv and dominant frequencies) is now supported (Menhir only).
- For Vdv data, there is the possibility of summation in defined time intervals.
- Avoidance of overlapping labels in log entries that are close together in time.
- Modernization of the user group management UI.
- Improved display of the project tree: The selected section of the projct hierarchy is extended by default.
- The optional torsion angle Phi is now also evaluated in the location-value diagram. (Tachymeter only).
- When diagrams are displayed in full-screen mode, all previous settings are now carried over.
- Device management / Device monitoring: Simplification of the “No license” warning: It now explicitly reads “No valid license for device monitoring available” (also in the edit view of vibration measuring devices).
- Time zone list in the “Edit” view of projects and in the “Create” view of report templates is now sorted according to the time difference to UTC (the so-called UTC offset).
- You can now select how many decimal points are used in tachymeter channels.
- The measuring channels of a measuring point are now displayed in a table and both the unit and the digits after the decimal point can be adjusted.
- The interval data diagrams that are displayed in a measuring point can now be selected and arranged in tabs.
- The device overview is no longer sorted according to module, which means that all devices are visible in one list. This list can be searched and sorted.
- Only the reception of interval data and vibration events are taken into account in the device monitoring of Menhir measuring devices. This means that if a device is only transmitting health data, it is considered offline as long as no measurement data (= interval data & events) is received.
- There are no longer pages in the project list. All projects are shown at once.
- When exporting events in mka format, the original file was not available to download. The metadata was previously missing.
- The type of measuring point can now be freely defined.
- New alert type: Alerts can be triggered if error codes occur in measured values.
- It is now possible to set or delete reference measurements for several measuring points simultaneously.
- Diagrams can be exported as images.
- Logbook : You can make entries in a logbook, which you can choose to display in diagrams. Logbook entries can be restricted to certain folder levels.
- You can choose to hide error codes in tables, or to display them in a separate column.
- The tolerance interval for raw values can now be modified.
- In measuring points, folders, devices and channels, it is possible to post individual documents (such as a data sheet or a handbook).
- The time resolution of a table can be set (e.g. measured values shown only in a certain rhythm).
- It is possible to import manually measured tachymeter data .
- In the project properties you can set the level up to which the project hierarchy should be expanded by default.
- Location-value diagrams can now be created.
- Newplaceholders in document templates.
- When creating assignments, the last selected device/channel is remembered.
- In the user-defined visualization, clicking on the symbol takes you to the folder or measuring point.
- A subject line consisting of more than one line led to an error when sending alert emails.
- User groups could only be notified in the super-administrator role.
- Alert messages to user groups were not sent to all users.
- The function name of function blocks was not correctly translated after switching language.
- Visualization using own plans has been extended again. The shapes (square, circle, triangle) can now be set.
- The color of the shapes now corresponds to the alert status of the measuring point or folder.
- The transparency of the color can be set.
- The labels can now be hidden as standard and become visible on mousover.
- External links can also now be added to the visualization.
- You can also choose to display measured values from individual channels in the visualization (only tachymeter and logger module)
- CSV export is now available for tables (tachymeter & logger module), which exports the data just as they are seen in the table.
- A user-defined CSV export is moreover available, in which various settings are possible (time zone, language, representation of time stamp, time resolutione etc.).
- SDC is now also available in Spanish.
- Live update of dashboard, devices list and folders after the set interval.
- Displaying the measuring points of a folder no longer occurs according to module, but rather in a joint table that is also sortable and searchable.
- Hidden measuring points are now marked with an icon.
- The devices list has been revised and there is now the possibility to also display devices that are not being monitored (that is, devices that do not have an alert definition assigned to them).
- The number of devices not being monitored is also displayed in the dashboard.
- The icon library has been refreshed and technologically updated.
- If a new image was uploaded to a visualization, the page format was no longer correct.
- Folders and measuring points can now be hidden in the project tree if desired.
- First version of the Logger module
- Supports Glötzl data loggers and the MCC measuring system
- Importing water level data from https://www.pegelonline.wsv.de is possible.
- Alerting for vibration events.
- Measurement data can now be edited retrospectively. Values can be changed (the original value is kept) and certain flags (e.g. transducer failer) can be set.
- The right to create reports and the right to edit report templates have been separated, so that rights for user groups can be adjusted more finely.
- The device view interface has been modernized and adapted to the Logger and Tachymeter modules.
- Device monitoring now occurs via alert definitions. Previously, each device had to be assigned a user group and the maximum allowed times since last contact had to be maintained for each device. In the new version, this can occur directly in the alert definition. The device needs only to be assigned to the relevant alert definition.
- The escalation of unacknowledged alerts only functioned the first time.
- New “Alerting” feature. SDC can now send alert notifications via email and SMS. Three-level alert definitions can be created including optional acknowledgement and escalation messages if the alert is not acknowledged in time.
- Track monitoring function block
- Along with visualization with Google Maps, you can now also upload your own plans and/or images for the visualization of measurement points and folders. In the project properties you can select which view should be displayed after logging in.
- After the beta phase, first operational version for tachymeter data in SDC
- Document measuring points can now be created. These are measuring points, the data of which is not evaluated in SDC but merely managed as documents. This gives you the possibility to manage foreign data or reports in SDC.
- Measuring points with negative coordinates were not displayed on the map.
- When zooming in diagrams, the diagram was always reset when the zoom tool was selected again.
- When editing the email address of a user, domains with more than three letters were not allowed.
- The revision of the report engine is now complete. This means that in this version, there is no longer the possibility of creating reports with the old report engine.
- The way in which reports are created has been completely revised and is now much more intuitive and split into modules.
- Support for acceleration measurement devices
- You can now set up acceleration measuring points, and so evaluate the data from acceleration measurement devices.
- In reports, the y axis can be defined for background data.
- In background data diagrams, you can choose to “conceal” hidden events, which means that the values are set to 0. This option can also be selected in reports.
- New diagram: oscillation path (in analysis view)
- New diagram: acceleration (in analysis view)
- Limit values for the Swiss and French standards can now be optionally displayed in a report.
- When filtering measuring points and blasts by time, there is now also the option instead of fixed time limits to display the last existing data.
- New feature: “CSV export of event table”
- The interface for filtering measuring points and blasts by time has been revised and standardized.
- Events in background data (interval data) are no longer displayed only as a point, but as a range.
- Measuring points with negative coordinates were not displayed on the map.
- When zooming in diagrams, the diagram was always reset when the zoom tool was selected again.
- When editing the email address of a user, domains with more than three letters were not allowed.
- The interval data from Syscom MR3000 measurement devices were offset by one interval in the diagrams, so that when the events were displayed, the deflections did not match.
- In the measuring point properties, user-defined limit values could be selected for DIN 4150-3 independently of the vibration type. This is now only possible if continuous vibration is selected as the vibration type.
- During BMR export, the peak of the third channel was not displayed in the evalution with view.
- The map view of a folder can be automatically adjusted so that all measuring points are visible on the map.
- Beta support for Menhir accelerometer in the vibration measurement module.
- Importing tachymeter data and displaying measurements/measuring points is now possible
- Coordinate system can be set in the project properties
- Expanded dashboard for tachymeter
- Error when creating a user group, if only admin users existed within the project.
- A folder with deleted measuring points could not be deleted. (Background: Deleted measuring points are still available for a certain time in the database and are only then permanently deleted.)
- When changing the project of a Menhir device, it took a certain amount of time (ca. 1h) until remote access to the device worked again.
- Umlauts in device measuring point names were not displayed correctly.
- The zip files created during XMR/BMR exports could not be opened in Windows Explorer in certain circumstances.
- Map view no longer functioned after version 2.4 in some circumstances.
- New license model introduced. An entry in the license is now required for each device. Automatic device monitoring can now be booked per device.
- Export im XMR/BMR format also from Menhir measurement devices. The export can be begun from the device or in the measuring point.
- New right for remote access to devices has been defined.
- First beta version of the inclinometer module: File-based import of inclinometer measurements is possible, display of measurements from a measuring point, diagrams for borehole paths and deformation, measured value tables.
- First beta version of the tachymeter module: Remote access to the web interface of a MCC TS is possible.
- The list of measuring points across projects has been removed. Measuring points are now only available via the folder structure in the menu on the left.
- The folder view has been revised. All information is no longer displayed at once, but organized into meaningful groups.
- Display of archived devices / measuring points / projects
- In the blast list, the list of available time periods was incorrect.
- If a device was archived and sent data again, it was set up again.
- When assigning device measuring points to measuring points, the time change was not taken into account.
- Device monitoring can be activated per device in the device settings. If a monitored device is offline, a email is automatically sent to the selected user group.
- The generation of reports has been completely revised. The ‘Play’ button in a report template can be used to start the report generation. This happens completely separately from the user interface, this means that it is no longer necessary to wait for the report generation. Completed reports are saved as files and listed in the folder view. The ‘old’ report generation option is still available as long as not all features are available (for example, the blast report is still missing).
- The devices list is now ordered according to the time of the most recent transfer of data, not device name. Start/end of measuring point view remains constant per session. Once start and end dates have been manually selected in the measuring point view, they remain set per session for other measuring points as well, allowing for better comparison of measuring points.
- After selecting a project in the project list, you will now automatically be forwarded to the dashboard of the selected project.
- If the end date of a device assignment was in the future, this was selected as the end date in the measuring point view by default, which of course led to empty diagrams.