NVGate Recorder

The Recorder module is used to configure the time signal recording sessions (Bandwidth, Trigger).

This plug-in is used to record signals from the different types of Front-end (inputs, DC inputs or external synch inputs) or Player inputs (in Post-Analysis mode). The data can be recorded on the PC hard disk in office mode or on the OR3x hard disk in connected mode. Each recorded signal is called a track in the recorder. A recorded signal file can contain up to 4 different sampling frequencies:

• One for parametric inputs
• One for external synch inputs
• Up to 2 for other inputs

The user can select a trigger event to start the acquisition of a record and another one to stop the record.

Tutorial

Using Go to result

Just click on "record signal using go to resut windows. The track are automatically record.

Using Connect Input

For connecting, DC channels, Can Bus, Xpods,(...) we can advice to use the connect input and do a drag and drop into the recorder.

Available results:

Type	Size	Dimension	Domain	Save
RMS	1 pt	1D		Display only
Monitoring Signal	2048 pt max	2D	Compressed time	Saved on PC hard disk
Time	20, 40 or 60 GBytes<ref>Depending on the analyzer type</ref>	2D	Time	Saved on PC or on Analyzer hard disk.

RMS: RMS level measured on a recorded input signal computed on the selected bandwidth.

Monitoring signal: this result displays the compressed input signal after frequency decimation. The result is only updated during recording.

Time: time domain signal sampled at Sampled Frequency 1 or Sampled Frequency 2 automatically saved on hard disk during acquisition.

Settings

• 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. '

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

Tracks

Used to configure the track x to be recorded.

• Source: signal to be recorded. It may come from the input Front-end or from the Player in post analysis mode (see "Post analysis" topic chapter 6).
• Signal bandwidth: frequency bandwidth of the recorded track. This value is equal to the sampling frequency of the recorded signal divided by 2.56 (this factor was chosen in order to avoid any aliasing problem during frequency analysis). For the DC input this setting is forced to the input setting DC input sampling value. For the External Synchro input this setting is forced to the input setting input sampling value. For the input, the user can choose between the 2 frequencies bandwidths defined in the next settings.

Mode

This sub-module is used to define the recording set-up (record on PC hard disk or on the analyzer hard disk, the number of records...).

• Record: enables the Record plug-in. The user can choose between Off (the recorder is disabled) and On PC (in the Office mode) or On analyzer (in the Connected mode).
• Mode: defines the ways the signal is recorded.

Recorder mode	Description
Start to time	Acquisition begins on the start event and stops when the specified duration has been recorded. The user with the Stop command can stop the acquisition at any moment. If the Number of records is greater than 1, a new record is started with a new start event. When all the specified records have been recorded the plug-in goes in the Stopped state (the Stop command also forces the plug-in the Stopped state).
Start to stop	Acquisition begins on the start event and stops when the user sends a stop command or when a stop event occurs (depending on the selected stop event). If the Number of records is greater than 1, a new record is started with a new start event. When all the specified records have been recorded the plug-in goes in the Stopped state (the Stop command also forces the plug-in the Stopped state).
Time to stop	Acquisition begins on the Run command. The record stops when a stop event has been detected or when the user sends a Stop command. The duration of the recorded signal is equal to the minimum between the time elapsed since the Run command and the value specified in the Duration setting (i.e. only the last Duration seconds of the recorded inputs are saved in the signal file).

• Duration: defines the duration of a record.
• Max duration: displays the largest value for the Duration setting corresponding to the space available on the selected hard disk (PC hard disk in Office mode or the OR3x hardware HD in Connected mode). 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.

In the Time to stop mode the maximum duration is defined by the size of memory available on the hardware. For information only, if the record is on the analyzer hard drive, max size is 262144 blocks of 2048 samples. Max duration is then: (262144 * 2048)/(Sampling freq*Nb. Channels) :)

If the Record is on the PC the max size is 1048576 blocks of 2048 samples .

For "V1 hardware" the available size is either 262144 blocks of 2048 samples.

Hidden/fixed: Fixed

• Number of records : defines the number of records (1 to 1000). The recorded signal file can contain several records except in the Time to stop recorder mode (in this case only one record is available).

Note: The start and stop displayed on the picture below are not the start and stop of the analyzer, but the ones of the recorder i.e. the start and stop trigger.

• Format: defines the format of the recorded samples.

Format	Description
Normal	Samples are saved in 32 bit floating point format in SI unit
Compacted	Samples are saved in 16 bit signed integer format in logical unit (-32767<= sample value <= 32768). This format reduces the amount of hard disk space and throughput required by a factor of 2.

Trigger

This sub-module is used to you define the start and stop conditions of the signal to be recorded.

• Recorder: defines the status of the recorder ("armed" or "unarmed"). The user can choose to arm the record in order to be ready for recording. When a "Run" is made with a recorder in the status "unarmed", before running the record will be set to "armed". In the status "armed", any modifications of Front End or Recorder settings put automatically the recorder in the status "unarmed". The action of "armed" corresponds to the creation of a .lxf file (which corresponds to save the record set up).
• Start: defines an event to start the recorder. 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.

Hidden/fixed: Hidden if the recorder mode is "Time To Stop"

• Stop: defines an event to stop the recorder. 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.

Hidden/fixed: Hidden if the recorder mode is "Start To Time".

Note: If a trigger is used to stop the recorder, it doesn’t stop exactly at the event, one more block is recorded. It is useful in connected mode to stop the record on all the DSPs at the same time.

• Start delay: defines the delay between the start event date and the real beginning of the record. The user can enter a value between -131072/Fe_Max s and 360000 s (where Fe_Max is the largest sampling frequency of the recorded signals). The pre-trigger capability (Start Delay < 0) is very useful when the user wants to record the signal just before the start event.

Hidden/fixed: Hidden if the recorder mode is "Time To Stop".

• Stop delay: defines the delay between the stop event date and the real stop date. The user can enter a value between 0 s and 360000 s.

Hidden/fixed: Hidden if the recorder mode is "Start To Time".

Bandwidths

Used to set the bandwidth and sampling frequency of the signal to be recorded.

• Sampling: sampling frequency. The user can define up to 2 sampling frequencies among the available decimated values of the input setting sampling frequency.
• Bandwidth: this is the signal frequency bandwidth in the frequency domain. The frequency bandwidth is equal to the sampling frequency divided by 2.56.

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

Note: once running the recorder, the other plug-in analyzer settings cannot be modified without restarting the record.

Autobandwidth

Principle

Autobandwith manages the analysis and recording bandwidths automatically.

The nInputs 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 concerned plug-ins.

Recorder

When inputs are associated with the recorder, it adjusts the recording bandwidths channel by channel.

Deactivating the recorder's Autobandwidth allows managing the dynamic inputs sampling from the recorder. Out of the case of recording signal at lower frequency than the analysis, it is recommended to keep the recorder Autobandwidth active.

Arming

Arming of the recorder creates a backup of your record settings. Arming the recorder secure the record allowing an easy recover of the data whatever is the record ending cause.

The recorder is armed automatically when pressing the RUN This operation may take a couple of seconds.. It is possible to pre-arm the recorder allowing an immediate start of the recorder. This is available from the Measurement tab of the Vision interface:

• Unarmed record: the recorder is armed automatically by the start event. Then between the beginning of the start event and recording, there is a time ΔT corresponding to the arming (i.e. the backup of the record settings).

• Armed record: after the setup the recorder is armed (i.e. backup of the record settings allowing more security for you record). Then at any moment, when the recorder is armed, a ’Run event’ starts the record instantaneously (ΔT = 0).

Recovering records

The recorded data benefit of specific safety tools that allow recovering the data in case of failure during the record.

There are 2 type of recovery:

• Manual recovery: in the case of the initial project have been cancelled from your PC, or have been recorded with another PC, or if the project has been renamed. The recovering tools are available into the hard drive manager called from the Home tab/Disk group (Manage)

• Automatic recover: in the case of an unexpected stop of the analyzer; i.e; during a record, at the end of the record or before saving the measurement.

During the next launch of NVGate, the Disc is scanned, and then all unsaved files will be recovered if the initial project is found in the local tree diagram. The recovered measurement will be renamed with the date of record.

This recovery type can handle multi records; the recover will be based on the shorter record.

If an unexpected stop occurred (power out …), signals will be recovered and only few seconds will be lost, depending on the configuration of your record (sampling frequency, slow inputs).

For example at 1 ch @ 51.2 kS/s, a maximum of 2.5 s could be lost.

If the mode ’Time to stop’ in the recorder is selected, unsaved files will not be recovered.

Progress Bar

Depending on the recorder mode the progress bar can be a normal, backward or ’snake’ type, with text indicating the state of the recording and the time of recorded data.