OROS Wiki - User contributions [en]

NVGate BatchPostProcess tool

2020-12-29T09:26:48Z

Yannick Balter: /* Download */

Have hundreds of records to post process at once? It has never been easier using the NVGate add-on tool “BatchPostProcess”. 

The batch post-processing tool allows users to automate their post analysis campaigns. Users will be able to calculate a set of results for an entire measurement campaign. In the example below, we carried out 8 run-ups and 8 run-downs for each, then calculated FFTs, RMS values and overall profiles. 

<youtube>https://youtu.be/x86l7EccUEc</youtube>

==Download==
[https://orossas.sharepoint.com/:u:/g/support/ETUgSN0KswdNrk28zg9gHNMBcolEkPwO4Z71HRYthjopgA?e=iti82p Click here]

==Package composition==
NVGate add-on tool “BatchPostProcess”: BatchPostProcess.exe

==Configuration==
The add-on “BatchPostProcess.exe” needs to be located in NVGate install directory (next to NVGate.exe). 
Optional : It is recommended to add a shortcut of this exe file in the “Link” directory (C:\OROS\NVGate data\Links) to have direct access from NVGate in Link Section.

[[Image:BatchPostProcess_shortcut.png|framed|none]]

==Principle==
From NVGate, setup your post analysis based on the first record file. Once your configuration is done, run the “BatchPostProcess”.
Select from the top left list box the project where the signal files is located to be post processed (can be from any project). Select the signal from middle list box, then “Add” to the list of signal files to be post processed. It is possible to select signal files from several projects.
Press “Process All Files” to start the post process according to the current setup in NVGate. All files from top right list box will be post processed.
Results from post analysis are stored in current project, the name of the measurement is based on each signal file name with additional extension “_PA”
All signal files to be processed should be similar (number of channels) to the initial record file. If this condition is not valid, the record file may not be post processed.
[[image:BPP.png|framed|none|BatchPostProcess Interface]]

==Option==

* Option: “Apply Input” allows to keep the current input table for “label / Component / Node / Direction”. It’s useful to modify this data for several signal files, either in re-recording or for post analysis.
* Options “Save Report” allows to generate report from each Post Analysis to Excel. It requires that current post analysis configuration in NVGate is configured with reporting to Excel.
* Option “Refresh On Stop” should not be activated in NVGate in order to have a report file for each measurement. Report file could be saved in either Excel or PDF format. If the target file for reporting already exists, it is replaced by this new one.

* Option “Save Log” allows to save a log file from application within NVGate directory.
* Right click on the application background (grey part) offers 3 options:
** Enable/Disable function “Set on top”. By default application remains on top of displayed windows.
** Enlarge “Selection Measurement” display zone in order to display entire name for measurement list.
** Minimize to minimize the application windows.

==Notes==
1) This program is delivered free of charge for NVGate V12.00 and later. Support is not automatically provided on this tool. 

2) For any other requests please contact your local distributor or the OROS Customer Care department.

NVGate Export/import

2020-09-29T13:57:26Z

Yannick Balter: /* Result files */

[[category:NVGate]]

====Export====
[[Image:Reports_Tools_Ribbons_503.jpg|framed|none]]

=====Result files=====
Export results from the project manager to a user specified directory in various data format.

[[Image:Reports_Tools_Ribbons_504.png|framed|none]]

Project: Lists the projects that contain measurements. Only one project can be selected.

Measurement: Lists the measurements in the project selected. Select one or several measurements and click on the add button.

Batch list: Contains all the measurements that will be converted. Use the add/remove button to modify list content.

Format: This is the output format. The formats available are:

{|border="2" cellspacing="0" cellpadding="4" width="84%" align="center"
|Result
|Signal

|-
|Mat: to be used with Matlab
|Mat: to be used with Matlab (max 4.7 Go file)

|-
|Txt: usable by any text or spreadsheet editor
|SDF: Standard data format

|-
|UFF: Universal File Format
|UFF: Universal File Format

|-
| 
|Wav audio: Wav file, re-sampled to standard audio frequency (44.1, 48, 96 kHz) / 16 bit . To be used by any audio player

|-
| 
|Wav: Standard wav format 16 bit, usable with OR2X technology

|-
| 
|Txt: Text usable by any text or spreadsheet editor

|} 

[[NVGate_User_Preferences#Export|''See User preferences- § Export" topic for more details'']]

Output directory: The location on the disk where the files will be exported. During the export, a directory will be created for each project, and will contain the exported files corresponding to all selected measurements.

=====Signals files=====
Export Signal from the project manager records to a user specified directory in various data format.

''See details from previous § Export result files''

====Import====
[[Image:Reports_Tools_Ribbons_505.jpg|framed|none]]

=====Import project=====
This command is used to import project that are not in the project database. It makes a copy of the project and makes it available to the current user, or whoever created the project. If a project already exists in the project base, a <nowiki>~</nowiki> (tilde) will automatically be added.

Directory: Select the directory in which you would like to look for the project. The "found project" list will display all projects that are immediately in the directory selected. If the "scan" button is pressed, all the projects that are contained in the specified directory will be displayed.

Found projects: Displays the list of projects found. Select one or several projects to import.

=====Import Files=====
This command is used to import results or signals. It makes a copy of the file and makes it available to the current user, or whoever created the file. The file will be included in a measurement If a measurement already exists in the project, a <nowiki>~</nowiki> (tilde) will automatically be appended.

[[Image:import.png|framed|none]]

* Destination project: Determines which project will receive the new measurement
* File type: One or several types can be selected. File type may be OR2X or OR3X.
** '''Note :''' Time signal .UFF files needs to have [[NVGate_Front_End#Input_settings|sampling frequency compatible with NVGate Front end]]. WAV signal files does not have this limitation.

* Source: Selects the directory in which you would like to look for the files. The "found files" list will display all the files that are immediately in the directory selected. all the files that are contained in the specified directory will be displayed.
*Filter : filter the list
*Check : you can choose to select all or none.

NVGate FFT

2020-09-29T08:25:44Z

Yannick Balter: /* Display available results */

[[category:NVGate]]
[[Image:Reports_Tools_Ribbons_391.png|framed]]
[[image:ASB_FFT.png|right]]
A spectrum analyzer is an instrument used to characterize signals in the frequency domain. 

Frequency-domain displays show a parameter (usually amplitude) versus frequency. A spectrum analyzer takes an analog input signal (a time domain signal) and converts it to the frequency domain. The resulting spectrum measurement shows the energy of each frequency component at each point along the frequency spectrum. 

FFT spectrum analyzer uses digital signal processing to sample the input signal and convert it to the frequency domain. This conversion is done using the Fast Fourier Transform (FFT), the math algorithm used for transforming data from the time domain to the frequency domain. 

FFT spectrum analyzer is a powerful instrument, since their processing power can extract both magnitude and phase, and can also switch easily between the time and frequency domains. It makes them ideal measuring instrument for acoustic, vibration analysis, measures for audio, electronic, telephone equipments, measures for electricity networks, seismic analysis, control of manufacture and monitoring. 

The NVGate FFT plug-in is used to compute the input signal FFT (you can also compute time signals in post analysis mode with the Player module).
Up to 4 FFT plug-in can be present in the software configuration, each of them running independent analyses on the same or different channels.

==Video tutorial==

<youtube>https://youtu.be/hjdu8OvIMxQ</youtube> 

<youtube>https://youtu.be/UrH9RM57E9k</youtube>

We advise using [[NVGate_Software_overview#GoToResult|GoToResult]] for performing FFT.

==Display available results==
Diplay windows can be done in 2 ways.

*With Add/remove windows
[[Image:FFT_windows.png|framed|none]]

*Using GoToResult windows
[[Image:FFT results.png|framed|none]]
''Note: Zoom windows, Scalar value, cepstrum, enveloppe, orbit are not available using GoToResultWindows, use add/remove windows''

The results available are as follows :
With Resolution being the value of the ''FFT x/FFT analysis/Resolution ''setting
{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''
|'''Option'''

|-
|Filtered signal
|256 pt
|2D
|time
| Display only
| FFT

|-
|Triggered block
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT

|-
|Trigger Shaftview
|(Resolution-1)*2,56
|2D
|Angle
|Yes
| FFT

|-
|DC
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|RMS
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|Min level
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|Max level
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|Peak
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|Peak-Peak
|1pt
|1D
| 
| Yes
| FFT-Diag

|-
|Crest Factor
|1pt
|2D
| 
| Yes
| FFT-Diag

|-
|Avg. block
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT

|-
|Avg. Trigger Shaftview
|(Resolution-1)*2,56
|2D
|angle
|Yes
| FFT

|-
|Weighted block
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT

|-
|Spectrum
|Resolution
|2D
|spectral
| Yes
| FFT

|-
|Inst. spectrum
|Resolution
|2D
|spectral
| Yes
| FFT

|-
|Avg. spectrum
|Resolution
|2D
|spectral
| Yes
| FFT

|-
|Order & Overall
|1 pt
|1D
| 
| Yes
| FFT / CBT

|-
|Inst. cross-spectrum
|Resolution
|2D
|spectral
| Yes
| XFT

|-
|Avg. cross-spectrum
|Resolution
|2D
|spectral
| Yes
| XFT

|-
|FRF H1
|Resolution
|2D
|spectral
| Yes
| XFT

|-
|FRF H2
|Resolution
|2D
|spectral
| Yes
| XFT

|-
|Coherence
|Resolution
|2D
|spectral
| Yes
| XFT

|-
|Order profile
|2048 pt max
|2D
|time
| Display only
| CBT

|-
|Zoomed spectrum
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed avg. spectrum
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Lissajou
|(Resolution-1)*2,56
|2D
|Time Vs. time
| Yes
| FFT

|-
|Zoomed cross spectrum
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed avg. cross spectrum
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed FRF H1
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed FRF H2
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed Coherence
|Resolution
|2D
|spectral
| Yes
| FFT-Diag

|-
|Zoomed Cepstrum
|Resolution
|2D
| 
| Yes
| FFT-Diag

|-
|AutoCorrelation
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|CrossCorrelation
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|Inst.AutoCorr
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|Avg.AutoCorr
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|Inst.CrossCorr
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|Avg.CrossCorr
|(Resolution-1)*2,56
|2D
|time
| Yes
| FFT-Diag

|-
|Cepstrum*
|1/((Resolution-1)*2,56)
|2D 
|Quefrency
|Yes
| FFT-Diag

|-
|InstCepstrum*
|1/((Resolution-1)*2,56)
|2D
|Quefrency
|Yes
| FFT-Diag

|-
|AvgCepstrum*
|1/((Resolution-1)*2,56)
|2D
|Quefrency
|Yes
| FFT-Diag

|-
|ZommedCepstrum*
|1/((Resolution-1)*2,56)
|2D
|Quefrency
|Yes
| FFT-Diag

|-
|Row Orbit
|(Resolution-1)*2,56
|2D
|Time Vs. time
| Yes
| N/A

|-
|Synthetized Orbit
|(Resolution-1)*2,56
|2D
|Time Vs. time
| Yes
| N/A

|} 

* Filtered signal: This result is available if a filter is selected in the FFT x/Channel x/Input filter setting. It displays the input time signal after filtering.
* Triggered block: This displays the signal after being triggered by the event selected with the ''FFT x/Trigger/Trigger ''setting''.''
''Results below are calculated from the triggered block results. The refresh & computation rate depend on the PC to analyzer connection availability (non real-time results)''
* Min level: displays the maximal value of the signal.
* Max level: displays the minimal value of the signal.
* Peak: displays the absolute value of Min level and Max level.
* Peak-Peak: displays the difference between Min level and max level. Peak-Peak level ≥ 0.

[[Image:FFT_02.png|framed|none]]

* Crest factor: displays the ratio Peak level/RMS level. Characteristics of the Crest Factor:
* Crest Factor ≥ 1
* DC level = 1
* Crest Factor of sinus = [[Image:FFT_03.gif]]
* Max level = [[Image:FFT_04.gif]] with N = number of samples in the triggered block = 2.56*lines number-1
* Avg. block: This result is available if the ''FFT x/Average/Domain ''setting value is Time. It the time signal block average.
* Weighted block: This result displays the signal after being weighted by the weighting window selected using the ''FFT x/Channel x/Weighting window'' setting.
* Spectrum: This result is available if the ''FFT x/Average/Domain ''setting value is Time. It displays the result of the FFT processing after time averaging.
* Inst. spectrum: This result is available if the ''FFT x/Average/Domain ''setting value is Spectral. It displays the FFT processing results.
* Avg. spectrum: This result is available if the ''FFT x/Average/Domain ''setting value is Spectral. It displays the instant spectrum average result.
* Order & Overall: It displays the result of the computation of the orders chosen with the ''FFT x/Channel x/Tracked order'' setting and the Overall level if the ''FFT x/Overall Analysis/Band power tracking '' is set to On.
* Inst. cross-spectrum: This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the cross spectrum between the 2 channels selected.
* Avg. cross-spectrum: This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the instant cross spectrum average results.
* FRF H1: This result is not available if there is no cell checked in the matrix of the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the Frequency Response Function H1, see Appendix for details.
* FRF H2: This result is not available if there is no cell checked in ''FFT x/FFT analysis/Cross spectrum ''setting. It displays the Frequency Response Function H2, see Appendix for details.
* Coherence: This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the H1/H2 ratio.
* Order profile: It displays changes in the Order & Overall result.
* AutoCorrelation: This result is available if correlation is selected in ''the FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Time.
* CrossCorrelation: This result is available if correlation is selected in ''the FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Time. This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix
* Inst. AutoCorr: This result is available if correlation is selected in ''the FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Spectral or Frequency synchronous.
* Avg. AutoCorr: This result is available if correlation is selected in ''the'' ''FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Spectral or Frequency synchronous.
* Inst. CrossCorr: This result is available if correlation is selected in ''the FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Spectral or Frequency synchronous. This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix
* Avg. CrossCorr: This result is available if correlation is selected in ''the'' ''FFT x/Correlation ''and ''FFT x/Average/Domain ''setting value is Spectral or Frequency synchronous. This result is not available if there is no cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix
* Zoomed spectrum: This result is available when the value of the ''FFT x/FFT zoom/Factor ''setting is different from None. It displays the FFT zoomed signal processing result. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''settings respectively.
* Zoomed avg. spectrum: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None. It displays the zoom spectrum average result. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting respectively.
* Lissajous: This result simultaneously displays the value of the channel chosen on the Y axis and the value of the reference channel on the X axis at the same time.
* Cepstrum: This result is always available. X scale is in quefrency (time equivalent) and Y scale is always in dB.
Cepstrum analysis can be used as a tool for the detection of periodicity in a spectrum, for examples families of harmonics with uniform spacing.

A high quefrency represents rapid fluctuations in the spectrum (small frequency spacings) and a low quefrency represents slow changes with quefrency (large frequency spacings). Note that the quefrency does not give information regarding absolute frequency, only about frequency spacings.

* Zoomed cross-spectrum: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None and if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the zoomed cross spectrum between the two channels selected. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting, respectively.
* Zoomed avg. cross-spectrum: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None and if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the zoomed cross spectrum average result. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting, respectively.
* Zoomed FRF H1: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None and if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the zoomed Frequency Response Function H1, see Appendix for details. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting, respectively.
* Zoomed FRF H2: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None and if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the zoomed Frequency Response Function H2, see Appendix for details. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting, respectively.
* Zoomed Coherence: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None and if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. It displays the zoomed H1/H2 ratio results. The minimum and maximum of the X axis are the values of the ''FFT x/FFT zoom/Min freq ''setting and ''FFT x/FFT zoom/Max freq ''setting, respectively.
* Zoomed Cepstrum: This result is available when the ''FFT x/FFT zoom/Factor value ''setting is different from None. It displays the zoomed cepstrum.
'''Computation SPUs:'''

{|border="2" cellspacing="0" cellpadding="4" width="85%" align="center"
|Bandwidth
|Fdec
|Resolution
|Envelope
|Zoom
|SPU/Channel for Real-time
|SPU/Channel for non Real-time

|-
|20k
|1
|401
|No
|No
|1
|0,5

|-
|10k
|1
|401
|No
|No
|0,5
|0,25

|-
|Nk
|1
|401
|No
|No
|=N/20
|=N/40

|-
|10k
|2
|401
|No
|No
|1
|1

|-
|5k
|4
|401
|No
|No
|0,8
|0,6

|-
|2k
|10
|401
|No
|No
|0,6
|0,6

|-
|1k
|20
|401
|No
|No
|0,5
|0,6

|-
|Lower than 1k
|Higher than 20
|401
|No
|No
|0,5
|0,5

|-
|20k
|1
|401 and below
|No
|No
|1
|0,5

|-
|20k
|1
|801
|No
|No
|1,25
|0,5

|-
|20k
|1
|1601
|No
|No
|1,5
|0,5

|-
|20k
|1
|3201
|No
|No
|2
|0,5

|-
|20k
|1
|6401
|No
|No
|3
|0,5

|-
|20k
|1
|401
|No
|No
|1
|0,5

|-
|20k
|1
|401
|No
|Yes
|2
|1,5

|-
|20k
|1
|401
|No
|No
|1
|0,5

|-
|20k
|1
|401
|Yes
|Yes
|3
|3

|} 

[[Image:fft_sampling.png|500px|none]]

==Settings==
There are sevral ways to access the settings :
We advise the first one.
{| class="wikitable"
|-
! GoToResults !! ASB(Analyzer Setting Browser) !!Ribbon !! double click on FFT windows !!
|-
| [[image:FFT_results2.png|none]] || [[image:ASB_FFT2.png|framed|none]] || [[Image:Reports_Tools_Ribbons_391.png|framed|none|NVGate ribbon - tab:analysis]]Note: Clicking on the bottom right icon ([[Image:Reports_Tools_Ribbons_392.png]]) open the FFTx plug-in properties dialog allowing a full access to all the settings. || [[image:FFT double.png|framed|none]]||
|-
|}
===Channel===
Contains the settings related to the source input.

* '''Source''': input source to be analyzed. It may come from the input Front-end or from the Player in the post analysis mode (see the post analysis chapter). In the post analysis mode, the tracks with a signal bandwidth lower than the range of the FFT cannot be plugged.
* '''Input filter''': filter to be used for filtering the source before analysis. The Filters that are not compatible with the FFT range cannot be selected (see the Filter builder chapter). The A and C weighting on time domain are available in the NVGate® filter list.

These acoustics filters can be applied as all other NVGate® filters pass/stop band, high/low pass, and integrators.

Note: These weighting on time domain are no longer available for pass band higher than 25.6kHz and lower than 10kHz.

For filter characteristics, see the Appendix.

* '''Tracked order''': orders to be tracked with the FFT Constant Band Tracking mode. Up to 8 different orders may be selected for each channel, and there are three settings for each order:
*
[[Image:FFT_01.png|framed|none]]

'''State''': ON if you want the order to be computed
* '''Order number''': Select the number of the order you want to track, from 0.001 up to 800.
* '''Bandwidth''': Select the bandwidth used to compute the energy of the order from ''3*FrequencyRange/(NumberOfLine-1)'' up to ''FrequencyRange'' with ''FrequencyRange'' being the value of the setting Range from the FFT analysis sub-module, and ''NumberOfLines'' being the value of the Resolution setting from the FFT analysis sub-module.
* '''[https://en.wikipedia.org/wiki/Window_function Weighting window]''': window used to weighting the signal before the processing. There are six set windows: Uniform, Hanning, Hamming, Kaiser Bessel, Flat top, [[NVGate_Time_windows|and three customized windows: Force, Response and Dual exp (see the Time Windows chapter]]). [[NVGate_Weighting_Windows_appendix|For the window characteristics, see the Appendix.]]

===Trigger===
Contains the settings related to trigger events and how to start, and stop signal computation.

* '''Start''': defines the event to start the analysis. The user can choose any event among the list of defined events. By default only the Free run and Manual events are available. The user can define another event in the "Event Definition" shared resources and then use this event for the "Start" condition.
* '''Stop''': defines the event to stop the analysis. The user can choose any event among the list of defined events. By default only the Free run and Manual events are available. The user can define another event in the "Event Definition" shared resources and then use this event for the "Stop" condition.
* '''Trigger''': defines an event to compute the FFT on one block of time signal. After the computation, the plug-in waits for a new event to compute another block.
* '''Repeat''': this setting is used to select a condition for the plug-in to be restarted. If an event is selected as a Start event, the option "New start" is available, and when this mode is selected each Start event restarts the plug-in. The "End of averaging" mode is available when the value of the ''FFT x/Average/Type ''setting is different than "Exponential" mode. This restarts the plug-in when the averaging is finished. For linear average when it is set to "End of averaging", the "Avg duration" gives the periodicity of the average restart. By default the Repeat mode is set to "Off".
The following scheme describes the repeat mode for the FFT analysis:

[[Image:FFT_06.png|framed|none]]

The <nowiki>’</nowiki>Run<nowiki>’</nowiki> corresponds to the start of the analyzer. The start is the beginning of average duration. At the end of the first average, the second average will start and so on till the end of the integration time (even if the last short time integration duration is not over). Each averaging has the same size, except the last that can be smaller.

- Mode Repeat on <nowiki>’</nowiki>New start<nowiki>’</nowiki>:


[[Image:FFT_07.png|framed|none]]

The <nowiki>’</nowiki>Run<nowiki>’</nowiki> triggers the analyzer, but the average begins at the start event (set in the event definition). This averaging stops at the end of average duration or at the stop event. Then the next averaging is waiting for the new start event to occur.

In case a new event occurs during a previous averaging, this start event won<nowiki>’</nowiki>t be effective because the previous average duration is not over, you can only set other event after the end of the previous one.

* '''Start delay''': time delay applied to the time the start event occurs, or block percentage delay. The delay in percentage is calculated as: '''Start delay in % = <nowiki>[</nowiki>(Start delay in s) / (Block duration)<nowiki>]</nowiki> * 100 '''This value of start delay can be negative and also greater than 100 %. Note: some settings (bandwidth, number of lines) are directly linked with the start delay, then by modifying any of these settings the last Start delay modified (time or %) would be fixed, and the other one will be automatically sets regarding modified settings.
* '''Accept mode''': used to select the method for rejecting signal blocks.

{|border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
|'''Mode'''
|'''Description'''

|-
|Normal
|All the blocks are accepted

|-
|Manual
|After the computation of each block, the plug-in is in the Waiting mode and waits for the user to push the accept or reject button

|-
|Overload rejection
|Blocks with an overload are automatically rejected

|} 

* '''Trigger Frequency: '''Adjust the synchronous frequency (for Frequency Domain Synchronous Analysis).
''Hidden/fixed: The Trigger frequency is enabled when FFTx/Average/Domain is set to Frequency Synchronous.''

===Average===

See also : [[User_note:_FFT_averaging|User note about FFT averaging.]] 

Contains the settings related to the type of averaging of the signals to be computed.

* '''Domain''': You can choose between Spectral, Time or Frequency Synchronous.

{|border="2" cellspacing="0" cellpadding="4" width="94%"
|'''Domain'''
|'''Description'''

|-
|Spectral
|Calculates the average after FFT processing,

|-
|Time
|Calculates the average before FFT processing.

|-
|Frequency Synchronous
|Frequency domain Synchronous averaging (FDSA) uses one frequency band as the phase reference, and each FFT block is recomputed so that the phase of the frequency chosen with the ''FFT x/FFT analysis/Trigger Frequency ''setting is 0. Enables the Trigger frequency setting to be adjusted from ''FFTx/Trigger/Trigger frequency''.

|}

* '''Size''': The number of signal blocks used to compute the average, from 1 up to 1000000000.
* '''Duration''': The duration of the signal used to compute the average. This depends on four other settings: Size from the same sub-module, and Range Overlap and Resolution from the FFT Analysis sub-module. BlockDuration = (NumberOfLines-1)/FrequencyRange

'''Duration = BlockDuration * (Size - (Size-1)*Overlap)'''

With BlockDuration being the duration of one block of signal, NumberOfLines being the value of the setting Resolution from the FFT analysis sub-module, FrequencyRange being the value of the setting Range from the FFT analysis sub-module, Size being the value of the setting Size from the same sub-module and Overlap being the value of the setting Overlap from the FFT analysis sub-module.

The average duration disappears when the trigger of the FFT is changed from "Free Run" to a different trigger (Manual, Ext.Sync., Delta RPM,…) as the elapsed time between two triggering is not predictable anymore."

* '''Type''': The method of averaging the signal. There are four different averaging modes: Linear, Exponential, Peak hold, and Referenced Peak hold.

{|border="2" cellspacing="0" cellpadding="4" width="94%" align="center"
|'''Type'''
|'''Description'''

|-
|Linear
|Linear averaging of results is carried out on the value of the Size setting from the same sub-module. The FFT plug-in automatically stops when the given number of averages is reached.

|-
|Exponential
|In this mode of computation, each new average is obtained by adding its previous value and the new FFT result divided by the value of the Size setting, and then subtracting its previous value divided by the value of the Size setting.

|-
|Peak hold
|This method processes the peaks found in their spectrum power density for each channel, and for a number of FFT analysis given by the value of the Size setting. The FFT plug-in automatically stops when a given number of averages is reached. For each frequency line, each time the value of the instantaneous spectrum is greater than the value of the averaged spectrum, the averaged spectrum value becomes equal to the instantaneous spectrum value. Otherwise, the average spectrum value is not modified. Note: in this case averaged spectrum doesn<nowiki>’</nowiki>t mean average value but hold value.

|-
|Referenced Peak hold
|
[[Image:FFT_08_436.png|framed|none]]
 This method processes the peaks found in their spectrum power density for each channel, and for a number of FFT analyses determined by the size setting. The FFT plug-in automatically stops when a given number of averages is reached. When this mode is selected, a new setting called Reference channel appears in the same sub-module; if None is selected, the average processing is the same as the Peak hold mode. If a channel is selected, then there are two different behaviors depending on the channel: For the reference channel: For each frequency line, each time the value of the instantaneous spectrum is greater than the value of the average spectrum, the average spectrum value is equal to the instantaneous spectrum value. Otherwise, the average reference spectrum value is not modified. For the other channels: For each frequency line, for each modification of the average reference spectrum, the average channel spectrum is equal to the instantaneous channel spectrum values, even if it is less than the average spectrum value. The modification of the reference and the other channels is synchronized. In this example, the modified spectrum lines are between '''A''' and '''B''' for both reference channel and response channel. The spectrum lines between '''B''' and '''D''' in the response channel are not updated. The modification of the reference and response channels is synchronized Each time the peak value of the reference channel has been modified, the '''averaged cross spectrum''' is equal to the instantaneous reference spectrum by the response spectrum product. In this example, the modified spectrum lines are between '''A''' and '''B'''. The functions as transfer function (where the reference channel is taken into account) will be modified between '''A''' and '''B'''.

|} 

''Hidden/fixed: Peak hold and Referenced Peak hold are only available if the Domain setting from the same sub-module is set to Spectral.''

* '''Reference channel''': channel to be used as a reference in the Referenced Peak hold averaging mode. This setting is only available when this averaging mode is selected. You can choose between the channels that are plugged into the FFT plug-in, if <nowiki>’</nowiki>None<nowiki>’</nowiki> is selected the average processing is the same as the Peak hold mode.

===FFT analysis===
Contains the settings related to the type of analysis of the signals to be computed.

* '''Range''': the FFT plug-in frequency range. The analyzer sampling frequency divided by 2.56 limits this range, and the minimum is obtained by dividing this limit by 50000. For example, if the analyzer sampling frequency is 51,2kS/s, then the max range is 20 kHz and the min is 400mHz. In post analysis mode, the Max Bandwidth setting from the Player plug-in provides the analyzer sampling frequency by multiplying the value by 2.56 (ex: if max bandwidth = 20 kHz then the analyzer sampling frequency is 51.2kS/s), otherwise, the analyzer sampling frequency is provided by the input sampling setting from the Front end plug-in input setting sub-module.
* '''Resolution:''' This is a fixed setting, for information only. It displays the frequency span between two points of a spectral result. The FFT resolution is obtained by dividing the FFT frequency range by the resolution minus 1. For example if the FFT Range is 20 kHz and the resolution is 401 lines, then the frequency span is: 20000 / (401 - 1) = 20000 / 400 = 50Hz.
* '''Overlap''': Defines the amount of overlap of input signals between two successive FFT computations, from 0% to 99.99%.
* '''Number of lines''': The FFT number of analyzed lines. There are seven possibilities: 101, 201, 401, 801, 1601, 3201 or 6401 lines.
* '''Trigger Frequency:''' This setting is only available when the ''FFT x/Average/Domain ''setting is "Synchronous". The value can be chosen from the FFT Frequency range; this frequency is the phase reference: each FFT block is recomputed so that the phase of the frequency chosen is 0.
* '''Reverse cross function:''' this setting allows calculating the cross function of the greyed part of the Cross spectrum setting. Default value is True except on cascaded mode (multiple hardware) as the number of reference spectrum to be carried between the analyzers may lead to a dramatic loss of performances.
* '''Cross spectrum''': Matrix used for the selection of the computed cross spectra, Only the upper half of the matrix can be used, because when a box is checked, two cross spectra are computed with each of both channels being the reference. Selecting the cross spectra is necessary to have access to some results: instant cross spectrum, average cross spectrum, FRF H1, FRF H2 and coherence.

* '''Autobandwidth''': manages the analysis and recording bandwidths automatically. The ''Inputs selection'' window '''allows the use of 2 different sampling rates for the dynamic inputs'''. It gathers inputs with the same physical quantity into groups, maintaining the same sampling into each group. When inputs are associated with '''the analysis plug-in, it adjusts its analysis bandwidth to match the inputs ones'''. Mixing input bandwidths in one analysis plug-in lead to set its bandwidth to the lowest one. ''Autobandwidth'' is set by default in the FFT plug-ins. it adjusts the setting : FFT Analysis\Range .When it is enabled in the plug-in, these settings "switch to informative status"

===FFT zoom===
Unlike the display zoom function; the analysis zoom function allows you to zoom into a selected bandwidth increasing the analysis resolution.

[[Image:FFT_09.png|framed|none]]

* '''Factor''': Switch the FFT zoom on or off depending on its value. If the value is "None" there is no zoom result available. There are seven possible factors: x2, x4, x8, x16, x32, x64, x128. The value stands for the dividing factor to be used to obtain the frequency span of the zoom results. For example, if the FFT resolution is 401 lines and the Frequency range is 20kHz then the frequency span is 50Hz. If the zoom is activated with a x4 factor, the frequency span of the zoom results is 50 / 4 = 12,5Hz. The zoom results are Zoomed Spectrum, Zoomed Average Spectrum, and Zoomed cross spectrum, Zoomed Avrg cross spectrum, Zoomed FRF H1, Zoomed FRF H2, Zoomed Triggered Block and Zoomed Coherence if there is at least one cell checked in the ''FFT x/FFT analysis/Cross spectrum ''matrix. These results are available when the Factor is different from the None value.
* '''Center''': The center frequency of the zoom. The value can be set directly, or automatically by changing the Min Frequency or the Max frequency settings.
* '''Min freq''': The minimum frequency of the zoom. The value can be set directly, or automatically by changing the Center or Factor settings to match them.
* '''Max freq''': The maximum frequency of the zoom. The value can be set directly, or automatically by changing the Center or the Factor settings to match them.
'''Note''':''' '''These zoom settings are working as following:

* Set '''Factor''' and '''Center''' (min and max values are update automatically with the center frequency) if the zoom would be done around a central frequency well defined. By modifying Factor, max and min frequencies will be automatically set to define zoom limits.
* Set '''max''' and '''min''' frequencies (center and factor are update automatically) if the limits in frequency would be fixed on specific values.
====Envelope====
[[NVGate_Envelope_analysis|Read the user note for more info about envelope analysis.]]

FFT plug-in integrates as a standard an amplitude demodulation analysis that provides envelope results. Even demodulated time domain signal and envelope spectra can be handled for real time display, result saving and report generation.
Envelope demodulation is linked to the FFT zoom activation. When FFT zoom is different from none, the envelope demodulation can be activated through a simple click.

Then the envelope limits (range, modulating, frequency) are set by the zoom settings. It is then possible to get simultaneously the entire spectral and time information with the following displays:


[[Image:envelope.png|framed|none]]


''Hidden/fixed: The envelope is available only if the zoom is active.''

'''Note:''' All frequency setting, such as FFT zoom boundaries, start and stop sweep sine, filter limits, etc… can be directly controlled from a display. This is easily achieved by drag and drops the corresponding setting inside a compatible (with X-axis as frequency) graph.

[[Image:FFT_11.png|framed|none]]

As an example (see fig below) you can easily focus on spectra area using the zoom center setting as a cursor in the wideband FFT spectra. Then it is efficient to move the center of the FFT zoom from one peak to the order as a cursor. In cab also be useful to control pass-band filter limits, directly from the corresponding spectra. Try it when you use the monitor filter scalar values.

===CBT: Order analysis===
[[NVGate_CBT_principle_and_settings|Read the dedicated CBT page for more info.]] 

Contains the settings related to constant band tracking operations.

[[Image:Order_analysis_03.png|framed|none]]

* '''Associated tach''': The selected Tach enables the FFT plug-in to perform Constant Band Tracking.
'''Warning''': Do not select an associated tach if you do not use one, the FFT will not start.

* '''Center on peak''': This setting is used to center the spectral lines used to compute the total power around a peak (if it exists) close to the order frequency.
* '''Refresh mode''': When displaying some order profile results, this setting is used to choose between two methods of adding a new measurement point to the curve.
*

{|border="2" cellspacing="0" cellpadding="4" width="92%" align="center"
|'''Mode'''
|'''Description'''

|-
|Delta time
|A new point is added periodically. The Time Resolution settings set the refreshing period.

|-
|Delta RPM
|A new point is added each time the Tach speed has increased the Speed Resolution setting value.

|} 

* '''Duration profile''': The size of the profile window time axis.
* '''Time resolution''': used to set the refreshing period for the order profile results. This setting is visible if the Refresh Mode setting value is Delta time.
* '''Max speed''': The Max speed that the Tach selected with the Associated Tach setting can handle. This value is for information only; it cannot be set directly. This setting is visible if the Refresh Mode setting value is Delta RPM.
* '''Min speed''': The Min speed that the Tach selected with the Associated Tach setting can handle. This value is for information only; it cannot be set directly. This setting is visible if the Refresh Mode setting value is Delta RPM.
* '''Speed resolution''': used to set the refreshing conditions for the order profile results. A new point is added each time the Tach speed has increased of the setting value. This setting is visible if the Refresh Mode setting value is Delta RPM.
* '''Orders Phase ref''': This function allows to use the cross-spectrum phase value for the phase of the order (relative phase). The cross-spectrum phase is the relative phase between the input signal of the current channel and the reference input signal associated to this channel. Whatever the average mode, the average cross-spectrum is always used to calculate the orders phase.

[[Image:Order_analysis_04.png|framed|none]]

'''- Not activated''': The phase of the order is the spectrum phase of the frequency corresponding to the order value (absolute phase). If the average mode is spectral, the inst-spectrum is used and if the average mode is time, the average spectrum is used.

- '''Activated''': choose the channel used to calculate the orders phase.

If a channel is selected, the cross-spectrum matrix is not available anymore.

'''Note''': This set up don<nowiki>’</nowiki>t change the spectrum phases and consequently don<nowiki>’</nowiki>t change the orders phases extracted from a waterfall of spectra.

===Correlation===
Calculation of the Auto Correlation and the Cross Correlation.
[[File:Correlation2.png|left]] 
 
 
 
 
 
 

* '''Correlation: '''Allows to activate or not the calculation of the correlation.
All results of the correlation are in the time domain with –T/2 et T/2 where T equal to the duration of the block trigger of the FFT.

* '''Weighting window: '''Choose between following values of this setting:
Three types of correlation window are available:

'''Uniform '''<nowiki>[</nowiki>-T/2, T/2<nowiki>]</nowiki> (where T is the trigger block length): All the window coefficients are equal to 1. For best results with the Uniform weight window, you should use signal sources that are self-windowing, such as transients, burst, and periodic waveforms (signal period must be a multiple of the weight window length). In order to have the trigger point (T0) at the center of the time trigger block, the trigger Delay must be set to –T/2'''.'''

[[Image:Order_analysis_11.png|framed|none]]

'''Centered Zero Padding '''<nowiki>[</nowiki>-T/4, T/4<nowiki>]</nowiki> (where T is the trigger block length): Only the central part of the window (representing the half-length) is not null. This weight window must be used with random noise. In order to have the trigger point (T0) at the center of the time trigger block, '''the trigger Delay must be set to –T/4 '''(where T is the trigger block length)


[[Image:Order_analysis_12.png|framed|none]]


'''Left Zero Padding''' <nowiki>[</nowiki>0, T/2<nowiki>]</nowiki> (where T is the trigger block length): Only the first half of the window is not null. This weight window must be used with random noise. In order to have the trigger point (T0) at the beginning of the time trigger block, '''the trigger Delay must be set to 0.'''


[[Image:Order_analysis_13.png|framed|none]]



If the correlation is activated then all results of the FFT will be affected by the weighting windows of the correlation. When the setting Correlation is deactivated the weighting windows by default (Hanning) is applied on all inputs of the FFT plug-in.

Notes: Results from the correlation are normalized.

'''Considerations to obtain good results when making correlation measurement.'''

* Use input '''AC '''coupling. Both auto correlation and cross correlation are disturbed by DC offset in the input signal.
* Use appropriate trigger mode and trigger delay. The trigger mode should be different from free run. The trigger Delay must be set to –T/2 (where T is the time signal block length) with the Uniform and Centered Zero Padding correlation weighted window (and 0 for the Left Zero Padding window). But in some cases, especially with the Centered Zero Padding and Left Zero Padding window (as these function types attenuate parts of the trigger signal block), the trigger Delay must be adjusted to position the input signal with respect to time.

===Overall analysis===
Calculation of the FFT bands sum.

* '''Band power tracking''': Switches computation of the overall level result on or off.
* '''Lower frequency''': Specifies the lower frequency of the overall computation frequency range.
* '''Upper frequency''': Specifies the upper frequency of the overall computation frequency range.

==FFT status==
All status are available for the control panel. Statuses are refreshed all the time at roughly 10 Hz.

[[Image:Order_analysis_14.png|framed|none]]

The current plug-in status is synthesized in a special progress-bar. This progress bar is automatically displayed in the <nowiki>’</nowiki>control panel<nowiki>’</nowiki> when the plug-in is active (i.e. as soon as at least 1 input is connected to the FFT plug-in). This status is called <nowiki>’</nowiki>FFTx<nowiki>’</nowiki> (x from 1 to 4) and it is available in the status ASB tree (see customize control panel).

This status displays the averaging count (i.e. current analyzed block number), the plug-in state and the real-time status.

* '''State''': block number analyzed
* '''Run:''' The FFT plug-in is computing spectra and averaging it.
* '''Stop:''' The FFT plug-in is stopped.
* '''Trig:''' The FFT plug-in is waiting for next block; i.e. next trigger event (block triggering) or first start event (triggering)
* '''Pause: '''The FFT plug-in averaging is paused
* '''Waiting:''' The FFT plug-in averaging is waiting for the acquisition to be accepted or rejected (in structural mode).

'''Notes''': in exponential averaging mode the average counts stops increasing as soon as the set value is reached.

The way the status bar is displayed, depends on the type of averaging selected:

* '''<nowiki>’</nowiki>Linear<nowiki>’</nowiki>''', '''<nowiki>’</nowiki>Peak hold<nowiki>’</nowiki> '''or '''<nowiki>’</nowiki>Ref peak hold<nowiki>’</nowiki>: '''the progress bar is filled from left to right.
* '''<nowiki>’</nowiki>Exponential<nowiki>’</nowiki>''': the progress bar is filled from right to left with a flashing until the end of the acquisition.

The color of the background bar and of the text depends on real-time status:

* ''Green background and white or black text'': acquisition in real-time.
* ''Red background and white or black text'': the current acquisition is not real-time (current block is not analyzed).
* ''Green background and red text'': the current acquisition is real-time, but since start not all the blocks were analyzed.
* Triggering: displays the state of the triggering in percentage before acquiring.
* Acquiring: displays the progression of the time block acquisition in percentage. Until the acquiring period is not finished, the corresponding results are not available; they will be displayed at the end of the acquisition.
* Paused: the acquisition is paused
* Stop: the acquisition is stopped

Trigger State

The following scheme describes the basic statuses evolution of the FFT measurement:

[[Image:Order_analysis_17.png|framed|none]]

By default the trigger state is on <nowiki>’</nowiki>Stop<nowiki>’</nowiki> and waiting for a <nowiki>’</nowiki>Run<nowiki>’</nowiki> (start or trigger). Then the state become <nowiki>’</nowiki>Triggering<nowiki>’</nowiki> and is waiting for a start event, the states become <nowiki>’</nowiki>Block Triggering<nowiki>’</nowiki> and is now waiting for a trigger event for being in the <nowiki>’</nowiki>Running state. If there is less than one second elapsed since the end of current block analysis, FFT status stay at "running" state.

The status is <nowiki>’</nowiki>Stop<nowiki>’</nowiki> after a stop event or at the end of averaging.

In structural mode, a state <nowiki>’</nowiki>Waiting<nowiki>’</nowiki> is available and is waiting for the <nowiki>’</nowiki>Accept/Reject<nowiki>’</nowiki> event to continue.

====Count====
This status displays the averaging count processed. This status is expressed in analyzed block.

====Real-time====
This status displays if the averaging is in real-time or not (i.e. the current block is analyzed or not). If the corresponding signal were not available at this time, the acquisition is not real-time. That means that the treatment is longer than the acquisition. There are three values for this state:

* '''<nowiki>’</nowiki>OK<nowiki>’</nowiki>''': The acquisition is real-time (all block have been processed and averaged)
* '''<nowiki>’</nowiki>No<nowiki>’</nowiki>''': Acquisition was not real-time (some previous blocks are missing in the average).
* '''<nowiki>’</nowiki>-<nowiki>’</nowiki>''': The acquisition is currently not real-time (current block is not analyzed an averaged).

====Block overload====
This status corresponds to the instantaneous overload indication within 1 FFT trigger block, for instance amplitude overload occurred in the current analyzed block. It is useful in structural mode if for one hammer impact one channel is overloaded. Note that overloaded block may be automatically rejected (see accept mode).

====Analysis overload====
This status corresponds to overload indication over the measurement period. It means that during the whole measurement period there was (or not) an overload. It memorizes block overloaded.

NVGate User Preferences

2020-08-25T06:52:20Z

Yannick Balter: /* Wav (audio) */

'''User preferences'''

===Introduction===
The user preferences allow modifying and saving your preferred usages for future uses. NVGate propose to share the software use (from a unique PC) between multiple users allowing them to recall their preferences

The user preferences are saved in the user file (.usr).

Users preferences are accessible from the ''Home'' tab/ ''Preferences'' group

===General===
This page is dedicated to general NVGate setting.

[[Image:preference2.png|framed|none]]

* '''Default project:''' When this option is selected, a new project called "Default project" is created when NVGate is launched.
* '''Last project''': When this option is selected, the last project used is loaded when NVGate is launched.
* '''Default Model''': This command is only available when the option "Start with default project" is selected. When this option is selected, the new project will be empty and all settings take their default values.
* '''Specific Model: '''This command is only available when the option "Start with default project" is selected. In this case, the new project is created using a workbook model from the library (using <nowiki>'</nowiki>Load Model<nowiki>'</nowiki>). Use this option to create a project with some default settings and displays specific to your needs.
* '''Skip identification:''' This option bypasses user identification prompt. When selected, the last user is automatically selected. This will not work if the user has a password.
* '''Play sound:''' Option to produce a sound when a warning or an error is received.

'''Note''': Your computer must have speakers for this option.

* '''Windows refresh rate:''' Used to slow down the window refresh rate. This option should be modified only for heavy configurations or when the host computer has a slow processor.
* '''Scale: '''Modifies the graph scale font size.
* '''Infotrace: '''Modifies the Infotrace graph font size.
* '''Change of analyzer setting: '''When an important setting is modified while the Analyzer is running, a message informs the user that this modification will stop the current analysis.
* '''Auto-save configuration: '''Define the periodicity of the current setup automatic saving in minutes. In case of abnormal termination, NVGate will propose to recover the last saved setup. Attention if a large signal file is loaded in the player, a copy of this file will be saved periodically. Thus may lead to short freezes of the software and large disk space use.
* '''Specialized mode: '''choose between <nowiki>'</nowiki>structural<nowiki>'</nowiki> (this mode is dedicated to the acquisition of modal data (through hammer acquisition or signals provided by up to 6 shakers) or <nowiki>'</nowiki>rotating<nowiki>'</nowiki> (this mode is dedicated to rotating and reciprocating machines).
* '''date format''' can be forced to the month/day/year with 2 digits each or matches the regional windows settings. Selecting mm/dd/yy makes date sorting easier.
[[Image:Project_Manager_User_Pref2_75.png|framed|none]]

Select this option to block this message.

For users that selected the date as the measurement name auto increment, a choice of date format

===Project manager===
This preference page is used to configure the project manager.

[[Image:Project_Manager_User_Pref2_76.png|framed|none]]

=====Project manager options=====
* '''Only my projects:''' When this option is selected, only the projects that belong to the current user are displayed. This can be useful when NVGate is used by many users.
* '''All user projects:''' When this option is selected, the projects that belong to all users are displayed. This can be used to share data or set-ups between different users.
* '''Sort:''' The projects can be displayed in three different ways in the project manager:

{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center"
|'''Alphabetical'''
|The projects are classified by their name

|-
|'''Latest to oldest'''
|The projects are classified by date created, with the newest project being at the top of the project manager

|-
|'''Oldest to latest'''
|The projects are classified by date created, with the newest project being at the bottom of the project manager

|} 

=====Measurements displayed=====
* '''All:''' all measurements are displayed even the measurements that do not belong to the current user.
* '''Filtered by keyword:''' the measurement can be filtered by keyword. The keywords are assigned to the measurement when it is created, or can be changed in measurement properties. This option is very helpful when organizing measurement campaigns.

=====General=====
It is possible to hide all the inactive workbooks and to delete the measurement level. The table below illustrates the differences

[[Image:Project_Manager_User_Pref2_77.png|framed|none]]

=====New project=====
This option sets the default protection that will be applied to a new project. This protection can be modified later via the project properties.

* '''Read-only to all other users: '''he current user does not want to allow other users to modify his projects. Other users can load the project, but will not be allowed to modify it.
* '''No protection: '''Any user can freely modify the current user<nowiki>'</nowiki>s project.

----

===Save===

[[Image:Project_Manager_User_Pref2_78.png|framed|none]]

=====New measurement=====
* '''Save option: '''This option determines the way in which the measurement will be created when the analyzer stops

{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center"
|'''Do not save'''
|No measurement will be created. The only way to save the results selected is to perform the Save Result command manually

|-
|'''In default measurement'''
|The measurement is created with the name "Default measurement". If a measurement with this name already exists, it is overwritten.

|-
|'''With name confirmation'''
|A dialog box will be displayed when the analyzer stops. It will suggest a name using a Base name and an auto increment choice.

|-
|'''Without name confirmation'''
|The measurement is created with a name automatically generated from the Base name and the auto increment choice.

|} 

* '''Default keyword: '''Used to choose the keyword that will be associated with the new measurement. Refer to the preference section for more information.
* '''Automatic generation of results layouts:''' by checking this box, measurement will be saved with the corresponding layout and when this measurement will be open it will be possible to modify the current layout.

=====Saved Results=====

* '''Current Analysis result: '''Results obtained from an acquisition'''.'''
* End of acquisition: open automatically a dialog box to save the results when the analyzer stops.
* Manually: allow to save the results manually.
* '''Working results: '''Results obtained after an operation based on already saved results, for example a result calculated with an operator, or the computation of results from an edidted measurement such as FRF H2 from a saved H1. These results can be only saved manually.

'''Default: '''set all the parameters to their default values'''.'''

===Waterfall ===
This preference page is dedicated to Waterfall window configuration. Settings specific to the type of result can be modified in the graph preference page.

[[Image:Project_Manager_User_Pref2_04.png|framed|none]]

* '''Display style'''
Used to select the Waterfall 3D view style. Three display styles are available:

* Line display: in this mode, each spectrum or block is displayed with a filled plane surface defined by the spectrum points. The fill color is the selected color for single color field.
* If Waterfall color is activated, the current palette is used to compute the color of the points and an interpolation is used to display the spectrum. If not, the spectrum is black.
* Point display: in this mode, only points are displayed. There are no links between them. This mode is useful for small computer configurations or for large Waterfalls with many points or a large depth. If the Waterfall color is activated, the current palette is used to compute the point color. If not, the points get the selected signal color.
* Solid display: this is a colored mode: it displays the Waterfall with interpolation between the points of each spectrum and between two consecutive points with the same x value. This mode is the same one used for the color spectrum view.
* '''Scrolling'''
Used to select the scrolling direction. Two are available:

* '''Front to back:''' the Waterfall is filled from front to back of the displayed box.
* '''Back to front''': the Waterfall is filled from back to front of the displayed box.
* '''Color palette'''
Used to select the color mode used for 3D Waterfall displays. Two modes are available:

* '''Single color:''' no color interpolation is used for the points. This color is used for filling the plane in Line mode.
* '''Waterfall color:''' if checked, the selected palette is used for the color rendering and for the color spectrogram mode. The edit button displays the palette manager dialog box.

'''Palette manager'''

This dialog box is used to create and edit color palette.

[[Image:Project_Manager_User_Pref2_79.png|framed|none]]

'''Palette'''

'''Create''': Creates a new palette.

'''Remove''': Removes the selected palette.

'''Color'''

'''Add''': Adds a key color to the palette.

'''Remove''': Removes the selected key color from the palette.

'''Up''': The selected key color move up from one step, if possible.

'''Down''': The selected key color move down from one step, if possible.

Each color of the palette can be edited by clicking on a colored area. The percentage can also be edited by double-clicking on the text zone of each color.

* '''Z autoscale'''
Used to select an autoscale type. Two kinds are available:

* Disable: no autoscale is activated.
* Continuous: when a spectrum is not within the Z scale values, an autoscale is performed with no margin. This mode is not recommended for computers with limited processing power.
* '''Y autoscale'''
Used to select an autoscale type. Two kinds are available:

* Disable: no autoscale is activated.
* Continuous: when a spectrum is not within the Y scale values, an autoscale is performed with no margin. This mode is not recommended for computers with limited processing power.

* '''Cursor slice visibility'''
Used to choose the default slice visibility. Four choices are available:

* All: the default slices are displayed in all areas.
* Only in 3D: the default slices are Display only in the 3D area.
* Only in 2D: the default slices are Display only in the 2D area.
* No display: the default slices are not displayed in any area.
* '''Default reference'''
Used to select your default reference for your waterfall.

Note: If the measurement is loaded, then the waterfall is displayed as the measurement has been done.

If the Waterfall is displayed, then the reference is the one defined in the user preferences.

* '''View'''
Used to select a view mode in the Waterfall window: two modes are available:

* 3D View: only the 3D view is displayed in the window.
* All views: 3D view and slices areas are displayed in the window.

* '''Orientation'''
* X ratio: this setting displays the ratio between the window and the waterfall X-axis size.

[[Image:Project_Manager_User_Pref2_80.png|framed|none]]

* Y ratio: this setting displays the ratio between the window and the waterfall Y-axis size.

[[Image:Project_Manager_User_Pref2_81.png|framed|none]]

* Magnification: this setting displays the position of the waterfall in the window in term of depth. The waterfall will be far in the window if the cam factor is large.

----

* View type:

* 3D isometric

If isometric view is checked: you can change the position and dimension of the waterfall around two fixed points (see above).

[[Image:Project_Manager_User_Pref2_82.png|framed|none]]

* 3D perspective:

[[Image:Project_Manager_User_Pref2_05.png|framed|none]]

If Perspective is not checked: there is no fixed point, the waterfall can be moved in the 3D space. This view is an orthonormal view.

[[Image:Project_Manager_User_Pref2_83.png|framed|none]]

* Freq/Time Colormap:

* Time/Freq Colormap:

[[Image:Project_Manager_User_Pref2_06.png|framed|none]]

----

===Autodisplay===
This preference page is used to set up the type of result to be automatically displayed after input connections. It is possible to select the "Autodisplay" type of result for each available plug-in analyzer.

[[Image:Project_Manager_User_Pref2_84.png|framed|none]]

The plug-in analyzers available results are the same as in the "Add/Remove window" dialog.

Example of a FFT Averaged spectrum result autodisplay:

[[Image:Project_Manager_User_Pref2_85.png|framed|none]]

Input connection: The type of result selected in the autodisplay preferences is automatically displayed

===Graph===
This window allows selecting the graph desired and changing the preferences corresponding to it.

'''Graph type: '''Used to select the kind of graph desired.

====Time====

[[Image:Project_Manager_User_Pref2_86.png|framed|none]]

* '''Graph type: '''Used to select the kind of graph desired in order to change the preferences.
If Magnitude gathering is active, when the window is in a simple multi trace mode (module, phase, real, imaginary... but not in multi trace module/phase, real/imaginary....), one area is created for each different Y magnitude in the window.

* '''X-axis: '''Select the X scale type. Two kinds of X scale are available (depending on the kind of window).
* Linear
* Logarithmic

* '''Y-axis: '''Select the Y scale type. Three kinds of Y scale are available (depending on the kind of window).
* Linear
* Logarithmic
* dB

* '''Display mode: '''Select the display mode to use for this kind of graph. Several display modes are available for each kind of graph.
* '''Trace color:''' Select the color for each trace of the graph. Only 32 traces can be displayed in the same graph. If Filling mode is active, each trace of the window is filled with a color and has a black border. This option is especially useful for multi-graph modes.
* '''Cascade settings: '''If mode Cascade is <nowiki>'</nowiki>On<nowiki>'</nowiki> you can select the depth (the Z-axis) of the 3D Cascade view.

====Spectral====

[[Image:Project_Manager_User_Pref2_87.png|framed|none]]

* '''X-axis: '''Select the X scale type. Two kinds of X scale are available (depending on the kind of window).
* Linear
* Logarithmic

* '''Y-axis: '''Select the Y scale type. Three kinds of Y scale are available (depending on the kind of window).
* Linear
* Logarithmic
* dB
* '''Display mode'''
* '''Magnitude:''' overlays all magnitude traces on a single graph.
* '''Phase''': overlays all phase traces on a single graph.
* '''Real part''': overlays all real parts traces on a single graph.
* '''Imaginary part''': overlays all imaginary part traces on a single graph.
* '''Magnitude/phase''': overlays all magnitude traces on the upper graph and all the phase traces on the lower graph.
* '''Real/imaginary''': overlays all magnitude traces on the upper graph and all the phase traces on the lower graph.
* '''Polar''': overlays all complex traces on a polar graph: þ = magnitude, Ø = phase.
* '''Real part 3D''': displays all real part traces as a 3D graph arranged along the Z-axis.
* '''Imaginary part 3D''': displays all imaginary part traces as a 3D graph arranged along the Z-axis.
* '''Magnitude 3D''': displays all magnitude traces as a 3D graph arranged along the Z-axis.
* '''Phase 3D''': displays all phase traces as a 3D graph arranged along the Z-axis.
* '''Real part multi-graph''': displays all real part traces using one graph per trace in the same window.
* '''Imaginary part multi-graph''': displays all imaginary part traces using one graph per trace in the same window.
* '''Magnitude multi-graph''': displays all magnitude traces using one graph per trace in the same window.
* '''Phase multi-graph''': displays all phase traces using one graph per trace in the same window.
* '''Phase/Magnitude''': overlays all phase traces on the upper graph using 1/3 of window space and all the magnitude traces on the lower graph using 2/3 of the window.
* '''Merged Magnitude'''/'''Phase''': displays all magnitude and phase part traces as a unique graph.
* '''Magnitude gathering''': if this mode is activated and when a multi-trace mode is selected, an area is created for each different Y magnitude: all the signals with the same Y magnitude are in the same area. If there is only one different Y magnitude, all the signals are in the same area.
* '''Trace color'''
* '''Number: '''selects the trace number for color modification.
* '''Color box: '''click on this box to modify the color of the selected trace.
* '''Filling mode''': if selected, all the curves of the windows are filled from:
* the bottom of the area if Y scale is a dB one or Logarithmic one
* the 0 value of the Y scale is linear.
* '''Dynamics'''
* '''90 dB''': resizes the Y-axis to 90 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''110 dB''': resizes the Y-axis to 110 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''130 dB''': resizes the Y-axis to 130 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''150 dB''': resizes the Y-axis to 150 dB dynamics starting from <nowiki>+</nowiki>20 dBV.

* '''Phase'''
* '''-180° -<nowiki>></nowiki> 180°''': sets the phase graph Y-axis between –180° to <nowiki>+</nowiki>180°.

[[Image:Project_Manager_User_Pref2_88.png|framed|none]]

* '''0 -<nowiki>></nowiki> 360°''': sets the phase graph Y-axis between 0 to <nowiki>+</nowiki>360°.

[[Image:Project_Manager_User_Pref2_89.png|framed|none]]

* '''Rotations: '''sets the number of rotations to be displayed on the Y-axis.

[[Image:Project_Manager_User_Pref2_91.png|framed|none]]

Example for 5 rotations

====Nth octave====

[[Image:Project_Manager_User_Pref2_92.png|framed|none]]

* '''Y Axis'''
* '''Linear''': uses linear scale for Y-axis units.
* '''Logarithmic:''' uses logarithmic scale for Y-axis units.
* '''dB: '''uses reference dB scale for Y axis units.
* '''Display mode'''
* '''Bar: '''bar representation
* '''Step: '''step representation.
* '''Rectangle: '''overlaid rectangle
* '''Filled: '''overlaid filled rectangles.
* '''Display mode'''
* '''Multi-trace''': overlays all traces on a single graph.
* '''Multi-graph''': one graph for each trace.
* '''Magnitude gathering''': if this mode is activated and when a multi-trace mode is selected, an area is created for each different Y magnitude: all the signals with the same Y magnitude are in the same area. If there is only one different Y magnitude, all the signals are in the same area.
* '''Trace color'''
* '''Number: '''selects the trace number for color modification.
* '''Color box''': click on this box to modify the color of the selected trace.

* '''Weighting'''
Used to select the type of weighting desired.

* '''Overall level'''
* '''Linear''': if checked, the linear global level is displayed.
* '''Weighted''': if checked and available, the weighted level is displayed.

* '''Frequencies'''
* '''Exact: '''displays exact band center frequency.
* '''Preferred: '''displays preferred frequencies, i.e rounded values for the central frequencies. Preferred frequencies are only available for octave and 1/3rd octave windows: in the octave. If this mode is selected in 12th and 24th octave windows, exact frequencies are displayed.
* '''Dynamics'''
* '''90 dB: '''resizes the Y-axis to 90 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''110 dB: '''resizes the Y-axis to 110 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''130 dB: '''resizes the Y-axis to 130 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* '''150 dB''': resizes the Y-axis to 150 dB dynamics starting from <nowiki>+</nowiki>20 dBV.

----

====Viewmeter====

[[Image:Project_Manager_User_Pref2_93.png|framed|none]]

* '''Display mode: '''There are two types of display:
* Bar graph

[[Image:Project_Manager_User_Pref2_03-display.png|framed|none]]

* Digital display

* '''Y Axis'''
* '''Linear''': uses linear scale for Y-axis units.
* '''Logarithmic''': uses logarithmic scale for Y-axis units.
* '''dB''': uses reference dB scale for Y-axis units.
* '''Display max, Display min: '''Displays the min and the max scalar value as a cursor. The color of the cursor can be freely selected. This property only applies to bar graphs.
* '''Display low level: '''Changes the color of the display when the value is below this level. The color can be freely selected.
* '''Display high level: '''Changes the color of the display when the value is higher than this level. The color can be freely selected.
* '''Display alarm level: '''Changes the color of the display when the value is higher than this level. The color can be freely selected.
* '''Brick height: '''Defines the height of the bricks for the viewmeter and brick display modes.
* '''Save as user preference: '''When this box is checked, the value is given as a percentage of the full scale, and may be applied to any graph.

====Monitoring====

[[Image:Project_Manager_User_Pref2_02.png|framed|none]]

* '''Trace color'''
* '''Number: '''selects the trace number for color modification.
* '''Color box''': click on this box to modify the color of the selected trace.
* '''X Axis'''
* '''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.

* '''Y Autoscale'''
* '''Continuous''':''' '''the Y scale is automatically adjusted to the current min and max y values of the window traces with a margin to facilitate visibility.
* '''Disabled''': Y autoscale is not activated.

====Compressed signal====

[[Image:Project_Manager_User_Pref2_94.png|framed|none]]

* Trace color
* Number: selects the trace number for color modification.
* Color box: click on this box to modify the color of the selected trace.

* X Axis
* 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.

====Profile====

[[Image:Project_Manager_User_Pref2_95.png|framed|none]]

* X Axis
* Linear: uses linear scale for X-axis units.
* Y Axis
* Linear: uses linear scale for Y-axis units.
* Display mode
* Magnitude: overlays all magnitude traces on a single graph.
* Phase: overlays all phase traces on a single graph.
* Magnitude gathering: if this mode is activated and when a multi-trace mode is selected, an area is created for each different Y magnitude: all the signals with the same Y magnitude are in the same area. If there is only one different Y magnitude, all the signals are in the same area.
* Trace color
* Number: selects the trace number for color modification.
* Color box: click on this box to modify the color of the selected trace.
* Filling mode: if selected, all the curves of the windows are filled from:
* the bottom of the area if Y scale is dB or Logarithmic.
* the 0 value if the Y scale is linear.

* X Autoscale
* Continuous: the X scale is automatically adjusted to the current min and max x values of the window traces.
* Disabled: X autoscale is not activated.

* Y Autoscale
* Continuous: the Y scale is automatically adjusted to the current min and max y values of the window traces with a margin to facilitate visibility.
* Disabled: Y autoscale is not activated.

====Complex profile====

[[Image:Project_Manager_User_Pref2_96.png|framed|none]]

* X Axis
* Linear: uses linear scale for X-axis units.
* Y Axis
* Linear: uses linear scale for Y-axis units.
* Logarithmic: uses logarithmic scale for Y-axis units.
* dB: uses reference dB scale for Y axis units.
* Display mode
* Magnitude: overlays all magnitude traces on a single graph.
* Phase: overlays all phase traces on a single graph.
* Real part: overlays all real part traces on a single graph.
* Imaginary part: overlays all imaginary part traces on a single graph.
* Magnitude/phase: overlays all magnitude traces on the upper graph and all phase traces on the lower graph.
* Real/imaginary: overlays all magnitude traces on the upper graph and all phase traces on the lower graph.
* Polar: displays in polar coordinates, the phase and the amplitude on a single graph.
* Real part multi-graph: displays all real part traces using one graph per trace in the same window.
* Imaginary part multi-graph: displays all imaginary part traces using one graph per trace in the same window.
* Magnitude multi-graph: displays all magnitude traces using one graph per trace in the same window.
* Phase multi-graph: displays all phase traces using one graph per trace in the same window.
* Phase/Magnitude: overlays all phase traces on the upper graph using 1/3 of window space and all the magnitude traces on the lower graph using 2/3 of the window.
* Merged Magnitude/Phase: displays all magnitude and phase parts traces on a single graph.
* Magnitude gathering: if this mode is activated and when a multi-trace mode is selected, an area is created for each different Y magnitude: all the signals with the same Y magnitude are in the same area. If there is only one different Y magnitude, all the signals are in the same area.
* Trace color
* Number: selects the trace number for color modification.
* Color box: click on this box to modify the color of the selected trace.
* Filling mode: if selected, all the curves of the windows are filled from:
* The bottom of the area if Y scale is dB or Logarithmic.
* The 0 value if the Y scale is linear.
* Dynamics
* 90 dB: resizes the Y-axis to 90 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* 110 dB: resizes the Y-axis to 110 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* 130 dB: resizes the Y-axis to 130 dB dynamics starting from <nowiki>+</nowiki>20 dBV.
* 150 dB: resizes the Y-axis to 150 dB dynamics starting from <nowiki>+</nowiki>20 dBV.

* Phase
* -180° -<nowiki>></nowiki> 180°: sets the phase graph Y-axis between –180° to <nowiki>+</nowiki>180°.

[[Image:Project_Manager_User_Pref2_97.png|framed|none]]

* 0 -<nowiki>></nowiki> 360°: sets the phase graph Y-axis between 0 to <nowiki>+</nowiki>360°.

[[Image:Project_Manager_User_Pref2_98.png|framed|none]]

*
[[Image:Project_Manager_User_Pref2_99.gif|framed|none]]
Rotations: sets the number of rotations to be displayed on the Y-axis.

[[Image:Project_Manager_User_Pref2_100.png|framed|none]]

Example for 5 rotations

* X Autoscale
* Continuous: the X scale is automatically adjusted to the current min and max x values of the window traces.
* Disabled: X autoscale is not activated.

* Y Autoscale
* Continuous: the Y scale is automatically adjusted to the current min and max y values of the window traces with a margin to facilitate visibility.
* Disabled: Y autoscale is not activated.
====Coherence====

[[Image:Project_Manager_User_Pref2_101.png|framed|none]]

* X Axis
* Linear: uses linear scale for X-axis units.
* Y Axis
* Linear: uses linear scale for Y-axis units.
* Display mode
* Multi-graph: overlays all traces on a single graph.
* Multi-trace: displays all traces using one graph per trace in the same window.
* Time multi-trace 3D: overlays all traces on a single 3D graph.
* Magnitude gathering: if this mode is activated and when a multi-trace mode is selected, an area is created for each different Y magnitude: all the signals with the same Y magnitude are in the same area. If there is only one different Y magnitude, all the signals are in the same area.
* Trace color
* Number: selects the trace number for color modification.
* Color box: click on this box to modify the color of the selected trace.
* Filling mode: if selected, all the curves of the windows are filled from:
* the bottom of the area if Y scale is dB or Logarithmic.
* the 0 value if the Y scale is linear.

====Lissajous ====

[[Image:Project_Manager_User_Pref2_102.png|framed|none]]

* X Axis
* Linear: uses linear scale for X-axis units.
* Y Axis
* Linear: uses linear scale for Y-axis units.

* Trace color
* Number: selects the trace number for color modification.
* Color box: click on this box to modify the color of the selected trace.
*
===Window===

[[Image:Project_Manager_User_Pref2_103.png|framed|none]]

* Colors: Selects the different colors used in graphical displays.
Text: scale text color in the graph area

Grid: grid color used in graph area

Grid frame: color used for the graph area frame

Cursor: color for the cursors in the graph areas

Graph background: color used in the graph area background

Window background: color used for the background of graphical display windows

Infotrace background: color used for the infotrace background.

* Cursor style
Style: Selects the cursor style in graphical displays. The available styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

Linked: Enables links between the cursors of several windows: when one cursor moves, the other also moves. See cursor menu section for details.

Display values of all traces: if checked, all Y values for each trace will be displayed, not only for the active trace.

* Cursor number: Enables one or two cursors in the graphical display. Each cursor can be moved independently. The information of each cursor will be displayed (if activated) in the infotrace area. With 2 cursors enabled, the x and y difference will be displayed.
* Grid style: Selects the grid style in the graphical area for the scale and the second Y scale if available. The double grid is available when "Merged Module/Phase" display mode is selected from the window properties.
Grid styles available are:

* No grid
* Solid
* Dashed

[[Image:Project_Manager_User_Pref2_104.png|framed|none]]

* Arrangement: Selects the arrangement style used when a new window is created. Arrangements available are:
* No arrangement
* Tile horizontally
* Tile vertically
* Cascade
* Automatic tile

* Highlight active trace
Multi-trace or multi-graph windows are useful with several inputs and multi-analysis operation. This type of graphs features now a way to highlight the active trace. A preference allows activating larger drawing for the active trace (<nowiki>+</nowiki>1 pixel on both sides).

[[Image:Project_Manager_User_Pref2_105.png|framed|none]]

It applies on 2D graphs except the compressed signals view (TDA TimeView, Recorder monitoring, Player signal, zoomed signal and signal preview). Both multi-graphs and multi-trace support this option.

This feature is activated in the default users<nowiki>'</nowiki> preferences. You can de-activate this option from the ''Home\Preferences\General'' dialog or the contextual windows properties menu: select the ''Windows'' tab and unselect the "Enlarge active trace" option.

====Trace legend====
Trace identification is necessary and OROS paid attention to provide the maximum of information to identify clearly the results. On the other hand not all the information are necessary depending on the measurement/exploitation context.

NVGate made possible the selection of the viewed and printed data from the infotrace area:

[[Image:V10_release_31.png|framed|none]]

This is accessible from both users<nowiki>'</nowiki> preferences for all new display or locally from the window properties (right click out of the graph) to modify the current window only.

===Print colors===
This preferences allows setting the way the report or copy/paste out of NVGate are plotted.

2 palettes are available one for B&W printer the other one for colored export.

[[Image:Project_Manager_User_Pref2_106.png|framed|none]]

Note the trace width depends on the printer resolution (dpi). A width of 1 in the screen correspond approximately to a width of 50 on a laser printer

===Physical quantity===

{|border="0" cellspacing="2" width="100%"
|This preference page is dedicated to the choice of the units and the
|associated options.

|}

[[Image:Project_Manager_User_Pref2_107.png|framed|none]]

* Physical quantity: Here all quantities that can be managed by NVGate are displayed. This list cannot be modified.
* Unit: Displays the list of available units for the selected quantity. The main information about the unit is displayed just below the list.
* New: Use this button to create a new unit for the selected quantity.
The following dialog box is used to define the units.

[[Image:Project_Manager_User_Pref2_108.png|framed|none]]

Name: Name that will be displayed when the unit is used

Symbol: Symbol that will be used when a value is displayed in this unit

Enable right zero display: If selected, the value will be filled by zero after the decimal

Notation

Fixed: When possible, the value is displayed without any exponent and without a prefix.

Prefixed: Prefix (u, m, k, M) used as exponent preference.

Engineer: Values are displayed with exponents in multiples of 3 ( -9,-6,0,3,6,9,12...)

Scientific: Values are displayed with exponents so that only one figure is used before the decimal

Time: Should only be used to display date and time

The following table shows the effect of the notation on the display of three values: 20000 m/s², 70700 m/s², 0.0002091 m/s²

{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center"
| 
|Fixed
|Prefixed
|Scientific
|Engineer

|-
|Right zero display enabled
|20000 70700 2.091 E-4
|20.00 k 70.7 k 209.1 u
|2.000 E4 7.07 E4 2.091 E-4
|20.00 E3 70.7 E3 209.1 E-6

|-
|Right zero display disabled
|20000 70700 2.091 E-4
|20 k 70.7 k 209.1 u
|2 E4 7.07 E4 2.091 E-4
|20 E3 70.7 E3 209.1 E-6

|} 

Enable Lin display: Authorizes or not the use of a linear scale when displaying a result with this unit in a graph

Enable Log display: Authorizes or not the use of a logarithmic scale when displaying a result with this unit in a graph

* dB Display
* Enable dB display: Authorizes or not the use of dB scale when displaying a result with this unit in a graph
* dB symbol: This symbol will be added to the value when expressed in dB.
* 0 dB reference: Value used has the dB scale reference.
Example 2 E-5 Pa for Acoustic pressure in Pa

* Conversion: Used to convert linear values to dB values.
Example:

20 for Acoustic pressure in Pa because dB Value = 20*log (Lin_Value/2e-5), but 10 for the unit representing power.

* Prefix: If Automatic is selected, the lowest and highest prefix can be selected from the two lists on the right
If forced is selected, the value is always displayed with the selected prefix

* Conversion equation: Displays the coefficient to use for converting an SI value to a given units.
Example:

Value in_ = 0.101936 * Value in SI <nowiki>+</nowiki> 0 where Value in SI is m/s²

Value in Celsius = 1* Value in Kelvin - 273.15

* Hide view meter decimal digit(s) : This settings is only available for angular velocity. If the settings is selected the visualization of the view meter angular velocity will not have decimal digit.

=====Modify=====
Use this button to modify the selected unit. Only units created by the user can be modified. Refer to "New unit" for description of the parameters.

=====Remove=====
Use this button to remove the selected unit. Only units created by the user can be removed.

=====Precision in dB=====
General option (applied to every unit) to define the number of figures displayed after the decimal when using dB display.

=====Spare units and physical quantities=====
NVGate Features 4 "Spare units" to be used when requested physical quantity does not exist in the software. Actually these spare units are physical quantities. It is possible to rename it an choose the associated units

The procedure is as follow

1. Open the file orosunit.ini from the installation directory

2. In the MAGNITUDE DEFINITION section goes to the Spare ones

3. Set corresponding Ids to 0

4. Add a line QuantityName = new name

5. Start NVGate and create associated units

Example to create Dynamic Stifness magnitude:

[[Image:Project_Manager_User_Pref2_109.png|framed|none]]

For using special characters (ex Asian languages) the orosunit.in file must be encoded as UTF-8.

Note that the orosunit.ini file is overwritten at each new install of NVGate.

===Marker===
====Free Marker page ====

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_110.png|framed|none]]

Note: the interpolated values of free markers will be available only if the free marker is placed on a peak. The peak detection criteria are the same as the peak marker adjusted in the User preferences. The marker can be moved by 1/32 step. The x value is computed with the selected weighted window.

=====Label setup=====
* Text color: Selects label color.
* Background color: Selects label background color.
* Display current position: displays automatically the coordinates of the selected point.

=====Line setup=====
* Display line: If checked, a line between marker and label is displayed
* Line color: Selects line color
* Line style: Selects line style. Available styles are:
* Full line
* Dashed line

For more details on the marker use, see the "Markers" topic from the "Chapter 2: Display".

====Harmonic marker page ====

[[Image:Project_Manager_User_Pref2_111.png|framed|none]]

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_112.png|framed|none]]

Note: the interpolated values of harmonic markers will be available only if the harmonic marker is placed on a peak. The peak detection criteria are the same as the peak marker adjusted in the User preferences. The marker can be moved by 1/32 step. The x value is computed with the selected weighted window.

=====Harmonic=====
* Number of harmonics: Selects the number of harmonics to find.
* Color: Selects harmonics color.

For more details on the marker use, see the "Markers" topic from the "Chapter 2: Display".

----

====Peak marker page====

[[Image:Project_Manager_User_Pref2_113.png|framed|none]]

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_114.png|framed|none]]

=====Max=====
* Number of peaks: Selects the number of peaks to find.
* Threshold: Defines the threshold used for the detection of peaks.
* Ignore under: Defines the absolute threshold used for the detection of peaks.

=====Sort by=====
In the Infotrace the <nowiki>'</nowiki>Peak Marker Table<nowiki>'</nowiki> can be sort by:

* Frequency: in the marker table, results are displayed from the lowest to the highest frequency.
* Amplitude: in the marker table, results are displayed from the highest to the lowest amplitude.

=====Find peak algorithm=====
Finding peaks is only available for the Spectrum and Cross Spectrum traces. It looks for the peaks of the selected trace. It can be applied to the current frozen window or to all frozen windows in the workspace.

A spectrum line is detected as a peak if the two following conditions are met:

* The two adjacent spectrum line levels are lower than the central spectrum line level.
* The two following spectrum line levels are lower than the central spectrum level minus the peak threshold.

The next two pictures show how peaks are detected. The difference between the two figures is that the second peak threshold is greater than the first one and the peak is not detected.

* Threshold: In the example below, the "Threshold" is 10 dB.

[[Image:Project_Manager_User_Pref2_115.png|framed|none]]

----

* Ignore under: Does not display the detected peak if the peak is under this value. In the example below, the "ignore under" value is –15 dB.

[[Image:Project_Manager_User_Pref2_116.png|framed|none]]

=====Damping ratio=====
damping ratio is calculated for each detected peak. The calculation is based on the Half-power-band-width method, where DR is the damping ratio:

[[Image:Project_Manager_User_Pref2_117.png|framed|none]]

The calculation of the damping factor is activated through the marker properties or preferences.

When it is activated an additional column is added in the corresponding marker table.

Warning, using nonhomogeneous weighting windows (i.e.: equivalent noise bandwidths are not the same) on FRF channels leads to incorrect peak interpolation and damping results.

For more details on the marker use, see the "Markers" topic from the "Chapter 2: Display".

====Side band marker page====

[[Image:Project_Manager_User_Pref2_118.png|framed|none]]

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

=====Marker color=====
* Number color: Selects the marker color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_119.png|framed|none]]

=====Side bands=====
* Left band color: Selects left band color
* Right band color: Selects right band color
* Number: Selects number of side bands to compute.

====Max marker page====

[[Image:Project_Manager_User_Pref2_120.png|framed|none]]

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal
* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_121.png|framed|none]]

=====Damping ratio=====
Damping ratio is calculated for each detected peak. The calculation is based on the Half-power-band-width method, where DR is the damping ratio:

[[Image:Project_Manager_User_Pref2_122.png|framed|none]]

The calculation of the damping factor is activated through the marker properties or preferences.

When it is activated an additional column is added in the corresponding marker table.

Warning, using nonhomogeneous weighting windows (i.e.: equivalent noise bandwidths are not the same) on FRF channels leads to incorrect peak interpolation and damping results.

For more details on the marker use, see the "Markers" topic from the "Chapter 2: Display".

=====Find max algorithm=====
Looks for the maximum of the selected trace. It can apply to the current frozen window or to all frozen windows in the workspace A maximum is defined as a local maximum such that the variation in size of spectral density of ray, in relation to other local maximum surrounding it, is greater than a set threshold.

[[Image:Project_Manager_User_Pref2_123.png|framed|none]]

The following diagram shows how the maxima are searched for different maximum threshold values. In the first figure, the maximum threshold allows to find 2 maximum while in the second figure a larger maximum threshold found only one maximum.

* Ignore under: Does not display the detected peak if the peak is under this value. In the example below, the "ignore under" value is –15 dB.

[[Image:Project_Manager_User_Pref2_124.png|framed|none]]

Power band marker page

[[Image:Project_Manager_User_Pref2_125.png|framed|none]]

=====Style=====
Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
=====Power bands=====
* Right line color: Selects right line color.

=====Octave marker page=====

[[Image:Project_Manager_User_Pref2_126.png|framed|none]]

* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.

=====Kinematic marker page=====

[[Image:Project_Manager_User_Pref2_127.png|framed|none]]

Selects marker drawing style used in graphical area. The available marker drawing styles are:

* Vertical line
* Vertical dashed line
* Vertical with rectangle
* Cross-hair
* Vertical <nowiki>+</nowiki> Horizontal

* Marker color: Selects the marker color used in the graphical area.
* Number color: Selects the marker number color used in the graphical area.
* Associated to active trace: If checked, the marker added will be associated with the active trace: the markers display the values only for the active signal. If not checked, the markers display all the values when not associated with a signal.
* Interpolation: This setting selects the interpolation of values displayed in the marker table.
* None: no interpolation applied.
* X: x interpolation is active.
* X & Y: x and y interpolations are active.

[[Image:Project_Manager_User_Pref2_128.png|framed|none]]
Note: the interpolated values of harmonic markers will be available only if the harmonic marker is placed on a peak. The peak detection criteria are the same as the peak marker adjusted in the User preferences. The marker can be moved by 1/32 step. The x value is computed with the selected weighted window.

===Export ===
This function is used to configure the way data is converted to a specified format.

====UFF====
[http://www.sdrl.uc.edu/sdrl/referenceinfo/universalfileformats/file-format-storehouse/universal-dataset-number-58 UFF58] time export is ASCII so that resulting export file size may quite large. Time to export UFF58 files may be long according to the ASCII file size being exported.

[[Image:Project_Manager_User_Pref2_129.png|framed|none]]

Note: UFF export format also stores the result physical quantity. Please ensure that the software you will use to load the UFF file is set to the same physical quantity as the imported file.

=====Results=====
* Roving impact hammer: This option is used only when converting cross-spectra, FRH, coherence. Depending on the habits, the response and the reference may be different. For instance, to use a UFF converted file in Smart office software, the option must be selected.
* Overwrite existing files: you can overwrite existing files by new results.
* Append to existing files: you can append new results to existing files.
* Batch export in one file: The same features are associated to batch export, allowing the export of multiple acquisitions (from on project or several ones) in one unique file.

=====Signal=====
* One file per track: When a signal file is converted to UFF, every track is saved in a separate file if this option is selected.

====Mat====
[https://mathworks.com Matlab] export requires that the PC virtual memory be adjusted to double the size of the native OROS time recording.

For instance for a 500Mb OROS time data record to be converted into Matlab, you may need to adjust the PC virtual memory to 1Gb.

[[Image:Project_Manager_User_Pref2_130.png|framed|none]]

=====Matlab version=====
Used to select the matlab version of the created file. Refer to your installed version to find out which version you should select.

=====Format=====
* Binary format: The conversion of a signal file generates a matlab file containing the description of the track and one binary file containing the data itself. A procedure for reading the data in matlab has to be written.
* Matlab file (.mat): The conversion of a signal file generates a matlab file containing the description of the track and the data itself. Very large file may be difficult to open in Matlab.

====Txt====

[[Image:Project_Manager_User_Pref2_131.png|framed|none]]

=====Generate one file per track=====
When a result file is converted to txt, every result is exported to a dedicated file.

=====Complex results export=====
* Module/Phase: Complex result are in the Module / phase format.
* Real/Imaginary part: Complex results are in Real / Imaginary part format.

=====Waterfall export=====
* 1 slice per row: The Waterfall is displayed in the exported file so that each line represents a slice of the Waterfall (a spectrum for instance). If the Waterfall contains 50 slices, and the spectra contain 401 lines, the text file will contain 50 lines and 401 columns.
* 1 slice per column: The Waterfall is displayed in the exported file so that each column represents a slice of the Waterfall (a spectrum for instance). If the Waterfall contains 50 slices, and the spectra contain 401 lines, the text file will contain 401 lines and 50 columns.
* Column limitation: When the one slice per column option is selected, it is possible to specify the maximum number of columns that should be created. If the result contains more slices than this number, it is split. This option should be selected when the file is opened with a spreadsheet editor, because the number of columns in this editor might be limited (256 for Excel).

====Wav (audio)====
This option only applies to the conversion of signals to audio wav files, not to standard wav files.

Exported wav file sampling frequency depends on OROS native file sampling frequency.

OROS native files containing more than 16 tracks will automatically be exported in single tack wav file (one file per track, despite export preference option being unticked).

[[File:NVGate_Wav_Export.jpg|400px]]

Compatibility table (OROS to Wav):

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|OROS native file sampling frequency (kS/s)
|Wav audio formats (kHz)

|-
|102.4
|44.1, 48, 96

|-
|65.5536
|44.1, 48, 96

|-
|51.2
|44.1, 48

|-
|32.768
|44.1, 48

|-
|25.6
|44.1, 48

|-
|20.48
|44.1, 48

|-
|16.384
|44.1, 48

|-
|12.8
|44.1, 48

|-
|10.24
|44.1, 48

|}

=====Frequency=====
Sets the frequency of the converted file. The frequency can be 44.1 kHz, 48 kHz or 96 kHz. It might not be possible to convert the OROS file to the target frequency. It depends on the recording frequency of the OROS file.

=====Generate one file per track=====
When a signal file is converted to wav, every track is saved in a separate file if this option is selected.

=====Normalize=====
A WAV audio file is sampled within [-1;1] Y axis values. By default the export is done according full Range peak of the recorded track file to the WAV scale [-1;1].
If the dynamic of the recorded signal is low regarding the range peak, WAV level could become too low to be playback on speaker.
Activate the "Normalize" option so that the export is done according to true level of the signal to be exported. Min and Max of the signal will be taken into account to generate WAV audio file betweenrange [-1;1] corresponding to [Min;Max].
ATTENTION : Signal level become no more valid for comparison while using "Normalize" Option.

- With "Normalize" option : [-Range Peak ; Range Peak] --> [-1 ; 1]

- Without "Normalize" option : [Signal Min ; Signal Max] --> [-1 ; 1]

File:NVGate Wav Export.jpg

2020-08-25T06:41:59Z

Yannick Balter: File uploaded with MsUpload

File uploaded with MsUpload

NVGate Event definition

2020-08-24T13:31:38Z

Yannick Balter: /* Delta RPM */

==Event definition==
This module is used to define multiple events that can start, stop, and trigger the plug-ins or the source modules such as Recorder and Player.

[[Image:Event_definition_01.png|framed|none]]

==Connect ==
[[Image:Reports_Tools_Ribbons_17.png|framed|none]]
On the acquisition tab, this area manages events and corresponding triggers. This group allows selecting the event type (source, setup) and associates it with the plug-in analyzers triggers

This button opens the corresponding Event properties. The opened dialog shows both the source signal setup and the detection settings (may be split in different tabs).
On this dialog box you can easily "drag and drop" events to "start", "Stop" or "trigger" any NVGate plug in.
[[File:events.png|framed|none]]

The available event types are below:

==Edge detection==
[[Image:Reports_Tools_Ribbons_361.png]] Edge: Detect when the signal from an input or a recorded track crosses a threshold.
This module is used with the analog inputs (tach pulse or hammer impact). This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Edge n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source<ref>Input 5 to input 8 are not able to be set as source using an OR35 analyzer.</ref>''': selects the signal input source. The user can choose any Front-end fast analog input (in connected mode on-line) or from the Player (in post-analysis mode).
* '''Input ''''''filter''': adds a digital filter before the edge detection process. The user can choose any filter from the list of the defined filters.
* '''Threshold''': sets the signal threshold for edge detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full input signal scale (depending on the input range).
* '''Slope''': selects the slope of the input signal on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|The events are detected on rising edge of the input signal

|-
|Fall
|The events are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between the detection of two edges. If a transition is detected before this time has expired since the last valid event then the new edge is rejected. The user can enter any value between 0 and 36000s.

[[Image:Event_definition_02.png|framed|none]]

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new event can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new event can be detected. This setting is used to reject false edge detection following, for example, an input signal transition.

==RPM==
[[Image:Reports_Tools_Ribbons_364.png]]RPM: Detect when a tachometer is below or above a specified angular speed. This module is associated with the Tachometer module. You need to first activate it on Tachometer plug in. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source''': selects the tach source. The user can choose any active tach as the source of the RPM event.
* '''Threshold velocity''': defines the threshold velocity for detecting an event. The user can enter any value between the Min Speed and the Max Speed setting values defined in the tach source.

[[Image:Event_definition_03.png|framed|none]]

* '''Slope''': selects the slope of the tach velocity evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="62%" align="center"
|'''Slope'''
|'''Description'''

|-
|Run up
|Events are detected on speed acceleration

|-
|Run down
|Events are detected on speed deceleration

|} 

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the Max Speed setting of the tach source. If Slope is set to RISE, the velocity must go below Threshold - Hystersis before a new event can be detected. If Slope is set to FALL, the velocity must go above Threshold <nowiki>+</nowiki> Hystersis before a new event can be detected. This setting is used to reject false edges detection following, for example, tach velocity transition.
* '''Interpolation''': used for the interpolation of the event date. For example, if Threshold velocity is 1000 RPM and if the tach delivers a revolution at 990 RPM beginning on date t1 and a revolution at 1010 RPM beginning on date t2:
* if the Interpolation is disabled, the event is detected on date t2
* if the Interpolation is enabled, the event is detected on date

[[Image:Event_definition_04.png|framed|none]]

==Delta RPM==
[[Image:Reports_Tools_Ribbons_365.png]]Delta-RPM: Same as RPM but generates an event at each step. This module is associated with the Tachometer module. You need first to activate it on Tachometer plug in. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Delta RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source''': selects the tach source. The user can choose any active tach as source of the Delta RPM event.
* '''Lower velocity''': the level above which the velocity variation condition is tested for launching the delta RPM event.
* '''Upper velocity''': the level below which the velocity variation condition is tested for launching the delta RPM event.

[[Image:rpm_delta.png|framed|none]]

* '''Delta velocity''': the variation in velocity that launches the event.

[[Image:Event_definition_06.png|framed|none]]

* '''Number of events''': the number of events between Upper velocity and Lower velocity (considering Delta velocity).

[[Image:Event_definition_07.png|framed|none]]

* '''Slope''': selects the slope of the tach velocity evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="89%" align="center"
|'''Slope'''
|'''Description'''

|-
|Run up
|Events are detected on speed acceleration

|-
|Run down
|Events are detected on speed deceleration

|-
|First
|The first event detected (during rise or fall) determines the slope of this event.

|-
|Any
|Events are detected on speed acceleration and deceleration.

|} 

* '''Interpolation''': Used for the interpolation of the event date. For example, if Threshold velocity is 1000 RPM and if the tach delivers a revolution at 990 RPM beginning at the date t1 and a revolution at 1010 RPM beginning on date t2:
* If the Interpolation is disabled, the event is detected on date t2
* If the interpolation is enabled, the event is detected on date t1 <nowiki>+</nowiki> (t2 - t1) * (1000 - 990) / (1010 - 990)

[[Image:Event_definition_08.png|framed|none]]

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

==Level==
[[Image:Reports_Tools_Ribbons_362.png]] Level: Detect when a signal is below or above a level
This module is used with DC inputs (optional) and/or associated with the TDA or Monitor module. This event can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Level n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 4).
* '''Source''': selects a DC input or a Monitor channel as source of the level event.
* '''Type''': the type of measurement for level detection.

{|border="2" cellspacing="0" cellpadding="4" width="64%" align="center"
|'''Type'''
|'''Description'''

|-
|DC
|measurement of the input DC level

|-
|Min
|measurement of the minimum signed input level

|-
|Max
|measurement of the maximum signed input level

|-
|RMS
|measurement of the input RMS level

|-
|Skew
|measurement of the input skew level

|-
|Kurtosis
|measurement of the input kurtosis level

|} 

''Hidden/fixed: The type is fixed to DC if the source is a DC input.''

* '''Threshold''': The threshold of the level event. The limitation is <nowiki>+</nowiki>/- Range peak of the source for DC, Min and Max types. The limitation is <nowiki>+</nowiki>/- 20 for skew. The value goes from 1 to 250 for kurtosis and from 0 to Range peak of the source for RMS. This setting can be displayed in dB if the measurement type chosen is RMS.

[[Image:Event_definition_09.png|framed|none]]

* '''Status''':

{|border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
|'''Status'''
|'''Description'''

|-
|Above
|The event is detected if the measured value is above the threshold.

|-
|Under
|The event is detected if the measured value is below the threshold.

|} 

==Delta level==
[[Image:Reports_Tools_Ribbons_363.png]] This module is used with DC inputs (optional) and/or associated with the Monitor module. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Delta n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 4).
* '''Source''': selects a DC input or a Monitor channel as source of the level event.
* '''Type''': the type of measurement for delta level detection.

{|border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Type'''
|'''Description'''

|-
|DC
|measurement of the input DC level

|-
|Min
|measurement of the minimum signed input level

|-
|Max
|measurement of the maximum signed input level

|-
|RMS
|measurement of the input RMS level

|-
|Skew
|measurement of the input skew level

|-
|Kurtosis
|measurement of the input kurtosis level

|} 

''Hidden/fixed: The type is fixed to DC if the source is a DC input.''

* '''Lower value''': the lower level of the delta level event. Its minimum value is - Range peak of the source for DC, Min and Max types. It is 0 for RMS, - 20 for skew and 1 for kurtosis. This setting can be displayed in if the measurement type chosen is RMS.

[[Image:Event_definition_10.png|framed|none]]

* '''Upper value''': the upper level of the delta level event. Its maximum value is Range Peak of the source for DC, Min, Max and RMS types. It is 20 for skew, and 250 for kurtosis. This setting can be displayed in dB if the measurement type chosen is RMS.
* '''Delta value''': This setting can be displayed in dB if the measurement type chosen is RMS.
* '''Slope''': selects the slope of the level evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="92%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The events are detected on an increasing level

|-
|Fall
|The events are detected on a decreasing level

|-
|First
|The first event detected (during rise or fall) determines the slope of this event.

|-
|Any
|The events are detected on a increasing or decreasing level

|} 

==Periodic==
[[Image:Reports_Tools_Ribbons_366.png]]Periodic: Used to trigger a plug-in by periodic step. This event can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Periodic n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Period''': defines the event generation period. An event is generated every Period second (the first one is generated 1 period after the run). The user can enter a value between 2 ms and 1000000 s.
==Combined events==
[[Image:Reports_Tools_Ribbons_367.png]]Combined: Generates an event which is the result of a combination of 2 events. Possible combinations are: OR, AND and AFTER.

* '''Label''': the name of the event (Default: ''Combination n'', with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Event A''': defines the first operand of the combined event. The user can choose any defined event as operand except for a combined event.
* '''User''': defines the user used to detect a new event from the two operands, Event A and Event B.

{|border="2" cellspacing="0" cellpadding="4" width="92%" align="center"
|'''User'''
|'''Description'''

|-
|A or B
|An event is generated when event A or B occurs

|-
|A and B
|An event is generated when both event A and B occur at the same time (in the same data block = 256 pts) Example: 
[[Image:Event_definition_11.png|framed|none]]
 

|-
|A after B
|An event is generated when event A occurs after event B.

|} 

* '''Event B''': defines the second operand of the combined event. The user can choose any defined event as operand except for a combined event.

==User events==
[[Image:Reports_Tools_Ribbons_368.png]] User: Generates an event when the operator presses the corresponding event button in the software/remote controller interface.
Four user events are available. These events are compatible with the macros. They are particularly useful to run several plug-ins at different time in the same analysis. It can also be put in the control panel or controlled by NVDrive.

[[Image:Event_definition_12.png|framed|none]]

* '''Label''': Allows to rename the event.
* '''Trigger''': The user event<nowiki>’</nowiki>s triggering.

==External Synch==
[[Image:Reports_Tools_Ribbons_369.png]]''External synch:'' ''Properties of the Ext synch trigger inputs.

==Monitoring Solution==
If you would like more advanced trigger and actions, please have a look on the [[Monitoring_Solution|the monitoring solution]].

NVGate Event definition

2020-08-24T13:30:18Z

Yannick Balter: /* Delta RPM */

==Event definition==
This module is used to define multiple events that can start, stop, and trigger the plug-ins or the source modules such as Recorder and Player.

[[Image:Event_definition_01.png|framed|none]]

==Connect ==
[[Image:Reports_Tools_Ribbons_17.png|framed|none]]
On the acquisition tab, this area manages events and corresponding triggers. This group allows selecting the event type (source, setup) and associates it with the plug-in analyzers triggers

This button opens the corresponding Event properties. The opened dialog shows both the source signal setup and the detection settings (may be split in different tabs).
On this dialog box you can easily "drag and drop" events to "start", "Stop" or "trigger" any NVGate plug in.
[[File:events.png|framed|none]]

The available event types are below:

==Edge detection==
[[Image:Reports_Tools_Ribbons_361.png]] Edge: Detect when the signal from an input or a recorded track crosses a threshold.
This module is used with the analog inputs (tach pulse or hammer impact). This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Edge n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source<ref>Input 5 to input 8 are not able to be set as source using an OR35 analyzer.</ref>''': selects the signal input source. The user can choose any Front-end fast analog input (in connected mode on-line) or from the Player (in post-analysis mode).
* '''Input ''''''filter''': adds a digital filter before the edge detection process. The user can choose any filter from the list of the defined filters.
* '''Threshold''': sets the signal threshold for edge detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full input signal scale (depending on the input range).
* '''Slope''': selects the slope of the input signal on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|The events are detected on rising edge of the input signal

|-
|Fall
|The events are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between the detection of two edges. If a transition is detected before this time has expired since the last valid event then the new edge is rejected. The user can enter any value between 0 and 36000s.

[[Image:Event_definition_02.png|framed|none]]

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new event can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new event can be detected. This setting is used to reject false edge detection following, for example, an input signal transition.

==RPM==
[[Image:Reports_Tools_Ribbons_364.png]]RPM: Detect when a tachometer is below or above a specified angular speed. This module is associated with the Tachometer module. You need to first activate it on Tachometer plug in. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source''': selects the tach source. The user can choose any active tach as the source of the RPM event.
* '''Threshold velocity''': defines the threshold velocity for detecting an event. The user can enter any value between the Min Speed and the Max Speed setting values defined in the tach source.

[[Image:Event_definition_03.png|framed|none]]

* '''Slope''': selects the slope of the tach velocity evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="62%" align="center"
|'''Slope'''
|'''Description'''

|-
|Run up
|Events are detected on speed acceleration

|-
|Run down
|Events are detected on speed deceleration

|} 

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the Max Speed setting of the tach source. If Slope is set to RISE, the velocity must go below Threshold - Hystersis before a new event can be detected. If Slope is set to FALL, the velocity must go above Threshold <nowiki>+</nowiki> Hystersis before a new event can be detected. This setting is used to reject false edges detection following, for example, tach velocity transition.
* '''Interpolation''': used for the interpolation of the event date. For example, if Threshold velocity is 1000 RPM and if the tach delivers a revolution at 990 RPM beginning on date t1 and a revolution at 1010 RPM beginning on date t2:
* if the Interpolation is disabled, the event is detected on date t2
* if the Interpolation is enabled, the event is detected on date

[[Image:Event_definition_04.png|framed|none]]

==Delta RPM==
[[Image:Reports_Tools_Ribbons_365.png]]Delta-RPM: Same as RPM but generates an event at each step. This module is associated with the Tachometer module. You need first to activate it on Tachometer plug in. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Delta RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Source''': selects the tach source. The user can choose any active tach as source of the Delta RPM event.
* '''Lower velocity''': the level above which the velocity variation condition is tested for launching the delta RPM event.
* '''Upper velocity''': the level below which the velocity variation condition is tested for launching the delta RPM event.

[[Image:rpm_delta.png|framed|none]]

* '''Delta velocity''': the variation in velocity that launches the event.

[[Image:Event_definition_06.png|framed|none]]

* '''Number of events''': the number of events between Upper velocity and Lower velocity (considering Delta velocity).

[[Image:Event_definition_07.png|framed|none]]

* '''Slope''': selects the slope of the tach velocity evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="89%" align="center"
|'''Slope'''
|'''Description'''

|-
|Run up
|Events are detected on speed acceleration

|-
|Run down
|Events are detected on speed deceleration

|-
|First
|The first event detected (during rise or fall) determines the slope of this event.

|-
|Any
|Events are detected on speed acceleration and deceleration.

|} 

* '''Interpolation''': Used for the interpolation of the event date. For example, if Threshold velocity is 1000 RPM and if the tach delivers a revolution at 990 RPM beginning at the date t1 and a revolution at 1010 RPM beginning on date t2:
* If the Interpolation is disabled, the event is detected on date t2
* If the interpolation is enabled, the event is detected on date t1 <nowiki>+</nowiki> (t2 - t1) * (1000 - 990) / (1010 - 990)

[[Image:Event_definition_08.png|framed|none]]

* '''Average size''': Blabla bla

==Level==
[[Image:Reports_Tools_Ribbons_362.png]] Level: Detect when a signal is below or above a level
This module is used with DC inputs (optional) and/or associated with the TDA or Monitor module. This event can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Level n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 4).
* '''Source''': selects a DC input or a Monitor channel as source of the level event.
* '''Type''': the type of measurement for level detection.

{|border="2" cellspacing="0" cellpadding="4" width="64%" align="center"
|'''Type'''
|'''Description'''

|-
|DC
|measurement of the input DC level

|-
|Min
|measurement of the minimum signed input level

|-
|Max
|measurement of the maximum signed input level

|-
|RMS
|measurement of the input RMS level

|-
|Skew
|measurement of the input skew level

|-
|Kurtosis
|measurement of the input kurtosis level

|} 

''Hidden/fixed: The type is fixed to DC if the source is a DC input.''

* '''Threshold''': The threshold of the level event. The limitation is <nowiki>+</nowiki>/- Range peak of the source for DC, Min and Max types. The limitation is <nowiki>+</nowiki>/- 20 for skew. The value goes from 1 to 250 for kurtosis and from 0 to Range peak of the source for RMS. This setting can be displayed in dB if the measurement type chosen is RMS.

[[Image:Event_definition_09.png|framed|none]]

* '''Status''':

{|border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
|'''Status'''
|'''Description'''

|-
|Above
|The event is detected if the measured value is above the threshold.

|-
|Under
|The event is detected if the measured value is below the threshold.

|} 

==Delta level==
[[Image:Reports_Tools_Ribbons_363.png]] This module is used with DC inputs (optional) and/or associated with the Monitor module. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Delta n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 4).
* '''Source''': selects a DC input or a Monitor channel as source of the level event.
* '''Type''': the type of measurement for delta level detection.

{|border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Type'''
|'''Description'''

|-
|DC
|measurement of the input DC level

|-
|Min
|measurement of the minimum signed input level

|-
|Max
|measurement of the maximum signed input level

|-
|RMS
|measurement of the input RMS level

|-
|Skew
|measurement of the input skew level

|-
|Kurtosis
|measurement of the input kurtosis level

|} 

''Hidden/fixed: The type is fixed to DC if the source is a DC input.''

* '''Lower value''': the lower level of the delta level event. Its minimum value is - Range peak of the source for DC, Min and Max types. It is 0 for RMS, - 20 for skew and 1 for kurtosis. This setting can be displayed in if the measurement type chosen is RMS.

[[Image:Event_definition_10.png|framed|none]]

* '''Upper value''': the upper level of the delta level event. Its maximum value is Range Peak of the source for DC, Min, Max and RMS types. It is 20 for skew, and 250 for kurtosis. This setting can be displayed in dB if the measurement type chosen is RMS.
* '''Delta value''': This setting can be displayed in dB if the measurement type chosen is RMS.
* '''Slope''': selects the slope of the level evolution on which a transition is detected.

{|border="2" cellspacing="0" cellpadding="4" width="92%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The events are detected on an increasing level

|-
|Fall
|The events are detected on a decreasing level

|-
|First
|The first event detected (during rise or fall) determines the slope of this event.

|-
|Any
|The events are detected on a increasing or decreasing level

|} 

==Periodic==
[[Image:Reports_Tools_Ribbons_366.png]]Periodic: Used to trigger a plug-in by periodic step. This event can be applied to any plug-in analyzer including Waterfall and Recorder.

* '''Label''': the name of the event (by default Periodic n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Period''': defines the event generation period. An event is generated every Period second (the first one is generated 1 period after the run). The user can enter a value between 2 ms and 1000000 s.
==Combined events==
[[Image:Reports_Tools_Ribbons_367.png]]Combined: Generates an event which is the result of a combination of 2 events. Possible combinations are: OR, AND and AFTER.

* '''Label''': the name of the event (Default: ''Combination n'', with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Event A''': defines the first operand of the combined event. The user can choose any defined event as operand except for a combined event.
* '''User''': defines the user used to detect a new event from the two operands, Event A and Event B.

{|border="2" cellspacing="0" cellpadding="4" width="92%" align="center"
|'''User'''
|'''Description'''

|-
|A or B
|An event is generated when event A or B occurs

|-
|A and B
|An event is generated when both event A and B occur at the same time (in the same data block = 256 pts) Example: 
[[Image:Event_definition_11.png|framed|none]]
 

|-
|A after B
|An event is generated when event A occurs after event B.

|} 

* '''Event B''': defines the second operand of the combined event. The user can choose any defined event as operand except for a combined event.

==User events==
[[Image:Reports_Tools_Ribbons_368.png]] User: Generates an event when the operator presses the corresponding event button in the software/remote controller interface.
Four user events are available. These events are compatible with the macros. They are particularly useful to run several plug-ins at different time in the same analysis. It can also be put in the control panel or controlled by NVDrive.

[[Image:Event_definition_12.png|framed|none]]

* '''Label''': Allows to rename the event.
* '''Trigger''': The user event<nowiki>’</nowiki>s triggering.

==External Synch==
[[Image:Reports_Tools_Ribbons_369.png]]''External synch:'' ''Properties of the Ext synch trigger inputs.

==Monitoring Solution==
If you would like more advanced trigger and actions, please have a look on the [[Monitoring_Solution|the monitoring solution]].