Difference between revisions of "NVGate Event definition"

Jump to navigation Jump to search
m
English edits
m (English edits)
Line 6: Line 6:
==Connect ==
==Connect ==
[[Image:Reports_Tools_Ribbons_17.png|framed|none]]
[[Image:Reports_Tools_Ribbons_17.png|framed|none]]
On tab acquisition, this part Manage the event and corresponding triggers. This group allows selecting the event type (source, setup) and associates it with the plug-in analyzers triggers
On the acquisition tab, this area manages events and corresponding triggers. This group allows selecting the event type (source, setup) and associates it with the plug-in analyzers triggers




This button opens the corresponding Event properties. The opened dialog shows both the source signal setup and the detection settings (may be spitted in different tabs).
This button opens the corresponding Event properties. The opened dialog shows both the source signal setup and the detection settings (may be split in different tabs).
On this dialog box you can easily "drag and drop" events to "start", "Stop" or "trigger" any NVGate plug in.
On this dialog box you can easily "drag and drop" events to "start", "Stop" or "trigger" any NVGate plug in.
[[File:events.png|framed|none]]
[[File:events.png|framed|none]]


The available event types are below
The available event types are below:




==Edge detection==
==Edge detection==
[[Image:Reports_Tools_Ribbons_361.png]] Edge: Detect when the signal from an input or a recorded track cross a threshold.
[[Image:Reports_Tools_Ribbons_361.png]] Edge: Detect when the signal from an input or a recorded track crosses a threshold.
This module is used with the analog inputs (tach pulse or hammer impact). This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.
This module is used with the analog inputs (tach pulse or hammer impact). This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.


Line 47: Line 47:


==RPM==
==RPM==
[[Image:Reports_Tools_Ribbons_364.png]]RPM: Detect when a tachometer is below or above a specified angular speed. This module is associated with the Tachometer module. You need first to activate it on Tachometer plug in.  This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.
[[Image:Reports_Tools_Ribbons_364.png]]RPM: Detect when a tachometer is below or above a specified angular speed. This module is associated with the Tachometer module. You need to first activate it on Tachometer plug in.  This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.


* '''Label''': the name of the event (by default RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Label''': the name of the event (by default RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
Line 79: Line 79:


==Delta RPM==
==Delta RPM==
[[Image:Reports_Tools_Ribbons_365.png]]Delta-RPM: Same as RPM but generates an event at each step. This module is associated with the Tachometer module, You need first to actibate it on Tachometer plug in.. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.
[[Image:Reports_Tools_Ribbons_365.png]]Delta-RPM: Same as RPM but generates an event at each step. This module is associated with the Tachometer module. You need first to activate it on Tachometer plug in. It is used to trigger a plug-in by step. This trigger can be applied to any plug-in analyzer including Waterfall and Recorder.


* '''Label''': the name of the event (by default Delta RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
* '''Label''': the name of the event (by default Delta RPM n, with 1 <nowiki><</nowiki>= n <nowiki><</nowiki>= 2).
Line 291: Line 291:
==User events==
==User events==
[[Image:Reports_Tools_Ribbons_368.png]] User: Generates an event when the operator presses the corresponding event button in the software/remote controller interface.
[[Image:Reports_Tools_Ribbons_368.png]] User: Generates an event when the operator presses the corresponding event button in the software/remote controller interface.
Four user events are available. These events are compatible with the macros. They are particularly useful to run several plug-ins at different time in the same analysis. It can also be put in the control pannel or control by NVDrive.
Four user events are available. These events are compatible with the macros. They are particularly useful to run several plug-ins at different time in the same analysis. It can also be put in the control panel or controlled by NVDrive.


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


* '''Label''': allows to rename the event.
* '''Label''': Allows to rename the event.
* '''Trigger''': The user event<nowiki>’</nowiki>s triggering.
* '''Trigger''': The user event<nowiki>’</nowiki>s triggering.


Line 302: Line 302:


==Monitoring Solution==
==Monitoring Solution==
If you need  more advanced trigger and action, plase have a look on the [[Monitoring_Solution|the monitoring solution]].
If you would like more advanced trigger and actions, please have a look on the [[Monitoring_Solution|the monitoring solution]].
maintenancecenter, writer
115

edits

Navigation menu