NVGate Ribbons: Acquisition Tab

From OROS Wiki
Jump to navigation Jump to search

The "Acquisition" tab

This tab provides all the necessary entries to setup the front-end and the use of any channels in details. It separates the acquisition channels setup from the outputs, triggering, tachometer, and filters ones. A special group is available to manage the recorder setup.

While switching to post-analysis the inputs group is swapped to player track group which control the player operations, track connections and track setup.

Source dispatcher groups

The Inputs, Outputs, Tachometers, Events and Filters groups operates in the same way.

The External sync. Inputs benefit of special button due to their importance in rotating applications.

Inputs group

The inputs group allows dispatching the front-end channels to the plug-in analyzer and setting up the front-end. These settings are available in the on-line mode only.


Read front end Page for more details

Tracks group

In the Post-analysis mode, the inputs group switches to the Player management with and is replaced by the Track settings.

The Track group allows dispatching the recorded tracks to the plug-in analyzer and setting up the signal post-process. These settings are available in the post-analysis mode only.

Note: Clicking on the bottom right icon (File:Reports Tools Ribbons 327.png) opens the player plug-in properties dialog allowing a full access to all the settings.

  •  Connect Tracks: This button allows dispatching the signal tracks (all type) to the analysis modules.
  •  Record num: Define the record number (i.e. a section in the file defined during the acquisition) to be post-processed.
  • File:Reports Tools Ribbons 330.pngStart offset: Define the start position of the signal to post-process or playback on the generators: (0 <= Start Offset < Stop Offset).
  • File:Reports Tools Ribbons 331.pngStop offset: Define the end position of the signal to post-process or playback on the generators: (Start Offset < Stop Offset <= selected record duration).

Note: The Start, Stop and Record num can be handled directly from the Player file or Player Zoomed signal windows with the start and stop cursors and/or the bottom slide


  Playback mode: Allows choosing between a continuous and a step/step post-process. .

  • Continuous: the signal analyses are processed as fast as possible between the start and stop offset.
  • Time step: the signal analyses are processed step by step. The step duration is defined by the Step setting (see hereafter). Each new step is manually (or automated by a macro) triggered through the Next step setting (see hereafter)


  •  Step: defines the time duration if play back step in the "Time step" analysis mode. The player switches to "pause" every "time step" second.
See Chapter 1 ASB - § Player for details
  •  Next step: defines the time duration if play back step in the "Time step" analysis mode. The player switches to "pause" every "time step".

Read Player page for details.

Recorder group

This group controls the recorder plug-in setup.

File:Reports Tools Ribbons 337.png Clicking on this bottom right icon opens the recorder plug-in properties dialog allowing a full access to all the settings.

  •   Bandwidths: Opens the bandwidths definition dialog.

The recorder support up to 4 different bandwidths:

Type Range Mode
FS 1 2.048 S/s to FSF User define
FS 2 2.048 S/s to FSF User define
Ext. Synch Front-end Sampling Freq (FSF) Automatic
Parametric inputs 15 Hz Fixed
See Chapter 1 ASB - § Recorder for details

  Mode: defines the time frame recording type. It can be:

  • Start to stop: Records between a start and a stop event (can be run/stop)
  • Start to time: Records for a fixed duration after a start event (can be run)
  • Time to Stop: Records a fixed duration until a stop event (can be the manual stop)
See Chapter 1 ASB - § Recorder/Mode for details
  •   Records: defines the maximum number of records in the signal file.

See Chapter 1 ASB - § Recorder/Mode for details


  •   Available: Display the maximum possible recording duration depending the current recorder setup. Read only. The max duration is computed from the free space of the selected hard disk, the number of tracks (and their corresponding sampling frequency) and the number of records

Note in time to stop, the max duration may also be limited by the local available memory (PC/Analyzer) for the description blocks. See Chapter 1 ASB - § Recorder/Mode for details


  • Used Space: gives a visual overview of the disk occupation.
Outputs group

Manages the generated signal on the front-end outputs (generators)

Read outptut page for details.

Tachometers group

Manage the tachometer resources. This group allows selecting the tach type (source, setup) and associates it with the plug-in analyzers and waterfall

See tachometer page for details

Events group

Manage the event and corresponding triggers. This group allows selecting the event type (source, setup) and associates it with the plug-in analyzers triggers

The left button (Associate to) allows dispatching the different possible event (internal or external) to the plug-in analyzers.

The 2 others items open the corresponding event detection setup.

Associate to: This button opens the corresponding Event properties. The opened dialog shows both the source signal setup and the detection settings (may be spitted in different tabs) See Chapter 1 ASB - § Connection wizard for details

  • Events properties: This button opens the corresponding Events properties dialog for setup.

The available event types are:

Edge: Detect when the signal from an input or a recorded track cross a threshold.

Level: Detect when a signal (from parametric input or statistical extraction form the TDA or monitor) is below or above a level

Delta-Level: Same as the Level but generates an event at each step

RPM: Detect when a tachometer is below or above a specified angular speed

Delta-RPM: Same as RPM but generates an event at each step

Periodic: Generates events periodically at a fixed rate

Combined: Generates an event which is the result of a combination of 2 events. Possible combinations are: OR, AND and AFTER.

User: Generates an event when the operator presses the corresponding event button in the software/remote controller interface.

External synch: Properties of the Ext synch trigger inputs. See Chapter 1 ASB - § Resources/Events for details

Filters group

Manage the filters definition and position. These filters operate on the time domain series. They can be applied in various locations onto the signal process (Inputs, Plug-in channels, Outputs, Player tracks)

The left button (Apply to) allows dispatching the filters to the different possible location in the signal process..

The second button allows selecting a filter type and opens the corresponding setup.


Apply to: This button opens the filter dispatching dialog:

Filters are available only for tachometers, outputs, aux. Outputs, edge detection, FFT, and Sync. Order and only after being activated using the ’Inputs’, ’Outputs signals’, ’Tachometers’ or ’Event’ connections previously described.

All filters are available, and by adding any filters to any channel, the properties of filters and channel selected are displayed and filters are applied in the current measurement:

See Chapter 1 ASB - § Connection wizard for details

  • Filter properties: This button opens the corresponding filter properties dialog for setup.

The available filter types are:

High/Low pass: Filter the high or low (depends on setup) frequencies of a signal

Pass/stop band: Filter or reject (depends on setup) the specified bandwidth.

Integrator: Integrates or double integrates the signal. The high pass for avoiding divergences is included. Useful for acceleration to velocity/displacement conversion.

Differentiator: Derivate the signal. Useful for torsional velocity conversion in angular acceleration See Chapter 1 ASB - § Resources/Filter for details

Warning: Due to bandwidth compatibility, the filters use is exclusive of the plug-in. I.e: Once a filter is associated to a location (ex: a plug-in channel) it can be used on the same plug-in channels only. The front-end is considered as a plug-in.