OROS Wiki - User contributions [en]

NVGate Sequence

2023-11-24T11:31:11Z

Anouck: /* Source format */

[[category:NVGate]]
The sequencer is used to import/export/load/view an Excel® file that contains a series of steps. These steps are executed one by one. The sequencer is generally used to operate the Roving hammer impact for modal acquisition, for example.

===Tutorial===

====Video====

<youtube>https://www.youtube.com/watch?v=0ruv0kaYWkA&list=PLwB9Ae8PGEbP-aPxWtOo1m59tingiiBIq&index=56</Youtube> 
 

The following describes the video contents. 

Step 1 – Create a sequence :
How to create a sequence from scratch. 

Step 2 – Import a sequence :
How to import an Excel sequence into NVGate. 

Step 3 – Measurement with a sequence :
Once measurement is completed, the active sequence will update a set of settings such as Label, Node, Direction… Measurements are also labeled from sequence. 

Tip – Automatic measurement with a sequence :
How to get a fully automated sequence of measurements. 

[https://orossas.sharepoint.com/:u:/g/support/Eak5MxkswKZKkDQqO2y_WssByyYLYPDIsPrL2h4OMcTwdA?e=ybQ11G Video Download offline]

====Tutorial Data Download====
- NVGate Model: List_BLADES_v1, to be copied in the NVGate Models base (usually under C:\OROS\NVGate data\Workbook Library\user). It is the setup used during the tutorial videos. 

- The sequence update_DOF.seq is included in the model folder. 

[https://orossas.sharepoint.com/:u:/g/support/EUeELwJNpolCmWiMHZNG7GQBZFgxvN8eRB6PWpUEBt5New?e=0DfToB Download here]

==Sequences group==

[[Image:Reports_Tools_Ribbons_123.png]]

{|border="0" cellspacing="0" cellpadding="4" width="100%" align="center"
|-
|[[Image:Reports_Tools_Ribbons_124.png]]
|'''Manage:''' Open the [[NVGate_Sequence#Sequence_Manager|Sequence manager]] and display the sequences list.

|-
|[[Image:Reports_Tools_Ribbons_134.png]]
|'''Enable:''' enable/disable the sequence execution. When the loaded sequence is enabled, the steps are executed each time the analyzer finish an acquisition/analysis (i.e: the general status switch to STOP)

|-
|[[Image:Reports_Tools_Ribbons_135.png]]
|'''Reset:''' reset the sequence to the initial step, execute it and disable the sequence.

|-
|[[Image:Reports_Tools_Ribbons_136.png]]
|'''Browse:''' Move to the next or previous step in the sequence. Disabled when the sequence is enabled.

|-
|[[Image:Reports_Tools_Ribbons_137.png]]
|'''Active sequence name:''' shows the loaded sequence name.

|-
|"impact node 25"
|'''Current step:''' displays the name of the current step. The current step is the one which has been executed at the last stop.

|} 

==Sequence Manager==

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

* '''Import''': Import a sequence from an Excel® file, to create a sequence in NVGate format. Sequences in NVGate format are stored in the "Sequence" directory.
Names of sequences in NVGate format are displayed by the sequence manager. See Source format for more information about sequences in Excel®.

* '''Export''': Export selected sequence (in NVGate format) to Excel®.
* '''Load''': Load selected sequence. Only the loaded sequence can be executed or opened in the sequence viewer to perform a modal analysis.
* '''View''': Open the selected sequence in the [[NVGate_Sequence#Sequence_viewer|Sequence viewer]]. Only the loaded sequence can be opened in the viewer.

A Sequence is a set of acquisitions. Each acquisition is a set of setting modifications, and it is associated to a measurement. When a measurement is performed, the acquisition associated with it, is called the current acquisition and is designated by the execution pointer (yellow arrow to the left of the sequence tree). At the end of each measurement, next acquisition becomes current and is executed to prepare the next measurement. When an acquisition is executed, all settings assigned to it are applied.

* '''Delete''': Delete the selected acquisition.
* '''Properties''': Edit sequence properties.
[[Image:Reports_Tools_Ribbons_130.png]]

When "Run after setup" is checked, a new measurement is launched automatically after the current acquisition is executed.

==Sequence viewer==

[[Image:Reports_Tools_Ribbons_126.jpg]] '''Run/Pause''': When the sequence is not running, it is launched from the current acquisition. The current acquisition is executed to prepare the measurement.

''Note: The Pause button operates at the inverse of the enable button in the sequence group ribbon.''

[[Image:Reports_Tools_Ribbons_127.jpg]] '''Reset''': Sets the execution pointer (which designates the current acquisition) to the first acquisition of the sequence.

Note: the reset button operates like the reset button in the sequence group ribbon

[[Image:Reports_Tools_Ribbons_128.jpg]] '''Back to previous''': The acquisition preceding the current acquisition becomes current and is executed.
Disabled if sequence is running.

[[Image:Reports_Tools_Ribbons_129.jpg]] '''Run next''': The acquisition following the current acquisition becomes current and is executed. Disabled if the sequence is running.

''Note: Next and previous button operates like the sequence browser arrows in the sequence group ribbon.''

* '''Jump to''': Accessible by right-clicking on the acquisition. This acquisition becomes current.

==Source format==
"Roving hammer test" sequence in Excel®.

[[Image:Reports_Tools_Ribbons_131.png|700px|none]]

"Roving hammer test" sequence in NVGate

[[Image:Reports_Tools_Ribbons_132.gif|framed|none]]

The first Excel® cell is dedicated to sequence name.

The first column contains the name of acquisitions.

The second column contains, for each acquisition, the key words which identify the NVGate configuration sub-modules.

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

Second line is composed of the keywords, which identify the NVGate configuration<nowiki>’</nowiki>s settings.

They can be found in the ASB.

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

The column called <nowiki>’</nowiki>Remote Node Label<nowiki>’</nowiki> is the field displayed by the remote controller.

Number the columns with the channel names sequentially and exclude any that are not assigned.

''Menu <nowiki>’</nowiki>Impact<nowiki>’</nowiki> of the remote controller''

These key words in the excel file, should be also defined in the Sequence.ini file which contains alias definitions. An IDNumber is associated to each setting. It can be retrieved from the ASB in NVGate by using shift <nowiki>+</nowiki> right click on the corresponding setting. Settings aliases could be modified by users.

''Part of Sequence.ini file''

Each couple (sub-module key word, setting keyword) designates a specific setting in the NVGate configuration. The value to assign to this setting is defined in the corresponding cell.

The semicolon character marks the rest of a line as a comment.

==FAQ==

'''How do I load a signal in the player using sequence?'''

[004.090.233] ==> modify the player signal file. Then, You need to have 2 columns one for the project and just next another one for the measurement. (see picture)

[[File:sequence_player.PNG|500px]]

NVGate Sequence

2023-11-24T11:30:43Z

Anouck: /* Source format */

OR3X Hardware Instruments

2023-10-24T09:49:42Z

Anouck: /* Back panel connectors description */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is powered by DC power through USB 3.0 Power Delivery protocol, which can be provided through a USB computer port or external DC supply.
When the computer can power O4 (8 W) with a single cable, the LEDs on the back panel are lit as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PCs without a USB 3.0 port. Then a backup power source is required, with a maximum of 5 volts and 2 amps.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod to the analyzer to avoid any damage. In the absence of an XPod, secure the rubber cover on the analyzer. There are two rubber covers on the XPod, which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* '''A''': Two Ethernet (1 Gb/s) connectors: One for connection to PC and one for cascade of analyzers.
Connect the PC to IN. In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode. The cables required are Category 5 un-shielded twisted-pair. Use the blue cables.
* '''B''': 2 clock synchronization connectors (100 Mb/s Ethernet). Please do not use while using a sole analyzer. Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…). On the Mobi-Pack, synchronization connectors are on the front panel
*'''C''': DC power in XLR connector (Not available on ORMP ). To be plug with the external power supply. Warning, do not mix the instrument power supply types.
* '''D''': Mobi-disk. The Mobi-Disk holds the recorded raw data. So please power off the analyzer prior removing or inserting it. When using the analyzer without the Mobi-disk plugged in, use the obturator cover to protect the internal parts of the analyzer.
* '''E''': Disk activity LED: The LED will flash while data are written on or read from the disk.
* '''F''': USB 2.0 for raw data recording: To record on an external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug your USB memory device and power on. The raw data will be saved on the memory device. Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* '''G''': Interface connector: RS-232 for remote control through RJ11 connector
*'''H''': Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* '''I''': Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
1. <nowiki>+</nowiki>5V, 3W, 1.6 A
*
2. <nowiki>+</nowiki>9V, 6W, 650 mA
*
3. <nowiki>+</nowiki>15V, 6W, 25 mA
*'''J''': High speed port: Used for connection the CAN bus probe
*'''K''': Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:48:31Z

Anouck: /* Back panel connectors description */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is powered by DC power through USB 3.0 Power Delivery protocol, which can be provided through a USB computer port or external DC supply.
When the computer can power O4 (8 W) with a single cable, the LEDs on the back panel are lit as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PCs without a USB 3.0 port. Then a backup power source is required, with a maximum of 5 volts and 2 amps.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod to the analyzer to avoid any damage. In the absence of an XPod, secure the rubber cover on the analyzer. There are two rubber covers on the XPod, which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* '''A''': Two Ethernet (1 Gb/s) connectors: One for connection to PC and one for cascade of analyzers.
Connect the PC to IN. In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode. The cables required are Category 5 un-shielded twisted-pair. Use the blue cables.
* '''B''': 2 clock synchronization connectors (100 Mb/s Ethernet). Please do not use while using a sole analyzer. Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…). On the Mobi-Pack, synchronization connectors are on the front panel
*'''C''': DC power in XLR connector (Not available on ORMP ). To be plug with the external power supply. Warning, do not mix the instrument power supply types.
* '''D''': Mobi-disk. The Mobi-Disk holds the recorded raw data. So please power off the analyzer prior removing or inserting it. When using the analyzer without the Mobi-disk plugged in, use the obturator cover to protect the internal parts of the analyzer.
* '''E''': Disk activity LED: The LED will flash while data are written on or read from the disk.
* '''F''': USB 2.0 for raw data recording: To record on an external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug your USB memory device and power on. The raw data will be saved on the memory device. Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* '''G''': Interface connector: RS-232 for remote control through RJ11 connector
*'''H''': Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* '''I''': Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
1. <nowiki>+</nowiki>5V, 3W, 1.6 A
*
2. <nowiki>+</nowiki>9V, 6W, 650 mA
*
3. <nowiki>+</nowiki>15V, 6W, 25 mA
*'''J''': High speed port: Used for connection the CAN bus probe
*'''H''': Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:41:49Z

Anouck: /* Back panel connectors description */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is powered by DC power through USB 3.0 Power Delivery protocol, which can be provided through a USB computer port or external DC supply.
When the computer can power O4 (8 W) with a single cable, the LEDs on the back panel are lit as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PCs without a USB 3.0 port. Then a backup power source is required, with a maximum of 5 volts and 2 amps.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod to the analyzer to avoid any damage. In the absence of an XPod, secure the rubber cover on the analyzer. There are two rubber covers on the XPod, which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 ""Ethernet"" (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 un-shielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ). To be plug with the external power supply. Warning, do not mix the instrument power supply types.
* Mobi-disk: The Mobi-Disk holds the recorded raw data. So please power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged in, use the obturator cover to protect the internal parts of the analyzer.
* Disk activity LED: The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording: To record on an external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug your USB memory device and power on. The raw data will be saved on the memory device. Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:34:59Z

Anouck: /* Lateral panel */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is powered by DC power through USB 3.0 Power Delivery protocol, which can be provided through a USB computer port or external DC supply.
When the computer can power O4 (8 W) with a single cable, the LEDs on the back panel are lit as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PCs without a USB 3.0 port. Then a backup power source is required, with a maximum of 5 volts and 2 amps.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod to the analyzer to avoid any damage. In the absence of an XPod, secure the rubber cover on the analyzer. There are two rubber covers on the XPod, which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:29:53Z

Anouck: /* DC POWER SUPPLY AND POWERING ON */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is powered by DC power through USB 3.0 Power Delivery protocol, which can be provided through a USB computer port or external DC supply.
When the computer can power O4 (8 W) with a single cable, the LEDs on the back panel are lit as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PCs without a USB 3.0 port. Then a backup power source is required, with a maximum of 5 volts and 2 amps.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:26:13Z

Anouck: /* O4 analyzer */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is DC power supplied through USB 3.0 Power Delivery protocol, provided by USB computer port or external DC supply.
When computer is able to power O4 (8 W) through one cable, the LEDs in the back panel are lighted as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PC without USB 3.0 port. Then a back-up power is required, with 5 volts and 2 amperes max.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:25:40Z

Anouck: /* OROS Teamwork instruments Range */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.
OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is DC power supplied through USB 3.0 Power Delivery protocol, provided by USB computer port or external DC supply.
When computer is able to power O4 (8 W) through one cable, the LEDs in the back panel are lighted as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PC without USB 3.0 port. Then a back-up power is required, with 5 volts and 2 amperes max.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:25:26Z

Anouck: /* OROS Teamwork instruments Range */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis. Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal. These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.

OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is DC power supplied through USB 3.0 Power Delivery protocol, provided by USB computer port or external DC supply.
When computer is able to power O4 (8 W) through one cable, the LEDs in the back panel are lighted as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PC without USB 3.0 port. Then a back-up power is required, with 5 volts and 2 amperes max.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:23:58Z

Anouck: /* OLD PC */

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis.

Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal.

These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.

OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is DC power supplied through USB 3.0 Power Delivery protocol, provided by USB computer port or external DC supply.
When computer is able to power O4 (8 W) through one cable, the LEDs in the back panel are lighted as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PC without USB 3.0 port. Then a back-up power is required, with 5 volts and 2 amperes max.
*
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

OR3X Hardware Instruments

2023-10-24T09:23:31Z

Anouck:

[[category:NVGate]]
===OROS Teamwork instruments Range===
This manual applies to the whole OROS Teamwork instruments range.

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

Dear customer, thank you for purchasing an OROS Teamwork instrument. The Teamwork instruments are designed to fulfill industrial applications of noise and vibration measurement and analysis.

Your new instrument covers most of the measurement situations in the Automotive, Manufacturing and Automation, Energy & Process, Aerospace and Marine industries. It applies for real-time/Post-analyses as well as recording/playback of a raw signal.

These instruments are suitable for field, on board and laboratory operations. They are also capable of remote/standalone measurements without any operator at their side.

OROS Teamwork analyzers mainly run while connected to a Windows PC that drives the control and analysis software.

===O4 analyzer===
O4 is a compact analyzer. It offers 2 or 4 dynamic inputs with 2 ext. sync.

[[Image:O4_description.png|400px|none]]

====Back Panel====
The back panel includes:

* USB-C connector for data and power supply
* USB-C connector for back-up power supply
* Mini-LEMO connector for Generator (Mini-LEMO-to-BNC adaptor is provided)

*
[[Image:O4_back_2.png|400px|none]]

====DC POWER SUPPLY AND POWERING ON====
O4 instrument is DC power supplied through USB 3.0 Power Delivery protocol, provided by USB computer port or external DC supply.
When computer is able to power O4 (8 W) through one cable, the LEDs in the back panel are lighted as shown below:

[[File:O4_power_1.png|100px]]

=====OLD PC=====
When the computer port is not powerful enough to supply O4, this could happen with old PC without USB 3.0 port. Then a back-up power is required, with 5 volts and 2 amperes max.
In case of back-up powering, please follow the instructions:
*
1. Connect the back-up power first and wait until the LED turns green

[[File:O4_power_2.png|100px]]

2. Connect the first USB port to PC and wait until the LED turns green.

[[File:O4_power_3.png|100px]]

All the connections of O4 instruments comply with SELV (Safety Extra Low Voltage) conditions.

===OR35/OR36/ORMP/OR38 Teamwork instruments===
OR35, OR36, ORMP & OR38 cover high end applications with multi-channels chassis. They offer from 4 to 32 universal inputs, 2 ext. synch, 2 generators and optional auxiliary channels supporting generators, trigger/tach and parametric inputs.

====Front Panels====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
| 
|OR38
|OR36/MP
|OR35

|-
|Inputs
|1 to 32 Universal
|1 to 16 Universals 
|4 or 8 Universal <nowiki>+</nowiki> 2 Dynamic

|-
|Outputs
|Generators 1 & 2
|Generators 1 & 2
|Generators 1 & 2

|-
| Triggers
|External Sync.1 & 2
|External Sync 1 & 2
|External Sync 1 & 2 in // with Dynamic 9 & 10

|-
|Auxiliaries
|4 DC, GEN or Ext synch (Depending on the purchased options)
|4 DC, GEN or Ext synch
|No

|-
|Overview
|
[[Image:Usersmanual_56.jpg|framed|none]]

|
[[Image:Usersmanual_57.jpg|framed|none]]

|
[[Image:Usersmanual_58.gif|framed|none]]

|}

The universal inputs gather both dynamics and parametric input in the same board and connectors. The type of use of the universal inputs is selectable by software (NVGate®) during the analyzer operations. The universal inputs fulfill all the performances, precision and operability of each specific input type. All the connections are Very Low Safety Voltage.

=====Inputs LED colors=====
For each input connector LED shows the current status:

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Color
|Input type
|Signal level

|-
|bgcolor = "#92D050"|Green
|Dynamic
|FS<ref>Full scale</ref>-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#00B0F0"|Cyan
|Dynamic
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|bgcolor = "#FF0000"|Red
|Dynamic/Parametric
|Signal <nowiki>></nowiki> FS (Overload)

|-
|bgcolor = "#FFFF00"|Yellow
|Parametric
|FS-30 dB <nowiki><</nowiki> Signal <nowiki><</nowiki> FS

|-
|bgcolor = "#7030A0"|Purple
|Parametric
|0 <nowiki><</nowiki> Signal <nowiki><</nowiki> FS-30 dB

|-
|Off
|Inactive
|N.A.

|}

====Lateral panel====
With the universal inputs and the adapted connection kit (Not available for ORMP), the OR35, OR36 and OR38 can hold signal conditioning modules called XPod (dockable e'''XP'''ander m'''od'''ule).

[[Image:Usersmanual_32.jpg|framed|none]]

The XPod is a device that can be fixed on the OR35/OR36/OR38 side. Each XPod is associated to a block of 8 inputs.

The following optional XPod are available:

* Bridge signal conditioning for strain gauges, dynamic pressure and force measurements.
* Thermocouple and RTDs for temperature measurements.
To fix the XPod on the analyzer:

1.
'''Warning:''' do not plug or unplug the XPod when the analyzer is powered on, shut it down for this operation.

2. Lock the XPod hook in the notch on the back of the analyzer,

3. Lower the XPod to the corresponding connector on the top of the analyzer,

4. Secure the XPod on the analyzer with the screw on the extension key of the XPod


{| class="wikitable"
|-
! 1 !! 2 !! 3
|-
| [[Image:Usersmanual_60.gif|framed|none]] || [[Image:Usersmanual_61.gif|framed|none]] || [[Image:Usersmanual_62.gif|framed|none]]
|}


'''Note''': When travelling, fix the XPod on the analyzer to avoid any damages. When there is no XPod, fix the rubber cover on the analyzer. There are two rubber covers on the XPod which allows having a cover left if one is lost.

====Back Panels====
The back panel supports the connectivity, power supply and accessories connections.

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

OR35 instrument complies with SELV (Safety Extra Low Voltage) conditions.

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

All the connections of OR36, ORMP and OR38 instruments comply with SELV (Safety Extra Low Voltage) conditions.

=====Back panel connectors description=====
* 2 Ethernet (1 Gb/s) connectors for connection to PC and cascade of analyzers.
* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
* 2 clock synchronization connectors (100 Mb/s Ethernet)
* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
* On the Mobi-Pack, synchronization connectors are on the front panel
* DC power in XLR connector (Not available on ORMP ).
To be plug with the external power supply.

Warning, do not mix the instrument power supply types.
* Mobi-disk. The Mobi-Disk holds the recorded raw data.
*
, Caution, power off the analyzer prior removing or inserting it.
* When using the analyzer without the Mobi-disk plugged-in, use the obturator cover to protect the internal part of the analyzer
* Disk activity LED. The LED will flash while data are written on or read from the disk.
* USB 2.0 for raw data recording. To record on a external disk, power off the analyzer, remove the Mobi-Disk (put the obturator cover), plug you USB memory device and power on. The raw data will be saved on the memory device.
Caution, the write speed on your memory device may lead to a throughput error, check the performance before using it for actual measurements
* Interface connector: RS-232 for remote control through RJ11 connector
* Reset. To be used when your analyzer does no respond to any command. Insert a paper clip in the hole and press smoothly.
* Accessory Power supply. This connector provides power supply for external use (transducer, tachometer, etc… power supply). The available voltage and power are:
* <nowiki>+</nowiki>5V, 3W, 1.6 A
* <nowiki>+</nowiki>9V, 6W, 650 mA
* <nowiki>+</nowiki>15V, 6W, 25 mA
* High speed port: Used for connection the CAN bus probe
* Ground connection. Use this screw to connect the analyzer to the ground potential

====DC Power supply====

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

=====OR35 connector=====

[[Image:Usersmanual_31.jpg|framed|none]]

OR35 features a coaxial connector. Center is positive terminal; outer ring is negative and ground terminal:

The analyzers may be powered from an external DC voltage6 to replace the external power supply. The power voltage and current must fulfill the following conditions:

----

=====OR35 Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 30 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|10 V to 28 V

|-
|Overload protection
|Absolute maximum <nowiki><</nowiki> 40 V / <nowiki>></nowiki> 31 V poles are disconnected

|-
|rowspan = "4"|Battery
|Type
|Built-in 89 Wh Li-ion 8 modules (UN38.3 certified)

|-
|Autonomy
|'''3 h '''(4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 12V

|}

=====OR36/ORMP Power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 60 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 1.7 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in (Not applicable to the ORMP)
|Range
|12 V to 28 V (DC voltage <nowiki><</nowiki> 17 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 11 modules (no memory effect)

|-
|Autonomy
|'''2 h ('''4 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''2 h''' '''30 min''' (typical)

|-
|bgcolor = "#D9D9D9"|Charge conditions
|bgcolor = "#D9D9D9"|DC power supply <nowiki>></nowiki> 18 V

|}

=====OR38 power supply=====

{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Power
|colspan = "2"|<nowiki><</nowiki> 100 VA

|-
|rowspan = "2"|External AC Power supply
|Voltage
|110 to 220 VAC / 2.0 A max

|-
|Frequency
|50/60 Hz

|-
|rowspan = "2"|DC in
|Range
|15 V to 28 V (DC voltage <nowiki><</nowiki> 22 V will discard the battery)

|-
|Overload protection
|'''31 V''' (over this voltage DC poles are short-circuited)

|-
|rowspan = "4"|Battery
|Type
|'''NiMh''' 17 modules (no memory effect)

|-
|Autonomy
|'''2 h '''(8 ch 1 DSP 12.8 kS/s)

|-
|Charge time
|'''3 h''' (typical)

|-
|Charge conditions
|DC power supply <nowiki>></nowiki> 24 V

|}

Note: All External power supplies accept mains supply voltage fluctuations up to ±10 % of the nominal voltage; Transient overvoltage up to the levels of Cat II; Temporary overvoltage occurring on the mains power supply.

Note: Externals power supplies provided by OROS must operate in the range of -10°C to <nowiki>+</nowiki>40 °C

===Batteries===
OROS Teamwork instruments contains an internal battery block particularly useful for autonomous operations (except for OR34) or in case of temporary power failure (all OROS Teamwork instruments).

The batteries of OROS Teamwork instruments are designed to provide maximum trouble-free life. To obtain the longest battery life, please follow the following advice:

* Caution: Temperature above normal room temperature will shorten battery life. If OROS Teamwork instruments is stored or shipped at more than 40°C (104°F), recharge it before running the system.
* Charge the battery in cool area. The battery is charging when an OROS Teamwork instrument is plugged to a power supply. Charge stops when the Front Panel indicates 100%.
* Caution: Never store OROS Teamwork instruments with a discharged battery.
All batteries gradually lose their charge (the higher the temperature is, the quicker the batteries lose their charge). If you store your system for a long time without using it, recharge the batteries every two or three months. This practice will extend battery life.

===Fan===
The cooling fan is used to reduce the temperature inside OROS Teamwork instruments. From the Front Panel the user can manually switch it on or switch off (for very sensitive acoustic measurements).

The fan operation will be automatically forced when the temperature inside the OROS Teamwork instruments reaches 50°C and stops at 43°C.

Warning: Do not cover the Teamwork instrument in order to let the ventilation operate properly.

====Temperature and fan management====

{|border="2" cellspacing="0" cellpadding="4" width="80%" align="center"
|align = "center"|'''Internal temp'''
|align = "center"|'''System status'''
|align = "center"|'''Fan'''

|-
|align = "right" bgcolor = "#FF0000"|70°C (158 °F)
|align = "center" bgcolor = "#FF0000"|Absolute maximum rating
|align = "center" bgcolor = "#FF0000"|Off

|-
|align = "right" bgcolor = "#FFC000"|65°C (149 °F)
|align = "center" bgcolor = "#FFC000"|Forced shutdown, do not operate
|align = "center" bgcolor = "#FFC000"|Off

|-
|align = "right" bgcolor = "#FFFF00"|60°C (140 °F)
|align = "center" bgcolor = "#FFFF00"|Normal
|align = "center" bgcolor = "#FFFF00"|Forced max

|-
|align = "right" bgcolor = "#92D050"|50°C (122 °F)
|align = "center" bgcolor = "#92D050" rowspan = "2"|Normal
|align = "center" bgcolor = "#92D050" rowspan = "2"|Automatic Fast

|-
|align = "right" bgcolor = "#92D050"|45°C (113 °F)

|-
|align = "right" bgcolor = "#00B050"|40°C (104 °F)
|align = "center" bgcolor = "#00B050" rowspan = "2"|Normal
|align = "center" bgcolor = "#00B050" rowspan = "2"|Automatic Slow

|-
|align = "right" bgcolor = "#00B050"|35°C (95 °F)

|-
|align = "right" bgcolor = "#D9D9D9"|30°C (86 °F)
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Normal
|align = "center" bgcolor = "#D9D9D9" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#D9D9D9"|0°C (32 °F)

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>5°C (23 °F)
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|OK with 1 min/°C Warmup
|align = "center" bgcolor = "#B4C6E7" rowspan = "2"|Off

|-
|align = "right" bgcolor = "#B4C6E7"|<nowiki>-</nowiki>20°C (-4 °F)

|-
|align = "right" bgcolor = "#8EA9DB"|<nowiki>-</nowiki>25°C (-13 °F)
|align = "center" bgcolor = "#8EA9DB"|Storage, do not operate
|align = "center" bgcolor = "#8EA9DB"|Off

|-
|align = "right" bgcolor = "#0070C0"|<nowiki>-</nowiki>35°C (-31 °F)
|align = "center" bgcolor = "#0070C0"|Absolute minimum rating
|align = "center" bgcolor = "#0070C0"|Off

|} 

====Powering on/off OR35- OR36/ORMP - OR38====
The Teamwork instrument feature an LCD screen on the front panel.

'''To start OR35/OR36/ORMP/OR38 instruments''', press the On/Off button of the Front Panel. "OROS-3 Series Powering up" is displayed on the LCD screen.

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

Instrument auto-tests are performed until "System OK " appears on the screen or "Ready D-rec" if the D-rec option is available.

If auto-tests return an error message, please contact your OROS Support.

'''Power off OR35/OR36/ORMP/OR38 instruments''' by pressing on the On/Off button of the front panel for a few seconds until "Shutdown" appears on the screen or by pressing on the right-hand button of the front panel «", then on the second button for "S" (Shutdown) and confirm by pressing "Y" (Yes).

From the LCD screen:

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

Press the right-hand button for "". The following menu is displayed:

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

This menu allows to:

* shutdown the analyzer (second button for "S")
* reset the analyzer (third button for "R")
* go back to the first menu (fourth button for ""). 

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

Answer "Y" for Yes

'''If Instrument does not respond''', press the On/Off button until it turns off. Then, power it on again after a few minutes.

NVGate Tachometer

2023-08-30T12:35:38Z

Anouck: /* Difference between speed results : RPM Profile, FFT1 Tacho in Waterfall, and Ext. angular speed in Waterfall */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

== F.A.Q ==

=== Difference between speed results : RPM Profile, FFT1 Tacho in Waterfall, and Ext. angular speed in Waterfall ===

'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

NVGate Tachometer

2023-08-30T12:35:23Z

Anouck: /* F.A.Q */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

== F.A.Q ==

== Difference between speed results : RPM Profile, FFT1 Tacho in Waterfall, and Ext. angular speed in Waterfall ==

'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

NVGate Tachometer

2023-08-30T12:34:52Z

Anouck: /* F.A.Q */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

=== F.A.Q ===
== Difference between speed results : RPM Profile, FFT1 Tacho in Waterfall, and Ext. angular speed in Waterfall ==

'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

NVGate Tachometer

2023-08-30T12:34:21Z

Anouck: /* Extract tach from FFT waterfall and edit tachometer */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

=== F.A.Q ===
*''' Difference between speed results : RPM Profile, FFT1 Tacho in Waterfall, and Ext. angular speed in Waterfall'''

'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

NVGate Tachometer

2023-08-30T12:32:16Z

Anouck: /* Extract tach from FFT waterfall and edit tachometer */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

NVGate Tachometer

2023-08-30T12:29:10Z

Anouck:

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

*'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

The RPM centering and averaging is done in the analysis plug-in prior to be connected to the
waterfall. To use the centered tach simply add the said tachometer to the corresponding plug-in
(FFTn or SOAn). These additional tachometers are available in the waterfall as soon as one of the
result of the plug-in is added to the waterfall.
*1. Add Tach to the Plug-in,
*2. Add plug-in results (Spectra, orders, etc..) to the waterfall,
*3. Display the waterfall,
*4. Select the Plug-in Tach, as a tachometer and reference

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

'''Colored floor in 3D displays'''

The colored 3D displays use palette that define the color of each level. With NVGate V9.10 the
bottom of the Y scale remain colored with the lowest defined level.
[[Image:RPM4.png|framed|none]]

'''Oversampled waterfall collections'''

The waterfall collects and synchronizes results generated by various calculations (plug-ins, front
end, tachometers, monitor). NVGate V9.10 allows collecting the results at very different rates. This
is useful while measuring at different spectral resolutions (which influence the result availability
rate) or with more frequent references like tachometers.
[[Image:RPM5.png|framed|none]]
Ex: Using a short periodic trigger (ex 100 ms) the waterfall collect a smooth RPM profile and the
spectra at lower speed.

File:RPM5.png

2023-08-30T12:27:35Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:RPM4.png

2023-08-30T12:27:35Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:RPM3.png

2023-08-30T12:27:34Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

NVGate Tachometer

2023-08-30T12:23:29Z

Anouck:

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

*'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

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

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[Image:RPM2.png|framed|none]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[Image:CT1.png|framed|none]]

NVGate Tachometer

2023-08-30T12:22:08Z

Anouck: /* Extract tach from FFT waterfall and edit tachometer */

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

*'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

[[File:RPM1.png|thumb]]

This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[File:RPM2.png|thumb]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[File:CT1.png|thumb]]

File:CT1.png

2023-08-30T12:21:26Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:RPM2.png

2023-08-30T12:21:26Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:RPM1.png

2023-08-30T12:21:25Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

NVGate Tachometer

2023-08-30T12:20:38Z

Anouck:

[[category:NVGate]]
NVGate can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.

==Connect==

<Youtube>https://www.youtube.com/watch?v=H3smiuy2QCM</Youtube>

{| class="wikitable"
|-
! Using GoToResult !! Using Ribbon ASB
|-
| On this window, only input tachometer and ext. synch tachometers are available. To use it, just open the GoToResults windows, then select the tachometer. [[File:tach3.png|framed|none]] || For more advanced options, on ribbon/acquisition tab, the left button (''Select'') allows dispatching the different tachometer type to the plug-in analyzers. The others items open the corresponding event detection setup.[[File:tach1.png|framed|none]] ''Select:'' '' Shows the list of available tachometer sources and allows plugging it, to the plug-in, events and waterfall.
|}

==Available results and display==

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="91%"
|'''Type'''
|'''Size'''
|'''Dimension'''
|'''Domain'''
|'''Save'''

|-
|Filtered signal
|256 pt
|2D
|time
|Display only

|-
|Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Ext Tach Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|Virtual Angular speed
|1 pt
|1D
|Angular speed
|Display only

|-
|RPM Profile
|2048 pt max
|2D
|time
|Display only

|-
|Ext Tach Profile
|2048 pt max
|2D
|time
|Display only

|-
|Virtual Tach Profile
|2048 pt max
|2D
|time
|Display only

|}

All tachs can be used as a source for the RPM and Delta RPM event type and/or for order analysis (Constant band tracking of the FFT plug-in and Synchronous Order Analysis plug-in analyzers), and/or as a reference for the waterfall plug-in.

'''Display'''

{| class="wikitable"
|-
! Using GoToResult !! Using Add/remove windows
|-
| You can display scalar values, or profiles using GoToResult windows.[[File:tach5.png|600px|none]] First activate a tachometer in a window plug in. Second, a new tab is created: "tachometer". Select the profile or scalar value || For advanced results, use the: add/remove windows.
[[File:tach6.png|600px|none]]
Tips : to create Advanced tachometer profile, put the scalar of tachometer into the [[NVGate_Waterfall|waterfall]]
|}

==Tachometer Source==

In NVGate we can set up several tachometer sources, including virtual tachometers in the case of multiple shafts. Tachometers are based on signals that provide pulses/revolution from a CAN bus or from a voltage proportional to the angular velocity.
[[File:tach4.png|framed|none]]

The tach probe that provides the pulse signal can be connected either on an input or on an External sync. The External sync is sampled at 64* the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

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

===Input: Tachs===

[[Image:Reports_Tools_Ribbons_354.png]]''Inputs:'' Opens the properties dialog for the tachometers based on a dynamic input.
Used to define up to 4 tachometers using signal from fast analog inputs (from the Front-end or from the Player).

* '''Source:''': the tach input signal (NONE by default). The input signal can be any Front-end input in Connected mode, on-line or any Player track in Post-analysis mode (except for the DC input and the Ext. Sync. inputs or tracks). (note : on OR35V1, Input 5 to input 8 are not able to be set as source using an OR35 analyzer.)
* '''Input filter''': adds a digital filter before the tach process. The user can choose any filter from the list of the defined filters.

* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).

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

* '''Slope''': selects the input signal slope on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''Slope'''
|'''Description'''

|-
|Rise
|Tach pulses are detected on rising edge of the input signal

|-
|Fall
|Tach pulses are detected on falling edge of the input signal

|}

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value. The user can enter any value between 0 and 36000s.

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected.

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

This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off(% period) setting value.

* '''Mixed Hold off:''' in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range). If Slope is set to RISE, the input signal must go below Threshold; Hystersis before a new pulse can be detected. If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, an input signal transition.
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Ext. Tach===

[[Image:Reports_Tools_Ribbons_355.png]]: ''Ext. Synch:''Opens the properties dialog for the tachometers based on a high speed oversampled Ext Synch input.<big>Big text</big>
In acquisition mode, the tach Ext synch comes from the frond end. 

In post analyze, we connect player track on tachometer Ext synch resource. 

====Acquisition mode====
External syncs are high speed level comparators that provides accurate events dates for the tachs and trigger. External sync is sampled at 64 time the Front-end sampling frequency in order to achieve higher precision in delay or phase measurements.

For external sync or tach signals whose frequencies overload the inputs sampling rate, an internal hardware divider is available in order to lower signal frequency. The upper frequency of the external sync must be lower than 64 times the Front-end frequency range. At input frequencies greater than 300 kHz, sensitivity can be decreased due to the electronic circuitry.

In any case the maximum frequency of a signal on an Ext Sync (before any pre-divider has been applied) is 375 kHz.

[[Image:front_end_12_1024.png|700px|none]]

In acquisition mode, Ext synch channels are front end settings.

* '''Label''': the name of this External Sync. (by default Ext. sync. n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2). The label of each External Sync is used in the result name and in all connection tools.
* '''Threshold''': the detection level.

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

* '''Slope''': the slope associated with the threshold that defines the trigger detection.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="82%" align="center"
| '''Slope'''
|'''Description'''

|-
|Rise
|The threshold is reached on rising edge of the External sync. signal

|-
|Fall
|The threshold is reached on falling edge of the External sync. signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two pulses. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. The user can enter any value between 0 and 36000s.

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

* '''Hystersis''': defines the hystersis around the threshold. The value can be adjusted between 0 and the full scale of the input signal (depending on the input range).
* If Slope is set to RISE, the input signal must go below Threshold - Hystersis before a new pulse can be detected.
* If Slope is set to FALL, the input signal must go above Threshold <nowiki>+</nowiki> Hystersis before a new pulse can be detected. This setting is used to reject false pulse detection following, for example, a transition of the input signal. This setting can be displayed in dB.
* '''Pre-''''''divider''': Hardware pre-divider is available after the edge detector and is used to reduce the frequency of the signal to be measured. When the tach is enabled, the measured speed takes into account the pre-divider setting when displaying the true RPM value. The user can enter any integer value between 1 and 255. If tach is <nowiki>’</nowiki>On<nowiki>’</nowiki> this setting it is linked to the <nowiki>’</nowiki>pulse/rev<nowiki>’</nowiki> setting.
* '''Post''''''-mutiplier:''' selection of the multiplier factor. It allows the generation of a <nowiki>’</nowiki>ExtSync<nowiki>’</nowiki> signal which the pulse frequency is multiplied by the selected factor. The user can enter any integer value between 1 and 50. This is particularly useful with slow time base as GPS or standard clock.

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

* '''Multiplier Hold off: '''defines the maximum time (expressed in percentage of the last period measured after multiplication) between a detected pulse and a simulated pulse. If a simulated pulse is detected before time has expired since the detected pulse then this pulse will not be added. In this way, the simulated signal is synchronized with the input signal. The user can enter any value between 1% and 99%.

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

* '''Physical qty'''.: the physical quantity applied to this External sync. It modifies the sensitivity and range peak units if necessary.
* '''Sensitivity''': the sensitivity of the transducer. Changing it updates the range peak.
* '''Range pk'''.: the maximum input level for this channel, from 300mV up to 40V. For a sensibility of 2 V/m/s2 those values will be divided by 2 (0.015 m/s2 and 20 m/s2) and for a gain of 0.1 those values will be multiplied by 10 (3 V and 400V). This setting can be displayed in dB.
* '''External ''''''gain''': this setting can be displayed in dB. This allows the analyzer to offset an external gain: for example if there is an external gain of 3dB, the value may be set to 3dB to retrieve the genuine amplitude of the signal.
* '''Offset comp'''.: the offset compensation in Volts.

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

* '''Coupling''': the coupling of this external sync.
[[NVGate_SOA_and_CBT_techniques#Tachometer_setup|This article compare the difference beetween coupling AC Vs DC for the tachometer phase.]]

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%" align="left"
|'''Coupling'''
|'''Description'''

|-
|AC
|AC coupling with signal ground connected to the analyzer hardware ground and a 0.35 Hz high pass filter.

|-
|DC
|DC coupling with signal ground connected to the analyzer hardware ground. It is advisable to use the DC coupling when analyzing very low frequency (<nowiki><</nowiki> 10 Hz frequency range).

|} 

* '''Mode: '''This setting allows selecting available signals generated by the Ext. synch input to be used by the NVGate analysis components.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="70%"
|'''Mode'''
|'''Description'''

|-
|Trigger
|The Input generates events only. It can be used as trigger, start and stop of plug-in analyzers and be recorded. Recorded event occurs as 0/1 V signals. Note that the trigger event remains available on any mode.

|-
|[[NVGate_Tachometer#Ext._Tach|Tach]]
|The input generates a tach signal (RPM and revolution phases) in addition to the events.

|-
|[[NVGate_Torsional|Torsional]]
|The input generates the instantaneous velocity measured with the F to V converter from a pulses train. The torsional signal is considered as a dynamic input. It appears as Tors # in the inputs list (# being the Ext sync number)

|-
|[[NVGate_Torsional|Torsional]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Same as above plus the tach signal is also available. The revolution phase correspond:
* to the missing teeth occurrence if missing teeth is <nowiki>></nowiki> 0
* to the ending of the pulse/rev counting at each revolution (no phase reference) if missing teeth setting is <nowiki>></nowiki> 0

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]]
|The detected pulses on the inputs will be used to synchronize the SOA re-sampling algorithm. The number of pulse/rev is free and may be different from the SAO resolution.

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Torsional|Tors]]
|Combine the sampling and the Torsional modes. Both angular re-sampling and instantaneous velocity are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|Tach]]
|Combine the sampling and the Tachometer modes. Both angular re-sampling and RPM measurement are provided by the input

|-
|[[NVGate_Torsional#Angular_sampling_for_SOA_analysis|Sampling]] <nowiki>+</nowiki> [[NVGate_Tachometer#Ext._Tach|tach]] <nowiki>+</nowiki> [[NVGate_Torsional|tors]]
|Combine the sampling, the Tachometer and the Torsional modes. Angular re-sampling, Tachometer speed and instantaneous velocity are provided by the input
|}

* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between 2 tach pulses used to measure RPM.
If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

''Hidden/fixed: ''Hidden if Mode is Trigger or Torsional.

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

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

* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 4092. For a non-integer number of pulses per revolution the user must use a virtual tach.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Rotation''': This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.
The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional).

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

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Max speed''': defines the highest measured angular speed. All revolutions with a speed higher than Max speed are rejected. By default Max speed is expressed in RPM. The limit of Max speed depends on the sampling frequency of the input, on the pulse/rev and on the hold off. If the Max speed value is modified, the Min speed is automatically adjusted according to a speed ratio (''MinSpeed = MaxSpeed / SpeedRatio''). The Speed Ratio value is not able to be modified.
*
The Max speed setting is also used:

* to specify the limit of Y axis of the RPM profile result.
* to compute the limit of the maximum order of the SOA plug-in analyzer.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. The user can enter any value between Max speed / 1000 and Max speed. The max Min speed and min Min speed are defined according to the Max speed and Speed ratio.
''Hidden/fixed: ''Hidden if Mode is Trigger.

* '''Missing teeth:''' [[NVGate_Torsional|read Torsional page]]

* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.
''Hidden/fixed: ''Hidden if Mode is Trigger

* '''Input filter:''' Select the filter to apply on the instantaneous angular velocity signal computed by the torsional converter. The applied bandwidth is the front-end one.
''Hidden/fixed: ''Hidden if Mode is Trigger or Tach

====In post Analyse====
Used to define up to 6 Ext Tachs, using signal from the Ext. Sync. input from the Player). This replaces the Ext Sync (with tach <nowiki>’</nowiki>On<nowiki>’</nowiki>) from the front-end, in Post-analysis. Then Ext tach is visible, on Track x connect the Ext Sync and then in the Ext tach set the source to Ext Sync.

* '''Label''': the name of the tach.
* '''Source''': the input signal of the tach (NONE by default). The input signal can be any Front end Ext. Sync. input (in Connected mode on line) or player track (in Post-analysis mode).
* '''Pulse / rev''': the number of pulses per revolution. The user can enter an integer value between 1 and 1024. For a non-integer number of pulses per revolution the user must use a virtual tach.
'''Note''': In Post-analysis, the number of pulses per revolution is added to the number entered for the acquisition.

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Threshold''': sets the signal threshold for tach pulse detection. The threshold is expressed in the same unit as for the input signal. The value can be adjusted between <nowiki>+</nowiki>/- the full scale of the input signal (depending of the input range).
* '''Slope''': selects the slope of the input signal on which a tach pulse is detected.

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="81%" align="center"
|'''Slope'''
|'''Description'''

|-
|Rise
|The tach pulses are detected on rising edge of the input signal

|-
|Fall
|The tach pulses are detected on falling edge of the input signal

|} 

* '''Hold off''': defines the minimum time (expressed in seconds) between two tach pulses used to measure angular speed. If a pulse is detected before the time has expired since the last valid pulse then the new pulse will be rejected. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value. The user can enter any value between 0 and 36000s.
* '''Hold off (% period): '''defines the minimum time (expressed in % of the last valid tach period) between two tach pulses used to measure angular speed. If a pulse is detected before this time has expired since the last valid pulse then the new pulse is rejected. This is used to reject angular speed variations that are too large. This minimum time is in fact the maximum between the Hold off setting value and the value computed using the last tach period length and the Hold off (% period) setting value.

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

* '''Mixed Hold off''': in this case, the hold off to be applied is the highest value between hold off time and hold off %.

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

'''Note: '''the hold off value in Post-Analysis is added to the time or the percentage already put for the acquisition.

* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Missing teeth:''' This setting indicates the number of possible consecutive missing teeth (no pulses). In such case depending on the active mode:
* ''Torsional:'' the system interpolates the missing pulses intervals in order to maintain the instantaneous speed at a continuous level during the missing pulses.
* ''Tach:'' the system uses the missing teeth occurrence as the phase reference.

===DC Tach===
Up to 4 tachometers using signal from DC inputs can be activated. It<nowiki>’</nowiki>s particularly interesting if a tachometric transducer which delivers voltage proportional to rotational speed is used for the measurement (the sensitivity is in Volt/RPM). The actual speed is continuously known during the rotation. Be aware that phase measurements are not accurate with the method.

====Acquisition====
[[image:DC_tach acquisition.png|framed|DC tach on connected mode]]
On acquisition mode, you need to activate a DC input on the frond tend, then activate the tach option.

'''Tach:''' On / Off. Used to activate a tachometer with an RPM level proportional to the DC level.
Rotation: Depending on the way you look at a measured shaft or on the convention you are using, the shaft may be considered as rotating clockwise or counterclockwise. This has noticeable impact on the phase of spectra and orders.

''Hidden/fixed: Hidden if Tach is Off.''

'''Average size:''' defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed[n-1] + (inst_speed[n-1] - avrg_speed[n-1]) / avrg_size.

'''Max speed:''' defines the highest measured angular speed. Speeds higher than Max speed are rejected. By default Max speed is expressed in RPM.

The Max speed setting is also used:

* To specify the limit of Y axis of the RPM profile result.
* To compute the limit of the maximum order of the SOA plug-in analyzer.
'''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size: '''defines the average number used to compute the average speed.
:'''Notes:'''

:'''- '''The DC Input '''physical quantity''' must be angular velocity.

The connection of a DC Input is possible using the wizard toolbar and especially the tachometer connection window. If a DC Input is defined as a tach by this way, the set up <nowiki>’</nowiki>tach<nowiki>’</nowiki> is automatically activated and the physical quantity is forced to angular velocity.

- The '''sensitivity''' and the '''offset''' can be automatically updated by calibrating the DC Input

====Post analyse====
[[image:DCPA.png|framed|DC Tach in PA ]]

In Post-Analyze, the DC tachs are available.

They can be activated and connected to a DC Input available in the signal loaded in the player. Then set up magnitude, sensitivity and offset allow to calibrate the DC Input in post analyze to obtain the correct values of the angular velocity.
Settings are the same in acquisition mode.

=====Extract a DC tachometer from dynamical input=====
On post analysis, if you have record a tachometer on a dynamical input, you can extract the DC of this channels using the monitor. Then, define a DC tachometer with the value "monitor DC". The process is as follow :

* Open the ribbon Analyses / Monitor / Inputs button.
* Select the DC tach Track in one Monitor channel.
* From the ASB, add a DC tach and select the ''Mon'' of selected input as a source.

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

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

The DC tach is then available for any tachometer usage.

===Fractional Tachs===

[[Image:Reports_Tools_Ribbons_356.png]]: ''Fractional:'' '' Opens the properties dialog for the tachometers that derives from another one. Fractional tach. computes RPM speed for a non accessible shaft by using gear ratio setting.'' ''Adapted for gear boxes and transmissions.
Note: the fractional tach. cannot be settled from the ''Vision'' interface, use the ASB for it.
Used to define up to 4 fractional tachs using data from the tach or the Ext Tach.

Virtual tachs computes RPM speed for a not accessible shaft by using gear ratio setting.

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

* '''Label''': the name of the output tach.
* '''Source''': the source of a virtual tach can be any tach or Ext. tach.
* '''Tach ratio''': this is the ratio between the output angular speed and the input angular speed. This setting is defined by the product of 2 fractions: N1/D1 * N2/D2 where N1, D1, N2 and D2 are integer values. Tach.1 / Tach. Ratio maximum value cannot be higher than 100.
[[File:Tach ratio.png|framed|none]]

* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefine a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.

===Simulated tachometer===
''This option is available for customers owning the FFTDiag option.''

This feature will allow you to simulate a tachometer with a fixed speed for your measurement. This is useful''' when using a real tachometer sensor is not possible''' and your shaft is rotating at steady speed.

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

''Setting up the simulated tach''

You can use this tachometer as any tachometers to '''calculate order spectrums''' or save it as a result.

===Combined Tach===
[[Image:Reports_Tools_Ribbons_357.png]]: ''Combined:'' '' Opens the properties dialog for the tachometers computed from other ones. Adapted for CVT. Note: the combined tach cannot be settled from the ''Vision'' interface, use the ASB for it.

====Application====
The main application is in automotive : studying vibration due to a CVT gear box. We will first compute the speed of the belt with a [https://en.wikipedia.org/wiki/Continuously_variable_transmission continuously variable transmission (CVT)]deducing by the speed of the 2 shafts. Then, with this belt speed, we can deduce vibration due to this belt using waterfall or order tracking techniques.
[[File:CVT1.png|framed|none]]
Exemple of study in CVT Vibration : https://www.hindawi.com/journals/sv/2015/857978/

====How to use====
This module allows computing tachometer information (Speed, Phase) relatively to 2 measured tachometers. Up to 4 different combined tachs can be computed simultaneously. The combined tach can be used as any other standard tach.

* '''Label''': the name of the output tach.
* '''Source 1 & 2''': the calculation sources can be any tach or Ext. tach. Source 1 is called Rpm 1 and Source 2 is called Rpm2 in the formula.
* '''Rotation:''' This setting defines the way the phase variation is counted: clockwise or counterclockwise for each tachometer.

The rotation side is managed independently for each tachometer (Ext. sync, input, D, combined and fractional). Default setup is ''Counterclockwise'';

See ''Ext Sync §'' for details

* '''Average size''': defines the average number used to compute the average speed. Revolution number n average speed is: avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> <nowiki>+</nowiki> (inst_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki> - avrg_speed<nowiki>[</nowiki>n-1<nowiki>]</nowiki>) / avrg_size.
* '''Max speed''': predefines a maximum angular speed to preset the scale and order tracking maxima. The limit of Max speed depends on the sampling frequency of the input signal and is equal to: 60 * Fe / (2 * 2.56) for the maximum. The Max speed setting is also used:
* to specify the limit of Y axis of the RPM profile result
* to compute the limit of the maximum order of the SOA plug-in analyzer.
* '''Min speed''': defines the lowest measured angular speed. All revolutions with a speed lower than Min speed are forced to 0 RPM. By default Min speed is expressed in RPM. Min speed is automatically adjusted to Max speed/1000 but it is possible to go lower.
* '''Formula''': Allows editing the computation formula. The formula uses RPM1 as the speed of Source 1 and RPM2 as the speed of source 2. The computed tach speed is the result of the last line of the editor.
'''Copy/paste '''from or to a text editor are possible, to simplify the storage of different formula

'''Attention''': ''' '''All computation are done in SI unit (i.e: Rad/sec) the constant value must be expresses in Rad/sec.

Hereafter an example of computation of the belt speed in a car CVT:

R=97/2

K2=4*R*Pi/2

K3=2*R/Pi/120

Rt=Rpm1/Rpm2

Rtp1=Rt-1

Rtm1=Rt-1

R1=K2/Gp1

R2=1-K3*SQRT(Rtm1/Rtp1)

R1*R2*Rpm1

The formula editor accepts various math operators and functions such as square root, logarithms and power allowing polynomial equations. The following table gives the syntax of the operators and functions;

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''In/out'''''
|'''''Description'''''

|-
|'''Chi'''
|Channel i level

|-
|'''N.A.'''
|The output level is the result of the last line in the editor

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="90%"
|'''''Operator'''''
|'''''Description'''''

|-
|'''<nowiki>+</nowiki>'''
|Parameter or constant addition with another parameter or constant

|-
|'''-'''
|Parameter or constant subtraction from another parameter or constant

|-
|'''<nowiki>*</nowiki>''' 
|Parameter or constant multiplication by another parameter or constant

|-
|'''/'''
|Parameter or constant division by another parameter or constant

|-
|'''<nowiki>^</nowiki>'''
|Parameter or constant powered by another parameter or constant

|-
|'''='''
|Parameter affectation with the expression result at the right of sign

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''If(c, t, f)'''
|Returns '''t''' if '''c''' is true or '''f''' if c is false (ex of '''c''': I <nowiki>></nowiki>4)

|-
|'''Rint(x)'''
|Returns the nearest integer of x

|-
|'''Sign(x)'''
|Returns -1 if x <nowiki><</nowiki> 0, 0 if x = 0 or 1 if x <nowiki>></nowiki> 0

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="86%"
|'''''Function'''''
|'''''Description'''''

|-
|'''Sin(x)'''
|Returns the sine of expression or parameter x

|-
|'''Cos(x)'''
|Returns the cosine of expression or parameter x

|-
|'''Tan(x)'''
|Returns the tangent of expression or parameter x

|-
|'''ASin(x)'''
|Returns the arc sine of expression or parameter x

|-
|'''ACos(x)'''
|Returns the arc cosine of expression or parameter x

|-
|'''ATan(x)'''
|Returns the arc tangent of expression or parameter x

|-
|'''Sinh(x)'''
|Returns the hyperbolic sine of expression or parameter x

|-
|'''Cosh(x)'''
|Returns the hyperbolic cosine of expression or parameter x

|-
|'''Tanh(x)'''
|Returns the hyperbolic tangent of expression or parameter x

|-
|'''ASinh(x)'''
|Returns the hyperbolic arc sine of expression or parameter x

|-
|'''ACosh(x)'''
|Returns the hyperbolic arc cosine of expression or parameter x

|-
|'''ATanh(x)'''
|Returns the hyperbolic arc tangent of expression or parameter x

|-
|'''Log2(x)'''
|Returns the base 2 logarithm of expression or parameter x

|-
|'''Log10(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Log(x)'''
|Returns the base 10 logarithm of expression or parameter x

|-
|'''Ln(x)'''
|Returns the base e (natural) logarithm of expression or parameter x

|-
|'''Exp(x)'''
|Returns the exponential of expression or parameter x

|-
|'''Sqrt(x)'''
|Returns the square root of expression or parameter x

|-
|'''Abs(x)'''
|Returns the absolute value of expression or parameter x

|-
|'''Min(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Max(x,y,…)'''
|Returns the minimum level of listed parameters

|-
|'''Sum(x,y,…)'''
|Returns the sum of listed parameters

|-
|'''Avg(x,y,…)'''
|Returns the average level of listed parameters

|}

{|class="wikitable" style="background:white" border="2" cellspacing="0" cellpadding="4" width="92%"
|'''''Predefined'''''
|'''''Description'''''

|-
|'''pi'''
|Constant pi (3.1416…). Do not declare any constant with this name

|-
|'''e'''
|Constant e (2.718). Do not declare any constant with this name

|}

Constants and parameters can be defined (except ''pi'' and ''e'') using the = sign; eg: ''var1 = pi * 2'' or ''var2 = rpm1/2''. The constants may be defined only once.

Parameter/constant names must start with a letter and may be ended by a number.

The dot (.) is always the decimal separator independently from the OS preferences and the comma (,) is used as parameter separator.

The editor does not check the dimension of this result. The content of the formula can be copy/paste from any text editor.

===RPM Profiles===
Defines the RPM profile window display.

*[[Image:Reports_Tools_Ribbons_358.png]]: ''Profile:'' ''Set up the tachometer profiles duration. These graphs are available for the Tachometer module in the Add/Remove graph dialog.(from 10s to 1200s).
The profile displays continuously the tachometer speeds with a memory depth defined by the ''profile ''setting.

*[[Image:Reports_Tools_Ribbons_359.png]]: ''Resolution:'' defines the shortest time between 2 angular speed values saved in the profile.

*Hidden/fixed: fixed to a value equal to Duration profile / 2048.

===Extract tach from FFT waterfall and edit tachometer===
[[External_Tools:_TachTool|Read this page]]

*'''Tachometer centered on FFT/SOA blocks'''

This allows centering tachometer speed at the center of the FFT/SOA trigger block(s). It is useful with long trigger blocks (High resolution analyses) to perfectly match the actual data with the order cursor or section.

'''With classical tach:'''
The RPM is collected at the end of the analysis block

[[File:RPM1.png|thumb]]
This situation leads to an offset in the waterfall calculation of the orders (cursors, sections). For a
run up, as the angular speed is over evaluated, the order calculation is lower than the actual ones.

'''With centered tach:'''
The RPM is calculated as the average speed during the block duration to be synchronized with the
analyzed data.
[[File:RPM2.png|thumb]]

With the centered tachometer, the orders calculations match more accurately the actual orders in
waterfall.
The computation of the angular speed takes in account the averaging, triggering and overlap used
in the plug-in.
The centered speed is calculated as:
[[File:CT1.png|thumb]]

NVGo

2023-06-22T01:27:56Z

Anouck:

[[category:NVGate]]
{{Software
|Logo= [[image:logo_NVgo.png|50px]]
|Name= NVGo
|Screenshot=[[File:MODS_51.png|120px]]
|Developers= [http://www.OROS.com Oros SA]
|Type= [https://en.wikipedia.org/wiki/Data_acquisition Data Acquisition], Recorder
|First release= 2018

|Latest Version= V1.1.10253 - June 2023
|Download= [https://orossas.sharepoint.com/:u:/g/support/Ea2Hmhqv2fNDugIkwCr4R_sBnhNm_-ceN3YVOIOK0pnSaA?e=4EnnaY .apk Here]
|Update= [https://orossas.sharepoint.com/:u:/g/support/EVewNvLHdm5Pof_c31A3kKIBRldZnjcWegziE_awsOtzVg?e=kfXKAU .apk Here]
|Operating system= [https://en.wikipedia.org/wiki/Android_(operating_system) Android] (only working with [[OR10_MODS|OR10 Hardware]])
|Language= English
|Licence = Proprietery
|website=[http://www.oros.com oros.com] and here!
}}

==NVGo==
NVGo is the MODS monitoring software for android devices. This app is designed to:

* Manage ''Templates'' for OR10 front-end and record setup.
* Adjust the front-end and recorder settings.
* Continuously monitor the signals in different domains (level, time and spectral).
* Start & stop recording.
* Add properties and comments to records.
* Manage records in OR10 memory.
===Installation===

1. Download the latest NVGo Android Package Kit (.APK) on your Tablet or smartphone. Use the download link on the right.

2. On your Android device select the NVGo .apk file, then choose install.

3. Authorize the installation of unknown sources to install it directly

''If the install is not working you need to enable APK installs on your Android device''

1) Navigate to your phone settings menu then to the security settings and/or private live protection.

2) Enable the Install from Unknown Sources option. (can be on specific autorisation)

3) Use a file browser and navigate to your download folder.

4) Tap the APK to begin the installation process.

The app should safely install.

===Connection to OR10===
1. Start NVGo from the Android device.

[[Image:MODS_46.png|700px]]

2. Power on the OR10 hardware.

3. Wait for power-on to complete, until you get the main menu on the OR10 screen.

4. Press the "Wi-Fi" button on NVGo. The Android Wi-Fi menu is displayed.

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

5. Connect to the OR10. (default password is : 12345678 )

6. Press Android back (<) button to return to NVGo.

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

Refresh the instrument list. When your OR10 appears showing "Ready", click on it to start NVGo with this instrument.

Main screen :

[[Image:MODS_49.png|700px]]

====LiveView====
''LiveView ''screen shows the spectra and trigger blocks of the 2 highlighted inputs of the left column.

[[Image:MODS_50.png|700px]]

Displayed inputs are changed by swiping the graph up/down. It is also possible to select the displayed inputs by pressing the selected input from the left column.

FFT settings allows for adjusting averaging and resolution. The
Y scale may be set to linear or log. This preference is saved in the Android device.

====Signal====
''Signal ''shows the raw data envelope of the 2 highlighted inputs of the left column.

[[Image:MODS_51.png|700px]]

Displayed inputs are changed by swiping the graph up or down. It is also possible to select the displayed inputs by pressing the selected input from the left column.

Y scale is continuously adjusted to input ranges. When the 2 active inputs show the same units, both Y scales are identical.

====Levels====
''Levels ''shows the RMS and Peak levels of all dynamic inputs together.

[[Image:MODS_52.png|700px]]

====Playback====
Press the headphone icon on bottom right of the main screen to activate the playback. The 2 active inputs (blue background on the ''Signal'' and ''LiveView'' screens) are replayed on the OR10 headphone plug. The volume is automatically adjusted.
Caution, the playback volume is dependent on the used headphone impedance. Signal amplitudes close to the range peak may generate high volume with low impedance headphone. Usage of very low impedance below 60 Ohms is not recommended. The stereo allocation of the played signals may be inverted by pressing the headphone button until the 2 background colors are inverted.

===Setting up the OR10===
====Loading a Template====
The ''Templates'' are generated and added to the OR10 memory with NVGate (see NVGate Template generation §). They are used in the same way NVGate ''Models'' is in order to setup the front-end with predefined settings. The ''Template ''properties and description will be saved in the ''Measurements ''made with it.

Press the central (''Setup'') field of the top ribbon to open the ''Template'' selection screen.
[[Image:MODS_54.png|700px]]

====Adjust the Front-End====
Input settings may be adjusted manually. Press the left (''Settings'') BNC button of the top ribbon to open the ''Front-End settings'' screen.
[[Image:MODS_55.png|700px]]

====Adjust the Sampling Frequency====
The sampling frequency is always displayed in the main screen. Simply select the desired sampling rate from the Top Ribbon drop down menu.

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

This menu is not available when the OR10 is recording.

====Adjust the Recorder====
The recorder mode and duration may be adjusted. On the left (''in Settings''), press the recorder button on the Top Ribbon to open the ''Recorder Settings'' screen. This menu is not available when the OR10 is recording.

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

You can choose between fixed duration ''Start to Time'' and manually controlled ''Start to Stop'' for recorder modes. 
[[Image:MODS_58.png|700px]]

[[Image:MODS_59.png|700px]]

For ''Start to Time'', the duration should be updated by editing the field or using the <nowiki>+</nowiki>/- buttons.

===Make a Recording===
====Start Recording====
When the OR10 setup is done, the system is ready to start acquiring and saving the input data. To start the recording, press the bottom left ''Run'' button or press the "REC" button on the OR10.

[[Image:MODS_60.png|700px]]

To stop the recording, press ''Stop ''on the bottom left or press the "REC" button on the OR10. In ''Start to Time'' mode, the recording will stop automatically when the duration time is reached.

====Save & Inform Recorded Data====
When the record is finished, the save screen is shown.

[[Image:MODS_61.png|700px]]

Recordings are saved with the predefined base name of ''Template''. A combination of 3 numbers and a letter is added to manage the multi-acquisitions:

* Letter is incremented while using the same ''Template'' for multiple acquisitions (called RUNs)
* Number is incremented and letter reset when ''Template ''is changed.
* Number and letter are automatically incremented to avoid overwriting existing files in the OR10 memory.
In that way, each RUN of a measurement type will be called: ''BaseName_102A, BaseName_102B, BaseName_102C'', etc…

All the properties with contents are saved with the recorded data. Saved properties will be associated to the ''Measurement ''when records are imported into NVGate.

====Check OR10 Memory Content====
You may browse the OR10 recorded data from NVGo. Press on the Capacity field (DAQ) which is in the Top Ribbon on the right.

[[Image:MODS_62.png|700px]]

[[Image:MODS_63.png|700px]]

The Record list screen is displayed.

NVGate Installation and Connection

2023-04-25T15:06:10Z

Anouck: /* NVGate cannot detect my dongle but my dongle is plugged in the PC, why? */

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

==F.A.Q==

====NVGate is not able to detect my dongle but my dongle is plugged into the PC, why?====

Sentinel Driver allows NVGate to communicate with the dongle. It must be installed if you are using a dongle or another USB device.
If NVGate does not detect the dongle, it might be caused by incorrectly install sentinel drive.

First verify that the Sentinel driver is properly installed.
To check open the NVGate software folder and launch "CheckConfig.exe":

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Proceed with the installation.

When this window is displayed, choose Next:
[[File:1-1.png|framed|none]]

Perform a 'Modify' installation to customise your option.
Select 'Remove' if the installation is incorrect (see below for further details).
Now click Next.

[[File:2-2.png|framed|none]]

In the custom setup, choose to delete the last three options.

[[File:4.png|framed|none]]

Perform installation by clicking on Next.

[[File:3.png|framed|none]]

This last message should appear at the end :

[[File:5.png|framed|none]]

In case it still has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

NVGate Installation and Connection

2023-04-25T15:03:25Z

Anouck:

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

==F.A.Q==

====NVGate cannot detect my dongle but my dongle is plugged in the PC, why?====

Sentinel Driver allows NVGate to communicate with the dongle. It must be installed if you are using a dongle or another USB device.
If NVGate does not detect the dongle, it might be caused by incorrectly install sentinel drive.

First verify that the Sentinel driver is properly installed.
To check open the NVGate software folder and launch "CheckConfig.exe":

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Proceed with the installation.

When this window is displayed, choose Next:
[[File:1-1.png|framed|none]]

Perform a 'Modify' installation to customise your option.
Select 'Remove' if the installation is incorrect (see below for further details).
Now click Next.

[[File:2-2.png|framed|none]]

In the custom setup, choose to delete the last three options.

[[File:4.png|framed|none]]

Perform installation by clicking on Next.

[[File:3.png|framed|none]]

This last message should appear at the end :

[[File:5.png|framed|none]]

In case it still has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

NVGate Installation and Connection

2023-04-25T15:01:46Z

Anouck:

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

==F.A.Q==

====NVGate cannot detect my dongle but my dongle is plugged in the PC, why?====

Sentinel Driver allows NVGate to communicate with the dongle. It must be installed if you are using a dongle or another USB device.
If NVGate does not detect the dongle, it might be caused by incorrectly install sentinel drive.

First verify that the Sentinel driver is properly installed.
To check open the NVGate software folder and launch "CheckConfig.exe":

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Proceed with the installation.

When this window is displayed, choose Next:
[[File:1-1.png|400px]]

Perform a 'Modify' installation to customise your option.
Select 'Remove' if the installation is incorrect (see below for further details).
Now click Next.
[[File:2-2.png|400px]]

In the custom setup, choose to delete the last three options.
[[File:4.png|400px]]

Perform installation by clicking on Next.
[[File:3.png|400px]]

This last message should appear at the end :
[[File:5.png|400px]]

In case it still has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

NVGate Installation and Connection

2023-04-25T14:52:18Z

Anouck: /* NVGate cannot detect my dongle but my dongle is pluged in the PC, why? */

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

==F.A.Q==

====NVGate cannot detect my dongle but my dongle is plugged in the PC, why?====

Sentinel Driver allows NVGate to communicate with the dongle. It must be installed if you are using a dongle or another USB device.
If NVGate does not detect the dongle, it might be caused by incorrectly install sentinel drive.

First verify that the Sentinel driver is properly installed.
To check open the NVGate software folder and launch "CheckConfig.exe":

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Proceed with the installation this way :

[[File:1-1.png|400px]]
[[File:2-2.png|400px]]
[[File:4.png|400px]]
[[File:3.png|400px]]
[[File:5.png|400px]]

In case it still has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

File:5.png

2023-04-25T14:50:08Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:1-1.png

2023-04-25T14:50:08Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:2-2.png

2023-04-25T14:50:08Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:3.png

2023-04-25T14:50:07Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

File:4.png

2023-04-25T14:50:07Z

Anouck: File uploaded with MsUpload

File uploaded with MsUpload

NVGate Installation and Connection

2023-04-25T14:41:57Z

Anouck:

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

==F.A.Q==

====NVGate cannot detect my dongle but my dongle is pluged in the PC, why?====

Sentinel Driver allows NVGate to communicate with the dongle. It must be installed if you are using a dongle or another USB device.
If NVGate does not detect the dongle it might be caused by uncorrectly install sentinel drive.

First verify that the Sentinel driver is properly installed.
To check open the NVGate software folder and launch "CheckConfig.exe":

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Proceed with the installation.

In case it still has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

NVGate Installation and Connection

2023-04-25T14:16:44Z

Anouck:

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

====Sentinel Driver====
Sentinel Driver allows NVGate to communicate with the dongle.
It is necessary to have it installed if you are using a dongle or any other USB support.

First check that Sentinel driver is correctly installed.
To check open NVGate program folder and execute “CheckConfig.exe” :

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Execute the installation.

In case it has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.

NVGate Installation and Connection

2023-04-25T14:15:18Z

Anouck:

==Get STARTED==
===NVGate installation and update===
====Preparation====
For the installation in the "Office Mode" (without OROS Teamwork instrument):

* USB dongle
* USB key containing:
** NVGate Installation Setup
** License keys

For the installation in the "Connected Mode" (with OROS Teamwork instrument connected):

* The OROS-3 Series Instrument (OR34, OR35, OR36 or OR38)
* DC power supply
* 1 Ethernet connection cable
* USB key containing
** NVGate Installation Setup
** License keys
'''Note''': before installing NVGate® check that the configuration of your PC is compatible with the minimum requirement (see the NVGate technical specifications in the appendixes)

Caution: Windows user need to have right for reading/writing on NVGate install directory (by default : C:\OROS\Programs\NVGate) and on NVGate Project Database (by default : C:\OROS\NVGate data).

====First Installation====
Plug the USB Key to your PC and run the "setup.exe" application from the NVGate directory. Then the following window is displayed:

[[Image:Install_1.png|500px]]

Click on next

Read the terms in the license agreement and select "I accept the terms in the license agreement" if you agree.

[[Image:Install_2.png|500px]]

Click on "Next <nowiki>></nowiki>", the following window is displayed:

Enter the user name, the organization.

click on "Next <nowiki>></nowiki>", the following window is displayed:

Select the location of the OR3X folder. By default, NVGate is installed on ''C:\OROS\Programs\NVGate''

Caution: It is not recommended to install NVGate or any data directory in the C:\program files directory. This may lead to malfunctions and data loss.

[[Image:Install_3.png|500px]]

Click on "Next <nowiki>></nowiki>". The following window is displayed:

Remove any OROS license dongle from the PC and Click on "Install". NVGate software installation is processed:

[[Image:Install_4.png|500px]]

During the installation, other tools needed by NVGate are automatically installed and setup like Sentinel Protection software:

Caution: Let the installation wizard proceed to the full installation. Do not abort the installation process.

At the end of installation, the keys location is requested:

Indicate the path where key files are located (by default, they are in the "Keys" directory on the CD).

Key files are: "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" (xxxx is the serial number of your OROS Teamwork instrument; yyyy is the serial number of your dongle). These keys are in the Keys directory of your NVGate installation CD. Keep it safely.

If you have several instrument and/or dongles, you will have several "h_xxxx.bat", "h_xxxx.cfg", "o_yyyy.bat" and "o_yyyy.cfg" files in the "Keys" directory

All the key files are copied to the NVGate installation directory.

====Directories setup====
This window is displayed. You can choose where your data will be located. The setup and measurement will be saved in the Project base directory. It is strongly recommended to keep the default directories.

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

Note: This NVGate environment window is also available from NVGate installation folder (as recommended: C:\OROS\Programs\NVGate). Execute the NVGateCfg.exe and NVGate environment will be displayed.

Then click on <nowiki>’</nowiki>OK, the following window is displayed:

[[Image:Usersmanual_81.jpg|500px]]

Click on "Yes to all". The NVGate software is installed:

[[Image:Install_6.png|500px]]

It is necessary to restart the computer to complete the installation of Sentinel driver. Click on "Finish".

===Connecting the analyzer to your PC===
NVGate features a dialog box dedicated to the connection and update of the analyzer(s). This dialog allows choosing between office, connected and cascaded modes.

====Connection dialog====
This dialog gathers in a unique list the office mode and the list of visible analyzers for connected mode. It is possible to select one or multiple analyzers, Teamwork instruments only, or the office mode

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

The dialog contains multiple area and commands.

* '''''Model''''' list area shows the available analyzers and the office mode.
* '''''Details''''' '''& modifications''' area shows the information related to the highlighted analyzer and allows updating it through the hyperlinks. Analyzer may be highlighted by clicking on the corresponding row out of the selection check box.
* '''''Connection Issue notification'''''. This area appears at the bottom of the Model list when an issue blocks the start of NVGate (''Start'' button is disabled)
* '''''Refresh''' ''button rescans the network and updates model column.
* '''''Resync''''' button re-launches the clock synchronization between multiple Teamwork analyzers for cascade purposes.
* '''''Start''''' button launches NVGate with the selected model; Office, Connected, Multiple analyzers

====Visibility of analyzers====
Visible analyzers are the OROS 3-Series (V2 and V3 called ''Teamwork'') connected on the same network as the PC. The connection between the PC and the visible analyzer(s) must be on the same logical network (i.e.: A company LAN with LAN switches or cascade of ''Teamwork'' analyzers).

* Analyzers already running an NVGate session are not visible in this dialog.
* Analyzers with the same IP address are visible in this dialog. IP must be changed to different ones to allow starting NVGate on multiple analyzers.
'''''Name,''''' '''''Chain''''', and '''''Status''''' columns are periodically updated.

NB: Internet Routers are supported by ''Teamwor''k analyzers only by specifying the analyzer IP address in the command line of NVGate.

====Ethernet connection rules====
On the back panel of the analyzer:

2 Ethernet 1 Gb/S connectors for connection to PC and cascade of analyzers.

* Connect the PC to IN
* In cascade mode connect the PC to first analyzer (master) to IN. Next units are daisy chained (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…) in cascaded mode.
* Cable required Category 5 unshielded twisted-pair. Use the blue cables.
2 clock synchronization connectors 100 Mb/s Ethernet

* Do not use while using a sole analyzer
* Daisy chain from Master unit to the next one in cascaded mode (OUT -<nowiki>></nowiki> IN, OUT- <nowiki>></nowiki> IN, etc…)
====Connection to the analyzer====
To connect to your analyzer, select the corresponding check box in the '''''Model''''' column. To start NVGate with the '''''Office''''' mode (Running on the PC with a dongle or the analyzer as a dongle) select the '''''Office''''' model.

The '''''Office''''' model is automatically selected if there is no visible analyzer.

In the presence of visible analyzers, NVGate will select the first connected one in the list according to the following priority:

* Firmware compatibility
* IP compatibility
* Discovery date
The '''''Start''''' button will remain disabled until the following criteria are fulfilled:

* At least one model is selected
* If it is one or plural connected one:
* The corresponding models<nowiki>’</nowiki> firmware are up to date.
* The IP address of the selected models are compatible with the PC one
NB: it is not possible to mix '''''Office''''' and '''''Connected''''' models

====Ethernet IP management====
Both PC IP and and highlighted analyzer are visible in the detail area. You can change the analyzer IP settings by clicking on the '''''analyzer IP''''' link.

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

You can update the analyzer IP manually but the most substantial and easy way to solve IP address conflicts is to use the '''''Generate Automatically''' ''button. This method will take in account all IP addresses in the logical network to avoid any conflict; even the ones not visible from this dialog.

====DHCP server from the analyzer====
This feature allows the analyzer to provide the PC<nowiki>’</nowiki>s IP address. This is available from ''Teamwork'' analyzers only.

When a ''Teamwork'' analyzer is set as a DHCP server, it will update your PC IP address when this one is set as '''''Get automatically IP address.''''' This configuration allows immediate connection of PC configured for company network.

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

The DHCP server of the analyzer is '''''Non-authoritative''''', this means that when the analyzer is connected to a local network it will not act when an '''''Authoritative''''' one exists.

====Sentinel Driver====
Sentinel Driver allows NVGate to communicate with the dongle.
It is necessary to have it installed if you are using a dongle or any other USB support.

First check that Sentinel driver is correctly installed.
To check open NVGate program folder and execute “CheckConfig.exe” :

* green check mark indicates that sentinel driver has been successfully installed
* red cross mark indicates that sentinel drive has not been installed

[[File:wiki.png|400px]]

To install the Sentinel driver, go in NVGate installation folder, select “SentinelDriver_7.6.9” folder and then select “Sentinel Protection Installer 7.6.9.exe”.
Execute the installation.

In case it has not been correctly installed :

* uninstall sentinel driver with add/remove program
* reboot the PC
* install sentinel driver 7.6.9
* reboot the PC

====Firmware update====
The firmware can be updated on demand. The '''''Connection''''' dialog detects the not-up-to-date firmware. Simply click in the '''''firmware''''' link: ''Not up-to-date'' to enter the firmware update process.

[[Image:Usersmanual_87.png|500px]]

A monitoring window is opened during the update. At the end if the update is successful, the window background goes to green. In case of unsuccessful, it goes to red.

====Change analyzer name====
While using multiple analyzers together, it is useful to set easily the identification of each chassis. Click on the '''''Name''''' Link to update the highlighted analyzer identifiers.

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

* Long name is used to identify the system in the software installation and properties dialogs
* Short names are used in NVGate settings and trace/result management.

====Connect to multiple analyzers at a time (Teamwork only)====
NVGate allows running multiple ''Teamwork instruments'' from a unique NVGate instance at a time. This allows cascaded or distributed configuration of OR36/OR38 ''Teamwork''.

The same program (NVGate.exe) and connection dialog is used. After launching NVGate you get the visible analyzer list in the connection dialog.

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

 

The '''''Chain''''' column shows the possible analyzers combination.

* The first digit is for the chain Id.
* The second one is for the analyzer position in the said chain.
* A chain is defined by a group of consecutive daisy-chained analyzers with a clock synchronization line in between.
A unique analyzer is considered as a chain.

The '''''Status''''' column shows the synchronization status.

* '''''Synchronized''''' means the analyzers sampling clocks are in phase (<nowiki><</nowiki> ±0.2° @ 20 kHz).
* It is possible to start NVGate before the synchronization process is finished; NVGate interface will wait for the achievement.
* Single chain analyzers are automatically synchronized.
If the synchronization cannot achieve (ex. cabling change) you can restart the process with the '''''ReSync''''' button.