Skip to main content
TVela.1
Associate III
Nov 19, 2026 11:47 PM UTC
Question

AIS2DW12: telling human walking from vibration with wake-up + FIFO on a low-power device. Is it feasible?

Hello ST team,

We are using the AIS2DW12 in a small battery-powered device. Wake-up on motion already works. We now want to know whether the sensor can also help us tell human walking apart from vibration, and what configuration you would recommend.

Setup

  • AIS2DW12 on I²C, connected to a low-power, non-STM32 MCU.
  • Only INT1 is connected to the MCU. INT2 is not connected.
  • The MCU spends most of its time in a deep sleep mode and is woken by INT1.
  • Driver: the official ST platform-independent AIS2DW12 driver (ais2dw12_reg.c/.h), unmodified.

Current configuration (wake-up on motion, working)

  • ODR 100 Hz, continuous low-power mode 1 (12-bit), FS ±2 g, BDU enabled.
  • Low-pass filter on the output path, BW_FILT = ODR/2.
  • Activity/inactivity enabled (SLEEP_ON = 1), wake-up threshold WK_THS = 1 LSB.
  • SLEEP_DUR = 0, WAKE_DUR = 0.
  • Wake-up routed to INT1.

What we want to achieve

  1. Detect moving vs. stationary. This already works with the wake-up function.
  2. While the MCU is awake, tell human walking apart from vibration (for example, vehicle or surface vibration). We plan a short, time-limited FIFO capture and a simple rule-based analysis on the MCU, based on signal intensity, periodicity and a typical step cadence of about 1.4–2.5 Hz. We are not planning to use machine learning at this stage.
  3. We do not intend to estimate displacement from acceleration. We know double integration drifts.

Our candidate capture profile has not been validated: 25 Hz, ±4 g, BW = ODR/4, BDU, FIFO in Stream mode, with analysis windows of a few seconds accumulated in MCU RAM.

Questions

  1. Feasibility. Is the AIS2DW12 suitable for telling walking apart from vibration with FIFO analysis on the MCU? Is there an application note, design tip or reference algorithm (pedometer or activity recognition) for the AIS2DW12 / LIS2DW12 family? Can ST libraries such as MotionPM or MotionAR (X-CUBE-MEMS1) be used with this sensor on a non-STM32 MCU, and if not, what would you suggest instead?
  2. Configuration for gait. Which ODR, power mode (low-power mode 1 at 12-bit vs. high-performance at 14-bit), full scale (±2 g vs. ±4 g) and filter bandwidth do you recommend, considering the current consumption? What RMS noise should we expect in low-power mode 1 at 25 Hz and at 100 Hz, so we can set a sensible "stationary" threshold? With a Nyquist frequency of 12.5 Hz at 25 Hz, would you recommend a higher ODR to characterize vibration?
  3. Coexistence of wake-up and FIFO. Can the wake-up function, with or without activity/inactivity, stay active while the FIFO collects data in Stream mode? What is the recommended way to avoid the ODR change caused by sleep: disable SLEEP_ON during capture, use stationary detection, or use Continuous-to-FIFO mode triggered by wake-up?
  4. Filter paths. Does wake-up detection always use the high-pass filtered data (or the user-offset path), whatever the FDS setting? In other words, can we keep the low-pass filter on the output for FIFO analysis without changing wake-up sensitivity?
  5. Durations. Please confirm what SLEEP_DUR = 0 and WAKE_DUR = 0 mean in time. We understand SLEEP_DUR = 0 as 16 × 1/ODR.
  6. FIFO reads over I²C. When the FIFO is enabled, does the register address wrap from OUT_Z_H (0x2D) back to OUT_X_L (0x28), so that several samples can be read in one burst? Is there a recommended maximum burst length?
  7. Interrupts with INT1 only. Do you recommend latched or pulsed notification when the MCU sleeps and is woken only by INT1? How can we avoid lost events, or INT1 staying asserted, when switching between wake-up and FIFO servicing? Can the FIFO watermark and wake-up share INT1, with the source identified by reading ALL_INT_SRC or the status registers?
  8. Known pitfalls. Are there errata or known issues when combining BDU, the FIFO and low-power mode 1?

Thank you in advance for your help and recommendations.