...
If a CM v2 beacon is configured with the default settings per the Installation Guide, then the beacon will automatically generate all four of these metrics approximately once every two minutes
For more details on these metrics, please see: (LINK)
Threshold Value
This is the numerical value of the vibration metric that must be exceeded in order to generate an alert. The value entered may be up to two decimal places, and will be in units of measure as indicated in the policy:
...
Velocity RMS is commonly used indicate the presence of mid-frequency faults, like looseness, imbalance, and mis-alignment. Keep in mind that the vibration levels are sensitive to sensor placement, and care should be taken when using these values, per the instruction of the published standards. To help address uncertainty in relative vibration levels due to sensor placement, the Motion Condition Policy may be useful, as it establishes a baseline vibration level for the specific beacon placement on the asset, and alerts based on deviations from this baseline.
For acceleration-based metrics on the BEEKs CM v2, no specific standard is used to set the bandwidth. The default configuration settings will provide a bandwidth of approximately 2 Hz - 7500 Hz (+/- 25% error). This higher bandwidth is used since higher frequency faults like bearing defects and gear tooth defects typically manifest in higher-frequency acceleration-based metrics. Although the Vibration Threshold Policy may be used with Acceleration Peak-to-peak and Acceleration RMS, care should be taken in using these as there are no established/ published values to compare them to. It may, however, be suitable to set levels based on your own historical observation. For acceleration-based metrics, it is expected that better performance will be achieved using the Motion Condition Policy, which determines a unique baseline for the asset on which the beacon is installed and alerts when the vibration levels deviate significantly from this for a sustained period of time.
...