Calibration settings
Look up one calibration field: its unit, range, default, and what it changes.
This page is a lookup table. It does not explain how to calibrate a device, because the procedure differs by device family and each has its own page: Calibrate SenseAi and SenseAi Embedded and Calibrate BeamTracker. Every row here links to the section that sets it.
Which field do I change?
Find the symptom, then read across to the field. Change one field, verify against a real run, then change the next.
| The numbers are doing this | Change this |
|---|---|
| A running machine reads as stopped | Running Threshold, lower it |
| A stopped machine reads as running | Stopping Threshold, raise it |
| Status flickers between running and down | Momentum, raise it |
| One-second runs appear inside a long stop | Uptime Filter |
| Tool changes and part loading count as downtime | Auto-Classify Downtimes, or the toggle above it |
| Every press stroke reports a crash | Shock Acceleration Threshold, raise it |
| Part counts run low | Min Object Thickness, lower it, or Depth of View |
| Part counts run high | Reading Speed, slower, or Depth of View, shorter |
| Counts are right but the line reads as stopped mid-run | Downtime Filter |
| A jammed part leaves the line reading as running | Blocked Sensor Stop Time |
SenseAi calibration fields
These apply to SenseAi and SenseAi Embedded. Embedded reads vibration only, so its acoustic copies of the first three fields never come into play.
| Field | Stored as | Unit | Range | Default | Effect | Edited on |
|---|---|---|---|---|---|---|
| Running Threshold | node_vibration_upper_threshold, node_acoustic_upper_threshold | Signal level | 0.001 to 0.7, step 0.0001 | Set during calibration | Where uptime starts counting | Web |
| Stopping Threshold | node_vibration_lower_threshold, node_acoustic_lower_threshold | Signal level | 0.001 to 0.7, step 0.0001 | Set during calibration | Where uptime stops counting | Web |
| Momentum | node_vibration_momentum, node_acoustic_momentum | — | 0.2 to 2, step 0.05 | 0.2 | How much the trace is smoothed before it is compared to the thresholds | Web, mobile |
| Shock Acceleration Threshold | node_shock_threshold | g | 20 to 100, step 1 | 100 | The acceleration above which the device reports a shock. No effect on running or stopped detection | Web |
| Vibration and Acoustics checkboxes | node_analysis_mode | — | At least one selected | Vibration | Which channels the device analyses. Each channel carries its own thresholds and momentum | Web |
| Sensitivity | node_sensitivity | — | 0.001 to 0.96, step 0.001 | 0.5 | A single combined control over what counts as motion, in place of the two thresholds | Mobile, and web below firmware 2.0 |
| Uptime Filter | asset_uptime_filter_seconds | Seconds | 0 or more | Empty | Drops any run shorter than this from uptime | Web |
| Auto-Classify Downtimes | asset_auto_classify_downtimes_less_than_min | Minutes | 0 or more | Empty | Stops under this length are labeled Short Downtime automatically | Web |
| Treat short downtimes as uptime | asset_filter_downtime_instead_of_classification | — | On or off | Off | On, stops under the cutoff become runtime instead of being classified. The field label above changes to Downtime Threshold | Web |
The last three fields belong to the machine, not the sensor, so swapping a sensor carries them across. The rest go with the device. Full map on Where each setting is stored.
Why is my shock slider only reaching 20 g? The 20 to 100 g range is the decided range and the dashboard is being updated to match. A device still on the older build shows a 2 to 20 g slider. Set it to the top of whatever range you are shown, and revisit after the update.
BeamTracker calibration fields
The three distances are measured out from the sensor face, in centimetres. They are the units the fields are labeled with and the units the validation messages quote, so enter them as centimetres rather than converting.
| Field | Stored as | Unit | Range | Default | Effect | Edited on |
|---|---|---|---|---|---|---|
| Reading Speed | node_reading_moving_average_count | Readings averaged | Faster 3X (1), Faster 2X (2), Faster (3), Fast (5), Standard (10), Slow (20), Slower (50) | Standard | How heavily readings are averaged before they are judged. Slower rides over a single noisy reading | Web |
| Min Object Thickness | node_calibration_min_object_tickness | cm | 0 to 100 | 2 | How far the reading must climb back before a part counts as gone. A floor, not a ceiling: set it to the thinnest part you must count | Web |
| Gap from Background | node_calibration_gap_from_background | cm | 0 to 100 | 2 | Spare room left between the detection zone and the background surface | Web |
| Depth of View | node_calibration_max_distance | cm | 1 to 795, and Depth of View plus thickness must fall between 6 and 800 | 400 | The far edge of the detection zone. Anything past it is background | Web, device screen |
| Downtime Filter | node_filter_downtime_seconds | Seconds or minutes | 0 or more | Empty | How long the line stays running after the last part. Every part resets the timer | Web |
| Auto-Classify Downtimes | asset_auto_classify_downtimes_less_than_min | Minutes | Greater than the downtime filter | Empty | Stops under this length are labeled automatically | Web |
| Blocked Sensor Stop Time | node_publish_stop_after_running_seconds | Seconds | 25 or more | 60, toggle off | How long an object may sit in the beam before the line reads as stopped. Needs firmware 2.1 | Web |
| Laser Light | node_is_laser_on | — | On or off | Off | Makes the beam visible for aiming. An installer's aid, not a production setting. Needs firmware 3.0 | Web |
Three ranges are enforced on save and report a message rather than clamping the value:
| Message | What to do |
|---|---|
| Detection distance plus thickness must be between 6 and 800 cm | Reduce whichever of the two you set last |
| Auto-classify must be greater than downtime filter | Raise the auto-classify value above the filter value the message names |
| Minimum is 25 seconds | Raise the blocked sensor stop time |
Where each field is edited
Most fields are web only. Three exceptions are worth knowing before you walk to the machine:
- Momentum and Sensitivity are the only calibration controls in the mobile app. Sensitivity replaces the two thresholds there, so the app adjusts a calibration rather than making one. See Calibrate from the mobile app.
- Depth of View can be set from the BeamTracker's own screen, under Settings then Calibrate Sensor, by placing an object at the far edge you want. See Set the range from the device screen.
- Sensitivity, Momentum and Shock Acceleration Threshold appear on the web for devices below firmware 2.0, each with its own Send button, in place of the threshold sliders.
You do not need this page to calibrate a device. Both procedure pages carry the values you need in the order you set them. Come here when you already know the field and want its range, its default, or the setting it writes.