Difference between revisions of "NVGate Status bar"
(Created page with "===Status bar=== The software interface features a status bar that shows continuously the different status of the hardware, analysis and ongoing actions. Image:Reports_Tool...") |
(No difference)
|
Revision as of 09:00, 20 April 2020
Status bar
The software interface features a status bar that shows continuously the different status of the hardware, analysis and ongoing actions.
The status bar is divided in 5 parts
Control Tab
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:
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.
The input is not active | |
The input is under loaded. The signal amplitude is more than 24 dB below the current input range | |
Normal, the signal amplitude is between -24 dB and the input range. | |
An overload has been detected since the last run. The signal on the input is no more overloaded | |
The input is overloaded. |
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:
Status | Color on Front End | Color on XPod |
Dynamic inputs normal | Green | none |
Dynamic inputs underload | Cyan (clear blue) | none |
Every input type overload | Red | Red |
Parametric input normal | Yellow | none |
Parametric input underload | Clear purple | none |
Strain gauges normal | none | Blue |
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
Shortcut: Ctrl + Y. Accepts the last acquisition.
Reject
Shortcut: Ctrl + N. Rejects the last acquisition.
Battery
Shows the battery and powering status:
The analyzer is powered by and external power | |
The analyzer is running on its battery |
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.
Office mode. The software processes data from a signal file (post-analysis) in the PC or simulates the inputs for preparing a measurement setup. | |
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
The acquisition and analysis are real-time | |
The acquisition is not real-time. The analyzer is not working properly. Both software and hardware should be restarted |