NVGate Architecture
Analyzer architecture
On-Line acquisition synopsis
The following synopsis presents the basic structure of the NVGate multi analyzer architecture for real-time acquisition and analysis. In this mode, OR3X processes parallel analysis with all plug-in analyzers running at the same time (FFT, 1/n Octave, SOA, Recorder…). The Front-end inputs may be connected to any plug-in analyzer through the channels. There are up to 32 (8 for OR34/OR35 analyzer) channels on each plug-in analyzer. Any input plug-in analyzer channel combination is allowed.
The plug-in analyzers share general resources such as Filters, Events, Time windows, and Tachometers. These resources can be associated with any channel or plug-in analyzer with a centralized set of parameters: for example, by applying filter 1 to channel 1 to 8 of each plug-in analyzer and filter 2 to channels 9 to 16 you can modify filtering characteristics directly from the resource settings.
The Filter builder provides general purpose filters for low pass, high pass, pass band, stop band and integration functions that apply to the time domain signals. For example: distributing Input I to channel 1 to 3, will provide simultaneous analysis of acceleration, velocity and displacement of an accelerometer by applying Integrator filter to channel 2 and double Integrator filter to channel 3. The Time windows resources allow the modification of force and response weighting windows. For example: associating the force window with channel 1 and the Response window to the rest of channels allows the modification of response characteristics from a single set of parameters in the resource.
The Event Definition resource is used to create an event that can start, stop and trigger plug-in analyzers acquisition. These events can be based on different criteria (DC level, RPM, time…) as well as on results computed by the Monitor (Kurtosis, RMS, DC…). For example: an event based on an input RMS level can be used to start and/or stop the FFT averaging and the Recorder simultaneously by connecting the event to the plug-in analyzer trigger sub-module.
The Waterfall module collects and synchronizes the results computed and provided by the different plug-in analyzers. These results are displayed in segments and can be sorted in relation to selectable references (Time, RPM, DC…). For example: while computing orders, it is possible to track these values by adding them and the Tachometer (the reference) to the Waterfall. You will then be able to display order profiles and switch the reference between time and RPM. It is then possible to add any new result (value or spectrum) or any reference (DC input, 2nd tach) to the Waterfall.
Using the ’Setup’ menu (see also VOL3 § "Operation with Vision") it is possible to guide you through connections of inputs, player tracks, output signals, event, filters or waterfall and display properties related.
Post Analysis synopsis
In the Post analysis mode, the Front-end and Output signals are no longer available. The only source able to provide recorded time signals is the player. Post analysis features exactly the same functions as the On-Line mode replacing the inputs by the Player tracks. The Player tracks are then connectable to the plug-in analyzer channels and can be used by the resources. Post analysis processing can be performed on the DSP (Connected mode, only for OR36/OR38) as well as on the PC CPU (Office mode).
In addition to the Post analysis, it is possible to split the recorded signal files (channels and duration) by re-recording selected channels and time segments in a new signal file.
Post analysis processing time depends directly on the computation load. It may be faster or slower than the real-time analysis. Using the Post analysis accommodates larger requests in terms of computation power that cannot be achieved in real-time analysis.
