This tutorial explains how to set up stop detection so that your device correctly recognizes the production and stop states based on the machine's vibrations.

Before you start

Log in to your device's configuration interface. 

Step 1: Run a capture over a normal production cycle

Run a vibration capture over a production cycle of the machine, stopping production at least once. The more representative the capture, the more reliable the stop detection setting will be over time. 

To do this 

1. On the "Production detection" widget, click "Configure"

2. A page then opens: 

• In the "Detection algorithm choice" section, click "Legacy"

• Then click the "Calibrate" button
• Finally, click the "play" button to start the vibration acquisition. It then turns into a "stop" button

• Let the recording run for as long as you like
• Then click the stop button to stop the vibration acquisition
• You can now configure stop detection by following the steps below

Step 2: Set the threshold

The threshold is the boundary between the two states:

• Vibration above the threshold will trigger production detection
• Vibration below the threshold will trigger stop detection

To do this

1. On the curve, identify an area where the machine is stopped, generally the vibration is low amplitude and stable, unless for example a fan is running inside, in which case noise attenuation may be needed.
2. Identify an area where the machine is in production (stronger vibrations)
3. Set the threshold between the two

Warning

• A threshold that is too low creates a risk of detecting production while the machine is stopped
• A threshold that is too high creates a risk of detecting a stop while the machine is producing
• Be sure to click the Save button

The bottom curve, the "detection curve," lets you see which states are detected over time on the segment you just recorded.  Red indicates a stop and blue indicates production.

Step 3: Set the delay

The delay is used to stabilize state changes. It prevents the state from switching due to:

• Brief spikes, such as shocks for example
• Temporary and normal drops in vibration amplitude within the cycle, for example during a finishing phase

Some simple rules

• If the state changes too often, then increase the delay
• If the state changes too slowly, then decrease the delay

The delay is often the setting that "calms" an unstable detection.

You can, of course, also let your device be more responsive with a shorter delay and then smooth the production and stop event curve afterward on your dashboards on your platform.

Step 4: Adjust the sensitivity

Sensitivity helps decide when the vibration is close to the threshold.

• A high sensitivity favors production
• A low sensitivity favors a stop

First set the threshold and the delay, then adjust the sensitivity last.

Step 5: Validate/correct over several cycles

After adjusting, observe the detection curve over several production cycles of your machine.

Quick diagnostic

• The machine is almost always detected as being in production: The threshold is too low, the sensitivity is too high, or the delay is too short
• The machine is almost always detected as being in a stop: The threshold is too high, the sensitivity is too low, or the delay is too short
• The state switches often: The delay is too short or the threshold is placed too close to the "mixed" zone
• The state takes too long to change: The delay is too long

Best practices

• Configure stop detection while the machine is running under normal conditions, avoiding exceptional situations and adjustment phases
• If your cycle includes finishing phases, treat them as production during configuration
• After changing a setting, validate it, if possible, over several cycles
• If stop detection still isn't satisfactory, consider changing the sensor or gain.