|Download Help (Windows Only)|
Parent Topic: Getting Started with Configuring Devices
NI Monitoring Devices continuously monitor data from equipment. However, these devices collect and log data only when initiated by one of several types of triggers.
NI InsightCM Server or software on the devices automatically initiates a data set collection when the following triggers fire.
|Type||Description||Where to Configure||Use Case|
|Time interval||Collect a data set at specific times of day or intervals of time.||Operating States tab on the Asset Configuration page||Ensure that trends are complete enough to provide a useful display of machine conditions.|
|Delta EU||Collect a data set when a feature or spectral band value changes by a specified amount.||Ensure data is collected at the time that a rapid change in measurements occurs.|
|Enter Condition||Collect a data set when the enter condition for an operating state is met.||View the measurements from the time that equipment changed its status.|
|Exit Condition||Collect a data set when the exit condition for the active operating state is met.||View the measurements from the time that equipment changed its status.|
|Alarm set||Collect a data set whenever an alarm is set.||Alarms page||Access data from the time an alarm condition occurred.|
|Alarm clears||Collect a data set whenever an alarm clears.||Access data from the time an alarm condition ended.|
Users manually initiate data set collections via the following triggers.
|Type||Description||Where to Initiate||Use Case|
|Force Trigger||Collect a data set on demand.||In the NI InsightCM web application, on the Devices tab, via the Force Trigger option in the Action menu .||See or check the health of equipment.|
|Test Panel||Temporarily display live data in the NI InsightCM web application.||Test Panel page||See or check the health of equipment without collecting and storing a data set. Test panels are useful for quickly verifying hardware changes or replacements if you do not care about storing the data for future analysis.|
The variety of triggers available in NI InsightCM Server means that devices can perform collections more frequently than the standard time-based intervals. Consider a device whose configuration includes the following settings:
|Total collection duration||1 time unit|
|Timed-based trigger||Every 7 time units|
|Delta EU trigger level||3 engineering units|
The following illustration shows an example of how the device might perform collections over a period of time.
|1||Begin Collection A (Delta EU trigger)||7||Begin Collection D (Alarm cleared)|
|2||End collection||8||End collection|
|3||Begin Collection B (Periodic collection)||9||Begin Collection E (Periodic collection)|
|4||End collection||10||End collection|
|5||Begin Collection C (Alarm set)||11||Begin Collection F (Delta EU trigger)|
|6||End collection||12||End collection|
During multi-second collections, devices always log only the final second of static-sensor data. For example, in the previous graph, if each collection spans 6 seconds, the only value logged is the value collected during the final second. In the previous graph, these are the values at the shaded callout circles.
The following table lists the values logged and displayed on the Data Viewer page during each collection in the previous graph.
Data Set from
|Value in Data Set (°F)|
As mentioned previously, devices log the value of a single-point feature from only the final second of a multi-second collection. However, for multi-second waveforms, devices calculate and log values from the entire duration of the collection. Therefore, the value logged to file and displayed on the Data Viewer page is frequently different from the value at the end of the collection.