Difference between revisions of "NVGate Synchronous Order Analysis"

* Avg. Order CrossCorr: This result is available if correlation is selected in ''the Synch. Order x/Correlation ''and ''Synch. Order x x/Average/Domain is ''Spectral or Frequency synchronous. This result is not available if there is no cell checked in the ''Synch. Order x /Order FFT/Cross spectrum ''matrix

{|border="2" cellspacing="0" cellpadding="4" width="79%" align="center"

FFT Bandwidth: set in ''FFTx/FFT analysis/range''

Contains the settings related to the source input.

* '''Order number''': Select the number of the order you want to track, from 0.001 up to 800

* '''Weighting window''': window used to weight the signal before processing. There are 6 fixed windows: Uniform, Hanning, Hamming, Kaiser Bessel, and Flat top; 3 customized windows: Force, Response (see the Time Windows chapter) For the window characteristics, see the Appendix.

Contains the Synchronous order analysis tachometer settings.

* If set to ''None'', the SOA will works on the regular way: Interpolation of the sampling dates from the RPM information).

* If set to a sampling input, the SOA will use it for sampling the channels signals

Contains the settings related to triggering events and how to start, and stop signal computation. Note that the trigger is always done on the next available revolution pulse:

|}<br clear="all">

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

''Hidden/fixed: This setting is only available when the Referenced Peak hold averaging mode is selected.''

Transforms the order blocks into order spectra.

''Hidden/fixed: fixed''

Calculation of the order bands sum.

* '''Lower Order''': Specifies the lower order of the overall computation order range

* '''Upper Order''': Specifies the upper order of the overall computation order range

Calculation of the Auto Correlation and the Cross Correlation in the angle domain.

[[File:Correlation2.png|left]]<br>

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

All statuses are available to add to the control panel

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

* ''Green background and red text'': the current acquisition is real-time, but since start not all the blocks were analyzed.

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

* Stop: the acquisition is stopped

The following scheme describes the different states of the measurement:

'''Note''': all start event, trigger, new revolution or run are ignored in <nowiki>’</nowiki>free run<nowiki>’</nowiki> mode

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

* <nowiki>’</nowiki>'''-'''<nowiki>’</nowiki>: The acquisition is currently not real-time (current block is not analyzed an averaged).

This status corresponds to the instantaneous overload indication within 1 SOA trigger block, for instance amplitude overload occurred in the current analyzed block. Note that overloaded block may be automatically rejected (see accept mode).

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.

[[category:Order analysis]]