9,121
edits
| Line 9: | Line 9: | ||
Use: [[NVGate_Software_overview#GoToResult|GoToResult]] | Use: [[NVGate_Software_overview#GoToResult|GoToResult]] | ||
==Display Available results== | |||
Diplay windows can be done in 2 ways. | Diplay windows can be done in 2 ways. | ||
| Line 540: | Line 540: | ||
[[Image:FFT_05.png|framed|none]] | [[Image:FFT_05.png|framed|none]] | ||
==Settings== | |||
There are sevral ways to access the settings : | There are sevral ways to access the settings : | ||
We advice the first one. | We advice the first one. | ||
| Line 554: | Line 554: | ||
===Channel=== | |||
Contains the settings related to the source input. | Contains the settings related to the source input. | ||
| Line 575: | Line 575: | ||
* '''Weighting window''': window used to weighting the signal before the processing. There are six set windows: Uniform, Hanning, Hamming, Kaiser Bessel, Flat top, and three customized windows: Force, Response and Dual exp (see the Time Windows chapter). For the window characteristics, see the Appendix. | * '''Weighting window''': window used to weighting the signal before the processing. There are six set windows: Uniform, Hanning, Hamming, Kaiser Bessel, Flat top, and three customized windows: Force, Response and Dual exp (see the Time Windows chapter). For the window characteristics, see the Appendix. | ||
===Trigger=== | |||
Contains the settings related to trigger events and how to start, and stop signal computation. | Contains the settings related to trigger events and how to start, and stop signal computation. | ||
| Line 621: | Line 621: | ||
''Hidden/fixed: The Trigger frequency is enabled when FFTx/Average/Domain is set to Frequency Synchronous.'' | ''Hidden/fixed: The Trigger frequency is enabled when FFTx/Average/Domain is set to Frequency Synchronous.'' | ||
===Average=== | |||
Contains the settings related to the type of averaging of the signals to be computed. | Contains the settings related to the type of averaging of the signals to be computed. | ||
| Line 682: | Line 682: | ||
* '''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. | * '''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. | Contains the settings related to the type of analysis of the signals to be computed. | ||
| Line 695: | Line 695: | ||
* '''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" | * '''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. | Unlike the display zoom function; the analysis zoom function allows you to zoom into a selected bandwidth increasing the analysis resolution. | ||
| Line 708: | Line 708: | ||
* 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 '''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. | * 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.]] | [[NVGate_Envelope_analysis|Read the user note for more info about envelope analysis.]] | ||
| Line 730: | Line 730: | ||
[[category:FFT]] | [[category:FFT]] | ||
===CBT: Order analysis=== | |||
Contains the settings related to constant band tracking operations. | Contains the settings related to constant band tracking operations. | ||
[[NVGate_CBT_principle_and_settings|Read the dedicated CBT page for more info.]] | [[NVGate_CBT_principle_and_settings|Read the dedicated CBT page for more info.]] | ||
| Line 774: | Line 774: | ||
'''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. | '''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. | Calculation of the Auto Correlation and the Cross Correlation. | ||
[[File:Correlation2.png|left]]<br> | [[File:Correlation2.png|left]]<br> | ||
| Line 818: | Line 818: | ||
* 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. | * 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. | Calculation of the FFT bands sum. | ||
| Line 825: | Line 825: | ||
* '''Upper frequency''': Specifies the upper 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. | All status are available for the control panel. Statuses are refreshed all the time at roughly 10 Hz. | ||
| Line 879: | Line 879: | ||
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. | 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. | 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: | 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: | ||
| Line 889: | Line 889: | ||
* '''<nowiki>’</nowiki>-<nowiki>’</nowiki>''': The acquisition is currently not real-time (current block is not analyzed an averaged). | * '''<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). | 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. | 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. | ||