Difference between revisions of "Monitoring Solution"

Jump to navigation Jump to search

Monitoring Solution (view source)

Revision as of 13:29, 5 May 2023

6,173 bytes removed ,  13:29, 5 May 2023
→‎Operating the Monitoring solution
Line 104: Line 104:


It could be useful to control the computer when an alert is trigged for example.
It could be useful to control the computer when an alert is trigged for example.
==Operating the Monitoring solution==
===First steps in NVGate===
One should go first through the basic settings of the acquisition of NVGate. From NVGate, setup a project dedicated to monitoring and display the scalar values which should be monitored on the current layout.
<font color="#4DA836">'''Create a new project'''</font>
A new project, with the name "Monitoring App", should be created as below when first starting.
Then a new setup configuration should be started
[[Image:Monitoring_OROS_04.png|framed|none]]
<font color="#4DA836">'''Setting up the inputs and analysis'''</font>
Then one should go through inputs, analysis and display setups using for example ''Gotoresult''
[[Image:Monitoring_OROS_05.png|framed|none]]
<font color="#1F497D">''Figure 5 - Inputs setup''
</font>
[[Image:Monitoring_OROS_06.png|framed|none]]
Figure 6 - <font color="#1F497D">''Adding displays of Scalar values''</font>
It is necessary to display scalar values: those will be the ones to be monitored and trigger actions
<font color="#4DA836">'''Adding/naming a layout:'''</font>
<big>'''This current layout must be named "monitoring" (in lowercase)'''</big>. Here below is shown one way to rename the current layout: right click on "Layout1" and the rename possibility is shown
[[Image:Monitoring_Layout_Rename.png|framed|none]]
<font color="#1F497D">''Figure 7 - Renaming the layout''</font>
<font color="#4DA836">'''Saving the project and the model'''</font>
[[Image:Monitoring_OROS_08.png|framed|none]]
Then the project should be saved
===First steps in the Monitoring Application===
Launch "Monitoring_Settings.exe" which is located into Monitoring folder. You will be able to fill some values which are necessary to monitor and operate the watchdog. Those are:
* '''NVGate location''': NVGate folder location (containing NVGate.exe).
* '''Workbook name''': Name of the monitoring model.
* '''Project name''': Name of the monitoring project.
* '''Autonomy kit connection''': Analyzer type should be detected automatically. This is necessary to ensure the Monitoring Box functions properly. It supports V2 and V3s instruments (for OR36 and OR38) as well as OR35TW
* '''Analyzer IP''': If the IP is not defined correctly, the application will not be able to check if the unit is on and therefore will also not be able to boot or shutdown the Analyzer.
* '''RebootBox COM:''' Select the Monitoring Box COM Port. This is required to boot/shutdown the analyzer. If the Monitoring Box is not connected, or the correct drivers are not installed the list will be empty. If more than one COM port are listed, please ensure you are selecting the rebootbox one.
* '''Significant digits:''' Set significant digits to display.
As shown in the dialog window as below
[[Image:Monitoring_OROS_09.png|800px]]
<font color="#1F497D">''Figure 10 - Monitoring and Autonomy box parameters settings''</font>
In the following window, settings can be entered in order to let the system use the email Action
[[Image:Monitoring_OROS_10.png|800px]]
<font color="#1F497D">''Figure 11 – Setup of the email''</font>
===First start of the Monitoring Application===
After parameters set-up, launch the Monitoring application, press "Refresh", It will recognize some parameters and display your scalars in the current layout.
Then, configure the condition you want for each scalar and linked actions. To do that, select an operator to compare the measured value with the target value (which must also be defined). For example, if you select "<nowiki>></nowiki>" and "2" for an acceleration scalar, when this value is larger than 2 the selected action will be triggered.
Finally, close the Monitoring Application, close NVGate, shutdown your analyzer, and then launch the Monitoring Application. If everything starts by itself, Monitoring was setup properly and monitoring has initiated.
===User interface===
The user interface main window is as below. It is built with 3 main sections: Parameters (as described previously), Monitoring panel, and the Logbook.
[[Image:Monitoring_OROS_11.png|framed|none]]
<font color="#1F497D">''Figure 12 - Main user interface window''</font>
[[Image:Monitoring_OROS_12.png|800px]]
<font color="#1F497D">''Figure 13 - Main user interface window''</font>
===Monitoring panel===
[[Image:Monitoring_OROS_13.png|900px]]
<font color="#1F497D">''Figure 14 - The Monitoring panel window''</font>
The columns have the following content:
* Information retrieved from NVGate running project:
* '''Window: '''Selected scalar window<nowiki>'</nowiki>s name.
* '''Module: '''Selected scalar module<nowiki>'</nowiki>s name.
* '''Result: '''Selected scalar process<nowiki>'</nowiki>s name.
* '''Channel: '''Selected scalar channel<nowiki>'</nowiki>s number.
* '''Label: '''Selected scalar input<nowiki>'</nowiki>s name.
* '''Values: '''Selected scalar values (SI).
* '''Units: '''Selected scalar units.
* Information specified by the user:
* '''Operator: '''Condition to be satisfied for actions:
* '''<nowiki>></nowiki>: '''If the measured value is greater than the target value, then action.
* '''<nowiki><</nowiki>: '''If the measured value is less than the target value, then action.
* '''Trigger Values: '''Condition to be satisfied for actions.
* '''Action: '''What do you want to do when the condition is satisfied:
* Activate / Deactivate outputs.
* Run / Stop analyzer.
* Trigger a User Event.
* Launch a macro (coming from NVGate).
* Email
* '''Hold off (s): '''Time holdoff is the delay between each action coming from this scalar (e.g.: 10s means the action cannot be triggered during the 10s following a triggered action.). Default value is 5 seconds and must be higher than 1 second.
* '''Persistence (s): '''Time persistence is the time necessary to trig the action (e.g.: 2s means the action will be triggered only if the condition is respected during 2s).
* '''Comments: '''Comments, it will be used in Email.
* Information computed by the monitoring application:
* '''Status: '''Green if the condition is not satisfied (no action). Red if the condition is satisfied (action).
* '''Events: '''How many times it has been triggered.


==FAQ==
==FAQ==
ChaoranDu
writer
544

edits

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

Navigation menu