Difference between revisions of "NVGate Ribbons overview"

Jump to navigation Jump to search

NVGate Ribbons overview (view source)

Revision as of 09:01, 20 April 2020

5,517 bytes removed ,  09:01, 20 April 2020
→‎Status bar
Line 88: Line 88:


This section of the Vision tab offers a clear way to build or modify a measurement or post-analysis configuration. That covers the main steps of a measurement setup. These steps are respectively managed by the Acquisition, Analyses and Display/Graphs tabs.
This section of the Vision tab offers a clear way to build or modify a measurement or post-analysis configuration. That covers the main steps of a measurement setup. These steps are respectively managed by the Acquisition, Analyses and Display/Graphs tabs.
===Status bar===
The software interface features a status bar that shows continuously the different status of the hardware, analysis and ongoing actions.
[[Image:Reports_Tools_Ribbons_485.png|framed|none]]
The status bar is divided in 5 parts
====Control Tab====
[[Image:Reports_Tools_Ribbons_486.png|framed|none]]
Allows starting, pausing and stopping the analysis.
''See Measurement tab/control group for details''
====Plug-ins progress bars====
Shows the individual analysis status of the active plug-ins. The Progress bars appear automatically when the plug-in are activated (i.e: Inputs or tracks are connected to their channels).
Ex:
[[Image:Reports_Tools_Ribbons_487.png|framed|none]]
Each progress bar displays:
* A progress bar:
* Indicates the current averaging number or analysis duration. In case of un expectable duration, the progress bar continuously run for one side to the other.
* The color indicates the real time status:
* Green = real-time, all sample are processed
* Red = the analysis has encountered a non real-time situation, sample have not been analyzed
* A text: (''AVT) SSSS: AAA''
* AVT = Average type
* SSSS= Plug-in status (Stop, run, Paused, triggering,)
* The text color indicates the current real-time status: Red = not real-time
====Information area====
In the top left of the status bar, contextual information and progress bar appear depending the on-going action. This concern the disk download, the setup and data saving and any long duration process from NVGate.
====Inputs status LED====
Shows the inputs/signal tracks status. The same status is displayed on the front-end LED.
{|border="2" cellspacing="0" cellpadding="4" width="79%" align="center"
|
[[Image:Reports_Tools_Ribbons_488.png|framed|none]]
|The input is not active
|-
|
[[Image:Reports_Tools_Ribbons_489.png|framed|none]]
|The input is under loaded. The signal amplitude is more than 24 dB below the current input range
|-
|
[[Image:Reports_Tools_Ribbons_490.png|framed|none]]
|Normal, the signal amplitude is between -24 dB and the input range.
|-
|
[[Image:Reports_Tools_Ribbons_491.png|framed|none]]
|An overload has been detected since the last run. The signal on the input is no more overloaded
|-
|
[[Image:Reports_Tools_Ribbons_492.png|framed|none]]
|The input is overloaded.
|}<br clear="all">
[[Image:Reports_Tools_Ribbons_19.png|framed|none]]
A right-click on an active input status LED displays a pop-up menu. It is used to modify the range or any of the input parameters.
=====Front-end LED colors=====
For those who use OR36, Mobi-Pack and OR38 version 2, the front-end LED colors helps knowing what is connected and signal levels.
The LED statuses are:
{|border="2" cellspacing="0" cellpadding="4" width="100%"
|Status
|Color on Front End
|Color on XPod
|-
|Dynamic inputs normal
|bgcolor = "#59FD5D"|Green
|none
|-
|Dynamic inputs underload
|bgcolor = "#69D8FF"|Cyan (clear blue)
|none
|-
|Every input type overload
|bgcolor = "#FF0000"|<font color="#000000">Red</font>
|bgcolor = "#FF0000"|<font color="#000000">Red</font>
|-
|Parametric input normal
|bgcolor = "#FFFF00"|Yellow
|none
|-
|Parametric input underload
|bgcolor = "#CCC0D9"|Clear purple
|none
|-
|Strain gauges normal
|none
|bgcolor = "#0070C0"|<font color="#000000">Blue</font>
|-
|Thermocouple JKTNB
|none
|Yellow, Green, Brown, Pink, purple
|-
|PT 100, PT1000
|none
|Blue, Grey (low white)
|}
====Accept/reject====
This function is used to accept or reject a measurement when the FFT trigger accept mode is set to manual.
=====Accept=====
[[Image:Reports_Tools_Ribbons_493.jpg|framed|none]]
Shortcut: Ctrl <nowiki>+</nowiki> Y. Accepts the last acquisition.
=====Reject =====
[[Image:Reports_Tools_Ribbons_494.jpg|framed|none]]
Shortcut: Ctrl <nowiki>+</nowiki> N. Rejects the last acquisition.
====Battery====
Shows the battery and powering status:
{|border="2" cellspacing="0" cellpadding="4" width="72%" align="center"
|
[[Image:Reports_Tools_Ribbons_495.png|framed|none]]
|The analyzer is powered by and external power
|-
| 
[[Image:Reports_Tools_Ribbons_496.png|framed|none]]
|The analyzer is running on its battery
|}<br clear="all">
The battery level shows the available autonomy. The steps shows: 100%, 75%, 50%, 25% and 10% of battery charge. Note: The battery level is also replicated on the LCD screen of OR36 and OR38.
''See user manual for details about battery''
====Connection mode====
Depending the connection mode an analyzer or a display icon is displayed in the bottom right area.
{|border="2" cellspacing="0" cellpadding="4" width="95%"
|
[[Image:Reports_Tools_Ribbons_497.png|framed|none]]
|Office mode. The software processes data from a signal file (post-analysis) in the PC or simulates the inputs for preparing a measurement setup.
|-
|
[[Image:Reports_Tools_Ribbons_498.png|framed|none]]
|Connected mode. The hardware is connected. The software runs the analysis on the DSPs directly from the inputs or post-processing signal files from the Mobi-disk.
|}
Note: a fly over the Analyzer icon with the mouse will show the internal temperature and fan status of the analyzer.
====Acquisition status====
{|border="2" cellspacing="0" cellpadding="4" width="95%"
|
[[Image:Reports_Tools_Ribbons_499.png|framed|none]]
|The acquisition and analysis are real-time
|-
|
[[Image:Reports_Tools_Ribbons_500.png|framed|none]]
|The acquisition is not real-time. The analyzer is not working properly. Both software and hardware should be restarted
|}


===File Menu===
===File Menu===
Retrieved from "https://wiki.oros.com/index.php?title=Special:MobileDiff/2167"

Navigation menu