Related Products:

EGMA-007, EGMA-013, EGMA-015, EGMA-016, EGMA-019

Related Documents:

EZDP-2020, EZDP-2038

Type:

Operation

Keywords/Labels:

gating conditions, data sets, delta EU triggers, MCSO operating states, data set collection

Summary:

This article describes alarm operating states.

Operating States

Operating states set different collection settings and/or alarm levels for your assets.

For many assets, it is useful to define discrete operating states that have different collection settings and/or alarm levels. For example, if a motor is running, you may want to collect data more frequently than when the motor is idle or off. Consider the following examples of operating states turbine which has a tachometer sensor with a speed feature.

Operating States

Settings

Run-Up

  • Enter state when RPM rises above 200

  • Collect a data set every 30 seconds

  • Write data sets whose length is 10 seconds

  • Exit state when speed is above 1200 RPM for 20 seconds or speed is less than 200 RPM for 20 seconds

Default

  • Collect a data set once per hour

  • Write data sets whose length is 4 seconds, including 1 seconds of pre-trigger data

Transitions Between Operating States

Defining an operating state for unique equipment conditions allows the device to dynamically switch between collection behaviors. As the Run-Up operating state in the previous example shows, operating states express a condition to enter the state and a condition to exit the state. While in the state, the collection settings and conditions can be configured differently than when the asset is in the default state.

How Operating States Affect Data Visualization

The metadata pane on the Data Viewer page displays the operating state that was active when the device collected the data.

loc_env_metadataopstat.png

Editing an Operating State

Change operating states that you can assign to an alarm.

  1. Select the Navigation menu (noloc_env_navmenu.png) and select System > Operating States.

  2. Select an existing operating state and click Edit.

  3. Adjust the name and weight of the operating state as needed.

  4. Create additional operating states by clicking the Add button and specifying the name and weight of the new operating state.

Gating Conditions for Data Sets and Tags

Use gating conditions to prevent data from being acquired when the condition is not met.

When you enable a gating condition for an operating state, the server evaluates each data set collected under that operating state to see if the gating condition is true. For example, you might want to store data sets only when the equipment is running as indicated by an RMS above 0.1 g. If the gating condition is true for a data set, the server stores the data set. Otherwise, the server discards the data set.

Note

Force trigger always stores a data set and ignores gate conditions.

Trigger Type

Evaluated

Time

support.gif

Delta EU

support.gif

Alarm

support.gif

Force

unsupport.gif

Note

The gating conditions set for an operating state do not affect burst mode data sets. Instead, burst mode data sets are evaluated for gating conditions set in the Burst Mode Collection Conditions section on the Device Properties tab of the Device Configuration page.

Delta EU Triggers

You can define one or more delta EU triggers that initiate an acquisition when a feature or spectral band changes by at least a specified amount. Both positive and negative changes in value cause a delta EU trigger to fire.

Note

If the device is unable to calculate the spectral bands on the device, the delta EU triggers will not fire on the bands.

This setting can be found on the Operating States Tab of the Asset Configuration page.

The following process explains how the InsightCM Server monitors delta EU triggers.

Device Action

Example

When a device starts running, it sets the current value of the feature or spectral band as the baseline EU value.

Consider a feature whose value is 1 upon startup. The baseline EU value is therefore 1.

The device monitors the feature value regularly and compares it to the baseline value to check for a difference greater than the trigger level.

Consider a delta EU trigger with a delta level of 3. Given the baseline EU value of 1, the device checks for values less than -2 and greater than 4 to see if the trigger condition is met.

If the current value increases or decreases by the delta level, the trigger fires and the device performs an acquisition.

If the current value is 8, the device performs one acquisition.

The device sets the value that caused the trigger to fire as the new baseline value.

The new baseline EU value is 8.

The device continues to calculate the feature value to see if the difference from the baseline is greater than the delta level.

Given the new baseline of 8, the device checks for values less than 5 and greater than 11.

Only the initial start-up value and values that cause delta EU triggers to fire can serve as the baseline EU value. In other words, when a device performs a time-, alarm-, or force-triggered acquisition, the device does not update the baseline EU value with the feature value from that acquisition.

MCSA Operating States

An electric motor has discrete operating states such as On (Default), Startup, and Off. The following table lists the default operating states of MCSA devices.

Operating States

Default Settings

Default

  • Collect a data set once per hour.

  • Collect trend values every 5 minutes.

  • Write data sets whose length is 3 seconds, including 1 second of pre-trigger data.

Startup

  • Enter state when Percent Full Load Amps rises above 200% Full Load Amps (FLA), where FLA specifies the motor full load current in amperes according to the motor nameplate.

  • Collect a data set when entering state. The length of this data set is 30 seconds, including 1 second of pre-trigger data.

  • Exit state when Percent Full Load Amps is less than 110% FLA for 5 seconds or the state lasts for 30 seconds.

Off

  • Enter state when Percent Full Load Amps falls below 25% FLA.

  • Collect a data set once per hour.

  • Collect trend values every 5 minutes.

  • Exit state when Percent Full Load Amps rises above 25% FLA.

Methods for Initiating Data Set Collection

Cutsforth Monitoring Devices continuously or wirelessly monitor data from equipment. However, these devices collect and log data only when initiated by one of several types of triggers.

Use one of the following triggers to collect and log data.

Automatic Triggers

Either the software on the devices or the server automatically initiates a data set collection when the following triggers fire.

Use Case

Type

Description

Where to Configure

Time Interval

Collect a data set at specific times of day or intervals of time. Ensure that trends are complete enough to provide a useful display of machine conditions.

Operating States tab on the Asset Configuration page

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 operating state is met. View the measurements from the time that equipment changed its status.

Alarm Set

Collect a data set whenever an alarm condition is met. Access data from the time an alarm condition occurred.

Note

Data sets are sent to the server only when the threshold for new maximum severity is crossed. Otherwise, only trend points are sent to the server, including when an alarm clears.

Alarms page

Alarm Clears

Collect a data set whenever an alarm clears. Access trend point data from the time an alarm condition ends.

Burst Mode

Collect high-resolution data sets at specific times of day or intervals of time. Troubleshoot equipment with data that may indicate an issue.

Device Properties tab on a device's configuration page

Example: Relationships Between Different Trigger Types

The variety of triggers available in the 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.

Setting

Value

Total collection duration

1 time unit

Time-based trigger

Every 7 time units

Delta EU trigger level

3 engineering units

Alarm rule

  • Set Point - 75 degrees

  • Condition - Above

High-Resolution Data Acquisition with Burst Mode

What happens to the device while burst mode is active?

The device suspends normal operation and does not check for changes, such as alarms or operating states, for about 30 seconds before and after acquiring high-resolution data to allow the acquisition anti-aliasing filters to settle.

What happens to high-resolution data if the device cannot connect to the server?

By default, InsightCM discards high-resolution data if the device cannot connect to the server.

Requesting a Periodic Acquisition

Collect data by using force trigger and view a periodic acquisition.

Complete the following steps to force trigger and view a periodic acquisition.

  1. Click the Action menu (noloc_env_action.png) on the Trend viewer toolbar and select Force Trigger.

  2. If the Trend viewer already contains curves for the features or sensors of interest, click the Refresh trend data button (noloc_env_refresh.png). You might need to wait several seconds to see force-triggered data in viewers because devices must perform the periodic acquisition, and then InsightCM must receive and store the data.

Manual Data Acquisition

To view new trend values and sensor measurements between scheduled periodic acquisitions, you can manually request that a device perform an acquisition. These requests are known as force triggers. Force triggers are useful when you want to view current asset data without waiting for the next scheduled acquisition.

You can perform a force trigger from the Action menu (noloc_env_action.png) on the Trend viewer toolbar on the Data Viewer page or on the Devices or Device Dashboard page.

What Is the Duration and Sampling Rate of the Acquisition?

Devices perform force-triggered acquisitions according to the sampling rate, duration, and other periodic-acquisition settings configured in the web application.

Do Force Triggers Affect Regularly Scheduled Periodic Acquisitions?

No. Force-triggered acquisitions do not affect the timing of scheduled periodic acquisitions that devices perform.

Scheduling Temporary High-Resolution Data Acquisition

Schedule a high-resolution data acquisition on a device.

Complete the following steps to schedule high-resolution data acquisition on a device:

  1. Click the Configuration pull-down (noloc_env_config.png) and select Devices.

  2. Double-click a device and select the Device Properties tab.

    Note

    This tab is not available for thermal imaging device configuration pages.

  3. Select the Enable burst mode checkbox.

  4. In the Burst Collection Conditions section, click Time.

  5. In the Edit Condition dialog box, specify how frequently to acquire high-resolution data.

  6. In the Burst Collection Settings section, specify the sample rate in Hz and acquisition length in seconds that you want InsightCM to use for the scheduled high-resolution data acquisition.

  7. Update the device configuration.

Do you need more help?

Was this article helpful?
0 out of 0 found this helpful

Articles in this section