Difference between revisions of "NVGate 2021: Release note"
(246 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
[[category:NVGate2021]] | |||
Other languages available: ''[[NVGate_2021:_Release_note_fr|Fr]], [[NVGate_2021:_Release_note_de|De]]''<br><br> | |||
OROS strives to be closer to its users, carefully listening to needs and requests. For that reason, OROS regularly releases new versions. Customers under contract automatically benefit from each release. | |||
[[File:Screenshot 2020-12-21 102850.png|500px]] | |||
<br><br> | |||
The NVGate® 2021 major version became available in January 2021. This release of the OROS 3-Series analyzer’s software platform brings additional functionalities and significant performance improvements. Below is a summary of the main enhancements of your NVGate experience:<br> | |||
== | {| class="wikitable" style="width: 90%;" | ||
== | |- | ||
| style="width: 25%"| [[File:1250px-Wikipedia_logo_(svg).svg.png|50px|link=NVGate_2021:_Release_note#Here_is_OROS_Wiki_on_the_line.2C_how_can_I_help_you.3F]]<br>''' On line OROS Wiki, how can I help you?''' <br> Help is now available online with a powerful search engine. An offline version is available as well for when you are in the field. | |||
| style="width: 25%"| [[File:filter__2021.png|50px]]<br> '''Relax the limits of filtering!'''<br> Cut off frequencies of filters, Butterworth and '''new Chebyshev type I and II''', can now be chosen very flexibly. | |||
| style="width: 25%"| [[File:kinematik_2021.png|50px]]<br>'''Tracking my bearing frequencies on RPMs variations''' <br> Kinematik markers are now tracking the frequency lines as the speed fluctuates. | |||
| style="width: 25%"| [[File:gps_2021.png|50px]]<br> Enrich your measurements in real time with '''GPS''' information.''' | |||
|- | |||
| [[File:simulated_dc.png|200px]]<br> Using the '''DC simulated''' function, one can now associate NVGate results with information from external software in real time using NVDrive. | |||
| [[File:orbit_2021.jpg|50px]]<br> '''Draw those orbits!''' <br>Orbits can now be displayed directly in NVGate with FFt-Diag option. | |||
| [[File:calibration_2021.png|50px]]<br> Dynamical inputs can now calibrate DC sensors with y = ax + b formula. | |||
| [[File:human_2021.png|50px]]<br>'''How much does this body shake?''' <br>A new add-on is available to apply human vibrations filters and calculate associated quantities. | |||
|} | |||
This release note describes the content of version, with operating details. | |||
<br> | |||
To download and install NVGate 2021, [[NVGate_2021:_Install_Process|check this page]]. | |||
<br><br> | |||
'''Compatibility:''' | |||
NVGate 2021 is compatible with all OROS instruments that have not been discontinued. Depending on the hardware options and version, some instrument features may or may not be available. | |||
= | = Here is OROS Wiki on the line, how can I help you? = | ||
All the documentation and help have been completely renewed. We have put an online wiki-based documentation with videos, manuals, application notes, and download links. | |||
= DC simulated | This page is in free access and can be consulted here: https://wiki.oros.com/wiki/index.php/Home | ||
== Online Help: wiki == | |||
We advise being connected to internet to enjoy the new documentation page. <br> | |||
If you are connected to Internet, the following buttons will bring you to the NVGate wiki page.<br> | |||
[[NVGate|https://wiki.oros.com/wiki/index.php/NVGate]] | |||
<gallery> | |||
File:help_menu.png | |||
File:Help_ribbon.png | |||
File:Help_asb.png | |||
</gallery> | |||
Be aware this wiki page has a powerful search button if you need to search any setting.<br> | |||
[[File:help search.png]] | |||
If you are using NVGate in a different language than english, the wikipage will be opened with /XX at the end (XX correspond to the unicode language.<br> | |||
For example, if you are using NVGate in Japanese, help will bring you to the page: | |||
https://wiki.oros.com/wiki/index.php/NVGate/ja (==> ja is the international Japanese code) | |||
== Off line Help: PDF manual == | |||
If you are not connected to the internet which may often happen in the field, the NVGate.pdf manual will be opened. This file is located in the "Manuals" folder in the installation directory of NVGate. | |||
== Tutorials Videos == | |||
The OROS Youtube channel is available here featuring a full panel of videos on how to use OROS products: | |||
[[File:youtube.png|600px]]<br> | |||
[https://www.youtube.com/user/OROSanalyzers/ OROS Youtube channels page] | |||
We have included tutorial videos in this wiki to help you to use the OROS software. | |||
= Tracking bearing frequencies on RPMs variations = | |||
== Kinematik markers follow FFT tachometer== | |||
The Kinematik marker can now be associated to the speed of the tachometer. | |||
So during a Run up the kinematik marker will automatically move inside FFT spectrum with the speed. | |||
How to use it: | |||
Select a Tachometer on the FFT tab from GoToResult page. | |||
[[File:kiné_fft.png|500px]] | |||
Then display a FFT spectrum. Select a kinematik marker and put it on the window. | |||
[[File:kiné_select.png|400px]] | |||
Now this marker will be linked to the FFT speed. | |||
Then on properties, you can link (or not) this marker to the speed. | |||
[[File:kiné_select_active.png|300px]] | |||
== Automatic installation of the database == | |||
Now the excel kinematic database including bearings from NSK, SKF, FAG, SNRn, GMN, INA, RHP is installed automatically. | |||
You can find it in the installation folder: "NVGate Data\Markers\Kinematic\" | |||
== Direct access to database== | |||
When clicking on the "open folder" button, you will directly access the folder where the Excel kinematic database is stored | |||
so you can edit the database easily if you need to add the kinematic configuration of a rotating machine. | |||
[[File:kiné_select_edit.png|400px]] | |||
= Relax the limits of filtering! = | |||
All details on the filters can be read [[NVGate_Filter_Builder|here]] | |||
===Relaxed constraints on the cut-off frequency=== | |||
To guarantee the stability of the filter, there are certain constraints on the value of the cut-off frequency. Compared with previous version of NVGate, such constraints are relaxed significantly now. | |||
[[File:image_2020-11-27_095451.png|600px]] | |||
For the high pass and low pass filters, the maximum value of the cut-off frequency is the input frequency range '''FR'''. The minimum value is '''FR''' / 50000 in the Office mode, and '''FR''' / 40000 in the Connected mode. In the previous NVGate version, the minimum value was '''FR''' / 40 for the low pass filter, and '''FR''' / 400 for the high pass filter. | |||
For the band pass and band stop filters, the low cut-off frequency ''f''<sub>low</sub> and the high cut-off frequency ''f''<sub>high</sub> need to meet the following conditions in the Office mode: | |||
* ''f''<sub>low</sub> ≥ 0.0001 * '''FR''' | |||
* ''f''<sub>high</sub> ≤ '''FR''' | |||
* 0.0004 * '''FR''' ≤ ''f''<sub>high</sub> - ''f''<sub>low</sub> ≤ 0.9998 * '''FR''' | |||
And in the Connected mode, the conditions are as below: | |||
* ''f''<sub>low</sub> ≥ 0.0005 * '''FR''' | |||
* ''f''<sub>high</sub> ≤ '''FR''' | |||
* 0.000675 * '''FR''' ≤ ''f''<sub>high</sub> - ''f''<sub>low</sub> ≤ 0.99 * '''FR''' | |||
In the previous NVGate version, the conditions on the cut-off frequencies were: | |||
* ''f''<sub>low</sub> ≥ 0.055 * '''FR''' | |||
* ''f''<sub>high</sub> ≤ '''FR''' | |||
* 0.0075 * '''FR''' ≤ ''f''<sub>high</sub> - ''f''<sub>low</sub> ≤ 0.99 * '''FR''' | |||
==Improved precision== | |||
Now, the filters are calculated in 64-bit floating point format in the Office mode, and in 40-bit floating point format in the Connected mode. In the previous NVGate version, the 32-bit floating point format was used in both modes. | |||
===New prototype filters=== | |||
In addition to the Butterworth filter, now you can build the IIR filters with the Chebyshev type I (band-pass ripple) filter or Chebyshev type II (stop-band ripple) filter. | |||
The Butterworth filter has flat response in both the pass band and stop band, but its transition band is wide. | |||
The Chebyshev type I (band-pass ripple filter) has the steepest roll-off among the three filters, and its response in the stop band is flat. However, it has ripples in the pass band. | |||
The Chebyshev type II (stop-band ripple) filter has flat response in the pass band, but it has ripples in the stop band. Its transition band is narrower than the Butterworth filter, but wider than the Chebyshev type I. | |||
Below is an example showing these three filters with the same filter order. | |||
[[File:filters_3.png|600px]] | |||
Thanks to its maximal flat frequency response in the pass band, the Butterworth filter is commonly used in applications where signal distortion should be minimized, such as audio noise reduction. It is also widely used for anti-aliasing. The Chebyshev filters are optimized to provide steep roll-off, and they are usually used in applications where the maximum rejection of the nearby frequencies is required. | |||
===Increased filter order=== | |||
The order of the filter affects the steepness of its roll-off. The higher the order is, the sharper the transition between the pass band and the stop band is. An example demonstrating the impact of the filter order is shown below: | |||
[[File:butterworth_freq_response.png|600px]] | |||
For the high pass and low pass filters, the filter order can be selected from 1 to 40 in the Office mode, and from 1 to 10 in the Connected mode now. In the previous NVGate version, the maximum filter order was 6. | |||
For the band pass and band stop filters, the filter order is 2*N, and N can be selected from 1 to 30 in the Office mode, and between 1 to 10 in the Connected mode now. In the previous NVGate version, the maximum value of N was 5. | |||
===Octave overall no limitation=== | |||
1/n Octave Overall levels frequency range plug-ins are now editable. You can define the min and max. | |||
This overall is computed in the time domain (weighting filter and detector). Processing weighting in the time domain provides accurate measurement for non-stationary signals (impulsive). | |||
[[File:octave_filter.png|400px]] | |||
'''Full range mode''' computes the overall on the whole frequency range excluding the DC component. (The minimum range is defined by "CPB filters Lower central frequency"/5). | |||
'''Limited range''' lets the user define the range by changing the low cut off frequency and high cut off frequency. | |||
= Enrich your measurements in real time: from GPS to environmental metadata = | |||
The DC simulated inputs allow you to inject up to 32 external DC channels in NVGate from external source (example : GPS, weather station, external can bus...). The frequency sampling is up to 15 samples / second. | |||
Thanks to the python developer toolkit, a developer can easily develop an interface to inject the values into NVGate. The GPS and weather station below have been developed using the DC simulated. | |||
This option is included with the reference ORNV-VI-DC (which also includes the Virtual input). | |||
How to use it: | |||
<br> | |||
On the Acquisition Tab, select connect input, select the DC inputs and select the DC simulated channels. | |||
[[File:DC simulat.png|600px]] | |||
These channels can be activated and connected to the recorder and/or waterfall like any other DC channels. | |||
[[File:DC_simul.png]] | |||
The settings '''Value''' (which can be controlled by an external software) will change the value of the inputs. | |||
[[NVGate_Front_End#Simulated_DC_Inputs|The other DC simulated settings details]] are explained on the front end settings page. | |||
== GPS == | == GPS == | ||
== | Thanks to the "DC simulated channels" we have created an Add-on to record GPS data. | ||
== | |||
The GPS have the following features | |||
* Record the X-Y GPS coordinates. | |||
* Record and display the speed profile. | |||
* Use the speed profile as a waterfall reference. | |||
* Create a .gpx and display it on an internet website if you have an Internet connection). | |||
You can visit the dedicated page to download it and advanced configuration. : https://wiki.oros.com/wiki/index.php/NVGate_DC_Simulated_Manager | |||
We have 2 ways to acquire the GPS position, android phone or GPS Compliant with NMEA 0183 standard. | |||
=== Serial GPGGA GPS === | |||
We are compatible with GPS USB Serial Interface Compliant with NMEA 0183 standard GPGGA <br> | |||
We recommend the GPS USB Navilock NL-602U but other GPS units will work as well.<br> | |||
[[File:gps_navilock.jpg|200px]] | |||
=== Android GPS === | |||
[[File:GPS_phone.png|500px]] | |||
GPS data can also be retrieved using Android ADB (Android Debug Bridge). | |||
If you plug your android phone, we can inject the GPS position into NVGate. | |||
=== How to use it === | |||
Once the gps is plugged and configured, click on inject data, this will put the value on the DC simulated inputs. | |||
[[File:GPS process 2.png|400px]] | |||
Then you can use these channels on NVGate. | |||
If you need to record the data, click on connect input, go on DC input tab, then drag and drop the DC simulated channels on recorder. | |||
[[File:GPS process.png|600px]] | |||
If you have recorded the data you will be able to create a .gpx file | |||
=== Creating and visualize .gpx file === | |||
We can create a .gpx from an .oxf (OROS) signal file. a .gpx is gps file to follow the geographic information of the signal on a map. | |||
You need to click on "Convert signal to gpx". | |||
[[File:GPS_creategpx.png|150px]] | |||
This will open the windows below. | |||
[[File:signal_gpx.png|400px]] | |||
= | Select the signal file that you need to convert and click on load data. | ||
== DC Dynamical sensor y = ax+b calibration == | You can modify the channels if needed. | ||
Click on create .gpx. | |||
The .gpx will be put in the "attachement" folder of the NVGate project. | |||
If you want to visualize the .gpx we advise using the website : https://www.gpsvisualizer.com/ | |||
Clicking on "Click here to visualize the .gpx on a website" opens a website allowing you to plot the gpx on a map. | |||
== Weather station== | |||
Precipitation, wind speed/direction, pressure, temperature, and pressure can prejudice sound pressure levels or need to be recorded when you are doing sound measurement. | |||
Thanks to the DC simulated channels, we can now enter manually the value or we can connect a weather station to NVGate. | |||
=== Manual === | |||
The user can enter manually the weather value. | |||
[[File:weather_manual.png|400px]]<br> | |||
===Davis instruments weather station === | |||
[[File:weather.png|200px|right]] | |||
3 elements are required to make it work | |||
- [https://www.davisinstruments.com/product/wireless-vantage-pro2-integrated-sensor-suite/ 6322OV Wireless Vantage Pro2 Integrated Sensor Suite] | |||
- [https://www.davisinstruments.com/product/wireless-weather-envoy/ 6316 Wireless Envoy] | |||
- [https://www.davisinstruments.com/product/weatherlink-windows-usb/ 6510USB WeatherLink Data Logger]. | |||
This weather station provides accurate, reliable weather monitoring with real-time data updates every 2.5 seconds. Sensor suite includes outside temperature and humidity sensors in a passive radiation shield, wind speed and direction, and rainfall. | |||
Note : The weather Station needs to pass by OROS SA for configuration. | |||
=== Other weather stations === | |||
Please contact OROS to check the possibility to import the data (paid service). | |||
=DC Dynamical sensor y = ax+b calibration = | |||
It is now possible to calibrate a dynamical sensor in "DC" or "DC floating" coupling using 2 values, then the software will automatically compute sensitivity and offset to obtain the "y = ax + b" formula. | |||
This function is practical for 4-20 mA sensors or “quasi-static” sensors acquired on dynamic channels. Wire sensor displacement sensor calibrated with a rule, pressure sensor with a calibrated compressor, proximity probe calibrated with a micrometer. | |||
For using it, first create a DC sensor on the sensor database. Then apply this sensor to a channel. | |||
Now on the calibration part, you can calibrate it using 2 values. Then the software will automatically apply the sensitivity and offset. | |||
[[File:calibrator.png|500px]] | |||
== Remove a sensor from history == | == Remove a sensor from history == | ||
= Human body vibration = | If you have made a mistake during a sensor calibration, you can now delete a value from calibration sensor history. | ||
[[File:remove_caibration.png|600px]] | |||
You need to go on history, select the sensor, select the value that you need to delete, then click on remove. | |||
= How much does this body shake? = | |||
The OROS Body Vibration tool allows you to evaluate the effect of vibration on the human body according to standards ISO 2631 and ISO 5349. These standards define measurement practice and vibration signal analysis to evaluate the effect on health and comfort of environmental and equipment vibrations on the Human body.<br> | |||
The ISO 2631 describes the effect on health and comfort of vibration on the whole-body in transportation system, and the ISO 5349 the effect on health of vibration on hands and arms when manipulating machine-tools or vibrating objects.<br> | |||
<br> | |||
This is a post analysis toolkit, operating after the recording of the signal. It will calculate time-weighted signal of acceleration and specific indicators both defined in the standards.<br> | |||
[[Image:OROS_BodyVib.png|400px|none]] | |||
'''Standards compatible''': international standards about whole/body vibration including: ISO 5349, ISO 8041, ISO 2631-1 and ISO 2631-5.<br> | |||
'''Whole/body Vibration Indicators include ''': VDV, MSDV, MTVV, Weighted raw, al(ISO 2631-5), D(ISO 2631-5) are available. RMS, Peak, Crest, peak-Peak, are also available in NVGate plug in. | |||
{| class="wikitable" style="margin: auto;" | |||
|+style="caption-side:bottom;"|''Body vibration indicators'' | |||
|- | |||
|style="height:30px; width:100px;"|<math>MTVV</math> | |||
|Maximum Transient Vibration Value, represent the maximal RMS value of the signal | |||
|- | |||
|style="height:30px; width:100px;"|<math>VDV</math> | |||
|Vibration Dose Value, taking into account the temporal shocks in the signal | |||
|- | |||
|style="height:30px; width:100px;"|<math>MSDV</math> | |||
|Motion Sickness Dose Value, representing the comfort in transportation measurement | |||
|- | |||
|style="height:30px; width:100px;"|<math>D_k</math> | |||
|The Acceleration Dose, representing the effect of the vibration on the spine | |||
|- | |||
|style="height:30px; width:100px;"|<math>A_w</math> | |||
|Daily maximal exposure value (Calculated from Post processing in NVGate) | |||
|- | |||
|style="height:30px; width:100px;"|<math>Peak</math> | |||
|Amplitude Peak of the vibration; maximal amplitude of the signal from the 0 (Calculated from Post processing in NVGate) | |||
|- | |||
|style="height:30px; width:100px;"|<math>Crest factor</math> | |||
|Ratio between the Peak level and the RMS of the weighted signal(Calculated from Post processing in NVGate) | |||
|} | |||
'''Signal filtering including''': | |||
{| class="wikitable" style="margin: auto;" | |||
|+style="caption-side:bottom;"|''Time-weighting filters'' | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_k</math> | |||
|Time weighting for the Z axis for whole-body measurement (ISO 2631-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_d</math> | |||
|Time weighting for the X and Y axis for whole-body measurement (ISO 2631-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_h</math> | |||
|Time weighting for the hand-arms measurement in any direction (ISO 5349-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_f</math> | |||
|Time weighting for motion sickness measurement in the vertical direction (ISO 2631-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_c</math> | |||
|Time weighting for the X axis for whole-body measurement (ISO 2631-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_e</math> | |||
|Time weighting for all rotational directions for whole-body measurement (ISO 2631-1) | |||
|- | |||
|style="height:30px; width:100px;"|<math>W_j</math> | |||
|Time weighting for the Z axis for head comfort measurement (ISO 2631-1) | |||
|} | |||
How to use it: | |||
https://wiki.oros.com/wiki/index.php/Human_Vibration | |||
This Add-on is free of charge for NVGate 2021 users and TDA (?) | |||
= Orbit display included in FFT diag or ORD diag = | |||
For customer with option FFT-Diag or ORD-Diag, they will now have the Orbit display available in NVGate. | |||
[[File:Display_Graphs_Traces_122.png|400px]]<br> | |||
The orbit is available using the add/remove windows. | |||
For more details, please check the [[NVGate_Display#Orbit|orbit dipslay page.]] | |||
=Miscellaneous= | |||
== Displaying Time in Zoomed signal relative to measurement== | |||
It is now possible to display the time "relative to measurement" in zoom signal.<br> | |||
[[image:zomm_relative.png|600px]] | |||
*Absolute time: displays the time from windows format. | |||
*Relative time: displays the duration of the record. The beginning of the record is set to 0. | |||
*Auto: selects absolute or relative time depending on the duration of the record. For records smaller than 2s, the relative time is displayed, for others, the absolute time is chosen. | |||
*relative to measurement: displays the duration of the record. The beginning of the record is set to the "player start offset" | |||
== NVdrive : SetViewmeterLevels == | |||
Using NVdrive, you can now control and set the alarm level, high level and low level. | |||
[[File:Viewmeter.jpg|none]] | |||
Check the NVDrive toolkit for more info. | |||
=Bug fixing= | |||
<br> | |||
* 13728: [Fractional Tachometer] Using a fractional tachometer lead to DSP error - | |||
* 13729: [Drec] : Impossible to record more than 38 ch in Drec | |||
* 13672: Delta RPM with source DC tach (from monitor) - do not trig the waterfall | |||
* 10572: Low pass response for ICP and AC coupling poorly specified | |||
* 13811: NVDrive GetResultEx error while running without displaying result | |||
* 13774: Orbit display improvement | |||
* 13790: Change the number of displayed orbits | |||
* 13794: A problem of DRPM stop at 5000 RPM instead of 6000. | |||
* 13953: [General] A-weighting can be applied several times (report 13912) | |||
* 13938: Input type: Xpod bridge, one channel 5 doesn't work if 1 activated | |||
* 13767: Create a new unit : do not go on a "empty" windows, keep the previous configuration. | |||
* 13979: WIFI connection | |||
* 14011: import a template from NVgate to OR10 , the japanese label became wrong | |||
* 14009: OR10 Stand Alone : the japanese label data become wrong | |||
* 13912: A-weighting can be applied several times | |||
* 13984: Units - The number of digits doesn't change in a specific configuration |
Latest revision as of 15:53, 15 March 2021
Other languages available: Fr, De
OROS strives to be closer to its users, carefully listening to needs and requests. For that reason, OROS regularly releases new versions. Customers under contract automatically benefit from each release.
The NVGate® 2021 major version became available in January 2021. This release of the OROS 3-Series analyzer’s software platform brings additional functionalities and significant performance improvements. Below is a summary of the main enhancements of your NVGate experience:
This release note describes the content of version, with operating details.
To download and install NVGate 2021, check this page.
Compatibility:
NVGate 2021 is compatible with all OROS instruments that have not been discontinued. Depending on the hardware options and version, some instrument features may or may not be available.
Here is OROS Wiki on the line, how can I help you?
All the documentation and help have been completely renewed. We have put an online wiki-based documentation with videos, manuals, application notes, and download links.
This page is in free access and can be consulted here: https://wiki.oros.com/wiki/index.php/Home
Online Help: wiki
We advise being connected to internet to enjoy the new documentation page.
If you are connected to Internet, the following buttons will bring you to the NVGate wiki page.
https://wiki.oros.com/wiki/index.php/NVGate
Be aware this wiki page has a powerful search button if you need to search any setting.
If you are using NVGate in a different language than english, the wikipage will be opened with /XX at the end (XX correspond to the unicode language.
For example, if you are using NVGate in Japanese, help will bring you to the page: https://wiki.oros.com/wiki/index.php/NVGate/ja (==> ja is the international Japanese code)
Off line Help: PDF manual
If you are not connected to the internet which may often happen in the field, the NVGate.pdf manual will be opened. This file is located in the "Manuals" folder in the installation directory of NVGate.
Tutorials Videos
The OROS Youtube channel is available here featuring a full panel of videos on how to use OROS products:
We have included tutorial videos in this wiki to help you to use the OROS software.
Tracking bearing frequencies on RPMs variations
Kinematik markers follow FFT tachometer
The Kinematik marker can now be associated to the speed of the tachometer. So during a Run up the kinematik marker will automatically move inside FFT spectrum with the speed.
How to use it: Select a Tachometer on the FFT tab from GoToResult page.
Then display a FFT spectrum. Select a kinematik marker and put it on the window.
Now this marker will be linked to the FFT speed.
Then on properties, you can link (or not) this marker to the speed.
Automatic installation of the database
Now the excel kinematic database including bearings from NSK, SKF, FAG, SNRn, GMN, INA, RHP is installed automatically.
You can find it in the installation folder: "NVGate Data\Markers\Kinematic\"
Direct access to database
When clicking on the "open folder" button, you will directly access the folder where the Excel kinematic database is stored so you can edit the database easily if you need to add the kinematic configuration of a rotating machine.
Relax the limits of filtering!
All details on the filters can be read here
Relaxed constraints on the cut-off frequency
To guarantee the stability of the filter, there are certain constraints on the value of the cut-off frequency. Compared with previous version of NVGate, such constraints are relaxed significantly now.
For the high pass and low pass filters, the maximum value of the cut-off frequency is the input frequency range FR. The minimum value is FR / 50000 in the Office mode, and FR / 40000 in the Connected mode. In the previous NVGate version, the minimum value was FR / 40 for the low pass filter, and FR / 400 for the high pass filter.
For the band pass and band stop filters, the low cut-off frequency flow and the high cut-off frequency fhigh need to meet the following conditions in the Office mode:
- flow ≥ 0.0001 * FR
- fhigh ≤ FR
- 0.0004 * FR ≤ fhigh - flow ≤ 0.9998 * FR
And in the Connected mode, the conditions are as below:
- flow ≥ 0.0005 * FR
- fhigh ≤ FR
- 0.000675 * FR ≤ fhigh - flow ≤ 0.99 * FR
In the previous NVGate version, the conditions on the cut-off frequencies were:
- flow ≥ 0.055 * FR
- fhigh ≤ FR
- 0.0075 * FR ≤ fhigh - flow ≤ 0.99 * FR
Improved precision
Now, the filters are calculated in 64-bit floating point format in the Office mode, and in 40-bit floating point format in the Connected mode. In the previous NVGate version, the 32-bit floating point format was used in both modes.
New prototype filters
In addition to the Butterworth filter, now you can build the IIR filters with the Chebyshev type I (band-pass ripple) filter or Chebyshev type II (stop-band ripple) filter.
The Butterworth filter has flat response in both the pass band and stop band, but its transition band is wide.
The Chebyshev type I (band-pass ripple filter) has the steepest roll-off among the three filters, and its response in the stop band is flat. However, it has ripples in the pass band.
The Chebyshev type II (stop-band ripple) filter has flat response in the pass band, but it has ripples in the stop band. Its transition band is narrower than the Butterworth filter, but wider than the Chebyshev type I.
Below is an example showing these three filters with the same filter order.
Thanks to its maximal flat frequency response in the pass band, the Butterworth filter is commonly used in applications where signal distortion should be minimized, such as audio noise reduction. It is also widely used for anti-aliasing. The Chebyshev filters are optimized to provide steep roll-off, and they are usually used in applications where the maximum rejection of the nearby frequencies is required.
Increased filter order
The order of the filter affects the steepness of its roll-off. The higher the order is, the sharper the transition between the pass band and the stop band is. An example demonstrating the impact of the filter order is shown below:
For the high pass and low pass filters, the filter order can be selected from 1 to 40 in the Office mode, and from 1 to 10 in the Connected mode now. In the previous NVGate version, the maximum filter order was 6.
For the band pass and band stop filters, the filter order is 2*N, and N can be selected from 1 to 30 in the Office mode, and between 1 to 10 in the Connected mode now. In the previous NVGate version, the maximum value of N was 5.
Octave overall no limitation
1/n Octave Overall levels frequency range plug-ins are now editable. You can define the min and max. This overall is computed in the time domain (weighting filter and detector). Processing weighting in the time domain provides accurate measurement for non-stationary signals (impulsive).
Full range mode computes the overall on the whole frequency range excluding the DC component. (The minimum range is defined by "CPB filters Lower central frequency"/5).
Limited range lets the user define the range by changing the low cut off frequency and high cut off frequency.
Enrich your measurements in real time: from GPS to environmental metadata
The DC simulated inputs allow you to inject up to 32 external DC channels in NVGate from external source (example : GPS, weather station, external can bus...). The frequency sampling is up to 15 samples / second. Thanks to the python developer toolkit, a developer can easily develop an interface to inject the values into NVGate. The GPS and weather station below have been developed using the DC simulated.
This option is included with the reference ORNV-VI-DC (which also includes the Virtual input).
How to use it:
On the Acquisition Tab, select connect input, select the DC inputs and select the DC simulated channels.
These channels can be activated and connected to the recorder and/or waterfall like any other DC channels.
The settings Value (which can be controlled by an external software) will change the value of the inputs.
The other DC simulated settings details are explained on the front end settings page.
GPS
Thanks to the "DC simulated channels" we have created an Add-on to record GPS data.
The GPS have the following features
- Record the X-Y GPS coordinates.
- Record and display the speed profile.
- Use the speed profile as a waterfall reference.
- Create a .gpx and display it on an internet website if you have an Internet connection).
You can visit the dedicated page to download it and advanced configuration. : https://wiki.oros.com/wiki/index.php/NVGate_DC_Simulated_Manager
We have 2 ways to acquire the GPS position, android phone or GPS Compliant with NMEA 0183 standard.
Serial GPGGA GPS
We are compatible with GPS USB Serial Interface Compliant with NMEA 0183 standard GPGGA
We recommend the GPS USB Navilock NL-602U but other GPS units will work as well.
Android GPS
GPS data can also be retrieved using Android ADB (Android Debug Bridge). If you plug your android phone, we can inject the GPS position into NVGate.
How to use it
Once the gps is plugged and configured, click on inject data, this will put the value on the DC simulated inputs.
Then you can use these channels on NVGate.
If you need to record the data, click on connect input, go on DC input tab, then drag and drop the DC simulated channels on recorder.
If you have recorded the data you will be able to create a .gpx file
Creating and visualize .gpx file
We can create a .gpx from an .oxf (OROS) signal file. a .gpx is gps file to follow the geographic information of the signal on a map.
You need to click on "Convert signal to gpx".
This will open the windows below.
Select the signal file that you need to convert and click on load data. You can modify the channels if needed. Click on create .gpx. The .gpx will be put in the "attachement" folder of the NVGate project.
If you want to visualize the .gpx we advise using the website : https://www.gpsvisualizer.com/ Clicking on "Click here to visualize the .gpx on a website" opens a website allowing you to plot the gpx on a map.
Weather station
Precipitation, wind speed/direction, pressure, temperature, and pressure can prejudice sound pressure levels or need to be recorded when you are doing sound measurement.
Thanks to the DC simulated channels, we can now enter manually the value or we can connect a weather station to NVGate.
Manual
The user can enter manually the weather value.
Davis instruments weather station
3 elements are required to make it work
- 6322OV Wireless Vantage Pro2 Integrated Sensor Suite
- 6510USB WeatherLink Data Logger.
This weather station provides accurate, reliable weather monitoring with real-time data updates every 2.5 seconds. Sensor suite includes outside temperature and humidity sensors in a passive radiation shield, wind speed and direction, and rainfall.
Note : The weather Station needs to pass by OROS SA for configuration.
Other weather stations
Please contact OROS to check the possibility to import the data (paid service).
DC Dynamical sensor y = ax+b calibration
It is now possible to calibrate a dynamical sensor in "DC" or "DC floating" coupling using 2 values, then the software will automatically compute sensitivity and offset to obtain the "y = ax + b" formula.
This function is practical for 4-20 mA sensors or “quasi-static” sensors acquired on dynamic channels. Wire sensor displacement sensor calibrated with a rule, pressure sensor with a calibrated compressor, proximity probe calibrated with a micrometer.
For using it, first create a DC sensor on the sensor database. Then apply this sensor to a channel.
Now on the calibration part, you can calibrate it using 2 values. Then the software will automatically apply the sensitivity and offset.
Remove a sensor from history
If you have made a mistake during a sensor calibration, you can now delete a value from calibration sensor history.
You need to go on history, select the sensor, select the value that you need to delete, then click on remove.
How much does this body shake?
The OROS Body Vibration tool allows you to evaluate the effect of vibration on the human body according to standards ISO 2631 and ISO 5349. These standards define measurement practice and vibration signal analysis to evaluate the effect on health and comfort of environmental and equipment vibrations on the Human body.
The ISO 2631 describes the effect on health and comfort of vibration on the whole-body in transportation system, and the ISO 5349 the effect on health of vibration on hands and arms when manipulating machine-tools or vibrating objects.
This is a post analysis toolkit, operating after the recording of the signal. It will calculate time-weighted signal of acceleration and specific indicators both defined in the standards.
Standards compatible: international standards about whole/body vibration including: ISO 5349, ISO 8041, ISO 2631-1 and ISO 2631-5.
Whole/body Vibration Indicators include : VDV, MSDV, MTVV, Weighted raw, al(ISO 2631-5), D(ISO 2631-5) are available. RMS, Peak, Crest, peak-Peak, are also available in NVGate plug in.
Maximum Transient Vibration Value, represent the maximal RMS value of the signal | |
Vibration Dose Value, taking into account the temporal shocks in the signal | |
Motion Sickness Dose Value, representing the comfort in transportation measurement | |
The Acceleration Dose, representing the effect of the vibration on the spine | |
Daily maximal exposure value (Calculated from Post processing in NVGate) | |
Amplitude Peak of the vibration; maximal amplitude of the signal from the 0 (Calculated from Post processing in NVGate) | |
Ratio between the Peak level and the RMS of the weighted signal(Calculated from Post processing in NVGate) |
Signal filtering including:
Time weighting for the Z axis for whole-body measurement (ISO 2631-1) | |
Time weighting for the X and Y axis for whole-body measurement (ISO 2631-1) | |
Time weighting for the hand-arms measurement in any direction (ISO 5349-1) | |
Time weighting for motion sickness measurement in the vertical direction (ISO 2631-1) | |
Time weighting for the X axis for whole-body measurement (ISO 2631-1) | |
Time weighting for all rotational directions for whole-body measurement (ISO 2631-1) | |
Time weighting for the Z axis for head comfort measurement (ISO 2631-1) |
How to use it: https://wiki.oros.com/wiki/index.php/Human_Vibration
This Add-on is free of charge for NVGate 2021 users and TDA (?)
Orbit display included in FFT diag or ORD diag
For customer with option FFT-Diag or ORD-Diag, they will now have the Orbit display available in NVGate.
The orbit is available using the add/remove windows.
For more details, please check the orbit dipslay page.
Miscellaneous
Displaying Time in Zoomed signal relative to measurement
It is now possible to display the time "relative to measurement" in zoom signal.
- Absolute time: displays the time from windows format.
- Relative time: displays the duration of the record. The beginning of the record is set to 0.
- Auto: selects absolute or relative time depending on the duration of the record. For records smaller than 2s, the relative time is displayed, for others, the absolute time is chosen.
- relative to measurement: displays the duration of the record. The beginning of the record is set to the "player start offset"
NVdrive : SetViewmeterLevels
Using NVdrive, you can now control and set the alarm level, high level and low level.
Check the NVDrive toolkit for more info.
Bug fixing
- 13728: [Fractional Tachometer] Using a fractional tachometer lead to DSP error -
- 13729: [Drec] : Impossible to record more than 38 ch in Drec
- 13672: Delta RPM with source DC tach (from monitor) - do not trig the waterfall
- 10572: Low pass response for ICP and AC coupling poorly specified
- 13811: NVDrive GetResultEx error while running without displaying result
- 13774: Orbit display improvement
- 13790: Change the number of displayed orbits
- 13794: A problem of DRPM stop at 5000 RPM instead of 6000.
- 13953: [General] A-weighting can be applied several times (report 13912)
- 13938: Input type: Xpod bridge, one channel 5 doesn't work if 1 activated
- 13767: Create a new unit : do not go on a "empty" windows, keep the previous configuration.
- 13979: WIFI connection
- 14011: import a template from NVgate to OR10 , the japanese label became wrong
- 14009: OR10 Stand Alone : the japanese label data become wrong
- 13912: A-weighting can be applied several times
- 13984: Units - The number of digits doesn't change in a specific configuration